
From nobody Tue Apr  1 08:09:08 2014
Return-Path: <eric@notcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D6D31A08B1 for <ietf@ietfa.amsl.com>; Mon, 31 Mar 2014 12:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
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 Z-0I4pwmeffn for <ietf@ietfa.amsl.com>; Mon, 31 Mar 2014 12:06:41 -0700 (PDT)
Received: from mail-yk0-f175.google.com (mail-yk0-f175.google.com [209.85.160.175]) by ietfa.amsl.com (Postfix) with ESMTP id 518A01A6F32 for <ietf@ietf.org>; Mon, 31 Mar 2014 12:06:41 -0700 (PDT)
Received: by mail-yk0-f175.google.com with SMTP id 131so6521813ykp.6 for <ietf@ietf.org>; Mon, 31 Mar 2014 12:06:38 -0700 (PDT)
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:content-type; bh=6oVkf954FS6g/YDChMnhw43EIuwRNICTlr9T1IyWygI=; b=BoAEfvys+Tzb9gYeuUeDpvqAvQszv8wZy5+qw2BD6tCCwipI7SW0LJHlWDbmRzXjOi FCiRlLiOcYcBIkWe65RmRms+YOBArWpfKACQeBAfBzPIuiBWL7CaqKpMIE0nV26qcM5Y Dw22POWFLt7/MmlKxhlsaF8fCIYe4505za8edNS7IHZcRPwzKuPmH6vmfpsVzP48R0p3 uwG1pGM/a156D9HZBBu+C41D1kr8JvLrgjANF7NhGigjTOSskhjxIl/Yqn/DpySTtmBL o9oqz0h7WKudAJakDKWr7EOrCMdgvdWAcp70XOt9L53PI7qFXRoMnekSy0zuoFETrckk MP/A==
X-Gm-Message-State: ALoCoQkTziWPat2iUeF0YGVUh94rzNjGf5Ri2i8EDJ36ZYDUGcYpD83SZYKFaU5GA3B6vwSuMeWn
MIME-Version: 1.0
X-Received: by 10.236.139.70 with SMTP id b46mr39035035yhj.63.1396292797978; Mon, 31 Mar 2014 12:06:37 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Mon, 31 Mar 2014 12:06:37 -0700 (PDT)
In-Reply-To: <CAM0WBXWAm8mAAAXKxNaCi+x3O7hfPr_U5_bcvzWZKYExCUSiAA@mail.gmail.com>
References: <20140326195717.26906.70350.idtracker@ietfa.amsl.com> <CAM0WBXWAm8mAAAXKxNaCi+x3O7hfPr_U5_bcvzWZKYExCUSiAA@mail.gmail.com>
Date: Mon, 31 Mar 2014 15:06:37 -0400
Message-ID: <CA+97oKMnSJ2g+32OwrUHzSzCzaNtRRnXTMsJvHYbDgPsNF8GvA@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-psc-updates-03.txt> (Updates to MPLS Transport Profile Linear Protection) to Proposed Standard
From: Eric Osborne <eric@notcom.com>
To: Yaacov Weingarten <wyaacov@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VKe0BVpGCA0S0_fNYkfBrLPgR5I
X-Mailman-Approved-At: Tue, 01 Apr 2014 08:09:03 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Mar 2014 19:06:43 -0000

Hi Yaacov-

  Thanks for the review.  I'll fix the typos you point out in 1 and 2c.
As far as the non-typo bits:

----
2. Section 5 is very confusing to me -
       a. My understanding was that the PSC Control Logic always
receives two inputs - one local and one remote and decides on the the
next state based upon these two inputs and the current state of the
Control Logic as defined in the FSM. You, however, state that you need
to explain how the Control Logic should react to different inputs.
After explaining, the two cases of different inputs, you then state
that the reaction to these inputs is already covered in RFC6378, and
what needs to be clarified is the recovery from the input that was
defining the current state! Not sure what you really meant to say, but
it would help if you gave a consistent message throughout as to what
needs to be clarified!
----

Section 5 clarifies the behavior when we have multiple simultaneous
requests from either the Local or Remote logic.  Consider the text
"In both cases the question is not how the PSC Control logic decides
which of these is the one it acts upon.....The point that this section
clears up is around what happens when the highest priority input goes
away.... A strict reading of the FSM would suggest that PSC transition
from PA:F:L into N, and at some future time (perhaps after the remote
request refreshes) PSC would transition from N to PA:F:R.  This is an
unreasonable behavior, as there is no sensible justification for a
node behaving as if things were normal (i.e. N   state) when it is
clear that they are not."

I've had multiple questions around this exact behavior offline, which
is the motivation for the clarification.  Nowhere in rfc6378 do we
make explicit that when a higher priority request goes away, the lower
priority request is evaluated.  A langauge-laywer interpretation of
rfc6378 could lead to incompatible implementations, and since the
behavior I spell out in section 5 is what a sensible implementation
would do anyways, the clarification just helps those who would work
strictly by the book.



---
     b. At some point you state that the Control Logic should remember
the last received local and remote inputs for reevaluation when the
driving input is cleared. But then you go and prove that this is not
necessarily true, since the inputs may change during the interim (went
from R(LO) to R(SF-W)). Therefore, I think that the correct
interpretation should be based on the two current inputs as provided
by the Local Request Logic and Remote Input. What may need to be
corrected is that each of these two units should persist their latest
outputs to continue to be provided as input to the Control Logic.
----

If I disprove my thesis in the course of an example, it is purely by
accident.  I'm not sure I see where you're reading that, though.
Section 5's text that says "What should happen is that the PSC Control
logic should, upon removal of an input, immediately reevaluate all
other inputs to decide on the next course of action.  This requires an
implementation to store the most recent local and remote inputs
regardless of their eventual use as triggers for the PSC Control
Logic" says what I think you are asking for.  Right?  If that's not
sufficient, can you show me exactly where the misleading text is?





eric


On Wed, Mar 26, 2014 at 5:08 PM, Yaacov Weingarten <wyaacov@gmail.com> wrote:
> Hi,
>
> Some comments and nits regarding this draft:
>
> 1. The Abstract states "This document contains four updates to", whereas the
> first statement of the Introduction states "This document contains firve
> updates to" -  so aside from the spelling mistake please align the two
> statements to the correct number of updates.
>
> 2. Section 5 is very confusing to me -
>        a. My understanding was that the PSC Control Logic always receives
> two inputs - one local and one remote and decides on the the next state
> based upon these two inputs and the current state of the Control Logic as
> defined in the FSM. You, however, state that you need to explain how the
> Control Logic should react to different inputs. After explaining, the two
> cases of different inputs, you then state that the reaction to these inputs
> is already covered in RFC6378, and what needs to be clarified is the
> recovery from the input that was defining the current state! Not sure what
> you really meant to say, but it would help if you gave a consistent message
> throughout as to what needs to be clarified!
>      b. At some point you state that the Control Logic should remember the
> last received local and remote inputs for reevaluation when the driving
> input is cleared. But then you go and prove that this is not necessarily
> true, since the inputs may change during the interim (went from R(LO) to
> R(SF-W)). Therefore, I think that the correct interpretation should be based
> on the two current inputs as provided by the Local Request Logic and Remote
> Input. What may need to be corrected is that each of these two units should
> persist their latest outputs to continue to be provided as input to the
> Control Logic.
>      c. Your first example, (in the third paragraph) describes two FS inputs
> (a "local" and "remove" [should be changed to "remote"]) to the Control
> Logic, but then in the fifth paragraph it is a "local SF" that is driving
> the state. Please change this to "local FS".
>
> Hope these help,
> yaacov
>
>
> On Wed, Mar 26, 2014 at 9:57 PM, The IESG <iesg-secretary@ietf.org> wrote:
>>
>>
>> The IESG has received a request from the Multiprotocol Label Switching WG
>> (mpls) to consider the following document:
>> - 'Updates to MPLS Transport Profile Linear Protection'
>>   <draft-ietf-mpls-psc-updates-03.txt> as Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2014-04-09. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>    This document contains four updates to the Protection State
>>    Coordination (PSC) logic defined in RFC6378, "MPLS Transport Profile
>>    (MPLS-TP) Linear Protection" . Two of the updates correct existing
>>    behavior.  The third clarifies a behavior which was not explained in
>>    the RFC, and the fourth adds rules around handling capabilities
>>    mismatches.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-psc-updates/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-psc-updates/ballot/
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
>
>
>
> --
> Thanx and BR,
> yaacov
>
> Still looking for new opportunity
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>


From nobody Tue Apr  1 08:09:15 2014
Return-Path: <eric@notcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C209B1A6F72 for <ietf@ietfa.amsl.com>; Mon, 31 Mar 2014 12:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable
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 ly-iFkLDNG1t for <ietf@ietfa.amsl.com>; Mon, 31 Mar 2014 12:08:52 -0700 (PDT)
Received: from mail-yh0-f45.google.com (mail-yh0-f45.google.com [209.85.213.45]) by ietfa.amsl.com (Postfix) with ESMTP id 992141A6F2A for <ietf@ietf.org>; Mon, 31 Mar 2014 12:08:52 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id a41so8001195yho.4 for <ietf@ietf.org>; Mon, 31 Mar 2014 12:08:49 -0700 (PDT)
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:content-type; bh=xr/z2NloJG1brEXJYr3wRiOZO3p489bvAujt+ojuKA4=; b=YK89J/Bmz/UuQBaWGxZgGa895rDKMJYmgTfS5DcWvA9cZJScKqZLAvxyzDdbsjnlok flc+PnJqEp8NnKOmGs7VZ4sJDs5qO+b6jE0zcIERI3puihG+0yD3s+p049FYfhcueTAz XRnSjlXfHc3JVHosYOBvNT7i/p5QuRelQNkUTFDA3TRSemGPyJRQDzEux8i6M8b8Gg47 ZFI7TV7HS80+36P3PrrZyAIvJZFszdkL1IG5AtrRKDsWUmDIvRa0JA9BxxV0nv55XF1H BbM1RDULm6umi9fc29sNInsvTdVj/pJtZK4Y4fW+B+b1qRxjZksp2ziLNwz/fOcninax aqbw==
X-Gm-Message-State: ALoCoQlm/zm258c/YJgYo3IkvX6pqtSyMzs3kiQuUNZAFg2DGV8VRrGykxIQNZE2qGQbcqeJ2rOH
MIME-Version: 1.0
X-Received: by 10.236.81.79 with SMTP id l55mr4008810yhe.154.1396292929221; Mon, 31 Mar 2014 12:08:49 -0700 (PDT)
Received: by 10.170.60.5 with HTTP; Mon, 31 Mar 2014 12:08:49 -0700 (PDT)
In-Reply-To: <08fb01cf4932$a0b51c50$e21f54f0$@olddog.co.uk>
References: <08fb01cf4932$a0b51c50$e21f54f0$@olddog.co.uk>
Date: Mon, 31 Mar 2014 15:08:49 -0400
Message-ID: <CA+97oKNeKjAn5DmxTkFQPx6ifYeUaWYgMqUfT7EG=TH6yf48Nw@mail.gmail.com>
Subject: Re: [mpls] Last Call: <draft-ietf-mpls-psc-updates-03.txt> (Updates to MPLS Transport Profile Linear Protection) to Proposed Standard
From: Eric Osborne <eric@notcom.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FnUODmzllLaM3uMpptbmxrN4oLs
X-Mailman-Approved-At: Tue, 01 Apr 2014 08:09:12 -0700
Cc: "mpls@ietf.org" <mpls@ietf.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Mar 2014 19:08:54 -0000

Hello Adrian, WG-

  I propose this:

Malformed TLV: reject the message and vigorously report it
Unknown TLV type: report the TLV, ignore the TLV and process the rest
of the message

I'm open to other opinions, though.




eric

On Wed, Mar 26, 2014 at 4:33 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> Hi,
>
> I have one issue I want to bring up as a last call comment. I discussed it
> briefly with Eric and we agreed it is something that needs wider discussion than
> just a late editorial change.
>
> Currently 6378 does not describe the format of PSC TLVs and
> draft-ietf-mpls-tp-itu introduces one without defining the format tightly.
> Therefore, this document contains a simple statement of the fields and meanings
> in a TLV.
>
> However, 6378 also does not state how to handle:
> - a malformed TLV
> - an unknown TLV type
>
> We need to add some simple text to cover this.
>
> Options for each of the above are:
> - ignore the TLV but process the message
> - report the TLV but ignore the TLV and process the message
> - ignore the message
> - report the message but ignore it
> - reject the message
>
> Thanks,
> Adrian
>
>> -----Original Message-----
>> From: mpls [mailto:mpls-bounces@ietf.org] On Behalf Of The IESG
>> Sent: 26 March 2014 19:57
>> To: IETF-Announce
>> Cc: mpls@ietf.org
>> Subject: [mpls] Last Call: <draft-ietf-mpls-psc-updates-03.txt> (Updates to
> MPLS
>> Transport Profile Linear Protection) to Proposed Standard
>>
>>
>> The IESG has received a request from the Multiprotocol Label Switching WG
>> (mpls) to consider the following document:
>> - 'Updates to MPLS Transport Profile Linear Protection'
>>   <draft-ietf-mpls-psc-updates-03.txt> as Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2014-04-09. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>    This document contains four updates to the Protection State
>>    Coordination (PSC) logic defined in RFC6378, "MPLS Transport Profile
>>    (MPLS-TP) Linear Protection" . Two of the updates correct existing
>>    behavior.  The third clarifies a behavior which was not explained in
>>    the RFC, and the fourth adds rules around handling capabilities
>>    mismatches.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-psc-updates/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-mpls-psc-updates/ballot/
>>
>> No IPR declarations have been submitted directly on this I-D.
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@ietf.org
>> https://www.ietf.org/mailman/listinfo/mpls
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls


From nobody Tue Apr  1 09:47:48 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7273C1A0998 for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 09:47:43 -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, SPF_PASS=-0.001] autolearn=ham
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 mM_O2OcVdtKX for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 09:47:41 -0700 (PDT)
Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) by ietfa.amsl.com (Postfix) with ESMTP id 9C06B1A0564 for <ietf@ietf.org>; Tue,  1 Apr 2014 09:47:40 -0700 (PDT)
Received: by mail-lb0-f180.google.com with SMTP id 10so6996644lbg.25 for <ietf@ietf.org>; Tue, 01 Apr 2014 09:47:36 -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:content-type; bh=qzturFC/YcTldRD3f/cEDu2Hk9/hhNEAjum/0dEWgjo=; b=VMnLGVrVWvzMmWnrV+G0RaTfmY3T69QErCrDsrhaEPq/JxZtEc8VHAWiEel4Dq4PQH wTmdcnp21ZpJPQhaMaSUv9ysBIfXR4pkY029qb+hKsGmvQVTYVp6pTqy7x3rsRzwfbwV 6KiHzWU3mCnECipoDss5G0AMpMR4BBOh8wB2+8zEI6pfxEKrN6pl1FvKmnjlsycNdMLU +QZNcsYkm8YaAYaUsAyrM38l65EdSvKmZiSq1EgYV3a8z1YNVaiBzhpB/HAmzyFXZ5WW rzIgaMJYrzF06qh/VCS0rJy84jsvwUfQHQwp83t+LSl7amRGM38Ww5BxOC0CLmPXiSy8 tjSg==
MIME-Version: 1.0
X-Received: by 10.112.147.36 with SMTP id th4mr2310902lbb.32.1396370856478; Tue, 01 Apr 2014 09:47:36 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Tue, 1 Apr 2014 09:47:36 -0700 (PDT)
In-Reply-To: <m28urr9rcp.wl%randy@psg.com>
References: <20140330151432.2721.qmail@joyce.lan> <A3DE810811F791EDC532BDFB@JcK-HP8200.jck.com> <m28urr9rcp.wl%randy@psg.com>
Date: Tue, 1 Apr 2014 12:47:36 -0400
Message-ID: <CAMm+LwiE_U2jY8xkdUCNxACaTVM6h8i-Xh1PnK_PC-QvRLkyCw@mail.gmail.com>
Subject: Re: SMTP RFC: "MUST NOT" change or delete Received header
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=047d7b3a8666e00c8d04f5fdec6d
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4KaC5k-ngDfxuTaUIgmjX-0KWpc
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 16:47:43 -0000

--047d7b3a8666e00c8d04f5fdec6d
Content-Type: text/plain; charset=ISO-8859-1

If you need to do manual debugging daily then you are not engaged in
debugging, you have a protocol that depends on manual intervention.

That is an architectural defect.

I understand your pain, what I don't understand is why you tolerate it or
my business model for mitigating your problem. I have no qualms about
telling people that their 'requirement' to run infrastructure obsolete
twenty years is not a requirement I recognize.

The bar for justifying MUST requirements should be very high. They
certainly should not become a mechanism for people to defer the cost of
upgrading their infrastructure onto the rest of us.


"Running a relay" is not a properly stated requirement. What is this relay
for? If it is for gating X.400 or DECNET mail then my response would be
more or less 'not only do I reject your requirement, I would if it were
legal and expeditious to do so personally go to the system in question and
reprogram it with a very large axe'. The privacy concerns for running
different types of gateway/relay/mailing list are all very different.
Simply stating they are essential does not persuade me.

Every time a message passes through a relay it is because either the sender
has configured their mail to do that or the receiver has configured their
mail to do use it. So the privacy concerns are very different for those
hops to the concerns that arise when the sender hands a message over to the
receiver.

The reason the privacy concerns come up is that the relay has no idea what
role it is forwarding the message under, whether it is acting for the
sender or the receiver.




On Sun, Mar 30, 2014 at 7:52 PM, Randy Bush <randy@psg.com> wrote:

> the day was weird enough already without my having to agree with an
> entire, typically long, jck posting :)
>
> the truth is, i have not used received: headers to authenticate/debug
> [0] since yesterday.  but it's not yet 09:00, so there is still time
> today.
>
> randy
>
> ---
>
> [0] - from an ops pov, loop detection, lists subscribing to eachother,
>       and all that stuff is debugging.
>
>


-- 
Website: http://hallambaker.com/

--047d7b3a8666e00c8d04f5fdec6d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">If you need to do manual debugging daily then you are not =
engaged in debugging, you have a protocol that depends on manual interventi=
on.<div><br></div><div>That is an architectural defect.</div><div><br></div=
>
<div>I understand your pain, what I don&#39;t understand is why you tolerat=
e it or my business model for mitigating your problem. I have no qualms abo=
ut telling people that their &#39;requirement&#39; to run infrastructure ob=
solete twenty years is not a requirement I recognize.</div>
<div><br></div><div><div>The bar for justifying MUST requirements should be=
 very high. They certainly should not become a mechanism for people to defe=
r the cost of upgrading their infrastructure onto the rest of us.</div>
</div><div><br></div><div><br></div><div>&quot;Running a relay&quot; is not=
 a properly stated requirement. What is this relay for? If it is for gating=
 X.400 or DECNET mail then my response would be more or less &#39;not only =
do I reject your requirement, I would if it were legal and expeditious to d=
o so personally go to the system in question and reprogram it with a very l=
arge axe&#39;. The privacy concerns for running different types of gateway/=
relay/mailing list are all very different. Simply stating they are essentia=
l does not persuade me.</div>
<div><br></div><div>Every time a message passes through a relay it is becau=
se either the sender has configured their mail to do that or the receiver h=
as configured their mail to do use it. So the privacy concerns are very dif=
ferent for those hops to the concerns that arise when the sender hands a me=
ssage over to the receiver.</div>
<div><br></div><div>The reason the privacy concerns come up is that the rel=
ay has no idea what role it is forwarding the message under, whether it is =
acting for the sender or the receiver.</div><div><br></div><div><br></div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Sun,=
 Mar 30, 2014 at 7:52 PM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<br><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex">
the day was weird enough already without my having to agree with an<br>
entire, typically long, jck posting :)<br>
<br>
the truth is, i have not used received: headers to authenticate/debug<br>
[0] since yesterday. =A0but it&#39;s not yet 09:00, so there is still time<=
br>
today.<br>
<br>
randy<br>
<br>
---<br>
<br>
[0] - from an ops pov, loop detection, lists subscribing to eachother,<br>
=A0 =A0 =A0 and all that stuff is debugging.<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Website: <a =
href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div>

--047d7b3a8666e00c8d04f5fdec6d--


From nobody Tue Apr  1 12:46:17 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B06B51A09FA; Tue,  1 Apr 2014 12:46:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable
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 qRvwJFqRB2EM; Tue,  1 Apr 2014 12:46:09 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 953471A09F1; Tue,  1 Apr 2014 12:46:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 9FF2E1E45B4; Tue,  1 Apr 2014 12:45:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rAJ0zoMeEpfo; Tue,  1 Apr 2014 12:45:26 -0700 (PDT)
Received: from [IPv6:2001:14b8:400:f33:1993:71e2:177d:2aae] (unknown [IPv6:2001:14b8:400:f33:1993:71e2:177d:2aae]) by c8a.amsl.com (Postfix) with ESMTPSA id A78191E45AA; Tue,  1 Apr 2014 12:45:25 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: IANA changes
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Tue, 1 Apr 2014 22:46:01 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D272A88D-B935-4BAE-A649-13815E5896D3@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ArJ5MME-8gbj_QH1IBhYV2qUrBs
Cc: "internetgovtech@iab.org" <internetgovtech@iab.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "internetgovtech@iab.org" <internetgovtech@iab.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 19:46:10 -0000

I wanted to provide some updates and pointers on the topic of the =
possible changes regarding IANA. After the NTIA announcement, there has =
been plenty of discussion at last week's ICANN meeting, for instance. =
And it is important the enough people participate discussion also from =
an IETF perspective, so please join the discussion on the =
internetgovtech list (led by the IAB).

Here's my summary: http://www.ietf.org/blog/2014/04/iana-changes/

Jari Arkko
IETF Chair


From nobody Tue Apr  1 12:53:21 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9290B1A09C8 for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 12:53:19 -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, SPF_PASS=-0.001] autolearn=ham
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 DAaFHFF_gL4k for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 12:53:17 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 5E8661A09A8 for <ietf@ietf.org>; Tue,  1 Apr 2014 12:53:17 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hi2so4415905wib.5 for <ietf@ietf.org>; Tue, 01 Apr 2014 12:53:13 -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:content-type; bh=PQEr7k6BwS0pNdFrVOprXmWPEBoArdBc5xDCCxu35HE=; b=Y8c2/imX9uFiSGNwFNHKF6Q1KBVO9nbRVQsEVV98sZFWs7pFfYLS84oabcYny0RYsk LI37/z+iEJqa5eEWZo8aMJqpWL6ZXy4aKBbugE2iXzmqh0XJryBA0CNAx/AlsrB2vDwt GdJUlH9U03f4szEQL7yG3t6HO2if8vO4PwVtsMQd2UEV6cfDLq9TnZNop/m2WDmSi8m8 FJOaTUECKbI8SY1Rq3cjvX6et3lSslrDJnbtw6J9HzP3kAqkqJ3qRBoJHWqOtlcuSkL0 IQh3hRIpVnfAGqgsiyBpgtjPUHpmXcSFFidfr3Fw2lg7BbHQvy0p28zbjJXNkovUufcc 571A==
MIME-Version: 1.0
X-Received: by 10.180.12.233 with SMTP id b9mr22315468wic.8.1396381992970; Tue, 01 Apr 2014 12:53:12 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Tue, 1 Apr 2014 12:53:12 -0700 (PDT)
In-Reply-To: <9EC12CC9-81CD-4C3E-ADD1-283615767B17@nominum.com>
References: <20140330151432.2721.qmail@joyce.lan> <A3DE810811F791EDC532BDFB@JcK-HP8200.jck.com> <CAMm+LwjrY44GhdMCkqEL_YssNNR=isx-cSQ6KZH-1bkXO7RJWQ@mail.gmail.com> <86005B600BB2261DFDEE715B@JcK-HP8200.jck.com> <9EC12CC9-81CD-4C3E-ADD1-283615767B17@nominum.com>
Date: Tue, 1 Apr 2014 12:53:12 -0700
Message-ID: <CAL0qLwZExfPYj_F2RrD_EueZk8owM=Y26r1OQ9qsDRjZ9Xy=Nw@mail.gmail.com>
Subject: Re: SMTP RFC: "MUST NOT" change or delete Received header
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c24114a9728804f600842e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TmqT9c3WkPssttu4NZkp0S0mDMo
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 19:53:19 -0000

--001a11c24114a9728804f600842e
Content-Type: text/plain; charset=ISO-8859-1

On Sun, Mar 30, 2014 at 5:38 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Mar 30, 2014, at 6:44 PM, John C Klensin <john-ietf@jck.com> wrote:
> > Whether one accepts it or not, "been here already" tests are not
> > about debugging.  They are about loop detection and DoS attacks.
>
> Are there MTAs that make use of the Received: header for loop detection?
>
>
sendmail does, and has since the '80s.

-MSK

--001a11c24114a9728804f600842e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sun, Mar 30, 2014 at 5:38 PM, Ted Lemon <span dir=3D"lt=
r">&lt;<a href=3D"mailto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon=
@nominum.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On Mar 30, 2014, at 6:44 PM,=
 John C Klensin &lt;<a href=3D"mailto:john-ietf@jck.com">john-ietf@jck.com<=
/a>&gt; wrote:<br>

&gt; Whether one accepts it or not, &quot;been here already&quot; tests are=
 not<br>
&gt; about debugging. =A0They are about loop detection and DoS attacks.<br>
<br>
</div>Are there MTAs that make use of the Received: header for loop detecti=
on?<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra">sendmail does, and =
has since the &#39;80s.<br><br>-MSK<br></div></div>

--001a11c24114a9728804f600842e--


From nobody Tue Apr  1 15:49:15 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98CA51A6EDC for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 15:49:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 ayDC8c8jiHD9 for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 15:49:11 -0700 (PDT)
Received: from mail-qg0-x235.google.com (mail-qg0-x235.google.com [IPv6:2607:f8b0:400d:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBBD1A6EDB for <ietf@ietf.org>; Tue,  1 Apr 2014 15:49:11 -0700 (PDT)
Received: by mail-qg0-f53.google.com with SMTP id i50so1561415qgf.12 for <ietf@ietf.org>; Tue, 01 Apr 2014 15:49:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=jxmuYkG/lnfhG8p5KGkW9BDHxi4Yvy1xTM7M4agabhg=; b=usoo+hIjbqa4nM+4W+8RlJg58f4Xj8vp5L0+vyxciQR27x3gal2H1+7rRJ7IJ7wloL 2KWGQaXUkO3dkCGWJ+ZtlDYmuMKTvM6XNGm3wepyWVeZ5XiwGEbHgIo2tlrOPWvswd4i L4FqMZwcejedZr6sij7sOIbKNqsTfBw33NJ6LANnm0N5o4jgoTG1EdsReQUfE95ugzjl DRCIrkKknlgAyQ4Na3ebXdHjTMUQR6bNcbH30NCmiIFHFZFfMZPK4ZnGrT1SgY776ktH EpIHW7BYYIYvKplvgj2AIMy0mgZPSTvWu+17Eh+8jcwxRz3ufeOv36p5c4kMI3jcsPz4 vQUg==
X-Received: by 10.224.131.132 with SMTP id x4mr5639726qas.97.1396392547339; Tue, 01 Apr 2014 15:49:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.205.69 with HTTP; Tue, 1 Apr 2014 15:48:47 -0700 (PDT)
In-Reply-To: <20140401220040.F06667FC394@rfc-editor.org>
References: <20140401220040.F06667FC394@rfc-editor.org>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 1 Apr 2014 18:48:47 -0400
Message-ID: <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
To: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XdHZ_K-HmEngS-SuAI-z8Z1HUW0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 22:49:13 -0000

As a tea drinker, I'm very happy to see this extension to RFC 2324.
However, many people drink their tea with lemon, and that doesn't
really fit into any of the addition-types in section 2.2.1. Another
addition-type may be required.

Cheers,
Andy


On Tue, Apr 1, 2014 at 6:00 PM,  <rfc-editor@rfc-editor.org> wrote:
> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 7168
>
>         Title:      The Hyper Text Coffee Pot
>                     Control Protocol for Tea Efflux Appliances
>                     (HTCPCP-TEA)
>         Author:     I. Nazar
>         Status:     Informational
>         Stream:     Independent
>         Date:       1 April 2014
>         Mailbox:    inazar@deviantart.com
>         Pages:      7
>         Characters: 14490
>         Updates:    RFC 2324
>
>         I-D Tag:    draft-nazar-htcpcp-tea-00.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc7168.txt
>
> The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification
> does not allow for the brewing of tea, in all its variety and
> complexity.  This paper outlines an extension to HTCPCP to allow
> for pots to provide networked tea-brewing facilities.
>
>
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see http://www.rfc-editor.org/search
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>


From nobody Tue Apr  1 16:14:31 2014
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4A731A0007 for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 16:14:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 DpPhXfS3MpQq for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 16:14:27 -0700 (PDT)
Received: from st11p00mm-asmtp002.mac.com (st11p00mm-asmtpout002.mac.com [17.172.81.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86EBB1A0004 for <ietf@ietf.org>; Tue,  1 Apr 2014 16:14:25 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Received: from 173-11-110-132-sfba.hfc.comcastbusiness.net (173-11-110-132-SFBA.hfc.comcastbusiness.net [173.11.110.132]) by st11p00mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N3D00LIWKJV5T40@st11p00mm-asmtp002.mac.com> for ietf@ietf.org; Tue, 01 Apr 2014 23:14:22 +0000 (GMT)
Date: Tue, 01 Apr 2014 16:14:19 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, Ted Lemon <mellon@fugue.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
In-reply-to: <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
Message-id: <alpine.OSX.2.01.1404011612360.14186@rabdullah.local>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaGBEKTEMXGx0EGx0YBBIZBBsdEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsYGmJCH2luGEgTGXhzB xkbGBkbHmYTEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGx0QGx4aHxsRCl5ZF2FJZVB FEQpMRhdia2sRCkNaFxsdGQQbGwQbGxoEGxkYEQpCXhcbEQpEWBcZEQpEXhcYEQpESRcbEQpCR RdjWUJrc3JMelNyWxEKQk4XbHBgeUAdYlJpGmIRCkJMF2BJWUZ/eWRYHENeEQpCbBdoRFxTTWt CfUcFTBEKQkAXbk1uaWZieksbaVkRCnBoF2FDUkBgR39DfhlQEQpwaBdoXU9bHxNrYEFTRBEKc GgXaW4aQE5HYxNnRmgRCnBsF2YBEkd9TWdzSUBJEQpwTBdkE3hiUENBXwVASxE=
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-04-01_06:2014-04-01,2014-04-01,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=3 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404010134
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NrpljNG_Ssl6HuuNCxPFEYnPOec
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 23:14:29 -0000

Have you spoken with Ted Lemon about this at all?

On Tue, 1 Apr 2014, Andrew G. Malis wrote:

> As a tea drinker, I'm very happy to see this extension to RFC 2324.
> However, many people drink their tea with lemon, and that doesn't
> really fit into any of the addition-types in section 2.2.1. Another
> addition-type may be required.
> 
> Cheers,
> Andy
> 
> 


From nobody Tue Apr  1 16:38:09 2014
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E801A0011 for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 16:38:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 74KAxx_tZeUV for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 16:38:03 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 868EC1A0028 for <ietf@ietf.org>; Tue,  1 Apr 2014 16:37:56 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1WV8FX-0002GG-Nn; Wed, 02 Apr 2014 00:37:51 +0100
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Elwyn Davies <elwynd@dial.pipex.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
In-Reply-To: <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
Content-Type: text/plain
Date: Wed, 02 Apr 2014 00:37:46 +0100
Message-Id: <1396395466.15324.6860.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/A1GGO-A7fmmC2DONnU9HB00SxX4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 23:38:07 -0000

On Tue, 2014-04-01 at 18:48 -0400, Andrew G. Malis wrote:
> As a tea drinker, I'm very happy to see this extension to RFC 2324.
> However, many people drink their tea with lemon, and that doesn't
> really fit into any of the addition-types in section 2.2.1. Another
> addition-type may be required.
> 
> Cheers,
> Andy

+1

We also need the internationalized version to cater for all those
excellent varieties of China Tea.  A nice drop of pu-erh perhaps?

Tea 'up,
Elwyn

> 
> 
> On Tue, Apr 1, 2014 at 6:00 PM,  <rfc-editor@rfc-editor.org> wrote:
> > A new Request for Comments is now available in online RFC libraries.
> >
> >
> >         RFC 7168
> >
> >         Title:      The Hyper Text Coffee Pot
> >                     Control Protocol for Tea Efflux Appliances
> >                     (HTCPCP-TEA)
> >         Author:     I. Nazar
> >         Status:     Informational
> >         Stream:     Independent
> >         Date:       1 April 2014
> >         Mailbox:    inazar@deviantart.com
> >         Pages:      7
> >         Characters: 14490
> >         Updates:    RFC 2324
> >
> >         I-D Tag:    draft-nazar-htcpcp-tea-00.txt
> >
> >         URL:        http://www.rfc-editor.org/rfc/rfc7168.txt
> >
> > The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification
> > does not allow for the brewing of tea, in all its variety and
> > complexity.  This paper outlines an extension to HTCPCP to allow
> > for pots to provide networked tea-brewing facilities.
> >
> >
> > INFORMATIONAL: This memo provides information for the Internet community.
> > It does not specify an Internet standard of any kind. Distribution of
> > this memo is unlimited.
> >
> > This announcement is sent to the IETF-Announce and rfc-dist lists.
> > To subscribe or unsubscribe, see
> >   http://www.ietf.org/mailman/listinfo/ietf-announce
> >   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
> >
> > For searching the RFC series, see http://www.rfc-editor.org/search
> > For downloading RFCs, see http://www.rfc-editor.org/rfc.html
> >
> > Requests for special distribution should be addressed to either the
> > author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> > specifically noted otherwise on the RFC itself, all RFCs are for
> > unlimited distribution.
> >
> >
> > The RFC Editor Team
> > Association Management Solutions, LLC
> >
> >
> 


From nobody Tue Apr  1 16:51:44 2014
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 844201A002E for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 16:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.231
X-Spam-Level: 
X-Spam-Status: No, score=-1.231 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=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 WcXuqV_NEclO for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 16:51:40 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 2FEB61A002B for <ietf@ietf.org>; Tue,  1 Apr 2014 16:51:39 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost.ecs.soton.ac.uk [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s31NpRfb004585; Wed, 2 Apr 2014 00:51:30 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s31NpRfb004585
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1396396290; bh=fpD1Cm/bIlHFTOWP8OnI+oqXbvk=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=nCwzHcrPpqUcNVPO/MnxwvemLs1wRIfrYc65wOp9jT6qwkKelnPG6Ee+O8xcwOvAc dyHSF+eRCvg3ztP2rVh6MhmJngGVal9Z7FY7+PbLv5rn6nsG4LSDI2ETnkPczxlW6b 1DE7bISH63pkIDIQezELG+Fi6Dlk96oYkwyJ/KFk=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id q310pR0546039926O1 ret-id none; Wed, 02 Apr 2014 00:51:30 +0100
Received: from [192.168.1.108] (host213-123-213-183.in-addr.btopenworld.com [213.123.213.183]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s31No8hw024736 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 2 Apr 2014 00:50:08 +0100
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <1396395466.15324.6860.camel@mightyatom>
Date: Wed, 2 Apr 2014 00:50:07 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|33c7555e392787d4239b395665fe58f2q310pR03tjc|ecs.soton.ac.uk|B96B618C-9DBB-4E44-9D02-A85A44B5ABF0@ecs.soton.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom> <B96B618C-9DBB-4E44-9D02-A85A44B5ABF0@ecs.soton.ac.uk>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1874)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q310pR054603992600; tid=q310pR0546039926O1; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s31NpRfb004585
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9Sv0IK0lkklnnVxi2ZW25iN4fvU
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Apr 2014 23:51:42 -0000

On 2 Apr 2014, at 00:37, Elwyn Davies <elwynd@dial.pipex.com> wrote:

>=20
> On Tue, 2014-04-01 at 18:48 -0400, Andrew G. Malis wrote:
>> As a tea drinker, I'm very happy to see this extension to RFC 2324.
>> However, many people drink their tea with lemon, and that doesn't
>> really fit into any of the addition-types in section 2.2.1. Another
>> addition-type may be required.
>>=20
>> Cheers,
>> Andy
>=20
> +1
>=20
> We also need the internationalized version to cater for all those
> excellent varieties of China Tea.  A nice drop of pu-erh perhaps?

I think this protocol will only run effectively over older, thicker =
Ethernet media, specifically through a 10base2 tea-piece connector.

Tim

>=20
> Tea 'up,
> Elwyn
>=20
>>=20
>>=20
>> On Tue, Apr 1, 2014 at 6:00 PM,  <rfc-editor@rfc-editor.org> wrote:
>>> A new Request for Comments is now available in online RFC libraries.
>>>=20
>>>=20
>>>        RFC 7168
>>>=20
>>>        Title:      The Hyper Text Coffee Pot
>>>                    Control Protocol for Tea Efflux Appliances
>>>                    (HTCPCP-TEA)
>>>        Author:     I. Nazar
>>>        Status:     Informational
>>>        Stream:     Independent
>>>        Date:       1 April 2014
>>>        Mailbox:    inazar@deviantart.com
>>>        Pages:      7
>>>        Characters: 14490
>>>        Updates:    RFC 2324
>>>=20
>>>        I-D Tag:    draft-nazar-htcpcp-tea-00.txt
>>>=20
>>>        URL:        http://www.rfc-editor.org/rfc/rfc7168.txt
>>>=20
>>> The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification
>>> does not allow for the brewing of tea, in all its variety and
>>> complexity.  This paper outlines an extension to HTCPCP to allow
>>> for pots to provide networked tea-brewing facilities.
>>>=20
>>>=20
>>> INFORMATIONAL: This memo provides information for the Internet =
community.
>>> It does not specify an Internet standard of any kind. Distribution =
of
>>> this memo is unlimited.
>>>=20
>>> This announcement is sent to the IETF-Announce and rfc-dist lists.
>>> To subscribe or unsubscribe, see
>>>  http://www.ietf.org/mailman/listinfo/ietf-announce
>>>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>>=20
>>> For searching the RFC series, see http://www.rfc-editor.org/search
>>> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>>>=20
>>> Requests for special distribution should be addressed to either the
>>> author of the RFC in question, or to rfc-editor@rfc-editor.org.  =
Unless
>>> specifically noted otherwise on the RFC itself, all RFCs are for
>>> unlimited distribution.
>>>=20
>>>=20
>>> The RFC Editor Team
>>> Association Management Solutions, LLC
>>>=20
>>>=20
>>=20
>=20


From nobody Tue Apr  1 17:22:37 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FC091A0035 for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 17:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 0CweWMwQA6EB for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 17:22:33 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 87B621A001C for <ietf@ietf.org>; Tue,  1 Apr 2014 17:22:33 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WV8wk-0005g6-TJ for ietf@ietf.org; Wed, 02 Apr 2014 00:22:27 +0000
Date: Wed, 02 Apr 2014 09:22:25 +0900
Message-ID: <m2a9c437i6.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: Re: RFC 7169 on The NSA (No Secrecy Afforded) Certificate Extension
In-Reply-To: <20140401220128.3CD897FC3A9@rfc-editor.org>
References: <20140401220128.3CD897FC3A9@rfc-editor.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-2y_wsTU2Dbi6V_UQMJq-ARZoNM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 00:22:35 -0000

>         RFC 7169
>         Title:      The NSA (No Secrecy Afforded) 
>                     Certificate Extension 
>         URL:        http://www.rfc-editor.org/rfc/rfc7169.txt

i do not understand why this extension is needed.  the 5eyes have all
your keys.  the flag should always be on.  is the real intent that, when
the extension/flag is not on in a received certificate, then you know it
is bogus?

randy


From nobody Tue Apr  1 18:46:10 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13A261A005F for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 18:46:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.137
X-Spam-Level: 
X-Spam-Status: No, score=-1.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 En5xaRzhVNU6 for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 18:46:07 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4B95F1A0059 for <ietf@ietf.org>; Tue,  1 Apr 2014 18:46:07 -0700 (PDT)
Received: (qmail 36039 invoked from network); 2 Apr 2014 01:46:02 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 2 Apr 2014 01:46:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=533b6bda.xn--yuvv84g.k1404; i=johnl@user.iecc.com; bh=vnjnZb94UIHeAcQWBRVS/iG4plbmxfOfMWBsdXUH//4=; b=BaT8iPClSaQdob9AQajY66/3leP1zUpCgrmMUMbCeRZkGgmmuIZWSCEH79x3CtMy89HD+FXX6B1ij5WSoSR8xDnAZeG5XuVyBed9Vrh0huLPKR8Xa2FnBsYSeKRRloPWnFRa0SA+PAMqBcdk5NEf49weOzJLdLAzWzxVvrmvf8cD+imhXYwBoTTuXTl9Zi9+B/umrcMPPEy/2vuBy9wJu3yfhwQJ0GiaSgZwUlbCoQyUwLKzAIsePyoYRDhU1KmE
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=533b6bda.xn--yuvv84g.k1404; bh=vnjnZb94UIHeAcQWBRVS/iG4plbmxfOfMWBsdXUH//4=;  b=TQiO+AU9l9Rh+rFIeQwzj2HEhgUJwjGcSK00eIlrYVsj/6DvU7ZWtSJiSLqyUhpBcpMAlrXc/CY+vrjw2E2olLYEPZ2O7iMmpTzeROgtKiaZXiWj5QcoZdVDCqtZ6cAkr5Kd+1JxnUOUPG3jYlpbl+pMAL1+5yy8eL9BOIYkRs1f28iUqNeXMRcwHGT8prEfGzf5ZShpzJO1rSwQ0fTMxIrM53Pl2lK1Ph9PIYo3G8JH7taIfrGeBg3uOK5rCp4Q
Date: 2 Apr 2014 01:45:40 -0000
Message-ID: <20140402014540.22971.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
In-Reply-To: <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JTkRIDlc7ugozHjBP_nCQ34kP5o
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 01:46:09 -0000

In section 2.1, shouldn't POST be POSTUM?

R's,
John


From nobody Tue Apr  1 19:53:09 2014
Return-Path: <rgd.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFD0D1A00AA for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 19:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 YA4ph1aMt6ai for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 19:52:59 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id A82E91A00B4 for <ietf@ietf.org>; Tue,  1 Apr 2014 19:52:59 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id rd3so10794633pab.39 for <ietf@ietf.org>; Tue, 01 Apr 2014 19:52:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:from:subject:date:to; bh=lZYgzEITnt+ClcUVv4bbfSFv4cZvg+Dq13q/8qb0JCw=; b=JiFo7hfVSvE+Jx2ms7yUk6cbykrOPqKUKEbetFqkK3uBv0LFVOjp9Ot03q/VoSy7SS pN0HxYTozr17TH0TgIRWGJ1XEgCHxBzBZDStspYeBf57K5GtmEB9ujghQO7ZLhAmuMgf 4Nr13ebvWskezfyz5iQYPCl7yzsEdM4pIt2+J8xhYmcK7+jxKKVga/G1IFe9vVDBa0Wn QOVZdRhn1pBglmGzsmW7H7Fs03Z29oMG+2tYrOa3aRq2UYiRyDXfJJEqnbcuZdy6+kuj ymsvb0Djls2GcBpIFTdgv0VJ7gOBcxhshK63L4Btk9fdsqkKbziq8g8GqvTu8Pw6OuyC XXOw==
X-Received: by 10.66.141.144 with SMTP id ro16mr13656560pab.131.1396407176060;  Tue, 01 Apr 2014 19:52:56 -0700 (PDT)
Received: from [10.0.1.7] (cpe-142-136-145-221.socal.res.rr.com. [142.136.145.221]) by mx.google.com with ESMTPSA id iu10sm869542pbd.71.2014.04.01.19.52.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 01 Apr 2014 19:52:54 -0700 (PDT)
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
In-Reply-To: <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com>
X-Mailer: iPad Mail (11B651)
From: "Rgd.ietf" <rgd.ietf@gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Date: Tue, 1 Apr 2014 19:52:53 -0700
To: "Andrew G. Malis" <agmalis@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TMljSg6jabFVGtOD4SlP1tCV7p0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 02:53:06 -0000

Review comments:

Section 2.2.1 There are also additional modes of sugar than cane sugar.  It s=
hould support sugar beet sugar. So section 2.2.1 sugar-beet and sugar-cane s=
hould be included in the options.

Tea has state(s) - it is either brewed or unbrewed , as well as cold or hot.=
 There needs to be an optional state monitor reporting {brewed | unbrewed } a=
nd { hot | cold }. =20

 I'm undecided if there should be a  { sat-too-long-and-is-cold | fresh } me=
ssage. Perhaps a wider review would be helpful.

Finally is there any requirement for a parameter to specify ice?

-rgd

> On Apr 1, 2014, at 3:49 PM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>=20
> As a tea drinker, I'm very happy to see this extension to RFC 2324.
> However, many people drink their tea with lemon, and that doesn't
> really fit into any of the addition-types in section 2.2.1. Another
> addition-type may be required.
>=20
> Cheers,
> Andy
>=20
>=20
>> On Tue, Apr 1, 2014 at 6:00 PM,  <rfc-editor@rfc-editor.org> wrote:
>> A new Request for Comments is now available in online RFC libraries.
>>=20
>>=20
>>        RFC 7168
>>=20
>>        Title:      The Hyper Text Coffee Pot
>>                    Control Protocol for Tea Efflux Appliances
>>                    (HTCPCP-TEA)
>>        Author:     I. Nazar
>>        Status:     Informational
>>        Stream:     Independent
>>        Date:       1 April 2014
>>        Mailbox:    inazar@deviantart.com
>>        Pages:      7
>>        Characters: 14490
>>        Updates:    RFC 2324
>>=20
>>        I-D Tag:    draft-nazar-htcpcp-tea-00.txt
>>=20
>>        URL:        http://www.rfc-editor.org/rfc/rfc7168.txt
>>=20
>> The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification
>> does not allow for the brewing of tea, in all its variety and
>> complexity.  This paper outlines an extension to HTCPCP to allow
>> for pots to provide networked tea-brewing facilities.
>>=20
>>=20
>> INFORMATIONAL: This memo provides information for the Internet community.=

>> It does not specify an Internet standard of any kind. Distribution of
>> this memo is unlimited.
>>=20
>> This announcement is sent to the IETF-Announce and rfc-dist lists.
>> To subscribe or unsubscribe, see
>>  http://www.ietf.org/mailman/listinfo/ietf-announce
>>  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>=20
>> For searching the RFC series, see http://www.rfc-editor.org/search
>> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>>=20
>> Requests for special distribution should be addressed to either the
>> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
>> specifically noted otherwise on the RFC itself, all RFCs are for
>> unlimited distribution.
>>=20
>>=20
>> The RFC Editor Team
>> Association Management Solutions, LLC
>=20


From nobody Tue Apr  1 20:16:45 2014
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21D671A00BC for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 20:16:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 dNKOHGOZPNSv for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 20:16:39 -0700 (PDT)
Received: from st11p02mm-asmtp002.mac.com (st11p02mm-asmtpout002.mac.com [17.172.220.237]) by ietfa.amsl.com (Postfix) with ESMTP id F2F481A00B6 for <ietf@ietf.org>; Tue,  1 Apr 2014 20:16:37 -0700 (PDT)
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_hKby9VZSp/exYbW+O4rrXw)"
Received: from [10.1.10.15] (173-11-110-134-SFBA.hfc.comcastbusiness.net [173.11.110.134]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N3D00JZSVRJRE80@st11p02mm-asmtp002.mac.com> for ietf@ietf.org; Wed, 02 Apr 2014 03:16:34 +0000 (GMT)
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Ole Jacobsen <olejacobsen@me.com>
X-Mailer: iPhone Mail (11D167)
In-reply-to: <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com>
Date: Tue, 01 Apr 2014 20:16:33 -0700
Message-id: <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com>
To: "Rgd.ietf" <rgd.ietf@gmail.com>
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaEhEKTEMXGx0EGx0YBBIZBBsdEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsYGmJCH2lmHh9AGXhzB xkYGhkbHHIfEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGx0QGx4aHxsRCl5ZF2FJeX1 ZEQpMRhdsa2sRCkNaFxsdGQQbGwQbGxoEGxkeEQpEWBceEQpESRcYEQpCRRdjWUJrc3JMelNyW xEKQk4XbHBgeUAdYlJpGmIRCkJMF2BJWUZ/eWRYHENeEQpCbBdoRFxTTWtCfUcFTBEKQkAXbk1 uaWZieksbaVkRCnBnF3oeaWQTT355YkN/EQpwaBdhbkJiGEgBYV5vSREKcGgXbl9IQl1ZHntjH h0RCnBoF2V7Y0ZGRxlEcGZsEQpwaBdibkFBb0YeZwV+fREKcGgXYh8aeXt9E2RLT2wRCnBnF2M fbB1vZEB7G2dLEQpwfxdieGlfGm18G1ITbhEKcF8XZkZtWklvckNlWx8RCnB/F2t+eEljbE5/W 054EQpwXxdoSX5sU2VQYGx8RxEKcF8XZW5kbx5bek5sGXARCnBfF2RCR1xlW3p+Ek5FEQpwXxd jRmdzb3Mde2JFUBEKcGwXZgESR31NZ3NJQEkRCnBMF2lDf08YRGJAWAFSEQ==
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-04-01_07:2014-04-01,2014-04-01,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=2 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404010173
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/K-ColUDgIu5INmXANl_S28X3WYQ
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 03:16:42 -0000

--Boundary_(ID_hKby9VZSp/exYbW+O4rrXw)
Content-type: text/plain; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

As any Brit will tell you: ice has absolutely NOTHING to do with tea, so it would be out of scope.

Sat-too-long-and-is-still-hot is, if I recall, known as "stewed" and anyone responsible faces possible deportation from the UK. A very serious matter indeed, almost as serious as refusing to obey the rules of a queue.

Ole

Ole J. Jacobsen
Editor & Publisher
Cell: +1 415 370-4628
docomo: (090) 3337 9311
UK Orange: +44 780 5977 889

Sent from my iPhone

> On 1 Apr 2014, at 19:52, "Rgd.ietf" <rgd.ietf@gmail.com> wrote:
> 
> Review comments:
> 
> Section 2.2.1 There are also additional modes of sugar than cane sugar.  It should support sugar beet sugar. So section 2.2.1 sugar-beet and sugar-cane should be included in the options.
> 
> Tea has state(s) - it is either brewed or unbrewed , as well as cold or hot. There needs to be an optional state monitor reporting {brewed | unbrewed } and { hot | cold }.  
> 
> I'm undecided if there should be a  { sat-too-long-and-is-cold | fresh } message. Perhaps a wider review would be helpful.
> 
> Finally is there any requirement for a parameter to specify ice?
> 
> -rgd
> 
>> On Apr 1, 2014, at 3:49 PM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>> 
>> As a tea drinker, I'm very happy to see this extension to RFC 2324.
>> However, many people drink their tea with lemon, and that doesn't
>> really fit into any of the addition-types in section 2.2.1. Another
>> addition-type may be required.
>> 
>> Cheers,
>> Andy
>> 
>> 
>>> On Tue, Apr 1, 2014 at 6:00 PM,  <rfc-editor@rfc-editor.org> wrote:
>>> A new Request for Comments is now available in online RFC libraries.
>>> 
>>> 
>>>       RFC 7168
>>> 
>>>       Title:      The Hyper Text Coffee Pot
>>>                   Control Protocol for Tea Efflux Appliances
>>>                   (HTCPCP-TEA)
>>>       Author:     I. Nazar
>>>       Status:     Informational
>>>       Stream:     Independent
>>>       Date:       1 April 2014
>>>       Mailbox:    inazar@deviantart.com
>>>       Pages:      7
>>>       Characters: 14490
>>>       Updates:    RFC 2324
>>> 
>>>       I-D Tag:    draft-nazar-htcpcp-tea-00.txt
>>> 
>>>       URL:        http://www.rfc-editor.org/rfc/rfc7168.txt
>>> 
>>> The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification
>>> does not allow for the brewing of tea, in all its variety and
>>> complexity.  This paper outlines an extension to HTCPCP to allow
>>> for pots to provide networked tea-brewing facilities.
>>> 
>>> 
>>> INFORMATIONAL: This memo provides information for the Internet community.
>>> It does not specify an Internet standard of any kind. Distribution of
>>> this memo is unlimited.
>>> 
>>> This announcement is sent to the IETF-Announce and rfc-dist lists.
>>> To subscribe or unsubscribe, see
>>> http://www.ietf.org/mailman/listinfo/ietf-announce
>>> http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>>> 
>>> For searching the RFC series, see http://www.rfc-editor.org/search
>>> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>>> 
>>> Requests for special distribution should be addressed to either the
>>> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
>>> specifically noted otherwise on the RFC itself, all RFCs are for
>>> unlimited distribution.
>>> 
>>> 
>>> The RFC Editor Team
>>> Association Management Solutions, LLC
> 

--Boundary_(ID_hKby9VZSp/exYbW+O4rrXw)
Content-type: text/html; CHARSET=US-ASCII
Content-transfer-encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div>As any Brit will tell you: ice has abs=
olutely NOTHING to do with tea, so it would be out of scope.</div><div><br><=
/div><div>Sat-too-long-and-is-still-hot is, if I recall, known as "stewed" a=
nd anyone responsible faces possible deportation from the UK. A very serious=
 matter indeed, almost as serious as refusing to obey the rules of a queue.<=
/div><div><br></div><div>Ole<br><br><div><div style=3D"font-family: UICTFont=
TextStyleBody; font-size: 18px; -webkit-text-size-adjust: auto;">Ole J. Jaco=
bsen</div><div style=3D"font-family: UICTFontTextStyleBody; font-size: 18px;=
 -webkit-text-size-adjust: auto;">Editor &amp; Publisher</div><div style=3D"=
font-family: UICTFontTextStyleBody; font-size: 18px; -webkit-text-size-adjus=
t: auto;">Cell: +1 415 370-4628</div><div style=3D"font-family: UICTFontText=
StyleBody; font-size: 18px; -webkit-text-size-adjust: auto;">docomo: (090) 3=
337 9311</div><div style=3D"font-family: UICTFontTextStyleBody; font-size: 1=
8px; -webkit-text-size-adjust: auto;">UK Orange: +44 780 5977 889</div></div=
><div><br></div>Sent from my iPhone</div><div><br>On 1 Apr 2014, at 19:52, "=
Rgd.ietf" &lt;<a href=3D"mailto:rgd.ietf@gmail.com">rgd.ietf@gmail.com</a>&g=
t; wrote:<br><br></div><blockquote type=3D"cite"><div><span>Review comments:=
</span><br><span></span><br><span>Section 2.2.1 There are also additional mo=
des of sugar than cane sugar. &nbsp;It should support sugar beet sugar. So s=
ection 2.2.1 sugar-beet and sugar-cane should be included in the options.</s=
pan><br><span></span><br><span>Tea has state(s) - it is either brewed or unb=
rewed , as well as cold or hot. There needs to be an optional state monitor r=
eporting {brewed | unbrewed } and { hot | cold }. &nbsp;</span><br><span></s=
pan><br><span> I'm undecided if there should be a &nbsp;{ sat-too-long-and-i=
s-cold | fresh } message. Perhaps a wider review would be helpful.</span><br=
><span></span><br><span>Finally is there any requirement for a parameter to s=
pecify ice?</span><br><span></span><br><span>-rgd</span><br><span></span><br=
><blockquote type=3D"cite"><span>On Apr 1, 2014, at 3:49 PM, "Andrew G. Mali=
s" &lt;<a href=3D"mailto:agmalis@gmail.com">agmalis@gmail.com</a>&gt; wrote:=
</span><br></blockquote><blockquote type=3D"cite"><span></span><br></blockqu=
ote><blockquote type=3D"cite"><span>As a tea drinker, I'm very happy to see t=
his extension to RFC 2324.</span><br></blockquote><blockquote type=3D"cite">=
<span>However, many people drink their tea with lemon, and that doesn't</spa=
n><br></blockquote><blockquote type=3D"cite"><span>really fit into any of th=
e addition-types in section 2.2.1. Another</span><br></blockquote><blockquot=
e type=3D"cite"><span>addition-type may be required.</span><br></blockquote>=
<blockquote type=3D"cite"><span></span><br></blockquote><blockquote type=3D"=
cite"><span>Cheers,</span><br></blockquote><blockquote type=3D"cite"><span>A=
ndy</span><br></blockquote><blockquote type=3D"cite"><span></span><br></bloc=
kquote><blockquote type=3D"cite"><span></span><br></blockquote><blockquote t=
ype=3D"cite"><blockquote type=3D"cite"><span>On Tue, Apr 1, 2014 at 6:00 PM,=
 &nbsp;&lt;<a href=3D"mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-edito=
r.org</a>&gt; wrote:</span><br></blockquote></blockquote><blockquote type=3D=
"cite"><blockquote type=3D"cite"><span>A new Request for Comments is now ava=
ilable in online RFC libraries.</span><br></blockquote></blockquote><blockqu=
ote type=3D"cite"><blockquote type=3D"cite"><span></span><br></blockquote></=
blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></span>=
<br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"=
cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;RFC 7168</span><br></blockq=
uote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>=
</span><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote t=
ype=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Title: &nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;The Hyper Text Coffee Pot</span><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite"><span> &nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;Control Protocol for Tea Efflux Appliances</span><br></blo=
ckquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><sp=
an> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(HTCPCP-TEA)</span><br></blockquote></bl=
ockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span> &nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;Author: &nbsp;&nbsp;&nbsp;&nbsp;I. Nazar</span><=
br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"c=
ite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Status: &nbsp;&nbsp;&nbsp;&n=
bsp;Informational</span><br></blockquote></blockquote><blockquote type=3D"ci=
te"><blockquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Str=
eam: &nbsp;&nbsp;&nbsp;&nbsp;Independent</span><br></blockquote></blockquote=
><blockquote type=3D"cite"><blockquote type=3D"cite"><span> &nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;&nbsp;Date: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1 April 2014</=
span><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote typ=
e=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Mailbox: &nbsp;&nbsp;&=
nbsp;<a href=3D"mailto:inazar@deviantart.com">inazar@deviantart.com</a></spa=
n><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D=
"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Pages: &nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;7</span><br></blockquote></blockquote><blockquote type=3D"cite"><=
blockquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Characte=
rs: 14490</span><br></blockquote></blockquote><blockquote type=3D"cite"><blo=
ckquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Updates: &n=
bsp;&nbsp;&nbsp;RFC 2324</span><br></blockquote></blockquote><blockquote typ=
e=3D"cite"><blockquote type=3D"cite"><span></span><br></blockquote></blockqu=
ote><blockquote type=3D"cite"><blockquote type=3D"cite"><span> &nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;I-D Tag: &nbsp;&nbsp;&nbsp;draft-nazar-htcpcp-tea-00.=
txt</span><br></blockquote></blockquote><blockquote type=3D"cite"><blockquot=
e type=3D"cite"><span></span><br></blockquote></blockquote><blockquote type=3D=
"cite"><blockquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
URL: &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<a href=3D"http://www.rfc-edi=
tor.org/rfc/rfc7168.txt">http://www.rfc-editor.org/rfc/rfc7168.txt</a></span=
><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D=
"cite"><span></span><br></blockquote></blockquote><blockquote type=3D"cite">=
<blockquote type=3D"cite"><span>The Hyper Text Coffee Pot Control Protocol (=
HTCPCP) specification</span><br></blockquote></blockquote><blockquote type=3D=
"cite"><blockquote type=3D"cite"><span>does not allow for the brewing of tea=
, in all its variety and</span><br></blockquote></blockquote><blockquote typ=
e=3D"cite"><blockquote type=3D"cite"><span>complexity. &nbsp;This paper outl=
ines an extension to HTCPCP to allow</span><br></blockquote></blockquote><bl=
ockquote type=3D"cite"><blockquote type=3D"cite"><span>for pots to provide n=
etworked tea-brewing facilities.</span><br></blockquote></blockquote><blockq=
uote type=3D"cite"><blockquote type=3D"cite"><span></span><br></blockquote><=
/blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></span=
><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D=
"cite"><span>INFORMATIONAL: This memo provides information for the Internet c=
ommunity.</span><br></blockquote></blockquote><blockquote type=3D"cite"><blo=
ckquote type=3D"cite"><span>It does not specify an Internet standard of any k=
ind. Distribution of</span><br></blockquote></blockquote><blockquote type=3D=
"cite"><blockquote type=3D"cite"><span>this memo is unlimited.</span><br></b=
lockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><=
span></span><br></blockquote></blockquote><blockquote type=3D"cite"><blockqu=
ote type=3D"cite"><span>This announcement is sent to the IETF-Announce and r=
fc-dist lists.</span><br></blockquote></blockquote><blockquote type=3D"cite"=
><blockquote type=3D"cite"><span>To subscribe or unsubscribe, see</span><br>=
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite=
"><span> <a href=3D"http://www.ietf.org/mailman/listinfo/ietf-announce">http=
://www.ietf.org/mailman/listinfo/ietf-announce</a></span><br></blockquote></=
blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span> <a hre=
f=3D"http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist">http://mailman=
.rfc-editor.org/mailman/listinfo/rfc-dist</a></span><br></blockquote></block=
quote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></span><br><=
/blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"=
><span>For searching the RFC series, see <a href=3D"http://www.rfc-editor.or=
g/search">http://www.rfc-editor.org/search</a></span><br></blockquote></bloc=
kquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>For downloa=
ding RFCs, see <a href=3D"http://www.rfc-editor.org/rfc.html">http://www.rfc=
-editor.org/rfc.html</a></span><br></blockquote></blockquote><blockquote typ=
e=3D"cite"><blockquote type=3D"cite"><span></span><br></blockquote></blockqu=
ote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>Requests for s=
pecial distribution should be addressed to either the</span><br></blockquote=
></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>auth=
or of the RFC in question, or to <a href=3D"mailto:rfc-editor@rfc-editor.org=
">rfc-editor@rfc-editor.org</a>. &nbsp;Unless</span><br></blockquote></block=
quote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>specifically=
 noted otherwise on the RFC itself, all RFCs are for</span><br></blockquote>=
</blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>unlim=
ited distribution.</span><br></blockquote></blockquote><blockquote type=3D"c=
ite"><blockquote type=3D"cite"><span></span><br></blockquote></blockquote><b=
lockquote type=3D"cite"><blockquote type=3D"cite"><span></span><br></blockqu=
ote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>T=
he RFC Editor Team</span><br></blockquote></blockquote><blockquote type=3D"c=
ite"><blockquote type=3D"cite"><span>Association Management Solutions, LLC</=
span><br></blockquote></blockquote><blockquote type=3D"cite"><span></span><b=
r></blockquote><span></span><br></div></blockquote></body></html>=

--Boundary_(ID_hKby9VZSp/exYbW+O4rrXw)--


From nobody Wed Apr  2 00:07:37 2014
Return-Path: <chaitanyabd@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBB531A014D for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 00:07:32 -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, SPF_PASS=-0.001] autolearn=ham
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 kFPw3Ff12i-7 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 00:07:28 -0700 (PDT)
Received: from mail-vc0-x235.google.com (mail-vc0-x235.google.com [IPv6:2607:f8b0:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 3558C1A0133 for <ietf@ietf.org>; Wed,  2 Apr 2014 00:07:27 -0700 (PDT)
Received: by mail-vc0-f181.google.com with SMTP id id10so11024349vcb.40 for <ietf@ietf.org>; Wed, 02 Apr 2014 00:07:23 -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:content-type; bh=GuaOMZiDrLDVZAFAO/rgEO9jzeE4r7yhZHhxYenTYuU=; b=bUJ74SA5QYjIHbuzCexjkVdybH3L0x2YAsEUdTNgMDqsK7TTwTE+YLMSyH+z5hYQ3U iNm857VZATShiOdtmKp5LVKYCTyhX/49JkGQl7b/meDhRvCyCZs3MgP0/IekJzPQuGfA qaXmWEqoWqV8KN4Uybgn8LMKdKdq88KJof+OVpH/eS4ILyee7bVzMTHcsFY86utjiIed hLPArnJP9TKL2A8QsT+IG9hcJuEBwKWN7Osnck8r4SVGOLita48S1FxxNaJWvEg0p5T9 PY0rRG81RutUqFef97+UqZG1/pDxyhIhKQLasBCPSuBcYXjv4d8zVtJS85HQj4dr0u9y QKhQ==
MIME-Version: 1.0
X-Received: by 10.52.147.238 with SMTP id tn14mr6443558vdb.23.1396422443109; Wed, 02 Apr 2014 00:07:23 -0700 (PDT)
Received: by 10.221.34.13 with HTTP; Wed, 2 Apr 2014 00:07:23 -0700 (PDT)
In-Reply-To: <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>
Date: Wed, 2 Apr 2014 12:37:23 +0530
Message-ID: <CAEP5zKSOcSgBLGOk4xGspvaaF8=FXqcXpt-kOX2r-1Z1HA4kVg@mail.gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Chaitanya Dhareshwar <chaitanyabd@gmail.com>
To: Ole Jacobsen <olejacobsen@me.com>
Content-Type: multipart/alternative; boundary=bcaec51a7128ad929904f609efd2
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rmKUdJxvrXhtAvz_MuRECpg_uNY
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 07:07:33 -0000

--bcaec51a7128ad929904f609efd2
Content-Type: text/plain; charset=ISO-8859-1

I would beg to differ, I love my Iced Tea (ref:
http://en.wikipedia.org/wiki/Iced_tea)

Further as the Internet Engineering Tea Force we must ensure all
possibilities are covered... Even if its not common within a region/culture
doesn't mean its not used elsewhere.

*Chaitanya Dhareshwar*

Linkedin <http://in.linkedin.com/in/chaitanyabd> | Blog <http://cbd.vcio.in> |
Skype: chaitanyabd
Mobile: +91.9820760253


On Wed, Apr 2, 2014 at 8:46 AM, Ole Jacobsen <olejacobsen@me.com> wrote:

> As any Brit will tell you: ice has absolutely NOTHING to do with tea, so
> it would be out of scope.
>
> Sat-too-long-and-is-still-hot is, if I recall, known as "stewed" and
> anyone responsible faces possible deportation from the UK. A very serious
> matter indeed, almost as serious as refusing to obey the rules of a queue.
>
> Ole
>
> Ole J. Jacobsen
> Editor & Publisher
> Cell: +1 415 370-4628
> docomo: (090) 3337 9311
> UK Orange: +44 780 5977 889
>
> Sent from my iPhone
>
> On 1 Apr 2014, at 19:52, "Rgd.ietf" <rgd.ietf@gmail.com> wrote:
>
> Review comments:
>
> Section 2.2.1 There are also additional modes of sugar than cane sugar.
>  It should support sugar beet sugar. So section 2.2.1 sugar-beet and
> sugar-cane should be included in the options.
>
> Tea has state(s) - it is either brewed or unbrewed , as well as cold or
> hot. There needs to be an optional state monitor reporting {brewed |
> unbrewed } and { hot | cold }.
>
> I'm undecided if there should be a  { sat-too-long-and-is-cold | fresh }
> message. Perhaps a wider review would be helpful.
>
> Finally is there any requirement for a parameter to specify ice?
>
> -rgd
>
> On Apr 1, 2014, at 3:49 PM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>
>
> As a tea drinker, I'm very happy to see this extension to RFC 2324.
>
> However, many people drink their tea with lemon, and that doesn't
>
> really fit into any of the addition-types in section 2.2.1. Another
>
> addition-type may be required.
>
>
> Cheers,
>
> Andy
>
>
>
> On Tue, Apr 1, 2014 at 6:00 PM,  <rfc-editor@rfc-editor.org> wrote:
>
> A new Request for Comments is now available in online RFC libraries.
>
>
>
>       RFC 7168
>
>
>       Title:      The Hyper Text Coffee Pot
>
>                   Control Protocol for Tea Efflux Appliances
>
>                   (HTCPCP-TEA)
>
>       Author:     I. Nazar
>
>       Status:     Informational
>
>       Stream:     Independent
>
>       Date:       1 April 2014
>
>       Mailbox:    inazar@deviantart.com
>
>       Pages:      7
>
>       Characters: 14490
>
>       Updates:    RFC 2324
>
>
>       I-D Tag:    draft-nazar-htcpcp-tea-00.txt
>
>
>       URL:        http://www.rfc-editor.org/rfc/rfc7168.txt
>
>
> The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification
>
> does not allow for the brewing of tea, in all its variety and
>
> complexity.  This paper outlines an extension to HTCPCP to allow
>
> for pots to provide networked tea-brewing facilities.
>
>
>
> INFORMATIONAL: This memo provides information for the Internet community.
>
> It does not specify an Internet standard of any kind. Distribution of
>
> this memo is unlimited.
>
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
>
> To subscribe or unsubscribe, see
>
> http://www.ietf.org/mailman/listinfo/ietf-announce
>
> http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
>
> For searching the RFC series, see http://www.rfc-editor.org/search
>
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>
>
> Requests for special distribution should be addressed to either the
>
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
>
> specifically noted otherwise on the RFC itself, all RFCs are for
>
> unlimited distribution.
>
>
>
> The RFC Editor Team
>
> Association Management Solutions, LLC
>
>
>
>

--bcaec51a7128ad929904f609efd2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif">I would beg to differ, I love my Iced Tea (ref:=A0<a href=3D"htt=
p://en.wikipedia.org/wiki/Iced_tea" style=3D"font-family:arial">http://en.w=
ikipedia.org/wiki/Iced_tea</a>)</div>
<div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif"><br></=
div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-serif">Fu=
rther as the Internet Engineering Tea Force we must ensure all possibilitie=
s are covered... Even if its not common within a region/culture doesn&#39;t=
 mean its not used elsewhere.=A0</div>
<div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr"><div><fo=
nt face=3D"tahoma,sans-serif"><strong><font color=3D"#3d85c6">Chaitanya Dha=
reshwar</font></strong></font></div><div><strong><font color=3D"#3d85c6" fa=
ce=3D"Tahoma"></font></strong><font face=3D"tahoma,sans-serif"><br>
<a href=3D"http://in.linkedin.com/in/chaitanyabd" target=3D"_blank"><font c=
olor=3D"#3d85c6">Linkedin</font></a></font><font face=3D"tahoma,sans-serif"=
> | </font><a href=3D"http://cbd.vcio.in" target=3D"_blank"><font color=3D"=
#3d85c6">Blog</font></a><font> <font face=3D"tahoma,sans-serif">| </font><f=
ont face=3D"tahoma,sans-serif">Skype: <font color=3D"#3d85c6">chaitanyabd</=
font></font></font></div>
<div><font face=3D"Tahoma"><font>Mobile: <font color=3D"#3d85c6">+91.982076=
0253</font></font></font></div></div></div>
<br><br><div class=3D"gmail_quote">On Wed, Apr 2, 2014 at 8:46 AM, Ole Jaco=
bsen <span dir=3D"ltr">&lt;<a href=3D"mailto:olejacobsen@me.com" target=3D"=
_blank">olejacobsen@me.com</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex">
<div dir=3D"auto"><div>As any Brit will tell you: ice has absolutely NOTHIN=
G to do with tea, so it would be out of scope.</div><div><br></div><div>Sat=
-too-long-and-is-still-hot is, if I recall, known as &quot;stewed&quot; and=
 anyone responsible faces possible deportation from the UK. A very serious =
matter indeed, almost as serious as refusing to obey the rules of a queue.<=
/div>
<div><br></div><div>Ole<br><br><div><div style=3D"font-family:UICTFontTextS=
tyleBody;font-size:18px">Ole J. Jacobsen</div><div style=3D"font-family:UIC=
TFontTextStyleBody;font-size:18px">Editor &amp; Publisher</div><div style=
=3D"font-family:UICTFontTextStyleBody;font-size:18px">
Cell: +1 415 370-4628</div><div style=3D"font-family:UICTFontTextStyleBody;=
font-size:18px">docomo: (090) 3337 9311</div><div style=3D"font-family:UICT=
FontTextStyleBody;font-size:18px">UK Orange: +44 780 5977 889</div></div><d=
iv>
<br></div>Sent from my iPhone</div><div><div class=3D"h5"><div><br>On 1 Apr=
 2014, at 19:52, &quot;Rgd.ietf&quot; &lt;<a href=3D"mailto:rgd.ietf@gmail.=
com" target=3D"_blank">rgd.ietf@gmail.com</a>&gt; wrote:<br><br></div><bloc=
kquote type=3D"cite">
<div><span>Review comments:</span><br><span></span><br><span>Section 2.2.1 =
There are also additional modes of sugar than cane sugar. =A0It should supp=
ort sugar beet sugar. So section 2.2.1 sugar-beet and sugar-cane should be =
included in the options.</span><br>
<span></span><br><span>Tea has state(s) - it is either brewed or unbrewed ,=
 as well as cold or hot. There needs to be an optional state monitor report=
ing {brewed | unbrewed } and { hot | cold }. =A0</span><br><span></span><br=
>
<span> I&#39;m undecided if there should be a =A0{ sat-too-long-and-is-cold=
 | fresh } message. Perhaps a wider review would be helpful.</span><br><spa=
n></span><br><span>Finally is there any requirement for a parameter to spec=
ify ice?</span><br>
<span></span><br><span>-rgd</span><br><span></span><br><blockquote type=3D"=
cite"><span>On Apr 1, 2014, at 3:49 PM, &quot;Andrew G. Malis&quot; &lt;<a =
href=3D"mailto:agmalis@gmail.com" target=3D"_blank">agmalis@gmail.com</a>&g=
t; wrote:</span><br>
</blockquote><blockquote type=3D"cite"><span></span><br></blockquote><block=
quote type=3D"cite"><span>As a tea drinker, I&#39;m very happy to see this =
extension to RFC 2324.</span><br></blockquote><blockquote type=3D"cite"><sp=
an>However, many people drink their tea with lemon, and that doesn&#39;t</s=
pan><br>
</blockquote><blockquote type=3D"cite"><span>really fit into any of the add=
ition-types in section 2.2.1. Another</span><br></blockquote><blockquote ty=
pe=3D"cite"><span>addition-type may be required.</span><br></blockquote><bl=
ockquote type=3D"cite">
<span></span><br></blockquote><blockquote type=3D"cite"><span>Cheers,</span=
><br></blockquote><blockquote type=3D"cite"><span>Andy</span><br></blockquo=
te><blockquote type=3D"cite"><span></span><br></blockquote><blockquote type=
=3D"cite">
<span></span><br></blockquote><blockquote type=3D"cite"><blockquote type=3D=
"cite"><span>On Tue, Apr 1, 2014 at 6:00 PM, =A0&lt;<a href=3D"mailto:rfc-e=
ditor@rfc-editor.org" target=3D"_blank">rfc-editor@rfc-editor.org</a>&gt; w=
rote:</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span>A new Request for Comments is now available in online RFC librarie=
s.</span><br></blockquote></blockquote><blockquote type=3D"cite"><blockquot=
e type=3D"cite">
<span></span><br></blockquote></blockquote><blockquote type=3D"cite"><block=
quote type=3D"cite"><span></span><br></blockquote></blockquote><blockquote =
type=3D"cite"><blockquote type=3D"cite"><span> =A0=A0=A0=A0=A0=A0RFC 7168</=
span><br></blockquote>
</blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></sp=
an><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=
=3D"cite"><span> =A0=A0=A0=A0=A0=A0Title: =A0=A0=A0=A0=A0The Hyper Text Cof=
fee Pot</span><br></blockquote>
</blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span> =A0=
=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0Control Protocol for Tea=
 Efflux Appliances</span><br></blockquote></blockquote><blockquote type=3D"=
cite"><blockquote type=3D"cite"><span> =A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0=A0=A0=A0(HTCPCP-TEA)</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span> =A0=A0=A0=A0=A0=A0Author: =A0=A0=A0=A0I. Nazar</span><br></blockq=
uote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span=
> =A0=A0=A0=A0=A0=A0Status: =A0=A0=A0=A0Informational</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span> =A0=A0=A0=A0=A0=A0Stream: =A0=A0=A0=A0Independent</span><br></blo=
ckquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><s=
pan> =A0=A0=A0=A0=A0=A0Date: =A0=A0=A0=A0=A0=A01 April 2014</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span> =A0=A0=A0=A0=A0=A0Mailbox: =A0=A0=A0<a href=3D"mailto:inazar@devi=
antart.com" target=3D"_blank">inazar@deviantart.com</a></span><br></blockqu=
ote></blockquote><blockquote type=3D"cite">
<blockquote type=3D"cite"><span> =A0=A0=A0=A0=A0=A0Pages: =A0=A0=A0=A0=A07<=
/span><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote t=
ype=3D"cite"><span> =A0=A0=A0=A0=A0=A0Characters: 14490</span><br></blockqu=
ote></blockquote><blockquote type=3D"cite">
<blockquote type=3D"cite"><span> =A0=A0=A0=A0=A0=A0Updates: =A0=A0=A0RFC 23=
24</span><br></blockquote></blockquote><blockquote type=3D"cite"><blockquot=
e type=3D"cite"><span></span><br></blockquote></blockquote><blockquote type=
=3D"cite"><blockquote type=3D"cite">
<span> =A0=A0=A0=A0=A0=A0I-D Tag: =A0=A0=A0draft-nazar-htcpcp-tea-00.txt</s=
pan><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote typ=
e=3D"cite"><span></span><br></blockquote></blockquote><blockquote type=3D"c=
ite"><blockquote type=3D"cite">
<span> =A0=A0=A0=A0=A0=A0URL: =A0=A0=A0=A0=A0=A0=A0<a href=3D"http://www.rf=
c-editor.org/rfc/rfc7168.txt" target=3D"_blank">http://www.rfc-editor.org/r=
fc/rfc7168.txt</a></span><br></blockquote></blockquote><blockquote type=3D"=
cite"><blockquote type=3D"cite">
<span></span><br></blockquote></blockquote><blockquote type=3D"cite"><block=
quote type=3D"cite"><span>The Hyper Text Coffee Pot Control Protocol (HTCPC=
P) specification</span><br></blockquote></blockquote><blockquote type=3D"ci=
te">
<blockquote type=3D"cite"><span>does not allow for the brewing of tea, in a=
ll its variety and</span><br></blockquote></blockquote><blockquote type=3D"=
cite"><blockquote type=3D"cite"><span>complexity. =A0This paper outlines an=
 extension to HTCPCP to allow</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span>for pots to provide networked tea-brewing facilities.</span><br></=
blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"=
><span></span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span></span><br></blockquote></blockquote><blockquote type=3D"cite"><bl=
ockquote type=3D"cite"><span>INFORMATIONAL: This memo provides information =
for the Internet community.</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span>It does not specify an Internet standard of any kind. Distribution=
 of</span><br></blockquote></blockquote><blockquote type=3D"cite"><blockquo=
te type=3D"cite">
<span>this memo is unlimited.</span><br></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><span></span><br></blockquote></=
blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>This a=
nnouncement is sent to the IETF-Announce and rfc-dist lists.</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span>To subscribe or unsubscribe, see</span><br></blockquote></blockquo=
te><blockquote type=3D"cite"><blockquote type=3D"cite"><span> <a href=3D"ht=
tp://www.ietf.org/mailman/listinfo/ietf-announce" target=3D"_blank">http://=
www.ietf.org/mailman/listinfo/ietf-announce</a></span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span> <a href=3D"http://mailman.rfc-editor.org/mailman/listinfo/rfc-dis=
t" target=3D"_blank">http://mailman.rfc-editor.org/mailman/listinfo/rfc-dis=
t</a></span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span></span><br></blockquote></blockquote><blockquote type=3D"cite"><bl=
ockquote type=3D"cite"><span>For searching the RFC series, see <a href=3D"h=
ttp://www.rfc-editor.org/search" target=3D"_blank">http://www.rfc-editor.or=
g/search</a></span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span>For downloading RFCs, see <a href=3D"http://www.rfc-editor.org/rfc=
.html" target=3D"_blank">http://www.rfc-editor.org/rfc.html</a></span><br><=
/blockquote>
</blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></sp=
an><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=
=3D"cite"><span>Requests for special distribution should be addressed to ei=
ther the</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span>author of the RFC in question, or to <a href=3D"mailto:rfc-editor@=
rfc-editor.org" target=3D"_blank">rfc-editor@rfc-editor.org</a>. =A0Unless<=
/span><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span>specifically noted otherwise on the RFC itself, all RFCs are for</=
span><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote ty=
pe=3D"cite">
<span>unlimited distribution.</span><br></blockquote></blockquote><blockquo=
te type=3D"cite"><blockquote type=3D"cite"><span></span><br></blockquote></=
blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></span=
><br>
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span>The RFC Editor Team</span><br></blockquote></blockquote><blockquot=
e type=3D"cite"><blockquote type=3D"cite"><span>Association Management Solu=
tions, LLC</span><br>
</blockquote></blockquote><blockquote type=3D"cite"><span></span><br></bloc=
kquote><span></span><br></div></blockquote></div></div></div></blockquote><=
/div><br></div></div>

--bcaec51a7128ad929904f609efd2--


From nobody Wed Apr  2 03:11:13 2014
Return-Path: <leaf.yeh.sdo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8CED1A0196 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 03:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 kl4gNRnuLYqT for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 03:11:06 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id D43B01A019C for <ietf@ietf.org>; Wed,  2 Apr 2014 03:10:58 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id z10so10959758pdj.32 for <ietf@ietf.org>; Wed, 02 Apr 2014 03:10:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:thread-index :content-language; bh=eQt/b9BxmlGq6DP1+uht/Pd64nHNGj8yp0c/YoJxkUo=; b=zRnVctb/0v8m9Rmyoo/2BIPPQuXDdEl73AGKOWITUTsbTGugvr9a0hj/Pp27hPDlXh b8wCfg7mHpIdD1ix3sbS1ott0Dl8u3uHSp/qRb5J5vCmi9WOP/fMGlohCaiy+SyB6Hqt lGFdf5P45VkeLmPZN1ZYY6GtpNPpK+2P8RG7GJDHS5ZTqOkDD9iMnrbAc+7TDb1ULFfx onaFswTC/69EcrxzWu1lcn8JNCOzCBWnSY9ToH7Hr3/c0Fr3jwXbatkKYI6QcOZIiFW2 FSDfHE/Wtd9PV5ICjXE5HwScWKKcC9JR3VRqYg8oxQGviEAqHFBiSNG0cCPifoCt5ruY AlGQ==
X-Received: by 10.68.113.5 with SMTP id iu5mr24672823pbb.60.1396433455177; Wed, 02 Apr 2014 03:10:55 -0700 (PDT)
Received: from PC ([218.241.103.217]) by mx.google.com with ESMTPSA id oa3sm3414912pbb.15.2014.04.02.03.10.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 02 Apr 2014 03:10:54 -0700 (PDT)
From: "Leaf Yeh" <leaf.yeh.sdo@gmail.com>
To: "'Randy Bush'" <randy@psg.com>, "'IETF Disgust'" <ietf@ietf.org>
References: <20140401220128.3CD897FC3A9@rfc-editor.org> <m2a9c437i6.wl%randy@psg.com>
In-Reply-To: <m2a9c437i6.wl%randy@psg.com>
Subject: RE: RFC 7169 on The NSA (No Secrecy Afforded) Certificate Extension
Date: Wed, 2 Apr 2014 18:10:50 +0800
Message-ID: <533be22e.0382440a.2187.ffff90e5@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac9OCab4hBAEhIa9ThqxpEjMWONZOgAC6/oQ
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6tYX7vBpydA40CoRDiLJeI2Y3Fk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 10:11:11 -0000

This extension is needed on Apr. 1st. 

Leaf


-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Randy Bush
Sent: Wednesday, April 02, 2014 8:22 AM
To: IETF Disgust
Subject: Re: RFC 7169 on The NSA (No Secrecy Afforded) Certificate Extension

>         RFC 7169
>         Title:      The NSA (No Secrecy Afforded) 
>                     Certificate Extension 
>         URL:        http://www.rfc-editor.org/rfc/rfc7169.txt

i do not understand why this extension is needed.  the 5eyes have all your
keys.  the flag should always be on.  is the real intent that, when the
extension/flag is not on in a received certificate, then you know it is
bogus?

randy


From nobody Wed Apr  2 04:58:17 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77E951A01F7 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 04:58:15 -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, SPF_PASS=-0.001] autolearn=ham
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 c2KOxwWZFUN7 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 04:58:11 -0700 (PDT)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) by ietfa.amsl.com (Postfix) with ESMTP id B09F31A01F5 for <ietf@ietf.org>; Wed,  2 Apr 2014 04:58:10 -0700 (PDT)
Received: by mail-lb0-f170.google.com with SMTP id s7so61442lbd.29 for <ietf@ietf.org>; Wed, 02 Apr 2014 04:58:06 -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:content-type; bh=OhPE5FlXahPPJP9AnPzTWXJxLg0wetvIH/wasIc5sOU=; b=YmSY617xC/BcqPqUlU+YinHAfQfamFotau9RjUr5rVEY3jCEWXhl0LfkXV9rmWZte7 MVxzH4dwbhVlwMlVB4SAbGBMjBWjhfhc8UVYFX1NQP0NgvZCsS6KbdBtYjoJOUOWO3EZ 6xTQIXntVOTqxXGCO+DyO3XoUjiKME7+F6QmlH9lirmX0S36BOdBV4gUVv7aW5Rzp4M7 WsVMZazioiWxczCeGtNeoSNk0sx4+Kf80B98wf8bntE+kD/rUqpfssMYvAzrJCyiakYT j15epwe21ByRlNj9BgJVb3yHNrqewjirQb0snFTB/wAaD/s7J0LsPw9VRhTcNnPT/Lxl JtyA==
MIME-Version: 1.0
X-Received: by 10.112.202.3 with SMTP id ke3mr39846lbc.68.1396439886299; Wed, 02 Apr 2014 04:58:06 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Wed, 2 Apr 2014 04:58:06 -0700 (PDT)
In-Reply-To: <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>
Date: Wed, 2 Apr 2014 07:58:06 -0400
Message-ID: <CAMm+LwhNS-iKuzSCb0dhBypVFVzmi7HCZFvGNGExL5WtJ1jhsg@mail.gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ole Jacobsen <olejacobsen@me.com>
Content-Type: multipart/alternative; boundary=001a11c36cce5f861a04f60dffba
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eDeMsk3MerUeuCmGmQ1VZZjcR_U
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 11:58:15 -0000

--001a11c36cce5f861a04f60dffba
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Apr 1, 2014 at 11:16 PM, Ole Jacobsen <olejacobsen@me.com> wrote:

> As any Brit will tell you: ice has absolutely NOTHING to do with tea, so
> it would be out of scope.
>
> Sat-too-long-and-is-still-hot is, if I recall, known as "stewed" and
> anyone responsible faces possible deportation from the UK. A very serious
> matter indeed, almost as serious as refusing to obey the rules of a queue.
>

Oh we have discovered over the years that people have the oddest ideas on
how to make tea.

Here in Boston there was a group that made tea with salt water some years
back. Turned out the only solution was kicking them out of the empire.

-- 
Website: http://hallambaker.com/

--001a11c36cce5f861a04f60dffba
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Apr 1, 2014 at 11:16 PM, Ole Jacobsen <span dir=3D"ltr">&lt=
;<a href=3D"mailto:olejacobsen@me.com" target=3D"_blank">olejacobsen@me.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"auto"><div>As any Brit will tell=
 you: ice has absolutely NOTHING to do with tea, so it would be out of scop=
e.</div>
<div><br></div><div>Sat-too-long-and-is-still-hot is, if I recall, known as=
 &quot;stewed&quot; and anyone responsible faces possible deportation from =
the UK. A very serious matter indeed, almost as serious as refusing to obey=
 the rules of a queue.</div>
</div></blockquote><div><br></div><div>Oh we have discovered over the years=
 that people have the oddest ideas on how to make tea.</div><div><br></div>=
<div>Here in Boston there was a group that made tea with salt water some ye=
ars back. Turned out the only solution was kicking them out of the empire.<=
/div>
</div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br>
</div></div>

--001a11c36cce5f861a04f60dffba--


From nobody Wed Apr  2 05:06:50 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED31E1A01F5 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 05:06:45 -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, SPF_PASS=-0.001] autolearn=ham
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 RhTGAcF9nu2T for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 05:06:41 -0700 (PDT)
Received: from mail-wg0-x22b.google.com (mail-wg0-x22b.google.com [IPv6:2a00:1450:400c:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id D3E2F1A01EC for <ietf@ietf.org>; Wed,  2 Apr 2014 05:06:40 -0700 (PDT)
Received: by mail-wg0-f43.google.com with SMTP id x13so107610wgg.14 for <ietf@ietf.org>; Wed, 02 Apr 2014 05:06:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=YTLEjpOmcF+557GC0YywkpK31rFoMynCqXmaA2KPq7Q=; b=oVYV+QFGPl9Kdbp5MzNmo737pypceuvjVqpASK5v8MIoUODGCb5gCU40i7CSGdYl76 v8/zaa6RwJXluT8/Dq0xYapp1qfoNxP1lKjwMDUPCXrvX0HAC2f8OYsXaNK7eUDkA1uq 0cVJ3XIOPpbB1751F9KAuPLkmxmqBYIGvu0b1ljkDuQ2E2kUnHYW+gGWEVfWL/Wd0N0P L9mL4tAWrBal/bo5Kl4+eOwIzPIVTvGLZZTs6iJbaenehPunPsUNV7vx8pUFmgf0M6qH oInsoKnS/TAvoPl8VnnxwEWj/1tyhKkN2LyTARL33ZYPRs9TrOt388oHqXpkAudUufKu LPHg==
X-Received: by 10.194.57.38 with SMTP id f6mr45868wjq.59.1396440396352; Wed, 02 Apr 2014 05:06:36 -0700 (PDT)
Received: from [172.24.251.171] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id n41sm4111297eeg.4.2014.04.02.05.06.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 02 Apr 2014 05:06:35 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_823C0483-4E73-4C7D-A4C2-855B3A9F139A"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CAMm+LwhNS-iKuzSCb0dhBypVFVzmi7HCZFvGNGExL5WtJ1jhsg@mail.gmail.com>
Date: Wed, 2 Apr 2014 15:06:31 +0300
Message-Id: <59C504C7-9E84-4CE8-B46D-A5E90329C0C8@gmail.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com> <CAMm+LwhNS-iKuzSCb0dhBypVFVzmi7HCZFvGNGExL5WtJ1jhsg@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7PB3RiqfsREvJsMMzjTOtoDNhag
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 12:06:46 -0000

--Apple-Mail=_823C0483-4E73-4C7D-A4C2-855B3A9F139A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 2, 2014, at 2:58 PM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:

>=20
>=20
>=20
> On Tue, Apr 1, 2014 at 11:16 PM, Ole Jacobsen <olejacobsen@me.com> =
wrote:
> As any Brit will tell you: ice has absolutely NOTHING to do with tea, =
so it would be out of scope.
>=20
> Sat-too-long-and-is-still-hot is, if I recall, known as "stewed" and =
anyone responsible faces possible deportation from the UK. A very =
serious matter indeed, almost as serious as refusing to obey the rules =
of a queue.
>=20
> Oh we have discovered over the years that people have the oddest ideas =
on how to make tea.
>=20
> Here in Boston there was a group that made tea with salt water some =
years back. Turned out the only solution was kicking them out of the =
empire.

The problem with that tea was not the salt. That turns out to be =
customary in Mongolia. The real issue that the tea was =93weak, =
bordering on homeopathic=94:

http://what-if.xkcd.com/79/

We can=92t have that.

Yoav



--Apple-Mail=_823C0483-4E73-4C7D-A4C2-855B3A9F139A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Apr 2, 2014, at 2:58 PM, Phillip =
Hallam-Baker &lt;<a =
href=3D"mailto:hallam@gmail.com">hallam@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Tue, Apr 1, 2014 at 11:16 PM, Ole Jacobsen =
<span dir=3D"ltr">&lt;<a href=3D"mailto:olejacobsen@me.com" =
target=3D"_blank">olejacobsen@me.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin: 0px 0px 0px 0.8ex; =
border-left-width: 1px; border-left-color: rgb(204, 204, 204); =
border-left-style: solid; padding-left: 1ex; position: static; z-index: =
auto;"><div dir=3D"auto"><div>As any Brit will tell you: ice has =
absolutely NOTHING to do with tea, so it would be out of scope.</div>
<div><br></div><div>Sat-too-long-and-is-still-hot is, if I recall, known =
as "stewed" and anyone responsible faces possible deportation from the =
UK. A very serious matter indeed, almost as serious as refusing to obey =
the rules of a queue.</div>
</div></blockquote><div><br></div><div>Oh we have discovered over the =
years that people have the oddest ideas on how to make =
tea.</div><div><br></div><div>Here in Boston there was a group that made =
tea with salt water some years back. Turned out the only solution was =
kicking them out of the empire.</div>
</div></div></div></blockquote><br></div><div>The problem with that tea =
was not the salt. That turns out to be customary in Mongolia. The real =
issue that the tea was =93weak, bordering on =
homeopathic=94:</div><div><br></div><div><a =
href=3D"http://what-if.xkcd.com/79/">http://what-if.xkcd.com/79/</a></div>=
<div><br></div><div>We can=92t have =
that.</div><div><br></div><div>Yoav</div><div><br></div><br></body></html>=

--Apple-Mail=_823C0483-4E73-4C7D-A4C2-855B3A9F139A--


From nobody Wed Apr  2 06:59:38 2014
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED781A01EA for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 06:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 4I6gBRsIqg75 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 06:59:30 -0700 (PDT)
Received: from b.painless.aa.net.uk (b.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e34]) by ietfa.amsl.com (Postfix) with ESMTP id 14DA61A01E1 for <ietf@ietf.org>; Wed,  2 Apr 2014 06:59:30 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by b.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <elwynd@dial.pipex.com>) id 1WVLhM-0002RR-2j; Wed, 02 Apr 2014 14:59:24 +0100
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <59C504C7-9E84-4CE8-B46D-A5E90329C0C8@gmail.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com> <CAMm+LwhNS-iKuzSCb0dhBypVFVzmi7HCZFvGNGExL5WtJ1jhsg@mail.gmail.com> <59C504C7-9E84-4CE8-B46D-A5E90329C0C8@gmail.com>
Content-Type: text/plain; charset="iso-8859-13"
Date: Wed, 02 Apr 2014 14:59:22 +0100
Message-Id: <1396447162.15324.7725.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XMgrk8UBwP86j_L9kQWryz-J_tI
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 13:59:35 -0000

On Wed, 2014-04-02 at 15:06 +0300, Yoav Nir wrote:
>=20
> On Apr 2, 2014, at 2:58 PM, Phillip Hallam-Baker <hallam@gmail.com>
> wrote:
>=20
> >=20
> >=20
> >=20
> > On Tue, Apr 1, 2014 at 11:16 PM, Ole Jacobsen <olejacobsen@me.com>
> > wrote:
> >         As any Brit will tell you: ice has absolutely NOTHING to do
> >         with tea, so it would be out of scope.
> >        =20
> >        =20
> >         Sat-too-long-and-is-still-hot is, if I recall, known as
> >         "stewed" and anyone responsible faces possible deportation
> >         from the UK. A very serious matter indeed, almost as serious
> >         as refusing to obey the rules of a queue.
> >=20
> >=20
> > Oh we have discovered over the years that people have the oddest
> > ideas on how to make tea.
> >=20
> >=20
> > Here in Boston there was a group that made tea with salt water some
> > years back. Turned out the only solution was kicking them out of the
> > empire.
>=20
>=20
> The problem with that tea was not the salt. That turns out to be
> customary in Mongolia.=20

.. and of course the rancid yak butter...

/Elwyn

> The real issue that the tea was =B4weak, bordering on homeopathic=A1:
>=20
>=20
> http://what-if.xkcd.com/79/
>=20
>=20
> We can=FFt have that.
>=20
>=20
> Yoav
>=20
>=20
>=20


From nobody Wed Apr  2 07:13:05 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C6A01A01E6 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 07:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4TErhXqQTGzI for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 07:12:59 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id D1DFD1A0220 for <ietf@ietf.org>; Wed,  2 Apr 2014 07:12:59 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 316381B83EA for <ietf@ietf.org>; Wed,  2 Apr 2014 07:12:56 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 0A49C190043; Wed,  2 Apr 2014 07:12:56 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Apr 2014 07:12:55 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <1396447162.15324.7725.camel@mightyatom>
Date: Wed, 2 Apr 2014 10:12:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <E987419F-495E-4AA7-AD1C-26122486D9EF@nominum.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com> <CAMm+LwhNS-iKuzSCb0dhBypVFVzmi7HCZFvGNGExL5WtJ1jhsg@mail.gmail.com> <59C504C7-9E84-4CE8-B46D-A5E90329C0C8@gmail.com> <1396447162.15324.7725.camel@mightyatom>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wlY3m5ZMjNS7Wc1krigFJsO8TCk
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 14:13:04 -0000

On Apr 2, 2014, at 9:59 AM, Elwyn Davies <elwynd@dial.pipex.com> wrote:
> .. and of course the rancid yak butter...

It's better if the yak butter isn't rancid.

Anyway, these are all good suggestions for draft-ietf-tcoff-rfc7168bis.  =
 Is anyone interested in forming a BOF?


From nobody Wed Apr  2 07:13:52 2014
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 746C51A022D; Wed,  2 Apr 2014 07:13:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable
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 9mMFeYAKPoZI; Wed,  2 Apr 2014 07:13:44 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 6B7D61A0230; Wed,  2 Apr 2014 07:13:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 3ECF31E4366; Wed,  2 Apr 2014 07:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6jsgwVSZXjg0; Wed,  2 Apr 2014 07:12:54 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) by c8a.amsl.com (Postfix) with ESMTPSA id AA7FC1E1890; Wed,  2 Apr 2014 07:12:53 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1085)
Subject: Reminder: Call for RFC Series Oversight Committee (RSOC) Nominations
From: IAB Chair <iab-chair@iab.org>
Date: Wed, 2 Apr 2014 10:13:35 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CE5C4977-CEFC-4B0E-9916-9733BAECA42B@iab.org>
References: <BFB28BF0-3561-455A-963F-B780C1560EB2@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DhnpNDaRuBSRbgrCLNedxeOmLE0
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 14:13:48 -0000

Please submit nominations by 8 April 2014.

Thanks,
  Russ


Begin forwarded message:

> From: IAB Chair <iab-chair@iab.org>
> Date: March 26, 2014 11:29:38 AM EDT
> To: IETF Announce <ietf-announce@ietf.org>
> Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
> Subject: Call for RFC Series Oversight Committee (RSOC) Nominations
>=20
> As specified in "RFC Editor Model (Version 2)" (RFC 6635), the IAB is =
responsible for appointing the members of the RFC Series Oversight =
Committee (RSOC).  Bernard Aboba has stepped down from his role on the =
RSOC.  The IAB thanks him for his service.
>=20
> The IAB is now looking for a community member to appoint to the RSOC. =
This message is a call for nominations for that position.  If you are =
interested, or there is someone you know of who would make a good =
member, please nominate yourself or that person.
>=20
> As noted in RFC 6635, the RSOC, which currently includes two IAB =
members, acts with authority delegated from the IAB, and the RSOC is =
responsible for approving consensus policy and vision documents =
developed by the RFC Series Editor (RSE) in collaboration with the =
community.  The RSOC is also responsible for ensuring that the RFC =
Series is run in a transparent and accountable manner.  For decisions =
that affect the RFC Series Editor individually, the RSOC prepares =
recommendations for the IAB, such as preparing the performance reviews =
of the RSE.  RSOC members are expected to recognize potential conflicts =
of interest and behave accordingly.
>=20
> If you would like to nominate a candidate for membership in the RSOC, =
please send information on the candidate, including their email address, =
to iab-chair at iab.org and execd at iab.org.  Self-nominations are =
acceptable.
>=20
> The current membership of the RSOC can be seen at =
http://www.iab.org/activities/programs/rfc-editor-program/.
>=20
> Nominations should be received by 8 April 2014.
>=20
> The IAB will confirm individuals willingness to be considered, and =
publish the resulting list so that the community can provide comments =
before the IAB makes any decisions on RSOC membership.
>=20
> The new member will begin serving on the RSOC as soon as the IAB =
completes the selection process.
>=20
> For the information of potential nominees, the RSOC will be having a =
half-day face-to-face meeting in Toronto on 19 July 2014, the Saturday =
before IETF 90.
>=20
> The current focus of the RSOC is on:
>=20
> 1) Overseeing and assisting the RSE in the process of evoling the RFC =
format and style.
>=20
> 2) Periodic reviews of the RFSE performance.
>=20
> 3) Working with the RSE and the IETF Administrative Oversight =
Committee (IAOC) on the statements of work for contracts related to the =
RFC Production Center and RFC Publisher.
>=20
> The RSOC usually meets virtually once a month for an hour, a lunch at =
every IETF meeting, and a half day in-person meeting once a year =
(usually scheduled the weekend before an IETF meeting at the same venue =
(as noted above the next one will be in Toronto).  More time may be =
required if the applicant participates in leadership of the committee, =
design teams, or other related activities. RSOC members are expected to =
follow the rfc-interest mailing list, a usually low-volume list for =
internal communication, and to be familiar with discussion topics =
related to the RFC series on the ietf@ietf.org list.
>=20
> Thank you,
> Russ Housley
> IAB Chair
>=20


From a.arsenault.81@gmail.com  Wed Apr  2 04:44:59 2014
Return-Path: <a.arsenault.81@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 935FD1A01F1 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 04:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 Spu7XP4SXZhR for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 04:44:55 -0700 (PDT)
Received: from mail-qg0-x22d.google.com (mail-qg0-x22d.google.com [IPv6:2607:f8b0:400d:c04::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 242941A01EC for <ietf@ietf.org>; Wed,  2 Apr 2014 04:44:55 -0700 (PDT)
Received: by mail-qg0-f45.google.com with SMTP id j5so57842qga.4 for <ietf@ietf.org>; Wed, 02 Apr 2014 04:44:51 -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:content-type; bh=c+bA1NkQ4MZdrD3bED0JPAAHBbV1oeNcqqmVnXLxh6Q=; b=r55t4+A9CM0RdI9S0hB3p7K7dHtLhCr4XEfzJzyM438pDIBjyBOhjgZaTkeGbh92TB J5Ak4XMufv16lL88mtOhAzEM42da2lqa5nGtUjKwXvc5PK8tdI4lpNpSGkVK9hMuaBAC c61q1MD4xNxhumTSN3KocvHCmYnpF1Qu2tUTtENktJfCOdFHJ0btcaWqCVjLJAoXvBr6 8G8BDEh912RK6AXbf1H+ERyNX+q6sB3V9Q4p5jRDnOGA8Pkxrtf3A0TRUJPNuJ02aett XSSzE91UuODZsjiAoZIK2topBRUWL07/gCUnhsFfk8qai+QrDgYIItw6cwH3J49RERez oZXw==
MIME-Version: 1.0
X-Received: by 10.140.20.36 with SMTP id 33mr22194255qgi.37.1396439091210; Wed, 02 Apr 2014 04:44:51 -0700 (PDT)
Received: by 10.140.18.197 with HTTP; Wed, 2 Apr 2014 04:44:51 -0700 (PDT)
In-Reply-To: <533be22e.0382440a.2187.ffff90e5@mx.google.com>
References: <20140401220128.3CD897FC3A9@rfc-editor.org> <m2a9c437i6.wl%randy@psg.com> <533be22e.0382440a.2187.ffff90e5@mx.google.com>
Date: Wed, 2 Apr 2014 07:44:51 -0400
Message-ID: <CAEC7viAbxd=kpKAzMkYUA3L5jXAcp-9kVN1-oyO3=FMpLvcTmw@mail.gmail.com>
Subject: Re: RFC 7169 on The NSA (No Secrecy Afforded) Certificate Extension
From: Al Arsenault <a.arsenault.81@gmail.com>
To: Leaf Yeh <leaf.yeh.sdo@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c12accfb6ef504f60dcf57
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pa3d9Ig1uc7l-EtWRdsE1q4mbtA
X-Mailman-Approved-At: Wed, 02 Apr 2014 08:51:15 -0700
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 11:46:45 -0000

--001a11c12accfb6ef504f60dcf57
Content-Type: text/plain; charset=ISO-8859-1

RFC 7169 lacks a needed reference to RFC 3514.  The author should have
specified that if a certificate with the NSA extension set to "TRUE" is
used with IPsec or TLS, the Evil Bit as specified in 3514 SHOULD also be
set in any appropriate IP headers.

I would argue that this is the case even if the subject of the certificate
has no explicit evil intent. That's the best way to characterize the
system.




On Wed, Apr 2, 2014 at 6:10 AM, Leaf Yeh <leaf.yeh.sdo@gmail.com> wrote:

> This extension is needed on Apr. 1st.
>
> Leaf
>
>
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Randy Bush
> Sent: Wednesday, April 02, 2014 8:22 AM
> To: IETF Disgust
> Subject: Re: RFC 7169 on The NSA (No Secrecy Afforded) Certificate
> Extension
>
> >         RFC 7169
> >         Title:      The NSA (No Secrecy Afforded)
> >                     Certificate Extension
> >         URL:        http://www.rfc-editor.org/rfc/rfc7169.txt
>
> i do not understand why this extension is needed.  the 5eyes have all your
> keys.  the flag should always be on.  is the real intent that, when the
> extension/flag is not on in a received certificate, then you know it is
> bogus?
>
> randy
>
>

--001a11c12accfb6ef504f60dcf57
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">RFC 7169 lacks a needed reference to RFC 3514.=A0 The auth=
or should have specified that if a certificate with the NSA extension set t=
o &quot;TRUE&quot; is used with IPsec or TLS, the Evil Bit as specified in =
3514 SHOULD also be set in any appropriate IP headers. <br>
<br>I would argue that this is the case even if the subject of the certific=
ate has no explicit evil intent. That&#39;s the best way to characterize th=
e system. <br><br><br></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">
On Wed, Apr 2, 2014 at 6:10 AM, Leaf Yeh <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:leaf.yeh.sdo@gmail.com" target=3D"_blank">leaf.yeh.sdo@gmail.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This extension is needed on Apr. 1st.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Leaf<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
-----Original Message-----<br>
From: ietf [mailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ie=
tf.org</a>] On Behalf Of Randy Bush<br>
Sent: Wednesday, April 02, 2014 8:22 AM<br>
To: IETF Disgust<br>
Subject: Re: RFC 7169 on The NSA (No Secrecy Afforded) Certificate Extensio=
n<br>
<br>
&gt; =A0 =A0 =A0 =A0 RFC 7169<br>
&gt; =A0 =A0 =A0 =A0 Title: =A0 =A0 =A0The NSA (No Secrecy Afforded)<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Certificate Extension<br>
&gt; =A0 =A0 =A0 =A0 URL: =A0 =A0 =A0 =A0<a href=3D"http://www.rfc-editor.o=
rg/rfc/rfc7169.txt" target=3D"_blank">http://www.rfc-editor.org/rfc/rfc7169=
.txt</a><br>
<br>
i do not understand why this extension is needed. =A0the 5eyes have all you=
r<br>
keys. =A0the flag should always be on. =A0is the real intent that, when the=
<br>
extension/flag is not on in a received certificate, then you know it is<br>
bogus?<br>
<br>
randy<br>
<br>
</div></div></blockquote></div><br></div>

--001a11c12accfb6ef504f60dcf57--


From nobody Wed Apr  2 08:51:50 2014
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D01281A0034 for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 17:18:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 YoUt_yxjdkee for <ietf@ietfa.amsl.com>; Tue,  1 Apr 2014 17:18:07 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by ietfa.amsl.com (Postfix) with ESMTP id 65C241A002F for <ietf@ietf.org>; Tue,  1 Apr 2014 17:18:07 -0700 (PDT)
Received: from [IPv6:2001:470:88a3::c99f:d7f4:3743:79f] (unknown [IPv6:2001:470:88a3:0:c99f:d7f4:3743:79f]) by toccata.fugue.com (Postfix) with ESMTPSA id 37ADF2380295; Tue,  1 Apr 2014 20:18:01 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <alpine.OSX.2.01.1404011612360.14186@rabdullah.local>
Date: Tue, 1 Apr 2014 20:18:01 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <A27DA46C-0ED9-4DBA-A4E1-B6B7070179DD@fugue.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <alpine.OSX.2.01.1404011612360.14186@rabdullah.local>
To: Ole Jacobsen <olejacobsen@me.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gaOY3YhwhMtU5CPH7KXL4glSH64
X-Mailman-Approved-At: Wed, 02 Apr 2014 08:51:46 -0700
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 00:18:10 -0000

On Apr 1, 2014, at 7:14 PM, Ole Jacobsen <olejacobsen@me.com> wrote:
> Have you spoken with Ted Lemon about this at all?

My wife (Andrea, for those who haven't met her) usually only drinks tea =
at work, so not with Lemon, unless she is beside herself for some =
reason.


From nobody Wed Apr  2 09:21:26 2014
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D552B1A02D4 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 09:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
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 guHsRuPntWue for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 09:21:18 -0700 (PDT)
Received: from auth.a.painless.aa.net.uk (a.painless.aa.net.uk [IPv6:2001:8b0:0:30::51bb:1e33]) by ietfa.amsl.com (Postfix) with ESMTP id 5123F1A0254 for <ietf@ietf.org>; Wed,  2 Apr 2014 09:21:18 -0700 (PDT)
Received: from mightyatom.folly.org.uk ([81.187.254.250]) by a.painless.aa.net.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from <elwynd@dial.pipex.com>) id 1WVNuX-00083i-PD; Wed, 02 Apr 2014 17:21:13 +0100
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <59C504C7-9E84-4CE8-B46D-A5E90329C0C8@gmail.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com> <CAMm+LwhNS-iKuzSCb0dhBypVFVzmi7HCZFvGNGExL5WtJ1jhsg@mail.gmail.com> <59C504C7-9E84-4CE8-B46D-A5E90329C0C8@gmail.com>
Content-Type: text/plain; charset="iso-8859-13"
Date: Wed, 02 Apr 2014 17:21:02 +0100
Message-Id: <1396455663.15324.7874.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hLVmAXi22I5DnEL9c8AFt_QSMlc
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 16:21:23 -0000

On Wed, 2014-04-02 at 15:06 +0300, Yoav Nir wrote:
>=20
> On Apr 2, 2014, at 2:58 PM, Phillip Hallam-Baker <hallam@gmail.com>
> wrote:
>=20
> >=20
> >=20
> >=20
> > On Tue, Apr 1, 2014 at 11:16 PM, Ole Jacobsen <olejacobsen@me.com>
> > wrote:
> >         As any Brit will tell you: ice has absolutely NOTHING to do
> >         with tea, so it would be out of scope.
> >        =20
> >        =20
> >         Sat-too-long-and-is-still-hot is, if I recall, known as
> >         "stewed" and anyone responsible faces possible deportation
> >         from the UK. A very serious matter indeed, almost as serious
> >         as refusing to obey the rules of a queue.
> >=20
> >=20
> > Oh we have discovered over the years that people have the oddest
> > ideas on how to make tea.
> >=20
> >=20
> > Here in Boston there was a group that made tea with salt water some
> > years back. Turned out the only solution was kicking them out of the
> > empire.
>=20
>=20
> The problem with that tea was not the salt. That turns out to be
> customary in Mongolia. The real issue that the tea was =B4weak,
> bordering on homeopathic=A1:
>=20
>=20
> http://what-if.xkcd.com/79/
>=20

Nice!

And it addresses the failure to boil the ocean (unlike certain WGs)!  ;-)

/E
>=20
> We can=FFt have that.
>=20
>=20
> Yoav
>=20
>=20
>=20


From nobody Wed Apr  2 10:15:41 2014
Return-Path: <thierry.moreau@connotech.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1661A02ED for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 10:15:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.013
X-Spam-Level: 
X-Spam-Status: No, score=-0.013 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 RmLPndzu_4JE for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 10:15:33 -0700 (PDT)
Received: from mail.connotech.com (connotech.com [76.10.176.241]) by ietfa.amsl.com (Postfix) with ESMTP id 3A1081A024D for <ietf@ietf.org>; Wed,  2 Apr 2014 10:15:33 -0700 (PDT)
Received: from [192.168.1.204] (DODECA1ER.CONNOTECH-INTERNAL.COM [192.168.1.204]) by mail.connotech.com (Postfix) with ESMTPA id D1A49318E5 for <ietf@ietf.org>; Wed,  2 Apr 2014 13:10:55 -0400 (EDT)
Message-ID: <533C4624.50408@connotech.com>
Date: Wed, 02 Apr 2014 17:17:24 +0000
From: Thierry Moreau <thierry.moreau@connotech.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: An RFC7169 use case (!)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RjChg7nEgJJtxpe1V4T_eOeznW0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 17:15:38 -0000

Dear IETF'ers:

Notwithstanding the fact that the RFC7169 and the -02 revision to the 
Internet Draft draft-housley-pkix-oids are at face value April fool 
publications in the IETF tradition, the informational X.509 certificate 
extension does have a specific use case in the context of "first party 
certification" paradigm.

My purpose is neither to document the underlying trust arrangements and 
security mechanisms (as I did in the ill-fated 
draft-moreau-pkix-aixcm-00 or 
http://www.connotech.com/public-domain-aixcm-00.txt), neither to argue 
about their value, nor to propose an RFC7169bis draft that would fix the 
semantic deficiencies in the RFC7169 as published. My only purpose is to 
give notice to IETF'ers that RFC7169 does have an unintended usefulness.

Nonetheless, here is a high level description for the reader who would 
accept to offload the preconceived notions of PKI trust model. A TLS 
server in the "first party certification" paradigm accepts (or denies) a 
TLS client identity based on the sole client public key found in the TLS 
handshake (the server denies client access if an unknown public key is 
presented). Because bare client public keys are not well supported (if 
allowed at all) by the fielded TLS implementations, the TLS client has 
to package the public key in a so-called "client certificate." However, 
obtaining a proper PKI client certificate is an undertaking in the 
Internet era similar to the Peary and Scott treks to the North Pole in 
the nineteen century (neither of them were able to provide reliable 
evidence of their achievements). The first party certification paradigm 
relieves the client from the requirement for a proper client 
certificate. The remaining are implementation details. Self-signed 
client certificates has been proposed for this purpose (if I recall 
correctly some PKIX discussions a few years back). I proposed 
self-issued client certificates, which involves a "dummy certification 
authority," i.e. with a publicly breached signature key pair and for 
which the RFC7169 certificate extension applies. If the reader follows 
the reasoning, it becomes evident that anyone can act (sign security 
certificates) on behalf of the dummy CA, including the TLS client 
implementation (just like anyone can issue a self-signed certificate).

Thus I am grateful to the RFC7169 author and to the IETF for an official 
certificate extension in support of the first party certification 
paradigm, offering an RFC-compliant alternative to the client 
self-signed certificates.

It may me the first time that an April fool RFC is actually useful.

Regards,

-- Thierry Moreau


From nobody Wed Apr  2 15:54:57 2014
Return-Path: <clint.chaplin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8B91A040B; Wed,  2 Apr 2014 15:54:55 -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, SPF_PASS=-0.001] autolearn=ham
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 yX-aqp7R0_Yn; Wed,  2 Apr 2014 15:54:51 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7D5A51A040F; Wed,  2 Apr 2014 15:54:46 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id w62so973419wes.0 for <multiple recipients>; Wed, 02 Apr 2014 15:54:42 -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:content-type; bh=NH9KqfYdbQjwJuKJmyUyJsMGVzos3JcVRb/6kL4pvj4=; b=bm7Z4I7yznQ+BkPqqSBZzjg6ABFpXMU81VUkhDEy5jjyrdPJngspM466p/vvo0MCde yQxkhow7iR3G3hqUmr+ctv++zG7l8LDUACxyenfE8C0Uh/H+8Y3SS6KR08wuN78ud8nI Z2JFb8o54VuzQKRdBhp9uPwiRBhC2L+sg4vg9kvr9kKau5Pk1zvA74RHOMYkQSooio5C 7AeDr9P8qzIi2j8kCPJjMQfcFWs3xpbEqVbTeIpmYQX4g9WrMNDmZl2pvNoKqS/R8gt8 X5KNHsfqK58rHoVqWg45SEo6UHHd9733JH8GtC7pEUnXmS47Yk8bVL9IT2SlLE3DN7Al Nukw==
MIME-Version: 1.0
X-Received: by 10.194.187.107 with SMTP id fr11mr4504459wjc.70.1396479282041;  Wed, 02 Apr 2014 15:54:42 -0700 (PDT)
Received: by 10.194.235.10 with HTTP; Wed, 2 Apr 2014 15:54:41 -0700 (PDT)
In-Reply-To: <20140401220040.F06667FC394@rfc-editor.org>
References: <20140401220040.F06667FC394@rfc-editor.org>
Date: Wed, 2 Apr 2014 15:54:41 -0700
Message-ID: <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Clint Chaplin <clint.chaplin@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=047d7bb03f608adab404f6172bd7
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Aq4nKwIt25llnjWwHqLnqPE2lZM
Cc: drafts-update-ref@iana.org, rfc-dist@rfc-editor.org, IETF Announcement list <ietf-announce@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 22:54:55 -0000

--047d7bb03f608adab404f6172bd7
Content-Type: text/plain; charset=UTF-8

Will there be an option for not-tea?


On Tue, Apr 1, 2014 at 3:00 PM, <rfc-editor@rfc-editor.org> wrote:

> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 7168
>
>         Title:      The Hyper Text Coffee Pot
>                     Control Protocol for Tea Efflux Appliances
>                     (HTCPCP-TEA)
>         Author:     I. Nazar
>         Status:     Informational
>         Stream:     Independent
>         Date:       1 April 2014
>         Mailbox:    inazar@deviantart.com
>         Pages:      7
>         Characters: 14490
>         Updates:    RFC 2324
>
>         I-D Tag:    draft-nazar-htcpcp-tea-00.txt
>
>         URL:        http://www.rfc-editor.org/rfc/rfc7168.txt
>
> The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification
> does not allow for the brewing of tea, in all its variety and
> complexity.  This paper outlines an extension to HTCPCP to allow
> for pots to provide networked tea-brewing facilities.
>
>
> INFORMATIONAL: This memo provides information for the Internet community.
> It does not specify an Internet standard of any kind. Distribution of
> this memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   http://www.ietf.org/mailman/listinfo/ietf-announce
>   http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see http://www.rfc-editor.org/search
> For downloading RFCs, see http://www.rfc-editor.org/rfc.html
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
>
>


-- 
Clint (JOATMON) Chaplin
Principal Engineer
Standards & Technology Enabling
Advanced Technology Lab
Samsung R&D Institute America - Silicon Valley

--047d7bb03f608adab404f6172bd7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Will there be an option for not-tea?</div><div class=3D"gm=
ail_extra"><br><br><div class=3D"gmail_quote">On Tue, Apr 1, 2014 at 3:00 P=
M,  <span dir=3D"ltr">&lt;<a href=3D"mailto:rfc-editor@rfc-editor.org" targ=
et=3D"_blank">rfc-editor@rfc-editor.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">A new Request for Comments is now available =
in online RFC libraries.<br>
<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 RFC 7168<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title: =C2=A0 =C2=A0 =C2=A0The Hyper Text Coffe=
e Pot<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Contr=
ol Protocol for Tea Efflux Appliances<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (HTCP=
CP-TEA)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Author: =C2=A0 =C2=A0 I. Nazar<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Status: =C2=A0 =C2=A0 Informational<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Stream: =C2=A0 =C2=A0 Independent<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Date: =C2=A0 =C2=A0 =C2=A0 1 April 2014<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Mailbox: =C2=A0 =C2=A0<a href=3D"mailto:inazar@=
deviantart.com">inazar@deviantart.com</a><br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Pages: =C2=A0 =C2=A0 =C2=A07<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Characters: 14490<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Updates: =C2=A0 =C2=A0RFC 2324<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 I-D Tag: =C2=A0 =C2=A0draft-nazar-htcpcp-tea-00=
.txt<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 URL: =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"http=
://www.rfc-editor.org/rfc/rfc7168.txt" target=3D"_blank">http://www.rfc-edi=
tor.org/rfc/rfc7168.txt</a><br>
<br>
The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification<br>
does not allow for the brewing of tea, in all its variety and<br>
complexity. =C2=A0This paper outlines an extension to HTCPCP to allow<br>
for pots to provide networked tea-brewing facilities.<br>
<br>
<br>
INFORMATIONAL: This memo provides information for the Internet community.<b=
r>
It does not specify an Internet standard of any kind. Distribution of<br>
this memo is unlimited.<br>
<br>
This announcement is sent to the IETF-Announce and rfc-dist lists.<br>
To subscribe or unsubscribe, see<br>
=C2=A0 <a href=3D"http://www.ietf.org/mailman/listinfo/ietf-announce" targe=
t=3D"_blank">http://www.ietf.org/mailman/listinfo/ietf-announce</a><br>
=C2=A0 <a href=3D"http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" =
target=3D"_blank">http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist</=
a><br>
<br>
For searching the RFC series, see <a href=3D"http://www.rfc-editor.org/sear=
ch" target=3D"_blank">http://www.rfc-editor.org/search</a><br>
For downloading RFCs, see <a href=3D"http://www.rfc-editor.org/rfc.html" ta=
rget=3D"_blank">http://www.rfc-editor.org/rfc.html</a><br>
<br>
Requests for special distribution should be addressed to either the<br>
author of the RFC in question, or to <a href=3D"mailto:rfc-editor@rfc-edito=
r.org">rfc-editor@rfc-editor.org</a>. =C2=A0Unless<br>
specifically noted otherwise on the RFC itself, all RFCs are for<br>
unlimited distribution.<br>
<br>
<br>
The RFC Editor Team<br>
Association Management Solutions, LLC<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Clint (JOATM=
ON) Chaplin<br>Principal Engineer<br>Standards &amp; Technology Enabling<br=
>Advanced Technology Lab<br>Samsung R&amp;D Institute America - Silicon Val=
ley
</div>

--047d7bb03f608adab404f6172bd7--


From nobody Wed Apr  2 16:16:10 2014
Return-Path: <suzworldwide@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37E901A041D for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 16:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 ycd2KdnY6cAV for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 16:16:02 -0700 (PDT)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) by ietfa.amsl.com (Postfix) with ESMTP id 651FE1A0416 for <ietf@ietf.org>; Wed,  2 Apr 2014 16:16:02 -0700 (PDT)
Received: by mail-qg0-f49.google.com with SMTP id e89so961478qgf.22 for <ietf@ietf.org>; Wed, 02 Apr 2014 16:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1j8eym6U2yqaYGrzQFSotkCeAKakyHGHizbB6DprtLA=; b=lWvt+bi7n0Sydm71rugNHzXx9H64w2XpHLulEV5tWf5uDJaArIXaWWzauciVaf82Zk E9u9gXpDRl5GSQ4hQW5+EWQvNmX1lc5jXtoJTbi9sLvOO+jSgNpQI66CBizkBZe2AUe4 qxilr+kd56uH6CoWjjXFqkWm5UXHF3MgqfWMEpt5RxpeYpCEYVusZi3u5MeX15gu6U2y xnb2aNFqFedXx/U+J8f64h7IzzNOF0h62l+nR3YMRhvHoJey2jFxo5SAWk7NqUv/bTN0 WMv01MwbrCX+9Ug41DzoCt8St6KMmTR0Qt6uZkICrlueMTP0DDj8m3JcrdQ+Jp2erz0B f3+A==
X-Received: by 10.140.36.77 with SMTP id o71mr3565617qgo.25.1396480558257; Wed, 02 Apr 2014 16:15:58 -0700 (PDT)
Received: from ?IPv6:2601:6:3a80:77e:6475:9ee9:6848:262? ([2601:6:3a80:77e:6475:9ee9:6848:262]) by mx.google.com with ESMTPSA id g92sm4511553qge.7.2014.04.02.16.15.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 02 Apr 2014 16:15:57 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Suzanne Woolf <suzworldwide@gmail.com>
In-Reply-To: <E987419F-495E-4AA7-AD1C-26122486D9EF@nominum.com>
Date: Wed, 2 Apr 2014 19:15:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0264E354-7040-4AF2-9F90-873332F03C59@gmail.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com> <CAMm+LwhNS-iKuzSCb0dhBypVFVzmi7HCZFvGNGExL5WtJ1jhsg@mail.gmail.com> <59C504C7-9E84-4CE8-B46D-A5E90329C0C8@gmail.com> <1396447162.15324.7725.camel@mightyatom> <E987419F-495E-4AA7-AD1C-26122486D9EF@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ilhnUgVonrwCjnNt8Mqp_AFcxm4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 23:16:07 -0000

On Apr 2, 2014, at 10:12 AM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Apr 2, 2014, at 9:59 AM, Elwyn Davies <elwynd@dial.pipex.com> =
wrote:
>> .. and of course the rancid yak butter...
>=20
> It's better if the yak butter isn't rancid.
>=20
> Anyway, these are all good suggestions for =
draft-ietf-tcoff-rfc7168bis.   Is anyone interested in forming a BOF?
>=20
Yeah, sounds like we have some i18n issues=85.until the politicians get =
involved, and then it's an "internet governance" problem=85.




From nobody Wed Apr  2 16:43:11 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DCF91A0007; Wed,  2 Apr 2014 16:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 URNVS9Uiy82V; Wed,  2 Apr 2014 16:43:04 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id E6B3A1A000E; Wed,  2 Apr 2014 16:43:02 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1C8491B83E9; Wed,  2 Apr 2014 16:42:59 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id DD396190043; Wed,  2 Apr 2014 16:42:58 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Apr 2014 16:42:58 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com>
Date: Wed, 2 Apr 2014 19:42:57 -0400
Content-Transfer-Encoding: 7bit
Message-ID: <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com>
To: Clint Chaplin <clint.chaplin@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uFLCieZO4hAd5v7PvL4JzTU1EMg
Cc: drafts-update-ref@iana.org, rfc-dist@rfc-editor.org, "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement list <ietf-announce@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 23:43:09 -0000

On Apr 2, 2014, at 6:54 PM, Clint Chaplin <clint.chaplin@gmail.com> wrote:
> Will there be an option for not-tea?

No.   You can't have tea and not-tea.



From nobody Wed Apr  2 17:02:36 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08A4F1A0413 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:02:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 osF2_SqRa6EN for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:02:28 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA5A1A000D for <ietf@ietf.org>; Wed,  2 Apr 2014 17:02:28 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WVV6T-0008hg-UE; Wed, 02 Apr 2014 20:01:57 -0400
Date: Wed, 02 Apr 2014 20:01:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <ted.lemon@nominum.com>, Clint Chaplin <clint.chaplin@gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Message-ID: <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
In-Reply-To: <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/g6ygAok47MQ0l9YVuDuVnZLYvag
Cc: drafts-update-ref@iana.org, rfc-dist@rfc-editor.org, ietf@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 00:02:33 -0000

--On Wednesday, April 02, 2014 19:42 -0400 Ted Lemon
<ted.lemon@nominum.com> wrote:

> On Apr 2, 2014, at 6:54 PM, Clint Chaplin
> <clint.chaplin@gmail.com> wrote:
>> Will there be an option for not-tea?
> 
> No.   You can't have tea and not-tea.

At least until you answer the question "when is tea not tea" in
a satisfactory way.  For example, the stuff that comes
identified as tea but arrives in bags in many bad restaurants
(and others that should know better), is pretty clearly not tea
but it is less clear whether it is not-tea or not.






From nobody Wed Apr  2 17:29:42 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783321A0413 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:29:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 meilHQ_tJ94c for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:29:36 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 132951A0028 for <ietf@ietf.org>; Wed,  2 Apr 2014 17:29:36 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id z10so937530pdj.4 for <ietf@ietf.org>; Wed, 02 Apr 2014 17:29:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=4f6+ZcXTjUQuBYVgNSXxA/qob7cSzxOdXxDG/9Yih4A=; b=vu5R1AwAyMhKsfi0mLY6ubF/Mq0D/VlKh0rbS+fY0XvVakjuQt1PPekSDIkFPq2nSn 0piUf56VyHnGThVVn/rmvDyDkww8aMAOqnTQIGZhAzxVqmryGKlRIUzAYD/q6gMOIr08 LX+QNTKXyPxwvCVAWCzZW4t/5u4tKGX++oI+lhIGF2G/fcj5wmkMKrAm9M5PRuQsopET QDKmcZUBQfx7RYwUm0sNrxUxdKW8ghc55NLg3a2g6sWITJbDRhTsrSBsEiGKmiXNDUsR vkrVrRWiHwJACDKApfTNhrzgd2vrM0AAnj97RRIRshAtnYmVatc3tN/n/MmGGYUpjL/B k4NA==
X-Received: by 10.68.193.100 with SMTP id hn4mr3661436pbc.50.1396484972228; Wed, 02 Apr 2014 17:29:32 -0700 (PDT)
Received: from [192.168.178.23] (89.195.69.111.dynamic.snap.net.nz. [111.69.195.89]) by mx.google.com with ESMTPSA id xk3sm7076494pbb.65.2014.04.02.17.29.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 02 Apr 2014 17:29:31 -0700 (PDT)
Message-ID: <533CAB6F.5060108@gmail.com>
Date: Thu, 03 Apr 2014 13:29:35 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com> <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
In-Reply-To: <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3x6oAdLOtI_o38M-Tw8Z0hdXY-o
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 00:29:40 -0000

On 03/04/2014 13:01, John C Klensin wrote:
> 
> --On Wednesday, April 02, 2014 19:42 -0400 Ted Lemon
> <ted.lemon@nominum.com> wrote:
> 
>> On Apr 2, 2014, at 6:54 PM, Clint Chaplin
>> <clint.chaplin@gmail.com> wrote:
>>> Will there be an option for not-tea?
>> No.   You can't have tea and not-tea.
> 
> At least until you answer the question "when is tea not tea" in
> a satisfactory way.  For example, the stuff that comes
> identified as tea but arrives in bags in many bad restaurants
> (and others that should know better), is pretty clearly not tea
> but it is less clear whether it is not-tea or not.

RFC 7169 describes a situation where TRUE and FALSE might mean the
same thing. I can't see, therefore, why tea and not-tea cannot
be simultaneously true (or false).

In the supermarket the other day, I was handed a free sample
of Red Bush Tea, which is clearly not tea. I do not know
whether it is not-tea.

   Brian


From nobody Wed Apr  2 17:42:07 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 766A11A0435 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:42:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.141
X-Spam-Level: 
X-Spam-Status: No, score=-0.141 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=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 ysdrRtTzEbgl for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:42:01 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0BF1A0432 for <ietf@ietf.org>; Wed,  2 Apr 2014 17:42:01 -0700 (PDT)
Received: from mx1.yitter.info (c-75-69-155-67.hsd1.nh.comcast.net [75.69.155.67]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 99DB68A031 for <ietf@ietf.org>; Thu,  3 Apr 2014 00:41:56 +0000 (UTC)
Date: Wed, 2 Apr 2014 20:41:54 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Someone should do some work (was Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA))
Message-ID: <20140403004154.GF56668@mx1.yitter.info>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com> <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/510Blhumym7dcUs6JfF7Dtq4uc8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 00:42:05 -0000

On Wed, Apr 02, 2014 at 08:01:52PM -0400, John C Klensin wrote:
> (and others that should know better), is pretty clearly not tea
> but it is less clear whether it is not-tea or not.

There is evidently an opportunity for an intuitionistic state machine
here.  In intuitionism, as I'm sure everyone is fully aware, the law
of excluded middle and double-negation are both rejected as axioms
(mostly because of the principle of constructive provability.
Intuitionism is not a 2-value logic, and may not be a finite-value
logic).

I think it would be fun to write ABNF for this system.  Or more
exactly, I think it would be fun if someone else did that.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Wed Apr  2 17:52:27 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B00F71A0426 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:52:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 eReB18_opVH6 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:52:20 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 5FE091A0436 for <ietf@ietf.org>; Wed,  2 Apr 2014 17:52:20 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 827C51B83EC for <ietf@ietf.org>; Wed,  2 Apr 2014 17:52:16 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 5036B190043; Wed,  2 Apr 2014 17:52:16 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Apr 2014 17:52:16 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
Date: Wed, 2 Apr 2014 20:52:12 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <6588D887-46A0-46BC-97CD-F7BB2F3D9270@nominum.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com> <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ni8JAeK8FCf3pbNGfkesOsOR5Hc
Cc: drafts-update-ref@iana.org, RFC Errata System <rfc-editor@rfc-editor.org>, rfc-dist@rfc-editor.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 00:52:24 -0000

On Apr 2, 2014, at 8:01 PM, John C Klensin <john-ietf@jck.com> wrote:
> For example, the stuff that comes
> identified as tea but arrives in bags in many bad restaurants
> (and others that should know better), is pretty clearly not tea
> but it is less clear whether it is not-tea or not.

What it is is almost, but not completely, unlike tea.   Still services =
as a good source of randomness, as long as it's nice and hot.


From nobody Wed Apr  2 17:55:25 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18FC01A0037 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 kdnVeR_hQ_8u for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 17:55:18 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 91A671A0426 for <ietf@ietf.org>; Wed,  2 Apr 2014 17:55:18 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D99FB1B83EC for <ietf@ietf.org>; Wed,  2 Apr 2014 17:55:14 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id CEFC6190043; Wed,  2 Apr 2014 17:55:14 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Apr 2014 17:55:14 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <533CAB6F.5060108@gmail.com>
Date: Wed, 2 Apr 2014 20:55:11 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <9D6790E7-7FFA-4627-80B7-7A35FAFC10CA@nominum.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com> <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com> <533CAB6F.5060108@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KK7hHDb_gth1u2m4WsS3m3vozV0
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 00:55:23 -0000

On Apr 2, 2014, at 8:29 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> In the supermarket the other day, I was handed a free sample
> of Red Bush Tea, which is clearly not tea. I do not know
> whether it is not-tea.

As I mentioned to someone privately earlier, not-tea is the logical =
complement of tea, which is to say the complete set of all things that =
are not tea.   Hence, Rooibos tea is not not-tea, although it is not =
tea.


From nobody Wed Apr  2 18:01:38 2014
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 328FF1A042F for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 18:01:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 41HswPoQ47uk for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 18:01:31 -0700 (PDT)
Received: from qmta06.westchester.pa.mail.comcast.net (qmta06.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:56]) by ietfa.amsl.com (Postfix) with ESMTP id 9A98E1A001C for <ietf@ietf.org>; Wed,  2 Apr 2014 18:01:31 -0700 (PDT)
Received: from omta13.westchester.pa.mail.comcast.net ([76.96.62.52]) by qmta06.westchester.pa.mail.comcast.net with comcast id l7Sx1n00817dt5G56D1T7l; Thu, 03 Apr 2014 01:01:27 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta13.westchester.pa.mail.comcast.net with comcast id lD1T1n0071KKtkw3ZD1TSE; Thu, 03 Apr 2014 01:01:27 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s3311QXX006162 for <ietf@ietf.org>; Wed, 2 Apr 2014 21:01:26 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s3311QtT006161; Wed, 2 Apr 2014 21:01:26 -0400
Date: Wed, 2 Apr 2014 21:01:26 -0400
Message-Id: <201404030101.s3311QtT006161@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <CAEP5zKSOcSgBLGOk4xGspvaaF8=FXqcXpt-kOX2r-1Z1HA4kVg@mail.gmail.com> (chaitanyabd@gmail.com)
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com> <CAEP5zKSOcSgBLGOk4xGspvaaF8=FXqcXpt-kOX2r-1Z1HA4kVg@mail.gmail.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1396486887; bh=znh5LntByUM4ne1ZJWR6kDTir/PHCmHtxdeckqckITc=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=qzaRrivpvatB/45fMPWhGczopZuxzvPb+CMVrOs8kNuOPoJKsThsBQi4baJYOh/c+ oagMHUt8e3hBqxoBwq2PNQTnFpNL1MiWUVJyV45DPVyW4nJmnFNE7qZphmYL4HwvJ7 LcYE/uxkfuW9+yqa7whOZSxdbKYZs85B0m+pUAm3+b43sEZEnQCKo9cHl1jqRagdjl eZ0JWrrcgJ16gWRaJedEE6WNd14wnNWrllko+xuJBkbOQlzkQz4vsI7NHvi89vJZPY 7l5Jmidm5F+UjJ7SMleO38tHTNg3Cc9vfr/wAqFu1TX0Ahb+XSfq60wGdi5U78r2al pANqiUZ7NXe2A==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kNscqRJeFBmzYMTWfpFMQmGFtSw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 01:01:36 -0000

> From: Chaitanya Dhareshwar <chaitanyabd@gmail.com>
> 
> On Wed, Apr 2, 2014 at 8:46 AM, Ole Jacobsen <olejacobsen@me.com> wrote:
> 
> > As any Brit will tell you: ice has absolutely NOTHING to do with tea, so
> > it would be out of scope.
> >
> > Sat-too-long-and-is-still-hot is, if I recall, known as "stewed" and
> > anyone responsible faces possible deportation from the UK. A very serious
> > matter indeed, almost as serious as refusing to obey the rules of a queue.
> 
> I would beg to differ, I love my Iced Tea (ref:
> http://en.wikipedia.org/wiki/Iced_tea)
> 
> Further as the Internet Engineering Tea Force we must ensure all
> possibilities are covered... Even if its not common within a region/culture
> doesn't mean its not used elsewhere.

We definitely need to avoid the growth of national extensions of
HTCPCP-TEA by including the features that are being used already!

Dale


From nobody Wed Apr  2 19:44:14 2014
Return-Path: <clint.chaplin@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A96BA1A0084; Wed,  2 Apr 2014 19:44:11 -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, SPF_PASS=-0.001] autolearn=ham
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 R-kFH3pNUljm; Wed,  2 Apr 2014 19:44:05 -0700 (PDT)
Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 714A21A007B; Wed,  2 Apr 2014 19:44:05 -0700 (PDT)
Received: by mail-wi0-f171.google.com with SMTP id q5so8259349wiv.4 for <multiple recipients>; Wed, 02 Apr 2014 19:44:01 -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:content-type; bh=HlaXrztyqOZDizGa+4B0pRtuLRh+vRJ51e1nRt9hOhY=; b=Cn1BIzYLOugOmr7EOIOY0cdcHE3pRB+a3ItwywE8wZJ0cOS4qk2VaMqHCCJMo8Y2cn zIemACRYx9UBXGWbLiMVZjNdbYLN2oc0sQggSDSbGmP19HSMC+bIkjs2m+wqyPcyi+Sx vka9eaeKRrlf+2r/DVdwjmA5s148dKZHSZ+1H+k6kHUQjzR3vizzmMq8cB7AB7X3kmEs fGdLNIbpExB3wSZ6XQcIyXty9rasAaMcBzJkhhDSXwXPcg0qsQ/Oo2p/QYYOZnptraz7 8Og6jL6RA2rt3gd5dDpbJY6iHKgQHQc1/rSLsKd0Iyvb42AniiH1Fs0J1s9aZRt7h9lS w4pQ==
MIME-Version: 1.0
X-Received: by 10.194.189.80 with SMTP id gg16mr5513914wjc.84.1396493040859; Wed, 02 Apr 2014 19:44:00 -0700 (PDT)
Received: by 10.194.235.10 with HTTP; Wed, 2 Apr 2014 19:44:00 -0700 (PDT)
In-Reply-To: <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com>
Date: Wed, 2 Apr 2014 19:44:00 -0700
Message-ID: <CADn-GtgnEOyr2zGwguJc9Tqu15ZVGaYNvdAvFuWaeSw2R1sHiw@mail.gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Clint Chaplin <clint.chaplin@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7bb03f9ca1bf8a04f61a5ff2
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Jln_ISOrbbCt4t47CHpD-XNckOI
Cc: drafts-update-ref@iana.org, rfc-dist@rfc-editor.org, "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement list <ietf-announce@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 02:44:11 -0000

--047d7bb03f9ca1bf8a04f61a5ff2
Content-Type: text/plain; charset=UTF-8

Well, unless you have removed that little bit of common sense from your
brain, then you can have both.

Yes, I know it should have been no-tea.  How many people have any clue what
I am referring to?


On Wed, Apr 2, 2014 at 4:42 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Apr 2, 2014, at 6:54 PM, Clint Chaplin <clint.chaplin@gmail.com> wrote:
> > Will there be an option for not-tea?
>
> No.   You can't have tea and not-tea.
>
>
>


-- 
Clint (JOATMON) Chaplin
Principal Engineer
Standards & Technology Enabling
Advanced Technology Lab
Samsung R&D Institute America - Silicon Valley

--047d7bb03f9ca1bf8a04f61a5ff2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Well, unless you have removed that little bit of common se=
nse from your brain, then you can have both.<div><br></div><div>Yes, I know=
 it should have been no-tea. =C2=A0How many people have any clue what I am =
referring to?</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed,=
 Apr 2, 2014 at 4:42 PM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mailto:=
ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.com</a>&gt;</spa=
n> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On Apr 2, 2014, at 6:54 PM, =
Clint Chaplin &lt;<a href=3D"mailto:clint.chaplin@gmail.com">clint.chaplin@=
gmail.com</a>&gt; wrote:<br>

&gt; Will there be an option for not-tea?<br>
<br>
</div>No. =C2=A0 You can&#39;t have tea and not-tea.<br>
<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>Clint (JOATM=
ON) Chaplin<br>Principal Engineer<br>Standards &amp; Technology Enabling<br=
>Advanced Technology Lab<br>Samsung R&amp;D Institute America - Silicon Val=
ley
</div>

--047d7bb03f9ca1bf8a04f61a5ff2--


From nobody Wed Apr  2 19:56:55 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32EDC1A0089; Wed,  2 Apr 2014 19:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 t_FpP2TIiavd; Wed,  2 Apr 2014 19:56:46 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 9FCBA1A008D; Wed,  2 Apr 2014 19:56:46 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AB98C1B8067; Wed,  2 Apr 2014 19:56:42 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 76525190043; Wed,  2 Apr 2014 19:56:42 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 2 Apr 2014 19:56:42 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CADn-GtgnEOyr2zGwguJc9Tqu15ZVGaYNvdAvFuWaeSw2R1sHiw@mail.gmail.com>
Date: Wed, 2 Apr 2014 22:56:39 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <4E7458E6-66EE-4765-9713-953EE577FCDA@nominum.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com> <CADn-GtgnEOyr2zGwguJc9Tqu15ZVGaYNvdAvFuWaeSw2R1sHiw@mail.gmail.com>
To: Clint Chaplin <clint.chaplin@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ncpk7R59BCsevJ1yhzZL2AJtXxU
Cc: drafts-update-ref@iana.org, rfc-dist@rfc-editor.org, "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement list <ietf-announce@ietf.org>, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 02:56:51 -0000

On Apr 2, 2014, at 10:44 PM, Clint Chaplin <clint.chaplin@gmail.com> =
wrote:
> Yes, I know it should have been no-tea.  How many people have any clue =
what I am referring to?

Quite a few of us, I suspect.

If only I could figure out where I put that thing my aunt gave me which =
I don't know what it is...



From nobody Thu Apr  3 01:11:04 2014
Return-Path: <julian.reschke@gmx.de>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 827E81A00B2; Thu,  3 Apr 2014 01:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
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 RVbk2aicGxfN; Thu,  3 Apr 2014 01:10:48 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id DA9D51A00A3; Thu,  3 Apr 2014 01:10:44 -0700 (PDT)
Received: from [192.168.2.117] ([93.217.104.143]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0Md3Eg-1Wnq4M0BwA-00IBst; Thu, 03 Apr 2014 10:10:28 +0200
Message-ID: <533D176C.3010600@gmx.de>
Date: Thu, 03 Apr 2014 10:10:20 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mohammed serrhini <serrhini@mail.ru>, iab@iab.org, ietf@ietf.org,  wgchairs@ietf.org, iesg@ietf.org, iad@ietf.org
Subject: Re: Fwd: Re[2]: IAOC Seeks Community Input on IETF Website Revamp SOW
References: <1395020361.178909826@f402.i.mail.ru>
In-Reply-To: <1395020361.178909826@f402.i.mail.ru>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:mbCcdQ+6ETSlzZU5SvJTSVzf7n7DYIb5m5z4zMkxXTHLnca3Vi0 PVN+tXoIycNl/GHijA16ga3JntRXlbUejaLDevL/Aal9v5BxZVZUHyhtVNgclzvU9FS8sKx yFU8FKhV+fXjXoBbksG/owh+DEbpNVxOV1C6b0ktMR/Smf8RyMcDnNthdF9hs44gOLfpo8x fg2lyBe0a+pcm2Tal/EPQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/w5cN5XFdvTL4BaLpgPXO4Ah2RDY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 08:10:54 -0000

On 2014-03-17 02:39, mohammed serrhini wrote:
>
>
> Hello
> to Modernize the web site visual design  the main page must be not
> scrollable as it is now.

-1. There is no problem with "scrollable" content.

> 7.d.vii: "For pages that require the use of applets, a link to the page
> where the user can obtain the plug-ins will be provided. some plugins
> are known as 0 days attacks vulnerability .
> I propose also a link to update this plugins if out of date.

It simply shouldn't use plugins or applets.

> for 2 .c  and e.i .Responsive Design: I propose for mobile devices that
> mobile version of the IETF web site must be developed and accessible
> from the link m.ietf.org

I would avoid that until proven to be needed.

> for 5. h. Events calendar must be in the form of calendar months table
> with selection button of years and month to allow users to select date
> quickly and to view the full IETF agenda By Month and by year

Actually, event information should be available as a calendar resource 
(ics).

Best regards, Julian


From nobody Thu Apr  3 02:14:17 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 096BB1A010E for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 02:14:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.099
X-Spam-Level: 
X-Spam-Status: No, score=0.099 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
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 qXzaz_GrRUB2 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 02:14:12 -0700 (PDT)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0017.outbound.protection.outlook.com [213.199.154.17]) by ietfa.amsl.com (Postfix) with ESMTP id 89DAB1A008E for <ietf@ietf.org>; Thu,  3 Apr 2014 02:14:11 -0700 (PDT)
Received: from AMXPRD0111HT003.eurprd01.prod.exchangelabs.com (157.56.250.117) by DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) with Microsoft SMTP Server (TLS) id 15.0.908.10; Thu, 3 Apr 2014 09:14:06 +0000
Message-ID: <009601cf4f1c$d6e145c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Mukom Akong T. <mukom.tamon@gmail.com>
References: <5328F67A.2070605@att.com> <CAHDzDLCGKhX98=y=-_i9sjV8DzmzXQr=Y5TrnkPNK-G=XMASPA@mail.gmail.com>
Subject: Re: it's been a while since we discussed the use of PowerPoint in meetings
Date: Thu, 3 Apr 2014 10:12:20 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.250.117]
X-ClientProxiedBy: AM3PR07CA004.eurprd07.prod.outlook.com (10.242.16.44) To DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153)
X-Forefront-PRVS: 0170DAF08C
X-Forefront-Antispam-Report: =?utf-8?B?U0ZWOk5TUE07U0ZTOigxMDAwOTAwMSkoNjAwOTAwMSkoNDI4MDAxKSg1MTcw?= =?utf-8?B?NDAwNSkoMzc3NDU0MDAzKSgxOTkwMDIpKDE4OTAwMikoMjQ0NTQwMDIpKDEz?= =?utf-8?B?NDY0MDAzKSg3Njc5NjAwMSkoNzY0ODIwMDEpKDE1Mzk1NzI1MDAzKSg3Njc4?= =?utf-8?B?NjAwMSkoOTcxODYwMDEpKDYyOTY2MDAyKSg5NzMzNjAwMSkoODA5NzYwMDEp?= =?utf-8?B?KDk1NDE2MDAxKSg1MDQ2NjAwMikoMTUxOTg2NjUwMDMpKDk1NjY2MDAzKSg1?= =?utf-8?B?MTg1NjAwMSkoODc5NzYwMDEpKDQzOTYwMDEpKDg4MTM2MDAyKSg0MjE4NjAw?= =?utf-8?B?NCkoNDQ3MzYwMDQpKDg1MzA2MDAyKSg2OTIyNjAwMSkoNzQ3MDYwMDEpKDkw?= =?utf-8?B?MTQ2MDAxKSg1MzgwNjAwMSkoNjEyOTYwMDIpKDk4Njc2MDAxKSg3NzA5NjAw?= =?utf-8?B?MSkoOTkzOTYwMDIpKDc3MTU2MDAxKSg0OTg2NjAwMSkoNzQ4NzYwMDEpKDUw?= =?utf-8?B?MjI2MDAxKSg1MDk4NjAwMSkoODcyODYwMDEpKDg3MjY2MDAxKSg4MTU0MjAw?= =?utf-8?B?MSkoMTY2MDEwNzUwMDMpKDgxMzQyMDAxKSg0NjEwMjAwMSkoMTQ0OTYwMDEp?= =?utf-8?B?KDgzMDcyMDAyKSg2MjIzNjAwMikoNjYwNjYwMDEpKDE1MjAyMzQ1MDAzKSgx?= =?utf-8?B?OTU4MDQwNTAwMSkoMTU5NzU0NDUwMDYpKDQ0NzE2MDAyKSg3OTEwMjAwMSko?= =?utf-8?B?NjM2OTYwMDIpKDc0NjYyMDAxKSgzMTk2NjAwOCkoNzQ1MDIwMDEpKDU5NzY2?= =?utf-8?B?MDAxKSg3Nzk4MjAwMSkoMjA3NzYwMDMpKDQ3Nzc2MDAzKSg0NzQ0NjAwMiko?= =?utf-8?B?OTM1MTYwMDIpKDY1ODE2MDAxKSg4NTg1MjAwMykoOTMxMzYwMDEpKDgzMzIy?= =?utf-8?B?MDAxKSgyMzY3NjAwMikoNTY4MTYwMDUpKDE5NTgwMzk1MDAzKSgzMzY0NjAw?= =?utf-8?B?MSkoODk5OTYwMDEpKDQ3NzM2MDAxKSg0Nzk3NjAwMSkoODAwMjIwMDEpKDU0?= =?utf-8?B?MzE2MDAyKSg5NDMxNjAwMikoOTI1NjYwMDEpKDk0OTQ2MDAxKSg3NDM2NjAw?= =?utf-8?B?MSkoODQzOTIwMDEpKDkzOTE2MDAyKSg5MjcyNjAwMSkoODYzNjIwMDEpKDU2?= =?utf-8?B?Nzc2MDAxKSg3NDQxNjAwMSkoNzcyNjAwMSk7RElSOk9VVDtTRlA6MTEwMTtT?= =?utf-8?B?Q0w6MTtTUlZSOkRCNFBSMDdNQjI1MjtIOkFNWFBSRDAxMTFIVDAwMy5ldXJw?= =?utf-8?B?cmQwMS5wcm9kLmV4Y2hhbmdlbGFicy5jb207RlBSOkNGNDNGMUFFLkFGRjI2?= =?utf-8?B?RkUxLkZFQzM1MzgzLkVFODExNDkuMjA0NzI7TUxWOm5vdjtQVFI6SW5mb05v?= =?utf-8?Q?Records;A:0;MX:1;LANG:en;?=
Received-SPF: None (: btconnect.com does not designate permitted sender hosts)
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/r8oe9pVic1mAW3Fp6rYEnY-ZWNE
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 09:14:16 -0000

----- Original Message -----
From: "Mukom Akong T." <mukom.tamon@gmail.com>
To: "Tony Hansen" <tony@att.com>
Cc: "IETF Discussion" <ietf@ietf.org>
Sent: Monday, March 31, 2014 3:54 AM

If a presenter is bad, no tool can rescue him (PowerPoint or Keynote or
Prezi or etc etc). The problem is that most people were never taught (or
took the time to learn) how to present to an audience. There are really
simple rules of effective presentation and the tool (PowerPoint vs
Keynote
etc) is insignificant .

What the organisers could do to help speakers is to present presentation
guidelines for speakers

<tp>

So true, and IETF89 provided plenty of case studies thereon.

But you do omit what I would see as rule zero of any presentation -
introduce yourself; not your life history, not all those I-Ds you have
authored, just a  statement of your name and, if it is relevant to what
you are about to say, the context within which you are involved with the
topic.  Not doing so is a powerful message to the audience, along the
lines of if you don't know this already, you do not belong here:-(

In the same vein, I was surprised at how many Working Groups at IETF89
like to be anonymous; walk into a room, hoping to have navigated to the
correct one, to be greeted by a blank screen and then someone - who? -
starts talking about 'Note Well'.  You could be anywhere:-)

Tom Petch


a) No more than X slides per 15 minutes

b) Minimum font size (I personally don't go below 25 for bullets and 18
for
text on a diagram)

c) Good visuals (as most of the talks might be about networking ... the
organisers could commission a designer to provide standard elements to
be
used in presentations ... router, switch, server etc. But then you can
get
all of that from free from openclipart.org)

d) A ration of text : graphic slides. (I personally try to have every
other
slide be graphic/illustration .... but I'd say 1 graphic slide to every
4
is ok)

e) Maximum number of bullets points per slide ( 5 - 7 max)

For those who might be interested. Nancy Duarte (a presentations expert)
released an online copy of her book "Resonate" for free. Find it at
http://resonate.duarte.com

And yes .... slides are not the only way to present and not every
presentation must be in the format of slides.



On Wed, Mar 19, 2014 at 5:44 AM, Tony Hansen <tony@att.com> wrote:

> I ran into this article and felt it worth sharing:
>
> Physicists, Generals And CEOs Agree: Ditch The PowerPoint
> http://www.npr.org/blogs/alltechconsidered/2014/03/16/
> 288796805/physicists-generals-and-ceos-agree-ditch-the-powerpoint
>
> Actually, the article is not all one sided -- it does also discuss
some
> times when they feel that PowerPoint *is* useful.
>
>     Tony Hansen
>
>


--

Mukom Akong T.

http://about.me/perfexcellence |  twitter: @perfexcellent
------------------------------------------------------------------------
------------------------------------------------------------------
â€œWhen you work, you are the FLUTE through whose lungs the whispering of
the
hours turns to MUSIC" - Kahlil Gibran
------------------------------------------------------------------------
-------------------------------------------------------------------


From nobody Thu Apr  3 03:48:44 2014
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 821481A0221; Thu,  3 Apr 2014 03:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 WqO9BC2H-6pk; Thu,  3 Apr 2014 03:48:35 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id 4FB061A0232; Thu,  3 Apr 2014 03:48:29 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id l18so1657832wgh.7 for <multiple recipients>; Thu, 03 Apr 2014 03:48:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=yRyXLy+JPtECGEufnKiq9TViy2IaUAgS9WbWZPkaDQ4=; b=KFx8wz9wOrn3f1G9Jg33NOT809kEoPd5mUpauKdNODk6srHBObjjqAq7/aUS2urfks 6uhJE8v1mIMTvkNszPM4E9zeYOQxDi89OLThPUuhCi8DA+RNUoJAWlkIdhydwg0mhfFV 8uhWRlT5DGiMw6EzkITlehT0sTwni3PCnLT3+aRtKcOmTMRgdxVaEr1UTIR6pf2o2KWG SoLjdo+I3GgSRpG0+jg7w3ulQq7U0/w2Agoa+f0T9OLfoqWvA1pPqiZoVOEPDOdo9CI/ EGpbSiDLuCfFgdub2Qg/tRanLk33RTVvMchQW/2zd/abWIuOLjkszZbhnLM2CBHr896o SS3Q==
X-Received: by 10.180.7.198 with SMTP id l6mr628908wia.52.1396522105287; Thu, 03 Apr 2014 03:48:25 -0700 (PDT)
Received: from RoniE (bzq-79-183-174-212.red.bezeqint.net. [79.183.174.212]) by mx.google.com with ESMTPSA id s46sm11190997ees.3.2014.04.03.03.48.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 03 Apr 2014 03:48:23 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-lsp-ping-ttl-tlv.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-mpls-lsp-ping-ttl-tlv-07
Date: Thu, 3 Apr 2014 13:48:18 +0300
Message-ID: <0a7d01cf4f2a$3b3cba10$b1b62e30$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0A7E_01CF4F43.608A8E50"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac9PKjjoTsJKpdiERKaL9DKHmOz8KQ==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NEYOpRdtcCe6FVH1678Z_HJu4GQ
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 10:48:39 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0A7E_01CF4F43.608A8E50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments you
may receive.

Document:  draft-ietf-mpls-lsp-ping-ttl-tlv-07

Reviewer: Roni Even

Review Date:2014-4-3

IETF LC End Date: 2014-4-7

IESG Telechat date: 

 

Summary: This draft is ready for publication as Standard track RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

In section 1 first paragraph "request packet to any another node" 

 


------=_NextPart_000_0A7E_01CF4F43.608A8E50
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><META =
HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 14 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:10.0pt;
	margin-left:0in;
	line-height:115%;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:Consolas;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue =
vlink=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><a =
name=3D"OLE_LINK1"></a><a name=3D"OLE_LINK2">I am the assigned Gen-ART =
reviewer for this draft. For background on Gen-ART, please see the FAQ =
at &lt;</a><a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
target=3D"_blank">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq=
</a>&gt;.<o:p></o:p></p><p class=3DMsoNormal>Please resolve these =
comments along with any other Last Call comments you may =
receive.<o:p></o:p></p><pre><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Document:&n=
bsp; </span><span =
style=3D'font-size:10.5pt'>draft-ietf-mpls-lsp-ping-ttl-tlv-07</span><spa=
n style=3D'color:black'><o:p></o:p></span></pre><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Reviewer: =
Roni Even<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Review =
Date:2014&#8211;4-3<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IETF LC =
End Date: 2014&#8211;4-7<o:p></o:p></span></p><p =
class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>IESG =
Telechat date: <o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Summary: =
This draft is ready for publication as Standard track RFC</span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>.<o:p></o:p=
></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Major =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>Minor =
issues:<o:p></o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoPlainText><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p>&nbsp;=
</o:p></span></p><p class=3DMsoNormal>Nits/editorial =
comments:<o:p></o:p></p><p class=3DMsoNormal>In section 1 first =
paragraph &#8220;request packet to any another node&#8221; =
<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0A7E_01CF4F43.608A8E50--


From nobody Thu Apr  3 07:32:18 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05F151A0211; Thu,  3 Apr 2014 07:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.892
X-Spam-Level: 
X-Spam-Status: No, score=-101.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 eQiS5n6TNRoe; Thu,  3 Apr 2014 07:31:57 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0187.outbound.protection.outlook.com [207.46.163.187]) by ietfa.amsl.com (Postfix) with ESMTP id 533061A020E; Thu,  3 Apr 2014 07:31:57 -0700 (PDT)
Received: from [192.168.0.34] (184.61.83.93) by BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20) with Microsoft SMTP Server (TLS) id 15.0.913.9; Thu, 3 Apr 2014 14:31:52 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Liaison Statement Improvements SOW for Community Input
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <20140324183422.4579.53478.idtracker@ietfa.amsl.com>
Date: Thu, 3 Apr 2014 10:31:41 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <B3589989-2FD8-4D88-9460-05B64645353B@isoc.org>
References: <20140324183422.4579.53478.idtracker@ietfa.amsl.com>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [184.61.83.93]
X-ClientProxiedBy: BLUPR01CA002.prod.exchangelabs.com (10.255.223.160) To BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20)
X-Forefront-PRVS: 0170DAF08C
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(428001)(243025003)(377454003)(51704005)(199002)(189002)(24454002)(51856001)(76796001)(54316002)(81816001)(80976001)(83072002)(76482001)(15202345003)(85852003)(77096001)(74366001)(46102001)(95666003)(4396001)(50226001)(98676001)(99396002)(56776001)(50986001)(97186001)(76786001)(59766001)(49866001)(47736001)(81686001)(47976001)(77982001)(97336001)(15975445006)(81342001)(92566001)(53806001)(82746002)(77156001)(79102001)(74502001)(50466002)(88136002)(19580405001)(92726001)(83322001)(19580395003)(69226001)(62966002)(85306002)(95416001)(93136001)(63696002)(47776003)(36756003)(87266001)(81542001)(94316002)(87286001)(93516002)(83716003)(66066001)(80022001)(42186004)(23746002)(33656001)(47446002)(74706001)(89996001)(86362001)(56816005)(31966008)(90146001)(74662001)(65816001)(74876001)(87976001)(93916002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB234; H:[192.168.0.34]; FPR:FCF8F21C.AC3A9719.70E39EAB.8AA6DA4D.203E1; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zyivcVKEqsq11EFJY0851wJni6M
Cc: iaoc@ietf.org, "iab@iab.org IAB" <iab@iab.org>, The IESG <iesg@ietf.org>, IETF Announcement list <ietf-announce@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 14:32:02 -0000

All;

A reminder that Community input is being sought for this Liaison =
Statement Improvements SOW
http://iaoc.ietf.org/documents/liaison-sow-03.pdf

Thanks
Ray

On Mar 24, 2014, at 2:34 PM, IETF Administrative Director <iad@ietf.org> =
wrote:

> The IAOC desires improvements to the liaison statement tracking =
capabilities in the datatracker to=20
> address community requests and to simplify ongoing maintenance of the =
related code.
>=20
> The community comment period ends 7 April 2014.  The IAOC will =
consider all comments received=20
> during this prior.
>=20
> Liaison relationships with other standards setting bodies are managed =
by the IAB. The processes for=20
> managing the relationships are detailed in RFC4052, and the procedures =
for handling liaison statements=20
> are detailed in RFC4053. The current liaison statement management tool =
(LSMT) began from the=20
> definitions in that RFC and the LMST has been improved through =
previous contracted development.=20
> Individuals using the tool must follow the guidelines in RFC4691.  =
Developers working on the liaison=20
> statement management section of the datatracker must be familiar with =
all three RFCs.=20
>=20
> SOW Deliverables / Tasks
>=20
> a.  Migrate the codebase and data to new models, refining the models =
as necessary.=20
> b.  Add history to liaison statements, capturing when they were =
received, posted, resent, approved, marked=20
> dead or modified.
> c.  Add Point of Contact email addresses for each body to be used as =
the default Response Contact.
> d.  Capture other SDOs identifiers for liaison statements.
> e.  Add =93Action Holder=94 email addresses to incoming liaison =
statements.
> f.  Add the ability for a liaison statement to reference multiple =
other liaison statements as related.
> g.  Allow a liaison statement to be sent from multiple bodies and sent =
to multiple bodies.
> h.  Add the concept of a =93dead=94 liaison statement, allowing an =
approver or the secretariat to remove a=20
> statement from the pending queue without posting it. Add a view to =
manage the set of dead liaison statements.
> i.  Add the ability to resend a liaison statement.
> j.  Improve search over posted liaison statements, searching all =
fields and allowing the results to be=20
> limited to a particular source and/or destination body and/or a =
particular time range. Facilitate browsing a=20
> series of related liaison statements as a =93thread=94.
> k.  Address known issues with the liaison statement entry form when =
used as the secretariat and when used=20
> as a liaison manager.
> l.  Make it easier to see which liaison statements still need action.
> m.  Ensure liaison statement approvers are notified when there is =
something to approve.
> n.  Remove the restriction against duplicate liaison statement titles.
> o.  Allow the set of attachments to a liaison statement to be edited. =
In particular allow an attachment to be=20
> deleted. Leave a record in the history for each editing event.
> p.  Improve test coverage, and ensure tests exercise the use cases =
detailed in this document.
>=20
> All information submitted in response to this announcement is =
voluntary and may be used in the=20
> development of the SOW.
>=20
> Thanks for your continuing advice and support.
>=20
> Ray Pelletier=20
> IETF Administrative Director=20
>=20


From nobody Thu Apr  3 08:09:56 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63B471A0383 for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 11:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=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 lgB0_cO4Ub4w for <ietf@ietfa.amsl.com>; Wed,  2 Apr 2014 11:41:57 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 73DBE1A037B for <ietf@ietf.org>; Wed,  2 Apr 2014 11:41:57 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 80430206D0; Wed,  2 Apr 2014 14:41:50 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aUBm-ngSmJor; Wed,  2 Apr 2014 14:41:46 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-50-177-27-27.hsd1.ma.comcast.net [50.177.27.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed,  2 Apr 2014 14:41:46 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 92B1481945; Wed,  2 Apr 2014 14:41:47 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Thierry Moreau <thierry.moreau@connotech.com>
Subject: Re: An RFC7169 use case (!)
References: <533C4624.50408@connotech.com>
Date: Wed, 02 Apr 2014 14:41:47 -0400
In-Reply-To: <533C4624.50408@connotech.com> (Thierry Moreau's message of "Wed,  02 Apr 2014 17:17:24 +0000")
Message-ID: <tsl4n2bfuac.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/viPejIACwT-GGnwgUEY5GqZkyCA
X-Mailman-Approved-At: Thu, 03 Apr 2014 08:09:52 -0700
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 Apr 2014 18:42:01 -0000

>>>>> "Thierry" == Thierry Moreau <thierry.moreau@connotech.com> writes:


    Thierry> It may me the first time that an April fool RFC is actually
    Thierry> useful.


Seems UTF-9 is more useful than this.


From nobody Thu Apr  3 09:21:53 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 449701A0239 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 09:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 5mhPA6i7ahXn for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 09:21:43 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4151A0268 for <ietf@ietf.org>; Thu,  3 Apr 2014 09:21:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 41FB1BE5C for <ietf@ietf.org>; Thu,  3 Apr 2014 17:21:36 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pVvknknENkab for <ietf@ietf.org>; Thu,  3 Apr 2014 17:21:36 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1D8C7BE39 for <ietf@ietf.org>; Thu,  3 Apr 2014 17:21:36 +0100 (IST)
Message-ID: <533D8A90.60309@cs.tcd.ie>
Date: Thu, 03 Apr 2014 17:21:36 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: Security for various IETF services
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kQTFzgf-OndQI_lqDgGCD4IpkTM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 16:21:49 -0000

Hi all,

>From time to time the issue of how to secure IETF services
comes up e.g. whether to turn on TLS for some IETF web server
or jabber or mail etc.

The most recent such was a request to turn on HSTS [1] for
the IETF web site, which I don't think we can do without
breaking old tools etc. Nonetheless we would like to turn
on things like TLS more often going forward as seemed to
me to be the outcome of a long thread on here late last
year.

So, the IESG are considering the following as an IESG
statement to offer some guidance about this:

"The IETF are committed to providing secure and privacy
friendly access to information via the web, mail, jabber
and other services. While most (but not all) data on IETF
services is public, nonetheless access to that data
should use best practices for security and privacy.
However, as there are numerous legacy tools that have been
built that require access via cleartext, the IETF will
continue to allow such access so as not to break such
tooling. New services will however generally only be made
available in ways that use security protocols such as
TLS."

If you have wordsmithing changes to suggest please just send
those to me or the iesg. More substantive comments should go
here I guess. I hope the only bit worth discussing (except
for the few folks who would rather we do none of this;-)
might be the last sentence.

A few weeks after any discussion here dies down I'll put the
resulting text on an IESG telechat for approval if that seems
like the right thing to do.

Thanks,
S

[1] https://tools.ietf.org/html/rfc6797



From nobody Thu Apr  3 14:21:22 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD5781A02AF for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 14:21:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 xxQTA9dc9B72 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 14:21:16 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.173]) by ietfa.amsl.com (Postfix) with ESMTP id C06151A02A4 for <ietf@ietf.org>; Thu,  3 Apr 2014 14:21:15 -0700 (PDT)
Received: from [195.245.230.131:19405] by server-13.bemta-3.messagelabs.com id 1A/4C-18692-6C0DD335; Thu, 03 Apr 2014 21:21:10 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-78.messagelabs.com!1396560070!23709763!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20804 invoked from network); 3 Apr 2014 21:21:10 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-14.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 3 Apr 2014 21:21:10 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Thu, 3 Apr 2014 22:21:09 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <ietf@ietf.org>
Date: Thu, 3 Apr 2014 22:18:06 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9PWOTvs71UBGOqTsyzT3b1lZ7UEwAKU/Xc
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie>
In-Reply-To: <533D8A90.60309@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/k2KesyFLX8yRoVztIWh9njxO8E8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 21:21:21 -0000

"nonetheless access to that data
should use best practices for security and privacy."

why?

" New services will however generally only be made
available in ways that use security protocols such as
TLS."

again, why?

secured access is limited access, which is counter
to the goal of an open Internet.

thanks

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stephen Farrell [stephen.fa=
rrell@cs.tcd.ie]
Sent: 03 April 2014 17:21
To: IETF-Discussion
Subject: Security for various IETF services

Hi all,

>From time to time the issue of how to secure IETF services
comes up e.g. whether to turn on TLS for some IETF web server
or jabber or mail etc.

The most recent such was a request to turn on HSTS [1] for
the IETF web site, which I don't think we can do without
breaking old tools etc. Nonetheless we would like to turn
on things like TLS more often going forward as seemed to
me to be the outcome of a long thread on here late last
year.

So, the IESG are considering the following as an IESG
statement to offer some guidance about this:

"The IETF are committed to providing secure and privacy
friendly access to information via the web, mail, jabber
and other services. While most (but not all) data on IETF
services is public, nonetheless access to that data
should use best practices for security and privacy.
However, as there are numerous legacy tools that have been
built that require access via cleartext, the IETF will
continue to allow such access so as not to break such
tooling. New services will however generally only be made
available in ways that use security protocols such as
TLS."

If you have wordsmithing changes to suggest please just send
those to me or the iesg. More substantive comments should go
here I guess. I hope the only bit worth discussing (except
for the few folks who would rather we do none of this;-)
might be the last sentence.

A few weeks after any discussion here dies down I'll put the
resulting text on an IESG telechat for approval if that seems
like the right thing to do.

Thanks,
S

[1] https://tools.ietf.org/html/rfc6797


From nobody Thu Apr  3 16:31:51 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BACAD1A034F for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 00R0JL1TCobt for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:31:44 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3F6AC1A0348 for <ietf@ietf.org>; Thu,  3 Apr 2014 16:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1396567900; x=1428103900; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=tFpOaFO9/IPTVr/wOq/cWay57JK9+sUqP0XaBXWGJXY=; b=TzSkj5rI/ByltG0cMYCWyaYYaYq2ZUV88cwxXzhEqzbLu/8g6lOCaVi8 ODVvckzK0egEnyx/GnT6z707KIflqTUKFgpydCdHPVNAzDXTV9DganLZY 8oyX3NMxdm4fmyn4EbnAl0xpnldi2q1EYPZSjDguUo1flPwmJDH8oo6yT w=;
X-IronPort-AV: E=McAfee;i="5400,1158,7397"; a="117578946"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 03 Apr 2014 16:31:40 -0700
X-IronPort-AV: E=Sophos;i="4.97,791,1389772800"; d="scan'208";a="643369739"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Apr 2014 16:31:40 -0700
Received: from [99.111.97.136] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 3 Apr 2014 16:31:39 -0700
Message-ID: <p06240601cf639cb2113b@[99.111.97.136]>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk>
X-Mailer: Eudora for Mac OS X
Date: Thu, 3 Apr 2014 16:24:29 -0700
To: <l.wood@surrey.ac.uk>, <stephen.farrell@cs.tcd.ie>, <ietf@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: RE: Security for various IETF services
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kPBue2-wb4tvgY9DUZnVcyadRzo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 23:31:49 -0000

My reaction is also to ask "Why?"  Security and privacy involve 
trade-offs where various costs (including operational difficulty) are 
weighed against the benefits, such as protecting information from 
unauthorized disclosure or modification.  So, I'd suggest that a 
blanket statement isn't a good idea, but rather, a service-by-service 
decision should be made.  For example, XMPP and document submission 
may justify requiring encryption while email and document retrieval 
might not.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
!!!!!CP MBI na ni deppart m'I  !pleH


From nobody Thu Apr  3 16:32:00 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D5BC1A034F for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:31:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level: 
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 NEDUdh_XH8It for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:31:47 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 21AED1A034E for <ietf@ietf.org>; Thu,  3 Apr 2014 16:31:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1396567903; x=1428103903; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=WrCefpro22e0lmHYGeh6s+XTX3Ee4A/TqKQ+zIOrahs=; b=J9tpjR1TTZTiInnTaqV5ei/Lzmz/+1oPG48iCe0STmMnxvejGh2wWhD+ KOEhX2DbMM8x8FX5mNTOgJVdzw8tx5a0rm2dSphxxhVHBmyCU5DBJ+xM0 zTzZdVS0GCCEygW4/eLT11JD+I+usBeYgjLK5VDZGjJs6up0Ddcw8SrqS s=;
X-IronPort-AV: E=McAfee;i="5400,1158,7397"; a="61556612"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by sabertooth02.qualcomm.com with ESMTP; 03 Apr 2014 16:31:42 -0700
X-IronPort-AV: E=Sophos;i="4.97,791,1389772800"; d="scan'208";a="29486803"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Apr 2014 16:31:42 -0700
Received: from [99.111.97.136] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 3 Apr 2014 16:31:41 -0700
Message-ID: <p06240602cf639e817dc4@[99.111.97.136]>
In-Reply-To: <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com> <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 3 Apr 2014 16:26:20 -0700
To: John C Klensin <john-ietf@jck.com>, Ted Lemon <ted.lemon@nominum.com>, Clint Chaplin <clint.chaplin@gmail.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control  Protocol for Tea Efflux Appliances (HTCPCP-TEA)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UmLxYFxUpwaamB0z9hPSbXVolhI
Cc: drafts-update-ref@iana.org, rfc-dist@rfc-editor.org, ietf@ietf.org, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 23:31:51 -0000

At 8:01 PM -0400 4/2/14, John C Klensin wrote:

>  --On Wednesday, April 02, 2014 19:42 -0400 Ted Lemon
>  <ted.lemon@nominum.com> wrote:
>
>>  On Apr 2, 2014, at 6:54 PM, Clint Chaplin
>>  <clint.chaplin@gmail.com> wrote:
>>>  Will there be an option for not-tea?
>>
>>  No.   You can't have tea and not-tea.
>
>  At least until you answer the question "when is tea not tea" in
>  a satisfactory way.  For example, the stuff that comes
>  identified as tea but arrives in bags in many bad restaurants
>  (and others that should know better), is pretty clearly not tea
>  but it is less clear whether it is not-tea or not.

"Waiter, if this is coffee, bring me tea.  If this is tea, bring me coffee."

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
There are two ways of constructing a software design: One way
is to make is so simple that there are obviously no
deficiencies, and the other way is to make it so complicated
that there are no obvious deficiencies."     --C. A. R. Hoare


From nobody Thu Apr  3 16:32:01 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F024B1A035D for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 AHoFEavWcrQN for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:31:49 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3B59C1A0348 for <ietf@ietf.org>; Thu,  3 Apr 2014 16:31:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1396567905; x=1428103905; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=TT56VrCm4FJBbM6SLeaKP9+Yc7e8JnoPHUj7a3/e/j8=; b=CUTDJwRl7x9wUKXwU1gEtfJ8J+QxwD6izVBQWGUC34iN0aQWYK0+LvEW UUgHCriGnqAwyGNDzO2i8HM9PGmKyHHEJXsvJVzc5L/0Xv6JtRNeQNJtT g2YIhZ7fCwYV7cc5ivaQ1YEv7MSI04IapJwgRHjyuJYuTSZK8JuOjIQiN Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,7397"; a="117578954"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine02.qualcomm.com with ESMTP; 03 Apr 2014 16:31:45 -0700
X-IronPort-AV: E=Sophos;i="4.97,791,1389772800"; d="scan'208";a="28975075"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Apr 2014 16:31:44 -0700
Received: from [99.111.97.136] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 3 Apr 2014 16:31:44 -0700
Message-ID: <p06240603cf639ebf8c0d@[99.111.97.136]>
In-Reply-To: <1396395466.15324.6860.camel@mightyatom>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>
X-Mailer: Eudora for Mac OS X
Date: Thu, 3 Apr 2014 16:29:37 -0700
To: Elwyn Davies <elwynd@dial.pipex.com>, "Andrew G. Malis" <agmalis@gmail.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea  Efflux Appliances (HTCPCP-TEA)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bBjHqM5o_sDWKjATlvO--0hxDug
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 23:31:54 -0000

At 12:37 AM +0100 4/2/14, Elwyn Davies wrote:

>  We also need the internationalized version to cater for all those
>  excellent varieties of China Tea.  A nice drop of pu-erh perhaps?

I stopped reading when I saw that there was no provision for handling 
more delicate teas, just as Japanese sencha or gyokuro, which require 
significantly cooler water and shorter brewing times.  I'm not sure 
I'd characterize this as a question of internationalization, since it 
involves fundamental protocol elements and operation rather than user 
display text.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
The single biggest problem in communication is the illusion that it
has taken place.                                       --G. B. Shaw


From nobody Thu Apr  3 16:40:18 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE4AF1A036D for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:40:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.511
X-Spam-Level: 
X-Spam-Status: No, score=-109.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 5V3lFI3lA8zp for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:40:11 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2351A0369 for <ietf@ietf.org>; Thu,  3 Apr 2014 16:40:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2392; q=dns/txt; s=iport; t=1396568407; x=1397778007; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=SsRsnUlMPkSjgMmSDvuEI8a5HXR+ncWHVQ89k8sJABQ=; b=CWrSoNuaamYkVPs5VDAyi7TCsZZu62OpzbJ99MOOihIM9hNTehRI2AKD tR2ZMiwdVYiTBFQNSWFG0ZlXdutE8vbbLXJqur7K1PD9iAKie+GqSwH+X f8e0ie+0eEUTIV6H0PmNl1wdolbvEqIE0wIeCJ8mqGsSizOF8DgGu1F6B c=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkQFACvwPVOtJA2L/2dsb2JhbABXgwY7V8N/gRsWdIIlAQEBAwF5BQsCAQgOODIlAgQOBQ6HYwjPVheODxEBUAeDJIEUBJBfgTWGR4YajCSDMIFyOQ
X-IronPort-AV: E=Sophos;i="4.97,791,1389744000";  d="asc'?scan'208";a="32731602"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by alln-iport-3.cisco.com with ESMTP; 03 Apr 2014 23:40:01 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by alln-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s33Ne19G023342 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 3 Apr 2014 23:40:01 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.247]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Thu, 3 Apr 2014 18:40:00 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPT1jb9RjrCInNDUKc3+ugPcK7EpsAuYgAgAAjUICAAARUgA==
Date: Thu, 3 Apr 2014 23:40:00 +0000
Message-ID: <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]>
In-Reply-To: <p06240601cf639cb2113b@[99.111.97.136]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_E9BB0649-48A2-4608-8A3F-A228C4DAC22A"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VfzD4ot32s-ESm8GcOr2vtYry2U
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 23:40:16 -0000

--Apple-Mail=_E9BB0649-48A2-4608-8A3F-A228C4DAC22A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

In view of recent issues in TurkTelecom and Indosat, it seems like the =
simplest reason would be to ensure that data putatively obtained from =
the IETF would in fact be obtained from the IETF.

=46rom my perspective, I would support a statement to the effect that =
IETF technology should be obtainable using https or whatever else we are =
recommending as "secure.=94 I=92d also be in favor of asking IETF =
contributors to obtain and use PGP keys and/or DKIM encodings to sign =
messages. And of asking that IETF tools not reformat email in ways that =
corrupt data that has been signed.

To that end, I could imagine a requirement for some kind of roadmap. =
=93The tools that access the IETF SMTP and HTTP sites use protocols X, =
Y, and Z. After <date>, we require them to use Secure X, Secure Y, and =
Secure Z, and traffic originated by the IETF sites shall use such =
protocols."

On Apr 3, 2014, at 4:24 PM, Randall Gellens <randy@qti.qualcomm.com> =
wrote:

> My reaction is also to ask "Why?"  Security and privacy involve =
trade-offs where various costs (including operational difficulty) are =
weighed against the benefits, such as protecting information from =
unauthorized disclosure or modification.  So, I'd suggest that a blanket =
statement isn't a good idea, but rather, a service-by-service decision =
should be made.  For example, XMPP and document submission may justify =
requiring encryption while email and document retrieval might not.
>=20
> --=20
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself =
only
> -------------- Randomly selected tag: ---------------
> !!!!!CP MBI na ni deppart m'I  !pleH
>=20


--Apple-Mail=_E9BB0649-48A2-4608-8A3F-A228C4DAC22A
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFTPfFPbjEdbHIsm0MRAgKGAKDXR/A/zdsgBYnAXqFCbQJzjVDpNACfbQiR
OZSVPElQftJH10EzQNoz1u4=
=Wx/b
-----END PGP SIGNATURE-----

--Apple-Mail=_E9BB0649-48A2-4608-8A3F-A228C4DAC22A--


From nobody Thu Apr  3 16:48:29 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26B8E1A03AA for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 vhURAjUSmOOr for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:48:24 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 72B981A0210 for <ietf@ietf.org>; Thu,  3 Apr 2014 16:48:24 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P67T1Z25A80052KU@mauve.mrochek.com> for ietf@ietf.org; Thu, 3 Apr 2014 16:43:20 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P5NOFJJ0Y800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 3 Apr 2014 16:43:15 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P67T1X0MI000004W@mauve.mrochek.com>
Date: Thu, 03 Apr 2014 16:35:41 -0700 (PDT)
Subject: RE: Security for various IETF services
In-reply-to: "Your message dated Thu, 03 Apr 2014 16:24:29 -0700" <p06240601cf639cb2113b@[99.111.97.136]>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]>
To: Randall Gellens <randy@qti.qualcomm.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rxR2a7TAtS_lVkdoDLl57RxlKqk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 23:48:29 -0000

> My reaction is also to ask "Why?"  Security and privacy involve
> trade-offs where various costs (including operational difficulty) are
> weighed against the benefits, such as protecting information from
> unauthorized disclosure or modification.  So, I'd suggest that a
> blanket statement isn't a good idea, but rather, a service-by-service
> decision should be made.  For example, XMPP and document submission
> may justify requiring encryption while email and document retrieval
> might not.

Bingo. There's a perfectly reasonable case to be made for protecting any sort
of authorization/authentication exchange and not allowing alternatives.

But in the case of document distribution, our primary goal should be to insure
maximum availability and access to the information we provide, including
to those who are unable to whatever reason to use protected services.

And yes, I'm aware of the argument that access to certain standards, especially
ones themselves having to do with security, might be problematic to folks
living under some repressive regime or other. I don't buy it, mostly
because that level of paranoia is going to regard any sort of access to
IETF materials whatsoever as a red flag, especially it was conducted over
TLS/SSL.

				Ned


From nobody Thu Apr  3 16:52:02 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9EDDA1A03B3 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:51:59 -0700 (PDT)
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] autolearn=ham
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 Y6B9g81gDZBP for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:51:55 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7F7571A03B1 for <ietf@ietf.org>; Thu,  3 Apr 2014 16:51:55 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s33NpkFf023863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 3 Apr 2014 16:51:49 -0700
Message-ID: <533DF3A9.4030201@dcrocker.net>
Date: Thu, 03 Apr 2014 16:50:01 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Fred Baker (fred)" <fred@cisco.com>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
In-Reply-To: <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 03 Apr 2014 16:51:49 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dGeaIRxVeWRQuFiZK3o-ygca8R4
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 23:51:59 -0000

On 4/3/2014 4:40 PM, Fred Baker (fred) wrote:
> DKIM encodings to sign messages. And of asking that IETF tools not reformat email in ways that corrupt data that has been signed.


Yes, but...

DKIM does not authenticate message contents, and the dkim signing name 
(d=) is not require to correlate with any other identifier in the 
message.  In particular, it can be unrelated to the domain name in the 
From: field.

This independence is essential for some scenarios, such as having a 
mailing list provide its own DKIM signature, using it's own domain name, 
while preserving the author's original From address.

In other words, I like the goal you have in mind, but fear it is 
considerably more challenging to achieve than any of us would like.


d/

ps. The other reason for using https is privacy to reduce traffic 
analysis and other meta-data review.  This is quite separate from 
keeping IETF data 'confidential'.

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Thu Apr  3 16:55:18 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CED7B1A03B1 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:55:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 I5jVZ-jTy06p for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:55:13 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id A414A1A03AA for <ietf@ietf.org>; Thu,  3 Apr 2014 16:55:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1396569309; x=1428105309; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=C6Y/HbUfNBjBuMaC015sq3DhAOlaXv+Ohhnw7MqmRCA=; b=iNQQEdvCNpwIKeY8g6b4iO2HTB+dwRN8rYaNhSX8SgJRlb8mGMkOVTi/ oOrOwflARhpaTJ1ixMlR4bFP+1FWGaeLQ8URNXXPKTjQccolVKnSEjk6Z 5xQscF5wP9hQ3EfpWrZO5qy0YrKyeU1M9neCeIoa4L9Bl8amIE9ArbH5E I=;
X-IronPort-AV: E=McAfee;i="5400,1158,7397"; a="26523538"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 03 Apr 2014 16:55:09 -0700
X-IronPort-AV: E=Sophos;i="4.97,791,1389772800"; d="scan'208";a="710144091"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Apr 2014 16:55:09 -0700
Received: from [99.111.97.136] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 3 Apr 2014 16:55:08 -0700
Message-ID: <p06240604cf63a4b0f0c5@[99.111.97.136]>
In-Reply-To: <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 3 Apr 2014 16:55:04 -0700
To: "Fred Baker (fred)" <fred@cisco.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: Security for various IETF services
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gCRhS8R4X19B5hocqsJk2Lkdowo
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 23:55:18 -0000

At 11:40 PM +0000 4/3/14, Fred Baker (fred) wrote:

>  In view of recent issues in TurkTelecom and Indosat, it seems like 
> the simplest reason would be to ensure that data putatively 
> obtained from the IETF would in fact be obtained from the IETF.

Would this be met by allowing access using protocols where server 
certificates are sent, rather than requiring it?  You can't force 
anyone to verify a server certificate or to do a good job if they 
try, so why force them to take a certificate?

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
If the employees come first, then they are happy. A motivated
employee treats the customer well. The customer is happy so they
keep coming back, which pleases the shareholders.  It's not one of
the enduring Green mysteries of all time, it is just the way it
works.       --Herb Kelleher, Southwest Airlines CEO, 1994


From nobody Thu Apr  3 16:56:47 2014
Return-Path: <pranesh@cis-india.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 828771A03BC for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.79
X-Spam-Level: 
X-Spam-Status: No, score=0.79 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_PSBL=2.7, T_RP_MATCHES_RCVD=-0.01] autolearn=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 tAz78aJXysvh for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 16:56:42 -0700 (PDT)
Received: from mail.cis-india.org (mail.cis-india.org [202.190.125.68]) by ietfa.amsl.com (Postfix) with ESMTP id 77B7A1A03AA for <ietf@ietf.org>; Thu,  3 Apr 2014 16:56:42 -0700 (PDT)
Received: from [192.168.1.65] (172-0-8-35.lightspeed.wlfrct.sbcglobal.net [172.0.8.35]) by mail.cis-india.org (Postfix) with ESMTPSA id 87CE4A7CAE7; Thu,  3 Apr 2014 23:54:27 +0000 (UTC)
Message-ID: <533DF52E.5020707@cis-india.org>
Date: Thu, 03 Apr 2014 19:56:30 -0400
From: Pranesh Prakash <pranesh@cis-india.org>
Organization: Centre for Internet and Society
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>,  IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie>
In-Reply-To: <533D8A90.60309@cs.tcd.ie>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="7FktWsb96krVfa2tUrxWgUH5LQrnQknq3"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5Ui6zP9qfpH98UH6sY1ZKwyKnvY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2014 23:56:46 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7FktWsb96krVfa2tUrxWgUH5LQrnQknq3
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Stephen Farrell <stephen.farrell@cs.tcd.ie> [2014-04-003 17:21:36 +0100]:=

> The most recent such was a request to turn on HSTS [1] for
> the IETF web site, which I don't think we can do without
> breaking old tools etc.

> However, as there are numerous legacy tools that have been
> built that require access via cleartext

Could you please expand on this?  What kinds of legacy tools is that=20
statement talking about?

Thanks.

~ Pranesh




--7FktWsb96krVfa2tUrxWgUH5LQrnQknq3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJTPfUuAAoJEFUPonS5l6Cpe/0P/iNdraQvpfIbEYi9yO/ApoFm
98kPwFeTD240s8VCIBBW0GmktHTebCF3PfCs1FoFy7p3K5NlPGgw3c8IOd8fPaDs
AMGwnw9WXs41AWlJAXi0Ioxk56qwH0D7Pzlaztu5Azcs2plO9TLBxlt2Za+P33Xm
HTm1V6WN9sIJM/CU6+TI42hNyqfA9EAdOOz/3LLavdDXN89bz8u/wK2YKJytF19t
m5zCBTXuzIBhPojT1Pgrhat1fZUk660RxTtVchz4iHbvAl5EZvl4xGFNnL0ZSbxk
nFLb+bbkZ3YQLA5z6YuByjaQgCPbow9kv2598Fhbrb+CZDkG7l42UPsGohfdfxvp
SiVet/fCRYSf0/J5+KA6vYsU8hJ5faeC2Er+I1KqLkISKUhNtY3mMKRmEEUlJ5IM
yFJtjkTD8Ic/7+WoNjyRaBsktG8Akl2dExiAH0uKWCdm7oFKx8jAjPYUPvI5PyNC
efgxP+WRKef9NZiaN8iU+SfLJRoM08aytgiyzutHuVVCFbOxcLLVKfwuH4oIDnB2
aKUiHdx5HcJYtyyQ7fYi2k1TuGIqYK3SV6TCYWlvheI3Iv5CGVwmpy4eblxdlRgs
xjjMGexiX9HQfXz54zNeVs14TfQMLBtYIVJFL8S7YYshq6GMhuCaeBXkZu5+tKSf
wbWB/p39S0Ly1QPwv+dT
=HOTu
-----END PGP SIGNATURE-----

--7FktWsb96krVfa2tUrxWgUH5LQrnQknq3--


From nobody Thu Apr  3 17:01:26 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2524F1A03DB for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:01:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.511
X-Spam-Level: 
X-Spam-Status: No, score=-114.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 RdJnFT4EfqZF for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:01:21 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 356371A03D7 for <ietf@ietf.org>; Thu,  3 Apr 2014 17:01:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1581; q=dns/txt; s=iport; t=1396569677; x=1397779277; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=R35eG5PuXDwBAl0mH1iw67HBfZvhu3iqZGONl/atvuA=; b=RD8ytWVVzaqxVZv9dvy5Rqk0u2dSQJ3mmxFyzDiEnmllUa889od2tT3Z qy8WuDUfy76DmNI7cIVAp2dsjehxJ91+lJWaGmEeKbCIZJh3n9EYJfYvI hXG4xhDNkbm5HGWfW13uJfc2weR8+Tq0bFBpgLwI+EROlizEJcmMFMPYF g=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkQFAJr1PVOtJA2G/2dsb2JhbABXgwY7V8N/gRwWdIIlAQEBAwF5BQsCAQhGMiUCBA4FDodjCK53oFwXjnEHCYMbgRQBA5BfgTWGR4E0kQqDMIIr
X-IronPort-AV: E=Sophos;i="4.97,791,1389744000";  d="asc'?scan'208";a="314985401"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-7.cisco.com with ESMTP; 04 Apr 2014 00:01:16 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id s3401G6L015142 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Apr 2014 00:01:16 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.247]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Thu, 3 Apr 2014 19:01:16 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: Re: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPT1jb9RjrCInNDUKc3+ugPcK7EpsAuYgAgAAjUICAAARUgIAAAs6AgAADIgA=
Date: Fri, 4 Apr 2014 00:01:15 +0000
Message-ID: <E361A3FC-18FB-459E-819B-4C782F7E99F7@cisco.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com> <533DF3A9.4030201@dcrocker.net>
In-Reply-To: <533DF3A9.4030201@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_54E015C1-DB32-48AE-B673-328CA7C10B42"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/M4EVdGy131NXiJUqI8BJeuDNhOo
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:01:25 -0000

--Apple-Mail=_54E015C1-DB32-48AE-B673-328CA7C10B42
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 3, 2014, at 4:50 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> ps. The other reason for using https is privacy to reduce traffic =
analysis and other meta-data review.  This is quite separate from =
keeping IETF data 'confidential'.

I=92m actually not in the least interested in IETF data =
=93confidentiality=94. It=92s not confidential.

If someone can hijack 8.8.8.8 and send it to a DNS server in their =
favorite country, they can hijack ietf.org or 2001:1900:3001:11::2c and =
send it to a web server of their choice. I=92d like for information from =
the IETF to be verifiably authentic. That includes, of course, a =
signature on the file and at least a signature in flight. If the way to =
get something equivalent to a signature is encryption in the IETF=92s =
private key, whatever. But not a key that can be copied and reused to =
sign/encrypt corrupted data.

--Apple-Mail=_54E015C1-DB32-48AE-B673-328CA7C10B42
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFTPfZKbjEdbHIsm0MRAn08AJ9W1KswmEk+I9ycYCn8nio4fd+krACfdzDL
Onib4qrzpiX7ELMZ1o2O0gk=
=WdYh
-----END PGP SIGNATURE-----

--Apple-Mail=_54E015C1-DB32-48AE-B673-328CA7C10B42--


From nobody Thu Apr  3 17:14:04 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15A041A03AA for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:14:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level: 
X-Spam-Status: No, score=-1.99 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, SPF_PASS=-0.001, T_TVD_FUZZY_SECURITIES=0.01] autolearn=ham
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 qolWRs8i56BT for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:13:55 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 80C1B1A002E for <ietf@ietf.org>; Thu,  3 Apr 2014 17:13:52 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id uo5so2617209pbc.32 for <ietf@ietf.org>; Thu, 03 Apr 2014 17:13:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=L/tpIJSVyaXKyGqJOUByH/lll1owYpSi6muFOGlrSYE=; b=pfFBUCOquSOPyZD20t361jHhfRkExyAlAVwrxmVrGxovhcMu1O08+sIsFJYG9HpmTM Lqt07jsCeuJK1e/dzC5XgPlkqX48MAUFxwOmllR/sDAFKBRAeoHz/Yg4twUXGohKPOJn 1D0MtWjAWwLMTSORhR4I/RVQeNR1TvVTeXvoCMQZjtoLQm21KXfslB4+A9QuDf7wmDcm 1k8J6pKHnbIkMr2AC8lJKlRZ6wHisnMEnmHVGbiseTdbLa7Yl8w4SruViXloBCB1toFB 1JryffLDt+R1ggcI8p830kTGQ9QX0kLzEhqCJdrT+i7oQNwtQj7/SD+pkNjTxfVDbV7s scMg==
X-Received: by 10.66.171.76 with SMTP id as12mr11142491pac.52.1396570428268; Thu, 03 Apr 2014 17:13:48 -0700 (PDT)
Received: from [192.168.2.242] (c-67-188-1-12.hsd1.ca.comcast.net. [67.188.1.12]) by mx.google.com with ESMTPSA id hr5sm31818178pac.18.2014.04.03.17.13.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Apr 2014 17:13:46 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
Date: Thu, 3 Apr 2014 17:13:49 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <57560B49-6A9A-4F4B-A3DD-191C5BA11722@gmail.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
To: "Fred Baker (fred)" <fred@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TKWlnOVAzskEpXUwzsPcpcaU9y8
Cc: Randall Gellens <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:14:00 -0000

On Apr 3, 2014, at 4:40 PM, Fred Baker (fred) <fred@cisco.com> wrote:

> In view of recent issues in TurkTelecom and Indosat, it seems like the =
simplest reason would be to ensure that data putatively obtained from =
the IETF would in fact be obtained from the IETF.
>=20
> =46rom my perspective, I would support a statement to the effect that =
IETF technology should be obtainable using https or whatever else we are =
recommending as "secure.=94 I=92d also be in favor of asking IETF =
contributors to obtain and use PGP keys and/or DKIM encodings to sign =
messages. And of asking that IETF tools not reformat email in ways that =
corrupt data that has been signed.
>=20
> To that end, I could imagine a requirement for some kind of roadmap. =
=93The tools that access the IETF SMTP and HTTP sites use protocols X, =
Y, and Z. After <date>, we require them to use Secure X, Secure Y, and =
Secure Z, and traffic originated by the IETF sites shall use such =
protocols."

Dear Fred,

XMPP provides an interesting feature called server federation.  It would =
be good to see the excellent work of Dukhovni and Parsons extended to =
include authentication of sending servers (clients) to support =
federation.  This is something TLS supports but is rarely used.  Such a =
feature could significantly improve overall security especially in the =
wake of RTF messages exposing users to remote code execution. =20

DKIM only covers message fragments and is unrelated to the actual sender =
by design.  A malicious link might be found in the Subject line that can =
be followed with user clicks which may not have been signed or users =
might see prepended =46rom header fields which don't impact DKIM =
signature validity.

Regards,
Douglas Otis=


From nobody Thu Apr  3 17:22:32 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8C9D1A02F7 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:22:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.59
X-Spam-Level: 
X-Spam-Status: No, score=-2.59 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_TVD_FUZZY_SECURITIES=0.01, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 ZGzaj8HGeNwh for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:22:23 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.166]) by ietfa.amsl.com (Postfix) with ESMTP id 8FEAD1A0025 for <ietf@ietf.org>; Thu,  3 Apr 2014 17:22:22 -0700 (PDT)
Received: from [85.158.137.99:45986] by server-6.bemta-3.messagelabs.com id 05/94-00470-93BFD335; Fri, 04 Apr 2014 00:22:17 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-3.tower-217.messagelabs.com!1396570936!14226675!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13485 invoked from network); 4 Apr 2014 00:22:17 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-3.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 4 Apr 2014 00:22:17 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Fri, 4 Apr 2014 01:22:16 +0100
From: <l.wood@surrey.ac.uk>
To: <doug.mtview@gmail.com>, <fred@cisco.com>
Date: Fri, 4 Apr 2014 01:21:55 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9PmtgG+06G4xkCQAqxnt7g94Y0ZAAAQpYB
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEB7@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>, <57560B49-6A9A-4F4B-A3DD-191C5BA11722@gmail.com>
In-Reply-To: <57560B49-6A9A-4F4B-A3DD-191C5BA11722@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/e5dQy1qK2hHhDSIR8woQxkE-3Gw
Cc: randy@qti.qualcomm.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:22:29 -0000

"It would be good to see the excellent work of Dukhovni and Parsons extende=
d
to include authentication of sending servers (clients) to support federatio=
n. "

Why?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Douglas Otis [doug.mtview@g=
mail.com]
Sent: 04 April 2014 01:13
To: Fred Baker (fred)
Cc: Randall Gellens; ietf@ietf.org
Subject: Re: Security for various IETF services

On Apr 3, 2014, at 4:40 PM, Fred Baker (fred) <fred@cisco.com> wrote:

> In view of recent issues in TurkTelecom and Indosat, it seems like the si=
mplest reason would be to ensure that data putatively obtained from the IET=
F would in fact be obtained from the IETF.
>
> From my perspective, I would support a statement to the effect that IETF =
technology should be obtainable using https or whatever else we are recomme=
nding as "secure.=94 I=92d also be in favor of asking IETF contributors to =
obtain and use PGP keys and/or DKIM encodings to sign messages. And of aski=
ng that IETF tools not reformat email in ways that corrupt data that has be=
en signed.
>
> To that end, I could imagine a requirement for some kind of roadmap. =93T=
he tools that access the IETF SMTP and HTTP sites use protocols X, Y, and Z=
. After <date>, we require them to use Secure X, Secure Y, and Secure Z, an=
d traffic originated by the IETF sites shall use such protocols."

Dear Fred,

XMPP provides an interesting feature called server federation.  It would be=
 good to see the excellent work of Dukhovni and Parsons extended to include=
 authentication of sending servers (clients) to support federation.  This i=
s something TLS supports but is rarely used.  Such a feature could signific=
antly improve overall security especially in the wake of RTF messages expos=
ing users to remote code execution.

DKIM only covers message fragments and is unrelated to the actual sender by=
 design.  A malicious link might be found in the Subject line that can be f=
ollowed with user clicks which may not have been signed or users might see =
prepended From header fields which don't impact DKIM signature validity.

Regards,
Douglas Otis


From nobody Thu Apr  3 17:24:03 2014
Return-Path: <fred@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFD931A0429 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:23:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.501
X-Spam-Level: 
X-Spam-Status: No, score=-114.501 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, T_TVD_FUZZY_SECURITIES=0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 taqBISjlkXTw for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:23:55 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) by ietfa.amsl.com (Postfix) with ESMTP id 401D21A0025 for <ietf@ietf.org>; Thu,  3 Apr 2014 17:23:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3218; q=dns/txt; s=iport; t=1396571031; x=1397780631; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=MWt+R81H3/AnUwfIP0RK3WiLv6fqH1k0RKIOeakBkKU=; b=PqeDHzs0mrQJHw/xnxVCGDjyOedNhnnA7rL9eA4Br0GheOAXgoRngOB5 zEDyevOJ7+/+AJtjTshHn+PRvEpnf64DrxDAQzy1om6X4RcOXzdCnnI0I oXbNDKjih20u9/ZhcxO72G5r985zmAt7SSHfJTJydY+zgq+rxi8/eNDa9 I=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AogFAK/6PVOtJV2Z/2dsb2JhbABXDoJ4O1EGw36BHBZ0giUBAQEDAXkFCwIBCBEEAQEBLiERHQgCBA4FDodXAwkICMgZDYciF4xXgTgRAVAHBoMegRQEkF+BNYJbgX+BbYE0izsDhUyCcECBcjk
X-IronPort-AV: E=Sophos;i="4.97,791,1389744000";  d="asc'?scan'208";a="315027593"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-3.cisco.com with ESMTP; 04 Apr 2014 00:23:50 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s340Noxu005700 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 4 Apr 2014 00:23:50 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.247]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Thu, 3 Apr 2014 19:23:50 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: Re: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPT1jb9RjrCInNDUKc3+ugPcK7EpsAuYgAgAAjUICAAARUgIAACXSAgAACRICAAACHAA==
Date: Fri, 4 Apr 2014 00:23:49 +0000
Message-ID: <E87EF968-2AD5-47BD-95A7-39891975D0D0@cisco.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>, <57560B49-6A9A-4F4B-A3DD-191C5BA11722@gmail.com> <290E20B455C66743BE178C5C84F1240847E779EEB7@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEB7@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.19.64.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_3F20B16C-E495-41C6-9886-384BC2F0F43B"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lBUgorxsyUfcdVqwt3ydH9Aj-Kc
Cc: "randy@qti.qualcomm.com" <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:24:00 -0000

--Apple-Mail=_3F20B16C-E495-41C6-9886-384BC2F0F43B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 3, 2014, at 5:21 PM, <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk> =
wrote:

> "It would be good to see the excellent work of Dukhovni and Parsons =
extended
> to include authentication of sending servers (clients) to support =
federation. "
>=20
> Why?

In order to support data authentication.

> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Douglas Otis =
[doug.mtview@gmail.com]
> Sent: 04 April 2014 01:13
> To: Fred Baker (fred)
> Cc: Randall Gellens; ietf@ietf.org
> Subject: Re: Security for various IETF services
>=20
> On Apr 3, 2014, at 4:40 PM, Fred Baker (fred) <fred@cisco.com> wrote:
>=20
>> In view of recent issues in TurkTelecom and Indosat, it seems like =
the simplest reason would be to ensure that data putatively obtained =
from the IETF would in fact be obtained from the IETF.
>>=20
>> =46rom my perspective, I would support a statement to the effect that =
IETF technology should be obtainable using https or whatever else we are =
recommending as "secure.=94 I=92d also be in favor of asking IETF =
contributors to obtain and use PGP keys and/or DKIM encodings to sign =
messages. And of asking that IETF tools not reformat email in ways that =
corrupt data that has been signed.
>>=20
>> To that end, I could imagine a requirement for some kind of roadmap. =
=93The tools that access the IETF SMTP and HTTP sites use protocols X, =
Y, and Z. After <date>, we require them to use Secure X, Secure Y, and =
Secure Z, and traffic originated by the IETF sites shall use such =
protocols."
>=20
> Dear Fred,
>=20
> XMPP provides an interesting feature called server federation.  It =
would be good to see the excellent work of Dukhovni and Parsons extended =
to include authentication of sending servers (clients) to support =
federation.  This is something TLS supports but is rarely used.  Such a =
feature could significantly improve overall security especially in the =
wake of RTF messages exposing users to remote code execution.
>=20
> DKIM only covers message fragments and is unrelated to the actual =
sender by design.  A malicious link might be found in the Subject line =
that can be followed with user clicks which may not have been signed or =
users might see prepended =46rom header fields which don't impact DKIM =
signature validity.
>=20
> Regards,
> Douglas Otis

	=95 Make things as simple as possible, but not simpler.
Albert Einstein


--Apple-Mail=_3F20B16C-E495-41C6-9886-384BC2F0F43B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFTPfuUbjEdbHIsm0MRAghVAKCxpYm2B7ouxjCK1jnUgp45qoK+SwCfU6a1
+Yr8dYVgOLY0zlp/nF7ywfI=
=d4Cs
-----END PGP SIGNATURE-----

--Apple-Mail=_3F20B16C-E495-41C6-9886-384BC2F0F43B--


From nobody Thu Apr  3 17:26:59 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1807A1A0025 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:26:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 ZhVeMe1KZZKv for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:26:52 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 7C6101A03F5 for <ietf@ietf.org>; Thu,  3 Apr 2014 17:26:52 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id fp1so2521413pdb.14 for <ietf@ietf.org>; Thu, 03 Apr 2014 17:26:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5cQj37wLWknYQ5kYhuTrLKMtbLl/E0s0txdLCUjexf0=; b=XNKASzvkjkDoT1BrjUWhizEd91zPwAy77yTkVrv4BB8Dd54v85r6L+rLzlDunt07OJ 7mjtqoAMwO+hS2PsRtcYGfG6euk0bpJWa0O9JjIW1fZuKTl+pj1S7Drc8vSwudjonzjp 7AzWchVmt4FAVM9CyGqpVkzlkWkIMNJAS9tQe+CnenN0JkgWBM9VIOVLgPXff/EXZgoF xUQq9W0kvyVcQLws+Fax2otXSvd28IQDZpKTaKVXIUjjCzGP3Izel8AV7JnWC+y5hQir u1dYzvps/lxiefiWkTb3CO6oWIqjtuzqtADGnjdYxgmioU4jA3GbSBoYDmbg7MRFSYyN xjYw==
X-Received: by 10.68.160.163 with SMTP id xl3mr11191295pbb.39.1396571208239; Thu, 03 Apr 2014 17:26:48 -0700 (PDT)
Received: from [192.168.178.23] (203.202.69.111.dynamic.snap.net.nz. [111.69.202.203]) by mx.google.com with ESMTPSA id xk1sm31927475pac.21.2014.04.03.17.26.46 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 03 Apr 2014 17:26:47 -0700 (PDT)
Message-ID: <533DFC4F.2040902@gmail.com>
Date: Fri, 04 Apr 2014 13:26:55 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <01P67T1X0MI000004W@mauve.mrochek.com>
In-Reply-To: <01P67T1X0MI000004W@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dK0n_3ik1q-xSaz7BLwn8oXWEUA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:26:57 -0000

On 04/04/2014 12:35, ned+ietf@mauve.mrochek.com wrote:
>> My reaction is also to ask "Why?"  Security and privacy involve
>> trade-offs where various costs (including operational difficulty) are
>> weighed against the benefits, such as protecting information from
>> unauthorized disclosure or modification.  So, I'd suggest that a
>> blanket statement isn't a good idea, but rather, a service-by-service
>> decision should be made.  For example, XMPP and document submission
>> may justify requiring encryption while email and document retrieval
>> might not.
> 
> Bingo. There's a perfectly reasonable case to be made for protecting any
> sort
> of authorization/authentication exchange and not allowing alternatives.
> 
> But in the case of document distribution, our primary goal should be to
> insure
> maximum availability and access to the information we provide, including
> to those who are unable to whatever reason to use protected services.
> 
> And yes, I'm aware of the argument that access to certain standards,
> especially
> ones themselves having to do with security, might be problematic to folks
> living under some repressive regime or other. I don't buy it, mostly
> because that level of paranoia is going to regard any sort of access to
> IETF materials whatsoever as a red flag, especially it was conducted over
> TLS/SSL.

That may be, but that doesn't mean we shouldn't offer privacy of
access to those who want it. I think we need to distinguish various
quite separate issues. Off the top of my head, I can see:

* authenticity and integrity of data coming from the IETF site;
* privacy of the fact of access, if the user wants it;
* preventing access to the IETF site being used as an attack
  vector for either the site itself or the remote user
  (which indirectly includes protecting the privacy of
  personal information held at either end);


From nobody Thu Apr  3 17:29:36 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9C251A02B8 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Tca35PcQpNNY for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:29:29 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 5225D1A02A6 for <ietf@ietf.org>; Thu,  3 Apr 2014 17:29:29 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WVs0Z-0003tq-GD; Fri, 04 Apr 2014 00:29:24 +0000
Date: Fri, 04 Apr 2014 09:29:22 +0900
Message-ID: <m238huvswt.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lloyd Wood <L.Wood@surrey.ac.uk>
Subject: Re: Security for various IETF services
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEB7@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MOW9okzEUQSjAcRQHU_sTgfOrrA
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:29:35 -0000

> "It would be good to see the excellent work of Dukhovni and Parsons extended
> to include authentication of sending servers (clients) to support federation. "
> 
> Why?

because we blew it way back when, by designing a completely insecure
and un-private internet.  as supposedly responsible and occasionally
competent engineers, we should rectify our mistakes.

the internet is not an experimental plaything.

randy


From nobody Thu Apr  3 17:35:29 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C274B1A03FE for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:35:27 -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, SPF_PASS=-0.001] autolearn=ham
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 2aeoF-2uhrAj for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:35:21 -0700 (PDT)
Received: from mail-oa0-x22d.google.com (mail-oa0-x22d.google.com [IPv6:2607:f8b0:4003:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id B35661A03FB for <ietf@ietf.org>; Thu,  3 Apr 2014 17:35:21 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id eb12so2862507oac.32 for <ietf@ietf.org>; Thu, 03 Apr 2014 17:35:17 -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:content-type; bh=SQemCnfH4kMAx043A+y7R1fI8lESP5UeyOXAOPfzETI=; b=gcAGwmaTYOMmksZDegWPZ7FbuS7qq2y2RaVg7WQZfOUhz5aQsDHUO1AEz2lftyD4KO DDaKhCjSVJSRSR8ynO/9lDoMg1E0RmnsWCd6ZaF7Tl3zqT12duGczljsREQLP+sBXFwp 5lYI5ExCteWSRLoM12GNkeaxt/IgG5kz0Ije3cm5/ddl+HpdToIy6zr8Qcrmc8C+RbBy MYUcdFgs/GTLzS+8Rg8eOfzlN9qaiUM9yiRkk0NjsJt8gv38wsBL9Jyerfl5ogGCqXGv ENpR0xjpez8VorvcN9eeyYEEYTd5F93U/qx+W/gZlhTWjVEQgPO56CmUEc32cGCwp0ZA JBbw==
MIME-Version: 1.0
X-Received: by 10.60.15.38 with SMTP id u6mr13337957oec.26.1396571717293; Thu, 03 Apr 2014 17:35:17 -0700 (PDT)
Received: by 10.182.48.9 with HTTP; Thu, 3 Apr 2014 17:35:17 -0700 (PDT)
Received: by 10.182.48.9 with HTTP; Thu, 3 Apr 2014 17:35:17 -0700 (PDT)
In-Reply-To: <533D8A90.60309@cs.tcd.ie>
References: <533D8A90.60309@cs.tcd.ie>
Date: Thu, 3 Apr 2014 20:35:17 -0400
Message-ID: <CAPv4CP9eLwu8ftM=c5uEBvy3wb1J-UrRoi6NNxqA6LuJZ=LU6A@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Scott Brim <scott.brim@gmail.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Content-Type: multipart/alternative; boundary=089e013cc0241cdc9904f62cb199
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HxsxJTk-MsLf0qxbOAYiqK9JtnA
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:35:28 -0000

--089e013cc0241cdc9904f62cb199
Content-Type: text/plain; charset=ISO-8859-1

It looks like a statement of direction that's blanket
mandatory-to-implement is too much, since so many services need to be able
to run in an open mode. If there are any services that are only useful when
secured, we can trust the deployers to know that.

--089e013cc0241cdc9904f62cb199
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">It looks like a statement of direction that&#39;s blanket ma=
ndatory-to-implement is too much, since so many services need to be able to=
 run in an open mode. If there are any services that are only useful when s=
ecured, we can trust the deployers to know that. </p>


--089e013cc0241cdc9904f62cb199--


From nobody Thu Apr  3 17:48:14 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 689191A0450 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:48:13 -0700 (PDT)
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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 HNleuAhtlTIm for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:48:08 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.109]) by ietfa.amsl.com (Postfix) with ESMTP id 769001A044A for <ietf@ietf.org>; Thu,  3 Apr 2014 17:48:07 -0700 (PDT)
Received: from [193.109.255.147:49515] by server-5.bemta-14.messagelabs.com id 56/02-26413-2410E335; Fri, 04 Apr 2014 00:48:02 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-72.messagelabs.com!1396572481!10245291!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19151 invoked from network); 4 Apr 2014 00:48:01 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-6.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 4 Apr 2014 00:48:01 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Fri, 4 Apr 2014 01:48:00 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@psg.com>
Date: Fri, 4 Apr 2014 01:47:03 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9PnO+pqK/WYW7kTKm/2RXsP240hAAAnXOP
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEB8@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>, <m238huvswt.wl%randy@psg.com>
In-Reply-To: <m238huvswt.wl%randy@psg.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tMxzCz7W9SGZZ3U_ZfSdrmBBLpE
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:48:13 -0000

"because we blew it way back when, by designing a completely insecure
and un-private internet"

That was not a mistake. That is what made adoption possible.

DTN started with security from the get-go, and DTN has gone nowhere.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Randy Bush [randy@psg.com]
Sent: 04 April 2014 01:29
To: Wood L  Dr (Electronic Eng)
Cc: IETF Disgust
Subject: Re: Security for various IETF services

> "It would be good to see the excellent work of Dukhovni and Parsons exten=
ded
> to include authentication of sending servers (clients) to support federat=
ion. "
>
> Why?

because we blew it way back when, by designing a completely insecure
and un-private internet.  as supposedly responsible and occasionally
competent engineers, we should rectify our mistakes.

the internet is not an experimental plaything.

randy=


From nobody Thu Apr  3 17:56:38 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 390B81A0470 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:56:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 rn13ZKdU0nXJ for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 17:56:33 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id DC7E01A045B for <ietf@ietf.org>; Thu,  3 Apr 2014 17:56:32 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P67VFHK01S0057B2@mauve.mrochek.com> for ietf@ietf.org; Thu, 3 Apr 2014 17:51:27 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P5NOFJJ0Y800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 3 Apr 2014 17:51:25 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P67VFG3GTG00004W@mauve.mrochek.com>
Date: Thu, 03 Apr 2014 17:44:49 -0700 (PDT)
Subject: Re: Security for various IETF services
In-reply-to: "Your message dated Fri, 04 Apr 2014 13:26:55 +1300" <533DFC4F.2040902@gmail.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <01P67T1X0MI000004W@mauve.mrochek.com> <533DFC4F.2040902@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AZO1_psXYiKKVmRgvF8rMR1pShI
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 00:56:37 -0000

> On 04/04/2014 12:35, ned+ietf@mauve.mrochek.com wrote:
> >> My reaction is also to ask "Why?"  Security and privacy involve
> >> trade-offs where various costs (including operational difficulty) are
> >> weighed against the benefits, such as protecting information from
> >> unauthorized disclosure or modification.  So, I'd suggest that a
> >> blanket statement isn't a good idea, but rather, a service-by-service
> >> decision should be made.  For example, XMPP and document submission
> >> may justify requiring encryption while email and document retrieval
> >> might not.
> >
> > Bingo. There's a perfectly reasonable case to be made for protecting any
> > sort
> > of authorization/authentication exchange and not allowing alternatives.
> >
> > But in the case of document distribution, our primary goal should be to
> > insure
> > maximum availability and access to the information we provide, including
> > to those who are unable to whatever reason to use protected services.
> >
> > And yes, I'm aware of the argument that access to certain standards,
> > especially
> > ones themselves having to do with security, might be problematic to folks
> > living under some repressive regime or other. I don't buy it, mostly
> > because that level of paranoia is going to regard any sort of access to
> > IETF materials whatsoever as a red flag, especially it was conducted over
> > TLS/SSL.

> That may be, but that doesn't mean we shouldn't offer privacy of
> access to those who want it.

I never said we shouldn't offer it. The previous discussion was largley
about requiring it.

> I think we need to distinguish various
> quite separate issues. Off the top of my head, I can see:

> * authenticity and integrity of data coming from the IETF site;

Your problem here is people get IETF data from many sources besides the
IETF site. Indeed, alternative data stores may provide access alternatives
for those concerned about being seen accessing IETF data in the obvious way.

As a result I don't see how transport security offers a meaningful solution
here. We should instead be looking at various signature mechanisms.

> * privacy of the fact of access, if the user wants it;

Again, there's nothing wrong with offering secure access as an option.
Wikipedia is the obvious example of a site that does this.

> * preventing access to the IETF site being used as an attack
>   vector for either the site itself or the remote user
>   (which indirectly includes protecting the privacy of
>   personal information held at either end);

Certain aspects of this are easy, others are hard, and some are probably
research problems.

				Ned


From nobody Thu Apr  3 18:06:08 2014
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF3FF1A0489; Thu,  3 Apr 2014 18:06:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Level: 
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 DUbuyyv1fkIn; Thu,  3 Apr 2014 18:06:02 -0700 (PDT)
Received: from mail210.messagelabs.com (mail210.messagelabs.com [216.82.250.179]) by ietfa.amsl.com (Postfix) with ESMTP id B65561A0491; Thu,  3 Apr 2014 18:06:02 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-6.tower-210.messagelabs.com!1396573556!7719780!1
X-Originating-IP: [20.137.2.88]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32140 invoked from network); 4 Apr 2014 01:05:57 -0000
Received: from amer-mta102.csc.com (HELO amer-mta112.csc.com) (20.137.2.88) by server-6.tower-210.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP;  4 Apr 2014 01:05:57 -0000
Received: from amer-gw15.amer.csc.com (amer-gw15.amer.csc.com [20.137.2.189]) by amer-mta112.csc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id s3415twh004353; Thu, 3 Apr 2014 21:05:55 -0400
In-Reply-To: <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CADn-GthSGvG9SOtE7sfzsbtS0SyXHO6xOKXYZHgzDjYux+tYcQ@mail.gmail.com> <F11C2722-7821-4BBB-B6ED-6B8F20A978AB@nominum.com> <BC2AAC258726307E193F95F0@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
MIME-Version: 1.0
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
X-KeepSent: 06728785:EE017DEC-85257CB0:000511BE; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF06728785.EE017DEC-ON85257CB0.000511BE-85257CB0.000608E0@csc.com>
Date: Thu, 3 Apr 2014 21:05:54 -0400
X-MIMETrack: Serialize by Router on AMER-GW15/SRV/CSC(Release 8.5.2FP3 HF666|December 11, 2012) at 04/03/2014 09:05:56 PM, Serialize complete at 04/03/2014 09:05:56 PM
Content-Type: multipart/alternative; boundary="=_alternative 0006084785257CB0_="
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aQsO-bswdfQLFVkixMJ7CpORo7w
Cc: ietf <ietf-bounces@ietf.org>, ietf@ietf.org, drafts-update-ref@iana.org, rfc-dist@rfc-editor.org, RFC Errata System <rfc-editor@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 01:06:07 -0000

This is a multipart message in MIME format.
--=_alternative 0006084785257CB0_=
Content-Type: text/plain; charset="US-ASCII"

Which reminds me of a family expression.

My father was part of the 1950s Brain Drain, and left RRE in England to go 
to UBC in Vancouver in 1956.  Another British physicist, Geoff Bates, 
joined the Physics Department at the same time. 

The head of the Physics Department was very proud of the fact that the 
faculty gathered for "tea" each afternoon, and were very  anxious to have 
the two British additions join them.

After tasting the "tea" Geoff said: "Hmm, it is quite good, but it will 
never replace tea."

The expression "It is quite good but it will never replace X" is now 
firmly established in the Gunn family lexicon.

Janet

"ietf" <ietf-bounces@ietf.org> wrote on 04/02/2014 08:01:52 PM:

> From: John C Klensin <john-ietf@jck.com>
> 
> 
> 
> At least until you answer the question "when is tea not tea" in
> a satisfactory way.  For example, the stuff that comes
> identified as tea but arrives in bags in many bad restaurants
> (and others that should know better), is pretty clearly not tea
> but it is less clear whether it is not-tea or not.
> 
> 
> 
> 
> 

--=_alternative 0006084785257CB0_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Which reminds me of a family expression.</font>
<br>
<br><font size=2 face="sans-serif">My father was part of the 1950s Brain
Drain, and left RRE in England to go to UBC in Vancouver in 1956. &nbsp;Another
British physicist, Geoff Bates, joined the Physics Department at the same
time. </font>
<br>
<br><font size=2 face="sans-serif">The head of the Physics Department was
very proud of the fact that the faculty gathered for &quot;tea&quot; each
afternoon, and were very &nbsp;anxious to have the two British additions
join them.</font>
<br>
<br><font size=2 face="sans-serif">After tasting the &quot;tea&quot; Geoff
said: &quot;Hmm, it is quite good, but it will never replace tea.&quot;</font>
<br>
<br><font size=2 face="sans-serif">The expression &quot;It is quite good
but it will never replace X&quot; is now firmly established in the Gunn
family lexicon.<br>
<br>
Janet</font>
<br>
<br><tt><font size=2>&quot;ietf&quot; &lt;ietf-bounces@ietf.org&gt; wrote
on 04/02/2014 08:01:52 PM:<br>
<br>
&gt; From: John C Klensin &lt;john-ietf@jck.com&gt;</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; <br>
&gt; <br>
&gt; At least until you answer the question &quot;when is tea not tea&quot;
in<br>
&gt; a satisfactory way. &nbsp;For example, the stuff that comes<br>
&gt; identified as tea but arrives in bags in many bad restaurants<br>
&gt; (and others that should know better), is pretty clearly not tea<br>
&gt; but it is less clear whether it is not-tea or not.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
</font></tt>
--=_alternative 0006084785257CB0_=--


From nobody Thu Apr  3 18:20:11 2014
Return-Path: <jgunn6@csc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EA841A02B2; Thu,  3 Apr 2014 18:20:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 olqfA5qUP7mJ; Thu,  3 Apr 2014 18:20:01 -0700 (PDT)
Received: from mail171.messagelabs.com (mail171.messagelabs.com [216.82.253.243]) by ietfa.amsl.com (Postfix) with ESMTP id 15E4D1A0349; Thu,  3 Apr 2014 18:20:00 -0700 (PDT)
X-Env-Sender: jgunn6@csc.com
X-Msg-Ref: server-16.tower-171.messagelabs.com!1396574393!17491973!1
X-Originating-IP: [20.137.2.180]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10427 invoked from network); 4 Apr 2014 01:19:54 -0000
Received: from amer-mta103.csc.com (HELO amer-mta113.csc.com) (20.137.2.180) by server-16.tower-171.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP;  4 Apr 2014 01:19:54 -0000
Received: from amer-gw15.amer.csc.com (amer-gw15.amer.csc.com [20.137.2.189]) by amer-mta113.csc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id s341Jrse030580; Thu, 3 Apr 2014 21:19:53 -0400
In-Reply-To: <p06240603cf639ebf8c0d@[99.111.97.136]>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom> <p06240603cf639ebf8c0d@[99.111.97.136]>
To: Randall Gellens <randy@qti.qualcomm.com>
MIME-Version: 1.0
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
X-KeepSent: 49BF796B:DDACCEB7-85257CB0:000642CC; type=4; name=$KeepSent
X-Mailer: Lotus Notes Release 8.5.2FP4 SHF97 March 26, 2012
From: Janet P Gunn <jgunn6@csc.com>
Message-ID: <OF49BF796B.DDACCEB7-ON85257CB0.000642CC-85257CB0.0007509E@csc.com>
Date: Thu, 3 Apr 2014 21:19:53 -0400
X-MIMETrack: Serialize by Router on AMER-GW15/SRV/CSC(Release 8.5.2FP3 HF666|December 11, 2012) at 04/03/2014 09:19:53 PM, Serialize complete at 04/03/2014 09:19:53 PM
Content-Type: multipart/alternative; boundary="=_alternative 0007503385257CB0_="
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dARjAmb_PktM9FTJ3-f47FrQwmU
Cc: ietf <ietf-bounces@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 01:20:08 -0000

This is a multipart message in MIME format.
--=_alternative 0007503385257CB0_=
Content-Type: text/plain; charset="US-ASCII"

The teamaker that sits on my desk at work allows me to select from 4 
different temperature settings ( appropriate for black tea, herbal tea, 
green tea, and white tea).  It also allows me to select the number of 
minutes to brew the tea.

I would expect the tea making protocol to allow for "water temperature" 
and "brewing time" parameters.

Furthermore, brewing time is a much better metric for tea strength than 
opacity.  One of the best known "teas"  sold in the US is well known to 
have been designed for speed in reaching a dark color, without regard for 
strength.

Stewed tea is tea which has been brewed too long.  Tea which has been kept 
warm for a long time, but with the tea leaves removed after the proper 
brewing time, is not "stewed".  It may be stale, but not stewed.

Some people actually LIKE stewed tea (usually with lots of sugar), so an 
extended brewing time should be an option.

Janet


"ietf" <ietf-bounces@ietf.org> wrote on 04/03/2014 07:29:37 PM:

> From: Randall Gellens <randy@qti.qualcomm.com>
> To: Elwyn Davies <elwynd@dial.pipex.com>, "Andrew G. Malis" 
> <agmalis@gmail.com>
> Cc: IETF Discussion <ietf@ietf.org>
> Date: 04/03/2014 07:32 PM
> Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol 
> for Tea  Efflux Appliances (HTCPCP-TEA)
> Sent by: "ietf" <ietf-bounces@ietf.org>
> 
> At 12:37 AM +0100 4/2/14, Elwyn Davies wrote:
> 
> >  We also need the internationalized version to cater for all those
> >  excellent varieties of China Tea.  A nice drop of pu-erh perhaps?
> 
> I stopped reading when I saw that there was no provision for handling 
> more delicate teas, just as Japanese sencha or gyokuro, which require 
> significantly cooler water and shorter brewing times.  I'm not sure 
> I'd characterize this as a question of internationalization, since it 
> involves fundamental protocol elements and operation rather than user 
> display text.
> 
> -- 
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself only
> -------------- Randomly selected tag: ---------------
> The single biggest problem in communication is the illusion that it
> has taken place.                                       --G. B. Shaw
> 

--=_alternative 0007503385257CB0_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif"><br>
The teamaker that sits on my desk at work allows me to select from 4 different
temperature settings ( appropriate for black tea, herbal tea, green tea,
and white tea). &nbsp;It also allows me to select the number of minutes
to brew the tea.</font>
<br>
<br><font size=2 face="sans-serif">I would expect the tea making protocol
to allow for &quot;water temperature&quot; and &quot;brewing time&quot;
parameters.</font>
<br>
<br><font size=2 face="sans-serif">Furthermore, brewing time is a much
better metric for tea strength than opacity. &nbsp;One of the best known
&quot;teas&quot; &nbsp;sold in the US is well known to have been designed
for speed in reaching a dark color, without regard for strength.</font>
<br>
<br><font size=2 face="sans-serif">Stewed tea is tea which has been brewed
too long. &nbsp;Tea which has been &nbsp;kept warm for a long time, but
with the tea leaves removed after the proper brewing time, is not &quot;stewed&quot;.
&nbsp;It may be stale, but not stewed.</font>
<br>
<br><font size=2 face="sans-serif">Some people actually LIKE stewed tea
(usually with lots of sugar), so an extended brewing time should be an
option.</font>
<br>
<br><font size=2 face="sans-serif">Janet<br>
</font>
<br>
<br><tt><font size=2>&quot;ietf&quot; &lt;ietf-bounces@ietf.org&gt; wrote
on 04/03/2014 07:29:37 PM:<br>
<br>
&gt; From: Randall Gellens &lt;randy@qti.qualcomm.com&gt;</font></tt>
<br><tt><font size=2>&gt; To: Elwyn Davies &lt;elwynd@dial.pipex.com&gt;,
&quot;Andrew G. Malis&quot; <br>
&gt; &lt;agmalis@gmail.com&gt;</font></tt>
<br><tt><font size=2>&gt; Cc: IETF Discussion &lt;ietf@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; Date: 04/03/2014 07:32 PM</font></tt>
<br><tt><font size=2>&gt; Subject: Re: RFC 7168 on The Hyper Text Coffee
Pot Control Protocol <br>
&gt; for Tea &nbsp;Efflux Appliances (HTCPCP-TEA)</font></tt>
<br><tt><font size=2>&gt; Sent by: &quot;ietf&quot; &lt;ietf-bounces@ietf.org&gt;</font></tt>
<br><tt><font size=2>&gt; <br>
&gt; At 12:37 AM +0100 4/2/14, Elwyn Davies wrote:<br>
&gt; <br>
&gt; &gt; &nbsp;We also need the internationalized version to cater for
all those<br>
&gt; &gt; &nbsp;excellent varieties of China Tea. &nbsp;A nice drop of
pu-erh perhaps?<br>
&gt; <br>
&gt; I stopped reading when I saw that there was no provision for handling
<br>
&gt; more delicate teas, just as Japanese sencha or gyokuro, which require
<br>
&gt; significantly cooler water and shorter brewing times. &nbsp;I'm not
sure <br>
&gt; I'd characterize this as a question of internationalization, since
it <br>
&gt; involves fundamental protocol elements and operation rather than user
<br>
&gt; display text.<br>
&gt; <br>
&gt; -- <br>
&gt; Randall Gellens<br>
&gt; Opinions are personal; &nbsp; &nbsp;facts are suspect; &nbsp; &nbsp;I
speak for myself only<br>
&gt; -------------- Randomly selected tag: ---------------<br>
&gt; The single biggest problem in communication is the illusion that it<br>
&gt; has taken place. &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;
&nbsp; --G. B. Shaw<br>
&gt; <br>
</font></tt>
--=_alternative 0007503385257CB0_=--


From nobody Thu Apr  3 19:04:40 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DAE2D1A0056 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 19:04:38 -0700 (PDT)
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] autolearn=ham
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 79zVfJulMod4 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 19:04:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 733A41A0055 for <ietf@ietf.org>; Thu,  3 Apr 2014 19:04:34 -0700 (PDT)
Received: from [192.168.2.36] (adsl-108-81-170-124.dsl.pltn13.sbcglobal.net [108.81.170.124]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3424Pcl025825 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 3 Apr 2014 19:04:28 -0700
Message-ID: <533E12BF.9080308@dcrocker.net>
Date: Thu, 03 Apr 2014 19:02:39 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <01P67T1X0MI000004W@mauve.mrochek.com> <533DFC4F.2040902@gmail.com>
In-Reply-To: <533DFC4F.2040902@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 03 Apr 2014 19:04:29 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Bk---N09xeD1xmW05YJnvrhPkhY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 02:04:39 -0000

On 4/3/2014 5:26 PM, Brian E Carpenter wrote:
> I think we need to distinguish various
> quite separate issues. Off the top of my head, I can see:

What I like most about Brian's list is that it seeks to gain some 
discipline an clarity about what might be done and why.  As Ned's 
responses shows, this requires even more clarity and -- depending on 
what answers we give -- different difficulty.



On 4/3/2014 5:29 PM, Randy Bush wrote:
 > because we blew it way back when, by designing a completely insecure
 > and un-private internet.  as supposedly responsible and occasionally
 > competent engineers, we should rectify our mistakes.

This promotes a collection of popular myths which both give a false 
history and a false (and counter-productively distracting) present.

The presumption that 'security' was ignored "way back" is simply wrong. 
  Both in the 70s and again in the 90s, security issues were given 
attention.  In the 70s, the primary answer was encryption boxes, for 
those special cases deem to need them.  In terms of the technology of 
the day, when combined with the nature of the scale and use of the 
Arpanet and eventually Internet, that was a reasonable choice.

In the 90s, we got PEM, PGP, S/MIME and the beginnings of DNSSec.

The experience of the 90s nicely highlights the problem with the second 
myth, that we merely needed to 'decide' to do 'security'.  As the 
increasing list of problematic security-related efforts over the last 25 
years demonstrate, doing 'security' for Internet scale and diversity is 
a challenge, often appearing to be beyond the state of the art.

Note how little DNSSec we still have.  Note how little PGP and S/MIME 
use we still have.  All three of those were diligent, reasonable design 
efforts.  Yet their deployment and use remains problematic.

Added to this is that the word 'security' is almost completely 
meaningless in technical terms.  For most technical discussions, it's so 
vague there's no way to know what specific problems are of concern or 
what functions are intended.

So please, let's focus on the kind of disciplined, targeted effort that 
Brian is promoting to consider needs and solutions, and move away from 
mythology.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Thu Apr  3 19:07:16 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB7221A04E9 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 19:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 x8_3_huanBGm for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 19:07:08 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id E6DB41A04C5 for <ietf@ietf.org>; Thu,  3 Apr 2014 19:07:07 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WVtX4-0004Dq-8L; Fri, 04 Apr 2014 02:07:02 +0000
Date: Fri, 04 Apr 2014 11:07:00 +0900
Message-ID: <m2mwg1voe3.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Lloyd Wood <L.Wood@surrey.ac.uk>
Subject: Re: Security for various IETF services
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEB8@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DneVNss4aEooZMNMqa4aNEc5mro
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 02:07:14 -0000

> "because we blew it way back when, by designing a completely insecure
> and un-private internet"
> That was not a mistake. That is what made adoption possible.

this is not clear.  though, certainly, crypto would have had serious
performance impact in the ealy '80s.  then again, if at 9600 baud, you
can afford a bit of processing on the ends. :)

> DTN started with security from the get-go, and DTN has gone nowhere.

i was not aware that security was a major cause of the lack of success
of the dtn.

randy


From nobody Thu Apr  3 19:08:20 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED0911A04D2 for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 19:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 a61-GrxqIf1r for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 19:08:13 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 7B8101A0055 for <ietf@ietf.org>; Thu,  3 Apr 2014 19:08:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1396577290; x=1428113290; h=message-id:in-reply-to:references:date:to:from:subject: mime-version; bh=ol0RUdWc0NASSuBblVW6TGKH+OMUI09TDcQahv9EEUg=; b=indpya8yrd7ZWVi3FQtbaU8XOsqyOMQ2+0Ti0XLcCwARM6kRV3uBlR5E 2+LTbABKs+ZxXCk7IXdr434LBt85tteaW0TNHD6MBVr3sWt1qdY4kdahv uni2HETXAQoti0U+PY+wjJGWBdnguhqkdWsIw/IOaEXc1l2Ir7zpTn5hX 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,7397"; a="117614664"
Received: from ironmsg01-lv.qualcomm.com ([10.47.202.180]) by wolverine02.qualcomm.com with ESMTP; 03 Apr 2014 19:08:10 -0700
X-IronPort-AV: E=Sophos;i="4.97,791,1389772800"; d="scan'208";a="29491828"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg01-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 03 Apr 2014 19:08:10 -0700
Received: from [99.111.97.136] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 3 Apr 2014 19:08:08 -0700
Message-ID: <p06240605cf63c268e7df@[99.111.97.136]>
In-Reply-To: <533DF52E.5020707@cis-india.org>
References: <533D8A90.60309@cs.tcd.ie> <533DF52E.5020707@cis-india.org>
X-Mailer: Eudora for Mac OS X
Date: Thu, 3 Apr 2014 19:00:18 -0700
To: Pranesh Prakash <pranesh@cis-india.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF-Discussion <ietf@ietf.org>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: Security for various IETF services
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tTw-dpTYD5vTJoQzl5Z5BLcrJv4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 02:08:18 -0000

At 7:56 PM -0400 4/3/14, Pranesh Prakash wrote:

>>  However, as there are numerous legacy tools that have been
>>  built that require access via cleartext
>
>  Could you please expand on this?  What kinds of legacy tools is 
> that statement talking about?

I have a number of tools and scripts that access IETF and RFC Editor 
documents and information using HTTP and FTP.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
f u cn rd ths, itn tyg h myxbl cd.


From nobody Thu Apr  3 19:46:46 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D5771A022D for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 19:46:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 t1FAOSt2f_RF for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 19:46:41 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.177]) by ietfa.amsl.com (Postfix) with ESMTP id 4B4661A01B3 for <ietf@ietf.org>; Thu,  3 Apr 2014 19:46:41 -0700 (PDT)
Received: from [85.158.137.99:58309] by server-17.bemta-3.messagelabs.com id C2/AB-22741-C0D1E335; Fri, 04 Apr 2014 02:46:36 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-13.tower-217.messagelabs.com!1396579595!2342123!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20629 invoked from network); 4 Apr 2014 02:46:35 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-13.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 4 Apr 2014 02:46:35 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Fri, 4 Apr 2014 03:46:35 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@psg.com>
Date: Fri, 4 Apr 2014 03:46:34 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9PqpP+tuS8n2OdSEuWeD+29/r+ygABJ1OM
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEB9@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>, <m2mwg1voe3.wl%randy@psg.com>
In-Reply-To: <m2mwg1voe3.wl%randy@psg.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kd-xGT8wIsOrA1Agc9un5f_aq4s
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 02:46:46 -0000

Randy,

Security was encouraged to be the primary focus of the
DTNRG research group, above and beyond application
scenarios, or anything else. Examining years of list
discussion will confirm that. It's what happens when
you let security people run things as they see fit,
with their natural bias towards security above all
else.

Focus on security, you can get security. You won't get
users, or anything useful for the scenario,
but you can get security.


Lloyd Wood
http://sat-net.com/L.Wood/dtn
________________________________________
From: Randy Bush [randy@psg.com]
Sent: 04 April 2014 03:07
To: Wood L  Dr (Electronic Eng)
Cc: IETF Disgust
Subject: Re: Security for various IETF services

> "because we blew it way back when, by designing a completely insecure
> and un-private internet"
> That was not a mistake. That is what made adoption possible.

this is not clear.  though, certainly, crypto would have had serious
performance impact in the ealy '80s.  then again, if at 9600 baud, you
can afford a bit of processing on the ends. :)

> DTN started with security from the get-go, and DTN has gone nowhere.

i was not aware that security was a major cause of the lack of success
of the dtn.

randy


From nobody Thu Apr  3 21:53:24 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A70241A00BB for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 21:53:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.012
X-Spam-Level: 
X-Spam-Status: No, score=-5.012 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 wuMBtnSLNGSo for <ietf@ietfa.amsl.com>; Thu,  3 Apr 2014 21:53:10 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id 5CFE21A001A for <ietf@ietf.org>; Thu,  3 Apr 2014 21:53:10 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 3 Apr 2014 22:53:05 -0600
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 3 Apr 2014 22:53:04 -0600
Received: from b01cxnp22036.gho.pok.ibm.com (b01cxnp22036.gho.pok.ibm.com [9.57.198.26]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id 9F708C90041 for <ietf@ietf.org>; Fri,  4 Apr 2014 00:52:59 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by b01cxnp22036.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s344r3nd4653364 for <ietf@ietf.org>; Fri, 4 Apr 2014 04:53:03 GMT
Received: from d01av03.pok.ibm.com (localhost [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s344r3KW022270 for <ietf@ietf.org>; Fri, 4 Apr 2014 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s344r336022257 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 4 Apr 2014 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s344r2qV010930 for <ietf@ietf.org>; Fri, 4 Apr 2014 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s344r1AO010872 for ietf@ietf.org; Fri, 4 Apr 2014 00:53:01 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201404040453.s344r1AO010872@rotala.raleigh.ibm.com>
Date: Fri, 04 Apr 2014 00:53:01 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14040404-9332-0000-0000-00000056A529
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kJR0yKqgOf_XgQhJVXZT3Mh8c8U
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 04:53:20 -0000

Total of 114 messages in the last 7 days.
 
script run at: Fri Apr  4 00:53:01 EDT 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.02% |    8 |  5.48% |    48559 | ted.lemon@nominum.com
  6.14% |    7 |  5.96% |    52844 | john-ietf@jck.com
  5.26% |    6 |  5.84% |    51744 | hsantos@isdg.net
  5.26% |    6 |  4.17% |    36997 | johnl@taugh.com
  5.26% |    6 |  3.45% |    30595 | randy@psg.com
  3.51% |    4 |  4.76% |    42208 | hallam@gmail.com
  4.39% |    5 |  3.69% |    32745 | randy@qti.qualcomm.com
  3.51% |    4 |  3.29% |    29192 | l.wood@surrey.ac.uk
  3.51% |    4 |  2.98% |    26390 | dhc@dcrocker.net
  2.63% |    3 |  2.98% |    26438 | fred@cisco.com
  2.63% |    3 |  2.29% |    20258 | lear@cisco.com
  2.63% |    3 |  2.27% |    20137 | elwynd@dial.pipex.com
  1.75% |    2 |  3.10% |    27439 | olejacobsen@me.com
  1.75% |    2 |  2.46% |    21809 | eric@notcom.com
  1.75% |    2 |  2.26% |    20054 | jgunn6@csc.com
  1.75% |    2 |  2.14% |    18956 | clint.chaplin@gmail.com
  1.75% |    2 |  2.06% |    18249 | dave@cridland.net
  1.75% |    2 |  1.64% |    14566 | brian.e.carpenter@gmail.com
  0.88% |    1 |  2.49% |    22064 | chaitanyabd@gmail.com
  1.75% |    2 |  1.56% |    13867 | ned+ietf@mauve.mrochek.com
  1.75% |    2 |  1.51% |    13348 | worley@ariadne.com
  1.75% |    2 |  1.40% |    12446 | scott.brim@gmail.com
  1.75% |    2 |  1.39% |    12306 | dwm@xpasc.com
  0.88% |    1 |  1.32% |    11678 | ron.even.tlv@gmail.com
  0.88% |    1 |  1.30% |    11522 | david.black@emc.com
  0.88% |    1 |  1.27% |    11276 | mukom.tamon@gmail.com
  0.88% |    1 |  1.18% |    10481 | gvandeve@cisco.com
  0.88% |    1 |  1.17% |    10390 | daedulus@btconnect.com
  0.88% |    1 |  1.10% |     9754 | rpelletier@isoc.org
  0.88% |    1 |  1.05% |     9305 | ynir.ietf@gmail.com
  0.88% |    1 |  1.05% |     9275 | tjc@ecs.soton.ac.uk
  0.88% |    1 |  1.03% |     9154 | a.arsenault.81@gmail.com
  0.88% |    1 |  1.01% |     8994 | rwfranks@acm.org
  0.88% |    1 |  1.01% |     8981 | adrian@olddog.co.uk
  0.88% |    1 |  1.00% |     8839 | rgd.ietf@gmail.com
  0.88% |    1 |  0.98% |     8690 | abdussalambaryun@gmail.com
  0.88% |    1 |  0.98% |     8662 | huitema@microsoft.com
  0.88% |    1 |  0.96% |     8519 | serrhini@mail.ru
  0.88% |    1 |  0.96% |     8516 | iab-chair@iab.org
  0.88% |    1 |  0.94% |     8346 | narten@us.ibm.com
  0.88% |    1 |  0.89% |     7848 | doug.mtview@gmail.com
  0.88% |    1 |  0.88% |     7788 | wesley.george@twcable.com
  0.88% |    1 |  0.85% |     7540 | agmalis@gmail.com
  0.88% |    1 |  0.83% |     7388 | superuser@gmail.com
  0.88% |    1 |  0.83% |     7343 | thierry.moreau@connotech.com
  0.88% |    1 |  0.77% |     6843 | suzworldwide@gmail.com
  0.88% |    1 |  0.74% |     6595 | pranesh@cis-india.org
  0.88% |    1 |  0.74% |     6580 | leaf.yeh.sdo@gmail.com
  0.88% |    1 |  0.73% |     6459 | mcr+ietf@sandelman.ca
  0.88% |    1 |  0.72% |     6403 | stephen.farrell@cs.tcd.ie
  0.88% |    1 |  0.69% |     6079 | ietf2dave@davearonson.com
  0.88% |    1 |  0.67% |     5912 | julian.reschke@gmx.de
  0.88% |    1 |  0.65% |     5760 | ajs@anvilwalrusden.com
  0.88% |    1 |  0.64% |     5664 | kevin@ageispolis.net
  0.88% |    1 |  0.64% |     5638 | hartmans-ietf@mit.edu
  0.88% |    1 |  0.63% |     5608 | chair@ietf.org
  0.88% |    1 |  0.61% |     5415 | mellon@fugue.com
--------+------+--------+----------+------------------------
100.00% |  114 |100.00% |   886456 | Total


From nobody Fri Apr  4 02:36:02 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D8A31A0442 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 02:36:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level: 
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
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 Ver-2n8ZFjtw for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 02:35:56 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0082.outbound.protection.outlook.com [213.199.154.82]) by ietfa.amsl.com (Postfix) with ESMTP id EE2E31A0429 for <ietf@ietf.org>; Fri,  4 Apr 2014 02:35:55 -0700 (PDT)
Received: from AMXPRD0310HT005.eurprd03.prod.outlook.com (157.56.248.133) by DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) with Microsoft SMTP Server (TLS) id 15.0.908.10; Fri, 4 Apr 2014 09:35:50 +0000
Message-ID: <01ec01cf4fe9$0a4e1f60$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <stephen.farrell@cs.tcd.ie>, <ietf@ietf.org>, Randall Gellens <randy@qti.qualcomm.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]>
Subject: Re: Security for various IETF services
Date: Fri, 4 Apr 2014 09:48:32 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.248.133]
X-ClientProxiedBy: DBXPR07CA020.eurprd07.prod.outlook.com (10.141.8.178) To DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153)
X-Forefront-PRVS: 01713B2841
X-Forefront-Antispam-Report: =?iso-8859-1?Q?SFV:NSPM; SFS:(10009001)(6009001)(428001)(13464003)(189002)?= =?iso-8859-1?Q?(199002)(377454003)(77982001)(20776003)(47776003)(47446002?= =?iso-8859-1?Q?)(74502001)(31966008)(59766001)(84392001)(74366001)(237560?= =?iso-8859-1?Q?03)(85852003)(93516002)(65816001)(93136001)(44716002)(1958?= =?iso-8859-1?Q?0405001)(74662001)(63696002)(79102001)(54316002)(94946001)?= =?iso-8859-1?Q?(94316002)(92726001)(56776001)(86362001)(93916002)(1958039?= =?iso-8859-1?Q?5003)(83322001)(56816005)(47976001)(47736001)(33646001)(80?= =?iso-8859-1?Q?022001)(92566001)(89996001)(51856001)(87976001)(66066001)(?= =?iso-8859-1?Q?95416001)(4396001)(88136002)(50466002)(74706001)(61296002)?= =?iso-8859-1?Q?(53806001)(69226001)(87286001)(90146001)(85306002)(4218600?= =?iso-8859-1?Q?4)(44736004)(97336001)(62966002)(97186001)(76786001)(76482?= =?iso-8859-1?Q?001)(76796001)(80976001)(98676001)(77096001)(81542001)(509?= =?iso-8859-1?Q?86001)(87266001)(50226001)(83072002)(62236002)(95666003)(1?= =?iso-8859-1?Q?4496001)(46102001)(99396002)(49866001)(74876001)(81342001)?= =?iso-8859-1?Q?(77156001)(74416001)(7726001);DIR:OUT;SFP:1101;SCL:1;SRVR:?= =?iso-8859-1?Q?DB4PR07MB252;H:AMXPRD0310HT005.eurprd03.prod.outlook.com;F?= =?iso-8859-1?Q?PR:DA48F255.A538D4DA.FCF32D8B.90F7E960.2036B;MLV:nov;PTR:I?= =?iso-8859-1?Q?nfoNoRecords;MX:1;A:0;LANG:en;?=
Received-SPF: None (: btconnect.com does not designate permitted sender hosts)
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nalh4OrScBO7rId5j-BIFpNDFAI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 09:36:00 -0000

----- Original Message -----
From: "Randall Gellens" <randy@qti.qualcomm.com>
To: <l.wood@surrey.ac.uk>; <stephen.farrell@cs.tcd.ie>; <ietf@ietf.org>
Sent: Friday, April 04, 2014 12:24 AM
Subject: RE: Security for various IETF services


> My reaction is also to ask "Why?"  Security and privacy involve
> trade-offs where various costs (including operational difficulty) are
> weighed against the benefits, such as protecting information from
> unauthorized disclosure or modification.  So, I'd suggest that a
> blanket statement isn't a good idea, but rather, a service-by-service
> decision should be made.  For example, XMPP and document submission
> may justify requiring encryption while email and document retrieval
> might not.

Yes, it is a trade off, a more secure service, for some meaning of
security, but a worse service for some users or usages.

Setting up a TLS session takes time; I notice every time I access
e-mail, ever since my ISP required the use of TLS.   It is only a few
seconds, but it means that I batch my usage rather than doing it
promptly, and every so often forget and shut down without having sent a
message in reply.  And certainly with that e-mail access, it is forever
tearing down the TLS session and creating a new one, e.g. between
sending e-mail on an account and receiving it from the same account, so
one (unmet) requirement is that having gone to the cost of setting up a
session, it stays up and is reused.

And then there is CRL checking.  I would assume that that would be
recommended as part of a secure system, yet with the IETF website, that
hangs the session.  The CRL is downloaded and ......  hours later, the
web page has yet to display.  There is something weird about the IETF's
use of certificates which other websites do not share.  Surmountable no
doubt but it means that a secure service is a worse service than that
obtainable via HTTP.

And what threat is this trying to counter? a corrupted DNS directing me
to a phishing website of a foreign power?

Tom Petch


> --
> Randall Gellens


From nobody Fri Apr  4 06:04:30 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9A8D1A0182 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 06:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01, T_TVD_FUZZY_SECURITIES=0.01] autolearn=ham
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 iV58LE7RxSdH for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 06:04:21 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 044341A0169 for <ietf@ietf.org>; Fri,  4 Apr 2014 06:04:19 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WW3mt-000DFa-5R; Fri, 04 Apr 2014 09:04:03 -0400
Date: Fri, 04 Apr 2014 09:03:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randall Gellens <randy@qti.qualcomm.com>, Pranesh Prakash <pranesh@cis-india.org>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
Message-ID: <2A0E1EB4BED37EB84AEF66E0@JcK-HP8200.jck.com>
In-Reply-To: <p06240605cf63c268e7df@[99.111.97.136]>
References: <533D8A90.60309@cs.tcd.ie> <533DF52E.5020707@cis-india.org> <p06240605cf63c268e7df@[99.111.97.136]>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/T9tZ_L3WIj8Xjb3JEdTmQh7SKP0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 13:04:26 -0000

--On Thursday, April 03, 2014 19:00 -0700 Randall Gellens
<randy@qti.qualcomm.com> wrote:

> At 7:56 PM -0400 4/3/14, Pranesh Prakash wrote:
> 
>>>  However, as there are numerous legacy tools that have been
>>>  built that require access via cleartext
>> 
>>  Could you please expand on this?  What kinds of legacy tools
>>  is  that statement talking about?
> 
> I have a number of tools and scripts that access IETF and RFC
> Editor documents and information using HTTP and FTP.

I do too and more with FTP than HTTP.  This is not just being
old and set in my ways (age being both the tools and about me).
Many of the tools that use HTTP can't make up their minds (or
need special handling) to deliver an XML file to me rather that
deciding they "really" know what I intend and trying to
render/interpret it, while FTP always does what it is told and
retrieves the d**m file.  My preferred reading tools for I-Ds
and RFCs and my preferred editing tools for I-Ds involve an
emacs clone text editor.  It provides a very satisfactory
solution, a range of paging and text tools, a satisfactory XML
editing experience, and a largely platform-independent
consistent interface.  Given that, I'm loathe to seek out and
learn something new and shiny and, having looked around, I'm not
convinced that doing so would bring any real benefit.

More important from the security front, although, in this case,
it more a matter of principle than a serious concern, it is none
of the IETF's, or anyone else's, business what files I retrieve
and when.  I don't want to be authenticated unless there is a
demonstrated and persuasive need that gets community consensus;
I don't want logs kept at all; and, by the way, I don't want web
beacons in my mail from IETF lists because some future genius
decides that better service could be provided by analyzing what
is read and when.  

In addition, if I want to set up caches for documents (or even
shadows of directories) or trick routing, whether to protect my
privacy, improve performance, or because I'm perverse. I don't
think the IETF should be "helping" me and someone else's
perception of what security issues I think (or should think) are
important by getting in the way (with SSL/TLS or anything else).

IMO, the IESG needs to carefully consider whether better privacy
and security, especially for access to public documents, lies in
more anonymity and openness rather than in more restrictive and
powerful tools whose side-effects may be to compromise that
anonymity.  The answer will inevitably be different for
different cases, but these knee-jerk "need more security"
reactions are just bad systems engineering.

Finally, like (I assume) many others here, I don't have a lot of
spare time on my hands [1].  Time that goes into following one
of these procedural threads, questions from the IAOC, etc., is
time that doesn't get spent on substantive work for the IETF.
So I really wish that the IESG and IAOC would keep their
responsibility for facilitating getting technical/ standards
work around here in the front of their minds and ask themselves
(and maybe each other) hard questions about relative importance
of each of their trial balloons and inquiries.

    john

p.s. I also agree with most of Dave Crocker's recent analyses
and comments.  That is becoming a scary trend :-)


Any time someone needs to think about or discuss data retention
policies, security of logs, or the like, I think we first need
to have a discussion of why we need to collect the data in the
first place.

[1] Sorry, I type rapidly enough that it doesn't predict to
messages that are so short and pointed as to seem cryptic.  But
I am sending a lot fewer of them.


From nobody Fri Apr  4 06:15:38 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 486EB1A0175 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 06:15:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 mVl4W55PFAQq for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 06:15:31 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id D8C561A015F for <ietf@ietf.org>; Fri,  4 Apr 2014 06:15:31 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6B5781B8062 for <ietf@ietf.org>; Fri,  4 Apr 2014 06:15:27 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 611ED190043; Fri,  4 Apr 2014 06:15:27 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 4 Apr 2014 06:15:27 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <01ec01cf4fe9$0a4e1f60$4001a8c0@gateway.2wire.net>
Date: Fri, 4 Apr 2014 09:15:29 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <8988DC95-A4AB-490B-93D7-18D3F50E7639@nominum.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <01ec01cf4fe9$0a4e1f60$4001a8c0@gateway.2wire.net>
To: t.p. <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FiJxU2JpfGONO331RynkAYhRWGk
Cc: Randall Gellens <randy@qti.qualcomm.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 13:15:36 -0000

On Apr 4, 2014, at 4:48 AM, t.p. <daedulus@btconnect.com> wrote:
> Setting up a TLS session takes time; I notice every time I access
> e-mail, ever since my ISP required the use of TLS.   It is only a few
> seconds,

Whaaat?   It takes a few SECONDS for your MUA to set up a TLS =
connection?   Something is broken.   This is not a TLS problem.  It's =
probably either a load problem on your IMAP store, or bufferbloat on =
your network causing unreasonable round trip times=97if your RTT to the =
IMAP store is 1000ms, then sure, it could take a couple of seconds to =
set up a TLS connection.

Similarly, if there's a bug in IETF's CRL support, that should be fixed =
regardless of the ultimate outcome of this discussion.


From nobody Fri Apr  4 06:25:48 2014
Return-Path: <john@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D4CA1A0182 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 06:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 zdNbdxF4BmMr for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 06:25:42 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 24C321A017C for <ietf@ietf.org>; Fri,  4 Apr 2014 06:25:42 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john@jck.com>) id 1WW47k-000DGu-1J; Fri, 04 Apr 2014 09:25:36 -0400
Date: Fri, 04 Apr 2014 09:25:30 -0400
From: John C Klensin <john@jck.com>
To: ned+ietf@mauve.mrochek.com, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Security for various IETF services
Message-ID: <FEACD58B167F6AA60980844A@JcK-HP8200.jck.com>
In-Reply-To: <01P67VFG3GTG00004W@mauve.mrochek.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <01P67T1X0MI000004W@mauve.mrochek.com> <533DFC4F.2040902@gmail.com> <01P67VFG3GTG00004W@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/z4DsWculJCTlY8t6TxlzVn_UFJI
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 13:25:46 -0000

--On Thursday, April 03, 2014 17:44 -0700
ned+ietf@mauve.mrochek.com wrote:

>...
>> * authenticity and integrity of data coming from the IETF
>> site;
> 
> Your problem here is people get IETF data from many sources
> besides the IETF site. Indeed, alternative data stores may
> provide access alternatives for those concerned about being
> seen accessing IETF data in the obvious way.
> 
> As a result I don't see how transport security offers a
> meaningful solution here. We should instead be looking at
> various signature mechanisms.

Concur.  

If we think there is a real threat and problem that needs to be
solved in this area, we should see documents signed at the time
of posting and those signatures either made part of them or made
readily, easily, and obviously accessible along with any tools
needed to apply them.  We should also be sure that careful
questions are asked the relationship between signatures (or
other integrity-assurance) methods and the current IPR policies
allowing duplicates (should we require that the signatures be
preserved or explicit pointers to the authoritative, signed,
copies be provided?) and the RFC Editor's plans about multiple
output formats (e.g., is an integrity check over the XML file
adequate if there is no guarantee the that file recipient can
generate the user-accessible version?) and that answers
evaluated by experts.  Those are mostly technical issues --the
stuff we supposedly do well-- and need not be carried out on
this list, just competently reported to it.

More generally, I think the conclusion from Brian's remarks and
those of several others is that what is really needed here is a
serious analysis of what threats actually exist and whether we
care about them.   In the absence of a clear statement and
understanding of a problem and explanation of how a particular
technique will significantly mitigate it, these "we have a
technique, should we apply it" questions are, IMO, fairly
meaningless and a very bad example of the kind of engineering
the IETF should be advocating and demonstrating.

Back to trying to get substantive work done.
 
   john




From nobody Fri Apr  4 09:56:42 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 567C21A026E for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 09:56:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 oEgWHjZ2_EWM for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 09:56:36 -0700 (PDT)
Received: from mail-yh0-x22c.google.com (mail-yh0-x22c.google.com [IPv6:2607:f8b0:4002:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 20E721A0263 for <ietf@ietf.org>; Fri,  4 Apr 2014 09:56:36 -0700 (PDT)
Received: by mail-yh0-f44.google.com with SMTP id f10so3380354yha.17 for <ietf@ietf.org>; Fri, 04 Apr 2014 09:56:31 -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:from:date:message-id :subject:to:cc:content-type; bh=um0tfSdOIFdNODcIhOiQO2dtN+n3Ma8An83KlGRK0/s=; b=igGN5JTDkebNqD2ZuTMDj+LMAIX5Qu5p+WZDOK39JpBvjKjPckRg9fFcz5vmgNDFZt uihd+pwCIvgEqqlgqZGgr+Kdi2/I47L6gSLmvW8vbEM1R9yRu77WX5jm1Xo8LhzHKFjb Rx6rzNViGqxiskGK/yrM6ZSuW/ysZDbs7MCCDxS1Nz/6bhR2icMKgDnaaKZ98Gws95O2 WYXThhBnCiVlzHc3z1n5zT2BxfUJf3OnR/ICMaCeuzz61EyZ+SSrdJplbhl0TAB7yJKu hk3TMWq1hUAGTAvIjuSMNJyO7phEwqiciwgoJFM6eICuVPY8FsY//FbhLYdVQQmP5GpS MGOw==
X-Received: by 10.236.52.74 with SMTP id d50mr18618042yhc.44.1396630591467; Fri, 04 Apr 2014 09:56:31 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Fri, 4 Apr 2014 09:55:51 -0700 (PDT)
In-Reply-To: <FEACD58B167F6AA60980844A@JcK-HP8200.jck.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@99.111.97.136> <01P67T1X0MI000004W@mauve.mrochek.com> <533DFC4F.2040902@gmail.com> <01P67VFG3GTG00004W@mauve.mrochek.com> <FEACD58B167F6AA60980844A@JcK-HP8200.jck.com>
From: Dick Franks <rwfranks@acm.org>
Date: Fri, 4 Apr 2014 17:55:51 +0100
X-Google-Sender-Auth: adUZc7WbJeLY27dUgPDvWJm7wrk
Message-ID: <CAKW6Ri7NrTNxzt-E237aPT9+GSfe0Y5M9Lk0g8MeE47-AcQ5JQ@mail.gmail.com>
Subject: Re: Security for various IETF services
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec508f5164976fd04f63a6612
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VHwziELetIcods4KXS2yY_tiewI
Cc: ned+ietf@mauve.mrochek.com, John C Klensin <john@jck.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 16:56:41 -0000

--bcaec508f5164976fd04f63a6612
Content-Type: text/plain; charset=UTF-8

entia non sunt multiplicanda modulo p praeter necessitatem

--bcaec508f5164976fd04f63a6612
Content-Type: text/html; charset=UTF-8

<div dir="ltr"><br>entia non sunt multiplicanda modulo p praeter necessitatem<br><div class="gmail_extra"><br clear="all"><div></div></div></div>

--bcaec508f5164976fd04f63a6612--


From nobody Fri Apr  4 10:44:12 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 063911A02A5 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 10:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 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, USER_IN_WHITELIST=-100] autolearn=ham
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 HFACRVAOijGZ for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 10:44:06 -0700 (PDT)
Received: from listserv.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id F21D31A03A7 for <ietf@ietf.org>; Fri,  4 Apr 2014 10:43:31 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3132; t=1396633397; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=/uUlbdGCrM+e/8f9FnCLU+bipw8=; b=qbEk2+ZZdn3ldxyMA7tz cJD6UUKRNti4grMF0Cim5sHRchQVsZqItkAPVC/13r5HVgjPAJUSOkztD6BlZkPy /qHDfouHzUMyu+954r9ab1eIViGJTs+iAibUT/Wd3nj0QZO4PBHnOmtLpUeIRfxy w0B5t1DJXdSaq/pM/6b+LX0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 04 Apr 2014 12:43:17 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1620853330.3926.4536; Fri, 04 Apr 2014 12:43:16 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3132; t=1396633347; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=uRIB5/m 9QEG5WjsPqBZOR7pxdMFCCtr7zyZ5K1QlWPQ=; b=Qj2TtwVuKYGC9LsXII5gaGG V+e+W4Jjwr95idLmf60NB2SZlcOJ6qfs4gnXv3ERm5vyLJl6+L2nv0YnPf3fr4Se Vpu0KFs4PvbKckdhFc8retScuw+x0/BK48Tbg8Z15ezTGZbFQHG1gs9PtC7Z+c8l Kjdo8TpESAyXnQv7pOnA=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 04 Apr 2014 13:42:27 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1067103100.9.18440; Fri, 04 Apr 2014 13:42:26 -0400
Message-ID: <533EEF35.7070901@isdg.net>
Date: Fri, 04 Apr 2014 13:43:17 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>,  IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie>
In-Reply-To: <533D8A90.60309@cs.tcd.ie>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wvJlyyyM0FUZH9_mOrPcOaOm6kE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 17:44:11 -0000

I would add and be specific with the last sentence, for example, the 
IETF site
"new services" might need to be PCI/DSS compliant. This is especially 
the case if the IETF site is collecting credit card information for 
IETF meeting registrations or other purposes.  For logging in 
purposes, it may also need to be PCI/DSS compliant depending on the 
AUTH method. For DIGEST AUTH, it may require SSL and NONCE support. 
BASIC AUTH requires SSL, and it may not be sufficient for PCI/DSS 
unless there is other methods wrapping the BASIC AUTH process, i.e. a 
cookie method method. A form-based cookie login methods, where there 
is no standard protocol method, may require other conditions. 
Overall, there are areas at the IETF site that require updated, modern 
security-aware connection client access software to be used as 
required by industry standards such as PCI/DSS.  (I note, that this is 
probably USA, not sure how that applies in Europe, Asia, etc)

If fact, the IETF may not be running proper software that complies 
with PCI/DSS.

Maybe visiting one of the PCI/DSS resource/compliance sites can tell 
you what compliancy level the IETF site may fit.  Depending on what 
software is used, it may suffice or it may not, thus perhaps even 
adding new functional requirements to the IETF Web Site revamping project.

Hope this helps

--
HLS

On 4/3/2014 12:21 PM, Stephen Farrell wrote:
>
> Hi all,
>
>>From time to time the issue of how to secure IETF services
> comes up e.g. whether to turn on TLS for some IETF web server
> or jabber or mail etc.
>
> The most recent such was a request to turn on HSTS [1] for
> the IETF web site, which I don't think we can do without
> breaking old tools etc. Nonetheless we would like to turn
> on things like TLS more often going forward as seemed to
> me to be the outcome of a long thread on here late last
> year.
>
> So, the IESG are considering the following as an IESG
> statement to offer some guidance about this:
>
> "The IETF are committed to providing secure and privacy
> friendly access to information via the web, mail, jabber
> and other services. While most (but not all) data on IETF
> services is public, nonetheless access to that data
> should use best practices for security and privacy.
> However, as there are numerous legacy tools that have been
> built that require access via cleartext, the IETF will
> continue to allow such access so as not to break such
> tooling. New services will however generally only be made
> available in ways that use security protocols such as
> TLS."
>
> If you have wordsmithing changes to suggest please just send
> those to me or the iesg. More substantive comments should go
> here I guess. I hope the only bit worth discussing (except
> for the few folks who would rather we do none of this;-)
> might be the last sentence.
>
> A few weeks after any discussion here dies down I'll put the
> resulting text on an IESG telechat for approval if that seems
> like the right thing to do.
>
> Thanks,
> S
>
> [1] https://tools.ietf.org/html/rfc6797
>
>
>
>

-- 
HLS



From nobody Fri Apr  4 11:00:24 2014
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB1ED1A0442; Fri,  4 Apr 2014 11:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level: 
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3] autolearn=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 xri3qHX3ktxS; Fri,  4 Apr 2014 11:00:01 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A40831A0235; Fri,  4 Apr 2014 11:00:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: =?utf-8?q?Community_Input_Requested_on_Trustees=E2=80=99_Intent_to?= =?utf-8?q?_Renounce_=E2=80=9CIETF_Secretariat=E2=80=9D_Trademark?=
X-Test-IDTracker: no
X-IETF-IDTracker: 5.2.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
Date: Fri, 04 Apr 2014 11:00:01 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/52kB60c5A2DyMF7GCw92moSYTc8
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 18:00:06 -0000

All;

The Trustees of the IETF Trust have voted an intent to renounce (abandon) the â€œIETF Secretariatâ€� 
trademark, but before taking any action they desire to hear from the community.  

Specifically:  

It is the Trusteesâ€™ intent to:

1. Not renew the â€œIETF Secretariatâ€� trademark, Registration 3860848, in the European Community 
at an approximate cost of $5,000 USD for a ten-year period when due on May 28, 2014, and 
thereby renounce the trademark as having no foreseeable future value in accordance with Article 7.1a 
of the Amended and Restated Trust Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.  
The trademark has no foreseeable future value as the â€œIETFâ€� trademark is registered in the European 
Community and its use with Secretariat is protected.

2. Not renew the â€œIETF Secretariatâ€� trademark, Registration 2392833, in the United States at an unknown 
future cost when the trademark expires on October 10, 2020, and thereby renounce the trademark as 
having no foreseeable future value in accordance with Article 7.1a of the Amended and Restated Trust 
Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.  The trademark has no foreseeable 
future value as the â€œIETFâ€� trademark is registered in the United States and its use with Secretariat is 
protected.

Authority:

The Trustees have the authority to renounce the trademark in accordance with Article 7.1a of the 
Amended and Restated Trust Agreement after consulting with the Beneficiary.   
<http://trustee.ietf.org/trust-agreement-2014.html>

This Article states in relevant part:
"the Trustees may, after due consultation with the Beneficiary, dispose of, assign, sell, transfer, 
renounce, convey or terminate Trust Assets that are of no current or foreseeable future value to 
the Beneficiary and which require the expenditure of funds to retain.This exception does not 
include RFCs.â€�

The purpose of this announcement is to begin the consultation with the Beneficiary, the IETF 
Community.  This thirty (30) day comment period expires on 5 May 2014.  The Trustees will consider 
the Community input before making a decision whether to renounce the â€œIETF Secretariatâ€� trademark 
or not.  

Your feedback is appreciated.

Thanks
Ray Pelletier
IETF Administrative Director
Trustee
IETF Trust


From nobody Fri Apr  4 11:09:41 2014
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF901A02DA for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 11:09:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.267
X-Spam-Level: 
X-Spam-Status: No, score=-1.267 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 inUN-Uvvve-E for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 11:09:33 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 6BFD21A0235 for <ietf@ietf.org>; Fri,  4 Apr 2014 11:09:33 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-186.snva.ca.megapath.net [68.164.244.186]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 8EE5340376 for <ietf@ietf.org>; Fri,  4 Apr 2014 18:08:41 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id s34I9QbK002148 for <ietf@ietf.org>; Fri, 4 Apr 2014 11:09:26 -0700
Date: Fri, 4 Apr 2014 11:09:26 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: =?UTF-8?Q?Re=3A_Community_Input_Requested_on_Trustees=E2=80=99_Intent_to_Renounce_=E2=80=9CIETF_Secretariat=E2=80=9D_Trademark?=
In-Reply-To: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
Message-ID: <alpine.LRH.2.01.1404041107080.19664@egate.xpasc.com>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Cda6YcrbMh7tHt9Hwns7AKzV77M
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 18:09:37 -0000

An english interpretation would be helpful ... I think this is saying is
that "IETF Secretariat" is not needed because we have "IETF" as a
registered trademark (and thus "IETF Secretariat" remains prtected)?


On Fri, 4 Apr 2014, IETF Administrative Director wrote:

> All;
>
> The Trustees of the IETF Trust have voted an intent to renounce (abandon) the ?IETF Secretariat?
> trademark, but before taking any action they desire to hear from the community.
>
> Specifically:
>
> It is the Trustees? intent to:
>
> 1. Not renew the ?IETF Secretariat? trademark, Registration 3860848, in the European Community
> at an approximate cost of $5,000 USD for a ten-year period when due on May 28, 2014, and
> thereby renounce the trademark as having no foreseeable future value in accordance with Article 7.1a
> of the Amended and Restated Trust Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.
> The trademark has no foreseeable future value as the ?IETF? trademark is registered in the European
> Community and its use with Secretariat is protected.
>
> 2. Not renew the ?IETF Secretariat? trademark, Registration 2392833, in the United States at an unknown
> future cost when the trademark expires on October 10, 2020, and thereby renounce the trademark as
> having no foreseeable future value in accordance with Article 7.1a of the Amended and Restated Trust
> Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.  The trademark has no foreseeable
> future value as the ?IETF? trademark is registered in the United States and its use with Secretariat is
> protected.
>
> Authority:
>
> The Trustees have the authority to renounce the trademark in accordance with Article 7.1a of the
> Amended and Restated Trust Agreement after consulting with the Beneficiary.
> <http://trustee.ietf.org/trust-agreement-2014.html>
>
> This Article states in relevant part:
> "the Trustees may, after due consultation with the Beneficiary, dispose of, assign, sell, transfer,
> renounce, convey or terminate Trust Assets that are of no current or foreseeable future value to
> the Beneficiary and which require the expenditure of funds to retain.This exception does not
> include RFCs.?
>
> The purpose of this announcement is to begin the consultation with the Beneficiary, the IETF
> Community.  This thirty (30) day comment period expires on 5 May 2014.  The Trustees will consider
> the Community input before making a decision whether to renounce the ?IETF Secretariat? trademark
> or not.
>
> Your feedback is appreciated.
>
> Thanks
> Ray Pelletier
> IETF Administrative Director
> Trustee
> IETF Trust
>


From nobody Fri Apr  4 11:14:44 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B291A04B1; Fri,  4 Apr 2014 11:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.9
X-Spam-Level: 
X-Spam-Status: No, score=-3.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 Sfv6UMrDx7sT; Fri,  4 Apr 2014 11:14:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACD81A027C; Fri,  4 Apr 2014 11:13:04 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s34ICuiQ012350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 4 Apr 2014 11:12:59 -0700
Message-ID: <533EF5BE.7080300@dcrocker.net>
Date: Fri, 04 Apr 2014 11:11:10 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IETF Administrative Director <iad@ietf.org>, iaoc@ietf.org
Subject: Re: Community Input Requested on =?UTF-8?B?VHJ1c3RlZXPigJkgSW50ZQ==?= =?UTF-8?B?bnQgdG8gUmVub3VuY2Ug4oCcSUVURiBTZWNyZXRhcmlhdOKAnSBUcmFkZW1hcms=?=
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
In-Reply-To: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 04 Apr 2014 11:12:59 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ibt9yFxP_x1g3nHCgf212klsgkk
Cc: wgchairs@ietf.org, iab@iab.org, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 18:14:27 -0000

On 4/4/2014 11:00 AM, IETF Administrative Director wrote:
> The Trustees of the IETF Trust have voted an intent to renounce (abandon) the â€œIETF Secretariatâ€�
> trademark,


It sounds as if this will open the door to my being able to advertise 
myself as the IETF Secretariat.  Or even the ITU's being able to.  Yes?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Apr  4 11:20:05 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34D801A0231; Fri,  4 Apr 2014 11:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.301
X-Spam-Level: 
X-Spam-Status: No, score=-102.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 CgzxIMBRTi1D; Fri,  4 Apr 2014 11:19:53 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0212.outbound.protection.outlook.com [207.46.163.212]) by ietfa.amsl.com (Postfix) with ESMTP id 731861A0265; Fri,  4 Apr 2014 11:19:53 -0700 (PDT)
Received: from [192.168.0.34] (69.131.53.57) by CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149) with Microsoft SMTP Server (TLS) id 15.0.913.9; Fri, 4 Apr 2014 18:19:47 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: =?windows-1252?Q?Re=3A_Community_Input_Requested_on_Trustees=92_?= =?windows-1252?Q?Intent_to_Renounce_=93IETF_Secretariat=94_Trade?= =?windows-1252?Q?mark?=
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <533EF5BE.7080300@dcrocker.net>
Date: Fri, 4 Apr 2014 14:19:38 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BN1PR06CA019.namprd06.prod.outlook.com (10.141.56.39) To CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149)
X-Forefront-PRVS: 01713B2841
X-Forefront-Antispam-Report: =?Windows-1252?Q?SFV:NSPM; SFS:(10019001)(6049001)(6009001)(428001)(517040?= =?Windows-1252?Q?05)(377454003)(479174003)(24454002)(199002)(189002)(7648?= =?Windows-1252?Q?2001)(56776001)(81542001)(53806001)(42186004)(54316002)(?= =?Windows-1252?Q?76796001)(74706001)(57306001)(33656001)(76786001)(629660?= =?Windows-1252?Q?02)(51856001)(81342001)(4396001)(50226001)(97186001)(973?= =?Windows-1252?Q?36001)(19580405001)(19580395003)(83322001)(74876001)(367?= =?Windows-1252?Q?56003)(46102001)(95666003)(49866001)(47736001)(74366001)?= =?Windows-1252?Q?(47976001)(50986001)(93516002)(81686001)(47446002)(81816?= =?Windows-1252?Q?001)(93136001)(87976001)(94316002)(99396002)(93916002)(8?= =?Windows-1252?Q?6362001)(92566001)(92726001)(89996001)(79102001)(7466200?= =?Windows-1252?Q?1)(66066001)(80022001)(98676001)(80976001)(69226001)(745?= =?Windows-1252?Q?02001)(88136002)(83716003)(94946001)(65816001)(82746002)?= =?Windows-1252?Q?(23746002)(83072002)(224303002)(85852003)(31966008)(2077?= =?Windows-1252?Q?6003)(63696002)(59766001)(77982001)(85306002)(47776003)(?= =?Windows-1252?Q?224313003)(87286001)(77096001)(95416001)(87266001)(90146?= =?Windows-1252?Q?001)(77156001)(56816005);DIR:OUT;SFP:1102;SCL:1;SRVR:CO1?= =?Windows-1252?Q?PR06MB237;H:[192.168.0.34];FPR:9F05F521.208A44E9.7AF02FA?= =?Windows-1252?Q?7.C8A0B371.20120;MLV:sfv;PTR:InfoNoRecords;A:1;MX:1;LANG?= =?Windows-1252?Q?:en;?=
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lq5Vi3UIF6PTlchUHfrtNUwNvIA
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, iaoc@ietf.org, "iab@iab.org IAB" <iab@iab.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 18:19:58 -0000

On Apr 4, 2014, at 2:11 PM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 4/4/2014 11:00 AM, IETF Administrative Director wrote:
>> The Trustees of the IETF Trust have voted an intent to renounce =
(abandon) the =93IETF Secretariat=94
>> trademark,
>=20
>=20
> It sounds as if this will open the door to my being able to advertise =
myself as the IETF Secretariat.  Or even the ITU's being able to.  Yes?

You could certainly use =93Secretariat=94 but you cannot use =93IETF =
Secretariat=94 without violating the =93IETF=94 trademark.

Ray

>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From nobody Fri Apr  4 11:20:49 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CBD51A041A for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 11:20:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.301
X-Spam-Level: 
X-Spam-Status: No, score=-102.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 i3RCeCTMn4JM for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 11:20:43 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0211.outbound.protection.outlook.com [207.46.163.211]) by ietfa.amsl.com (Postfix) with ESMTP id 7FA061A0231 for <ietf@ietf.org>; Fri,  4 Apr 2014 11:20:43 -0700 (PDT)
Received: from [192.168.0.34] (69.131.53.57) by CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149) with Microsoft SMTP Server (TLS) id 15.0.913.9; Fri, 4 Apr 2014 18:20:38 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: =?windows-1252?Q?Re=3A_Community_Input_Requested_on_Trustees=92_?= =?windows-1252?Q?Intent_to_Renounce_=93IETF_Secretariat=94_Trade?= =?windows-1252?Q?mark?=
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <alpine.LRH.2.01.1404041107080.19664@egate.xpasc.com>
Date: Fri, 4 Apr 2014 14:20:30 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <3C9EB576-5085-4301-A215-E639ACEDD0CF@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1404041107080.19664@egate.xpasc.com>
To: David Morris <dwm@xpasc.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BN1PR06CA019.namprd06.prod.outlook.com (10.141.56.39) To CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149)
X-Forefront-PRVS: 01713B2841
X-Forefront-Antispam-Report: =?us-ascii?Q?SFV:NSPM; SFS:(10019001)(6049001)(6009001)(428001)(13734003)(?= =?us-ascii?Q?51704005)(377454003)(24454002)(199002)(189002)(76482001)(567?= =?us-ascii?Q?76001)(81542001)(53806001)(42186004)(54316002)(76796001)(747?= =?us-ascii?Q?06001)(57306001)(33656001)(76786001)(62966002)(51856001)(813?= =?us-ascii?Q?42001)(4396001)(50226001)(97186001)(23726002)(97336001)(1958?= =?us-ascii?Q?0405001)(19580395003)(83322001)(74876001)(36756003)(46102001?= =?us-ascii?Q?)(95666003)(49866001)(47736001)(74366001)(47976001)(50986001?= =?us-ascii?Q?)(93516002)(81686001)(47446002)(81816001)(93136001)(87976001?= =?us-ascii?Q?)(94316002)(99396002)(93916002)(86362001)(92566001)(92726001?= =?us-ascii?Q?)(89996001)(79102001)(74662001)(66066001)(80022001)(98676001?= =?us-ascii?Q?)(80976001)(69226001)(74502001)(88136002)(83716003)(94946001?= =?us-ascii?Q?)(65816001)(82746002)(83072002)(224303002)(85852003)(3196600?= =?us-ascii?Q?8)(20776003)(63696002)(59766001)(77982001)(85306002)(4777600?= =?us-ascii?Q?3)(97756001)(224313003)(87286001)(77096001)(95416001)(464060?= =?us-ascii?Q?03)(87266001)(90146001)(77156001)(56816005);DIR:OUT;SFP:1102?= =?us-ascii?Q?;SCL:1;SRVR:CO1PR06MB237;H:[192.168.0.34];FPR:7FD8F5FC.2FF29?= =?us-ascii?Q?6F1.B3E33BAB.C6E93171.202FD;MLV:sfv;PTR:InfoNoRecords;A:1;MX?= =?us-ascii?Q?:1;LANG:en;?=
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SmfiX9S2ZJesogkJqIEsHryey-Q
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 18:20:48 -0000

On Apr 4, 2014, at 2:09 PM, David Morris <dwm@xpasc.com> wrote:

>=20
> An english interpretation would be helpful ... I think this is saying =
is
> that "IETF Secretariat" is not needed because we have "IETF" as a
> registered trademark (and thus "IETF Secretariat" remains protected)?

That is correct.

Ray



>=20
>=20
> On Fri, 4 Apr 2014, IETF Administrative Director wrote:
>=20
>> All;
>>=20
>> The Trustees of the IETF Trust have voted an intent to renounce =
(abandon) the ?IETF Secretariat?
>> trademark, but before taking any action they desire to hear from the =
community.
>>=20
>> Specifically:
>>=20
>> It is the Trustees? intent to:
>>=20
>> 1. Not renew the ?IETF Secretariat? trademark, Registration 3860848, =
in the European Community
>> at an approximate cost of $5,000 USD for a ten-year period when due =
on May 28, 2014, and
>> thereby renounce the trademark as having no foreseeable future value =
in accordance with Article 7.1a
>> of the Amended and Restated Trust Agreement, =
<http://trustee.ietf.org/trust-agreement-2014.html>.
>> The trademark has no foreseeable future value as the ?IETF? trademark =
is registered in the European
>> Community and its use with Secretariat is protected.
>>=20
>> 2. Not renew the ?IETF Secretariat? trademark, Registration 2392833, =
in the United States at an unknown
>> future cost when the trademark expires on October 10, 2020, and =
thereby renounce the trademark as
>> having no foreseeable future value in accordance with Article 7.1a of =
the Amended and Restated Trust
>> Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.  The =
trademark has no foreseeable
>> future value as the ?IETF? trademark is registered in the United =
States and its use with Secretariat is
>> protected.
>>=20
>> Authority:
>>=20
>> The Trustees have the authority to renounce the trademark in =
accordance with Article 7.1a of the
>> Amended and Restated Trust Agreement after consulting with the =
Beneficiary.
>> <http://trustee.ietf.org/trust-agreement-2014.html>
>>=20
>> This Article states in relevant part:
>> "the Trustees may, after due consultation with the Beneficiary, =
dispose of, assign, sell, transfer,
>> renounce, convey or terminate Trust Assets that are of no current or =
foreseeable future value to
>> the Beneficiary and which require the expenditure of funds to =
retain.This exception does not
>> include RFCs.?
>>=20
>> The purpose of this announcement is to begin the consultation with =
the Beneficiary, the IETF
>> Community.  This thirty (30) day comment period expires on 5 May =
2014.  The Trustees will consider
>> the Community input before making a decision whether to renounce the =
?IETF Secretariat? trademark
>> or not.
>>=20
>> Your feedback is appreciated.
>>=20
>> Thanks
>> Ray Pelletier
>> IETF Administrative Director
>> Trustee
>> IETF Trust
>>=20
>=20


From nobody Fri Apr  4 11:54:50 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB2611A0522 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 11:54:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 jK0pybLkcqB5 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 11:54:44 -0700 (PDT)
Received: from mail-yh0-x234.google.com (mail-yh0-x234.google.com [IPv6:2607:f8b0:4002:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id A43A61A0515 for <ietf@ietf.org>; Fri,  4 Apr 2014 11:54:44 -0700 (PDT)
Received: by mail-yh0-f52.google.com with SMTP id c41so3513464yho.39 for <ietf@ietf.org>; Fri, 04 Apr 2014 11:54:40 -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:from:date:message-id :subject:to:cc:content-type; bh=l1iBITbkCF6Defpsnwv5mwFUHMQ1Ekcm6E1DV2tM0TE=; b=sAWZDFJlSLZqodh/gv5P8e3Am6x7VpyDVrvvxmWvQuF2meTpseK086BweIjJoY3d6D A8VqVtYfjTioF138KF0xO2d7c2BmPFopgCURJAC8kSt1GKb8LOb/8KLhTboQfrWV0dSI MZmuKCv2PgwkFFE1m8CSvpV2Hj5GB8EHkW2YXZzMgVpIBSarve5bNJq/tG7sPyy6x+1s 7Pwnl7tgbrl8oWfFR+eypfQLb8K1+HeUuJ6fq36K+9+KjrOkHYyzofPvFHwS5WcVJTKp s2j8FUOqnxFP47ZVo6ndmHn7hKvKjtlm8D+9xQN/3hpmmcPTEQaO2UK7zqQcuY6izK07 +H3w==
X-Received: by 10.236.166.39 with SMTP id f27mr12231354yhl.116.1396637679919;  Fri, 04 Apr 2014 11:54:39 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Fri, 4 Apr 2014 11:53:59 -0700 (PDT)
In-Reply-To: <533EEF35.7070901@isdg.net>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net>
From: Dick Franks <rwfranks@acm.org>
Date: Fri, 4 Apr 2014 19:53:59 +0100
X-Google-Sender-Auth: kTRVxFcGLGHrQ38C2HfPOltHcT0
Message-ID: <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com>
Subject: Re: Security for various IETF services
To: Hector Santos <hsantos@isdg.net>
Content-Type: multipart/alternative; boundary=20cf3040e3f4caa98104f63c0c9c
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VGKVQnBSqjLDmXyJl5b5mIztrc8
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 18:54:49 -0000

--20cf3040e3f4caa98104f63c0c9c
Content-Type: text/plain; charset=UTF-8

Tinkering with the text of a 90 word statement full of PR claptrap is not
going to achieve anything.

The starting point for any sensible discussion on this topic is a threat
model, for each service,  against which the effectiveness of proposed
mitigation strategies can be assessed.

Until that is forthcoming, reasoned discussion taken place, and (rough)
consensus reached, this proposal MUST go nowhere.


Dick
________________________



On 4 April 2014 18:43, Hector Santos <hsantos@isdg.net> wrote:

> I would add and be specific with the last sentence, for example, the IETF
> site
> "new services" might need to be PCI/DSS compliant. This is especially the
> case if the IETF site is collecting credit card information for IETF
> meeting registrations or other purposes.  For logging in purposes, it may
> also need to be PCI/DSS compliant depending on the AUTH method. For DIGEST
> AUTH, it may require SSL and NONCE support. BASIC AUTH requires SSL, and it
> may not be sufficient for PCI/DSS unless there is other methods wrapping
> the BASIC AUTH process, i.e. a cookie method method. A form-based cookie
> login methods, where there is no standard protocol method, may require
> other conditions. Overall, there are areas at the IETF site that require
> updated, modern security-aware connection client access software to be used
> as required by industry standards such as PCI/DSS.  (I note, that this is
> probably USA, not sure how that applies in Europe, Asia, etc)
>
> If fact, the IETF may not be running proper software that complies with
> PCI/DSS.
>
> Maybe visiting one of the PCI/DSS resource/compliance sites can tell you
> what compliancy level the IETF site may fit.  Depending on what software is
> used, it may suffice or it may not, thus perhaps even adding new functional
> requirements to the IETF Web Site revamping project.
>
> Hope this helps
>
> --
> HLS
>
>
> On 4/3/2014 12:21 PM, Stephen Farrell wrote:
>
>>
>> Hi all,
>>
>>  From time to time the issue of how to secure IETF services
>>>
>> comes up e.g. whether to turn on TLS for some IETF web server
>> or jabber or mail etc.
>>
>> The most recent such was a request to turn on HSTS [1] for
>> the IETF web site, which I don't think we can do without
>> breaking old tools etc. Nonetheless we would like to turn
>> on things like TLS more often going forward as seemed to
>> me to be the outcome of a long thread on here late last
>> year.
>>
>> So, the IESG are considering the following as an IESG
>> statement to offer some guidance about this:
>>
>> "The IETF are committed to providing secure and privacy
>> friendly access to information via the web, mail, jabber
>> and other services. While most (but not all) data on IETF
>> services is public, nonetheless access to that data
>> should use best practices for security and privacy.
>> However, as there are numerous legacy tools that have been
>> built that require access via cleartext, the IETF will
>> continue to allow such access so as not to break such
>> tooling. New services will however generally only be made
>> available in ways that use security protocols such as
>> TLS."
>>
>> If you have wordsmithing changes to suggest please just send
>> those to me or the iesg. More substantive comments should go
>> here I guess. I hope the only bit worth discussing (except
>> for the few folks who would rather we do none of this;-)
>> might be the last sentence.
>>
>> A few weeks after any discussion here dies down I'll put the
>> resulting text on an IESG telechat for approval if that seems
>> like the right thing to do.
>>
>> Thanks,
>> S
>>
>> [1] https://tools.ietf.org/html/rfc6797
>>
>>
>>
>>
>>
> --
> HLS
>
>
>

--20cf3040e3f4caa98104f63c0c9c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Tinkering with the text of a 90 word statement full o=
f PR claptrap is not going to achieve anything.<br><br></div>The starting p=
oint for any sensible discussion on this topic is a threat model, for each =
service,=C2=A0 against which the effectiveness of proposed mitigation strat=
egies can be assessed.<br>


<div><br></div><div>Until that is forthcoming, reasoned discussion taken pl=
ace, and (rough) consensus reached, this proposal MUST go nowhere.<br></div=
><div class=3D"gmail_extra"><br clear=3D"all"><div><br clear=3D"all">
<div><div dir=3D"ltr">Dick<br><span><font color=3D"#888888">_______________=
_________<br>
</font></span><br></div></div>
</div>
<br><br><div class=3D"gmail_quote">On 4 April 2014 18:43, Hector Santos <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:hsantos@isdg.net" target=3D"_blank">hs=
antos@isdg.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


I would add and be specific with the last sentence, for example, the IETF s=
ite<br>
&quot;new services&quot; might need to be PCI/DSS compliant. This is especi=
ally the case if the IETF site is collecting credit card information for IE=
TF meeting registrations or other purposes. =C2=A0For logging in purposes, =
it may also need to be PCI/DSS compliant depending on the AUTH method. For =
DIGEST AUTH, it may require SSL and NONCE support. BASIC AUTH requires SSL,=
 and it may not be sufficient for PCI/DSS unless there is other methods wra=
pping the BASIC AUTH process, i.e. a cookie method method. A form-based coo=
kie login methods, where there is no standard protocol method, may require =
other conditions. Overall, there are areas at the IETF site that require up=
dated, modern security-aware connection client access software to be used a=
s required by industry standards such as PCI/DSS. =C2=A0(I note, that this =
is probably USA, not sure how that applies in Europe, Asia, etc)<br>



<br>
If fact, the IETF may not be running proper software that complies with PCI=
/DSS.<br>
<br>
Maybe visiting one of the PCI/DSS resource/compliance sites can tell you wh=
at compliancy level the IETF site may fit. =C2=A0Depending on what software=
 is used, it may suffice or it may not, thus perhaps even adding new functi=
onal requirements to the IETF Web Site revamping project.<br>



<br>
Hope this helps<br>
<br>
--<br>
HLS<div><div><br>
<br>
On 4/3/2014 12:21 PM, Stephen Farrell wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Hi all,<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
>From time to time the issue of how to secure IETF services<br>
</blockquote>
comes up e.g. whether to turn on TLS for some IETF web server<br>
or jabber or mail etc.<br>
<br>
The most recent such was a request to turn on HSTS [1] for<br>
the IETF web site, which I don&#39;t think we can do without<br>
breaking old tools etc. Nonetheless we would like to turn<br>
on things like TLS more often going forward as seemed to<br>
me to be the outcome of a long thread on here late last<br>
year.<br>
<br>
So, the IESG are considering the following as an IESG<br>
statement to offer some guidance about this:<br>
<br>
&quot;The IETF are committed to providing secure and privacy<br>
friendly access to information via the web, mail, jabber<br>
and other services. While most (but not all) data on IETF<br>
services is public, nonetheless access to that data<br>
should use best practices for security and privacy.<br>
However, as there are numerous legacy tools that have been<br>
built that require access via cleartext, the IETF will<br>
continue to allow such access so as not to break such<br>
tooling. New services will however generally only be made<br>
available in ways that use security protocols such as<br>
TLS.&quot;<br>
<br>
If you have wordsmithing changes to suggest please just send<br>
those to me or the iesg. More substantive comments should go<br>
here I guess. I hope the only bit worth discussing (except<br>
for the few folks who would rather we do none of this;-)<br>
might be the last sentence.<br>
<br>
A few weeks after any discussion here dies down I&#39;ll put the<br>
resulting text on an IESG telechat for approval if that seems<br>
like the right thing to do.<br>
<br>
Thanks,<br>
S<br>
<br>
[1] <a href=3D"https://tools.ietf.org/html/rfc6797" target=3D"_blank">https=
://tools.ietf.org/html/<u></u>rfc6797</a><br>
<br>
<br>
<br>
<br>
</blockquote>
<br></div></div><span><font color=3D"#888888">
-- <br>
HLS<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>

--20cf3040e3f4caa98104f63c0c9c--


From nobody Fri Apr  4 12:47:43 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B67B41A01CC; Fri,  4 Apr 2014 12:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 p4hkBvvwJ9FG; Fri,  4 Apr 2014 12:47:33 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 82EA91A055D; Fri,  4 Apr 2014 12:46:09 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WWA3p-000DgJ-Lk; Fri, 04 Apr 2014 15:45:57 -0400
Date: Fri, 04 Apr 2014 15:45:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ray Pelletier <rpelletier@isoc.org>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
Message-ID: <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com>
In-Reply-To: <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net> <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bzxv8sPA0OMrLgB_CTwEt22dWKM
Cc: The IESG <iesg@ietf.org>, Working Group Chairs <wgchairs@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, IETF Discussion <ietf@ietf.org>, iaoc@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 19:47:38 -0000

--On Friday, April 04, 2014 14:19 -0400 Ray Pelletier
<rpelletier@isoc.org> wrote:

>> It sounds as if this will open the door to my being able to
>> advertise myself as the IETF Secretariat.  Or even the ITU's
>> being able to.  Yes?
> 
> You could certainly use "Secretariat" but you cannot use
> "IETF Secretariat" without violating the "IETF"
> trademark.

Ray, I assume that if Dave (or someone else) set themselves up
as the International Elegant Tophat Fabrication Society, made at
least a perfunctory effect to establish themselves as being in
that business, established a business unit that they called
their "Secretariat", and then advertised the result as the "IETF
Secretariat", things could get dicey.  Given the different line
of business, they might even be able to take out a trademark on
"IETF Secretariat".  Right?

Now, whether having a trademark registered as "IETF Secretariat"
with whatever line of business the IETF and IETF Secretariat
claim to be in would offer significant protection against that
attack is far outside my knowledge or experience.

I have enough trouble imagining someone going to the trouble to
attempt the above as an attack that I think it would probably be
foolish to worry about it, but it is, in principle, the
difference between "no risk" and "no risk worth worrying about".

    john





From nobody Fri Apr  4 12:49:50 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 426641A0667 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 12:49:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.138
X-Spam-Level: 
X-Spam-Status: No, score=-101.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 5nGu2_FsF4Tg for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 12:49:44 -0700 (PDT)
Received: from listserv.winserver.com (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 277D61A0584 for <ietf@ietf.org>; Fri,  4 Apr 2014 12:48:12 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4822; t=1396640887; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=XXW1wBdQh7zHx9W5ShIN1xUd3hs=; b=h4/EW62pR9XvXMycOnwj HxcSIDISaRpi6zckVv52OXtCfUoeprveV5FScjs6/5M5YQh071VrQPiIZe3NYDSX yEEAhgCmplOJCOEJDT2/lpnPTK2aGNx5XakLcQrKlrZZ5vPFs/oZ1Ix8qZOHkxnY aIlmR4pV44mKp1/+vNN+COM=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 04 Apr 2014 14:48:07 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1628343624.3926.5880; Fri, 04 Apr 2014 14:48:07 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4822; t=1396640840; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=rtj4W8r FRFrt4vZjnwoe/ZASdGbtTxo6XNQPP3ssNp0=; b=F7/J8UWuV3OTio+mJvk4MoS G9iEgCan/mU+FYEydpUgmVhhSxejdYuPERxce6IDrERI7Oa2HSLjRqShkkqeiJPO 9tjCd0JrDGBc5IJnFuO9PvwehfxURW8Fjs4hzmAyNxuDiyV69hyG0N2sDS+R0RJ5 PkJnHpQyDI7JwuiEH/Ug=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 04 Apr 2014 15:47:20 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1074596350.9.18756; Fri, 04 Apr 2014 15:47:19 -0400
Message-ID: <533F0C7B.9090705@isdg.net>
Date: Fri, 04 Apr 2014 15:48:11 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Dick Franks <rwfranks@acm.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com>
In-Reply-To: <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KBYxl7UO3HCPTXcuvro3aP3M1R8
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 19:49:48 -0000

Hi Dick,

Everyone else has already touch based with the same issues. I'm 
pointing out there are legal, business related regulations to be 
followed making it well understood, it (modern security methods) may 
be mandatory in certain "new service" areas.   If not, then never 
mind. If so, Stephen asked about the last sentence:

   New services will however generally only be made
   available in ways that use security protocols such as
   TLS.

If it is not already implied, I thought it may help with some specific 
admonition as to why it will only be made available in a secured way. 
It says TLS.  Anything else?  A draft suggestion only, additional 
sentence:

   There are areas at the IETF site that may require updated, modern
   security-aware connection client access software to be used
   as required for industry compliance standards, e.g.; PCI/DSS.

Nothing to do with PR, but it doesn't hurt either.

Thanks

-- 
HLS

On 4/4/2014 2:53 PM, Dick Franks wrote:
> Tinkering with the text of a 90 word statement full of PR claptrap is
> not going to achieve anything.
>
> The starting point for any sensible discussion on this topic is a
> threat model, for each service,  against which the effectiveness of
> proposed mitigation strategies can be assessed.
>
> Until that is forthcoming, reasoned discussion taken place, and
> (rough) consensus reached, this proposal MUST go nowhere.
>
>
> Dick
> ________________________
>
>
>
> On 4 April 2014 18:43, Hector Santos <hsantos@isdg.net
> <mailto:hsantos@isdg.net>> wrote:
>
>     I would add and be specific with the last sentence, for example,
>     the IETF site
>     "new services" might need to be PCI/DSS compliant. This is
>     especially the case if the IETF site is collecting credit card
>     information for IETF meeting registrations or other purposes.  For
>     logging in purposes, it may also need to be PCI/DSS compliant
>     depending on the AUTH method. For DIGEST AUTH, it may require SSL
>     and NONCE support. BASIC AUTH requires SSL, and it may not be
>     sufficient for PCI/DSS unless there is other methods wrapping the
>     BASIC AUTH process, i.e. a cookie method method. A form-based
>     cookie login methods, where there is no standard protocol method,
>     may require other conditions. Overall, there are areas at the IETF
>     site that require updated, modern security-aware connection client
>     access software to be used as required by industry standards such
>     as PCI/DSS.  (I note, that this is probably USA, not sure how that
>     applies in Europe, Asia, etc)
>
>     If fact, the IETF may not be running proper software that complies
>     with PCI/DSS.
>
>     Maybe visiting one of the PCI/DSS resource/compliance sites can
>     tell you what compliancy level the IETF site may fit.  Depending
>     on what software is used, it may suffice or it may not, thus
>     perhaps even adding new functional requirements to the IETF Web
>     Site revamping project.
>
>     Hope this helps
>
>     --
>     HLS
>
>
>     On 4/3/2014 12:21 PM, Stephen Farrell wrote:
>
>
>         Hi all,
>
>             >From time to time the issue of how to secure IETF services
>
>         comes up e.g. whether to turn on TLS for some IETF web server
>         or jabber or mail etc.
>
>         The most recent such was a request to turn on HSTS [1] for
>         the IETF web site, which I don't think we can do without
>         breaking old tools etc. Nonetheless we would like to turn
>         on things like TLS more often going forward as seemed to
>         me to be the outcome of a long thread on here late last
>         year.
>
>         So, the IESG are considering the following as an IESG
>         statement to offer some guidance about this:
>
>         "The IETF are committed to providing secure and privacy
>         friendly access to information via the web, mail, jabber
>         and other services. While most (but not all) data on IETF
>         services is public, nonetheless access to that data
>         should use best practices for security and privacy.
>         However, as there are numerous legacy tools that have been
>         built that require access via cleartext, the IETF will
>         continue to allow such access so as not to break such
>         tooling. New services will however generally only be made
>         available in ways that use security protocols such as
>         TLS."
>
>         If you have wordsmithing changes to suggest please just send
>         those to me or the iesg. More substantive comments should go
>         here I guess. I hope the only bit worth discussing (except
>         for the few folks who would rather we do none of this;-)
>         might be the last sentence.
>
>         A few weeks after any discussion here dies down I'll put the
>         resulting text on an IESG telechat for approval if that seems
>         like the right thing to do.
>
>         Thanks,
>         S
>
>         [1] https://tools.ietf.org/html/__rfc6797
>         <https://tools.ietf.org/html/rfc6797>
>
>
>
>
>
>     --
>     HLS
>
>
>




From nobody Fri Apr  4 13:06:36 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CDCE1A0265 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 13:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.062
X-Spam-Level: *
X-Spam-Status: No, score=1.062 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 Li4UyWmrNKkz for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 13:06:28 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8950F1A024D for <ietf@ietf.org>; Fri,  4 Apr 2014 13:06:28 -0700 (PDT)
Received: (qmail 59256 invoked from network); 4 Apr 2014 20:06:23 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 4 Apr 2014 20:06:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=533f10bf.xn--btvx9d.k1404; i=johnl@user.iecc.com; bh=i2k1huUeCrJkgbV3TLg2EB4s+1Li536Ma9dEzWEmmUo=; b=MtPajW0UbsY94KRpzayYPSJK+fhh9Rs7HTCs+8dA2RLhTzua0xpFkaDCUG3yt6QIGypAxFeQwUngMXPT/4lEbPWfQBWo0mSaygOlhf4Ve/1OJ0YDISj+fliWSCmPmmg782YkqKavxXwIRVruSsfdr8XNsx0jI/9G8brg/hwwkpsH1yj0jdA+Fd4NmT+Bxc/LUcovEuzXrP/IY5IvaGTmMvlmCV+dBA+jvl8+EtbqdhRnAYyg13mI+Qj4W6KoxSXG
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=533f10bf.xn--btvx9d.k1404; bh=i2k1huUeCrJkgbV3TLg2EB4s+1Li536Ma9dEzWEmmUo=;  b=4AUziB34HIxRgmwmzYEKAX4m0bBAwii1roS7IIViTxgeHgNTjNYf1WP9r+w2cK1ahzgoaBG/ysQT4GMtENlj6NKeCgU+n7tInTJHDRmwousxagdEL3Twdh4taLp+VBUFfop+btLVKQ/HcdQaH1wl0WVv0Q5zoA9S1PMqE7mBNE6j7YfX4utdf1H54SGLByhsv9ZTQDkHkSa22mFR9QxsRu9Zmc/bsFzjetVdv7G+pohm/nMMz2jRc8irCmm5N+Pc
Date: 4 Apr 2014 20:06:00 -0000
Message-ID: <20140404200600.94331.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: =?windows-1252?Q?Re=3A_Community_Input_Requested_on_Trustees=92_?= =?windows-1252?Q?Intent_to_Renounce_=93IETF_Secretariat=94_Trade?= =?windows-1252?Q?mark?=
In-Reply-To: <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EZ9J7elEacPg_YhwLMRRmsS4Ioc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 20:06:34 -0000

>> It sounds as if this will open the door to my being able to
>> advertise myself as the IETF Secretariat.  Or even the ITU's being
>> able to.  Yes?

> You could certainly use "Secretariat" but you cannot use "IETF
> Secretariat" without violating the "IETF" trademark.

Secretariat is a generic world, while IETF is made up.  Trademark law
generally allows you to protect a made up word, or a phrase containing
made up words or a combination of generic and made up.

I agree that so long as we maintain a trademark on "IETF" there is
little value in separate registration of phrases, particularly
considering how expensive it is.  The US renewal fee is only $450 but
that still seems like a waste in this case.

By the way, when I go to the WIPO Madrid Protocol web site, it says
that the renewal fee for the EU is CHF2186, about $2500.  Where'd the
$5000 come from?  And did we ever follow up on Japan's rejection of
our application?

R's,
John



From nobody Fri Apr  4 13:13:17 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C00E11A0238 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 13:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 AttD7z0tBDOU for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 13:13:11 -0700 (PDT)
Received: from mail-yh0-x231.google.com (mail-yh0-x231.google.com [IPv6:2607:f8b0:4002:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 521321A041A for <ietf@ietf.org>; Fri,  4 Apr 2014 13:13:11 -0700 (PDT)
Received: by mail-yh0-f49.google.com with SMTP id z6so3579188yhz.22 for <ietf@ietf.org>; Fri, 04 Apr 2014 13:13:06 -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:from:date:message-id :subject:to:cc:content-type; bh=qJigv8O6PGsTz5qd1XiAMxNEfQr2SktetR6OoOE4w8s=; b=DzvWruwYP7w0GImhrDXrdXG5sMDbaULMb+PVyxfHVyeGvoGWhJLzl+uoDwPVKm6lA3 k0RNp2FjasUnyVCwMhsYqNMlK0AHuzBv9Kb1vD6Ed0qMplY3mdOxmW9HbtfWE9f4iTgc zsR0PZEPNWj9FQnzvq0r+Zq4KuwpDhHqmKzwj88S5GGPrp3OhUXDWvWh1OLFT5L0i6lt mXBqs9dpI8kNGvRTBhCgIQxPYZ7GFtzOtGWZO0Ha5+RUEula+MZ43mDCwuk8opfkH9WK xvwMuuejcIOrRbLaL5X3Jmo6scuShqDGJBzfQdUv4n05DR27S6Ledb8OmIdshUk7upYQ J/iQ==
X-Received: by 10.236.77.165 with SMTP id d25mr12674622yhe.119.1396642386559;  Fri, 04 Apr 2014 13:13:06 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Fri, 4 Apr 2014 13:12:26 -0700 (PDT)
In-Reply-To: <533F0C7B.9090705@isdg.net>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net>
From: Dick Franks <rwfranks@acm.org>
Date: Fri, 4 Apr 2014 21:12:26 +0100
X-Google-Sender-Auth: F8ECh9tNjUWlbrSvIQi67n7A5_k
Message-ID: <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com>
Subject: Re: Security for various IETF services
To: Hector Santos <hsantos@isdg.net>
Content-Type: multipart/alternative; boundary=20cf30050d7e54488f04f63d257e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JY-WANrGDZLGpnGEvMIxdbwh3tg
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 20:13:16 -0000

--20cf30050d7e54488f04f63d257e
Content-Type: text/plain; charset=UTF-8

On 4 April 2014 20:48, Hector Santos <hsantos@isdg.net> wrote:

>
> Everyone else has already touch based with the same issues.


>  Silence could easily be misconstrued as acceptance.

[snip]

>   Stephen asked about the last sentence:
>
>   New services will however generally only be made
>   available in ways that use security protocols such as
>   TLS.
>
> Which to my eye looks like a conclusion;  without shred of justification
and before any meaningful discussion has taken place.


26 messages on and the consensus thus far is that an answer to Lloyd Wood's
one-liner is very much required.

--20cf30050d7e54488f04f63d257e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On 4 April 2014 20:48, Hector Santos <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:hsantos@isdg.net" target=3D"_blank">hs=
antos@isdg.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<br>
Everyone else has already touch based with the same issues.=C2=A0=C2=A0</bl=
ockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><br></blockquote><div>=C2=A0Silence=
 could easily be misconstrued as acceptance.<br>

<br></div><div>[snip]<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=C2=A0 Stephe=
n asked about the last sentence:<div class=3D"">
<br>
=C2=A0 New services will however generally only be made<br>
=C2=A0 available in ways that use security protocols such as<br>
=C2=A0 TLS.<br>
<br></div></blockquote><div>Which to my eye looks like a conclusion;=C2=A0 =
without shred of justification and before any meaningful discussion has tak=
en place.<br></div><div><br><br></div><div class=3D"h5">26 messages on and =
the consensus thus far is that an answer to Lloyd Wood&#39;s one-liner is v=
ery much required.<br>

</div></div></div></div>

--20cf30050d7e54488f04f63d257e--


From nobody Fri Apr  4 13:19:27 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C54F81A0502 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 13:19:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.762
X-Spam-Level: 
X-Spam-Status: No, score=0.762 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001] autolearn=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 zygPEoADutNO for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 13:19:20 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 501A71A013D for <ietf@ietf.org>; Fri,  4 Apr 2014 13:19:20 -0700 (PDT)
Received: (qmail 61474 invoked from network); 4 Apr 2014 20:19:15 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 4 Apr 2014 20:19:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=533f13c3.xn--btvx9d.k1404; i=johnl@user.iecc.com; bh=Hpq29iy9Aedtj7G4wfMKm2LFuUt0S6SIk6n6TbwKs0g=; b=p0sw4842SzLdPiFZiP6usdIXkgZo89kmgo8IJz/Dc4I2kv5qeBN56MgpLdRnpMcXPP41mxwCiBou5KVNjAJgYDjmt2BEFJrDqA7P4H28mZOAIK0oVkwJqSzgib+wlCy1ij9NM5t+5IxTUNTRA7iejq34htQvv1xGZac6FTWBoZUSKD5NX985zyVcQk8N5imxZHiM6z26Wv1WtI5P4cb71onyvfWsl3m9XXltKpI2ahmpu3R1BD/ty6ZASxLXSnDc
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=533f13c3.xn--btvx9d.k1404; bh=Hpq29iy9Aedtj7G4wfMKm2LFuUt0S6SIk6n6TbwKs0g=;  b=GcI1VCpgrroy6/yUCY1X1XBlWN1wwY5ErQN+f16qQ8LjZE0ICnLFGQtHP/vpzqvZ6Pe4tW+1unCpifTlPcCUhmo7stHGuk2+IWBCGDVqPKbUnD3ETb5GO5HuOqBdgf5N7rln7VeyKPinClXYq3luFy+5UuQfLY9XxldqAGndFzue3EGcraVfnA/X6YBaBxF33IXO3OcfVvl1g6XnoypJCGDiTSsSPWfcN3aJGdc5tzeRBNOVD3oxp/Pz01t55MUw
Date: 4 Apr 2014 20:18:53 -0000
Message-ID: <20140404201853.94380.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
In-Reply-To: <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7hqOGY9f9zCxYJ3JQLmerjdjYWY
Cc: john-ietf@jck.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 20:19:25 -0000

>Ray, I assume that if Dave (or someone else) set themselves up
>as the International Elegant Tophat Fabrication Society, made at
>least a perfunctory effect to establish themselves as being in
>that business, established a business unit that they called
>their "Secretariat", and then advertised the result as the "IETF
>Secretariat", things could get dicey.  Given the different line
>of business, they might even be able to take out a trademark on
>"IETF Secretariat".  Right?

Yes, and under those circumstances, it wouldn't matter whether we had
a registration or not, since trademarks are topic specific unless you
can persuade a court that your trademark is "famous".  That's why
there are live registrations for both the Ford Motor Company, and the
unrelated Ford Gum and Machine Company.

If someone other than us started passing itself as the IETF anything,
trademark registration would be only one bit of the battle.

Although I do note that on the WIPO Madrid Trademark page, we have
registrations in Australia, the EU, Korea, Norway, Russia, and
Singapore, but not in Switzerland, where the ITU is, nor China.

R's,
John


From nobody Fri Apr  4 14:07:16 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC7391A00EF for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 14:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 LPsGIlJEpAWU for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 14:07:09 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id E57551A00B4 for <ietf@ietf.org>; Fri,  4 Apr 2014 14:07:08 -0700 (PDT)
Received: from [10.30.0.101] (unknown [83.150.71.93]) by p130.piuha.net (Postfix) with ESMTPSA id AD89C2CC48; Sat,  5 Apr 2014 00:07:00 +0300 (EEST)
Message-ID: <533F1EF4.40202@piuha.net>
Date: Sat, 05 Apr 2014 00:07:00 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: New TLDs and software
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tapiT9N2C7UcSQdRWN24evg_MeQ
Cc: barryleiba@computer.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 21:07:14 -0000

This is another blog post, a continuation of topics that came up in the 
ICANN meeting. The previous blog post was about the IANA discussions. 
But of course that was not the only topic that we talked about.

The biggest project in the last couple of years at ICANN has been the 
introduction of new TLDs. Those are new finally coming online, and 
include both new ASCII-based names as well as many internationalized 
domain names. The latter are, of course, very important for the 
worldwide users of the Internet. But adding new TLDs is not just an 
administrative matter. In this blog article Barry and I wanted to 
highlight that there are some cases where software updates may be needed:

http://www.ietf.org/blog/2014/04/new-tlds/

Jari & Barry


From nobody Fri Apr  4 14:58:31 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 473C21A0132; Fri,  4 Apr 2014 14:58:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.601
X-Spam-Level: 
X-Spam-Status: No, score=-102.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=unavailable
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 OrTizsTs5vh4; Fri,  4 Apr 2014 14:58:16 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6F31A00CA; Fri,  4 Apr 2014 14:58:16 -0700 (PDT)
Received: from [192.168.0.34] (69.131.53.57) by CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149) with Microsoft SMTP Server (TLS) id 15.0.913.9; Fri, 4 Apr 2014 21:58:02 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com>
Date: Fri, 4 Apr 2014 17:57:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F8B2F4F2-4B8F-49A8-8233-E80BAE737128@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net> <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org> <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BLUPR06CA016.namprd06.prod.outlook.com (10.141.20.36) To CO1PR06MB237.namprd06.prod.outlook.com (10.242.166.149)
X-Forefront-PRVS: 01713B2841
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(428001)(189002)(199002)(24454002)(377454003)(51704005)(74662001)(79102001)(92566001)(86362001)(89996001)(92726001)(88136002)(74502001)(69226001)(83716003)(66066001)(80976001)(80022001)(98676001)(47976001)(50986001)(74366001)(99396002)(94316002)(93916002)(81686001)(47446002)(93516002)(87976001)(93136001)(81816001)(87286001)(77156001)(90146001)(87266001)(56816005)(77096001)(95416001)(23746002)(94946001)(65816001)(83072002)(82746002)(77982001)(59766001)(47776003)(85306002)(63696002)(85852003)(20776003)(31966008)(50466002)(33656001)(76786001)(51856001)(62966002)(76796001)(74706001)(4396001)(81342001)(81542001)(53806001)(76482001)(56776001)(54316002)(36756003)(49866001)(47736001)(46102001)(95666003)(97186001)(50226001)(74876001)(97336001)(19580405001)(19580395003)(83322001); DIR:OUT; SFP:1102; SCL:1; SRVR:CO1PR06MB237; H:[192.168.0.34]; FPR:1CC4F01C.AF2697E8.F1E3736B.84E6DA6B.202D9; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Kk7ntj8OJK5e9wgFWREISwopYx8
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, IAOC <iaoc@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, The IESG <iesg@ietf.org>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 21:58:20 -0000

On Apr 4, 2014, at 3:45 PM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Friday, April 04, 2014 14:19 -0400 Ray Pelletier
> <rpelletier@isoc.org> wrote:
>=20
>>> It sounds as if this will open the door to my being able to
>>> advertise myself as the IETF Secretariat.  Or even the ITU's
>>> being able to.  Yes?
>>=20
>> You could certainly use "Secretariat" but you cannot use
>> "IETF Secretariat" without violating the "IETF"
>> trademark.
>=20
> Ray, I assume that if Dave (or someone else) set themselves up
> as the International Elegant Tophat Fabrication Society, made at
> least a perfunctory effect to establish themselves as being in
> that business, established a business unit that they called
> their "Secretariat", and then advertised the result as the "IETF
> Secretariat", things could get dicey.  Given the different line
> of business, they might even be able to take out a trademark on
> "IETF Secretariat".  Right?

The "risk" applies to IETF in addition to IETF Secretariat. =20
We don't own IETF in every class of goods and services.=20
IETF bananas, top hats and car tires can be sold and =20
that won=92t violate our IETF trademark =20

People aren=92t going to be confused between the two,
just like they aren=92t for Apple computers and Apple records.

Ray
>=20
> Now, whether having a trademark registered as "IETF Secretariat"
> with whatever line of business the IETF and IETF Secretariat
> claim to be in would offer significant protection against that
> attack is far outside my knowledge or experience.
>=20
> I have enough trouble imagining someone going to the trouble to
> attempt the above as an attack that I think it would probably be
> foolish to worry about it, but it is, in principle, the
> difference between "no risk" and "no risk worth worrying about".
>=20
>    john
>=20
>=20
>=20
>=20


From nobody Fri Apr  4 15:06:52 2014
Return-Path: <pranesh@cis-india.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763561A0121; Fri,  4 Apr 2014 15:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.345
X-Spam-Level: *
X-Spam-Status: No, score=1.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FU_ENDS_2_WRDS=0.255, MIME_8BIT_HEADER=0.3, RCVD_IN_PSBL=2.7, T_RP_MATCHES_RCVD=-0.01] autolearn=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 RJNSL4e9gVEI; Fri,  4 Apr 2014 15:06:46 -0700 (PDT)
Received: from mail.cis-india.org (mail.cis-india.org [202.190.125.68]) by ietfa.amsl.com (Postfix) with ESMTP id A248F1A0150; Fri,  4 Apr 2014 15:06:45 -0700 (PDT)
Received: from [192.168.1.65] (unknown [162.243.72.125]) by mail.cis-india.org (Postfix) with ESMTPSA id 2AC13A7CB9C; Fri,  4 Apr 2014 22:04:19 +0000 (UTC)
Message-ID: <533F2CE3.3080102@cis-india.org>
Date: Fri, 04 Apr 2014 18:06:27 -0400
From: Pranesh Prakash <pranesh@cis-india.org>
Organization: Centre for Internet and Society
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, IETF Administrative Director <iad@ietf.org>,  iaoc@ietf.org
Subject: Re: Community Input Requested on =?UTF-8?B?VHJ1c3RlZXPigJkgSW50ZQ==?= =?UTF-8?B?bnQgdG8gUmVub3VuY2Ug4oCcSUVURiBTZWNyZXRhcmlhdOKAnSBUcmFkZW1hcms=?=
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net>
In-Reply-To: <533EF5BE.7080300@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="CdDtxMFgSf0bEtQo36GmAnQnIaWt09pxo"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AjVy9GJXtkK7DLYjqg40R788QwA
Cc: wgchairs@ietf.org, iab@iab.org, ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 22:06:51 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--CdDtxMFgSf0bEtQo36GmAnQnIaWt09pxo
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Dave Crocker <dhc@dcrocker.net> [2014-04-004 11:11:10 -0700]:
> On 4/4/2014 11:00 AM, IETF Administrative Director wrote:
>> The Trustees of the IETF Trust have voted an intent to renounce
>> (abandon) the =E2=80=9CIETF Secretariat=E2=80=9D
>> trademark,
>
>
> It sounds as if this will open the door to my being able to advertise
> myself as the IETF Secretariat.  Or even the ITU's being able to.  Yes?=


IAAL: Anyone can do that already.  One must remember that trademarks are =

granted on a class-wise basis.

A trademark for IETF (or IETF Secretariat) can simultaneously belong to=20
multiple companies and organization as long as they are for different=20
classes (of goods and services).

--=20
Pranesh Prakash
Policy Director, Centre for Internet and Society
T: +91 80 40926283 | W: http://cis-india.org
-------------------
Access to Knowledge Fellow, Information Society Project, Yale Law School
M: +1 520 314 7147 | W: http://yaleisp.org
PGP ID: 0x1D5C5F07 | Twitter: https://twitter.com/pranesh_prakash


--CdDtxMFgSf0bEtQo36GmAnQnIaWt09pxo
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJTPyzjAAoJEFUPonS5l6Cppf4P/0KE9NaaBAgIzTNDKeah3e95
n10gHnal4BlFFtwVyzjZCqjytkcchBF9rCaa8RnkIa3ACVkfmNPcmKNsvkt51C04
aX7kqS2URedTVKZoOwABuItWCxOMVI+4JrVVrXDvP7FVeMhZyBfjvNETUT77sN74
Dx810EilkUo4C7KspRSsJf6MgIOK0DgZcygo2lJZO6W5aYzEKUmo3lAzPotl6Uqk
qIrRoKp4N7sU7P2AQGymRLLib2fMGS3VuMK8sLAHtdKT3Xh8ZMrlt2+MfkrL/Yo0
XlOy8OPjrUap8WXuYOoKykkag7wCzvnxgCJmz1DSJO7XQltv0bTzzjJDpUkXBQDE
VX3vJj6EBYA3mbviFL3OfciPFHS0hLASvkMb+jaujfYiDvdsJ50mzEPiaBHp+RcY
3yx2HNLsD/MwQ8b05AmLGoCufKMQGR47VNgHzJqsRx+5qUACOcHrZRjVU2Mipdgu
NAJdfRi4CwLzNxZXM5YY80QVYJNywZQGlowHgIH1zYK7jW3HrMRT2wHVk/QrARqu
UgBboOWUpvKzbgLKiPSogqLDDoEOlj9e6l4zIg7KIZJRXK2puCnZpFeB+jSYgPZ5
0+rnhhLt7TSWb/Objp8QgUI8yXkPt6YShrHtE6HCmD/MSwc+s+J0Hhp8ENfN51Mk
SdIf3XmQ/D7zsZHJdk09
=iISK
-----END PGP SIGNATURE-----

--CdDtxMFgSf0bEtQo36GmAnQnIaWt09pxo--


From nobody Fri Apr  4 15:09:14 2014
Return-Path: <cdel@firsthand.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3438D1A014B; Fri,  4 Apr 2014 15:09:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.25
X-Spam-Level: 
X-Spam-Status: No, score=0.25 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, T_RP_MATCHES_RCVD=-0.01] autolearn=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 63FfwWJmGPZY; Fri,  4 Apr 2014 15:08:59 -0700 (PDT)
Received: from bmtwo.vm.bytemark.co.uk (mail.firsthand.net [IPv6:2001:41c8:1:6062::d46e:bc35]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABA31A00CA; Fri,  4 Apr 2014 15:08:59 -0700 (PDT)
X-No-Relay: not in my network
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=firsthand.net;  b=gcxJJWoKMUTXeyPiXMdAVkWKnUFM2SUoOPYounclwqUMP1HTPp9rzvXYHwkHJzxlFgjEo781l86KHtsNt7njp8/3069w6cbxw/OfADiB/Hkh8AQc8BfXV76SGS0Ak4wU; h=X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:X-No-Relay:Received:References:In-Reply-To:Mime-Version:Content-Transfer-Encoding:Content-Type:Message-Id:Cc:X-Mailer:From:Subject:Date:To;
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from [192.168.1.118] (host-78-149-8-96.as13285.net [78.149.8.96]) by bmtwo.vm.bytemark.co.uk (Postfix) with ESMTPSA id 957EFE0004; Fri,  4 Apr 2014 23:08:51 +0100 (BST)
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net> <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org> <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com> <F8B2F4F2-4B8F-49A8-8233-E80BAE737128@isoc.org>
In-Reply-To: <F8B2F4F2-4B8F-49A8-8233-E80BAE737128@isoc.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=utf-8
Message-Id: <0F1BA31B-4580-4AC0-9CB4-7FC0EE3860B0@firsthand.net>
X-Mailer: iPad Mail (11D167)
From: "cdel.firsthand.net" <cdel@firsthand.net>
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
Date: Fri, 4 Apr 2014 23:08:51 +0100
To: Ray Pelletier <rpelletier@isoc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BK6u_YPUalgD0LS3UTmgiqUZ5S0
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, IAOC <iaoc@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, The IESG <iesg@ietf.org>, John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 22:09:03 -0000

I was about to ask under what classes IETF registrations are held?=20


Christian de Larrinaga


> On 4 Apr 2014, at 22:57, Ray Pelletier <rpelletier@isoc.org> wrote:
>=20
>=20
>> On Apr 4, 2014, at 3:45 PM, John C Klensin <john-ietf@jck.com> wrote:
>>=20
>>=20
>>=20
>> --On Friday, April 04, 2014 14:19 -0400 Ray Pelletier
>> <rpelletier@isoc.org> wrote:
>>=20
>>>> It sounds as if this will open the door to my being able to
>>>> advertise myself as the IETF Secretariat.  Or even the ITU's
>>>> being able to.  Yes?
>>>=20
>>> You could certainly use "Secretariat" but you cannot use
>>> "IETF Secretariat" without violating the "IETF"
>>> trademark.
>>=20
>> Ray, I assume that if Dave (or someone else) set themselves up
>> as the International Elegant Tophat Fabrication Society, made at
>> least a perfunctory effect to establish themselves as being in
>> that business, established a business unit that they called
>> their "Secretariat", and then advertised the result as the "IETF
>> Secretariat", things could get dicey.  Given the different line
>> of business, they might even be able to take out a trademark on
>> "IETF Secretariat".  Right?
>=20
> The "risk" applies to IETF in addition to IETF Secretariat. =20
> We don't own IETF in every class of goods and services.=20
> IETF bananas, top hats and car tires can be sold and =20
> that won=E2=80=99t violate our IETF trademark =20
>=20
> People aren=E2=80=99t going to be confused between the two,
> just like they aren=E2=80=99t for Apple computers and Apple records.
>=20
> Ray
>>=20
>> Now, whether having a trademark registered as "IETF Secretariat"
>> with whatever line of business the IETF and IETF Secretariat
>> claim to be in would offer significant protection against that
>> attack is far outside my knowledge or experience.
>>=20
>> I have enough trouble imagining someone going to the trouble to
>> attempt the above as an attack that I think it would probably be
>> foolish to worry about it, but it is, in principle, the
>> difference between "no risk" and "no risk worth worrying about".
>>=20
>>   john
>=20


From nobody Fri Apr  4 15:48:02 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8618C1A01E6 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 15:48:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.763
X-Spam-Level: 
X-Spam-Status: No, score=0.763 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, LOTS_OF_MONEY=0.001, SPF_PASS=-0.001] autolearn=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 id6TAFr9b-p9 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 15:47:56 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5B7591A01F0 for <ietf@ietf.org>; Fri,  4 Apr 2014 15:47:56 -0700 (PDT)
Received: (qmail 80806 invoked from network); 4 Apr 2014 22:47:50 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 4 Apr 2014 22:47:50 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=533f3696.xn--9vv.k1404; i=johnl@user.iecc.com; bh=BGlXnWmu8zMcXfq0/QYjyVCDtCXgMDgzOK9OggUlOes=; b=mtlAOQTKxjB6Gw5S7+a95hTTc6sQs7u00fSsCnUAIE6FVMJzuIYcfLI+/J9zwsa9fmYzQ+lk7oviuxLSf6Otp+QVHAPomBtSr5BII2Xc2+JPbE6tO4DgVABC9L8aUPEv+vaXTm+Huj91bbcWl8a3TIeWT11BO66zVKy9zXYjQ125DAs6EXLH4cWg2jSCoWClXZVrImHWLxE0ImmyXrsxqg332edckM5Pizt7cslvwS6mZPqGwgBscnM7dzmzaITf
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=533f3696.xn--9vv.k1404; bh=BGlXnWmu8zMcXfq0/QYjyVCDtCXgMDgzOK9OggUlOes=; b=yGRM/0ojQldc4nZQePIDIqc3O345xDtt6o/NIzd8YLCv75hn0f4WzD3eWt+FmlK7Rswr9bP0Q/QAWcbzwz4win3T4gvV7u2dOq/JeXoMwvCGcUlVy1A60PKY0zFxTekrfA4FlpadqTtW0sk699uKSF98G6sAmNM6p3CtXGS+64laRKLaafTfQdvGPQJDjUt4mjbDlfygIHiKvIW1OkwcYZmAvSJZzB56ijml+xK3SM3yVzonip2YPQ3AQUAnTN8d
Date: 4 Apr 2014 22:47:28 -0000
Message-ID: <20140404224728.94976.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
In-Reply-To: <0F1BA31B-4580-4AC0-9CB4-7FC0EE3860B0@firsthand.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/b-QDVdzexbb0GsG0JVZAHDHji2Y
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 22:48:00 -0000

>I was about to ask under what classes IETF registrations are held? 

No need to ask when the answer is a few clicks away at uspto.gov.

The IETF has two trademark registrations, #78755455 on the term IETF,
and #78755496 on the logo.  Both are in the same three classes, one
cancelled and two active:

(CANCELLED) IC 009. US 021 023 026 036 038. G & S: [ CD-ROMs
containing technical, design, engineering, management and
administrative information in the field of standards and best
practices development for the development and evolution of the
Internet ]. FIRST USE: 19970831. FIRST USE IN COMMERCE: 19970831

IC 035. US 100 101 102. G & S: Providing information services and an
Internet website containing information about administrative,
management, and business standards and best practices for promoting
the development and evolution of the Internet. FIRST USE: 20011231.
FIRST USE IN COMMERCE: 20011231

IC 042. US 100 101. G & S: Providing information services and an
Internet website containing information about technical, engineering,
and design standards and best practices for the development and
evolution of the Internet. FIRST USE: 20011231. FIRST USE IN COMMERCE:
20011231

IETF SECRETARIAT is in two areas:

IC 035. US 100 101 102. G & S: Providing administrative, and
management support services in the field of standards related
activities to facilitate the development and evolution of global
computer networks. FIRST USE: 19990714. FIRST USE IN COMMERCE:
19990714

IC 042. US 100 101. G & S: Providing technical coordination support
services for standards related activities to facilitate the
development and evolution of global computer network. FIRST USE:
19990714. FIRST USE IN COMMERCE: 19990714

Did the IETF ever distribute CD-ROMS?  Not that I recall, but I'm a
relative newcomer.

R's,
John


From nobody Fri Apr  4 15:59:51 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD8341A025A for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 15:59:49 -0700 (PDT)
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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 4FvXddYE2OPu for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 15:59:45 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.163]) by ietfa.amsl.com (Postfix) with ESMTP id 60D1A1A0267 for <ietf@ietf.org>; Fri,  4 Apr 2014 15:59:45 -0700 (PDT)
Received: from [85.158.137.99:34573] by server-3.bemta-3.messagelabs.com id 5C/7A-05289-C593F335; Fri, 04 Apr 2014 22:59:40 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-217.messagelabs.com!1396652378!14266223!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11731 invoked from network); 4 Apr 2014 22:59:38 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-6.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 4 Apr 2014 22:59:38 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 4 Apr 2014 23:59:37 +0100
From: <l.wood@surrey.ac.uk>
To: <rwfranks@acm.org>, <hsantos@isdg.net>
Date: Fri, 4 Apr 2014 23:58:46 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9QQl0SJK7e4cRARV+uyHxqXlLYwQAFxI8w
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEBB@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net>, <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com>
In-Reply-To: <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iSXpB4e2mOBIkrFICJXXitaWJ5s
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 22:59:49 -0000

I haven't had an answer to my questions from Stephen.

"nonetheless access to that data
should use best practices for security and privacy."

why?

" New services will however generally only be made
available in ways that use security protocols such as
TLS."

again, why?


"Because... SECURITY!" would not be a good answer.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Dick Franks [rwfranks@acm.o=
rg]
Sent: 04 April 2014 21:12
To: Hector Santos
Cc: IETF-Discussion
Subject: Re: Security for various IETF services

On 4 April 2014 20:48, Hector Santos <hsantos@isdg.net<mailto:hsantos@isdg.=
net>> wrote:

Everyone else has already touch based with the same issues.

 Silence could easily be misconstrued as acceptance.

[snip]
  Stephen asked about the last sentence:

  New services will however generally only be made
  available in ways that use security protocols such as
  TLS.

Which to my eye looks like a conclusion;  without shred of justification an=
d before any meaningful discussion has taken place.


26 messages on and the consensus thus far is that an answer to Lloyd Wood's=
 one-liner is very much required.


From nobody Fri Apr  4 16:06:40 2014
Return-Path: <pranesh@cis-india.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 212BA1A02C3 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 16:06:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.045
X-Spam-Level: *
X-Spam-Status: No, score=1.045 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FU_ENDS_2_WRDS=0.255, RCVD_IN_PSBL=2.7, T_RP_MATCHES_RCVD=-0.01] autolearn=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 Ht5jFTUtwsl1 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 16:06:35 -0700 (PDT)
Received: from mail.cis-india.org (mail.cis-india.org [202.190.125.68]) by ietfa.amsl.com (Postfix) with ESMTP id 3CABF1A02B0 for <ietf@ietf.org>; Fri,  4 Apr 2014 16:06:35 -0700 (PDT)
Received: from [192.168.1.65] (unknown [162.243.72.125]) by mail.cis-india.org (Postfix) with ESMTPSA id B0496A7DD84; Fri,  4 Apr 2014 23:03:48 +0000 (UTC)
Message-ID: <533F3AD5.6000408@cis-india.org>
Date: Fri, 04 Apr 2014 19:05:57 -0400
From: Pranesh Prakash <pranesh@cis-india.org>
Organization: Centre for Internet and Society
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Randall Gellens <randy@qti.qualcomm.com>,  Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533DF52E.5020707@cis-india.org> <p06240605cf63c268e7df@[99.111.97.136]>
In-Reply-To: <p06240605cf63c268e7df@[99.111.97.136]>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="du1HMAd3EL5G9M1AITcvUi4EHo24nN55K"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/IjD-58pMwd73oQhOowTJgk3SSJ0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Apr 2014 23:06:39 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--du1HMAd3EL5G9M1AITcvUi4EHo24nN55K
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Randall Gellens <randy@qti.qualcomm.com> [2014-04-03 19:00:18 -0700]:
> At 7:56 PM -0400 4/3/14, Pranesh Prakash wrote:
>
>>>  However, as there are numerous legacy tools that have been
>>>  built that require access via cleartext
>>
>>  Could you please expand on this?  What kinds of legacy tools is that
>> statement talking about?
>
> I have a number of tools and scripts that access IETF and RFC Editor
> documents and information using HTTP and FTP.

And these tools and scripts will stop working if HTTPS or FTPS are used? =

   Can these tools and scripts not be made to work/compile with NSS /=20
GnuTLS / OpenSSL?  Or is it just that it is easier not to deal with=20
encryption?

Curl, wget, and even the perl-based Twitter client I use (ttytter) all=20
work just fine with SSL, so I'm curious what tools and scripts have=20
trouble using encryption.

--=20
Pranesh Prakash
Policy Director, Centre for Internet and Society
T: +91 80 40926283 | W: http://cis-india.org
-------------------
Access to Knowledge Fellow, Information Society Project, Yale Law School
M: +1 520 314 7147 | W: http://yaleisp.org
PGP ID: 0x1D5C5F07 | Twitter: https://twitter.com/pranesh_prakash




--du1HMAd3EL5G9M1AITcvUi4EHo24nN55K
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCAAGBQJTPzrVAAoJEFUPonS5l6CpGRYQAKVowGJMV0W3ytDSbatszU5c
6W1wOhIAkhBg57H4pEuBttCHrFE57MVlJmnlIqHn9E0m2yHyv/vqHuTjRAcIKAyg
tEFN8jcbNphr6nZ5uuYCQimJhC0qG9wBmJ7ai6lqXx+VukG3T25Pd3Kmy/m2O/Nt
6G2YJ9PcRpGUhAsBduuu5InhJ7OuQm1XVefbdXJfDJpAwXPb5fbv7R9D8dFVVpz6
ntATLHmBTDwPZ3TA1xlwKZGia0CJMOi/WdAIto3xTuQ6FST38JT0YJJmz5Nu4qE4
TE4u4hT384iPzaeWKE4iUewnXfboVaENjb/5q67ISyK7BvAeYeXC/hIPanxxd9ho
fM0tujRn/WdUppz2ZDDrCqBVeolGN1ZBaX0tW1JTQykXYJhuu6Dh37VfAA2eIRjr
SRtDgAJqDb2EUaKc//QDCwo+7YplwY7cBsbc+go6PEFJTSG2+Ww+uSWOCGnnpuq8
JiIdiowuftKr7G4FWaAqOaYPFpsj8eddH4NQk4PZqHcKbT9lmQoVgv9yIINuwtor
QM0Bnjv3MR6qImGmE02qmV/BQywZuSx03RuHEqu/aEbw64Sei5QiM/jUFjfgpCUh
P4b3t9+3VRntD8MKL8FrfEZhGh51QvcwzvMbQn9ic+E6nTz9yTWg1c778b7thyf2
GoplLlGJQLGf8/3wwalK
=n2V5
-----END PGP SIGNATURE-----

--du1HMAd3EL5G9M1AITcvUi4EHo24nN55K--


From nobody Fri Apr  4 17:02:57 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 831F21A0343 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 17:02:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 uW32ISwvJv9f for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 17:02:51 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 868D31A02AF for <ietf@ietf.org>; Fri,  4 Apr 2014 17:02:51 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id cc10so2187524wib.2 for <ietf@ietf.org>; Fri, 04 Apr 2014 17:02:46 -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:content-type; bh=aCESaq1gHiccw2GNQ+h26Nr4i4eFNYZ0hr6PM4364tU=; b=KLev1iwDvUhj0UKqzbpLo8iZiuRMnCrpl+pM5NZipUTCpWXrzRN0pHfmfCbZeVs6uG F9eBGwQmaRW7O/aMhSGpGqm2xXX2btf7CT6Kqmamv8Z6fvEm6G8hgEsrujsh4ux1Jaft 2ue/aGbvn8Q9/nvihGF720kutjJMREOYX/4Ocd73B0bSHFTO1suguWWMQ+mRxFQ7aKea MKV8BKgqMV5p8fBz0JiaZTuRG7mHSI+ju4A0mw3ucVVXXVy9WGDUlQqlBt7L7c8vcAyJ 2KjwGymeWDk9pjtLCEK13jUbfGfB5HXHxLPUhpnt6alXfSn8zukrmQpfm6QVlO0XU7ED hR0Q==
MIME-Version: 1.0
X-Received: by 10.194.82.9 with SMTP id e9mr23675974wjy.45.1396656166343; Fri, 04 Apr 2014 17:02:46 -0700 (PDT)
Received: by 10.227.147.10 with HTTP; Fri, 4 Apr 2014 17:02:46 -0700 (PDT)
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEBB@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net> <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E779EEBB@EXMB01CMS.surrey.ac.uk>
Date: Fri, 4 Apr 2014 17:02:46 -0700
Message-ID: <CABkgnnV=x1+2_FeJMf2p65qcwW3-qrUW8hbM8p06PDC6wXuoBw@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Martin Thomson <martin.thomson@gmail.com>
To: l.wood@surrey.ac.uk
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/sGTs-0yZ0AGdP1QbgYLy5lubbPs
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 00:02:57 -0000

On 4 April 2014 15:58,  <l.wood@surrey.ac.uk> wrote:
> I haven't had an answer to my questions from Stephen.

I think that the question has been answered adequately, if not
directly in this thread by Stephen himself.  By Fred, Dave, and by
others.

I found the answers sufficiently compelling, even if it seems like you did not.


From nobody Fri Apr  4 22:13:11 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3112D1A00A8 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 22:13:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 S4qIsrh1xTvN for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 22:12:59 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B70B71A001E for <ietf@ietf.org>; Fri,  4 Apr 2014 22:12:59 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WWIuG-000ECJ-LC; Sat, 05 Apr 2014 01:12:40 -0400
Date: Sat, 05 Apr 2014 01:12:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Pranesh Prakash <pranesh@cis-india.org>, Randall Gellens <randy@qti.qualcomm.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
Message-ID: <74F15552A07DC08F9A9822B4@JcK-HP8200.jck.com>
In-Reply-To: <533F3AD5.6000408@cis-india.org>
References: <533D8A90.60309@cs.tcd.ie> <533DF52E.5020707@cis-india.org> <p06240605cf63c268e7df@[99.111.97.136]> <533F3AD5.6000408@cis-india.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ybu02S02MGobREPaaCRhOVgiUNc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 05:13:04 -0000

--On Friday, April 04, 2014 19:05 -0400 Pranesh Prakash
<pranesh@cis-india.org> wrote:

> Randall Gellens <randy@qti.qualcomm.com> [2014-04-03 19:00:18
> -0700]:
>> At 7:56 PM -0400 4/3/14, Pranesh Prakash wrote:
>> 
>>>>  However, as there are numerous legacy tools that have been
>>>>  built that require access via cleartext
>>> 
>>>  Could you please expand on this?  What kinds of legacy
>>>  tools is that statement talking about?
>> 
>> I have a number of tools and scripts that access IETF and RFC
>> Editor documents and information using HTTP and FTP.
> 
> And these tools and scripts will stop working if HTTPS or FTPS
> are used?    Can these tools and scripts not be made to
> work/compile with NSS / GnuTLS / OpenSSL?  Or is it just that
> it is easier not to deal with encryption?

I can't speak for Randy's, but, for the ones I use, yes, they
will stop working.  And, no, I don't have access to source or
other arrangements that would permit me to recode and recompile
them.

> Curl, wget, and even the perl-based Twitter client I use
> (ttytter) all work just fine with SSL, so I'm curious what
> tools and scripts have trouble using encryption.

See my earlier message.
    john





From nobody Fri Apr  4 22:40:26 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB11C1A00B8 for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 22:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 IjWcDJk1jtMb for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 22:40:19 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 450421A02DF for <ietf@ietf.org>; Fri,  4 Apr 2014 22:40:16 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WWJKs-000EDa-Ph; Sat, 05 Apr 2014 01:40:10 -0400
Date: Sat, 05 Apr 2014 01:40:05 -0400
From: John C Klensin <john-ietf@jck.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: CD-ROMs and secure access (was: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark)
Message-ID: <3F86EAF1605477ACEA9E6FB0@JcK-HP8200.jck.com>
In-Reply-To: <20140404224728.94976.qmail@joyce.lan>
References: <20140404224728.94976.qmail@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0B9uTkg7LU07OakBVjCr9V1YwUk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 05:40:24 -0000

--On Friday, April 04, 2014 22:47 +0000 John Levine
<johnl@taugh.com> wrote:

>...
> Did the IETF ever distribute CD-ROMS?  Not that I recall, but
> I'm a relative newcomer.

Yes.  Meeting proceedings were distributed in CD-ROM form for
several years (after distribution in paper volumes was
discontinued).  

IIR, at the time physical distribution of CD-ROMs was
discontinued, there was a commitment to make ISO-format images
available for the whole set for a meeting as well as the HTML
pages that are broken up by, chapter categories and then e.g.,
by area and WG.  As far as I can tell from a quick scan of the
archives, that project was never initiated.  Also, while I know
that most people in the community are quite certain that HTTP
access to structured HTML (mixed with text and PDF) files will
be available forever, it may be that having proceedings only in
that form will eventually turn out to be inconsistent with our
supposed commitments to historical preservation.  

That is another part of the "security and the files" discussion:
if one looks at the very long term, it is much easier to have
confidence in availability of materials through methods that do
not require encrypted access using particular encryption
technologies then through those that do.   So a decision to make
information available only via security-protected mechanisms
may, depending on the techniques chosen, imply a somewhat larger
maintenance commitment than access that does not require those
mechanisms.

     john


From nobody Fri Apr  4 23:39:11 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0CCF1A032A for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 23:39:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.561
X-Spam-Level: 
X-Spam-Status: No, score=-1.561 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 KHvf2murkVeN for <ietf@ietfa.amsl.com>; Fri,  4 Apr 2014 23:39:05 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id 40F3D1A02F2 for <ietf@ietf.org>; Fri,  4 Apr 2014 23:39:04 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9E193A3; Sat,  5 Apr 2014 08:38:57 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 94097A2 for <ietf@ietf.org>; Sat,  5 Apr 2014 08:38:57 +0200 (CEST)
Date: Sat, 5 Apr 2014 08:38:57 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: CD-ROMs and secure access (was: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark)
In-Reply-To: <3F86EAF1605477ACEA9E6FB0@JcK-HP8200.jck.com>
Message-ID: <alpine.DEB.2.02.1404050836290.10236@uplift.swm.pp.se>
References: <20140404224728.94976.qmail@joyce.lan> <3F86EAF1605477ACEA9E6FB0@JcK-HP8200.jck.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/avncj_LdVWvdb40_tOiCbp8k9nk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 06:39:09 -0000

On Sat, 5 Apr 2014, John C Klensin wrote:

> be available forever, it may be that having proceedings only in
> that form will eventually turn out to be inconsistent with our
> supposed commitments to historical preservation.

Speaking of which, how is the data/documents/whatever IETF produces backed 
up? I would feel better if I knew that there were 10+ backups spread 
around the world. This would include recordings from the meetings, 
documents (all kinds) etc.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Sat Apr  5 01:50:35 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0C151A03B1; Sat,  5 Apr 2014 01:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 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_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 SD7Z_DP6qMzP; Sat,  5 Apr 2014 01:50:28 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 4713D1A0085; Sat,  5 Apr 2014 01:50:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1326; q=dns/txt; s=iport; t=1396687824; x=1397897424; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=vC24JDfr1NZkcJGOR8pfdWLwwiS+D5w+dA2arDHeW7o=; b=gyh7D1Xd+VwjHvMEerpy3OYLawepcpmiZ7QX7ECvTUTDnGGTsMXuYUGw S0NMA3RL/YBBWFMGSDPpW3aKRFrw+dQKmaYUfLsasWQ+7dOXc4rGNWZLK YyQ6dklliOu193P6DfSu3L+VB66vWTldVaUoDnYzfnf6cqowEm/mHSl6+ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjcFAFzDP1OtJV2c/2dsb2JhbABZgwbFIoEZFnSCJQEBAQMBOj8QAgEINhAyJQIEDod2CNAmF44gAQFPB4MkgRQEmFuSP4MwgXI
X-IronPort-AV: E=Sophos;i="4.97,799,1389744000"; d="scan'208";a="315532613"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-4.cisco.com with ESMTP; 05 Apr 2014 08:50:22 +0000
Received: from xhc-rcd-x11.cisco.com (xhc-rcd-x11.cisco.com [173.37.183.85]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s358oMTZ026012 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 5 Apr 2014 08:50:22 GMT
Received: from xmb-rcd-x04.cisco.com ([169.254.8.101]) by xhc-rcd-x11.cisco.com ([173.37.183.85]) with mapi id 14.03.0123.003; Sat, 5 Apr 2014 03:50:21 -0500
From: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPUC2GODnIxqXM80KR8vvcGbq07psCt8zG
Date: Sat, 5 Apr 2014 08:50:21 +0000
Message-ID: <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com>
References: <533D8A90.60309@cs.tcd.ie>,<533EEF35.7070901@isdg.net>
In-Reply-To: <533EEF35.7070901@isdg.net>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2lglnoiOcqv1gImSRQdHBJehcyk
Cc: IETF-Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 08:50:32 -0000

>>=20
>> "The IETF are committed to providing secure and privacy
>> friendly access to information via the web, mail, jabber
>> and other services.

Please confirm that "friendly" implies that the user gets to
choose the degree of security privacy that they consider=20
appropriate, and that their applications and devices are not=20
encumbered  with the overheads unless they choose to invoke
the privacy and security mechanisms.
=20

>> While most (but not all) data on IETF
>> services is public, nonetheless access to that data
>> should use best practices for security and privacy.

I agree, but please can you clarify your interpretation
of "best practise" so that we can understand how
liberal or prescriptive this is?

>> However, as there are numerous legacy tools that have been
>> built that require access via cleartext, the IETF will
>> continue to allow such access so as not to break such
>> tooling. New services will however generally only be made
>> available in ways that use security protocols such as
>> TLS."
>>=20

That is worrying, because it seems that you are intent on
encumbering transactions, without requiring a case by=20
case study of the threat model, and applying a security
and privacy model that is appropriate to the specific=20
transaction.

Stewart.


From nobody Sat Apr  5 02:39:04 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF351A03DA; Sat,  5 Apr 2014 02:39:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 68AULPUE7PYA; Sat,  5 Apr 2014 02:38:59 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.162]) by ietfa.amsl.com (Postfix) with ESMTP id 3C77A1A03D8; Sat,  5 Apr 2014 02:38:59 -0700 (PDT)
Received: from [195.245.230.131:5848] by server-2.bemta-3.messagelabs.com id 15/C9-23530-D2FCF335; Sat, 05 Apr 2014 09:38:53 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-78.messagelabs.com!1396690732!23839049!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20076 invoked from network); 5 Apr 2014 09:38:52 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-14.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 5 Apr 2014 09:38:52 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Sat, 5 Apr 2014 10:38:52 +0100
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <stephen.farrell@cs.tcd.ie>
Date: Sat, 5 Apr 2014 10:38:51 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPUC2GODnIxqXM80KR8vvcGbq07psCt8zGgAALbI0=
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEBE@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie>, <533EEF35.7070901@isdg.net>, <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com>
In-Reply-To: <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/sPl-wK_WY98l09ICGu-F89t6eRM
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 09:39:04 -0000

"That is worrying, because it seems that you are intent on
encumbering transactions, without requiring a case by
case study of the threat model, and applying a security
and privacy model that is appropriate to the specific
transaction."

yes. not coincidentally, that's EXACTLY what Stephen
encouraged in DTNRG, starting with MD5-is-ALWAYS-bad
and working up to the-security-model-is-everything. As
opposed to the needs of the networking scenario.

we had the perpass debate, and here we go again.
Well, you've been warned.

Lloyd Wood
http://sat-net.com/L.Wood/dtn
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant (stbryant) [=
stbryant@cisco.com]
Sent: 05 April 2014 09:50
To: Stephen Farrell
Cc: IETF-Discussion; The IESG
Subject: Re: Security for various IETF services

>>
>> "The IETF are committed to providing secure and privacy
>> friendly access to information via the web, mail, jabber
>> and other services.

Please confirm that "friendly" implies that the user gets to
choose the degree of security privacy that they consider
appropriate, and that their applications and devices are not
encumbered  with the overheads unless they choose to invoke
the privacy and security mechanisms.


>> While most (but not all) data on IETF
>> services is public, nonetheless access to that data
>> should use best practices for security and privacy.

I agree, but please can you clarify your interpretation
of "best practise" so that we can understand how
liberal or prescriptive this is?

>> However, as there are numerous legacy tools that have been
>> built that require access via cleartext, the IETF will
>> continue to allow such access so as not to break such
>> tooling. New services will however generally only be made
>> available in ways that use security protocols such as
>> TLS."
>>

That is worrying, because it seems that you are intent on
encumbering transactions, without requiring a case by
case study of the threat model, and applying a security
and privacy model that is appropriate to the specific
transaction.

Stewart.


From nobody Sat Apr  5 06:21:41 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7914A1A044C for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 06:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level: 
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 4d1W3ChDAmx0 for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 06:21:35 -0700 (PDT)
Received: from ntbbs.santronics.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id D0C571A0428 for <ietf@ietf.org>; Sat,  5 Apr 2014 06:21:34 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1540; t=1396704085; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=iZIBFKSu/+2MgKq5yJdiF1i7uNk=; b=O5+Qio5iAESO6WJUeCUA SqqNuby+ckaABlonLNNuUZ0tsFXPzvhiPqsED79+b2Ji8X8HC1GX1Uvvqv9HedxI i9b4F5hnodFh6JVLalwJngMppECrME9SRAq1pwpZQLNoHvsAg0mUz8MpK0lDWQwO nNm9uf+OBRAbIPjNmzNWClc=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 05 Apr 2014 08:21:25 -0500
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1691539660.604.4468; Sat, 05 Apr 2014 08:21:23 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1540; t=1396704032; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=AmNxw9H +CPtDwMgzHYpOZWhcgZnhpaTcBXTW2Diigjk=; b=zY7ZUuWoXO4N94Bq5ZGLCEY 6ecH4ZK04cAo+iD5ciBa9oIGf/Vu8dd6lw9f9/HuEPqf3BKO4JDBPKqvg1v06Zay eMEorF5SF8ODYe7X6y0k34yIYwoLXVgnY3xSLYkRWA89b4TXAJTQcgJdleIaTnvB ekWXV6cpgQW9sQFHVNDg=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 05 Apr 2014 09:20:32 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1137788819.9.16568; Sat, 05 Apr 2014 09:20:32 -0400
Message-ID: <53400355.7030807@isdg.net>
Date: Sat, 05 Apr 2014 09:21:25 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Dick Franks <rwfranks@acm.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net> <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com>
In-Reply-To: <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AyqiiNuCxRU_grhJL6lS_-lhPNc
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 13:21:39 -0000

On 4/4/2014 4:12 PM, Dick Franks wrote:
>
>        Stephen asked about the last sentence:
>
>        New services will however generally only be made
>        available in ways that use security protocols such as
>        TLS.
>
> Which to my eye looks like a conclusion;  without shred of
> justification and before any meaningful discussion has taken place.

I don't see anything odd about the statement. My input, once again and 
I'll leave it at this, there might be 'new services' where the IETF 
has no "legal" OR "Security Audit" choice but to provide it in secured 
only mode and thus, for those who need to get access MUST be updated 
with modern software client access tools that support such security, 
not just TLS.   The IETF lawyer should determine if they must comply 
with PCI/DSS security audits.  Thats all. It wasn't difficult.

Of course, where it isn't needed, its common sense to keep legacy 
access for the old timers to access it via their own means or tools. 
  That includes me with various simple access tools, in particular, a 
non-SSL FTP scripting tool for quick command line download of RFC 
files from the IETF ftp site.  If that was made SSL only, we would 
have to update the script. I don't have time for that so it would 
"break something" for me.

> 26 messages on and the consensus thus far is that an answer to Lloyd
> Wood's one-liner is very much required.

I didn't see anything that stood out. Are you referring to his why 
question?  Really?  It seems others answered why.

Thanks for your comments.

-- 
HLS



From nobody Sat Apr  5 06:41:17 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C00671A0182 for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 06:41:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 AWhy6iHqxTPv for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 06:41:11 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.171]) by ietfa.amsl.com (Postfix) with ESMTP id 3D96C1A017A for <ietf@ietf.org>; Sat,  5 Apr 2014 06:41:11 -0700 (PDT)
Received: from [85.158.137.99:25758] by server-11.bemta-3.messagelabs.com id 61/24-19438-1F700435; Sat, 05 Apr 2014 13:41:05 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-217.messagelabs.com!1396705264!14082871!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 18559 invoked from network); 5 Apr 2014 13:41:05 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-8.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 5 Apr 2014 13:41:05 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Sat, 5 Apr 2014 14:41:04 +0100
From: <l.wood@surrey.ac.uk>
To: <hsantos@isdg.net>, <rwfranks@acm.org>
Date: Sat, 5 Apr 2014 14:40:17 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9Q0g1ZWIrNnh4nRLeyP8py/UzDdAAAodTT
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEBF@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net> <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com>, <53400355.7030807@isdg.net>
In-Reply-To: <53400355.7030807@isdg.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/c88rejkdLwEepyVLpD8i-NYIa1w
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 13:41:16 -0000

"I didn't see anything that stood out. Are you referring to his why
question?  Really?  It seems others answered why."

they did not.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Hector Santos [hsantos@isdg=
.net]
Sent: 05 April 2014 14:21
To: Dick Franks
Cc: IETF-Discussion
Subject: Re: Security for various IETF services

On 4/4/2014 4:12 PM, Dick Franks wrote:
>
>        Stephen asked about the last sentence:
>
>        New services will however generally only be made
>        available in ways that use security protocols such as
>        TLS.
>
> Which to my eye looks like a conclusion;  without shred of
> justification and before any meaningful discussion has taken place.

I don't see anything odd about the statement. My input, once again and
I'll leave it at this, there might be 'new services' where the IETF
has no "legal" OR "Security Audit" choice but to provide it in secured
only mode and thus, for those who need to get access MUST be updated
with modern software client access tools that support such security,
not just TLS.   The IETF lawyer should determine if they must comply
with PCI/DSS security audits.  Thats all. It wasn't difficult.

Of course, where it isn't needed, its common sense to keep legacy
access for the old timers to access it via their own means or tools.
  That includes me with various simple access tools, in particular, a
non-SSL FTP scripting tool for quick command line download of RFC
files from the IETF ftp site.  If that was made SSL only, we would
have to update the script. I don't have time for that so it would
"break something" for me.

> 26 messages on and the consensus thus far is that an answer to Lloyd
> Wood's one-liner is very much required.

I didn't see anything that stood out. Are you referring to his why
question?  Really?  It seems others answered why.

Thanks for your comments.

--
HLS


From nobody Sat Apr  5 08:23:18 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DC5E1A01A5; Sat,  5 Apr 2014 08:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.95
X-Spam-Level: 
X-Spam-Status: No, score=0.95 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 L2-GRALffltp; Sat,  5 Apr 2014 08:23:10 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4F1121A018C; Sat,  5 Apr 2014 08:23:10 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id eb12so4895464oac.30 for <multiple recipients>; Sat, 05 Apr 2014 08:23:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=dGXDd8s7r2BciJ/PKBcXMBZKHvmrP6VKqil5pkwRzpU=; b=KNlB8+RyS7nB3djXTTq8duOFR+3EqLebQBpuPzTB+R/MUlRX8OckelW91z8/pVDRJW CCdylmxPEN2kAbbgzwKmfwS29Dr9RYfik38fk9dTj+M4k7TzK/aMhHdty2AXKPrKkEhG 6zOxXwDNsTYZxTZE8hPqbVKrneIxdAvsI+GxjKrNP3JWPavzPHQN+KSUJKJzLogrZuC/ Y71cZ9fbsQRzLfcu6gyqIgWwvt0QXK5KjsxG/F+1d5xYfcYfvCYiNdxr35azSud+L+cs azQlE2gcStWr3OCWNxXsEumz1UEwZ2twFxeF4LyOIDKoZnjkdYwYW/tTAncrjF4jFM79 tEUw==
X-Received: by 10.182.44.232 with SMTP id h8mr64072obm.73.1396711385266; Sat, 05 Apr 2014 08:23:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Sat, 5 Apr 2014 08:22:45 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sat, 5 Apr 2014 11:22:45 -0400
Message-ID: <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/n32gipcI6iYya9913JCYU-gvaEc
Cc: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 15:23:14 -0000

Hi David,

Thanks for this very thorough review. See my responses below:

On Sat, Mar 29, 2014 at 10:23 PM, Black, David <david.black@emc.com> wrote:
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-trill-esadi-06.txt
> Reviewer: David L. Black
> Review Date: March 29, 2014
> IETF LC End Date: April 1, 2014
>
> Summary: This draft is on the right track, but has open issues
> described in the review.
>
> This draft revises the ESADI specification for TRILL from its
> original form in RFC 6325.
>
> Major issues:
>
> The draft changes ESADI in a non-backwards-compatible fashion from
> its original specification in RFC 6325, but does not explain why this
> is ok.  That explanation needs to be provided, and if implementations
> of ESADI as originally specified in RFC 6325 exist, that explanation
> needs to encompass coexistence and interoperability (or lack thereof)
> with such implementations.  That explanation probably belongs in
> Section 1.1, and could be expanded upon in Appendix A.

This was a considered decision of the TRILL WG. At least since the -02
version in February 2013, the ESADI WG draft has had ESADI-LSP
provisions that were incompatible with RFC 6325 ESADI for the purpose
of accomodating orders of magnitude more LSP fragments. This text in
the draft, which originally used a somewhat ad hoc change from IS-IS
LSPs to accomodate additional fragments, was posted to the list
without objection before being incorporated. Since a standard IS-IS
way of doing this was later in process in the ISIS WG, the ESADI draft
was changed to follow this more standard way of providing for more LSP
fragments and a new WG Last Call done in the TRILL WG specifically on
this issue. See

http://www.ietf.org/mail-archive/web/trill/current/msg06037.html
http://www.ietf.org/mail-archive/web/trill/current/msg06009.html

In Appendix A (Changes to [RFC6325]), how about replacing items 2 and
3 in the list as follows (includes fixing a typo in item 3):

OLD
   2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
      is changed from the base IS-IS format to the Extended Level 1
      Circuit Scoped format in [FS-LSP].
NEW
   2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
      is changed from the base IS-IS format to the Extended Level 1
      Circuit Scoped format (E-L1CS) specified in [FS-LSP]. This
      change is not backwards compatible with [RFC6325]. It is made in
      light of (a) the very limited, if any, deployment of [RFC6325]
      ESADI, and (b) the 256 times greater information carrying
      capacity of the E-L1CS format compared with the base IS-IS
      format. It is anticipated that this greater carrying capacity
      will be needed, under some circumstances, to carry end station
      addressing information or other information that is added to
      ESADI in the future.
OLD
   3. Unicasting of ESADI PDUs is supported including replacing Section
      4.6.2.2 of [RFC6325] with the next text give in Section 4.1 of
      this document.
NEW
   3. Unicasting of ESADI PDUs is optionally supported including
      replacing Section 4.6.2.2 of [RFC6325] with the new text give in
      Section 4.1 of this document. This unicast support is backwards
      compatible because it is only used when the recipient RBridge
      signals its support.

See possible replacement below for the first paragraph of Section 1.1
that includes a condensed version of this additional material
concerning backwards non-compatibility.

> Overall, this draft is not self-contained - to a significant extent,
> it is written as if it were effectively a long collection of errata
> to the ESADI specification in RFC 6325. That makes it difficult to
> understand - it would be better if this draft completely obsoleted
> and replaced the ESADI specification in RFC 6325, describing its
> changes, instead of providing specific text changes to portions of
> the RFC 6325 text.

All of the changes to ESADI are described in Appendix A.

If the ESADI related material in RFC 6325 was entirely contained in
one contiguous area of RFC 6325, it would have been easy to write this
draft as simply obsoleting and replacing that area of RFC 6325.  The
largest such monolithic block on ESADI in RFC 6325 is Section 4.2.5
(The TRILL ESADI Protocol), including its two subsections ("4.2.5.1
TRILL ESADI Participation" and "4.2.5.2 TRILL ESADI Information"). All
of that is obsoleted and replaced by this draft.  However, there are
other non-contiguous parts of RFC 6325 necessarily affected. For
example, Section 4.6 of RFC 6325 describes how to handle every
possible type of frame that might be received; since an ESADI PDU is
one such type of frame, it is necessary to change Section 4.6.2.2
("TRILL ESADI Frames") of RFC 6325.

There is really no substitute for having a general familiarity with
RFC 6325 in understanding this document. Although I have seen IESG
members criticize statements such as "Familiarity with X is assumed."
when X is a normative reference, on the grounds that familiarity with
all normative references is automatically assumed, perhaps some such
statement is warranted in this case.

In addressing both of your issues here, the first paragraph of Section
1.1 could be changed as follows:

OLD
   This document updates [RFC6325], the TRILL base specification,
   replacing the description of the ESADI protocol in Section 4.2.5 of
   [RFC6325], providing more detail, and prevailing over [RFC6325] where
   they conflict. The changes are summarized in Appendix A. These
   changes are not backwards compatible because, among other things,
   they change the format of ESADI-LSPs.
NEW
   This document updates [RFC6325], the TRILL base protocol
   specification, obsoleting and replacing the description of the
   ESADI protocol (Section 4.2.5 of [RFC6325] including all
   subsections), providing more detail on ESADI, updating other ESADI
   related sections of [RFC6325], and prevailing over [RFC6325] in any
   case where they conflict. For this reason, familiarity with
   [RFC6325] is particularly assumed.  These changes are not backwards
   compatible because they change the format of ESADI-LSPs to
   substantially increase the amount of information that can be
   carried. These changes are further discussed in Appendix A.


> Minor issues:
>
> I don't understand the discussion in section 2 of it being "an
> implementation decision how independent the multiple ESADI instances
> at an RBridge are" in light of the clear statement that "the ESADI
> update process operates separately for each ESADI instance."  The
> example given involves database structure considerations that are
> specific to the node implementation and do not affect the independent
> updates for each ESADI instance.  There may not be an actual
> technical problem here, but at least the first chunk of text quoted
> in this paragraph of the review needs to be rewritten.

Two things motivated the text you cite in Section 2: (1) ESADI uses
multiple instances of the flooding process for the purpose of limiting
the flooding to the TRILL switches that have expressed interest in a
particular Data Label. RFC 6822 specifies a different type of IS-IS
"instance" and there is some implication in 6822 of fault and
performance isolation between RFC 6822 instances. Although this
document says its instances are not the same as RFC 6822 instances,
someone might still have the impression that ESADI instances are
necessarily to be implemented inside a TRILL switch is a highly
isolated manner. This text is to emphasize that the extent to which
the execution of different ESADI instances are isolated within a TRILL
switch is an implementation decision. (2) Perhaps a symptom of item 1:
in early discussions of ESADI, there were multiple complaints that
maintaining 'so many different link state databases' in a TRILL switch
would be an undue burden. So the text here specifically mentions that
the databases for all ESADI instances at a TRILL switch can be merged
(with an appropriate marker in each record saying which instance it
belongs to).

While the IETF generally standardizes bits on the wire and not
internal implementation details, the above concerns lead to these few
sentences to dispel any false impression.  I do not really see how
there can be much confusion since the draft also says, as your point
out, "But the ESADI update process operates separately for each ESADI
instance and independently from the TRILL IS-IS update process.". I
suggest the following change:

OLD
   It is an implementation decision how independent the multiple ESADI
   instances at an RBridge are.
NEW
   This specification does not constrain how coupled or independent
   the multiple ESADI instances are in their implementation internal
   to an RBridge.


> Also in Section 2:
>
>    ESADI does no routing so there is no reason for pseudo-nodes in ESADI
>    and none are created.
>
> Need to explain what a pseudo-node is before this sentence.

I do not think this document is the right place for a detailed
explanation of pseudo-nodes. How about changing to the following:

   ESADI does no routing calculations so there is no reason for
   pseudo-nodes in ESADI and none are created (Pseudo-nodes [IS-IS]
   are a construct for optimizing routing calculations.)


> p.9, Figure 2 - explain how the receiver determines whether the inner
> Ethernet header contains a VLAN tag or FGL.  This also applies to Figure
> 3 on p.10.

I'm not sure this draft is the place for a detailed explanation but I
have no problem adding the already existing reference "[RFCfgl]" to
both figures right after where they say "VLAN or FGL Data Label (4 or
8 bytes)". That referenced document [RFCfgl], which is in the RFC
Editor's queue, explains this.


> p.10, Section 2.1:
>
>    All transit RBridges forward ESADI packets as if they were ordinary
>    TRILL Data packets.
>
> Need to explain what a "transit" RBridge is.  Between this and the
> above pseudo-node comment, I suggest adding an overview of the
> TRILL protocol to the start of Section 2.

How about just eliminating the word "transit", which I don't think is
necessary, and changing the sentence in question to

     All RBridges forward ESADI packets as if they were ordinary TRILL
     Data packets [RFC6325].


> p.11, Section 2.1:
>
>    No "routing" computation or routing decisions ever have to be
>    performed by ESADI.
>
> What is a ' "routing" computation' ??  This should be rephrased to
> contrast to what the non-ESADI TRILL usage of IS-IS does.

How about the following change:

OLD
   No "routing" computation or routing decisions ever have to be
   performed by ESADI.
NEW
   No "routing" calculation (least cost path or distribution tree
   construction) ever has to be performed by ESADI.


> p.12, Section 2.2:
>
>    If a VLAN or FGL ID
>    field within an ESADI-LSP PDU does include a value, that field's
>    contents is ignored.
>
> This looks like it's an important requirement, so:
>          "is ignored" -> "MUST be ignored"

OK.


> p.13, Section 3
>
>   "SNPA/MAC address"
>    is not considered in this tie breaking and there is no "Port ID".
>
> This is contrasting ESADI tie-breaking to a tie-breaking procedure
> that I'd guess is specified in another document; that needs to be
> explained, along with a reference to that document, preferably with
> the section number where the other tie-breaking procedure is
> specified.

The other document is [rfc6327bis] which is referenced.  However, this
reference can be made clearer. How about

OLD
   Generally speaking, the DRB election on the ESADI virtual link (see
   Section 2.1) operates similarly to a TRILL IS-IS broadcast link
   [rfc6327bis] with the following exceptions:
NEW
   Generally speaking, the DRB election on the ESADI virtual link (see
   Section 2.1) operates similarly to the DRB election on a TRILL
   IS-IS broadcast link, as described in Section 4.2.1 ("DRB Election
   Details") of [rfc6327bis], with the following exceptions:


> Section 6 - explain where the 1470 byte number in the third
> paragraph comes from.

How about adding the following at the end of the relevant paragraph,
just before the Section 6.1 header:

   (As stated in Section 4.3.1 of [RFC6325], 1470 bytes was chosen to
   make it extremely unlikely that a TRILL control packet, even with
   reasonable additional headers, tags, and/or encapsulation, would
   encounter MTU problems on an inter-RBridge link.)


> Section 8 - more should be said on whether/when the Authentication
> TLV should be used when ESADI conveys information from an
> authenticated registration. In particular, if this recommendation
> for usage of the Authentication TLV with information from an
> authenticated registration usage is not a "SHOULD" or "MUST", an
> explanation is in order.

Consider the following: we have a network with secure trunk links
between trusted TRILL switches but in some cases those switches are
connected to end stations via 802.11 Wi-Fi links. It seems entirely
reasonable to use 802.11 authentication in allowing end stations to
connect due to the inherent accessiblity of radio links, but might not
be necessary to use authentication on ESADI PDUs between TRILL
switches.

In any case, if there is a concern about forged packets, the IS-IS
LSPs in the TRILL campus should be authenticated and, in that case,
the ESADI PDUs will be authenticated by default as provided in Section
6.3 of this draft.

How about adding a new paragraph to Section 8, between the current
first and second paragraphs, incorporating the above, such as:

   However, there may be cases where it is not necessary to
   authenticate ESADI PDUs despite using authenticated registration
   for end stations.  For example a TRILL campus with secure RBridges
   and inter-RBridge links configured as trunks but some end stations
   connected via 802.11 wireless access links might use 802.11
   authentication for the connection of such end staions but not
   necessarily authenticate ESDAI PDUs. Note that if the IS-IS LSPs in
   a TRILL campus are authenticated, perhaps due to a concern about
   forged packets, the ESADI PDUs will be authenticated by default as
   provided in Section 6.3.


> Nits/editorial comments:
>
> There are lots of acronyms that are not expanded on first use,
> defined in the terminology section, or otherwise explained, e.g.,
> DRB, Sz, CSNP, PSNP. It may be ok to point to terminology/acronym
> definitions in RFC 6325.

I believe these are all defined/expanded in RFC 6325 but it would
still be a good idea to expand them on first use in this document.


> Last sentence on p.8:
>
> OLD
>    The outer VLAN tag will not be present if it was stripped by
>    an Ethernet port out of which the packet was sent.
> NEW
>    The outer VLAN tag will not be present for a packet on an
>    an Ethernet link that does not use VLAN tags.

Well, whether or not any particular Ethernet frame carrying a TRILL
Data packet is VLAN tagged or not depends on whether the port sending
that frame is configured to send it tagged or untagged. There is no
requirement or enforcement mechanism that all the ports on that
Ethernet link be identically configured in this regard. So I do not
consider it to be a property of the link.


Also, Appendix A item 1: replces -> replaces

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
> RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
> this is not a problem.
>
> idnits also warned about possible pre-RFC5378 (2008) content.  This
> is probably not a problem, but please check with your AD.
>
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA  01748
> +1 (508) 293-7953             FAX: +1 (508) 293-7786
> david.black@emc.com        Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From nobody Sat Apr  5 10:25:36 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 077541A0491 for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 10:25:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level: 
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 YqZykCJIyFAs for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 10:25:23 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id A58741A02FC for <ietf@ietf.org>; Sat,  5 Apr 2014 10:25:23 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6A89R7I5C00513E@mauve.mrochek.com> for ietf@ietf.org; Sat, 5 Apr 2014 10:20:18 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6A66V86WW00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 5 Apr 2014 10:20:13 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6A89PP18Q00004W@mauve.mrochek.com>
Date: Sat, 05 Apr 2014 10:19:30 -0700 (PDT)
Subject: Re: Security for various IETF services
In-reply-to: "Your message dated Sat, 05 Apr 2014 08:50:21 +0000" <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com>
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5npq6ciaBRmdjTVC6dwuzyyq34Y
Cc: The IESG <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 17:25:31 -0000

Agreed on all points. This is rapidly turning into the IETF's own version
of "if we can, we must" thinking.

				Ned

> >>
> >> "The IETF are committed to providing secure and privacy
> >> friendly access to information via the web, mail, jabber
> >> and other services.

> Please confirm that "friendly" implies that the user gets to
> choose the degree of security privacy that they consider
> appropriate, and that their applications and devices are not
> encumbered  with the overheads unless they choose to invoke
> the privacy and security mechanisms.
 

> >> While most (but not all) data on IETF
> >> services is public, nonetheless access to that data
> >> should use best practices for security and privacy.

> I agree, but please can you clarify your interpretation
> of "best practise" so that we can understand how
> liberal or prescriptive this is?

> >> However, as there are numerous legacy tools that have been
> >> built that require access via cleartext, the IETF will
> >> continue to allow such access so as not to break such
> >> tooling. New services will however generally only be made
> >> available in ways that use security protocols such as
> >> TLS."
> >>

> That is worrying, because it seems that you are intent on
> encumbering transactions, without requiring a case by
> case study of the threat model, and applying a security
> and privacy model that is appropriate to the specific
> transaction.

> Stewart.


From nobody Sat Apr  5 10:29:50 2014
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29CB1A045A for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 10:29:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level: 
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 nA_Xq6ECm2cX for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 10:29:41 -0700 (PDT)
Received: from mail-ve0-f171.google.com (mail-ve0-f171.google.com [209.85.128.171]) by ietfa.amsl.com (Postfix) with ESMTP id DCD151A0211 for <ietf@ietf.org>; Sat,  5 Apr 2014 10:29:40 -0700 (PDT)
Received: by mail-ve0-f171.google.com with SMTP id jy13so2386703veb.2 for <ietf@ietf.org>; Sat, 05 Apr 2014 10:29:35 -0700 (PDT)
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:from:date :message-id:subject:to:cc:content-type; bh=4i7mNTbc6ovtyGMwOTeZSwfHepNq/qkNh4c4+2FpxNU=; b=c+6oKxatdUngkFhDlYIwk5BpAXErTYHCV/45F00EtarO85sibx6BRnTZFzocCbbdgE GHBbvYdzU2Wi8GdhupWpCPCOyGYR4xZ6X4N0YBUedPvCz1wrmbcQqJmnMMJApuvb3niQ Mp/vTjJpsT3QRYgRhg7NZ/qlR95zEwyCRAauhrJPftApGpGy4JEhe53uR6RJlLu5Hn8E xvR3hVOr3P9yBsnKDd0KRRPNovmhWA4EFp01VcbRxmejx+UXDst7kOmrD1SkuP3FHt1k SdEWt2eC7eSfQuKjOf5UdrtQEGjIWQCejYmrLPPHVv0RnrfayE6goBchtL1nRsXJJIUy yUsw==
X-Gm-Message-State: ALoCoQn4x6SKRwwAxtpPSyZVAATQ0FudtYCH1vQgnngbuEt6XufOMVnFYxXkTkx6tc4ATbr0wVH/
X-Received: by 10.58.38.166 with SMTP id h6mr951151vek.22.1396718975773; Sat, 05 Apr 2014 10:29:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.98.73 with HTTP; Sat, 5 Apr 2014 10:29:15 -0700 (PDT)
X-Originating-IP: [24.84.235.32]
In-Reply-To: <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com>
From: Tim Bray <tbray@textuality.com>
Date: Sat, 5 Apr 2014 10:29:15 -0700
Message-ID: <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com>
Subject: Re: Security for various IETF services
To: "Stewart Bryant (stbryant)" <stbryant@cisco.com>
Content-Type: multipart/alternative; boundary=089e013a0d4067050d04f64efab5
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XImAchpYuGIh-2d8nzU9G1SvdUQ
Cc: The IESG <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 05 Apr 2014 17:29:46 -0000

--089e013a0d4067050d04f64efab5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Sat, Apr 5, 2014 at 1:50 AM, Stewart Bryant (stbryant) <
stbryant@cisco.com> wrote:

> Please confirm that "friendly" implies that the user gets to
> choose the degree of security privacy that they consider
> appropriate, and that their applications and devices are not
> encumbered  with the overheads unless they choose to invoke
> the privacy and security mechanisms.

Here, I think, is a key issue.  I disagree with Stewart.  WHAT?!  How can I
possibly disagree with
=E2=80=8Buser choice?  Because, a huge majority of people

(a) aren=E2=80=99t aware that there is a choice to be made, and shouldn=E2=
=80=99t need to be
(b) do not understand the technical issues surrounding the choice, and
shouldn=E2=80=99t have to
(c) do not understand the legal/policy issues surrounding the choice, and
shouldn=E2=80=99t have to

This includes both the people who use online services and the people who
offer them.  Thus, the only sane ethical position is to operate in a mode
that is private by default, because the consequences of a negative failure
(the user really didn=E2=80=99t need privacy but got it anyhow) are immense=
ly less
damaging than the consequences of a positive failure (the user really
needed privacy but didn=E2=80=99t get it).

=E2=80=8BYes, it is certainly desirable that for those who are in the unusu=
al
position of being confident that they understand the technical and policy
issues, they be given the option of choosing to operate in plain-text
anyone-can-MITM anyone-can-eavesdrop mode.  But saying that the needs of
that very small and specialized group of people should trump the interests
of the vast majority who shouldn=E2=80=99t have to understand or worry abou=
t where
privacy is appropriate and how to provide it; that seems bizarre to me.

So yeah, please turn the IETF=E2=80=99s public-facing offerings over into
private-by-default mode. It=E2=80=99s the only ethical course of action.  -=
T

--089e013a0d4067050d04f64efab5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Apr 5, 2014 at 1:50 AM, Stewart Bryant (stbryant) =
&lt;<a href=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbryant@cisco.=
com</a>&gt; wrote:<br><br><div>&gt; Please confirm that &quot;friendly&quot=
; implies that the user gets to<br>


&gt; choose the degree of security privacy that they consider<br>&gt; appro=
priate, and that their applications and devices are not<br>&gt; encumbered =
=C2=A0with the overheads unless they choose to invoke<br>&gt; the privacy a=
nd security mechanisms.</div>


<div><br></div><div>Here, I think, is a key issue. =C2=A0I disagree with St=
ewart. =C2=A0WHAT?! =C2=A0How can I possibly disagree with=C2=A0<div class=
=3D"gmail_default" style=3D"font-size:small;display:inline">=E2=80=8Buser c=
hoice? =C2=A0Because, a huge majority of people</div>

</div><div><div class=3D"gmail_default" style=3D"font-size:small;display:in=
line"><br></div></div><div><div class=3D"gmail_default" style=3D"font-size:=
small;display:inline">(a) aren=E2=80=99t aware that there is a choice to be=
 made, and shouldn=E2=80=99t need to be</div>

</div><div><div class=3D"gmail_default" style=3D"font-size:small;display:in=
line">(b) do not understand the technical issues surrounding the choice, an=
d shouldn=E2=80=99t have to</div></div><div><div class=3D"gmail_default" st=
yle=3D"font-size:small;display:inline">

(c) do not understand the legal/policy issues surrounding the choice, and s=
houldn=E2=80=99t have to</div></div><div><div class=3D"gmail_default" style=
=3D"font-size:small;display:inline"><br></div></div><div><div class=3D"gmai=
l_default" style=3D"font-size:small;display:inline">

This includes both the people who use online services and the people who of=
fer them. =C2=A0Thus, the only sane ethical position is to operate in a mod=
e that is private by default, because the consequences of a negative failur=
e (the user really didn=E2=80=99t need privacy but got it anyhow) are immen=
sely less damaging than the consequences of a positive failure (the user re=
ally needed privacy but didn=E2=80=99t get it).</div>

</div><div><div class=3D"gmail_default" style=3D"font-size:small;display:in=
line"><br></div></div><div><div class=3D"gmail_default" style=3D"font-size:=
small">=E2=80=8BYes, it is certainly desirable that for those who are in th=
e unusual position of being confident that they understand the technical an=
d policy issues, they be given the option of choosing to operate in plain-t=
ext anyone-can-MITM anyone-can-eavesdrop mode. =C2=A0But saying that the ne=
eds of that very small and specialized group of people should trump the int=
erests of the vast majority who shouldn=E2=80=99t have to understand or wor=
ry about where privacy is appropriate and how to provide it; that seems biz=
arre to me.</div>

<div class=3D"gmail_default" style=3D"font-size:small"><br></div><div class=
=3D"gmail_default" style=3D"font-size:small">So yeah, please turn the IETF=
=E2=80=99s public-facing offerings over into private-by-default mode. It=E2=
=80=99s the only ethical course of action. =C2=A0-T</div>

<div class=3D"gmail_default" style=3D"font-size:small"><br></div></div><div=
><br></div></div>

--089e013a0d4067050d04f64efab5--


From nobody Sat Apr  5 17:41:55 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF57A1A01E8 for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 17:41:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 Xob5z29nHvB3 for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 17:41:50 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) by ietfa.amsl.com (Postfix) with ESMTP id 85E161A01DD for <ietf@ietf.org>; Sat,  5 Apr 2014 17:41:49 -0700 (PDT)
Received: from [85.158.136.51:41391] by server-13.bemta-5.messagelabs.com id CB/31-16341-7C2A0435; Sun, 06 Apr 2014 00:41:43 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-49.messagelabs.com!1396744903!21247004!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28075 invoked from network); 6 Apr 2014 00:41:43 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-4.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 6 Apr 2014 00:41:43 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Sun, 6 Apr 2014 01:41:42 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@qti.qualcomm.com>, <elwynd@dial.pipex.com>, <agmalis@gmail.com>
Date: Sun, 6 Apr 2014 01:41:41 +0100
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Topic: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Index: Ac9PlRli6HVAjPTbShSk3czARFusbABmUumu
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>, <p06240603cf639ebf8c0d@[99.111.97.136]>
In-Reply-To: <p06240603cf639ebf8c0d@[99.111.97.136]>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dJWtDU2y1aZnx5WCaZkEDQvH8sM
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 00:41:54 -0000

Look, if the water is not boiling, it may contain more bacteria,
with adverse effects on health. Boiling water properly
is most likely to kill that bacteria and prevent infection.

Boiling the water is best practice, and you should use that
best practice even though you clearly don't understand why.
Trust us, you'll come to love it. It's for your own good.

This is clearly another security threat to be prevented, and
the IETF's core work and primary focus is on mitigating
security threats that the IETF created in the first place.

Boiling could have been mentioned in the security considerations
section. I see there's no mention of TLS or SHA or authenticating
commands either - so the IETF needs to set up a security group to
fix and properly secure HTCPCP-TEA immediately.
Documenting how everyone must always make tea will also be
a useful outcome of this group.

get to it, Stephen!

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Randall Gellens [randy@qti.=
qualcomm.com]
Sent: 04 April 2014 00:29
To: Elwyn Davies; Andrew G. Malis
Cc: IETF Discussion
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea=
  Efflux Appliances (HTCPCP-TEA)

At 12:37 AM +0100 4/2/14, Elwyn Davies wrote:

>  We also need the internationalized version to cater for all those
>  excellent varieties of China Tea.  A nice drop of pu-erh perhaps?

I stopped reading when I saw that there was no provision for handling
more delicate teas, just as Japanese sencha or gyokuro, which require
significantly cooler water and shorter brewing times.  I'm not sure
I'd characterize this as a question of internationalization, since it
involves fundamental protocol elements and operation rather than user
display text.

--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
The single biggest problem in communication is the illusion that it
has taken place.                                       --G. B. Shaw


From nobody Sat Apr  5 18:27:31 2014
Return-Path: <rgd.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B96341A0286 for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 18:27:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 ID44iMJkkshw for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 18:27:24 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 74CC51A019B for <ietf@ietf.org>; Sat,  5 Apr 2014 18:27:24 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id v10so4950233pde.25 for <ietf@ietf.org>; Sat, 05 Apr 2014 18:27:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:from:subject:date:to; bh=VAK2IGSk/ZSaeZk6Vevll7//h5Bt0FPAdv2C9y+r6ak=; b=XJSHFQsoZplpit/kLnzbCsGSs/55g88eD+4hAjqaV+RZMLqVR4x4W4ULllO5bah3Nm WaQkvsmgVb+qNW+ZR4zoOZ2Owr4O9J7z2OI/IE0Z5EtEe9wtI91emXy77SRuxRfU2aAX +o5ycfK1/JYojGnSufyHgBSpRGMZy7R7v/OBEQTn2AvvDqBdduFvyXoU6eKlP76dKEDc 21aJQ44LA3PXrejc0uJSoQN/J98xCfLMCV4L7C3+8o/cgY3sDp5KUrg75Du4BzMSTmI+ m9XheKNzxma8YVzcmLmDYe4pXfC9+/Mp/WujfvMgFz40eCM23Ht7b4JHbUg2+A6gaJ13 vJ3A==
X-Received: by 10.66.146.229 with SMTP id tf5mr23392328pab.50.1396747639207; Sat, 05 Apr 2014 18:27:19 -0700 (PDT)
Received: from [10.0.1.7] (cpe-142-136-145-221.socal.res.rr.com. [142.136.145.221]) by mx.google.com with ESMTPSA id pl10sm27111168pbb.56.2014.04.05.18.27.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 05 Apr 2014 18:27:16 -0700 (PDT)
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom> <p06240603cf639ebf8c0d@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <6EC1F23D-F2ED-403B-9996-B897CC9CE5A1@gmail.com>
X-Mailer: iPad Mail (11B651)
From: "Rgd.ietf" <rgd.ietf@gmail.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Date: Sat, 5 Apr 2014 18:27:15 -0700
To: "<l.wood@surrey.ac.uk>" <l.wood@surrey.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OV5Bces8PXZ77i_BbnvwMVRkJ0Y
Cc: "<randy@qti.qualcomm.com>" <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 01:27:29 -0000

Bacterial issues almost seems like policy.  Many users may desire bacterial e=
nriched tea, the protocol should not enforce local policy, though it can pre=
sent interfaces for policy application.


> On Apr 5, 2014, at 5:41 PM, <l.wood@surrey.ac.uk> wrote:
>=20
> Look, if the water is not boiling, it may contain more bacteria,
> with adverse effects on health. Boiling water properly
> is most likely to kill that bacteria and prevent infection.
>=20
> Boiling the water is best practice, and you should use that
> best practice even though you clearly don't understand why.
> Trust us, you'll come to love it. It's for your own good.
>=20
> This is clearly another security threat to be prevented, and
> the IETF's core work and primary focus is on mitigating
> security threats that the IETF created in the first place.
>=20
> Boiling could have been mentioned in the security considerations
> section. I see there's no mention of TLS or SHA or authenticating
> commands either - so the IETF needs to set up a security group to
> fix and properly secure HTCPCP-TEA immediately.
> Documenting how everyone must always make tea will also be
> a useful outcome of this group.
>=20
> get to it, Stephen!
>=20
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Randall Gellens [randy@qti=
.qualcomm.com]
> Sent: 04 April 2014 00:29
> To: Elwyn Davies; Andrew G. Malis
> Cc: IETF Discussion
> Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Te=
a  Efflux Appliances (HTCPCP-TEA)
>=20
> At 12:37 AM +0100 4/2/14, Elwyn Davies wrote:
>=20
>> We also need the internationalized version to cater for all those
>> excellent varieties of China Tea.  A nice drop of pu-erh perhaps?
>=20
> I stopped reading when I saw that there was no provision for handling
> more delicate teas, just as Japanese sencha or gyokuro, which require
> significantly cooler water and shorter brewing times.  I'm not sure
> I'd characterize this as a question of internationalization, since it
> involves fundamental protocol elements and operation rather than user
> display text.
>=20
> --
> Randall Gellens
> Opinions are personal;    facts are suspect;    I speak for myself only
> -------------- Randomly selected tag: ---------------
> The single biggest problem in communication is the illusion that it
> has taken place.                                       --G. B. Shaw
>=20


From nobody Sat Apr  5 18:56:16 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 667011A030F for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 18:56:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 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_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 oW8jfcTGqOiN for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 18:56:11 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 48ACF1A0238 for <ietf@ietf.org>; Sat,  5 Apr 2014 18:56:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1396749366; x=1428285366; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=IQdbHrDiRtczM4SHmf/8p84BUDhfgGiGVuZj64VsBLs=; b=Y3ycfCPMJilogKfwHh1scLj7exjx0ckulkA5WsXFKqzu8ICwRKWY6sku ThhWvR2DFxOEwzZeQ6V5+zVhraJYhUSKxEewf2mL/I0Rup9X9cyUVWUz3 lqUZ83ysWCSIcUdgpBUe841llNQiWu0A9SkZdYDXKxSgowTHRB5j5Ra6V o=;
X-IronPort-AV: E=McAfee;i="5400,1158,7399"; a="117973011"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 05 Apr 2014 18:56:06 -0700
X-IronPort-AV: E=Sophos;i="4.97,802,1389772800"; d="scan'208";a="657405809"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 05 Apr 2014 18:56:05 -0700
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 5 Apr 2014 18:56:04 -0700
Message-ID: <p06240601cf6663952ae4@[99.111.97.136]>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>,<p06240603cf639ebf8c0d@[99.11 1.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>
X-Mailer: Eudora for Mac OS X
Date: Sat, 5 Apr 2014 18:55:40 -0700
To: <l.wood@surrey.ac.uk>, <randy@qti.qualcomm.com>, <elwynd@dial.pipex.com>,  <agmalis@gmail.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea   Efflux Appliances (HTCPCP-TEA)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zxGRmrI7ghBDRDbrMRes3M0kgmk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 01:56:15 -0000

At 1:41 AM +0100 4/6/14, <l.wood@surrey.ac.uk> wrote:

>  Look, if the water is not boiling, it may contain more bacteria,
>  with adverse effects on health. Boiling water properly
>  is most likely to kill that bacteria and prevent infection.

Only if the source of water is not clean.

>  Boiling the water is best practice, and you should use that
>  best practice even though you clearly don't understand why.
>  Trust us, you'll come to love it. It's for your own good.

Even if the water is first boiled, it can be cooled (or allowed to 
cool) to the desired temperature for the specific tea being steeped 
(e.g., a selected value most often between 140F and 208F (60C to 98C).

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
If the odds are a million to one against something occurring, chances
are 50-50 it will.


From nobody Sat Apr  5 19:09:01 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7D41A0238 for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 19:08:59 -0700 (PDT)
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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 hziV72QD3EsU for <ietf@ietfa.amsl.com>; Sat,  5 Apr 2014 19:08:55 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.119]) by ietfa.amsl.com (Postfix) with ESMTP id 89BAC1A0197 for <ietf@ietf.org>; Sat,  5 Apr 2014 19:08:54 -0700 (PDT)
Received: from [193.109.255.147:3241] by server-15.bemta-14.messagelabs.com id F5/43-15813-137B0435; Sun, 06 Apr 2014 02:08:49 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-72.messagelabs.com!1396750128!11532864!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24643 invoked from network); 6 Apr 2014 02:08:48 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-10.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 6 Apr 2014 02:08:48 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Sun, 6 Apr 2014 03:08:48 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@qti.qualcomm.com>, <elwynd@dial.pipex.com>, <agmalis@gmail.com>
Date: Sun, 6 Apr 2014 03:05:09 +0100
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Topic: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Index: Ac9RO2FrPsGgb3KjR5iLcbKJw+nIdQAAUHAs
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>,<p06240603cf639ebf8c0d@[99.11 1.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>, <p06240601cf6663952ae4@[99.111.97.136]>
In-Reply-To: <p06240601cf6663952ae4@[99.111.97.136]>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/d0YscuSgZmfm4HFdpWdmWi-z3bo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 02:08:59 -0000

Assuming the water is clean is like assuming
there are no secuity attackers. That's obviously
untenable in this day and age.

Best-practice hygiene is best-practice security.

Always boil the water first. This is in line
with best security practice, which attempts
to boil the ocean.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Randall Gellens [randy@qti.qualcomm.com]
Sent: 06 April 2014 02:55
To: Wood L  Dr (Electronic Eng); randy@qti.qualcomm.com; elwynd@dial.pipex.=
com; agmalis@gmail.com
Cc: ietf@ietf.org
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea=
   Efflux Appliances (HTCPCP-TEA)

At 1:41 AM +0100 4/6/14, <l.wood@surrey.ac.uk> wrote:

>  Look, if the water is not boiling, it may contain more bacteria,
>  with adverse effects on health. Boiling water properly
>  is most likely to kill that bacteria and prevent infection.

Only if the source of water is not clean.

>  Boiling the water is best practice, and you should use that
>  best practice even though you clearly don't understand why.
>  Trust us, you'll come to love it. It's for your own good.

Even if the water is first boiled, it can be cooled (or allowed to
cool) to the desired temperature for the specific tea being steeped
(e.g., a selected value most often between 140F and 208F (60C to 98C).

--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
If the odds are a million to one against something occurring, chances
are 50-50 it will.


From nobody Sun Apr  6 04:42:03 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2FB21A03D4 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 04:42:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 RmdD_P4RGece for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 04:41:57 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id DC7BF1A03D1 for <ietf@ietf.org>; Sun,  6 Apr 2014 04:41:57 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id AB60E1B80C2 for <ietf@ietf.org>; Sun,  6 Apr 2014 04:41:52 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 8CE9D190043; Sun,  6 Apr 2014 04:41:52 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 6 Apr 2014 04:41:52 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>
Date: Sun, 6 Apr 2014 07:41:51 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <594D5B3E-F70B-4C21-96D0-9C414D915341@nominum.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>, <p06240603cf639ebf8c0d@[99.11 1.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>, <p06240601cf6663952ae4@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>
To: <l.wood@surrey.ac.uk>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/57BQ1ugXhuwuRajnDJqO6jATW0A
Cc: randy@qti.qualcomm.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 11:42:02 -0000

On Apr 5, 2014, at 10:05 PM, <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk> =
wrote:
> Always boil the water first. This is in line
> with best security practice, which attempts
> to boil the ocean.

Again with the salt water tea!


From nobody Sun Apr  6 05:05:48 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 529791A03EC for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 05:05:47 -0700 (PDT)
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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 pSsoHnnbcUs3 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 05:05:42 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.107]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3341A03E8 for <ietf@ietf.org>; Sun,  6 Apr 2014 05:05:41 -0700 (PDT)
Received: from [193.109.255.147:24739] by server-3.bemta-14.messagelabs.com id 9A/66-22179-01341435; Sun, 06 Apr 2014 12:05:36 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-7.tower-72.messagelabs.com!1396785935!2499761!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 32211 invoked from network); 6 Apr 2014 12:05:35 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-7.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 6 Apr 2014 12:05:35 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Sun, 6 Apr 2014 13:05:35 +0100
From: <l.wood@surrey.ac.uk>
To: <ted.lemon@nominum.com>
Date: Sun, 6 Apr 2014 13:04:27 +0100
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Topic: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Index: Ac9RjTae6CMIdDKnRaqb0tvXbpxM1QAAyVs1
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEC2@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>,<p06240603cf639ebf8c0d@[99.11 1.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>, <p06240601cf6663952ae4@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>, <594D5B3E-F70B-4C21-96D0-9C414D915341@nominum.com>
In-Reply-To: <594D5B3E-F70B-4C21-96D0-9C414D915341@nominum.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3LmoLtgyT6a5_qzPkrAVPDjBw-E
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 12:05:47 -0000

Again with promoting the Lemon detox?

https://www.lemondetox.com.au/lemon-detox-diet-laxative-tea-and-sea-salt.ph=
p

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Ted Lemon [ted.lemon@nominum.com]
Sent: 06 April 2014 12:41
To: Wood L  Dr (Electronic Eng)
Cc: randy@qti.qualcomm.com; elwynd@dial.pipex.com; agmalis@gmail.com; ietf@=
ietf.org
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea=
 Efflux Appliances (HTCPCP-TEA)

On Apr 5, 2014, at 10:05 PM, <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk> wr=
ote:
> Always boil the water first. This is in line
> with best security practice, which attempts
> to boil the ocean.

Again with the salt water tea!


From nobody Sun Apr  6 06:17:55 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1B601A0429; Sun,  6 Apr 2014 06:17:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=unavailable
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 MZAFU3tzF4Vi; Sun,  6 Apr 2014 06:17:43 -0700 (PDT)
Received: from mail-yk0-x22f.google.com (mail-yk0-x22f.google.com [IPv6:2607:f8b0:4002:c07::22f]) by ietfa.amsl.com (Postfix) with ESMTP id B40D91A0421; Sun,  6 Apr 2014 06:17:43 -0700 (PDT)
Received: by mail-yk0-f175.google.com with SMTP id 131so4580555ykp.20 for <multiple recipients>; Sun, 06 Apr 2014 06:17:38 -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:content-type; bh=FRb2shnQLEW3qQNc7msR2X/fqsnT8QxX8Zg+BnQz6/4=; b=CGfwncS9HQ0+iZuHYc1VV8qXOV2weQ7EnU2gOszHcktzjDFCYX96Q+fuD11lBrS+Wt EwBfWEV/9bwD2sFmCLT53jg3ooOLhBbzR6Qq8/t6AADXV62Naoyd6YspIQlF0zC3/lD/ dUkfrD05qa9Hn8rTkfTi0YndoQYJm4a57QdkI1Q8ngWOoySVjf8u/W0GsA5uX+jLymMl 24pwskNFlsLK7tHSh/X7At4g+bXurHORcU1H0cOj6ymvYxE27XaYSk6Os4DHPLaMLk4A pd+DWZmKO7n3AojfJdGAZY3YdsGyMSCIEpK4RJ3N/4mfC17rfoHPzFfC33eQu+D4cYQl jLyw==
MIME-Version: 1.0
X-Received: by 10.236.101.198 with SMTP id b46mr35826829yhg.68.1396790258394;  Sun, 06 Apr 2014 06:17:38 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Sun, 6 Apr 2014 06:17:38 -0700 (PDT)
In-Reply-To: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
Date: Sun, 6 Apr 2014 15:17:38 +0200
Message-ID: <CADnDZ8-tg52c9FDZgHxgpSJjqPQvqAOg1hSR8usoRx-739msrA@mail.gmail.com>
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/h5U-w2Sdnim4w2sb4JsgV5jWXJ8
Cc: iaoc@ietf.org, iab@iab.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 13:17:49 -0000

Hi Ray,

my questions below,

On 4/4/14, IETF Administrative Director <iad@ietf.org> wrote:
> All;
>
> The Trustees of the IETF Trust have voted an intent to renounce (abandon)
> the "IETF Secretariat"
> trademark, but before taking any action they desire to hear from the
> community.

What is this hearing status like? is it like if the community reply
was: *no* don't do that, then they as trustees will change their mind,
or is it, just hearing. I am not sure if my input has any value in
this community request.

If IETF is not active in using its trademarks in business, then why
the trustees don't think in different directions. Was IETF trademarks
used in US and Europe and the result was not good, we need information
to know what is happening?

My thoughts is that we may get benefits from IETF trademarks in
future, so if the trustees decide now to leave it, could they
establish it any time by thoes governments registrations? I am not a
legal expert person but for international organisation like IETF is it
possible to get registrations at UN or any other authority that may
make discounts?

Thanks

AB


From nobody Sun Apr  6 08:52:33 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 134511A0471 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 08:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 P8MvNkdGBNJ5 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 08:52:27 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 8C6291A0473 for <ietf@ietf.org>; Sun,  6 Apr 2014 08:52:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F356CBE4D for <ietf@ietf.org>; Sun,  6 Apr 2014 16:52:20 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZuEM2pp-f88H for <ietf@ietf.org>; Sun,  6 Apr 2014 16:52:19 +0100 (IST)
Received: from [10.87.48.12] (unknown [86.44.74.117]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 21B26BE4C for <ietf@ietf.org>; Sun,  6 Apr 2014 16:52:19 +0100 (IST)
Message-ID: <53417832.90405@cs.tcd.ie>
Date: Sun, 06 Apr 2014 16:52:18 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie>
In-Reply-To: <533D8A90.60309@cs.tcd.ie>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/x-_8XVyIR1SlMgQbJDtKsxqyPCQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 15:52:32 -0000

As others have said, I think the questions posed have been
answered pretty much. I also got some good offlist wording
suggestions, the result of which is:

   "The IETF is committed to providing secure and private
   access to information via the web, mail, jabber and
   other services. While most data on IETF services is
   public, individual accesses to that data should be
   kept private to the extent possible.  However, as
   there are numerous existing tools that have been built
   that require access via cleartext, the IETF will
   continue to allow such access so as not to break such
   tooling. New services will however generally only be
   made available in ways that use security protocols
   such as TLS."

And just adding some stuff that's not been said before...

I agree that IETF services aren't the most sensitive in the
world, but think we all nonetheless win if we up the ante for
attackers of whatever kind when we reasonably can.

There is a value in not making cleartext versions of services
available though - I've personally seen a number of cases where
http:// URLs were sent via mail with instructions to login at
that URL using e.g. a datatracker or tools login. Yes, that ought
not happen (https:// URLs should be sent), but it does happen
and will so long as the http:// URLs work, and it'd be naive of
us to assume that everyone sending out such mails would be aware
that doing so isn't a good plan.

Using e.g. TLS for confidentiality also helps counter attacks
where cleartext HTTP cookies etc. are being used for monitoring
which has been shown to be the case. [1] IMO that's already a
good enough reason to turn on TLS or equivalent as much as
possible since most services will expose some similar
fingerprint when run in clear.

For those who expressed a wish for data origin authentication
over and above TLS server auth, that is already in place for
I-Ds. [2]

A couple of people expressed concern that this was a bit of a
"blanket statement," while that is true, the statement is not
absolutist, e.g. it says "generally" in the last sentence
which I think is about right.

A number of people made mechanism-specific points which were
mostly reasonable but of course we shouldn't put those in
this proposed iesg statement. One person said that e.g. this
statement should not be used to require client authentication
which is of course correct.

Someone mentioned having an IETF privacy policy for services
which sounds like a fine thing to me, and which is something
that I think Alissa has done a bit of work on in the past and
the IESG has chatted about resurrecting that. That is trickier
to get right though, and more work to get agreed, so not sure
if it'll happen.

Lastly, I'm heartbroken that Lloyd has sussed out my formerly
secret plan to try to take over the world;-) Ah well, I'll
just have to try again tomorrow.

S.

[1] http://www.bbc.co.uk/news/technology-25333663
[2] https://www.ietf.org/id-info/idsignatures.html


On 04/03/2014 05:21 PM, Stephen Farrell wrote:
> 
> Hi all,
> 
>>From time to time the issue of how to secure IETF services
> comes up e.g. whether to turn on TLS for some IETF web server
> or jabber or mail etc.
> 
> The most recent such was a request to turn on HSTS [1] for
> the IETF web site, which I don't think we can do without
> breaking old tools etc. Nonetheless we would like to turn
> on things like TLS more often going forward as seemed to
> me to be the outcome of a long thread on here late last
> year.
> 
> So, the IESG are considering the following as an IESG
> statement to offer some guidance about this:
> 
> "The IETF are committed to providing secure and privacy
> friendly access to information via the web, mail, jabber
> and other services. While most (but not all) data on IETF
> services is public, nonetheless access to that data
> should use best practices for security and privacy.
> However, as there are numerous legacy tools that have been
> built that require access via cleartext, the IETF will
> continue to allow such access so as not to break such
> tooling. New services will however generally only be made
> available in ways that use security protocols such as
> TLS."
> 
> If you have wordsmithing changes to suggest please just send
> those to me or the iesg. More substantive comments should go
> here I guess. I hope the only bit worth discussing (except
> for the few folks who would rather we do none of this;-)
> might be the last sentence.
> 
> A few weeks after any discussion here dies down I'll put the
> resulting text on an IESG telechat for approval if that seems
> like the right thing to do.
> 
> Thanks,
> S
> 
> [1] https://tools.ietf.org/html/rfc6797
> 
> 
> 
> 


From nobody Sun Apr  6 12:28:45 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B86731A0283 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 12:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 6GCq9HRD0M6J for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 12:28:39 -0700 (PDT)
Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 2C02A1A026E for <ietf@ietf.org>; Sun,  6 Apr 2014 12:28:39 -0700 (PDT)
Received: by mail-yh0-f48.google.com with SMTP id z6so5023113yhz.7 for <ietf@ietf.org>; Sun, 06 Apr 2014 12:28:33 -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:from:date:message-id :subject:to:cc:content-type; bh=XFExA2q8Px6NjDhx6WFk6DB3cxcOAJPpu+QSQ1WMOxo=; b=oCqjJ1c/YGoNUuEjQFNBq7dAk/FQGVBjOzz61yKX7JsfXt0uIGAnBgZdEIbKsLNEYB K2xTC0cNGFDoJBIXpwp3E8PkSL5Rdd39EvCXKZJIPCHBMrr8/b4xgyt9LD7eyvgfWOCK E6sl7sSyD/lmtegaucBtkzu8z0ihWAv6YuKsnO9XszJqchoeYxhP9mxrkfEMUiupnYLV mOrQBrwPfBMCKB1081x9a3xBWKfSojru5Z9RU3D+FPIOopBIUAsS72jFcOO/dpAhJBat bksSNeq5BGvhZuaC0ZxB9oIfEbXg+aT5bMyPVIfXr82VyJczMbaz4G/y4P1Lh5nMvP08 6SDw==
X-Received: by 10.236.2.37 with SMTP id 25mr3924969yhe.123.1396812513675; Sun, 06 Apr 2014 12:28:33 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Sun, 6 Apr 2014 12:27:52 -0700 (PDT)
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEBF@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net> <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com> <53400355.7030807@isdg.net> <290E20B455C66743BE178C5C84F1240847E779EEBF@EXMB01CMS.surrey.ac.uk>
From: Dick Franks <rwfranks@acm.org>
Date: Sun, 6 Apr 2014 20:27:52 +0100
X-Google-Sender-Auth: xI7MLIQBlzfh708P9bfWXQwHLTY
Message-ID: <CAKW6Ri6jD4=pMdE_nsSnqyg6sKDT29_69_9jf=vfT2z6au7hNQ@mail.gmail.com>
Subject: Re: Security for various IETF services
To: l.wood@surrey.ac.uk
Content-Type: multipart/alternative; boundary=089e0112c5e6b2119c04f664c117
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AM9RStYjtwWQmyweGiQqv-MxJp4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 19:28:44 -0000

--089e0112c5e6b2119c04f664c117
Content-Type: text/plain; charset=UTF-8

On 5 April 2014 14:40, <l.wood@surrey.ac.uk> wrote:

> "I didn't see anything that stood out. Are you referring to his why
> question?  Really?  It seems others answered why."
>
> they did not.
>
> Other noises off-stage are rrelevant

The author(s) of the proposal MUST provide the threat model for each
service and a reasoned argument why the proposed action mitigates the
identified threat or threats.

Engineering best practice demands no less.

Transparent decision process demands no less.

Ignoring Lloyd Wood's question is not an option.


Dick Franks

--089e0112c5e6b2119c04f664c117
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On 5 April 2014 14:40,  <span dir=3D"ltr">&lt;<a href=3D"mailto:l.wood@surr=
ey.ac.uk" target=3D"_blank">l.wood@surrey.ac.uk</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">

<div class=3D"">&quot;I didn&#39;t see anything that stood out. Are you ref=
erring to his why<br>
question? =C2=A0Really? =C2=A0It seems others answered why.&quot;<br>
<br>
</div>they did not.<br>
<br></blockquote><div>Other noises off-stage are rrelevant<br></div><br></d=
iv><div class=3D"gmail_quote">The author(s) of the proposal MUST provide th=
e threat model for each service and a reasoned argument why the proposed ac=
tion mitigates the identified threat or threats.<br>

<br></div><div class=3D"gmail_quote">Engineering best practice demands no l=
ess.<br><br></div><div class=3D"gmail_quote">Transparent decision process d=
emands no less.<br><br></div><div class=3D"gmail_quote">Ignoring Lloyd Wood=
&#39;s question is not an option.<br>

<br><br></div><div class=3D"gmail_quote">Dick Franks<br></div><br></div></d=
iv>

--089e0112c5e6b2119c04f664c117--


From nobody Sun Apr  6 15:12:03 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B5F01A01BD for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 15:12:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 zx6fZ_GSYAvx for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 15:11:55 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id C11E11A0502 for <ietf@ietf.org>; Sun,  6 Apr 2014 15:11:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CA126BE24; Sun,  6 Apr 2014 23:11:48 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtVyecNMcytd; Sun,  6 Apr 2014 23:11:46 +0100 (IST)
Received: from [10.87.48.12] (unknown [86.44.74.117]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 84617BE20; Sun,  6 Apr 2014 23:11:46 +0100 (IST)
Message-ID: <5341D122.6010002@cs.tcd.ie>
Date: Sun, 06 Apr 2014 23:11:46 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Dick Franks <rwfranks@acm.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net> <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com> <53400355.7030807@isdg.net> <290E20B455C66743BE178C5C84F1240847E779EEBF@EXMB01CMS.surrey.ac.uk> <CAKW6Ri6jD4=pMdE_nsSnqyg6sKDT29_69_9jf=vfT2z6au7hNQ@mail.gmail.com>
In-Reply-To: <CAKW6Ri6jD4=pMdE_nsSnqyg6sKDT29_69_9jf=vfT2z6au7hNQ@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EUpD-taemDYHmLIunmDAfhqQms4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 22:12:00 -0000

On 04/06/2014 08:27 PM, Dick Franks wrote:
> On 5 April 2014 14:40, <l.wood@surrey.ac.uk> wrote:
> 
>> "I didn't see anything that stood out. Are you referring to his why
>> question?  Really?  It seems others answered why."
>>
>> they did not.
>>
>> Other noises off-stage are rrelevant
> 
> The author(s) of the proposal MUST provide the threat model for each
> service and a reasoned argument why the proposed action mitigates the
> identified threat or threats.
> 
> Engineering best practice demands no less.

I disagree. Asking for a threat model seems odd, since the
proposed IESG statement isn't specific to a particular service
and absent that you can't sensibly construct a threat model I
think.

> Transparent decision process demands no less.

I have no idea what's apparently opaque.

> Ignoring Lloyd Wood's question is not an option.

LLoyd's questions were answered IMO.

S..



> 
> 
> Dick Franks
> 


From nobody Sun Apr  6 15:50:37 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F28D91A032F for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 15:50:34 -0700 (PDT)
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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 LQAjg9oOj-ft for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 15:50:31 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.115]) by ietfa.amsl.com (Postfix) with ESMTP id A2F531A02F0 for <ietf@ietf.org>; Sun,  6 Apr 2014 15:50:30 -0700 (PDT)
Received: from [193.109.255.147:40675] by server-11.bemta-14.messagelabs.com id 83/B2-09902-03AD1435; Sun, 06 Apr 2014 22:50:24 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-72.messagelabs.com!1396824624!10451848!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9495 invoked from network); 6 Apr 2014 22:50:24 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-11.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 6 Apr 2014 22:50:24 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Sun, 6 Apr 2014 23:50:23 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <rwfranks@acm.org>
Date: Sun, 6 Apr 2014 23:49:59 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9R5VFfQ9yrlLCtQ66a/yfO4AYUnAABTiWQ
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEC3@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net> <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com> <53400355.7030807@isdg.net> <290E20B455C66743BE178C5C84F1240847E779EEBF@EXMB01CMS.surrey.ac.uk> <CAKW6Ri6jD4=pMdE_nsSnqyg6sKDT29_69_9jf=vfT2z6au7hNQ@mail.gmail.com>, <5341D122.6010002@cs.tcd.ie>
In-Reply-To: <5341D122.6010002@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/U0RWQ-7EoYSBlh4zBSzuA-ncQiU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 22:50:35 -0000

> LLoyd's questions were answered IMO.

they weren't.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stephen Farrell [stephen.fa=
rrell@cs.tcd.ie]
Sent: 06 April 2014 23:11
To: Dick Franks
Cc: IETF Discussion
Subject: Re: Security for various IETF services

On 04/06/2014 08:27 PM, Dick Franks wrote:
> On 5 April 2014 14:40, <l.wood@surrey.ac.uk> wrote:
>
>> "I didn't see anything that stood out. Are you referring to his why
>> question?  Really?  It seems others answered why."
>>
>> they did not.
>>
>> Other noises off-stage are rrelevant
>
> The author(s) of the proposal MUST provide the threat model for each
> service and a reasoned argument why the proposed action mitigates the
> identified threat or threats.
>
> Engineering best practice demands no less.

I disagree. Asking for a threat model seems odd, since the
proposed IESG statement isn't specific to a particular service
and absent that you can't sensibly construct a threat model I
think.

> Transparent decision process demands no less.

I have no idea what's apparently opaque.

> Ignoring Lloyd Wood's question is not an option.

LLoyd's questions were answered IMO.

S..



>
>
> Dick Franks
>


From nobody Sun Apr  6 16:08:20 2014
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DBC81A0515 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 16:08:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.546
X-Spam-Level: 
X-Spam-Status: No, score=-0.546 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, MISSING_HEADERS=1.021, SPF_PASS=-0.001] autolearn=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 em0DZ6xr3F-v for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 16:08:12 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 46FC71A0503 for <ietf@ietf.org>; Sun,  6 Apr 2014 16:08:12 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-186.snva.ca.megapath.net [68.164.244.186]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 391253F9DE for <ietf@ietf.org>; Sun,  6 Apr 2014 23:07:17 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id s36N868M024562 for <ietf@ietf.org>; Sun, 6 Apr 2014 16:08:06 -0700
Date: Sun, 6 Apr 2014 16:08:06 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
In-Reply-To: <53417832.90405@cs.tcd.ie>
Message-ID: <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com>
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jC-0U5ynKGLfpkJDR47gPNysNMU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 23:08:17 -0000

On Sun, 6 Apr 2014, Stephen Farrell wrote:

> ...
> There is a value in not making cleartext versions of services
> available though - I've personally seen a number of cases where
> http:// URLs were sent via mail with instructions to login at
> that URL using e.g. a datatracker or tools login. Yes, that ought
> not happen (https:// URLs should be sent), but it does happen
> and will so long as the http:// URLs work, and it'd be naive of
> us to assume that everyone sending out such mails would be aware
> that doing so isn't a good plan.

Um, it is not difficult to protect the login credentials will leaving
the remainder of the interaction in the clear. Then it won't matter
what is the the email.

I don't object to making TLS/et al access available when it can be
done at a moderate cost. But that is different than the implied
statement that the intent is to require TLS for future service
access.

I agree with those who've said a threat analysis is needed before
deciding access is limited to TLS or other secure alternative.


From nobody Sun Apr  6 16:30:28 2014
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB0871A01C7 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 16:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 83hZa0rZRJBf for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 16:30:20 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0240.outbound.protection.outlook.com [207.46.163.240]) by ietfa.amsl.com (Postfix) with ESMTP id 9025B1A0584 for <ietf@ietf.org>; Sun,  6 Apr 2014 16:30:19 -0700 (PDT)
Received: from BLUPR03MB424.namprd03.prod.outlook.com (10.141.78.152) by BLUPR03MB423.namprd03.prod.outlook.com (10.141.78.150) with Microsoft SMTP Server (TLS) id 15.0.908.10; Sun, 6 Apr 2014 23:30:12 +0000
Received: from BLUPR03MB424.namprd03.prod.outlook.com ([10.141.78.152]) by BLUPR03MB424.namprd03.prod.outlook.com ([10.141.78.152]) with mapi id 15.00.0908.008; Sun, 6 Apr 2014 23:30:12 +0000
From: Christian Huitema <huitema@microsoft.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPT1jcTXDUfJOah0OH2ltCrxPwgZsEwa4AgAB5wwCAAATOIA==
Date: Sun, 6 Apr 2014 23:30:11 +0000
Message-ID: <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com>
In-Reply-To: <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [24.16.156.113]
x-forefront-prvs: 0173C6D4D5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(199002)(189002)(50986001)(94316002)(95666003)(86362001)(49866001)(87936001)(97186001)(69226001)(80976001)(76786001)(87266001)(31966008)(83072002)(92566001)(56816005)(47976001)(2656002)(85852003)(74662001)(97336001)(47446002)(53806001)(74316001)(74876001)(95416001)(76482001)(74502001)(90146001)(94946001)(47736001)(93516002)(46102001)(85306002)(93136001)(54356001)(63696002)(33646001)(81542001)(66066001)(54316002)(76576001)(81342001)(81816001)(74366001)(76796001)(98676001)(59766001)(4396001)(65816001)(81686001)(80022001)(83322001)(20776003)(56776001)(77982001)(99396002)(79102001)(74706001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB423; H:BLUPR03MB424.namprd03.prod.outlook.com; FPR:605BF61F.1D14F4E9.6DE013B8.C4E9A1CC.20133; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
received-spf: None (: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AuRGN_6eV7T4xP2Tnv-E9DB4Dhw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Apr 2014 23:30:26 -0000

> I agree with those who've said a threat analysis is needed before
> deciding access is limited to TLS or other secure alternative.

But we have that threat analysis, and the recommended mitigation is precise=
ly "encrypt everything." The "pervasive monitoring" threat is analyzed by a=
 number of perpass drafts, and Stephen has merely followed the conclusions =
of that analysis. There is no need to repeat that analysis for each and eve=
ry tool that the IETF produces, and there is indeed a need for the IETF as =
a whole to "lead by example."

-- Christian Huitema




From nobody Sun Apr  6 17:37:29 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10FE61A0552 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 17:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 bLyxhzXm3GOU for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 17:37:22 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9F43D1A00EC for <ietf@ietf.org>; Sun,  6 Apr 2014 17:37:22 -0700 (PDT)
Received: from [85.158.137.99:24174] by server-12.bemta-3.messagelabs.com id 06/77-14831-C33F1435; Mon, 07 Apr 2014 00:37:16 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-217.messagelabs.com!1396831035!17158276!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10864 invoked from network); 7 Apr 2014 00:37:16 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-15.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 7 Apr 2014 00:37:16 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Mon, 7 Apr 2014 01:37:15 +0100
From: <l.wood@surrey.ac.uk>
To: <huitema@microsoft.com>, <ietf@ietf.org>
Date: Mon, 7 Apr 2014 01:35:38 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPT1jcTXDUfJOah0OH2ltCrxPwgZsEwa4AgAB5wwCAAATOIIAAE6e/
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEC5@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com>, <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
In-Reply-To: <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/j1spyzigSGBoBzyfnP_cePwPmVA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 00:37:27 -0000

https://datatracker.ietf.org/wg/perpass/
that's a lot of drafts.

and yet perpass is still not a WG with formal process and charter? Odd, tha=
t.

Knee-jerk reactions are not good things.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Christian Huitema [huitema@=
microsoft.com]
Sent: 07 April 2014 00:30
To: ietf@ietf.org
Subject: RE: Security for various IETF services

> I agree with those who've said a threat analysis is needed before
> deciding access is limited to TLS or other secure alternative.

But we have that threat analysis, and the recommended mitigation is precise=
ly "encrypt everything." The "pervasive monitoring" threat is analyzed by a=
 number of perpass drafts, and Stephen has merely followed the conclusions =
of that analysis. There is no need to repeat that analysis for each and eve=
ry tool that the IETF produces, and there is indeed a need for the IETF as =
a whole to "lead by example."

-- Christian Huitema




From nobody Sun Apr  6 17:40:31 2014
Return-Path: <serrhini@mail.ru>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDB4F1A055D for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 17:40:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.15
X-Spam-Level: ***
X-Spam-Status: No, score=3.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 6XLyW7LNTPlD for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 17:40:23 -0700 (PDT)
Received: from f126.i.mail.ru (f126.i.mail.ru [94.100.178.189]) by ietfa.amsl.com (Postfix) with ESMTP id 63C671A018D for <ietf@ietf.org>; Sun,  6 Apr 2014 17:40:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2;  h=References:In-Reply-To:Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:Cc:To:From; bh=ZpbII0lto0BW4R7hUj/d/x53PGnyxYiJESRjCDAisc0=;  b=Ax6VJNTuW4Q4sULhRKecY+Vd5ufOF7jgcYUgqKteC4qXUiz+yt22MsrBuCH/wWz/WXuVX655+kCAQRpHAXqzrwlwVv9sCaO391X2673hhQ49ECV+F4dhS6edlQlSokDUBnQl44WVZH8za8ErMOWz1zows6Pa9xC45K+UQ9T5zXM=;
Received: from mail by f126.i.mail.ru with local (envelope-from <serrhini@mail.ru>) id 1WWxbj-000688-E6; Mon, 07 Apr 2014 04:40:15 +0400
Received: from [41.137.68.112] by e.mail.ru with HTTP; Mon, 07 Apr 2014 04:40:15 +0400
From: =?UTF-8?B?bW9oYW1tZWQgc2Vycmhpbmk=?= <serrhini@mail.ru>
To: =?UTF-8?B?Q2hyaXN0aWFuIEh1aXRlbWE=?= <huitema@microsoft.com>
Subject: =?UTF-8?B?UmVbMl06IFNlY3VyaXR5IGZvciB2YXJpb3VzIElFVEYgc2VydmljZXM=?=
Mime-Version: 1.0
X-Mailer: Mail.Ru Mailer 1.0
X-Originating-IP: [41.137.68.112]
Date: Mon, 07 Apr 2014 04:40:15 +0400
X-Priority: 3 (Normal)
Message-ID: <1396831215.88792064@f126.i.mail.ru>
Content-Type: multipart/alternative; boundary="--ALT--2TPB6QXn1396831215"
X-Mras: Ok
X-Spam: undefined
In-Reply-To: <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
References: <533D8A90.60309@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com> <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7wEUuxFzNkL6LVrQBAuWcYMXEKw
Cc: =?UTF-8?B?aWV0ZkBpZXRmLm9yZw==?= <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: =?UTF-8?B?bW9oYW1tZWQgc2Vycmhpbmk=?= <serrhini@mail.ru>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 00:40:28 -0000

----ALT--2TPB6QXn1396831215
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

CkkgYWdyZWUsIFRoZSBTZWN1cml0eSBhbmQgUmlzayBBbmFseXNpc8KgIGlzIG1ham9yIGxvb2tz
IGF0IGhvdyB0byByZWRlc2lnbiBzeXN0ZW1zIHRoYXQgYXJlIHNlY3VyZSwgaG93IHRvIG1lYXN1
cmUgcmlzaywgYW5kIGhvdyBlbnN1cmUgdGhhdCBwcm9wZXIgbGV2ZWxzIG9mIHByaXZhY3kgYXJl
IG1haW50YWluZWQgZm9yIGluZGl2aWR1YWzCoCB1c2Vycy4gIFJlbWVtYmVyIHRoYXQgc2VjdXJp
dHkgaXMgYSBwcm9jZXNzLCBub3QgYQpwcm9kdWN0LiBub3QgYWxsIHNlY3VyaXR5IGFuZCBwcml2
YWN5IGFyZSByZXNvbHZlZCB0ZWNobmljYWxseSzCoCB3aXRob3V0IGZvcmdldGluZyB0aGF0IFVz
ZXIgaXMgV2VhayBub2RlIG9mIGNoYWluLiAKSFNUUyAsICBUTFMgLEhUVFBTICBGVFBTICBvciBO
U1MgLyBHbnVUTFMgLyBPcGVuU1NMICAuIMKgIGNhbsKgIGJyZWFrICB0aGUgSUVURiB3ZWIgc2l0
ZSBvbGQgdG9vbHMuICBidXQgcHJvdmlkZcKgIGxldmVscyBvZiBwcml2YWN5IGFuZCBzZWN1cml0
eSAuIApUaGUgZGVsaXZlcnkgYW5kIG1haW50ZW5hbmNlIHRlYW0gaXMgcmVzcG9uc2libGUgZm9y
IG9uLWdvaW5nIHVwZGF0aW5nIGFuZCBtb25pdG9yaW5nLCBpbmNsdWRpbmcgc2VjdXJpdHkgbWVh
c3VyZXMgZm9yIGFjY2VzcyBjb250cm9sIGFuZCBpbmZvcm1hdGlvbiBjb25maWRlbnRpYWxpdHku
ICB3aGVuIHRoZXJlIGFyZSBtZWNoYW5pc21zIGluIHBsYWNlIHRvIGVzdGFibGlzaApwcml2YWN5
IGFuZCB0cnVzdCAgLgoKU2VycmhpbmkgTW9oYW1tZWQKClN1biwgNiBBcHIgMjAxNCAyMzozMDox
MSArMDAwMCDQvtGCIENocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQG1pY3Jvc29mdC5jb20+Ogo+
PiBJIGFncmVlIHdpdGggdGhvc2Ugd2hvJ3ZlIHNhaWQgYSB0aHJlYXQgYW5hbHlzaXMgaXMgbmVl
ZGVkIGJlZm9yZQo+PiBkZWNpZGluZyBhY2Nlc3MgaXMgbGltaXRlZCB0byBUTFMgb3Igb3RoZXIg
c2VjdXJlIGFsdGVybmF0aXZlLgo+Cj5CdXQgd2UgaGF2ZSB0aGF0IHRocmVhdCBhbmFseXNpcywg
YW5kIHRoZSByZWNvbW1lbmRlZCBtaXRpZ2F0aW9uIGlzIHByZWNpc2VseSAiZW5jcnlwdCBldmVy
eXRoaW5nLiIgVGhlICJwZXJ2YXNpdmUgbW9uaXRvcmluZyIgdGhyZWF0IGlzIGFuYWx5emVkIGJ5
IGEgbnVtYmVyIG9mIHBlcnBhc3MgZHJhZnRzLCBhbmQgU3RlcGhlbiBoYXMgbWVyZWx5IGZvbGxv
d2VkIHRoZSBjb25jbHVzaW9ucyBvZiB0aGF0IGFuYWx5c2lzLiBUaGVyZSBpcyBubyBuZWVkIHRv
IHJlcGVhdCB0aGF0IGFuYWx5c2lzIGZvciBlYWNoIGFuZCBldmVyeSB0b29sIHRoYXQgdGhlIElF
VEYgcHJvZHVjZXMsIGFuZCB0aGVyZSBpcyBpbmRlZWQgYSBuZWVkIGZvciB0aGUgSUVURiBhcyBh
IHdob2xlIHRvICJsZWFkIGJ5IGV4YW1wbGUuIgo+Cj4tLSBDaHJpc3RpYW4gSHVpdGVtYQo+Cj4K
PgoKCtChINGD0LLQsNC20LXQvdC40LXQvCwKbW9oYW1tZWQgc2VycmhpbmkKc2VycmhpbmlAbWFp
bC5ydQo=

----ALT--2TPB6QXn1396831215
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

CjxIVE1MPjxCT0RZPjxicj48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4KIDx3OldvcmREb2N1bWVu
dD4KICA8dzpWaWV3Pk5vcm1hbDwvdzpWaWV3PgogIDx3Olpvb20+MDwvdzpab29tPgogIDx3OlRy
YWNrTW92ZXMvPgogIDx3OlRyYWNrRm9ybWF0dGluZy8+CiAgPHc6SHlwaGVuYXRpb25ab25lPjIx
PC93Okh5cGhlbmF0aW9uWm9uZT4KICA8dzpQdW5jdHVhdGlvbktlcm5pbmcvPgogIDx3OlZhbGlk
YXRlQWdhaW5zdFNjaGVtYXMvPgogIDx3OlNhdmVJZlhNTEludmFsaWQ+ZmFsc2U8L3c6U2F2ZUlm
WE1MSW52YWxpZD4KICA8dzpJZ25vcmVNaXhlZENvbnRlbnQ+ZmFsc2U8L3c6SWdub3JlTWl4ZWRD
b250ZW50PgogIDx3OkFsd2F5c1Nob3dQbGFjZWhvbGRlclRleHQ+ZmFsc2U8L3c6QWx3YXlzU2hv
d1BsYWNlaG9sZGVyVGV4dD4KICA8dzpEb05vdFByb21vdGVRRi8+CiAgPHc6TGlkVGhlbWVPdGhl
cj5GUjwvdzpMaWRUaGVtZU90aGVyPgogIDx3OkxpZFRoZW1lQXNpYW4+WC1OT05FPC93OkxpZFRo
ZW1lQXNpYW4+CiAgPHc6TGlkVGhlbWVDb21wbGV4U2NyaXB0PkFSLVNBPC93OkxpZFRoZW1lQ29t
cGxleFNjcmlwdD4KICA8dzpDb21wYXRpYmlsaXR5PgogICA8dzpCcmVha1dyYXBwZWRUYWJsZXMv
PgogICA8dzpTbmFwVG9HcmlkSW5DZWxsLz4KICAgPHc6V3JhcFRleHRXaXRoUHVuY3QvPgogICA8
dzpVc2VBc2lhbkJyZWFrUnVsZXMvPgogICA8dzpEb250R3Jvd0F1dG9maXQvPgogICA8dzpTcGxp
dFBnQnJlYWtBbmRQYXJhTWFyay8+CiAgIDx3OkRvbnRWZXJ0QWxpZ25DZWxsV2l0aFNwLz4KICAg
PHc6RG9udEJyZWFrQ29uc3RyYWluZWRGb3JjZWRUYWJsZXMvPgogICA8dzpEb250VmVydEFsaWdu
SW5UeGJ4Lz4KICAgPHc6V29yZDExS2VybmluZ1BhaXJzLz4KICAgPHc6Q2FjaGVkQ29sQmFsYW5j
ZS8+CiAgPC93OkNvbXBhdGliaWxpdHk+CiAgPG06bWF0aFByPgogICA8bTptYXRoRm9udCBtOnZh
bD0iQ2FtYnJpYSBNYXRoIi8+CiAgIDxtOmJya0JpbiBtOnZhbD0iYmVmb3JlIi8+CiAgIDxtOmJy
a0JpblN1YiBtOnZhbD0iJiM0NTstIi8+CiAgIDxtOnNtYWxsRnJhYyBtOnZhbD0ib2ZmIi8+CiAg
IDxtOmRpc3BEZWYvPgogICA8bTpsTWFyZ2luIG06dmFsPSIwIi8+CiAgIDxtOnJNYXJnaW4gbTp2
YWw9IjAiLz4KICAgPG06ZGVmSmMgbTp2YWw9ImNlbnRlckdyb3VwIi8+CiAgIDxtOndyYXBJbmRl
bnQgbTp2YWw9IjE0NDAiLz4KICAgPG06aW50TGltIG06dmFsPSJzdWJTdXAiLz4KICAgPG06bmFy
eUxpbSBtOnZhbD0idW5kT3ZyIi8+CiAgPC9tOm1hdGhQcj48L3c6V29yZERvY3VtZW50Pgo8L3ht
bD48IVtlbmRpZl0tLT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtsaW5lLWhlaWdodDoK
MTUwJTtmb250LWZhbWlseTomcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYm
cXVvdDs7bXNvLWFzY2lpLXRoZW1lLWZvbnQ6bWFqb3ItYmlkaTsKbXNvLWZhcmVhc3QtZm9udC1m
YW1pbHk6Q2FsaWJyaTttc28tZmFyZWFzdC10aGVtZS1mb250Om1pbm9yLWxhdGluO21zby1oYW5z
aS10aGVtZS1mb250OgptYWpvci1iaWRpO21zby1iaWRpLXRoZW1lLWZvbnQ6bWFqb3ItYmlkaTtt
c28tYW5zaS1sYW5ndWFnZTpFTi1VUzttc28tZmFyZWFzdC1sYW5ndWFnZToKRU4tVVM7bXNvLWJp
ZGktbGFuZ3VhZ2U6QVItU0EiIGxhbmc9IkVOLVVTIj48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4K
IDx3OldvcmREb2N1bWVudD4KICA8dzpWaWV3Pk5vcm1hbDwvdzpWaWV3PgogIDx3Olpvb20+MDwv
dzpab29tPgogIDx3OlRyYWNrTW92ZXMvPgogIDx3OlRyYWNrRm9ybWF0dGluZy8+CiAgPHc6SHlw
aGVuYXRpb25ab25lPjIxPC93Okh5cGhlbmF0aW9uWm9uZT4KICA8dzpQdW5jdHVhdGlvbktlcm5p
bmcvPgogIDx3OlZhbGlkYXRlQWdhaW5zdFNjaGVtYXMvPgogIDx3OlNhdmVJZlhNTEludmFsaWQ+
ZmFsc2U8L3c6U2F2ZUlmWE1MSW52YWxpZD4KICA8dzpJZ25vcmVNaXhlZENvbnRlbnQ+ZmFsc2U8
L3c6SWdub3JlTWl4ZWRDb250ZW50PgogIDx3OkFsd2F5c1Nob3dQbGFjZWhvbGRlclRleHQ+ZmFs
c2U8L3c6QWx3YXlzU2hvd1BsYWNlaG9sZGVyVGV4dD4KICA8dzpEb05vdFByb21vdGVRRi8+CiAg
PHc6TGlkVGhlbWVPdGhlcj5GUjwvdzpMaWRUaGVtZU90aGVyPgogIDx3OkxpZFRoZW1lQXNpYW4+
WC1OT05FPC93OkxpZFRoZW1lQXNpYW4+CiAgPHc6TGlkVGhlbWVDb21wbGV4U2NyaXB0PkFSLVNB
PC93OkxpZFRoZW1lQ29tcGxleFNjcmlwdD4KICA8dzpDb21wYXRpYmlsaXR5PgogICA8dzpCcmVh
a1dyYXBwZWRUYWJsZXMvPgogICA8dzpTbmFwVG9HcmlkSW5DZWxsLz4KICAgPHc6V3JhcFRleHRX
aXRoUHVuY3QvPgogICA8dzpVc2VBc2lhbkJyZWFrUnVsZXMvPgogICA8dzpEb250R3Jvd0F1dG9m
aXQvPgogICA8dzpTcGxpdFBnQnJlYWtBbmRQYXJhTWFyay8+CiAgIDx3OkRvbnRWZXJ0QWxpZ25D
ZWxsV2l0aFNwLz4KICAgPHc6RG9udEJyZWFrQ29uc3RyYWluZWRGb3JjZWRUYWJsZXMvPgogICA8
dzpEb250VmVydEFsaWduSW5UeGJ4Lz4KICAgPHc6V29yZDExS2VybmluZ1BhaXJzLz4KICAgPHc6
Q2FjaGVkQ29sQmFsYW5jZS8+CiAgPC93OkNvbXBhdGliaWxpdHk+CiAgPG06bWF0aFByPgogICA8
bTptYXRoRm9udCBtOnZhbD0iQ2FtYnJpYSBNYXRoIi8+CiAgIDxtOmJya0JpbiBtOnZhbD0iYmVm
b3JlIi8+CiAgIDxtOmJya0JpblN1YiBtOnZhbD0iJiM0NTstIi8+CiAgIDxtOnNtYWxsRnJhYyBt
OnZhbD0ib2ZmIi8+CiAgIDxtOmRpc3BEZWYvPgogICA8bTpsTWFyZ2luIG06dmFsPSIwIi8+CiAg
IDxtOnJNYXJnaW4gbTp2YWw9IjAiLz4KICAgPG06ZGVmSmMgbTp2YWw9ImNlbnRlckdyb3VwIi8+
CiAgIDxtOndyYXBJbmRlbnQgbTp2YWw9IjE0NDAiLz4KICAgPG06aW50TGltIG06dmFsPSJzdWJT
dXAiLz4KICAgPG06bmFyeUxpbSBtOnZhbD0idW5kT3ZyIi8+CiAgPC9tOm1hdGhQcj48L3c6V29y
ZERvY3VtZW50Pgo8L3htbD48IVtlbmRpZl0tLT48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxOHB4
OyI+PHNwYW4gZGF0YS1tY2Utc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBmb250LWZhbWlseTog
J1RpbWVzIE5ldyBSb21hbicsJ3NlcmlmJzsiIHN0eWxlPSJsaW5lLWhlaWdodDogMTUwJTsgZm9u
dC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCdzZXJpZic7IiBsYW5nPSJFTi1VUyI+SSBhZ3Jl
ZSwgVGhlIFNlY3VyaXR5IGFuZCBSaXNrIEFuYWx5c2lzJm5ic3A7IGlzIG1ham9yIGxvb2tzIGF0
IGhvdyB0byByZWRlc2lnbiBzeXN0ZW1zIHRoYXQgYXJlIHNlY3VyZSwgaG93IHRvIG1lYXN1cmUg
cmlzaywgYW5kIGhvdyBlbnN1cmUgdGhhdCBwcm9wZXIgbGV2ZWxzIG9mIHByaXZhY3kgYXJlIG1h
aW50YWluZWQgZm9yIGluZGl2aWR1YWwmbmJzcDsgdXNlcnMuIDwvc3Bhbj48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4KIDx3OkxhdGVudFN0eWxlcyBEZWZMb2NrZWRTdGF0ZT0iZmFsc2UiIERlZlVu
aGlkZVdoZW5Vc2VkPSJ0cnVlIgogIERlZlNlbWlIaWRkZW49InRydWUiIERlZlFGb3JtYXQ9ImZh
bHNlIiBEZWZQcmlvcml0eT0iOTkiCiAgTGF0ZW50U3R5bGVDb3VudD0iMjY3Ij4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjAiIFNlbWlIaWRkZW49ImZhbHNlIgog
ICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9Ik5vcm1hbCIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgU2VtaUhpZGRlbj0i
ZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVh
ZGluZyAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBR
Rm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgMyIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1
ZSIgTmFtZT0iaGVhZGluZyA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI5IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDUiLz4KICA8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9Imhl
YWRpbmcgNiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIg
UUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVhZGluZyA3Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDgiLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjkiIFFGb3JtYXQ9InRy
dWUiIE5hbWU9ImhlYWRpbmcgOSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iMzkiIE5hbWU9InRvYyAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9jIDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2MgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIE5hbWU9InRvYyA0Ii8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9jIDUiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2MgNiIvPgogIDx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIE5hbWU9InRvYyA3Ii8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9j
IDgiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1l
PSJ0b2MgOSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzUi
IFFGb3JtYXQ9InRydWUiIE5hbWU9ImNhcHRpb24iLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjEwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVz
ZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJUaXRsZSIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMSIgTmFtZT0iRGVmYXVsdCBQYXJhZ3JhcGggRm9u
dCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMTEiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5h
bWU9IlN1YnRpdGxlIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSIyMiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1h
dD0idHJ1ZSIgTmFtZT0iU3Ryb25nIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSIyMCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iRW1waGFzaXMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjU5IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJUYWJsZSBHcmlkIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iUGxhY2Vob2xkZXIgVGV4dCIv
PgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMSIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0i
Tm8gU3BhY2luZyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ikxp
Z2h0IFNoYWRpbmciLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjYxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJM
aWdodCBMaXN0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2
MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGln
aHQgR3JpZCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMi
IFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1
bSBTaGFkaW5nIDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjY0IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJN
ZWRpdW0gU2hhZGluZyAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2NSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTWVkaXVtIExpc3QgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNjYiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9Ik1lZGl1bSBMaXN0IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjY3IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJNZWRpdW0gR3JpZCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI2OCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIg
TmFtZT0iTWVkaXVtIEdyaWQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNjkiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2Ui
IE5hbWU9Ik1lZGl1bSBHcmlkIDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjcwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJEYXJrIExpc3QiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjcxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJDb2xvcmZ1bCBTaGFkaW5nIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI3MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgTmFtZT0iQ29sb3JmdWwgTGlzdCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNzMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9IkNvbG9yZnVsIEdyaWQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjYwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZh
bHNlIiBOYW1lPSJMaWdodCBTaGFkaW5nIEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdo
ZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDEiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2Vu
dCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNo
YWRpbmcgMiBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNjUiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9Ik1lZGl1bSBMaXN0IDEgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJSZXZpc2lvbiIvPgogIDx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzQiIFNlbWlIaWRkZW49ImZhbHNlIgog
ICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9Ikxpc3QgUGFyYWdy
YXBoIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIyOSIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIg
TmFtZT0iUXVvdGUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjMwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0
PSJ0cnVlIiBOYW1lPSJJbnRlbnNlIFF1b3RlIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI2NiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMiBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjciIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhp
ZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDEgQWNjZW50IDEiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY4IiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAyIEFjY2VudCAx
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQg
MyBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NzAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkRh
cmsgTGlzdCBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9IkNvbG9yZnVsIFNoYWRpbmcgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjcyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVz
ZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBMaXN0IEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgR3JpZCBBY2NlbnQgMSIvPgogIDx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIFNlbWlIaWRkZW49ImZh
bHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmcgQWNjZW50
IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBMaXN0
IEFjY2VudCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2
MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGln
aHQgR3JpZCBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNjMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9Ik1lZGl1bSBTaGFkaW5nIDEgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVz
ZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAyIEFjY2VudCAyIi8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMSBBY2NlbnQgMiIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDIgQWNj
ZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY3IiBT
ZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0g
R3JpZCAxIEFjY2VudCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2OCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTWVkaXVtIEdyaWQgMiBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNjkiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0i
ZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDMgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJEYXJrIExpc3QgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAg
VW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5nIEFjY2VudCAyIi8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MiIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgTGlzdCBB
Y2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzMi
IFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9y
ZnVsIEdyaWQgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjYwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJMaWdodCBTaGFkaW5nIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVX
aGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAg
VW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2VudCAzIi8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcg
MiBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjUiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1l
ZGl1bSBMaXN0IDEgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjY2IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJNZWRpdW0gTGlzdCAyIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI2NyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5V
c2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMSBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjgiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDIgQWNjZW50IDMiLz4KICA8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY5IiBTZW1pSGlkZGVuPSJm
YWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAzIEFjY2Vu
dCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MCIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iRGFyayBMaXN0
IEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3
MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29s
b3JmdWwgU2hhZGluZyBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNzIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9IkNvbG9yZnVsIExpc3QgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjczIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2VudCAzIi8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgU2hhZGluZyBBY2NlbnQgNCIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjEiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IExpc3QgQWNjZW50
IDQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYyIiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBHcmlk
IEFjY2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2
MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVk
aXVtIFNoYWRpbmcgMSBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNjQiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDIgQWNjZW50IDQiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY1IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gTGlzdCAxIEFjY2VudCA0Ii8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NiIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMiBBY2NlbnQgNCIv
PgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjciIFNlbWlIaWRk
ZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDEg
QWNjZW50IDQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY4
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRp
dW0gR3JpZCAyIEFjY2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI2OSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIg
TmFtZT0iTWVkaXVtIEdyaWQgMyBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNzAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIE5hbWU9IkRhcmsgTGlzdCBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVX
aGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIFNoYWRpbmcgQWNjZW50IDQiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcyIiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBMaXN0IEFjY2VudCA0
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MyIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgR3Jp
ZCBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ikxp
Z2h0IFNoYWRpbmcgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjYxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJMaWdodCBMaXN0IEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI2MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iTGlnaHQgR3JpZCBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVX
aGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDEgQWNjZW50IDUiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAyIEFjY2Vu
dCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExp
c3QgMSBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iNjYiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9
Ik1lZGl1bSBMaXN0IDIgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjY3IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZh
bHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAxIEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdo
ZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMiBBY2NlbnQgNSIvPgogIDx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjkiIFNlbWlIaWRkZW49ImZhbHNlIgog
ICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDMgQWNjZW50IDUiLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcwIiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJEYXJrIExpc3QgQWNjZW50
IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcxIiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBT
aGFkaW5nIEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI3MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iQ29sb3JmdWwgTGlzdCBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNzMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0i
ZmFsc2UiIE5hbWU9IkNvbG9yZnVsIEdyaWQgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBTaGFkaW5nIEFjY2VudCA2Ii8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQgNiIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjIiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50
IDYiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hh
ZGluZyAxIEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2NCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTWVkaXVtIFNoYWRpbmcgMiBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNjUiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDEgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY2IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5o
aWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gTGlzdCAyIEFjY2VudCA2Ii8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NyIgU2VtaUhpZGRlbj0iZmFs
c2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMSBBY2NlbnQg
NiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjgiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlk
IDIgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjY5IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJN
ZWRpdW0gR3JpZCAzIEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI3MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgTmFtZT0iRGFyayBMaXN0IEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI3MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgU2hhZGluZyBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIExpc3QgQWNjZW50IDYiLz4KICA8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjczIiBTZW1pSGlkZGVuPSJm
YWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2Vu
dCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIxOSIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIg
TmFtZT0iU3VidGxlIEVtcGhhc2lzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSIyMSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iSW50ZW5zZSBFbXBoYXNpcyIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9IlN1YnRsZSBSZWZlcmVu
Y2UiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjMyIiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBO
YW1lPSJJbnRlbnNlIFJlZmVyZW5jZSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iMzMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9IkJvb2sgVGl0bGUiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM3IiBOYW1lPSJCaWJsaW9ncmFwaHkiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBRRm9ybWF0PSJ0cnVlIiBO
YW1lPSJUT0MgSGVhZGluZyIvPgogPC93OkxhdGVudFN0eWxlcz4KPC94bWw+PCFbZW5kaWZdLS0+
PCEtLVtpZiBndGUgbXNvIDEwXT4KPHN0eWxlPgogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8KIHRh
YmxlLk1zb05vcm1hbFRhYmxlCgl7bXNvLXN0eWxlLW5hbWU6IlRhYmxlYXUgTm9ybWFsIjsKCW1z
by10c3R5bGUtcm93YmFuZC1zaXplOjA7Cgltc28tdHN0eWxlLWNvbGJhbmQtc2l6ZTowOwoJbXNv
LXN0eWxlLW5vc2hvdzp5ZXM7Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7Cgltc28tc3R5bGUtcWZv
cm1hdDp5ZXM7Cgltc28tc3R5bGUtcGFyZW50OiIiOwoJbXNvLXBhZGRpbmctYWx0OjBjbSA1LjRw
dCAwY20gNS40cHQ7Cgltc28tcGFyYS1tYXJnaW4tdG9wOmF1dG87Cgltc28tcGFyYS1tYXJnaW4t
cmlnaHQ6MGNtOwoJbXNvLXBhcmEtbWFyZ2luLWJvdHRvbTphdXRvOwoJbXNvLXBhcmEtbWFyZ2lu
LWxlZnQ6MGNtOwoJdGV4dC1hbGlnbjpqdXN0aWZ5OwoJbGluZS1oZWlnaHQ6MTUwJTsKCW1zby1w
YWdpbmF0aW9uOndpZG93LW9ycGhhbjsKCWZvbnQtc2l6ZToxMS4wcHQ7Cglmb250LWZhbWlseToi
Q2FsaWJyaSIsInNhbnMtc2VyaWYiOwoJbXNvLWFzY2lpLWZvbnQtZmFtaWx5OkNhbGlicmk7Cglt
c28tYXNjaWktdGhlbWUtZm9udDptaW5vci1sYXRpbjsKCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5
OiJUaW1lcyBOZXcgUm9tYW4iOwoJbXNvLWZhcmVhc3QtdGhlbWUtZm9udDptaW5vci1mYXJlYXN0
OwoJbXNvLWhhbnNpLWZvbnQtZmFtaWx5OkNhbGlicmk7Cgltc28taGFuc2ktdGhlbWUtZm9udDpt
aW5vci1sYXRpbjt9Cjwvc3R5bGU+CjwhW2VuZGlmXS0tPlJlbWVtYmVyIHRoYXQgc2VjdXJpdHkg
aXMgYSBwcm9jZXNzLCBub3QgYQpwcm9kdWN0Ljwvc3Bhbj48L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTogMThweDsiPiBub3QgYWxsIHNlY3VyaXR5IGFuZCBwcml2YWN5IGFyZSByZXNvbHZl
ZCB0ZWNobmljYWxseSwmbmJzcDsgd2l0aG91dCBmb3JnZXRpbmcgdGhhdCBVc2VyIGlzIFdlYWsg
bm9kZSBvZiBjaGFpbi4gPC9zcGFuPjxicj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxOHB4OyI+
PHNwYW4gZGF0YS1tY2Utc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBmb250LWZhbWlseTogJ1Rp
bWVzIE5ldyBSb21hbicsJ3NlcmlmJzsiIHN0eWxlPSJsaW5lLWhlaWdodDogMTUwJTsgZm9udC1m
YW1pbHk6ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OywmcXVvdDtzZXJpZiZxdW90OzsiIGxh
bmc9IkVOLVVTIj5IU1RTICwgPC9zcGFuPjxzcGFuIGRhdGEtbWNlLXN0eWxlPSJsaW5lLWhlaWdo
dDogMTUwJTsgZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCdzZXJpZic7IiBzdHlsZT0i
bGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDssJnF1b3Q7c2VyaWYmcXVvdDs7IiBsYW5nPSJFTi1VUyI+VExTICxIVFRQUyA8L3NwYW4+PHNw
YW4gZGF0YS1tY2Utc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBmb250LWZhbWlseTogJ1RpbWVz
IE5ldyBSb21hbicsJ3NlcmlmJzsiIHN0eWxlPSJsaW5lLWhlaWdodDogMTUwJTsgZm9udC1mYW1p
bHk6ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OywmcXVvdDtzZXJpZiZxdW90OzsiIGxhbmc9
IkVOLVVTIj5GVFBTIDwvc3Bhbj48c3BhbiBkYXRhLW1jZS1zdHlsZT0ibGluZS1oZWlnaHQ6IDE1
MCU7IGZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJywnc2VyaWYnOyIgc3R5bGU9ImxpbmUt
aGVpZ2h0OiAxNTAlOyBmb250LWZhbWlseTogJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZx
dW90O3NlcmlmJnF1b3Q7OyIgbGFuZz0iRU4tVVMiPm9yPC9zcGFuPjxzcGFuIGRhdGEtbWNlLXN0
eWxlPSJsaW5lLWhlaWdodDogMTUwJTsgZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCdz
ZXJpZic7IiBzdHlsZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAmcXVvdDtUaW1l
cyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7IiBsYW5nPSJFTi1VUyI+IE5TUyAv
IEdudVRMUyAvIE9wZW5TU0wgPC9zcGFuPjxzcGFuIGRhdGEtbWNlLXN0eWxlPSJsaW5lLWhlaWdo
dDogMTUwJTsgZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCdzZXJpZic7IiBzdHlsZT0i
bGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVv
dDssJnF1b3Q7c2VyaWYmcXVvdDs7IiBsYW5nPSJFTi1VUyI+Ljwvc3Bhbj48c3BhbiBkYXRhLW1j
ZS1zdHlsZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFu
Jywnc2VyaWYnOyIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBmb250LWZhbWlseTogJnF1b3Q7
VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7OyIgbGFuZz0iRU4tVVMiPiZu
YnNwOyBjYW4mbmJzcDsgYnJlYWsgPC9zcGFuPjxzcGFuIGRhdGEtbWNlLXN0eWxlPSJsaW5lLWhl
aWdodDogMTUwJTsgZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCdzZXJpZic7IiBzdHls
ZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAmcXVvdDtUaW1lcyBOZXcgUm9tYW4m
cXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7IiBsYW5nPSJFTi1VUyI+dGhlIElFVEYgd2ViIHNpdGU8
c3BhbiBkYXRhLW1jZS1zdHlsZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAnVGlt
ZXMgTmV3IFJvbWFuJywnc2VyaWYnOyIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBmb250LWZh
bWlseTogJ1RpbWVzIE5ldyBSb21hbicsJ3NlcmlmJzsiIGxhbmc9IkVOLVVTIj4gPC9zcGFuPjwv
c3Bhbj48c3BhbiBkYXRhLW1jZS1zdHlsZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5
OiAnVGltZXMgTmV3IFJvbWFuJywnc2VyaWYnOyIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBm
b250LWZhbWlseTogJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7LCZxdW90O3NlcmlmJnF1b3Q7
OyIgbGFuZz0iRU4tVVMiPm9sZCB0b29scy4gPC9zcGFuPjxzcGFuIGRhdGEtbWNlLXN0eWxlPSJs
aW5lLWhlaWdodDogMTUwJTsgZm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCdzZXJpZic7
IiBzdHlsZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAmcXVvdDtUaW1lcyBOZXcg
Um9tYW4mcXVvdDssJnF1b3Q7c2VyaWYmcXVvdDs7IiBsYW5nPSJFTi1VUyI+YnV0IHByb3ZpZGUm
bmJzcDs8c3BhbiBkYXRhLW1jZS1zdHlsZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5
OiAnVGltZXMgTmV3IFJvbWFuJywnc2VyaWYnOyIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBm
b250LWZhbWlseTogJ1RpbWVzIE5ldyBSb21hbicsJ3NlcmlmJzsiIGxhbmc9IkVOLVVTIj48c3Bh
biBkYXRhLW1jZS1zdHlsZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAnVGltZXMg
TmV3IFJvbWFuJywnc2VyaWYnOyIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBmb250LWZhbWls
eTogJ1RpbWVzIE5ldyBSb21hbicsJ3NlcmlmJzsiIGxhbmc9IkVOLVVTIj5sZXZlbHMgb2YgcHJp
dmFjeTwvc3Bhbj48L3NwYW4+IGFuZCBzZWN1cml0eSAuIDxicj48c3BhbiBkYXRhLW1jZS1zdHls
ZT0ibGluZS1oZWlnaHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAnVGltZXMgTmV3IFJvbWFuJywnc2Vy
aWYnOyIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxNTAlOyBmb250LWZhbWlseTogJ1RpbWVzIE5ldyBS
b21hbicsJ3NlcmlmJzsiIGxhbmc9IkVOLVVTIj5UaGUgZGVsaXZlcnkgYW5kIG1haW50ZW5hbmNl
IHRlYW0gaXMgcmVzcG9uc2libGUgZm9yIG9uLWdvaW5nIHVwZGF0aW5nIGFuZCBtb25pdG9yaW5n
LCBpbmNsdWRpbmcgc2VjdXJpdHkgbWVhc3VyZXMgZm9yIGFjY2VzcyBjb250cm9sIGFuZCBpbmZv
cm1hdGlvbiBjb25maWRlbnRpYWxpdHkuIDwvc3Bhbj48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4K
IDx3OkxhdGVudFN0eWxlcyBEZWZMb2NrZWRTdGF0ZT0iZmFsc2UiIERlZlVuaGlkZVdoZW5Vc2Vk
PSJ0cnVlIgogIERlZlNlbWlIaWRkZW49InRydWUiIERlZlFGb3JtYXQ9ImZhbHNlIiBEZWZQcmlv
cml0eT0iOTkiCiAgTGF0ZW50U3R5bGVDb3VudD0iMjY3Ij4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVu
VXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9Ik5vcm1hbCIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVhZGluZyAxIi8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBRRm9ybWF0PSJ0cnVl
IiBOYW1lPSJoZWFkaW5nIDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgMyIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVh
ZGluZyA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBR
Rm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgNiIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1
ZSIgTmFtZT0iaGVhZGluZyA3Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI5IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDgiLz4KICA8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9Imhl
YWRpbmcgOSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzki
IE5hbWU9InRvYyAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSIzOSIgTmFtZT0idG9jIDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjM5IiBOYW1lPSJ0b2MgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iMzkiIE5hbWU9InRvYyA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9jIDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2MgNiIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIE5hbWU9InRvYyA3Ii8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9jIDgiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2MgOSIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzUiIFFGb3JtYXQ9InRy
dWUiIE5hbWU9ImNhcHRpb24iLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjEwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBR
Rm9ybWF0PSJ0cnVlIiBOYW1lPSJUaXRsZSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iMSIgTmFtZT0iRGVmYXVsdCBQYXJhZ3JhcGggRm9udCIvPgogIDx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMTEiIFNlbWlIaWRkZW49ImZhbHNl
IgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9IlN1YnRpdGxl
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIyMiIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFt
ZT0iU3Ryb25nIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIy
MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0i
dHJ1ZSIgTmFtZT0iRW1waGFzaXMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjU5IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJUYWJsZSBHcmlkIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iUGxhY2Vob2xkZXIgVGV4dCIvPgogIDx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iTm8gU3BhY2luZyIv
PgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIFNlbWlIaWRk
ZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmci
Lz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBTZW1pSGlk
ZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBMaXN0Ii8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MiIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgR3JpZCIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDEi
Lz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBTZW1pSGlk
ZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGlu
ZyAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExp
c3QgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIFNl
bWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBM
aXN0IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY3IiBT
ZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0g
R3JpZCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIg
U2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVt
IEdyaWQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjki
IFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1
bSBHcmlkIDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9Ijcw
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJEYXJr
IExpc3QiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcxIiBT
ZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1
bCBTaGFkaW5nIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3
MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29s
b3JmdWwgTGlzdCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NzMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNv
bG9yZnVsIEdyaWQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjYwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJM
aWdodCBTaGFkaW5nIEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgTmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNjIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2VudCAxIi8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgU2VtaUhpZGRlbj0iZmFs
c2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMiBBY2Nl
bnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjUiIFNl
bWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBM
aXN0IDEgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJSZXZpc2lvbiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzQiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVu
VXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9Ikxpc3QgUGFyYWdyYXBoIi8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIyOSIgU2VtaUhpZGRlbj0iZmFs
c2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iUXVvdGUi
Lz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjMwIiBTZW1pSGlk
ZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBOYW1l
PSJJbnRlbnNlIFF1b3RlIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2NiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTWVkaXVtIExpc3QgMiBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNjciIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0i
ZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDEgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY4IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAyIEFjY2VudCAxIi8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMyBBY2NlbnQgMSIv
PgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzAiIFNlbWlIaWRk
ZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkRhcmsgTGlzdCBBY2Nl
bnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzEiIFNl
bWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVs
IFNoYWRpbmcgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjcyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJDb2xvcmZ1bCBMaXN0IEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI3MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgR3JpZCBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhp
ZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmcgQWNjZW50IDIiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBMaXN0IEFjY2VudCAyIi8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MiIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgR3JpZCBBY2Nl
bnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIFNl
bWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBT
aGFkaW5nIDEgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjY0IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJNZWRpdW0gU2hhZGluZyAyIEFjY2VudCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5V
c2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMSBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDIgQWNjZW50IDIiLz4KICA8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY3IiBTZW1pSGlkZGVuPSJm
YWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAxIEFjY2Vu
dCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdy
aWQgMiBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iNjkiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9
Ik1lZGl1bSBHcmlkIDMgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjcwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZh
bHNlIiBOYW1lPSJEYXJrIExpc3QgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjcxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVz
ZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5nIEFjY2VudCAyIi8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgTGlzdCBBY2NlbnQgMiIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzMiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIEdyaWQgQWNj
ZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYwIiBT
ZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBT
aGFkaW5nIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTGlnaHQgTGlzdCBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNjIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVz
ZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2VudCAzIi8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMiBBY2NlbnQgMyIv
PgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjUiIFNlbWlIaWRk
ZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDEg
QWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY2
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRp
dW0gTGlzdCAyIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI2NyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIg
TmFtZT0iTWVkaXVtIEdyaWQgMSBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNjgiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDIgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY5IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5o
aWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAzIEFjY2VudCAzIi8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MCIgU2VtaUhpZGRlbj0iZmFs
c2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iRGFyayBMaXN0IEFjY2VudCAzIi8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MSIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgU2hhZGlu
ZyBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NzIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNv
bG9yZnVsIExpc3QgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjczIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI2MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5V
c2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgU2hhZGluZyBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IExpc3QgQWNjZW50IDQiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYyIiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBHcmlkIEFjY2VudCA0Ii8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MyIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcg
MSBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjQiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1l
ZGl1bSBTaGFkaW5nIDIgQWNjZW50IDQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjY1IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZh
bHNlIiBOYW1lPSJNZWRpdW0gTGlzdCAxIEFjY2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdo
ZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMiBBY2NlbnQgNCIvPgogIDx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjciIFNlbWlIaWRkZW49ImZhbHNlIgog
ICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDEgQWNjZW50IDQiLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY4IiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAyIEFj
Y2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIg
U2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVt
IEdyaWQgMyBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNzAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9IkRhcmsgTGlzdCBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9IkNvbG9yZnVsIFNoYWRpbmcgQWNjZW50IDQiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBMaXN0IEFjY2VudCA0Ii8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MyIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgR3JpZCBBY2NlbnQgNCIv
PgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIFNlbWlIaWRk
ZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmcg
QWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYx
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdo
dCBMaXN0IEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTGlnaHQgR3JpZCBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNjMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDEgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAyIEFjY2VudCA1Ii8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgU2VtaUhpZGRlbj0iZmFs
c2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMSBBY2NlbnQg
NSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0
IDIgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjY3IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJN
ZWRpdW0gR3JpZCAxIEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI2OCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgTmFtZT0iTWVkaXVtIEdyaWQgMiBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjkiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVu
VXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDMgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAg
VW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJEYXJrIExpc3QgQWNjZW50IDUiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcxIiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5nIEFjY2Vu
dCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MiIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwg
TGlzdCBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iNzMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9
IkNvbG9yZnVsIEdyaWQgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjYwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZh
bHNlIiBOYW1lPSJMaWdodCBTaGFkaW5nIEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdo
ZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDYiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2Vu
dCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNo
YWRpbmcgMiBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNjUiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9Ik1lZGl1bSBMaXN0IDEgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjY2IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9
ImZhbHNlIiBOYW1lPSJNZWRpdW0gTGlzdCAyIEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlk
ZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMSBBY2NlbnQgNiIvPgogIDx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjgiIFNlbWlIaWRkZW49ImZhbHNl
IgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDIgQWNjZW50IDYi
Lz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY5IiBTZW1pSGlk
ZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAz
IEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3
MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iRGFy
ayBMaXN0IEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI3MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iQ29sb3JmdWwgU2hhZGluZyBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNzIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIExpc3QgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjczIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5o
aWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2VudCA2Ii8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIxOSIgU2VtaUhpZGRlbj0iZmFs
c2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iU3VidGxl
IEVtcGhhc2lzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIy
MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0i
dHJ1ZSIgTmFtZT0iSW50ZW5zZSBFbXBoYXNpcyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iMzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9IlN1YnRsZSBSZWZlcmVuY2UiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjMyIiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJJbnRlbnNl
IFJlZmVyZW5jZSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
MzMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9
InRydWUiIE5hbWU9IkJvb2sgVGl0bGUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjM3IiBOYW1lPSJCaWJsaW9ncmFwaHkiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJUT0MgSGVh
ZGluZyIvPgogPC93OkxhdGVudFN0eWxlcz4KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUg
bXNvIDEwXT4KPHN0eWxlPgogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8KIHRhYmxlLk1zb05vcm1h
bFRhYmxlCgl7bXNvLXN0eWxlLW5hbWU6IlRhYmxlYXUgTm9ybWFsIjsKCW1zby10c3R5bGUtcm93
YmFuZC1zaXplOjA7Cgltc28tdHN0eWxlLWNvbGJhbmQtc2l6ZTowOwoJbXNvLXN0eWxlLW5vc2hv
dzp5ZXM7Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7Cgltc28tc3R5bGUtcWZvcm1hdDp5ZXM7Cglt
c28tc3R5bGUtcGFyZW50OiIiOwoJbXNvLXBhZGRpbmctYWx0OjBjbSA1LjRwdCAwY20gNS40cHQ7
Cgltc28tcGFyYS1tYXJnaW4tdG9wOmF1dG87Cgltc28tcGFyYS1tYXJnaW4tcmlnaHQ6MGNtOwoJ
bXNvLXBhcmEtbWFyZ2luLWJvdHRvbTphdXRvOwoJbXNvLXBhcmEtbWFyZ2luLWxlZnQ6MGNtOwoJ
dGV4dC1hbGlnbjpqdXN0aWZ5OwoJbGluZS1oZWlnaHQ6MTUwJTsKCW1zby1wYWdpbmF0aW9uOndp
ZG93LW9ycGhhbjsKCWZvbnQtc2l6ZToxMS4wcHQ7Cglmb250LWZhbWlseToiQ2FsaWJyaSIsInNh
bnMtc2VyaWYiOwoJbXNvLWFzY2lpLWZvbnQtZmFtaWx5OkNhbGlicmk7Cgltc28tYXNjaWktdGhl
bWUtZm9udDptaW5vci1sYXRpbjsKCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iOwoJbXNvLWZhcmVhc3QtdGhlbWUtZm9udDptaW5vci1mYXJlYXN0OwoJbXNvLWhhbnNp
LWZvbnQtZmFtaWx5OkNhbGlicmk7Cgltc28taGFuc2ktdGhlbWUtZm9udDptaW5vci1sYXRpbjt9
Cjwvc3R5bGU+CjwhW2VuZGlmXS0tPjwvc3Bhbj48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4KIDx3
OkxhdGVudFN0eWxlcyBEZWZMb2NrZWRTdGF0ZT0iZmFsc2UiIERlZlVuaGlkZVdoZW5Vc2VkPSJ0
cnVlIgogIERlZlNlbWlIaWRkZW49InRydWUiIERlZlFGb3JtYXQ9ImZhbHNlIiBEZWZQcmlvcml0
eT0iOTkiCiAgTGF0ZW50U3R5bGVDb3VudD0iMjY3Ij4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9Ik5vcm1hbCIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlk
ZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVhZGluZyAxIi8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBRRm9ybWF0PSJ0cnVlIiBO
YW1lPSJoZWFkaW5nIDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgMyIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVhZGlu
ZyA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBRRm9y
bWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgNiIvPgogIDx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1ZSIg
TmFtZT0iaGVhZGluZyA3Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI5IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDgiLz4KICA8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRp
bmcgOSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIE5h
bWU9InRvYyAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIz
OSIgTmFtZT0idG9jIDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjM5IiBOYW1lPSJ0b2MgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iMzkiIE5hbWU9InRvYyA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9jIDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2MgNiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIE5hbWU9InRvYyA3Ii8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9jIDgiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2MgOSIvPgogIDx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzUiIFFGb3JtYXQ9InRydWUi
IE5hbWU9ImNhcHRpb24iLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjEwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9y
bWF0PSJ0cnVlIiBOYW1lPSJUaXRsZSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iMSIgTmFtZT0iRGVmYXVsdCBQYXJhZ3JhcGggRm9udCIvPgogIDx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMTEiIFNlbWlIaWRkZW49ImZhbHNlIgog
ICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9IlN1YnRpdGxlIi8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIyMiIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0i
U3Ryb25nIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIyMCIg
U2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1
ZSIgTmFtZT0iRW1waGFzaXMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjU5IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJUYWJsZSBHcmlkIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFVuaGlk
ZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iUGxhY2Vob2xkZXIgVGV4dCIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iTm8gU3BhY2luZyIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmciLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBMaXN0Ii8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MiIgU2VtaUhpZGRlbj0i
ZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgR3JpZCIvPgogIDx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIFNlbWlIaWRkZW49ImZh
bHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDEiLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAy
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3Qg
MSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0
IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY3IiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3Jp
ZCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdy
aWQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjkiIFNl
bWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBH
cmlkIDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcwIiBT
ZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJEYXJrIExp
c3QiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcxIiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBT
aGFkaW5nIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MiIg
U2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3Jm
dWwgTGlzdCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzMi
IFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9y
ZnVsIEdyaWQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYw
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdo
dCBTaGFkaW5nIEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIg
TmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNjIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0i
ZmFsc2UiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2VudCAxIi8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMiBBY2NlbnQg
MSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjUiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0
IDEgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJSZXZpc2lvbiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iMzQiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9Ikxpc3QgUGFyYWdyYXBoIi8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIyOSIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iUXVvdGUiLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjMwIiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJJ
bnRlbnNlIFF1b3RlIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSI2NiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0i
TWVkaXVtIExpc3QgMiBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNjciIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDEgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY4IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAyIEFjY2VudCAxIi8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMyBBY2NlbnQgMSIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzAiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkRhcmsgTGlzdCBBY2NlbnQg
MSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzEiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIFNo
YWRpbmcgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjcyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1l
PSJDb2xvcmZ1bCBMaXN0IEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSI3MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJm
YWxzZSIgTmFtZT0iQ29sb3JmdWwgR3JpZCBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVX
aGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmcgQWNjZW50IDIiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBTZW1pSGlkZGVuPSJmYWxzZSIK
ICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBMaXN0IEFjY2VudCAyIi8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MiIgU2VtaUhpZGRlbj0i
ZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgR3JpZCBBY2NlbnQg
MiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFk
aW5nIDEgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjY0IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1l
PSJNZWRpdW0gU2hhZGluZyAyIEFjY2VudCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI2NSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMSBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhp
ZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDIgQWNjZW50IDIiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY3IiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAxIEFjY2VudCAy
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQg
MiBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjkiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1l
ZGl1bSBHcmlkIDMgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjcwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJEYXJrIExpc3QgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjcxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9
ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5nIEFjY2VudCAyIi8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgTGlzdCBBY2NlbnQgMiIvPgogIDx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzMiIFNlbWlIaWRkZW49ImZh
bHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIEdyaWQgQWNjZW50
IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYwIiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBTaGFk
aW5nIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0i
TGlnaHQgTGlzdCBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNjIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2Ui
IE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9
ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMiBBY2NlbnQgMyIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjUiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDEgQWNj
ZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY2IiBT
ZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0g
TGlzdCAyIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2NyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTWVkaXVtIEdyaWQgMSBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNjgiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0i
ZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDIgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY5IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAzIEFjY2VudCAzIi8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MCIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iRGFyayBMaXN0IEFjY2VudCAzIi8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MSIgU2VtaUhpZGRlbj0i
ZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgU2hhZGluZyBB
Y2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzIi
IFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9y
ZnVsIExpc3QgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjczIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI2MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iTGlnaHQgU2hhZGluZyBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhp
ZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IExpc3QgQWNjZW50IDQiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYyIiBTZW1pSGlkZGVuPSJmYWxzZSIK
ICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBHcmlkIEFjY2VudCA0Ii8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MyIgU2VtaUhpZGRlbj0i
ZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMSBB
Y2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjQi
IFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1
bSBTaGFkaW5nIDIgQWNjZW50IDQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjY1IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJNZWRpdW0gTGlzdCAxIEFjY2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI2NiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5V
c2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMiBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjciIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDEgQWNjZW50IDQiLz4KICA8
dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY4IiBTZW1pSGlkZGVuPSJm
YWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAyIEFjY2Vu
dCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIgU2Vt
aUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdy
aWQgMyBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iNzAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9
IkRhcmsgTGlzdCBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2Ui
IE5hbWU9IkNvbG9yZnVsIFNoYWRpbmcgQWNjZW50IDQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBMaXN0IEFjY2VudCA0Ii8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgR3JpZCBBY2NlbnQgNCIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmcgQWNj
ZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBT
ZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBM
aXN0IEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSI2MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0i
TGlnaHQgR3JpZCBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNjMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2Ui
IE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDEgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAyIEFjY2VudCA1Ii8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NSIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMSBBY2NlbnQgNSIv
PgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIFNlbWlIaWRk
ZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDIg
QWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY3
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRp
dW0gR3JpZCAxIEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI2OCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIg
TmFtZT0iTWVkaXVtIEdyaWQgMiBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNjkiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDMgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5o
aWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJEYXJrIExpc3QgQWNjZW50IDUiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcxIiBTZW1pSGlkZGVuPSJmYWxzZSIK
ICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5nIEFjY2VudCA1
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MiIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgTGlz
dCBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NzMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNv
bG9yZnVsIEdyaWQgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjYwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJMaWdodCBTaGFkaW5nIEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tl
ZD0iZmFsc2UiIFByaW9yaXR5PSI2MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5V
c2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhp
ZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IEdyaWQgQWNjZW50IDYiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYzIiBTZW1pSGlkZGVuPSJmYWxzZSIK
ICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAxIEFjY2VudCA2
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NCIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRp
bmcgMiBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0
eT0iNjUiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9
Ik1lZGl1bSBMaXN0IDEgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjY2IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZh
bHNlIiBOYW1lPSJNZWRpdW0gTGlzdCAyIEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdo
ZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMSBBY2NlbnQgNiIvPgogIDx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjgiIFNlbWlIaWRkZW49ImZhbHNlIgog
ICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDIgQWNjZW50IDYiLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY5IiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAzIEFj
Y2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MCIg
U2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iRGFyayBM
aXN0IEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSI3MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0i
Q29sb3JmdWwgU2hhZGluZyBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iNzIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0i
ZmFsc2UiIE5hbWU9IkNvbG9yZnVsIExpc3QgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRpb24g
TG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjczIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRl
V2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2VudCA2Ii8+CiAgPHc6THNk
RXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIxOSIgU2VtaUhpZGRlbj0iZmFsc2Ui
CiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iU3VidGxlIEVt
cGhhc2lzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIyMSIg
U2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1
ZSIgTmFtZT0iSW50ZW5zZSBFbXBoYXNpcyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBQcmlvcml0eT0iMzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0i
ZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9IlN1YnRsZSBSZWZlcmVuY2UiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjMyIiBTZW1pSGlkZGVuPSJmYWxzZSIK
ICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJJbnRlbnNlIFJl
ZmVyZW5jZSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzMi
IFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRy
dWUiIE5hbWU9IkJvb2sgVGl0bGUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjM3IiBOYW1lPSJCaWJsaW9ncmFwaHkiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJUT0MgSGVhZGlu
ZyIvPgogPC93OkxhdGVudFN0eWxlcz4KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNv
IDEwXT4KPHN0eWxlPgogLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8KIHRhYmxlLk1zb05vcm1hbFRh
YmxlCgl7bXNvLXN0eWxlLW5hbWU6IlRhYmxlYXUgTm9ybWFsIjsKCW1zby10c3R5bGUtcm93YmFu
ZC1zaXplOjA7Cgltc28tdHN0eWxlLWNvbGJhbmQtc2l6ZTowOwoJbXNvLXN0eWxlLW5vc2hvdzp5
ZXM7Cgltc28tc3R5bGUtcHJpb3JpdHk6OTk7Cgltc28tc3R5bGUtcWZvcm1hdDp5ZXM7Cgltc28t
c3R5bGUtcGFyZW50OiIiOwoJbXNvLXBhZGRpbmctYWx0OjBjbSA1LjRwdCAwY20gNS40cHQ7Cglt
c28tcGFyYS1tYXJnaW4tdG9wOmF1dG87Cgltc28tcGFyYS1tYXJnaW4tcmlnaHQ6MGNtOwoJbXNv
LXBhcmEtbWFyZ2luLWJvdHRvbTphdXRvOwoJbXNvLXBhcmEtbWFyZ2luLWxlZnQ6MGNtOwoJdGV4
dC1hbGlnbjpqdXN0aWZ5OwoJbGluZS1oZWlnaHQ6MTUwJTsKCW1zby1wYWdpbmF0aW9uOndpZG93
LW9ycGhhbjsKCWZvbnQtc2l6ZToxMS4wcHQ7Cglmb250LWZhbWlseToiQ2FsaWJyaSIsInNhbnMt
c2VyaWYiOwoJbXNvLWFzY2lpLWZvbnQtZmFtaWx5OkNhbGlicmk7Cgltc28tYXNjaWktdGhlbWUt
Zm9udDptaW5vci1sYXRpbjsKCW1zby1mYXJlYXN0LWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9t
YW4iOwoJbXNvLWZhcmVhc3QtdGhlbWUtZm9udDptaW5vci1mYXJlYXN0OwoJbXNvLWhhbnNpLWZv
bnQtZmFtaWx5OkNhbGlicmk7Cgltc28taGFuc2ktdGhlbWUtZm9udDptaW5vci1sYXRpbjt9Cjwv
c3R5bGU+CjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPgogPHc6V29yZERvY3Vt
ZW50PgogIDx3OlZpZXc+Tm9ybWFsPC93OlZpZXc+CiAgPHc6Wm9vbT4wPC93Olpvb20+CiAgPHc6
VHJhY2tNb3Zlcy8+CiAgPHc6VHJhY2tGb3JtYXR0aW5nLz4KICA8dzpIeXBoZW5hdGlvblpvbmU+
MjE8L3c6SHlwaGVuYXRpb25ab25lPgogIDx3OlB1bmN0dWF0aW9uS2VybmluZy8+CiAgPHc6VmFs
aWRhdGVBZ2FpbnN0U2NoZW1hcy8+CiAgPHc6U2F2ZUlmWE1MSW52YWxpZD5mYWxzZTwvdzpTYXZl
SWZYTUxJbnZhbGlkPgogIDx3Oklnbm9yZU1peGVkQ29udGVudD5mYWxzZTwvdzpJZ25vcmVNaXhl
ZENvbnRlbnQ+CiAgPHc6QWx3YXlzU2hvd1BsYWNlaG9sZGVyVGV4dD5mYWxzZTwvdzpBbHdheXNT
aG93UGxhY2Vob2xkZXJUZXh0PgogIDx3OkRvTm90UHJvbW90ZVFGLz4KICA8dzpMaWRUaGVtZU90
aGVyPkZSPC93OkxpZFRoZW1lT3RoZXI+CiAgPHc6TGlkVGhlbWVBc2lhbj5YLU5PTkU8L3c6TGlk
VGhlbWVBc2lhbj4KICA8dzpMaWRUaGVtZUNvbXBsZXhTY3JpcHQ+QVItU0E8L3c6TGlkVGhlbWVD
b21wbGV4U2NyaXB0PgogIDx3OkNvbXBhdGliaWxpdHk+CiAgIDx3OkJyZWFrV3JhcHBlZFRhYmxl
cy8+CiAgIDx3OlNuYXBUb0dyaWRJbkNlbGwvPgogICA8dzpXcmFwVGV4dFdpdGhQdW5jdC8+CiAg
IDx3OlVzZUFzaWFuQnJlYWtSdWxlcy8+CiAgIDx3OkRvbnRHcm93QXV0b2ZpdC8+CiAgIDx3OlNw
bGl0UGdCcmVha0FuZFBhcmFNYXJrLz4KICAgPHc6RG9udFZlcnRBbGlnbkNlbGxXaXRoU3AvPgog
ICA8dzpEb250QnJlYWtDb25zdHJhaW5lZEZvcmNlZFRhYmxlcy8+CiAgIDx3OkRvbnRWZXJ0QWxp
Z25JblR4YngvPgogICA8dzpXb3JkMTFLZXJuaW5nUGFpcnMvPgogICA8dzpDYWNoZWRDb2xCYWxh
bmNlLz4KICA8L3c6Q29tcGF0aWJpbGl0eT4KICA8bTptYXRoUHI+CiAgIDxtOm1hdGhGb250IG06
dmFsPSJDYW1icmlhIE1hdGgiLz4KICAgPG06YnJrQmluIG06dmFsPSJiZWZvcmUiLz4KICAgPG06
YnJrQmluU3ViIG06dmFsPSImIzQ1Oy0iLz4KICAgPG06c21hbGxGcmFjIG06dmFsPSJvZmYiLz4K
ICAgPG06ZGlzcERlZi8+CiAgIDxtOmxNYXJnaW4gbTp2YWw9IjAiLz4KICAgPG06ck1hcmdpbiBt
OnZhbD0iMCIvPgogICA8bTpkZWZKYyBtOnZhbD0iY2VudGVyR3JvdXAiLz4KICAgPG06d3JhcElu
ZGVudCBtOnZhbD0iMTQ0MCIvPgogICA8bTppbnRMaW0gbTp2YWw9InN1YlN1cCIvPgogICA8bTpu
YXJ5TGltIG06dmFsPSJ1bmRPdnIiLz4KICA8L206bWF0aFByPjwvdzpXb3JkRG9jdW1lbnQ+Cjwv
eG1sPjwhW2VuZGlmXS0tPjxzcGFuIGRhdGEtbWNlLXN0eWxlPSJsaW5lLWhlaWdodDogMTUwJTsg
Zm9udC1mYW1pbHk6ICdUaW1lcyBOZXcgUm9tYW4nLCdzZXJpZic7IiBzdHlsZT0ibGluZS1oZWln
aHQ6IDE1MCU7IGZvbnQtZmFtaWx5OiAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDssJnF1b3Q7
c2VyaWYmcXVvdDs7IiBsYW5nPSJFTi1VUyI+d2hlbiB0aGVyZSBhcmUgbWVjaGFuaXNtcyBpbiBw
bGFjZSB0byBlc3RhYmxpc2gKcHJpdmFjeSBhbmQgdHJ1c3QgPC9zcGFuPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPgogPHc6TGF0ZW50U3R5bGVzIERlZkxvY2tlZFN0YXRlPSJmYWxzZSIgRGVmVW5o
aWRlV2hlblVzZWQ9InRydWUiCiAgRGVmU2VtaUhpZGRlbj0idHJ1ZSIgRGVmUUZvcm1hdD0iZmFs
c2UiIERlZlByaW9yaXR5PSI5OSIKICBMYXRlbnRTdHlsZUNvdW50PSIyNjciPgogIDx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iTm9ybWFsIi8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBTZW1pSGlkZGVuPSJm
YWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFk
aW5nIDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjkiIFFG
b3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVhZGluZyAzIi8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBRRm9ybWF0PSJ0cnVl
IiBOYW1lPSJoZWFkaW5nIDQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgNSIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iaGVh
ZGluZyA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI5IiBR
Rm9ybWF0PSJ0cnVlIiBOYW1lPSJoZWFkaW5nIDciLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjkiIFFGb3JtYXQ9InRydWUiIE5hbWU9ImhlYWRpbmcgOCIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iOSIgUUZvcm1hdD0idHJ1
ZSIgTmFtZT0iaGVhZGluZyA5Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSIzOSIgTmFtZT0idG9jIDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxz
ZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2MgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iMzkiIE5hbWU9InRvYyAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9jIDQiLz4KICA8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2MgNSIvPgogIDx3OkxzZEV4
Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIE5hbWU9InRvYyA2Ii8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzOSIgTmFtZT0idG9jIDciLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjM5IiBOYW1lPSJ0b2Mg
OCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIE5hbWU9
InRvYyA5Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzNSIg
UUZvcm1hdD0idHJ1ZSIgTmFtZT0iY2FwdGlvbiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iMTAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5hbWU9IlRpdGxlIi8+CiAgPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIxIiBOYW1lPSJEZWZhdWx0IFBhcmFncmFwaCBGb250
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIxMSIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFt
ZT0iU3VidGl0bGUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9
IjIyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0
PSJ0cnVlIiBOYW1lPSJTdHJvbmciLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjIwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJFbXBoYXNpcyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iNTkiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVu
VXNlZD0iZmFsc2UiIE5hbWU9IlRhYmxlIEdyaWQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJQbGFjZWhvbGRlciBUZXh0Ii8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIxIiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJO
byBTcGFjaW5nIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2
MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGln
aHQgU2hhZGluZyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ikxp
Z2h0IExpc3QiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYy
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdo
dCBHcmlkIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MyIg
U2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVt
IFNoYWRpbmcgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjQiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1l
ZGl1bSBTaGFkaW5nIDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjY1IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1l
PSJNZWRpdW0gTGlzdCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2NiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTWVkaXVtIExpc3QgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNjciIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9Ik1lZGl1bSBHcmlkIDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjY4IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJNZWRpdW0gR3JpZCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFBy
aW9yaXR5PSI2OSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIg
TmFtZT0iTWVkaXVtIEdyaWQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNzAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2Ui
IE5hbWU9IkRhcmsgTGlzdCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9IkNvbG9yZnVsIFNoYWRpbmciLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjcyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJDb2xvcmZ1bCBMaXN0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI3MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgTmFtZT0iQ29sb3JmdWwgR3JpZCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmcgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBMaXN0IEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgR3JpZCBBY2NlbnQgMSIvPgogIDx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIFNlbWlIaWRkZW49ImZhbHNl
IgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDEgQWNjZW50
IDEiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hh
ZGluZyAyIEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2NSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTWVkaXVtIExpc3QgMSBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZh
bHNlIiBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IlJldmlzaW9uIi8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzNCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iTGlzdCBQYXJhZ3Jh
cGgiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjI5IiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBO
YW1lPSJRdW90ZSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
MzAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9
InRydWUiIE5hbWU9IkludGVuc2UgUXVvdGUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjY2IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9
ImZhbHNlIiBOYW1lPSJNZWRpdW0gTGlzdCAyIEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9u
IExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlk
ZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMSBBY2NlbnQgMSIvPgogIDx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjgiIFNlbWlIaWRkZW49ImZhbHNl
IgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDIgQWNjZW50IDEi
Lz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY5IiBTZW1pSGlk
ZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAz
IEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3
MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iRGFy
ayBMaXN0IEFjY2VudCAxIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI3MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iQ29sb3JmdWwgU2hhZGluZyBBY2NlbnQgMSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNzIiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIExpc3QgQWNjZW50IDEiLz4KICA8dzpMc2RFeGNlcHRp
b24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjczIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5o
aWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBHcmlkIEFjY2VudCAxIi8+CiAgPHc6
THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MCIgU2VtaUhpZGRlbj0iZmFs
c2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgU2hhZGluZyBBY2NlbnQg
MiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjEiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IExpc3Qg
QWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYy
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdo
dCBHcmlkIEFjY2VudCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9y
aXR5PSI2MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFt
ZT0iTWVkaXVtIFNoYWRpbmcgMSBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9
ImZhbHNlIiBQcmlvcml0eT0iNjQiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNl
ZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDIgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY1IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAg
VW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gTGlzdCAxIEFjY2VudCAyIi8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NiIgU2VtaUhpZGRlbj0i
ZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMiBBY2Nl
bnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjciIFNl
bWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBH
cmlkIDEgQWNjZW50IDIiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjY4IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1l
PSJNZWRpdW0gR3JpZCAyIEFjY2VudCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSI2OSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJm
YWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMyBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVX
aGVuVXNlZD0iZmFsc2UiIE5hbWU9IkRhcmsgTGlzdCBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIFNoYWRpbmcgQWNjZW50IDIiLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcyIiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBMaXN0IEFj
Y2VudCAyIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MyIg
U2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3Jm
dWwgR3JpZCBBY2NlbnQgMiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlv
cml0eT0iNjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5h
bWU9IkxpZ2h0IFNoYWRpbmcgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjYxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9
ImZhbHNlIiBOYW1lPSJMaWdodCBMaXN0IEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdo
ZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgR3JpZCBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2Vw
dGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBV
bmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDEgQWNjZW50IDMiLz4K
ICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY0IiBTZW1pSGlkZGVu
PSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gU2hhZGluZyAy
IEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2
NSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVk
aXVtIExpc3QgMSBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNjYiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2Ui
IE5hbWU9Ik1lZGl1bSBMaXN0IDIgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2Vk
PSJmYWxzZSIgUHJpb3JpdHk9IjY3IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVz
ZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAxIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMiBBY2NlbnQgMyIvPgogIDx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjkiIFNlbWlIaWRkZW49ImZh
bHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDMgQWNjZW50
IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjcwIiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJEYXJrIExpc3Qg
QWNjZW50IDMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9Ijcx
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xv
cmZ1bCBTaGFkaW5nIEFjY2VudCAzIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI3MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgTmFtZT0iQ29sb3JmdWwgTGlzdCBBY2NlbnQgMyIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2Nr
ZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzMiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVu
VXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIEdyaWQgQWNjZW50IDMiLz4KICA8dzpMc2RFeGNl
cHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAg
VW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBTaGFkaW5nIEFjY2VudCA0Ii8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MSIgU2VtaUhpZGRlbj0i
ZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgTGlzdCBBY2NlbnQg
NCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjIiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IEdyaWQg
QWNjZW50IDQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYz
IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRp
dW0gU2hhZGluZyAxIEFjY2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSI2NCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMiBBY2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjUiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVX
aGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDEgQWNjZW50IDQiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY2IiBTZW1pSGlkZGVuPSJmYWxzZSIK
ICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gTGlzdCAyIEFjY2VudCA0Ii8+
CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2NyIgU2VtaUhpZGRl
bj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMSBB
Y2NlbnQgNCIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjgi
IFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1
bSBHcmlkIDIgQWNjZW50IDQiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJp
b3JpdHk9IjY5IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBO
YW1lPSJNZWRpdW0gR3JpZCAzIEFjY2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI3MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iRGFyayBMaXN0IEFjY2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdo
ZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgU2hhZGluZyBBY2NlbnQgNCIvPgogIDx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzIiIFNlbWlIaWRkZW49ImZhbHNl
IgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIExpc3QgQWNjZW50IDQi
Lz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjczIiBTZW1pSGlk
ZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBHcmlk
IEFjY2VudCA0Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2
MCIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGln
aHQgU2hhZGluZyBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQ
cmlvcml0eT0iNjEiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2Ui
IE5hbWU9IkxpZ2h0IExpc3QgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjYyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9
ImZhbHNlIiBOYW1lPSJMaWdodCBHcmlkIEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExv
Y2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdo
ZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIFNoYWRpbmcgMSBBY2NlbnQgNSIvPgogIDx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjQiIFNlbWlIaWRkZW49ImZhbHNl
IgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFkaW5nIDIgQWNjZW50
IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY1IiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gTGlz
dCAxIEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5
PSI2NiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0i
TWVkaXVtIExpc3QgMiBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNl
IiBQcmlvcml0eT0iNjciIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFs
c2UiIE5hbWU9Ik1lZGl1bSBHcmlkIDEgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9j
a2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY4IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hl
blVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAyIEFjY2VudCA1Ii8+CiAgPHc6THNkRXhj
ZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAg
IFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQgMyBBY2NlbnQgNSIvPgog
IDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzAiIFNlbWlIaWRkZW49
ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkRhcmsgTGlzdCBBY2NlbnQg
NSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzEiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIFNo
YWRpbmcgQWNjZW50IDUiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjcyIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1l
PSJDb2xvcmZ1bCBMaXN0IEFjY2VudCA1Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFs
c2UiIFByaW9yaXR5PSI3MyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJm
YWxzZSIgTmFtZT0iQ29sb3JmdWwgR3JpZCBBY2NlbnQgNSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjAiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVX
aGVuVXNlZD0iZmFsc2UiIE5hbWU9IkxpZ2h0IFNoYWRpbmcgQWNjZW50IDYiLz4KICA8dzpMc2RF
eGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjYxIiBTZW1pSGlkZGVuPSJmYWxzZSIK
ICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJMaWdodCBMaXN0IEFjY2VudCA2Ii8+CiAg
PHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2MiIgU2VtaUhpZGRlbj0i
ZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTGlnaHQgR3JpZCBBY2NlbnQg
NiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjMiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBTaGFk
aW5nIDEgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3Jp
dHk9IjY0IiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1l
PSJNZWRpdW0gU2hhZGluZyAyIEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0i
ZmFsc2UiIFByaW9yaXR5PSI2NSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2Vk
PSJmYWxzZSIgTmFtZT0iTWVkaXVtIExpc3QgMSBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2VwdGlv
biBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNjYiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhp
ZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1lZGl1bSBMaXN0IDIgQWNjZW50IDYiLz4KICA8dzpM
c2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjY3IiBTZW1pSGlkZGVuPSJmYWxz
ZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBOYW1lPSJNZWRpdW0gR3JpZCAxIEFjY2VudCA2
Ii8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI2OCIgU2VtaUhp
ZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iTWVkaXVtIEdyaWQg
MiBBY2NlbnQgNiIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0i
NjkiIFNlbWlIaWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9Ik1l
ZGl1bSBHcmlkIDMgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjcwIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBOYW1lPSJEYXJrIExpc3QgQWNjZW50IDYiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJm
YWxzZSIgUHJpb3JpdHk9IjcxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9
ImZhbHNlIiBOYW1lPSJDb2xvcmZ1bCBTaGFkaW5nIEFjY2VudCA2Ii8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSI3MiIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgTmFtZT0iQ29sb3JmdWwgTGlzdCBBY2NlbnQgNiIvPgogIDx3
OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iNzMiIFNlbWlIaWRkZW49ImZh
bHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIE5hbWU9IkNvbG9yZnVsIEdyaWQgQWNjZW50
IDYiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIgUHJpb3JpdHk9IjE5IiBTZW1p
SGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNlIiBRRm9ybWF0PSJ0cnVlIiBO
YW1lPSJTdWJ0bGUgRW1waGFzaXMiLz4KICA8dzpMc2RFeGNlcHRpb24gTG9ja2VkPSJmYWxzZSIg
UHJpb3JpdHk9IjIxIiBTZW1pSGlkZGVuPSJmYWxzZSIKICAgVW5oaWRlV2hlblVzZWQ9ImZhbHNl
IiBRRm9ybWF0PSJ0cnVlIiBOYW1lPSJJbnRlbnNlIEVtcGhhc2lzIi8+CiAgPHc6THNkRXhjZXB0
aW9uIExvY2tlZD0iZmFsc2UiIFByaW9yaXR5PSIzMSIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVu
aGlkZVdoZW5Vc2VkPSJmYWxzZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iU3VidGxlIFJlZmVyZW5j
ZSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzIiIFNlbWlI
aWRkZW49ImZhbHNlIgogICBVbmhpZGVXaGVuVXNlZD0iZmFsc2UiIFFGb3JtYXQ9InRydWUiIE5h
bWU9IkludGVuc2UgUmVmZXJlbmNlIi8+CiAgPHc6THNkRXhjZXB0aW9uIExvY2tlZD0iZmFsc2Ui
IFByaW9yaXR5PSIzMyIgU2VtaUhpZGRlbj0iZmFsc2UiCiAgIFVuaGlkZVdoZW5Vc2VkPSJmYWxz
ZSIgUUZvcm1hdD0idHJ1ZSIgTmFtZT0iQm9vayBUaXRsZSIvPgogIDx3OkxzZEV4Y2VwdGlvbiBM
b2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzciIE5hbWU9IkJpYmxpb2dyYXBoeSIvPgogIDx3Okxz
ZEV4Y2VwdGlvbiBMb2NrZWQ9ImZhbHNlIiBQcmlvcml0eT0iMzkiIFFGb3JtYXQ9InRydWUiIE5h
bWU9IlRPQyBIZWFkaW5nIi8+CiA8L3c6TGF0ZW50U3R5bGVzPgo8L3htbD48IVtlbmRpZl0tLT4u
PC9zcGFuPjxicj48YnI+U2VycmhpbmkgTW9oYW1tZWQ8YnI+PGJyPlN1biwgNiBBcHIgMjAxNCAy
MzozMDoxMSArMDAwMCDQvtGCIENocmlzdGlhbiBIdWl0ZW1hICZsdDtodWl0ZW1hQG1pY3Jvc29m
dC5jb20mZ3Q7Ojxicj4KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlci1sZWZ0OjFweCBzb2xpZCAj
MDg1N0E2OyBtYXJnaW46MTBweDsgcGFkZGluZzowIDAgMCAxMHB4OyI+Cgk8ZGl2IGlkPSIiPgoJ
CgoKCiAgICAKCgoKCgoKCgoKCQoJCgoKCQoJCgkKCQoJCgoJCgkKCgkKCQoKCgo8ZGl2IGNsYXNz
PSJqcy1oZWxwZXIganMtcmVhZG1zZy1tc2ciPgoJPHN0eWxlIHR5cGU9InRleHQvY3NzIj48L3N0
eWxlPgogCTxkaXY+CgkJPGJhc2UgdGFyZ2V0PSJfc2VsZiIgaHJlZj0iaHR0cHM6Ly9lLm1haWwu
cnUvIj4KCQkKCQkJPGRpdiBpZD0ic3R5bGVfMTM5NjgyNzA1MjAwMDAwMDAzMzhfQk9EWSI+Jmd0
OyBJIGFncmVlIHdpdGggdGhvc2Ugd2hvJ3ZlIHNhaWQgYSB0aHJlYXQgYW5hbHlzaXMgaXMgbmVl
ZGVkIGJlZm9yZTxicj4KJmd0OyBkZWNpZGluZyBhY2Nlc3MgaXMgbGltaXRlZCB0byBUTFMgb3Ig
b3RoZXIgc2VjdXJlIGFsdGVybmF0aXZlLjxicj4KPGJyPgpCdXQgd2UgaGF2ZSB0aGF0IHRocmVh
dCBhbmFseXNpcywgYW5kIHRoZSByZWNvbW1lbmRlZCBtaXRpZ2F0aW9uIGlzIHByZWNpc2VseSAi
ZW5jcnlwdCBldmVyeXRoaW5nLiIgVGhlICJwZXJ2YXNpdmUgbW9uaXRvcmluZyIgdGhyZWF0IGlz
IGFuYWx5emVkIGJ5IGEgbnVtYmVyIG9mIHBlcnBhc3MgZHJhZnRzLCBhbmQgU3RlcGhlbiBoYXMg
bWVyZWx5IGZvbGxvd2VkIHRoZSBjb25jbHVzaW9ucyBvZiB0aGF0IGFuYWx5c2lzLiBUaGVyZSBp
cyBubyBuZWVkIHRvIHJlcGVhdCB0aGF0IGFuYWx5c2lzIGZvciBlYWNoIGFuZCBldmVyeSB0b29s
IHRoYXQgdGhlIElFVEYgcHJvZHVjZXMsIGFuZCB0aGVyZSBpcyBpbmRlZWQgYSBuZWVkIGZvciB0
aGUgSUVURiBhcyBhIHdob2xlIHRvICJsZWFkIGJ5IGV4YW1wbGUuIjxicj4KPGJyPgotLSBDaHJp
c3RpYW4gSHVpdGVtYTxicj4KPGJyPgo8YnI+Cjxicj4KPC9kaXY+CgkJCQoJCQoJCTxiYXNlIHRh
cmdldD0iX3NlbGYiIGhyZWY9Imh0dHBzOi8vZS5tYWlsLnJ1LyI+Cgk8L2Rpdj4KCgkKPC9kaXY+
CgoKPC9kaXY+CjwvYmxvY2txdW90ZT4KPGJyPgo8YnI+0KEg0YPQstCw0LbQtdC90LjQtdC8LDxi
cj5tb2hhbW1lZCBzZXJyaGluaTxicj5zZXJyaGluaUBtYWlsLnJ1PGJyPjwvQk9EWT48L0hUTUw+
Cg==

----ALT--2TPB6QXn1396831215--


From nobody Sun Apr  6 18:06:36 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 258CB1A055D for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 18:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 Njwfq70VlFst for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 18:06:31 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.170]) by ietfa.amsl.com (Postfix) with ESMTP id 9ED391A05E5 for <ietf@ietf.org>; Sun,  6 Apr 2014 18:06:30 -0700 (PDT)
Received: from [195.245.230.131:61870] by server-10.bemta-3.messagelabs.com id F5/3E-16608-01AF1435; Mon, 07 Apr 2014 01:06:24 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-78.messagelabs.com!1396832784!30614184!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14673 invoked from network); 7 Apr 2014 01:06:24 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-12.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 7 Apr 2014 01:06:24 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Mon, 7 Apr 2014 02:06:23 +0100
From: <l.wood@surrey.ac.uk>
To: <l.wood@surrey.ac.uk>, <huitema@microsoft.com>, <ietf@ietf.org>
Date: Mon, 7 Apr 2014 02:05:43 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPT1jcTXDUfJOah0OH2ltCrxPwgZsEwa4AgAB5wwCAAATOIIAAE6e/gAAIaO4=
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEC6@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com>, <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>, <290E20B455C66743BE178C5C84F1240847E779EEC5@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEC5@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kmXGbKlqrovjXxatStZm-vQAxRA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 01:06:35 -0000

to enlarge on that:
http://www.ietf.org/proceedings/88/perpass.html
no charter

http://tools.ietf.org/wg/perpass
not found

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of l.wood@surrey.ac.uk [l.wood=
@surrey.ac.uk]
Sent: 07 April 2014 01:35
To: huitema@microsoft.com; ietf@ietf.org
Subject: RE: Security for various IETF services

https://datatracker.ietf.org/wg/perpass/
that's a lot of drafts.

and yet perpass is still not a WG with formal process and charter? Odd, tha=
t.

Knee-jerk reactions are not good things.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Christian Huitema [huitema@=
microsoft.com]
Sent: 07 April 2014 00:30
To: ietf@ietf.org
Subject: RE: Security for various IETF services

> I agree with those who've said a threat analysis is needed before
> deciding access is limited to TLS or other secure alternative.

But we have that threat analysis, and the recommended mitigation is precise=
ly "encrypt everything." The "pervasive monitoring" threat is analyzed by a=
 number of perpass drafts, and Stephen has merely followed the conclusions =
of that analysis. There is no need to repeat that analysis for each and eve=
ry tool that the IETF produces, and there is indeed a need for the IETF as =
a whole to "lead by example."

-- Christian Huitema




From nobody Sun Apr  6 23:42:39 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 309131A0680 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 23:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 3eM-_Ei9zmq8 for <ietf@ietfa.amsl.com>; Sun,  6 Apr 2014 23:42:31 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id A9FA91A02CC for <ietf@ietf.org>; Sun,  6 Apr 2014 23:42:31 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WX3GA-00059m-RX; Mon, 07 Apr 2014 06:42:24 +0000
Date: Mon, 07 Apr 2014 16:42:16 +1000
Message-ID: <m27g71prnb.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: <l.wood@surrey.ac.uk>
Subject: Re: Security for various IETF services
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEC5@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uxsQLxmAtTlkXsJh4TX0Rw3YFy0
Cc: huitema@microsoft.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 06:42:38 -0000

> Knee-jerk reactions are not good things.

QED


From nobody Mon Apr  7 00:37:58 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C24A21A0671 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 00:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 uLsD-ltTjrHy for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 00:37:49 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.148]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0C71A0552 for <ietf@ietf.org>; Mon,  7 Apr 2014 00:37:48 -0700 (PDT)
Received: from [85.158.136.51:47534] by server-12.bemta-5.messagelabs.com id 7D/F9-03824-6C552435; Mon, 07 Apr 2014 07:37:42 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-49.messagelabs.com!1396856262!17238182!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5891 invoked from network); 7 Apr 2014 07:37:42 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-12.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 7 Apr 2014 07:37:42 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Mon, 7 Apr 2014 08:37:41 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <ietf@ietf.org>
Date: Mon, 7 Apr 2014 08:37:40 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9RsE0XEUmRYhw7SIi2OaT5LB81ywAf9REP
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EEC7@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie>,<53417832.90405@cs.tcd.ie>
In-Reply-To: <53417832.90405@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lVsz0VntYZ-6U0xM-zx0EC_o-nM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 07:37:55 -0000

> There is a value in not making cleartext versions of services
> available though - I've personally seen a number of cases where
> http:// URLs were sent via mail with instructions to login at
> that URL using e.g. a datatracker or tools login. Yes, that ought
> not happen (https:// URLs should be sent), but it does happen
> and will so long as the http:// URLs work, and it'd be naive of
> us to assume that everyone sending out such mails would be aware
> that doing so isn't a good plan.

Your problem is with the servers, not the users.

that can be addressed by server-side redirection from http:// to https://
whever a login is required. Either a 301 permanent redirect, or a 401
unauthorised. A number of other services already do this.

Indeed, as an example
http://datatracker.ietf.org/accounts/login/?next=3D/
autoredirects to
https://datatracker.ietf.org/accounts/login/?next=3D/

lynx will report 'access without authorisation denied, retrying' ie 401

So the http urls still 'work' but the considered-necessary level
of security is imposed without requiring the users to know the
difference in the URL. Transparent 'upgrade', if you like. What
is sent in mail - http or https - does not matter.

Whether you can trust DNS (whatever happened to the trailing dot,
anyone? You'd think that would be widespread) is another matter...

I'm not convinced that https is required to all material throughout
once past login. Certainly not to public drafts or published rfcs/minutes.


> A couple of people expressed concern that this was a bit of a
> "blanket statement,"=20

well, yes. That's perpass in a nutshell. "OMG never again, this
was fine after 9/11 for foreigners, but not to Americans!" etc.

> Lastly, I'm heartbroken that Lloyd has sussed out my formerly
> secret plan to try to take over the world;-)=20

In retrospect, your plans have always failed on their own merits.

In retrospect.

But why take chances?

Lloyd Wood
http://about.me/lloydwood

Lack of past performance is no guarantee of future failure.
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stephen Farrell [stephen.fa=
rrell@cs.tcd.ie]
Sent: 06 April 2014 16:52
To: IETF-Discussion
Subject: Re: Security for various IETF services

As others have said, I think the questions posed have been
answered pretty much. I also got some good offlist wording
suggestions, the result of which is:

   "The IETF is committed to providing secure and private
   access to information via the web, mail, jabber and
   other services. While most data on IETF services is
   public, individual accesses to that data should be
   kept private to the extent possible.  However, as
   there are numerous existing tools that have been built
   that require access via cleartext, the IETF will
   continue to allow such access so as not to break such
   tooling. New services will however generally only be
   made available in ways that use security protocols
   such as TLS."

And just adding some stuff that's not been said before...

I agree that IETF services aren't the most sensitive in the
world, but think we all nonetheless win if we up the ante for
attackers of whatever kind when we reasonably can.

There is a value in not making cleartext versions of services
available though - I've personally seen a number of cases where
http:// URLs were sent via mail with instructions to login at
that URL using e.g. a datatracker or tools login. Yes, that ought
not happen (https:// URLs should be sent), but it does happen
and will so long as the http:// URLs work, and it'd be naive of
us to assume that everyone sending out such mails would be aware
that doing so isn't a good plan.

Using e.g. TLS for confidentiality also helps counter attacks
where cleartext HTTP cookies etc. are being used for monitoring
which has been shown to be the case. [1] IMO that's already a
good enough reason to turn on TLS or equivalent as much as
possible since most services will expose some similar
fingerprint when run in clear.

For those who expressed a wish for data origin authentication
over and above TLS server auth, that is already in place for
I-Ds. [2]

A couple of people expressed concern that this was a bit of a
"blanket statement," while that is true, the statement is not
absolutist, e.g. it says "generally" in the last sentence
which I think is about right.

A number of people made mechanism-specific points which were
mostly reasonable but of course we shouldn't put those in
this proposed iesg statement. One person said that e.g. this
statement should not be used to require client authentication
which is of course correct.

Someone mentioned having an IETF privacy policy for services
which sounds like a fine thing to me, and which is something
that I think Alissa has done a bit of work on in the past and
the IESG has chatted about resurrecting that. That is trickier
to get right though, and more work to get agreed, so not sure
if it'll happen.

Lastly, I'm heartbroken that Lloyd has sussed out my formerly
secret plan to try to take over the world;-) Ah well, I'll
just have to try again tomorrow.

S.

[1] http://www.bbc.co.uk/news/technology-25333663
[2] https://www.ietf.org/id-info/idsignatures.html


On 04/03/2014 05:21 PM, Stephen Farrell wrote:
>
> Hi all,
>
>>From time to time the issue of how to secure IETF services
> comes up e.g. whether to turn on TLS for some IETF web server
> or jabber or mail etc.
>
> The most recent such was a request to turn on HSTS [1] for
> the IETF web site, which I don't think we can do without
> breaking old tools etc. Nonetheless we would like to turn
> on things like TLS more often going forward as seemed to
> me to be the outcome of a long thread on here late last
> year.
>
> So, the IESG are considering the following as an IESG
> statement to offer some guidance about this:
>
> "The IETF are committed to providing secure and privacy
> friendly access to information via the web, mail, jabber
> and other services. While most (but not all) data on IETF
> services is public, nonetheless access to that data
> should use best practices for security and privacy.
> However, as there are numerous legacy tools that have been
> built that require access via cleartext, the IETF will
> continue to allow such access so as not to break such
> tooling. New services will however generally only be made
> available in ways that use security protocols such as
> TLS."
>
> If you have wordsmithing changes to suggest please just send
> those to me or the iesg. More substantive comments should go
> here I guess. I hope the only bit worth discussing (except
> for the few folks who would rather we do none of this;-)
> might be the last sentence.
>
> A few weeks after any discussion here dies down I'll put the
> resulting text on an IESG telechat for approval if that seems
> like the right thing to do.
>
> Thanks,
> S
>
> [1] https://tools.ietf.org/html/rfc6797
>
>
>
>


From nobody Mon Apr  7 01:17:46 2014
Return-Path: <Ray.Bellis@nominet.org.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3531A069C for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 01:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level: 
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 oKWqFLW6DaMB for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 01:17:39 -0700 (PDT)
Received: from mx1.nominet.org.uk (mx1.nominet.org.uk [213.248.242.48]) by ietfa.amsl.com (Postfix) with ESMTP id 9A96B1A0694 for <ietf@ietf.org>; Mon,  7 Apr 2014 01:17:39 -0700 (PDT)
DomainKey-Signature: s=main2.dk.nominet.selector; d=nominet.org.uk; c=nofws; q=dns;  h=X-IronPort-AV:X-IPAS-Result:Received:Received:From:To:CC: Subject:Thread-Topic:Thread-Index:Date:Message-ID: References:In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator:x-originating-ip: Content-Type:Content-ID:Content-Transfer-Encoding: MIME-Version; b=DvDphZTvw7ZZPrJfBX4Au7FP1C/0AILMUof+3Lwm55mdrJM8bZLtKjNm q1AqfI3Y15Iq+pZO062zUzeDQVVQuXYNbKFR/xfhKGkemaSMH749Qa6Ko xxCAQ3FzUCa9AufY6TGbfGn5ThjaMK3FPdEifFx0IBxo+q8Gi8P8R/goc Yrg7DZ9PFrMUo9x3ZGjEDCDcnXJpXZp/qPAglh7hFrzOX5x4VTOGWu3fQ QGPEnvJYIQ4AshTtBJSa36Q3BKaZ6;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nominet.org.uk; i=@nominet.org.uk; q=dns/txt; s=main2.dkim.nominet.selector; t=1396858654; x=1428394654; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=s6nKWmg3HgKChTY9D49mONWNKiym4L2xVgV7vWd3RTE=; b=NU3Y7vKo++0pxiOsOB6ppXK8X4spB+3q8jTcK17+9WdRVMAN5WMzmE0Y LrhToK4OpX1s4U2JoA45vsM0iJBwgPr4kOgscAwT3eRyEVv4NQXg9vSKY JPbu7KL5YYAvCjjGQgyV9hZ635yduLn6Azbu7yACkHRYnyodlD9vZreCd qq8zTmc/V2s0AfQXNZQa8hb6oV8iDJs0IQx6SmOzKJcM93q7vS8cPyDgm ctMeAOPPGKSdsmPZCRR5ny/TIpqIb;
X-IronPort-AV: E=Sophos;i="4.97,808,1389744000";  d="scan'208";a="9009085"
X-IPAS-Result: AhgFAPRdQlPV+MWR/2dsb2JhbABZgmUhgRLEGoEgFnSCJQEBAQECAVMmBQsCAQhGMiUCBA4Fh3EJA8tMF44+MweDJIEUBIkioXiDMIIr
Received: from wds-exc2.okna.nominet.org.uk ([213.248.197.145]) by mx1.nominet.org.uk with ESMTP; 07 Apr 2014 09:17:32 +0100
Received: from WDS-EXC1.okna.nominet.org.uk ([fe80::1593:1394:a91f:8f5f]) by wds-exc2.okna.nominet.org.uk ([fe80::7577:eaca:5241:25d4%17]) with mapi id 14.03.0123.003; Mon, 7 Apr 2014 09:17:32 +0100
From: Ray Bellis <Ray.Bellis@nominet.org.uk>
To: Thierry Moreau <thierry.moreau@connotech.com>
Subject: Re: An RFC7169 use case (!)
Thread-Topic: An RFC7169 use case (!)
Thread-Index: AQHPTpc9BIGzSTWnzkmOoNQWuqyh7psFxbEA
Date: Mon, 7 Apr 2014 08:17:31 +0000
Message-ID: <7FDD3E90-E4C4-46CB-A97F-DEE30E311405@nominet.org.uk>
References: <533C4624.50408@connotech.com>
In-Reply-To: <533C4624.50408@connotech.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.168.2.1]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <D18A9226A9281E449783F56233493D08@okna.nominet.org.uk>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nSIkcrM9uQlY-498805wCB1byMk
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 08:17:44 -0000

On 2 Apr 2014, at 18:17, Thierry Moreau <thierry.moreau@connotech.com> wrot=
e:

> It may me the first time that an April fool RFC is actually useful.

Not necessarily...

Geoff Huston and I wrote a draft a couple of years ago that repurposed the =
Evil Bit as an indicator that a packet has been through an address translat=
or.

The purpose was to act as a tie-breaker for those cases when Happy Eyeball =
algorithms couldn't otherwise distinguish between paths.

Ray


From nobody Mon Apr  7 01:25:08 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD70E1A0357 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 01:25:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 KbxAa4TbRhk1 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 01:25:01 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DB47F1A02C0 for <ietf@ietf.org>; Mon,  7 Apr 2014 01:25:01 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.147.234]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s378OhQg022661 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 7 Apr 2014 01:24:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1396859095; bh=SYmb8CamL42zt60yGHWW7WDIsd2sstCeLXHbIrG5vWo=; h=Date:To:From:Subject:In-Reply-To:References; b=Bui6Y5W5ILYadmS8MxpDbm/lUPp7BCtDSAjGvpIah4wBZb364bMdL+cbmSfL0sMtR JMS+1siRXn4LX3Zezv33ZRIg1aX+iszeEnyzmC1n2lpSApZ+BctgrQt7R0VTT+IB+Z x6hDP+UGa6f1DqdSs+2Gje/B6IdDhqj9lTwOQRsU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1396859095; i=@elandsys.com; bh=SYmb8CamL42zt60yGHWW7WDIsd2sstCeLXHbIrG5vWo=; h=Date:To:From:Subject:In-Reply-To:References; b=a/OfFErof7IYq3sGuAIYzWPT/TSuIGc5eEF0nkhAhRHz98SVIfifFDwk0NKSy1iRC WxMGBirbCrPx7wavbj78/UkS2iEIYQsPrMq8aUJv/Nb5jCSSxjGU83f6REbb3ciU8t vvbsBIH88qy0UX/EMG2nrDYrny8l5YDOBghN/AWs=
Message-Id: <6.2.5.6.2.20140406230005.07a30850@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 07 Apr 2014 01:08:00 -0700
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Security for various IETF services
In-Reply-To: <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com>
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3T_naLAmqCS7tXNuvSIiSNn-ywE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 08:25:07 -0000

At 16:08 06-04-2014, David Morris wrote:
>I don't object to making TLS/et al access available when it can be
>done at a moderate cost. But that is different than the implied
>statement that the intent is to require TLS for future service
>access.

I read the statement as being about not having recurring discussions 
about whether access to a future service will require secure 
access.  That's worthwhile.

https://datatracker.ietf.org has links to http://tools.ietf.org/  and 
http://www.ietf.org.  The "Search" link is to 
"www.google.com".  jabber.ietf.org is listed as having the following issues:

   - Certificate is not trusted
   - Server allows SSLv2, which is obsolete and insecure.
   - Server does not support the newest version, TLS 1.2.

The mail service does not support STARTTLS.

The current guideline for services is "server security based on 
best-practices and data sensitivity level".  There isn't any 
information about the best-practices for information which will be 
publicly available.  Some people have been accessing (IETF) publicly 
available information using clear-text protocols for many years.  The 
people do not consider "X is spying on you" as a reason to stop using 
those protocols.

A few months ago, a person (not in the IETF) posted the following comment:

   "I'd really like to know how secure this offer is before considering it...."

Regards,
S. Moonesamy 


From nobody Mon Apr  7 02:40:28 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94DC61A06CD; Mon,  7 Apr 2014 02:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.51
X-Spam-Level: 
X-Spam-Status: No, score=-9.51 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 e3yfl0wZm5F0; Mon,  7 Apr 2014 02:40:21 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id C72DA1A06CA; Mon,  7 Apr 2014 02:40:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6799; q=dns/txt; s=iport; t=1396863616; x=1398073216; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=ZmR/cPumouiWecs8kh5lRDpmAmdtK2n9DA/XArGul8I=; b=k4D0cqMthcjxSjhVJ6st29y/1JOSmID6bRzrfgcDKH+PcARi8bSR6lXl KQ8CIgIdxUeBZ4mZVIISaLMg0+j4UO7Jg1aC6L0JonhZKyt3BBrr5djtw w5SzpBd4JHVZTor9uG3ifVFDG07+GAe8jVWEzqCDuIrggcbxTr59Vao2O A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAAJyQlOQ/khN/2dsb2JhbABZgwaEHMEQgSEWdIIlAQEBAwEjVgULCQIOCgkeAwICDwI1EQYNAQUCAQEWh1cIjQ2cGIVZnD4XjiNOB4JvgUkEmFuGUYtugzE
X-IronPort-AV: E=Sophos;i="4.97,809,1389744000"; d="scan'208,217";a="9741947"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-3.cisco.com with ESMTP; 07 Apr 2014 09:40:14 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s379eD1Y011744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Apr 2014 09:40:14 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s379e6Z3028735; Mon, 7 Apr 2014 10:40:08 +0100 (BST)
Message-ID: <53427277.30707@cisco.com>
Date: Mon, 07 Apr 2014 10:40:07 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Tim Bray <tbray@textuality.com>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com>
In-Reply-To: <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------010907060306060300010901"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_v0pbSnpc6QdIodtN6CkdjZC5Ew
Cc: The IESG <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 09:40:26 -0000

This is a multi-part message in MIME format.
--------------010907060306060300010901
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

On 05/04/2014 18:29, Tim Bray wrote:
> On Sat, Apr 5, 2014 at 1:50 AM, Stewart Bryant (stbryant) 
> <stbryant@cisco.com <mailto:stbryant@cisco.com>> wrote:
>
> > Please confirm that "friendly" implies that the user gets to
> > choose the degree of security privacy that they consider
> > appropriate, and that their applications and devices are not
> > encumbered  with the overheads unless they choose to invoke
> > the privacy and security mechanisms.
>
> Here, I think, is a key issue.  I disagree with Stewart.  WHAT?!  How 
> can I possibly disagree with
> â€‹user choice?  Because, a huge majority of people
>
> (a) arenâ€™t aware that there is a choice to be made, and shouldnâ€™t need 
> to be
> (b) do not understand the technical issues surrounding the choice, and 
> shouldnâ€™t have to
> (c) do not understand the legal/policy issues surrounding the choice, 
> and shouldnâ€™t have to
>
> This includes both the people who use online services and the people 
> who offer them.  Thus, the only sane ethical position is to operate in 
> a mode that is private by default, because the consequences of a 
> negative failure (the user really didnâ€™t need privacy but got it 
> anyhow) are immensely less damaging than the consequences of a 
> positive failure (the user really needed privacy but didnâ€™t get it).
I could be persuaded towards "crypto by default", but I hear in these 
discussions "crypto as an exclusive mode", and I do not think that is an 
acceptable constraint on implementations.

Privacy and authentication always ends up taking CPU, memory and 
bandwidth, which in turn costs money, silicon, power, weight and 
complexity. If a specific application requires privacy and or 
authentication, then fine, but each case needs to be examined on its own 
merits. Now you may say "ah but we are getting so much better at the 
engineering that who cares about such things", to which I would point 
out that such thinking stunts our ability to build things that are 
orders of magnitude smaller, lighter, cheaper and more power efficient 
than we can conceive of oday.

So please, let's not react to the recent news on spying, by creating a 
security religion that in the end hurts us even more that the problem we 
are reacting to.

Stewart

--------------010907060306060300010901
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 05/04/2014 18:29, Tim Bray wrote:<br>
    </div>
    <blockquote
cite="mid:CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">On Sat, Apr 5, 2014 at 1:50 AM, Stewart Bryant
        (stbryant) &lt;<a moz-do-not-send="true"
          href="mailto:stbryant@cisco.com" target="_blank">stbryant@cisco.com</a>&gt;
        wrote:<br>
        <br>
        <div>&gt; Please confirm that "friendly" implies that the user
          gets to<br>
          &gt; choose the degree of security privacy that they consider<br>
          &gt; appropriate, and that their applications and devices are
          not<br>
          &gt; encumbered Â with the overheads unless they choose to
          invoke<br>
          &gt; the privacy and security mechanisms.</div>
        <div><br>
        </div>
        <div>Here, I think, is a key issue. Â I disagree with Stewart.
          Â WHAT?! Â How can I possibly disagree withÂ 
          <div class="gmail_default"
            style="font-size:small;display:inline">â€‹user choice?
            Â Because, a huge majority of people</div>
        </div>
        <div>
          <div class="gmail_default"
            style="font-size:small;display:inline"><br>
          </div>
        </div>
        <div>
          <div class="gmail_default"
            style="font-size:small;display:inline">(a) arenâ€™t aware that
            there is a choice to be made, and shouldnâ€™t need to be</div>
        </div>
        <div>
          <div class="gmail_default"
            style="font-size:small;display:inline">(b) do not understand
            the technical issues surrounding the choice, and shouldnâ€™t
            have to</div>
        </div>
        <div>
          <div class="gmail_default"
            style="font-size:small;display:inline">
            (c) do not understand the legal/policy issues surrounding
            the choice, and shouldnâ€™t have to</div>
        </div>
        <div>
          <div class="gmail_default"
            style="font-size:small;display:inline"><br>
          </div>
        </div>
        <div>
          <div class="gmail_default"
            style="font-size:small;display:inline">
            This includes both the people who use online services and
            the people who offer them. Â Thus, the only sane ethical
            position is to operate in a mode that is private by default,
            because the consequences of a negative failure (the user
            really didnâ€™t need privacy but got it anyhow) are immensely
            less damaging than the consequences of a positive failure
            (the user really needed privacy but didnâ€™t get it).</div>
        </div>
      </div>
    </blockquote>
    I could be persuaded towards "crypto by default", but I hear in
    these discussions "crypto as an exclusive mode", and I do not think
    that is an acceptable constraint on implementations.<br>
    <br>
    Privacy and authentication always ends up taking CPU, memory and
    bandwidth, which in turn costs money, silicon, power, weight and
    complexity. If a specific application requires privacy and or
    authentication, then fine, but each case needs to be examined on its
    own merits. Now you may say "ah but we are getting so much better at
    the engineering that who cares about such things", to which I would
    point out that such thinking stunts our ability to build things that
    are orders of magnitude smaller, lighter, cheaper and more power
    efficient than we can conceive of oday.<br>
    <br>
    So please, let's not react to the recent news on spying, by creating
    a security religion that in the end hurts us even more that the
    problem we are reacting to.<br>
    <br>
    Stewart<br>
  </body>
</html>

--------------010907060306060300010901--


From nobody Mon Apr  7 02:52:05 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 758C01A06E7 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 02:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level: 
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 GJ0GdJBnfHiJ for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 02:51:58 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id CA1C11A06DD for <ietf@ietf.org>; Mon,  7 Apr 2014 02:51:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=628; q=dns/txt; s=iport; t=1396864312; x=1398073912; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=J+KBjsgLZaRsiboMzoLGPB1P6Z4jBoymO4LpVkcs/6g=; b=OY7ItCgwWEKq9i5pAslgYEs4wiFUSzYPfMqwrnIc1WjsKn6wMx96t2hh eUvhcEwlYxtUuF4uTXD2rxIUXzmjOHcTYhb3BGbi2XFog9RHxbhH4c6Dg nCCnfdoUI02C0ZOHd/NON/TZcY8RLRJAEOdqxh8vbsjPgRFt0WWYJUG8j 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAF90QlOtJssU/2dsb2JhbABZDoJ4wh6DDoEiFnSCJQEBAQQ4QAEQCxgJFg8JAwIBAgFFBgEMAQcBAYd1rwOcQBeOI04HhDgBA5hbhlGLboJwQQ
X-IronPort-AV: E=Sophos;i="4.97,809,1389744000";  d="scan'208";a="9743912"
Received: from aer-core-3.cisco.com ([173.38.203.20]) by aer-iport-3.cisco.com with ESMTP; 07 Apr 2014 09:51:51 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s379pUJs008122 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Apr 2014 09:51:30 GMT
Received: from [127.0.0.1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s379pT7X029176; Mon, 7 Apr 2014 10:51:29 +0100 (BST)
Message-ID: <53427521.5070909@cisco.com>
Date: Mon, 07 Apr 2014 10:51:29 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, Lloyd Wood <L.Wood@surrey.ac.uk>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@[99.111.97.136]> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com> <m2mwg1voe3.wl%randy@psg.com>
In-Reply-To: <m2mwg1voe3.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mOif2L04NuKA9YmeTiRkiFw1uBE
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 09:52:02 -0000

On 04/04/2014 03:07, Randy Bush wrote:
>> "because we blew it way back when, by designing a completely insecure
>> and un-private internet"
>> That was not a mistake. That is what made adoption possible.
> this is not clear.  though, certainly, crypto would have had serious
> performance impact in the ealy '80s.  then again, if at 9600 baud, you
> can afford a bit of processing on the ends. :)
Randy

It is incorrect to assume that those considerations no longer apply. The
engineering and economics still apply, but to much smaller, cheaper,
lower power, and potentially far more ubiquitous, devices.

Stewart


From nobody Mon Apr  7 03:09:33 2014
Return-Path: <ietf@trammell.ch>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9A321A06EC; Mon,  7 Apr 2014 03:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 m97cu0Rpfxmm; Mon,  7 Apr 2014 03:09:27 -0700 (PDT)
Received: from trammell.ch (trammell1.nine.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id C80621A06E6; Mon,  7 Apr 2014 03:09:26 -0700 (PDT)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) by trammell.ch (Postfix) with ESMTPSA id E694E1A002D; Mon,  7 Apr 2014 12:09:19 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_1EAA7E2D-7FD1-4932-AA10-FF73214BAF86"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <53427277.30707@cisco.com>
Date: Mon, 7 Apr 2014 12:09:18 +0200
Message-Id: <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com>
To: stbryant@cisco.com
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XscN1zWVmhSX66FqMK8q8wSv3pE
Cc: Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 10:09:32 -0000

--Apple-Mail=_1EAA7E2D-7FD1-4932-AA10-FF73214BAF86
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


On 07 Apr 2014, at 11:40, Stewart Bryant <stbryant@cisco.com> wrote:

> On 05/04/2014 18:29, Tim Bray wrote:
>> On Sat, Apr 5, 2014 at 1:50 AM, Stewart Bryant (stbryant) =
<stbryant@cisco.com> wrote:
>>=20
>> > Please confirm that "friendly" implies that the user gets to
>> > choose the degree of security privacy that they consider
>> > appropriate, and that their applications and devices are not
>> > encumbered  with the overheads unless they choose to invoke
>> > the privacy and security mechanisms.
>>=20
>> Here, I think, is a key issue.  I disagree with Stewart.  WHAT?!  How =
can I possibly disagree with  =E2=80=8Buser choice?  Because, a huge =
majority of people
>>=20
>> (a) aren=E2=80=99t aware that there is a choice to be made, and =
shouldn=E2=80=99t need to be
>> (b) do not understand the technical issues surrounding the choice, =
and shouldn=E2=80=99t have to
>> (c) do not understand the legal/policy issues surrounding the choice, =
and shouldn=E2=80=99t have to
>>=20
>> This includes both the people who use online services and the people =
who offer them.  Thus, the only sane ethical position is to operate in a =
mode that is private by default, because the consequences of a negative =
failure (the user really didn=E2=80=99t need privacy but got it anyhow) =
are immensely less damaging than the consequences of a positive failure =
(the user really needed privacy but didn=E2=80=99t get it).
> I could be persuaded towards "crypto by default", but I hear in these =
discussions "crypto as an exclusive mode", and I do not think that is an =
acceptable constraint on implementations.

Then let's talk about crypto by default, which I think is a useful =
position in the case of IETF services, which is of course the subject of =
the thread. Here the specific threats posed by an adversary are:

(1) Leakage of browsing history. It may be tempting to presume that =
there is no value to the information that person X was interested in =
IETF documents w, y, and z, at time t, but that is indeed a presumption. =
We don't know X, and we can't presume to know why X might think their =
interest in the work of the IETF (or their presence at a particular =
point in time when they were accessing our services) is private, so we =
should make it as easy as possible to use TLS to at least limit the =
passively-observable information to that about the flow. And it doesn't =
get any easier than on-by-default. :)

(One could say that post-Snowden there is no reasonable practical =
presumption of privacy over HTTP, and that people using HTTP are =
knowingly serving up their browsing history to all observers. I have to =
agree with Tim on this point, though. As far as I am concerned this =
threat is justification enough to provide TLS by default for IETF web =
services. The details of how to do this to best "upgrade" initial =
landings without breaking access for deep-links and/or automated =
processes are just that, details of implementation.)

(2) Credential theft and subsequent impersonation: unencrypted access to =
the datatracker could allow eavesdroppers to impersonate anyone who logs =
in over HTTP. Yes, there are non-TLS ways to deal with this, though I'm =
not sure how universally reliable they are. (We also send mailing list =
credentials in plaintext at incredibly predictable times, so it would be =
relatively easy for someone to bulk-unsubscribe most of the IETF from =
most of our mailing lists, but that's unrelated to web services.)

I think the practical risk here is only of vandalism, creating a mess in =
the datatracker that it would take a fair amount of work to clean up. =
Any impersonation materially impacting the process would presumably =
(hopefully) be detected by the impersonated themselves. And the =
possibility of someone actually doing this certainly seems far-fetched, =
but so do so many of the things one reads in the press these days on =
this subject.

Protecting credential exchange by default via TLS for IETF web services =
requiring a login is a nice side-benefit to addressing (1) above, but if =
we think we have really good reasons for addressing (2) without =
addressing (1), there are ways to do so that are slightly =
computationally less expensive. It would take some effort to convince me =
that this is the correct tradeoff though.

(3) Injection/deletion/modification of RFC or draft content inline. =
There are already lots and lots and lots of places that mirror our =
documents anyway, so TLS won't help much here. The appropriate way to =
handle this is to sign the documents, not to provide protection on the =
wire. As I understand it this is an ongoing project anyway. Ignoring =
issues with the web PKI, TLS provides a practical bootstrap to this =
process by ensuring authenticity and integrity of public keys for =
verification retrieved from a known source.

There are probably a few others, but I think I've used all my Narten =
points for the week.

So there are specific reasons to do this, beyond simply increasing the =
cost of bulk collection by adding a few drops to the growing ocean of =
traffic encrypted on the wire.

> Privacy and authentication always ends up taking CPU, memory and =
bandwidth, which in turn costs money, silicon, power, weight and =
complexity. If a specific application requires privacy and or =
authentication, then fine, but each case needs to be examined on its own =
merits.

Yep. And I think in the case of the IETF services the real question =
comes down to "is the impact on 'restricted execution environments' =
worth the benefit (especially wrt threat 1) to default-on TLS for =
*.ietf.org?"

> Now you may say "ah but we are getting so much better at the =
engineering that who cares about such things", to which I would point =
out that such thinking stunts our ability to build things that are =
orders of magnitude smaller, lighter, cheaper and more power efficient =
than we can conceive of oday.

Agree completely.

Cheers,

Brian

--Apple-Mail=_1EAA7E2D-7FD1-4932-AA10-FF73214BAF86
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJTQnlOAAoJENt3nsOmbNJc0BgH/0xi8SRevQNOmGRrCE8ML3SJ
Bm/TD8LT9FuY8poRbBDyhTnz9K1dw7guNpZzgwaHcbP+cM1j752E+eoo/yuc9zk4
WgiptyyUuVmIgJ1sZYn1xSkfU11C0SOkwA6KFv8+7rtpIFBVLxMD27/kVspJx+fW
enEB9MaUuUKwFEewTGUE2DQOdLV+Ze5iGUnv2SEeA1GW99ytnL7lFRxZ4YFGjzTl
y213dmn/oDESaOENVJKBarc6YFnMShG6td6LCJJf1nIwU0Zs8GRSI4KOPG0YqQMS
5QpPFPDbl+SfgkcOXwayUCOqHSKcH/nCwdTPOBqqPKBZlY8z2pztHT3Fn/zWSc4=
=Ufw8
-----END PGP SIGNATURE-----

--Apple-Mail=_1EAA7E2D-7FD1-4932-AA10-FF73214BAF86--


From nobody Mon Apr  7 03:14:47 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 169A91A0392 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 03:14:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level: 
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 WQ_peY-Mglle for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 03:14:39 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id AFDFA1A0680 for <ietf@ietf.org>; Mon,  7 Apr 2014 03:14:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4133; q=dns/txt; s=iport; t=1396865673; x=1398075273; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=vQiQFWnpZ5l3RZGlp2OwTnVLIKmKGgzL3htI7fPsmnA=; b=iolXLs+uhDeNb+HZE9ixvpV3ZJba0+Lgh0q1ZykO7xYBB+t2+inUwXHp Zv6Xk3P5pgRTHNlbOVcEpobdLohxY34sZtdb9iunLFXcDM1txNJ0fLddJ hoUNbUsehBacCOK3GFZahyGepHbHHjzwfqDoD+NzR521s+JeQ9xs8xyeO s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhkFAAd6QlOtJssH/2dsb2JhbABZgwY7wWODDoEiFnSCJQEBAQQ4QBELGAkNAQgPCQMCAQIBRQYBDAgBARYEh1uuapw8F4lGhFoBAQFVEgGEJQSYW5I/gzGBagcX
X-IronPort-AV: E=Sophos;i="4.97,809,1389744000"; d="scan'208";a="13837051"
Received: from aer-core-2.cisco.com ([173.38.203.7]) by aer-iport-2.cisco.com with ESMTP; 07 Apr 2014 10:14:32 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s37AEKpu004410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Apr 2014 10:14:20 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s37AEJev000324; Mon, 7 Apr 2014 11:14:19 +0100 (BST)
Message-ID: <53427A7B.8020109@cisco.com>
Date: Mon, 07 Apr 2014 11:14:19 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, IETF-Discussion <ietf@ietf.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie>
In-Reply-To: <53417832.90405@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/C8lhz_kMFMI1em9Si3hD_2zl7Ho
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 10:14:45 -0000

On 06/04/2014 16:52, Stephen Farrell wrote:
> As others have said, I think the questions posed have been
> answered pretty much.
> I also got some good offlist wording
> suggestions, the result of which is:
>
>     "The IETF is committed to providing secure and private
>     access to information via the web, mail, jabber and
>     other services. While most data on IETF services is
>     public, individual accesses to that data should be
>     kept private to the extent possible.
That is an assumption that is the thin end of a wedge.
A threat  analysis is needed on a case by case basis.
> However, as
>     there are numerous existing tools that have been built
>     that require access via cleartext, the IETF will
>     continue to allow such access so as not to break such
>     tooling. New services will however generally only be
>     made available in ways that use security protocols
>     such as TLS."
It would be better to say: "The specification of new service
will each be required to include a threat analysis.
In each case a decision will be made about which,
if any, security protocols are needed to match the needs
of the application in the light of the threats."
>
> And just adding some stuff that's not been said before...
>
> I agree that IETF services aren't the most sensitive in the
> world, but think we all nonetheless win if we up the ante for
> attackers of whatever kind when we reasonably can.
... and we loose if we needlessly burn power, silicon, time,
bandwidth.... What I hope we are doing is best in class
engineering, and not simply reacting to the news of the
past few months.
>
> There is a value in not making cleartext versions of services
> available though - I've personally seen a number of cases where
> http:// URLs were sent via mail with instructions to login at
> that URL using e.g. a datatracker or tools login. Yes, that ought
> not happen (https:// URLs should be sent), but it does happen
> and will so long as the http:// URLs work, and it'd be naive of
> us to assume that everyone sending out such mails would be aware
> that doing so isn't a good plan.
This is a very sweeping statement, which is surely application
specific?
>
> Using e.g. TLS for confidentiality also helps counter attacks
> where cleartext HTTP cookies etc. are being used for monitoring
> which has been shown to be the case. [1] IMO that's already a
> good enough reason to turn on TLS or equivalent as much as
> possible since most services will expose some similar
> fingerprint when run in clear.
>
> For those who expressed a wish for data origin authentication
> over and above TLS server auth, that is already in place for
> I-Ds. [2]
>
> A couple of people expressed concern that this was a bit of a
> "blanket statement," while that is true, the statement is not
> absolutist, e.g. it says "generally" in the last sentence
> which I think is about right.
A question here concerns the degree to which the en clare
applications need to justify their case against an assumption
of encryption. Each application surely needs to be considered
on it's own merits. The text that you have is presumptive
of the outcome, which is surely not best engineering practice.
>
> A number of people made mechanism-specific points which were
> mostly reasonable but of course we shouldn't put those in
> this proposed iesg statement. One person said that e.g. this
> statement should not be used to require client authentication
> which is of course correct.
>
> Someone mentioned having an IETF privacy policy for services
> which sounds like a fine thing to me, and which is something
> that I think Alissa has done a bit of work on in the past and
> the IESG has chatted about resurrecting that. That is trickier
> to get right though, and more work to get agreed, so not sure
> if it'll happen.
>
> Lastly, I'm heartbroken that Lloyd has sussed out my formerly
> secret plan to try to take over the world;-) Ah well, I'll
> just have to try again tomorrow.
>
I am not sure that last para is called for.

- Stewart


From nobody Mon Apr  7 03:17:32 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B66EB1A038E for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 03:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level: 
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 r8-UptJUOy8w for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 03:17:26 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id CBC191A018D for <ietf@ietf.org>; Mon,  7 Apr 2014 03:17:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1339; q=dns/txt; s=iport; t=1396865840; x=1398075440; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=jWPcwz2ou0DZaHWhYqEiTFr8HUlzQjfsDUN4coI99XY=; b=b7mi5XYaMpk0hNv+R7GFjppQ+lXuzsHESfpebI2vzKcabmWvVBtCzGNh seMWBf1umzF+bU+Gr09E43TjVKzTbgoxhaxqUUY14ylhpRD8kaV+K3qLE sx+gmFd0IaL7JsL9QVNPJD3mzyv9XrkPeDtmtvTnjl1yxTjGvvzPh+55U U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFALJ6QlOQ/khM/2dsb2JhbABZgwY7xHGBIhZ0giUBAQEEODwEARALGAkWDwkDAgECAUUGAQwBBQIBAYd1Da5fnDwXjnEHhDgBA5hbkj+DMQ
X-IronPort-AV: E=Sophos;i="4.97,809,1389744000"; d="scan'208";a="14497462"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 07 Apr 2014 10:17:19 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s37AHIBh022480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Apr 2014 10:17:19 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s37AHHJ9000475; Mon, 7 Apr 2014 11:17:18 +0100 (BST)
Message-ID: <53427B2D.1010205@cisco.com>
Date: Mon, 07 Apr 2014 11:17:17 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Dick Franks <rwfranks@acm.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <CAKW6Ri5_Ty6rVsMTBKXEjC6r7Mg-o8pZoLQP+yJ4pBwqOF-nYw@mail.gmail.com> <533F0C7B.9090705@isdg.net> <CAKW6Ri699AuEOf-qf-iZ7vNdD7iEdF4uEnwX-HGB31EshJ_OXQ@mail.gmail.com> <53400355.7030807@isdg.net> <290E20B455C66743BE178C5C84F1240847E779EEBF@EXMB01CMS.surrey.ac.uk> <CAKW6Ri6jD4=pMdE_nsSnqyg6sKDT29_69_9jf=vfT2z6au7hNQ@mail.gmail.com> <5341D122.6010002@cs.tcd.ie>
In-Reply-To: <5341D122.6010002@cs.tcd.ie>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/K8MVquOYPKefywgzoAHFyMd-hbQ
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 10:17:30 -0000

On 06/04/2014 23:11, Stephen Farrell wrote:
>
> On 04/06/2014 08:27 PM, Dick Franks wrote:
>> On 5 April 2014 14:40, <l.wood@surrey.ac.uk> wrote:
>>
>>> "I didn't see anything that stood out. Are you referring to his why
>>> question?  Really?  It seems others answered why."
>>>
>>> they did not.
>>>
>>> Other noises off-stage are rrelevant
>> The author(s) of the proposal MUST provide the threat model for each
>> service and a reasoned argument why the proposed action mitigates the
>> identified threat or threats.
>>
>> Engineering best practice demands no less.
> I disagree. Asking for a threat model seems odd, since the
> proposed IESG statement isn't specific to a particular service
> and absent that you can't sensibly construct a threat model I
> think.
The request is surely that the specification of the application
include the threat model, which seems a very reasonable
requirement.
>
>> Transparent decision process demands no less.
> I have no idea what's apparently opaque.
>
>> Ignoring Lloyd Wood's question is not an option.
> LLoyd's questions were answered IMO.
I regret that I am not convinced they were.

Stewart
>
> S..
>
>
>
>>
>> Dick Franks
>>
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From nobody Mon Apr  7 03:21:14 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 600D01A06E4 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 03:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level: 
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 FjdgIHYeyKK4 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 03:21:06 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id 489D61A018D for <ietf@ietf.org>; Mon,  7 Apr 2014 03:21:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=939; q=dns/txt; s=iport; t=1396866061; x=1398075661; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=R2dHIyqPzd1y8Z5dFS/9SyqdulHBdTxOItQI7fu/5qQ=; b=fFiGdqZBK/KTNxTUWGApcSLaLPKUFSIjT12AnHjVSBVM3VqwXNFBLy0Z r9YzxGVqsT7ztHtu9WUel+bc/MFutm4v9Rz7uSPI9w7OTuYVZLlDZLzBG LuMsU/BKIZNlifUSjRSIoiWPAanljTCHXJnQQwZPXfkqrwcljq/wOwnV4 k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAGV7QlOQ/khL/2dsb2JhbABZgwbCHoMOgSIWdIIlAQEBAwE4QAYLCxgJFg8JAwIBAgFFBgEMCAEBh20Irm+cPBeOGV+EOAEDmFuSP4MxgWg
X-IronPort-AV: E=Sophos;i="4.97,809,1389744000";  d="scan'208";a="9749311"
Received: from ams-core-2.cisco.com ([144.254.72.75]) by aer-iport-3.cisco.com with ESMTP; 07 Apr 2014 10:21:00 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s37AKxo4012395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Apr 2014 10:21:00 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s37AKwRj000543; Mon, 7 Apr 2014 11:20:58 +0100 (BST)
Message-ID: <53427C0A.6050305@cisco.com>
Date: Mon, 07 Apr 2014 11:20:58 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Christian Huitema <huitema@microsoft.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com> <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
In-Reply-To: <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/P-QaFFiTY70kxKSJKUASo4agl54
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 10:21:11 -0000

On 07/04/2014 00:30, Christian Huitema wrote:
>> I agree with those who've said a threat analysis is needed before
>> deciding access is limited to TLS or other secure alternative.
> But we have that threat analysis, and the recommended mitigation is precisely "encrypt everything." The "pervasive monitoring" threat is analyzed by a number of perpass drafts, and Stephen has merely followed the conclusions of that analysis. There is no need to repeat that analysis for each and every tool that the IETF produces,
A (justified) reference to a base RFC is surely allowed, and the degree 
of commonality will surely determine whether it passes on the nod, or 
the covers get taken off for a closer investigation.

> and there is indeed a need for the IETF as a whole to "lead by example."
I am concerned that statement makes too broad an assumption about what 
an application is let alone what a threat mitigation is.

Stewart


From nobody Mon Apr  7 04:01:54 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3BF01A06E8; Mon,  7 Apr 2014 04:01:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Ru6vYAOzsGgF; Mon,  7 Apr 2014 04:01:49 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 7759D1A06CE; Mon,  7 Apr 2014 04:01:45 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id E3DFBBE49; Mon,  7 Apr 2014 12:01:38 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l11Vy4zuZaBD; Mon,  7 Apr 2014 12:01:38 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id AAF4BBE47; Mon,  7 Apr 2014 12:01:38 +0100 (IST)
Message-ID: <53428593.3020707@cs.tcd.ie>
Date: Mon, 07 Apr 2014 12:01:39 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian Trammell <ietf@trammell.ch>, stbryant@cisco.com
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch>
In-Reply-To: <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/89CLAL47qDbKP4s_DoGKlaQKJzc
Cc: Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 11:01:54 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Brian's response covers the issues very well I think. (Thanks.)

Just one thing to add...

On 04/07/2014 11:09 AM, Brian Trammell wrote:
> I think the practical risk here is only of vandalism, creating a
> mess in the datatracker that it would take a fair amount of work to
> clean up. Any impersonation materially impacting the process would 
> presumably (hopefully) be detected by the impersonated themselves. 
> And the possibility of someone actually doing this certainly seems 
> far-fetched, but so do so many of the things one reads in the
> press these days on this subject.

Given that password re-use over many services is common, there is
also the not at all insignificant risk that any credentials captured
could be abused elsewhere with more impact.

Yes, we ought move away from passwords if/when we ever find an
acceptably better solution, and yes, people ought manage their
passwords well, but neither are today's reality more's the pity.

S.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQEcBAEBAgAGBQJTQoWPAAoJEC88hzaAX42iAZ0H/AherdQFB54RMS/Puiwmk+qb
VzA+CbYotJKKrt6NHcQt9wi0SxkC9e9zIhtxUAMdHxxOd0X2KOu00tSJsYPEhoaz
CC7s3woqCiQp8vQj2FqE7fEKFIxohModpUlbKidLq/JdkJ3zW9/9tMGeffoGoFLg
j/B9tNr9vlCW3I+ZqyaKMUneEKwYB/YYyli/iEIzztsuGoWFu6xfSnOYQG1+Bdre
27ec95FMAkBNTF2x/KOZ+FN8o1i92XzzXUNRCwTmWn3iqmp9rJ3OQAst0lkDOzzv
k36rQx2r9uU1lpJProty2dQOTOf2GTmlE+QZ7BJC4g9O3Dn/Y+eMvHnWF1OwS8s=
=MXlA
-----END PGP SIGNATURE-----


From nobody Mon Apr  7 06:03:30 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D59E1A0702; Mon,  7 Apr 2014 06:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Ej0v3ILB1f6v; Mon,  7 Apr 2014 06:03:15 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id CEB2E1A06FB; Mon,  7 Apr 2014 06:03:15 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 69C271B80B7; Mon,  7 Apr 2014 06:03:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 4771B190043; Mon,  7 Apr 2014 06:03:10 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 7 Apr 2014 06:03:09 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <53428593.3020707@cs.tcd.ie>
Date: Mon, 7 Apr 2014 09:03:06 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D3IJ1o4PuFmmTYHY63TbTe5iYI4
Cc: IETF-Discussion <ietf@ietf.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 13:03:21 -0000

On Apr 7, 2014, at 7:01 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:
> Yes, we ought move away from passwords if/when we ever find an
> acceptably better solution, and yes, people ought manage their
> passwords well, but neither are today's reality more's the pity.

Perhaps it would be worth setting up support for client certs as a way =
to log in to IETF services.   If we won't start, why would someone else?


From nobody Mon Apr  7 07:02:50 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59D031A0424; Mon,  7 Apr 2014 07:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 GX0KxVvsF6Uv; Mon,  7 Apr 2014 07:02:41 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8FA3D1A070C; Mon,  7 Apr 2014 07:02:41 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WXA83-000IsB-NH; Mon, 07 Apr 2014 10:02:27 -0400
Date: Mon, 07 Apr 2014 10:02:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <ted.lemon@nominum.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Security for various IETF services
Message-ID: <DC23F34E807E77F8C4C095C3@JcK-HP8200.jck.com>
In-Reply-To: <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KoD-e-O3vzUuNqYBjMLe2wPtKJM
Cc: Stewart Bryant <stbryant@cisco.com>, Tim Bray <tbray@textuality.com>, IETF-Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 14:02:46 -0000

--On Monday, April 07, 2014 09:03 -0400 Ted Lemon
<ted.lemon@nominum.com> wrote:

> On Apr 7, 2014, at 7:01 AM, Stephen Farrell
> <stephen.farrell@cs.tcd.ie> wrote:
>> Yes, we ought move away from passwords if/when we ever find an
>> acceptably better solution, and yes, people ought manage their
>> passwords well, but neither are today's reality more's the
>> pity.
> 
> Perhaps it would be worth setting up support for client certs
> as a way to log in to IETF services.   If we won't start, why
> would someone else?

If we are really serious about promoting/ encouraging security,
I'd really like to see this as an option.  Not only would it be
responsive to Ted's question, but, if we made it available and
almost no one used it, it would give us a lot of information
about the course we are on.

As to the core proposal, unlike SM, I would like to see each new
application that someone proposes to be accessible through
"secure" means only discussed one at a time.  My fear of the
whole Prepass effort was that it would be used in "we approved
that, therefore we can and should do this without further
discussion" arguments.  I just thought it would take a few years
to get to that point.

Finally, if the IETF effectively declares HTTP obsolete for
anything but legacy applications, I think it is logically
necessary that we create an applicability statement deprecating
HTTP and approve it.  Anyone really, seriously, want to go there
or think that would could without losing all credibility in the
vendor and user communities?

   john





From nobody Mon Apr  7 07:13:21 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0249A1A0449; Mon,  7 Apr 2014 07:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 rXdsfa332s91; Mon,  7 Apr 2014 07:13:08 -0700 (PDT)
Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D4E691A0431; Mon,  7 Apr 2014 07:13:06 -0700 (PDT)
Received: by mail-ob0-f175.google.com with SMTP id uy5so6554377obc.6 for <multiple recipients>; Mon, 07 Apr 2014 07:13:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Fq/BhaxJcKqV4EvcFRn+n1dqRwPYCoRFSKSByrnhI5o=; b=aXDSRqgv0EjdWR9jIviTH27McM18dHATZrGwWmTf7SqPmQrWiuRtyuQ6YugDPJuM8h ubJo8cB0omcB3uCZOoHZ4kWdbRYT3G1CuWS3K3AfuvrVuZOZh5ucTbpjRKZLzSZVfxqG HF6W+Nj0qiO1cJWmknBkE+wddMeO+LW7ZZgq+a+yRSsSBi9ERVHukkk9tz0Mp3HCQlEb GK2PEG0XjQCPEbzjzloNh5MVcpUbH/wwsJP/2ihT0Qt8VJiPyv4c9CLQIBsRpqk0Vk+d Lxbh5vg612wD+a0+D6+OMKOok8oo1S9G1LUBI4cx6gKqwxUBRkFN3nJkr0lCoQIKlmTk 4sEg==
X-Received: by 10.60.159.36 with SMTP id wz4mr35506486oeb.30.1396879981218; Mon, 07 Apr 2014 07:13:01 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id dh8sm76912274oeb.10.2014.04.07.07.12.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Apr 2014 07:13:00 -0700 (PDT)
Message-ID: <5342B26B.5020704@gmail.com>
Date: Mon, 07 Apr 2014 09:12:59 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>,  Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com>
In-Reply-To: <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cpr6RGF2CPWzz_wVv7HC0UxNCgQ
Cc: Stewart Bryant <stbryant@cisco.com>, Tim Bray <tbray@textuality.com>, IETF-Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 14:13:14 -0000

On 04/07/2014 08:03 AM, Ted Lemon wrote:
> On Apr 7, 2014, at 7:01 AM, Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>> Yes, we ought move away from passwords if/when we ever find an
>> acceptably better solution, and yes, people ought manage their
>> passwords well, but neither are today's reality more's the pity.
> Perhaps it would be worth setting up support for client certs as a way to log in to IETF services.   If we won't start, why would someone else?

(Speaking as 1/15th, but only 1/15th, of the IESG that's asking for 
community input on this topic)

For me, "If we won't start, why would someone else?" was a significant 
consideration. I'm not locked in on any particular path, but I thought 
it was useful to ask about this was that if the IETF can't make an 
improved security environment work, that's not a good sign 
(http://en.wikipedia.org/wiki/Eating_your_own_dog_food).

We can spin up new working groups to address problems we encounter. Most 
communities seeking to improve their security environment can't do that.

So, from my own perspective, on-by-default would be sufficient to find 
out what I'd like to find out ... but I'd love to find out at least part 
of what we'd like to know, in a post-Snowdon world.

We could find out something, without making Stewart run a 
state-of-the-art secure environment on his IoT device to FTP Internet 
Drafts.

Spencer


From nobody Mon Apr  7 07:25:35 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B42A41A079F; Mon,  7 Apr 2014 07:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.511
X-Spam-Level: 
X-Spam-Status: No, score=-9.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 J8Kg5ie3T83n; Mon,  7 Apr 2014 07:25:23 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4972E1A045A; Mon,  7 Apr 2014 07:25:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=565; q=dns/txt; s=iport; t=1396880713; x=1398090313; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ZL+MmQ/hUbZq4qK32Im00lJLNdUF0LkYFgeXjtBYs9k=; b=QBja5QVFaeCwXtgbB2VVnCZt0mxtb4ky1m63FhulEumLVLGGLoc3u09q gu/+ktSE2gf1Wups052ZXUtDYjHRWKXy/jjybVJrRc77WVhcvecVtgLTT dl892WJMu1AALfrFNzBRIC2JGNP8gk7grejW9eCqusWN1Eek0/8XV/Gbc o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFAGG0QlOtJssG/2dsb2JhbABZgwbCHoMOgSIWdIIlAQEBBDhAARALGAkWDwkDAgECAUUGAQwBBwEBh3WvL5wlF45xB4Q4AQOYW5I/gzE
X-IronPort-AV: E=Sophos;i="4.97,810,1389744000"; d="scan'208";a="14536419"
Received: from aer-core-1.cisco.com ([173.38.203.6]) by aer-iport-1.cisco.com with ESMTP; 07 Apr 2014 14:25:12 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s37EP1GI019265 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Apr 2014 14:25:01 GMT
Received: from STBRYANT-M-R010.CISCO.COM (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s37EOvhF015251; Mon, 7 Apr 2014 15:24:58 +0100 (BST)
Message-ID: <5342B539.6030604@cisco.com>
Date: Mon, 07 Apr 2014 15:24:57 +0100
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Ted Lemon <ted.lemon@nominum.com>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <DC23F34E807E77F8C4C095C3@JcK-HP8200.jck.com>
In-Reply-To: <DC23F34E807E77F8C4C095C3@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2ywhbjAEcKojRiSWkwm7-rFGgDA
Cc: Tim Bray <tbray@textuality.com>, IETF-Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 14:25:29 -0000

On 07/04/2014 15:02, John C Klensin wrote:
> As to the core proposal, unlike SM, I would like to see each new 
> application that someone proposes to be accessible through "secure" 
> means only discussed one at a time.
I concur with John.
> My fear of the whole Prepass effort was that it would be used in "we 
> approved that, therefore we can and should do this without further 
> discussion" arguments. I just thought it would take a few years to get 
> to that point.
That was the root of my object to the publication of the Attack RFC.

- Stewart


From nobody Mon Apr  7 07:57:07 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C98AD1A0786; Mon,  7 Apr 2014 07:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 9m28uXTvjadM; Mon,  7 Apr 2014 07:57:01 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id A663F1A0797; Mon,  7 Apr 2014 07:56:06 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 175F51B80C2; Mon,  7 Apr 2014 07:56:01 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id EA7DD190043; Mon,  7 Apr 2014 07:56:00 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 7 Apr 2014 07:56:00 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5342B26B.5020704@gmail.com>
Date: Mon, 7 Apr 2014 10:55:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <4C322461-8FF5-4376-92AE-27DCF7A45720@nominum.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iJ2ZiYNnxKcPzdTESVHAl8OMcmY
Cc: IETF-Discussion <ietf@ietf.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 14:57:06 -0000

On Apr 7, 2014, at 10:12 AM, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:
> We could find out something, without making Stewart run a =
state-of-the-art secure environment on his IoT device to FTP Internet =
Drafts.

Well, e.g. allowing client certs for authentication without requiring =
them would certainly be interesting.   And we certainly should make sure =
that authentication credentials are never accidentally sent in the =
clear=97the web server shouldn't even propose authentication other than =
over a secure link.   Not sure we can do that with FTP.


From nobody Mon Apr  7 08:05:30 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C61B1A0791; Mon,  7 Apr 2014 08:05:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 BSx1FrIgJ0DR; Mon,  7 Apr 2014 08:05:15 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.139]) by ietfa.amsl.com (Postfix) with ESMTP id B3E0B1A0799; Mon,  7 Apr 2014 08:05:05 -0700 (PDT)
Received: from [85.158.136.51:65470] by server-3.bemta-5.messagelabs.com id 03/8B-28132-99EB2435; Mon, 07 Apr 2014 15:04:57 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-49.messagelabs.com!1396883096!21372619!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 26009 invoked from network); 7 Apr 2014 15:04:56 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-4.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 7 Apr 2014 15:04:56 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Mon, 7 Apr 2014 16:04:56 +0100
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <john-ietf@jck.com>
Date: Mon, 7 Apr 2014 16:04:55 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9SbUlEL+eMK3RSTFK2HNH59Dqu9wABCvVs
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EECA@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <DC23F34E807E77F8C4C095C3@JcK-HP8200.jck.com>,<5342B539.6030604@cisco.com>
In-Reply-To: <5342B539.6030604@cisco.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UmYdnd6CYVWUnXIC78bnNHwmUsk
Cc: ietf@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 15:05:23 -0000

once you hand security the keys to your organisation, it's no longer your o=
rganisation.

I am unsurprised by the increasing speed of security moves here (really, se=
curity
policy matters; policy is easy to push. governments do it all the time) and
the increasing slowness of everything else. (it's been twenty years since
RFC1323bis kicked off. Don't hold your breath.)

Lloyd Wood
http://sat-net.com/L.Wood/dtn

I was right in warning about DTN. Seems I''m right in warning about this. r=
ight?
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant [stbryant@ci=
sco.com]
Sent: 07 April 2014 15:24
To: John C Klensin; Ted Lemon; Stephen Farrell
Cc: Tim Bray; IETF-Discussion; The IESG
Subject: Re: Security for various IETF services

On 07/04/2014 15:02, John C Klensin wrote:
> As to the core proposal, unlike SM, I would like to see each new
> application that someone proposes to be accessible through "secure"
> means only discussed one at a time.
I concur with John.
> My fear of the whole Prepass effort was that it would be used in "we
> approved that, therefore we can and should do this without further
> discussion" arguments. I just thought it would take a few years to get
> to that point.
That was the root of my object to the publication of the Attack RFC.

- Stewart


From nobody Mon Apr  7 12:14:27 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54EE41A03EA for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 12:14:26 -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, SPF_PASS=-0.001] autolearn=ham
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 wy3hLxURTcW8 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 12:14:21 -0700 (PDT)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4F7EA1A07F7 for <ietf@ietf.org>; Mon,  7 Apr 2014 12:14:21 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id a41so6304393yho.32 for <ietf@ietf.org>; Mon, 07 Apr 2014 12:14:15 -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:content-type; bh=peymF8RoiAOHn2euN54CBCb+G8BCasWJjFNzvvUr6Dw=; b=Ols5dIiB8Z6En7OvD6YGggbKBtyF8b3Gt53HuBh1IZVaTwGgEjhLmkYDuEMH+T0y49 utMqzJPbwYJii/ShL4Etqbjdl/Hvh918Y/epz2JUvli6ZgWXkmlgfDL9lOWgQA7KF4s8 d2DkHejbjgJgO2NjNQhRorDlU7ksUY8n6b50O7TXlD8warMfHFL1UTs/zxPWVxSHWNJj U3aX+4DJ6DTJ2igwV4MzZXARd/LVS5rMPHNrwZFtXY0/xbXydLKL54zxLhXpammfeacX JL+NSiCrM/0J7hqPCkSQo2qfxkViwrKi24SjDbw5vjM1lCOYvScWGOyEayprp1U+gnh7 MOwQ==
MIME-Version: 1.0
X-Received: by 10.236.199.212 with SMTP id x60mr8439904yhn.90.1396898055418; Mon, 07 Apr 2014 12:14:15 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Mon, 7 Apr 2014 12:14:15 -0700 (PDT)
In-Reply-To: <94F8DB7E-0803-450E-8D99-02A4F3DF67C8@iab.org>
References: <CAOW+2dukS-Zye-T9NcWnstSmydpG4YaT6bW_CKh-KYhJQfasUA@mail.gmail.com> <02364CCE-9122-4EC0-A2D8-16C3FE16245F@isoc.org> <94F8DB7E-0803-450E-8D99-02A4F3DF67C8@iab.org>
Date: Mon, 7 Apr 2014 20:14:15 +0100
Message-ID: <CADnDZ88g4GQKZQwJYYAW4iozQ3gbGHtYu6SeH8njiytX5rBkhA@mail.gmail.com>
Subject: Re: Comments from the IAB on NISTIR 7977
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec52c62236179d304f678ac88
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RFZgu6CEtpMqHn5EG4bTWavni3A
Cc: IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 19:14:26 -0000

--bcaec52c62236179d304f678ac88
Content-Type: text/plain; charset=ISO-8859-1

Just need to clarify that the word 'public' in your statement means the US
public and not all regions/world public. IMO the statement is for only one
region not the total internet regions, but can be related to other
regions. Thanks.

AB

On Monday, April 7, 2014, IAB Chair wrote:

> Today, the IAB sent comments to the US National Institute for Standards
> and Technology (NIST) in the matter of the draft NISTIR 7977 (NIST
> Cryptographic Standards and Guidelines Development Process).  In the
> statement, the IAB supports transparency and openness, encouraging NIST to
> make improvements for not only Federal Information Processing Standards,
> but also Recommendations and Special Publications.
>
> The Draft NISTIR 7977 is available from the NIST website:
> http://csrc.nist.gov/publications/drafts/nistir-7977/nistir_7977_draft.pdf
>
> The IAB statement is available from the IAB website:
> http://www.iab.org/wp-content/IAB-uploads/2014/04/IAB-NIST7977-20140407.pdf
>
> On behalf of the IAB,
> Russ Housley
> IAB Chair
>
>

--bcaec52c62236179d304f678ac88
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Just need to clarify that the word &#39;public&#39;=A0in your statement mea=
ns the=A0US public and=A0not all regions/world public. IMO the statement is=
 for only one region not the total internet regions, but can be related to =
other regions.=A0Thanks.=A0<div>
<br></div><div>AB<br><br>On Monday, April 7, 2014, IAB Chair  wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">Today, the IAB sent comments to the US National=
 Institute for Standards and Technology (NIST) in the matter of the draft N=
ISTIR 7977 (NIST Cryptographic Standards and Guidelines Development Process=
). =A0In the statement, the IAB supports transparency and openness, encoura=
ging NIST to make improvements for not only Federal Information Processing =
Standards, but also Recommendations and Special Publications.<br>

<br>
The Draft NISTIR 7977 is available from the NIST website: <a href=3D"http:/=
/csrc.nist.gov/publications/drafts/nistir-7977/nistir_7977_draft.pdf" targe=
t=3D"_blank">http://csrc.nist.gov/publications/drafts/nistir-7977/nistir_79=
77_draft.pdf</a><br>

<br>
The IAB statement is available from the IAB website: <a href=3D"http://www.=
iab.org/wp-content/IAB-uploads/2014/04/IAB-NIST7977-20140407.pdf" target=3D=
"_blank">http://www.iab.org/wp-content/IAB-uploads/2014/04/IAB-NIST7977-201=
40407.pdf</a><br>

<br>
On behalf of the IAB,<br>
Russ Housley<br>
IAB Chair<br>
<br>
</blockquote></div>

--bcaec52c62236179d304f678ac88--


From nobody Mon Apr  7 12:51:31 2014
Return-Path: <matthew.kaufman@skype.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1953B1A0237 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 12:51:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
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 lhAZZuvMLjiq for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 12:51:24 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0142.outbound.protection.outlook.com [207.46.163.142]) by ietfa.amsl.com (Postfix) with ESMTP id D66901A0257 for <ietf@ietf.org>; Mon,  7 Apr 2014 12:51:23 -0700 (PDT)
Received: from BY2PR03CA032.namprd03.prod.outlook.com (10.242.234.153) by BY2PR03MB025.namprd03.prod.outlook.com (10.255.240.39) with Microsoft SMTP Server (TLS) id 15.0.913.9; Mon, 7 Apr 2014 19:51:16 +0000
Received: from BN1AFFO11FD032.protection.gbl (2a01:111:f400:7c10::164) by BY2PR03CA032.outlook.office365.com (2a01:111:e400:2c2c::25) with Microsoft SMTP Server (TLS) id 15.0.908.10 via Frontend Transport; Mon, 7 Apr 2014 19:51:16 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1AFFO11FD032.mail.protection.outlook.com (10.58.52.186) with Microsoft SMTP Server (TLS) id 15.0.918.6 via Frontend Transport; Mon, 7 Apr 2014 19:51:15 +0000
Received: from TK5EX14MBXC298.redmond.corp.microsoft.com ([169.254.1.124]) by TK5EX14HUBC107.redmond.corp.microsoft.com ([157.54.80.67]) with mapi id 14.03.0181.007; Mon, 7 Apr 2014 19:50:35 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: Christian Huitema <huitema@microsoft.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPT1jXle3ChO4j00Wi4jXF9jNZyZsEwa4AgAB5wwCAAAYrgIABTx3Q
Date: Mon, 7 Apr 2014 19:50:34 +0000
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A484504B5176@TK5EX14MBXC298.redmond.corp.microsoft.com>
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com> <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
In-Reply-To: <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.37]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: =?us-ascii?Q?CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; ?= =?us-ascii?Q?SFS:(10009001)(6009001)(438001)(199002)(377454003)(189002)(5?= =?us-ascii?Q?1704005)(50986001)(49866001)(20776003)(98676001)(95666003)(2?= =?us-ascii?Q?3726002)(54316002)(99396002)(94316002)(84676001)(33656001)(8?= =?us-ascii?Q?1542001)(79102001)(92726001)(93136001)(97186001)(6806004)(86?= =?us-ascii?Q?362001)(90146001)(85306002)(46406003)(63696002)(76796001)(87?= =?us-ascii?Q?936001)(47776003)(1511001)(2009001)(97336001)(44976005)(9494?= =?us-ascii?Q?6001)(97736001)(77096001)(54356001)(87266001)(77982001)(5584?= =?us-ascii?Q?6006)(83322001)(81686001)(19580395003)(80976001)(65816001)(5?= =?us-ascii?Q?6816005)(19580405001)(31966008)(74662001)(74502001)(74366001?= =?us-ascii?Q?)(74706001)(81816001)(92566001)(47446002)(80022001)(66066001?= =?us-ascii?Q?)(50466002)(74876001)(53806001)(81342001)(97756001)(47976001?= =?us-ascii?Q?)(47736001)(69226001)(93516002)(4396001)(76786001)(56776001)?= =?us-ascii?Q?(46102001)(85852003)(2656002)(76482001)(59766001)(95416001)(?= =?us-ascii?Q?83072002);DIR:OUT;SFP:1101;SCL:1;SRVR:BY2PR03MB025;H:mail.mi?= =?us-ascii?Q?crosoft.com;FPR:A03BF4DF.AD34D7D9.7DF03773.84E6A100.20310;ML?= =?us-ascii?Q?V:sfv;PTR:InfoDomainNonexistent;A:1;MX:1;LANG:en;?=
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0174BD4BDA
Received-SPF: Pass (: domain of skype.net designates 131.107.125.37 as permitted sender) receiver=; client-ip=131.107.125.37; helo=mail.microsoft.com;
X-OriginatorOrg: skype.net
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rBZtbF2I7xW3NnmhS33_0hz76rw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 19:51:29 -0000

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Christian Huitema
> Sent: Sunday, April 6, 2014 4:30 PM
> To: ietf@ietf.org
> Subject: RE: Security for various IETF services
>=20
> > I agree with those who've said a threat analysis is needed before
> > deciding access is limited to TLS or other secure alternative.
>=20
> But we have that threat analysis, and the recommended mitigation is
> precisely "encrypt everything." The "pervasive monitoring" threat is anal=
yzed
> by a number of perpass drafts, and Stephen has merely followed the
> conclusions of that analysis. There is no need to repeat that analysis fo=
r each
> and every tool that the IETF produces, and there is indeed a need for the
> IETF as a whole to "lead by example."

I've been following this thread with some amusement, as it was clear that w=
hen the perpass draft took its unusual journey from personal draft submissi=
on to BCP the fallout would include things like an immediate call for all I=
ETF services to be encrypted. At the same time, there are an equally well k=
nown number of attacks against TCP itself that make TCP the wrong substrate=
 upon which to build "secure" communication channels. (Just a couple of wel=
l-known examples: the ease of session hijacking of established connection a=
nd SYN flood attacks against well-known servers, both of which lead to deni=
al of service and potentially forcing the user to downgrade to an alternati=
ve channel for obtaining the information).

If the same level of urgency were shown towards a viable, and secure, repla=
cement for TCP itself, then the calls for secure-only access to IETF servic=
es might make sense. Instead, it feels a lot like requiring stronger deadbo=
lts on glass doors.

Matthew Kaufman


From nobody Mon Apr  7 13:11:50 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C659C1A026E for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 13:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.343
X-Spam-Level: **
X-Spam-Status: No, score=2.343 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 JbkINjVpySoY for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 13:11:39 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 085FC1A026F for <ietf@ietf.org>; Mon,  7 Apr 2014 13:11:32 -0700 (PDT)
Received: (qmail 53009 invoked from network); 7 Apr 2014 20:11:26 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 7 Apr 2014 20:11:26 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=5343066e.xn--30v786c.k1404; i=johnl@user.iecc.com; bh=a8IFGY1og6UTSOGgvB7l6158a15id3zm50i2BWiqo44=; b=Jhjvd1b8WfguhemYGujvV3Dks46UpGDxlDvcfIomwuzq8wcb/SV8p2DGekQy4kU4sldBqv+ie7GQbxonngs3LOw7wukx0BXbrEwQ4fj31pgv/aSV96Z9iLm7bURjhBfSidVw1nPH+4oQXtegUp4I29b6uOTNK3rnCW5x3lGbsZpThhlJSxgTrNqwJeMKR5zQJlAmTKumA1AODOLKcbw1Pu5nPvVQaK7asoRAB76gE6h41AjCAkdQ7VFmSd26e1QM
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:content-transfer-encoding; s=5343066e.xn--30v786c.k1404; bh=a8IFGY1og6UTSOGgvB7l6158a15id3zm50i2BWiqo44=;  b=fCmXPaD7VhuYhtHEQiVqxlbG7qja9PdegEJUjmfY0XdyPH4E+opigGuMaKzyNYo7iiiRSHCjHikS242JmUftTc8HtjWQNBwxP5bUKhyv0eZJGhbElPrz/osLcyn1eAyUHSWN1bbxN6J4KcbNevqSygU1zoFGQeuqDWxARg16Kd0CTJsKWlz9fwzcEPg27iTRwmG6qliF5osq2+12zz8JSQnLkHWW54spUBpk+/hnLJRSoij6hm4c3vaa25nt/b+4
Date: 7 Apr 2014 20:11:04 -0000
Message-ID: <20140407201104.42050.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Yahoo breaks every mailing list in the world including the IETF's
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/J-IsfA0Lb-6T_NeMD1ENKZyb9tA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 20:11:48 -0000

DMARC is what one might call an emerging e-mail security scheme.
There's a draft on it at draft-kucherawy-dmarc-base-04, intended for
the independent stream.  It's emerging pretty fast, since many of the
largest mail systems in the world have already implemented it,
including Gmail, Hotmail/MSN/Outlook, Comcast, and Yahoo.

DMARC lets a domain owner make assertions about the From: address, in
particular that mail with their domain on the From: line will have a
DKIM signature with the same domain, or a bounce address in the same
domain that will pass SPF.  They can also offer policy advice about
what to do with mail that doesn't have matching DKIM or SPF, ranging
from nothing to reject the mail in the SMTP session.  The assertions
are in the DNS, in a TXT record at _dmarc.<domain>.  You can see mine
at _dmarc.taugh.com.

For a lot of mail, notably bulk mail sent by companies, DMARC works
great.  For other kinds of mail it works less great, because like
every mail security system, it has an implicit model of the way mail
is delivered that is similar but not identical to the way mail is
actually delivered.

Mailing lists are a particular weak spot for DMARC.  Lists invarably
use their own bounce address in their own domain, so the SPF doesn't
match. Lists generally modify messages via subject tags, body footers,
attachment stripping, and other useful features that break the DKIM
signature.  So on even the most legitimate list mail like, say, the
IETF's, most of the mail fails the DMARC assertions, not due to the
lists doing anything "wrong".

The reason this matters is that over the weekend Yahoo published a
DMARC record with a policy saying to reject all yahoo.com mail that
fails DMARC.  I noticed this because I got a blizzard of bounces from
my church mailing list, when a subscriber sent a message from her
yahoo.com account, and the list got a whole bunch of rejections from
gmail, Yahoo, Hotmail, Comcast, and Yahoo itself.  This is definitely
a DMARC problem, the bounces say so.

The problem for mailing lists isn't limited to the Yahoo subscribers.
Since Yahoo mail provokes bounces from lots of other mail systems,
innocent subscribers at Gmail, Hotmail, etc. not only won't get Yahoo
subscribers' messages, but all those bounces are likely to bounce them
off the lists.  A few years back we had a similar problem due to an
overstrict implementation of DKIM ADSP, but in this case, DMARC is
doing what Yahoo is telling it to do.

Suggestions:

* Suspend posting permission of all yahoo.com addresses, to limit damage

* Tell Yahoo users to get a new mail account somewhere else, pronto, if
  they want to continue using mailing lists

* If you know people at Yahoo, ask if perhaps this wasn't such a good idea

R's,
John


From nobody Mon Apr  7 13:38:02 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1FE31A0259 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 13:38:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 yCNhDsXnK92A for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 13:37:54 -0700 (PDT)
Received: from mail-pb0-x231.google.com (mail-pb0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 316611A082B for <ietf@ietf.org>; Mon,  7 Apr 2014 13:37:48 -0700 (PDT)
Received: by mail-pb0-f49.google.com with SMTP id jt11so7181234pbb.8 for <ietf@ietf.org>; Mon, 07 Apr 2014 13:37:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5y1OlPoE/jWszBv3A08qPrf8OngpcDWC0G+85MZ82Tc=; b=K5eGyxMxh4eQhgeaWDO1DuKdtgj7znh2E3FQuX7ps8gkbzfxw/5msepTF9axyFkvHH ZO3qUUoOPJz3OgZRn1nGEuyr7fmRiyoIzZrEJVreLDwImcrc5OGYGWlFlW/VeIn/w6N/ cbxDqUzu356tRg+dvUqUaWWRUQycOkUiJOKNVCL0Y6sh/rpnEwpXtSixZIorsvQay5Ws 5y67EfHqYR6ONe9i32bKmCloOgXE20ZNqc9XDAtGdq0vVOW3zOn+WLD0Dp0hdEFAcwQ4 N8MafXBPVarBvb3JeDDr5UEG5uBxxCVqS2znIvOtHYRlr1kfycwr8uxVHY/lAY5BwPav lQtQ==
X-Received: by 10.67.1.106 with SMTP id bf10mr22753040pad.78.1396903062655; Mon, 07 Apr 2014 13:37:42 -0700 (PDT)
Received: from [192.168.178.23] (211.197.69.111.dynamic.snap.net.nz. [111.69.197.211]) by mx.google.com with ESMTPSA id et3sm38741038pbc.52.2014.04.07.13.37.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Apr 2014 13:37:42 -0700 (PDT)
Message-ID: <53430C95.2070705@gmail.com>
Date: Tue, 08 Apr 2014 08:37:41 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Yahoo breaks every mailing list in the world including the IETF's
References: <20140407201104.42050.qmail@joyce.lan>
In-Reply-To: <20140407201104.42050.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RinBAOkJXsGsztgbEpEK73y2mG4
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 20:38:01 -0000

> * Suspend posting permission of all yahoo.com addresses, to limit damage

Mailman admins:

You can find all subscribers with a yahoo address from the mailman
list admin page:
1. select "Membership List"
2. enter "yahoo" in the search box
3. click "Search"

Regards
   Brian

On 08/04/2014 08:11, John Levine wrote:
> DMARC is what one might call an emerging e-mail security scheme.
> There's a draft on it at draft-kucherawy-dmarc-base-04, intended for
> the independent stream.  It's emerging pretty fast, since many of the
> largest mail systems in the world have already implemented it,
> including Gmail, Hotmail/MSN/Outlook, Comcast, and Yahoo.
> 
> DMARC lets a domain owner make assertions about the From: address, in
> particular that mail with their domain on the From: line will have a
> DKIM signature with the same domain, or a bounce address in the same
> domain that will pass SPF.  They can also offer policy advice about
> what to do with mail that doesn't have matching DKIM or SPF, ranging
> from nothing to reject the mail in the SMTP session.  The assertions
> are in the DNS, in a TXT record at _dmarc.<domain>.  You can see mine
> at _dmarc.taugh.com.
> 
> For a lot of mail, notably bulk mail sent by companies, DMARC works
> great.  For other kinds of mail it works less great, because like
> every mail security system, it has an implicit model of the way mail
> is delivered that is similar but not identical to the way mail is
> actually delivered.
> 
> Mailing lists are a particular weak spot for DMARC.  Lists invarably
> use their own bounce address in their own domain, so the SPF doesn't
> match. Lists generally modify messages via subject tags, body footers,
> attachment stripping, and other useful features that break the DKIM
> signature.  So on even the most legitimate list mail like, say, the
> IETF's, most of the mail fails the DMARC assertions, not due to the
> lists doing anything "wrong".
> 
> The reason this matters is that over the weekend Yahoo published a
> DMARC record with a policy saying to reject all yahoo.com mail that
> fails DMARC.  I noticed this because I got a blizzard of bounces from
> my church mailing list, when a subscriber sent a message from her
> yahoo.com account, and the list got a whole bunch of rejections from
> gmail, Yahoo, Hotmail, Comcast, and Yahoo itself.  This is definitely
> a DMARC problem, the bounces say so.
> 
> The problem for mailing lists isn't limited to the Yahoo subscribers.
> Since Yahoo mail provokes bounces from lots of other mail systems,
> innocent subscribers at Gmail, Hotmail, etc. not only won't get Yahoo
> subscribers' messages, but all those bounces are likely to bounce them
> off the lists.  A few years back we had a similar problem due to an
> overstrict implementation of DKIM ADSP, but in this case, DMARC is
> doing what Yahoo is telling it to do.
> 
> Suggestions:
> 
> * Suspend posting permission of all yahoo.com addresses, to limit damage
> 
> * Tell Yahoo users to get a new mail account somewhere else, pronto, if
>   they want to continue using mailing lists
> 
> * If you know people at Yahoo, ask if perhaps this wasn't such a good idea
> 
> R's,
> John
> 
> 


From nobody Mon Apr  7 14:17:41 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6CF71A0257; Mon,  7 Apr 2014 14:17:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 DgELsRrSX_tE; Mon,  7 Apr 2014 14:17:31 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 40A271A01FC; Mon,  7 Apr 2014 14:17:31 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s37LHI2D007337 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 7 Apr 2014 23:17:18 +0200 (MEST)
Subject: Re: Security for various IETF services
In-Reply-To: <DC23F34E807E77F8C4C095C3@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
Date: Mon, 7 Apr 2014 23:17:18 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140407211718.60C021ACAA@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fkpWT__UBUDkItEpd5fZ4uyKoRo
Cc: IETF-Discussion <ietf@ietf.org>, Tim Bray <tbray@textuality.com>, The IESG <iesg@ietf.org>, Stewart Bryant <stbryant@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Apr 2014 21:17:37 -0000

John C Klensin wrote:
> 
> Ted Lemon <ted.lemon@nominum.com> wrote:
>>
>> Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>>>
>>> Yes, we ought move away from passwords if/when we ever find an
>>> acceptably better solution, and yes, people ought manage their
>>> passwords well, but neither are today's reality more's the
>>> pity.
>> 
>> Perhaps it would be worth setting up support for client certs
>> as a way to log in to IETF services.   If we won't start, why
>> would someone else?
> 
> If we are really serious about promoting/ encouraging security,
> I'd really like to see this as an option.  Not only would it be
> responsive to Ted's question, but, if we made it available and
> almost no one used it, it would give us a lot of information
> about the course we are on.

TLS _client_ certificates are typically used in closed groups,
where a single CA is issuing all these certs.

TLS client cert authentication has a few small issues.  The TLS server
needs to explicitly request the client cert (unsolicited client certs
are not possible/not allowed), and when the server asks for them
in the initial handshake, the client certificates will travel the
network _in_the_clear_.  Requesting client certificates only in the
renegotiation handshake has it own set of problems, besides twice
the full handshake crypto overhead.  For TLS renego problems and fixes
see rfc5746 and https://secure-resumption.com/



I also think that discontinuing the _public_ services of the IETF
over traditional, insecure channels (HTTP, anon-FTP, plain SMTP, whatever)
should require a threat analysis.

Different to what a lot of folks believe, TLS is neither a panacea nor
magic pixie dust.  In order to determine whether doing X-over-TLS really
provides the desired security characteristics, it is necessary to know
what security properties one is looking for.

The reason why there was an issue with TLS renegotiation is that applications
boldly assumed properties which never existed in the first place -- and
that problem would have been obvious if anyone of those abusing
TLS renegotiation for delayed authentication would have actually cared
to check for _the_real_TLS_protocol_characteristics_ instead of
believing in TLS magic pixie dust.


-Martin


From nobody Mon Apr  7 21:19:22 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C94A31A00CF for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 21:19:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 9ZFWydmEvfBI for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 21:19:10 -0700 (PDT)
Received: from nk11p04mm-asmtp001.mac.com (nk11p04mm-asmtp001.mac.com [17.158.236.236]) by ietfa.amsl.com (Postfix) with ESMTP id EA9741A00B0 for <ietf@ietf.org>; Mon,  7 Apr 2014 21:19:09 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N3P00K872NHLUB0@nk11p04mm-asmtp001.mac.com> for ietf@ietf.org; Tue, 08 Apr 2014 04:18:55 +0000 (GMT)
Subject: Re: Yahoo breaks every mailing list in the world including the IETF's
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <20140407201104.42050.qmail@joyce.lan>
Date: Tue, 08 Apr 2014 05:18:52 +0100
Message-id: <0E945AB4-71ED-4EFD-B7CE-D9CDE60D3084@me.com>
References: <20140407201104.42050.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXREEbG1oaGkdHB0lGUkdDRl5PWBoaHhEKTEMXGx0EGx8SBBscHwQdGBAbHho fGhEKWE0XSxEKbX4XGhEKTFkXGxobGxEKWUkXEQpZXhdoY3kRCkNOF0sbGBpiTk1mHBpCaRl4c wcZEhoeGxJeGxEKWFwXGQQaBB0HTUsdEkhJHEwFGx0EGx8SBBscHwQdGBAbHhofGxEKXlkXYU9 4G2ERCkxGF2xraxEKQ1oXGBsZBBsYGQQbExgEGRoRCkRYFxgRCkRJFxgRCkJFF2ZQfV0fbWQaB UhjEQpCThdscGB5QB1iUmkaYhEKQkwXZ0kfbXlpGH5yQk0RCkJsF2VoZRhtTRwYQ0ZOEQpCQBd oeWBafUZnWH5zHxEKcGgXYGRsX2xLYU58a30RCnBoF2N+SRtkaxJkfVxFEQpwaBdjb0NZH3hvf WIFZhEKcGgXZh4aUGxOZURtAWERCnBoF25mW2dbblwfaxxbEQpwbBdrZk5rQWVfZlNnAREKcEw XZXJfZ15fSUlMXEsR
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-08_02:2014-04-07,2014-04-08,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404070303
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uzu7BAe0wND4-rbUgCiCxdVTeP4
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 04:19:16 -0000

I was *sure* that the SPF pass was all that was required; I didn't get that bit in the spec where "Alignment" means matching up the From: field.  Has it always been like that?  Because if not then list-friendly (but not forwarding-friendly) domains could have just used SPF.

Ah well, guess it's a lot more messed up than I thought. :(

Cheers,
Sabahattin


From nobody Mon Apr  7 21:22:02 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1BD31A00D7 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 21:21:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 0HoR1_T9GTFg for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 21:21:54 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id B2D771A00B0 for <ietf@ietf.org>; Mon,  7 Apr 2014 21:21:53 -0700 (PDT)
Received: (qmail 41172 invoked from network); 8 Apr 2014 04:21:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=a0d3.5343795b.k1404; bh=CO/YbZEYfukS7owxsbQI/KtWmlwPXE3ekZVZXp5MuZY=; b=XHKCNSn8T9CLYu5nK5ro1ESgTN1jDS2n2tOjFYXnvr64ObTcJ7xW10SXPXa4szLN6ZEvuTvxpMdkYi0NfP/Ed9SKzQbSOibRPDRYMmlBHvQNTw3FC6F56B1QauIerJoWTGyfffQ9HbBvTpqOa6MOMvWdl+w/u0EUZP2diqUFD57j30NJcsgWz4c0WgyrbEsBM4m1++rhPkIegmeMpjKLr6gcXfWOALXRUdUA4rd1lkZlxofcQ+5OwFaCYhHhs71V
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=a0d3.5343795b.k1404; bh=CO/YbZEYfukS7owxsbQI/KtWmlwPXE3ekZVZXp5MuZY=; b=TxTpfaLetIhC4reiClXsUt0NNV8nhTCsOu+tzJcFRHOf8fQFFH5nfQP8wgzptJRfwJHnFHmA4N5N2Tcfwz6rpGn149BWCrTv3fjWCFixgkkkWzF21sXpqiYrQhcwlrsOyv9I09jttwdIUCOZ7yW5TOqpE+XVsWIh0dmih0IBrA9836VjHZIzKJktdgy32d2Zc1iuVvuV3kUMiZKPhxzD4tb/MLVcDP7PZehGp6u59Ue+J/a+2PXOi1f0Xs9PPyOu
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 08 Apr 2014 04:21:47 -0000
Date: 8 Apr 2014 00:21:46 -0400
Message-ID: <alpine.BSF.2.00.1404072357400.73388@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-2096504466-1396930907=:73388"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3UwUJEPPt3_ISgz5YtnX-NuSp1E
Cc: IETF general list <ietf@ietf.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 04:21:59 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-2096504466-1396930907=:73388
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> differ from the envelope sender. That's why the extra DMARC header
> X-Original-Authentication-Results [1] is needed sadly :-(.

Several people have proposed that, but a few minutes' thought reveals that 
it wouldn't actually help, becuase bad guys can add fake X-O-A-R headers 
just as easily as good guys can add real ones.  You would have to track 
which forwarders are well behaved and add valid X-O-A-R headers, but if 
you can do that, you can skip the header analysis and just whitelist the 
mail from the well behaved forwarders.

Note that there are also well behaved things that don't pass DMARC and 
don't have any original authentication results to report, with the usual 
examples being mail-an-article at the NY Times and Wall Street Journal.

Tracking who is well behaved is quite hard.  You can't ask people to 
self-identify, since again, bad guys will lie.  I was under the impression 
that gmail tried to do it, but given the blizzard of bounces I've seen, 
apparently not.

> The problem described WILL vanish when all mailing list apps implement
> DMARC, but until then, it's really broken.

Mailing list apps can't "implement DMARC" other than by getting rid of 
every feature that makes lists more functional than simple forwarders. 
Given that we haven't done so for any of the previous FUSSPs that didn't 
contemplate mailing lists, because those features are useful to our users, 
it seems unlikely we'll do so now.

If receivers want to implement DMARC policy, they need to make their false 
alarm whitelist first.  This appears to be a substantial, perhaps 
insurmountable, hurdle.

> At the same time, delaying mass usage of the reject policy would limit
> damage.

Reject policy is fine for domains that don't have individual human users, 
or for companies with firm staff policies that all mail goes through the 
company mail server, and employees don't join mailing lists and the like 
using company addresses, or the company provides a separate less strictly 
managed domain for its staff mail. Strict policies will never be 
appropriate for public webmail systems where the users will use their mail 
addresses any way one can use a mail address.  Yahoo appears to understand 
most of this, viz. the different domain for Elizabeth's company mail.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
--3825401791-2096504466-1396930907=:73388
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIII7gYJKoZIhvcNAQcCoIII3zCCCNsCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBh8wggYbMIIFA6ADAgECAgMJWEYwDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xNDAzMTgxOTQ3NDdaFw0xNTAzMjAwMDU2MDBaMDoxGDAW
BgNVBAMMD2pvaG5sQHRhdWdoLmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxA
dGF1Z2guY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnMGH
52DBxB4jb86Sxi3VvgOjirvLveIVP7zvqxBDpJzxrF02wCYwnQuxi3S3U5ge
3iHihzhM9qP+N03frkr4KH6Spgec88YjMioVQStTQZcrogTdHweZOgT8tckg
HEmHCF8uHBjD0HbfDk+9zYFtaE3QPk5aGm02Id0fNNM5WmSQSxVwF0Ddryq5
vIU0AHbB/1kok1zJpwWA06SgHenlnYngnSpNWlOn+SxboiD28m2XTWDP5ULL
e1b040VtkQMzpuVXzAHWVQYQWUevJ4y8mrUsqAyGuYSb5pTU28D+NExVAYxn
WD94rzgBpkXgC4Xxcp3TmyfMaLMF4M9ef0nu+QIDAQABo4IC1TCCAtEwCQYD
VR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSpNAr06FueusUfmbDdecnZ1kznsTAfBgNVHSME
GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0
YXVnaC5jb20wggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIB
KjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5
LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3Vl
ZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJl
bWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25s
eSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0
aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmg
J4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYI
KwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRz
c2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRw
Oi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5j
YS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0G
CSqGSIb3DQEBCwUAA4IBAQC3OSsHtuc1se2JPbLqI1b31i0EER3UX6Ep2Zuy
FkACIpk/i8mPi0KIfMWWiDlNmqeQEq8308i0/2mVcMVdgKWIUMJdZb3CmNfs
3qtTlrdXXYXT7ZLjL6a1Bbh/lKUm35JYRH8zf3rqDbLkpiA92vc7uTQcbDay
1sQ4CSTvOWuq0CIwMXqJePhHf/runG7ndDuX2yFagHlxhsvn7raw5NQuu4Sj
ofwbNiszwkryB7ZYUxq2Pg2i1m2XlgMbNEfw8deAZOyHGKKGz25Ei1KvJofH
1izh0WDU+ueJum6RHm8/o/i53MbYZN4Il64aBD1HPqQow3jHQBhAc8XN85hH
csS2MYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZp
Y2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCVhGMAkGBSsOAwIaBQCggdgw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQw
NDA4MDQyMTQ2WjAjBgkqhkiG9w0BCQQxFgQUbLH2+CsySpO5hTmO0Mz+130J
+7gweQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEW
MAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEggEANZBZ4V/5M8rNlQh/uemyB0APcVf5TdAf3lAh+n1njwmDN5xo
IxbKqjUkAvHUQLk2Xd+muON6TPpQP6BRNjwU+SuMQokFfCS1qLlYyYbm7blj
6y4XL2Fu0+UIY00zERCPWHiSS61ShR83VVL9XEgMRRHlZK5wq9cp4wa9CPmO
SCb/8htSgpEgck1CaYfUEyQ9Z68DPRz0+/d/oKkyf2yh31Dg6lcfLEvCB7BQ
o7BStqygktFZ9b3LoOcvkqV8lU5e0hqHXeqDH3ON4lSnKk1IU9MJl8yvS+ay
gu685ttq8t8zJsJEAQD9LlyDa27vWhl9SKpmthpBfrid/+ifaz57Tg==

--3825401791-2096504466-1396930907=:73388--


From nobody Mon Apr  7 21:26:04 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9B431A00E5 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 21:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.112
X-Spam-Level: 
X-Spam-Status: No, score=-0.112 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 szs5D9rP4XoL for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 21:25:57 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id B66501A00B0 for <ietf@ietf.org>; Mon,  7 Apr 2014 21:25:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1396931153; x=1428467153; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=R7u+1RByhJgAZKjSF5a1/wySfPYETZkxIqQURjI9B5Q=; b=SBVQeATyZ912i+JEYBGYAnkVMD6TMKkpBCrwmiPMe5dXfwT8vwFk2Whu U48tehwxazT80VJj7VapNqayDejOA8B1fa6Dhk60ZOJx/VP68fn8V3/PD LtnEE9+rdMXcx069eEIMep87TyvMsejUUKWeR8RMhkAfgqofnxL29SkOz E=;
X-IronPort-AV: E=McAfee;i="5400,1158,7401"; a="61745734"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth02.qualcomm.com with ESMTP; 07 Apr 2014 21:25:53 -0700
X-IronPort-AV: E=Sophos;i="4.97,815,1389772800"; d="scan'208";a="645473101"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Apr 2014 21:25:52 -0700
Received: from [99.111.97.136] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 7 Apr 2014 21:25:51 -0700
Message-ID: <p06240607cf6927f80f42@[99.111.97.136]>
In-Reply-To: <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>
X-Mailer: Eudora for Mac OS X
Date: Mon, 7 Apr 2014 21:17:08 -0700
To: Ole Jacobsen <olejacobsen@me.com>, Rgd.ietf <rgd.ietf@gmail.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea  Efflux Appliances (HTCPCP-TEA)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FLqR4v3k1fRHD8Vk_W8tKPcgxpo
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 04:26:03 -0000

At 8:16 PM -0700 4/1/14, Ole Jacobsen wrote:

>  Sat-too-long-and-is-still-hot is, if I recall, known as "stewed" 
> and anyone responsible faces possible deportation from the UK. A 
> very serious matter indeed, almost as serious as refusing to obey 
> the rules of a queue.

Sitting and steeping are orthogonal, provided the tea preparation 
apparatus has a method to arrest steepage (e.g., a Chatsford tea pot 
with large-basket mesh infuser that one simply lifts out after the 
appropriate interval).  However, my understanding was that the 
customary way to prepare British-style tea is to leave the leaves in 
all day, providing a strongly tannic tea which is better suited to 
copious milk and sugar.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
He hadn't a single redeeming vice.
        --Oscar Wilde


From nobody Mon Apr  7 22:06:48 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE2F51A010C for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:06:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 T8oEUhkt0WW8 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:06:40 -0700 (PDT)
Received: from nk11p04mm-asmtp002.mac.com (nk11p04mm-asmtp002.mac.com [17.158.236.237]) by ietfa.amsl.com (Postfix) with ESMTP id D21441A010B for <ietf@ietf.org>; Mon,  7 Apr 2014 22:06:39 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N3P00DDE4USPU70@nk11p04mm-asmtp002.mac.com> for ietf@ietf.org; Tue, 08 Apr 2014 05:06:33 +0000 (GMT)
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <alpine.BSF.2.00.1404072357400.73388@joyce.lan>
Date: Tue, 08 Apr 2014 06:06:27 +0100
Message-id: <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXREEbG1oaGkdHB0lGUkdDRl5PWBoaHhEKTEMXGx0EGx8SBBscHwQdHhAbHho fGhEKWE0XSxEKbX4XGhEKTFkXGxobGxEKWUkXEQpZXhdoY3kRCkNOF0sbHhpiTk1mHBpCaRl4c wcZEhofGhxyGBEKWFwXGQQaBB0HTUsdEkhJHEwFGx0EGx8SBBscHwQdHhAbHhofGxEKXlkXYU9 5QhoRCkxGF2xraxEKQ1oXGBsZBBsYGQQbExgEGRoRCkRYFx4RCkRJFxkRCkJFF2ZQfV0fbWQaB UhjEQpCThdscGB5QB1iUmkaYhEKQkwXZ0kfbXlpGH5yQk0RCkJsF2VoZRhtTRwYQ0ZOEQpCQBd vQlBdfU1pfh0bUBEKcGgXZU5uQH1Qe0tfSxMRCnBoF2xdXxxfHEIaTVNfEQpwaBdpcBofQmNQR hptYxEKcGgXZnxBQ0YTfUtfeFwRCnBoF2RnYksfcmFjGEZMEQpwbBdrZk5rQWVfZlNnAREKcEw XZXJfZ15fSUlMXEsR
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-08_02:2014-04-07,2014-04-08,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404070317
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RX3jOAZXit7m5c5P8JRSnyMKDsQ
Cc: IETF general list <ietf@ietf.org>, "Robin H. Johnson" <robbat2@gentoo.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 05:06:45 -0000

On 8 Apr 2014, at 05:21, John R Levine <johnl@taugh.com> wrote:
> Mailing list apps can't "implement DMARC" other than by getting rid of every feature that makes lists more functional than simple forwarders. Given that we haven't done so for any of the previous FUSSPs that didn't contemplate mailing lists, because those features are useful to our users, it seems unlikely we'll do so now.

Well,  Mailman 2.1.16 has the FROM_IS_LIST feature that "Fixes" the problem by putting the list address in the From: field.  That seems to work, except that you lose information (the sender's address) if the list wants to operate a policy of "Reply goes to list".  You can then assure that DKIM signatures are valid and set up SPF, etc.  This also has the effect of letting you operate through the various cloud email platforms that try to validate sender addresses.

But I agree it's broken.

Cheers,
Sabahattin


From nobody Mon Apr  7 22:09:59 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D18481A0108 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:09:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.6
X-Spam-Level: 
X-Spam-Status: No, score=-3.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 XyIxL8vI7y-H for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:09:53 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.113]) by ietfa.amsl.com (Postfix) with ESMTP id E031B1A0106 for <ietf@ietf.org>; Mon,  7 Apr 2014 22:09:52 -0700 (PDT)
Received: from [193.109.255.147:20831] by server-9.bemta-14.messagelabs.com id D7/C4-03644-A9483435; Tue, 08 Apr 2014 05:09:46 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-72.messagelabs.com!1396933785!10573865!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21415 invoked from network); 8 Apr 2014 05:09:46 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-6.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 8 Apr 2014 05:09:46 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Tue, 8 Apr 2014 06:09:45 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@qti.qualcomm.com>, <olejacobsen@me.com>, <rgd.ietf@gmail.com>
Date: Tue, 8 Apr 2014 06:06:31 +0100
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Topic: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Index: Ac9S4rKMjcY2OMoVTrmuwJ3pUYWGhwABZubf
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EECC@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>, <p06240607cf6927f80f42@[99.111.97.136]>
In-Reply-To: <p06240607cf6927f80f42@[99.111.97.136]>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hDuXJc5szoBgGpxCutyUpNspH6k
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 05:09:58 -0000

George Orwell: A Nice Cup of Tea, 12 Jan 1946
http://www.booksatoz.com/witsend/tea/orwell.htm

is often cited as the correct _English_ way to take tea. No sugar.

Lloyd Wood
http://about.me/lloydwood

sure, why not take your dietary advice from someone who died at the age of =
46?
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Randall Gellens [randy@qti.=
qualcomm.com]
Sent: 08 April 2014 05:17
To: Ole Jacobsen; Rgd.ietf
Cc: IETF Discussion
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea=
  Efflux Appliances (HTCPCP-TEA)

At 8:16 PM -0700 4/1/14, Ole Jacobsen wrote:

>  Sat-too-long-and-is-still-hot is, if I recall, known as "stewed"
> and anyone responsible faces possible deportation from the UK. A
> very serious matter indeed, almost as serious as refusing to obey
> the rules of a queue.

Sitting and steeping are orthogonal, provided the tea preparation
apparatus has a method to arrest steepage (e.g., a Chatsford tea pot
with large-basket mesh infuser that one simply lifts out after the
appropriate interval).  However, my understanding was that the
customary way to prepare British-style tea is to leave the leaves in
all day, providing a strongly tannic tea which is better suited to
copious milk and sugar.

--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
He hadn't a single redeeming vice.
        --Oscar Wilde


From nobody Mon Apr  7 22:18:47 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E41C1A011D for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 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] autolearn=ham
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 Ig3Iv-pcN65T for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:18:39 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id 316221A0117 for <ietf@ietf.org>; Mon,  7 Apr 2014 22:18:39 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id ECD1CD04508; Tue,  8 Apr 2014 01:18:32 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1396934313; bh=ukAHfCuxWSas6lMlhTEtO2HCwIAnjrddf6uYaHgmWPs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=gmdhfnmZLIApgxvUoZay95dKzQyypuyllj9RLFqfX0mKzZqsvfPvBy6K8Z2nHubYi gP3kkyF4nod1sBPM/I/DBEWj7+m0wORLoLbW4cXt2nc8mjrRPY1E66VmB6K/MexinN c4GO+8+LM09aNI6B5Mh8yf8mlmtErKAPeWjVu0o8=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id B7155D042F2; Tue,  8 Apr 2014 01:18:32 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf general list <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Date: Tue, 08 Apr 2014 01:18:29 -0400
Message-ID: <1418087.9IOA94zE9f@scott-latitude-e6320>
User-Agent: KMail/4.11.5 (Linux/3.11.0-19-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/sZ91964iJKSyGqd4tUr-D0LBgfk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 05:18:44 -0000

On Tuesday, April 08, 2014 06:06:27 Sabahattin Gucukoglu wrote:
> On 8 Apr 2014, at 05:21, John R Levine <johnl@taugh.com> wrote:
> > Mailing list apps can't "implement DMARC" other than by getting rid of
> > every feature that makes lists more functional than simple forwarders.
> > Given that we haven't done so for any of the previous FUSSPs that didn't
> > contemplate mailing lists, because those features are useful to our
> > users, it seems unlikely we'll do so now.
> Well,  Mailman 2.1.16 has the FROM_IS_LIST feature that "Fixes" the problem
> by putting the list address in the From: field.  That seems to work, except
> that you lose information (the sender's address) if the list wants to
> operate a policy of "Reply goes to list".  You can then assure that DKIM
> signatures are valid and set up SPF, etc.  This also has the effect of
> letting you operate through the various cloud email platforms that try to
> validate sender addresses.
> 
> But I agree it's broken.

It's unrelated to SPF.  SPF uses Mail From and so on lists that aren't just 
forwarders, the list already uses it's own Mail From.  The only way SPF gets 
roped into this thing is the DMARC use of SPF plus an insistence on "identity 
alignment" to add a requirement that the From domain is in the same domain as 
Mail From.  That's not SPF's fault.

DMARC is interesting for the feedback reports, but I'm certainly not 
publishing reject policies on any domains I have that have real users.

Scott K


From nobody Mon Apr  7 22:19:35 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FDE81A0133 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:19:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 ti-_McdkwyaN for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:19:24 -0700 (PDT)
Received: from mail-pb0-x22f.google.com (mail-pb0-x22f.google.com [IPv6:2607:f8b0:400e:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 898241A012D for <ietf@ietf.org>; Mon,  7 Apr 2014 22:19:24 -0700 (PDT)
Received: by mail-pb0-f47.google.com with SMTP id up15so501993pbc.34 for <ietf@ietf.org>; Mon, 07 Apr 2014 22:19:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=n5nlEvflt7o9mzc90dAcy6tkp/1KNzbx8bTxdX42EtA=; b=REsRusjyCRzxw/ZD+0t5asD4gvMCZ9rez+UymJ1RUASArBRGjDSYWfgbwdP5JTx15G fembW0sYAFFHzq4U711BbAZ3xd5xek/HLNMKzYk/ynROirZGcVXxhuZ53Ssy0LkCHYnB Ezi6QLcizq8W32zDxvHUA6b9VWB6JsdAjjF3BM6Wl2nueIfSwvR1n+nVPIyZcOMOgzo8 JPLWifPZ1oDh/8hEt79Xkp6ENzcKM2mhwv30O7Dz+todMUIkzcuUBT+vZPo+fjcShIVX ehwi+3xxIK2u1cPtqakDKccWBbaqT0suBLXfoWGZz9IFwhxc6TqnqFiV9LhqYR0m4Kt3 65jA==
X-Received: by 10.66.66.135 with SMTP id f7mr1857336pat.22.1396934358835; Mon, 07 Apr 2014 22:19:18 -0700 (PDT)
Received: from [192.168.178.23] (211.197.69.111.dynamic.snap.net.nz. [111.69.197.211]) by mx.google.com with ESMTPSA id om6sm1759939pbc.43.2014.04.07.22.19.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 07 Apr 2014 22:19:18 -0700 (PDT)
Message-ID: <534386D6.1030304@gmail.com>
Date: Tue, 08 Apr 2014 17:19:18 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
In-Reply-To: <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NAhf7RSWr9IQ10_ilNARy4Fzjoc
Cc: IETF general list <ietf@ietf.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 05:19:29 -0000

Hi,

On 08/04/2014 17:06, Sabahattin Gucukoglu wrote:
> On 8 Apr 2014, at 05:21, John R Levine <johnl@taugh.com> wrote:
...
> Well,  Mailman 2.1.16 has the FROM_IS_LIST feature that "Fixes" the problem by putting the list address in the From: field.  That seems to work, except that you lose information (the sender's address)

I would find that quite unacceptable. We need to know who said what
in an IETF discussion, and having to poke around in the headers to find
the original sender would be very painful. It would make some
archive searches impossible, too.

Data: I just had a quick look at my mail archives going back N years. I find
119 messages with 'yahoo' in the From field out of 52367 with 'ietf' in To or CC.

    Brian


From nobody Mon Apr  7 23:28:32 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 111CC1A0032 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 23:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.243
X-Spam-Level: 
X-Spam-Status: No, score=0.243 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_34=0.6, SPF_NEUTRAL=0.779] autolearn=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 gOKW5ZhgOGKL for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 23:28:23 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 72B0A1A00AF for <ietf@ietf.org>; Mon,  7 Apr 2014 23:28:23 -0700 (PDT)
Received: (qmail 54575 invoked from network); 8 Apr 2014 06:28:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=d52e.53439700.k1404; bh=E2fDR6bW067CPqgMF+sL6/JD034EVroEgnaLo+Xm88g=; b=kxk2pmFWwQqfIiaMk7FVe9oGR+G2W02InoE/OiEmnph/B4r0IWEfUFWGnH6v7ip0oY2QIB9FB7oOITBdAon+dV67cCpv3aBwtq+9hIAgShShOwYIs+9NrbTfg1smZWrKhM6pAWufLnK5s6gjzPXMaumHFHXkkaj138wdsL6+3ZkGWDyCRo8ok8z/S9xYB3pny8cUclHqRrFvSQcI6Q3LMH2e1ZxTLlq+Gzn3EX4Or6CRC+OSnOVAalS8p2wAySkB
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=d52e.53439700.k1404; bh=E2fDR6bW067CPqgMF+sL6/JD034EVroEgnaLo+Xm88g=; b=u8++zGLTbtYE0a+kzNdYd6dPzXtfr1tTZeRXHS87HRDSZkXijLUat6aIl71L0zD/8YRwRLRBlCjn2dkSjl5il152ezDZiviyZ4ayZMXfoEGsHtI+6hf19j5x5EkUn+xtCeYEex8PpLdujFLVB4nZj4d3RPyCITuhV6KchWQLKFHlimW/iRl36XxcrWAxVozdakCZJ9Q3XOVNNHAn9hURQTNUteSJ14KttZtwdUDwn2gtzAnr0+bHVOiDs/9M9d7K
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 08 Apr 2014 06:28:16 -0000
Date: 8 Apr 2014 02:28:15 -0400
Message-ID: <alpine.BSF.2.00.1404080216160.73769@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <20140408053752.GB2858@orbis-terrarum.net>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <20140408053752.GB2858@orbis-terrarum.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1373175125-1396938496=:73769"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gGnNLdlt4APLLFEAoEtOJyQSesU
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 06:28:29 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1373175125-1396938496=:73769
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII

> I think the original scenario you described could be implemented by bad
> players as follows:
> - set up a mailman instance with DMARC support, that forges the XOAR header.
> - Ensure that the mailman outgoing mail passes SPF+DKIM for the domain in question.

Right, except it doesn't even have to be mailman, just spamware that 
creates headers that look like mailman's.  Like I said, if you trust the 
sender to be a real list, deliver its mail.  If you don't, don't.  I don't 
think there are any major conceptual challenges here.

> Those uses shouldn't be considered valid, and NYTimes has already moved
> away from that, at least as of my test 5 minutes ago.

Well, the WSJ does.  This is a perfectly reasonable way to send mail, 
endorsed by decades of practice.

|Date: Tue, 8 Apr 2014 02:24:13
|From: "wsjol@johnlevine.com" <wsjol@johnlevine.com>
|To: johnl@taugh.com
|Subject: WSJ.com - Ukrainian leaders, U.S. slam Russia over new unrest;

The envelope bounce address is <bounces@wsjemail.com>, again perfectly 
reasonable.

> By implement DMARC, I meant implement XOAR headers; VERP is too useful

As described above, XOAR is not useful because you can't trust it.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
--3825401791-1373175125-1396938496=:73769
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIII7gYJKoZIhvcNAQcCoIII3zCCCNsCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBh8wggYbMIIFA6ADAgECAgMJWEYwDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xNDAzMTgxOTQ3NDdaFw0xNTAzMjAwMDU2MDBaMDoxGDAW
BgNVBAMMD2pvaG5sQHRhdWdoLmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxA
dGF1Z2guY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnMGH
52DBxB4jb86Sxi3VvgOjirvLveIVP7zvqxBDpJzxrF02wCYwnQuxi3S3U5ge
3iHihzhM9qP+N03frkr4KH6Spgec88YjMioVQStTQZcrogTdHweZOgT8tckg
HEmHCF8uHBjD0HbfDk+9zYFtaE3QPk5aGm02Id0fNNM5WmSQSxVwF0Ddryq5
vIU0AHbB/1kok1zJpwWA06SgHenlnYngnSpNWlOn+SxboiD28m2XTWDP5ULL
e1b040VtkQMzpuVXzAHWVQYQWUevJ4y8mrUsqAyGuYSb5pTU28D+NExVAYxn
WD94rzgBpkXgC4Xxcp3TmyfMaLMF4M9ef0nu+QIDAQABo4IC1TCCAtEwCQYD
VR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSpNAr06FueusUfmbDdecnZ1kznsTAfBgNVHSME
GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0
YXVnaC5jb20wggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIB
KjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5
LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3Vl
ZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJl
bWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25s
eSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0
aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmg
J4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYI
KwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRz
c2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRw
Oi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5j
YS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0G
CSqGSIb3DQEBCwUAA4IBAQC3OSsHtuc1se2JPbLqI1b31i0EER3UX6Ep2Zuy
FkACIpk/i8mPi0KIfMWWiDlNmqeQEq8308i0/2mVcMVdgKWIUMJdZb3CmNfs
3qtTlrdXXYXT7ZLjL6a1Bbh/lKUm35JYRH8zf3rqDbLkpiA92vc7uTQcbDay
1sQ4CSTvOWuq0CIwMXqJePhHf/runG7ndDuX2yFagHlxhsvn7raw5NQuu4Sj
ofwbNiszwkryB7ZYUxq2Pg2i1m2XlgMbNEfw8deAZOyHGKKGz25Ei1KvJofH
1izh0WDU+ueJum6RHm8/o/i53MbYZN4Il64aBD1HPqQow3jHQBhAc8XN85hH
csS2MYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZp
Y2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCVhGMAkGBSsOAwIaBQCggdgw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQw
NDA4MDYyODE1WjAjBgkqhkiG9w0BCQQxFgQUR2m7TcZK6tlpqwBmfDoGhxWc
e6gweQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEW
MAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEggEAnGqW0izv/81QpFGUskBcVE4S2mazv2kS0BzXWVd7nKCf8sYb
OD1ojka08tYG2JcrWS8gQcBJwFcHD+g5xj+M2I9z0iRUi82+jJUmcRSIARls
5knRGA3FV4M3TMvwDiFKAiMABNsqjn5F9ODZNvmogOMVmVkxnDzdUL89e6v0
XjPYvFTjEGzo3SqT3KFu31ms+APLBMOISt1oDh2p9yqz+/FIrhqKCmwfFtno
jgj0qC8TDwUv2b5xpsME/yLOSGbHW6UHC34pST3XpqbnjOnpS7cqSoY22HMN
N0MYUm3JmRhtVhAR5DZ0Zj9i2NxDEDgtXl1OsDbnGyxSn4iFSsp0wg==

--3825401791-1373175125-1396938496=:73769--


From nobody Mon Apr  7 23:35:30 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E6A81A00E6 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 23:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.8
X-Spam-Level: 
X-Spam-Status: No, score=-1.8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=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 AAHlaRuXKxsQ for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 23:35:23 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DE8361A0032 for <ietf@ietf.org>; Mon,  7 Apr 2014 23:35:23 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.147.234]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s386Z5Yq017829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 7 Apr 2014 23:35:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1396938917; bh=GgkulmGwPhYQ6osUcFHBMXMaaXfskMLo1LfV2zRm3Qg=; h=Date:To:From:Subject:In-Reply-To:References; b=Fa/h21qH+mB8JOTufN5ySqLMcXH1BO83gRfU8Bp7/9thZ1eVxjUg4Kg9h8g7NhyIc bRBI7H8E+DpS4kfYAKNI+ugstY7NTL3gwwFRnUVFDEoLT2iPQ/WuGkxGTciyLJXh4T vMzwXwnqBsj/7k2voO3jbwfpsTL7pNKfCSm41swQ=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1396938917; i=@elandsys.com; bh=GgkulmGwPhYQ6osUcFHBMXMaaXfskMLo1LfV2zRm3Qg=; h=Date:To:From:Subject:In-Reply-To:References; b=U6VwXBWtspJINicoHGrpMCB5Ve/Z36onCurvefiV6j1XPG4wbOFC7r30ganIqDXS+ B6+xEvMfcnEf7MiZ2Li+Q0XCDfcyiov54DmKYhpbitks5GVxnKURyvXWDWvEkhfC+M R66PEbd6NkefDZgtXESJOwyqHyWzyW4RHe2UBc24=
Message-Id: <6.2.5.6.2.20140407214815.079d3670@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 07 Apr 2014 23:19:44 -0700
To: John Levine <johnl@taugh.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Yahoo breaks every mailing list in the world including the IETF's
In-Reply-To: <20140407201104.42050.qmail@joyce.lan>
References: <20140407201104.42050.qmail@joyce.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/K4ZIp5110ppdeHccAWkCnAD2dC8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 06:35:28 -0000

Hi John,
At 13:11 07-04-2014, John Levine wrote:
>DMARC is what one might call an emerging e-mail security scheme.
>There's a draft on it at draft-kucherawy-dmarc-base-04, intended for
>the independent stream.  It's emerging pretty fast, since many of the
>largest mail systems in the world have already implemented it,
>including Gmail, Hotmail/MSN/Outlook, Comcast, and Yahoo.

[snip]

>Mailing lists are a particular weak spot for DMARC.  Lists invarably
>use their own bounce address in their own domain, so the SPF doesn't
>match. Lists generally modify messages via subject tags, body footers,
>attachment stripping, and other useful features that break the DKIM
>signature.  So on even the most legitimate list mail like, say, the
>IETF's, most of the mail fails the DMARC assertions, not due to the
>lists doing anything "wrong".

 From BCP 167:

   "In an idealized world, if an Author knows that the MLM to which a
    message is being sent is a non-participating resending MLM, the
    Author needs to be cautious when deciding whether or not to send a
    signed message to the list."

It will be interesting to see the results when other domains 
implement the specification.

Regards,
S. Moonesamy



From nobody Mon Apr  7 23:58:43 2014
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63BFD1A014B; Mon,  7 Apr 2014 23:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 NJBHjiHz1Adf; Mon,  7 Apr 2014 23:58:35 -0700 (PDT)
Received: from p3plsmtpa09-08.prod.phx3.secureserver.net (p3plsmtpa09-08.prod.phx3.secureserver.net [173.201.193.237]) by ietfa.amsl.com (Postfix) with ESMTP id 265961A0146; Mon,  7 Apr 2014 23:58:29 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa09-08.prod.phx3.secureserver.net with  id nJyH1n0061huGat01JyHvd; Mon, 07 Apr 2014 23:58:24 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-ietf-opsec-lla-only.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-opsec-lla-only-07
Date: Mon, 7 Apr 2014 23:58:18 -0700
Message-ID: <012001cf52f7$f0361670$d0a24350$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac9S8v0hRSibx5myQkiFkifq7Hdr0g==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ilCoUsNzn-BZI4BWUUARzKhRpcE
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 06:58:39 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-ietf-opsec-lla-only-07
Reviewer: Peter Yee
Review Date: April-7-2014
IETF LC End Date: April-7-2014
IESG Telechat date: TBD

Summary: This draft is basically ready for publication as an Informational
RFC, but has issues that should be fixed before publication. [Ready with
issues.]

This document discusses the (controversial) use of IPv6 link-local addresses
on router infrastructure links.  I don't find all of the arguments for use
of link-local addresses to be terribly compelling, but I'm not utterly
averse to the document's publication as a summary of some of the pros and
cons for those who desire to configure their routers in the manner
prescribed.  There may be other reasons that should be taken into
consideration, but I lack a network operator's experience to discuss them.

Minor:

Page 4, 4th paragraph: I don't buy this argument.  DNS can be simplified for
non-link-local addresses by simply not registering those addresses in DNS.
Use of link-local addresses isn't a requirement to simplify DNS.

Page 4, 5th paragraph, 2nd sentence: SSH brute force password attacks aren't
really reduced unless the reduction is simply not being able to attack a
single router over multiple interfaces in parallel.  A better scheme for
reducing SSH brute force password attacks might be to limit the rate of
responses to SSH login attempts in the face of repeated failures.
Considering dropping this marginal example.

Page 4, 6th paragraph, 1st sentence: I'm not sure what is meant by "the same
result".  Is this in reference to all 5 paragraphs that precede the 6th?  If
so, you might wish to elaborate with "the same results as the above" .
However, if the same results can be obtained without going to link-local
addressing as this paragraph indicates, why is the use of link-local
addressing being suggested?  The paragraph might do well to explain why one
scheme is preferable over the other.

Page 6, 1st partial paragraph: the argument is made that "more work" is
required to discover all of an IXPs loopback interface addresses before a
generic attack can be mounted.  This wouldn't seem to be a lot of upfront
work and once it has been done, the advantage is negated.  I don't find the
argument particularly persuasive.  

Nits:

Page 2, Section 2 title: change "Address" to "Addressing".

Page 3, second paragraph: change "non link-local" to "non-link-local".

Page 4, 1st paragraph, 3rd sentence: change "accellerated" to "
accelerated".

Page 4, 5th paragraph, 2nd sentence: delete the comma after "[RFC4987])" and
change the "or" to "and".

Page 6, 1st full paragraph, 1st sentence: change "allow" to "allows" and
insert "an" before "MPLS LSP".


		-Peter Yee




From nobody Tue Apr  8 00:13:31 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4BF21A0141 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 00:13:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 IwEUVZEzhlFc for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 00:13:25 -0700 (PDT)
Received: from nk11p04mm-asmtp001.mac.com (nk11p04mm-asmtp001.mac.com [17.158.236.236]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEB91A0156 for <ietf@ietf.org>; Tue,  8 Apr 2014 00:13:25 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N3P0087SAPWD7A0@nk11p04mm-asmtp001.mac.com> for ietf@ietf.org; Tue, 08 Apr 2014 07:13:11 +0000 (GMT)
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <robbat2-20140408T051158-246173691Z@orbis-terrarum.net>
Date: Tue, 08 Apr 2014 08:13:05 +0100
Message-id: <D22EB61C-12A3-40A8-9886-1652DE1AE273@me.com>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com> <robbat2-20140408T051158-246173691Z@orbis-terrarum.net>
To: "Robin H. Johnson" <robbat2@gentoo.org>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXREEbG1oaGkdHB0lGUkdDRl5PWBoaHREKTEMXGx0EGx8SBBscHwQdHhAbHho fGhEKWE0XSxEKbX4XGhEKTFkXGxobGxEKWUkXEQpZXhdoY3kRCkNOF0sbHhpiTk0dWhhNHxl4c wcZEhodGxloEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHxIEGxwfBB0eEBseGh8bEQpeWRdhT39 zQxEKTEYXbGtrEQpDWhcYGxkEGxgZBBsTGAQZGhEKRFgXHhEKREkXGREKQkUXZlB9XR9tZBoFS GMRCkJOF2xwYHlAHWJSaRpiEQpCTBdnSR9teWkYfnJCTREKQmwXZWhlGG1NHBhDRk4RCkJAF29 CUF19TWl+HRtQEQpwZxdkHh4bYGhGQlIZaxEKcGgXZHBDRxJIYh19W2gRCnBoF2NfSHxFWkt4W Vl6EQpwaBdmXmhGR2FIZWJaThEKcGwXa2ZOa0FlX2ZTZwERCnBMF21OQVJNXEQZZhtoEQ==
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-08_02:2014-04-07,2014-04-08,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404080002
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ysl6EXc75qEb31yoXgs4Olq2j4o
Cc: John Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 07:13:30 -0000

On 8 Apr 2014, at 06:16, Robin H. Johnson <robbat2@gentoo.org> wrote:
> And don't start on suggesting Reply-To instead, RFC 2822 already
> noted that it should be set by the author, not the list software [1].

Not that I disagree, but be sure to read the note in RFC 5598 s5.3.

Cheers,
Sabahattin


From nobody Tue Apr  8 02:21:17 2014
Return-Path: <eric.gray@ericsson.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE96F1A01CE; Tue,  8 Apr 2014 02:21:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 RbOCSpimqaZb; Tue,  8 Apr 2014 02:21:07 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id C62C81A01E1; Tue,  8 Apr 2014 02:20:56 -0700 (PDT)
X-AuditID: c6180641-b7f638e000005a82-2a-5343bc8b6732
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 3A.43.23170.B8CB3435; Tue,  8 Apr 2014 11:08:27 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0174.001; Tue, 8 Apr 2014 05:20:49 -0400
From: Eric Gray <eric.gray@ericsson.com>
To: "mrex@sap.com" <mrex@sap.com>, John C Klensin <john-ietf@jck.com>
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: AQHPT1jaUgQIQyDGsUaNKSIZ0ommd5sB/xWAgAD9boCAAJD7gIACoZaAgAAIKACAAA6ggIAAIe8AgAAQjwCAAHmFAIAAhs/A
Date: Tue, 8 Apr 2014 09:20:48 +0000
Message-ID: <48E1A67CB9CA044EADFEAB87D814BFF632A52848@eusaamb107.ericsson.se>
References: <DC23F34E807E77F8C4C095C3@JcK-HP8200.jck.com> <20140407211718.60C021ACAA@ld9781.wdf.sap.corp>
In-Reply-To: <20140407211718.60C021ACAA@ld9781.wdf.sap.corp>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.9]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrHLMWRmVeSWpSXmKPExsUyuXRPgm73Hudgg7k/DCxm/JnIbPFs43wW i9ZLf9gsen/vYLY493QOo8XSP/NZHNg8pvzeyOqxZMlPJo/LK18ze0z5vJXR49LSycwBrFFc NimpOZllqUX6dglcGbM+n2Qv2CJaMf3qJPYGxg2CXYycHBICJhIt/9ayQdhiEhfurQeyuTiE BI4ySkzc1MME4SxjlGj9N5cJpIpNQEPi2J21jCC2iICrxJOvv5lBipgFWhklrsxZyt7FyMEh LKAvcbI7FqLGQGLJlp+sEHaexKJP7xlBSlgEVCQmbfIGMXkFfCU2zK4FMYUEsiWezBIBKeYU sJH4cGQ12CJGoNO+n1oDdgCzgLjErSfzmSBOFpBYsuc8M4QtKvHy8T9WCFtRYl//dHaIeh2J Bbs/sUHY2hLLFr4Gq+cVEJQ4OfMJywRGsVlIxs5C0jILScssJC0LGFlWMXKUFqeW5aYbGW5i BMbZMQk2xx2MCz5ZHmKU5mBREuf98tY5SEggPbEkNTs1tSC1KL6oNCe1+BAjEwenVAMj850C xV8f7ry8+iOnZua1wI5Xr2IfscluP7LX9llq0lrpKd29VVZc3ULrzjVuZNEX/KudE/tCovGM JXcQ1xux/GksPseuXi73Ozp3Af+lu8KMzLmp9kzv2H6k2/Nerg3wc1IUm5SyX4lj5+row3+e HDZeEnbULZZlr/2CNxfDK04mFs8VkKtXYinOSDTUYi4qTgQAWDr5L4ECAAA=
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rhGFLdOqI1uYmC_0vWdhK-ydcBQ
Cc: Stewart Bryant <stbryant@cisco.com>, Tim Bray <tbray@textuality.com>, IETF-Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 09:21:12 -0000

Martin,

	You say "_the_real_TLS_protocol_characteristics_" like they are written do=
wn
somewhere.

	Would you care to provide a pointer?

--
Eric

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Martin Rex
Sent: Monday, April 07, 2014 5:17 PM
To: John C Klensin
Cc: IETF-Discussion; Tim Bray; The IESG; Stewart Bryant
Subject: Re: Security for various IETF services

John C Klensin wrote:
>=20
> Ted Lemon <ted.lemon@nominum.com> wrote:
>>
>> Stephen Farrell <stephen.farrell@cs.tcd.ie> wrote:
>>>
>>> Yes, we ought move away from passwords if/when we ever find an
>>> acceptably better solution, and yes, people ought manage their
>>> passwords well, but neither are today's reality more's the
>>> pity.
>>=20
>> Perhaps it would be worth setting up support for client certs
>> as a way to log in to IETF services.   If we won't start, why
>> would someone else?
>=20
> If we are really serious about promoting/ encouraging security,
> I'd really like to see this as an option.  Not only would it be
> responsive to Ted's question, but, if we made it available and
> almost no one used it, it would give us a lot of information
> about the course we are on.

TLS _client_ certificates are typically used in closed groups,
where a single CA is issuing all these certs.

TLS client cert authentication has a few small issues.  The TLS server
needs to explicitly request the client cert (unsolicited client certs
are not possible/not allowed), and when the server asks for them
in the initial handshake, the client certificates will travel the
network _in_the_clear_.  Requesting client certificates only in the
renegotiation handshake has it own set of problems, besides twice
the full handshake crypto overhead.  For TLS renego problems and fixes
see rfc5746 and https://secure-resumption.com/



I also think that discontinuing the _public_ services of the IETF
over traditional, insecure channels (HTTP, anon-FTP, plain SMTP, whatever)
should require a threat analysis.

Different to what a lot of folks believe, TLS is neither a panacea nor
magic pixie dust.  In order to determine whether doing X-over-TLS really
provides the desired security characteristics, it is necessary to know
what security properties one is looking for.

The reason why there was an issue with TLS renegotiation is that applicatio=
ns
boldly assumed properties which never existed in the first place -- and
that problem would have been obvious if anyone of those abusing
TLS renegotiation for delayed authentication would have actually cared
to check for _the_real_TLS_protocol_characteristics_ instead of
believing in TLS magic pixie dust.


-Martin


From nobody Tue Apr  8 05:50:12 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D5711A0375 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 05:50:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 rSGsL7g70irF for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 05:50:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D03781A0396 for <ietf@ietf.org>; Tue,  8 Apr 2014 05:50:05 -0700 (PDT)
Received: from [10.168.69.12] (pool-71-164-185-121.dllstx.fios.verizon.net [71.164.185.121]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s38CnsW6012553 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 8 Apr 2014 05:49:58 -0700
Message-ID: <5343F003.4080505@dcrocker.net>
Date: Tue, 08 Apr 2014 07:48:03 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Sabahattin Gucukoglu <listsebby@me.com>, "Robin H. Johnson" <robbat2@gentoo.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com> <robbat2-20140408T051158-246173691Z@orbis-terrarum.net> <D22EB61C-12A3-40A8-9886-1652DE1AE273@me.com>
In-Reply-To: <D22EB61C-12A3-40A8-9886-1652DE1AE273@me.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 08 Apr 2014 05:49:59 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dyn88t9Qju2oipqwiKy0B4yWZyg
Cc: John Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 12:50:10 -0000

On 4/8/2014 2:13 AM, Sabahattin Gucukoglu wrote:
> On 8 Apr 2014, at 06:16, Robin H. Johnson <robbat2@gentoo.org> wrote:
>> And don't start on suggesting Reply-To instead, RFC 2822 already
>> noted that it should be set by the author, not the list software [1].
>
> Not that I disagree, but be sure to read the note in RFC 5598 s5.3.


Section 5.3 has no "note". I assume you mean the portion on mailing lists:

      5.3. Mailing Lists
      ...
       RFC5322.Reply-To:  Set by - Mediator or original Author

          Although problematic, it is common for a Mailing List to assign
          its own addresses to the Reply-To: header field of messages
          that it posts.  This assignment is intended to ensure that
          replies go to all list members, rather than to only the
          original Author.  As a User Actor, a Mailing List is the Author
          of the new message and can legitimately set the Reply-To:
          value.  As a Mediator attempting to represent the message on
          behalf of its original Author, creating or modifying a
          Reply-To: field can be viewed as violating that Author's
          intent.  When the Reply-To is modified in this way, a reply
          that is meant only for the original Author will instead go to
          the entire list.  When the Mailing List does not set the field,
          a reply meant for the entire list can instead go only to the
          original Author.  At best, either choice is a matter of group
          culture for the particular list.


To the extent anyone wants to claim that this is in conflict with RFC 
5322, it's helpful to remember that a mailing list is a 'mediator' and 
not an MTA.

So it took delivery of a message and is posting a /new/ one.  In formal 
terms, the "author" of the new message is the mailing list; hence it 
gets to set Reply-To...

Consequently, the ending clause in "it should be set by the author, not 
the list software" is not correct.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Apr  8 06:03:39 2014
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C51971A03AB for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 06:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.691
X-Spam-Level: *
X-Spam-Status: No, score=1.691 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_03_06=1.592, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=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 kkQXCMibzsxw for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 06:03:34 -0700 (PDT)
Received: from emea01-db3-obe.outbound.protection.outlook.com (mail-db3lp0083.outbound.protection.outlook.com [213.199.154.83]) by ietfa.amsl.com (Postfix) with ESMTP id C3EC71A03A5 for <ietf@ietf.org>; Tue,  8 Apr 2014 06:03:33 -0700 (PDT)
Received: from DBXPRD0510HT002.eurprd05.prod.outlook.com (157.56.252.165) by DB4PR07MB251.eurprd07.prod.outlook.com (10.242.231.151) with Microsoft SMTP Server (TLS) id 15.0.913.9; Tue, 8 Apr 2014 13:03:32 +0000
Message-ID: <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com>
Subject: Re: Security for various IETF services
Date: Tue, 8 Apr 2014 09:32:00 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [157.56.252.165]
X-ClientProxiedBy: DB4PR07CA040.eurprd07.prod.outlook.com (10.242.229.50) To DB4PR07MB251.eurprd07.prod.outlook.com (10.242.231.151)
X-Forefront-PRVS: 017589626D
X-Forefront-Antispam-Report: =?iso-8859-1?Q?SFV:NSPM; SFS:(10009001)(6009001)(428001)(24454002)(199002)?= =?iso-8859-1?Q?(189002)(51704005)(13464003)(479174003)(377454003)(6223600?= =?iso-8859-1?Q?2)(44716002)(44736004)(4396001)(59766001)(77982001)(956660?= =?iso-8859-1?Q?03)(49866001)(47736001)(90146001)(79102001)(47976001)(5098?= =?iso-8859-1?Q?6001)(51856001)(42186004)(19580395003)(88136002)(62966002)?= =?iso-8859-1?Q?(50466002)(56776001)(87286001)(87266001)(14496001)(7470600?= =?iso-8859-1?Q?1)(15975445006)(56816005)(15202345003)(89996001)(94946001)?= =?iso-8859-1?Q?(66066001)(83322001)(93136001)(81342001)(80022001)(1958040?= =?iso-8859-1?Q?5001)(65816001)(87976001)(81542001)(86362001)(551544002)(9?= =?iso-8859-1?Q?3916002)(74366001)(92726001)(33646001)(47776003)(95416001)?= =?iso-8859-1?Q?(50226001)(23756003)(74876001)(63696002)(76482001)(9733600?= =?iso-8859-1?Q?1)(93516002)(80976001)(84392001)(69226001)(53806001)(76786?= =?iso-8859-1?Q?001)(31966008)(77156001)(94316002)(61296002)(74502001)(474?= =?iso-8859-1?Q?46002)(74662001)(46102001)(99396002)(76796001)(54316002)(9?= =?iso-8859-1?Q?2566001)(20776003)(97186001)(85852003)(77096001)(85306002)?= =?iso-8859-1?Q?(98676001)(83072002)(74416001)(7726001);DIR:OUT;SFP:1101;S?= =?iso-8859-1?Q?CL:1;SRVR:DB4PR07MB251;H:DBXPRD0510HT002.eurprd05.prod.out?= =?iso-8859-1?Q?look.com;FPR:FCDCC0D9.8EEA77FA.3DD9917F.8BE65339.20363;MLV?= =?iso-8859-1?Q?:nov;PTR:InfoNoRecords;A:0;MX:1;LANG:en;?=
Received-SPF: None (: btconnect.com does not designate permitted sender hosts)
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/L_LsIwzCyVq4ogmhDmIMKF0GgrM
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 13:03:37 -0000

----- Original Message -----
From: "Spencer Dawkins" <spencerdawkins.ietf@gmail.com>
To: "Ted Lemon" <ted.lemon@nominum.com>; "Stephen Farrell"
<stephen.farrell@cs.tcd.ie>
Sent: Monday, April 07, 2014 3:12 PM
> On 04/07/2014 08:03 AM, Ted Lemon wrote:
> > On Apr 7, 2014, at 7:01 AM, Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:
> >> Yes, we ought move away from passwords if/when we ever find an
> >> acceptably better solution, and yes, people ought manage their
> >> passwords well, but neither are today's reality more's the pity.
> > Perhaps it would be worth setting up support for client certs as a
way to log in to IETF services.   If we won't start, why would someone
else?
>
> (Speaking as 1/15th, but only 1/15th, of the IESG that's asking for
> community input on this topic)
>
> For me, "If we won't start, why would someone else?" was a significant
> consideration. I'm not locked in on any particular path, but I thought
> it was useful to ask about this was that if the IETF can't make an
> improved security environment work, that's not a good sign
> (http://en.wikipedia.org/wiki/Eating_your_own_dog_food).

The path that I have seen several Security ADs steer Working Groups down
is to start with a threat analysis before deciding what counter measures
are appropriate.

Here, we seem to be following a path of 'We have got TLS with server
certs (which is pretty useless against most threats) so we will impose
that on everyone and call it an improved security environment'.

Solution first, requirements ignored.  This is not what I think of as
engineering.

Tom Petch

> We can spin up new working groups to address problems we encounter.
Most
> communities seeking to improve their security environment can't do
that.
>
> So, from my own perspective, on-by-default would be sufficient to find
> out what I'd like to find out ... but I'd love to find out at least
part
> of what we'd like to know, in a post-Snowdon world.
>
> We could find out something, without making Stewart run a
> state-of-the-art secure environment on his IoT device to FTP Internet
> Drafts.
>
> Spencer


From nobody Tue Apr  8 07:06:56 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABA71A0401 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 07:06:47 -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, SPF_PASS=-0.001] autolearn=ham
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 rFwXVGLV0_K0 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 07:06:40 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 44C221A03FD for <ietf@ietf.org>; Tue,  8 Apr 2014 07:06:40 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id gq1so1033653obb.4 for <ietf@ietf.org>; Tue, 08 Apr 2014 07:06:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=79vM/BXJO5JUVg6bCU8PEaY4K+2BF9uoY/ZyzCRsZ6U=; b=Wvv6V0ZtULnzDit+GF/qui9yUNJ25lnR4erMy4Zf8ePyZZRyuLuYj77FUb2+Ikoj68 VkALAtP9oH9N3kBJ6s0n4b4ZEbhlu19toS36h82P7V56nipsg3mowTR36l2IwVi5CRkj 97eOtJe3AuNE+z5znDak1WXBxAdG2HhHF3hTxk76KUqS0IafIy6ATZqiewz8zsXs99Nd Y/+1JbnaKR3rEJtc0hHGOHGjd8tbIO4SB9fA24onME28OqdBP/6o/dyAROv7EJ8ykxhs I5VbiDsyLBhmE6of3ijVXAw08R+hFF3rTe+Yi8oLcM6clXE0ZLEKzDZ8PVCy+e3Gv0Co BlBQ==
X-Received: by 10.182.241.67 with SMTP id wg3mr3537312obc.16.1396966000068; Tue, 08 Apr 2014 07:06:40 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Tue, 8 Apr 2014 07:06:18 -0700 (PDT)
In-Reply-To: <AE1A6B5FD507DC4FB3C5166F3A05A484504B5176@TK5EX14MBXC298.redmond.corp.microsoft.com>
References: <533D8A90.60309@cs.tcd.ie> <53417832.90405@cs.tcd.ie> <alpine.LRH.2.01.1404061602580.14892@egate.xpasc.com> <ecabb0a4080548d99ab083c0ff0c27ee@BLUPR03MB424.namprd03.prod.outlook.com> <AE1A6B5FD507DC4FB3C5166F3A05A484504B5176@TK5EX14MBXC298.redmond.corp.microsoft.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Tue, 8 Apr 2014 10:06:18 -0400
Message-ID: <CAPv4CP8ZiUnOfoNPBSqpoOHrgS2m2GNwNGmTJm+q0B=hq8y5-w@mail.gmail.com>
Subject: Re: Security for various IETF services
To: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
Content-Type: multipart/alternative; boundary=001a11c2efb832902404f6887e79
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hUySrQ2xiiYxKCrYlqrrGt1isko
Cc: Christian Huitema <huitema@microsoft.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 14:06:47 -0000

--001a11c2efb832902404f6887e79
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 7, 2014 at 3:50 PM, Matthew Kaufman (SKYPE) <
matthew.kaufman@skype.net> wrote:

> If the same level of urgency were shown towards a viable, and secure,
> replacement for TCP itself, then the calls for secure-only access to IETF
> services might make sense. Instead, it feels a lot like requiring stronger
> deadbolts on glass doors.


FYI http://trac.tools.ietf.org/group/ppm-legacy-review/ticket/9

--001a11c2efb832902404f6887e79
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On M=
on, Apr 7, 2014 at 3:50 PM, Matthew Kaufman (SKYPE) <span dir=3D"ltr">&lt;<=
a href=3D"mailto:matthew.kaufman@skype.net" target=3D"_blank">matthew.kaufm=
an@skype.net</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">If the same level of urgency were shown towards a viable, =
and secure, replacement for TCP itself, then the calls for secure-only acce=
ss to IETF services might make sense. Instead, it feels a lot like requirin=
g stronger deadbolts on glass doors.</blockquote>

<div><br></div><div>FYI <a href=3D"http://trac.tools.ietf.org/group/ppm-leg=
acy-review/ticket/9">http://trac.tools.ietf.org/group/ppm-legacy-review/tic=
ket/9</a></div><div><br></div><div>=A0</div></div></div></div>

--001a11c2efb832902404f6887e79--


From robbat2@gentoo.org  Mon Apr  7 20:35:49 2014
Return-Path: <robbat2@gentoo.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34B3C1A00BC for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 20:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.412
X-Spam-Level: 
X-Spam-Status: No, score=-4.412 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 fNEqV6UDGLWn for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 20:35:42 -0700 (PDT)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by ietfa.amsl.com (Postfix) with ESMTP id 9F64D1A00AE for <ietf@ietf.org>; Mon,  7 Apr 2014 20:35:42 -0700 (PDT)
Received: from grubbs.orbis-terrarum.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 1C67933FF8A for <ietf@ietf.org>; Tue,  8 Apr 2014 03:35:36 +0000 (UTC)
Received: (qmail 28305 invoked by uid 10000); 8 Apr 2014 03:35:32 -0000
Date: Tue, 8 Apr 2014 03:35:32 +0000
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: johnl@taugh.com
Subject: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AsKt9WDFSpw8OJmf"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/j76xR2MwjeR0LdVdznM9kPkCivM
X-Mailman-Approved-At: Tue, 08 Apr 2014 08:48:29 -0700
Cc: ietf@ietf.org, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 03:37:56 -0000

--AsKt9WDFSpw8OJmf
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi,

I'm the listadmin (amongst other things) for Gentoo Linux. Our lists
handle somewhere north of 100k deliveries/day; it's a large deployment
of mlmmj.

I also happen to personally host the lists for my local hackerspace, and
that's where I first noticed DMARC causing problems, because one of our
members activated reject mode on his personal domain, and then all
yahoo+gmail recipients started having bounced mail whenever mail from
the DMARC-progressive user was sent.

I wrote up my findings here:
http://robbat2.livejournal.com/241253.html

If the listserv's outgoing MTA does implement DKIM signing, this problem
will still occur because it's legitimately valid for the From header to
differ from the envelope sender. That's why the extra DMARC header
X-Original-Authentication-Results [1] is needed sadly :-(.

The problem described WILL vanish when all mailing list apps implement
DMARC, but until then, it's really broken.

It's really bad because not a single list implementation supports DMARC
yet; mailman is the closest, but still not yet there.

If possible, if everybody could highlight the lack of open-source
support for DMARC in list apps, that would be hugely beneficial to the
cause.

At the same time, delaying mass usage of the reject policy would limit
damage.

[1] https://sites.google.com/site/oauthgoog/mlistsdkim

--=20
Robin Hugh Johnson
Gentoo Linux: Developer, Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85

--AsKt9WDFSpw8OJmf
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Robbat2 @ Orbis-Terrarum Networks - The text below is a digital signature. If it doesn't make any sense to you, ignore it.

iKYEARECAGYFAlNDboRfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl
bnBncC5maWZ0aGhvcnNlbWFuLm5ldDc1OTQwNEJFQkQ0MUY3MTIzODIzODZFRjNF
OTIyQzIyMzIzM0MyMkMACgkQPpIsIjIzwixitACg/Y+yd4sXtVBbfqL6wb2E2zGa
IuUAoPPPsS6d8aqxkC6+lVI3tAvVCg7g
=CXuH
-----END PGP SIGNATURE-----

--AsKt9WDFSpw8OJmf--


From nobody Tue Apr  8 08:51:54 2014
Return-Path: <robbat2@gentoo.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BE701A0122 for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:16:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.911
X-Spam-Level: 
X-Spam-Status: No, score=-6.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 5mj-Z8oKOFAa for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:16:31 -0700 (PDT)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by ietfa.amsl.com (Postfix) with ESMTP id 3F7081A0121 for <ietf@ietf.org>; Mon,  7 Apr 2014 22:16:27 -0700 (PDT)
Received: from grubbs.orbis-terrarum.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 3D38F33FFCB for <ietf@ietf.org>; Tue,  8 Apr 2014 05:16:21 +0000 (UTC)
Received: (qmail 11473 invoked by uid 10000); 8 Apr 2014 05:16:18 -0000
Date: Tue, 8 Apr 2014 05:16:18 +0000
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <robbat2-20140408T051158-246173691Z@orbis-terrarum.net>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cc39SlSbB-IifpNOQRlc6V0L4Us
X-Mailman-Approved-At: Tue, 08 Apr 2014 08:51:50 -0700
Cc: John Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>, "Robin H. Johnson" <robbat2@gentoo.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 05:16:35 -0000

On Tue, Apr 08, 2014 at 06:06:27AM +0100, Sabahattin Gucukoglu wrote:
> On 8 Apr 2014, at 05:21, John R Levine <johnl@taugh.com> wrote:
> > Mailing list apps can't "implement DMARC" other than by getting rid
> > of every feature that makes lists more functional than simple
> > forwarders. Given that we haven't done so for any of the previous
> > FUSSPs that didn't contemplate mailing lists, because those features
> > are useful to our users, it seems unlikely we'll do so now.
> Well,  Mailman 2.1.16 has the FROM_IS_LIST feature that "Fixes" the
> problem by putting the list address in the From: field.  That seems to
> work, except that you lose information (the sender's address) if the
> list wants to operate a policy of "Reply goes to list".  You can then
> assure that DKIM signatures are valid and set up SPF, etc.  This also
> has the effect of letting you operate through the various cloud email
> platforms that try to validate sender addresses.
This breaks the ability to reply directly to the sender when the
response should NOT be on the list, as well as the ability to put a
sender in a personal killfile.

And don't start on suggesting Reply-To instead, RFC 2822 already
noted that it should be set by the author, not the list software [1].

[1] http://marc.merlins.org/netrants/listreplyto.html List Reply-To
considered harmful.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85


From nobody Tue Apr  8 08:55:25 2014
Return-Path: <robbat2@gentoo.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 962DF1A012C for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.311
X-Spam-Level: 
X-Spam-Status: No, score=-6.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_34=0.6, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 xsWY8fMzSuds for <ietf@ietfa.amsl.com>; Mon,  7 Apr 2014 22:38:00 -0700 (PDT)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by ietfa.amsl.com (Postfix) with ESMTP id D62DA1A012F for <ietf@ietf.org>; Mon,  7 Apr 2014 22:38:00 -0700 (PDT)
Received: from grubbs.orbis-terrarum.net (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id 19A3B33FF98 for <ietf@ietf.org>; Tue,  8 Apr 2014 05:37:55 +0000 (UTC)
Received: (qmail 15095 invoked by uid 10000); 8 Apr 2014 05:37:52 -0000
Date: Tue, 8 Apr 2014 05:37:52 +0000
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: John R Levine <johnl@taugh.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <20140408053752.GB2858@orbis-terrarum.net>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IfZ+tgy+ooJOsAAy"
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1404072357400.73388@joyce.lan>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ExLDjDyb5mrmqTyrybJ_l-xGN9E
X-Mailman-Approved-At: Tue, 08 Apr 2014 08:55:21 -0700
Cc: IETF general list <ietf@ietf.org>, "Robin H. Johnson" <robbat2@gentoo.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 05:38:05 -0000

--IfZ+tgy+ooJOsAAy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Apr 08, 2014 at 12:21:46AM -0400, John R Levine wrote:
> You would have to track which forwarders are well behaved and add
> valid X-O-A-R headers, but if you can do that, you can skip the header
> analysis and just whitelist the mail from the well behaved forwarders.

The XOAR proposal does specify:
| The X-Original-Authentication-Results header is only useful if the
| forwarder is trusted.  The forwarder is free to modify the headers and
| body of the message however it wishes and can generate new signatures
| over arbitrary X-Original-Authentication-Results headers.  Thus, the
| user SHOULD only trust X-Original-Authentication-Results if the message
| was delivered by known good forwarders, and forwarders SHOULD NOT
| propagate X-Original-Authentication-Results unless the previous
| forwarder is known to be good.
|
| For the purposes of this memo, a message was delivered through trusted
| forwarder if:
| - The DKIM signature passes
| - The DKIM domain is a trusted forwarder

I think the original scenario you described could be implemented by bad
players as follows:
- set up a mailman instance with DMARC support, that forges the XOAR
  header.
- Ensure that the mailman outgoing mail passes SPF+DKIM for the domain
  in question.


> Note that there are also well behaved things that don't pass DMARC and=20
> don't have any original authentication results to report, with the usual=
=20
> examples being mail-an-article at the NY Times and Wall Street Journal.
Those uses shouldn't be considered valid, and NYTimes has already moved
away from that, at least as of my test 5 minutes ago.
| MAIL FROM:<emailthis@ms3.lga2.nytimes.com>
| RCPT TO:<robbat2@gentoo.org>
| DATA
| ...
| From: robbat2 <emailthis@ms3.lga2.nytimes.com>
| Sender: emailthis@ms3.lga2.nytimes.com
| To: robbat2@gentoo.org
| ...

> > The problem described WILL vanish when all mailing list apps implement
> > DMARC, but until then, it's really broken.
> Mailing list apps can't "implement DMARC" other than by getting rid of=20
> every feature that makes lists more functional than simple forwarders.=20
> Given that we haven't done so for any of the previous FUSSPs that didn't=
=20
> contemplate mailing lists, because those features are useful to our users=
,=20
> it seems unlikely we'll do so now.
By implement DMARC, I meant implement XOAR headers; VERP is too useful
to running lists to get rid of. Non-VERP bounce messages are still too
generic, even in this modern day.

--=20
Robin Hugh Johnson
Gentoo Linux: Developer, Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85

--IfZ+tgy+ooJOsAAy
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Robbat2 @ Orbis-Terrarum Networks - The text below is a digital signature. If it doesn't make any sense to you, ignore it.

iKYEARECAGYFAlNDizBfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3Bl
bnBncC5maWZ0aGhvcnNlbWFuLm5ldDc1OTQwNEJFQkQ0MUY3MTIzODIzODZFRjNF
OTIyQzIyMzIzM0MyMkMACgkQPpIsIjIzwixILACgiULnm4vncyww43wc3sMtpDZt
dVoAmgL+C3GpLar5FWHE6o7EB3DKedYE
=qfhG
-----END PGP SIGNATURE-----

--IfZ+tgy+ooJOsAAy--


From nobody Tue Apr  8 10:07:40 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF71B1A049A for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:07:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.526
X-Spam-Level: 
X-Spam-Status: No, score=0.526 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 j8YqLVbcO-hP for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:07:33 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id CE0691A03C4 for <ietf@ietf.org>; Tue,  8 Apr 2014 10:07:33 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6EEISF9MO005173@mauve.mrochek.com> for ietf@ietf.org; Tue, 8 Apr 2014 10:02:33 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6A66V86WW00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 8 Apr 2014 10:02:26 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6EEIPML6600004W@mauve.mrochek.com>
Date: Tue, 08 Apr 2014 09:52:40 -0700 (PDT)
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-reply-to: "Your message dated Tue, 08 Apr 2014 00:21:46 -0400" <alpine.BSF.2.00.1404072357400.73388@joyce.lan>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan>
To: John R Levine <johnl@taugh.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bAyz5rNpjkrpLjOgo8kfrHWlMGw
Cc: IETF general list <ietf@ietf.org>, "Robin H. Johnson" <robbat2@gentoo.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 17:07:36 -0000

> > The problem described WILL vanish when all mailing list apps implement
> > DMARC, but until then, it's really broken.

> Mailing list apps can't "implement DMARC" other than by getting rid of
> every feature that makes lists more functional than simple forwarders.
> Given that we haven't done so for any of the previous FUSSPs that didn't
> contemplate mailing lists, because those features are useful to our users,
> it seems unlikely we'll do so now.

Actually, mailing lists *can* implement DMARC, just not that way: Do a DMARC
check on all incoming messages, and if the domain policy is one that is
incompatible with the list's own policies - whatever they are - either change
the list's policies to conform to that message or reject it outright,
preferably with a nasty "find another a better mail provider" sort of message.

If the IETF wants to take a leadership position in regards to this issue,
perhaps someone could set this up.

> If receivers want to implement DMARC policy, they need to make their false
> alarm whitelist first.  This appears to be a substantial, perhaps
> insurmountable, hurdle.

> > At the same time, delaying mass usage of the reject policy would limit
> > damage.

> Reject policy is fine for domains that don't have individual human users,
> or for companies with firm staff policies that all mail goes through the
> company mail server, and employees don't join mailing lists and the like
> using company addresses, or the company provides a separate less strictly
> managed domain for its staff mail. Strict policies will never be
> appropriate for public webmail systems where the users will use their mail
> addresses any way one can use a mail address.  Yahoo appears to understand
> most of this, viz. the different domain for Elizabeth's company mail.

Which is why support for such policies is even in the specification. The
problem is there's no way to stop inappropriate use of such politicies in
advance of it happening. The best you can do is apply the clue-by-four later.

				Ned


From nobody Tue Apr  8 10:22:39 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A375D1A0473 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:22:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 rs9V24qqpj5y for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:22:27 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 427441A045E for <ietf@ietf.org>; Tue,  8 Apr 2014 10:22:13 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.104]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s38HLaWb011516 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Apr 2014 10:21:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1396977709; bh=fZtlQMUPOeIUryiXhNTC5k3E19VHfktnnCRz0rKuYV0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=mUccinNxrNS/OeRKbCo5/+YhFxmehuTxcdtc29WvRwPyoNOtbFf5jMvWXEUgSkuoq qqSzd2U9o/9TBuPQv+wfC43ymcn/9km2x3+QFoafW1F1mL2X+EzWZvNej9l2we4+j0 6OO5oeNnVr0+y27BSPJosYBJCzYpH58n2sgOITTE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1396977709; i=@elandsys.com; bh=fZtlQMUPOeIUryiXhNTC5k3E19VHfktnnCRz0rKuYV0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qDIeGYwdnOTurWrirsnWazPbigh+Y4+d7QWlthUQFlgVjzWsRcTDixrsJT2W4gZ2O vBrT7N3V1PBIMK8FKAG1pJJX4hs3Vg5RuKnpePcpqG0Xylc9e1nTFZpynZzo2saSPO /w+mlme2yLsQFqBf26BF6FI7aUJPxSwhrMfMLP1k=
Message-Id: <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Apr 2014 10:19:57 -0700
To: ned+ietf@mauve.mrochek.com, John R Levine <johnl@taugh.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <01P6EEIPML6600004W@mauve.mrochek.com>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Hbhw1njQELcxPSz8-o2fmFC6mbg
Cc: ietf@ietf.org, "Robin H. Johnson" <robbat2@gentoo.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 17:22:32 -0000

Hi Ned,
At 09:52 08-04-2014, ned+ietf@mauve.mrochek.com wrote:
>Actually, mailing lists *can* implement DMARC, just not that way: Do a DMARC
>check on all incoming messages, and if the domain policy is one that is
>incompatible with the list's own policies - whatever they are - either change
>the list's policies to conform to that message or reject it outright,
>preferably with a nasty "find another a better mail provider" sort of message.

There is some Mailman code which does the above.

>If the IETF wants to take a leadership position in regards to this issue,
>perhaps someone could set this up.

I did a search before asking this question; I did not find any 
answer.  Does anyone know whether the IETF adheres to BCP 167?

Regards,
S. Moonesamy


From nobody Tue Apr  8 10:34:41 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10BEA1A0671 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.043
X-Spam-Level: *
X-Spam-Status: No, score=1.043 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 iU_thJVlB7WF for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:34:38 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 92DCA1A0659 for <ietf@ietf.org>; Tue,  8 Apr 2014 10:34:37 -0700 (PDT)
Received: (qmail 48104 invoked from network); 8 Apr 2014 17:34:35 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=bbe7.5344332b.k1404; bh=eWEaO9rEJkwv6uJHFDRDOA6GUHWFd3jrMpT9faEsPq4=; b=EzV74tG6EWNOEWzWJIwNCiy4ZXeGxmMVbhIU0xLN/lcGqqECJYEaThd7zm1mUfDOfhSo9UiVDQeNlKBI3GQZ7ApdTPphe9dhHGfxrlkbw4B1/eYPg9NMdSs30fWy0s6hjEO4TtxiqmDwESUFwtX2RIezMaoYHV5pRmA05WDal1awlLnGAPzSsqZxfWQ2tBfEU7ysEWG/pbf9v/DoMZ6rwBwVylsX3jdaBLIOLrQj2SVtcfJpBvm75JW9OL44bpAY
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=bbe7.5344332b.k1404; bh=eWEaO9rEJkwv6uJHFDRDOA6GUHWFd3jrMpT9faEsPq4=; b=f8+27IvPkEeibOUf/CyHvzephEA51O7IQ4BhfY5peB4/FlXg/1wRTQ/hpirB4NIbRHE1Fu/5gICAbViSJZvQLmu7CNehrUSM/tKKCmbKC+YKSJKewyPHMiv5MxAuD0yeepHJiXkma+sbA8ML8NUwn/HaBRrPp5+9aB6vYfoR7RP4CbamrLymiSf5VZoNNbn0t64H7s8bE1n+GbenRh/NZKbNtot5A0pFqIV6IQNf904PTmUKqTKhbh/FjXaAFIwF
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 08 Apr 2014 17:34:35 -0000
Date: 8 Apr 2014 13:34:35 -0400
Message-ID: <alpine.BSF.2.00.1404081325130.76892@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "S Moonesamy" <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-2006038437-1396978475=:76892"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/opx9xiTACtQr3rXBGSKmJ4SXv3k
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 17:34:39 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-2006038437-1396978475=:76892
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> I did a search before asking this question; I did not find any answer.  Does 
> anyone know whether the IETF adheres to BCP 167?

I've never been a big fan of RFC 6377, but this bit seems relevant since 
strict ADSP policies had pretty much the same problems as strict DMARC 
policies.

    For domains that do publish strict ADSP policies, the originating
    site SHOULD use a separate message stream (see Section 2.5), such as
    a signing and Author subdomain, for the "personal" mail -- a
    subdomain that is different from domain(s) used for other mail
    streams.  This allows each to develop an independent reputation, and
    more stringent policies (including ADSP) can be applied to the mail
    stream(s) that do not go through mailing lists or perhaps do not get
    signed at all.

As far as I know, the "participating MLM" thing has never been 
implemented, which makes the C in BCP rather suspect.  My own MLM signs 
the outgoing mail and adds an Authentication-Results: header, but largely 
by default because it's embedded in a mail system that does those things.

Just today I did modify it so that any list mail with a From: address 
@yahoo.com is re written to @yahoo.com.INVALID.  That's the least 
intrusive way I've been able to come up with to mitigate the damage. 
It's also similar to what RFC 6858 suggests for delivering EAI mail to 
systems that can't handle EAI, which is a vaguely similar problem.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
--3825401791-2006038437-1396978475=:76892
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIII7gYJKoZIhvcNAQcCoIII3zCCCNsCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBh8wggYbMIIFA6ADAgECAgMJWEYwDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xNDAzMTgxOTQ3NDdaFw0xNTAzMjAwMDU2MDBaMDoxGDAW
BgNVBAMMD2pvaG5sQHRhdWdoLmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxA
dGF1Z2guY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnMGH
52DBxB4jb86Sxi3VvgOjirvLveIVP7zvqxBDpJzxrF02wCYwnQuxi3S3U5ge
3iHihzhM9qP+N03frkr4KH6Spgec88YjMioVQStTQZcrogTdHweZOgT8tckg
HEmHCF8uHBjD0HbfDk+9zYFtaE3QPk5aGm02Id0fNNM5WmSQSxVwF0Ddryq5
vIU0AHbB/1kok1zJpwWA06SgHenlnYngnSpNWlOn+SxboiD28m2XTWDP5ULL
e1b040VtkQMzpuVXzAHWVQYQWUevJ4y8mrUsqAyGuYSb5pTU28D+NExVAYxn
WD94rzgBpkXgC4Xxcp3TmyfMaLMF4M9ef0nu+QIDAQABo4IC1TCCAtEwCQYD
VR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSpNAr06FueusUfmbDdecnZ1kznsTAfBgNVHSME
GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0
YXVnaC5jb20wggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIB
KjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5
LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3Vl
ZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJl
bWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25s
eSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0
aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmg
J4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYI
KwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRz
c2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRw
Oi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5j
YS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0G
CSqGSIb3DQEBCwUAA4IBAQC3OSsHtuc1se2JPbLqI1b31i0EER3UX6Ep2Zuy
FkACIpk/i8mPi0KIfMWWiDlNmqeQEq8308i0/2mVcMVdgKWIUMJdZb3CmNfs
3qtTlrdXXYXT7ZLjL6a1Bbh/lKUm35JYRH8zf3rqDbLkpiA92vc7uTQcbDay
1sQ4CSTvOWuq0CIwMXqJePhHf/runG7ndDuX2yFagHlxhsvn7raw5NQuu4Sj
ofwbNiszwkryB7ZYUxq2Pg2i1m2XlgMbNEfw8deAZOyHGKKGz25Ei1KvJofH
1izh0WDU+ueJum6RHm8/o/i53MbYZN4Il64aBD1HPqQow3jHQBhAc8XN85hH
csS2MYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZp
Y2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCVhGMAkGBSsOAwIaBQCggdgw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQw
NDA4MTczNDM1WjAjBgkqhkiG9w0BCQQxFgQU3mckBSW9oVUuW8AES7VBeZ19
hGoweQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEW
MAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEggEAOAp1j/jPEWR33UrW5rMc77eSCY1qqWcaH+KZbEyu7bCB4oAX
mVR9WUEpm9xXG7A2u05ehXt4pVgjqZVZqZw10w8f7PoE+N7kdoX/xJ3qaQzx
HD433k1qmnFthafEXtAgFwIDiTdtCCmmlslHKi2eQ8bqMbD6gKFR66EWByNc
vTtdTQeVwuJhqJI6tnHbkMtf00pxCDjGpBVt1iAWrJkK69Gzt13ezseRZgXT
7+NT1d7EncxxAXRW9V0YTm5lmgJKGK7dv/jTRCY09SGqZJhN44qwc47NoH8c
/Z445a1gdmgKVhYfEvJgp5QGLMdeJ1JLyFH7g/4stdWwO5WU5HbrZw==

--3825401791-2006038437-1396978475=:76892--


From nobody Tue Apr  8 10:58:14 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C39D31A0675 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:58:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 gKQ_FsMQxZRp for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:58:10 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 0ACDC1A0653 for <ietf@ietf.org>; Tue,  8 Apr 2014 10:58:10 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 1BCD31B806B for <ietf@ietf.org>; Tue,  8 Apr 2014 10:58:10 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 0841219005C; Tue,  8 Apr 2014 10:58:10 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 8 Apr 2014 10:58:09 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net>
Date: Tue, 8 Apr 2014 13:58:08 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <AF05972E-26DE-4C95-8EBD-140314BA62CD@nominum.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net>
To: t.p. <daedulus@btconnect.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hAA4bddtfx3e6vFJJgVqvQcTNsU
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 17:58:11 -0000

On Apr 8, 2014, at 4:32 AM, t.p. <daedulus@btconnect.com> wrote:
> Solution first, requirements ignored.  This is not what I think of as
> engineering.

Um, can you cite an example where someone in a position to do something =
about this has ignored the arguments that have been made on this thread? =
  Maybe you're talking about some other discussion?


From nobody Tue Apr  8 10:59:09 2014
Return-Path: <alex@chilenetworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94AA81A0684 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:59:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 r7oW3Ck_zByk for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 10:59:03 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0203.outbound.protection.outlook.com [207.46.163.203]) by ietfa.amsl.com (Postfix) with ESMTP id B42621A0683 for <ietf@ietf.org>; Tue,  8 Apr 2014 10:59:02 -0700 (PDT)
Received: from BN1PR04MB533.namprd04.prod.outlook.com (10.141.59.144) by BN1PR04MB535.namprd04.prod.outlook.com (10.141.59.151) with Microsoft SMTP Server (TLS) id 15.0.908.10; Tue, 8 Apr 2014 17:58:59 +0000
Received: from BN1PR04MB533.namprd04.prod.outlook.com ([169.254.2.59]) by BN1PR04MB533.namprd04.prod.outlook.com ([169.254.2.59]) with mapi id 15.00.0913.002; Tue, 8 Apr 2014 17:58:59 +0000
From: Alex Ojeda <alex@chilenetworks.com>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, John R Levine <johnl@taugh.com>
Subject: RE: DMARC: perspectives from a listadmin of large open-source lists
Thread-Topic: DMARC: perspectives from a listadmin of large open-source lists
Thread-Index: AQHPUtuYTS4fL01ECEiytxQlwLX/hZsH9HcKgAANnuA=
Date: Tue, 8 Apr 2014 17:58:57 +0000
Message-ID: <5ffff09cb10c4e0fb28bcd0d470aef0e@BN1PR04MB533.namprd04.prod.outlook.com>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com>
In-Reply-To: <01P6EEIPML6600004W@mauve.mrochek.com>
Accept-Language: es-CL, en-US
Content-Language: es-ES
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [64.120.178.246]
x-forefront-prvs: 017589626D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(6009001)(428001)(199002)(189002)(51704005)(59124003)(377424004)(93516002)(74366001)(65816001)(99396002)(81542001)(74876001)(74316001)(81342001)(74706001)(69226001)(87266001)(2656002)(85306002)(47446003)(54356002)(47736002)(54316003)(47976002)(50986002)(53806002)(90146001)(80022001)(87936001)(86362001)(66066001)(31966008)(59766001)(77982001)(94316002)(63696002)(20776003)(74662001)(79102001)(4396001)(74502001)(49866001)(83072002)(46102001)(76482001)(85852003)(19580405001)(83322001)(19580395003)(566704002)(76786001)(76576001)(76796001)(77096001)(81816001)(95416001)(81686001)(94946001)(56816005)(93136001)(97186001)(97336001)(56776001)(98676001)(33646001)(80976001)(95666003)(92566001)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR04MB535; H:BN1PR04MB533.namprd04.prod.outlook.com; FPR:BCFCF6B7.8CD69702.33F35F4B.48A56B49.20452; MLV:sfv; PTR:InfoNoRecords; A:1; MX:3; LANG:en; 
received-spf: None (: chilenetworks.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: chilenetworks.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Exq6j4YYC9HLRAMfzWSh1JG9fms
Cc: IETF general list <ietf@ietf.org>, "Robin H. Johnson" <robbat2@gentoo.org>, "zwicky@yahoo-inc.com" <zwicky@yahoo-inc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 17:59:08 -0000

For mailman and DKIM problems (remote reject)=20
Example:
2014-04-06 08:09:43 1WWkxK-0007jZ-T5 H=3Dmail.ietf.org [4.31.198.44]:45557 =
rejected DKIM : DKIM: encountered the following problem validating gmail.co=
m: signature_incorrect

Fix:
In:
mm_cfg.py
Add:
REMOVE_DKIM_HEADERS =3D Yes





Alex Matias Ojeda Mercado
NOG CHILE
alex@nog.cl
+56971922362


-----Mensaje original-----
De: ietf [mailto:ietf-bounces@ietf.org] En nombre de ned+ietf@mauve.mrochek=
.com
Enviado el: martes, 08 de abril de 2014 12:53
Para: John R Levine
CC: IETF general list; Robin H. Johnson; zwicky@yahoo-inc.com
Asunto: Re: DMARC: perspectives from a listadmin of large open-source lists

> > The problem described WILL vanish when all mailing list apps=20
> > implement DMARC, but until then, it's really broken.

> Mailing list apps can't "implement DMARC" other than by getting rid of=20
> every feature that makes lists more functional than simple forwarders.
> Given that we haven't done so for any of the previous FUSSPs that=20
> didn't contemplate mailing lists, because those features are useful to=20
> our users, it seems unlikely we'll do so now.

Actually, mailing lists *can* implement DMARC, just not that way: Do a DMAR=
C check on all incoming messages, and if the domain policy is one that is i=
ncompatible with the list's own policies - whatever they are - either chang=
e the list's policies to conform to that message or reject it outright, pre=
ferably with a nasty "find another a better mail provider" sort of message.

If the IETF wants to take a leadership position in regards to this issue, p=
erhaps someone could set this up.

> If receivers want to implement DMARC policy, they need to make their=20
> false alarm whitelist first.  This appears to be a substantial,=20
> perhaps insurmountable, hurdle.

> > At the same time, delaying mass usage of the reject policy would=20
> > limit damage.

> Reject policy is fine for domains that don't have individual human=20
> users, or for companies with firm staff policies that all mail goes=20
> through the company mail server, and employees don't join mailing=20
> lists and the like using company addresses, or the company provides a=20
> separate less strictly managed domain for its staff mail. Strict=20
> policies will never be appropriate for public webmail systems where=20
> the users will use their mail addresses any way one can use a mail=20
> address.  Yahoo appears to understand most of this, viz. the different do=
main for Elizabeth's company mail.

Which is why support for such policies is even in the specification. The pr=
oblem is there's no way to stop inappropriate use of such politicies in adv=
ance of it happening. The best you can do is apply the clue-by-four later.

				Ned


From nobody Tue Apr  8 11:17:56 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54BE01A0161; Tue,  8 Apr 2014 11:17:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.202
X-Spam-Level: 
X-Spam-Status: No, score=-99.202 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 CpqYcKylnPnt; Tue,  8 Apr 2014 11:17:37 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0182.outbound.protection.outlook.com [207.46.163.182]) by ietfa.amsl.com (Postfix) with ESMTP id 231491A067C; Tue,  8 Apr 2014 11:17:37 -0700 (PDT)
Received: from BN1PR06MB231.namprd06.prod.outlook.com (10.242.215.143) by BN1PR06MB248.namprd06.prod.outlook.com (10.242.215.139) with Microsoft SMTP Server (TLS) id 15.0.913.9; Tue, 8 Apr 2014 18:17:35 +0000
Received: from [192.168.0.34] (69.131.53.57) by BN1PR06MB231.namprd06.prod.outlook.com (10.242.215.143) with Microsoft SMTP Server (TLS) id 15.0.918.8; Tue, 8 Apr 2014 18:17:34 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <CADnDZ8-tg52c9FDZgHxgpSJjqPQvqAOg1hSR8usoRx-739msrA@mail.gmail.com>
Date: Tue, 8 Apr 2014 14:17:25 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <F900C807-DB26-48BA-8D3A-C127C6594A5D@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <CADnDZ8-tg52c9FDZgHxgpSJjqPQvqAOg1hSR8usoRx-739msrA@mail.gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BN1PR06CA011.namprd06.prod.outlook.com (10.141.56.31) To BN1PR06MB231.namprd06.prod.outlook.com (10.242.215.143)
X-Forefront-PRVS: 017589626D
X-Forefront-Antispam-Report: =?Windows-1252?Q?SFV:NSPM; SFS:(10019001)(6049001)(6009001)(428001)(479174?= =?Windows-1252?Q?003)(377454003)(189002)(199002)(51704005)(24454002)(8274?= =?Windows-1252?Q?6002)(81686001)(57306001)(76482001)(98676001)(85306002)(?= =?Windows-1252?Q?81816001)(93516002)(85852003)(50466002)(66066001)(319660?= =?Windows-1252?Q?08)(59766001)(74662001)(77982001)(80976001)(74366001)(62?= =?Windows-1252?Q?966002)(80022001)(23746002)(83072002)(63696002)(49866001?= =?Windows-1252?Q?)(79102001)(74706001)(65816001)(74876001)(81342001)(9494?= =?Windows-1252?Q?6001)(4396001)(74502001)(56776001)(20776003)(47776003)(8?= =?Windows-1252?Q?1542001)(50226001)(95666003)(93136001)(95416001)(9939600?= =?Windows-1252?Q?2)(87976001)(94316002)(86362001)(69226001)(90146001)(770?= =?Windows-1252?Q?96001)(42186004)(97336001)(56816005)(33656001)(92726001)?= =?Windows-1252?Q?(88136002)(83716003)(77156001)(1411001)(97186001)(899960?= =?Windows-1252?Q?01)(76786001)(76796001)(46102001)(93916002)(92566001)(87?= =?Windows-1252?Q?286001)(47446003)(83322001)(36756003)(87266001)(19580395?= =?Windows-1252?Q?003)(50986002)(53806002)(47736002)(54316003)(47976002)(1?= =?Windows-1252?Q?9580405001);DIR:OUT;SFP:1102;SCL:1;SRVR:BN1PR06MB231;H:[?= =?Windows-1252?Q?192.168.0.34];FPR:8CD4FA0C.AC3A47D9.30F19D6B.8AFCE240.20?= =?Windows-1252?Q?2EC;MLV:sfv;PTR:InfoNoRecords;MX:1;A:1;LANG:en;?=
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-3_CKl5Aa-a786bhOV1smlFUux8
Cc: iaoc@ietf.org, "iab@iab.org IAB" <iab@iab.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 18:17:42 -0000

On Apr 6, 2014, at 9:17 AM, Abdussalam Baryun =
<abdussalambaryun@gmail.com> wrote:

> Hi Ray,
>=20
> my questions below,
>=20
> On 4/4/14, IETF Administrative Director <iad@ietf.org> wrote:
>> All;
>>=20
>> The Trustees of the IETF Trust have voted an intent to renounce =
(abandon)
>> the "IETF Secretariat"
>> trademark, but before taking any action they desire to hear from the
>> community.
>=20
> What is this hearing status like? is it like if the community reply
> was: *no* don't do that, then they as trustees will change their mind,
> or is it, just hearing. I am not sure if my input has any value in
> this community request.

The responsibility of the Trustees is to =93consult=94 with the =
community.  There may
be reasons the Trustees hadn=92t heard of or considered for not taking =
this=20
particular action.=20

>=20
> If IETF is not active in using its trademarks in business, then why
> the trustees don't think in different directions. Was IETF trademarks
> used in US and Europe and the result was not good, we need information
> to know what is happening?

The reason for this action is that it is unnecessary to protect =93IETF =
Secretariat=94
because =93IETF=94 is protected. =20

>=20
> My thoughts is that we may get benefits from IETF trademarks in
> future, so if the trustees decide now to leave it, could they
> establish it any time by thoes governments registrations?

The Trustees could apply for trademark protections in the future.

> I am not a
> legal expert person but for international organisation like IETF is it
> possible to get registrations at UN or any other authority that may
> make discounts?

One has to apply for trademark protections all over the world.
=93IETF=94 is registered in Australia, Canada, China, European =
Community, Japan, Korea,=20
Norway, Russia, Singapore, Switzerland, New Zealand, South Africa,
Taiwan, and the United States.

Ray


>=20
> Thanks
>=20
> AB
>=20


From nobody Tue Apr  8 11:30:05 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64A431A0699 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 11:30:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.301
X-Spam-Level: 
X-Spam-Status: No, score=-99.301 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 QQHpHCrks_LM for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 11:29:53 -0700 (PDT)
Received: from secure.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7DD5D1A068B for <ietf@ietf.org>; Tue,  8 Apr 2014 11:29:52 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=6404; t=1396981789; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=wQqvGVhxCoI+uZDFXXtGUvXxBi4=; b=TrOCWuis3LiSqHVmy3yO k5aC0d4f8z8gVNflcpooxGAqWEREudn25dTsZ6BApBX1x9PZ2uq04OL7Y+VpNq0v sOgJrFrtFloCV6h9pkjSw/Lp/TVr/F6nkkW5XT+jd9vWJmi1wsD0DzlqSrCMIbBm 1cpPWvp59uOpdh6/jlJuwm0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 08 Apr 2014 14:29:49 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 90372907.3.3644; Tue, 08 Apr 2014 14:29:48 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=6404; t=1396981736; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=FC37Ay5 EXj1Q+5ueJJJbtCQIgVOzUGLSk5h5W3/ioVs=; b=ja/hnGEG9z30x52I4LIlqO8 jWwhNLCMc6vok5rxexOG4FedZOiTpOT9kyldTrb5MHpJA+uDOSmEXyY5szZl+yEg pnHqQZc5me54ndf+ejLbib6+BKcPrnqOhm5EjGSp28s2gTq8oVSpPSt8O2gN0eIJ /jq+dHlfUrfW8AV7BUOc=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 08 Apr 2014 14:28:56 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 109911515.9.2380; Tue, 08 Apr 2014 14:28:54 -0400
Message-ID: <5344401C.2050602@isdg.net>
Date: Tue, 08 Apr 2014 14:29:48 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Robin H. Johnson" <robbat2@gentoo.org>,  Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com> <robbat2-20140408T051158-246173691Z@orbis-terrarum.net>
In-Reply-To: <robbat2-20140408T051158-246173691Z@orbis-terrarum.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Btqyzvdqgx-T5fIZRHEnizwtKqM
Cc: IETF general list <ietf@ietf.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 18:30:00 -0000

By far, the list REPLY-TO feature benefited the layman list user 
inability to figure it out how to reply back to the list by 
manipulating header input fields with the lack of MUA support for a 
3rd reply button:

    REPLY
    REPLY TO ALL
    REPLY TO LIST  <--- NEW

With greater support for LIST-* headers, the MUA can now add the 3rd 
button and the default, natural "reply" action to reply back to the list.

Without it, most layman and even "lazy" veterans can mistakenly and 
naturally click that "reply" button only to unintentionally go 
directly and not to the groupware discussion area A.K.A "mailing list."

You have to look at it from the perspective of the UI ERGONOMICS and 
the support process why it even existed.

That said, it is not natural to TAMPER with mail, especially of the 
body text, but including headers that were not created by the middle 
ware.  However, there has been a historical school of though that 
mailing list server/agent was acting as a NEW MAIL AUTHOR.  I didn't 
think it was 100% kolsher, but it was a rationale for the technical 
justification to tamper with mail; list software is really a "new 
author" therefore it has "right" to tamper with mail.

I didn't generally agree with this, but even our own (commercial) 
Mailing List Server does manipulate the headers in principle to 
improve communications, and of recent as an option to improve DKIM 
resigning logical "faults."

Improving the communications included:

   - Prepare the BOUNCE, ERROR address.  Different remote
     Bouncing software behave differently in how or where
     they get the bounce or error address.  So this one reason
     you will have redundancy, changes in error addresses;
     Sender:, Errors-To: to target all forms.

   - Minimizing mistakes, making it easy for the USER to
     have a "natural" reply back to the list by adjusting
     the Reply-To header.  By far, the preferred intention is
     to reply back to the list.  Newer MUA with list-* header
     and "REPLY TO LIST"  reduces the new to set or strip &
     replace the reply-to field.

There was also major concerns with DKIM tampering with originality. 
It will be an injustice to try to cover, go over all that again here.

Finally, this whole discussion about DMARC is all deja-vu and surreal 
too that the OP is concern now when DKIM with SSP or ADSP had the same 
problems and DMARC does not resolve it.  He knows that. So I see this 
as a marketing effort to push something that clearly will not work for 
the same reasons ADSP did not. Its no different.

In principle, we will always have the same problems with LIST software 
because of the mindset and rationale that the middle ware is a "new 
author" and therefore does not have to respect any SECURITY POLICY 
controls by the originating, authoring, copyright holding domain.  It 
was a clear case of intentional ignorance (don't recognize ADSP, make 
it historic) and tampering of a email security control.

It was the reason the powerful concept of SSP/ADSP did not get the 
wider MARKETING endorsement it deserved.   The main hurdle was with 
LIST systems.

The same problem will be with DMARC.  There is nothing that DMARC can 
do to change that except perhaps advocate (and document) stronger 
middle ware controls to properly follow these security controls.

But you can't have this when DKIM was revised to be based on a 
futuristic, never materializing 3rd party signer control system that 
is consistent and persistent from point to point, end to end, pretty 
much like the SSL/BROWSER market with each browser supporting the same 
3rd party signature framework.  We can not repeat this in the mail 
system -- too  many vendors to begin with. With browsers, there were 
only a few you had to deal with.

We knew all this list problem in DKIM 101. It was part of the original 
charter that any idea to make it work would be secondary to the 
primary purpose of gaining stronger direct domain security controls. 
DKIM and ASDP were part of the original standard track charter.  It 
made perfect engineering sense.

But that seem to change by the "big" list operators who felt that DKIM 
needs be a 3rd PARTY signer control framework with less recognition to 
the original author. SSP which has 3rd party controls was reduced to 
ADSP that allowed for a secured 1st party control.  But that still 
would not work with LIST system unless these middle ware routers 
supports the 1st party controls too.

It was too easy to see that it won't work.  Not thru LIST systems 
without 100% advocated support for honoring these new domain security 
protocol policies.  Instead, it is documented in DKIM related RFCs 
that its OK to tamper with mail as long it was resigned with "trusted" 
3rd party signing domains.  The theory is that if the receivers also 
had a table of the same 3rd party Trusted signers, then it would 
resolve the broken chain of trusted mail problem.

We can't have it both ways.

---
HLS

On 4/8/2014 1:16 AM, Robin H. Johnson wrote:
> On Tue, Apr 08, 2014 at 06:06:27AM +0100, Sabahattin Gucukoglu wrote:
>> On 8 Apr 2014, at 05:21, John R Levine <johnl@taugh.com> wrote:
>>> Mailing list apps can't "implement DMARC" other than by getting rid
>>> of every feature that makes lists more functional than simple
>>> forwarders. Given that we haven't done so for any of the previous
>>> FUSSPs that didn't contemplate mailing lists, because those features
>>> are useful to our users, it seems unlikely we'll do so now.
>> Well,  Mailman 2.1.16 has the FROM_IS_LIST feature that "Fixes" the
>> problem by putting the list address in the From: field.  That seems to
>> work, except that you lose information (the sender's address) if the
>> list wants to operate a policy of "Reply goes to list".  You can then
>> assure that DKIM signatures are valid and set up SPF, etc.  This also
>> has the effect of letting you operate through the various cloud email
>> platforms that try to validate sender addresses.
> This breaks the ability to reply directly to the sender when the
> response should NOT be on the list, as well as the ability to put a
> sender in a personal killfile.
>
> And don't start on suggesting Reply-To instead, RFC 2822 already
> noted that it should be set by the author, not the list software [1].
>
> [1] http://marc.merlins.org/netrants/listreplyto.html List Reply-To
> considered harmful.
>



From nobody Tue Apr  8 12:21:19 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE7E1A0702 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 12:21:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.137
X-Spam-Level: 
X-Spam-Status: No, score=-101.137 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 gnDA4726Xcu0 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 12:21:11 -0700 (PDT)
Received: from secure.winserver.com (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 661371A06FA for <ietf@ietf.org>; Tue,  8 Apr 2014 12:21:07 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3352; t=1396984865; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=IdCoBR4wTcwBlSllnI+rWFqC9s0=; b=EiFtCxLJIVovtJqxP0N+ xav6n67X7H9yeHTjx4wRPMt65z6a1aKfgk90G5Znjb0vg19zTWxS8vMfiXgtJTKZ vZNyzlMVDjnRfas3UOiJPLQoRTUQUNIQ3YEXGZSbPoR+ADY9q1D8tyTAMc6C9Sce UykOZuNmxG6DD+jzoN9xCxI=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 08 Apr 2014 15:21:05 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 93448374.3.2132; Tue, 08 Apr 2014 15:21:04 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3352; t=1396984807; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=HaE5Klw /OVCVj03Jrxq0YTSWrpc5Ro0i+grIHh75kJQ=; b=jlc+6+jsy9UUuAnupsD5NAc egUyvB3l1z+hXHmZdytcwXCJeFV/hlASzmKOYkfp2M/m5mzCNFJnzn1sRnMJR85o xMym/G5D+Kk494+pYiBBGgEfK6P1PYjJw7jAZLFBNAY2Gj6sUZpIHkjmH4RMvGC6 vev5y70RC4fiS6tTOnQ4=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 08 Apr 2014 15:20:07 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 112983687.9.2428; Tue, 08 Apr 2014 15:20:06 -0400
Message-ID: <53444C1C.5080506@isdg.net>
Date: Tue, 08 Apr 2014 15:21:00 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net>
In-Reply-To: <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/m80aF-P8lFFG5BRI6IJzFyIfh0w
Cc: ietf@ietf.org, "Robin H. Johnson" <robbat2@gentoo.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 19:21:15 -0000

Really?

You knew that our software was the first to suggest and document in 
the 2006 DSAP I-D on how to a MLS will need to handle restrictive 
domain security policies.  RFC 6377 (BCP 167) notes on this came from 
my I-D and the DKIM WG discussions about it whether directly or not.

   http://tools.ietf.org/html/draft-santos-dkim-dsap-00#section-3.3

   3.3.  Mailing List Servers

    Mailing List Servers (MLS) applications who are compliant with DKIM
    and DSAP operations, SHOULD adhere to the following guidelines:

    Subscription Controls

       MLS subscription processes should perform a DSAP check to
       determine if a subscribing email domain DSAP policy is restrictive
       in regards to mail integrity changes or 3rd party signatures.  The
       MLS SHOULD only allow original domain policies who allow 3rd party
       signatures.

    Message Content Integrity Change

       List Servers which will alter the message content SHOULD only do
       so for original domains with optional DKIM signing practices and
       it should remove the original signature if present.  If the List
       Server is not going to alter the message, it SHOULD NOT remove the
       signature, if present.

Our MLS was the first supports this.

During development of RFC6377, the potential interop issues was well 
known. I was able to show this when the middle ware ignores DKIM 
signature controls.

DMARC will not resolve the problem, but .....

Part of the problem has been with the DKIM mindset to make it a 3rd 
party signature framework where the LIST or 'central' mail distributor 
has full control of signatures.  Remember, in the original DKIM, 
making it work with LIST system was a secondary chartered concern. 
That charter changed (or did it?) and not for the better with a lesser 
focus on the author domain policies, and eventually dismantling of 
ADSP, but replaced with DMARC.

Restrictive 1st party controls are by design not to work in the 3rd 
party environment. That was the purpose and intent of the original SSP 
policies, and the reduced ADSP proposal.  DSAP attempted to bring back 
that idea. You could only implement it as described above or by simply 
following the policy in some fashion to not cause downlink issues. 
Intentionally ignoring it was not an option if you wanted to support DKIM.

But DKIM and its deployment documents are in conflict.  It says follow 
ADSP, but it allows for the 3rd party DKIM signing system to ignore it.

Can't have it both ways.

---
HLS


On 4/8/2014 1:19 PM, S Moonesamy wrote:
> Hi Ned,
> At 09:52 08-04-2014, ned+ietf@mauve.mrochek.com wrote:
>> Actually, mailing lists *can* implement DMARC, just not that way: Do
>> a DMARC
>> check on all incoming messages, and if the domain policy is one that is
>> incompatible with the list's own policies - whatever they are -
>> either change
>> the list's policies to conform to that message or reject it outright,
>> preferably with a nasty "find another a better mail provider" sort
>> of message.
>
> There is some Mailman code which does the above.
>
>> If the IETF wants to take a leadership position in regards to this
>> issue,
>> perhaps someone could set this up.
>
> I did a search before asking this question; I did not find any
> answer.  Does anyone know whether the IETF adheres to BCP 167?
>
> Regards,
> S. Moonesamy
>
>
>



From nobody Tue Apr  8 12:29:13 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49FEC1A04B8 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 12:29:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 boL4D5yLRXp0 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 12:29:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C908D1A023B for <ietf@ietf.org>; Tue,  8 Apr 2014 12:29:06 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.104]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s38JSsAr026935 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Apr 2014 12:29:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1396985345; bh=LaiKApddjJQ82dfwyU36hlvf9gGbGjFDrMaNSGJiRZY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=l5X4/uAjGFsSaEJ2ds6G70AXbM4nvnuUx4sjk6ab70/eWVCCxhvK5IpqAwbY8MH9D dfotVnEvrvrM5HrX4w+4maRQJm4GTkbT7gQVuqLgNFJ97kJQs5IEFU6UNnVSHanhFe lNV2cIgofGH0JvNgCrWzlu2GeA88JRFMf55yh+Os=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1396985345; i=@elandsys.com; bh=LaiKApddjJQ82dfwyU36hlvf9gGbGjFDrMaNSGJiRZY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=C6g2SkSyQF70MZsG/qAQCYhr1LZolgAVe06G6NoehwM8Ndx+Jsj9TxstShrSAorMi 0ST2vmf+Z7yvu3GOYCFqSPyuWIkeDEz+yIdAKXsoX66D7RF4ToN2g9N0P+KZfO9U6Q 2ctvRy1aniU0zuGQTtUxuwCZC0YGHgwrQM3K0cMc=
Message-Id: <6.2.5.6.2.20140408110441.0ccb5070@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Apr 2014 11:55:58 -0700
To: "John R Levine" <johnl@taugh.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <alpine.BSF.2.00.1404081325130.76892@joyce.lan>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kNahEgFDRU1lnDeE8LnjIIFBtHU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 19:29:11 -0000

Hi John,
At 10:34 08-04-2014, John R Levine wrote:
>I've never been a big fan of RFC 6377, but this bit seems relevant 
>since strict ADSP policies had pretty much the same problems as 
>strict DMARC policies.

Strict ADSP policies do cause problems.

>    For domains that do publish strict ADSP policies, the originating
>    site SHOULD use a separate message stream (see Section 2.5), such as
>    a signing and Author subdomain, for the "personal" mail -- a
>    subdomain that is different from domain(s) used for other mail
>    streams.  This allows each to develop an independent reputation, and
>    more stringent policies (including ADSP) can be applied to the mail
>    stream(s) that do not go through mailing lists or perhaps do not get
>    signed at all.
>
>As far as I know, the "participating MLM" thing has never been 
>implemented, which makes the C in BCP rather suspect.  My own MLM 
>signs the outgoing mail and adds an Authentication-Results: header, 
>but largely by default because it's embedded in a mail system that 
>does those things.

There was a message stating that the IETF implemented support for 
DKIM ( 
http://www.ietf.org/mail-archive/web/ietf-announce/current/msg09173.html 
).  Given that there is an existing BCP about DKIM and mailing lists 
it might be assumed that the IETF is following it.  There is a 
recommendation in the BCP to reject some types of messages.

My mailing list implementation does not break DKIM signatures.  I 
would not describe it as a "participating MLM" as the postmaster does 
not follow some of the recommendations in that BCP. :-)

>Just today I did modify it so that any list mail with a From: 
>address @yahoo.com is re written to @yahoo.com.INVALID.  That's the 
>least intrusive way I've been able to come up with to mitigate the 
>damage. It's also similar to what RFC 6858 suggests for delivering 
>EAI mail to systems that can't handle EAI, which is a vaguely similar problem.

I found some other domains which implemented DMARC as described at 
http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html  I 
suggest taking that into account if you haven't already done it.

Regards,
S. Moonesamy 


From nobody Tue Apr  8 12:53:43 2014
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABD851A02B0 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 12:53:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 2h2dM6Oc1NFT for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 12:53:30 -0700 (PDT)
Received: from qmta01.westchester.pa.mail.comcast.net (qmta01.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:16]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4281A072A for <ietf@ietf.org>; Tue,  8 Apr 2014 12:53:29 -0700 (PDT)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta01.westchester.pa.mail.comcast.net with comcast id nPcZ1n0040mv7h051XtVnq; Tue, 08 Apr 2014 19:53:29 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta11.westchester.pa.mail.comcast.net with comcast id nXtU1n00K1KKtkw3XXtUJS; Tue, 08 Apr 2014 19:53:29 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s38JrSSq006545; Tue, 8 Apr 2014 15:53:28 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s38JrSFd006544; Tue, 8 Apr 2014 15:53:28 -0400
Date: Tue, 8 Apr 2014 15:53:28 -0400
Message-Id: <201404081953.s38JrSFd006544@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: <l.wood@surrey.ac.uk>
In-reply-to: <290E20B455C66743BE178C5C84F1240847E779EECC@EXMB01CMS.surrey.ac.uk> (l.wood@surrey.ac.uk)
Subject: Re: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <AE6C1CD9-8E98-458B-8B53-A6275892471A@gmail.com> <0FA55A15-7D95-4AD9-B2FE-19C6C80CD377@me.com>, <p06240607cf6927f80f42@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EECC@EXMB01CMS.surrey.ac.uk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1396986809; bh=ZAzy4mWwrRWZvyT8cWwvzZNlod8dy3I4VQfCjPyjbok=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=kztzAndeCHSpcjwPUgm4mqlG4KWC5rJRP6D9vu5PuJO6JGZbe4YHnpksy3x6h35Q/ N+4ml5M4GNjIU3EFkI7iLTjzkxHgbV1B5AKFOAz1aT9IMXjHBeZg8g168oCdBoSyTD CAPUPrnI4qozSUTM+7bVDKcb3x/R4pPJVC4v0o9NlVf1yovkc3nHMon7Iajg86Mf2n nD2tiR9hJfz6f749Nyj0vuTaidKrKNgtHYacOFjwQ4lCkV+bqv0i4ULUS1EbBfSsmX t0jzajxOCc+poAqdzIOf3QaH1A56jP1WmJrv/EDnHpngrcd00oWsx9e+88UeX7RZMi +CMXOeruCc76A==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gP4_dRcY0m0jAcG5Ls-9ijEIgd0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 19:53:36 -0000

> From: <l.wood@surrey.ac.uk>

> George Orwell: A Nice Cup of Tea, 12 Jan 1946
> http://www.booksatoz.com/witsend/tea/orwell.htm
> 
> is often cited as the correct _English_ way to take tea. No sugar.

It looks like we're already starting a 7168bis...

Dale


From nobody Tue Apr  8 13:12:55 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 476F51A026A for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 13:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 ynqnuzxlcy8t for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 13:12:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A348F1A0218 for <ietf@ietf.org>; Tue,  8 Apr 2014 13:12:48 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.104]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s38KCIpg009220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Apr 2014 13:12:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1396987952; bh=DgGtwuvUsVxAEJZGZplkoqxc9q2mPqat28+S7fVb3xs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=v+BkRTiLYRPfLnAqwCDj7kdr8n9bAX4uq1BvevJm1Up44st9ZMD11OudjswYx2ykk cIxpry71iJu7yeXkcBaRrMVjamJV81OxplYRfY0mSFjw+vhXe3DnENzVXZ+LPBOIBE rK8FqJE8Om+sAI+O6hwRIHlm8z1z7Yx1JPAI0VYg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1396987952; i=@elandsys.com; bh=DgGtwuvUsVxAEJZGZplkoqxc9q2mPqat28+S7fVb3xs=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rUXSf3+e+JBi+GYbkB3oJ9tcGj6V2cicJBV1+peheAI9/trNVJIhv1ZGdynYzdtMM urjrJ/SkJ4keh5dJK3Yxx1g4n5I6xMOllDBKvH7QLCue06qOIg/PdW5i/gLUKVYtzS 7aLEdPJoGK0I7J1/ono3JztnfweeOwdJbVC9t0g0=
Message-Id: <6.2.5.6.2.20140408122848.0be6f720@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Apr 2014 13:09:11 -0700
To: Hector Santos <hsantos@isdg.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <53444C1C.5080506@isdg.net>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <53444C1C.5080506@isdg.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Kw_6_1eGR0_KrWwaE7QMKamGOrE
Cc: ietf@ietf.org, "Robin H. Johnson" <robbat2@gentoo.org>, zwicky@yahoo-inc.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 20:12:53 -0000

Hi Hector,
At 12:21 08-04-2014, Hector Santos wrote:
>Really?
>
>You knew that our software was the first to suggest and document in 
>the 2006 DSAP I-D on how to a MLS will need to handle restrictive 
>domain security policies.  RFC 6377 (BCP 167) notes on this came 
>from my I-D and the DKIM WG discussions about it whether directly or not.

The question I asked was whether the IETF adheres to BCP 167.  I must 
have been aware that your software implemented that draft if it was 
mentioned during the DKIM WG discussions.  I forgot about that as it 
has been a while.

Regards,
S. Moonesamy 


From nobody Tue Apr  8 13:59:17 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 659AF1A040D; Tue,  8 Apr 2014 13:59:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.427
X-Spam-Level: 
X-Spam-Status: No, score=0.427 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 p8ndqZgaA8Kj; Tue,  8 Apr 2014 13:59:07 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id A29C51A026E; Tue,  8 Apr 2014 13:59:06 -0700 (PDT)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s38KwumY001289 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Apr 2014 16:58:57 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s38KwumY001289
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1396990740; bh=h0bIKzzWEU1n2jM90gYTQeYA8/E=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=WlBrDPXh2HRboR1yXuwIz8ntmEf7ScWQlVe9lvALNRQwHk5fugR7I2xfKeQgdpzkB f9RfJBqYnlPgq2VGgq6IztahDRSeu/YWcr1I/IMBRu+UK9q6U/vJcEt+fA+5ROB2SK W+JkXcDGKzpA+c67HjY3RLkG/hJE7jB9LH1ak51o=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd51.lss.emc.com s38KwumY001289
Received: from mailusrhubprd51.lss.emc.com (mailusrhubprd51.lss.emc.com [10.106.48.24]) by maildlpprd53.lss.emc.com (RSA Interceptor); Tue, 8 Apr 2014 16:58:39 -0400
Received: from mxhub08.corp.emc.com (mxhub08.corp.emc.com [128.222.70.205]) by mailusrhubprd51.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s38Kwbbd021670 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 8 Apr 2014 16:58:38 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub08.corp.emc.com ([128.222.70.205]) with mapi; Tue, 8 Apr 2014 16:58:37 -0400
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 8 Apr 2014 16:58:36 -0400
Subject: RE: Gen-ART review of draft-ietf-trill-esadi-06.txt
Thread-Topic: Gen-ART review of draft-ietf-trill-esadi-06.txt
Thread-Index: Ac9Q4vX57WukMZzRQMC+3VZdMgWnAwCdvEuQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C1D15CD@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com> <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com>
In-Reply-To: <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd51.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/98HKQberd3z32FoUc6Om9sqlnxo
Cc: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 20:59:12 -0000

Donald,

Thank you for the extensive comments on the review.  I'll summarize here
rather than add more text inline.  I'm fine with the proposed course of
action for anything not mentioned here:

[1] Absence of backwards compatibility:
        - The Appendix A changes look good.
        - The "limited deployment" (and presumably also "limited
                implementation") rationale for no backwards compatibility
                should be included in Section 1.1.  This merits additional
                text in Section 1.1

[2] Structure of draft wrt RFC 6325:
        I think the rest of the proposed changes to Section 1.1 are reasona=
ble:

        - Appendix A does explain what's changed.  I would have liked to se=
e
                more formality/precision in Section 1.1, but that's a matte=
r of
                editorial taste that I'll leave to the authors.  The propos=
ed
                addition of a forward reference to Appendix A will definite=
ly
                help.
        - The proposed addition of an explicit statement about expecting
                familiarity with RFC 6325 in Section 1.1 will also help.

[3] Independence of ESADI instances: What bothered me was the absence of
a strong mention of implementation structure - I have some new text to
suggest to strengthen that point:

OLD
   It is an implementation decision how independent the multiple ESADI
   instances at an RBridge are.
NEW
   Multiple ESADI instances may share implementation components within
   an RBridge as long as that sharing preserves the independent operation
   of each instance of the ESADI protocol.

Then the link state database example that follows makes more sense,
at least to me.

[4] Section 8  Authentication TLV usage discussion.

> How about adding a new paragraph to Section 8, between the current
> first and second paragraphs, incorporating the above, such as:
>
>    However, there may be cases where it is not necessary to
>    authenticate ESADI PDUs despite using authenticated registration
>    for end stations.  For example a TRILL campus with secure RBridges
>    and inter-RBridge links configured as trunks but some end stations
>    connected via 802.11 wireless access links might use 802.11
>    authentication for the connection of such end stations but not
>    necessarily authenticate ESADI PDUs. Note that if the IS-IS LSPs in
>    a TRILL campus are authenticated, perhaps due to a concern about
>    forged packets, the ESADI PDUs will be authenticated by default as
>    provided in Section 6.3.

These seems a bit descriptive, with most of the text describing a
specific example.  I'm looking for some more prescriptive guidance
about what SHOULD (or perhaps should?) be the case when the Authentication
TLV is not used with authenticated registration.

[5] VLAN tag presence (nit)

> > Last sentence on p.8:
> >
> > OLD
> >    The outer VLAN tag will not be present if it was stripped by
> >    an Ethernet port out of which the packet was sent.
> > NEW
> >    The outer VLAN tag will not be present for a packet on an
> >    an Ethernet link that does not use VLAN tags.

I don't think the word "stripped" is right, as it would not apply if
the tag wasn't present in the first place, although I also agree with
your comment that my suggested use of "link" isn't right, either.

Here's another suggestion:

    The outer VLAN tag will not be present if it was not included
    by the Ethernet port that sent the packet.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Saturday, April 05, 2014 11:23 AM
> To: Black, David
> Cc: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu;
> ostokes@extremenetworks.com; General Area Review Team (gen-art@ietf.org);
> trill@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
>
> Hi David,
>
> Thanks for this very thorough review. See my responses below:
>
> On Sat, Mar 29, 2014 at 10:23 PM, Black, David <david.black@emc.com> wrot=
e:
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-trill-esadi-06.txt
> > Reviewer: David L. Black
> > Review Date: March 29, 2014
> > IETF LC End Date: April 1, 2014
> >
> > Summary: This draft is on the right track, but has open issues
> > described in the review.
> >
> > This draft revises the ESADI specification for TRILL from its
> > original form in RFC 6325.
> >
> > Major issues:
> >
> > The draft changes ESADI in a non-backwards-compatible fashion from
> > its original specification in RFC 6325, but does not explain why this
> > is ok.  That explanation needs to be provided, and if implementations
> > of ESADI as originally specified in RFC 6325 exist, that explanation
> > needs to encompass coexistence and interoperability (or lack thereof)
> > with such implementations.  That explanation probably belongs in
> > Section 1.1, and could be expanded upon in Appendix A.
>
> This was a considered decision of the TRILL WG. At least since the -02
> version in February 2013, the ESADI WG draft has had ESADI-LSP
> provisions that were incompatible with RFC 6325 ESADI for the purpose
> of accomodating orders of magnitude more LSP fragments. This text in
> the draft, which originally used a somewhat ad hoc change from IS-IS
> LSPs to accomodate additional fragments, was posted to the list
> without objection before being incorporated. Since a standard IS-IS
> way of doing this was later in process in the ISIS WG, the ESADI draft
> was changed to follow this more standard way of providing for more LSP
> fragments and a new WG Last Call done in the TRILL WG specifically on
> this issue. See
>
> http://www.ietf.org/mail-archive/web/trill/current/msg06037.html
> http://www.ietf.org/mail-archive/web/trill/current/msg06009.html
>
> In Appendix A (Changes to [RFC6325]), how about replacing items 2 and
> 3 in the list as follows (includes fixing a typo in item 3):
>
> OLD
>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
>       is changed from the base IS-IS format to the Extended Level 1
>       Circuit Scoped format in [FS-LSP].
> NEW
>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
>       is changed from the base IS-IS format to the Extended Level 1
>       Circuit Scoped format (E-L1CS) specified in [FS-LSP]. This
>       change is not backwards compatible with [RFC6325]. It is made in
>       light of (a) the very limited, if any, deployment of [RFC6325]
>       ESADI, and (b) the 256 times greater information carrying
>       capacity of the E-L1CS format compared with the base IS-IS
>       format. It is anticipated that this greater carrying capacity
>       will be needed, under some circumstances, to carry end station
>       addressing information or other information that is added to
>       ESADI in the future.
> OLD
>    3. Unicasting of ESADI PDUs is supported including replacing Section
>       4.6.2.2 of [RFC6325] with the next text give in Section 4.1 of
>       this document.
> NEW
>    3. Unicasting of ESADI PDUs is optionally supported including
>       replacing Section 4.6.2.2 of [RFC6325] with the new text give in
>       Section 4.1 of this document. This unicast support is backwards
>       compatible because it is only used when the recipient RBridge
>       signals its support.
>
> See possible replacement below for the first paragraph of Section 1.1
> that includes a condensed version of this additional material
> concerning backwards non-compatibility.
>
> > Overall, this draft is not self-contained - to a significant extent,
> > it is written as if it were effectively a long collection of errata
> > to the ESADI specification in RFC 6325. That makes it difficult to
> > understand - it would be better if this draft completely obsoleted
> > and replaced the ESADI specification in RFC 6325, describing its
> > changes, instead of providing specific text changes to portions of
> > the RFC 6325 text.
>
> All of the changes to ESADI are described in Appendix A.
>
> If the ESADI related material in RFC 6325 was entirely contained in
> one contiguous area of RFC 6325, it would have been easy to write this
> draft as simply obsoleting and replacing that area of RFC 6325.  The
> largest such monolithic block on ESADI in RFC 6325 is Section 4.2.5
> (The TRILL ESADI Protocol), including its two subsections ("4.2.5.1
> TRILL ESADI Participation" and "4.2.5.2 TRILL ESADI Information"). All
> of that is obsoleted and replaced by this draft.  However, there are
> other non-contiguous parts of RFC 6325 necessarily affected. For
> example, Section 4.6 of RFC 6325 describes how to handle every
> possible type of frame that might be received; since an ESADI PDU is
> one such type of frame, it is necessary to change Section 4.6.2.2
> ("TRILL ESADI Frames") of RFC 6325.
>
> There is really no substitute for having a general familiarity with
> RFC 6325 in understanding this document. Although I have seen IESG
> members criticize statements such as "Familiarity with X is assumed."
> when X is a normative reference, on the grounds that familiarity with
> all normative references is automatically assumed, perhaps some such
> statement is warranted in this case.
>
> In addressing both of your issues here, the first paragraph of Section
> 1.1 could be changed as follows:
>
> OLD
>    This document updates [RFC6325], the TRILL base specification,
>    replacing the description of the ESADI protocol in Section 4.2.5 of
>    [RFC6325], providing more detail, and prevailing over [RFC6325] where
>    they conflict. The changes are summarized in Appendix A. These
>    changes are not backwards compatible because, among other things,
>    they change the format of ESADI-LSPs.
> NEW
>    This document updates [RFC6325], the TRILL base protocol
>    specification, obsoleting and replacing the description of the
>    ESADI protocol (Section 4.2.5 of [RFC6325] including all
>    subsections), providing more detail on ESADI, updating other ESADI
>    related sections of [RFC6325], and prevailing over [RFC6325] in any
>    case where they conflict. For this reason, familiarity with
>    [RFC6325] is particularly assumed.  These changes are not backwards
>    compatible because they change the format of ESADI-LSPs to
>    substantially increase the amount of information that can be
>    carried. These changes are further discussed in Appendix A.
>
>
> > Minor issues:
> >
> > I don't understand the discussion in section 2 of it being "an
> > implementation decision how independent the multiple ESADI instances
> > at an RBridge are" in light of the clear statement that "the ESADI
> > update process operates separately for each ESADI instance."  The
> > example given involves database structure considerations that are
> > specific to the node implementation and do not affect the independent
> > updates for each ESADI instance.  There may not be an actual
> > technical problem here, but at least the first chunk of text quoted
> > in this paragraph of the review needs to be rewritten.
>
> Two things motivated the text you cite in Section 2: (1) ESADI uses
> multiple instances of the flooding process for the purpose of limiting
> the flooding to the TRILL switches that have expressed interest in a
> particular Data Label. RFC 6822 specifies a different type of IS-IS
> "instance" and there is some implication in 6822 of fault and
> performance isolation between RFC 6822 instances. Although this
> document says its instances are not the same as RFC 6822 instances,
> someone might still have the impression that ESADI instances are
> necessarily to be implemented inside a TRILL switch is a highly
> isolated manner. This text is to emphasize that the extent to which
> the execution of different ESADI instances are isolated within a TRILL
> switch is an implementation decision. (2) Perhaps a symptom of item 1:
> in early discussions of ESADI, there were multiple complaints that
> maintaining 'so many different link state databases' in a TRILL switch
> would be an undue burden. So the text here specifically mentions that
> the databases for all ESADI instances at a TRILL switch can be merged
> (with an appropriate marker in each record saying which instance it
> belongs to).
>
> While the IETF generally standardizes bits on the wire and not
> internal implementation details, the above concerns lead to these few
> sentences to dispel any false impression.  I do not really see how
> there can be much confusion since the draft also says, as your point
> out, "But the ESADI update process operates separately for each ESADI
> instance and independently from the TRILL IS-IS update process.". I
> suggest the following change:
>
> OLD
>    It is an implementation decision how independent the multiple ESADI
>    instances at an RBridge are.
> NEW
>    This specification does not constrain how coupled or independent
>    the multiple ESADI instances are in their implementation internal
>    to an RBridge.
>
>
> > Also in Section 2:
> >
> >    ESADI does no routing so there is no reason for pseudo-nodes in ESAD=
I
> >    and none are created.
> >
> > Need to explain what a pseudo-node is before this sentence.
>
> I do not think this document is the right place for a detailed
> explanation of pseudo-nodes. How about changing to the following:
>
>    ESADI does no routing calculations so there is no reason for
>    pseudo-nodes in ESADI and none are created (Pseudo-nodes [IS-IS]
>    are a construct for optimizing routing calculations.)
>
>
> > p.9, Figure 2 - explain how the receiver determines whether the inner
> > Ethernet header contains a VLAN tag or FGL.  This also applies to Figur=
e
> > 3 on p.10.
>
> I'm not sure this draft is the place for a detailed explanation but I
> have no problem adding the already existing reference "[RFCfgl]" to
> both figures right after where they say "VLAN or FGL Data Label (4 or
> 8 bytes)". That referenced document [RFCfgl], which is in the RFC
> Editor's queue, explains this.
>
>
> > p.10, Section 2.1:
> >
> >    All transit RBridges forward ESADI packets as if they were ordinary
> >    TRILL Data packets.
> >
> > Need to explain what a "transit" RBridge is.  Between this and the
> > above pseudo-node comment, I suggest adding an overview of the
> > TRILL protocol to the start of Section 2.
>
> How about just eliminating the word "transit", which I don't think is
> necessary, and changing the sentence in question to
>
>      All RBridges forward ESADI packets as if they were ordinary TRILL
>      Data packets [RFC6325].
>
>
> > p.11, Section 2.1:
> >
> >    No "routing" computation or routing decisions ever have to be
> >    performed by ESADI.
> >
> > What is a ' "routing" computation' ??  This should be rephrased to
> > contrast to what the non-ESADI TRILL usage of IS-IS does.
>
> How about the following change:
>
> OLD
>    No "routing" computation or routing decisions ever have to be
>    performed by ESADI.
> NEW
>    No "routing" calculation (least cost path or distribution tree
>    construction) ever has to be performed by ESADI.
>
>
> > p.12, Section 2.2:
> >
> >    If a VLAN or FGL ID
> >    field within an ESADI-LSP PDU does include a value, that field's
> >    contents is ignored.
> >
> > This looks like it's an important requirement, so:
> >          "is ignored" -> "MUST be ignored"
>
> OK.
>
>
> > p.13, Section 3
> >
> >   "SNPA/MAC address"
> >    is not considered in this tie breaking and there is no "Port ID".
> >
> > This is contrasting ESADI tie-breaking to a tie-breaking procedure
> > that I'd guess is specified in another document; that needs to be
> > explained, along with a reference to that document, preferably with
> > the section number where the other tie-breaking procedure is
> > specified.
>
> The other document is [rfc6327bis] which is referenced.  However, this
> reference can be made clearer. How about
>
> OLD
>    Generally speaking, the DRB election on the ESADI virtual link (see
>    Section 2.1) operates similarly to a TRILL IS-IS broadcast link
>    [rfc6327bis] with the following exceptions:
> NEW
>    Generally speaking, the DRB election on the ESADI virtual link (see
>    Section 2.1) operates similarly to the DRB election on a TRILL
>    IS-IS broadcast link, as described in Section 4.2.1 ("DRB Election
>    Details") of [rfc6327bis], with the following exceptions:
>
>
> > Section 6 - explain where the 1470 byte number in the third
> > paragraph comes from.
>
> How about adding the following at the end of the relevant paragraph,
> just before the Section 6.1 header:
>
>    (As stated in Section 4.3.1 of [RFC6325], 1470 bytes was chosen to
>    make it extremely unlikely that a TRILL control packet, even with
>    reasonable additional headers, tags, and/or encapsulation, would
>    encounter MTU problems on an inter-RBridge link.)
>
>
> > Section 8 - more should be said on whether/when the Authentication
> > TLV should be used when ESADI conveys information from an
> > authenticated registration. In particular, if this recommendation
> > for usage of the Authentication TLV with information from an
> > authenticated registration usage is not a "SHOULD" or "MUST", an
> > explanation is in order.
>
> Consider the following: we have a network with secure trunk links
> between trusted TRILL switches but in some cases those switches are
> connected to end stations via 802.11 Wi-Fi links. It seems entirely
> reasonable to use 802.11 authentication in allowing end stations to
> connect due to the inherent accessiblity of radio links, but might not
> be necessary to use authentication on ESADI PDUs between TRILL
> switches.
>
> In any case, if there is a concern about forged packets, the IS-IS
> LSPs in the TRILL campus should be authenticated and, in that case,
> the ESADI PDUs will be authenticated by default as provided in Section
> 6.3 of this draft.
>
> How about adding a new paragraph to Section 8, between the current
> first and second paragraphs, incorporating the above, such as:
>
>    However, there may be cases where it is not necessary to
>    authenticate ESADI PDUs despite using authenticated registration
>    for end stations.  For example a TRILL campus with secure RBridges
>    and inter-RBridge links configured as trunks but some end stations
>    connected via 802.11 wireless access links might use 802.11
>    authentication for the connection of such end staions but not
>    necessarily authenticate ESDAI PDUs. Note that if the IS-IS LSPs in
>    a TRILL campus are authenticated, perhaps due to a concern about
>    forged packets, the ESADI PDUs will be authenticated by default as
>    provided in Section 6.3.
>
>
> > Nits/editorial comments:
> >
> > There are lots of acronyms that are not expanded on first use,
> > defined in the terminology section, or otherwise explained, e.g.,
> > DRB, Sz, CSNP, PSNP. It may be ok to point to terminology/acronym
> > definitions in RFC 6325.
>
> I believe these are all defined/expanded in RFC 6325 but it would
> still be a good idea to expand them on first use in this document.
>
>
> > Last sentence on p.8:
> >
> > OLD
> >    The outer VLAN tag will not be present if it was stripped by
> >    an Ethernet port out of which the packet was sent.
> > NEW
> >    The outer VLAN tag will not be present for a packet on an
> >    an Ethernet link that does not use VLAN tags.
>
> Well, whether or not any particular Ethernet frame carrying a TRILL
> Data packet is VLAN tagged or not depends on whether the port sending
> that frame is configured to send it tagged or untagged. There is no
> requirement or enforcement mechanism that all the ports on that
> Ethernet link be identically configured in this regard. So I do not
> consider it to be a property of the link.
>
>
> Also, Appendix A item 1: replces -> replaces
>
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
> > idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
> > RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
> > this is not a problem.
> >
> > idnits also warned about possible pre-RFC5378 (2008) content.  This
> > is probably not a problem, but please check with your AD.
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> > david.black@emc.com        Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From nobody Tue Apr  8 14:49:39 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0CA91A0696 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 14:49:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.001
X-Spam-Level: 
X-Spam-Status: No, score=-99.001 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 KZu5sjRlpyRv for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 14:49:33 -0700 (PDT)
Received: from dkim.winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id DC4601A04AF for <ietf@ietf.org>; Tue,  8 Apr 2014 14:49:30 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2734; t=1396993760; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=KsRubGYopeL0NsUvsG1ff98SwgQ=; b=bFAhaOxlB3HehYI3hI3l Uqa5/kiHC+LQ0rhNfoTwuL7ynUNU/T5Ec3sj+ti9/EVdPDnRfdr7yP4zNCY7CvN3 +rxVaxsM7aM8UHXXmIM9d9iEeNpjRFnemYlCmfWE41T6DKsklDstG4ydWqJxKFM7 wiXRjsEohzjy4BkHq2U8r/g=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 08 Apr 2014 17:49:20 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 102343675.3.3744; Tue, 08 Apr 2014 17:49:19 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2734; t=1396993706; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=jgRSVXx 9DqW2Bc2Lhs5AtWCVjDJNICOM+HylXtwdvWo=; b=OL8SrsVH/jbL2my884cDrF2 JxqU73+2QP0XWUZYunrPDEOCpY/QzXi3L4jCcQZaw5bwo/l+vUVD2MNxukDbrAHe 7gYUWt14BTu0Y6xX5kI2Io4ybcJvny10IjVv8D6fTIE0zkWXr2ltyjVZvOtJOB04 1NGv6ucCq7aQkDZFWbzM=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 08 Apr 2014 17:48:26 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 121882156.9.3304; Tue, 08 Apr 2014 17:48:25 -0400
Message-ID: <53446EDF.6090504@isdg.net>
Date: Tue, 08 Apr 2014 17:49:19 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org, IETF Announcement List <ietf-announce@ietf.org>
Subject: Re: Community Input Requested on =?UTF-8?B?VHJ1c3RlZXPigJkgSW50ZQ==?= =?UTF-8?B?bnQgdG8gUmVub3VuY2Ug4oCcSUVURiBTZWNyZXRhcmlhdOKAnSBUcmFkZW1hcms=?=
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
In-Reply-To: <20140404180001.19898.85635.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TINw0B1uDdKWRegX3ZgV8wEL4I0
Cc: iaoc@ietf.org, iab@iab.org, iesg@ietf.org, wgchairs@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 21:49:36 -0000

I don't see a legal issue or lost of trademark infringement protection 
for the reason stated.  I would suggest that, if necessary, the IETF 
could still legally list "IETF Secretariat" as a trademark <TM>, just 
not registered (R).

--
HLS

On 4/4/2014 2:00 PM, IETF Administrative Director wrote:
> All;
>
> The Trustees of the IETF Trust have voted an intent to renounce (abandon) the â€œIETF Secretariatâ€�
> trademark, but before taking any action they desire to hear from the community.
>
> Specifically:
>
> It is the Trusteesâ€™ intent to:
>
> 1. Not renew the â€œIETF Secretariatâ€� trademark, Registration 3860848, in the European Community
> at an approximate cost of $5,000 USD for a ten-year period when due on May 28, 2014, and
> thereby renounce the trademark as having no foreseeable future value in accordance with Article 7.1a
> of the Amended and Restated Trust Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.
> The trademark has no foreseeable future value as the â€œIETFâ€� trademark is registered in the European
> Community and its use with Secretariat is protected.
>
> 2. Not renew the â€œIETF Secretariatâ€� trademark, Registration 2392833, in the United States at an unknown
> future cost when the trademark expires on October 10, 2020, and thereby renounce the trademark as
> having no foreseeable future value in accordance with Article 7.1a of the Amended and Restated Trust
> Agreement, <http://trustee.ietf.org/trust-agreement-2014.html>.  The trademark has no foreseeable
> future value as the â€œIETFâ€� trademark is registered in the United States and its use with Secretariat is
> protected.
>
> Authority:
>
> The Trustees have the authority to renounce the trademark in accordance with Article 7.1a of the
> Amended and Restated Trust Agreement after consulting with the Beneficiary.
> <http://trustee.ietf.org/trust-agreement-2014.html>
>
> This Article states in relevant part:
> "the Trustees may, after due consultation with the Beneficiary, dispose of, assign, sell, transfer,
> renounce, convey or terminate Trust Assets that are of no current or foreseeable future value to
> the Beneficiary and which require the expenditure of funds to retain.This exception does not
> include RFCs.â€�
>
> The purpose of this announcement is to begin the consultation with the Beneficiary, the IETF
> Community.  This thirty (30) day comment period expires on 5 May 2014.  The Trustees will consider
> the Community input before making a decision whether to renounce the â€œIETF Secretariatâ€� trademark
> or not.
>
> Your feedback is appreciated.
>
> Thanks
> Ray Pelletier
> IETF Administrative Director
> Trustee
> IETF Trust
>
>
>



From nobody Tue Apr  8 16:05:38 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67EDF1A0767; Tue,  8 Apr 2014 16:05:28 -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, SPF_PASS=-0.001] autolearn=unavailable
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 p-GZ33UmVKBa; Tue,  8 Apr 2014 16:05:27 -0700 (PDT)
Received: from mail-yh0-x22d.google.com (mail-yh0-x22d.google.com [IPv6:2607:f8b0:4002:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id DDD261A075C; Tue,  8 Apr 2014 16:05:26 -0700 (PDT)
Received: by mail-yh0-f45.google.com with SMTP id a41so1617488yho.32 for <multiple recipients>; Tue, 08 Apr 2014 16:05:26 -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:content-type; bh=VcbWQmbw3rPntD9Q5dJz/9jQxrJs6Ctb7jjdwTUxU9k=; b=jEyPHWSKcl8hvsBSTmOhO9GJJs7vXzLAhGsYx/Gzg0Z68YAds9AXUD4hf54FoJiU5s MOCAoJuF3EpF2R/IsCyrRrFnaD4R9opd1O+9/Wnlao8YKucSSrHOMvK180EEfrFpJ28J vcrcAg/uDgrdDFIyj2PlpQ2MqNn3TcUkmkVJNn/cy5gXHZY7NAqNRYc0Lnyji8Z4kn4j u2uPZ5+ShbvWZJjwMAvc7sEptTwpEVpyIq9Nb3nS9mKXBO3uSMAIevG7Gtv035SC44Ou nNVXdIGGxKm1URpzRfr6xcZDn9+yq9e4JTQkw9QTU2zVfgwrnQJAFC0vcjVT7jDGOoQU Ks2A==
MIME-Version: 1.0
X-Received: by 10.236.85.45 with SMTP id t33mr9202655yhe.74.1396998326576; Tue, 08 Apr 2014 16:05:26 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Tue, 8 Apr 2014 16:05:26 -0700 (PDT)
In-Reply-To: <53446EDF.6090504@isdg.net>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <53446EDF.6090504@isdg.net>
Date: Wed, 9 Apr 2014 00:05:26 +0100
Message-ID: <CADnDZ8972WfDumGrSSK3a9fuJSAv69d3_O1t2sBn0nDT5bTbLA@mail.gmail.com>
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: multipart/alternative; boundary=20cf3005dd4e020f1004f6900562
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Z4ZX8D8dADsXQr4BOFYcxHYK6Tc
Cc: "wgchairs@ietf.org" <wgchairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "iaoc@ietf.org" <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "iesg@ietf.org" <iesg@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Apr 2014 23:05:28 -0000

--20cf3005dd4e020f1004f6900562
Content-Type: text/plain; charset=ISO-8859-1

On Tuesday, April 8, 2014, Hector Santos wrote:

> I don't see a legal issue or lost of trademark infringement protection for
> the reason stated.  I would suggest that, if necessary, the IETF could
> still legally list "IETF Secretariat" as a trademark <TM>, just not
> registered (R)


Yes. However, I don't understand what is the real value of that
registered mark. I don't understand why it was started/continued in the
first place for such volunteering organisation. If IETF
community agree/identifies that there are some values, then we can find
alternatives. Mostly we only need the one IETF trademark.

AB



>

--20cf3005dd4e020f1004f6900562
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br>On Tuesday, April 8, 2014, Hector Santos  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">I don&#39;t see a legal issue or lost of trademark infringeme=
nt protection for the reason stated. =A0I would suggest that, if necessary,=
 the IETF could still legally list &quot;IETF Secretariat&quot; as a tradem=
ark &lt;TM&gt;, just not registered (R)</blockquote>
<div><br></div><div>Yes. However,=A0I don&#39;t understand what is the real=
=A0value of that registered=A0mark. I don&#39;t understand why it was start=
ed/continued=A0in the first place for such volunteering organisation. If IE=
TF community=A0agree/identifies that=A0there are some values, then we can f=
ind alternatives. Mostly we only need the=A0one IETF=A0trademark.=A0</div>
<div><br></div><div>AB</div><div><br></div><div>=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
</blockquote>
</blockquote>

--20cf3005dd4e020f1004f6900562--


From nobody Tue Apr  8 17:03:40 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD4AA1A04A7 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 17:03:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 4K952IrKPDG0 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 17:03:36 -0700 (PDT)
Received: from mail-yh0-x236.google.com (mail-yh0-x236.google.com [IPv6:2607:f8b0:4002:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9AA1A04A6 for <ietf@ietf.org>; Tue,  8 Apr 2014 17:03:36 -0700 (PDT)
Received: by mail-yh0-f54.google.com with SMTP id f73so1673019yha.13 for <ietf@ietf.org>; Tue, 08 Apr 2014 17:03:36 -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:from:date:message-id :subject:to:cc:content-type; bh=ORhzItk2fDHik6BQOEX/0IqsWmZKtodvyF3R6XJDmpw=; b=zgiHZzA/bVCeYtyeBkBVwKLOjl0/zQt+TBP/HbC065TAh/yZpsE8uiwpEAqTUEKyFm 2uVr2qdNnmoqpy18xUehCjsqsmnRWLKzx7PYyetd60cb0jvbjQTa4TCdMVNgeP7eMnwR zHQya9O+ZwK3ZUNwfH7ATjWP+xiYewmA52clvGp55U9O24K4j3NTaXM4UbP+ZxKqyM+u szChGIK/NzvjrST3W3zFxix/GRG+ZKlFQECXs3ISqFqzQpNjduH9uK9MyZwFDq089K0D czDnhZV2y6cRbLx5dm8mJlbiCYDkJyIr0b1NvrW9J3d1bseQn/jXCd6bYqRx5HUWzHUX kJww==
X-Received: by 10.236.149.38 with SMTP id w26mr7375555yhj.51.1397001816182; Tue, 08 Apr 2014 17:03:36 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Tue, 8 Apr 2014 17:02:56 -0700 (PDT)
In-Reply-To: <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net>
From: Dick Franks <rwfranks@acm.org>
Date: Wed, 9 Apr 2014 01:02:56 +0100
X-Google-Sender-Auth: oPcz_y1BgzfRMxZ_cC42Wzc9JPk
Message-ID: <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com>
Subject: Re: Security for various IETF services
To: "t.p." <daedulus@btconnect.com>
Content-Type: multipart/alternative; boundary=20cf302efb0201121e04f690d5d2
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HtKaO8tcYDlZ11A3yMgXrHsnw8s
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 00:03:37 -0000

--20cf302efb0201121e04f690d5d2
Content-Type: text/plain; charset=UTF-8

On 8 April 2014 09:32, t.p. <daedulus@btconnect.com> wrote:

>
>
> The path that I have seen several Security ADs steer Working Groups down
> is to start with a threat analysis before deciding what counter measures
> are appropriate.
>
>
Several contributors have been saying exactly that for almost a week.

These suggestions have been answered by dismissive emails and a relentless
bombardment of magic pixie dust.

--20cf302efb0201121e04f690d5d2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On 8 April 2014 09:32, t.p. <span dir=3D"ltr">&lt;<a href=3D"mailto:daedulu=
s@btconnect.com" target=3D"_blank">daedulus@btconnect.com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">

<div class=3D""><br>
<br>
</div>The path that I have seen several Security ADs steer Working Groups d=
own<br>
is to start with a threat analysis before deciding what counter measures<br=
>
are appropriate.<br>
<br></blockquote><div><br></div><div>Several contributors have been saying =
exactly that for almost a week.<br><br></div><div>These suggestions have be=
en answered by dismissive emails and a relentless bombardment of magic pixi=
e dust.<br>

</div><br></div><br></div></div>

--20cf302efb0201121e04f690d5d2--


From nobody Tue Apr  8 18:04:46 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDB41A075A; Tue,  8 Apr 2014 18:04:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 FLlMEOP4ssFX; Tue,  8 Apr 2014 18:04:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AA2D91A0758; Tue,  8 Apr 2014 18:04:40 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.128.104]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3914S1V018084 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 8 Apr 2014 18:04:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397005479; bh=JEjOjiU7rFiRJG90aB43+SUap5w4n+z5acQzee3U/XU=; h=Date:To:From:Subject:Cc; b=rGamFG4U2+7qvKppm0jLNbVjoFvEnUoTSiz/kQbROS0M9XMHc/NIiLP92Cc6ldMx0 zchIfQ5LxzihonmSw9r0lckQq93rzqhZQC3OoQqb3kKcp3pIowxLcYacCH3ramE/Yb AlTG6lQSibC1rVTHbVDvE/MlJ5iryN1BP76lpH+U=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397005479; i=@elandsys.com; bh=JEjOjiU7rFiRJG90aB43+SUap5w4n+z5acQzee3U/XU=; h=Date:To:From:Subject:Cc; b=pUqt10T5pOABk+5g2b6/BfnUu+F5SWIZywfXvRHDycaqGw/CUeoea9IHI0ci7RBdt K8Iz+HtKZrWwYEte6Sd81M7/LQ4TWw6OfDVd4zKKj3XwxbQeOmt1IiXxXRAf4QiAm9 rGE08E0TBGn9+ajxuScSJkbU5Scwqpnh+b2z52So=
Message-Id: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 08 Apr 2014 18:01:17 -0700
To: iesg@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-0Es1ehzoW4yFu6NseSDapQRqo4
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 01:04:45 -0000

Hello,

The Ed25519 signature algorithm has been implemented in OpenSSH.  RFC 
4255 defines a DNS resource record, "SSHFP", which can be used to 
publish a fingerprint of the SSH server publickey in the 
DNS.  draft-moonesamy-sshfp-ed25519 
(http://tools.ietf.org/html/draft-moonesamy-sshfp-ed25519-01 ) is a 
request for a code point assignment for ED25519 in the SSHFP RR Types 
for public key algorithms registry.  The draft has received comments 
in SAAG and (IRTF) CFRG:

http://www.ietf.org/mail-archive/web/saag/current/msg04584.html
http://www.ietf.org/mail-archive/web/saag/current/msg04588.html
http://www.ietf.org/mail-archive/web/saag/current/msg04827.html
http://www.ietf.org/mail-archive/web/saag/current/msg04828.html
http://www.ietf.org/mail-archive/web/saag/current/msg04829.html
http://www.ietf.org/mail-archive/web/cfrg/current/msg04411.html
http://www.ietf.org/mail-archive/web/cfrg/current/msg04412.html
http://www.ietf.org/mail-archive/web/cfrg/current/msg04414.html
http://www.ietf.org/mail-archive/web/cfrg/current/msg04422.html

I responded to the comments.  There hasn't been any objections.  It 
seems to me that the Security Area Director is a bit slow in 
processing this request for a code point assignment.  I would 
appreciate if some information could be provided to explain the delay.

Regards,
S. Moonesamy


From nobody Tue Apr  8 19:12:46 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62AE11A0055 for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 19:12:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 bb2u5ZQftCRs for <ietf@ietfa.amsl.com>; Tue,  8 Apr 2014 19:12:43 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.145]) by ietfa.amsl.com (Postfix) with ESMTP id 4DAD41A0735 for <ietf@ietf.org>; Tue,  8 Apr 2014 19:12:43 -0700 (PDT)
Received: from [195.245.231.67:30853] by server-9.bemta-5.messagelabs.com id 5F/2D-04350-A9CA4435; Wed, 09 Apr 2014 02:12:42 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-12.tower-82.messagelabs.com!1397009561!33933628!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29705 invoked from network); 9 Apr 2014 02:12:42 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-12.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 9 Apr 2014 02:12:42 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 9 Apr 2014 03:12:41 +0100
From: <l.wood@surrey.ac.uk>
To: <rwfranks@acm.org>, <daedulus@btconnect.com>
Date: Wed, 9 Apr 2014 03:12:07 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9Thzq45VwCSS/wT5aApzO4bGzkvwAEeCrM
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EECE@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net>, <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com>
In-Reply-To: <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/l4YqLBOXvu19HmZTpAV7hi2oEA4
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 02:12:45 -0000

Gee, you don't need a threat analysis when you're going to protect against =
EVERYTHING!

That's SECURITY!

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Dick Franks [rwfranks@acm.o=
rg]
Sent: 09 April 2014 01:02
To: t.p.
Cc: IETF-Discussion
Subject: Re: Security for various IETF services

On 8 April 2014 09:32, t.p. <daedulus@btconnect.com<mailto:daedulus@btconne=
ct.com>> wrote:


The path that I have seen several Security ADs steer Working Groups down
is to start with a threat analysis before deciding what counter measures
are appropriate.


Several contributors have been saying exactly that for almost a week.

These suggestions have been answered by dismissive emails and a relentless =
bombardment of magic pixie dust.



From nobody Wed Apr  9 01:38:27 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 931831A0160 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 01:38:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 yQs90XvqB1Lz for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 01:38:20 -0700 (PDT)
Received: from mail-ee0-x234.google.com (mail-ee0-x234.google.com [IPv6:2a00:1450:4013:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id 1E88D1A019E for <ietf@ietf.org>; Wed,  9 Apr 2014 01:38:16 -0700 (PDT)
Received: by mail-ee0-f52.google.com with SMTP id e49so1559070eek.39 for <ietf@ietf.org>; Wed, 09 Apr 2014 01:38:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=H/9YDZv46y903S58CGw1fKsNJv842uN6oa70MPygX8s=; b=JnI955ir2CVfSd4nkcakwmLQWeOfIda2LEtmUvn4DDParV4d3Xt5JaIwMaWPayrbS4 2jkQ4+QZXsv+fZUEsgoe1tFJZM4R18nMRYGmKVFkQ9HTjU4U7E5+NIm4jNPVYHYBm9lW uACs86/PuDV584tvEYJ+Ob96syEhro+a47I6yDpdPVgubYygTfIMke/Hl4uIplZbFNNs Ff3mPR76xe6bj43fHHQfrs4q974UuPSrNIPEF6oZZNrQyW2B0nnmLSiiFgoP6lFDqzUu 3IY9LditGmenuuX8+0UEJv2Ih4jxb+WsCQhlY8tnyWLBG2FApPcBdocBx72uIpp+4mEl 3QjQ==
X-Received: by 10.15.90.201 with SMTP id q49mr1308579eez.65.1397032696291; Wed, 09 Apr 2014 01:38:16 -0700 (PDT)
Received: from [192.168.243.52] ([192.116.177.210]) by mx.google.com with ESMTPSA id 48sm781232eei.24.2014.04.09.01.38.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Apr 2014 01:38:14 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_C4F474F3-091A-4B6D-99CF-0949C3271EEA"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com>
Date: Wed, 9 Apr 2014 11:38:12 +0300
Message-Id: <A1442D4F-DB3F-4A69-B42C-C89BD3758104@gmail.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net> <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com>
To: Dick Franks <rwfranks@acm.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ap_t3qJBBgTJnw_kaY_tVkyCcLA
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 08:38:24 -0000

--Apple-Mail=_C4F474F3-091A-4B6D-99CF-0949C3271EEA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 9, 2014, at 3:02 AM, Dick Franks <rwfranks@acm.org> wrote:

>=20
> On 8 April 2014 09:32, t.p. <daedulus@btconnect.com> wrote:
>=20
>=20
> The path that I have seen several Security ADs steer Working Groups =
down
> is to start with a threat analysis before deciding what counter =
measures
> are appropriate.
>=20
>=20
> Several contributors have been saying exactly that for almost a week.
>=20
> These suggestions have been answered by dismissive emails and a =
relentless bombardment of magic pixie dust.


The thing is, the IETF websites are not that special. There=92s a bunch =
of information, most of it public. The sites accept payments by credit =
card thrice a year. There=92s a wiki. There=92s some mailing lists with =
archives and registration pages, There=92s content that can be edited by =
privileged users, and there=92s other content that can be uploaded by =
anyone and viewed by anyone. Pretty much any corporate website has these =
parts.

The point of having best practices is that we don=92t need to think =
about a threat model for each website. It=92s a set of practices that =
someone has called =93best practices=94 because they protect against =
several common types of attack at a low enough cost, that many web sites =
can implement them without actually proving to management that each part =
is strictly necessary.

Sure, we can have a debate here about the security needs of each service =
provided and have some of the most knowledgeable experts debate whether =
the www.ietf.org should have HTTP access, while datatracker.ietf.org =
should have only HTTPS, and tools. should have both and HSTS and HPKP to =
boot. But that is not eating our own dog food, because the next =93store =
that sells soap making supplies on the =91net=94 will not have access to =
such expertise. Our dogfood should be implementable by people who don=92t =
read these mailing lists - the web site developer that said store hires. =
Hence the need for =93best practices=94 shortcuts, which are very much a =
part of all branches of engineering.

That said, if there are security implications that are not common to =
regular websites, these should be considered and discussed. For example, =
if reading drafts and RFCs from the office might betray your company=92s =
future plans, that is a good reason to allow encrypted access to RFCs. =
Or if reading certain articles on Wikipedia can get you in trouble in =
some countries, then encrypted access to those may be in order. And if =
having both encrypted and non-encrypted access results in encrypted =
access being red-flagged as subversive, that may be a good argument for =
encrypted access by default or even exclusively.=20

But before diving into such a discussion we need to have a good argument =
for what makes us so special.

Yoav



--Apple-Mail=_C4F474F3-091A-4B6D-99CF-0949C3271EEA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Apr 9, 2014, at 3:02 AM, Dick =
Franks &lt;<a href=3D"mailto:rwfranks@acm.org">rwfranks@acm.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On 8 April 2014 09:32, t.p. <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:daedulus@btconnect.com" =
target=3D"_blank">daedulus@btconnect.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">

<div class=3D""><br>
<br>
</div>The path that I have seen several Security ADs steer Working =
Groups down<br>
is to start with a threat analysis before deciding what counter =
measures<br>
are appropriate.<br>
<br></blockquote><div><br></div><div>Several contributors have been =
saying exactly that for almost a week.<br><br></div><div>These =
suggestions have been answered by dismissive emails and a relentless =
bombardment of magic pixie =
dust.</div></div></div></div></blockquote></div><div><br></div><div>The =
thing is, the IETF websites are not that special. There=92s a bunch of =
information, most of it public. The sites accept payments by credit card =
thrice a year. There=92s a wiki. There=92s some mailing lists with =
archives and registration pages, There=92s content that can be edited by =
privileged users, and there=92s other content that can be uploaded by =
anyone and viewed by anyone. Pretty much any corporate website has these =
parts.</div><div><br></div><div>The point of having best practices is =
that we don=92t need to think about a threat model for each website. =
It=92s a set of practices that someone has called =93best practices=94 =
because they protect against several common types of attack at a low =
enough cost, that many web sites can implement them without actually =
proving to management that each part is strictly =
necessary.</div><div><br></div><div>Sure, we can have a debate here =
about the security needs of each service provided and have some of the =
most knowledgeable experts debate whether the <a =
href=3D"http://www.ietf.org">www.ietf.org</a> should have HTTP access, =
while <a href=3D"http://datatracker.ietf.org">datatracker.ietf.org</a> =
should have only HTTPS, and tools. should have both and HSTS and HPKP to =
boot. But that is not eating our own dog food, because the next =93store =
that sells soap making supplies on the =91net=94 will not have access to =
such expertise. Our dogfood should be implementable by people who don=92t =
read these mailing lists - the web site developer that said store hires. =
Hence the need for =93best practices=94 shortcuts, which are very much a =
part of all branches of engineering.</div><div><br></div><div>That said, =
if there are security implications that are not common to regular =
websites, these should be considered and discussed. For example, if =
reading drafts and RFCs from the office might betray your company=92s =
future plans, that is a good reason to allow encrypted access to RFCs. =
Or if reading certain articles on Wikipedia can get you in trouble in =
some countries, then encrypted access to those may be in order. And if =
having both encrypted and non-encrypted access results in encrypted =
access being red-flagged as subversive, that may be a good argument for =
encrypted access by default or even =
exclusively.&nbsp;</div><div><br></div><div>But before diving into such =
a discussion we need to have a good argument for what makes us so =
special.</div><div><br></div><div>Yoav</div><div><br></div><br></body></ht=
ml>=

--Apple-Mail=_C4F474F3-091A-4B6D-99CF-0949C3271EEA--


From nobody Wed Apr  9 01:43:38 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F30341A0689 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 01:43:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 bfGLl2EemTut for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 01:43:33 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 2271B1A01B0 for <ietf@ietf.org>; Wed,  9 Apr 2014 01:43:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 17B56BE83; Wed,  9 Apr 2014 09:43:09 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KnWIx1e793Ea; Wed,  9 Apr 2014 09:43:07 +0100 (IST)
Received: from [10.87.48.4] (unknown [86.45.52.44]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 2FD57BE79; Wed,  9 Apr 2014 09:43:07 +0100 (IST)
Message-ID: <5345081A.8070802@cs.tcd.ie>
Date: Wed, 09 Apr 2014 09:43:06 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, rwfranks@acm.org, daedulus@btconnect.com
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net>, <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E779EECE@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EECE@EXMB01CMS.surrey.ac.uk>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7c_D5bdSh6OUCz2AcykJ4Oo3QBI
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 08:43:38 -0000

I love how folks who it seems would rather we do nothing
are asking for more security process in this case.

IMO, the tools folks haven't gone terribly wrong on this in
the past and are not likely to do so in future. We are also
not developing new protocols for broad Internet use here
but rather talking about an IESG statement that those who
develop tooling and who deploy services should find useful
when considering new IETF services such as some new web
tool or remote participation tool. The statement also
reminds them to not go OTT and break stuff just in order
to improve security.

So no, we do not need a common criteria evaluation for
this and we will not suddenly forget how to do sound
engineering and no we do not need to do all that
engineering right now for every possible future service
and nor do we need to include "don't forget to do
engineering" in this IESG statement.

Regards,
S.

On 04/09/2014 03:12 AM, l.wood@surrey.ac.uk wrote:
> Gee, you don't need a threat analysis when you're going to protect against EVERYTHING!
> 
> That's SECURITY!
> 
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Dick Franks [rwfranks@acm.org]
> Sent: 09 April 2014 01:02
> To: t.p.
> Cc: IETF-Discussion
> Subject: Re: Security for various IETF services
> 
> On 8 April 2014 09:32, t.p. <daedulus@btconnect.com<mailto:daedulus@btconnect.com>> wrote:
> 
> 
> The path that I have seen several Security ADs steer Working Groups down
> is to start with a threat analysis before deciding what counter measures
> are appropriate.
> 
> 
> Several contributors have been saying exactly that for almost a week.
> 
> These suggestions have been answered by dismissive emails and a relentless bombardment of magic pixie dust.
> 
> 
> 
> 


From nobody Wed Apr  9 01:59:39 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C590E1A01AF for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 01:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 IT7bV_khkXxL for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 01:59:33 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.152]) by ietfa.amsl.com (Postfix) with ESMTP id 059FE1A01AB for <ietf@ietf.org>; Wed,  9 Apr 2014 01:59:32 -0700 (PDT)
Received: from [195.245.231.67:47825] by server-16.bemta-5.messagelabs.com id 8C/0C-19700-4FB05435; Wed, 09 Apr 2014 08:59:32 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-82.messagelabs.com!1397033971!25868362!2
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28633 invoked from network); 9 Apr 2014 08:59:31 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-11.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 9 Apr 2014 08:59:31 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 9 Apr 2014 09:59:30 +0100
From: <l.wood@surrey.ac.uk>
To: <ynir.ietf@gmail.com>, <rwfranks@acm.org>
Date: Wed, 9 Apr 2014 09:54:42 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9TzylyoALiO/RaQ+m7yme8v5VM7gAAi91U
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EECF@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net> <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com>, <A1442D4F-DB3F-4A69-B42C-C89BD3758104@gmail.com>
In-Reply-To: <A1442D4F-DB3F-4A69-B42C-C89BD3758104@gmail.com>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jk2mI1javAsLGnGrMW5XaM92Ofs
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 08:59:38 -0000

Yoav,

the problem here is that the perpass work (also spearheaded by Stephen) has=
 redefined what 'best practice' is.

perpass gives the security contingent of the IETF no limit in mitigation of=
 pervasive monitoring -
which means making everything as secure and private as possible, even when =
common sense,
threat analysis and conventional 'best practice' would say otherwise.

perpass makes the IETF special.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Yoav Nir [ynir.ietf@gmail.c=
om]
Sent: 09 April 2014 09:38
To: Dick Franks
Cc: IETF-Discussion
Subject: Re: Security for various IETF services

On Apr 9, 2014, at 3:02 AM, Dick Franks <rwfranks@acm.org<mailto:rwfranks@a=
cm.org>> wrote:


On 8 April 2014 09:32, t.p. <daedulus@btconnect.com<mailto:daedulus@btconne=
ct.com>> wrote:


The path that I have seen several Security ADs steer Working Groups down
is to start with a threat analysis before deciding what counter measures
are appropriate.


Several contributors have been saying exactly that for almost a week.

These suggestions have been answered by dismissive emails and a relentless =
bombardment of magic pixie dust.

The thing is, the IETF websites are not that special. There=92s a bunch of =
information, most of it public. The sites accept payments by credit card th=
rice a year. There=92s a wiki. There=92s some mailing lists with archives a=
nd registration pages, There=92s content that can be edited by privileged u=
sers, and there=92s other content that can be uploaded by anyone and viewed=
 by anyone. Pretty much any corporate website has these parts.

The point of having best practices is that we don=92t need to think about a=
 threat model for each website. It=92s a set of practices that someone has =
called =93best practices=94 because they protect against several common typ=
es of attack at a low enough cost, that many web sites can implement them w=
ithout actually proving to management that each part is strictly necessary.

Sure, we can have a debate here about the security needs of each service pr=
ovided and have some of the most knowledgeable experts debate whether the w=
ww.ietf.org<http://www.ietf.org> should have HTTP access, while datatracker=
.ietf.org<http://datatracker.ietf.org> should have only HTTPS, and tools. s=
hould have both and HSTS and HPKP to boot. But that is not eating our own d=
og food, because the next =93store that sells soap making supplies on the =
=91net=94 will not have access to such expertise. Our dogfood should be imp=
lementable by people who don=92t read these mailing lists - the web site de=
veloper that said store hires. Hence the need for =93best practices=94 shor=
tcuts, which are very much a part of all branches of engineering.

That said, if there are security implications that are not common to regula=
r websites, these should be considered and discussed. For example, if readi=
ng drafts and RFCs from the office might betray your company=92s future pla=
ns, that is a good reason to allow encrypted access to RFCs. Or if reading =
certain articles on Wikipedia can get you in trouble in some countries, the=
n encrypted access to those may be in order. And if having both encrypted a=
nd non-encrypted access results in encrypted access being red-flagged as su=
bversive, that may be a good argument for encrypted access by default or ev=
en exclusively.

But before diving into such a discussion we need to have a good argument fo=
r what makes us so special.

Yoav



From nobody Wed Apr  9 02:05:23 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C24A71A079F for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 02:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 hjfwwNGDmi2X for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 02:05:17 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) by ietfa.amsl.com (Postfix) with ESMTP id 29D9C1A01B4 for <ietf@ietf.org>; Wed,  9 Apr 2014 02:05:17 -0700 (PDT)
Received: from [85.158.137.99:37343] by server-12.bemta-3.messagelabs.com id 47/48-14831-A4D05435; Wed, 09 Apr 2014 09:05:14 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-217.messagelabs.com!1397034313!15022657!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 29672 invoked from network); 9 Apr 2014 09:05:14 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-5.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 9 Apr 2014 09:05:14 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 9 Apr 2014 10:05:13 +0100
From: <l.wood@surrey.ac.uk>
To: <stephen.farrell@cs.tcd.ie>, <rwfranks@acm.org>, <daedulus@btconnect.com>
Date: Wed, 9 Apr 2014 10:05:12 +0100
Subject: RE: Security for various IETF services
Thread-Topic: Security for various IETF services
Thread-Index: Ac9Tz8JJ4cz1vFOYTpSWbn235cQZMQAAkUlS
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EED0@EXMB01CMS.surrey.ac.uk>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net>, <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E779EECE@EXMB01CMS.surrey.ac.uk>, <5345081A.8070802@cs.tcd.ie>
In-Reply-To: <5345081A.8070802@cs.tcd.ie>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gJTCxKyrZ1ENYpgEJJ_wEPDDIUM
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 09:05:21 -0000

Stephen,

once again I refer you to
http://www.ietf.org/mail-archive/web/ietf/current/msg81787.html

> we will not suddenly forget how to do sound engineering=20

oddly enough, that happens. DTNRG forgot checksums, the
end-to-end-principle, designing for embedded systems...

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Stephen Farrell [stephen.farrell@cs.tcd.ie]
Sent: 09 April 2014 09:43
To: Wood L  Dr (Electronic Eng); rwfranks@acm.org; daedulus@btconnect.com
Cc: ietf@ietf.org
Subject: Re: Security for various IETF services

I love how folks who it seems would rather we do nothing
are asking for more security process in this case.

IMO, the tools folks haven't gone terribly wrong on this in
the past and are not likely to do so in future. We are also
not developing new protocols for broad Internet use here
but rather talking about an IESG statement that those who
develop tooling and who deploy services should find useful
when considering new IETF services such as some new web
tool or remote participation tool. The statement also
reminds them to not go OTT and break stuff just in order
to improve security.

So no, we do not need a common criteria evaluation for
this and we will not suddenly forget how to do sound
engineering and no we do not need to do all that
engineering right now for every possible future service
and nor do we need to include "don't forget to do
engineering" in this IESG statement.

Regards,
S.

On 04/09/2014 03:12 AM, l.wood@surrey.ac.uk wrote:
> Gee, you don't need a threat analysis when you're going to protect agains=
t EVERYTHING!
>
> That's SECURITY!
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Dick Franks [rwfranks@acm=
.org]
> Sent: 09 April 2014 01:02
> To: t.p.
> Cc: IETF-Discussion
> Subject: Re: Security for various IETF services
>
> On 8 April 2014 09:32, t.p. <daedulus@btconnect.com<mailto:daedulus@btcon=
nect.com>> wrote:
>
>
> The path that I have seen several Security ADs steer Working Groups down
> is to start with a threat analysis before deciding what counter measures
> are appropriate.
>
>
> Several contributors have been saying exactly that for almost a week.
>
> These suggestions have been answered by dismissive emails and a relentles=
s bombardment of magic pixie dust.
>
>
>
>


From nobody Wed Apr  9 02:06:43 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA6B1A01B0 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 02:06:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 DLC2V5TL-Tti for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 02:06:41 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A79191A0171 for <ietf@ietf.org>; Wed,  9 Apr 2014 02:06:40 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id F0040BE79 for <ietf@ietf.org>; Wed,  9 Apr 2014 10:06:39 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AK3jrc8MgHaM for <ietf@ietf.org>; Wed,  9 Apr 2014 10:06:38 +0100 (IST)
Received: from [10.87.48.4] (unknown [86.45.52.44]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 35C1DBE87 for <ietf@ietf.org>; Wed,  9 Apr 2014 10:06:38 +0100 (IST)
Message-ID: <53450D9D.5040002@cs.tcd.ie>
Date: Wed, 09 Apr 2014 10:06:37 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net> <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com>, <A1442D4F-DB3F-4A69-B42C-C89BD3758104@gmail.com> <290E20B455C66743BE178C5C84F1240847E779EECF@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EECF@EXMB01CMS.surrey.ac.uk>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uWal5uuHd_NLiVVi_mGnYJYMHKU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 09:06:42 -0000

Just in the highly improbable case that its not entirely
obvious: Lloyd is talking utter nonsense. (As usual on
this topic, sadly.)

S

On 04/09/2014 09:54 AM, l.wood@surrey.ac.uk wrote:
> Yoav,
> 
> the problem here is that the perpass work (also spearheaded by Stephen) has redefined what 'best practice' is.
> 
> perpass gives the security contingent of the IETF no limit in mitigation of pervasive monitoring -
> which means making everything as secure and private as possible, even when common sense,
> threat analysis and conventional 'best practice' would say otherwise.
> 
> perpass makes the IETF special.
> 
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Yoav Nir [ynir.ietf@gmail.com]
> Sent: 09 April 2014 09:38
> To: Dick Franks
> Cc: IETF-Discussion
> Subject: Re: Security for various IETF services
> 
> On Apr 9, 2014, at 3:02 AM, Dick Franks <rwfranks@acm.org<mailto:rwfranks@acm.org>> wrote:
> 
> 
> On 8 April 2014 09:32, t.p. <daedulus@btconnect.com<mailto:daedulus@btconnect.com>> wrote:
> 
> 
> The path that I have seen several Security ADs steer Working Groups down
> is to start with a threat analysis before deciding what counter measures
> are appropriate.
> 
> 
> Several contributors have been saying exactly that for almost a week.
> 
> These suggestions have been answered by dismissive emails and a relentless bombardment of magic pixie dust.
> 
> The thing is, the IETF websites are not that special. There’s a bunch of information, most of it public. The sites accept payments by credit card thrice a year. There’s a wiki. There’s some mailing lists with archives and registration pages, There’s content that can be edited by privileged users, and there’s other content that can be uploaded by anyone and viewed by anyone. Pretty much any corporate website has these parts.
> 
> The point of having best practices is that we don’t need to think about a threat model for each website. It’s a set of practices that someone has called “best practices” because they protect against several common types of attack at a low enough cost, that many web sites can implement them without actually proving to management that each part is strictly necessary.
> 
> Sure, we can have a debate here about the security needs of each service provided and have some of the most knowledgeable experts debate whether the www.ietf.org<http://www.ietf.org> should have HTTP access, while datatracker.ietf.org<http://datatracker.ietf.org> should have only HTTPS, and tools. should have both and HSTS and HPKP to boot. But that is not eating our own dog food, because the next “store that sells soap making supplies on the ‘net” will not have access to such expertise. Our dogfood should be implementable by people who don’t read these mailing lists - the web site developer that said store hires. Hence the need for “best practices” shortcuts, which are very much a part of all branches of engineering.
> 
> That said, if there are security implications that are not common to regular websites, these should be considered and discussed. For example, if reading drafts and RFCs from the office might betray your company’s future plans, that is a good reason to allow encrypted access to RFCs. Or if reading certain articles on Wikipedia can get you in trouble in some countries, then encrypted access to those may be in order. And if having both encrypted and non-encrypted access results in encrypted access being red-flagged as subversive, that may be a good argument for encrypted access by default or even exclusively.
> 
> But before diving into such a discussion we need to have a good argument for what makes us so special.
> 
> Yoav
> 
> 
> 
> 


From nobody Wed Apr  9 02:12:25 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9402E1A0178 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 02:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 ABvzadqnl7wX for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 02:12:20 -0700 (PDT)
Received: from mail-ee0-x22d.google.com (mail-ee0-x22d.google.com [IPv6:2a00:1450:4013:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 6DD671A07AB for <ietf@ietf.org>; Wed,  9 Apr 2014 02:12:14 -0700 (PDT)
Received: by mail-ee0-f45.google.com with SMTP id d17so1598008eek.18 for <ietf@ietf.org>; Wed, 09 Apr 2014 02:12:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=aYsj/Ua7O/5plsj8Th+KMB11WJ3PL2vOYLSFmlzrpgk=; b=P0lQR8PZjDQZ7LDG4K3EibwlUD55/xGeOx7oKGzqlVaqDql5BGrAOCrNskIsl35fkO FCEcdDqv9llojnpif1NokJqA8bwRy/2C3a9y4Griym+2sOa26dBY/TYd1El0KRW53DBJ dQpvZZ04582Oiz/Y8f+M/m3a2SIEMdoIvqmC046HEywRjmynq7ZG0EsPlaqSi+ahD3cM xbQzLi4vyclfXl/nFWuj+EcABwA7nJRta7MkjqN0J92sj6hAPuI+gPzeG77qPf/gLEHl nZXFA8yM66SvrwaPrLVu6QoH/nnuA0d8upSEApX2gkkqzg048BwXqAtODL8ifAwGlL9g e6kQ==
X-Received: by 10.14.180.2 with SMTP id i2mr11226701eem.53.1397034733651; Wed, 09 Apr 2014 02:12:13 -0700 (PDT)
Received: from [192.168.243.52] ([192.116.177.210]) by mx.google.com with ESMTPSA id s46sm990653ees.3.2014.04.09.02.12.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 09 Apr 2014 02:12:13 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EECF@EXMB01CMS.surrey.ac.uk>
Date: Wed, 9 Apr 2014 12:12:06 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <165CB866-22F7-4B1E-8ECF-D55AAA7DBAAC@gmail.com>
References: <533D8A90.60309@cs.tcd.ie> <533EEF35.7070901@isdg.net> <27993A73-491B-4590-9F37-0C0D369B4C6F@cisco.com> <CAHBU6iuX8Y8VCgkY1Qk+DEPEgN2=DWbNEWVffyVmmP_3qmmmig@mail.gmail.com> <53427277.30707@cisco.com> <B275762E-3A1A-44A3-80BE-67F4C8B115B2@trammell.ch> <53428593.3020707@cs.tcd.ie> <A33A3F1E-8F6D-4BD9-8D1B-B24FBCD74D8D@nominum.com> <5342B26B.5020704@gmail.com> <011301cf532a$b4cd02a0$4001a8c0@gateway.2wire.net> <CAKW6Ri5=6eVEKvJ3SVrFxnX9Hd1vxUFW9n4p99g=NM+LHky9kA@mail.gmail.com>, <A1442D4F-DB3F-4A69-B42C-C89BD3758104@gmail.com> <290E20B455C66743BE178C5C84F1240847E779EECF@EXMB01CMS.surrey.ac.uk>
To: l.wood@surrey.ac.uk
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/d_5NXbLW1CCO56QDuGCiovzQlGk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 09:12:24 -0000

I disagree that this is not conventional best practice.

Since I brought up soap making supplies, I typed that in google and the =
first result was http://www.brambleberry.com That=92s a very =
conventional web store. It has instructional videos, forums for =
exchanging advice and recipes, and of course, the supplies themselves =
(with user-generated comments on each of them).=20

As soon as you log in (necessary for posting on the forums and =
commenting on the supplies), you=92re at HTTPS. You can use HTTP for =
browsing the videos, forums and comments, but if you=92ve logged in, you =
do that over HTTPS as well. I=92m pretty sure the people behind that =
store aren=92t following perpass.

How is the IETF different enough that it needs *less* encryption than =
this store? As long as we provide HTTP access to the I-D and RFC =
repository (our =93supplies=94), why doesn=92t it make sense to use =
HTTPS for other things?

Yoav

On Apr 9, 2014, at 11:54 AM, <l.wood@surrey.ac.uk> <l.wood@surrey.ac.uk> =
wrote:

> Yoav,
>=20
> the problem here is that the perpass work (also spearheaded by =
Stephen) has redefined what 'best practice' is.
>=20
> perpass gives the security contingent of the IETF no limit in =
mitigation of pervasive monitoring -
> which means making everything as secure and private as possible, even =
when common sense,
> threat analysis and conventional 'best practice' would say otherwise.
>=20
> perpass makes the IETF special.
>=20
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Yoav Nir =
[ynir.ietf@gmail.com]
> Sent: 09 April 2014 09:38
> To: Dick Franks
> Cc: IETF-Discussion
> Subject: Re: Security for various IETF services
>=20
> On Apr 9, 2014, at 3:02 AM, Dick Franks =
<rwfranks@acm.org<mailto:rwfranks@acm.org>> wrote:
>=20
>=20
> On 8 April 2014 09:32, t.p. =
<daedulus@btconnect.com<mailto:daedulus@btconnect.com>> wrote:
>=20
>=20
> The path that I have seen several Security ADs steer Working Groups =
down
> is to start with a threat analysis before deciding what counter =
measures
> are appropriate.
>=20
>=20
> Several contributors have been saying exactly that for almost a week.
>=20
> These suggestions have been answered by dismissive emails and a =
relentless bombardment of magic pixie dust.
>=20
> The thing is, the IETF websites are not that special. There=92s a =
bunch of information, most of it public. The sites accept payments by =
credit card thrice a year. There=92s a wiki. There=92s some mailing =
lists with archives and registration pages, There=92s content that can =
be edited by privileged users, and there=92s other content that can be =
uploaded by anyone and viewed by anyone. Pretty much any corporate =
website has these parts.
>=20
> The point of having best practices is that we don=92t need to think =
about a threat model for each website. It=92s a set of practices that =
someone has called =93best practices=94 because they protect against =
several common types of attack at a low enough cost, that many web sites =
can implement them without actually proving to management that each part =
is strictly necessary.
>=20
> Sure, we can have a debate here about the security needs of each =
service provided and have some of the most knowledgeable experts debate =
whether the www.ietf.org<http://www.ietf.org> should have HTTP access, =
while datatracker.ietf.org<http://datatracker.ietf.org> should have only =
HTTPS, and tools. should have both and HSTS and HPKP to boot. But that =
is not eating our own dog food, because the next =93store that sells =
soap making supplies on the =91net=94 will not have access to such =
expertise. Our dogfood should be implementable by people who don=92t =
read these mailing lists - the web site developer that said store hires. =
Hence the need for =93best practices=94 shortcuts, which are very much a =
part of all branches of engineering.
>=20
> That said, if there are security implications that are not common to =
regular websites, these should be considered and discussed. For example, =
if reading drafts and RFCs from the office might betray your company=92s =
future plans, that is a good reason to allow encrypted access to RFCs. =
Or if reading certain articles on Wikipedia can get you in trouble in =
some countries, then encrypted access to those may be in order. And if =
having both encrypted and non-encrypted access results in encrypted =
access being red-flagged as subversive, that may be a good argument for =
encrypted access by default or even exclusively.
>=20
> But before diving into such a discussion we need to have a good =
argument for what makes us so special.
>=20
> Yoav
>=20
>=20


From nobody Wed Apr  9 05:20:46 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 959EF1A028F; Wed,  9 Apr 2014 05:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.002
X-Spam-Level: 
X-Spam-Status: No, score=-0.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Xa9RuWm0fB41; Wed,  9 Apr 2014 05:20:40 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id C82251A028E; Wed,  9 Apr 2014 05:20:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A41851E4366; Wed,  9 Apr 2014 05:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rlek8XESiquY; Wed,  9 Apr 2014 05:20:31 -0700 (PDT)
Received: from [10.156.44.192] (unknown [192.165.183.201]) by c8a.amsl.com (Postfix) with ESMTPSA id D259C1E40EF; Wed,  9 Apr 2014 05:20:30 -0700 (PDT)
Subject: IANA changes process
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Content-Type: text/plain; charset=us-ascii
From: IETF Chair <chair@ietf.org>
In-Reply-To: <D272A88D-B935-4BAE-A649-13815E5896D3@ietf.org>
Date: Wed, 9 Apr 2014 14:20:32 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <14E4E6DE-CACF-4057-9308-49BC980A5197@ietf.org>
References: <D272A88D-B935-4BAE-A649-13815E5896D3@ietf.org>
To: internetgovtech@iab.org
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eeAI5U00vgO_FsnaU_9D4DqvrGo
Cc: "ietf@ietf.org List" <ietf@ietf.org>, "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "internetgovtech@iab.org" <internetgovtech@iab.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 12:20:44 -0000

A draft proposal for IANA transition process has been published by =
ICANN, based on early input gathered during their meeting two weeks ago.

=
http://www.icann.org/en/about/agreements/iana/transition/draft-proposal-08=
apr14-en.htm

We would be interested in opinions about this process from an IETF =
perspective. Please comment on the internetgovtech list.

Jari Arkko, IETF Chair


From nobody Wed Apr  9 05:45:26 2014
Return-Path: <lear@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE1FB1A0281 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 05:45:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 861suFm_V3nJ for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 05:45:20 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id 451A01A0251 for <ietf@ietf.org>; Wed,  9 Apr 2014 05:45:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1165; q=dns/txt; s=iport; t=1397047520; x=1398257120; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=puP7ogV91+rKAs+1WHCwf7w/1T37tOxKzOcz2VWID5E=; b=GzYpsXsaBNvz+s0eRIqjRpJ9V/eRkGt364B7dSSIFtNje7pGoKPtnDOd H0zzIgoMRT6hh7LV7d2UWMDxD0/s77s3yxIgeVru8PhJz+pq3mB0ZWnwq bSZ0zzuCSpegAarFMkDkeFExTbBR9eOYexZfje7b3ipp3DuBDcRV1tR6d A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhYKAOk/RVOtJssW/2dsb2JhbABZg0GDYsB8AgKBNnSCJQEBAQQjDwFGEAsYAgIFIQICDwJGBg0BBwEBBQuHaA2pU6IUF4EpjUMHgm+BSQEDiVWPCZJCgzU4
X-IronPort-AV: E=Sophos;i="4.97,826,1389744000"; d="scan'208";a="10135012"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 09 Apr 2014 12:45:18 +0000
Received: from ELEAR-M-C3ZS.CISCO.COM ([10.61.193.138]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s39CjIku008153; Wed, 9 Apr 2014 12:45:18 GMT
Message-ID: <534540DD.20107@cisco.com>
Date: Wed, 09 Apr 2014 16:45:17 +0400
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: IANA changes process
References: <D272A88D-B935-4BAE-A649-13815E5896D3@ietf.org> <14E4E6DE-CACF-4057-9308-49BC980A5197@ietf.org>
In-Reply-To: <14E4E6DE-CACF-4057-9308-49BC980A5197@ietf.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WwxRZ_meBdE8dI-_lDpaaEwnKfo
Cc: "internetgovtech@iab.org" <internetgovtech@iab.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 12:45:25 -0000

Hi Jari,

While I appreciate your measured tones, you may have understated the
situation in this case.  Two things are being proposed that require
careful consideration.  The first is the structure and process of how a
proposal to evolve the IANA functions.  The second is a statement about
what will be evolved and as important what will not change â€“ perhaps for
a very long time.  Our input is very important into the process, and it
will be important that we provide a comprehensive response in the coming
weeks.  This is the IETF community's chance to provide input into that
response.  On these two issues, there will not be another opportunity.

Eliot




In this case, people may not agree on

On 4/9/14, 4:20 PM, IETF Chair wrote:
> A draft proposal for IANA transition process has been published by ICANN, based on early input gathered during their meeting two weeks ago.
>
> http://www.icann.org/en/about/agreements/iana/transition/draft-proposal-08apr14-en.htm
>
> We would be interested in opinions about this process from an IETF perspective. Please comment on the internetgovtech list.
>
> Jari Arkko, IETF Chair
>
>
>


From nobody Wed Apr  9 06:12:24 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 237D51A02A4 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 06:12:22 -0700 (PDT)
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_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 8S5dptrh2CKu for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 06:12:17 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C49BB1A028C for <ietf@ietf.org>; Wed,  9 Apr 2014 06:12:16 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id pn19so1126917lab.34 for <ietf@ietf.org>; Wed, 09 Apr 2014 06:12:14 -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:content-type:content-transfer-encoding; bh=iJU4fI87/k6u7JK5qX1Jka6QLnvlN1HThAA+bompvjg=; b=EG+LWPlM+6w3VMNJb/dTAoXUwnrVSbQqnGCZtEvB3ROe9bJiLvlfjHjWc3ZMgEDHlT vhvQBDE3btg24fJsvc6b95pXvAHZLR/BUG83YbHghOb0u8EWczb0hdU44Tj2OUdrJBKh 2f5yd2xMbHPJmtQc14R1QbqaFLrp2mm7ASmWzwUuFYNrIUsNRpIMDi81BfPbKFEqjv8T k/Tmc3W7wzVjo1pwleTepyMmjeZ4QOl+bjodj4cSIaXqhYTYmp5+vLp3GxRXad2rhj9T loqFByNUeq//+sZaQ4OMEr1qIwpJ7Nqe5CtySmozvLptcSIB2PeCX9fL0X0dopjUd+R2 lYmA==
MIME-Version: 1.0
X-Received: by 10.112.134.230 with SMTP id pn6mr7156618lbb.37.1397049134440; Wed, 09 Apr 2014 06:12:14 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Wed, 9 Apr 2014 06:12:14 -0700 (PDT)
In-Reply-To: <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@99.111.97.136> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com>
Date: Wed, 9 Apr 2014 09:12:14 -0400
Message-ID: <CAMm+LwgLxR65a1nKmKpqW39_BvgMgAGwBCxAE+eEs-9bnLdv8A@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Fred Baker (fred)" <fred@cisco.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/r1MXawm1Eq22Ey3VqVYMjEVguIY
Cc: Randall Gellens <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 13:12:22 -0000

On Thu, Apr 3, 2014 at 7:40 PM, Fred Baker (fred) <fred@cisco.com> wrote:
> In view of recent issues in TurkTelecom and Indosat, it seems like the si=
mplest reason would be to ensure that data putatively obtained from the IET=
F would in fact be obtained from the IETF.
>
> From my perspective, I would support a statement to the effect that IETF =
technology should be obtainable using https or whatever else we are recomme=
nding as "secure." I'd also be in favor of asking IETF contributors to obta=
in and use PGP keys and/or DKIM encodings to sign messages. And of asking t=
hat IETF tools not reformat email in ways that corrupt data that has been s=
igned.
>
> To that end, I could imagine a requirement for some kind of roadmap. "The=
 tools that access the IETF SMTP and HTTP sites use protocols X, Y, and Z. =
After <date>, we require them to use Secure X, Secure Y, and Secure Z, and =
traffic originated by the IETF sites shall use such protocols."

This sounds like a good idea. But we currently have a big problem in
that the IETF has two email security standards, not one. And the two
sides don't talk and this has created a stalemate that has blocked
ubiquitous use of either.

Today PGP has all the mindshare for encrypted messages and S/MIME has
all the deployment. Neither is a success at anything approaching
Internet scale. And neither is going to succeed in its current form.

The only way forward is going to be to develop a new specification
that is a worthy successor to both. Fortunately this is more a matter
of optics than technical work. 95% of the work is already done.

Any solution needs to comprise a message format, a trust model and a
configuration model. And all need to be just as easy to use as regular
mail is. 'Quite easy' does not cut it any more, today a security
standard must have no impact at all or it won't be used.

If we use the deployed infrastructure as a starting point and agree
that any new scheme must support the trust models of both PGP and
S/MIME, the way forward is pretty straightforward: Take the S/MIME
message format and graft the PGP web of trust and fingerprint trust
models onto it. What I have found is that this model is actually
demonstrably more secure than either model on its own when measured
against a time based work factor model.

The reason to take the S/MIME message format is twofold. First it is
the one that is already supported in billions of email clients. This
means that if we build on the S/MIME model those clients can read
encrypted messages without changing the client at all. That is a big
plus since I have to be able to read any message I receive on my
iPhone, iPad, and either of my two laptops and three desktops (total 7
machines). But I only need to be able to respond securely on two
(though all is better of course). The other advantage to the S/MIME
format is that it is a lot more mature than PGP/MIME and has been
completely and thoroughly tested in the deployed mail infrastructure.

I won't justify my trust model argument here since everyone who is
approaching the problem in good faith should be willing to accept that
the other side has good reasons for wanting their model. But in my
podcast I show that a hybrid of both is superior. I explain why both
is better here:

http://www.youtube.com/watch?v=3DPBFnBpWkK8M

(if people are interested I have put the whole design rationale onto YouTub=
e).


I do have code as well as specs. Right now I am working on a part of
the design to make it easy to move keys from one client to another.
This is necessary because if I am trying to read an encrypted message
I need to be able to read it on any of my 7 machines. Right now that
is a hand cranked operation but there is no reason that it can't be
automatic. So I have a model that makes it easy to transfer the
private decryption key to other machines.


--=20
Website: http://hallambaker.com/


From nobody Wed Apr  9 07:12:24 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAAE81A031B; Wed,  9 Apr 2014 07:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.149
X-Spam-Level: 
X-Spam-Status: No, score=0.149 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 vhbMOTHYZzDD; Wed,  9 Apr 2014 07:12:16 -0700 (PDT)
Received: from mail-oa0-x229.google.com (mail-oa0-x229.google.com [IPv6:2607:f8b0:4003:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 8C7521A030F; Wed,  9 Apr 2014 07:12:16 -0700 (PDT)
Received: by mail-oa0-f41.google.com with SMTP id j17so2786963oag.28 for <multiple recipients>; Wed, 09 Apr 2014 07:12:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=/NIGo8WZTEy/5SnGfqjh8vN6IGks3+JRMpkOo2m6gmA=; b=k7EZ205U5NvuomikPMsQ0+ZoMZCWleQKLuwCQUcrBj8CD9HRPntQSBRdHgbKnN905Y taCP/Os9jLHAJwg61QEOgHtIOkZamfMG2owlm21uWN0RL0tWPjf1KAVPX2z4A4PDNdDX Hnez7ThQaX3mIRHPkcxxRWF+15NE9+g0YpQkgdzeitxFtmnQJHSlxleHgwX8llhW8frW QAyHYFp1jvjBQRIY4ZkZZ5zWGCtMAUHzqFNcgl5Dap18TMUNPL+dgxHmXv97Tt5wG8m9 XVGdEn6sfUkTVxKf12ufxi4/qCnvj/5XM5MXGMSshDKS9TWBM8hT44+MltngYgqOPQQg pjBQ==
X-Received: by 10.182.38.199 with SMTP id i7mr1145673obk.68.1397052735937; Wed, 09 Apr 2014 07:12:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Wed, 9 Apr 2014 07:11:55 -0700 (PDT)
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C1D15CD@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com> <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE712076C1D15CD@MX15A.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 9 Apr 2014 10:11:55 -0400
Message-ID: <CAF4+nEGDK+=sdmQqs=Qx=2jZb8KAS5h6XvAQJAtmMBF_WC8z1w@mail.gmail.com>
Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
To: "Black, David" <david.black@emc.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Z3yHr8VpbHY6vX8Cd-W_MIYp508
Cc: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 14:12:20 -0000

Hi David,

On Tue, Apr 8, 2014 at 4:58 PM, Black, David <david.black@emc.com> wrote:
> Donald,
>
> Thank you for the extensive comments on the review.  I'll summarize here
> rather than add more text inline.  I'm fine with the proposed course of
> action for anything not mentioned here:

OK. It is good sign when the amount of text being written with each
exchange starts to shrink rather than grow :-)

> [1] Absence of backwards compatibility:
>         - The Appendix A changes look good.
>         - The "limited deployment" (and presumably also "limited
>                 implementation") rationale for no backwards compatibility
>                 should be included in Section 1.1.  This merits additional
>                 text in Section 1.1

OK. We could add a few more words to the proposed new version of the
first paragraph in Section 1.1 as follows:

NEWER
   This document updates [RFC6325], the TRILL base protocol
   specification, obsoleting and replacing the description of the
   ESADI protocol (Section 4.2.5 of [RFC6325] including all
   subsections), providing more detail on ESADI, updating other ESADI
   related sections of [RFC6325], and prevailing over [RFC6325] in any
   case where they conflict. For this reason, familiarity with
   [RFC6325] is particularly assumed.  These changes include a change
   to the format of ESADI-LSPs that is not backwards compatible; this
   change is justified by the substantially increased amount of
   information that can be carried in light of the very limited, if
   any, deployment of [RFC6325] ESADI. These changes are further
   discussed in Appendix A.

> [2] Structure of draft wrt RFC 6325:
>         I think the rest of the proposed changes to Section 1.1 are reasonable:
>
>         - Appendix A does explain what's changed.  I would have liked to see
>                 more formality/precision in Section 1.1, but that's a matter of
>                 editorial taste that I'll leave to the authors.  The proposed
>                 addition of a forward reference to Appendix A will definitely
>                 help.
>         - The proposed addition of an explicit statement about expecting
>                 familiarity with RFC 6325 in Section 1.1 will also help.
>
> [3] Independence of ESADI instances: What bothered me was the absence of
> a strong mention of implementation structure - I have some new text to
> suggest to strengthen that point:
>
> OLD
>    It is an implementation decision how independent the multiple ESADI
>    instances at an RBridge are.
> NEW
>    Multiple ESADI instances may share implementation components within
>    an RBridge as long as that sharing preserves the independent operation
>    of each instance of the ESADI protocol.
>
> Then the link state database example that follows makes more sense,
> at least to me.

I'm OK with the wording you suggest.

> [4] Section 8  Authentication TLV usage discussion.
>
>> How about adding a new paragraph to Section 8, between the current
>> first and second paragraphs, incorporating the above, such as:
>>
>>    However, there may be cases where it is not necessary to
>>    authenticate ESADI PDUs despite using authenticated registration
>>    for end stations.  For example a TRILL campus with secure RBridges
>>    and inter-RBridge links configured as trunks but some end stations
>>    connected via 802.11 wireless access links might use 802.11
>>    authentication for the connection of such end stations but not
>>    necessarily authenticate ESADI PDUs. Note that if the IS-IS LSPs in
>>    a TRILL campus are authenticated, perhaps due to a concern about
>>    forged packets, the ESADI PDUs will be authenticated by default as
>>    provided in Section 6.3.
>
> These seems a bit descriptive, with most of the text describing a
> specific example.  I'm looking for some more prescriptive guidance
> about what SHOULD (or perhaps should?) be the case when the Authentication
> TLV is not used with authenticated registration.

Well, a more general statement of the criteria for such cases could be
added such as below:

   However, there may be cases where it is not necessary to
   authenticate ESADI PDUs despite using authenticated registration
   for end stations because of a significant threat of forged packets
   on end station links when that threat is not present for
   inter-RBridge trunks.  For example a TRILL campus with secure
   RBridges and inter-RBridge links configured as trunks but some end
   stations connected via 802.11 wireless access links might use
   802.11 authentication for the connection of such end stations but
   not necessarily authenticate ESADI PDUs. Note that if the IS-IS
   LSPs in a TRILL campus are authenticated, perhaps due to a concern
   about forged packets, the ESADI PDUs will be authenticated by
   default as provided in Section 6.3.

> [5] VLAN tag presence (nit)
>
>> > Last sentence on p.8:
>> >
>> > OLD
>> >    The outer VLAN tag will not be present if it was stripped by
>> >    an Ethernet port out of which the packet was sent.
>> > NEW
>> >    The outer VLAN tag will not be present for a packet on an
>> >    an Ethernet link that does not use VLAN tags.
>
> I don't think the word "stripped" is right, as it would not apply if
> the tag wasn't present in the first place, although I also agree with
> your comment that my suggested use of "link" isn't right, either.
>
> Here's another suggestion:
>
>     The outer VLAN tag will not be present if it was not included
>     by the Ethernet port that sent the packet.

I agree that "stripped" is not a very good word to use. I'm OK with
your suggested wording.

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks,
> --David
>
>> -----Original Message-----
>> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
>> Sent: Saturday, April 05, 2014 11:23 AM
>> To: Black, David
>> Cc: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu;
>> ostokes@extremenetworks.com; General Area Review Team (gen-art@ietf.org);
>> trill@ietf.org; ietf@ietf.org
>> Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
>>
>> Hi David,
>>
>> Thanks for this very thorough review. See my responses below:
>>
>> On Sat, Mar 29, 2014 at 10:23 PM, Black, David <david.black@emc.com> wrote:
>> >
>> > I am the assigned Gen-ART reviewer for this draft. For background on
>> > Gen-ART, please see the FAQ at
>> >
>> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>> >
>> > Please resolve these comments along with any other Last Call comments
>> > you may receive.
>> >
>> > Document: draft-ietf-trill-esadi-06.txt
>> > Reviewer: David L. Black
>> > Review Date: March 29, 2014
>> > IETF LC End Date: April 1, 2014
>> >
>> > Summary: This draft is on the right track, but has open issues
>> > described in the review.
>> >
>> > This draft revises the ESADI specification for TRILL from its
>> > original form in RFC 6325.
>> >
>> > Major issues:
>> >
>> > The draft changes ESADI in a non-backwards-compatible fashion from
>> > its original specification in RFC 6325, but does not explain why this
>> > is ok.  That explanation needs to be provided, and if implementations
>> > of ESADI as originally specified in RFC 6325 exist, that explanation
>> > needs to encompass coexistence and interoperability (or lack thereof)
>> > with such implementations.  That explanation probably belongs in
>> > Section 1.1, and could be expanded upon in Appendix A.
>>
>> This was a considered decision of the TRILL WG. At least since the -02
>> version in February 2013, the ESADI WG draft has had ESADI-LSP
>> provisions that were incompatible with RFC 6325 ESADI for the purpose
>> of accomodating orders of magnitude more LSP fragments. This text in
>> the draft, which originally used a somewhat ad hoc change from IS-IS
>> LSPs to accomodate additional fragments, was posted to the list
>> without objection before being incorporated. Since a standard IS-IS
>> way of doing this was later in process in the ISIS WG, the ESADI draft
>> was changed to follow this more standard way of providing for more LSP
>> fragments and a new WG Last Call done in the TRILL WG specifically on
>> this issue. See
>>
>> http://www.ietf.org/mail-archive/web/trill/current/msg06037.html
>> http://www.ietf.org/mail-archive/web/trill/current/msg06009.html
>>
>> In Appendix A (Changes to [RFC6325]), how about replacing items 2 and
>> 3 in the list as follows (includes fixing a typo in item 3):
>>
>> OLD
>>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
>>       is changed from the base IS-IS format to the Extended Level 1
>>       Circuit Scoped format in [FS-LSP].
>> NEW
>>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
>>       is changed from the base IS-IS format to the Extended Level 1
>>       Circuit Scoped format (E-L1CS) specified in [FS-LSP]. This
>>       change is not backwards compatible with [RFC6325]. It is made in
>>       light of (a) the very limited, if any, deployment of [RFC6325]
>>       ESADI, and (b) the 256 times greater information carrying
>>       capacity of the E-L1CS format compared with the base IS-IS
>>       format. It is anticipated that this greater carrying capacity
>>       will be needed, under some circumstances, to carry end station
>>       addressing information or other information that is added to
>>       ESADI in the future.
>> OLD
>>    3. Unicasting of ESADI PDUs is supported including replacing Section
>>       4.6.2.2 of [RFC6325] with the next text give in Section 4.1 of
>>       this document.
>> NEW
>>    3. Unicasting of ESADI PDUs is optionally supported including
>>       replacing Section 4.6.2.2 of [RFC6325] with the new text give in
>>       Section 4.1 of this document. This unicast support is backwards
>>       compatible because it is only used when the recipient RBridge
>>       signals its support.
>>
>> See possible replacement below for the first paragraph of Section 1.1
>> that includes a condensed version of this additional material
>> concerning backwards non-compatibility.
>>
>> > Overall, this draft is not self-contained - to a significant extent,
>> > it is written as if it were effectively a long collection of errata
>> > to the ESADI specification in RFC 6325. That makes it difficult to
>> > understand - it would be better if this draft completely obsoleted
>> > and replaced the ESADI specification in RFC 6325, describing its
>> > changes, instead of providing specific text changes to portions of
>> > the RFC 6325 text.
>>
>> All of the changes to ESADI are described in Appendix A.
>>
>> If the ESADI related material in RFC 6325 was entirely contained in
>> one contiguous area of RFC 6325, it would have been easy to write this
>> draft as simply obsoleting and replacing that area of RFC 6325.  The
>> largest such monolithic block on ESADI in RFC 6325 is Section 4.2.5
>> (The TRILL ESADI Protocol), including its two subsections ("4.2.5.1
>> TRILL ESADI Participation" and "4.2.5.2 TRILL ESADI Information"). All
>> of that is obsoleted and replaced by this draft.  However, there are
>> other non-contiguous parts of RFC 6325 necessarily affected. For
>> example, Section 4.6 of RFC 6325 describes how to handle every
>> possible type of frame that might be received; since an ESADI PDU is
>> one such type of frame, it is necessary to change Section 4.6.2.2
>> ("TRILL ESADI Frames") of RFC 6325.
>>
>> There is really no substitute for having a general familiarity with
>> RFC 6325 in understanding this document. Although I have seen IESG
>> members criticize statements such as "Familiarity with X is assumed."
>> when X is a normative reference, on the grounds that familiarity with
>> all normative references is automatically assumed, perhaps some such
>> statement is warranted in this case.
>>
>> In addressing both of your issues here, the first paragraph of Section
>> 1.1 could be changed as follows:
>>
>> OLD
>>    This document updates [RFC6325], the TRILL base specification,
>>    replacing the description of the ESADI protocol in Section 4.2.5 of
>>    [RFC6325], providing more detail, and prevailing over [RFC6325] where
>>    they conflict. The changes are summarized in Appendix A. These
>>    changes are not backwards compatible because, among other things,
>>    they change the format of ESADI-LSPs.
>> NEW
>>    This document updates [RFC6325], the TRILL base protocol
>>    specification, obsoleting and replacing the description of the
>>    ESADI protocol (Section 4.2.5 of [RFC6325] including all
>>    subsections), providing more detail on ESADI, updating other ESADI
>>    related sections of [RFC6325], and prevailing over [RFC6325] in any
>>    case where they conflict. For this reason, familiarity with
>>    [RFC6325] is particularly assumed.  These changes are not backwards
>>    compatible because they change the format of ESADI-LSPs to
>>    substantially increase the amount of information that can be
>>    carried. These changes are further discussed in Appendix A.
>>
>>
>> > Minor issues:
>> >
>> > I don't understand the discussion in section 2 of it being "an
>> > implementation decision how independent the multiple ESADI instances
>> > at an RBridge are" in light of the clear statement that "the ESADI
>> > update process operates separately for each ESADI instance."  The
>> > example given involves database structure considerations that are
>> > specific to the node implementation and do not affect the independent
>> > updates for each ESADI instance.  There may not be an actual
>> > technical problem here, but at least the first chunk of text quoted
>> > in this paragraph of the review needs to be rewritten.
>>
>> Two things motivated the text you cite in Section 2: (1) ESADI uses
>> multiple instances of the flooding process for the purpose of limiting
>> the flooding to the TRILL switches that have expressed interest in a
>> particular Data Label. RFC 6822 specifies a different type of IS-IS
>> "instance" and there is some implication in 6822 of fault and
>> performance isolation between RFC 6822 instances. Although this
>> document says its instances are not the same as RFC 6822 instances,
>> someone might still have the impression that ESADI instances are
>> necessarily to be implemented inside a TRILL switch is a highly
>> isolated manner. This text is to emphasize that the extent to which
>> the execution of different ESADI instances are isolated within a TRILL
>> switch is an implementation decision. (2) Perhaps a symptom of item 1:
>> in early discussions of ESADI, there were multiple complaints that
>> maintaining 'so many different link state databases' in a TRILL switch
>> would be an undue burden. So the text here specifically mentions that
>> the databases for all ESADI instances at a TRILL switch can be merged
>> (with an appropriate marker in each record saying which instance it
>> belongs to).
>>
>> While the IETF generally standardizes bits on the wire and not
>> internal implementation details, the above concerns lead to these few
>> sentences to dispel any false impression.  I do not really see how
>> there can be much confusion since the draft also says, as your point
>> out, "But the ESADI update process operates separately for each ESADI
>> instance and independently from the TRILL IS-IS update process.". I
>> suggest the following change:
>>
>> OLD
>>    It is an implementation decision how independent the multiple ESADI
>>    instances at an RBridge are.
>> NEW
>>    This specification does not constrain how coupled or independent
>>    the multiple ESADI instances are in their implementation internal
>>    to an RBridge.
>>
>>
>> > Also in Section 2:
>> >
>> >    ESADI does no routing so there is no reason for pseudo-nodes in ESADI
>> >    and none are created.
>> >
>> > Need to explain what a pseudo-node is before this sentence.
>>
>> I do not think this document is the right place for a detailed
>> explanation of pseudo-nodes. How about changing to the following:
>>
>>    ESADI does no routing calculations so there is no reason for
>>    pseudo-nodes in ESADI and none are created (Pseudo-nodes [IS-IS]
>>    are a construct for optimizing routing calculations.)
>>
>>
>> > p.9, Figure 2 - explain how the receiver determines whether the inner
>> > Ethernet header contains a VLAN tag or FGL.  This also applies to Figure
>> > 3 on p.10.
>>
>> I'm not sure this draft is the place for a detailed explanation but I
>> have no problem adding the already existing reference "[RFCfgl]" to
>> both figures right after where they say "VLAN or FGL Data Label (4 or
>> 8 bytes)". That referenced document [RFCfgl], which is in the RFC
>> Editor's queue, explains this.
>>
>>
>> > p.10, Section 2.1:
>> >
>> >    All transit RBridges forward ESADI packets as if they were ordinary
>> >    TRILL Data packets.
>> >
>> > Need to explain what a "transit" RBridge is.  Between this and the
>> > above pseudo-node comment, I suggest adding an overview of the
>> > TRILL protocol to the start of Section 2.
>>
>> How about just eliminating the word "transit", which I don't think is
>> necessary, and changing the sentence in question to
>>
>>      All RBridges forward ESADI packets as if they were ordinary TRILL
>>      Data packets [RFC6325].
>>
>>
>> > p.11, Section 2.1:
>> >
>> >    No "routing" computation or routing decisions ever have to be
>> >    performed by ESADI.
>> >
>> > What is a ' "routing" computation' ??  This should be rephrased to
>> > contrast to what the non-ESADI TRILL usage of IS-IS does.
>>
>> How about the following change:
>>
>> OLD
>>    No "routing" computation or routing decisions ever have to be
>>    performed by ESADI.
>> NEW
>>    No "routing" calculation (least cost path or distribution tree
>>    construction) ever has to be performed by ESADI.
>>
>>
>> > p.12, Section 2.2:
>> >
>> >    If a VLAN or FGL ID
>> >    field within an ESADI-LSP PDU does include a value, that field's
>> >    contents is ignored.
>> >
>> > This looks like it's an important requirement, so:
>> >          "is ignored" -> "MUST be ignored"
>>
>> OK.
>>
>>
>> > p.13, Section 3
>> >
>> >   "SNPA/MAC address"
>> >    is not considered in this tie breaking and there is no "Port ID".
>> >
>> > This is contrasting ESADI tie-breaking to a tie-breaking procedure
>> > that I'd guess is specified in another document; that needs to be
>> > explained, along with a reference to that document, preferably with
>> > the section number where the other tie-breaking procedure is
>> > specified.
>>
>> The other document is [rfc6327bis] which is referenced.  However, this
>> reference can be made clearer. How about
>>
>> OLD
>>    Generally speaking, the DRB election on the ESADI virtual link (see
>>    Section 2.1) operates similarly to a TRILL IS-IS broadcast link
>>    [rfc6327bis] with the following exceptions:
>> NEW
>>    Generally speaking, the DRB election on the ESADI virtual link (see
>>    Section 2.1) operates similarly to the DRB election on a TRILL
>>    IS-IS broadcast link, as described in Section 4.2.1 ("DRB Election
>>    Details") of [rfc6327bis], with the following exceptions:
>>
>>
>> > Section 6 - explain where the 1470 byte number in the third
>> > paragraph comes from.
>>
>> How about adding the following at the end of the relevant paragraph,
>> just before the Section 6.1 header:
>>
>>    (As stated in Section 4.3.1 of [RFC6325], 1470 bytes was chosen to
>>    make it extremely unlikely that a TRILL control packet, even with
>>    reasonable additional headers, tags, and/or encapsulation, would
>>    encounter MTU problems on an inter-RBridge link.)
>>
>>
>> > Section 8 - more should be said on whether/when the Authentication
>> > TLV should be used when ESADI conveys information from an
>> > authenticated registration. In particular, if this recommendation
>> > for usage of the Authentication TLV with information from an
>> > authenticated registration usage is not a "SHOULD" or "MUST", an
>> > explanation is in order.
>>
>> Consider the following: we have a network with secure trunk links
>> between trusted TRILL switches but in some cases those switches are
>> connected to end stations via 802.11 Wi-Fi links. It seems entirely
>> reasonable to use 802.11 authentication in allowing end stations to
>> connect due to the inherent accessiblity of radio links, but might not
>> be necessary to use authentication on ESADI PDUs between TRILL
>> switches.
>>
>> In any case, if there is a concern about forged packets, the IS-IS
>> LSPs in the TRILL campus should be authenticated and, in that case,
>> the ESADI PDUs will be authenticated by default as provided in Section
>> 6.3 of this draft.
>>
>> How about adding a new paragraph to Section 8, between the current
>> first and second paragraphs, incorporating the above, such as:
>>
>>    However, there may be cases where it is not necessary to
>>    authenticate ESADI PDUs despite using authenticated registration
>>    for end stations.  For example a TRILL campus with secure RBridges
>>    and inter-RBridge links configured as trunks but some end stations
>>    connected via 802.11 wireless access links might use 802.11
>>    authentication for the connection of such end staions but not
>>    necessarily authenticate ESDAI PDUs. Note that if the IS-IS LSPs in
>>    a TRILL campus are authenticated, perhaps due to a concern about
>>    forged packets, the ESADI PDUs will be authenticated by default as
>>    provided in Section 6.3.
>>
>>
>> > Nits/editorial comments:
>> >
>> > There are lots of acronyms that are not expanded on first use,
>> > defined in the terminology section, or otherwise explained, e.g.,
>> > DRB, Sz, CSNP, PSNP. It may be ok to point to terminology/acronym
>> > definitions in RFC 6325.
>>
>> I believe these are all defined/expanded in RFC 6325 but it would
>> still be a good idea to expand them on first use in this document.
>>
>>
>> > Last sentence on p.8:
>> >
>> > OLD
>> >    The outer VLAN tag will not be present if it was stripped by
>> >    an Ethernet port out of which the packet was sent.
>> > NEW
>> >    The outer VLAN tag will not be present for a packet on an
>> >    an Ethernet link that does not use VLAN tags.
>>
>> Well, whether or not any particular Ethernet frame carrying a TRILL
>> Data packet is VLAN tagged or not depends on whether the port sending
>> that frame is configured to send it tagged or untagged. There is no
>> requirement or enforcement mechanism that all the ports on that
>> Ethernet link be identically configured in this regard. So I do not
>> consider it to be a property of the link.
>>
>>
>> Also, Appendix A item 1: replces -> replaces
>>
>> Thanks,
>> Donald
>> =============================
>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>  155 Beaver Street, Milford, MA 01757 USA
>>  d3e3e3@gmail.com
>>
>> > idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
>> > RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
>> > this is not a problem.
>> >
>> > idnits also warned about possible pre-RFC5378 (2008) content.  This
>> > is probably not a problem, but please check with your AD.
>> >
>> > Thanks,
>> > --David
>> > ----------------------------------------------------
>> > David L. Black, Distinguished Engineer
>> > EMC Corporation, 176 South St., Hopkinton, MA  01748
>> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
>> > david.black@emc.com        Mobile: +1 (978) 394-7754
>> > ----------------------------------------------------
>


From nobody Wed Apr  9 07:50:06 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 189751A0381; Wed,  9 Apr 2014 07:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 h4AEyxcnSWVG; Wed,  9 Apr 2014 07:49:08 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 819751A035C; Wed,  9 Apr 2014 07:49:04 -0700 (PDT)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s39Emuv0014241 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 9 Apr 2014 10:48:56 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s39Emuv0014241
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397054937; bh=Zd/PWnSobXXG+1rB6Sv7YqTLvvI=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=qm7xeSsqkmOp0Lpu588vlTX22tWwcSaNltBoWU+cwaAViO6gWk+y/Q2Zsb+ms4j/p j6Ou7+v4RVWRnNJJ2s5zT3WgN2T3zls28WHeLynLRLHHXgFsy74Bs+pMBL1aDUd9wf m4EdcjbrueorOteC5cfEOCSeaA6c1ymGItMKz+EU=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s39Emuv0014241
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd04.lss.emc.com (RSA Interceptor); Wed, 9 Apr 2014 07:48:33 -0700
Received: from mxhub34.corp.emc.com (mxhub34.corp.emc.com [10.254.93.82]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s39EmWx0005663 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 9 Apr 2014 10:48:32 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub34.corp.emc.com ([::1]) with mapi; Wed, 9 Apr 2014 10:48:31 -0400
From: "Black, David" <david.black@emc.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 9 Apr 2014 10:48:31 -0400
Subject: RE: Gen-ART review of draft-ietf-trill-esadi-06.txt
Thread-Topic: Gen-ART review of draft-ietf-trill-esadi-06.txt
Thread-Index: Ac9T/bw5MYNmhqmoQ322fGIxvjgcIgABHitQ
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C1D16FC@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C0ADDF7@MX15A.corp.emc.com> <CAF4+nEEL1LUxBEaGyUxEHNWb=fMgu2zVAuHqiSf64d0ZW=w3ng@mail.gmail.com> <8D3D17ACE214DC429325B2B98F3AE712076C1D15CD@MX15A.corp.emc.com> <CAF4+nEGDK+=sdmQqs=Qx=2jZb8KAS5h6XvAQJAtmMBF_WC8z1w@mail.gmail.com>
In-Reply-To: <CAF4+nEGDK+=sdmQqs=Qx=2jZb8KAS5h6XvAQJAtmMBF_WC8z1w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: DLM_1, public
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mkB2OL3dpxn-mvOm042PGXvuAGY
Cc: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "trill@ietf.org" <trill@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 14:49:24 -0000

Hi Donald,

I think we're basically done here.

For [4], I would like to see stronger requirements in the security text, bu=
t
I can accept what's proposed below as an improvement.  Please ensure that a
good security reviewer (e.g., a sec-dir reviewer) takes a look at that new
text as well as the rest of the security considerations.

Everything else below is fine with me.

Thanks,
--David

> -----Original Message-----
> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> Sent: Wednesday, April 09, 2014 10:12 AM
> To: Black, David
> Cc: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu;
> ostokes@extremenetworks.com; General Area Review Team (gen-art@ietf.org);
> trill@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
>
> Hi David,
>
> On Tue, Apr 8, 2014 at 4:58 PM, Black, David <david.black@emc.com> wrote:
> > Donald,
> >
> > Thank you for the extensive comments on the review.  I'll summarize her=
e
> > rather than add more text inline.  I'm fine with the proposed course of
> > action for anything not mentioned here:
>
> OK. It is good sign when the amount of text being written with each
> exchange starts to shrink rather than grow :-)
>
> > [1] Absence of backwards compatibility:
> >         - The Appendix A changes look good.
> >         - The "limited deployment" (and presumably also "limited
> >                 implementation") rationale for no backwards compatibili=
ty
> >                 should be included in Section 1.1.  This merits additio=
nal
> >                 text in Section 1.1
>
> OK. We could add a few more words to the proposed new version of the
> first paragraph in Section 1.1 as follows:
>
> NEWER
>    This document updates [RFC6325], the TRILL base protocol
>    specification, obsoleting and replacing the description of the
>    ESADI protocol (Section 4.2.5 of [RFC6325] including all
>    subsections), providing more detail on ESADI, updating other ESADI
>    related sections of [RFC6325], and prevailing over [RFC6325] in any
>    case where they conflict. For this reason, familiarity with
>    [RFC6325] is particularly assumed.  These changes include a change
>    to the format of ESADI-LSPs that is not backwards compatible; this
>    change is justified by the substantially increased amount of
>    information that can be carried in light of the very limited, if
>    any, deployment of [RFC6325] ESADI. These changes are further
>    discussed in Appendix A.
>
> > [2] Structure of draft wrt RFC 6325:
> >         I think the rest of the proposed changes to Section 1.1 are
> reasonable:
> >
> >         - Appendix A does explain what's changed.  I would have liked t=
o see
> >                 more formality/precision in Section 1.1, but that's a m=
atter
> of
> >                 editorial taste that I'll leave to the authors.  The
> proposed
> >                 addition of a forward reference to Appendix A will
> definitely
> >                 help.
> >         - The proposed addition of an explicit statement about expectin=
g
> >                 familiarity with RFC 6325 in Section 1.1 will also help=
.
> >
> > [3] Independence of ESADI instances: What bothered me was the absence o=
f
> > a strong mention of implementation structure - I have some new text to
> > suggest to strengthen that point:
> >
> > OLD
> >    It is an implementation decision how independent the multiple ESADI
> >    instances at an RBridge are.
> > NEW
> >    Multiple ESADI instances may share implementation components within
> >    an RBridge as long as that sharing preserves the independent operati=
on
> >    of each instance of the ESADI protocol.
> >
> > Then the link state database example that follows makes more sense,
> > at least to me.
>
> I'm OK with the wording you suggest.
>
> > [4] Section 8  Authentication TLV usage discussion.
> >
> >> How about adding a new paragraph to Section 8, between the current
> >> first and second paragraphs, incorporating the above, such as:
> >>
> >>    However, there may be cases where it is not necessary to
> >>    authenticate ESADI PDUs despite using authenticated registration
> >>    for end stations.  For example a TRILL campus with secure RBridges
> >>    and inter-RBridge links configured as trunks but some end stations
> >>    connected via 802.11 wireless access links might use 802.11
> >>    authentication for the connection of such end stations but not
> >>    necessarily authenticate ESADI PDUs. Note that if the IS-IS LSPs in
> >>    a TRILL campus are authenticated, perhaps due to a concern about
> >>    forged packets, the ESADI PDUs will be authenticated by default as
> >>    provided in Section 6.3.
> >
> > These seems a bit descriptive, with most of the text describing a
> > specific example.  I'm looking for some more prescriptive guidance
> > about what SHOULD (or perhaps should?) be the case when the Authenticat=
ion
> > TLV is not used with authenticated registration.
>
> Well, a more general statement of the criteria for such cases could be
> added such as below:
>
>    However, there may be cases where it is not necessary to
>    authenticate ESADI PDUs despite using authenticated registration
>    for end stations because of a significant threat of forged packets
>    on end station links when that threat is not present for
>    inter-RBridge trunks.  For example a TRILL campus with secure
>    RBridges and inter-RBridge links configured as trunks but some end
>    stations connected via 802.11 wireless access links might use
>    802.11 authentication for the connection of such end stations but
>    not necessarily authenticate ESADI PDUs. Note that if the IS-IS
>    LSPs in a TRILL campus are authenticated, perhaps due to a concern
>    about forged packets, the ESADI PDUs will be authenticated by
>    default as provided in Section 6.3.
>
> > [5] VLAN tag presence (nit)
> >
> >> > Last sentence on p.8:
> >> >
> >> > OLD
> >> >    The outer VLAN tag will not be present if it was stripped by
> >> >    an Ethernet port out of which the packet was sent.
> >> > NEW
> >> >    The outer VLAN tag will not be present for a packet on an
> >> >    an Ethernet link that does not use VLAN tags.
> >
> > I don't think the word "stripped" is right, as it would not apply if
> > the tag wasn't present in the first place, although I also agree with
> > your comment that my suggested use of "link" isn't right, either.
> >
> > Here's another suggestion:
> >
> >     The outer VLAN tag will not be present if it was not included
> >     by the Ethernet port that sent the packet.
>
> I agree that "stripped" is not a very good word to use. I'm OK with
> your suggested wording.
>
> Thanks,
> Donald
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
> > Thanks,
> > --David
> >
> >> -----Original Message-----
> >> From: Donald Eastlake [mailto:d3e3e3@gmail.com]
> >> Sent: Saturday, April 05, 2014 11:23 AM
> >> To: Black, David
> >> Cc: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu=
;
> >> ostokes@extremenetworks.com; General Area Review Team (gen-art@ietf.or=
g);
> >> trill@ietf.org; ietf@ietf.org
> >> Subject: Re: Gen-ART review of draft-ietf-trill-esadi-06.txt
> >>
> >> Hi David,
> >>
> >> Thanks for this very thorough review. See my responses below:
> >>
> >> On Sat, Mar 29, 2014 at 10:23 PM, Black, David <david.black@emc.com> w=
rote:
> >> >
> >> > I am the assigned Gen-ART reviewer for this draft. For background on
> >> > Gen-ART, please see the FAQ at
> >> >
> >> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >> >
> >> > Please resolve these comments along with any other Last Call comment=
s
> >> > you may receive.
> >> >
> >> > Document: draft-ietf-trill-esadi-06.txt
> >> > Reviewer: David L. Black
> >> > Review Date: March 29, 2014
> >> > IETF LC End Date: April 1, 2014
> >> >
> >> > Summary: This draft is on the right track, but has open issues
> >> > described in the review.
> >> >
> >> > This draft revises the ESADI specification for TRILL from its
> >> > original form in RFC 6325.
> >> >
> >> > Major issues:
> >> >
> >> > The draft changes ESADI in a non-backwards-compatible fashion from
> >> > its original specification in RFC 6325, but does not explain why thi=
s
> >> > is ok.  That explanation needs to be provided, and if implementation=
s
> >> > of ESADI as originally specified in RFC 6325 exist, that explanation
> >> > needs to encompass coexistence and interoperability (or lack thereof=
)
> >> > with such implementations.  That explanation probably belongs in
> >> > Section 1.1, and could be expanded upon in Appendix A.
> >>
> >> This was a considered decision of the TRILL WG. At least since the -02
> >> version in February 2013, the ESADI WG draft has had ESADI-LSP
> >> provisions that were incompatible with RFC 6325 ESADI for the purpose
> >> of accomodating orders of magnitude more LSP fragments. This text in
> >> the draft, which originally used a somewhat ad hoc change from IS-IS
> >> LSPs to accomodate additional fragments, was posted to the list
> >> without objection before being incorporated. Since a standard IS-IS
> >> way of doing this was later in process in the ISIS WG, the ESADI draft
> >> was changed to follow this more standard way of providing for more LSP
> >> fragments and a new WG Last Call done in the TRILL WG specifically on
> >> this issue. See
> >>
> >> http://www.ietf.org/mail-archive/web/trill/current/msg06037.html
> >> http://www.ietf.org/mail-archive/web/trill/current/msg06009.html
> >>
> >> In Appendix A (Changes to [RFC6325]), how about replacing items 2 and
> >> 3 in the list as follows (includes fixing a typo in item 3):
> >>
> >> OLD
> >>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
> >>       is changed from the base IS-IS format to the Extended Level 1
> >>       Circuit Scoped format in [FS-LSP].
> >> NEW
> >>    2. The format of ESADI-LSP, ESADI-CSNP, and ESADI-PSNP PDU payloads
> >>       is changed from the base IS-IS format to the Extended Level 1
> >>       Circuit Scoped format (E-L1CS) specified in [FS-LSP]. This
> >>       change is not backwards compatible with [RFC6325]. It is made in
> >>       light of (a) the very limited, if any, deployment of [RFC6325]
> >>       ESADI, and (b) the 256 times greater information carrying
> >>       capacity of the E-L1CS format compared with the base IS-IS
> >>       format. It is anticipated that this greater carrying capacity
> >>       will be needed, under some circumstances, to carry end station
> >>       addressing information or other information that is added to
> >>       ESADI in the future.
> >> OLD
> >>    3. Unicasting of ESADI PDUs is supported including replacing Sectio=
n
> >>       4.6.2.2 of [RFC6325] with the next text give in Section 4.1 of
> >>       this document.
> >> NEW
> >>    3. Unicasting of ESADI PDUs is optionally supported including
> >>       replacing Section 4.6.2.2 of [RFC6325] with the new text give in
> >>       Section 4.1 of this document. This unicast support is backwards
> >>       compatible because it is only used when the recipient RBridge
> >>       signals its support.
> >>
> >> See possible replacement below for the first paragraph of Section 1.1
> >> that includes a condensed version of this additional material
> >> concerning backwards non-compatibility.
> >>
> >> > Overall, this draft is not self-contained - to a significant extent,
> >> > it is written as if it were effectively a long collection of errata
> >> > to the ESADI specification in RFC 6325. That makes it difficult to
> >> > understand - it would be better if this draft completely obsoleted
> >> > and replaced the ESADI specification in RFC 6325, describing its
> >> > changes, instead of providing specific text changes to portions of
> >> > the RFC 6325 text.
> >>
> >> All of the changes to ESADI are described in Appendix A.
> >>
> >> If the ESADI related material in RFC 6325 was entirely contained in
> >> one contiguous area of RFC 6325, it would have been easy to write this
> >> draft as simply obsoleting and replacing that area of RFC 6325.  The
> >> largest such monolithic block on ESADI in RFC 6325 is Section 4.2.5
> >> (The TRILL ESADI Protocol), including its two subsections ("4.2.5.1
> >> TRILL ESADI Participation" and "4.2.5.2 TRILL ESADI Information"). All
> >> of that is obsoleted and replaced by this draft.  However, there are
> >> other non-contiguous parts of RFC 6325 necessarily affected. For
> >> example, Section 4.6 of RFC 6325 describes how to handle every
> >> possible type of frame that might be received; since an ESADI PDU is
> >> one such type of frame, it is necessary to change Section 4.6.2.2
> >> ("TRILL ESADI Frames") of RFC 6325.
> >>
> >> There is really no substitute for having a general familiarity with
> >> RFC 6325 in understanding this document. Although I have seen IESG
> >> members criticize statements such as "Familiarity with X is assumed."
> >> when X is a normative reference, on the grounds that familiarity with
> >> all normative references is automatically assumed, perhaps some such
> >> statement is warranted in this case.
> >>
> >> In addressing both of your issues here, the first paragraph of Section
> >> 1.1 could be changed as follows:
> >>
> >> OLD
> >>    This document updates [RFC6325], the TRILL base specification,
> >>    replacing the description of the ESADI protocol in Section 4.2.5 of
> >>    [RFC6325], providing more detail, and prevailing over [RFC6325] whe=
re
> >>    they conflict. The changes are summarized in Appendix A. These
> >>    changes are not backwards compatible because, among other things,
> >>    they change the format of ESADI-LSPs.
> >> NEW
> >>    This document updates [RFC6325], the TRILL base protocol
> >>    specification, obsoleting and replacing the description of the
> >>    ESADI protocol (Section 4.2.5 of [RFC6325] including all
> >>    subsections), providing more detail on ESADI, updating other ESADI
> >>    related sections of [RFC6325], and prevailing over [RFC6325] in any
> >>    case where they conflict. For this reason, familiarity with
> >>    [RFC6325] is particularly assumed.  These changes are not backwards
> >>    compatible because they change the format of ESADI-LSPs to
> >>    substantially increase the amount of information that can be
> >>    carried. These changes are further discussed in Appendix A.
> >>
> >>
> >> > Minor issues:
> >> >
> >> > I don't understand the discussion in section 2 of it being "an
> >> > implementation decision how independent the multiple ESADI instances
> >> > at an RBridge are" in light of the clear statement that "the ESADI
> >> > update process operates separately for each ESADI instance."  The
> >> > example given involves database structure considerations that are
> >> > specific to the node implementation and do not affect the independen=
t
> >> > updates for each ESADI instance.  There may not be an actual
> >> > technical problem here, but at least the first chunk of text quoted
> >> > in this paragraph of the review needs to be rewritten.
> >>
> >> Two things motivated the text you cite in Section 2: (1) ESADI uses
> >> multiple instances of the flooding process for the purpose of limiting
> >> the flooding to the TRILL switches that have expressed interest in a
> >> particular Data Label. RFC 6822 specifies a different type of IS-IS
> >> "instance" and there is some implication in 6822 of fault and
> >> performance isolation between RFC 6822 instances. Although this
> >> document says its instances are not the same as RFC 6822 instances,
> >> someone might still have the impression that ESADI instances are
> >> necessarily to be implemented inside a TRILL switch is a highly
> >> isolated manner. This text is to emphasize that the extent to which
> >> the execution of different ESADI instances are isolated within a TRILL
> >> switch is an implementation decision. (2) Perhaps a symptom of item 1:
> >> in early discussions of ESADI, there were multiple complaints that
> >> maintaining 'so many different link state databases' in a TRILL switch
> >> would be an undue burden. So the text here specifically mentions that
> >> the databases for all ESADI instances at a TRILL switch can be merged
> >> (with an appropriate marker in each record saying which instance it
> >> belongs to).
> >>
> >> While the IETF generally standardizes bits on the wire and not
> >> internal implementation details, the above concerns lead to these few
> >> sentences to dispel any false impression.  I do not really see how
> >> there can be much confusion since the draft also says, as your point
> >> out, "But the ESADI update process operates separately for each ESADI
> >> instance and independently from the TRILL IS-IS update process.". I
> >> suggest the following change:
> >>
> >> OLD
> >>    It is an implementation decision how independent the multiple ESADI
> >>    instances at an RBridge are.
> >> NEW
> >>    This specification does not constrain how coupled or independent
> >>    the multiple ESADI instances are in their implementation internal
> >>    to an RBridge.
> >>
> >>
> >> > Also in Section 2:
> >> >
> >> >    ESADI does no routing so there is no reason for pseudo-nodes in E=
SADI
> >> >    and none are created.
> >> >
> >> > Need to explain what a pseudo-node is before this sentence.
> >>
> >> I do not think this document is the right place for a detailed
> >> explanation of pseudo-nodes. How about changing to the following:
> >>
> >>    ESADI does no routing calculations so there is no reason for
> >>    pseudo-nodes in ESADI and none are created (Pseudo-nodes [IS-IS]
> >>    are a construct for optimizing routing calculations.)
> >>
> >>
> >> > p.9, Figure 2 - explain how the receiver determines whether the inne=
r
> >> > Ethernet header contains a VLAN tag or FGL.  This also applies to Fi=
gure
> >> > 3 on p.10.
> >>
> >> I'm not sure this draft is the place for a detailed explanation but I
> >> have no problem adding the already existing reference "[RFCfgl]" to
> >> both figures right after where they say "VLAN or FGL Data Label (4 or
> >> 8 bytes)". That referenced document [RFCfgl], which is in the RFC
> >> Editor's queue, explains this.
> >>
> >>
> >> > p.10, Section 2.1:
> >> >
> >> >    All transit RBridges forward ESADI packets as if they were ordina=
ry
> >> >    TRILL Data packets.
> >> >
> >> > Need to explain what a "transit" RBridge is.  Between this and the
> >> > above pseudo-node comment, I suggest adding an overview of the
> >> > TRILL protocol to the start of Section 2.
> >>
> >> How about just eliminating the word "transit", which I don't think is
> >> necessary, and changing the sentence in question to
> >>
> >>      All RBridges forward ESADI packets as if they were ordinary TRILL
> >>      Data packets [RFC6325].
> >>
> >>
> >> > p.11, Section 2.1:
> >> >
> >> >    No "routing" computation or routing decisions ever have to be
> >> >    performed by ESADI.
> >> >
> >> > What is a ' "routing" computation' ??  This should be rephrased to
> >> > contrast to what the non-ESADI TRILL usage of IS-IS does.
> >>
> >> How about the following change:
> >>
> >> OLD
> >>    No "routing" computation or routing decisions ever have to be
> >>    performed by ESADI.
> >> NEW
> >>    No "routing" calculation (least cost path or distribution tree
> >>    construction) ever has to be performed by ESADI.
> >>
> >>
> >> > p.12, Section 2.2:
> >> >
> >> >    If a VLAN or FGL ID
> >> >    field within an ESADI-LSP PDU does include a value, that field's
> >> >    contents is ignored.
> >> >
> >> > This looks like it's an important requirement, so:
> >> >          "is ignored" -> "MUST be ignored"
> >>
> >> OK.
> >>
> >>
> >> > p.13, Section 3
> >> >
> >> >   "SNPA/MAC address"
> >> >    is not considered in this tie breaking and there is no "Port ID".
> >> >
> >> > This is contrasting ESADI tie-breaking to a tie-breaking procedure
> >> > that I'd guess is specified in another document; that needs to be
> >> > explained, along with a reference to that document, preferably with
> >> > the section number where the other tie-breaking procedure is
> >> > specified.
> >>
> >> The other document is [rfc6327bis] which is referenced.  However, this
> >> reference can be made clearer. How about
> >>
> >> OLD
> >>    Generally speaking, the DRB election on the ESADI virtual link (see
> >>    Section 2.1) operates similarly to a TRILL IS-IS broadcast link
> >>    [rfc6327bis] with the following exceptions:
> >> NEW
> >>    Generally speaking, the DRB election on the ESADI virtual link (see
> >>    Section 2.1) operates similarly to the DRB election on a TRILL
> >>    IS-IS broadcast link, as described in Section 4.2.1 ("DRB Election
> >>    Details") of [rfc6327bis], with the following exceptions:
> >>
> >>
> >> > Section 6 - explain where the 1470 byte number in the third
> >> > paragraph comes from.
> >>
> >> How about adding the following at the end of the relevant paragraph,
> >> just before the Section 6.1 header:
> >>
> >>    (As stated in Section 4.3.1 of [RFC6325], 1470 bytes was chosen to
> >>    make it extremely unlikely that a TRILL control packet, even with
> >>    reasonable additional headers, tags, and/or encapsulation, would
> >>    encounter MTU problems on an inter-RBridge link.)
> >>
> >>
> >> > Section 8 - more should be said on whether/when the Authentication
> >> > TLV should be used when ESADI conveys information from an
> >> > authenticated registration. In particular, if this recommendation
> >> > for usage of the Authentication TLV with information from an
> >> > authenticated registration usage is not a "SHOULD" or "MUST", an
> >> > explanation is in order.
> >>
> >> Consider the following: we have a network with secure trunk links
> >> between trusted TRILL switches but in some cases those switches are
> >> connected to end stations via 802.11 Wi-Fi links. It seems entirely
> >> reasonable to use 802.11 authentication in allowing end stations to
> >> connect due to the inherent accessiblity of radio links, but might not
> >> be necessary to use authentication on ESADI PDUs between TRILL
> >> switches.
> >>
> >> In any case, if there is a concern about forged packets, the IS-IS
> >> LSPs in the TRILL campus should be authenticated and, in that case,
> >> the ESADI PDUs will be authenticated by default as provided in Section
> >> 6.3 of this draft.
> >>
> >> How about adding a new paragraph to Section 8, between the current
> >> first and second paragraphs, incorporating the above, such as:
> >>
> >>    However, there may be cases where it is not necessary to
> >>    authenticate ESADI PDUs despite using authenticated registration
> >>    for end stations.  For example a TRILL campus with secure RBridges
> >>    and inter-RBridge links configured as trunks but some end stations
> >>    connected via 802.11 wireless access links might use 802.11
> >>    authentication for the connection of such end staions but not
> >>    necessarily authenticate ESDAI PDUs. Note that if the IS-IS LSPs in
> >>    a TRILL campus are authenticated, perhaps due to a concern about
> >>    forged packets, the ESADI PDUs will be authenticated by default as
> >>    provided in Section 6.3.
> >>
> >>
> >> > Nits/editorial comments:
> >> >
> >> > There are lots of acronyms that are not expanded on first use,
> >> > defined in the terminology section, or otherwise explained, e.g.,
> >> > DRB, Sz, CSNP, PSNP. It may be ok to point to terminology/acronym
> >> > definitions in RFC 6325.
> >>
> >> I believe these are all defined/expanded in RFC 6325 but it would
> >> still be a good idea to expand them on first use in this document.
> >>
> >>
> >> > Last sentence on p.8:
> >> >
> >> > OLD
> >> >    The outer VLAN tag will not be present if it was stripped by
> >> >    an Ethernet port out of which the packet was sent.
> >> > NEW
> >> >    The outer VLAN tag will not be present for a packet on an
> >> >    an Ethernet link that does not use VLAN tags.
> >>
> >> Well, whether or not any particular Ethernet frame carrying a TRILL
> >> Data packet is VLAN tagged or not depends on whether the port sending
> >> that frame is configured to send it tagged or untagged. There is no
> >> requirement or enforcement mechanism that all the ports on that
> >> Ethernet link be identically configured in this regard. So I do not
> >> consider it to be a property of the link.
> >>
> >>
> >> Also, Appendix A item 1: replces -> replaces
> >>
> >> Thanks,
> >> Donald
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D
> >>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
> >>  155 Beaver Street, Milford, MA 01757 USA
> >>  d3e3e3@gmail.com
> >>
> >> > idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
> >> > RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
> >> > this is not a problem.
> >> >
> >> > idnits also warned about possible pre-RFC5378 (2008) content.  This
> >> > is probably not a problem, but please check with your AD.
> >> >
> >> > Thanks,
> >> > --David
> >> > ----------------------------------------------------
> >> > David L. Black, Distinguished Engineer
> >> > EMC Corporation, 176 South St., Hopkinton, MA  01748
> >> > +1 (508) 293-7953             FAX: +1 (508) 293-7786
> >> > david.black@emc.com        Mobile: +1 (978) 394-7754
> >> > ----------------------------------------------------
> >


From nobody Wed Apr  9 08:04:04 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D47D1A0285 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 05:57:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.819
X-Spam-Level: *
X-Spam-Status: No, score=1.819 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 Ntnagrsx10sg for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 05:56:59 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 974D01A021F for <ietf@ietf.org>; Wed,  9 Apr 2014 05:56:59 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id D96A8CC080; Wed,  9 Apr 2014 08:56:58 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tVJchK4YJEiD; Wed,  9 Apr 2014 08:56:54 -0400 (EDT)
Received: from Miles-Fidelmans-MacBook-Pro.local (static-173-56-67-50.nycmny.fios.verizon.net [173.56.67.50]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 872BBCC07F; Wed,  9 Apr 2014 08:56:54 -0400 (EDT)
Message-ID: <53454396.4040109@meetinghouse.net>
Date: Wed, 09 Apr 2014 08:56:54 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
Subject: Re: [Internetgovtech] IANA changes process
References: <D272A88D-B935-4BAE-A649-13815E5896D3@ietf.org> <14E4E6DE-CACF-4057-9308-49BC980A5197@ietf.org> <534540DD.20107@cisco.com>
In-Reply-To: <534540DD.20107@cisco.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JnJvCAB8QYwS1nZGfq-b7pT-FwQ
X-Mailman-Approved-At: Wed, 09 Apr 2014 08:03:59 -0700
Cc: "internetgovtech@iab.org" <internetgovtech@iab.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 12:57:03 -0000

It's probably worth mentioning that IANA essentially performs the 
"registration authority" function that's common to lots of standards 
processes.  And it's typically the standards maker that designates the 
registration authority (or is the registration authority).  As has been 
discussed elsewhere, using the example of credit cards, ISO sets the 
numbering standards, and ANSI acts as registration authority for the 
issuer database (formerly it was the American Bankers Association).  For 
ethernet MAC addresses, IEEE plays both roles.

For IANA functions, IETF is the standards body - and the logical body to 
designate and oversee the registration authority - so.... it's certainly 
a good idea for the IETF community to weigh in.

Miles Fidelman

Eliot Lear wrote:
> Hi Jari,
>
> While I appreciate your measured tones, you may have understated the
> situation in this case.  Two things are being proposed that require
> careful consideration.  The first is the structure and process of how a
> proposal to evolve the IANA functions.  The second is a statement about
> what will be evolved and as important what will not change â€“ perhaps for
> a very long time.  Our input is very important into the process, and it
> will be important that we provide a comprehensive response in the coming
> weeks.  This is the IETF community's chance to provide input into that
> response.  On these two issues, there will not be another opportunity.
>
> Eliot
>
>
>
>
> In this case, people may not agree on
>
> On 4/9/14, 4:20 PM, IETF Chair wrote:
>> A draft proposal for IANA transition process has been published by ICANN, based on early input gathered during their meeting two weeks ago.
>>
>> http://www.icann.org/en/about/agreements/iana/transition/draft-proposal-08apr14-en.htm
>>
>> We would be interested in opinions about this process from an IETF perspective. Please comment on the internetgovtech list.
>>
>> Jari Arkko, IETF Chair
>>
>>
>>
> _______________________________________________
> Internetgovtech mailing list
> Internetgovtech@iab.org
> https://www.iab.org/mailman/listinfo/internetgovtech


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Wed Apr  9 08:06:29 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6A471A0392 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 08:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable
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 Bhk1UsVrm2at for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 08:06:21 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8521A0391 for <ietf@ietf.org>; Wed,  9 Apr 2014 08:06:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id D9E481E41DE; Wed,  9 Apr 2014 08:06:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id okPg9MpBkdOp; Wed,  9 Apr 2014 08:06:16 -0700 (PDT)
Received: from [10.156.44.192] (unknown [192.165.183.201]) by c8a.amsl.com (Postfix) with ESMTPSA id 164F21E40EF; Wed,  9 Apr 2014 08:06:15 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [Internetgovtech] IANA changes process
From: IETF Chair <chair@ietf.org>
In-Reply-To: <534540DD.20107@cisco.com>
Date: Wed, 9 Apr 2014 17:06:17 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D4407F3D-D963-4E5D-AB18-B3A4AAC088C8@ietf.org>
References: <D272A88D-B935-4BAE-A649-13815E5896D3@ietf.org> <14E4E6DE-CACF-4057-9308-49BC980A5197@ietf.org> <534540DD.20107@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PDkx3j92Q7Vz4Rs9zkNH-6ecfsM
Cc: "internetgovtech@iab.org" <internetgovtech@iab.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 15:06:25 -0000

Eliot,

> While I appreciate your measured tones, you may have understated the
> situation in this case.  Two things are being proposed that require
> careful consideration.=20

I am sorry if I was unclear. This is indeed very important, and, yes, as =
you point out there are multiple aspects, both the process and the =
scope.=20

The process is here: =
http://www.icann.org/en/about/agreements/iana/transition/draft-proposal-08=
apr14-en.htm
And the scope here: =
http://www.icann.org/en/about/agreements/iana/iana-transition-scoping-08ap=
r14-en.pdf

I expect the IAB and its IANA program to lead the preparation of =
response(s), but nevertheless, community discussion of the topic would =
be very helpful as well.

Jari


From nobody Wed Apr  9 08:49:22 2014
Return-Path: <jnc@mercury.lcs.mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48F691A0390 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 08:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.772
X-Spam-Level: 
X-Spam-Status: No, score=-1.772 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 xPLNGqUVxLu5 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 08:49:20 -0700 (PDT)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id E29C81A032F for <ietf@ietf.org>; Wed,  9 Apr 2014 08:49:19 -0700 (PDT)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 11E6118C106; Wed,  9 Apr 2014 11:49:19 -0400 (EDT)
To: ietf@ietf.org
Subject: Re: Security for various IETF services
Message-Id: <20140409154919.11E6118C106@mercury.lcs.mit.edu>
Date: Wed,  9 Apr 2014 11:49:19 -0400 (EDT)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/t6hQakLcdmVycgn6Lcu4xcxRuuY
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 15:49:21 -0000

    > From: Phillip Hallam-Baker <hallam@gmail.com>

    > a security standard must have no impact at all or it won't be used.

While I agree with the conclusion part ("or .. used"), isn't the first part
sort of internally contradictory? Adding security almost always has some
cost, in that people have to set up the security, etc. (I'm thinking in very
broad terms here - e.g one has to lock one's car/house, enter a security code
to use an ATM card, etc, etc.) OK, so HTTPS has basically zero impact on the
average user - is the same level of user inattention really possible with
email security?

But I'm just being nitpicky about a background statement; on your main
point:

    > we currently have a big problem in that the IETF has two email security
    > standards, not one. ... Neither is a success at anything approaching
    > Internet scale.
    > ...
    > the way forward is pretty straightforward: Take the S/MIME message
    > format and graft the PGP web of trust and fingerprint trust models onto
    > it. 

I agree wholly with your prefatory observation, and like your suggested
solution.

	Noel


From nobody Wed Apr  9 09:37:30 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C95A41A02F7 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 09:37:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 uds7gYotXKT9 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 09:37:22 -0700 (PDT)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id 5452A1A0380 for <ietf@ietf.org>; Wed,  9 Apr 2014 09:37:22 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id c11so1372292lbj.12 for <ietf@ietf.org>; Wed, 09 Apr 2014 09:37:20 -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:content-type; bh=dz6u4Ltj5JiQRYse3gPc5qy8a8RlaGSH6Yu1T6hYKZM=; b=nRE9WyOxlTnq+BWuK69f26NNpiPD54MOSEIRJAeV+sw6tr+81gI8wZ0i06fMstdiVg znt61ya2NSo5v2svYBW8UAhxGmcX/Rwa73ebznXhuDgt98+/RupSlXi0ehyrDOzvmaWT osDOBS2o3LgY9mt9/DAOwhTggZcPRww5Y09lp/w+Bq1W57q0ASF4qIRnm5R7d5W9ovDY MuxPFYoQ8XxuaRR3QuYgqdacEeyCJCMBl4ik+6ZaB8gzSOGFbTyYrIG9DJpEwkPFAeKr mgqEVnhKXJyFvPsPj2ZJKHKBYLILsaw51yx4pJ5ayhkwh8eW4YgHZ8z5zVahv4gLfMS9 asRA==
MIME-Version: 1.0
X-Received: by 10.152.19.65 with SMTP id c1mr2996077lae.35.1397061440853; Wed, 09 Apr 2014 09:37:20 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Wed, 9 Apr 2014 09:37:20 -0700 (PDT)
In-Reply-To: <20140409154919.11E6118C106@mercury.lcs.mit.edu>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu>
Date: Wed, 9 Apr 2014 12:37:20 -0400
Message-ID: <CAMm+LwhVm68yvbi4RYqAbQvbQs_7vZ8JF3e38UYH_RCoEv0sVg@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NOdamdWNmxHWPMSQmUsEDlGnyk4
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 16:37:28 -0000

On Wed, Apr 9, 2014 at 11:49 AM, Noel Chiappa <jnc@mercury.lcs.mit.edu> wrote:
>     > From: Phillip Hallam-Baker <hallam@gmail.com>
>
>     > a security standard must have no impact at all or it won't be used.
>
> While I agree with the conclusion part ("or .. used"), isn't the first part
> sort of internally contradictory? Adding security almost always has some
> cost, in that people have to set up the security, etc. (I'm thinking in very
> broad terms here - e.g one has to lock one's car/house, enter a security code
> to use an ATM card, etc, etc.) OK, so HTTPS has basically zero impact on the
> average user - is the same level of user inattention really possible with
> email security?

What I currently have is a prototype that makes sending the email
completely transparent except in the case where I either want to only
send the mail if t can be sent encrypted or only if it can be sent
encrypted under particular security guarantees.

That bit is almost complete, I just need to finish one little bit and
its good to go. It works with the mail client you have right now
without any plug in or extension. The outbound mail is redirected
through a proxy which does all the necessary.


The second part is the configuration model. Right now the situation is
that configuration is a one time operation. But it is far from
painless because I am using the legacy clients and the configuration
model is, well stupid. It requires a lot of user intervention and
understanding.

I have a plan that will make that part easier than configuring a mail
client today. i can't make configuring crypto a zero effort operation
but I can make sure you only need to do it once per device (i.e.
subsequent updates are completely automatic). And I can make the joint
task of configuring the crypto and the mail account settings easier
than one or the other alone.

This is the part that I am coding now. It does have impact on the use
piece however since one of the ways I am simplifying the approach is
to have as much consistency as possible. Rather than deal with a
single key or dual keys for encryption and signature I require
everyone have dual keys. This makes it much easier to do recovery from
user blunders or machine failures.


-- 
Website: http://hallambaker.com/


From nobody Wed Apr  9 10:19:36 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 100A11A029B for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 10:19:36 -0700 (PDT)
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] autolearn=ham
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 q4EEViqjVn1n for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 10:19:31 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B06321A01C1 for <ietf@ietf.org>; Wed,  9 Apr 2014 10:19:31 -0700 (PDT)
Received: from [10.168.69.12] (pool-71-164-185-121.dllstx.fios.verizon.net [71.164.185.121]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s39HJRL9025340 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 9 Apr 2014 10:19:31 -0700
Message-ID: <534580AF.4080602@dcrocker.net>
Date: Wed, 09 Apr 2014 12:17:35 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
Subject: Re: Security for various IETF services
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu>
In-Reply-To: <20140409154919.11E6118C106@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 09 Apr 2014 10:19:31 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6S8fzp4Yj9tN2mI2jzt4eyb7QeQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 17:19:36 -0000

On 4/9/2014 10:49 AM, Noel Chiappa wrote:
>      > the way forward is pretty straightforward: Take the S/MIME message
>      > format and graft the PGP web of trust and fingerprint trust models onto
>      > it.
>
> I agree wholly with your prefatory observation, and like your suggested
> solution.


The interesting premise in the suggestion is that a web of trust key 
management model is useful at Internet scale.

I don't understand why anyone believes that.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Apr  9 10:30:50 2014
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EFCF1A02D4; Wed,  9 Apr 2014 10:30:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_PASS=-0.001] autolearn=ham
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 3do3K2wBkzPo; Wed,  9 Apr 2014 10:30:43 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 20DD71A02D3; Wed,  9 Apr 2014 10:30:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 166551E41E0; Wed,  9 Apr 2014 10:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8f52hU9VKylm; Wed,  9 Apr 2014 10:30:38 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) by c8a.amsl.com (Postfix) with ESMTPSA id AF45F1E40EF; Wed,  9 Apr 2014 10:30:37 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Request for Feedback on RFC Series Oversight Committee (RSOC) Nominations 
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Wed, 9 Apr 2014 13:30:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <9529EEB5-7D6B-483E-A9B8-CDB47D64CFD6@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VXf67l4DYmDPKFWZtZXTc9gFI2E
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IAB <iab@iab.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 17:30:48 -0000

The IAB announced a call for nominations and volunteers for serving on
the RSOC on 26 March 2014.  For details on the position and further
links, please see the previous message here:
=
https://mailarchive.ietf.org/arch/msg/ietf-announce/nAOM54TxJOtg_wFfmnKXoS=
Sf594

The call completed, and xx people accepted nominations.  As specified in
the announcement, the IAB is now providing that list to the community.
If you have opinions, information, or perspectives on the individuals =
for
the RSOC which you believe would help the IAB select the RSOC =
membership,
please provide comments to iab-chair at iab.org and execd at iab.org.
Please provide feedback before 23 April 2014.

With thanks for their willingness to serve, the list of willing =
nominees:

- Sara Banks
- Donald Eastlake
- Paul Hoffman
- Robert Sparks

Thank you,
  Russ Housley
  IAB Chair=20=


From nobody Wed Apr  9 10:31:53 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC1C1A03E4 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 10:31:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 ikdHwGDD3Dzf for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 10:31:49 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 3D3B81A03C3 for <ietf@ietf.org>; Wed,  9 Apr 2014 10:31:47 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D99CC1B805A for <ietf@ietf.org>; Wed,  9 Apr 2014 10:31:46 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id AA6BA19005C; Wed,  9 Apr 2014 10:31:46 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Apr 2014 10:31:40 -0700
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <534580AF.4080602@dcrocker.net>
Date: Wed, 9 Apr 2014 13:31:40 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <3979F9B2-01CB-4DFE-A872-3EED6840F44D@nominum.com>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net>
To: <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/T022d81uMXcTQT-WcUcAFZ0u2E0
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 17:31:50 -0000

On Apr 9, 2014, at 1:17 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> The interesting premise in the suggestion is that a web of trust key =
management model is useful at Internet scale.

It doesn't actually require a web of trust.   It could work as well =
(likely better) as a simple whitelisting system with no shared trust at =
all.


From nobody Wed Apr  9 10:48:15 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0984B1A02D4; Wed,  9 Apr 2014 10:48:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.502
X-Spam-Level: 
X-Spam-Status: No, score=-100.502 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 GN60jYj02W8b; Wed,  9 Apr 2014 10:48:02 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0144.outbound.protection.outlook.com [207.46.163.144]) by ietfa.amsl.com (Postfix) with ESMTP id 3B53E1A0303; Wed,  9 Apr 2014 10:48:01 -0700 (PDT)
Received: from [192.168.0.34] (69.131.53.57) by BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20) with Microsoft SMTP Server (TLS) id 15.0.913.9; Wed, 9 Apr 2014 17:47:58 +0000
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <0F1BA31B-4580-4AC0-9CB4-7FC0EE3860B0@firsthand.net>
Date: Wed, 9 Apr 2014 13:47:48 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <7FA1855F-AE17-41DC-B0CD-1A11B293C5A3@isoc.org>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <533EF5BE.7080300@dcrocker.net> <DDC6FCD7-B956-44A8-AAA9-AA798EA94B80@isoc.org> <8A8DDF7840E041B5EFDAC863@JcK-HP8200.jck.com> <F8B2F4F2-4B8F-49A8-8233-E80BAE737128@isoc.org> <0F1BA31B-4580-4AC0-9CB4-7FC0EE3860B0@firsthand.net>
To: cdel.firsthand.net <cdel@firsthand.net>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BLUPR06CA004.namprd06.prod.outlook.com (10.255.223.142) To BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20)
X-Forefront-PRVS: 01762B0D64
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(428001)(377454003)(51704005)(199002)(189002)(24454002)(74502001)(92566001)(77982001)(81342001)(99396002)(92726001)(80976001)(57306001)(82746002)(46102001)(50466002)(79102001)(20776003)(50226001)(83322001)(4396001)(88136002)(36756003)(74662001)(89996001)(93916002)(19580405001)(86362001)(42186004)(87976001)(31966008)(62966002)(81542001)(19580395003)(23746002)(83072002)(80022001)(66066001)(87286001)(77156001)(83716003)(33656001)(76482001)(47776003)(85852003)(50986999)(76176999); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB234; H:[192.168.0.34]; FPR:1CC4F01C.AF2297E8.F1E3736B.84E6D9AB.20336; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/M80qepso2-93Q0kxzMta03uTdwo
Cc: Working Group Chairs <wgchairs@ietf.org>, IETF Discussion <ietf@ietf.org>, IAOC <iaoc@ietf.org>, "iab@iab.org IAB" <iab@iab.org>, The IESG <iesg@ietf.org>, John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 17:48:07 -0000

=20
On Apr 4, 2014, at 6:08 PM, cdel.firsthand.net <cdel@firsthand.net> =
wrote:

> I was about to ask under what classes IETF registrations are held?=20

IETF is in Class 42.

The IETF Logo is in the following classes:  9, 35, 42

=93IETF Secretariat=94 is in: 35, 42.

Ray


>=20
>=20
> Christian de Larrinaga
>=20
>=20
>> On 4 Apr 2014, at 22:57, Ray Pelletier <rpelletier@isoc.org> wrote:
>>=20
>>=20
>>> On Apr 4, 2014, at 3:45 PM, John C Klensin <john-ietf@jck.com> =
wrote:
>>>=20
>>>=20
>>>=20
>>> --On Friday, April 04, 2014 14:19 -0400 Ray Pelletier
>>> <rpelletier@isoc.org> wrote:
>>>=20
>>>>> It sounds as if this will open the door to my being able to
>>>>> advertise myself as the IETF Secretariat.  Or even the ITU's
>>>>> being able to.  Yes?
>>>>=20
>>>> You could certainly use "Secretariat" but you cannot use
>>>> "IETF Secretariat" without violating the "IETF"
>>>> trademark.
>>>=20
>>> Ray, I assume that if Dave (or someone else) set themselves up
>>> as the International Elegant Tophat Fabrication Society, made at
>>> least a perfunctory effect to establish themselves as being in
>>> that business, established a business unit that they called
>>> their "Secretariat", and then advertised the result as the "IETF
>>> Secretariat", things could get dicey.  Given the different line
>>> of business, they might even be able to take out a trademark on
>>> "IETF Secretariat".  Right?
>>=20
>> The "risk" applies to IETF in addition to IETF Secretariat. =20
>> We don't own IETF in every class of goods and services.=20
>> IETF bananas, top hats and car tires can be sold and =20
>> that won=92t violate our IETF trademark =20
>>=20
>> People aren=92t going to be confused between the two,
>> just like they aren=92t for Apple computers and Apple records.
>>=20
>> Ray
>>>=20
>>> Now, whether having a trademark registered as "IETF Secretariat"
>>> with whatever line of business the IETF and IETF Secretariat
>>> claim to be in would offer significant protection against that
>>> attack is far outside my knowledge or experience.
>>>=20
>>> I have enough trouble imagining someone going to the trouble to
>>> attempt the above as an attack that I think it would probably be
>>> foolish to worry about it, but it is, in principle, the
>>> difference between "no risk" and "no risk worth worrying about".
>>>=20
>>>  john
>>=20


From nobody Wed Apr  9 13:08:30 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 583241A024F for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 13:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.637
X-Spam-Level: 
X-Spam-Status: No, score=0.637 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
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 mOv9qDPbqxWr for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 13:08:22 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1791A0230 for <ietf@ietf.org>; Wed,  9 Apr 2014 13:08:18 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WXynB-0007OH-IC; Wed, 09 Apr 2014 20:08:17 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id EA9C05804C9; Wed,  9 Apr 2014 16:08:14 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1397074094; bh=kRWegHfNRnuX5SR6fvRwjsSxc+fghV9opu0MDdVBdzs=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ornd91mPS/EeN9d09v7LEuqT6jxplOminK+Gg8/njf5htcoD9TBzrcy4FMTAPCqvQ L/nDrpL7Isqr4/i8P3p3owx+e1zpGoS+Ev/cnoCCRMnF5HX6CggX93xTIqXewxBsO1 9luamig4bq3Io92KM8SBuVtFiy6PRCiEDcK0nZbg=
Date: Wed, 9 Apr 2014 16:08:14 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: dcrocker@bbiw.net
Subject: Re: Security for various IETF services
Message-ID: <20140409200814.GA15303@thunk.org>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534580AF.4080602@dcrocker.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PsjT1Kh85iPxi_-1vw4QzOQ9Av8
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 20:08:27 -0000

On Wed, Apr 09, 2014 at 12:17:35PM -0500, Dave Crocker wrote:
> 
> The interesting premise in the suggestion is that a web of trust key
> management model is useful at Internet scale.
> 
> I don't understand why anyone believes that.

The problem is that nearly all solutions to the PKI problem I've seen
to date fall into three classes, all of which have problems (which is
why there is the oft-retold joke about how any protocol which requires
a PKI is doomed).

1) The current "race to the bottom" multiple competing CA model, which
while scalable, has had some rather spectacular failures, of which
Diginotar is only one example.

2) Trust the government to run the CA ("I'm from the government, and
I'm here to help!") --- which raises questions of "which government"
and "how do you trust that someone won't invoke 'national security' as
the root password to the Constitution / Fundamental Rights" to abuse
the trust that the government would have it served as the CA?

3) The PGP web of trust model, which doesn't scale to the Internet,
but which is good enough for small communities for which high trust is
extremely important (for example, such as Debian Developers and the
Linux kernel.org keyrings).

I suspect #1 could have gotten traction as far as usage is concerned,
if the pricing model for a given level of security had been attractive
enough and if it had been sufficiently easy for mere mortals to get
x509 user certificates.  But as it is, #3 has been winning out as far
as usage because the people who care enough about security to go do
the extra work are also the folks who (a) don't trust the CA's, and/or
(b) are too cheap to be willing to pay what the CA's want to charge,
and so the PGP web of trust model is quite suited for their needs.

At the end, because the use cases and the requirements for different
communities are quite different, I think the only thing that has a
chance is some kind of hybrid solution.  Because questions of format
aside, the main difference between all of these schemes is who do you
put in your trusted root, and how much cerifying delegation do you
allow?  

If you're the US military and you let the NSA handle all of your key
management needs, that's one answer.  If you're a web browser, you
mark several dozen or several hundred CA's (depending on how you
count), and that's another answer.  If you're a Linux kernel developer
and you want to get an account on kernel.org and be able to sign git
tags, you need to either be directly signed by one of four or five
trusted root individuals, or have 3 signatures by keys that are signed
by the root individuals, and that's yet another answer.

What we really need is widely deployed software which can support all
of these different use cases, and deal with the fact that there is
significant base deployed that will add resistance to switching to a
whole new certificate format.  (For example, x509 certs have a large
amount of infrastructure, but so do PGP --- there are smart card and
Yubikey NEO's that support storage of private keys for PGP and ssh on
hardware tokens.)  And so I might want to use one of PKI policy when
validating e-mail sent by a fellow kernel developer, and use a
different PKI policy if I'm talking to a stranger someone for whom the
only authentication path is via some "race to the bottom" cerifying
authority, and where my trust requirements might be different.

I'll note that I can mostly do that today, because my mail user agent
(mutt) supports both S/MIME and PGP.  So any proposed solution should
ideally be better than what we can do today with that kind of support
(namely, adding both S/MIME and PGP into the mail client).

Cheers,

						- Ted


From nobody Wed Apr  9 13:15:10 2014
Return-Path: <tbray@textuality.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 562A21A0321 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 13:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.377
X-Spam-Level: 
X-Spam-Status: No, score=-1.377 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_LOW=-0.7] autolearn=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 P_3nDlj2n8NQ for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 13:15:02 -0700 (PDT)
Received: from mail-vc0-f174.google.com (mail-vc0-f174.google.com [209.85.220.174]) by ietfa.amsl.com (Postfix) with ESMTP id 261701A0397 for <ietf@ietf.org>; Wed,  9 Apr 2014 13:15:02 -0700 (PDT)
Received: by mail-vc0-f174.google.com with SMTP id ld13so2506683vcb.5 for <ietf@ietf.org>; Wed, 09 Apr 2014 13:15:01 -0700 (PDT)
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:content-type; bh=2nC2ho/ttrs2D/Z8cR3kKfAjhtp3OLW/fQQwMVDHBTY=; b=kIPJ3VJBaTKMwkCkgZzkL5Y3l1CgSm6tqBmokihHOox95DEBiPwYMNxokcx8rlUe8T iZ+2nOCaFEMdxFosiKtGRcOLq91mlxwDjH8DL30mqfVTFdSgGVsI8FN/WTrQxuKTOVHm U9WEF0VihSDgrFERkHBgaiBclXPeS1LhOrwUWDCaWFc+vNOjgnTtMZz8cfcvHPNs9Dp9 EejLI7DzXFNO0FNYrWRfZOWBnQbLwIR6A12MbRoEzTdkTVRq6hni4GE1g5zogI8fRzHq yqiEt+WvwUTymzR5CliNvOP1HkYKcbQu9ynsnNL9xIjWtitaXCjBjyAOl656BgbdXhsd 4YSw==
X-Gm-Message-State: ALoCoQll6jcxH1ng73FSmjxrWN6oMYuz/kczDs6CDTEWgYb6bT192vO0QZ73AD4FDpfa2gYOF5ii
MIME-Version: 1.0
X-Received: by 10.221.4.66 with SMTP id ob2mr2251207vcb.28.1397074501388; Wed, 09 Apr 2014 13:15:01 -0700 (PDT)
Received: by 10.220.98.73 with HTTP; Wed, 9 Apr 2014 13:15:00 -0700 (PDT)
X-Originating-IP: [208.54.5.149]
Received: by 10.220.98.73 with HTTP; Wed, 9 Apr 2014 13:15:00 -0700 (PDT)
In-Reply-To: <20140409200814.GA15303@thunk.org>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org>
Date: Wed, 9 Apr 2014 13:15:00 -0700
Message-ID: <CAHBU6ivQbta_kW8L1JWUoELyJWpX53Km60QOnk7xk4qoYNwt-A@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Tim Bray <tbray@textuality.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=089e0122a9246160c704f6a1c1dc
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gSQYd23FylyxbtPNmWVigqBW16Q
Cc: dcrocker@bbiw.net, IETF Discussion <ietf@ietf.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 20:15:07 -0000

--089e0122a9246160c704f6a1c1dc
Content-Type: text/plain; charset=UTF-8

While not a solution, I'm thinking the keybase.io work is a step in a
useful direction.  Just a directory of accounts where you can associate a
keypair with verifiable assertions that its holder controls a particular
Twitter/github account and Web server and DNS.
On Apr 9, 2014 1:08 PM, "Theodore Ts'o" <tytso@mit.edu> wrote:

> On Wed, Apr 09, 2014 at 12:17:35PM -0500, Dave Crocker wrote:
> >
> > The interesting premise in the suggestion is that a web of trust key
> > management model is useful at Internet scale.
> >
> > I don't understand why anyone believes that.
>
> The problem is that nearly all solutions to the PKI problem I've seen
> to date fall into three classes, all of which have problems (which is
> why there is the oft-retold joke about how any protocol which requires
> a PKI is doomed).
>
> 1) The current "race to the bottom" multiple competing CA model, which
> while scalable, has had some rather spectacular failures, of which
> Diginotar is only one example.
>
> 2) Trust the government to run the CA ("I'm from the government, and
> I'm here to help!") --- which raises questions of "which government"
> and "how do you trust that someone won't invoke 'national security' as
> the root password to the Constitution / Fundamental Rights" to abuse
> the trust that the government would have it served as the CA?
>
> 3) The PGP web of trust model, which doesn't scale to the Internet,
> but which is good enough for small communities for which high trust is
> extremely important (for example, such as Debian Developers and the
> Linux kernel.org keyrings).
>
> I suspect #1 could have gotten traction as far as usage is concerned,
> if the pricing model for a given level of security had been attractive
> enough and if it had been sufficiently easy for mere mortals to get
> x509 user certificates.  But as it is, #3 has been winning out as far
> as usage because the people who care enough about security to go do
> the extra work are also the folks who (a) don't trust the CA's, and/or
> (b) are too cheap to be willing to pay what the CA's want to charge,
> and so the PGP web of trust model is quite suited for their needs.
>
> At the end, because the use cases and the requirements for different
> communities are quite different, I think the only thing that has a
> chance is some kind of hybrid solution.  Because questions of format
> aside, the main difference between all of these schemes is who do you
> put in your trusted root, and how much cerifying delegation do you
> allow?
>
> If you're the US military and you let the NSA handle all of your key
> management needs, that's one answer.  If you're a web browser, you
> mark several dozen or several hundred CA's (depending on how you
> count), and that's another answer.  If you're a Linux kernel developer
> and you want to get an account on kernel.org and be able to sign git
> tags, you need to either be directly signed by one of four or five
> trusted root individuals, or have 3 signatures by keys that are signed
> by the root individuals, and that's yet another answer.
>
> What we really need is widely deployed software which can support all
> of these different use cases, and deal with the fact that there is
> significant base deployed that will add resistance to switching to a
> whole new certificate format.  (For example, x509 certs have a large
> amount of infrastructure, but so do PGP --- there are smart card and
> Yubikey NEO's that support storage of private keys for PGP and ssh on
> hardware tokens.)  And so I might want to use one of PKI policy when
> validating e-mail sent by a fellow kernel developer, and use a
> different PKI policy if I'm talking to a stranger someone for whom the
> only authentication path is via some "race to the bottom" cerifying
> authority, and where my trust requirements might be different.
>
> I'll note that I can mostly do that today, because my mail user agent
> (mutt) supports both S/MIME and PGP.  So any proposed solution should
> ideally be better than what we can do today with that kind of support
> (namely, adding both S/MIME and PGP into the mail client).
>
> Cheers,
>
>                                                 - Ted
>
>

--089e0122a9246160c704f6a1c1dc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">While not a solution, I&#39;m thinking the <a href=3D"http:/=
/keybase.io">keybase.io</a> work is a step in a useful direction.=C2=A0 Jus=
t a directory of accounts where you can associate a keypair with verifiable=
 assertions that its holder controls a particular Twitter/github account an=
d Web server and DNS.</p>

<div class=3D"gmail_quote">On Apr 9, 2014 1:08 PM, &quot;Theodore Ts&#39;o&=
quot; &lt;<a href=3D"mailto:tytso@mit.edu">tytso@mit.edu</a>&gt; wrote:<br =
type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Apr 09, 2014 at 12:17:35PM -0500, Dave Crocker wrote:<br>
&gt;<br>
&gt; The interesting premise in the suggestion is that a web of trust key<b=
r>
&gt; management model is useful at Internet scale.<br>
&gt;<br>
&gt; I don&#39;t understand why anyone believes that.<br>
<br>
The problem is that nearly all solutions to the PKI problem I&#39;ve seen<b=
r>
to date fall into three classes, all of which have problems (which is<br>
why there is the oft-retold joke about how any protocol which requires<br>
a PKI is doomed).<br>
<br>
1) The current &quot;race to the bottom&quot; multiple competing CA model, =
which<br>
while scalable, has had some rather spectacular failures, of which<br>
Diginotar is only one example.<br>
<br>
2) Trust the government to run the CA (&quot;I&#39;m from the government, a=
nd<br>
I&#39;m here to help!&quot;) --- which raises questions of &quot;which gove=
rnment&quot;<br>
and &quot;how do you trust that someone won&#39;t invoke &#39;national secu=
rity&#39; as<br>
the root password to the Constitution / Fundamental Rights&quot; to abuse<b=
r>
the trust that the government would have it served as the CA?<br>
<br>
3) The PGP web of trust model, which doesn&#39;t scale to the Internet,<br>
but which is good enough for small communities for which high trust is<br>
extremely important (for example, such as Debian Developers and the<br>
Linux <a href=3D"http://kernel.org" target=3D"_blank">kernel.org</a> keyrin=
gs).<br>
<br>
I suspect #1 could have gotten traction as far as usage is concerned,<br>
if the pricing model for a given level of security had been attractive<br>
enough and if it had been sufficiently easy for mere mortals to get<br>
x509 user certificates. =C2=A0But as it is, #3 has been winning out as far<=
br>
as usage because the people who care enough about security to go do<br>
the extra work are also the folks who (a) don&#39;t trust the CA&#39;s, and=
/or<br>
(b) are too cheap to be willing to pay what the CA&#39;s want to charge,<br=
>
and so the PGP web of trust model is quite suited for their needs.<br>
<br>
At the end, because the use cases and the requirements for different<br>
communities are quite different, I think the only thing that has a<br>
chance is some kind of hybrid solution. =C2=A0Because questions of format<b=
r>
aside, the main difference between all of these schemes is who do you<br>
put in your trusted root, and how much cerifying delegation do you<br>
allow?<br>
<br>
If you&#39;re the US military and you let the NSA handle all of your key<br=
>
management needs, that&#39;s one answer. =C2=A0If you&#39;re a web browser,=
 you<br>
mark several dozen or several hundred CA&#39;s (depending on how you<br>
count), and that&#39;s another answer. =C2=A0If you&#39;re a Linux kernel d=
eveloper<br>
and you want to get an account on <a href=3D"http://kernel.org" target=3D"_=
blank">kernel.org</a> and be able to sign git<br>
tags, you need to either be directly signed by one of four or five<br>
trusted root individuals, or have 3 signatures by keys that are signed<br>
by the root individuals, and that&#39;s yet another answer.<br>
<br>
What we really need is widely deployed software which can support all<br>
of these different use cases, and deal with the fact that there is<br>
significant base deployed that will add resistance to switching to a<br>
whole new certificate format. =C2=A0(For example, x509 certs have a large<b=
r>
amount of infrastructure, but so do PGP --- there are smart card and<br>
Yubikey NEO&#39;s that support storage of private keys for PGP and ssh on<b=
r>
hardware tokens.) =C2=A0And so I might want to use one of PKI policy when<b=
r>
validating e-mail sent by a fellow kernel developer, and use a<br>
different PKI policy if I&#39;m talking to a stranger someone for whom the<=
br>
only authentication path is via some &quot;race to the bottom&quot; cerifyi=
ng<br>
authority, and where my trust requirements might be different.<br>
<br>
I&#39;ll note that I can mostly do that today, because my mail user agent<b=
r>
(mutt) supports both S/MIME and PGP. =C2=A0So any proposed solution should<=
br>
ideally be better than what we can do today with that kind of support<br>
(namely, adding both S/MIME and PGP into the mail client).<br>
<br>
Cheers,<br>
<br>
=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 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 - Ted<br>
<br>
</blockquote></div>

--089e0122a9246160c704f6a1c1dc--


From nobody Wed Apr  9 13:16:03 2014
Return-Path: <steve@shinkuro.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F95D1A0332 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 13:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.455
X-Spam-Level: *
X-Spam-Status: No, score=1.455 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_DSL=1.129, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=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 64rHJn1340f5 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 13:16:00 -0700 (PDT)
Received: from execdsl.com (remote.shinkuro.com [50.56.68.178]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD1B1A0396 for <ietf@ietf.org>; Wed,  9 Apr 2014 13:15:54 -0700 (PDT)
Received: from dummy.name; Wed, 09 Apr 2014 20:15:53 +0000
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Steve Crocker <steve@shinkuro.com>
In-Reply-To: <20140409200814.GA15303@thunk.org>
Date: Wed, 9 Apr 2014 16:15:53 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org>
To: Theodore Ts'o <tytso@mit.edu>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dPIUy30kCR2qYOCQNH0d_s4RSQs
Cc: ietf@ietf.org, David Crocker <dcrocker@bbiw.net>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 20:16:01 -0000

My own opinion is related but not identical.  I agree solutions 1 and 3 =
are failures; 1 doesn=92t provide the trust and 3 doesn=92t scale.  =
Solution 2 is also problematic because the government tends to overreach =
and there isn=92t a single government.

DNSSEC provides a base platform to build upon.  It doesn=92t claim to =
provide the level of trust the CA system tried to provide.  That=92s a =
key strength, not a weakness.

Steve



On Apr 9, 2014, at 4:08 PM, Theodore Ts'o <tytso@mit.edu> wrote:

> On Wed, Apr 09, 2014 at 12:17:35PM -0500, Dave Crocker wrote:
>>=20
>> The interesting premise in the suggestion is that a web of trust key
>> management model is useful at Internet scale.
>>=20
>> I don't understand why anyone believes that.
>=20
> The problem is that nearly all solutions to the PKI problem I've seen
> to date fall into three classes, all of which have problems (which is
> why there is the oft-retold joke about how any protocol which requires
> a PKI is doomed).
>=20
> 1) The current "race to the bottom" multiple competing CA model, which
> while scalable, has had some rather spectacular failures, of which
> Diginotar is only one example.
>=20
> 2) Trust the government to run the CA ("I'm from the government, and
> I'm here to help!") --- which raises questions of "which government"
> and "how do you trust that someone won't invoke 'national security' as
> the root password to the Constitution / Fundamental Rights" to abuse
> the trust that the government would have it served as the CA?
>=20
> 3) The PGP web of trust model, which doesn't scale to the Internet,
> but which is good enough for small communities for which high trust is
> extremely important (for example, such as Debian Developers and the
> Linux kernel.org keyrings).
>=20
> I suspect #1 could have gotten traction as far as usage is concerned,
> if the pricing model for a given level of security had been attractive
> enough and if it had been sufficiently easy for mere mortals to get
> x509 user certificates.  But as it is, #3 has been winning out as far
> as usage because the people who care enough about security to go do
> the extra work are also the folks who (a) don't trust the CA's, and/or
> (b) are too cheap to be willing to pay what the CA's want to charge,
> and so the PGP web of trust model is quite suited for their needs.
>=20
> At the end, because the use cases and the requirements for different
> communities are quite different, I think the only thing that has a
> chance is some kind of hybrid solution.  Because questions of format
> aside, the main difference between all of these schemes is who do you
> put in your trusted root, and how much cerifying delegation do you
> allow? =20
>=20
> If you're the US military and you let the NSA handle all of your key
> management needs, that's one answer.  If you're a web browser, you
> mark several dozen or several hundred CA's (depending on how you
> count), and that's another answer.  If you're a Linux kernel developer
> and you want to get an account on kernel.org and be able to sign git
> tags, you need to either be directly signed by one of four or five
> trusted root individuals, or have 3 signatures by keys that are signed
> by the root individuals, and that's yet another answer.
>=20
> What we really need is widely deployed software which can support all
> of these different use cases, and deal with the fact that there is
> significant base deployed that will add resistance to switching to a
> whole new certificate format.  (For example, x509 certs have a large
> amount of infrastructure, but so do PGP --- there are smart card and
> Yubikey NEO's that support storage of private keys for PGP and ssh on
> hardware tokens.)  And so I might want to use one of PKI policy when
> validating e-mail sent by a fellow kernel developer, and use a
> different PKI policy if I'm talking to a stranger someone for whom the
> only authentication path is via some "race to the bottom" cerifying
> authority, and where my trust requirements might be different.
>=20
> I'll note that I can mostly do that today, because my mail user agent
> (mutt) supports both S/MIME and PGP.  So any proposed solution should
> ideally be better than what we can do today with that kind of support
> (namely, adding both S/MIME and PGP into the mail client).
>=20
> Cheers,
>=20
> 						- Ted
>=20


From nobody Wed Apr  9 13:36:22 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 537061A0256 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 13:36:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 u-8H4bxCypH2 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 13:36:16 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 6EBF51A02B0 for <ietf@ietf.org>; Wed,  9 Apr 2014 13:36:16 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id wp18so3314160obc.37 for <ietf@ietf.org>; Wed, 09 Apr 2014 13:36:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9u53Z39C7LZbgsYBkxUSKc8wKcrCOFR9r/e/SbW6J7c=; b=BLhFwWQFM+oUUViiF8oCIuxeXXpAAvQXmPmpYbjYB0OG/L/zTERfT5oA533H/anWnf TPLbV6Xi4XJ2ibW5UVwmZ5T2WoY3rd7n5rjYc/7ATeNrXhyGuD8lFtUJneq6ugIbEpY8 8nIzMNGhXM0tFh4Z5TmQvt+maNenC/QZ+RiYk=
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:content-type; bh=9u53Z39C7LZbgsYBkxUSKc8wKcrCOFR9r/e/SbW6J7c=; b=ZJ9yoDHA8rF38VlbVPKMQ7H3HtG8/weKeY/iaEpqjwBOrLhCZyQ77DJD4RtKnBbuIf 4vjwrXFbENgxotBGv8TpLIRKo/JxvPDyJMuc6RBU349VN5aas9M6aboXqyFcvE7knjun P6AwgjXOTYipAUvUr6id9MbqOYLKRQ34LUN+0yaI76rbxp6owa6o+ch1CseZE8UAqWat kS/+ip3NqxMWi9xt6y6aglBkX/8xoc/NnREVdURK3yB2EtAp9u/zgsE+C0xiQNgun3SX 5lU/7vbG4VTSthFJpmasrquzqBz18Zazyr/gNtJQkqqnNmATk1XV+7jfxoVaA74Ii9t/ 0cTg==
X-Gm-Message-State: ALoCoQn+L5feLl+15fG1a8xu9ZUOGYWqB/vHLDTWjtCwqrtq/mTFO1bOzo5g7LPB46i9scz1VA0V
MIME-Version: 1.0
X-Received: by 10.60.103.210 with SMTP id fy18mr2251660oeb.75.1397075775807; Wed, 09 Apr 2014 13:36:15 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Wed, 9 Apr 2014 13:36:15 -0700 (PDT)
In-Reply-To: <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com>
Date: Wed, 9 Apr 2014 21:36:15 +0100
Message-ID: <CAKHUCzymXu0TGEYD6dQj9OVhGn2pgE9nPqDG6guV+RS+L8XTow@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Dave Cridland <dave@cridland.net>
To: Steve Crocker <steve@shinkuro.com>
Content-Type: multipart/alternative; boundary=089e0115ee7c57765504f6a20d5e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aiTUIJ4xMC4JL7jpATuEWNuyP8Q
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, Theodore Ts'o <tytso@mit.edu>, "ietf@ietf.org Discussion" <ietf@ietf.org>, David Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 20:36:21 -0000

--089e0115ee7c57765504f6a20d5e
Content-Type: text/plain; charset=ISO-8859-1

On 9 April 2014 21:15, Steve Crocker <steve@shinkuro.com> wrote:

> My own opinion is related but not identical.  I agree solutions 1 and 3
> are failures; 1 doesn't provide the trust and 3 doesn't scale.  Solution 2
> is also problematic because the government tends to overreach and there
> isn't a single government.
>
> DNSSEC provides a base platform to build upon.  It doesn't claim to
> provide the level of trust the CA system tried to provide.  That's a key
> strength, not a weakness.
>

DNSSEC, and DANE, allow you to provide a "Domain Validated" public key,
much like the cheap/free certificates currently available from CAs, but
more reliably and simply. I think the same level of trust is there either
way, except that the cheap/free CA certs are very weakly validated in
practise.

CAs can provide actual identity assertions, and in private situations
authorization information.

I suspect that if we can get DANE deployed, we'll see most of the cheap and
somewhat useless CAs vanish, and only those with reasonable tust remaining
survive on fully validated, EV et al, certs, actually, but that's besides
the point.

I wonder if we can't use DANE, S/MIME, WebFinger and a little
sensibly-applied PKI, so that:

1) You could find out assertions of what CA (if any) users of a particular
domain use for end-user client certificates via a TLSA record. Say _users
IN TLSA ...

2) We can use WebFinger to find the certificate itself, and therefore a
possibly signed assertion of actual identity, both WebFinger and this
certificate protected currently by stock PKIX (and in the future, DANE).

I think this gives you essentially everything anyone might want, but for
added bonuses, we could do a web-of-trust thing hanging off WebFinger
(publish any signatures anyone else is prepared to give you) or via public
services.

However, it's probably been suggested before and shot down before, so feel
free to point me to its death notice. :-)

Dave.

--089e0115ee7c57765504f6a20d5e
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 9=
 April 2014 21:15, Steve Crocker <span dir=3D"ltr">&lt;<a href=3D"mailto:st=
eve@shinkuro.com" target=3D"_blank">steve@shinkuro.com</a>&gt;</span> wrote=
:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex">
My own opinion is related but not identical. &nbsp;I agree solutions 1 and =
3 are failures; 1 doesn&rsquo;t provide the trust and 3 doesn&rsquo;t scale=
. &nbsp;Solution 2 is also problematic because the government tends to over=
reach and there isn&rsquo;t a single government.<br>

<br>
DNSSEC provides a base platform to build upon. &nbsp;It doesn&rsquo;t claim=
 to provide the level of trust the CA system tried to provide. &nbsp;That&r=
squo;s a key strength, not a weakness.<br></blockquote><div><br></div><div>=
DNSSEC, and DANE, allow you to provide a &quot;Domain Validated&quot; publi=
c key, much like the cheap/free certificates currently available from CAs, =
but more reliably and simply. I think the same level of trust is there eith=
er way, except that the cheap/free CA certs are very weakly validated in pr=
actise.</div>
<div><br></div><div>CAs can provide actual identity assertions, and in priv=
ate situations authorization information.</div><div><br></div><div>I suspec=
t that if we can get DANE deployed, we&#39;ll see most of the cheap and som=
ewhat useless CAs vanish, and only those with reasonable tust remaining sur=
vive on fully validated, EV et al, certs, actually, but that&#39;s besides =
the point.</div>
<div><br></div><div>I wonder if we can&#39;t use DANE, S/MIME, WebFinger an=
d a little sensibly-applied PKI, so that:</div><div><br></div><div>1) You c=
ould find out assertions of what CA (if any) users of a particular domain u=
se for end-user client certificates via a TLSA record. Say _users IN TLSA .=
..</div>
<div><br></div><div>2) We can use WebFinger to find the certificate itself,=
 and therefore a possibly signed assertion of actual identity, both WebFing=
er and this certificate protected currently by stock PKIX (and in the futur=
e, DANE).</div>
<div><br></div><div>I think this gives you essentially everything anyone mi=
ght want, but for added bonuses, we could do a web-of-trust thing hanging o=
ff WebFinger (publish any signatures anyone else is prepared to give you) o=
r via public services.</div>
<div><br></div><div>However, it&#39;s probably been suggested before and sh=
ot down before, so feel free to point me to its death notice. :-)</div><div=
><br></div><div>Dave.</div></div></div></div>

--089e0115ee7c57765504f6a20d5e--


From nobody Wed Apr  9 19:01:26 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379DB1A0573 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 19:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.674
X-Spam-Level: 
X-Spam-Status: No, score=-2.674 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 HHKW7N8b3rU5 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 19:01:18 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id D52D11A05D1 for <ietf@ietf.org>; Wed,  9 Apr 2014 19:01:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397095278; x=1428631278; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=4BermJ8hk7OHpErHmvoR6qsSRulc2OeHKF6L47wyIU0=; b=RALt0hET7j5qczfLl8YAYk9b0QjINam0RZgxN+afF24zdPZYjGKXXo59 JYavYzyptJlyb8z06sMSsfxRkTqkmFI8xdkVIADRTJCzkRyuhJ8ZxrxRk c7JA9LETPaTAFPCmXbtXoRPuR9ZMWAYFilTVo96u8dlvLiLOsdrdLE4qS w=;
X-IronPort-AV: E=McAfee;i="5400,1158,7403"; a="27803571"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 09 Apr 2014 19:01:18 -0700
X-IronPort-AV: E=Sophos;i="4.97,830,1389772800"; d="scan'208";a="713330351"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Apr 2014 19:01:50 -0700
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Apr 2014 19:01:17 -0700
Message-ID: <p06240604cf6baa6b989d@[99.111.97.136]>
In-Reply-To: <CAMm+LwgLxR65a1nKmKpqW39_BvgMgAGwBCxAE+eEs-9bnLdv8A@mail.gmail.com>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@99.111.97.136> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com> <CAMm+LwgLxR65a1nKmKpqW39_BvgMgAGwBCxAE+eEs-9bnLdv8A@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Wed, 9 Apr 2014 19:01:16 -0700
To: Phillip Hallam-Baker <hallam@gmail.com>, "Fred Baker (fred)" <fred@cisco.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: Security for various IETF services
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KIfen3GPNB90sjqh64urwbVeM6Q
Cc: Randall Gellens <randy@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 02:01:23 -0000

At 9:12 AM -0400 4/9/14, Phillip Hallam-Baker wrote:

>>  To that end, I could imagine a requirement for some kind of 
>> roadmap. "The tools that access the IETF SMTP and HTTP sites use 
>> protocols X, Y, and Z. After <date>, we require them to use Secure 
>> X, Secure Y, and Secure Z, and traffic originated by the IETF 
>> sites shall use such protocols."
>
>  This sounds like a good idea.

To me it sounds like a knee-jerk reaction rather than an assessment 
of what we need to protect and what the costs are of various 
mechanisms.

>  But we currently have a big problem in
>  that the IETF has two email security standards, not one. And the two
>  sides don't talk and this has created a stalemate that has blocked
>  ubiquitous use of either.

We actually have a few more email security standards, but regardless, 
I don't think the major barrier to deployment is that there is not a 
single standard.  There are a number of reasons why email end-to-end 
encryption is rarely used, which include the difficulty of managing 
keys, but it's also worth pointing out that end-to-end encrypted 
email breaks a lot of the anti-spam, unless users share their private 
keys with their mail provider (which kind of defeats the point).

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Frequently, people can tell you they've read a book and
liked it, but they can't tell you why.  We don't want the
reader to have to do the hard work of figuring that out.
                    --Duncan Smith, creator of NoveList.


From nobody Wed Apr  9 19:24:46 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 390E71A02D1 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 19:24:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.374
X-Spam-Level: 
X-Spam-Status: No, score=-0.374 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 oX7TPTYSFTwo for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 19:24:42 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id E0AC81A02B7 for <ietf@ietf.org>; Wed,  9 Apr 2014 19:24:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397096683; x=1428632683; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=BlwKF4mmxeF1IQ4UzNaQ2rwPzc9b38rQNAILWY+i3EU=; b=epNEdJFPXOShOsx092RGOSrtgpOGhIgj4AikdA45gUcnLrpOKgSKSi9s isK++tIlT0uD7GJ4MHuTB9hx+WmdvzWw7fQQfvwxS7/wu2Wm+F/qYQwDs rdDfyR+fcw+wrnZMFRFEHXm+yeZ61r9oL1Ju5BYSSBFrSEpaOcVfkvVQa o=;
X-IronPort-AV: E=McAfee;i="5400,1158,7403"; a="61857120"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 09 Apr 2014 19:24:43 -0700
X-IronPort-AV: E=Sophos;i="4.97,830,1389772800"; d="scan'208";a="29216668"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Apr 2014 19:25:11 -0700
Received: from [99.111.97.136] (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Apr 2014 19:24:41 -0700
Message-ID: <p06240605cf6bb14e35f7@[99.111.97.136]>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>,<p06240603cf639ebf8c0d@[99.11 1.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>, <p06240601cf6663952ae4@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>
X-Mailer: Eudora for Mac OS X
Date: Wed, 9 Apr 2014 19:24:39 -0700
To: <l.wood@surrey.ac.uk>, <randy@qti.qualcomm.com>, <elwynd@dial.pipex.com>,  <agmalis@gmail.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea  Efflux Appliances (HTCPCP-TEA)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/L7z2aLWaWHMnFZ8TsOwWiRYVcnc
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 02:24:44 -0000

At 3:05 AM +0100 4/6/14, <l.wood@surrey.ac.uk> wrote:

>  Always boil the water first. This is in line
>  with best security practice, which attempts
>  to boil the ocean.

So global warming is a security effort?

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
It was the first airplane . . . that could make money just by
hauling passengers.
    --C. R. Smith, president of American Airlines, regarding the
    DC-3. The DC-3 specifications were shaped by AA.


From nobody Wed Apr  9 21:10:56 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44F641A040E for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 21:10:53 -0700 (PDT)
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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 Wztzdr65U5-k for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 21:10:49 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.106]) by ietfa.amsl.com (Postfix) with ESMTP id 7F41A1A0407 for <ietf@ietf.org>; Wed,  9 Apr 2014 21:10:48 -0700 (PDT)
Received: from [193.109.255.147:34285] by server-2.bemta-14.messagelabs.com id 1E/F6-21684-7C916435; Thu, 10 Apr 2014 04:10:47 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-72.messagelabs.com!1397103046!10795743!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10185 invoked from network); 10 Apr 2014 04:10:46 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-6.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 10 Apr 2014 04:10:46 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Thu, 10 Apr 2014 05:10:45 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@qti.qualcomm.com>, <elwynd@dial.pipex.com>, <agmalis@gmail.com>
Date: Thu, 10 Apr 2014 05:07:04 +0100
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Topic: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Index: Ac9UZAoIRaaY65faRNWm60z+O+PC3QADksYG
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EED1@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>,<p06240603cf639ebf8c0d@[99.11 1.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>, <p06240601cf6663952ae4@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>, <p06240605cf6bb14e35f7@[99.111.97.136]>
In-Reply-To: <p06240605cf6bb14e35f7@[99.111.97.136]>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aCDmzn7pdui7LAF-tLUJhQHr7Gk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 04:10:53 -0000

Crypto requires increased processing power, requiring more energy, producin=
g more waste heat.

So, yes, it is a contributing factor to global warming. Crypto is red or bl=
ack. It isn't green.

Whatever the sun does in terms of output (e.g. Maunder minimum) dwarfs this=
 and many other man-made contributing factors, of course.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Randall Gellens [randy@qti.qualcomm.com]
Sent: 10 April 2014 03:24
To: Wood L  Dr (Electronic Eng); randy@qti.qualcomm.com; elwynd@dial.pipex.=
com; agmalis@gmail.com
Cc: ietf@ietf.org
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea=
  Efflux Appliances (HTCPCP-TEA)

At 3:05 AM +0100 4/6/14, <l.wood@surrey.ac.uk> wrote:

>  Always boil the water first. This is in line
>  with best security practice, which attempts
>  to boil the ocean.

So global warming is a security effort?

--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
It was the first airplane . . . that could make money just by
hauling passengers.
    --C. R. Smith, president of American Airlines, regarding the
    DC-3. The DC-3 specifications were shaped by AA.


From nobody Wed Apr  9 21:31:50 2014
Return-Path: <randy@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E45F41A041E for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 21:31:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level: 
X-Spam-Status: No, score=-4.573 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 LRVjjKaPRE4T for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 21:31:44 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id DC08A1A041D for <ietf@ietf.org>; Wed,  9 Apr 2014 21:31:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397104304; x=1428640304; h=message-id:in-reply-to:references:date:to:from:subject: cc:mime-version; bh=bsofvQmMzGJ7iWzBmnV7cf+f1dkdz9rnxDBAcjQRgO0=; b=cFwHKmWE3Cj05U1419n9lLJSennS/zUwvWi8MGFtYFwHHyoBypNijc+z j8frYYsDgX+i5J0PLwfPoUQKtS41K0lgeUW4ozxkTRXfIrJD0EJMsh6eM 3jjAw8BFzXXZbP8cTAWZPmDz0vC7uQR0a0qVHLB12cGWH7KrajdX0/nhs w=;
X-IronPort-AV: E=McAfee;i="5400,1158,7403"; a="118904087"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by wolverine02.qualcomm.com with ESMTP; 09 Apr 2014 21:31:43 -0700
X-IronPort-AV: E=Sophos;i="4.97,832,1389772800"; d="scan'208";a="659766378"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 09 Apr 2014 21:32:20 -0700
Received: from [99.111.97.136] (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 9 Apr 2014 21:31:43 -0700
Message-ID: <p06240607cf6bce31fb2f@[99.111.97.136]>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E779EED1@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>,<p06240603cf639ebf8c0d@[99.11 1.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>, <p06240601cf6663952ae4@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>,<p 06240605cf6bb14e35f7@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EED1@EXMB01CMS.surrey.ac.uk>
X-Mailer: Eudora for Mac OS X
Date: Wed, 9 Apr 2014 21:28:58 -0700
To: <l.wood@surrey.ac.uk>, <randy@qti.qualcomm.com>, <elwynd@dial.pipex.com>,  <agmalis@gmail.com>
From: Randall Gellens <randy@qti.qualcomm.com>
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea   Efflux Appliances (HTCPCP-TEA)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Random-Sig-Tag: 1.0b28
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vl3OOcIcgvTR8YFlnQ7HHAfFKFM
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 04:31:49 -0000

At 5:07 AM +0100 4/10/14, <l.wood@surrey.ac.uk> wrote:

>  Crypto requires increased processing power, requiring more energy, 
> producing more waste heat.
>
>  So, yes, it is a contributing factor to global warming. Crypto is 
> red or black. It isn't green.

I think you misunderstood me.  I didn't ask if global warming was a 
side-effect of security, I asked if global warming was an intentional 
security effort, as part of the plan to boil the ocean.

>
>  Whatever the sun does in terms of output (e.g. Maunder minimum) 
> dwarfs this and many other man-made contributing factors, of course.
>
>  Lloyd Wood
>  http://about.me/lloydwood
>  ________________________________________
>  From: Randall Gellens [randy@qti.qualcomm.com]
>  Sent: 10 April 2014 03:24
>  To: Wood L  Dr (Electronic Eng); randy@qti.qualcomm.com; 
> elwynd@dial.pipex.com; agmalis@gmail.com
>  Cc: ietf@ietf.org
>  Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol 
> for Tea  Efflux Appliances (HTCPCP-TEA)
>
>  At 3:05 AM +0100 4/6/14, <l.wood@surrey.ac.uk> wrote:
>
>>   Always boil the water first. This is in line
>>   with best security practice, which attempts
>>   to boil the ocean.
>
>  So global warming is a security effort?
>
>  --
>  Randall Gellens
>  Opinions are personal;    facts are suspect;    I speak for myself only
>  -------------- Randomly selected tag: ---------------
>  It was the first airplane . . . that could make money just by
>  hauling passengers.
>      --C. R. Smith, president of American Airlines, regarding the
>      DC-3. The DC-3 specifications were shaped by AA.


-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Few ideas are really bad.  Most are either pre- or post-mature.
                                                   --Jon Postel


From nobody Wed Apr  9 21:42:30 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29C671A00A7 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 21:42:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 Acg2ddyJ1KAx for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 21:42:26 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.145]) by ietfa.amsl.com (Postfix) with ESMTP id 9A56F1A00A3 for <ietf@ietf.org>; Wed,  9 Apr 2014 21:42:25 -0700 (PDT)
Received: from [85.158.136.51:27241] by server-9.bemta-5.messagelabs.com id B7/77-04350-03126435; Thu, 10 Apr 2014 04:42:24 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-49.messagelabs.com!1397104943!22838420!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1902 invoked from network); 10 Apr 2014 04:42:23 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-8.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 10 Apr 2014 04:42:23 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.150]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 10 Apr 2014 05:42:23 +0100
From: <l.wood@surrey.ac.uk>
To: <randy@qti.qualcomm.com>, <elwynd@dial.pipex.com>, <agmalis@gmail.com>
Date: Thu, 10 Apr 2014 05:40:37 +0100
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Topic: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)
Thread-Index: Ac9UdctEn8TROBrURA+ug7kkDJcTSwAATlj6
Message-ID: <290E20B455C66743BE178C5C84F1240847E779EED2@EXMB01CMS.surrey.ac.uk>
References: <20140401220040.F06667FC394@rfc-editor.org> <CAA=duU2cV0XLctSBeeW8OtXnCSYDGeWJUyv_uGT25V-4N+J8EA@mail.gmail.com> <1396395466.15324.6860.camel@mightyatom>,<p06240603cf639ebf8c0d@[99.11 1.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC0@EXMB01CMS.surrey.ac.uk>, <p06240601cf6663952ae4@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EEC1@EXMB01CMS.surrey.ac.uk>,<p 06240605cf6bb14e35f7@[99.111.97.136]> <290E20B455C66743BE178C5C84F1240847E779EED1@EXMB01CMS.surrey.ac.uk>, <p06240607cf6bce31fb2f@[99.111.97.136]>
In-Reply-To: <p06240607cf6bce31fb2f@[99.111.97.136]>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ukFC2MTRELEhVQ2X0gh26LVPPLI
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 04:42:28 -0000

http://www.investopedia.com/terms/b/boil-the-ocean.asp

In my experience, side-effects of security are generally
unintentional - to be intentional, they'd first have to be
understood by the security people, and of any interest to
them.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Randall Gellens [randy@qti.qualcomm.com]
Sent: 10 April 2014 05:28
To: Wood L  Dr (Electronic Eng); randy@qti.qualcomm.com; elwynd@dial.pipex.=
com; agmalis@gmail.com
Cc: ietf@ietf.org
Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol for Tea=
   Efflux Appliances (HTCPCP-TEA)

At 5:07 AM +0100 4/10/14, <l.wood@surrey.ac.uk> wrote:

>  Crypto requires increased processing power, requiring more energy,
> producing more waste heat.
>
>  So, yes, it is a contributing factor to global warming. Crypto is
> red or black. It isn't green.

I think you misunderstood me.  I didn't ask if global warming was a
side-effect of security, I asked if global warming was an intentional
security effort, as part of the plan to boil the ocean.

>
>  Whatever the sun does in terms of output (e.g. Maunder minimum)
> dwarfs this and many other man-made contributing factors, of course.
>
>  Lloyd Wood
>  http://about.me/lloydwood
>  ________________________________________
>  From: Randall Gellens [randy@qti.qualcomm.com]
>  Sent: 10 April 2014 03:24
>  To: Wood L  Dr (Electronic Eng); randy@qti.qualcomm.com;
> elwynd@dial.pipex.com; agmalis@gmail.com
>  Cc: ietf@ietf.org
>  Subject: RE: RFC 7168 on The Hyper Text Coffee Pot Control Protocol
> for Tea  Efflux Appliances (HTCPCP-TEA)
>
>  At 3:05 AM +0100 4/6/14, <l.wood@surrey.ac.uk> wrote:
>
>>   Always boil the water first. This is in line
>>   with best security practice, which attempts
>>   to boil the ocean.
>
>  So global warming is a security effort?
>
>  --
>  Randall Gellens
>  Opinions are personal;    facts are suspect;    I speak for myself only
>  -------------- Randomly selected tag: ---------------
>  It was the first airplane . . . that could make money just by
>  hauling passengers.
>      --C. R. Smith, president of American Airlines, regarding the
>      DC-3. The DC-3 specifications were shaped by AA.


--
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Few ideas are really bad.  Most are either pre- or post-mature.
                                                   --Jon Postel=


From nobody Thu Apr 10 01:57:38 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C47D01A0169 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 01:57:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 qAGRitz3dq2y for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 01:57:32 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF251A0049 for <ietf@ietf.org>; Thu, 10 Apr 2014 01:57:32 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.146.71]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3A8vJcI023154 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Apr 2014 01:57:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397120251; bh=a38RaOkKpbfMgHgEPZBli9vBtjFgf72giYdlQBh+q58=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4cksBX3Sa0dl8+lajqrHxXKPuUP8aOo0hI4J5i4e8VPBDKBUu0RiG0CMRzn4EjMYP K9a7jqgvK8CgmBXilXNHxiN1f8Dy8D1Y62eGYjjFHPv1wWMJ4kOktN23/qb3zY6LkO zH1BnOlJY1akabcmXB3Hmg7F/jTP0J/XZqh/XFKA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397120251; i=@elandsys.com; bh=a38RaOkKpbfMgHgEPZBli9vBtjFgf72giYdlQBh+q58=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Uuc2T/0mZAhVCeOJI8H0JY6XhE2B0p/u4+NkoK2YNk5UZs7+JjUx1CUabfDqVjom9 b0b51GapB854QPUxczQXFo7uubIhFRG1V5vTUx0D51ywdKxqEqVu5LdywoHSeyX9Iz VxqnDH7Q5XWHqavF0pco5zkpjDVHdw1SlEZ0PH/Q=
Message-Id: <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Apr 2014 01:54:16 -0700
To: Jari Arkko <jari.arkko@piuha.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
In-Reply-To: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/spMPe9_o4yrNEnWTuB30eMf802s
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 08:57:36 -0000

Hi Jari,

I sent a message to the IESG yesterday (see 
http://www.ietf.org/mail-archive/web/ietf/current/msg87189.html 
).  As the wasn't any response from the IESG there might be a 
perception that the IESG isn't responsive to concerns when the matter 
affects OpenSSH code.  For what it is worth OpenSSH is widely 
deployed.  It is easy to assess whether what I wrote is true by 
looking at a few open source operating systems.

It has been stated that:

   'To break the deadlock, document authors often choose some "seemingly
    unused" code points, often by selecting the next available value from
    the registry; this is problematic because these may turn out to be
    different from those later assigned by IANA.  To make this problem
    worse, "pre-RFC" implementations are often developed and deployed
    based on these code point selections.'

I did not choose a "seemingly unused" code point (see 
draft-moonesamy-sshfp-ed25519-01).  I followed what the IETF 
documentation says and the advice I have been given.  I requested 
feedback from CFRG even though it is not an IETF Working Group.  I 
could have objected to that given what has been said in the news.

According to RFC 2026:

   "If an individual should disagree with an action taken by the IESG in
    this process, that person should first discuss the issue with the
    ISEG Chair."

The problem is that the IESG has not taken any action.  In my opinion 
it is constructive to be open to discussion.

Regards,
S. Moonesamy


From nobody Thu Apr 10 02:10:24 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6314B1A0198 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 02:10:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 dZcMdGA1-a0x for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 02:10:21 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 3843A1A031B for <ietf@ietf.org>; Thu, 10 Apr 2014 02:10:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 58EE1BEB1; Thu, 10 Apr 2014 10:10:19 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XD2BdxPslCIe; Thu, 10 Apr 2014 10:10:19 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 36630BE79; Thu, 10 Apr 2014 10:10:19 +0100 (IST)
Message-ID: <53465FFA.1090602@cs.tcd.ie>
Date: Thu, 10 Apr 2014 10:10:18 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
In-Reply-To: <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LQu2-oJhbrIoLVcaoHBZtcjsQW4
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 09:10:23 -0000

Hi SM,

On 04/10/2014 09:54 AM, S Moonesamy wrote:
> Hi Jari,
> 
> I sent a message to the IESG yesterday (see
> http://www.ietf.org/mail-archive/web/ietf/current/msg87189.html ).  

You ask in that message "why the delay?"

As I told you off list before you posted that, we are hoping that
CFRG will organise a virtual interim meeting for which the main
topic of discussion will be whether CFRG's advise the IETF that
some set of new curves (including that required by your draft)
are good enough for use in IETF standards. That question was
raised at the CFRG session in London but there were not enough
people in the room who felt they knew enough about the topic to
be sure. Aside from you the TLS wg are also waiting on that
answer. I hope the CFRG virtual interim will happen in the next
few weeks. That is the reason for delay.

If that CFRG meeting doesn't happen soon, (but I expect it
will) then I will organise some other way to get an answer on
this topic, but better if we can get folks who do crypto for
a living to give us an answer if we can.

Regards,
Stephen.

PS: I don't really know what the rest of you mail relates to
but feel free to explain off list if it needs a response.

> As
> the wasn't any response from the IESG there might be a perception that
> the IESG isn't responsive to concerns when the matter affects OpenSSH
> code.  For what it is worth OpenSSH is widely deployed.  It is easy to
> assess whether what I wrote is true by looking at a few open source
> operating systems.
> 
> It has been stated that:
> 
>   'To break the deadlock, document authors often choose some "seemingly
>    unused" code points, often by selecting the next available value from
>    the registry; this is problematic because these may turn out to be
>    different from those later assigned by IANA.  To make this problem
>    worse, "pre-RFC" implementations are often developed and deployed
>    based on these code point selections.'
> 
> I did not choose a "seemingly unused" code point (see
> draft-moonesamy-sshfp-ed25519-01).  I followed what the IETF
> documentation says and the advice I have been given.  I requested
> feedback from CFRG even though it is not an IETF Working Group.  I could
> have objected to that given what has been said in the news.
> 
> According to RFC 2026:
> 
>   "If an individual should disagree with an action taken by the IESG in
>    this process, that person should first discuss the issue with the
>    ISEG Chair."
> 
> The problem is that the IESG has not taken any action.  In my opinion it
> is constructive to be open to discussion.
> 
> Regards,
> S. Moonesamy
> 
> 
> 


From nobody Thu Apr 10 03:06:00 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 428061A0675 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 WaIrGSAJSrEB for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:05:53 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 25DC31A066A for <ietf@ietf.org>; Thu, 10 Apr 2014 03:05:53 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.146.71]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3AA5YsB025887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Apr 2014 03:05:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397124347; bh=9IHwDeZj9eCFkvoYUQxeXHCveAhSGncda/9x8Jn8v04=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=SGqF7BONSKPMCmRrtw5AtQx/sCukX0rArxRDV5LMQ3SO8mZ7pbroCfU569WepjH2G G8zqe2K/6bW0dg1cgBiBB9785w6u7I8pGjGTYTAFp2aMyt92sIV8AHzgdOcn6L6RYZ uTIBvSwlyElD8xU8Y4+yxYeViYS1iC0hpBUdq3bA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397124347; i=@elandsys.com; bh=9IHwDeZj9eCFkvoYUQxeXHCveAhSGncda/9x8Jn8v04=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iMXfzxwJbw9lOV0ZT0tgd0/zq7r3KHrPFYidNuG3k1PGH5C5cemdYnBH5dr7nI2Fn hc2fLvkSuuR3ScSbHyypMB32FBwBznWPrH81vTeUztbxvImWTi75IvYmlUfWhKO2SD k3Wa2/dgyGkTj79sRNBP6ebi0NaafaAZCzUftFtc=
Message-Id: <6.2.5.6.2.20140410022352.0ca49f40@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Apr 2014 02:30:37 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Jari Arkko <jari.arkko@piuha.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
In-Reply-To: <53465FFA.1090602@cs.tcd.ie>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net> <53465FFA.1090602@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OoNRoGTI73mH3F8Ql1M5m884V3Y
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 10:05:58 -0000

Hi Stephen,
At 02:10 10-04-2014, Stephen Farrell wrote:
>You ask in that message "why the delay?"
>
>As I told you off list before you posted that, we are hoping that
>CFRG will organise a virtual interim meeting for which the main
>topic of discussion will be whether CFRG's advise the IETF that
>some set of new curves (including that required by your draft)
>are good enough for use in IETF standards. That question was
>raised at the CFRG session in London but there were not enough
>people in the room who felt they knew enough about the topic to
>be sure. Aside from you the TLS wg are also waiting on that
>answer. I hope the CFRG virtual interim will happen in the next
>few weeks. That is the reason for delay.
>
>If that CFRG meeting doesn't happen soon, (but I expect it
>will) then I will organise some other way to get an answer on
>this topic, but better if we can get folks who do crypto for
>a living to give us an answer if we can.

Thanks for explaining the delay.  I am okay with waiting a few weeks.

Regards,
S. Moonesamy 


From nobody Thu Apr 10 03:15:39 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47DA01A01F3 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 7UBykKqg45kw for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:15:35 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 607781A01E1 for <ietf@ietf.org>; Thu, 10 Apr 2014 03:15:35 -0700 (PDT)
Received: from [188.67.5.132] (188-67-5-132.bb.dnainternet.fi [188.67.5.132]) by p130.piuha.net (Postfix) with ESMTPSA id D2C572CC61; Thu, 10 Apr 2014 13:15:32 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
From: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: iPad Mail (11D167)
In-Reply-To: <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
Date: Thu, 10 Apr 2014 13:12:01 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5CE78BA-5805-4922-9E1A-A30D3B5AA4CA@piuha.net>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uOHYQYU8ZwDgeh5o2VbYFF9eRSY
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 10:15:37 -0000

SM,

SSH is obviously important and I am a long-term OpenSSH user myself :-) And I=
 also happen to believe in timely registration of values in registries, part=
icularly when there is running code.

Anyway, I cannot speak for the IESG yet in this case but please do not take l=
ack of a response to a message sent yesterday as a sign that we do not care :=
-)

I looked at the draft and it seems fine, ready to move forward. I do not per=
sonally have any knowledge about ED25519 and I cannot say whether it is some=
thing that we should be using in IETF standards. Stephen seems to think that=
 waiting a bit to get an opinion from the crypto experts would be useful. Wh=
at is your opinion on that, SM? What about others, do you have an opinion? A=
nd SM, do you have an idea how soon we need an answer for the implementation=
s to usefully employ the allocated number?

Jari


From nobody Thu Apr 10 03:33:21 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22EC81A01CF for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:33:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 CWEn72PeAEeX for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:33:19 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 3840B1A01CE for <ietf@ietf.org>; Thu, 10 Apr 2014 03:33:19 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WYCI6-0002s0-1D; Thu, 10 Apr 2014 10:33:06 +0000
Date: Thu, 10 Apr 2014 19:33:04 +0900
Message-ID: <m2vbuhh3tr.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
In-Reply-To: <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8zTCm0fGEjAZITLvDyyjZCfOTk4
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 10:33:20 -0000

perhaps one day is a bit impatient


From nobody Thu Apr 10 03:36:05 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C93E1A023A for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:36:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 eu7P5wyTFNAU for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:36:02 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id D5C151A01D3 for <ietf@ietf.org>; Thu, 10 Apr 2014 03:36:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 45B3BBEBE; Thu, 10 Apr 2014 11:36:00 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nt2T5-6Pk+Bb; Thu, 10 Apr 2014 11:36:00 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 1E5C4BEB1; Thu, 10 Apr 2014 11:36:00 +0100 (IST)
Message-ID: <5346740F.6060907@cs.tcd.ie>
Date: Thu, 10 Apr 2014 11:35:59 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net> <m2vbuhh3tr.wl%randy@psg.com>
In-Reply-To: <m2vbuhh3tr.wl%randy@psg.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1va7mXXEmdzdh0utNcrBkj9OmFM
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 10:36:03 -0000

On 04/10/2014 11:33 AM, Randy Bush wrote:
> perhaps one day is a bit impatient

To be fair, SM has been asking me about this for a while,
and there has been delay while we're trying to get the
crypto ducks in a crypto row. (...cue jokes about randmoness:-)

S.


From nobody Thu Apr 10 03:49:59 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A294F1A01E8 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:49:57 -0700 (PDT)
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] autolearn=ham
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 H5bvltxdPVIu for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 03:49:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 426881A01D5 for <ietf@ietf.org>; Thu, 10 Apr 2014 03:49:54 -0700 (PDT)
Received: from [10.168.69.12] (pool-71-164-185-121.dllstx.fios.verizon.net [71.164.185.121]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3AAnmws010470 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 10 Apr 2014 03:49:52 -0700
Message-ID: <534676DB.7090002@dcrocker.net>
Date: Thu, 10 Apr 2014 05:47:55 -0500
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: Security for various IETF services
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu>	<534580AF.4080602@dcrocker.net>	<20140409200814.GA15303@thunk.org>	<3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com> <CAKHUCzymXu0TGEYD6dQj9OVhGn2pgE9nPqDG6guV+RS+L8XTow@mail.gmail.com>
In-Reply-To: <CAKHUCzymXu0TGEYD6dQj9OVhGn2pgE9nPqDG6guV+RS+L8XTow@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 10 Apr 2014 03:49:52 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tOyCfRZVLZHtr8ICPE99NGcsjFk
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 10:49:57 -0000

On 4/9/2014 3:36 PM, Dave Cridland wrote:
> DNSSEC, and DANE, allow you to provide a "Domain Validated" public key,
> much like the cheap/free certificates currently available from CAs, but
> more reliably and simply. I think the same level of trust is there
> either way, except that the cheap/free CA certs are very weakly
> validated in practise.


What deployment and use has DANE achieved, so far?


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Thu Apr 10 04:52:02 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A45FC1A0158 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 04:51:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 Df_eEpFhdi6N for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 04:51:52 -0700 (PDT)
Received: from mail-lb0-x235.google.com (mail-lb0-x235.google.com [IPv6:2a00:1450:4010:c04::235]) by ietfa.amsl.com (Postfix) with ESMTP id DC7D91A0212 for <ietf@ietf.org>; Thu, 10 Apr 2014 04:51:51 -0700 (PDT)
Received: by mail-lb0-f181.google.com with SMTP id c11so2171077lbj.40 for <ietf@ietf.org>; Thu, 10 Apr 2014 04:51:50 -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:content-type; bh=1NA+joCUYRJlh8WDjtkDnHAKBB9oB6ukJwNfBKCyX1M=; b=SlWZuKoUn97t5j30hos4lEp3TzAdj/x4BiV/icrrqZQxScdLYOh2NFDWau8TtVC2fE M5oMj1ahyvoNHn0vgKMmOdL9FKHTnRHAosazKghQ4Rtf1C7hc/kxpunIJh30rMNHPM9s BTUcAEWXsg3J3zC1w9AbtVDVVSYC0lkBr3kxZ6iZuPNZCshylObkwXKkFbDNbMozC9Km rTz0GtfvLIkKpIO9Q+d9aRaJDXlsLFSDDQ4qCcFSvkBJCJP/fQ7Xe61zGjV3rcn8L4p3 S2zoYDmpOqZKOTWICo46w0mDyEO+nIz6ymiUrI8aGOv8759e6ucszDX3KnoRdpaARqu3 hgWQ==
MIME-Version: 1.0
X-Received: by 10.152.170.137 with SMTP id am9mr12104337lac.15.1397130710421;  Thu, 10 Apr 2014 04:51:50 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Thu, 10 Apr 2014 04:51:50 -0700 (PDT)
In-Reply-To: <p06240604cf6baa6b989d@99.111.97.136>
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@99.111.97.136> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com> <CAMm+LwgLxR65a1nKmKpqW39_BvgMgAGwBCxAE+eEs-9bnLdv8A@mail.gmail.com> <p06240604cf6baa6b989d@99.111.97.136>
Date: Thu, 10 Apr 2014 07:51:50 -0400
Message-ID: <CAMm+LwhxHi2Wj=L3sCPQgHna=SrQr4rbfh7B8vYfQdoLJUqkng@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Randall Gellens <randy@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TyEK3dNN9gm8mSgSYuqBknuZGMg
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 11:51:57 -0000

On Wed, Apr 9, 2014 at 10:01 PM, Randall Gellens <randy@qti.qualcomm.com> wrote:
> At 9:12 AM -0400 4/9/14, Phillip Hallam-Baker wrote:
>
>>>  To that end, I could imagine a requirement for some kind of roadmap.
>>> "The tools that access the IETF SMTP and HTTP sites use protocols X, Y, and
>>> Z. After <date>, we require them to use Secure X, Secure Y, and Secure Z,
>>> and traffic originated by the IETF sites shall use such protocols."
>>
>>
>>  This sounds like a good idea.
>
>
> To me it sounds like a knee-jerk reaction rather than an assessment of what
> we need to protect and what the costs are of various mechanisms.
>
>
>>  But we currently have a big problem in
>>  that the IETF has two email security standards, not one. And the two
>>  sides don't talk and this has created a stalemate that has blocked
>>  ubiquitous use of either.
>
>
> We actually have a few more email security standards, but regardless, I
> don't think the major barrier to deployment is that there is not a single
> standard.  There are a number of reasons why email end-to-end encryption is
> rarely used, which include the difficulty of managing keys, but it's also
> worth pointing out that end-to-end encrypted email breaks a lot of the
> anti-spam, unless users share their private keys with their mail provider
> (which kind of defeats the point).

As a meta-point, people can disagree with me over whether I have
solved all the problems but I am pretty sure that I already know most
if not all the problems that people come up with after thinking about
the problem for a few minutes. I have been discussing this for quite a
while now and I used to sell S/MIME as a main product for about ten
years. I have discussed the problem with Callas and Zimmerman.

Too much security is a really easy problem to solve: allow people to use less.


There are many reasons why end-to-end is not the only model that a
message layer encryption system should provide. It actually doesn't
break as much anti-spam as is imagined. Content-analysis is not a
powerful anti-spam technique. But there are some situations in which
archiving is required for regulatory reasons.

The end-to-end model should be an option, not a requirement.

I am very comfortable with a model in which 95% of my mail is
encrypted to a key held by my mail provider and the 5% that I consider
to be sensitive is secured under an end-to-end key only I hold and
mail is only accepted under that key from pre-approved senders.


I go into a very full requirements analysis for making secure email work here:

http://www.youtube.com/watch?v=06KyOCtjxLs


The end-to-end model is really not a useful one for security
discussions because the ends of the IP channel are not the same as the
ends of the conversation. The important part is being able to know
where the end-points are so that senders can make a decision on that
basis.

S/MIME and PGP don't actually enforce an end-to-end model. But because
they assume that is all that is wanted they make end-to-end an all or
nothing proposition.

Since my security concerns are a little different to most I would
probably end up with a three tier model in which mail from people I
don't know goes to the Gmail/Postini decryption key, most mail from
most people I have whitelisted goes to a decryption key that is on all
my machines I configure for mail and I also have a key for sensitive
stuff that is only on one or two machines or is in a smart token.

I can make the two tier scheme transparent from a usability point of
view but when we get into three or more tiers it starts to demand more
of users which is why I would not make it default.

-- 
Website: http://hallambaker.com/


From nobody Thu Apr 10 04:57:47 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFEF01A0167 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 04:57:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 W_PWOXN1dAmD for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 04:57:42 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 4501A1A016C for <ietf@ietf.org>; Thu, 10 Apr 2014 04:57:42 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 81572BEB0; Thu, 10 Apr 2014 12:57:40 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NHn4d7fQ99R; Thu, 10 Apr 2014 12:57:40 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 58079BEA0; Thu, 10 Apr 2014 12:57:40 +0100 (IST)
Message-ID: <53468734.4060809@cs.tcd.ie>
Date: Thu, 10 Apr 2014 12:57:40 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>,  Randall Gellens <randy@qti.qualcomm.com>
Subject: Re: Security for various IETF services
References: <533D8A90.60309@cs.tcd.ie> <290E20B455C66743BE178C5C84F1240847E779EEB6@EXMB01CMS.surrey.ac.uk> <p06240601cf639cb2113b@99.111.97.136> <F8AEEDAE-C8BB-4979-8122-1110DFF62770@cisco.com> <CAMm+LwgLxR65a1nKmKpqW39_BvgMgAGwBCxAE+eEs-9bnLdv8A@mail.gmail.com> <p06240604cf6baa6b989d@99.111.97.136> <CAMm+LwhxHi2Wj=L3sCPQgHna=SrQr4rbfh7B8vYfQdoLJUqkng@mail.gmail.com>
In-Reply-To: <CAMm+LwhxHi2Wj=L3sCPQgHna=SrQr4rbfh7B8vYfQdoLJUqkng@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/szpyN0HZuWLfP6FxJaD81jmKOr0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 11:57:45 -0000

Just to note that this has wandered off topic, but is a
fine separate topic. Could be better on saag maybe but
please change the subject if continuing here.

Reason this is a different topic: this is about a new
protocol and is not something that'd be covered by the
proposed iesg statement until much later after it'd
worked out well.

Thanks,
S.

On 04/10/2014 12:51 PM, Phillip Hallam-Baker wrote:
> On Wed, Apr 9, 2014 at 10:01 PM, Randall Gellens <randy@qti.qualcomm.com> wrote:
>> At 9:12 AM -0400 4/9/14, Phillip Hallam-Baker wrote:
>>
>>>>  To that end, I could imagine a requirement for some kind of roadmap.
>>>> "The tools that access the IETF SMTP and HTTP sites use protocols X, Y, and
>>>> Z. After <date>, we require them to use Secure X, Secure Y, and Secure Z,
>>>> and traffic originated by the IETF sites shall use such protocols."
>>>
>>>
>>>  This sounds like a good idea.
>>
>>
>> To me it sounds like a knee-jerk reaction rather than an assessment of what
>> we need to protect and what the costs are of various mechanisms.
>>
>>
>>>  But we currently have a big problem in
>>>  that the IETF has two email security standards, not one. And the two
>>>  sides don't talk and this has created a stalemate that has blocked
>>>  ubiquitous use of either.
>>
>>
>> We actually have a few more email security standards, but regardless, I
>> don't think the major barrier to deployment is that there is not a single
>> standard.  There are a number of reasons why email end-to-end encryption is
>> rarely used, which include the difficulty of managing keys, but it's also
>> worth pointing out that end-to-end encrypted email breaks a lot of the
>> anti-spam, unless users share their private keys with their mail provider
>> (which kind of defeats the point).
> 
> As a meta-point, people can disagree with me over whether I have
> solved all the problems but I am pretty sure that I already know most
> if not all the problems that people come up with after thinking about
> the problem for a few minutes. I have been discussing this for quite a
> while now and I used to sell S/MIME as a main product for about ten
> years. I have discussed the problem with Callas and Zimmerman.
> 
> Too much security is a really easy problem to solve: allow people to use less.
> 
> 
> There are many reasons why end-to-end is not the only model that a
> message layer encryption system should provide. It actually doesn't
> break as much anti-spam as is imagined. Content-analysis is not a
> powerful anti-spam technique. But there are some situations in which
> archiving is required for regulatory reasons.
> 
> The end-to-end model should be an option, not a requirement.
> 
> I am very comfortable with a model in which 95% of my mail is
> encrypted to a key held by my mail provider and the 5% that I consider
> to be sensitive is secured under an end-to-end key only I hold and
> mail is only accepted under that key from pre-approved senders.
> 
> 
> I go into a very full requirements analysis for making secure email work here:
> 
> http://www.youtube.com/watch?v=06KyOCtjxLs
> 
> 
> The end-to-end model is really not a useful one for security
> discussions because the ends of the IP channel are not the same as the
> ends of the conversation. The important part is being able to know
> where the end-points are so that senders can make a decision on that
> basis.
> 
> S/MIME and PGP don't actually enforce an end-to-end model. But because
> they assume that is all that is wanted they make end-to-end an all or
> nothing proposition.
> 
> Since my security concerns are a little different to most I would
> probably end up with a three tier model in which mail from people I
> don't know goes to the Gmail/Postini decryption key, most mail from
> most people I have whitelisted goes to a decryption key that is on all
> my machines I configure for mail and I also have a key for sensitive
> stuff that is only on one or two machines or is in a smart token.
> 
> I can make the two tier scheme transparent from a usability point of
> view but when we get into three or more tiers it starts to demand more
> of users which is why I would not make it default.
> 


From nobody Thu Apr 10 05:15:31 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FD741A0242 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 05:15:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 5byBKnXzDGw5 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 05:15:25 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BC31A01CB for <ietf@ietf.org>; Thu, 10 Apr 2014 05:15:22 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.146.71]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3ACF9GY013066 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 10 Apr 2014 05:15:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397132121; bh=dmwoByV9cnh/d3UopwWQ8dH5N8qBuTA3CLJlZX4guPM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Y0C55zD5dPh4KMH7d+HZlWd2/hiIJqR2K7rfDvgkJ0cq2weUpro+Jg+ptcxf+TBj0 /FeEFUYJf4lFKdjVl5s6oIQZUK/CIdj2OGhCt340YddO/xjgYSTRS746OL3kR4CEMb nL5EY21S/6e00kSvvGbYBV1r7FO4QJs/fY0KtVZw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397132121; i=@elandsys.com; bh=dmwoByV9cnh/d3UopwWQ8dH5N8qBuTA3CLJlZX4guPM=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=F1JhvV5fgq4gKF68vKhiFAs1tmkJlcOm0VU4nV2IXZgMeRPWNHbN/Mdj3VQYw+qXd DZRJR92+rLw+je89F8AUkTpbDhHEOQ+78KL6wCIehopDcqXYUx6NDlnT+VxGpIs88g DchfiyuYEudylmAoUZH1iAmV+t21wLRnnuqknX4c=
Message-Id: <6.2.5.6.2.20140410034359.0bc89d30@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 10 Apr 2014 05:12:46 -0700
To: Jari Arkko <jari.arkko@piuha.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
In-Reply-To: <A5CE78BA-5805-4922-9E1A-A30D3B5AA4CA@piuha.net>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net> <A5CE78BA-5805-4922-9E1A-A30D3B5AA4CA@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dkQikOM0EJuH_xOeEyw9DLsqgG8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 12:15:29 -0000

Hi Jari,
At 03:12 10-04-2014, Jari Arkko wrote:
>SSH is obviously important and I am a long-term OpenSSH user myself 
>:-) And I also happen to believe in timely registration of values in 
>registries, particularly when there is running code.

I am also an OpenSSH user. :-)  I wrote the draft because of the code.

>I looked at the draft and it seems fine, ready to move forward. I do 
>not personally have any knowledge about ED25519 and I cannot say 
>whether it is something that we should be using in IETF standards. 
>Stephen seems to think that waiting a bit to get an opinion from the 
>crypto experts would be useful. What is your opinion on that, SM? 
>What about others, do you have an opinion? And SM, do you have an 
>idea how soon we need an answer for the implementations to usefully 
>employ the allocated number?

The draft is intended as Informational.  I would not argue that what 
is in the draft is an IETF standard.  I suggested to Stephen to start 
the Last Call as it would take a month.  That does not prevent the 
gathering of input from folks who do crypto.

It is usually good to get more opinions from crypto experts.  I did 
some research before writing the draft to determine whether there 
were any concerns.  I did not find anything noteworthy.

 From a code point request perspective a possible outcome would be to 
deny the request.  It is a problem when a registry does not reflect 
what is used in the wild.  I am okay with having disclaimer text in 
the draft (I'll defer to Stephen).  The code was not included in the 
last release (March).  Note that I am not one of the person who gets 
to decide about code release.  I could provide feedback saying, for 
example, that there will be a (IETF) decision about the code point 
request by end of May.

Regards,
S. Moonesamy 


From nobody Thu Apr 10 07:14:22 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86C881A0307 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 07:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.164
X-Spam-Level: 
X-Spam-Status: No, score=-0.164 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
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 k3W9sAaUuM4F for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 07:14:14 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 79CE31A0277 for <ietf@ietf.org>; Thu, 10 Apr 2014 07:14:14 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WYFk4-0004NS-2h; Thu, 10 Apr 2014 14:14:12 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 6FE2C5802B6; Thu, 10 Apr 2014 10:14:06 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1397139246; bh=l6GULf0gWeYNZpLwEJkg4LDymXBu5Jx0XYzzWD+kmm8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XWulVvznUPToSDjUnkdH96Fw1ui5SocyeDKkFJR46nF9DcfbXUHf4HleyO2kItS/S H2hI9sD4VSnZVxbyIQQzVmN5h1QCgT+cZoytysadYEFy81bEXOaoscqiNMUhGad3/s 5kng+mMc9TRpmiELbGMn1ode/pgV+bPaH17f7aqY=
Date: Thu, 10 Apr 2014 10:14:06 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Steve Crocker <steve@shinkuro.com>
Subject: Re: Security for various IETF services
Message-ID: <20140410141406.GF15925@thunk.org>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PSCcUDgCN1iQNpEOXBkbQAIiQ5w
Cc: ietf@ietf.org, David Crocker <dcrocker@bbiw.net>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 14:14:20 -0000

On Wed, Apr 09, 2014 at 04:15:53PM -0400, Steve Crocker wrote:
> My own opinion is related but not identical.  I agree solutions 1
> and 3 are failures; 1 doesnâ€™t provide the trust and 3 doesnâ€™t scale.
> Solution 2 is also problematic because the government tends to
> overreach and there isnâ€™t a single government.
> 
> DNSSEC provides a base platform to build upon.  It doesnâ€™t claim to
> provide the level of trust the CA system tried to provide.  Thatâ€™s a
> key strength, not a weakness.

DNSSEC basically has the same properties as the "race to the bottom
certifying authorities" model, except it's a "race to the bottom of
the DNS registraries" --- and some cases, the same company runs both a
CA and a DNS registry.  "Meet the new boss, same as the old boss"....

So if you're willing to disclaim the amount of trust that the CA
system purports to provide, it's really a question of "IPSEC" vs "TLS"
--- i.e., at which layer of the stack you are applying the protection.

Cheers,

					- Ted


From nobody Thu Apr 10 07:35:37 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 623BB1A01C1 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 07:35:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 xPlcHGC0Ynww for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 07:35:29 -0700 (PDT)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 5C81F1A017D for <ietf@ietf.org>; Thu, 10 Apr 2014 07:35:29 -0700 (PDT)
Received: by mail-la0-f49.google.com with SMTP id mc6so2352959lab.22 for <ietf@ietf.org>; Thu, 10 Apr 2014 07:35: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:content-type; bh=1tblu9NQfNE7YOjLy5oL4J3yMW3exHRwHDxRYZKeDD8=; b=PWPczh9kbFnGZqzYaZKHy7oC9ckPXQym12daulWDDRTOWhANTTZKk/IfevI1Io/5FU 0zYiLLacsSypUSI5jX8tWf+szE5sWrWKxN1tXZfn30bx8uDnBexojWuRAOMwqpsRkB4i EjXChvglVKTUDsjoMlZfcxj3sZNtRLE7HIZ4t4QoV/4u95PqncE/l1hE8FG0rESAV+aE Vhfa63hCf+KLghXsM3juk79dSlwWXCBMchggIHo2F/F/PTuLJE1+eVT2AKnRMttRiM8f E74kGLHvEoAG7CWqLY9wT1mly0oVDNg+sTIQ8a/fsH2S5UvAKkiBJZrxZkH6BK3nlNmU Zm5A==
MIME-Version: 1.0
X-Received: by 10.112.143.99 with SMTP id sd3mr11887850lbb.11.1397140527767; Thu, 10 Apr 2014 07:35:27 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Thu, 10 Apr 2014 07:35:27 -0700 (PDT)
In-Reply-To: <534580AF.4080602@dcrocker.net>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net>
Date: Thu, 10 Apr 2014 10:35:27 -0400
Message-ID: <CAMm+Lwi2bsj9s-h6eyYzJLpbOG8RY2yRmKSssuKoDCA-KAAH2w@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SrXYmZfy25am4jv4m525OPJMIEI
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 14:35:35 -0000

On Wed, Apr 9, 2014 at 1:17 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> On 4/9/2014 10:49 AM, Noel Chiappa wrote:
>>
>>      > the way forward is pretty straightforward: Take the S/MIME message
>>      > format and graft the PGP web of trust and fingerprint trust models
>> onto
>>      > it.
>>
>> I agree wholly with your prefatory observation, and like your suggested
>> solution.
>
>
>
> The interesting premise in the suggestion is that a web of trust key
> management model is useful at Internet scale.
>
> I don't understand why anyone believes that.

Perhaps they believe that I have the solution because they actually
read my proposal where I suggest something very different and back it
with like actual math and an attack model.

The actual code is designed in such a way that people can plug in any
trust model of their choice however.


https://datatracker.ietf.org/doc/draft-hallambaker-prismproof-trust/
http://www.youtube.com/watch?v=PBFnBpWkK8M

There are problems with both the S/MIME and the Web of Trust models
which I discuss in the video presentation.

What I am proposing is to combine features of both trust models and in
addition ground the system in time using Certificate Transparency.
What this means is that a given key can be accredited in both models
simultaneously.


The metric that I apply is the time based work factor for the
attacker. Timestamping documents against an append only notary that is
a member of a federation of such notaries can effectively raise the
work factor for the attacker to infinity after that point in time.


-- 
Website: http://hallambaker.com/


From nobody Thu Apr 10 07:39:03 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 295DB1A01F4 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 07:39:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 oeoNWanqUHoz for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 07:39:01 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 422191A01DC for <ietf@ietf.org>; Thu, 10 Apr 2014 07:39:01 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id A80851B805A for <ietf@ietf.org>; Thu, 10 Apr 2014 07:39:00 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A104119005C; Thu, 10 Apr 2014 07:39:00 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 10 Apr 2014 07:39:00 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Security for various IETF services
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAMm+Lwi2bsj9s-h6eyYzJLpbOG8RY2yRmKSssuKoDCA-KAAH2w@mail.gmail.com>
Date: Thu, 10 Apr 2014 10:38:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <82F536E3-FF79-4C35-A3E3-893A1BDD8449@nominum.com>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <CAMm+Lwi2bsj9s-h6eyYzJLpbOG8RY2yRmKSssuKoDCA-KAAH2w@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iFLncQzAFxXEYKJVdS7AJZ6kjuE
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 14:39:02 -0000

On Apr 10, 2014, at 10:35 AM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:
> There are problems with both the S/MIME and the Web of Trust models
> which I discuss in the video presentation.

Are these documented in the draft?   Because I'm not going to watch the =
video.


From nobody Thu Apr 10 07:57:22 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A2EC61A0224 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 07:57:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 JtsPK09HcKfp for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 07:57:15 -0700 (PDT)
Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 66E4D1A01DC for <ietf@ietf.org>; Thu, 10 Apr 2014 07:57:15 -0700 (PDT)
Received: by mail-lb0-f173.google.com with SMTP id p9so2387385lbv.4 for <ietf@ietf.org>; Thu, 10 Apr 2014 07:57:13 -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:content-type:content-transfer-encoding; bh=aMlXe5673i3+2xr8u44ju/1x8PZjN0B9UN63dS7hTlo=; b=orvu8afYLUoA/xvnb5QIN56p4Fa3bHPTjB9Xnq247zBrs96cLJdPVl+VVpnBy5wkDB hLi2YkRiIiy3P/6t+gxeLmV5Lxs2X/m2ZQuUPo8ReOXAKdMOFbHYWMvQQBfLWursKgRS OcAKbJ00LsJRw8eNA7/8k8uqVYj5+Nq+kvdqXZp++wBli8zk/9bLSv4bjTnoByZmwXuh PhfQTBmrQCR3JWKmRjSN8sAyajEIgTfebyDbN2/dutEIX05uaT9OuSHeqoVIQeqj5vcn lTgQJzBoCxkHDARJ0J9loueFWqaIf2r6wFfoOLAkTE51a4Rwb29/+eL+18Oy5u+5lOan SOUQ==
MIME-Version: 1.0
X-Received: by 10.152.234.229 with SMTP id uh5mr392257lac.64.1397141833683; Thu, 10 Apr 2014 07:57:13 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Thu, 10 Apr 2014 07:57:13 -0700 (PDT)
In-Reply-To: <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com>
Date: Thu, 10 Apr 2014 10:57:13 -0400
Message-ID: <CAMm+Lwj0bUZEwBJ+PW4GW_EYJtQKhxsGzGuFLcrVQQbATQCe6A@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Steve Crocker <steve@shinkuro.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2o6e6yGlJOScJlJGwaMMhZWpeKs
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, Theodore Ts'o <tytso@mit.edu>, IETF Discussion Mailing List <ietf@ietf.org>, David Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 14:57:20 -0000

On Wed, Apr 9, 2014 at 4:15 PM, Steve Crocker <steve@shinkuro.com> wrote:
> My own opinion is related but not identical.  I agree solutions 1 and 3 a=
re failures; 1 doesn=E2=80=99t provide the trust and 3 doesn=E2=80=99t scal=
e.  Solution 2 is also problematic because the government tends to overreac=
h and there isn=E2=80=99t a single government.
>
> DNSSEC provides a base platform to build upon.  It doesn=E2=80=99t claim =
to provide the level of trust the CA system tried to provide.  That=E2=80=
=99s a key strength, not a weakness.
>

I agree as long as you continue to use the indefinite article. DNSSEC
is A platform to build on, so is PGP and so is S/MIME. There is
actually a considerable built out base of S/MIME that is just as large
as PGP and in fact gets a lot more use.

On Monday I was in a room where over half the audience put their hand
up when I asked it they had used encrypted mail that week.


The way forward as I see it is to separate out the trust model
question from the steps necessary to support encryption in the client.
At the very least for development purposes. My prototype is designed
to allow anyone to plug their favorite trust model in as a web
service. So we can share 95% of the code that is the hardest to write
and has to be supported on every platform. We only need to implement
the 5% where the difference lies.


Given this week's Heartbleed news, I think we can stop hearing
conclusions drawn from DigiNotar. No crypto is ever going to be
perfect, get over it. If people want to hold CAs up to a 'zero
tolerance' standard, thats fine. Just make sure you hold OpenSSL up to
the same standard and pull them from the code base as well. And kick
anyone who might have been implicated in an NSA plot out of the IETF.
And stop using all their specs. And.. and., and..

The problem with the CA model for email is that as a CA it is really
difficult for me to actually validate individuals. The best I can do
is to check their government issued ID. Which really does not help me
in a country like Iran. The CA model does give me a lot of leverage if
I am looking to authenticate an institution however.

Web of trust has a scaling problem that I illustrate in the video.
Basically a web of trust with 1000 members that is ten hops away from
me has a work factor of essentially zero as I have no way to tell if
it is genuine or fake. But the curious thing is that if we combine the
two models, the work factor for the attacker increases over the CA
model alone and we get scaling. If there are 50 members of that web of
trust with CA validated certificates with a work factor of X, the web
of trust might have an average work factor approaching 20-30X for a
given cert.




--=20
Website: http://hallambaker.com/


From nobody Thu Apr 10 08:01:07 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC0A1A032A for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 08:01:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 qNuQTUh4HK0l for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 08:00:56 -0700 (PDT)
Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 1C5951A0323 for <ietf@ietf.org>; Thu, 10 Apr 2014 08:00:50 -0700 (PDT)
Received: by mail-la0-f44.google.com with SMTP id c6so2455016lan.3 for <ietf@ietf.org>; Thu, 10 Apr 2014 08:00:49 -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:content-type; bh=V7YUpGAGq2ZXVsQFcwkTp5l++siWCmBvFoUhslbgUbg=; b=NXO5/7sQ1vSc9mGP8iB4PoGJc1meSihB4rMGTLj+H6tpCm5XMc0IkXf+UB5jCbn0wi AGD8jw9gzZ8ugErMMcUWK7dMXehPS51QTTISn4l0L3bszHpn1O+8NnpdHjws9QX5Iibj 9ooKV5vq/c1NDn+7yaJZtEl2bn1G3hc65SUQRriGncLI1lgSfGboaRGYHk23YBkMBmq7 xW2tDZG8rUaMpQjbHtxKPRqNAyr+9t/EHz0tOyehWYrduxVrE5UGDiql/8wjbeyJ+XXd JgQ5JSbU5yVXeR1yeUOu2dShhVK3MEqDMFrQo0nrSl7NvoT/H0kRdkW/IthV3n8zb5UF VaOg==
MIME-Version: 1.0
X-Received: by 10.112.205.35 with SMTP id ld3mr11967046lbc.1.1397142049547; Thu, 10 Apr 2014 08:00:49 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Thu, 10 Apr 2014 08:00:49 -0700 (PDT)
In-Reply-To: <82F536E3-FF79-4C35-A3E3-893A1BDD8449@nominum.com>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <CAMm+Lwi2bsj9s-h6eyYzJLpbOG8RY2yRmKSssuKoDCA-KAAH2w@mail.gmail.com> <82F536E3-FF79-4C35-A3E3-893A1BDD8449@nominum.com>
Date: Thu, 10 Apr 2014 11:00:49 -0400
Message-ID: <CAMm+LwjWKmquXKVJh2D-nGPnXFZeHt48cVDrrsC0pgaqttAqGg@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VipUa9L8OjG3DuafwURyzKG2yzw
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 15:01:01 -0000

On Thu, Apr 10, 2014 at 10:38 AM, Ted Lemon <ted.lemon@nominum.com> wrote:
> On Apr 10, 2014, at 10:35 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>> There are problems with both the S/MIME and the Web of Trust models
>> which I discuss in the video presentation.
>
> Are these documented in the draft?   Because I'm not going to watch the video.

The draft does discuss them but the draft was written 3 months before
the video and my thinking has developed since I started writing code.

I don't plan to update the draft again till the code is finished. At
that point I plan to release a new set of drafts and a video showing
how to use the actual code.



-- 
Website: http://hallambaker.com/


From nobody Thu Apr 10 08:16:36 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4314A1A02F2 for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 10:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_SOFTFAIL=0.665] autolearn=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 NXm2OWVPQLvV for <ietf@ietfa.amsl.com>; Wed,  9 Apr 2014 10:51:01 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id D34251A02E9 for <ietf@ietf.org>; Wed,  9 Apr 2014 10:51:01 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 999C1206D4; Wed,  9 Apr 2014 13:50:41 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1XoMDaZhWoJx; Wed,  9 Apr 2014 13:50:37 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-50-177-27-27.hsd1.ma.comcast.net [50.177.27.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Wed,  9 Apr 2014 13:50:37 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id EC93181B05; Wed,  9 Apr 2014 13:50:54 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: dcrocker@bbiw.net
Subject: Web of trust at Internet Scale
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net>
Date: Wed, 09 Apr 2014 13:50:54 -0400
In-Reply-To: <534580AF.4080602@dcrocker.net> (Dave Crocker's message of "Wed,  09 Apr 2014 12:17:35 -0500")
Message-ID: <tslbnwas875.fsf_-_@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uB_f6PVebaNGmJ4vMbH0M1Ugyls
X-Mailman-Approved-At: Thu, 10 Apr 2014 08:16:34 -0700
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Apr 2014 17:51:04 -0000

>>>>> "Dave" == Dave Crocker <dhc@dcrocker.net> writes:

I have no idea how we got from security for ietf.org services to this.
I hope we're not going to pilot Phil's e-mail trust model in the IETF,
even though I think his work has significant value.

    Dave> The interesting premise in the suggestion is that a web of
    Dave> trust key management model is useful at Internet scale.

    Dave> I don't understand why anyone believes that.

I'm not sure that's actually an implied premise.

I guess bulk mailers do need to communicate with people at Internet
scale.

The rest of us not so much though.
Yes, I can communicate with anyone on the Internet.
However, the set of people that I communicate with is smaller than
that.  The set of people for whom I need trusted communication is even
smaller.

>From my experience in the open-source and product-security communities
(some of the larger web of trust users), web-of-trust tends to work well
when people are communicating with a small enough set of people that
they can make individual authorization decisions but where that set is
drawn from a large enough infrastructure that shared key management is
valuable.

We're seeing something similar as we're putting together the Moonshot
deployment of ABFAB federation.  There's value in some environments  in
having a large trust infrastructure from which I actually trust only
some principals.

I think that the same is likely true for some uses of secure e-mail.


From nobody Thu Apr 10 08:37:35 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D447F1A01DD for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 08:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 TkwLEjFy9c2X for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 08:37:27 -0700 (PDT)
Received: from mail-oa0-x235.google.com (mail-oa0-x235.google.com [IPv6:2607:f8b0:4003:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6E68F1A01DC for <ietf@ietf.org>; Thu, 10 Apr 2014 08:37:27 -0700 (PDT)
Received: by mail-oa0-f53.google.com with SMTP id j17so4625866oag.40 for <ietf@ietf.org>; Thu, 10 Apr 2014 08:37:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=fr2SN5DqVzg/cHCQ7mt7UcgU8R2p8PCjNVjLP23Squ8=; b=b/eApfmoVUe3UJse7MNm2lqP+VhmE/Gca04D3fXSH5EAsAU0BgDDu/XrmwTN1/CVnI Xq3u76q89au3+q6lDNh2Ty+E2elkn+lxxf7XYby5kh1PLDfeGhGmd17yq0y4CA8Tdja6 cvuOEE3S7z/GbwKViAcoHAB3v+m+6vcvS7nLM=
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:content-type; bh=fr2SN5DqVzg/cHCQ7mt7UcgU8R2p8PCjNVjLP23Squ8=; b=Fuk5cne3mQuGRR/M/nBf+6bvKvhUcGDg3oxWmk/vtmM5p/TCJIVU0uFKuwKmeBrUmE OeLxPYfS9TPlMz0By1AJGg4JaMCYreN93JnEFgyyhfu1JoN/8e0G8DZnJ8Fb4vCzjtnY J/WirhjR3wCX7NZblYJlk3+DQ/aIlgKFkviLPqJauodKCU9E/quLOOxfUJBaBJAhBavw zKuP+cafoiVqyrNQhq/Llw5HOV+TU5TGWR6gcR+sPUte0MTiCqiCZoqZ6700BZWWOHBV a/JmKhE6msohix4JEtiYG82TXceP+aKBVLyUG7G6RWlEfZqmhO5LNOvsJ4BHNVeEKMnw 273g==
X-Gm-Message-State: ALoCoQk62i6e+nDmp2oQCrVCoCfDu52Amh5zXknN53tW/HvUywh2eaqy1S5U9HXF1hiSEVeUEtrX
MIME-Version: 1.0
X-Received: by 10.182.18.102 with SMTP id v6mr1494739obd.71.1397144246465; Thu, 10 Apr 2014 08:37:26 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Thu, 10 Apr 2014 08:37:26 -0700 (PDT)
In-Reply-To: <534676DB.7090002@dcrocker.net>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com> <CAKHUCzymXu0TGEYD6dQj9OVhGn2pgE9nPqDG6guV+RS+L8XTow@mail.gmail.com> <534676DB.7090002@dcrocker.net>
Date: Thu, 10 Apr 2014 16:37:26 +0100
Message-ID: <CAKHUCzzS82uk-z120zWqh+B-9i7fdhNX1bJSscXLZkG5wOQb1Q@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Dave Cridland <dave@cridland.net>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c339e682c96f04f6b1feee
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3op43RqQvmBJgbkc0LzV8NVord8
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 15:37:32 -0000

--001a11c339e682c96f04f6b1feee
Content-Type: text/plain; charset=ISO-8859-1

On 10 April 2014 11:47, Dave Crocker <dhc@dcrocker.net> wrote:

> On 4/9/2014 3:36 PM, Dave Cridland wrote:
>
>> DNSSEC, and DANE, allow you to provide a "Domain Validated" public key,
>> much like the cheap/free certificates currently available from CAs, but
>> more reliably and simply. I think the same level of trust is there
>> either way, except that the cheap/free CA certs are very weakly
>> validated in practise.
>>
>
>
> What deployment and use has DANE achieved, so far?
>
>
Like all new security technology it's slow going. In the DANE case, we're
obviously limited by the deployment of DNSSEC itself as well.

Within the XMPP community, which is really the only place I'm able to
track, https://xmpp.net/stats.php will give you the live information, but
to save you looking, the percentages are still pretty low. 83 sites out of
3283, so about 2.5%, support DANE. 6.3% deploy DNSSEC signed SRV records.
We have, on those servers tested, 100% TLS deployment, but only about 49.4%
of those use trusted certificates (there's a lot of CACert.org which are
considered untrusted here).

Given that DANE itself is not yet fully specified for XMPP, and is less
than two years old, I think this is reasonable traction.

These stats are gathered and maintained by Thijs Alkemade's excellent
software, by the way, I don't mean to take any credit for this. I just read
'em.

Dave.

--001a11c339e682c96f04f6b1feee
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
0 April 2014 11:47, Dave Crocker <span dir=3D"ltr">&lt;<a href=3D"mailto:dh=
c@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
<div class=3D"">On 4/9/2014 3:36 PM, Dave Cridland wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
DNSSEC, and DANE, allow you to provide a &quot;Domain Validated&quot; publi=
c key,<br>
much like the cheap/free certificates currently available from CAs, but<br>
more reliably and simply. I think the same level of trust is there<br>
either way, except that the cheap/free CA certs are very weakly<br>
validated in practise.<br>
</blockquote>
<br>
<br></div>
What deployment and use has DANE achieved, so far?<div class=3D"HOEnZb"><di=
v class=3D"h5"><br></div></div></blockquote><div><br></div><div>Like all ne=
w security technology it&#39;s slow going. In the DANE case, we&#39;re obvi=
ously limited by the deployment of DNSSEC itself as well.<br>
</div><div><br></div><div>Within the XMPP community, which is really the on=
ly place I&#39;m able to track, <a href=3D"https://xmpp.net/stats.php">http=
s://xmpp.net/stats.php</a> will give you the live information, but to save =
you looking, the percentages are still pretty low. 83 sites out of 3283, so=
 about 2.5%, support DANE. 6.3% deploy DNSSEC signed SRV records. We have, =
on those servers tested, 100% TLS deployment, but only about 49.4% of those=
 use trusted certificates (there&#39;s a lot of CACert.org which are consid=
ered untrusted here).</div>
<div><br></div><div>Given that DANE itself is not yet fully specified for X=
MPP, and is less than two years old, I think this is reasonable traction.</=
div><div><br></div><div>These stats are gathered and maintained by Thijs Al=
kemade&#39;s excellent software, by the way, I don&#39;t mean to take any c=
redit for this. I just read &#39;em.</div>
<div><br></div><div>Dave.</div></div></div></div>

--001a11c339e682c96f04f6b1feee--


From nobody Thu Apr 10 11:08:38 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD68C1A02FA for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 11:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 iW7h4tEXAWsJ for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 11:08:33 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 8A4BC1A02C2 for <ietf@ietf.org>; Thu, 10 Apr 2014 11:08:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 8B5022CCBE; Thu, 10 Apr 2014 21:08:31 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vqBqdxs_ADnV; Thu, 10 Apr 2014 21:08:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E30292CC61; Thu, 10 Apr 2014 21:08:30 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <6.2.5.6.2.20140410034359.0bc89d30@elandnews.com>
Date: Thu, 10 Apr 2014 21:08:30 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <E8D78AA7-1BDB-4A35-8773-2513880EFB4C@piuha.net>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net> <A5CE78BA-5805-4922-9E1A-A30D3B5AA4CA@piuha.net> <6.2.5.6.2.20140410034359.0bc89d30@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D3Erazb77fGkoV2DPBpzabdMRAk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 18:08:35 -0000

> I suggested to Stephen to start the Last Call as it would take a =
month.  That does not prevent the gathering of input from folks who do =
crypto.

FWIW, I would be fine with this.

Jari


From nobody Thu Apr 10 14:34:55 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2648C1A01BA for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 14:34:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 Eb30crElXe25 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 14:34:48 -0700 (PDT)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com [IPv6:2607:f8b0:4003:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id ACAA81A0073 for <ietf@ietf.org>; Thu, 10 Apr 2014 14:34:48 -0700 (PDT)
Received: by mail-ob0-f172.google.com with SMTP id wm4so5132230obc.3 for <ietf@ietf.org>; Thu, 10 Apr 2014 14:34:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=grZxw5ma3bXKfgTknJhnZDANyp4kuLyFNo3uW+AeqRo=; b=SZX9jq1DlMjwdOptLydTlA1ECm/o14Qip9NdfTrtWYmSDpoUR6uBDVBCGmOik0G6wZ 720SBfyehpHGgRLMJj6n0uvuBwKgqDw1U1OL07ykyPsOe/gRHcVl6f+7CoDGE6/i8r0E XQrJhC2gQKTZ0QqN8fQlgtVHKDMW2F99wMVvc=
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:content-type; bh=grZxw5ma3bXKfgTknJhnZDANyp4kuLyFNo3uW+AeqRo=; b=UKM6xcqNp1li2KjIOi73Y0scuqlqWCzdvBjbC/hXcz2Vz8NXcmsHUNDJj/O7qzWedA F1RbeEbmiWug/jHT1qqETzxos6p2fMLvz6YXTIX1SN9Wfo0R+qOWNaKZczZvsnrwhJEY xcuRgKT9N7nNy+4YIiJJoEVCDYkdECr0lqJkS3e1Ge/AtyhUWLI/il1L4x6tsmdqS0X5 wSnyh94JWN8Z6GvZY5u9XbpRk+LzjKjVptwCn7ejaajsLqx3CZyvYgyR2/YQ4vNxIU0I yrk6pSIMFjYIAjBdya1bbTXBXfwrUTYySetk9P7dRrbyPAJFoSvrdOS9iMbiGnpnXEux tmRQ==
X-Gm-Message-State: ALoCoQlBdvGeIUX2dg2JfyNCrydNQKLNwzkvMWkTTFVRuepcrgywfOJr2nC0Xyt1YxIdSVdYd2W+
MIME-Version: 1.0
X-Received: by 10.60.157.202 with SMTP id wo10mr4074860oeb.9.1397165687491; Thu, 10 Apr 2014 14:34:47 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Thu, 10 Apr 2014 14:34:47 -0700 (PDT)
In-Reply-To: <CAKHUCzzS82uk-z120zWqh+B-9i7fdhNX1bJSscXLZkG5wOQb1Q@mail.gmail.com>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com> <CAKHUCzymXu0TGEYD6dQj9OVhGn2pgE9nPqDG6guV+RS+L8XTow@mail.gmail.com> <534676DB.7090002@dcrocker.net> <CAKHUCzzS82uk-z120zWqh+B-9i7fdhNX1bJSscXLZkG5wOQb1Q@mail.gmail.com>
Date: Thu, 10 Apr 2014 22:34:47 +0100
Message-ID: <CAKHUCzzxu-RQyMMEtXRxmgu6UHy7q9j-DPa2S3mZ9-_Efk9bRQ@mail.gmail.com>
Subject: Re: Security for various IETF services
From: Dave Cridland <dave@cridland.net>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7bd6c5e87ee44b04f6b6fccc
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hHzMWuSaWAwlvC1he7dJCCYZJlI
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2014 21:34:53 -0000

--047d7bd6c5e87ee44b04f6b6fccc
Content-Type: text/plain; charset=ISO-8859-1

On 10 April 2014 16:37, Dave Cridland <dave@cridland.net> wrote:

> On 10 April 2014 11:47, Dave Crocker <dhc@dcrocker.net> wrote:
>
>> On 4/9/2014 3:36 PM, Dave Cridland wrote:
>>
>>> DNSSEC, and DANE, allow you to provide a "Domain Validated" public key,
>>> much like the cheap/free certificates currently available from CAs, but
>>> more reliably and simply. I think the same level of trust is there
>>> either way, except that the cheap/free CA certs are very weakly
>>> validated in practise.
>>>
>>
>>
>> What deployment and use has DANE achieved, so far?
>>
>>
> Like all new security technology it's slow going. In the DANE case, we're
> obviously limited by the deployment of DNSSEC itself as well.
>
> Within the XMPP community, which is really the only place I'm able to
> track, https://xmpp.net/stats.php will
>

not, because I'm an idiot who didn't check the URI he typed, but
https://xmpp.net/reports.php will


> give you the live information, but to save you looking, the percentages
> are still pretty low. 83 sites out of 3283, so about 2.5%, support DANE.
> 6.3% deploy DNSSEC signed SRV records. We have, on those servers tested,
> 100% TLS deployment, but only about 49.4% of those use trusted certificates
> (there's a lot of CACert.org which are considered untrusted here).
>
> Given that DANE itself is not yet fully specified for XMPP, and is less
> than two years old, I think this is reasonable traction.
>
> These stats are gathered and maintained by Thijs Alkemade's excellent
> software, by the way, I don't mean to take any credit for this. I just read
> 'em.
>
> Dave.
>

--047d7bd6c5e87ee44b04f6b6fccc
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
0 April 2014 16:37, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"mailto:d=
ave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
 class=3D"">On 10 April 2014 11:47, Dave Crocker <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;<=
/span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div>On 4/9/2014 3:36 PM, Dave Cridland wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
DNSSEC, and DANE, allow you to provide a &quot;Domain Validated&quot; publi=
c key,<br>
much like the cheap/free certificates currently available from CAs, but<br>
more reliably and simply. I think the same level of trust is there<br>
either way, except that the cheap/free CA certs are very weakly<br>
validated in practise.<br>
</blockquote>
<br>
<br></div>
What deployment and use has DANE achieved, so far?<div><div><br></div></div=
></blockquote><div><br></div></div><div>Like all new security technology it=
&#39;s slow going. In the DANE case, we&#39;re obviously limited by the dep=
loyment of DNSSEC itself as well.<br>

</div><div><br></div><div>Within the XMPP community, which is really the on=
ly place I&#39;m able to track, <a href=3D"https://xmpp.net/stats.php" targ=
et=3D"_blank">https://xmpp.net/stats.php</a> will </div></div></div></div>
</blockquote><div><br></div><div>not, because I&#39;m an idiot who didn&#39=
;t check the URI he typed, but <a href=3D"https://xmpp.net/reports.php">htt=
ps://xmpp.net/reports.php</a> will</div><div>=A0</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
>give you the live information, but to save you looking, the percentages ar=
e still pretty low. 83 sites out of 3283, so about 2.5%, support DANE. 6.3%=
 deploy DNSSEC signed SRV records. We have, on those servers tested, 100% T=
LS deployment, but only about 49.4% of those use trusted certificates (ther=
e&#39;s a lot of CACert.org which are considered untrusted here).</div>

<div><br></div><div>Given that DANE itself is not yet fully specified for X=
MPP, and is less than two years old, I think this is reasonable traction.</=
div><div><br></div><div>These stats are gathered and maintained by Thijs Al=
kemade&#39;s excellent software, by the way, I don&#39;t mean to take any c=
redit for this. I just read &#39;em.</div>
<span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div><div>Dave.</div></font></span></div></div></div>
</blockquote></div><br></div></div>

--047d7bd6c5e87ee44b04f6b6fccc--


From nobody Thu Apr 10 17:33:01 2014
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DFB21A03AA for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 17:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.873
X-Spam-Level: 
X-Spam-Status: No, score=-3.873 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 TN7YyNiaO2R4 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 17:32:42 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) by ietfa.amsl.com (Postfix) with ESMTP id 9DF591A038A for <ietf@ietf.org>; Thu, 10 Apr 2014 17:32:41 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP id 915AC34941D; Fri, 11 Apr 2014 00:32:36 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id AAC7E160066; Fri, 11 Apr 2014 00:34:21 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 75E92160047; Fri, 11 Apr 2014 00:34:21 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id F1A171365D59; Fri, 11 Apr 2014 10:32:31 +1000 (EST)
To: Theodore Ts'o <tytso@mit.edu>
From: Mark Andrews <marka@isc.org>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com> <20140410141406.GF15925@thunk.org>
Subject: Re: Security for various IETF services
In-reply-to: Your message of "Thu, 10 Apr 2014 10:14:06 -0400." <20140410141406.GF15925@thunk.org>
Date: Fri, 11 Apr 2014 10:32:31 +1000
Message-Id: <20140411003231.F1A171365D59@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oknewnk4jWTYAoWCiw1-08mOIic
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org, David Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 00:32:49 -0000

In message <20140410141406.GF15925@thunk.org>, Theodore Ts'o writes:
> On Wed, Apr 09, 2014 at 04:15:53PM -0400, Steve Crocker wrote:
> > My own opinion is related but not identical.  I agree solutions 1
> > and 3 are failures; 1 doesnâ€™t provide the trust and 3 doesnâ€™t scale.
> > Solution 2 is also problematic because the government tends to
> > overreach and there isnâ€™t a single government.
> > 
> > DNSSEC provides a base platform to build upon.  It doesnâ€™t claim to
> > provide the level of trust the CA system tried to provide.  Thatâ€™s a
> > key strength, not a weakness.
> 
> DNSSEC basically has the same properties as the "race to the bottom
> certifying authorities" model, except it's a "race to the bottom of
> the DNS registraries" --- and some cases, the same company runs both a
> CA and a DNS registry.  "Meet the new boss, same as the old boss"....

No quite the same.  A CA could issue a cert without any checking
for any domain.  Here you need to be the registrar of record to add
records to the registry.  Also a registry can only add records for
the namespace it manages not any arbitary name.

So to get a bad DS added you need to be a corrupt registry or a
corrupt employee of registry or you need to compromise the registrants
credentials or you need to succeed in transfering the zone to you.

The registry can provide some protection for some of these threats.

This is a smaller attack surface than the plain CA attack surface.

> So if you're willing to disclaim the amount of trust that the CA
> system purports to provide, it's really a question of "IPSEC" vs "TLS"
> --- i.e., at which layer of the stack you are applying the protection.
> 
> Cheers,
> 
> 					- Ted
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Apr 10 17:57:42 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C97911A03A4 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 17:57:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.063
X-Spam-Level: 
X-Spam-Status: No, score=-2.063 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
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 2LoT-bhaHY2O for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 17:57:29 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 74E0D1A0258 for <ietf@ietf.org>; Thu, 10 Apr 2014 17:57:18 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WYPmL-0007SU-SV; Fri, 11 Apr 2014 00:57:13 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 396AD5802B6; Thu, 10 Apr 2014 20:57:12 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1397177832; bh=gRV2EQLXyPwCxmph9mmxLe3OlHydJOsg7SAPAuaR3bc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mqF5SNeBXQcomigQzD9IT5rV4nTvBZUwnBsUmQS/9/xSwLnrQFWpPFz/qgM4TMFHZ Vx8THLRmvesK09v9E2vCNOBWlskH2ogPTvRiUmILuA5IClj+wTG/F2ppfHR3G8iLZ3 fZ5n/JvvSxQ5kIgmWQB7vNl0v89w8+o/R24kkFmU=
Date: Thu, 10 Apr 2014 20:57:12 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Mark Andrews <marka@isc.org>
Subject: Re: Security for various IETF services
Message-ID: <20140411005712.GA29956@thunk.org>
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com> <20140410141406.GF15925@thunk.org> <20140411003231.F1A171365D59@rock.dv.isc.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140411003231.F1A171365D59@rock.dv.isc.org>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/snK2WazI4qU0EBlJlW_-agF-AaM
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org, David Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 00:57:38 -0000

On Fri, Apr 11, 2014 at 10:32:31AM +1000, Mark Andrews wrote:
> No quite the same.  A CA could issue a cert without any checking
> for any domain.  Here you need to be the registrar of record to add
> records to the registry.  Also a registry can only add records for
> the namespace it manages not any arbitary name.
> 
> So to get a bad DS added you need to be a corrupt registry or a
> corrupt employee of registry or you need to compromise the registrants
> credentials or you need to succeed in transfering the zone to you.

Or you have to be the corrupt registry operator or an employee for the
registry operator (i.e., Verisign for the .com domain)....

    	 	       		    	- Ted


From nobody Thu Apr 10 21:54:11 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD40E1A0280 for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 21:54:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MANGLED_TOOL=2.3, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 wQLmy1gFZyFX for <ietf@ietfa.amsl.com>; Thu, 10 Apr 2014 21:54:04 -0700 (PDT)
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by ietfa.amsl.com (Postfix) with ESMTP id 17AC71A028F for <ietf@ietf.org>; Thu, 10 Apr 2014 21:54:04 -0700 (PDT)
Received: from /spool/local by e33.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Thu, 10 Apr 2014 22:54:02 -0600
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 10 Apr 2014 22:54:01 -0600
Received: from b03cxnp08028.gho.boulder.ibm.com (b03cxnp08028.gho.boulder.ibm.com [9.17.130.20]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 42CC219D8039 for <ietf@ietf.org>; Thu, 10 Apr 2014 22:53:56 -0600 (MDT)
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by b03cxnp08028.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s3B4rqTN7799276 for <ietf@ietf.org>; Fri, 11 Apr 2014 06:54:00 +0200
Received: from d03av02.boulder.ibm.com (localhost [127.0.0.1]) by d03av02.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s3B4rR3s014997 for <ietf@ietf.org>; Thu, 10 Apr 2014 22:53:27 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av02.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s3B4rRQS014485 for <ietf@ietf.org>; Thu, 10 Apr 2014 22:53:27 -0600
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s3B4r2HO007291 for <ietf@ietf.org>; Fri, 11 Apr 2014 00:53:02 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s3B4r2Jt007243 for ietf@ietf.org; Fri, 11 Apr 2014 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201404110453.s3B4r2Jt007243@rotala.raleigh.ibm.com>
Date: Fri, 11 Apr 2014 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14041104-0928-0000-0000-0000011542B2
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kGwVoWk37D2uGa-lGpMVejEHEUw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 04:54:10 -0000

Total of 151 messages in the last 7 days.
 
script run at: Fri Apr 11 00:53:02 EDT 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 11.26% |   17 |  9.86% |   134906 | l.wood@surrey.ac.uk
  5.96% |    9 |  4.59% |    62759 | sm+ietf@elandsys.com
  5.30% |    8 |  4.61% |    63070 | stephen.farrell@cs.tcd.ie
  4.64% |    7 |  4.69% |    64230 | johnl@taugh.com
  4.64% |    7 |  4.28% |    58603 | stbryant@cisco.com
  0.66% |    1 |  8.01% |   109605 | serrhini@mail.ru
  3.97% |    6 |  4.49% |    61372 | hsantos@isdg.net
  3.97% |    6 |  2.72% |    37195 | ted.lemon@nominum.com
  3.31% |    5 |  3.15% |    43114 | rwfranks@acm.org
  3.31% |    5 |  3.14% |    43018 | rpelletier@isoc.org
  3.31% |    5 |  2.65% |    36224 | randy@qti.qualcomm.com
  3.31% |    5 |  2.54% |    34811 | john-ietf@jck.com
  1.32% |    2 |  4.40% |    60268 | david.black@emc.com
  1.32% |    2 |  3.79% |    51787 | d3e3e3@gmail.com
  2.65% |    4 |  1.75% |    23929 | dhc@dcrocker.net
  1.99% |    3 |  1.96% |    26802 | hallam@gmail.com
  1.99% |    3 |  1.67% |    22857 | abdussalambaryun@gmail.com
  1.99% |    3 |  1.64% |    22430 | robbat2@gentoo.org
  1.99% |    3 |  1.40% |    19165 | listsebby@me.com
  1.32% |    2 |  1.92% |    26324 | tbray@textuality.com
  1.99% |    3 |  1.21% |    16544 | jari.arkko@piuha.net
  1.32% |    2 |  1.74% |    23806 | ynir.ietf@gmail.com
  1.32% |    2 |  1.63% |    22322 | dave@cridland.net
  1.32% |    2 |  1.31% |    17930 | daedulus@btconnect.com
  1.32% |    2 |  1.15% |    15793 | brian.e.carpenter@gmail.com
  1.32% |    2 |  1.10% |    15083 | tytso@mit.edu
  1.32% |    2 |  1.09% |    14876 | pranesh@cis-india.org
  1.32% |    2 |  1.00% |    13649 | dwm@xpasc.com
  1.32% |    2 |  0.98% |    13455 | ned+ietf@mauve.mrochek.com
  1.32% |    2 |  0.85% |    11628 | chair@ietf.org
  1.32% |    2 |  0.70% |     9553 | randy@psg.com
  0.66% |    1 |  0.87% |    11887 | ietf@trammell.ch
  0.66% |    1 |  0.70% |     9521 | alex@chilenetworks.com
  0.66% |    1 |  0.69% |     9496 | narten@us.ibm.com
  0.66% |    1 |  0.69% |     9419 | matthew.kaufman@skype.net
  0.66% |    1 |  0.67% |     9148 | steve@shinkuro.com
  0.66% |    1 |  0.66% |     8972 | eric.gray@ericsson.com
  0.66% |    1 |  0.62% |     8490 | rgd.ietf@gmail.com
  0.66% |    1 |  0.59% |     8104 | cdel@firsthand.net
  0.66% |    1 |  0.57% |     7789 | mfidelman@meetinghouse.net
  0.66% |    1 |  0.56% |     7654 | spencerdawkins.ietf@gmail.com
  0.66% |    1 |  0.56% |     7645 | peter@akayla.com
  0.66% |    1 |  0.54% |     7452 | scott.brim@gmail.com
  0.66% |    1 |  0.53% |     7276 | john@jck.com
  0.66% |    1 |  0.53% |     7225 | ray.bellis@nominet.org.uk
  0.66% |    1 |  0.52% |     7169 | marka@isc.org
  0.66% |    1 |  0.51% |     7046 | scott@kitterman.com
  0.66% |    1 |  0.51% |     7036 | huitema@microsoft.com
  0.66% |    1 |  0.51% |     7001 | lear@cisco.com
  0.66% |    1 |  0.51% |     6919 | mrex@sap.com
  0.66% |    1 |  0.50% |     6903 | iad@ietf.org
  0.66% |    1 |  0.46% |     6318 | worley@ariadne.com
  0.66% |    1 |  0.44% |     5955 | iab-chair@iab.org
  0.66% |    1 |  0.43% |     5871 | martin.thomson@gmail.com
  0.66% |    1 |  0.40% |     5517 | jnc@mercury.lcs.mit.edu
  0.66% |    1 |  0.39% |     5293 | swmike@swm.pp.se
--------+------+--------+----------+------------------------
100.00% |  151 |100.00% |  1368214 | Total


From nobody Fri Apr 11 01:06:22 2014
Return-Path: <Jelte.Jansen@sidn.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 632891A044B for <ietf@ietfa.amsl.com>; Fri, 11 Apr 2014 01:06:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.632
X-Spam-Level: 
X-Spam-Status: No, score=0.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=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 5WfqsoscIifT for <ietf@ietfa.amsl.com>; Fri, 11 Apr 2014 01:06:16 -0700 (PDT)
Received: from arn2-kamx.sidn.nl (kamx.sidn.nl [IPv6:2a00:d78:0:147:94:198:152:69]) by ietfa.amsl.com (Postfix) with ESMTP id DE2571A044A for <ietf@ietf.org>; Fri, 11 Apr 2014 01:06:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=sidn.nl; s=sidn_nl; c=relaxed/relaxed;  h=message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding:x-originating-ip; bh=JeKTdxGG+g346BEonrlZmCv8KY5eK2ADkO/5AFx6Z3w=; b=PyCuuVijjN2vHIojrOcf805mdRgOQQDQQVkp13uWTuEZXYwUT5Tbx6wQxJy39I4x3g894BeJut/VYXnVSKRPKpSsolgGDUa63L5Gmch0JXhfvupNu4VPsht8x6R2IOvvFIMB9ULz4AO09ZsRIl3qQ302FUIPnuAFFCocVF3xtaA=
Received: from kahubcasn01.SIDN.local ([192.168.2.73]) by arn2-kamx.sidn.nl  with ESMTP id s3B863pf007245-s3B863pg007245; Fri, 11 Apr 2014 10:06:03 +0200
Received: from [94.198.152.218] (94.198.152.218) by kahubcasn01.SIDN.local (192.168.2.77) with Microsoft SMTP Server (TLS) id 14.3.174.1; Fri, 11 Apr 2014 10:06:02 +0200
Message-ID: <5347A269.4000202@sidn.nl>
Date: Fri, 11 Apr 2014 10:06:01 +0200
From: Jelte Jansen <jelte.jansen@sidn.nl>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0
MIME-Version: 1.0
To: "Theodore Ts'o" <tytso@mit.edu>, Mark Andrews <marka@isc.org>
Subject: Re: Security for various IETF services
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com> <20140410141406.GF15925@thunk.org> <20140411003231.F1A171365D59@rock.dv.isc.org> <20140411005712.GA29956@thunk.org>
In-Reply-To: <20140411005712.GA29956@thunk.org>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [94.198.152.218]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MZ0vradYlApOoiAp6KLu6wYVEQ8
Cc: David Crocker <dcrocker@bbiw.net>, Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 08:06:20 -0000

On 04/11/2014 02:57 AM, Theodore Ts'o wrote:
>>
>> So to get a bad DS added you need to be a corrupt registry or a
>> corrupt employee of registry or you need to compromise the registrants
>> credentials or you need to succeed in transfering the zone to you.
> 
> Or you have to be the corrupt registry operator or an employee for the
> registry operator (i.e., Verisign for the .com domain)....
> 

But at least you have the option to switch away from the corrupt
registry operator. An expensive option, since it would involve changing
your domain names, but an option you don't have with x509 (well, you can
switch, but that doesn't protect you, which was the point). Far from
perfect, but for that specific problem much better than the current x509
model.

Jelte


From nobody Fri Apr 11 03:40:38 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAD2F1A0422 for <ietf@ietfa.amsl.com>; Fri, 11 Apr 2014 03:40:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.795
X-Spam-Level: 
X-Spam-Status: No, score=-0.795 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 nndyYZj38a1v for <ietf@ietfa.amsl.com>; Fri, 11 Apr 2014 03:40:31 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 711471A01E6 for <ietf@ietf.org>; Fri, 11 Apr 2014 03:40:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1397212826; bh=nd2CBubZH4ZIO+yq6af9zlW1hdubC9tzSvQvRqzkI9k=; l=429; h=Date:From:To:References:In-Reply-To; b=YWDE/nDpLG9YlFnHBpYcoqdi+3F66ruIzOSgAzLvshQYBa7siBbQiTtBrDcdy+2CQ r4QqncxcWL6JVA3c1n1yZVFYgJeAbXXFohcGvbO0wS80EDEXJweNvnspyvaPZnwvX7 1Tep18axw8YFWcf6wwq3ZTjGg7H7u3hx+ZC+WDDI=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Fri, 11 Apr 2014 12:40:25 +0200 id 00000000005DC03F.000000005347C699.00005BB0
Message-ID: <5347C698.6040108@tana.it>
Date: Fri, 11 Apr 2014 12:40:24 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1404081325130.76892@joyce.lan>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CcrIX1CGuNJc7qoO46QMKhp8c4g
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 10:40:36 -0000

On Tue 08/Apr/2014 19:34:35 +0200 John R Levine wrote:
>
> Just today I did modify it so that any list mail with a From: address
> @yahoo.com is re written to @yahoo.com.INVALID.  That's the least
> intrusive way I've been able to come up with to mitigate the damage.

Fair enough.  I've copied that suggestion to
http://en.wikipedia.org/wiki/DMARC#Human_policy
Please feel free to amend that page at your leisure.

Ale


From nobody Fri Apr 11 14:24:40 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4A01A02FA for <ietf@ietfa.amsl.com>; Fri, 11 Apr 2014 14:24:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.001
X-Spam-Level: 
X-Spam-Status: No, score=-102.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 dYDWIy_fS32i for <ietf@ietfa.amsl.com>; Fri, 11 Apr 2014 14:24:34 -0700 (PDT)
Received: from dkim.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 860821A01DF for <ietf@ietf.org>; Fri, 11 Apr 2014 14:24:33 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=646; t=1397251461; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=tigj72rGYoBRpfqUcZ1t/z0IxxQ=; b=vY16rP2Qa1UetJ4rtI31 JXh/zpJ67OoGLFTDkf+x8JROQK8/Ob3xHtN4XDQs5HT6DDa5Kc7etFW2S1WsYf1b Mj07x4bwFesyWJfqsF0W2lzbzyP/tKEIZOVRJRpMVYj5mUkmcf2c3hA8vEuYagNZ GTFwBfdIVB+ia0ABgUiQJH4=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 11 Apr 2014 17:24:21 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 360042055.4781.3232; Fri, 11 Apr 2014 17:24:21 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=646; t=1397251399; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=pGbjsxY C/rDAiRz1BnwtVOrIgqLgCEIroypMOJivkts=; b=UShQfkbSYd1dFeX2ydIAbRQ dbzeJNtGf0iGQRXlPs12V6Ii3ppMslYG8TkFiYr5QzXCHfafN3/3JdjIX94YFHc9 TbpWxFwqDxoEaDyFm9wWWyyfn78uW4YQp8pDiGaRqqtZPOcbOlzRQjCt9dGAGnVc B1/ScfTsMhLk8735fSV8=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 11 Apr 2014 17:23:19 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 379575625.9.4492; Fri, 11 Apr 2014 17:23:18 -0400
Message-ID: <53485D86.6000207@isdg.net>
Date: Fri, 11 Apr 2014 17:24:22 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan> <5347C698.6040108@tana.it>
In-Reply-To: <5347C698.6040108@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/W_W47dnuRWjggXNQrkq7O1bqBY0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Apr 2014 21:24:39 -0000

Wouldn't that be tampering with a domain and telecommunications that 
would be valid for all other purposes other than for DMARC?

-- 
HLS

On 4/11/2014 6:40 AM, Alessandro Vesely wrote:
> On Tue 08/Apr/2014 19:34:35 +0200 John R Levine wrote:
>>
>> Just today I did modify it so that any list mail with a From: address
>> @yahoo.com is re written to @yahoo.com.INVALID.  That's the least
>> intrusive way I've been able to come up with to mitigate the damage.
>
> Fair enough.  I've copied that suggestion to
> http://en.wikipedia.org/wiki/DMARC#Human_policy
> Please feel free to amend that page at your leisure.
>
> Ale
>
>
>




From nobody Sat Apr 12 01:19:37 2014
Return-Path: <abhishekv.verma@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D828F1A0120 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 01:19:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 DmXgWWlilIYa for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 01:19:33 -0700 (PDT)
Received: from mail-ig0-x234.google.com (mail-ig0-x234.google.com [IPv6:2607:f8b0:4001:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 88A9E1A00BF for <ietf@ietf.org>; Sat, 12 Apr 2014 01:19:33 -0700 (PDT)
Received: by mail-ig0-f180.google.com with SMTP id c1so1687621igq.7 for <ietf@ietf.org>; Sat, 12 Apr 2014 01:19:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=IJp56J4aruUVzOjgiON6oxcA927eXW9syh/j3YWPPDY=; b=HeaFeFH2ppN+KX7k2I7wq3DqZdn5azCghnyUBU49KNQ+1c+zRXRxsKCTU8qF7gqqbf lXfpBPu0QlgbO19zS5a7ll5p5vygVavhfInuQPcqdn/40XJG5HJ6Mc9d7YMYVm9uVnva oiFKU8cyrRFS9sbbKubtG/gckKfBgcA0W24TbhVtzItfs2C8bCKGNKU0bSJG1/PsPaP3 YJLyjnbr2NzjXf2yOq4jopNBOiJrU09TXSiTAiz32j5WIL3FLqjRMRcJsY638nXb/I6Q AYL+FTDnOsi0BQ2JseN6Q8ZAC2vRSfHi5liv1timcKidxeETkIW+iVeuYHg3zqE/4Y+W VtHg==
MIME-Version: 1.0
X-Received: by 10.50.43.134 with SMTP id w6mr2220863igl.3.1397290771865; Sat, 12 Apr 2014 01:19:31 -0700 (PDT)
Received: by 10.64.89.10 with HTTP; Sat, 12 Apr 2014 01:19:31 -0700 (PDT)
Date: Sat, 12 Apr 2014 13:49:31 +0530
Message-ID: <CADDmorQ+ML8oOdkG5OJ4uQj8ufC6K15c4ieXgz=5RtSXPQJZZw@mail.gmail.com>
Subject: SDN and Routing Protocols
From: Abhishek Verma <abhishekv.verma@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=089e01184b0c1ae4fa04f6d41c94
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3q1-gokAL_AMD_tP874RVtSqme8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 08:19:36 -0000

--089e01184b0c1ae4fa04f6d41c94
Content-Type: text/plain; charset=ISO-8859-1

Hi,

Is SDN going to make routing protocols less relevant? I understand that
this list is frequented by several routing guys, so this question may
offend them. However, as i understand more and more of this technology,
there seems to be a clear trend towards OSPF/ISIS less environments.
Obviously, BGP is still needed if youre talking across AS boundaries. SDN
also obviates the need to run LDP/RSVP to set up the tunnels.

ANy comments here?

Regards, Abhishek

--089e01184b0c1ae4fa04f6d41c94
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>Is SDN going to make routing protoc=
ols less relevant? I understand that this list is frequented by several rou=
ting guys, so this question may offend them. However, as i understand more =
and more of this technology, there seems to be a clear trend towards OSPF/I=
SIS less environments. Obviously, BGP is still needed if youre talking acro=
ss AS boundaries. SDN also obviates the need to run LDP/RSVP to set up the =
tunnels.</div>
<div><br></div><div>ANy comments here?</div><div><br></div><div>Regards, Ab=
hishek</div></div>

--089e01184b0c1ae4fa04f6d41c94--


From nobody Sat Apr 12 12:56:24 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCF431A022D for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 12:56:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.398
X-Spam-Level: *
X-Spam-Status: No, score=1.398 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 OvAUf1ZVPWsU for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 12:56:21 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 28D151A0227 for <ietf@ietf.org>; Sat, 12 Apr 2014 12:56:21 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 0C2CCCC0BE for <ietf@ietf.org>; Sat, 12 Apr 2014 15:56:19 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id Wgxw+D2AbvxW for <ietf@ietf.org>; Sat, 12 Apr 2014 15:56:14 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 8DD66CC0B0 for <ietf@ietf.org>; Sat, 12 Apr 2014 15:56:14 -0400 (EDT)
Message-ID: <53499A5E.9020805@meetinghouse.net>
Date: Sat, 12 Apr 2014 15:56:14 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/s4srqTka-5m2mRvO8_yOFF2ARKo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 19:56:23 -0000

Folks,

We (really I) support perhaps 2 dozen small email lists, for a bunch of 
community groups (PTOs, churches, neighborhood groups) - mostly the 
legacy of previously running a small hosting firm, and still having the 
machines sitting in a data center.  The kinds of groups with lots of 
non-technical users who have email accounts on Yahoo, hotmail, AOL, 
Comcast, and such.  The lists range in size from tiny (5 person boards 
of directors) to maybe 1000 (high school parents).

Yahoo's implementation of it's new DMARC policy has been an absolute 
disaster.  Kind of messes things up when a few days before tax filings 
are due, and in parallel with the Heartbleed mess, (not to mention the 
work that pays the bills), roughly 1/3 of the addresses on almost all of 
the lists start bouncing mail from yahoo addresses - particularly when 
yahoo's postmaster didn't have a clue what was going on (my initial 
thought was - oh heck, need to get back on their whitelist).  Luckily 
gmail seems not to be honoring the Yahoo's p=reject policy, at least so 
far, or things would be a LOT worse.

Still trying to figure out a reasonable fix for this, as it looks like 
lots of other listmasters are trying to do - and doesn't help that I'm 
running a less common list package (sympa).

Anyway - one of my reactions to this is that something is really broken 
about the process by which DMARC and Yahoo's policy have been foisted on 
the larger Internet community - and in particular IETF's role or lack 
thereof.  Specifically:

- DMARC is an ad-hoc group that assembled with a "common goal was to 
develop an operational specification to be introduced to the IETF for 
standardization"
(http://dmarc.org/about.html)

- DMARC.org defines the "DMARC Base Specification" with a link to 
https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an IETF 
document

- the referenced document is an informational  Internet draft, that 
expires in October of this year, that starts with "This memo presents a 
proposal for a scalable mechanism by which a mail sending organization 
can express,.

- It's also being presented as mature - through such publicity 
statements as "DMARC standard now protects almost two-thirds of the 
world's 3.3 billion consumer mailboxes worldwide" 
(http://dmarc.org/news/press_release_20140218.html)

In essence, DMARC is being represented as a mature, standards-track IETF 
specification - with the implication that it's been widely vetted, and 
is marching through the traditional experimental -> optional -> 
recommended -> mandatory steps that IETF standards go through.

In reality:
- DMARC was developed by a tiny number of people, all of whom work for 
very large ISPs
- as far as I can tell, all input from the broader community - notably 
mailing list developers and operators was roundly ignored or dismissed 
(the transcript is really clear on this)
- while DMARC is at least partially tested, deploying and honoring 
"p=reject" messages is brand new, and has wreaked tremendous damage 
across the net
- as far as I can tell, those who are behind DMARC are taking the 
position "it's not our problem" (see discussions on 
dmarc-discuss@dmarc.org and dmarc@ietf.org) - and there is nary a Yahoo 
representative to be seen anywhere

 From an operational perspective, this is akin to a large player 
publishing a corrupt nameserver database or routing update - and then 
actively resting attempts to clean up the mess (which, in effect is what 
Yahoo did by updating their DMARC record to p=reject).

The situation strikes me as incredibly perverse and broken - the more so 
that the perpetrators are presenting this as blessed by the IETF 
standards process.

It strikes me that IETF should weigh in on this in a formal fashion - if 
only to make it very clear that IETF is not responsible for this 
debacle, and perhaps to exert some moral influence on the perpetrators 
to back off and help clean up the mess they've created.

On a broader scope - this sort of points out a really big hole in our 
consensus governance process - when one bad actor can inflict damage 
across the entire Internet, apparently, with impunity.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sat Apr 12 13:32:31 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A951A1A023C for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 13:32:28 -0700 (PDT)
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] autolearn=ham
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 cQhl4WIAXe17 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 13:32:27 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id F41CF1A023B for <ietf@ietf.org>; Sat, 12 Apr 2014 13:32:26 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3CKWLPF020943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 12 Apr 2014 13:32:25 -0700
Message-ID: <5349A261.9040500@dcrocker.net>
Date: Sat, 12 Apr 2014 13:30:25 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net>
In-Reply-To: <53499A5E.9020805@meetinghouse.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 12 Apr 2014 13:32:25 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/F6_7YMuS3x0rUATK854w9vsKjZA
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 20:32:28 -0000

On 4/12/2014 12:56 PM, Miles Fidelman wrote:
> - DMARC.org defines the "DMARC Base Specification" with a link to
> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an IETF
> document

While the Internet-Draft mechanism is operated by the IETF, it is an 
open mechanism and issuance through it carries no automatic status, 
particularly with respect to the IETF.

The DMARC specification is not 'an IETF document'.  The current plan is 
to publish it as an RFC, through the 'Independent' stream, which also is 
/not/ an IETF activity.


> - the referenced document is an informational  Internet draft, that

Drafts do not have status.  So the qualifier 'informational' here is not 
meaningful.


> In essence, DMARC is being represented as a mature, standards-track IETF
> specification - with the implication that it's been widely vetted, and
> is marching through the traditional experimental -> optional ->
> recommended -> mandatory steps that IETF standards go through.
>
> In reality:
> - DMARC was developed by a tiny number of people, all of whom work for
> very large ISPs

Well, a few of us who participated don't...


> - as far as I can tell, all input from the broader community - notably
> mailing list developers and operators was roundly ignored or dismissed
> (the transcript is really clear on this)

What transcript?  I'm not aware of its being 'ignored or dismissed'.


> - while DMARC is at least partially tested, deploying and honoring
> "p=reject" messages is brand new, and has wreaked tremendous damage
> across the net

It's not new at all, though of course Yahoo's use is distinctive.


> - as far as I can tell, those who are behind DMARC are taking the
> position "it's not our problem" (see discussions on
> dmarc-discuss@dmarc.org and dmarc@ietf.org) - and there is nary a Yahoo
> representative to be seen anywhere

I've no idea what specifics you are referring to.


> The situation strikes me as incredibly perverse and broken - the more so
> that the perpetrators are presenting this as blessed by the IETF
> standards process.

I haven't seen anyone present such a claim of blessing.  Please point to 
the specifics.

I fear you are confusing the difference between a desire for standards 
status with a claim of its having been granted.

  d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sat Apr 12 13:49:32 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2251A023C for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 13:49:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level: 
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 LqQ7nbgq-2k8 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 13:49:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 884F21A023A for <ietf@ietf.org>; Sat, 12 Apr 2014 13:49:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5C7F020011; Sat, 12 Apr 2014 16:49:35 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A192B63ABA; Sat, 12 Apr 2014 16:49:27 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 8D64E63AB6; Sat, 12 Apr 2014 16:49:27 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <53499A5E.9020805@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Sat, 12 Apr 2014 16:49:27 -0400
Message-ID: <25006.1397335767@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ncW9ftrz1E54VQ841vQrRhtAjz4
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 20:49:30 -0000

--=-=-=


Miles Fidelman <mfidelman@meetinghouse.net> wrote:
    > We (really I) support perhaps 2 dozen small email lists, for a bunch of
    > community groups (PTOs, churches, neighborhood groups) - mostly the
    > legacy of
    > previously running a small hosting firm, and still having the machines

ditto.

+5 on everything you said.
It is a great idea, but it is not mature, and there wasn't much in the way of
running code.

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU0mm14qHRg3pndX9AQL+nQP/YlnFrWl1UZbZ5i1QqN7GRuiBoWMEDTsp
ZrsVQKryIJwlrqk/TGlTWsdDXH5X/Ht6rhOEihWyqbp/xUJ7VGI0W+fmIIJlKon3
yFojTfFzmidJEcM5xK3f7vGLRHG1v3RTMevULpNwnpBMMG29MknE0hF0ADJbDx7X
UNByOEu27Xg=
=oH7p
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Apr 12 14:21:04 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5161A0249 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 14:21:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.419
X-Spam-Level: **
X-Spam-Status: No, score=2.419 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 fcif-wLyZoca for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 14:21:00 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5781A0243 for <ietf@ietf.org>; Sat, 12 Apr 2014 14:21:00 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 26153CC0BE for <ietf@ietf.org>; Sat, 12 Apr 2014 17:20:58 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lbJCTrL4FcwE for <ietf@ietf.org>; Sat, 12 Apr 2014 17:20:53 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 99181CC0B9 for <ietf@ietf.org>; Sat, 12 Apr 2014 17:20:53 -0400 (EDT)
Message-ID: <5349AE35.2000908@meetinghouse.net>
Date: Sat, 12 Apr 2014 17:20:53 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net>
In-Reply-To: <5349A261.9040500@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/omEcOIeU7XBzz3w1l9g756B1Lmc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 21:21:02 -0000

Dave,

Dave Crocker wrote:
> On 4/12/2014 12:56 PM, Miles Fidelman wrote:
>> - DMARC.org defines the "DMARC Base Specification" with a link to
>> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an IETF
>> document
>
> While the Internet-Draft mechanism is operated by the IETF, it is an 
> open mechanism and issuance through it carries no automatic status, 
> particularly with respect to the IETF.
>
> The DMARC specification is not 'an IETF document'.  The current plan 
> is to publish it as an RFC, through the 'Independent' stream, which 
> also is /not/ an IETF activity.
>

My point is that the folks behind dmarc PRESENT it in a way that 
implicitly makes it look like an IETF document, and that it's on the 
standards track.  The reality, as you say, is different.  "Plan to" is 
vaporware.
>
>> - the referenced document is an informational  Internet draft, that
>
> Drafts do not have status.  So the qualifier 'informational' here is 
> not meaningful.
>
As currently published, it carries the header

Intended status: Informational

>
>> In essence, DMARC is being represented as a mature, standards-track IETF
>> specification - with the implication that it's been widely vetted, and
>> is marching through the traditional experimental -> optional ->
>> recommended -> mandatory steps that IETF standards go through.
>>
>> In reality:
>> - DMARC was developed by a tiny number of people, all of whom work for
>> very large ISPs
>
> Well, a few of us who participated don't...

fair enough - but again, just look at http://dmarc.org/about.html - I 
don't see your name, or any other small individuals or ISPs - what I do 
see are
"A group of leading organizations came together in the spring of 2011"
and
"The founding contributors include:

  * *Receivers:* AOL, Comcast, GMail, Hotmail, Netease, Yahoo! Mail
  * *Senders:* American Greetings, Bank of America, Facebook, Fidelity,
    JP Morgan Chase, LinkedIn, PayPal
  * *Intermediaries & Vendors:* Agari, Cloudmark, ReturnPath, Trusted
    Domain Project"

This was very much an industry-based effort.

>
>> - as far as I can tell, all input from the broader community - notably
>> mailing list developers and operators was roundly ignored or dismissed
>> (the transcript is really clear on this)
>
> What transcript?  I'm not aware of its being 'ignored or dismissed'.

Funny, that's the impression I get when I read back through the archives 
for dmarc-discuss@dmarc.org and dmarc@ietf.org

pretty much all discussion of aligning the From: field came down to - 
"you change"

>
>> - while DMARC is at least partially tested, deploying and honoring
>> "p=reject" messages is brand new, and has wreaked tremendous damage
>> across the net
>
> It's not new at all, though of course Yahoo's use is distinctive.

Depends on your definition of "new" - and while DMARC builds on an older 
base, DMARC itself was started in 2011, and I assume the first standards 
and software are more recent then that.

As you say, Yahoo's use is "distinctive" - though I'd use a somewhat 
stronger word.
>
>
>> - as far as I can tell, those who are behind DMARC are taking the
>> position "it's not our problem" (see discussions on
>> dmarc-discuss@dmarc.org and dmarc@ietf.org) - and there is nary a Yahoo
>> representative to be seen anywhere
>
> I've no idea what specifics you are referring to.

I've been following the discussions, on lots of lists, and I've yet to 
see someone say even "I'm from Yahoo and we feel your pain" - much less 
"hmm... maybe this wasn't such a good idea, we're going to back off and 
implement in a slightly gentler manner - and maybe provide some support 
to help patch the major list management packages" - or even "our 
implementation honors Original-Authentication-Results"

nope - as far as I can tell, the folks who turned on p=reject at Yahoo 
don't seem to have even told their own security or customer care folks 
about what's going on - at least when this first broke, and I contacted 
Yahoo's postmaster (thinking I needed to get our servers back on the 
whitelist) - they just pointed me at the whitelist request form

>
>
>> The situation strikes me as incredibly perverse and broken - the more so
>> that the perpetrators are presenting this as blessed by the IETF
>> standards process.
>
> I haven't seen anyone present such a claim of blessing.  Please point 
> to the specifics.
>
> I fear you are confusing the difference between a desire for standards 
> status with a claim of its having been granted.
>
No... I'm quoting the way that dmarc.org is presenting the "DMARC Draft 
Specification" - as marching through the IETF standards track, as it is 
generally understood, and then hiding in the fine print that no such 
thing has happened, or is currently happening

I'm not confused.  It is, and I think intentionally, being presented in 
a way that is intended to confuse.  And I personally think that IETF 
should be calling them on it.  Officially, loudly, and clearly.  (The 
same way that Xerox and Kleenex jump down the throats of anybody who 
tries to use their names generically.  )

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sat Apr 12 15:09:59 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD9061A0250 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 15:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.503
X-Spam-Level: 
X-Spam-Status: No, score=-99.503 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 XLvdZvhELGH8 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 15:09:52 -0700 (PDT)
Received: from mail.catinthebox.net (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id BDEAB1A01DF for <ietf@ietf.org>; Sat, 12 Apr 2014 15:09:51 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4499; t=1397340579; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=HqJV14LX5nKt01RytM8n8j1IGkY=; b=v1sdAIgte5gKphVP4Fqw oX0dBHNsNwqG1kITKPKtpuGsVyoABXGVMp02X5xiV6X62LKHbSpx6TuplfJyPdJ7 oKqmh6mcRTZqYEs/IEXHZB233jeWLtcfkHPc7JHhgnOxE/5RBhFp1Y6NbY17fsGF mVWZucgQwZW/jWIkJB7umxY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 12 Apr 2014 18:09:39 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 449158531.9010.3196; Sat, 12 Apr 2014 18:09:38 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4499; t=1397340519; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=SreszKX LgD2nqyw3DGymZcKI2F+K12Waf7Jvv0tYhqE=; b=vbz5CJ6dafMQmrv13aH5ppY MMPtM3ZDRGbxFJGc8+3m14tKb2MR/lySBw+//TwiMFfklfD1OMAZVxQ0d2dRJVLk b7X+OAvG7j3gFIgMkb36teQvx6VwQ4RHRT4YpOqokfv6zM9qb91kuHTrYlIpLnsu S1XhTMXrCZ26357UDsz0=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 12 Apr 2014 18:08:39 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 468694625.9.5520; Sat, 12 Apr 2014 18:08:37 -0400
Message-ID: <5349B9A8.2090900@isdg.net>
Date: Sat, 12 Apr 2014 18:09:44 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Miles Fidelman <mfidelman@meetinghouse.net>, ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net>
In-Reply-To: <53499A5E.9020805@meetinghouse.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1YxeLf30r449aj_0416PeinjkDg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 22:09:55 -0000

Miles, Bravo to you for being brave!! +100 on everything you said!!

--
HLS

n 4/12/2014 3:56 PM, Miles Fidelman wrote:
> Folks,
>
> We (really I) support perhaps 2 dozen small email lists, for a bunch
> of community groups (PTOs, churches, neighborhood groups) - mostly the
> legacy of previously running a small hosting firm, and still having
> the machines sitting in a data center.  The kinds of groups with lots
> of non-technical users who have email accounts on Yahoo, hotmail, AOL,
> Comcast, and such.  The lists range in size from tiny (5 person boards
> of directors) to maybe 1000 (high school parents).
>
> Yahoo's implementation of it's new DMARC policy has been an absolute
> disaster.  Kind of messes things up when a few days before tax filings
> are due, and in parallel with the Heartbleed mess, (not to mention the
> work that pays the bills), roughly 1/3 of the addresses on almost all
> of the lists start bouncing mail from yahoo addresses - particularly
> when yahoo's postmaster didn't have a clue what was going on (my
> initial thought was - oh heck, need to get back on their whitelist).
> Luckily gmail seems not to be honoring the Yahoo's p=reject policy, at
> least so far, or things would be a LOT worse.
>
> Still trying to figure out a reasonable fix for this, as it looks like
> lots of other listmasters are trying to do - and doesn't help that I'm
> running a less common list package (sympa).
>
> Anyway - one of my reactions to this is that something is really
> broken about the process by which DMARC and Yahoo's policy have been
> foisted on the larger Internet community - and in particular IETF's
> role or lack thereof.  Specifically:
>
> - DMARC is an ad-hoc group that assembled with a "common goal was to
> develop an operational specification to be introduced to the IETF for
> standardization"
> (http://dmarc.org/about.html)
>
> - DMARC.org defines the "DMARC Base Specification" with a link to
> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an IETF
> document
>
> - the referenced document is an informational  Internet draft, that
> expires in October of this year, that starts with "This memo presents
> a proposal for a scalable mechanism by which a mail sending
> organization can express,.
>
> - It's also being presented as mature - through such publicity
> statements as "DMARC standard now protects almost two-thirds of the
> world's 3.3 billion consumer mailboxes worldwide"
> (http://dmarc.org/news/press_release_20140218.html)
>
> In essence, DMARC is being represented as a mature, standards-track
> IETF specification - with the implication that it's been widely
> vetted, and is marching through the traditional experimental ->
> optional -> recommended -> mandatory steps that IETF standards go
> through.
>
> In reality:
> - DMARC was developed by a tiny number of people, all of whom work for
> very large ISPs
> - as far as I can tell, all input from the broader community - notably
> mailing list developers and operators was roundly ignored or dismissed
> (the transcript is really clear on this)
> - while DMARC is at least partially tested, deploying and honoring
> "p=reject" messages is brand new, and has wreaked tremendous damage
> across the net
> - as far as I can tell, those who are behind DMARC are taking the
> position "it's not our problem" (see discussions on
> dmarc-discuss@dmarc.org and dmarc@ietf.org) - and there is nary a
> Yahoo representative to be seen anywhere
>
>  From an operational perspective, this is akin to a large player
> publishing a corrupt nameserver database or routing update - and then
> actively resting attempts to clean up the mess (which, in effect is
> what Yahoo did by updating their DMARC record to p=reject).
>
> The situation strikes me as incredibly perverse and broken - the more
> so that the perpetrators are presenting this as blessed by the IETF
> standards process.
>
> It strikes me that IETF should weigh in on this in a formal fashion -
> if only to make it very clear that IETF is not responsible for this
> debacle, and perhaps to exert some moral influence on the perpetrators
> to back off and help clean up the mess they've created.
>
> On a broader scope - this sort of points out a really big hole in our
> consensus governance process - when one bad actor can inflict damage
> across the entire Internet, apparently, with impunity.
>
> Miles Fidelman



From nobody Sat Apr 12 15:23:32 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A465D1A0251 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 15:23:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 CVBp6-oFBuHR for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 15:23:28 -0700 (PDT)
Received: from mail-pd0-x236.google.com (mail-pd0-x236.google.com [IPv6:2607:f8b0:400e:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id DFEDA1A0250 for <ietf@ietf.org>; Sat, 12 Apr 2014 15:23:27 -0700 (PDT)
Received: by mail-pd0-f182.google.com with SMTP id y10so6679695pdj.13 for <ietf@ietf.org>; Sat, 12 Apr 2014 15:23:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=je7maACMH6UIx56IqdXb4hDj3t5rBABqvTt3grgdsB4=; b=NBu2Nink1fVae8CAf82MGGknjQJanT1e5J2ZklHhRrtMxPWIRRZ3rfiV0VlLNI+tqD TF+qTl6aeh/aKhC5AnSPjfEzs1ZtnVEZffbxpq2CVl4KVXROo7IoBE0UFZ9EmxzUhNbu 5XUsS9kcBUWquWtpbxW88YntchoF3lSvvfsHPiJ6iYQBvpqSZkoM1iclCLCDePuSrg+k rtWtTcyjVW0qGbxEPfVuG7kzAqPdCY/GacZ+X3N9kyvo35VRLMKBa0WzKg/IcNIelh1j fJbNZxqMmw+DG81wAeyLS9935FEiZS5G+uMfen3Kda/XEzsE8hTximYg8DvD9t6Br4wX aamg==
X-Received: by 10.68.203.135 with SMTP id kq7mr35503456pbc.85.1397341406192; Sat, 12 Apr 2014 15:23:26 -0700 (PDT)
Received: from [192.168.178.20] (61.198.69.111.dynamic.snap.net.nz. [111.69.198.61]) by mx.google.com with ESMTPSA id ov4sm19538534pbc.46.2014.04.12.15.23.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 12 Apr 2014 15:23:25 -0700 (PDT)
Message-ID: <5349BCDA.7080701@gmail.com>
Date: Sun, 13 Apr 2014 10:23:22 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net>
In-Reply-To: <5349AE35.2000908@meetinghouse.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Lfkd_cKY_u_BU33Z9T5lTNz4tJU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 22:23:29 -0000

Hi,

In the DMARC draft, I noticed this:

>  Descriptions of the PolicyOverrideTypes:
...
>    mailing_list:  Local heuristics determined that the message arrived
>       via a mailing list, and thus authentication of the original
>       message was not expected to succeed.

Could somebody explain what that means and whether it can be used to
mitigate the current issue? Or are substantial changes needed
in the fundamentals of DMARC?

I assume the authors will be adding a discussion of this issue
to the draft.

Regards
   Brian

On 13/04/2014 09:20, Miles Fidelman wrote:
> Dave,
> 
> Dave Crocker wrote:
>> On 4/12/2014 12:56 PM, Miles Fidelman wrote:
>>> - DMARC.org defines the "DMARC Base Specification" with a link to
>>> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an IETF
>>> document
>>
>> While the Internet-Draft mechanism is operated by the IETF, it is an
>> open mechanism and issuance through it carries no automatic status,
>> particularly with respect to the IETF.
>>
>> The DMARC specification is not 'an IETF document'.  The current plan
>> is to publish it as an RFC, through the 'Independent' stream, which
>> also is /not/ an IETF activity.
>>
> 
> My point is that the folks behind dmarc PRESENT it in a way that
> implicitly makes it look like an IETF document, and that it's on the
> standards track.  The reality, as you say, is different.  "Plan to" is
> vaporware.
>>
>>> - the referenced document is an informational  Internet draft, that
>>
>> Drafts do not have status.  So the qualifier 'informational' here is
>> not meaningful.
>>
> As currently published, it carries the header
> 
> Intended status: Informational
> 
>>
>>> In essence, DMARC is being represented as a mature, standards-track IETF
>>> specification - with the implication that it's been widely vetted, and
>>> is marching through the traditional experimental -> optional ->
>>> recommended -> mandatory steps that IETF standards go through.
>>>
>>> In reality:
>>> - DMARC was developed by a tiny number of people, all of whom work for
>>> very large ISPs
>>
>> Well, a few of us who participated don't...
> 
> fair enough - but again, just look at http://dmarc.org/about.html - I
> don't see your name, or any other small individuals or ISPs - what I do
> see are
> "A group of leading organizations came together in the spring of 2011"
> and
> "The founding contributors include:
> 
>  * *Receivers:* AOL, Comcast, GMail, Hotmail, Netease, Yahoo! Mail
>  * *Senders:* American Greetings, Bank of America, Facebook, Fidelity,
>    JP Morgan Chase, LinkedIn, PayPal
>  * *Intermediaries & Vendors:* Agari, Cloudmark, ReturnPath, Trusted
>    Domain Project"
> 
> This was very much an industry-based effort.
> 
>>
>>> - as far as I can tell, all input from the broader community - notably
>>> mailing list developers and operators was roundly ignored or dismissed
>>> (the transcript is really clear on this)
>>
>> What transcript?  I'm not aware of its being 'ignored or dismissed'.
> 
> Funny, that's the impression I get when I read back through the archives
> for dmarc-discuss@dmarc.org and dmarc@ietf.org
> 
> pretty much all discussion of aligning the From: field came down to -
> "you change"
> 
>>
>>> - while DMARC is at least partially tested, deploying and honoring
>>> "p=reject" messages is brand new, and has wreaked tremendous damage
>>> across the net
>>
>> It's not new at all, though of course Yahoo's use is distinctive.
> 
> Depends on your definition of "new" - and while DMARC builds on an older
> base, DMARC itself was started in 2011, and I assume the first standards
> and software are more recent then that.
> 
> As you say, Yahoo's use is "distinctive" - though I'd use a somewhat
> stronger word.
>>
>>
>>> - as far as I can tell, those who are behind DMARC are taking the
>>> position "it's not our problem" (see discussions on
>>> dmarc-discuss@dmarc.org and dmarc@ietf.org) - and there is nary a Yahoo
>>> representative to be seen anywhere
>>
>> I've no idea what specifics you are referring to.
> 
> I've been following the discussions, on lots of lists, and I've yet to
> see someone say even "I'm from Yahoo and we feel your pain" - much less
> "hmm... maybe this wasn't such a good idea, we're going to back off and
> implement in a slightly gentler manner - and maybe provide some support
> to help patch the major list management packages" - or even "our
> implementation honors Original-Authentication-Results"
> 
> nope - as far as I can tell, the folks who turned on p=reject at Yahoo
> don't seem to have even told their own security or customer care folks
> about what's going on - at least when this first broke, and I contacted
> Yahoo's postmaster (thinking I needed to get our servers back on the
> whitelist) - they just pointed me at the whitelist request form
> 
>>
>>
>>> The situation strikes me as incredibly perverse and broken - the more so
>>> that the perpetrators are presenting this as blessed by the IETF
>>> standards process.
>>
>> I haven't seen anyone present such a claim of blessing.  Please point
>> to the specifics.
>>
>> I fear you are confusing the difference between a desire for standards
>> status with a claim of its having been granted.
>>
> No... I'm quoting the way that dmarc.org is presenting the "DMARC Draft
> Specification" - as marching through the IETF standards track, as it is
> generally understood, and then hiding in the fine print that no such
> thing has happened, or is currently happening
> 
> I'm not confused.  It is, and I think intentionally, being presented in
> a way that is intended to confuse.  And I personally think that IETF
> should be calling them on it.  Officially, loudly, and clearly.  (The
> same way that Xerox and Kleenex jump down the throats of anybody who
> tries to use their names generically.  )
> 
> Miles Fidelman
> 


From nobody Sat Apr 12 16:02:08 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D2901A0257 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 16:02:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.164
X-Spam-Level: 
X-Spam-Status: No, score=-0.164 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
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 TTex6qmgFFb0 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 16:02:04 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 4C3EC1A0214 for <ietf@ietf.org>; Sat, 12 Apr 2014 16:02:04 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WZ6vx-0004ku-Du; Sat, 12 Apr 2014 23:02:01 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 9D1E658026D; Sat, 12 Apr 2014 19:02:00 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1397343720; bh=8SE/M45RhUNX5nTTIIO64OW2rSQo0qA32HHOUO3Mxcg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=sSnl/k758Lna4q/aD04DrMBj84SGRTD80tllYitrafbvFPh189CsnuY0fZj9FOEl9 yvMNoBl2x6EnFyQVPcabT2XPT1RAhfbXGXht723d8Ak5w/xPHOenhZU/Lse+5YA4/K I9ZgMJkyz696u2exddwDj2SBgyulFDo4NiSvrlRs=
Date: Sat, 12 Apr 2014 19:02:00 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Message-ID: <20140412230200.GA14599@thunk.org>
References: <53499A5E.9020805@meetinghouse.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53499A5E.9020805@meetinghouse.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JoK33C64We_awSq_ZhgJ06_NbG0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 23:02:06 -0000

On Sat, Apr 12, 2014 at 03:56:14PM -0400, Miles Fidelman wrote:
> 
> We (really I) support perhaps 2 dozen small email lists, for a bunch of
> community groups (PTOs, churches, neighborhood groups) - mostly the legacy
> of previously running a small hosting firm, and still having the machines
> sitting in a data center.  The kinds of groups with lots of non-technical
> users who have email accounts on Yahoo, hotmail, AOL, Comcast, and such.
> The lists range in size from tiny (5 person boards of directors) to maybe
> 1000 (high school parents).

Why don't you just respond by sending an e-mail to each of the
affected users, telling them that they will unfortunately no longer be
able to participate in the mailing list due to the choices of their
mail provider, and that if they want to continue to receiving e-mail,
to consider setting up new e-mail account with some other provider
such as gmail -- and then cc postmaster@yahoo.com on the message.

That's how I plan to deal with things....

					- Ted


From nobody Sat Apr 12 16:10:15 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 878981A025A for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 16:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.618
X-Spam-Level: *
X-Spam-Status: No, score=1.618 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_21=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 jY-rup5BkjHz for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 16:10:12 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6600B1A0259 for <ietf@ietf.org>; Sat, 12 Apr 2014 16:10:12 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 369C6CC0C0 for <ietf@ietf.org>; Sat, 12 Apr 2014 19:10:10 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZtxIqsbrIzUc for <ietf@ietf.org>; Sat, 12 Apr 2014 19:10:01 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 68F55CC0BE for <ietf@ietf.org>; Sat, 12 Apr 2014 19:10:01 -0400 (EDT)
Message-ID: <5349C7C9.6030908@meetinghouse.net>
Date: Sat, 12 Apr 2014 19:10:01 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <20140412230200.GA14599@thunk.org>
In-Reply-To: <20140412230200.GA14599@thunk.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5G3x1wUAKveeH0GmwXp30iAEt2g
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 23:10:13 -0000

Theodore Ts'o wrote:
> On Sat, Apr 12, 2014 at 03:56:14PM -0400, Miles Fidelman wrote:
>> We (really I) support perhaps 2 dozen small email lists, for a bunch of
>> community groups (PTOs, churches, neighborhood groups) - mostly the legacy
>> of previously running a small hosting firm, and still having the machines
>> sitting in a data center.  The kinds of groups with lots of non-technical
>> users who have email accounts on Yahoo, hotmail, AOL, Comcast, and such.
>> The lists range in size from tiny (5 person boards of directors) to maybe
>> 1000 (high school parents).
> Why don't you just respond by sending an e-mail to each of the
> affected users, telling them that they will unfortunately no longer be
> able to participate in the mailing list due to the choices of their
> mail provider, and that if they want to continue to receiving e-mail,
> to consider setting up new e-mail account with some other provider
> such as gmail -- and then cc postmaster@yahoo.com on the message.
>
> That's how I plan to deal with things....
>
> 					- Ted

Well, it's certainly attractive, if time consuming.  2000 or so people, 
or 24 or so list messages, plus dealing with all the folks who ask me to 
personally unsubscribe one address, and add their new one.  Probably 
less painful to patch the list manager to re-write the From address of 
incoming mail (which is what seems to be where a lot of people are going).

As to them impact on Yahoo - I expect they'd ignore it.  On the other 
hand, I'm starting to wonder about suing them for damages and creating a 
public nuisance. :-)  [yes, I'm feeling a little vindictive right now.]

Sigh...

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sat Apr 12 16:48:59 2014
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBD871A023E for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 16:48:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.273
X-Spam-Level: 
X-Spam-Status: No, score=-3.273 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 JrFQ6CwDjcRz for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 16:48:54 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id 1B22B1A023D for <ietf@ietf.org>; Sat, 12 Apr 2014 16:48:54 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 13B852383D9; Sat, 12 Apr 2014 23:48:39 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 3A1EB160066; Sat, 12 Apr 2014 23:50:32 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 0A691160052; Sat, 12 Apr 2014 23:50:32 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 86C0A13A7AA6; Sun, 13 Apr 2014 09:48:34 +1000 (EST)
To: Miles Fidelman <mfidelman@meetinghouse.net>
From: Mark Andrews <marka@isc.org>
References: <53499A5E.9020805@meetinghouse.net> <20140412230200.GA14599@thunk.org> <5349C7C9.6030908@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: Your message of "Sat, 12 Apr 2014 19:10:01 -0400." <5349C7C9.6030908@meetinghouse.net>
Date: Sun, 13 Apr 2014 09:48:34 +1000
Message-Id: <20140412234834.86C0A13A7AA6@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SFxzZ7m6OJfmyr9kM1TtmEYyyJc
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 23:48:56 -0000

In message <5349C7C9.6030908@meetinghouse.net>, Miles Fidelman writes:
> Theodore Ts'o wrote:
> > On Sat, Apr 12, 2014 at 03:56:14PM -0400, Miles Fidelman wrote:
> >> We (really I) support perhaps 2 dozen small email lists, for a bunch of
> >> community groups (PTOs, churches, neighborhood groups) - mostly the legacy
> >> of previously running a small hosting firm, and still having the machines
> >> sitting in a data center.  The kinds of groups with lots of non-technical
> >> users who have email accounts on Yahoo, hotmail, AOL, Comcast, and such.
> >> The lists range in size from tiny (5 person boards of directors) to maybe
> >> 1000 (high school parents).
> > Why don't you just respond by sending an e-mail to each of the
> > affected users, telling them that they will unfortunately no longer be
> > able to participate in the mailing list due to the choices of their
> > mail provider, and that if they want to continue to receiving e-mail,
> > to consider setting up new e-mail account with some other provider
> > such as gmail -- and then cc postmaster@yahoo.com on the message.
> >
> > That's how I plan to deal with things....
> >
> > 					- Ted
> 
> Well, it's certainly attractive, if time consuming.  2000 or so people, 
> or 24 or so list messages, plus dealing with all the folks who ask me to 
> personally unsubscribe one address, and add their new one.  Probably 
> less painful to patch the list manager to re-write the From address of 
> incoming mail (which is what seems to be where a lot of people are going).
> 
> As to them impact on Yahoo - I expect they'd ignore it.  On the other 
> hand, I'm starting to wonder about suing them for damages and creating a 
> public nuisance. :-)  [yes, I'm feeling a little vindictive right now.]

Just reject any email with a DMARC "p=reject" qualifier destined
to a email list at the SMTP level that doesn't include you as a
valid sender.

5.x.x DMARC p=reject not compatible with email sent to a mailing list

What Yahoo is doing is anti-social.  It is forcing people who don't
want to be involved in DMARC to particate to some level as they are
getting all the bounces from Yahoo's idiocy.

Alterntively reject all @yahoo.com email until the DMARC record is
changed.  If Yahoo want to apply presure to people to support DMARC
by changing their software, email list operators can apply presure
back when they deliberately do something stupid like this.

Mark

> Sigh...
> 
> Miles
> 
> -- 
> In theory, there is no difference between theory and practice.
> In practice, there is.   .... Yogi Berra
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Sat Apr 12 21:37:20 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72DE31A0261 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 21:37:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.702
X-Spam-Level: 
X-Spam-Status: No, score=-98.702 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 xA4-unExsTsA for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 21:37:16 -0700 (PDT)
Received: from news.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 41F2D1A025B for <ietf@ietf.org>; Sat, 12 Apr 2014 21:37:15 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1920; t=1397363825; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=RFtch09TUr0bzvdnzBjm+skNMSE=; b=LPtC+iEhuT7JPZb/lQjt bpWQEkJyfec6BKUU7bdLJ+jXeh2frovst+5bjM/9Q5qPGF+46ZfxbwbCiFgu+eSH X47n4UPPxTNGqZRKZZbFo1EGyDVGBzCuLuqqU52d3FoOVrHSpigsvBRNPeKhPHa5 xTt3BsfcVNb79tAwxgcjHQA=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 13 Apr 2014 00:37:05 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 472404240.9010.3640; Sun, 13 Apr 2014 00:37:04 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1920; t=1397363761; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=vLGBLb3 kBulm1JTkU4I8v+3yhy+eh8Qj6Epn05rzWq8=; b=kS/gO5Hr8e3lOEzFYn1fivs DBJemYMXmINCkJop5bzKfFrTaYiArxy6gdmnEUza1uNWn/9rL9X4sB9abd0YISu+ IVWFufRZSSBLXeXnX5Esl5eMc9L5BNqGKnd4SVx/+0Alyvif0lLB4cV5k/UWUIiI J9IaT+bxnxxjc9E+DS4Y=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 13 Apr 2014 00:36:01 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 491937328.9.8064; Sun, 13 Apr 2014 00:36:00 -0400
Message-ID: <534A1473.8090206@isdg.net>
Date: Sun, 13 Apr 2014 00:37:07 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com>
In-Reply-To: <5349BCDA.7080701@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/I4dI1sq6zGmWgw4kyFhcL-F-PZo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 04:37:18 -0000

On 4/12/2014 6:23 PM, Brian E Carpenter wrote:
> Hi,
>
> In the DMARC draft, I noticed this:
>
>>   Descriptions of the PolicyOverrideTypes:
> ...
>>     mailing_list:  Local heuristics determined that the message arrived
>>        via a mailing list, and thus authentication of the original
>>        message was not expected to succeed.
>
> Could somebody explain what that means and whether it can be used to
> mitigate the current issue? Or are substantial changes needed
> in the fundamentals of DMARC?
>
> I assume the authors will be adding a discussion of this issue
> to the draft.
>
> Regards
>     Brian

Brian,

The overall problem is that the middle ware, mailing list servers 
(MLS) need to change in order to support any DKIM optional add-on 
security policy layer.

If the MLS is going to break the integrity and resign the mail, it 
could not do this blindly without considering the submitting author 
domain security policy.

First it was SSP, then ADSP, now DMARC.  Same problem. Unless the 
middle ware supports this policy layer, they risk causing distribution 
problems at the ADSP and/or DMARC, policy-compliant downlinks.   This 
was one of the cited interop problem reasons why ADSP was made historic.

So its really a matter of getting wider support at the Mailing List 
Software or once again, like it was done for ADSP, promoting the idea 
of not supporting the p=reject feature of DMARC.

Keep in mind, this is really only a problem because a "public" 
yahoo.com domain, for some odd reason, use a DMARC p=reject and there 
is apparently mail distribution down links that support it.  The list 
servers blindly resigned the mail and there is no 3rd party support 
concept in place to handle it.

But it would be precisely what another domain like fedex.com would 
want with its restrictive ADSP discardable and DMARC p=reject policies 
being used in a public mailing list.


-- 
HLS



From nobody Sat Apr 12 23:04:44 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 327981A026F for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 23:04:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.5
X-Spam-Level: 
X-Spam-Status: No, score=0.5 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 unZqi9MX8Cx1 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 23:04:39 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id B81E51A026D for <ietf@ietf.org>; Sat, 12 Apr 2014 23:04:39 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id kl14so7036217pab.32 for <ietf@ietf.org>; Sat, 12 Apr 2014 23:04:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=JSyTPQVyOLWQXSqQtuhgFmQfwbScbnw1gL890gpdaLY=; b=yISrA5cBhHmXZJY5hlr5/8Q8cIZGEP3WpS6GdYOH+AiQai7LyYSEpdt/HOs3g0Ooix qB7WkqkSNyWQHdRYlyElJ+4y4q+DRjUqry7lA4QzidWykMLEx5em/ODjza9AvzMZjLQ6 U+OKisIKdaokEaORgD4PDWG5WRvJE09bRO9k5/gF6TglWQ4tkFBpc+cyujTTNWLAaovT RqMq0c5gemWjuNLpxwfsLq9WEiufa7ZJdcWHswBgRHS6fbI1Z+s4HohdtyGcwJL8CTyf IX1EaL6mLUD5moAjdCSBLwNNxeAcmcA3BzSwcEmKlZoa35TFQ9Y4M5MOKAWSAvrvD2P1 7xog==
X-Received: by 10.68.202.8 with SMTP id ke8mr37303228pbc.86.1397369077345; Sat, 12 Apr 2014 23:04:37 -0700 (PDT)
Received: from [192.168.2.114] (c-67-188-1-12.hsd1.ca.comcast.net. [67.188.1.12]) by mx.google.com with ESMTPSA id id10sm25700547pbc.35.2014.04.12.23.04.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 12 Apr 2014 23:04:36 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_94D536FC-525C-4904-83F7-1F6560FF10D7"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <5349BCDA.7080701@gmail.com>
Date: Sat, 12 Apr 2014 23:04:33 -0700
Message-Id: <4B5E63AB-0331-4155-9317-141537B87F1D@gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Yzru1cogywlJmqUQfdraQ96tj3I
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 06:04:42 -0000

--Apple-Mail=_94D536FC-525C-4904-83F7-1F6560FF10D7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Apr 12, 2014, at 3:23 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> Hi,
>=20
> In the DMARC draft, I noticed this:
>=20
>> Descriptions of the PolicyOverrideTypes:
> ...
>>   mailing_list:  Local heuristics determined that the message arrived
>>      via a mailing list, and thus authentication of the original
>>      message was not expected to succeed.
>=20
> Could somebody explain what that means and whether it can be used to
> mitigate the current issue? Or are substantial changes needed
> in the fundamentals of DMARC?
>=20
> I assume the authors will be adding a discussion of this issue
> to the draft.
>=20
> Regards
>   Brian

Dear Brian,

There was an extension that foresaw this problem by offering a safe =
policy override scheme for third-party services that might result in =
DKIM signature failure.  DMARC often fails with messages from =
third-party services such as mailing-list.  Such failures normally =
result in these messages being placed into junk folders.  Unfortunately, =
too many ignore cautions about rejecting as can be demanded by DMARC.  =
This work began as =
http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06 by Daniel Black =
and myself that eventually resulted in =
http://tools.ietf.org/html/rfc6541.  Murray considered TPA too complex.  =
The TPA scheme could have avoided the very problems caused by DMARC =
policies placed on wrong account types.  DMARC is often promoted without =
its limitation being clearly stated or seemingly understood.  Does Yahoo =
expect mailing lists to drop users of their service? =20

This could have been avoided without any disruption to mailing lists by =
a community generated list of known good third-party service providers =
published as hash labels.  Although IESG did not think SPF records able =
to generate hundreds of DNS transactions against otherwise uninvolved =
domains a concern, IESG regarded a single ATPS query against the =
authoritative domain a major threat that MUST be addressed by use of a =
"special" DKIM signature.  This IESG mandated change defeated efforts =
aimed at avoiding such disruptions and also made virtually any policy =
exception scheme non-deployable.=20

The IESG needs to explain their thinking.  I can't, nor have they =
allowed a means for a functional alternative.

Regards,
Douglas Otis


> On 13/04/2014 09:20, Miles Fidelman wrote:
>> Dave,
>>=20
>> Dave Crocker wrote:
>>> On 4/12/2014 12:56 PM, Miles Fidelman wrote:
>>>> - DMARC.org defines the "DMARC Base Specification" with a link to
>>>> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an =
IETF
>>>> document
>>>=20
>>> While the Internet-Draft mechanism is operated by the IETF, it is an
>>> open mechanism and issuance through it carries no automatic status,
>>> particularly with respect to the IETF.
>>>=20
>>> The DMARC specification is not 'an IETF document'.  The current plan
>>> is to publish it as an RFC, through the 'Independent' stream, which
>>> also is /not/ an IETF activity.
>>>=20
>>=20
>> My point is that the folks behind dmarc PRESENT it in a way that
>> implicitly makes it look like an IETF document, and that it's on the
>> standards track.  The reality, as you say, is different.  "Plan to" =
is
>> vaporware.
>>>=20
>>>> - the referenced document is an informational  Internet draft, that
>>>=20
>>> Drafts do not have status.  So the qualifier 'informational' here is
>>> not meaningful.
>>>=20
>> As currently published, it carries the header
>>=20
>> Intended status: Informational
>>=20
>>>=20
>>>> In essence, DMARC is being represented as a mature, standards-track =
IETF
>>>> specification - with the implication that it's been widely vetted, =
and
>>>> is marching through the traditional experimental -> optional ->
>>>> recommended -> mandatory steps that IETF standards go through.
>>>>=20
>>>> In reality:
>>>> - DMARC was developed by a tiny number of people, all of whom work =
for
>>>> very large ISPs
>>>=20
>>> Well, a few of us who participated don't...
>>=20
>> fair enough - but again, just look at http://dmarc.org/about.html - I
>> don't see your name, or any other small individuals or ISPs - what I =
do
>> see are
>> "A group of leading organizations came together in the spring of =
2011"
>> and
>> "The founding contributors include:
>>=20
>> * *Receivers:* AOL, Comcast, GMail, Hotmail, Netease, Yahoo! Mail
>> * *Senders:* American Greetings, Bank of America, Facebook, Fidelity,
>>   JP Morgan Chase, LinkedIn, PayPal
>> * *Intermediaries & Vendors:* Agari, Cloudmark, ReturnPath, Trusted
>>   Domain Project"
>>=20
>> This was very much an industry-based effort.
>>=20
>>>=20
>>>> - as far as I can tell, all input from the broader community - =
notably
>>>> mailing list developers and operators was roundly ignored or =
dismissed
>>>> (the transcript is really clear on this)
>>>=20
>>> What transcript?  I'm not aware of its being 'ignored or dismissed'.
>>=20
>> Funny, that's the impression I get when I read back through the =
archives
>> for dmarc-discuss@dmarc.org and dmarc@ietf.org
>>=20
>> pretty much all discussion of aligning the From: field came down to -
>> "you change"
>>=20
>>>=20
>>>> - while DMARC is at least partially tested, deploying and honoring
>>>> "p=3Dreject" messages is brand new, and has wreaked tremendous =
damage
>>>> across the net
>>>=20
>>> It's not new at all, though of course Yahoo's use is distinctive.
>>=20
>> Depends on your definition of "new" - and while DMARC builds on an =
older
>> base, DMARC itself was started in 2011, and I assume the first =
standards
>> and software are more recent then that.
>>=20
>> As you say, Yahoo's use is "distinctive" - though I'd use a somewhat
>> stronger word.
>>>=20
>>>=20
>>>> - as far as I can tell, those who are behind DMARC are taking the
>>>> position "it's not our problem" (see discussions on
>>>> dmarc-discuss@dmarc.org and dmarc@ietf.org) - and there is nary a =
Yahoo
>>>> representative to be seen anywhere
>>>=20
>>> I've no idea what specifics you are referring to.
>>=20
>> I've been following the discussions, on lots of lists, and I've yet =
to
>> see someone say even "I'm from Yahoo and we feel your pain" - much =
less
>> "hmm... maybe this wasn't such a good idea, we're going to back off =
and
>> implement in a slightly gentler manner - and maybe provide some =
support
>> to help patch the major list management packages" - or even "our
>> implementation honors Original-Authentication-Results"
>>=20
>> nope - as far as I can tell, the folks who turned on p=3Dreject at =
Yahoo
>> don't seem to have even told their own security or customer care =
folks
>> about what's going on - at least when this first broke, and I =
contacted
>> Yahoo's postmaster (thinking I needed to get our servers back on the
>> whitelist) - they just pointed me at the whitelist request form
>>=20
>>>=20
>>>=20
>>>> The situation strikes me as incredibly perverse and broken - the =
more so
>>>> that the perpetrators are presenting this as blessed by the IETF
>>>> standards process.
>>>=20
>>> I haven't seen anyone present such a claim of blessing.  Please =
point
>>> to the specifics.
>>>=20
>>> I fear you are confusing the difference between a desire for =
standards
>>> status with a claim of its having been granted.
>>>=20
>> No... I'm quoting the way that dmarc.org is presenting the "DMARC =
Draft
>> Specification" - as marching through the IETF standards track, as it =
is
>> generally understood, and then hiding in the fine print that no such
>> thing has happened, or is currently happening
>>=20
>> I'm not confused.  It is, and I think intentionally, being presented =
in
>> a way that is intended to confuse.  And I personally think that IETF
>> should be calling them on it.  Officially, loudly, and clearly.  (The
>> same way that Xerox and Kleenex jump down the throats of anybody who
>> tries to use their names generically.  )
>>=20
>> Miles Fidelman
>>=20
>=20


--Apple-Mail=_94D536FC-525C-4904-83F7-1F6560FF10D7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;"><br>On Apr 12, 2014, at 3:23 PM, =
Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a=
>&gt; wrote:<br><br><blockquote type=3D"cite">Hi,<br><br>In the DMARC =
draft, I noticed this:<br><br><blockquote type=3D"cite">Descriptions of =
the PolicyOverrideTypes:<br></blockquote>...<br><blockquote =
type=3D"cite">&nbsp; mailing_list: &nbsp;Local heuristics determined =
that the message arrived<br>&nbsp; &nbsp; &nbsp;via a mailing list, and =
thus authentication of the original<br>&nbsp; &nbsp; &nbsp;message was =
not expected to succeed.<br></blockquote><br>Could somebody explain what =
that means and whether it can be used to<br>mitigate the current issue? =
Or are substantial changes needed<br>in the fundamentals of =
DMARC?<br><br>I assume the authors will be adding a discussion of this =
issue<br>to the draft.<br><br>Regards<br>&nbsp; =
Brian<br></blockquote><div><br></div>Dear =
Brian,<div><br></div><div>There was an extension that foresaw this =
problem by offering a safe policy override scheme for third-party =
services that might result in DKIM signature failure. &nbsp;DMARC often =
fails with messages from third-party services such as mailing-list. =
&nbsp;Such failures normally result in these messages being placed into =
junk folders. &nbsp;Unfortunately, too many ignore cautions about =
rejecting as can be demanded by DMARC. &nbsp;This work began as&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06">http://to=
ols.ietf.org/html/draft-otis-dkim-tpa-label-06</a>&nbsp;by Daniel Black =
and myself that eventually resulted in&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc6541">http://tools.ietf.org/html/rfc=
6541</a>. &nbsp;Murray considered TPA too complex. &nbsp;The TPA scheme =
could have avoided the very problems caused by DMARC policies placed on =
wrong account types. &nbsp;DMARC is often promoted without its =
limitation being clearly stated or seemingly understood. &nbsp;Does =
Yahoo expect mailing lists to drop users of their service? =
&nbsp;</div><div><br></div><div>This could have been avoided without any =
disruption to mailing lists by a community generated list of known good =
third-party service providers published as hash labels. &nbsp;Although =
IESG did not think SPF records able to generate hundreds of DNS =
transactions against otherwise uninvolved domains a concern, IESG =
regarded a single ATPS query against the authoritative domain a major =
threat that MUST be addressed by use of a "special" DKIM signature. =
&nbsp;This IESG mandated change defeated efforts aimed at avoiding such =
disruptions and also made virtually any policy exception scheme =
non-deployable.&nbsp;</div><div><br></div><div>The IESG needs to explain =
their thinking. &nbsp;I can't, nor have they allowed a means for a =
functional =
alternative.</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div><div><br></div><div><blockquote type=3D"cite">On =
13/04/2014 09:20, Miles Fidelman wrote:<br><blockquote =
type=3D"cite">Dave,<br><br>Dave Crocker wrote:<br><blockquote =
type=3D"cite">On 4/12/2014 12:56 PM, Miles Fidelman =
wrote:<br><blockquote type=3D"cite">- <a =
href=3D"http://DMARC.org">DMARC.org</a> defines the "DMARC Base =
Specification" with a link to<br><a =
href=3D"https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/">http=
s://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/</a> - an =
IETF<br>document<br></blockquote><br>While the Internet-Draft mechanism =
is operated by the IETF, it is an<br>open mechanism and issuance through =
it carries no automatic status,<br>particularly with respect to the =
IETF.<br><br>The DMARC specification is not 'an IETF document'. =
&nbsp;The current plan<br>is to publish it as an RFC, through the =
'Independent' stream, which<br>also is /not/ an IETF =
activity.<br><br></blockquote><br>My point is that the folks behind =
dmarc PRESENT it in a way that<br>implicitly makes it look like an IETF =
document, and that it's on the<br>standards track. &nbsp;The reality, as =
you say, is different. &nbsp;"Plan to" is<br>vaporware.<br><blockquote =
type=3D"cite"><br><blockquote type=3D"cite">- the referenced document is =
an informational &nbsp;Internet draft, that<br></blockquote><br>Drafts =
do not have status. &nbsp;So the qualifier 'informational' here =
is<br>not meaningful.<br><br></blockquote>As currently published, it =
carries the header<br><br>Intended status: =
Informational<br><br><blockquote type=3D"cite"><br><blockquote =
type=3D"cite">In essence, DMARC is being represented as a mature, =
standards-track IETF<br>specification - with the implication that it's =
been widely vetted, and<br>is marching through the traditional =
experimental -&gt; optional -&gt;<br>recommended -&gt; mandatory steps =
that IETF standards go through.<br><br>In reality:<br>- DMARC was =
developed by a tiny number of people, all of whom work for<br>very large =
ISPs<br></blockquote><br>Well, a few of us who participated =
don't...<br></blockquote><br>fair enough - but again, just look at <a =
href=3D"http://dmarc.org/about.html">http://dmarc.org/about.html</a> - =
I<br>don't see your name, or any other small individuals or ISPs - what =
I do<br>see are<br>"A group of leading organizations came together in =
the spring of 2011"<br>and<br>"The founding contributors =
include:<br><br>* *Receivers:* AOL, Comcast, GMail, Hotmail, Netease, =
Yahoo! Mail<br>* *Senders:* American Greetings, Bank of America, =
Facebook, Fidelity,<br>&nbsp; JP Morgan Chase, LinkedIn, PayPal<br>* =
*Intermediaries &amp; Vendors:* Agari, Cloudmark, ReturnPath, =
Trusted<br>&nbsp; Domain Project"<br><br>This was very much an =
industry-based effort.<br><br><blockquote type=3D"cite"><br><blockquote =
type=3D"cite">- as far as I can tell, all input from the broader =
community - notably<br>mailing list developers and operators was roundly =
ignored or dismissed<br>(the transcript is really clear on =
this)<br></blockquote><br>What transcript? &nbsp;I'm not aware of its =
being 'ignored or dismissed'.<br></blockquote><br>Funny, that's the =
impression I get when I read back through the archives<br>for <a =
href=3D"mailto:dmarc-discuss@dmarc.org">dmarc-discuss@dmarc.org</a> and =
<a href=3D"mailto:dmarc@ietf.org">dmarc@ietf.org</a><br><br>pretty much =
all discussion of aligning the From: field came down to -<br>"you =
change"<br><br><blockquote type=3D"cite"><br><blockquote type=3D"cite">- =
while DMARC is at least partially tested, deploying and =
honoring<br>"p=3Dreject" messages is brand new, and has wreaked =
tremendous damage<br>across the net<br></blockquote><br>It's not new at =
all, though of course Yahoo's use is =
distinctive.<br></blockquote><br>Depends on your definition of "new" - =
and while DMARC builds on an older<br>base, DMARC itself was started in =
2011, and I assume the first standards<br>and software are more recent =
then that.<br><br>As you say, Yahoo's use is "distinctive" - though I'd =
use a somewhat<br>stronger word.<br><blockquote =
type=3D"cite"><br><br><blockquote type=3D"cite">- as far as I can tell, =
those who are behind DMARC are taking the<br>position "it's not our =
problem" (see discussions on<br><a =
href=3D"mailto:dmarc-discuss@dmarc.org">dmarc-discuss@dmarc.org</a> and =
<a href=3D"mailto:dmarc@ietf.org">dmarc@ietf.org</a>) - and there is =
nary a Yahoo<br>representative to be seen =
anywhere<br></blockquote><br>I've no idea what specifics you are =
referring to.<br></blockquote><br>I've been following the discussions, =
on lots of lists, and I've yet to<br>see someone say even "I'm from =
Yahoo and we feel your pain" - much less<br>"hmm... maybe this wasn't =
such a good idea, we're going to back off and<br>implement in a slightly =
gentler manner - and maybe provide some support<br>to help patch the =
major list management packages" - or even "our<br>implementation honors =
Original-Authentication-Results"<br><br>nope - as far as I can tell, the =
folks who turned on p=3Dreject at Yahoo<br>don't seem to have even told =
their own security or customer care folks<br>about what's going on - at =
least when this first broke, and I contacted<br>Yahoo's postmaster =
(thinking I needed to get our servers back on the<br>whitelist) - they =
just pointed me at the whitelist request form<br><br><blockquote =
type=3D"cite"><br><br><blockquote type=3D"cite">The situation strikes me =
as incredibly perverse and broken - the more so<br>that the perpetrators =
are presenting this as blessed by the IETF<br>standards =
process.<br></blockquote><br>I haven't seen anyone present such a claim =
of blessing. &nbsp;Please point<br>to the specifics.<br><br>I fear you =
are confusing the difference between a desire for standards<br>status =
with a claim of its having been granted.<br><br></blockquote>No... I'm =
quoting the way that <a href=3D"http://dmarc.org">dmarc.org</a> is =
presenting the "DMARC Draft<br>Specification" - as marching through the =
IETF standards track, as it is<br>generally understood, and then hiding =
in the fine print that no such<br>thing has happened, or is currently =
happening<br><br>I'm not confused. &nbsp;It is, and I think =
intentionally, being presented in<br>a way that is intended to confuse. =
&nbsp;And I personally think that IETF<br>should be calling them on it. =
&nbsp;Officially, loudly, and clearly. &nbsp;(The<br>same way that Xerox =
and Kleenex jump down the throats of anybody who<br>tries to use their =
names generically. &nbsp;)<br><br>Miles =
Fidelman<br><br></blockquote><br></blockquote><br></div></body></html>=

--Apple-Mail=_94D536FC-525C-4904-83F7-1F6560FF10D7--


From nobody Sun Apr 13 07:04:51 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDB341A0165 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 07:04:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 n1-VqsyDdPS8 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 07:04:45 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7B99C1A015B for <ietf@ietf.org>; Sun, 13 Apr 2014 07:04:45 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3DE4ctT012705 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 13 Apr 2014 07:04:42 -0700
Message-ID: <534A9901.8040907@dcrocker.net>
Date: Sun, 13 Apr 2014 07:02:41 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com>
In-Reply-To: <5349BCDA.7080701@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 13 Apr 2014 07:04:42 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Z1Sa4UY5fA0g5w29LSKxa-ilOyU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 14:04:50 -0000

On 4/12/2014 3:23 PM, Brian E Carpenter wrote:
> Could somebody explain what that means and whether it can be used to
> mitigate the current issue? Or are substantial changes needed
> in the fundamentals of DMARC?


It means that a receiving system, which otherwise complies with DMARC 
policy records, has chosen to deviate from a domain owner's request to 
reject messages that fail DMARC, by virtue of knowing that it went 
through a mailing list that was trusted.

In other words, it means that the receiving mail system whitelisted a 
mailing list.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Apr 13 07:26:48 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA131A0165 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 07:26:46 -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, SPF_PASS=-0.001] autolearn=ham
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 dykEMt1nOaZ8 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 07:26:44 -0700 (PDT)
Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id C6DE61A014B for <ietf@ietf.org>; Sun, 13 Apr 2014 07:26:44 -0700 (PDT)
Received: by mail-qa0-f50.google.com with SMTP id ih12so7052489qab.37 for <ietf@ietf.org>; Sun, 13 Apr 2014 07:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=e2XMY63o223lViLIktjHVzE7h2UKIIxXDPZsd7H5dO0=; b=qjETTyTC8Ge+HN94X9xaWdUVdP5ThrNB9Eh53MfrlTHEUjnWhvGek748hlnsiPJieO pTHmEVww/mp1bVblWFHQFlTe7bWjkOMDlG5d8s7EFfK1rZiFpVBA+6CKPbsDJs3P1HEb M75NRRRtI01DSg2KyeWsU3+/g2QA+bdSI5OZFBnbm4SiEwn9e/ZNvDhlNBKuAUWRil9M UcUWESyejtBFhOeUEo9tdqdfdtS597gjkU8gSS7JStpvYXGj+PbkwlaN3KlJJId8k6PJ 76p6Rkjn3OY5E8pjGHAjul0BeVPk7gMqopXBe/AtKCBxi+fdNR5NldOaXwxeGdXh+5vk emog==
X-Received: by 10.140.95.8 with SMTP id h8mr41478404qge.2.1397399202515; Sun, 13 Apr 2014 07:26:42 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.205.69 with HTTP; Sun, 13 Apr 2014 07:26:22 -0700 (PDT)
In-Reply-To: <5349A261.9040500@dcrocker.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Sun, 13 Apr 2014 10:26:22 -0400
Message-ID: <CAA=duU0tNVpdRrjwHX6D5arnNenzOztvpfoPgPLwo2aauMASQg@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11c15cc4134ffc04f6ed5b9c
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kiHQVuBNTM-RIJOvUZaBK6K7H24
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 14:26:46 -0000

--001a11c15cc4134ffc04f6ed5b9c
Content-Type: text/plain; charset=ISO-8859-1

Dave,

I couldn't help seeing in your email:

The DMARC specification is not 'an IETF document'.  The current plan is to
> publish it as an RFC, through the 'Independent' stream, which also is /not/
> an IETF activity.
>

when compared to the following at dmarc.org (on the front page):

"DMARC policies are published in the public Domain Name System (DNS), and
available to everyone. It is the goal of DMARC.org to submit the draft
specification to the IETF so that it may begin the process of becoming an
official Internet Standard RFC - available to everyone for reference,
implementation, and improvement."

The statement on dmarc.org really does look like a misrepresentation.

Cheers,
Andy

--001a11c15cc4134ffc04f6ed5b9c
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">Dave,</div><div class=3D"gmail_=
extra"><br></div><div class=3D"gmail_extra">I couldn&#39;t help seeing in y=
our email:</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;pa=
dding-left:1ex">

<div id=3D":18l" class=3D"" style=3D"overflow:hidden">The DMARC specificati=
on is not &#39;an IETF document&#39;. =A0The current plan is to publish it =
as an RFC, through the &#39;Independent&#39; stream, which also is /not/ an=
 IETF activity.<div class=3D"">

</div></div></blockquote></div><br>when compared to the following at <a hre=
f=3D"http://dmarc.org">dmarc.org</a> (on the front page):</div><div class=
=3D"gmail_extra"><br></div><div class=3D"gmail_extra">&quot;DMARC policies =
are published in the public Domain Name System (DNS), and available to ever=
yone. It is the goal of DMARC.org to submit the draft specification to the =
IETF so that it may begin the process of becoming an official Internet Stan=
dard RFC - available to everyone for reference, implementation, and improve=
ment.&quot;<br>

</div><div class=3D"gmail_extra"><div class=3D"gmail_extra"><br></div><div =
class=3D"gmail_extra">The statement on <a href=3D"http://dmarc.org">dmarc.o=
rg</a> really does look like a misrepresentation.</div><div class=3D"gmail_=
extra">

<br></div><div class=3D"gmail_extra">Cheers,<br>Andy</div><div class=3D"gma=
il_extra"><br></div></div></div>

--001a11c15cc4134ffc04f6ed5b9c--


From nobody Sun Apr 13 08:01:24 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6A321A02C5 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 08:01:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.775
X-Spam-Level: **
X-Spam-Status: No, score=2.775 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_12_24=1.049, J_CHICKENPOX_14=0.6, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 d3R-mj95mn58 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 08:01:22 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id D98E61A02C6 for <ietf@ietf.org>; Sun, 13 Apr 2014 08:01:20 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6L9K0P2PC0060QK@mauve.mrochek.com> for ietf@ietf.org; Sun, 13 Apr 2014 07:56:18 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6J01PRR8W00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 13 Apr 2014 07:56:14 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6L9JZF5SC00004W@mauve.mrochek.com>
Date: Sat, 12 Apr 2014 16:35:13 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Sun, 13 Apr 2014 10:23:22 +1200" <5349BCDA.7080701@gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/U3li8C0tg1PGNIDyxavnOj1aZto
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 15:01:24 -0000

> In the DMARC draft, I noticed this:

> >  Descriptions of the PolicyOverrideTypes:
> ...
> >    mailing_list:  Local heuristics determined that the message arrived
> >       via a mailing list, and thus authentication of the original
> >       message was not expected to succeed.

> Could somebody explain what that means and whether it can be used to
> mitigate the current issue?

"mailing_list" is an indicator that a Receiver has chosen to override the
policy the Domain Owner specified for a failed DMARC check, on the basis that
the Receiver has knowledge that the message was forwarded by a mailing list and
thus the DMARC failure is expected. A whitelisting mechansism, in other words.

This is viable mitigation in theory, but not in practice, because it assumes
that Receviers are aware of and can verify mail they receive from every
possible legitimate mailing list out there. That's clearly not possible.

> Or are substantial changes needed
> in the fundamentals of DMARC?

The underlying technical issue is that the two technologies DMARC is built on -
DKIM and SPF - both attach additional/restrictive semantics to longstanding mail
system fields. (Broadly speaking, From: for DKIM and MAIL FROM for SPF.)

An unavoidable consequence of doing this is that longstanding email mechanisms
that depend on the semantics of those fields are going to be affected. (Mailing
lists are the obvious example for DKIM, autoforwarers the obvious one for SPF.)
And when you couple this with an unforgiving policy choice, things break badly.

If you're expecting any of this to be fixable by some technical change to
DMARC, DKIM, or SPF, you can forget it. The design constraints in the space are
very tight, and if you "fix" them to address the issues they cause, you ruin
their effectiveness.

> I assume the authors will be adding a discussion of this issue to the draft.

You're really looking at the wrong draft. draft-crocker-dmarc-bcp-03 talks about
when p=reject should be used, and has this to say:

   DMARC provides protection against some forms of email domain name
   abuse.  Its restricted policy form (p=quarantine or p=reject) is not
   intended for all use cases, and is beneficial only in the presence of
   an actual spoofing problem.  You may, however, want to protect
   mailboxes by checking inbound mail, and you may want information
   about how your domains are showing up at recipients by publishing a
   p=none record.

It goes on to discuss the use of p=reject with domains that only send
transactional. AFAICT there is no discussion of when *not* to use p=reject, and
why. Nor, for that matter is there substantive discussion of mailing_list,
and why it's not a general solution to the problems caused by p=reject.

More generally, I have to say I find myself in substantive agrement with Miles
Fidelman and Hector Santos on this matter. There has been a cascade failure
leading to a colossal screwup. And while Yahoo is clearly the primary malfeasor
here, as is always the case in a cascade failure, there's blame aplenty to go
around.

Like it or not, the IETF published a draft that defines certain mechanisms
which, if used improperly by a large provider, cause serious problems for a
large number of people. The text describing the consequences of the use of
those mechansisms in the drafts is, IMO, entirely inadequate.

And it's not like we didn't know. As others have pointed out, this issue
existed in the earlier ADSP proposal. It was given insufficient attention there
as well.

The clear discrepancy between the fine print regarding intended status in the
specifications (which only engineers read) and what's on the DMARC web site
(which is what managers read)  is also nothing short of deplorable.

Of course the IETF can fall back on the usual excuses, including, but not
limited to:

    Yahoo, of all ISPs, should have known better
    We don't tell people what to do
    It was just a draft
    It was never intended to be a standard
    We're not the Internet Protocol Police
    etc.

I'm sorry, but this time none of these dogs are hunting for me. An attractive
nuisance is an attractive nuisance, and this is what the IETF has, albeit with
the best of intentions, managed to create.

The real question we should be discussing is what options the IETF has to try
and address this.

				Ned


From nobody Sun Apr 13 10:37:59 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A68501A0202 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 10:37:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.702
X-Spam-Level: 
X-Spam-Status: No, score=-98.702 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_46=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 Gb9CwD6hG4xp for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 10:37:54 -0700 (PDT)
Received: from mail.catinthebox.net (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 39FF01A01FF for <ietf@ietf.org>; Sun, 13 Apr 2014 10:37:52 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4293; t=1397410661; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=22QZ0PBkRgO/03+9M6FklJRGVnM=; b=abbF3li4JG0Z9TOEDB2/ UgM0zhXZgeT1rlh6TV9pv6FAaazCQThH/cpo2bHg5H85lqKbVVPVMkwmhbCObvdi K3aJER3KvZDBecegEF9GHhQvQbj6oDX7Sg6V8mpzPt44Y0nnpll26OlWtcKlS9Oc NwLT59/WjUy0U5f3o+yIu9I=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 13 Apr 2014 13:37:41 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 519239905.12247.1620; Sun, 13 Apr 2014 13:37:40 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4293; t=1397410597; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=JRxK+zb MXqXTqYTNJDwhVjv8ztO0Xynr34+VROZ9tlA=; b=iU0cB6q4uCQ7Ed/8fgx57Vo lI/+31G5ziboPUOQk+67y8//zbci+2uSHhmq+jl/KDoRdZvcFqasX2vuXgu+3xpm 1zgsuTyaZP+5RbgZJRMxQSUJ8MVGGvioEsANNZHdcCNk2BhrtjJRY5F4OSk9o2mq TK0cOdc/qkoSZqHJrkgA=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 13 Apr 2014 13:36:37 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 538773031.9.9520; Sun, 13 Apr 2014 13:36:36 -0400
Message-ID: <534ACB5F.7060400@isdg.net>
Date: Sun, 13 Apr 2014 13:37:35 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan> <5347C698.6040108@tana.it>
In-Reply-To: <5347C698.6040108@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zeIeymB7ZsUIKNXVFeE_j6gfuIg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 17:37:56 -0000

On 4/11/2014 6:40 AM, Alessandro Vesely wrote:> On Tue 08/Apr/2014 
19:34:35 +0200 John R Levine wrote:
>>
>> Just today I did modify it so that any list mail with a From: address
>> @yahoo.com is re written to @yahoo.com.INVALID.  That's the least
>> intrusive way I've been able to come up with to mitigate the damage.
>
> Fair enough.  I've copied that suggestion to
> http://en.wikipedia.org/wiki/DMARC#Human_policy
> Please feel free to amend that page at your leisure.
>

Hi Alessandro,

You added (I presume):

    According to John Levine, a well known mail expert, the least
    intrusive way to mitigate the damage would be to rewrite the
    From: address in a predictable, comprehensible manner, such as
    the following:

It may be the "quickest" way, but I would consider this the most 
intrusive and even email damaging, extremely harmful suggestion to 
electronic mail communications.

It opens a can of worms, Pandora's box, so to speak, to begin 
suggesting one can modifying and tampering with one the key x822/5322 
mail headers, From:, for any local reason.

In my ethical engineering book, it would just be major TABOO to do 
this. The 5322.From one is the anchor for fundamental electronic mail 
I/O for both networking and non-networking and for other technologies. 
To tamper with it,  it is bound to break other things.

Keep in mind, ADSP also proposed a "radical" DISCARD concept for mail. 
  But because of the ADSP standard track work and synergism at the 
time, we did get RFC2821BIS (RFC5322) to recognize the new reality 
that there are new reasons to ACCEPT and DISCARD rather than ACCEPT 
and BOUNCE without referring to the ADSP work (it was still a draft).

     side note:

     There was also a new modern reality where the SMTP DATA state point
     would be used more as a CALL OUT, SHIM, HOOK to handle new RFC5322
     based Payload technology such as DKIM verification where a ADSP
     policy check would also apply.  One main goal was dynamic processing
     with instant non-bounce notifications.  But with ADSP, there was
     suggestions for an implementation to set a ADSP fail that allows
     the acceptance of mail so it can be quietly discarded. IOW, no
     dynamic 55x rejection at the SMTP level for ADSP fail policies 
because
     that caused problems for the blind mailing list servers.

Yes, it is all complex, but here, the real solution is for John Levine 
and other large list operators to update their mail listing software 
to follow the suggestions in RFC6377:

    RFC6377 DomainKeys Identified Mail (DKIM) and Mailing List

Its not a new problem, its been known since 2006. There are secondary 
DKIM security "wrapper" layers that augment DKIM.  DMARC may be the 
focus, but the issue existed since SSP and ADSP.  If the list service 
is going to resign mail with DKIM, it needs to recognize that DKIM 
does comes with signature security baggage that the not covered by the 
trust model.

So this is a "integration" issue.  Honestly, the changes are not too 
difficult and IMO, it is far less intrusive than changing the 
5322.From.

1) When a new subscriber applies to a list, check for restrictive 
domain policies. Deny subscribers and explain why in the notification 
message.

2) Check for restrictive domains in list mail submissions.

The first one is the piece a cake.  The 2nd one can be more complex 
due to the wider number of software things to do here.

2a) Dynamic SMTP check, reject (55x) the message with policy reason.

2b) Accept message and send a "no access" notification message. 
Explain why.

2c) During the redesign software change, write a one time membership 
scanner to remove restrictive domain members. Send email notification 
explaining why.

Etc.  My main point is that we been doing this for 9+ years.  We knew 
the problems and we have the ideas for solutions.  Whether it was all 
practical and could scale, well, everyone had different opinions here.

But we got a different issue here when list operations don't want to 
change to add policy protocol support but change enough to support a 
pure DKIM-BASE but nothing else.  I fail to see how it can work that way.

This is a "integration" issue and can only be solved using an 
integrated DKIM+POLICY framework and mentality.


-- 
HLS



From mars.techno.cat@gmail.com  Sun Apr 13 11:34:36 2014
Return-Path: <mars.techno.cat@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 456071A0213 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 11:34:36 -0700 (PDT)
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_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 aDhpcljb_fKv for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 11:34:34 -0700 (PDT)
Received: from mail-yk0-x22e.google.com (mail-yk0-x22e.google.com [IPv6:2607:f8b0:4002:c07::22e]) by ietfa.amsl.com (Postfix) with ESMTP id CF6241A0204 for <ietf@ietf.org>; Sun, 13 Apr 2014 11:34:33 -0700 (PDT)
Received: by mail-yk0-f174.google.com with SMTP id 20so6718094yks.19 for <ietf@ietf.org>; Sun, 13 Apr 2014 11:34:31 -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 :content-type:content-transfer-encoding; bh=u967hiWZUXdaobyq13u4jWsJGMFsTNn+pbPa5Eqj9CU=; b=WSgA6JPcvECB3LZc/fI6YvizyYcQLsEGkrkXEUAsaOKJoU3b6paEhxmHHuJHcRs18H 7eh/yZHH+UX79J6jhaq0Pwtydm1EwsLgn5O3b1yl4sqKFIJ4xY0/grUm3Oqg0dcDOGqL sGmeYBF+nTt9Vc6bkrqu+5BNr5JfWBmDrFo7O1rViYT3oRFwjR3jAoz1AdfAeekj0qdx z6jI1GNucpRJEJFLqkqvIwS64Rv+0lpiaUfycqD6B4Cc/LSXldfFMRIsZ1ElFafSgHFE 98X0tvIlASUVbojO0UvJ08pfyvnRBfmB5xTZTsJuRrbaA8jLU8JElkJwwFZNRF9ESuX6 2Z7Q==
MIME-Version: 1.0
X-Received: by 10.236.7.47 with SMTP id 35mr51566046yho.23.1397414071494; Sun, 13 Apr 2014 11:34:31 -0700 (PDT)
Received: by 10.170.146.215 with HTTP; Sun, 13 Apr 2014 11:34:31 -0700 (PDT)
In-Reply-To: <CAHxHggft7P6Zh1WqpM34j_xR3OG3EeCgiz+AMD=B4W0pQ4Ltgg@mail.gmail.com>
References: <CAK41CSRDMN0am9sVY4sd2nmgg-xMR1K8XXxYJ5D27o5aOyJo-g@mail.gmail.com> <CAHxHggft7P6Zh1WqpM34j_xR3OG3EeCgiz+AMD=B4W0pQ4Ltgg@mail.gmail.com>
Date: Sun, 13 Apr 2014 13:34:31 -0500
Message-ID: <CAK41CSQMU0hNz9iDQutFao_-FJbjRg9P6QO5t3hN1wm843K-bw@mail.gmail.com>
Subject: Fwd: WHEN are CERF & CROCKER going to be Accountable...?
From: Techno CAT <mars.techno.cat@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ujsuq1Hly33pHhjcNlqov-6iHqc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 18:36:29 -0000

The first question....NOT answered...was....
...
WHEN are CERF & CROCKER going to be Accountable...?
...
with respect to "you are also free to build your own root"
...
Why would anyone "build a root" in this day and age. That is so 1980s DNS.
Peer-2-Peer DNS & Currency technology has clearly demonstrated the
superior architecture of NON Centralized IANA ICANN etc.
...
As for...."You will soon have many more choices of TLD."
...Jon Postel said that in 1998...



---------- Forwarded message ----------
From: Vint Cerf <vint@google.com>
Date: Sun, Apr 13, 2014 at 9:01 AM
Subject: Re: WHEN are CERF & CROCKER going to be Accountable...?
To: Techno CAT <mars.techno.cat@gmail.com>
Cc: Steve Crocker <steve@shinkuro.com>, Fadi Chehad=C3=A9
<fadi.chehade@icann.org>, kathy brown <brown@isoc.org>, Brian E
Carpenter <brian.e.carpenter@gmail.com>, Miles Fidelman
<mfidelman@meetinghouse.net>


nonsense.

it is easy and cheap to get a domain name at second level or below.
You will soon have many more choices of TLD.
The reason people use the large providers is convenience of not having
to run your own servers.

you are also free to build your own root if you want and try to get
people to use it.

vint



On Sun, Apr 13, 2014 at 9:55 AM, Techno CAT <mars.techno.cat@gmail.com> wro=
te:
>
> "all of this actually unrelated to DMARC"
>
> Really ? Artificial Scarcity IANA DNS policies and Toy Protocols have
> pushed people away from the simple models where people and
> domains were closer to 1 to 1. People were forced into mass
> service providers such as Yahoo. They then want to take their
> email "handles" and use them other places. They did that and now
> are not encouraged to do that.....this ALL can be traced to the
> STONEWALLING of DNS by POSTEL CERF and  CROCKER.....
>
> WHEN are CERF & CROCKER going to be Accountable for THEIR #ICANN #IANA
> #ARIN #ISOC #IETF Eco.System?
> http://mm.icann.org/pipermail/ianatransition/2014-April/000476.html =E2=
=80=A6
> #NTIA #DOJ #FTC
>
> http://mm.icann.org/pipermail/ianatransition/2014-April/000476.html
>
> [IANAtransition] [IANAxfer] DMARC snafu as a wake-up call
>
> Vint Cerf vint at google.com
> Sun Apr 13 11:54:39 UTC 2014
>
> Previous message: [IANAtransition] [IANAxfer] DMARC snafu as a wake-up ca=
ll
> Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>
> ________________________________
>
> Steve's analysis strikes me as the correct one.
>
> see www.dmarc.org
>
> v
>
>
>
> On Sat, Apr 12, 2014 at 9:58 PM, Steve Crocker <steve at shinkuro.com> wr=
ote:
>
> > Apparently I can't post to this list from this email address.  I'm not
> > sure why, but the other readers of this list will have to depend on you=
r
> > inclusion of my message in your reply.  This also means you'll have the
> > last word :)
> >
> > The liability argument you're suggesting is a very slippery slope.  The
> > IANA group does do some checking before changes are made to the entries=
 in
> > the root zone for top level domains, but for general protocol parameter
> > entries I don't believe they do more than make sure entries are distinc=
t.
> >  If expert judgment is needed for a particular protocol parameter regis=
try,
> > that's arranged in advance when the registry is defined by the IETF.
> >
> > But all of this actually unrelated to DMARC.  Anyone can publish whatev=
er
> > they want in his own portion of the DNS tree, and anyone is free to dep=
end
> > upon or ignore what's published.  The DMARC conventions come out of the
> > email community.  There just isn't any direct connection to ICANN or IA=
NA.
> >  Thus, even if the IANA team had wanted to intercede, they couldn't hav=
e.
> >  They simply aren't in that loop.
> >
> > Steve
> >
> > Sent from my iPhone
> >
> > > On Apr 12, 2014, at 9:20 PM, Miles Fidelman <mfidelman at meetinghous=
e.net>
> > wrote:
> > >
> > > Steve,
> > >
> > > Long time, no see.
> > >
> > > In theory, what you say is true.  But... I wouldn't be so cavalier as=
 to
> > assume no liability.  "I was following orders" has never been valid
> > defense, for anything.  And standards bodies have been held liable for
> > failing to exercise a "duty of care."  Re. email, IANA, and by extensio=
n
> > ICANN, does handle various SMTP-extension related stuff.
> > >
> > > Still - a bit offtrack from the transition.
> > >
> > > Miles
> > >
> > > Steve Crocker wrote:
> > >> Miles,
> > >>
> > >> IANA publishes what it's told to publish.  Editorial control lies
> > elsewhere.  The definition of DNS and how it's to be used is done withi=
n
> > the IETF.  Allocation of top level domains is done within ICANN but IAN=
A's
> > role is to execute the decisions that are made in the other parts of IC=
ANN.
> > >>
> > >> The current DMARC problem isn't really even a DNS problem except tha=
t
> > DNS is used to publish DMARC information.  The current DMARC problem is=
,
> > well, a DMARC problem.  The community that defined, implemented and dep=
end
> > upon DMARC are the ones who need to sort this out.  That's the email
> > community.  ICANN does not play a role here.
> > >>
> > >> Steve
> > >>
> > >> Sent from my iPhone
> > >>
> > >>> On Apr 12, 2014, at 7:47 PM, Miles Fidelman <
> > mfidelman at meetinghouse.net> wrote:
> > >>>
> > >>> Sorry - I mentioned it as a cautionary tale, and the thread seems t=
o
> > have exploded.  But... in thinking about it, I will say it sure does se=
em
> > like an IANA/ICANN related issue - given that the DNS system is the veh=
icle
> > that propagates DMARCS policies.
> > >>>
> > >>> Miles
> > >>>
> > >>> Brian E Carpenter wrote:
> > >>>> Miles,
> > >>>>
> > >>>> I understand that you are very seriously inconvenienced by this.
> > >>>> I just think you're reading it wrong from the point of view
> > >>>> of "IANA transition".
> > >>>>
> > >>>>> On 13/04/2014 10:50, Miles Fidelman wrote:
> > >>>>> ...
> > >>>>> After all, what's really causing this DMARC
> > >>>>> debacle is precisely the publication of a DNS record containing
> > >>>>> "p=3Dreject" by Yahoo, multiple large players honoring that recor=
d,
> > >>>> It's inside a TXT record as I understand it. ICANN has absolutely
> > >>>> nothing to do with TXT records. The DMARC draft actually says it
> > >>>> quite well:
> > >>>>
> > >>>>   "DMARC assumes that entities who send messages with their domain=
s in
> > >>>>    the RFC5322.From field and wish to protect those messages with
> > DMARC
> > >>>>    can
> > >>>>
> > >>>>    1.  Control DNS entries for the domains to be protected, includ=
ing
> > >>>>        adding arbitrary new subdomains with TXT records...."
> > >>>>
> > >>>> Therefore, control lies entirely with the domain's controller, Yah=
oo
> > >>>> in this case, according to the DMARC non-standard itself.
> > >>>>
> > >>>> Yahoo has chosen to use a TXT record that is described in an
> > unapproved
> > >>>> draft (that seems unlikely ever to be approved except as an
> > independent
> > >>>> publication) using a format not assigned by IANA (so far).
> > >>>>
> > >>>> That's an issue of Yahoo governance.
> > >>>>
> > >>>>> denying delivery to a huge number of legitimate emails - effectiv=
ely
> > a
> > >>>>> DDoS attack, effected through the DNS system, with no recourse.  =
DNS
> > is
> > >>>>> under IANA and ICANN purvue.
> > >>>> The names in the root zone are under ICANN purvue and the contents
> > >>>> of the various registries are under IANA stewardship.  But there i=
t
> > >>>> ends. Neither of them is responsible for network operations.
> > >>>>
> > >>>>    Brian
> > >>>>
> > >>>>> To me, that makes it a governance issue.
> > >>>>>
> > >>>>> Miles Fidelman
> > >>>
> > >>> --
> > >>> In theory, there is no difference between theory and practice.
> > >>> In practice, there is.   .... Yogi Berra
> > >>>
> > >>> _______________________________________________
> > >>> IANAxfer mailing list
> > >>> IANAxfer at elists.isoc.org
> > >>> https://elists.isoc.org/mailman/listinfo/ianaxfer
> > >
> > >
> > > --
> > > In theory, there is no difference between theory and practice.
> > > In practice, there is.   .... Yogi Berra
> > >
> > > _______________________________________________
> > > IANAxfer mailing list
> > > IANAxfer at elists.isoc.org
> > > https://elists.isoc.org/mailman/listinfo/ianaxfer
> > _______________________________________________
> > IANAxfer mailing list
> > IANAxfer at elists.isoc.org
> > https://elists.isoc.org/mailman/listinfo/ianaxfer
> >
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://mm.icann.org/pipermail/ianatransition/attachments/20140413/c=
b797e99/attachment-0001.html>




--=20
3DNB - Real Banking for Your VIRTUAL Worlds
http://3DNB.COM
Login: ZOOM
Password: BOX

@Techno_CAT_r
http://Twitter.com/Techno_CAT_r


From nobody Sun Apr 13 12:17:13 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D255D1A0210 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 12:17:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.018
X-Spam-Level: *
X-Spam-Status: No, score=1.018 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 6cUigoYLl_tZ for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 12:17:10 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id E78B31A0204 for <ietf@ietf.org>; Sun, 13 Apr 2014 12:17:09 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 4AF41CC099 for <ietf@ietf.org>; Sun, 13 Apr 2014 15:17:07 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kObEt54cjQG5 for <ietf@ietf.org>; Sun, 13 Apr 2014 15:16:58 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7D4CECC096 for <ietf@ietf.org>; Sun, 13 Apr 2014 15:16:58 -0400 (EDT)
Message-ID: <534AE2AA.2000000@meetinghouse.net>
Date: Sun, 13 Apr 2014 15:16:58 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <534A9901.8040907@dcrocker.net>
In-Reply-To: <534A9901.8040907@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/P9gBT55dUcqpv1TntihaxP58ohs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 19:17:11 -0000

Dave Crocker wrote:
> On 4/12/2014 3:23 PM, Brian E Carpenter wrote:
>> Could somebody explain what that means and whether it can be used to
>> mitigate the current issue? Or are substantial changes needed
>> in the fundamentals of DMARC?
>
>
> It means that a receiving system, which otherwise complies with DMARC 
> policy records, has chosen to deviate from a domain owner's request to 
> reject messages that fail DMARC, by virtue of knowing that it went 
> through a mailing list that was trusted.
>
> In other words, it means that the receiving mail system whitelisted a 
> mailing list.
>
Which - I'll note - Yahoo is not providing for.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sun Apr 13 12:21:42 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DEDD1A0258 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 12:21:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.519
X-Spam-Level: 
X-Spam-Status: No, score=0.519 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 DEBuLkl-KJKM for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 12:21:29 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3409E1A0245 for <ietf@ietf.org>; Sun, 13 Apr 2014 12:21:29 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id BD4EDCC09B for <ietf@ietf.org>; Sun, 13 Apr 2014 15:21:26 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id A7oUE91xZcFV for <ietf@ietf.org>; Sun, 13 Apr 2014 15:21:21 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 58749CC099 for <ietf@ietf.org>; Sun, 13 Apr 2014 15:21:21 -0400 (EDT)
Message-ID: <534AE3B1.50606@meetinghouse.net>
Date: Sun, 13 Apr 2014 15:21:21 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <CAA=duU0tNVpdRrjwHX6D5arnNenzOztvpfoPgPLwo2aauMASQg@mail.gmail.com>
In-Reply-To: <CAA=duU0tNVpdRrjwHX6D5arnNenzOztvpfoPgPLwo2aauMASQg@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yNoU_i0kA3pUbhm-HdoGSDfsy7c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 19:21:30 -0000

Andrew G. Malis wrote:
> Dave,
>
> I couldn't help seeing in your email:
>
>     The DMARC specification is not 'an IETF document'.  The current
>     plan is to publish it as an RFC, through the 'Independent' stream,
>     which also is /not/ an IETF activity.
>
>
> when compared to the following at dmarc.org <http://dmarc.org> (on the 
> front page):
>
> "DMARC policies are published in the public Domain Name System (DNS), 
> and available to everyone. It is the goal of DMARC.org to submit the 
> draft specification to the IETF so that it may begin the process of 
> becoming an official Internet Standard RFC - available to everyone for 
> reference, implementation, and improvement."
>
> The statement on dmarc.org <http://dmarc.org> really does look like a 
> misrepresentation.
>

Exactly.  And IETF is complicit by providing the publication vehicle and 
not loudly denying that it's an IETF standards-track protocol, with all 
the associated careful vetting, testing, and maturation over time.  
(There's a reason that folks like Xerox and Kleenex very actively 
protect their brand.)

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sun Apr 13 12:55:20 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152771A0221 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 12:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.943
X-Spam-Level: **
X-Spam-Status: No, score=2.943 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_16=0.6, SPF_NEUTRAL=0.779] autolearn=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 j9TKfV6ueDso for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 12:55:15 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 10CE21A021D for <ietf@ietf.org>; Sun, 13 Apr 2014 12:55:14 -0700 (PDT)
Received: (qmail 37441 invoked from network); 13 Apr 2014 19:55:11 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 13 Apr 2014 19:55:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=60fd.534aeba0.k1404; i=johnl@user.iecc.com; bh=0lZGDVokqhcql7SAOqjZfwygflr/1V+xXorcFQ1VXn4=; b=m5WbFc4D23iOSql53V8Xo9J/YntHUwjqt5muv2R29T8t6jPJuMTkPZiTvns6qobc+Aqq99F2ZLxrnjo07E5r8zmKtZy1elNai6zo3FesD49k00yJnnjROFfQLUCPvL+Etuyl9TkkQdRrb/ko+ilUg3d+V6cvZMicZv9QbABELWrBARY4IyWBnPkR+QXE8+orTVqh7iHD3Qtn2+VA7y9qVE6HMT+PY/RkPc+XeT3I3JEwnV7hBnTiDs3w8JYSISWi
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=60fd.534aeba0.k1404; olt=johnl@user.iecc.com; bh=0lZGDVokqhcql7SAOqjZfwygflr/1V+xXorcFQ1VXn4=; b=iwPnPU1ZnJGMjwRiofMwY80ZUhvZ3q8bRPgvnoRpWWIusRp76EpTNCnC8jFhwBmpdKgT0XK9dpVq+FRQ7MKTlv1x1OyWrtpvYa9321zirkyB6JovNrs/qYkAx3DVptBIgVlJbEvw6OI8llAL6Ld/+vcnDzpKbMezomok6nvDL5rMBMvdBUBAGNrmH1DdAikXgPwiWTDWSszwNbxSdwtg6feN/VairfbuvSKZxm3/MyqAF14FXvsxK+2b2yNwmE3B
Date: 13 Apr 2014 19:54:50 -0000
Message-ID: <20140413195450.24828.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <534A9901.8040907@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/exCk61p3bLsx4BQk8elFQNDlC0U
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 19:55:19 -0000

In article <534A9901.8040907@dcrocker.net> you write:
>On 4/12/2014 3:23 PM, Brian E Carpenter wrote:
>> Could somebody explain what that means and whether it can be used to
>> mitigate the current issue? Or are substantial changes needed
>> in the fundamentals of DMARC?
> ...

>In other words, it means that the receiving mail system whitelisted a 
>mailing list.

Yeah.  The problem is that as we are now seeing from the Yahoo fiasco,
receivers don't whitelist mailing lists, leading to all sorts of
damage to mail that has been working perfectly well and that, if my
experience is any guide, recipients want a lot more than the bulk
blasts that p=reject was designed to handle.

R's,
John


From nobody Sun Apr 13 12:57:23 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 101DD1A02CA for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 12:57:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 kyW4LgXSONDK for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 12:57:20 -0700 (PDT)
Received: from mail-pb0-x236.google.com (mail-pb0-x236.google.com [IPv6:2607:f8b0:400e:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id 7C91A1A0221 for <ietf@ietf.org>; Sun, 13 Apr 2014 12:57:20 -0700 (PDT)
Received: by mail-pb0-f54.google.com with SMTP id ma3so7452290pbc.27 for <ietf@ietf.org>; Sun, 13 Apr 2014 12:57:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bl/AG8NQeeGraHzMXjtKU6m7WCgXii9BLpoeOW26m0Q=; b=mBOSE5rSH3OmzXvZayiwUd8kENaVVZ1gyEv4vgMBEm6R0Q3dWn6UdK05DvS+1N7JQ4 uId2JYY3NjTORV+Yg15fZYk5lqrpChRVl/BWzO5ZtmplTOkZQB9BR80yI67+vYuRYxEC eiE5/oMZz+VCf8SEE/wKb6syCyr3OqMn7EK0vX6e4bUHw+y3cvoZwi7LTsVjZgqocGlr xoUuj+iFZNdI7j36YvkRYxwVRKqqcnzDW73D2Z9XnL/hQDOFgwc1syFIJoCigIDhp5Ez ZKEPOsMwDSHntA1iwZObII/agx2//ouF9ruwQ57ZagRDyrqu+EUZezgi3qCfrWwRySkV 3JzQ==
X-Received: by 10.66.142.201 with SMTP id ry9mr39864831pab.14.1397419038400; Sun, 13 Apr 2014 12:57:18 -0700 (PDT)
Received: from [192.168.178.20] (252.198.69.111.dynamic.snap.net.nz. [111.69.198.252]) by mx.google.com with ESMTPSA id sv10sm29269879pbc.74.2014.04.13.12.57.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Apr 2014 12:57:17 -0700 (PDT)
Message-ID: <534AEC1A.3060502@gmail.com>
Date: Mon, 14 Apr 2014 07:57:14 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <CAA=duU0tNVpdRrjwHX6D5arnNenzOztvpfoPgPLwo2aauMASQg@mail.gmail.com> <534AE3B1.50606@meetinghouse.net>
In-Reply-To: <534AE3B1.50606@meetinghouse.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dqgTEHgqvYUCW3_FyBE1PApsarA
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 19:57:22 -0000

Miles,

On 14/04/2014 07:21, Miles Fidelman wrote:
> Andrew G. Malis wrote:
>> Dave,
>>
>> I couldn't help seeing in your email:
>>
>>     The DMARC specification is not 'an IETF document'.  The current
>>     plan is to publish it as an RFC, through the 'Independent' stream,
>>     which also is /not/ an IETF activity.
>>
>>
>> when compared to the following at dmarc.org <http://dmarc.org> (on the
>> front page):
>>
>> "DMARC policies are published in the public Domain Name System (DNS),
>> and available to everyone. It is the goal of DMARC.org to submit the
>> draft specification to the IETF so that it may begin the process of
>> becoming an official Internet Standard RFC - available to everyone for
>> reference, implementation, and improvement."
>>
>> The statement on dmarc.org <http://dmarc.org> really does look like a
>> misrepresentation.
>>
> 
> Exactly.  And IETF is complicit by providing the publication vehicle and
> not loudly denying that it's an IETF standards-track protocol, with all
> the associated careful vetting, testing, and maturation over time. 
> (There's a reason that folks like Xerox and Kleenex very actively
> protect their brand.)

Hold on though. At the moment the text says, among other things,

   Note that other groups may also distribute
   working documents as Internet-Drafts.  ...

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 4, 2014.

If published in the Independent Stream as an RFC, it will say

   This document is not an Internet Standards Track specification; it is
   published for informational purposes.

   This is a contribution to the RFC Series, independently of any
   other RFC stream.  The RFC Editor has chosen to publish this
   document at its discretion and makes no statement about its value
   for implementation or deployment.  Documents approved for
   publication by the RFC Editor are not a candidate for any level of
   Internet Standard; see Section 2 of RFC 5741.

and might also carry an explicit statement from the IESG along the
YMMV axis.

We know this doesn't prevent marketing people from telling lies
about the status of a document, but the IETF doesn't do so.

    Brian


From nobody Sun Apr 13 13:05:17 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 583271A026B for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 ameKUm22xA7v for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:05:14 -0700 (PDT)
Received: from mail-pb0-x22e.google.com (mail-pb0-x22e.google.com [IPv6:2607:f8b0:400e:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 673D11A0242 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:05:14 -0700 (PDT)
Received: by mail-pb0-f46.google.com with SMTP id rq2so7416074pbb.19 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:05:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=PszJeN6uoV4ydLaFPUclBCM4byrdtUJ7f5hcWTIff1s=; b=H+5NGTGa/wyNUzlYmlb8OYAF+Do8/OX/8EmqzLtexLtSHqDL4u/pvA5SQ/3YciGnG4 8EFTFmPXS4mp3wEIqLeJH94xvmMd0EVu6U8oZL+eWaJnL+m3UhmAoCnB2wv3H+lzh67q ufCpi99ibB5R6Ryzw5WnaBW7gWkhms2fmA5IzAVBs+Q04CoRCnacoESJiGTutn2nlADA im4jC+RE78+LWuUushzCuj36uwcPJKLDvE624BQnZKiR68U4kELjbXEuwiUbx/Px7TcE xaLwRoh6gqthx3lLVUm3QMpCnI6KCtdptshdGa2w/4bqBrHvHsJyY7s9/2CojVMF3Wlc 5aXw==
X-Received: by 10.66.249.233 with SMTP id yx9mr40043925pac.3.1397419512290; Sun, 13 Apr 2014 13:05:12 -0700 (PDT)
Received: from [192.168.178.20] (252.198.69.111.dynamic.snap.net.nz. [111.69.198.252]) by mx.google.com with ESMTPSA id i10sm69525471pat.36.2014.04.13.13.05.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 13 Apr 2014 13:05:11 -0700 (PDT)
Message-ID: <534AEDF4.6080801@gmail.com>
Date: Mon, 14 Apr 2014 08:05:08 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com>
In-Reply-To: <01P6L9JZF5SC00004W@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/L_OrTJMCzNEDB5jb-D7DwS_jInE
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 20:05:15 -0000

Ned (and others),

Thanks for the explanations. Very helpful to a non-expert.

On 13/04/2014 11:35, Ned Freed wrote:
...
> The real question we should be discussing is what options the IETF has to try
> and address this.

Yes please. I don't think it's going to work to dump this problem
in the lap of the Independent RFC Series Editor.

   Brian


From nobody Sun Apr 13 13:08:50 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 724801A0225 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:08:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.164
X-Spam-Level: 
X-Spam-Status: No, score=-0.164 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=ham
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 wPPi1Qt5j7bf for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:08:46 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 139391A0221 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:08:45 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WZQhm-0004RZ-QO; Sun, 13 Apr 2014 20:08:42 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id E326F58026D; Sun, 13 Apr 2014 16:08:41 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1397419721; bh=4IozFJFkuGjI4IXFTfhQAe3uInC9jd/YeTvOrpyYjRo=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LYLwLpZ/JeDv11k5oQkAq3aN0xhEOkvJ5LPTA3baOuqwvlUiZQGwV3rHznjN50Wb3 sw2goRGcTT4WLOnuDQvWEDB50JQbrqzyqgJcWKePex/1c7EXy1sVa6ftD4GXCUIKXS 9Hbj26F+SiH6D8qVNPBEMdXAg6yBQq2XS8NyYKNw=
Date: Sun, 13 Apr 2014 16:08:41 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Message-ID: <20140413200841.GC8122@thunk.org>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <CAA=duU0tNVpdRrjwHX6D5arnNenzOztvpfoPgPLwo2aauMASQg@mail.gmail.com> <534AE3B1.50606@meetinghouse.net> <534AEC1A.3060502@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534AEC1A.3060502@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jDhvMMUh48Iv8yYnb3lRKex2lDE
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 20:08:47 -0000

On Mon, Apr 14, 2014 at 07:57:14AM +1200, Brian E Carpenter wrote:
> Hold on though. At the moment the text says, among other things,
> 
>    Note that other groups may also distribute
>    working documents as Internet-Drafts.  ...
> 
> We know this doesn't prevent marketing people from telling lies
> about the status of a document, but the IETF doesn't do so.

Well, maybe someone like Miles should consider writing an I-D "DMARC
considered harmful", which advises users impacted by Yahoo's diastrous
implementation of DMARC to find another e-mail provider.

Perhaps the metaphorical swatting the nose of these other groups with
a newspaper will help encourage them to avoid abusing the IETF's
reputation in order to market their specification.

					- Ted




From nobody Sun Apr 13 13:22:11 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DE771A0242 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:22:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.018
X-Spam-Level: *
X-Spam-Status: No, score=1.018 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 D5zq6wERGZB7 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:22:09 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id CDCE51A02D2 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:22:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 5FF64CC09F for <ietf@ietf.org>; Sun, 13 Apr 2014 16:22:05 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VMGy8e4Qy7nQ for <ietf@ietf.org>; Sun, 13 Apr 2014 16:22:00 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id D3E69CC09C for <ietf@ietf.org>; Sun, 13 Apr 2014 16:21:59 -0400 (EDT)
Message-ID: <534AF1E7.4070800@meetinghouse.net>
Date: Sun, 13 Apr 2014 16:21:59 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <CAA=duU0tNVpdRrjwHX6D5arnNenzOztvpfoPgPLwo2aauMASQg@mail.gmail.com> <534AE3B1.50606@meetinghouse.net> <534AEC1A.3060502@gmail.com>
In-Reply-To: <534AEC1A.3060502@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/C1YBT4KEvqY6XoBoSLZwRFY-31o
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 20:22:10 -0000

Brian E Carpenter wrote:
> Miles,
>
> On 14/04/2014 07:21, Miles Fidelman wrote:
>> Andrew G. Malis wrote:
>>> Dave,
>>>
>>> I couldn't help seeing in your email:
>>>
>>>      The DMARC specification is not 'an IETF document'.  The current
>>>      plan is to publish it as an RFC, through the 'Independent' stream,
>>>      which also is /not/ an IETF activity.
>>>
>>>
>>> when compared to the following at dmarc.org <http://dmarc.org> (on the
>>> front page):
>>>
>>> "DMARC policies are published in the public Domain Name System (DNS),
>>> and available to everyone. It is the goal of DMARC.org to submit the
>>> draft specification to the IETF so that it may begin the process of
>>> becoming an official Internet Standard RFC - available to everyone for
>>> reference, implementation, and improvement."
>>>
>>> The statement on dmarc.org <http://dmarc.org> really does look like a
>>> misrepresentation.
>>>
>> Exactly.  And IETF is complicit by providing the publication vehicle and
>> not loudly denying that it's an IETF standards-track protocol, with all
>> the associated careful vetting, testing, and maturation over time.
>> (There's a reason that folks like Xerox and Kleenex very actively
>> protect their brand.)
> Hold on though. At the moment the text says, among other things,
>
>     Note that other groups may also distribute
>     working documents as Internet-Drafts.  ...
>
>     Internet-Drafts are draft documents valid for a maximum of six months
>     and may be updated, replaced, or obsoleted by other documents at any
>     time.  It is inappropriate to use Internet-Drafts as reference
>     material or to cite them other than as "work in progress."
>
>     This Internet-Draft will expire on October 4, 2014.
>
> If published in the Independent Stream as an RFC, it will say
>
>     This document is not an Internet Standards Track specification; it is
>     published for informational purposes.
>
>     This is a contribution to the RFC Series, independently of any
>     other RFC stream.  The RFC Editor has chosen to publish this
>     document at its discretion and makes no statement about its value
>     for implementation or deployment.  Documents approved for
>     publication by the RFC Editor are not a candidate for any level of
>     Internet Standard; see Section 2 of RFC 5741.
>
> and might also carry an explicit statement from the IESG along the
> YMMV axis.
>
> We know this doesn't prevent marketing people from telling lies
> about the status of a document, but the IETF doesn't do so.
>
>      Brian

Just pointing out that when marketing people tell lies, pointing to the 
fine print may not be a sufficient response (morally, or legally).

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sun Apr 13 13:22:35 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A0581A02CA for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:22:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.018
X-Spam-Level: *
X-Spam-Status: No, score=1.018 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 GDs_k6jw2hrH for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:22:32 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id A18671A02D3 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:22:32 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 78A2CCC09C for <ietf@ietf.org>; Sun, 13 Apr 2014 16:22:30 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id cbDxtXf1+9O4 for <ietf@ietf.org>; Sun, 13 Apr 2014 16:22:24 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 37DFCCC09F for <ietf@ietf.org>; Sun, 13 Apr 2014 16:22:24 -0400 (EDT)
Message-ID: <534AF1FF.5090503@meetinghouse.net>
Date: Sun, 13 Apr 2014 16:22:23 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <534AEDF4.6080801@gmail.com>
In-Reply-To: <534AEDF4.6080801@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KkdfxiD2byFFC_JiRcUbQvP9dQY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 20:22:33 -0000

Brian E Carpenter wrote:
> Ned (and others),
>
> Thanks for the explanations. Very helpful to a non-expert.
>
> On 13/04/2014 11:35, Ned Freed wrote:
> ...
>> The real question we should be discussing is what options the IETF has to try
>> and address this.
> Yes please. I don't think it's going to work to dump this problem
> in the lap of the Independent RFC Series Editor.
>
>     Brian

Yes!

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sun Apr 13 13:28:47 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46A941A0225 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:28:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.098
X-Spam-Level: 
X-Spam-Status: No, score=0.098 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, J_CHICKENPOX_21=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 ughjl0TjhLRM for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:28:43 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4C4301A0210 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:28:43 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id CF3D1CC0A0; Sun, 13 Apr 2014 16:28:40 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id NV1aiYwws8X8; Sun, 13 Apr 2014 16:28:36 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 01EC0CC09C; Sun, 13 Apr 2014 16:28:35 -0400 (EDT)
Message-ID: <534AF373.1090702@meetinghouse.net>
Date: Sun, 13 Apr 2014 16:28:35 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <CAA=duU0tNVpdRrjwHX6D5arnNenzOztvpfoPgPLwo2aauMASQg@mail.gmail.com> <534AE3B1.50606@meetinghouse.net> <534AEC1A.3060502@gmail.com> <20140413200841.GC8122@thunk.org>
In-Reply-To: <20140413200841.GC8122@thunk.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/odVLt73v5doHBDK9X0159suEOXM
Cc: John Levine <johnl@taugh.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 20:28:44 -0000

Theodore Ts'o wrote:
> On Mon, Apr 14, 2014 at 07:57:14AM +1200, Brian E Carpenter wrote:
>> Hold on though. At the moment the text says, among other things,
>>
>>     Note that other groups may also distribute
>>     working documents as Internet-Drafts.  ...
>>
>> We know this doesn't prevent marketing people from telling lies
>> about the status of a document, but the IETF doesn't do so.
> Well, maybe someone like Miles should consider writing an I-D "DMARC
> considered harmful", which advises users impacted by Yahoo's diastrous
> implementation of DMARC to find another e-mail provider.
>
> Perhaps the metaphorical swatting the nose of these other groups with
> a newspaper will help encourage them to avoid abusing the IETF's
> reputation in order to market their specification.
>
> 					- Ted
>
Hmm.  Good idea.  Though I think John Levine's piece pretty much IS 
"DMARC considered harmful" - just needs to be titled!
http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html
Yahoo breaks every mailing list in the world including the IETF's

As are some of Hector Santos' posts to various lists, re. the recent 
debacle.

Both of whom are probably far more qualified to address the technical 
details (on this one, I can talk primarily from the perspective of 
operational pain, and having to deal with the fallout).

John, Hector - want to collaborate on a "DMARC considered harmful" 
Internet draft?

Miles



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sun Apr 13 13:29:02 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC4D1A02D2 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:28:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.426
X-Spam-Level: 
X-Spam-Status: No, score=0.426 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 bNWhrWHFaXuJ for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:28:52 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id D5ECC1A02CA for <ietf@ietf.org>; Sun, 13 Apr 2014 13:28:52 -0700 (PDT)
Received: from [192.168.2.19] (unknown [99.17.31.1]) by dougbarton.us (Postfix) with ESMTPSA id B8F3222C1F for <ietf@ietf.org>; Sun, 13 Apr 2014 20:28:50 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397420930; bh=UTZlky4cYmU6JNOxJm3sakToBTaF5ddZdCE6CKqA9FI=; h=Date:From:To:Subject:References:In-Reply-To; b=O2LzSXr0aA00t4it/wCA7KnRjP/bsKl2XBciDM5h5KlhNZZY7sB1G1tmdwBAwQEe/ T7oGm5KGjK0ELJ2tUQvgJwxuCNIiwOTpaiOj30BVRQ44eZ2sHDymP7go0xOfjhcXKk +rHaScH+yEg0qkp/gFPZZ3T3ia0+4H+BFqgjpfO8=
Message-ID: <534AF382.1030806@dougbarton.us>
Date: Sun, 13 Apr 2014 13:28:50 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
In-Reply-To: <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eeN4nczG9ZHl0sxqjgApNCdEt-Y
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 20:28:57 -0000

On 04/07/2014 10:06 PM, Sabahattin Gucukoglu wrote:
> On 8 Apr 2014, at 05:21, John R Levine <johnl@taugh.com> wrote:
>> Mailing list apps can't "implement DMARC" other than by getting rid of every feature that makes lists more functional than simple forwarders. Given that we haven't done so for any of the previous FUSSPs that didn't contemplate mailing lists, because those features are useful to our users, it seems unlikely we'll do so now.
>
> Well,  Mailman 2.1.16 has the FROM_IS_LIST feature that "Fixes" the problem by putting the list address in the From: field.  That seems to work, except that you lose information (the sender's address) if the list wants to operate a policy of "Reply goes to list".  You can then assure that DKIM signatures are valid and set up SPF, etc.  This also has the effect of letting you operate through the various cloud email platforms that try to validate sender addresses.

I haven't seen this suggestion anywhere yet, although I don't follow 
DMARC development, but here goes ...

Building on the FROM_IS_LIST idea, rather than having the From be 
rewritten to simply "list@example.com" why not establish a convention 
(dare I say "standard?") to encode the real from address and list to the 
left of the @ sign? The rub with DMARC/SPF/DKIM is the domain itself, 
not the whole address.

Something like user.name-at-realsenderdomain.tld%list@example.com would 
work. I'm sure others could come up with better suggestions. In this way 
the identity of the sender is preserved, and the sending domain of the 
message satisfies the anti-spam tools. MUAs could then be adapted to 
decode the addresses in this form and show a "real" fake From field.

Given that tools like DMARC more or less work for everything but mailing 
lists (I'm being generous here in the interests of re-framing the 
discussion into solutions instead of griping), and given that mailing 
lists constitute a tiny percentage of overall e-mail traffic, I think 
that the solutions to this problem are going to lie with the mailing 
list software vendors. I think the above would work, but I'm not an 
expert in this area so feel free to tell me why I'm wrong.

Doug


From nobody Sun Apr 13 13:42:21 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7B361A0231 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 Vyt2SD2s6ZfW for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:42:13 -0700 (PDT)
Received: from mail-yk0-x22a.google.com (mail-yk0-x22a.google.com [IPv6:2607:f8b0:4002:c07::22a]) by ietfa.amsl.com (Postfix) with ESMTP id C64811A0226 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:42:13 -0700 (PDT)
Received: by mail-yk0-f170.google.com with SMTP id 9so6782541ykp.15 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:42:11 -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:from:date:message-id :subject:to:cc:content-type; bh=NVqYJ+9AODUucOv5drSnsdtpsTeb/Zvxbbz+OzSiOoI=; b=NxDpTJv8hIkgV3tT1KrdAtE1yzxAfB1Xexcal8jVej3RwQs+fJ5ypWgsx/Ae0JQzXX keqsJGMw44BOUIljY3Z5eXttSt6a0Wwi3eEKeyScVgbUoZjjJ84GQ38OVCZpdep/Z7m6 J6VJFnwkIPijHUCjcdE5Ux++gBjTZjWKX3N+X5skCPMAKlZO89BX8hutIqPnAi1A7YG0 8TWi5InpBK0GUUOQI7UfTCGyFCd9JKULNxk8mpr/Hz1CDNgD9kNN5GG9p8UXMnIbYWT0 6qIkbWngwFnMB7AGJNcA6qj+5WhXnIqVDcsFn2qUFJn1AHNYRc9n4pX/h2gosgBbniN3 +dyg==
X-Received: by 10.236.133.67 with SMTP id p43mr71764yhi.114.1397421731547; Sun, 13 Apr 2014 13:42:11 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Sun, 13 Apr 2014 13:41:31 -0700 (PDT)
In-Reply-To: <01P6L9JZF5SC00004W@mauve.mrochek.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com>
From: Dick Franks <rwfranks@acm.org>
Date: Sun, 13 Apr 2014 21:41:31 +0100
X-Google-Sender-Auth: etXg7F_J5hbDfstKaRK6C-oL12U
Message-ID: <CAKW6Ri5N8kpoMkW_qvqBfRzvrsCfP+9r1ybmpuBc0mHm1G0J0Q@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
To: ned+ietf@mauve.mrochek.com
Content-Type: multipart/alternative; boundary=20cf303e9fcee9101a04f6f299bc
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tr56Uf-bdDXk8q8EimmwppcEtbQ
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 20:42:14 -0000

--20cf303e9fcee9101a04f6f299bc
Content-Type: text/plain; charset=UTF-8

On 13 April 2014 00:35, <ned+ietf@mauve.mrochek.com> wrote:
[snip]

>
> The real question we should be discussing is what options the IETF has to
> try
> and address this.
>

IETF has already adequately addressed this issue by its insistence on
inclusion of this statement in the document preamble:

  It is inappropriate to use Internet-Drafts as reference


  material or to cite them other than as "work in progress."

An implementation based on I-D reference material is therefore no
better than "work in progress".


The blame for this debacle lies squarely with Yahoo, and its
inadequate engineering change management.

--20cf303e9fcee9101a04f6f299bc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_quote">On 13 April 2014 00:35,  <span =
dir=3D"ltr">&lt;<a href=3D"mailto:ned+ietf@mauve.mrochek.com" target=3D"_bl=
ank">ned+ietf@mauve.mrochek.com</a>&gt;</span> wrote:<br></div><div class=
=3D"gmail_quote">


[snip]<br></div><div class=3D"im"><div class=3D"gmail_quote"><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex">
<br>
The real question we should be discussing is what options the IETF has to t=
ry<br>
and address this.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">IETF has already ad=
equately addressed this issue by its insistence on inclusion of this statem=
ent in the document preamble:<br></div><div class=3D"im"><pre>  It is inapp=
ropriate to use Internet-Drafts as reference<br>


  material or to cite them other than as &quot;work in progress.&quot;<br><=
br></pre></div><pre>An implementation based on I-D reference material is th=
erefore no better than &quot;work in progress&quot;.<br><br></pre><pre>

The blame for this debacle lies squarely with Yahoo, and its inadequate eng=
ineering change management.<br>
</pre></div>

--20cf303e9fcee9101a04f6f299bc--


From nobody Sun Apr 13 14:10:53 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8625E1A0237 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 14:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.343
X-Spam-Level: **
X-Spam-Status: No, score=2.343 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 ImvJgIaqUa51 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 14:10:49 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3582F1A0235 for <ietf@ietf.org>; Sun, 13 Apr 2014 14:10:48 -0700 (PDT)
Received: (qmail 3797 invoked from network); 13 Apr 2014 21:10:45 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 13 Apr 2014 21:10:45 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=6271.534afd56.k1404; i=johnl@user.iecc.com; bh=0GQ8Tyn+7w6M7VPrhT5fNGtii/gGhozJkX450dHLkyo=; b=J1a7op3aQypBhcPeqN9A93H5vMkZzwC23fkOPqCwdtK9nkHwnhbl0JEZNkKUPUKyqCivKyjHfBpcZ70VaaAbE/PkO760JPBEm+Zh4WcYpYf49Tqn0mRNlOY63FCJrTNqSkEZIM5ZwoTzaHhfa6dIrwy+FIfs7x6sXfa+YrInP7ifILyPjn5weJYncV4asLkXLux9pK5956brcsa4BfxzJxxw6JB+ihU6ZrD7vPMPKtevR/bPPw7gSTEh/+aDXSCA
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=6271.534afd56.k1404; olt=johnl@user.iecc.com; bh=0GQ8Tyn+7w6M7VPrhT5fNGtii/gGhozJkX450dHLkyo=; b=pp+jUR/Drw18Z9mRemIwqGDihQAp7C4q/zq5AMvK3AUP1DC7+ZaOsp63o8DRL8CcbaPSE7vn/e96wXs/41ImsTMHG5EN0za21ce0sJOliOAJ7nx+r4v/HpW+1KpUmAHS+kYLIlzzBqomI8vWlZgzRpCa+ljcFevefbMfnhqys9ojk4jZed3v1E6Adx8EmqJRlSPrIPbUF4OAjDaAVJRuErwkq/PUV5rF89Z8zeoQW05tcLRMe7HS95qs4ShZ+C+Q
Date: 13 Apr 2014 21:10:24 -0000
Message-ID: <20140413211024.25200.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534AF382.1030806@dougbarton.us>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UGU3_a7hp0eUBOswUFoF3PP0-9A
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 21:10:51 -0000

>Building on the FROM_IS_LIST idea, rather than having the From be 
>rewritten to simply "list@example.com" why not establish a convention 
>(dare I say "standard?") to encode the real from address and list to the 
>left of the @ sign? The rub with DMARC/SPF/DKIM is the domain itself, 
>not the whole address.

This is a minor tweak of the "authenticated phish via on-behalf-of" proposal.

Spammers can send mail that looks a lot like mailing lists, you know.

 From: Paypal Security <security@paypal.com.lists.rbn.ru>

But wait, I have an even better idea, Nobody ever thought of this one!

 From: Paypal Security <security%paypal.com@lists.rbn.ru>

R's,
John

PS: You can safely assume that any possible workaround for mailing
list From: lines has been invented, argued about, and discarded at
least a dozen times already.  The response to pretty much all of them
is that you have to know it's a real mailing list to trust the hack,
but if you know it's a real mailing list, just deliver the fripping
mail.


From nobody Sun Apr 13 18:59:26 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADD6A1A02FB for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 18:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 5-b45PGhDFrs for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 18:59:24 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 598C71A02F8 for <ietf@ietf.org>; Sun, 13 Apr 2014 18:59:24 -0700 (PDT)
Received: from [192.168.4.101] (unknown [67.159.169.102]) by dougbarton.us (Postfix) with ESMTPSA id 9A4C222B1A for <ietf@ietf.org>; Mon, 14 Apr 2014 01:59:21 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397440761; bh=d4ldePIyszqgKaHvpSXSgWCIZt1wu5diibdhLCrC8OA=; h=Date:From:To:Subject:References:In-Reply-To; b=q4XiQFGiTHS4D2/hKX/QEW17SaeSp5HrHs1JbprCeY9X8xaNaXiVggNWYmUhi2+oA /9u53iqDcgIoAq28XGJ7bH5IjX1JT/GKRbsLM73lYJ77PfSQJ29wq/kfSHSNFJjDUl kLXNqDMgkiFIITcDZdCzm85ACyP626AqHluHieX4=
Message-ID: <534B40F8.1000808@dougbarton.us>
Date: Sun, 13 Apr 2014 18:59:20 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140413211024.25200.qmail@joyce.lan>
In-Reply-To: <20140413211024.25200.qmail@joyce.lan>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QFk9s67YqRywpQc0tGuXxebAzyQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 01:59:25 -0000

On 04/13/2014 02:10 PM, John Levine wrote:
>> Building on the FROM_IS_LIST idea, rather than having the From be
>> rewritten to simply "list@example.com" why not establish a convention
>> (dare I say "standard?") to encode the real from address and list to the
>> left of the @ sign? The rub with DMARC/SPF/DKIM is the domain itself,
>> not the whole address.
>
> This is a minor tweak of the "authenticated phish via on-behalf-of" proposal.

It's not, actually. The defects in XOAR are obvious even to me.

> Spammers can send mail that looks a lot like mailing lists, you know.

What does that have to do with anything? If the message authenticates 
via DMARC/SPF/DKIM then that's a point in its favor in terms of it not 
being spam. If the message comes through with a From: that "looks like a 
mailing list" who cares? Even if that message passes all of the other 
spam filtering mechanisms between it and the user, the user is likely to 
know if they are signed up for a mailing list that the spam message is 
trying to fake, even if it isn't obvious on its face that it's spam to 
start with.

>   From: Paypal Security <security@paypal.com.lists.rbn.ru>

DMARC/SPF/DKIM will actually benefit that message if it has a valid 
signature. Nothing "mailing list" related about it.

> But wait, I have an even better idea, Nobody ever thought of this one!
>
>   From: Paypal Security <security%paypal.com@lists.rbn.ru>

Same here. And again, if the message comes through with a valid 
signature it's less likely to get caught as spam.

Meanwhile, I'm still not proposing that we train users, or even 
anti-spam software to "recognize" or "validate" mailing list addresses. 
What I'm proposing is a way to send mail from a list with From: 
@domain-of-list.tld so that it can pass DMARC/SPF/DKIM, and allow the 
left side of the @ sign to identify the actual sender of the message.

Doug


From nobody Sun Apr 13 19:50:27 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 622921A031C for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 19:50:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.343
X-Spam-Level: **
X-Spam-Status: No, score=2.343 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 dvdv_lQqpc3L for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 19:50:21 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1F74B1A0309 for <ietf@ietf.org>; Sun, 13 Apr 2014 19:50:20 -0700 (PDT)
Received: (qmail 63711 invoked from network); 14 Apr 2014 02:50:18 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 14 Apr 2014 02:50:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=65df.534b4cea.k1404; i=johnl@user.iecc.com; bh=BYN9UG+3H1WguM+bnjqB1b8qLy64hWyx+nZv6w1HD1w=; b=nyXwB3ZV/9fLo2ioD5OofiaejCEWfdQcoYhdvJsj4v0Me5quMPx/Rc7GdV82oPNvy/kvvmtFJhzBJ7vGTDfm//xAqhBJtu8EDHhKaUElke8lxOZl/8Px40Z/CwLqB41+EDQZvoSTso9JvE3pR8UWHKUW3/ffgKepKLIXgccoP9VCraF7LL2Helr7eff/WcgOOZD2ptJRwR1o9LTWqAgdDXQLrHVuDg2fs5GJGPPP/dOenx2SeGpVqHmzQot8DqFP
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=65df.534b4cea.k1404; olt=johnl@user.iecc.com; bh=BYN9UG+3H1WguM+bnjqB1b8qLy64hWyx+nZv6w1HD1w=; b=veVt9XZlXkoHPqwxscAyTzK4w1anQaPfGQQ6CB+S2pAl2ZGCCSXdBKC3Zk0V3QuLDt4PXvv6dYaZUB6c6mMERmrjG0KreVN1U4FJu/TTqbmYcd6UvwluihY06pWYq69q61A/77Pa2NjMVBlh8KZ45AOa9l8DAEf5mK0aghogn5ImPOWQkEBl/0+t79x/Fkt6E/lZwR/ge2heoNAOfAMhPFRgEuVTSNZVGcMrylSiShJhTS63SSawrQpScZgBIFOE
Date: 14 Apr 2014 02:49:56 -0000
Message-ID: <20140414024956.26078.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534B40F8.1000808@dougbarton.us>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4RrgLq_tmlPmA2b-E6POqOls4k4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 02:50:25 -0000

>Meanwhile, I'm still not proposing that we train users, or even 
>anti-spam software to "recognize" or "validate" mailing list addresses. 
>What I'm proposing is a way to send mail from a list with From: 
>@domain-of-list.tld so that it can pass DMARC/SPF/DKIM, and allow the 
>left side of the @ sign to identify the actual sender of the message.

Yes, that's the 1980s percent hack.  Do you really think it's a good
idea to reinvent it to get around the defects of the FUSSP du jour?

I agree that it's not plausible to train people to recognize mailing
list addresses.  But what you're proposing is to train people to be
phished, by telling them that a rewritten address from something that
looks sort of like a mailing list is equivalent to whatever the
original address was.  Given that DMARC is supposed to be an
anti-phishing tool, this completely defeats the point.

R's,
John


From nobody Sun Apr 13 19:57:42 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C15941A0319 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 19:57:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Xlh1u1uVbFXq for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 19:57:39 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6B8711A0315 for <ietf@ietf.org>; Sun, 13 Apr 2014 19:57:39 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id D2EC2CC0A4 for <ietf@ietf.org>; Sun, 13 Apr 2014 22:57:36 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6iJmfJU3lK9Q for <ietf@ietf.org>; Sun, 13 Apr 2014 22:57:28 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 2E6E9CC0A1 for <ietf@ietf.org>; Sun, 13 Apr 2014 22:57:28 -0400 (EDT)
Message-ID: <534B4E97.2050000@meetinghouse.net>
Date: Sun, 13 Apr 2014 22:57:27 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan>
In-Reply-To: <20140414024956.26078.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mvi_tXh3P2yBnSGtesGkwfOupAQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 02:57:41 -0000

John Levine wrote:
>> Meanwhile, I'm still not proposing that we train users, or even
>> anti-spam software to "recognize" or "validate" mailing list addresses.
>> What I'm proposing is a way to send mail from a list with From:
>> @domain-of-list.tld so that it can pass DMARC/SPF/DKIM, and allow the
>> left side of the @ sign to identify the actual sender of the message.
> Yes, that's the 1980s percent hack.  Do you really think it's a good
> idea to reinvent it to get around the defects of the FUSSP du jour?
>
> I agree that it's not plausible to train people to recognize mailing
> list addresses.  But what you're proposing is to train people to be
> phished, by telling them that a rewritten address from something that
> looks sort of like a mailing list is equivalent to whatever the
> original address was.  Given that DMARC is supposed to be an
> anti-phishing tool, this completely defeats the point.
>
> R's,
> John

It strikes me that the real way to address some of these issues is to 
add a few new headers to SMTP - to get rid of the overloading of the 
From: and Reply-to: headers associated with mailing lists.  An SMTP 
extension that would absorb some of the well-known and well-understood 
functions of list software.

I have to think a bit about what the full list of headers might be, but 
I'd start with:
From: <original author>
List-From: <mailing list>
Reply-To-Original:
Reply-To-List: <set by list manager>
List-Name:
DKIM signature stuff applied to original message
DKIM signature applied by list server

That might be a start toward a real solution that solves both sets of 
problems.

Then again - it's late, I'm in the middle doing my taxes - this might 
not make any sense at all.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sun Apr 13 20:15:35 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4B731A031A for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 20:15:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.126
X-Spam-Level: *
X-Spam-Status: No, score=1.126 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 bbwbcby90coR for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 20:15:31 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id BCEB51A0315 for <ietf@ietf.org>; Sun, 13 Apr 2014 20:15:31 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6LZ78VGSW0059W2@mauve.mrochek.com> for ietf@ietf.org; Sun, 13 Apr 2014 20:10:28 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6J01PRR8W00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 13 Apr 2014 20:10:22 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6LZ76HYUG00004W@mauve.mrochek.com>
Date: Sun, 13 Apr 2014 19:48:15 -0700 (PDT)
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-reply-to: "Your message dated Sun, 13 Apr 2014 13:28:50 -0700" <534AF382.1030806@dougbarton.us>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <E2D6EA08-144D-4DB3-ABFC-6F98AF3C588F@me.com> <534AF382.1030806@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pB_syuPXEi3FbI10T-WX9TMNRg4
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 03:15:33 -0000

> On 04/07/2014 10:06 PM, Sabahattin Gucukoglu wrote:
> > On 8 Apr 2014, at 05:21, John R Levine <johnl@taugh.com> wrote:
> >> Mailing list apps can't "implement DMARC" other than by getting rid of every feature that makes lists more functional than simple forwarders. Given that we haven't done so for any of the previous FUSSPs that didn't contemplate mailing lists, because those features are useful to our users, it seems unlikely we'll do so now.

> > Well,  Mailman 2.1.16 has the FROM_IS_LIST feature that "Fixes" the problem
> > by putting the list address in the From: field.  That seems to work, except
> > that you lose information (the sender's address) if the list wants to operate a
> > policy of "Reply goes to list".  You can then assure that DKIM signatures are
> > valid and set up SPF, etc.  This also has the effect of letting you operate
> > through the various cloud email platforms that try to validate sender
> > addresses.

> I haven't seen this suggestion anywhere yet, although I don't follow
> DMARC development, but here goes ...

> Building on the FROM_IS_LIST idea, rather than having the From be
> rewritten to simply "list@example.com" why not establish a convention
> (dare I say "standard?") to encode the real from address and list to the
> left of the @ sign? The rub with DMARC/SPF/DKIM is the domain itself,
> not the whole address.

No, the rub with DMARC in this case is the choice of a p=reject policy by
a site that doesn't meet the requirements for its use.

> Something like user.name-at-realsenderdomain.tld%list@example.com would
> work. I'm sure others could come up with better suggestions. In this way
> the identity of the sender is preserved, and the sending domain of the
> message satisfies the anti-spam tools.

The From: identity is NOT preserved. There isn't an user agent in the world
that would know how to deal with this. So when people reply, their message
bounces.

Of course there are other tricks you can play, such as making an address that
actually works. But while this trick works for things like SRS, in the case
of a user-visible address, it makes a mess.

> MUAs could then be adapted to
> decode the addresses in this form and show a "real" fake From field.

Uh huh. Even assuming you could get some traction on this with user agents - a
type of software collectively notorious for being slow to adapt, implement, and
update pretty much everything, you then have to get this deployed quickly to do
any good.

> Given that tools like DMARC more or less work for everything but mailing
> lists (I'm being generous here in the interests of re-framing the
> discussion into solutions instead of griping),

You're not being generous, you're being inaccurate. And even if this was
accurate, you don't call for a change to every MLM and every UA in the world to
address a completely inappropriate policy choice.

> and given that mailing
> lists constitute a tiny percentage of overall e-mail traffic, I think
> that the solutions to this problem are going to lie with the mailing
> list software vendors. I think the above would work, but I'm not an
> expert in this area so feel free to tell me why I'm wrong.

Riiight. Penalize longstanding practice on the basis of traffic percentages.

By that measure, spam wins.

				Ned


From nobody Sun Apr 13 20:15:52 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D21D1A031F for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 20:15:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 eHhHSRs6A9e4 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 20:15:34 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E8F2F1A0315 for <ietf@ietf.org>; Sun, 13 Apr 2014 20:15:33 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3E3FS0e024296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 13 Apr 2014 20:15:31 -0700
Message-ID: <534B524F.4050206@dcrocker.net>
Date: Sun, 13 Apr 2014 20:13:19 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan>
In-Reply-To: <20140414024956.26078.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 13 Apr 2014 20:15:31 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PK_92HxYFocd2Go87WjrwDuoSbQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 03:15:35 -0000

On 4/13/2014 7:49 PM, John Levine wrote:
>> Meanwhile, I'm still not proposing that we train users, or even
>> anti-spam software to "recognize" or "validate" mailing list addresses.
>> What I'm proposing is a way to send mail from a list with From:
>> @domain-of-list.tld so that it can pass DMARC/SPF/DKIM, and allow the
>> left side of the @ sign to identify the actual sender of the message.
>
> Yes, that's the 1980s percent hack.


1979, to be precise, for MMDF's relaying telephone/Arpanet mail with the 
original funding agency, the Army Materiel Command, and then the NSF's 
CSNet.  It was difficult to find a character that made any intuitive 
sense and wasn't already taken.

As an overall construct, in this case, it might work pretty well.  It 
preserves all of the original address in a way that is easily 
machine-parseable.

It treats the list engine as a kind of gateway.  This means that a reply 
to that address will show up at the list host and needs to be relayed to 
the intended recipient.  While a bit inefficient -- and probably will 
emerge as an attack vector (sigh) -- it's a plausible mechanism.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Apr 13 20:28:58 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF1741A0322 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 20:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 XAGQ797280VO for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 20:28:55 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id DB73C1A01C7 for <ietf@ietf.org>; Sun, 13 Apr 2014 20:28:54 -0700 (PDT)
Received: (qmail 70778 invoked from network); 14 Apr 2014 03:28:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=11479.534b55f4.k1404; bh=6DjafW8R3ksSJrAWTB7xFXqGDNMdoBTgCj5dBZ8dceg=; b=O47tss5YqL7/zBJhnvTk+5wHvWUpngFrT1FkG+Ga/JlTB3ax7JuZbMBA+PKFFS8t/SJan0OJ7gUu0QVgGPu185YcjpnOTKcn6eogryQSCv9pRgrJQYTf6CTjnjkHhwR4pQRNDpHedOWr8mydj1HLRX10ETU8IR2YqFrWlueuTHWgMx4z9WkmFRuU80f8+jF+Ri/+OBE5pBZ6eAuUGEnu4XhQp4iQpLaja4SJao2WR6qQz3AZm0tRJOKvzgIUCUuJ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=11479.534b55f4.k1404; bh=6DjafW8R3ksSJrAWTB7xFXqGDNMdoBTgCj5dBZ8dceg=; b=uXh/b0O+8Ph28tkzQg3Byvn2JAS25WbVrJkAs12zoi/AxwfOEpulvKlQAQ/8OeTpVLmKD8vWLwkmsDP/mb3Mu+Om7bfw3SvEylOc5qGssjhk2YKyC302F9NC7vjLXqkc5+nb4Xvz2tBecDHkSlTFqX7BkYjKhanXI8NOQniCkRv5yVAaBkChEn6zudaqK45XanwdYXZ5EsfEO1zBD+q4i1zswTwMrmLzqgoTOYztfyD2M/9u4KWtQ5g+Xl/7R4WB
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 14 Apr 2014 03:28:52 -0000
Date: 13 Apr 2014 23:28:52 -0400
Message-ID: <alpine.BSF.2.00.1404132327560.26258@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Dave Crocker" <dcrocker@bbiw.net>, "IETF general list" <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534B524F.4050206@dcrocker.net>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dtWh9Kpw54c3L0mwPs-1IOyVbs4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 03:28:56 -0000

>> Yes, that's the 1980s percent hack.

> intended recipient.  While a bit inefficient -- and probably will emerge as 
> an attack vector (sigh) -- it's a plausible mechanism.

Right -- something is seriously wrong with DMARC as used if we need to 
invent new phish syntaxes to work around it.

R's,
John


From nobody Sun Apr 13 20:44:46 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE4BE1A032C for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 20:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level: 
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 2ZOLSNm05UnA for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 20:44:44 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 35DCB1A0328 for <ietf@ietf.org>; Sun, 13 Apr 2014 20:44:44 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WZXoi-000417-S0; Sun, 13 Apr 2014 23:44:20 -0400
Date: Sun, 13 Apr 2014 23:44:15 -0400
From: John C Klensin <john-ietf@jck.com>
To: John R Levine <johnl@taugh.com>, Dave Crocker <dcrocker@bbiw.net>, IETF general list <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com>
In-Reply-To: <alpine.BSF.2.00.1404132327560.26258@joyce.lan>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uEIqOKGp5xg9p7pwEXjlTzT0vW8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 03:44:45 -0000

--On Sunday, April 13, 2014 23:28 -0400 John R Levine
<johnl@taugh.com> wrote:

>>> Yes, that's the 1980s percent hack.
> 
>> intended recipient.  While a bit inefficient -- and probably
>> will emerge as  an attack vector (sigh) -- it's a plausible
>> mechanism.
> 
> Right -- something is seriously wrong with DMARC as used if we
> need to invent new phish syntaxes to work around it.

Sadly, there are a non-trivial number of MTA installations whose
implementers or operators, having discovered that they had not
seen a legitimate use of the percent hack in years, decided that
they were about as likely to appear in legitimate messages as
source routing and dealt with them accordingly.  Put more
simply, a "%" in a local-part may be least as likely to get a
message rejected or dumped as a badly specified DMARC record, so
the one is really not a very good cure for the other.

    john




From nobody Sun Apr 13 21:10:35 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4AA01A032C for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 21:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 0nJLLg0rootb for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 21:10:29 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD561A0330 for <ietf@ietf.org>; Sun, 13 Apr 2014 21:10:28 -0700 (PDT)
Received: (qmail 76324 invoked from network); 14 Apr 2014 04:10:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=12a23.534b5fb1.k1404; bh=iWwEktwxUc3o7mtsajWuh8IwaQbBiaEmWY+rVmnpDu8=; b=kdwJQGuvjqYW02SmMnF035Smllapks+iB9U2tmsBTu3VXzz55IuqkX1sb/Kq7ZcjLR38IuRwygu/LFrp3TSB97YOJImxJ9VqX54KA8/xRvEZzQa832N5RPHp6gq6ZrhVWLNd2KGyACSxjW4BOW0vh3petZespPfrr40wCZNsWPNRNqAWElquyk0GrBrL3IQJAcYLp4LAvNxTDEFr3TNTzHzcknmeaPZV808GulmNpiaOpSJMAAuxgvOsUuLJ/gsL
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=12a23.534b5fb1.k1404; bh=iWwEktwxUc3o7mtsajWuh8IwaQbBiaEmWY+rVmnpDu8=; b=J2Q0y4XYJ1E84UtqD8AI7fCLUhTVR8oE4wrUkm9tWvWyh5sPTeT5B0fsE3BcCzEAQaKR/W5aEhUQ2xmTvAHNEdiSvbTZm7j5CettjOVWujGe4pRLn3QWE/jmdGTdYYvxBaVPXqUEx05ZajIK4OjyFJi5V2p2vvPlhr2FeFTvJ5fqvEXhA+DmHjAC9NlnW0eGimYS4mVZHsjrj+8zBLxyth6P66tPMhBIZ2fhmnQ8qvCcqXo92o6dH8QmiIP2SbjK
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 14 Apr 2014 04:10:25 -0000
Date: 14 Apr 2014 00:10:25 -0400
Message-ID: <alpine.BSF.2.00.1404132346420.26386@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "John C Klensin" <john-ietf@jck.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bhIvZFjfyp6EVWXtdmfstPAIfbU
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 04:10:33 -0000

> Sadly, there are a non-trivial number of MTA installations whose
> implementers or operators, having discovered that they had not
> seen a legitimate use of the percent hack in years, decided that
> they were about as likely to appear in legitimate messages as
> source routing and dealt with them accordingly.  Put more
> simply, a "%" in a local-part may be least as likely to get a
> message rejected or dumped as a badly specified DMARC record, so
> the one is really not a very good cure for the other.

Since the percent hack became a famous vector for open relay abuse, so we 
all stopped honoring it.  A lot of MTAs still reject anything with a % 
saying something like no more source routing.  Mine does.

So this would require inventing something with the same semantics as the 
percent hack, but a different syntax.  Perhaps we can use an exclamation 
point.

Regards,
John Levine, ima!johnl@cca.arpa
Please consider the environment before reading this e-mail.


From nobody Sun Apr 13 21:12:02 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 809F81A032C for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 21:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 LcYmwaYVkRrD for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 21:11:49 -0700 (PDT)
Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtpout001.mac.com [17.172.220.236]) by ietfa.amsl.com (Postfix) with ESMTP id B9EB81A0331 for <ietf@ietf.org>; Sun, 13 Apr 2014 21:11:49 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N40002ZJ6B5ND90@st11p02mm-asmtp001.mac.com> for ietf@ietf.org; Mon, 14 Apr 2014 04:11:31 +0000 (GMT)
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <534B40F8.1000808@dougbarton.us>
Date: Mon, 14 Apr 2014 05:11:29 +0100
Content-transfer-encoding: quoted-printable
Message-id: <33951EF9-4C5A-4594-A34B-589D583002B9@me.com>
References: <20140413211024.25200.qmail@joyce.lan> <534B40F8.1000808@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaGBEKTEMXGx0EGx0YBBIZBBscEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsbGmJCH2luHARwGXhzB xlvGh4bG3weEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGxwQGx4aHxsRCl5ZF2FNe3l lEQpMRhdia2sRCkNaFxgbGQQbGBkEGxMYBBkaEQpEWBcYEQpESRcbEQpCRRdmUH1dH21kGgVIY xEKQk4XbHBgeUAdYlJpGmIRCkJMF2dJH215aRh+ckJNEQpCbBdlaGUYbU0cGENGThEKQkAXb0J QXX1NaX4dG1ARCnBoF2wSXm9cewFDeF9/EQpwaBdoQXBmf2xoY2tIHBEKcGgXYkNwaXt6TkVZG 14RCnBoF2gbeFBQTlkSbR5SEQpwaBdiWUFrWE4cGl1QaREKcGwXa2ZOa0FlX2ZTZwERCnBMF2I Tem1zBXgBQF9NEQ==
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-12_01:2014-04-11,2014-04-12,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404140078
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/o-xyOzlv7AbwfCnxjLST5bN6xFU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 04:11:54 -0000

On 14 Apr 2014, at 02:59, Doug Barton <dougb@dougbarton.us> wrote:
> Meanwhile, I'm still not proposing that we train users, or even =
anti-spam software to "recognize" or "validate" mailing list addresses. =
What I'm proposing is a way to send mail from a list with From: =
@domain-of-list.tld so that it can pass DMARC/SPF/DKIM, and allow the =
left side of the @ sign to identify the actual sender of the message.

I agree.  In fact, I'm resigned to it already.  OTOH, you'll find the =
idea unpopular around here. :)

FWIW: I really do believe it is a great shame that DMARC misplaces the =
burden so profoundly.  Also, I've stopped caring--the fact is that given =
the choice of:
1.  Authenticate every message from everybody without discrimination, at =
the cost of making mailing lists a lot less like they were in the Good =
Old Days (=99) and breaking a ton of compatibility
2.  Authenticate only some messages, discriminating personal use from =
business use (and sending conflicting messages about the trustworthiness =
of the From: field to regular users) but making mailing lists from 1995 =
shine
I (and I expect lots of people) choose option 1.

We only need to upgrade the mailing list servers.  The people who run =
those are supposed to be competent--they can probably manage to upgrade =
to supported software, or patch what they have.  Mailing lists aren't =
popular any more anyway.  And this is a golden opportunity to bring some =
trust into Internet mail.  Let's do it.

Cheers,
Sabahattin


From nobody Sun Apr 13 21:34:56 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBD9F1A0322 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 21:34:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level: 
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 T4EsgZbU6KPF for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 21:34:47 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C1D491A0319 for <ietf@ietf.org>; Sun, 13 Apr 2014 21:34:47 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WZYbS-00044a-GK; Mon, 14 Apr 2014 00:34:42 -0400
Date: Mon, 14 Apr 2014 00:34:37 -0400
From: John C Klensin <john-ietf@jck.com>
To: John R Levine <johnl@taugh.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com>
In-Reply-To: <alpine.BSF.2.00.1404132346420.26386@joyce.lan>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WlpJMesxuF_SlB4Hjsd_QCy_G5E
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 04:34:53 -0000

--On Monday, April 14, 2014 00:10 -0400 John R Levine
<johnl@taugh.com> wrote:

>> Sadly, there are a non-trivial number of MTA installations
>> whose implementers or operators, having discovered that they
>> had not seen a legitimate use of the percent hack in years,
>> decided that they were about as likely to appear in
>> legitimate messages as source routing and dealt with them
>> accordingly.  Put more simply, a "%" in a local-part may be
>> least as likely to get a message rejected or dumped as a
>> badly specified DMARC record, so the one is really not a very
>> good cure for the other.
> 
> Since the percent hack became a famous vector for open relay
> abuse, so we all stopped honoring it.  A lot of MTAs still
> reject anything with a % saying something like no more source
> routing.  Mine does.

Exactly.

> So this would require inventing something with the same
> semantics as the percent hack, but a different syntax.
> Perhaps we can use an exclamation point.

I suppose the correct response is "bang, bang, bang,..."

But this takes us back to Ned's point (or at least my
interpretation of it): it is lots easier to fix a bad DMARC
config, ignore restrictive DMARC specifications, or even to
abandon DMARC entirely, than it is to believe that we can
upgrade every MTA and MUA on the network to start accepting
percent hacks, bang paths, or the syntax characters used to
denote them, again.  Or any other strange local-part syntax
anyone is likely to come up with, e.g., perhaps we could use
plus signs, hyphens, or appropriately-escaped backslashes.  Or
we could steal "/" and "=" back from X.400 gateways.  Right.

   john






From nobody Sun Apr 13 21:41:57 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7E061A02FB for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 21:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 iYbkVKmCEXRn for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 21:41:52 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1D51A0319 for <ietf@ietf.org>; Sun, 13 Apr 2014 21:41:52 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id CB7D1CC0A8 for <ietf@ietf.org>; Mon, 14 Apr 2014 00:41:49 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id j3viclALuglm for <ietf@ietf.org>; Mon, 14 Apr 2014 00:41:41 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 1664DCC0A4 for <ietf@ietf.org>; Mon, 14 Apr 2014 00:41:41 -0400 (EDT)
Message-ID: <534B6704.4030506@meetinghouse.net>
Date: Mon, 14 Apr 2014 00:41:40 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net>
In-Reply-To: <534B524F.4050206@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LOVnPMYlMh4403DuTuuLkZU_ZcQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 04:41:55 -0000

On 4/13/2014 7:49 PM, John Levine wrote:
>>> Meanwhile, I'm still not proposing that we train users, or even
>>> anti-spam software to "recognize" or "validate" mailing list addresses.
>>> What I'm proposing is a way to send mail from a list with From:
>>> @domain-of-list.tld so that it can pass DMARC/SPF/DKIM, and allow the
>>> left side of the @ sign to identify the actual sender of the message.
>>

Sure would be nice if current mailers still recognized bang paths -- 
rewrite
From: user@yaho.com
to
From: yahoo.com!user

Sigh...

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 01:08:17 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E59971A03A5 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 01:08:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.426
X-Spam-Level: 
X-Spam-Status: No, score=0.426 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 lIXJMb75GkPL for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 01:08:08 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 02C191A03A4 for <ietf@ietf.org>; Mon, 14 Apr 2014 01:08:02 -0700 (PDT)
Received: from [192.168.4.101] (unknown [67.159.169.102]) by dougbarton.us (Postfix) with ESMTPSA id A798F22B20 for <ietf@ietf.org>; Mon, 14 Apr 2014 08:08:00 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397462880; bh=FfdQRHUDL82J85cyznu7Fqtdc6TRg65Z24O7t9eDOb4=; h=Date:From:To:Subject:References:In-Reply-To; b=MNf2B5eAynjRB4z+/ntH1CIW7Ybk9LVL4xNm/Wq8ZrwTST9wJv2eOIeDNSF1GXpru mARAptgMdlkeNXDNuZIj+UZXGzN64+TG1f9z26elDfsayIODcTaYCjn4SVT8dD/n3K dxRbDuZrGQJU0WBMxMahOkJ+NncEOO7j1H+st+L4=
Message-ID: <534B9760.90301@dougbarton.us>
Date: Mon, 14 Apr 2014 01:08:00 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com>
In-Reply-To: <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UafwJsFte2t0ghvSOdto_bzIe8I
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 08:08:14 -0000

On 04/13/2014 09:34 PM, John C Klensin wrote:
>
>
> --On Monday, April 14, 2014 00:10 -0400 John R Levine
> <johnl@taugh.com> wrote:
>
>>> Sadly, there are a non-trivial number of MTA installations
>>> whose implementers or operators, having discovered that they
>>> had not seen a legitimate use of the percent hack in years,
>>> decided that they were about as likely to appear in
>>> legitimate messages as source routing and dealt with them
>>> accordingly.  Put more simply, a "%" in a local-part may be
>>> least as likely to get a message rejected or dumped as a
>>> badly specified DMARC record, so the one is really not a very
>>> good cure for the other.
>>
>> Since the percent hack became a famous vector for open relay
>> abuse, so we all stopped honoring it.  A lot of MTAs still
>> reject anything with a % saying something like no more source
>> routing.  Mine does.
>
> Exactly.

Perhaps my suggestion to use the percent sign dragged in some baggage I 
wasn't intending. To be clear, I wasn't suggesting that receiving 
systems do anything special with the address, only that we establish a 
convention/standard for how to encode the real address of the sender for 
mail sent through mailing lists. It could at least by visually inspected 
by recipients, and in theory MUAs could learn to deal with it for 
display and/or reply purposes. If a ! works better than a % to separate 
the sender's address from the list address that's great.

For those that are skeptical of MUAs actually doing this, I agree. 
However in recent memory a non-trivial number of modern MUAs have picked 
up parsing of list headers sufficiently to make "reply to list" buttons 
a reality. So not all hope is lost here.

>> So this would require inventing something with the same
>> semantics as the percent hack, but a different syntax.
>> Perhaps we can use an exclamation point.
>
> I suppose the correct response is "bang, bang, bang,..."
>
> But this takes us back to Ned's point (or at least my
> interpretation of it): it is lots easier to fix a bad DMARC
> config, ignore restrictive DMARC specifications, or even to
> abandon DMARC entirely, than it is to believe that we can
> upgrade every MTA and MUA on the network to start accepting
> percent hacks, bang paths, or the syntax characters used to
> denote them, again.  Or any other strange local-part syntax
> anyone is likely to come up with, e.g., perhaps we could use
> plus signs, hyphens, or appropriately-escaped backslashes.  Or
> we could steal "/" and "=" back from X.400 gateways.  Right.

Well + is out, since that's used by various local filtering solutions.

But your point is well taken ... the "right" answer may be to fix or 
discard DMARC, I honestly don't know. But in a world where DMARC is here 
to stay, or if not DMARC then some other anti-spam solution that breaks 
mailing list forwarding; and in that same world where mailing list 
traffic is negligible (and therefore the cost of breaking mailing lists 
is in the noise compared to the benefits of deploying said anti-spam 
solution) it's incumbent on the mailing list software folks to solve 
this problem.

Doug


From nobody Mon Apr 14 02:15:02 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8AE51A0297 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 02:15:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level: 
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 s4aJteSvzQG4 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 02:14:56 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5F2171A0106 for <ietf@ietf.org>; Mon, 14 Apr 2014 02:14:56 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WZcyb-0004Y1-I6; Mon, 14 Apr 2014 05:14:53 -0400
Date: Mon, 14 Apr 2014 05:14:48 -0400
From: John C Klensin <john-ietf@jck.com>
To: Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
In-Reply-To: <534B9760.90301@dougbarton.us>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3IqG9zOjQdk36tgzakCUyDqnjiE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 09:15:01 -0000

--On Monday, April 14, 2014 01:08 -0700 Doug Barton
<dougb@dougbarton.us> wrote:

>> But this takes us back to Ned's point (or at least my
>> interpretation of it): it is lots easier to fix a bad DMARC
>> config, ignore restrictive DMARC specifications, or even to
>> abandon DMARC entirely, than it is to believe that we can
>> upgrade every MTA and MUA on the network to start accepting
>> percent hacks, bang paths, or the syntax characters used to
>> denote them, again.  Or any other strange local-part syntax
>> anyone is likely to come up with, e.g., perhaps we could use
>> plus signs, hyphens, or appropriately-escaped backslashes.  Or
>> we could steal "/" and "=" back from X.400 gateways.  Right.
> 
> Well + is out, since that's used by various local filtering
> solutions.

Doug, I think you are missing my, and probably John Levine's,
attempts at humor.   Let me spell it out:

The point was the "+" is used in local filtering and, perhaps
more generally, as subaddresses with all sorts of applications.
Both "%" and "!", along with <@a:x@y>, were, at different points
and gateways to different systems, mail routing mechanisms that
are now sufficiently deprecated and/or rare that many
intermediate MTAs will singly reject or drop messages containing
them.  "/" and "=" were used on the local part of addresses
bound for, or coming from, X.400 gateways and many systems will
reject (or possibly) drop messages with local parts in which
they appear but that don't conform to that gateway syntax...
except that "/" may also designate delivery to a file and "//"
may be a piece of ancient JCL. 

It isn't just the MTAs: Some POP and IMAP client MUAs will trash
this stuff too.  As with the MTAs, using these sorts of trick
conventions without disrupting the existing mail systems,
including those that don't pay any attention to DMARC or DKIM
headers and hence are unaffected by the problem, requires that
everything be upgraded and upgraded more or less on a flag day
basis.  

There is a strong rule in RFC 5321 and its predecessor
forbidding anything but the final delivery system from rewriting
a local-part and it is there precisely because one doesn't know
what sorts of conventions and indicates were begin used there. 

The bottom line is that trying to work around this by a trick
syntax convention is really hard, unlikely to succeed, and quite
likely to result in legitimate messages disappearing and/or
breaking existing conforming systems.  

> But your point is well taken ... the "right" answer may be to
> fix or discard DMARC, I honestly don't know. But in a world
> where DMARC is here to stay, or if not DMARC then some other
> anti-spam solution that breaks mailing list forwarding; and in
> that same world where mailing list traffic is negligible (and
> therefore the cost of breaking mailing lists is in the noise
> compared to the benefits of deploying said anti-spam solution)
> it's incumbent on the mailing list software folks to solve
> this problem.

I'm going to risk more humor and suggest that everyone who
believes that mailing list traffic is negligible and the cost of
breaking them is in the noise should be immediately unsubscribed
from all IETF-related lists, including this one.

best,
    john





From nobody Mon Apr 14 02:39:17 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 485C91A03A8 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 02:39:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.163
X-Spam-Level: 
X-Spam-Status: No, score=-0.163 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 KuGh3zUV04nu for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 02:39:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BED1B1A0298 for <ietf@ietf.org>; Mon, 14 Apr 2014 02:39:11 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.146.211]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3E9ct08010474 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Apr 2014 02:39:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397468348; bh=SXoTz9GvFsReA1Ft3aF8NXD8et+CSDJlJdvz7BfXrmY=; h=Date:To:From:Subject:In-Reply-To:References; b=iFcrc4NkzK7BfGdScQooie4xsv0djFgJgnftrZ3PY0utzlopPQWRYUNjOwfMfcFxD Q9m2EHmzcK4EGyV8zmfHTYx0VoOyCUGESwhLxvE6LALL+3yoSmjBP1e4Ck9Au87T8H VoHGpymnO3vXFIZsbYYEYpR0yNyJfMeN9gFqnMpw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397468348; i=@elandsys.com; bh=SXoTz9GvFsReA1Ft3aF8NXD8et+CSDJlJdvz7BfXrmY=; h=Date:To:From:Subject:In-Reply-To:References; b=yBu3v4ZocRQQLj/vnhQcQDmbTmutnNkORksTfxOfJi0fIV0U+u/EqdZPKRXwX2wuK 4oHf8mH95c23RrvvYAdwtiM8G7nV4MZ9lRahxtyi9IcvX1K35070AhAk83+EUKrxyq MhINJ/ps8jYuikhKpyHmNIxJc/pDYax8h8gPtACs=
Message-Id: <6.2.5.6.2.20140413225142.0c3d3158@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 Apr 2014 00:38:28 -0700
To: Alessandro Vesely <vesely@tana.it>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <5347C698.6040108@tana.it>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan> <5347C698.6040108@tana.it>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/a9RP4Z01p2CdHX-aHMzTe9JwskY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 09:39:16 -0000

Hi Alessandro,
At 03:40 11-04-2014, Alessandro Vesely wrote:
>Please feel free to amend that page at your leisure.

"Big, popular brands are often used in phishing and scam email 
attacks and I'm sure you've seen some of them first hand" [1].  DMARC 
is a technology that provides brand protection.  Let's say that you 
work for cs.helsinki.fi.  cs.helsinki.fi currently publishes a policy 
to protect its brand.  If you use that domain name to send a message 
to ietf@ietf.org, cs.helsinki.fi will reject that message.  Several 
big companies will also reject that message.

The suggestion is to have the ietf.org mail service rewrite the 
domain part in the "From:" header as cs.helsinki.fi.invalid.  The 
ietf.org mail service is not doing that at the moment.  The mail 
service does not have to do that as the collateral damage is 
considered as acceptable.  The rewrite will cause other problems.

Email is like the Titanic.

Regards,
S. Moonesamy

1. 
http://www.symantec.com/connect/blogs/introducing-dmarc-validation-email-securitycloud  


From nobody Mon Apr 14 04:21:11 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 727371A02B5 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 04:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 xAWiRhWikILQ for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 04:21:03 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.167]) by ietfa.amsl.com (Postfix) with ESMTP id 798D01A02AF for <ietf@ietf.org>; Mon, 14 Apr 2014 04:21:03 -0700 (PDT)
Received: from [85.158.137.99:27425] by server-7.bemta-3.messagelabs.com id 28/46-04151-B94CB435; Mon, 14 Apr 2014 11:20:59 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-217.messagelabs.com!1397474459!19348359!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17384 invoked from network); 14 Apr 2014 11:20:59 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-11.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 14 Apr 2014 11:20:59 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.14]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Mon, 14 Apr 2014 12:20:58 +0100
From: <l.wood@surrey.ac.uk>
To: <johnl@taugh.com>, <dcrocker@bbiw.net>, <ietf@ietf.org>
Date: Mon, 14 Apr 2014 12:20:57 +0100
Subject: RE: DMARC: perspectives from a listadmin of large open-source lists
Thread-Topic: DMARC: perspectives from a listadmin of large open-source lists
Thread-Index: Ac9XkbqyfBTaTXV9SBS8uqjuP4pj2gAQI/2t
Message-ID: <290E20B455C66743BE178C5C84F1240847E88E3F8C@EXMB01CMS.surrey.ac.uk>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net>, <alpine.BSF.2.00.1404132327560.26258@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1404132327560.26258@joyce.lan>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NgIsL_9Si1TprkSJxp1cSy8zf8M
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 11:21:08 -0000

But DMARC is email authentication best practice.

Sure, some legacy email things are having some minor teething problems with=
 it,
but it's clearly the way to go. Because it introduces authentication.

Now all the spammers will have to open their free yahoo accounts first, bef=
ore
sending email! That's a great step forwards!

Security! Best practice!

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of John R Levine [johnl@taugh.=
com]
Sent: 14 April 2014 04:28
To: Dave Crocker; IETF general list
Subject: Re: DMARC: perspectives from a listadmin of large open-source list=
s

>> Yes, that's the 1980s percent hack.

> intended recipient.  While a bit inefficient -- and probably will emerge =
as
> an attack vector (sigh) -- it's a plausible mechanism.

Right -- something is seriously wrong with DMARC as used if we need to
invent new phish syntaxes to work around it.

R's,
John


From nobody Mon Apr 14 06:20:15 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B81D1A0484; Mon, 14 Apr 2014 06:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.873
X-Spam-Level: 
X-Spam-Status: No, score=-0.873 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 VLY__cycL83n; Mon, 14 Apr 2014 06:20:08 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CD73C1A0494; Mon, 14 Apr 2014 06:20:04 -0700 (PDT)
Received: from maildlpprd02.lss.emc.com (maildlpprd02.lss.emc.com [10.253.24.34]) by mailuogwprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3EDJsfJ025680 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Apr 2014 09:19:56 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s3EDJsfJ025680
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397481596; bh=TzurfSxhx1crxzjb21l9IQpecwM=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=YGhiPNkFhliIcOzmMgEwi89Jgdc7ceAIEjmbbQvbEtL4u2Q00PCU6kKUzo9u+WYC7 gFPZARJ2kKSqvyQ4OHTmdOoFNzIo7bRsuORFcMm0rOgv6ZK/R8xZRc+gC9PbGWoVuP DPMWgj+7Fgde9fiUYrBpayvwKI6zXrLx1Oerg9Pw=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd02.lss.emc.com s3EDJsfJ025680
Received: from mailusrhubprd01.lss.emc.com (mailusrhubprd01.lss.emc.com [10.253.24.19]) by maildlpprd02.lss.emc.com (RSA Interceptor); Mon, 14 Apr 2014 09:19:36 -0400
Received: from mxhub28.corp.emc.com (mxhub28.corp.emc.com [10.254.110.184]) by mailusrhubprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3EDJZxt020247 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 14 Apr 2014 09:19:35 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub28.corp.emc.com ([10.254.110.184]) with mapi; Mon, 14 Apr 2014 09:19:34 -0400
From: "Black, David" <david.black@emc.com>
To: "zhai.hongjun@zte.com.cn" <zhai.hongjun@zte.com.cn>, "hu.fangwei@zte.com.cn" <hu.fangwei@zte.com.cn>, "Radia@alum.mit.edu" <Radia@alum.mit.edu>, "Donald Eastlake (d3e3e3@gmail.com)" <d3e3e3@gmail.com>, "ostokes@extremenetworks.com" <ostokes@extremenetworks.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Mon, 14 Apr 2014 09:19:34 -0400
Subject: Gen-ART review of draft-ietf-trill-esadi-07.txt
Thread-Topic: Gen-ART review of draft-ietf-trill-esadi-07.txt
Thread-Index: Ac9X5C1IRV0XGBZDQo+hNsgFemwTCQ==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C1D1C22@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd01.lss.emc.com
X-RSA-Classifications: public, Resumes
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Dw1aiDKbQ7WtEFmtzJID4oc2s-A
Cc: "ietf@ietf.org" <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 13:20:13 -0000

The -07 version of this draft addresses all of the concerns raised by the G=
en-ART
review of the -06 version.  I would have preferred to see stronger Security
Considerations text on usage (and non-usage of the Authentication TLV.  Tha=
t said,
the text in the -07 version is an improvement, and I will leave any further
follow-up to the IESG.

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Saturday, March 29, 2014 10:24 PM
> To: zhai.hongjun@zte.com.cn; hu.fangwei@zte.com.cn; Radia@alum.mit.edu; D=
onald
> Eastlake (d3e3e3@gmail.com); ostokes@extremenetworks.com; General Area Re=
view
> Team (gen-art@ietf.org)
> Cc: trill@ietf.org; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-trill-esadi-06.txt
>=20
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-trill-esadi-06.txt
> Reviewer: David L. Black
> Review Date: March 29, 2014
> IETF LC End Date: April 1, 2014
>=20
> Summary: This draft is on the right track, but has open issues
> described in the review.
>=20
> This draft revises the ESADI specification for TRILL from its
> original form in RFC 6325.
>=20
> Major issues:
>=20
> The draft changes ESADI in a non-backwards-compatible fashion from
> its original specification in RFC 6325, but does not explain why this
> is ok.  That explanation needs to be provided, and if implementations
> of ESADI as originally specified in RF 6325 exist, that explanation
> needs to encompass coexistence and interoperability (or lack thereof)
> with such implementations.  That explanation probably belongs in
> Section 1.1, and could be expanded upon in Appendix A.
>=20
> Overall, this draft is not self-contained - to a significant extent,
> it is written as if it were effectively a long collection of errata
> to the ESADI specification in RFC 6325.  That makes it difficult to
> understand - it would be better if this draft completely obsoleted
> and replaced the ESADI specification in RFC 6325, describing its
> changes, instead of providing specific text changes to portions
> of the RFC 6325 text.
>=20
> Minor issues:
>=20
> I don't understand the discussion in section 2 of it being "an
> implementation decision how independent the multiple ESADI instances
> at an RBridge are" in light of the clear statement that "the ESADI
> update process operates separately for each ESADI instance."  The
> example given involves database structure considerations that are
> specific to the node implementation and do not affect the independent
> updates for each ESADI instance.  There may not be an actual
> technical problem here, but at least the first chunk of text quoted
> in this paragraph of the review needs to be rewritten.
>=20
> Also in Section 2:
>=20
>    ESADI does no routing so there is no reason for pseudo-nodes in ESADI
>    and none are created.
>=20
> Need to explain what a pseudo-node is before this sentence.
>=20
> p.9, Figure 2 - explain how the receiver determines whether the inner
> Ethernet header contains a VLAN tag or FGL.  This also applies to Figure
> 3 on p.10.
>=20
> p.10, Section 2.1:
>=20
>    All transit RBridges forward ESADI packets as if they were ordinary
>    TRILL Data packets.
>=20
> Need to explain what a "transit" RBridge is.  Between this and the
> above pseudo-node comment, I suggest adding an overview of the
> TRILL protocol to the start of Section 2.
>=20
> p.11, Section 2.1:
>=20
>    No "routing" computation or routing decisions ever have to be performe=
d
>    by ESADI.
>=20
> What is a ' "routing" computation' ??  This should be rephrased to
> contrast to what the non-ESADI TRILL usage of IS-IS does.
>=20
> p.12, Section 2.2:
>=20
>    If a VLAN or FGL ID
>    field within an ESADI-LSP PDU does include a value, that field's
>    contents is ignored.
>=20
> This looks like it's an important requirement, so:
> 	 "is ignored" -> "MUST be ignored"
>=20
> p.13, Section 3
>=20
>   "SNPA/MAC address"
>    is not considered in this tie breaking and there is no "Port ID".
>=20
> This is contrasting ESDI tie-breaking to a tie-breaking
> procedure that I'd guess is specified in another document; that needs to
> be explained, along with a reference to that document, preferably with
> the section number where the other tie-breaking procedure is specified.
>=20
> Section 6 - explain where the 1470 byte number in the third paragraph
> comes from.
>=20
> Section 8 - more should be said on whether/when the Authentication TLV
> should be used when ESADI conveys information from an authenticated
> registration.  In particular, if this recommendation for usage of the
> Authentication TLV with information from an authenticated
> registration usage is not a "SHOULD" or "MUST", an explanation is in
> order.
>=20
> Nits/editorial comments:
>=20
> There are lots of acronyms that are not expanded on first use, defined
> in the terminology section, or otherwise explained, e.g., DRB, Sz, CSNP,
> PSNP.  It may be ok to point to terminology/acronym definitions in RFC
> 6325.
>=20
> Last sentence on p.8:
>=20
> OLD
>    The outer VLAN tag will not be present if it was stripped by
>    an Ethernet port out of which the packet was sent.
> NEW
>    The outer VLAN tag will not be present for a packet on an
>    an Ethernet link that does not use VLAN tags.
>=20
> idnits 2.13.01 got confused by the Section 4.6.2.2 reference to
> RFC 6325 in Section 4.1, and thought 4.6.2.2 was an IPv4 address -
> this is not a problem.
>=20
> idnits also warned about possible pre-RFC5378 (2008) content.  This
> is probably not a problem, but please check with your AD.
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From nobody Mon Apr 14 06:58:01 2014
Return-Path: <kent@bbn.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03DC91A0493 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 06:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.473
X-Spam-Level: 
X-Spam-Status: No, score=-4.473 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 RutEhALkGZoZ for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 06:57:50 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id E4A121A0491 for <ietf@ietf.org>; Mon, 14 Apr 2014 06:57:49 -0700 (PDT)
Received: from dommiel.bbn.com ([192.1.122.15]:49949 helo=comsec.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1WZhOW-0009wt-5o for ietf@ietf.org; Mon, 14 Apr 2014 09:57:56 -0400
Message-ID: <534BE95B.2080102@bbn.com>
Date: Mon, 14 Apr 2014 09:57:47 -0400
From: Stephen Kent <kent@bbn.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Security for various IETF services
References: <20140409154919.11E6118C106@mercury.lcs.mit.edu> <534580AF.4080602@dcrocker.net> <20140409200814.GA15303@thunk.org> <3C46B827-BFFC-4A9E-B600-A1E79C839970@shinkuro.com> <20140410141406.GF15925@thunk.org>
In-Reply-To: <20140410141406.GF15925@thunk.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PKZECf1j3o1OTxBlnt_UWuuTo_c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 13:57:51 -0000

Ted,

The fact that, within the DNS each CA-like entity is syntactically 
constrained,
is very important. It addresses the fundamental flaw of the Web PKI, 
that was
illustrated by the DigiNotar debacle.

Steve


From nobody Mon Apr 14 07:26:00 2014
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AFBC11A0491 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 07:25:59 -0700 (PDT)
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] autolearn=ham
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 ViDWXluqYu5N for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 07:25:54 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CDDBD1A03EB for <ietf@ietf.org>; Mon, 14 Apr 2014 07:25:54 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3EEPmkd009424 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 14 Apr 2014 07:25:51 -0700
Message-ID: <534BEF75.5060804@bbiw.net>
Date: Mon, 14 Apr 2014 07:23:49 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
In-Reply-To: <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Mon, 14 Apr 2014 07:25:52 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lky21iDSk03dDw7iWwg9OVkfTGo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 14:25:59 -0000

On 4/14/2014 2:14 AM, John C Klensin wrote:
> There is a strong rule in RFC 5321 and its predecessor
> forbidding anything but the final delivery system from rewriting
> a local-part and it is there precisely because one doesn't know
> what sorts of conventions and indicates were begin used there.


Just to avoid possible confusion about the implications of the above:

      Mediators, like mailing lists, take final delivery and post a new 
message.  In formal terms, it's legitimate for them to create a 
different rfc5322.From field, including one that looks like some sort of 
'rewrite' of the one used by the original author.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 14 07:37:35 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6B0E1A02F7 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 07:37:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.872
X-Spam-Level: 
X-Spam-Status: No, score=-2.872 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 rYVrKzw_lDsz for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 07:37:22 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C04D01A02F5 for <ietf@ietf.org>; Mon, 14 Apr 2014 07:37:22 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WZi0b-0004yg-HR; Mon, 14 Apr 2014 10:37:17 -0400
Date: Mon, 14 Apr 2014 10:37:12 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@bbiw.net>, Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <641C1E5EF4C1D458FF909DAF@JcK-HP8200.jck.com>
In-Reply-To: <534BEF75.5060804@bbiw.net>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VjUR4a3GR4OK9I_NouyPGUBHFKI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 14:37:28 -0000

--On Monday, April 14, 2014 07:23 -0700 Dave Crocker
<dcrocker@bbiw.net> wrote:

> On 4/14/2014 2:14 AM, John C Klensin wrote:
>> There is a strong rule in RFC 5321 and its predecessor
>> forbidding anything but the final delivery system from
>> rewriting a local-part and it is there precisely because one
>> doesn't know what sorts of conventions and indicates were
>> begin used there.
> 
> 
> Just to avoid possible confusion about the implications of the
> above:
> 
>       Mediators, like mailing lists, take final delivery and
> post a new message.  In formal terms, it's legitimate for them
> to create a different rfc5322.From field, including one that
> looks like some sort of 'rewrite' of the one used by the
> original author.

Yes.

     john




From nobody Mon Apr 14 08:08:50 2014
Return-Path: <wesley.george@twcable.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B6121A04A1 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:08:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.964
X-Spam-Level: *
X-Spam-Status: No, score=1.964 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_MODEMCABLE=0.768, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 CowjZnrpahae for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:08:45 -0700 (PDT)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id 8D49D1A049D for <ietf@ietf.org>; Mon, 14 Apr 2014 08:08:44 -0700 (PDT)
X-SENDER-IP: 10.136.163.13
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.97,857,1389762000";  d="scan'208,217";a="267495885"
Received: from unknown (HELO PRVPEXHUB04.corp.twcable.com) ([10.136.163.13]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 14 Apr 2014 11:07:53 -0400
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.79]) by PRVPEXHUB04.corp.twcable.com ([10.136.163.13]) with mapi; Mon, 14 Apr 2014 11:08:07 -0400
From: "George, Wes" <wesley.george@twcable.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 14 Apr 2014 11:08:10 -0400
Subject: "why I quit writing internet standards"
Thread-Topic: "why I quit writing internet standards"
Thread-Index: Ac9X81eHeq16KFTYS36hQmTuRsUdgw==
Message-ID: <CF71721A.180A9%wesley.george@twcable.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.3.9.131030
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_CF71721A180A9wesleygeorgetwcablecom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/y18KLcNIkW1gvVmXW_RVAO6sqb4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 15:08:49 -0000

--_000_CF71721A180A9wesleygeorgetwcablecom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmW0gc3VycHJpc2VkIHRoYXQgbm8gb25lIGhhcyBzZW50IHRoaXMgb3V0IHlldDogaHR0cDov
L2dpZ2FvbS5jb20vMjAxNC8wNC8xMi93aHktaS1xdWl0LXdyaXRpbmctaW50ZXJuZXQtc3RhbmRh
cmRzLw0KDQoiU3VtbWFyeTogQWZ0ZXIgY29udHJpYnV0aW5nIHRvIHN0YW5kYXJkcyBvcmdhbml6
YXRpb25zIGZvciBtb3JlIHRoYW4gc2V2ZW4geWVhcnMsIGVuZ2luZWVyIFZpZHlhIE5hcmF5YW5h
biBkZWNpZGVkIGl0IHdhcyB0aW1lIHRvIG1vdmUgb24uIEFsdGhvdWdoIHNoZSBzdGlsbCBiZWxp
ZXZlcyB0aGF0IHRoZXNlIG9yZ2FuaXphdGlvbnMgbWFrZSB0aGUgSW50ZXJuZXQgYSBiZXR0ZXIg
cGxhY2UsIHNoZSB3b25kZXJzIGFib3V0IHRoZSBwYWNlIG9mIGNoYW5nZSB2ZXJzdXMgdGhlIHBh
Y2Ugb2Ygb3JnYW5pemF0aW9ucy4iDQoNCk15IHRob3VnaHRzLQ0KDQpUaGVyZSBhcmUgc29tZSBu
dWdnZXRzIG9mIHRydXRoIGluIHdoYXQgc2hlIHNheXMgaW4gdGhpcyBhcnRpY2xlLCBhbmQgaW4g
c29tZSBvZiB0aGUgY29tbWVudHMuIEkgdGhpbmsgdGhhdCB0aGUgcHJvYmxlbXMgYXJlIHJlYWws
IHNvIHRoZXJl4oCZcyB2YWx1ZSBpbiB0YWtpbmcgdGhlIGNyaXRpY2lzbSBjb25zdHJ1Y3RpdmVs
eSwgZGVzcGl0ZSB0aGUgZmFjdCB0aGF0IHRoZSBhdXRob3IgY2hvc2UgdG8gZm9jdXMgb24gdGhl
IHByb2JsZW1zIHdpdGhvdXQgYW55IHN1Z2dlc3Rpb25zIG9mIHNvbHV0aW9ucy4NCg0KIndoaWxl
IHRoZSBwYWNlIGF0IHdoaWNoIHN0YW5kYXJkcyBhcmUgd3JpdHRlbiBoYXNu4oCZdCBjaGFuZ2Vk
IGluIG1hbnkgeWVhcnMsIHRoZSBwYWNlIGF0IHdoaWNoIHRoZSByZWFsIHdvcmxkIGFkb3B0cyBz
b2Z0d2FyZSBoYXMgYmVjb21lIG9yZGVycyBvZiBtYWduaXR1ZGUgZmFzdGVyLiINCuKApg0KIlJ1
bm5pbmcgY29kZSBhbmQgcm91Z2ggY29uc2Vuc3VzLCB0aGUgbW90dG8gb2YgdGhlIElFVEYsIHVz
ZWQgdG8gYmUgcmVhbGl6YWJsZSBhdCBzb21lIHBvaW50LiDigKYgSW4gdGhlIG5hbWUgb2YgY29u
c2Vuc3VzLCB3ZSBkZWJhdGUgZnJpdm9sb3VzIGRldGFpbHMgZm9yZXZlci4gSW4gdGhlIG5hbWUg
b2YgcGF0ZW50cywgd2UgbmV2ZXIgZmluaXNoLuKAnQ0K4oCmDQoiVW5sZXNzIHRoZXNlIHN0YW5k
YXJkcyBvcmdhbml6YXRpb25zIG1ha2UgcmFkaWNhbCBzaGlmdHMgdG93YXJkcyBwcmFjdGljYWxp
dHksIHRoZWlyIHJlbGV2YW5jZSB3aWxsIHNvb24gYmUgcXVlc3Rpb25hYmxlLuKAnQ0KDQpJIGRv
buKAmXQgaGF2ZSB0b28gbWFueSBiaWcgaWRlYXMgaG93IHRvIGZpeCB0aGVzZSBwcm9ibGVtcywg
YnV0IEnigJlsbCBhdCBsZWFzdCB0YWtlIGEgY3JhY2sgYXQgaXQgaW4gb3JkZXIgdG8gc3B1ciBk
aXNjdXNzaW9uLiBNeSBwYXJhcGhyYXNlIG9mIHRoZSBwcm9ibGVtIGFuZCBzb21lIGRpc2N1c3Np
b24gZm9sbG93cy4NCg0KLSBXZeKAmXZlIGxvc3Qgc2lnaHQgb2YgY29uc2Vuc3VzIGFuZCBhcmUg
dG9vIG9mdGVuIGRlcmFpbGVkIGJ5IGEgdm9jYWwgbWlub3JpdHkgb2YgdGhvc2Ugd2lsbGluZyB0
byBlbmRsZXNzbHkgZGViYXRlIGEgcG9pbnQuDQoNClBhcnQgb2YgdGhlIHNvbHV0aW9uIHRvIHRo
YXQgaXMgcmVpdGVyYXRpbmcgd2hhdCBjb25zZW5zdXMgaXMgYW5kIGlzIG5vdCwgc3VjaCBhcyBk
cmFmdC1yZXNuaWNrLW9uLWNvbnNlbnN1cyBzbyB0aGF0IHdlIGRvbuKAmXQgY29uZnVzZSBhIG5l
ZWQgZm9yIGNvbnNlbnN1cyB3aXRoIGEgbmVlZCBmb3IgdW5hbmltaXR5LiBQYXJ0IG9mIHRoZSBz
b2x1dGlvbiBpcyBJRVRGIGxlYWRlcnNoaXAgaGVscGluZyB0byBpZGVudGlmeSB3aGVuIHdlIGhh
dmUgcm91Z2ggY29uc2Vuc3VzIGVuY3VtYmVyZWQgYnkgYSBkZWJhdGUgdGhhdCB3aWxsIG5ldmVy
IHJlc29sdmUgaXRzZWxmLCB3aXRob3V0IHF1aWV0aW5nIGFjdHVhbCBkaXNhZ3JlZW1lbnQgdGhh
dCBuZWVkcyBjb250aW51ZWQgZGlzY3Vzc2lvbiBpbiBvcmRlciB0byBmaW5kIGEgY29tcHJvbWlz
ZS4gSSBkb27igJl0IGhhdmUgZ29vZCBzdWdnZXN0aW9ucyBvbiBob3cgdG8gbWFrZSB0aGF0IHNl
Y29uZCBoYWxmIGJldHRlci4NCg0KLSBXZSBkb27igJl0IGhhdmUgbmVhcmx5IGVub3VnaCBmb2N1
cyBvbiBydW5uaW5nIGNvZGUgYXMgdGhlIHRoaW5nIHRoYXQgaGVscHMgdG8gZW5zdXJlIHRoYXQg
d2XigJlyZSB1c2luZyBvdXIgbGltaXRlZCBjeWNsZXMgb24gZ2V0dGluZyB0aGUgcmlnaHQgdGhp
bmdzIG91dCBleHBlZGllbnRseSwgYW5kIGVpdGhlciBnZXR0aW5nIHRoZSBkZXNpZ24gcmlnaHQg
dGhlIGZpcnN0IHRpbWUsIG9yIGZhaWxpbmcgcXVpY2tseSBhbmQgaXRlcmF0aW5nIHRvIGltcHJv
dmUNCg0KVGhlIHNvbHV0aW9uIGhlcmUgbWF5IGJlIHRoYXQgd2UgbmVlZCB0byBiZSBtdWNoIG1v
cmUgYWdncmVzc2l2ZSBhdCBleHBlY3RpbmcgYW55IHN0YW5kYXJkcyB0cmFjayBkb2N1bWVudHMg
dG8gaGF2ZSBydW5uaW5nIGNvZGUgbXVjaCBlYXJsaWVyIGluIHRoZSBwcm9jZXNzLiBUaGUgb3Ro
ZXIgcGFydCBvZiB0aGF0IGlzIHRvIHJlbmV3IG91ciBmb2N1cyBvbiBhY3R1YWwgaW50ZXJvcCBz
dGFuZGFyZHMgd29yaywgcHJvYmFibHkgYnkgY2hhcnRlciBvciBpbi1ncm91cCBmZWVkYmFjaywg
c2hpZnQgZm9jdXMgYXdheSBmcm9tIEJDUCBhbmQgaW5mbyBkb2N1bWVudHMuIFBlcmhhcHMgd2hl
biBjb25zaWRlcmluZyB3aGV0aGVyIHRvIHByb2NlZWQgd2l0aCBhIGdpdmVuIGRvY3VtZW50LCB3
ZSBuZWVkIHRlc3QgYXMgdG8gd2hldGhlciBpdOKAmXMgYWN0aXZlbHkgaGVscGZ1bC9uZWVkZWQg
YW5kIGVuc3VyZSB0aGF0IHdlIGtub3cgd2hhdCBhdWRpZW5jZSB3b3VsZCBiZSBsb29raW5nIGF0
IGl0LCByYXRoZXIgdGhhbiBzaW1wbHkgZW5zdXJpbmcgdGhhdCBpdCBpcyDigJxub3QgaGFybWZ1
bOKAnSBhbmQgbW9zdGx5IHdpdGhpbiB0aGUgV0figJlzIGNoYXJ0ZXJlZCBmb2N1cy4NCg0KVGhh
bmtzLA0KDQpXZXMgR2VvcmdlDQoNCkFueXRoaW5nIGJlbG93IHRoaXMgbGluZSBoYXMgYmVlbiBh
ZGRlZCBieSBteSBjb21wYW554oCZcyBtYWlsIHNlcnZlciwgSSBoYXZlIG5vIGNvbnRyb2wgb3Zl
ciBpdC4NCi0tLS0tLS0tLS0tDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpU
aGlzIEUtbWFpbCBhbmQgYW55IG9mIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBUaW1lIFdh
cm5lciBDYWJsZSBwcm9wcmlldGFyeSBpbmZvcm1hdGlvbiwgd2hpY2ggaXMgcHJpdmlsZWdlZCwg
Y29uZmlkZW50aWFsLCBvciBzdWJqZWN0IHRvIGNvcHlyaWdodCBiZWxvbmdpbmcgdG8gVGltZSBX
YXJuZXIgQ2FibGUuIFRoaXMgRS1tYWlsIGlzIGludGVuZGVkIHNvbGVseSBmb3IgdGhlIHVzZSBv
ZiB0aGUgaW5kaXZpZHVhbCBvciBlbnRpdHkgdG8gd2hpY2ggaXQgaXMgYWRkcmVzc2VkLiBJZiB5
b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50IG9mIHRoaXMgRS1tYWlsLCB5b3UgYXJl
IGhlcmVieSBub3RpZmllZCB0aGF0IGFueSBkaXNzZW1pbmF0aW9uLCBkaXN0cmlidXRpb24sIGNv
cHlpbmcsIG9yIGFjdGlvbiB0YWtlbiBpbiByZWxhdGlvbiB0byB0aGUgY29udGVudHMgb2YgYW5k
IGF0dGFjaG1lbnRzIHRvIHRoaXMgRS1tYWlsIGlzIHN0cmljdGx5IHByb2hpYml0ZWQgYW5kIG1h
eSBiZSB1bmxhd2Z1bC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBFLW1haWwgaW4gZXJyb3Is
IHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVs
ZXRlIHRoZSBvcmlnaW5hbCBhbmQgYW55IGNvcHkgb2YgdGhpcyBFLW1haWwgYW5kIGFueSBwcmlu
dG91dC4NCg==

--_000_CF71721A180A9wesleygeorgetwcablecom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdiBzdHlsZT0iY29s
b3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQt
c2l6ZTogMTRweDsiPg0KSeKAmW0gc3VycHJpc2VkIHRoYXQgbm8gb25lIGhhcyBzZW50IHRoaXMg
b3V0IHlldDombmJzcDs8YSBocmVmPSJodHRwOi8vZ2lnYW9tLmNvbS8yMDE0LzA0LzEyL3doeS1p
LXF1aXQtd3JpdGluZy1pbnRlcm5ldC1zdGFuZGFyZHMvIj5odHRwOi8vZ2lnYW9tLmNvbS8yMDE0
LzA0LzEyL3doeS1pLXF1aXQtd3JpdGluZy1pbnRlcm5ldC1zdGFuZGFyZHMvPC9hPjwvZGl2Pg0K
PGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNh
bnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KPGJyPg0KPC9kaXY+DQo8ZGl2IHN0eWxlPSJj
b2xvcjogcmdiKDAsIDAsIDApOyI+JnF1b3Q7U3VtbWFyeTombmJzcDs8c3BhbiBzdHlsZT0iYmFj
a2dyb3VuZC1jb2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyBjb2xvcjogcmdiKDQyLCA0NiwgNTEp
OyBmb250LXN0eWxlOiBpdGFsaWM7IGxpbmUtaGVpZ2h0OiAyMnB4OyI+QWZ0ZXIgY29udHJpYnV0
aW5nIHRvIHN0YW5kYXJkcyBvcmdhbml6YXRpb25zIGZvciBtb3JlIHRoYW4gc2V2ZW4geWVhcnMs
IGVuZ2luZWVyIFZpZHlhIE5hcmF5YW5hbg0KIGRlY2lkZWQgaXQgd2FzIHRpbWUgdG8gbW92ZSBv
bi4gQWx0aG91Z2ggc2hlIHN0aWxsIGJlbGlldmVzIHRoYXQgdGhlc2Ugb3JnYW5pemF0aW9ucyBt
YWtlIHRoZSBJbnRlcm5ldCBhIGJldHRlciBwbGFjZSwgc2hlIHdvbmRlcnMgYWJvdXQgdGhlIHBh
Y2Ugb2YgY2hhbmdlIHZlcnN1cyB0aGUgcGFjZSBvZiBvcmdhbml6YXRpb25zLiZxdW90Ozwvc3Bh
bj48L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7Ij48YnI+DQo8L2Rpdj4N
CjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7Ij5NeSB0aG91Z2h0cy08L2Rpdj4NCjxk
aXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwgMCk7Ij48YnI+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9
ImNvbG9yOiByZ2IoMCwgMCwgMCk7Ij5UaGVyZSBhcmUgc29tZSBudWdnZXRzIG9mIHRydXRoIGlu
IHdoYXQgc2hlIHNheXMgaW4gdGhpcyBhcnRpY2xlLCBhbmQgaW4gc29tZSBvZiB0aGUgY29tbWVu
dHMuIEkgdGhpbmsgdGhhdCB0aGUgcHJvYmxlbXMgYXJlIHJlYWwsIHNvIHRoZXJl4oCZcyB2YWx1
ZSBpbiB0YWtpbmcgdGhlIGNyaXRpY2lzbSBjb25zdHJ1Y3RpdmVseSwgZGVzcGl0ZSB0aGUgZmFj
dCB0aGF0IHRoZSBhdXRob3IgY2hvc2UNCiB0byBmb2N1cyBvbiB0aGUgcHJvYmxlbXMgd2l0aG91
dCBhbnkgc3VnZ2VzdGlvbnMgb2Ygc29sdXRpb25zLjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6
IHJnYigwLCAwLCAwKTsiPjxicj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbjow
IDAgMCA0MHB4OyBib3JkZXI6bm9uZTsgcGFkZGluZzowcHg7Ij4NCjxkaXYgc3R5bGU9ImNvbG9y
OiByZ2IoMCwgMCwgMCk7Ij4mcXVvdDt3aGlsZSB0aGUgcGFjZSBhdCB3aGljaCBzdGFuZGFyZHMg
YXJlIHdyaXR0ZW4gaGFzbuKAmXQgY2hhbmdlZCBpbiBtYW55IHllYXJzLCB0aGUgcGFjZSBhdCB3
aGljaCB0aGUgcmVhbCB3b3JsZCBhZG9wdHMgc29mdHdhcmUgaGFzIGJlY29tZSBvcmRlcnMgb2Yg
bWFnbml0dWRlIGZhc3Rlci4mcXVvdDs8L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwg
MCwgMCk7Ij7igKY8L2Rpdj4NCjxkaXY+JnF1b3Q7PHNwYW4gc3R5bGU9ImJhY2tncm91bmQtY29s
b3I6IHJnYigyNTUsIDI1NSwgMjU1KTsiPjxmb250IGNvbG9yPSIjMmEyZTMzIj48c3BhbiBzdHls
ZT0ibGluZS1oZWlnaHQ6IDIycHg7Ij5SdW5uaW5nIGNvZGUgYW5kIHJvdWdoIGNvbnNlbnN1cywg
dGhlIG1vdHRvIG9mIHRoZSBJRVRGLCB1c2VkIHRvIGJlIHJlYWxpemFibGUgYXQgc29tZSBwb2lu
dC4mbmJzcDvigKYmbmJzcDtJbiB0aGUgbmFtZSBvZiBjb25zZW5zdXMsIHdlIGRlYmF0ZSBmcml2
b2xvdXMgZGV0YWlscw0KIGZvcmV2ZXIuIEluIHRoZSBuYW1lIG9mIHBhdGVudHMsIHdlIG5ldmVy
IGZpbmlzaC48L3NwYW4+PC9mb250Pjwvc3Bhbj48Zm9udCBjb2xvcj0iIzJhMmUzMyI+PHNwYW4g
c3R5bGU9ImxpbmUtaGVpZ2h0OiAyMnB4OyI+4oCdPC9zcGFuPjwvZm9udD48L2Rpdj4NCjxkaXY+
PGZvbnQgY29sb3I9IiMyYTJlMzMiPjxzcGFuIHN0eWxlPSJsaW5lLWhlaWdodDogMjJweDsiPuKA
pjwvc3Bhbj48L2ZvbnQ+PC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyI+
DQo8ZGl2PiZxdW90O1VubGVzcyB0aGVzZSBzdGFuZGFyZHMgb3JnYW5pemF0aW9ucyBtYWtlIHJh
ZGljYWwgc2hpZnRzIHRvd2FyZHMgcHJhY3RpY2FsaXR5LCB0aGVpciByZWxldmFuY2Ugd2lsbCBz
b29uIGJlIHF1ZXN0aW9uYWJsZS7igJ08L2Rpdj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6
IHJnYigwLCAwLCAwKTsiPjxicj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdiBzdHlsZT0i
Y29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZv
bnQtc2l6ZTogMTRweDsiPg0KSSBkb27igJl0IGhhdmUgdG9vIG1hbnkgYmlnIGlkZWFzIGhvdyB0
byBmaXggdGhlc2UgcHJvYmxlbXMsIGJ1dCBJ4oCZbGwgYXQgbGVhc3QgdGFrZSBhIGNyYWNrIGF0
IGl0IGluIG9yZGVyIHRvIHNwdXIgZGlzY3Vzc2lvbi4gTXkgcGFyYXBocmFzZSBvZiB0aGUgcHJv
YmxlbSBhbmQgc29tZSBkaXNjdXNzaW9uIGZvbGxvd3MuPC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xv
cjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsgZm9udC1z
aXplOiAxNHB4OyI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoMCwgMCwg
MCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0cHg7Ij4N
Ci0gV2XigJl2ZSBsb3N0IHNpZ2h0IG9mIGNvbnNlbnN1cyBhbmQgYXJlIHRvbyBvZnRlbiBkZXJh
aWxlZCBieSBhIHZvY2FsIG1pbm9yaXR5IG9mIHRob3NlIHdpbGxpbmcgdG8gZW5kbGVzc2x5IGRl
YmF0ZSBhIHBvaW50LjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9u
dC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KPGJyPg0K
PC9kaXY+DQo8ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2Fs
aWJyaSwgc2Fucy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQpQYXJ0IG9mIHRoZSBzb2x1dGlv
biB0byB0aGF0IGlzIHJlaXRlcmF0aW5nIHdoYXQgY29uc2Vuc3VzIGlzIGFuZCBpcyBub3QsIHN1
Y2ggYXMgZHJhZnQtcmVzbmljay1vbi1jb25zZW5zdXMgc28gdGhhdCB3ZSBkb27igJl0IGNvbmZ1
c2UgYSBuZWVkIGZvciBjb25zZW5zdXMgd2l0aCBhIG5lZWQgZm9yIHVuYW5pbWl0eS4gUGFydCBv
ZiB0aGUgc29sdXRpb24gaXMgSUVURiBsZWFkZXJzaGlwIGhlbHBpbmcgdG8gaWRlbnRpZnkgd2hl
biB3ZSBoYXZlIHJvdWdoDQogY29uc2Vuc3VzIGVuY3VtYmVyZWQgYnkgYSBkZWJhdGUgdGhhdCB3
aWxsIG5ldmVyIHJlc29sdmUgaXRzZWxmLCB3aXRob3V0IHF1aWV0aW5nIGFjdHVhbCBkaXNhZ3Jl
ZW1lbnQgdGhhdCBuZWVkcyBjb250aW51ZWQgZGlzY3Vzc2lvbiBpbiBvcmRlciB0byBmaW5kIGEg
Y29tcHJvbWlzZS4gSSBkb27igJl0IGhhdmUgZ29vZCBzdWdnZXN0aW9ucyBvbiBob3cgdG8gbWFr
ZSB0aGF0IHNlY29uZCBoYWxmIGJldHRlci48L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9yOiByZ2Io
MCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNpemU6IDE0
cHg7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAwKTsgZm9u
dC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0KLSBXZSBk
b27igJl0IGhhdmUgbmVhcmx5IGVub3VnaCBmb2N1cyBvbiBydW5uaW5nIGNvZGUgYXMgdGhlIHRo
aW5nIHRoYXQgaGVscHMgdG8gZW5zdXJlIHRoYXQgd2XigJlyZSB1c2luZyBvdXIgbGltaXRlZCBj
eWNsZXMgb24gZ2V0dGluZyB0aGUgcmlnaHQgdGhpbmdzIG91dCBleHBlZGllbnRseSwgYW5kIGVp
dGhlciBnZXR0aW5nIHRoZSBkZXNpZ24gcmlnaHQgdGhlIGZpcnN0IHRpbWUsIG9yIGZhaWxpbmcg
cXVpY2tseSBhbmQgaXRlcmF0aW5nIHRvIGltcHJvdmU8L2Rpdj4NCjxkaXYgc3R5bGU9ImNvbG9y
OiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250LXNp
emU6IDE0cHg7Ij4NCjxicj4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0iY29sb3I6IHJnYigwLCAwLCAw
KTsgZm9udC1mYW1pbHk6IENhbGlicmksIHNhbnMtc2VyaWY7IGZvbnQtc2l6ZTogMTRweDsiPg0K
VGhlIHNvbHV0aW9uIGhlcmUgbWF5IGJlIHRoYXQgd2UgbmVlZCB0byBiZSBtdWNoIG1vcmUgYWdn
cmVzc2l2ZSBhdCBleHBlY3RpbmcgYW55IHN0YW5kYXJkcyB0cmFjayBkb2N1bWVudHMgdG8gaGF2
ZSBydW5uaW5nIGNvZGUgbXVjaCBlYXJsaWVyIGluIHRoZSBwcm9jZXNzLiBUaGUgb3RoZXIgcGFy
dCBvZiB0aGF0IGlzIHRvIHJlbmV3IG91ciBmb2N1cyBvbiBhY3R1YWwgaW50ZXJvcCBzdGFuZGFy
ZHMgd29yaywgcHJvYmFibHkgYnkgY2hhcnRlcg0KIG9yIGluLWdyb3VwIGZlZWRiYWNrLCBzaGlm
dCBmb2N1cyBhd2F5IGZyb20gQkNQIGFuZCBpbmZvIGRvY3VtZW50cy4gUGVyaGFwcyB3aGVuIGNv
bnNpZGVyaW5nIHdoZXRoZXIgdG8gcHJvY2VlZCB3aXRoIGEgZ2l2ZW4gZG9jdW1lbnQsIHdlIG5l
ZWQgdGVzdCBhcyB0byB3aGV0aGVyIGl04oCZcyBhY3RpdmVseSBoZWxwZnVsL25lZWRlZCBhbmQg
ZW5zdXJlIHRoYXQgd2Uga25vdyB3aGF0IGF1ZGllbmNlIHdvdWxkIGJlIGxvb2tpbmcgYXQgaXQs
IHJhdGhlcg0KIHRoYW4gc2ltcGx5IGVuc3VyaW5nIHRoYXQgaXQgaXMg4oCcbm90IGhhcm1mdWzi
gJ0gYW5kIG1vc3RseSB3aXRoaW4gdGhlIFdH4oCZcyBjaGFydGVyZWQgZm9jdXMuPC9kaXY+DQo8
ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDAsIDAsIDApOyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fu
cy1zZXJpZjsgZm9udC1zaXplOiAxNHB4OyI+DQo8YnI+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9ImNv
bG9yOiByZ2IoMCwgMCwgMCk7IGZvbnQtZmFtaWx5OiBDYWxpYnJpLCBzYW5zLXNlcmlmOyBmb250
LXNpemU6IDE0cHg7Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDBpbiAw
aW4gMC4wMDAxcHQ7IGZvbnQtc2l6ZTogMTFwdDsiPlRoYW5rcyw8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7IGZvbnQt
c2l6ZTogMTFwdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFw
dDsiPiZuYnNwOzwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
OiAwaW4gMGluIDAuMDAwMXB0OyBmb250LXNpemU6IDExcHQ7Ij5XZXMgR2VvcmdlPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwaW4gMGluIDAuMDAw
MXB0OyBmb250LXNpemU6IDExcHQ7Ij48c3BhbiBzdHlsZT0iY29sb3I6IHJnYigxMjcsIDEyNywg
MTI3KTsgZm9udC1zaXplOiAxMXB0OyI+PGJyPg0KPC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7IGZvbnQtc2l6ZTogMTFwdDsi
PjxzcGFuIHN0eWxlPSJjb2xvcjogcmdiKDEyNywgMTI3LCAxMjcpOyBmb250LXNpemU6IDExcHQ7
Ij5Bbnl0aGluZyBiZWxvdyB0aGlzIGxpbmUgaGFzIGJlZW4gYWRkZWQgYnkgbXkgY29tcGFueeKA
mXMgbWFpbCBzZXJ2ZXIsIEkgaGF2ZSBubyBjb250cm9sIG92ZXIgaXQuPC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDBpbiAwaW4gMC4wMDAxcHQ7IGZvbnQt
c2l6ZTogMTFwdDsiPjxzcGFuIHN0eWxlPSJjb2xvcjogcmdiKDEyNywgMTI3LCAxMjcpOyI+LS0t
LS0tLS0tLS08L3NwYW4+PC9wPg0KPC9kaXY+DQo8YnI+DQo8aHI+DQo8Zm9udCBmYWNlPSJBcmlh
bCIgY29sb3I9IkdyYXkiIHNpemU9IjEiPlRoaXMgRS1tYWlsIGFuZCBhbnkgb2YgaXRzIGF0dGFj
aG1lbnRzIG1heSBjb250YWluIFRpbWUgV2FybmVyIENhYmxlIHByb3ByaWV0YXJ5IGluZm9ybWF0
aW9uLCB3aGljaCBpcyBwcml2aWxlZ2VkLCBjb25maWRlbnRpYWwsIG9yIHN1YmplY3QgdG8gY29w
eXJpZ2h0IGJlbG9uZ2luZyB0byBUaW1lIFdhcm5lciBDYWJsZS4gVGhpcyBFLW1haWwgaXMgaW50
ZW5kZWQgc29sZWx5DQogZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRv
IHdoaWNoIGl0IGlzIGFkZHJlc3NlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lw
aWVudCBvZiB0aGlzIEUtbWFpbCwgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBhbnkgZGlz
c2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBjb3B5aW5nLCBvciBhY3Rpb24gdGFrZW4gaW4gcmVs
YXRpb24gdG8gdGhlIGNvbnRlbnRzIG9mIGFuZCBhdHRhY2htZW50cyB0bw0KIHRoaXMgRS1tYWls
IGlzIHN0cmljdGx5IHByb2hpYml0ZWQgYW5kIG1heSBiZSB1bmxhd2Z1bC4gSWYgeW91IGhhdmUg
cmVjZWl2ZWQgdGhpcyBFLW1haWwgaW4gZXJyb3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBp
bW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkgZGVsZXRlIHRoZSBvcmlnaW5hbCBhbmQgYW55IGNv
cHkgb2YgdGhpcyBFLW1haWwgYW5kIGFueSBwcmludG91dC48YnI+DQo8L2ZvbnQ+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_CF71721A180A9wesleygeorgetwcablecom_--


From nobody Mon Apr 14 08:09:20 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 987721A047E for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:09:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 1-zuRLoilyNq for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:09:17 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 297501A0262 for <ietf@ietf.org>; Mon, 14 Apr 2014 08:09:13 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 5E18FCC0BA for <ietf@ietf.org>; Mon, 14 Apr 2014 11:09:10 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id cSFHwXs9sVL9 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:09:01 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id C04E3CC0A4 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:09:01 -0400 (EDT)
Message-ID: <534BFA0D.7000404@meetinghouse.net>
Date: Mon, 14 Apr 2014 11:09:01 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us>
In-Reply-To: <534B9760.90301@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OKfQBWbEHrZf5UKbvJi_Xa_DHNk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 15:09:18 -0000

Doug Barton wrote:

<snip>
>
>
> But your point is well taken ... the "right" answer may be to fix or 
> discard DMARC, I honestly don't know. But in a world where DMARC is 
> here to stay, or if not DMARC then some other anti-spam solution that 
> breaks mailing list forwarding; and in that same world where mailing 
> list traffic is negligible (and therefore the cost of breaking mailing 
> lists is in the noise compared to the benefits of deploying said 
> anti-spam solution) it's incumbent on the mailing list software folks 
> to solve this problem

Is it perhaps also incumbent on the folks promulgating DMARC (and its 
predecessors, and its sure-to-be successors) to work cooperatively with 
mailing list developers, rather than taking the position "nope, we break 
mailing lists, not our problem?"

I'm kind of coming to the conclusion that what we need to be looking at 
is defining an SMTP extension that addresses BOTH sets of concerns - and 
doing so in a cooperative manner that engages not just the community 
behind DKIM and DMARC, but also the developers and operators of mailman, 
sympa, majordomo, listserv - and ideally the sendmail, postfix, exim, 
qmail community.

Dare I suggest that this calls for an IETF working group?

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 08:11:02 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE5741A0242 for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:19:33 -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, SPF_PASS=-0.001] autolearn=ham
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 2tQqUoKmswAj for <ietf@ietfa.amsl.com>; Sun, 13 Apr 2014 13:19:32 -0700 (PDT)
Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 42A201A0226 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:19:32 -0700 (PDT)
Received: by mail-yh0-f48.google.com with SMTP id z6so7229781yhz.21 for <ietf@ietf.org>; Sun, 13 Apr 2014 13:19:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=FsDRvGr+HQxskvdgWauVVFC1o45VNKfOagJylwdaEOg=; b=i8rDW7mCzG03PRigj6uj180WZ5CGCPob0wny5co6XrALU9bQ6gCzZERvlOH1LTorLx YB2Ap+W7AWP4SbfKxP/wkE6N+YZspZK7Jq0WRRl6px2zlF/uiSg45ngt3t1M/p9/GYTw lAHiUR81fkF4nYx+4JdFB6+FWHwTpCtn+0Zb1Kb5kPeJecFRFOivRt5ptVzepgtUQ0Ue ihLG5jEhYwwq3YjxgrmwLNJXtEtcAgo4GWcf4ADv/llpXkn29gbyUjTyQy84kahqxlD2 6qa/RPHoOBPMoKWccs5qTLu+AUfqdzylpM8ykgEtoOBRqIY7fWZkFGUyIIiR/oDdQI5L 3ucw==
X-Received: by 10.236.198.243 with SMTP id v79mr5366688yhn.87.1397420369968; Sun, 13 Apr 2014 13:19:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.170.129.143 with HTTP; Sun, 13 Apr 2014 13:18:49 -0700 (PDT)
In-Reply-To: <01P6L9JZF5SC00004W@mauve.mrochek.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com>
From: Dick Franks <rwfranks@gmail.com>
Date: Sun, 13 Apr 2014 21:18:49 +0100
Message-ID: <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
To: ned+ietf@mauve.mrochek.com
Content-Type: multipart/alternative; boundary=089e0160bea6c102d704f6f24892
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SdalsTEusa79z2OUfK_6Qffe2pM
X-Mailman-Approved-At: Mon, 14 Apr 2014 08:10:52 -0700
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Apr 2014 20:19:33 -0000

--089e0160bea6c102d704f6f24892
Content-Type: text/plain; charset=UTF-8

On 13 April 2014 00:35, <ned+ietf@mauve.mrochek.com> wrote:
[snip]

>
> The real question we should be discussing is what options the IETF has to
> try
> and address this.
>

IETF has already adequately addressed this issue by its insistence on
inclusion of this statement in the document preamble:

  It is inappropriate to use Internet-Drafts as reference

  material or to cite them other than as "work in progress."

An implementation based on I-D reference material is therefore no
better than "work in progress".

The blame for this debacle lies squarely with Yahoo, and its
inadequate engineering change management.

--089e0160bea6c102d704f6f24892
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On 13 April 2014 00:35,  <span dir=3D"lt=
r">&lt;<a href=3D"mailto:ned+ietf@mauve.mrochek.com" target=3D"_blank">ned+=
ietf@mauve.mrochek.com</a>&gt;</span> wrote:<br></div><div class=3D"gmail_q=
uote">

[snip]<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">
<br>
The real question we should be discussing is what options the IETF has to t=
ry<br>
and address this.<br>
</blockquote></div><br></div><div class=3D"gmail_extra">IETF has already ad=
equately addressed this issue by its insistence on inclusion of this statem=
ent in the document preamble:<br></div><div class=3D"gmail_extra"><pre>  It=
 is inappropriate to use Internet-Drafts as reference<br>

  material or to cite them other than as &quot;work in progress.&quot;<br><=
br></pre><pre>An implementation based on I-D reference material is therefor=
e no better than &quot;work in progress&quot;.<br><br></pre><pre>The blame =
for this debacle lies squarely with Yahoo, and its inadequate engineering c=
hange management.<br>

</pre><pre><br><br></pre></div></div>

--089e0160bea6c102d704f6f24892--


From nobody Mon Apr 14 08:11:19 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19B901A0545 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:11:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 e6lS4v8swm2P for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:11:02 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id B23E41A052E for <ietf@ietf.org>; Mon, 14 Apr 2014 08:11:01 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 31AB0CC0B9 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:10:59 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id r87YjY8hVOcV for <ietf@ietf.org>; Mon, 14 Apr 2014 11:10:50 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7A7B0CC0A4 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:10:50 -0400 (EDT)
Message-ID: <534BFA7A.3010601@meetinghouse.net>
Date: Mon, 14 Apr 2014 11:10:50 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
In-Reply-To: <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SrX52rfqlAd-Atb8upuFsSnv5Q8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 15:11:07 -0000

John C Klensin wrote:
> I'm going to risk more humor and suggest that everyone who
> believes that mailing list traffic is negligible and the cost of
> breaking them is in the noise should be immediately unsubscribed
> from all IETF-related lists, including this one.
>
>
But then how could the rest of us yell at them (excuse me, educate 
them)?    :-)

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From syedalisuleman@gmail.com  Sat Apr 12 10:45:38 2014
Return-Path: <syedalisuleman@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE54B1A0209 for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 10:45:38 -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, SPF_PASS=-0.001] autolearn=ham
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 QEbcPrYhJ_yN for <ietf@ietfa.amsl.com>; Sat, 12 Apr 2014 10:45:38 -0700 (PDT)
Received: from mail-ig0-x236.google.com (mail-ig0-x236.google.com [IPv6:2607:f8b0:4001:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id 074621A0207 for <ietf@ietf.org>; Sat, 12 Apr 2014 10:45:37 -0700 (PDT)
Received: by mail-ig0-f182.google.com with SMTP id uy17so1994726igb.9 for <ietf@ietf.org>; Sat, 12 Apr 2014 10:45:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=yYfNwzWBuBiol0r5haBFxR1qFfni8vHrkSyLrJBXvQM=; b=gSfJ3l/S31oLCpDDUhkBbHl/ayKznoK0DvtggWfAHrt3Arfz/QPOLxFhHPLXulq14f Bk0BQFD4INkWouIIEgb1jKXpwwWNqyaD06GkedGzFnBQ4MzwPy3x4mjOGuC4Y6hjFnCg 97xuQ3tgxdcY55OW/+OhV/wrdGnfUQycX5/nFnE7Q9SG9sjEfzdF/mIvGKALEeWCKa0G mtGtIZCLZlr2uZ3yK0tFuYKH0eSxxiqPT5qC+D9mUU4ALEmWKsfnIJwqNSetJcfr7gdQ AvtdTnGKU1l0xbGJ6Y9F8rIHkBaINOPKlv9Ct3Ahlu4NvKEsjjhhdYboeZ2MKrnANFcX tG4g==
MIME-Version: 1.0
X-Received: by 10.50.61.177 with SMTP id q17mr4953126igr.44.1397324736225; Sat, 12 Apr 2014 10:45:36 -0700 (PDT)
Received: by 10.64.7.107 with HTTP; Sat, 12 Apr 2014 10:45:36 -0700 (PDT)
Date: Sat, 12 Apr 2014 22:45:36 +0500
Message-ID: <CAHgexWdXoQ1of5CLBojjKtv+qGBqxr6U=36KOvH8-sd+r=cDVw@mail.gmail.com>
Subject: IETF recommendations for Video Traffic Types
From: Ali Suleman <syedalisuleman@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=047d7bdca44089e74604f6dc04a4
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/N4cBgJ7Wdrb_Bu_SqEUfZYLjLFo
X-Mailman-Approved-At: Mon, 14 Apr 2014 08:14:40 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 Apr 2014 17:48:57 -0000

--047d7bdca44089e74604f6dc04a4
Content-Type: text/plain; charset=ISO-8859-1

Hello,

I was working on a research and I was wondering if IETF could help me in
which video traffic classifications are recommended by IETF. It would be
great if you provide a link to some official document/website URL. Thanks a
lot!

Best regards,

-- 
*Ali Suleman*

--047d7bdca44089e74604f6dc04a4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>I was working on a research and =
I was wondering if IETF could help me in which video traffic classification=
s are recommended by IETF. It would be great if you provide a link to some =
official document/website URL. Thanks a lot!</div>
<div><br></div><div>Best regards,<br clear=3D"all"><div><br></div>-- <br><d=
iv dir=3D"ltr"><b><font size=3D"4">Ali Suleman</font></b><br></div>
</div></div>

--047d7bdca44089e74604f6dc04a4--


From nobody Mon Apr 14 08:36:43 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CA3D1A02CF for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:36:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.819
X-Spam-Level: *
X-Spam-Status: No, score=1.819 tagged_above=-999 required=5 tests=[BAYES_50=0.8, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 6eysx5Qs0hHr for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:36:36 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 7FE591A04A6 for <ietf@ietf.org>; Mon, 14 Apr 2014 08:36:36 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id A48E0CC0BB for <ietf@ietf.org>; Mon, 14 Apr 2014 11:36:33 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 3gHSZSM+3ZMm for <ietf@ietf.org>; Mon, 14 Apr 2014 11:36:25 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id C64BECC0B9 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:36:24 -0400 (EDT)
Message-ID: <534C0078.3070808@meetinghouse.net>
Date: Mon, 14 Apr 2014 11:36:24 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com>
In-Reply-To: <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4ot3Nwg1MblSq0lQ-wnb-uTU7N8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 15:36:39 -0000

Dick Franks wrote:
>
>
> On 13 April 2014 00:35, <ned+ietf@mauve.mrochek.com 
> <mailto:ned+ietf@mauve.mrochek.com>> wrote:
> [snip]
>
>
>     The real question we should be discussing is what options the IETF
>     has to try
>     and address this.
>
>
> IETF has already adequately addressed this issue by its insistence on 
> inclusion of this statement in the document preamble:
>    It is inappropriate to use Internet-Drafts as reference
>
>
>    material or to cite them other than as "work in progress."
>
> An implementation based on I-D reference material is therefore no better than "work in progress".
>
> The blame for this debacle lies squarely with Yahoo, and its inadequate engineering change management.
>

That's all in the fine print.  The folks behind DMARC are representing 
DMARC as both IETF standards-track - both implicitly (by pointing to a 
"specification" published as an IETF document) and explicitly (multiple 
statements along the lines of "intended as... " and "intend to submit), 
and as mature.  Yahoo is using that to justify it's actions ("Today, 80% 
of US email user accounts and over 2B accounts globally can be protected 
by the DMARC standard.")

By no sense of the imagination is DMARC a "standard" (or even much of a 
specification) - IETF or otherwise - much less a mature one.

To my mind, IETF's inaction, and silence is both morally wrong, and 
carries a longer term risk:

- as the Internet standards body, IETF and its participant have a 
professional and moral responsibility to speak for "what is an Internet 
standard," as well as what constitutes responsible implementation, 
deployment, and operation of Internet protocols -- not just leave it in 
the fine print

- IETF, to a large degree, dropped the ball on a "standard," that for 
some period of time was worked on under the aegis of an IETF WG

- allowing someone to represent something as an IETF standard carries a 
risk to IETF's standing, effectiveness, and credibility as the 
Internet's standards body (ISO tends to get very upset if someone claims 
to be ISO9000 certified, but isn't; Xerox sends lawyers after 
competitors who refer to their copiers as "xerox machines")

 From an operational perspective, concerned with the stability and 
reliability of the Internet infrastructure, this kind of thing really 
scares me - particularly in the larger context of current discussions 
over changes to Internet governance.  This strikes me as a very clear 
cut example where our voluntary, cooperative model for doing things is 
failing very badly -- in large part because none of our institutions of 
self-governance are stepping up to the plate.  ("We wrote a disclaimer 
in the fine print" is not stepping up to the plate.)

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 08:39:00 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D82E51A04AB for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 1fASE71jad9e for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:38:53 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id DC6C81A02CF for <ietf@ietf.org>; Mon, 14 Apr 2014 08:38:52 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 72AC8CC0B9 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:38:50 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id k-C6qFJ2XW1Z for <ietf@ietf.org>; Mon, 14 Apr 2014 11:38:41 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 9C3AECC0A7 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:38:41 -0400 (EDT)
Message-ID: <534C0101.6040208@meetinghouse.net>
Date: Mon, 14 Apr 2014 11:38:41 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net>, <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <290E20B455C66743BE178C5C84F1240847E88E3F8C@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E88E3F8C@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4VekO_Ggs1iDOqyYaWUaTTh9K0E
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 15:38:58 -0000

You really need to use <sarcasm></sarcasm> tags - my first reaction was 
a knee-jerk "says who?"

Miles

l.wood@surrey.ac.uk wrote:
> But DMARC is email authentication best practice.
>
> Sure, some legacy email things are having some minor teething problems with it,
> but it's clearly the way to go. Because it introduces authentication.
>
> Now all the spammers will have to open their free yahoo accounts first, before
> sending email! That's a great step forwards!
>
> Security! Best practice!
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of John R Levine [johnl@taugh.com]
> Sent: 14 April 2014 04:28
> To: Dave Crocker; IETF general list
> Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
>
>>> Yes, that's the 1980s percent hack.
>> intended recipient.  While a bit inefficient -- and probably will emerge as
>> an attack vector (sigh) -- it's a plausible mechanism.
> Right -- something is seriously wrong with DMARC as used if we need to
> invent new phish syntaxes to work around it.
>
> R's,
> John


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 08:49:01 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 799361A049A for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:49:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 tE0p2xGAU2dD for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:48:59 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) by ietfa.amsl.com (Postfix) with ESMTP id 675AC1A0479 for <ietf@ietf.org>; Mon, 14 Apr 2014 08:48:58 -0700 (PDT)
Received: from unnumerable.local (pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89]) (authenticated bits=0) by nostrum.com (8.14.8/8.14.7) with ESMTP id s3EFmtFQ080374 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK) for <ietf@ietf.org>; Mon, 14 Apr 2014 10:48:56 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-173-71-50-89.dllstx.fios.verizon.net [173.71.50.89] claimed to be unnumerable.local
Message-ID: <534C0366.10600@nostrum.com>
Date: Mon, 14 Apr 2014 10:48:54 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Logging into the datatracker
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/n_-TYX1pzriSMQALvuWAKbzABAA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 15:49:00 -0000

Today's datatracker release changed the way you sign in, and has added 
the ability to sign out.

See <https://datatracker.ietf.org/release/> for details.

RjS

p.s. As usual, if you need to request a password reset, you can do so at
<http://datatracker.ietf.org/accounts/>



From nobody Mon Apr 14 08:57:22 2014
Return-Path: <dmm@1-4-5.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F82E1A04C2 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:57:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.422
X-Spam-Level: *
X-Spam-Status: No, score=1.422 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 j4ksZgSqS1pk for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 08:57:17 -0700 (PDT)
Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3311A01D9 for <ietf@ietf.org>; Mon, 14 Apr 2014 08:57:16 -0700 (PDT)
Received: by mail-qg0-f53.google.com with SMTP id f51so7547154qge.40 for <ietf@ietf.org>; Mon, 14 Apr 2014 08:57:14 -0700 (PDT)
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:content-type :content-transfer-encoding; bh=kYS1Fkgw5ky0CdoNKaVjZNnT/me3XsPs5SxSFfN1d6M=; b=CNEcIBERcuA3DWGul2I2ujTIUu3hKKMJDJ+BRxWYx1j/IDeSL61EwhGPR2oN5ABkHr wJo3Q0oZUBY6f3JNal7aqpzqjBAjjvB9ETtXtVyP2LsejA/tTVd+NRyw+XSYRoQejeFX 5dA98BnDHUABHgrGEUwlQZldp1vXgQFn73wb2D7XtsN85VLtA0bWcK0rD24xFgcPf3pO KQ/tY8CY90TO3ukJlr16MuoL71CHRmQo0qYz/QqqC0V/JemC9lixmIFvpN176kWz87vI G81L3rEJyug9LX4Sr5xXscMq6ileIh9LzpSvOhThXpWMnnHuy/PqaZGuzqBSOmLAmz5v xeMQ==
X-Gm-Message-State: ALoCoQmaHqpC31kERZXPd+JeeHYRQ92Z1oRvnp+HWmA9G7g2B2A8SVZZsOU7Q5FYG3Kqv3Qqp+4/
MIME-Version: 1.0
X-Received: by 10.140.29.131 with SMTP id b3mr49442089qgb.5.1397491034286; Mon, 14 Apr 2014 08:57:14 -0700 (PDT)
Received: by 10.140.105.98 with HTTP; Mon, 14 Apr 2014 08:57:14 -0700 (PDT)
X-Originating-IP: [12.35.79.254]
In-Reply-To: <CF71721A.180A9%wesley.george@twcable.com>
References: <CF71721A.180A9%wesley.george@twcable.com>
Date: Mon, 14 Apr 2014 08:57:14 -0700
Message-ID: <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: David Meyer <dmm@1-4-5.net>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Sox1CSh3VxRJsD9sC-BJn1IWtqE
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 15:57:21 -0000

On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.com> wr=
ote:
> I=E2=80=99m surprised that no one has sent this out yet:
> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>
> "Summary: After contributing to standards organizations for more than sev=
en
> years, engineer Vidya Narayanan decided it was time to move on. Although =
she
> still believes that these organizations make the Internet a better place,
> she wonders about the pace of change versus the pace of organizations."
>
> My thoughts-
>
> There are some nuggets of truth in what she says in this article, and in
> some of the comments. I think that the problems are real, so there=E2=80=
=99s value
> in taking the criticism constructively, despite the fact that the author
> chose to focus on the problems without any suggestions of solutions.
>
> "while the pace at which standards are written hasn=E2=80=99t changed in =
many years,
> the pace at which the real world adopts software has become orders of
> magnitude faster."
> =E2=80=A6
> "Running code and rough consensus, the motto of the IETF, used to be
> realizable at some point. =E2=80=A6 In the name of consensus, we debate f=
rivolous
> details forever. In the name of patents, we never finish.=E2=80=9D
> =E2=80=A6
> "Unless these standards organizations make radical shifts towards
> practicality, their relevance will soon be questionable.=E2=80=9D
>
> I don=E2=80=99t have too many big ideas how to fix these problems, but I=
=E2=80=99ll at least
> take a crack at it in order to spur discussion. My paraphrase of the prob=
lem
> and some discussion follows.
>
> - We=E2=80=99ve lost sight of consensus and are too often derailed by a v=
ocal
> minority of those willing to endlessly debate a point.
>
> Part of the solution to that is reiterating what consensus is and is not,
> such as draft-resnick-on-consensus so that we don=E2=80=99t confuse a nee=
d for
> consensus with a need for unanimity. Part of the solution is IETF leaders=
hip
> helping to identify when we have rough consensus encumbered by a debate t=
hat
> will never resolve itself, without quieting actual disagreement that need=
s
> continued discussion in order to find a compromise. I don=E2=80=99t have =
good
> suggestions on how to make that second half better.
>
> - We don=E2=80=99t have nearly enough focus on running code as the thing =
that helps
> to ensure that we=E2=80=99re using our limited cycles on getting the righ=
t things
> out expediently, and either getting the design right the first time, or
> failing quickly and iterating to improve
>
> The solution here may be that we need to be much more aggressive at
> expecting any standards track documents to have running code much earlier=
 in
> the process. The other part of that is to renew our focus on actual inter=
op
> standards work, probably by charter or in-group feedback, shift focus awa=
y
> from BCP and info documents. Perhaps when considering whether to proceed
> with a given document, we need test as to whether it=E2=80=99s actively
> helpful/needed and ensure that we know what audience would be looking at =
it,
> rather than simply ensuring that it is =E2=80=9Cnot harmful=E2=80=9D and =
mostly within the
> WG=E2=80=99s chartered focus.

My friend @colin_dixon pointed this out to me yesterday, and I've been
giving it quite a bit of thought since then (I have a nascent blog on
the topic of how open source and standards orgs might
productively/efficiently work together; follow up to
http://www.sdncentral.com/education/david-meyer-reflections-opendaylight-op=
en-source-project-brocade/2014/03).

What I can say is that after seeing the kind of progress that several
open source communities make (they do epitomize the best of the IETF's
running code/rough consensus ethic), one does have to wonder if
traditional standards making is either obsolete or in dire need of a
make over. What is needed, IMO, is a reimagining of how the standards
process interacts with the open source movement specifically focused
on how they can compliment one another.

--dmm


From nobody Mon Apr 14 09:02:17 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3DC91A0505 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:02:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.018
X-Spam-Level: *
X-Spam-Status: No, score=1.018 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 LxohKcjPZsw9 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:02:14 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id BCCDB1A04A6 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:02:14 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id A1687CC0C0 for <ietf@ietf.org>; Mon, 14 Apr 2014 12:02:11 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ThahmGxCOR3L for <ietf@ietf.org>; Mon, 14 Apr 2014 12:02:07 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id AAE11CC0BC for <ietf@ietf.org>; Mon, 14 Apr 2014 12:02:05 -0400 (EDT)
Message-ID: <534C067D.8080506@meetinghouse.net>
Date: Mon, 14 Apr 2014 12:02:05 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
In-Reply-To: <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LVQ3VuUalhF4tVf9E7z2fAyMPf0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:02:16 -0000

David Meyer wrote:
> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.com> wrote:
>> Iâ€™m surprised that no one has sent this out yet:
>> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>>
>> "Summary: After contributing to standards organizations for more than seven
>> years, engineer Vidya Narayanan decided it was time to move on. Although she
>> still believes that these organizations make the Internet a better place,
>> she wonders about the pace of change versus the pace of organizations."
>>
>>
>> My friend @colin_dixon pointed this out to me yesterday, and I've been
>> giving it quite a bit of thought since then (I have a nascent blog on
>> the topic of how open source and standards orgs might
>> productively/efficiently work together; follow up to
>> http://www.sdncentral.com/education/david-meyer-reflections-opendaylight-open-source-project-brocade/2014/03).
>>
>> What I can say is that after seeing the kind of progress that several
>> open source communities make (they do epitomize the best of the IETF's
>> running code/rough consensus ethic), one does have to wonder if
>> traditional standards making is either obsolete or in dire need of a
>> make over. What is needed, IMO, is a reimagining of how the standards
>> process interacts with the open source movement specifically focused
>> on how they can compliment one another.
>>

Funny - I spent years pointing out to folks the advantages of the RFC 
process and IETF, over traditional standards bodies and procedures 
(e.g., ISO).  And here we are thinking about IETF as "traditional."

Then again, the current DMARC debacle presents a cautionary tale of more 
ad hoc approaches.

One example that comes to mind is RSS and Atom - started outside, then 
pulled under the IETF process.

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 09:08:05 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E837B1A0601 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 d9jLatI3NtFv for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:08:01 -0700 (PDT)
Received: from mail-yk0-x234.google.com (mail-yk0-x234.google.com [IPv6:2607:f8b0:4002:c07::234]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4221A03D7 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:07:45 -0700 (PDT)
Received: by mail-yk0-f180.google.com with SMTP id 19so7528140ykq.25 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:07:41 -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:content-type:content-transfer-encoding; bh=yudIQ+i4/XPNt01Y7SCrYHCNsL88ZDL8gALkRqKJ170=; b=0zgrECxAVHH9EOI1xIE/0OOE6jTk1Zn+GJ/+8E6xedlqE63ptvfiVEpsW+FxQKqZPV jyCOkMQW2z7ddu7lBlMa1LSLLMZXo4iGXLAHpXbXX2fHTYFd8u8H3tTOCaO330SAj9R+ 8yAj2zU1JXzAGVyz1SxWSGhcdab5rg6K+Vjme80qO1Z0PFRmSgleeK+qc3mKLu2pqWSI 1UbJlhwPudDGcu2FQt8TX4Cqz1XxGtaOTdomSPzmGNxsPss87mviOl0MyNSl0iJllxXT KM/bzt5yFh3srMVhWxeqPP2xlktG/5JSps9z8nEy5xGFnw6sYUBq3wRPSPBEoEwGLybP 0DrQ==
MIME-Version: 1.0
X-Received: by 10.236.138.73 with SMTP id z49mr2013202yhi.152.1397491661698; Mon, 14 Apr 2014 09:07:41 -0700 (PDT)
Received: by 10.170.194.69 with HTTP; Mon, 14 Apr 2014 09:07:41 -0700 (PDT)
In-Reply-To: <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
Date: Mon, 14 Apr 2014 12:07:41 -0400
Message-ID: <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: Alia Atlas <akatlas@gmail.com>
To: David Meyer <dmm@1-4-5.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gX5V1wJVv-2RFggssvmk-jYf0zE
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:08:03 -0000

On Mon, Apr 14, 2014 at 11:57 AM, David Meyer <dmm@1-4-5.net> wrote:
> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.com> =
wrote:
>> I=E2=80=99m surprised that no one has sent this out yet:
>> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>>
>> "Summary: After contributing to standards organizations for more than se=
ven
>> years, engineer Vidya Narayanan decided it was time to move on. Although=
 she
>> still believes that these organizations make the Internet a better place=
,
>> she wonders about the pace of change versus the pace of organizations."
>>
>> My thoughts-
>>
>> There are some nuggets of truth in what she says in this article, and in
>> some of the comments. I think that the problems are real, so there=E2=80=
=99s value
>> in taking the criticism constructively, despite the fact that the author
>> chose to focus on the problems without any suggestions of solutions.
>>
>> "while the pace at which standards are written hasn=E2=80=99t changed in=
 many years,
>> the pace at which the real world adopts software has become orders of
>> magnitude faster."
>> =E2=80=A6
>> "Running code and rough consensus, the motto of the IETF, used to be
>> realizable at some point. =E2=80=A6 In the name of consensus, we debate =
frivolous
>> details forever. In the name of patents, we never finish.=E2=80=9D
>> =E2=80=A6
>> "Unless these standards organizations make radical shifts towards
>> practicality, their relevance will soon be questionable.=E2=80=9D
>>
>> I don=E2=80=99t have too many big ideas how to fix these problems, but I=
=E2=80=99ll at least
>> take a crack at it in order to spur discussion. My paraphrase of the pro=
blem
>> and some discussion follows.
>>
>> - We=E2=80=99ve lost sight of consensus and are too often derailed by a =
vocal
>> minority of those willing to endlessly debate a point.
>>
>> Part of the solution to that is reiterating what consensus is and is not=
,
>> such as draft-resnick-on-consensus so that we don=E2=80=99t confuse a ne=
ed for
>> consensus with a need for unanimity. Part of the solution is IETF leader=
ship
>> helping to identify when we have rough consensus encumbered by a debate =
that
>> will never resolve itself, without quieting actual disagreement that nee=
ds
>> continued discussion in order to find a compromise. I don=E2=80=99t have=
 good
>> suggestions on how to make that second half better.
>>
>> - We don=E2=80=99t have nearly enough focus on running code as the thing=
 that helps
>> to ensure that we=E2=80=99re using our limited cycles on getting the rig=
ht things
>> out expediently, and either getting the design right the first time, or
>> failing quickly and iterating to improve
>>
>> The solution here may be that we need to be much more aggressive at
>> expecting any standards track documents to have running code much earlie=
r in
>> the process. The other part of that is to renew our focus on actual inte=
rop
>> standards work, probably by charter or in-group feedback, shift focus aw=
ay
>> from BCP and info documents. Perhaps when considering whether to proceed
>> with a given document, we need test as to whether it=E2=80=99s actively
>> helpful/needed and ensure that we know what audience would be looking at=
 it,
>> rather than simply ensuring that it is =E2=80=9Cnot harmful=E2=80=9D and=
 mostly within the
>> WG=E2=80=99s chartered focus.
>
> My friend @colin_dixon pointed this out to me yesterday, and I've been
> giving it quite a bit of thought since then (I have a nascent blog on
> the topic of how open source and standards orgs might
> productively/efficiently work together; follow up to
> http://www.sdncentral.com/education/david-meyer-reflections-opendaylight-=
open-source-project-brocade/2014/03).
>
> What I can say is that after seeing the kind of progress that several
> open source communities make (they do epitomize the best of the IETF's
> running code/rough consensus ethic), one does have to wonder if
> traditional standards making is either obsolete or in dire need of a
> make over. What is needed, IMO, is a reimagining of how the standards
> process interacts with the open source movement specifically focused
> on how they can compliment one another.

[Alia] It would be very useful to have a functional model for how the
two can compliment each other.  We also tend to talk about open-source
as a single monolith - when it can have very different models for
accepting in changes, how and who runs the community, who is really
participating (open source doesn't mean non-corporate) etc.   Some of
what the IETF does is the architecture and requirements thinking about
how the solution should fit in - while some of the open-source is
about getting a solution implemented ASAP.   IMHO, a spiral is useful
with an easy way of interaction.  With I2RS, as a WG chair, I
suggested having experimental drafts describing solutions that were
being implemented - but haven't seen any.   A question is what is
needed to encourage the interactions.

[Alia] Diversity of implementation is important as is stability of a
standard and it being understood how to change/upgrade for different
versions.  These don't come automatically via open-source.

Regards,
Alia


From nobody Mon Apr 14 09:10:07 2014
Return-Path: <cdel@firsthand.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA4851A0646 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.689
X-Spam-Level: **
X-Spam-Status: No, score=2.689 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272] autolearn=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 5jnKszERmNtm for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:09:52 -0700 (PDT)
Received: from bmtwo.vm.bytemark.co.uk (mail.firsthand.net [IPv6:2001:41c8:1:6062::d46e:bc35]) by ietfa.amsl.com (Postfix) with ESMTP id 80C8F1A0639 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:09:46 -0700 (PDT)
X-No-Relay: not in my network
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=firsthand.net;  b=k9VpZwE/BKvEgY+S3dcuLAuFi0Dv5kjVczvyYPeoja6Y97M97sPSiZnVTLydab/R3syY9jLh7oQ2mkwF2q6fV368plh6KoWF4OTwU3jiP9zwmti6akHIPABzyofgHn9W; h=X-No-Relay:X-No-Relay:Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type;
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from orionlocal.local (host-78-149-8-96.as13285.net [78.149.8.96]) by bmtwo.vm.bytemark.co.uk (Postfix) with ESMTPSA id 787A2E0100; Mon, 14 Apr 2014 16:09:40 +0100 (BST)
Message-ID: <534C0842.7030005@firsthand.net>
Date: Mon, 14 Apr 2014 17:09:38 +0100
From: Christian de Larrinaga <cdel@firsthand.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: "George, Wes" <wesley.george@twcable.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com>
In-Reply-To: <CF71721A.180A9%wesley.george@twcable.com>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig4B1E42717DE656E6B9866E51"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dkOw0rEy0xHYWVQ1SDvax_gBMsc
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: cdel@firsthand.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:09:54 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig4B1E42717DE656E6B9866E51
Content-Type: multipart/alternative;
 boundary="------------050701080005000802080705"

This is a multi-part message in MIME format.
--------------050701080005000802080705
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Two observations.

First her point that the pace of change at " which the real world adopts
software has become orders of magnitude faster."

This is true at the applications layer but Internet layer has not seen
fast adoption of new services and protocols by networks. IPv6 has been
dismally slow.  This maybe one reason why IoT deployments are focussing
at application layer services and ignoring IP other than implement
ICE/STUN/TURN which otherwise would be unrequired complication.

Much of this has been outside standardisation controls being in the
decision making hands of the financial managers of network operators and
their customers.

Secondly maybe she should have stood for the IAB. We should have people
involved who are prepared to shake not just the cobwebs but the
spiders.  Somehow the link between having power (knowledge etc) for
defining "standards" and having the power to define their adoption have
diverged.

If true then IETF could benefit from having more users and operators (of
all sizes and shapes) involved - perhaps?


C

George, Wes wrote:
> I=E2=80=99m surprised that no one has sent this out
> yet: http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards=
/
>
> "Summary: After contributing to standards organizations for more than
> seven years, engineer Vidya Narayanan decided it was time to move on.
> Although she still believes that these organizations make the Internet
> a better place, she wonders about the pace of change versus the pace
> of organizations."
>
> My thoughts-
>
> There are some nuggets of truth in what she says in this article, and
> in some of the comments. I think that the problems are real, so
> there=E2=80=99s value in taking the criticism constructively, despite t=
he fact
> that the author chose to focus on the problems without any suggestions
> of solutions.
>
>     "while the pace at which standards are written hasn=E2=80=99t chang=
ed in
>     many years, the pace at which the real world adopts software has
>     become orders of magnitude faster."
>     =E2=80=A6
>     "Running code and rough consensus, the motto of the IETF, used to
>     be realizable at some point. =E2=80=A6 In the name of consensus, we=
 debate
>     frivolous details forever. In the name of patents, we never finish.=
=E2=80=9D
>     =E2=80=A6
>     "Unless these standards organizations make radical shifts towards
>     practicality, their relevance will soon be questionable.=E2=80=9D
>
> I don=E2=80=99t have too many big ideas how to fix these problems, but =
I=E2=80=99ll at
> least take a crack at it in order to spur discussion. My paraphrase of
> the problem and some discussion follows.
>
> - We=E2=80=99ve lost sight of consensus and are too often derailed by a=
 vocal
> minority of those willing to endlessly debate a point.
>
> Part of the solution to that is reiterating what consensus is and is
> not, such as draft-resnick-on-consensus so that we don=E2=80=99t confus=
e a
> need for consensus with a need for unanimity. Part of the solution is
> IETF leadership helping to identify when we have rough consensus
> encumbered by a debate that will never resolve itself, without
> quieting actual disagreement that needs continued discussion in order
> to find a compromise. I don=E2=80=99t have good suggestions on how to m=
ake
> that second half better.
>
> - We don=E2=80=99t have nearly enough focus on running code as the thin=
g that
> helps to ensure that we=E2=80=99re using our limited cycles on getting =
the
> right things out expediently, and either getting the design right the
> first time, or failing quickly and iterating to improve
>
> The solution here may be that we need to be much more aggressive at
> expecting any standards track documents to have running code much
> earlier in the process. The other part of that is to renew our focus
> on actual interop standards work, probably by charter or in-group
> feedback, shift focus away from BCP and info documents. Perhaps when
> considering whether to proceed with a given document, we need test as
> to whether it=E2=80=99s actively helpful/needed and ensure that we know=
 what
> audience would be looking at it, rather than simply ensuring that it
> is =E2=80=9Cnot harmful=E2=80=9D and mostly within the WG=E2=80=99s cha=
rtered focus.
>
> Thanks,
>
>  =20
>
> Wes George
>
>
> Anything below this line has been added by my company=E2=80=99s mail se=
rver, I
> have no control over it.
>
> -----------
>
>
> -----------------------------------------------------------------------=
-
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject
> to copyright belonging to Time Warner Cable. This E-mail is intended
> solely for the use of the individual or entity to which it is
> addressed. If you are not the intended recipient of this E-mail, you
> are hereby notified that any dissemination, distribution, copying, or
> action taken in relation to the contents of and attachments to this
> E-mail is strictly prohibited and may be unlawful. If you have
> received this E-mail in error, please notify the sender immediately
> and permanently delete the original and any copy of this E-mail and
> any printout.

--=20
Christian de Larrinaga
FBCS, CITP, MCMA
-------------------------
@ FirstHand
-------------------------
+44 7989 386778
cdel@firsthand.net
-------------------------

--------------050701080005000802080705
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Type">=

</head><body style=3D"font-family: Calibri; font-size: 12pt;"=20
bgcolor=3D"#FFFFFF" text=3D"#000000"><div style=3D"font-size:=20
12pt;font-family: Calibri;"><span style=3D"font-family: Calibri;">Two=20
observations. <br><br>First her point that the pace of change </span><spa=
n>at
 " which the real world adopts software has become orders of magnitude=20
faster." </span><br><br>This is true at the applications layer but=20
Internet layer has not seen fast adoption of new services and protocols=20
by networks. IPv6 has been dismally slow.=C2=A0 This maybe one reason why=
 IoT
 deployments are focussing at application layer services and ignoring IP
 other than implement ICE/STUN/TURN which otherwise would be unrequired=20
complication. <br><br>Much of this has been outside standardisation=20
controls being in the decision making hands of the financial managers of
 network operators and their customers. <br><br>Secondly maybe she=20
should have stood for the IAB. We should have people involved who are=20
prepared to shake not just the cobwebs but the spiders.=C2=A0 Somehow the=
=20
link between having power (knowledge etc) for defining "standards" and=20
having the power to define their adoption have diverged. <br><br>If true
 then IETF could benefit from having more users and operators (of all=20
sizes and shapes) involved - perhaps?<br><br><br>C<br><br>George, Wes=20
wrote:<blockquote style=3D"word-wrap: break-word; -webkit-nbsp-mode:=20
space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0);=20
font-size: 14px; font-family: Calibri, sans-serif;"=20
cite=3D"mid:CF71721A.180A9%25wesley.george@twcable.com" type=3D"cite"><me=
ta=20
http-equiv=3D"Content-Type" content=3D"text/html; charset=3DUTF-8">


<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
I=E2=80=99m surprised that no one has sent this out yet:=C2=A0<a=20
moz-do-not-send=3D"true"=20
href=3D"http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standard=
s/">http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/</=
a></div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0);">"Summary:=C2=A0<span=20
style=3D"background-color: rgb(255, 255, 255); color: rgb(42, 46, 51);=20
font-style: italic; line-height: 22px;">After contributing to standards=20
organizations for more than seven years, engineer Vidya Narayanan
 decided it was time to move on. Although she still believes that these=20
organizations make the Internet a better place, she wonders about the=20
pace of change versus the pace of organizations."</span></div>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<div style=3D"color: rgb(0, 0, 0);">My thoughts-</div>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<div style=3D"color: rgb(0, 0, 0);">There are some nuggets of truth in=20
what she says in this article, and in some of the comments. I think that
 the problems are real, so there=E2=80=99s value in taking the criticism =

constructively, despite the fact that the author chose
 to focus on the problems without any suggestions of solutions.</div>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div>
<blockquote style=3D"margin:0 0 0 40px; border:none; padding:0px;"><div=20
style=3D"color: rgb(0, 0, 0);">"while the pace at which standards are=20
written hasn=E2=80=99t changed in many years, the pace at which the real =
world=20
adopts software has become orders of magnitude faster."</div>
<div style=3D"color: rgb(0, 0, 0);">=E2=80=A6</div>
<div>"<span style=3D"background-color: rgb(255, 255, 255);"><font=20
color=3D"#2a2e33"><span style=3D"line-height: 22px;">Running code and rou=
gh=20
consensus, the motto of the IETF, used to be realizable at some=20
point.=C2=A0=E2=80=A6=C2=A0In the name of consensus, we debate frivolous =
details
 forever. In the name of patents, we never finish.</span></font></span><f=
ont
 color=3D"#2a2e33"><span style=3D"line-height: 22px;">=E2=80=9D</span></f=
ont></div>
<div><font color=3D"#2a2e33"><span style=3D"line-height: 22px;">=E2=80=A6=
</span></font></div>
<div style=3D"color: rgb(0, 0, 0);">
<div>"Unless these standards organizations make radical shifts towards=20
practicality, their relevance will soon be questionable.=E2=80=9D</div>
</div>
<div style=3D"color: rgb(0, 0, 0);"><br>
</div></blockquote>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
I don=E2=80=99t have too many big ideas how to fix these problems, but I=E2=
=80=99ll at=20
least take a crack at it in order to spur discussion. My paraphrase of=20
the problem and some discussion follows.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
- We=E2=80=99ve lost sight of consensus and are too often derailed by a v=
ocal=20
minority of those willing to endlessly debate a point.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
Part of the solution to that is reiterating what consensus is and is=20
not, such as draft-resnick-on-consensus so that we don=E2=80=99t confuse =
a need=20
for consensus with a need for unanimity. Part of the solution is IETF=20
leadership helping to identify when we have rough
 consensus encumbered by a debate that will never resolve itself,=20
without quieting actual disagreement that needs continued discussion in=20
order to find a compromise. I don=E2=80=99t have good suggestions on how =
to make
 that second half better.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
- We don=E2=80=99t have nearly enough focus on running code as the thing =
that=20
helps to ensure that we=E2=80=99re using our limited cycles on getting th=
e right
 things out expediently, and either getting the design right the first=20
time, or failing quickly and iterating to improve</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
The solution here may be that we need to be much more aggressive at=20
expecting any standards track documents to have running code much=20
earlier in the process. The other part of that is to renew our focus on=20
actual interop standards work, probably by charter
 or in-group feedback, shift focus away from BCP and info documents.=20
Perhaps when considering whether to proceed with a given document, we=20
need test as to whether it=E2=80=99s actively helpful/needed and ensure t=
hat we=20
know what audience would be looking at it, rather
 than simply ensuring that it is =E2=80=9Cnot harmful=E2=80=9D and mostly=
 within the=20
WG=E2=80=99s chartered focus.</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
<br>
</div>
<div style=3D"color: rgb(0, 0, 0); font-family: Calibri, sans-serif;=20
font-size: 14px;">
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt=
;">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt=
;"><o:p>=C2=A0</o:p><span
 style=3D"font-size: 11pt;">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt=
;">Wes
 George<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt=
;"><span
 style=3D"color: rgb(127, 127, 127); font-size: 11pt;"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt=
;"><span
 style=3D"color: rgb(127, 127, 127); font-size: 11pt;">Anything below thi=
s
 line has been added by my company=E2=80=99s mail server, I have no contr=
ol over
 it.</span></p>
<p class=3D"MsoNormal" style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt=
;"><span
 style=3D"color: rgb(127, 127, 127);">-----------</span></p>
</div>
<br>
<hr>
<font color=3D"Gray" face=3D"Arial" size=3D"1">This E-mail and any of its=
=20
attachments may contain Time Warner Cable proprietary information, which
 is privileged, confidential, or subject to copyright belonging to Time=20
Warner Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If=20
you are not the intended recipient of this E-mail, you are hereby=20
notified that any dissemination, distribution, copying, or action taken=20
in relation to the contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have=20
received this E-mail in error, please notify the sender immediately and=20
permanently delete the original and any copy of this E-mail and any=20
printout.<br>
</font></blockquote><br><div class=3D"moz-signature">-- <br>Christian de =

Larrinaga <br>
FBCS, CITP, MCMA <br>
-------------------------<br>
 <span style=3D"font-weight: bold;">@ FirstHand</span><br=20
style=3D"font-weight: bold;">
-------------------------<br>
+44 7989 386778<br>
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:cdel@firsthand.net">=
cdel@firsthand.net</a> <br>
-------------------------<br>
</div></div></body></html>

--------------050701080005000802080705--

--------------enig4B1E42717DE656E6B9866E51
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCgAGBQJTTAhEAAoJEO8NEF3l27YrEB4H/RRjJf6XUILE3NV4MMx41M0F
7F8L6V1Ee2+IoKvp4xhwb1RfUPi9FqFJBycE3WDHPH/r7+gKN9JIywOxoJMaVd+P
RYRCt4pw82LR/Ub8NilgkBA3Bq6DuTl7zuDf5OE5/W5gdOUJugwz6JDPTt/e3RF7
EL7hMB3ZQ1Ot2mSToPjZhV5W4ARs0KNuEt/W7eL8ASDG1F3qRAkX9gt2gBNU0VJI
p5Aakvx42IrAsxwf6H1yj5lfgy+LoNunmFQftuZDkM/1+bHJzvvt2B90l75aK83n
GH4g7Xs9Ov8O/YX8le+QR0WGD8FeGnvANTe8pqWnbT9zeBae36jpQoluDDoH0t0=
=YwMW
-----END PGP SIGNATURE-----

--------------enig4B1E42717DE656E6B9866E51--


From nobody Mon Apr 14 09:11:36 2014
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCD181A0515 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.722
X-Spam-Level: 
X-Spam-Status: No, score=0.722 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 ZMM2wrEPy_Xb for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:11:31 -0700 (PDT)
Received: from mail-qa0-f48.google.com (mail-qa0-f48.google.com [209.85.216.48]) by ietfa.amsl.com (Postfix) with ESMTP id A75861A0639 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:11:29 -0700 (PDT)
Received: by mail-qa0-f48.google.com with SMTP id s7so7609756qap.7 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:11:27 -0700 (PDT)
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:content-type; bh=clcsblMuYa72n3EdOEyvbdn09lgDVgt9/kmU3V6tZj0=; b=SxDSiX8gToqBjikSztRTrvw09OCvTHOSDgvr2LOOCSx5NOta2qjJVawuQVVtMfD7x3 3vZ1SyRbcarpkRuqmgHBZ2D6UZu9hgvd06WftcQ3uYPg+JRoa6getTxjLgqRfHo0ReIq 7RJ9uBXIXJzLJzByCyrer62ZT55qpdO0/NaeiLFOPKfRGijNKt6KjzNl+i7gcMsGkhVU pqHgco+VT2lPXsGXBc1TpFJnlPtIvEGpfzCh3dsW3fKAjRDfXGEWVazWK9FUNBaLcWQu Bz+we6O+GegssnaMhEfAXUMAmjOj2Ee7miJeChHCeA23EABEpdrWNv4WtkVxnztvm4D5 h+Qg==
X-Gm-Message-State: ALoCoQkyyvNjUd8DNqkardY2Hxt38XK3ahm2w/D3SyOxQQDAGCIMlMPQ+raxg36U6wX+vT5ONW8+
MIME-Version: 1.0
X-Received: by 10.224.16.69 with SMTP id n5mr47549907qaa.7.1397491886990; Mon, 14 Apr 2014 09:11:26 -0700 (PDT)
Received: by 10.140.41.134 with HTTP; Mon, 14 Apr 2014 09:11:26 -0700 (PDT)
In-Reply-To: <CF71721A.180A9%wesley.george@twcable.com>
References: <CF71721A.180A9%wesley.george@twcable.com>
Date: Mon, 14 Apr 2014 09:11:26 -0700
Message-ID: <CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: Andy Bierman <andy@yumaworks.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: multipart/alternative; boundary=047d7bea398680397b04f702eff8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ly7jSzQNOk0qewSK3OGkS8lBSAU
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:11:34 -0000

--047d7bea398680397b04f702eff8
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.com>wrote:

>  I'm surprised that no one has sent this out yet:
> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>
>  "Summary: After contributing to standards organizations for more than
> seven years, engineer Vidya Narayanan decided it was time to move on.
> Although she still believes that these organizations make the Internet a
> better place, she wonders about the pace of change versus the pace of
> organizations."
>
>  My thoughts-
>
>  There are some nuggets of truth in what she says in this article, and in
> some of the comments. I think that the problems are real, so there's value
> in taking the criticism constructively, despite the fact that the author
> chose to focus on the problems without any suggestions of solutions.
>
>  "while the pace at which standards are written hasn't changed in many
> years, the pace at which the real world adopts software has become orders
> of magnitude faster."
> ...
>
>
I think this issue (used to be called "timeliness") is critical and
continues to be overlooked.
The charter milestones are just not that relevant to the process, and it
shows.
It takes a long time to go from individual I-D -00 to RFC.

IMO all WGs behind schedule should be taking steps to finish faster, like
monthly virtual interim meetings, real interim meetings, etc.  More remote
meeting and project management tools might help some.


"Running code and rough consensus, the motto of the IETF, used to be
> realizable at some point. ... In the name of consensus, we debate frivolous
> details forever. In the name of patents, we never finish."
> ...
>  "Unless these standards organizations make radical shifts towards
> practicality, their relevance will soon be questionable."
>
>   I don't have too many big ideas how to fix these problems, but I'll at
> least take a crack at it in order to spur discussion. My paraphrase of the
> problem and some discussion follows.
>
>  - We've lost sight of consensus and are too often derailed by a vocal
> minority of those willing to endlessly debate a point.
>
>  Part of the solution to that is reiterating what consensus is and is
> not, such as draft-resnick-on-consensus so that we don't confuse a need for
> consensus with a need for unanimity. Part of the solution is IETF
> leadership helping to identify when we have rough consensus encumbered by a
> debate that will never resolve itself, without quieting actual disagreement
> that needs continued discussion in order to find a compromise. I don't have
> good suggestions on how to make that second half better.
>
>
Consensus is the real commodity here.
Perhaps vendors are figuring out they can get a better outcome by
contributing
to corporate open-source projects instead of SDOs.
Customers just want software that works with their equipment.

Vendor engineers just want to work together to produce a solution
that meets the requirements for the specific upcoming release.
There is no way for "bad actors" who want to stall or delay the
effort to have any influence on the engineering.  There is no
tail-heavy review process to introduce extraordinary delays.



>  - We don't have nearly enough focus on running code as the thing that
> helps to ensure that we're using our limited cycles on getting the right
> things out expediently, and either getting the design right the first time,
> or failing quickly and iterating to improve
>
>
With the open-source approach to consensus, running code is the entire
focus.
This is a bug and a feature.  The documentation quality is much higher in
the IETF.


>  The solution here may be that we need to be much more aggressive at
> expecting any standards track documents to have running code much earlier
> in the process. The other part of that is to renew our focus on actual
> interop standards work, probably by charter or in-group feedback, shift
> focus away from BCP and info documents. Perhaps when considering whether to
> proceed with a given document, we need test as to whether it's actively
> helpful/needed and ensure that we know what audience would be looking at
> it, rather than simply ensuring that it is "not harmful" and mostly within
> the WG's chartered focus.
>
>
Generally it is very time-consuming to implement a protocol I-D in progress.
The draft will change so radically and so often before the final RFC is
published,
that lots of code will get re-written in the effort.  People are told "too
bad, it's
just a work-in-progress", but that doesn't help promote early
implementations.

The IETF needs to reduce the cost of consensus somehow.


 Thanks,
>
>
>
> Wes George
>
>
>
Andy

--047d7bea398680397b04f702eff8
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <span dir=3D"ltr">&lt;=
<a href=3D"mailto:wesley.george@twcable.com" target=3D"_blank">wesley.georg=
e@twcable.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">



<div style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
I&rsquo;m surprised that no one has sent this out yet:&nbsp;<a href=3D"http=
://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/" target=3D"=
_blank">http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/=
</a></div>

<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style>&quot;Summary:&nbsp;<span style=3D"line-height:22px;color:rgb(42=
,46,51);font-style:italic">After contributing to standards organizations fo=
r more than seven years, engineer Vidya Narayanan
 decided it was time to move on. Although she still believes that these org=
anizations make the Internet a better place, she wonders about the pace of =
change versus the pace of organizations.&quot;</span></div>
<div style><br>
</div>
<div style>My thoughts-</div>
<div style><br>
</div>
<div style>There are some nuggets of truth in what she says in this article=
, and in some of the comments. I think that the problems are real, so there=
&rsquo;s value in taking the criticism constructively, despite the fact tha=
t the author chose
 to focus on the problems without any suggestions of solutions.</div>
<div style><br>
</div>
<blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px">
<div style>&quot;while the pace at which standards are written hasn&rsquo;t=
 changed in many years, the pace at which the real world adopts software ha=
s become orders of magnitude faster.&quot;</div>
<div style>&hellip;</div></blockquote></div></blockquote><div><br></div><di=
v>I think this issue (used to be called &quot;timeliness&quot;) is critical=
 and continues to be overlooked.</div><div>The charter milestones are just =
not that relevant to the process, and it shows.</div>
<div>It takes a long time to go from individual I-D -00 to RFC.</div><div><=
br></div><div>IMO all WGs behind schedule should be taking steps to finish =
faster, like</div><div>monthly virtual interim meetings, real interim meeti=
ngs, etc. &nbsp;More remote</div>
<div>meeting and project management tools might help some.</div><div><br></=
div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border=
-left-style:solid;padding-left:1ex">
<div style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break=
-word"><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:0px=
">
<div>&quot;<span style><font color=3D"#2a2e33"><span style=3D"line-height:2=
2px">Running code and rough consensus, the motto of the IETF, used to be re=
alizable at some point.&nbsp;&hellip;&nbsp;In the name of consensus, we deb=
ate frivolous details
 forever. In the name of patents, we never finish.</span></font></span><fon=
t color=3D"#2a2e33"><span style=3D"line-height:22px">&rdquo;</span></font><=
/div>
<div><font color=3D"#2a2e33"><span style=3D"line-height:22px">&hellip;</spa=
n></font></div>
<div style>
<div>&quot;Unless these standards organizations make radical shifts towards=
 practicality, their relevance will soon be questionable.&rdquo;</div>
</div>
<div style><br>
</div>
</blockquote>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
I don&rsquo;t have too many big ideas how to fix these problems, but I&rsqu=
o;ll at least take a crack at it in order to spur discussion. My paraphrase=
 of the problem and some discussion follows.</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
- We&rsquo;ve lost sight of consensus and are too often derailed by a vocal=
 minority of those willing to endlessly debate a point.</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
Part of the solution to that is reiterating what consensus is and is not, s=
uch as draft-resnick-on-consensus so that we don&rsquo;t confuse a need for=
 consensus with a need for unanimity. Part of the solution is IETF leadersh=
ip helping to identify when we have rough
 consensus encumbered by a debate that will never resolve itself, without q=
uieting actual disagreement that needs continued discussion in order to fin=
d a compromise. I don&rsquo;t have good suggestions on how to make that sec=
ond half better.</div>

<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br></div></div></blockquote><div><br></div><div>Consensus is the real comm=
odity here.</div><div>Perhaps vendors are figuring out they can get a bette=
r outcome by contributing</div><div>to corporate open-source projects inste=
ad of SDOs.</div>
<div>Customers just want software that works with their equipment.<br></div=
><div><br></div><div>Vendor engineers just want to work together to produce=
 a solution</div><div>that meets the requirements for the specific upcoming=
 release.</div>
<div>There is no way for &quot;bad actors&quot; who want to stall or delay =
the</div><div>effort to have any influence on the engineering. &nbsp;There =
is no</div><div>tail-heavy review process to introduce extraordinary delays=
.</div>
<div><br></div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,20=
4,204);border-left-style:solid;padding-left:1ex"><div style=3D"font-size:14=
px;font-family:Calibri,sans-serif;word-wrap:break-word">
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
- We don&rsquo;t have nearly enough focus on running code as the thing that=
 helps to ensure that we&rsquo;re using our limited cycles on getting the r=
ight things out expediently, and either getting the design right the first =
time, or failing quickly and iterating to improve</div>

<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br></div></div></blockquote><div><br></div><div>With the open-source appro=
ach to consensus, running code is the entire focus.</div><div>This is a bug=
 and a feature. &nbsp;The documentation quality is much higher in the IETF.=
</div>
<div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex"><div style=3D"font-size:14px;font-family:=
Calibri,sans-serif;word-wrap:break-word">
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
The solution here may be that we need to be much more aggressive at expecti=
ng any standards track documents to have running code much earlier in the p=
rocess. The other part of that is to renew our focus on actual interop stan=
dards work, probably by charter
 or in-group feedback, shift focus away from BCP and info documents. Perhap=
s when considering whether to proceed with a given document, we need test a=
s to whether it&rsquo;s actively helpful/needed and ensure that we know wha=
t audience would be looking at it, rather
 than simply ensuring that it is &ldquo;not harmful&rdquo; and mostly withi=
n the WG&rsquo;s chartered focus.</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br></div></div></blockquote><div><br></div><div>Generally it is very time-=
consuming to implement a protocol I-D in progress.</div><div>The draft will=
 change so radically and so often before the final RFC is published,</div>
<div>that lots of code will get re-written in the effort. &nbsp;People are =
told &quot;too bad, it&#39;s</div><div>just a work-in-progress&quot;, but t=
hat doesn&#39;t help promote early implementations.</div><div><br></div><di=
v>
The IETF needs to reduce the cost of consensus somehow.</div><div><br></div=
><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-le=
ft-style:solid;padding-left:1ex">
<div style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break=
-word"><div style=3D"font-size:14px;font-family:Calibri,sans-serif">
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt">Tha=
nks,<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt"><u>=
</u>&nbsp;<u></u><span style=3D"font-size:11pt">&nbsp;</span></p>
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt">Wes=
 George<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt"><sp=
an style=3D"color:rgb(127,127,127);font-size:11pt"><br></span></p></div></d=
iv></blockquote><div><br></div><div>Andy</div><div><br></div></div></div></=
div>

--047d7bea398680397b04f702eff8--


From nobody Mon Apr 14 09:17:43 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF6501A0653 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:17:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 uz1iFN6R-UYe for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:17:35 -0700 (PDT)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id D41AC1A0667 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:17:03 -0700 (PDT)
Received: by mail-yh0-f43.google.com with SMTP id b6so8191617yha.2 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:17:01 -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:content-type; bh=y/nBpIEVjfqXWWyQ57tboIsakmubNF6kf2y+rwKUyeM=; b=Eth5rezeJnXaIWcHINz81uWQ2+i3bB4rnPE7U2hYEXyfHWY8K1KkaZhdWvpc51Wy3K DPWHmeiPck6u8pcX4W6/6oUOuoLGI00LywEl6OUHUwq+fXOrITDR8fCO87/7nx4sE/il bZ2XqluD4RpM6UCJle2zK2p85wOY8rgG1T1AbGPpW/7VH7/FqWGLbAX6M3w93QqXmXA3 IPJhtvdzNFEy0fUgwfimB1oR6FkALkzoinHS1RAiOyuhO4a0QIdr3xzjYH7V+YCaeDNF skf9t7NldKbcG6wIjWYxmOxq3RuC2y397TpByMEZukmuNu6NPGJGW1fWxDucPhNArHvu iopA==
MIME-Version: 1.0
X-Received: by 10.236.79.134 with SMTP id i6mr60155149yhe.16.1397492221266; Mon, 14 Apr 2014 09:17:01 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Mon, 14 Apr 2014 09:17:01 -0700 (PDT)
In-Reply-To: <CF71721A.180A9%wesley.george@twcable.com>
References: <CF71721A.180A9%wesley.george@twcable.com>
Date: Mon, 14 Apr 2014 17:17:01 +0100
Message-ID: <CADnDZ88i9tzST7d8QraJ4HMuCVqr2NPBvDej3p0SRwuS0zQbQw@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: multipart/alternative; boundary=20cf300510446cd0a004f70303e2
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QHred_8XQl7XPtmAFK_o8MqGBVs
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:17:40 -0000

--20cf300510446cd0a004f70303e2
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I was thinking of why many quit reviewing adopted IETF drafts (or even quit
participating). In my situation there is a draft adopted in 6Lo WG and
still the author does not answer my question reminder, and it may make me
quit reviewing as well. I think IETF does not have problem of
participants quit to write but participants quit to review and contribute
more into drafts.

AB

On Monday, April 14, 2014, George, Wes wrote:

>  I=E2=80=99m surprised that no one has sent this out yet:
> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>
>  "Summary: After contributing to standards organizations for more than
> seven years, engineer Vidya Narayanan decided it was time to move on.
> Although she still believes that these organizations make the Internet a
> better place, she wonders about the pace of change versus the pace of
> organizations."
>
>  My thoughts-
>
>  There are some nuggets of truth in what she says in this article, and in
> some of the comments. I think that the problems are real, so there=E2=80=
=99s value
> in taking the criticism constructively, despite the fact that the author
> chose to focus on the problems without any suggestions of solutions.
>
>  "while the pace at which standards are written hasn=E2=80=99t changed in=
 many
> years, the pace at which the real world adopts software has become orders
> of magnitude faster."
> =E2=80=A6
> "Running code and rough consensus, the motto of the IETF, used to be
> realizable at some point. =E2=80=A6 In the name of consensus, we debate f=
rivolous
> details forever. In the name of patents, we never finish.=E2=80=9D
> =E2=80=A6
>  "Unless these standards organizations make radical shifts towards
> practicality, their relevance will soon be questionable.=E2=80=9D
>
>   I don=E2=80=99t have too many big ideas how to fix these problems, but =
I=E2=80=99ll at
> least take a crack at it in order to spur discussion. My paraphrase of th=
e
> problem and some discussion follows.
>
>  - We=E2=80=99ve lost sight of consensus and are too often derailed by a =
vocal
> minority of those willing to endlessly debate a point.
>
>  Part of the solution to that is reiterating what consensus is and is
> not, such as draft-resnick-on-consensus so that we don=E2=80=99t confuse =
a need for
> consensus with a need for unanimity. Part of the solution is IETF
> leadership helping to identify when we have rough consensus encumbered by=
 a
> debate that will never resolve itself, without quieting actual disagreeme=
nt
> that needs continued discussion in order to find a compromise. I don=E2=
=80=99t have
> good suggestions on how to make that second half better.
>
>  - We don=E2=80=99t have nearly enough focus on running code as the thing=
 that
> helps to ensure that we=E2=80=99re using our limited cycles on getting th=
e right
> things out expediently, and either getting the design right the first tim=
e,
> or failing quickly and iterating to improve
>
>  The solution here may be that we need to be much more aggressive at
> expecting any standards track documents to have running code much earlier
> in the process. The other part of that is to renew our focus on actual
> interop standards work, probably by charter or in-group feedback, shift
> focus away from BCP and info documents. Perhaps when considering whether =
to
> proceed with a given document, we need test as to whether it=E2=80=99s ac=
tively
> helpful/needed and ensure that we know what audience would be looking at
> it, rather than simply ensuring that it is =E2=80=9Cnot harmful=E2=80=9D =
and mostly within
> the WG=E2=80=99s chartered focus.
>
>  Thanks,
>
>
>
> Wes George
>
>
>  Anything below this line has been added by my company=E2=80=99s mail ser=
ver, I
> have no control over it.
>
> -----------
>
> ------------------------------
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to Time Warner Cable. This E-mail is intended solely
> for the use of the individual or entity to which it is addressed. If you
> are not the intended recipient of this E-mail, you are hereby notified th=
at
> any dissemination, distribution, copying, or action taken in relation to
> the contents of and attachments to this E-mail is strictly prohibited and
> may be unlawful. If you have received this E-mail in error, please notify
> the sender immediately and permanently delete the original and any copy o=
f
> this E-mail and any printout.
>

--20cf300510446cd0a004f70303e2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I was thinking of why many=C2=A0quit reviewing adopted IETF=C2=A0drafts (or=
 even=C2=A0quit participating). In my situation there is a=C2=A0draft adopt=
ed in 6Lo WG and still the author does not answer my question reminder, and=
 it=C2=A0may make me quit reviewing=C2=A0as well. I think IETF does not hav=
e problem of participants=C2=A0quit to write but participants=C2=A0quit to =
review and contribute more into drafts.=C2=A0<div>
<br></div><div>AB<br><br>On Monday, April 14, 2014, George, Wes  wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
I=E2=80=99m surprised that no one has sent this out yet:=C2=A0<a href=3D"ht=
tp://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/" target=
=3D"_blank">http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standa=
rds/</a></div>

<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style>&quot;Summary:=C2=A0<span style=3D"line-height:22px;color:rgb(42=
,46,51);font-style:italic">After contributing to standards organizations fo=
r more than seven years, engineer Vidya Narayanan
 decided it was time to move on. Although she still believes that these org=
anizations make the Internet a better place, she wonders about the pace of =
change versus the pace of organizations.&quot;</span></div>
<div style><br>
</div>
<div style>My thoughts-</div>
<div style><br>
</div>
<div style>There are some nuggets of truth in what she says in this article=
, and in some of the comments. I think that the problems are real, so there=
=E2=80=99s value in taking the criticism constructively, despite the fact t=
hat the author chose
 to focus on the problems without any suggestions of solutions.</div>
<div style><br>
</div>
<blockquote style=3D"margin:0 0 0 40px;border:none;padding:0px">
<div style>&quot;while the pace at which standards are written hasn=E2=80=
=99t changed in many years, the pace at which the real world adopts softwar=
e has become orders of magnitude faster.&quot;</div>
<div style>=E2=80=A6</div>
<div>&quot;<span style><font color=3D"#2a2e33"><span style=3D"line-height:2=
2px">Running code and rough consensus, the motto of the IETF, used to be re=
alizable at some point.=C2=A0=E2=80=A6=C2=A0In the name of consensus, we de=
bate frivolous details
 forever. In the name of patents, we never finish.</span></font></span><fon=
t color=3D"#2a2e33"><span style=3D"line-height:22px">=E2=80=9D</span></font=
></div>
<div><font color=3D"#2a2e33"><span style=3D"line-height:22px">=E2=80=A6</sp=
an></font></div>
<div style>
<div>&quot;Unless these standards organizations make radical shifts towards=
 practicality, their relevance will soon be questionable.=E2=80=9D</div>
</div>
<div style><br>
</div>
</blockquote>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
I don=E2=80=99t have too many big ideas how to fix these problems, but I=E2=
=80=99ll at least take a crack at it in order to spur discussion. My paraph=
rase of the problem and some discussion follows.</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
- We=E2=80=99ve lost sight of consensus and are too often derailed by a voc=
al minority of those willing to endlessly debate a point.</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
Part of the solution to that is reiterating what consensus is and is not, s=
uch as draft-resnick-on-consensus so that we don=E2=80=99t confuse a need f=
or consensus with a need for unanimity. Part of the solution is IETF leader=
ship helping to identify when we have rough
 consensus encumbered by a debate that will never resolve itself, without q=
uieting actual disagreement that needs continued discussion in order to fin=
d a compromise. I don=E2=80=99t have good suggestions on how to make that s=
econd half better.</div>

<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
- We don=E2=80=99t have nearly enough focus on running code as the thing th=
at helps to ensure that we=E2=80=99re using our limited cycles on getting t=
he right things out expediently, and either getting the design right the fi=
rst time, or failing quickly and iterating to improve</div>

<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
The solution here may be that we need to be much more aggressive at expecti=
ng any standards track documents to have running code much earlier in the p=
rocess. The other part of that is to renew our focus on actual interop stan=
dards work, probably by charter
 or in-group feedback, shift focus away from BCP and info documents. Perhap=
s when considering whether to proceed with a given document, we need test a=
s to whether it=E2=80=99s actively helpful/needed and ensure that we know w=
hat audience would be looking at it, rather
 than simply ensuring that it is =E2=80=9Cnot harmful=E2=80=9D and mostly w=
ithin the WG=E2=80=99s chartered focus.</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt">Tha=
nks,<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt"><u>=
</u>=C2=A0<u></u><span style=3D"font-size:11pt">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt">Wes=
 George<u></u><u></u></p>
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt"><sp=
an style=3D"color:rgb(127,127,127);font-size:11pt"><br>
</span></p>
<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt"><sp=
an style=3D"color:rgb(127,127,127);font-size:11pt">Anything below this line=
 has been added by my company=E2=80=99s mail server, I have no control over=
 it.</span></p>

<p class=3D"MsoNormal" style=3D"margin:0in 0in 0.0001pt;font-size:11pt"><sp=
an style=3D"color:rgb(127,127,127)">-----------</span></p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1">This E-mail and any of its a=
ttachments may contain Time Warner Cable proprietary information, which is =
privileged, confidential, or subject to copyright belonging to Time Warner =
Cable. This E-mail is intended solely
 for the use of the individual or entity to which it is addressed. If you a=
re not the intended recipient of this E-mail, you are hereby notified that =
any dissemination, distribution, copying, or action taken in relation to th=
e contents of and attachments to
 this E-mail is strictly prohibited and may be unlawful. If you have receiv=
ed this E-mail in error, please notify the sender immediately and permanent=
ly delete the original and any copy of this E-mail and any printout.<br>

</font>
</div>

</blockquote></div>

--20cf300510446cd0a004f70303e2--


From nobody Mon Apr 14 09:20:07 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5992B1A0667 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:20:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.528
X-Spam-Level: 
X-Spam-Status: No, score=0.528 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 dPIPndD5JAee for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:20:03 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 97B5E1A065F for <ietf@ietf.org>; Mon, 14 Apr 2014 09:19:36 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 58AA01B805A for <ietf@ietf.org>; Mon, 14 Apr 2014 09:19:34 -0700 (PDT)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 3A5C819005C; Mon, 14 Apr 2014 09:19:34 -0700 (PDT)
Received: from [192.168.146.119] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 14 Apr 2014 09:19:33 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <534C067D.8080506@meetinghouse.net>
Date: Mon, 14 Apr 2014 11:19:32 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <874A841F-3356-4992-9F25-D8F629EA1A89@nominum.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com> <534C067D.8080506@meetinghouse.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/X525tswE-iUxXnyJ6SEiyqpLXrk
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:20:05 -0000

The IETF, when it is functioning well, does a good job of documenting, =
debugging and refining work that is brought to us.   When we innovate, =
it's usually some team of individuals who has the innovative idea, and =
then they decide they want to do it in the context of the IETF.   =
There's nothing wrong with doing this, but there is a cost to doing it.  =
 We can certainly work to minimize the cost that we impose, but I don't =
think we ought to change the basic mechanism whereby we do standards in =
order to optimize this use case: in doing so we would be letting go of =
what we do well.

An open source project that gets a prototype working well may or may not =
actually have something.   To the extent that they have made an =
incremental change to an existing standard, or layered what they have =
done on top of existing standards, there may well be little left to do.  =
 Then the IETF process may feel like a straitjacket.

On the other hand, consider a project like Diaspora (in the abstract, =
please=97I am not suggesting the IETF take it on).   Diaspora was =
invented by people who didn't entirely know what they were doing, and =
exists essentially as an implementation, not as a standard.   When I've =
looked at hacking on it, I've thrown my hands up in disgust because =
there's no documentation at the level that would allow me to do an =
independent implementation.   I think the security is also half-baked, =
and could have benefited from some IETF process.

Projects _like_ this can definitely benefit from IETF process.   Up to a =
point, you are innovating and learning, and probably the most =
heavyweight IETF-like process you can afford is to publish work in =
progress through the ISE, or as individual submissions.   But at some =
point you have something that you think is a result, and then it's time =
to write an interoperable implementation and get some peer review to =
shake out issues.   This is when the IETF can help, and when the IETF =
should help.

So I don't mean to say there's no problem here to solve, but I think the =
basic idea that because open source is innovating without us, we need to =
fundamentally change what we do, is mistaken.

To put it more positively, I think that IETF is an enabling technology =
for open source, and that there is a strong positive feedback loop =
between a successful open source project and a successful, related IETF =
process.   And this is true even in cases where some participants are =
doing closed-source projects.

So I think the things Wes outlined as weaknesses in the IETF are quite =
correct, and we should work on them, but let's not throw the baby out =
with the bathwater.=


From nobody Mon Apr 14 09:34:53 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 485A21A065B for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:34:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.527
X-Spam-Level: 
X-Spam-Status: No, score=0.527 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 r39lopNJkO3V for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:34:44 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id ED74D1A01CB for <ietf@ietf.org>; Mon, 14 Apr 2014 09:34:43 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id DE5A220032 for <ietf@ietf.org>; Mon, 14 Apr 2014 12:34:54 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id CCB6D63ABA; Mon, 14 Apr 2014 12:34:40 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id B90EA63AA2 for <ietf@ietf.org>; Mon, 14 Apr 2014 12:34:40 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "ietf\@ietf.org" <ietf@ietf.org>
Subject: Re: "why I quit writing internet standards"
In-Reply-To: <CF71721A.180A9%wesley.george@twcable.com>
References: <CF71721A.180A9%wesley.george@twcable.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Mon, 14 Apr 2014 12:34:40 -0400
Message-ID: <19983.1397493280@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vZRPsvPSTHJD-6JUwM74Ps8Cgyo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:34:49 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


George, Wes <wesley.george@twcable.com> wrote:
    > - We don=E2=80=99t have nearly enough focus on running code as the th=
ing that helps to
    > ensure that we=E2=80=99re using our limited cycles on getting the rig=
ht things out
    > expediently, and either getting the design right the first time, or f=
ailing
    > quickly and iterating to improve

    > The solution here may be that we need to be much more aggressive at e=
xpecting
    > any standards track documents to have running code much earlier in the
    > process.

For instance, had DMARC proponents and/or Yahoo, spent some time making sure
that there was some running code for mailing list use, life would be better.

I'm not entirely clear how it was that we produced/funded (more) running co=
de in the
1990s.  Maybe this is a false idea; it could be that there was less code th=
en
than there is now.   I will posit several factors:
  1) there was less working occuring, and perhaps over a longer time period
     (where time is subject to perception as well as reality), such that
     code became mature sooner in the specification process, and/or there
     were simply more volunteers willing to produce it.

  2) many companies were much smaller, and it was easier to get line manage=
rs
     to see why they wanted to be directly involved, even lead, efforts.

  3) it wasn't so much the dotcom boom which made money available via VCs,
     but rather that the (ultimately unstainable) revenue doubling, quarter
     over quarter which made resources available for prototypes.

  4) there were some clear institutions (MIT, CMU, Berkeley, LLBL, UW) where
     some good reference implementations were developed by students, facult=
y,
     staff.  And don't forget WIDE and USAGI!!!

When I founded Xelerance, it was with the idea that multiple large
organizations were shipping IPsec code on Linux, and would rather pay a
company a maintenance fee than attempt to manage the process internally.
We got some work funded, but we never got enough funding to get ahead of
the standardization process and write code will an ID was still young.
Overall, that effort failed.

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU0wOIIqHRg3pndX9AQIEfAQAsWcCFn258uO8fLf6LZEngGkriiJ6D2s9
5O2SayqxK0IVWbvQ1v7K3Fer8G8h4Ty9b0r8nNTdXDo4nBkSqjtdSCBffjjoKf2e
oraovoXNpRirPdfrAujs6GQOjdcIfcj9Z2PRWktsuKg2oLX5r5G0Dw1nMXSy51q/
m3Z6j4Jv1Q4=
=fdsc
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Apr 14 09:42:09 2014
Return-Path: <kathleen.moriarty.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24C511A0522 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.711
X-Spam-Level: 
X-Spam-Status: No, score=0.711 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_FREEMAIL_DOC_PDF=0.01] autolearn=ham
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 TD4uuzibqP_g for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:42:04 -0700 (PDT)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 94A881A064B for <ietf@ietf.org>; Mon, 14 Apr 2014 09:41:42 -0700 (PDT)
Received: by mail-la0-f53.google.com with SMTP id b8so5813731lan.26 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:41:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=Y127EwwBZ4F6NrwHvNYatfLm5thYRFhfKazhEvpiOGg=; b=E0nbUUE9e9Rq6yT6k6UksHMoLIzfO9InLyrFWBScvZ7RnLRmYeqHGKLGsxyuiQM0x0 5ncjrHOjYQvkfqIwUM9hqGHSr+f0g8o6ad2ckuJGy6qG6Db/BCGxuuHHS2EOOVtoP1S+ /iLOYgkXTcuMlPNCIKVII/y4vcwgQ6bZx8KX3fIRnDLVSONXyJv41mBx6yXEbIpa+Q1c Ka/SGAtOmDXa3p54LgCbUa36tmtXiYt4u/Cs7r4JZfC2v8/E0rTsgyydPBGQDWMuLoNN lJsvfvoTFHqBSlMb05MoeivgwgSj/D56XiCS4FQtYCloS/IsnimN8PjEdfeZ0jbPZMhZ IDvw==
MIME-Version: 1.0
X-Received: by 10.112.131.65 with SMTP id ok1mr1971517lbb.51.1397493699429; Mon, 14 Apr 2014 09:41:39 -0700 (PDT)
Received: by 10.112.26.142 with HTTP; Mon, 14 Apr 2014 09:41:39 -0700 (PDT)
Date: Mon, 14 Apr 2014 12:41:39 -0400
Message-ID: <CAHbuEH75s1c44x7-1hdVfxkKKwGHdtxR5ijVRH4mcvGP28M3Tw@mail.gmail.com>
Subject: Connecting code (open source and proprietary) with IETF standards
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
To: IETF <ietf@ietf.org>
Content-Type: multipart/mixed; boundary=047d7b3439e487e20e04f7035b34
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/B2dLBvYw3DRuwbYk6ixqE4B1YbI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:42:06 -0000

--047d7b3439e487e20e04f7035b34
Content-Type: multipart/alternative; boundary=047d7b3439e487e20904f7035b32

--047d7b3439e487e20904f7035b32
Content-Type: text/plain; charset=UTF-8

Hello,

Out of my work with the diversity effort and some observations from working
with ISOC at the Grace Hopper Celebration, I thought it would be a good
idea to more clearly demonstrate the connections between standards and
running code.  With the theme on the list at the moment, it seems like a
good time to put this idea out to a broad set of reviewers (IETF list)
before moving forward.  The diversity list members and some others have
contributed to the list of requested features for such a tool that would
enable a social aspect to connecting working groups, drafts, and code (open
source and proprietary).

The motivation was to create better connections with the open source
community and to better show those relationships as well as to expose the
IETF to researchers and students.  There are numerous connection points and
benefits listed int eh attached proposal.  I look forward to your comments.


-- 

Best regards,
Kathleen

--047d7b3439e487e20904f7035b32
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>Out of my work with the diversit=
y effort and some observations from working with ISOC at the Grace Hopper C=
elebration, I thought it would be a good idea to more clearly demonstrate t=
he connections between standards and running code. =C2=A0With the theme on =
the list at the moment, it seems like a good time to put this idea out to a=
 broad set of reviewers (IETF list) before moving forward. =C2=A0The divers=
ity list members and some others have contributed to the list of requested =
features for such a tool that would enable a social aspect to connecting wo=
rking groups, drafts, and code (open source and proprietary). =C2=A0</div>
<div><br></div><div>The motivation was to create better connections with th=
e open source community and to better show those relationships as well as t=
o expose the IETF to researchers and students. =C2=A0There are numerous con=
nection points and benefits listed int eh attached proposal. =C2=A0I look f=
orward to your comments. =C2=A0<br clear=3D"all">
<div><br></div>-- <br><div dir=3D"ltr"><br><div>Best regards,</div><div>Kat=
hleen</div></div>
</div></div>

--047d7b3439e487e20904f7035b32--
--047d7b3439e487e20e04f7035b34
Content-Type: application/pdf; 
	name="CodeMatchandimplementationtracking (2).pdf"
Content-Disposition: attachment; 
	filename="CodeMatchandimplementationtracking (2).pdf"
Content-Transfer-Encoding: base64
X-Attachment-Id: f_htzznu4a0

JVBERi0xLjQKJeHp69MKMjAgMCBvYmoKPDwvVHlwZSAvQ2F0YWxvZwovUGFnZXMgMSAwIFIKPj4K
ZW5kb2JqCjIxIDAgb2JqCjw8L1R5cGUgL1BhZ2UKL1BhcmVudCAxIDAgUgovUmVzb3VyY2VzIDw8
L1Byb2NTZXRzIFsvUERGIC9UZXh0IC9JbWFnZUIgL0ltYWdlQyAvSW1hZ2VJXQovRXh0R1N0YXRl
IDw8L0cwIDIyIDAgUgo+PgovRm9udCA8PC9GMCAyMyAwIFIKL0YxIDI0IDAgUgo+Pgo+PgovTWVk
aWFCb3ggWzAgMCA2MTIgNzkyXQovQ29udGVudHMgMjUgMCBSCj4+CmVuZG9iagoyNSAwIG9iago8
PC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCi9MZW5ndGggMjAwNjUKPj4gc3RyZWFtCnicnX3tymU7bub/
cxV1A7PjD8kfEAaSTHd+z3BgLiBMAoEEJrl/iB6v/da2rGWt7VB0012l7WXLsixZ0qP4K8if/xHl
v2pPv/7p3/74/3/gb0pM4y/+4//98X9//Tv+8lV50P7+H0Ibf+HP//nHX9f/+I9/+eNv/jH8+pf/
HEO0WH7FwAVj/PPvv+HUgv6bmaaX8Ve9/NC86NfPf+Qz8/+Vj/39n3/8zV/DL/nBn//8R/xZiYwR
U/r157/98bchpPI/f/35r59/lI+9autxIuG0kER6NcptIqG6kCR6xZwUSVtIcn4JxfyhHBYS4lfi
eQxaCDi/as00T3adSQmvGGuaR1mXXNoryxJmkr8fJH/5c2xCGKwdf36Yim8bphZ6/zz+3crU/mop
tImE4s8X7seTuQgHa51/8g8rB2Wb1Zh/WQnKq7Q8z+y9sInF9CrE3lc4vXqr2RtEeNypqbn+dSWp
r9zphAG1v6owbvoJr/LRSGS13KxvP2qvr+oyLYX86hyrneqHJMZXKm3+bv5fK0l7cU/zh/LCkpRE
ukNRvCd/9ik32fHUnb1IVF5ENG8Xr9NnYZua2pux++8WOfEhV2cvUhERr3qHH/YitSR6RJ+KlUet
v1Ir0ftwp1cusTkLziFByBWnl1FyFBEufHNCJ5Imc0lKMJZznpMcONbMXz+U40sfpr+uBO0VK88k
rfqMzLLniSM7Up3lFAsHorc+lgMHRbmfWpHvRD37dZCaX5wpOUcjt/Bq3MibbauvUJJzeHLPr1L1
fi2XA4UoBzl5SybRyyK4zkwo8otq8lQbJfmOkr+n/aLUX71TdJhEWfRl1ExahI3kdiytdyvV+w/L
FocYPPkkOeqhcfcYW5OcuHQjBvsPN2xXT47ioh7lkAalzP9hJRG+Lepv2VEO9ZV6bw7f5KDIXOLM
2rbMhVOQcxy7s+ucRER79VbEmV+B1TWxaibRFS85LdmRQKb+YlIbsh4G5vKK3G+urO2GsNzHVNXV
aUatIgk9eBc/iwaXNSlu94VE1DPnlBySInsWojpjK5+K7FnqxTsOIpCvUtRUeKWor5aZHOkvWYyd
GNV9s45CYnUVxeyn816omi1cdrmwmN1cPGaXIsZurDf39kTSXrXnE5OitCiqtrt8a8L8rNX+3z2Y
Wcp+CvnJ1OMT6p4PqFM+oi7hhFptxhN1Vgr/iZrSCU9ISfUjdTtZpZbKJ+pCJzMp9UROSj8ZGx5Z
27ossPILLoEPyeo9iUkYYZ5/KFb/I8IcZzXIoriiGPktQP2t39nLt1z9crT79BPj+JDo3RbZLnA/
qiiYAMu07Y653CBi3QW1mtWPlVtDdP5EsV4aUS6N2GGX7fkq9l/u3eWa2H81lnm2q4EkH5H1BMWC
1XkQA1C2p9kP7U90zNiuOv9kMUISHHNiZ2pJzDu5IW72fNJKsEGSt8dJ7hnxVNnZsSTOe4/F2Q7x
Cl6cevMGEcGQ6yx7S4ZNmNV5MmuuUWzC3LwFVfFMc3cXJKJRQunOwU1NHOvSbqR0r3jhCOSumJ1X
307cFi7JmVuOIpMpF2eFYubI9dsVKxfbGe5fqFy9D4lsJMrpZIXUXqLMqjc3FvOo69O9zq0In4YJ
9fV5yXLcU8vzh8MiPLn2l55aWF4C4e3VSvP+xOUVT4RPjDuljEN/uOQC3o/YE33CaW85H3CaxIZM
rOa6njnKMmpp1RFioiiWaIgzyWIUy40uDqDWbyuJuOO1z4OsZjNVUZJVMd94keKZERXvYiDZnxLd
s009wRf1zjbJFjbWZ9s4b3J5VPWht07fGydw5qJigvH3xDHoPXj7wfnnqWBd4f7DsoVhGICfnywr
ZjmV4v55Fx2L8hUXK598WJRxr54yY1G0LMvxviu73qNa8Po+z7LrvRFZkv3UZIsDF2V3rX5OSC8x
srMztyIHl2tVc1t0ShFd3GP3rLeCCERyvyObTvpaWC2IIqZYa+yOghhFSJ4AFlG9XLOnnQuLAifX
JhLtB+2s5rKOMrSx4v+ja9pwb6dZjNervciNu6izh0MZ1eX16M9xOKBOoZ9Q93pAnZW0P1KXk5lo
U/XZ+zvhIMd4Qp1PeMLlaOx+Mu/h/X1P3U84KNZqCjsNGQNuNDH3PiTGBYmiZsVam0nWCGbscNTI
kjhRvSYXcp3nZhwbMf8oxD6P+nTeSK5WqvNyjMcojkAXx2Qe9cljRNCnics4/WR1GUu/3v8mktVl
rPVFeISZVrz6jA3uRVWsXn3GHsQmljvc2bAuvim7rJV/kRXp6a4OUxR9mPRcnnxGPDwSOcxPsutV
5jcPutje4liIkVKOvktdLES1Pet6WVgS1aAmFii3SsV7ucO1muUmvZHyiaKK0188SUnt7R86XGpv
/3Ai4Sf13l7+5HMosp8pOxKa5aSXrqb2FEfJOMaRksP7nN+xsj3v5bp5cYje7OXUtsTJmz3yG3rx
GJtlj1NN7GyP3GWXLeSMIsaFWNvlYHtGGK9qNi2Wd8YzTlajUnq6SWUitVSHbySnuIuHOM81rSSy
YlbSZkZJ4l/Bud3zjXJAskByDgchCpQyeR+i9MpU1YrWOCQH0W7Nu47gMZYc6ECFwIPsVL2DSzW+
Ivz3iWT1Q8WZGP7GRGIid3iCqexNH85DUIfZ+odIGSreXOAPtnCnv5U/uOiz1WOEZ9C1qIeVRHys
qrTvuquI7YlLzN4o4iH2qsVndSLFeRDfuzpnSEy0VwxKkZgV4XzXqEZ58qybiHZ0vyuOQauNDs4u
i8ImOG6fn6zvReIcXmkWE8kiKgXHO4Z5f9YHo5LC9e4+jfLwYITYX5Pr0hHjIk5/XK6K1e8kJDpp
SV8DeeL0Z26esi2i1SlT8UZB1pqycle7quD1ZzlR6yAtGQFcmQ0lLkrMMZrk9nxRa/OH2lOAUF3J
jy6iukMeqUs4oE7K1H6kVobes/t5Qp2PeJLbCU8onPCEysnY2uh+dhFPVlnSye4UZWN/4yKmnQKJ
8BUQXPmQmOzTKKoZlteH4jGpU9Rwoz79xDhDcrHImVXfvcnZDAX6Pu20UBRzIRWYLt/PTWwB0fnu
h2EC4ih+KB70fZQrIrQ8/cI4pqI7Irfq8HnE8cQUnklW9yLwqwSYuGlRUo7bFkWv1XkvbKhPPKzu
MhqBPB43wpZriRBb4uR9CHb+uDT2o3BH1ly3K5x8uYI85vlDd75cSbiyP6M8PFnALashVI/74p23
0tIB94dfFvO84rCkZcMvq3rXV+cB8bZhyn1IbtItQ043B2EikYuUtDIwwTOxvluMDmez+No9sCfq
uSCTOjqHH24Yd/IOQxZfu1U1lcf00NbfVv5+9r2KixiVAD5FwuA2U/b2h2R/ikjLzJM1QiUOlFgO
yWEbHKhecndOIRyoWPT5WT9EQ/WSwwTiIjajUr0mtlfE0kla4h4SrAgx7a4V3OodyQbJhL0FdsSE
yVPOcI5SKGqUNTAUZSpRn9M12zAKD1JsDpsYkRU9lQfLmlFkkMq8Pat/K/rx1fCivheV4eYkfUGt
zhJeOpo6YiasJUcsl0BW4BxPKMn94/K+h7fR//XxKaIAq17v6gOIlyMCW53vliiXAhKljWw5Xk6R
3dM3wDqqbFcMXR24h3u+MBLfw81PJn8FvlP0drgML5WLxxSYIByzNwrKCtTNYnw0nLesbaxHyy3M
V9VjSKudUCsj5NlfSSfU9WQmCJd9T53VQXv2QMoJdT1ZJeeTeXOlE+p+sjsIpR5Q09HY/YSDIKbd
bYj0xxyhfmhRWJN3E1+lNZ5JjAMkhkWhNpGYaBbyZVBO6HwIuXAlzNM1TpHc76ni8t6vCGnyHYrh
Q7K8DUaxv0KNzRsFt0PDZb2frhhgFRkMHxJblzY0kOLuUwiv49UruqN2sVNZ79lThZVc+KOKZD9q
ijwK8/a7POJbNdww30m6pqtmcPqJSW8UCQy1OLKTxOouWe2XmT3S5kNlbxQx2UKO1RulNLnwqlrh
6udVpGNF7ztNzkvm7IgxchcTqQ1cXh1Sl9s5wlfcimiWo0s5RTvZvaKOGVNTUr3czihui7U0K1yT
t1XwEp1OPizGRiZ3B+WfXxTVDppqMKpiPrrMzywCRy7zkd3IrDXRmmUI+yOpUUygDPVtqOvcKwi5
FqEVlTQ93aRy+nMt7H0Y4W3KSnjWOIyc9pD0h1dPQ7Y5l6IkYY3DJFi73ZFAlK9VZncqUNi5ZG8U
KGzOyeEkwadO5IkPHDK5Cz0FQFWUYCJPASBPkoJWcSYOJtMt9Ub7Tm5cRbJ19lbU+R2Y/PpmYLyU
jAfZ7YdZXPFFlz4GYhJqb5v6iQlxRTxvdudkMqoUa/KU+PD9ulYsaSXpqC/ytplHNmzmE74VPB81
T6NxTa+awolGgy/YU252IhMJPEytaFZXFunMivnGzwlRrAx1az0tGP5iCtVZL9xF2VE+kJOCGHjo
7MhJGQHu3hw5Qdws5UyOnBQky/KdDE9OZn4/je/ZxrjGKDvbU0QuhBHzKI9JkhVPOOzZuaW2V/B0
mWy32Fnx5sA5j+fz2XtOjCwn1DkeUOcYTqiVUn/2Ik9WyeFkbJTwHlCXE55wPRm7hHZCneiEuhyN
rQ7zN17kHn8jvItZPiQmEIV67Io7cVvqjkxL8ad4Jln9vxTfyVSfDxnEmY5I0zyKyVbMGTAJM8Xq
24meKinNa34y3QBBEzJVj01QSiisS2tV7uR3inZoRXHyJviWqanpm0TKcJX/TiRP71o9mbmt3lFA
LkLwdll0jzgY5O0yKutEhaq5pZWkvah3dlgJX5Qr/KOVCa4vGlJwP5xRUxbZ4T5gVXjkz65M2H+Y
5epMRR2g5UEejmcmeBNbyUDV3Chw2cs1quYGDM7+ACUxTS8D93usmd7F7S/NmX6GxaHOtvEZxeJI
TOTITk5ie3NzjnYeSFGUHBZkMURpZCvtsVmIX63kfHC2EdNLlcn+ZHIZCcUR7C1QrIfWY/TYJNZD
46Qkf3X7ZQdjLooJa6VdB1aJPmIPhwO5lJc5u91kiiL55Eye0khj9SZPWQztpo+tSZNEeVi9UUT7
yROMvVq9UTm9kncnIOZ3PT9sxQ+IKKPG8XutShVXWvDuTviTcrxuDs9+1I73ML3eNT7Z65Vv4QCk
EKqv+8Fq4F7WqDSBjQmmK4K5vUU4B8A0ZZcEhUaxONvFBLdVaUObU/nzaLAfRaQi9OQpLi7hFTh7
CoVFeV+vRXu2VH5VUjfaYw0d3o5HAHY/fXEletN616Cu9AukZK8tgLrSonckRwCykSdN8ChT0KOs
6C45ml01lXgjjZ8dZo+0yhq8jS+AuNI3ifHSBsSVNwZqXkhbtCsaCmpeUOG2Fx45169eqXjrafx+
1dme5dIjyntnrjxmVdJ8rh/jjq0dUKccTqjVuXiOO5YD6nw0NoV0Qk18Ql2Pxj7iN8eTsbmd7E7p
J6vE5myL95EnWRJ84U9xqwkTRuSJzyTGNRMjI8hFO5MYHzC9Tbw9LEqqeKMl70MDfo/UXIwTGF4x
6Lk8l7C+OLbiTV8MjSuLaT83ZEiMiq79CoHAF2YemAgmAhRJf+cp9og3TeCVfH5i0VYCLH322Nbl
9i6K4glVMgDOjclZL6KTI6dpjwciHmFIiT0SFOk0zZK1gm1AtZV0wLVEP2bvFn4h8Y/Zu8eoAehO
DuzsKNI6xaihE84iSRDVtdOOri67GBGhtpm1z9V28PKLdwIBtXJlZO5RRsauQxV+jzKSxHYMXC0H
JpKGFDOHjYBV6ZSUolqDoMjU1VtqQTLFmRsR9a0sIRbZeiiORCITtAFvYiIxsClIl6LszUW8Ro5R
iddTQHYAK1FzjvpVkdejc9QJIeioV/jkq8GHyN5BHsmiXYvOGr0cybzkqT9CMu8o4vke0oU6gH2i
c0rhJV6Bk/30C/AmenfUAXAzKeZi92siAZBPVap4nctA44sHxwdBRyZ1RRusx4AE2ujJLJJHR9XO
Fo+GR7qvviRWEuhZdXpuETG16jKOF+MO72oqxsNDnNVVVfDwelPyZgBcxMNjmln9FCkCZuayfzY8
CMDF5N0bI4JIxZMCRiBZbdcTziMe4kdEfg/0IWdUuMJ28l6g4sKqmwzE1dPJ2Zyd1aVCGDmrUYxj
Rjg7SkCDKatL71DllrEoq+s9K8Y+aMwihzYFdWht7K+LyVWbc67h7on6o4NTq7X0sy8XDqi1Cflc
85ZOqCufUHc6oM7xZN65ncyE4skqiU5mQkpZPUcWT2Yyctm/p1ZGx3NksZ9QH61StFfeFtrCqxy4
yHlblxoDSolpHsVGFnHqxNScRlm9FhQzIP7lkGRRPS32mWR1urKYEF1/yEB2IgjY40QSVlQauddG
cck0ytp6g0ctjCIxzRjy9f45kaxB2YqrvJE3l4oswzhzd1WmscHWZ7VHJiApi0Zqr8O6EbQQnfEh
aWtotyM1JFdnuigRHOBykzAYNFCRlxqqw7oUy5VauRcG2Z6rE4JDgguvar6sLh0wpHtK3nSp4hVi
5r/JfRWbrUWPufAuCQ+re7lMBc/ASnQNc+GKJMWWO2zP2GvzmNsIIOXJ+xCilEUdANvtIb0YhQfT
h4yDCReN2OFLFlkYLy37uSC2OSrwJxJToIiWF1pcTM4sIMeztwHIkZVT1Lzpik28iK6tUEQitJqL
ceyQKolXvz1380iE1qOsabSVLlhNZwPwnqSl23C3lVfqTB5fOkxprs6K6AfYdb8iGtjy7N0ScE1z
7s0bBWAxonsdnUrpDUTpfAjg8qSUt8UORVJsVSK1hiPpDai1lxcgwVS8ezvTHS17snfsR9yT9FzW
6Y7EOH1jmbxZUZjs75HYzz2zd2CRWiv6bv7QJxby3+yBhS++d2F9iEUPLLSV+pBY7DeSixhq80Oy
Pnun/FbyH5K18xRiY7XXmcQU+yMLl+JMshpLxBe4zofE3NWAHGlJTddge+NRR33IGAWiHhJAEqcP
rQZKfdf7TCQr61BQToovpmlXz1cTEmcuHfXW4s/uRwHcW2JnsshJGo2/9p9BTlLUgyx7iDZOl4bZ
T0S2WdxbcpgCi6DpD5naEEZcIhZHKsdrci/dkQSkHD1wPwE3RnPfLBo1Dmgf4nAO26znYnKbxPbL
4lw705XtedWiuGvSg+QoBnZ3EdUtTR0Q82g7gBnVVGwaUn3aRTRiWndxNRqYHY7gjuakNM+6OyhS
aaUmR67xMNyBazORrAlTeJDg2uwe/+Wo510W5fW2SEwjQQBLR5pIbP4oHrBrnEkMDCdq8kObSIxn
JQcwojxoIjH+GWpa1CA3Qb8W1IJs0wW+wICnUZ4ia7KdOYd5VBv0Q+bazdScpx5hSVFTNfmyA5Ap
z7w35jhAVYjUh5fH2pGymfSCb5ohiAdRnB1E9G1UbO85O7ohpOpsYKL0Nlc+JE/plwBGJBz6dbsm
knIVc+05CcCU0aRvv4MItolV7M2+oQYmdEf+Em48vAo7U+nvjDHzIee9rFzvndOoq1eQUFmjp79m
TuYB7m6PoJOhEYE8djPViaQByy9535XtKcOp/JCsir2+oQr22wNlKFuUvQ/JiSqkV7hOt+erP+Ce
BN7IAK4zMqq8EWp6C01PAjEJ2dVVlFDnx2T5sn+ARH5srp54EVCl9Dm1AClix1RmO7f9h+W2qqRU
vPUQgEVPxdFENIpn2FFE1BFf1LtsACbbquJtcqT44kmfdgMw2a4WJc4ociGNpNr9FnKmt/+7KkUH
RKUL89U1t0Inokruss8/JAb+JMnlkWY+rchn4n6KaZDnFT5BJyJg1YLSM+sGAfkxkpYd0xsAj75d
yYqpYEtXV4z9ZYLeAHKgkzdK4gtvdX8akLU4+kM5o4ivPiC19yJXCK0nWK1o/ZBY9URh/lB7SBFF
kmLu7DLhwvtUTFhMzQIcA6recUDUKqA7sDP9Hl8c+o1edJKl5mk9g6OUA2pU139PjaKWA2qKB9SU
TsamEg6ol8P5RWrg99RFKaXnkM/JTET3UtwawiFcGF4TyQrgEdHHt/aZZH0LSYjwhjSTrO8PcNhh
ak0kN/5CRjNjZy70ftdyRsEDPSpoJhLz6CLGsVjqE4lN+YNxPE/FhLkqjOOWvEFGeWruHv9bAj6T
WvP6FtVlizi5C0KsBuWFE8lTIt1ovSxCNE1/fUsQN4PxIrGf23AzkCU3jWI8ETEAAOKxl43hZ6Af
z0TylGuHIiH0BZt+subaDdS4mhxZSRXd3ihavik/I6LHkrPChmBadlfYRjtZssLiqMlw4W/shWc8
07RWrGQ4vgmK0fVJvYmeiGdfnPOOrD4q2TuGmZCFGW6k1i38EkHPzm6Ml5peqzf9+kYc2W8YmqM1
0ifK9MJ+p0ZPCsA0w05AULqRL7/wC02W9qPCE+Gu+bYmvUWEK1Kyx2W+BxEkKydzQwL2IujrqOi6
VFiJ5NqlGl2XKM6jGH+mALeU68FZQMSjk9aSq5+B59OYq3NcEPGIKL6ZPrz2J8DzaVZa0Ticna52
W9/rWg78YvfMiQeIA0UHp4VTGYB7E6MNTgiadSqlY5wmejcVn1hiir9gcAfvFmBGwy59cE3ZVnkl
1hrjyfVCghf6WOwFkvHEQ9ocWASSO6BDSj44CSW8W0HuFWBB58qmWbv6VXJKa1N6yHpE4gyIcMwk
y3suPKIRONjvITyioBWe8avo3fj0+yM3WmOjEaozankUHnhEi/BYvPzyYqQX7892+WlQ6jABffPg
/X9Insq2kmL8c2lVPKHuJ2MjJ+KA+mgmgKA/oM4n8yalBZ9BRE7mre+35+S9k3mXI56UI36XfkIN
3yz/fhIyuXaMBlZpIjGpXhEZ5DSPclfkBWyYieImG68i2XYieXofyAMxr04/sYGb+PZsPqOusXqg
Q5favNlzvvD9DA+c8I9c0IDU//zE9stGBgWpUQ3wR3uJDlRzM4CTKDgtcSYxeXY0sBo+FE+57IgQ
DRyr/XdRwTXavu6/myK6mZf5wyYMDwABQKE6o+R4dW6bSG5KuDqy9fecBOZkRxrPRGKQ+AEYoAXh
JqmO0VR3IjEOHxJI2omsIIPuciM/P1njca3J6VArNCgraKKU1Icfm3QF9HQv3TkdOb6hM/Yfzmiq
hBD7fptzhot7J6TOk1t6LbJj4CPr1R7Jmb3YD8MP+P6zaKws/qkjSgg8lZ7JEaXc8tXazCHpCKhU
90O9IzuNHGkjGPXkcYku4HelJFdnIrZXD0mJrIk7AQ4lq9mafmjxCvo7c0HnLAT9vxdRAH0MnCln
VLTJYq3jn+A05JDKrdWc/UFoipi9Ewd4/1qVYjX7M/AaUvemL75B4ObdnuiPlpI6PndVXA2ZjPtR
GPmQoWZn0WihNvph7Bc9Kr3QqHu/IoZHQXdXg/esLae9kDd90eApaxF88k7RFi9opW+qxUSx1nQz
6uQ1ip4BOICzYlQKAU1yf3UMRzIr2TeQmkjMQafTvUrgnq9c3/0eos22KEJy5oI22wOQZT+XIpKw
XMym9gk4ok1ZhqvzD8cx9O7JNiAkU9F8WT2vbPXgOsoo3y2eVA6UyZb4QPkAM0QsyOiNikzZWDyj
oeAtMGe1rcb9rKOxu/Md3ChMN4M45vG8Nd90Tjug7vWAerx/f02NPN8DaqWKnht35wNqfYqeHdF4
QM2ZT6j5hINFWR7PzuLJzuMw828pXTNzf5prf0isJxivzqrTKKtLg8Q/ZFtOozyUuCJqFwFzPv3E
ZFMH0UU1eR8mMQvGZbB+WLmCRF2t0DQSELOglDiTPCSsoeTqioN9fnLTWEDPzNRk9ff71Gd9a4Z2
l5us4D7cjoLEaUJp9ESyeltI3RyqaMtrVFON7tMTiUkfRBC1kTcXbCqqqQwjJ5ImVnRTfDHVVPIh
1LF+SB4f5croITzPbc2UGUE7LQYGvREmzd0CnQe7/MpNL3j1CeCZU/GOD/qrjVrC/dyuvtetOsxH
g7WR2/69FCMgl6Jmyur14J4G3OaHxOL5oy2YPsprXIwBdacUxF3DNRF1RxHB08s5qamYgidE10v2
RkFkNuIO2q8ZkVlWh8ECb4w4pfqQAd6I8HK6s2YKcBMq28PgVD6395v8doU04OLv5uamHKYYvVNJ
IgiFtTY2pUxyCil0Z4OIrSp66slW0zsTYL9iYLihdNLZDWC4AZPO2Y0eLky6/RkDZGNF9vNe1NHa
rZfiqQRGS+RUqxVBN2yXPB2CBgCZ2FMQA7IRuDv7TWbcp6F6MsuobGn5ZpT95OVol9Q8uUCnt0TJ
u6IY1UrjRW0rgPDHqFW1g2tOJVIqipKDp4gimly3pi4X483IDTv6k+4FsKBeOSoVaGJagMcaj+7b
6SP2F4MyCAxuRkb5mFbqxrPKF/rG9zddgQZHQaoztxIvyP+92iwDhlNrr9UDre/+gxPJYrSiadxo
Cff99KO6Np5dq3pAjfr9A2o17+c20ydjU8wn1DmeUB/xhFM4oeajsfsJT0Yc7ntqpaW+ca3q7jTH
IFpvGBp1p9JiDBdC+kSypi5CJwz+fEjWNEqo/vEYUXfnTqbxqimpD5miKjngXU/XRNXiSyxtNYpJ
o5T7HUh1E8nKl4IWJHiN/03yFN0CesX1KrUfFf18iLrDSmDjj1KMPZ+SuMPXc2rdabkErAHU6xmS
/ZFPwMqn6AgLAmLXxbsVFgTEAmBbnBUyggu9OcKC9Ea5HKLHhIoGDiU7wgJXiZuergG6z2g8RY6w
pI6WFCk725rQSQtp5d8LCxqo8SLIdw3UMs0kJtkv4bqGSbllQs700iww8a584dXsWQDf6co2XUfZ
rw8lH6RYYh2YAHdLseAmU3GAhO4FDqAOclzUCtcC2Y4meaU4KxwBr6I+ZJMX8WygmGCDYgNToDui
Qmh92Fs6EBUAEFa0qtzzCZVWKGtzFogodCd3aohZAOPBGUWc2wAwif25RIAro+2kM9txLl1eN4C/
NHWfrMmYsu+EZu772TKgQ3tyZoLYVe/sqWxA1dNwF7/eMJGAdzxyK7VoczYaK5i5OeYHv8SmdEcV
tVnQV3ovogAgvPJutpzl4aeyd1yQm5iHtfr19BE/ut7utqyGfzIqpPbTB6BgyIq1xrNICRAA6jCY
/mJB+BQ92QGAIPpz7RVroSLf6R6zC+C3AntXBzyWxuHk6gB+YE/FO+1IKkx4fHfmhqeGqC5q4+l1
gOHkmU2PcPFqWs+Np/mAOod4Qs39gHo49V9TczxZJSvV/ew3nKyylCPqfsJviPanpNOEZAj45HEi
sVh56DYPw2lbnxkjXiSwU3uMBKQBjYqNPeDBT0do2hZfolFXD3BT96PkN17HRGJgcWBupeItmsWg
zKV5K5J7dkB6OHMpcsTVZE3L6HiBEk8kj3ie6VULdMIe9wKmLkILe9gLMaUI3Uan5a25dwFZc52d
UQADkWpRHzIODHycphZocNqhwUJ0NgzAeYW1CN4A5w2o+r2UDuC88Zr9NUwHSrhKbGrU1Q2q4f0Q
tRUm1GddD1Efbj8hqje5Q1skR7gQDorAJtgLAsJBtDDlBvCuthIdIc0RNU+1OmcB4aDRxnM/3eHj
aJEznlIeJTQnfEIeIKPLr/NhOe1FnWRTsYUUsZizS4J6JrXLxokDXiK5QporX0iH30sgwkMl0LxA
02yto84wVIcHCA/lpuT4Ljx01cutheFueOjyNPajitpvkW9Gnfyid88lwzcn8yKLLGk+mrQ/cRqS
Vl+r/4Im0sMu2uNaFEbSb3aEduBY9JY9JgDprtLBrtNvq24/NZT2DSdhjyWBLpyRo2WTYxIBl4jn
ucY1Jw4pfqxOaTBg7uFV0fxpIikrSX+n537NFFR5sbrWTPYhWqmEdnK+kL6XR7bNdvuQvkdJS9vq
ayHXM3Bxzj63drUj+V65oVcXt+gZRAW4JJ2UdjPIGIBXLdk5LPC1CKBt3x9BgLePjqLOhwlwIdTt
EXTez8PVC3S/G0X2OGTy7rQCcC1WfLO9nnFqlenyWG1W6wXq6swN+KZUb3bDye1RB+mxwotOqBUj
n1PlTmaS1Sl7jhWdzISOZkLKe3mu8DoZm6mcUKtD9uwhnoxdcjihVhrhkbqe7E7pJ/yWRfIefOKn
TTRva2MjkpHREIe/ro2Fq1kQW5t+YvzIIBYf5ZnEBLoa8nLYfnjyI99osLytHAXSh9xyaR7FBLrK
laUykayZeSPYrflkXE0kSufkzaWi29o8iMULeTdtdLasEXy+7k1FbjoizVyDFwJngNtMskZ9ABwB
dDb+vlo2hVfDXf75STCAqyjKqM2ZPtpCd+LsiE8iBEFDcZidUJki0uwwIQ3IfsUE44QP1E89yg0+
SEMsfiJZHV+5uQLClc6iG8Jwyf1QA4BLv+GL89QXrnaXeybA/+y5WOF3Qm5AsKrRWQ1qzgpqMvZb
CF9zRK08ElR9szoNBkGELoz8Pdsyv3OPD9hW6LL79tpp5B4C63u/60AQial6vG9IlGzkCODAWidP
8SAqN0D1J5IbqPURAf1ehwPJkEDujJpGbY7DehSUyfq6s76RaAgsUGcU2KRFn0HTTBqd0Yon54Sn
QC1upqQMSXUhe1MZBb96zaakTCSyhBu53vO6iwsUiqf1UT+WUWW7v6jRBUyU2c1+OAG2LOqBo8M2
ZBqKemCHb0xBbqTmsZapXThFzodwC6P+Z89aZBaOpzKHT3gDKopPJm0QDTEAd7i/+hCWG4HH/amD
N1kaecbVKAYrSp4eK5qQkaLVmY3ciSR0fdwfXJySygvVrnu7A85kacGTa1R5tZbdqSF6jhfrPdsK
rTrRONT8rrLb7yCKukJyFQJSD0Mvnq0lRveLADviLKihGYxWK0+2r1KZz92+2gm1Yu03gCEH1NwP
qFFHfEDd4wE1xxOeILn3gDqFE+p2MhM4Wnugi9+O1h7o4rejtUeKiOXtWO3BPhDmG47V18W9cSAQ
w+nYI2wQAMda8T4MexsPBw4Jo3ipz3MzoPJQ8QgROUyoP4bj96WWLb8NyT2UR4/vo/51+XIKQHtv
ydl2pA8OcPT9tsNnGrXJ328YHKRRq/z5iYl4yYY1lBBPoxo8jXC1T/RI0GWT1W4YPA26isn3rE1i
KtcYuvchpHxyTt6HRp+Z0hwpRYYhJSX7FoWjXYhV+z3LKABAQdr3GzIyDJEH8/nJCgANj+hyRz8k
a4sKtJwRuolkLWsT8/RqIT6N8gAADYwNroq1Jn5V3vCV+z28AmfBkwQxT0V/kRplnX7rV6Bsv4d5
1NipQ3VXalVZK4DH+0psvhq7/cnkzeQR3NgvkBLA2mpx2ITKqkrzZ0zVFOH1PFV7GLzCZWC7z79Y
QdiriCwzO4JPsjsR/Yz2rB8xL6qK9auf1fpV1uKM0vMFWrPfQITFRpDh+w1kAFTVUJy5MTxW0leH
iZyhcVlQ01/TFAGJwOqifoZ/z1fLuj33UUYlLsfN7TKRiBuflFJ/Bj/MVx8NZzlIEUUfjf19ysBA
CVoyHsEPcWcVz+ABPmIOSQnTCnOO1O2qjQqTgxherfON7Dvv9ADjL845BtCh8MX9Lif5bvE4C/CJ
TLE52qAgtBmyd6AAPjH6NkycTCsJHujIswsL0rv5RHRiDvMd8oj0Xg+oUzgZOynhfHZq4gm1UsXP
KIhH1EwH1Hw0Niur7DnqdbI73E/mDWixA2plQ3zjMO2xHn47THush98O07a8EG2GmfUoq+GPe3+8
9WxrLFFyNTpd8bZIEW2GU8Tl8z0mBpKahze0LaC8MhwRT/m6tns0EG7sLkcUCg3fdlsTPxpZRcVZ
k+LI70tvO3txat6X3naXUYHFepRH5yciy6tFb9SULpxXs+uOS5WvDmLOqBlZ9eFmiyevS3wUtLo5
WA5XBB+Tw2pAFrZK7Mg5XKxQFVNsDqSYbkCRm0ZZg13iJo8uqA4TxAAMcebBY0yw4yWO5wWu/egy
iobG6/0ex0HO+gBY3B/BkSUJcBtzWCYn7F0x7nxIjPzC7LEJlWCxl+yNAtyToiTQgFeMUqPKzpYh
cpVDbN6KSgDc243cOsGtdvkoe3COOjzgasVYOXvi8RZvga1eJYH785KBiZljdRYINHwK2WM2AfCm
Bo/ZJPdAHK/1W2YDR4OD1ooPlZ5wCFmrSds1+J0etr+AUHM20sMcJoggcFJya1EW66uE7CkJQjFo
UDedYWWp73jxZ0Wm6Kw8XTAIgS0XjJnu6HVB5M0F4ZOodI2JGYW4Sr9xq2J4h96/B7BAfBuNavbC
MnD1o6uSWW6UEJVKfgzH0cj9dNiGOBqh9/xEYhAT+crD39/ujC5VYho5zEd5GxAu9pLN6KUwPMs9
l5oYAPp0G3yOstpAhqSHC5LILNmLCbxiCt5tiBK5K0Vmj88hOiOw3sDlPasMQ4M8+QPEYursSTE8
1pHjPK1wxcAA6FLVp3v1JHlkzTQrb5M/ipagSW3I6raL+chNLWidSq1X4zTnOyN5+sak2Vut6rL5
BrDje+qkZOeROscTaj4aW53KZyzEckBN6YQnHE/GZgon1L0dUJdOB9RwGfeAFT9tynitNXUyFeVi
zT3OP1kdnRwutENeS3QnkjqwsD8UxpGTO/7KQtyiFCB+Jup0JrEFb/SSsfs8ioHbCBf+IX9dBou+
8Iy85unDq3fb+tva2xY7A7twvIbtISJEK492KLwtlAV0Yexq9k9eNPIJqXJxZo/OYaH7cyM8oPV5
C20D9yCXc2RLsp8bLtGQ1YfXwJdYUwN5fS9daeS04312DxYid2SPcR7FJDKi4LDoUYyPlV4layFd
PQM0hGN9xJ5iY1kuHaAu7KePqFbK7PEp0xtpxiFB7UkK7ofE8Bm9CvbcBt5G0FJq3SOxgIvmtnGP
6GrhbVTR5PskMSELeRvSgU6uzrstGgM6uasW37CD0e7Z5B6hIdedYnFKBFBZq0/MmtqX8bgTsrMh
aBZGPVa7IU40DNiYnD2moLZEL3gteasDwY0O5Bg9ikV+snM60KP4ygnbAz4AdyEoLbKeVE7xwqxz
RkntSiTfaivOQ2kkh/dI2+vDl9geKRR8DRwWZypI2yv95kg5YaufrP09ukZDTrW+l5+S3OR6aeg/
vD8JiEkB3WV/KFGqNRCh9ncUQlK9qNlb2D6+2kvsFQQS7kZ94V6aUL0lrsGNNHkoBqKeCzucRUwq
5HRzxU4WPkJ3zRNj1FmVYfzumY0ueXqBTyjLYRa0ZyeADqiTMl6+qfL6njqrC+XZUA8n1JxOqBsf
ULMyWZ97FZ/sDloTHFD3k5ngSOxxI4IcrJG9s8ewCP0FxLAPxerXR8QYghrE9sNCRgmrUdbIEt6J
hz21rRwfBUwMZbIFcED/q5YQwtqDSaAnKqWZLcaLKWjGCk2+4lxMfoAYJDDt9t8RrRx7VIOsAIYo
iq6JvFF6f1sOW+bCD8gjh35b6QnoCxp56d9jSaT+tv72kA6yZbKmm7k5uiK904j36BkDcT4rQVhr
e8RkCVTmUdaHVxQRXc9Ee7APpGAldT5snREsLhhH2/ORZA9jVNy3aXRduM/R2aA8gG1CdeaC0qNS
W3LOUEbGa9YrugnqhBjTgSRkuVqv0sL9h9F2TsvKU2diuVlrU1O1nkNCV1s11TUk8juwsgexQHnf
SJ/acxbHUCuEJ7M6iMpbRGd9+R+YYUqMjSORkAMYot2L+aFK7AIm5zCMsqHao6Nn0HeKuXtsQk1Q
q2qTn2KVA1mcFd/WDEwkyTUibwuBqBdTuJmb8x4X5Dwp5Wve29Gtj2N2ZJbHSUjqyBngcIQY8snU
5CCM9rl7bTBQHypF55DKYbsAy83UHIMDrbOLI0pA945RscTW4BCa3zlMA55epEaO4CNYcCWafI0c
URK9nautPocLEEdN1B5HgSAWzZE1dE2qkcjRBSOXrd2pMuU3pMUMeQRjwINMrg7v0RNJJIe86QMZ
L2kr6ilhAvbz9wgM6qQ+IzDEE2o170dqdYSe7f4Taq1xn5/zj6grHVAXdXM94x6c7GU54qDcDWVb
ugrUvZxCnklMrU28XkM/JKZfTxT9A3BLZ5SETjuiksu2VA0BBtzmZa3nmyhQhiH+7kRyg6jXWlPf
WU1zJKwCO8KZbcEDlmKcwctDULTOJE/5JiN4gDunbEvxBhoBnpX3HwYagdgn0W6qoymg2TvZuU4k
QO5ijyej2IZmMbBgBEEcmpq97yDrvyhxW+1yVOPk4LKAxVxGc8GJ5LGzGywCNXsTHWmwsAN5c+to
plS7I8SpA2ErREviYBPUV6fkSTWs/9RISfX6Xg/kpNayc3yANEAIoOxPMvK1xDz0NghAd8Ph32uV
Ae/dy400eUFeZHg68od2tlH8rXn2Nz5DbmEmuUvG6p2K96HOV1bIfpdHx1vUAO9JKOSrm9L+Q2h5
O2r89qJO0KzAj/hezZCYU6OObr8/hCpG0mdsDZbgQSY057QjFyuyVmd3AODomTnN3gCAw5r3P4QO
t4s0GZIOvEbv7CIXS3z57pyP0eG26svwqXPrSJ+J3Tm7qNipTStO46+gdpCLM31EOnrM0ZEVQIAv
SsKmTSW8J5Fl5X6F4tM0uenmn6yBmvLu9eassHQ8pavpP0VHUKuKKnKHKXKYCwDZHaYgs1LLl63Q
QZZUYeekXllSmez0J4PvwifZ61YkSaXg7vIAKKieFrwACrQWXBOTiC8Uje83GTU8lZXKsz2M6lWH
sJcD1PCUWDwBLFUu2a7vOhNSQWSw5wNRiS1M1M8hkHxCXcoJtdqZbxyn76m1ifDsCp3wBOCIB9T1
hCd45zug7ifzhnOzrWRFCIRiijPJmrEUuogspHpbsgisgQ6ntaxFZZNzA8gzXBz7ev78zixwPiTm
8yijn0a5afw6yuinuRgQt3C9BZVtOR6qaUJNapTVvRFzbKSFfkie3gyxFb9DV3EdLyB4AzW8T5wC
dDv63pZtKBVZaqnQ/CHjREKDinc3kzzCPgDLKKu5GUwH5Pj2OJMYpqJPEWyqD8nqeBb0KYonUwPS
J9fuTQ2dM1BbWbahbjieo/ls2YbhkbU2miSWbRh+wLC3dMPZWbO+ErClJpLVd0vIVIeltp1uSkgF
q9Eu2kl+Q75cIof58CtHB9EPiQnmAIa5qw8/oqMjTRhpm/sNGph34WbXJ88Taej1RGZTh7NKzWEj
INcrarz3Rw7FRF1UjnPk8sDshSL4ejMQh+Ku1IEp6MnvwrSDUVETUNQRfI/qXK/IkMrkyD3a7/Z6
J2sTSb/aFO83EIlwNXfFpNWxBqwhOuc6cxk9OskqN+cpVU5tLkplrlhuV6oPO5uBpLcckpJhE/GS
qY13m32uWQJU4DyVtrpXqBIqib1BsuxYbt4dgOZVlz+yPepAXE+AR/v+PAEUr6jdMc4hTnohtlxy
slAQ7m6ecBHAXKISUVv+8/OosVXN1PuFcv79gtGMd1Tl7KWa5UJGFc60XSvSHk56Y+9KGPl36JOy
F64BwB6U4JuYH14jxpvGlk0IzzXkAu6ZDVd2vL/uZzv6XfV5QY+9udBgPRXPNGCAJSKjZC/4cHZH
ZsReWTNeJ7JSq2b6eJZaVIgJ4fGVVPm95kULX+y9c+IKWj02bo6WQX/eFsPJ5SrutKj8Nm+piR0O
UJ/uiTGKfZpm2xr1Q+fHUj3Ojihf06d/9X4bwpjMjowWnPZ+o0Ud23Rm+zM8RT6gTvmIupQT6p4O
qHOKJ9S5n1Dz0dj9hN/EJzMhpZye/fcj6nJCXeLJ7hQ6kZNytPM4l313olDHNPylbUKCXBviKpAa
xDQbJrkbixrlATkHvnpseBDcp/fJhVTA8/13xR8UtUje7FmuLOj8r2P+sb47LZU1P2Fy9t6dlso2
ESKik0/Ws1+n1tFqDQaRm74YAQH8IbFlTDzqD8qaGuGlJ8t39dTWQROczPmzJocwR/SXVoOYPl7i
+cTmUVB7v+lstzgxCkqix8dUkBTJ+YQFssfIY9ifizSKNpL3WWDjj4DCfvIdr9H14Fig5ukyY/Z5
fZHfZsw+ry/R24zZ5/Whs/cwY/Z5fWJNDPw/wwPHgaxiqKnpm1HFcQD830RxAzORkIy1l09EMke5
vsMm9DIGgJ4zlYqmd3xzdpRLGXJozkmAS5lRnu+M0gkdBKI3l44cw+pJE2qrWK3ZRjJJeBs8zo2k
SeDvfkgeExUR0h5PvPtEReCghXyjq517XVRMcZmP0GYmxXyT/ogkklg9TQynso6Q3dcpuyRmZvL0
MgEnABnUzl50BBObEnRTwgUEnzav79ETAjRhpO6ICQKdo0/jXmThMF4Oyj6XMePZgz29CwSJNoy5
LZ/kcF1wI9P9ZfI54daEmU/GMy14GaYbjed4jO2CcHRWKJssZs3N5eNUm6ORSfUuvYJGJuxwrYyq
1uwd9BIhOmoQE+b8SXzYp3Pmn8SHrS5Au+QUW/ZI0DGh+LOVPR4vTvslo11yajdqySku6yLE6u6x
kOoFMNHROYMIc3b8szmDTpH+TP0NOMT31Mi/PaAu7YA6qxP0jFWYDqhHUPR7ajrhCdUTao7hhLrm
E+p+sjulnPAENWffU4vhVrfR/d9YhXUb3Y9IIe9pHsUGXMWIRN/vicSAuyexFMI8igknoiV7kGuw
brMtUJdWUZFft+kjEZC2pL7zdOyY0J81egssYmY2ucTrmqAxkQib5Kb0SCpdStRZIBBTKZA3CiBq
mtoys6tiUFCJ5K2oo+SHi8NJgMQPd3H/IYDEp6xX9FjKFq/Kqbomi0wk9Ur73wtlEm8i9lYdPgFH
vmhRMQ7jCKapXTUOY726MjpsKuWqh3amAhj5ooVyTVRF/Q5e1aYtMy4iX7WS0yimig5YnnTDOUfV
B+BYKk6ukbDAV/bBnk855quzptlV5wkRZrFm7erp4FlAn0zrebZR+unMHg1/o8d7+Jliv7GzyYCi
H86dM4o4mqLlvBMF/ELqFA+UU4ZCCMWTLrR5Ho3g9+c0QyEkfZRNDm27Wh3stwOFdgGQp/vtoIFC
oHdsdWUSeir0G/3l+oyj8G5/lmn0BK7VUStIkM0UveMON3IEVieSspIgIqD1ismQBVa7+pDJs0UA
Iyl5sp2fRa8Auvd73YoKvwHJM4269gpAw66ib7I1Lge0o9SbM7cBFxJYnRjT04uMEl8/FPtVsmyE
ZW9W4fUgKSm1viZf7VCcuYlKWC/iG19ztGpxps/vBt/f6zzAF1LRh2zZIB6dNm8GVd5oqKU6cgxw
wpDVMTReO16Rkt4f432ijFGrq8fIY3qJEiFHAuFt1sSeQi4wAHpWH16BStDcrXC2JPu5iYoIuXqG
rNzRcjrizZmb3M90QZF6JAN7hrwVFlxK/cZwUk7rqLj+Xk8OgEMKnoEJ+BOx6G8saMc+nhf77Ja2
E2p1DzzDlfQTarXVz27pybyp5QNqTier5HLCb61NnkHxT3hSlGH1TR7w99RwS50k33Q1eKr73NvQ
L2Dhuk+sFaN04G1NJMYtFaONQvFGSXQVQtR97m0GdAhE+euuMIBVHMh+zgqBsh/nqRkMlpIvRCRn
kBquyIzDbDx94f12IjHwKXmgdjksQHAKID7OIB3ZZEzOdsDlDEDeMCRu/HE8XtZt9nSSHaRY1dwe
GgUnJEGxWs4dqP7l8uwbpOE6AbDXXrqQ5Epaip8WLH7GaN87/cSgtnREQ7wThvLKEXR22IYn7Rxu
pHpS3wA7S837UEcDaSWAJrcUJc1VH8KnyOZo1x2jN2pqqHrMjtCOLs0IvEwkTxD0JP5mqd6u54Fp
pJSXRXMUV17JBT9dZshMTDE5Agk/sHa9mocQBGAaK0CT97KEdNQYgqeKKSJkTp4UUGxXbsV++uhi
Nvok7A8LAFhaVSrRotajUaNWMjf5qGJXNW/RcnAHUrSzaKb3s89+RShb755KpJ/I84fkGegFnYTV
dRTWbFpAEOZKjgBSE2+/t5st238Y3TBC8tQ3o+PBos1WzwSyErTeWaaPkGNr2j54yo0Vn0/uDk/R
8miuRVYbOHWU4arx3AsBwo0BEJJ7gYTLV5pryjBaoATNthtUSVFo3h09SiuJHcai99nId9xzCQHH
pITauEgAl4hKAT6FmYX8yurfHxVUWlatula8FXS3I32wTZCyvd82nAZqBBukH8gW0OlbS56hCYdP
lnRjaDoRHzwFsndJICQJ3CFjtUzOXBiN4R2+4iEA/+xwDW0ru759nzxCCrP6efQI0wl16ifUij/P
/uMRtTpMz97m0didDqipnvCb+sm80br2gFrd8s9ZqyczGW8d31OXk7FrOBkbd8/af2N/GBAfBVhT
3bamGM2vgQlRt40n0Mutj5Dd2uxl8jLFVQh499v2PkF8lKuey+rtETI5cNl83dxlFEp2Uh9eE3/5
neAzkazptailRLWomZuTPFuu7nUHuwHInsQeAwAWgvyR/Wag/ZtcpexsRgqi8nu4YaP2TJHfY2Y/
KTuxecer1r4/WgLkq5qLSdodbgxu7a87+KUfaNbpJzcdtEdMfz81NOMZ5vh20xH5RAHPNHkT1UTy
W1a8NlFNukq+HV4DjS0nNZUnFzIAJhOPzPtuYhHORGt2gY5jWuXSDslZMTJhSwk3Auhmwo6Oa3uB
ROkkjctzuxkoncyNssNqpMIOeNGJKWs8tdIrjDdht8Ua0Db3GhFprqLv56k8WZEonaypeTxAx7VY
88l+jfbambMjBUhyTSMyuu0Gh0JJGlGbfU8wwICM6/Prbl6jvRoKkfcKBIWTo2/8/hzDC61IgHZI
xBgdSDv7s04V7q5WrManTFeWnTNdFMwiy26vzKgX4Xa84bZTeNMuIC1z+CefEtD3+iQbvB60BS1K
atfYHDJdqd0o2slAClcDQiNPjk0lGj4EclQG/MyBa/y9yuBRBK1uH4O0U4Fnq+8NE0hEeUA4Wg7w
1HLxllNCviCjv1/OaG9Q8s3xmXxIYX3oSqGbptz96vy2FwPA9Ywqkr1CGH4mst73GhCIPtcb09eN
xJDX2qt7HyFqKCr7RL+VAaOnlmM8+oY7mrwbGG7kano+RFv1Nx9TX5VifK6aTCfUjQ6ok2LEc6Ls
ydgjVPM9NZ1wMPcTaoonMyH4+993UTviCVM5oS4nu8NKGTx7qyerHIGs76nr0Uz6yUzgrX7Kkw2i
UgXCV5pIbL0lKrLrPIrxmRLKn5DR9CFZG0+g+zDBRN2DAaFTNcpNJhKTvZuuQs6JxDSeGDbEPN2w
kjAgDGL3RikBpS/emgsKpDRbVs6JUYRWoxP7TeAU75oI/2/xPlC4OWJBe8CgjkbbYeb+F9BO7ROK
f2rnjm70eGls21QgtBWB+dS2KUdA1BqQ2W2b0YIw+XhH8EiAFzwTrDIkAlKDiNmHZLUugKeFyLoz
CPPVKa1t84tQ6RvR2MUZpaBfC6eJxCRijzZ64jpMJA8QChHAmNznBZrHFvGHWUbydqMnZIDPH356
bEGTw1KYHaaM6mCk7E7MX180kAhckv3uRPEOTk8ka1g5lVepmvkmATxfqLAHC0RlQG/z3MxLCp5F
YnIYi4Tw0QFsIjFN74uIefYEECBUqegPrWnlgCDJqVk27ReIDvdoGO2wrb8T3PbShYTwgf/ikTDA
NT11gIRwktvIEYQsglDgde7PD0qPR1s6ozH2dlB+gw7vdxlNGyvl6k0fzQlEm89zWx850DqiaZ1o
XlPiC0AGRlacKAKeaGJ2ZAfQVUz6u2teAyrV0E/S4YHcOozsFWf2nVGPQw4PAJncUIq8Pw1IDkhR
zeUR2imNnvEzE8KahZ3hz5OniRDmlxOh5nYT5i9Zc9sAIucr2XYvpCgsjnjL2osT4vwxZm/P8MBC
y530xCfZ5hZS8lbY84VGvT+GgKIaKfv76aO0OAdlU6xp8UCnykGz8gadSlSPp3/xBpNy9FQCMsCz
7IizZ5yR1ZLmUR4rocWsGBj9e1aO6mPgIDp8gtGw6Oyb6uPRDdYhQTpAyp4VxOjj2pVdYZ6M0Mc1
RM/GYXRjqnlm5ZN1AryqkXG4nz7wqqgqC80klkc4At27P8qPx7E/MahJjuxyu+R3Va/zIWQEcL8x
JCZX790EbS/bBYkg7U4RukXJFLSSXj9c4byFdrBBUZmFzw8p5YRa3arPDynhhLqdzATdbg6oy8m8
0eXygFrps2/a0R9Q9xOe4In/gLqdyAkmsk+Q/mle39YEkomkXc3qJ5KbGPloVv8hMc40Xugpq1GM
/4hO7U2Nsn5IdMKoaplGMTFyNLuD/5GXc6ecTEolTySP3eoZkJxJzW19lahyx6Dp1zQ38+bQ35pm
P/0mtyj+eSJZX2uGXYDzvN9WVIrFSs62wh8sTQ3ymAsE5MgYHR4kFPsBF28/NTS2kU1uzi4PuCj0
TZhGeYqJM4nxUeZRjXdb0OA6WpbsBwUqEALTe7Ee0E9RiZJhtLjz3Gp3zs/ltkEbbTO90LRyFB3u
RWdEvJMWwGV/chpAY80bJQHuisjhJILgAynSWRHlRbqsCxZfvabqfQe1WEiK3otKHmkMaose4/G4
mIE7tT+nyMYWw6FbNrkRbvEA2GE+srEHmtWe+SSWOCHfac8UZGPXrvbHuG2piiai6nCfsIW9ebtM
eK1LaoOM9wSQr97yAfepQEuyEvW1lw8S7Ju+k9bpi5nNQTFhTXVAInUoN1ObKERJVq1HHwJjqMAl
tGSc2HaTRx2QpboXL+RRh6S0pKnwTHji9k47jxZvpKTJ+FLp1W+OxmzSACBqnuvT4zQKZ5Fy8fnF
igCGpOlEemJroB3bp7h45ySV1tiubj8z8Yhizs1jSKcLv3Yv0nCSRqrHnvNwkho3z9pBxFsMEU9O
EPGuzJ5yK2IztRzZ+xBezJbjZNKmIUqtHRxS1MmOjEBn+tDN5GpR9LAZuTfO9FHJ1LWsrOHrisqz
cnN9OsbavDffNKg5oFai8UhdwwE12j4eUPcTamREHlCrM/LsGZ1wkNsJdTnid2kn1NCN+6TekOXY
QO62OTijV+dQUtv8DPTqHL2RJxITn0UzSHhG2xQOeEYJGBpmuk5SBp4f8LC5z0kWm3k01fyQGH+L
3000JxLTvLOiQHP+zjpIHZGn7DG7ZZkKXrT3zO7IluPmzbYXYLmyXbNz+MUKpeKNmtABW0zvedSH
xJ0R4Gq5O1s6KlC5JIcpCZgnim22hYro6a45u0bsGBg04UaMHaVVxCpQC7aJv3jwTt2bvexXRYGL
w1nZL7Hz2CFBW5XO0WMTcoET+j4YJji5PIj9K6E1MRaULDV95EyDz35lwu1FPw9M/aqmf4OCy5mq
I/rwgwaO0ETyjJ+AS19Nf+1yisxspDLvhQfQQw2A5HsRBPRQXHTgTWbvFerYp+miYVWt3eET0IlG
DZnzITGpxC7xhAWuUa8lWhUxuUZwo+P8oafXIcSixDUo3vTREKmws8vI9Q25FG+BZfil5OgVkce3
17bV2AQMmkWc1v1oIj6pVG9BgKUCHpazoo56a64HcstRfGRUuOyZwHjD6LE4J5OTiBN7C2S0sKr5
5k5yPB+Rix6Sc164BBRLNkcAubQLJWHan7XBZ0XTkJ4d5osTI1dqcT/U0Oo1qw+tKdGyPwXtzb+/
L4djM/yNfUqq7A+hdHovGEjlbTHa/XHMQKT6R8WT9bso6kYq7F7y0ZzkimLuZ1/61R56f8TKKKIg
77SjgYl8Z16hre7MQKBS9+NTfEhZFI++R8gn1Oq+f0akrQfUOZ6MnY/GpnxCzeq6e/ZrTuaNboQH
1EpLPCeVxgNq+DXbzkDDr0HJY9vnLAZUneAE70nQIh2J322fPgkjqzc1yur6IFyA1vLOdGEnJySy
OHmnclmhT/w0inF1xL9Ad+NpFOPHhKu08EPyGBQaUWDFBIsJm19c4Ybtp9/i1WV0YqXpMiK6PHaX
lT2/vchtxiuSBONIyHK6TiLMRd3ZVrhDtSk+mUw87HzQi16jQKnhjmsOX1AZObqMtzUR2IkCATAp
s8PKxCzWXVfivyL/FICZcHGEJdX49gnXJl1ugh+H1L25jedJxdrHksVw5dzu+ynKhd2bJln9mJTe
PvC+nyIqI1v1ZDSPTgKa92v0CTVxgNraH/fhDYXcHUkHRM+VRfx1+71cg2wXkbOjiAoNgNG9QA6M
nqh20MTX+uhK5gg+4kQifux8B3GiK8i9nS0S80ZqzJ5CfKGklaIJNqWf5xKn/SO8lta92Q4vOPDB
MR2Fj5yUnN8VPnZypy/OUNf3iwlhVdx1qTm6ipCynYunMoDMGmJKHp9Qub5ItqmNBMJTvhHbyTrJ
qBS8Oc6Ov0RXR9y9wmY53qM5x15JwF9KaIzizA2ZFyHeXB5+bWSK3eEbfKrQ+s3t7lQR1QuG1Rm1
xguwai+13IJzDSKUlIf9vOcqWgLfbdVkD+YLIXcvWUW096IuTI8QWq2SNZsF/lZrdRbPpyAeoka9
5Hn2a5Iu2n1c1Q/7HpNIrRspCdtjPMB1SnXZhKTK8UK+ZxOawbbm3WGjYyS59gTqIHuKN5eAY+DN
u/ccGqIT6nZCncPJTLQ+e64QLAfUaLxxQE0nMxnv4d/3PkwnY5d+wm+4UNvOPhGYhwT7dt/RLwIZ
A9Fdp1WiiGyoapTlEKLxxkj02rcFHC8p6jvG9xHNTcDq/ZAY/4JgdcFI/LotDwBOO7pmOqNyfbtu
fae7YkEba/Z4XdG7HNpt32ARLd9HadqeB2j4G9SHbFMN9HdL8ygmDNcv5EePAnaAmu1jT3uRlJoR
19ouMMGGD1lJyuosoSFDpVkO1mdF5OY1dJjeiySCUpfVtV1hutIrk/ehkV6pV/SgaJGbVyl5W5jQ
o4WVNFlcVLrAcB1Wyj0x2hLuxRbQqS1kT+JSQxQhuNOFL4cWxnuJG7Gt0G4kzrkG+mX37weNKPfg
5MhKRrVnLc0bJYvtohm5FhjlCnC6G0lX7l7JsVmtoty9gJ6le16je8eVTvS1bgJCqzgt3RsVAO1c
ybJpP2pD24furQYojpWyc8JGXdbIrNlzdrSXb84BQy+PK5Fw3+oQiYSZoiMGFIUFQU/l8bFVnMpY
byTHgx94jcD+VsMTUHkbebcpjZrf6t2mVH6s7c/UDAyObCD35vCeKg/wo/2FC6Ccgp7AE8kK4Ypr
IvVZth5LmEQVpPHktO+OiJee5M4eeYVlPKc6JOVJRAHhuoioCRyJSZHY05DILBQBuzlfEwkum3gg
fijREq8sOkcQJVqyPcrmWJ07dAFN6mgY5w55+kHJuXUR6wXquhcVZBsWdQMYlwQuYlQH+c5FDF3b
mo8xuvpiNFBwRk0IhOUbMXB8RrxkKyvLwu9U3OLe3TPieKOYck/CP8WU+0aT6PNMxdOR8BmDNmlt
20hsYXf51NK7EnrfXbONgPu86Cf3e8RNvu/+qOyMZ1DVk7HR1O+AuqQT6noyE238PUf9jsbuJ9TM
JzwBTOoBtVJe3/SK/J5aBLn/Lgpbk7Lhso6kiQ+JaeEY88CMnChMT44K7CyaSZ7cRPFPawtq1NUP
/tEafVtzighfgDHtkAwIxeJ+aEAoNvUhgxsjlyzwRz4kxqut6INb57lY4Jh30tr0IZPNGK6XaYfb
/Z1v4szl6srRZ5JHdxMRCs3KxX5J8A/CTGHyDlFYgCDawXeRIoUI0n5/UMNF1D22pYJSby1Oq4Na
ytV/6mBuTYwVFnJnxQ3QIYrTBnO142prnhyjWQbh1Xg//RHQwzPE99NH/C70mB1BQfwOHYoN8/eD
UhQ5afNULRSHPbimyEsMdyB57Y8ccDZS0Qs2RV5F9I6ey+qwjlOZinOeEOFr4nNb8fJS7MXgVIJh
evIBRSPW7sg1fLFae3aYQKJZO/JpJ5JFgxOKQUiz8iZaN8zJ/QECsMaqA7+I1jXhuP3JRILWpYm8
FYphTvr+WdmEYF2t8yAmc7EB5ihG54ghLVEme3JHcYA12bxdRpgtFOoO84GQIXqRHDnmlK9uVOYS
3s8NIAj65jOjolduUfeEBTZ9BznNSfWe4sXFy96ZA0rpwJ6bSEy7w3o1PHH4Ni5LVpJhsC4K6uW8
y5Jl2yPahTl86kgtPbkXSkC3emVXGQcBgfigvvvoSOEgF62MTVWXXNLoOzJ9eG2pAQc7kzs3QmRN
H1wDfYH7tN7oxMnXile35onksZUhyYe7NzUUdeHJfi+zpY1+QfFAZrUG+savOqCmcEJdT2aSlV58
xs/gE+p2MjbREXU/oUazigNqPtmdoqT8OXAYT6jryc4jbfJ7ajBwDyjxA//ZtyWWv+E/+7b88zf8
50Syg//sa+nc5KSlK9znzIUA3QjWOtgcKEzn6n0IwaPY+swXE1d8F41OH1p9WaTw1ejNtgpbxnW9
xyNBEjeQDPtaODt5emYqZkGjW1edF2Q9vXT1w51IDFoHUPlLdz6UAp4bw7xoC/CIxrtE3odQeA58
bOdDYsYUVJ/u+YJYYwfYhjOXAfEWsiMuifASmBXrTDhS3CVWZ2QNQyUuFxqCsyJGO4k2f8d0ZazA
Us+OzKFsbtTvOGtuYgCW0ByhQ5poC8VlbpdTlLKzHuCJDICb/SECDCRaXezXAxTIWlt21gM4kRgS
e99Jwv3akjfb0YAhzlJpq/EAy8meKkS0MbBiv4UcSa9MehNX91uEhWJSuuUGckQ0h3dCMop8shb/
1e1FkSWp6dpOHPnKqN2f1jxap3D0RumjofVMYcKJ+TXc062CQsBxAPLs95mAHauXvHIF7ToyEhGd
qaANQFMfslmrFW+BjiQA22RUCk4ka4hOLiJOrpZDwd5AFXTYwvTqXe/h6m8DZ7go8bfgkbiJune1
Ikm1hqi0nIE7qVdwc39a6UpJ8DZxgF/oqayOFt47krpaTf0a4CQbe/cmnOUakndvIm1VxvbuTR66
JWfnsDKKOfHPzlzEf25I69lzDv5zzOTpbeCicFO37zOUyo38CfX/lj//BeHv6bgKZW5kc3RyZWFt
CmVuZG9iagoyMiAwIG9iago8PC9UeXBlIC9FeHRHU3RhdGUKL0NBIDEKL2NhIDEKL0xDIDAKL0xK
IDAKL0xXIDAKL01MIDQKL1NBIHRydWUKL0JNIC9Ob3JtYWwKPj4KZW5kb2JqCjIzIDAgb2JqCjw8
L1R5cGUgL0ZvbnQKL1N1YnR5cGUgL1R5cGUwCi9CYXNlRm9udCAvVHJlYnVjaGV0TVMtQm9sZAov
RW5jb2RpbmcgL0lkZW50aXR5LUgKL0Rlc2NlbmRhbnRGb250cyBbMjYgMCBSXQovVG9Vbmljb2Rl
IDI3IDAgUgo+PgplbmRvYmoKMjQgMCBvYmoKPDwvVHlwZSAvRm9udAovU3VidHlwZSAvVHlwZTAK
L0Jhc2VGb250IC9DYW1icmlhCi9FbmNvZGluZyAvSWRlbnRpdHktSAovRGVzY2VuZGFudEZvbnRz
IFsyOCAwIFJdCi9Ub1VuaWNvZGUgMjkgMCBSCj4+CmVuZG9iagoyNiAwIG9iago8PC9UeXBlIC9G
b250Ci9Gb250RGVzY3JpcHRvciAzMCAwIFIKL0Jhc2VGb250IC9UcmVidWNoZXRNUy1Cb2xkCi9T
dWJ0eXBlIC9DSURGb250VHlwZTIKL0NJRFRvR0lETWFwIC9JZGVudGl0eQovQ0lEU3lzdGVtSW5m
byA8PC9SZWdpc3RyeSAoQWRvYmUpCi9PcmRlcmluZyAoSWRlbnRpdHkpCi9TdXBwbGVtZW50IDAK
Pj4KL1cgWzAgWzUwMCAwIDAgMzAxLjI2OTVdIDE2IFszNjcuMTg3NV0gMzYgWzYzMy4zMDA4IDAg
NjExLjgxNjQgNjQyLjU3ODEgNTY4Ljg0NzcgNTgzLjQ5NjEgMCAwIDI3OC4zMjAzIDAgMCAwIDc0
NS4xMTcyXSA1MyBbNjEwLjgzOTggNTExLjIzMDUgNjExLjgxNjRdIDY4IFs1MzIuNzE0OCAwIDUx
MS43MTg4IDU4MC41NjY0IDU3NC43MDcgMzY5LjYyODkgNTAxLjk1MzEgNTkyLjc3MzQgMjk4LjMz
OTggMCA1NDcuODUxNiAyOTQuOTIxOSA4NTkuMzc1IDU5MC4zMzIgNTY1LjkxOCA1ODIuNTE5NSAw
IDQyNy4yNDYxIDQzMC42NjQxIDM5Ni40ODQ0IDU5MC44MjAzIDUyNy4zNDM4IDc4My42OTE0IDAg
NTMzLjY5MTRdXQo+PgplbmRvYmoKMzAgMCBvYmoKPDwvVHlwZSAvRm9udERlc2NyaXB0b3IKL0Zv
bnRGaWxlMiAzMSAwIFIKL0ZvbnROYW1lIC9UcmVidWNoZXRNUy1Cb2xkCi9GbGFncyA0Ci9Bc2Nl
bnQgOTM4Ljk2NDgKL0Rlc2NlbnQgLTIyMi4xNjgKL1N0ZW1WIDEyNi45NTMxCi9DYXBIZWlnaHQg
MAovSXRhbGljQW5nbGUgMAovRm9udEJCb3ggWy0xMDAuNTg1OSAtMjY5LjUzMTMgMTEyOS44ODI4
IDk4MC40Njg4XQo+PgplbmRvYmoKMzEgMCBvYmoKPDwvTGVuZ3RoMSAxNzQ5NgovRmlsdGVyIC9G
bGF0ZURlY29kZQovTGVuZ3RoIDEwNjE1Cj4+IHN0cmVhbQp4nO17eXhURbb4OXXXXtLpztYJQdJJ
ExJIIJAAHRChISuGsIQlCRKTEEISCZCFkIAguE0g7qKAyyDqOCCiBtQhOOOu4DLgMiqogPBccCHP
ZXTESLrfqerbARnxve/33+/7pm+frlNVp6pOnTpbXQggAFhgLUgwvKGpuuHIginbASL/BoCvLalc
XP19yty1AJ5lANYTiyvbGqQzahf1RdMoV/3Sqsp/DvwmASD6UwD5mtrFy9pmP3XgIPVnApigtra6
MvRFk060PxAMpOqCNz6xc5zmh9E19SsWZq179iGAi2oB+pkXNtQsfvDuh+sBQt8CUL6qWr7MVTtw
9IsAznU059yqxZUNavqHDQBmml/ZCJx3AlvVxXeVh477EWL5UgCPrr30SV7+5acrb/Gn9x42mbXD
RGcV9BAYo13rG0M8TvGn+yeZzH09xod5eQv9zgANCkABBnZIg9k0NE/5imSFMpDM6CN5iK6O4Fv4
kH0DuXInTCS4R1kBccqfoQHfhzbqe5CD1AJu6vsT4dcRLCZ4TIoDO7UVyJ0YSuUNBLcQZBE8RHAd
wU0ELQTLOD0fS/jzBE/QGJN0NdSoQyBXcYAivwQb5c9gujKQypsIHoGNSjnV22AjGwv3yFngkL+l
9npq/xdEKMVUboXp8m4qd1L5CfU5qfyM+ohG/hkULYzmPUjwBcGVMJ32u5Ed9p/mJfHwN7nTf5r4
aKK5J8rboFmOpvIhmC3fBRPZj7RfGdLlZ6GdVVH9G/8P8nzC58Fu9Ti0y3sJ2on+YRq3E2ZLi6Bd
aoKJUiqMkJ+mvkxQ1BwIkRfR2jkEY6mvDWbQej8HSniS71vsnfbN9xzck+Cf8/RbwHm869dA/OUK
Hqv82wiq+3g7Hzhf54C0E+jc8Fri5bicDgul+8FD5ccEy+VyqFOehAIBSbCC6G4jOg6PaVcCo3MZ
RzjXmT/1wa3+D+QKmEv4XDkDxirRkCq/RfqR7v9KWgp3ENQpc2GoepLkSvzw8+e6Fxjv/0mK9acT
/oj8mP8XKqu4TinHYQHX0aCsuHx0DcZpl4Obxk6g/glEd5DrFNUPEjwh5jtAc+QYZ98J2QRe6ruJ
4Cm5B9zEm5vv39DLJ2jPV+uTSe/5efCzMEoOXP/YWP8agqWEh4oz4rpHdhQ8ryDwc6C17if4juBL
rucEOwkqCbZT22tUviho6iGS9CmF6y3XHa6jXE+o/zTZQT9xZpz/5dAm9Iz2Jd0LRwka6aw2qNfB
bIJ5BBO43LlshexyxJ7vEnZKekvlJ2RPg7g9cZ2mPazrW5PrXvQ5Jdd/sgsa8xnBASEH0ru+kuxT
OSbKfkI+XAeDJd8/2QcvJcUor4LdXK+5TvaVXHZ8b2Sz3G6Mcuk5PEUIO6JSLoMRwh5IX4Nln5z6
5AXZxCvpMW4l/GolEWL4uSrX+jerS/2bpcFUphBkEMz1b2ZF/mzFDrLwOfMMf0Nzkd/bqDwL09kY
uJf7GkUHXfiaOYRbYaE46+lESz5H3g4XC/5OgqzOgynym1ReC1eyMf4reJv8AuTLdlhM/N7CiuBu
eSv5Qd7GfeJ6SJI3BPqlp6kkGnkLzBN0mwlfATFyNpilj6hvg+i/WnqPyv2QL71CY7dCuypTvQXs
ahpcq2bDVNrTCt4u6Hk/tcn3wkbVTHJcGPCtcizM4nsjHv8mXw4puhXitc1Ek0gyjiOa02BTImiv
MaDLr1F9PwGNVd6DOD6X1grzaM0MZQu1vUBAYyiSxatjaPwKw3cV0Zi/GL48g2REc6pFMIvqdqWR
aOxwpUaltoPWHQWjVE77AcG3MEpbL+acIueSve6gMfPIR+2mcwfS662Qq14MU6WjZC9v0j45XE7w
BgxVXiK/RX5avoX80U4qHyOIh1zpM5gkzyIZVUARnW+E/Da1r4fFdF7t6gaadxTFntPUVkQwArLV
i4Rucflly2/4z/C1qT1XWk3+tZb0otb/NNvuf0M9TT6si6/tPyN4oDVkXidZkU9pD9rKv9nW+fZi
lIZdDg7aZ19JsY/vS7mX9IHWIv/zNPn3t6ncSeV+Kt+m8iTZcyv3O+psipM9Ik44yO4/EPGSYpbQ
qYBt/qHPBlvJp7b82h7Ps8tLDXuMDNrj+XZ4fsnjrYh5XwRiHvsE7g7KgscM7vdF3KA1grTnl8Gx
Ab/uP40bYRjzwTD5OMWJdH+PNIHsfAQsNE2BG9RLgXwq7NKepvWr4RLDF6YRXEywWn4Pbmfvw7Uc
CN9FZQP39TxJMrKmCJ4PUWbUj0CFs0mWJGh+/aFOSVZUTTeZLdYQW6jdERYeERnljI7pF9v/ogFx
rvgE98DEQUnJg4ekpA4dljZ8RHrGyFGjPZljxl487pLxE7wTJ2Vl5+Tm5U++tGBK4dRp02cUzZw1
e05xSency+aVXV5eUQnzqxZUL6yprbtiUf3iJUsbGpual7Usb21bsfLKVauvWrP26muuve76P7Sv
W99xw4033XzLrbfdvuGOOzdu2nzX3ffc+8ct9229/4EH//TQn7dtf3jHIzsffezxzl27n3jyqb/s
6dr79F//9syzzz3/wosvvfzKvv2vvvb6G38/cPDNt96Gf7z73vuHDn/w4UdHjh77+PgJ8luraKcr
wUt541i4Ctfg7ehn+9lr7Kh0ldQh3SjdLx2UrfI0eZ5cLt824PoB/3TZXZGuAa4E1yDXcFeGa6xr
nGu8K9u1xvUn1zbXznglPjw+Kj4hflD8sPjLE1iCmhCaEJYQmdAvYUBCSkJ+QkVCdeL9iY8kvp74
ZuLn37JvtV+Y388zdNhKa/ewfbT2YVr7Olr7ZulBGWWbPEO+XL51wNoB39Pa4S6nyyXWTneN6Vv7
wX9b+zJjbQetHdO39gJae4exNnyr/IJ+v/8TAH8ExAP4HAC9e3p39+7ix9+7orett7V3eW/uJ/d/
Muq4oRTHrz++8cTPx68/8d2Jb4+3negEONFx3HFi6AnXiQEfX/HxWye04x8d23jsu2M3ABzbRrDs
WOOx8mNpx4YfuevIbR9+c2TJkRI+j/KcUL42kcGnB0Dgo8lqz/uwB9if2ZP/1rr9/Ja+ntsD8Bs9
a9l1AtkJD8J1cD2OhI3wBfwBboYb4I/wMPwJeqADdbgWNsC38B3cBD/COjTDMfgGtsAO+Cd8T/ej
B+BReA32w2MwH6rgVlgAb0A1vAqvw5vwdzgAB+FLWAj/gLfgbXgcauBnuA3eh3fhPaiFr+EUrIcr
oA4WwWKohyWwFZZCIzRAEzRDCyyD5dAKX5FkVsIKuBJWwyrogvthDVxFt5ir4TR0w9N4GD9AC1ox
BG0ooYwf4kd4BI+igiqGoh0dqOEx/BiP4wn8L/wEwzAcIzASP8XPwAd+/BxP4hf4JX6FX+Mp7Mb/
xm/wW/wOv8d/4g/4Ix3NIfwX/oSn8WfswV/wDEahE3vRh9EYg/0wFv4LPsH+eBFZC+AAjGPIGJOY
zBSmMg1dGA/kqTAB3UxnJhyIiTgIk5iZWRCRwafwGSbjYByCKczKQpiNhTI7c7AwFo6pOBSHYRqL
YJEsijlZNIuBv+JwHIHpmAGfw0nWDw7DCfgIjsBROA4fwMc4HiegFyfiJMyC7ZiNOZiLeZiPk/FS
LMApWIhTcRpOxxlYhDNxFs7GOXAfFmMJluJcvAznYRlejuVYgZU4H6twAVbjQqzBWtiEdXgFLoJ7
sB4X4xJcig3YiE3YjMuwBZdjK7bhCthN2fhgNgT+AnvgZTYBnoSn4BW4Bl6Eduhlw+Eu+G94CR6C
d+B5eAFN8AucAfCOmlVw6eT8vNyc7KxJE70Txl8y7uKxYzI9o0elDRuamjwocaA7IS46wmEPDbGY
TbqmKrLEEFJz3LkVrs5BFZ3yIHd+/lBed1dSQ+U5DRWdLmrK/TVNp6tCkLl+TeklyoXnUXoDlN4+
SrS7xsG4oamuHLer80C229WFc2eUEH5TtrvU1dkt8EKBy4NEJYQq8fE0wpUTXZvt6sQKV05n7vLa
jpyKbJpvl8Wc5c6qNg9NhV1mC6EWwjqT3Q27MHk8CoQl54zdxUAP4ct2Sok5lQs6p88oycmOjY8v
FW2QJebqVLM6NTGXq47zDDe4dqU+33Fjlx3mV6RYF7gXVM4r6ZQqaVCHlNPR0d7pSOkc7M7uHLzy
02jacnVnqjs7pzPFTZMVFPUtgJ1Kot3t6vgRiHl396lft1QaLWqi/UfgKN9in5ioP4gD8UYc0v7i
4zkvN3R5YT5VOtfOKAnUXTA/djd401JKO1kF73k+2BM5m/esDfb0Da9wx/OjyqkwvstrozvXzncN
TSXpi28ifanf1SkNqphfVcvLyuoOd3Z2QG6zSjq92YR4K4295uwankb0lRW0iTouhhklnWnuhs4I
96QAATW4+BnUzSwRQ4xhnRFZnVBRZYzqTMvJ5ny5cjoqsgMM8rncM0r2Qob/+K6RrtgnMmAklHI+
OqOy6FAG5XSULFjYGVcRu4D0c6GrJDa+01tK4it1l1SX8lNy2zsHH6fl4sWKYhTt7TzqIDHfuZao
u0pYrFTKT4saXLn04540jjrsdFyiyk900jhXCbmyIBmtYlBw7FfzUEVKzMrnXRIfmpUfG18aH/j8
DkuxBk9KYqd+zlx2aujjKbDOBVkLUHOGBrtyqrPPYfBXkyoGg8Zsv80n47IwFqYROj/O/GCXlEiW
S22MphFN/BSjXZ0w3VXirnaXukmHvNNL+N64rMX5Fsx0F8yYWyJO27DJDt1dMLODt7ozA03g6pjc
CaROXjKczLCRgdZc8jwdHbluV25HRUdll3/tfLfL7u7YVVDQ0ZBTwZctIRF2+Z++IbYz98bSTntF
LY7l87snL+hwzywZFyuUgWXNKjG4yDS0UkxPbmPSLjeum7HLi+tmzi3Za6cUa92skt0UqLIqJpXu
Gkh9JXtd5IVFK+tr5TUXr0EBki/YTfGLd8Xu9QKsFb2yaBD1qi4E0aYH2xCquligzS7a6DOUVvHP
mrYD03ZM2PHmDumy/BFxcwlmEhQRzCCYTDCdoC57RFwJQTHBHIKpBNMICglyCXIIQtfhmmi8pey+
MmaPxo8B17Tc0nJfy+Mtz7W82fJxi+ZqwjVNWF6E9i3eLQ1bbt2ydcvzW1TXhuEb1m6QvA1461XY
sHrt6q2rO1cfX60sXYOhq+JWuVbdskoOvTLuyluulLzLcRqbJk2TpylyRVtDW2ebFJodl52WfUv2
fdmPZ6uQnExJVJhD93pCJxyMQrctJ8GaE2/Ocek5cWrOADnnIpbTH3L66dF6lB6hh+l2r0O36Vbd
rOu6qss600Ev6NL8RQWd+vTLSnYh3lzaGVYABbMm7QVE//U3pfzmZxJeVNAZO7Okc+NFpQWd6YTA
RbuiYJJRGX5RaQqSi5qEBdNLdunUnjUvUEbZG8bv8nhy6lwB51dRmr1rODQ8kQ7DIaYhuqH5V59l
geL81ZuXpfDclfJ1ZS/EEETIaXSnAv9JglMcfJS9Kocolx5Dtye6ZSn/oKyTBimvgvlC+er/64fy
PhvaKN88SU/g00NtMrUEnrM0YNBsp3z3cdhLueohyqSePQfn7S9Rvko4m4xPsPVowiRop9zlNjxK
83xFeVkq5Yh34iya5xnKhVLhVXYcy6Rr5OcoY7JQ/TbKob5hw+XDlOk8hB/R71bmpPYn2VusRvor
/Mzq2ElYy9ZSVrQDmnE0ZbzBz7fEx7cCS/5fnqz/4/MCZVoN+Az+zDzimRl4pDF9z71yhjz/Qo9C
ybSyXvlavV39VLtTO0RqHKFX64+aokzFpufM0fRUW+yWKssDVsl6q/XWEOU/z3+e/zz/vz/8NQGs
xcultfLlIIEGg7xRyn3SVvk+DZzgoSbQ7kOqAqT19nZjWnkZFSOGhzviHYnxjvi1EvSuZXTLpimg
l7wdf5O2GI+wq9h+GnyR1y45IYkmKgYZQMZ8mqcb7e+Xlx2gSUbFRy5mDjzy9dfEBfGiWJUDxIMZ
XvLOzFfyVCaXmJENUceql6pz1SvUlWqHere6QzUlKqOUHGW2Uq20KNcrdyoPKSYp2VpiZbo12pps
bbPKzCSpaFYgV5NyZYrCcoOidfnfetJuVwsI+eJJq1Ugbz1psQQQb6zJRFiDmqcgKHqjYspnTJE1
it8KgwkTJjjCxqR124UMjnbzAGnvDhtzSVq0nRodY8ZQ95iyxvKyshHDy8uwvCxeogczEKnsXuQz
L/R9zPKbWGHvSn5zGuw7pBzoyZBDej8hiU33n5QfVt6BSLR638oDumsjK7bUWFotEt3rkSXT3b2W
7t7rcDNuxy58FQ+jWfrNVrg07O6w18MkqU1ZR3w3h2Nk+PXhTNMxUqV7PrZYUEqy5FlYEuYhA83q
tCZZPdY8a7G1xtpq1a1ONSfPgY6oZCuWWGotbZZ1ls0WxWItxhq6/7fjJtyGe3A/HsKTaOZREzbB
NthDIoNoYHw+UoIIq02aHGGabDNFSCQ7kpD9gP0ACacsvcyRUVZGKlDWTbCvrIw3jhhOP1BedvYh
AUIZaoPcCSwyIiwj3eNU413gsEN8unzNouIX9nz1wVNvtqy4z3eAnp24AgedURYdKvYd+Ppr36k7
3nkY78AyzMGnuH5vJM17V3kJdAiDqd7RoTma5tSYZs7eg6ihE5PQQ7Iopr1tM/b1E1oBw83WfGQm
R76Musw1wN6dnkEg1Lex990ysoP4eMfADM4XCSwjPcxhj0/Aj3x/Rc909GLrmX0TJr/ysa9giNJl
8a33vX7mK/m9M9EqDkDE97mlcM4uoczKArneIdGUreeZzZy5JE3SQiBbydb0JJ2BbsV8WVYg36Tk
67qJBSTqGGOYUjeX5Dj7pyRGdMRHxhuAd+Onvv5s85kF0jb5Hd/DR32TTyp7TwbXvYzWNcE072iW
59FR0520lEcv1lv1dn2bvl8/pJ/ULboiuFCTVAaqmXOhQr6m6lpAHmHnsPBuWeOnfQyI5ZnU2+s7
I70iFu+db6x9D/3cR2tLEOcNk7K5n+EOgrsH0JHPG5hxxPAMmucelJW9PWQSEOE/pZyicVa8xbu2
VcI2GVtN2GbBfL1NZ3mku4y5KTEzoXSS4RcKHSsmq5hpy7cdtkm6LdqWaau1rbMpGnOyJCbpSrSS
rEiYC2pusoa6Fq0la5lavlaidWmvaoe1LzRzEmCQvzxyYXtgP6WMJ8FM/uK0t9FsJn/RrEOz1WyW
ZMasFkXRW0zWFotuibYkWyTN5DQlmaRWC7aZ0NQsW5ols7ld2iTtkfZLh6STkiq1aLJTTpKL5Xb5
pKxyNI8qrfI2+ZCsyW0M28gb5ZhR+sKM5i7/ceG3OOIdxt2VuVFmC0zUxJosikCUJj1ZRpMcIw+W
JZBNSDcQC93YuAebMIGMzd6dEvimCEMrw7Syxu6yMTEBR0Z2WMZLcmzc33Hg7b0pZY1EJvobGxuF
1XI/Jz6KW0I3Sm7u7DKUU2c2+z4o832w5RdM6sBLcPR6lKLOHJIGn/lKefpMovSRYZFn6JYQCv2g
xjv+ekq0mYQ2mewgNCon34LtFrTI9mw5W1OcSpLiUfIUBZRYe4xqsjmk8MmISsxkE+hKwBomBKwh
Iz3DQc9ZjSzrfr+b++VyYjYeByWRQqWTvToiVA2FxY4eNZJcjPSWb8XFV/i+j8JBc9mwu1tw15nt
+YMe3PTAY0NYGaq99yp7Q33Tr3k/tbdePuSrU+ddXz8n4LWl/eS1XfC69/ZWB7bZEVYCSm1k3qMc
SP45k7w3984KS3J4HHmObY49jv0O1a7kaP2d/T39pf5REJXjsRyysDxLwOG3WzZZtln2UJPJEk+T
Qq2zzcnwCtNKE7siemU0k5LsHnueXUqGTMgnK0rsh0NMGK3pkhTusGFc+GRyvXEm2zl+1xHmHCOO
THzLhfdt7N5HAup+2fC3IFwuicnjIbGQVAYOGjRq5OiMdCf3wWpkhDKAHLHsTphecfedn9X7Hm+Z
8PNLvtZp6zfPrULnhmuyfSdPHZjxZf3WgnUPL9542Y7j5cfnl0+5al3+ivurdn/O7Z5ujvLbZL8a
ZHoTtQ0ob8DsJLqp1LB2to3tYSowK1dppuXL+QoLBF17N8XbFDrNz+2fC+fiiKekgX3lO+MbJj8j
v/PLMPmdkydJoyb6T8lhchZcBIPgNW+7FuGMYNDixpXxuDIRWxJxpZUOhvyogslyppwvS1jL/QZz
2tGuWmBAYWSyluBMYAlT21VUk4oHYskALHEhsOjYAUUWU2iRbo+2J9sz7fn2Enutvc2+zr7Zvt3e
ZX/Vftj+hT0U7GGuIpMpZGCRFFIUFmuRLGFaQDUDymk/StuwvycOpMyIgGX293tfecX+MsldRD/k
QU9EPgKqJ6qqO4HOYWB8unOkO0FLogOJckRGOEW7NMjtioyg02IfJTw879F9FMowddw3N5WPvnr3
j5/OiZsyYvScJK/Ld3jbiUWZeY/e9/Q7oc+kvTj+Y99rn73vGR0zHf8W8uKtJ/jZkPSkQyS9SHjB
e0ONudXcbt5k3mbeY1aDMV+GPErFEsNzwmdTOnFnuCKRT2bJXDchkdyTx5xnZkAuV8RSyissTouH
VHoTpQ7q1HbHJkP3DzlUoNzCgtynMjQXXUr5CCdmFhsWiRQCQCqK0ItslggtoMJCcEdJHN3lQm6U
g75LmUMwVRCywz4VxoDC2uN5zkBiAsdIShqkNxeV3HHzQzjxhivmLX5w6WnfCRyLoX+VPvzrzGe2
+R6f90r2QIxH7OX/QZDBbNKmdKVH+Kdab8574Z+FM6k2oi2CDFFZqbAc02wTRZD+yf0Z2EMKbVsi
p27X0KMVa+3aJm2bpoAWG2JzFslhReZQs2wxazYQDlgoQ8BBlfX+0DtuXMCLisOPHyXYHTUSyOrI
XUjBfYz2SJlxd0w77vNj0rGVC3p6phdvfAAnDayzT0zIwP4+H05Ix0fH9ahSmnfPI77dKVFgWEQJ
nWk4yfQHb1e7ukndpkpQr65S2ewolPJDEJNUj8pyVYTZoZR7UOBhqPdL7sfODYa1Wpu2Ttusbdcs
gSZeUbTIqZ4wdIZ5wvLCWsPawzaFqWEYMRWnalZst26ybrPuse63nrSq1hhNxVa1nRKImQ5Ui4Zo
Y7VLNUlykrBqtFZN1kzREckRTEg3gqsbA0TZWRQqF5ksoVpfrkNXhrJG+3tcDcrKG5sCPozrRSM5
sUZDF84aEkF8VFQgcRQ6kJEOkRGJ8SRUOatX0h5Y/0hp5XW+nh99n+CYj77Efmd+YrZ+X72Pb6y9
ufS5RRjHlWGs76tDw8q/Jgtxk1YOUj4nCyn3ZkWaLDyfYNG2ZEoqumyvUobxhe20TbfZlUKt0FIY
zKqDktDBairSbUWhrCjcag5VwyHoGcaJ+0R3d/e4fbS7fS+Tkwv4W2dGpNtBz6iM0dwLsyNFqXlV
eOzDnnv/qH+ws3StgrErS0NCDp65T6o8+Mr3SXTi6b550ufy1TAcxsFe74pkayal4sLOElNGpZC+
jo8e3zZectv7h6lTk1MzU/NT21Ll1BjP1KT+2NYf+4+HxKkhI6a2hWHYJcksk5UwiW4fdvfI5H7O
uOjIkUXJcZlx+XElcbVxSlzxEBwyUy9OQkiaSTZclDa2KDLNZjFHBr1e7z47Gey7vWU81d8XZtyQ
Ao7vXYo+71N43kchSDQHjJgbQrgnEJdJCm4XhSCPEYc8Ti0qMoIsJCmJy4doeCCniBQe0RfIVc+W
a++vv/GeIX8e4vPNGbPnTNetlfMfbR3/8Y7YoYO1spy420fiYt+Rg//KqCstragpmlPv636pzZtZ
HrF31MLo1g93nhjd9Mfiy9fu+UhRU5zJA3wfPbBXvqy8uWH+jIZ60oJ2imEe8gthkO1N1SMQCsN0
S6FeGEj0PKZiU7vppOknkw6mcLNFLrKFmU1mm2YJGv85uUk3T0kcgmmNztnj4K490iGNW7Vg/FWx
Pl/ljteOsTuq2rJSzviVZ8f1flfy8Vu99dyuyWEfUQ7SncEBY70JXBGTbZLpSslhsxYedmAX5QyO
8JDpdlil2q1mu8rD6Pv84hq4t+wLrI3pAWly6UqkZvEOLBg3e/Y4gpz1+AfloEAJetKl+Qd+edvY
fRnt3gJ13mzdjHpIdEhyiEQ3UbpHWPRpJoukFkqFgYzWIxLZdkpirUmah+4LiqpNYxRDJNmkgmwG
s0kVUuHJCZdMIC3houHMGkpRFo8B6XDnLI30vdLW00O32KG+jfgkfrbGdzeJ5szdeI/vit4a4nC3
/xRLIA51uMKbmSMh/8ootZrx372ZKZAHrJM3y9tlVYbCzUjOBwG7/Ke8Np5m02UaZU21ID8+yqL4
4aVwxy3idUBb6Tfc46CA7E4Ytbtn+dgbdxBHv0zZN2jJqYDE1FLywXHQ6J2ix5O+aHHoidsWx+JI
aXjE2EYXUXuh5nA6kig/rHGcdKgOlx4dHc30iGhKYaKjQiOipKJYa1FUnFk3O8yxWpQWFpBcwIPY
jwZu1lx6FBcbuzkElMvQrT4ly3ByQxod0DSl/JnM2sie+aVpS2N6dmbUPvRefdr2WU/sZ/f9Y1LK
mV/YvmlluUPO+OS0y5uWjZpw4IneS8DQgXTaURhkeYcKC8gjb6EXHjLhbxmBYQJm1aYZJhC8PTee
ZwCCN24AmXWtntXunieHLdz/3FG2aP1V44ed6ZHTFrR9dqB3qRHXcokDC/ni1d655KDyIym1cyK0
WddZN1slqdXB8w2JlQAWqyjpzmQnc0x1UqzLU2soDO5RVdU6lV/pWPDlReBepwFE2YpM4UUSqbIG
Afmeve4H02cj5SgLF0HFYQeK2ol27oPstJmJGPvFD2jzdX/zg+87lP0t630tHazfjzjSd9jn94Pv
HRzR69vStQPLunicbvbNk2fRfkIoTl/u9VbrLTq5ah6FI6aatoSGolyIhdEMPSyPFTMpcHv1ENrO
NjENWIyjyOos0tAmqVaLpvWlGQG+eYgcZ/+hW+QZiVzOkdxvcp6lsxcgXNzTc/l6Br7PflxemX3Z
o5s2Pjo31jdR+Uf+vN6/+372fSpd0nvA89DuZ+8xdECaRxzbYIH3Up4VM83mseXZpCRRFNtqbK22
dtse236byaaaCtXCLg0DrzU8lCCd1H7SNC1UBCYAMyuy6qpmthph48CBgCPgnoBCYlkwIBqsUyT8
Pmt6cXtPT91ja7Ol3NQtTb1b5LT5y5OCeewI4mwAnPbu1Zyo6/wdAax0kg/QMc+JLJ8h5EVhPuUY
OZTzBNIUKc+Oemh0aHJoZmh+qLIudHPo9tCu0MOhX4SeDtVClamemLwYpsU4Y5JiPDE1Ma0x7TGb
YrbF7Ikxx0RAxNQuM7aLdHm/+ZD5pPknswbmOHPUFVErozqi5B5Ktg5bkGl6lFMOkzS708422ffb
D9mlTLp8hPDXT5TzSEX9w4pC+ltCgor3SnmZ/RW6bnMHyZWuMZA2dr/MX7WInCeY7ZSd/SkL3t+S
Bp69vkVGRMmGt88pbbjp9pI1vq/ffWjbhvyi26+dg/1WHX120dU5+0trL5k6qvnNG+4peDG3dvCk
pVsa7nzEzaU6grzqd0o12VuFd4KdvyXK01v1Tfo2fY+u6SRf1SSZCtvgNLDA25JNIENyeGY4g9AQ
hd+GVFMRFElhFB8Cd7px4l66r5y/fCij2jiqHS2j5Cec8p1RHvEOiUd1T6SIUI+uWtWDg3wf5s+d
O7X4/q07pYWvfTjP9/prvpTm8hGfD3hqm9BK8gsZchpFxQnewXo4YmihnfzSWc0rFrqngRZmKZKB
snJdtavneaVenpArPBF3ORwZDp5leKiUxox6eqrvhp69s2+P7sG5Q714I9vTO+9gyVh2/Je3+OqK
sboKm72z+dWciWPFSJbIRjGpn8rfYkuSrkfrtfp2/VVdgXUKtksU1aYxZZpIxHnKxdTVwFajLEML
n6BVvJTcgyrKXf57vZH8guyhqMp0GUFuRIuqMrEHfjVKIWl2G2+ke0muPP0KqgbflpsH0XiWNdfX
H8Mo0IWjKYJy4SZ2M99BiP+Umkk7sMIR72UamYkOqMmIgQQj09ZmW2fbbiS6ZqhV21TG31cwVKcp
lmnWq0C5StY0STabsQWkFhnWmOQ1dME2tTjJ9PQaUpj9uqybxTt34+W7dzjH2PCoGP7rCOO/1hC1
IJkHbLp6N+rmRtQaZbTIRKirihH4RNwTW+Yf8QYr+CZevLyKOfviKiiF4D2LpIAkiHDMwPAM+cHL
fB/6Pprnq0ftEKpzMfSLf0Ww23uXkFiuZmt6V7Nr+dmShx5NkgmBx7xTPDoyxRRpSjRJ5pB+IUNC
JCkZ2oAxutNiayhyH8La6HTWUd1isUKbiqpsnZYZgq0hGBJqnpYkt8pMNplsli7/80/y7dLZPu91
WfjGA+8mkiyYacm3lFgksITIRZItRA1kS3QR4kZOeyab2SdeoYufA/xfIgIOoO8iRHtVZfcoyqGT
Agdfmez7+XGMn+7bhRIORA2lnYtuOnpbxT5pQm9/9qn49+gsaUjff5QeD8H/NM3/Rm28gTMy7ioD
lyhmTTNwmSwvSKMQfY2Bq2CHZvGXaRKNtcEfDZxcBFwrcP5XbGZ4xcBlGAiPCFyldhW+NHAZXPCm
wCnogY4mA5chAb4RuE7tVkwxcBkGoUPgJuJiFXoMHCEanzBwmoeZDFyC4XjCwGlOFhyrQDTLMHAV
XKzAwHUYwBYZuInwPQZulk+x9QZugeFai4FbId/AzVwO2iEDJzlozwjcQu1hmt/AZUjVPhO4lfOp
pxg48aYHeLPxv/7Tiw1chiH6JQK383kMejufx6AP5/LUrzZwkqdeI/AIzo9+v4ETP3q7wCOpPQIP
GLgMwwy5RQn61wyc0z8u8BhOr39n4ESvB/YYy8/XFGfgdL4mReAXcX6Mc7yI82MaLPA4QV9l4Jx+
ssAH8vM1tRs4na9pscCHCvpHDZzTb+C4fo6c9XPkrJ/Dv34O/9Zz6K3n0FvPkb/VkH/W0oYVTXU1
tctcyVWDXSPGjBntKqyralravHThMlfW0qaGpU2Vy+qWLhnmmlhf7xKUza6m6ubqpuXVC4bNaqqe
31JVW73MVTjTNWlp/YKzY8928fY51U3NNItrxLD09L6ewplDeR/MgiaohvnQQuZYS9gyMpBCmEm/
U6lWI3qXQeXv0C2DFgyBJWRiF6ZZSLXfWytX1JZdmEJaJz0jvSw9R7+7IAuWQgOsINo64rBWUCXT
iMFUjoAx9IwW4+qorYlomwkWCio+sonG8t9KaqkjbAkMo56JUE+P65w5m0WtmspqKpeLHQz7nT1M
p7m4vFqoNzDvit/k4bdmmES99b8roSDFHMFNs7EC3+8wSKfn30fycUP7xv2eNH5rV6nUv0Dsnstj
idi9iyhW0O8caltClNX0G5xnCT2VYhaX6D17EqmihUuzkqCW1lhM2BLRxkc3i1qzwKqF/Bf+5toL
BbcuqlVSzwpBXyVWrBbrNYmeBQRc/vUEy4hq2AUkznV6kVjDJSibDb6bSR51v9IOvjKX22Ixqlbs
8Ld45rWlgvcgFZdABgwXPa3UVifW5zKoFDuqFxKrEbRtor36V9rH11ggdraUeF9iSKFa8NZi6GaA
62VCBgsMSS0jepf48wjO9VLReyH5uIw9BmXdbEgssANO0UDYQhpVJVr4KS82TpmvHjiBBWK2c1ev
FBy0wEp66gV9rVi/SdBUGpp9vk6mGpKqNjQpKMlGmqla6EvwTFqFFrjE7yKxMh+bQPNxWdWLVVYI
3CVOvs5oq7yAPiSLnoCOLe47ycXG3qrJ/iuFf6gSvFeKvdUTNrhvx/w0W4Rd1PbtP2CrF9IibgcB
W6kSUuVzNvfNF6SqEuObhd1UCws4lzr1HD2pJcpWmEBSOHuCv7XXhWLGoI6dtdnf0qL5vzoH7gUD
elzf115pzFnXp5EBuTcZ8msW1lJj9FX2nXjzOfNONlZvEta+TOhgAkz5lUQvNCvXhTox04VPt8Gg
TaCZa0WkaYCxkEZPq3iG0Zzn6+IwIfnFRBOwgoB35ydfS/W0/0PkrPtfIucUouDyW05z1wmbvjBt
nli7WfibZeJsfi+afknnswj+RTN/SVQXppwjahfuzxdav1x4nd+jO3fHv8OZHCePly+Ws+gilCl7
5UvkAnnM78w66/+QWeT+L5wV8B3gCJrl92h4TwNJ7PekOoV6uS+opIvA/wBiNE9FCmVuZHN0cmVh
bQplbmRvYmoKMjcgMCBvYmoKPDwvRmlsdGVyIC9GbGF0ZURlY29kZQovTGVuZ3RoIDMwNwo+PiBz
dHJlYW0KeJxdkdtugzAMhu/zFL7sLiognFQJIXXtJnGxg8b6AJCYLtIIUQgXvP1C3HXSIhH0y99v
O3Z0as6NVg6idzuJFh0MSkuL87RYgdDjVWmWcJBKuJsKtxg7wyJvbtfZ4djoYWJVBRB9+Ojs7Aq7
o5x6fGDRm5Volb7C7nJqvW4XY75xRO0gZnUNEgef6aUzr92IEAXbvpE+rty6954/4nM1CDzohLoR
k8TZdAJtp6/IqtifGqpnf2qGWv6Ll+TqB/HV2UCnno5jHtebSmJS56B4FlSWkDqROgSVEpkRmRFZ
EJkTWR5CB7da+W/le6O8oGIHypRS3jyotAy/nFN6IjPKWxCZPRFCDygeqTTZ8yN1wG8dUM1tHNva
7rMWi7V+zGG3Yb7bZJXG+/rNZDbX9v0Aak6dbwplbmRzdHJlYW0KZW5kb2JqCjI4IDAgb2JqCjw8
L1R5cGUgL0ZvbnQKL0ZvbnREZXNjcmlwdG9yIDMyIDAgUgovQmFzZUZvbnQgL0NhbWJyaWEKL1N1
YnR5cGUgL0NJREZvbnRUeXBlMgovQ0lEVG9HSURNYXAgL0lkZW50aXR5Ci9DSURTeXN0ZW1JbmZv
IDw8L1JlZ2lzdHJ5IChBZG9iZSkKL09yZGVyaW5nIChJZGVudGl0eSkKL1N1cHBsZW1lbnQgMAo+
PgovVyBbMCBbNjU4LjIwMzEgMCAwIDIyMC4yMTQ4IDYyMy4wNDY5IDYxMS4zMjgxIDU2Mi41IDY2
MS42MjExIDU3NS4xOTUzIDUzNi42MjExIDYxMC44Mzk4IDY4Ni41MjM0IDMyNC4yMTg4IDAgMCA1
MzYuNjIxMSA4MTUuNDI5NyA2ODAuNjY0MSA2NTMuMzIwMyA1NjcuODcxMSAwIDYyMS4wOTM4IDQ5
Ni4wOTM4IDU5Mi43NzM0IDY0Ny45NDkyIDAgOTIxLjM4NjddIDYxIFs0ODguMjgxMyA1NDcuMzYz
MyA0NDAuOTE4IDU1NC42ODc1IDQ4Ny43OTMgMzAyLjczNDQgNDk0LjE0MDYgNTUxLjc1NzggMjc3
LjgzMiAyNjYuMTEzMyA1MjQuNDE0MSAyNzEuNDg0NCA4MzIuMDMxMyA1NTguMTA1NSA1MzAuNzYx
NyA1NTYuMTUyMyA1NDYuODc1IDQxMy41NzQyIDQyOS42ODc1IDMzOC4zNzg5IDU1Mi4yNDYxIDUw
My45MDYzIDc3NC40MTQxIDQ4My4zOTg0IDUwMy45MDYzIDQ1NC41ODk4XSAxMzUgWzIwNS4wNzgx
IDI2My42NzE5IDI2My42NzE5IDIwNS4wNzgxIDMzMi4wMzEzXSAxNDUgWzIyMS4xOTE0XSAxNDYg
MTUzIDM3NS40ODgzIDE1NCBbNDkwLjIzNDRdIDE2MCAxNjEgMzgxLjgzNTkgMTkzIFs1NTMuNzEw
OV1dCj4+CmVuZG9iagozMiAwIG9iago8PC9UeXBlIC9Gb250RGVzY3JpcHRvcgovRm9udEZpbGUy
IDMzIDAgUgovRm9udE5hbWUgL0NhbWJyaWEKL0ZsYWdzIDQKL0FzY2VudCA3NzguODA4NgovRGVz
Y2VudCAtMjIyLjE2OAovU3RlbVYgMTAzLjAyNzMKL0NhcEhlaWdodCA2NjYuNTAzOQovSXRhbGlj
QW5nbGUgMAovRm9udEJCb3ggWy0xOC41NTQ3IC0yMTguMjYxNyA5NTYuMDU0NyA4OTEuMTEzM10K
Pj4KZW5kb2JqCjMzIDAgb2JqCjw8L0xlbmd0aDEgMjcyNzYKL0ZpbHRlciAvRmxhdGVEZWNvZGUK
L0xlbmd0aCAxNjYyOQo+PiBzdHJlYW0KeJztvQl4U9e1MLr2OZola7Qmy8ORZcmDbMuyPCPbx7Zs
DMZgwIDNaGMZbAZjsCGQBHASHIghA2koGRvSMKS0vRGQtqQjSVNK0pCSNs1N09sGMrRpEhLS24kk
yG/tLckYwr1/3//e+9/73vcfe+29zh7XvAfJAAQA1DACPBQNbugdvF/70U4AExbq3x/oXtu7a/bv
/gTQfQpA8dLa7s2Dqoc4FQCxYQNhzbqebkhfXQSQ3wfA9/WtHd687G8taqyvwPdwX19vty5D9iC2
/StCFr6G/+xY/QTiP0QoW7lmywpDZf0AgO8cgP/SisGVa8+9ES4GkGG9pq5n07BwMRrlAFzv4/zb
etZ2D37vse+6ASSPAnDpQGmXAlQdd+9bpgv+DRwKoM+zf3ywmuZnbruLH38zWic/LHfiqxI41gNo
KpsSrSTdChh/c3xUfjhefvX5LSv5LazE8ZeCBHvqwQe9OEgtMdFxpCH4MRvqpzGQfAEyybuwRTIC
N0lbYLPkYcRbEN7B922whXsQYRjSpMpYuexO2CjdgFAFN0l2wxaW/xO28P+EQcmPoV7qg4WS18Ai
XwYWyf1gltwHRkkrLGXz3ABkHyMNdO7ZUMzmngQ4d4DN/yBkIIiJeW8AvXTeyUDnZWPuR9rehzZJ
NxTxO6FfMgj9/J+gj1sDs/i/Qq1kFYhcJczlnCCVFEMtlw+1sqdgruQmhFpsPwTTJF3Qx8+Cufwg
LOW+A27JaixTgElWDGn8H8CKeDL/JMym89wIZFLMd8bmnQw4r4vNXTkexTyD4hPzfhkWSd6AWWzu
yYBzM6jBNt3gl45AJzcV+ZiK402F3QgbEGTc1PG/I7wZA/AgWBEcCHVxCJKDYONSYRrCUcTXck/B
Gm4anEL4Lt8NixFayM+gH2EqT5AfAlOxXSH3NvhQnmEKyFcMPoIabhf8QwKwEK17Ib8H9nH18BCv
hWcQvNxZeBfBy9thGYKXXw0zsW2H5BmYLRmAx6QnYCvtj+PUcv9AW30P9vJu2Cs3w12yV2CAgmQh
3CrRwCDTaxU0SM5DNT8fBvg1aMd/xfoBuA3heDy/D6EV4asItyM8gLAOIczXwzaEHoShybjsI9gm
T4dtmA9i3o9tb43DUwjbJ71TWI/yaEeavsM8lWeeqAEJZ8Q8Hf2QBy1sg3GiJ37uNPci9yb3H4Je
SBZShHQhU6gaH6exCQ5cV28SbEIq1leyehi3jJdd+d6V7185euXJ87ecv4uWnb/1/BKcLR3evC4a
ANlF9sRRHvbA0/B9eAZegc3wb3AAnoDD8EvYCbthDB6GH2Bs+xHGhp/AKXgOnoefwgtwF+yC1+DX
8Bu4ByIYTaQgAzkoMCKpMPZqIAk50iFnBjBi6E0GM1jACjawQwo4IBXS4OvwLXgSvgHfhi1QDTVQ
CyLUQT00QAgaoQmmQjNMg+nQAjOgFWbCLGiD2TAH5kI7zIP5cBAegUNwFKm/G+X6XTgB34NvwhG4
DY7BSXgQXkfqj8Md8O9wDk7Dz+EWeAOegsfhTvgZPAsPwS/gZTgL96JsMlC2TsgEF2SBG7IhB3Ih
D7yQDwVQCFMwShaBH4ohACXwKpRCGZRDBVRCFQRhHSyADuiEhbAIFsMSjKzLoAu6YTn0QBij6wrY
BH3QD6tgNayBtfArGIBBWA8bYAiG4SbYCPfBXngA7oevwD4AsTO8bOmSxYsWdnbMa5/TOqNl+rTm
qU2hhvo6sbamOjilqrKivKy0JFDsL/IVFuR783Jzsj3uLFemU8hIT0t1pNhtVos52WQ06HXaJI1a
pVTIZVIJzxHIJ7aIraGjcVXE3tAV0bhCLr0Q0cy81OqLgNHhdBmEgK+zIN4qIvVGwNQSSW7rOAZi
RWdE5r2+ycwI79b/xYmdWx1CY0Tixl/X9O5wJGdOh9Olf90xUd+JfSIpDR1OpyPCufF3Glbh7/Ru
IRzRt2G50xErmRaBtg4KJ8ffrsBCqHB2YjqnI5KeeO3svBGRz6L5n7qOzJlkTH9MY28IRSD5GGje
joCZNrtUgQYbjOR4kRA9Ymw08EVI8l8ixBQh5lYk+dopaLfzFTeQQWN4lasx3I8SDXddlemlmESd
wpgwNqfDEECUEd0SOTO745ha1eBq6FVhAbACOKZSY4maFuAQg8eIpoYwhNM0Vh3jQJGE4jNSchsp
rIqIu7sQcYVQblhjulpzcvzUnslVgN0SmCmGxYiIyBoi8hgRQn9E7I7AbuFY/qmxPSf1sLzLqwm7
wt2LOyJ8NzY4Bry7sa89ktrSthCLcCqErj6BqjvEEqo8obFPGMN32rYLU1eIKv2a8nBfbxc1E9Ll
CmGdsqFjp/OUI2LEvDFi8EaSsFnSze86+LFGW79AX8fGdgqRA0jupFonTdEIbEj6WKMLZ8PBGlfV
U5X4JtTGrHFamClH3N0tREaWr4rZXveehP07x/QRzd+dqB3UD/ZkHeOiDHetoiSv6qZsNq4Sxnb3
Mlb3MNbQXoXGVSEKtCNaP8zD3gs7GvtcjVcnRMYR4d3X93U6I3Yv7Tg21khJ7A4j9TGSseIq/dQn
HF6C9DRExHaWQTvTAc4odoc640XxBgtpN1rTFersdMb0jk0jcvdOaaFLGKMjyt2RZK/e+QLWnSrI
b5nT0RhyMO4jXENH9UWb4yLiLW0TxcSGbcZ8Fx0xGbXMdbXMjllBXyLpao85MDeheWwab89GPWtz
nI3hizuaXE1dY2NNLqFprGus++T4yHKXoHeNHdNoxgYbuwTm/gTLv7/bEWna0xnRd/WRKqYhOpxA
ba9pTkvENHsRVVWT0NcdCxy1LmeFw2mYaNP2X1XHfQ6tH32A+tyY/iOkTYPRySE00VBzEiOEI6Kv
oC6LBM3rQJ/oYfbLEvSVuTi4g3oN3+lu7J8bFxZaZtx4aAycHS/FQZxO6k+7T4qwHF8iI7M7Yu8C
LHccB9HnRT120ZpTiRrzPFozkqiZ6N7lQr3ZWub+D+x7sm2PGVxGodLH5M9Cbzhyqh15/GdFRFER
V72poYN3cHGMc/AUU3kxlAUjVi/rSGWCEXNM7xLOuSJ6b0Ta0HHKEewU9AYMdQTbNHupB2FEPed6
kdA4Csn6CAlGiIWWA8ZVFt55awVWThiS0DjWFbe0yWzFF4Nw3415wzZ6F7LniLU3GF2Uw5dZeItH
bXcT9SuHM9ZiemdES2NzRPsRS5BeR0OHgJEIPXc2Q4RGoY8qOyJ0hVhI6HRMLj45fr4rREMgkkyb
OOImjmlMtNfaWkH+v2roI2jot+3p7KvCUcQ85EAoxWmZt7R3xKVU4Yh7FJ1rGmXl2voJKSbaoPLR
8ZyRopQXbWioKbaLnTcSeUv7NW+TJmN1FRORob0j0uRNDB57n+p1TH5tvq56WqIaw8dWx810GeGg
/piL7Jp9TCS75i7seFaPW9pd7R3HOcI1dNV3HsvCuo5nBdwDsVKOltJC+iLQFzxh4GjHOQVr73hW
BBhhtRJWwN57ThJgZYpEGYGek1ysTJ8o47BMEisTWVlsV9Fo60MRdLhQ6eGI2NZxa2ffWFcnFTZY
YgaIlu2qgQjnqjlGOJkmonL11kfUrnpaXkvLa2PlMloud9Wj+aNzCNTVx7pc6P4YgDvAQTqpCVNz
4dzCyfFxjKBnMfI6IzL3YgQMsEpvp4BWPB3bTaXQhcVTIyM93ZQOaqY8jeXTejojiokBscm0iBJH
UMZHwBZNrA9dBbBTDxprt4uhWIzOMdIZ6fTSSTv66QCCgPuhZldVROaJjSn10Il8nWNGVzFbTmTu
iMq9k2ZKpI0GQlbiwFecrDMmJLkGKe9xYVVPl4DSlkDPXDRGiYf+qhyxkl5c1SWeXgYqR7wSYh6k
TlJFlIV0rZIzXF2IA+KvvLMzRjx72xlvgHPrI2qkyDNJlPEOKB2smkZpwd+dSCpt+hwdZvZJmOPa
jD5IiWYjybE6kuSe1o0BJ9ZfjSWuikRnHEvBiugYL8RK5ZRzDdvQtp8cP+La4pz0FOS7cHXuoIYJ
DtxDitA5dn1BZBEGTsX1pUmseGxMkXTjDjF5KZImclooNPaHCuhdEQgk+ozSRqYLJ8lnCeRyAvln
AvlHAvl7ArmUQD5JIB8nkIsJ5KME8mEC+WMCeS+BvJtA3kkgbyeQCwnkfAL5dQL5VQJ5NYH8MoG8
kkDOJpCXE8iBBHJvArkngYwlkF0JZGcCuTOBLEogCxNIZwLpSCDtCaQtgcxIIC0JZHoCKUsgRQnE
l0AKEkh+AlEmEHkCkYrjDPsrS//C0k9Zeomln7D0Iks/YukHLH2Ppe+y9B2WXmDpH1j6JkvfYOmv
WXqWpS+z9CWWvsjSMyw9zdIXWPo8S0+x9Ccs/RFLT7D0GEufZukhlh5k6QGW3sPSu1m6h6W7WTrG
0rtYOsrSHSy9A1OxZrowwt62s3QbS7eydDlLZ7O0jaXNLK1nqZamy+qa+Q8w6o/wf4X7EA4gRBBO
IZxDOI9wCUEBPkkAahFmISxDWIewHeFehMcRnkb4CYIKMiQl2LoEW5dg6xJsXYKtS7B1CcjhlxIX
vIXwCQIPOkwzEGoRliE8LnGJLumlt0nkyqkr3Kkr566cv3LpiiSW8afGz42fH780LhmsU0ncSPYp
TM8hnEe4JHGLGsn5H1/6MccSXZ1B4sSBnfTuluvA1jpMzyNwOK2KvksUzxCdh+jqHBI5e5dhup2z
sraPQgaCD6EWYRbCMgQZvIXpJwjj3KPiXP6t8xZr6mu/weSWWy2OW261v/orxDfdhMnaQUzWrMNk
9YDFsXpg+4aU4Y3J5tSVqzBZ0Y9Jb1+yo7dvdH2Kfchyc4PduQXBXufn7oeHEDhIxTSfYtxD3MPc
I6Dh7ubu4e7FfIzbze0BDTi4h2A3ArKE6eMIP0D4HYKEO4RtjkAS9zj2fQLzR7Hv1yBp/H3unuPJ
rspnEXmYInUp3O3cVlSxl7uNuxWkmG/jbsZlx8ttjec3cwtY+U3cSpav5BYcl3qFk9zgcYdQ+SNu
A9bTdgNYLqHlC074A5XKujpuPdgRjmL9SdamH9/eROx9BJ7bwW1BiXq5Ecxp/+2YUzpuiedbuPms
fjO3AkO1l9uEOS3fGM+H4vmKeLthzIGVx/J13Pzjcm9uXRu+E7iTptwSbim3DEU4m5vDzcV8JjeL
a0NRqrmZCLNBxS2BKYh3Ir4JYSO+P4Lv38H8t5iruH7ssRoF2oMj9WLehSMtx7wfglwPQhfCEoTZ
CDMRQlyQSa2BM6CivLiLir3X4DvlupozoNSa6sxYTqAJ09MIHDcF6+VYX4k55a483t6J7eVUyoHj
JktlnYXzxSsK43kB5nSC/Pi7N57nYUepd2pdPb4TkGJ6iJE0hQtAC0IY34ZpW66e07Op6zCnI9Vi
TkmvipdXxPOyeF4az4V4XhLv54/nRfHy3Hiew+mRhbG6AXwnkILps1wxsmzlbJwdlaLmNFwS5gpO
yamYchQIahS+FalVoHLUqBw1KseKylGgcqyoHAXWu7CHG5WRhiNlYJ6CI6Vi7kJFpCGkIFgR1AgK
CJK5pJVyRmbG8/lkMZUVmRfPF2BOy98kr2Fs85I34vl75DzljFyI5+fJhyz/BHPa/iPyIcpaxJX/
uFKFznaKSI77/XEEnebk+Klnfp4hVGIL/nh+fuX3CU9QFMczMl3PUvTEqfR0V6IwLS1RmJo6Uehw
JAqTU+LYiNoUx0SlCjGOkBNi227ECC1DrE6FhQCzIIMW0RwJguNt8xhlcMLlohTB99LSK8X3HQ5G
5p+y3JXzTxKFaCK/f0PqnfJ6y+ucGFEnVT53SurFBmL54yZTpfior6jy0YeJ95GHpd6H90q833hI
4n3oft4r/izfX3n/Xt67a++Dezllj63n5z280JOkw8EvPTM1w135i5NEJaaSB/cRb/nXyFf3cV7b
fk9epXU/0e+rFSt/u4/8kJSRfFwvvKTo+FmJF7cJx1+mWcHxszxm+bTwh2QGmc7aTD++Xep9liwi
7ehXujo7aUd224Ejd5JdTDk7MafKvSue7yL3so73YE7f7z0xKvXW1mnIASDkFfIyq/wV5uiG5FXy
8nEZ1az8eHFxJc2e5qkYTvwhnalVNPyHLaXyxZd470tnJF7xjDOTlp44Y7ay/DRKk+WWFNba9ZMC
f2XbbJTTbJT3e8jWu+/gyzt5eZVnX0YLerk+xNq/nJ1N8++9bE2pfP4Dglwrj7/JJhYDH7jdlW99
QMQXHGmVJ45JvcdQMeKp6urKU09LvL9+Wup9eiuG6zeNlsqf/YgI9xD9PYQOubusgg29O9vLSCne
jWPvuVvqvXtM4r1rTOodQzn+9RPe+5dPpN5PRzjvpQMS7ycoGvGj4pJK8SOcjXY/MHtOLG+cGssr
gmw49QFU/FsHyAHsScsfQPun5a+NoHxu206825CqrTjFRYQ3tpPto+6MXaPEuxNhB85yB0LuaOXo
tFF+xShpGiVlo8QzShzlZluZ2VxqNpaYdQGzptis9JtlRWbeZ4ZC8+XPdMLlosucJ1ubk63L82rz
vbpMlzbLpUvP0AoZOpDqpVywWqsODgcfCvI6vUGjVKk1MrlCw0ukGlwgNDI+nDGYR3R5RK1r0WGk
mAIhfpj/JvxOJ1ODmlfrpsAUZSe/SLmJfwQeUT6k+y1oniVqohHzdA6SlmSTpySZ9dYkoyQ5yXd5
3eXHLx+4/MvL5y7Lai+Ll5++HLl8/rIUThL1cd9l3/eJGmqJWiyUfB68HPxH8G/B/GBeMCfoCWYF
M4NCMD3oCNqC5qAxqAsqg7IgH4RgW6CdRIwt0NJeHzERzOfWRwLelpO8MCdS7G2JKNsWdRwj5J5O
LI1wu9Cf2yOSXXiwb48YGxYu6jhJ7LR6FA9JGAQiLV2jd3d6vWmRML1VGknrjBRT5L60TmiJFM+O
OFz13hs9Q8MbE/nQcLwIf9hzLMfTGMlr7I7kN3aFvIlS9pAhfGLt470m8kkPjjkxzw1nn1xFM8Iw
GKaDDdOS4eFrGt5gDtr+v3hjIw5d2wcSDMebDP9rfb5E83CiXcQWqUXdXd/gmJIqsW1OPb0EbomE
57RE0tsWdUVSXPUtkTP4Vta2KKJx1ePYQ7FnmP5uHKKKiJUdA66h/RhHExkmixZ11PWQKITJZwiX
Ef6J8A+EvyNcQvgE4WOEiwgfIXyI8EeE9xDeRXgH4W2ECwjnEX6N8CuEVxF+ifAKwlmElxEOINyL
cA/CGMIuhJ0IdyIsQliI0InQgdCO0IYwA6EFYTpCGUIRgg+hACEfQYkgR5CK/eG/hv8S/jR8KfxJ
+GL4o/AH4ffC74bfCV8I/yH8ZviN8K/DZ8Mvh18Kvxg+Ez4dfiH8fPhU+CfhH4VPhI+Fnw4fCh8M
HwjfE747vCe8OzwWvis8Gt4RviM8Et4e3hbeGl4enh1uCzeH68Pa8A0N5v/2p/N/zTTSu3HbAtJ5
oAdv7INsiRXxxIfaP4zheLh6jKaJ8uicqzj2PgZJfDUk0VE48/gl7jzoxw9MbvHlhz+fmEURBwl9
qYet8QY9E/kgy+f/d6PB8/9t7Y2fV+BF+AHcwfAfwgn4Vrz8W/AdGMURfwib2Xsnbod2wAFM27Fk
IUyDebAU+rFmPRyEQ/Fey6EL/PgDUIMSHYuXvgTvw3fJF+xz9uufr+AsG+AkzvQITMfxamAvcvsA
fBMehxa4E9+uPq+z9DzXDatgCI5ABPuGoY+VtsJt0AyLkbYmlNJ6GMDZF8LT8Az0wjF4CMt/CHPg
a7Ifg4Ibppoa/0+uavw/YTf2/SqejW7j7uFHYBhuha/BHwAP/HBv9Pn/Xnv/wnMfPIhc7IB7UKcL
+Wq+je+a0O3/6Pkeyus5lM1m1Mph1MfX4D7ihodhJ2wlGngMfkiKr5HO/8zzPdiDY1/7/BSeRbkd
Qv3egxIbQr08hdS3Xd+V5BAV2s0qWEi08Bks+79IyY2fQbSFzWhxt+M8G5DzDliB1rUR8z6EjRO0
lJEa2IVafxJj4rtYXg/bYIA4MVKehl3EBjdj+8ew9AH4PinCtkPwDMmByzj+IuTySw/GA308HgD1
S2JBP0Hf5D+j7/wHiXiQSEkWnJkcD4iLJKG9fQ+O4vxfh0eIg/DwN7gAUeIjqai5XHgV4TTK7fvw
HMrvI2xhg38n13/T7ga0YI/d0l5JvPbLtKC1331NbLoNPeVR9K+taEPPoK8/B/fDdzHfg28H0IP2
w7fRBg6jLY0grVfnXQgBTFfSlMlACz+Nxyc67ylaPv7q+Fk279lEr+g9E/hv0Jt/h/7chrHifz//
+/lf+HDyL96RvsVNk+qkZPxDyVG5JLqI/A0rDqHHfwXTW/Bn5Y378lf496VPj38s/X60XmqQZkXX
R2/Ftezf4bfwS/gZvMO+qfYS/Ikv4n/GX+D/IumSyKRnpV+H70gK4Sb46vXjSQYkfZLZkoOShZJC
aTa+p+JaNQcW4FrVhevlaoxrieejawH3ksBhzmNskexAX3wQQHYAQP4U+iOCUpgE2Eb1BoD6JICm
HSDJFgNtEYAuhPAFgP5UDAz/HwKTCJCcA2DGwGbRIPwVwIp827Eu5RyA41aA1HyAtGEEjGgZrwEI
2Mb5KEAmtnHhfiVrF4A7AuDpAsieAZCD8shFPA/3TF7cHeS3//8AkM8ClEMB8lqAOi74642hENv6
0Hx8j/438MaNoQjl5Vf8vwyX/h8FCf1euuROaTvkQD4UQQm0iG6zryQnNx/y09T+wpJ8dWGhOr9E
UloGud6igNFk0tpshX4eas8W+/C39vevny02GIm10oeP/qz+rCGgP1us//1pfxEpLanhymv40hKP
K1PLyV2lZWWB4nTOnIwvWt5stppdpcTgNFDgymWWvCyrx6GrqxGKsuzKruBdDU09Nam6rGC+4DHL
jfeRL67I+O4vKsifLBZ3Xmm23ReodLXMSc4qTr89vTAt0JTrqaluKnDmZ+ekygaeeCL6ruThz1dI
/vHZt5BB4ECGvP5Z2gsZkAnbxJBC6cyUqlVCpjbTbssUnJm8VCtNycjI0lpNCnVmsqDiVXtFnTBL
4Ay8INiMJDmdNxgNh0Ng0cocUmOmTQK1AZ814DWANWAwVtp8y5YuSWm96DUYobKyiNh8gYCxEhOD
0VppCAT0O0+dOkXB7yyt4VAs2dlOuUxmTrZYzU4UTjkJkHTOaiZOnk8t9tv0One0MDNFX10bnVcx
N5s88TXSbnOXFHxxgnz9x36VzZuVOct/2/LpMzKCFUq/XznYJ5n7+aGZcwrVfi6VG6XfP96CPK/C
3VIa5EEZDIhTLOayvLwyvmyvmKdJy9ubU5RWwBfsTRPTyOFQmlHj4T17NaJGfTik4Q3bnE6/Jc++
ze+vyPNul/ouFCM3FwyVNIVaL6TY9Mgs2CZQxH0T/PuLApRLQ0khl13qLLZYzMkymdwcy118cVkp
1rgyZXKDwRIoLsNXj8fl2lKTl6SyerDm8eeWNqyZt2vPljcfyXrwiYJZa2o9t2ZMW3jH3rqpD9z+
iF+f3Tyd726sdZmT/KHR/gUj7VnK3G9u2vWtVu7Tr+xpXFRmlXBXPrsyIK+/rbt7Ww0QuGn8ksSI
+hdgUNQn67Xm5mSdcZlxnZE3WuHk+CWxCIvQUNq4Lu4cJ1HyXLpVy2v3ilZTuoyX7U2XpBOZjFMR
00HOaMxUbUvxXaDqvYAOUIm/UMuEkcJkon8BbaHSq38BE3QFg4vxirZvZMyWBwwohEwwlBizAsUW
ibHHNn1548onFs94YM2cvqlCz9KfbYpGv9hJZN9d9LC0IvrhgpX5d0Uv/vSF6Id3+1b0RN+220kH
mfc6qY+YqG3jqVTyGurZgSf2KlFwpPPpex2iA5XqMGo1h0PaXD53r5Y3bXW7C1K3yxjhFyjBk9XH
NMZPaIx6KieXoYW6spHoGklpCYeeLN9cmGNRoY585Ls/+vTwnNbp4pLWl45U5sxs37Fmfpl9428e
CFX7NZZMsZHvbqrNRP3M/fqnR74RHV8ww5+TuUSSGly9+2jvL4h0M90+E2ajeUh7Idz1LOjGT4kt
Sk2zTpWRYbVxnBJn4o0ilhite0VVYaYKbTbTdTiUaeNte8XMwoLDoUIlr9xbyBsO6oxGGznIcTan
cDAjo0hl254dN1qWMGXFmWZ2GkeunPYyk7X5UIs+/em4wiQupyGuK6o9l8FZXMOXB3jnVbOWCMt1
QmZuRXb0hdfzi526pUu1mT7f66TcX52faU3uMX2xPG7P0nnRX/mnF6err/zVHhSjI8HqlCs/MeTW
Tw1Fn7jGlmFCJkqUSR7sEueCVq8VtAe0Ea1UyWuVHKdQKi28zpBh8BmeNvzEIFUaLHtFUBIzr8xL
V+5VFqVmpGccDqXn5R4O5Sl4xd48XnfQoNW6qHDyldbtrhtJBMNYgOYsiF05vXRJXCj601gSEwl/
vUiSabyaLBDlcktuQdAf/d0rMXnoMn2Fr2iFspxoaJIkQu35xivn00JTowtDjWnRzcHmPDNGsC/L
gfrsg+izBXCLmJLj9rgx+nqIkvd4NFyaNI1P2ysSqUlHvTcXvVcH+jZ9l/6cHr1Xr9GYefNejcSs
0Sj0Bw0GrmC7IPjsWxUx669kscwQiLlt3F9rAyx+QSAezSnqL3LLsyd7q/U6by6loQs9xoyLmqRs
5rS6exZfGYc9RHZsybf6exzTV85ae3BR64PrNm0wFZWTB7KyTHKpeWaOhywi839D6r9tToleXNjr
3RP95LkXoh/cvXJ1cGFbvtbv12QUNtRM2INUgvZQAUvFIq+O1+0VvS6rd29RkUxp5m1W2+GQwmp0
+0v4zGKXK/NwyMXD9vykpCpd3vY0lM4JHWlN83mZ1qnGKV8Ga8BWG1u8Eg6BrOIil9Co80vqZSxi
eYJfziy5T6ZNdmdHl5TnG668pjTnFkYXxRVNDuVnW9VcviFnCnmyIl//WVWVy2JU+f3azKa55Mno
koaaLJvmWq371RZnfWP0a2T5AjFTj01dTXPi/HMZyH8KZIlGqUKuOBySm40m4+GQCRnV+OIsxYyY
cXEDwslRRt/CBH2HKX2f/ZdUJPxQj/OmQ7OYDUq9ktPwSqUV1BhT1bi+7hXVdovVcjhk5VXKgwqF
ANv1MfMqTlDEAk3Mk5gfuTGMSK4NIzHqvkFk3qpcZ7ojuTf5i61Xhei2aRarzO7gokXRgWvJ1JiE
+mZmHxvxLETvWstghTilxC4qjc12e8Ct1mbzWe6sw6EkN/gD/sOhUquDD/B2W4kNDaKkJEN20WIt
5Y3GihRHgM8Y8fouWKmJWAOUB28AnYNtb5CNSbscL0qYUEOYLGVjuYvgj8Vo/rLVEOKUJVFhM/kv
q8zXK2WG6PBQ9D6MXazsKwl2e8kycjuZI81iKvji8bh2tFlNs8n2/aS08gsn/0l19NQ3ovffQHFf
BPizMXmMfyblUR4l0CBmxeKGxOrRJxWXFB8OpWpLePMIL7HyCkWZI7WEF0byrzKOezrGMvJ8ujhm
TsRisQY8XGnpJCdwEfQByq75S+zyj2b5U5KkCoXZXUj6CtxWzdYrvy7JNxnksmuZreTSggsrqsnq
+3/VKGYyjSYL4rTPH+cPL2jLbo2uPfPyDZik6z2Niz/FuKjH3Uy+aIVkPhlXAJMylU/dq5QkbbXZ
Mg1bpb4/I0t/nrQv8RdJMz3ISIkRd+JIezInI3ojhjBjbG3Xctw9m392d+uuK0eO/+cte8ajSSe+
tfbBGZ0Pr1h427xs/awjRPKdt4h45LHoL3/3QfTHB7hfRM9GT+0mmhNvkozb2x/5D0ob9ZkK5jNe
aBTdqQIv7BVTUzHoxfyWeS3dj5h467asrIIM5sDFhqs7EubFzNQmgtJ1Ii620FOEKzO7NLZ1pPFY
Tr6R5Cj0R6clxHvpg/eadzzTs656eP1XZhbOHqzvKb4ypSnXqr5Wnie+13d4VaFk7pS71s8fakqT
JHj4J/LggyB6VGmqA/x+4P0oY5giz1LipuhwyOmRJ5sOh5Kn8FP2JvN5GRkOj9tBbNvKy2vcfrI9
CXnyGeKLjDG+0FDm4uY1wV98t0y+7DeUS7ZltlpZFVpcNq7BPK7B7PyAGiNH1RbPpJj2yQfv799f
vaB0YXZFVVH0Q0/I2ZET8Pr9A+sXrFlcXrdjcCE3O/qt5jontbbJUjh64q5TZQr7kuUHm2fkKPyl
N9cemdGcpuaeuvJv9qati5Ztq6d+NTh+id+HdlcEd4o6H91D+wp89K8u1RILXYSDWGIx4XJqE2wj
NomWt9lS1VlZktQCCS/ZKxaYTNRCTRLbwVlWYrXmCBd1uqKci3J5MRwsigXO2BnDt+TCJLulIjIk
1mRjpZfu02juLzKlc3QFpgtSIYqEnjAn1md6srJYYwdONBXDa8mhNfM2bi3ZtGXjrob+X9wxY+/a
HmvT0pa6lcHAmlUjd8+q3/hk92NnSXnHCv/NG1tWLAxWrbu9dfDQQn1q9C8dy7OLuhumLm8vEQfu
Xtq/d1FuKTGyWIOCkdyKtiLAfLFAZzSgeRt4XQZJ4jMyDEo72Hk72g3PHeS1qgxbfcZBQXCqtqOH
Og0Jfr1E3/qXC5TZyZuPQHw1MznZ1uvqbktSaoidqOslVcst3qLy8u3M8svxGGxSb/NVl3hNPbjP
Ojg/XGL5AuI2L9dbs2qCEjBW9rdRuhdiDHkT6fZDiZiqYF6qMJnyCniLGRc0r5n3H/B4AinbtYnT
QmwJSEQSkoxnAyrYwknLGMeiPzPPyZuE3mSTx9X3QHjLt9cXq0xZfnIQ9wO501fMaFo1NcWQXU3u
rfLqyRtrZ7VUlUzLK7vlyG3c/TPLBWtSbAdwJdi9Y5rTH77/Fm59bF+gywqxfYFl/LK8C3lwwzb6
t4TnRBQ4mWEuoqmRpXiyOydWKkkrFpJWI03cRjPPGdV4SFIoMSCZUiVasGXKlbw7y2xOB44YjYpk
PFYp0rMVuPul/sscmLqsYWJNpJKwonZin5kSXPwKecpv7EBvwrO8idplbL2QExf/7eipr0d/b0xP
dznJt2r8Rv2LpP4pIv3IG5hCxtKznNkp0Qfulcz//ElJTWi+3477YU2R19VV/cUHkoHP93Kf755S
XYa7J5Xdu3DG5y+yi11oQ3+M4JrngWJ4/1kg4+8/o9Mzpt8XVRTjCkmaJOfk+HkxpNQ156jV2Xz2
V8VB9Yg6oj6lloBar25T36c+oJZqeLXaXkQKJYV84ddEicWddSTkNgumItMBU8QkKcKEM9Hv5GRn
5zdLTMn4Zk8yp5kL8NTBm/V2Pa9/0K43JScr0keJ2sMX00mVuM0oLi7JG1XgG92EKnATSrcWsR3G
WerjaONo7LgDX+9dsr52wuUhkPCD9fF3L9s/eb1uthv3eEpLstyxKCiTuzBsBuglgyG2geVj3s9W
B+5J3YKH5s8YriFO4syZ3zxzme2OrpGR+p7NQU6VnJ0f/Vjzi5cKm4pC62rulXROn7K66f7Hk+r6
NlfMmXN7sc9Re/sd0YPTq0syLBo/OcP19VfW2+tXFDP5F6H8L0v3QyqeXrtEdz7JleLKtl+U6nEf
ZNEnuZJcvGufmGRJsR8JpUAqUd7hoTJMorrxeIr0hYWpoyZ2GqNSQSernRzzbLW1E8JAj7PGeUxm
/GfLs9Hv0ObwNIZMx8IgjQtmskTStKRnyuqH5vY8t2P6Hc1NjXySNTvwlylaZ+3Mos23rt9Q2TbL
zWeQafWutW9+7ckLQ47Mar2ktmtGabpRWaL6/NXWRcFi0wsvnP65a3pzIfpZP/I5B+3MCVvEkECK
CBchhGSMmKYKYNQbBSOvzDASnZHY8bDuyW026mx4SNkv2iwZMl62T8zQ6/Uqo2AyuTj0FNUdDhbj
zyLPKfazVM1AQ9/V25PXqa434EHU3noxxaY/u2Q9sm+eCOss6JdbtTyKIR70+enbDcX1/qY1tbaq
rqmNN4mVgZmdCwI/OjP40o45u/lDr9a1pC88OTrv7nBFWai+ojrX9PnFB9671RTzI+RP4kU9ZuIO
epVYaDiq1+uOhPTmQLLP5uN9lJHM3IwM1C3lRS47EpKDgqhGjcmZvIsqlBq6y1WRTzmL2/eXdJnQ
JL1xselb30OWruoPI7vcVZ5NA6pnYh3DamQYDZldv/CSuBplyd6yj4IaXe2S/uDB48M/u6V+TaXW
WdHgG7lzYDC/qqLKoZ2kzJtnNuTY1SWqg5KGhpzLHx58b9Bsix6buVTMTz576tQZnbOqqMaPMuhD
HT+AOrajlm8VGwSTJd1p4A1fFZ1OtQWmCm/ZP7FzYNfbBfslOx6w7RaJhbfsx1ChTufT94lqrLHi
kug06u9ISXEZd8iZKD41Vj7vM1ainmPr2yQlM99GDce2QhM7IfckIaBcnHFHLudj94X8iLh6pPWV
X60+fVvvPfN8/JWx0i3dc+6oWy3Law+tvEV9tGGG9x+f7nv3VnHdN3YZNz2xqLqRzFtz17RDD8XO
0rNQ4X+SPgr5sE4UVHKF/EhIYdYbUd0W8rFXB4JeEIRTwjlBmsQLVLf2THezkCamZfFZX03DvQ7n
PCQIXm7UpqNfVdSTVh0eiT4tPsXYZbsWarLUgmtbLwaK2RVb7BxxdQnncQnHhby8Bv3WanbRIEav
xANczydJ9tyC6Mp8j1m1xWO3GpIkyuqNowtnlfeYAoXOAo8j6RN+wZUnG0IuM64G7J6NWxLApTgl
ULh2V1e2+jtT/EaPuGxGP55Pa6N1/Nuo02Kog7nwn+KCeuec7GyVwqco4xX7TpURXVlGma+MV5aV
+XRzyBwR9MSMsUmnz9D79J/ox/VSF6/X+5oJDsHDx2Kxzt7MN+8T7am+Wr52n0+frdJkzsiiYspF
SWRlpTvr62c0CnoTmdGYnt7OKXP8krwpO6R6dBCp1BwAmDeDrgxqHbaYYTbPC+zIY4I768XEwKIg
vS6nBXTlRQQrzhYXX3O9mvClxK37egwVZ3FH6EM0saXGOrqtzpaziIkbwNiKcDWCsg1jOV1HYimN
rlYnYd4W317LTLKY+8UPGa5M/u1nlRlZLz47NzgjrSF0adWdlWte3tV75Ka69lZfmTi7uaWyd6yt
eSpZfmX6iq5Ac4G5eH7FsrA9ELj3KwtvC2mzm6v2zeYXyNUZq2uePGauqnB79PXrpi/9yhxb5ZKm
2pXZpunFlcuq8+5bPH/73FxD9NzWXdmhTn/HpvJtX1z0zCtbOK9oYTC1NM8es2U8j0gyMW5VwWox
yFMZczmYEJoATfQmL5+Tm3MkZMw1C4RdmdHVqaL8SKgCKolm1GYLgmu0KG7JRfE7omuCFwtZsS1P
bLsTW4jS6Q2AxZIwZyav+AZwoiwW3shaycxFnYHy+XW5ybrsKdFN2ZnWJMesqTliu1eenOuNDlNr
Z8Ht0yAuS7NqhZTS1tVzojsX1Lpwt6cxCg0hIhu9uym1eYY3eluoKtuujts+35gIdDSOz0Wh/Fka
QlO1wwIxzyqxS46E7OZEPNdxPYM80fFv8ZyOX4YZz5M7ONMop4pvT1RxOah8Xu8LF/QXwLdk/ZKL
8Xid8GKzq5SfuCenwZsJgWw/uSLbaU2S2PwFf67WFwSim6Wh55//7CJSX99EnhFn+qyKUuWV0vkN
riQab6XRRrKR0WqFpaJfrVAoeeWDoiLVnHwkZDlqRmLF66lVCEqlzkZ2cNbRScHnwmsXDLGlFI+X
SHDKxdr3JmkvRrKJfvySPYlusvF7x6vuHcmsqcuzyJLzyj+oZvT+cs9TG90dNm9lVwv3p5mhbJu6
VMlsrRZtLYi2JtJ7euP4+1ReuCFkeTI9/FUjkldYLVgdUnMWnytyYAROg+dpnT3Vzxf6Co+EHD6z
TnskpNPVVB8J1YBItAazPUsKeaNlcXbKqAVai+P2RyFmeYmP185aA7GdODNFEiguLytjv/G9NjIp
J5b4J2rsXJhN/dY82VLjVrlGcJrtwfJCn1LhziNPF/aV/5EIxbOLoiMpdnVmwU2ZaYKjgipyqDjb
II+bJ1cgV3oD3qAdjwqZMr9fKZa8Gd1VX4uxmDck69KKaw4UpGouMSX7k1KzG8omW2hcjuQ/UI4W
KBLNEjxEHQlhjDEdCSWDmVgIjCbFRZEU2xDWXl1A3Dfi4noKP/tv5kb/kC3jX4YueFucr1ZQi6c3
gUoBEwl95WnC0VdCE6CJIiCzOQKz5kjLSsuOhNpSSs3Lji5duuRIaKmOKHO8TdIGWQPfsD9JplcW
jAapRSDxNBdpQAoGO0yjOidpeAt339TNsNJJK9VY6XQu74Lm0Q7KsYG0dsTNif5bEbRdB7ohmgON
SF4vxni2tfLSu9XAxfgRLO6agYn7ycSJjIUpnm6jWLC6PjBJbhCsJsr4q2UxV1mnDbY21zrD22wt
S7orGrobMlQmT0H0JhrIlCZHZqEnp3F21tUyldmZWZiW29zikSUlu93RzR6nTUMjwwfVfKYkWO3W
L142ozk7e/bNK6M7Z1QJVs1ElJu3rt6TqhdmtJZEv3JtTedgKM+idjfNyI/eVRnMNJtUrGpScEno
WOJDHQfhJrG6kKqggK4E+TTx0sSeGuQ5wuGBhJhzj+bkZB8J5ejyjboiumUv0peNKhQ1+XnJo5l4
dKbayKR/2aM3kBmZvoQ2LsQPbpMUMGl9cF4v0MlWywQqv7qCoAIkvtiSoDA53EXZ2U3tHhY+E9H0
g2q1dvqiJSVl8+ryzIpkjy8hkKYN03LTDBkzphdFd8eM/lpxPClpEV32ktY1c6M7G2twgsRen38d
90RJeGqbLmYA7nH3iWCRp/Ap++R6i15NWi13qAQN+oYqXYuW+B0s0d7BU9vFQh690su2Kd7rb1bj
+3a6u7h2F8Eln/vd0JmR1/9j4KXorjtublg6JaVusHnLbfq/XTr07rrLfz787nry2Su/rxvYO+sr
zy/6VexMMi06R6JGPeZABdwu5tFLRzx2OMBT6MEj+j7RYylLCWQE+MB+PJJYj+KuBpcNXeYd/vha
5mcHTfQiv78KbCl8BVsyRCVdM6hV6Kg2rTHfYp/nMz2mJPR69dwSjz3mLy/s8piHxQ+kfOxcVqqP
HUIHlVZvUbQvq8CmkGis2QUfVifpappbp+YcOhb+yY7pm4tt1XNDW25+r2J2mzP913Wi20ZvN8y5
TVX8wubqnBSjkmqwttKj/8fHhy6st5NlXX11wosvkF2umdPyYjLqQxkJqMt08MMi0ZPOzJo4ChV5
mjw+b7+osViyTCbcuO8z6W06q95iH1X4E+c1vz+QfYcudl4LXKikofYGR7XYAhpj+5rTWbmVGS+J
fY0hcUiTCNG+Iq9VWbZkg3jo2NArO6duCDaFlNaCrOg7tqqZpbfdtW5d3pTKKSna6By/yuaurSed
1dMK//7h4ffWpwnV+s/vmdKYY1Hxry5ZMTXj3I/wfJZZ5cPzGfNrvgB5zYZeMd1it9mPhGxmekvj
OerW6YgGFHoFl8wrpCMauhob9ZZmqYbXSPVKhSI3mxhH0+P+nE6XWHrffhZqz3rBS08ruLTislrb
+t6k0wrz0cTh5IZujHGxfOnaxirfeluZL2tqvR2319G1k2KdhW9ozZP9scyf19ZUFP36okZBea2T
soWJwFL0SRXy5oeHRYsvpTZlVgr/kxQCKfoUAf0yxZNG/wpNbDZamn0EH6lHs0lzp4Zza0o1HA8a
vUbUtGm6NFKlVJNWaMZd7j7RbCmU8tJ9hfqUQ3Z7XjE5BCih0czMgGI0b+KamW2crr9qRmEsW7Ik
duG8JHbZvGQDPb4lNH31Vhn3HAHLhKtPuoPmxrsswRnlbcs8bb0r1tWWLd/Z1v61luWOVUuyGsuE
nPZViwZqO59aX3/LEu5CsDG1pa4wWOLNn748NGtNKN2e/OriuTpXsCAglhZ4mpc3zNkiJplQTu7x
S9zzkhMYuRaIfqueTxZMosfXbBI1umaTfr/Vwql0MqLhZXJRBbjdUn0s15mSlcp0uVQ9muK7UEnV
/jq9diuOnVKp3itrW6+87vXi9pFeqNPvOJidZqchccvCfBuPq+7iGley+h7SEP2RPr8iP6cps2Dq
9tBt2x7gxxQ5tcsW/aM32tA9VJfqzChrrHnoSc6L9E4bvyRx8z/Es/YKMTPtaGqq40go1Yynbpec
l+8XXRZTPsnHnQ/RWUaFdE3iylCjKeRGc5if4q4gh25CcmiUin0oGb+KDtzoRsXknHQBzS5kr96t
xG8N2cX0NJJmzKqv8jTNd8u0Jlc2ScMtcNl71TLd3P0zFm2qSnLX8D+M8htvrslLb5nuJzdVxj68
vjKvNRS/TVnY3nzv7eTm9lq3ntmwafzvEhXymgF9oqgsMuG2qkipJTPkenrZp2ApbrRoarPoTen0
T3OPhKRJBotDCjqTFrVUn54u2G1KpVNAo6v2xW5A6YcD58F29daZrrKE/TUZobfr9LbZVDZx18zJ
6VU0uif5ZqHHlKT9t5eT9QVBsik7Ly8t+vSm6KepzmxUiV+dLDgcU7KjMvJeUY0jLx9XT4VzqnjF
wX3YWpmq8DOe0sY/l+UjT254XtRr9WzpwERPE3bJnIZIsoCJgSZatq7QRE8T9q0qA5VBsp6mBpay
ftU6O5YKNDXE0mQ3T8xg1Kkc6Ty7lJEk2VIzpQqdOys5Oc3EEYPBZEQXTkvLVvjQENhd/A1v5QOT
7+W9sT+7I7E7ej72OcXEHf1kwbFL+vToZ7svWTPQIHZX5Wo0jxFy95sRrbGgjCxB43Xao2/t5D68
ouf+2DwljW6/srOpDDle9sVn5M+exvS8QvpJiy6tWrwioPysGLN/jvIrh/CzkDf+Txp+vSfH/ykW
IeLIA63EVWQ0u/lMVyZ6gUuuKuZ9Rb4jIUWRDrSOPImxCG3IbTRWumMsV/p8RmvlxEcxE5/KWyuZ
TZDyssnnIFP8HMS+anj1m4Y1XLkpIQhaxCluN6dkZpGpnlmVv3zXPzM7OjBXa9r7sMHkzoked5aW
F5z7TX5JvoXsmmW2cHWHHAGHNV3u96vFqdHo2fomHS7bJWaP/aUzFrfV4ZKgWLIqywlHsoJlqXhE
0hRbC1Nj54/k6HTmI4XoIzVqm8HS/J76b2pOLiIGcr1ckPNKXq4WceOj/qYoSRVAbzFn59FvuOAm
1apTHJLLLXoQhFxLzAAwnF28+skUrmDsfggj28v02ztL6L4s/jlxLEqXk4lPqr7kN5yivG/r/PLG
Tk1WZrov0OiNvu9werLJfp/HmKQ9fsZg8lXF/GjOrQ/PTDqdK1grhju5T6dVpeOqpjY7UxxV2VE1
OZ/TkOZN+FOM79loB3OR72R4TEzWqTJUHCTrkzklLyiTmnktl0QjXy7iSVI1q9Ela0GlV3F2XiXl
tLx2n8ip6Wqm1ikPqSTUrzLokS2JulmSKknFJx8C5nJgYU6o5dE2Ypdp1GjwxKqPr3K+SV9Q1J/G
8B/7PNW7dAn7kpezlDgz0XhcBqeZOKnE+LlfRLms6KfFVSW2Bdzfr/yeyEtKPFl2khn9g5+vymqf
SvTFX/xc75oxh/Fqi35EGuB93F+7RKPs+KkkkfIlkydxx9RqnZYtuKdPF4PPm/IRbitj3wvNpgto
NinVFvUvLgsUJsvfbwo1DQ81Vhe1Lp8+Y3psP/wRGeZ34rgGqBE9+ojYZRg0jBgihksGqWFiIv3T
unouPpvJmJhNf+kCm9C3JOXidZOa6NeQV0xM/IMz107NPf7BB2yveRSZ24Dz8yCHEjGDiwCv5wW+
jb+Pl+p4Xh4RZYSTPi1TKGVP5xTRqH0hUEzlfZFeXFyM38LQyTacOXOG3/nBB1e6338/Zh9rMSlH
mfFgFVV8ZIQjT3OcVBLbnPgYybRj+Uvv0x4E1pDnuCC3GNs7RSNHeO4ZEQgx80QiJZBTNfE1PvZB
rbPUyQWjReQcee4R7DuV/wZZLN0PWnCLejn202rVckHBo7z0Ojbj61c/lDnLvv0Sk1bMV0iDJiln
QWe1v1Cmke53zhTqV/TPDE7ZsiA91Ej/YAT6+Rd4In0K9UT/PeImMcMBokVhlqeSpCS1XKFQOxx2
s2Cx2NUneN5+wuD79CXfBf3ziU+CEEvM/nqx/Wxxiu1sMRLBrmnZbsScbHVe80bIK2p1VvvsyvJs
Q9Q4gZJ3+BeyZqTV9q6aVtZ0S2fD7GteyK+pTqfyJ7gHmSzSoFJ0KKyC3AJpJC3NYbE6tFqNXKEx
nnA4+BOaGJWv04+sYilGndeKkebiSRJi9uS85o0E1GrX3LmVuS6jgXx8FZfup+SE+2aUlU5fXBsj
7uob1XFNdA7/baSNhzRRwxPOAUTgE1YRSKk+i8ZVW4uz43rPf/tK4WPca9L9//yBvBH7PhNt5d6R
PoLnogLRqsJg+lVRRSCdT/8qONTp5h1SqZBBh7lyuviaQyyhXw8y6I24hzVn0u/+0h9zstFqoT8B
7p2j/765rHTzG0ebyqq9RekugzHdlZrnDkxZGm1d8SqZSdJJKpn92qo5Gm1O/qzFDz4xfiH6s3C7
L9dsY3buRboWXkeXI0YXSVdLd5jNMbouXkeXqdhiMRr0HG7hSovLy2I/pSVctof+uLz/JVnSR1a8
Gj0efTv6bvTpa8giUybIQju4HfepKmkv2KEAd9b56VKZzKBU4snjUVGptHvshCeiXWLw8B5cFaUu
O8o86W6v1+fakzxxlAhc/Qr42fgX/q5+d4VdwmbKOLmVHQ/iR2bOUGIsyyonNODK5PGPGthRgr/3
4Y8fE1TtTy5b/3hb+NWHfvfW4CtE/9XouH9Rm0cjU8lGbm9ZUeu4WVro3zEOEUmwoufE5tt/voHo
ifI4KfvTqOLKakueoNaYKup/cqZk0S3ND9C/Sk6Gv0/8vwaxXWuMfzXo47gEMUccl9J/piaOy7C8
KI4nkU0gxnEtFJLv0n95XUJvn+i/ABDD6edkzXGcA+0EzkMRNz+OS7D8zjguhXzugTguw/JTcVwO
n3GvxHElNPFn4rga5ku0cVwDOZJwHE/iPpLsieNaWCzfPKt9rhDu3dC/qTcsrFg3MDxvYGiwt6d/
RX9v+Poqf2FRUREWFsQLC2hhe1//EKsV+rqHhOW9vQPCmv6e3oEh7DS8Tpi6bt3KNb3CtIGeQqF7
ICxg4+G+XmFT95qN3cuxYnDDusHeDcNbhHUrhNZ1A+uGtwxi67XdK/sHVtIOvnUbhP7hIWFo4+Dg
mv7eDUOFQue6jRuEjUO9tMswnf2m3uUxChDvWbepdwNOvXEAiWRTDfduWDtE226h/eL0zO3dsAmp
HBK6V27o7V3bOzDMxhXWdm8RkAgBh+gfGt7Qv3zjcG8+Djq4haYDOPZwvrB2Xbh/BVK8AZthCVLS
O4D09rIJ49IoFNrW9HZjFfYa7u4ZvsrcCuzXPbBFWL+xd2i4f93AEI6ysntDmDK8ADlpwg5DVULf
8PBglc930003FdLxhgp71q31IadM6EM3rO0fWLHOtwYHW+Pr3bim+2pr+AYIUIz2WQRliLVCP/TA
BlgHQwgrYBjLGhDbAIMs7caSfsQGcB8qQB2swR8B5mDZSujDuiH21ot5L7behGkYW9KSlbAR23Zj
6ZfnqGKzdONavhzL+xGrmkTVtTXz2chDcSoEKMXxaTsB6nGGfpwjjLgfS8qv63ntm4AppbYX82Gk
nY4qsPINjNp+9q/h97I3OuIw457++/lrGRersWzdRJ8b1674PyVRStEAG4tSI8A8fOtnNND55yLW
zd6G2JwDWOqLU7BuEgc9+LYRa4cZn7R1IdJAx6ettuCsdOxpjM6VbMaVE+MJ0I4llFaKxdrexOZY
jeNQ/Q5jWRXO68Ny+lOI41zPXyGjYS22ic23DmegfA7iCFuwtAfLVzCKhv/LUa/WJ0ZrZ/9nAeU9
USdgSTcrWY509jLZrWHUUHxoQm+Um6mYUjrWxLkfwFaFk/iOjZyQ/CYsX4NSpP9nQqzHIONwkMmY
cnVVu/+aZBOa6o/7yBCOPog/a5iONjA+BehkuqPtNjL6E7MMT/B+E5Yuv0YGsXIqo02TrHUjmzVm
EQmuYta8lrWPjbtlYr5r5TM37r0xWcbsbSUbm9p3L5v5Kr0C45jKJCYJIU5FzIOoFS7HVnT2/Dil
g9g6gQ/E6R5mJWuxhPZcEZfxhvhom+JS6mUeOxCXb+8kDq+1DUpdG+OmO96rJ17TzezvRppbMeHP
A2z29Uh1L+Mh5p9DE7GBenh4QsML4jppmrDZKmab/5pd++I6Lfif8Akfo4GW+xivK5nd0v9BKRZr
bzQ2/B/ht4OPCmVuZHN0cmVhbQplbmRvYmoKMjkgMCBvYmoKPDwvRmlsdGVyIC9GbGF0ZURlY29k
ZQovTGVuZ3RoIDMzMgo+PiBzdHJlYW0KeJxdkk1ugzAQhfecwst0EWGbhAQJIRHSSCz6o9IeAOwh
RSrGMmTB7WtmaCLVkm19M/OsZ4/DojyXpptY+O4GVcHE2s5oB+NwcwpYA9fOBEIy3alpJVxVX9sg
9OJqHifoS9MOQZoyFn747Di5mW1yPTTwFIRvToPrzJVtvorKc3Wz9gd6MBPjQZYxDa0/6aW2r3UP
LETZttQ+303z1mseFZ+zBSaRBblRg4bR1gpcba4QpNyPjKUXP7IAjP6XF5xkTau+a4flkS/nXPJs
IZEj7Q9IxwPlCqIjUnQiSohyItLJZ6IT0RkpEZ4kFwnRWnlBKgSdEqPZ1VX85/Fxpx2W8QK3nUAt
vyAJusCOTIo9BcnrXmIwOhPFuMUkTyRSEpE7kuccgznZksfVFhlZnnNp+71X6uacbxP+DezP0pnO
wP372MEuqmX+AhFbqk4KZW5kc3RyZWFtCmVuZG9iagoyIDAgb2JqCjw8L1R5cGUgL1BhZ2UKL1Bh
cmVudCAxIDAgUgovUmVzb3VyY2VzIDw8L1Byb2NTZXRzIFsvUERGIC9UZXh0IC9JbWFnZUIgL0lt
YWdlQyAvSW1hZ2VJXQovRXh0R1N0YXRlIDw8L0cwIDIyIDAgUgo+PgovRm9udCA8PC9GMCAyNCAw
IFIKL0YxIDMgMCBSCi9GMiAyMyAwIFIKPj4KPj4KL01lZGlhQm94IFswIDAgNjEyIDc5Ml0KL0Nv
bnRlbnRzIDQgMCBSCj4+CmVuZG9iago1IDAgb2JqCjw8L1R5cGUgL1BhZ2UKL1BhcmVudCAxIDAg
UgovUmVzb3VyY2VzIDw8L1Byb2NTZXRzIFsvUERGIC9UZXh0IC9JbWFnZUIgL0ltYWdlQyAvSW1h
Z2VJXQovRXh0R1N0YXRlIDw8L0cwIDIyIDAgUgo+PgovRm9udCA8PC9GMCAyMyAwIFIKL0YxIDI0
IDAgUgovRjIgMyAwIFIKL0YzIDYgMCBSCj4+Cj4+Ci9NZWRpYUJveCBbMCAwIDYxMiA3OTJdCi9D
b250ZW50cyA3IDAgUgo+PgplbmRvYmoKOCAwIG9iago8PC9UeXBlIC9QYWdlCi9QYXJlbnQgMSAw
IFIKL1Jlc291cmNlcyA8PC9Qcm9jU2V0cyBbL1BERiAvVGV4dCAvSW1hZ2VCIC9JbWFnZUMgL0lt
YWdlSV0KL0V4dEdTdGF0ZSA8PC9HMCAyMiAwIFIKPj4KL0ZvbnQgPDwvRjAgMjQgMCBSCi9GMSAz
IDAgUgovRjIgMjMgMCBSCj4+Cj4+Ci9NZWRpYUJveCBbMCAwIDYxMiA3OTJdCi9Db250ZW50cyA5
IDAgUgo+PgplbmRvYmoKMTAgMCBvYmoKPDwvVHlwZSAvUGFnZQovUGFyZW50IDEgMCBSCi9SZXNv
dXJjZXMgPDwvUHJvY1NldHMgWy9QREYgL1RleHQgL0ltYWdlQiAvSW1hZ2VDIC9JbWFnZUldCi9F
eHRHU3RhdGUgPDwvRzAgMjIgMCBSCj4+Ci9Gb250IDw8L0YwIDIzIDAgUgovRjEgMjQgMCBSCj4+
Cj4+Ci9NZWRpYUJveCBbMCAwIDYxMiA3OTJdCi9Db250ZW50cyAxMSAwIFIKPj4KZW5kb2JqCjEg
MCBvYmoKPDwvVHlwZSAvUGFnZXMKL0NvdW50IDUKL0tpZHMgWzIxIDAgUiAyIDAgUiA1IDAgUiA4
IDAgUiAxMCAwIFJdCj4+CmVuZG9iago0IDAgb2JqCjw8L0ZpbHRlciAvRmxhdGVEZWNvZGUKL0xl
bmd0aCAxNzYyNAo+PiBzdHJlYW0KeJyVve0KLb2OHvj/XMV7A6n29wcMgZNOd/+ecGAuYJg0BDKQ
zv1D9Khq7WXJZXmZTTf77FfLZcuyLFnSI/+Xoz//ydP/qz389f/+z7/9r7/hX4oP/A//8f/97f/5
6//HP141M+3zl//0kPu/8Oe//dtf91/+49//9k//5v769/9No3iXy1/Nl/svNNJ/56HxLzk09/mX
VzLvc+B/7MV9f+rwofsv9KH/8o+//dO/Emn+6x///W/+s5BOA/lW//rH//zb/+Wc+/t//usf/+P7
X+kbly9B0GSvaHy8UipxpElZ09Sr+NgEjVM0IV89Ji9o9LdivEKWJE2T1CuGGMzpJH+l7qqg0UtP
/WolRHM6uV4eOzvS/CvT/Ms/Fgz31V0lpCx+E9S4FWzPkua/KJoWLx/kEv5l8+lerhhdeZnuH5rg
wlVr7mLHnaapV8velIrgy+VjjtaOh5CulHOxWByip/mEbG1VSO7yKZlTTvkKvteTnQq5XaWIL0fN
rULD1tasjQqVZDa5YK6geTofvplLaOUqreaXHf/S9HC17r0l/KHXy+UmuB7VOJHOfSjd2uBIxz5n
KYB6ytETB0NL1nRiIIHrUuA0eyIJgS9q6dHevZjSlatUb9P86IzTMYsv27cet0TaqlItoY10xnuM
8ttJ07TLt1RM3rRwxRy8dWBja8S/akp/7PFq1dTQsbeLDqh5zpIrV/JqOpttSJ7UaEhvKvJLEwqk
zVR3KaaLdIElkSmFK3vF0X/RNMQtUp3WoSaVRGoyvGzwepWFBD21bg5bcaaUxtarJKVOWlFyWG1m
6v7KSaq73fyyS3SZeSkB/yzHzXSgg4sm+zLtZnI1WGsgnXBFUlSCpigaOtCxuLc1DDTE0yq/pXma
oda7t2Q/Z0efKkeaPxdSo158+e96WNrxHG3rKdd6VafOi+ZWy3TJKK5rGjq+Jbxpvz8kxfnLxWpa
RgXGnOtHglNIg9PxFILj1WbS1Ei4arXOZqHj6+lwim93RZPogovyEpxocr+8t62yUkhNBWWVbUyj
Qtq4xGBe5IUu4NyVKgsbk6uIJbuNtvRShezIQw4n5DEejR5zOyFP/mipymPYkvejuedcT8iLP2Jk
qUdzL1JD7cihVMjE/lCr0+ZJlacIW+hLM/kGnuyGDlkaaCZ3i1xTj1My0Gj/JpBREIsfaVrdiDD5
X/cJNcYl2+w+oV8arbfhf9G1Jdag1b/P5GSAseP8tB8HjdFTG2n+vtF68NE63cPm/Og6710Mm5SJ
R+YdeQdJDBP/q6LBbd5befnU+tiTj1ZqkixWijJ4UvZZLlt/O5DpnargcM6bT8eCe0ZMVzsPgXY3
yC/vrplAjnQucrP19RUK+UixSoHVvg35Y80lIRCTr1XpKqpFcq9qXyuQNRyyJcShdTLOe3o5ZGuV
6ugmr71aghUdmag5p5cDvh4XTpQvgudZmQiRruAYo6U3IlnQoUuB1SZgJAs6KblX3It0LGNR8qn9
jeLIfvLmTpEVeXWnpry7tMiTjl5xT3MCLlNQKlQvsydy4Xyw2EVOPXnbQZ5d7ZR4P0vbP2/uukCu
q5c6QUtfIgu6RbXOoGloH2rJJk0iVeft6wROU6vqOtGOFTlNrskToyU70Z773CRPN6Z4qnTqXbTH
rQWnSo6rdHEiXdz5rclYA+liui7sPe90nQRn7nl2lbyk9Ca3gydFHhlbh9Oc10YNruMexNnT5kGm
Pc+kZqw1ZFy/XZ29yW16XKC1CGZsZ5Bi4fUwNTyO3voayrVfhV9C1lucaftqkcuanEHavliPOEoz
u0qW09OaqpA+bl5ekzupLWRckddkSlKh3SQbw5Skgt10LVqsKYksiJZepjeQkOCEbirkQhvuu7xC
tFAUKG1f/YtUGLYyCVI0TSnyHUnPy1tRn184X+8q0bBExUS3vpdUlFtyOd+tqxbdEXkOR+TyQt56
dv5o7sre27pq4WipqRxNJkvXYut7uaPJFH8kBKUc8b1Ia/EnRzCsDrUn6yMlPF5/aSYHyfXLZbif
wziTs1hJOeDld6BRb4OIzcXCN0/4/fjVj627/nbKF+kvOb/dkwpZGr4F8ZvJOSNFRT6FnK/2zvgF
D885A40OFJLyqs7Xl30w3nDIv0j1hVXC6UsFrzHTsgca8rRu/3dJExzp45S7xeJA1xcZJEJMprAR
GSOVZMViafD9qq0IkXx8bUPpBcRQxTZ4ZQgFur5ik9+eHFW82rvszTVkMvBcq+Yacr96Y/9mueWh
8Etlt45VqI6skVzMcSociOitYxXw3F9zMtfeaY+7VAXTujodoypVwRz261dL6ghr/w+BXaeOxGaP
Y4CDk5u1hkimTn4ZdPBNC3kYXjJ050tnMj+73KjJ08ukg5zg7xTHxJNBq9XiHeJ5LufwMr2BppH1
mbN17iMe+3uQ8tc0DZ2zkkzZQjyvR6kC52AdWd4umnoo0fVQbmfmZ/VGt/vlSjb1EhzY4oqplxLp
hlxaejnT628nJCcE62im1EmdZPPWSSQVMdU3MR+skoxAYbOOXYIa6OltCcI3vZ8Jl7uZmn+yPYZl
6WHw2FSLJcipk6znbirAjOyOmE0FmB3N2NmKgr3X+4VnyUEy1K4QpWLYBt5iJFfQm3dyJruipVZO
lBSCgCG4YCmpjDfIpHZTr4mkoks1tXsxRRAw1WSacpnuAdJk3dre3MMTnl0Lf+7sqsol7Fxg7y/X
45tpN9C0K3mpJ3Q+A6KApXhTb5WAZABljmpfla6C59F8KcZweUn9e/NbZFqSr/omJoPPG0n3dylu
W5OfTGHno3U8ClJ+ONS/vvsLUn6ceV2U1q4e1A23kXQfxcy2Xmx2R+S1n5CHcDSZKKVnS57yCXk6
Gz3Fo6XmeMTInI4mk+sRI4urR+TFH5H3o9HZdE0/eLFpdZy8d1dy/EyQVurRI9Wss6n3HUddovSf
rtYFyeQwRw9vqYlhdo5uikhxqi+/Gc4Z3fG3BH5ptMdHjm1pwaaBYxtiMdlVkFnG3tKaFeSdxNYk
SzcGNxzbVJLgnw4ysdfanDm/4NJ1OxnL3QwIYIcsWarjgb5csbNC+tLsIqd0Ad3pX8NvdHwwNlpC
fxOBwSHNk0RONJlsLb1Vu/kVYt+tefS2DI4liZLvbyxej0tb55r3lmiFhmTN4M2to+0lYyVb+xKd
Q1Jls2kS8aZZn4okAqX1/CJthi9KVrLLb1I9uJqQfC9FQOdmkp9Rcn3bXsMdJX//tvO+v1F3PnJH
6ZLr1smMpV/5fo77aintT5NT0ZLUOFqTRbIpU27Z5EX78wT2nc/ka/55Alt/q/dP0HV5HJA8WmKQ
fN/5mqTUXa3F4hd8zaD38yVYSraxFO3/qmnINnVynDnDFKohW+xKdOrp5Jv3EG0LbU3x5pThf9Zw
pN1S7TDl48uRGbxE8lldt9fQ6Z6s5ilCGLRndVepU5QdAlzd+lLmRKUiZ7Pz5cjRqEVu5uTnRkcH
JDZzepEjuaa+y6lCb+YXoR38xkgHVh3qXT5uSfP8tMNXw0XXvWkOZFIE+nBONORohBSquc7WyblM
psmQO+48WywK6f50R/t+PuTFI9nq1RQZaPgxPFn7WVgROMFTrThL/DhdP1s9JdF11pxk35SVGmmr
5PU6fbqANVJH7t4OEDvV5oB+GaK5kcJJb7rXcBLFkL95fT+Th5CPyKUi3JKfTSZKVbzPeXUn5Ene
F1vyejSZHI44k88YWaRMb8njGXlpR+TtiJyt37J0ttwfM6soLTTQ4Jk9hJFmiiLilTNWMc6Uvxmg
pXmjyuqIerqNYg1yzlPZIjlXibMmvzQ6GomKiDu1dr0u8kzIApbf0pFPUleRlfSahQVGvJMs3PmH
yIit3mYpXUYuqa3ZOC93JLRFa74BW34nTXxptGPnSfnfGS5L9gWyOH2S2zk5pwH1BVmOo6ORkTyI
0N94vNZsqVyd0+KH3+hoIILfSY47zY+8jHRHHpdiyxHM+1VpKZKIYLagjtoU5WxX79Vbe87O5+3t
fWl2ecYd9Rg+vsjJ4ESiHkOOu0seQEWij1H8ZvJmyJCoSR0h/e0Ir+jteAxOpP8kXS3FFsm0MRUh
trsE+wjv4U5OX48L7yHKb0/OH4lA86mbrEDw4rbNvvPb2OfJ+U/i/p/f6KB/IpvP3b7BUkST/xOl
Wx6zFFCE6pq1Tpo/HUX2MZZijGBk7dHkBRzEx/5dj5NoPlWpIfUIkLL/ZNyu157JHk++musiHyLe
wZ71fArJSktv6nYwSspTvz+pTqMax31yItffRgb1bfD+PC7dOFfMr9fD4DOSXPiWLB5nDkY500rI
tOe9yn3Yzi9BJrtQd2/+4BMVXq+heOT4i3VOAT8kHUSlfrVPRnsXUgyW3OYWrqZ5uvNP6cr1VarJ
KTpFV+4NojCp34EGBUTepvGBzoxS41OurPs8VC15QWecdF41dQH8v+Zjftk/wwEkvzI3Ob/JASyT
vp0dQLoGi/z23gGsnzfZpXVZWiYrNeST/VXG8U9lib+Th+SOyHs4IY/eH5HnM/J2RJ5aPiHPLh6R
p6PJ5H7E9yLP977o8WibSj9aKuu5ZZ03ooQ3fkxYluciSvjcvWtQFzL/yMSW4+hvIde185lbFpXD
o0ulynEmrw9VKSiKHdalvUeyF3rPYu0zWA2ZrCV6c10ZVR8cEFiD1ZBbcKO2DDRblw73AGcgLLFC
EBaMjb3S9qte851cxeS6xeOAknZf5HyTpiE7qceXZRuvU+TZut4tUQrIV6xejqtzN2l7u4/FYjlX
QkZ+b9RbZ2T+k9g4KX6Tl0pb6e7HJAN2xsNrFiI6eYoV7AvZEuNA10vqxVvHE7AzXvN0Fy+D+RDU
UZwwZshLTVGKddA0+SIPc0ODvKNcLX7FUK/aqrd4ESOOq6svYmtkqdBelWKqAaSyxu6KdcTh9j0P
Vj8f3wgZaGp/lemCOGEu0ZwerP1Ww8kJT3deh6mxE+d1yHG3KaA4vt41a0mJtsl1b64JdY/J53y0
JnhuNZmaGDWOMdmiBq8suvp2wxhPxxVaVqx7ThLNV77jf78j13SoMRcsXgE9JsSUTtQYXTRXURI9
AcUkkjylxbQjByftLg1bI7zE+nE0l5doTqShcjDFEUmi3qd4tExy5IjtzWRfQVamk9v9Esi7QXOM
ceiklh66uc5Wr3ZnvC9xYFAn2WMo5rc63Qy5mOJWUObKUBjrbyG79IbJ+V0kS/BwWJO153D2ngz4
n5G7ChKHu7qxp0pJFMk30zApqZPqSGKcqXAThQe9vWnrwSEsZOA004JAJmmM+e3oDQ6gv+rrpTSQ
kH/aQjWX3oE9JXZ8i/Uhdfe+ZPKIPPh6RJ7jEbk0V37CzjkgL0dzj72dkKczztxhpd/J6xEjUz8i
z/6MPB/NvfijbbqfYw6AfMoJOajjEiYFQD7BQ1XHZf03gHxST17Q7Hw2Up+5QKDistgbPm6N2Oeo
i8aNpAFUYIfy8pvBV0XYC+/C03wHGqCixWLOjywtssXFuqeIaYYPGdMLjfHulUjlZrkv2icnozlG
xb9d1j1dzTRdORf9PkHXbuGMroFGO5XOYX7epiHrMVfzW5wby9VLA4127EK4MudqrPcqkFN0J86t
ZTREFND5N35JRzirvdKhRADLBGfKDo0BZ1Ts3zaUWPJTvDd8W+e+Iumyl2DylCzwzJH1iadG3i3J
OoOLfX+jETuQU+s7TL/1t5Ev64uT85vAVklXNCf2c3ao+wMW+qXRkB0IbbogZWfyCCPiNNHaqsgY
X3JZU3gx+wdmaZjypl7pzqHdTA8Yyyl6SyQjkiXZiptYalzTUA3miSFb9ymVmpY0+MbpKmrDd24a
J8BFcTicDiySa9z4lXagaZqGbNcuFYxX8E0pkoJpRczP9Z1rTO601OlT5mkhucohmJyhjYuhFUuG
4QmXlLOl24Cj2jhOd8DiDtDtYm1uJvV8h2XXS0DWa/bt6NOAVW1Srt5QVWsvUoNOzjIwt18Fa3CE
44O5/fvtlummJedBLklHGWl3Qw32Gmh3Q5RCPEc921O2t95dBgMKUqu+ggHFN2VoJMQh6993S7MU
169ei6lZUC0ZU60nmgWVkZwyt+YwCiM9l/etBRSFkRysM1aQwOAYzBXkQld6ai8rGLzXfAUnNcn0
rQoTo0drM4G8WqMyiyb3FZDlas47c1VaJFvfVI6+BwtyR+TtiDxIAduSt3RCHnM/IpcKZe+bHjEy
yRt472wecYbDXQfk+WjuuR8xkguCD8jlufnJ2TSAgD4B1LisWv4GUAca9bTuQ4QxXU0acggyo8Z+
aSbHFjWTvsv5TEFNIJKxU7UG6AHUZGaNZ4ABebJNUjHHIW12R93ishwbYEDdy29NDjBZlTf0ZdQF
soMyoL3gbgbGfqEgg6uajP3q9SnsWPOZNDSKUyQPdZ6n6w8E7UAzof/Uae16XSH4i5xKIT/aCGRE
oNiStS6086hdycaEMVthD8txNIhrBkiFPBfTnHO7/O2Ur9F1Chp4tGzOudLapfToL9VPeeVawhBr
5SxEYzLdf9yWJbIVoH4YZWH9JeTOFle7xWM4lM37bPEvos0Lo12t9QGj/3SlV6Z82kLOdSnmfID+
whiQxrrID3G1enPOSH9vLlnnLwIp6n54WyP1cEJXMWU5ooIn1GbpDCAHpRrt/SLJULv1ght09ysa
hGeq5ayfJ5afMbz4/HwTebVuRY1fZB29TN7zkBGOW8VlYh4eLUNp4ltvj5a3j/kdRpfHI1zYk6CZ
c27c5wFhPZ2EHCDgSxjTAUA5PxmtVw5ImRAld/QtB/ypLr40XRgFEOZNfmpqGRWfDERjOhwoQqRo
oJmyeYDFmaI5H9JBwVXJHX2BMRpRMLnMvaZCE+PMSADQd0Gu/QWaLnIG5EDzUrRRuHBivRV4ybxt
gPWUSXhcL9VaOuo4cgoWBwOai6UczE+hoPw+rMsdDWhUwrlXxrcK3u2z5I5+U66JBLU269ygR1XL
kj1zslD7mIfrdfV4eS7tWJ8t9KgKXZ7RSUU7gCYFU2UAS90156214wq76ynWa49k9tZUirUuXHMt
yL2Y1Di/0HRTNvC2mpKcT5PPb36O+TjotYfc980bqodmS19XWp9vMrzvPk9p6dqjrUKNyBsaxpmM
6gj89iZodpEUugxvSMThN9oQ5zyXIL6t4ag8OqGlKOc3RVL8czLW37rhM4Oczxt8pive4gUKy1qN
9rcCLkqXXvg16Kh03zrD1kz654PIOH3KCJ4DEhy+hDEu+VHeFZsVBcUZzpvLJGVT1KdedE3PXixz
LisDbi0S2Q2uA9G9p2hytOMez/3lRBg56KgdERyecCXZovFimZPlh0ddVy1mRb6TopydTm+M/eme
YUwnfVDzhnE20VKgZ9430PAbbeAyfGYwz1mkDb+Rzo11NnQ18/lEV0RkETPK95rFDIPJ8OjrNSAP
MfJjxJp/gCK5+xCshR9QJI3z+taHCFAkSfN0F5lI6alsMcbNgMTzxVxnBkyL3KqpqIzMtqjU5m56
FVggzjysSE10QR0yHfwhwyC6ECzFgAjMXcw3fct4BHRPG7ZJ9AcaYjGjDq6VSebiAS+Pmc7jCwDs
d6aaB8jljdI4ia1RCfJpHrjeXhSe3c0Dfz9C5HLDN5fKeCoyg1jLO2daUwuXVzfylJqINg+2hGZ4
DSm+LeEPTXHleQGZxNhKC7qjQWsJBXzIHbhdS2hBVXd709dG9Vh+ArdrHVXo7KbUzQOEkEwOto5H
hVlz7Y0zX5oan6Yd680EpMidu23sQmuTEG8zk6pY4r6MrJ2QR3mR7qMgR5OJ3Z2QJ7nj+5S7fEKe
pZjuy8iO5q7My33KXToiP5sMt0z4nZzbQKcl6Co8m5hYTy2fGX1uD6h+Wj7reahNBtUfaHSjvkqn
qMthpogCGWVefmqOBHCvvDrSqIO2cAc/aCo/uoNLdCO8Yt2JRWmJbuRZ9eAdOP2MbuQbOrOyrbFE
N/JAqKtRjLv1ZRzdr1xNs54vnpXIbWuCZsICod3hZJTh2zrGgELzLsd5c9nud+KBZop5fN6JB/5N
sYp4MfzmMIwO5dBWVV/iC7sGF41uJO5vPNBMGJMR+V1SLPR02qcJgvEtvAdxAdL0LUOPk8Az/vjw
m5d3nVxdfGH7ely64B/z7c9vvB43cq23GNfpcEYCsH4V69Y5fQhD1JS9mN/GxIMn9Xj/Syw3gENW
fm5fixIwO+4ykYFmk6eIxLbGOHzTfAcapLV4c1/gbWXXoyU3aDrQg1qDrqIiUzuoYfSn0Lyy2Owi
jXlhk81xuLd865YmSLE+5RNrjUIGE15HurkspK/WJuazLfzCVcPPydNvBvPBA22oW0cx1U/ps7FO
PKwVqenfvLQW7XWizUBwzeQ72gxEeYqmHC68srRusj0H+O5vSnFt36D5eCvB/HRs1hmDO9aLLcO0
aXe/zfW+5QxImVZfjupgjeUH9MvgJdRC7XJvJy+uonZVytHkxQF7P3ZzzkisS72Y8+n56RO3ZiHD
h6izsFPhyKxrjPu/tlYA8RGjffsXAKlldWtPqXTl6lWp8J2zV/zFaBbGsLRVejsnPw5moeLwBPpB
NkW3dwEuWihqF7Qb14HKqyRwCwcpVriv+ion5OGMnMFlDsjzGXlLJ+S313CA73g0OtcRHJDno9Gr
OyK/HS0jOA7QCvZql6A5jDHI/afTMjgHLPtHay1x6hD6diXIb00hI0Aw9mTOByEjzulbj4MCHV/5
Fl2HkWGcJjYi10FQT7Z8ENOZu3M7urBbMIcJ5RMdWMdSo3vS6NI6jkwK8S6PNpaV+AVKjPMa1w58
q6/XRT7K3WDN+FbJT+LEQPPio9wYysZ8SJNydpLBHm4YnbI5HX66LOZOdDSo9dUSnkhmkatynCnJ
CQk1LQRrtxCxDgyLsT448HZyy6YwR7oq705PxnwgGXfQbx0dRzeE+/ltiVIV2XlFRd96KxBvet4v
l4c90hXbuF2gMQ53UbAPIKAxvDyAU7YUMva44HEtYAhbda7/Nz6FQCU3FjW2gsSHvicFfgplOTpc
ctsnT8Ahm6ibupnBF0sxDyAcMDpbcs7ySli8On2qY398dVoiPzBI7f1Ut4ZPwg1SihxHvyAVtBZk
m3EN50TC0O8H7zUMU/2UXwzzmd7qkNBUvTkO2ditb9ZO9nOIpVlrR/IUIz6vlxUcgnlIVho+9QM8
Us/IslsvAY9ePni5zG0r0P5JMFiPmyJQG8PLuMPtER5EQWPduGEcxybW0EwFz6opWqIDkNy7mnmg
mRJ/6bLnpkLr7QwNYBW+mPMhBXAnGa/ng84qiTOw1mKBFp61FjGfSRd78l5bMcU9khz4rPijdTEQ
90MxZQVZUVGyZ+7IQp4gN5UaaDZvx0hnoJsrWixFR5bISXbDuNODmv+kKK3HIZctBFctscSj25OS
tF4n5/3LT01NW/qkZLZ4wB3tnrqUnOnNDeUNUgJnvN1w9WArQWDy3h1G1qxISNMtyR4H5W4x2OOg
D9MdOdXrsstQ7YOG5p93vdmwU/qNqwC6Vn1aV9viiTyUYH6rfeqQ14c64T5IxVSM6U76t7+F59n4
qpS/DqdDu5AgxWB6dGPw/DflaTiy+ZM1skYmQu9H55o5v8jVGKa2QAFrSOaBBZDTkw+1ZHsGYutt
0xvATXhkCc1kF4DUnTRBpinXjOfjYLIHSTSpm0omN9ri4OPJiUBHlspg/8P8lHYAAu/zpLecHzqw
PE96BiiTfwDZh3F27UcjF+mYJlMh28FFdc/ohyy6EJJrksdTDkV+8s2HNbzkUNz55mstXRDZzdXc
81JRBBeDJYMM3BTtexjovnc+/lpOH+QmeQNsHsGDF+TbVzl5uPetOf0ReQ8n5CkdzV1ZTPuqznJC
XqI7IpdH/KdntmxkYXvSCLgY8jJTB5napeNez8usIDyzkXngR5qp6gO4OB5BuWGcqa0kCl5wueZl
dhESGhrj6+RlRhRXmLQczHHQIoLT+tb8QfljD8WcM3pNeg6eDeO8tAW5gUiHcaRme3eH8ydn4zd3
OC+L6L5JGF+adRLGME7VO0RGKHeuyDotxUjUaGQOITlh+raRhJFJWoL4ycRU/xiceZlog9KeG3p0
oNEuIbkYN0B71hkyo/5CyxvJ4qlnSyeV3bygeXFRq0PSw7AuPQ43eBAkc4sWvMn2ak4ZAAtcCWFM
p3CtSDdZiB4efINMLDSCMEiHzd2cX+8PnvT0bSNaUy6ual4Pi7z5xp1ph2F1f048aZd8IsMxFTo/
vlvcRNbGXSO2PoeAH3q0xTLLDG+LqYZgCRtnaVRb+FH0WaIU/smBRTVVV+NMrTfJHvahWuti76/H
YI7DsXbnrcPI3Vaakv5dikPyTzOiNS9S4s69cp2bZj9AHAq5m4oBCe83wOZa3FJFCN6/8dgAqvh0
Nfz+ZgJs6ijqNXVbZuCv+MbOgaZfgUs/11sHON7MiZ1rkaSLm7ZBsmv20PxTvGd8i7y4xIErY85o
lMOBqy/N7qEDCRXkzgjxm1023Cmvyk64bKFL5bZLSkNmBLlAkn8Tri46RbY3tTTQ4FFDituMMURX
J4fB13t14+rGN9mx8EfgSrxd44M1m++erevrrQBBKvZsnVbOaHfSypghchFUS0eaAoBCNwTA+lTd
PVOimJ+GQQMeLl3TgkbDoBXggfHjzTDOBgaNcX4G8l9SI34n51zU38mja0fksZ6QM/LmAXk+I2/x
hDyno7nn2k/ISzja1SItk33ixdFSb4/wm6yzzHDPy+Shb4Z7XqZnfTPcvzRTuItrSfDkmHWK1Hgi
Lg7SDyRT1AxoYzGaNKgNu+V/nWyM2jAGBpzG2ThpnxDnj07asiQd7viNspSXwXIwv0uSGRKCbBLH
umGNwYDYlA9yHO0ztvi81hvT6Xgxr2JZk8/YkZPA6sFIjEGEwZlzRmLMHWxZszD4/OD/5WX+QwhI
HewWCwMafWU5ndknLJ/HgXWyCgPXOnPX6b9fjTGfjG9lRvaRc57qq+nothxNFiIb9LYxvt96SXqJ
9zOAmfXyuCjrOTfgWCg+T1BD6BGagjlnBKgCwrHDONplcuWJAa5FjMzOq7Ziiga8x5qa+akICA8n
2DxFNiPM7lDM6SSwsGdr6QDBvRPH11uBHqB3+exanJEZQ0tr5reQDBGytaPcFpQBYNY7Gkmpd0ZQ
MpaOlvIMVGVMp6Ur9xrMpTf0tEnFXHqv5HEUOc5L1kvKRa59KuAGhIdis86wQdCbASHWPER4M3Aq
5jCOjumhyLtIMdTZRWgn6jjFbc3DhFIT9FCz5sOBjxCtPaVL8Sq1iXGm8C96SrnQzW/hmZgT2Iw5
45m4eVPJJ85Fz+ZJRi0CFyYbW8o5E0qcNeAxwqI+WtKDqOgdvVyvCj52j1LCJvhdFK3U1izJQM8b
co2TtXL0vElJXpNTnTlwiJwaZ+p5AyWm7pypAgENBtSpmMKp/YE1MPiDZzFuZjCMUzQN0nKCN9de
89Mkc5CeCf43PlUKxnxwd2ktNhWbJ7z3FmtPgQl8pxsaNKglDNH8FgrQfVOabmpgSn5/a+adXLjx
oFz75FjH9vSvXmtVhEu9796SHzjxQd23b2XpsSjto8ehiymH3iwZK6U+WRCTdiZjnNb81+f//tu/
/TX+z//499tUJ66VCbeukBp6ZEhn4dGNUSu075dmyiv36eoF53mg0TBDMEU77KiBRhcCRzR+gG0z
0Gh3C5g9BVHTgUa7dig6ijDVvzQTrmrOT5uwYZzJvYjoXyS+NUPOtafl1/CtCXKuknx0MU7WPETj
oST5kyf3gm4eTlU25tPxdgVbfT1OQEOVbM0YWfe3Zbz+EkJ9Xg0zFf2SEteCMWXUR+RRekvAEEzy
qSVzOnRQtRBOy8r1MSUGmhcUuMiXijEfzllQGzpV9CI1SgqGBoUM6BeYu5zP1PWiXtXcLLgETW2W
Fi/OhM9VcmfKQGQvuFlHFJnwN9zumjsRHQNrKdZuIRM+9NLNb6EItNlHi1TqvBNTBnuZj9/UjYJ7
iJtHlLzSSYVNlhY8d6V6poQ4GNjedevkwMB2We3pP/9R80wGBc9/Pqr9FZKULpWP9L2o9juB7Usz
vUr58Jh8X5rpZcQD1ojX/KWZegWXp1Hs8C19RSDDidsBDDR6znAGuO/PQKPVNnrPc1uOgWb3WAiU
PsZRHH4zvfTV5039SzNdKxUVFTA7Bpod2ktDwrzcqynxnvHZcnyZn5FZQGZtVnzQGpHktTBA23rd
6JFUMsJvA43WiME99fYDzXQbAN5Y7e+m1p9hRFO0RIJfntiinkTCQPGrV27B4jgemUpWs9WPOtXR
aU/+5QQZsYmIiIrJcCT1cM3NQKNT5QHGdyuI5eHli6H6csIZpLPTdRteNmmgKc/b2noNeBgqjOqy
PiwAiOgxyvlNWNbkD3Bof61cItIV89EuxIJSo9rNYWt8IvTGMpt/EpcHGp0JQe6T5zjbmiYxzHiy
uEWWKDJ86stuDtcGhKub5wVYD3c/6bXwkwA8YJ4Dza7pbwJ6izc/ndqTf/m7BkiZNFSNYrq7nKpU
AEouf6JfngCf6tRU9HRbuJEXftflSEBP2VdrrzPweLkl61qusvdPC9b10cAziuvyaOwT0PvHpVku
G7B7uflsCVpO/mO1f3kzPb2QivKKFxMUX30g3dd3C1IVModFjW8B+duZpgw6B9+AkgONfuVBwyRu
zPKl2eG+A+fhBnj7/sbpELnDa7vNCnRMqi6aW1PIdGzVvWn04XUkoNuFFIttbm4EzkN8OZjDS4h7
kBR+N0EKitBsnYCHkVOdgIbAWidM8Ba1P3VZa5WKdklJqZap2S9ptezlp3bBzyxWs+955I/I5aW6
T0g/mkyQNuaWXJqOexCKo8kwbPbv5AmIeQfkZ9vEqOYH5K2ekOdwNJncjvjOufcH5Ols9LNtqi6c
kLPGaUsH1XEVVh9pZgfVPSX1wzjaQUXBXmNnuK1UFffeyLGb8wkMuNYEzQZUDE7tjan7/Y1+luIC
BsbqG8bVDjQSxdjfW0+PNOddsDfQbHv2uotM7Cymp/3TBmQDvjjX0+tICa/Zmh+Q5l2QrJjSz129
+69PwxhFPGSKpNSt3UWyRL29Li0llnKlS6ZWS/qAWHgnVA/jTg+cH+wyY9kZWaf1bd2D04quPsme
D5JmepPzmSBDyKPiLvTDlu/aBwNFqcr5Td/un+5hv4sfgD56jVLyX4A+esxy3AnoA2UCSNRa8w8t
fXNX+7CbH0Oc5WZpl8iNIpQGmgDigbwTxDonj7kAj6tES04AIn+j8wz7MJVPIyUjvmlWo/aMzkd3
5vFNaBTBgALrbycU3gelKiag+fwgiqx5ClxDz6ADk4wONIxHk81xuNWIb5Z6Q+J92KguOLdZq65d
N2AAsDhbL6HV713r+7tMoq1vTvHtVjRc13y10kwdlBmYx5s6CBkAketS1voOtdOpOPPWBmBh5dK2
9b6gnroVZ8+HfBtfpY7eZrGjCKabqgwg8ncXG4NdUMcM5m9MD+o4BftbaAQiL/atVwqElfsdb/1p
BD2K8y/jDjTxySoaxtFl0Sib4UTk3+dX8PAckjhRXgWAUErtis2+EuInjrvUOOgZTI6rqVmRCxCa
M7ezoFO7Np60O5ugoX2ypLaQ6NzoN7/frnB5yUsulpgAsp4OVTfXQG5x89HUZHCLfXTpRHuoIbdO
bD0i5yLsA3J2d34nl6K7LxdIR+TJH5FLy2zvlR6NnurZ6P1o9Hy2VGXMbt3MM76XM84wfv7v5PBK
q1t6awCU4iqoL83c7TEj80qMMxUgIEuXw+0Djc4KgY3DfREGmilsik4qsDMGmilsSvYU20oDzTZs
mp6OuNNvBpeTbAaP5ENjncii4YINg1/AFeNC0IHvLyXzKXe5hn/erKEDTM+3l98MLid9W03vpTr+
bma/XgKipNF1b34qfC4QY5xYnpqGgWZqboYG1E18a0aYdLg8pXjt8DAAxZyTKbacfM/x1YFmam4W
Htjg6dsDTb1I3pO5hgZAQC+P45Sgj+rvGs35dODcJDnnHQI/AAJbyta3gSHmGatt2k8jCIvUKrkm
XXUXI/HGRzGu024eeupwqvswTtl8G/1zGE1q4Lkel5NYpaxP+GrAfuEuApPKMe6+8Bgn631Cps5t
nBjfRvteLaOTG4rmF13Ob0Lpb4gSJ0tGUQ/uo7oOdqFSMlpLV+dj6pFGRqtT/NMuJ8lA4FrvNS8Q
luUwyHo70RLtThQZPrWJcSALPsXoLTXFGe5dHY8Jbb8j4z68HCHDu21XzVJEJ48d6PtBbsvu2GXk
ukrtPDmcHiVMr6waaPpTDzvt3PrTnK78onsGClo0OyhreYDbekeEhxXoSCnwZbO8Rmef1JFuDtWS
e8Dtu6RMiilJHaUSRc5ZFwMAVjgpE2KC26c7seRsnRckqd/4WNOZNyzK/EAar9eAkGtghI+BZoOn
AHyvxkEJY9yAR/9m8gZOqQ/O5E1hTGFl/umQMN4qtN2hnWTa85CVjTPRkN3BaCxruQDmV5UiuH0L
qNxyU0xvKlbHe4ZXZtEucJGdGHIbWI0n5CGnE/Lo8hF5OJpMzGfktZ+Qp3DEyJTPRm9HnMnSltoH
VssJOT+HHZBLv2FLXo9kRqmzn3zSsLrlvQtPzfVAoyOlXL0lSOZAaSGfARnBA80OFwu6zvG+rcfF
MzyH5L80k3uXuMVbMJdJxgxnjA6f2uVrlPwAthmcARxYioLD+8BpfZKVJ1YNSgfNb8wVoVz/Bt0e
htEeIVeMV5PDqBiPnGcwcHgKgpJXxoEqYxzaTfISkhhnKhmnneIct/XS0X67sgHxJdnESxDfpM+L
JUyxywLQhm6zqwKk0wdzeg0WZHtjxXp+nfsCpRcpGZ8Pgb5gTQ9ds4t75bB1YSBkZnIcFd23y/Md
dkIMa5cUkbkMOzxACGsRQal2K6FZIoLyjs7I+V+aLYQzvyWlYjIPyZ+1eHMPavs81vysxOB4lpJM
HQvHM9xG3VKTJOy/UzzexfN8pTUlsaYpozWUp3Ly9zUBOjpz37fhN7oUJaFyUfFKO8oAEuZGsWve
AE/ap9bNb8Gp0Bpzqon2Tz+7tWwlnO8oZWDaB5xvNc7khHOEzP4U0I9if2P7aLI8ZfeT2lrbLR6F
l6Vb30aItCmNPnmjpK3vPsbrZdLW4RIydRLDSTOUwfp+znT3Pk/a33F0wTFgXbhX3e8XdKbLNxS5
nTN2dH26Lhq8AE6gb29q30jvrU9qyVq0SYoQADWvHGBHZ++ipZYK9rN5U22i+PmutlrvJ9pv+6Ju
8QkrujxAQWuVgoDnXV233nOk+LZgq/qCfjW9JXM+UO0c7DV4WBFPr288XNvQdMzvdCdjXLTq06pg
4+NzptiXfOtcypX9lBP8O/nti/5Ojh7dv5NHKZE/tY47IJcyuPUWfTwij0ecyf6I7/ej6e/k/Wju
pR7xvfQjRjJ1Wh0J5NXejTsHGl1nj5CXA9zVQDMVkPar3E9Y6dcjCxyAzoW2w28md7F9nr3Wa4Dl
ch/9tFJfiGDemWbDOFN0Emq5iPlMbmepV35hhJEBUT9vhOtBEc7kfmHGIjttQme7/0sz9TdyT2rr
7/MD6LTj1sID86bmfGRyurc9WA+LTsPc4/v7G90UGlm1TwhquWyEN8lajOayM6LnuVjyiXCmv63x
PzRTmT7iGFFMeYpCogXaHfFcc4tuohqjueNABHgck++UN9ZRdP5ukTh8Wpfb4xGbMZ2GYbVf54GP
JD89Y04jl1myYju9GB+03DX7ABHmWjpREpxSm7OpxJBSy1VXax2GjNqapZhPbjOKuqs8//tQZkXI
uVk6DBm1rUdvLQEZtS2nbOkw9KkjfRgsHZbwbHebx0vhQ0Zt1yzdepAIj8jzM4VII0zzVC3pQ4Zt
9sHUsciw9cE8zgDwunHep60anExOhsnW1iDpNiih3bKikRNci1ymBv0iseitNXOrUC/cg6lvyGkn
dpW3a3WgQUsAWydlhu5RqlZ7dSgobE7Oeee9oqDQeSHaEzxVQpTMS9HeRM4BwxW5SaGxJtSU3u+l
WkkNhhs63CgTY+cJQg3c3tBSbpB2e2OWrI8r0m5raTZvOooempRRXeHoUWvcrVNVkEcfSrbYBaez
umCyFE5nrfXtOAwOJeBj1CnfVD6VRKLVm9S+E0T2y1HcjYskpSLvqWlN5Y9zuxQTwGg3n98Mp8HB
hPYN0dwHMuRCP1vDnd/1NZJ+yaj9nTy4o9GDVEd7B7OfkEd5B+4zas9Gb0dzT0gePiCvR4zMZ0vN
Z0vl3hC/kyvFv2+UXo7I+9FS2R9dVp8jeklKPQqayR9FxUiV40xZt+0JOq3xg8hFebIu1tMBRsL9
WrX+FEya+7VqieEArCKGP6jLAnkENJ/Hs/WUERergmKrLtInXLReQPsT81wvoDWANoWXbw8uanlQ
Sb40cwMqgE5w6t9yldwHKWeTW+yShiDmPEGqwc5NPpnzicTRW+DXEEF4Nr/fo9bzQa8kxwbfGu8H
yLRcFW2snQzbdtvvPyNTcIqt/InOIgW8dXPq6E3Q1e6BHRxodsEylwC2ay4bUc7IcODrIx3Dp2vk
9O2Bpj2ofhP7jCsEr8LZOuJAHmrJRXMJ+U/u+BrlCDV+LSfrFEUEOBiibpDICY6oPU3oD7YBDQ99
r+a4aE8V1cmbvFBSU12pTR0Iw8nzOZzMLyHtMQbzRKeIGoPX22E9LnmKT3LiGuMox1nNT/1tkcFa
LekD1HP18e1GMTzFNIuEdppJsd6l5QZr8PYXsqk4Mpo99CLFpmqadnFV8XqZCEe22t8kwLJ1ruCk
XpvSUZHWmpV+nPCZw9N/YNLXhqNYn34E39/od8Z89wiwBB8ZrHens7XgI4O1F1tKcusPRPCgi7VD
wj598y/LHGhw3YZoCTYyVpXanysiEa/39UX2DWORJMDJ6U2fTngpj28sNaxK3GxSiGdfDU3CXLek
pCB3oCk7aaN/UA2ZXLbZiUd4uezJTezh6cv2+6e9PJL7CF8/IpfiuHfAyhF5OyJX8rqH8fFH5PVo
qTmkI3LOIf4dCiccbVNJZ+TSzt4D7RzNna/YNfiNQytJfmTQ8AaDcwWHgXOLlzAcdOVenYH0BxoN
hh3+1C2tkWwiXgJZM6/nkz5QGMY4OVzEpCZoXtyru8C9Lou6kUR6R2HWOESwx7nfnzFMZWO2m1tB
fpnvXi59CgvSduVgL6t/ECuqrnsd/DJyEEIt1pxRHdldjNZ8AtArC78Orr8FRHG5E9OnAHDJ/YWH
T2l/JcLvtvY8kNHRYunmZFAOm/il2YD2wTOjZOBUz8kuQikmTSmf1Lg1/A8Jz5O9u2YykJq8PZ32
QZAxPtVfjo32a3v/pOIs2QP82ciNb9cbGvGIHaq5XZHfbJK3tguRyadUdP0tftiJluxEuPRdaZUX
2NrqJQtnfHNy+nyXuzUlwCL1uzdrKyJrnphNNqMlxJ2g+R1H46ST9CTXqske9D9uUpq7TpzlnuRS
w2tccca7vUsOv/yZ8G7J4XVRiIY2z9Mf2LY1n4Gl3pP8ll57IvFJt7e1BhwK5UqpmHsBUNySnaku
aauAi2qKPEKdT2bFUg7RxTe6XC05TLnQjROKOZ/cn9bhxrqgfYIt84n8IOKPnPOUUOs/vtISZoWU
HCCfvfktJFHLk6OjbA71s9m8j+HTcl+btQ7LaOV8Z6Av78gc/NPKeaDRKa2hfYKJy41AryIXpBDq
LA2k2JLAF0tQkWLLGPTr/cxvN472+GGt1GCqeGDqPg9ga/YARtn7brKnTZbR3IWokZiqW0DT9AJ1
maylowuR0jxzHi5pVJdMKS24cFqTm64LEsMHJOdLs3uQhYXdvgl62hxz+eml15bZtt5/zmFbZtIC
yvIu9BpotJmJLGJGphloJgv7QaofSLShjsyOgPIlYzpo/9eRxNZ00u5A01EvEs3poH6Au4APNJt3
QDRevVGmmk7sFRa35+LitkwQ5hYNQS5hE74NJIoxOrGbkzGGG45P4ZrFMJxrktsw9ZpB55bQ5I5r
exZPrcl1ixWo2uoMVbnehnCH7NvLNgw0H4NtmPOUnIcsnP42jhHQ4KCMHFevExENhsxZiyQadrqk
1qD5DgeKe/ZONGbUw3dEIr6/0ZkdiHokp07n7hkf9ZNBHSFtvUU8eZsHGnAgkVs6D+zThmJGzKhk
cxxEG6Nc5tQEqKTHgFmfKo56lOqtIxLJpSmuJ3M+SKoKSinuMCTINwkM6TxslTZoSNneWL5rzZXI
PugppKNvJ4ixUidTPhyn/kptp41oMgC7t1UMKqpCVipm6oXgn/Kk9V4Bp4PDj2vRSXSqepUsnW07
JMLEfMIumGnTfabNIjxo1xys+cFMozvt7eQNZhoapLojTZ+ze8Dz19ouo0WJqZO4eWSv2dpw1EGR
l/amn9ezg8Pfk9y5FwDHqFSdfl1HQJcT0taLRAeDG8V4GGcXVSDHq+lrcipVcnc7jzVnCtLB1fQm
iw2JFMGZcoTEsdpCsI4LAg295Waygo6UKz5b6qWgCLVl0zAqaAuY65tsGZEFoY32sBfhhDwUd0Te
jyYTw9HoUVnUv6R2/U6eXTwiT0eMzO1oMkUq333y1dFkmI/rOpQ/0BFtmaaJ5KtHAy8zkpF81fmV
ZaCZOsXlp56lLdMpgSdB+lLMefJwyDW5A9ZtmbqJRqG+q/noBCfSGsnBzxv4ox/2Mx4AkpjPHB8A
Bg9L1HpdBT0sq83nStqHMTAMPgMTz7k3Phv+iiObvXhrDYE81Mbd1af5GZmjaEYfg7VuFAX1+9Zd
ZjujE9zdYWCg0f4U/A6GX1jvZ8jpadu+5jF6v90PQwMvtK8EfLuuxtn2fkPNVzKX0Auw2KIlbtGh
MabL1jKjA/J5MrczwrXkzOr11uDt/X6ZWasHIOvnZJ5Y9mCc5Ohk6sODyVJq50Ih0g41m6sicyxp
YdLTQdUfF4KvhYBbi1alZLZVP2SpZCWk2sNCqwyubjR2r3s8cJqKAHlbJcud2eLNAzM/1mrxD/3h
gleHSD9Pw0zmIv7fhR8og/ez5HpNeK6+SyPWYoKEq7uD+lqxJ1KSSUntNikLSRz3w8a6LIh4HlIy
lUdGexKX5WXwkk1F/IuWDODlmW7xbp08uDRR8/TFpSncBepLs8NZyak+QG/G/IDfwlFf49sFHd9d
sHgKAPwb3M8Yp+JhKpiXMEpvJl7oOZMzdIMwGDwFoEcwxb9AASubYMdSlOLcXZHXS0Drtqbvbe0R
RP+0g5hsHyPNpEHlVGsbCu5FaeK9ZWE5H6sl2QVIzr2+TW9wfABfXN+0x+D4AB0ovWnf0cbFjoeX
ORvejji8e+D5dEQubbc9DN/RZJK8WPZ5VPGIvB0tlfFXfycvrhyRH44uVdVP3s4yOXLwdowykj/e
zrIDocerfGb/fk2DUncGKvrSzKh3f17K1wUg+ZMS1JYJkmRWXjEjy6Qtkx09Kex0H7v1OOXTxKnp
bMfBS+HSA/GtydOr/cn//9LsImiAy0vJiXVqqFDf+wNLseYXeoiVmqO1TpSbNO7MsuYXyk1ondkc
J/infmKQOZ1JRBd58k7K0w6JHRAY96X4/Y32UoACz7UR671iFHiO81o09WNsLvOggfpOnpXghY5+
BLrIGbDaYEX7VIKvjyiymLgSfJjNDjrOfUBF1juFhCWfuyk5cJpy9NGaXqQd5wLzaTOFzxR8jdbB
B3JCdt7iOYATyCM39+5uod3Cy1lccws9d7kcy+BWedpur9UbalZCVGppivAUUqXquE6+Tnrw5QYa
HcXAA0Zs5nFNeMBQO/MW9SF2mUKAqM9jR+pvGY+P5E9qNTD1IqOt6t3kRSLb/Ab3MuaXca2E+rLl
gx/lUWJu7TBnBjEm61oCE53oxO3v1hKIzKDa1HT09jEyQonm1nQAtbpsbTHqXSKD9azXlYHXlm2R
y4zXlk02M/5eK29sNpERGPB1rbQzP11Gc3aJBDkqFbONU7XLxeYtDiMvKN6JGOt6lxofyKRhF/QS
aMfDba+uvwVnrORkcrijsWO1zgycsXw/Gy0FsDBsf60vyzIiU1lfVTM+O306qptT46HTZt5wn2tO
AGevh2JaeMBwv6ESDBo60qX0bsk+olctVpPrhc40V9sMJDsLnI5vCVIrTf4j+Wt3Kdok2GuDT95b
+85fZ+TSE9gj2x2RJ6nx9pUpZ+T5aKnF9yPyM75Xaab85ICtSzL+9HRuy8RDT8Z5aWx4L9NEEW56
Av7LVD+PxF/GzmjLrEKUmjyyree8lttUnueUdSUMXdJ3y8EvzRRZKkCCTvb0SnsK89oyGxaJcHdh
Xlvme3LpSfZyPi+IdKVkcxggAjCYrLH0jly+1KylB2QcdFMI0HOrVVeslQdAJ98Zk1pQDC2Csl8v
hXSqMkGzbXsFkIHb5fhOTzto6KB2314/yxYQzp/bbP1tdEvrXrJvAqRLH09rXSrT4WB0KftTPMqR
YaHWqZ0Q1+hM527NGa2yCpfcrLeTAQF8PuIXijrcbQ2vx03u8gxBt5bsSNf03QpmoNEeT0bChhK3
3fyQLFJjMOdXPyVCw7i7NmK0d0+kZKkjgVie70eqdUI+ncTGnanXiiGhjqfJdc84dWh5Y6myhLRk
7kv9O/fgMwXuSz38Rqem4Qkt+mzODk9ojF+wVjgJgIJNnvrJIWJ1XL0lSYmb36VifosbIxU5n22/
TkR0m3mlcA/npvSzNrs9YqjJv6zTKqyl3U1S2nSzJ/Ri9kXKgG4sRQazb6aiyMCl9vFtq0zvpzV5
5Uy+YwHorTowOoSEdtxFsmbu14xKKrkNs4eE/lnKyJmQ4oCQom7tzasgSiCSPEF/n/L0kPGuTtmE
HIf0dWXzbNte4ToO3pIshK/uAs71stH2Khd5oievD6k7Nb3p2cFlIlZ0L8VkCns1stOKaUfCZYoM
y77eciDFkSXiLdEpjODS5T00IcWRPVqk6Pxdr6vjsV/egduH8+RG8p/w3g7IpZraZ/m1I/JyNJnY
jshTjEfkUjXtAcXPyPPRZLJ0pPY+YD0i7/mEHHPpywZuwA8g+yCONJNT5+gqZ3S/L43Wm+g/VTmD
fBhnyg900ONynKkCCmieRcx58r7wVldgnBvjMBB5seeT2IsTJDqgiA4q/Bg2scdI9I3341hfduOD
b+hcl1yfYnWk3vgEG6tsZBBwN1KLBhkONZvf4iSbJJep/Vlgn3bB9K3DBnuFof6H3+gEQqC+hdis
DWfUtyT3e4NIi3qoO61pGHbKOSQD31f/whlDpcYbdHx9XIBLXjnTaM3wUFGnH8SmzNE08ruiFIDZ
DwQ2dPQvuzLQdODtJ4smIgKT7F0AWjnjQKxlJJIrcXd9/n2nItoKcEnNMK5Ozot0/VYfrKMauTQn
lJf5GS+HLyyeuirDMPfZ/DY6oKRoyTmaKOegJGeLE5eeUt/1rqBk33P/q7VEomT/TmcYaHZxsUC+
GbeTWy87RUBFV1P9kBIGmrqc31RWjxLb3i1Jhx94+3hr8UsZRTXuTdINnCLgBOdq7V0C4qaXYjL3
repXT/LbW9hsOAVq2dqvQb28C6Yyyf6DajHQaN+H3EBStWKZU/ojQqHcF3h9Z2b0uK/R3AYAw7Va
j0QdlVi+yyM0+4E3nKoxu5Ke9iPrzQReOOOwHUyuvRhAenLoGMlB0Om8GE4h+tKZ2geocZUTEtb7
j77GLiYpnhO0XH0woNb7Dyi5Hv2bBh0cPKQq57f5GFBytCs5eIt9qPDKnKdnfBuZDZy2sD6GpX6y
u9a2KqDBi082TxH3jurG2fj4/I46mNpbrO98RC4P3R6Z7og8yoO1D7n5I3J0tvqdPPkjRqZyxMjU
j5bKUHMH5NLQ2idghiPydMQZLjf7nZxdxTUig3N3PcmXZArbAQczAE6sL2sngYPhO98yJg7G3Udj
oJmwvoHvyZLyh2b/3JKfXIvvb7yGxc5IXODLfg2wgby7wDu95gXy7nwQ35oguElbxZCCyXZ0pCpZ
0uhvNSRFqG9pfqF4JVQ5Z833Tl68i2/jGGqsIQRijhvQ6ChI2Zkid0jecqwTl7W5yMfU8rVL8AqR
NLlzyRyX5CJwpeB6z4EqF3oR8jbllOb4IM+t9xzNklst+eWMGAns8XGADYANRvKL5vTIjnGML2ts
FWDCnBSTfasrbj4u5qcfmoAoRzsnRMDp7EtyH1sVnNHI6EAVr0VqBrcpr0IQsd2X87JSPXIeT0nW
KQPABtlj0aapH292yeIIG8VlU5KA+kbaIb5IyeBSosAvdUvaIj8Q1JMDnbiMJkRLmSQ0MWKI1/WB
BsAbV+wMJC/4bjfi9lqPAmg8ctOK9dlEw+TErQOmO8UofEO/H3kYpubNCEPU8KZ7TYfyBo0ffqOL
5dCXjrOVjTU1hC5isfQWN0K+reY1FEpvD3bimoa8vhuVbS3YaEnlWu0nLM7I4nHNvN4yUCRSD9Yy
gUZ+928fxtmlVaK4arcmwH9w82SDNeRS3jhUazEGAAjjUK2lOOOllkFh1mc1ow6Ze/b+rnqBEeK6
krYXkJCgdOa2P68nPz82c1tKQFw2vJ26wadECwXFG+2PRSgTeRrmXMw6b8OUi4n0arnlkx9caKuy
6ycnGj5lKuqUaYSSBsDU/ibqRjJfJ+3i3ni8tmCjYMHex4xH5PKM7eOL/YRcXYt79PN6RN6PJpPS
0ehJmRzbpNGjpeZ0xPfcjyZT/JEQlLNdLe1sMv2I77zSJfoE/M0bcqEvS1a9h5Jng3ZNE5AAw8bz
GikEOFWNhWyNFAL086y+NYEqkt0R5DDaLURHTYbY7bp4cnBBSeGkzZRzYcjt4Us6vlm4i0Iyv0Qm
bW18XNZQKzUjT0+sagoR4xWdoeqN+ZBBQ461zWRkU92m+rKWGX2r7oym9bqAj5683NDZcQVKZpZC
qMOInqvyg8WfAOj8W7uuoUu4EilYcors1tYVeyY/lW7lO1a2XnrCw3OSLJwQ0jOCHtX8VgacSTdX
TtLjOClsfSQCQt2cBGZMGSZzEyRvAdPIbZ/WAhbQeqnY0+HOzVFOZ4pIoiax5mZxJ/pP2NrAcaHz
53O2loWyxRuYei2nMTwtv4dP6WEgXoydtWYyUnJbjtlcOemv2JN5jIl5V7RPTeQMa6nep+kAMrmE
Zokp+ngFl70lg3C4s+Lg3OurXzUGUxswzLprxdxRYCbX4s0d7WSotm5LRu8PxNx67eRbwfgv1toT
AC7u2MFS4BHrrT0na+0JT29V3knTqwBg+n0xbxO46sXLOetMSKBsRu5euFaFwK0pnPA5zFm/QMB9
99liM7pO32m3xrLKn9jUmj1o3Oii/a36YJ8bO0EuoE9BSpjmIKpuczLvNoC1N8aUXUs8yi1vMMQ1
lzPdf7G2ZLEne7itsZrjoGovOVMjoC9ZTEns+ltfsrvb3lricyKNECSfZ+BP+pYL1douvA7c/R/X
ig6pyekOmS73NFcgLKkrR/MQFdmpib1oGhwemefB3veMQqCg9n1KXwY2bjLFOZP8uODMewkVnnRN
Cg3VtEuOhyWudRhO+1QFitTo9jIMeQX/N/35P2jwpv4KZW5kc3RyZWFtCmVuZG9iago3IDAgb2Jq
Cjw8L0ZpbHRlciAvRmxhdGVEZWNvZGUKL0xlbmd0aCAxNjYwOQo+PiBzdHJlYW0KeJyVfevqLDmO
5/d6ivMCk+2rbMOwUN073Z93KNgHWHYaBnphet4fVj858p8hOazI4FBN1ymlw9bNknWLvwL/+ZfI
/9NG+vV//vHbf/2Gv6GY5C/++X9/+9+//h/+8tWqwB7/519i7QXw8Rf+/Pvffs3/88+///anv4Vf
f/9vXiZFXqVH+hVDJSz1H7I2/qamHt5/cwmWUujyl4PegK/y6/0Pf+78r/zRP//x25/+Gn7xD/74
j9/i+1SDeKFcfv3xj9/+NYRU/sevP/7z819joFfMqZ9hSjMwsb5KiuMMU5OBSeVVGqlv1Wxgcn61
QXod+60SXvyPWqf8xcKU14gluvup+TWoq3PVaGAov4pZJ9g9U3/xfy1qnd8NTGeGaLm4e+71VcvN
2Ud89WHO/mcNk0J8ZeY+51MJJC29eEdPTNI6cveOzuy3oMduOSViWWjd3XKmVyopKZhuYAqzmDnX
sp8aXsl8K9mz1/JqMSg0J/stJnuPSX0r23O1/KIQtegMgfm3P0SCgwig/HmLHrhuFb1Gx++jJXco
TO6oYIoVz5hfzIIKJL63cf3RmNqLqT/OvxlWOlgSY2xJrTuslIFFWjvD5P9ppSy9xtQMPzA1WJj2
GqOpY+a/WikrL+Kzuqho6dW73s/IN7iA1OlTViuX40VdGO8D87u/agr1FeqIHoZTDC9iJXWGCWRh
xiumrrC3CA9TM4ygMROsgLHwxEAXXHISsPRqSZ8z2nVYeEYdHsETpVfqOXkET9ReuepjWYJDvgbv
xyN46vwtw8c39E6DRaobPvo3vWxmDRp69ZCVQ3+VoNm6GALnyKxf0nDXSdBYo7vbYQ1aKCtGKX/1
j5lzf43Qm0eFXBjDvZQL5tqvC1EttXtqITe+FViFelySW+NbIVR3f0zdzuzkcUlm4Sx5DI9L8uBv
Rb0fK+RMS2aL3C+E/AMTQauq8XXDbiXxLUFGedhvswD3fKVfPiC4IAO56ColsuCl5LFbKZ01ttZL
lt0Ky3gPRvDsOizkMerLq/zVwvC3qLiav+ASLb5eKmw7jWpQGG7QPuortdZdtA9mnVKzx8o1Rr69
DLsbg6JChKlrnHYLU165GB1tzllzfFH1b9zKdm3MzaVNrfHFNCSPn2odi2hZ2jDtWIVEV33xdl8p
dld9sT3G6iA9Ul91hFcnfU7rK1BIbMXk4dGY2NClqu9Ye062KnDvxQsVst0fsUpmZVQ8vmCNzTSv
zcMN8z7b/EPzxZ8tDMtRDK4qJ/ZlaqcrVf6Bocjfau6lSyyzkYzBaddp7Dyk7LE7scjGYUTrhuQ0
0qIKxo2ZFVNQ1tOdracPfwuur+U78NQfgeecH4FrI/UOvMRHmyn9EWaqNo7uwOkZmUibLXfgLTxa
XS6tsTOU4XGxTZYVjBHayHZATaJ4fmAWtyfynV7kUvisszyIpBfbL+kMs7hGcNVYA6h1biQpwvaL
Qa17K0l8abDJ1tz91sqGQdEwFw8mMUVycQP7cNqQ+3M3uGWxKhj7rc5eeqjJpRVfJCH07u6Z7cOc
anuC48T2f2vR+3SKfH+2Qt6nE7NAGvqYxTpUmdE19DrLY03GdrpmW3MXwr8bBu3Lngv7m/wxdx2+
a3Ikxf7Wvkh811Dv+lx3+pNtwRgCud9mt+GwtT4wxkZid/nVivm2fQQaHT6zxoW5xDLbF8zO0aNf
DmxDdm83ObEFSaG4q6QBazV7GM258fXYhyc0WTz44gpfriwQpbvCl1nQYyrVo0RmCzJp3WUNhcxe
PjNLcY/Fck5JfanfqCq4hS1E9elgP83GxBjDQ3oJgdm4Dk8c2Bxh02tUd53IWiiTOmVvd14huzQx
aZE25m3JiTXgpebar8sefS9Gk1m3h83JEHPyqFIq8c1UXCYpLOLlhrHhArYbxi4s0tEw9q17B6+f
/JuTtRibu2VccOjergG9A7m3f43Mfq5SgEMYErn2QU14AYtqHWuM14wAhVEvN44J+32vVKIrl5Ud
/BSSe6FUgnOlMVFvqFIbOxjkEqWy70DTf/2eKP3nzWIrLMTCzNZC9o5NfGXHRu79R3xn526Y2jzK
E+7sQu49Bf/wCIxsGR/+YetVr3NnGjN52VzpF79RviCF4So2gv8fc3Xxxeq7NS1Alk3gCwZ2PL27
lnp5sbLV+7F+J/z9onnnTolGfbPcenP6Xrz15sKj1Y2433pz7RF4ie0ReAmPwLWtdOv8ae/oFryk
R+BaQL/zRL8Gp2ebofGICeBa5rh1aRBVaLicPzB3ui9Glq+M6+bzm8WdSmyPEyIap3W7hWE3Mmdy
YTKr7wCDaNnfCQYXb1PfqneCV9ngkPdtBzdwGysu9NO3l+geGxxsmioY68o1Njgq3hpPMONmfwPx
+zS8/aXAOA6dntAuRV63eRiH98c2u6ac9XgSTBK8RJ1gbKiMTcVRa7w4wX53pTJnBb3uEu3Lh5Fy
grEeI98kbFA0j0MT0au3rjnLRkNB3Th8KvBtU0alC1w4r3KDvd7gf5tNxdKjy/nwBtm8Lhe42Gv5
yM6NRo01XHKCQ5tdxs+5vmrWymVxx1gwW9BUsKEyth1yMhS/MScz3oxHSx5VMlOXmpaf5QitMBWM
fFsvGMFcIs3F9pgdcQuN0mHXGaxLSqILzt5fgQjnkjmDkVa2qpkMNXlkKKyvWzDfNvZjSeyYSN7R
gov9/nJ/9a7vjjX+B3chlic6qrBuHsmce4njVb5fuku70tKLutZAt2fq7RVC8hQHfLgsYaq9kqoB
cQOqLkxkf5uoe6SrLKxsUmYPxRLqi+4qCPSx1eypksrqOmejDm2ArgRkKRUPOxWefC5XV8zeXmKC
x0DDPQMyOFq5ukRPjhw7L7XodWxgtOdXMMpjCYwyE0Qxs/bMVUU9U/b2g0DfQmHrrLBzl3puHt7h
3FGtLhcQ6+yWXZuMMvJ/qqs3EfuLObikoMJbHj177EQ1HSkkzrEosN+tbcS7dzYiuVKUYNkENWpv
33yv+6nj9jd2mz3nYNtYy95tlENj7tb908rpPvb3CDzFZ+C5PwLXDHDrXD7DjDGpb73F8OioRds2
t+D1GXgPT8Drs9WJyiPw0Z6Ai0GXdzZpDMgMiGeQJf7FRsthDOWd4CMOGYfozh+YJbUyIds16G8t
ccgfAyTvhBgpo2zgJgVjHcjCgi5PMc6ey3jlTmqdNa2U3vfjZx3r0LLSaz35e0aSSw3JPXvDe644
xh+YeqM/WOnVjhDK6Tc2cRyOZwjNw5dkalNy+QCBxhlP3eMCzmiNXa1zZxQjabTnrnCcl4BhOcJJ
p3VvDL/EdMlkeMkG6BA5CHpZ+2n4FDGSiz6kEDbF/bYMII3wKtksY51wxBLmNWexpxzEEUe5wMTJ
IWT7MWtpvKMCPMRaiTwqwENs1OITDmVP5oh6L1LmuIOdbe0xPK7OPbzduD0e2OqrPbtHGnykkZUA
LZ4Jo5yv0u6RDiG8EjTKF88pxrf//zUTI2mzDf3txX3JdWZK7XUdnLYZ3P+eIwrLT49lPKGcRNny
SC46e1501uLosbSMEMsFOp0HYyRCaO5cfCLkSueuv51u1k31VdqonlRWKSgaLpn4mkW42+OQKnGX
cSUsJ+MiH2lBzjpV7GXy9BryLnvI7vWHvMuYmlbNNnyIt1AJBZ6+Zez3ytcUheYqrTrya6SSL/a8
N4UQa0tNS5R12diZZrjisQUl5BBr8lkSUybUREVPCxDMjtpci4ukmqW7FwErP1a0WrktOZQInrdx
JZ4ny5LZMhTX5CIJng9Xu1FDTo++4BYcIn9aSgH2aoj6YNc45Av14GRTqq3dOjHaELsFr/EJeNba
+xZcs/MtOIUn4OXZZqbP8z04PcJ70drm1kWKj8hE4RFm6NlmBLruBP+Tq3mCsT4SX+2U5Q2qGsY+
wSBAhSSkD8zqI5UXTT+qGiV48n/4XpasoxPM4iPVVyBRuJ9v2XXYJpjFC865KruHQ3w/i5+9wFJ9
Sa6h82m2qWOq1f10Z2upJHWExfVCVd108+pOL0W+V0oTXfoDY41JqaMbSaH97t0KhauRujpDtEY/
k3NQ1+S0OYxsOuQ8uscWfN2z+5jpAl+OZgN5g6bDEjG7IO/dueEPkWHRJX9ysBmYNWvZ/MnBIhOL
XmfJn8S5qXo8kFk8gySw7Xkps3jOGon9fjKeJ2YQYL9OZhOu5OjREyEyy5NrBiUcPaNSbCSQHada
Y79QBc4FgufyWjzawLk6YjFWVTm5kPEdm9njbyApsJPHbyh/i01/e/GSAlLLuqsmESPrpOXVvgeX
xN/KvXn0LGz3lVqv1L+T9ZLYXqr+GUp79Rqv9JJz38aXFIwu6HO8LcSSzK1j8zt7Okp/9izBVEPl
omI1+36BGFlqhrWsCR8Qxk1X6s4xBPi2oDwuSHDywBBRKelCFE4eWGDnWt9mizuTG+rt1TLmmJWp
m2v2iFuZuMw4irHGUviGpLuUPOVWpYahVPdUNNj26NFTFBXJ6n24CqcyF2SqyV2Hfe6cqHmCVwch
zaF461B4F/QtSntvsM0ihuiRhiIUa40eByIhUorC90yAfMhYySUx8+MrZX2EJSeR2YC3Qx75kCPZ
4nDvFNTLhaztk7ucRGrhFWPyzwDlYK7FJWSWUfXjXhfUG0J6ep07l01rx/scyP4IXNsrX6VMfg+e
n+1dOoV8D17yo70XzV73LtujvdcYnoBTeLT6jGp9Dz4egYu623cMQZ5NF9t33zEkvsvM8rbeNSZ2
tSRPO29rWSXncYjq+rquF72FWtP7W1w49BYSE/rr2tYo9RQo+HSOLU9CrV6se3LPWL3UdPXtEwzh
GSu6R0A7IqqaVDY61ZEu3xQZlkgd3zqHDbNvKxLY/CQx378u30+IWna6YhPnfWkcZdJ79kslvsaI
yaMDSuByrMVjP7RBySNGj/1QAocdPGE/uHBp2ppb+ibQLhFdrHuCGUitGi5dmHZZSpxPMMYSggtH
M/q4767xebm/6XKicXrZ5aSOJ2wiSY9Ns9/vi0dXUdLTPbaQpiYzTPghuT0CsffTXIpnaT9U+hOK
M+JQcK8xbB1pPM7mXDyJhpM3iyxOMDbxMKDGV5/hNsyFpMdenggiWp6M0K8E/nTdpldKhmmMuVqQ
H9XH8FBeCiFW0jzKsR/5YsOteBxQiG1Gaq7AlFZW8tpwHhtuadqwVnk4D7RIB0yezJfxrqPby2EN
DdkXzTtCRXlTC+TJfE2ob0tXekv5dKP7er/m/srB6H3rReG5JRgdtITMWKpyUFz7+9LypL/qDO/8
wNw9E8KDo6zvcZvehhBaTUZvWVwgvS3E/kSq+H5mN6G7dxWhy8DMOdjeVcT3JLv1V+x28ryOUti9
FBFfnRTTI8WFiFqX5gV7tkXnEtZb1UMfomV81Cv0nSxWRCCNKWKrzNCJprlf6sioouJ+iZ2qThqh
i+84yisQPbqpYla8+V2y4vedR7RFcx+Jq4/A9VHv+5o8Wj33R0ct4dFmCjqPPADv/Ql4pUd4r6M8
Aaf8aDMtPNqM+GnbrgUnP81pcfLjp33qQ62jIbVpIk8P6jqRkDX0t5dQ208i0r49CNsGY9a8fV3C
DEcNPQQVbqzTQ1IjrL691qHFF0mdrgcz3qmQXxe+o//rFLD99gbStknDLFmF7TWT5b/GTEJly3wl
2VJFomozaXXf8QSWX4tPGAJBtlzkNX1/otLeBXr7piRsCPIlkC625yg/QmvS6H4bgTcpRD3B3OQu
JbzwDc3ki5eJwvdW9X6tp8de3BHQ+PpM6F15BEi3fZAyk5u1YffOndHQuWp8Lj5RZi9Y7tytnOZJ
3ubpo1zZ2pjP7fsuKhW9a1zZQEcSRtYjlZDlPSUplbA0VWFqjqhlbjkmm/kpaGwt4cfREMsZHsVL
YIe2Jlca0JOkRi2sS2+TyHoiNq3qbt6xCqvmSIncb+d+ZNPZTzuRO7YTU1PLRutZoeOktKz+wIQb
Ex8eW47R409pLplKdzEO/1sazuw5oOAlbHoK26YQNaDhbxoeVdCBpA+jvW2sh6mbpcHbSYfeRvPG
y/xkcXYSHDZjFyyOH9LaDYPaY+INVdr+fM9YtaJhYHcZtlZk8mpBXEJluJun4fSBsSVnxLZNfqQx
6ywrd698+IFhpipu9Y9UspV4hZqP2RfwtE3N0yUUWNW1cCVkJ9+wsq9fvC1Lsdswlsxdm0a+v9mb
cdUYZVZjMbpqDNmWfMG4ahWVbbMN+/fqGpVufG/5+6Of0PZ+f3iKLZfGwslbjHh2iC4Z2KNsFNoT
dotaw957i+kRuBaze+cyPwLX1um9c/ls9TaegGctIvcxw0ebKc/IVMqjzRTNV/cxw0ebqeURE9T2
aHVKj8hEtT8CH49YDDda2Vaeos4uSoPuYktPTzB0vI8VW913ghkvmdTwAbnqCTpVyulTS6MWdvBE
5X1g1iEpGKkAKXa+VRBxARlO6yyBTGTdRP/o6BUmPXmco1c8nofo7ofk8Ty766D5cDeksENSYI2n
ofazJJai4ZRE+Ryys2/FbKdwuHrSDS1S1J7XxjDpJXMV9sdCDmsJI3lbTjDpml5n6VKCx94Y/W8x
+6RYFHqWwCTazadO7n5QUDY85KDwb3aKdpBTELhq2WMMZi5mHs2Eayg1s7lTfUJgCk+NLnLQn07a
Ue1lC375tKz2vMOi98pZo2fZDnt7RV59T+vYyCn8AQlw7b+FCGyvrXikyMw8SYu6PTrc+ZpT8raM
TqVsqAx3y2ksYrzm4rbDXXL2g77noahjBRt8Lug70pSIBhsaxQwn6Qj0gbF+DRurmAqj93MxsmJk
qu6eYRHm0TwZzXAUenDVU0ZSZ9G0WILh492r19nPoDn8ZC9cJeRXbdklBdJ6e9NHX3JVpXNGdy9S
9i5fpZKSwCVXFW3z5clzzz5F0u7NrbRUTcZXC9mV9oIGV1L4eYIx43UKs08p2SWX9DkNWvks4Wy0
ykjVP1fj26Tom92O15GXhpZ9mo53fs9elJHvSy2710ANrDB7czVUhdogJaV3Dw1ibX2yxezVjBzy
ITpmXxcCZqt4g//A3PaYy+XoMVJsfqkXZDtqOk97WUybjqlTXcEsLQTSkYVy2q/t5sD65bgy9nU1
zCBUi/7WXdv2UdFqtqjfLMPeEIPp+pz25Z6t19pS9ugC+6PmrNZZrj28KIRR3HUy636p7T/Raqmr
QQJYIXcdFvBoQG6ymROTM8WePXJiflWWThcnmLsmcw0TfGJ0UdNZpQdqF0farzv4upXyjhOqlmFV
/RVapwvWcnoKIH9Ni8tieUjprUaVvTWLdO2pHvdlaeZh0Hlxi8/Lbl/gg14e0ozW2U7LR5aZsw6S
ACyjW3uKfYMxb4V9oRCSAKQz+P5byLfK2QjnXTJQhF9iuGSZF4W5WCU94dACo4yGSyrcmIuyW4ZD
oRimugJeKtLyaHj4K/AHa6ruOsini8XTE6WNV5HMEGcZmOuSqbLnQHYXX4X0t7pdhy/eIqW9C9pP
l+qPrbkvL4kR5rrLOhXtWgq5Z0f7g0gheazCrvIRWTnB2MqajATd7rIckrlmLYSzH/YIZ0z+hMOb
0G6tFcmsel1bHERoKxRckUXr8Tl/9ntRQ+u5ww7fKtfK9+uo6Uq5fp6j+H5dRGt51EewrVypFOcR
je2KEarHt1JWQ8lVnVJX04ydY0t4MD8khau73Xm1i5jVWzwxR3YXi0O8kE+nhgYJf/pWWWtoGl+m
RqYv+s7FXq/kzH95P5mvtz3F0yPw/mj1pK+7r/K0HoCP+AR8emTfV7yghOUBeHq0d2Ml3zcJf7QZ
enZUqdN6AE7PVh+PVhf3a5u6GNEwKWQNs3SVY1cgidrZ15hIbahYbNuETHRMYNs0KpilnXh6q859
jUkJfK3E6O6nsG8t4+9OMNZNw4SrKr71JxHW4qeOo+7utM7SVS6zG0RXONwLPpspvWZ1TpvggHYI
1ORp7ZPEZx9dYV5kUmfoN+3N0Q6hiabcl7wkzHqm5JEzZUyV7NWH4WOG0D30JYyoadmjVEJf26I5
cHEQa4GznN1jUXyNprd8NYk4zDfh/X4aDDb0RdlzsjRW6DlecLKjgelonb4/Q0b1lLRO30sIKnBS
NRJ721VuvJ3wfVlMSYyb6OJY3Lv58LLfX4Wh1aK7DlX2YvW37GMM6mtKz+VC8k4wwoLZPRcysbo5
+5KtNY7R5vtzlcBGCGnRui32YKMuyFSivRghyypPJ2KryTEQuA5zhqWAphyZYnv+5628SKLqzjqI
7/VRPHmEP5dCdrU9/LlIhTz1wP8FHRL1ue58WzQs6cnlLwz7PV6D99Uoob70Krd5QSnyXan18Tr6
tx51HHsNAzetkblTbHoWBsDl5HItXLBRRnP3wxQPhiluWkVWFk62ochjJFYmeLjIFwzgemAUtZBd
eWAz8/N7slBMMxN0j3GK9I6z7ytwUn/Nd9191QneKaUtxR7hqJRJUti7J5zM+E3G8LDb+SkoddYh
ZFLG7qktzGyiodXo4l919u3I/xRqTCUV8PtbJ+pL4L7/QHsE3vsT8Jwebaboy+m+lOQReH22eq2P
MFO1gr9vKPBoMzQebUZclG3i+aep2wlmydnpR0uZss27QxSJhrzo7SswcBmHrr61dhHofEEKq2zz
CdH4elZ7nL61TFfCNDW1ypKOU9FSRmGn3wQ0MJJ3jjRwTkmIyQSNdet8IP7d5FbYZkTCiZn9n07Y
smk+aHvdUne/NXBJFRfrCQ2Lao/euTCCd2YLbcsGkA6Ta63uMiBwS8XbMsJRbI4OjwkwXjdGw9x3
caOKUTDFX5d90jkX/bTuXdyoYQSgz7Sp4dyaJZewYEfWVsweyZPUNVSXvZDpUqUD8IKbE0yDXaJp
ZYNJyGmWiUoLLk5qPR8zY/bnEu9nZpF9XweCd4hQXfbPBfW4o7m4QC+QoHF6663BuJKp2s66TM8x
cvJ4HaknWTr97/kio8RsBuw+MEvOSJ6je/ZkKDJyJxePDAVtPkhj625yLuqJsjml9SHQdvuGUmgW
VwylrEKGbzS6vh6WGF9F3Vm94rb9GYi5T2aS7zkd2SJdRq856GPpDNWXBjQXCJFcihfkOY7YvXXg
G83ZDnuljcAWkbsdlKGwWV088tWERjihXSiLvYHD7vDMBfj5iW0Egi7fvWX3LoBvFEdQ2+tLBzkZ
U6ZlMVsYPmbr7WIdx8nqx0Sl07o2VIcI96jD44qKkKhUFjpkYMerSNuo5e50jMLK17Y2qBa3IWK6
h9HzNiwTMTj8kg5O0Qlakmq6/GUJc70TsLfmAOpJshRX7RUDJuMekTCrap2IVT661Drr9vAqUX97
7cKN7EFj9dy5VJpjvospPSjP6E/AsybrfVvtR+AlPQOn8gS85vAInPITcOmT/QA8tUfgz8hE49Hq
sGnrNtfwM9a2bnMNI+rNO3TSB2aJF8mo26jWuR3dmtOrRrgtn98scRWMvUQHgg+IDavAi5pzRU+f
tkdAMEG6T3xgfr8N++BC7OrYi8ckZlvSx7a+LJpESfPxatNL3czAGrNCzeKT4pG7I5mnbtN6kT04
Sx9PMOZpMuHil4lpy/5OMB0Z1t52EIaa7viJ226eJtGku0ozlj2HJmkWkfS37zwovIsHhZml20FF
+UypT6iCKoUoc/gcjKOTjUyWWQRBOWYz53QvUAlzUMVpcFA+MB4sd49yKEGYjfX2+0F9wWys56zz
ExA+wSw9uhMbTqN55ER9weyl7XwLyd+S5neCuXOy4JgNwyZLj+5wlDotZ3CcN9YcWdNhcRzxtlLr
eLTugFPYygVbn2A6S3gfHp+gAID359JOCgBK95RUSWzgVK2/F68LQ5NadaUVreFmR4s9GZDNKI2M
95yEZEbGkF7mtqsrOtoYXbwEupLFxOI3EmKQ5F4nEueqyUUEertL7p5DF5SxFaODbi5NjGOSyMde
ocOTuxNnuHKLOFtfBLGvaO50608h/bDnq8tN+W6zd8aiyrwcoRerUvfyRfphHeTvD83HqF+pkpPP
lY76mA/M0nm84R0vRU9cJSAWcr3A6f6c6AATWvTOic7fy7Vz59RENM40F/9FA4EuPURPbGz9vRxY
FYfuyTNSFPmWzp7EYFwuk8G1RdFUoNXhXq8Y4TTEr9nTnFAnMMx+7m3wYyLlaX8WXw3XZInuOdEZ
KI8rs+JkwKPFhjEIb/gkalLe5ipqDN3Py81PwFOOj8BLewRO9Qm4xG8fgNMjROb+CJHl2WZqeITI
Wh5hRjrWfQ9O8dHeSV+RX3mt34OL17qddYhMyDJxvZ1BGiPmxza1zlrTj06eeDut24FwyISc1YGn
b9kgXU5HdWC107FOMPUYluOcC5WR4ontx9miZ6680zrHqgUPocM9FjqtSP+/03aahUGQSa/TrRfK
l6f0lHJO3iriKkl9anGS0ZgmKUqsI6f4LhpFrbO0DWSTObc2PBTCKS4y9un0rcVxbojZKFIscUXk
0U7n/wOzlPSjs3PpHn5Sojktd8/MSSbSh+yhEO3RZ4rsHoVS0x+14Fy1R0+aCZdlYEZXRF33DAZn
eXaOd9bhG7UnLaOLk9vfc9n2ciM1/TKIz8EyHC5pQbYXHDjUo2mKLg4someSH7I/FwZjBemMvCdp
hgVeU/T2nFGQWY2eWxzzcQT/T3u2hf+oH5u39pbjUQ54uFxbPCNC2mWUh4Ofmo5GF863KnuARtGt
3f4q+hO60iU92ym50oUOgNI00CFXL8c8VodcaAkxL7E9KdC8s5tvLWmnfOXUrsi11KrFfMzY2pMC
DQCr5uYleojZ06UqmKW9OqaEW2m3bwPIJM5aKtZW7nBlqXrogYM+g8p7aqH6cMbnnP2AM6RhrnP2
lo+54M7ZkSZ3owxlhtdwBUeGKktuvUN15owsbdD3zIzmgbOibY+eykZNMCRdKxQ7EpA19yxRWnCz
pwolqbWby3YZz4wyUKOal/rEcYw22BMLo7+yzJ3bE13mM5NWPfYdsxIxdqh4cgNnv4yosNOXxvH1
mCfgUKIhf8kYCBdNBWVWlIPCgakO2ZWtyrcS01Md6y4eTeHqYvHN7U8OoDWl0dRQ+kCfYKwdGMbR
tukDY3u5ROFMUdefdWzvagwSkeTOanMSz87wq2WRgk8OrIXBdTYfIvcFTDIsRh1rsUvxxjSvj21u
N2qK7LHWNhOsi6cBt6+VEjtZHka3VRSxo79KcbGDqeAyvtBZBgXwMvpnf/QU3k3I9hhEFl+KRVNi
iR0xRYfGjjVv2cfqxWBnaSrBktKrooSpnkrrq0lg8HeolA998wwi/vUnCWDhhcyHlTciJ10zvGpC
hVTdJgrArepDnvX36+CFOaJG7wRj25J0eUfSMEuntHKMf//ALC7lOGNp5afBLCcT7Z2tQEWVomEW
fgLPNX3spUtJOjq4n2CWtNDyKl0sse2e0SWt6WUWWx95ZrHpLS9ZobAiWnVhUEhdm0sF9C4fqbpU
mBOnorsMvWcjOxhsiBuO4TFgQufTEKuLns5MmqrC8hp/ZPN7aIqubhcd/cT2R88YbSQFC3uBQKOU
OmOd+yRUdshDHtH9VsKMx9I8PGcZjJqSh0OJdVazn4s+aWHaLFv85IL+PnrPS3yxhqPmw9kPG85B
kpH3rIoG6rlrNlzdJTzUGx5b+qTVoweGQy8ZkEuussRorMOu2O8Zw3Zm4GCrmBEDzaN4KIRL1aR3
0AnG+jApzFFOp93YIVypo9N18jCIJFcrXWubdZQqJ1dKZdpx1lfS6i5hGnNrHgbhUhVzk1x4VCTt
IB0MsuE8un8jIe91VtTtBRCTkymk6gkyOqnZq2I5OgZvSY7tnjHQs322p9wzISZv9daLd64a0Q9S
c9jixIB7ZLDIHs+MGzjt/n4yBrDF4p29SpPGQh6eMXI59aCFy3aIY8VSK5G7HyTKSObt6Vu2AhIe
+TTa93tGhG0a7Xt6IcJmeXVxqlg5S4bdXpIxc3l2RXToxYqlZ2OOLFO80M+3u0qM0PMp+0qVUjym
LH5g4hJFxfOtVuDWOUKWbA7azLJdETFAuZXYLuTLt5PpHZz5zk7+AV9DCxUJZbgaTzBLiKLPMay0
DePCZZoTDciGjU5mcjh6O5/WseYtcvRyjgrGmtsdCR0KwvqlGOKXg4ZZvCHUZsKB258KQYNAWa+z
9PiNR4nBB2bt1fdWJad1rMXNNsrMSN4TIpX3zGvnW+WYeb1HIDuKaAk7PGIlSdAx21miBuloBXX6
ljU7iY7RwM5+2Azu0T95j0f1r4NBaRbc/WNJYCH5x8JoGMkQ23NPlgL2lj3uQbPgmRHmwEDZSPbj
Hj0IGqSmv7UO/2FyDY3DxZouqBMizRpLYIG5J5fsnr0iBx/ehnMutHIlgx+7Z0KX7eTqDGT0Tdf6
dHZbYiad6Si7OJROwLAXHfwMNNwzknxRjlVyddkZ9VgyS8oD6axYuqtS0cG3FM0ai12FxzUZFbZH
M/pXRM2Fa2sKPGwW8iQQQYM7bi6VVm5e2hHWoyWI8y3EqYOrLguedGUKmfMpVgh83wwXOwN9m0ty
sYy8L3nT3VNUUv2GERxrmYa3VeXAoMN4o+IJIHphpNy6h5+KkexSQ7Qne5Wc/hY9/KAd4aDkcqFY
rzLjfE9S1HvVPlyOh/U6KLrsg7ABXwbN3Q9Jsr2LQjg/xaDZxmZ6xXyb5pKd2WeW5O6PRaiwbhrN
i9GJ5vPdSI5NV4OBm4ze/bOFGWg1re+BJZWwHQ2J9uzDjj6awKr9LLNsC5yo7io6MXBD9c9e41GM
4HyrtqM3gHN26Z1irLWlmyEctnxlHt0Y3O/wzJcG9zZyGCvcUznJPkVJKuPGGWR5B0ZXV0kJom3Y
S6Z8yJgB2gZEowzzFZ20DYji7Zr0pxY3oqPpbVAwS3gGg9Ol5dv+5IhjNCmDp220E3GMWXRM28hh
imjIJDy+/xar0S5TD04wS0FLOKzpfa5KzkcwjbaB1SRNXVNyt4M0+jJcxoDlLgF3Z8eEgeGkMWgt
ZULxLXUXyzL+JXpElwkeuWgk24KlcbyUOwgc5XCUHQTiAUCShvb8BZs8FE2sNdmHbdcYFHaWCpuE
GrXgilaeDYuGu59cMNCUPIKi8Vu2GmNJ5EG58nB5GRU1oVHzKJopH9F9Z88kxVjVI3uWcFfXOLRJ
TDIYqJCLQ3QFHlo9LXse7I8koy2XLB0IYHbluMQ4G1zvt1PiO8a0Z5+CujnpAH+CWXrKoUGyQfOS
yQNLsHX3WHx1Rmnw7+y5otQ5kcc+MMp7NbfAMnmjoLpAkXTJwEGwykjOYpTjyUvrp3UMKMJrwb0F
YJTPaUbO0dHSUVpX7r9VmTOitK7cHx0FODHW5mkE9Emog5ILk1cJtChE07hMwb1s0fSg5ehe2pjP
2YdmjcW4l5acNbrrEHo5JFdDoRFCqcPVUCi4GUFfBCbpZWNVvbvtfmlV7SeDoJ2EzJY7wSy1x5iq
IRfsttu1dHCSiONpHWvHICVAHprJdto+mVWEqtGuYOy3UGs878a64xiJ5/es1llsrzHe98y2MzlS
pLPB4XIPx3D0CNzjBy+iM7p5+pYdlJ1QxjWaux9JECFy98P35+EyfmAu+uCWmhUObbaTNLmd74s/
MDbbCbPRZjLxaR2by4DGqWLD7bcsTQFrclHYfq7h/cAVFCRKkp3zLb5i2eXRLH9RmBxC69630DFq
9lY9wVx0jCrS9cWBYdNqJhjuxTTj3Usybk7svHSMovfrxn6MCfq2Ri06V8PRyFD0IuY/ckie1pC2
uyF291MVUyu7lhz7LUzNy2W4+8HYvNyjR1JpuztfCrZzHGBZzZDjXotleGOhu6yKeH7p2SVpCcit
iHo/9s4PSBSu0V0n4mU1kXf2wh7bHE2zPzueRMPQWn4xrZg1SguupkMi9fFCtGV5vIkOyU/9wNj8
VHZaXkHyU/d0R7J1blpDLYPhMPuq5+SJRSGYekYlLMnWMPVoeCLINF/FdGnzG46cTWc/GMKdsivK
BTw2SN+Cyzh3OtpvnfD8Y1+wCfzr/c+//+3X+V//+fdpToRfeO0xObRggLlWskmiQR4Z8xlm6dEY
3w8wH5hq12F+jVLG4qyT0MAK9p6zDmzLWNWe156W72J+51s1viRD7gRCFmS8KiUNc2EAZWkUfIJZ
Ss2QXZKLu2W+wbIUPn5g1gTZcYxUOa1zMRl29gI8wSwjXdkc7kWTwhoBeFdves9r9qukrStyLUmP
WYJ6w12HScqfKh4tMPh15hjvSZpkrmLNHvugr2XrI7r7obLQfcEhel2Kh3yCsYYdVIddh35EVcAg
pPLnLZ6XKe7Q8wdPWDYO7+rMD8w6N+OozjwtY1kL0X0pUTwts4zWwK2E5JQPzJIewcbInDt/WseK
TEZkTMj9A7NWi6Iw1d2xPBEiB+/0Jet5VGQAF70bmwGMNCGDwPXxWHTXUDBWWUighYq7H4m0NLXO
lSc0h++dYC48IYZTFLVDPWX+c/SphazlVjS1Vi8H/Yb0udbZzny3ie142rMVTuR0BL0fax/I/Oee
XFrAy5kNwE97XhI2mAulEe0ehxjKKM1cnE8Rgkwpe0KB52OScPGe4VO7IOni5WTUs5H7rZFY/+s9
X3kwMRuxWDwYtEvu5KFHPBiZ1bjHT0Yj1dGbx2JISa4yJnrP8khJ7laUl4QNFkG8qJxhLhI2sszD
PMEs6cZo85n0Oot7Eo9Ua+fsfEcUeEJ7zQIvZ2hGXeeGECJOw8VgR1flED0hxexIalVtx95GGNw8
5PFqz6l4PmYsu4KDlI7SPf4qaMslVQN7/CFnOaVe3XXYvpjzhPc0x9SSLk3yTzDGBilIVU/RX6c0
FGfodax5zibjzMrdU6uwWum9uhcg0j6CTDZx8AO7cmg+XdwyvJ5Ij6C9PkCt6Ow47HwLbd2yltE1
+3kcOSZ7FQ/3JRiSLqkhfCvdqF1JDQn6drtMDSkUvaNLaohMwNiTFK2ikrxNejDvgnfnWxlvill9
y95KaA01DCnW12zkkzV9VSytoZBP1vWeL5KWuyR1O3jGYJxeXMWC3JBUDX6W9lGoqojJ/VZ/Txpx
vjVWRbe08Q3xSJDe8ximXkZ5l93vB7Na2NPWprWxRtBmagav9uJOknRWXRyizVRPobvrlGN2jLNM
QS8E37QmeEBSNed8CjONixbTJcWE3oXNp29Z9EgxjS/uJMU0tbh7RvvhorD8VXkkxpMJ+Hfxkh/w
1YWq5e1C/cAsJZSUUHCQzjBrqSy7sUlMlL7TJcj7btMo2K/TytFu4AOz+Ec9HBVjJ5ibpqXSm1WG
i+3XRc4JX7lZ7e+uaWlE3a6YBH3HdBIHMcde6mQDOs5kH4b4th90sT31UiARjtNuljF+uBT1jq9K
H6t013ZORWgZQtXFKDJ7R9Kcc9evFcXSQVP3+LYz1g/lHNlFn2SFTMPf7uVk1KdjSPtyJmemERpb
xOSRJef3m/YJJt2sywb9aFqibNQLNYZzOOVpXZvFgkL32JRErbGE+KI6mie9qB+c8WgHfz0fmTfO
fiCJaWRvHcQSejEax77dY6Z3bN3jPxjjs/H9no+RyjGjnc46GFgztFZajXG0tQnd44NSmF5Jy9Wa
7jGO/sALLzt91/kMeSh8LRnruLKkh69zBsmgT8PFhWT0dIXTcnMJoaRvxmu+l+mK5uRD64ElCRhv
L1Lid4KxCdAZPXtdVQYDdpSWL8TzZMBiEmbPT1SD9Dql4nEEWp2yHX51Ame0WJtZoXtlh3q72Ior
ZOhiMvMVvz8R0pNn7+/9kWBe1tSvsOk03y+vQEYpLKYkK+du7r8lXVkKzl1qo2PpiK161CbkU9Xu
Xm4E6uaSPDqQJN8Mtc5tF5iGGbDaJLNpChhtsXDsMox9oH8YeQJPSCsZ2mC4UzZR6/f7iYLjEbgm
zFcj1b8Hl2EHD8Dzo6OWSo/ANb/f9x19tJlanoG38Ah8PEIkPcM70SMmaOHR3qX1Dd4Hro2qWPrR
4OADsxSW4nW8gDtOMHYdvI7D3jyBLB4RJj10/amlylWGfSR3OyheEpWxXwfeTW9J72cZdo55g3gV
+cCsMRH2GKUB9Qdm9XjiizSWr0phWxx6y9YNwfumTGU+wViPJyMhvF8dy5kB2PGaoNZda1rLSwZf
76mHJK8hA44dTMhwZWSnntZZ0ufT8YC9wDh6b2DShKbUEqIISC7OHvqQiEUSxjits9Sd0mv05OIi
Y0icZGacYG7H+42ZheAsK1Ftc4SLvpQzVXOPYkQsgrRXWzjSGSIxUGrcPBlHglVp3cUe+ztN9N+J
Sy5CD7Md6B4V6EHJd3zxUFEwlj7CR1sY2xnx9O4ZtEcfGk6mFj1GQpwhZc0kS+Y4YggyGe+0jkUF
JtcbvXA1+TzL4KtF3TnDgeHihuJ+u2MCYLlY9nRnVzasw/CYAtnmcw7QHl3INi+tkIf1GlEXPYZH
cfSEDL25qhYloDOw5ewHjbVSqR56MBJipvucvmX3g8uzkyJfvxkwKRnq0lfHOScy1LMh30WXyNp8
TkaGugTH91yKiRAzceJ77oJfNKeF7smAp3kaRpdZ/wXdqYNmr/XZnSUt1ehJCJ7mu7RAOH3L+hD5
XZK5RzvJBEffaICvZI0GG5KRss2qr8o7tiA8FxuNsuCisVKUXjjO/jq9WMlpcbzR/UmT/34M+ngC
nvMzcHoEXuIzcG1f3Y9BfwY+6hNw0pfD/XyCR6tPwz/tHhhQkTvnoJ9gbBYThaPs/AOzdumnI33k
A7PUczTcI3ixO33LWvUYTSOO1glmyYYqbDmIAKSdAKB1fi6it9NOOaGWdmbons61ZExVBM/cZRIe
OLPesrXqUzkmHe3RjISpUdPVsRyrHsPci1o3LiY7SkOzIo3t6ZSaZKOOM0y4MNlLMOS7MbTQMLHL
NJDPb+zEXNRXSJ/xPfrQpr6VoZa5jSWgc8wI1aNuzvQ2oz/ktVk9Bc+KObvrIL4kVUjOGSpa1+kj
LJb/eDsv+09RY6s+6mMtTWFguib3U6hWLJpxrvrGsHJSMvT7YunjgbIrDN5dcrDq2Zx15Q4FqTNt
93tmE4s9a323RAQwlaQG8s5dMJVE6un2+EPaT8pGT92MCkM0ImsdsBwbbnGmRzJWA8xhnyPQjj0N
99OwvClefvpkVZeF+VbrHA8NSpPcuWNoq95LUgyxlobS0cDZOQICC7lr4tpS1UYzDdQ5QUffAyOq
djvIb6n6fllycgaimSE9kQ0EEmZn+D3vMZVeMXb3wiGk23WKF2Q4wdAxsGQvCzIyTYZ07XGBXBbG
R/E4B+PQQvYvSSSzzA68zrcI/WQMq1jDG29UvYxHeO/odhc97iJRdTV722vh3el6Mbkcu1t99ju7
+2twGS3xAFxfsvezstMjcHoG/uyoNT/auzV37uzu9mjv873ka/Cp2falGDDTCyK6fZuWBzM9BxGx
bbohOufMxI2+TTdEV5xDG+/LNRqeaRAr/MDY4TCYlDW7xzt7Rv9TaQpwgllatksKafG+hYf+3KPa
8/K6jQG0Mn57vx889Et3vz16kNmUUycPPYnvwJna1LdpeVL7kDQKly2Xlexrz8s2E9P7NvlRyiOS
ofqS/lSOhl/O0fl+TRSyRy2kP/UQXU5FfUST8uS+zRJEFfgg0uvYWjOUWBbqHprhgUj/sT0GUR7R
C7mCI4OyYknesRBXGM0w2NLzEgPAWvLIhQLv49l2X2uAt8uhhWLZT0EHEC3ISyU04hGSr+HsB42X
pk++xyGesKW93+lbti8Opt7ImN4TzFIgsUrX1aAsyprlF3ph5MQYLvugCnzmgu8VLyueo/faCWaJ
UqAvhJb2tYgCvZeMCNqyBem95ONHMq5Cd3kMHS1jD8mjF/yg2ed1LzoFk4x6cGUHfhDV6tIC1ds9
ZVd2Ch4+e3HVDzK1YtUq4S6xpPQrUfMTjTsd4N8lGv+Ah32i8Qdmn2j8gdknGp9gtonGzjo/icYf
mH2i8QnmNtE4HonGzrqDjkTj0/7uEo1DPxKNT/i7eKCzx16qFdP7NnZg+pFovGzvdGPTTDQ+7Wa5
sPORaLynAi7smWjsnIo5ZyYa7zGKyuaZaHz61l2icYtHovHy7fdv8upwxCPR+PQdu5eOoVqXeznd
1oSrr3lkyHjLmIkfW/zhuo4lqDMs1xqCwlLzsN8P5lrKkKTlWO6b4hG1+wi9DY9L9YcRaHvzYI6c
9Ao7wSx5zhVjQIcn9PJgOA27/THxYCh9VZz9sGatsZO7TieM1NT4stYNm+pSsbLn2oJhXVLyu+f+
gpm2gYa7DlOYeiKPU5AK3avhlKWrnVQP1ItjOQ+N6CqdtY5cHhrb2wDZ76/Goym5c05MIJWJzad1
bq4lqSWUlMWtlF88TmIupj7T2lOalvtjySdAqTq55EVm9EzCPS2ztIuuR9PQBTVO9nQ+Wr7uyY0a
wZl0uxzBeVcIeE537xh0wJtje/YShA54IddnZ2LbO8bQ3TOx4x+avlDuoiOV8NrrK3VMlxzZmB32
YVnGYbfk0huXg7S2duiNOX8huaZJHQPVLNGjA4V6tF75wNwmH0eYL/ruX5KP0wXP2uRj9EWl5qok
JHQP6aG/nGG/P7wCdHNTmduCxMXXanUtFkSZNl2ZYB8YpAB2Y8rZRHFMJi3kqjaCjyajVfb8RRj5
l0v0ZAaPrukZuoziu8/Vro/AtW67T+0eT8BzerR60QJ8//z66KhFs/Lte2oMj8CfHVUGDj0Af3ZU
aVj0ADw/Ax+PwOdb8L4UFKGUmfK1rYNAk5tZwn6CWSaAooeiGJg2jfwE095JmvtSWcwtn5bYtv4E
02BrEEtnWzeCblfD7tl6sHxNxDj0t5Z3XuRQ5eKdS0Z8ZlLrLD4NCiMrDe9cKSLfPSaPXsj9OGJC
+3VyOtp0OnvOla8BcWO3NTxoljM7cZxg7MtqoWMyyAnGurrsf4YR9DpLS1A6Rik4e6bxmpma2xo9
uJdlhOSxM9zLRoZc1q1mw/O4TbasgWY5sx/T/luY39lnSs32WHAvY9LnWr4VUeauWWN5oUVBQEgu
G+KlN8yA+r4GFRZCHi4pUFt7GPj7OtXa+VwSRtuyasYIvZn/vWV5zOY8rLA9flp7W457WnT0tMrk
nn2kY97ZXrVkVA7MaoMtflB/a1jjqpVnGMmVZPicMtTutJtluFHBtDNyd8O2ZBhRf8q6Wuxz5KCV
8/JeXFDpO1zFgrfgkVLxOENmc4abo8szZYseNyMHJhQtOcue2afIpBXdVx21xzsr8ruH2/FJotw+
3H5g9g+3Y5tK/Hm4PcFsH26ddX4ebsc21frzcHuC+frh1ln35+H2tL+vH27HNo355+H2tOz24daD
eT/cLts73YrHw+1pN9uH2z0VPg+3zql+Hm73GP083J6+9fXDrbO/hq4MpFGxTNTOKB2L7v46+hbl
frG/021LrySdBE8wy0wS+InlinNOtySagFT9LfsSKjepux1cpHOotLOdjEldnTzy8SUKEndP8PF4
22XM/J4USAgdzaBnebxFN9XsLoPMa3mj3lMry0w5eiT3iKD2Uly5zwjAJ/3tq7nYc1bFXkDxJjwf
apdvORmi5agR3a8rvTCC1q3LhS29LJs+g21iBtYZPrcX9DKJQUvWxRzBljUZlsTSgCQC9zpA8mmA
r+htBw3BgtnyXXIsK5BetAJZRw+OI9V5r0BQL1aLkTSLioH+l1VJyLAJlCFjkE73lIOMJ5FA9iLV
zrNCOIZG7DXBnG7dXNae062NeNqiN8z+K+TePZhcLb3AnO1UmIzxSkJO7xlM8n4paV55O3tEWvJs
8j3SYYk0ipfk4V7YidPcf6dhkPtaJOP48xtbmIC32tkh/ARj3xFjOXLFT9bakseKUY5Ffev3u+I1
zOAQO/10JptHKl3Fm2uZoUlbkF4me9oR3vCDtj/uQjiEDkZNs+hdCAfz/VrQZ1rex5HbrBX/2sOt
McrzuDiS/+Z6otA3b64PwKk9ATcX0u0zZ4iPwOnRUWt8tPf6cHUtYbcPkenR6qwYHoG3R4iUKNz3
4PIqOvZFahJLjRrmJggWUS8gQafPb5bOGIilkriCTtFaOFp3nWDsOujl35GRMLaJ/WhpMQdJjm1C
Pl43a8PL/H4/CclmUpzgrIN7suntLJmusLtJfWrxFXI+unuNbeJ8Qj6axB6cdZCPlpJG4ZKiGo5m
SHs2QJsLNr6jey7xypNGs/UHMfBNZPHrEgK4VrMm2Dlm70cjkeUITg1dPgZy7NfFo+V8qz6tu+TE
oI9VqB6pMJK996L2tzzcIbl5GE6+wQ1SUbOMUd2jHKmoXeYanc65DBvqb2N9X/1GdIzUdL7V0lFQ
uJcQpJAGIq1Rll7dnSVWr3PVh7vWnLxvoRkGm1gu20qji2myWD5w6jPK0QhxL1Z4aixSLuN8Gy8o
VePiapA6m5uu1kGjv1RcNsU8oCJlsHspR++/ErWoHQrXTXBpkj3qHAGvIzeUGu/REHvuKgMPRZoD
F4Meo6MkMLinDEb/9GyoZ/2oiJQrvcxt5HWgcYPGns3HyKiBNMS0rg16GEu0YKGmk8/CDClvxHsB
rnhZzeaKs+4ZAktSWOygGK+mMqXCgYGQhzrcb6E5Rkr90TnHeDETu4JHLPRklNlS74Z6QKpXZs0J
hpAu55pHaDZYZRLXXvIIs1xa1PQ0pgWh5U1VKF3q5CosFHLRjj6CVKPL/VTHMZfVORa1V+vhCoVO
qV9CWYSrCOADWYrfXNNR24j3iSH0CHw8Apesre/Bza3yVfuM78ENrr9q4vcAfJQn4PQM7+Zu/85J
2VZUyAwyiS1/YNaOHAN95OoZxmZgIS0jBXls3H+rYRCLuML7Ur+fEr3TOhdpGTWKtbytSkGMaA6z
GduqnSSDakSmtmeXjhxVn2tJX2Azlio17+zoxTe6XsZmSuANMClKrL7NT3RsO7JEhtuX7B4cLaSm
d+gU8aFfT1SEuMrJyD3730LPISld/8BEO1mN0PaqDXc/Lbwf1/dIlil3rXsMljDcSoY1O0QfKDEf
LkFRxVdLHh5joI9Ik5y1/bcyGiyTPvviG8hzYk4entEAfQ7JOuHZpIyiEEDSY5wtYwbrfPndH72g
00TtnoxmFG8WLX+29VXGDM2o1/kuqv6sHGp88tz2UfUvyqHGNrf0FFX/ohzKWecTVf+iHOoEcxtV
T2+94ZRDtXdU/ftyKMyonlF1pxyqveyxr4a3TZ21h5EpS4MutqdU34yqO+VQ9R1Vd8qhxjuq7pRD
0Tuqvi+HQke9GVV/UA5V3lH1/f7Ybzyi6tv6mTTCLBs/gSyz3NCOaGSPafHSk1ukiyOcNBgzwXxH
3JfzJHm8Gu46mL7RqyaNLecBhWtzBQQvOyPn6JEP0XC+mbK7DpM4G3m4iIbXEKrHlJjBVigO91iI
fksrzUUA9gY1HnpaV+haes8yifuo3hEQ2J4TQveYQJZZzF0z8l3FDzJlZmR5X70D906GcJ9gLlLK
2COtHjVL4ftaqvdP6yQL05Ej4apAlBf3NsoTMmCSWpZGhc7+WjoK5/YsgM6oIRlWuntLG7i+gmIB
G65EVJtqU7QLtgMRmpkFrczscFFEsacv8TVqUKVU+3CFFR1Pia4EyO3NRIlcjsCjzqhBU3t5sMlH
cy5ne1K3FqIn4FUmKEZX/6E5kxSROltmjyU0bWeszUvjK9Z4pUbd/k1zVtue+VBL1Eu4uvtPMBCg
2N39IfbStHpe642kg/LwhHX2b/JtJWIHpVVtKy39pDB9l5qLdwwjI+lb4ZyL0B6kubcy0UC2t2ug
EDso3dgwd29DfJGn+USwX3YcDc4WjN6Exx+UJNEjcBpPwHPPT8Dn29CDGqPwCLw/2ntNjzZTtb65
rwJ6RKaZS/g1eAuP8D7V/76i5vOUtB1xJU9JU9/vYVjnsiPYFcxS4QMPPan9LPF3vKrK7NYPzPJs
hTKObNZZnpJQ7yx28r4yBzPQSSTbqfDBhFwR0+23JAW5y8vDvlqGLas5XNKDwezW5pFrdnuKilzr
IxB8VhruOqUfMxDGRW48m/S/3v9g0PzpX9/j5gNTXPEZozEzht/fM68GGDcvfThPMAvpEYJiy1LB
WH8cTifuxRPMUmyGjq3mW8lOXc9HDfAJZmEz4Agvjef92HPVNh/cvD0Talj5PjvjZ2mE1l81G/zY
d4/eptF/3rPdz8jslFNW69iHOzyCIV7k0CKhT5XBzyIaEY9yXdGr2m8x2y90ty5taq96c64kaZTm
XD99Uv8X//n/hiHpngplbmRzdHJlYW0KZW5kb2JqCjkgMCBvYmoKPDwvRmlsdGVyIC9GbGF0ZURl
Y29kZQovTGVuZ3RoIDE3ODA4Cj4+IHN0cmVhbQp4nJW96wpsu44e+n8/xXqBVHyRbxAO7E7S/fs0
G84DhKQhkMDpvD9En0bVLEse1iiz2Ju15lR52JIs6674V+B//kPk/2sj/fXf/tff/v+/4U9qTPIH
//7f//b//fW/8YevVgT2/S//IeVWAR//wj//+i9/Xf/y7//2t//4L+Gvf/s/vEyOtf/VY/0rhlKx
1P+QtfEnJfXw+ZNbsJwqyR+OGr4/DfjQ9S/8oX/6x9/+4z+Hv2L56x//42/xc5JR+cdt/PWP//W3
/xRCKP/PX//4n9+/5W+8Yh1jhinRwMT8opLVOmTXie1VU4wKphuYFF91ZFLfCgLzX/+x2X3MjOCq
tkf/ZJbN/dVyKArm7w/LlviKIcWbrUww9RVba+63K71iZsaYYf7zw7dbeVGP5K7bGeWU9LnTw7oj
vEbPwz3TqK9QNEsQaZgU6JVz0d+O/rdTpFdlJlas1sy6iV6lNYXz/F8MTI6vEeIdi0ww9TWe1iE+
Q4jZXYfGKxvy/lcDUsqr9FDdT9XEWyZ19PzPFma8Suwa7RY9rb1y1+uQuYmp06uFeLfnPWlG5v0V
hYq/W1SM8apZk8+yZA7tVQalk2+zKHu10YYnOXJitq16f0/XN+fELGrEwn8261J41aavpqVdpv7i
PyWPB3KhVwrNXabGV8ma26zwy7W8asjFh2EytOKyAD8zrzFSu1lnjy5mm1DJFfIsxF6MjnpDhj8w
FFgYp5C8W0X8oLRRXJJTGExyg/aHMxA/MIy+6pGKUn6lPLKHP+IHpZSq2fi/WBh+UYpex+KLiPdD
2T0mPzIpBpe7qLQXRYrulvmRaVmDPDyb1CDnNUdaoUQ9vWrVDGmeAsKTQlocW+an0V+pFpdxSqgs
X5pGejYw/IQE8olXWIPI1RDvn31UFCZ4j7F4qCiZqZC0DLLnLPykNBpHakaBCmG0omw4oFQ8t3p/
T89tafzcUtecNcy6vfG3+3DPNAia3R1r/YGpIb1aM5f1YX+VNcYwgvv81thZ83Q1kZoqtKC7T39h
cl7uqr1kNUPepDuN5gvD95n/trtbLiwjS9GkMs9kreHFz5761t/ttyrfTiJ1rt4eUNoSk1OrIsv+
WIVgDS+7OO2sfTbzfjyQM2rwkB/A6Qxcy4VH8N5PwFM8Wj2NeAKetWx8BNc8+AjejzZDZ5uhlk/A
rXb/BF7OVj9jghrDEXg9wnsdR3sXc2r8ga7WwmYZm1uZYRZzL7JgGSKrvzDWdGM9uUXRZ8dOiLG8
ZyWpxhkm2nVYL061qT3bd4FvMOv6sc8wq3kM9UGfy76rsYxX6qKGDCOQXPO4FL2/YnSFiLet5e7i
Am/bEMX9uz9r3+FtC1Hj1NpurKxGqpp+RtNL/N5domCLrsTPXe6aVR6tarxtwXza2AyJVZfWene3
R2xVU83uMdkUyiNW9wwlv6i2u3X2Z6jtNWKqLhka1KTs3RBYvqFTcbfXmVI1pBNuy2yuUPapm5kD
alDUtcpWTmnZ3mKQsiJKqXaPmjmDaYfH15mJ2WMZ7nZgs45K7jpstLKeprH+dwvDilOn4WGdRRsb
l8GVb7mzPpg0YayZzcRLqdQT3qKQ2V4OanuLeRLZhBklesekOGBWKFHxaGFltud7864Uq66vmA1f
L2bkYBVXS/XFpGZqlqSp8Iia2l+jmbtgqAIjcWR95Z+cjMRkequP25eKBoukkT1qF6bcGNV9hEpk
Yy+FfrO9Caa8evUfqgIHk32ArQGY4HxLap0njVyMxuIyn9iMPd+9L47ixPZ06lrSWVuZ72Unah5n
FRgD1VDXiJvS44sfmXEDs98fHEWhJvfc4k80IvPh3GIztqLfa0Omyhe19qFxY40rJuW43CVb9qss
ZmMzotjCsJ6Ue3BlKIzGOporQ2thY6/2OxZ19FW2jUk/JxbHFWEEs+7ybZa7nUI+EWxRo+XRYNJP
+yN4DUfgo52A53G0GUpHRyWtWD+C9yPwko8wU8rZ6lqgPFpA4QiR9QwzVb93v9hXOW5tDNbhWXb0
GWa1r8KrtJIUjNGZWAF9hQL5M8EYFS5mfpIknjHB2ChnhoMl6G9Z24Q1g9YRwvrCLPYVy5ZeU3fX
KYXl2NB7frzf41VcRPCjMHpQMIuByGoAy/fmHoANsEuA7omXArQzUohY45GsGTa9nyUwFuur9Ka+
tVg4IHBOas/9wYGbMqtwoSuCRxu4Y4UcgXX3DIQzVM041kqDdUUIKSxncMQp6z/dXBAboGz5xQaq
y7QIPqZeowvDfJFLJ++iwQTjv1VMa5WXDJrnenLMDPta/AgTGaytwu9+kpD+FyZYmFxZ0dds+/ht
Nox7DO5dzUy63o3s+KeHdWvlt7klj3S5QU+JdHO/J8MpsckY9VU0anIegWVbyN4VYrnGuNH7WaJV
rLaXFrqHCwr9VcVfsmd1iunVo3tbYZMl8esvW3Zsssjbq/oIRoQTYgGxF/eYBH+EZqXFeCpwSGS9
TrUwHSqt+xQwpvhJ0d9aInUtsYQpw0U73+DQYzlhbeqdDUstlWxqALEUT4VcWhW+0XWYZ8iaI8wW
QeI9+zMUCRulIwlYkFWC3CuHViWny6sygTzYuYVf6ODeu1LYPqgGxpq5rPuXSt4VLxWio6ebzU0w
/UVpJBd3LOVLoHGEu06vUbSqMp5CmhATITdvvzXEt3m654cKt6qYp3vc8F+/qBdX3NTEd75qvl9N
QpjLxRVtNSMm1111qxI/Q7UcPR+V5USP7utRC2+v16PXA+HALhbGhD57JH6wQ+n15kiOdqi49Sfr
7wAc1t/v4Dm0I3CtOz2C64fi2Vg82gz1I0SWdISZko82U/rZ6uMIM7UcrV5rPwLvR+CiC+ed4hH5
pYoStJpgrP3DygnriEPBWEMQPsUhkvMLs6S7wjGe9LesAYdEtjbI3Q+xBCljuOuU9HZoTTBG+Y2V
jWDqeYZZbDZkqSVyP8WSZ1DQ27HLwK+InOkJxiZBxF7ZzOxqy8HG+Vhvvd69/Y5Hgdra1HasVcJq
a5bI/v5TSVKUUvaojizX0ai630rpbd1st5wQpY2xeVhOmY+VevUImgjhweCiB2G91srwLkUqoGhW
VF+zXD9R4z3DJ8lkGi5FEQ7kZzS6+2mIcAX3kiIeaCi6UGvwPc45u1selVFYqkeKHAjBK3c7SHRl
Rcq9o8xcfKzh3lEktsYRySNpzg2kiO63WGZcpvoXZMlrDfBB6aP/s4XhT2V9rG7cHxkJT8G/XJmV
3Br15VptXXELFBc9DW6nro++2MOoRNBnX/aDvEaJfE1oXmzmjvyB5HEqwfdYtPBZjDdxX0X3GSBx
X/l7hkHch79n1lFeVMyelwRYejXLPosBHBA9bB5vIAGW9HaW2GtByqTezpPHjcqd/PCf+z+ZOtY1
h9ybN862CXGobpGYRz7Jh2O7RGwtm4Y6veyZWUzOvi+ayfwQDGGffcUGC/nYRIr9vj8kFY+HbyP8
X/S3n2yZCHdU0FtZXn42tZPZrv00v/xlBIVyy8lwHkcSxWi/Dt/QK9Vyv5/0J/N4Qd/0rDOpijih
f06wxhueGqn9LWktuS5sUsrDuiyVA4lbaV9xUtpH5dlXrlR46uId20zvbPi4Huy39vvDuxsTufsb
KIeo+tZZ3WWMF7NAOsF5ZvXrioxP+LSSnZXut+thX8nCV7NLBHuPP1SPhDC0WLAvHyI0rXosmkta
yLkm2QQWpBrkyXRtfILU4s1vpncwvoshnFPyW3mVmTnYYgWbpNJhwrp9U5CI0zWyrN+VraqQtfB4
yrCghCq9Sh7BiTWmlpImuC1jwHM2hncXCOlvklW1x5bk4cRRbtZxYsbMI9kcYXHdJqTIRfcITM3Y
+923J5jOSmgh9wwDFWR3qNh7A+C5TQY1hs9LhN6a9ad/8NzW3N2rCs9tDUGhxj4Vhakbi1nHep+h
rLRSPdSUkt8FYxOMTZhh0dtKdMVzYRv6SmRZboOT/jxYBqgLtNSJfPXa/TGZuoNK9riN0fkKmtns
naoxPj6aKN9YHs3F71pfVko9qH/IuqmUqrs9FqqpGHFzU4aRUnBlPMowWFdxZXxtsDM91q+N7YTS
XBFfWePpl7n6s4yP4hH8vSyinIFrjffZz5uOwLVi9AjejjaTwxn42VHNU/ycFHSEmRLOwOM4Am/5
BLzmo6PWcURVMc2GYffJNMss8UQObVPwIhKvo0hSp3SivavK8zYlEJ7YXoVrttnZMaPMN+v9WJtO
hJOIYJslquy1lkidfXFronb0Yvp9CQYrG6w9Rncdfo2qFNpM69g9Vz6X2Eh7FLL+kaSBQt5mEsbO
Rw+GXAsMco6zJvtSlcFPwtDfWpOCpKJeHWvxa4b2GpqgS00GqyTUindyfiE+6T3bU8HSo653vHg1
c0Ser2bUZGHqKydqHsMnSq+Senb3zBYi9aHXsd5R9CS4ctD2e654nDN51ELqUJE6zj2jJuaMETXD
LxRl3WU5l02RYjujB42fZc9sNcbQFL0WCzCiSJ2ih8PMykvtpXi0YFohtUrhcLEAYXyUQh4fIudo
pOTyWKbCt4L0OvZcJb2Lgfb4ycg1DuZe3Phi2bAa7tnRiCAV9+7kxjTtWrIsTQU607QFLRFsWcwQ
j8JwzzX4W7FGj+7ws17VFntaUMyMZ4OfbmHai3Xf6MKwYfpO1dvumRKcn03fC2uNMf+M0r0rCNs1
NXLRwzvhN7BHD81oRjBSII/syFe6fDv7mhGULnfN8YsXmqVGJfdSIFvpKsqfYKxZzEpzzNHHzkDO
ZG/eOiXEq4XQ9Ggv/QnokyCyRTLM4Ggef5uDiP4EoxqZYU3lhGNVteUlmSfHj5dtKy9LZpPxip/u
v8WMUUvNnuwpcFEZZWQ5eynoURDdPcONFfS5lj1XyF2jZC11K1pc2FwzOJhJ6zzLEn0wxZNPTuYc
lqYKxUtbCJSxNE3OJUeJFZGrhcweNRW+rzbcY6O0JfsqM8zpHrr7slWJ7gz3ZasS3TFUsFYtv0is
7rq6HOzwt+W7JVdlkTJCUtzVhzIc4q3lS58QUBxPBcOok/kDHuKiJGf0XoozzKKVMu9KLidtQ49I
m0/y/NI29BjxJIqyTduQIVIj2JDK7reQrluLXufJhmalmXCLp58s6Qt8yhT0p60GijY7KetPL1oz
se6NqzPBVAvT30269liHRpyG/taiORJsAcQ6vjBrjgNsgaz385Q4X1h6pq7WXXMeKmt3abj4gu+2
GLZ4KutmrejSvJf9TpouP1rS6mKCWTTm8S5t3dMKXbvs/laNebD6kPoNS7oduAZpNl7WRRKCVAbv
rwOy682nb5PrJeN0QYXj80E2dNCosbXWLb5iSdndXivveob9bUVxc5WcjQnGGgoIicnL9juLIqgS
gma/u2T70Hq9YQE3qhLIXRUqivhd9syHNIIrb/13xud3+wo+7EWopNWn4coogm83a8QsqQfMAIxw
vb1FT+VneeiX4S6t/uo08YVZUuR7ejct3N9n1E1nqgqlf39CF9/v0NBxb39OdNbKo5PHoOispSXo
U6QV5dBX/6bly05Kakcns+pJBOTMB3Hf7q8cm9MvvnHJu06lJjS0u5Msjm8UXBOHxxHoq9Vacl8/
KKAsvOmGQ92a6aGZaG2zFRHUcKVRRbOKVLrHaIjd9BYVU69l1P2dmDCR6iZ202q/k1iTsvmpLPNg
WIeWhGLnXIRwtr4ci2Jb4GIzatxTMAndWcvw15W+WvFOUDgpyeFVa3IFB/pstdzcB5z1wBfLDY2b
p9wefZzH0IpW0x7BezgBz/rl/inj/gB8HK0uyWgH4HS0Gen89zu40Sue8/mPyFTq0VFLHyfgtR4x
QW1HHNm0VvbcTA6YKVuTCy35LpummCs0wYx3OPsLsya+s+QXL+QXZgnJQF/IolOUnSiLjW2aIK/g
F8YWBvTwLgaeYJ5S70ZBmos6w12ae+1Zf/tBlMHeS0nvd81XR8cPg2Nri6CtahMRbungRInrqw+z
X2uzFraVsjx5X5gl1y2+mKGKixs23ykEjXNrs7YMlbZ6vIRoB6uw6lt30Y6csstvSE6/Or59YZ7S
oZCITq1Ej0czP/9tDE2rpVI6sE5rcPGUe4dmNyMmjwcQxWhSI7CnA4y5pq9ZeUx2Y0tDnLN7dCIx
nJI5kt1e/zRr+Z1FKfx5obfoRGZbluLvPdsgebsFzVpP54bnP18uAPubyVyKrFhqllgrlZE4Xot3
heDWj5JnNcE8ZefB7Kk134ibCYbNsGBwbmMBbBvXRt2jL6FOowR9hqf8Mr4KcRjRseStoXoou9eF
n3Io/MPbX0n9XbKy0MEpMRZjw12WULjamsfW5RO0+Z2rUStMpG/L4vvuaBlAzeOs0qWmO7rYY8rx
zWveMWH7kPQD39+gGjrr//oRKlafjpUf6JhvvrXXXhJCyuYxXpzqDS2c6IbTnUQ2NA0c/pkKQsPV
PxNsGMMmi/1UO0tIQytrh8G0dXm4sgzt1cgx+yW0YczZlYeVnzYK+j4/Jrt19dlHMyX0I/B8Bq6f
99+MoN/B69nqZ5uR0roD8EYn4EXfv5+qlA/AzzBzGeC/g+tX/NlMCSfgl5myzX4XM4XEJtymo0YW
5EUaCtI2rTXW+nlP9xVDLb4uR9J+Gb7qhfSWl8QxhN+L+OH266BKJyJqOcFYa2d0lDSqYy3zR9AO
Mg6NQqtVx/Du3TOtc9MG6mog8oV5bPGkt2YIvQlOfmKZPwYnv1FoixzknCeRy9/osS1QQ3CydQWz
VnOVF9szpGAsQZkvrkZBtI1Uw3wttZH7LZhAlz7kpAKOd+UG2XC2I9TpPSRn/+2E5kIGxOa+oWhE
5lpMMNaq5Ee/BFGttzk+aL5cpHMHbSPgiVX0PjT5lv0wiXPr5K5T0UAHSQ17lMKCDdLIfE++hAI9
yZ6nbcIC2niR9GBw1kGFHqXikmKgH7mCsDY33/wq3av2p0J8UlI9F7513tuIxJfsfTonaaureP1J
Y0Nj5SENw/eIQckXE0EfydqZSJaR1pILwR0bN8BL3rz7i4S7y8TY0haDfq5GQXt+zKyQj2A+9WQG
s4mbUtX3bgkaor2E5s91QM8fM257BgQWQ6M70k0w/Z0YvicVkuLeYdk/MEvkjqTsZnhop4Lkcc2i
j5E79FiU/vnOOdF9OVYXXT1/ntffSTXau6H5/kjovty73t5iViJ9+nr+t7cMnZXt/paQH1KjLwfe
PgUNFVxBvzqP3ZcL/+Zydu7T3ySH3ohwOyYHbfhk/M7+uSitfILAe1yAVtmI8KWEa7xy7q4Il5E8
VxjVyTkDTruL0xpBm0A333I0aqa5eV1tay/c4OTLfeSgValVXFDhaOeNX9LkvrYVvuCgsWe3V9PH
BblfhmXt1avfwZ4UddXoUQrNlZm7tRCy3xrSrJ9caiKpPZtb/tCEO2r5/TymJh+BZzoCr0erUzha
XQqsDsBHOAEvdLT3qgXFs80ZT8BbONqM2Jxl22QzUn/3uppgrJ6OBoUZmall255OOkXITKey7YwX
MW5AGqqUbYc9DHa5JGSxbe4muwEdIKv+lrWlh4R73O0MDPArw9sOzI1RhkLPoitD75G6nrLtsoca
IpIWxntSIGOyVoMea28kjLE157Lr5E+m0Z5cGAhzZV5OMMtAmMJkL2o/S60N+t7KY+V8q+R37c+e
FojOpaz3vNj26Aol7cucbzXU2iSX5ZPoVGN4LC/ZlyPqa7HUGaHWJvv4wSjdoPe8Zl8yfmrXLG/7
DAVU7Y/sfQtRvR6Te5UlqtcNHy4tqBCO0axhP5X5NZKRbM52CE1eArnrIJFPmoA46KmwuLp3SzML
liQTbycYm1yJYZe1Kaobr8+9G6ec5ZiXb9KCddEUCVG2GWZNIGeeinDdfWGeusFcmQIix7YJVvDT
NZly94VZfHkjY6SzWmbpsg4pH9X2lqvMrDpSV59aGu4goYC6+pbVilKC+El6nUUcytCl4u5HSutE
tPyc2igJBRQ1qZaGeEgWGMkjJ0RW64hDTOe8EVld+v86Z+jh3d9pgrFPDJNYJlVPIIuvBb33uv6U
rbRDt7IemrcdzLoaAwr0fjtodpeC4TjriUisHEvy2QRj1/ljGu5JwVzLL55BzzI0i/cszT2cdQie
sRw9cmU06ZeA++83FF3cWzO3eklOYOld3JuF/IVYh3vRUUzJ+mdyPzXgSAx36zj6eENBmuZ263BB
RxCJQu5ZEDkOVz+XhXWccBXaNSUXfdK9J3ZPeMGPE6WoZo9igqobNdcuvp76qeZY1nHSIMK7mmPP
fQS/HBmyGEcEUhwWYWYdEYGFV83Nuw2sS0DWDw8XhW9wlYGe+/0UBMZzdnFa0OFMWlrsBSXSHHqK
rqCUPIfRiidR0HonJS241xpE1tdHc2kBhw9V6h4rIw+cJDDvnAt54OL7//2qoaAwUXYlZw2fEMxe
AqOg8FLxf2ZT5DmEfrvdyXGDd1lvb8lZRq52GNVDn+Rq6+0tPXwqJno0l3Mqy81WtDx+HJOMiVda
01n9NqzFxHB3Aqfz4awu/tD/ppyAZ605PqcEHIFLPOgA/Oyoklv8O3hNR6vXdoTIeoaZy4GyTV6D
A0U6XH1B1i4tCA7Im7zNpILiL+3EyzatBmH9a2bKBGNDxS28KwKddRp6VlS1nTXEi2HocbjH6p9x
QM46yGCV0YvTfhY/DAqoRSWwmRSTUcFvbtf7WStXMQqSkoefhFS+oXG4+HMSmgUGtZ9FsWet9Moh
8GAGEtZcmqI7dxXHq7MOau+lxG+CsfiBMRKLi0IxLbv+lDUQEGGUUWF7hmdTE03TfHI1zIzJPrnQ
7qxqNlybhKLMK+gLaA2EEJik5HGhzO+t5lh383sl/39/ScWmKdFdBo4+mRy0P3mGE69qDC6mUZYW
Gu6pCDkM8kTtt0PSIT56REe2dZLxYHselDnANUaP6LkSywwtLRdrrqFRMSl5YP2OWVJHMrnf6n8c
R18Yk6mfkWLYyD07MfOweaHJdVM++/YTO6nbTC4pUf7C2JnqxGTPgVyGl4HB0r9xT3eYOi2YJ+em
73aO5j2x9hA/S2Xo/SxNY0r/6Nz71OyKJhmkv2XtFsxrp0LetUAgu0sS8F5+I1XccOrS7KW862b2
uykBDTpb9tZB0vdVV7u/FUj6JulFvqcWkr5L0qJ5tZAKvOiumLtmTentPBgSgqhvG5pt2/MvzLbt
edkGSjHk5CoTLTYmNcHkd1nmF2ZRgDD4PES1zhL4yf2diD/BLK3Q67u+ydkz3M4yjHGCsQNVYAGa
LS+lXrByRK9zcuX4AvUw3KP3guCQT4mR39bSHsujfTh2m9SBHMqrO/EEs6TPtWto+f5UCHm1mpqH
ZIS8QtM8uOgJKb8nak/fWtrm0dWXec8X0v9DpqxNy9jtsLmZiBQGF+0QSVky3GrPX+iZXqUzk3Os
ipnpZs8380uudBbnW1Kw1Hw0w7NPmnnu1KhrurRzdmTgUnTxA99wilnj+UaPunyAW/Tka4i3glkU
hcTk6sW9xtCjakjF/RYr6iOU7t0ttHGPPUWPxdCCJJIRK8sgFMxT6cO7ORllppX8c4F9ZPLlnjWk
50iI3T17A36Kd7ngCk5XXGjLqVlG9PoCgZkd/jLy0AwXcqPQvG/BhXx1/J9gbCldgi91uEcnRBZ6
9rYMdawWfay1f0l9V87tqUWE2Zcuw0MbK6W4WEaR3tWi3vkUM0/IWqQux0IpUDTfso56dFiTjm9f
GNvtjuBXy4m8S0Esn6q0rJhglvTE8tEgvzAWP4g8Bv+pgOe7Rv1UrE38+KnI2b3ISFnsg9y3vyS+
XHrLi6MZPefHcEkKxzdbuM1j5oKmnrnfkYL1OlaJ/vr871//5a/5P//93y6tL7Gmsmh9lcJn38Yo
gtZ3DQP/whTrRIp44oDqCWZR6RAEydGFYRxdQY8JZnGfxbeBOsHc5iiRhrHaLGRvaGrPayfksX7L
4gcNb8WB5nyrpVeRmX3OnjGESlruOHjurBuWqOhly81FqZPcq/1+ZHJdN/RaHF8JLu/h7TkhNtei
gvnmGAYBAxfKPx/+u7U6KiP5yer4wmytjgnkcdgSva2Q729WdkT5coxqXWthEL3HMU4wSwkWptxV
vc7Cjv3dZ3aCWfy56d1ndoKx+SDikIMqMME8lkmm99Dp5TcTDL/Xo1T3nGxJXyJujy/pJiE+qAnv
S71VfHeBm9Z5GHWBXDjWbNW6SwcFthhHCOSxEnyw18jLaR2rHVO98p32pEI77Vq7yxapsLSXlsAT
zFODwSpuGnK31+hVydyYJV2NNeqYNamWZhIsabNmi7EMXOqX6beneMasLOlwu6DCySxm1BSNmjUX
BA9TzR4noZ8gaV67GXt45SzueQI+0R5dtpYGFNfLtaU3NPkrhfJ3eqOCh1Ii9wgN3oDunqBje+Sy
DZoJhtHvsOUkeSDNyNxUq88FSTNSknb1hqKqhvQZrKeTDbyrKm5Pb8owzAzrLzDoOWKu5uINzZhd
2o9wUXClRvHEApX2iua6WMcnmqRLgHIRfpMa3d8N2SeYxfEJoZ5cTPTx7haz3w7aXHcZJbxfB7kh
ceibuHYLbMg/GB4jl4QRybl6XIr8kVHbHWUmNbq8x6PtKYE+1ymG4V1qjHdi1Y1uzuUUEKEGOvvr
ooukTNSaYB7KCAuyUaUUd8GNE0RHz3n91i4WkLzZBg82LwQ8IBbQni41fLLcljN9YfiWtzKOblXF
rc8aV0vWR84vtobdV4gfxBdLmehJD2muMap7rSoEfR03KHUanzE79nHHRl8Y9E6pwRWS6A/YWrtT
cycYzP6kdrI/SVr+gj+mN+gdPM94Olo9aTHyUwnSAbhWEJ9TYo7ASZsTjzku5Wj10tIReD/CjKRu
HIDXo83UM0QCGg397sU7m2TvSXhfmMdMKwTnpMne9BtbAYTYgjx1E4w1cVDiD8wun56sxvbugjEd
YXFilGvk7bTM4sPAgGc4YyeYpU1he4+8nWCeDF8MxJbW59Nvlp4O/HAU/5QdkQ/S27MRsdFejM9x
sj3YfjFGfSSbUMLEvPJM9/tDoKhGyh4xUQzQJea9nMHJwetsg/scAMMuyTu3nMGRe5jCYEhp7Vd+
JNj2VEy82M49vlhH6h6jJ9b7LsPTgWHDLkXNxXeWXWylezjOaGNnLtXTm48sfyolekIAoZySwx0P
OK0Y2BocKBBx1qWPnjqte9OKoUuj19/5GrOPouTD7K88cl34XNW7UzL7KAyXdoi/xBI17WxkDvRN
ud6cYbLckIMR3DtOsV9zP51l4BzPBqU2eMAq3NUAc08atGdovdyhfXqC4bIz+1nmEaHxaLmTgE65
ML1acamHGMmQRK7lmG6zw6QQs+TlIK04ZMXnSw4Qpt8lV3QUFOlIPdDvLIsG70Pmve9pgl4N10yR
/XVBQsvVpWpPN5hsVz/v6VtPrdchikUb3dMavRoo6atgRSbS+/mhjSeEE3NMGtPuGQK9Dq8Egj3f
o9fh1XLEwfH4tBz5XdQh3X95Im3XvT+DW/Z8U1F3V0t1YZCsI6b0HscVUXXJWNnzAHq6Z5ne9fu9
rIVtolL1OW1mPoKgrbnPZoVftQaXl2CjlWpUnmVsL6s8Mg5gT3OM7WXlT6/zZHRp9D7P4S0n4Cmc
geun79mkiyfg0vviAFy/YT91lfgdnMoR3qkd7b3EcAROR3sv7QjvNRxRtdIR3qtWAX+yANPWNoLb
WXykE4w1PiKciaJ1fGEWiy98XrgvjI25svZyBfgmGJsemP8oufv9oGANIXtvHdZMruDTBLMUfKMh
lhggf2DW3hpIClbbues6P6gndxm4mSUp3yEFazDxepy+MEs/x4CRSHfH8nqxsh1D7rroy0i96HWf
7CzUYcgwtQU3rs13NXyavmNts4JGuJU8dkMmYJRS1j0LoKCCxDM07W+xA9EubmSPLrADU653uJlg
ytuh6K0zmE9KdvfD+mcpI3r8lqU5WHbZFj0rRnHZDZmAMdXisQUyAa+axP0tkk5+0qblC/PU0hPm
4xUq/P7GZiswmyABU0uUxXwc7zYgCxs4cUAM0AvFYy+Yhrmaa2bNcUwMq4ZNbdB09IVUS0IY5qwn
yt46hJHJFJO3H5RBDCJ3z0jNu0akOt9CMnjVbPrk9yYSe1LTYYnGxXfqhvNtNvxKd28IqhniMLfR
pg52RqnMz9zfIkJ3TKlE3rM25nvF2t1rhFZ9rDjpdRaTkdm0x3aDHqc1M9CVksc6UrsQcvKuMCbM
tkvDsGzhuNP7uyvOXsKw+o7I4PDoUNpn9svv11PMuGyuvcX5SO9J5Ht2wyiudLk4ttccUbSaDA/Y
KFXEUIrhvjQVik2sLvtXiZU3l/0rFJvosiSCZlEGo+9Jg5GubCkk91Os11wTqffSQsq7Lds+WZEo
TE36mMv+UJgaUrthW6efnuK051BZPALP/QQ8a4n+bCi1E3BzqZ4HWaUj8BKOwPsReG1HiJQe7r+D
iylDu5chwjEXhZK0k4YxYgqSSAXa3VQEr0IRR9IeRhoxyGP2B8Y6QiIaMcho0mmdpb3fH52fdtIO
LQCzVPE7Z0dflJbUnlc7JbxYv1TrrHYKsq+TwvNjGKyj6ksUQDJiYrq+0Nepe/hCg6urfHd/Ttgy
QRpTTd96aA2GYijWh6uHY+Q8UtP0XOwS5DwmQ6sFBs6v2txzEhy0gW5wPNlAqKpCleTyLS/ez/jT
tFsKupi+IXX3jiSMDbpM+f0ZWPlNLSteWqua0Ga7alo9xatQ/ya94SceWOJgrPW0dsKiaKsXhxYN
a/pi4lfTsPFNtdI1AeLg22zH9MuW2JIlg3RteFRBjyoiwzVLhTdjjzSItarYsilXvHx7GXJHLrrB
sLX62LJhqajXeewri0Ilc4FsqQnSVVsu3jFhxby90Ft0EZwTWV/6NcURNQlJn+EhORqlQlcN2f5x
kDIg0jy89BZHj/+RPDLA0rmqHfd3DFVAMijOWQal3U1fqdXQSegJeELMcmWfJ293UustdUz77WEI
WJca071ULbG/B8ztr6/UgyeNiic3RMn00cn//CYs9hN9Mi+2zFYKOp/W7F1x2Eubl3Wyl+Lyktp8
l9LGQiq7DIZDVLNlG81DA9Wq78djR/eBYWfUPHJWmcdnHuinKcARE8i0dF4mIqPmSdoe7i9V5Qc6
SyOzPSvxhUL/8XiDP8c/39GP3OM+MctkPMT+8agyBdNlAMwJY+3UpRzmhF0t8A5OgJa6klPvUA5l
KRTuLqKj+imefzSzYj0C1w/to5mlH8fnqWBHezfK63MP9XIEfrZ6Ebvpd/B0hPcyjsAvT8Pv4HRE
ptrPVj/bu0DXrXUWILOjhnlMj+yvyz9QdzcYBXNF8mcnmCUOJi1Ji4JZ2nZIAl1XMDYuh5Yc0lpg
OcJkYNK7lt9BhRiYFN39YISvDAlbzuUWzLUrkrzfn/RMbf1mf14c/hPY+fObtZNGeOtp32VtDRtT
85308vORknTN7erT0RZ7ob/7Fef5AxOejlQD+kg3tRdrcyG5aohd9oWxti6yq6o50xIXKy8Ktd2g
b7+/jhhiIo+U6IZBUg20XA9HroOFW/HOlJGAE0mf+2mcVIqvKwa15ZCc+EjZCABrE7IS2UI/4RA0
tAiJXCpl8Qwll0q5iK+8uTBSMqHvwdLbOH+cFlt5hMZgV2uf5VNOzj8ijF0dczGE0ARMatn38pIk
A+t2f/sHNaJC0OzX2mkoaSxGpt3YiJep+fM9IJkJbO6ONXOhC9bkcgAh9eBSarYMSug5GWq8YVAn
UzK/hr2nNoIGg7CYp8VaPQH9S8QC3HJfAelqKd4ZYAG+g5tbXKAj2AjdlX0FJO931HQMQGlHrDl0
af4VMIowe1yC8rYujUj2KC1FSuCrdxsK/ECpKLSvBmDgYxK56EKQtMThkk9ml91qKo5mSGjSNFxy
DpRCJldmVnHzacnwaMMIeTVuxjL8Ch3Yu6KDbU2I4Vdv9/4WNxUN36K+9msuZEAu9p1qMMHwOa9c
s68qYNdhral3vZ/Fsm3tle6E0Kwmv3s2TatY2xc9L8a4u/iOOquR+VjR1o7AxzgBT5qrnu3HcgQu
oa6fwXOIR+DxaDOZjvCe+xHeSWt/z9bp0d6pHVG1pKO9l360ej3Du3Sq/R1c7Mdt7TsiknRlfDkN
V/5o9dtSVNiUb2f2tpA9JjjRxH2z/xbm/knxo/MtDFm9DL19dxI0BboCBNtqaEQtpZWCgx7YlCRe
qW9XDNssBRlBV4WirXmchE58z1+evmUDth2TJof61hIgHfGj434Lm20wVgYEpOTtBw2zr4ar036s
ARgxM8OlOmzPJPPGHBgM6imhe5TAnOTeYnS3nNu7+8R0dLsOQSdUX1qq9VgjjJHcLxV0wSTNy0vL
F3TBTNFFYK38jOfm7hh9HpMm+polyhY+1ezxe+poAzMUJaxaholkSbpGO99i5rlm7uzPhQhoHy5j
IACaomaMp1AHBFX/JlpYwRDKezxWt5lH+7dbalUQop7WXYQS8vmC/rbNCmfWuxD3hVk6V0ktGh7c
aZ2HBLooUTgQv2+TsjBNna2wMcOsrfbZXBIrcVpnSd1mgSje7QnGnnOkdwzaWWdUtOzPN3SYpAsh
qKb2/Di5HSPXqXjbgyRJhpxrlgSr9p30EZYMCPRT1qR69ByxxXw1Cp3WtfcL5WdUNYyVPxjkIJ1a
JpgHkwYZ4FWqpJffTPc/v4fETjA3GRFX1zEHN6PxY9aqt06WJm2aVksGOKZeSoeQ/Z6zeC6T2vPS
Ux95i5LFNK2zuLcym3ypuHtmE7kmc9XsfghjnO/Q4+TNoYdhzy4q0OMnmO1ZkdraW6WZYJ4SUdDK
fBB55CSZ8jzaDasr35VlnSUPAR0Vxrjb3xcG4e04XBZE5vblS9/jAv6sGNpw94xRbKIH/U4rtEet
4uubfmN7LVXQISaPnkh6SKO4rEQ9vmj4R0AIXGbU76WZZICLKre/IRjWLj7i/TJo61RSJu/kSADv
Vb+vi+8noqGVfyy0dbpqSJ39iM86R48LkPhwJVD//oYUNPGO1X2/Cpp4d7rjQKe2Lr1HPExvu/HZ
FKY4v50ax4s/izm7mMdp8U21F0nx+f4WIYOhDcUVi8smooREb2dx2SRMHG2ucMDIL77Y2eNAJCxc
7VYWGe2U8kJm5+KuixZ6Ul7jnIEvbCrxTrg68VrWlfUzaD2qyP/uOd89KY4fSmH70bFUjsCTFkrP
VbvxCLyOE3BpF3MA3usJOJWjvRc6wozMUv0dvNIZeDs6qmSX/w4uJtI2NSeizkdc332bXBRR5yM1
O32bKcSMzMzf1DqLycFiPlbYvxOM9cEg2Unyyab9LKYVdGYRifvs8oy2CXJh9+ciVlBK099aJiyj
DopcFNaAxGeNwqXetn90hJ/T+DCEmR8z9e3FgkTzjzzcEww42Uv2sIUc9avd84ItR7jEV5fW19Nv
jCGK/PMrR935NhvTV476BLP4cdj66j1550xQ7ySFdeFSx5WOBNGQPI5EfgIVzBhYWMCxvgLS8fRe
Fg/NYO6LLocmGeNS3RsMD02/XsWDfHTCjNXunVv6MkkPo+kMT1OJkc4YbvlogmFrmzTfrEnraMqi
97eE9wlNWdrduac3B7XcrXv4Q7ZBlvTPCWaZVVZfLdbs7hllZSOdXKEsJdjNXxYzuA2XPHWxwo2X
Xr4TdRcjL683ahmszDechiuLYeSNFIcPg9nepOX+0rsXbas7eRyJSWZFqjycPRMblEPf6MXQos+M
CWc/hXXh6HMppjYHs85jAgebBSRDYJ0zdHkD4w1H7tcdyDbIzbsNyGwI1X3LkNp+hVumY9tIPbo+
5VHcdWDRFX1hlsQGhHZSd1EBiy5p5rI2KIuBms1Db1sUs/0WY3LFAHo8URquGECOQg/x7r46dmC/
ynqmZa2J3JnXetC8ZreHqqN6y2uTiceo6OalsvYROjGnu0dyMgMZ5yHqZZbOUBibNqJHuwr6ZsPq
tu5XsswMqz/V4uKhJy34FxMPXRZavEPFft36jl1NqLF9hDGmQwZVO1Tgd70XTc2l+hrO98uLaWGc
HAT12eeOTf0InMYReD1aPWt0POewhyPwdraZQSfgVI8wQ/0I3Jgfz5blESJrOcJM7Ufgohlsk3vE
spRGYF+Yx8KLKL2zy/yb1dJkgSpVU90mOu3XzRDcVe13MdHgQkbOxgSydNzNH+/5PluclYu393yb
sXSVPmd9zMWqpHfDCOdbDX1sUjlCsbR/lRuzz66X9q9yZ53s9cYGf7z79iSD6D041YGRRJGUPLwn
OBe6YbelVW/+xFL3aeTp065/gnlMe2fztCPjfvqNDeIxX4QcsnsGjAoYBu/LWG5WcKv51s2wSIuL
u1T4IM3dnG+1yvpO1/xuzW4ECCn0E/5CKvw1wn3PXxj6eI0knmCWGdx8zbPLFrBQx9DSYm31FDDH
c9x8av9A5PjxJOxT6HP9eA5+lkLIj38rVnvUsGi4pkM4Z6r0ng6xv1YYCzMur8X+DGhRmiq5OGZb
5B3e37JS7p3Z1uzn8RGGQ6y5tEOQcRhUPJlB0EtjUMuupiYS0OnuSPt1M6vooaqbabNCiFARr2+m
zQqhElCaq2CsTw8xx9yHYq2nrBAkzFPu+kWxyfmY91KouSgfAS1/onczpZlw1C+crcfH2MTQy/BY
q/ANTyWTx1olIpOlnHAWP26fyNJWsEmFNGkUr9Oxw7tB7h5daDB89ZDfP+RIkL+mEi233ok39FW6
WKMWwz6SvuFL8BXDPmTohEMGZHhF8yhaUx0k7+QqR1VKXpL76FQI9ZTvHh03QT7l0r39ocEwPxjR
3V+SIKl+OJeoJOwy/Vos5jErBGNoXfLJlS+l1k3zkhUfFb1Rcj2RShXF96H5R4IrWmqv92xcW3+1
aPRa2+gLiUDDSM3H6GZQJ36Kbmrt+6cxM7+DJy1pHsHH0d7z2d4zHW0mm1flMQ++HIGfYUZqwH4H
L+lodWkB8Dt4jUeYqdoefR5iE4/AxzgBF6JuZ1F++371fWp3GK+hQRYb8epCkRWMtTWR8xrkudmv
k6WquMwwT501YFInKQJw1kXbqKpAFou/SEaThlkaI4+PLrvP3UcLd9LfWlCB0Zg1K8osReMYjZlL
cveM1NkY7kjjuOzCi7UFTQYbUcWgeymy33OFdAar+ttPkTtk048rEe+7rjWxKSHvfNzgzytW+uS3
bus3YNK2JKldTj57fAXyGAkZr9SLhrnpefzW6fbZ9b3ybnpxMTxQbKc5cs14T+8GuMu3nGqq/Cre
5pD+etWNTB9+MjsznNZNo9eanazsXkMcl3WV+fr2BmyJgME3b+v/90NXyQ53iSJtwmR++sG50e1Y
hlfuCZnRL8iy3pMtGNp7gt73N4stiAHFRR1pMQX5lpbLRPoDs5iCyKRr+tiPpiAxD125WfsRomyT
hNCyhxqqyHyJxbtPSH0lIxCWVl6ROTZmd5lW0Fqie9eJOkGgag590lSQmJ5S8fYnea6GmqulWj4J
UFvOL0heD+3u9jqqUebbkpP7bZgtlyPn91GgubGJEt1HFQ2UQ20an0ttd+QH0+gXi3nb3+O6f39s
0BAsxZE89kPctMiI1unb1kRnnmjU7h4Op9a7vYPg+ymfUjbUXOkuk0rNEdaxN+HjR9x/C9lPMmVh
f8wq9Y3x6N3lz6LXtSadNfsKAvlG7XtgLZicdCWybVkLpd+FjASypfINrQUM6y+jSgurnCF61wPt
vd4msMWfo5YqafRczV1OwJNWL34LvP4+cDQcrZ61jvLc0jkcgbejvRtSPpulR0clfRmfJ+scYabk
s9W1hv7cmuxo9cuK/R28HJGpjqO9A3p8x1QtFiqSSaBgje1oLQzioQ4bYVpngRmYCdAUjDUlE2Iy
Q31qCfJGBKX1MkvqcHkPgZxgbPQTaWYl66MvTbDju3vKF+Yx55d1YYam+TdLzi+0JQQJp0/bnF9+
GK82Yc4xe3/Pf1kw6lqoVwXz9JsbCzXWpFBzZ6EuFL/pXX01GZlgloBuZ/W9VncdNn9ktvaeUoni
u/5ognnswkHvbsLO9gr6XrqbQ6+AaGCsYcvP6TW1ZeHr/e76Jx40/cZGd8cnHrTn8xw+8aD99UWk
No3RPUxcQ14N4zwOea2vKq3Cpt9YuzWj1NOcYSnRRJZtz+45abyijMOYzmmi/AjNttLdS5WRQyad
jpZzTjDjPaR3EXeOLcs2fM03d8ot9ey9KfGzZgHzsiF6mMGMHqqGCtacRNo3JSV5l3lAsGN6Hu63
IHmlsciemoiyVkmy2kt5zHhtiVwRRAWDXrqi1JJwjErdMlwRRPBeiJn8OzXR3rrKvKI9Z1OHDRdc
+YJ2ZuGWKyYQBJN9LkA3sxCO+BFNybIMxt5THNZtL92lOMYBXRNGF4o7tVv0Hjq354DC9zkMo5os
1m1jmVRvjj2pcQQRNG6Yf789NCCTQbrO9vD20h1m9lpZQJg2kCehqhRqDe9EUuMpXqffHxPYqFEC
LXvBVzHgMI07AT+prQH9RsjdHzHbV5+nK5yMI9w9mo7dyiIha8G8Zvdiip95pBZ7kyWmWIR76mJY
UBla8XtsSFbUkj/ZpL+DG157BG90Ap41yp6txnYEjkDs7+B0tncpwDoAz/0I/OyoRQusR0NN2yjP
wcwz8LPNCPS2U4C0nJYJ38PWRk8mXnxP+PZgkDYmutO2jwLmsfLT1BTMEs2MV17RF6RbM0tKE6La
ztKiK/cX7rZ7dFZGrqjjBHPTqvrKX3G2jD7Jki7lwSDJtOtvWbuvRbTFVedaqnBZQSnN7NlW4fI7
91bEvp0AlsY/8e0Ud3A4CKNb/D2PzsZW16yx2J3xFYs5u52vymrLpe/um+Iw97RA1SMXgqW1KpCl
bxaMjmSWWVKCEaBKejtLSjAy4rM+lTXkKp+8ydu2xXISv60m1pJZzMi57MFt2xwEWXuO0bujSdy2
+lsLsUZ7ZwDvtwzbc0iX6j1BM2s818CmPUXRV+wKou1JkSM08uIRHcOWqkQOnE+hJ13UDLYcCz3p
xAW9JwVqW6O+Wst2CkYmBx+D5Y+Xao/BirLV4n+LOaOVlj3Rg2TiFFJ1j4V6V+l85FCiiw3YvUuB
Dtw9NvIuBboYpTRc0UMBEwuSK5oJzkkpXt3vB6Hcqw+O861E76Grk9i1xlpGB6DsPjmUP2Ok97eL
qL3rLpxvyXQEc5NtXBb+K5mms38GYCNfWQHOOhXZ04buFocyom8Ml6aYqjB89HS2ZS/de7/l8RkO
72wZLaFz8Tge5bStB/ciI3Is7YsnPeOPCzi86K/P//71X/6a//Pf/+1SsxI/6auaxY/3tVYyDYXQ
8LB1scL+wNiXSTp1SGzlC2PTtzHKI+akYZYuHKjv6upb2brb+YUTLeu7yk1/jSYjfKYd292w5hOl
/HFax568su0mrZ8mGKtl8eNlsbNoI8xibEar/WT7LXTYMussKgK6yJtzLe5hGRzXFZYXJ23sz99i
+/zxW5jTa7+16CO04tDQQvqcDs09ay/U/qJImjNuSpRib8XjVCgbV1PaaT9Lh4z4ru9Zzo4bJmC4
W/LP51bFNfM4YGRDvhZgjfTB+mZN4QseouUh6QXb4wyzGCkY8Y7UyBnG8mtFv9is1lluMxrLkVln
0fiZzwLLzRlmyVfku4HncoZ5yu0L6cUXkdRvlqbB/O3S1bpLJ5TYro51zhnQ6nOE0bwzYJIpm5gT
xBJ34ltQ0PtpXuVmho248Od1LNcVpNSxLD7BVq14ChS27jr7DrhTVq5wQj2oL8nV3S8rTAX5Xg63
ZcyphYRwMJxl4vuIJ+fOeEtCdZfFxJJU882yE8xAg4vkXYbMeg8fo7vrQO9hblcwNlqFnCbmNhdd
FdNbNLstujVm2g26Y5NJ300vNqiKJyykwC4WjXarf7PCwoJQsddTfjaFciUTO/uD/iu1ys6Vgf7b
kr8/ktpbvb91cmm5Jtc4uJD4D/xqjrBg++GKvHt7Zj6Io2peeax8YL4IfXgiBnrsyFpo3+UyykPr
4QtKhhabtoiNxa84chzqoUOnfUKWLDoMHu71bjdO5uJ4ZX0ZlwS+LOONsvtptnN7GeNEniBsE5sh
nG0KUzEOeLifRrumlNwHGENJayf3AUbzlkTJ5ccyMAI8uA8w5su0HO4e4D8wmC8jHeHWdTwnMXOJ
f1/QqaXk2/vidaLgB1lzzVNIWgI3Rp9Zcgcx1dyIJLtd8WUZMWHL1VpFe3NXtKGnJ7+4GuVLp5Z+
pcDOe35Ib41ajXrupRKOwPsReNa64XO0pZ+AkxY/z7VgZ+Dl6Kg1HuG95jNwGkfgWjt8DOgRbnX6
w4ZWzSdkQ8cZZKkF48vVq1zi7zI3o0mkPH6GsRZ5Q11CHQpmsSiIHyezZWu9wFkTRY9ORqhMNwUN
TJpa5ylFDk1FYhV9989vorHQEQuo+pjrlMx6NcuaYZYxJNCpzDFvxpBIafQMY9dB4Bsz0hxUJEJk
K0d3z5+clZXEjnQpl/9y/o31xl+d5KvHXvDqy1TWeX9PRWXoEVM0eZdG/KFerSidb6MsijQnLao/
24eM4XpDBqcwChUuuXjkzaJu6u2tcwJAOs1KyxFKReug4X4L2SbR3GBrmkAF7a14tzM3aFXF4zbx
xKdbdGmrgwx6HmdjYpqd4ZJldgBm2FK5ER5uX4+AwdkOF2NOQAmicG7PhD4eUnbgwdC77GA9w35/
0GyMsFuHY1bpaONQDm08pKONhz50bWmGSx5nY7K6XrQAWmcCsOHCrO5xn3SQRM6Uw+nSQrLGOyE1
mRz5xbI3nrBWwSQXFJPPv7F6f85XMdcMYxV/OBJGzzfsN9kljd+3oc9gm/cXNiBKLB4rFVQls5rp
4R22iuRUOzQv0sSh+TiFtzToB+TpLS0DXuqhcGHfUhRMSZ8RZ39ITpOglPOY1hivLpeOBESvD1aa
yMMpjBUZ0OSIt4q04N6Hu2d6V2cd8CDaStYwXDEE6ySMkL07UlHOGvW3nx5TZJ5ZBWEdQRCvEScH
ryCKvifw36yV38E1cz2nkvUjcC0qn/tiHG2GytFRqR8hsqSj1Us/Aq9aCD6PIBhH4OMI/DJuaPcw
wnKpUSzJPzBrLCRfM6ZmGBtTQZpCFxp/YZbimXZNXZ9hlsqYeE1dn2EWy4WlB5tbCuaxJStKjXv1
cIHqmcTWnrc/xEtyT+qci6mQ0ltl/i5jc3lkrpImzVo8Q6hHukOFk2zarnDk9JsnzxBChvzQtBt0
TpIHaeqjeyyQGrKk9beXcCla2jWN4sXyY933Hbb6rvPQtAv5Sp3fXA+faLw/as8n+Mwgd9bnfiz+
SKjKFqvv+xsbMeBHki0/vV9rbmQojiHefHsyf9iSxpDNeZ2lLwSmco96A+MUo/KVr+Ya2igMuguk
Skf4RFfL0cYRPjE3LSUtoha7hvdLSfPMEk0JcHhrcWgrZTDiLnZ3GSQpZoOapb/E+OjYW/TBHJIE
n5XNJ3OoXp1sZpilnwSur5G8ds9VZt2nG1JNtg08sprVH00vBNBK8dHO9k9tSbOJRTsal1rRscD0
j99ri1NU07z9XlsxhWYRIxo2eGwWAduwuFexJLS/HHdX0W0W0S49ePsqoZxGxgI4OEafwzp8cVKQ
w9xuIJxCajbYSb91a6sINtireYttI0m+9CX3eHOBHeuIUMBEHiUrv+lBqy5rO4lxTaE9kFFoHfE2
crZvCUax9W5UhcUQytccBkdVQEPDK5Znedrzhb9Ys9cYtx0eSkMzY/eZZaIxhs06FsMtXc2MHdFb
ZWJGI4/3EO0hGs3jYdhPrdajZyrqIz6X4uQjcC3Yns2tdgKe49FmcjraTBZT8XfwfgY+4gk46Qf/
uS7oiKqGh39pcngCPtIJeD3bu5H9z7bf0eqX7Vd/sP3qTtBJrlzPTa2z9Pajj2JVdxKJ5ekr5qLW
WfI/0RY9D7WMrUHip0Qme87bWYauRfSL7modWxiE0lwSLq47oZVYpyS2B2eYJTKDDvpUqlrHRpfi
uFJovXUwYZX0txazMrO+HVv0yIVhbSxs9X6sDUYoHvK3XFjux6Zhljy8juL04VEU1TENjTy9LVdJ
2vH305C0U5L7LXgXQtdcuPQXRH5hV1y4mLEYqp5F69mTayCzUgTJdx0bFWP2GUPjcCnKYPUktJw8
PKOEhiVi9c6O1oQ9xe6RHS0dWjffWmpoWDfu+uqsNTSIpnl3PROx9lHdi4PpcH0EjZ2l6cO4OoU7
AkGmwxkOW3bcwtWRxdsPc08e2ccyazp1GMGyBPf+RB32ex5oC1uyBwODVoYzOdyM9MCQUvH2jBlx
rDo0j1MxI67X2jzuQQqhTJx0uAflMeHKednvJ7fXFfb9ksIGw1g+DTKX1BrYaOqtsbMW2aCTXHH5
nVg+lSuov5VPsJ1l/qCHQeawVFp212mYq0jdPXrnpyvru76cC1lRNXVPrtDIVwsabz9Dauo8oqOC
ptRGHsMjnDj0o20iX5uM//4G/zHj/wPuZfz3HZ2njP++O+yU8d93EmnK+O87vE4Z/313c6eM/24k
wC8Z/9/fLEN/+E0een9r8k3+ELXveAw9ovqQmPV+nYSYtfD8F8a6cjFCsMSbLTs2GlwZNXvkhHrS
h8RBLPomtSJcs+VnGFuSXPuLlcnosQVm9ZQUirsfpFslii66QPIx+gku4NVOVNz9SQeoUPX+nryw
Kb1K868MvNgM0jwcQxUIV1Bly5Iopy2XVr9lE9TT9tT0OktdAC00X9QpDKBv5W4/TkcM1D8EzUtW
EUFCa43DxRdaz9RSXFohRJw0Sp86CiOJPOjbukhy9ENtNG5YYHq/WaslzSbLq8Fv/NvRviU53viS
h8s6RO+e8Q4q8IC3oK/M4v3GHFgr8RbPNmE2pysu8DqzPqrws5YONEg8tZ+lJVWvrxi0VFxfVb6y
+lNrCSz6ccTsL8OSKfTukasg5tH14/jY/Tc2ZoPsSiqZHxv1t9cZswNZ6+7N579nY8L/FLG+U6qL
0YI6ViNcFyVEKiOL5rhHPxAKo1v3uLSgiKiat/ypRVaXQXfD42xMlH0XFW3ZBEUJpeubv7q3mWub
5lobuq2xXI2uHQGH3J+eyL35mOETKd495l8Y5IB1fWPvXN61Jn8dpAEaqfc45weVylf+zVdXNBkI
6I78zt/7fvumO/I7X2/LkxWDHM178OiqVhf12VUdj8AHnYBn/a4/O5PrCTiFo82UeHTUUs/A+xF4
pX4E3o/AxSEbt6WiGLYiY2cmmLVdkUyhSDPMOr+0Xt3/5nVsC4EmHV7UOouZwqZMkjTLaIspJlMm
XZ1r5nWWpJ56zRmdYZaknnINdHfwgySehpZGzrkS2jBIGHuPH8w0DVKCsj87knhYp9O0WGoUBmb3
NA8/qFHgPxzuuTIrebE1j+7I7CltRAVjawlYBAY0MpthbmwekqwiB4fQiaXIa09T2EWVovrWWreQ
kdbcPbrD3Zpzc+9FwsDKYnh16YRbWfHq0aMF3K0yD2PmjWXKC70quaSA+XR5mp1PwTqOPnpQAyHT
9bx1cn3r23tWhb/1ir9MMNY8KVHalXrbYcki7UrnZawlhJ7JqScXg5iAazh+dclGjA6I7rdaeXXS
FF1IgXyiYDjeHl3maubk7mfkV46VPA4jNODO2cUh5tOwHlo8bibmMMuFVgmBudapuZKFUkUXquHd
UtRl5KhZde1YhATy3j2pQcw+l/K3lxpXHUb2cVjRvCFkdz9M9xC1VF2TitDytFVPssAUq2O4vIrC
i8t03tMUdlYY+gqutlh/5zXuaYHEI+nD6PAzEo0yWu0750KiUW1FrfNVjv9f/uf/AgaiLmYKZW5k
c3RyZWFtCmVuZG9iagoxMSAwIG9iago8PC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCi9MZW5ndGggOTk5
NAo+PiBzdHJlYW0KeJyVXeuqbbtt/n+eYr9ARnyTbEMpnFx/txzoA5QmUEih6ftD9XnMueeQPKwx
zSYhWUvLw5ZlWZ91iz+C/PtdlP+qPf34z3/88r+/4Ccc0/jBP//rl//48T/44VFp0L7+x+9y5Ab6
+AP//v2vP87/8c+///L7v4Yff/8/GaakVH60yD9iIMZQfxtj4yeUWnj/5Jas5HRSdn4THuXH+z/y
uev/lY/+4bdffv+X8EP+4Le//RLfq+osA2X52T9++ZcQ0h//9cdv//35bQzyx5TjlYaipelH661c
aQobmtiO0KgrmmZoUj1Si9n9VuajJlZzpmpoSj5CDWqcYtdV6tFKbmqcbmiIp/lMc2Y6SjXzOdf+
59/GVoaxE+Pfew8w9LwHtb7+Pv56w98U2pWmlBv+9poUDVn+piNxUd+a94APWUlXNPG9nvvZx1wP
pqznN/EyHDGXrGj+YGmwBqqK5i+W3+WgEq8kFB6mV/PBkav76RYPqk2NW9LDuF2WFPvdXC40dMRe
3K1LIYsIxbTD8hTzUZuZr9nuFOvRidjblpTleGdN8kdL0o5aW/akJpV0NAp8s4QPDSSARTF60+F0
cKl30neh6Udnw1JzYlJtkOLibU1qwvaYovst2eKa9HT+bEn46DnxjdAudy8HOWTVLNOwPccinw5K
KvKfDI0caBGn4s0vp3YkzS3LiZzzkVOunjBlOeOlayHN5mzmUg65n9xhisymJnJXLmqXRT+7K+cs
XO/uqkROQjTazk5HVENsRgaMLGWoBjLcyQ8b3KPIKDX32yI4UVh/8+3luCXUg+TUeOsWmT6ombNo
VE5JQc7rnpYvOR6iSpsnAfIrUUtVf9uo2lLoqHoJxS6ByhG4563pycWQGydPvchFfTRmV7JKEyHu
wWdx63KRMrusEM3fWig327BcA8n2itHhzo9ELxSj+M2RJ9ldbuVOG68/Lbsrlgfd/M2FRrRqbFqr
Gski2V2yW2cOuJymo8fo3hbE8Uipkcdi4ZTYcCl7W0U1ybea+6kWjpRvJXLNrg6lQMn9tBxwzlqS
XodhOS7jgHe9JHs6OJIsKd0dsvW4Yta1qoXRcJNxC8R+Z6GthxWNLyhF3y7ZjEtyELp7uTAHOe+F
PG6yGNqxhHhznj40FVc6k6d+WNS5vXstyGA538xaQB+tzKy4Gx5uiFjDFnnjHfIU4w55DnmLvPUd
8qJNgkfy1LbIeWupFLa2ifYmQ3uc4T3OcNqaO5ctznDfmsyArH2Je4JcJ3VAub46rYC1mYbx9aF5
gpq42nhw2f6NekbobRhfn/nZb2cSnc+KZn4iyIIJ+938FKxtmhX2looEm603l10Mm42KGudPlkZw
T+jVHacWLF2NM70C1C5GRtJLn+CwGCJxoPUPzYNtGnsXw4TccZNcb6VUPe4DzE4Ra2rZ400SIJTj
gBV2vgrqilWktpPo4dtFrJCSqvttgTTErEXSYk2BNK2N15k1jVxwwh/y9g7YN2uSCdaKCBQxJN1h
BB6z4B53qxpD+tllaZetoZg89uSQBPEZkWxP95Ess1S9BmPL5xSPllr01pBTFzjiryGLURs5uqc8
FzzyuSc4iyJ4ocQ1K0QTtNP0+HzKwnWBMaFF2pHSLFvOp2m03PIsW95C9VmBU48XbUeb5Z6P2rPH
LZnJIbq9e58qAcoiFo+lRQ4+UXWXVWI7air6LkoW7OIZNyd3zmL8cjAstIiuiJVatCS3+mCdFAH5
KbK7BhGd1PQ982RtFhIoxsU9IaXK3VTIPZ0i1SL9veyIW2nguToN2UhxGY9ijW5Y7oLfRLd34Ppv
Yp2VlMEflERJ9Vg9RUFZUOLp5VjTyPb3qEXtESZSekPL5faT3A0lpHwz7gXp4jFQ30MTjBWkG7Kx
RZ741+Te5OxqNhKtIL+mG9448LjJmkL3+Ml4BOV0ZwtcoK7wPOQHGlHOpbgqicU+qKwvqpfmXdvD
Ob7fmZcqQVgngDO4FykXPPYaFWCOKstxbpumsJgccnSNKWx5I4C4ulINOMxVK2J7J3HDvUU3C1gb
g/q8PcJbLV7P8DZtkWsBf0bDvEVetyZjJPWRnLY4U9rW3E80/D153JoMacX3SF73yPdkhtPW6Ofr
7tfkNYQdcmjpEpfoK2TRPDiTF5onZ2QUsBqS+psJQeLVP+F5+UNjX+ui3ISlgFfOOFnMaoZeuczP
6IwoJnOvQX3r6baM1I/U482yLyA4H8OUc7hXIyxUupmd87wmur7rFU3YWrRgGHbPZVz7rNBJgItZ
wpMrV+7BIW3rT6coS8KvnWWnKJsSsv70H58UY3pZtOuNhPs3lX6zogsCxps/aRpzUyaxhEKMaufs
s2tiMYS7+Zb1NMPNwzW57JKb0crwNJ8K90xT47SHF44k1pJYBIpd0cSeiPzCs+YJSQ4IhYDhc6Gx
cC0UYUVvN0tYX0TwGBdSEjDBN0HNebxSriUJqDmnkL2tgjuYQ/F2KhdYFpx3NECGZ6jrwzC7fiOm
t8ca6ATm6EkEELIctOJuC+zlathnHyZ6EQno5eYgXuBvPlIwB7pZGsFDNd+dvPX1L3CYuubNBPkS
3Ee0w76SYaoHf0lFpC8k9nQJkG4PRiSseximMFd9SVlEzwKZErsnCOiXem434qfQr0C66I7T8utB
5kJjXzPk0J9BcheaR9MryTopeVtFAn9i63ffdjwWSZRx9FhMWViTEnnbCV9vGw8MDk2peLF0P0UE
kHJ3GV/ALTxyyb18CTs+nuDWOomqSGA2B9jsFMluxuAKDvBuqoHc6XTRA4X1LfTwbMKw6kLRAmnx
WhA8Wah5LOWI9wJ9Az5i2YSQmlu94ODfeogZ5epM+H9zM4rBYm+Se6BXzfNmaUj0sxF0Ow7jILK2
cO18GEZQcK0DhphUci0aFj0ferpTHmsbMqghHyGvNrue/cVth9xc34/kaW/0urXUHOMWOYUtct6a
e9Gq/JFcg41H8r7FGYpb5By2OMNpSwg4b0kk963JDMibV0oXYeZncOiFxoYQx3dw6IXG+mwF4vY+
FEBeKZsoBlDgpL81hZnD0BtG3Ho+ZRh63R1HYE+sQ0I/NDa8W2APFTg4PzSzg5iO4f53PoVIpxL0
dB5xbz9kGeR+WuzZlAxLH95/k2xVRGbC5W8mv6kAVgrUvW+nVA46jS+Hph9MNXm8SWLA9joMveU2
AMXmgpCFC82Dzhcb9IXd18usNxL5CDQFgXFUUhNsWPbYFlJLChaCwcYkJVgWr+bxtFDUEsLD4+5w
q47o2/XhyAVu3+JKbC4iAT1ml4Zk50JLngQAEfZm5mORmxiQkWLxJAB+VLGL9TjfRPpmvQ23kb7B
KJynSF+EeVqJtZBLTH05ZC6PSw6vKONJK2h4N3I+LjST8zMdtaU7LaDgXcWvd9bJ7YiRkneESqWX
B2q9d4BpLcadw0vwU2cjftZ5KAY5lezeFRRJoFIoNyLqoLQuYnOnOJzXdD4SBzXdKSJWrpsR5nmZ
rQ3QlcMSSc92wp2yKSJ87DGcEEt9QqD1dJBiwTe8cx71RbVUdi8FYTWcZXQjio4pFI9mTr85TYyT
QuyeFMZJebjyuWS8ezXvNDFyYVKK7jg0/K7eHiAmto2Mi+8lj2s/WmNXoXIrcEB0T4645yPldqe8
HRCjhnwGMWmLnMoW+d5kkGu5Q9625l7C1twLbc299K3JkBbMR3Kt8Z/9dlujs1bQj+R1a/QatsgH
iKEvQMyHZg1iaKWJLiDmQ7MGMbTSIBcQs57PB8Ssx/mAGFqpoguIoZVa+YCYnySTa3GAmJbcYWo7
Qsrd3YomU+5RL906CpG/OQJhp2U5KqmKiVj0uOYRD+AnMBWPpQA/oiKyS4NHu961GFjwk0UMRvTE
hafWg1egqT2upxG8WNSX7F2e5DqKRgYegt8QihqyGdZ+ug2HVLnZ8PW4HfbgsI3tuN4b1FFJy6fN
s85yps6A7w9NeBCILMx9uWaXZwwYJqWUvM1GQiNl/e2JpoaXb3F5NrKYyj1HV03lFo7QzaemUFBY
gEEv6/kOE8tCn6dfp5jOgIdotd2RLY2cb4rNO7uI6QwxJ4/tBcFZPVePpUhGfFlQS54C1rwsps84
NqGSEIyVXL4X2eKcg8v3AkdliHt8b4BQWfPLOhM7HmT86XXYtpluTvgFDpVDVNcdS703TpFsdsUW
MZocjTq0wEVus9ba3reRbhz0kQl2XORnUNSaYcpGrK/4wQuN9RtVxIdU9a34aAvJqR8VDy68sflz
geCXdq87RsC8ueknox4vCkTxhsfOk3B4u9S+1rSIdwyk1zTjn3RQcJUdy4lq0RhK1m2EaKD+MI6c
qKQV2eQ1kp0762s43BODonUmdxcQIcSuzcFydYVkbIPnxBolv0+4Rk/ykVxrha9SBTfI89Zkct+a
jLGjn70taYu8hC3yPUZy2mIka/3+jGu2Rh9sX+ZZxyCY5bxg1gVU5GKnOt7x1jVgUn5rhjWNGLRy
W0RFY437PELd1JwnkIBwlJGo4tGIikF87eVTE/RBSsxQvt+Xw0H4mdxU6tM2zLLFs1SGw9HWRZsM
dbJMVJarWO7soLllI+ZCPEb5qCvNk4U9QslS9ZYAePIKJVuuIeXyDiVbF1ApiEbJepwnZEFiSnWz
bgvDCPELMXmShHozoTclSXMtmQBTOHlikuqoe6Hm86ulaXLXj/yRD81TxKFYi+94rk91qMmDI/Nr
Zn9tyCHSpEiL5JMY5/xO4f38jXVCiXo/y7BcpjdVfKFXWo+zBCrHKPhy+dKTD0ossthZSdYUKTj8
OeaUTUAH93qKO6cD/hwB+cXjTAkz9yagA+dC1FITbahbRM0NViwO7M8PPp9KpXi6r8jOtWxOkAU1
o56P1kB3IX0igdHTAgjpSzWSp8kQ0ncW1LiMYzROqYiLr/lmzl5CxJFOn9RSC5QuJyjG6PILbw6N
9Ql6CJukgNOhZSuY+06Ax9FPz8S6QEkSE7Y3ve5maUgQQGCf5mdc9HKvCHWeQtH3pnWKyb0Z7Ll6
4oWY82VURLr8jY0nRD2X0KInbwjyCyO7yFkDovlrjp4sEVzsp298/S3Zc1Ga3dMxHFBfxnzrQXcx
Hv+6tl+mjDDRvqcnb/1pMYNib+rIPAYhwkVL7G4DkNfrfWjJGnieckjuNiD5LHHR87MBjw0pKal5
x3N4o7q5gC086yheE+5sOcdO0xr8MeksbJGXtkXe6g75KDi3Qc5pi1xv/nPFlq25l7Y1GQp75Nqg
f3Yv7ZGXraXWsMXIAcPWhUQ+MGxduOMDw5a59ygV2gs3lybVV6mvskyqjWLccx4qdD3nUUCjX0lm
FCY4Ig2+rmuWiNoqPSV36WJlFMrsLkusjJYMex5urlh/xoOv19B+xoN/nSONuLo8KjI443bcUlmx
eC4fiuqr3eUfEshaGpbm1+tGTZWzVON6fgliMqrRXWjst0VMemA9PxvMBheVFpPHtDnBDK+ks3UN
E5TVSVWz76ncTBXDnY3kT/VTUD2I3BMEuMehFu90oLxoGsnM61OWBOJT1iyeQAwMzaBFYPIMIZV+
lAZarytHentEl9U0UHO0nmlS63opAkBCaorvj1C34EWkKHGzT/UoslLO++AzP2PYZUD689lkXYgF
ZXR60KrCFmKRPaZe9N5Ynrb8Kgnx/bFCetgrhGiZtp+7aOhRPmEt2yWglmXKN2twggrxQE2uOkZQ
oWhtdr+NUKmQb070+tMFecX6sphwWEGWiha/yak3jNN89+0LlkTkFClRmhxicswp1OaJMdLDmr2Z
7Hx6FC1O7hEusp18RnstjzDJdvbTWbmuxDECC3r2RJs+2GI9TiqCxXry9kK0gFzuRmtPWFEwe/dV
ExWEkpnb6REryvwieWxHPljrZosnhxw0uZYUiwIr3NykV2D9g40FMsW7e9Dx65Xpvp28TniXLf4h
h1/vrA2z5jDLoa5nnui6Tkkaflt3x1l2PDez4xZmofp+qJ6wIyXsFZ3zfakVkus/Vb2bFu2ysCvr
b091O5H+FYur++HsC7mxpxxQFCWe6XJrdjWxAaq+4yanodzvWV+5TwA9amvluXBK2CFPsW2R65Px
7HmsO+Q5by017y21xK3RS97iDO1xhvTRe0SZtLVU7ltzB8qkL4qPXGi+Lj5Cy9RMBDXGCIjkfFtU
0BlCQTbt8oI6BS52OH5pmb6Jyp2iB9qV5qlSWySUDYnuEoAwgx52WgIjVd4s0/o4YVcUHJYLjY0B
RS2+pldpQ0DF9EgjKOVCY4Eznq3H29JlWTYEL4hFT0l/y6IZAZAxwTpfswf9JuqICJ92Zq0ygBTG
s//nbyaQmQWVjDraE9u91zck8GZ3XLl1RkTjZViLrXHpjIpNG0tCzS27LVPvifQqKnChsX7R1o7U
NGumrZPtFRvh7rBewGF4JXxMrHCiJQFMOXqSDp9iHGXBpjW4mWO5Rz2urcMxPFN8N98LWEQtvhQ9
3oxWE5mzJ9aj1UQwymTKLhMLNjV3H3JNRyKtAGdAifcpw9MJUDLSX8qO4jrrjSTyeApvZHpQmvBG
nm031kdcrPJXVf7L3thxEvzcKXm8KMggjNQ81YWSnG28fa3lACGendSy7PMTQKX8lndYiv4TZ+2Q
9ZYXJB3G5kkXSpCk1u+uM+dxHM9G/U7ZKcwp4MbnDJoP6M2cgE2AYOc75aYgZyrhbjOd9BFAfc09
q5QoCdxtpXscJgSPBP9KHkU5k767JriLUmRdC+1cpwRWjyeyxEjuyOwdM6BSDvrWfnr3QtioYAm1
yilEFYGFOSiOTk5ZPDIU96JHJGmv0T2ZjMztamwcC2sSXuPpTou7kaS9mFvIRrqWdBAxe1oB0aU1
Ff3tqZpIEFNOa9GnktOjAicbQ2lyeiLCVwvkY5VOdKLSkjVtiyDJs9PTpErW1qo2hx5hohaM53Ig
tEWuDaRnmLg19xy2JpP1LfwVqvyevNAeed1aKun75Llg5tZkOG0JAdMW37lu8Z37Fvk4QV9UD7nQ
LBPvaJkC/Em8u9DcYNSOiV9pbPFLIBbCYzctc2xjQdeheCWZkuFKfcVE0TIFWD4jF+BAMV+nAEfo
sROur1laIwqDd/fbtaMXo2L7hJkbT6yY4HpHA8TkrhNRrGe/zjVLUUmzx+6uC0A2NFbrsi6uFHGV
Et3M2QGyqBZteGrHxXt5yMUTr1TwNl/ajXg5z3SoINr0fC045/xKEnL4h1oMo9zchWaKdGXZKy23
M7otrwqs6z1PSEgaiWDrPQdyLS12b85wfRJVvlm7g26H/PvjorVibXyzV16yw2FWZONlS36lfa5P
PZycNTB5CmZURYlaUd1XRaHmnYazKkrO3gkGtj2r/TrjVNT7L+yufTyY65M3rV2kgkOM7rp6fdVX
+P50ot3E6V1brwEVV85GIJNEepFPB+Wkxg02yjePSsjupSJw6ZW2uT5VhcYbg3eo4Bwlboo1cap5
KYo0BFcEC1oEna99y21An8QU9LLmHojhrLpxmbKNMe7w5+rpPEImYBTWJ8SGlCNmNlCL3rcRD5tz
2dLzhKq2FF0djvjY04+9Pg3IOuzDi+DQyOlMvfrfqrIN1O7uiwt8FD1q7qa5ywO9wkzWuh/Zim24
kNY6G/Gwcp+7d/DZ+SG4d5EcRDQm1iL4FNyaUD2YXO3Bsueh6m8/dzlEZw1jn9hxEQd/vsK5FV2Y
tX0yBcTyeGFzhxGFTKVo08xC4IpQiuoqHcTVkr3iHsI4IivuPgNJ3iKnrdFHcs8GeQ475KNt4Qa5
vtW/imrdINd313NUa98i3xy9by11YLd1xY+A5tOIs/rQ2DANRLXW8yl/PQ6qBoyGirRM0I0IaRyH
a13HBLWRu57y1IM+V7Td7leaR8xVxLZO4Y4V3mGD90nPd6qpgl4M49x8aCwcRVGI0yxYs69luWsU
h6feC2gDMzT796segWyI/ll/Gagt5dy9XUE+ouwt3XDC0T3y7UR61VNzg3rEERx/Gfcx8DS8in07
ayLE5FQtsBMiK29f2LLeQhp+JT3OHGgaDk5N829q5jfqwqtxpsBJQVvpxB3LhPvRlqBqSZqCP2N8
1TRYS22OYo9H9s58Rmjx6O/nfAoR6GVLKuAV7EzZUxPoQhDzrZ5w8xEplOJJBfIR28i33xgXrcZP
M3tZeQLhohRZjWvzzBAueoZLX2ie8ghTEJysT7xVCgUVWote9xwuml6VXicd5cSLZkHBXe+thReo
okdGP07N9ZCBnLInanDl1WzWcOPLi1p9zx0HcDge2IXQj1jcW6qgzcj57LFUHuhAbw/ZhOL6eA5z
FStSFNPoBvG9Uke9y7MFy3p+gF/dHF6LXFACsySX62fH+bsr5wK28KRiLmwLgEah2eweengAKwfN
0ZtOBS8H2mc+UxcCUaN0axxcaAiVgFxpIsHgpTeXg+jMR+aMWA52RFOYW+bJVzc6j7Cry3jcyGYJ
FoTgHbWmu3N/wWOiE6u5dSzgyT8x5Xo+ub/d/MtbhwsMmKq35glTcoD/zp8fqgNFYxlNrenLq3fQ
estRmjPm2G726gLaUKOsRk+8EHbKlPxxekXlAzXOY4icttKfOxzQFrm2Pp+h5R65Zv0jVixboxsT
8rk46NboJW4xsmhb+tnpGHbIOWwtlfeEYPTR+558qP1l/YI4rNWhx5y6NejQijyQD81UrCXlY2RO
kc0tvkDCeMQ6nPLLXOeY0Td3qOv1OCieVcyULZwbD8FXimAnTHCKoDrehcY8S6OTXu/jvlszp8p9
N6rB0jLzOgr8ONMEnVXJRUWtq1XZd2mkOp5FuD40M1QUuFbUp+ZWeYD4ellzoGoDkCVPdpDZeKYA
rNmM4NUy2kddxrnJfjw7GFxo7HxKPMIZFbH+FjrtjHodzrcKCh5WfSYsWkQneu7R5SHMnPPdYV3x
hjuCj6v7LYQ2jSj/tfgkuc/6yNp1voVS0yMDdz3Op1LOmodAr0YKZ3dif6UrrU8F3IdnYSHnUyjZ
cUKKjxhaJ94ox+GzOSPhxrB5DoaNMGv8dRV+lalwviVQKWVP82QxhkrWmzWtXPRKHT15HA5WtIRq
yf2WCE8PUR2K6Y1AhOeEB+saQPAoZvOpqRm9nL/Qm3e2igClWKsah6bCpegiyi6TC/LzYvY4iAxM
PjMllssqAzyF4i5rgKfknZqRcZmTP52CVgVELndQwClkdzacXj0F1oq5iFIJrbk3bUEAQiD/WwhA
qFqhzv7L/g6bdgoDIZfNu9PRQ+LlQ1mOAowtC9diYfFyfNerXq98FFINzd0sGi1B/OsGwDuRPqET
is1yYxetcufY24LnF70TU3HV9Mrac+aM5m/nA/B67Wj+Rlq9TzHFeII7Q7LXNDW9n/ac8kGoj1xc
7YSk0FdA/VLCCKnBNft7ITCsxabm8+T+htHLy1jhGN5tjHgZwIt8rdG2yCEZDzhwufAyFjemET3S
rjRTmJsYxmkYvc44mZDSpUisJYpXnlEmnG2M7MXqxTPelWJyciB5fNQ5v4zyEBgMB0scNVWdBdTh
POnu7JrceQMNXeY3BcuhUFrXTJ+C5VCXgJP3rTRy+Kq7MUksnTA626zXlURO0gg1voxjg9pSeLVu
XM8ZrpizdeOF5qn8CMpC5qilwjxqI4MrjFST9Z6jqXTO+ttPjz5I4Wp6SZPnCA0GAt0tez3sSMZL
xWMVWnbVbETARmTJ1sVW2NteNIM+uwWtWQMjVc6Uu86z11fpN0fmYqRmtOxNnihlMUZCLtVdF2If
ldBOdSwJqYrsHhAYqaFmPZsnr1Atr6oJDkfxIDuqJjjzE6BbC2nNajkqaKYXM85U3APJRUHPZ7Ik
g5gMRfPC2m4RbbrNwXuqmIjKc6OM/1pRnaX1zQ0yxbSJoUbNYwVC2pijHmYq5gHj3OhW+yl+O/Wc
b9XRibh7BwKel9K16Mx2Y33F2H1/8CmggwC5wk+hip6K0eMFPC9cc/Z4QUnu9myO0eRWScJTdpUM
XC8jQN/7FrZ4oMo132EByhb7a8e9zO7JgnEnOqR4OoZGTRfqNyxcb41AyDYqWDnLRNxb6Hen2nkm
fTeoWI/LqP1ZfT2OWpHyw+zxhoer3LB48qHAVZ731oDmGMXodRuvhri31vSRmeLe4AeKrnk0cqus
OTJ1bobjUdubdz4UGgDb+VbD04LWcE9NNqI+LY/uBr2S55SotkWu1dhXHZK/Jy+Jt8j71lIFXe2Q
j5bHG+QlbpHvzX2ogHVm0M/KGWzjKS/IKx05INyOlyGqUS7ts5kHL0NoAc9E+3Z3Pun9XnChmcLd
BH/Wrsd5KoiIIz8i0ae/udAgkR3vB5d1WiTD9EZj6/QhvBQO8bVR3Ovp4UV51Gy4DGuBIF6UufHO
shOecWLWrLKoAC+Asapl37X+Op+G1+xLCRd9r+44con30wZbrhMgKg+nijNnJMgnPZ+5+Rciolra
2YeEKmyjON7lb6xXY0REcXXnJ8A5jLYjzjoFOGcq5Il66sgcxjPc+ujBi9BCbDtyMZBWqdE7isgm
km2gm3U64cqogpaip07QZfms9L7mDfKJzkymNY9Hh7LR3dfhDaNTW+0ej1FY8XRxruUWD/uni9OZ
D6JRyTshiIsT7Z1vJPKCtCrCdbR0Te/6eBDsyeNyGR0W4t2JdS7R+MrLvHDUojPBzaQV1VwEA6El
oXgbc7Zm1oL9CPJkw8/2kc63OQx/0Hq7gbs4RC1aU74RCyOiEpsJyiI1bLTpWm84il6IsdldTpxH
3BV1QsH2HLSoP7wHAXedHV0u404VLVDztDdPDZAY6r3HtKMGaFR5L2pc68unUl9unLUaQFHFTkye
oOOVXZZwp/4uNB0N4101iqSkFh940SC10ZUvvKCf9WgndeIYjOg5ba5OW+Ee5ZBvt+FC0gS/kWvw
yfkR/WI0P1ua/oq9X2tE+Q0qPemb3MZrFTxJdlcRMGKbRzXL9fYx4Q1SK5QnhwPzz9eeZb4dyiq+
cOBSHyN2jdlYBE9F+vXl9hhENtDF9wlHYY9cK9nnyhVtizxtkRd9sT1Xrtia+4gK2yDPW9tEfWup
o2/IBnnPO+QD1X2Rn8TLwNIo+oTLMD8dGiiCoced/KQC72S+0kzoEN7b4A8jdkWupKczOdQi3CJd
0VhwWNBnrZHLHkJpImRAX8Z5dKnR2fzMWQLCi0ZUmTM9hBcN9bAMQ49IUqaquTU51ODCL9X9VEe4
BbsbA3wYUvJWlYbjpqtVzcUnxIYp7oyTiEngovfuCb3C1hwhGpdPTzFm9HZ1rpcgMvFydS7jvkd3
tlED83uZSCO0SMvahARRXqsMRLTmDXpEkZ7eBBaRPq6HmcpcoCXU6b1Ys6KjaW3O3pSRVNWiOWZP
jddQazPn5h07FF+005sqWOAJpmWXBhUrRv+79TJzRqQfR0/24bnLJbrsQuaV2O/Z00rAoWfb6fVZ
RD3GVrSSvKvHeFYI+F4C4d9LuTV3O8WCKSNnZS2BiDirZNZp0WuHEi/sjTMytlJ0tW+JYhWewR7L
OY8srqLnM/nz0Gqesz5Zj35ChEEaZTZBUzjoKd7suWOowCvC7MktgslSvz1WF5r+apfjzE+AChuF
PI3TfjrL1jxG4IZepS1YL4qAeyjeCUFBxna+sKzzeRCSkW5nvLa2UJHzfHFZfzvV9+umTV5zjD56
pTqtOYwCjWeq0yRZFxo8I/i7SaPOld7NGZomuXf63f3g1FBLB2sFOKPZ+orBvdBY9iESNenrdULX
HVFXyT30LGLSq9nep3QtPE8lYzJMrsZR3D/tbO+At6m6Fg3KOobuG08MTzKzq4DgagwtuFc7moaf
YWLrTzGCkfztRIWNVoq/rBpeXQbXhhoQL1Wz5XbKYn+2Zlj45F7RV+2zp3GPXF8W30HY78kr75Cf
/t7vyWlrqZT2yHPaIkfxxe/JOWzxnbV984x4t5Y6EO8ytvyCeNc5SIJk5MpoisYCK0EyctDqlWbK
VEJXgFGV8TLOVJURz09Bz8fC2czvaJVlrG0saPX7QNLFjh28X4ZzR0Kzg66WbqPmULnjLOl6GceW
7xc9VPuAuGsWCpqJo767w0IExMfkb2l7J2VcvjVhXEQ0NvWtKVsHFflGO4H1fBB8WnPUW2qzq9DJ
6HRNL7c0xXcqzodmQqwZEYzU3flk6OCu9mJuMfDzcWY9Z9STLzF5+5VG4t2IJrItWS8oFpUY2ech
Y0+7WtfkkxXZCDlXb99RG+Tls1tnabV3WqIzn57erzzrdCbUDynZ5U8OCJ4L0fsWeg80zlo2bE8D
OGRGl+L12kejulGrfs3D0Y/g4bwjutWe9zkCFgmOyR2miEooms13WVpne0pnWaNXulYJ0zgk8HIU
03K2Ag23jZKfIl7Lq8Xch+axjZ++E765ieon/sZq/vAWhboM5sJNJEe8X2mmZ8A4gvzUtyZVm9AN
BI+mzregbjIcPnUZsIeb6Cz+V5dBaqj9W1tQ65qyhUXd5Ny6O2dRNzJl/a1H87KJmo9qDdN1UeEk
Ip/vuFIGBK82YM8tBxVHVbr1mvCMWnLRPL65Ps6a+Wse4x31zO+aePOhSfmVxbPeT+QunFk8zrdQ
4EZPedKyZ8cSLYKPtnp5dca9/M1Ni9M0nP8Xmqd6wRVx9l2PazuyNjGWcnI/3cOrzK/D4V5fj2pr
miwGgwAldzdxcciGK/ZNF1DkM4r4MozV0zA3R22HSQCdOJwM0zK5SxD7oY0qIWuOnv1oDCtu3j/P
ak9rScL7J9XosxStD6NWVHMSLrzFjW4k50PT6IgtRfdbCMxISD++0EyROGJfhewqRbnPjzC6mkw8
dHygDQHo7K0Tb5u5ulsj+uaoo/OeQ4OnTOr+pwiJ/Hdn8UIiByIV9lQOXjfFmtLXw5QGG46RD7cW
FNSa6kTsMl20eEzZnY3Yh6K4qztMTy+Pz1qxo9Ivt3wnS36l36SXOaWhigzUklxVhXYzNWg5mVNe
yyHLzJ7+QDDOJARP5bLgDRshtmvVhcJSZ32+7/USgmx60JfpFPTTUN0klpv5fmhEjRNpfTKlOY+L
OxRvf9FdpiRzuU9RNaIrRiu3tbwxHKCB3QsXHWiaUTlTy1N0sO93LP3QjA72RmwftnME2ZCZnn1t
HeXZ283hXA8rGvvsFeVwpqJuMunpTjE2yPOId6auYxKqIZ8LNW2Rj5fpDXLeIh+g9HvyErfmToG3
yMvWZEhbz8+5DXmLXMvo8xPiFmeGpC4DElF5qZyX7jo9AakQfQCcZfAongfrKW/L6LnRNDQPC/gT
nXbXbIWrmvNtt5Xz1K5TM0bCol7X3CVUAOkIbKzLSDh0YDm7VlQbpnQBYQC/Qc1neq9E1N1p865T
RVpExw5219XwGNCzy2dkwbH+1uc14N/k3/8DayV5NgplbmRzdHJlYW0KZW5kb2JqCjMgMCBvYmoK
PDwvVHlwZSAvRm9udAovU3VidHlwZSAvVHlwZTAKL0Jhc2VGb250IC9BcmlhbE1UCi9FbmNvZGlu
ZyAvSWRlbnRpdHktSAovRGVzY2VuZGFudEZvbnRzIFsxMiAwIFJdCi9Ub1VuaWNvZGUgMTMgMCBS
Cj4+CmVuZG9iago2IDAgb2JqCjw8L1R5cGUgL0ZvbnQKL1N1YnR5cGUgL1R5cGUwCi9CYXNlRm9u
dCAvQ2FtYnJpYS1JdGFsaWMKL0VuY29kaW5nIC9JZGVudGl0eS1ICi9EZXNjZW5kYW50Rm9udHMg
WzE0IDAgUl0KL1RvVW5pY29kZSAxNSAwIFIKPj4KZW5kb2JqCjEyIDAgb2JqCjw8L1R5cGUgL0Zv
bnQKL0ZvbnREZXNjcmlwdG9yIDE2IDAgUgovQmFzZUZvbnQgL0FyaWFsTVQKL1N1YnR5cGUgL0NJ
REZvbnRUeXBlMgovQ0lEVG9HSURNYXAgL0lkZW50aXR5Ci9DSURTeXN0ZW1JbmZvIDw8L1JlZ2lz
dHJ5IChBZG9iZSkKL09yZGVyaW5nIChJZGVudGl0eSkKL1N1cHBsZW1lbnQgMAo+PgovVyBbMCBb
NzUwXSA0MDQgWzYwNC4wMDM5XV0KPj4KZW5kb2JqCjE2IDAgb2JqCjw8L1R5cGUgL0ZvbnREZXNj
cmlwdG9yCi9Gb250RmlsZTIgMTcgMCBSCi9Gb250TmFtZSAvQXJpYWxNVAovRmxhZ3MgNAovQXNj
ZW50IDkwNS4yNzM0Ci9EZXNjZW50IC0yMTEuOTE0MQovU3RlbVYgODcuODkwNgovQ2FwSGVpZ2h0
IDcxNS44MjAzCi9JdGFsaWNBbmdsZSAwCi9Gb250QkJveCBbLTY2NC41NTA4IC0zMjQuNzA3IDIw
MjguMzIwMyAxMDM3LjEwOTRdCj4+CmVuZG9iagoxNyAwIG9iago8PC9MZW5ndGgxIDI4ODMyCi9G
aWx0ZXIgL0ZsYXRlRGVjb2RlCi9MZW5ndGggMTE2NTgKPj4gc3RyZWFtCnic7X15fFRF1vaputXd
IQQI+5KQ3CQkAgkJhB0REkhYBtkDJoiSTqdJGrKR7hBwFMIoAmHRcWEAN0BUBJUmIAZcwF1RxA03
kMVl3AUdl5GE9PtU3dudBUZn3ne+f75f0j73nKo6derUqVOn6jYEiRFRS6ogjfqWlDpLvnl0wSdE
SV2Igi8U2Qudz7K84UQzbiUKa1VoX1TS4o2Q24kY2kkvKHbYif+cQpQyjqjDtvxCz6LDW90osyEo
b87Pd9rbFbbdAdmfgB4o5h4e+gt00VPAoLyCxXM/fvPPTqKMb1HeNrckr7D8sod/JuqVT2TxOhZ6
9PUlby8kGobxrH0dhfaSvL0TbyHq+AFR+3Ukbedvffvnmz/bOKfN8J+DwoJI/mz99LLekj5+RdUr
53ddyAsdFnQlii0gz5QAnrYRdZNodCid31XXP3SYWR/4sfSUNZaeeIwkB1mIUygl0SgiERJ8Ab7i
VrMLHxqAl79P1wo3dQTG27pTuWUmZbIVNIvvoOsltO6UIh6hUsjuQDkV9IDsC/kZwClgODAT6GbW
TQTswHRZhux+2Rc6SqQeRd00KyiSii0zfRcw3nrLyzQXuBf8VvEpbbcOpUKUt6HfQUE0WMqgz3rr
DtqA+rvR7kDdvaCZKG8BPxv9+pp8C9ta6iopYEV9L+hZbc73Mu1ZGiTcvjOYSxZ0/gm4GWNMAR0D
TIBMe9BRwAr2Mq1kL/u2oh2UbsT4K2Q9kGbScdCzHO0j0a8HyjeC7wY7rKBtgCigJ3+EhvIO9BRo
EuZ/lTFv4GXKl3MOzAn2mzZdDMPGCQ2BMZ8GYvhQ3+egLRrY1hQ3NsF4rT9VgM4HwoCp/AgViiuJ
wV8bLZ+TJoHIlH46CVwhcmkSygx2TrfspU2yDExUcPsuiLtps/YTDUHbddb1mEcu/N0P+IWS+LfU
xxpLSxFfadC/DLgXOr9U8ZBLGRg/EbS/+FzF0M3AGox11u8n6RuUl2Fdp2GsWrlj0H86MBbrUgEU
SHswfpL0uVx3NrNuKGQ/g8xsCdR3VsDcZUzKPrI/dMWacbi1ntJWyKyFX0+DCqCjtMEPFWcm0PYS
9HQFrEB3IBH4HNgKzAeGAU8APTE2YVxNxStiRsamig/EhuVl+BC2qZg15nCvWk9jz2wxdclxoqyP
0HwTUVKn3C8yZmHLbr9uuadkzPipiu/5Mu7ZD3KeMqYCFHtPfENjpQ1qDyK2/FTuO9gs98N6PoNW
gm5CHN8oY1ba56fSLzLWlE+wJ0w6vMFc+6o9AqoRxZixfqOf+n0RoPm0DTqzrTnIKZtpnPDQOO2v
lCPOUZrWixItfVGH+UDWy7+haUGHqD/WcjLKG5vQDRK2Y2ye5RDmuRP+PEb3wKcLxDEeLY4xi2Wn
7ysLsVctO/kSxV9Em4IdMtoklWjY9p/W/2/A37PsRM7c6fvacsznw3xuk3vC9g3rC+h+ivoqoALo
HRTPNgTNZ9W2GRRqxdkGFIsUGmZJocHiENanI/I89gLqZ1jO0EFtLa0Sx3wfsgqq4MfoZltHsvP1
yGkYi79HN0pI/aAlDeKoUcw1jSU/9cdrUypzvhlTkaBW7L83THxm4hfgZ8TR/cwYY7DMz+p8QI4G
bjbi1Xc+EJ+v0gOgq/3x2SRO5zeJz5CmcdmUqrMF+d2/T2HHKv/8ZX6UOU7mSJnnZJ7xyzelDfpX
8h2IY5mHj9Asc19Hm/gTbPzE3PvIw1jvq3w+6xjfQ9a9vu1aO992azL4DwCL7yHMe1HgTM301Znn
aS//WWrUU0v/OWrpT4VmPtum8s2PdIc6R2cq+1pYd9FSSw3WHTlQ2bvZ3IPwJ+yeL7Lh8020BvPo
qq3AfkQ9MFv6RK0FURd5LsgzUbsTfpZn0Vq6UTuO+4Ls25/aqvNiJF0F219VdThTJZV1lqtoq/Ub
ShYzkGsPUa5cKzkPaY9c+6AyahXUEXniGPUTD0OmIwVDbrPyQQo9pOJC9p2PexF8YXOQDTE7CTJS
3xbVJ4Xamf7Ypnyh+uMuIuNL+gI6rR1pmrpPfEP3WWbQVdhDW2wVtMU6A3uuI22HjgfQb4a0Bf26
qfP6Troa+2slctNK5BxS8T/LV6PtxHwWIa8DWgV8tJO6WCrgw/lq7mnCyLEr5P7RdlCcjBHrncjD
8j5xJ1WKeEq3zqe1qFtrQZ7EuKtRdxP2b1/s3VXoH2nmbcLYq1Av+46Udxl5R5D7xZZC7a0V6h5A
ygZ5T8H42le0RfsTrUQcpwbdCT8spz44LxhiLwLoZ0CVl5hYY0DVhRqURWmhdIOq709v8x1aS8St
PEP3i2XkEjMpWetHXUVb6iPewl79je7S2tAccZjuEtW0RpZFe+qpeTH/vbhbyvqjNEXW87dR3kCz
xHD0X0lFYg65td2IvXcpWMzFWqOfZR3ipAf6/wi9JtinNEubib11M/jffI9IOTXGXt9VEmIc9VH9
GkDZ6kcTm/kE+O1PWFPYK/lG9sLWgJ1+Gy9hn5qn1It+UkbcRXhn8Z0AYg1aN5WvpZ3AZv4RjdYm
0mK2HQnmbhrDPgfuNvEojVN0NzAVZ/xAdj2QKAbSE8Ay8AmgzwC7jDLubgPpOLAcup8F3SPfCyT4
KBokKeruBTYAr/nbGkKOdan6hrCEUePy41QhwX7yXZBoKg8/D8J4g8QV8CeAWLxVwrqUZtkWYv0u
Q30EdDYpY5xk8TjN+yN7/gjsKPVVPjSQ0nCO/vUA7fRv4EQDqktqng3/J/v+N8D6LgWuUf79njqa
MdSavUfRoDNBZ2pltEgC5T4oZ/n9yfD2q7Cdblf1gfUz6hEreKWkK5rWNy03Xdc/KvM99EBD+OMg
EA+30U0SYiTkgabloFfpJgnri2h78eKyeOgPMIt6a5uUTaRirEnZOhlnJsB7wNZuqs8aiUD5KPYy
IGVV/1a0VkLtXYDvJZdEoH0g8jfQwK+DpF8xpmr3r49/XZquD+xLEW8As3BWvEF9QaeDpvppIL7N
fNEo5qca8R4oy1zyeROZ+j1RvzeOyrPm0jr/fwL2zmHgZeCl/9djySwjc0SozBMncA8ZiXvkMdxP
rqYbiS4gl9QmAQ8iD2WAvo86nN51vYBW4NuiLg/0HqKan8GXov6YAR8XYbTZvFd2Rd0+s2+QqW+6
0b/mFaLziKjzu4z+NTuAeeB/AG4A/zHos6AbIP81+t0E+pzRfmEOyguBp1D+BuUCIBP8raAdQROA
9kA79F8vIe8jF72H/tfppd8//l2KO4sDdkbK77xAr2/6DvFvU/96/gFt+q7hX/8/og2+M2hCDT/g
nekT3Pu8Dd99fu8dx0+xnnUNIWb4LuBOGSLv0fIuK+/P6v5oUvX+pu6xGJeog5/Ku7O8v8q7s7y/
gm4BXWm1KHtmyPd8aRepI0UhXG0IajENJXDBmSRaDJLf0cqvQWkILWFL2S3sNraFedkJ5uNZ/GX+
Kv9YY5qmtdBitCVapbZG26K9IULEZDFbzBG3i7+Je8T9Yo94UnwovrLstzxv+drykzXEGmaNtA6z
TrPOtxZaF1iXWG+2brBusz5s3WV93XrM+lvE8ojf9DZ6Rz1Cj9bj9ES9r95fH6YP10foaXqxvlTf
pj+kPxJliWof1SkqOiouKjEqI+raqDujtkfzaGt0m+h20R2ju0VHRveKjo8eF22PdsbwmNCYqFiK
5bEhsaGxHWK7xIbH9ohNiB0QOzy2ILYi9qbYlbFrYm+P3RL7SGxV7IHYp2JfiH0t9mjsh7F/jxse
lxI3Ki47zhE3N27+l5Yvu3w57Bw/16+G1+g1g2qG14yoSa1Jq5lck1VzQ83qmjtrfLU5F0Ze+LGu
1lfr88lvwGmz8txmtosdYefhuZfguQ80CnjuJnhunXa/YKK1mCquFbeK9WKT2CoeE9XiA/GlxWt5
0vKm5ZzpuShrijX7kp47F1ERsVkP0dvrnXUdnusNzyXrQ03PzYPn7ofndjTy3PSoq6NuDXiuLTzX
NTrC9Fx2dK7ynP4vPDcl4LlbYzfH7gh47jA89wE8NyzgOWfcvC+Z8hw7J2oYPNe7Zgg8l1IzumZM
zcya62oqa9bV1NZee2EEPFchPef7FIF5p68DP8yf1pJ8J/jr2BFtEJG3sXI2n5XWbkbZJWO2Lr6u
d12vup5gr6fraCEVUD5dSSNqP649Uftm7Wu1p2vfrj0qJWs31m6ofaR2Cz631y6tvan2L7Wu2v5E
n15D9MkJ41v908uBO89cffqm07+d2X66HKUnAOTV05WnbzhTdmreqcWnD3yacHrdqe2n1p9cf3Lr
ydVEJx+UfU91PrngJDLzyb4nU072P9njxJgT6SeGnxh6YtCJ/if6nuh1IvpE2IkOJ9jx749/c/zL
458f/0T2Ov7S8YPHnzmOUY6/ePyB47uOpx8fdTz1eI/j0cejjkd0O9TtfLczoc/gpveM7UHbPba7
bXfZNtk22jbYXrU9attiuw/n11fWERa8nWoOuXfZoMZ/TsH/bqBR+ZzWyV/Wcul3frRJyDSXblkH
3Isb0SQxTWSD5jRsFdcCcw38qx8xRUJMM0uTfs+OJj3jRM8A3+N3JYP/ZcuVjYoa3U830XLtWlpP
f6ebaR2tpnvoYdqGK0Il3Hoj3U7n6AdaS3+jlfQcnaCzdC/toH/Qj/QTbaVH6BV6iR6lHHLQrZRL
h8lJL9Or9Aa9Rq/TEfqC5tJbdJTepMcoj76nv9K79Da9g1j9ir6hVTSPXDSfChG9RbSZimkBlVAp
uamMPIjpcvqSFiG6F9Of6QbE+RO0hZbSEqqgZfQ1fUv72Xr2N8aZxgSzUA3Vsg1sI9vE7qILVMes
zMaCyMfuZvewe9l9yEVbWAsWzFqyELaV3U+/0K9sG3uAPcgeYtvZw2wH28keYY+yx5CzvGw3q2J7
6J90jFWy1Wwve5ztY0+wataKtWb72QHWhoWytqwdnaYzrD3rwJ5kT7GOrBNbw55mz7CD7BB7lj3H
OrMutIu8rCvrxp5nL7AwFs66swj2InuJfqPz9Al9yiKZzqJYNHuZvcJeZYfZa+x15Mw3WAzrwWJZ
HDvK3mRvsbfZO+xd3BAuYz1ZL9abPqPP2TF6j07Rh/QRHaeT9D59zM6yc+wHnFU/sn+wn9gv7Ff2
T/YbO8/iWQ2rZRdYHUvAOUaccc41LriFW7mNB/EWPJj14S15CG/FW/M2PJS35e14e96BJfKOvBNL
Yn15Z96Fd+XdeBgP5915BI/kOl/Do3g068eSeQzrz3vwWB7HL+M9eS/em8fzlXyVJdTSlp/Vlmk3
asu1Fdoqba12i3a7dqe2UbsHJ+cD2sPaTu1RbZe2W3tc2689rT2rvai9qh3BXn1LO6Z9qH2sndE+
177SvtPOaj/wH/iP/B/8J/4z/4X/yv/Jf+PneQ2v1YK1lloITheGSW0TD4gHxUNiu3hY7BA7xSPi
UZwqu4RX7BZVOJn3isfFPvEEzpn94gDO6afE0+IZcVAcEs+K58Tz4gXxonhJvCxeEa+Kw+I18bo4
It4QR8Wb4i3xtnhHvCuOiffE+zilPhQfiePihPhYnBSnxGlxRnwiPhWfic/F38UX4kvxlfhafCO+
Fd+J78VZcU78IH4U/xA/iZ/Zp+wz8Yv4VfxT/CbOixraTVW8kg2gx2kfPY+3oz20l16gv9CztAK5
aLI2TZuiTdVmaDO1q7RMbbqWQT+zL/ghsYSeoo30HXbmA3QbG0m3sFS2kP0V58XtrJyq2fXsO/a9
WCBKxTLh1rK0WdrV2mztGnGTKBPlYrlYKG4Wi8UKsVKsEpVitVgjFok7xFqxTtyCE/mv6ky+S9yN
O829uNlsEBvFDeI+sVlswUl9vzZQG6T9Q5PviFYi/x8UM44Hb5J20KgJi9UW1CK4ZUir1m1C27Zr
36Fjp85dunYLC+8eEalHRcf0iI27rGev3vEJfRKT+vZL7j9g4KDBQ4YOu3z4FSNGpqSOGp2WPmbs
uPF/mnDlxEmTp0ydNj1jxsyrMrNmXT37mmvnZNspx5HrnJuX75o3v6CwqLhkQanbU7awfNHi6/58
/Q1LllYs+8uNNy2/ecXKVZWr16xdd8utf73t9jvuXP+3DRs33XX3Pffet3nL1vu3PfDgQ9sf3rFT
e+TRx3Z5d1ft2fv4vieq9x948qmnnzl46Nnnnn/hxZdefuXVw6+9fuSNo2/SW2+/8+6x997/4MOP
jp/4+OSp5rtj892x+e7YfHdsvjs23x2b747Nd8fmu+O/d3dMSU1NGTniiuGXDxs6ZPDAAf2T+/VN
SuyTEN+7V8/L4mJ7xERH6ZER3cPDunXt0rlTxw7t27UNbdO6VUjL4BZBNqtFaJxRQnrMmGzdG5ft
FXEx48b1keUYOyrsDSqyvTqqxjSW8erZSkxvLJkCyblNJFMMyZSAJAvVh9PwPgl6eozuPZIWo1ez
WVMzwa9Ni8nSvd8pfqLib1V8K/BRUeigp3fJT9O9LFtP945ZmF+Znp0GdbtbBo+OGe0M7pNAu4Nb
gm0Jzts5pmQ36zyCKYZ3Th+2m1NQKxjl7RaTlu7tGpMmLfBqsen2XO+UqZnpaWFRUVl9ErxstCMm
x0sxo7xt4pUIjVbDeK2jvTY1jO6Ss6HV+u6EQ5VrqkMpJzs+JDcm1z4706vZs+QYbeMxbpq383Wf
dakvQnm70ZkrGraGaZXpXVy6LFZWrtC9m6dmNmyNks+sLOhAXx47JrtyDIZeAydOmK5jNL48K9PL
lmNIXc5EzsqYnzMmXdZkz9O9LWJGxeRXzsvG0nSr9NK0xVFV3bql7Pedpm7pemVGZkyUd2RYTJY9
LXx3B6qctnhP1xS9a+OWPgm7Q9sajt3duo3JhLRqyDgDbYpT4pKbMC3gWSYtihmPgPDqDh2WZMZg
TkPkwzmEKh1DIIafLIZe3lysiMvbYnR2ZegwWS/7ey2xuCNW/ozcnh3z3beNa+xmjTU29GeSrIyT
QKih3c974+O9vXvLELGNxprCxhGqPLBPwsJqHhNTEqqDwH00Bb61Zw1LgvujouQCr65OoRwUvBVT
M42yTjlhVZSSFJ/l5dmy5ZC/peMM2VLhbwl0z45BJO9Vb30dvUFxgf/ahHZqn54/zMs6/U6z02if
MD1mwtRZmXp6Zbbp2wkZjUpG+5BAm8l524/O1MK4yfEwTbUiKGcHhGUhM8QrYvGfVQV1brUtCFGp
apg+xhuaPc54ZgVHRf2bnap952QvReq7mWZ6h8U3Ll/eqNzIvJBKDQaLOD4hY1ZlZXCjNoSaMeB4
kyDiKSMzSh/tpRnYmbH4r9p3aIhEVpg3BS4bLQUQf0aVWWwkGGbyWfiR0dknYQwSXWXlmBh9TGV2
pb3aV5ETo4fGVO7nz/HnKkvSs/2BU+07sDrMO2ZNFnyVz4b1SY2hNlpnOgv4AI0i8UwCJgNzgFuA
+wCrkpM1xcBS4CBwTrWkaJ2rbuufUg2yWpE98wqSVdFuFGdfo4p7rsoy6MSpBk0bb4gNM8T6DTCq
E0cZ9LIEg7aLTa6QNLhV8qHUTri6vwlwKsGT8ReoDWMUSZu1juQFuGY1a1K0dnt6xCXfd1AThOuA
xnAtjfQd0lhVq7bJqcHcx89SO4rk3/PvjBb+3Z7WbZPvS/0T/4R2AQcBjX+Czxl+hpby09gBbfAc
CdwHHASOAmcBKz+Nzyl8TvKTkPqYkoCRwBzgPuAgcBaw8Y/xDOUn5H5ST8mPBDg/gWcoP45pHcez
Df8I3Ef8I5j2TtXgocn7FROfZDKRsSbTOcxk2nVKruZvV/3WK7Kaf7pHj4/cnNqXv0tegGOwd6H8
XdKBKUA2UAJYwb0H7j2qAG4FNgNewIo+76HPe+hzGHgdeI/6AinAFCCIv1mFYar50aq4UZGpnfgb
/GXqDKce4a8o+jp/SdHX+IuKvgoaAXqYv1QVEUmpLdFO6BMKGgqahHYLf3ZPj3aRvtS2/CDcE4ln
EjASmAzMAW4BrPwgj67KjWwHJU/S4SCCZBV9peiDtDWIUuZFpsSNRozp8hE37ApweNyn3xfHU+LW
b0RRPuLW3QZOPuJuWgNOPuKuWwZOPuIKFoKTj7jceeDkI27WHHDyETc5Axwe1fzeJ3pcFjl48nym
p7bh5fBSObxUDi+Vk+Dl8kO/CWnbXVW9e8Njm1Lie/WOrDjAKp5iFdNYxVZW4WQVS1jFMlYxnFVc
yyriWUU4q4hgFSms4kk2BK6oYCl7GxWHpnRhFYdZxaOsws0q4lhFLKvowSp0NjilmkdVje+vSLoi
e1LlvgK9YkRyG9gYBY9GIayjsO0P4nkU8KlSCoT0aEO4a4Sk0Xt6jzTKicOSi1PH8efR8Xksw/N0
ChBYoOcRRs9DyfNQ0AbPkcAc4BBwFvABVkhHw/Bb1LMNnknASGAOsBQ4C1iVOWcBTsWmibuUYUmm
0ZNliT+PTzQ+UTwqpXtoeGh86DjtlnDWJoJNjvBF8MHUSb7lt2sb1BZva/t+bfXPX1tRi9QWfB2/
hbpjIW416S1Vv3WPrGYbquKejEztyP5GEQJRx4ZSHIsFHUJuVR5I4UGSDqBwvhM0uSp8Jrq1qYpL
iDzAWste+yJ/C/8s8qvwag72y/AnI9/XqwWrijyGmp37It8NXxX5alJ1EGqeiqtmIAd0Jbo/fEjk
o4eV6DI0bKqKXCLJvsgbwsdGzg9XDU6j4Vo3SiltIqfFzYocB31p4TmRKW7o3Bc5MvzayOGG1EDZ
Z19kX5gQb7C9YWyvcDVoTIRSOGNwNctPSbCtt2XaJtsG2ZJtCbYoW6Stuy3M1iGoXVBoUOugkKDg
oKAga5AI4kEU1KHadzolXn4B3MEaKon8OwOMhOJDuXzK74plXmNBnP5E3vbaBD5h+ig2wXvIQRNy
dO8v02OqWTAOUEvMKOZtN4EmZIzyDomfUG3zTfMOjp/gtU25OnM3Y+uyUOvlK6sZTr9q5pNVy8Pk
VXU/MdZ2+dowSXsuX5uVRV06LRzZZWS7EW2Hjkm7xCPbfMbX/3RpxHf3rp8wPdO7o3uWN1kyvu5Z
E7y3y7vsfrw/n0tP249XaZCszP3aCPZj+jRZr41Iy8qaUM1mKjnS2Q+QQ8T8oOSCIkiXcqQHRRhy
mwy5WPSHXA9JINeiBcUqudgWLZScYFJut7tHetruHj2UTGed3ErG3VlvKHM4FjKxsUqmUwUdVjKH
O1VIGe8IJRIeDpGIcCXCulG4Egln3ZTIzHqRJFNkVUBklRpJY/Uy4YZMq9N+mVanIRP/7/44R8XH
sz2XZzlmy/eA7Jh0J5DtXb0wv4u3IkfXdzuyzBeEuOwcR76kdqc3K8aZ5nXEpOm7L599iebZsvny
mLTdNDs9I3P37BRnWtXlKZenx9jTsvaMnTJgcKOxVgXGGjDlEsqmSGUD5FhjB1+iebBsHivHGizH
GizHGpsyVo1FKsanZO4OolFZuHYquoe3DEa8ZodFZY3qFFoyQgXv5VFdloQdEPIv9rXELTwEb3St
ANnUJ7VPqmzCnpJNreXLntnUZcnlUWEH2HazKRTVbWNGUbynzF1GXdJdacZ/bvygylMmHW48493/
6gdt6XhvS3N7iCZ4e0+f4B2Je+5umw212XJK3mH+upYt03HdNCoTUTlMVmpaQFDWDZd1LVqYghev
f5lJR8tdUMGf3MNSIpiH3FmaN2JCBkcqyDBv1QdwXZLHgzsLE3SzeOb261Bmk8GTnK8fnjKTM/3g
ManRC13cfncEftAHqcpygLoC3SwPUVcRR12IfF8AX0pa5/J9Kdsl5V9DuNoE0XZ6lLnoUTpIz7Fz
JL/Z2097Sd540uhuup7uoBU4xWahZhVNw8eC+jtYV99eSqItOMe20BHIXkVL6AB1Yl18X9FSWq69
g17LqRVFUypNoWJay670ldFsOiVupMF0JRVRCavwZfrW+W7zbaMHaL/2iu8CtaRu5MDniO97ywe+
E9QHPe6kjXSK3dbicUrBKBWQvIdKaZN2jWC+PN95WBBF5bBB0EQ6wg7xeGh30hesC7teGw0t9/u8
vhcgFU7XUD5togNsIBvLoyyzfRN9R6gTxlgErRupivbhU01P00csxHLOt813jrpSAo3HfPbSG+yQ
VndhWd1I6Wh4qRcNRUsxPUMv05sshj3Liy0hlmRLiuU637vUgfrRDFj7EHr+nf3Kl+CzVHtJjPGN
otbwy1+lt+lFOsO6sSQ2mc3kvXgxv1crpSCM2A+fXHLB3xug/SSiZh8P4Ue1+8VOUWPtXnfa1xor
Ekd30T30LGuFmerMzf7C3mOf8tF8Dr+Lf6LdIR4Wb9vsmPW1VEhraSf9ytqxIWwqu5rls+vZCvZX
tpEdYW+yL3kqz+Dz+VktX1ugPS1G4TNduMWNlpstq61f1mXWvVD3Vt2vvmTfzTQV8bAM1t9J92Jm
++kofYjPKfqEWVhL1hof+a3vDPZnfJawtWyr+g56L0Z5k33CvsIJ9DOr4ThYuZWHyW9Z8YnhpbhQ
3sHv5kfxeZN/y3/TOmvRWrw2UBuuZWnFsGqFdis+j2tnRDdxVPjg52TLest9lu2WnZbn5J+n2f6C
I/312vsv9L5wso7qVtatr6uq2+s7Qx2xhjgs8Ao1HNbb8ZmH9V6PiNtF77AQ+K4b681GsCvhmTls
HlvAFsGTN7FN7AFl+2PsKXjpfXYWNrfi4crmRD6Qj+KT8bmWO/kC3L1u43v5e/y8ZtNaam20jlpv
bax2jebUPNpibb3m1V7XPtY+0X7RavHxiWARKaJFnIgXY8UcUSbuFV+ILyyzLa9ZPrcGWwutN1ur
rT/gEjPCNsU21XaN7RbbPtu7QdnyW1R6nJ5o+Ecd7LS2TEvXHqd1vL/oijeWNxDPcyhXm8gRqXw7
W8lvYHt5D8si6+X8cjaJzuHV/g7+Er+P/8Iv1yayCWw6zZO/qSp/rB2E/M3v4eJ5+k48hbm9Ac2L
rCFsCT9rDaEqpn5vmr2o9RXx2mv0kXaK2cQWOi6CWWf2HX9Im4IoeFqMsGRSlHY3PaYtYDfQ4zyd
KLgmaA3ieBLbgbyQwZLZPzUfbr2TEEWDtU/pRprPP6DvsI9X0t9YrsijddSfXU9f0IPYFb0sRdbe
1o7sVe4Slbw920tcPCx/n5n1YJqlA93ErtE2Wc/yD6mMjopgOqk9AuuP8se0ieKcZRrLxw64gW6m
Bb5ltNiSKd5meaSxmRQrTiO7Xa8liyjQpcgqs5HT9mF3H0AeSNUmoqYLIudKxMUMZIhN+GxAnhCI
IBf2+FXIYm/QXmsGr6Y8S2uGrEMkXqubRrN8D9JGXx4V+W6jPsgHK3zXQ+N2+pxuoe1sed2fqQRv
jh9ib19pGcOPWsb4+vBK/iGfztc3Xl94O5Z1oa/xeYzG0AjLk1Qp3qfpNNK3xncM0d0TGXYj5eB+
+hlm+T1GGKcdov51k/hu3xitBPM9RVN9D/kiWTDl+wpoMj1FD9gsZLfFmwMUNKMZzWhGM5rxX8C2
ZjSjGc1oRjOa0YxmNKMZzWhGM/5jcPkX9Sz4kEY2GrWXs8+stmq+MaU9WcRnGgXbxGeMugZZLZ9x
7Snej1qwjSyRusSH/jL8wvBJoT8Nn3hhOI0EH1qLR7++UW2j2sbiwUhQra4dqk2Rf8leF4fkn/VX
0SoRo52nVigkd+rUsQPFRNPAAYMG8flF7y6sq9v3RF3dwne186XvloJj/An3O6Wwj8Zo8jce5G/u
E9Wpp+QZBbMRJs+pteUk+X/D/1rLIZMXDWQs1MXyvclbqbU1wuRt9II1weSDKM52vcm3oMpW20w+
WDynRpZ8S8ppnWjyITS39a0m38q613rO5FvT7Na/BH41bmmbaeT/d1YtbX4weU62dqkmr1FSu2ST
Fw1kLBTSbrzJWyFvN3kb5bTLN/kgat8+1ORbUHqnHiYfzO1t3jL5ltSvk8vkQ6h/p00m30qb1e6w
ybemxE5H5L+IIDTYFtKpRvHqX3rt3FLxVlnfOUzxNlV/meKDFD9Y8S3MNTJ4Y40M3lgjgzfWyOBF
AxljjQzeWCODN9bI4I01MnhjjQzeWCODN9bI4I01MnhjjQzeWCPJBzeYb0s1l7GKD2lQ31rN/SrF
h8q5dM5TfHvw7TqXKb5DA/mOUo/Jd2pQ31X1XaH4MDWWobN7A5nIBnwPJX+n4nsr/n7F91H8bskH
NbA/qMFYIQ3qQ/xzyaDFVEJOmkt2coDq9DCQQfmKn0jFVAR4TCmdRqNUCl4+7ah3KQkdNQXonwgu
TdXb/4+akgKW6TQdLQXq93kMGTfqxoMa4/Wjofj0pT4ml6xqU9GjAHQa+uTBBo/qNQ363EApLcQz
V9lQhDYnFQYsKcW4OqTs5kiGvAse0tFD9pcaiyhBjSJb7Gokh6nLjhqjZ6HSKGeQD+sLlUYXWjxK
Ol+NJb3uMUdwqxk6VF+Pai9SWiSVNhUrG1zmXEqUbmmRQ1nlVqPJFimfq6hhf5kaTVcjNLTKpfR7
0F6kyuVKd745utOULVa6jLH99QVKt8f0iAMlwzNN5TzQ6VRecYEauh1mTZnytFyr+igpVutSqjxa
oPpLS2V0FJq9/CM4VP+F5qguc6ayzfBmvRfmQlJqM2rr/eoyvVtszsSl5MtUqX5V3SpiC5R1l44J
/85xB+Yi2wqVvnodpRhnvmmt3fS/Q8W0bsa932e5auw8VWv0L0eLy1xDKVOAtTdipBjPPLQtNL1t
aKjfy3a1VkZ06MqHDnP+LrVqBUqmRO0zIxqLVE9jJg2j2xWILB3ti8yVKVTWyNg01s1t7uSCgB2F
qlQfvZ4m+cbdZH4Oc4wcpaFMeTq3UWw6aQHq/Z4tU3+DxT/DuSq2dRUDi5Rv3SruPGo18gKrLm03
9rvcSwmB3eQ2o6w+HxmthWpF7HSd6m9YLfU6VGt9pBmj5ypvlahdsjgwC//Ysn+5arcrT5SaY8g9
ZHjRo/r7LfZrL1ExVKhyqN+2xIvy6rBGqybzXZ6Kf7m6w2imOZ4/18pcOQRPnXpCk1yDUrUfjH3U
q4GuiYjr+tJjKs5LzX1fqLTPD6zx/zbnG+uSZ2ZCp5nf6vOUoXUGzgOdpqj+OsWp8SbiORljz1WR
6/eYjE238na+qS2RJkEuA6fHGGA0ZiT5yaiV/cfgeaWqT0fNdDzlHhgLL6bjM1HVZuC2GqyQoaLW
fYmY1gP1hsXGypWYa1u/Fy72j3HmFcMHpSo68pW0fz7+zO+PpxzVuhjyZYExHYEcaviuTPWtz31O
c3fIDFWfr4084TJzs9vMHXlKizOQe6Vvs8zRZBZZaObsnMCpZ4zp+R3P+GOrPJAFnebOdgb2TqnK
Ux4zb8w14/5S/vLvdukxZwMt9dni4vFyzfiSsZyjMrBhdY65MkWm5kut0GVqVo09ZWT+i6Pi4pH9
OVRmS7u60dgxaoHpbbeZq/7V2Ikq9osa5PPFF62F07zNNNw5xilhVxaVKM/Kc8ul9tsfr7luxmJR
gxzqH1fu/lzlaVeD06q0wY0rISBd2iBu6+8Iv+8paV2h0u+Pq+JG+srV+s9Xq9kwm/jzcL1kMWSN
PFOmPC715wfmY9jVMLoLzcxt+N/YVSVmfNRn+MYx9Hszqo+P8WruF6+c/44nzzaneRM0ZmPcKx1q
VYuarEFpE3/Xa5bzK1aZP9fMqwvVHaycGt7i/nj1/fqMPek07xqNT2S/vovX0fBW/c3YoXRevI/9
K2Zv4uu5/5G19V6+eITG94rGFjnN27IHJ6RfgzxlUlHbh+TZOIQG0GCchzqe/VDqg/eNAUBfku+c
M2iCKdlX/W3SAfgY/GDqD8heg2gg3k0kpPZ8dScpwXhJ+JSrT6I62xvveIfKfP/qnJBcmtqd5YG4
ME5Bl5ltpU3TVIY2ztBJ5j2r2LzBy/1pnKSlqsWlVmA6nvXnhowq+WYl7wn/md1JSl7+ywxJeHpU
hpBrlaTOnjkqSoz7RGJA8r87Qrm6Axiyzv/KKP62pCbxGNCdsbjEOdfucOoP6xn5Tn1icVGxB1X6
6OLSkuJSu8dVXKSXFDgS9TS7x/4HQklSmT69uKBM1rj18UXo12/o0L598EhO1FMLCvRprrx8j1uf
5nQ7Sxc6c0cXF3mchVJJ6WLdbUcn1Lvm6rlOtyuvKEFPLXXZC3QHpOwuNBYWlzr1/LJCe5HL7dEd
+fZSu8ODDm6Py+HWPfn2Ih1ti/XiuboLo5SUOnOdDqfbXVzq1u1Fubod+ssc+brLVOUq0j1lRU69
3OXJR3cnaotzZW/JF9gxBvrbYYy/zlPuLPK4nJB2gCkrXZyoK5cUL3SW2jE9T6nT7ilEk+zgKMMU
3XIwd/FcmKlMmFtWUABW2YrhC4sxiKsot8ztUVN1exYXOBt6Qi6OW47iLC10FSmJ0uL5UGuH/Y4y
DFSkLMt12fOKZXt5vgszzHcWlMAjxXqea6FTCahVtusFcIde6ITvilwOiNtLSpxwY5HDiUEMd7uk
s3TnIkym0FmwWMfc3FjkAqmj0FWg3Osx48ZtjudAjxynXuZ25hredC4ok8aWOaT/9bnFmDI0YlIe
j6soT0691Il197gT5DK54TIVRygW2vPs17mKoNrpcSQYTkP3XJe7pMC+WA4hexc5y90l9hKYBpFc
mOhxuaViKV5SWlxYrLQl+mN1mDG1ac68sgJ76bCZ6CejNjlxSLLec6LLUVos16iXkpqYoch2PaMU
a19oL50vZ/x7kY+55CEInYg3FVMQnTFdn2L36HF6xkR98ty5icowZ4HbWZ4PscRJkzPGjxk/OjVj
/ORJ+uQx+pXjR6dPmp6up46dlp4+MX1SRqvgVsEZ+VgKv6flskjFmBxm7VGrELAHO684r9Rekr9Y
jSODX/opZ7G+uLhM9nTICIV1ZUW5KvoQEwgoFdeICReiGeL2vFKnU0Zvop6Fbvl2hE5xjtx66Olp
ZIz0VrkMQScW2ylXp9Tp8CA25sL39XbJZS/OcyoRFRaBflhORHxOmQeqYWYxdmGDCV3m9huF4A+4
ItBZRqi+0F5QZs9BVNrdiKqGvRP1GUUqzhf7Z4E5mYuDLWHX3SVOh2uuy3HxzHV4sUhFqOxrz811
yTVG5JSqxJUgq0uVb1VGaGJUgavQJSeEQZRceXHpfLcR2CqGVWVxOWKmLKfA5c6X40CX4e5CBDfs
x1KVLNaNgDc91Hgg5Y/xc+snJzPegjKnWw2DXOlwlhaZMyg17VbC7vzisoJcxOpCl7PcSHEXTV/K
YSWdyBq59WkxMEeYpZKxw1O/xnJidtPquZdWq0wOdDBzhakI49g9w6TAjOmpeh+955ABg3vpg/sN
6dN3QN++LVrMmIDKvv36DRiA5+D+g/XBgwYOHTi0VXC+x1MyLCmpvLw8sdC/8I7iwoZ7wqmnldrL
pS+wBWEUNE0rzsEOnYScVYwEnyA3aanL4bLr0+1qb7hxYg1J/he6k/I9hQVJhR75f9JLKnTPscs8
kSgr/80O5c4C1Dr/uIssJZl+VNK4DBWr12B5ASlSF128ArJWOMznofyVugr426ery6K8EslLS662
SdutPa0dBPZrB7RHGuiyq4uBv3xG6XY2GsvZSJvSJyJEPzFBjBVX4DkU0nb1iphrXkfymZdt0Uhd
8eSXMKXqeiZ1EP0PRC0LsQplbmRzdHJlYW0KZW5kb2JqCjEzIDAgb2JqCjw8L0ZpbHRlciAvRmxh
dGVEZWNvZGUKL0xlbmd0aCAyMjcKPj4gc3RyZWFtCnicXZDBasMwDIbvfgod20NxE9rDIARGRiGH
raPZHsCxldSw2EZxDnn7yW7oYAIb5P//xG/Jpn1rnY0gP8nrDiMM1hnC2S+kEXocrRNFCcbquHX5
1pMKQjLcrXPEqXWDF1UFIG+szpFW2L0a3+NeyCsZJOtG2H03HffdEsIPTugiHEVdg8GBJ72r8KEm
BJmxQ2tYt3E9MPPn+FoDQpn74pFGe4NzUBpJuRFFdeSqobpw1QKd+advVD/ouyJ2Fy8ndpfn5uHe
3hOX/vcMpRcizpOXkIOkCNbhc0/Bh0Sl8wtRVm9yCmVuZHN0cmVhbQplbmRvYmoKMTQgMCBvYmoK
PDwvVHlwZSAvRm9udAovRm9udERlc2NyaXB0b3IgMTggMCBSCi9CYXNlRm9udCAvQ2FtYnJpYS1J
dGFsaWMKL1N1YnR5cGUgL0NJREZvbnRUeXBlMgovQ0lEVG9HSURNYXAgL0lkZW50aXR5Ci9DSURT
eXN0ZW1JbmZvIDw8L1JlZ2lzdHJ5IChBZG9iZSkKL09yZGVyaW5nIChJZGVudGl0eSkKL1N1cHBs
ZW1lbnQgMAo+PgovVyBbMCBbNjU4LjIwMzFdIDY0IFs1MjMuOTI1OCA0NTcuMDMxMyAwIDAgMCAy
NzAuOTk2MV0gNzggWzQwNy4yMjY2IDM4MS44MzU5XV0KPj4KZW5kb2JqCjE4IDAgb2JqCjw8L1R5
cGUgL0ZvbnREZXNjcmlwdG9yCi9Gb250RmlsZTIgMTkgMCBSCi9Gb250TmFtZSAvQ2FtYnJpYS1J
dGFsaWMKL0ZsYWdzIDY4Ci9Bc2NlbnQgNzc4LjgwODYKL0Rlc2NlbnQgLTIyMi4xNjgKL1N0ZW1W
IDIzMC45NTcKL0NhcEhlaWdodCA2NjYuNTAzOQovSXRhbGljQW5nbGUgLTEzCi9Gb250QkJveCBb
LTI0NC4xNDA2IC0yMTguMjYxNyA5ODQuODYzMyA4OTEuMTEzM10KPj4KZW5kb2JqCjE5IDAgb2Jq
Cjw8L0xlbmd0aDEgMTEyNDAKL0ZpbHRlciAvRmxhdGVEZWNvZGUKL0xlbmd0aCA2MjQzCj4+IHN0
cmVhbQp4nO06aXgb1bVnFkmWJUuyLNmyZTsjj+04liLJUeItjqN4ix2TYDsOkbIh2ZKX4C227GCW
EBqyoAQKtCFheYVCIRQIHbPVSSmEpZS2hG6UAi0fKY++9vUjbaBASwPWO/fO2HHcvNLX1/frVfK5
c+45557tnntmxjYwAKCDncCBd2g4OnTsBw/8J0AaErmxgXB/9LoX3/4AQMwGSHq5P3z5EPdLdgEA
Y0MBoW+wMwz8+scBbIdRvqenP3b5in1Lf4/8cpxHenqi4ZT7+X9H2Q8R8nEa+c3Y3nmIP4VQ2t03
3jVS+GweAKoHTXbXUHf/+B8eHAVQvwCgr+wciwmL321xA6RfDsAKnf3hoVe//7oEwN+J80IgvqsA
vmXrKrzUWPUR6JKAfI79x+Fl5PrS1V+7dko/tULzK40DWNAiMFQAR/XSqQomnART+s9e1PwKYpCZ
OATnPm9QyTfgUuAhiDZYMIEHQmh1D7Mcc8Wo6uBpqup5GfgnEvfy34FivhWuVrnwegChDOERnG+A
YvYmhGgil/8p0jxQrL4EilRboIj/BK7ityGNXI9BMfcmcPwhOK4ywlP87fC0xgUn+E2Jp/kO+Daf
mXif2rkAqI8mbqe2F4GX2p4F1PYsmLH7V5B4m9idDcQu1Xkl6loC7bwTVnPbYT1fAu3cA9DGrp/6
I+9OfJGvhtWsE9azjqlPuL8gnger1RGUa0QwwFq+LPFn3gXruBpYzxkSCfZ52IG83dwj0Kj6CVzE
HU78nHskwXO3JT6hdi4AqofBjra9xO5soHbnwIzdv4LEz/h96DPang3UNgJvhlbemXhP1QA+tpjh
EQoRdAjNbDF8CeFNhGGEZxAeR/gE4QmEd1DGwxYnrmUOJ25izYkTrBlWMIeBZ2+ALrYa/apO/AHj
n+BqEseYJ+DXCMfZP8CvEY7jmqPsDxPfYFuhAyGFOwEdCCnc8cQ4uwfcPMAlWN2XcAfgEeb3cBf7
CVzOfpIIs09CDvtkIsIBbOEg0cO1wVHuZOJV/kZ4hq+ksIqs544zJvZPiUHmFJPN5TDZGiscVb8C
ewjwA3CE+y2kczuhl2cw/z+AMOeEHZwf9+hD2IY6rkQY5CsTH+E1DcGHUIdwM8KLCA0I+7kiOIvw
GcI9CJMI34O3pvTqt+ApjQGewut2hOMouxvBgbAd4XqEIMJ1CF6EBzgGfsH3JD6iJ5WjJ1GPWcwi
PQe/mArYAQnGxJSwL7Jvsr8ULEKWkCvkCZVCnTAkxBIJKnn3LIk0wSZko0TFLAlIpCdKP/vmZw9+
du+p68n81FWnNp/ac2rdqXVoU4BfzuoHwNzI3DJ7jn4dgG/AcXgcXoHL4RG4G74K98MPYS/shzjc
Dt/CHvdt7BHPwAl4Fp6D5+EFuB72wavwU/gZ3AgSxqECNWggCTtTMvZgPaSAAYzYaVLBjC3YAlZI
hwywQSZkgR2bZA7cAw/DvfB1OArjsAyqYTn4YQXUQC3UQT00wEpohCZYBc1wEayGNXAxtEArtMFa
aId1cAl8De6A++BB9P4GeAKehMfgm/AQHIFrYQIm4TC8ht4/Crvg5/Aj+C68BFfC6/AA3AV74EU4
BrfBD+BlOAlfhFyYhxlyQB6IkA8FMB+KYAEUgxNcsBDcsBS7pRdKYBH4YDH8GJZAKZRBOVRAJVTB
IKyHAPbVDbARNsFm2IJ9NgRh6IBOiEAUumAMeqAXtsJl0Af98BMYgCHYBsMwgp16O4zCTXAzfBlu
gS/BQQB/4NItmzdt3BAMrGtvW31R86qmxpUNdbU1K/zLq5dVLa2sKC8rXbLYt6jE63EvdDmLFxTN
LyzIF/McwrzcnGx7VqYtI91qSTOnmoyGFL0uWZukUat4jmXAxdgkW22gfquUWRuS9GKdaBIk/Zoz
qz0SmO0OMVXweYILFSlJ5ZQgrVmytAQmwF8elNTOuSJrJK7A9IEDF6+2C/USX4A/4qpwRCpqCzhE
02v2GX4Q10hZtQGHwy6xBfjThCz8WRUWIpKpBekOu0xpkqAlQGAy8U45EqHcEcSxLSDlTk+DwQs5
eQxPwIk5bq5h4qYJfWZtnQSWCdC/I4GViJ0px3qtkoqc6IgJMaoNPBJj+UBi0iTGuhpdPt8EWXaq
/AI5qI9sFesjvZjRSOhcTs/IGXUIcSHeFkj1IUqdbpZeag1M6JJrxdpoMhKAEmAiWYcUHSGgiqEJ
Rl/NUITV11dOsJCUgukzE3frCWyV/PtDiIh1mDfkpJ3jTCZOHJjNAlw2jaXJmOyEpK6VNLITQq/k
D0uwX5hwnYgfmDRBR8ipj4iR8KaAxIVRYAK4gvqedim7uWUDktAUQqhHINtdRweyeUJ9jxDHOZEN
4SjWkU0/jx7piYZImTAhsQ552trAXscJu2TGa72U6pRSUCzlinftXLze1iuQaTy+V5DuRndncR1k
xCKwoevxehGtobL6rTVkSzwz20arsSlCN8e/PyxIOzu2yrUXPjBd/464SdJ/7MDdwf3BlXShkspI
aCtxeWuYhFm/VYjvj9JQD9DQsF6F+q11BMhCrH5Yh6s3BOp7xPpzBjFwRLiCuWsdDinTSRbG4/XE
xXAEvZddRsY5/8mZsDsZ9KdW8rfTC7TTPUCL/nBdUCEpAhvIMsIJ1QWDDnnfUVTSFOxVuUUhTjRq
CiSL0+R4AXknFrqa2wL1dXYavcTWBpadttlPI97cMkNmbCgT95y2yzlqXis2t8pV0DM9hNrlA8zO
7DyKKvJU60mb/aSMbwo0iA2heLxBFBrioXh4MrGzQxRMYnxCr48P1YcEevwZpB/fb5caDgQlU6iH
qaQ7RNQJpPYa2pqltNaNZKsahJ6w3DiWi45yuyN1Rqblv2MrZw6rH88AOXNx03vomx67k11oIK1m
EjuEXTKVkyOLDq0L4JnopPVLBzwra1G5nZwaLlhQ37tWSRZWplI8pAe2KlRU4nCQ87R/0g8dOJF2
tgbkuQAd9kfB73HiPoYI58Q0x7qOcHZOc2aWh0TcN1vz2s+p79m1HU8VzUKFh+aftt6IdKIdY/xz
uZRUrmx9Wm2As7MKxto5giU7sZVVSRlOupDkBDtm3CQKPxIlk1NS1QZO2KuCgikVWx2DMo1OcoKw
o/5I/B5D+ihYTBJTJTHphA7YV2l75zLKkTlTSEJ9PKRU2uywlJtBpOfCsaGMScTw7LJ8qlkkEb5M
25vStQsayLmyO2SJVUHJQHqzZHiPDuivvTYgYCfCk9tKEaFe6CGbLQmhOtoSgvbZ5MnEqVAdaYHo
MhGxKyWOo5za82ttoevvLfSdWOjXHgj2VKIWfzFGICxBs/S0tAeULJXblRNFbDWRUM7nz2RxWgY3
Hw+eQ/Jmfc+GhZplOx28UMqb28+bzTJGeeUznaE9IDU4p5XL85VO++xp4xx20zQb28fV9ivIbYSF
mgmR2dc64Wf2rd0QOGbC59p97YFHWYatDdUEJ/KRFzgm4CMQpbKESohkIpAJNDOo7VE2icrbj/kB
dlIuTwl03jnJAKUlTdMY6JxkZZppmsYijZdpfkqTnyrqbT2YgoCImx6R/C2Bq4I98VCQJBvS5QLE
yharQWLF6gmGVeulZDFaI+nEGkJfTujLZbqa0DViDZY/Hg6BHPV4SMTjjw04AHYmSEqYlAtbIEwm
EthBT2LndUjqgk0I2GC1zqCAVbwK5VYSCCF5pbSzM0z8IGXKkV7e1BmUkmYUokiTpEUNWkUDSjTQ
NeQugIs6sVjDIkWRjIdjZ1AKOonRQC9RIAj4PNQoVkrqQlmnqpAY8gTjZnERvZ2oC6Tkgr3kokXf
SCOkFDtO0VhQTpJGj553isjqDAmYbR4612Ix8oXkJ9kuU6J4V+cLoxSS7QoT5BOkS0mWtG5yr9JQ
XOdGhfijCQZl5+lsryKAtk2SDj0qnJVKZQFmB1lNxBf82YuuEtFniZrWSWgTL8czSJymmjTIllIK
msLYcOT1OqSI5dOLUVcSJREdL8hUDYlcTx9o2ycTR8Rxx6zPQpeId+cAKUyw4zOkH4LxuQRpIzbO
pLnUFEqOx5NSLrxAzldSyswVichtfftUekb2qz/D4cqr0u1XXpX5458gPrYdh/4hHPoGcbhsIN1+
2cA1w1mxUYs1u3srDl29OER7LPZoz+5tWZkj6VfUZjrGEbDxP3ZHrqMCr/70OwWxQnhNb6h4/WlG
kHQpFf7vuEqQdeKxx9LSqEjeGXtOxdmbWWfdn/fdvO/9wzcffl81+T6j7bR1freTEzpTjETssZXz
Cqj4gsN5BRVlX2FuPcg6bYcWFFdkHGJMB5f7K944yJz+Hev0/86SUeF/yWIhRvybJtDK9btVzp3X
sM5rr2GcO65ROT/dxTr37Oacr1/DXLO7YN6+3YxzL8J1KLYLIWm3tgxq/SVaU4W9zGortVqXWM2L
rUafVb/Iqi2xqr1WzmMFt3WFk9EwSWBkVIwaDAzH8IgzDItvscsZBoFDUIEfr4SjwrdoDZgQBMQF
vHqR40Xci7gf4W1clcyk+Ptqqx2F8w1F843GYm8RW+w0uJzGPNGQLxpz5xmEeUZQmVSs0ZSq1ybr
9GpNkp7jVXpgWL2ai8zLhaJ5OmOzkdXha2gdF+Megl8Y1TrQcTrjUliqDXIbtWPcHXCH9jbjG6A/
xhgYo99stDM5KTZNVorVlJFi5i0p8DRjAA9DYjHAFxmDv5B3VRVXFVUVVuVX5VUJVblV9ipblbXK
XGWs0lapq7gqqGrxtTOSuRma22ukNAava2skn7N5khPapEXOZknbsjEwwTA3BpEqsfuw87ZL/D5s
tu34TL9hY2CSySTs3Vi4mAupObT7hqDTmSNFyJ1+Z05QWkSQm3KC+Ey2qFWyizXOuZ8ReYyNnjd3
jkjF9ZKrPiwV1YekQrGOysxZysiXWWSIkRkhxBRpWZ1kk5ZjbHNtT2hJkC1tNeTBtVmK4GNnbsvG
kJQl1uAzJM5KWzbi40gNgOoGSMZxHZjAqdoEWgA+A/HpX648JeOJM4l/I6OMA0y1kVF1K6gQOzst
rb4aTNyyxBn2FJgSdyc+hFRKriLD1NXn/dYGpkansSQFyK+ToAbuh5uByG6GIbgYr+sQXPB5n+c+
V+JCn2/DMXyfJp8JeAjug69Q/Chqe3yWVFC5XgztcDlsgLvRpy7yO2jYBk0zUiGUK8EvICTPUJ+G
38LX8bz9jvnVBezvpZafg7vgIohCteoD1QfwZfTkLmiGXZiHc59X6Pg6G4Zuiu2Yo6kbVuPYiB6R
fF2HXkpwE+rcC6NwK873wjBm9S04AX3wJbgD/X8G7oFr4Ra4Q/0k3bU/qiYgha3E3UzCXRiDmqnX
p56Tdxz95/9/AzuEZ+GF84F//PNB9RL5e8q/4F/wucCTv2Pxe1TtUIT9zguLIexPs1gMeWq1AVxO
p9dgs3kX+z14j/LbveAz+Vhfjq4IoNiZZllkceo438KFpV6f56S5wmPOqDjpwW8FGcCz+WTWW1mE
fjK1wvPWK6kVqT6clHiZJYur2bJqbsniQjHPwGrEJaWlvkW5rNWCEwNntWZYxSVMqiOVAFumTi/O
zyi0G1dUC978TG2o6vrahs7qbGN+lUsotGrMNzGffqbmwp+WM79JTy8oXjI/0+OrEJvbLPmLcr+Q
687xNSworF7WsNDhml+UrR746len3uVvP9vF/+kvD2PY+MHbb+J9vhHvK/n4yPAtfB+pXRfwVy4t
yLda0gCSdVxa2rKSXX58wNdz9mQmSXOkLgnyix3FXPFBv8NktSy2LeYWH/Lb0s2pR+rMVrAtdyJk
rT7tTAWfbwaTyV7Gc+mWzUjCZGT49p4gnxK7X/zfKw4ypaWY1ML5ZWU+Rq22WtIzNI6y+Wq1mFeI
Oed8i9IzuFI57TxyfYtKS8vwh+tK0qcvWKI/u3TqM0Oye4V26p3lKaGHQwPjruBV94aWdZc2GmtW
F1+0ZmWlUFE7r7ZtsafMzF/laMnF5zFusfbszuXV1gUFqpKz/IEv3H9r6Nmj163JnDf1cqN/zUr7
8q5bjlzc053d3FS7K4i5xns49wXuJGRDMbym5LoaizE9dXd+viv9Or/WksPl3Oo3WuZZ2BwOa5E3
zOfmH/QbTOAXChpBgOwz2ayOy+b5TC7zkJ9PV1ICNtOrJLOZJ51KZsxQYVOS7fQyNo+c9NNYjj7M
eMn/kaFggYEV89wsKXNMudXCO9RytssKqlU0/Wo15161b1/bxcPN+avvfPPK8fGpZ6de1Ldt3nRr
21Txpv2RmvnGivKGvd3fbd1S5Ate2XjZR89f1tHz4INVDb2Xtqz9lElzuMuWOZbVRx8i9bseB6+q
Djiwwa1KTr02vIXwBjaFA47nUthO/xDHGLm3OdbIXcqxWo6zPZiebj1Sl27U647U6aeLi0S3+tck
mG2bs05jsdIaNe2lRZr3j6oJMhqxjKM1SYoy7Vyhsl73hLtBp7YUe7VT3z+UkpxaVKL7cKmq7rnn
zj7p85hy88yqEvaeyvqMHMHELtGSvwpivNwO7mWsoceVaDOT7/NrtUlJFjObxuA3g7PAg9kmLiVl
MvFbf7YloxG0Ji1r4bTqneoULsWvNmXbj9RlGy3EYflUnXRCls10El12pvp86D0NnkSeyvg8Pk/W
6RL7k/8ErUHGp8kgLS9DIxbKLZAT05SEMDdWNegvfSLUVOLtTsrLn9+1dYlh49HDVnORV8d952N+
1w7dqcWlLQfGGqcuZh/aUpI9z8gtwZwkEniuzJgTF/xQycmKjPtwZ6wFcJ8LO7lhT06OW7OnwKHT
ZXHgCrmGXDtdvJ5zLfAv4DjuoH+ByZg+L501c+lmcxaXddBvnlXvL6D/Mq4Ek2rGdo4Jkk/UIkzP
6VSSJMyR3/VPtRFkCumJoaWDAVloP5tf5ksnR4pmjZw1OaHsl3Wt6zwXuXJX+sNrNtzZEbit0bNG
s3F9MJLrX7p8jbPtUPS+HW72pxtaxdqFBctqnCuuaNmyy59leX3TxmCTs666yHnRxrK1V/id5NnX
Ah/P/M+IiY7y/UKHMxnnEbMruAq/TgVXI92r4CnMGPgV3ABu5knyV20eCxkizLsKjly2UcFZ0M/g
HFSz7QrOQzZ7i4KrwMU+ouBqpL+p4Br4C/uxgmtB4M4ouA4u4U0KrocivkvBU9j3+BsV3ACbNFdc
3L5WiESHe8eiEaFrcCC2bmBkKNrZ29Ubjcxllbi9Xi8SFyrEhYTY3tM7QrlCT3hE6IhGB4S+3s7o
wAguig0KKwcHu/uiQtNAp1sID0QEFI71RIWxcN9ouAMZQ8ODQ9Hh2Lgw2CWsHhwYjI0PoXR/uLt3
oJss8AwOC72xEWFkdGiorzc6POIWgoOjw8LoSJQsiRHr26MdsgeIdw6ORYfR9OgAOklNxaLD/SNE
dpysU/xZGx0eQy9HhHD3cDTaHx2IUb1Cf3hcQCcEVNE7Ehvu7RiNRV2odGicjAOoO+YS+gcjvV3o
8TCKIQU9iQ6gv1FqUMmGW2jpi4aRhati4c7YueC6cF14YFzYNhodifUODoyglu7wcIQEvB4jacAF
I5VCTyw2VOnxbN++3U30jbg7B/s9GClN+sgFub0DXYOePlTW54mO9oXPSeO7oQCLsD69sASx1dAL
nfimNggjCF0QQ1otYsP4LkzGMFJ6ERsAN3JW4LtcH17bkNYNPcgbobMoXqMoPYZjBCWbkBNGSaL7
ry1UUhth6IcOpPciJpy3onKWh39L7hJqc0TxT0BpN10l4NvkKFL70BcB3429UDZHz8Lz9My10Uuj
iuI1hjESGwKlDyPeTbkxSo1S/TGaJfK/C/14HYbLkDY4s+bC3K7/UeaJRwNUF/FGwPftAeqbbH8t
jSRG94DYHECqR/FgcFYEnTgbRW6Mxkmk3egD0U+kxtFqlOaX+NlNLco7HENOJWr0wHb6daPEXM/d
VHs/ysiaBnEtiWAINYwjtRPpXdQWqZgLaz3Hn9bWTv8ThEQ1zROQEqaUDvQ2SrMi7yHBR2Z2ZBDH
lTgSP/qUuAZQyj2Toeldns7pGK2GUfqfKPKKIRrhEM0eiercvv3tnM3dg17llIyg9iH89tHsD9M4
BQjSXSFyo9T/aSuxmdi3I7XjvBzIdJKjsVl1OEqtyns9HZVcp/1UXtY7PmPv/PysVc6vnEu5krqp
blK5UWr5nL8CjZjkRM6EoHghnw1SXx0oRay7FE+HUHoaH1D8jlFKP1LIyi4lx8OKtjElS1F6FgeU
/EZnRXh+bRDvWmg0YWVVp8IJ0/q70M51zZzUAWp9G3odpTHIJ29k5tSTsxuZ2eH1yp40zNRsJa3N
v6+uPcqeLvwHzoSH+kDoHhprN61bD2KjeA1fSPd/AUVk2EsKZW5kc3RyZWFtCmVuZG9iagoxNSAw
IG9iago8PC9GaWx0ZXIgL0ZsYXRlRGVjb2RlCi9MZW5ndGggMjUyCj4+IHN0cmVhbQp4nF2Qz2rE
IBDG7z7FHHcPiyakLYUgLNsu5NA/NO0DGJ2kwkbFmEPevmrSFCqozMzvG/2GXpqnxugA9N1b2WKA
XhvlcbKzlwgdDtqQogSlZdiifMpROEKjuF2mgGNjekvqGoB+xOoU/AKHs7IdHgl98wq9NgMcvi5t
jNvZuRuOaAIwwjko7GOnF+FexYhAs+zUqFjXYTlFzR/xuTiEMsfF+htpFU5OSPTCDEhqFheH+hoX
J2jUv/qm6nr5LXyiq7tIM3b/mOktX/5Se9OKZawqVrriOfm8Jq/5eii3FqsovZ1mtBuTs/fRUx5k
NpNsaIP7rJ11SZX2D4rLgNcKZW5kc3RyZWFtCmVuZG9iagp4cmVmCjAgMzQKMDAwMDAwMDAwMCA2
NTUzNSBmIAowMDAwMDUxNjQwIDAwMDAwIG4gCjAwMDAwNTA3NjIgMDAwMDAgbiAKMDAwMDExNDA0
OSAwMDAwMCBuIAowMDAwMDUxNzIyIDAwMDAwIG4gCjAwMDAwNTA5ODEgMDAwMDAgbiAKMDAwMDEx
NDE4MiAwMDAwMCBuIAowMDAwMDY5NDE5IDAwMDAwIG4gCjAwMDAwNTEyMTAgMDAwMDAgbiAKMDAw
MDA4NjEwMSAwMDAwMCBuIAowMDAwMDUxNDI5IDAwMDAwIG4gCjAwMDAxMDM5ODIgMDAwMDAgbiAK
MDAwMDExNDMyMiAwMDAwMCBuIAowMDAwMTI2NTE3IDAwMDAwIG4gCjAwMDAxMjY4MTYgMDAwMDAg
biAKMDAwMDEzMzY2MSAwMDAwMCBuIAowMDAwMTE0NTQ0IDAwMDAwIG4gCjAwMDAxMTQ3NzAgMDAw
MDAgbiAKMDAwMDEyNzA5NiAwMDAwMCBuIAowMDAwMTI3MzMwIDAwMDAwIG4gCjAwMDAwMDAwMTUg
MDAwMDAgbiAKMDAwMDAwMDA2NCAwMDAwMCBuIAowMDAwMDIwNDE0IDAwMDAwIG4gCjAwMDAwMjA1
MDkgMDAwMDAgbiAKMDAwMDAyMDY1MiAwMDAwMCBuIAowMDAwMDAwMjc1IDAwMDAwIG4gCjAwMDAw
MjA3ODYgMDAwMDAgbiAKMDAwMDAzMjI3MSAwMDAwMCBuIAowMDAwMDMyNjUwIDAwMDAwIG4gCjAw
MDAwNTAzNTggMDAwMDAgbiAKMDAwMDAyMTMzOSAwMDAwMCBuIAowMDAwMDIxNTY3IDAwMDAwIG4g
CjAwMDAwMzM0MTYgMDAwMDAgbiAKMDAwMDAzMzY0MCAwMDAwMCBuIAp0cmFpbGVyCjw8L1NpemUg
MzQKL1Jvb3QgMjAgMCBSCj4+CnN0YXJ0eHJlZgoxMzM5ODUKJSVFT0Y=
--047d7b3439e487e20e04f7035b34--


From nobody Mon Apr 14 09:48:47 2014
Return-Path: <tjw.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B4F71A01F4 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:48:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 OnDlCbYOE3Mm for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:48:41 -0700 (PDT)
Received: from mail-qa0-x235.google.com (mail-qa0-x235.google.com [IPv6:2607:f8b0:400d:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id 1DFCA1A01E7 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:48:41 -0700 (PDT)
Received: by mail-qa0-f53.google.com with SMTP id w8so8253163qac.12 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:48:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=pYMkB1eAr75LqDszU4cfSrtdFVAFG8CjHoW47Tg83I8=; b=JADBnu33h44PsOLxhu0VL+x4hgo5djagW+Mgy0QvhlUheGShDLa083U9HgZmxPnntz 7wTPK5FOyY7QevxD0vFukznTr3rWb0OBd0QPmCA0BILFs+pLOD9Td55NeIc4VtfAJ2Bn fHtOWQ0jpNpNqrhPolkaUkTubdv9+/+LOmC2MDyXIYaTaycaxSesas37bAud1tIOy/Yf DueUGW3SPB9RIeUmmZnZZV3zMyQPuFxHEQAgfJMmW8JvStwOAQWsKvcJXAM0CT1JthPh /ogQhgl80sOEtnV6C82WuH0JtT9zMLxhbnDUsth0ZRkmJhISMrwk1uZwV0mTQQCGdhbJ q7sw==
X-Received: by 10.140.28.70 with SMTP id 64mr49873007qgy.36.1397494118414; Mon, 14 Apr 2014 09:48:38 -0700 (PDT)
Received: from still.local (184-19-89-148.drr03.clbg.wv.frontiernet.net. [184.19.89.148]) by mx.google.com with ESMTPSA id k9sm32249483qat.18.2014.04.14.09.48.37 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 Apr 2014 09:48:37 -0700 (PDT)
Message-ID: <534C1164.5060300@gmail.com>
Date: Mon, 14 Apr 2014 12:48:36 -0400
From: Tim Wicinski <tjw.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:28.0) Gecko/20100101 Thunderbird/28.0
MIME-Version: 1.0
To: Abdussalam Baryun <abdussalambaryun@gmail.com>,  "George, Wes" <wesley.george@twcable.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <CADnDZ88i9tzST7d8QraJ4HMuCVqr2NPBvDej3p0SRwuS0zQbQw@mail.gmail.com>
In-Reply-To: <CADnDZ88i9tzST7d8QraJ4HMuCVqr2NPBvDej3p0SRwuS0zQbQw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ozrgf8BlD0t8QQJsyJ4OlkItxnI
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:48:46 -0000

AB

One thing I've stumbled across as WG Chair and Attempting to shepherd 
documents through the process is if you're not vigilant, that some 
comments or questions get lost in the process.

I like where httpbis WG has gone in using github for tracking issues 
raised during the document process. I think it has two useful cases: 1) 
when working with other groups outside IETF, it presents a nice 'neutral 
spot' for collaboration, and 2) their issue tracker is more lightweight 
and robust than the existing tools.

I think Ted's comment is right - we innovate when some group tries 
something to see if makes them more productive.

tim

On 4/14/14, 12:17 PM, Abdussalam Baryun wrote:
> I was thinking of why many quit reviewing adopted IETF drafts (or
> even quit participating). In my situation there is a draft adopted in
> 6Lo WG and still the author does not answer my question reminder, and
> it may make me quit reviewing as well. I think IETF does not have
> problem of participants quit to write but participants quit to review
> and contribute more into drafts.
>
> AB
>
> On Monday, April 14, 2014, George, Wes wrote:
>
>     Iâ€™m surprised that no one has sent this out yet:
>     http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>
>     "Summary: After contributing to standards organizations for more
>     than seven years, engineer Vidya Narayanan decided it was time to
>     move on. Although she still believes that these organizations make
>     the Internet a better place, she wonders about the pace of change
>     versus the pace of organizations."
>
>     My thoughts-
>
>     There are some nuggets of truth in what she says in this article,
>     and in some of the comments. I think that the problems are real, so
>     thereâ€™s value in taking the criticism constructively, despite the
>     fact that the author chose to focus on the problems without any
>     suggestions of solutions.
>
>         "while the pace at which standards are written hasnâ€™t changed in
>         many years, the pace at which the real world adopts software has
>         become orders of magnitude faster."
>         â€¦
>         "Running code and rough consensus, the motto of the IETF, used
>         to be realizable at some point. â€¦ In the name of consensus, we
>         debate frivolous details forever. In the name of patents, we
>         never finish.â€�
>         â€¦
>         "Unless these standards organizations make radical shifts
>         towards practicality, their relevance will soon be questionable.â€�
>
>     I donâ€™t have too many big ideas how to fix these problems, but Iâ€™ll
>     at least take a crack at it in order to spur discussion. My
>     paraphrase of the problem and some discussion follows.
>
>     - Weâ€™ve lost sight of consensus and are too often derailed by a
>     vocal minority of those willing to endlessly debate a point.
>
>     Part of the solution to that is reiterating what consensus is and is
>     not, such as draft-resnick-on-consensus so that we donâ€™t confuse a
>     need for consensus with a need for unanimity. Part of the solution
>     is IETF leadership helping to identify when we have rough consensus
>     encumbered by a debate that will never resolve itself, without
>     quieting actual disagreement that needs continued discussion in
>     order to find a compromise. I donâ€™t have good suggestions on how to
>     make that second half better.
>
>     - We donâ€™t have nearly enough focus on running code as the thing
>     that helps to ensure that weâ€™re using our limited cycles on getting
>     the right things out expediently, and either getting the design
>     right the first time, or failing quickly and iterating to improve
>
>     The solution here may be that we need to be much more aggressive at
>     expecting any standards track documents to have running code much
>     earlier in the process. The other part of that is to renew our focus
>     on actual interop standards work, probably by charter or in-group
>     feedback, shift focus away from BCP and info documents. Perhaps when
>     considering whether to proceed with a given document, we need test
>     as to whether itâ€™s actively helpful/needed and ensure that we know
>     what audience would be looking at it, rather than simply ensuring
>     that it is â€œnot harmfulâ€� and mostly within the WGâ€™s chartered focus.
>
>     Thanks,____
>
>     __ __
>
>     Wes George____
>
>
>     Anything below this line has been added by my companyâ€™s mail server,
>     I have no control over it.
>
>     -----------
>
>
>     ------------------------------------------------------------------------
>     This E-mail and any of its attachments may contain Time Warner Cable
>     proprietary information, which is privileged, confidential, or
>     subject to copyright belonging to Time Warner Cable. This E-mail is
>     intended solely for the use of the individual or entity to which it
>     is addressed. If you are not the intended recipient of this E-mail,
>     you are hereby notified that any dissemination, distribution,
>     copying, or action taken in relation to the contents of and
>     attachments to this E-mail is strictly prohibited and may be
>     unlawful. If you have received this E-mail in error, please notify
>     the sender immediately and permanently delete the original and any
>     copy of this E-mail and any printout.
>


From nobody Mon Apr 14 09:53:13 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32C481A01FA for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:53:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.399
X-Spam-Level: *
X-Spam-Status: No, score=1.399 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 oSQ5xdbWrPWo for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:53:08 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.31]) by ietfa.amsl.com (Postfix) with ESMTP id 4497B1A0643 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:53:08 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES533.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Mon, 14 Apr 2014 12:53:05 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: DMARC: perspectives from a listadmin of large open-source lists
Thread-Topic: DMARC: perspectives from a listadmin of large open-source lists
Thread-Index: AQHPV1b69xJg0SLv5E6irQO+Rle3hpsQTfIAgABQugCAAA4jAIAABomAgAAEWACAAARMgIAAB1CAgAAGw4CAADueAIAAdaKA//++oSA=
Date: Mon, 14 Apr 2014 16:53:05 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net>
In-Reply-To: <534BFA0D.7000404@meetinghouse.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nxf5eIo4IJ8tg7LHnTh0kPVAue8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:53:12 -0000

First an introduction, I've been active in IETF email and email authenticat=
ion working groups (As well as in other forums) for quite a number of years=
 but have not been active in IETF from an organizational perspective. I was=
 recently given a heads up about the discussion on the IETF list and joined=
 as well as reviewed the archives related to this discussion. I recognize a=
 number of participants here from other arenas although the majority of par=
ticipants are not familiar to me. Full disclosure:

1)  I represent my organization as a member of DMARC.ORG but I do not speak=
 on behalf of DMARC.ORG;
2) My comments here unless otherwise specifically stated represent my own o=
pinions and are not a statement representing my employer.
3) While I currently moderate various mail lists, I do not administer them =
from a technical perspective, although I have in the past.

I'd like to also provide to a blog post of mine on CircleID from 2009 - htt=
p://www.circleid.com/posts/20090414_thoughts_on_future_of_email_authenticat=
ion/ as well as a response from Dave Crocker - http://www.circleid.com/post=
s/20090422_thoughts_on_email_authentication_trust/. I believe these are as =
relevant to the discussion today as they were back then (pre-DMARC). There =
are not simple issues involved despite some of the pronouncements I've seen=
 and there are not likely to be simple solutions other than local policy on=
es that work locally.

Additional Comments in-line.

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Miles Fidelman
> Sent: Monday, April 14, 2014 11:09 AM
> To: ietf@ietf.org
> Subject: Re: DMARC: perspectives from a listadmin of large open-source li=
sts
>=20
> Doug Barton wrote:
>=20
> <snip>
> >
> >
> > But your point is well taken ... the "right" answer may be to fix or
> > discard DMARC, I honestly don't know. But in a world where DMARC is
> > here to stay, or if not DMARC then some other anti-spam solution that
> > breaks mailing list forwarding; and in that same world where mailing
> > list traffic is negligible (and therefore the cost of breaking mailing
> > lists is in the noise compared to the benefits of deploying said
> > anti-spam solution) it's incumbent on the mailing list software folks
> > to solve this problem
>=20

DMARC has been shown to work extremely well for specific implementations in=
 terms of mitigating direct domain abuse. The DMARC specification was deriv=
ed from private-channel arrangements between some senders and mailbox provi=
ders that started developing in roughly the 2007 timeframe. The impetus for=
 DMARC (and predecessor efforts) was to leverage what was essentially a set=
 of private relationships that were working to create an open standard that=
 would be available for anyone to implement, regardless of size. Mail Lists=
 were identified as a potential issue but the initial set of sending domain=
s did not involve domains with end users and in all of the efforts, this wa=
s considered an edge case.

My own analysis - for internal consumption within my organization - which d=
ates back to 2004 following the FTC email authentication workshop, the FTC =
anti-spam workshop and the DKIM "organizational" dinner that followed, was =
that if email authentication gained any sort of traction in the wild there =
would be increasing pressure on domains such as ours (greeting cards/social=
 expressions) and Mail Lists, which did not conform to whatever email authe=
ntication standards evolved. If we were going to change our practices, I pr=
eferred to do so in a planned manner rather than as a result of a change fo=
rced by someone else's decision that would force us to react in a short tim=
eframe and under the gun.

This was one of the reasons that we changed our organizational practices fr=
om spoofing (yes, I know that Dave Crocker objects to this term but until w=
e have a better one that gains a consensus I will continue to use it) to se=
nding mail using our own website domains as of the end of 2007/beginning of=
 2008 depending on the website domain.

> Is it perhaps also incumbent on the folks promulgating DMARC (and its
> predecessors, and its sure-to-be successors) to work cooperatively with
> mailing list developers, rather than taking the position "nope, we break
> mailing lists, not our problem?"
>=20

The fact is that a vocal constituency led by John Levine made it extremely =
clear that MLMs were out of scope and there was zero interest on the part o=
f the MLM community in discussing ways in which MLMs could be made to work =
in an email authentication framework even if there were any MLM operators w=
illing to do so. His stated solution has been and continues to be that list=
 operators should drop any participants who post from a domain publishing p=
=3Dreject and to prevent any new participants from joining from a domain th=
at publishes p=3Dreject. The record is quite clear on this and is available=
 to anyone who wishes to peruse email archives, blog posts, etc. I view thi=
s as local policy and up to the list operator. I'm not confident how well t=
his will ultimately work for many organizations the operators manage lists =
for. Just to be clear, the preceding is more of a question than an assertio=
n.

This was also a point of contention within the DKIM working group with rega=
rd to ADSP and if memory serves me correctly it even came up earlier in the=
 MARID working group as part of the discussion surrounding SenderID and the=
 use of the "Sender" field. I don't intend my statements to lay blame or be=
 pejorative. It is what it is. The folks pursuing email authentication stan=
dards and practices publicly noted the potential issues and focused on othe=
r areas. It was NOT a position of "nope, we break mailing lists, not our pr=
oblem?", it was a position of not getting into a painful fight over somethi=
ng that many viewed as an edge case while continuing to pursue the stated e=
mail authentication goals. I was personally willing to kick the can down th=
e road and respect the MLM operator position as expressed by John and other=
s.

I also note a comment in another IETF thread:  Re: "why I quit writing inte=
rnet standards". The comment is: "For instance, had DMARC proponents and/or=
 Yahoo, spent some time making sure that there was some running code for ma=
iling list use, life would be better." My response is that if the MLM commu=
nity, as led by John Levine, had expressed an interest (rather than a stone=
 wall effort) in finding ways of making MLMs compatible then there just mig=
ht have been running code available at an earlier point and yes, life would=
 currently be better. If the position that John has taken and publicly advo=
cated does not represent the MLM developer and operator community position =
then I'd appreciate folks speaking up because that is the only position whi=
ch has been communicated - and very stridently. Again, I am NOT advocating =
that MLM developers and operators must change. I am simply stating that no =
rational person pursuing email authentication standards and practices devel=
opment would willingly walk into this buzzsaw absent an expression of inter=
est on the part of MLM developers and operators.

> I'm kind of coming to the conclusion that what we need to be looking at i=
s
> defining an SMTP extension that addresses BOTH sets of concerns - and
> doing so in a cooperative manner that engages not just the community
> behind DKIM and DMARC, but also the developers and operators of
> mailman, sympa, majordomo, listserv - and ideally the sendmail, postfix,
> exim, qmail community.
>=20

I don't know whether it is possible to find a solution by modifying current=
 implementation practices or if there is a need for an SMTP extension. Fran=
ck Martin has posted in a few places a list of MLMs and how they can work (=
depending on version, configuration, etc) in a DMARC/email authentication c=
ontext (I don't believe he has done so here). I have not looked into the sp=
ecifics of the MLM issue deep enough to make any meaningful comments as to =
what might be done, if anything. I'm also not interested in getting involve=
d in such an effort if there is a vocal constituency within IETF claiming t=
hat any such discussion or effort is an attempt to force MLM developers and=
 operators to change how MLMs function and operate. My personal ox isn't ge=
tting gored here and I'm not that much of a masochist that I would choose t=
o engage in such a process under those circumstances.

> Dare I suggest that this calls for an IETF working group?
>=20

Suggest away but the notion of such a group, unless well wrangled and with =
a well-defined charter, brings back memories of the MARID working group and=
 its outcome.

> Miles Fidelman
>=20

Mike


From nobody Mon Apr 14 09:56:26 2014
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09DAB1A0652 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:56:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.079
X-Spam-Level: 
X-Spam-Status: No, score=-0.079 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 DEU6HG1isKUu for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 09:56:20 -0700 (PDT)
Received: from mail-qc0-f172.google.com (mail-qc0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id BC11A1A03D7 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:56:19 -0700 (PDT)
Received: by mail-qc0-f172.google.com with SMTP id i8so9268865qcq.31 for <ietf@ietf.org>; Mon, 14 Apr 2014 09:56:17 -0700 (PDT)
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:content-type; bh=dTIrYNHv/X2ZsPfUR1HsaEisKB91yQPpZfB8bWFq+t4=; b=NupHwGp+ew6KvglnftyRXjtbpWb2bjTidbIhPtqKGucFUqArppU5MUHEXmckx3c+Ll lxxqjcvKyppY8V17RtZDPwnsBNUk4CS/GVdEClohl7ffHRECtEEJiP3ScgRKaWKe6T8v 8fVgoIpEoN36UN5jzsBo7cNr2iIixY3vgobVHZ5nEHD0LyGLsXMVAkOysz18K4M16XoP G5OUDdjz/rKOPOe/ZPclbAUxPW4EvMkQYBSPYQ+2bahK/PvXkroXAesh05pe7j+ecbga pEQbBBNXbdnO83EVirt+vc+cQRr09kdz1ji1lqKXLWCeQrgQw10RfyLm+uHxDYrd53D9 FH9w==
X-Gm-Message-State: ALoCoQkO3tTHYIDsfZP+B+W4XRT8fFGWfi2/RtRZxh4g3g9e4s0XKTdNC5J0zKAzAAGwXzMG9DD6
MIME-Version: 1.0
X-Received: by 10.229.96.199 with SMTP id i7mr6124578qcn.20.1397494577003; Mon, 14 Apr 2014 09:56:17 -0700 (PDT)
Received: by 10.140.41.134 with HTTP; Mon, 14 Apr 2014 09:56:16 -0700 (PDT)
In-Reply-To: <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com> <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com>
Date: Mon, 14 Apr 2014 09:56:16 -0700
Message-ID: <CABCOCHTRtoVmGffCuxKiNM1j0mRW1DLOR_db78=KBKTc7TA3Jg@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: Andy Bierman <andy@yumaworks.com>
To: Alia Atlas <akatlas@gmail.com>
Content-Type: multipart/alternative; boundary=001a1133886ed6943b04f7038f41
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4nQH7irzcVZFWt1uyhrusuynFC4
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 16:56:25 -0000

--001a1133886ed6943b04f7038f41
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Apr 14, 2014 at 9:07 AM, Alia Atlas <akatlas@gmail.com> wrote:

> On Mon, Apr 14, 2014 at 11:57 AM, David Meyer <dmm@1-4-5.net> wrote:
> > On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.com>
> wrote:
> >> I'm surprised that no one has sent this out yet:
> >> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
> >>
> >> "Summary: After contributing to standards organizations for more than
> seven
> >> years, engineer Vidya Narayanan decided it was time to move on.
> Although she
> >> still believes that these organizations make the Internet a better
> place,
> >> she wonders about the pace of change versus the pace of organizations."
> >>
> >> My thoughts-
> >>
> >> There are some nuggets of truth in what she says in this article, and in
> >> some of the comments. I think that the problems are real, so there's
> value
> >> in taking the criticism constructively, despite the fact that the author
> >> chose to focus on the problems without any suggestions of solutions.
> >>
> >> "while the pace at which standards are written hasn't changed in many
> years,
> >> the pace at which the real world adopts software has become orders of
> >> magnitude faster."
> >> ...
> >> "Running code and rough consensus, the motto of the IETF, used to be
> >> realizable at some point. ... In the name of consensus, we debate
> frivolous
> >> details forever. In the name of patents, we never finish."
> >> ...
> >> "Unless these standards organizations make radical shifts towards
> >> practicality, their relevance will soon be questionable."
> >>
> >> I don't have too many big ideas how to fix these problems, but I'll at
> least
> >> take a crack at it in order to spur discussion. My paraphrase of the
> problem
> >> and some discussion follows.
> >>
> >> - We've lost sight of consensus and are too often derailed by a vocal
> >> minority of those willing to endlessly debate a point.
> >>
> >> Part of the solution to that is reiterating what consensus is and is
> not,
> >> such as draft-resnick-on-consensus so that we don't confuse a need for
> >> consensus with a need for unanimity. Part of the solution is IETF
> leadership
> >> helping to identify when we have rough consensus encumbered by a debate
> that
> >> will never resolve itself, without quieting actual disagreement that
> needs
> >> continued discussion in order to find a compromise. I don't have good
> >> suggestions on how to make that second half better.
> >>
> >> - We don't have nearly enough focus on running code as the thing that
> helps
> >> to ensure that we're using our limited cycles on getting the right
> things
> >> out expediently, and either getting the design right the first time, or
> >> failing quickly and iterating to improve
> >>
> >> The solution here may be that we need to be much more aggressive at
> >> expecting any standards track documents to have running code much
> earlier in
> >> the process. The other part of that is to renew our focus on actual
> interop
> >> standards work, probably by charter or in-group feedback, shift focus
> away
> >> from BCP and info documents. Perhaps when considering whether to proceed
> >> with a given document, we need test as to whether it's actively
> >> helpful/needed and ensure that we know what audience would be looking
> at it,
> >> rather than simply ensuring that it is "not harmful" and mostly within
> the
> >> WG's chartered focus.
> >
> > My friend @colin_dixon pointed this out to me yesterday, and I've been
> > giving it quite a bit of thought since then (I have a nascent blog on
> > the topic of how open source and standards orgs might
> > productively/efficiently work together; follow up to
> >
> http://www.sdncentral.com/education/david-meyer-reflections-opendaylight-open-source-project-brocade/2014/03
> ).
> >
> > What I can say is that after seeing the kind of progress that several
> > open source communities make (they do epitomize the best of the IETF's
> > running code/rough consensus ethic), one does have to wonder if
> > traditional standards making is either obsolete or in dire need of a
> > make over. What is needed, IMO, is a reimagining of how the standards
> > process interacts with the open source movement specifically focused
> > on how they can compliment one another.
>
> [Alia] It would be very useful to have a functional model for how the
> two can compliment each other.  We also tend to talk about open-source
> as a single monolith - when it can have very different models for
> accepting in changes, how and who runs the community, who is really
> participating (open source doesn't mean non-corporate) etc.   Some of
> what the IETF does is the architecture and requirements thinking about
> how the solution should fit in - while some of the open-source is
> about getting a solution implemented ASAP.   IMHO, a spiral is useful
> with an easy way of interaction.  With I2RS, as a WG chair, I
> suggested having experimental drafts describing solutions that were
> being implemented - but haven't seen any.   A question is what is
> needed to encourage the interactions.
>
>

+1

I was going to mention OpenDaylight as a cooperation model.
I think their goal is to provide implementation feedback to
the I2RS, NETMOD, and other WGs.

The corporate acceptance of open-source software is the key trend.
I would not characterize any of these well-funded projects as
quick-and-dirty, or "solution implemented ASAP" (any more than
every commercial project I've worked on in my career. :-)


[Alia] Diversity of implementation is important as is stability of a
> standard and it being understood how to change/upgrade for different
> versions.  These don't come automatically via open-source.
>
>
Right.  Vendors have to decide to contribute engineering hours to a project,
similar to the decision to let engineers contribute to SDOs.

Open-source software can move the "standards boundary"
and achieve multi-vendor support at the north-bound API only.
For example, a vendor can provide a proprietary Python plug-in
(e.g. OpenStack Neutron) for an open-source platform, without
standardizing the south-bound protocols.

Regards,
> Alia
>
>
Andy

--001a1133886ed6943b04f7038f41
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Mon, Apr 14, 2014 at 9:07 AM, Alia Atlas <span dir=3D"ltr">&lt;<=
a href=3D"mailto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail.com</a>=
&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">On Mon, Apr 14, 2014 at 11:57 AM, David Meye=
r &lt;<a href=3D"mailto:dmm@1-4-5.net">dmm@1-4-5.net</a>&gt; wrote:<br>
&gt; On Mon, Apr 14, 2014 at 8:08 AM, George, Wes &lt;<a href=3D"mailto:wes=
ley.george@twcable.com">wesley.george@twcable.com</a>&gt; wrote:<br>
&gt;&gt; I&rsquo;m surprised that no one has sent this out yet:<br>
&gt;&gt; <a href=3D"http://gigaom.com/2014/04/12/why-i-quit-writing-interne=
t-standards/" target=3D"_blank">http://gigaom.com/2014/04/12/why-i-quit-wri=
ting-internet-standards/</a><br>
&gt;&gt;<br>
&gt;&gt; &quot;Summary: After contributing to standards organizations for m=
ore than seven<br>
&gt;&gt; years, engineer Vidya Narayanan decided it was time to move on. Al=
though she<br>
&gt;&gt; still believes that these organizations make the Internet a better=
 place,<br>
&gt;&gt; she wonders about the pace of change versus the pace of organizati=
ons.&quot;<br>
&gt;&gt;<br>
&gt;&gt; My thoughts-<br>
&gt;&gt;<br>
&gt;&gt; There are some nuggets of truth in what she says in this article, =
and in<br>
&gt;&gt; some of the comments. I think that the problems are real, so there=
&rsquo;s value<br>
&gt;&gt; in taking the criticism constructively, despite the fact that the =
author<br>
&gt;&gt; chose to focus on the problems without any suggestions of solution=
s.<br>
&gt;&gt;<br>
&gt;&gt; &quot;while the pace at which standards are written hasn&rsquo;t c=
hanged in many years,<br>
&gt;&gt; the pace at which the real world adopts software has become orders=
 of<br>
&gt;&gt; magnitude faster.&quot;<br>
&gt;&gt; &hellip;<br>
&gt;&gt; &quot;Running code and rough consensus, the motto of the IETF, use=
d to be<br>
&gt;&gt; realizable at some point. &hellip; In the name of consensus, we de=
bate frivolous<br>
&gt;&gt; details forever. In the name of patents, we never finish.&rdquo;<b=
r>
&gt;&gt; &hellip;<br>
&gt;&gt; &quot;Unless these standards organizations make radical shifts tow=
ards<br>
&gt;&gt; practicality, their relevance will soon be questionable.&rdquo;<br=
>
&gt;&gt;<br>
&gt;&gt; I don&rsquo;t have too many big ideas how to fix these problems, b=
ut I&rsquo;ll at least<br>
&gt;&gt; take a crack at it in order to spur discussion. My paraphrase of t=
he problem<br>
&gt;&gt; and some discussion follows.<br>
&gt;&gt;<br>
&gt;&gt; - We&rsquo;ve lost sight of consensus and are too often derailed b=
y a vocal<br>
&gt;&gt; minority of those willing to endlessly debate a point.<br>
&gt;&gt;<br>
&gt;&gt; Part of the solution to that is reiterating what consensus is and =
is not,<br>
&gt;&gt; such as draft-resnick-on-consensus so that we don&rsquo;t confuse =
a need for<br>
&gt;&gt; consensus with a need for unanimity. Part of the solution is IETF =
leadership<br>
&gt;&gt; helping to identify when we have rough consensus encumbered by a d=
ebate that<br>
&gt;&gt; will never resolve itself, without quieting actual disagreement th=
at needs<br>
&gt;&gt; continued discussion in order to find a compromise. I don&rsquo;t =
have good<br>
&gt;&gt; suggestions on how to make that second half better.<br>
&gt;&gt;<br>
&gt;&gt; - We don&rsquo;t have nearly enough focus on running code as the t=
hing that helps<br>
&gt;&gt; to ensure that we&rsquo;re using our limited cycles on getting the=
 right things<br>
&gt;&gt; out expediently, and either getting the design right the first tim=
e, or<br>
&gt;&gt; failing quickly and iterating to improve<br>
&gt;&gt;<br>
&gt;&gt; The solution here may be that we need to be much more aggressive a=
t<br>
&gt;&gt; expecting any standards track documents to have running code much =
earlier in<br>
&gt;&gt; the process. The other part of that is to renew our focus on actua=
l interop<br>
&gt;&gt; standards work, probably by charter or in-group feedback, shift fo=
cus away<br>
&gt;&gt; from BCP and info documents. Perhaps when considering whether to p=
roceed<br>
&gt;&gt; with a given document, we need test as to whether it&rsquo;s activ=
ely<br>
&gt;&gt; helpful/needed and ensure that we know what audience would be look=
ing at it,<br>
&gt;&gt; rather than simply ensuring that it is &ldquo;not harmful&rdquo; a=
nd mostly within the<br>
&gt;&gt; WG&rsquo;s chartered focus.<br>
&gt;<br>
&gt; My friend @colin_dixon pointed this out to me yesterday, and I&#39;ve =
been<br>
&gt; giving it quite a bit of thought since then (I have a nascent blog on<=
br>
&gt; the topic of how open source and standards orgs might<br>
&gt; productively/efficiently work together; follow up to<br>
&gt; <a href=3D"http://www.sdncentral.com/education/david-meyer-reflections=
-opendaylight-open-source-project-brocade/2014/03" target=3D"_blank">http:/=
/www.sdncentral.com/education/david-meyer-reflections-opendaylight-open-sou=
rce-project-brocade/2014/03</a>).<br>

&gt;<br>
&gt; What I can say is that after seeing the kind of progress that several<=
br>
&gt; open source communities make (they do epitomize the best of the IETF&#=
39;s<br>
&gt; running code/rough consensus ethic), one does have to wonder if<br>
&gt; traditional standards making is either obsolete or in dire need of a<b=
r>
&gt; make over. What is needed, IMO, is a reimagining of how the standards<=
br>
&gt; process interacts with the open source movement specifically focused<b=
r>
&gt; on how they can compliment one another.<br>
<br>
[Alia] It would be very useful to have a functional model for how the<br>
two can compliment each other. &nbsp;We also tend to talk about open-source=
<br>
as a single monolith - when it can have very different models for<br>
accepting in changes, how and who runs the community, who is really<br>
participating (open source doesn&#39;t mean non-corporate) etc. &nbsp; Some=
 of<br>
what the IETF does is the architecture and requirements thinking about<br>
how the solution should fit in - while some of the open-source is<br>
about getting a solution implemented ASAP. &nbsp; IMHO, a spiral is useful<=
br>
with an easy way of interaction. &nbsp;With I2RS, as a WG chair, I<br>
suggested having experimental drafts describing solutions that were<br>
being implemented - but haven&#39;t seen any. &nbsp; A question is what is<=
br>
needed to encourage the interactions.<br>
<br></blockquote><div><br></div><div><br></div><div>+1</div><div><br></div>=
<div>I was going to mention OpenDaylight as a cooperation model.</div><div>=
I think their goal is to provide implementation feedback to</div><div>
the I2RS, NETMOD, and other WGs.</div><div><br></div><div>The corporate acc=
eptance of open-source software is the key trend.</div><div>I would not cha=
racterize any of these well-funded projects as</div><div>quick-and-dirty, o=
r &quot;solution implemented ASAP&quot; (any more than</div>
<div>every commercial project I&#39;ve worked on in my career. :-)</div><di=
v><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[Alia] Diversity of implementation is important as is stability of a<br>
standard and it being understood how to change/upgrade for different<br>
versions. &nbsp;These don&#39;t come automatically via open-source.<br>
<br></blockquote><div><br></div><div>Right. &nbsp;Vendors have to decide to=
 contribute engineering hours to a project,</div><div>similar to the decisi=
on to let engineers contribute to SDOs. &nbsp;</div><div><br></div><div>Ope=
n-source software can move the &quot;standards boundary&quot;</div>
<div>and achieve multi-vendor support at the north-bound API only.</div><di=
v>For example, a vendor can provide a proprietary Python plug-in</div><div>=
(e.g. OpenStack Neutron) for an open-source platform, without</div><div>
standardizing the south-bound protocols.</div><div><br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">
Regards,<br>
Alia<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Andy</div><div clas=
s=3D"gmail_extra"><br></div></div>

--001a1133886ed6943b04f7038f41--


From nobody Mon Apr 14 10:01:15 2014
Return-Path: <spromano@unina.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACDAB1A04D2 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:01:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.408
X-Spam-Level: **
X-Spam-Status: No, score=2.408 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 34Kg8TSgZeFm for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:01:10 -0700 (PDT)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 2EAAB1A03D7 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:01:10 -0700 (PDT)
Received: from [143.225.28.167] ([143.225.28.167]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id s3EH1588031774 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 14 Apr 2014 19:01:06 +0200
Subject: Re: "why I quit writing internet standards"
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: multipart/alternative; boundary="Apple-Mail=_C755E6C8-4810-4CE6-B36E-9944C5DC927E"
From: Simon Pietro Romano <spromano@unina.it>
In-Reply-To: <19983.1397493280@sandelman.ca>
Date: Mon, 14 Apr 2014 19:01:05 +0200
Message-Id: <8B56205B-8143-4B5B-B2FD-22FABE95ED16@unina.it>
References: <CF71721A.180A9%wesley.george@twcable.com> <19983.1397493280@sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZfClGjfv9xYBJY1lMbO391lBDbE
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:01:14 -0000

--Apple-Mail=_C755E6C8-4810-4CE6-B36E-9944C5DC927E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

I read the post from Vidya and I have to say I totally agree with her. =
As to running code, in particular, my impression is that if you are used =
to implement prototypes of ongoing standards and you're neither a big =
company nor a member of the IETF elite of gurus, the best you can buck =
for is an informational "call flows" RFC. Standards Track stuff is left =
to those who (seem to) do the high-level specification work. This =
happens because people seem to rush for editing documents as soon as a =
new WG is chartered, but then they progressively reduce efforts when =
such a WG starts to lose momentum and is not latest fashion any longer.
Finally, coming to interoperability, it is hard to work on it if your =
implementation is the only one available. In the long run, I do =
acknowledge the fact that you get tired of doing all that hard work and =
investing so many cycles in a highly underestimated engineering =
activity.

My two cents,

Simon


On 14/apr/2014, at 18:34, Michael Richardson wrote:

>=20
> George, Wes <wesley.george@twcable.com> wrote:
>> - We don=92t have nearly enough focus on running code as the thing =
that helps to
>> ensure that we=92re using our limited cycles on getting the right =
things out
>> expediently, and either getting the design right the first time, or =
failing
>> quickly and iterating to improve
>=20
>> The solution here may be that we need to be much more aggressive at =
expecting
>> any standards track documents to have running code much earlier in =
the
>> process.
>=20
> For instance, had DMARC proponents and/or Yahoo, spent some time =
making sure
> that there was some running code for mailing list use, life would be =
better.
>=20
> I'm not entirely clear how it was that we produced/funded (more) =
running code in the
> 1990s.  Maybe this is a false idea; it could be that there was less =
code then
> than there is now.   I will posit several factors:
>  1) there was less working occuring, and perhaps over a longer time =
period
>     (where time is subject to perception as well as reality), such =
that
>     code became mature sooner in the specification process, and/or =
there
>     were simply more volunteers willing to produce it.
>=20
>  2) many companies were much smaller, and it was easier to get line =
managers
>     to see why they wanted to be directly involved, even lead, =
efforts.
>=20
>  3) it wasn't so much the dotcom boom which made money available via =
VCs,
>     but rather that the (ultimately unstainable) revenue doubling, =
quarter
>     over quarter which made resources available for prototypes.
>=20
>  4) there were some clear institutions (MIT, CMU, Berkeley, LLBL, UW) =
where
>     some good reference implementations were developed by students, =
faculty,
>     staff.  And don't forget WIDE and USAGI!!!
>=20
> When I founded Xelerance, it was with the idea that multiple large
> organizations were shipping IPsec code on Linux, and would rather pay =
a
> company a maintenance fee than attempt to manage the process =
internally.
> We got some work funded, but we never got enough funding to get ahead =
of
> the standardization process and write code will an ID was still young.
> Overall, that effort failed.
>=20
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -=3D IPv6 IoT consulting =3D-
>=20
>=20
>=20

                     					       _\\|//_
                           				      ( O-O )
   ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
                    				Simon Pietro Romano
             				 Universita' di Napoli Federico =
II
                		     Computer Engineering Department=20
	             Phone: +39 081 7683823 -- Fax: +39 081 7683816
                                           e-mail: spromano@unina.it

		    <<Molti mi dicono che lo scoraggiamento =E8 l'alibi =
degli=20
		    idioti. Ci rifletto un istante; e mi scoraggio>>. =
Magritte.
               			                     oooO
  ~~~~~~~~~~~~~~~~~~~~~~~(   )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
					                 \ (            =
(   )
			                                  \_)          ) =
/
                                                                       =
(_/







--Apple-Mail=_C755E6C8-4810-4CE6-B36E-9944C5DC927E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
">Hi,<div><br></div><div>I read the post from Vidya and I have to say I =
totally agree with her. As to running code, in particular, my impression =
is that if you are used to implement prototypes of ongoing standards and =
you're neither a big company nor a member of the IETF elite of gurus, =
the best you can buck for is an informational "call flows" RFC. =
Standards Track stuff is left to those who (seem to) do the high-level =
specification work. This happens because people seem to rush for editing =
documents as soon as a new WG is chartered, but then they progressively =
reduce efforts when such a WG starts to lose momentum and is not latest =
fashion any longer.</div><div>Finally, coming to interoperability, it is =
hard to work on it if your implementation is the only one available. In =
the long run, I do acknowledge the fact that you get tired of doing all =
that hard work and investing so many cycles in a highly underestimated =
engineering activity.</div><div><br></div><div>My two =
cents,</div><div><br></div><div>Simon</div><div><br></div><div><br><div><d=
iv>On 14/apr/2014, at 18:34, Michael Richardson wrote:</div><br =
class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div><br>George, Wes &lt;<a =
href=3D"mailto:wesley.george@twcable.com">wesley.george@twcable.com</a>&gt=
; wrote:<br><blockquote type=3D"cite">- We don=92t have nearly enough =
focus on running code as the thing that helps =
to<br></blockquote><blockquote type=3D"cite">ensure that we=92re using =
our limited cycles on getting the right things =
out<br></blockquote><blockquote type=3D"cite">expediently, and either =
getting the design right the first time, or =
failing<br></blockquote><blockquote type=3D"cite">quickly and iterating =
to improve<br></blockquote><br><blockquote type=3D"cite">The solution =
here may be that we need to be much more aggressive at =
expecting<br></blockquote><blockquote type=3D"cite">any standards track =
documents to have running code much earlier in =
the<br></blockquote><blockquote =
type=3D"cite">process.<br></blockquote><br>For instance, had DMARC =
proponents and/or Yahoo, spent some time making sure<br>that there was =
some running code for mailing list use, life would be better.<br><br>I'm =
not entirely clear how it was that we produced/funded (more) running =
code in the<br>1990s. &nbsp;Maybe this is a false idea; it could be that =
there was less code then<br>than there is now. &nbsp;&nbsp;I will posit =
several factors:<br> &nbsp;1) there was less working occuring, and =
perhaps over a longer time period<br> &nbsp;&nbsp;&nbsp;&nbsp;(where =
time is subject to perception as well as reality), such that<br> =
&nbsp;&nbsp;&nbsp;&nbsp;code became mature sooner in the specification =
process, and/or there<br> &nbsp;&nbsp;&nbsp;&nbsp;were simply more =
volunteers willing to produce it.<br><br> &nbsp;2) many companies were =
much smaller, and it was easier to get line managers<br> =
&nbsp;&nbsp;&nbsp;&nbsp;to see why they wanted to be directly involved, =
even lead, efforts.<br><br> &nbsp;3) it wasn't so much the dotcom boom =
which made money available via VCs,<br> &nbsp;&nbsp;&nbsp;&nbsp;but =
rather that the (ultimately unstainable) revenue doubling, quarter<br> =
&nbsp;&nbsp;&nbsp;&nbsp;over quarter which made resources available for =
prototypes.<br><br> &nbsp;4) there were some clear institutions (MIT, =
CMU, Berkeley, LLBL, UW) where<br> &nbsp;&nbsp;&nbsp;&nbsp;some good =
reference implementations were developed by students, faculty,<br> =
&nbsp;&nbsp;&nbsp;&nbsp;staff. &nbsp;And don't forget WIDE and =
USAGI!!!<br><br>When I founded Xelerance, it was with the idea that =
multiple large<br>organizations were shipping IPsec code on Linux, and =
would rather pay a<br>company a maintenance fee than attempt to manage =
the process internally.<br>We got some work funded, but we never got =
enough funding to get ahead of<br>the standardization process and write =
code will an ID was still young.<br>Overall, that effort =
failed.<br><br>--<br>Michael Richardson &lt;<a =
href=3D"mailto:mcr+IETF@sandelman.ca">mcr+IETF@sandelman.ca</a>&gt;, =
Sandelman Software Works<br> -=3D IPv6 IoT consulting =
=3D-<br><br><br><br></div></blockquote></div><br><div =
apple-content-edited=3D"true">
<span class=3D"Apple-style-span" style=3D"border-collapse: separate; =
color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: =
0px; text-transform: none; white-space: normal; widows: 2; word-spacing: =
0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; color: =
rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: =
normal; font-weight: normal; letter-spacing: normal; line-height: =
normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; =
text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><span class=3D"Apple-style-span" =
style=3D"border-collapse: separate; color: rgb(0, 0, 0); font-family: =
Helvetica; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; orphans: 2; =
text-align: -webkit-auto; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: =
0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div =
style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; "><div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span><span class=3D"Apple-converted-space">&nbsp;</span>&nbsp; =
&nbsp; &nbsp; _\\|//_</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;<span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>&nbsp; &nbsp; &nbsp;&nbsp;( O-O )</div><div>&nbsp; =
&nbsp;~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div><di=
v>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
</span>Simon Pietro Romano</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; =
">				</span><span =
class=3D"Apple-converted-space">&nbsp;</span>Universita' di Napoli =
Federico II</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;&nbsp;<span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
	</span>&nbsp; &nbsp; &nbsp;Computer Engineering =
Department&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">	</span>&nbsp; &nbsp; &nbsp;&nbsp; &nbsp; =
&nbsp; &nbsp; Phone: +39 081 7683823 -- Fax: +39 081 =
7683816</div><div>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;e-mail: <a =
href=3D"mailto:spromano@unina.it">spromano@unina.it</a></div><div><br></di=
v><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">		=
</span>&nbsp; &nbsp; &lt;&lt;Molti mi dicono che lo scoraggiamento =E8 =
l'alibi degli&nbsp;</div><div><span class=3D"Apple-tab-span" =
style=3D"white-space: pre; ">		</span>&nbsp;&nbsp; =
&nbsp;idioti. Ci rifletto un istante; e mi scoraggio&gt;&gt;. =
Magritte.</div><div>&nbsp; &nbsp; &nbsp; &nbsp;&nbsp; &nbsp; &nbsp; =
&nbsp;<span class=3D"Apple-converted-space">&nbsp;</span><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">			=
</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp;oooO</div><div>&nbsp; ~~~~~~~~~~~~~~~~~~~~~~~( &nbsp; =
)~~~&nbsp;Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div><div><span =
class=3D"Apple-tab-span" style=3D"white-space: pre; ">				=
	</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp;\ ( &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;( &nbsp; =
)</div><div><span class=3D"Apple-tab-span" style=3D"white-space: pre; ">	=
		</span>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
\_) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;) /</div><div>&nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; =
&nbsp; &nbsp; &nbsp;(_/</div></div><div><br></div></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></div></span><br =
class=3D"Apple-interchange-newline"></span><br =
class=3D"Apple-interchange-newline">
</div>
<br></div></body></html>=

--Apple-Mail=_C755E6C8-4810-4CE6-B36E-9944C5DC927E--


From nobody Mon Apr 14 10:07:36 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70A531A0572 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.018
X-Spam-Level: *
X-Spam-Status: No, score=1.018 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 tviUcvD6Jbh7 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:07:29 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 946C61A04C1 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:07:29 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id DAF6BCC0B5 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:07:26 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id m1bprZLOffVD for <ietf@ietf.org>; Mon, 14 Apr 2014 13:07:18 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 0890CCC0A7 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:07:18 -0400 (EDT)
Message-ID: <534C15C5.6040300@meetinghouse.net>
Date: Mon, 14 Apr 2014 13:07:17 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <19983.1397493280@sandelman.ca> <8B56205B-8143-4B5B-B2FD-22FABE95ED16@unina.it>
In-Reply-To: <8B56205B-8143-4B5B-B2FD-22FABE95ED16@unina.it>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/T9hldMI0aXCoY6hMzF-dPewBUYc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:07:33 -0000

It probably also helped, back in the day, that so many people working on 
protocols were doing so under funded grants.

Miles

Simon Pietro Romano wrote:
> Hi,
>
> I read the post from Vidya and I have to say I totally agree with her. 
> As to running code, in particular, my impression is that if you are 
> used to implement prototypes of ongoing standards and you're neither a 
> big company nor a member of the IETF elite of gurus, the best you can 
> buck for is an informational "call flows" RFC. Standards Track stuff 
> is left to those who (seem to) do the high-level specification work. 
> This happens because people seem to rush for editing documents as soon 
> as a new WG is chartered, but then they progressively reduce efforts 
> when such a WG starts to lose momentum and is not latest fashion any 
> longer.
> Finally, coming to interoperability, it is hard to work on it if your 
> implementation is the only one available. In the long run, I do 
> acknowledge the fact that you get tired of doing all that hard work 
> and investing so many cycles in a highly underestimated engineering 
> activity.
>
> My two cents,
>
> Simon
>
>
> On 14/apr/2014, at 18:34, Michael Richardson wrote:
>
>>
>> George, Wes <wesley.george@twcable.com 
>> <mailto:wesley.george@twcable.com>> wrote:
>>> - We don’t have nearly enough focus on running code as the thing 
>>> that helps to
>>> ensure that we’re using our limited cycles on getting the right 
>>> things out
>>> expediently, and either getting the design right the first time, or 
>>> failing
>>> quickly and iterating to improve
>>
>>> The solution here may be that we need to be much more aggressive at 
>>> expecting
>>> any standards track documents to have running code much earlier in the
>>> process.
>>
>> For instance, had DMARC proponents and/or Yahoo, spent some time 
>> making sure
>> that there was some running code for mailing list use, life would be 
>> better.
>>
>> I'm not entirely clear how it was that we produced/funded (more) 
>> running code in the
>> 1990s.  Maybe this is a false idea; it could be that there was less 
>> code then
>> than there is now.   I will posit several factors:
>>  1) there was less working occuring, and perhaps over a longer time 
>> period
>>     (where time is subject to perception as well as reality), such that
>>     code became mature sooner in the specification process, and/or there
>>     were simply more volunteers willing to produce it.
>>
>>  2) many companies were much smaller, and it was easier to get line 
>> managers
>>     to see why they wanted to be directly involved, even lead, efforts.
>>
>>  3) it wasn't so much the dotcom boom which made money available via VCs,
>>     but rather that the (ultimately unstainable) revenue doubling, 
>> quarter
>>     over quarter which made resources available for prototypes.
>>
>>  4) there were some clear institutions (MIT, CMU, Berkeley, LLBL, UW) 
>> where
>>     some good reference implementations were developed by students, 
>> faculty,
>>     staff.  And don't forget WIDE and USAGI!!!
>>
>> When I founded Xelerance, it was with the idea that multiple large
>> organizations were shipping IPsec code on Linux, and would rather pay a
>> company a maintenance fee than attempt to manage the process internally.
>> We got some work funded, but we never got enough funding to get ahead of
>> the standardization process and write code will an ID was still young.
>> Overall, that effort failed.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca 
>> <mailto:mcr+IETF@sandelman.ca>>, Sandelman Software Works
>> -= IPv6 IoT consulting =-
>>
>>
>>
>
>   _\\|//_
>       ( O-O )
>  ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
> Simon Pietro Romano
> Universita' di Napoli Federico II
>      Computer Engineering Department
>       Phone: +39 081 7683823 -- Fax: +39 081 7683816
>  e-mail: spromano@unina.it <mailto:spromano@unina.it>
>
> <<Molti mi dicono che lo scoraggiamento è l'alibi degli
>  idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>                      oooO
>   ~~~~~~~~~~~~~~~~~~~~~~~( )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>            \ (            (   )
>                             \_)          ) /
>                              (_/
>
>
>
>
>
>


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 10:12:27 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F26461A0564 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 QS7Z9ASgjnMr for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:12:18 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 8B91C1A059F for <ietf@ietf.org>; Mon, 14 Apr 2014 10:12:18 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w61so8497476wes.1 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:12:15 -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:content-type; bh=8KS6fnybB9Ye44bwNBd5+nt9+7p4hmJo1Ks4ZVRgZVg=; b=02+g1Ta3ydakU6e1j9NUFFh8m4+EIZhBxaos4GplSl2cHNd0T9bGooe3CxPDVu+DMc kxigutSRqWnDNSGR2O7Imve+2J0gMviqNYrh3xNzGkUDFu1xELMGA8BEsyT86/YNTp5+ aNcoR04Ec1BYotjdQp5UuW4aaFIzrVg6BI/+YPeIYr4B3hlsRD7Zv1pr7FP5sraTFGav qVlPrPFYib/2IdnXg/RwdaWJKLSYJRsQx1KxrmJFnPvY28PuD6i78xMfg9nnPmWTeSQ3 rMPBaHljWnhYX7PgFmSQn6sHQDvPcPBC75DHuIHI5w1qOnmMoeiVauBbCe59dXH8dw1m kfOA==
MIME-Version: 1.0
X-Received: by 10.194.243.3 with SMTP id wu3mr33722129wjc.29.1397495535330; Mon, 14 Apr 2014 10:12:15 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 10:12:14 -0700 (PDT)
In-Reply-To: <CF71721A.180A9%wesley.george@twcable.com>
References: <CF71721A.180A9%wesley.george@twcable.com>
Date: Mon, 14 Apr 2014 10:12:14 -0700
Message-ID: <CAL0qLwbBNWY6qVSj6z82vZwjNccNgCdWD4Y0XwrG5Bx0wWPJ-g@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "George, Wes" <wesley.george@twcable.com>
Content-Type: multipart/alternative; boundary=089e013d14c4f56c8f04f703c8c7
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Y7oRvnLJqxbWFZoqO-XsIf-mhL4
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:12:24 -0000

--089e013d14c4f56c8f04f703c8c7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.com>wro=
te:

>  I=E2=80=99m surprised that no one has sent this out yet:
> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>
>  "Summary: After contributing to standards organizations for more than
> seven years, engineer Vidya Narayanan decided it was time to move on.
> Although she still believes that these organizations make the Internet a
> better place, she wonders about the pace of change versus the pace of
> organizations."
> [...]
>

Hi Wes,

I'm so glad you posted this.  I imagine there's a large community of
engineers, open source and otherwise, that avoid getting involved in
standards work in the first place specifically for the reasons this article
and this thread are highlighting.

There's a large part of my time in the IETF, spanning several employers of
varying sizes, that has been frustrating because there are serious pain
points that need solving, but even creative solutions are often stymied by
a wall of objection rather than curiosity and exploration.  It's exhausting
to want to make the Internet work better but be told time and again that
it's as good as it can get, and that fixing what's broken would cost too
much because any useful change would just be too disruptive (though
sometimes only to a vocal minority).  Worse, I've bought the argument, and
thus (sadly) started doing the same thing to others, in direct conflict
with my open source roots and other similar influences.

The DMARC issue at hand is possibly a good, though extreme, example.  Part
of the email community is suffering a great deal of pain because of the
abuse brought about by the fact that definitions made 30 years ago have
evidently not scaled to the modern Internet.  Previous efforts at solutions
have drawn huge investments of time and energy, but ultimately have had
limited (i.e., almost no) effect in the name of being purely incremental
and non-disruptive, brought on by a few who cling tenaciously to the status
quo.  Finally one operator had enough and did something terribly drastic,
presumably because no solution has been forthcoming in a decade or more.
>From where I sit, it looks a lot like we, the IETF, have failed to produce
workable solutions, opting instead to come to consensus on a "Sorry, it is
what it is" posture.  This is the result.

I believe in standards work, and I find the work very stimulating when it
actually makes progress.  But I also get tired sometimes of having to
explain to my employers, who foot the bill for my participation, why I'm
still going, because the impact just isn't there.

-MSK

--089e013d14c4f56c8f04f703c8c7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <span dir=3D"=
ltr">&lt;<a href=3D"mailto:wesley.george@twcable.com" target=3D"_blank">wes=
ley.george@twcable.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra">=
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">



<div style=3D"font-size:14px;font-family:Calibri,sans-serif;word-wrap:break=
-word">
<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
I=E2=80=99m surprised that no one has sent this out yet:=C2=A0<a href=3D"ht=
tp://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/" target=
=3D"_blank">http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standa=
rds/</a></div>

<div style=3D"font-size:14px;font-family:Calibri,sans-serif">
<br>
</div>
<div style>&quot;Summary:=C2=A0<span style=3D"line-height:22px;color:rgb(42=
,46,51);font-style:italic">After contributing to standards organizations fo=
r more than seven years, engineer Vidya Narayanan
 decided it was time to move on. Although she still believes that these org=
anizations make the Internet a better place, she wonders about the pace of =
change versus the pace of organizations.&quot;</span></div>
<div style>[...]<br></div></div></blockquote><div><br></div><div>Hi Wes,<br=
><br></div><div>I&#39;m so glad you posted this.=C2=A0 I imagine there&#39;=
s a large community of engineers, open source and otherwise, that avoid get=
ting involved in standards work in the first place specifically for the rea=
sons this article and this thread are highlighting.<br>
<br></div>There&#39;s a large part of my time in the IETF, spanning several=
 employers of varying sizes, that has been frustrating because there are se=
rious pain points that need solving, but even creative solutions are often =
stymied by a wall of objection rather than curiosity and exploration.=C2=A0=
 It&#39;s exhausting to want to make the Internet work better but be told t=
ime and again that it&#39;s as good as it can get, and that fixing what&#39=
;s broken would cost too much because any useful change would just be too d=
isruptive (though sometimes only to a vocal minority).=C2=A0 Worse, I&#39;v=
e bought the argument, and thus (sadly) started doing the same thing to oth=
ers, in direct conflict with my open source roots and other similar influen=
ces.<br>
<br></div><div class=3D"gmail_quote">The DMARC issue at hand is possibly a =
good, though extreme, example.=C2=A0 Part of the email community is sufferi=
ng a great deal of pain because of the abuse brought about by the fact that=
 definitions made 30 years ago have evidently not scaled to the modern Inte=
rnet.=C2=A0 Previous efforts at solutions have drawn huge investments of ti=
me and energy, but ultimately have had limited (i.e., almost no) effect in =
the name of being purely incremental and non-disruptive, brought on by a fe=
w who cling tenaciously to the status quo.=C2=A0 Finally one operator had e=
nough and did something terribly drastic, presumably because no solution ha=
s been forthcoming in a decade or more.=C2=A0 From where I sit, it looks a =
lot like we, the IETF, have failed to produce workable solutions, opting in=
stead to come to consensus on a &quot;Sorry, it is what it is&quot; posture=
.=C2=A0 This is the result.<br>
<br></div><div class=3D"gmail_quote">I believe in standards work, and I fin=
d the work very stimulating when it actually makes progress.=C2=A0 But I al=
so get tired sometimes of having to explain to my employers, who foot the b=
ill for my participation, why I&#39;m still going, because the impact just =
isn&#39;t there.<br>
<br></div><div class=3D"gmail_quote">-MSK<br></div></div></div>

--089e013d14c4f56c8f04f703c8c7--


From nobody Mon Apr 14 10:14:25 2014
Return-Path: <dmm@1-4-5.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D87C1A065B for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:14:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.122
X-Spam-Level: 
X-Spam-Status: No, score=0.122 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 m7SZ_0bzzdg5 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:14:19 -0700 (PDT)
Received: from mail-qg0-f53.google.com (mail-qg0-f53.google.com [209.85.192.53]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4BD1A059F for <ietf@ietf.org>; Mon, 14 Apr 2014 10:14:19 -0700 (PDT)
Received: by mail-qg0-f53.google.com with SMTP id f51so7655276qge.40 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:14:16 -0700 (PDT)
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:content-type :content-transfer-encoding; bh=YCiO4xRJuO/Cq0GEmYzmFEh53iZ6VIg1AXulVb9kQqk=; b=LhfTZ0Skv6dI65OajlVlAFJiGNS2mB0yVmbqfnfFjaTiwSomiuR8YoKKtdeclABIG3 9Rmz7ihUeHwGW5bJn1TIBONKpx8mpdlMPCZzY3RsY6ARErmSl4LMKZ7UpBwxdIePddaR 2amRtbprStWq9l++TRWGMiSaAt63hkntoJBHgjtsPXrbwbHHLofR7jakYBlKJtfoZstY sABAmo/hYcsmOXnxJYbOuA6ALfkDdGPch/DCGbl4az6pNwB2WmZhQoJkzehHnJGQgfTc ghmT84HViE/d54lgrHwBUIgLwkivFDvcbsExLuIOv0k8aRC5CMVIN8BagdzB44jnkUje EJCg==
X-Gm-Message-State: ALoCoQlaXtzWOwMII3RU4M6/SnEEIEgJw8dVkielgapHf1ZQf9yEml/mvPglybZUea7Fjl2kzLVo
MIME-Version: 1.0
X-Received: by 10.229.136.135 with SMTP id r7mr52961054qct.17.1397495656516; Mon, 14 Apr 2014 10:14:16 -0700 (PDT)
Received: by 10.140.105.98 with HTTP; Mon, 14 Apr 2014 10:14:16 -0700 (PDT)
X-Originating-IP: [12.35.79.254]
In-Reply-To: <CABCOCHTRtoVmGffCuxKiNM1j0mRW1DLOR_db78=KBKTc7TA3Jg@mail.gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com> <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com> <CABCOCHTRtoVmGffCuxKiNM1j0mRW1DLOR_db78=KBKTc7TA3Jg@mail.gmail.com>
Date: Mon, 14 Apr 2014 10:14:16 -0700
Message-ID: <CAHiKxWgRhoO6cJDKUTxgAZN=x6Gned7JipM5_iEQV6TPtH82Lw@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: David Meyer <dmm@1-4-5.net>
To: Andy Bierman <andy@yumaworks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/u7ayN5_TbpO2HI4J_ihqkDtJeac
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:14:23 -0000

On Mon, Apr 14, 2014 at 9:56 AM, Andy Bierman <andy@yumaworks.com> wrote:
>
>
>
> On Mon, Apr 14, 2014 at 9:07 AM, Alia Atlas <akatlas@gmail.com> wrote:
>>
>> On Mon, Apr 14, 2014 at 11:57 AM, David Meyer <dmm@1-4-5.net> wrote:
>> > On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.co=
m>
>> > wrote:
>> >> I=E2=80=99m surprised that no one has sent this out yet:
>> >> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>> >>
>> >> "Summary: After contributing to standards organizations for more than
>> >> seven
>> >> years, engineer Vidya Narayanan decided it was time to move on.
>> >> Although she
>> >> still believes that these organizations make the Internet a better
>> >> place,
>> >> she wonders about the pace of change versus the pace of organizations=
."
>> >>
>> >> My thoughts-
>> >>
>> >> There are some nuggets of truth in what she says in this article, and
>> >> in
>> >> some of the comments. I think that the problems are real, so there=E2=
=80=99s
>> >> value
>> >> in taking the criticism constructively, despite the fact that the
>> >> author
>> >> chose to focus on the problems without any suggestions of solutions.
>> >>
>> >> "while the pace at which standards are written hasn=E2=80=99t changed=
 in many
>> >> years,
>> >> the pace at which the real world adopts software has become orders of
>> >> magnitude faster."
>> >> =E2=80=A6
>> >> "Running code and rough consensus, the motto of the IETF, used to be
>> >> realizable at some point. =E2=80=A6 In the name of consensus, we deba=
te
>> >> frivolous
>> >> details forever. In the name of patents, we never finish.=E2=80=9D
>> >> =E2=80=A6
>> >> "Unless these standards organizations make radical shifts towards
>> >> practicality, their relevance will soon be questionable.=E2=80=9D
>> >>
>> >> I don=E2=80=99t have too many big ideas how to fix these problems, bu=
t I=E2=80=99ll at
>> >> least
>> >> take a crack at it in order to spur discussion. My paraphrase of the
>> >> problem
>> >> and some discussion follows.
>> >>
>> >> - We=E2=80=99ve lost sight of consensus and are too often derailed by=
 a vocal
>> >> minority of those willing to endlessly debate a point.
>> >>
>> >> Part of the solution to that is reiterating what consensus is and is
>> >> not,
>> >> such as draft-resnick-on-consensus so that we don=E2=80=99t confuse a=
 need for
>> >> consensus with a need for unanimity. Part of the solution is IETF
>> >> leadership
>> >> helping to identify when we have rough consensus encumbered by a deba=
te
>> >> that
>> >> will never resolve itself, without quieting actual disagreement that
>> >> needs
>> >> continued discussion in order to find a compromise. I don=E2=80=99t h=
ave good
>> >> suggestions on how to make that second half better.
>> >>
>> >> - We don=E2=80=99t have nearly enough focus on running code as the th=
ing that
>> >> helps
>> >> to ensure that we=E2=80=99re using our limited cycles on getting the =
right
>> >> things
>> >> out expediently, and either getting the design right the first time, =
or
>> >> failing quickly and iterating to improve
>> >>
>> >> The solution here may be that we need to be much more aggressive at
>> >> expecting any standards track documents to have running code much
>> >> earlier in
>> >> the process. The other part of that is to renew our focus on actual
>> >> interop
>> >> standards work, probably by charter or in-group feedback, shift focus
>> >> away
>> >> from BCP and info documents. Perhaps when considering whether to
>> >> proceed
>> >> with a given document, we need test as to whether it=E2=80=99s active=
ly
>> >> helpful/needed and ensure that we know what audience would be looking
>> >> at it,
>> >> rather than simply ensuring that it is =E2=80=9Cnot harmful=E2=80=9D =
and mostly within
>> >> the
>> >> WG=E2=80=99s chartered focus.
>> >
>> > My friend @colin_dixon pointed this out to me yesterday, and I've been
>> > giving it quite a bit of thought since then (I have a nascent blog on
>> > the topic of how open source and standards orgs might
>> > productively/efficiently work together; follow up to
>> >
>> > http://www.sdncentral.com/education/david-meyer-reflections-opendaylig=
ht-open-source-project-brocade/2014/03).
>> >
>> > What I can say is that after seeing the kind of progress that several
>> > open source communities make (they do epitomize the best of the IETF's
>> > running code/rough consensus ethic), one does have to wonder if
>> > traditional standards making is either obsolete or in dire need of a
>> > make over. What is needed, IMO, is a reimagining of how the standards
>> > process interacts with the open source movement specifically focused
>> > on how they can compliment one another.
>>
>> [Alia] It would be very useful to have a functional model for how the
>> two can compliment each other.  We also tend to talk about open-source
>> as a single monolith - when it can have very different models for
>> accepting in changes, how and who runs the community, who is really
>> participating (open source doesn't mean non-corporate) etc.   Some of
>> what the IETF does is the architecture and requirements thinking about
>> how the solution should fit in - while some of the open-source is
>> about getting a solution implemented ASAP.   IMHO, a spiral is useful
>> with an easy way of interaction.  With I2RS, as a WG chair, I
>> suggested having experimental drafts describing solutions that were
>> being implemented - but haven't seen any.   A question is what is
>> needed to encourage the interactions.
>>
>
>
> +1
>
> I was going to mention OpenDaylight as a cooperation model.
> I think their goal is to provide implementation feedback to
> the I2RS, NETMOD, and other WGs.
>
> The corporate acceptance of open-source software is the key trend.
> I would not characterize any of these well-funded projects as
> quick-and-dirty, or "solution implemented ASAP" (any more than
> every commercial project I've worked on in my career. :-)
>
>
>> [Alia] Diversity of implementation is important as is stability of a
>> standard and it being understood how to change/upgrade for different
>> versions.  These don't come automatically via open-source.

BTW, this is one area where the open source development methodology
(and communities) doesn't operate in the same way traditional
standards orgs do (e.g., IETF). Code diversity arises *inside the
project* (in the same way consensus does). Note that this is
fundamentally different than the black box model that we have at the
IETF, and is one of the key reasons while multiple implementations are
important; we can't see anything but what's on the wire. Obviously
this is (fundamentally) not the case with open source. In addition, if
all we can see is what's on the wire then it makes very good sense to
also want to be able to verify whether a protocol is sufficiently
specified to enable interoperable implementations.

A  question one might ask to try to elucidate the difference is
whether it makes sense to ask if there are multiple interoperable
implementations of say, OpenStack? Equivalently, does it make sense to
ask what interoperates with OpenStack?

--dmm

>>
>
> Right.  Vendors have to decide to contribute engineering hours to a proje=
ct,
> similar to the decision to let engineers contribute to SDOs.
>
> Open-source software can move the "standards boundary"
> and achieve multi-vendor support at the north-bound API only.
> For example, a vendor can provide a proprietary Python plug-in
> (e.g. OpenStack Neutron) for an open-source platform, without
> standardizing the south-bound protocols.
>
>> Regards,
>> Alia
>>
>
> Andy
>


From nobody Mon Apr 14 10:14:31 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 529B01A0564 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:14:25 -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, SPF_PASS=-0.001] autolearn=ham
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 VvQnFmfjTdYA for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:14:23 -0700 (PDT)
Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0CA141A0572 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:14:22 -0700 (PDT)
Received: by mail-wi0-f174.google.com with SMTP id d1so4388746wiv.13 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:14:20 -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:content-type; bh=h1HJC7Ac25+tws4QKpIwo6RNi+/i2kmncL1kIDRDBAE=; b=JwdOkkOYNznPCcZ/8eIydnqxKqz8Px++NMpwSYj+AUbgOPDRncZj3x1oPXKc1X3ipM 1XHvKm1qvXOaf7UW7hLddd0w/mq3ifzj/DrR7F8dFwZTmyn++VJiIfHR9fV44M1V/S81 n3lxeHLDJ8/RpPdg8BawqAXN0Hdf9RsOc/5YglpH26cp1//ctBcrQAa6bpOvbRLF+qGu oGdcOqGC6A01930mibM2iwn33FM7+CYtq8MY26Ot8pIzzSz3+dkf03+aBf99dLgZnSmL ZH93IKIv3ZhJjJXHT6TZ8iK2LiBnKabPhko8r5R4R8Pwu5Qy9x9NT54zmdkdBT6gytzV raUg==
MIME-Version: 1.0
X-Received: by 10.194.90.107 with SMTP id bv11mr33401161wjb.11.1397495660009;  Mon, 14 Apr 2014 10:14:20 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 10:14:19 -0700 (PDT)
In-Reply-To: <534C067D.8080506@meetinghouse.net>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com> <534C067D.8080506@meetinghouse.net>
Date: Mon, 14 Apr 2014 10:14:19 -0700
Message-ID: <CAL0qLwa5CRwxn0V=7D84KFv9K_u5W5L+PPUXc3KPkD0YHkNo1w@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=047d7beb9ec063df7e04f703d0fa
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1Uoi-TZ0DEjMwHmeqMzv2e_h30E
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:14:25 -0000

--047d7beb9ec063df7e04f703d0fa
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 9:02 AM, Miles Fidelman
<mfidelman@meetinghouse.net>wrote:

>
> Then again, the current DMARC debacle presents a cautionary tale of more
> ad hoc approaches.
>
>
DMARC's proponents tried to come to the IETF to form a working group so
that it could undergo the rigors of standards development, and thus not be
as "ad hoc" as you're describing.  It was not accepted, on the basis that,
in essence, the work was already done so there's nothing for the IETF to
contribute.

(If I've mischaracterized this, I'm happy to be corrected.)

-MSK

--047d7beb9ec063df7e04f703d0fa
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 9:02 AM, Miles Fidelman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank=
">mfidelman@meetinghouse.net</a>&gt;</span> wrote:<br><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
Then again, the current DMARC debacle presents a cautionary tale of more ad=
 hoc approaches.<br>
<br></blockquote><div><br></div><div>DMARC&#39;s proponents tried to come t=
o the IETF to form a working group so that it could undergo the rigors of s=
tandards development, and thus not be as &quot;ad hoc&quot; as you&#39;re d=
escribing.=C2=A0 It was not accepted, on the basis that, in essence, the wo=
rk was already done so there&#39;s nothing for the IETF to contribute.<br>
<br></div><div>(If I&#39;ve mischaracterized this, I&#39;m happy to be corr=
ected.)<br></div><div><br></div><div>-MSK <br></div></div><br></div></div>

--047d7beb9ec063df7e04f703d0fa--


From nobody Mon Apr 14 10:17:33 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C896A1A0673 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:17:31 -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, SPF_PASS=-0.001] autolearn=ham
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 w9733w8rnatt for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:17:26 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 5150B1A0680 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:17:26 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hi2so4395826wib.17 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:17:23 -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:content-type; bh=FdaHOx48kBnmDFt6eukSFSKz54ZfZWBIJEHUIqUi1NI=; b=QlBCLYyIdGodeswZQtyFKdwl6aS30IAe0Qlt1kvTrMmEr1+NYfDgo29zuQC3IzMBbo AFG2tlkf0T506QoAPah7lP+ShDdKsIz8qR2/10mjNqJiI6Z4RJWQyp4/ehYBY3R24Kpr 0NzdIBIbl5Ob4DSpL8Xt5EGFZJhm185Ijw0unR8G0kqGI5Z6u/HtODqtes1Zg5grbrWr Flb0hnVf1AxLRFOvSGdm+uskfZHY/FsZWHZ1UHxqy4MZZ0Hf0/GvOflvc2cXlhqbKLYe 9CeXlpLzNz/kcUmOBOXBICFvXcMLY1eatWaHOtRvb4hHt7Wgxd7h7uUwK2ffVYwiCJRY sTaA==
MIME-Version: 1.0
X-Received: by 10.194.243.3 with SMTP id wu3mr33742174wjc.29.1397495843293; Mon, 14 Apr 2014 10:17:23 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 10:17:23 -0700 (PDT)
In-Reply-To: <19983.1397493280@sandelman.ca>
References: <CF71721A.180A9%wesley.george@twcable.com> <19983.1397493280@sandelman.ca>
Date: Mon, 14 Apr 2014 10:17:23 -0700
Message-ID: <CAL0qLwYvg=jFjtZy1fCPcNOO6CaW2bqBD=o7xpQ0d6S_Y1bb3A@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=089e013d14c45090c404f703db83
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kSVvy26JsoHDyHBKUFQ-euwCCqA
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:17:31 -0000

--089e013d14c45090c404f703db83
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 9:34 AM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

>
> For instance, had DMARC proponents and/or Yahoo, spent some time making
> sure
> that there was some running code for mailing list use, life would be
> better.
>
>
They did, and there is:

https://launchpad.net/mailman/2.1/2.1.16

-MSK

--089e013d14c45090c404f703db83
Content-Type: text/html; charset=UTF-8

<div dir="ltr">On Mon, Apr 14, 2014 at 9:34 AM, Michael Richardson <span dir="ltr">&lt;<a href="mailto:mcr+ietf@sandelman.ca" target="_blank">mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=""><br>
</div>For instance, had DMARC proponents and/or Yahoo, spent some time making sure<br>
that there was some running code for mailing list use, life would be better.<br>
<br></blockquote><div><br></div><div>They did, and there is:<br><br><a href="https://launchpad.net/mailman/2.1/2.1.16">https://launchpad.net/mailman/2.1/2.1.16</a><br><br></div><div>-MSK<br></div></div></div></div>

--089e013d14c45090c404f703db83--


From nobody Mon Apr 14 10:26:57 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18B2C1A06AF for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:26:53 -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, SPF_PASS=-0.001] autolearn=ham
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 AiNtw0Ohhyqk for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:26:51 -0700 (PDT)
Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by ietfa.amsl.com (Postfix) with ESMTP id B461B1A06A9 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:26:47 -0700 (PDT)
Received: by mail-wi0-f176.google.com with SMTP id r20so4417064wiv.9 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:26:44 -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:content-type; bh=UNFpe+IL6XUm9flau9+6jh4wLOdUPyicNUI7yOR8mr0=; b=f4cqFq86GwJeSDgsNo8nNFUWVU1hF97JaudNUiAByMBy1WdDAagdtDhe6ykqeFl21+ 7QwQ2c06gGvTUSg5S1A1/MFQNjms2mliz6Krlu1z3Bq2SMX3vYBucFnhtKVr5IDEYiqB RY9q5h36FI+Vhbp5VJ+EmwHsC5j2KHV+gAE5ypO4gab1q/yAXHJhJ/UBQyxyIWUwW7/M 4huANHUdH0bvTW2zAFUDHTje0DHSS/kKIlOs8CQ0Pyoy2Yry+d9DmL6ujz8bpp9FjkOm 8stw5UwbMGXM1MVN+jlah+WwemaRFFSffWn0/9l8qcRFiOTeJKfZB9IaiOV2+EY4queq Y8Rw==
MIME-Version: 1.0
X-Received: by 10.180.76.146 with SMTP id k18mr1405760wiw.5.1397496404799; Mon, 14 Apr 2014 10:26:44 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 10:26:44 -0700 (PDT)
In-Reply-To: <534BFA0D.7000404@meetinghouse.net>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net>
Date: Mon, 14 Apr 2014 10:26:44 -0700
Message-ID: <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=f46d04374995c8761b04f703fcbd
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LH3WvA1Gwa_oxSkuxxqvPVhdUn8
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:26:53 -0000

--f46d04374995c8761b04f703fcbd
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 8:09 AM, Miles Fidelman
<mfidelman@meetinghouse.net>wrote:

> Is it perhaps also incumbent on the folks promulgating DMARC (and its
> predecessors, and its sure-to-be successors) to work cooperatively with
> mailing list developers, rather than taking the position "nope, we break
> mailing lists, not our problem?"
>
>
The DMARC proponents did engage mailman.   Version 2.1.16 includes support
for a setting that makes the operation of the list DMARC-friendly, though
likely in a way some people will find unpalatable.  Either way, it was not
done entirely in a vacuum.


> I'm kind of coming to the conclusion that what we need to be looking at is
> defining an SMTP extension that addresses BOTH sets of concerns - and doing
> so in a cooperative manner that engages not just the community behind DKIM
> and DMARC, but also the developers and operators of mailman, sympa,
> majordomo, listserv - and ideally the sendmail, postfix, exim, qmail
> community.
>
> Dare I suggest that this calls for an IETF working group?
>
>
I mentioned in another thread that the DMARC people did come to the IETF to
ask for a working group to complete development of the work on the
standards track.  This request was denied on the grounds that DMARC was
essentially already done, and thus the IETF had nothing engineering-wise to
contribute.  There were also too few people that were not already DMARC
proponents that would commit to working on it.

(And as I said on that other thread, I'm happy to stand corrected if I've
mischaracterized any of that.)

-MSK

--f46d04374995c8761b04f703fcbd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 8:09 AM, Miles Fidelman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank=
">mfidelman@meetinghouse.net</a>&gt;</span> wrote:<br><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div>Is it perhaps also i=
ncumbent on the folks promulgating DMARC (and its predecessors, and its sur=
e-to-be successors) to work cooperatively with mailing list developers, rat=
her than taking the position &quot;nope, we break mailing lists, not our pr=
oblem?&quot;<br>
<br></div></blockquote><div><br></div><div>The DMARC proponents did engage =
mailman. =C2=A0 Version 2.1.16 includes support for a setting that makes th=
e operation of the list DMARC-friendly, though likely in a way some people =
will find unpalatable.=C2=A0 Either way, it was not done entirely in a vacu=
um.<br>
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div></div><div=
>
<br>
I&#39;m kind of coming to the conclusion that what we need to be looking at=
 is defining an SMTP extension that addresses BOTH sets of concerns - and d=
oing so in a cooperative manner that engages not just the community behind =
DKIM and DMARC, but also the developers and operators of mailman, sympa, ma=
jordomo, listserv - and ideally the sendmail, postfix, exim, qmail communit=
y.<br>

<br>
Dare I suggest that this calls for an IETF working group?<div class=3D"HOEn=
Zb"><div class=3D"h5"><br></div></div></div></blockquote><div><br></div><di=
v>I mentioned in another thread that the DMARC people did come to the IETF =
to ask for a working group to complete development of the work on the stand=
ards track.=C2=A0 This request was denied on the grounds that DMARC was ess=
entially already done, and thus the IETF had nothing engineering-wise to co=
ntribute.=C2=A0 There were also too few people that were not already DMARC =
proponents that would commit to working on it.<br>
<br></div><div>(And as I said on that other thread, I&#39;m happy to stand =
corrected if I&#39;ve mischaracterized any of that.)<br><br></div><div>-MSK=
<br></div></div></div></div>

--f46d04374995c8761b04f703fcbd--


From nobody Mon Apr 14 10:29:00 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D593F1A01ED for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:28:58 -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, SPF_PASS=-0.001] autolearn=ham
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 3EwLuALff8Nt for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:28:54 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 2BEE31A065D for <ietf@ietf.org>; Mon, 14 Apr 2014 10:28:54 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id z2so4417313wiv.0 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:28:51 -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:content-type; bh=2Q6lUIjEcElqMLEmMSKJQ58X6s1daRb26Jl3hXXA01k=; b=qYX+lUiwHchmtLfAx/TPwNKhqG9L6PXzpXZDS5nYEYeeOui5JdJJ7Od8vQOkPoSLMi /umH9vrg06qCQjDEM39C4zbwXN00W2Rm+uOvlH1WDK2RGVGi/nwgsIiynoXfUmq+1t2f 0roEzcnlFgiJzog+LBhSQmV+HdegJ4gxQtxMYc9DrO6/1+asR/WPYT+xqUNpoZN5YmZq SgNsiDuwdkzGAluLKyxqdbbT3ARcB2tBZLeNan3XuEe13+Up008jwzTm5VMYc8dw/Vpc 6mxkS886dYQz3LAVqACYialCWZo4W3O/Y8NJ2ni6onC0yINQ1hRfUhybuJZ6HxSUPuT6 ijbg==
MIME-Version: 1.0
X-Received: by 10.180.36.101 with SMTP id p5mr10441866wij.8.1397496531209; Mon, 14 Apr 2014 10:28:51 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 10:28:51 -0700 (PDT)
In-Reply-To: <534B4E97.2050000@meetinghouse.net>
References: <20140414024956.26078.qmail@joyce.lan> <534B4E97.2050000@meetinghouse.net>
Date: Mon, 14 Apr 2014 10:28:51 -0700
Message-ID: <CAL0qLwYHP-rVF5TmEH2_kTZ7bDnxms7md=Y8Voef9OyPD4Bj8Q@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=e89a8f50345e5152c604f7040442
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Tzp7tvQ_qnCaXp55OlZBK4l7bUw
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:28:59 -0000

--e89a8f50345e5152c604f7040442
Content-Type: text/plain; charset=UTF-8

On Sun, Apr 13, 2014 at 7:57 PM, Miles Fidelman
<mfidelman@meetinghouse.net>wrote:

>
> It strikes me that the real way to address some of these issues is to add
> a few new headers to SMTP - to get rid of the overloading of the From: and
> Reply-to: headers associated with mailing lists.  An SMTP extension that
> would absorb some of the well-known and well-understood functions of list
> software.
>
> [...]
>

I made that same suggestion on a different list.  It seems as if that
suggestion was made long ago and the debate reached "religious"
proportions.  One of the usual answers emerged, which was that it'll take
forever to get this deployed with sufficient ubiquity as to be helpful.

I'm guessing that means we shouldn't try.

-MSK

--e89a8f50345e5152c604f7040442
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sun, Apr 13, 2014 at 7:57 PM, Miles Fidelman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank=
">mfidelman@meetinghouse.net</a>&gt;</span> wrote:<br><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><br>=
</div></div>
It strikes me that the real way to address some of these issues is to add a=
 few new headers to SMTP - to get rid of the overloading of the From: and R=
eply-to: headers associated with mailing lists. =C2=A0An SMTP extension tha=
t would absorb some of the well-known and well-understood functions of list=
 software. <br>
<br>[...]<br></blockquote><div><br></div><div>I made that same suggestion o=
n a different list.=C2=A0 It seems as if that suggestion was made long ago =
and the debate reached &quot;religious&quot; proportions.=C2=A0 One of the =
usual answers emerged, which was that it&#39;ll take forever to get this de=
ployed with sufficient ubiquity as to be helpful.<br>
<br>I&#39;m guessing that means we shouldn&#39;t try.<br><br></div><div>-MS=
K<br></div></div></div></div>

--e89a8f50345e5152c604f7040442--


From nobody Mon Apr 14 10:29:42 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D621A06B1 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:29:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.702
X-Spam-Level: 
X-Spam-Status: No, score=-98.702 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 Bsa1Fqw01Kqu for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:29:36 -0700 (PDT)
Received: from winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 783491A06AF for <ietf@ietf.org>; Mon, 14 Apr 2014 10:29:36 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5299; t=1397496563; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=l8a3d5dz95sdyc6plerz9WZ353Y=; b=EhIxgDhQr2a+kL15VCt5 P957CDl6E39ku4pmiDsvlHSRSsOQsmYF+23yaQo2EepUvpp4poOc1z/mH9zKsTDV AFzrBqQ2Jj5TuJh40K/6ttgDBLk3Pb7nu7rI2U6S1Lb8wMikK9crvtMPggwxbUQ7 jKfV59j8u7UnnCUlMOzmQr0=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 14 Apr 2014 13:29:23 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 605140795.14763.2756; Mon, 14 Apr 2014 13:29:22 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5299; t=1397496497; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=+fb1Sfb LAcEOC/HgWXuVtj7ZyFCA4YdZEq/ySXohsjo=; b=js2bdXKD7fJiy+Z8ziFZxRC noex2E1NURrxu8+VCdT/V0/JzKHLQvqAJBL99z6gbdDWg1ZBEtBM5qmM2Q/BEHyf 6ThfskDdV5KyC7fPJn+kqWFAisDcocAA7TvtDOf/WTPNF2nMF1d8rw0+2AL6zM99 DXaRZ/UAHNVPXp2rjM60=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 14 Apr 2014 13:28:17 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 624672859.9.10176; Mon, 14 Apr 2014 13:28:16 -0400
Message-ID: <534C1AEE.3080003@isdg.net>
Date: Mon, 14 Apr 2014 13:29:18 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Miles Fidelman <mfidelman@meetinghouse.net>, ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net>
In-Reply-To: <53499A5E.9020805@meetinghouse.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0XyLhP4SauM0rnGiCc3aBWp8jDU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:29:41 -0000

This DMARC issue has finally hit our support forum today!

-------- Original Message --------
Subject: [WINServer] Lists, Yahoo and DMARC
Date: 	 Mon, 14 Apr 2014 12:51:38 -0400
From: 	 Kevin M. Agard <lists@agard.org>
Reply-To: <WINServer@winserver.com>
To: 	 WINServer@winserver.com


Is anyone else running the wcListserver seeing bounces on messages to
Yahoo, MSN and Comcast due to these provider's DMARC configs??

What I am seeing is that any message originating from a @yahoo.com
address is being bounced by these domains with a Â“554 5.7.9: Message not
accepted for policy reasonsÂ” error messages.

Interestingly enough, although Yahoo, MSN and Comcast all bounce these
messages, it is only messages from Yahoo that bounce. Messages
originating from MSN and Comcast make it through fine.

KMA
------------------------------------------



On 4/12/2014 3:56 PM, Miles Fidelman wrote:
> Folks,
>
> We (really I) support perhaps 2 dozen small email lists, for a bunch
> of community groups (PTOs, churches, neighborhood groups) - mostly the
> legacy of previously running a small hosting firm, and still having
> the machines sitting in a data center.  The kinds of groups with lots
> of non-technical users who have email accounts on Yahoo, hotmail, AOL,
> Comcast, and such.  The lists range in size from tiny (5 person boards
> of directors) to maybe 1000 (high school parents).
>
> Yahoo's implementation of it's new DMARC policy has been an absolute
> disaster.  Kind of messes things up when a few days before tax filings
> are due, and in parallel with the Heartbleed mess, (not to mention the
> work that pays the bills), roughly 1/3 of the addresses on almost all
> of the lists start bouncing mail from yahoo addresses - particularly
> when yahoo's postmaster didn't have a clue what was going on (my
> initial thought was - oh heck, need to get back on their whitelist).
> Luckily gmail seems not to be honoring the Yahoo's p=reject policy, at
> least so far, or things would be a LOT worse.
>
> Still trying to figure out a reasonable fix for this, as it looks like
> lots of other listmasters are trying to do - and doesn't help that I'm
> running a less common list package (sympa).
>
> Anyway - one of my reactions to this is that something is really
> broken about the process by which DMARC and Yahoo's policy have been
> foisted on the larger Internet community - and in particular IETF's
> role or lack thereof.  Specifically:
>
> - DMARC is an ad-hoc group that assembled with a "common goal was to
> develop an operational specification to be introduced to the IETF for
> standardization"
> (http://dmarc.org/about.html)
>
> - DMARC.org defines the "DMARC Base Specification" with a link to
> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an IETF
> document
>
> - the referenced document is an informational  Internet draft, that
> expires in October of this year, that starts with "This memo presents
> a proposal for a scalable mechanism by which a mail sending
> organization can express,.
>
> - It's also being presented as mature - through such publicity
> statements as "DMARC standard now protects almost two-thirds of the
> world's 3.3 billion consumer mailboxes worldwide"
> (http://dmarc.org/news/press_release_20140218.html)
>
> In essence, DMARC is being represented as a mature, standards-track
> IETF specification - with the implication that it's been widely
> vetted, and is marching through the traditional experimental ->
> optional -> recommended -> mandatory steps that IETF standards go
> through.
>
> In reality:
> - DMARC was developed by a tiny number of people, all of whom work for
> very large ISPs
> - as far as I can tell, all input from the broader community - notably
> mailing list developers and operators was roundly ignored or dismissed
> (the transcript is really clear on this)
> - while DMARC is at least partially tested, deploying and honoring
> "p=reject" messages is brand new, and has wreaked tremendous damage
> across the net
> - as far as I can tell, those who are behind DMARC are taking the
> position "it's not our problem" (see discussions on
> dmarc-discuss@dmarc.org and dmarc@ietf.org) - and there is nary a
> Yahoo representative to be seen anywhere
>
>  From an operational perspective, this is akin to a large player
> publishing a corrupt nameserver database or routing update - and then
> actively resting attempts to clean up the mess (which, in effect is
> what Yahoo did by updating their DMARC record to p=reject).
>
> The situation strikes me as incredibly perverse and broken - the more
> so that the perpetrators are presenting this as blessed by the IETF
> standards process.
>
> It strikes me that IETF should weigh in on this in a formal fashion -
> if only to make it very clear that IETF is not responsible for this
> debacle, and perhaps to exert some moral influence on the perpetrators
> to back off and help clean up the mess they've created.
>
> On a broader scope - this sort of points out a really big hole in our
> consensus governance process - when one bad actor can inflict damage
> across the entire Internet, apparently, with impunity.
>
> Miles Fidelman
>

-- 
HLS



From nobody Mon Apr 14 10:30:48 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20E5D1A06B0 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:30:47 -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, SPF_PASS=-0.001] autolearn=ham
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 ps-tj_7VZfie for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:30:46 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id C22E41A06AE for <ietf@ietf.org>; Mon, 14 Apr 2014 10:30:45 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id cc10so4421904wib.14 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:30:42 -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:content-type; bh=wCYZylI8jaUw5SgoIv/npnTWu0eGshUKlQmEDz29Eqw=; b=Iq14QU6F0UWnqit8Sn8Wdlw+wQCjyFnZNjH3h1OLQIWrTB9dAqQ4Z9iGMTlkyoJroM phtI86gia9RoOkjk3RzsymL4vEeBtCvk8d4hhh9HnMmnI5SxCDRmyRzu2s/Rxs2W78lB evCyDt9dcsY981aA8rAX7vZ3wz8gBr7D5ErYSgPMOAYoQqnKqYZVtI8vliTZ8bOhcxVS kkUtaNd+k6CL/bEYuEjIQ2NIjSUTamGXzsjN3GWssBcVIxQx7+3Y9SbdeeW0sbtahCl4 u0wO28cYr/Y7XqRnCAyiadeVap6IBgW51eObqxMwkEJlgybPshIfwwF8gDXcHkoGNC9d QB6g==
MIME-Version: 1.0
X-Received: by 10.194.89.168 with SMTP id bp8mr1488630wjb.73.1397496642300; Mon, 14 Apr 2014 10:30:42 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 10:30:42 -0700 (PDT)
In-Reply-To: <01P6EEIPML6600004W@mauve.mrochek.com>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com>
Date: Mon, 14 Apr 2014 10:30:42 -0700
Message-ID: <CAL0qLwYGENn5PT26awrZ_k8D4C5VW2tY1RMSb3mxxwpA9m5rjA@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Content-Type: multipart/alternative; boundary=047d7bf10a1cf12c1404f7040a1a
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JxL7churfR2rx9IChjbq3D5JetY
Cc: John R Levine <johnl@taugh.com>, IETF general list <ietf@ietf.org>, "Robin H. Johnson" <robbat2@gentoo.org>, Elizabeth Zwicky <zwicky@yahoo-inc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:30:47 -0000

--047d7bf10a1cf12c1404f7040a1a
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 8, 2014 at 9:52 AM, <ned+ietf@mauve.mrochek.com> wrote:

> Actually, mailing lists *can* implement DMARC, just not that way: Do a
> DMARC
> check on all incoming messages, and if the domain policy is one that is
> incompatible with the list's own policies - whatever they are - either
> change
> the list's policies to conform to that message or reject it outright,
> preferably with a nasty "find another a better mail provider" sort of
> message.
>
> If the IETF wants to take a leadership position in regards to this issue,
> perhaps someone could set this up.
>

The DKIM WG discussed this idea in RFC 6377.

-MSK

--047d7bf10a1cf12c1404f7040a1a
Content-Type: text/html; charset=UTF-8

<div dir="ltr">On Tue, Apr 8, 2014 at 9:52 AM,  <span dir="ltr">&lt;<a href="mailto:ned+ietf@mauve.mrochek.com" target="_blank">ned+ietf@mauve.mrochek.com</a>&gt;</span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Actually, mailing lists *can* implement DMARC, just not that way: Do a DMARC<br>
check on all incoming messages, and if the domain policy is one that is<br>
incompatible with the list&#39;s own policies - whatever they are - either change<br>
the list&#39;s policies to conform to that message or reject it outright,<br>
preferably with a nasty &quot;find another a better mail provider&quot; sort of message.<br>
<br>
If the IETF wants to take a leadership position in regards to this issue,<br>
perhaps someone could set this up.<br></div></blockquote><div><br></div><div>The DKIM WG discussed this idea in RFC 6377.<br><br></div><div>-MSK<br></div></div></div></div>

--047d7bf10a1cf12c1404f7040a1a--


From nobody Mon Apr 14 10:37:04 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 277221A069E for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:37:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.281
X-Spam-Level: 
X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 lc_YRphdElQs for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:36:58 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 039641A06C7 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:36:57 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 1FD28CC0B5 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:36:55 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zO8HOIe26EHg for <ietf@ietf.org>; Mon, 14 Apr 2014 13:36:50 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id E0ECBCC0A7 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:36:49 -0400 (EDT)
Message-ID: <534C1CB1.2070308@meetinghouse.net>
Date: Mon, 14 Apr 2014 13:36:49 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <19983.1397493280@sandelman.ca> <CAL0qLwYvg=jFjtZy1fCPcNOO6CaW2bqBD=o7xpQ0d6S_Y1bb3A@mail.gmail.com>
In-Reply-To: <CAL0qLwYvg=jFjtZy1fCPcNOO6CaW2bqBD=o7xpQ0d6S_Y1bb3A@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Y2uM7oh_2vt9GS57hN2-arfED9c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:37:02 -0000

Murray S. Kucherawy wrote:
> On Mon, Apr 14, 2014 at 9:34 AM, Michael Richardson 
> <mcr+ietf@sandelman.ca <mailto:mcr+ietf@sandelman.ca>> wrote:
>
>
>     For instance, had DMARC proponents and/or Yahoo, spent some time
>     making sure
>     that there was some running code for mailing list use, life would
>     be better.
>
>
> They did, and there is:
>
> https://launchpad.net/mailman/2.1/2.1.16
>
>

Well... an awful lot of folks run other list software - listserve, 
listproc, majordomo, ezmlm, sympa (what I run) - it might have 
represented good citizenship if Yahoo had contributed patches to, say, 
the top half dozen open-source list management packages, and had 
discussions with the commercial vendors - before propagating p=reject.

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 10:42:03 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E4311A069E for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.423
X-Spam-Level: *
X-Spam-Status: No, score=1.423 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 5hk-fKNETG4X for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:41:56 -0700 (PDT)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 958AD1A01F8 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:41:56 -0700 (PDT)
Received: by mail-yh0-f43.google.com with SMTP id b6so8381213yha.30 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:41:54 -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:from:date:message-id :subject:to:cc:content-type; bh=vh0QTjl87YgntcfRO8wsYSpgARFTz7oN+f9uM63Jh34=; b=aEtxjUC5FQ7QopZuYk6MysJKab1nhKFAgroq5PgjPTDmy7k7W2M3jsS7Wa6SaKoKp9 oHU5hidRlYO2+Z0OcTErA2ZQ5v7G92+xWhq85+jgpUf+XrMsMdAi2YnDS9/zbwL8RG+d X1ciiZD29H4dBeXI+yJ3LhYccecbXvtR6wGecdJezLOvCyO8EskWwVj549pGyB5i0fzg 0lNJem+VTzsjZfCnhagMJyZz6JXaOExQa55VX9WKI/8VNHfvWaMGLSQvAUNKZ89O1flx oQ5tmNi1G+C48EMGvvrkl+l9TbgPP5xnS3q17CSSgW+RYNMWqcdaPnlLCGpoLehix6yV 1aLQ==
X-Received: by 10.236.157.167 with SMTP id o27mr4709128yhk.127.1397497314018;  Mon, 14 Apr 2014 10:41:54 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Mon, 14 Apr 2014 10:41:13 -0700 (PDT)
In-Reply-To: <534C0078.3070808@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net>
From: Dick Franks <rwfranks@acm.org>
Date: Mon, 14 Apr 2014 18:41:13 +0100
X-Google-Sender-Auth: IXx07FvPvuMbWv5nGUKe136lQi0
Message-ID: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=20cf303f676cfa0c3804f7043229
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CTLjv-r8Ym82BFkbSVOKX2Qmhh4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:42:00 -0000

--20cf303f676cfa0c3804f7043229
Content-Type: text/plain; charset=UTF-8

On 14 April 2014 16:36, Miles Fidelman <mfidelman@meetinghouse.net> wrote:

> Dick Franks wrote:
>
>
>> On 13 April 2014 00:35, <ned+ietf@mauve.mrochek.com <mailto:
>> ned+ietf@mauve.mrochek.com>> wrote:
>> [snip]
>>
>>    It is inappropriate to use Internet-Drafts as reference
>>    material or to cite them other than as "work in progress."
>>
>> An implementation based on I-D reference material is therefore no better
>> than "work in progress".
>>
>> The blame for this debacle lies squarely with Yahoo, and its inadequate
>> engineering change management.
>>
>>
> That's all in the fine print.


Indeed, but with blame so firmly attached, list operators need not be too
concerned about inconveniencing Yahoo customers by rejecting posts. Those
most affected will doubtless vote with their metaphorical feet.




> - allowing someone to represent something as an IETF standard carries a
> risk to IETF's standing, effectiveness, and credibility as the Internet's
> standards body (ISO tends to get very upset if someone claims to be ISO9000
> certified, but isn't; Xerox sends lawyers after competitors who refer to
> their copiers as "xerox machines")
>

Are you suggesting that IETF brings an action for trademark infringement?

Against whom?


A more pragmatic, less expensive, and publicly visible expression of IETF
displeasure might be to expunge all versions of the offending I-D from IETF
document store and refuse to publish any subsequent version until the
unwarranted claims made for it are retracted.

To be effective, that needs to be done now, while the iron is still hot;
not after the usual 3-month email debate about the diplomatic niceties.

--20cf303f676cfa0c3804f7043229
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div dir=3D"ltr"><span></s=
pan><br></div></div>
<br><div class=3D"gmail_quote">On 14 April 2014 16:36, Miles Fidelman <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_b=
lank">mfidelman@meetinghouse.net</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

Dick Franks wrote:<div><div class=3D"h5"><br><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>
<br>
On 13 April 2014 00:35, &lt;<a href=3D"mailto:ned%2Bietf@mauve.mrochek.com"=
 target=3D"_blank">ned+ietf@mauve.mrochek.com</a> &lt;mailto:<a href=3D"mai=
lto:ned%2Bietf@mauve.mrochek.com" target=3D"_blank">ned+ietf@mauve.<u></u>m=
rochek.com</a>&gt;&gt; wrote:<br>


[snip]<br>
<br>
=C2=A0=C2=A0 It is inappropriate to use Internet-Drafts as reference<br>

=C2=A0 =C2=A0material or to cite them other than as &quot;work in progress.=
&quot;<br>
<br>
An implementation based on I-D reference material is therefore no better th=
an &quot;work in progress&quot;.<br>
<br>
The blame for this debacle lies squarely with Yahoo, and its inadequate eng=
ineering change management.<br>
<br>
</blockquote>
<br></div></div>
That&#39;s all in the fine print.</blockquote><div><br></div><div>Indeed, b=
ut with blame so firmly attached, list operators need not be too concerned =
about inconveniencing Yahoo customers by rejecting posts. Those most affect=
ed will doubtless vote with their metaphorical feet.<br>

<br><br></div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- allowing someone to represent something as an IETF standard carries a ris=
k to IETF&#39;s standing, effectiveness, and credibility as the Internet&#3=
9;s standards body (ISO tends to get very upset if someone claims to be ISO=
9000 certified, but isn&#39;t; Xerox sends lawyers after competitors who re=
fer to their copiers as &quot;xerox machines&quot;)<br>

</blockquote><div><br></div><div>Are you suggesting that IETF brings an act=
ion for trademark infringement? <br><br></div><div>Against whom?<br><br></d=
iv><div><br></div><div>A more pragmatic, less expensive, and publicly visib=
le expression of IETF displeasure might be to expunge all versions of the o=
ffending I-D from IETF document store and refuse to publish any subsequent =
version until the unwarranted claims made for it are retracted.<br>

<br></div><div>To be effective, that needs to be done now, while the iron i=
s still hot; not after the usual 3-month email debate about the diplomatic =
niceties.<br></div><div class=3D"h5"><br><br>
<br>
</div></div><br></div></div>

--20cf303f676cfa0c3804f7043229--


From nobody Mon Apr 14 10:53:52 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9181D1A0208 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:53:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.301
X-Spam-Level: *
X-Spam-Status: No, score=1.301 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 gFp5o6JBnekt for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:53:46 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1F1AF1A01FC for <ietf@ietf.org>; Mon, 14 Apr 2014 10:53:45 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id cc10so4453728wib.14 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:53:42 -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:content-type; bh=Ev1CngUV9hdhEOR2e3tkJljhBUvl5nRToY4eQg0G3xU=; b=AynKSd5qOcUimTKCOaizYBrJkeYD1KvknOzmRqth8GehBsK7HcZeiQ2qRQrn0ERA6t r04o9N+40myq6xyo+wvjN1TCQrQM6nhiJQzauHdUvP26WdyYnktbOZIpvN/ND4xRlaMs x4oe29XJxj/G6+fSdk1H4vKTBTv6foGg9JvfzTcJ7q6aRjFTP6nq3l4aQNANZq3T/S/+ AoB3vVS8dIpF/7ZhI9nOJu1Mvi85/3+DBQWe4wLrEXbRZBICCVACfb8eJuErX8j+awJ5 /s5muict2cIJr4jtaUFF5YBaUxgp34zTaARcI1t1z3SgRAJYVCkCgdBRmuiI7U+1OuZc rSEg==
MIME-Version: 1.0
X-Received: by 10.180.84.129 with SMTP id z1mr10523391wiy.8.1397498022765; Mon, 14 Apr 2014 10:53:42 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 10:53:42 -0700 (PDT)
In-Reply-To: <01P6L9JZF5SC00004W@mauve.mrochek.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com>
Date: Mon, 14 Apr 2014 10:53:42 -0700
Message-ID: <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Content-Type: multipart/alternative; boundary=f46d043bdec038aa7304f7045d81
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BHfQd2yn_x0fukFawC7gwKggsb8
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:53:47 -0000

--f46d043bdec038aa7304f7045d81
Content-Type: text/plain; charset=UTF-8

On Sat, Apr 12, 2014 at 4:35 PM, <ned+ietf@mauve.mrochek.com> wrote:

> The underlying technical issue is that the two technologies DMARC is built
> on -
> DKIM and SPF - both attach additional/restrictive semantics to
> longstanding mail
> system fields. (Broadly speaking, From: for DKIM and MAIL FROM for SPF.)
>

Something's amiss here.  What new semantics does DKIM attach to From:?  As
far as I know, it only requires that the field be signed.  It doesn't
require that it be interpreted in a particular way or that it contain any
particular value.


> It goes on to discuss the use of p=reject with domains that only send
> transactional. AFAICT there is no discussion of when *not* to use
> p=reject, and
> why. Nor, for that matter is there substantive discussion of mailing_list,
> and why it's not a general solution to the problems caused by p=reject.
>

Yes, that's useful advice for a future revision.


> Like it or not, the IETF published a draft that defines certain mechanisms
> which, if used improperly by a large provider, cause serious problems for a
> large number of people. The text describing the consequences of the use of
> those mechansisms in the drafts is, IMO, entirely inadequate.
>

It's the same document that was posted on other web sites for some time,
and was in use by a number of operators (including Yahoo) long before it
went into the datatracker.

As it's only a draft, there's ample opportunity to make such improvements.

Also: By "the IETF published a draft", are you talking about an RFC, or the
DMARC base draft?  It seems extreme to lay blame on the IETF in general
merely for having an open mechanism by which to post a draft for all to see
and discuss.  A "Request For Comment", as it were.  Are you suggesting that
process should be closed or moderated somehow?


> And it's not like we didn't know. As others have pointed out, this issue
> existed in the earlier ADSP proposal. It was given insufficient attention
> there
> as well.
>

As with any draft, its content is only as good as its contributions and the
reviews it got.


> Of course the IETF can fall back on the usual excuses, including, but not
> limited to:
>
>     Yahoo, of all ISPs, should have known better
>     We don't tell people what to do
>     It was just a draft
>     It was never intended to be a standard
>     We're not the Internet Protocol Police
>     etc.
>
> I'm sorry, but this time none of these dogs are hunting for me. An
> attractive
> nuisance is an attractive nuisance, and this is what the IETF has, albeit
> with
> the best of intentions, managed to create.
>

I would add to this that, by its ultimate inaction in the face of a
protracted period of abuse and attempts by participants to solve that
problem within its procedures, the IETF has abdicated any authority it may
have had.

The real question we should be discussing is what options the IETF has to
> try
> and address this.
>

I certainly agree with that.

-MSK

--f46d043bdec038aa7304f7045d81
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Apr 12, 2014 at 4:35 PM,  <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:ned+ietf@mauve.mrochek.com" target=3D"_blank">ned+ietf@mauv=
e.mrochek.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">The underlying technical =
issue is that the two technologies DMARC is built on -<br>
DKIM and SPF - both attach additional/restrictive semantics to longstanding=
 mail<br>
system fields. (Broadly speaking, From: for DKIM and MAIL FROM for SPF.)<br=
></blockquote><div>=C2=A0</div><div>Something&#39;s
 amiss here.=C2=A0 What new semantics does DKIM attach to From:?=C2=A0 As f=
ar as I
 know, it only requires that the field be signed.=C2=A0 It doesn&#39;t requ=
ire=20
that it be interpreted in a particular way or that it contain any=20
particular value.<br><div>=C2=A0<br></div></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">
It goes on to discuss the use of p=3Dreject with domains that only send<br>
transactional. AFAICT there is no discussion of when *not* to use p=3Drejec=
t, and<br>
why. Nor, for that matter is there substantive discussion of mailing_list,<=
br>
and why it&#39;s not a general solution to the problems caused by p=3Drejec=
t.<br></blockquote><div><div><br></div><div>Yes, that&#39;s useful advice f=
or a future revision.<br></div>=C2=A0
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Like it or not, the IETF published a draft that defines certain mechanisms<=
br>
which, if used improperly by a large provider, cause serious problems for a=
<br>
large number of people. The text describing the consequences of the use of<=
br>
those mechansisms in the drafts is, IMO, entirely inadequate.<br></blockquo=
te><div><br></div><div>It&#39;s the same document that was posted on other =
web sites for some time, and was in use by a number of operators (including=
 Yahoo) long before it went into the datatracker.<br>
<br></div><div>As it&#39;s only a draft, there&#39;s ample opportunity to m=
ake such improvements.<br><br><div>Also: By &quot;the IETF published a draf=
t&quot;,=20
are you talking about an RFC, or the DMARC base draft?=C2=A0 It seems extre=
me
 to lay blame on the IETF in general merely for having an open mechanism
 by which to post a draft for all to see and discuss.=C2=A0 A &quot;Request=
 For=20
Comment&quot;, as it were.=C2=A0 Are you suggesting that process should be =
closed or moderated somehow?<br></div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">

And it&#39;s not like we didn&#39;t know. As others have pointed out, this =
issue<br>
existed in the earlier ADSP proposal. It was given insufficient attention t=
here<br>
as well.<br></blockquote><div><br></div><div>As with any draft, its content=
 is only as good as its contributions and the reviews it got.<br>=C2=A0<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">

Of course the IETF can fall back on the usual excuses, including, but not<b=
r>
limited to:<br>
<br>
=C2=A0 =C2=A0 Yahoo, of all ISPs, should have known better<br>
=C2=A0 =C2=A0 We don&#39;t tell people what to do<br>
=C2=A0 =C2=A0 It was just a draft<br>
=C2=A0 =C2=A0 It was never intended to be a standard<br>
=C2=A0 =C2=A0 We&#39;re not the Internet Protocol Police<br>
=C2=A0 =C2=A0 etc.<br>
<br>
I&#39;m sorry, but this time none of these dogs are hunting for me. An attr=
active<br>
nuisance is an attractive nuisance, and this is what the IETF has, albeit w=
ith<br>
the best of intentions, managed to create.<br></blockquote><div><br></div><=
div>I would add to this that, by its ultimate inaction in the face of a pro=
tracted period of abuse and attempts by participants to solve that problem =
within its procedures, the IETF has abdicated any authority it may have had=
.<br>
</div><div><div><br></div></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex">
The real question we should be discussing is what options the IETF has to t=
ry<br>
and address this.<br>
<span class=3D""></span></blockquote><div><br></div><div>I certainly agree =
with that.<br><br>-MSK <br></div></div></div></div>

--f46d043bdec038aa7304f7045d81--


From nobody Mon Apr 14 10:58:19 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E4701A01FC for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:58:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 JRhxG6dkefTK for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:58:10 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 66E5F1A01F8 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:58:10 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id ACC5ACC0BF; Mon, 14 Apr 2014 13:58:07 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id UdydSpRGCxln; Mon, 14 Apr 2014 13:57:59 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id AC53ECC0BE; Mon, 14 Apr 2014 13:57:58 -0400 (EDT)
Message-ID: <534C21A6.8080901@meetinghouse.net>
Date: Mon, 14 Apr 2014 13:57:58 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan>	<534B524F.4050206@dcrocker.net>	<alpine.BSF.2.00.1404132327560.26258@joyce.lan>	<E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com>	<alpine.BSF.2.00.1404132346420.26386@joyce.lan>	<1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com>	<534B9760.90301@dougbarton.us>	<534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
In-Reply-To: <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8JlYP5ZVeSGUZE_d5nvexSi4hHI
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:58:15 -0000

Murray S. Kucherawy wrote:
> On Mon, Apr 14, 2014 at 8:09 AM, Miles Fidelman 
> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>
>     Is it perhaps also incumbent on the folks promulgating DMARC (and
>     its predecessors, and its sure-to-be successors) to work
>     cooperatively with mailing list developers, rather than taking the
>     position "nope, we break mailing lists, not our problem?"
>
>
> The DMARC proponents did engage mailman.   Version 2.1.16 includes 
> support for a setting that makes the operation of the list 
> DMARC-friendly, though likely in a way some people will find 
> unpalatable.  Either way, it was not done entirely in a vacuum.
>
>
>     I'm kind of coming to the conclusion that what we need to be
>     looking at is defining an SMTP extension that addresses BOTH sets
>     of concerns - and doing so in a cooperative manner that engages
>     not just the community behind DKIM and DMARC, but also the
>     developers and operators of mailman, sympa, majordomo, listserv -
>     and ideally the sendmail, postfix, exim, qmail community.
>
>     Dare I suggest that this calls for an IETF working group?
>
>
> I mentioned in another thread that the DMARC people did come to the 
> IETF to ask for a working group to complete development of the work on 
> the standards track.  This request was denied on the grounds that 
> DMARC was essentially already done, and thus the IETF had nothing 
> engineering-wise to contribute.  There were also too few people that 
> were not already DMARC proponents that would commit to working on it.
>
> (And as I said on that other thread, I'm happy to stand corrected if 
> I've mischaracterized any of that.)
>
> -MSK


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 10:59:11 2014
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 481891A0683 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:59:10 -0700 (PDT)
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] autolearn=ham
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 hRy943pYk3mv for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 10:59:06 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 698621A01F8 for <ietf@ietf.org>; Mon, 14 Apr 2014 10:59:04 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3EHwvde015969 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 14 Apr 2014 10:59:00 -0700
Message-ID: <534C216A.8090104@bbiw.net>
Date: Mon, 14 Apr 2014 10:56:58 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
In-Reply-To: <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Mon, 14 Apr 2014 10:59:00 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6yX2nmuOqhZzpDO0GrCqUwxIPzQ
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 17:59:10 -0000

On 4/14/2014 10:53 AM, Murray S. Kucherawy wrote:
> Something's amiss here.  What new semantics does DKIM attach to From:?
> As far as I know, it only requires that the field be signed.  It doesn't
> require that it be interpreted in a particular way or that it contain
> any particular value.


Correct.

DKIM does not carry any semantics about message content, other than the 
DKIM-Signature field.

A side-effect of the DKIM mechanism is some transit data integrity 
between signing and validation, but that has nothing to do with content 
'validity'.

DMARC, on the other hand, defines an "alignment" between the 
rfc5322.From field domain name and the domain name in the DKIM d= value 
and or (for SPF) the domain name in the rfc5321.MailFrom command.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 14 11:01:22 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BB3E1A0697 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:01:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 HTZ7DsnCm8P8 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:01:18 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3F2711A06AC for <ietf@ietf.org>; Mon, 14 Apr 2014 11:01:18 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id BBE93CC0BE for <ietf@ietf.org>; Mon, 14 Apr 2014 14:01:15 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id G5BQd1fDGtek for <ietf@ietf.org>; Mon, 14 Apr 2014 14:01:07 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id D5D6ECC0BF for <ietf@ietf.org>; Mon, 14 Apr 2014 14:01:06 -0400 (EDT)
Message-ID: <534C2262.1070507@meetinghouse.net>
Date: Mon, 14 Apr 2014 14:01:06 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com>
In-Reply-To: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QgAm2Zb-HBQXoFStGF5PjKGsQcY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 18:01:19 -0000

Dick Franks wrote:
>
>
> On 14 April 2014 16:36, Miles Fidelman <mfidelman@meetinghouse.net 
> <mailto:mfidelman@meetinghouse.net>> wrote:
>
>     Dick Franks wrote:
>
>
>         On 13 April 2014 00:35, <ned+ietf@mauve.mrochek.com
>         <mailto:ned%2Bietf@mauve.mrochek.com>
>         <mailto:ned+ietf@mauve.mrochek.com
>         <mailto:ned%2Bietf@mauve.mrochek.com>>> wrote:
>         [snip]
>
>            It is inappropriate to use Internet-Drafts as reference
>            material or to cite them other than as "work in progress."
>
>         An implementation based on I-D reference material is therefore
>         no better than "work in progress".
>
>         The blame for this debacle lies squarely with Yahoo, and its
>         inadequate engineering change management.
>
>
>     That's all in the fine print.
>
>
> Indeed, but with blame so firmly attached, list operators need not be 
> too concerned about inconveniencing Yahoo customers by rejecting 
> posts. Those most affected will doubtless vote with their metaphorical 
> feet.
>
>
>
>     - allowing someone to represent something as an IETF standard
>     carries a risk to IETF's standing, effectiveness, and credibility
>     as the Internet's standards body (ISO tends to get very upset if
>     someone claims to be ISO9000 certified, but isn't; Xerox sends
>     lawyers after competitors who refer to their copiers as "xerox
>     machines")
>
>
> Are you suggesting that IETF brings an action for trademark infringement?
>
> Against whom?
>
>
> A more pragmatic, less expensive, and publicly visible expression of 
> IETF displeasure might be to expunge all versions of the offending I-D 
> from IETF document store and refuse to publish any subsequent version 
> until the unwarranted claims made for it are retracted.
>
> To be effective, that needs to be done now, while the iron is still 
> hot; not after the usual 3-month email debate about the diplomatic 
> niceties.
>
The later, accompanied with a strong statement about the limits of 
DMARC, and the flaws in its deployment - might not be a bad start.

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 11:03:30 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DCD81A01FC for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:03:29 -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, SPF_PASS=-0.001] autolearn=ham
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 iWdkj7dq-Y3H for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:03:28 -0700 (PDT)
Received: from mail-wg0-x229.google.com (mail-wg0-x229.google.com [IPv6:2a00:1450:400c:c00::229]) by ietfa.amsl.com (Postfix) with ESMTP id A516C1A049D for <ietf@ietf.org>; Mon, 14 Apr 2014 11:03:27 -0700 (PDT)
Received: by mail-wg0-f41.google.com with SMTP id n12so8634614wgh.24 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:03:24 -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:content-type; bh=xX/JT7eWfxZwSdpmOPRS7959x/yIQ7NdJAP6T7nv7e4=; b=HjL6HAjY+q67ikHa7PpI1rZOkgAsqojsV2Dx8qnLsA07OI6X2kURlvxYoj7ZEvn0gw rGTrW8572PBS1a4VfHuUOEcLZCs85LugHZE07QrLhitt9DEvYJ45QOyotBNw4FJfHxA4 Yd/u+mbJqk572F7/3nLARTeRM+R3+LBsJREINUeEm/hJ78fXdIzB5SWQxEbx8BAptn1g 4OBoE5/gxA4AomTf+Qw/mDp6V2CDrLQ7SjAn+E3Mz+Exq3CeKIma5G7pVxTxol4+dasj X9/CFmeFPnqK98NBobsTodMoFu6NnPGu/lnuYEFOw3EHyxtA+TziYUmtFqQjvcdrA0wC v+YA==
MIME-Version: 1.0
X-Received: by 10.180.211.116 with SMTP id nb20mr10610350wic.5.1397498604666;  Mon, 14 Apr 2014 11:03:24 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 11:03:24 -0700 (PDT)
In-Reply-To: <534C2262.1070507@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net>
Date: Mon, 14 Apr 2014 11:03:24 -0700
Message-ID: <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=001a11c26ab4e7c50d04f7047f2d
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/U6AP9tHxzHPhLuWf9Zcl-DniJbQ
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 18:03:29 -0000

--001a11c26ab4e7c50d04f7047f2d
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 11:01 AM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:

>
>
>> A more pragmatic, less expensive, and publicly visible expression of IETF
>> displeasure might be to expunge all versions of the offending I-D from IETF
>> document store and refuse to publish any subsequent version until the
>> unwarranted claims made for it are retracted.
>>
>> To be effective, that needs to be done now, while the iron is still hot;
>> not after the usual 3-month email debate about the diplomatic niceties.
>>
>>  The later, accompanied with a strong statement about the limits of
> DMARC, and the flaws in its deployment - might not be a bad start.
>

What real-world effect is this supposed to have, apart from setting a very
dangerous precedent?

-MSK

--001a11c26ab4e7c50d04f7047f2d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 11:01 AM, Miles Fidelman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank=
">mfidelman@meetinghouse.net</a>&gt;</span> wrote:<br><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div cla=
ss=3D"">

<br>
A more pragmatic, less expensive, and publicly visible expression of IETF d=
ispleasure might be to expunge all versions of the offending I-D from IETF =
document store and refuse to publish any subsequent version until the unwar=
ranted claims made for it are retracted.<br>

<br>
To be effective, that needs to be done now, while the iron is still hot; no=
t after the usual 3-month email debate about the diplomatic niceties.<br>
<br>
</div></blockquote>
The later, accompanied with a strong statement about the limits of DMARC, a=
nd the flaws in its deployment - might not be a bad start.<span class=3D"HO=
EnZb"><font color=3D"#888888"><br>
</font></span></blockquote><div><br></div><div>What real-world effect is th=
is supposed to have, apart from setting a very dangerous precedent?<br><br>=
</div><div>-MSK <br></div></div></div></div>

--001a11c26ab4e7c50d04f7047f2d--


From nobody Mon Apr 14 11:09:01 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8181A01FE for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 DOiD6ZcABGS1 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:08:47 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 526551A0505 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:08:44 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 93691CC08E for <ietf@ietf.org>; Mon, 14 Apr 2014 14:08:41 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id f23uz8yLzVAV for <ietf@ietf.org>; Mon, 14 Apr 2014 14:08:32 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 9BC1DCC0B3 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:08:32 -0400 (EDT)
Message-ID: <534C2420.60801@meetinghouse.net>
Date: Mon, 14 Apr 2014 14:08:32 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan>	<534B4E97.2050000@meetinghouse.net> <CAL0qLwYHP-rVF5TmEH2_kTZ7bDnxms7md=Y8Voef9OyPD4Bj8Q@mail.gmail.com>
In-Reply-To: <CAL0qLwYHP-rVF5TmEH2_kTZ7bDnxms7md=Y8Voef9OyPD4Bj8Q@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/txBQFbY2hVAQtgt7ezJ0N393nzM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 18:08:48 -0000

Murray S. Kucherawy wrote:
> On Sun, Apr 13, 2014 at 7:57 PM, Miles Fidelman 
> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>
>
>     It strikes me that the real way to address some of these issues is
>     to add a few new headers to SMTP - to get rid of the overloading
>     of the From: and Reply-to: headers associated with mailing lists.
>      An SMTP extension that would absorb some of the well-known and
>     well-understood functions of list software.
>
>     [...]
>
>
> I made that same suggestion on a different list.  It seems as if that 
> suggestion was made long ago and the debate reached "religious" 
> proportions.  One of the usual answers emerged, which was that it'll 
> take forever to get this deployed with sufficient ubiquity as to be 
> helpful.
>
> I'm guessing that means we shouldn't try.
>
Can anybody comment on the process by which mailing list control headers 
(RFC 2919 and 2369) were coordinated?  Seems like there might be some 
lessons to be learned.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 11:43:54 2014
Return-Path: <warren@kumari.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B50C1A06AE for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 JMMns2r5sBXy for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:43:47 -0700 (PDT)
Received: from mail-wg0-f46.google.com (mail-wg0-f46.google.com [74.125.82.46]) by ietfa.amsl.com (Postfix) with ESMTP id 0B04C1A06AC for <ietf@ietf.org>; Mon, 14 Apr 2014 11:43:46 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id b13so8585291wgh.29 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:43:44 -0700 (PDT)
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:content-type; bh=uO0xuEx01TefLyBM0IG7V3prLPhp+FV36j8/SjBVUfk=; b=G9mxMXaNELA3Yxrit/JEx+n0sugO6L0nWeij+kq+uq+VccMOvyhe+t17JpURicDiUr H5Pr9NliqyVy3XP8dm1hzs2hrpb1zWszhCO0OQMxvhRYGRTAEbKll/VICX5Oex2GdMqz EHBFyRn6mwm6gubmzT4TsSv2qGn1fVW3lMaxTEqeGru3P7fuI9f1wZmKjmr7n56APPMI efEwm9u6j0Jk4AbNv2Ei1N0oKQH3P9ViihtvJAjMQGsPnni2jInSyjFM3gpUS2ktj+KX 8zvs3uR3qBVIDlFp9F0rhkU3gkKExgLxn7M6ocImu5R5AwJpnzRfhZAIUYD3pYKwx0Ds dEBQ==
X-Gm-Message-State: ALoCoQnUAj7zHvn67FBcjaEKHqi8za9aSQKsSClmGeXFMyjYaXRyTrQq38pd3FdEiOeIg0v8mxS0
MIME-Version: 1.0
X-Received: by 10.180.37.110 with SMTP id x14mr10910234wij.52.1397501024017; Mon, 14 Apr 2014 11:43:44 -0700 (PDT)
Received: by 10.194.54.162 with HTTP; Mon, 14 Apr 2014 11:43:43 -0700 (PDT)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <5349A261.9040500@dcrocker.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net>
Date: Mon, 14 Apr 2014 14:43:43 -0400
Message-ID: <CAHw9_iK85xZjpsw27OAmbJd5xFKL_roLcRdu++uquFwf7K4kaw@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Warren Kumari <warren@kumari.net>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SbjwAJYbAFBB85D_4VtWCw2lvnw
Cc: "ietf@ietf.org Disgust" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 18:43:52 -0000

On Sat, Apr 12, 2014 at 4:30 PM, Dave Crocker <dhc@dcrocker.net> wrote:
> On 4/12/2014 12:56 PM, Miles Fidelman wrote:
>>
>> - DMARC.org defines the "DMARC Base Specification" with a link to
>> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an IETF
>> document
>
>
> While the Internet-Draft mechanism is operated by the IETF, it is an open
> mechanism and issuance through it carries no automatic status, particularly
> with respect to the IETF.

It seems that folk often miss this particular point (see the recent
drama about draft-loreto-httpbis-trusted-proxy20). Pointing at the
boilerplate, explaining the fact that anyone (with an Internet
connection and an XML editor) can submit an ID, etc doesn't seem to
work. I considered pointing at, well, anything by Terrell, but instead
decided to publish a draft :-P

http://tools.ietf.org/html/draft-wkumari-not-a-draft-00

Comments welcome.
W


>
> The DMARC specification is not 'an IETF document'.  The current plan is to
> publish it as an RFC, through the 'Independent' stream, which also is /not/
> an IETF activity.
>
>
>
>> - the referenced document is an informational  Internet draft, that
>
>
> Drafts do not have status.  So the qualifier 'informational' here is not
> meaningful.
>
>
>
>> In essence, DMARC is being represented as a mature, standards-track IETF
>> specification - with the implication that it's been widely vetted, and
>> is marching through the traditional experimental -> optional ->
>> recommended -> mandatory steps that IETF standards go through.
>>
>> In reality:
>> - DMARC was developed by a tiny number of people, all of whom work for
>> very large ISPs
>
>
> Well, a few of us who participated don't...
>
>
>
>> - as far as I can tell, all input from the broader community - notably
>> mailing list developers and operators was roundly ignored or dismissed
>> (the transcript is really clear on this)
>
>
> What transcript?  I'm not aware of its being 'ignored or dismissed'.
>
>
>
>> - while DMARC is at least partially tested, deploying and honoring
>> "p=reject" messages is brand new, and has wreaked tremendous damage
>> across the net
>
>
> It's not new at all, though of course Yahoo's use is distinctive.
>
>
>
>> - as far as I can tell, those who are behind DMARC are taking the
>> position "it's not our problem" (see discussions on
>> dmarc-discuss@dmarc.org and dmarc@ietf.org) - and there is nary a Yahoo
>> representative to be seen anywhere
>
>
> I've no idea what specifics you are referring to.
>
>
>
>> The situation strikes me as incredibly perverse and broken - the more so
>> that the perpetrators are presenting this as blessed by the IETF
>> standards process.
>
>
> I haven't seen anyone present such a claim of blessing.  Please point to the
> specifics.
>
> I fear you are confusing the difference between a desire for standards
> status with a claim of its having been granted.
>
>  d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>


From nobody Mon Apr 14 11:47:16 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD3F31A06E4 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:47:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 yBl0p12t85pV for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:47:12 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD991A06AC for <ietf@ietf.org>; Mon, 14 Apr 2014 11:47:11 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 549A3CC0BF for <ietf@ietf.org>; Mon, 14 Apr 2014 14:47:08 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id i3s7Q1lTpUZv for <ietf@ietf.org>; Mon, 14 Apr 2014 14:46:59 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 8116ACC09E for <ietf@ietf.org>; Mon, 14 Apr 2014 14:46:59 -0400 (EDT)
Message-ID: <534C2D23.3050600@meetinghouse.net>
Date: Mon, 14 Apr 2014 14:46:59 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan>	<534B524F.4050206@dcrocker.net>	<alpine.BSF.2.00.1404132327560.26258@joyce.lan>	<E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com>	<alpine.BSF.2.00.1404132346420.26386@joyce.lan>	<1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com>	<534B9760.90301@dougbarton.us>	<534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
In-Reply-To: <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4rZXX7LYAtiuwydzMtG6GUyzKFo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 18:47:13 -0000

Murray S. Kucherawy wrote:
> On Mon, Apr 14, 2014 at 8:09 AM, Miles Fidelman 
> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>
>     Is it perhaps also incumbent on the folks promulgating DMARC (and
>     its predecessors, and its sure-to-be successors) to work
>     cooperatively with mailing list developers, rather than taking the
>     position "nope, we break mailing lists, not our problem?"
>
>
> The DMARC proponents did engage mailman.   Version 2.1.16 includes 
> support for a setting that makes the operation of the list 
> DMARC-friendly, though likely in a way some people will find 
> unpalatable.  Either way, it was not done entirely in a vacuum.
>
>
>     I'm kind of coming to the conclusion that what we need to be
>     looking at is defining an SMTP extension that addresses BOTH sets
>     of concerns - and doing so in a cooperative manner that engages
>     not just the community behind DKIM and DMARC, but also the
>     developers and operators of mailman, sympa, majordomo, listserv -
>     and ideally the sendmail, postfix, exim, qmail community.
>
>     Dare I suggest that this calls for an IETF working group?
>
>
> I mentioned in another thread that the DMARC people did come to the 
> IETF to ask for a working group to complete development of the work on 
> the standards track.  This request was denied on the grounds that 
> DMARC was essentially already done, and thus the IETF had nothing 
> engineering-wise to contribute.  There were also too few people that 
> were not already DMARC proponents that would commit to working on it

Thanks for the history Murray.

Does this, perhaps, illuminate a flaw or failing in the way IETFs 
effects its role as the Internet's official standards body?  The more so 
that it's not stepping in after the fact to help clear up this mess?

I do wonder if there's a related case study in the way that RSS evolved 
into Atom - a case where outside work, and conflicts within it, ended up 
being worked under the IETF aegis?  (Sort of  shame that Atom has not 
become more popular.)

Miles


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 11:47:33 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 419491A06E1 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:47:32 -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, SPF_PASS=-0.001] autolearn=ham
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 3RK43sTINC3b for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:47:31 -0700 (PDT)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com [IPv6:2a00:1450:400c:c05::22d]) by ietfa.amsl.com (Postfix) with ESMTP id BCC4F1A0468 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:47:30 -0700 (PDT)
Received: by mail-wi0-f173.google.com with SMTP id z2so4524271wiv.12 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:47: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:content-type; bh=a6U3OkVPw3K5Jn+P0bzpaqz91F5DjfJa3T/BvXaz/lY=; b=cNWONmPYBmwEyx565Oi0ZaD5SXeazQzBU9fZGyQIwNWkPN/Ziv20DLKvqknitFiAxy YJuKqVKw06QnSzsDtVairGr/ZrSOWXfKRueIEdb7RiRUYIuZAD3eja2cVt7fH6ABCset QT1x3ZELIwFR4ZF0+momVkJTZbPmXTqLxvbg4GBpYBsBDhVT970HQXOuvkEDhgxTlrWX JTuj4N130naaKV5GnLqZ245xtFWzqrAy+370W0cyDT6C3w6s1SJz8Hr2OXYoOP5nTKt7 Gxw00X8oLb9TKCdTPG7yhEPo02XS5KwtArx8eWSj1OklF+2ATzXnbyyRxh58Qwl7XQXR WNHQ==
MIME-Version: 1.0
X-Received: by 10.194.161.168 with SMTP id xt8mr34357551wjb.35.1397501247612;  Mon, 14 Apr 2014 11:47:27 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 11:47:27 -0700 (PDT)
In-Reply-To: <CAHw9_iK85xZjpsw27OAmbJd5xFKL_roLcRdu++uquFwf7K4kaw@mail.gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <CAHw9_iK85xZjpsw27OAmbJd5xFKL_roLcRdu++uquFwf7K4kaw@mail.gmail.com>
Date: Mon, 14 Apr 2014 11:47:27 -0700
Message-ID: <CAL0qLwaVcCczkWARGZQrAH_vD51wacnJqfhXMKKPWiPBKfaZ1Q@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=089e01419c6a6febd304f7051dc9
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Gz2LPamdfvnzlNsptIaNkiaP3-8
Cc: Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org Disgust" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 18:47:32 -0000

--089e01419c6a6febd304f7051dc9
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 11:43 AM, Warren Kumari <warren@kumari.net> wrote:

>
> http://tools.ietf.org/html/draft-wkumari-not-a-draft-00
>
> Comments welcome.
> W
>

Let me know if you need a document shepherd.

-MSK

--089e01419c6a6febd304f7051dc9
Content-Type: text/html; charset=UTF-8

<div dir="ltr">On Mon, Apr 14, 2014 at 11:43 AM, Warren Kumari <span dir="ltr">&lt;<a href="mailto:warren@kumari.net" target="_blank">warren@kumari.net</a>&gt;</span> wrote:<br><div class="gmail_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<a href="http://tools.ietf.org/html/draft-wkumari-not-a-draft-00" target="_blank">http://tools.ietf.org/html/draft-wkumari-not-a-draft-00</a><br>
<br>
Comments welcome.<br>
<div class="HOEnZb"><div class="h5">W<br></div></div></blockquote><div><br></div><div>Let me know if you need a document shepherd.<br><br>-MSK <br></div></div></div></div>

--089e01419c6a6febd304f7051dc9--


From nobody Mon Apr 14 11:55:08 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17DEA1A069E for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:55:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.4
X-Spam-Level: *
X-Spam-Status: No, score=1.4 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 b1gOk51cP6-p for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:55:05 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.4]) by ietfa.amsl.com (Postfix) with ESMTP id C9E721A0468 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:55:04 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES532.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Mon, 14 Apr 2014 14:55:01 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Subject: RE: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Thread-Topic: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Thread-Index: AQHPWAp5PWZYqrDS0kS5LDODiAAGHZsRZnHA
Date: Mon, 14 Apr 2014 18:55:00 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D45BFB@USCLES544.agna.amgreetings.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
In-Reply-To: <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_CE39F90A45FF0C49A1EA229FC9899B0507D45BFBUSCLES544agnaam_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zQr_bhLVefhS-IubQdXM9DznigI
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 18:55:07 -0000

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D45BFBUSCLES544agnaam_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCkZyb206IGlldGYgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBP
ZiBNdXJyYXkgUy4gS3VjaGVyYXd5DQpTZW50OiBNb25kYXksIEFwcmlsIDE0LCAyMDE0IDE6NTQg
UE0NClRvOiBuZWQraWV0ZkBtYXV2ZS5tcm9jaGVrLmNvbQ0KQ2M6IGlldGYNClN1YmplY3Q6IFJl
OiBETUFSQyBmcm9tIHRoZSBwZXJzcGVjdGl2ZSBvZiB0aGUgbGlzdGFkbWluIG9mIGEgYnVuY2gg
b2YgU01BTEwgY29tbXVuaXR5IGxpc3RzDQoNCk9uIFNhdCwgQXByIDEyLCAyMDE0IGF0IDQ6MzUg
UE0sIDxuZWQraWV0ZkBtYXV2ZS5tcm9jaGVrLmNvbTxtYWlsdG86bmVkK2lldGZAbWF1dmUubXJv
Y2hlay5jb20+PiB3cm90ZToNClRoZSB1bmRlcmx5aW5nIHRlY2huaWNhbCBpc3N1ZSBpcyB0aGF0
IHRoZSB0d28gdGVjaG5vbG9naWVzIERNQVJDIGlzIGJ1aWx0IG9uIC0NCkRLSU0gYW5kIFNQRiAt
IGJvdGggYXR0YWNoIGFkZGl0aW9uYWwvcmVzdHJpY3RpdmUgc2VtYW50aWNzIHRvIGxvbmdzdGFu
ZGluZyBtYWlsDQpzeXN0ZW0gZmllbGRzLiAoQnJvYWRseSBzcGVha2luZywgRnJvbTogZm9yIERL
SU0gYW5kIE1BSUwgRlJPTSBmb3IgU1BGLikNCg0KU29tZXRoaW5nJ3MgYW1pc3MgaGVyZS4gIFdo
YXQgbmV3IHNlbWFudGljcyBkb2VzIERLSU0gYXR0YWNoIHRvIEZyb206PyAgQXMgZmFyIGFzIEkg
a25vdywgaXQgb25seSByZXF1aXJlcyB0aGF0IHRoZSBmaWVsZCBiZSBzaWduZWQuICBJdCBkb2Vz
bid0IHJlcXVpcmUgdGhhdCBpdCBiZSBpbnRlcnByZXRlZCBpbiBhIHBhcnRpY3VsYXIgd2F5IG9y
IHRoYXQgaXQgY29udGFpbiBhbnkgcGFydGljdWxhciB2YWx1ZS4NCg0KSXQgZ29lcyBvbiB0byBk
aXNjdXNzIHRoZSB1c2Ugb2YgcD1yZWplY3Qgd2l0aCBkb21haW5zIHRoYXQgb25seSBzZW5kDQp0
cmFuc2FjdGlvbmFsLiBBRkFJQ1QgdGhlcmUgaXMgbm8gZGlzY3Vzc2lvbiBvZiB3aGVuICpub3Qq
IHRvIHVzZSBwPXJlamVjdCwgYW5kDQp3aHkuIE5vciwgZm9yIHRoYXQgbWF0dGVyIGlzIHRoZXJl
IHN1YnN0YW50aXZlIGRpc2N1c3Npb24gb2YgbWFpbGluZ19saXN0LA0KYW5kIHdoeSBpdCdzIG5v
dCBhIGdlbmVyYWwgc29sdXRpb24gdG8gdGhlIHByb2JsZW1zIGNhdXNlZCBieSBwPXJlamVjdC4N
Cg0KWWVzLCB0aGF0J3MgdXNlZnVsIGFkdmljZSBmb3IgYSBmdXR1cmUgcmV2aXNpb24uDQoNCkxp
a2UgaXQgb3Igbm90LCB0aGUgSUVURiBwdWJsaXNoZWQgYSBkcmFmdCB0aGF0IGRlZmluZXMgY2Vy
dGFpbiBtZWNoYW5pc21zDQp3aGljaCwgaWYgdXNlZCBpbXByb3Blcmx5IGJ5IGEgbGFyZ2UgcHJv
dmlkZXIsIGNhdXNlIHNlcmlvdXMgcHJvYmxlbXMgZm9yIGENCmxhcmdlIG51bWJlciBvZiBwZW9w
bGUuIFRoZSB0ZXh0IGRlc2NyaWJpbmcgdGhlIGNvbnNlcXVlbmNlcyBvZiB0aGUgdXNlIG9mDQp0
aG9zZSBtZWNoYW5zaXNtcyBpbiB0aGUgZHJhZnRzIGlzLCBJTU8sIGVudGlyZWx5IGluYWRlcXVh
dGUuDQoNCkl0J3MgdGhlIHNhbWUgZG9jdW1lbnQgdGhhdCB3YXMgcG9zdGVkIG9uIG90aGVyIHdl
YiBzaXRlcyBmb3Igc29tZSB0aW1lLCBhbmQgd2FzIGluIHVzZSBieSBhIG51bWJlciBvZiBvcGVy
YXRvcnMgKGluY2x1ZGluZyBZYWhvbykgbG9uZyBiZWZvcmUgaXQgd2VudCBpbnRvIHRoZSBkYXRh
dHJhY2tlci4NCkFzIGl0J3Mgb25seSBhIGRyYWZ0LCB0aGVyZSdzIGFtcGxlIG9wcG9ydHVuaXR5
IHRvIG1ha2Ugc3VjaCBpbXByb3ZlbWVudHMuDQpBbHNvOiBCeSAidGhlIElFVEYgcHVibGlzaGVk
IGEgZHJhZnQiLCBhcmUgeW91IHRhbGtpbmcgYWJvdXQgYW4gUkZDLCBvciB0aGUgRE1BUkMgYmFz
ZSBkcmFmdD8gIEl0IHNlZW1zIGV4dHJlbWUgdG8gbGF5IGJsYW1lIG9uIHRoZSBJRVRGIGluIGdl
bmVyYWwgbWVyZWx5IGZvciBoYXZpbmcgYW4gb3BlbiBtZWNoYW5pc20gYnkgd2hpY2ggdG8gcG9z
dCBhIGRyYWZ0IGZvciBhbGwgdG8gc2VlIGFuZCBkaXNjdXNzLiAgQSAiUmVxdWVzdCBGb3IgQ29t
bWVudCIsIGFzIGl0IHdlcmUuICBBcmUgeW91IHN1Z2dlc3RpbmcgdGhhdCBwcm9jZXNzIHNob3Vs
ZCBiZSBjbG9zZWQgb3IgbW9kZXJhdGVkIHNvbWVob3c/DQoNCkFuZCBpdCdzIG5vdCBsaWtlIHdl
IGRpZG4ndCBrbm93LiBBcyBvdGhlcnMgaGF2ZSBwb2ludGVkIG91dCwgdGhpcyBpc3N1ZQ0KZXhp
c3RlZCBpbiB0aGUgZWFybGllciBBRFNQIHByb3Bvc2FsLiBJdCB3YXMgZ2l2ZW4gaW5zdWZmaWNp
ZW50IGF0dGVudGlvbiB0aGVyZQ0KYXMgd2VsbC4NCg0KTUg6IEnigJltIGdvaW5nIHRvIGRpc2Fn
cmVlIHdpdGggeW91ciBzdGF0ZW1lbnQgYWJvdXQgaW5zdWZmaWNpZW50IGF0dGVudGlvbiBOZWQu
IEnigJl2ZSBiZWVuIHJldmlld2luZyB0aGUgZGlzY3Vzc2lvbnMgZnJvbSB0aGUgREtJTSB3b3Jr
aW5nIGdyb3VwIGF0IHRoYXQgdGltZSAoZWFybHkgMjAwOCkgYW5kIHRoZXJlIHdhcyBpbiBmYWN0
IHF1aXRlIGEgYml0IG9mIGF0dGVudGlvbiBnaXZlbiB0byB0aGUgaXNzdWUgaW4gdGhlIGNvbnRl
eHQgb2YgU1NQIGFuZCB0aGUgZGlzY3Vzc2lvbiBnb3QgcXVpdGUgaGVhdGVkLiBPbmUgc3VjaCBk
aXNjdXNzaW9uIGF0IHRoYXQgdGltZSB3YXMg4oCcUkU6IFtpZXRmLWRraW1dIFJlOiBJU1NVRSAx
NTIxIC0tIExpbWl0IHRoZSBhcHBsaWNhdGlvbiBvZiBTU1AgdG91bnNpZ25lZCBtZXNzYWdlc+KA
nS4gT25lIHBvc2l0aW9uIGluIHRoYXQgZGlzY3Vzc2lvbiB3YXMgdGhhdCBtYWlsIGxpc3RzIGNv
dWxkIGJlIHRydXN0ZWQgYW5kIHRoZXJlZm9yZSBzaG91bGQgc3VwZXJjZWRlIGFueSBwb2xpY3kg
YXNzZXJ0aW9ucyBieSBkb21haW4gb3duZXJzIG1hZGUgdGhyb3VnaCBTU1AgKHdoaWNoIG5hbWUg
d2FzIGNoYW5nZWQgYXQgbXkgc3VnZ2VzdGlvbiBiZWNhdXNlIHRoZSBzdGFuZGFyZCByZXByZXNl
bnRlZCBkb21haW4gcG9saWN5IGFzc2VydGlvbnMgYW5kIG5vdCBpbmRpdmlkdWFsIHNlbmRlciBh
c3NlcnRpb25zKS4gVGhlIGRpc2N1c3Npb24gb2YgbWFpbCBsaXN0cyBpbiB0aGUgY29udGV4dCBv
ZiBlbWFpbCBhdXRoZW50aWNhdGlvbiBoYXMgYmVlbiBleGhhdXN0aXZlIChib3RoIGxpdGVyYWxs
eSBhbmQgZmlndXJhdGl2ZWx5KSBvbiBtdWx0aXBsZSBvY2Nhc2lvbnMgYW5kIGluIG11bHRpcGxl
IHBsYWNlcyBmb3Igc29tZSB0aW1lIGZyYW1lIGFwcHJvYWNoaW5nIGEgZGVjYWRlIGlmIG5vdCBs
b25nZXIuDQoNCkFzIHdpdGggYW55IGRyYWZ0LCBpdHMgY29udGVudCBpcyBvbmx5IGFzIGdvb2Qg
YXMgaXRzIGNvbnRyaWJ1dGlvbnMgYW5kIHRoZSByZXZpZXdzIGl0IGdvdC4NCg0KTUg6IFRoZSBy
ZWFsaXR5IGlzIHRoYXQgdGhlcmUgd2FzIGEgY29tcHJvbWlzZSB0byBnZXQgQURTUCBzZXQgYW5k
IG91dCB0aGUgZG9vciB3aXRoIHRoZSB1bmRlcnN0YW5kaW5nIHRoYXQgb25jZSB0aGVyZSB3YXMg
c29tZSBleHBlcmllbmNlIHJ1bm5pbmcgaW4gdGhlIHdpbGQg4oCcd2XigJ0gd291bGQgY2lyY2xl
IGJhY2sgYW5kIHJlbWVkaWF0ZSBpZGVudGlmaWVkIGlzc3Vlcy4gSXQgd2FzIGEgYmFkIGNvbXBy
b21pc2UgYW5kIHRoZXJlIHdlcmUgZXZlbiBzb21lIHRoYXQgc3RhdGVkIGF0IHRoZSB0aW1lLCB0
aGUgY29tcHJvbWlzZSB3YXMgaW50ZW5kZWQgdG8ga2lsbCBBRFNQLiBJZiBJIGhhZCBpdCB0byBk
byBvdmVyIGFnYWluIEkgd291bGQgYmUgbW9yZSByZXNpc3RhbnQgdG8gY29tcHJvbWlzZSByZWdh
cmRpbmcgdGhlIE1MTSBpc3N1ZSBldmVuIGlmIGl0IGhhZCBtZWFudCBBRFNQIG5vdCBnZXR0aW5n
IG91dCB0aGUgZG9vci4NCg0KT2YgY291cnNlIHRoZSBJRVRGIGNhbiBmYWxsIGJhY2sgb24gdGhl
IHVzdWFsIGV4Y3VzZXMsIGluY2x1ZGluZywgYnV0IG5vdA0KbGltaXRlZCB0bzoNCg0KICAgIFlh
aG9vLCBvZiBhbGwgSVNQcywgc2hvdWxkIGhhdmUga25vd24gYmV0dGVyDQogICAgV2UgZG9uJ3Qg
dGVsbCBwZW9wbGUgd2hhdCB0byBkbw0KICAgIEl0IHdhcyBqdXN0IGEgZHJhZnQNCiAgICBJdCB3
YXMgbmV2ZXIgaW50ZW5kZWQgdG8gYmUgYSBzdGFuZGFyZA0KICAgIFdlJ3JlIG5vdCB0aGUgSW50
ZXJuZXQgUHJvdG9jb2wgUG9saWNlDQogICAgZXRjLg0KDQpJJ20gc29ycnksIGJ1dCB0aGlzIHRp
bWUgbm9uZSBvZiB0aGVzZSBkb2dzIGFyZSBodW50aW5nIGZvciBtZS4gQW4gYXR0cmFjdGl2ZQ0K
bnVpc2FuY2UgaXMgYW4gYXR0cmFjdGl2ZSBudWlzYW5jZSwgYW5kIHRoaXMgaXMgd2hhdCB0aGUg
SUVURiBoYXMsIGFsYmVpdCB3aXRoDQp0aGUgYmVzdCBvZiBpbnRlbnRpb25zLCBtYW5hZ2VkIHRv
IGNyZWF0ZS4NCg0KSSB3b3VsZCBhZGQgdG8gdGhpcyB0aGF0LCBieSBpdHMgdWx0aW1hdGUgaW5h
Y3Rpb24gaW4gdGhlIGZhY2Ugb2YgYSBwcm90cmFjdGVkIHBlcmlvZCBvZiBhYnVzZSBhbmQgYXR0
ZW1wdHMgYnkgcGFydGljaXBhbnRzIHRvIHNvbHZlIHRoYXQgcHJvYmxlbSB3aXRoaW4gaXRzIHBy
b2NlZHVyZXMsIHRoZSBJRVRGIGhhcyBhYmRpY2F0ZWQgYW55IGF1dGhvcml0eSBpdCBtYXkgaGF2
ZSBoYWQuDQoNCk1IOiBJ4oCZbSBub3Qgc3VyZSBJIHdvdWxkIGdvIHRoaXMgZmFyIGJ1dCBJIHRo
aW5rIGl0IHJlZmxlY3RzIGNvbmNlcm5zIGhlbGQgYnkgbWFueS4NCg0KVGhlIHJlYWwgcXVlc3Rp
b24gd2Ugc2hvdWxkIGJlIGRpc2N1c3NpbmcgaXMgd2hhdCBvcHRpb25zIHRoZSBJRVRGIGhhcyB0
byB0cnkNCmFuZCBhZGRyZXNzIHRoaXMuDQoNCkkgY2VydGFpbmx5IGFncmVlIHdpdGggdGhhdC4N
Cg0KTUg6IEZpcnN0IHRoZXJlIG5lZWRzIHRvIGJlIGEgY29uc2Vuc3VzIGFzIHRvIHdoYXQg4oCc
dGhpc+KAnSBpcyBiZWZvcmUgdGhlcmUgY2FuIGJlIGFuIGF0dGVtcHQgdG8gYWRkcmVzcyDigJx0
aGlz4oCdLg0KDQotTVNLDQo=

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D45BFBUSCLES544agnaam_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAx
LjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRz
IHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1h
cCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRp
Zl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVy
cGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzow
aW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IGlldGYgW21haWx0bzppZXRmLWJv
dW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPk11cnJheSBTLiBLdWNoZXJhd3k8
YnI+DQo8Yj5TZW50OjwvYj4gTW9uZGF5LCBBcHJpbCAxNCwgMjAxNCAxOjU0IFBNPGJyPg0KPGI+
VG86PC9iPiBuZWQmIzQzO2lldGZAbWF1dmUubXJvY2hlay5jb208YnI+DQo8Yj5DYzo8L2I+IGll
dGY8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IERNQVJDIGZyb20gdGhlIHBlcnNwZWN0aXZlIG9m
IHRoZSBsaXN0YWRtaW4gb2YgYSBidW5jaCBvZiBTTUFMTCBjb21tdW5pdHkgbGlzdHM8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gU2F0LCBB
cHIgMTIsIDIwMTQgYXQgNDozNSBQTSwgJmx0OzxhIGhyZWY9Im1haWx0bzpuZWQmIzQzO2lldGZA
bWF1dmUubXJvY2hlay5jb20iIHRhcmdldD0iX2JsYW5rIj5uZWQmIzQzO2lldGZAbWF1dmUubXJv
Y2hlay5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGJs
b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4w
cHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmln
aHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSB1bmRlcmx5aW5nIHRlY2huaWNhbCBp
c3N1ZSBpcyB0aGF0IHRoZSB0d28gdGVjaG5vbG9naWVzIERNQVJDIGlzIGJ1aWx0IG9uIC08YnI+
DQpES0lNIGFuZCBTUEYgLSBib3RoIGF0dGFjaCBhZGRpdGlvbmFsL3Jlc3RyaWN0aXZlIHNlbWFu
dGljcyB0byBsb25nc3RhbmRpbmcgbWFpbDxicj4NCnN5c3RlbSBmaWVsZHMuIChCcm9hZGx5IHNw
ZWFraW5nLCBGcm9tOiBmb3IgREtJTSBhbmQgTUFJTCBGUk9NIGZvciBTUEYuKTxvOnA+PC9vOnA+
PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U29tZXRo
aW5nJ3MgYW1pc3MgaGVyZS4mbmJzcDsgV2hhdCBuZXcgc2VtYW50aWNzIGRvZXMgREtJTSBhdHRh
Y2ggdG8gRnJvbTo/Jm5ic3A7IEFzIGZhciBhcyBJIGtub3csIGl0IG9ubHkgcmVxdWlyZXMgdGhh
dCB0aGUgZmllbGQgYmUgc2lnbmVkLiZuYnNwOyBJdCBkb2Vzbid0IHJlcXVpcmUgdGhhdCBpdCBi
ZSBpbnRlcnByZXRlZCBpbiBhIHBhcnRpY3VsYXIgd2F5IG9yIHRoYXQgaXQgY29udGFpbiBhbnkg
cGFydGljdWxhciB2YWx1ZS48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8YmxvY2txdW90ZSBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+SXQgZ29lcyBvbiB0byBkaXNjdXNzIHRoZSB1c2Ugb2YgcD1y
ZWplY3Qgd2l0aCBkb21haW5zIHRoYXQgb25seSBzZW5kPGJyPg0KdHJhbnNhY3Rpb25hbC4gQUZB
SUNUIHRoZXJlIGlzIG5vIGRpc2N1c3Npb24gb2Ygd2hlbiAqbm90KiB0byB1c2UgcD1yZWplY3Qs
IGFuZDxicj4NCndoeS4gTm9yLCBmb3IgdGhhdCBtYXR0ZXIgaXMgdGhlcmUgc3Vic3RhbnRpdmUg
ZGlzY3Vzc2lvbiBvZiBtYWlsaW5nX2xpc3QsPGJyPg0KYW5kIHdoeSBpdCdzIG5vdCBhIGdlbmVy
YWwgc29sdXRpb24gdG8gdGhlIHByb2JsZW1zIGNhdXNlZCBieSBwPXJlamVjdC48bzpwPjwvbzpw
PjwvcD4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5ZZXMsIHRoYXQncyB1c2VmdWwgYWR2aWNlIGZvciBhIGZ1dHVyZSByZXZpc2lvbi48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7IDxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0
OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TGlrZSBpdCBv
ciBub3QsIHRoZSBJRVRGIHB1Ymxpc2hlZCBhIGRyYWZ0IHRoYXQgZGVmaW5lcyBjZXJ0YWluIG1l
Y2hhbmlzbXM8YnI+DQp3aGljaCwgaWYgdXNlZCBpbXByb3Blcmx5IGJ5IGEgbGFyZ2UgcHJvdmlk
ZXIsIGNhdXNlIHNlcmlvdXMgcHJvYmxlbXMgZm9yIGE8YnI+DQpsYXJnZSBudW1iZXIgb2YgcGVv
cGxlLiBUaGUgdGV4dCBkZXNjcmliaW5nIHRoZSBjb25zZXF1ZW5jZXMgb2YgdGhlIHVzZSBvZjxi
cj4NCnRob3NlIG1lY2hhbnNpc21zIGluIHRoZSBkcmFmdHMgaXMsIElNTywgZW50aXJlbHkgaW5h
ZGVxdWF0ZS48bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SXQncyB0aGUgc2FtZSBk
b2N1bWVudCB0aGF0IHdhcyBwb3N0ZWQgb24gb3RoZXIgd2ViIHNpdGVzIGZvciBzb21lIHRpbWUs
IGFuZCB3YXMgaW4gdXNlIGJ5IGEgbnVtYmVyIG9mIG9wZXJhdG9ycyAoaW5jbHVkaW5nIFlhaG9v
KSBsb25nIGJlZm9yZSBpdCB3ZW50IGludG8gdGhlIGRhdGF0cmFja2VyLjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0
b206MTIuMHB0Ij5BcyBpdCdzIG9ubHkgYSBkcmFmdCwgdGhlcmUncyBhbXBsZSBvcHBvcnR1bml0
eSB0byBtYWtlIHN1Y2ggaW1wcm92ZW1lbnRzLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkFsc286IEJ5ICZxdW90O3RoZSBJRVRGIHB1Ymxpc2hlZCBhIGRyYWZ0
JnF1b3Q7LCBhcmUgeW91IHRhbGtpbmcgYWJvdXQgYW4gUkZDLCBvciB0aGUgRE1BUkMgYmFzZSBk
cmFmdD8mbmJzcDsgSXQgc2VlbXMgZXh0cmVtZSB0byBsYXkgYmxhbWUgb24gdGhlIElFVEYgaW4g
Z2VuZXJhbCBtZXJlbHkgZm9yIGhhdmluZyBhbiBvcGVuIG1lY2hhbmlzbSBieSB3aGljaCB0byBw
b3N0IGEgZHJhZnQgZm9yIGFsbCB0byBzZWUgYW5kIGRpc2N1c3MuJm5ic3A7DQogQSAmcXVvdDtS
ZXF1ZXN0IEZvciBDb21tZW50JnF1b3Q7LCBhcyBpdCB3ZXJlLiZuYnNwOyBBcmUgeW91IHN1Z2dl
c3RpbmcgdGhhdCBwcm9jZXNzIHNob3VsZCBiZSBjbG9zZWQgb3IgbW9kZXJhdGVkIHNvbWVob3c/
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdp
bi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QW5k
IGl0J3Mgbm90IGxpa2Ugd2UgZGlkbid0IGtub3cuIEFzIG90aGVycyBoYXZlIHBvaW50ZWQgb3V0
LCB0aGlzIGlzc3VlPGJyPg0KZXhpc3RlZCBpbiB0aGUgZWFybGllciBBRFNQIHByb3Bvc2FsLiBJ
dCB3YXMgZ2l2ZW4gaW5zdWZmaWNpZW50IGF0dGVudGlvbiB0aGVyZTxicj4NCmFzIHdlbGwuPG86
cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj5NSDogSeKAmW0gZ29pbmcgdG8gZGlzYWdyZWUgd2l0aCB5b3VyIHN0YXRlbWVudCBh
Ym91dCBpbnN1ZmZpY2llbnQgYXR0ZW50aW9uIE5lZC4gSeKAmXZlIGJlZW4gcmV2aWV3aW5nIHRo
ZSBkaXNjdXNzaW9ucyBmcm9tIHRoZSBES0lNIHdvcmtpbmcgZ3JvdXAgYXQgdGhhdCB0aW1lDQog
KGVhcmx5IDIwMDgpIGFuZCB0aGVyZSB3YXMgaW4gZmFjdCBxdWl0ZSBhIGJpdCBvZiBhdHRlbnRp
b24gZ2l2ZW4gdG8gdGhlIGlzc3VlIGluIHRoZSBjb250ZXh0IG9mIFNTUCBhbmQgdGhlIGRpc2N1
c3Npb24gZ290IHF1aXRlIGhlYXRlZC4gT25lIHN1Y2ggZGlzY3Vzc2lvbiBhdCB0aGF0IHRpbWUg
d2FzIOKAnFJFOiBbaWV0Zi1ka2ltXSBSZTogSVNTVUUgMTUyMSAtLSBMaW1pdCB0aGUgYXBwbGlj
YXRpb24gb2YgU1NQIHRvdW5zaWduZWQgbWVzc2FnZXPigJ0uDQogT25lIHBvc2l0aW9uIGluIHRo
YXQgZGlzY3Vzc2lvbiB3YXMgdGhhdCBtYWlsIGxpc3RzIGNvdWxkIGJlIHRydXN0ZWQgYW5kIHRo
ZXJlZm9yZSBzaG91bGQgc3VwZXJjZWRlIGFueSBwb2xpY3kgYXNzZXJ0aW9ucyBieSBkb21haW4g
b3duZXJzIG1hZGUgdGhyb3VnaCBTU1AgKHdoaWNoIG5hbWUgd2FzIGNoYW5nZWQgYXQgbXkgc3Vn
Z2VzdGlvbiBiZWNhdXNlIHRoZSBzdGFuZGFyZCByZXByZXNlbnRlZCBkb21haW4gcG9saWN5IGFz
c2VydGlvbnMgYW5kDQogbm90IGluZGl2aWR1YWwgc2VuZGVyIGFzc2VydGlvbnMpLiBUaGUgZGlz
Y3Vzc2lvbiBvZiBtYWlsIGxpc3RzIGluIHRoZSBjb250ZXh0IG9mIGVtYWlsIGF1dGhlbnRpY2F0
aW9uIGhhcyBiZWVuIGV4aGF1c3RpdmUgKGJvdGggbGl0ZXJhbGx5IGFuZCBmaWd1cmF0aXZlbHkp
IG9uIG11bHRpcGxlIG9jY2FzaW9ucyBhbmQgaW4gbXVsdGlwbGUgcGxhY2VzIGZvciBzb21lIHRp
bWUgZnJhbWUgYXBwcm9hY2hpbmcgYSBkZWNhZGUgaWYgbm90IGxvbmdlci4NCjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZx
dW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BcyB3aXRoIGFueSBkcmFmdCwgaXRzIGNvbnRl
bnQgaXMgb25seSBhcyBnb29kIGFzIGl0cyBjb250cmlidXRpb25zIGFuZCB0aGUgcmV2aWV3cyBp
dCBnb3QuPGJyPg0KJm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+TUg6IFRoZSByZWFsaXR5
IGlzIHRoYXQgdGhlcmUgd2FzIGEgY29tcHJvbWlzZSB0byBnZXQgQURTUCBzZXQgYW5kIG91dCB0
aGUgZG9vciB3aXRoIHRoZSB1bmRlcnN0YW5kaW5nIHRoYXQgb25jZSB0aGVyZSB3YXMgc29tZSBl
eHBlcmllbmNlIHJ1bm5pbmcgaW4gdGhlIHdpbGQNCiDigJx3ZeKAnSB3b3VsZCBjaXJjbGUgYmFj
ayBhbmQgcmVtZWRpYXRlIGlkZW50aWZpZWQgaXNzdWVzLiBJdCB3YXMgYSBiYWQgY29tcHJvbWlz
ZSBhbmQgdGhlcmUgd2VyZSBldmVuIHNvbWUgdGhhdCBzdGF0ZWQgYXQgdGhlIHRpbWUsIHRoZSBj
b21wcm9taXNlIHdhcyBpbnRlbmRlZCB0byBraWxsIEFEU1AuIElmIEkgaGFkIGl0IHRvIGRvIG92
ZXIgYWdhaW4gSSB3b3VsZCBiZSBtb3JlIHJlc2lzdGFudCB0byBjb21wcm9taXNlIHJlZ2FyZGlu
ZyB0aGUgTUxNDQogaXNzdWUgZXZlbiBpZiBpdCBoYWQgbWVhbnQgQURTUCBub3QgZ2V0dGluZyBv
dXQgdGhlIGRvb3IuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
Pk9mIGNvdXJzZSB0aGUgSUVURiBjYW4gZmFsbCBiYWNrIG9uIHRoZSB1c3VhbCBleGN1c2VzLCBp
bmNsdWRpbmcsIGJ1dCBub3Q8YnI+DQpsaW1pdGVkIHRvOjxicj4NCjxicj4NCiZuYnNwOyAmbmJz
cDsgWWFob28sIG9mIGFsbCBJU1BzLCBzaG91bGQgaGF2ZSBrbm93biBiZXR0ZXI8YnI+DQombmJz
cDsgJm5ic3A7IFdlIGRvbid0IHRlbGwgcGVvcGxlIHdoYXQgdG8gZG88YnI+DQombmJzcDsgJm5i
c3A7IEl0IHdhcyBqdXN0IGEgZHJhZnQ8YnI+DQombmJzcDsgJm5ic3A7IEl0IHdhcyBuZXZlciBp
bnRlbmRlZCB0byBiZSBhIHN0YW5kYXJkPGJyPg0KJm5ic3A7ICZuYnNwOyBXZSdyZSBub3QgdGhl
IEludGVybmV0IFByb3RvY29sIFBvbGljZTxicj4NCiZuYnNwOyAmbmJzcDsgZXRjLjxicj4NCjxi
cj4NCkknbSBzb3JyeSwgYnV0IHRoaXMgdGltZSBub25lIG9mIHRoZXNlIGRvZ3MgYXJlIGh1bnRp
bmcgZm9yIG1lLiBBbiBhdHRyYWN0aXZlPGJyPg0KbnVpc2FuY2UgaXMgYW4gYXR0cmFjdGl2ZSBu
dWlzYW5jZSwgYW5kIHRoaXMgaXMgd2hhdCB0aGUgSUVURiBoYXMsIGFsYmVpdCB3aXRoPGJyPg0K
dGhlIGJlc3Qgb2YgaW50ZW50aW9ucywgbWFuYWdlZCB0byBjcmVhdGUuPG86cD48L286cD48L3A+
DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIHdvdWxkIGFk
ZCB0byB0aGlzIHRoYXQsIGJ5IGl0cyB1bHRpbWF0ZSBpbmFjdGlvbiBpbiB0aGUgZmFjZSBvZiBh
IHByb3RyYWN0ZWQgcGVyaW9kIG9mIGFidXNlIGFuZCBhdHRlbXB0cyBieSBwYXJ0aWNpcGFudHMg
dG8gc29sdmUgdGhhdCBwcm9ibGVtIHdpdGhpbiBpdHMgcHJvY2VkdXJlcywgdGhlIElFVEYgaGFz
IGFiZGljYXRlZCBhbnkgYXV0aG9yaXR5IGl0IG1heSBoYXZlIGhhZC48bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+TUg6IEnigJltIG5v
dCBzdXJlIEkgd291bGQgZ28gdGhpcyBmYXIgYnV0IEkgdGhpbmsgaXQgcmVmbGVjdHMgY29uY2Vy
bnMgaGVsZCBieSBtYW55LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQg
I0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0
O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIHJlYWwgcXVlc3Rp
b24gd2Ugc2hvdWxkIGJlIGRpc2N1c3NpbmcgaXMgd2hhdCBvcHRpb25zIHRoZSBJRVRGIGhhcyB0
byB0cnk8YnI+DQphbmQgYWRkcmVzcyB0aGlzLjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3Rl
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBjZXJ0YWlubHkgYWdyZWUgd2l0aCB0
aGF0Ljxicj4NCjxicj4NCjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+TUg6IEZpcnN0IHRoZXJlIG5lZWRzIHRvIGJlIGEgY29uc2Vuc3Vz
IGFzIHRvIHdoYXQg4oCcdGhpc+KAnSBpcyBiZWZvcmUgdGhlcmUgY2FuIGJlIGFuIGF0dGVtcHQg
dG8gYWRkcmVzcyDigJx0aGlz4oCdLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxicj4NCi1NU0sgPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D45BFBUSCLES544agnaam_--


From nobody Mon Apr 14 11:55:15 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD7261A06E8 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.599
X-Spam-Level: 
X-Spam-Status: No, score=-0.599 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 ev4VgXmPLs7b for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 11:55:08 -0700 (PDT)
Received: from mail-wg0-x22d.google.com (mail-wg0-x22d.google.com [IPv6:2a00:1450:400c:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 3214A1A0468 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:55:08 -0700 (PDT)
Received: by mail-wg0-f45.google.com with SMTP id l18so8720982wgh.16 for <ietf@ietf.org>; Mon, 14 Apr 2014 11:55:05 -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:content-type; bh=2Mt4+gD0Ew9nI6vNj0BSwfPJbxgtKRuyBFbO7DHYr6M=; b=UaZEfEwi9JCkeAqGmxzmrr4syaXcDumo1BgZArv+PW2LCCLp72HZTFZtCwdRnPTnzS TkkQa+KQgxnKZyMfc4PpGEhSB/X+tBjlIj0o4xEFFnjl5GkYB9Esb/KTEI9MhAP1dCU7 W2nwRfS1PgHC1qs8tV6Ofw/YiVDNq+WDHyiYD0dmpXdWSIZ6TWSRPcFmsaidgdzK8c+i lIDacXgmyfHxEZ7mdVdXZj6iOeeG42/AFTx/aZcpWsOHhIRWBmkuEqBa0rrljK4CV2Ln 6AlLDOl/g/ygGXyXoITymnEILrVQfe/R1E4BKkKdMH14CdxPGkhW1AU5KX34jSSQxv1C IeyA==
MIME-Version: 1.0
X-Received: by 10.180.211.116 with SMTP id nb20mr10786446wic.5.1397501705264;  Mon, 14 Apr 2014 11:55:05 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 11:55:05 -0700 (PDT)
In-Reply-To: <534C2D23.3050600@meetinghouse.net>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <534C2D23.3050600@meetinghouse.net>
Date: Mon, 14 Apr 2014 11:55:05 -0700
Message-ID: <CAL0qLwb-v2H8hh=D2prrmO_r4K9QohWcKsL7d_qf=18FFgFcHw@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=001a11c26ab4b7253c04f7053899
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ub6yS4mKzlzawGzBsm4XF1dj4Vk
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 18:55:10 -0000

--001a11c26ab4b7253c04f7053899
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 11:46 AM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:

> Does this, perhaps, illuminate a flaw or failing in the way IETFs effects
> its role as the Internet's official standards body?  The more so that it's
> not stepping in after the fact to help clear up this mess?
>

Possibly.  I confess I heard the reasons for rejecting the request, but I
still don't fully understand them.


> I do wonder if there's a related case study in the way that RSS evolved
> into Atom - a case where outside work, and conflicts within it, ended up
> being worked under the IETF aegis?  (Sort of  shame that Atom has not
> become more popular.)


I'm not familiar with the story of RSS, but I do know that XMPP and DKIM
are held up as cases where work was started externally and then brought
into the IETF and finished, so there are cases where it is indeed palatable
to the powers-that-be.

-MSK

--001a11c26ab4b7253c04f7053899
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 11:46 AM, Miles Fidelman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank=
">mfidelman@meetinghouse.net</a>&gt;</span> wrote:<br><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Does this, perhaps, illuminate a flaw or fai=
ling in the way IETFs effects its role as the Internet&#39;s official stand=
ards body? =C2=A0The more so that it&#39;s not stepping in after the fact t=
o help clear up this mess?<br>
</blockquote><div><br></div><div>Possibly.=C2=A0 I confess I heard the reas=
ons for rejecting the request, but I still don&#39;t fully understand them.=
<br>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">

I do wonder if there&#39;s a related case study in the way that RSS evolved=
 into Atom - a case where outside work, and conflicts within it, ended up b=
eing worked under the IETF aegis? =C2=A0(Sort of =C2=A0shame that Atom has =
not become more popular.)<span class=3D"HOEnZb"></span></blockquote>
<div><br></div><div>I&#39;m not familiar with the story of RSS, but I do kn=
ow that XMPP and DKIM are held up as cases where work was started externall=
y and then brought into the IETF and finished, so there are cases where it =
is indeed palatable to the powers-that-be.<br>
<br></div><div>-MSK<br></div></div></div></div>

--001a11c26ab4b7253c04f7053899--


From nobody Mon Apr 14 12:15:15 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE9D1A063F for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 12:15:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.018
X-Spam-Level: *
X-Spam-Status: No, score=1.018 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 kN1fmy2Q73W7 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 12:15:09 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id BE0DC1A04A1 for <ietf@ietf.org>; Mon, 14 Apr 2014 12:15:09 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id ECED3CC0BF for <ietf@ietf.org>; Mon, 14 Apr 2014 15:15:06 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id F0BLhzLFUONu for <ietf@ietf.org>; Mon, 14 Apr 2014 15:15:02 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 85312CC0BE for <ietf@ietf.org>; Mon, 14 Apr 2014 15:15:02 -0400 (EDT)
Message-ID: <534C33B6.9050909@meetinghouse.net>
Date: Mon, 14 Apr 2014 15:15:02 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org Disgust" <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net>	<5349A261.9040500@dcrocker.net> <CAHw9_iK85xZjpsw27OAmbJd5xFKL_roLcRdu++uquFwf7K4kaw@mail.gmail.com>
In-Reply-To: <CAHw9_iK85xZjpsw27OAmbJd5xFKL_roLcRdu++uquFwf7K4kaw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SPTCwYk3q5k3SHxWXL-WgvHXxh4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 19:15:13 -0000

Warren Kumari wrote:
> On Sat, Apr 12, 2014 at 4:30 PM, Dave Crocker <dhc@dcrocker.net> wrote:
>> On 4/12/2014 12:56 PM, Miles Fidelman wrote:
>>> - DMARC.org defines the "DMARC Base Specification" with a link to
>>> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/ - an IETF
>>> document
>>
>> While the Internet-Draft mechanism is operated by the IETF, it is an open
>> mechanism and issuance through it carries no automatic status, particularly
>> with respect to the IETF.
> It seems that folk often miss this particular point (see the recent
> drama about draft-loreto-httpbis-trusted-proxy20). Pointing at the
> boilerplate, explaining the fact that anyone (with an Internet
> connection and an XML editor) can submit an ID, etc doesn't seem to
> work. I considered pointing at, well, anything by Terrell, but instead
> decided to publish a draft :-P
>
> http://tools.ietf.org/html/draft-wkumari-not-a-draft-00
>

Well yes, but that's the "fine print."

Who ever reads a 20-page shrink-wrap license - and he jury is still out 
as to when those apply or can be ignored.  And then there's a "warrant 
of merchantability" that vendors can be held to despite all kinds of 
disclaimers buried in a license.

When the organization that coordinated and promulgated DMARC:
- describes their efforts as "their common goal was to develop an 
operational specification to be introduced to the IETF for standardization
- refers to the only defining document as a "Base Specification" and 
links to a document, on the IETF's webserver, with an IETF document number

It's kind of easy for the uninitiated to draw the conclusion that it's a 
standards-track IETF standard.

Then, when Yahoo defends the havoc they've wrought with statements like 
(they) "designed and built something called DMARC 
<http://www.dmarc.org/>, or Domain-based Message Authentication, 
Reporting and Conformance. Today, 80% of US email user accounts and over 
2B accounts globally can be protected by the DMARC standard." - with a 
pointer to dmarc.org - and from there to an IETF webserver and document 
-- it sure is easy for the general community to draw the conclusion 
"Yahoo implemented a vetted IETF standard - and it broke all the mailing 
lists I'm on."  And it sure is easy for someone to draw the conclusion 
that the fault lies with the broken standard, not with Yahoo.

You have to look hard to figure out who really broke what.  And (IMHO) 
one would not be wrong to draw the conclusion that IETF dropped the ball 
in its role as the Internet standards body - if only in it's relative 
silence (a disclaimer in the fine print does not constitute exercising 
one's professional or institutional responsibilities).

ISO, for example, has processes for complaining about mis-use of their 
standards, and about misrepresentation of being certified against a 
standard.  Perhaps it's time for IETF to institute similar policies and 
proceedures - beyond:
"it's not actually a standard - we just provided space for the document"
"it's a voluntary standard, we're not responsible if it's not 
implemented properly, or not deployed properly"

We all claim that we don't want governments to run the Internet - but 
when our voluntary, cooperative mechanisms drop the ball - that's the 
end result.  (Along with lots of litigation.)

Just one man's opinion, of course.

Miles Fidelman



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 12:22:40 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78F481A06C9 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 12:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 8UCgpHYELvD0 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 12:22:35 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 48D261A0666 for <ietf@ietf.org>; Mon, 14 Apr 2014 12:22:35 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.146.211]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3EJMGD9019530 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Apr 2014 12:22:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397503352; bh=m5ClO6YnkyaWPtesrOiSxIWNt/2GWVyWnAhNp+GAdkE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UPt9pb/dlfceqrsEAK4WtnZmM9RL+HzG2sqkRQNaa0eZZgSQjV8u6bLKVVdbsVjTw yEXqxXZ1ZCCmF8Nji0U3a8XyV1YRZTLZ9OD+1rvgVHMLVtymMSJqmgRfMGoxCjLQu0 ZvTq9+iGWK9a6qPyBuy9x3etmhZORclxh63+D2Gc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397503352; i=@elandsys.com; bh=m5ClO6YnkyaWPtesrOiSxIWNt/2GWVyWnAhNp+GAdkE=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=O/zWGxM8LMhYkudV/wah0qx8CATP3WaFMyEs+MnpFpS3zpDdpfC8GjaQLmySN6m+6 fw11Z4AinJNcsWqPdre0TbEAk8lmw0lGOyxfFUfdFL1LhGg3DSAhlIkt5mcva0SkQy aN04eRMLzxuvL9JTPcOaMFe8HyQLGyNOvOJVEMI8=
Message-Id: <6.2.5.6.2.20140414120949.0c15af68@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 Apr 2014 12:18:33 -0700
To: Miles Fidelman <mfidelman@meetinghouse.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534C2420.60801@meetinghouse.net>
References: <20140414024956.26078.qmail@joyce.lan> <534B4E97.2050000@meetinghouse.net> <CAL0qLwYHP-rVF5TmEH2_kTZ7bDnxms7md=Y8Voef9OyPD4Bj8Q@mail.gmail.com> <534C2420.60801@meetinghouse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6ERYA0_qW5gCJIsGQi2uADjjPCg
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 19:22:39 -0000

Hi Miles,
At 11:08 14-04-2014, Miles Fidelman wrote:
>Can anybody comment on the process by which mailing list control 
>headers (RFC 2919 and 2369) were coordinated?  Seems like there 
>might be some lessons to be learned.

I submitted draft-moonesamy-rfc2369bis-04 [1] and 
draft-moonesamy-rfc2919bis-04 [2] in 2012.  Due to difficulties in an 
IETF working group I did not have any time left to focus on those 
drafts.  The process is to get one of the Applications Area Director 
to sponsor the draft.

Regards,
S. Moonesamy

1. http://tools.ietf.org/html/draft-moonesamy-rfc2369bis-04
2. http://tools.ietf.org/html/draft-moonesamy-rfc2919bis-04 


From nobody Mon Apr 14 13:25:35 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31CB71A066F for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 13:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 gg0MzssqexJe for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 13:25:29 -0700 (PDT)
Received: from mail-yh0-x22a.google.com (mail-yh0-x22a.google.com [IPv6:2607:f8b0:4002:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id D43701A0473 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:25:28 -0700 (PDT)
Received: by mail-yh0-f42.google.com with SMTP id t59so8590981yho.1 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:25: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:from:date:message-id :subject:to:cc:content-type; bh=3JgjJFYHjnFmRbAG4eI9D7MSgYIiqKbGo0hvPWKA6v0=; b=KDnQdz5UC5wFoG5SKfw6xZlGDwi8JZTSqEfbCbyJ6ohqXZJMqg9Gr75WzEkUwB2uHw 4AFoj52864MPgb2P1HlL1iwTNhmDX5BAcAese5zyRQdJBdPEdVU03t6s3oI7cie3glny yE2TEZexD1zDNTKceo4fiJtlDB2gPFYLF+guTeKFlRqqQANptuT08lBpllJQ127edJMO wsAuMP0ezJpi1Abn3aK6Cu0NZyer9fnyBl6xqCSG40RY95uGGn4GawkHbcBYtjy35Qt4 65rR38JysdppfsytR4GmBBMzTRBiPzwNHxW85ysKfYqSVlz2C0I9wHVcW0x8oeBZ50h6 i39g==
X-Received: by 10.236.32.178 with SMTP id o38mr5891426yha.119.1397507126211; Mon, 14 Apr 2014 13:25:26 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Mon, 14 Apr 2014 13:24:46 -0700 (PDT)
In-Reply-To: <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com>
From: Dick Franks <rwfranks@acm.org>
Date: Mon, 14 Apr 2014 21:24:46 +0100
X-Google-Sender-Auth: lZLM6abBB3Lw3tfrXeqYjWiL3xc
Message-ID: <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=089e0158cb52d4540104f7067ba3
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1-aW83br3Ml1WF7lw6LZBy4sNLc
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 20:25:33 -0000

--089e0158cb52d4540104f7067ba3
Content-Type: text/plain; charset=UTF-8

On 14 April 2014 19:03, Murray S. Kucherawy <superuser@gmail.com> wrote:

> On Mon, Apr 14, 2014 at 11:01 AM, Miles Fidelman <
> mfidelman@meetinghouse.net> wrote:
>
>
>>
>>> A more pragmatic, less expensive, and publicly visible expression of
>>> IETF displeasure might be to expunge all versions of the offending I-D from
>>> IETF document store and refuse to publish any subsequent version until the
>>> unwarranted claims made for it are retracted.
>>>
>>> To be effective, that needs to be done now, while the iron is still hot;
>>> not after the usual 3-month email debate about the diplomatic niceties.
>>>
>>>  The later, accompanied with a strong statement about the limits of
>> DMARC, and the flaws in its deployment - might not be a bad start.
>>
>
> What real-world effect is this supposed to have, apart from setting a very
> dangerous precedent?
>
>
1)  Invalidates the inappropriate document citations on DMARC site.

2)  Publicly refutes any claim that this is an IETF standardisation effort.


Robust action in defence of IETF reputation is possibly a precedent worth
setting.

--089e0158cb52d4540104f7067ba3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On 14 April 2014 19:03, Murray S. Kucherawy <span dir=3D"ltr">&lt;<a href=
=3D"mailto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a>&g=
t;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>On Mon, Apr 14, 2014 a=
t 11:01 AM, Miles Fidelman <span dir=3D"ltr">&lt;<a href=3D"mailto:mfidelma=
n@meetinghouse.net" target=3D"_blank">mfidelman@meetinghouse.net</a>&gt;</s=
pan> wrote:<br>



</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>

<br>
A more pragmatic, less expensive, and publicly visible expression of IETF d=
ispleasure might be to expunge all versions of the offending I-D from IETF =
document store and refuse to publish any subsequent version until the unwar=
ranted claims made for it are retracted.<br>





<br>
To be effective, that needs to be done now, while the iron is still hot; no=
t after the usual 3-month email debate about the diplomatic niceties.<br>
<br>
</div></blockquote>
The later, accompanied with a strong statement about the limits of DMARC, a=
nd the flaws in its deployment - might not be a bad start.<span><font color=
=3D"#888888"><br>
</font></span></blockquote><div><br></div></div><div>What real-world effect=
 is this supposed to have, apart from setting a very dangerous precedent?<s=
pan><font color=3D"#888888"><br><br></font></span></div><span></span></div>



</div></div></blockquote><div><br></div><div>1)=C2=A0 Invalidates the inapp=
ropriate document citations on DMARC site.<br><br></div><div>2)=C2=A0 Publi=
cly refutes any claim that this is an IETF standardisation effort.<br><br><=
br></div>



<div>Robust action in defence of IETF reputation is possibly a precedent wo=
rth setting.<br><br></div><div>=C2=A0<br><br></div></div><br></div></div>

--089e0158cb52d4540104f7067ba3--


From nobody Mon Apr 14 13:39:55 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85AAD1A070D for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 13:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 3ztxwAJzUoOT for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 13:39:53 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 988081A06F8 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:39:53 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id x10so8496111pdj.20 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:39:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1pabkP6xN62Q4LiCOGX3v0SPV5NnVlcaC5DC9pKD3pQ=; b=rZrKWCogijVIveIz0+J04muhFpKckZkOxU5RX2ZDXTvmw/m7mtDbV/QagJC0F/8gSE 9bn3GBT6WfgmPRNHpSEv6CwQlTavlMDKcexJQEYzFi+1QSXx10dw9nFOA8sNl8TgeiDJ YWpHnPW7kiuXpqWSL6ltgROeor8+EpbX9wkVxGZhwYorS7ORPGzNB/2KPJXZsMQ1sjgj rcC7EttM6GnsWZP5TIe7yjFEaJApTNtvZS24xeBft1EuMqEW5Hm8nHbQmKFI660j5ytQ /LaTakpt0erg59AXpGQr+5ibNgVCOTS5eiwf/5CrZh/dtfXahCZMfPFm5OXwiF2M3Y7p yfrQ==
X-Received: by 10.68.196.168 with SMTP id in8mr5492475pbc.132.1397507991170; Mon, 14 Apr 2014 13:39:51 -0700 (PDT)
Received: from [192.168.178.20] (172.200.69.111.dynamic.snap.net.nz. [111.69.200.172]) by mx.google.com with ESMTPSA id n6sm35681499pbj.22.2014.04.14.13.39.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Apr 2014 13:39:50 -0700 (PDT)
Message-ID: <534C4794.5000600@gmail.com>
Date: Tue, 15 Apr 2014 08:39:48 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
In-Reply-To: <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7aaoqbXukcJFlWHVrY7XJ1uliDg
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 20:39:54 -0000

Murray,

On 15/04/2014 05:26, Murray S. Kucherawy wrote:
...
> The DMARC proponents did engage mailman.   Version 2.1.16 includes support
> for a setting that makes the operation of the list DMARC-friendly, though
> likely in a way some people will find unpalatable. 

Please tell us more about that.

    Brian


From nobody Mon Apr 14 13:46:19 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F5C1A0672 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 13:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 4yCBcojUf6RQ for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 13:46:15 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 255C81A021F for <ietf@ietf.org>; Mon, 14 Apr 2014 13:46:15 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id fa1so8662246pad.14 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=B6g0/67B2nruIJh6/3JOzr+JT1xWTDYsQror1ie4Z6M=; b=CQB4BqqoyQWH54Xq7F1OtgHM60s/J+dlmeOYffuw+f8B2Cr2c9JtdS+j10W5xi/13i QDnxLh/TEtdcRWazCAhGHlJxThJ7IfAxao15ch/Xg1I6+xJzrlRfzkvWAsbhDdOxBwaq bUxfeuOYm/IhuhNlkIpzkNkBeZ/nBQkUGGpZ39RzeScUPglBPtFII9Nr932aHK9sjQlO EKv2mnGFa2e5ODce1QBVudPso/jJYigxGtuY4/tYFpbtGuK8VVC7YyDgXsSfhiQlMUVi rtT6RJ7tE+mHwNc64LB151BlW53iIhBm+pRr0StfFvTA3doeKdJbpLgWdyXVG3P1zYwk hbfA==
X-Received: by 10.68.212.10 with SMTP id ng10mr46420249pbc.95.1397508372705; Mon, 14 Apr 2014 13:46:12 -0700 (PDT)
Received: from [192.168.178.20] (172.200.69.111.dynamic.snap.net.nz. [111.69.200.172]) by mx.google.com with ESMTPSA id ov4sm31113367pbc.46.2014.04.14.13.46.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Apr 2014 13:46:11 -0700 (PDT)
Message-ID: <534C4912.9010705@gmail.com>
Date: Tue, 15 Apr 2014 08:46:10 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Dick Franks <rwfranks@acm.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com>
In-Reply-To: <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2nSZKtS90vHw4Hqx2H8Cx6_eoWo
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 20:46:16 -0000

On 15/04/2014 08:24, Dick Franks wrote:
> On 14 April 2014 19:03, Murray S. Kucherawy <superuser@gmail.com> wrote:
> 
>> On Mon, Apr 14, 2014 at 11:01 AM, Miles Fidelman <
>> mfidelman@meetinghouse.net> wrote:
>>
>>
>>>> A more pragmatic, less expensive, and publicly visible expression of
>>>> IETF displeasure might be to expunge all versions of the offending I-D from
>>>> IETF document store and refuse to publish any subsequent version until the
>>>> unwarranted claims made for it are retracted.
>>>>
>>>> To be effective, that needs to be done now, while the iron is still hot;
>>>> not after the usual 3-month email debate about the diplomatic niceties.
>>>>
>>>>  The later, accompanied with a strong statement about the limits of
>>> DMARC, and the flaws in its deployment - might not be a bad start.
>>>
>> What real-world effect is this supposed to have, apart from setting a very
>> dangerous precedent?
>>
>>
> 1)  Invalidates the inappropriate document citations on DMARC site.
> 
> 2)  Publicly refutes any claim that this is an IETF standardisation effort.
> 
> 
> Robust action in defence of IETF reputation is possibly a precedent worth
> setting.

Not at the price of looking like censorship and distorting the
historical record.

We have very carefully designed boilerplate, and the point of
boilerplate is precisely that it's there even if people don't
read it. We're an open voluntary standards organisation;
we're still not the Internet Police.

I'm strongly against removing drafts from the public record unless
they are obscene or libellous.

   Brian


From nobody Mon Apr 14 13:54:39 2014
Return-Path: <R.E.Sonneveld@sonnection.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B24441A0643 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 13:54:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.6
X-Spam-Level: 
X-Spam-Status: No, score=0.6 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 21ISWpDFUhuR for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 13:54:26 -0700 (PDT)
Received: from mx20.mailtransaction.com (mx20.mailtransaction.com [78.46.16.213]) by ietfa.amsl.com (Postfix) with ESMTP id 5DFFA1A0574 for <ietf@ietf.org>; Mon, 14 Apr 2014 13:54:26 -0700 (PDT)
Received: from mx24.mailtransaction.com (mx21.mailtransaction.com [78.46.16.236]) by mx20.mailtransaction.com (Postfix) with ESMTP id 3g72BR0HmPz1L8g4; Mon, 14 Apr 2014 22:54:23 +0200 (CEST)
Received: from jaguar.sonnection.nl (D57E1702.static.ziggozakelijk.nl [213.126.23.2]) by mx24.mailtransaction.com (Postfix) with ESMTP id 3g72BQ5nFcz1L8cK; Mon, 14 Apr 2014 22:54:22 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by jaguar.sonnection.nl (Postfix) with ESMTP id 89237122EAB; Mon, 14 Apr 2014 22:54:22 +0200 (CEST)
X-Virus-Scanned: amavisd-new at sonnection.nl
Received: from jaguar.sonnection.nl ([127.0.0.1]) by localhost (jaguar.sonnection.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id KhQ3FbPmiHww; Mon, 14 Apr 2014 22:54:17 +0200 (CEST)
Received: from [192.168.1.49] (unknown [192.168.1.49]) by jaguar.sonnection.nl (Postfix) with ESMTPSA id CE5D0122E8C; Mon, 14 Apr 2014 22:54:16 +0200 (CEST)
Message-ID: <534C4AF8.60709@sonnection.nl>
Date: Mon, 14 Apr 2014 22:54:16 +0200
From: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
Organization: Sonnection B.V.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>,  "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
In-Reply-To: <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090508010002030103000205"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sonnection.nl; s=2009; t=1397508863; bh=pHOxCxi+zLzeHhZH80Cf43yZb9GB9Upx6WBfrarc2o4=; h=Message-ID:Date:From:To:Subject:From; b=JD32VvITdVLT9mKPu5M6Vmyy9ywYTsIWFwTfcEPC3EPKCPU9NLyb1Akf9XX9hL2Qf qwx2Gk3fO3Xc5g2cHvy+QgTgmzvubGy51OqKMAHHMdWBPChB1aReaAKN5VV4qPWgM1 W1EKo+Xrn5d6e5YJ4NOXCeL8kp4oIvH+kGRSk5wE=
DKIM-Filter: OpenDKIM Filter v2.8.2 mx20.mailtransaction.com 3g72BR0HmPz1L8g4
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CH4uLmnEZ4AGCVjQgDX1XwsZM0g
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: R.E.Sonneveld@sonnection.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 20:54:31 -0000

This is a multi-part message in MIME format.
--------------090508010002030103000205
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 04/14/2014 07:53 PM, Murray S. Kucherawy wrote:
> On Sat, Apr 12, 2014 at 4:35 PM, <ned+ietf@mauve.mrochek.com 
> <mailto:ned+ietf@mauve.mrochek.com>> wrote:
>
>     The underlying technical issue is that the two technologies DMARC
>     is built on -
>     DKIM and SPF - both attach additional/restrictive semantics to
>     longstanding mail
>     system fields. (Broadly speaking, From: for DKIM and MAIL FROM for
>     SPF.)
>
> Something's amiss here.  What new semantics does DKIM attach to 
> From:?  As far as I know, it only requires that the field be signed.  
> It doesn't require that it be interpreted in a particular way or that 
> it contain any particular value.
>
>     It goes on to discuss the use of p=reject with domains that only send
>     transactional. AFAICT there is no discussion of when *not* to use
>     p=reject, and
>     why. Nor, for that matter is there substantive discussion of
>     mailing_list,
>     and why it's not a general solution to the problems caused by
>     p=reject.
>
>
> Yes, that's useful advice for a future revision.
>
>     Like it or not, the IETF published a draft that defines certain
>     mechanisms
>     which, if used improperly by a large provider, cause serious
>     problems for a
>     large number of people. The text describing the consequences of
>     the use of
>     those mechansisms in the drafts is, IMO, entirely inadequate.
>
>
> It's the same document that was posted on other web sites for some 
> time, and was in use by a number of operators (including Yahoo) long 
> before it went into the datatracker.
>
> As it's only a draft, there's ample opportunity to make such improvements.
>
> Also: By "the IETF published a draft", are you talking about an RFC, 
> or the DMARC base draft?  It seems extreme to lay blame on the IETF in 
> general merely for having an open mechanism by which to post a draft 
> for all to see and discuss.  A "Request For Comment", as it were.  Are 
> you suggesting that process should be closed or moderated somehow?
>
>     And it's not like we didn't know. As others have pointed out, this
>     issue
>     existed in the earlier ADSP proposal. It was given insufficient
>     attention there
>     as well.
>
>
> As with any draft, its content is only as good as its contributions 
> and the reviews it got.
>
>     Of course the IETF can fall back on the usual excuses, including,
>     but not
>     limited to:
>
>         Yahoo, of all ISPs, should have known better
>         We don't tell people what to do
>         It was just a draft
>         It was never intended to be a standard
>         We're not the Internet Protocol Police
>         etc.
>
>     I'm sorry, but this time none of these dogs are hunting for me. An
>     attractive
>     nuisance is an attractive nuisance, and this is what the IETF has,
>     albeit with
>     the best of intentions, managed to create.
>
>
> I would add to this that, by its ultimate inaction in the face of a 
> protracted period of abuse and attempts by participants to solve that 
> problem within its procedures, the IETF has abdicated any authority it 
> may have had.

This might have been true if:

1. Yahoo _did_ solve the abuse problem and
2. the decision making process within a closed industry consortium with 
maybe less than 20 members, representing immense commercial power, could 
be compared to the process of consensus, that's being used within IETF.

Ad 1. Yahoo only solved some of the problem, for some time and only for 
themselves. But we have seen that bad guys have adapted faster than 
anyone else to new technologies:
- 90% of all mail agents show the display-name in the From field and 
with the current move towards mobile devices this percentage will likely 
further increase;
- Yahoo doesn't use the From:From construct to enable receivers to 
detect use of multiple From: fields;
- developments like EAI will help bad guys to find lookalike 
domains/cousin domains [1], [2]
Ad 2. I assume this doesn't need further explanation.

/rolf

[1] http://www.ietf.org/mail-archive/web/dmarc/current/msg00370.html
[2] http://en.wikipedia.org/wiki/IDN_homograph_attack


--------------090508010002030103000205
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Ty=
pe">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">On 04/14/2014 07:53 PM, Murray S.
      Kucherawy wrote:<br>
    </div>
    <blockquote
cite=3D"mid:CAL0qLwZr=3DwVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gm=
ail.com"
      type=3D"cite">
      <div dir=3D"ltr">On Sat, Apr 12, 2014 at 4:35 PM, <span dir=3D"ltr"=
>&lt;<a
            moz-do-not-send=3D"true"
            href=3D"mailto:ned+ietf@mauve.mrochek.com" target=3D"_blank">=
ned+ietf@mauve.mrochek.com</a>&gt;</span>
        wrote:<br>
        <div class=3D"gmail_extra">
          <div class=3D"gmail_quote">
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">The underlying
              technical issue is that the two technologies DMARC is
              built on -<br>
              DKIM and SPF - both attach additional/restrictive
              semantics to longstanding mail<br>
              system fields. (Broadly speaking, From: for DKIM and MAIL
              FROM for SPF.)<br>
            </blockquote>
            <div>=C2=A0</div>
            <div>Something's amiss here.=C2=A0 What new semantics does DK=
IM
              attach to From:?=C2=A0 As far as I know, it only requires t=
hat
              the field be signed.=C2=A0 It doesn't require that it be
              interpreted in a particular way or that it contain any
              particular value.<br>
              <div>=C2=A0<br>
              </div>
            </div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              It goes on to discuss the use of p=3Dreject with domains
              that only send<br>
              transactional. AFAICT there is no discussion of when *not*
              to use p=3Dreject, and<br>
              why. Nor, for that matter is there substantive discussion
              of mailing_list,<br>
              and why it's not a general solution to the problems caused
              by p=3Dreject.<br>
            </blockquote>
            <div>
              <div><br>
              </div>
              <div>Yes, that's useful advice for a future revision.<br>
              </div>
              =C2=A0
              <br>
            </div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              Like it or not, the IETF published a draft that defines
              certain mechanisms<br>
              which, if used improperly by a large provider, cause
              serious problems for a<br>
              large number of people. The text describing the
              consequences of the use of<br>
              those mechansisms in the drafts is, IMO, entirely
              inadequate.<br>
            </blockquote>
            <div><br>
            </div>
            <div>It's the same document that was posted on other web
              sites for some time, and was in use by a number of
              operators (including Yahoo) long before it went into the
              datatracker.<br>
              <br>
            </div>
            <div>As it's only a draft, there's ample opportunity to make
              such improvements.<br>
              <br>
              <div>Also: By "the IETF published a draft", are you
                talking about an RFC, or the DMARC base draft?=C2=A0 It s=
eems
                extreme to lay blame on the IETF in general merely for
                having an open mechanism by which to post a draft for
                all to see and discuss.=C2=A0 A "Request For Comment", as=
 it
                were.=C2=A0 Are you suggesting that process should be clo=
sed
                or moderated somehow?<br>
              </div>
              =C2=A0</div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              And it's not like we didn't know. As others have pointed
              out, this issue<br>
              existed in the earlier ADSP proposal. It was given
              insufficient attention there<br>
              as well.<br>
            </blockquote>
            <div><br>
            </div>
            <div>As with any draft, its content is only as good as its
              contributions and the reviews it got.<br>
              =C2=A0<br>
            </div>
            <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              Of course the IETF can fall back on the usual excuses,
              including, but not<br>
              limited to:<br>
              <br>
              =C2=A0 =C2=A0 Yahoo, of all ISPs, should have known better<=
br>
              =C2=A0 =C2=A0 We don't tell people what to do<br>
              =C2=A0 =C2=A0 It was just a draft<br>
              =C2=A0 =C2=A0 It was never intended to be a standard<br>
              =C2=A0 =C2=A0 We're not the Internet Protocol Police<br>
              =C2=A0 =C2=A0 etc.<br>
              <br>
              I'm sorry, but this time none of these dogs are hunting
              for me. An attractive<br>
              nuisance is an attractive nuisance, and this is what the
              IETF has, albeit with<br>
              the best of intentions, managed to create.<br>
            </blockquote>
            <div><br>
            </div>
            <div>I would add to this that, by its ultimate inaction in
              the face of a protracted period of abuse and attempts by
              participants to solve that problem within its procedures,
              the IETF has abdicated any authority it may have had.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    This might have been true if:<br>
    <br>
    1. Yahoo _did_ solve the abuse problem and <br>
    2. the decision making process within a closed industry consortium
    with maybe less than 20 members, representing immense commercial
    power, could be compared to the process of consensus, that's being
    used within IETF.<br>
    <br>
    Ad 1. Yahoo only solved some of the problem, for some time and only
    for themselves. But we have seen that bad guys have adapted faster
    than anyone else to new technologies:<br>
    - 90% of all mail agents show the display-name in the From field and
    with the current move towards mobile devices this percentage will
    likely further increase;<br>
    - Yahoo doesn't use the From:From construct to enable receivers to
    detect use of multiple From: fields;<br>
    - developments like EAI will help bad guys to find lookalike
    domains/cousin domains [1], [2]<br>
    Ad 2. I assume this doesn't need further explanation.<br>
    <br>
    /rolf<br>
    <br>
    [1] <a class=3D"moz-txt-link-freetext" href=3D"http://www.ietf.org/ma=
il-archive/web/dmarc/current/msg00370.html">http://www.ietf.org/mail-arch=
ive/web/dmarc/current/msg00370.html</a><br>
    [2] <a class=3D"moz-txt-link-freetext" href=3D"http://en.wikipedia.or=
g/wiki/IDN_homograph_attack">http://en.wikipedia.org/wiki/IDN_homograph_a=
ttack</a><br>
    <br>
  </body>
</html>

--------------090508010002030103000205--


From nobody Mon Apr 14 14:01:11 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEF711A0208 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:01:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.463
X-Spam-Level: 
X-Spam-Status: No, score=-1.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_DKIM_INVALID=0.01] autolearn=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 VlpbAlnigwKo for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:01:05 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF0A1A0652 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:01:04 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WZnzx-0003Nx-Se; Mon, 14 Apr 2014 21:01:01 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 3260958026D; Mon, 14 Apr 2014 17:00:59 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1397509259; bh=ock5oGy3KiZRJpzUt+z/lZVPv47h2p1va2fLgi9yYY8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=UA8mZtHbQ165+eLMBqXyzaXHSq0YhxcRv9eOxtPqt7HAAN0EE2vHjtX/M+BbOoOyB vUBzlXaz5B0t/z8OyQi1xhhvkb3grHQBCsfnwcKD3jGBPd1VqA7dtwod/XqNnAFr0d NDepkrsrue9KtKg2EDkXsnmha82OYyOJ5rUgNyuM=
Date: Mon, 14 Apr 2014 17:00:59 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <20140414210059.GA8345@thunk.org>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <534C4794.5000600@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534C4794.5000600@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rqqq4NdvyWhWvw6ghT7u95j30RA
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:01:09 -0000

On Tue, Apr 15, 2014 at 08:39:48AM +1200, Brian E Carpenter wrote:
> Murray,
> 
> On 15/04/2014 05:26, Murray S. Kucherawy wrote:
> ...
> > The DMARC proponents did engage mailman.   Version 2.1.16 includes support
> > for a setting that makes the operation of the list DMARC-friendly, though
> > likely in a way some people will find unpalatable. 
> 
> Please tell us more about that.

>From what I can tell, it has an option which you can replace the From
field with the original sender's from field with the mailing list's
e-mail address.   i.e., instead of:

From: Brian E Carpenter <brian.e.carpenter@gmail.com>

it would instead be;

From: IETF <ietf@ietf.org>

Any SPF or DKIM fields would also get stripped, and the original from
field would be moved elsewhere (it's not clear from reading the
description whether it's to some other header field, i.e.,
"X-Original-From" or to the body of the e-mail.



The solution I would prefer is one where mailman look up the DMARC
record, and if it's p=reject, it could rewrite the email from:

From: Brian E Carpenter <brian.e.carpenter@yahoo.com>

to something like:

From: Brian E Carpenter <brian.e.carpenter@yahoo.com.INVALID>

(or maybe instead of yahoo.com.INVALID, it should be "yahoo.com.BREAKS.MAILING.LISTS" :-)

    	  	     			   	  - Ted


From nobody Mon Apr 14 14:02:14 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97F9D1A066A for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:02:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.398
X-Spam-Level: *
X-Spam-Status: No, score=1.398 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 I91V39TboOaz for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:02:09 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 538261A0447 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:02:08 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 25471CC0AB for <ietf@ietf.org>; Mon, 14 Apr 2014 17:02:04 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 9g10Od9S47AU for <ietf@ietf.org>; Mon, 14 Apr 2014 17:01:59 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7231ECC084 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:01:59 -0400 (EDT)
Message-ID: <534C4CC7.1060900@meetinghouse.net>
Date: Mon, 14 Apr 2014 17:01:59 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/E-C2oY6saLwUukcfNfL593B5_lU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:02:12 -0000

Mike,

Thanks for the history lesson.  It does seem to highlight some=20
brokenness in the process, though.

Miles

MH Michael Hammer (5304) wrote:
> First an introduction, I've been active in IETF email and email authent=
ication working groups (As well as in other forums) for quite a number of=
 years but have not been active in IETF from an organizational perspectiv=
e. I was recently given a heads up about the discussion on the IETF list =
and joined as well as reviewed the archives related to this discussion. I=
 recognize a number of participants here from other arenas although the m=
ajority of participants are not familiar to me. Full disclosure:
>
> 1)  I represent my organization as a member of DMARC.ORG but I do not s=
peak on behalf of DMARC.ORG;
> 2) My comments here unless otherwise specifically stated represent my o=
wn opinions and are not a statement representing my employer.
> 3) While I currently moderate various mail lists, I do not administer t=
hem from a technical perspective, although I have in the past.
>
> I'd like to also provide to a blog post of mine on CircleID from 2009 -=
 http://www.circleid.com/posts/20090414_thoughts_on_future_of_email_authe=
ntication/ as well as a response from Dave Crocker - http://www.circleid.=
com/posts/20090422_thoughts_on_email_authentication_trust/. I believe the=
se are as relevant to the discussion today as they were back then (pre-DM=
ARC). There are not simple issues involved despite some of the pronouncem=
ents I've seen and there are not likely to be simple solutions other than=
 local policy ones that work locally.
>
> Additional Comments in-line.
>
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Miles Fidelman
>> Sent: Monday, April 14, 2014 11:09 AM
>> To: ietf@ietf.org
>> Subject: Re: DMARC: perspectives from a listadmin of large open-source=
 lists
>>
>> Doug Barton wrote:
>>
>> <snip>
>>>
>>> But your point is well taken ... the "right" answer may be to fix or
>>> discard DMARC, I honestly don't know. But in a world where DMARC is
>>> here to stay, or if not DMARC then some other anti-spam solution that=

>>> breaks mailing list forwarding; and in that same world where mailing
>>> list traffic is negligible (and therefore the cost of breaking mailin=
g
>>> lists is in the noise compared to the benefits of deploying said
>>> anti-spam solution) it's incumbent on the mailing list software folks=

>>> to solve this problem
> DMARC has been shown to work extremely well for specific implementation=
s in terms of mitigating direct domain abuse. The DMARC specification was=
 derived from private-channel arrangements between some senders and mailb=
ox providers that started developing in roughly the 2007 timeframe. The i=
mpetus for DMARC (and predecessor efforts) was to leverage what was essen=
tially a set of private relationships that were working to create an open=
 standard that would be available for anyone to implement, regardless of =
size. Mail Lists were identified as a potential issue but the initial set=
 of sending domains did not involve domains with end users and in all of =
the efforts, this was considered an edge case.
>
> My own analysis - for internal consumption within my organization - whi=
ch dates back to 2004 following the FTC email authentication workshop, th=
e FTC anti-spam workshop and the DKIM "organizational" dinner that follow=
ed, was that if email authentication gained any sort of traction in the w=
ild there would be increasing pressure on domains such as ours (greeting =
cards/social expressions) and Mail Lists, which did not conform to whatev=
er email authentication standards evolved. If we were going to change our=
 practices, I preferred to do so in a planned manner rather than as a res=
ult of a change forced by someone else's decision that would force us to =
react in a short timeframe and under the gun.
>
> This was one of the reasons that we changed our organizational practice=
s from spoofing (yes, I know that Dave Crocker objects to this term but u=
ntil we have a better one that gains a consensus I will continue to use i=
t) to sending mail using our own website domains as of the end of 2007/be=
ginning of 2008 depending on the website domain.
>
>> Is it perhaps also incumbent on the folks promulgating DMARC (and its
>> predecessors, and its sure-to-be successors) to work cooperatively wit=
h
>> mailing list developers, rather than taking the position "nope, we bre=
ak
>> mailing lists, not our problem?"
>>
> The fact is that a vocal constituency led by John Levine made it extrem=
ely clear that MLMs were out of scope and there was zero interest on the =
part of the MLM community in discussing ways in which MLMs could be made =
to work in an email authentication framework even if there were any MLM o=
perators willing to do so. His stated solution has been and continues to =
be that list operators should drop any participants who post from a domai=
n publishing p=3Dreject and to prevent any new participants from joining =
from a domain that publishes p=3Dreject. The record is quite clear on thi=
s and is available to anyone who wishes to peruse email archives, blog po=
sts, etc. I view this as local policy and up to the list operator. I'm no=
t confident how well this will ultimately work for many organizations the=
 operators manage lists for. Just to be clear, the preceding is more of a=
 question than an assertion.
>
> This was also a point of contention within the DKIM working group with =
regard to ADSP and if memory serves me correctly it even came up earlier =
in the MARID working group as part of the discussion surrounding SenderID=
 and the use of the "Sender" field. I don't intend my statements to lay b=
lame or be pejorative. It is what it is. The folks pursuing email authent=
ication standards and practices publicly noted the potential issues and f=
ocused on other areas. It was NOT a position of "nope, we break mailing l=
ists, not our problem?", it was a position of not getting into a painful =
fight over something that many viewed as an edge case while continuing to=
 pursue the stated email authentication goals. I was personally willing t=
o kick the can down the road and respect the MLM operator position as exp=
ressed by John and others.
>
> I also note a comment in another IETF thread:  Re: "why I quit writing =
internet standards". The comment is: "For instance, had DMARC proponents =
and/or Yahoo, spent some time making sure that there was some running cod=
e for mailing list use, life would be better." My response is that if the=
 MLM community, as led by John Levine, had expressed an interest (rather =
than a stone wall effort) in finding ways of making MLMs compatible then =
there just might have been running code available at an earlier point and=
 yes, life would currently be better. If the position that John has taken=
 and publicly advocated does not represent the MLM developer and operator=
 community position then I'd appreciate folks speaking up because that is=
 the only position which has been communicated - and very stridently. Aga=
in, I am NOT advocating that MLM developers and operators must change. I =
am simply stating that no rational person pursuing email authentication s=
tandards and practices development would willingly walk into this buzzsaw=
 absent an expression of interest on the part of MLM developers and opera=
tors.
>
>> I'm kind of coming to the conclusion that what we need to be looking a=
t is
>> defining an SMTP extension that addresses BOTH sets of concerns - and
>> doing so in a cooperative manner that engages not just the community
>> behind DKIM and DMARC, but also the developers and operators of
>> mailman, sympa, majordomo, listserv - and ideally the sendmail, postfi=
x,
>> exim, qmail community.
>>
> I don't know whether it is possible to find a solution by modifying cur=
rent implementation practices or if there is a need for an SMTP extension=
=2E Franck Martin has posted in a few places a list of MLMs and how they =
can work (depending on version, configuration, etc) in a DMARC/email auth=
entication context (I don't believe he has done so here). I have not look=
ed into the specifics of the MLM issue deep enough to make any meaningful=
 comments as to what might be done, if anything. I'm also not interested =
in getting involved in such an effort if there is a vocal constituency wi=
thin IETF claiming that any such discussion or effort is an attempt to fo=
rce MLM developers and operators to change how MLMs function and operate.=
 My personal ox isn't getting gored here and I'm not that much of a masoc=
hist that I would choose to engage in such a process under those circumst=
ances.
>
>> Dare I suggest that this calls for an IETF working group?
>>
> Suggest away but the notion of such a group, unless well wrangled and w=
ith a well-defined charter, brings back memories of the MARID working gro=
up and its outcome.
>
>> Miles Fidelman
>>
> Mike


--=20
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra



From nobody Mon Apr 14 14:09:04 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC271A0493 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:09:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.022
X-Spam-Level: 
X-Spam-Status: No, score=0.022 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 D3IqMjzj_FDD for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:08:58 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3F73B1A0397 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:08:58 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id wp18so9626954obc.23 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:08:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u4AzSgFbsMIgsp9b0/sSIWRceHANvhE4KSpKxat4owE=; b=FDR76YgHHEpILoPakN8EYMs6GFjjSJmT7TkF2wvTacOqnAWCg8w0gSXqGYe7skmoTC RG8esleMEnnys3rzQZaMwjNaFmedDHqTxSAnuRTSWKLHSO9d2aQL/JFiZVEExpEwB/jc KWrFaPxt6B+Ee2TRtzDKcB52MQ3SUcGEeFEAY=
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:content-type; bh=u4AzSgFbsMIgsp9b0/sSIWRceHANvhE4KSpKxat4owE=; b=MY+WOIjLIESo37VcLSlN7K46EwoXXIooZusY/hXjttZcAvRSNsKOB41PNpZoE80swU HIKcLwTePKzCPzHHcX+WU4aD6LvBmdJ34KP0hI+WXzMOpguAtdFWLU7ihYtDN+KawYua M7AiS9nrTbjDHweLC0QrTlhgss8ok6EpArfYnIS5QjyXLjIGD9rgGQ9Re897JS9N+YOc qk+7SRHDa3L76dAiPi6kDxStU81uO+w1GB980HAslxuERd61uqg35ieNv5fvfqp+Gk/m zm9DtIgqc04qGzWNdOh5dYlU71kj1FcH4VsX5+TA9Zs362KEWTOqnujmOdKaezTKGXNq IeOw==
X-Gm-Message-State: ALoCoQnCXQ+VDIyMcQiVEo5Y6X1sO1xUy24aEDIiJH+MI9u1A7acOcG74Tzlrz4kUe9ay37ob9jP
MIME-Version: 1.0
X-Received: by 10.182.33.73 with SMTP id p9mr35910488obi.37.1397509735584; Mon, 14 Apr 2014 14:08:55 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Mon, 14 Apr 2014 14:08:55 -0700 (PDT)
In-Reply-To: <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
Date: Mon, 14 Apr 2014 22:08:55 +0100
Message-ID: <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Dave Cridland <dave@cridland.net>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d58b45c2cfd04f7071729
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GYBcKeqEq8Nj8K0hZ3Xkshg5oRM
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:09:02 -0000

--047d7b5d58b45c2cfd04f7071729
Content-Type: text/plain; charset=UTF-8

On 14 April 2014 18:26, Murray S. Kucherawy <superuser@gmail.com> wrote:

> I mentioned in another thread that the DMARC people did come to the IETF
> to ask for a working group to complete development of the work on the
> standards track.  This request was denied on the grounds that DMARC was
> essentially already done, and thus the IETF had nothing engineering-wise to
> contribute.  There were also too few people that were not already DMARC
> proponents that would commit to working on it.
>
>
The DMARC folk came to the IETF to have a rubber stamp put on their work,
and pretty explicitly stated that no substantive changes were acceptable,
and that change control would de-facto remains with the DMARC consortium.

So nobody who wasn't already "in the club" was really invited.

Feel free to go review the quite extensive discussion almost exactly a year
ago, but it includes suggestions that the DMARC group really only wanted
the IETF to polish the document's text a bit, but that this was rejected.

So no, I dispute very heavily that the DMARC people ever came to the IETF
to "complete development of the work"; there were explicit statements at
the time that they came to have the document wordsmithed without changing
the protocol at all.

The discussion (that I read at the time; there may be more) is all in the
apps-discuss archives.

Dave.

--047d7b5d58b45c2cfd04f7071729
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
4 April 2014 18:26, Murray S. Kucherawy <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a>&gt;</sp=
an> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>I mentioned in another=
 thread that the DMARC people did come to the IETF to ask for a working gro=
up to complete development of the work on the standards track.=C2=A0 This r=
equest was denied on the grounds that DMARC was essentially already done, a=
nd thus the IETF had nothing engineering-wise to contribute.=C2=A0 There we=
re also too few people that were not already DMARC proponents that would co=
mmit to working on it.<br>


</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div><br></div>=
</div></div></div></blockquote><div><br></div><div>The DMARC folk came to t=
he IETF to have a rubber stamp put on their work, and pretty explicitly sta=
ted that no substantive changes were acceptable, and that change control wo=
uld de-facto remains with the DMARC consortium.<br>

</div>
<div><br></div><div>So nobody who wasn&#39;t already &quot;in the club&quot=
; was really invited.</div><div><br></div><div>Feel free to go review the q=
uite extensive discussion almost exactly a year ago, but it includes sugges=
tions that the DMARC group really only wanted the IETF to polish the docume=
nt&#39;s text a bit, but that this was rejected.</div>
<div><br></div><div>So no, I dispute very heavily that the DMARC people eve=
r came to the IETF to &quot;complete development of the work&quot;; there w=
ere explicit statements at the time that they came to have the document wor=
dsmithed without changing the protocol at all.</div>
<div><br></div><div>The discussion (that I read at the time; there may be m=
ore) is all in the apps-discuss archives.</div><div><br></div><div>Dave.</d=
iv></div></div></div>

--047d7b5d58b45c2cfd04f7071729--


From nobody Mon Apr 14 14:16:46 2014
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8883D1A064D for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.8
X-Spam-Level: 
X-Spam-Status: No, score=-2.8 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 hO2GNSU17Jt0 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:16:40 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 82EC71A06B9 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:16:40 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3ELGYj1022818 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 14 Apr 2014 14:16:37 -0700
Message-ID: <534C4FB1.9060508@bbiw.net>
Date: Mon, 14 Apr 2014 14:14:25 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: R.E.Sonneveld@sonnection.nl
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <534C4AF8.60709@sonnection.nl>
In-Reply-To: <534C4AF8.60709@sonnection.nl>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Mon, 14 Apr 2014 14:16:38 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6gjmDBPAu5J3Sy5fb5Gg8GmU4wM
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:16:44 -0000

On 4/14/2014 1:54 PM, Rolf E. Sonneveld wrote:
>
> This might have been true if:
...
> 2. the decision making process within a closed industry consortium with
> maybe less than 20 members, representing immense commercial power, could
> be compared to the process of consensus, that's being used within IETF.


By way of pressing a particular process issue, without commenting on any 
of the surrounding issues:

    It's certainly true that the DMARC specification has not gone 
through an IETF approval process.

    That said, the document has been subject to open review for quite 
awhile, first (and continuing) via a mailing list at dmarc.org and more 
recently also one hosted at the IETF.  And the handling of reviews has 
been substantive.  Again, not an IETF open process, but substantive.

    Over quite a few months, there were a number of aggressive efforts 
to solicit community suggestions and agreement about the engineering 
work or document refinement work needed on the specification.

    Nothing close to rough consensus developed for any technical or 
documentation work.  Not on the dmarc.org list and not on the IETF's 
dmarc list.

If the community wanted changes to the specification, it had quite a bit 
of opportunity to call for the changes and/or call for  doing such work 
in the IETF.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 14 14:17:39 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 903381A06ED for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:17:34 -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, SPF_PASS=-0.001] autolearn=ham
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 nBGQMymayT3l for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:17:29 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id A1CBD1A06E1 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:17:29 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id cc10so4725465wib.8 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:17:26 -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:content-type; bh=qK4RMtIVqsnZA7xOeoK8mDFAeNW+kiQa3cL0C5dxg0I=; b=si75dHFoW7sXqVKzwTDJe0cTiVI6h+cALlSNn37tBqveGGORQ4kiqPJjZlybIy8+b1 O/6VnkXEMtm6k/NvOqvoy/G0VNJicWW7qKHCpr+ITNeqGMqUgrUs9rgD0hA/VgLPfnPT bw/eZsVFAn+/KjmUxDs99g4MtasAZpMueuf0I7BV2lEMqQY6KuM5x6rXYtQiAT3uRIPU ijV1DSE+9yVhQsk3atEr6x+fIq2iN5Q1dlhgMiUWYqsGvtRlgox/j5Z7Y73Tv9dKha4w L7o1SCX4TuiYrKD6ImdqfA+kQKK4cqMPKKvhH9lDpDeFI9RkaP6gAJtDpJ+ocC3yJwjG 4qkg==
MIME-Version: 1.0
X-Received: by 10.180.211.116 with SMTP id nb20mr11194144wic.5.1397510246682;  Mon, 14 Apr 2014 14:17:26 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 14:17:26 -0700 (PDT)
In-Reply-To: <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com>
Date: Mon, 14 Apr 2014 14:17:26 -0700
Message-ID: <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dick Franks <rwfranks@acm.org>
Content-Type: multipart/alternative; boundary=001a11c26ab4d2da3804f707356b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ETvs3wJbVegIoUDzS_pT6gY24Tg
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:17:34 -0000

--001a11c26ab4d2da3804f707356b
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 1:24 PM, Dick Franks <rwfranks@acm.org> wrote:

>
> 1)  Invalidates the inappropriate document citations on DMARC site.
>

I think you give them more weight than is justified.


>
> 2)  Publicly refutes any claim that this is an IETF standardisation effort.
>

Any such claim is merely outdated and needs correction.  DMARC did seek
standardization, but it was effectively denied.


>
> Robust action in defence of IETF reputation is possibly a precedent worth
> setting.
>

I suggest the price of going about it the way you described will do far
more harm than good, for reasons Brian has already cited.

-MSK

--001a11c26ab4d2da3804f707356b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 1:24 PM, Dick Franks <span dir=3D"=
ltr">&lt;<a href=3D"mailto:rwfranks@acm.org" target=3D"_blank">rwfranks@acm=
.org</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmai=
l_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<br><div class=3D"gmail_quote"><div>1)=C2=A0 Invalidates the inappropriate =
document citations on DMARC site.<br>
</div></div></div></div></blockquote><div><br></div><div>I think you give t=
hem more weight than is justified.<br>=C2=A0<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><br></div><div>2)=C2=A0 Publicly refutes any claim that this is an IETF st=
andardisation effort.<br></div></div></div></div></blockquote><div><br></di=
v><div>
Any such claim is merely outdated and needs correction.=C2=A0 DMARC did see=
k standardization, but it was effectively denied.<br>=C2=A0<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
><br></div>



<div>Robust action in defence of IETF reputation is possibly a precedent wo=
rth setting.<br></div></div></div></div></blockquote><div><br></div><div>I =
suggest the price of going about it the way you described will do far more =
harm than good, for reasons Brian has already cited.<br>
<br></div><div>-MSK <br></div></div></div></div>

--001a11c26ab4d2da3804f707356b--


From nobody Mon Apr 14 14:21:12 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FED61A0730 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:21:11 -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, SPF_PASS=-0.001] autolearn=ham
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 n7KE_aLGOk6t for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:21:09 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB091A0704 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:21:09 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id hm4so5987621wib.2 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:21:06 -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:content-type; bh=o0rZPPZ0vfeupx0n41YeJT9pq1zio2svGimwprtUG3U=; b=dt0yAtcp43hHQw4zFhBBT6G5vPV+dQPQFertLyQBnBlJq/wNesvvmeCUPy5AfJlUCB djjVN0mrntdWOKvfWPvsdOC3Xo7/+N+ndFhARZkBAmy479KYeemp8ZqlqLLWYbZYCuyD 2q95ZUVVnKZDU8sgITfWcOxyfza49m7/u598hpE2TIxLEqB6NTWMdlSCw8/+g+ZmKDxA 6ERLYPugLwvaBDsG5UxkXy9ULW7P5vpo+/7PhQXOR8a+ltMhRGFmMsPXBvbnWeXNHaZ0 2UZ2xqlTCZaVtFTaa6T4cKxSPPlnmtWOeH45QPsCvi+EpoKVk1sPBFu42XGNdvIjYPPt NAKQ==
MIME-Version: 1.0
X-Received: by 10.180.211.116 with SMTP id nb20mr11203576wic.5.1397510466312;  Mon, 14 Apr 2014 14:21:06 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 14:21:06 -0700 (PDT)
In-Reply-To: <534C4AF8.60709@sonnection.nl>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <534C4AF8.60709@sonnection.nl>
Date: Mon, 14 Apr 2014 14:21:06 -0700
Message-ID: <CAL0qLwZSAarop5A8NA2ZTNXeBxxk2Yw8vw5CRV0P4pwrH2Bp4Q@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "<R.E.Sonneveld@sonnection.nl>" <R.E.Sonneveld@sonnection.nl>
Content-Type: multipart/alternative; boundary=001a11c26ab4ea240904f7074268
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/u2hXz-6XFqQBtRBStQIpnHMX7HM
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:21:11 -0000

--001a11c26ab4ea240904f7074268
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 1:54 PM, Rolf E. Sonneveld <
R.E.Sonneveld@sonnection.nl> wrote:

>
> This might have been true if:
>
> 1. Yahoo _did_ solve the abuse problem and
>

We'll have to wait for them to tell us whether it did.  Anything we
conclude is our perspective, not theirs.


> 2. the decision making process within a closed industry consortium with
> maybe less than 20 members, representing immense commercial power, could be
> compared to the process of consensus, that's being used within IETF.
>

The consortium hasn't been closed for a long time.  A public mailing list
outside the IETF was announced and created, and then a second one
maintained at the IETF, both of which have been places from which
suggestions from the general community have been discussed, accepted, and
incorporated into revisions.  There was furthermore a BoF to create a
working group held a couple of IETF meetings ago.  It's not correct to
claim this has been closed the entire time any more than DKIM was.

-MSK

--001a11c26ab4ea240904f7074268
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 1:54 PM, Rolf E. Sonneveld <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:R.E.Sonneveld@sonnection.nl" target=3D"_bl=
ank">R.E.Sonneveld@sonnection.nl</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000"><div><div class=3D"h5"><br></di=
v></div>
    This might have been true if:<br>
    <br>
    1. Yahoo _did_ solve the abuse problem and <br></div></blockquote><div>=
<br></div><div>We&#39;ll have to wait for them to tell us whether it did.=
=C2=A0 Anything we conclude is our perspective, not theirs.<br>=C2=A0<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div bgcolor=3D"#FFFFFF" text=3D"#000000">
    2. the decision making process within a closed industry consortium
    with maybe less than 20 members, representing immense commercial
    power, could be compared to the process of consensus, that&#39;s being
    used within IETF.<br></div></blockquote><div><br></div><div>The consort=
ium hasn&#39;t been closed for a long time.=C2=A0 A public mailing list out=
side the IETF was announced and created, and then a second one maintained a=
t the IETF, both of which have been places from which suggestions from the =
general community have been discussed, accepted, and incorporated into revi=
sions.=C2=A0 There was furthermore a BoF to create a working group held a c=
ouple of IETF meetings ago.=C2=A0 It&#39;s not correct to claim this has be=
en closed the entire time any more than DKIM was.<br>
<br></div><div>-MSK<br></div></div></div></div>

--001a11c26ab4ea240904f7074268--


From nobody Mon Apr 14 14:27:20 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 810721A072B for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:27:18 -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, SPF_PASS=-0.001] autolearn=ham
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 2Bn7HHsBVQi4 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:27:14 -0700 (PDT)
Received: from mail-we0-x236.google.com (mail-we0-x236.google.com [IPv6:2a00:1450:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 56B741A06E6 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:27:13 -0700 (PDT)
Received: by mail-we0-f182.google.com with SMTP id p61so8558815wes.41 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:27:10 -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:content-type; bh=XT823+v4J4VRWUiLDgeudf51jsL+vS+Z+9Z7O//ed64=; b=m/5FRnEf9wTeCAbNWAo9+Y5bp+sj2+6GCS6hNk7Xac6VNlnz9kY8kP417mLIEB/DOh UNegJ0QUZKPYOP9FywLnUG1HBhRu47NiWz2qrWM3JBPcG9htHTRaYoWYFZy8aqabdVRo WBwKE3aTvLDZv7CoCG3GfJ2e6zkiyJTDPNiA11bHMaXM4P0daWqdWl55NCOasKoKHbu4 JFiRLKVS9efZQvDD1uYdqguxDEpgUdCZFNuxNG/Lbcy4mEZqgsoAh0T5y4kLWNiqKIlO PN3Z/05EUnoJELZYnh6T5jwToz+vx50xUQGCNeEEaSuh5ojerG0TepzFda3alIhMXuQc aVUg==
MIME-Version: 1.0
X-Received: by 10.194.89.168 with SMTP id bp8mr311090wjb.73.1397510830161; Mon, 14 Apr 2014 14:27:10 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 14:27:09 -0700 (PDT)
In-Reply-To: <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com>
Date: Mon, 14 Apr 2014 14:27:09 -0700
Message-ID: <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=047d7bf10a1c9a09b704f70758b2
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pSJU0r7vtFAz6KwDs3fsNJWD078
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:27:18 -0000

--047d7bf10a1c9a09b704f70758b2
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 2:08 PM, Dave Cridland <dave@cridland.net> wrote:

> The DMARC folk came to the IETF to have a rubber stamp put on their work,
> and pretty explicitly stated that no substantive changes were acceptable,
> and that change control would de-facto remains with the DMARC consortium.
>
> So nobody who wasn't already "in the club" was really invited.
>

I understand that's how the move was interpreted.  We spent a lot of time
arguing about how to word the charter so that changes were restricted only
to what was necessary versus wholesale changes that caused serious and
unjustified disruption to the installed base, etc. etc.  A lot of work has
been derailed by cracking base specs wide open in the past (think 2821 and
2822, for example).  It was the same argument under which DKIM and XMPP
were brought to the IETF, but in the case of DMARC case the two sides
couldn't agree on exactly how to do it.

One of the very specific items that was on the proposed charter was dealing
with the question of how to integrate DMARC with mailing lists.  This was
called out very early on as an open issue, as were some other important
ones:

http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC

-MSK

--047d7bf10a1c9a09b704f70758b2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 2:08 PM, Dave Cridland <span dir=
=3D"ltr">&lt;<a href=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cr=
idland.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div cla=
ss=3D"gmail_extra"><div class=3D"gmail_quote">The DMARC folk came to the IE=
TF to have a rubber stamp put on their work, and pretty explicitly stated t=
hat no substantive changes were acceptable, and that change control would d=
e-facto remains with the DMARC consortium.<br>



<div><br></div><div>So nobody who wasn&#39;t already &quot;in the club&quot=
; was really invited.</div></div></div></div></blockquote><div><br></div><d=
iv>I understand that&#39;s how the move was interpreted.=C2=A0 We spent a l=
ot of time arguing about how to word the charter so that changes were restr=
icted only to what was necessary versus wholesale changes that caused serio=
us and unjustified disruption to the installed base, etc. etc.=C2=A0 A lot =
of work has been derailed by cracking base specs wide open in the past (thi=
nk 2821 and 2822, for example).=C2=A0 It was the same argument under which =
DKIM and XMPP were brought to the IETF, but in the case of DMARC case the t=
wo sides couldn&#39;t agree on exactly how to do it.<br>
<br></div><div>One of the very specific items that was on the proposed char=
ter was dealing with the question of how to integrate DMARC with mailing li=
sts.=C2=A0 This was called out very early on as an open issue, as were some=
 other important ones:<br>
<br><a href=3D"http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC">http:=
//wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC</a><br><br></div><div>-MSK=
<br></div></div></div></div>

--047d7bf10a1c9a09b704f70758b2--


From nobody Mon Apr 14 14:43:07 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8531A1A075F for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 E5zzEmCD8rxn for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:43:03 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id B45E21A0755 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:43:03 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id D70C4CC0C6 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:43:00 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id MlkpW1v-nM8I for <ietf@ietf.org>; Mon, 14 Apr 2014 17:42:52 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id EA239CC0BC for <ietf@ietf.org>; Mon, 14 Apr 2014 17:42:51 -0400 (EDT)
Message-ID: <534C565B.9090501@meetinghouse.net>
Date: Mon, 14 Apr 2014 17:42:51 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <534C4912.9010705@gmail.com>
In-Reply-To: <534C4912.9010705@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/x0p8C7J542-OYgdcugMd0xvqC0Y
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:43:04 -0000

Brian E Carpenter wrote:
> On 15/04/2014 08:24, Dick Franks wrote:
>> On 14 April 2014 19:03, Murray S. Kucherawy <superuser@gmail.com> wrote:
>>
>>> On Mon, Apr 14, 2014 at 11:01 AM, Miles Fidelman <
>>> mfidelman@meetinghouse.net> wrote:
>>>
>>>
>>>>> A more pragmatic, less expensive, and publicly visible expression of
>>>>> IETF displeasure might be to expunge all versions of the offending I-D from
>>>>> IETF document store and refuse to publish any subsequent version until the
>>>>> unwarranted claims made for it are retracted.
>>>>>
>>>>> To be effective, that needs to be done now, while the iron is still hot;
>>>>> not after the usual 3-month email debate about the diplomatic niceties.
>>>>>
>>>>>   The later, accompanied with a strong statement about the limits of
>>>> DMARC, and the flaws in its deployment - might not be a bad start.
>>>>
>>> What real-world effect is this supposed to have, apart from setting a very
>>> dangerous precedent?
>>>
>>>
>> 1)  Invalidates the inappropriate document citations on DMARC site.
>>
>> 2)  Publicly refutes any claim that this is an IETF standardisation effort.
>>
>>
>> Robust action in defence of IETF reputation is possibly a precedent worth
>> setting.
> Not at the price of looking like censorship and distorting the
> historical record.
>
> We have very carefully designed boilerplate, and the point of
> boilerplate is precisely that it's there even if people don't
> read it. We're an open voluntary standards organisation;
> we're still not the Internet Police.
>
> I'm strongly against removing drafts from the public record unless
> they are obscene or libellous.
>
>
Big red disclaimer at the top then:
- THIS IS A DRAFT DISCUSSION MEMO
- THIS IS NOT A STANDARDS-TRACK SPECIFICATION
- THIS IS AN INDEPENDENT SUBMISSION, NOT AN IETF DOCUMENT
- SHOULD NOT BE USED AS THE BASIS FOR OPERATIONAL DEPLOYMENT OF PROTOCOL 
SOFTWARE




-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 14:45:02 2014
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 808C31A076A for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level: 
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 Q7jo6mhjFm1p for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:44:54 -0700 (PDT)
Received: from qmta07.westchester.pa.mail.comcast.net (qmta07.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:64]) by ietfa.amsl.com (Postfix) with ESMTP id 807A01A023A for <ietf@ietf.org>; Mon, 14 Apr 2014 14:44:54 -0700 (PDT)
Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta07.westchester.pa.mail.comcast.net with comcast id pwuR1n0011wpRvQ57xkr1k; Mon, 14 Apr 2014 21:44:51 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta18.westchester.pa.mail.comcast.net with comcast id pxkr1n00J1KKtkw3exkr29; Mon, 14 Apr 2014 21:44:51 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s3ELiplg014506 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:44:51 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s3ELipR8014504; Mon, 14 Apr 2014 17:44:51 -0400
Date: Mon, 14 Apr 2014 17:44:51 -0400
Message-Id: <201404142144.s3ELipR8014504@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <CF71721A.180A9%wesley.george@twcable.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1397511891; bh=sJjPUv7N8mgQ8hSWXicuYZyJpZxzp2LIklqpHSp0HT8=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=bChnEZGHL+R4vAChCQ5ldqgDxxIKpTkOf8CcVbiVYGuEzAgPrN8wP9U10f25FeoIy DRbipBM0JoVkh4tu8otwKlE9lXF/u5VhHbIiwISlxXx754QzdFD1Tpq6xYuCyhMUks oLogeQbFd5S7ctR3L2aMUHWLtTUvi+l42sRE+vWSGPaGnbnS7v8f9VPDhBtiumkKDk 2nyDp271X+dPjM4nbYo7SH/2NhzrJ/jx3IsNUe/Mj9Nnzi4JEtaz/VtK3gI+Dp0qmc r5jP5c3a+qq1z3DdTF+CAlIc6ATkTdpvrT3mXVBdapb6nLKkAkrYFZ+ZdibSSBvUiw npaWBGx81hvQA==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/V2Uktbg_RMhR2ZSmbuK6DqOK26w
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:44:59 -0000

> I'm surprised that no one has sent this out yet:
> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
> 
> "Summary: After contributing to standards organizations for more
> than seven years, engineer Vidya Narayanan decided it was time to
> move on. Although she still believes that these organizations make
> the Internet a better place, she wonders about the pace of change
> versus the pace of organizations."

> "while the pace at which standards are written hasn't changed in
> many years, the pace at which the real world adopts software has
> become orders of magnitude faster."

This is key, in a way.  But the pace at which software has been
adopted hasn't changed.  Nor has the pace at which the real world
adopts *interoperable protocols* changed -- and that has always been
much slower.  What has happened is that a lot of the focus (and money
and employment) has moved from adopting new protocols to adopting new
software, software which is under no interoperation constraints.

A simpler comparison is between the compilers for two languages:
Fortran and Perl.  There have been many, many Fortran compilers
written, and at any era, there has been the effort to standardize the
language that the compilers accept, so that a program can be compiled
using more than one compiler.  In reality, to ensure that the
compilers interoperate.

Now look at Perl.  There has only been one compiler in all of history,
so that any Perl program that works on one computer works on every
computer that implements Perl -- because it's always run using the
same compiler.

In this case, it is a side-effect of open source, I think, because
open source eliminates the financial pressure on computer vendors to
write their own compilers for a language.

A similar thing has been happening in other fields.  An internal
feature can be added to Apache and distributed to the world in
months.  But adding a feature to HTTP can take years, because it has
to be designed and implemented to be interoperable -- in this case,
between the HTTP servers and the HTTP clients.

In the current Internet business, a lot of the new business is at the
application layer, and it is composed of "walled garden" web sites,
which don't have to interoperate with anything else.  In the more
elaborate cases, the user's web browser effectively downloads the
client software at the point when the user accesses the server.  There
are no true interoperability constraints.

In situations where you are going to need "two independently-developed
interoperable implementations", a standards process is still needed.
But there are a lot of high-profile situations where that isn't
needed.

In regard to speeding up the standards process, it's clear that in
most cases, the process could in principle be carried out much faster.
In all the cases I've observed, the major problem is that the
participants can only spend a small fraction of their working hours on
the standards discussion.  I assume this is because it's rare that
getting the standard completed is gating to shipping their employer's
product.

Dale


From nobody Mon Apr 14 14:49:26 2014
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A21761A0685 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 d7HFCpYpVSGd for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:49:20 -0700 (PDT)
Received: from qmta14.westchester.pa.mail.comcast.net (qmta14.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:212]) by ietfa.amsl.com (Postfix) with ESMTP id 792741A04E8 for <ietf@ietf.org>; Mon, 14 Apr 2014 14:49:20 -0700 (PDT)
Received: from omta23.westchester.pa.mail.comcast.net ([76.96.62.74]) by qmta14.westchester.pa.mail.comcast.net with comcast id prZy1n0051c6gX85ExpH9Y; Mon, 14 Apr 2014 21:49:17 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta23.westchester.pa.mail.comcast.net with comcast id pxpH1n00M1KKtkw3jxpHmb; Mon, 14 Apr 2014 21:49:17 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s3ELnHdl015021 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:49:17 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s3ELnH4R015020; Mon, 14 Apr 2014 17:49:17 -0400
Date: Mon, 14 Apr 2014 17:49:17 -0400
Message-Id: <201404142149.s3ELnH4R015020@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <534C0366.10600@nostrum.com> (rjsparks@nostrum.com)
Subject: Re: Logging into the datatracker
References: <534C0366.10600@nostrum.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1397512157; bh=SFw/z5VzfR6oq9rYBc/mZbErhHKZe/T5CPiRzlrogxg=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=GS2z7Z+Weok4uP6T+SL3bSMj11YbneVGh9ADd8lyc19/Uv/FwFEnx7nkfydbEtQqC URIB0YkdOKa9WGG1lU6t3gKGdDRJoN3n9Mahg+O0eC8V5GAQEp9YiCu3i8awAhfP1U 3VJiOnQ8QTHckVrB3NPIsy1tnUHAiOm3QpGs26vzgylmTuiUzhfVgPEcVhgpW3zoCT zZn21CFoaIjjjYMqHGALjmpBu0zrYjdrRzB8ll0VRsXgDN4MlpnNCF2JcdDZ9/wnou tTxJlWGKsFUoDEgID6XSQj/OwFjbHh+ZXLmNHxTljv3ZLvinO5k7z7WlBZOJrit492 Xpaa62NDpV66g==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BkNnAvSP9ki86ESkROZ7UlMqUjI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:49:24 -0000

> From: Robert Sparks <rjsparks@nostrum.com>

> Today's datatracker release changed the way you sign in, and has added 
> the ability to sign out.
> 
> See <https://datatracker.ietf.org/release/> for details.

> "This release changes user authentication for the datatracker from
> basic http auth to Django's built-in authentication."

No doubt this is all for the best in practice, but it does eliminate
the one and only web site I've ever used that uses HTTP
authentication.  R.I.P. RFC 2617.

Dale


From nobody Mon Apr 14 14:50:32 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87EF1A04E8 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:50:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.343
X-Spam-Level: **
X-Spam-Status: No, score=2.343 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 mcEqTEcqf2ML for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 14:50:27 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id F16971A06FE for <ietf@ietf.org>; Mon, 14 Apr 2014 14:50:23 -0700 (PDT)
Received: (qmail 54910 invoked from network); 14 Apr 2014 21:50:11 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 14 Apr 2014 21:50:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=7d7f.534c5813.k1404; i=johnl@user.iecc.com; bh=5rlAmmhZn8L5yTJPQgNju785eRhfQnAPaGEr984FkR4=; b=nAMKRUJD+Tse7iQ/T10UE9rI2n/yD3Ou11Pz1WVnM0Hrbg4IMKDgt4j3MJPDo/Suxl0p3/FUzkpwsg3uHpBPhIjUBorsch0C0bQRRuXTIHgXPmfRRAMYrdguNICzY77mBcBBAs+RjJX0vLjBwjj3dz4DVrIuTlWXxd0K1LHyZa9ru4odc+D9MV0ebYPSFDhDYkJK9fZrJOoiry19hS9Toa/e9SaCTVaZNW/YaCLEYrT+Er5FQZld9XBQuAzm6MtO
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=7d7f.534c5813.k1404; olt=johnl@user.iecc.com; bh=5rlAmmhZn8L5yTJPQgNju785eRhfQnAPaGEr984FkR4=; b=0L/kNFOjOWAUSrHuoGhNDf5B89bTxlp6d6nd13tMLVZm1pG8Yi5t4fAxzcRPmNIUCqo8dn0J8Ef9ThMwbm4Zb3CgM+7zDiZJ9qUDWU0WI2q19J3f3ZW+Llxm6CybNCNezgLomC97TgSnuzRhMHdO60BKrelzu6n+O8QkW6fSE89DdAR4PwH/ZL5AGt8bQ84zgfCIixJDNERsfIVw4YPeK32Z4ssIZJo5RAxj35/r0DrrBO6NMt5XLqg6LlLh4fCA
Date: 14 Apr 2014 21:49:49 -0000
Message-ID: <20140414214949.32126.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: protecting the Internet from DMARC damage, was perspectives
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AtJHyiimDJKgVo8nXegw9o-sQLc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 21:50:32 -0000

>The fact is that a vocal constituency led by John Levine made it extremely clear that MLMs were out of scope
>and there was zero interest on the part of the MLM community in discussing ways in which MLMs could be made to
>work in an email authentication framework even if there were any MLM operators willing to do so. ...

DMARC must be in pretty bad shape if its proponents have to resort to
malicious lies like this.  It saddens me that Mike, who I used to
consider a friend, would do so.

My position has always been perfectly clear: mailing lists are not
broken, they provide a significant service to individual Internet mail
users, and it is not our job to spend time and money to solve other
people's problems.  DMARC, like all of its predecessor authentication
schemes, has a model of the way people send mail that describes much
but not all of the actual mail people send.  There are an awful lot of
ways that people send mail, so this shouldn't come as a surprise to
anyone.

The invariable next step is that some of the proponents of the scheme,
rather than recognizing and admitting to its limitations, declare that
the mail the scheme can't describe is bad and must be eradicated, with
the term "forged" often misused.  People who have been around long
enough will remember when the SPF crowd demanded that everyone stop
forwarding mail, or a few people wanted to apply strict DKIM ADSP to
everything.  Mailing lists are the most obvious sending scenario that
DMARC doesn't describe, but it's far from the only one.

I have always said that DMARC is useful for a lot of mail, such as the
"spam cannon" stuff (a comment on the volume, not necessarily the
character) that Mike's employer sends, or that Paypal and banks send.
As we have seen, it fails miserably for domains with non-employee live
users.

Without exception the ways proposed to change MLMs to "to work in an
email authentication framework" have involved removing useful features
added over the decades that our users use and like, so it also
shouldn't be a surprise that we're not interested in bowdlerizing our
service to solve their problem.  We also note that many of the
proposed solutions are overcomplicated and unlikely to work in
practice (original-authentication-results) or just plain won't work
(turning off all subject tags, message footers, and other message
modifications.)

If the DMARC crowd were interested in being good net citizens, there
is a way to deal with DMARC's limitations that is straightforward but
not free: whitelisting.  Most of the lists I see sign their mail, and
they generally use static IP sending addresses, so they're not hard to
characterize.  The set of mailing lists and other legitimate mail
sources that DMARC doesn't describe is not enormous, and it should be
possible to develop shared whitelists for them, if someone were
willing to pay for doing so.  (This is a much smaller problem than
trying to whitelist all "legitimate" mail.) If the list-whitelist
group said that lists need to sign their mail or use an unshared IP to
get whitelisted, you would find little resistance, both because most
of us do that already, and because it doesn't ask us to make our lists
worse for our users.

Unfortunately, we've seen no willingness to spend their money to help
us solve their problem, and far too much of do it our way or else,
because we are bigger than you are.

R's,
John


From nobody Mon Apr 14 15:00:46 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A79BA1A0473 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:00:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 7I6kak7CKpxG for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:00:43 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id AB7AC1A0230 for <ietf@ietf.org>; Mon, 14 Apr 2014 15:00:42 -0700 (PDT)
Received: (qmail 56834 invoked from network); 14 Apr 2014 22:00:39 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 14 Apr 2014 22:00:39 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=7db4.534c5a87.k1404; i=johnl@user.iecc.com; bh=jWKZoNALYtlcp1eu1eG8Lib8+UsdzgQSF9LFPPRbMQY=; b=Zk2xq+d5K6f4F+TZWoNw2scuqG7f3dpGasSR/DPVI20IAULEgZ0SzykFwS0UJZvMaEYkx5d8Id8/RNEiNwCWM9ueXT/Xuw2qAg66ZNypdZNZSzvWw6f/fMeKp+J2qMn5Tv1zP00HVKqXxlbxGN4u7OWapOkx9WMukgiSME7XTNys9Dth+R87NfH+gM6m2tNFTkBRxngRfGKbjzMsdnCgKNW0v2ghR5AvDj0fXs0su3t5GlJ56RDl9WVAhH6R4uuF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=7db4.534c5a87.k1404; olt=johnl@user.iecc.com; bh=jWKZoNALYtlcp1eu1eG8Lib8+UsdzgQSF9LFPPRbMQY=; b=o9fj5D8JEYTGQ5tn3OQ7IWZywY5YSJwmGhg5s8pSKWCFr/HusmKgV+0LNO8NJbgpxs+b/VSMi4fXP8noEDQ0AyguWuFC60LOeaDaqgLZJV0qPunY/wq50cat0XyQWfWFjmacWr5hD7HM2vqktDQ7C7FX5Zlhbr7NZbdgNMNZ9cNgan0gjQ1CvLPO/B8vGlj/QrIsH99rvvCGanP/1O7mK3uPkeqqq60HtuaNaA2FcJ31X+hG9xchRsFBRRyu9gw0
Date: 14 Apr 2014 22:00:17 -0000
Message-ID: <20140414220017.32179.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534C4794.5000600@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FppbE_uCxdqDpMvRjcg9ohDJOlM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 22:00:44 -0000

>> The DMARC proponents did engage mailman.   Version 2.1.16 includes support
>> for a setting that makes the operation of the list DMARC-friendly, though
>> likely in a way some people will find unpalatable. 
>
>Please tell us more about that.

It turns it into a pure forwarder, no subject tags, message footers,
or anything else that might break a DKIM signature.

Of course, even if you do that, it still won't solve the problems that
DMARC causes.  Consider, for example, a Yahoo mail user who prefers
the Gmail interface, so has set up Gmail to collect her Yahoo mail,
and sends her mail from Gmail using her existing Yahoo address.  Gmail
does COI confirmation before letting you use your other outgoing
address, no forgery allowed.  Yahoo provides POP and IMAP service, so
this is clearly something Yahoo anticipated.

As I said in my prior screed, the only way to un-break DMARC is to
whitelist the exceptions.

R's,
John


From nobody Mon Apr 14 15:02:50 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02EF41A0679 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:02:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.521
X-Spam-Level: 
X-Spam-Status: No, score=0.521 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 mQdJoov1RYIl for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:02:35 -0700 (PDT)
Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 58C481A0601 for <ietf@ietf.org>; Mon, 14 Apr 2014 15:02:35 -0700 (PDT)
Received: by mail-ob0-f174.google.com with SMTP id gq1so1539494obb.19 for <ietf@ietf.org>; Mon, 14 Apr 2014 15:02:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LeqASykDuj9wcpUDGJxIBhAqc6EE9BRKmPcjL1EAZlg=; b=gQ3m+Mr9msyWO27XdUz35RCj/sVVc0nDGlDq2uNQPUDfWYU3v4dgVJCChx7qRhiV1d c1QSLr2uJGpnscbl6lCmLbSsqm9PHQ4AKjumsuZlCvsvigzUULxRrwL86+xktyplSo80 pk5cToUdx7yFIuDZp8MOX45iwnXJ/ncOwC3qA=
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:content-type; bh=LeqASykDuj9wcpUDGJxIBhAqc6EE9BRKmPcjL1EAZlg=; b=ERw6Wc6WmosWmYHiZ0hMB7V0CMupUGTM3IeYca0XcNT691dUlD/LfwOno76ASHCTO1 RDVNsXfiNQ57DvStJdj7rEjiPvLSVyuR1GLwSTY/I/atOl+0mQygGXHLcYE7v8mM9Lzn OKaYEu7y4S7gpbzid8dC4NYlYYiEeR1mL29yPTNfMYi+CRZlXbZTjwyOFyllGo9TOj+u QHFJr5RZmpgESnBMeb3Xu9eXB0hjw2nxaFoCSZgIOTPRo8Twtg47jeY9jh//FrmOUPqk sBwXOvUmt1J8o6pUhscqaM9sTpX78Zd0dmtmh0+/mGjwHHV49bbpKfbTBw/LN6lje2DL oZCQ==
X-Gm-Message-State: ALoCoQkhQQATzFBzj9UiLrPsc5vT1WhWuQwRfjUsbZ12N+Zh+E6pIfAKWSXaJ0M8duRJaMKpBRRy
MIME-Version: 1.0
X-Received: by 10.60.17.132 with SMTP id o4mr25671371oed.34.1397512952731; Mon, 14 Apr 2014 15:02:32 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Mon, 14 Apr 2014 15:02:32 -0700 (PDT)
In-Reply-To: <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com>
Date: Mon, 14 Apr 2014 23:02:32 +0100
Message-ID: <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Dave Cridland <dave@cridland.net>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=089e01294d0c1df39204f707d7b2
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/sHfOBEr7BM5bPdFnHNd1-dC1MWk
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 22:02:37 -0000

--089e01294d0c1df39204f707d7b2
Content-Type: text/plain; charset=UTF-8

On 14 April 2014 22:27, Murray S. Kucherawy <superuser@gmail.com> wrote:

> On Mon, Apr 14, 2014 at 2:08 PM, Dave Cridland <dave@cridland.net> wrote:
>
>> The DMARC folk came to the IETF to have a rubber stamp put on their work,
>> and pretty explicitly stated that no substantive changes were acceptable,
>> and that change control would de-facto remains with the DMARC consortium.
>>
>> So nobody who wasn't already "in the club" was really invited.
>>
>
> I understand that's how the move was interpreted.  We spent a lot of time
> arguing about how to word the charter so that changes were restricted only
> to what was necessary versus wholesale changes that caused serious and
> unjustified disruption to the installed base, etc. etc.  A lot of work has
> been derailed by cracking base specs wide open in the past (think 2821 and
> 2822, for example).  It was the same argument under which DKIM and XMPP
> were brought to the IETF, but in the case of DMARC case the two sides
> couldn't agree on exactly how to do it.
>
>
Actually, you specifically stated that it was different. DKIM had quite low
deployment, you said - and that in itself was DomainKeys rather than DKIM
per-se. DMARC had, you said, 60% of the mailboxes covered already. Changes
just weren't practical, you said - deployment was already a fact. In fact,
you rejected the phrases used in both DKIM and XMPP's charters, saying they
weren't suitable.

Scott Kitterman said it seemed like the DMARC people wanted just
wordsmithing; Dave Crocker said that was, indeed, what they wanted, but "at
least one AD" had pushed back.

I'm paraphrasing to some degree, but I'll dig out actual links to messages
if you really want.

There's little room for misinterpretation; you and Dave Crocker were, quite
characteristically, very clear and explicit; saying you "understand that's
how the move was interpreted" is a good political phrase, but it was
interpreted that way because you made it very clear that was how it was.


> One of the very specific items that was on the proposed charter was
> dealing with the question of how to integrate DMARC with mailing lists.
> This was called out very early on as an open issue, as were some other
> important ones:
>
> http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC
>
>
Right, but the WG was expected to make it work with mailing lists without
changing it. Tough ask.

Sorry, but given the way in which IETF participants were asked to work on
DMARC, there is absolutely no way you could say that the "DMARC people came
to the IETF to [...] complete development" - it was more or less stated
that development was done and dusted - and the IETF didn't reject it on the
basis that no engineering work remained - the DMARC people rejected any
engineering work happening.

It doesn't actually matter whether you think the reasons behind this were
valid; the fact is that you're putting one heck of a slant on recent
history, and it's not borne out by what's in the archives.

Dave.

--089e01294d0c1df39204f707d7b2
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 14 April 2014 22:27, Murray S. Kucherawy <span dir=3D"ltr">&lt;<=
a href=3D"mailto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com=
</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"">On Mon, Apr=
 14, 2014 at 2:08 PM, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"mailto=
:dave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;</span> wrot=
e:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D""=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div cla=
ss=3D"gmail_extra"><div class=3D"gmail_quote">The DMARC folk came to the IE=
TF to have a rubber stamp put on their work, and pretty explicitly stated t=
hat no substantive changes were acceptable, and that change control would d=
e-facto remains with the DMARC consortium.<br>




<div><br></div><div>So nobody who wasn&#39;t already &quot;in the club&quot=
; was really invited.</div></div></div></div></blockquote><div><br></div></=
div><div>I understand that&#39;s how the move was interpreted.=C2=A0 We spe=
nt a lot of time arguing about how to word the charter so that changes were=
 restricted only to what was necessary versus wholesale changes that caused=
 serious and unjustified disruption to the installed base, etc. etc.=C2=A0 =
A lot of work has been derailed by cracking base specs wide open in the pas=
t (think 2821 and 2822, for example).=C2=A0 It was the same argument under =
which DKIM and XMPP were brought to the IETF, but in the case of DMARC case=
 the two sides couldn&#39;t agree on exactly how to do it.<br>

<br></div></div></div></div></blockquote><div><br></div><div>Actually, you =
specifically stated that it was different. DKIM had quite low deployment, y=
ou said - and that in itself was DomainKeys rather than DKIM per-se. DMARC =
had, you said, 60% of the mailboxes covered already. Changes just weren&#39=
;t practical, you said - deployment was already a fact. In fact, you reject=
ed the phrases used in both DKIM and XMPP&#39;s charters, saying they weren=
&#39;t suitable.</div>
<div><br></div><div>Scott Kitterman said it seemed like the DMARC people wa=
nted just wordsmithing; Dave Crocker said that was, indeed, what they wante=
d, but &quot;at least one AD&quot; had pushed back.</div><div><br></div>
<div>I&#39;m paraphrasing to some degree, but I&#39;ll dig out actual links=
 to messages if you really want.</div><div><br></div><div>There&#39;s littl=
e room for misinterpretation; you and Dave Crocker were, quite characterist=
ically, very clear and explicit; saying you &quot;understand that&#39;s how=
 the move was interpreted&quot; is a good political phrase, but it was inte=
rpreted that way because you made it very clear that was how it was.</div>
<div>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div c=
lass=3D"gmail_extra"><div class=3D"gmail_quote"><div></div><div>One of the =
very specific items that was on the proposed charter was dealing with the q=
uestion of how to integrate DMARC with mailing lists.=C2=A0 This was called=
 out very early on as an open issue, as were some other important ones:<br>

<br><a href=3D"http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC" targe=
t=3D"_blank">http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC</a><span=
 class=3D"HOEnZb"><font color=3D"#888888"><br><br></font></span></div></div=
></div>
</div></blockquote><div><br></div><div>Right, but the WG was expected to ma=
ke it work with mailing lists without changing it. Tough ask.</div><div><br=
></div><div>Sorry, but given the way in which IETF participants were asked =
to work on DMARC, there is absolutely no way you could say that the &quot;D=
MARC people came to the IETF to [...] complete development&quot; - it was m=
ore or less stated that development was done and dusted - and the IETF didn=
&#39;t reject it on the basis that no engineering work remained - the DMARC=
 people rejected any engineering work happening.</div>
<div><br></div><div>It doesn&#39;t actually matter whether you think the re=
asons behind this were valid; the fact is that you&#39;re putting one heck =
of a slant on recent history, and it&#39;s not borne out by what&#39;s in t=
he archives.</div>
<div><br></div><div>Dave.</div></div></div></div>

--089e01294d0c1df39204f707d7b2--


From nobody Mon Apr 14 15:03:04 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E028D1A0679 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 ezWC0XPS4B7M for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:02:59 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id EFDDF1A066F for <ietf@ietf.org>; Mon, 14 Apr 2014 15:02:58 -0700 (PDT)
Received: (qmail 57200 invoked from network); 14 Apr 2014 22:02:56 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 14 Apr 2014 22:02:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=7dca.534c5b10.k1404; i=johnl@user.iecc.com; bh=5X103C0dtTdq+9gUOt2X6EriBkU1Ih2FxefjE9uQ+8U=; b=I/pkVAhVR1z84bwcy2Clsh79WI1iLEBOVdaArZLoQef48/3TmVI727QPYuH0f3SFHQN29Ky5M0PdwMigLfyyQhoTVJX038vZjMJRJvr7fJ1kLYRJD/pJub9j9rI9jJuxFzGhXiF+I+S+8IYgoqYPnxS6lKRgmAsb1doFMpAo+r5f0gh0gxFm5veZOsCtplyHxZT3NbDP8c9DYyOmSLrSfdYxXFWx/04arALjb3b8viGetwqDvl7+/jY/PhNoH27E
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=7dca.534c5b10.k1404; olt=johnl@user.iecc.com; bh=5X103C0dtTdq+9gUOt2X6EriBkU1Ih2FxefjE9uQ+8U=; b=ia5/pJKGdMmZRD5KME0PtWd1Sxtp3OKv9+N7jZY7Ib9M82luLRj0eUTDtwsSwoy4YCVx0nUamIW7qRdx86U8aY3CejtJFjCwr5PIxEHhsfDKNDbPUcR+taCrFWHoX+97lCzuBK5BuPAb9p0cNwUc3vDUT969kvqpPYAlBFsIBuhCq9A7I3OkG7XkM4Axy+Sp22aCWKNk0T4secIW21gSoEQ9231RU6yZFDWlRFpO9+i08wexgB5gplHDpwluhgNO
Date: 14 Apr 2014 22:02:33 -0000
Message-ID: <20140414220233.32201.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <20140414210059.GA8345@thunk.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/g7coDHyYX_kPIt1r-s9OE9FqGoc
Cc: tytso@mit.edu
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 22:03:00 -0000

>to something like:
>
>From: Brian E Carpenter <brian.e.carpenter@yahoo.com.INVALID>

That's what I do on my lists.  It was pretty easy to add in the shim
that adds the outgoing DKIM signature, and is the least painful thing
I could think of for my mostly non-technical users.

>(or maybe instead of yahoo.com.INVALID, it should be "yahoo.com.BREAKS.MAILING.LISTS"

Now, now, there's no LISTS TLD.  Yet.

R's,
John


From nobody Mon Apr 14 15:06:33 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C44F1A0737 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:06:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 tsESmgMKGTsB for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:06:27 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 83AF21A0730 for <ietf@ietf.org>; Mon, 14 Apr 2014 15:06:27 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wn1so2314782obc.18 for <ietf@ietf.org>; Mon, 14 Apr 2014 15:06:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=N4JGZN2mbxgHq7aVu2/Pki9HLQ5r6yfo/UE3eCy3IBY=; b=ZljmgEXMevNDA8g9H+VzwLN7iC6aSkS3eqXD/0vwxy7DTc9xJ7DjcJx/0Snk1xJPDy MHZ9ehiqVUR+Cf8QiC0TRNBrl26F2olwB9vVZo4kds/BKKoIUzX2tok3GAyHL000c2ZO MAoFl9lX5DbQs0hEKZ1FmuY55tXTXb/w8dz1U=
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:content-type; bh=N4JGZN2mbxgHq7aVu2/Pki9HLQ5r6yfo/UE3eCy3IBY=; b=DK4meyIHmJscst8d4AcQ3VtHBrC5XCLt35oIU9LBgVOfQC8K7bkMvPu4l5fkPGdqjF 02a4H12ONe+RHjx1w2Qhq37KtgcQJ2MGQS4YYVqmPJmedU6Nr80zmqb8XRU0+0kC1aS8 vmqI8/6iiTqpcIyNeQmCZbsU/+uS92lLl1KZ1LYpmxMx7cZ84F/thf023LXjKPrzNlvd gr07f6XjnGIy32J9IQGRRCKvoDsst6yHqY+fin+cl02PNQiwGiRoq2PipXcDS1ZaxI/N x6lBtVM/dUbRvSg0VFWMPZ6w5/2zk0kNlS8bkEXsESk41wisEfcDoAkPLraBWKH/58u8 ieVA==
X-Gm-Message-State: ALoCoQm/Bo553DWJTPBmdpeT0hcF66xqlgrQaRbAT4T3cokKTfADuWUV+uF6PPXIh0WjtIPoXEWH
MIME-Version: 1.0
X-Received: by 10.60.76.194 with SMTP id m2mr4230547oew.47.1397513184890; Mon, 14 Apr 2014 15:06:24 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Mon, 14 Apr 2014 15:06:24 -0700 (PDT)
In-Reply-To: <534C565B.9090501@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <534C4912.9010705@gmail.com> <534C565B.9090501@meetinghouse.net>
Date: Mon, 14 Apr 2014 23:06:24 +0100
Message-ID: <CAKHUCzxiQhEm7bCoMMh6ceOgmjbTtnHBoQGohP7HO5Vh=+XAyg@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Dave Cridland <dave@cridland.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=047d7b33cea6f4641704f707e47b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hqhjLKz3TzUm38rIHVrFlg0Pc9c
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 22:06:31 -0000

--047d7b33cea6f4641704f707e47b
Content-Type: text/plain; charset=UTF-8

On 14 April 2014 22:42, Miles Fidelman <mfidelman@meetinghouse.net> wrote:

> Big red disclaimer at the top then:
> - THIS IS A DRAFT DISCUSSION MEMO
> - THIS IS NOT A STANDARDS-TRACK SPECIFICATION
> - THIS IS AN INDEPENDENT SUBMISSION, NOT AN IETF DOCUMENT
> - SHOULD NOT BE USED AS THE BASIS FOR OPERATIONAL DEPLOYMENT OF PROTOCOL
> SOFTWARE
>
>
It doesn't matter. The fact that DMARC is an I-D at all is largely
incidental.

If Yahoo had privately developed DMARC in a consortium under entirely
different practice and operational rules than the IETF, where any
participants in their mailing lists would have no clue how their
contributions might be used, and without any review by the IETF as a whole,
and then that consortium had published the result as an I-D, it'd be
exactly the same situation as we are now.

Dave.

--047d7b33cea6f4641704f707e47b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On 14 April 2014 22:42, Miles Fidelman <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank">mfidelman@meeting=
house.net</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><spa=
n style=3D"color:rgb(34,34,34)">Big red disclaimer at the top then:</span><=
br></div>
</div>
- THIS IS A DRAFT DISCUSSION MEMO<br>
- THIS IS NOT A STANDARDS-TRACK SPECIFICATION<br>
- THIS IS AN INDEPENDENT SUBMISSION, NOT AN IETF DOCUMENT<br>
- SHOULD NOT BE USED AS THE BASIS FOR OPERATIONAL DEPLOYMENT OF PROTOCOL SO=
FTWARE<div class=3D"HOEnZb"><div class=3D"h5"><br></div></div></blockquote>=
<div><br></div><div>It doesn&#39;t matter. The fact that DMARC is an I-D at=
 all is largely incidental.</div>
<div><br></div><div>If Yahoo had privately developed DMARC in a consortium =
under entirely different practice and operational rules than the IETF, wher=
e any participants in their mailing lists would have no clue how their cont=
ributions might be used, and without any review by the IETF as a whole, and=
 then that consortium had published the result as an I-D, it&#39;d be exact=
ly the same situation as we are now.</div>
<div><br></div><div>Dave.</div></div></div></div>

--047d7b33cea6f4641704f707e47b--


From nobody Mon Apr 14 15:28:01 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B9CB1A077F for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:28:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.426
X-Spam-Level: 
X-Spam-Status: No, score=0.426 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 zviQ9j0DdJ1h for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:27:56 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 33F931A077C for <ietf@ietf.org>; Mon, 14 Apr 2014 15:27:56 -0700 (PDT)
Received: from [192.168.4.67] (unknown [67.159.169.102]) by dougbarton.us (Postfix) with ESMTPSA id 6F73A22B1A for <ietf@ietf.org>; Mon, 14 Apr 2014 22:27:52 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397514473; bh=QUiLW2oanhg3xeX0HK1xvwUiSudrD3Ru1d3kCoz3MA8=; h=Date:From:To:Subject:References:In-Reply-To; b=aKD3niE/cn6jkLoI4AlHmz6m9vs9UnTz1rKvnfrjm/w9hoRFDU83O1LvomWc6u50n d6fRJgy3fYTpfVqGMxd0FHlg+MeiO+/NGt63ewrGle2oREIs2u6ZEJcnvDXQiNGuTV /VwGwEIcgIlssutmdBu/dz6DU0Yd87Bj2D6+vP1Q=
Message-ID: <534C60E4.8030802@dougbarton.us>
Date: Mon, 14 Apr 2014 15:27:48 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
In-Reply-To: <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/r4L31ZXRm0rcimMMWIUgdTuJa5E
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 22:28:00 -0000

On 04/14/2014 02:14 AM, John C Klensin wrote:
>
>
> --On Monday, April 14, 2014 01:08 -0700 Doug Barton
> <dougb@dougbarton.us> wrote:
>
>>> But this takes us back to Ned's point (or at least my
>>> interpretation of it): it is lots easier to fix a bad DMARC
>>> config, ignore restrictive DMARC specifications, or even to
>>> abandon DMARC entirely, than it is to believe that we can
>>> upgrade every MTA and MUA on the network to start accepting
>>> percent hacks, bang paths, or the syntax characters used to
>>> denote them, again.  Or any other strange local-part syntax
>>> anyone is likely to come up with, e.g., perhaps we could use
>>> plus signs, hyphens, or appropriately-escaped backslashes.  Or
>>> we could steal "/" and "=" back from X.400 gateways.  Right.
>>
>> Well + is out, since that's used by various local filtering
>> solutions.
>
> Doug, I think you are missing my, and probably John Levine's,
> attempts at humor.

Not so much "missing" it as ignoring it because I'd rather focus on 
finding a solution than on dark sarcasm.

>  Let me spell it out:

... yes, I get all of that, which is why I didn't suggest any of those 
characters. I also specifically didn't suggest ! because I didn't want 
to look like a throwback to UUCP.

> The bottom line is that trying to work around this by a trick
> syntax convention is really hard, unlikely to succeed, and quite
> likely to result in legitimate messages disappearing and/or
> breaking existing conforming systems.

.... which is why I'm suggesting open conversation to try and avoid 
those pitfalls. I would also like to make sure we are scoping the 
problem correctly when you say "working around _this_." John Levine has 
already attempted to derail the concept I'm actually proposing by 
arguing against something I'm not.

And while even the problem I'm actually proposing to solve is hard, 
complaining about it the fact that someone else broke mailing lists is 
definitely not going to solve it.

>> But your point is well taken ... the "right" answer may be to
>> fix or discard DMARC, I honestly don't know. But in a world
>> where DMARC is here to stay, or if not DMARC then some other
>> anti-spam solution that breaks mailing list forwarding; and in
>> that same world where mailing list traffic is negligible (and
>> therefore the cost of breaking mailing lists is in the noise
>> compared to the benefits of deploying said anti-spam solution)
>> it's incumbent on the mailing list software folks to solve
>> this problem.
>
> I'm going to risk more humor and suggest that everyone who
> believes that mailing list traffic is negligible and the cost of
> breaking them is in the noise should be immediately unsubscribed
> from all IETF-related lists, including this one.

John, if you want me off this list just say the word.

Meanwhile, *I* was not suggesting that mailing list traffic is 
unimportant, I get at least a hundred messages a day from various lists, 
and it constitutes the vast majority of my daily electronic communication.

What I AM suggesting however, and I realize that this is a hard pill to 
swallow for many IETF'ers, is that IN THE GRAND SCHEME OF THINGS mailing 
list traffic is inconsequential to large e-mail providers. It's a small 
percentage of the overall traffic they process, and AS A RESULT Yahoo!'s 
calculus clearly reached the conclusion that even though they knew they 
were going to break traffic from some percentage of their users, the 
overall benefit was worth it to them. We may not like to hear that, but 
it IS the reality. If we're going to be serious about the E in IETF 
we're a lot better off starting from the world of reality, rather than 
the world we wish we lived in.

So even if we were somehow able to magically fix DMARC today so that 
list traffic works perfectly with it, tomorrow another anti-spam 
solution is going to come along that is better than DMARC, and mailing 
list traffic as it exists currently won't work with it. The tail will 
not be wagging the dog here, the mailing list software has to be fixed 
if we want to solve this problem.

Doug


From nobody Mon Apr 14 15:33:41 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52F5F1A077E for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:33:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.426
X-Spam-Level: 
X-Spam-Status: No, score=0.426 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 9crUfXKrhoHl for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 15:33:38 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 619901A0776 for <ietf@ietf.org>; Mon, 14 Apr 2014 15:33:38 -0700 (PDT)
Received: from [192.168.4.67] (unknown [67.159.169.102]) by dougbarton.us (Postfix) with ESMTPSA id A4B7E22B1A; Mon, 14 Apr 2014 22:33:35 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397514815; bh=a+zStyLqMfpHQPr8yfATWXNLlQTHhf4X6YVYDAQrMIc=; h=Date:From:To:Subject:References:In-Reply-To; b=EqKnCl/IUL24+jgXFl3veHXh/IG2K1abMmCL+Rk3a/4JWNyhlAwb+i7U+YANPrKfs yFfzOlQgWXuP0vu9C2Xt32LGVV81bB+FuSP2P8bSbtjVxiceCmi3LQ0CezUg7qfxoY YD/dYdwGZw8Ne7hJJ+zffQ00xK2YsIDpB2d4Ov3k=
Message-ID: <534C623E.9080100@dougbarton.us>
Date: Mon, 14 Apr 2014 15:33:34 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "MH Michael Hammer (5304)" <MHammer@ag.com>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wLjIvD_RhzChmoAs_YuH_UlFyXI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Apr 2014 22:33:39 -0000

On 04/14/2014 09:53 AM, MH Michael Hammer (5304) wrote:
> The fact is that a vocal constituency led by John Levine made it extremely clear that MLMs were out of scope and there was zero interest on the part of the MLM community in discussing ways in which MLMs could be made to work in an email authentication framework even if there were any MLM operators willing to do so.

Mike,

While I appreciate your version of the history, the above (and the other 
places where you seem to be placing the blame on John Levine) read like 
a bad excuse to me. "John was mean to us" only works if John were 
somehow the elected representative of the MLM Software Cabal, and was 
speaking on their behalf.

We already have evidence that someone from the DMARC community reached 
out to the mailman devs and that resulted in forward motion on a 
solution. That effort should be both applauded and encouraged. Making 
excuses for not conducting additional such outreaches is just ... weak.

Doug


From nobody Mon Apr 14 17:05:32 2014
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BB191A0671 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:05:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 LPn72pOO8WqU for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:05:24 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 80F241A04A4 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:05:24 -0700 (PDT)
Received: from [192.168.1.65] (c-50-161-100-84.hsd1.ca.comcast.net [50.161.100.84]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3F05HHx029619 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 14 Apr 2014 17:05:21 -0700
Message-ID: <534C7746.4070706@bbiw.net>
Date: Mon, 14 Apr 2014 17:03:18 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534C60E4.8030802@dougbarton.us>
In-Reply-To: <534C60E4.8030802@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Mon, 14 Apr 2014 17:05:21 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_7ioUUDzuvaG1nPlS7JDx1YwvyE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 00:05:29 -0000

On 4/14/2014 3:27 PM, Doug Barton wrote:
> What I AM suggesting however, and I realize that this is a hard pill to
> swallow for many IETF'ers, is that IN THE GRAND SCHEME OF THINGS mailing
> list traffic is inconsequential to large e-mail providers.


That view is popular, but it's quite wrong.

What /is/ true is that mailing list traffic by users of large mailbox 
providers, through small, independent mailing list providers, is 
probably negligible.  That's the category of primary victim of the 
recent change.

Large email providers come in a few forms.

Some provide mailbox services for gillions of users.  All such services 
focus on social networking, much of which entails some form of mailing 
list or 'group' technology, though often under the guise of different 
packaging.  All of their users are under a single domain name, which is 
always a very attractive target for unauthorized use by abusers.  The 
pressure to limit abuse of the domain is what drove the recent change.

Another major player is the ESP, which does bulk marketing/subscription 
mailings to individuals.  These are, of course, list processing engines.

And so on.

In other words, this space has some complexity and nuance to it, most of 
which is being ignored in the postings over the last week, but all of 
which is actually important to any effort at navigating the challenges 
of fighting abuse while keeping things still useful.

Unfortunately, once all that complexity and nuance is factored in, the 
proper choices and balance still aren't clear...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 14 17:12:26 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54D721A06D7 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:12:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 DQ_RF_jPpPgD for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:12:14 -0700 (PDT)
Received: from mail-wg0-x22c.google.com (mail-wg0-x22c.google.com [IPv6:2a00:1450:400c:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 266411A0692 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:11:49 -0700 (PDT)
Received: by mail-wg0-f44.google.com with SMTP id m15so8714715wgh.3 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:11:47 -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:content-type; bh=mWB/WJpzKYMcvwG/fSLHVoJ7eU6/rKrAPtpHEdljN1Y=; b=04SgwSS9c9FzVS2z3+9IanBvRC+nYkzybAqqik3tzRQOnVcnuUGZPztYMIFH+5OBr0 /1VHBsyPi8XkBRaO9KTo3NYimJ+GOZpVMe8XC75BTwFKkBGEFIN0H82J8wjpVgBlsVyW TXUJgEV4sslox+JwEl9A8HhbDbKwfX9UUpG2ai9KNd4wlR+YnANAabmuhoA6Lg8KofoN 2JpWjvJDujSuEWcYxhfS7xXZ+2ipSOKP5qSE/i44YvOBHkuI+x0ZbwOd9IWFJ6ZFblE9 CcJ1nUd92UiYtX253VgOtygLHMSVm7QU84dJOXBSZT6P3KwynCRqTpGj5OP2IIQzkfXq Gm/A==
MIME-Version: 1.0
X-Received: by 10.194.188.68 with SMTP id fy4mr34919725wjc.30.1397520707120; Mon, 14 Apr 2014 17:11:47 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 17:11:46 -0700 (PDT)
In-Reply-To: <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com>
Date: Mon, 14 Apr 2014 17:11:46 -0700
Message-ID: <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=047d7bb03f9a5074c504f709a582
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LAfMxPA5WrWT1IVJ7WJfauYYSCI
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 00:12:23 -0000

--047d7bb03f9a5074c504f709a582
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 3:02 PM, Dave Cridland <dave@cridland.net> wrote:

> One of the very specific items that was on the proposed charter was
>> dealing with the question of how to integrate DMARC with mailing lists.
>> This was called out very early on as an open issue, as were some other
>> important ones:
>>
>> http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC
>>
>
> Right, but the WG was expected to make it work with mailing lists without
> changing it. Tough ask.
>

Could it not have been done as an extension?  And as I recall, one of the
proposed paths was to just record and publish DMARC as it is now, and then
get a WG going to help revise it into something that also resolves the
questions in the proposed charter, on the standards track.  This also
failed to gain acceptance.


> Sorry, but given the way in which IETF participants were asked to work on
> DMARC, there is absolutely no way you could say that the "DMARC people came
> to the IETF to [...] complete development" - it was more or less stated
> that development was done and dusted - and the IETF didn't reject it on the
> basis that no engineering work remained - the DMARC people rejected any
> engineering work happening.
>
> It doesn't actually matter whether you think the reasons behind this were
> valid; the fact is that you're putting one heck of a slant on recent
> history, and it's not borne out by what's in the archives.
>

I remember what was said.  I'm not trying to be revisionist here.  Rather,
I think I'm trying to remember all the details of a very chaotic
negotiation.

I can't say I blame the DMARC people, or anyone for that matter, for trying
to insulate itself against its work being bogged down for months or longer
rat-holing on things as has been the fate of so many past efforts in the
same area.  (See the thread Wes George started this morning separately.)
Maybe they tried too hard and maybe I even contributed.  But I also think
maybe the IETF needs to rethink its position on taking on work from outside
organizations in the first place, which was one of several road blocks that
came up.  Another is that it was too far along the deployment axis to be
eligible for consideration as new IETF work, regardless of whether the main
document was up for revision.  Yet another is that despite repeated
requests, we couldn't even more than a couple of people (I can remember
four) to submit substantive reviews of the current document; it seemed like
the IETF wasn't interested regardless of the other "regulatory" issues.

I don't have any idea how to retroactively fix all of that, and I suspect
it would be another rat-hole to try.  What I'd really like to talk about is
where we go from here.

-MSK

--047d7bb03f9a5074c504f709a582
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 3:02 PM, Dave Cridland <span dir=
=3D"ltr">&lt;<a href=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cr=
idland.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D""><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
></div><div>One of the very specific items that was on the proposed charter=
 was dealing with the question of how to integrate DMARC with mailing lists=
.=C2=A0 This was called out very early on as an open issue, as were some ot=
her important ones:<br>


<br><a href=3D"http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC" targe=
t=3D"_blank">http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC</a><span=
><font color=3D"#888888"><br></font></span></div></div></div>
</div></blockquote><div><br></div></div><div>Right, but the WG was expected=
 to make it work with mailing lists without changing it. Tough ask.</div></=
div></div></div></blockquote><div><br></div><div>Could it not have been don=
e as an extension?=C2=A0 And as I recall, one of the proposed paths was to =
just record and publish DMARC as it is now, and then get a WG going to help=
 revise it into something that also resolves the questions in the proposed =
charter, on the standards track.=C2=A0 This also failed to gain acceptance.=
<br>
=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_extra">Sorry, but given the way in which IETF participants were a=
sked to work on DMARC, there is absolutely no way you could say that the &q=
uot;DMARC people came to the IETF to [...] complete development&quot; - it =
was more or less stated that development was done and dusted - and the IETF=
 didn&#39;t reject it on the basis that no engineering work remained - the =
DMARC people rejected any engineering work happening.<div class=3D"gmail_qu=
ote">

<div><br></div><div>It doesn&#39;t actually matter whether you think the re=
asons behind this were valid; the fact is that you&#39;re putting one heck =
of a slant on recent history, and it&#39;s not borne out by what&#39;s in t=
he archives.</div>
</div></div></div></blockquote><div><br></div><div>I remember what was said=
.=C2=A0 I&#39;m not trying to be revisionist here.=C2=A0 Rather, I think I&=
#39;m trying to remember all the details of a very chaotic negotiation.<br>=
<br></div>
<div>I can&#39;t say I blame the DMARC people, or anyone for that matter, f=
or trying to insulate itself against its work being bogged down for months =
or longer rat-holing on things as has been the fate of so many past efforts=
 in the same area.=C2=A0 (See the thread Wes George started this morning se=
parately.)=C2=A0 Maybe they tried too hard and maybe I even contributed.=C2=
=A0 But I also think maybe the IETF needs to rethink its position on taking=
 on work from outside organizations in the first place, which was one of se=
veral road blocks that came up.=C2=A0 Another is that it was too far along =
the deployment axis to be eligible for consideration as new IETF work, rega=
rdless of whether the main document was up for revision.=C2=A0 Yet another =
is that despite repeated requests, we couldn&#39;t even more than a couple =
of people (I can remember four) to submit substantive reviews of the curren=
t document; it seemed like the IETF wasn&#39;t interested regardless of the=
 other &quot;regulatory&quot; issues.<br>
<br>I don&#39;t have any idea how to retroactively fix all of that, and I s=
uspect it would be another rat-hole to try.=C2=A0 What I&#39;d really like =
to talk about is where we go from here.<br><br></div><div>-MSK<br></div></d=
iv>
</div></div>

--047d7bb03f9a5074c504f709a582--


From nobody Mon Apr 14 17:34:59 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A8511A04A4 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:34:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.462
X-Spam-Level: 
X-Spam-Status: No, score=-1.462 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=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 oui0Tn5LXHy4 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:34:53 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CF56B1A044C for <ietf@ietf.org>; Mon, 14 Apr 2014 17:34:53 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.146.211]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3F0YZHJ008086 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 14 Apr 2014 17:34:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397522087; bh=BMCaWw1H8TJi3cgRaFZ8Tll+pFJerrf+Kpc5ZPaUsqg=; h=Date:To:From:Subject:In-Reply-To:References; b=s5vRMeFhgU+mOJHzT2wIhVJRdZFgL/q/eqEVH/GlSOAzT3Cumf4Ho4l9V/xEVqU9x bIPDc0qXAJK9ZGDD5xIk01DbtPqjb1dKs4clTR7KHwi656VKzlkVLsI44NNhdIPdgW F1kfCnACKQYC1iSfKI+jRnUuO2aHcpXuxfZi5Ftw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397522087; i=@elandsys.com; bh=BMCaWw1H8TJi3cgRaFZ8Tll+pFJerrf+Kpc5ZPaUsqg=; h=Date:To:From:Subject:In-Reply-To:References; b=RcHYxNe2I2gDJp2+zZKFNPNBYsLfpgxTYOCestO8kekmT33r/Ke86j3LNhXF5w5sS p68xagjXbEW1WtRM9HyEIbOrr+YOXN0/ybdR6bBQAFYkoteBnGUMp+SGXn9MQNqfOf gVUz1GdmhU/7pllfxrZmAViavclsLGWPsV75wC3I=
Message-Id: <6.2.5.6.2.20140414153913.0d0fe480@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 Apr 2014 16:50:08 -0700
To: "MH Michael Hammer (5304)" <MHammer@ag.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.am greetings.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Y7v_LEv-ScrlLZh-KWzIrRDQR4U
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 00:34:58 -0000

Hi Mike,
At 09:53 14-04-2014, MH Michael Hammer (5304) wrote:
>The fact is that a vocal constituency led by John Levine made it 
>extremely clear that MLMs were out of scope and there was zero 
>interest on the part of the MLM community in discussing ways in 
>which MLMs could be made to work in an email authentication 
>framework even if there were any MLM operators willing to do so. His 
>stated solution has been and continues to be that list operators 
>should drop any participants who post from a domain publishing 
>p=reject and to prevent any new participants from joining from a 
>domain that publishes p=reject. The record is quite clear on this 
>and is available to anyone who wishes to peruse email archives, blog 
>posts, etc. I view this as local policy and up to the list operator. 
>I'm not confident how well this will ultimately work for many 
>organizations the operators manage lists for. Just to be clear, the 
>preceding is more of a question than an assertion.

I don't think that there is zero interest from the Mailman community 
(that's my interpretation of the Mailman discussions).  Mailman 
developers do not participate in the IETF.  There is an employee of a 
well-known company who has been arguing for changes to the mailing 
list management software since a long time.  The Mailman patch for 
DMARC was written by Jim Popovitch and Phil Pennock ( 
https://mail.python.org/pipermail/mailman-developers/2013-October/023349.html 
and 
https://mail.python.org/pipermail/mailman-developers/2013-November/023384.html 
).

Mailing list traffic is not significant in comparison with overall 
mail traffic.  At the risk of sounding insensitive there isn't a 
business case for some providers to support mailing list traffic.  I 
would consider John Levine's point about making it out of 
scope.  There's still the problem of what to do about mailing lists.

Regards,
S. Moonesamy  


From nobody Mon Apr 14 17:45:51 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9F41A06A6 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:45:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 gNtM57pGY-va for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:45:48 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5B97B1A069E for <ietf@ietf.org>; Mon, 14 Apr 2014 17:45:48 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id lf10so8946490pab.13 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:45:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=YJL00wi/zZ9mleykhxoj92IhrwIMUe/xcOcslcFZoZc=; b=bUZzuTA+pMxdfEPIyddzgA2j1ZCEREui5KFByhZrwRj5LWd+4KDsDNt7hadgiKyAD7 3yg4UNVUd1Lw1I6YNmDyCGbB9tis+ASbriQjpqO8Em4+2C6mdhE2dkxz9ZTeUncYPevT k23qq6eN0u8v/ZftwVU2GH9iZFU5mCr0EA6rBKKqBrIE8pCCwNlZh+E7pwUAMCWQ8b0Z tDX4ELYgQN/6Dn5DLTi87PoeXZXBkVlYDsIqZiu0+LIdG9a/GLxMi2FEzH+MN21O2l/C DnXj4w72I6LeYg+dL40L+J9V3FrGBhKZOLsBWqN8dpUY0O9gbGZFAfrwQ+HT2eXRThq7 gP3A==
X-Received: by 10.68.212.10 with SMTP id ng10mr47345581pbc.95.1397522745803; Mon, 14 Apr 2014 17:45:45 -0700 (PDT)
Received: from dhcp150.priv.bungi.com (c-24-4-159-60.hsd1.ca.comcast.net. [24.4.159.60]) by mx.google.com with ESMTPSA id i10sm87114465pat.36.2014.04.14.17.45.43 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Apr 2014 17:45:44 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com>
Date: Mon, 14 Apr 2014 17:45:45 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <44378438-ABC4-4D18-B284-FF2808CC87A5@gmail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yQRpeMnRVIWKHoqsOkhdHLEjsAs
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 00:45:50 -0000

On Apr 14, 2014, at 5:11 PM, Murray S. Kucherawy <superuser@gmail.com> =
wrote:
>=20
> I don't have any idea how to retroactively fix all of that, and I =
suspect it would be another rat-hole to try.  What I'd really like to =
talk about is where we go from here.

Dear Murray,

Perhaps the IESG now has more of an open mind regarding risks associated =
with an "authoritative"  domain responding to a query about a =
third-party domain impacting the delivery of their users email. =20

I'll be happy to re-write the ATPS or ATP draft to offer a simpler, =
deployable, and functional version able to support aggregated listings.  =
Brian has already asked that this not be done as an individual =
submission.  It seems fruitless trying to motivate bulk senders or large =
ISPs into addressing this problem.  This is something the "email =
community" needs to solve.  At most, it should involve a simple =
reference to a ATP listing domain.

1) make use of existing authentication schemes, not just DKIM.
2) always generate consistent labels to ensure fewer community =
conflicts.

Regards,
Douglas Otis=


From nobody Mon Apr 14 17:46:42 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 763881A06E4 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ChfSPmPkhcp8 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:46:36 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 67FAC1A06D4 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:46:36 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id B68AACC0C1 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:46:33 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id L2n+prZeKIpf for <ietf@ietf.org>; Mon, 14 Apr 2014 20:46:25 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id D74E7CC0BF for <ietf@ietf.org>; Mon, 14 Apr 2014 20:46:24 -0400 (EDT)
Message-ID: <534C8160.70608@meetinghouse.net>
Date: Mon, 14 Apr 2014 20:46:24 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534C60E4.8030802@dougbarton.us> <534C7746.4070706@bbiw.net>
In-Reply-To: <534C7746.4070706@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/W_EFf1i8raERFiZLfAEto4vuRjQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 00:46:38 -0000

Dave Crocker wrote:
> On 4/14/2014 3:27 PM, Doug Barton wrote:
>> What I AM suggesting however, and I realize that this is a hard pill to
>> swallow for many IETF'ers, is that IN THE GRAND SCHEME OF THINGS mailing
>> list traffic is inconsequential to large e-mail providers.
>
>
> That view is popular, but it's quite wrong.
>
> What /is/ true is that mailing list traffic by users of large mailbox 
> providers, through small, independent mailing list providers, is 
> probably negligible.  That's the category of primary victim of the 
> recent change.

I'm not sure that's true, Dave.

The lists I run, these days, are for things like community 
organizations, parent-teacher groups, churches, and such.  What I find 
is that over half of my subscribers - both in the high-income city where 
I live, and Boston Public Schools (where I used to live) - are coming in 
through yahoo and hotmail accounts, followed by a mix of ISP accounts 
with broadband providers (Comcast, RCN, Verizon in these climes).

Now an awful lot of these folks ALSO have work email, and a lot of some 
other personal email address - so my guess is that:
- folks who don't do a lot of email, sign up for a yahoo or hotmail 
account because it's free and easy
- more sophisticated folks, sign up for a free account to segregate 
truly personal, and work related email from lists, and commercial sites

This also doesn't seem to be limited to more settled folks - all three 
of my college/just-post-college kids have either a hotmail, yahoo, or 
gmail account (1 each) - again, probably because it's free.  They use 
accounts on one of my servers for more official things like job 
applications.

Now, given that pretty much every parent with a kid in the local schools 
is on a parent-teacher email list; and everyone in the two churches I 
support is on their respective email lists; and there are very active 
neighborhood level parent and community lists - there are an awful lot 
of email list users around here.  I expect the same is true elsewhere 
(how many people reading this are on a school or church related list, 
not to mention various technical lists?).  And I note that those lists 
are all quite active.

Now, the list activity is still dwarfed by spam - but once you filter 
out the spam, and general commercial crap, I expect what's left in most 
people's email is a mix of directly personal, work, email lists, and 
notifications from social network sites.

I could be wrong on this - but I have a pretty good window into email 
use in this corner of the world, and that's what I see.

Cheers,

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 17:53:16 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61BD01A06FE for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 lvcm92GNSJIG for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 17:53:13 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 10B5F1A06F9 for <ietf@ietf.org>; Mon, 14 Apr 2014 17:53:12 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 28066CC09B for <ietf@ietf.org>; Mon, 14 Apr 2014 20:53:10 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id h18q4WaeCbE6 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:53:01 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 31590CC0C5 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:53:01 -0400 (EDT)
Message-ID: <534C82EC.5040001@meetinghouse.net>
Date: Mon, 14 Apr 2014 20:53:00 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <6.2.5.6.2.20140414153913.0d0fe480@resistor.net>
In-Reply-To: <6.2.5.6.2.20140414153913.0d0fe480@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GTiVcvouxSOC--z5X2cWb6VLfNU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 00:53:14 -0000

S Moonesamy wrote:
>
> Mailing list traffic is not significant in comparison with overall 
> mail traffic.  At the risk of sounding insensitive there isn't a 
> business case for some providers to support mailing list traffic. I 
> would consider John Levine's point about making it out of scope.  
> There's still the problem of what to do about mailing lists.

Depends on what you mean by "significant."

I'm probably being redundant here, after my previous response to Dave - 
but I expect that once you filter out the 90% of traffic that's pure 
spam, email traffic is a VERY significant portion of what's left.  (For 
that matter, it's probably true of postal mail too.  Most of what comes 
through the slot is junk mail, throw that away and it's a mix of 
personal mail and magazines.)

Not that much different than email being a wart on the side of Internet 
traffic - until you filter out the video.  By transaction count, email 
dwarfs everything else, probably even after discounting for spam.

Now, if you're an ISP or ESP that makes money off of sending bulk email, 
or providing a home for outbound spammers, maybe you don't consider list 
traffic to be "significant."  But if you're an individual email USER - I 
expect that one or two email lists represent the MOST significant part 
of your email stream.

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 18:06:40 2014
Return-Path: <rwfranks@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0536A1A0669 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:06:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 romgj2H3h5Iy for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:06:34 -0700 (PDT)
Received: from mail-yh0-x22b.google.com (mail-yh0-x22b.google.com [IPv6:2607:f8b0:4002:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFD61A024C for <ietf@ietf.org>; Mon, 14 Apr 2014 18:06:34 -0700 (PDT)
Received: by mail-yh0-f43.google.com with SMTP id b6so8731225yha.2 for <ietf@ietf.org>; Mon, 14 Apr 2014 18:06:31 -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:from:date:message-id :subject:to:cc:content-type; bh=5s5qAytMPAOnINr0gRUGHziKQC+2dtYqCPgQqWeFuXE=; b=htlxi5duiYUoD4JW5pXkTUJU1NaQjztGoX0W4oSdeD5H2XmyAiKoncDD+3tTDMm+LB tYFnOnXjIS889+iND/BNxyJmvYfawpcPoc9egHTZnZOpgceHuQq3a6Y9VYcgHWV6Tkgv fm8uuKG/VOo+4u56ze+wcqKwHCoVpCLADUjFpNrSHo+QRa80rYP2gMEqYMEh/b0DqO6V PxcjsZ74tHTzabL36PWCAk6BZg46CITU6jGawOoMUTT1FF85VaHcuhkmRwphP6Tpz3ca hMDPMnilFiYEziSisEmfjPEqOLXeacSpNkHB39S8spKzJJ4G63XiBFkA2uYScURhmUe6 3V2g==
X-Received: by 10.236.116.99 with SMTP id f63mr60783862yhh.10.1397523991783; Mon, 14 Apr 2014 18:06:31 -0700 (PDT)
MIME-Version: 1.0
Sender: rwfranks@gmail.com
Received: by 10.170.129.143 with HTTP; Mon, 14 Apr 2014 18:05:51 -0700 (PDT)
In-Reply-To: <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com>
From: Dick Franks <rwfranks@acm.org>
Date: Tue, 15 Apr 2014 02:05:51 +0100
X-Google-Sender-Auth: 8NbSQfgf-_HGFgP2txjw-zmBRyA
Message-ID: <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=20cf3036387d186d0604f70a6993
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Q10f9ttFd2ODJj9zB2WhtubVv7U
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 01:06:37 -0000

--20cf3036387d186d0604f70a6993
Content-Type: text/plain; charset=UTF-8

On 14 April 2014 22:17, Murray S. Kucherawy <superuser@gmail.com> wrote:

> On Mon, Apr 14, 2014 at 1:24 PM, Dick Franks <rwfranks@acm.org> wrote:
>
>  2)  Publicly refutes any claim that this is an IETF standardisation
>> effort.
>>
>
> Any such claim is merely outdated and needs correction.
>

 Correct it and the objection goes away.

--20cf3036387d186d0604f70a6993
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div dir=3D"ltr"><span></s=
pan></div></div>
<br><br><div class=3D"gmail_quote">On 14 April 2014 22:17, Murray S. Kucher=
awy <span dir=3D"ltr">&lt;<a href=3D"mailto:superuser@gmail.com" target=3D"=
_blank">superuser@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">

<div dir=3D"ltr"><div class=3D"">On Mon, Apr 14, 2014 at 1:24 PM, Dick Fran=
ks <span dir=3D"ltr">&lt;<a href=3D"mailto:rwfranks@acm.org" target=3D"_bla=
nk">rwfranks@acm.org</a>&gt;</span> wrote:<br></div><div class=3D"gmail_ext=
ra"><br>

<div class=3D"gmail_quote"><div class=3D""><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
>2)=C2=A0 Publicly refutes any claim that this is an IETF standardisation e=
ffort.<br></div></div></div></div></blockquote><div><br></div></div><div>
Any such claim is merely outdated and needs correction.</div></div></div></=
div></blockquote><div><br></div><div>=C2=A0Correct it and the objection goe=
s away.<br></div></div><br></div></div>

--20cf3036387d186d0604f70a6993--


From nobody Mon Apr 14 18:21:41 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3E01A0397 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:21:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.399
X-Spam-Level: *
X-Spam-Status: No, score=1.399 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 F6venaHz1zzs for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:21:35 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.4]) by ietfa.amsl.com (Postfix) with ESMTP id B8CA71A02F6 for <ietf@ietf.org>; Mon, 14 Apr 2014 18:21:34 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES532.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Mon, 14 Apr 2014 21:21:31 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: John Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: protecting the Internet from DMARC damage, was perspectives
Thread-Topic: protecting the Internet from DMARC damage, was perspectives
Thread-Index: AQHPWCuK1AzJKLxP3EO5kHczw4HabZsRrAfQ
Date: Tue, 15 Apr 2014 01:21:30 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan>
In-Reply-To: <20140414214949.32126.qmail@joyce.lan>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_rSfi1uqPdDCIVTkwf6dtNXNqaQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 01:21:37 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogSm9obiBMZXZpbmUgW21h
aWx0bzpqb2hubEB0YXVnaC5jb21dDQo+IFNlbnQ6IE1vbmRheSwgQXByaWwgMTQsIDIwMTQgNTo1
MCBQTQ0KPiBUbzogaWV0ZkBpZXRmLm9yZw0KPiBDYzogTUggTWljaGFlbCBIYW1tZXIgKDUzMDQp
DQo+IFN1YmplY3Q6IFJlOiBwcm90ZWN0aW5nIHRoZSBJbnRlcm5ldCBmcm9tIERNQVJDIGRhbWFn
ZSwgd2FzIHBlcnNwZWN0aXZlcw0KPiANCj4gPlRoZSBmYWN0IGlzIHRoYXQgYSB2b2NhbCBjb25z
dGl0dWVuY3kgbGVkIGJ5IEpvaG4gTGV2aW5lIG1hZGUgaXQNCj4gPmV4dHJlbWVseSBjbGVhciB0
aGF0IE1MTXMgd2VyZSBvdXQgb2Ygc2NvcGUgYW5kIHRoZXJlIHdhcyB6ZXJvIGludGVyZXN0DQo+
ID5vbiB0aGUgcGFydCBvZiB0aGUgTUxNIGNvbW11bml0eSBpbiBkaXNjdXNzaW5nIHdheXMgaW4g
d2hpY2ggTUxNcyBjb3VsZA0KPiBiZSBtYWRlIHRvIHdvcmsgaW4gYW4gZW1haWwgYXV0aGVudGlj
YXRpb24gZnJhbWV3b3JrIGV2ZW4gaWYgdGhlcmUgd2VyZQ0KPiBhbnkgTUxNIG9wZXJhdG9ycyB3
aWxsaW5nIHRvIGRvIHNvLiAuLi4NCj4gDQo+IERNQVJDIG11c3QgYmUgaW4gcHJldHR5IGJhZCBz
aGFwZSBpZiBpdHMgcHJvcG9uZW50cyBoYXZlIHRvIHJlc29ydCB0bw0KPiBtYWxpY2lvdXMgbGll
cyBsaWtlIHRoaXMuICBJdCBzYWRkZW5zIG1lIHRoYXQgTWlrZSwgd2hvIEkgdXNlZCB0byBjb25z
aWRlciBhDQo+IGZyaWVuZCwgd291bGQgZG8gc28uDQo+IA0KDQpKb2huLCB5b3VyIHBvc2l0aW9u
IGhhcyBiZWVuIGFic29sdXRlbHkgY29uc2lzdGVudCB0aHJvdWdoIHRoZSB5ZWFycy4gWW91ciBj
b21tZW50cyBiZWxvdyByZWZsZWN0IHRoYXQuIFlvdXIgY29tbWVudHMgaW4gdGhlIElFVEYtREtJ
TSB3b3JraW5nIGdyb3VwIHJlZmxlY3RlZCB0aGF0IGFzIHdlbGwuIEknbSBzb3JyeSB5b3Ugbm8g
bG9uZ2VyIGNvbnNpZGVyIG1lIGEgZnJpZW5kIGJ1dCB5b3VyIHBvc2l0aW9uIGhhcyBjb25zaXN0
ZW50bHkgYmVlbiAid2UgYXJlIG5vdCBicm9rZW4sIG5vdyBnbyBhd2F5Ii4gSWYgdGhlIHdvcmxk
IHdlcmUgZW5jYXNlZCBpbiBhbWJlcmdyaXMgdGhhdCBtaWdodCBiZSBhIHVzZWZ1bCBwb3NpdGlv
biBidXQgdGhlIHdvcmxkIGlzIG5vdC4gV2UgaGF2ZSBkaXNhZ3JlZWQgb24gdGhpcyBmb3Igb3Zl
ciBhIGRlY2FkZS4NCg0KPiBNeSBwb3NpdGlvbiBoYXMgYWx3YXlzIGJlZW4gcGVyZmVjdGx5IGNs
ZWFyOiBtYWlsaW5nIGxpc3RzIGFyZSBub3QgYnJva2VuLCB0aGV5DQo+IHByb3ZpZGUgYSBzaWdu
aWZpY2FudCBzZXJ2aWNlIHRvIGluZGl2aWR1YWwgSW50ZXJuZXQgbWFpbCB1c2VycywgYW5kIGl0
IGlzIG5vdCBvdXINCj4gam9iIHRvIHNwZW5kIHRpbWUgYW5kIG1vbmV5IHRvIHNvbHZlIG90aGVy
IHBlb3BsZSdzIHByb2JsZW1zLiAgRE1BUkMsIGxpa2UNCj4gYWxsIG9mIGl0cyBwcmVkZWNlc3Nv
ciBhdXRoZW50aWNhdGlvbiBzY2hlbWVzLCBoYXMgYSBtb2RlbCBvZiB0aGUgd2F5IHBlb3BsZQ0K
PiBzZW5kIG1haWwgdGhhdCBkZXNjcmliZXMgbXVjaCBidXQgbm90IGFsbCBvZiB0aGUgYWN0dWFs
IG1haWwgcGVvcGxlIHNlbmQuDQo+IFRoZXJlIGFyZSBhbiBhd2Z1bCBsb3Qgb2Ygd2F5cyB0aGF0
IHBlb3BsZSBzZW5kIG1haWwsIHNvIHRoaXMgc2hvdWxkbid0IGNvbWUNCj4gYXMgYSBzdXJwcmlz
ZSB0byBhbnlvbmUuDQo+IA0KDQpIb3cgZG9lcyB5b3VyIHN0YXRlbWVudCBzdWJzdGFudGl2ZWx5
IGRpZmZlciBmcm9tIHdoYXQgSSB3cm90ZSBpbiBteSBwcmV2aW91cyBwb3N0PyBZb3UgZXhwbGlj
aXRseSBzdGF0ZSB0aGF0IGl0IGlzIG5vdCB5b3VyIHByb2JsZW0gYW5kIGl0IGlzIHNvbWVib2R5
IGVsc2UncyBwcm9ibGVtLiBZb3UgaGF2ZSBiZWVuIHZvY2FsIGFib3V0IHlvdXIgcG9zaXRpb24g
Zm9yIHllYXJzIGFuZCB5ZWFycy4gWW91IG1heSBub3QgbGlrZSBteSBjaGFyYWN0ZXJpemF0aW9u
IG9mIHlvdXIgcG9zaXRpb24gYnV0IHRoYXQgaXMgeW91ciBwb3NpdGlvbiBub25ldGhlbGVzcy4g
SXQgaXMgbm90IHNpbXBseSB0aGF0IHlvdSB0b29rIHRoYXQgcG9zaXRpb24gcmVnYXJkaW5nIERN
QVJDIGJ1dCB0aGF0IHlvdSBoYXZlIGNvbnNpc3RlbnRseSB0YWtlbiB0aGF0IHBvc2l0aW9uIGZv
ciBBTlkgZGlzY3Vzc2lvbiByZWdhcmRpbmcgcG90ZW50aWFsIGNoYW5nZXMgdG8gTUxNcyBmb3Ig
QU5ZIGNoYW5nZXMgdGhhdCBtaWdodCByZWxhdGUgdG8gYXV0aGVudGljYXRpb24uIFlvdXIgcG9z
aXRpb24gaGFzIGJlZW4gdGhhdCB0aGUgY29tbXVuaXR5IGF0IGxhcmdlIGNhbiByZWx5IG9uICJ5
b3VyIiByZXB1dGF0aW9uICh0aGUgYWN0dWFsIGV4YW1wbGUgeW91IGdhdmUgaW4gdGhlIFNTUCBk
aXNjdXNzaW9uIGluIDIwMDggcmVsYXRlZCB0byB0aGUgSUVURi1ES0lNIGxpc3QgaG9zdGVkIGJ5
IERhdmUgQ3JvY2tlcikuIFdoaWxlIHlvdSAob3IgRGF2ZSkgbWF5IGhhdmUgYW4gZXhjZWxsZW50
IHJlcHV0YXRpb24gLSBhbmQgSSBhZ3JlZSB0aGF0IHlvdSBkbyBkZXNwaXRlIG91ciBkaWZmZXJl
bmNlcyAtIHRoYXQgaXMgbm90IHRoZSBiYXNpcyBmb3IgYSBzY2FsYWJsZSBzdGFuZGFyZC4gWW91
IGFzc2VydCB0aGF0IGxpc3RzIGFyZSBub3QgYW5kIGhhdmUgbm90IGJlZW4gYSB2ZWN0b3IgZm9y
IGFidXNlLiBJJ3ZlIHNlZW4gYWJ1c2UgdGhyb3VnaCBsaXN0cyB3aGVyZSBhIHN1YnNjcmliZXIg
YWNjb3VudCBoYXMgYmVlbiBjb21wcm9taXNlZC4gWWVzIGl0IG1heSBnZXQgYWRkcmVzc2VkIGJ5
IG9wZXJhdG9ycywgc29tZSBmYXN0ZXIgdGhhbiBvdGhlcnMuIFJhdGhlciB0aGFuIHdvcmtpbmcg
dG8gZmluZCBhIG1vZGVsIChvciBleHBhbmQgZXhpc3Rpbmcgb25lcykgdG8gYWRkcmVzcyB0aGUg
dXNlIGNhc2VzIHlvdSBjbGFpbSB3b24ndCB3b3JrIG9yIHNob3VsZG4ndCBiZSBjaGFuZ2VkIGJl
Y2F1c2UgIndlIHdlcmUgaGVyZSBmaXJzdCBhbmQgaXQgd29ya3MgZm9yIHVzIiwgSSB3b3VsZCBh
c3NlcnQgdGhhdCBpdCBpcyBiZW5lZmljaWFsIHRvIHRoZSBjb21tdW5pdHkgdG8gaGF2ZSB0aGUg
ZGlzY3Vzc2lvbnMgdG8gY29tZSB1cCB3aXRoIHN0YW5kYXJkcyBhbmQgcHJhY3RpY2VzIHRoYXQg
cHJvdGVjdCBlbmQgdXNlcnMgZnJvbSBhYnVzZS4gDQoNCj4gVGhlIGludmFyaWFibGUgbmV4dCBz
dGVwIGlzIHRoYXQgc29tZSBvZiB0aGUgcHJvcG9uZW50cyBvZiB0aGUgc2NoZW1lLA0KPiByYXRo
ZXIgdGhhbiByZWNvZ25pemluZyBhbmQgYWRtaXR0aW5nIHRvIGl0cyBsaW1pdGF0aW9ucywgZGVj
bGFyZSB0aGF0IHRoZSBtYWlsDQo+IHRoZSBzY2hlbWUgY2FuJ3QgZGVzY3JpYmUgaXMgYmFkIGFu
ZCBtdXN0IGJlIGVyYWRpY2F0ZWQsIHdpdGggdGhlIHRlcm0NCj4gImZvcmdlZCIgb2Z0ZW4gbWlz
dXNlZC4gIFBlb3BsZSB3aG8gaGF2ZSBiZWVuIGFyb3VuZCBsb25nIGVub3VnaCB3aWxsDQo+IHJl
bWVtYmVyIHdoZW4gdGhlIFNQRiBjcm93ZCBkZW1hbmRlZCB0aGF0IGV2ZXJ5b25lIHN0b3AgZm9y
d2FyZGluZw0KPiBtYWlsLCBvciBhIGZldyBwZW9wbGUgd2FudGVkIHRvIGFwcGx5IHN0cmljdCBE
S0lNIEFEU1AgdG8gZXZlcnl0aGluZy4NCj4gTWFpbGluZyBsaXN0cyBhcmUgdGhlIG1vc3Qgb2J2
aW91cyBzZW5kaW5nIHNjZW5hcmlvIHRoYXQgRE1BUkMgZG9lc24ndA0KPiBkZXNjcmliZSwgYnV0
IGl0J3MgZmFyIGZyb20gdGhlIG9ubHkgb25lLg0KPiANCg0KWW91IGFyZSBhYnNvbHV0ZWx5IGNv
cnJlY3QgaW4gc3RhdGluZyB0aGF0IERNQVJDIGRvZXNuJ3QgYWRkcmVzcyBtYWlsaW5nIGxpc3Rz
IC0gYmVjYXVzZSB5b3UgaGF2ZSBzdGFrZWQgb3V0IGEgcG9zaXRpb24gdGhhdCBtYWlsaW5nIGxp
c3RzIHNob3VsZCBub3QgaGF2ZSB0byBjaGFuZ2UgaW4gYW55IHdheSBzaGFwZSBvciBmb3JtIHRv
IGRlYWwgd2l0aCBhbnkgYXV0aGVudGljYXRpb24gbW9kZWwuIFRoYXQgaXMgZXh0cmVtZWx5IGNv
bnN0cmFpbmluZyBvdXQgb2YgdGhlIGdhdGUgYW5kIHByZXR0eSBtdWNoIGVuZHMgYW55IG1lYW5p
bmdmdWwgZGlzY3Vzc2lvbiBhdCB0aGF0IHBvaW50LiAiSG93IGFib3V0IGlmIHdlLi4uIE5PISIN
Cg0KPiBJIGhhdmUgYWx3YXlzIHNhaWQgdGhhdCBETUFSQyBpcyB1c2VmdWwgZm9yIGEgbG90IG9m
IG1haWwsIHN1Y2ggYXMgdGhlICJzcGFtDQo+IGNhbm5vbiIgc3R1ZmYgKGEgY29tbWVudCBvbiB0
aGUgdm9sdW1lLCBub3QgbmVjZXNzYXJpbHkgdGhlDQo+IGNoYXJhY3RlcikgdGhhdCBNaWtlJ3Mg
ZW1wbG95ZXIgc2VuZHMsIG9yIHRoYXQgUGF5cGFsIGFuZCBiYW5rcyBzZW5kLg0KPiBBcyB3ZSBo
YXZlIHNlZW4sIGl0IGZhaWxzIG1pc2VyYWJseSBmb3IgZG9tYWlucyB3aXRoIG5vbi1lbXBsb3ll
ZSBsaXZlDQo+IHVzZXJzLg0KPiANCg0KSSBoYXZlbid0IHB1c2hlZCBmb3IgRE1BUkMgdG8gYmUg
YXBwbGllZCB0byBkb21haW5zIHdpdGggZW5kIHVzZXJzIGJ1dCB0aGUgZmFjdCB0aGF0IGl0ICJm
YWlscyBtaXNlcmFibHkiIChmb3Igc29tZSBkZWZpbml0aW9uIG9mIGZhaWwpIHJlZmxlY3RzIG1v
cmUgb24gYSBsYWNrIG9mIGRpc2N1c3Npb24gYW5kIGVmZm9ydCBvbiBob3cgaXQgKG9yIG90aGVy
IGFwcHJvYWNoZXMpIG1pZ2h0IHdvcmsgKGR1ZSB0byBpbnRyYW5zaWdlbmNlKSByYXRoZXIgdGhh
biB0aGUgZmFjdCB0aGF0IGl0IG9yIHNvbWUgb3RoZXIgYXBwcm9hY2ggY291bGQgd29yay4NCg0K
PiBXaXRob3V0IGV4Y2VwdGlvbiB0aGUgd2F5cyBwcm9wb3NlZCB0byBjaGFuZ2UgTUxNcyB0byAi
dG8gd29yayBpbiBhbg0KPiBlbWFpbCBhdXRoZW50aWNhdGlvbiBmcmFtZXdvcmsiIGhhdmUgaW52
b2x2ZWQgcmVtb3ZpbmcgdXNlZnVsIGZlYXR1cmVzDQo+IGFkZGVkIG92ZXIgdGhlIGRlY2FkZXMg
dGhhdCBvdXIgdXNlcnMgdXNlIGFuZCBsaWtlLCBzbyBpdCBhbHNvIHNob3VsZG4ndCBiZSBhDQo+
IHN1cnByaXNlIHRoYXQgd2UncmUgbm90IGludGVyZXN0ZWQgaW4gYm93ZGxlcml6aW5nIG91ciBz
ZXJ2aWNlIHRvIHNvbHZlIHRoZWlyDQo+IHByb2JsZW0uICBXZSBhbHNvIG5vdGUgdGhhdCBtYW55
IG9mIHRoZSBwcm9wb3NlZCBzb2x1dGlvbnMgYXJlDQo+IG92ZXJjb21wbGljYXRlZCBhbmQgdW5s
aWtlbHkgdG8gd29yayBpbiBwcmFjdGljZSAob3JpZ2luYWwtYXV0aGVudGljYXRpb24tDQo+IHJl
c3VsdHMpIG9yIGp1c3QgcGxhaW4gd29uJ3Qgd29yayAodHVybmluZyBvZmYgYWxsIHN1YmplY3Qg
dGFncywgbWVzc2FnZSBmb290ZXJzLA0KPiBhbmQgb3RoZXIgbWVzc2FnZQ0KPiBtb2RpZmljYXRp
b25zLikNCj4gDQoNCkpvaG4sIGFidXNlIGlzIGEgY29tbXVuaXR5IHByb2JsZW0uIEkgaGF2ZW4n
dCBiZWVuIGludm9sdmVkIGluIGFueSBvZiB0aGUgcHJvcG9zZWQgc29sdXRpb25zIHJlZ2FyZGlu
ZyBtYWlsaW5nIGxpc3RzIHdoaWNoIHlvdSBtZW50aW9uIGZvciBwcmVjaXNlbHkgdGhlIHJlYXNv
biB0aGF0IHlvdSAoQXMgdGhlIHZvaWNlIG9mIE1MTSBkZXZlbG9wZXJzIGFuZCBvcGVyYXRvcnMp
IGhhdmUgbWFkZSBjbGVhciB0aGF0IHRoZXJlIGlzIGFic29sdXRlbHkgbm8gaW1wbGVtZW50YXRp
b24gKG90aGVyIHRoYW4gbGVhdmUgeW91IHRvIHlvdXIgb3duIGRldmljZXMpIHRoYXQgaXMgYWNj
ZXB0YWJsZS4gSSBkb24ndCBjb3VudCB1c2luZyBzZXBhcmF0ZSBJUHMgYW5kIHNpZ25pbmcgbWFp
bCBlbWl0dGVkIGJ5IHlvdXIgc2VydmVycyAoZm9yIGRvbWFpbnMgb3RoZXIgdGhhbiB5b3VyIG93
bikgYXMgYSBtZWFuaW5nZnVsIGVmZm9ydC4gSSdtIGp1c3Qgbm90IHRoZSBraW5kIG9mIGd1eSB3
aG8gYWNjZXB0cyAidHJ1c3QgbWUiIGFzIGEgbWVhbmluZ2Z1bCBhbnRpLWFidXNlIHNvbHV0aW9u
Lg0KDQo+IElmIHRoZSBETUFSQyBjcm93ZCB3ZXJlIGludGVyZXN0ZWQgaW4gYmVpbmcgZ29vZCBu
ZXQgY2l0aXplbnMsIHRoZXJlIGlzIGENCj4gd2F5IHRvIGRlYWwgd2l0aCBETUFSQydzIGxpbWl0
YXRpb25zIHRoYXQgaXMgc3RyYWlnaHRmb3J3YXJkIGJ1dCBub3QgZnJlZToNCj4gd2hpdGVsaXN0
aW5nLiAgTW9zdCBvZiB0aGUgbGlzdHMgSSBzZWUgc2lnbiB0aGVpciBtYWlsLCBhbmQgdGhleSBn
ZW5lcmFsbHkgdXNlDQo+IHN0YXRpYyBJUCBzZW5kaW5nIGFkZHJlc3Nlcywgc28gdGhleSdyZSBu
b3QgaGFyZCB0byBjaGFyYWN0ZXJpemUuICBUaGUgc2V0IG9mDQo+IG1haWxpbmcgbGlzdHMgYW5k
IG90aGVyIGxlZ2l0aW1hdGUgbWFpbCBzb3VyY2VzIHRoYXQgRE1BUkMgZG9lc24ndCBkZXNjcmli
ZSBpcw0KPiBub3QgZW5vcm1vdXMsIGFuZCBpdCBzaG91bGQgYmUgcG9zc2libGUgdG8gZGV2ZWxv
cCBzaGFyZWQgd2hpdGVsaXN0cyBmb3INCj4gdGhlbSwgaWYgc29tZW9uZSB3ZXJlIHdpbGxpbmcg
dG8gcGF5IGZvciBkb2luZyBzby4gIChUaGlzIGlzIGEgbXVjaCBzbWFsbGVyDQo+IHByb2JsZW0g
dGhhbiB0cnlpbmcgdG8gd2hpdGVsaXN0IGFsbCAibGVnaXRpbWF0ZSIgbWFpbC4pIElmIHRoZSBs
aXN0LXdoaXRlbGlzdA0KPiBncm91cCBzYWlkIHRoYXQgbGlzdHMgbmVlZCB0byBzaWduIHRoZWly
IG1haWwgb3IgdXNlIGFuIHVuc2hhcmVkIElQIHRvIGdldA0KPiB3aGl0ZWxpc3RlZCwgeW91IHdv
dWxkIGZpbmQgbGl0dGxlIHJlc2lzdGFuY2UsIGJvdGggYmVjYXVzZSBtb3N0IG9mIHVzIGRvIHRo
YXQNCj4gYWxyZWFkeSwgYW5kIGJlY2F1c2UgaXQgZG9lc24ndCBhc2sgdXMgdG8gbWFrZSBvdXIg
bGlzdHMgd29yc2UgZm9yIG91ciB1c2Vycy4NCj4gDQoNCllvdSBoYXZlIHB1dCBmb3J3YXJkIHRo
ZSB3aGl0ZWxpc3QgKEZVU1dQIC0gRmluYWwgVWx0aW1hdGUgU29sdXRpb24gdG8gdGhlIFdoaXRl
bGlzdGluZyBQcm9ibGVtKSBzb2x1dGlvbiBpbiB0aGUgZmFjZSBvZiBhIHZhcmlldHkgb2YgcHJv
cG9zYWxzLiBETUFSQyBkb2VzIG5vdCBwcmVjbHVkZSB3aGl0ZWxpc3RpbmcgYnkgdGhlIHZhbGlk
YXRpbmcgb3BlcmF0b3IuIEluIGZhY3QsIGl0IHNwZWNpZmljYWxseSBwcm92aWRlcyBmb3IgbG9j
YWwgcG9saWN5IG92ZXJyaWRlcywgaW5jbHVkaW5nIG9uZSBmb3IgbWFpbGluZyBsaXN0cy4gWW91
IHNheSBpdCBpcyBzb21lb25lIGVsc2UncyAodGhlICJETUFSQyBjcm93ZCIgYXMgeW91IHB1dCBp
dCkgcHJvYmxlbS4gSXQncyBraW5kIG9mIGxpa2UgdGhlIG9sZCBzYXcgYWJvdXQgdHJ1Y2tlcnMg
dGhpbmtpbmcgdGhleSBhcmUgaW4gdGhlIHRydWNraW5nIGJ1c2luZXNzIHJhdGhlciB0aGFuIHRo
ZSB0cmFuc3BvcnRhdGlvbiBidXNpbmVzcy4gV2UgYXJlIEFMTCBpbiB0aGUgZW1haWwgc3BhY2Uu
DQoNCllvdXIgc29sdXRpb24gdG8gbWFpbGJveCBwcm92aWRlcnMgd2l0aCB1c2VycyB0aGF0IGlt
cGxlbWVudCBwPXJlamVjdCBpcyB0byBib290IHRoZSB1c2VycyBvZmYgb2YgbWFpbCBsaXN0cyBh
bmQgdGVsbCB0aGVtIHRvIGdvIGZpbmQgYW5vdGhlciBtYWlsIHByb3ZpZGVyLiBUaGF0IG1heSB3
b3JrIGZvciBzb21lIGxpc3RzIGJ1dCB0aGVyZSB3aWxsIGJlIHNpZ25pZmljYW50IGlzc3VlcyBm
b3Igb3RoZXJzLiBJJ20gbm90IGV2ZW4gZ29pbmcgdG8gZGVsdmUgaW50byB5b3VyIGNvbW1lbnRz
IGFib3V0IGxpc3RzIHNpZ25pbmcgdGhlaXIgbWFpbCB3aGVuIHNlbmRpbmcgYXMgYSBkb21haW4g
b3RoZXIgdGhhbiB0aGVtc2VsdmVzLiBUaGF0IGRpc2N1c3Npb24gaGFzIGJlZW4gaGFkIG11bHRp
cGxlIHRpbWVzIGluIG11bHRpcGxlIGZvcnVtcy4gV2hlbiBwcmVzZW50ZWQgd2l0aCBhIG1haWwg
bGlzdCBzaWduYXR1cmUgb24gYW4gZW1haWwgcHVycG9ydGluZyB0byBiZSBmcm9tIGEgZ2l2ZW4g
ZG9tYWluIGFuZCBhbiBhc3NlcnRpb24gZnJvbSB0aGUgZG9tYWluIGl0c2VsZiB0aGF0IGNvbnN0
cmFpbnMgdXNlIG9mIHRoYXQgZG9tYWluLCBJIGtub3cgd2hpY2ggb25lIEknbSBnb2luZyB0byBn
byB3aXRoIGFzIGEgZ2VuZXJhbCBydWxlLg0KDQpXaGVuIEkgdGhpbmsgb2YgeW91ciBjaHVyY2gg
bWFpbCBsaXN0IGV4YW1wbGUsIHRoZSBmaXJzdCB0aGluZyB0aGF0IGNhbWUgdG8gbWluZCBpcyBX
V0pEPyBUaGUgc2Vjb25kIHRoaW5nIHRoYXQgY2FtZSB0byBtaW5kIGlzIHRoYXQgYW4gb3JnYW5p
emF0aW9uLCB3aGV0aGVyIGEgY2h1cmNoLCBhIHVuaXZlcnNpdHkgb3Igc2ltaWxhciBvcmdhbml6
YXRpb24sIG1pZ2h0IG5vdCBiZSB0b28gYXBwcmVjaWF0aXZlIGlmIHNpZ25pZmljYW50IGRvbm9y
cyBvciB2b2x1bnRlZXJzIHdlcmUgdG9sZCBieSB0aGVpciBtYWlsIGxpc3Qgb3BlcmF0b3IgInRv
IHRha2UgYSBoaWtlIiBiZWNhdXNlIHRoZSBtYWlsIGxpc3Qgb3BlcmF0b3IgaXMgdXBzZXQgYnkg
dGhhdCBwZXJzb25zIG1haWxib3ggcHJvdmlkZXIuIFdoZXRoZXIgeW91IGxpa2UgaXQgb3Igbm90
IGFuZCB3aGV0aGVyIHlvdSBhZG1pdCBpdCBvciBub3QsIGl0IGlzIHlvdXIgcHJvYmxlbSBiZWNh
dXNlIGl0IGlzIGEgY29tbXVuaXR5IHByb2JsZW0uIEFzIEkgaGF2ZSBzdGF0ZWQgYmVmb3JlLCBJ
IGhhdmUgbm90IGFkdm9jYXRlZCB0aGF0IGRvbWFpbnMgd2l0aCB1c2VycyBzaG91bGQgcHVibGlz
aCBhIHA9cmVqZWN0LiBJIGRvIHJlY29nbml6ZSB0aGF0IHRob3NlIGRvbWFpbnMgbWF5IGhhdmUg
YW4gaW50ZXJlc3QgaW4gcHJvdGVjdGluZyB0aGVpciBkb21haW5zIGZyb20gYWJ1c2UgYW5kIHNl
ZSBETUFSQyBpcyBhIHBvdGVudGlhbCB0b29sIHRvIG1pdGlnYXRlIGRpcmVjdCBkb21haW4gYWJ1
c2UuIEkgc2F5IHRoaXMgd2l0aG91dCBwZXJzb25hbGx5IGFkdm9jYXRpbmcgZm9yIGl0LiBZb3Ug
aGF2ZSBzdHVkaW91c2x5IGF2b2lkZWQgb25lIG9mIHRoZSBrZXkgdW5kZXJseWluZyBxdWVzdGlv
bnMgZm9yIHRoaXMgZGlzY3Vzc2lvbiBhbmQgb3RoZXJzOiBEb2VzIHRoZSBvd25lciBvZiBhIGRv
bWFpbiBoYXZlIHRoZSByaWdodCB0byBjb250cm9sIG9yIGxpbWl0IHRoZSB1c2Ugb2YgaXRzIGRv
bWFpbiAob3Igb3RoZXIgc2ltaWxhciByZXNvdXJjZXMpPyBJZiBub3QsIHdoaWNoIDNyZCBwYXJ0
eSBnZXRzIHRvIGJlIHRoZSBkZWNpZGVyPyBBcmUgdGhlcmUgYW55IGxpbWl0cyBvbiB0aGUgM3Jk
IHBhcnR5IGRlY2lkZXI/IElmIHNvLCB3aG8gZ2V0cyB0byBzZXQgdGhlIGxpbWl0cyBvbiB0aGUg
M3JkIHBhcnR5IGRlY2lkZXI/IEJlIGNhcmVmdWwsIGl0J3MgYSBzbGlwcGVyeSBzbG9wZS4NCg0K
PiBVbmZvcnR1bmF0ZWx5LCB3ZSd2ZSBzZWVuIG5vIHdpbGxpbmduZXNzIHRvIHNwZW5kIHRoZWly
IG1vbmV5IHRvIGhlbHAgdXMNCj4gc29sdmUgdGhlaXIgcHJvYmxlbSwgYW5kIGZhciB0b28gbXVj
aCBvZiBkbyBpdCBvdXIgd2F5IG9yIGVsc2UsIGJlY2F1c2Ugd2UNCj4gYXJlIGJpZ2dlciB0aGFu
IHlvdSBhcmUuDQo+IA0KDQpMb29rIGF0IGhvdyB5b3UgcGhyYXNlZCB0aGUgYWJvdmUuIFRoYXQg
dHJhbnNsYXRlcyBpbnRvIGdpdmUgdXMgbW9uZXkgb3Igd2Ugd29uJ3QgbWFrZSBhbnkgZWZmb3J0
IHdoYXRzb2V2ZXIuIElzIGl0IHJlYWxseSBhYm91dCBtb25leT8gSSB0cnVseSBkb24ndCB0aGlu
ayBzby4gUGxlYXNlIHByb3ZpZGUgYXMgYSByZWZlcmVuY2UgeW91ciBJRCBmb3IgdGhpcyBwcm9w
b3NlZCB3aGl0ZWxpc3Rpbmcgc3RhbmRhcmQgaW4gZGF0YXRyYWNrZXIuIEFic2VudCBzcGVjaWZp
YyBkZXRhaWxlZCBwcm9wb3NhbHMgdGhhdCB3b3VsZCBpbmR1Y2Ugc29tZW9uZSB0byBzcG9uc29y
IHlvdXIgZWZmb3J0IHdoeSB3b3VsZCBhbnlvbmUgZ2l2ZSB5b3UgbW9uZXkgZm9yIHRoaXMgd2hp
dGVsaXN0aW5nIGVxdWl2YWxlbnQgb2YgRlVTU1A/IEdvb2QgbWFpbGVycyBnbyBiYWQuIEV2ZXJ5
IG9uY2UgaW4gYSB3aGlsZSBiYWQgbWFpbGVycyBnbyBnb29kLiBJJ20gcXVpdGUgZmFtaWxpYXIg
d2l0aCB3aGl0ZWxpc3Rpbmcgc2NoZW1lcyBhbmQgbXkgcGVyc29uYWwgcG9zaXRpb24gaXMgIldo
YXQgaGF2ZSB5b3UgZG9uZSB0byBtZSB0b2RheT8iLiBJIGRvbid0IGNhcmUgd2hhdCB5b3VyIHJl
cHV0YXRpb24gaGFzIGJlZW4gZm9yIHRoZSBsYXN0IHggeWVhcnMgaWYgeW91IGFyZSBlbWl0dGlu
ZyBiYWRuZXNzIHRvZGF5LiBZb3Ugb3BlbmVkIHlvdXIgZW1haWwgc3RhdGluZyB0aGF0ICJJdCBz
YWRkZW5zIG1lIHRoYXQgTWlrZSwgd2hvIEkgdXNlZCB0byBjb25zaWRlciBhIGZyaWVuZCwgd291
bGQgZG8gc28uIiBZb3Ugb2J2aW91c2x5IGRvbid0IHdoaXRlbGlzdCBwZW9wbGUgc28gd2h5IHdv
dWxkIHlvdSBleHBlY3QgcGVvcGxlIHRvIGFjY2VwdCB5b3VyIGFzc2VydGlvbiB0aGF0IHlvdSAo
eW91ciBtYWlsbGlzdCkgc2hvdWxkIGJlIHdoaXRlbGlzdGVkPyBJIGFtIG9mIGNvdXJzZSBkaXNh
cHBvaW50ZWQgdGhhdCB5b3Ugbm8gbG9uZ2VyIGNvbnNpZGVyIG1lIGEgZnJpZW5kLCBidXQgaWYg
Ymx1bnQgZGlzY291cnNlIG9uIGEgZGlmZmljdWx0IHN1YmplY3QgcmVxdWlyZXMgeW91IHRvIGRv
IHNvIHRoZW4gSSBhY2NlcHQgdGhhdC4gUmVhZGVycyBvZiB0aGlzIGV4Y2hhbmdlIGNhbiBkZWNp
ZGUgZm9yIHRoZW1zZWx2ZXMgd2hldGhlciwgYXMgeW91IGhhdmUgYXNzZXJ0ZWQsIEkgaGF2ZSBt
YWxpY2lvdXNseSBsaWVkIGFib3V0IHlvdS4gVGhlIGFyY2hpdmVzIGZyb20gSUVURi1ES0lNIGFy
ZSBhdmFpbGFibGUgYXMgYXJlIHRoZSBvbmVzIGZvciBJRVRGLURNQVJDIGFuZCBETUFSQy1ESVND
VVNTLiBJIHdvdWxkIGFsc28gcG9pbnQgcGVvcGxlIHRvIHRoZSBhcmNoaXZlcyBmb3IgQVNSRyBh
cyB3ZWxsIGZvciBhIGxpdGFueSBvZiBvdXQtb2YtaGFuZCByZWplY3Rpb24gKGFsdGhvdWdoIEkg
d2lsbGluZ2x5IGFkbWl0IHRoYXQgbWFueSBvZiB0aGUgcHJvcG9zYWxzIGZyb20gbmV3bHkgc3Vi
c2NyaWJlZCBwYXJ0aWNpcGFudHMgZGlkIGxhY2sgYSBjZXJ0YWluIHVuZGVyc3RhbmRpbmcgb2Yg
dGhlIHByb2JsZW0gc3BhY2UpLg0KDQpZb3UgbWF5IG5vdCBsaWtlIG15IGNoYXJhY3Rlcml6YXRp
b24gb2YgeW91ciBwb3NpdGlvbiBidXQgeW91ciBwb3NpdGlvbiBoYXMgY29uc2lzdGVudGx5IC0g
b3ZlciBxdWl0ZSBhIGZldyB5ZWFycyAtIGJlZW4gdGhhdCBNTE1zIGFyZSBmaW5lLCBub3cgZ28g
YXdheSBiZWNhdXNlIGl0IGlzICJ5b3VyIiBwcm9ibGVtLCBub3QgbWluZS4gVGhhdCBpcyB0aGUg
ZXNzZW5jZSBvZiB5b3VyIHBvc3QgSSdtIGN1cnJlbnRseSByZXNwb25kaW5nIHRvLiAgSXQncyBu
b3QgYSBmdW5jdGlvbiBvZiAidGhlbSIgYmVpbmcgYmlnZ2VyIHRoYW4geW91LiBJdCdzIGEgZnVu
Y3Rpb24gb2YgeW91IG5vdCBiZWluZyB3aWxsaW5nIHRvIGhhdmUgYW55IHNvcnQgb2YgbWVhbmlu
Z2Z1bCBlbmdhZ2VtZW50IHdpdGggInRoZW0iIG90aGVyIHRoYW4gb24gdGVybXMgeW91IGRpY3Rh
dGUuIEl0J3Mgbm90IGp1c3QgbGFyZ2UgZG9tYWluIG93bmVycyBhbmQgY29ycG9yYXRpb25zIHN0
cnVnZ2xpbmcgd2l0aCBhYnVzZS4gSXQncyBkb21haW4gb3duZXJzIG9mIGFsbCBzaXplcyBhbmQg
dHlwZXMuIEFuZCB5ZXMsIGl0J3MgaW5kaXZpZHVhbHMgdGhhdCBzdWZmZXIgdGhlIGNvbnNlcXVl
bmNlcyBvZiBvdXIgY29sbGVjdGl2ZSBmYWlsdXJlIHRvIGZpbmQgc29sdXRpb25zIHRvIHJlYWwg
d29ybGQgYWJ1c2UuIEkgYWdhaW4gcmVpdGVyYXRlIHRoYXQgSSBhbSBub3QgcGVyc29uYWxseSBh
ZHZvY2F0aW5nIHRoYXQgZG9tYWlucyB3aXRoIHVzZXJzIHB1Ymxpc2ggcD1yZWplY3QgcmVnYXJk
bGVzcyBvZiBpbXBhY3Qgb24gb3RoZXJzLiBJIHdpbGwgc2F5IHRoYXQgdGhlIHRyYWluIGhhcyBs
ZWZ0IHRoZSBzdGF0aW9uIGFuZCBJIGV4cGVjdCB0aGVyZSB3aWxsIGJlIG90aGVyIGRvbWFpbnMg
d2hpY2gsIGluIHRoZSBmYWNlIG9mIHNpZ25pZmljYW50IGFidXNlLCB3aWxsIG1ha2Ugc2ltaWxh
ciBkZWNpc2lvbnMuIEFic2VudCBhbHRlcm5hdGl2ZXMgYW5kIHNlZWluZyB0aGF0IHNpbWlsYXIg
ZG9tYWlucyBjbGFpbSB0aGF0IHRoZSBhcHByb2FjaCBoYXMgcHJvdmlkZWQgcmVsaWVmIGZvciB0
aGVtLCB0aGlzIHdvdWxkIGFwcGVhciB0byBiZSBhIGxvZ2ljYWwgY2hvaWNlIGFuZCBub3QgYW4g
aXJyYXRpb25hbCBvbmUuDQoNCldpdGggZWFjaCBhZGRpdGlvbmFsIGRvbWFpbiB0aGF0IG1ha2Vz
IHN1Y2ggYSBkZWNpc2lvbiB5b3VyIHBvc2l0aW9uIGJlY29tZXMgaW5jcmVhc2luZ2x5IHVudGVu
YWJsZS4gWW91IChhbmQgb3RoZXJzKSBtaWdodCBiZSB3aWxsaW5nIHRvIGtpY2sgb2ZmIGxpc3Qg
cGFydGljaXBhbnRzIGZyb20gc3VjaCBkb21haW5zIGlmIGl0IHJlcHJlc2VudHMgc29tZSBzbWFs
bCBwZXJjZW50YWdlIG9mIHBhcnRpY2lwYW50cyBidXQgaG93IG1hbnkgbGlzdCBvcGVyYXRvcnMg
d2lsbCBkbyBzbyBpZiBzdWNoIHBhcnRpY2lwYW50cyByZXByZXNlbnQgYSBzaWduaWZpY2FudCBw
b3J0aW9uIG9yIG1ham9yaXR5IG9mIHBhcnRpY2lwYW50cz8gV2lsbCB0aGUgb3JnYW5pemF0aW9u
cyB0aGF0IHRoZXNlIGxpc3RzIGFyZSBtYW5hZ2VkIGZvciBhY2NlcHQgc3VjaCBvdXRjb21lcz8g
U29tZSB3aWxsIGJ1dCBtYW55IHdvbid0LiBUaGV5IHdpbGwgc3dpdGNoIHRvIGltcGxlbWVudGVy
cyB0aGF0IGFsbG93IHRoZW0gdG8gZ28gYWJvdXQgdGhlaXIgZGFpbHkgYWN0aXZpdGllcyB3aXRo
b3V0IGl0IGJlaW5nIG1hZGUgcGFpbmZ1bCBmb3IgdGhlbS4gSWYgYSBtYWlsaW5nIGxpc3QgaXMg
Y29uZmlndXJlZCBhbmQgbm9ib2R5IGlzIHN1YnNjcmliZWQgb3IgcGFydGljaXBhdGVzIGlzIGl0
IGEgbWFpbGluZyBsaXN0PyBZb3UgcHJvcG9zZSBwYWluIGFzIGEgbW90aXZhdG9yIGJ1dCB5b3Ug
ZG9uJ3Qgc2VlbSB0byByZWNvZ25pemUgdGhhdCBzdWNoIHBhaW4gbWF5IG1vdGl2YXRlIHBlb3Bs
ZSBhbmQgb3JnYW5pemF0aW9ucyB0byBvdXRjb21lcyBvdGhlciB0aGFuIHRoYXQgd2hpY2ggeW91
IGRlc2lyZS4NCg0KSSByZWNvZ25pemUgdGhhdCB0aGlzIGlzIGEgYml0dGVyIGRpc2N1c3Npb24g
Zm9yIHNvbWUuIEl0IGNvdWxkIGhhdmUgYW5kIHNob3VsZCBoYXZlIGJlZW4gYSBkaXNjdXNzaW9u
IGhlbGQgbXVjaCBlYXJsaWVyIGFuZCBpbiBhIGRpZmZlcmVudCBjb250ZXh0LiBUaGF0IGlzIHdh
dGVyIHVuZGVyIHRoZSBicmlkZ2UuIEFzIG90aGVycyBoYXZlIGFza2VkLCB3aGVyZSBzaG91bGQg
dGhlIElFVEYgYW5kIHRoZSBsYXJnZXIgY29tbXVuaXR5IGdvIGZyb20gaGVyZT8gUHVuaXNoaW5n
IHVzZXJzIGFzIGEgbWVhbnMgb2YgZ2V0dGluZyBhdCBhIG1haWxib3ggcHJvdmlkZXIgZG9lc24n
dCBzZWVtIHBhcnRpY3VsYXJseSBjb25zdHJ1Y3RpdmUgaW4gdGhlIGxvbmcgcnVuIGFuZCBhcyBJ
IGhhdmUgaW5kaWNhdGVkIGFib3ZlIG1heSBiZSBzb21ld2hhdCBzZWxmLWRlZmVhdGluZy4gSUVU
RiBzaHVubmluZyBvZiBETUFSQyBtYXkgZmVlbCBnb29kIGJ1dCBldmVuIEpvaG4gTGV2aW5lIGhh
cyBzdGF0ZWQgdGhhdCBpdCBoYXMgYmVuZWZpdHMgaW4gcGFydGljdWxhciBpbXBsZW1lbnRhdGlv
biBjYXRlZ29yaWVzIChhcyBsb25nIGFzIG5vIGNoYW5nZSBpcyBhc2tlZCBvZiBNTE1zKS4gQSBk
aXNjdXNzaW9uIG9mIHRlY2huaWNhbCBhcHByb2FjaGVzIHRoYXQgZW5hYmxlIG1haWwgbGlzdHMg
dG8gcGFydGljaXBhdGUgaW4gYXV0aGVudGljYXRpb24gYXBwcm9hY2hlcyBmb3IgM3JkIHBhcnR5
IGRvbWFpbnMgd2l0aG91dCBsb3NpbmcgKHNpZ25pZmljYW50KSBmdW5jdGlvbmFsaXR5IG1pZ2h0
IGJlIHVzZWZ1bC4gQXJlIHRoZXJlIGFsdGVybmF0aXZlIHdheXMgb2YgcHJvdmlkaW5nIHRoYXQg
c2FtZSBmdW5jdGlvbmFsaXR5PyBOb3RlIHRoYXQgSSdtIG5vdCBldmVuIGJlaW5nIERNQVJDIHNw
ZWNpZmljIGluIHByb3Bvc2luZyB0aGF0LiBKb2huIExldmluZSBoYXMgcHJvcG9zZWQgd2hpdGVs
aXN0aW5nIGFzIGEgc29sdXRpb24uIEkgZG9uJ3QgYnV5IGludG8gdGhhdCBwZXJzb25hbGx5IGJ1
dCBpdCBtaWdodCBiZSBhIHVzZWZ1bCBkaXNjdXNzaW9uIHRvIGhhdmUgLSBtb25ldGFyeSBkb25h
dGlvbnMgc2hvdWxkIG5vdCBiZSByZXF1aXJlZCBpbiBvcmRlciB0byBoYXZlIGEgZGlzY3Vzc2lv
biBhYm91dCB0aGlzLg0KDQpBcG9sb2dpZXMgdG8gYWxsIGZvciB0aGlzIGxvbmcgbWlzc2l2ZS4N
Cg0KTWlrZQ0KDQo=


From nobody Mon Apr 14 18:36:32 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 432BC1A02CA for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 qL91pQFD9tbL for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:36:27 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id AEDE21A06B1 for <ietf@ietf.org>; Mon, 14 Apr 2014 18:36:24 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kq14so8962843pab.38 for <ietf@ietf.org>; Mon, 14 Apr 2014 18:36:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=m6UTOxF1ro9fFzkbg1NK0TNunu77C1VCv+8sv/WqJxU=; b=n88IjAnnBzYM8pnwTJ977lL5UrTGbphSVw7lo9YczCryLCTU82kIOH9JroCmyHlOzT hrSoQ2sfD0LWbu/hOa5T3+N94ngxO7ciukAkprdSMmebmSLkKWWpjZgyfQzOQkXdXTJZ xuCuiKOQPyPSVWS3pBvW7rornK+HUU8NFYy3P4ssO7TebaxzJFd0N97wK7UWRvq62Yv4 Ne/SE2PlFKNLrTXkBJnDTSwk0oX3PF3D46ZDLDhpoF23cp0m4F3kyK3N1JAWG3D9jM4G REWhDggiUH71c3X9pSwpllGVsRZPxWb4iR4w4udttYWXZzrlWDoYKtkmbQg3kE+KBa9t nUyQ==
X-Received: by 10.68.203.135 with SMTP id kq7mr47459702pbc.85.1397525782200; Mon, 14 Apr 2014 18:36:22 -0700 (PDT)
Received: from [192.168.178.20] (172.200.69.111.dynamic.snap.net.nz. [111.69.200.172]) by mx.google.com with ESMTPSA id qc8sm36554498pbc.68.2014.04.14.18.36.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Apr 2014 18:36:21 -0700 (PDT)
Message-ID: <534C8D14.1010605@gmail.com>
Date: Tue, 15 Apr 2014 13:36:20 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
References: <20140414220233.32201.qmail@joyce.lan>
In-Reply-To: <20140414220233.32201.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GdE1NuTZICrcgop8O6S38nZUl9s
Cc: tytso@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 01:36:28 -0000

On 15/04/2014 10:02, John Levine wrote:
>> to something like:
>>
>> From: Brian E Carpenter <brian.e.carpenter@yahoo.com.INVALID>
> 
> That's what I do on my lists.  It was pretty easy to add in the shim
> that adds the outgoing DKIM signature, and is the least painful thing
> I could think of for my mostly non-technical users.

It's also much better than destroying everybody's From field, which rather
defeats the purpose of a mailing list to my mind. OK, Mailman 2.1.16
doesn't actually solve the problem in a useful way. Thanks.

   Brian

> 
>> (or maybe instead of yahoo.com.INVALID, it should be "yahoo.com.BREAKS.MAILING.LISTS"
> 
> Now, now, there's no LISTS TLD.  Yet.
> 
> R's,
> John
> 
> 


From nobody Mon Apr 14 18:45:22 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58C161A06D0 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:45:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 Waote6sdAECw for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:45:19 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id BA9AB1A06CE for <ietf@ietf.org>; Mon, 14 Apr 2014 18:45:19 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id md12so8851634pbc.21 for <ietf@ietf.org>; Mon, 14 Apr 2014 18:45:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Wi3SzLfi3IYFV4OW6LFRL3TxynKxmOMMeTJUNm1dItg=; b=sSVTYD6hFwG2MyP0YAx+LRjbTCZEYHZQVWjB/bJwxychnCyX4m6lSE2FP+B4VcKZYF 3YQfheOzsRDSwa5KgioG4kW6USofiujFDB1HA2Rt5LY1+NQC3RUYOfsx2Ui3EvUKvU/V A7teqFgRdWvBCP6KFu/8HUQorwYzF4gTSZzEpTcEQ1vCAYk0Ds3jPgu7R7X8qqVUp3Xb p41jKMWLHYGiy+QIClN0uqagLAUoufhBk8Ezog6nnFES+6vDhUtE28xZLj8xdJheym3O Cy2H5x7qUH3RjWXZQhTPxmZYgPh1IKIwtNoFkwtA7IFJw6b8/OuMJyjGdi9+A2hlRzwk an8A==
X-Received: by 10.68.202.230 with SMTP id kl6mr47804127pbc.55.1397526317153; Mon, 14 Apr 2014 18:45:17 -0700 (PDT)
Received: from [192.168.178.20] (172.200.69.111.dynamic.snap.net.nz. [111.69.200.172]) by mx.google.com with ESMTPSA id y4sm36574110pbk.76.2014.04.14.18.45.15 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 14 Apr 2014 18:45:16 -0700 (PDT)
Message-ID: <534C8F2B.9060903@gmail.com>
Date: Tue, 15 Apr 2014 13:45:15 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com>
In-Reply-To: <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7kn-hvl54DL95n8hD635_7eWvcY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 01:45:21 -0000

I thought that standard operating procedure in the IT industry
was: if you roll something out and it causes serious breakage to
some of your users, you roll it back as soon as possible.

Why hasn't Yahoo rolled back its 'reject' policy by now?

Regards
   Brian


From nobody Mon Apr 14 18:52:28 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEDD31A02D7; Mon, 14 Apr 2014 18:52:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 abRVuM3otsI8; Mon, 14 Apr 2014 18:52:20 -0700 (PDT)
Received: from mail-yk0-x22f.google.com (mail-yk0-x22f.google.com [IPv6:2607:f8b0:4002:c07::22f]) by ietfa.amsl.com (Postfix) with ESMTP id ABB331A024D; Mon, 14 Apr 2014 18:52:19 -0700 (PDT)
Received: by mail-yk0-f175.google.com with SMTP id 131so8220273ykp.20 for <multiple recipients>; Mon, 14 Apr 2014 18:52:16 -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:content-type; bh=0Ws4wOSz9/vv4WbM2NaYt5wmlA5s/4GShtawocdAiW8=; b=HfFNI+3pF6yvzqNr2zSadaSAnwWN1da88lpxC5SYns2Rs2ytqeRm4p8NE0nOaslUSm AvgkkZPsFJFFGXW81zH09xA5ahZWlWp18D8GAJILk2j36py04mM0zIJrBL0/dHmykP05 J59rQhhZf6VRIxy9z1MOWU0uBIo/b04GWlyoup7JZY6Z6H3W2qJvI46U72wSv3N4HNfw Mic8Gvm4Czim8PDr5ZDyFDRlSP0UE7KoDTybi8DHiMHCuzRNkmaOQHnTkIIwzbB6iQXm mw/Dsa94Qhdju0u4WxScLv1I3dGDzX0P6uaU+/u6HkzFB+8CfFpe74sry+sv1wnzcNzm 4IvQ==
MIME-Version: 1.0
X-Received: by 10.236.134.71 with SMTP id r47mr18239694yhi.83.1397526736850; Mon, 14 Apr 2014 18:52:16 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Mon, 14 Apr 2014 18:52:16 -0700 (PDT)
In-Reply-To: <CADnDZ8-tg52c9FDZgHxgpSJjqPQvqAOg1hSR8usoRx-739msrA@mail.gmail.com>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <CADnDZ8-tg52c9FDZgHxgpSJjqPQvqAOg1hSR8usoRx-739msrA@mail.gmail.com>
Date: Tue, 15 Apr 2014 02:52:16 +0100
Message-ID: <CADnDZ88kDVKg6hYfYXtmYezARUCZW12ZEBXJ4n=tbM67YUKv2A@mail.gmail.com>
Subject: RE: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: IAOC IAOC <iaoc@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec5468c51b6d4c204f70b0cb6
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jZAuE7tFs5gE6Y3GEG6UGQpDQXI
Cc: "iab@iab.org" <iab@iab.org>, "iesg@ietf.org" <iesg@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 01:52:23 -0000

--bcaec5468c51b6d4c204f70b0cb6
Content-Type: text/plain; charset=UTF-8

Comment Date: 15.04.2014

Subject Issue: IETF trademarks and future plans/decisions.
Comment Author: Abdussalam Baryun (AB).
Your request for comments was dated 04.04.2014
The end date of comment period 05.05.2014

Dear Trustees,

I thank you for your request, and would like to see more feedback requests
in the future on this list for at least once per year. IMO the trust
agreement may need some changes in future to involve more
organised feedback but organised by IETF general area participants. It will
be better to involve IETF WGs when requests related to IETF future image. I
am not sure if there is a RFC for that openness and involvement but it will
be good to have in similar request issues.

My feedbacks/comments or opinions/suggestions on the issue are:

0) IMHO the secretariatsIETF is a service mark not a trademark. But IETF is
the registered trademark. Any trademark and organisation logo has its
markets, so hopefully we know our markets.
1) that we IETF need to protect and use our trademarks, and not sure how we
were using the secretariats trademark. If used we should have made some
money from it. You did not report about past benefits from that trademark
within your request. Also what kind of markets was that trademark
targeting.
2) the IETF trademark should be used in  favour of IETF to cover
its protect expenses. Is there plans for this? I need to know also if there
are future plans. I suggest you make plans available to community because
our feedback needs to stand on some ground otherwise you are asking someone
with no market-history knowledge. I would like to know information of the
markets for all IETF marks if available, then my feedback will be better
useful.
3) I don't know who is the current IETF secretariats (it may be because I
think that knowledge will not benefit me). I don't think there is/were a
market plan for that trademark. The IETF web page does not announce
the secretariats name, which can be a form of protection. However, IETF ADs
and IETF chair are well known, so I suggest announcing the name of the
secretariats.
4) many companies use IETF meetings and participate/host but is there
integrated projects among companies using IETF trademark, so that the IETF
general area can establish. Is that situation I think the secretariats
trademark can be helpful. So I hope you define (defined conditions or
situations or markets) when we need or don't need that secretariats
trademark, also that you have a plan when to bring it back registered if
your defined conditions apply.
5) IETF trademark is not really with good standards of trademarks (if we
evaluate it properly). If I compare with IEEE then I may think that whom
responsible are not marketing/planning for IETF marks/logos.

Thanks for your message, wishing you all the best.

Best Regards
AB



> On 4/4/14, IETF Administrative Director <iad@ietf.org> wrote:
> > All;
> >
> > The Trustees of the IETF Trust have voted an intent to renounce (abandon)
> > the "IETF Secretariat"
> > trademark, but before taking any action they desire to hear from the
> > community.
>
>
>
>

--bcaec5468c51b6d4c204f70b0cb6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div>Comment Date: 15.04.2014<br></div><div><br></div><div>Subject=C2=A0Iss=
ue: IETF trademarks and future plans/decisions.=C2=A0</div><div>Comment=C2=
=A0Author:=C2=A0Abdussalam Baryun (AB).=C2=A0</div><div>Your request for co=
mments was=C2=A0dated 04.04.2014</div>
<div>The end date of comment period 05.05.2014</div><div><br></div><div>Dea=
r Trustees,</div><div><br></div><div>I thank you for your request, and woul=
d like to see more feedback=C2=A0requests in the=C2=A0future on this list=
=C2=A0for at least once per year. IMO the=C2=A0trust agreement may need som=
e changes in future to involve more organised=C2=A0feedback but organised b=
y IETF general area participants. It will be better to involve IETF=C2=A0WG=
s when requests=C2=A0related to IETF future image. I am not sure if there i=
s a RFC for that openness and involvement=C2=A0but it will be good to have =
in similar request issues.=C2=A0</div>


<div><br></div><div>My feedbacks/comments=C2=A0or opinions/suggestions<span=
></span> on the issue=C2=A0are:</div><div><br></div><div>0) IMHO=C2=A0the s=
ecretariats<span></span>IETF is a service mark not a trademark. But IETF is=
 the registered=C2=A0trademark. Any trademark=C2=A0and=C2=A0organisation lo=
go has its markets, so hopefully we know our markets.=C2=A0</div>


<div>1)=C2=A0that we IETF=C2=A0need to protect and use our=C2=A0trademarks,=
 and not sure how we were using the secretariats trademark. If used we shou=
ld have made some money from it. You did not report about past benefits fro=
m that trademark within your request. Also what kind of markets was that tr=
ademark targeting.=C2=A0</div>



<div>2) the IETF trademark should be used in =C2=A0favour of IETF to cover =
its=C2=A0protect=C2=A0expenses. Is there plans for this?=C2=A0I need to kno=
w also if there are future plans. I suggest you make plans available to com=
munity because our feedback needs to stand on some ground otherwise you are=
 asking someone with no market-history knowledge. I would like to know info=
rmation of=C2=A0the markets for all IETF marks if available, then my feedba=
ck will be better useful.=C2=A0</div>
<div>3) I don&#39;t know who is the current IETF secretariats (it may be be=
cause I think=C2=A0that knowledge=C2=A0will not=C2=A0benefit me). I don&#39=
;t think there is/were=C2=A0a market plan for that trademark.=C2=A0The IETF=
 web page=C2=A0does not announce the=C2=A0secretariats=C2=A0name, which can=
 be a=C2=A0form of protection. However,=C2=A0IETF=C2=A0ADs and IETF chair a=
re well=C2=A0known, so I suggest announcing the name of the secretariats.=
=C2=A0</div>





<div>4) many companies use IETF meetings and participate/host but is there =
integrated=C2=A0projects among companies using IETF trademark,=C2=A0so=C2=
=A0that the IETF general area can establish. Is that situation I think the =
secretariats trademark can be helpful. So I hope you define (defined condit=
ions or situations or markets)=C2=A0when we need or don&#39;t need that sec=
retariats trademark, also that you have a plan when to bring it back regist=
ered if your defined conditions apply.=C2=A0</div>
<div>5) IETF trademark is not really with good standards of trademarks (if =
we evaluate it properly). If=C2=A0I compare with IEEE then I may think that=
 whom responsible=C2=A0are not marketing/planning=C2=A0for=C2=A0IETF marks/=
logos.=C2=A0<span></span></div>
<div><br></div><div>Thanks for your message, wishing you all the best.=C2=
=A0</div>

<div><br></div><div>Best Regards</div><div>AB</div><div><br></div><br><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">
<br>
On 4/4/14, IETF Administrative Director &lt;<a>iad@ietf.org</a>&gt; wrote:<=
br>
&gt; All;<br>
&gt;<br>
&gt; The Trustees of the IETF Trust have voted an intent to renounce (aband=
on)<br>
&gt; the &quot;IETF Secretariat&quot;<br>
&gt; trademark, but before taking any action they desire to hear from the<b=
r>
&gt; community.<br>
<br><br><br>
</blockquote>

--bcaec5468c51b6d4c204f70b0cb6--


From nobody Mon Apr 14 19:00:07 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BAD61A0473 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 19:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.343
X-Spam-Level: **
X-Spam-Status: No, score=2.343 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 8Vj5EZgFg8Mf for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 18:59:57 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 26E8B1A0259 for <ietf@ietf.org>; Mon, 14 Apr 2014 18:59:57 -0700 (PDT)
Received: (qmail 96004 invoked from network); 15 Apr 2014 01:59:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=17702.534c929a.k1404; bh=r79xaPiwERF8C0XIqxzYmRPi1vULpctjRJ4A091bpIA=; b=CQJ0WqLKZXEr7MKerVAGq4A2b672K8nf+ik6eYaW/ztf//rgUyx9gR/4iWdp3XWDjP89BNu1vyU87d5hSzy0J2lVv9m87TilTUlz34JVmfHfiO2AObN1eiXhcibHD12Exp5uAlb9QWSPnW7ArG//3b8XsKNFzusmgSNaZbWH67f0Qmdn9za9RA+17WSxP8/OmIDIwHAgG7dGMl8eer9Ohxmv6cZyberGx+OD92uVDueQszXNjAygJGwwuDwO/F7t
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=17702.534c929a.k1404; bh=r79xaPiwERF8C0XIqxzYmRPi1vULpctjRJ4A091bpIA=; b=31d8u7q+QXOkcDli7L7T7UJNfy5sV2k7FWuKliBZLxVwxsUxQ/x0uYJbJ+KKj96m3g+pAsxIAF+PhLPsrEp1d2tj08evS73MHYPqG9kzaqfznNVDPyA5z41Z/5FCinLas6S2asYGugf8RASLOSX0xeLGKRYkoIq5GUID6JKPXPFum/FW/0bPPGKE7WSc09EwhBMIEENxWGXETzJMRU5Ddz2hL3VDGfCQk5tFLtpf2oEaopHgFqbSsDjr9aRBiCSF
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 15 Apr 2014 01:59:54 -0000
Date: 14 Apr 2014 21:59:53 -0400
Message-ID: <alpine.BSF.2.00.1404142150430.32657@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "MH Michael Hammer (5304)" <MHammer@ag.com>
Subject: RE: protecting the Internet from DMARC damage, was perspectives
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/R87r_Ysx6trrR81kd9iRUsoVmOE
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 02:00:01 -0000

> You are absolutely correct in stating that DMARC doesn't address mailing 
> lists - because you have staked out a position that mailing lists should 
> not have to change in any way shape or form to deal with any 
> authentication model. That is extremely constraining out of the gate and 
> pretty much ends any meaningful discussion at that point. "How about if 
> we... NO!"

The sentence always ends "... spend our own time and money to break or 
remove features our users expect and like to solve your problems", so of 
course the answer is no.

I've never said that lists won't change, I've said that we're not going to 
screw them up to work around your FUSSP.

If you ever made a reasonable offer, I would be happy to talk about it.
But you haven't.

If the DMARC gorillas hired someone (Returnpath? Spamhaus?) to build a 
mailing list whitelist, the goodwill would be enormous and the cost, 
spread among the DMARC group, would be nominal.  But spending your own 
money to solve your own propblems somehow isn't on the table.  We're 
supposed to spend ours, instead.  Are you really surprised this is not 
making you any friends?

R's,
John


From nobody Mon Apr 14 19:14:19 2014
Return-Path: <olejacobsen@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 950751A02F0; Mon, 14 Apr 2014 19:14:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 ihTZyM2Um6-u; Mon, 14 Apr 2014 19:14:02 -0700 (PDT)
Received: from st11p00mm-asmtp002.mac.com (st11p00mm-asmtp002.mac.com [17.172.81.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE9001A02E5; Mon, 14 Apr 2014 19:14:01 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Received: from 173-11-110-132-sfba.hfc.comcastbusiness.net (173-11-110-132-SFBA.hfc.comcastbusiness.net [173.11.110.132]) by st11p00mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N4100D6EVJ87550@st11p00mm-asmtp002.mac.com>; Tue, 15 Apr 2014 02:13:59 +0000 (GMT)
Date: Mon, 14 Apr 2014 19:13:56 -0700 (PDT)
From: Ole Jacobsen <olejacobsen@me.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: RE: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
In-reply-to: <CADnDZ88kDVKg6hYfYXtmYezARUCZW12ZEBXJ4n=tbM67YUKv2A@mail.gmail.com>
Message-id: <alpine.OSX.2.01.1404141912380.99918@rabdullah.local>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <CADnDZ8-tg52c9FDZgHxgpSJjqPQvqAOg1hSR8usoRx-739msrA@mail.gmail.com> <CADnDZ88kDVKg6hYfYXtmYezARUCZW12ZEBXJ4n=tbM67YUKv2A@mail.gmail.com>
User-Agent: Alpine 2.01 (OSX 1266 2009-07-14)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaEhEKTEMXGx0EGx0YBBIZBBscEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsbGmJCH2lmGVtNGXhzB xlsGhgbGV0dEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGxwQGx4aHxsRCl5ZF2FNQFt oEQpMRhdia2sRCkNaFxsdGQQbGwQbGxoEGxkYEQpCXhcbEQpEWBcfEQpESRccEQpCRRdjWUJrc 3JMelNyWxEKQk4XbHBgeUAdYlJpGmIRCkJMF2BJWUZ/eWRYHENeEQpCbBdoRFxTTWtCfUcFTBE KQkAXZUYfS29iQkN5c2gRCnBoF2kba0B6fkQaXRsTEQpwaBdmQUVkfmtrQHJeGREKcGgXbBlwc kxdYR5/AVwRCnBoF2hTH3IaUloBQGcbEQpwaBdsZGtLHRxjGWtkRREKcH8Xb11PYRhnGGBpcnw RCnBsF2YBEkd9TWdzSUBJEQ==
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-14_01:2014-04-14,2014-04-14,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=4 spamscore=4 suspectscore=21 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404150037
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Cy25BIJF48Z2AVS2t4RUfPNrFnw
Cc: IAOC IAOC <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "iesg@ietf.org" <iesg@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Ole Jacobsen <olejacobsen@me.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 02:14:07 -0000

AB,

Why do you think this has *anything* to do with "marketing" ???

Trademarks are there to protect brands and owners, so that somebody 
else cannot cause confusion by using the same name/mark/logo.

That's all.

Ole


Ole J. Jacobsen
Editor and Publisher
Home: +1 415-550-9427
Cell: +1 415-370-4628
Japan Docomo: +81 90 3337-9311
UK Orange: +44 7805 977889
E-mail: olejacobsen@me.com
URL: http://organdemo.info
Skype: organdemo



From nobody Mon Apr 14 19:58:36 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 371621A02FF for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 19:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 1jhHIP_jpKZH for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 19:58:31 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 132BD1A02EC for <ietf@ietf.org>; Mon, 14 Apr 2014 19:58:31 -0700 (PDT)
Received: from [192.168.2.23] (unknown [99.17.31.1]) by dougbarton.us (Postfix) with ESMTPSA id 1200022B1A for <ietf@ietf.org>; Tue, 15 Apr 2014 02:58:28 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397530708; bh=IKQJ1o3YnpANT4YIx0yw+5GduvI0Jgcthc5/G0k5WtI=; h=Date:From:To:Subject:References:In-Reply-To; b=QiUckyUS2DZf/FI0o8Nwa1bGi6AEddt1dGJVIlYRh3SV5QzNhwfSXHUAT/wGhou4y YE8rHRUaMOIMa6ZuSHL4hVcyGllrS0DrfZlSXG6WNXU6OrTKeDTwk/620H1h+jEQna MBvnM4EUvqSjp4LvKFvR+PssLXL2YnDQY/ceB1C8=
Message-ID: <534CA053.2090906@dougbarton.us>
Date: Mon, 14 Apr 2014 19:58:27 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534C60E4.8030802@dougbarton.us> <534C7746.4070706@bbiw.net>
In-Reply-To: <534C7746.4070706@bbiw.net>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Hn93AHAkksJB4gJxZC2G1LN_x7A
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 02:58:32 -0000

On 04/14/2014 05:03 PM, Dave Crocker wrote:
> On 4/14/2014 3:27 PM, Doug Barton wrote:
>> What I AM suggesting however, and I realize that this is a hard pill to
>> swallow for many IETF'ers, is that IN THE GRAND SCHEME OF THINGS mailing
>> list traffic is inconsequential to large e-mail providers.
>
>
> That view is popular, but it's quite wrong.
>
> What /is/ true is that mailing list traffic by users of large mailbox
> providers, through small, independent mailing list providers, is
> probably negligible.  That's the category of primary victim of the
> recent change.

Right, which is what we're talking about.

If all my message traffic is on internal only systems (such as the 
social networking you described) then I don't care what my transport 
mechanism is; mail, XMPP, or RFC 1419. It's not going out of my network, 
so I don't even need to use an Internet standard.

So getting back to solving the actual problem at hand ....

Doug


From nobody Mon Apr 14 20:04:22 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00B031A0307 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 BemPD7BlC7bj for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:04:18 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id E1A821A0301 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:04:18 -0700 (PDT)
Received: from [192.168.2.23] (unknown [99.17.31.1]) by dougbarton.us (Postfix) with ESMTPSA id 284E122B1A; Tue, 15 Apr 2014 03:04:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397531056; bh=0c0p4GvePxaVCSXZrvfIQAkWvDsvHbzTTCVBH08LKD4=; h=Date:From:To:Subject:References:In-Reply-To; b=IMi9Y8HELmRhXeQHhZpEbxdkm1TQAv+B+fjazaO9Fyh7kfP2j1Y7916WT6r9FvhfD 8fyi0GSfXBJ9+WlB1E0EI3qdEhXM7KQC1yajmm+At0fe5nEx9sm8Ov9XsSIju3qpl7 oJl51Jq5VPqExLVeIiZYhWVAd7E0ZVErZepV3e74=
Message-ID: <534CA1AF.2040603@dougbarton.us>
Date: Mon, 14 Apr 2014 20:04:15 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com>
In-Reply-To: <534C8F2B.9060903@gmail.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/J2Ry-4CuTqJ7SA4K10-QGPDfYms
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:04:20 -0000

On 04/14/2014 06:45 PM, Brian E Carpenter wrote:
> I thought that standard operating procedure in the IT industry
> was: if you roll something out and it causes serious breakage to
> some of your users, you roll it back as soon as possible.
>
> Why hasn't Yahoo rolled back its 'reject' policy by now?

Simple ... from Yahoo!'s perspective the breakage is negligible, not 
serious. Traditional e-mail traffic to and from traditional e-mail lists 
(like this one) is simply not large enough to lose sleep over. Keep in 
mind, Yahoo! knew what breakage was going to occur before they threw the 
switch, and they threw the switch anyway.

Again, I realize that it's hard for most IETF'ers to conceive of, but in 
this matter we are the ultimate anachronists.

Doug


From nobody Mon Apr 14 20:12:19 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09A951A030C for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 9J1WSte9kpa4 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:12:15 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8B7601A0301 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:12:15 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 95722CC0C1 for <ietf@ietf.org>; Mon, 14 Apr 2014 23:12:12 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id SeIDJJJdxq0J for <ietf@ietf.org>; Mon, 14 Apr 2014 23:12:03 -0400 (EDT)
Received: from Miles-Fidelmans-MacBook-Pro.local (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 9CD0DCC0BC for <ietf@ietf.org>; Mon, 14 Apr 2014 23:12:03 -0400 (EDT)
Message-ID: <534CA383.3090801@meetinghouse.net>
Date: Mon, 14 Apr 2014 23:12:03 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com>
In-Reply-To: <534C8F2B.9060903@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qjnUR8ml6tdKHOpZFoD-eWg234M
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:12:17 -0000

Brian E Carpenter wrote:
> I thought that standard operating procedure in the IT industry
> was: if you roll something out and it causes serious breakage to
> some of your users, you roll it back as soon as possible.
>
> Why hasn't Yahoo rolled back its 'reject' policy by now?
>
>
That really is a great question.

I guess the one that immediately follows is - why has there not been a 
strong call for them to do so?

Miles



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 20:13:30 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFC491A0311 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 c2_T6ao1_Qyj for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:13:27 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 9FC411A0301 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:13:27 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 9CE82CC0C1 for <ietf@ietf.org>; Mon, 14 Apr 2014 23:13:24 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ieB0VLQRqk6r for <ietf@ietf.org>; Mon, 14 Apr 2014 23:13:16 -0400 (EDT)
Received: from Miles-Fidelmans-MacBook-Pro.local (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 0AF98CC0BC for <ietf@ietf.org>; Mon, 14 Apr 2014 23:13:16 -0400 (EDT)
Message-ID: <534CA3CB.7090205@meetinghouse.net>
Date: Mon, 14 Apr 2014 23:13:15 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534CA1AF.2040603@dougbarton.us>
In-Reply-To: <534CA1AF.2040603@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oSyKcC5eeXznbqkNWDxh8Hud4kg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:13:28 -0000

Doug Barton wrote:
> On 04/14/2014 06:45 PM, Brian E Carpenter wrote:
>> I thought that standard operating procedure in the IT industry
>> was: if you roll something out and it causes serious breakage to
>> some of your users, you roll it back as soon as possible.
>>
>> Why hasn't Yahoo rolled back its 'reject' policy by now?
>
> Simple ... from Yahoo!'s perspective the breakage is negligible, not 
> serious. Traditional e-mail traffic to and from traditional e-mail 
> lists (like this one) is simply not large enough to lose sleep over. 
> Keep in mind, Yahoo! knew what breakage was going to occur before they 
> threw the switch, and they threw the switch anyway.
>
> Again, I realize that it's hard for most IETF'ers to conceive of, but 
> in this matter we are the ultimate anachronists.
>
Only by abdication.  That's reversible.



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 20:20:13 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D621A02FC for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:20:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 LTQxZTcV-IpY for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:20:00 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 15CA61A02F6 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:20:00 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id B58DE1B803E for <ietf@ietf.org>; Mon, 14 Apr 2014 20:19:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id A4CB719005C; Mon, 14 Apr 2014 20:19:57 -0700 (PDT)
Received: from [192.168.146.119] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 14 Apr 2014 20:19:51 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com>
Date: Mon, 14 Apr 2014 22:19:49 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <B3B3253C-6389-48B3-82C4-44F837CC0B31@nominum.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com>
To: Dick Franks <rwfranks@acm.org>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/j-N-zEinnzqmX4471VYHD9l4vyU
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:20:01 -0000

On Apr 14, 2014, at 3:24 PM, Dick Franks <rwfranks@acm.org> wrote:
> Robust action in defence of IETF reputation is possibly a precedent =
worth setting.

Robust, wrong action in defense of IETF reputation is a precedent worth =
avoiding.   The quoted statement makes no assertions about IETF policy, =
but simply says the proponents of DMARC would like to publish the spec =
through the IETF.   There is nothing wrong with them saying this.   If =
you think it means the IETF has endorsed the spec, no amount of =
word-smithing or protest is going to help.   More likely it's going to =
be a sound bite on some news program talking about a dispute between =
"those crazy boffins."


From nobody Mon Apr 14 20:23:25 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 489F11A0671 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.527
X-Spam-Level: 
X-Spam-Status: No, score=0.527 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 ejp6mqoJxD2c for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:23:19 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 2E3FC1A0663 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:23:19 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WZtxq-0005VF-BJ; Tue, 15 Apr 2014 03:23:14 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 656F7580287; Mon, 14 Apr 2014 23:23:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397532193; bh=iY/LnGS3VnV3F23wsME6Mmlgs3xc8WCZ3cnnlncCxH8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=C8uASI3UkRNiyJ/s8/pysaOpDGtd+koL7IfJjFqR47BeromW857qXQdtsvl/dTMZJ unKdyUtw/jJw8sDqABblwmyp7ZhG+NbrW7+eyRdjOgKawFO9zL56hGcYBVRjK9Fu/b xEFnKhMtKlWhEUDAznYWwSMHeNxiqbU1eHHCwYBA=
Date: Mon, 14 Apr 2014 23:23:13 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: What I've been wondering about the DMARC problem
Message-ID: <20140415032313.GA3403@thunk.org>
References: <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534CA1AF.2040603@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534CA1AF.2040603@dougbarton.us>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9xy4AhHtuMgZg0EVwsxkJC4ca8A
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:23:24 -0000

On Mon, Apr 14, 2014 at 08:04:15PM -0700, Doug Barton wrote:
> 
> Simple ... from Yahoo!'s perspective the breakage is negligible, not
> serious. Traditional e-mail traffic to and from traditional e-mail lists
> (like this one) is simply not large enough to lose sleep over. Keep in mind,
> Yahoo! knew what breakage was going to occur before they threw the switch,
> and they threw the switch anyway.
> 
> Again, I realize that it's hard for most IETF'ers to conceive of, but in
> this matter we are the ultimate anachronists.

The problem is that e-mail volume really is the wrong way to measure
"breakage".  After all, the vast majority of e-mail may be SPAM, but
that doesn't mean that those e-mail messages are the ones that any
users care about.

I've already had to send out message to my church's vestry (governing
board) explaining that people who are using Yahoo aren't going to be
able to send to the church mailing lists reliably, and that for now,
until I can get around to fixing the mailing list software (hint: not
during Holy Week), that their messages will be held for moderation
until someone can manually cut and paste it and send it on their
behalf.

I've also explained that if they care, they should consider
complaining to Yahoo and/or switching e-mail providers.

If enough people do the same, maybe Yahoo will reconsider.  If not, so
long most of my e-mail community switches mail providers (i.e.,
treating yahoo.com as damage, and routing around it), I may not care
all that much.

In the maintime, if someone has had the time to hack together some
patches to mailman to write the from field of yahoo.com users to be
yahoo.com.INVALID.  Please send them my way; I'll be most grateful.

		    	   	     	- Ted


From nobody Mon Apr 14 20:28:28 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3C31A031A for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 Oe6sHiqCbpmU for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:28:25 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id D667D1A02F6 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:28:25 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id BEECFD04394; Mon, 14 Apr 2014 23:28:22 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1397532502; bh=WcHnNVR6vkCX23vUxwR06e4BaWFElZ0Z9JfhDpviR0s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=oS6D12jG7im3ZzjX5q+OZpjaxmzSCw2FEw+6ou1UeLTeecLimckV7jq9rBqFWuiqn jFIyrmX+ikU9+4mT+pWaofo62jPKW/MmqxENAgfd7ZtESZQRsHgeZxTXgw609iB/AJ v0p1JuASRHtBTL7sBtu2Dx5bnGWni4lyYBOE/7r0=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 885DDD04101; Mon, 14 Apr 2014 23:28:22 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: "why I quit writing internet standards"
Date: Mon, 14 Apr 2014 23:28:20 -0400
Message-ID: <4756885.Eo3b3po9Vj@scott-latitude-e6320>
User-Agent: KMail/4.11.5 (Linux/3.11.0-19-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <CAL0qLwa5CRwxn0V=7D84KFv9K_u5W5L+PPUXc3KPkD0YHkNo1w@mail.gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <534C067D.8080506@meetinghouse.net> <CAL0qLwa5CRwxn0V=7D84KFv9K_u5W5L+PPUXc3KPkD0YHkNo1w@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/phHD2k-0NfZMSsKP3q9QBQYtyt4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:28:27 -0000

On Monday, April 14, 2014 10:14:19 Murray S. Kucherawy wrote:
> On Mon, Apr 14, 2014 at 9:02 AM, Miles Fidelman
> 
> <mfidelman@meetinghouse.net>wrote:
> > Then again, the current DMARC debacle presents a cautionary tale of more
> > ad hoc approaches.
> 
> DMARC's proponents tried to come to the IETF to form a working group so
> that it could undergo the rigors of standards development, and thus not be
> as "ad hoc" as you're describing.  It was not accepted, on the basis that,
> in essence, the work was already done so there's nothing for the IETF to
> contribute.
> 
> (If I've mischaracterized this, I'm happy to be corrected.)

If that's true, it's my impression it's true because the DMARC proponents 
insisted any possible working group charter preclude meaningful changes to the 
base specification because the work was already done.

Personally, I was kind of OK with the current plan, although I thought it far 
from ideal because I thought there was a clear understanding among the DMARC 
proponents about what kinds of domains p=reject was appropriate for (not ones 
with real users that commonly use use cases for which p=reject is 
problematic).

Now that that clearly isn't the case, I think the plan needs to be revisited.

Scott K


From nobody Mon Apr 14 20:31:12 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5126E1A069D for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.698
X-Spam-Level: 
X-Spam-Status: No, score=0.698 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 0W0-W_Ei0c4L for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:31:09 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id 004921A02F6 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:31:08 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 27A59D043A5; Mon, 14 Apr 2014 23:31:06 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1397532666; bh=zlpg5HCh+m/4S7e9B69TxCiEFfxDur6cuNi5C6bzzJU=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ndk65Q71XyZNBG5fbw1/2bUdMCU9uMtRCSdTRLb+gPVb5elaiYQGvwFrXPUOvjCRw XNoYWpj8jox7JC0je3fcj/DllOkLvoeY/eGFD9kWKA9L8uvw+dm793NAojc3tz4Cr+ 2ylZ1INK4CwJw/E5spL+AxsELEk93xyCmiAvJqtc=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id EC3CDD04101; Mon, 14 Apr 2014 23:31:05 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Date: Mon, 14 Apr 2014 23:31:03 -0400
Message-ID: <3907096.AUYVErToL4@scott-latitude-e6320>
User-Agent: KMail/4.11.5 (Linux/3.11.0-19-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
References: <20140414024956.26078.qmail@joyce.lan> <534BFA0D.7000404@meetinghouse.net> <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4_vGYyJh2yEIX-ffStObFsh1Kec
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:31:10 -0000

On Monday, April 14, 2014 16:53:05 MH Michael Hammer wrote:
...
> Suggest away but the notion of such a group, unless well wrangled and with a
> well-defined charter, brings back memories of the MARID working group and
> its outcome.

The failure of MARID was entirely legal and political.  At the time the 
working group was summarily closed there weren't major technical issues left 
to resolve.  When you try to mix two groups of people, one almost exclusively 
from a free software/open source background with a large corporation that 
insists on patent licenses that are incompatible with free software/open 
source no amount of wrangling is going to save it.

Scott K


From nobody Mon Apr 14 20:35:56 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB9631A06E1 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:35:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 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] autolearn=ham
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 68hrzrSPqugq for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:35:53 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA541A070D for <ietf@ietf.org>; Mon, 14 Apr 2014 20:35:53 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id CB945956135; Mon, 14 Apr 2014 23:35:50 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1397532950; bh=/smlEEgVfSk7uOPpFheIZ4jruSyTcQCU2G/TClqoJQA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=WSd2rieOtXy3D3StyLmf94lNm85J/YwNgj04g/ct0FUmVSaFyifMqTKYW8gPDMytL w51kHnVYUCqbnPoJPICexidkX9l3i/tAIpfEHHIAH8uFBHkgCFkRI5/XOgNcPlrRs2 cXfy2ycOw9dquE0a/k2I6lT43WB/YsZECg5Y1khw=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 964A195612D; Mon, 14 Apr 2014 23:35:50 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Date: Mon, 14 Apr 2014 23:35:48 -0400
Message-ID: <1485381.SfhK6qmW0I@scott-latitude-e6320>
User-Agent: KMail/4.11.5 (Linux/3.11.0-19-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VGCF5NOMUky8dGXzdCG4vmLew0M
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:35:55 -0000

On Monday, April 14, 2014 10:26:44 Murray S. Kucherawy wrote:
> On Mon, Apr 14, 2014 at 8:09 AM, Miles Fidelman
> 
> <mfidelman@meetinghouse.net>wrote:
> > Is it perhaps also incumbent on the folks promulgating DMARC (and its
> > predecessors, and its sure-to-be successors) to work cooperatively with
> > mailing list developers, rather than taking the position "nope, we break
> > mailing lists, not our problem?"
> 
> The DMARC proponents did engage mailman.   Version 2.1.16 includes support
> for a setting that makes the operation of the list DMARC-friendly, though
> likely in a way some people will find unpalatable.  Either way, it was not
> done entirely in a vacuum.
> 
> > I'm kind of coming to the conclusion that what we need to be looking at is
> > defining an SMTP extension that addresses BOTH sets of concerns - and
> > doing
> > so in a cooperative manner that engages not just the community behind DKIM
> > and DMARC, but also the developers and operators of mailman, sympa,
> > majordomo, listserv - and ideally the sendmail, postfix, exim, qmail
> > community.
> > 
> > Dare I suggest that this calls for an IETF working group?
> 
> I mentioned in another thread that the DMARC people did come to the IETF to
> ask for a working group to complete development of the work on the
> standards track.  This request was denied on the grounds that DMARC was
> essentially already done, and thus the IETF had nothing engineering-wise to
> contribute.  There were also too few people that were not already DMARC
> proponents that would commit to working on it.
> 
> (And as I said on that other thread, I'm happy to stand corrected if I've
> mischaracterized any of that.)

My perception (and it may also be wrong) is that anyone who claimed there was 
work yet to be done was shouted down.  It was either prove there was work to 
be done by going off and doing it on your own, or clearly it was done and no 
more work needed doing.

The DMARC spec has certainly improved since it's been public, but I certainly 
don't think it's done and have said so multiple times.  I'm also willing to 
work on it.

As I said in the other thread, I think the only reason it was perceived as 
done is that the private group that developed the spec declared it done and 
fought against any WG charter language that would have permitted changes to 
the core protocol.    Based on that approach, no wonder it was declined.

Scott K


From nobody Mon Apr 14 20:41:18 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12B2F1A0714 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:41:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.398
X-Spam-Level: *
X-Spam-Status: No, score=1.398 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 YN9XxWn6NPbi for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:41:15 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 128501A06E1 for <ietf@ietf.org>; Mon, 14 Apr 2014 20:41:15 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 1954FCC0C2 for <ietf@ietf.org>; Mon, 14 Apr 2014 23:41:12 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id M01X1xu1r+tI for <ietf@ietf.org>; Mon, 14 Apr 2014 23:41:03 -0400 (EDT)
Received: from Miles-Fidelmans-MacBook-Pro.local (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 55725CC0C1 for <ietf@ietf.org>; Mon, 14 Apr 2014 23:41:03 -0400 (EDT)
Message-ID: <534CAA4F.5030200@meetinghouse.net>
Date: Mon, 14 Apr 2014 23:41:03 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <534C067D.8080506@meetinghouse.net> <CAL0qLwa5CRwxn0V=7D84KFv9K_u5W5L+PPUXc3KPkD0YHkNo1w@mail.gmail.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320>
In-Reply-To: <4756885.Eo3b3po9Vj@scott-latitude-e6320>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0a2g9s3GmDt4WqrPGtdQTPeAY5k
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:41:16 -0000

Scott Kitterman wrote:
> On Monday, April 14, 2014 10:14:19 Murray S. Kucherawy wrote:
>> On Mon, Apr 14, 2014 at 9:02 AM, Miles Fidelman
>>
>> <mfidelman@meetinghouse.net>wrote:
>>> Then again, the current DMARC debacle presents a cautionary tale of more
>>> ad hoc approaches.
>> DMARC's proponents tried to come to the IETF to form a working group so
>> that it could undergo the rigors of standards development, and thus not be
>> as "ad hoc" as you're describing.  It was not accepted, on the basis that,
>> in essence, the work was already done so there's nothing for the IETF to
>> contribute.
>>
>> (If I've mischaracterized this, I'm happy to be corrected.)
> If that's true, it's my impression it's true because the DMARC proponents
> insisted any possible working group charter preclude meaningful changes to the
> base specification because the work was already done.
>
> Personally, I was kind of OK with the current plan, although I thought it far
> from ideal because I thought there was a clear understanding among the DMARC
> proponents about what kinds of domains p=reject was appropriate for (not ones
> with real users that commonly use use cases for which p=reject is
> problematic).
>
> Now that that clearly isn't the case, I think the plan needs to be revisited.
>

It it was clearly understood about when p=reject is/is not appropriate - 
and someone (who's corporate name begins with Y) misapplied it - is this 
not akin to the propagation of corrupted routing data, and meriting a 
comparable response from all concerned?  If done intentionally, with 
knowledge of the potential consequences - does this not tread into the 
grounds of a DDoS attack, and merit comparable response?  And if the 
perpetrator does not act to roll back their action - does that not merit 
a strong response?

I believe that there are laws against "knowingly caus[ing] the 
transmission of a program, information code, or command, and as a result 
of such conduct, intentionally causes damages without authorization to a 
protected computerâ€� (That's from the Computer Fraud and Abuse Act.)

And.. just for the heck of it.. I reported this to CERT.  The impact on 
the systems I run has been far higher than, say, the Heartbeat 
vulnerability.  Kind of interested to see what kind of response I get.

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 20:57:11 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1BD1A0770 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:56:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.602
X-Spam-Level: 
X-Spam-Status: No, score=-0.602 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 akbw-LRP9B8f for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 20:56:37 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD471A076D for <ietf@ietf.org>; Mon, 14 Apr 2014 20:56:37 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 48B6995612D; Mon, 14 Apr 2014 23:56:34 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1397534194; bh=nZAEXg4fjouwTypy/ZJ9cJlBi4N8MbYlPtEUJv24j/U=; h=From:To:Subject:Date:In-Reply-To:References:From; b=j7E8hLf+5azJm7BFufIPq365pLNG/f2H4aagY3fcPKYY8o5Jk3hSH3ooe5VNSHuZU HWDL/OWsQ3roLWttDOF13QrDfd31iC28I8oMGFobJLTNMqC2PY+003EeCT9R+LwL4S PgD1J+0En/h1oJaUfsygj83xsHCXJ7azlImcp9fA=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 12284D041A0; Mon, 14 Apr 2014 23:56:33 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Date: Mon, 14 Apr 2014 23:56:23 -0400
Message-ID: <5593510.KZqL8eSkZ2@scott-latitude-e6320>
User-Agent: KMail/4.11.5 (Linux/3.11.0-19-generic; KDE/4.11.5; x86_64; ; )
In-Reply-To: <534C4FB1.9060508@bbiw.net>
References: <53499A5E.9020805@meetinghouse.net> <534C4AF8.60709@sonnection.nl> <534C4FB1.9060508@bbiw.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SLF0Fru0Oh_exjN5_UWDHh9utx4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 03:56:49 -0000

On Monday, April 14, 2014 14:14:25 Dave Crocker wrote:
> On 4/14/2014 1:54 PM, Rolf E. Sonneveld wrote:
> > This might have been true if:
> ...
> 
> > 2. the decision making process within a closed industry consortium with
> > maybe less than 20 members, representing immense commercial power, could
> > be compared to the process of consensus, that's being used within IETF.
> 
> By way of pressing a particular process issue, without commenting on any
> of the surrounding issues:
> 
>     It's certainly true that the DMARC specification has not gone
> through an IETF approval process.
> 
>     That said, the document has been subject to open review for quite
> awhile, first (and continuing) via a mailing list at dmarc.org and more
> recently also one hosted at the IETF.  And the handling of reviews has
> been substantive.  Again, not an IETF open process, but substantive.
> 
>     Over quite a few months, there were a number of aggressive efforts
> to solicit community suggestions and agreement about the engineering
> work or document refinement work needed on the specification.
> 
>     Nothing close to rough consensus developed for any technical or
> documentation work.  Not on the dmarc.org list and not on the IETF's
> dmarc list.
> 
> If the community wanted changes to the specification, it had quite a bit
> of opportunity to call for the changes and/or call for  doing such work
> in the IETF.

Not really.  As long as change control is outside the IETF and it's normal 
processes, outsiders to the core group can call for change and that change can 
be accepted or ignored be the insiders in the group with none of the normal 
IETF processes that resolve issues and lead to rough consensus.

It's not a very attractive environment to expend ones "free" time in.  I did 
some review of the spec, but certainly would be been more motivated to do a 
more thorough and complete job in the context of a WG.

Scott K


From nobody Mon Apr 14 21:02:31 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 706E31A0198 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 21:02:26 -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, SPF_PASS=-0.001] autolearn=ham
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 MPPmhX2xZNvj for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 21:02:23 -0700 (PDT)
Received: from mail-yh0-x22e.google.com (mail-yh0-x22e.google.com [IPv6:2607:f8b0:4002:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 55B7B1A0491 for <ietf@ietf.org>; Mon, 14 Apr 2014 21:02:23 -0700 (PDT)
Received: by mail-yh0-f46.google.com with SMTP id b6so8839935yha.5 for <ietf@ietf.org>; Mon, 14 Apr 2014 21:02:20 -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:content-type; bh=XlAF+/ziouawaCF4MAKOAYZZjVir+JrBL8Ws/2oUa/Y=; b=aEXwJd/8zXCjX6PKhAQKajcg3rIJKpEr9nCnT8l7XCwDC3qDHEQZfYyelzOPRvQkHa IK6s4u9cgxtVwERVwIPLlfVw80wW4OPYsImoVakaCqCFRhMF+VNfUGdbUS2VQCL1yv7w C68qLOBe2R431a8iomtmpWTPPk2yoH3u5pwbe8SblvO6rNoBxGXqrDrGRmqGGszo7sHI Mo/kBOdCXt1At91GusiWoD5UsyIbijpjFXBdYABm3VTrt1ztEoist0mMuagyyGFSZvkg IfGasaDoYJMv8drshDbzxpMcTfMkfdeciFQwvPSPiMqEd92HNeZNGp4K6PvyDxoVASNv +jGw==
MIME-Version: 1.0
X-Received: by 10.236.13.46 with SMTP id a34mr64405397yha.28.1397534540360; Mon, 14 Apr 2014 21:02:20 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Mon, 14 Apr 2014 21:02:20 -0700 (PDT)
In-Reply-To: <534C8F2B.9060903@gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com>
Date: Tue, 15 Apr 2014 05:02:20 +0100
Message-ID: <CADnDZ8-DWU3ZE_WZO3vwBWvYtNZacdN9mDUof0jmfu2uKZ2poQ@mail.gmail.com>
Subject: What I've been wondering about the DMARC problem
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c3dc3ad6f32c04f70cdd30
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ELnsHWl2-EsYyKJDFc5lpsu_e-4
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 04:02:27 -0000

--001a11c3dc3ad6f32c04f70cdd30
Content-Type: text/plain; charset=UTF-8

The standard procedure in many companies is business scoped, so they
identify important business users and the business returns/damages. Most
important users are not IT experts, and use email for personal exchange. Yahoo
has signed an agreement with users to protect its information system, so
all seem to follow that, and all users are free to stop using services or
not.

AB

On Tuesday, April 15, 2014, Brian E Carpenter wrote:

> I thought that standard operating procedure in the IT industry
> was: if you roll something out and it causes serious breakage to
> some of your users, you roll it back as soon as possible.
>
> Why hasn't Yahoo rolled back its 'reject' policy by now?
>
> Regards
>    Brian
>
>

--001a11c3dc3ad6f32c04f70cdd30
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

The standard procedure in many=C2=A0companies=C2=A0is business scoped, so t=
hey identify important business=C2=A0users and the=C2=A0business returns/da=
mages. Most important=C2=A0users are not IT experts, and use email for pers=
onal exchange.=C2=A0<span></span>Yahoo has signed an agreement with users t=
o protect its information system,=C2=A0so all seem to follow that, and all =
users are free to=C2=A0stop using services or not.=C2=A0<div>

<br></div><div>AB<br><br>On Tuesday, April 15, 2014, Brian E Carpenter  wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">I thought that standard operating pro=
cedure in the IT industry<br>


was: if you roll something out and it causes serious breakage to<br>
some of your users, you roll it back as soon as possible.<br>
<br>
Why hasn&#39;t Yahoo rolled back its &#39;reject&#39; policy by now?<br>
<br>
Regards<br>
=C2=A0 =C2=A0Brian<br>
<br>
</blockquote></div>

--001a11c3dc3ad6f32c04f70cdd30--


From nobody Mon Apr 14 21:07:54 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A60ED1A031F for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 21:07:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 53nfibOSteU0 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 21:07:50 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 803371A02FF for <ietf@ietf.org>; Mon, 14 Apr 2014 21:07:50 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id A79C8CC0C8 for <ietf@ietf.org>; Tue, 15 Apr 2014 00:07:47 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id HO0MS7nXlEGG for <ietf@ietf.org>; Tue, 15 Apr 2014 00:07:39 -0400 (EDT)
Received: from Miles-Fidelmans-MacBook-Pro.local (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id B9B9ACC0CD for <ietf@ietf.org>; Tue, 15 Apr 2014 00:07:38 -0400 (EDT)
Message-ID: <534CB08A.8080802@meetinghouse.net>
Date: Tue, 15 Apr 2014 00:07:38 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <CADnDZ8-DWU3ZE_WZO3vwBWvYtNZacdN9mDUof0jmfu2uKZ2poQ@mail.gmail.com>
In-Reply-To: <CADnDZ8-DWU3ZE_WZO3vwBWvYtNZacdN9mDUof0jmfu2uKZ2poQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/b0CdjibFrsnhOOgg8MaNgVsFq5Q
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 04:07:51 -0000

Important business users, with Yahoo accounts?  Is that a joke?

Just as a reference point:
- I just logged into my long-unused, and un-publicized yahoo email 
account - and the only thing there is Spam
- the lion's share of mail that comes from yahoo, to my normal account, 
is spam
- unfortunately, a good number of people on the email lists that I run 
seem to have Yahoo mail accounts - and a good amount of the mail that 
comes from those accounts is... you guessed it... spam - because yahoo 
email accounts seem to be vulnerable to cracking and exploitation

So, just who is it that Yahoo is protecting here?

Abdussalam Baryun wrote:
> The standard procedure in many companies is business scoped, so they 
> identify important business users and the business returns/damages. 
> Most important users are not IT experts, and use email for personal 
> exchange. Yahoo has signed an agreement with users to protect its 
> information system, so all seem to follow that, and all users are free 
> to stop using services or not.
>
> AB
>
> On Tuesday, April 15, 2014, Brian E Carpenter wrote:
>
>     I thought that standard operating procedure in the IT industry
>     was: if you roll something out and it causes serious breakage to
>     some of your users, you roll it back as soon as possible.
>
>     Why hasn't Yahoo rolled back its 'reject' policy by now?
>
>     Regards
>        Brian
>


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 14 21:32:59 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31E6E1A0301 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 21:32:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 MItbwWUJg58T for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 21:32:56 -0700 (PDT)
Received: from st11p02mm-asmtp002.mac.com (st11p02mm-asmtpout002.mac.com [17.172.220.237]) by ietfa.amsl.com (Postfix) with ESMTP id 727571A024D for <ietf@ietf.org>; Mon, 14 Apr 2014 21:32:55 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N4200G061XWFT40@st11p02mm-asmtp002.mac.com> for ietf@ietf.org; Tue, 15 Apr 2014 04:32:22 +0000 (GMT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <5593510.KZqL8eSkZ2@scott-latitude-e6320>
Date: Tue, 15 Apr 2014 05:32:19 +0100
Message-id: <B078C9C1-1148-412B-9752-4B7A437A9780@me.com>
References: <53499A5E.9020805@meetinghouse.net> <534C4AF8.60709@sonnection.nl> <534C4FB1.9060508@bbiw.net> <5593510.KZqL8eSkZ2@scott-latitude-e6320>
To: "ietf@ietf.org list" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaEhEKTEMXGx0EGx0YBBIZBBsSEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsZGmJCH2lmGVtNGXhzB xlsGh4ZGGcZEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGxIQGx4aHxsRCl5ZF2FNRlh SEQpMRhdsa2sRCkNaFxgbGQQbGBkEGxMYBBkaEQpEXhcYEQpCRRdmUH1dH21kGgVIYxEKQk4Xb HBgeUAdYlJpGmIRCkJMF2dJH215aRh+ckJNEQpCbBdlaGUYbU0cGENGThEKQkAXbmkdZVkTHH1 yR0MRCkJYF2lsWR0Ta20dfXpQEQpwZxdlfVxiYU9lbRNSTBEKcGgXbUNGBWBCThNvUFsRCnBoF 2dAcHhdThMcEn97EQpwaBdrcE0cBU5HEhJYHxEKcGgXYHJJQ0ZAY2llHB0RCnBoF2Jmek5JbFM SfnpMEQpwfxdvG0FoemNmHkhmExEKcF8XZHAeGVh9UGxwYVkRCnBsF2tmTmtBZV9mU2cBEQpwT BdjTkxufU4cc2RpWxE=
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-14_01:2014-04-14,2014-04-14,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404150072
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mGrwLb-CyBXhtWuLAsUx_pIGL1A
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 04:32:58 -0000

On 15 Apr 2014, at 04:56, Scott Kitterman <scott@kitterman.com> wrote:
> On Monday, April 14, 2014 14:14:25 Dave Crocker wrote:
>> If the community wanted changes to the specification, it had quite a bit
>> of opportunity to call for the changes and/or call for  doing such work
>> in the IETF.
> 
> Not really.  As long as change control is outside the IETF and it's normal 
> processes, outsiders to the core group can call for change and that change can 
> be accepted or ignored be the insiders in the group with none of the normal 
> IETF processes that resolve issues and lead to rough consensus.

Yes.

Basically DMARC was always an outsider effort.  The effect of a bunch of very important ESPs (and a bunch of security types) crying "Look!  We've solved the email forgery problem!" was to inspire me to look at the spec, shrug it off as yet another FUSSP *, and move on.  Does this mean that I have materially failed to contribute?  Well maybe, but it means a lot for the spec to be in the IETF where I can point out how broken it is. :)

And, to be clear: I respect the goals of the proposal, and will be reasonable in accommodating it.  But to suggest that the contortions of the proponents in keeping it from the watchful eye of the IETF weren't in some small way intended to advance DMARC by force in numbers rather than consensus strains credulity, just a tad.

Cheers,
Sabahattin

* https://twitter.com/sgucukoglu/status/174104462758133760


From nobody Mon Apr 14 21:59:13 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C768D1A072D for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 21:58:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 h550lCJxxt3e for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 21:58:52 -0700 (PDT)
Received: from mail-we0-x229.google.com (mail-we0-x229.google.com [IPv6:2a00:1450:400c:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 50E281A0743 for <ietf@ietf.org>; Mon, 14 Apr 2014 21:58:52 -0700 (PDT)
Received: by mail-we0-f169.google.com with SMTP id w62so9052569wes.14 for <ietf@ietf.org>; Mon, 14 Apr 2014 21:58:49 -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:content-type; bh=PEk0UkJWzP09KEYwjXL99I6WiohX9u9FgFV4s3P1FdA=; b=ZsNzlWmpT93Mdg2s+kv8QRk/nAcN8H/v4HDlYDcyO6SbI1+6OoKJ6ihoydeT38OHjD r7Hq3Zgl7FanQ0EK/b5LPSfWzbY64GbwJJff9Qp3zOh1SllkZKZuIQvG+zWFnK4+NQVC kskesrrRaNkQCjoUgKF/M+15qJi8Rd9C5NAWEvXdzSPZRTaD4pUxBY+Uf4puriQHWbU9 8logF55FaudSCIn0KG8nrJqMWKaBdpW4/TpyhLIKcC+qsEIzsnCe4sg3JkJrregzirp9 U4kqdUEkVf3kkykkkCppqbfaWh8sOSP4JzoE8+QmHWc+A09JCHyAxf3mOyrrx9r+mXHO oJKQ==
MIME-Version: 1.0
X-Received: by 10.180.211.116 with SMTP id nb20mr624891wic.5.1397537929051; Mon, 14 Apr 2014 21:58:49 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Mon, 14 Apr 2014 21:58:48 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1404142150430.32657@joyce.lan>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan>
Date: Mon, 14 Apr 2014 21:58:48 -0700
Message-ID: <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com>
Subject: Re: protecting the Internet from DMARC damage, was perspectives
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=001a11c26ab4d2447604f70da7d7
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/sv_zH0OPXo39wAtyS3KMppsCtVQ
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 04:58:58 -0000

--001a11c26ab4d2447604f70da7d7
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 14, 2014 at 6:59 PM, John R Levine <johnl@taugh.com> wrote:

> I've never said that lists won't change, I've said that we're not going to
> screw them up to work around your FUSSP.
>

It would be great if it were more of a dialog rather than a repeated
exercise in intransigence.  I guess when you're a list, everything looks
like a FUSSP.

Having been involved in things like SPF, DKIM, ADSP, etc. over the years, I
can say that mailing lists always recur as a major obstacle.  "Lists have
been doing what they're doing for N years and they work fine.  You don't
get to mess with them."  That's the mantra.

In DKIM, we even did a whole separate RFC to talk about all the fun ways
lists are a special case.

The specifications of 30 years ago included some neat capabilities for
communication, some of which mailing list servers employ to do what they
do.  I mean, I get that being able to put whatever you want in the From:
field is a feature.  Honest, I do.  But meanwhile, increasingly, bad people
use the very same capabilities to do their hugely expensive harm.  Is it
really the case that the benefit mailing lists (as they are today anyway)
bring to the Internet outweighs the harm of leaving these capabilities wide
open?

There are probably earlier examples, but remember the finger protocol?  In
80s and 90s, it was on, and it was harmless, maybe even useful.  Then it
started to get abused and exploited, so we collectively turned it off
because the damage outweighed the benefit.  That practice has been applied
countless times since, to any service that gets rolled out in any context
you can imagine that then gets discovered and exploited by bad actors: We
fix the vulnerability, or we kill the service.  We don't believe in
"substantial non-infringing use" as a reason to keep something bad online.
I can't think of an instance where that's not the case except email abuse,
because we protect mailing lists, which have enjoyed apparent immunity
despite ever-increasing pain to the victims of that abuse with no solution
in sight.

So why do lists get the privilege of being immutable?  Can't there be some
quid pro quo?  Do the people with the problem also have to come up with the
solution, preferably maintaining the status quo for lists, or could it
maybe be more of a cooperative brainstorming thing?  Is it really totally
inconceivable and unacceptable that there has to be some evolution here?

And before anyone tries to claim it, I'm not saying lists are second class
actors, nor am I making any kind of claim about traffic percentage.  I
would just like to understand when and why they were granted this protected
status in standards work that they appear to enjoy.

-MSK

--001a11c26ab4d2447604f70da7d7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 14, 2014 at 6:59 PM, John R Levine <span dir=
=3D"ltr">&lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@tau=
gh.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote">

<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">I&#39;ve never said that =
lists won&#39;t change, I&#39;ve said that we&#39;re not going to screw the=
m up to work around your FUSSP.<br>

</blockquote><div><br></div><div>It would be great if it were more of a dia=
log rather than a repeated exercise in intransigence.=C2=A0 I guess when yo=
u&#39;re a list, everything looks like a FUSSP.<br></div><div><br>Having be=
en involved in things like SPF, DKIM, ADSP, etc. over the years, I can say =
that mailing lists always recur as a major obstacle.=C2=A0 &quot;Lists have=
 been doing what they&#39;re doing for N years and they work fine.=C2=A0 Yo=
u don&#39;t get to mess with them.&quot;=C2=A0 That&#39;s the mantra.<br>

<br></div><div>In DKIM, we even did a whole separate RFC to talk about all =
the fun ways lists are a special case.<br></div><div><br></div><div>The spe=
cifications of 30 years ago included some neat capabilities for communicati=
on, some of which mailing list servers employ to do what they do.=C2=A0 I m=
ean, I get that being able to put whatever you want in the From: field is a=
 feature.=C2=A0 Honest, I do.=C2=A0 But meanwhile, increasingly, bad people=
 use the very same capabilities to do their hugely expensive harm.=C2=A0 Is=
 it really the case that the benefit mailing lists (as they are today anywa=
y) bring to the Internet outweighs the harm of leaving these capabilities w=
ide open?<br>

</div><div><br></div><div>There are probably earlier examples, but remember=
 the finger protocol?=C2=A0 In 80s and 90s, it was on, and it was harmless,=
 maybe even useful.=C2=A0 Then it started to get abused and exploited, so w=
e collectively turned it off because the damage outweighed the benefit.=C2=
=A0 That practice has been applied countless times since, to any service th=
at gets rolled out in any context you can imagine that then gets discovered=
 and exploited by bad actors: We fix the vulnerability, or we kill the serv=
ice.=C2=A0 We don&#39;t believe in &quot;substantial non-infringing use&quo=
t; as a reason to keep something bad online.=C2=A0 I can&#39;t think of an =
instance where that&#39;s not the case except email abuse, because we prote=
ct mailing lists, which have enjoyed apparent immunity despite ever-increas=
ing pain to the victims of that abuse with no solution in sight.<br>

<br></div><div>So why do lists get the privilege of being immutable?=C2=A0 =
Can&#39;t there be some quid pro quo?=C2=A0 Do the people with the problem =
also have to come up with the solution, preferably maintaining the status q=
uo for lists, or could it maybe be more of a cooperative brainstorming thin=
g?=C2=A0 Is it really totally inconceivable and unacceptable that there has=
 to be some evolution here?<br>

<br></div><div>And before anyone tries to claim it, I&#39;m not saying list=
s are second class actors, nor am I making any kind of claim about traffic =
percentage.=C2=A0 I would just like to understand when and why they were gr=
anted this protected status in standards work that they appear to enjoy.<br=
>

</div><div><br></div><div>-MSK<br></div></div></div></div>

--001a11c26ab4d2447604f70da7d7--


From nobody Mon Apr 14 22:21:11 2014
Return-Path: <seth.p.johnson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46DB61A0345 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 22:21:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 1yUCp9cc5umw for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 22:21:05 -0700 (PDT)
Received: from mail-ve0-x22e.google.com (mail-ve0-x22e.google.com [IPv6:2607:f8b0:400c:c01::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 0462A1A0338 for <ietf@ietf.org>; Mon, 14 Apr 2014 22:21:04 -0700 (PDT)
Received: by mail-ve0-f174.google.com with SMTP id oz11so8411124veb.5 for <ietf@ietf.org>; Mon, 14 Apr 2014 22:21:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=y11iWshWUytiBhkUtEHwnRFwHTMpmwlwAKt0BXvnQHA=; b=Dcm9qlpwSgVRQrWJcxn+zcBivMS40ObwRQ5hP9rLSoIj409uW0ZOgq58+jcnw6SqcQ Cvvxw1zX5kNhs+O/SzH+8DkQLbeXPjyn9sLL8nheu5oDSr44ngU5TRQytce0ftzBEiiH eHd8KKjlbvfvrCt0/FR2BN9X3NnX06NafdFmWx9F1gpVHmBAd+/sO1ShsVkUzOsl62hd Lr6mJJYwaPU99P+W9wu5lfF1Ew7LBBp8NMOrubvZmpJ9c9MY3vgFVKm8Lcs82quT+RVx Wi32yzP5G6dZLe6/ZHaSarNEWuv4QVLsAy5XHnrQZm03zfEtnDoVsPxqXTZoDy2Y/Fda DklA==
X-Received: by 10.220.4.132 with SMTP id 4mr40841106vcr.9.1397539262067; Mon, 14 Apr 2014 22:21:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.66.6 with HTTP; Mon, 14 Apr 2014 22:20:21 -0700 (PDT)
In-Reply-To: <534CB08A.8080802@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <CADnDZ8-DWU3ZE_WZO3vwBWvYtNZacdN9mDUof0jmfu2uKZ2poQ@mail.gmail.com> <534CB08A.8080802@meetinghouse.net>
From: Seth Johnson <seth.p.johnson@gmail.com>
Date: Tue, 15 Apr 2014 01:20:21 -0400
Message-ID: <CAJkfFBzs6JMxGSePJ6-1_=kLZRwwgwEPBD_tnh8qXPKQCmSMPA@mail.gmail.com>
Subject: Re: What I've been wondering about the DMARC problem
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=001a11c3a2c6467bc104f70df702
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/U6pK_H3eNDwA-TxmTOPElwBhk48
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 05:21:10 -0000

--001a11c3a2c6467bc104f70df702
Content-Type: text/plain; charset=UTF-8

The framework internationally is different.  Within free countries, there's
a culture of expectations that certain things will be unacceptable, or will
be resisted by self-respecting citizens.  That culture is based in a system
that guards fundamental liberties, and people are able to rely on it to do
so, though for private firms the limits aren't so definitive as they are
for the government.

Internationally, the limits are no longer so definitive, and that's because
even though governments will sign onto instruments like the UDHR, those
rights are not actually fundamental, even if we call them that.
Fundamental rights have an undeniable priority within countries where they
have been claimed in the founding act.  On that foundation, judges are
always obliged to assess fundamental rights in light of the unarguable fact
that their priority over the government was part of the original creation
of the whole system.  There's no founding act in the international arena
that sets the priority of people over the governments of the world, so
rights are actually at the indulgence of governments, and governments can
always assert their state interests are so important that they warrant
impinging on fundamental liberties.

We just saw an example of this with the Snowden disclosures.  We've been
through a long period where we couldn't get our government to actually do
much for us, or conversely to not invade our liberties -- because the
claims that the government was snooping pervasively were kept marginal.
But once documentation moved those considerations, we suddenly began seeing
the appeals work again: that's not the kind of country we are, what we set
up for ourselves.  And while it's still in a bit of denial, we are seeing a
gradual grudging retracting -- again, because the basis in fundamental
liberties is unarguably related to how we set the government up in the
founding act(s).

This is for governments and the more definitive relationship between
fundamental liberties and the government; that is, that they are limits on
the government.  The judicial system treats fundamental rights violations
by the government in terms of "strict scrutiny," which means a governmental
act that impinges on fundamental liberties must serve a compelling state
interest, and even then, must be narrowly tailored.  For private parties,
it's more that the working system creates a culture of people who enjoy
this ability to live in a system where these limits on the government are
actually at play -- and that's a context that more easily supports
attitudes of resistance and pushback from people who see their dignity
invaded by private firms that do excessive things.

None of this exists internationally.  The best you can place some faint
hope in is that national/state interests will be "balanced" against rights
expressed in a treaty.  That's a totally different standard from strict
scrutiny.  And relying on even that is unrealistic, because governments
have the "epistemic priority" -- and so they often, quite freely, simply
claim their sovereignty and act according to what they claim is an
important state interest.  They simply have that wherewithal at the
international level.

All of which is preface to say that the result is that governments and
private parties (and corporations, who have concocted trans-state "rights"
through judges acting to fill in gaps in the law over the years) know the
rules don't apply the same way in the international arena.

In fact, given the transitions currently being attempted, whether with the
IANA functions or "Internet governance" more generally, Yahoo's DMARC
behavior may really be a sort of dry run, testing the ability to take
advantage of the moves to put concerns related to the operation of the
Internet into an international frame, which folks are pushing for without
really recognizing what's missing in that context, what they have sort of
unconsciously relied on and taken for granted within systems of checks and
balances that are rooted solidly at national levels.

The checks and balances don't work the same internationally, and that
circumstance can be exploited (and is, all the times, these days).

People might push back, but they don't really do so with the same sense of
fundamental recourse assured by a solidly rooted system.  And Yahoo knows
this.  And we're just shoring that up by saying we can just switch
multistakeholderism to the international arena.

(All of this is aside from other factors not generally acknowledged -- that
there are actually inter-governmentally endorsed frames in place that will
have a bearing on IANA type functions or domain names (Names, Numbers,
Addresses and Identifiers/NNAI, in the ITU parlance), regardless of the
fact the IANA transition defines itself as non-governmentally-led or
inter-governmental.  Looking at this in that light, Yahoo may be forcing
the creation of a context in which it can start to exercise those
frameworks.)


Seth


On Tue, Apr 15, 2014 at 12:07 AM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:

> Important business users, with Yahoo accounts?  Is that a joke?
>
> Just as a reference point:
> - I just logged into my long-unused, and un-publicized yahoo email account
> - and the only thing there is Spam
> - the lion's share of mail that comes from yahoo, to my normal account, is
> spam
> - unfortunately, a good number of people on the email lists that I run
> seem to have Yahoo mail accounts - and a good amount of the mail that comes
> from those accounts is... you guessed it... spam - because yahoo email
> accounts seem to be vulnerable to cracking and exploitation
>
> So, just who is it that Yahoo is protecting here?
>
>
> Abdussalam Baryun wrote:
>
>> The standard procedure in many companies is business scoped, so they
>> identify important business users and the business returns/damages. Most
>> important users are not IT experts, and use email for personal exchange.
>> Yahoo has signed an agreement with users to protect its information system,
>> so all seem to follow that, and all users are free to stop using services
>> or not.
>>
>> AB
>>
>> On Tuesday, April 15, 2014, Brian E Carpenter wrote:
>>
>>     I thought that standard operating procedure in the IT industry
>>     was: if you roll something out and it causes serious breakage to
>>     some of your users, you roll it back as soon as possible.
>>
>>     Why hasn't Yahoo rolled back its 'reject' policy by now?
>>
>>     Regards
>>        Brian
>>
>>
>
> --
> In theory, there is no difference between theory and practice.
> In practice, there is.   .... Yogi Berra
>
>

--001a11c3a2c6467bc104f70df702
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><div><div><div><div><div><div>The framework internati=
onally is different.=C2=A0 Within free countries, there&#39;s a culture of =
expectations that certain things will be unacceptable, or will be resisted =
by self-respecting citizens.=C2=A0 That culture is based in a system that g=
uards fundamental liberties, and people are able to rely on it to do so, th=
ough for private firms the limits aren&#39;t so definitive as they are for =
the government.<br>


<br></div>Internationally, the limits are no longer so definitive, and that=
&#39;s because even though governments will sign onto instruments like the =
UDHR, those rights are not actually fundamental, even if we call them that.=
=C2=A0 Fundamental rights have an undeniable priority within countries wher=
e they have been claimed in the founding act.=C2=A0 On that foundation, jud=
ges are always obliged to assess fundamental rights in light of the unargua=
ble fact that their priority over the government was part of the original c=
reation of the whole system.=C2=A0 There&#39;s no founding act in the inter=
national arena that sets the priority of people over the governments of the=
 world, so rights are actually at the indulgence of governments, and govern=
ments can always assert their state interests are so important that they wa=
rrant impinging on fundamental liberties.<br>


<br>We just saw an example of this with the Snowden disclosures.=C2=A0 We&#=
39;ve been through a long period where we couldn&#39;t get our government t=
o actually do much for us, or conversely to not invade our liberties -- bec=
ause the claims that the government was snooping pervasively were kept marg=
inal.=C2=A0 But once documentation moved those considerations, we suddenly =
began seeing the appeals work again: that&#39;s not the kind of country we =
are, what we set up for ourselves.=C2=A0 And while it&#39;s still in a bit =
of denial, we are seeing a gradual grudging retracting -- again, because th=
e basis in fundamental liberties is unarguably related to how we set the go=
vernment up in the founding act(s).<br>


<br></div>This is for governments and the more definitive relationship betw=
een fundamental liberties and the government; that is, that they are limits=
 on the government.=C2=A0 The judicial system treats fundamental rights vio=
lations by the government in terms of &quot;strict scrutiny,&quot; which me=
ans a governmental act that impinges on fundamental liberties must serve a =
compelling state interest, and even then, must be narrowly tailored.=C2=A0 =
For private parties, it&#39;s more that the working system creates a cultur=
e of people who enjoy this ability to live in a system where these limits o=
n the government are actually at play -- and that&#39;s a context that more=
 easily supports attitudes of resistance and pushback from people who see t=
heir dignity invaded by private firms that do excessive things.<br>


<br></div>None of this exists internationally.=C2=A0 The best you can place=
 some faint hope in is that national/state interests will be &quot;balanced=
&quot; against rights expressed in a treaty.=C2=A0 That&#39;s a totally dif=
ferent standard from strict scrutiny.=C2=A0 And relying on even that is unr=
ealistic, because governments have the &quot;epistemic priority&quot; -- an=
d so they often, quite freely, simply claim their sovereignty and act accor=
ding to what they claim is an important state interest.=C2=A0 They simply h=
ave that wherewithal at the international level.<br>

<br></div>All of which is preface to say that the result is that government=
s and private parties (and corporations, who have concocted trans-state &qu=
ot;rights&quot; through judges acting to fill in gaps in the law over the y=
ears) know the rules don&#39;t apply the same way in the international aren=
a.<br>

<br></div>In fact, given the transitions currently being attempted, whether=
 with the IANA functions or &quot;Internet governance&quot; more generally,=
 Yahoo&#39;s DMARC behavior may really be a sort of dry run, testing the ab=
ility to take advantage of the moves to put concerns related to the operati=
on of the Internet into an international frame, which folks are pushing for=
 without really recognizing what&#39;s missing in that context, what they h=
ave sort of unconsciously relied on and taken for granted within systems of=
 checks and balances that are rooted solidly at national levels.<br>

<br>The checks and balances don&#39;t work the same internationally, and th=
at circumstance can be exploited (and is, all the times, these days).<br><b=
r></div>People might push back, but they don&#39;t really do so with the sa=
me sense of fundamental recourse assured by a solidly rooted system.=C2=A0 =
And Yahoo knows this.=C2=A0 And we&#39;re just shoring that up by saying we=
 can just switch multistakeholderism to the international arena.<br>

<br></div>(All of this is aside from other factors not generally acknowledg=
ed -- that there are actually inter-governmentally endorsed frames in place=
 that will have a bearing on IANA type functions or domain names (Names, Nu=
mbers, Addresses and Identifiers/NNAI, in the ITU parlance), regardless of =
the fact the IANA transition defines itself as non-governmentally-led or in=
ter-governmental.=C2=A0 Looking at this in that light, Yahoo may be forcing=
 the creation of a context in which it can start to exercise those framewor=
ks.)<br>

<div><div><div><div><br><br></div><div>Seth
</div></div></div></div></div><div class=3D"gmail_extra"><br><br><div class=
=3D"gmail_quote">On Tue, Apr 15, 2014 at 12:07 AM, Miles Fidelman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank=
">mfidelman@meetinghouse.net</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Important business users, with Yahoo account=
s? =C2=A0Is that a joke?<br>
<br>
Just as a reference point:<br>
- I just logged into my long-unused, and un-publicized yahoo email account =
- and the only thing there is Spam<br>
- the lion&#39;s share of mail that comes from yahoo, to my normal account,=
 is spam<br>
- unfortunately, a good number of people on the email lists that I run seem=
 to have Yahoo mail accounts - and a good amount of the mail that comes fro=
m those accounts is... you guessed it... spam - because yahoo email account=
s seem to be vulnerable to cracking and exploitation<br>


<br>
So, just who is it that Yahoo is protecting here?<div class=3D"HOEnZb"><div=
 class=3D"h5"><br>
<br>
Abdussalam Baryun wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The standard procedure in many companies is business scoped, so they identi=
fy important business users and the business returns/damages. Most importan=
t users are not IT experts, and use email for personal exchange. Yahoo has =
signed an agreement with users to protect its information system, so all se=
em to follow that, and all users are free to stop using services or not.<br=
>


<br>
AB<br>
<br>
On Tuesday, April 15, 2014, Brian E Carpenter wrote:<br>
<br>
=C2=A0 =C2=A0 I thought that standard operating procedure in the IT industr=
y<br>
=C2=A0 =C2=A0 was: if you roll something out and it causes serious breakage=
 to<br>
=C2=A0 =C2=A0 some of your users, you roll it back as soon as possible.<br>
<br>
=C2=A0 =C2=A0 Why hasn&#39;t Yahoo rolled back its &#39;reject&#39; policy =
by now?<br>
<br>
=C2=A0 =C2=A0 Regards<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Brian<br>
<br>
</blockquote>
<br>
<br></div></div><div class=3D"HOEnZb"><div class=3D"h5">
-- <br>
In theory, there is no difference between theory and practice.<br>
In practice, there is. =C2=A0 .... Yogi Berra<br>
<br>
</div></div></blockquote></div><br></div>

--001a11c3a2c6467bc104f70df702--


From nobody Mon Apr 14 22:30:12 2014
Return-Path: <seth.p.johnson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4245F1A075C for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 22:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 AOeH0yvMM8qv for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 22:30:03 -0700 (PDT)
Received: from mail-vc0-x22b.google.com (mail-vc0-x22b.google.com [IPv6:2607:f8b0:400c:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 282991A0751 for <ietf@ietf.org>; Mon, 14 Apr 2014 22:30:02 -0700 (PDT)
Received: by mail-vc0-f171.google.com with SMTP id lg15so8567963vcb.16 for <ietf@ietf.org>; Mon, 14 Apr 2014 22:29:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=KwTz0wIW4dGLtohc2YkSiR2aItKX8yW1T255BDuC+/A=; b=U6m1K06m+7bC46saeMOo+LNPdoyJMu0fufG6HoGXUS2MYeMXBVUhFq2T6Y4fli25Rv ZqYwD8R1r1b/3CB48Y1ltCk6K2VcmrYnNNifKEeqAW+rw6npWzZOUW6FROUhz8LQPbMJ XkgsSACG3Jg9SBJ6lym+smLtGNB3pBMMptBsAGBy1H+xDnWLF8fLK+AyAKWXhcfnTStC 5qETCvINGjNhCq58xS8B8ob8cr2KPe0qOLAeoDWaj/EibZubPqc+oDqFum6P+pNF6fQe M0/J0pOIQ1k/Ky25Y4L4kf0M1BeEP+8UGL5Nbsjtp1La0/k/tSO7+sb/UCF206Oh0h0h TZmQ==
X-Received: by 10.220.92.135 with SMTP id r7mr40448084vcm.11.1397539799231; Mon, 14 Apr 2014 22:29:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.66.6 with HTTP; Mon, 14 Apr 2014 22:29:19 -0700 (PDT)
In-Reply-To: <CAJkfFBzs6JMxGSePJ6-1_=kLZRwwgwEPBD_tnh8qXPKQCmSMPA@mail.gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <CADnDZ8-DWU3ZE_WZO3vwBWvYtNZacdN9mDUof0jmfu2uKZ2poQ@mail.gmail.com> <534CB08A.8080802@meetinghouse.net> <CAJkfFBzs6JMxGSePJ6-1_=kLZRwwgwEPBD_tnh8qXPKQCmSMPA@mail.gmail.com>
From: Seth Johnson <seth.p.johnson@gmail.com>
Date: Tue, 15 Apr 2014 01:29:19 -0400
Message-ID: <CAJkfFBzpVCX0KgXhid1W5JXbuUivgydnYYttPD_pB+FFxKvgww@mail.gmail.com>
Subject: Re: What I've been wondering about the DMARC problem
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=047d7b66f5fb4af32e04f70e17a8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/duJKfOKciMb_lJDLSzSPHkwAqxw
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 05:30:08 -0000

--047d7b66f5fb4af32e04f70e17a8
Content-Type: text/plain; charset=UTF-8

(one insert/correction inline)

On Tue, Apr 15, 2014 at 1:20 AM, Seth Johnson <seth.p.johnson@gmail.com>wrote:

> The framework internationally is different.  Within free countries,
> there's a culture of expectations that certain things will be unacceptable,
> or will be resisted by self-respecting citizens.  That culture is based in
> a system that guards fundamental liberties, and people are able to rely on
> it to do so, though for private firms the limits aren't so definitive as
> they are for the government.
>
> Internationally, the limits are no longer so definitive, and that's
> because even though governments will sign onto instruments like the UDHR,
> those rights are not actually fundamental, even if we call them that.
> Fundamental rights have an undeniable priority within countries where they
> have been claimed in the founding act.  On that foundation, judges are
> always obliged to assess fundamental rights in light of the unarguable fact
> that their priority over the government was part of the original creation
> of the whole system.  There's no founding act in the international arena
> that sets the priority of people over the governments of the world, so
> rights are actually at the indulgence of governments, and governments can
> always assert their state interests are so important that they warrant
> impinging on fundamental liberties.
>
> We just saw an example of this with the Snowden disclosures.  We've been
> through a long period where we couldn't get our government to actually do
> much for us, or conversely to not invade our liberties -- because the
> claims that the government was snooping pervasively were kept marginal in
> various ways.
>

<fixed>

> But once documentation moved those considerations out of the frame of
> "conspiracy" or zealotry by activist organizations, we suddenly began
> seeing the appeals work again: "that's not the kind of country we are, what
> we set up for ourselves," we started saying again.
>
</fixed>

(eom)


> And while it's still in a bit of denial, we are seeing a gradual grudging
> retracting -- again, because the basis in fundamental liberties is
> unarguably related to how we set the government up in the founding act(s).
>
> This is for governments and the more definitive relationship between
> fundamental liberties and the government; that is, that they are limits on
> the government.  The judicial system treats fundamental rights violations
> by the government in terms of "strict scrutiny," which means a governmental
> act that impinges on fundamental liberties must serve a compelling state
> interest, and even then, must be narrowly tailored.  For private parties,
> it's more that the working system creates a culture of people who enjoy
> this ability to live in a system where these limits on the government are
> actually at play -- and that's a context that more easily supports
> attitudes of resistance and pushback from people who see their dignity
> invaded by private firms that do excessive things.
>
> None of this exists internationally.  The best you can place some faint
> hope in is that national/state interests will be "balanced" against rights
> expressed in a treaty.  That's a totally different standard from strict
> scrutiny.  And relying on even that is unrealistic, because governments
> have the "epistemic priority" -- and so they often, quite freely, simply
> claim their sovereignty and act according to what they claim is an
> important state interest.  They simply have that wherewithal at the
> international level.
>
> All of which is preface to say that the result is that governments and
> private parties (and corporations, who have concocted trans-state "rights"
> through judges acting to fill in gaps in the law over the years) know the
> rules don't apply the same way in the international arena.
>
> In fact, given the transitions currently being attempted, whether with the
> IANA functions or "Internet governance" more generally, Yahoo's DMARC
> behavior may really be a sort of dry run, testing the ability to take
> advantage of the moves to put concerns related to the operation of the
> Internet into an international frame, which folks are pushing for without
> really recognizing what's missing in that context, what they have sort of
> unconsciously relied on and taken for granted within systems of checks and
> balances that are rooted solidly at national levels.
>
> The checks and balances don't work the same internationally, and that
> circumstance can be exploited (and is, all the time, these days).
>
> People might push back, but they don't really do so with the same sense of
> fundamental recourse assured by a solidly rooted system.  And Yahoo knows
> this.  And we're just shoring that up by saying we can just switch
> multistakeholderism to the international arena.
>
> (All of this is aside from other factors not generally acknowledged --
> that there are actually inter-governmentally endorsed frames in place that
> will have a bearing on IANA type functions or domain names (Names, Numbers,
> Addresses and Identifiers/NNAI, in the ITU parlance), regardless of the
> fact the IANA transition defines itself as non-governmentally-led or
> inter-governmental.  Looking at this in that light, Yahoo may be forcing
> the creation of a context in which it can start to exercise those
> frameworks.)
>
>
> Seth
>
>
> On Tue, Apr 15, 2014 at 12:07 AM, Miles Fidelman <
> mfidelman@meetinghouse.net> wrote:
>
>> Important business users, with Yahoo accounts?  Is that a joke?
>>
>> Just as a reference point:
>> - I just logged into my long-unused, and un-publicized yahoo email
>> account - and the only thing there is Spam
>> - the lion's share of mail that comes from yahoo, to my normal account,
>> is spam
>> - unfortunately, a good number of people on the email lists that I run
>> seem to have Yahoo mail accounts - and a good amount of the mail that comes
>> from those accounts is... you guessed it... spam - because yahoo email
>> accounts seem to be vulnerable to cracking and exploitation
>>
>> So, just who is it that Yahoo is protecting here?
>>
>>
>> Abdussalam Baryun wrote:
>>
>>> The standard procedure in many companies is business scoped, so they
>>> identify important business users and the business returns/damages. Most
>>> important users are not IT experts, and use email for personal exchange.
>>> Yahoo has signed an agreement with users to protect its information system,
>>> so all seem to follow that, and all users are free to stop using services
>>> or not.
>>>
>>> AB
>>>
>>> On Tuesday, April 15, 2014, Brian E Carpenter wrote:
>>>
>>>     I thought that standard operating procedure in the IT industry
>>>     was: if you roll something out and it causes serious breakage to
>>>     some of your users, you roll it back as soon as possible.
>>>
>>>     Why hasn't Yahoo rolled back its 'reject' policy by now?
>>>
>>>     Regards
>>>        Brian
>>>
>>>
>>
>> --
>> In theory, there is no difference between theory and practice.
>> In practice, there is.   .... Yogi Berra
>>
>>
>

--047d7b66f5fb4af32e04f70e17a8
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">(one insert/correction inline)<=
br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, =
Apr 15, 2014 at 1:20 AM, Seth Johnson <span dir=3D"ltr">&lt;<a href=3D"mail=
to:seth.p.johnson@gmail.com" target=3D"_blank">seth.p.johnson@gmail.com</a>=
&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><div><div><d=
iv><div>The framework internationally is different.=C2=A0 Within free count=
ries, there&#39;s a culture of expectations that certain things will be una=
cceptable, or will be resisted by self-respecting citizens.=C2=A0 That cult=
ure is based in a system that guards fundamental liberties, and people are =
able to rely on it to do so, though for private firms the limits aren&#39;t=
 so definitive as they are for the government.<br>



<br></div>Internationally, the limits are no longer so definitive, and that=
&#39;s because even though governments will sign onto instruments like the =
UDHR, those rights are not actually fundamental, even if we call them that.=
=C2=A0 Fundamental rights have an undeniable priority within countries wher=
e they have been claimed in the founding act.=C2=A0 On that foundation, jud=
ges are always obliged to assess fundamental rights in light of the unargua=
ble fact that their priority over the government was part of the original c=
reation of the whole system.=C2=A0 There&#39;s no founding act in the inter=
national arena that sets the priority of people over the governments of the=
 world, so rights are actually at the indulgence of governments, and govern=
ments can always assert their state interests are so important that they wa=
rrant impinging on fundamental liberties.<br>



<br>We just saw an example of this with the Snowden disclosures.=C2=A0 We&#=
39;ve been through a long period where we couldn&#39;t get our government t=
o actually do much for us, or conversely to not invade our liberties -- bec=
ause the claims that the government was snooping pervasively were kept marg=
inal in various ways.</div>

</div></div></div></div></div></div></blockquote><div><br></div><div>&lt;fi=
xed&gt; <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div=
>
<div>
<div><div><div>But once documentation moved those considerations out of the=
 frame of &quot;conspiracy&quot; or zealotry by activist organizations, we =
suddenly began seeing the appeals work again: &quot;that&#39;s not the kind=
 of country we are, what we set up for ourselves,&quot; we started saying a=
gain.</div>

</div></div></div></div></div></div></blockquote><div>&lt;/fixed&gt;<br></d=
iv><div><br></div><div>(eom)<br></div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">

<div dir=3D"ltr"><div><div><div><div><div><div>And while it&#39;s still in =
a bit of denial, we are seeing a gradual grudging retracting -- again, beca=
use the basis in fundamental liberties is unarguably related to how we set =
the government up in the founding act(s).<br>



<br></div>This is for governments and the more definitive relationship betw=
een fundamental liberties and the government; that is, that they are limits=
 on the government.=C2=A0 The judicial system treats fundamental rights vio=
lations by the government in terms of &quot;strict scrutiny,&quot; which me=
ans a governmental act that impinges on fundamental liberties must serve a =
compelling state interest, and even then, must be narrowly tailored.=C2=A0 =
For private parties, it&#39;s more that the working system creates a cultur=
e of people who enjoy this ability to live in a system where these limits o=
n the government are actually at play -- and that&#39;s a context that more=
 easily supports attitudes of resistance and pushback from people who see t=
heir dignity invaded by private firms that do excessive things.<br>



<br></div>None of this exists internationally.=C2=A0 The best you can place=
 some faint hope in is that national/state interests will be &quot;balanced=
&quot; against rights expressed in a treaty.=C2=A0 That&#39;s a totally dif=
ferent standard from strict scrutiny.=C2=A0 And relying on even that is unr=
ealistic, because governments have the &quot;epistemic priority&quot; -- an=
d so they often, quite freely, simply claim their sovereignty and act accor=
ding to what they claim is an important state interest.=C2=A0 They simply h=
ave that wherewithal at the international level.<br>


<br></div>All of which is preface to say that the result is that government=
s and private parties (and corporations, who have concocted trans-state &qu=
ot;rights&quot; through judges acting to fill in gaps in the law over the y=
ears) know the rules don&#39;t apply the same way in the international aren=
a.<br>


<br></div>In fact, given the transitions currently being attempted, whether=
 with the IANA functions or &quot;Internet governance&quot; more generally,=
 Yahoo&#39;s DMARC behavior may really be a sort of dry run, testing the ab=
ility to take advantage of the moves to put concerns related to the operati=
on of the Internet into an international frame, which folks are pushing for=
 without really recognizing what&#39;s missing in that context, what they h=
ave sort of unconsciously relied on and taken for granted within systems of=
 checks and balances that are rooted solidly at national levels.<br>


<br>The checks and balances don&#39;t work the same internationally, and th=
at circumstance can be exploited (and is, all the time, these days).<br><br=
></div>People might push back, but they don&#39;t really do so with the sam=
e sense of fundamental recourse assured by a solidly rooted system.=C2=A0 A=
nd Yahoo knows this.=C2=A0 And we&#39;re just shoring that up by saying we =
can just switch multistakeholderism to the international arena.<br>


<br></div>(All of this is aside from other factors not generally acknowledg=
ed -- that there are actually inter-governmentally endorsed frames in place=
 that will have a bearing on IANA type functions or domain names (Names, Nu=
mbers, Addresses and Identifiers/NNAI, in the ITU parlance), regardless of =
the fact the IANA transition defines itself as non-governmentally-led or in=
ter-governmental.=C2=A0 Looking at this in that light, Yahoo may be forcing=
 the creation of a context in which it can start to exercise those framewor=
ks.)<span class=3D"HOEnZb"><font color=3D"#888888"><br>


<div><div><div><div><br><br></div><div>Seth
</div></div></div></div></font></span></div><div class=3D"HOEnZb"><div clas=
s=3D"h5"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On T=
ue, Apr 15, 2014 at 12:07 AM, Miles Fidelman <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank">mfidelman@meetingh=
ouse.net</a>&gt;</span> wrote:<br>


<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Important business users, with Yahoo account=
s? =C2=A0Is that a joke?<br>
<br>
Just as a reference point:<br>
- I just logged into my long-unused, and un-publicized yahoo email account =
- and the only thing there is Spam<br>
- the lion&#39;s share of mail that comes from yahoo, to my normal account,=
 is spam<br>
- unfortunately, a good number of people on the email lists that I run seem=
 to have Yahoo mail accounts - and a good amount of the mail that comes fro=
m those accounts is... you guessed it... spam - because yahoo email account=
s seem to be vulnerable to cracking and exploitation<br>



<br>
So, just who is it that Yahoo is protecting here?<div><div><br>
<br>
Abdussalam Baryun wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The standard procedure in many companies is business scoped, so they identi=
fy important business users and the business returns/damages. Most importan=
t users are not IT experts, and use email for personal exchange. Yahoo has =
signed an agreement with users to protect its information system, so all se=
em to follow that, and all users are free to stop using services or not.<br=
>



<br>
AB<br>
<br>
On Tuesday, April 15, 2014, Brian E Carpenter wrote:<br>
<br>
=C2=A0 =C2=A0 I thought that standard operating procedure in the IT industr=
y<br>
=C2=A0 =C2=A0 was: if you roll something out and it causes serious breakage=
 to<br>
=C2=A0 =C2=A0 some of your users, you roll it back as soon as possible.<br>
<br>
=C2=A0 =C2=A0 Why hasn&#39;t Yahoo rolled back its &#39;reject&#39; policy =
by now?<br>
<br>
=C2=A0 =C2=A0 Regards<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Brian<br>
<br>
</blockquote>
<br>
<br></div></div><div><div>
-- <br>
In theory, there is no difference between theory and practice.<br>
In practice, there is. =C2=A0 .... Yogi Berra<br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div></div>

--047d7b66f5fb4af32e04f70e17a8--


From nobody Mon Apr 14 22:57:52 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E98F1A0346 for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 22:57:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 hIJbsop9vFzs for <ietf@ietfa.amsl.com>; Mon, 14 Apr 2014 22:57:44 -0700 (PDT)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.166]) by ietfa.amsl.com (Postfix) with ESMTP id 34CA71A0784 for <ietf@ietf.org>; Mon, 14 Apr 2014 22:57:44 -0700 (PDT)
Received: from [195.245.230.131:28127] by server-6.bemta-3.messagelabs.com id 09/9D-00470-45ACC435; Tue, 15 Apr 2014 05:57:40 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-78.messagelabs.com!1397541459!25093556!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14059 invoked from network); 15 Apr 2014 05:57:39 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-9.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 15 Apr 2014 05:57:39 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.14]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Tue, 15 Apr 2014 06:57:39 +0100
From: <l.wood@surrey.ac.uk>
To: <mfidelman@meetinghouse.net>
Date: Tue, 15 Apr 2014 06:57:37 +0100
Subject: RE: What I've been wondering about the DMARC problem
Thread-Topic: What I've been wondering about the DMARC problem
Thread-Index: Ac9YYFN7CmyFLHtJRIKL2CvC9tIWZAADoQVO
Message-ID: <290E20B455C66743BE178C5C84F1240847E88E3F8D@EXMB01CMS.surrey.ac.uk>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <CADnDZ8-DWU3ZE_WZO3vwBWvYtNZacdN9mDUof0jmfu2uKZ2poQ@mail.gmail.com>, <534CB08A.8080802@meetinghouse.net>
In-Reply-To: <534CB08A.8080802@meetinghouse.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-B5g-EmLDyyumHGF_4nbQQa3jJo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 05:57:49 -0000

> Important business users, with Yahoo accounts?  Is that a joke?

If you've ever done business in the third world, you will find
that government officials use e.g. Yahoo accounts, because
they're more reliable than their local provider, and, unlike the
local provider, aren't spamblocked.

Yes, this makes telling the actual government officials from the
fraudsters pretending to be government officials a bit more work -
personal relationships, introductions, and whatnot.

Lloyd Wood
http://about.me/lloydwood


From nobody Tue Apr 15 00:42:22 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29DDF1A031D for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 00:42:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.521
X-Spam-Level: 
X-Spam-Status: No, score=0.521 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 0HMv5dqPyEyp for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 00:42:15 -0700 (PDT)
Received: from mail-oa0-x234.google.com (mail-oa0-x234.google.com [IPv6:2607:f8b0:4003:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 3D8CA1A019D for <ietf@ietf.org>; Tue, 15 Apr 2014 00:42:15 -0700 (PDT)
Received: by mail-oa0-f52.google.com with SMTP id l6so10456340oag.11 for <ietf@ietf.org>; Tue, 15 Apr 2014 00:42:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xkXiHdfovNU76aAHJpVO8sn6fdE4Knp8o6mpWCJgmnI=; b=PbmfWdlULJ7yDbmA0DoQWwKNbn0Tl4Ld/cEdKUBOVW34R3arSqwt3a2JK3cRwE6z8m 2v71rGJwB62iUCJL3IcYrwtSLZUdhVgVsFMuPIVQAAF/rQYRwHbYjJuOs1IzqQhuy6do XmVuWfRAbjTPUzy3Q/c8Im1SdcTHNhNw2KwuU=
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:content-type; bh=xkXiHdfovNU76aAHJpVO8sn6fdE4Knp8o6mpWCJgmnI=; b=XsujIaXFbgkn5sqUfn77M557WOjQ9biDJwfbDPCqvR8DUipilY6mdLI82HCYX+pzHH 3AXkBfE0azFP+NYfdmfAr49YcnuCLqlukZjesMRuy9HjxcLaev/DH1PENwKAOAK0Mcx1 mnTFDF/EUDgI3vgnlHmwut3etJhfxtycX0EE5quMuHiZHyYTF8+cUXt6JVquc+pkKPut eQHAjvYEZWs7iuBnICakG7MkBm2Z5hxpNUHzkhQbz0FQPvLDWDhRQNzxoRDlhgPFUG36 xYAZjQH3/fRSS97Ptv9qSNnaTTtvDV0NFxGiyC24P2euWOXXD2ZYNAikZw7cg5Akvqat 0eog==
X-Gm-Message-State: ALoCoQlHixD8BQkILrxNJU84VhVKPdEdqn7fj9cf7xwurrIS/erO8vPsmtInc1r8rDFOvEImOKfH
MIME-Version: 1.0
X-Received: by 10.182.24.69 with SMTP id s5mr158268obf.35.1397547732240; Tue, 15 Apr 2014 00:42:12 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Tue, 15 Apr 2014 00:42:12 -0700 (PDT)
In-Reply-To: <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com>
Date: Tue, 15 Apr 2014 08:42:12 +0100
Message-ID: <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Dave Cridland <dave@cridland.net>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2a20c231f6b04f70ff0d1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AVfPZ95QfanxD5OdOew-wCzzhoI
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 07:42:19 -0000

--001a11c2a20c231f6b04f70ff0d1
Content-Type: text/plain; charset=UTF-8

On 15 April 2014 01:11, Murray S. Kucherawy <superuser@gmail.com> wrote:

> On Mon, Apr 14, 2014 at 3:02 PM, Dave Cridland <dave@cridland.net> wrote:
>
>> One of the very specific items that was on the proposed charter was
>>> dealing with the question of how to integrate DMARC with mailing lists.
>>> This was called out very early on as an open issue, as were some other
>>> important ones:
>>>
>>> http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC
>>>
>>
>> Right, but the WG was expected to make it work with mailing lists without
>> changing it. Tough ask.
>>
>
> Could it not have been done as an extension?  And as I recall, one of the
> proposed paths was to just record and publish DMARC as it is now, and then
> get a WG going to help revise it into something that also resolves the
> questions in the proposed charter, on the standards track.  This also
> failed to gain acceptance.
>

An "incremental and optional" extension which would not require changes to
the deployed software and operational practises. You want an optional
extension which would optionally allow DMARC to traverse mailing lists
usefully when it's optionally deployed? Good one. Can I base it off ACAP?

In fact, I can't find any evidence for willingness to let go of change
control. The closest I can find is a year and a day ago, when you said:

"I'm pretty sure the intent is to publish the current base draft through
the ISE, since it was developed outside the IETF, but if it changes (via
rechartering), move it to the IETF stream.  The latter can obsolete the
former if the timing warrants doing so.  Thus, if the working group is ever
actually cracking open the base draft, it's on the IETF stream."

Note, that's "via rechartering", so the WG was not initially chartered to
change the base spec. The actual proposed charter says it could recharter
in extremis, but that's after two paragraphs explaining why it shouldn't.


>
>
>> Sorry, but given the way in which IETF participants were asked to work on
>> DMARC, there is absolutely no way you could say that the "DMARC people came
>> to the IETF to [...] complete development" - it was more or less stated
>> that development was done and dusted - and the IETF didn't reject it on the
>> basis that no engineering work remained - the DMARC people rejected any
>> engineering work happening.
>>
>> It doesn't actually matter whether you think the reasons behind this were
>> valid; the fact is that you're putting one heck of a slant on recent
>> history, and it's not borne out by what's in the archives.
>>
>
> I remember what was said.  I'm not trying to be revisionist here.  Rather,
> I think I'm trying to remember all the details of a very chaotic
> negotiation.
>
>
Go read the archives. Refresh your memory.


> I can't say I blame the DMARC people, or anyone for that matter, for
> trying to insulate itself against its work being bogged down for months or
> longer rat-holing on things as has been the fate of so many past efforts in
> the same area.  (See the thread Wes George started this morning
> separately.)  Maybe they tried too hard and maybe I even contributed.  But
> I also think maybe the IETF needs to rethink its position on taking on work
> from outside organizations in the first place, which was one of several
> road blocks that came up.  Another is that it was too far along the
> deployment axis to be eligible for consideration as new IETF work,
> regardless of whether the main document was up for revision.  Yet another
> is that despite repeated requests, we couldn't even more than a couple of
> people (I can remember four) to submit substantive reviews of the current
> document; it seemed like the IETF wasn't interested regardless of the other
> "regulatory" issues.
>
>
It's hard to be interested in doing IETF work on something that wasn't
managed by IETF process, or IPR rules, and was actively marketed as being
done, deployed, and not subject to further change. "Please review our
specification so we can ignore your comments and rubber stamp the result"
is not a tremendously attractive proposition.

I suspect that had the IETF been involved considerably earlier, none of
this would have happened. I'm not really sure how this could have been
fixed, as I've noticed a strong tendency amongst organisations which
control large proportions of the deployed market to assume that minority
viewpoints do not count. The "60% of all mailboxes" fanfare is an example
of this. I've seen similar from browser vendors in WebSocket, and I've no
doubt that the major router vendors play the same card with BGP et al.

Some of this is understandable - expertise and experience do tend to pool
at such organisations - but increasingly I feel that we've lost sight,
somewhere, that - for example - because 60% of the world's mailboxes are
handled by the DMARC cabal, that still leaves 40% who may have somewhat
different needs and requirements from the protocol. Given the expense and
difficulty of IETF participation for smaller organisations and individuals,
it's hard for them to club together and stand up to the 8000lb gorillas.

DMARC is not an IETF standard - you know this, I realise - but there was no
sense from the messages exchanged a year ago that it ever would be an IETF
product in anything more than - perhaps - name.


> I don't have any idea how to retroactively fix all of that, and I suspect
> it would be another rat-hole to try.  What I'd really like to talk about is
> where we go from here.
>
>
It really depends on whether the 8000lb gorillas are open to letting go of
the change control or not. A year ago they clearly weren't.

Dave.

--001a11c2a20c231f6b04f70ff0d1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
5 April 2014 01:11, Murray S. Kucherawy <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div class=3D"">On Mon, Apr 14, 2014 at 3=
:02 PM, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"mailto:dave@cridland=
.net" target=3D"_blank">dave@cridland.net</a>&gt;</span> wrote:<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D""=
>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">
<div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:so=
lid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
></div><div>One of the very specific items that was on the proposed charter=
 was dealing with the question of how to integrate DMARC with mailing lists=
.=C2=A0 This was called out very early on as an open issue, as were some ot=
her important ones:<br>



<br><a href=3D"http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC" targe=
t=3D"_blank">http://wiki.tools.ietf.org/wg/appsawg/trac/wiki/DMARC</a><span=
><font color=3D"#888888"><br></font></span></div></div></div>
</div></blockquote><div><br></div></div><div>Right, but the WG was expected=
 to make it work with mailing lists without changing it. Tough ask.</div></=
div></div></div></blockquote><div><br></div></div><div>Could it not have be=
en done as an extension?=C2=A0 And as I recall, one of the proposed paths w=
as to just record and publish DMARC as it is now, and then get a WG going t=
o help revise it into something that also resolves the questions in the pro=
posed charter, on the standards track.=C2=A0 This also failed to gain accep=
tance.<br>

</div></div></div></div></blockquote><div><br></div><div>An &quot;increment=
al and optional&quot; extension which would not require changes to the depl=
oyed software and operational practises. You want an optional extension whi=
ch would optionally allow DMARC to traverse mailing lists usefully when it&=
#39;s optionally deployed? Good one. Can I base it off ACAP?</div>
<div><br></div><div>In fact, I can&#39;t find any evidence for willingness =
to let go of change control. The closest I can find is a year and a day ago=
, when you said:</div><div><br></div><div>&quot;<span style=3D"font-family:=
arial,sans-serif;font-size:13px">I&#39;m pretty sure the intent is to publi=
sh the current base draft through the ISE, since it was developed outside t=
he IETF, but if it changes (via rechartering), move it to the IETF stream.=
=C2=A0 The latter can obsolete the former if the timing warrants doing so.=
=C2=A0 Thus, if the working group is ever actually cracking open the base d=
raft, it&#39;s on the IETF stream.&quot;</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span=
></div><div><span style=3D"font-family:arial,sans-serif;font-size:13px">Not=
e, that&#39;s &quot;via rechartering&quot;, so the WG was not initially cha=
rtered to change the base spec. The actual proposed charter says it could r=
echarter in extremis, but that&#39;s after two paragraphs explaining why it=
 shouldn&#39;t.</span></div>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote">
<div>=C2=A0<br></div><div class=3D""><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(2=
04,204,204);border-left-style:solid;padding-left:1ex"><div dir=3D"ltr"><div=
 class=3D"gmail_extra">
Sorry, but given the way in which IETF participants were asked to work on D=
MARC, there is absolutely no way you could say that the &quot;DMARC people =
came to the IETF to [...] complete development&quot; - it was more or less =
stated that development was done and dusted - and the IETF didn&#39;t rejec=
t it on the basis that no engineering work remained - the DMARC people reje=
cted any engineering work happening.<div class=3D"gmail_quote">


<div><br></div><div>It doesn&#39;t actually matter whether you think the re=
asons behind this were valid; the fact is that you&#39;re putting one heck =
of a slant on recent history, and it&#39;s not borne out by what&#39;s in t=
he archives.</div>

</div></div></div></blockquote><div><br></div></div><div>I remember what wa=
s said.=C2=A0 I&#39;m not trying to be revisionist here.=C2=A0 Rather, I th=
ink I&#39;m trying to remember all the details of a very chaotic negotiatio=
n.<br>
<br></div></div></div></div></blockquote><div><br></div><div>Go read the ar=
chives. Refresh your memory.</div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-le=
ft-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
></div>
<div>I can&#39;t say I blame the DMARC people, or anyone for that matter, f=
or trying to insulate itself against its work being bogged down for months =
or longer rat-holing on things as has been the fate of so many past efforts=
 in the same area.=C2=A0 (See the thread Wes George started this morning se=
parately.)=C2=A0 Maybe they tried too hard and maybe I even contributed.=C2=
=A0 But I also think maybe the IETF needs to rethink its position on taking=
 on work from outside organizations in the first place, which was one of se=
veral road blocks that came up.=C2=A0 Another is that it was too far along =
the deployment axis to be eligible for consideration as new IETF work, rega=
rdless of whether the main document was up for revision.=C2=A0 Yet another =
is that despite repeated requests, we couldn&#39;t even more than a couple =
of people (I can remember four) to submit substantive reviews of the curren=
t document; it seemed like the IETF wasn&#39;t interested regardless of the=
 other &quot;regulatory&quot; issues.<br>

<br></div></div></div></div></blockquote><div><br></div><div>It&#39;s hard =
to be interested in doing IETF work on something that wasn&#39;t managed by=
 IETF process, or IPR rules, and was actively marketed as being done, deplo=
yed, and not subject to further change. &quot;Please review our specificati=
on so we can ignore your comments and rubber stamp the result&quot; is not =
a tremendously attractive proposition.</div>
<div><br></div><div>I suspect that had the IETF been involved considerably =
earlier, none of this would have happened. I&#39;m not really sure how this=
 could have been fixed, as I&#39;ve noticed a strong tendency amongst organ=
isations which control large proportions of the deployed market to assume t=
hat minority viewpoints do not count. The &quot;60% of all mailboxes&quot; =
fanfare is an example of this. I&#39;ve seen similar from browser vendors i=
n WebSocket, and I&#39;ve no doubt that the major router vendors play the s=
ame card with BGP et al.</div>
<div><br></div><div>Some of this is understandable - expertise and experien=
ce do tend to pool at such organisations - but increasingly I feel that we&=
#39;ve lost sight, somewhere, that - for example - because 60% of the world=
&#39;s mailboxes are handled by the DMARC cabal, that still leaves 40% who =
may have somewhat different needs and requirements from the protocol. Given=
 the expense and difficulty of IETF participation for smaller organisations=
 and individuals, it&#39;s hard for them to club together and stand up to t=
he 8000lb gorillas.</div>
<div><br></div><div>DMARC is not an IETF standard - you know this, I realis=
e - but there was no sense from the messages exchanged a year ago that it e=
ver would be an IETF product in anything more than - perhaps - name.</div>
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-l=
eft-style:solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extr=
a"><div class=3D"gmail_quote">
<div>I don&#39;t have any idea how to retroactively fix all of that, and I =
suspect it would be another rat-hole to try.=C2=A0 What I&#39;d really like=
 to talk about is where we go from here.<span class=3D""><font color=3D"#88=
8888"><br>
<br></font></span></div></div></div></div></blockquote><div><br></div><div>=
It really depends on whether the 8000lb gorillas are open to letting go of =
the change control or not. A year ago they clearly weren&#39;t.</div><div>
<br></div><div>Dave.</div></div></div></div>

--001a11c2a20c231f6b04f70ff0d1--


From nobody Tue Apr 15 00:52:38 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C264E1A0681 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 00:52:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.606
X-Spam-Level: 
X-Spam-Status: No, score=0.606 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 sqOAIWockQs7 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 00:52:32 -0700 (PDT)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 14A1B1A031D for <ietf@ietf.org>; Tue, 15 Apr 2014 00:52:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1397548348; bh=U9U2/C+8TxEx3yYxy1Gb0gr5U4Rr7xXscNUIkCRq9PM=; l=2924; h=Date:From:To:CC:References:In-Reply-To; b=UB1gJSQdUpwc1VZupDig0RJiSJt+OO4HKyLIGx6iaBYVpe9fhlKaEXujQKBZs5N80 3QA26jZT2IuFaOFWk8NWmOHTetb103DdgjIZ4zvu39/DFeUPH1gqGCYTWjZ9yPRWCy wKouccZjz36dVGFinFaceQ+MKBfjfGjJQvt+YUp4=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Tue, 15 Apr 2014 09:52:28 +0200 id 00000000005DC035.00000000534CE53C.000012C2
Message-ID: <534CE53A.7090000@tana.it>
Date: Tue, 15 Apr 2014 09:52:26 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: Hector Santos <hsantos@isdg.net>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan> <5347C698.6040108@tana.it> <534ACB5F.7060400@isdg.net>
In-Reply-To: <534ACB5F.7060400@isdg.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LnEdzBPJBCaafi5ZWLjQIh4YlOg
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 07:52:36 -0000

On Sun 13/Apr/2014 19:37:35 +0200 Hector Santos wrote:
> On 4/11/2014 6:40 AM, Alessandro Vesely wrote:> On Tue 08/Apr/2014
> 19:34:35 +0200 John R Levine wrote:
>>>
>>> Just today I did modify it so that any list mail with a From: address
>>> @yahoo.com is re written to @yahoo.com.INVALID.  That's the least
>>> intrusive way I've been able to come up with to mitigate the damage.
>>
>> Fair enough.  I've copied that suggestion to
>> http://en.wikipedia.org/wiki/DMARC#Human_policy
>> Please feel free to amend that page at your leisure.
>>
> 
> Hi Alessandro,
> 
> You added (I presume):
> 
>    According to John Levine, a well known mail expert, the least
>    intrusive way to mitigate the damage would be to rewrite the
>    From: address in a predictable, comprehensible manner, such as
>    the following:
> 
> It may be the "quickest" way, but I would consider this the most
> intrusive and even email damaging, extremely harmful suggestion to
> electronic mail communications.

Ok, I added "temporarily", so it now reads:

   Various workarounds have been proposed to cope with domains that
   publish strict policies unwittingly. For example, a mailing list
   manager should reject posts from authors who use problematic email
   domains. The latter behavior is the most respectful the
   communication protocols as well as the domain owner's will.
   However, it might cause inconveniences in the face of sudden
   policy changes. According to John Levine, a well known mail
   expert, the least intrusive way to temporarily mitigate the damage
   would be to rewrite the From: address in a predictable,
   comprehensible manner, such as the following:

In the preceding "History" section, I appended:

   In April 2014, Yahoo changed its DMARC policy to p=reject, thereby
   causing misbehavior in several mailing lists.[6] DMARC is not yet
   a standard protocol, and currently misses a provision for such
   sudden changes.

Is that more acceptable?

> [...]
> So this is a "integration" issue.  Honestly, the changes are not too
> difficult and IMO, it is far less intrusive than changing the 5322.From.
> 
> 1) When a new subscriber applies to a list, check for restrictive
> domain policies. Deny subscribers and explain why in the notification
> message.
> 
> 2) Check for restrictive domains in list mail submissions.
> 
> The first one is the piece a cake.

Yes

> The 2nd one can be more complex
> due to the wider number of software things to do here.
> 
> 2a) Dynamic SMTP check, reject (55x) the message with policy reason.
> 
> 2b) Accept message and send a "no access" notification message.
> Explain why.
> 
> 2c) During the redesign software change, write a one time membership
> scanner to remove restrictive domain members. Send email notification
> explaining why.

I think (2c) has to be done politely, in order to allow people the
time to react adequately.

Ale


From nobody Tue Apr 15 04:37:18 2014
Return-Path: <seth.p.johnson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0DD11A03CA for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 04:37:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.701
X-Spam-Level: 
X-Spam-Status: No, score=0.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 FatqS2IR6YzO for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 04:37:09 -0700 (PDT)
Received: from mail-vc0-x22c.google.com (mail-vc0-x22c.google.com [IPv6:2607:f8b0:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 45F9D1A02B2 for <ietf@ietf.org>; Tue, 15 Apr 2014 04:37:09 -0700 (PDT)
Received: by mail-vc0-f172.google.com with SMTP id la4so9173218vcb.3 for <ietf@ietf.org>; Tue, 15 Apr 2014 04:37:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=doXUhewJD52EcX8X6D96EFqCbHBsYl8kwHpVz0Tp4zM=; b=GTmA+lnHWqj1Qc3CGC7MpcpZMcveBypDcR+AM6PC8nQJqj221TbdOmtc5Q6SmLkVqx 7MThJr8GcTcfy8WkMZfAhTzhuQFG4UpCSuLd3i4DjPmw1LOz123nTAN+FcvzJEt+CE1e xC7qRNAM53KPdIkmsJvC/gJpcoiWKX0vfsfdH3/TfNCAdl54hsWAqRZbs7t1xwzSn8JE aJrWsDXj5A7ETOHyFmorAv2hKtORZx7ZBV7eBd25SmpswZ9ZcDN7WCo1pfl5YqOT/lzA dUugnA0buDVz/CCI9uSa0AdkodoSEchA7MlN5lJxsHMnZcM6pJYwfhI42ON+jysjPvUS bfWw==
X-Received: by 10.52.6.162 with SMTP id c2mr826983vda.6.1397561826218; Tue, 15 Apr 2014 04:37:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.66.6 with HTTP; Tue, 15 Apr 2014 04:36:25 -0700 (PDT)
In-Reply-To: <CAJkfFBzpVCX0KgXhid1W5JXbuUivgydnYYttPD_pB+FFxKvgww@mail.gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <CADnDZ8-DWU3ZE_WZO3vwBWvYtNZacdN9mDUof0jmfu2uKZ2poQ@mail.gmail.com> <534CB08A.8080802@meetinghouse.net> <CAJkfFBzs6JMxGSePJ6-1_=kLZRwwgwEPBD_tnh8qXPKQCmSMPA@mail.gmail.com> <CAJkfFBzpVCX0KgXhid1W5JXbuUivgydnYYttPD_pB+FFxKvgww@mail.gmail.com>
From: Seth Johnson <seth.p.johnson@gmail.com>
Date: Tue, 15 Apr 2014 07:36:25 -0400
Message-ID: <CAJkfFBycRLckXVmYRQ=TzGHyu9KOnh81okqgHfoW5SFZYC2vTA@mail.gmail.com>
Subject: Re: What I've been wondering about the DMARC problem
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=20cf30334739341b8d04f71338dd
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uiBdqkQGa4Fsp0ItmHILgSkVJ3U
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 11:37:15 -0000

--20cf30334739341b8d04f71338dd
Content-Type: text/plain; charset=UTF-8

Jimmy Wales is, perhaps partially unconsciously, referencing this with his
point on a "culture of free expression."

Note: I am not implying in making these observations that stewardship
should be by any particular country, or any number less than the totality
for that matter -- only that we rely on systems that we have claimed for
the people to create such a context, and the international arena (and the
various systems so far presented for "checks and balances" or even simply
handoff to privatized systems to multistakeholder-ish processes that must
not be government-led or inter-governmental) does not presently support
that.


Seth


Seth


On Tue, Apr 15, 2014 at 1:29 AM, Seth Johnson <seth.p.johnson@gmail.com>wrote:

> (one insert/correction inline)
>
> On Tue, Apr 15, 2014 at 1:20 AM, Seth Johnson <seth.p.johnson@gmail.com>wrote:
>
>> The framework internationally is different.  Within free countries,
>> there's a culture of expectations that certain things will be unacceptable,
>> or will be resisted by self-respecting citizens.  That culture is based in
>> a system that guards fundamental liberties, and people are able to rely on
>> it to do so, though for private firms the limits aren't so definitive as
>> they are for the government.
>>
>> Internationally, the limits are no longer so definitive, and that's
>> because even though governments will sign onto instruments like the UDHR,
>> those rights are not actually fundamental, even if we call them that.
>> Fundamental rights have an undeniable priority within countries where they
>> have been claimed in the founding act.  On that foundation, judges are
>> always obliged to assess fundamental rights in light of the unarguable fact
>> that their priority over the government was part of the original creation
>> of the whole system.  There's no founding act in the international arena
>> that sets the priority of people over the governments of the world, so
>> rights are actually at the indulgence of governments, and governments can
>> always assert their state interests are so important that they warrant
>> impinging on fundamental liberties.
>>
>> We just saw an example of this with the Snowden disclosures.  We've been
>> through a long period where we couldn't get our government to actually do
>> much for us, or conversely to not invade our liberties -- because the
>> claims that the government was snooping pervasively were kept marginal in
>> various ways.
>>
>
> <fixed>
>
>>  But once documentation moved those considerations out of the frame of
>> "conspiracy" or zealotry by activist organizations, we suddenly began
>> seeing the appeals work again: "that's not the kind of country we are, what
>> we set up for ourselves," we started saying again.
>>
> </fixed>
>
> (eom)
>
>
>> And while it's still in a bit of denial, we are seeing a gradual grudging
>> retracting -- again, because the basis in fundamental liberties is
>> unarguably related to how we set the government up in the founding act(s).
>>
>> This is for governments and the more definitive relationship between
>> fundamental liberties and the government; that is, that they are limits on
>> the government.  The judicial system treats fundamental rights violations
>> by the government in terms of "strict scrutiny," which means a governmental
>> act that impinges on fundamental liberties must serve a compelling state
>> interest, and even then, must be narrowly tailored.  For private parties,
>> it's more that the working system creates a culture of people who enjoy
>> this ability to live in a system where these limits on the government are
>> actually at play -- and that's a context that more easily supports
>> attitudes of resistance and pushback from people who see their dignity
>> invaded by private firms that do excessive things.
>>
>> None of this exists internationally.  The best you can place some faint
>> hope in is that national/state interests will be "balanced" against rights
>> expressed in a treaty.  That's a totally different standard from strict
>> scrutiny.  And relying on even that is unrealistic, because governments
>> have the "epistemic priority" -- and so they often, quite freely, simply
>> claim their sovereignty and act according to what they claim is an
>> important state interest.  They simply have that wherewithal at the
>> international level.
>>
>> All of which is preface to say that the result is that governments and
>> private parties (and corporations, who have concocted trans-state "rights"
>> through judges acting to fill in gaps in the law over the years) know the
>> rules don't apply the same way in the international arena.
>>
>> In fact, given the transitions currently being attempted, whether with
>> the IANA functions or "Internet governance" more generally, Yahoo's DMARC
>> behavior may really be a sort of dry run, testing the ability to take
>> advantage of the moves to put concerns related to the operation of the
>> Internet into an international frame, which folks are pushing for without
>> really recognizing what's missing in that context, what they have sort of
>> unconsciously relied on and taken for granted within systems of checks and
>> balances that are rooted solidly at national levels.
>>
>> The checks and balances don't work the same internationally, and that
>> circumstance can be exploited (and is, all the time, these days).
>>
>> People might push back, but they don't really do so with the same sense
>> of fundamental recourse assured by a solidly rooted system.  And Yahoo
>> knows this.  And we're just shoring that up by saying we can just switch
>> multistakeholderism to the international arena.
>>
>> (All of this is aside from other factors not generally acknowledged --
>> that there are actually inter-governmentally endorsed frames in place that
>> will have a bearing on IANA type functions or domain names (Names, Numbers,
>> Addresses and Identifiers/NNAI, in the ITU parlance), regardless of the
>> fact the IANA transition defines itself as non-governmentally-led or
>> inter-governmental.  Looking at this in that light, Yahoo may be forcing
>> the creation of a context in which it can start to exercise those
>> frameworks.)
>>
>>
>> Seth
>>
>>
>> On Tue, Apr 15, 2014 at 12:07 AM, Miles Fidelman <
>> mfidelman@meetinghouse.net> wrote:
>>
>>> Important business users, with Yahoo accounts?  Is that a joke?
>>>
>>> Just as a reference point:
>>> - I just logged into my long-unused, and un-publicized yahoo email
>>> account - and the only thing there is Spam
>>> - the lion's share of mail that comes from yahoo, to my normal account,
>>> is spam
>>> - unfortunately, a good number of people on the email lists that I run
>>> seem to have Yahoo mail accounts - and a good amount of the mail that comes
>>> from those accounts is... you guessed it... spam - because yahoo email
>>> accounts seem to be vulnerable to cracking and exploitation
>>>
>>> So, just who is it that Yahoo is protecting here?
>>>
>>>
>>> Abdussalam Baryun wrote:
>>>
>>>> The standard procedure in many companies is business scoped, so they
>>>> identify important business users and the business returns/damages. Most
>>>> important users are not IT experts, and use email for personal exchange.
>>>> Yahoo has signed an agreement with users to protect its information system,
>>>> so all seem to follow that, and all users are free to stop using services
>>>> or not.
>>>>
>>>> AB
>>>>
>>>> On Tuesday, April 15, 2014, Brian E Carpenter wrote:
>>>>
>>>>     I thought that standard operating procedure in the IT industry
>>>>     was: if you roll something out and it causes serious breakage to
>>>>     some of your users, you roll it back as soon as possible.
>>>>
>>>>     Why hasn't Yahoo rolled back its 'reject' policy by now?
>>>>
>>>>     Regards
>>>>        Brian
>>>>
>>>>
>>>
>>> --
>>> In theory, there is no difference between theory and practice.
>>> In practice, there is.   .... Yogi Berra
>>>
>>>
>>
>

--20cf30334739341b8d04f71338dd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Jimmy Wales is, perhaps partially unconsciously, referenci=
ng this with his point on a &quot;culture of free expression.&quot;<div><br=
></div><div>Note: I am not implying in making these observations that stewa=
rdship should be by any particular country, or any number less than the tot=
ality for that matter -- only that we rely on systems that we have claimed =
for the people to create such a context, and the international arena (and t=
he various systems so far presented for &quot;checks and balances&quot; or =
even simply handoff to privatized systems to multistakeholder-ish processes=
 that must not be government-led or inter-governmental) does not presently =
support that.</div>

<div><br></div><div><br></div><div>Seth<br><div><br></div><div><br></div><d=
iv>Seth</div></div></div><div class=3D"gmail_extra"><br><br><div class=3D"g=
mail_quote">On Tue, Apr 15, 2014 at 1:29 AM, Seth Johnson <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:seth.p.johnson@gmail.com" target=3D"_blank">seth.p.j=
ohnson@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
(one insert/correction inline)<br></div><div class=3D"gmail_extra"><br><div=
 class=3D"gmail_quote">

<div class=3D"">On Tue, Apr 15, 2014 at 1:20 AM, Seth Johnson <span dir=3D"=
ltr">&lt;<a href=3D"mailto:seth.p.johnson@gmail.com" target=3D"_blank">seth=
.p.johnson@gmail.com</a>&gt;</span> wrote:<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div><div><div><=
div><div><div class=3D""><div>The framework internationally is different.=
=C2=A0 Within free countries, there&#39;s a culture of expectations that ce=
rtain things will be unacceptable, or will be resisted by self-respecting c=
itizens.=C2=A0 That culture is based in a system that guards fundamental li=
berties, and people are able to rely on it to do so, though for private fir=
ms the limits aren&#39;t so definitive as they are for the government.<br>




<br></div>Internationally, the limits are no longer so definitive, and that=
&#39;s because even though governments will sign onto instruments like the =
UDHR, those rights are not actually fundamental, even if we call them that.=
=C2=A0 Fundamental rights have an undeniable priority within countries wher=
e they have been claimed in the founding act.=C2=A0 On that foundation, jud=
ges are always obliged to assess fundamental rights in light of the unargua=
ble fact that their priority over the government was part of the original c=
reation of the whole system.=C2=A0 There&#39;s no founding act in the inter=
national arena that sets the priority of people over the governments of the=
 world, so rights are actually at the indulgence of governments, and govern=
ments can always assert their state interests are so important that they wa=
rrant impinging on fundamental liberties.<br>




<br></div>We just saw an example of this with the Snowden disclosures.=C2=
=A0 We&#39;ve been through a long period where we couldn&#39;t get our gove=
rnment to actually do much for us, or conversely to not invade our libertie=
s -- because the claims that the government was snooping pervasively were k=
ept marginal in various ways.</div>


</div></div></div></div></div></div></blockquote><div><br></div><div>&lt;fi=
xed&gt; <br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><div=
>

<div>
<div><div><div>But once documentation moved those considerations out of the=
 frame of &quot;conspiracy&quot; or zealotry by activist organizations, we =
suddenly began seeing the appeals work again: &quot;that&#39;s not the kind=
 of country we are, what we set up for ourselves,&quot; we started saying a=
gain.</div>


</div></div></div></div></div></div></blockquote><div>&lt;/fixed&gt;<br></d=
iv><div><br></div><div>(eom)<br></div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding=
-left:1ex">


<div dir=3D"ltr"><div><div><div class=3D""><div><div><div><div>And while it=
&#39;s still in a bit of denial, we are seeing a gradual grudging retractin=
g -- again, because the basis in fundamental liberties is unarguably relate=
d to how we set the government up in the founding act(s).<br>




<br></div>This is for governments and the more definitive relationship betw=
een fundamental liberties and the government; that is, that they are limits=
 on the government.=C2=A0 The judicial system treats fundamental rights vio=
lations by the government in terms of &quot;strict scrutiny,&quot; which me=
ans a governmental act that impinges on fundamental liberties must serve a =
compelling state interest, and even then, must be narrowly tailored.=C2=A0 =
For private parties, it&#39;s more that the working system creates a cultur=
e of people who enjoy this ability to live in a system where these limits o=
n the government are actually at play -- and that&#39;s a context that more=
 easily supports attitudes of resistance and pushback from people who see t=
heir dignity invaded by private firms that do excessive things.<br>




<br></div>None of this exists internationally.=C2=A0 The best you can place=
 some faint hope in is that national/state interests will be &quot;balanced=
&quot; against rights expressed in a treaty.=C2=A0 That&#39;s a totally dif=
ferent standard from strict scrutiny.=C2=A0 And relying on even that is unr=
ealistic, because governments have the &quot;epistemic priority&quot; -- an=
d so they often, quite freely, simply claim their sovereignty and act accor=
ding to what they claim is an important state interest.=C2=A0 They simply h=
ave that wherewithal at the international level.<br>



<br></div>All of which is preface to say that the result is that government=
s and private parties (and corporations, who have concocted trans-state &qu=
ot;rights&quot; through judges acting to fill in gaps in the law over the y=
ears) know the rules don&#39;t apply the same way in the international aren=
a.<br>



<br></div>In fact, given the transitions currently being attempted, whether=
 with the IANA functions or &quot;Internet governance&quot; more generally,=
 Yahoo&#39;s DMARC behavior may really be a sort of dry run, testing the ab=
ility to take advantage of the moves to put concerns related to the operati=
on of the Internet into an international frame, which folks are pushing for=
 without really recognizing what&#39;s missing in that context, what they h=
ave sort of unconsciously relied on and taken for granted within systems of=
 checks and balances that are rooted solidly at national levels.<br>



<br></div>The checks and balances don&#39;t work the same internationally, =
and that circumstance can be exploited (and is, all the time, these days).<=
br><br></div><div class=3D"">People might push back, but they don&#39;t rea=
lly do so with the same sense of fundamental recourse assured by a solidly =
rooted system.=C2=A0 And Yahoo knows this.=C2=A0 And we&#39;re just shoring=
 that up by saying we can just switch multistakeholderism to the internatio=
nal arena.<br>



<br></div></div><div class=3D"">(All of this is aside from other factors no=
t generally acknowledged -- that there are actually inter-governmentally en=
dorsed frames in place that will have a bearing on IANA type functions or d=
omain names (Names, Numbers, Addresses and Identifiers/NNAI, in the ITU par=
lance), regardless of the fact the IANA transition defines itself as non-go=
vernmentally-led or inter-governmental.=C2=A0 Looking at this in that light=
, Yahoo may be forcing the creation of a context in which it can start to e=
xercise those frameworks.)<span><font color=3D"#888888"><br>



<div><div><div><div><br><br></div><div>Seth
</div></div></div></div></font></span></div></div><div class=3D""><div><div=
><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Apr =
15, 2014 at 12:07 AM, Miles Fidelman <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:mfidelman@meetinghouse.net" target=3D"_blank">mfidelman@meetinghouse.net<=
/a>&gt;</span> wrote:<br>



<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Important business users, with Yahoo account=
s? =C2=A0Is that a joke?<br>
<br>
Just as a reference point:<br>
- I just logged into my long-unused, and un-publicized yahoo email account =
- and the only thing there is Spam<br>
- the lion&#39;s share of mail that comes from yahoo, to my normal account,=
 is spam<br>
- unfortunately, a good number of people on the email lists that I run seem=
 to have Yahoo mail accounts - and a good amount of the mail that comes fro=
m those accounts is... you guessed it... spam - because yahoo email account=
s seem to be vulnerable to cracking and exploitation<br>




<br>
So, just who is it that Yahoo is protecting here?<div><div><br>
<br>
Abdussalam Baryun wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The standard procedure in many companies is business scoped, so they identi=
fy important business users and the business returns/damages. Most importan=
t users are not IT experts, and use email for personal exchange. Yahoo has =
signed an agreement with users to protect its information system, so all se=
em to follow that, and all users are free to stop using services or not.<br=
>




<br>
AB<br>
<br>
On Tuesday, April 15, 2014, Brian E Carpenter wrote:<br>
<br>
=C2=A0 =C2=A0 I thought that standard operating procedure in the IT industr=
y<br>
=C2=A0 =C2=A0 was: if you roll something out and it causes serious breakage=
 to<br>
=C2=A0 =C2=A0 some of your users, you roll it back as soon as possible.<br>
<br>
=C2=A0 =C2=A0 Why hasn&#39;t Yahoo rolled back its &#39;reject&#39; policy =
by now?<br>
<br>
=C2=A0 =C2=A0 Regards<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Brian<br>
<br>
</blockquote>
<br>
<br></div></div><div><div>
-- <br>
In theory, there is no difference between theory and practice.<br>
In practice, there is. =C2=A0 .... Yogi Berra<br>
<br>
</div></div></blockquote></div><br></div>
</div></div></div></blockquote></div><br></div></div>
</blockquote></div><br></div>

--20cf30334739341b8d04f71338dd--


From nobody Tue Apr 15 06:11:13 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39EBC1A0442 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 06:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level: 
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 ER-EFtTF5vnE for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 06:11:05 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 0F6DE1A042E for <ietf@ietf.org>; Tue, 15 Apr 2014 06:11:04 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 921C520030; Tue, 15 Apr 2014 09:11:18 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 810D063ABA; Tue, 15 Apr 2014 09:11:01 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 6E92C63AA2; Tue, 15 Apr 2014 09:11:01 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "John Levine" <johnl@taugh.com>
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <20140414220233.32201.qmail@joyce.lan>
References: <20140414220233.32201.qmail@joyce.lan>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 15 Apr 2014 09:11:01 -0400
Message-ID: <20123.1397567461@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PeFHzzoo8THep2X56o2uoZPFp-w
Cc: tytso@mit.edu, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 13:11:10 -0000

--=-=-=


>>to something like:
>>
>From: Brian E Carpenter <brian.e.carpenter@yahoo.com.INVALID>

So, that totals people's address books.

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU00v4oqHRg3pndX9AQIdXwQA1JNJvdavWPQ5RkWir0spBjP8tJ5gqhdJ
EpNs9ZLPV/SZpooy3OVYP9ibof9pjqSl0tbZQ3Fx6FRo+/LVP6eVQnUWk1iiVRw6
WghoimphGx4TmcnMkewk51Hbu01wR8MDqEDk7naeqEuqW839aWzU7gDaAoPczoc9
pgzW+YuVBVE=
=3yoL
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 15 08:17:29 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 865881A04DC for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 08:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.994
X-Spam-Level: ****
X-Spam-Status: No, score=4.994 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665] autolearn=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 qKzjIecR0bJb for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 08:17:24 -0700 (PDT)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 870761A0658 for <ietf@ietf.org>; Tue, 15 Apr 2014 08:17:24 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6O2PIEIK0005DF2@mauve.mrochek.com> for ietf@ietf.org; Tue, 15 Apr 2014 08:12:19 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6O0FD8M9S00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 15 Apr 2014 08:12:11 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6O2PFTIR600004W@mauve.mrochek.com>
Date: Tue, 15 Apr 2014 07:51:20 -0700 (PDT)
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-reply-to: "Your message dated Mon, 14 Apr 2014 10:28:51 -0700" <CAL0qLwYHP-rVF5TmEH2_kTZ7bDnxms7md=Y8Voef9OyPD4Bj8Q@mail.gmail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B4E97.2050000@meetinghouse.net> <CAL0qLwYHP-rVF5TmEH2_kTZ7bDnxms7md=Y8Voef9OyPD4Bj8Q@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ChP9nLriPP3fZhm5l5D2s99Pl6Q
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 15:17:28 -0000

> On Sun, Apr 13, 2014 at 7:57 PM, Miles Fidelman
> <mfidelman@meetinghouse.net>wrote:

> >
> > It strikes me that the real way to address some of these issues is to add
> > a few new headers to SMTP - to get rid of the overloading of the From: and
> > Reply-to: headers associated with mailing lists.  An SMTP extension that
> > would absorb some of the well-known and well-understood functions of list
> > software.
> >
> > [...]
> >

> I made that same suggestion on a different list.  It seems as if that
> suggestion was made long ago and the debate reached "religious"
> proportions.  One of the usual answers emerged, which was that it'll take
> forever to get this deployed with sufficient ubiquity as to be helpful.

Suggestion? Try suggestions. I can think of at least four proposals at various
times, and I'm quite sure there have been others. At least one of them, by John
Myers, was written down in a draft.

And the problems with these proposals weren't religious. Rather, the problem
has always been that originator header semantics are already fairly nuanced,
and adding a bunch of them seems to exceed our design abilities. As a result
the discussions bogged down in misunderstandings about minutiae and talking
at cross purposes.

The only discussion I know of in this space that reached "religious
proportions" was the one in the failed mailing list WG.  But that was largely
focused on the "right" way to use existing header fields, not the addition of
new fields. So I don't think that really counts.

> I'm guessing that means we shouldn't try.

OK, for this to work you're going to have to come up with a solution that's
clear and comprehensible, get general agreement on it, publish it, and then get
widespread support for it implemented and deployed in both list processors and
user agents in a fairly timely way.

I'd also say there's a good chance that DMARC will have to be changed in some
way to support it, so that needs to be on the table. And that support needs to
be deployed.

Given these realities, do you think this is worth spending (a probably large
amount of) time doing?

				Ned


From nobody Tue Apr 15 08:30:59 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 005081A0476 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 08:30:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 Z7eG1iB1hN3F for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 08:30:52 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 62FF01A014B for <ietf@ietf.org>; Tue, 15 Apr 2014 08:30:52 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1Wa5Jw-0000wh-2Q; Tue, 15 Apr 2014 15:30:48 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 560CD580893; Tue, 15 Apr 2014 11:30:47 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397575847; bh=OPtakf1X72TuXOvR6VMlocSSYawdKPQO5WZCfJtQ6+o=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=xgxPsA/jMSBn4VxbOGTZjQM6woDwsO4F0y7M/C2rLdm3dgu2Rgb5MU3L1mzB1xW99 eoWY5Nt2HEVXROaS5l+kvX3XsTunM8f+Fk+hBjThMus5aznP3L080WYQENcpxPgcGc 0OjfAJUYoTNPtCEmk7T6hW1k5y5x8Hz7rwwLE1bM=
Date: Tue, 15 Apr 2014 11:30:47 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <20140415153047.GA4456@thunk.org>
References: <20140414220233.32201.qmail@joyce.lan> <20123.1397567461@sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20123.1397567461@sandelman.ca>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/isYRtBG6AmSANiBSpybucpv89BQ
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 15:30:57 -0000

On Tue, Apr 15, 2014 at 09:11:01AM -0400, Michael Richardson wrote:
> >>
> >From: Brian E Carpenter <brian.e.carpenter@yahoo.com.INVALID>
> 
> So, that totals people's address books.

But only for yahoo.com users.  Somehow, I have a very hard time
feeling sympathetic about their plight.

If Yahoo isn't going to care about screwing over mailing list
administrators, I'm not sure why I should care about about
inconveniencing Yahoo uesrs.  If they end up moving to some other mail
provider, I'll consider that a bonus.

And if Yahoo is right, and most Yahoo users don't use mailing lists,
then obviously this won't be a problem, right?

						- Ted


From nobody Tue Apr 15 08:51:59 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 564ED1A049A for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 08:51:56 -0700 (PDT)
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] autolearn=ham
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 mi-WbMB473lf for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 08:51:51 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 837171A0711 for <ietf@ietf.org>; Tue, 15 Apr 2014 08:51:50 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3FFphmW014751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 15 Apr 2014 08:51:46 -0700
Message-ID: <534D5516.7060902@dcrocker.net>
Date: Tue, 15 Apr 2014 08:49:42 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com>
In-Reply-To: <534C8F2B.9060903@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 15 Apr 2014 08:51:46 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5vbfrHUFZx65WXQ590D6DQMm9_s
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 15:51:56 -0000

On 4/14/2014 6:45 PM, Brian E Carpenter wrote:
> I thought that standard operating procedure in the IT industry
> was: if you roll something out and it causes serious breakage to
> some of your users, you roll it back as soon as possible.
>
> Why hasn't Yahoo rolled back its 'reject' policy by now?


As the most-recent public statement from Yahoo, this might have some 
tidbits in it that are relevant to your question:


 
http://yahoo.tumblr.com/post/82426971544/an-update-on-our-dmarc-policy-to-protect-our-users



d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Apr 15 08:54:32 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E734E1A0466 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 08:54:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 RnZtFg8eN4RV for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 08:54:25 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id C49621A03A5 for <ietf@ietf.org>; Tue, 15 Apr 2014 08:54:24 -0700 (PDT)
Received: (qmail 28868 invoked from network); 15 Apr 2014 15:54:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=70c3.534d562d.k1404; bh=e4TWZvR8M5g4iXWegs9VeluyX7JMjSzdibdy28gCS6w=; b=IrNzuhuR7tA4WPVY7nLyPH7tIL+LIMVlPntkBN36dDDtLKPiQY0+XJk534hUeg9x30Q/Tuu1G0y2nbXwoeCsHwRYbkAyPYTizY/Z6SdBfRA+/MpRtn6yak5l7CPg4ZpmXctxKh+8+Y+E6f9XHR0QdmsO2WPlXgojIp8TQVJSoTZWlwEhg5OBFkduyHTDM8fIzUq5k2P2KKUZKYE3+MzNucjEz1iHbQslh5rqaurAG+gHsKtlbXlS6zidNuz/aqmJ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=70c3.534d562d.k1404; bh=e4TWZvR8M5g4iXWegs9VeluyX7JMjSzdibdy28gCS6w=; b=sspAyeG7/roKIr/Lc9N53qhnGkE5X9rGq05jELglEcMaM2n8WWfq9DDNJ+8cxInz3fD/icWU5VK8vIEgn8eOyiwEsv8VZJUcEIpUHKGFFA5Rsj5wP6Pwd/dH+2IThdIDLVNRxnQlyUoW0gdeKu7Mdoxo9ZfxxVNE3RNJDkxz1wfsYOed2vwmP7afaDWeNd2jBdgfnrLZfjFotPcPzD6LVDEbZkoNXINcMqvAp0aZ1KgjzExZcLcnkkPBzQG0bBnQ
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 15 Apr 2014 15:54:21 -0000
Date: 15 Apr 2014 11:54:20 -0400
Message-ID: <alpine.BSF.2.00.1404151151490.37785@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <20140415153047.GA4456@thunk.org>
References: <20140414220233.32201.qmail@joyce.lan> <20123.1397567461@sandelman.ca> <20140415153047.GA4456@thunk.org>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QghtcX4Y9PlOzQ7ATJYNz5zp1Fs
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 15:54:30 -0000

>> So, that totals people's address books.
>
> But only for yahoo.com users.  Somehow, I have a very hard time
> feeling sympathetic about their plight.

No, it also screws up anyone who wants to correspond with Yahoo users who 
happen to correspond via shared mailing lists.

But in the current environment, it still seems the least bad option.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Tue Apr 15 09:03:10 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D5C1A04B7 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.501
X-Spam-Level: 
X-Spam-Status: No, score=-97.501 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_44=0.6, J_CHICKENPOX_45=0.6, J_CHICKENPOX_46=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 6nK8Bo_lr0bS for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:03:01 -0700 (PDT)
Received: from secure.winserver.com (ntbbs.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 708031A04A9 for <ietf@ietf.org>; Tue, 15 Apr 2014 09:03:01 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5298; t=1397577770; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=MpQYlFwbB8kLyeyboUJkOFKVVxg=; b=CnAbDTekLpaymCqwjxbY nXvtaMceOKbF+W+cqbdp2FLN8bEH8xEQJSi9mm4a67F+O6IFZYtKUVy+Ot4es3+i 7iROVIT+7jRsht8CiBQwiv5cem7e42lmLiwFlVzEkPLhDb/ynta4XsBtnoZc8sh3 arVqSDPEHuX0I5AjqlNusO4=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 12:02:50 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 686346756.3.3464; Tue, 15 Apr 2014 12:02:49 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5298; t=1397577704; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=Iky5OgR x2jaureC6Y3jQ4kKEbZohBl5JN/wyIVgyfJs=; b=qhAoSCkGSXgd+Pn3Eh9eDCO FOSJ68IjLcC154NuikbO3vRRIzwzYo6P8qHrC1TLADK13pVO0GauUhdhfZopdmQi U9tNFP4vWFGnkHQWmjvDZcGGoO5tKlPsy/qH1mM/lQHe99xjsJTqH8R+ait1sku5 8hoXVOC15smYJMt3DRtA=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 12:01:44 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 705880390.9.9008; Tue, 15 Apr 2014 12:01:43 -0400
Message-ID: <534D5829.8080503@isdg.net>
Date: Tue, 15 Apr 2014 12:02:49 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Sabahattin Gucukoglu <listsebby@me.com>,  "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <534C4AF8.60709@sonnection.nl> <534C4FB1.9060508@bbiw.net> <5593510.KZqL8eSkZ2@scott-latitude-e6320> <B078C9C1-1148-412B-9752-4B7A437A9780@me.com>
In-Reply-To: <B078C9C1-1148-412B-9752-4B7A437A9780@me.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OP6VffyRD1pCWYYqjIqF-OJo3u0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 16:03:06 -0000

On 4/15/2014 12:32 AM, Sabahattin Gucukoglu wrote:
>
> Basically DMARC was always an outsider effort.  The effect of a bunch of very important ESPs (and a bunch of security types) crying "Look!  We've solved the email forgery problem!" was to inspire me to look at the spec, shrug it off as yet another FUSSP *, and move on.  Does this mean that I have materially failed to contribute?  Well maybe, but it means a lot for the spec to be in the IETF where I can point out how broken it is. :)
>

I feel the same way.

But after the whole stressful, wasteful dollars, time and energy 
situation over 9 years starting with DKIM+SSP, reduced to DKIM+ADSP or 
DKIM+POLICY in general,  it is not healthy to repeat this with DMARC.

It was clear DMARC couldn't address the key central total mail 
integration support requirements if it lacked two things:

   - 3rd party policies,
   - MLM/MLS support for restrictive policies.

> And, to be clear: I respect the goals of the proposal, and will be reasonable in accommodating it.  But to suggest that the contortions of the proponents in keeping it from the watchful eye of the IETF weren't in some small way intended to advance DMARC by force in numbers rather than consensus strains credulity, just a tad.
>

Yes, that was an obvious problem, marketing hype we tend to ignore, 
but it was a concern that they were just repeating the same issues. 
Lets remember that DMARC was more about reporting than actually 
honoring and literally "rejecting" transactions.  Reporting was since 
as a potential mail-based DoS attack vector. So my input was to limit 
it to TESTING periods and under abuse controls when it was suggested 
to DKIM+POLICY reporting.

We saw this again repeated with SPF when in the SPFBIS, the same 
people mind you, began to add DOUBT on the whether anyone actually did 
reject mail and just simply quarantine the mail.  So it became a battle of

       SPFFAIL+REJECT vs SPFFAIL+ACCEPT+MARK

When I saw that mentality grow, I raised an SPFBIS issue to make sure 
we describe in the spec as two alternative implementation and 
deployment option:

    - SPFFAIL+REJECT
    - SPFFAIL+ACCEPT+MARK+SEPARATE

Without separation, we have a security loophole if the deployment did 
not operate by rejecting SPF Failure but instead accepted, marked it 
with an Auth-Res header but still delivered the failed message to the 
user.

And guess what?

Its happening now again with the new Yahoo/Facebook RRVS proposal. 
Again, they are raising the question if whether a reject should be 
taken literally or not.

IMO, what has occurred now is a realization that there are actual 
systems that are beginning to actually reject the mail based on 
restrictive policies.  When it happen to a big long time publicly used 
domain like yahoo.com, now it became a major problem.

Anyway, it is really too tiresome and stressful to repeat all this.

I thought it was a major mistake and IETF error to make ADSP historic, 
done to help make way for DMARC.  Who are we kidding?  But if thats 
the case, once again, the solution is simple:

  - Add 3rd party policy support,

  - In DMARC deployment guide, provide strong semantics for MiddleWare
    to support policies.  It can not be ignored.

With the latter, it was a mistake in the DKIM deployment guide to not 
raise an  Middle Ware resigning implementation note about not honoring 
ADSP checking.  This issue was raised when the document was written 
but largely ignored.

Again, we been through all this. It is all covered with the DKIM 
threat analysis and one of the main conclusions is that self-signing 
1st party policies are a powerful method to protect against fraud. 
ADSP was a proposed standard track work item along with DKIM-base. 
DKIM-WG ended on a sour note never resolving this basic issue.

The only reason common agreement and question was whether we can scale 
the 3rd party domain authorizations.

So what did we do?

Eventually, Murray saw the issue wouldn't go away. I talked about ASL 
(Authorized Signer List) which piggy backed off the ADSP record. It 
was meant for the smaller systems. Doug Otis talked about TPA (Third 
Party Authorization) but it was too complex.  So Murray did ATPS as an 
ADSP extension to help with the complexity and scalability questions.

See the wizard at

   http://www.winserver.com/public/wcadsp

which allows you to create zone records for ADSP+ATPS+ACL domains.  We 
implemented this into our software and mail system product, including 
the MLS that will deny restrictive ADSP domains.

The work was done.  The solutions and conflicts are known. The 
question is more a matter of getting people to accept policy more or 
as some will like, get rid of it or just don't really honor any kind 
of mail rejection -- always accept, mark and hopefully separate.

And lets not forget, the DKIM+TRUST model which is what Crocker and 
Levine want to see happen.  This market has not materialized 
unfortunately, which would be different than the DKIM+POLICY 
framework, in that TRUST requires all nodes in the system to query the 
same trust databases, otherwise we lack consistency and persistency in 
mail distributions.  Some nodes will become targets if they lack 
subscription to a 3rd party TRUST query system.

-- 
HLS



From nobody Tue Apr 15 09:27:52 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F24F21A049C for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.5
X-Spam-Level: 
X-Spam-Status: No, score=-1.5 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 MsN-ac6wk4jl for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:27:47 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1241A048A for <ietf@ietf.org>; Tue, 15 Apr 2014 09:27:47 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3FGRew6015649 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 15 Apr 2014 09:27:44 -0700
Message-ID: <534D5D84.2020307@dcrocker.net>
Date: Tue, 15 Apr 2014 09:25:40 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <1485381.SfhK6qmW0I@scott-latitude-e6320>
In-Reply-To: <1485381.SfhK6qmW0I@scott-latitude-e6320>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 15 Apr 2014 09:27:44 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/n1xsCjcpqk942Hy0MDt7wyDlr0A
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 16:27:52 -0000

On 4/14/2014 8:35 PM, Scott Kitterman wrote:
> On Monday, April 14, 2014 10:26:44 Murray S. Kucherawy wrote:
>> I mentioned in another thread that the DMARC people did come to the IETF to
>> ask for a working group to complete development of the work on the
>> standards track.  This request was denied on the grounds that DMARC was
>> essentially already done, and thus the IETF had nothing engineering-wise to
>> contribute.  There were also too few people that were not already DMARC
>> proponents that would commit to working on it.
>>
>> (And as I said on that other thread, I'm happy to stand corrected if I've
>> mischaracterized any of that.)
>
> My perception (and it may also be wrong) is that anyone who claimed there was
> work yet to be done was shouted down.

Given that the exchanges were on an open mailing list, I'm not quite 
sure what that means.

What I am sure of is that I've pressed quite vigorously and repeatedly, 
first on the open dmarc.org mailing list and then on the IETF DMARC 
mailing list, for folk to cite work that needed to be done and to 
develop group support for that work.

What I saw was some individuals suggesting some bits of work, but no 
support developed around it.  (By 'support' I mean more than a few folk.)

Perhaps you can point to specific examples of this 'shouting down' 
happening?

What I also saw was some folk insisting that the charter be vague and 
unconstrained, with no concern for the installed base.


> As I said in the other thread, I think the only reason it was perceived as
> done is that the private group that developed the spec declared it done and
> fought against any WG charter language that would have permitted changes to
> the core protocol.    Based on that approach, no wonder it was declined.

Changes to the core of a protocol is the essence of de-stabilizing its 
installed base.

Writing a charter that permits de-stabilizing a substantial installed 
base only makes sense when there is a clear and compelling basis already 
known for needing to make such changes.

With respect to DMARC, none has been offered or has developed community 
support.

Writing a charter that permits de-stablilizing an installed base 
covering 60% of the world's email traffic, in the absence of a clear and 
compelling understanding of the need would be irresponsible.

Arguably, the mere existence of such a charter would be de-stabilizing, 
since it means that anyone considering adoption has an excuse to defer 
it to the indefinite future, when the IETF might get around to releasing 
a revision.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Apr 15 09:35:50 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21C661A01BE for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 kFKY1aqwzN0I for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:35:42 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 7601D1A0639 for <ietf@ietf.org>; Tue, 15 Apr 2014 09:35:42 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id BC476CC093 for <ietf@ietf.org>; Tue, 15 Apr 2014 12:35:38 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id pVaRFmQRsmbl for <ietf@ietf.org>; Tue, 15 Apr 2014 12:35:34 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 62382CC08F for <ietf@ietf.org>; Tue, 15 Apr 2014 12:35:34 -0400 (EDT)
Message-ID: <534D5FD6.506@meetinghouse.net>
Date: Tue, 15 Apr 2014 12:35:34 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net>
In-Reply-To: <534D5516.7060902@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JC7afpq0pXRtheQuHevNC9L_prE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 16:35:47 -0000

Dave Crocker wrote:
> On 4/14/2014 6:45 PM, Brian E Carpenter wrote:
>> I thought that standard operating procedure in the IT industry
>> was: if you roll something out and it causes serious breakage to
>> some of your users, you roll it back as soon as possible.
>>
>> Why hasn't Yahoo rolled back its 'reject' policy by now?
>
>
> As the most-recent public statement from Yahoo, this might have some 
> tidbits in it that are relevant to your question:
>
>
>
> http://yahoo.tumblr.com/post/82426971544/an-update-on-our-dmarc-policy-to-protect-our-users 
>
>
You mean the part where they say:
"We know there are about 30,000 affected email sending services, but we 
also know that the change needed to support our new DMARC policy is 
important and not terribly  difficult to implement. We have detailed the 
changes we are requiring here 
<http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what-should-senders-do>."

I.e., 'not our problem'

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Tue Apr 15 09:46:39 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E70331A0499 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.563
X-Spam-Level: 
X-Spam-Status: No, score=-1.563 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=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 bCuzWzusiYb0 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:46:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id D37C61A01D2 for <ietf@ietf.org>; Tue, 15 Apr 2014 09:46:32 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7E1F720030; Tue, 15 Apr 2014 12:46:47 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 9A7D763ABA; Tue, 15 Apr 2014 12:46:29 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 81D0D63AA2; Tue, 15 Apr 2014 12:46:29 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <20140415153047.GA4456@thunk.org>
References: <20140414220233.32201.qmail@joyce.lan> <20123.1397567461@sandelman.ca> <20140415153047.GA4456@thunk.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 15 Apr 2014 12:46:29 -0400
Message-ID: <335.1397580389@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Zw0cFNIO2yieNWe_lGMX9jOmEnQ
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 16:46:37 -0000

--=-=-=


Theodore Ts'o <tytso@mit.edu> wrote:
    > On Tue, Apr 15, 2014 at 09:11:01AM -0400, Michael Richardson wrote:
    >> >>
    >> >From: Brian E Carpenter <brian.e.carpenter@yahoo.com.INVALID>
    >>
    >> So, that totals people's address books.

    > But only for yahoo.com users.  Somehow, I have a very hard time
    > feeling sympathetic about their plight.

yes, I take your point.  Let's be clear, it totals my address book for people
who are on yahoo.  I agree that maybe that's tough.

    > If Yahoo isn't going to care about screwing over mailing list
    > administrators, I'm not sure why I should care about about
    > inconveniencing Yahoo uesrs.  If they end up moving to some other mail
    > provider, I'll consider that a bonus.

+1

    > And if Yahoo is right, and most Yahoo users don't use mailing lists,
    > then obviously this won't be a problem, right?

funny, cause most people I know who have yahoo addresses do so because it
given to them so that they could manage their mailing lists.

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU01iYoqHRg3pndX9AQI/GwQAjUo+uxmHeZhKdoNXveSFRlegXUvljDeH
sVHzUjzcszBYyunLB+T3DIIerwb/bkjzNosTxAS9zHZfqyS8VORBdHTAOtZhoqox
/ziEgbg5S+ZMmZnuhdp2j13yc8mUL/eig3DLcZSpdaLM9WwHke3wwQuKheyUhDaD
ZKiaX4G/GSg=
=Dr4g
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 15 09:47:07 2014
Return-Path: <seth.p.johnson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5F721A07D4 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:47:03 -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, SPF_PASS=-0.001] autolearn=ham
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 97jC9_toyDl3 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:46:58 -0700 (PDT)
Received: from mail-ve0-x22c.google.com (mail-ve0-x22c.google.com [IPv6:2607:f8b0:400c:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 608301A079F for <ietf@ietf.org>; Tue, 15 Apr 2014 09:46:58 -0700 (PDT)
Received: by mail-ve0-f172.google.com with SMTP id jx11so9582454veb.31 for <ietf@ietf.org>; Tue, 15 Apr 2014 09:46:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=Fd+Iuz9sv/iKosFCwfjX0SLQ77mV/S6ewrJhRyJBulw=; b=C8QLv6YetACAYE74tTl67aPxTSvYWgYmBL9JLFetQBSW33N2DHKMWUsxIx1q1OW8Gr gqt8a9QS8Nf1bfQ4p8mivOry7RbK0WWbFT78ub3tjWy5OmIOyh2TSPnFq8ZnNiKtGa9x 4uUYJH2QF4E+K0LFmvLAIJDoMh8rb6IhShCdYZ6Rc8PSYJxKovHVdZhuYcs9WpM48mX8 dvwHWjmD0voUvelGEgrkecMG23kCWe94NdeSLi8ONN/S0quXJLO1QIF70egD+Npickk6 tNXE9SaMfQTTQ263C75T03A4wp6JURr7bK86VpmmzQtKI0O6PHoJ5ztIvG1GfZPBH+Bb pwQA==
X-Received: by 10.58.23.6 with SMTP id i6mr2094449vef.12.1397580415300; Tue, 15 Apr 2014 09:46:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.220.66.6 with HTTP; Tue, 15 Apr 2014 09:46:15 -0700 (PDT)
In-Reply-To: <534D5FD6.506@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D5FD6.506@meetinghouse.net>
From: Seth Johnson <seth.p.johnson@gmail.com>
Date: Tue, 15 Apr 2014 12:46:15 -0400
Message-ID: <CAJkfFBzw4uKOvOdZKiymW6PX+iQ9CYQuMENOopx-32nEA7TGyg@mail.gmail.com>
Subject: Re: What I've been wondering about the DMARC problem
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=047d7b339db132fb8504f7178cdc
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/F72pfYZCCSalKjegN2Px7GkJji0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 16:47:04 -0000

--047d7b339db132fb8504f7178cdc
Content-Type: text/plain; charset=UTF-8

They're forcing adoption -- while folks have not been addressing this piece
of the inter-governmental frame.  :-)


On Tue, Apr 15, 2014 at 12:35 PM, Miles Fidelman <mfidelman@meetinghouse.net
> wrote:

> Dave Crocker wrote:
>
>> On 4/14/2014 6:45 PM, Brian E Carpenter wrote:
>>
>>> I thought that standard operating procedure in the IT industry
>>> was: if you roll something out and it causes serious breakage to
>>> some of your users, you roll it back as soon as possible.
>>>
>>> Why hasn't Yahoo rolled back its 'reject' policy by now?
>>>
>>
>>
>> As the most-recent public statement from Yahoo, this might have some
>> tidbits in it that are relevant to your question:
>>
>>
>>
>> http://yahoo.tumblr.com/post/82426971544/an-update-on-our-
>> dmarc-policy-to-protect-our-users
>>
>>  You mean the part where they say:
> "We know there are about 30,000 affected email sending services, but we
> also know that the change needed to support our new DMARC policy is
> important and not terribly  difficult to implement. We have detailed the
> changes we are requiring here <http://yahoomail.tumblr.com/
> post/82426900353/yahoo-dmarc-policy-change-what-should-senders-do>."
>
> I.e., 'not our problem'
>
> Miles Fidelman
>
>
> --
> In theory, there is no difference between theory and practice.
> In practice, there is.   .... Yogi Berra
>
>

--047d7b339db132fb8504f7178cdc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">They&#39;re forcing adoption -- while folks have not been =
addressing this piece of the inter-governmental frame. =C2=A0:-)<div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">
On Tue, Apr 15, 2014 at 12:35 PM, Miles Fidelman <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank">mfidelman@meeti=
nghouse.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">


<div><div>Dave Crocker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 4/14/2014 6:45 PM, Brian E Carpenter wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I thought that standard operating procedure in the IT industry<br>
was: if you roll something out and it causes serious breakage to<br>
some of your users, you roll it back as soon as possible.<br>
<br>
Why hasn&#39;t Yahoo rolled back its &#39;reject&#39; policy by now?<br>
</blockquote>
<br>
<br>
As the most-recent public statement from Yahoo, this might have some tidbit=
s in it that are relevant to your question:<br>
<br>
<br>
<br>
<a href=3D"http://yahoo.tumblr.com/post/82426971544/an-update-on-our-dmarc-=
policy-to-protect-our-users" target=3D"_blank">http://yahoo.tumblr.com/post=
/<u></u>82426971544/an-update-on-our-<u></u>dmarc-policy-to-protect-our-<u>=
</u>users</a> <br>



<br>
</blockquote></div></div>
You mean the part where they say:<br>
&quot;We know there are about 30,000 affected email sending services, but w=
e also know that the change needed to support our new DMARC policy is impor=
tant and not terribly =C2=A0difficult to implement. We have detailed the ch=
anges we are requiring here &lt;<a href=3D"http://yahoomail.tumblr.com/post=
/82426900353/yahoo-dmarc-policy-change-what-should-senders-do" target=3D"_b=
lank">http://yahoomail.tumblr.com/<u></u>post/82426900353/yahoo-dmarc-<u></=
u>policy-change-what-should-<u></u>senders-do</a>&gt;.&quot;<br>



<br>
I.e., &#39;not our problem&#39;<span><font color=3D"#888888"><br>
<br>
Miles Fidelman</font></span><div><div><br>
<br>
-- <br>
In theory, there is no difference between theory and practice.<br>
In practice, there is. =C2=A0 .... Yogi Berra<br>
<br>
</div></div></blockquote></div><br></div></div>

--047d7b339db132fb8504f7178cdc--


From nobody Tue Apr 15 09:52:53 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 670541A011A for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 KaLcOk5s5HNZ for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 09:52:44 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 9B3881A0552 for <ietf@ietf.org>; Tue, 15 Apr 2014 09:52:44 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 7E770CC08F for <ietf@ietf.org>; Tue, 15 Apr 2014 12:52:41 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id hxYfKA55zXvt for <ietf@ietf.org>; Tue, 15 Apr 2014 12:52:37 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 29242CC095 for <ietf@ietf.org>; Tue, 15 Apr 2014 12:52:34 -0400 (EDT)
Message-ID: <534D63D1.3060202@meetinghouse.net>
Date: Tue, 15 Apr 2014 12:52:33 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D5FD6.506@meetinghouse.net> <CAJkfFBzw4uKOvOdZKiymW6PX+iQ9CYQuMENOopx-32nEA7TGyg@mail.gmail.com>
In-Reply-To: <CAJkfFBzw4uKOvOdZKiymW6PX+iQ9CYQuMENOopx-32nEA7TGyg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/E361qRBXCqfz97IFTbM6Sar0rjY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 16:52:48 -0000

Which does bring us back to the question of how to deal with "bad 
actors" (or at least "irresponsible actors" or "uncooperative actors") 
within a cooperative governance framework.  Sigh.... Miles

Seth Johnson wrote:
> They're forcing adoption -- while folks have not been addressing this 
> piece of the inter-governmental frame.  :-)
>
>
> On Tue, Apr 15, 2014 at 12:35 PM, Miles Fidelman 
> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>
>     Dave Crocker wrote:
>
>         On 4/14/2014 6:45 PM, Brian E Carpenter wrote:
>
>             I thought that standard operating procedure in the IT industry
>             was: if you roll something out and it causes serious
>             breakage to
>             some of your users, you roll it back as soon as possible.
>
>             Why hasn't Yahoo rolled back its 'reject' policy by now?
>
>
>
>         As the most-recent public statement from Yahoo, this might
>         have some tidbits in it that are relevant to your question:
>
>
>
>         http://yahoo.tumblr.com/post/82426971544/an-update-on-our-dmarc-policy-to-protect-our-users
>
>
>     You mean the part where they say:
>     "We know there are about 30,000 affected email sending services,
>     but we also know that the change needed to support our new DMARC
>     policy is important and not terribly  difficult to implement. We
>     have detailed the changes we are requiring here
>     <http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what-should-senders-do>."
>
>     I.e., 'not our problem'
>
>     Miles Fidelman
>
>
>     -- 
>     In theory, there is no difference between theory and practice.
>     In practice, there is.   .... Yogi Berra
>
>


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Tue Apr 15 10:00:59 2014
Return-Path: <fergie@people.ops-trust.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B3C71A0658 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:00:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 PPyZ3x36AxyM for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:00:57 -0700 (PDT)
Received: from people.ops-trust.net (people.usa5.ops-trust.net [199.168.91.182]) by ietfa.amsl.com (Postfix) with ESMTP id F19CE1A011A for <ietf@ietf.org>; Tue, 15 Apr 2014 10:00:56 -0700 (PDT)
Received: from [192.168.10.155] (unknown [64.122.169.98]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fergie) by people.ops-trust.net (Postfix) with ESMTPSA id 405B01468003; Tue, 15 Apr 2014 17:00:53 +0000 (UTC)
Message-ID: <534D65C2.2040209@people.ops-trust.net>
Date: Tue, 15 Apr 2014 10:00:50 -0700
From: Paul Ferguson <fergie@people.ops-trust.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D5FD6.506@meetinghouse.net> <CAJkfFBzw4uKOvOdZKiymW6PX+iQ9CYQuMENOopx-32nEA7TGyg@mail.gmail.com> <534D63D1.3060202@meetinghouse.net>
In-Reply-To: <534D63D1.3060202@meetinghouse.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uPI0xjbGBtRXR8ziFrcKVYG_S_o
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 17:00:58 -0000

On 4/15/2014 9:52 AM, Miles Fidelman wrote:

> Which does bring us back to the question of how to deal with "bad
> actors" (or at least "irresponsible actors" or "uncooperative actors")
> within a cooperative governance framework.  Sigh.... Miles
> 

Welcome to the club. I've been wondering about that same issue with
regards to getting adoption of BCP38 for over a decade. :-)

- ferg



> Seth Johnson wrote:
>> They're forcing adoption -- while folks have not been addressing this
>> piece of the inter-governmental frame.  :-)
>>
>>
>> On Tue, Apr 15, 2014 at 12:35 PM, Miles Fidelman
>> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>>
>>     Dave Crocker wrote:
>>
>>         On 4/14/2014 6:45 PM, Brian E Carpenter wrote:
>>
>>             I thought that standard operating procedure in the IT
>> industry
>>             was: if you roll something out and it causes serious
>>             breakage to
>>             some of your users, you roll it back as soon as possible.
>>
>>             Why hasn't Yahoo rolled back its 'reject' policy by now?
>>
>>
>>
>>         As the most-recent public statement from Yahoo, this might
>>         have some tidbits in it that are relevant to your question:
>>
>>
>>
>>        
>> http://yahoo.tumblr.com/post/82426971544/an-update-on-our-dmarc-policy-to-protect-our-users
>>
>>
>>
>>     You mean the part where they say:
>>     "We know there are about 30,000 affected email sending services,
>>     but we also know that the change needed to support our new DMARC
>>     policy is important and not terribly  difficult to implement. We
>>     have detailed the changes we are requiring here
>>    
>> <http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what-should-senders-do>."
>>
>>
>>     I.e., 'not our problem'
>>
>>     Miles Fidelman
>>
>>
>>     --     In theory, there is no difference between theory and practice.
>>     In practice, there is.   .... Yogi Berra
>>
>>
> 
> 


-- 
Paul Ferguson
VP Threat Intelligence, IID
PGP Public Key ID: 0x54DC85B2


From nobody Tue Apr 15 10:16:51 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9389D1A0657 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 x_31AYhA_pDE for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:16:47 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id BE1F21A04C8 for <ietf@ietf.org>; Tue, 15 Apr 2014 10:16:47 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 96F80CC08F for <ietf@ietf.org>; Tue, 15 Apr 2014 13:16:44 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id H1zPepzIqzB4 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:16:36 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 2CD5CCC094 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:16:31 -0400 (EDT)
Message-ID: <534D696E.2040202@meetinghouse.net>
Date: Tue, 15 Apr 2014 13:16:30 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D5FD6.506@meetinghouse.net> <CAJkfFBzw4uKOvOdZKiymW6PX+iQ9CYQuMENOopx-32nEA7TGyg@mail.gmail.com> <534D63D1.3060202@meetinghouse.net> <534D65C2.2040209@people.ops-trust.net>
In-Reply-To: <534D65C2.2040209@people.ops-trust.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gq37VgvJoBn7xLnV0GSf3-g8tLc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 17:16:48 -0000

Paul Ferguson wrote:
> On 4/15/2014 9:52 AM, Miles Fidelman wrote:
>
>> Which does bring us back to the question of how to deal with "bad
>> actors" (or at least "irresponsible actors" or "uncooperative actors")
>> within a cooperative governance framework.  Sigh.... Miles
>>
> Welcome to the club. I've been wondering about that same issue with
> regards to getting adoption of BCP38 for over a decade. :-)
>
Well, seriously, though - people do respond to large-scale ddos attacks, 
as well as to things like propagation of corrupted routing BGP tables - 
both operationally, and sometimes legally.  What are the ways that 
people deal with those who are propagating such information, when they 
don't cooperate, and particularly when they don't cooperate 
intentionally?  What recourse comes into the picture?

CERT comes to mind.  So does the CFAA (Computer Fraud and Abuse Act).  
But what about general principles for institutional response?

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Tue Apr 15 10:27:14 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED7571A06D1 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:27:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 pntvhxtaJZEj for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:27:06 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B0C401A063C for <ietf@ietf.org>; Tue, 15 Apr 2014 10:27:06 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.149.140]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3FHQp9f017010 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Apr 2014 10:27:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397582823; bh=UbGgOTwoj2rzeI5dGuc/X5Rc6k/yp7PAufBjnmWz83I=; h=Date:To:From:Subject:In-Reply-To:References; b=ovCwX22dyDkMVuAniGWpvUBIAl1bKaCZUnKhgUjwsZKGCgV1C5XupoyahE66pvqqH W2g67tOWflYBn6AvYkfVMnnePonoU04XU2WCTMKLkPWC0mdS2pfvoRavtzq1pOrRWP Ebmztjdw9+MV5N/zQomb6p1yMlkZH5kObsMmbzEU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397582823; i=@elandsys.com; bh=UbGgOTwoj2rzeI5dGuc/X5Rc6k/yp7PAufBjnmWz83I=; h=Date:To:From:Subject:In-Reply-To:References; b=BXeCVW1gxj6gwajzFIIXtvEPTaokvwQWlbehi6Ca5jLf2ozhFbtARq4hWtFu5QOf7 eW85vvjNf+uWavG676DH7Dk/yxixZ+fL5EM4aTVJcwkDgutYZDUZaD+zeZDrKo2Uh9 KZuAS/CAqP0EwVzz4WWwiCVk28yWCRmvs7I9SPRo=
Message-Id: <6.2.5.6.2.20140415075428.0774cea8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 15 Apr 2014 09:23:22 -0700
To: Miles Fidelman <mfidelman@meetinghouse.net>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534C82EC.5040001@meetinghouse.net>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <6.2.5.6.2.20140414153913.0d0fe480@resistor.net> <534C82EC.5040001@meetinghouse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Z30m_jK8XcSsA2Dacwpiy1l-8Sg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 17:27:12 -0000

Hi Miles,
At 17:53 14-04-2014, Miles Fidelman wrote:
>Depends on what you mean by "significant."

[snip]

>Now, if you're an ISP or ESP that makes money off of sending bulk 
>email, or providing a home for outbound spammers, maybe you don't 
>consider list traffic to be "significant."  But if you're an 
>individual email USER - I expect that one or two email lists 
>represent the MOST significant part of your email stream.

If the choice is to:

   (a) make money

   (b) put effort into what is in the interest of an individual user

What would people actually do?

What I mean by the word "significant" is what will make a corporation 
think thrice before it does anything against the interests of that 
group of people.  There were a lot of messages on the various mailing 
lists where the topic has been raised.  In my opinion there hasn't 
been any results up to now.

Regards,
S. Moonesamy  


From nobody Tue Apr 15 10:39:07 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A4CF1A0376 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.438
X-Spam-Level: 
X-Spam-Status: No, score=-98.438 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 A5q3EnhHxWdD for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:39:00 -0700 (PDT)
Received: from mail.winserver.com (ftp.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 97AF91A0366 for <ietf@ietf.org>; Tue, 15 Apr 2014 10:39:00 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2786; t=1397583535; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=w5lwpf+PjVlj/QfBHhL2IzrUJY4=; b=dA7QcHNSt+E0swrY+QDR M4EOgXa6TFgq8PaB9CNuEAbW15Lq446j35cUAtLawwO/azs+P6SxUkUZ4ZgoFBtb eDk3DVqd23mzvlevyLSWcuJ/hSykybNlkvkPDXD1brGnVEtZy343byClvZimLt4L G8RLeiJeuqBx0nC49tZ4HtI=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 13:38:55 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 692112101.3.3336; Tue, 15 Apr 2014 13:38:54 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2786; t=1397583466; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=kqupiUq axZKk8AP0WWH8dL/N+uUdeya1cNV/Rcpc+xc=; b=iRTcHPWPweZ3j1Xcjv/nEeg h6f9kdu9tq9BIik1nCptXSo/g+gPnLxohe70Fo7a03GgRNJuCwaPnoeqcXkrLBlv GEQ+m5YgSWeIi91TvWPR6RmXyJKQFJZyZcPRNtA0jRUtT6oB6k9Fkp4vrtKl76lS iX3H7Xou+1H6GTo5D3lw=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 13:37:46 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 711641703.9.9980; Tue, 15 Apr 2014 13:37:44 -0400
Message-ID: <534D6EAA.7010100@isdg.net>
Date: Tue, 15 Apr 2014 13:38:50 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, Brian E Carpenter <brian.e.carpenter@gmail.com>,  IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net>
In-Reply-To: <534D5516.7060902@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aR_5nMEaLxclkJ4IubqR7CGT8as
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 17:39:05 -0000

On 4/15/2014 11:49 AM, Dave Crocker wrote:
> On 4/14/2014 6:45 PM, Brian E Carpenter wrote:
>> I thought that standard operating procedure in the IT industry
>> was: if you roll something out and it causes serious breakage to
>> some of your users, you roll it back as soon as possible.
>>
>> Why hasn't Yahoo rolled back its 'reject' policy by now?
>
>
> As the most-recent public statement from Yahoo, this might have some
> tidbits in it that are relevant to your question:
>
>
>
> http://yahoo.tumblr.com/post/82426971544/an-update-on-our-dmarc-policy-to-protect-our-users

Thanks for the link.

Yes, it does provide some insight, but it would be nice if YAHOO made 
an official statement to provide vendors with planning decisions.

This is GOOD NEWS.

What it means that POLICY has won. I believe a policy-based DKIM 
framework is best and I invested in ADSP and its extensions.   Many 
never believed in ADSP or policy based protocols but you have changed 
your position and now promote DMARC as the way to go.  Thats great Dave.

But as I have been saying and largely ignored, it didn't still solve 
the problem unless the MLM supported the handling of restricted 
policies as well -- gracefully.  It doesn't matter if its ADSP or DMARC.

Yahoo has FORCE the issue so in that way, I am happy.

What it means is that I will now begin exploring DMARC implementation 
into our already laid out DKIM framework using ADSP.  Maybe we can 
finally get some payoff and value from all this DKIM work after all!!

I have to note the yahoo.com impact on our system was low. The few 
yahoo.com accounts in our support list was down to four and this was 
going on since January with no complaints.  But the fact, Yahoo hasn't 
roll back or relaxed its policy in over 4 months, DMARC is probably 
here to stay now!!

As the Jeff says:

    "With stricter DMARC policies, users are safer, and the
     bad guys will be in a tough spot. More importantly,
     verified senders will unlock a massive wave of innovation
     and advancement for all our inboxes."

Its time for the IETF to support DMARC.  We can do this using DMARC 
Extensions. Maybe Murray can consider writing DMARC extensions like 
ATPS  but using DMARC as the base call.  It should be a minor change 
to the ATPS specs.

I can see additional DMARC extensions for other advancements, but the 
main one is about managing 3rd party authorized domain to satisfy the 
"signing/sent on behalf of" design need that yahoo says is required:

    "Yahoo requires external email service providers, such as
     those who manage distribution lists, to cease using unsigned
     â€œsent fromâ€� mail, and switch to a more accurate â€œsent on
     behalf ofâ€� policy."

What is this so called "more accurate" method?

-- 
HLS



From nobody Tue Apr 15 10:53:10 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2071A036F for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.798
X-Spam-Level: 
X-Spam-Status: No, score=0.798 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 05OgzM3Ktcvk for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 10:53:07 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 6A17A1A01E7 for <ietf@ietf.org>; Tue, 15 Apr 2014 10:53:06 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id E177DCC09B for <ietf@ietf.org>; Tue, 15 Apr 2014 13:53:02 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kxw9TXWUNu+U for <ietf@ietf.org>; Tue, 15 Apr 2014 13:52:58 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 43091CC093 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:52:58 -0400 (EDT)
Message-ID: <534D71F9.3070108@meetinghouse.net>
Date: Tue, 15 Apr 2014 13:52:57 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D6EAA.7010100@isdg.net>
In-Reply-To: <534D6EAA.7010100@isdg.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_czElzyMw1NhSOWNJeMGjcF6-iM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 17:53:09 -0000

Hector Santos wrote:
> On 4/15/2014 11:49 AM, Dave Crocker wrote:
>> On 4/14/2014 6:45 PM, Brian E Carpenter wrote:
>>> I thought that standard operating procedure in the IT industry
>>> was: if you roll something out and it causes serious breakage to
>>> some of your users, you roll it back as soon as possible.
>>>
>>> Why hasn't Yahoo rolled back its 'reject' policy by now?
>>
>>
>> As the most-recent public statement from Yahoo, this might have some
>> tidbits in it that are relevant to your question:
>>
>>
>>
>> http://yahoo.tumblr.com/post/82426971544/an-update-on-our-dmarc-policy-to-protect-our-users 
>>
>
> Thanks for the link.
>
> Yes, it does provide some insight, but it would be nice if YAHOO made 
> an official statement to provide vendors with planning decisions.
>
> This is GOOD NEWS.
>
> What it means that POLICY has won. I believe a policy-based DKIM 
> framework is best and I invested in ADSP and its extensions. Many 
> never believed in ADSP or policy based protocols but you have changed 
> your position and now promote DMARC as the way to go. Thats great Dave.
>
> But as I have been saying and largely ignored, it didn't still solve 
> the problem unless the MLM supported the handling of restricted 
> policies as well -- gracefully.  It doesn't matter if its ADSP or DMARC.
>
> Yahoo has FORCE the issue so in that way, I am happy.
>
> What it means is that I will now begin exploring DMARC implementation 
> into our already laid out DKIM framework using ADSP.  Maybe we can 
> finally get some payoff and value from all this DKIM work after all!!
>
> I have to note the yahoo.com impact on our system was low. The few 
> yahoo.com accounts in our support list was down to four and this was 
> going on since January with no complaints.  But the fact, Yahoo hasn't 
> roll back or relaxed its policy in over 4 months, DMARC is probably 
> here to stay now!!
>
> As the Jeff says:
>
>    "With stricter DMARC policies, users are safer, and the
>     bad guys will be in a tough spot. More importantly,
>     verified senders will unlock a massive wave of innovation
>     and advancement for all our inboxes."
>
> Its time for the IETF to support DMARC.  We can do this using DMARC 
> Extensions. Maybe Murray can consider writing DMARC extensions like 
> ATPS  but using DMARC as the base call.  It should be a minor change 
> to the ATPS specs.
>
> I can see additional DMARC extensions for other advancements, but the 
> main one is about managing 3rd party authorized domain to satisfy the 
> "signing/sent on behalf of" design need that yahoo says is required:
>
>    "Yahoo requires external email service providers, such as
>     those who manage distribution lists, to cease using unsigned
>     â€œsent fromâ€� mail, and switch to a more accurate â€œsent on
>     behalf ofâ€� policy."
>
> What is this so called "more accurate" method?
>
And more to the point - what is a standard for representing 
"sent-on-behalf-of" that software developers can rely on when making 
changes to list software and user agents.  (Or even better, a way to 
represent it that allows standard reply and address functions to 
continue working tranparently).

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Tue Apr 15 11:10:50 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90C1A1A03D7 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 11:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.528
X-Spam-Level: **
X-Spam-Status: No, score=2.528 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_MUTUALBENEFIT=2, RP_MATCHES_RCVD=-0.272] autolearn=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 9-t2W0bRK0qy for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 11:10:46 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id EC2491A04F1 for <ietf@ietf.org>; Tue, 15 Apr 2014 11:10:43 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D18482CC95 for <ietf@ietf.org>; Tue, 15 Apr 2014 21:10:39 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3m7_3nLJeq8b for <ietf@ietf.org>; Tue, 15 Apr 2014 21:10:39 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0ADF52CC48 for <ietf@ietf.org>; Tue, 15 Apr 2014 21:10:39 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: "why I quit writing internet standards"
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <201404142144.s3ELipR8014504@hobgoblin.ariadne.com>
Date: Tue, 15 Apr 2014 21:10:38 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com>
To: "ietf@ietf.org List" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qfhk90DjgbEKwRwVhi67Erw86E4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 18:10:48 -0000

Vidya brings up some interesting points, some of it IETF-related but =
also some that relates how the world is evolving. For instance, the open =
source trend.=20

But to pick another trend, so many things can now be built without any =
permission from anyone - including SDOs. We call this permissionless =
innovation, and it is a good thing. The Internet has grown, and it is =
not our task at the IETF to do everything, we should, however, care =
about evolving the core protocols.

One of Vidya's examples was the Internet of Things, and she wondered how =
little standards work is needed. But that is not an accident, it is by =
design. =46rom my perspective what happened was that link layer =
technology developed to make the physical level connectivity possible =
and existing Internet protocols were sufficient to do 98% of what was =
needed. As an example, I see most of Internet of Things gadgets running =
on the web protocol stack. Because it just works, it is widely =
available, goes through every firewall, and so on. These are good =
things. As a consequence, places like IETF or IEEE are not developing =
thousands of applications for the Internet of Things, the vendors are. =
The union of the meter manufacturers are. And so on. There is still some =
core standards development necessary - as witnessed at the IETF in the =
form of mesh routing protocol work, various IPv6 over Foo working =
groups, the 6LO* working groups, the lightweight web/security protocol =
working groups, and so on. Fundamental and necessary efforts, but in =
numbers 1000x less than efforts higher up.

The IETF has its place, but it is more about being useful to the open =
source efforts, the permissionless innovators, and the like than trying =
to compete with them. How can we do this best? One avenue is working on =
tools that the permissionless innovation, SDN, virtualisation, IOT, and =
web development revolutions need underneath. We have active developments =
at the IETF on all of those fronts, and I suspect more is coming.

There are certainly also IETF process/organisation things that we should =
work on to improve. We do. Here are some things that I would like to =
see:

  o  Are there ways to work to mutual benefit with open source efforts =
(those that would benefit from an IETF-like environment)?

  o  Recognising that many successful cases of Internet technology =
development have been about some people somewhere making something that =
later required standards at which point the IETF took over. Learning to =
do this, and learning to do it well is important.

  o  How can we better build specs to (rough) consensus, including =
making sure that (an understood) vocal minority opinion does not block =
progress?

  o  More focus on running code.

(All my personal opinions, of course.)

Jari


From nobody Tue Apr 15 11:16:47 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 229EC1A02E3 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 11:16:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_PASS=-0.001] autolearn=ham
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 0Jawr0K2PkQx for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 11:16:41 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.4]) by ietfa.amsl.com (Postfix) with ESMTP id 059051A01FB for <ietf@ietf.org>; Tue, 15 Apr 2014 11:16:40 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES532.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Tue, 15 Apr 2014 14:16:34 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Hector Santos <hsantos@isdg.net>, IETF Discussion <ietf@ietf.org>
Subject: RE: What I've been wondering about the DMARC problem
Thread-Topic: What I've been wondering about the DMARC problem
Thread-Index: AQHPWMKqMz/vACTd+U64Jx1dUV/pjJsTNKgA//++/AA=
Date: Tue, 15 Apr 2014 18:16:33 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D4728F@USCLES544.agna.amgreetings.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D6EAA.7010100@isdg.net>
In-Reply-To: <534D6EAA.7010100@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ngDX8WCkFqcGM66E0P0JSWM9sPo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 18:16:46 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0ZiBbbWFpbHRvOmll
dGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEhlY3RvciBTYW50b3MNCj4gU2VudDog
VHVlc2RheSwgQXByaWwgMTUsIDIwMTQgMTozOSBQTQ0KPiBUbzogZGNyb2NrZXJAYmJpdy5uZXQ7
IEJyaWFuIEUgQ2FycGVudGVyOyBJRVRGIERpc2N1c3Npb24NCj4gU3ViamVjdDogUmU6IFdoYXQg
SSd2ZSBiZWVuIHdvbmRlcmluZyBhYm91dCB0aGUgRE1BUkMgcHJvYmxlbQ0KPiANCj4gT24gNC8x
NS8yMDE0IDExOjQ5IEFNLCBEYXZlIENyb2NrZXIgd3JvdGU6DQo+ID4gT24gNC8xNC8yMDE0IDY6
NDUgUE0sIEJyaWFuIEUgQ2FycGVudGVyIHdyb3RlOg0KPiA+PiBJIHRob3VnaHQgdGhhdCBzdGFu
ZGFyZCBvcGVyYXRpbmcgcHJvY2VkdXJlIGluIHRoZSBJVCBpbmR1c3RyeQ0KPiA+PiB3YXM6IGlm
IHlvdSByb2xsIHNvbWV0aGluZyBvdXQgYW5kIGl0IGNhdXNlcyBzZXJpb3VzIGJyZWFrYWdlIHRv
IHNvbWUNCj4gPj4gb2YgeW91ciB1c2VycywgeW91IHJvbGwgaXQgYmFjayBhcyBzb29uIGFzIHBv
c3NpYmxlLg0KPiA+Pg0KPiA+PiBXaHkgaGFzbid0IFlhaG9vIHJvbGxlZCBiYWNrIGl0cyAncmVq
ZWN0JyBwb2xpY3kgYnkgbm93Pw0KPiA+DQo+ID4NCj4gPiBBcyB0aGUgbW9zdC1yZWNlbnQgcHVi
bGljIHN0YXRlbWVudCBmcm9tIFlhaG9vLCB0aGlzIG1pZ2h0IGhhdmUgc29tZQ0KPiA+IHRpZGJp
dHMgaW4gaXQgdGhhdCBhcmUgcmVsZXZhbnQgdG8geW91ciBxdWVzdGlvbjoNCj4gPg0KPiA+DQo+
ID4NCj4gPiBodHRwOi8veWFob28udHVtYmxyLmNvbS9wb3N0LzgyNDI2OTcxNTQ0L2FuLXVwZGF0
ZS1vbi1vdXItZG1hcmMtDQo+IHBvbGljeQ0KPiA+IC10by1wcm90ZWN0LW91ci11c2Vycw0KPiAN
Cj4gVGhhbmtzIGZvciB0aGUgbGluay4NCj4gDQo+IFllcywgaXQgZG9lcyBwcm92aWRlIHNvbWUg
aW5zaWdodCwgYnV0IGl0IHdvdWxkIGJlIG5pY2UgaWYgWUFIT08gbWFkZSBhbg0KPiBvZmZpY2lh
bCBzdGF0ZW1lbnQgdG8gcHJvdmlkZSB2ZW5kb3JzIHdpdGggcGxhbm5pbmcgZGVjaXNpb25zLg0K
PiANCg0KSnVzdCBjdXJpb3VzLCB3aGF0IHNvcnQgb2Ygc3RhdGVtZW50IHdvdWxkIHlvdSBsaWtl
IHRvIHNlZT8gSG93IHdvdWxkIGl0IGhlbHAgd2l0aCB2ZW5kb3IgcGxhbm5pbmcgZGVjaXNpb25z
Pw0KDQo+IFRoaXMgaXMgR09PRCBORVdTLg0KPiANCj4gV2hhdCBpdCBtZWFucyB0aGF0IFBPTElD
WSBoYXMgd29uLiBJIGJlbGlldmUgYSBwb2xpY3ktYmFzZWQgREtJTQ0KPiBmcmFtZXdvcmsgaXMg
YmVzdCBhbmQgSSBpbnZlc3RlZCBpbiBBRFNQIGFuZCBpdHMgZXh0ZW5zaW9ucy4gICBNYW55DQo+
IG5ldmVyIGJlbGlldmVkIGluIEFEU1Agb3IgcG9saWN5IGJhc2VkIHByb3RvY29scyBidXQgeW91
IGhhdmUgY2hhbmdlZCB5b3VyDQo+IHBvc2l0aW9uIGFuZCBub3cgcHJvbW90ZSBETUFSQyBhcyB0
aGUgd2F5IHRvIGdvLiAgVGhhdHMgZ3JlYXQgRGF2ZS4NCj4gDQoNCkkndmUgYmVsaWV2ZWQgaW4g
cG9saWN5IGZvciBxdWl0ZSBzb21lIHRpbWUgKHByZS1kYXRpbmcgU1NQL0FEU1ApLiBUaGUgb25s
eSBwcm9ibGVtIHdpdGggQURTUCB3YXMgdGhhdCB3ZSBhZ3JlZWQgdG8gYSBjb21wcm9taXNlIHRo
YXQgbGVmdCBpdCB0b28gaW5mbGV4aWJsZSBhbmQgY3JpcHBsZWQuIExlc3NvbiBsZWFybmVkLg0K
DQo+IEJ1dCBhcyBJIGhhdmUgYmVlbiBzYXlpbmcgYW5kIGxhcmdlbHkgaWdub3JlZCwgaXQgZGlk
bid0IHN0aWxsIHNvbHZlIHRoZSBwcm9ibGVtDQo+IHVubGVzcyB0aGUgTUxNIHN1cHBvcnRlZCB0
aGUgaGFuZGxpbmcgb2YgcmVzdHJpY3RlZCBwb2xpY2llcyBhcyB3ZWxsIC0tDQo+IGdyYWNlZnVs
bHkuICBJdCBkb2Vzbid0IG1hdHRlciBpZiBpdHMgQURTUCBvciBETUFSQy4NCj4gDQo+IFlhaG9v
IGhhcyBGT1JDRSB0aGUgaXNzdWUgc28gaW4gdGhhdCB3YXksIEkgYW0gaGFwcHkuDQo+IA0KPiBX
aGF0IGl0IG1lYW5zIGlzIHRoYXQgSSB3aWxsIG5vdyBiZWdpbiBleHBsb3JpbmcgRE1BUkMgaW1w
bGVtZW50YXRpb24gaW50bw0KPiBvdXIgYWxyZWFkeSBsYWlkIG91dCBES0lNIGZyYW1ld29yayB1
c2luZyBBRFNQLiAgTWF5YmUgd2UgY2FuIGZpbmFsbHkgZ2V0DQo+IHNvbWUgcGF5b2ZmIGFuZCB2
YWx1ZSBmcm9tIGFsbCB0aGlzIERLSU0gd29yayBhZnRlciBhbGwhIQ0KPiANCg0KSSdtIGxvb2tp
bmcgZm9yd2FyZCB0byBoZWFyaW5nIHlvdXIgdGhvdWdodHMgYW5kIHF1ZXN0aW9ucyBhbmQgSSdt
IHN1cmUgb3RoZXJzIGRvIGFzIHdlbGwuIElzIHRoaXMgbGlzdCB0aGUgYmVzdCBwbGFjZSBmb3Ig
dGhpcyBvciBpcyB0aGVyZSBzb21ld2hlcmUgZWxzZSBtb3JlIGFwcHJvcHJpYXRlPw0KDQo+IEkg
aGF2ZSB0byBub3RlIHRoZSB5YWhvby5jb20gaW1wYWN0IG9uIG91ciBzeXN0ZW0gd2FzIGxvdy4g
VGhlIGZldw0KPiB5YWhvby5jb20gYWNjb3VudHMgaW4gb3VyIHN1cHBvcnQgbGlzdCB3YXMgZG93
biB0byBmb3VyIGFuZCB0aGlzIHdhcyBnb2luZw0KPiBvbiBzaW5jZSBKYW51YXJ5IHdpdGggbm8g
Y29tcGxhaW50cy4gIEJ1dCB0aGUgZmFjdCwgWWFob28gaGFzbid0IHJvbGwgYmFjayBvcg0KPiBy
ZWxheGVkIGl0cyBwb2xpY3kgaW4gb3ZlciA0IG1vbnRocywgRE1BUkMgaXMgcHJvYmFibHkgaGVy
ZSB0byBzdGF5IG5vdyEhDQo+IA0KDQpIZWN0b3IsIFlhaG9vIGltcGxlbWVudGVkIHRoZSBjaGFu
Z2UgYSB3ZWVrIGFnbyBGcmlkYXksIG5vdCA0IG1vbnRocyBhZ28uIEknbSBzdXJlIHRoZXkgaGF2
ZSByZWNlaXZlZCBjb21wbGFpbnRzLiANCg0KSSdkIGxvdmUgaXQgaWYgYXQgc29tZSBsYXRlciBw
b2ludCBzb21lb25lIHRoYXQgd2FzIGludm9sdmVkIGluIHRoZSBZYWhvbyBkZWNpc2lvbiBwcm9j
ZXNzIHdyaXRlcyBzb21ldGhpbmcgYWJvdXQgdGhlIGV2ZW50cyB0aGF0IHN0YXJ0ZWQgdGhlbSB0
aGlua2luZyBhYm91dCBtYWtpbmcgdGhlIGNoYW5nZSBhbmQgdGhlIGRlY2lzaW9uIG1ha2luZyBw
cm9jZXNzIGludm9sdmVkLiBJdCB3b3VsZCBiZSBuaWNlIHRvIGhhdmUgaW5zaWdodCBpbnRvIGhv
dyBhbmQgd2h5IHRoZXkgZGVjaWRlZCB0byBnbyBhaGVhZCB3aXRob3V0IGdpdmluZyBhbnlvbmUg
cHJpb3Igbm90aWNlLiBIb3cgZGlkIGl0IGltcGFjdCBjdXN0b21lciBzdXBwb3J0IGFuZCB3aGF0
IGtpbmQgb2YgcGxhbiB3YXMgaW4gcGxhY2UgKGFuZCBob3cgd2VsbCBkaWQgaXQgd29yayk/IEhv
dyBkaWQgdGhleSBkZWFsIHdpdGggcGFydG5lcnMgYW5kIHZlbmRvcnM/IEluIG90aGVyIHdvcmRz
IGl0IHdvdWxkIGJlIGEgY29tcGVsbGluZyBjYXNlIHN0dWR5IHdoZXRoZXIgb25lIHRoaW5rcyB0
aGVpciBhY3Rpb24gd2FzIGdvb2Qgb3IgaG9ycmlibGUuDQoNCj4gQXMgdGhlIEplZmYgc2F5czoN
Cj4gDQo+ICAgICAiV2l0aCBzdHJpY3RlciBETUFSQyBwb2xpY2llcywgdXNlcnMgYXJlIHNhZmVy
LCBhbmQgdGhlDQo+ICAgICAgYmFkIGd1eXMgd2lsbCBiZSBpbiBhIHRvdWdoIHNwb3QuIE1vcmUg
aW1wb3J0YW50bHksDQo+ICAgICAgdmVyaWZpZWQgc2VuZGVycyB3aWxsIHVubG9jayBhIG1hc3Np
dmUgd2F2ZSBvZiBpbm5vdmF0aW9uDQo+ICAgICAgYW5kIGFkdmFuY2VtZW50IGZvciBhbGwgb3Vy
IGluYm94ZXMuIg0KPiANCj4gSXRzIHRpbWUgZm9yIHRoZSBJRVRGIHRvIHN1cHBvcnQgRE1BUkMu
ICBXZSBjYW4gZG8gdGhpcyB1c2luZyBETUFSQw0KPiBFeHRlbnNpb25zLiBNYXliZSBNdXJyYXkg
Y2FuIGNvbnNpZGVyIHdyaXRpbmcgRE1BUkMgZXh0ZW5zaW9ucyBsaWtlIEFUUFMNCj4gYnV0IHVz
aW5nIERNQVJDIGFzIHRoZSBiYXNlIGNhbGwuICBJdCBzaG91bGQgYmUgYSBtaW5vciBjaGFuZ2Ug
dG8gdGhlIEFUUFMNCj4gc3BlY3MuDQo+IA0KPiBJIGNhbiBzZWUgYWRkaXRpb25hbCBETUFSQyBl
eHRlbnNpb25zIGZvciBvdGhlciBhZHZhbmNlbWVudHMsIGJ1dCB0aGUNCj4gbWFpbiBvbmUgaXMg
YWJvdXQgbWFuYWdpbmcgM3JkIHBhcnR5IGF1dGhvcml6ZWQgZG9tYWluIHRvIHNhdGlzZnkgdGhl
DQo+ICJzaWduaW5nL3NlbnQgb24gYmVoYWxmIG9mIiBkZXNpZ24gbmVlZCB0aGF0IHlhaG9vIHNh
eXMgaXMgcmVxdWlyZWQ6DQo+IA0KDQpPbiBvbmUgbGV2ZWwgdGhlcmUgYWxyZWFkeSBhcmUgd2F5
cyBmb3Igc2F0aXNmeWluZyB0aGUgM3JkIHBhcnR5IGF1dGhvcml6ZWQgZG9tYWluIGlzc3VlLiBB
IGRvbWFpbiBjb3VsZCB1c2UgU1BGIChlaXRoZXIgYnkgc3BlY2lmeWluZyBob3N0cy9JUHMgb3Ig
dXNpbmcgYW4gaW5jbHVkZSBpbiB0aGUgU1BGIHJlY29yZCkgZm9yIGEgM3JkIHBhcnR5IGRvbWFp
bi4gQW5vdGhlciBtZXRob2Qgd291bGQgYmUgdG8gcHJvdmlkZSBES0lNIHNpZ25pbmcga2V5cyB0
byB0aGUgM3JkIHBhcnR5LiBZZXQgYSAzcmQgd2F5IGlzIHRvIGRlbGVnYXRlIGEgc3ViZG9tYWlu
IHNvIHRoYXQgdGhlIDNyZCBwYXJ0eSBjYW4gbWFuYWdlIHRoZXNlIHRoaW5ncyBvbiB0aGVpciBv
d24uIFRoZXJlIGFyZSBzb21lIGJlc3QgcHJhY3RpY2UgZG9jdW1lbnRzIHB1Ymxpc2hlZCBhdCBt
YWF3Zy5vcmcgdGhhdCBtaWdodCBiZSB1c2VmdWwuIElmIHdoYXQgeW91IG1lYW4gaXMgYSBtZWNo
YW5pc20gdG8gc3BlY2lmeSByYW5kb20gM3JkIHBhcnRpZXMgdGhhdCBhbiBlbmQgdXNlciB3aXNo
ZXMgdG8gdXNlLCB0aGVuIG5vIHRoZXJlIGlzIG5vdCBhIG1lY2hhbmlzbSBhbmQgSSBkb24ndCBr
bm93IG9mIGFueW9uZSB3aG8gaGFzIHB1dCBmb3J0aCB3aGF0IEkgd291bGQgY29uc2lkZXIgYSB3
b3JrYWJsZSBtb2RlbC4NCg0KPiAgICAgIllhaG9vIHJlcXVpcmVzIGV4dGVybmFsIGVtYWlsIHNl
cnZpY2UgcHJvdmlkZXJzLCBzdWNoIGFzDQo+ICAgICAgdGhvc2Ugd2hvIG1hbmFnZSBkaXN0cmli
dXRpb24gbGlzdHMsIHRvIGNlYXNlIHVzaW5nIHVuc2lnbmVkDQo+ICAgICAg4oCcc2VudCBmcm9t
4oCdIG1haWwsIGFuZCBzd2l0Y2ggdG8gYSBtb3JlIGFjY3VyYXRlIOKAnHNlbnQgb24NCj4gICAg
ICBiZWhhbGYgb2bigJ0gcG9saWN5LiINCj4gDQo+IFdoYXQgaXMgdGhpcyBzbyBjYWxsZWQgIm1v
cmUgYWNjdXJhdGUiIG1ldGhvZD8NCj4gDQoNCk5vdCBzdXJlIGV4YWN0bHkgd2hhdCBoZSBtZWFu
cy4NCg0KTWlrZQ0K


From nobody Tue Apr 15 11:27:16 2014
Return-Path: <bzeeb-lists@lists.zabbadoz.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 404CF1A01DA for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 11:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.55
X-Spam-Level: 
X-Spam-Status: No, score=-1.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35] autolearn=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 FGreqSnNp4xl for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 11:27:11 -0700 (PDT)
Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) by ietfa.amsl.com (Postfix) with ESMTP id 22B7D1A01FB for <ietf@ietf.org>; Tue, 15 Apr 2014 11:27:11 -0700 (PDT)
Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 73E4325D3871; Tue, 15 Apr 2014 18:27:07 +0000 (UTC)
Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 7A2A3C22B9C; Tue, 15 Apr 2014 18:27:06 +0000 (UTC)
X-Virus-Scanned: amavisd-new at sbone.de
Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id dxvX_d9E_0JV; Tue, 15 Apr 2014 18:27:05 +0000 (UTC)
Received: from [IPv6:fde9:577b:c1a9:4410:7c90:1de7:5946:cc76] (unknown [IPv6:fde9:577b:c1a9:4410:7c90:1de7:5946:cc76]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 47B3BC22B81; Tue, 15 Apr 2014 18:27:03 +0000 (UTC)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
In-Reply-To: <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net>
Date: Tue, 15 Apr 2014 18:26:56 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <1BCA1D40-E535-4CF4-A9FE-EF5CDC1D1A5C@lists.zabbadoz.net>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oTI1IQXNZFtlQppybbfvbv4vtgU
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 18:27:15 -0000

On 15 Apr 2014, at 18:10 , Jari Arkko <jari.arkko@piuha.net> wrote:

>  o  How can we better build specs to (rough) consensus, including =
making sure that (an understood) vocal minority opinion does not block =
progress?

Apply KISS . . .

>  o  More focus on running code.

. . . after this.

=97=20
Bjoern A. Zeeb             "Come on. Learn, goddamn it.", WarGames, 1983


From nobody Tue Apr 15 11:48:58 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6BBA1A03A8 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 11:48:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 Dz0VmSECQHfC for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 11:48:55 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 198121A0262 for <ietf@ietf.org>; Tue, 15 Apr 2014 11:48:54 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1Wa8Pb-0001sb-8n; Tue, 15 Apr 2014 18:48:51 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 8AEE5580893; Tue, 15 Apr 2014 14:48:50 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397587730; bh=3g5Q+Q6u8U2wbs0sJcU4geRtCmZt06q+uwajYX46Qf0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=yhJrE+KKjG0WLUM+C9R00A0hD8pLEzAyEZdvU64hAYJNKi4h8qWlfRV0iqMISb54W 6hPW0mZLnEbGQunPyYaz2grYz5YwDqoVMjWsZ2k/WQhymQNbWCeefHLjoRLTM4S673 FajXaOPVVcjEc0wduftJk/vezLKigHbs4EhyEQAg=
Date: Tue, 15 Apr 2014 14:48:50 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: John R Levine <johnl@taugh.com>
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <20140415184850.GD4456@thunk.org>
References: <20140414220233.32201.qmail@joyce.lan> <20123.1397567461@sandelman.ca> <20140415153047.GA4456@thunk.org> <alpine.BSF.2.00.1404151151490.37785@joyce.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.BSF.2.00.1404151151490.37785@joyce.lan>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JOo6AN4aBvR62b8tsMxp94eahNA
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 18:48:56 -0000

On Tue, Apr 15, 2014 at 11:54:20AM -0400, John R Levine wrote:
> >But only for yahoo.com users.  Somehow, I have a very hard time
> >feeling sympathetic about their plight.
> 
> No, it also screws up anyone who wants to correspond with Yahoo users who
> happen to correspond via shared mailing lists.

Yes, it means it will be harder to correspond with Yahoo users.  Maybe
their friends who want to talk to those yahoo users will also help
convince them to use another mail provider.

					- Ted


From nobody Tue Apr 15 12:25:39 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 403B21A0186 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 12:25:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 QOriUgU0A5hj for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 12:25:34 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 58BEE1A068D for <ietf@ietf.org>; Tue, 15 Apr 2014 12:25:34 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.149.140]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3FJP8L2016390 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Apr 2014 12:25:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397589920; bh=oxRtuTyHPey/W+zMzj7pwrkGJKL+weGQFHnQeROHKwg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YuDa9nK3fQhjpBWTXTxGEx2KZ7Goe5UKbkma4g9EiTVdNCSFVo2pc2AM6FxJw5MaZ L5+TCPMvBDnmpOJeF+6fI1b3f8sy4Z5CzY3ERDCjqDFJW38KVSPb/iuaZhhFUWOPdQ Kqc038QNdESYm/7/yQoHAB781nBfdl/UKLP5FTTk=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397589920; i=@elandsys.com; bh=oxRtuTyHPey/W+zMzj7pwrkGJKL+weGQFHnQeROHKwg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=41hK76YwWSn+Q94Nu+sxnQtgef+ST6O+xxLYvriFS9WDYbylTcalqrtQwGkCDPnRZ KqYZvCg/45uX/StIqBxPJqhDuyBWnyBHfP5PTRB4bdlwJ9NpbdXODIGt+n7DLQhxmh jK6nIpSHhwAQv1hN2+Had4z2rlwGmO2SfyULQd0s=
Message-Id: <6.2.5.6.2.20140415111633.0da3d030@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 15 Apr 2014 12:23:44 -0700
To: Dave Cridland <dave@cridland.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.g mail.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com> <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1hMAgC9UGXzKUBgSqStOn8xsTzc
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 19:25:38 -0000

Hi Dave,
At 00:42 15-04-2014, Dave Cridland wrote:
>Given the expense and difficulty of IETF participation for smaller 
>organisations and individuals, it's hard for them to club together 
>and stand up to the 8000lb gorillas.

The above is an obvious problem or difficult situation that people do 
not want to talk about.

Publication in the IETF Stream usually entails giving up change 
control.  Sometimes that does not work out well; see RFC 6109.  The 
process is tedious.  It does not have to be like that if people make 
room for agreement.  In simple terms, people can discuss about X for 
the next three years or there can be a short discussion and a 
solution within the next three months.

The summary of the DMARC BoF is at 
http://www.ietf.org/mail-archive/web/apps-discuss/current/msg10138.html 
According to that message there was agreement for the IETF to take on 
the DMARC base specification.

Regards,
S. Moonesamy 


From nobody Tue Apr 15 12:42:02 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43FB41A07BA for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 12:42:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.302
X-Spam-Level: 
X-Spam-Status: No, score=-3.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 gO-mcHTpp9uJ for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 12:41:55 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id B4C691A068E for <ietf@ietf.org>; Tue, 15 Apr 2014 12:41:55 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 3D9F6CC094; Tue, 15 Apr 2014 15:41:52 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id DCI-i9TrKZiO; Tue, 15 Apr 2014 15:41:43 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 1A03DCC093; Tue, 15 Apr 2014 15:41:43 -0400 (EDT)
Message-ID: <534D8B76.3020307@meetinghouse.net>
Date: Tue, 15 Apr 2014 15:41:42 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: "ietf@ietf.org List" <ietf@ietf.org>, mailop <mailop@mailop.org>
Subject: re. DMARC - apropos cooperation, or lack there-of by yahoo
References: <1397588475.6407.YahooMailNeo@web125204.mail.ne1.yahoo.com>
In-Reply-To: <1397588475.6407.YahooMailNeo@web125204.mail.ne1.yahoo.com>
X-Forwarded-Message-Id: <1397588475.6407.YahooMailNeo@web125204.mail.ne1.yahoo.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/txSh_zxA6uwJI0ieWyGwoQdhShc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 19:42:00 -0000

Apropos the recent discussion, it strikes me that this exchange of email 
w/ Yahoo might be of interest:

On one of the pages pointed to by Yahoo's blog announcement of their 
DMARC policy change, they posted this invitation: "If you are a 
developer of mailing list software and would like help adding features 
to allow participants from domains with DMARC p=reject, please contact 
us at dmarc-help@yahoo-inc.com."

So... I took them up on it, by sending this:

-------
From: Miles Fidelman [mailto:mfidelman@meetinghouse.net]
Sent: Saturday, April 12, 2014 6:28 PM
To: dmarc-help@yahoo-inc.com
Subject: do you support Original-Authentication-Results?
Folks,
I'm not a mailing list software developer, but I'm sure interested in 
patching the software we use (Sympa).
The most pressing question right now is whether your DMARC 
implementation supports Original-Authentication-Results - which would 
allow us to actually support DMARC transparently to list subscribers.A 
related question is knowing which other large ISPs, who honor p=reject, 
also honor Original-Authentication-Results.
Miles Fidelman
---------------

To which, I received this in response:


-------- Original Message --------
x 	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
	
From: 	Mailing Help <dmarc_help@yahoo.com>
Reply-To: 	Mailing Help <dmarc_help@yahoo.com>
Subject: 	Subject: do you support Original-Authentication-Results?
To: 	mfidelman@meetinghouse.net <mfidelman@meetinghouse.net>
MIME-Version: 	1.0
Content-Type: 	multipart/alternative; 
boundary="833011919-776038816-1397588475=:6407"



Greetings Miles.
Yahoo Mail is not currently supporting OAR headers. Weâ€™re reviewing 
possible solutions in regards to OAR headers and how to act upon them 
from trusted third parties. Our primary goal at this time is to 
eliminate Mail Spoofing for email that does not originate from our mail 
servers.
Iâ€™d like to work with you in the near future if and when weâ€™d like to 
test new changes. Can I add you as a contact Miles?
Cheers,
Kendrick - Yahoo Mail

---------------

Talk about not helpful.

Miles Fidelman



From nobody Tue Apr 15 12:48:41 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 237301A06C4 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 12:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.103
X-Spam-Level: 
X-Spam-Status: No, score=-100.103 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 iX2J7OGzwepB for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 12:48:33 -0700 (PDT)
Received: from mail.santronics.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id CD75D1A0186 for <ietf@ietf.org>; Tue, 15 Apr 2014 12:48:32 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4449; t=1397591306; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=NUlSgojd0W1bmDjVcNlunH3lZNA=; b=VBoX9NOwhE06y0q9L3Tt 4gXqDnJ4rOVWepwwlqk2LoTxsMSAHS/kD/kjgjKYEUgEKdGTwz5YvQ0qIoZrENzg W0utgC3hXQvjzbL2eRcA0lqMQ0Nio0epLyV+UHn65E+HxtcEONP0KTd2hCNPZrFZ kM3Ibjiv85zrHLnO6rnxWTA=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 15:48:26 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 699882339.3.2304; Tue, 15 Apr 2014 15:48:25 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4449; t=1397591236; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=/ZySL0k 1Lt5s3aYXLdyIdXoVrUeC7vxUOR+mFJU4AKE=; b=1gILSAd9m75TwKTWQ+ic7KT sR8E2PyV7S3jz1AvdJWUUsXCtzmIjli2q+vTcuvb3oZoLVa7DDE/g6BHFMqMM5Ia /s24GJXJrSE2ql3A9jw3juvY5SxRS9t2lRLgn6M/FaIB/SYAD9PKTx1sihKtoBRI jsF4u7SzrTN+NZPa0WcY=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 15:47:16 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 719412109.9.9460; Tue, 15 Apr 2014 15:47:15 -0400
Message-ID: <534D8D05.3090601@isdg.net>
Date: Tue, 15 Apr 2014 15:48:21 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "MH Michael Hammer (5304)" <MHammer@ag.com>,  IETF Discussion <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D6EAA.7010100@isdg.net> <CE39F90A45FF0C49A1EA229FC9899B0507D4728F@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D4728F@USCLES544.agna.amgreetings.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nbjfIZud9XokTQj-j9Y-3tpKfPY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 19:48:39 -0000

On 4/15/2014 2:16 PM, MH Michael Hammer (5304) wrote:
>
> Just curious, what sort of statement would you like to see? How would it help with vendor planning decisions?

I think the one provided here, although a link via tumblr, appears to 
be the official Yahoo position and sufficient:

http://yahoomail.tumblr.com/post/82426900353/yahoo-dmarc-policy-change-what-should-senders-do


> I'm looking forward to hearing your thoughts and questions and I'm sure others do as well. Is this list the best place for this or is there somewhere else more appropriate?
>

I don't think the IETF-LIST would be the appropriate place. I would 
think Dave and Murray would take lead here, as the current IETF "reps" 
on DMARC.

> Hector, Yahoo implemented the change a week ago Friday,
> not 4 months ago. I'm sure they have received complaints.

This is a January 10, 2014 transaction for one of the yahoo.com 
subscribers to our support list getting a copy of a yahoo.com user 
mail submission:

**************************************************************************
Wildcat! ESMTP Server v7.0.454.4
SMTP log started at Fri, 10 Jan 2014  22:06:21
Connection Time: 20140110 22:06:21  cid: 00000000 tid: 144C
SSL Enabled: YES
Message Queue: d:\spool\santronics\smtp\47446W
Destination: ##############@yahoo.com
Mail Host IP: 98.136.216.26:25 (mta6.am0.yahoodns.net)
Attempt #1 LastAttempt: n/a
22:06:21.471 ** Opening Connection to host: mta6.am0.yahoodns.net ip: 
98.136.216.26:25
22:06:21.668 S: 220 mta1089.mail.gq1.yahoo.com ESMTP ready
22:06:21.669 C: EHLO secure.winserver.com
22:06:21.770 S: 250-mta1089.mail.gq1.yahoo.com
22:06:21.770 S: 250-PIPELINING
22:06:21.770 S: 250-SIZE 41943040
22:06:21.770 S: 250-8BITMIME
22:06:21.770 S: 250 STARTTLS
22:06:21.770 C: MAIL FROM:<listadmin-winserver@winserver.com>
22:06:21.884 S: 250 sender <listadmin-winserver@winserver.com> ok
22:06:21.884 C: RCPT TO:<lonehorseman82@yahoo.com>
22:06:21.987 S: 250 recipient <lonehorseman82@yahoo.com> ok
22:06:21.987 C: DATA
22:06:22.087 S: 354 go ahead
22:06:23.179 S: 554 5.7.9 Message not accepted for policy reasons. 
See http://postmaster.yahoo.com/errors/postmaster-28.html
22:06:23.180 C: QUIT
22:06:23.180 ** Completed. Elapsed Time: 1700 msecs

Its repeated for the other three yahoo.com users during a submission 
and its recorded in the last four months of logs.  Only yesterday did 
a customer post a support message he was now seeing it his Wildcat! 
List Server setup and logs.  There might have been earlier reports but 
I didn't see them.

>> I can see additional DMARC extensions for other advancements, but the
>> main one is about managing 3rd party authorized domain to satisfy the
>> "signing/sent on behalf of" design need that yahoo says is required:

> On one level there already are ways for satisfying the 3rd party authorized domain issue. A domain could use SPF (either by specifying hosts/IPs or using an include in the SPF record) for a 3rd party domain. Another method would be to provide DKIM signing keys to the 3rd party. Yet a 3rd way is to delegate a subdomain so that the 3rd party can manage these things on their own. There are some best practice documents published at maawg.org that might be useful. If what you mean is a mechanism to specify random 3rd parties that an end user wishes to use, then no there is not a mechanism and I don't know of anyone who has put forth what I would consider a workable model.
>

I have to begin reading the DMARC spec to see what are all the 
boundary conditions, but it means basically able to answer mail 
operation policy questions such as:

   o  Does the domain ever distribute mail?
   o  Do you expect the mail to be unsigned?
   o  Do you expect to sign all mail?
   o  Is your domain the exclusive signer?
   o  Are 3rd party signers allowed?
   o  Are 3rd party signers allowed to strip your original signatures?

This is an illustration of the logical flow when SSP defined policies 
were used to answer the above questions.

   http://www.winserver.com/public/ssp/ssp.htm

>>      "Yahoo requires external email service providers, such as
>>       those who manage distribution lists, to cease using unsigned
>>       â€œsent fromâ€� mail, and switch to a more accurate â€œsent on
>>       behalf ofâ€� policy."
>>
>> What is this so called "more accurate" method?
>>
>
> Not sure exactly what he means.

The 5322.From rewrite suggestion?

-- 
HLS



From nobody Tue Apr 15 13:10:34 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AEA621A01FB for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:10:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6] autolearn=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 M5b19Xq-1FKM for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:10:21 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.31]) by ietfa.amsl.com (Postfix) with ESMTP id 229861A0186 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:10:21 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES533.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Tue, 15 Apr 2014 16:10:17 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Hector Santos <hsantos@isdg.net>, IETF Discussion <ietf@ietf.org>
Subject: RE: What I've been wondering about the DMARC problem
Thread-Topic: What I've been wondering about the DMARC problem
Thread-Index: AQHPWMKqMz/vACTd+U64Jx1dUV/pjJsTNKgA//++/ACAAGU0gP//v8wg
Date: Tue, 15 Apr 2014 20:10:17 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D4742B@USCLES544.agna.amgreetings.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D6EAA.7010100@isdg.net> <CE39F90A45FF0C49A1EA229FC9899B0507D4728F@USCLES544.agna.amgreetings.com> <534D8D05.3090601@isdg.net>
In-Reply-To: <534D8D05.3090601@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/G4D8RJDvTc4aRbjAAZx-RUdeHMY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 20:10:32 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogSGVjdG9yIFNhbnRvcyBb
bWFpbHRvOmhzYW50b3NAaXNkZy5uZXRdDQo+IFNlbnQ6IFR1ZXNkYXksIEFwcmlsIDE1LCAyMDE0
IDM6NDggUE0NCj4gVG86IE1IIE1pY2hhZWwgSGFtbWVyICg1MzA0KTsgSUVURiBEaXNjdXNzaW9u
DQo+IFN1YmplY3Q6IFJlOiBXaGF0IEkndmUgYmVlbiB3b25kZXJpbmcgYWJvdXQgdGhlIERNQVJD
IHByb2JsZW0NCj4gDQo+IE9uIDQvMTUvMjAxNCAyOjE2IFBNLCBNSCBNaWNoYWVsIEhhbW1lciAo
NTMwNCkgd3JvdGU6DQo+ID4NCj4gPiBKdXN0IGN1cmlvdXMsIHdoYXQgc29ydCBvZiBzdGF0ZW1l
bnQgd291bGQgeW91IGxpa2UgdG8gc2VlPyBIb3cgd291bGQgaXQNCj4gaGVscCB3aXRoIHZlbmRv
ciBwbGFubmluZyBkZWNpc2lvbnM/DQo+IA0KPiBJIHRoaW5rIHRoZSBvbmUgcHJvdmlkZWQgaGVy
ZSwgYWx0aG91Z2ggYSBsaW5rIHZpYSB0dW1ibHIsIGFwcGVhcnMgdG8gYmUgdGhlDQo+IG9mZmlj
aWFsIFlhaG9vIHBvc2l0aW9uIGFuZCBzdWZmaWNpZW50Og0KPiANCj4gaHR0cDovL3lhaG9vbWFp
bC50dW1ibHIuY29tL3Bvc3QvODI0MjY5MDAzNTMveWFob28tZG1hcmMtcG9saWN5LQ0KPiBjaGFu
Z2Utd2hhdC1zaG91bGQtc2VuZGVycy1kbw0KPiANCg0KSXQgc291bmRlZCBsaWtlIHlvdSB3ZXJl
IGxvb2tpbmcgZm9yIHNvbWV0aGluZyBtb3JlLg0KDQo+IA0KPiA+IEknbSBsb29raW5nIGZvcndh
cmQgdG8gaGVhcmluZyB5b3VyIHRob3VnaHRzIGFuZCBxdWVzdGlvbnMgYW5kIEknbSBzdXJlDQo+
IG90aGVycyBkbyBhcyB3ZWxsLiBJcyB0aGlzIGxpc3QgdGhlIGJlc3QgcGxhY2UgZm9yIHRoaXMg
b3IgaXMgdGhlcmUgc29tZXdoZXJlIGVsc2UNCj4gbW9yZSBhcHByb3ByaWF0ZT8NCj4gPg0KPiAN
Cj4gSSBkb24ndCB0aGluayB0aGUgSUVURi1MSVNUIHdvdWxkIGJlIHRoZSBhcHByb3ByaWF0ZSBw
bGFjZS4gSSB3b3VsZCB0aGluayBEYXZlDQo+IGFuZCBNdXJyYXkgd291bGQgdGFrZSBsZWFkIGhl
cmUsIGFzIHRoZSBjdXJyZW50IElFVEYgInJlcHMiDQo+IG9uIERNQVJDLg0KPiANCg0KSWYgaXQg
aXMgRE1BUkMgcmVsYXRlZCB0aGVuIElFVEYtRE1BUkMgb3IgRE1BUkMtRElTQ1VTUyB3b3VsZCBw
cm9iYWJseSBiZSB0aGUgYXBwcm9wcmlhdGUgcGxhY2VzLiBJZiBpdCBpcyBzcGVjaWZpYyB0byBN
TE0gcmVsYXRlZCBpc3N1ZXMgYW5kIGhvdyB0aGV5IG1pZ2h0IGJlIGFkZHJlc3NlZCwgSSdtIG5v
dCBzdXJlIGFuZCB3b3VsZCBkZWZlciB0byBvdGhlcnMgYXMgdG8gdGhlIGJlc3QgcGxhY2UgZm9y
IGRpc2N1c3Npb25zLg0KDQo+ID4gSGVjdG9yLCBZYWhvbyBpbXBsZW1lbnRlZCB0aGUgY2hhbmdl
IGEgd2VlayBhZ28gRnJpZGF5LCBub3QgNCBtb250aHMNCj4gPiBhZ28uIEknbSBzdXJlIHRoZXkg
aGF2ZSByZWNlaXZlZCBjb21wbGFpbnRzLg0KPiANCj4gVGhpcyBpcyBhIEphbnVhcnkgMTAsIDIw
MTQgdHJhbnNhY3Rpb24gZm9yIG9uZSBvZiB0aGUgeWFob28uY29tIHN1YnNjcmliZXJzIHRvDQo+
IG91ciBzdXBwb3J0IGxpc3QgZ2V0dGluZyBhIGNvcHkgb2YgYSB5YWhvby5jb20gdXNlciBtYWls
IHN1Ym1pc3Npb246DQo+IA0KDQpBaCwgeW91IGFyZSB0YWxraW5nIGFib3V0IHZhbGlkYXRpbmcg
aW5ib3VuZCBlbWFpbCwgbm90IHRoZSBvdXRib3VuZCBwPXJlamVjdCBwb2xpY3kuIFlhaG9vIHN0
YXJ0ZWQgdmFsaWRhdGluZyBvdmVyIDIgeWVhcnMgYWdvIGFzIGRpZCB0aGUgb3RoZXIgRE1BUkMg
cGFydGljaXBhdGluZyBtYWlsYm94IHByb3ZpZGVycy4gSSdtIGF3YXJlIG9mIG90aGVyIG1haWxi
b3ggcHJvdmlkZXJzIHRoYXQgYXJlIHZhbGlkYXRpbmcgYWdhaW5zdCBETUFSQyBidXQgSSdtIG5v
dCBhd2FyZSBvZiBhIGxpc3Qgb2YgdGhlbSB0aGF0IGlzIGF2YWlsYWJsZS4gDQoNCj4gKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKg0KPiAq
KioqKioqKioqKioqKioqDQo+IFdpbGRjYXQhIEVTTVRQIFNlcnZlciB2Ny4wLjQ1NC40DQo+IFNN
VFAgbG9nIHN0YXJ0ZWQgYXQgRnJpLCAxMCBKYW4gMjAxNCAgMjI6MDY6MjEgQ29ubmVjdGlvbiBU
aW1lOiAyMDE0MDExMA0KPiAyMjowNjoyMSAgY2lkOiAwMDAwMDAwMCB0aWQ6IDE0NEMgU1NMIEVu
YWJsZWQ6IFlFUyBNZXNzYWdlIFF1ZXVlOg0KPiBkOlxzcG9vbFxzYW50cm9uaWNzXHNtdHBcNDc0
NDZXDQo+IERlc3RpbmF0aW9uOiAjIyMjIyMjIyMjIyMjI0B5YWhvby5jb20NCj4gTWFpbCBIb3N0
IElQOiA5OC4xMzYuMjE2LjI2OjI1IChtdGE2LmFtMC55YWhvb2Rucy5uZXQpIEF0dGVtcHQgIzEN
Cj4gTGFzdEF0dGVtcHQ6IG4vYQ0KPiAyMjowNjoyMS40NzEgKiogT3BlbmluZyBDb25uZWN0aW9u
IHRvIGhvc3Q6IG10YTYuYW0wLnlhaG9vZG5zLm5ldCBpcDoNCj4gOTguMTM2LjIxNi4yNjoyNQ0K
PiAyMjowNjoyMS42NjggUzogMjIwIG10YTEwODkubWFpbC5ncTEueWFob28uY29tIEVTTVRQIHJl
YWR5DQo+IDIyOjA2OjIxLjY2OSBDOiBFSExPIHNlY3VyZS53aW5zZXJ2ZXIuY29tDQo+IDIyOjA2
OjIxLjc3MCBTOiAyNTAtbXRhMTA4OS5tYWlsLmdxMS55YWhvby5jb20NCj4gMjI6MDY6MjEuNzcw
IFM6IDI1MC1QSVBFTElOSU5HDQo+IDIyOjA2OjIxLjc3MCBTOiAyNTAtU0laRSA0MTk0MzA0MA0K
PiAyMjowNjoyMS43NzAgUzogMjUwLThCSVRNSU1FDQo+IDIyOjA2OjIxLjc3MCBTOiAyNTAgU1RB
UlRUTFMNCj4gMjI6MDY6MjEuNzcwIEM6IE1BSUwgRlJPTTo8bGlzdGFkbWluLXdpbnNlcnZlckB3
aW5zZXJ2ZXIuY29tPg0KPiAyMjowNjoyMS44ODQgUzogMjUwIHNlbmRlciA8bGlzdGFkbWluLXdp
bnNlcnZlckB3aW5zZXJ2ZXIuY29tPiBvaw0KPiAyMjowNjoyMS44ODQgQzogUkNQVCBUTzo8bG9u
ZWhvcnNlbWFuODJAeWFob28uY29tPg0KPiAyMjowNjoyMS45ODcgUzogMjUwIHJlY2lwaWVudCA8
bG9uZWhvcnNlbWFuODJAeWFob28uY29tPiBvaw0KPiAyMjowNjoyMS45ODcgQzogREFUQQ0KPiAy
MjowNjoyMi4wODcgUzogMzU0IGdvIGFoZWFkDQo+IDIyOjA2OjIzLjE3OSBTOiA1NTQgNS43Ljkg
TWVzc2FnZSBub3QgYWNjZXB0ZWQgZm9yIHBvbGljeSByZWFzb25zLg0KPiBTZWUgaHR0cDovL3Bv
c3RtYXN0ZXIueWFob28uY29tL2Vycm9ycy9wb3N0bWFzdGVyLTI4Lmh0bWwNCj4gMjI6MDY6MjMu
MTgwIEM6IFFVSVQNCj4gMjI6MDY6MjMuMTgwICoqIENvbXBsZXRlZC4gRWxhcHNlZCBUaW1lOiAx
NzAwIG1zZWNzDQo+IA0KPiBJdHMgcmVwZWF0ZWQgZm9yIHRoZSBvdGhlciB0aHJlZSB5YWhvby5j
b20gdXNlcnMgZHVyaW5nIGEgc3VibWlzc2lvbiBhbmQgaXRzDQo+IHJlY29yZGVkIGluIHRoZSBs
YXN0IGZvdXIgbW9udGhzIG9mIGxvZ3MuICBPbmx5IHllc3RlcmRheSBkaWQgYSBjdXN0b21lciBw
b3N0DQo+IGEgc3VwcG9ydCBtZXNzYWdlIGhlIHdhcyBub3cgc2VlaW5nIGl0IGhpcyBXaWxkY2F0
IQ0KPiBMaXN0IFNlcnZlciBzZXR1cCBhbmQgbG9ncy4gIFRoZXJlIG1pZ2h0IGhhdmUgYmVlbiBl
YXJsaWVyIHJlcG9ydHMgYnV0IEkgZGlkbid0DQo+IHNlZSB0aGVtLg0KPiANCj4gPj4gSSBjYW4g
c2VlIGFkZGl0aW9uYWwgRE1BUkMgZXh0ZW5zaW9ucyBmb3Igb3RoZXIgYWR2YW5jZW1lbnRzLCBi
dXQgdGhlDQo+ID4+IG1haW4gb25lIGlzIGFib3V0IG1hbmFnaW5nIDNyZCBwYXJ0eSBhdXRob3Jp
emVkIGRvbWFpbiB0byBzYXRpc2Z5IHRoZQ0KPiA+PiAic2lnbmluZy9zZW50IG9uIGJlaGFsZiBv
ZiIgZGVzaWduIG5lZWQgdGhhdCB5YWhvbyBzYXlzIGlzIHJlcXVpcmVkOg0KPiANCj4gPiBPbiBv
bmUgbGV2ZWwgdGhlcmUgYWxyZWFkeSBhcmUgd2F5cyBmb3Igc2F0aXNmeWluZyB0aGUgM3JkIHBh
cnR5IGF1dGhvcml6ZWQNCj4gZG9tYWluIGlzc3VlLiBBIGRvbWFpbiBjb3VsZCB1c2UgU1BGIChl
aXRoZXIgYnkgc3BlY2lmeWluZyBob3N0cy9JUHMgb3IgdXNpbmcNCj4gYW4gaW5jbHVkZSBpbiB0
aGUgU1BGIHJlY29yZCkgZm9yIGEgM3JkIHBhcnR5IGRvbWFpbi4gQW5vdGhlciBtZXRob2Qgd291
bGQNCj4gYmUgdG8gcHJvdmlkZSBES0lNIHNpZ25pbmcga2V5cyB0byB0aGUgM3JkIHBhcnR5LiBZ
ZXQgYSAzcmQgd2F5IGlzIHRvIGRlbGVnYXRlDQo+IGEgc3ViZG9tYWluIHNvIHRoYXQgdGhlIDNy
ZCBwYXJ0eSBjYW4gbWFuYWdlIHRoZXNlIHRoaW5ncyBvbiB0aGVpciBvd24uDQo+IFRoZXJlIGFy
ZSBzb21lIGJlc3QgcHJhY3RpY2UgZG9jdW1lbnRzIHB1Ymxpc2hlZCBhdCBtYWF3Zy5vcmcgdGhh
dCBtaWdodA0KPiBiZSB1c2VmdWwuIElmIHdoYXQgeW91IG1lYW4gaXMgYSBtZWNoYW5pc20gdG8g
c3BlY2lmeSByYW5kb20gM3JkIHBhcnRpZXMNCj4gdGhhdCBhbiBlbmQgdXNlciB3aXNoZXMgdG8g
dXNlLCB0aGVuIG5vIHRoZXJlIGlzIG5vdCBhIG1lY2hhbmlzbSBhbmQgSSBkb24ndA0KPiBrbm93
IG9mIGFueW9uZSB3aG8gaGFzIHB1dCBmb3J0aCB3aGF0IEkgd291bGQgY29uc2lkZXIgYSB3b3Jr
YWJsZSBtb2RlbC4NCj4gPg0KPiANCj4gSSBoYXZlIHRvIGJlZ2luIHJlYWRpbmcgdGhlIERNQVJD
IHNwZWMgdG8gc2VlIHdoYXQgYXJlIGFsbCB0aGUgYm91bmRhcnkNCj4gY29uZGl0aW9ucywgYnV0
IGl0IG1lYW5zIGJhc2ljYWxseSBhYmxlIHRvIGFuc3dlciBtYWlsIG9wZXJhdGlvbiBwb2xpY3kN
Cj4gcXVlc3Rpb25zIHN1Y2ggYXM6DQo+IA0KPiAgICBvICBEb2VzIHRoZSBkb21haW4gZXZlciBk
aXN0cmlidXRlIG1haWw/DQo+ICAgIG8gIERvIHlvdSBleHBlY3QgdGhlIG1haWwgdG8gYmUgdW5z
aWduZWQ/DQo+ICAgIG8gIERvIHlvdSBleHBlY3QgdG8gc2lnbiBhbGwgbWFpbD8NCj4gICAgbyAg
SXMgeW91ciBkb21haW4gdGhlIGV4Y2x1c2l2ZSBzaWduZXI/DQo+ICAgIG8gIEFyZSAzcmQgcGFy
dHkgc2lnbmVycyBhbGxvd2VkPw0KPiAgICBvICBBcmUgM3JkIHBhcnR5IHNpZ25lcnMgYWxsb3dl
ZCB0byBzdHJpcCB5b3VyIG9yaWdpbmFsIHNpZ25hdHVyZXM/DQo+IA0KPiBUaGlzIGlzIGFuIGls
bHVzdHJhdGlvbiBvZiB0aGUgbG9naWNhbCBmbG93IHdoZW4gU1NQIGRlZmluZWQgcG9saWNpZXMg
d2VyZSB1c2VkDQo+IHRvIGFuc3dlciB0aGUgYWJvdmUgcXVlc3Rpb25zLg0KPiANCj4gICAgaHR0
cDovL3d3dy53aW5zZXJ2ZXIuY29tL3B1YmxpYy9zc3Avc3NwLmh0bQ0KPiANCg0KRG9uJ3QgdGhp
bmsgU1NQIHdoZW4geW91IGxvb2sgYXQgRE1BUkMuIFRoZXJlIGFyZSBvbmx5IDMgYmFzaWMgc2V0
dGluZ3MgZm9yIGEgc2VuZGVyIHB1Ymxpc2hpbmcgYSBETUFSQyByZWNvcmQuIEkgZG9uJ3Qgd2Fu
dCB0byBiZSBhY2N1c2VkIG9mIHNoaWxsaW5nIGZvciBETUFSQyBoZXJlIHNvIGlmIHlvdSBoYXZl
IHF1ZXN0aW9ucyBpdCBpcyBwcm9iYWJseSBiZXR0ZXIgZm9yIHlvdSB0byBnbyB0byBvbmUgb2Yg
dGhlIERNQVJDIHJlbGF0ZWQgbGlzdHMgb3IgY29udGFjdCBtZSBvZmZsaW5lLg0KDQo+ID4+ICAg
ICAgIllhaG9vIHJlcXVpcmVzIGV4dGVybmFsIGVtYWlsIHNlcnZpY2UgcHJvdmlkZXJzLCBzdWNo
IGFzDQo+ID4+ICAgICAgIHRob3NlIHdobyBtYW5hZ2UgZGlzdHJpYnV0aW9uIGxpc3RzLCB0byBj
ZWFzZSB1c2luZyB1bnNpZ25lZA0KPiA+PiAgICAgICDigJxzZW50IGZyb23igJ0gbWFpbCwgYW5k
IHN3aXRjaCB0byBhIG1vcmUgYWNjdXJhdGUg4oCcc2VudCBvbg0KPiA+PiAgICAgICBiZWhhbGYg
b2bigJ0gcG9saWN5LiINCj4gPj4NCj4gPj4gV2hhdCBpcyB0aGlzIHNvIGNhbGxlZCAibW9yZSBh
Y2N1cmF0ZSIgbWV0aG9kPw0KPiA+Pg0KPiA+DQo+ID4gTm90IHN1cmUgZXhhY3RseSB3aGF0IGhl
IG1lYW5zLg0KPiANCj4gVGhlIDUzMjIuRnJvbSByZXdyaXRlIHN1Z2dlc3Rpb24/DQo+IA0KDQpQ
b3NzaWJseSwgSSBoYXRlIGd1ZXNzaW5nIG9uIHNvbWV0aGluZyBsaWtlIHRoYXQuDQoNCk1pa2UN
Cg==


From nobody Tue Apr 15 13:21:25 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10E5F1A049E for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:21:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level: 
X-Spam-Status: No, score=-0.4 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, FREEMAIL_REPLY=1, J_CHICKENPOX_21=0.6, SPF_PASS=-0.001] autolearn=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 78S-6kDNT-ZN for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:21:20 -0700 (PDT)
Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id C33C91A03E9 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:21:20 -0700 (PDT)
Received: by mail-pa0-f41.google.com with SMTP id fa1so10098718pad.28 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:21:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=12EOK9QNthn2OfqkAhl1hvAqjha1t8oyVFrHOYQAwAY=; b=nriw0g+RDZbHN5dywFmS50+9ilX5fAs/WgpWqavYKctzoKGp3JnZWk7dcL0VhR2rah DR3+3veygxWL3T5Hb7osFhvx/LueYJCo33XzzuU9wZVI4wpvKeiVexnDYh6bCsTxJ6uZ koFqpNkMeB1x4ftdgOT9R0dFlfjqMCdGAG9ikoQ7VHAWMrMkAWwCgvLkhIyFCxNQxiFT DnIDIfADdfyiGXNlaJtIXiX8xJQ03P63oKjUGpAykKeyiVsPpU2plwjNRAFu0eXcx0BQ 1kW6QNozJvsS/kaHGYlQD9MrefsN/gcMRY4etD34dUuP76uuFl1a+JS2AXStPXSh42F/ XZRw==
X-Received: by 10.68.113.5 with SMTP id iu5mr4224071pbb.60.1397593277985; Tue, 15 Apr 2014 13:21:17 -0700 (PDT)
Received: from [192.168.178.20] (95.198.69.111.dynamic.snap.net.nz. [111.69.198.95]) by mx.google.com with ESMTPSA id tf10sm42174673pbc.70.2014.04.15.13.21.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 13:21:17 -0700 (PDT)
Message-ID: <534D94BE.1010005@gmail.com>
Date: Wed, 16 Apr 2014 08:21:18 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: Mailman 2.1.16 [DMARC: perspectives from a listadmin of large open-source lists
References: <20140414220233.32201.qmail@joyce.lan> <20123.1397567461@sandelman.ca> <20140415153047.GA4456@thunk.org>
In-Reply-To: <20140415153047.GA4456@thunk.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_BE1jnlC4PqbpuQfj_fIY9QlMDg
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 20:21:22 -0000

On 16/04/2014 03:30, Theodore Ts'o wrote:
> On Tue, Apr 15, 2014 at 09:11:01AM -0400, Michael Richardson wrote:
>>> From: Brian E Carpenter <brian.e.carpenter@yahoo.com.INVALID>
>> So, that totals people's address books.
> 
> But only for yahoo.com users.  Somehow, I have a very hard time
> feeling sympathetic about their plight.

Also, it isn't really 'total'. At least with my MUA, it's trivial to
edit a To or CC address, or an address book entry; it's an annoyance of course.

Note to spammers: brian.e.carpenter@yahoo.com, if it exists, isn't me.

    Brian

> If Yahoo isn't going to care about screwing over mailing list
> administrators, I'm not sure why I should care about about
> inconveniencing Yahoo uesrs.  If they end up moving to some other mail
> provider, I'll consider that a bonus.
> 
> And if Yahoo is right, and most Yahoo users don't use mailing lists,
> then obviously this won't be a problem, right?
> 
> 						- Ted
> 
> 


From nobody Tue Apr 15 13:30:39 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F02C61A0647 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:30:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level: 
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_PASS=-0.001] autolearn=ham
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 b9EpKtCUn_bK for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:30:37 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.31]) by ietfa.amsl.com (Postfix) with ESMTP id E256E1A06DF for <ietf@ietf.org>; Tue, 15 Apr 2014 13:30:36 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES533.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Tue, 15 Apr 2014 16:30:33 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: S Moonesamy <sm+ietf@elandsys.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: DMARC: perspectives from a listadmin of large open-source lists
Thread-Topic: DMARC: perspectives from a listadmin of large open-source lists
Thread-Index: AQHPWOA39xJg0SLv5E6irQO+Rle3hpsTEPzA
Date: Tue, 15 Apr 2014 20:30:32 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D4749E@USCLES544.agna.amgreetings.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com> <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.gmail.com> <6.2.5.6.2.20140415111633.0da3d030@resistor.net>
In-Reply-To: <6.2.5.6.2.20140415111633.0da3d030@resistor.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BLNfBtsuVXO0CdkvltcekJEhobA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 20:30:39 -0000

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of S Moonesamy
> Sent: Tuesday, April 15, 2014 3:24 PM
> To: Dave Cridland
> Cc: ietf@ietf.org
> Subject: Re: DMARC: perspectives from a listadmin of large open-source li=
sts
>=20
> Hi Dave,
> At 00:42 15-04-2014, Dave Cridland wrote:
> >Given the expense and difficulty of IETF participation for smaller
> >organisations and individuals, it's hard for them to club together and
> >stand up to the 8000lb gorillas.
>=20
> The above is an obvious problem or difficult situation that people do not
> want to talk about.
>=20

My experience with regard to working groups is that it is (technically) eas=
y to participate and does not necessarily involve any particular costs. I d=
on't go to IETF meetings but have participated in WG sessions during IETF m=
eetings through jabber. Not the optimal solution but it works. I think that=
 the notion of 8000lb gorillas somewhat misrepresents the situation. Some o=
f the active participants in the working groups I've been involved with con=
tinue their involvement even when they change employers. With that in mind,=
 I believe that in many cases it truly is the individual and not the indivi=
dual as mouthpiece for the organization. I also believe that the 8000lb gor=
illas have many of the same interests as smaller organizations and individu=
als even though there are times where interests may diverge. It's also clea=
r to me that there is not uniformity of interests across constituencies wit=
hin large organizations. It's complex. So let's talk.=20

> Publication in the IETF Stream usually entails giving up change control.
> Sometimes that does not work out well; see RFC 6109.  The process is
> tedious.  It does not have to be like that if people make room for agreem=
ent.
> In simple terms, people can discuss about X for the next three years or t=
here
> can be a short discussion and a solution within the next three months.
>=20
> The summary of the DMARC BoF is at
> http://www.ietf.org/mail-archive/web/apps-discuss/current/msg10138.html
> According to that message there was agreement for the IETF to take on the
> DMARC base specification.
>=20

Unfortunately, the operative word is "was". Barry dropped his submission an=
d Murray submitted as informational, so that ship has sailed. What that mea=
ns for whether a working group is spun up to work on extensions or anything=
 else is beyond me. If DMARC base is informational I would assume that any =
of the extensions would be informational. I'm not sure what the implication=
s are.

Mike


From nobody Tue Apr 15 13:38:44 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 036631A065B for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 cFO281ZYhgTv for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:38:38 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id E96221A0753 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:38:37 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id v10so9900941pde.15 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:38:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=praDA7cat32yQ41OtXGmq+5Tt7HSM/YQqzOTU614Ns8=; b=fIayNRaeun4yRvhXWnAd0f/MNu5MAr9s/pSp9Lct8u//W5PBYE3WwmncW1CA4zI6+h s9lCAYAq5oHnpfbjt3DPz/XT/7AknAETe2iLBTYiou7Hxu2xkUOzuEuN3xu5ezL9jq1r lJV5xZ7Rpag/FA9a+DOBNLiHCs7QQ9C7J2Uyix12u/j7wmA3MBOw42fs+trbNiQkxhI/ 2zS2bPC/4Vt6fucKNkIDMcfcW7BXCv4v0fkEcMAcoNjnVgM9vmN2Wi/cemp0TGNGVd0X L7tzZK1pDEQhTQoGHaQk974l3OAlW86zdjp+PNHGCVwufRCD0df7XFd8PkWfYh/3hJIn 329w==
X-Received: by 10.68.197.8 with SMTP id iq8mr4297985pbc.124.1397594315182; Tue, 15 Apr 2014 13:38:35 -0700 (PDT)
Received: from [192.168.178.20] (95.198.69.111.dynamic.snap.net.nz. [111.69.198.95]) by mx.google.com with ESMTPSA id 10sm19198228pbo.51.2014.04.15.13.38.33 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 13:38:34 -0700 (PDT)
Message-ID: <534D98CC.9080400@gmail.com>
Date: Wed, 16 Apr 2014 08:38:36 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net>
In-Reply-To: <534D5516.7060902@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8oZobTRHYIW9HD3sRig2gaXRtrs
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 20:38:43 -0000

On 16/04/2014 03:49, Dave Crocker wrote:
> On 4/14/2014 6:45 PM, Brian E Carpenter wrote:
>> I thought that standard operating procedure in the IT industry
>> was: if you roll something out and it causes serious breakage to
>> some of your users, you roll it back as soon as possible.
>>
>> Why hasn't Yahoo rolled back its 'reject' policy by now?
> 
> 
> As the most-recent public statement from Yahoo, this might have some
> tidbits in it that are relevant to your question:
> 
> 
> 
> http://yahoo.tumblr.com/post/82426971544/an-update-on-our-dmarc-policy-to-protect-our-users

It serves to explain their obduracy but this really annoys me:

> There is a regrettable, short-term impact to our more aggressive position on DMARC. Many legitimate emails sent on behalf of Yahoo Mail customers from third parties are also being rejected. We apologize for any inconvenience this may have caused.

Why do they assert that it's a *short-term* impact? There's no clean fix, as
the discussion here has shown. And doesn't that "any" in "any inconvenience"
make you grind your teeth? We know that it's caused great inconvenience.

And this:

> We know there are about 30,000 affected email sending services, but we also know that the change needed to support our new DMARC policy is important and not terribly  difficult to implement. 

"not terribly  difficult to implement"? From what list admins are telling us,
that is simply untrue.

>  We have detailed the changes we are requiring here.

"requiring"?? Who are Yahoo to _require_ changes from 30000 third parties?

The mailman fix is worse than the disease. I think the .INVALID fix is
much better, because Reply-all will still work.

    Brian


From nobody Tue Apr 15 13:53:16 2014
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F54D1A0454 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 RQz4cdjMl__j for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:53:09 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC861A01F8 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:53:09 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id fp1so9961633pdb.28 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:53:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=6NjK7RB1Oi4UsO0Nf/yFq1pGs/CXpzcU7v/UuW9d720=; b=PN85lTU4quq1deGNA2N6fqGQFDX6xSCg+f7QzWjfVmsW9dhDsfdAonscfNBxXCIxYm v5UpG3SO32BMGXqf1tSAfqpvvBwMZTFJ684AlW3Powt5bNP7E8mM2ibTmcAf77h6hp8G uBFxeh0IeELqzOfv07Et9+I3J+EExXM0M93AJniMubnWdcXKgLJUy8qjK64Uh1pWj6Qb 9kJ0A2fYcgRxdyUnrA6W+TFwGL18T97vP7/qiN/d1NTTGf94W7nIsGxIf+PbUBjMFeCk oG6qe5eVxJJ9v7ZLXa3c/wAKYt0zPFPXTgN4s9YO7ttzdcNspJHVuHetBCszxcgH5fxS VzdA==
X-Received: by 10.68.203.39 with SMTP id kn7mr4177121pbc.141.1397595186589; Tue, 15 Apr 2014 13:53:06 -0700 (PDT)
Received: from [192.168.15.4] (184-76-96-188.war.clearwire-wmx.net. [184.76.96.188]) by mx.google.com with ESMTPSA id qv9sm35384058pbc.71.2014.04.15.13.53.04 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 13:53:05 -0700 (PDT)
Message-ID: <534D9C2C.8010606@gmail.com>
Date: Tue, 15 Apr 2014 14:53:00 -0600
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com>
In-Reply-To: <534D98CC.9080400@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080107000705020602060008"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lX06iXY0qvOTbbX_TduyQwk4pK0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 20:53:14 -0000

This is a cryptographically signed message in MIME format.

--------------ms080107000705020602060008
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Yahoo policy says you must have DKIM, SPF, or DMARC records. At what=20
point could a large ISP start actually requiring these kinds of records=20
for FREE email they accept and allow users to send?

Annoying, but it sounds reasonable to me for them to state a policy and=20
enforce it.

If everyone had to wait until everyone upgraded, nothing would change.

--=20

Doug Royer - (K7DMR.us / DougRoyer.com)
DouglasRoyer@gmail.com
714-989-6135



--------------ms080107000705020602060008
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMhzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGSzCCBTOgAwIBAgIDCXp9MA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTQwMzMwMTMwMjIz
WhcNMTUwMzMwMjMzNjMxWjBjMRkwFwYDVQQNExBDclhsb0tOcDhuNUxjMW53MR8wHQYDVQQD
DBZEb3VnbGFzUm95ZXJAZ21haWwuY29tMSUwIwYJKoZIhvcNAQkBFhZEb3VnbGFzUm95ZXJA
Z21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvgDR3UbGHtnMaqNw
FtsXf5VxjGKQWuVUhAJoKnxzI7Hf/gH7fFN/uGYB1HQiPDUOF/X2aIapC98ycdsZeHZ1iRIz
Qe5ag581kNFxztRWdqvPtK/nnXiB1qw8sVahmkC9JpZeh0KjymnB1D9vCHGJ+4l1bs9SB/aU
1pQ+zZVU+1bZJyUm9D7RN1+jrzkWbYqBAV99XoNodSbENuEB+skUGFMwxKZmAFWgAVIKMzWf
5rs3tP0Do2p1O+OaPkvxzkgo3thX/RPmMYPhpuewURcq+HQ6YRW+r7oZ97H9PaOrrwslKBu4
70sAAhbfd0LmCv3gXRnRTWMRnNVotY1jjqfapQIDAQABo4IC3DCCAtgwCQYDVR0TBAIwADAL
BgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSQ
5w5XWt3QI8FUbPINB9XajsHB6DAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAh
BgNVHREEGjAYgRZEb3VnbGFzUm95ZXJAZ21haWwuY29tMIIBTAYDVR0gBIIBQzCCAT8wggE7
BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29t
L3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n
IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENv
bSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGlu
IGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQv
MC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsG
AQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20v
Y2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEARwipb/dALl2bQ7lZoavGzjro5vv3
yZ5PU2a+ZPLJaOOio6C1qfzoVmrwITTphp2VNACjbHJ9RHXbUi1WhMafgIw/YMXOj8cOlUFJ
2qz8R1WiK2Gt+aOVlgiin91pOpHlWUBlkhgH4yk1BAz1wcuZ5AWgm2r9g1DYX+NBLh6/IyPv
+1Imc9LoDJVwcatovbsa+zEEU3psvXEELJpwS4QPxWSYbDcuTL8jvA1HvXR1i8YtYJjm8A/u
VyxgNpve4UxrmNyya+vGMmRkOYAYt7ck4tuqe1L2NyErDhk7PIst1nxnEUPbRGTmSH2eQarV
lkDKXqdsl6bxWL72jZ0Kt+xgRDGCA90wggPZAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQG
A1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNh
dGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVk
aWF0ZSBDbGllbnQgQ0ECAwl6fTAJBgUrDgMCGgUAoIICHTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA0MTUyMDUzMDBaMCMGCSqGSIb3DQEJBDEWBBQ+
53tsoEPBy+mMk3i4wfgVaX+mwjBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcG
BSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBD
ZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg
SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCXp9MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDEL
MAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBE
aWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEg
UHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMJen0wDQYJKoZIhvcNAQEBBQAEggEA
ddrXKcxaJFiGOnme5P/rqw5o2DQ9WpQ9WI3hVJWJJCpjQO0by2IzgHMZ7VG6l5MYv7jBnMdq
0tbOxZoC1kV3uZ45gNGHA560+3nOuQhfVWMvFjce3jR4VStHjZOjx0s+bdX9KIvTVCjppg5N
Zbs4y1UfQFUxMlLhWz6xeVFtLNDB/wehoj6CdZPtdbfNNn94RXMBZJJ0mCKDgJ+CrFuNqQ2l
mVRoD6rp6cikFDLy2wZFx29YoLS9a4JWPdnkrs8tpFNKB9FzFAvaCTGDuhY3Md8/hic2qD3E
1XGYKbx/ybpfhSmwlvUco6/yvBou8fpHY7tpQDvq4NUiTb9UbQ5THAAAAAAAAA==
--------------ms080107000705020602060008--


From nobody Tue Apr 15 13:57:05 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 198C11A07D7 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.701
X-Spam-Level: 
X-Spam-Status: No, score=-98.701 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 IqB7SI92PjBq for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 13:56:59 -0700 (PDT)
Received: from ntbbs.santronics.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBF61A06B8 for <ietf@ietf.org>; Tue, 15 Apr 2014 13:56:59 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2832; t=1397595411; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=eh0ejrCUZjkwll1Bmhm3Ar3CTjc=; b=KfgxPaFWR9uRHmkWI8W+ w9L3jfcIZDi+TJHthvccU7Z+PZ9lpmSnzcZMRRfVPixZRWUa6lISYfTTcYOXaEm6 Tu9/jG7gJP2QCD4LwRqDArqtPGHB6NpZR7MwlN8BR6itR0aa+lwP/DqEGIzhkMSK 1pktHjmwTNYu5j7Eiw8qGM4=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 16:56:51 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 703987583.3.2836; Tue, 15 Apr 2014 16:56:50 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2832; t=1397595345; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=Egqwvi1 vk41BaScRP1otalKBwZAisK7kpsshLnRYIMU=; b=eFaLPjm8CGCnWxilmGuPoZD 40ssSrcz4mmcAPK3xj3bV2ZNeeZW2TE6A+GEsAqUzMcs1fJ6+1afH1eHeOFmOW3A F6f8PCUJAZ+mrkWi590QqueG6tfgMG8Lx6EyC6X15Ew4Xjyg+bf8xjvO7WtPs0zi jQdhpeKGxDcXsi7tpJ90=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 16:55:45 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 723521078.9.8728; Tue, 15 Apr 2014 16:55:44 -0400
Message-ID: <534D9D12.4080602@isdg.net>
Date: Tue, 15 Apr 2014 16:56:50 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan> <5347C698.6040108@tana.it> <534ACB5F.7060400@isdg.net> <534CE53A.7090000@tana.it>
In-Reply-To: <534CE53A.7090000@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/at_G4DbiZGLtVZXAKWFRNyOGVhE
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 20:57:04 -0000

>> It may be the "quickest" way, but I would consider this the most
>> intrusive and even email damaging, extremely harmful suggestion to
>> electronic mail communications.
>
> Ok, I added "temporarily", so it now reads:
>
>     Various workarounds have been proposed to cope with domains that
>     publish strict policies unwittingly. For example, a mailing list
>     manager should reject posts from authors who use problematic email
>     domains. The latter behavior is the most respectful the
>     communication protocols as well as the domain owner's will.
>     However, it might cause inconveniences in the face of sudden
>     policy changes. According to John Levine, a well known mail
>     expert, the least intrusive way to temporarily mitigate the damage
>     would be to rewrite the From: address in a predictable,
>     comprehensible manner, such as the following:
>
> In the preceding "History" section, I appended:
>
>     In April 2014, Yahoo changed its DMARC policy to p=reject, thereby
>     causing misbehavior in several mailing lists.[6] DMARC is not yet
>     a standard protocol, and currently misses a provision for such
>     sudden changes.
>
> Is that more acceptable?

I think adding temporarily helps and the additional text about DMARC 
certainly helps.

But the problem is YAHOO doesn't want you to do this (rewrite).

Just consider what you are essentially doing:

    Degrading a secured message to a non-secured message.

The whole point of Yahoo moving to a restrictive policy is to force a 
cleanup of their domain usage, to increase its security quality, even 
if it hurts the innocent users who were using their domains in public 
mail list areas.

So I would personally refrain from any product liability risk that its 
ok to "tamper" with their DKIM secured author domain submissions.

Case in point, lets say a real bad message got into the list, 
unsigned, purported from Yahoo, the 5322.From was rewritten and 
distributed to other list users and some of those users were "harmed" 
in some fashion that it worth the effort to sue.   Guess who would be 
at legal fault here?  Not YAHOO. They are legally protected.  The MLM, 
who wistfully and intentionally ignored policy and even went as far to 
break the security, is now at risk.

No, its not silly, and just because I am not a lawyer, doesn't mean we 
don't think about these things in our product development.  In fact, 
it is generally the engineer, us, that has to ask the our lawyers if 
this is ok.  He isn't going to generally tell you, it is not something 
he will pick up unless you pointed it out to him. Then he will give 
you his legal advise and in my strong opinion, you don't tamper with a 
security protocol which is what being suggested here.

Don't let me stop you from the wiki work.  It is just how I work.

Thanks

-- 
HLS



From nobody Tue Apr 15 14:15:24 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2219B1A0454 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 14:15:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 3TCfKwIx0ht4 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 14:15:19 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.41]) by ietfa.amsl.com (Postfix) with ESMTP id ABEED1A049E for <ietf@ietf.org>; Tue, 15 Apr 2014 14:15:19 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES531.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Tue, 15 Apr 2014 17:15:15 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Hector Santos <hsantos@isdg.net>, Alessandro Vesely <vesely@tana.it>
Subject: RE: DMARC: perspectives from a listadmin of large open-source lists
Thread-Topic: DMARC: perspectives from a listadmin of large open-source lists
Thread-Index: AQHPWO049xJg0SLv5E6irQO+Rle3hpsTKl8Q
Date: Tue, 15 Apr 2014 21:15:15 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D4750D@USCLES544.agna.amgreetings.com>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan> <5347C698.6040108@tana.it> <534ACB5F.7060400@isdg.net> <534CE53A.7090000@tana.it> <534D9D12.4080602@isdg.net>
In-Reply-To: <534D9D12.4080602@isdg.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TsrRFU2Z8nUXKARC4jNzXSz1Lhg
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 21:15:21 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0ZiBbbWFpbHRvOmll
dGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEhlY3RvciBTYW50b3MNCj4gU2VudDog
VHVlc2RheSwgQXByaWwgMTUsIDIwMTQgNDo1NyBQTQ0KPiBUbzogQWxlc3NhbmRybyBWZXNlbHkN
Cj4gQ2M6IGlldGZAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IERNQVJDOiBwZXJzcGVjdGl2ZXMg
ZnJvbSBhIGxpc3RhZG1pbiBvZiBsYXJnZSBvcGVuLXNvdXJjZSBsaXN0cw0KPiANCj4gDQo+ID4+
IEl0IG1heSBiZSB0aGUgInF1aWNrZXN0IiB3YXksIGJ1dCBJIHdvdWxkIGNvbnNpZGVyIHRoaXMg
dGhlIG1vc3QNCj4gPj4gaW50cnVzaXZlIGFuZCBldmVuIGVtYWlsIGRhbWFnaW5nLCBleHRyZW1l
bHkgaGFybWZ1bCBzdWdnZXN0aW9uIHRvDQo+ID4+IGVsZWN0cm9uaWMgbWFpbCBjb21tdW5pY2F0
aW9ucy4NCj4gPg0KPiA+IE9rLCBJIGFkZGVkICJ0ZW1wb3JhcmlseSIsIHNvIGl0IG5vdyByZWFk
czoNCj4gPg0KPiA+ICAgICBWYXJpb3VzIHdvcmthcm91bmRzIGhhdmUgYmVlbiBwcm9wb3NlZCB0
byBjb3BlIHdpdGggZG9tYWlucyB0aGF0DQo+ID4gICAgIHB1Ymxpc2ggc3RyaWN0IHBvbGljaWVz
IHVud2l0dGluZ2x5LiBGb3IgZXhhbXBsZSwgYSBtYWlsaW5nIGxpc3QNCj4gPiAgICAgbWFuYWdl
ciBzaG91bGQgcmVqZWN0IHBvc3RzIGZyb20gYXV0aG9ycyB3aG8gdXNlIHByb2JsZW1hdGljIGVt
YWlsDQo+ID4gICAgIGRvbWFpbnMuIFRoZSBsYXR0ZXIgYmVoYXZpb3IgaXMgdGhlIG1vc3QgcmVz
cGVjdGZ1bCB0aGUNCj4gPiAgICAgY29tbXVuaWNhdGlvbiBwcm90b2NvbHMgYXMgd2VsbCBhcyB0
aGUgZG9tYWluIG93bmVyJ3Mgd2lsbC4NCj4gPiAgICAgSG93ZXZlciwgaXQgbWlnaHQgY2F1c2Ug
aW5jb252ZW5pZW5jZXMgaW4gdGhlIGZhY2Ugb2Ygc3VkZGVuDQo+ID4gICAgIHBvbGljeSBjaGFu
Z2VzLiBBY2NvcmRpbmcgdG8gSm9obiBMZXZpbmUsIGEgd2VsbCBrbm93biBtYWlsDQo+ID4gICAg
IGV4cGVydCwgdGhlIGxlYXN0IGludHJ1c2l2ZSB3YXkgdG8gdGVtcG9yYXJpbHkgbWl0aWdhdGUg
dGhlIGRhbWFnZQ0KPiA+ICAgICB3b3VsZCBiZSB0byByZXdyaXRlIHRoZSBGcm9tOiBhZGRyZXNz
IGluIGEgcHJlZGljdGFibGUsDQo+ID4gICAgIGNvbXByZWhlbnNpYmxlIG1hbm5lciwgc3VjaCBh
cyB0aGUgZm9sbG93aW5nOg0KPiA+DQo+ID4gSW4gdGhlIHByZWNlZGluZyAiSGlzdG9yeSIgc2Vj
dGlvbiwgSSBhcHBlbmRlZDoNCj4gPg0KPiA+ICAgICBJbiBBcHJpbCAyMDE0LCBZYWhvbyBjaGFu
Z2VkIGl0cyBETUFSQyBwb2xpY3kgdG8gcD1yZWplY3QsIHRoZXJlYnkNCj4gPiAgICAgY2F1c2lu
ZyBtaXNiZWhhdmlvciBpbiBzZXZlcmFsIG1haWxpbmcgbGlzdHMuWzZdIERNQVJDIGlzIG5vdCB5
ZXQNCj4gPiAgICAgYSBzdGFuZGFyZCBwcm90b2NvbCwgYW5kIGN1cnJlbnRseSBtaXNzZXMgYSBw
cm92aXNpb24gZm9yIHN1Y2gNCj4gPiAgICAgc3VkZGVuIGNoYW5nZXMuDQo+ID4NCj4gPiBJcyB0
aGF0IG1vcmUgYWNjZXB0YWJsZT8NCj4gDQoNCk1hbnkgcHJvdG9jb2xzIGRvIG5vdCBhZGRyZXNz
IHN1ZGRlbiBpbmRpdmlkdWFsIGltcGxlbWVudGVyIGNoYW5nZXMgdG8gdGhlaXIgaW1wbGVtZW50
YXRpb24uIEkgZG8gYmVsaWV2ZSB0aGF0IHRoZXJlIHdlcmUgdmFyaW91cyBpc3N1ZXMgaW52b2x2
aW5nIEROU1NFQyB0cnVzdCBjaGFpbnMgd2hlbiB1cHN0cmVhbSBwYXJ0aWNpcGFudHMgKGluY2x1
ZGluZyBDQyBUTERzKSBpbXBsZW1lbnRlZCAic3VkZGVuIiBjaGFuZ2VzLiBBcmUgeW91IGV4cGVj
dGluZyBzb21ldGhpbmcgbGlrZSAiTVVTVCBwcm92aWRlIHggZGF5cyBub3RpY2Ugb2YgaW50ZW5k
ZWQgY2hhbmdlIiB0byBtYWtlIGl0IG5vbi1zdWRkZW4gb3IgcmVxdWlyZSBhIHJvbGxiYWNrIGlm
IG1vcmUgdGhhbiB4IG1haWxpbmcgbGlzdHMgaGF2ZSBwcm9ibGVtcz8gQXJlIHRoZXJlIGFueSBv
dGhlciBJRVRGIHN0YW5kYXJkcyB0aGF0IHdvdWxkIGJlIGEgcmVmZXJlbmNlIHBvaW50IGZvciBz
dWNoIGEgcHJvdmlzaW9uPyBJJ20gbm90IHRyeWluZyB0byBiZSBjdXRlIG9yIGFyZ3VtZW50YXRp
dmUgLSBJJ20ganVzdCBub3QgZmFtaWxpYXIgd2l0aCBzb21ldGhpbmcgbGlrZSB0aGlzIGluIGFu
eSBzdGFuZGFyZHMgSSBjYW4gdGhpbmsgb2YuDQoNCj4gSSB0aGluayBhZGRpbmcgdGVtcG9yYXJp
bHkgaGVscHMgYW5kIHRoZSBhZGRpdGlvbmFsIHRleHQgYWJvdXQgRE1BUkMNCj4gY2VydGFpbmx5
IGhlbHBzLg0KPiANCj4gQnV0IHRoZSBwcm9ibGVtIGlzIFlBSE9PIGRvZXNuJ3Qgd2FudCB5b3Ug
dG8gZG8gdGhpcyAocmV3cml0ZSkuDQo+IA0KPiBKdXN0IGNvbnNpZGVyIHdoYXQgeW91IGFyZSBl
c3NlbnRpYWxseSBkb2luZzoNCj4gDQo+ICAgICBEZWdyYWRpbmcgYSBzZWN1cmVkIG1lc3NhZ2Ug
dG8gYSBub24tc2VjdXJlZCBtZXNzYWdlLg0KPiANCj4gVGhlIHdob2xlIHBvaW50IG9mIFlhaG9v
IG1vdmluZyB0byBhIHJlc3RyaWN0aXZlIHBvbGljeSBpcyB0byBmb3JjZSBhIGNsZWFudXANCj4g
b2YgdGhlaXIgZG9tYWluIHVzYWdlLCB0byBpbmNyZWFzZSBpdHMgc2VjdXJpdHkgcXVhbGl0eSwg
ZXZlbiBpZiBpdCBodXJ0cyB0aGUNCj4gaW5ub2NlbnQgdXNlcnMgd2hvIHdlcmUgdXNpbmcgdGhl
aXIgZG9tYWlucyBpbiBwdWJsaWMgbWFpbCBsaXN0IGFyZWFzLg0KPiANCj4gU28gSSB3b3VsZCBw
ZXJzb25hbGx5IHJlZnJhaW4gZnJvbSBhbnkgcHJvZHVjdCBsaWFiaWxpdHkgcmlzayB0aGF0IGl0
cyBvayB0bw0KPiAidGFtcGVyIiB3aXRoIHRoZWlyIERLSU0gc2VjdXJlZCBhdXRob3IgZG9tYWlu
IHN1Ym1pc3Npb25zLg0KPiANCj4gQ2FzZSBpbiBwb2ludCwgbGV0cyBzYXkgYSByZWFsIGJhZCBt
ZXNzYWdlIGdvdCBpbnRvIHRoZSBsaXN0LCB1bnNpZ25lZCwNCj4gcHVycG9ydGVkIGZyb20gWWFo
b28sIHRoZSA1MzIyLkZyb20gd2FzIHJld3JpdHRlbiBhbmQgZGlzdHJpYnV0ZWQgdG8gb3RoZXIN
Cj4gbGlzdCB1c2VycyBhbmQgc29tZSBvZiB0aG9zZSB1c2VycyB3ZXJlICJoYXJtZWQiDQo+IGlu
IHNvbWUgZmFzaGlvbiB0aGF0IGl0IHdvcnRoIHRoZSBlZmZvcnQgdG8gc3VlLiAgIEd1ZXNzIHdo
byB3b3VsZCBiZQ0KPiBhdCBsZWdhbCBmYXVsdCBoZXJlPyAgTm90IFlBSE9PLiBUaGV5IGFyZSBs
ZWdhbGx5IHByb3RlY3RlZC4gIFRoZSBNTE0sIHdobw0KPiB3aXN0ZnVsbHkgYW5kIGludGVudGlv
bmFsbHkgaWdub3JlZCBwb2xpY3kgYW5kIGV2ZW4gd2VudCBhcyBmYXIgdG8gYnJlYWsgdGhlDQo+
IHNlY3VyaXR5LCBpcyBub3cgYXQgcmlzay4NCj4gDQo+IE5vLCBpdHMgbm90IHNpbGx5LCBhbmQg
anVzdCBiZWNhdXNlIEkgYW0gbm90IGEgbGF3eWVyLCBkb2Vzbid0IG1lYW4gd2UgZG9uJ3QNCj4g
dGhpbmsgYWJvdXQgdGhlc2UgdGhpbmdzIGluIG91ciBwcm9kdWN0IGRldmVsb3BtZW50LiAgSW4g
ZmFjdCwgaXQgaXMgZ2VuZXJhbGx5DQo+IHRoZSBlbmdpbmVlciwgdXMsIHRoYXQgaGFzIHRvIGFz
ayB0aGUgb3VyIGxhd3llcnMgaWYgdGhpcyBpcyBvay4gIEhlIGlzbid0IGdvaW5nIHRvDQo+IGdl
bmVyYWxseSB0ZWxsIHlvdSwgaXQgaXMgbm90IHNvbWV0aGluZyBoZSB3aWxsIHBpY2sgdXAgdW5s
ZXNzIHlvdSBwb2ludGVkIGl0IG91dA0KPiB0byBoaW0uIFRoZW4gaGUgd2lsbCBnaXZlIHlvdSBo
aXMgbGVnYWwgYWR2aXNlIGFuZCBpbiBteSBzdHJvbmcgb3BpbmlvbiwgeW91DQo+IGRvbid0IHRh
bXBlciB3aXRoIGEgc2VjdXJpdHkgcHJvdG9jb2wgd2hpY2ggaXMgd2hhdCBiZWluZyBzdWdnZXN0
ZWQgaGVyZS4NCj4gDQo+IERvbid0IGxldCBtZSBzdG9wIHlvdSBmcm9tIHRoZSB3aWtpIHdvcmsu
ICBJdCBpcyBqdXN0IGhvdyBJIHdvcmsuDQo+IA0KPiBUaGFua3MNCj4gDQo+IC0tDQo+IEhMUw0K
PiANCg0K


From nobody Tue Apr 15 14:43:57 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29A361A04A6 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 14:43:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 ZPLftnYgWoCY for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 14:43:53 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 4504C1A06A6 for <ietf@ietf.org>; Tue, 15 Apr 2014 14:43:53 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WaB8v-0002mN-6M; Tue, 15 Apr 2014 21:43:49 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 86A1F580893; Tue, 15 Apr 2014 17:43:48 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397598228; bh=TAGd/pVl/LQJBtmkiNC1iVosl9V+opoHjFjjlD+l8e8=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=cE+MNqId0hFuh57fvLT5Z6thzoYX7JGeVAVD4zCWTajFt5Jcor7coBl9JRmNVxaQx 7bruEjpNQuuu/L1ryw/MyPSAPJhueeYQK3gocvMBaiYB1wkbS7ZLk+ubbHeKN3TImw T5HhTMSxUnwMKGPZAVKkbxPA1Zg3glrsJdsG+8Do=
Date: Tue, 15 Apr 2014 17:43:48 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Doug Royer <douglasroyer@gmail.com>
Subject: Re: DMARC and yahoo
Message-ID: <20140415214348.GL4456@thunk.org>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <534D9C2C.8010606@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534D9C2C.8010606@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7CWELVDfvEe-4aCiqWlOMAMhYK8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 21:43:55 -0000

On Tue, Apr 15, 2014 at 02:53:00PM -0600, Doug Royer wrote:
> Yahoo policy says you must have DKIM, SPF, or DMARC records. At what point
> could a large ISP start actually requiring these kinds of records for FREE
> email they accept and allow users to send?
> 
> Annoying, but it sounds reasonable to me for them to state a policy and
> enforce it.
> 
> If everyone had to wait until everyone upgraded, nothing would change.

The problem is with the alignment requirements of DMARC.  That can't
be easily fixed without breaking existing mailing list functionality.

Given that, it seems that the "From: username@yahoo.com.INVALID"
rewrite solution for mailing list, is the best solution, since it puts
the pain on yahoo.com users and people who want to communicate with
yahoo.com users.  If Yahoo wants to unilaterially allocate pain to the
rest of the Internet, then it shouldn't be surprised if people choose
a technical solution which transfer some of the pain back to Yahoo.

	  	   	 	       - Ted


From nobody Tue Apr 15 15:20:33 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B08D1A06ED for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 15:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level: 
X-Spam-Status: No, score=-4.573 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 9OnvCUXwuryj for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 15:20:27 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 071DC1A04A1 for <ietf@ietf.org>; Tue, 15 Apr 2014 15:20:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397600424; x=1429136424; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=df1wMVOc/BWbJggv7t8ZE0yhNC0OWUX8TEiEeQ4Zjho=; b=rU4YIUOHKbHKKH/e1Kaa2nsLTRuK0vSyMsDPr2dGM82Cloo7lTSUC3Pc uBEwERA8rbpBbbxDeY5DiTxQ8V2MtP6CukELFwC52fE+6iK1b0zbzXg8P /wDSpvJnf2eIdq+R0ev+hm5DARHjQ1SquxMSWNoXIvtJcASW6lRWt/ST/ w=;
X-IronPort-AV: E=McAfee;i="5400,1158,7409"; a="28978324"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 15 Apr 2014 15:20:23 -0700
X-IronPort-AV: E=Sophos;i="4.97,867,1389772800"; d="scan'208";a="716288097"
Received: from nasanexhc16.na.qualcomm.com ([10.45.158.213]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 15 Apr 2014 15:24:39 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc16.na.qualcomm.com (10.45.158.213) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 15 Apr 2014 15:20:07 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 15 Apr 2014 15:20:06 -0700
Message-ID: <534DB093.5020507@qti.qualcomm.com>
Date: Tue, 15 Apr 2014 17:20:03 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net>
In-Reply-To: <534BEF75.5060804@bbiw.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qIu5FPlaCoCDLiQ9YLokcw71Azw
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 22:20:32 -0000

On 4/14/14 9:23 AM, Dave Crocker wrote:

> Mediators, like mailing lists, take final delivery and post a new 
> message.  In formal terms, it's legitimate for them to create a 
> different rfc5322.From field, including one that looks like some sort 
> of 'rewrite' of the one used by the original author.

It's legitimate for a mailing list to rewrite the author, but it would 
be wrong. :-)

More seriously: If the mailing list wishes to express that I am the 
author of *this message*, then I belong in the "From:" field. That 
differs semantically from forwarding a message authored by me; then the 
list is saying that the list is the author, and it is simply quoting me, 
but that the list is the entity that should be considered to have 
written the message. For most mailing lists, that seems like the wrong 
semantics to try to convey.

There should be a mechanism for an author to send a message to a mailing 
list, granting the mailing list permission to redistribute that message, 
and have that permission conveyed to the mailing list recipient such 
that when the mailing list recipient receives the message, they can 
assure themselves that the originating domain is OK with that 
redistribution. Sounds like some protocol which could be written.

(If the originating domain is expressly *not* OK with the 
redistribution, the mailing list should bounce the message back to the 
author saying as much.)

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Tue Apr 15 15:49:48 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79441A0009 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 15:49:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.4
X-Spam-Level: *
X-Spam-Status: No, score=1.4 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_MUTUALBENEFIT=2, SPF_PASS=-0.001] autolearn=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 glCyIcx88Z9j for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 15:49:45 -0700 (PDT)
Received: from mail-oa0-x233.google.com (mail-oa0-x233.google.com [IPv6:2607:f8b0:4003:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id D054F1A0004 for <ietf@ietf.org>; Tue, 15 Apr 2014 15:49:45 -0700 (PDT)
Received: by mail-oa0-f51.google.com with SMTP id i4so11719560oah.10 for <ietf@ietf.org>; Tue, 15 Apr 2014 15:49:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=tDDNq/embPQhgON+Ngy+nilgVruPkp04GmhhW4cPIEU=; b=e0qQuv6mV2+mawwNevDxOD4PXAMbggLazyEu6W1STve1SbdFG0Qqtd7L6VHQaNaKWt udrT6F4ZXiDYFP7aU1EloJnrQ3sFuFz3lXgkhKznp/dD9h8JSTA4AZw3J+ZGPFGQzj1U BjlDJseKXyHYf2XxP8oHxT+Aj6FgmiL/azK5H9W7cz6vOp5GIr+haIDP7nNluVioPn3P mczuY6HYh1sNuLqHIZJddis/SqDgzgSqVT8qI8nwaycWhZuFJUzd3yDwP7m6JCb41waC WZh1ZGIGEglSp9aIpblD2uqve+GwwyBqSsNxUAwCApdHBTS68NCGQTmA9uN5yElsxDqA HkVw==
X-Received: by 10.182.97.1 with SMTP id dw1mr3674214obb.23.1397602182817; Tue, 15 Apr 2014 15:49:42 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id c7sm91161578oek.12.2014.04.15.15.49.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 15:49:42 -0700 (PDT)
Message-ID: <534DB785.7040609@gmail.com>
Date: Tue, 15 Apr 2014 17:49:41 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>,  "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net>
In-Reply-To: <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8pZoCKBoXjT1il0BN4NrQyfQCFw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 22:49:47 -0000

On 04/15/2014 01:10 PM, Jari Arkko wrote:
> There are certainly also IETF process/organisation things that we should work on to improve. We do. Here are some things that I would like to see:
>
>    o  Are there ways to work to mutual benefit with open source efforts (those that would benefit from an IETF-like environment)?

... skipping down to

>    o  How can we better build specs to (rough) consensus, including making sure that (an understood) vocal minority opinion does not block progress?
>
>    o  More focus on running code.

In roughly 2002-2004, the IETF had conversations about a specification 
level,

     Standards Track RFC > new specification level > Internet-Draft,

including a variety of proposals for "Working Group Snapshots"/"Stable 
Snap Shots". The idea was that you could declare a specific 
Internet-Draft "good enough for now", for a variety of reasons (which 
varied from proposal to proposal), and one of the reasons could be 
"we're going to stop working on this draft until we get some 
implementation experience".

Perhaps that would help us be more responsive to open source projects. 
Right now, their choices are either to implement based on an 
Internet-Draft (which gets deployed about the time it expires) or slog 
all the way to some flavor of RFC. In principle, Experimental should be 
a lower bar than Proposed Standard, but I'm not sure how much lower the 
bar is in practice.

("Maybe we don't need full IETF consensus on your idea before you figure 
out whether your idea is horrible" :-)

Spencer

> (All my personal opinions, of course.)
>
> Jari
>


From nobody Tue Apr 15 15:58:13 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB54B1A0027 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 15:58:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 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, USER_IN_WHITELIST=-100] autolearn=ham
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 5dZpbbp9qvVS for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 15:58:05 -0700 (PDT)
Received: from news.winserver.com (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 983301A0028 for <ietf@ietf.org>; Tue, 15 Apr 2014 15:58:05 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2554; t=1397602676; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=nikQtC+iuBEzXHCCCJPemdpC0EQ=; b=p2LjWsu3voJRBSElJP6P 6O4kLcbZsfmiCIjWQ9X/P92c90j853UPJCrXlYZrHssgB3+SfVj1MaVtXtJfYFeT qpjgah0yQxXAl+ENrbFeEbus90dKop6gMOomhYtO+g9dGCtHgBPJFirFO2zOi0lb VCVaWX1D4wz1eMwMeJA6jeQ=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 18:57:56 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 711253096.3.3568; Tue, 15 Apr 2014 18:57:56 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2554; t=1397602609; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=7cCBM+s pr2F0InQxlS6boEtPfRN+fT1pcMK7vGXPD/c=; b=Qo9dsGc3hX3dCPsw8mog2ii cwc9gg60RqXcYuSkXWj8NszRB0xcoW57PWRTc/7W09fDq65KXhkeKSunNYvW44sj qcpZ1xcoo+J5699It+CiWVunEha7SLrY2qAVq1D9Z2WVzqQmpqqClZeqvM/oxQ9N CCTBoxiGP9JbnPJvtoMo=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 15 Apr 2014 18:56:49 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 730785906.9.8504; Tue, 15 Apr 2014 18:56:49 -0400
Message-ID: <534DB973.3000403@isdg.net>
Date: Tue, 15 Apr 2014 18:57:55 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>, Dave Crocker <dcrocker@bbiw.net>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net> <534DB093.5020507@qti.qualcomm.com>
In-Reply-To: <534DB093.5020507@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qcMzv_FGOA5fuS4bm7BLEeFiWI0
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 22:58:11 -0000

On 4/15/2014 6:20 PM, Pete Resnick wrote:
> On 4/14/14 9:23 AM, Dave Crocker wrote:
>
>> Mediators, like mailing lists, take final delivery and post a new
>> message.  In formal terms, it's legitimate for them to create a
>> different rfc5322.From field, including one that looks like some
>> sort of 'rewrite' of the one used by the original author.
>
> It's legitimate for a mailing list to rewrite the author, but it would
> be wrong. :-)

+1.

> More seriously: If the mailing list wishes to express that I am the
> author of *this message*, then I belong in the "From:" field. That
> differs semantically from forwarding a message authored by me; then
> the list is saying that the list is the author, and it is simply
> quoting me, but that the list is the entity that should be considered
> to have written the message. For most mailing lists, that seems like
> the wrong semantics to try to convey.
>
> There should be a mechanism for an author to send a message to a
> mailing list, granting the mailing list permission to redistribute
> that message, and have that permission conveyed to the mailing list
> recipient such that when the mailing list recipient receives the
> message, they can assure themselves that the originating domain is OK
> with that redistribution. Sounds like some protocol which could be
> written.

The methods was developed.  It was discussed during SSP, proposed in 
2006 DSAP I-D [1] as an Authorized, or Allowed Signer List (ASL),  and 
Murray wrote 2012 ATPS [2] to piggy back off the ADSP as an extension.

I've implemented ADSP, ATPS in our Mailing List Server (MLS).  A 
wizard was created [3] for public usages. A private version used for 
customers for their DKIM manager. I've held back on DMARC support but 
it will be the exact logic add.

> (If the originating domain is expressly *not* OK with the
> redistribution, the mailing list should bounce the message back to the
> author saying as much.)

I would suggest it be more of an ACCEPT + NOTIFY with explanation 
rather than bounce, but yet, the denial is needed.  Its also described 
in DSAP and I believed also in Murray's DKIM Mailing List BCP [4].

-- 
HLS

[1] DKIM Signature Authorization Protocol
     http://tools.ietf.org/html/draft-santos-dkim-dsap-00

[2] DKIM Authorized Third-Party Signatures
     http://tools.ietf.org/html/rfc6541

[3] DKIM Policy Zone Record Generator and Test Simulator v2.7
     http://www.winserver.com/public/wcadsp

[4] DKIM and Mailing Lists
     http://tools.ietf.org/html/bcp167



From nobody Tue Apr 15 16:00:38 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00BB01A0027 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 Bw6pr-i3AIKi for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:00:34 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 0909B1A0023 for <ietf@ietf.org>; Tue, 15 Apr 2014 16:00:33 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id lf10so10119865pab.41 for <ietf@ietf.org>; Tue, 15 Apr 2014 16:00:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hCTGZ3ply7hNEG6eEa0ezSa6fHqcmErjxMStoBpqTvg=; b=EjrvCymGhuhhpVS5QYBO0C+QDPNyU2giC0vxjf018r112cTrmMHPllG+YgQj1SlQ1c gHDjS/opACKu6j/SFKZFN6Aw59UM+L4fIadGQmbbCqXO5safKnF4cglpgSyfwmghygZ+ abqGQngT1tHFsjKN3WhUs763o6Nbd4KgGd9oEWbdVBfd5Ifk/MVeGmLE6CueSexiTYaS YDl9W1UJGhUEGtE21IisZj5OS8oKw3T/smOP2uXpAjxDQveWy5c0KOKO4T3Ut2qdUdyv MqhdeKuJdPC1noGHmEip6ZtfIJX0mRGE+wjPWFAUUxURIEb2Rw9UFIus4tnpk56TKevM D3GA==
X-Received: by 10.68.201.97 with SMTP id jz1mr4885065pbc.26.1397602831125; Tue, 15 Apr 2014 16:00:31 -0700 (PDT)
Received: from [172.24.22.37] (wireless-nat-20.auckland.ac.nz. [130.216.30.131]) by mx.google.com with ESMTPSA id y4sm42644052pbk.76.2014.04.15.16.00.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 16:00:30 -0700 (PDT)
Message-ID: <534DBA0F.2050507@gmail.com>
Date: Wed, 16 Apr 2014 11:00:31 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net> <534DB093.5020507@qti.qualcomm.com>
In-Reply-To: <534DB093.5020507@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JGtj8oHO2CoCHW6-ZWcsVT_gtiY
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 23:00:35 -0000

Pete,

On 16/04/2014 10:20, Pete Resnick wrote:
...

> (If the originating domain is expressly *not* OK with the
> redistribution, the mailing list should bounce the message back to the
> author saying as much.)

Isn't that exactly what p=reject implies? If so, the logical behaviour
for all list software would be to check the DMARC record for the
originating domain of each message, and bounce it if p=reject.

   Brian


From nobody Tue Apr 15 16:03:51 2014
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C291A0027 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:03:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 B5ce8F7Vc9Lh for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:03:47 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id 4C32C1A0023 for <ietf@ietf.org>; Tue, 15 Apr 2014 16:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s3FN3f8K020556; Wed, 16 Apr 2014 01:03:41 +0200 (CEST)
Received: from [192.168.217.105] (p548928B7.dip0.t-ipconnect.de [84.137.40.183]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 5264C1DF3; Wed, 16 Apr 2014 01:03:40 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <534DB785.7040609@gmail.com>
Date: Wed, 16 Apr 2014 01:03:38 +0200
X-Mao-Original-Outgoing-Id: 419295818.838241-c1aadab06b88e0142614aa6b9e4ee2e2
Content-Transfer-Encoding: quoted-printable
Message-Id: <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/whiAuV0gNYcw_pxRQbZ3m2IJ2vk
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 23:03:48 -0000

On 16 Apr 2014, at 00:49, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:

> The idea was that you could declare a specific Internet-Draft "good =
enough for now", for a variety of reasons (which varied from proposal to =
proposal), and one of the reasons could be "we're going to stop working =
on this draft until we get some implementation experience".

Working groups can do that today.

E.g., httpbis calls out some of their HTTP/2.0 drafts as =93implementation=
 drafts=94.

Giving this qualification a slightly more formal standing (as in a place =
in the datatracker, an easily accessible list of implementation drafts =
on the web site, etc.) might help inform implementers that aren't =
following the entire WG mailing list traffic whether it is time to go =
ahead implementing.

(Of course, the interesting part will be how to properly manage the =
expectation of stability.)

Gr=FC=DFe, Carsten


From nobody Tue Apr 15 16:14:51 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26EB61A0029 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:14:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.573
X-Spam-Level: 
X-Spam-Status: No, score=-1.573 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 ujQeFACMmjEW for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:14:43 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 15BDE1A002F for <ietf@ietf.org>; Tue, 15 Apr 2014 16:14:42 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WaCYo-0003LY-Ia; Tue, 15 Apr 2014 23:14:38 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id D724A580893; Tue, 15 Apr 2014 19:14:37 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397603677; bh=ZSJqey6qDtP+BATFteylskabDjDwT8mYMKpiaJ0Q45E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ekHRRGvjQWNMv2d2vJTcN6KYkZn4UROIrKC78ourNUd6s9FyeeXmFJw41JlF+l3Cr SspGwbswU9/9vwsZkGvZ+JrJflU/8/bIBSB6T2boGANgjsfH52GIHmFSWbwZT7APbf gmDOErTpzLxxFOynIKTmTBynEHmbJ5hG708C1Ka8=
Date: Tue, 15 Apr 2014 19:14:37 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <20140415231437.GP4456@thunk.org>
References: <robbat2-20140408T031810-279861577Z@orbis-terrarum.net> <alpine.BSF.2.00.1404072357400.73388@joyce.lan> <01P6EEIPML6600004W@mauve.mrochek.com> <6.2.5.6.2.20140408101346.0ccb5e88@resistor.net> <alpine.BSF.2.00.1404081325130.76892@joyce.lan> <5347C698.6040108@tana.it> <534ACB5F.7060400@isdg.net> <534CE53A.7090000@tana.it> <534D9D12.4080602@isdg.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534D9D12.4080602@isdg.net>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UedbNpx40rvoMdRDXQmP0sTTUyg
Cc: ietf@ietf.org, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 23:14:47 -0000

On Tue, Apr 15, 2014 at 04:56:50PM -0400, Hector Santos wrote:
> 
> I think adding temporarily helps and the additional text about DMARC
> certainly helps.
> 
> But the problem is YAHOO doesn't want you to do this (rewrite).

That's OK, we didn't want Yahoo turning on DMARC p=reject.  Life's
tough sometimes.

> 
> Case in point, lets say a real bad message got into the list, unsigned,
> purported from Yahoo, the 5322.From was rewritten and distributed to other
> list users and some of those users were "harmed" in some fashion that it
> worth the effort to sue.   Guess who would be at legal fault here?  Not
> YAHOO. They are legally protected.  The MLM, who wistfully and intentionally
> ignored policy and even went as far to break the security, is now at risk.

The message was unsigned before it hit the mailing list, and it's
unsigned after the mailing list altered the from field.  So the
mailing list software did nothing to "break" security in that case.
Furthermore, the from field would be "username@yahoo.com.INVALID".  So
obviously there is nothing that can be said about whether the message
came from a yahoo user or not.

Cheers,

							- Ted



From nobody Tue Apr 15 16:15:06 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC2441A0062 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:15:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 fYXCvW2Z9jNu for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:15:00 -0700 (PDT)
Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtpout001.mac.com [17.172.220.236]) by ietfa.amsl.com (Postfix) with ESMTP id 318511A0059 for <ietf@ietf.org>; Tue, 15 Apr 2014 16:15:00 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N4300C7EHWNP350@st11p02mm-asmtp001.mac.com> for ietf@ietf.org; Tue, 15 Apr 2014 23:14:50 +0000 (GMT)
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <534DB093.5020507@qti.qualcomm.com>
Date: Wed, 16 Apr 2014 00:14:47 +0100
Message-id: <763CF376-1776-489A-A97E-FB65E77214BF@me.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net> <534DB093.5020507@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaGBEKTEMXGx0EGx0YBBIZBBsTEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxseGmJCH2luHBkTGXhzB xlsGBkbHkUYEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGxMQGx4aHxsRCl5ZF2FNGGN sEQpMRhdia2sRCkNaFxgbGQQbGBkEGxMYBBkaEQpEWBceEQpESRceEQpCRRdmUH1dH21kGgVIY xEKQk4XbHBgeUAdYlJpGmIRCkJMF2dJH215aRh+ckJNEQpCbBdlaGUYbU0cGENGThEKQkAXb0J QXX1NaX4dG1ARCnBnF2hzTGleXXpOZRNTEQpwaBdiXlt/bVtnekgBQhEKcGgXY0xGUBwbRBlYX BgRCnBoF2ZvaGFhfnt+BRx9EQpwaBdsRmNmHFplQ3MYchEKcGgXaEJdem5jT2F4fAERCnBsF2t mTmtBZV9mU2cBEQpwTBdgeXxlWWYebkQbQxE=
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-15_03:2014-04-15,2014-04-15,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404150387
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2egdtyAKhFi2vFqoKBNXqzw3dBY
Cc: John C Klensin <john-ietf@jck.com>, Dave Crocker <dcrocker@bbiw.net>, "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 23:15:05 -0000

On 15 Apr 2014, at 23:20, Pete Resnick <presnick@qti.qualcomm.com> wrote:
> On 4/14/14 9:23 AM, Dave Crocker wrote:
>> Mediators, like mailing lists, take final delivery and post a new message.  In formal terms, it's legitimate for them to create a different rfc5322.From field, including one that looks like some sort of 'rewrite' of the one used by the original author.
> 
> It's legitimate for a mailing list to rewrite the author, but it would be wrong. :-)
> 
> More seriously: If the mailing list wishes to express that I am the author of *this message*, then I belong in the "From:" field. That differs semantically from forwarding a message authored by me; then the list is saying that the list is the author, and it is simply quoting me, but that the list is the entity that should be considered to have written the message. For most mailing lists, that seems like the wrong semantics to try to convey.
> 
> There should be a mechanism for an author to send a message to a mailing list, granting the mailing list permission to redistribute that message, and have that permission conveyed to the mailing list recipient such that when the mailing list recipient receives the message, they can assure themselves that the originating domain is OK with that redistribution. Sounds like some protocol which could be written.
> 
> (If the originating domain is expressly *not* OK with the redistribution, the mailing list should bounce the message back to the author saying as much.)

That suffers the same problems as X-O-A-R: you have to know when to trust the intermediate.  In the absence of that knowledge, any message transformation is invisible to the recipient, and potentially malicious.  You would have to invent a scheme for identifying transformations, so users could verify them against the original sender's signature.

DMARC has put *ALL* the trust into the From: field.  That is very unfortunate, but it seems to be the DMARC peoples' idea of a foolproof, user-visible identifier.

Cheers,
Sabahattin


From nobody Tue Apr 15 16:15:29 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66EF51A0063 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.698
X-Spam-Level: 
X-Spam-Status: No, score=0.698 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 y-3o4hcEpFd0 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:15:22 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 4B8181A0059 for <ietf@ietf.org>; Tue, 15 Apr 2014 16:15:22 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 0A3BCD043F1; Tue, 15 Apr 2014 19:15:19 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1397603719; bh=SecHU6I4zdO38IIXAkn89QX7qTsN81AYkIL/vLDIC+0=; h=In-Reply-To:References:Subject:From:Date:To:From; b=V/YcHsKM/UqLVcJeAl6YEikj1MkCKKSf5FUgGMu6jRRfLRjv1uYI5gjFajm1ScW2q tNtWhYYjrOgI4VZIcJn8n68FUa32uBySU/bsA4LP6GmNSg3BlU3Brbp6+DwoelerrQ cetWLzkSe94Yz29+2NLR21X9MsZRMANJeDOmniZc=
Received: from [IPV6:2600:1003:b120:6c43:5810:e380:3212:8f9] (unknown [IPv6:2600:1003:b120:6c43:5810:e380:3212:8f9]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 8A4B6D04326; Tue, 15 Apr 2014 19:15:18 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <534D5D84.2020307@dcrocker.net>
References: <20140414024956.26078.qmail@joyce.lan> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <1485381.SfhK6qmW0I@scott-latitude-e6320> <534D5D84.2020307@dcrocker.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
From: Scott Kitterman <scott@kitterman.com>
Date: Tue, 15 Apr 2014 19:15:15 -0400
To: ietf@ietf.org
Message-ID: <09c2d02c-2595-4134-b55c-d71796228adc@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Fkr97NWRNhncLam0xXhbSwtHyk4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 23:15:28 -0000

On April 15, 2014 12:25:40 PM EDT, Dave Crocker <dhc@dcrocker.net> wrote:
>On 4/14/2014 8:35 PM, Scott Kitterman wrote:
>> On Monday, April 14, 2014 10:26:44 Murray S. Kucherawy wrote:
>>> I mentioned in another thread that the DMARC people did come to the
>IETF to
>>> ask for a working group to complete development of the work on the
>>> standards track.  This request was denied on the grounds that DMARC
>was
>>> essentially already done, and thus the IETF had nothing
>engineering-wise to
>>> contribute.  There were also too few people that were not already
>DMARC
>>> proponents that would commit to working on it.
>>>
>>> (And as I said on that other thread, I'm happy to stand corrected if
>I've
>>> mischaracterized any of that.)
>>
>> My perception (and it may also be wrong) is that anyone who claimed
>there was
>> work yet to be done was shouted down.
>
>Given that the exchanges were on an open mailing list, I'm not quite 
>sure what that means.
>
>What I am sure of is that I've pressed quite vigorously and repeatedly,
>
>first on the open dmarc.org mailing list and then on the IETF DMARC 
>mailing list, for folk to cite work that needed to be done and to 
>develop group support for that work.
>
>What I saw was some individuals suggesting some bits of work, but no 
>support developed around it.  (By 'support' I mean more than a few
>folk.)
>
>Perhaps you can point to specific examples of this 'shouting down' 
>happening?
>
>What I also saw was some folk insisting that the charter be vague and 
>unconstrained, with no concern for the installed base.
>
>
>> As I said in the other thread, I think the only reason it was
>perceived as
>> done is that the private group that developed the spec declared it
>done and
>> fought against any WG charter language that would have permitted
>changes to
>> the core protocol.    Based on that approach, no wonder it was
>declined.
>
>Changes to the core of a protocol is the essence of de-stabilizing its 
>installed base.
>
>Writing a charter that permits de-stabilizing a substantial installed 
>base only makes sense when there is a clear and compelling basis
>already 
>known for needing to make such changes.
>
>With respect to DMARC, none has been offered or has developed community
>
>support.
>
>Writing a charter that permits de-stablilizing an installed base 
>covering 60% of the world's email traffic, in the absence of a clear
>and 
>compelling understanding of the need would be irresponsible.
>
>Arguably, the mere existence of such a charter would be de-stabilizing,
>
>since it means that anyone considering adoption has an excuse to defer 
>it to the indefinite future, when the IETF might get around to
>releasing 
>a revision.
>
Considering we're just in the finishing stages of spfbis, which you participated in significantly, and none of those fears were realized despite a charter that permitted incompatible changes if really needed I have a hard time understanding how you would believe all that to be true. 

I think we entirely agree on the facts.  I fully concur you have been loud and vigorous.

I also think it's not at all surprising given the volume and vigor coming from the DMARC developers that not that many people jumped up and lept into the fray.

Scott K


From nobody Tue Apr 15 16:17:29 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF1601A0012 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.573
X-Spam-Level: 
X-Spam-Status: No, score=-1.573 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 Ouqoh_t7o6tb for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:17:27 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 1A9B11A000B for <ietf@ietf.org>; Tue, 15 Apr 2014 16:17:27 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WaCbQ-0003Ll-RI; Tue, 15 Apr 2014 23:17:20 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 35967580893; Tue, 15 Apr 2014 19:17:20 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397603840; bh=P6pVGGPifL1k56/WHd9D7LYbfEEv/aHcH+H7FFLUE+Y=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=gA170T520y3cUyU1t+hy1VoeL2v9EKUrmLtYTqhTO6e/tjSrGdrnjqJbgFJHoY+Nk JChA1gdJSxY+q5cVVCknlIHXN4wq2LvUVrGnu2n6I1JQKse3M1b4MIrcsTqomBiEUp pM5xB+889vJtNVj6IdC7SnHJQ/5+q7DFlfK+99IA=
Date: Tue, 15 Apr 2014 19:17:20 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
Message-ID: <20140415231720.GQ4456@thunk.org>
References: <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net> <534DB093.5020507@qti.qualcomm.com> <534DBA0F.2050507@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534DBA0F.2050507@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ec00qu0LBwvkeGIsQvAGL81zl-o
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 23:17:27 -0000

On Wed, Apr 16, 2014 at 11:00:31AM +1200, Brian E Carpenter wrote:
> 
> > (If the originating domain is expressly *not* OK with the
> > redistribution, the mailing list should bounce the message back to the
> > author saying as much.)
> 
> Isn't that exactly what p=reject implies? If so, the logical behaviour
> for all list software would be to check the DMARC record for the
> originating domain of each message, and bounce it if p=reject.

The question is which is more or less unfriendly? 

1)  Forbidding yahoo.com users from participating on mailing lists

2)  Rewriting the from field of yahoo.com users.

I could easily see the mailing list software making this be
configurable, so it's up to each mailing list admin.  :-)

	      	      	    	 	      	      - Ted

P.S.  #1 could also be combined with a nice message inviting the
yahoo.com user to find another e-mail provider.


From nobody Tue Apr 15 16:36:16 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA1D1A000B for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 JUqWDFeOz_Am for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:36:10 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id B3B381A0002 for <ietf@ietf.org>; Tue, 15 Apr 2014 16:36:10 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.149.140]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3FNZrli000525 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 15 Apr 2014 16:36:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397604965; bh=2panHpeCnEYc0Dkpf9h6Nemr3qwOhodYoqeqr4Qm0+k=; h=Date:To:From:Subject:In-Reply-To:References; b=PKctdy/NHp+ByB2DIhSgnyXn37VX2Fs742EFgxD1aPidSzbHgD7QKUlYk5GnXcIWy fAhVQx63LPCyZwR8V+h3UKBk9jODARcO1CtmYDaJW/6gu/iKtyzdL307067/bQf5Bg UhJkLh3QmI62xAwmOrSQj/zzkPZtVC51O+9uNTD0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397604965; i=@elandsys.com; bh=2panHpeCnEYc0Dkpf9h6Nemr3qwOhodYoqeqr4Qm0+k=; h=Date:To:From:Subject:In-Reply-To:References; b=uofd125CI/5zWJjbOoHWoeMVVVt2TPnYgLGBoGr3/tm1TCi8XffNK9lK1bejwGRj2 7ZxOTyFjURd4jJuCPdN+jrw9WtA51KH68s1uICwvZSiWPgG6vjx6vqFtDIFe3sLSjZ kG4UCKu81+qlXdLhHzZGg9akRQAfFD1Ymfohdqds=
Message-Id: <6.2.5.6.2.20140415133648.0df89818@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 15 Apr 2014 15:36:20 -0700
To: "MH Michael Hammer (5304)" <MHammer@ag.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Let's talk (was: DMARC: perspectives from a listadmin of large open-source lists)
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D4749E@USCLES544.agna.am greetings.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com> <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.gmail.com> <6.2.5.6.2.20140415111633.0da3d030@resistor.net> <CE39F90A45FF0C49A1EA229FC9899B0507D4749E@USCLES544.agna.amgreetings.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-ulsD1QZSEronpGTM6MK9p_8V1w
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 23:36:15 -0000

Hi Mike,
At 13:30 15-04-2014, MH Michael Hammer (5304) wrote:
>My experience with regard to working groups is that it is 
>(technically) easy to participate and does not necessarily involve 
>any particular costs. I don't go to IETF meetings but have 
>participated in WG sessions during IETF meetings through jabber. Not 
>the optimal solution but it works. I think that the notion of 8000lb 
>gorillas somewhat misrepresents the situation. Some of the active 
>participants in the working groups I've been involved with continue 
>their involvement even when they change employers. With that in 
>mind, I believe that in many cases it truly is the individual and 
>not the individual as mouthpiece for the organization. I also 
>believe that the 8000lb gorillas have many of the same interests as 
>smaller organizations and individuals even though there are times 
>where interests may diverge. It's also clear to me that there is not 
>uniformity of interests across constituencies within large 
>organizations. It's complex. So let's talk.

It is, as you mentioned, complex.  I'll be one-sided in this 
comment.  There is a cost to participation on the mailing lists and 
to attend meetings.  There is a higher burden for a small company or 
an individual.  People from small companies sometimes get ignored or 
it is like the minority view (see Dave Cridland's message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg87389.html ).

I can understand that an individual is not the mouthpiece of the 
organization if that individual sometimes speaks up to say that 
management is saying X but he or she does not think that it is a 
great idea.  You have tried to be positive by discussing about this 
publicly, politely and without resorting to marketing 
language.  Let's see who else would like to talk.

Regards,
S. Moonesamy  


From nobody Tue Apr 15 16:44:53 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE1D71A0002 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:44:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 kbjY1w8aFWAW for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 16:44:50 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 963831A0049 for <ietf@ietf.org>; Tue, 15 Apr 2014 16:44:50 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id wp18so11484012obc.21 for <ietf@ietf.org>; Tue, 15 Apr 2014 16:44:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=GB0+OgGbKxmRVnVlJlmxnenWXoH2mgeCnI8mYzrOZ7M=; b=KMI6bLTqeWzYYbhru2Sk03WkcemnYhx5WYS53mbUkxpiV1WksCJdQVkUzdr4P+QrJl PPdBd0MkIgdHk1OXySWzJGGddEzMAge5FFdDjEwX3yHpOWUIt6lG4ZfbNj8yAuvviN/w cfUF2wS3FFtMUOXBZXJFBf4QeADQD28EDlg8PhodzSxSiwci6lnFePY/cOq2Z/qaHgit iyrBDK4ypvswZ7pUDSNOM+zfrYpOJNPCTt9ogBzjTKXG+FILYQVlSGMjXyks2/zdRfwa gLhInltPBYVGyWNrwr/oGMInSAijIdNHVUEvJRj3tsYoy2WblF0Gb0sF0LiLZlOytnVW /XSg==
X-Received: by 10.182.55.3 with SMTP id n3mr3832192obp.55.1397605487528; Tue, 15 Apr 2014 16:44:47 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id wy2sm36292036obc.21.2014.04.15.16.44.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 16:44:47 -0700 (PDT)
Message-ID: <534DC46C.60703@gmail.com>
Date: Tue, 15 Apr 2014 18:44:44 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org>
In-Reply-To: <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/52mNaQ2pi4isoXNHklv_IxzigvA
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Apr 2014 23:44:52 -0000

On 04/15/2014 06:03 PM, Carsten Bormann wrote:
> On 16 Apr 2014, at 00:49, Spencer Dawkins <spencerdawkins.ietf@gmail.com> wrote:
>
>> The idea was that you could declare a specific Internet-Draft "good enough for now", for a variety of reasons (which varied from proposal to proposal), and one of the reasons could be "we're going to stop working on this draft until we get some implementation experience".
> Working groups can do that today.
>
> E.g., httpbis calls out some of their HTTP/2.0 drafts as “implementation drafts”.
>
> Giving this qualification a slightly more formal standing (as in a place in the datatracker, an easily accessible list of implementation drafts on the web site, etc.) might help inform implementers that aren't following the entire WG mailing list traffic whether it is time to go ahead implementing.

Exactly.

> (Of course, the interesting part will be how to properly manage the expectation of stability.)

Indeed. Some proposals included a longer-than-six-months expiration 
date, and some other proposals established an archival series (the 
documents weren't called RFCs).

There are various ways to go. We'd just need to pick one.

Spencer


From nobody Tue Apr 15 17:16:07 2014
Return-Path: <serrhini@mail.ru>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 268B31A004E for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 17:16:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.15
X-Spam-Level: ***
X-Spam-Status: No, score=3.15 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HELO_EQ_RU=0.595, HOST_EQ_RU=0.875, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 eWb8kSSTtRRx for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 17:15:59 -0700 (PDT)
Received: from f361.i.mail.ru (f361.i.mail.ru [217.69.141.3]) by ietfa.amsl.com (Postfix) with ESMTP id 1F30A1A004A for <ietf@ietf.org>; Tue, 15 Apr 2014 17:15:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=mail.ru; s=mail2;  h=References:In-Reply-To:Content-Type:Message-ID:Reply-To:Date:Mime-Version:Subject:To:From; bh=Sqtppb5+xyhLKlonzrpGP2Nsr8L4D2kzSzCH9FXcJRM=;  b=uaDDk03TXKpANiP/SSyFnPElVywOgkEuw4a00b1dK974Vm7hxGrOJs2ghbIeIRtnjWhGd4gsNscxIqTUZ4cesRHBZIVl/iASww+zxJqWf048gegej2rNpwtpBcgc6VWCr3SKGMyz20ZDDqYFZcefvNfS9vyQ7JlJGaWLbpJv4pc=;
Received: from mail by f361.i.mail.ru with local (envelope-from <serrhini@mail.ru>) id 1WaDW4-0001Di-Mx; Wed, 16 Apr 2014 04:15:52 +0400
Received: from [41.137.68.4] by e.mail.ru with HTTP; Wed, 16 Apr 2014 04:15:52 +0400
From: =?UTF-8?B?bW9oYW1tZWQgc2Vycmhpbmk=?= <serrhini@mail.ru>
To: =?UTF-8?B?VGhlb2RvcmUgVHMnbw==?= <tytso@mit.edu>, =?UTF-8?B?aWV0ZkBpZXRmLm9yZw==?= <ietf@ietf.org>
Subject: =?UTF-8?B?UmVbMl06IERNQVJDIGFuZCB5YWhvbw==?=
Mime-Version: 1.0
X-Mailer: Mail.Ru Mailer 1.0
X-Originating-IP: [41.137.68.4]
Date: Wed, 16 Apr 2014 04:15:52 +0400
X-Priority: 3 (Normal)
Message-ID: <1397607352.389753533@f361.i.mail.ru>
Content-Type: multipart/alternative; boundary="--ALT--6tvzelpv1397607352"
X-Mras: Ok
X-Spam: undefined
In-Reply-To: <20140415214348.GL4456@thunk.org>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3IBgUWAFWMrUpmQlz2IVffMb1_c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: =?UTF-8?B?bW9oYW1tZWQgc2Vycmhpbmk=?= <serrhini@mail.ru>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 00:16:01 -0000

----ALT--6tvzelpv1397607352
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

ClRoZSBwcm9ibGVtIGlzIHdpdGggdGhlIGFsaWdubWVudCByZXF1aXJlbWVudHMgb2YgRE1BUkMu
ICBUaGF0IGNhbid0IGJlIGVhc2lseSBmaXhlZCB3aXRob3V0IGJyZWFraW5nIGV4aXN0aW5nIG1h
aWxpbmcgbGlzdCBmdW5jdGlvbmFsaXR5LmFuZMKgIHRvIGdpdmUgb3RoZXJzICBtYWlsIHNlcnZp
Y2VzIGhhZCBtYWRlIHRoZSBuZWNlc3NhcnkgY2hhbmdlcy4KWWFob28gcmVjb2duaXplcyB0aGF0
wqAgIiBZYWhvbyBpcyB0aGUgZmlyc3QgbWFqb3IgZW1haWwgcHJvdmlkZXIgaW4gdGhlIHdvcmxk
IHRvIGFkb3B0IHRoaXMgIGFnZ3Jlc3NpdmUgbGV2ZWwgb2YgRE1BUkMgcG9saWN5IG9uIGJlaGFs
ZiBvZiB0aGVpcnMgdXNlcnMuICIKdG8gcHJvdGVjdCB1c2VycyB3ZSBkbyBub3QgbmVlZCB0byBi
ZSBhZ2dyZXNzaXZlIC4KCgoK0KEg0YPQstCw0LbQtdC90LjQtdC8LAptb2hhbW1lZCBzZXJyaGlu
aQpzZXJyaGluaUBtYWlsLnJ1Cg==

----ALT--6tvzelpv1397607352
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

CjxIVE1MPjxCT0RZPjxicj4KVGhlIHByb2JsZW0gaXMgd2l0aCB0aGUgYWxpZ25tZW50IHJlcXVp
cmVtZW50cyBvZiBETUFSQy4gIFRoYXQgY2FuJ3QgYmUgZWFzaWx5IGZpeGVkIHdpdGhvdXQgYnJl
YWtpbmcgZXhpc3RpbmcgbWFpbGluZyBsaXN0IGZ1bmN0aW9uYWxpdHkuYW5kJm5ic3A7IHRvIGdp
dmUgb3RoZXJzIDxzcGFuPiBtYWlsIHNlcnZpY2VzIGhhZCBtYWRlIHRoZSBuZWNlc3NhcnkgY2hh
bmdlcy48L3NwYW4+PGJyPjxzcGFuPllhaG9vIHJlY29nbml6ZXMgdGhhdCZuYnNwOyAiPHNwYW4+
WWFob28gaXMgdGhlIGZpcnN0IG1ham9yIGVtYWlsIHByb3ZpZGVyIGluIHRoZSB3b3JsZCB0byBh
ZG9wdCB0aGlzIDxzcGFuIHN0eWxlPSJ0ZXh0LWRlY29yYXRpb246IHVuZGVybGluZTsiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6IDM2cHg7IGNvbG9yOiByZ2IoMjU0LCA5NCwgOTQpOyB0ZXh0LWRl
Y29yYXRpb246IHVuZGVybGluZTsiPmFnZ3Jlc3NpdmU8L3NwYW4+PC9zcGFuPiBsZXZlbCBvZiBE
TUFSQyBwb2xpY3kgb24gYmVoYWxmIG9mIHRoZWlycyB1c2Vycy48L3NwYW4+PC9zcGFuPiI8YnI+
dG8gcHJvdGVjdCB1c2VycyB3ZSBkbyBub3QgbmVlZCB0byBiZSBhZ2dyZXNzaXZlIC48YnI+PGJy
IHN0eWxlPSJvdmVyZmxvdzogYXV0bzsiIGRpcj0ibHRyIiBpZD0idGlueW1jZSIgY2xhc3M9Im1j
ZUNvbnRlbnRCb2R5ICIgb25sb2FkPSJ3aW5kb3cucGFyZW50LnRpbnlNQ0UuZ2V0KCdjb21wb3Nl
XzIxNDFfY29tcG9zZUVkaXRvcicpLm9uTG9hZC5kaXNwYXRjaCgpOyIgY29udGVudGVkaXRhYmxl
PSJ0cnVlIj4KCTxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXItbGVmdDoxcHggc29saWQgIzA4NTdB
NjsgbWFyZ2luOjEwcHg7IHBhZGRpbmc6MCAwIDAgMTBweDsiPjxkaXYgaWQ9IiI+PGRpdiBjbGFz
cz0ianMtaGVscGVyIGpzLXJlYWRtc2ctbXNnIj4KCgkKPC9kaXY+CgoKPC9kaXY+CjwvYmxvY2tx
dW90ZT4KPGJyPgo8YnI+0KEg0YPQstCw0LbQtdC90LjQtdC8LDxicj5tb2hhbW1lZCBzZXJyaGlu
aTxicj5zZXJyaGluaUBtYWlsLnJ1PGJyPjwvQk9EWT48L0hUTUw+Cg==

----ALT--6tvzelpv1397607352--


From nobody Tue Apr 15 17:34:15 2014
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A5D91A006C for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 17:34:14 -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, SPF_PASS=-0.001] autolearn=ham
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 84TtZOAamGxC for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 17:34:12 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6641A0065 for <ietf@ietf.org>; Tue, 15 Apr 2014 17:34:12 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id kx10so10144777pab.5 for <ietf@ietf.org>; Tue, 15 Apr 2014 17:34:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=X2/UOl3NwKj4HTC3l7LbkEtoj+N/NGU5v1qwGqNWDpg=; b=dJOgKIoaPfk0nc7GCHG9QpnB7xS2pA9N/0XhrDTFiMoURUbNemcKErgjqAHQIXBnC8 Fvkew0cLOIm8BpckqyxNrd892NXB4T5BmvFoZD9EeM9UtUsKjnfOLKmxV14bFcxT4GbM hl3M7X+brjqLRhLzNQldh+2pkrGhLgUNKf6dtwF2HULpkjusuDZOJyLz3Yhi8+6VuLNG wAFms6L3J33PTV6KEYmo5Y3/5LziABY9Ij5E9AK75QHcuxk3228kqtprb8t4nvv0s6IQ /N08t4SxZRRauyATDvAcfNC7E01Gq8dvL9jsQ/izzUIbify5AMURNIYf+sz31KOE04kj 7sLA==
X-Received: by 10.68.227.4 with SMTP id rw4mr5227534pbc.3.1397608449386; Tue, 15 Apr 2014 17:34:09 -0700 (PDT)
Received: from [192.168.15.4] (184-76-96-188.war.clearwire-wmx.net. [184.76.96.188]) by mx.google.com with ESMTPSA id yj6sm28417546pab.19.2014.04.15.17.34.07 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 17:34:08 -0700 (PDT)
Message-ID: <534DCFFB.4080102@gmail.com>
Date: Tue, 15 Apr 2014 18:34:03 -0600
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru>
In-Reply-To: <1397607352.389753533@f361.i.mail.ru>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050108020809000909000708"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qvuJfoyRR91bSHvPhWrwwzvrV8k
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 00:34:14 -0000

This is a cryptographically signed message in MIME format.

--------------ms050108020809000909000708
Content-Type: multipart/alternative;
 boundary="------------000108060500000708000801"

This is a multi-part message in MIME format.
--------------000108060500000708000801
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

Yahoo does not seem to require DMARK. Simply use one of the other two=20
options. I use SPF for my domains, and it makes it through their systems =

just fine.

It looks to me that some want to be able to send list email to many from =

a bogus email address (some-domain.invalid). Simply stop doing that. One =

of the responsibilities of being a list maintainer is cleaning up all of =

bounced mess from no longer valid email addresses. I have advocated in=20
the past for a email header that allows a bounced message to be=20
automatically routed for the correct reason back to the list maintainer=20
for processing by automated processes. Maybe it is time to revisit that=20
proposal.

I used to get thousands of spams from forged email. I get almost none=20
now. If I got thousands, Yahoo must get millions. I applaud them for=20
their courage to take a stand.

On 04/15/2014 06:15 PM, mohammed serrhini wrote:
>
> The problem is with the alignment requirements of DMARC. That can't be =

> easily fixed without breaking existing mailing list functionality.and  =

> to give others mail services had made the necessary changes.
> Yahoo recognizes that  "Yahoo is the first major email provider in the =

> world to adopt this aggressivelevel of DMARC policy on behalf of=20
> theirs users."
> to protect users we do not need to be aggressive .

--=20

Doug Royer - (K7DMR.us / DougRoyer.com)
DouglasRoyer@gmail.com
714-989-6135


--------------000108060500000708000801
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta content=3D"text/html; charset=3DISO-8859-1"
      http-equiv=3D"Content-Type">
  </head>
  <body bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Yahoo does not seem to require DMARK.
      Simply use one of the other two options. I use SPF for my domains,
      and it makes it through their systems just fine.<br>
      <br>
      It looks to me that some want to be able to send list email to
      many from a bogus email address (some-domain.invalid). Simply stop
      doing that. One of the responsibilities of being a list maintainer
      is cleaning up all of bounced mess from no longer valid email
      addresses. I have advocated in the past for a email header that
      allows a bounced message to be automatically routed for the
      correct reason back to the list maintainer for processing by
      automated processes. Maybe it is time to revisit that proposal.<br>=

      <br>
      I used to get thousands of spams from forged email. I get almost
      none now. If I got thousands, Yahoo must get millions. I applaud
      them for their courage to take a stand.<br>
      <br>
      On 04/15/2014 06:15 PM, mohammed serrhini wrote:<br>
    </div>
    <blockquote cite=3D"mid:1397607352.389753533@f361.i.mail.ru"
      type=3D"cite">
      <br>
      The problem is with the alignment requirements of DMARC. That
      can't be easily fixed without breaking existing mailing list
      functionality.and&nbsp; to give others <span> mail services had mad=
e
        the necessary changes.</span><br>
      <span>Yahoo recognizes that&nbsp; "<span>Yahoo is the first major e=
mail
          provider in the world to adopt this aggressive<span
            style=3D"font-size: 36px;"></span> level of DMARC policy on
          behalf of theirs users.</span></span>"<br>
      to protect users we do not need to be aggressive .<br>
    </blockquote>
    <br>
    <pre class=3D"moz-signature" cols=3D"72">--=20

Doug Royer - (K7DMR.us / DougRoyer.com)
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:DouglasRoyer@gmail.c=
om">DouglasRoyer@gmail.com</a>
714-989-6135
</pre>
  </body>
</html>

--------------000108060500000708000801--

--------------ms050108020809000909000708
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMhzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGSzCCBTOgAwIBAgIDCXp9MA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTQwMzMwMTMwMjIz
WhcNMTUwMzMwMjMzNjMxWjBjMRkwFwYDVQQNExBDclhsb0tOcDhuNUxjMW53MR8wHQYDVQQD
DBZEb3VnbGFzUm95ZXJAZ21haWwuY29tMSUwIwYJKoZIhvcNAQkBFhZEb3VnbGFzUm95ZXJA
Z21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvgDR3UbGHtnMaqNw
FtsXf5VxjGKQWuVUhAJoKnxzI7Hf/gH7fFN/uGYB1HQiPDUOF/X2aIapC98ycdsZeHZ1iRIz
Qe5ag581kNFxztRWdqvPtK/nnXiB1qw8sVahmkC9JpZeh0KjymnB1D9vCHGJ+4l1bs9SB/aU
1pQ+zZVU+1bZJyUm9D7RN1+jrzkWbYqBAV99XoNodSbENuEB+skUGFMwxKZmAFWgAVIKMzWf
5rs3tP0Do2p1O+OaPkvxzkgo3thX/RPmMYPhpuewURcq+HQ6YRW+r7oZ97H9PaOrrwslKBu4
70sAAhbfd0LmCv3gXRnRTWMRnNVotY1jjqfapQIDAQABo4IC3DCCAtgwCQYDVR0TBAIwADAL
BgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSQ
5w5XWt3QI8FUbPINB9XajsHB6DAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAh
BgNVHREEGjAYgRZEb3VnbGFzUm95ZXJAZ21haWwuY29tMIIBTAYDVR0gBIIBQzCCAT8wggE7
BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29t
L3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n
IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENv
bSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGlu
IGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQv
MC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsG
AQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20v
Y2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEARwipb/dALl2bQ7lZoavGzjro5vv3
yZ5PU2a+ZPLJaOOio6C1qfzoVmrwITTphp2VNACjbHJ9RHXbUi1WhMafgIw/YMXOj8cOlUFJ
2qz8R1WiK2Gt+aOVlgiin91pOpHlWUBlkhgH4yk1BAz1wcuZ5AWgm2r9g1DYX+NBLh6/IyPv
+1Imc9LoDJVwcatovbsa+zEEU3psvXEELJpwS4QPxWSYbDcuTL8jvA1HvXR1i8YtYJjm8A/u
VyxgNpve4UxrmNyya+vGMmRkOYAYt7ck4tuqe1L2NyErDhk7PIst1nxnEUPbRGTmSH2eQarV
lkDKXqdsl6bxWL72jZ0Kt+xgRDGCA90wggPZAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQG
A1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNh
dGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVk
aWF0ZSBDbGllbnQgQ0ECAwl6fTAJBgUrDgMCGgUAoIICHTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA0MTYwMDM0MDNaMCMGCSqGSIb3DQEJBDEWBBTi
8/TFF+/gFIv2276+U7CIPQX5KDBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcG
BSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBD
ZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg
SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCXp9MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDEL
MAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBE
aWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEg
UHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMJen0wDQYJKoZIhvcNAQEBBQAEggEA
skT8nMsVaLPlpmoRZiiBAMWs5Ve8TqJGgbiGJP5/3pXvvW7o3kGMMbugnodqW14J8+p30IF8
50I8AnT1cCTZkxRP1FZYAXL7VtPGFHjkS6iEYVU/+YDc0jYcVv4MJeLarBntNXJK4DpA340t
3EPAD8Z9Pd9CBgP0N4yUaXKkN2jPOq+AItGsuzT0p5r4E09dQmFCN8sCa0I6A/MmJMkVqzEm
khC+iE/btNYvgeWyH6jt2K06LBUOnrdXdyItGBpt0ykLlQeYE73abgjgZ4dt0TcDxEi2vp28
b8l6cl09c04Glh03R3CvhLovtU4mTrTbhynchOKKIbHMSDalnlsi9wAAAAAAAA==
--------------ms050108020809000909000708--


From nobody Tue Apr 15 18:22:15 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA2D1A0068 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.573
X-Spam-Level: 
X-Spam-Status: No, score=-1.573 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 S43JpDxGUYYJ for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:22:10 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 3B1DE1A0034 for <ietf@ietf.org>; Tue, 15 Apr 2014 18:22:10 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WaEYA-0003y0-Vw; Wed, 16 Apr 2014 01:22:07 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id C7714580893; Tue, 15 Apr 2014 21:22:05 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397611325; bh=XaaWVcSO7w7PAbqPckrmwCN915HZV1Us389V6hXVyqU=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ZxfT5UJrj4vDjm2XtC/q3wVJTTa8Av/XC4yUVJAjkxtbGZ7G40JVSHeMGSuj3Vm6z EMl05evNZq5/vydhLB6kl/daV/B8cCIx6l73JBpQheWptMovzYYU4xG6L3PJzl+xn2 PPpk0CzpDXSHayGLnRTPq+UYUbB/PmG13EkGI1do=
Date: Tue, 15 Apr 2014 21:22:05 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Doug Royer <douglasroyer@gmail.com>
Subject: Re: DMARC and yahoo
Message-ID: <20140416012205.GC12078@thunk.org>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534DCFFB.4080102@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iIJxAoRp_GM4vTjNGeonVnKv1Ic
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 01:22:14 -0000

On Tue, Apr 15, 2014 at 06:34:03PM -0600, Doug Royer wrote:
> Yahoo does not seem to require DMARK. Simply use one of the other two
> options. I use SPF for my domains, and it makes it through their systems
> just fine.

You seem to be confused about what the problem is.  It's not that
Yahoo is requiring DMARK.  The problem is that Yahoo is requesting
that *other* mailers reject mail if the From field is not aligned with
the Sender, and the From field is from yahoo.com.

This means that if a bob@yahoo.com sends a message to a list which
includes alice@hotmail.com, and the mailing list server keeps the from
field as "bob@yahoo.com", and sends the message to all of the mailing
list recipients, which includes alice@hotmail.com, the following things will happen:

a) hotmail.com will compare the sender address (authenticated with
   SPF) with the from address (authenticated by DKIM), see that they
   are different, and since yahoo.com has a DEMARK p=reject,
   hotmail.com will bounce the mail.

b) this means alice@hotmail.com will never see bob@yahoo.com's mail

c) since the mailing list server receives a bounce from hotmail.com,
   if there are enough attempts from yahoo.com users to send mail to
   the mailing list, the number of bounces will cause the mailing list
   server to suspend or remove alice@hotmail.com from the mailing
   list.

If we munge the from field from bob@yahoo.com to
bob@yahoo.com.INVALID, then hotmail.com will not bounce the mailing
list mail.  This means Alice will see Bob's message, and Alice will
not be in danger of getting suspended or dropped from the mailing list.

Alternatively, the mailing list server could determine the Bob is
sending his mail from a domain that has a DEMARK p=reject policy, and
simply bounce the mail back to Bob right away, instead of sending it
to the mailing list recipients.  That way, Bob's can get pursuaded to
use another mail provider, and Alice doesn't have to worry about
getting suspended from the mailing list.


Do you have another suggestion about what the mailing list server is
supposed to do?

						- Ted


From nobody Tue Apr 15 18:38:43 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F0661A0025 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.142
X-Spam-Level: **
X-Spam-Status: No, score=2.142 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_16=0.6, SPF_NEUTRAL=0.779] autolearn=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 tIWa8cGceA8c for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:38:36 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id D8E191A0010 for <ietf@ietf.org>; Tue, 15 Apr 2014 18:38:35 -0700 (PDT)
Received: (qmail 19609 invoked from network); 16 Apr 2014 01:38:32 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 16 Apr 2014 01:38:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9a10.534ddf17.k1404; i=johnl@user.iecc.com; bh=5xOZmgvp2+UcI7FuuTjsfQw9hwiJaPRGQrSHfDWA04o=; b=UeRbY9snhjMLGYRUqjbrHM0Kni6wnExkCZE2sh5DqRVyVI0PeLl5m6og2bAjc8qVwmgmZDfEKlhRO5+4EPVUZ+84ei7iZdYq+BEoL6XqzcnHsCjdEEU1FSiTj2JRBnS6z13gsO14qDs20h9G0sAAQqdXiwGuixqnsdEKlL2b7OWoxPSmKoLVXCxDpqsDLsAYjTLFUfZk+tHvKPCou8YFbNZgUs+EibludDP0dehomiwihfrOsHpbZFYT+68lZ8it
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9a10.534ddf17.k1404; olt=johnl@user.iecc.com; bh=5xOZmgvp2+UcI7FuuTjsfQw9hwiJaPRGQrSHfDWA04o=; b=QaB3hOmucNjTCxugsA57p2E7F1dJ1q/fSuOTabtsd6nGN/7ymIZcBaeekXAb3r8zY/fb5gTLVisNblZgTQuX6H5+5tsYjYD2Kyv18z/J30Jvp0Zhg/L08HBOc9fntGpcx+yyhyy8V7171IYCHnFJhGj0kTFD2sQodSWEmPuJxVSGsW7MPbsxcmUsD0VsADtvSR4ARq9xfwr82DwLtQfvx3qtVkk6yldnoaVL0ks2n+owHezX3Jg1JHfnEiw+YGF9
Date: 16 Apr 2014 01:38:09 -0000
Message-ID: <20140416013809.39439.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534DBA0F.2050507@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2GsA7XhYBRjNElPIwgK66eK01NE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 01:38:41 -0000

>> (If the originating domain is expressly *not* OK with the
>> redistribution, the mailing list should bounce the message back to the
>> author saying as much.)
>
>Isn't that exactly what p=reject implies? If so, the logical behaviour
>for all list software would be to check the DMARC record for the
>originating domain of each message, and bounce it if p=reject.

That's certainly been mentioned a lot of times and is certainly consistent
with what p=reject says it means.


The problem is pragmatic: there are a lot of people who use Yahoo's
mail, very few of them understand the technology very well, and they'd
see this as just another baffling thing that happens on their
computers.  I would like to encourage all of the Yahoo users on my
lists to find a better provider, but that will take years.  In the
meantime, the church has a lot of meetings to organize.  It's a market
power problem, not a technical problem.

R's,
John


From nobody Tue Apr 15 18:44:37 2014
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA4D1A0033 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:44:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_21=0.6, SPF_PASS=-0.001] autolearn=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 mY4BlH0IdljT for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:44:33 -0700 (PDT)
Received: from mail-pb0-x22b.google.com (mail-pb0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 7ECAC1A0031 for <ietf@ietf.org>; Tue, 15 Apr 2014 18:44:33 -0700 (PDT)
Received: by mail-pb0-f43.google.com with SMTP id um1so10218871pbc.16 for <ietf@ietf.org>; Tue, 15 Apr 2014 18:44:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=XRYm0G25TbeKl0QzM1ztbZnCJFWeHqdUPS+P0pcZxqw=; b=I8OQ2t1CmvrEYxhTKhXu8s9YLLUiV5KMo1AdD7jtbdt4mNzbkVxaOyns93d98pVO1n XA8sVEBbk2JduEZSGGRhNklp5GInopEyVp5xSw2QzcgQ2VmknsMMGZ17pAM+pINHOyJC vijlLxFNR9c5tE/rlTdBmfmnpsGi+N7shBYNvF2wNjbB5UOXF3+pO8gr84ojUm86fnpI VDPMtOUldEM+OeMnxja72hk3teq1YvrBC5jRS8h2O6QNRFjHTGhmeNB4dZ4X2ovv4tCJ +VVF6fWSOW0cp4ZkLdumvVW1PVogfxcJ8a1aKgi2fm8wKAR0TVIqvDsV/q+W7FWAk99p K0TQ==
X-Received: by 10.68.204.162 with SMTP id kz2mr5426348pbc.13.1397612670547; Tue, 15 Apr 2014 18:44:30 -0700 (PDT)
Received: from [192.168.15.4] (184-76-96-188.war.clearwire-wmx.net. [184.76.96.188]) by mx.google.com with ESMTPSA id iv2sm43232358pbc.19.2014.04.15.18.44.28 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 18:44:29 -0700 (PDT)
Message-ID: <534DE079.5050206@gmail.com>
Date: Tue, 15 Apr 2014 19:44:25 -0600
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org>
In-Reply-To: <20140416012205.GC12078@thunk.org>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms050305050300030400070508"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PtnoPSQK2a0PirJfS85k99OvcUk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 01:44:35 -0000

This is a cryptographically signed message in MIME format.

--------------ms050305050300030400070508
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

On 04/15/2014 07:22 PM, Theodore Ts'o wrote:
> On Tue, Apr 15, 2014 at 06:34:03PM -0600, Doug Royer wrote:
>> Yahoo does not seem to require DMARK. Simply use one of the other two
>> options. I use SPF for my domains, and it makes it through their syste=
ms
>> just fine.
> You seem to be confused about what the problem is.  ...

Yes, I did misunderstand. Now I wonder if the yahoo techs understood the =

effects.

> Do you have another suggestion about what the mailing list server is
> supposed to do?
>
Munge the from address to be the list-name@yahoo ? Odd, but would that wo=
rk?


--=20

Doug Royer - (K7DMR.us / DougRoyer.com)
DouglasRoyer@gmail.com
714-989-6135



--------------ms050305050300030400070508
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMhzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGSzCCBTOgAwIBAgIDCXp9MA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTQwMzMwMTMwMjIz
WhcNMTUwMzMwMjMzNjMxWjBjMRkwFwYDVQQNExBDclhsb0tOcDhuNUxjMW53MR8wHQYDVQQD
DBZEb3VnbGFzUm95ZXJAZ21haWwuY29tMSUwIwYJKoZIhvcNAQkBFhZEb3VnbGFzUm95ZXJA
Z21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvgDR3UbGHtnMaqNw
FtsXf5VxjGKQWuVUhAJoKnxzI7Hf/gH7fFN/uGYB1HQiPDUOF/X2aIapC98ycdsZeHZ1iRIz
Qe5ag581kNFxztRWdqvPtK/nnXiB1qw8sVahmkC9JpZeh0KjymnB1D9vCHGJ+4l1bs9SB/aU
1pQ+zZVU+1bZJyUm9D7RN1+jrzkWbYqBAV99XoNodSbENuEB+skUGFMwxKZmAFWgAVIKMzWf
5rs3tP0Do2p1O+OaPkvxzkgo3thX/RPmMYPhpuewURcq+HQ6YRW+r7oZ97H9PaOrrwslKBu4
70sAAhbfd0LmCv3gXRnRTWMRnNVotY1jjqfapQIDAQABo4IC3DCCAtgwCQYDVR0TBAIwADAL
BgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSQ
5w5XWt3QI8FUbPINB9XajsHB6DAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAh
BgNVHREEGjAYgRZEb3VnbGFzUm95ZXJAZ21haWwuY29tMIIBTAYDVR0gBIIBQzCCAT8wggE7
BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29t
L3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n
IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENv
bSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGlu
IGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQv
MC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsG
AQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20v
Y2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEARwipb/dALl2bQ7lZoavGzjro5vv3
yZ5PU2a+ZPLJaOOio6C1qfzoVmrwITTphp2VNACjbHJ9RHXbUi1WhMafgIw/YMXOj8cOlUFJ
2qz8R1WiK2Gt+aOVlgiin91pOpHlWUBlkhgH4yk1BAz1wcuZ5AWgm2r9g1DYX+NBLh6/IyPv
+1Imc9LoDJVwcatovbsa+zEEU3psvXEELJpwS4QPxWSYbDcuTL8jvA1HvXR1i8YtYJjm8A/u
VyxgNpve4UxrmNyya+vGMmRkOYAYt7ck4tuqe1L2NyErDhk7PIst1nxnEUPbRGTmSH2eQarV
lkDKXqdsl6bxWL72jZ0Kt+xgRDGCA90wggPZAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQG
A1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNh
dGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVk
aWF0ZSBDbGllbnQgQ0ECAwl6fTAJBgUrDgMCGgUAoIICHTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA0MTYwMTQ0MjVaMCMGCSqGSIb3DQEJBDEWBBSH
0fXrWJ8Lk/UsWV7lv8G76/oOSjBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcG
BSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBD
ZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg
SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCXp9MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDEL
MAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBE
aWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEg
UHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMJen0wDQYJKoZIhvcNAQEBBQAEggEA
G4LhgegvvkJCBRHmps2v4+B/432Ewo3VxcMLGNaBz5L4tnYu1prsDqq93JyxS9W0f5HB6kh4
MGfORmH6ahVpM9isubtotYMfFIAS5eTR8H02ScpKC/ont6j4Ct9OMzAOBkIdmxakz7RttAU5
JVR8YGOJHNQZ8pKxfXwqWl0QMhGCsWOfQbu5Q84HiqJsVwCl6FqAF845pOjsyjcsMhvOD9A5
BEyQLmMSlqkzjE5kIgbYMCfyUdjwx5sZ7FOCIiGufmR1mgw72yV4cz0fpgxAZbIhbiXdT6IF
X6vQlH/N44eSaS/rxKTHnFgi8mDYXW2TbJcixvdgrFYPPQ8XHTKhvQAAAAAAAA==
--------------ms050305050300030400070508--


From nobody Tue Apr 15 18:45:56 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A4311A0034 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:45:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 zy-BA-iwASn0 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:45:50 -0700 (PDT)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 512EF1A0033 for <ietf@ietf.org>; Tue, 15 Apr 2014 18:45:50 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id md12so10260108pbc.37 for <ietf@ietf.org>; Tue, 15 Apr 2014 18:45:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=ucCOMfw07Ew5hjRoBIR4ghNtm2O91VQpJLapYY02eLg=; b=u8Km+OufCtfdAIiJeYR4lJThYAQ/AeOd8G09hXdhvhQIQlPULAKYZE+BWfzFeXOsxP wI6EQfiuRQckZl5kF9xlmFJemeUStIHzIg3l7qruJ6iP65plCp2CYmbexZaUKHX7BQ9f BeVy3DKhGNhgoMMA53Y9W31IcV4ORBgwYCbot/JNTgFAJsfF7VIP8nPcTy62dBTHv0t8 GVFPy6dM8rUNmhHmTjxqdURi++o0UHgkVmYcELU0koOFai6y/RZVFfRl3Ym9NE37DTAz ZXHwuIHs1pLSQGB3omkq6GlU1KVYhVSOIIJhqnR6VDKcQUnCBW0e2q3Ii6l0OvMw7Ko0 X/tA==
X-Received: by 10.67.23.135 with SMTP id ia7mr5429988pad.5.1397612747309; Tue, 15 Apr 2014 18:45:47 -0700 (PDT)
Received: from dhcp150.priv.bungi.com (c-24-4-159-60.hsd1.ca.comcast.net. [24.4.159.60]) by mx.google.com with ESMTPSA id gg3sm43215185pbc.34.2014.04.15.18.45.45 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 15 Apr 2014 18:45:46 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_377C4C47-4DA5-44E4-A352-BF890D73F636"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC and yahoo
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <534DCFFB.4080102@gmail.com>
Date: Tue, 15 Apr 2014 18:45:45 -0700
Message-Id: <23DD0EB7-D083-4329-B5B5-51F1A38BA4CD@gmail.com>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com>
To: Doug Royer <douglasroyer@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/a_LIKuoV3CZqREWF_jvfKSGgo1E
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 01:45:54 -0000

--Apple-Mail=_377C4C47-4DA5-44E4-A352-BF890D73F636
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Apr 15, 2014, at 5:34 PM, Doug Royer <douglasroyer@gmail.com> wrote:

> Yahoo does not seem to require DMARK. Simply use one of the other two =
options. I use SPF for my domains, and it makes it through their systems =
just fine.

Dear Doug,

There's confusion about DMARC policy.  Policy is based on the domain in =
the =46rom header field as indicated at _dmarc.<email-domain>.  If the =
=46rom header contains "somebody@yahoo.com", then policy located at:

_dmarc.yahoo.com. IN TXT "v=3DDMARC1\; p=3Dreject\; sp=3Dnone\; =
pct=3D100\; rua=3Dmailto:dmarc-yahoo-rua@yahoo-inc.com, =
mailto:dmarc_y_rua@yahoo.com\;"
means any validation not aligned with yahoo.com is to be rejected.

> It looks to me that some want to be able to send list email to many =
from a bogus email address (some-domain.invalid). Simply stop doing =
that.

No. Having emailing lists change ]=46rom headers to =
"somebody@yahoo.com.invalid" sidesteps onerous _dmarc. policy (which =
prevents mailing-list use).

It seems 5 organizations outweigh 30,000 smaller groups.  There are =
scalable solutions such as ATP.  DMARC, on its own, requires all =
services to be under their domain.

> One of the responsibilities of being a list maintainer is cleaning up =
all of bounced mess from no longer valid email addresses. I have =
advocated in the past for a email header that allows a bounced message =
to be automatically routed for the correct reason back to the list =
maintainer for processing by automated processes. Maybe it is time to =
revisit that proposal.
>=20
> I used to get thousands of spams from forged email. I get almost none =
now. If I got thousands, Yahoo must get millions. I applaud them for =
their courage to take a stand.

What you describe reflects most mailing lists that are generally better =
managed than the general corpus of messages directly from yahoo.com =
itself.  This is also why I wrote the ATP protocol.  ATP offers sending =
domains a means to select an ATP label hashes of domains they or the =
community considers well-managed third-party services.  Such exceptions =
will not invite abuse.

Regards,
Douglas Otis


--Apple-Mail=_377C4C47-4DA5-44E4-A352-BF890D73F636
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><div><br></div><div><div><div>On Apr 15, 2014, at =
5:34 PM, Doug Royer &lt;<a =
href=3D"mailto:douglasroyer@gmail.com">douglasroyer@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">
 =20
    <meta content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3D"Content-Type">
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Yahoo does not seem to require DMARK.
      Simply use one of the other two options. I use SPF for my domains,
      and it makes it through their systems just =
fine.<br></div></div></blockquote><div><br></div><div>Dear =
Doug,<div><br></div><div>There's confusion about DMARC policy. =
&nbsp;Policy is based on the domain in the =46rom header field as =
indicated at _dmarc.&lt;email-domain&gt;. &nbsp;If the =46rom header =
contains "<a href=3D"mailto:somebody@yahoo.com">somebody@yahoo.com</a>", =
then policy located at:</div><div><br></div><div><div style=3D"margin: =
0px; font-family: Monaco; background-color: rgb(255, 232, 202); =
position: static; z-index: auto;">_<a =
href=3D"http://dmarc.yahoo.com">dmarc.yahoo.com</a>.&nbsp;IN&nbsp;TXT&nbsp=
;"v=3DDMARC1\; p=3Dreject\; sp=3Dnone\; pct=3D100\; rua=3D<a =
href=3D"mailto:dmarc-yahoo-rua@yahoo-inc.com">mailto:dmarc-yahoo-rua@yahoo=
-inc.com</a>, <a =
href=3D"mailto:dmarc_y_rua@yahoo.com">mailto:dmarc_y_rua@yahoo.com</a>\;"<=
/div></div><div>means any validation not aligned with <a =
href=3D"http://yahoo.com">yahoo.com</a> is to be =
rejected.</div></div><div><br></div><blockquote type=3D"cite"><div =
bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"moz-cite-prefix">
     =20
      It looks to me that some want to be able to send list email to
      many from a bogus email address (some-domain.invalid). Simply stop
      doing that. </div></div></blockquote><div><br></div><div>No. =
Having emailing lists change ]=46rom headers to "<a =
href=3D"mailto:somebody@yahoo.com.invalid">somebody@yahoo.com.invalid</a>"=
 sidesteps onerous _dmarc. policy (which prevents mailing-list =
use).</div><div><br></div><div>It seems 5 organizations outweigh 30,000 =
smaller groups. &nbsp;There are scalable solutions such as ATP. =
&nbsp;DMARC, on its own, requires all services to be under their =
domain.</div><div><br></div><blockquote type=3D"cite"><div =
bgcolor=3D"#FFFFFF" text=3D"#000000"><div class=3D"moz-cite-prefix">One =
of the responsibilities of being a list maintainer
      is cleaning up all of bounced mess from no longer valid email
      addresses. I have advocated in the past for a email header that
      allows a bounced message to be automatically routed for the
      correct reason back to the list maintainer for processing by
      automated processes. Maybe it is time to revisit that =
proposal.<br>
      <br>
      I used to get thousands of spams from forged email. I get almost
      none now. If I got thousands, Yahoo must get millions. I applaud
      them for their courage to take a =
stand.<br></div></div></blockquote><div><br></div><div>What you describe =
reflects most mailing lists that are generally better managed than the =
general corpus of messages directly from <a =
href=3D"http://yahoo.com">yahoo.com</a> itself. &nbsp;This is also why I =
wrote the ATP protocol. &nbsp;ATP offers sending domains a means to =
select an ATP label hashes of domains they or the community considers =
well-managed third-party services. &nbsp;Such exceptions will not invite =
abuse.</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div></div></div></body></html>=

--Apple-Mail=_377C4C47-4DA5-44E4-A352-BF890D73F636--


From nobody Tue Apr 15 18:47:22 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 09C3A1A0034 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:47:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.573
X-Spam-Level: 
X-Spam-Status: No, score=-1.573 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 CMRt1tVePKVD for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 18:47:19 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 672BD1A0033 for <ietf@ietf.org>; Tue, 15 Apr 2014 18:47:19 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WaEwV-0003z4-MK; Wed, 16 Apr 2014 01:47:15 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 9E348580893; Tue, 15 Apr 2014 21:47:14 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397612834; bh=AKFgiQ8dJEdSrG3l719HhgUWl0gSzPztP3cqPrgVFb4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fCQD4/Uicz1XwtSej+J1dEEl2tEpbfnVTQHGGhHeEvpSNbLQO1YcclXrhsptMQETI 3Acrx4ddXdlzXKgKBhvkpse0hFyNOTuFD66810BRAALE1B9WO1u0TGEMJwr4I2rScQ 3WteR8QotQFVTgRkKvVKOHYlTwIED5RwYvFSHtu0=
Date: Tue, 15 Apr 2014 21:47:14 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Doug Royer <douglasroyer@gmail.com>
Subject: Re: DMARC and yahoo
Message-ID: <20140416014714.GD12078@thunk.org>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <534DE079.5050206@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534DE079.5050206@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eScRFJCDqtSBKA6qfosPPqK38T8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 01:47:20 -0000

On Tue, Apr 15, 2014 at 07:44:25PM -0600, Doug Royer wrote:
> On 04/15/2014 07:22 PM, Theodore Ts'o wrote:
> >On Tue, Apr 15, 2014 at 06:34:03PM -0600, Doug Royer wrote:
> >>Yahoo does not seem to require DMARK. Simply use one of the other two
> >>options. I use SPF for my domains, and it makes it through their systems
> >>just fine.
> >You seem to be confused about what the problem is.  ...
> 
> Yes, I did misunderstand. Now I wonder if the yahoo techs understood the
> effects.

Apparnetly, they believe that mailing list traffic is "insignificant".

So if only an insignificant number of yahoo.com users are encouraged
to switch to another mail provider, I'm asusming they won't mind....

	     	       	   	    	       - Ted


From nobody Tue Apr 15 19:18:39 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A55FB1A0034 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 19:18:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.943
X-Spam-Level: **
X-Spam-Status: No, score=2.943 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_14=0.6, SPF_NEUTRAL=0.779] autolearn=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 c3V5y8InFSp6 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 19:18:32 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6AD491A00B0 for <ietf@ietf.org>; Tue, 15 Apr 2014 19:18:31 -0700 (PDT)
Received: (qmail 24494 invoked from network); 16 Apr 2014 02:18:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=5fad.534de873.k1404; bh=YphY30qnr67+yJUlU7O9pJbiPHdOBSpzmmR3qtkOtHM=; b=Tc5aLxD2Xc9d6YlaJ7COXUaIE4/ql/vXBKtSsucsR7ezSkVtik7nc73qfLU+9ZJgFgYqeDOgohn2thYPRz4eVTG5NkpORvOt8VBA8LVD5jem6XAWH3IjrPdlcdTP7C54jc5Hk7qdGozLEDqmKxxIzXmkcGlcLO8/5okqpLodqdQWku/EiVxU2tF1ZJLikU3juEoiisj5Wdbk2kxljr6f/IpVoJjGN4sdl2BAzTVeKMlSje9OAKNAAyaPfCo4JKKt
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=5fad.534de873.k1404; bh=YphY30qnr67+yJUlU7O9pJbiPHdOBSpzmmR3qtkOtHM=; b=eqFn6waY5myFsgm7Gv8WG6xD4R08S5xRNdpF7fOgaDX1sgCsOy8Ec4p7HJf21wDCdHgOO5AhV+ZOYFOJgzvUpTHEki6u6qInoUU76e2L/Pi2e+c4TgeVSfcomVHfMeOW3O2QdFwoaHwm8G7SFfezKnbcxldV+bcVeByOIHfo9nUxCJ+6meVWSkUPrML5aCmGCqD3TKba5ISPuiDXmX6kXLuhsOgNQs8ZxQNmXPKB3EAzCKWnVW3SCYIZ7dDRqtHh
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 16 Apr 2014 02:18:26 -0000
Date: 15 Apr 2014 22:18:26 -0400
Message-ID: <alpine.BSF.2.00.1404151832460.38826@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: (DMARC) Why mailing lists are only sort of special
In-Reply-To: <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Onvufv1kugK6uYTv6_PNeON3LgI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 02:18:37 -0000

Murray asked a couple of interesting questions, which I will address 
separately in separate message threads.

To the question why are mailing lists special, they're somewhat special, 
but they're more interesting here as canaries in the coal mine.

As a rough estimate, roughly 90% of e-mail is spam, most of what's left is 
bulk broadcast mail, most of what's left after that is transactional 
sort-of-broadcast mail, and the little bit at the end is discussion lists, 
individual mail, and some miscellaneous other stuff.  Nonetheless, people 
have consistently said that they want to get their individual mail, and 
don't care about the broadcast mail.  I'm not aware of surveys where they 
ask specifically about discussion lists, but since each message is 
generally hand written by an identifiable person, I'd expect people to 
consider it a lot closer to individual mail than the daily blast from 
BigCo.

So mailing list mail is special for the same reason individual mail is 
special--it's the mail people want.

The reason it's not special is that it's just the most visible example of 
a wide variety of legitimate useful mail that DMARC can't describe, and 
that are broken by DMARC policies other than p=none.

For example, I send and receive my Yahoo mail on my Gmail account, and 
have done so for years.  Gmail makes the obvious checks to ensure that 
it's my account, so it's just as secure as sending from Yahoo, and it's 
useful.  Or it was useful until last weekend. Now a lot of it bounces.

Or there's the WSJ's mail an article feature.  It's useful, nobody abuses 
it.  Yahoo users can't use it any more.

There's lots of these, and the only thing "wrong" with them is that DMARC 
can't distinguish them from other somewhat similar mail sources that send 
spam.  The proposals I'm seeing from the DMARC cartel are basically Google 
Purge applied to e-mail:

http://www.theonion.com/articles/google-announces-plan-to-destroy-all-information-i,1783/

Surely we can do better than that, but that's the next message.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Tue Apr 15 19:23:32 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 689871A00D7 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 19:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level: 
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 LMck-f3rOBMh for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 19:23:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 342A21A0034 for <ietf@ietf.org>; Tue, 15 Apr 2014 19:23:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 391C42003B; Tue, 15 Apr 2014 22:23:42 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 2AF6163ABA; Tue, 15 Apr 2014 22:23:23 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1161463A9E; Tue, 15 Apr 2014 22:23:23 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Theodore Ts'o" <tytso@mit.edu>
Subject: Re: DMARC and yahoo
In-Reply-To: <20140416012205.GC12078@thunk.org>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Tue, 15 Apr 2014 22:23:22 -0400
Message-ID: <24986.1397615002@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4F6q95oeS1CFgHevcLlVHNVb9O8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 02:23:31 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Theodore Ts'o <tytso@mit.edu> wrote:
    > This means that if a bob@yahoo.com sends a message to a list which
    > includes alice@hotmail.com, and the mailing list server keeps the from
    > field as "bob@yahoo.com", and sends the message to all of the mailing
    > list recipients, which includes alice@hotmail.com, the following thin=
gs will happen:

    > a) hotmail.com will compare the sender address (authenticated with
    > SPF) with the from address (authenticated by DKIM), see that they
    > are different, and since yahoo.com has a DEMARK p=3Dreject,
    > hotmail.com will bounce the mail.

    > b) this means alice@hotmail.com will never see bob@yahoo.com's mail

    > c) since the mailing list server receives a bounce from hotmail.com,
    > if there are enough attempts from yahoo.com users to send mail to
    > the mailing list, the number of bounces will cause the mailing list
    > server to suspend or remove alice@hotmail.com from the mailing
    > list.

So, as a WG chair, a person known to me just tried to post to the list
From=20a brand new yahoo.com mail account.  They aren't subscribed with that
address.  I would normally just approve, and add them...

It seems to me that I must now actually reject, because it would affect oth=
er
subscribers.

I'm now thinking that we need to remove all the @yahoo.com addresses from
posting to ietf mailing lists.

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU03pmoqHRg3pndX9AQKdOwP8DnYO/oOJikcselOAtOVii0jj33h8P20r
WQXlbPNSBv7QVBr2ZMBvCl7tWHekxBGDboH+VvOV6Ba4f8b1kupROqC2U0LHMp3o
EJcMhrqqI9IACByYQZ5h8Nv5gXk0rza89Vhw6hKp0DE5pDvXFfQaRNZ6mbbius9G
IftUf2MS5WE=
=TJ8v
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Tue Apr 15 19:38:24 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A30F1A0009 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 19:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 KY4d4PpmB0MH for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 19:38:19 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 7010B1A0011 for <ietf@ietf.org>; Tue, 15 Apr 2014 19:38:19 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WaFjq-0004H4-7n; Wed, 16 Apr 2014 02:38:14 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 5A399580893; Tue, 15 Apr 2014 22:38:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397615893; bh=I2IqAYlgIC9a8RZpI00rvlYt92W6gdo6X3Y0y/ejQ54=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=mVazR9XUSg7P273/akL7Y5d6vRUnNbBiQzSjKBhzJbFu9Jc0yNKjlecwQnXrDnomy P2LW/YTaew5xtOLO3SfW4DmX1hQGca+a9qmyKBnEbLzqR+cjzNoYhy7RRhK0dcmqcK pjfYOsBgjV63klmHIN1P51IGLhN0Z1mthbwkt8kk=
Date: Tue, 15 Apr 2014 22:38:13 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: DMARC and yahoo
Message-ID: <20140416023813.GA21807@thunk.org>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <24986.1397615002@sandelman.ca>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/o-LbCatkkJJyM0tMgRcirGf2x6k
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 02:38:22 -0000

On Tue, Apr 15, 2014 at 10:23:22PM -0400, Michael Richardson wrote:
> So, as a WG chair, a person known to me just tried to post to the list
> From a brand new yahoo.com mail account.  They aren't subscribed with that
> address.  I would normally just approve, and add them...
> 
> It seems to me that I must now actually reject, because it would affect other
> subscribers.
> 
> I'm now thinking that we need to remove all the @yahoo.com addresses from
> posting to ietf mailing lists.

So on my mailman configuration (which I believe is the default), if
alice@hotmail.com receives 5 hard fail bounces she will get
automatically suspended from the mailing list.  So a single e-mail
from a @yahoo.com address won't cause damage, and if seven days go by
without any further bounce messages, the "bounce counter" gets reset
to zero.  The problem comes if you have many e-mail messages from
yahoo.com users (which according to yahoo and the DMARC cheerleaders,
shouldn't happen happen, because mailing list traffic is
"insignificant" :-).

So this is what I've done on my church mailman setup.  First of all,
I've disabled bounce processing, so even if a yahoo.com posting slips
by, it won't do any damage.  (It does mean more bounce mail will end
up going to the list-owner address, which I'll then have to manually
deal with, but as a short-term hack, I'm willing to live with it).
Secondly, I've taken all of the yahoo.com users, and set the
moderation bit, so if they do send e-mail, it will be held for
moderation.

I can then manually cut and paste their e-mail and send it to them on
their behalf.  Unfortunately, about 25% of my church's governing board
is using Yahoo, and so this is something I was willing to do as a
short-term remediation, since I didn't want to just bounce their
e-mail or let their e-mail cause other Vestry members to be removed
from the mailing list.

In the long-term, I'm going to try to convince some of them to move to
another mail provider, or at least use another mail provider for
church business.  I'll also try to see if I can get a patch to mailman
so it will do the "username@yahoo.com" -> "username@yahoo.com.INVALID"
from header rewrite.  But that's not something I can do on short
notice, since this is a rather busy week for me.

I don't know what the ietf.org secretariat should do.  My short-term
remediations aren't very scalable, so what works for a small church
probably wouldn't work for the entire IETF.

What a mess.

							- Ted


From nobody Tue Apr 15 20:18:07 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 109811A005F; Tue, 15 Apr 2014 20:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=unavailable
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 rKfv5sND8k5i; Tue, 15 Apr 2014 20:17:58 -0700 (PDT)
Received: from mail-yh0-x231.google.com (mail-yh0-x231.google.com [IPv6:2607:f8b0:4002:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id 7CE3D1A0032; Tue, 15 Apr 2014 20:17:56 -0700 (PDT)
Received: by mail-yh0-f49.google.com with SMTP id z6so10270988yhz.8 for <multiple recipients>; Tue, 15 Apr 2014 20:17:53 -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:content-type; bh=RdLaIjpUlmYvBU39jUf92L0cPCy+vOoAGFKzQ7vpTGM=; b=LrPIFblzEBo93sxU4A5QB/tdjmDJTHUa+qsrtbT5xgrP0eKiWzfFQpbXNC4J9Cuu05 8yRJ9IN1p6rDVKZWLQ3AJ1LfPpZeDW4ozHN5DYJTGYTSfFxyxz/igvAJktlffavNxJIJ tnL5OFBMDtGvoLh48dGTmzpFUi6E/45cw0wUBinzQhWcVQwV1s0W8XlH46VSigKW/9VM Umy+uQ07mRyE0m54WfP8VUcnmSeEJ+SMyVahEf3jIpu01/Y2efdgJRtzoUoPuL5kUKdm OQOkv8/u/EQGpbnhwPP1Zd/pzMQafsvO2ScXTR64M8qubw58BtTxbgxVKoLyNijdfoCA I6TQ==
MIME-Version: 1.0
X-Received: by 10.236.199.212 with SMTP id x60mr8905011yhn.90.1397618273348; Tue, 15 Apr 2014 20:17:53 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Tue, 15 Apr 2014 20:17:53 -0700 (PDT)
In-Reply-To: <alpine.OSX.2.01.1404141912380.99918@rabdullah.local>
References: <20140404180001.19898.85635.idtracker@ietfa.amsl.com> <CADnDZ8-tg52c9FDZgHxgpSJjqPQvqAOg1hSR8usoRx-739msrA@mail.gmail.com> <CADnDZ88kDVKg6hYfYXtmYezARUCZW12ZEBXJ4n=tbM67YUKv2A@mail.gmail.com> <alpine.OSX.2.01.1404141912380.99918@rabdullah.local>
Date: Wed, 16 Apr 2014 04:17:53 +0100
Message-ID: <CADnDZ88+C6sfcxRh4fbdJuRxd0ZPAm2LVUnh0Rh21j3r8rXoLA@mail.gmail.com>
Subject: Re: Community Input Requested on Trustees' Intent to Renounce "IETF Secretariat" Trademark
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Ole Jacobsen <olejacobsen@me.com>
Content-Type: multipart/alternative; boundary=bcaec52c6223b6f14d04f7205c2e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/euorYKWA33XiRPprKItjUyQ-TTg
Cc: IAOC IAOC <iaoc@ietf.org>, "iab@iab.org" <iab@iab.org>, "iesg@ietf.org" <iesg@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 03:18:00 -0000

--bcaec52c6223b6f14d04f7205c2e
Content-Type: text/plain; charset=UTF-8

Hi Ole,

IMHO any registered organisation (even if volunteering) has a market which
has users/customers. If there is a market, then there should be a logo and
if there is a logo then that is a marketing signal, but will always need
marketing (planning and strategies) to make that organisation not die in
future within its markets (specially volunteering organisations don't last
without marketing).

@ Trustees:
My point 4 needs amendment as follows:

4) many companies use IETF documents/meetings and participate/host but are
there integrated projects among those companies by using the IETF
trademark. I think that the IETF general area can establish projects among
those companies to produce some new IETF products. In that situation I
think the secretariats trademark can be helpful within that general area
works/projects. So I hope you define (defined conditions or situations or
markets) when we need or don't need that secretariats trademark, also that
you have a plan when to bring it back registered if your defined conditions
apply.


On Tuesday, April 15, 2014, Ole Jacobsen wrote:

>
> AB,
>
> Why do you think this has *anything* to do with "marketing" ???
>
> Trademarks are there to protect brands and owners,


 Yes within its market.

so that somebody
> else cannot cause confusion by using the same name/mark/logo.
>
> That's all.


I don't think that is only the case. IMO it cost thousands for reasons not
just that. The confusion is related to users and those users may change to
use others. If no one uses IETF then it will close down, which trustees
should make sure not to let that happen.

AB

--bcaec52c6223b6f14d04f7205c2e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br>Hi Ole,<div><br></div><div>IMHO any registered=C2=A0organisation (even =
if volunteering) has a market which has users/customers. If there is a mark=
et, then=C2=A0there should be a logo and if there is a logo then that is a =
marketing signal,=C2=A0but will always need marketing (planning and strateg=
ies)=C2=A0to make that organisation not die in future within its markets=C2=
=A0(specially volunteering organisations don&#39;t last without marketing).=
=C2=A0=C2=A0</div>

<div><br></div><div>@ Trustees:</div><div>My point 4 needs amendment as fol=
lows:</div><div><br></div><div><font><span style=3D"background-color:rgba(2=
55,255,255,0)">4)=C2=A0many companies use IETF documents/meetings and parti=
cipate/host but are there integrated=C2=A0projects among those=C2=A0compani=
es by=C2=A0using the=C2=A0IETF trademark. I think=C2=A0that the IETF genera=
l area can establish projects among those=C2=A0companies to produce some ne=
w=C2=A0IETF products. In=C2=A0that situation I think the secretariats trade=
mark can be helpful within that general area works/projects.=C2=A0<span></s=
pan>So I hope you define (defined conditions or situations or markets)=C2=
=A0when we need or don&#39;t need that secretariats trademark, also that yo=
u have a plan when to bring it back registered if your defined conditions a=
pply.=C2=A0</span></font><br>

</div>
<div><br></div><div><br>On Tuesday, April 15, 2014, Ole Jacobsen  wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><br>
AB,<br>
<br>
Why do you think this has *anything* to do with &quot;marketing&quot; ???<b=
r>
<br>
Trademarks are there to protect brands and owners,=C2=A0</blockquote><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex"></blockquote><div><br></div><div>=C2=A0Yes within =
its market.=C2=A0</div>


<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">so that somebody<br>
else cannot cause confusion by using the same name/mark/logo.<br>
<br>
That&#39;s all.</blockquote><div><br></div><div>I don&#39;t think that is o=
nly the case. IMO it=C2=A0cost thousands=C2=A0for reasons not just that. Th=
e confusion is related to users and those=C2=A0users may change to use othe=
rs. If no one uses IETF then it will close down, which trustees should make=
 sure not to let that happen.=C2=A0</div>


<div><br></div><div>AB</div></div>

--bcaec52c6223b6f14d04f7205c2e--


From nobody Tue Apr 15 20:44:58 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 671901A004A for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 20:44:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.4
X-Spam-Level: *
X-Spam-Status: No, score=1.4 tagged_above=-999 required=5 tests=[BAYES_50=0.8,  J_CHICKENPOX_16=0.6] autolearn=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 DB6H6ZjV6i-m for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 20:44:51 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.31]) by ietfa.amsl.com (Postfix) with ESMTP id 54D591A0022 for <ietf@ietf.org>; Tue, 15 Apr 2014 20:44:51 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES533.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Tue, 15 Apr 2014 23:44:46 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: S Moonesamy <sm+ietf@elandsys.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Let's talk (was: DMARC: perspectives from a listadmin of large open-source lists)
Thread-Topic: Let's talk (was: DMARC: perspectives from a listadmin of large open-source lists)
Thread-Index: AQHPWQN9bKZz8hV0UEydk+uJkbO1MpsTa74Q
Date: Wed, 16 Apr 2014 03:44:45 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D47986@USCLES544.agna.amgreetings.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com> <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.gmail.com> <6.2.5.6.2.20140415111633.0da3d030@resistor.net> <CE39F90A45FF0C49A1EA229FC9899B0507D4749E@USCLES544.agna.amgreetings.com> <6.2.5.6.2.20140415133648.0df89818@elandnews.com>
In-Reply-To: <6.2.5.6.2.20140415133648.0df89818@elandnews.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.254.232]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tQAu9l3tFG-93aIYiLH3TlIcIrM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 03:44:56 -0000

> -----Original Message-----
> From: S Moonesamy [mailto:sm+ietf@elandsys.com]
> Sent: Tuesday, April 15, 2014 6:36 PM
> To: MH Michael Hammer (5304); ietf@ietf.org
> Subject: Let's talk (was: DMARC: perspectives from a listadmin of large o=
pen-
> source lists)
>=20
> Hi Mike,
> At 13:30 15-04-2014, MH Michael Hammer (5304) wrote:
> >My experience with regard to working groups is that it is
> >(technically) easy to participate and does not necessarily involve any
> >particular costs. I don't go to IETF meetings but have participated in
> >WG sessions during IETF meetings through jabber. Not the optimal
> >solution but it works. I think that the notion of 8000lb gorillas
> >somewhat misrepresents the situation. Some of the active participants
> >in the working groups I've been involved with continue their
> >involvement even when they change employers. With that in mind, I
> >believe that in many cases it truly is the individual and not the
> >individual as mouthpiece for the organization. I also believe that the
> >8000lb gorillas have many of the same interests as smaller
> >organizations and individuals even though there are times where
> >interests may diverge. It's also clear to me that there is not
> >uniformity of interests across constituencies within large
> >organizations. It's complex. So let's talk.
>=20
> It is, as you mentioned, complex.  I'll be one-sided in this comment.  Th=
ere is
> a cost to participation on the mailing lists and to attend meetings.  The=
re is a
> higher burden for a small company or an individual.  People from small
> companies sometimes get ignored or it is like the minority view (see Dave
> Cridland's message at http://www.ietf.org/mail-
> archive/web/ietf/current/msg87389.html ).
>=20

I think this conflates two different issues:

1) Cost to participation. While I may work for a larger organization, much =
if not most of my participation is in addition to my other work obligations=
. I know of other folks in a similar situation. I participated before I wor=
ked at a large organization, I participated when I had my own small busines=
s and I may choose to participate in the future if my circumstances change.=
 There are other people whose occupation consists solely of standards work.=
 I don't have any meaningful answer to your comment. Quite frankly, I'm ask=
ing myself why I should personally continue to engage with the IETF process=
 at all. It's not as if my employer is demanding it. Do I really want to be=
 engaging with IETF after a 16 hour day working on other stuff? It must be =
masochism.

2) Getting ignored or minority view. I don't believe it is simply a functio=
n of company size - at least for the WGs I've participated in. I'd assert t=
hat at least in the email/email auth WGs it's more a function of long term =
participants, many of whom have calcified positions (across the spectrum). =
I can think of at least one person from a relatively large company who gets=
 ignored a fair bit, so size is not necessarily a factor. I've been in the =
minority view on various issues in the WGs I've participated in. That's lif=
e - I chose Betamax. To a certain extent it's also a function of who is wra=
ngling the WG and how they manage the WG. I don't really think about whethe=
r a person is with a large company, a small company or an individual - I'm =
more interested in the quality and practicality of their ideas. I'm more of=
 a security and operations guy and that colors my perspective.

I'm not sure if you are looking for a response to Dave Cridland's message i=
n the context of DMARC specifically. As I noted when I first posted to this=
 group, I don't speak on behalf of DMARC and my comments are on a personal =
basis. When DMARC came along, as a sender I only had to publish a p=3Drejec=
t policy. We (my employer) had done the heavy lifting in terms of changing =
our mailing practices back in 2007 before there was a dmarc.org or a spec. =
I had some concerns about a wide open WG but wasn't necessarily against it.=
 My concerns were more along the line of how much of a grind it might be on=
 a personal basis (after my experiences with other WGs). I do recognize tha=
t others made a significant investment in implementing running code to make=
 things work. I think a lot of people underestimate what was involved and o=
verly discount concerns about radical modifications to the spec. When I did=
 my original effort in 2007 it was a five month project involving quite a f=
ew people to change how our websites handled mail to accommodate strong aut=
hentication for SPF and DKIM. I'll also point out that the interoperability=
 event for DKIM didn't take place until 2008 which meant I was somewhat goi=
ng out on a limb. I'm sure that for others to do their DMARC implementation=
s on the mailbox provider side several years later it was a larger effort t=
han what I went through. My personal belief is that nobody was looking to g=
et an IETF rubber stamp. Perhaps the concerns might have been communicated =
differently and perhaps there might have been a little less skepticism as t=
o intent.

So on to the mail list issue. On one level I want to say not my issue. I do=
n't publish p=3Dreject for any domains with users that send to mail lists s=
o as I've said, my ox isn't getting gored. There were plenty of discussions=
 in the DKIM working group about 1st party signatures vs 3rd party signatur=
es and trust and reputation and who should do what and who wouldn't do what=
. At the end of the day the can was kicked down the road. So here we are. I=
 don't have any answers for this group. I've already stated in a previous p=
ost how I think it will play out. I'm leaning towards just walking away and=
 spending cycles on something as that is more productive from my perspectiv=
e. The juice just isn't worth the squeeze.

> I can understand that an individual is not the mouthpiece of the organiza=
tion
> if that individual sometimes speaks up to say that management is saying X
> but he or she does not think that it is a great idea.  You have tried to =
be
> positive by discussing about this publicly, politely and without resortin=
g to
> marketing language.  Let's see who else would like to talk.
>=20

I don't think you are likely to see someone speaking up in that particular =
way. "My boss has bad ideas" posted to a public forum is not a career enhan=
cing move even if phrased politely. Those sorts of issues would likely get =
resolved internally or the person would likely choose to move to another ro=
ost if it is a significant issue. That's just common sense. At least for me=
, in the WGs I've participated in, I've had a lot of latitude because the i=
ssues are technical and it is more me keeping management apprised of what i=
s happening and what I'm doing than me getting directives. I can't speak fo=
r others or other organizations. I don't have anything to sell or market so=
 I have no reason to use marketing language. My goal is to protect end user=
s from maliciousness that tries to leverage our domains and brands - things=
 like SPF, DKIM and DMARC help do that in conjunction with other efforts su=
ch as takedowns, blocking, prosecutions, etc. I also get involved in other =
anti-abuse efforts that have nothing to do with my employer - because I bel=
ieve it is the right thing to do. Standards are just one piece of the puzzl=
e.

It's been a long day and I've rambled on more than enough.

Mike


From nobody Tue Apr 15 21:20:29 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65AD21A0049 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 21:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 Rh9Xv5ygSXUd for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 21:20:23 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 89DB01A006B for <ietf@ietf.org>; Tue, 15 Apr 2014 21:20:23 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 02E07CC0A1 for <ietf@ietf.org>; Wed, 16 Apr 2014 00:20:18 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id lHdXK2RQZ8RG for <ietf@ietf.org>; Wed, 16 Apr 2014 00:20:09 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 0750ECC09F for <ietf@ietf.org>; Wed, 16 Apr 2014 00:20:08 -0400 (EDT)
Message-ID: <534E04F8.805@meetinghouse.net>
Date: Wed, 16 Apr 2014 00:20:08 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org list" <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net> <534DB093.5020507@qti.qualcomm.com> <763CF376-1776-489A-A97E-FB65E77214BF@me.com>
In-Reply-To: <763CF376-1776-489A-A97E-FB65E77214BF@me.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LiCG_m3N8S1VxWz0_6mwUdBpus8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 04:20:27 -0000

Sabahattin Gucukoglu wrote:
> On 15 Apr 2014, at 23:20, Pete Resnick <presnick@qti.qualcomm.com> wrote:
> That suffers the same problems as X-O-A-R: you have to know when to trust the intermediate.  In the absence of that knowledge, any message transformation is invisible to the recipient, and potentially malicious.  You would have to invent a scheme for identifying transformations, so users could verify them against the original sender's signature.
>
> DMARC has put *ALL* the trust into the From: field.  That is very unfortunate, but it seems to be the DMARC peoples' idea of a foolproof, user-visible identifier.
>

First off, with xoar, you don't have to trust the intermediary.  If one 
removes DMARC's alignment mechanism - you can validate that a message 
originated from a yahoo address by dint of the crypto signature - as 
long as you don't modify any of the fields that get signed.  Now if you 
want to allow modification of the subject field (e.g., adding a tag) 
and/or the body (e.g., adding header and footer) - then you might have 
to be a little cleverer, perhaps by providing information about the 
diffs in extra headers and doing a few comparisons at the receiving end 
(subject tag = *****<original-signed-subject>).

It's worth noting that way back in 1999, the folks who designed HTTP 1.1 
designed an authentication scheme that works through proxies. They took 
the time to actually acknowledge mechanisms that were in use (i.e., 
caching proxies) and design mechanisms that could work in concert with 
them (and yes, in some cases the proxies have to do new things).  Those 
involved in DMARC, seemingly, did not take the same care to respect the 
infrastructure.

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Tue Apr 15 21:56:52 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF81C1A0027 for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 21:56:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 RcFYH6T8UOyi for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 21:56:46 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 418C41A0021 for <ietf@ietf.org>; Tue, 15 Apr 2014 21:56:46 -0700 (PDT)
Received: (qmail 48251 invoked from network); 16 Apr 2014 04:56:42 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=bc7a.534e0d8a.k1404; bh=5/OHzN3eEQSI9I6RicxbuV5cff8g6b1p6vOsmKZtYtY=; b=NErPYK66evKjeNbWlVFy+B/+55OsK5bHU9L3C700+F3F3nO7ZNYrkdGCn0j4MIHnk3dfWlEGzG0hqnRJcp9ia/jRly/Sqr0CS4XOmgjd1hEzNpVTbgI0ma0XV2fzYaQ8jpc9ipVAs7hEIXBj5/WFuXWngpH7V5pJl8Im2RjpXpNHBOXBraEc/8pkuESUHboOCdhDE8c7SK8LYytOrFxRAaC3H/yNWRmYqhwFqrZj69/HP7RICXfiiJJrBAc35rAG
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 16 Apr 2014 04:56:42 -0000
Date: 16 Apr 2014 00:56:42 -0400
Message-ID: <alpine.BSF.2.00.1404160054290.40095@joyce.lan>
From: "John R. Levine" <johnl@iecc.com>
To: "IETF general list" <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-39995716-1397624202=:40095"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/n_BqzRjk662bIQgeGNps4OLlgcs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 04:56:51 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-39995716-1397624202=:40095
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

>want to allow modification of the subject field (e.g., adding a tag)
>and/or the body (e.g., adding header and footer) - then you might have
>to be a little cleverer, perhaps by providing information about the
>diffs in extra headers and doing a few comparisons at the receiving end
>(subject tag = *****<original-signed-subject>).

That's unlikely to be a productive direction to go.  We had a lot of 
arguments about message modification when we were designing the DKIM 
strict and loose message digests.  We never found a way to allow subject 
tags that wouldn't also enable all sorts of abuse, and I don't think we 
missed anything.

The reasonable way to use DKIM with mailing lists has always been for
the list to add its own signature, and to use the list signatures to
develop a (presumably good) reputation for the list so its mail gets
delivered.  See the signatures on the messages from this list for an
example.

R's,
John
--3825401791-39995716-1397624202=:40095
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIIJBgYJKoZIhvcNAQcCoIII9zCCCPMCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBjcwggYzMIIFG6ADAgECAgMHCsYwDQYJKoZIhvcNAQEFBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xMzA3MTQwMzI4MjRaFw0xNDA3MTUwMTMzNDlaMFMxGTAX
BgNVBA0TEFBXY1lTWGN0Z0pVMTlaWTkxFzAVBgNVBAMMDmpvaG5sQGllY2Mu
Y29tMR0wGwYJKoZIhvcNAQkBFg5qb2hubEBpZWNjLmNvbTCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBALu27esh7DFfXV+FqyWcPE3tUV+mvwqW
C3VQk/LONISr7XbTjUIwiRpfia5MqcVY93a2MMAnEVqA7Tkt7pQ6AjVi5w6K
fq5VlDN93bntAGjlfS7un5qiNPUKq6oCJ4BMikLbhMcX3Te/rob//SlOZ/jW
DLd6yatuoAA4EYZ8yYClD50/XzKfPrDhQ3l8rOkkqJiY+il0xnkI3OcBKEys
5QaNgAuhY2svn/7uVhC/yRj79iieLQ2pYLUlcqdwbkkHxVlP6sCg/pHfv76A
nCFylpwpkcND0z9Fzv/4vdcVaopj4F/xa171sE3DHzxOiKYfPX+1XJMjideZ
HsowUy1Du8kCAwEAAaOCAtQwggLQMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSw
MB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDAdBgNVHQ4EFgQU065z
ZQKhcJYDiNkhDu6ej3TxRwgwHwYDVR0jBBgwFoAUU3Ltkpzg2ssBXHx+ljVO
8tS4UYIwGQYDVR0RBBIwEIEOam9obmxAaWVjYy5jb20wggFMBgNVHSAEggFD
MIIBPzCCATsGCysGAQQBgbU3AQIDMIIBKjAuBggrBgEFBQcCARYiaHR0cDov
L3d3dy5zdGFydHNzbC5jb20vcG9saWN5LnBkZjCB9wYIKwYBBQUHAgIwgeow
JxYgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkwAwIBARqBvlRo
aXMgY2VydGlmaWNhdGUgd2FzIGlzc3VlZCBhY2NvcmRpbmcgdG8gdGhlIENs
YXNzIDEgVmFsaWRhdGlvbiByZXF1aXJlbWVudHMgb2YgdGhlIFN0YXJ0Q29t
IENBIHBvbGljeSwgcmVsaWFuY2Ugb25seSBmb3IgdGhlIGludGVuZGVkIHB1
cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0aGUgcmVseWluZyBwYXJ0eSBvYmxp
Z2F0aW9ucy4wNgYDVR0fBC8wLTAroCmgJ4YlaHR0cDovL2NybC5zdGFydHNz
bC5jb20vY3J0dTEtY3JsLmNybDCBjgYIKwYBBQUHAQEEgYEwfzA5BggrBgEF
BQcwAYYtaHR0cDovL29jc3Auc3RhcnRzc2wuY29tL3N1Yi9jbGFzczEvY2xp
ZW50L2NhMEIGCCsGAQUFBzAChjZodHRwOi8vYWlhLnN0YXJ0c3NsLmNvbS9j
ZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5jYS5jcnQwIwYDVR0SBBwwGoYYaHR0
cDovL3d3dy5zdGFydHNzbC5jb20vMA0GCSqGSIb3DQEBBQUAA4IBAQAhGl57
1CTIxVCGhIyCPd/NouWlaMB4BATsPRCJZSyvx+wT/mRFdz3SeGjMocefbm+B
KyGEZD/VNJEDNrxqtwpKa1vhmTJBkhbiUjM+sCMuRBuCxRZkdEOWygY5gSQr
FC5oqx2ZxvzQhY7xjge0G36dEEp2yerEzGn87UqHia8r5ba+3j5GifKbqcEP
kGDvEe6pwnkIY5NT/Ukf0WuQ8rHuD5hXcKa5GoAep0+STcyZHjt0YEzFobRp
gPAIHaru48qCY8GwhWK/PKrBjjoPo8v4WfZuxJEKkRkPs305bolWP0AET7MU
6iTK0Aljt2b9FksEkYvWxTdI3xAu24PjF4oeMYIClzCCApMCAQEwgZQwgYwx
CzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQL
EyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQD
Ey9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVu
dCBDQQIDBwrGMAkGBSsOAwIaBQCggdgwGAYJKoZIhvcNAQkDMQsGCSqGSIb3
DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQwNDE2MDQ1NjQyWjAjBgkqhkiG9w0B
CQQxFgQUSSyFbrvm6RLeVJm/WLx0AHV4WYsweQYJKoZIhvcNAQkPMWwwajAL
BglghkgBZQMEASowCwYJYIZIAWUDBAEWMAsGCWCGSAFlAwQBAjAKBggqhkiG
9w0DBzAOBggqhkiG9w0DAgICAIAwDQYIKoZIhvcNAwICAUAwBwYFKw4DAgcw
DQYIKoZIhvcNAwICASgwDQYJKoZIhvcNAQEBBQAEggEAE5RbPuuJwQN5Srag
l1xRcuK7OmFV1zkZ50pnY+8WP/RMutyXdRiLj6SmTBq6uVbfVb92aD180a1z
vcaGaDCc1f+VB83SVwcSxooXF9LZ27k2ZdaesIAy0oTr4Bc8fVXvPgx07itr
rt1wAuhnOl0pJgPHwQiE4pxCim4rkLkMrpOJAygApbWleGfJoLrReabIsmLP
xqXJ7uAzM9bXYaVo1shWcO6j9ZBiKPhT3wq5fXrQ2868IeIy4CLEZYSjxxIq
nizWfVlE7cp763RBI+DmkfhW2lXrcq9w+mlfBrKddOTHJoA/dIpeHr1XpNA9
GkCT0TM7UDNe5kRbNnPEMEgozw==

--3825401791-39995716-1397624202=:40095--


From nobody Tue Apr 15 23:59:01 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A94371A006B for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 23:58:58 -0700 (PDT)
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_PASS=-0.001, URIBL_DBL_REDIR=0.001] autolearn=ham
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 Lu11xtuRJ3jx for <ietf@ietfa.amsl.com>; Tue, 15 Apr 2014 23:58:56 -0700 (PDT)
Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtpout001.mac.com [17.172.220.236]) by ietfa.amsl.com (Postfix) with ESMTP id 581B61A0064 for <ietf@ietf.org>; Tue, 15 Apr 2014 23:58:55 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N4400JPE3DXCL60@st11p02mm-asmtp001.mac.com> for ietf@ietf.org; Wed, 16 Apr 2014 06:58:47 +0000 (GMT)
Subject: Re: What I've been wondering about the DMARC problem
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <534D98CC.9080400@gmail.com>
Date: Wed, 16 Apr 2014 07:58:44 +0100
Content-transfer-encoding: quoted-printable
Message-id: <2478F2D1-2E08-45D7-86A2-36443959E272@me.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaGxEKTEMXGx0EGx0YBBIZBBsdEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsYGmJCH2lpHx9JGXhzB xltGhwfEkYZEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGx0QGx4aHxsRCl5ZF2FNEh1 pEQpMRhdia2sRCkNaFxgbGQQbGBkEGxMYBBkaEQpEWBcZEQpESRcYEQpCRRdmUH1dH21kGgVIY xEKQk4XbHBgeUAdYlJpGmIRCkJMF2dJH215aRh+ckJNEQpCbBdlaGUYbU0cGENGThEKQkAXZxx nXkJkY1Ibc2QRCnBoF2EacnpnbnJaTlpSEQpwaBdteGhLTH5TR194BREKcGgXZUtQa2BmeEdJX U4RCnBoF24SQWhvfVMTbnltEQpwaBdpfWEBHxJncgUdchEKcH8XelNve2JleFNpfmIRCnBfF2Q fY1hMf21CG10eEQpwbBdrZk5rQWVfZlNnAREKcEwXZxpTbEBrQG0fQ1oR
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-15_04:2014-04-15,2014-04-15,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404160063
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OoIJk9OPnJeK4Lz0I7KBkxtFg60
Cc: dcrocker@bbiw.net, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 06:58:59 -0000

On 15 Apr 2014, at 21:38, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
> The mailman fix is worse than the disease. I think the .INVALID fix is
> much better, because Reply-all will still work.

Reply-all should still work with the Mailman fix; reply-to contains =
member (or member and list, for the reply-to-list case) and To/CC are =
included by MUA as usual.  It's "Reply" that's broken, and in the =
reply-to-list case: if the sender's address is discarded then the =
recipient can't use it, and if it's included then the sender has to =
manually manipulate the recipients in the composer window just to reply =
to the sender only after hitting Reply.

I really have little issue with the Mailman fix as it currently stands.  =
It's borked, but it works.  My lists are mostly of the chatty =
reply-to-list variety anyway.  The display name isn't touched; lots of =
users won't even notice =85

Apparently Mailman 3 will do this properly, implementing support for =
DMARC by rejection and not tampering. http://j.mp/1m6N5Jt
Perhaps someone should point them to this discussion, or advise on the =
rewrite-to-invalid hack (which BTW has shortcomings of its own, =
especially for users of touchscreen devices =85).

Cheers,
Sabahattin


From nobody Wed Apr 16 03:13:23 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2FF1A00ED for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 03:13:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 qCZdYFgg8THs for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 03:13:19 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 79F3E1A004C for <ietf@ietf.org>; Wed, 16 Apr 2014 03:13:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id CF4ADBE58; Wed, 16 Apr 2014 11:13:15 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tzohn4IL4JVQ; Wed, 16 Apr 2014 11:13:15 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 9FEF2BE55; Wed, 16 Apr 2014 11:13:15 +0100 (IST)
Message-ID: <534E57BC.1060501@cs.tcd.ie>
Date: Wed, 16 Apr 2014 11:13:16 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>, Theodore Ts'o <tytso@mit.edu>
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca>
In-Reply-To: <24986.1397615002@sandelman.ca>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Pr_sCRjl39tjw2PGmVGQg00TDJc
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 10:13:21 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



On 04/16/2014 03:23 AM, Michael Richardson wrote:

> 
> So, as a WG chair, a person known to me just tried to post to the
> list From a brand new yahoo.com mail account.  They aren't
> subscribed with that address.  I would normally just approve, and
> add them...
> 
> It seems to me that I must now actually reject, because it would
> affect other subscribers.
> 
> I'm now thinking that we need to remove all the @yahoo.com
> addresses from posting to ietf mailing lists.
> 

This is probably obvious, but had gmail.com done what yahoo.com
has done, that could I guess have a pretty significant impact on
the IETF getting stuff done for a while since a lot of folks in
the last few years seem to have migrated their IETF mail to
gmail.com as a reasonable way to get around corporate this-and-that
issues.

Maybe people who've done that might want to consider whether its
such a good plan for so many IETF participants to be dependent on
just one service now that we have a demonstration that s/none/reject/
in one TXT RR can have such an impact.

S.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQEcBAEBAgAGBQJTTle3AAoJEC88hzaAX42i7jQIALBIZ3Z+jp1RbGCiJp4IVztN
qWa0aEUcx2Skp4gtM/vQnEEsCjYFAnRaoMofJqyUBuvTs3H0q/GMkcONcOPJW6wH
R/HpKKr24UpYsfpdYKx99b7D27kVNgzML3e0bD3csR1MNC/yR7wvsnTHTwbv2mxk
eb7O5Wp6kvKw/gRYjPHncMPSgBUyc+KixY6IDHzDk4IdCQP4CyVkhI4EV7dlu8nM
T1RNhljdzCmJBLd0y1USS1UmKrPVhoFgBXShvnxabseqJN/m2bz5WVSuJgIwWRov
duU5vRgbdQ5jTn9TBzEPdJ5LRbQczlHyLVdnjvOHApQ8HtNrQxKOe89C0b32+7A=
=cS/m
-----END PGP SIGNATURE-----


From nobody Wed Apr 16 04:07:28 2014
Return-Path: <hector.santos45@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F09A1A0139 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 04:07:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.771
X-Spam-Level: 
X-Spam-Status: No, score=-1.771 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO_END_DIGIT=0.25, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 UuXCJcL1OTxX for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 04:07:22 -0700 (PDT)
Received: from nm22-vm1.bullet.mail.bf1.yahoo.com (nm22-vm1.bullet.mail.bf1.yahoo.com [98.139.212.127]) by ietfa.amsl.com (Postfix) with ESMTP id 876071A012C for <ietf@ietf.org>; Wed, 16 Apr 2014 04:07:22 -0700 (PDT)
Received: from [98.139.215.143] by nm22.bullet.mail.bf1.yahoo.com with NNFMP;  16 Apr 2014 11:07:19 -0000
Received: from [98.139.212.251] by tm14.bullet.mail.bf1.yahoo.com with NNFMP;  16 Apr 2014 11:07:19 -0000
Received: from [127.0.0.1] by omp1060.mail.bf1.yahoo.com with NNFMP; 16 Apr 2014 11:07:19 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 113851.91087.bm@omp1060.mail.bf1.yahoo.com
Received: (qmail 27707 invoked by uid 60001); 16 Apr 2014 11:07:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1397646438; bh=auR14E+MAxsuIgWAZu57scRhq5K0twT2Um4j2/Ws18s=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=IaisrWUBB0NHPmZfgRVafvnefZ78it5OrPaZaLlnWZuCd9oSpdv5+o728t32AnytK0DejGPi8+rmZID8oPL5b2k8UzHYiTP9oQIvGVBGkbRXtsjdwpV865ONFj8qdN64EKiU5UguzWGiIC7pFq+y7GAk99LK2vcKRAG7v+BuCec=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=tDz8VlMnH5oKd0OwzpTogMjb+OUNZtt87nhNEKyUzSBIuzBbAW7QW9PNZDJyBIhtVqClQq33WaZKg8se11/ViIKi5x3LXyAr4B0De4o75gDUqmNFd9dBgHXKJngOApssIYIWf4cQrkCjZUFp62Amd9Rr8ZcIpKqSz5I7oNmw0w4=;
X-YMail-OSG: OdBi1WoVM1kGEIjj4MOfW87jn2Sy5AGlO1MF3Fofeh6SZld .wFJ94OzO5UCexw9ljyna9dTKvkZBLJmXrmD1EWlUM9QclXlETpkPz3FJoY2 HOMgXWoszqQp4ffZy8VIrESp77Z9.IfalTggyuNCFQQjApXfEs3_Ygr6C7Xw 5.bs0gNFZJRDZl.C3VoEaVkIUJOrwhA5PVBHbYpeFWf6MxJuemEttFMrflca ZKv7fTH76cKvKrbYrmEMMlHueFGAkjbqgt0RrhR1t05fSFxDjcPa69K_0uif hX.7vbztaiVjsW_lNLAGd7QfFZ7K94bVFXMTlm.RQxKX9HbABwCSO_6cIpV7 Q7k8wwh8bc4.tXjp.JIKmM8Vei6I.ZaDWZri4pNNyaH1k64p_oANHiCZ5KNQ lLpA8vK61IURRlezegSN_Xx_xnOC6G6aWT_aAnTlQU..KXVx1f49GpTuIFSO CcyYii39.WRuic1.x4_QrEg8CNEcMxfDxhNRshJpmi7IGEmXQ.3W.6VjR9Hf SQQfdWZIhJ7iWD1o4AD6BNnUiqQngxP4DTafIDHPaWt6je4HF_DM29RIIpU9 L4ZdbOgPOgWRM10GiEvshsN21CKr1Hw--
Received: from [99.121.4.27] by web160803.mail.bf1.yahoo.com via HTTP; Wed, 16 Apr 2014 04:07:18 PDT
X-Rocket-MIMEInfo: 002.001, VGhpcyBpcyBtb3N0bHkgYSB0ZXN0IHdpdGggbXkganVuayB5YWhvby5jb20gdGVzdGluZyBhY2NvdW50IHRvIHNlZSB3aGF0IGhhcHBlbnMgaGVyZS4gwqDCoAoKU3RlcGhlbiwgeW91IGFyZSByaWdodCwgYnV0IHdlIGhhdmUgYmVlbiBvbiB0aGlzIGZvciBvdmVyIDkgeWVhcnMuIMKgV2l0aCBhbGwgZHVlIHJlc3BlY3QgdG8gQ3JvY2tlciBhbmQgTGV2aW5lLCB3aG8gZm91Z2h0IMKgaGFyZCBhZ2FpbnN0IERLSU0gU2VjdXJpdHkgUG9saWN5IGJhc2VkIHNvbHV0aW9ucyBzdGFydGluZyB3aXRoIFNTUCwgdGgBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.185.657
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <534E57BC.1060501@cs.tcd.ie>
Message-ID: <1397646438.42236.YahooMailNeo@web160803.mail.bf1.yahoo.com>
Date: Wed, 16 Apr 2014 04:07:18 -0700 (PDT)
From: Hector Santos <hector.santos45@yahoo.com>
Subject: Re: DMARC and yahoo
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, Michael Richardson <mcr+ietf@sandelman.ca>, Theodore Ts'o <tytso@mit.edu>
In-Reply-To: <534E57BC.1060501@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1625196408-161270130-1397646438=:42236"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/e0Qe0eVrOhYJMNiC3A7DL_Si0jU
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Hector Santos <hector.santos45@yahoo.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 11:07:26 -0000

--1625196408-161270130-1397646438=:42236
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

This is mostly a test with my junk yahoo.com testing account to see what ha=
ppens here. =A0=A0=0A=0AStephen, you are right, but we have been on this fo=
r over 9 years. =A0With all due respect to Crocker and Levine, who fought =
=A0hard against DKIM Security Policy based solutions starting with SSP, the=
n ADSP which Levine authored as a poison pill many believe, he never suppor=
ted his own work. The industry was quite aware of what was coming and it to=
ok DMARC, an external development, which Eric Allman predicted would happen=
 when SSP was demoted by ADSP, to highlight the very high interest in the t=
echnology and tremendous need for an self-signing, low cost, email authenti=
cation protocol. DKIM was it and without a policy that Crocker and Levine t=
ried to remove, the payoff was low and signatures were worthless. =A0 So we=
 have to give some credit to Yahoo for pushing the issue, finally. =A0 Some=
 will continue to fight it and =A0some will continue to work with it. =A0 I=
 choose to work with it now as I did with ADSP.=0A=0A--=0AHLS via Yahoo=0AO=
n Wednesday, April 16, 2014 6:13 AM, Stephen Farrell <stephen.farrell@cs.tc=
d.ie> wrote:=0A =0A-----BEGIN PGP SIGNED MESSAGE-----=0AHash: SHA1=0A=0A=0A=
=0AOn 04/16/2014 03:23 AM, Michael Richardson wrote:=0A=0A> =0A> So, as a W=
G chair, a person known to me just tried to post to the=0A> list From a bra=
nd new yahoo.com mail account.=A0 They aren't=0A> subscribed with that addr=
ess.=A0 I would normally just approve, and=0A> add them...=0A> =0A> It seem=
s to me that I must now actually reject, because it would=0A> affect other =
subscribers.=0A> =0A> I'm now thinking that we need to remove all the @yaho=
o.com=0A> addresses from posting to ietf mailing lists.=0A> =0A=0AThis is p=
robably obvious, but had gmail.com done what yahoo.com=0Ahas done, that cou=
ld I guess have a pretty significant impact on=0Athe IETF getting stuff don=
e for a while since a lot of folks in=0Athe last few years seem to have mig=
rated their IETF mail to=0Agmail.com as a reasonable way to get around corp=
orate this-and-that=0Aissues.=0A=0AMaybe people who've done that might want=
 to consider whether its=0Asuch a good plan for so many IETF participants t=
o be dependent on=0Ajust one service now that we have a demonstration that =
s/none/reject/=0Ain one TXT RR can have such an impact.=0A=0AS.=0A=0A=0A---=
--BEGIN PGP SIGNATURE-----=0AVersion: GnuPG v1.4.14 (GNU/Linux)=0A=0AiQEcBA=
EBAgAGBQJTTle3AAoJEC88hzaAX42i7jQIALBIZ3Z+jp1RbGCiJp4IVztN=0AqWa0aEUcx2Skp4=
gtM/vQnEEsCjYFAnRaoMofJqyUBuvTs3H0q/GMkcONcOPJW6wH=0AR/HpKKr24UpYsfpdYKx99b=
7D27kVNgzML3e0bD3csR1MNC/yR7wvsnTHTwbv2mxk=0Aeb7O5Wp6kvKw/gRYjPHncMPSgBUyc+=
KixY6IDHzDk4IdCQP4CyVkhI4EV7dlu8nM=0AT1RNhljdzCmJBLd0y1USS1UmKrPVhoFgBXShvn=
xabseqJN/m2bz5WVSuJgIwWRov=0AduU5vRgbdQ5jTn9TBzEPdJ5LRbQczlHyLVdnjvOHApQ8Ht=
NrQxKOe89C0b32+7A=3D=0A=3DcS/m=0A-----END PGP SIGNATURE-----
--1625196408-161270130-1397646438=:42236
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<html><body><div style=3D"color:#000; background-color:#fff; font-family:He=
lveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;fo=
nt-size:12pt"><div><span>This is mostly a test with my junk yahoo.com testi=
ng account to see what happens here. &nbsp;&nbsp;</span></div><div style=3D=
"color: rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue, 'Helveti=
ca Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: =
transparent; font-style: normal;"><span><br></span></div><div style=3D"colo=
r: rgb(0, 0, 0); font-size: 16px; font-family: HelveticaNeue, 'Helvetica Ne=
ue', Helvetica, Arial, 'Lucida Grande', sans-serif; background-color: trans=
parent; font-style: normal;"><span>Stephen, you are right, but we have been=
 on this for over 9 years. &nbsp;With all due respect to Crocker and Levine=
, who fought &nbsp;hard against DKIM Security Policy based solutions starti=
ng with SSP, then ADSP which Levine authored as a poison pill many
 believe, he never supported his own work. The industry was quite aware of =
what was coming and it took DMARC, an external development, which Eric Allm=
an predicted would happen when SSP was demoted by ADSP, to highlight the ve=
ry high interest in the technology and tremendous need for an self-signing,=
 low cost, email authentication protocol. DKIM was it and without a policy =
that Crocker and Levine tried to remove, the payoff was low and signatures =
were worthless. &nbsp; So we have to give some credit to Yahoo for pushing =
the issue, finally. &nbsp; Some will continue to fight it and &nbsp;some wi=
ll continue to work with it. &nbsp; I choose to work with it now as I did w=
ith ADSP.</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; f=
ont-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Gran=
de', sans-serif; background-color: transparent; font-style: normal;"><span>=
<br></span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px;
 font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Gr=
ande', sans-serif; background-color: transparent; font-style: normal;"><spa=
n>--</span></div><div style=3D"color: rgb(0, 0, 0); font-size: 16px; font-f=
amily: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', =
sans-serif; background-color: transparent; font-style: normal;">HLS via Yah=
oo</div><div class=3D"yahoo_quoted" style=3D"display: block;"> <div style=
=3D"font-family: HelveticaNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida=
 Grande', sans-serif; font-size: 12pt;"> <div style=3D"font-family: Helveti=
caNeue, 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; fo=
nt-size: 12pt;"> <div dir=3D"ltr"> <font size=3D"2" face=3D"Arial"> On Wedn=
esday, April 16, 2014 6:13 AM, Stephen Farrell &lt;stephen.farrell@cs.tcd.i=
e&gt; wrote:<br> </font> </div>  <div class=3D"y_msg_container">-----BEGIN =
PGP SIGNED MESSAGE-----<br>Hash: SHA1<br><br><br><br>On 04/16/2014 03:23 AM=
, Michael
 Richardson wrote:<br><br>&gt; <br>&gt; So, as a WG chair, a person known t=
o me just tried to post to the<br>&gt; list From a brand new yahoo.com mail=
 account.&nbsp; They aren't<br>&gt; subscribed with that address.&nbsp; I w=
ould normally just approve, and<br>&gt; add them...<br>&gt; <br>&gt; It see=
ms to me that I must now actually reject, because it would<br>&gt; affect o=
ther subscribers.<br>&gt; <br>&gt; I'm now thinking that we need to remove =
all the @yahoo.com<br>&gt; addresses from posting to ietf mailing lists.<br=
>&gt; <br><br>This is probably obvious, but had gmail.com done what yahoo.c=
om<br>has done, that could I guess have a pretty significant impact on<br>t=
he IETF getting stuff done for a while since a lot of folks in<br>the last =
few years seem to have migrated their IETF mail to<br>gmail.com as a reason=
able way to get around corporate this-and-that<br>issues.<br><br>Maybe peop=
le who've done that might want to consider whether its<br>such a
 good plan for so many IETF participants to be dependent on<br>just one ser=
vice now that we have a demonstration that s/none/reject/<br>in one TXT RR =
can have such an impact.<br><br>S.<br><br><br>-----BEGIN PGP SIGNATURE-----=
<br>Version: GnuPG v1.4.14 (GNU/Linux)<br><br>iQEcBAEBAgAGBQJTTle3AAoJEC88h=
zaAX42i7jQIALBIZ3Z+jp1RbGCiJp4IVztN<br>qWa0aEUcx2Skp4gtM/vQnEEsCjYFAnRaoMof=
JqyUBuvTs3H0q/GMkcONcOPJW6wH<br>R/HpKKr24UpYsfpdYKx99b7D27kVNgzML3e0bD3csR1=
MNC/yR7wvsnTHTwbv2mxk<br>eb7O5Wp6kvKw/gRYjPHncMPSgBUyc+KixY6IDHzDk4IdCQP4Cy=
VkhI4EV7dlu8nM<br>T1RNhljdzCmJBLd0y1USS1UmKrPVhoFgBXShvnxabseqJN/m2bz5WVSuJ=
gIwWRov<br>duU5vRgbdQ5jTn9TBzEPdJ5LRbQczlHyLVdnjvOHApQ8HtNrQxKOe89C0b32+7A=
=3D<br>=3DcS/m<br>-----END PGP SIGNATURE-----<br><br><br><br></div>  </div>=
 </div>  </div> </div></body></html>
--1625196408-161270130-1397646438=:42236--


From nobody Wed Apr 16 04:34:36 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E9011A012A for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 04:34:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.373
X-Spam-Level: 
X-Spam-Status: No, score=-3.373 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 UFpDsn0K7jWA for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 04:34:32 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 9D86B1A010B for <ietf@ietf.org>; Wed, 16 Apr 2014 04:34:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397648069; x=1429184069; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=lTvNRpq2xBaT0FXRDg5c8r6Wj3Z64Xy0r3e4rUwLwRY=; b=u3S04RKnWXzeItUXfJMFbCKQWE4Qrr5YjCU7MppqM5kuxrAVgZXPbjVs Pc1EBUN0HQ3EHTbLHKmgOCwT6P+WyUQGUvvLNCwxhlZTiIpUYf/up4pbm 6pkoxM8XPDov4WM0W3fnw109kJ+n4fhuMlUztsU0PhMUrLeaB3azicGwL 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,7409"; a="29137261"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine01.qualcomm.com with ESMTP; 16 Apr 2014 04:34:29 -0700
X-IronPort-AV: E=Sophos;i="4.97,871,1389772800"; d="scan'208";a="29453084"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 16 Apr 2014 04:34:28 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 16 Apr 2014 04:34:34 -0700
Message-ID: <534E6AC1.7030709@qti.qualcomm.com>
Date: Wed, 16 Apr 2014 06:34:25 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net> <534DB093.5020507@qti.qualcomm.com> <534DBA0F.2050507@gmail.com> <20140415231720.GQ4456@thunk.org>
In-Reply-To: <20140415231720.GQ4456@thunk.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/T823fjs5PWq2BjvOZ-FzZ5YMjSA
Cc: John C Klensin <john-ietf@jck.com>, ietf@ietf.org, Dave Crocker <dcrocker@bbiw.net>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 11:34:34 -0000

On 4/15/14 6:14 PM, Sabahattin Gucukoglu wrote:

>> There should be a mechanism for an author to send a message to a mailing list, granting the mailing list permission to redistribute that message, and have that permission conveyed to the mailing list recipient such that when the mailing list recipient receives the message, they can assure themselves that the originating domain is OK with that redistribution. Sounds like some protocol which could be written.
>>      
> That suffers the same problems as X-O-A-R: you have to know when to trust the intermediate.  In the absence of that knowledge, any message transformation is invisible to the recipient, and potentially malicious.  You would have to invent a scheme for identifying transformations, so users could verify them against the original sender's signature.
>    

Not necessarily. If the originator of the message sends to a mailing 
list, the originator's site should trust the mailing list to 
redistribute the message and make any transformations. (If you can't 
trust your users to make a decision on which lists to send to, that's a 
different thing.) If the originator's site is going to allow that, you 
could create a mechanism where the originator's site gets some sort of 
cryptographic data from the mailing list site and include that in its 
signed message, such that when the eventual recipient gets the message, 
it can verify that it came from a mailing list site that the originator 
explicitly sent the mail to. That doesn't require the originator's or 
the recipient's site to independently trust the mailing list. (It would, 
of course, be perfectly OK for the recipient's site to check that it's 
getting the list mail from an authorized site; that's separate from of 
the above.)

And again, this is only if the originator indicates that it *wants* to 
allow its users to have their mail redistributed. The site is well 
within rights to indicate that it doesn't want that to happen, and a 
friendly mailing list would bounce the mail in that case.


On 4/15/14 6:17 PM, Theodore Ts'o wrote:
> On Wed, Apr 16, 2014 at 11:00:31AM +1200, Brian E Carpenter wrote:
>    
>>> (If the originating domain is expressly *not* OK with the
>>> redistribution, the mailing list should bounce the message back to the
>>> author saying as much.)
>>>        
>> Isn't that exactly what p=reject implies? If so, the logical behaviour
>> for all list software would be to check the DMARC record for the
>> originating domain of each message, and bounce it if p=reject.
>>      

Yep.

> The question is which is more or less unfriendly?
>
> 1)  Forbidding yahoo.com users from participating on mailing lists
>
> 2)  Rewriting the from field of yahoo.com users.
>    

More or less friendly to whom? If yahoo.com says that it doesn't want 
mail from its users sent via other servers, it might be unfriendly to 
its users to bounce the mail, but it's pretty darn friendly to 
yahoo.com. (Imagine the question: "So, you say you don't want things 
with your users' addresses sent from my server. Are you OK with me 
rewriting your users' addresses with '.invalid' on the end and then 
sending them?") And it's much friendlier to eventual recipients of this 
mail to bounce it (forcing the originator to send from a different 
address) than to get a piece of mail that will cause them to get a 
bounce if they reply to it without noticing that there's a ".invalid" at 
the end.

The problem is that the current protocol is not rich enough to express 
everyone's intentions. Yahoo conceivably might want to say, "It's OK to 
receive mail from a yahoo.com user from a site that is redistributing a 
piece of mail that a yahoo.com user explicitly sent to it." But there's 
no way to say that in the protocol now. Given that, yahoo.com has made 
the current choice to say, "Reject all yahoo.com mail that comes from a 
site other than yahoo.com". That's a choice yahoo.com is free to make. A 
friendly mailing list is well within spec to honor that request by not 
redistributing the mail.

> I could easily see the mailing list software making this be
> configurable, so it's up to each mailing list admin.  :-)
>    

I think that's a perfectly reasonable thing to do.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Wed Apr 16 04:52:03 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 949FB1A0148 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 04:52:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 v5EjBS1T6zFd for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 04:51:59 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id DFFF11A0112 for <ietf@ietf.org>; Wed, 16 Apr 2014 04:51:58 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WaONY-0005Os-Pu; Wed, 16 Apr 2014 11:51:49 +0000
Date: Wed, 16 Apr 2014 20:51:46 +0900
Message-ID: <m2ioq95w6l.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Subject: Re: DMARC and yahoo
In-Reply-To: <534E57BC.1060501@cs.tcd.ie>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <534E57BC.1060501@cs.tcd.ie>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/V_9Y-Wbl7hNUN7kmpFpCl--sjlM
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Theodore Ts'o <tytso@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 11:52:00 -0000

> Maybe people who've done that might want to consider whether its
> such a good plan for so many IETF participants to be dependent on
> just one service now that we have a demonstration that s/none/reject/
> in one TXT RR can have such an impact.

try smtp to goog over ipv6.  if you do not have an spf rr and good
reverse dns, high percentage of rejection.  the excuse is that ipv6
is mostly spam so they put up an aggressive barrier.

randy


From nobody Wed Apr 16 05:21:53 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C62391A0145 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 05:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 zmNnHiNdK7to for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 05:21:49 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 58CAB1A014E for <ietf@ietf.org>; Wed, 16 Apr 2014 05:21:47 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id DF89BCC0A8 for <ietf@ietf.org>; Wed, 16 Apr 2014 08:21:43 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EnesxEs5QxTR for <ietf@ietf.org>; Wed, 16 Apr 2014 08:21:35 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 0F17CCC0A5 for <ietf@ietf.org>; Wed, 16 Apr 2014 08:21:35 -0400 (EDT)
Message-ID: <534E75CE.5020602@meetinghouse.net>
Date: Wed, 16 Apr 2014 08:21:34 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: IETF general list <ietf@ietf.org>
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <alpine.BSF.2.00.1404160054290.40095@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1404160054290.40095@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_Tih0MKbOqSjY4giSFzEihSOsXs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 12:21:52 -0000

John R. Levine wrote:
>> want to allow modification of the subject field (e.g., adding a tag)
>> and/or the body (e.g., adding header and footer) - then you might have
>> to be a little cleverer, perhaps by providing information about the
>> diffs in extra headers and doing a few comparisons at the receiving end
>> (subject tag = *****<original-signed-subject>).
>
> That's unlikely to be a productive direction to go.  We had a lot of 
> arguments about message modification when we were designing the DKIM 
> strict and loose message digests.  We never found a way to allow 
> subject tags that wouldn't also enable all sorts of abuse, and I don't 
> think we missed anything.
>
> The reasonable way to use DKIM with mailing lists has always been for
> the list to add its own signature, and to use the list signatures to
> develop a (presumably good) reputation for the list so its mail gets
> delivered.  See the signatures on the messages from this list for an
> example.

I was thinking about combining:
- two signatures: at origination, by the list manager
- adding an additional header, along the lines of "original-subject"
- allowing for:
-- not breaking validation of the originating signature
-- adding tags to the subject line (and copying the original subject to 
original-subject)
-- adding a new signature at the mailing list
-- validating the original signature at receipt (just using the 
original-subject header in place of the tagged subject line)
-- doing a diff on the two subject lines to validate that the only thing 
added was a text tag before the original subject

Doesn't address the non-aligned From: header issue, but does reduce one 
impact.



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Wed Apr 16 05:47:32 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93C9C1A0156 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 05:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 PzTcRMgYTcNO for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 05:47:25 -0700 (PDT)
Received: from mail-wi0-x232.google.com (mail-wi0-x232.google.com [IPv6:2a00:1450:400c:c05::232]) by ietfa.amsl.com (Postfix) with ESMTP id 237EF1A0170 for <ietf@ietf.org>; Wed, 16 Apr 2014 05:47:10 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id bs8so1304409wib.11 for <ietf@ietf.org>; Wed, 16 Apr 2014 05:47:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=+nulO1lmWr2UDWm+JXB9JuoEveIrD1BRxujm6Go+xBc=; b=gdfRDJgE0lAKm9zD/ievzTCeQsPjTm0yd2TxrLsBMGd1EFB2zUQnP5XQxiTg9f/nMZ MBxIXL3tKbJNyjAO+ff1z1CDNnktO4pNfA4LodfavvOicKPtUFdhbp/qgTeoZz5BS9qp 4ufOY9LJkKw0JgAjisC8F8sWmkcMX6346ycfUqdZXCbj3+Akx9vlSMV8iDNQycFXbIlf CsU1Uvr25ZHhrs1DJ1XWvpKITV5glXBJS4vCY8XYO0KNHsZCoz1Cu/CzMju73pYY7EAx avItCpAyDvg+9CqBTxXErhlbwRFbu938t3GAkhONKMuKWfVqmtM2a9chvd+Ll7y1IWMv kV5Q==
X-Received: by 10.180.24.72 with SMTP id s8mr19257253wif.20.1397652426013; Wed, 16 Apr 2014 05:47:06 -0700 (PDT)
Received: from [172.24.248.99] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id lh6sm34219755wjb.27.2014.04.16.05.47.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 05:47:04 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC and yahoo
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <534E57BC.1060501@cs.tcd.ie>
Date: Wed, 16 Apr 2014 15:46:59 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A79E1B55-9390-4587-BFE5-9D7DE4C41D3D@gmail.com>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <534E57BC.1060501@cs.tcd.ie>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7V7Rcljl9MmPH7JraM1l_0qRvLg
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 12:47:30 -0000

On Apr 16, 2014, at 1:13 PM, Stephen Farrell <stephen.farrell@cs.tcd.ie> =
wrote:

>=20
> This is probably obvious, but had gmail.com done what yahoo.com
> has done, that could I guess have a pretty significant impact on
> the IETF getting stuff done for a while since a lot of folks in
> the last few years seem to have migrated their IETF mail to
> gmail.com as a reasonable way to get around corporate this-and-that
> issues.

I=92m one of those folks. It was mostly over spam filtering rejecting =
posts that it shouldn=92t, especially messages from the lists that =
seemed to be coming from my email address. And rejected messages lead to =
unsubscribing. I got fed up with re-enabling my subscription every week =
or so.=20

> Maybe people who've done that might want to consider whether its
> such a good plan for so many IETF participants to be dependent on
> just one service now that we have a demonstration that s/none/reject/
> in one TXT RR can have such an impact.

I considered this, so I first tried another provider (neither Yahoo! nor =
GMail). It turned out to be blocked from posting to @irtf.org mailing =
lists. I waited a week for this to sort itself out, but that didn=92t =
happen. So I thought I=92d complain/open a ticket/something. I searched =
their site and couldn=92t find a support email address. The =
troubleshooting flowchart ended with a phone number. I spent 20 minutes =
on hold and then 10 more with the firstest or first-line support (=93yes, =
I=92m sure I have an account.  Yes, I=92m logged in. Yes, I=92m sure the =
other SMTP server is up=94). He gave me the number for the second line =
of support. In the US. So I gave up, especially since their IMAP didn=92t =
work with my client.

It looks like there=92s a lot of providers out there, but there=92s not =
that many who work correctly.  So I ended up with a GMail account like =
many others.

Yoav


From nobody Wed Apr 16 05:58:38 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F8EC1A0156 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 05:58:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level: 
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 il40KdXt8I-y for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 05:58:28 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 8DD881A0178 for <ietf@ietf.org>; Wed, 16 Apr 2014 05:58:26 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id DF5AE2002C for <ietf@ietf.org>; Wed, 16 Apr 2014 08:58:40 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id DD22A63ABD; Wed, 16 Apr 2014 08:58:16 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id C91F763AA2 for <ietf@ietf.org>; Wed, 16 Apr 2014 08:58:16 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534E6AC1.7030709@qti.qualcomm.com>
References: <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net> <534DB093.5020507@qti.qualcomm.com> <534DBA0F.2050507@gmail.com> <20140415231720.GQ4456@thunk.org> <534E6AC1.7030709@qti.qualcomm.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 16 Apr 2014 08:58:16 -0400
Message-ID: <18443.1397653096@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EXmIOMYF6UYQZ3F8hG3iUNFlki8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 12:58:33 -0000

--=-=-=


It's clear to me that we need at least a non-WG mailing list for this
*technical* discussion.  Fixing the mailing list problem may require
fundamental changes in how things work; and I think that is okay.
Maybe we could try this NNTP thinkg I've heard about :-)

Pete Resnick <presnick@qti.qualcomm.com> wrote:
    > a decision on which lists to send to, that's a different thing.) If the
    > originator's site is going to allow that, you could create a mechanism
    > where
    > the originator's site gets some sort of cryptographic data from the
    > mailing list site and include that in its signed message, such that
    > when the eventual

so, what you are saying is that based upon the (SMTP) To: address, the sender
needs a signal that this is a mailing list, and some way to react.
Maybe this could be combined with various SMTP DANE mechanisms, or at least,
maybe "Additional RR" could return that kind of information.

I think that there are a whole bunch of architectually important things
here.  The signal has to come early enough to either modify the DKIM process,
or if the signal comes rather late (such as during SMTP delivery), then it
needs to be possible to redo the DKIM process.  I think that this will be
challenging for many large installations where there are multiple layers of
outgoing SMTP delivery machines, and DKIM is just a stage in the process.

But, I don't think it is impossible.
Consider all the other meta info that could be stored along with the "I am a
list" signal... things like how to subscribe, unsubscribe, location of
archive, etc.

Imagine if that signal also changed the protocol from SMTP to NNRP POST?

    > And again, this is only if the originator indicates that it *wants* to
    > allow its users to have their mail redistributed. The site is well
    > within rights to ndicate that it doesn't want that to happen, and a
    > friendly mailing list would bounce the mail in that case.

Running code.  we need someone to fund and participate in an experiment.
 (cf: other thread about not participating in SDOs anymore)


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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU05+aIqHRg3pndX9AQLNbgQAgtcWFujXKVfo9RW6rcMBmgaJoQ81fpxp
YlRuSL4ty9WQ5u2ET2NLmaDeICoFRtXVbNqm7bFJ1tkKHgl/rRhksyUSQyFkl2h0
yRqQ/ejJ+ucdrBEkKAWvA4S8+7ISaxdYPux3HWGhjJPEj3R91nGqQfKklVDfPODS
nLMpYb7Q2Xc=
=6RYv
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 16 06:32:04 2014
Return-Path: <ietf@thomasclausen.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D3191A0191 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 06:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 iPtzIAFDdMhP for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 06:32:02 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 26CA81A018F for <ietf@ietf.org>; Wed, 16 Apr 2014 06:32:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id 1D4DE1BCCDF9; Wed, 16 Apr 2014 06:31:59 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 7BD831BCCDEC; Wed, 16 Apr 2014 06:31:57 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Thomas Clausen <ietf@thomasclausen.org>
In-Reply-To: <534DC46C.60703@gmail.com>
Date: Wed, 16 Apr 2014 15:31:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com>
To: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Rkq2WoaQ2yp0OAQo9CBg9qrvSP8
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 13:32:03 -0000

On 16 Apr 2014, at 01:44, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:

>=20
> On 04/15/2014 06:03 PM, Carsten Bormann wrote:
>> On 16 Apr 2014, at 00:49, Spencer Dawkins =
<spencerdawkins.ietf@gmail.com> wrote:
>>=20
>>> The idea was that you could declare a specific Internet-Draft "good =
enough for now", for a variety of reasons (which varied from proposal to =
proposal), and one of the reasons could be "we're going to stop working =
on this draft until we get some implementation experience".
>> Working groups can do that today.
>>=20
>> E.g., httpbis calls out some of their HTTP/2.0 drafts as =
=93implementation drafts=94.
>>=20
>> Giving this qualification a slightly more formal standing (as in a =
place in the datatracker, an easily accessible list of implementation =
drafts on the web site, etc.) might help inform implementers that aren't =
following the entire WG mailing list traffic whether it is time to go =
ahead implementing.
>=20
> Exactly.
>=20
>> (Of course, the interesting part will be how to properly manage the =
expectation of stability.)
>=20
> Indeed. Some proposals included a longer-than-six-months expiration =
date, and some other proposals established an archival series (the =
documents weren't called RFCs).
>=20
> There are various ways to go. We'd just need to pick one.

And, convincing the IESG to start treating "Experimental" as exactly =
what you describe (and what, I believe, they were intended for) is =
simply not doable?

FWIW, my personal belief is that "running code" should be a requirement =
for anything going std. track -- and that a (mandatory) period as =
Experimental prior to go std. track would yield the stable spec against =
which to reasonably build code, and run (interoperability) tests, fix =
bugs, etc. If after (pulling a number out my hat here) a year as =
Experimental there's no running code, then that's probably a good =
indicator, also, as to if this is something the IETF should bother =
doing....


From nobody Wed Apr 16 07:01:45 2014
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B9EF1A01B5 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:01:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 adV9EaOjZClX for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:01:43 -0700 (PDT)
Received: from atl4mhob10.myregisteredsite.com (atl4mhob10.myregisteredsite.com [209.17.115.48]) by ietfa.amsl.com (Postfix) with ESMTP id 0FE921A01AD for <ietf@ietf.org>; Wed, 16 Apr 2014 07:01:43 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.203]) by atl4mhob10.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s3GE1cLV003939 for <ietf@ietf.org>; Wed, 16 Apr 2014 10:01:38 -0400
Received: (qmail 17517 invoked by uid 0); 16 Apr 2014 14:01:38 -0000
X-TCPREMOTEIP: 107.47.163.91
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.47.163.91) by 0 with ESMTPA; 16 Apr 2014 14:01:37 -0000
Message-ID: <534E8D3B.7080705@mti-systems.com>
Date: Wed, 16 Apr 2014 10:01:31 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Thomas Clausen <ietf@thomasclausen.org>, Spencer Dawkins <spencerdawkins.ietf@gmail.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org>
In-Reply-To: <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qHiMNMEbhFXoN3N9KW6taCElzwM
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:01:44 -0000

On 4/16/2014 9:31 AM, Thomas Clausen wrote:
> 
> FWIW, my personal belief is that "running code" should be a
> requirement for anything going std. track -- and that a (mandatory)
> period as Experimental prior to go std. track would yield the stable
> spec against which to reasonably build code, and run
> (interoperability) tests, fix bugs, etc. If after (pulling a number
> out my hat here) a year as Experimental there's no running code, then
> that's probably a good indicator, also, as to if this is something
> the IETF should bother doing....
> 


If there's no running code, or pretty concrete plans and commitments
to get there, then there's really no need for an Experimental RFC that
will get a number and last forever.  An I-D that expires in direct
conjunction with the interest and energy in it is just fine.

Experimental RFCs are for things that we're encouraging folks to get
out and play with in multiple implementations, perhaps on the real
Internet or under some specific conditions, but which may have sharp
edges or explode on impact, and need a bit more work to figure out
if we can seriously recommend the world to depend on them as Standards.

-- 
Wes Eddy
MTI Systems


From nobody Wed Apr 16 07:08:00 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31ADB1A01A9 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.199
X-Spam-Level: *
X-Spam-Status: No, score=1.199 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, J_CHICKENPOX_16=0.6, J_CHICKENPOX_21=0.6] autolearn=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 b_69NMVkbvrT for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:07:52 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.41]) by ietfa.amsl.com (Postfix) with ESMTP id C11941A01C2 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:07:44 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES531.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Wed, 16 Apr 2014 10:07:40 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: DMARC and yahoo
Thread-Topic: DMARC and yahoo
Thread-Index: AQHPWQudFl3OBUlCUUiD6pJYurib+psTtYSAgAARHwCAAINKAP//8RtA
Date: Wed, 16 Apr 2014 14:07:39 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D47D69@USCLES544.agna.amgreetings.com>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <534E57BC.1060501@cs.tcd.ie>
In-Reply-To: <534E57BC.1060501@cs.tcd.ie>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Q3j-WMOmutZgCgVjVE-ZIjiAVEA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:07:58 -0000

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Stephen Farrell
> Sent: Wednesday, April 16, 2014 6:13 AM
> To: Michael Richardson; Theodore Ts'o
> Cc: ietf@ietf.org
> Subject: Re: DMARC and yahoo
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
>=20
>=20
> On 04/16/2014 03:23 AM, Michael Richardson wrote:
>=20
> >
> > So, as a WG chair, a person known to me just tried to post to the list
> > From a brand new yahoo.com mail account.  They aren't subscribed with
> > that address.  I would normally just approve, and add them...
> >
> > It seems to me that I must now actually reject, because it would
> > affect other subscribers.
> >
> > I'm now thinking that we need to remove all the @yahoo.com addresses
> > from posting to ietf mailing lists.
> >
>=20
> This is probably obvious, but had gmail.com done what yahoo.com has done,
> that could I guess have a pretty significant impact on the IETF getting s=
tuff
> done for a while since a lot of folks in the last few years seem to have
> migrated their IETF mail to gmail.com as a reasonable way to get around
> corporate this-and-that issues.
>=20

Instead of "But had gmail.com..." substitute "When gmail.com does..." Add a=
 little loop to go down the list of various mailbox providers/ISPS/cable pr=
oviders/telcos/etc and add the same statement. Be sure to add a counter tha=
t stops the loop after the top <pick your number>. Add an if else statement=
 along the lines of "if too painful stop else keep on going". Susan Powter =
could be the spokesperson shouting "Stop the insanity".=20

> Maybe people who've done that might want to consider whether its such a
> good plan for so many IETF participants to be dependent on just one servi=
ce
> now that we have a demonstration that s/none/reject/ in one TXT RR can
> have such an impact.
>=20

Consider the scenario presented above. My impression is that the agreed upo=
n solution within this group is to remove individuals with mail accounts at=
 domains publishing p=3Dreject and tell them to go somewhere else. There ap=
pears to have been a rough consensus so that is what the group should do. N=
owhere to hide. This makes me think of the SIG at the bottom of Miles Fidel=
man posts.=20

I think a "guaranteed not to publish p=3Dreject" logo should be offered up =
by IETF as a branding mechanism. In fact, I like this idea so much I am goi=
ng to have a designer friend of mine create it. IETF prominently in the mid=
dle with "guaranteed not to publish p=3Dreject" around the perimeter of the=
 circular logo. Participating mailbox providers could display it prominentl=
y on their websites and in their marketing materials. Just to be clear for =
anyone wanting to jump in claiming trademark infringement, this falls under=
 the heading of parody - unless of course Y'all want to take the proposal s=
eriously in which case you can have the logo.

This approach will allow any potential list participants in the world the o=
pportunity to know that they won't run into the p=3Dreject problem with the=
 providers displaying the logo. IETF could maintain a webpage listing such =
providers to help market the concept. This approach will also provide miscr=
eants identification of which mailbox provider domains to abuse - kind of l=
ike homes that post gun free zone signs. And of course, it will provide oth=
er mailbox providers a heads up on which domains are potentially subject to=
 increased abuse. Hmm... what would that scoring look like in SpamAssassin?=
 MLMs that don't want to change will be protected and life will go on for s=
ome definition of go on.

Anther solution would be for IETF to provide IETF participants with account=
s at ietf.org (or a subdomain or something) and webmail, POP/IMAP access, e=
tc. Eating your own dog food, what? This is sounding more and more like wal=
led gardens from days of yore. Hey Hector, does WildCat! BBS still support =
dialup? Would you donate a license to IETF to solve this problem? Back to t=
he future. This would ensure that although IETF participants would be depen=
dent on just one service, there would only be one throat to choke so to spe=
ak.

Who would have thunk that the IETF standards process could be so exhilarati=
ng.  En garde.

Mike


From nobody Wed Apr 16 07:09:30 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 718D81A01C5 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:09:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 akEEEbni-pWE for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:09:23 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id D67A21A01C2 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:09:22 -0700 (PDT)
Received: (qmail 30583 invoked from network); 16 Apr 2014 14:09:19 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 16 Apr 2014 14:09:19 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=aac0.534e8f0f.k1404; i=johnl@user.iecc.com; bh=lQ9e6uSU3YAafUvfzdshAWn/G+YxMdEVw5CgDCLw6tg=; b=Wa6Y3VB6HYhpWo23Tqrcq5i6zEHMIvafF0QOM8FVGIdkjvCxVJyIFf9nqjorZj33NLhF9hA9j8qZ18FZkm2UrxcxGEJqsR+zXHdHTSarZFEOEiJU6E7Hc54MN23QLaZq6+ORgrh7Gq/eGrWP0tkxI6RnGUPdxZBth6ZRUO2aPje2KktuWvrSiMdj4sAMbDySjyjL2oHQeOmNcThm0IxU4Y3/8UrFaBHZdqqwOdIrXMdMHyqOWpCp6iA/Mz/MmosF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=aac0.534e8f0f.k1404; olt=johnl@user.iecc.com; bh=lQ9e6uSU3YAafUvfzdshAWn/G+YxMdEVw5CgDCLw6tg=; b=ExyChyyjZ8y0fB2R34VOCZNVgSPpnCpRNOuhScSQjT4kaSkUwv9TIEtWI08d0dhr14DlsIdMVTd9hW24oCp5CmtSMS4SNCQ/aarZAGgXte1NqxkMnHc8mczlDTVFp649wWadGMpPR6bSPGBSOLsOFCkB0kIyykqz36+Y+6bvTX43OY+oPOmS21WQaaTzJ7rBiWyuavkVGRAEpQV86Un3zoMD19g2JmMzclhqMJf2G589i5fBRbqHuxVNoVP0+AiH
Date: 16 Apr 2014 14:08:56 -0000
Message-ID: <20140416140856.43711.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
In-Reply-To: <534E6AC1.7030709@qti.qualcomm.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/K_YHv3XoYAND6lzRJIJUxv6sTdg
Cc: presnick@qti.qualcomm.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:09:27 -0000

>..., you 
>could create a mechanism where the originator's site gets some sort of 
>cryptographic data from the mailing list site and include that in its 
>signed message, such that when the eventual recipient gets the message, 
>it can verify that it came from a mailing list site that the originator 
>explicitly sent the mail to.

The Sympa list manager implemented that in what appears to be a fully
RFC compliant way about a decade ago:

http://www.sympa.org/manual/x509

I don't get the impression it's very widely used.

Every discussion list security proposal I've ever seen includes
building a whitelist of trustworthy mailers, to avoid being spoofed by
bad guys that look like discussion lists but aren't.  Once you've done
that, I've never understood the threat model of anything more complex
than delivering the mail from the whitelisted sources, perhaps after a
cursory check to ensure that it looks like the mail you were
expecting.

R's,
John


From nobody Wed Apr 16 07:15:01 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 299BC1A01C0 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:14:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 QodysHRvW0Jp for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:14:52 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 345891A01B2 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:14:52 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id p61so10851367wes.39 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:14:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kQkln4Ml6ohzDGr7WP7yFOTG0wM2GU7DTrNLuwCAxmM=; b=krrDFWhOh7mOVz5FZtI/zaYns27cYZ/CilTywIK0t9FoXcA1YDuwuk988i+XR042UV q3+8f0njXNCQ1wCi0i4iZRqK+I5t5GxLU9ILcMIvBDsgQX0NrIoB2kF5RWHogA/p/hVg RLTpt32EipxF8ijJY8PGiESQWCG0oc3CtMEhLaOrlkzYqAdKl5AZ/02a9t+y2ME4DSCm jUMy6V+UqteJfRTNw1QWTLTrny6b0MTJ75wWEr48+EDXZnEQFWLgMnLaJVr9w1V95EDC Vpgoh7yEoGh474US1lnw6ip1/l5slNj4MWXlnXKCGirUTAIaFAbzLGuhltMuROpYA6Ny ZqWw==
X-Received: by 10.194.60.114 with SMTP id g18mr2334362wjr.61.1397657688518; Wed, 16 Apr 2014 07:14:48 -0700 (PDT)
Received: from [172.24.248.99] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id h1sm34545500wjy.7.2014.04.16.07.14.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 07:14:47 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <534E8D3B.7080705@mti-systems.com>
Date: Wed, 16 Apr 2014 17:14:42 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B1D87F9-ED94-4B4A-B355-CE4D6AE7145B@gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com>
To: Wesley Eddy <wes@mti-systems.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8c24_2UtZKkaZLHpZ8rIp4a_fI8
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:14:57 -0000

On Apr 16, 2014, at 5:01 PM, Wesley Eddy <wes@mti-systems.com> wrote:

> On 4/16/2014 9:31 AM, Thomas Clausen wrote:
>>=20
>> FWIW, my personal belief is that "running code" should be a
>> requirement for anything going std. track -- and that a (mandatory)
>> period as Experimental prior to go std. track would yield the stable
>> spec against which to reasonably build code, and run
>> (interoperability) tests, fix bugs, etc. If after (pulling a number
>> out my hat here) a year as Experimental there's no running code, then
>> that's probably a good indicator, also, as to if this is something
>> the IETF should bother doing....
>>=20
>=20
>=20
> If there's no running code, or pretty concrete plans and commitments
> to get there, then there's really no need for an Experimental RFC that
> will get a number and last forever.  An I-D that expires in direct
> conjunction with the interest and energy in it is just fine.

Except that an I-D usually doesn=92t get IANA allocations, so you use a =
number from the private space, and you have to coordinate with anyone =
who wants to interoperate about which private number to use.=


From nobody Wed Apr 16 07:19:23 2014
Return-Path: <ietf@thomasclausen.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52EEC1A01E4 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:19:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.302
X-Spam-Level: 
X-Spam-Status: No, score=-1.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 uYSN5AiKoGPh for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:19:21 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 8989C1A01B3 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:19:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id A77731BDDC91; Wed, 16 Apr 2014 07:19:18 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 943051BDDCB5; Wed, 16 Apr 2014 07:19:16 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Thomas Clausen <ietf@thomasclausen.org>
In-Reply-To: <534E8D3B.7080705@mti-systems.com>
Date: Wed, 16 Apr 2014 16:19:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com>
To: Wesley Eddy <wes@mti-systems.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HVZUSiveFKvDnjdHxKCRdXFGy0M
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:19:22 -0000

On 16 Apr 2014, at 16:01, Wesley Eddy <wes@mti-systems.com> wrote:

> On 4/16/2014 9:31 AM, Thomas Clausen wrote:
>>=20
>> FWIW, my personal belief is that "running code" should be a
>> requirement for anything going std. track -- and that a (mandatory)
>> period as Experimental prior to go std. track would yield the stable
>> spec against which to reasonably build code, and run
>> (interoperability) tests, fix bugs, etc. If after (pulling a number
>> out my hat here) a year as Experimental there's no running code, then
>> that's probably a good indicator, also, as to if this is something
>> the IETF should bother doing....
>>=20
>=20
>=20
> If there's no running code, or pretty concrete plans and commitments
> to get there, then there's really no need for an Experimental RFC that
> will get a number and last forever.  An I-D that expires in direct
> conjunction with the interest and energy in it is just fine.
>=20
> Experimental RFCs are for things that we're encouraging folks to get
> out and play with in multiple implementations,

Isn't that *exactly* what we want to see happen before we propose things =
as standards?

I think that Spencer's thesis was that it didn't happen because =
"implementing towards something that isn't stable and which expires" =
(and I-D) wasn't attractive, and the bar for std.track was too high, so =
"something with a lower bar, which is stable and archival, but which =
isn't a PS" would be helpful?=20

That "something" could conveniently be Experimental.=20

Experimental exists already, and the experiment targeted (at least, the =
RTG ADs insist on Exp RFCs carrying an explicit section describing that) =
would simply be "to build a few implementations and see if they =
interoperate". (Of course, things with "sharp edges" or "things to =
figure out" would have a different "The Experiment" section ... )

The only required "process change" would be, that ADs treat =
"Experimental" as "Experimental" in their evaluation, and not at std. =
track (which they, currently, do).=20

> perhaps on the real
> Internet or under some specific conditions, but which may have sharp
> edges or explode on impact, and need a bit more work to figure out
> if we can seriously recommend the world to depend on them as =
Standards.

Fair enough, but almost orthogonal to the point I am trying to make: =
going std. track without running code (it has happened, and it is =
happening) makes even less sense than going experimental without running =
code.=20



From nobody Wed Apr 16 07:31:58 2014
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84AE31A01D6 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:31:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 9LM1BK5j7WLK for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:31:54 -0700 (PDT)
Received: from atl4mhob10.myregisteredsite.com (atl4mhob10.myregisteredsite.com [209.17.115.48]) by ietfa.amsl.com (Postfix) with ESMTP id 06A021A0205 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:31:53 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.208]) by atl4mhob10.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s3GEVmDX032042 for <ietf@ietf.org>; Wed, 16 Apr 2014 10:31:48 -0400
Received: (qmail 18342 invoked by uid 0); 16 Apr 2014 14:31:48 -0000
X-TCPREMOTEIP: 107.47.163.91
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.47.163.91) by 0 with ESMTPA; 16 Apr 2014 14:31:47 -0000
Message-ID: <534E944E.9000000@mti-systems.com>
Date: Wed, 16 Apr 2014 10:31:42 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Yoav Nir <ynir.ietf@gmail.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <4B1D87F9-ED94-4B4A-B355-CE4D6AE7145B@gmail.com>
In-Reply-To: <4B1D87F9-ED94-4B4A-B355-CE4D6AE7145B@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kZhgcmEt8pJKieEm-YNM1fjExmc
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:31:56 -0000

On 4/16/2014 10:14 AM, Yoav Nir wrote:
> 
>> 
>> If there's no running code, or pretty concrete plans and
>> commitments to get there, then there's really no need for an
>> Experimental RFC that will get a number and last forever.  An I-D
>> that expires in direct conjunction with the interest and energy in
>> it is just fine.
> 
> Except that an I-D usually doesn’t get IANA allocations, so you use a
> number from the private space, and you have to coordinate with anyone
> who wants to interoperate about which private number to use.
> 

Sounds like a protocol design issue, in not supporting experimental
codepoint usage very well.

We fixed that recently in TCP, for instance, such that experimental
options can be used by anyone (see RFC 6994), as an example.

In any case, getting registry values only requires an RFC if it's a
really important protocol that the IESG won't approve the value for
otherwise.

-- 
Wes Eddy
MTI Systems


From nobody Wed Apr 16 07:32:49 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6741A0204 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:32:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.281
X-Spam-Level: 
X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_35=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 rfmmpRjbIA5m for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:32:45 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA401A01F5 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:32:45 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 37E53CC0B0 for <ietf@ietf.org>; Wed, 16 Apr 2014 10:32:42 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id O0cSvKarlP6N for <ietf@ietf.org>; Wed, 16 Apr 2014 10:32:33 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 6A3DDCC0A8 for <ietf@ietf.org>; Wed, 16 Apr 2014 10:32:33 -0400 (EDT)
Message-ID: <534E9481.5090905@meetinghouse.net>
Date: Wed, 16 Apr 2014 10:32:33 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org List" <ietf@ietf.org>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org>
In-Reply-To: <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UkzqUI3gn28h0osgO9qTZhXueN4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:32:47 -0000

Thomas Clausen wrote:
> On 16 Apr 2014, at 16:01, Wesley Eddy <wes@mti-systems.com> wrote:
>
>> On 4/16/2014 9:31 AM, Thomas Clausen wrote:
>>> FWIW, my personal belief is that "running code" should be a
>>> requirement for anything going std. track -- and that a (mandatory)
>>> period as Experimental prior to go std. track would yield the stable
>>> spec against which to reasonably build code, and run
>>> (interoperability) tests, fix bugs, etc. If after (pulling a number
>>> out my hat here) a year as Experimental there's no running code, then
>>> that's probably a good indicator, also, as to if this is something
>>> the IETF should bother doing....
>>>
>>
>> If there's no running code, or pretty concrete plans and commitments
>> to get there, then there's really no need for an Experimental RFC that
>> will get a number and last forever.  An I-D that expires in direct
>> conjunction with the interest and energy in it is just fine.
>>
>> Experimental RFCs are for things that we're encouraging folks to get
>> out and play with in multiple implementations,
> Isn't that *exactly* what we want to see happen before we propose things as standards?
>
> I think that Spencer's thesis was that it didn't happen because "implementing towards something that isn't stable and which expires" (and I-D) wasn't attractive, and the bar for std.track was too high, so "something with a lower bar, which is stable and archival, but which isn't a PS" would be helpful?
>
> That "something" could conveniently be Experimental.
>
> Experimental exists already, and the experiment targeted (at least, the RTG ADs insist on Exp RFCs carrying an explicit section describing that) would simply be "to build a few implementations and see if they interoperate". (Of course, things with "sharp edges" or "things to figure out" would have a different "The Experiment" section ... )
>
> The only required "process change" would be, that ADs treat "Experimental" as "Experimental" in their evaluation, and not at std. track (which they, currently, do).
>
>> perhaps on the real
>> Internet or under some specific conditions, but which may have sharp
>> edges or explode on impact, and need a bit more work to figure out
>> if we can seriously recommend the world to depend on them as Standards.
> Fair enough, but almost orthogonal to the point I am trying to make: going std. track without running code (it has happened, and it is happening) makes even less sense than going experimental without running code.
>

With DMARC as a really clear-and-present example of the dangers of not 
being more explicit about the process.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Wed Apr 16 07:48:31 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ABE01A01E5 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 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, GB_MUTUALBENEFIT=2, SPF_PASS=-0.001] autolearn=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 RswvzVWaFNTK for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:48:24 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 61F271A01C0 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:48:21 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id wn1so870994obc.23 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:48:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=U7XE7z68TXOLXUTHF+NQvpmO1TGwIZy5VrJzHq1ae4Y=; b=BJo3E0NQzun9EDepyK5GO7OvtMvI8FWjIjSCcNVA++kWoSxYE3rlMHcdEWibgwlL5S uVJNrfYC6cwepdBjNnHR77LOKHnHG94d/2YrU7P3A9TN+x+M3PvAnzhwQTyWaBzhEtoX cqKdl/NZYnuor608WNw2C51vKZLWkWQQg8UwhjD5OhrUnhXgPuqmvj2xJX8krAFZseji B9MW3Qvinjiixcl78kT6pbzApzaTLyOlQaiiXVoYZMe8i+68TPtQp+Lb62k49gImJag+ /0MrgcnFUFobI39GU0LyN2x+0PQvN7h/88N5GVFunt0yS06ZbcGyrQ0dx4XEAE3PGcqx 0/sw==
X-Received: by 10.182.120.5 with SMTP id ky5mr2165546obb.11.1397659698149; Wed, 16 Apr 2014 07:48:18 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id sm4sm23989295obc.3.2014.04.16.07.48.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 07:48:17 -0700 (PDT)
Message-ID: <534E982F.5070005@gmail.com>
Date: Wed, 16 Apr 2014 09:48:15 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Yoav Nir <ynir.ietf@gmail.com>, Wesley Eddy <wes@mti-systems.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <4B1D87F9-ED94-4B4A-B355-CE4D6AE7145B@gmail.com>
In-Reply-To: <4B1D87F9-ED94-4B4A-B355-CE4D6AE7145B@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RPoXz4q2TVbppLkohfjhb0f98kI
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:48:29 -0000

On 04/16/2014 09:14 AM, Yoav Nir wrote:
> On Apr 16, 2014, at 5:01 PM, Wesley Eddy <wes@mti-systems.com> wrote:
>
>> On 4/16/2014 9:31 AM, Thomas Clausen wrote:
>>> FWIW, my personal belief is that "running code" should be a
>>> requirement for anything going std. track -- and that a (mandatory)
>>> period as Experimental prior to go std. track would yield the stable
>>> spec against which to reasonably build code, and run
>>> (interoperability) tests, fix bugs, etc. If after (pulling a number
>>> out my hat here) a year as Experimental there's no running code, then
>>> that's probably a good indicator, also, as to if this is something
>>> the IETF should bother doing....
>>>
>>
>> If there's no running code, or pretty concrete plans and commitments
>> to get there, then there's really no need for an Experimental RFC that
>> will get a number and last forever.  An I-D that expires in direct
>> conjunction with the interest and energy in it is just fine.
> Except that an I-D usually doesn’t get IANA allocations, so you use a number from the private space, and you have to coordinate with anyone who wants to interoperate about which private number to use.

All this is true, AFAICT.

In a private conversation yesterday with My Esteemed Colleague From 
Dublin, he asked why I thought we needed to pick AN answer, out of all 
the possible ways for working groups to do what we're talking about here.

Stephen was right - we don't have to pick AN answer. What's appropriate 
for some proposals may not be appropriate for other proposals (and IANA 
considerations would be one of several flavors of constraints that would 
vary across proposals).

But I think picking a few answers would be helpful.

One of the suggestions in this thread was that we put specifications 
that are thought ready for prototyping in the same place, so people who 
want to contribute to the process as implementers know where to look. 
Not saying that's the right thing to do, but it's probably something 
worth thinking about (rather than, "for that specification, in that 
working group, if they think it's ready for prototyping, you should look 
THERE, but for this other specification ...").

Finally, I'll say what I usually say at this point in the conversation, 
which is that when we were talking about stuff like this in the early 
2000s, the expectation was that we would wait until we had IETF 
consensus to modify our process BCPs. It turns out that's a really high 
bar. The IESG ended up approving https://tools.ietf.org/html/rfc3933 as 
one way to try things without making irrevocable changes to the way 
things work for everyone.

RFC 3933 is still in effect (as BCP 93), and it allows experiments with 
changes to BCPs that would go away if they turn out to be bad ideas. 
There are probably one or two reasonable process experiments that would 
be appropriate as we try to figure out ways to (as Jari suggested):

   o  ... work to mutual benefit with open source efforts (those that 
would benefit from an IETF-like environment)?

   o  ... better build specs to (rough) consensus, including making sure 
that (an understood) vocal minority opinion does not block progress?

   o  ... focus on running code.

As we said at the IETF 89 Admin Plenary when discussing TRAM and DART, 
the IESG can move pretty quickly when we get coherent proposals. Please 
talk amongst yourselves, if this matters to you.

Spencer, who (full disclosure) was co-author on RFC 3933, speaking only 
as a retired process wonk


From nobody Wed Apr 16 08:20:32 2014
Return-Path: <thomas@thomasclausen.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 082D41A0132 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:24:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 B69HyWy1A4R1 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 07:24:50 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 011861A01E1 for <ietf@ietf.org>; Wed, 16 Apr 2014 07:24:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id EB48E1BDE2C0; Wed, 16 Apr 2014 07:24:46 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 443D71BDE2BE; Wed, 16 Apr 2014 07:24:44 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Thomas Clausen <thomas@thomasclausen.org>
In-Reply-To: <4B1D87F9-ED94-4B4A-B355-CE4D6AE7145B@gmail.com>
Date: Wed, 16 Apr 2014 16:24:42 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B9D05FA7-BA82-491D-85DA-E5A285F82EA4@thomasclausen.org>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <4B1D87F9-ED94-4B4A-B355-CE4D6AE7145B@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ctP1f8-eyf8AiWTURvYQ9sI0Sec
X-Mailman-Approved-At: Wed, 16 Apr 2014 08:20:28 -0700
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 14:24:51 -0000

On 16 Apr 2014, at 16:14, Yoav Nir <ynir.ietf@gmail.com> wrote:

>=20
> On Apr 16, 2014, at 5:01 PM, Wesley Eddy <wes@mti-systems.com> wrote:
>=20
>> On 4/16/2014 9:31 AM, Thomas Clausen wrote:
>>>=20
>>> FWIW, my personal belief is that "running code" should be a
>>> requirement for anything going std. track -- and that a (mandatory)
>>> period as Experimental prior to go std. track would yield the stable
>>> spec against which to reasonably build code, and run
>>> (interoperability) tests, fix bugs, etc. If after (pulling a number
>>> out my hat here) a year as Experimental there's no running code, =
then
>>> that's probably a good indicator, also, as to if this is something
>>> the IETF should bother doing....
>>>=20
>>=20
>>=20
>> If there's no running code, or pretty concrete plans and commitments
>> to get there, then there's really no need for an Experimental RFC =
that
>> will get a number and last forever.  An I-D that expires in direct
>> conjunction with the interest and energy in it is just fine.
>=20
> Except that an I-D usually doesn=92t get IANA allocations, so you use =
a number from the private space, and you have to coordinate with anyone =
who wants to interoperate about which private number to use.

Hum....I do know that there are experimental protocols that have IANA =
allocations (though, that may be from the olden days), and I think that =
there's nothing preventing an Experimental from setting up IANA =
registries on its own.

Furthermore, that "coordination" you talk about....wouldn't simply =
documenting that in the Experimental RFC suffice:

	"For the purpose of the experiments, documented in this RFC, use =
UDP port XXXXX,=20
	 message type YYY, and error codes A, B and C from the register =
xxxx. Note that these
	 codepoints all are from the private/experimental spaces of =
their respective registries, and
	 that therefore this section does not represent IANA =
allocations"

Sure, the RFC would get an RFC number, but that's about it.=


From nobody Wed Apr 16 08:32:47 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBEE31A019B for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 08:32:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_35=0.6, SPF_PASS=-0.001] autolearn=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 fdc20-_11br4 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 08:32:44 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id CF0251A0135 for <ietf@ietf.org>; Wed, 16 Apr 2014 08:32:44 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id p10so10745462pdj.26 for <ietf@ietf.org>; Wed, 16 Apr 2014 08:32:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=qgSiYmohx/d7VrVY6TjoBiuRSE8X5XSkiIf59MMGB1I=; b=YAvkQCNSsIzPW+k9x6MondbnYKENYnjkQ7a5qNmsJKmt4deKGJgRdta3jRn9a2QgOo uUmQOinOquWkSFxy2tn6BjK5iwYEUBaLwEo38NeeR69B7BPwvsMBjtAiRpNKqNOyr3kM VUymhFGuNmu8xhFPvEZQ2VbYfe0D2HLdBnmUwhaipupeaMvVV09Dc9ls6j+t1+pV+HpH 6NCDty0VteHM3PJIEAoUyaNo3x8tMPNKUtel1xxZyeFxinjAqL4HMDljwAYWlo8GPw9r xOHZjXH+wN3qmqVLJ9ANwMDbaqpjptOm6VrO9wBPzUZHUjyYdsJjJ8TG4lVY7RbcOMNv ms4Q==
X-Received: by 10.68.135.42 with SMTP id pp10mr9312474pbb.58.1397662361735; Wed, 16 Apr 2014 08:32:41 -0700 (PDT)
Received: from spandex.local (209-193-46-203-rb1.sol.dsl.dynamic.acsalaska.net. [209.193.46.203]) by mx.google.com with ESMTPSA id y4sm47655291pbk.76.2014.04.16.08.32.40 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 08:32:40 -0700 (PDT)
Message-ID: <534EA296.20900@gmail.com>
Date: Wed, 16 Apr 2014 07:32:38 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org>
In-Reply-To: <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qowv_-jsA2H41uJbUcybPxS4o58
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 15:32:46 -0000

On 4/16/14 6:19 AM, Thomas Clausen wrote:
> I think that Spencer's thesis was that it didn't happen because
> "implementing towards something that isn't stable and which expires"
> (and I-D) wasn't attractive, and the bar for std.track was too high,
> so "something with a lower bar, which is stable and archival, but
> which isn't a PS" would be helpful?

I think that the terrain has changed a bit, or at least
that's certainly what the author of the blog post is
suggesting.  Implementation seemed to be de-emphasized
for some period, precisely because of the issues you
mention, but we're seeing more work being brought to the
IETF being driven by implementation (and here I'm
thinking of things like HIP and certificate transparency)
and frankly they seem to go a lot more smoothly in
terms of IETF process, as well.  Chartering seems to to
more smoothly and the work progresses more quickly.
The "open source" question really seems to be more
about collaboration than to do specifically with
licensing.

I'm not sure that the IETF should get more directly
involved with supporting implementation efforts but I
do think that we should recognize that work coming
in that's already been implemented tends to be more
fully-baked and privilege that in some way.  One worries
about that encouraging crappy implementation, but I'm
not sure that crappy implementation is much worse than
no implementation.

Melinda


From nobody Wed Apr 16 08:45:43 2014
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F64B1A01F2; Wed, 16 Apr 2014 08:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.501
X-Spam-Level: 
X-Spam-Status: No, score=-0.501 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_PASS=-0.001] autolearn=ham
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 dnAyrJjwTCjw; Wed, 16 Apr 2014 08:45:34 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id DCE631A0230; Wed, 16 Apr 2014 08:45:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 0DC741E41DE; Wed, 16 Apr 2014 08:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zzRWwbunKlmd; Wed, 16 Apr 2014 08:44:59 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) by c8a.amsl.com (Postfix) with ESMTPSA id 98A0C1E39E0; Wed, 16 Apr 2014 08:44:59 -0700 (PDT)
From: IAB Chair <iab-chair@iab.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Call for Review of draft-iab-cc-workshop-report-01, "Report from the IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communication"
Date: Wed, 16 Apr 2014 11:45:30 -0400
Message-Id: <F83C2EAE-6E47-40D2-AFCF-3FEC377E3973@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
Mime-Version: 1.0 (Apple Message framework v1085)
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JIH6cBBPS5EzWMECwZVxXKFbx5Q
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 15:45:39 -0000

This is a call for review of "Report from the IAB/IRTF Workshop on =
Congestion Control for Interactive Real-Time Communication" prior to =
potential approval as an IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-cc-workshop-report/

The Call for Review will last until 14 May 2014.  Please send comments =
to iab@iab.org.=20

On behalf of the IAB,
 Russ Housley
 IAB Chair


From nobody Wed Apr 16 08:51:07 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5354E1A01E4 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 08:51:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.573
X-Spam-Level: 
X-Spam-Status: No, score=-1.573 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 rwZYI5JQIcFy for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 08:51:00 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 34C291A0214 for <ietf@ietf.org>; Wed, 16 Apr 2014 08:51:00 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WaS6y-0008IX-5z; Wed, 16 Apr 2014 15:50:56 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 851455808C7; Wed, 16 Apr 2014 11:50:55 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397663455; bh=Bn7y+uyccx61RY4kCKR/nkbjRgGCQWKwWTV976Xn20I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=qBBUnXQlElOo24uthpYFzGhRYBXXLzt7qYPh046lqanROfb+sTs0Q97Ra8qNtuaY1 UCJPA4O7CMdMLIxUNSXJkK5yRV2z9NvWxj3W5gWBuLpFMBzz50ZjqO7ogn142zrphD gyGLpuLUobp+DBgaey7HOEdzO4xPtfC5EOB8TT3Y=
Date: Wed, 16 Apr 2014 11:50:55 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: "MH Michael Hammer (5304)" <MHammer@ag.com>
Subject: Re: DMARC and yahoo
Message-ID: <20140416155055.GC17208@thunk.org>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <534E57BC.1060501@cs.tcd.ie> <CE39F90A45FF0C49A1EA229FC9899B0507D47D69@USCLES544.agna.amgreetings.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D47D69@USCLES544.agna.amgreetings.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LGHJn5ZK8idWrtHCXdCPBjvzxqk
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 15:51:04 -0000

On Wed, Apr 16, 2014 at 02:07:39PM +0000, MH Michael Hammer (5304) wrote:
> 
> 
> Instead of "But had gmail.com..." substitute "When gmail.com
> does..." 

You are asserting that gmail will eventually do what Yahoo has done.

I can't speak for my employer, but I suspect there will be a lot of
people (both inside and outside of the company) lobbying to make sure
gmail doesn't do the same insane thing that Yahoo has done.  I have
quite a bit of faith that senior folks like Vint Cerf will take a bit
more of a nuanced view than some of the DMARC cheerleaders have done,
and his voice does carry a fair amount of weight.

Cheers,

						- Ted

P.S.  One of the reasons why I think mailing list software should pick
mechanisms that inflict pain on yahoo.com customers, and hopefully get
them to switch, is that hopefully other e-mail providers will consider
the costs of using DMARC p=reject for domains where users might need
to send mail to mailing list, and choose differently from Yahoo.


From nobody Wed Apr 16 09:08:56 2014
Return-Path: <cabo@tzi.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CFB91A0176 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 09:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, SPF_HELO_PASS=-0.001] autolearn=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 bJZbfxNab5vC for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 09:08:49 -0700 (PDT)
Received: from informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) by ietfa.amsl.com (Postfix) with ESMTP id BA9671A014B for <ietf@ietf.org>; Wed, 16 Apr 2014 09:08:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from smtp-fb3.informatik.uni-bremen.de (smtp-fb3.informatik.uni-bremen.de [134.102.224.120]) by informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id s3GG8ZbS014846; Wed, 16 Apr 2014 18:08:35 +0200 (CEST)
Received: from eduroam-pool7-0961.wlan.uni-bremen.de (eduroam-pool7-0961.wlan.uni-bremen.de [134.102.115.193]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp-fb3.informatik.uni-bremen.de (Postfix) with ESMTPSA id 8F12511B1; Wed, 16 Apr 2014 18:08:35 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org>
Date: Wed, 16 Apr 2014 18:08:33 +0200
X-Mao-Original-Outgoing-Id: 419357313.532677-d7f23b09160da1d82f189752b4dbae87
Content-Transfer-Encoding: quoted-printable
Message-Id: <A17B60B3-7921-4F02-9EDE-297FA126193A@tzi.org>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org>
To: Thomas Clausen <ietf@thomasclausen.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XZJV9odgCo5g3eh2EqGnRI8xexA
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 16:08:53 -0000

On 16 Apr 2014, at 16:19, Thomas Clausen <ietf@thomasclausen.org> wrote:

> That "something" could conveniently be Experimental.=20

Experimental means something different in the IETF, as in:

=93This is a finished specification, but we are really not sure this =
will work until we have run an experiment.
Don=92t base any plans on the assumption that this experiment will =
succeed.=94

Implementation draft means:

=93This is still subject to change, but we promise to be frugal in the =
changes we make from here on.
We are pretty sure this will work, no major experiments required, just =
implementation experience to maybe tweak it some more.
This will be done soon, so go ahead and build the products.=94

Conflating these two almost diametrally opposed sets of features into a =
single class of document increases confusion.

Yes, we need to find a way for implementation drafts to get IANA =
numbers.
(The IANA numbers problem is bigger, e.g., downrefs from finished specs =
should also be in a position to get numbers immediately even if not all =
i=92s are crossed and t=92s are dotted in the downref spec.)

Gr=FC=DFe, Carsten


From nobody Wed Apr 16 09:32:05 2014
Return-Path: <ietf@thomasclausen.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 122E11A0248 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 09:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 0yq09Mh3pOQV for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 09:31:58 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) by ietfa.amsl.com (Postfix) with ESMTP id B5A3D1A014B for <ietf@ietf.org>; Wed, 16 Apr 2014 09:31:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id A06CB1C0B23; Wed, 16 Apr 2014 09:31:49 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from [192.168.147.111] (mtg91-1-82-227-24-173.fbx.proxad.net [82.227.24.173]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 14DA91C0AD3; Wed, 16 Apr 2014 09:31:46 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Thomas Clausen <ietf@thomasclausen.org>
In-Reply-To: <A17B60B3-7921-4F02-9EDE-297FA126193A@tzi.org>
Date: Wed, 16 Apr 2014 18:31:43 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6E87476A-0FE1-4900-9BB7-7D882FBA6CBF@thomasclausen.org>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org> <A17B60B3-7921-4F02-9EDE-297FA126193A@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kWs_h0xJvGZKzN1Cs9od4AkS78c
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 16:32:03 -0000

On 16 Apr 2014, at 18:08, Carsten Bormann <cabo@tzi.org> wrote:

> On 16 Apr 2014, at 16:19, Thomas Clausen <ietf@thomasclausen.org> =
wrote:
>=20
>> That "something" could conveniently be Experimental.=20
>=20
> Experimental means something different in the IETF, as in:
>=20
> =93This is a finished specification, but we are really not sure this =
will work until we have run an experiment.
> Don=92t base any plans on the assumption that this experiment will =
succeed.=94

I'd submit that that would be true for /any/ specification that has not =
been implemented and experimented with. So I think that it exactly means =
what I say ;)

> Implementation draft means:
>=20
> =93This is still subject to change, but we promise to be frugal in the =
changes we make from here on.
> We are pretty sure this will work, no major experiments required, just =
implementation experience to maybe tweak it some more.
> This will be done soon, so go ahead and build the products.=94
>=20
> Conflating these two almost diametrally opposed sets of features into =
a single class of document increases confusion.

<sarcasm>
Oh, oh, oh, I have an idea. This "implementation draft" that you talk =
about, we could call that "Proposed Standard" then, because that is what =
we really "propose (after some implementation experience) becomes a =
standard".=20

And when the implementation experiences and tweaks have been done, we =
will then publish a "Draft Standard" based on it -- and later, once =
we're absolutely sure, we'll promote it as an "Internet Standard".

I think that I remember a process like this, from somewhere, where might =
that have been .... ;)
</sarcasm>

Being serious for a moment....the IESG/IETF/IAB/someone recently decided =
that we needed to reduce the std. track from 3 to 2 levels. This is =
proposing adding the third level back, perhaps perceived "below" =
Proposed Standard ...

In your definitions above, "Experimental" and "Implementation Draft" =
both are ways of saying "Look, this is not mature enough to be a =
standard yet, but we're at a breaking point where we think we have =
something stable, that we want to get coded up, and played with".

Either we're ready to "propose a standard" and we hit std. track -- or, =
we're not, and need to build up some more implementation and =
experimental basis, in which case Experimental is the way to go.=20

I much prefer using that which the RTG ADs have imposed on the RTG Area, =
which is for Experimental protocols to have a section discussing the =
experiment.  It gives the flexibility to say exactly what the document =
is, and why it is written -- without re-introducing a 3rd level on the =
std. track.

Having an "implementation draft" status that is declared by a WG alone =
(or by WG chairs, or perhaps the responsible AD) isn't terribly helpful =
in terms of overall document quality: it excludes the (often extremely =
valuable) cross-area reviews that occur as part of the IESG processing =
-- and which almost never occurs before IESG processing -- and which, =
occasionally, causes design decisions to be revisited profoundly.....

Sure, we can come up with a special status and process for =
"Implementation Draft" which captures cross-area reviews, etc -- but =
that'd look a lot like the process for Experimental, and would involve =
many of the same people.

As I always say: "if it walks like a duck, and it quacks like a duck -- =
then, it probably tastes good served in orange sauce"


> Yes, we need to find a way for implementation drafts to get IANA =
numbers.
> (The IANA numbers problem is bigger, e.g., downrefs from finished =
specs should also be in a position to get numbers immediately even if =
not all i=92s are crossed and t=92s are dotted in the downref spec.)

That, to me, seems to be a much simpler problem to manage ;)

Thomas

> Gr=FC=DFe, Carsten
>=20


From nobody Wed Apr 16 10:03:30 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8091A023D for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 10:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.1
X-Spam-Level: 
X-Spam-Status: No, score=-0.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, J_CHICKENPOX_21=0.6, J_CHICKENPOX_51=0.6] autolearn=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 AIQaR9_xeH3J for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 10:03:28 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.41]) by ietfa.amsl.com (Postfix) with ESMTP id 2CB811A0222 for <ietf@ietf.org>; Wed, 16 Apr 2014 10:03:24 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES531.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Wed, 16 Apr 2014 13:03:20 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Theodore Ts'o <tytso@mit.edu>
Subject: RE: DMARC and yahoo
Thread-Topic: DMARC and yahoo
Thread-Index: AQHPWQudFl3OBUlCUUiD6pJYurib+psTtYSAgAARHwCAAINKAP//8RtAgABtPID//78FsA==
Date: Wed, 16 Apr 2014 17:03:19 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D480CF@USCLES544.agna.amgreetings.com>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <534E57BC.1060501@cs.tcd.ie> <CE39F90A45FF0C49A1EA229FC9899B0507D47D69@USCLES544.agna.amgreetings.com> <20140416155055.GC17208@thunk.org>
In-Reply-To: <20140416155055.GC17208@thunk.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cRQNpOXDrpcTVoGdfFvpylZ8_8U
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 17:03:29 -0000

> -----Original Message-----
> From: Theodore Ts'o [mailto:tytso@mit.edu]
> Sent: Wednesday, April 16, 2014 11:51 AM
> To: MH Michael Hammer (5304)
> Cc: ietf@ietf.org
> Subject: Re: DMARC and yahoo
>=20
> On Wed, Apr 16, 2014 at 02:07:39PM +0000, MH Michael Hammer (5304)
> wrote:
> >
> >
> > Instead of "But had gmail.com..." substitute "When gmail.com does..."
>=20
> You are asserting that gmail will eventually do what Yahoo has done.
>=20

I am asserting that if, as an organization, Google (or any other mailbox pr=
ovider for that matter) perceives that p=3Dreject is working for other prov=
iders of a similar nature to mitigate abuse then yes, they will, even recog=
nizing potential negative consequences in some areas as long as they believ=
e that the benefits outweigh the consequences. It may be that no other mail=
box provider chooses to make such a move.  I'm also saying that mailbox pro=
viders which validate DMARC have the data to see what the impacts are - bot=
h on abuse as well as broken mail through mailing lists and other sources. =
This is especially true for large providers that have the resources to do t=
he analysis.

> I can't speak for my employer, but I suspect there will be a lot of peopl=
e
> (both inside and outside of the company) lobbying to make sure gmail
> doesn't do the same insane thing that Yahoo has done.  I have quite a bit=
 of
> faith that senior folks like Vint Cerf will take a bit more of a nuanced =
view
> than some of the DMARC cheerleaders have done, and his voice does carry a
> fair amount of weight.
>=20

As I've said before, my ox isn't gored on the mailing list issue. Each mail=
box provider will make a calculus as to which way to jump. This calculus wi=
ll change over time for each mailbox provider depending on a number of fact=
ors and the perceived outcomes for the organization and its customers. Let'=
s assume that Google chooses not to follow Yahoo but a number of other larg=
e providers do. You still have a similar outcome. I'm not presenting this a=
s cheerleading for DMARC. I'm presenting this as a real situation and other=
 mailbox providers, both large and small, may choose to go this direction. =
I haven't heard any of the denizens of this list present any approach as to=
 how they will deal with such a sea change.=20

As von Moltke the Elder wrote, "no plan of operations extends with any cert=
ainty beyond the first contact with the main hostile force".

Setting aside your personal preference as to outcomes, I'd love to hear you=
r thoughts on how IETF and/or mailing list operators would deal with such a=
 situation (some significant portion of mailbox providers/users migrated to=
 this new paradigm) should it occur.=20

> Cheers,
>=20
> 						- Ted
>=20
> P.S.  One of the reasons why I think mailing list software should pick
> mechanisms that inflict pain on yahoo.com customers, and hopefully get
> them to switch, is that hopefully other e-mail providers will consider th=
e
> costs of using DMARC p=3Dreject for domains where users might need to sen=
d
> mail to mailing list, and choose differently from Yahoo.

That is certainly a plan but it doesn't work so well if it becomes Yahoo+n.=
 My wife and I have discussed this issue and our personal decision is that =
if our alma maters, charitable organizations that we contribute to, etc. un=
dertake this tactic to intentionally inflict pain on us if our mailbox prov=
ider (neither of us happens to use Yahoo) should go this route, we will sim=
ply choose other places to give our support and donations. This is not a fu=
nction of the DMARC debate itself but is instead a function of an organizat=
ion biting the hand that feeds them to intentionally inflict pain to gain l=
everage over a 3rd party. For some organizations, while our donations are n=
ot critical, they are significant enough to get senior management attention=
 if withheld with an explanation of why we have made that choice.


From nobody Wed Apr 16 10:08:07 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D14C61A01E9 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 10:08:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 vHG8nW1EiCSP for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 10:08:01 -0700 (PDT)
Received: from mail-oa0-x236.google.com (mail-oa0-x236.google.com [IPv6:2607:f8b0:4003:c02::236]) by ietfa.amsl.com (Postfix) with ESMTP id 4E73E1A0165 for <ietf@ietf.org>; Wed, 16 Apr 2014 10:08:01 -0700 (PDT)
Received: by mail-oa0-f54.google.com with SMTP id n16so12909248oag.27 for <ietf@ietf.org>; Wed, 16 Apr 2014 10:07:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=uDB/rfvxsAvzIkRZ9LpaYKVyZVozs+FY/+QHBWGm6aQ=; b=yatRi9sbbpRcQHQWl+gMudmMiL8yH7qlNz+UCtYCG1MC6FGrweZQZWrtZaLbw8MR2w TBXVNXEMzb7l2wZUyAwuXK0Fcyzby0DHNisgYDuG68XT5AvPRYnELQtWyPPNfZIjVqsi zBt58v5ftl2NqaTwas9tLh/4bqWZbeyRtSzfwoQC52SYgwlFAB2OU8VSglrRvUvMoVce IFcfqI/NQscQsMq7van8RZhFwOziSm/5myu1s6Yv6bITNUDxwBlgnTjHqHUEXoDrdW4Y 2JszZn/951LWeDVLya5+fyxCyyPKp3aBeauny+Z/VfEDWanQM0j6qR3qNVEGZvg1tU97 miOg==
X-Received: by 10.182.250.200 with SMTP id ze8mr1562115obc.72.1397668078039; Wed, 16 Apr 2014 10:07:58 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id np9sm40240830obc.12.2014.04.16.10.07.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 10:07:57 -0700 (PDT)
Message-ID: <534EB8EC.8010409@gmail.com>
Date: Wed, 16 Apr 2014 12:07:56 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Carsten Bormann <cabo@tzi.org>,  Thomas Clausen <ietf@thomasclausen.org>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org> <A17B60B3-7921-4F02-9EDE-297FA126193A@tzi.org>
In-Reply-To: <A17B60B3-7921-4F02-9EDE-297FA126193A@tzi.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/s2v4btlmOfezJPPAupfD2sop_ss
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 17:08:06 -0000

I need to go read some drafts, but on one point ...

On 04/16/2014 11:08 AM, Carsten Bormann wrote:
> On 16 Apr 2014, at 16:19, Thomas Clausen <ietf@thomasclausen.org> wrote:
>
>> That "something" could conveniently be Experimental.
> Experimental means something different in the IETF, as in:
>
> “This is a finished specification, but we are really not sure this will work until we have run an experiment.
> Don’t base any plans on the assumption that this experiment will succeed.”
>
> Implementation draft means:
>
> “This is still subject to change, but we promise to be frugal in the changes we make from here on.
> We are pretty sure this will work, no major experiments required, just implementation experience to maybe tweak it some more.
> This will be done soon, so go ahead and build the products.”
>
> Conflating these two almost diametrally opposed sets of features into a single class of document increases confusion.

This was my point in mentioning https://tools.ietf.org/html/rfc3933. The 
parts of my memory of the early 2000s that I haven't successfully 
blotted out lead me to think that we were consistently making two errors 
in those discussions.

We tried to figure out *the* right answer when there probably were right 
answers with (quoting Carsten) "diametrically opposed" characteristics, 
and since we couldn't stretch one right answer over all the problems, 
nothing happened.

And we had to get IETF consensus for one answer that didn't solve all 
the problems, with no actual experience with that answer.

The IETF approved BCP 93 to give people the possibility of experimenting 
with multiple answers, dropping the answers that don't work, and keeping 
the ones that do.

The IETF discussion list has seen a lot of spilled digital ink trying to 
solve problems like these. If people want to chat and move on, that's 
fine. If people want to try to put proposals together, that's fine 
(perhaps even more fine).

But please don't make the mistakes we made more than a decade ago.

Spencer


From nobody Wed Apr 16 11:04:40 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92FBB1A0160 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 11:04:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.238
X-Spam-Level: *
X-Spam-Status: No, score=1.238 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=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 82E_v4PDg8Xa for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 11:04:34 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFF0F1A0273 for <ietf@ietf.org>; Wed, 16 Apr 2014 11:04:33 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.131.153]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3GI44uZ003076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Apr 2014 11:04:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397671458; bh=qO/Enz8B5AnpFIjFChskjH9Z7tKhIthTI4A4k+B/bD0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YQYANaGDjuQ5iNYteULJ3KJeAfb16fRor9VGHnzDkq020tiipZLHQPVfpLNuCyuie rnog3EloIWc7SG5wn1aQYYlFjq8Cglh+QKwg++H04uI4ZybLbAdZbqz28ehlqcgVcO 8fYf970yEpQHNdwC2tm9n4c6u00dWmEosp1f2DI0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397671458; i=@elandsys.com; bh=qO/Enz8B5AnpFIjFChskjH9Z7tKhIthTI4A4k+B/bD0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TZ0HVL0UNvkeJBMTMo3/9Z+Db5ZvW72r3oLoTOmU1Lx5zZKeW+uWnByxDEy6dzjs8 T9Or83pp9dbqqkbZNnAh9wuNxrQLj1l7AzmA33sHcfq79xtxoEryMoOxdL8WaC51P3 95eOcp9tQVjFl/5uS6D8BSh+xoDDCq59bz+m0q5g=
Message-Id: <6.2.5.6.2.20140415222043.0cc1b818@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 16 Apr 2014 10:26:15 -0700
To: "MH Michael Hammer (5304)" <MHammer@ag.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: Let's talk (was: DMARC: perspectives from a listadmin of large open-source lists)
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D47986@USCLES544.agna.am greetings.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com> <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.gmail.com> <6.2.5.6.2.20140415111633.0da3d030@resistor.net> <CE39F90A45FF0C49A1EA229FC9899B0507D4749E@USCLES544.agna.amgreetings.com> <6.2.5.6.2.20140415133648.0df89818@elandnews.com> <CE39F90A45FF0C49A1EA229FC9899B0507D47986@USCLES544.agna.amgreetings.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MX4Iw-iGCV-vduEnvErk54AGZFc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 18:04:38 -0000

Hi Mike,
At 20:44 15-04-2014, MH Michael Hammer (5304) wrote:
>I think this conflates two different issues:

Ok.

>1) Cost to participation. While I may work for a larger 
>organization, much if not most of my participation is in addition to 
>my other work obligations. I know of other folks in a similar 
>situation. I participated before I worked at a large organization, I 
>participated when I had my own small business and I may choose to 
>participate in the future if my circumstances change. There are 
>other people whose occupation consists solely of standards work. I 
>don't have any meaningful answer to your comment. Quite frankly, I'm 
>asking myself why I should personally continue to engage with the 
>IETF process at all. It's not as if my employer is demanding it. Do 
>I really want to be engaging with IETF after a 16 hour day working 
>on other stuff? It must be masochism.

One of the reasons to participate in the IETF is self-interest.  The 
IETF standard for IETF participants is attending three out of five 
meetings.  A small business cannot afford that cost.  The list of 
volunteers is at https://datatracker.ietf.org/nomcom/ann/58250/  How 
many of the people are from small businesses?

>2) Getting ignored or minority view. I don't believe it is simply a 
>function of company size - at least for the WGs I've participated 
>in. I'd assert that at least in the email/email auth WGs it's more a 
>function of long term participants, many of whom have calcified 
>positions (across the spectrum). I can think of at least one person 
>from a relatively large company who gets ignored a fair bit, so size 
>is not necessarily a factor. I've been in the minority view on 
>various issues in the WGs I've participated in. That's life - I 
>chose Betamax. To a certain extent it's also a function of who is 
>wrangling the WG and how they manage the WG. I don't really think 
>about whether a person is with a large company, a small company or 
>an individual - I'm more interested in the quality and practicality 
>of their ideas. I'm more of a security and operations guy and that 
>colors my perspective.

The usual explanation for the ways things are is "That's 
life".  That's what gets you (used in a general sense) calcified 
positions, specifications that takes years to be published and other 
IETF problems.

>I'm not sure if you are looking for a response to Dave Cridland's 
>message in the context of DMARC specifically. As I noted when I 
>first posted to this group, I don't speak on behalf of DMARC and my

I wasn't looking for a response as I have been staying out of DMARC 
discussions.

>  comments are on a personal basis. When DMARC came along, as a 
> sender I only had to publish a p=reject policy. We (my employer) 
> had done the heavy lifting in terms of changing our mailing 
> practices back in 2007 before there was a dmarc.org or a spec. I 
> had some concerns about a wide open WG but wasn't necessarily 
> against it. My concerns were more along the line of how much of a 
> grind it might be on a personal basis (after my experiences with 
> other WGs). I do recognize that others made a significant 
> investment in implementing running code to make things work. I 
> think a lot of people underestimate what was involved and overly 
> discount concerns about radical modifications to the spec. When I 
> did my original effort in 2007 it was a five month project 
> involving quite a few people to change how our websites handled 
> mail to accommodate strong authentication for SPF and DKIM. I'll 
> also point out that the interoperability event for DKIM didn't take 
> place until 2008 which meant I was somewhat going out on a limb. 
> I'm sure that for others to do their DMARC implementations on the 
> mailbox provider side several years later it was a larger effort 
> than what I went through. My personal belief is that nobody was 
> looking to get an IETF rubber stamp. Perhaps the concerns might 
> have been communicated differently and perhaps there might have 
> been a little less skepticism as to intent.

Rewriting a specification from scratch is rather silly if there isn't 
a good reason to do that.  In my opinion the purpose of a working 
group is to review the drafts and send work of acceptable quality to 
the Area Director.  It is possible to take into consideration the 
constraints of the various parties if there is a public 
explanation.  At the same time the parties could consider that 
hinting for an IETF rubber stamp is going to be problematic.

I'll highlight a comment from Stephen J. Turnbull:

   "It might help if you gave us the annotated version of what you do like
    about it, instead of telling us that everything we've been doing for
    20 years is wrong, and that we're crazy to object to the violation of
    the most fundamental and ancient email RFC (not to mention violating
    copyright law in every Berne Convention signatory) by corrupting the
    authorship information of each post we process."

If it is difficult to explain in English words, show the source 
code.  It is worthwhile to look into the interoperability issues.  It 
may not be possible to solve all of them quickly.  That's not a 
significant problem as long as a working group does not break too much stuff.

>So on to the mail list issue. On one level I want to say not my 
>issue. I don't publish p=reject for any domains with users that send 
>to mail lists so as I've said, my ox isn't getting gored. There were 
>plenty of discussions in the DKIM working group about 1st party 
>signatures vs 3rd party signatures and trust and reputation and who 
>should do what and who wouldn't do what. At the end of the day the 
>can was kicked down the road. So here we are. I don't have any 
>answers for this group. I've already stated in a previous post how I 
>think it will play out. I'm leaning towards just walking away and 
>spending cycles on something as that is more productive from my 
>perspective. The juice just isn't worth the squeeze.

It's okay to say "not my issue".  It is an issue if most people in 
the group say "not my issue".  If there isn't any progress on the 
issue the note to the Area Director could be "the working group does 
not have the competence to address this issue".

>I don't think you are likely to see someone speaking up in that 
>particular way. "My boss has bad ideas" posted to a public forum is 
>not a career enhancing move even if phrased politely. Those sorts of 
>issues would likely get resolved internally or the person would 
>likely choose to move to another roost if it is a significant issue. 
>That's just common sense. At least for me, in the WGs I've 
>participated in, I've had a lot of latitude because the issues are 
>technical and it is more me keeping management apprised of what is 
>happening and what I'm doing than me getting directives. I can't 
>speak for others or other organizations. I don't have anything to 
>sell or market so I have no reason to use marketing language. My 
>goal is to protect end users from maliciousness that tries to 
>leverage our domains and brands - things like SPF, DKIM and DMARC 
>help do that in conjunction with other efforts such as takedowns, 
>blocking, prosecutions, etc. I also get involved in other anti-abuse 
>efforts that have nothing to do with my employer - because I believe 
>it is the right thing to do. Standards are just one piece of the puzzle.

Speaking about career enhancing moves, common sense dictates that it 
is to be assumed that the individual is the mouthpiece of the 
organization (I am not inferring that you are).  In my opinion 
reviews from individuals affiliated with the companies listed on the 
web page might not fit within the objectivity guidelines.  It may be 
difficult to find an external reviewer if Dave Cridland does not wish 
to donate his intellectual property rights.

Takedowns, blocking, prosecutions, brand protection, etc. are 
non-technical issues.  These issues could be discussed if it helps 
the average participant to understand the puzzle.  Past DKIM and SPF 
discussions could be listed under "gives the WG Chair(s) a headache".

Is this work doable?  I don't know.  Would I put effort to solve 
Company X is breaking the internet?  No, as it is an expense which I 
cannot afford.  Did I learn anything from the discussions on the 
previous topic?  Yes. :-)

Regards,
S. Moonesamy 


From nobody Wed Apr 16 11:10:29 2014
Return-Path: <scott.brim@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 832EC1A02B4 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 11:10:26 -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, SPF_PASS=-0.001] autolearn=ham
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 GgMNuy9v5fvJ for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 11:10:25 -0700 (PDT)
Received: from mail-oa0-x231.google.com (mail-oa0-x231.google.com [IPv6:2607:f8b0:4003:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2D91A01AC for <ietf@ietf.org>; Wed, 16 Apr 2014 11:10:25 -0700 (PDT)
Received: by mail-oa0-f49.google.com with SMTP id o6so12794827oag.36 for <ietf@ietf.org>; Wed, 16 Apr 2014 11:10:22 -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:content-type; bh=ERe2Qla1ANW2OASCXE/AW1GHP9pprMnY55768Xb/xx8=; b=v4Xb1gWYgqL4/vF8UEVaXg1jswGL4uMQ3HZlJ3lzUWsrKX19e2yNtzxr/Dj1XiIppT 68em+bakt+An1VMjwUubiaiZL7l1twUlJsvPVJSbuNJBE2SnajwW9sfVWEhy3gYo0LiO hQ6LOO74ljj/mA5B+J+x32hbIE1jA8TskZ6f9zpXrPdTuvsdSnmDct6OKTNXg6PsxC0X 4XArK+Rt3NRDtFyVSP/AtiRCK5XaGNdnNR6PSxBu12B1o+rToWj6AeHIoyc0OdAtIdNC zGXsFZBgLe1rbkhy4tp6YElgMFUjehzjnMGAoWS0n16DOLa3W8fz24aZ+a8CrpmXjtFL mYTw==
MIME-Version: 1.0
X-Received: by 10.182.153.226 with SMTP id vj2mr7907639obb.26.1397671821903; Wed, 16 Apr 2014 11:10:21 -0700 (PDT)
Received: by 10.182.153.6 with HTTP; Wed, 16 Apr 2014 11:10:21 -0700 (PDT)
Received: by 10.182.153.6 with HTTP; Wed, 16 Apr 2014 11:10:21 -0700 (PDT)
In-Reply-To: <CADDmorQ+ML8oOdkG5OJ4uQj8ufC6K15c4ieXgz=5RtSXPQJZZw@mail.gmail.com>
References: <CADDmorQ+ML8oOdkG5OJ4uQj8ufC6K15c4ieXgz=5RtSXPQJZZw@mail.gmail.com>
Date: Wed, 16 Apr 2014 14:10:21 -0400
Message-ID: <CAPv4CP9nYR=u=MFhup_xWt_GFSQp6rFBwsUV_yWjjwytkWTr-Q@mail.gmail.com>
Subject: Re: SDN and Routing Protocols
From: Scott Brim <scott.brim@gmail.com>
To: Abhishek Verma <abhishekv.verma@gmail.com>
Content-Type: multipart/alternative; boundary=089e013d0dc0750eee04f72cd454
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5c6EI9a-GDzj12XDjXLibLIvWmc
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 18:10:26 -0000

--089e013d0dc0750eee04f72cd454
Content-Type: text/plain; charset=UTF-8

No one answered this?

On Apr 12, 2014 4:20 AM, "Abhishek Verma" <abhishekv.verma@gmail.com> wrote:
>
> Is SDN going to make routing protocols less relevant?

No. SDN is appropriate in some environments but not all.

> as i understand more and more of this technology, there seems to be a
clear trend towards OSPF/ISIS less environments.

Yes but we were already doing this, e.g. with MPLS, before SDN took off.

> Obviously, BGP is still needed if youre talking across AS boundaries.

Yes but inter-domain SDN is also reasonable.

swb

--089e013d0dc0750eee04f72cd454
Content-Type: text/html; charset=UTF-8

<p dir="ltr">No one answered this?</p>
<p dir="ltr">On Apr 12, 2014 4:20 AM, &quot;Abhishek Verma&quot; &lt;<a href="mailto:abhishekv.verma@gmail.com">abhishekv.verma@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; Is SDN going to make routing protocols less relevant? </p>
<p dir="ltr">No. SDN is appropriate in some environments but not all. </p>
<p dir="ltr">&gt; as i understand more and more of this technology, there seems to be a clear trend towards OSPF/ISIS less environments. </p>
<p dir="ltr">Yes but we were already doing this, e.g. with MPLS, before SDN took off.</p>
<p dir="ltr">&gt; Obviously, BGP is still needed if youre talking across AS boundaries. </p>
<p dir="ltr">Yes but inter-domain SDN is also reasonable.</p>
<p dir="ltr">swb</p>

--089e013d0dc0750eee04f72cd454--


From nobody Wed Apr 16 11:24:20 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 403531A0266 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 11:24:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 7UeOVD37kWTk for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 11:24:13 -0700 (PDT)
Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) by ietfa.amsl.com (Postfix) with ESMTP id ACFA61A02AE for <ietf@ietf.org>; Wed, 16 Apr 2014 11:23:54 -0700 (PDT)
Received: by mail-ob0-f182.google.com with SMTP id uz6so12765818obc.41 for <ietf@ietf.org>; Wed, 16 Apr 2014 11:23:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=IP0j6LWV8aSH4C4GEWWQy8mbckWWzdqSjSeOOdKGEng=; b=bsYyUfq7nd6HPAlXysrhQoALpjMXb8FdRzAOZzHZASLJV22X5+h8i78LPVZd/ESJM0 s86aDS2PiB8Ro8E4TekufBizcZwR+GeHklvQQTVnnlqUifUNFRGOTCS/LK7HsfkDcadO awVj7Urar3DPfhF5DFhKovhQfnbkLr91oe1gQ=
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:content-type; bh=IP0j6LWV8aSH4C4GEWWQy8mbckWWzdqSjSeOOdKGEng=; b=LkCvuejAcRcg+upVvndUQjU/PgEoHg1uocH+CzYhNcP0LdTcv5cum6SuzfPgn+7IUE zpKCoUU2Pxcz7+syxRVfJvBRU9ik7SBRjbT9XSJ2NOSAuP7FB9i6VHWcibPsx5LDkPxp WqH5uY80wHo9rOBP7397/LYydRmO40zrYgcrAXIVLthmDwDvEwDP0qfvYMfEGib3i6vz iMuj7+8ZTBmW5bRjQ1kYWw6R6Vh4dofQUZPGwOPHvMSlDO0AHU6886C5ONrXawm/1b5R 7noZCtPaLIKSyR9JK9FjvaWaylkrZ1KD6WdMIeUW+jpGRE74csTAhzmDtrm79/aI46OH 6K9w==
X-Gm-Message-State: ALoCoQli+fkBihB5+muCE3vEA6KQFX1Svci8wl0RDchaoPnQFnQbOsGVQvfrjt2t2TqxqExG+aa+
MIME-Version: 1.0
X-Received: by 10.182.85.193 with SMTP id j1mr3251605obz.52.1397672631173; Wed, 16 Apr 2014 11:23:51 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Wed, 16 Apr 2014 11:23:51 -0700 (PDT)
In-Reply-To: <6.2.5.6.2.20140415222043.0cc1b818@elandnews.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com> <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.gmail.com> <6.2.5.6.2.20140415111633.0da3d030@resistor.net> <CE39F90A45FF0C49A1EA229FC9899B0507D4749E@USCLES544.agna.amgreetings.com> <6.2.5.6.2.20140415133648.0df89818@elandnews.com> <CE39F90A45FF0C49A1EA229FC9899B0507D47986@USCLES544.agna.amgreetings.com> <6.2.5.6.2.20140415222043.0cc1b818@elandnews.com>
Date: Wed, 16 Apr 2014 19:23:51 +0100
Message-ID: <CAKHUCzwWHSSHe3-17D4aG=RbJUZOCujmm-Q8WxO657S3bpnK3g@mail.gmail.com>
Subject: Re: Let's talk (was: DMARC: perspectives from a listadmin of large open-source lists)
From: Dave Cridland <dave@cridland.net>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=089e01229a12b2330904f72d047d
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FNrzr3mNBT-bDDdPHVDKl8jyxbg
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 18:24:18 -0000

--089e01229a12b2330904f72d047d
Content-Type: text/plain; charset=UTF-8

On 16 April 2014 18:26, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Speaking about career enhancing moves, common sense dictates that it is to
> be assumed that the individual is the mouthpiece of the organization (I am
> not inferring that you are).  In my opinion reviews from individuals
> affiliated with the companies listed on the web page might not fit within
> the objectivity guidelines.  It may be difficult to find an external
> reviewer if Dave Cridland does not wish to donate his intellectual property
> rights.
>

I'm actually quite happy donating IPR; I do it all the time. The XSF policy
on copyright is an assignment one, for example.

I have no idea what the IPR policy is for DMARC, it has been developed
outside the IETF process, and changes to it from the IETF are not welcome.

So from my perspective, it's like saying "Hey, we'd like you to spend time
and effort on reviewing this so we can tell you why we're not going to make
any changes".

Dave.

--089e01229a12b2330904f72d047d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
6 April 2014 18:26, S Moonesamy <span dir=3D"ltr">&lt;<a href=3D"mailto:sm+=
ietf@elandsys.com" target=3D"_blank">sm+ietf@elandsys.com</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">
Speaking about career enhancing moves, common sense dictates that it is to =
be assumed that the individual is the mouthpiece of the organization (I am =
not inferring that you are). =C2=A0In my opinion reviews from individuals a=
ffiliated with the companies listed on the web page might not fit within th=
e objectivity guidelines. =C2=A0It may be difficult to find an external rev=
iewer if Dave Cridland does not wish to donate his intellectual property ri=
ghts.<br>
</blockquote><div><br></div><div>I&#39;m actually quite happy donating IPR;=
 I do it all the time. The XSF policy on copyright is an assignment one, fo=
r example.</div><div><br></div><div>I have no idea what the IPR policy is f=
or DMARC, it has been developed outside the IETF process, and changes to it=
 from the IETF are not welcome.</div>
<div><br></div><div>So from my perspective, it&#39;s like saying &quot;Hey,=
 we&#39;d like you to spend time and effort on reviewing this so we can tel=
l you why we&#39;re not going to make any changes&quot;.</div><div><br>
</div><div>Dave.</div></div></div></div>

--089e01229a12b2330904f72d047d--


From nobody Wed Apr 16 11:41:31 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D96F81A0277 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 11:41:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_14=0.6, SPF_PASS=-0.001] autolearn=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 19pKkxGH4h3i for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 11:41:24 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 6EC761A0227 for <ietf@ietf.org>; Wed, 16 Apr 2014 11:41:24 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id x48so11400197wes.10 for <ietf@ietf.org>; Wed, 16 Apr 2014 11:41:20 -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:content-type; bh=bnzYhLMdeXU10WcP0+1DkYc3NCA4A5pxj1ys7FoEtV0=; b=dX4E++5T6cWOIpD7oKF3Numx7n+qowQxV0GqHSpOaQaCOYhhfNdE+IbpNa8Ugvqsyq YV41ZF86+mbbO+eELzAHaLkLVNdBEwo8eTha4d0NpfrM6ZQvH/C3wQnRoQLYfcuCvXfW anBGCMZao5z7gGKyIPLhqDvDUf/o4oF5ooXYnec3UhUGL1kBkgEM6eXL42CAxXFfymLR SuEKQJSapaFK/sG7NtalT5Fnw4ZP+6KM6t2e42JY4IZBftF7yUhAnOJSsnECG+CcKhQJ 704nHu2TR/Ij6g8g7JyHZV/yg7YuMwyLXQYLxnU2wv/Frv77wmXCrPg3j34U9gQnIauo zRow==
MIME-Version: 1.0
X-Received: by 10.194.109.227 with SMTP id hv3mr8539264wjb.10.1397673680596; Wed, 16 Apr 2014 11:41:20 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Wed, 16 Apr 2014 11:41:20 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1404151832460.38826@joyce.lan>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan>
Date: Wed, 16 Apr 2014 11:41:20 -0700
Message-ID: <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com>
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=089e0102ee283e73fb04f72d436f
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kAMAmwHITR2hYy9hgksHEmvMoro
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 18:41:28 -0000

--089e0102ee283e73fb04f72d436f
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 15, 2014 at 7:18 PM, John R Levine <johnl@taugh.com> wrote:

> The reason it's not special is that it's just the most visible example of
> a wide variety of legitimate useful mail that DMARC can't describe, and
> that are broken by DMARC policies other than p=none.
>

As I see it, this is probably the core of the stalemate.  I agree that
DMARC, and its various antecedents that we all know and love, can't
precisely describe mailing list traffic as it's currently defined.  What I
observe, though, is that there's typically lots of talk about what we can't
do to add that capability, and almost none about what's actually possible.
People get discouraged and give up.  This isn't a path to success.

I'm all for being as incremental and non-destructive as possible when
building these things.  I also don't think it's possible to be completely
invisible 100% of the time.

Sure, whitelisting is one possible solution.  Publishing a whitelist is
easy, but populating it, managing it, making it robust, making it fair, and
protecting it against fraudulent entries needs to be sorted out, whether
it's a public whitelist or a private one.  Are we certain, though, that
it's flatly impossible to adjust lists in such a way that their traffic
could be described by these mechanisms?

-MSK

--089e0102ee283e73fb04f72d436f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Apr 15, 2014 at 7:18 PM, John R Levine <span dir=
=3D"ltr">&lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@tau=
gh.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The reason it&#39;s not special is that it&#=
39;s just the most visible example of a wide variety of legitimate useful m=
ail that DMARC can&#39;t describe, and that are broken by DMARC policies ot=
her than p=3Dnone.<br>
</blockquote><div><br></div><div>As I see it, this is probably the core of =
the stalemate.=C2=A0 I agree that DMARC, and its various antecedents that w=
e all know and love, can&#39;t precisely describe mailing list traffic as i=
t&#39;s currently defined.=C2=A0 What I observe, though, is that there&#39;=
s typically lots of talk about what we can&#39;t do to add that capability,=
 and almost none about what&#39;s actually possible.=C2=A0 People get disco=
uraged and give up.=C2=A0 This isn&#39;t a path to success.<br>
<br></div><div>I&#39;m all for being as incremental and non-destructive as =
possible when building these things.=C2=A0 I also don&#39;t think it&#39;s =
possible to be completely invisible 100% of the time.<br></div><div><br>Sur=
e, whitelisting is one possible solution.=C2=A0 Publishing a whitelist is e=
asy, but populating it, managing it, making it robust, making it fair, and =
protecting it against fraudulent entries needs to be sorted out, whether it=
&#39;s a public whitelist or a private one.=C2=A0 Are we certain, though, t=
hat it&#39;s flatly impossible to adjust lists in such a way that their tra=
ffic could be described by these mechanisms?<br>
<br>-MSK</div></div><br></div></div>

--089e0102ee283e73fb04f72d436f--


From nobody Wed Apr 16 12:01:29 2014
Return-Path: <fenton@bluepopcorn.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5BB1A02D8 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 12:01:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 eiADZsasv7kg for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 12:01:21 -0700 (PDT)
Received: from v2.bluepopcorn.net (v2.bluepopcorn.net [IPv6:2607:f2f8:a994::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0DEB91A036B for <ietf@ietf.org>; Wed, 16 Apr 2014 12:01:16 -0700 (PDT)
Received: from splunge.local (c-50-136-244-117.hsd1.ca.comcast.net [50.136.244.117]) (authenticated bits=0) by v2.bluepopcorn.net (8.14.3/8.14.3/Debian-9.4) with ESMTP id s3GJ1AUh021919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 16 Apr 2014 12:01:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=bluepopcorn.net; s=supersize; t=1397674871; bh=CiGr6dBpwrkOlHfqrEZjWHCTakd4SaiWOlcCcne6358=; h=Message-ID:Date:From:MIME-Version:To:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=BFsHu/nxo8CGV1lFHAj0ZtC1CuW+LJHXXJ8pw/vVUebQfLL0BxaO1AeVH+XCyB6F1 Dzh0oCAcPWoWicejrgkS81TgcUu0HkSPGIVHgyVW0p2rhs/5+71CyCtgHb7Mgy00pm prZL6bz+nFlPCJXiwM41SrI9tj52QYeOnP1FXP9k=
Message-ID: <534ED376.8060303@bluepopcorn.net>
Date: Wed, 16 Apr 2014 12:01:10 -0700
From: Jim Fenton <fenton@bluepopcorn.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com>
In-Reply-To: <534D98CC.9080400@gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eLBQxDTbAzVVfvXAGIc7SCEB9bI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 19:01:27 -0000

On 4/15/14 1:38 PM, Brian E Carpenter wrote:
> 
> The mailman fix is worse than the disease. I think the .INVALID fix is
> much better, because Reply-all will still work.
> 

>From the latest DMARC draft, section 8:

"If the RFC5322.From domain does not exist in the DNS, Mail Receivers
SHOULD direct the receiving SMTP server to reject the message."

So if a receiver that is implementing DMARC is faithful to the draft,
that won't work very well (nobody has gotten a TLD allocation for
.invalid, I hope?)

-Jim


From nobody Wed Apr 16 12:58:35 2014
Return-Path: <wes@mti-systems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E5271A030B for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 12:58:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.553
X-Spam-Level: 
X-Spam-Status: No, score=-0.553 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347] autolearn=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 oTWhCAB8b1rb for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 12:58:27 -0700 (PDT)
Received: from atl4mhob17.myregisteredsite.com (atl4mhob17.myregisteredsite.com [209.17.115.110]) by ietfa.amsl.com (Postfix) with ESMTP id 4727B1A030A for <ietf@ietf.org>; Wed, 16 Apr 2014 12:58:21 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob17.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s3GJwAf1003958 for <ietf@ietf.org>; Wed, 16 Apr 2014 15:58:10 -0400
Received: (qmail 5314 invoked by uid 0); 16 Apr 2014 19:58:07 -0000
X-TCPREMOTEIP: 107.47.163.91
X-Authenticated-UID: wes@mti-systems.com
Received: from unknown (HELO ?192.168.43.65?) (wes@mti-systems.com@107.47.163.91) by 0 with ESMTPA; 16 Apr 2014 19:58:05 -0000
Message-ID: <534EE0B9.8080709@mti-systems.com>
Date: Wed, 16 Apr 2014 15:57:45 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Call for Review of draft-iab-cc-workshop-report-01, "Report from the IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communication"
References: <F83C2EAE-6E47-40D2-AFCF-3FEC377E3973@iab.org>
In-Reply-To: <F83C2EAE-6E47-40D2-AFCF-3FEC377E3973@iab.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7IJL1N_XEL1kJWP3K7gcYgX2Ik4
Cc: IAB <iab@iab.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 19:58:31 -0000

On 4/16/2014 11:45 AM, IAB Chair wrote:
> This is a call for review of "Report from the IAB/IRTF Workshop on Congestion Control for Interactive Real-Time Communication" prior to potential approval as an IAB stream RFC.
> 
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-cc-workshop-report/
> 
> The Call for Review will last until 14 May 2014.  Please send comments to iab@iab.org. 
> 


The draft mentions that the RMCAT WG was subsequently formed, but
should also mention that the AQM WG was also subsequently formed,
as AQM and "network infrastructure" improvements to deal with
bufferbloat are mentioned multiple times.  It took a couple more
meeting cycles, but the issues and topics discussed in this workshop
had a big role in getting that WG started.

Otherwise, I don't have any major concerns with this, and it looks
pretty good.

-- 
Wes Eddy
MTI Systems


From nobody Wed Apr 16 13:01:18 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A14121A030E for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 p7SnCaRoeuFS for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:01:08 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4CDB91A02F3 for <ietf@ietf.org>; Wed, 16 Apr 2014 13:01:08 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wn1so5471537obc.32 for <ietf@ietf.org>; Wed, 16 Apr 2014 13:01:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=dSb2mvHB+ExvIgUfSl7heIhGwwVUOA4TXtXJsA9RUD0=; b=eMPTZKTkp1+9ZxweRoVI/CTS1OwGtfRJJJubCIU5vbq2aKqdGv2YQ3PXqnwuiqMn1d g+hJ82hKC6kEL6fsCV9IxPZ21DTGkPwVHfWnHA8xles+Ph75y7LKhXs09RdJbpw2THuZ B8zQHS2BAkIMYvq1hsqW7zZoiInd6RLsLzoLM=
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:content-type; bh=dSb2mvHB+ExvIgUfSl7heIhGwwVUOA4TXtXJsA9RUD0=; b=egj1TMnaXab5CjG+jnrmgsVSHwgM1qlBn41DEw/vLSBOe8LvXLJoyyX7/48f9zCVR3 fI9Ri13llRCRnhffRdKHsY03ATh13GDPFrLlxAXvEWDOFLpKDDWBfg5bOiXZzu69fbJP Ado2aPdoZdt35gBRpApjyFl561zX4IPZei226xrojGM8OMVO8a4cibIw9z6yE0P3C9YQ +5kcy3gYRQ/pW/blCUE0vissopEvCu24wuWk0B9KdDsvhdE8f1QSK5iKhksh/FM1tJxN BOO2ckBgxso2fQ6o9ByKK7KZfQP36pfsfpsRdpww8Ml0PbgOZxoMygHmuG75Y6AWVgq9 EE3g==
X-Gm-Message-State: ALoCoQlZZKV9Q52jIXz4+WpHlhC1JRasoApZ5SjVWCIl0CF9w7QnRjDmjExQBMCyGVArJG+O0khr
MIME-Version: 1.0
X-Received: by 10.183.1.34 with SMTP id bd2mr8354666obd.4.1397678465029; Wed, 16 Apr 2014 13:01:05 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Wed, 16 Apr 2014 13:01:04 -0700 (PDT)
In-Reply-To: <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com>
Date: Wed, 16 Apr 2014 21:01:04 +0100
Message-ID: <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com>
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: Dave Cridland <dave@cridland.net>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=001a1134acc26b2aef04f72e60c3
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4AdlOdXXGRSGbIYGqUCuajMZcww
Cc: John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 20:01:14 -0000

--001a1134acc26b2aef04f72e60c3
Content-Type: text/plain; charset=UTF-8

On 16 April 2014 19:41, Murray S. Kucherawy <superuser@gmail.com> wrote:

> whitelist or a private one.  Are we certain, though, that it's flatly
> impossible to adjust lists in such a way that their traffic could be
> described by these mechanisms?
>
>
If you mean, can we change mailing lists such that they're describable by
DMARC without any change in behaviour, whilst maintaining the essential
premises of mailing lists, then I don't see a mechanism that would allow
this.

If you mean, can we change DMARC (such that existing deployments will have
to change) such that a modified mailing list model (that handles the
existing use cases of mailing lists) would be describable, then I think
that's entirely possible.

Unfortunately, the only option I thought was possibly available isn't
permissible by the specification - therefore, the only solution involves
alterations to the deployed base, which has been ruled impossible for over
a year now.

Dave.

--001a1134acc26b2aef04f72e60c3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
6 April 2014 19:41, Murray S. Kucherawy <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:superuser@gmail.com" target=3D"_blank">superuser@gmail.com</a>&gt;</sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"">whitelist o=
r a private one.=C2=A0 Are we certain, though, that it&#39;s flatly impossi=
ble to adjust lists in such a way that their traffic could be described by =
these mechanisms?<br>
</div><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div><br></div>=
</div></div></div></blockquote><div><br></div><div>If you mean, can we chan=
ge mailing lists such that they&#39;re describable by DMARC without any cha=
nge in behaviour, whilst maintaining the essential premises of mailing list=
s, then I don&#39;t see a mechanism that would allow this.</div>
<div><br></div><div>If you mean, can we change DMARC (such that existing de=
ployments will have to change) such that a modified mailing list model (tha=
t handles the existing use cases of mailing lists) would be describable, th=
en I think that&#39;s entirely possible.</div>
<div><br></div><div>Unfortunately, the only option I thought was possibly a=
vailable isn&#39;t permissible by the specification - therefore, the only s=
olution involves alterations to the deployed base, which has been ruled imp=
ossible for over a year now.</div>
<div><br></div><div>Dave.</div></div></div></div>

--001a1134acc26b2aef04f72e60c3--


From nobody Wed Apr 16 13:21:59 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 739411A02CA for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:21:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 mJn1oG6TcX0E for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:21:53 -0700 (PDT)
Received: from mail-pd0-x22d.google.com (mail-pd0-x22d.google.com [IPv6:2607:f8b0:400e:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id D75741A02AF for <ietf@ietf.org>; Wed, 16 Apr 2014 13:21:53 -0700 (PDT)
Received: by mail-pd0-f173.google.com with SMTP id z10so11172590pdj.32 for <ietf@ietf.org>; Wed, 16 Apr 2014 13:21:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ZH4L583OmxNWS36mQ1MNmu89f+KkyXeDmzmanSdfv7Q=; b=XxgjnpGRlqX1cedYiqzW+N1wMc1EVBaUqIzwlVqinZ3RCeXh2Zf62Z0FXbUChD68Z7 wo57LggUMg/FYpN3Z1kordNjwrq5KOozs2DN7K5PVOQXkyEYk/axR4yV8D304ekBAuro i9Cb5EnfHQ7JiTZU0bIfo/pzGM73vBON0TITY7jLrDVmIpNGRRCAqDl/8FNauM2vgk0J UaHyKxWMrX8ck7Kvmq4BFytTIilJc4z1mx3Fddf8/Hm17hN9a8gnrBw3DBTFAq0n9+dY J27e7Np9CgveAyeoPWoW/ncNWVACa0berQUVgIf3Agkjb08rBKj7dOYVrvcp6oFMeemY kVvw==
X-Received: by 10.68.181.165 with SMTP id dx5mr10986555pbc.38.1397679710547; Wed, 16 Apr 2014 13:21:50 -0700 (PDT)
Received: from [192.168.178.20] (198.197.69.111.dynamic.snap.net.nz. [111.69.197.198]) by mx.google.com with ESMTPSA id qv9sm41923498pbc.71.2014.04.16.13.21.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 13:21:49 -0700 (PDT)
Message-ID: <534EE65A.9020602@gmail.com>
Date: Thu, 17 Apr 2014 08:21:46 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <534E8D3B.7080705@mti-systems.com> <33D51F54-A5A6-42F2-90EC-FE09783BB5A2@thomasclausen.org> <534EA296.20900@gmail.com>
In-Reply-To: <534EA296.20900@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hvP7L0gvv4vIGsmkCOEOKkrFcnQ
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 20:21:55 -0000

On 17/04/2014 03:32, Melinda Shore wrote:
...
> I'm not sure that the IETF should get more directly
> involved with supporting implementation efforts but I
> do think that we should recognize that work coming
> in that's already been implemented tends to be more
> fully-baked and privilege that in some way.  One worries
> about that encouraging crappy implementation, but I'm
> not sure that crappy implementation is much worse than
> no implementation.

I don't think we should privilege it particularly. We have at
least 3 modes of working, each of which has its value:

1. Preemptive standardisation: problem statement first,
then requirements, then design, then standardise, then sit
back and wait for implementation.

2. Parallel standardisation: there's some design work and
maybe some code, then retro-fit requirements, write the specs
as the code evolves, then standardise and hope that the code is
updated to match the spec.

3. Retroactive standardisation: there's some running code that
got itself deployed; write the v1 spec to be compatible with
the code, call it a standard, then develop v1.1 or v2 and
hope the code is updated.

We've done all three, and all with varying degrees of success.
I could give examples, but that would just start arguments ;-).
It isn't reasonable to expect all standards to fit the same
model. And people who don't have the desire to work in any
of these models may well prefer to quit standards work (but
still contribute code to one of the three models).

    Brian


From nobody Wed Apr 16 13:37:49 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7CC51A02E8 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:37:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 s0oLE4kg_xUv for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:37:46 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 285611A027F for <ietf@ietf.org>; Wed, 16 Apr 2014 13:37:46 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id kl14so11376250pab.32 for <ietf@ietf.org>; Wed, 16 Apr 2014 13:37:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FRF9QlMYQiWgh76e1YDJ4BL2oDs3B5uC6d7xBaKHGGQ=; b=FlgfM2X8F5dgAvYef/G/aCdTwNRUJwDSFemgyg7n/aGZRqlZE8lxUQHXCZ8zWI5vOK hyYHeYLu4Nyt2R+LCaD9KqqyIUONR1xUe0clzxMWYaWsRqj4vjNRxeh1jwxi0tSMZGNv /Y+wv0MJLmxkxZKwZ/qWvIEo1Pbg/MecCa5RcjM675ApnT8nM8qdyNU89r6izSM8pQnz YQkT/PtxdK7voL1+FOs+jzDZpL5o4QUF6oqLYGSAcUSho9xv3QlNf9J8/GbwTLX05CnZ wk/94T9mkye7mbAzjoENvXd8pQ9LR3NBirB91Z1BD/6wOBwKE5l2hulN4Gl2+PGXVZqu qa+g==
X-Received: by 10.67.1.39 with SMTP id bd7mr11033015pad.15.1397680663021; Wed, 16 Apr 2014 13:37:43 -0700 (PDT)
Received: from [192.168.178.20] (198.197.69.111.dynamic.snap.net.nz. [111.69.197.198]) by mx.google.com with ESMTPSA id ek2sm48901519pbd.30.2014.04.16.13.36.52 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 13:36:53 -0700 (PDT)
Message-ID: <534EE9EA.9060403@gmail.com>
Date: Thu, 17 Apr 2014 08:36:58 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Sabahattin Gucukoglu <listsebby@me.com>,  Jim Fenton <fenton@bluepopcorn.net>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <2478F2D1-2E08-45D7-86A2-36443959E272@me.com>
In-Reply-To: <2478F2D1-2E08-45D7-86A2-36443959E272@me.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UcBTq5B4ItUVZqRzkIkgh-5P8RA
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 20:37:47 -0000

On 16/04/2014 18:58, Sabahattin Gucukoglu wrote:
> On 15 Apr 2014, at 21:38, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> The mailman fix is worse than the disease. I think the .INVALID fix is
>> much better, because Reply-all will still work.
> 
> Reply-all should still work with the Mailman fix; 

It doesn't work *properly*. Firstly, this message wouldn't be sent
to you with CC to the list, which is the correct semantic.
If you weren't a subscriber, you would never see it. Secondly,
the first line above would read:

 On 16/04/2014 18:58, IETF discussion list wrote:

which is untrue.

On 17/04/2014 07:01, Jim Fenton wrote:
...
>>From the latest DMARC draft, section 8:
> 
> "If the RFC5322.From domain does not exist in the DNS, Mail Receivers
> SHOULD direct the receiving SMTP server to reject the message."
> 
> So if a receiver that is implementing DMARC is faithful to the draft,
> that won't work very well (nobody has gotten a TLD allocation for
> .invalid, I hope?)

DMARC isn't a standard, though, so standards-compliant mail receivers
shouldn't be implementing it. And that particular rule seems completely
out of place even if DMARC was a standard.

    Brian


From nobody Wed Apr 16 13:38:36 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BEE041A02CF for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:38:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.178
X-Spam-Level: 
X-Spam-Status: No, score=-0.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 zYaviA2z6GLg for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:38:30 -0700 (PDT)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id DDA3B1A0286 for <ietf@ietf.org>; Wed, 16 Apr 2014 13:38:29 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id gq1so3106150obb.40 for <ietf@ietf.org>; Wed, 16 Apr 2014 13:38:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=uN8scRpVelamP1G8MGECs85u6bzB+Hg/07AkZp5mCZY=; b=Hkn4NFH6PxAWiFZRSd+A8Cm9huvznG5+cCvUfHxhf9aKd7+oBGJpdXvEwMxPHW7xqg N94meYJ5gTF/oV+i1Y75gRyGqouwSBv7JwyFXxWCjRhvjvUmSacgNgup7VK/7J4zfp8i UHdLiNvF9XeAlw7C6kF/oOYBw9gPWsab4Ot6c=
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:content-type; bh=uN8scRpVelamP1G8MGECs85u6bzB+Hg/07AkZp5mCZY=; b=Yh/RnyxAYPHN5nkqk1iFOioH3tI0D6sqeXdjrsRU6PTqdla7IQQrd2Y8W23NOwyJbS A4xG8jjurCmt+6v8gzZ5t9ULA3Wc6NMuqZdtTE1CV8uQ9zmroyVAgl3E49KAEYjiyore Qsk4tmzuu1MB+9jfXenoybMt+Ir1ApnL7o0JcNsXKsiyaBtu4Bi5zgFetaML6Q1XbB1f d2Q+a29fOgJ4Bo3E4c7siQirgnTEanVrgw6H2i9Rki1Qi7c2tzRzlFQXIUtdxWbQcjBU le607/20FbENTybjNK9ELFu1sH0qxf1VnMUHjzbzMMSSbMancA6o5H9xFHu3/dsblr/s sQNA==
X-Gm-Message-State: ALoCoQlup3cH+xhzQxsDZ81KlRtIGq/cWi1IeUaQcGsMOYZyRTWg1M9OR/QN4PxujCsNIs8KoHXT
MIME-Version: 1.0
X-Received: by 10.60.157.202 with SMTP id wo10mr8399902oeb.9.1397680706373; Wed, 16 Apr 2014 13:38:26 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Wed, 16 Apr 2014 13:38:26 -0700 (PDT)
In-Reply-To: <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com>
Date: Wed, 16 Apr 2014 21:38:26 +0100
Message-ID: <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com>
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: Dave Cridland <dave@cridland.net>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd6c5e803980604f72ee6ce
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-BtC2GAnVo4s8AYscFM2rktPDJ4
Cc: John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 20:38:33 -0000

--047d7bd6c5e803980604f72ee6ce
Content-Type: text/plain; charset=UTF-8

On 16 April 2014 21:01, Dave Cridland <dave@cridland.net> wrote:

> Unfortunately, the only option I thought was possibly available isn't
> permissible by the specification - therefore, the only solution involves
> alterations to the deployed base, which has been ruled impossible for over
> a year now.
>
>
Oh, I tell a lie, it's just not where I expected, and not quite as nice as
I'd hoped.

So I think what needs to happen is that a new policy of "sender-reject" or
something is allowed, which is essentially deferring to the sender, so
receivers would check:

1) The sender exists and is valid.

2) The mail has a valid DKIM signature from the sender and otherwise
complies with the published DMARC policy.

3) Any such policy is treated as p=reject

That is, if I have a mailing list at "ietf@ietf.org", and a
p=forward-or-reject then my recipients would check for a _dmarc.ietf.org as
well, but ignore any p=, and treat as p=reject.

This means that mailing lists (and other forwarding cases) are enforced
into having DMARC records in order to forward DMARC originating messages,
which seems reasonable, and the Sender addresses must also be relatively
sensible, which they normally are already.

In fact, this case handles even people using gmail.com with their Yahoo
address sending messages to mailing lists, I think.

Note that the problem is that existing DMARC deployments which don't know
about sender-reject will either treat is as p=none - if there's a rua
listed - or "take no action", and I've not looked into this enough to
decide what that means.

So for Yahoo, should they implement this change, would effectively take a
backwards step to p=none until the DMARC deployments caught up, which would
be a little confusing to mailing list operators, but at least safe.

The alternative would be to add a new tag indicating this kind of deferral
to the sender; unknown tags are ignored, so this would behave like a reject
until software was updated. The problem with that is that it'd be very
unpredictable whether messages would pass or not; for mailing lists, which
typically drop subscribers after a certain number of failed deliveries, I
think it'd remain a huge problem.

In either case, there would be a knock-on to UAs, which would need to show
in the UI that the message had been forwarded - gmail does this with it's
"via", for example, so I don't think this is onerous.

I may be missing something.

Dave.

--047d7bd6c5e803980604f72ee6ce
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
6 April 2014 21:01, Dave Cridland <span dir=3D"ltr">&lt;<a href=3D"mailto:d=
ave@cridland.net" target=3D"_blank">dave@cridland.net</a>&gt;</span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
 class=3D"">Unfortunately, the only option I thought was possibly available=
 isn&#39;t permissible by the specification - therefore, the only solution =
involves alterations to the deployed base, which has been ruled impossible =
for over a year now.<br>
</div><span class=3D"HOEnZb"><font color=3D"#888888">
<div><br></div></font></span></div></div></div></blockquote><div><br></div>=
<div>Oh, I tell a lie, it&#39;s just not where I expected, and not quite as=
 nice as I&#39;d hoped.</div><div><br></div><div>So I think what needs to h=
appen is that a new policy of &quot;sender-reject&quot; or something is all=
owed, which is essentially deferring to the sender, so receivers would chec=
k:</div>
<div><br></div><div>1) The sender exists and is valid.</div><div><br></div>=
<div>2) The mail has a valid DKIM signature from the sender and otherwise c=
omplies with the published DMARC policy.</div><div><br></div><div>3) Any su=
ch policy is treated as p=3Dreject</div>
<div><br></div><div>That is, if I have a mailing list at &quot;<a href=3D"m=
ailto:ietf@ietf.org">ietf@ietf.org</a>&quot;, and a p=3Dforward-or-reject t=
hen my recipients would check for a _<a href=3D"http://dmarc.ietf.org">dmar=
c.ietf.org</a> as well, but ignore any p=3D, and treat as p=3Dreject.</div>
<div><br></div><div>This means that mailing lists (and other forwarding cas=
es) are enforced into having DMARC records in order to forward DMARC origin=
ating messages, which seems reasonable, and the Sender addresses must also =
be relatively sensible, which they normally are already.</div>
<div><br></div><div>In fact, this case handles even people using <a href=3D=
"http://gmail.com">gmail.com</a> with their Yahoo address sending messages =
to mailing lists, I think.</div><div><br></div><div>Note that the problem i=
s that existing DMARC deployments which don&#39;t know about sender-reject =
will either treat is as p=3Dnone - if there&#39;s a rua listed - or &quot;t=
ake no action&quot;, and I&#39;ve not looked into this enough to decide wha=
t that means.</div>
<div><br></div><div>So for Yahoo, should they implement this change, would =
effectively take a backwards step to p=3Dnone until the DMARC deployments c=
aught up, which would be a little confusing to mailing list operators, but =
at least safe.</div>
<div><br></div><div>The alternative would be to add a new tag indicating th=
is kind of deferral to the sender; unknown tags are ignored, so this would =
behave like a reject until software was updated. The problem with that is t=
hat it&#39;d be very unpredictable whether messages would pass or not; for =
mailing lists, which typically drop subscribers after a certain number of f=
ailed deliveries, I think it&#39;d remain a huge problem.</div>
<div><br></div><div>In either case, there would be a knock-on to UAs, which=
 would need to show in the UI that the message had been forwarded - gmail d=
oes this with it&#39;s &quot;via&quot;, for example, so I don&#39;t think t=
his is onerous.</div>
<div><br></div><div>I may be missing something.</div><div><br></div><div>Da=
ve.</div></div></div></div>

--047d7bd6c5e803980604f72ee6ce--


From nobody Wed Apr 16 13:44:52 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F67D1A0276 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:44:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 sGsCdz5J2iYu for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:44:43 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.31]) by ietfa.amsl.com (Postfix) with ESMTP id 7DB5F1A0347 for <ietf@ietf.org>; Wed, 16 Apr 2014 13:44:42 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES533.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Wed, 16 Apr 2014 16:44:39 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Dave Cridland <dave@cridland.net>, S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: Let's talk (was: DMARC: perspectives from a listadmin of large open-source lists)
Thread-Topic: Let's talk (was: DMARC: perspectives from a listadmin of large open-source lists)
Thread-Index: AQHPWaEY2trL5momxkq2TKj1OtwyKZsUp2qQ
Date: Wed, 16 Apr 2014 20:44:37 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D485AE@USCLES544.agna.amgreetings.com>
References: <20140414024956.26078.qmail@joyce.lan> <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com>	<534B9760.90301@dougbarton.us> <534BFA0D.7000404@meetinghouse.net> <CAL0qLwZdOORfasExjyc9BHDMYwR_gUk7NRiE7KFBWUC2Hae9jg@mail.gmail.com> <CAKHUCzz8Uuq_8ErsbdTA04uTihqNHAU2E_c+dUyNrVi2r3mtJw@mail.gmail.com> <CAL0qLwZ1P8r0CF+8LL3ewEcA7Rmn1W9u2FZUsuBykAcQzOy7oQ@mail.gmail.com> <CAKHUCzz9g+x0NuMUMKZR5tqn3NVWMS4E-2Di4KL0dJbk1XkKAw@mail.gmail.com> <CAL0qLwYu0AO=RTqJ+eazjB+YCARrtLo=pS6vYHSPKUc_LrxAwg@mail.gmail.com> <CAKHUCzxqrLkAjFgghZnf+SDAFYH_YMS6WR4r9jOm4yErXEFLXQ@mail.gmail.com> <6.2.5.6.2.20140415111633.0da3d030@resistor.net> <CE39F90A45FF0C49A1EA229FC9899B0507D4749E@USCLES544.agna.amgreetings.com> <6.2.5.6.2.20140415133648.0df89818@elandnews.com> <CE39F90A45FF0C49A1EA229FC9899B0507D47986@USCLES544.agna.amgreetings.com> <6.2.5.6.2.20140415222043.0cc1b818@elandnews.com> <CAKHUCzwWHSSHe3-17D4aG=RbJUZOCujmm-Q8WxO657S3bpnK3g@mail.gmail.com>
In-Reply-To: <CAKHUCzwWHSSHe3-17D4aG=RbJUZOCujmm-Q8WxO657S3bpnK3g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_CE39F90A45FF0C49A1EA229FC9899B0507D485AEUSCLES544agnaam_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_L33i-v5Pf3GeNPqEX06jVTAmi4
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 20:44:49 -0000

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D485AEUSCLES544agnaam_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCkZyb206IERhdmUgQ3JpZGxhbmQgW21haWx0bzpkYXZlQGNyaWRsYW5kLm5ldF0NClNlbnQ6
IFdlZG5lc2RheSwgQXByaWwgMTYsIDIwMTQgMjoyNCBQTQ0KVG86IFMgTW9vbmVzYW15DQpDYzog
TUggTWljaGFlbCBIYW1tZXIgKDUzMDQpOyBpZXRmQGlldGYub3JnIERpc2N1c3Npb24NClN1Ympl
Y3Q6IFJlOiBMZXQncyB0YWxrICh3YXM6IERNQVJDOiBwZXJzcGVjdGl2ZXMgZnJvbSBhIGxpc3Rh
ZG1pbiBvZiBsYXJnZSBvcGVuLXNvdXJjZSBsaXN0cykNCg0KT24gMTYgQXByaWwgMjAxNCAxODoy
NiwgUyBNb29uZXNhbXkgPHNtK2lldGZAZWxhbmRzeXMuY29tPG1haWx0bzpzbStpZXRmQGVsYW5k
c3lzLmNvbT4+IHdyb3RlOg0KU3BlYWtpbmcgYWJvdXQgY2FyZWVyIGVuaGFuY2luZyBtb3Zlcywg
Y29tbW9uIHNlbnNlIGRpY3RhdGVzIHRoYXQgaXQgaXMgdG8gYmUgYXNzdW1lZCB0aGF0IHRoZSBp
bmRpdmlkdWFsIGlzIHRoZSBtb3V0aHBpZWNlIG9mIHRoZSBvcmdhbml6YXRpb24gKEkgYW0gbm90
IGluZmVycmluZyB0aGF0IHlvdSBhcmUpLiAgSW4gbXkgb3BpbmlvbiByZXZpZXdzIGZyb20gaW5k
aXZpZHVhbHMgYWZmaWxpYXRlZCB3aXRoIHRoZSBjb21wYW5pZXMgbGlzdGVkIG9uIHRoZSB3ZWIg
cGFnZSBtaWdodCBub3QgZml0IHdpdGhpbiB0aGUgb2JqZWN0aXZpdHkgZ3VpZGVsaW5lcy4gIEl0
IG1heSBiZSBkaWZmaWN1bHQgdG8gZmluZCBhbiBleHRlcm5hbCByZXZpZXdlciBpZiBEYXZlIENy
aWRsYW5kIGRvZXMgbm90IHdpc2ggdG8gZG9uYXRlIGhpcyBpbnRlbGxlY3R1YWwgcHJvcGVydHkg
cmlnaHRzLg0KDQpNSDogUmV2aWV3cyBmcm9tIDNyZCBwYXJ0aWVzIGhhdmUgYmVlbiBhbHdheXMg
d2VsY29tZSBhbmQgd2VyZSBzcGVjaWZpY2FsbHkgYXNrZWQgZm9yIGZyb20gYSBudW1iZXIgb2Yg
cGVvcGxlIHVuYWZmaWxpYXRlZCB3aXRoIGRtYXJjLm9yZy4gVGhlcmUgd2VyZSBleHRlcm5hbCBy
ZXZpZXdzIChhbHRob3VnaCBpdCB3b3VsZCBoYXZlIGJlZW4gbmljZSB0byBzZWUgbW9yZSkgZnJv
bSB2YXJpb3VzIHBlb3BsZS4gSSBub3RlIHRoYXQgSmltIEZlbnRvbiBqdXN0IHBvc3RlZCB0byB0
aGUgZG1hcmMtaWV0ZiBsaXN0IGFib3V0IG1hbnkgb2YgaGlzIHN1Z2dlc3Rpb25zIGJlaW5nIGlu
Y29ycG9yYXRlZC4NCg0KV2l0aCByZWdhcmQgdG8gbW91dGhwaWVjZXMsIHRoZXJlIGFyZSBzb21l
IHBlb3BsZSB3aG8gY2xlYXJseSBhcmUgYW5kIG90aGVyIHBlb3BsZSB3aG8gYXJlIG5vdC4gSXTi
gJlzIGdlbmVyYWxseSBub3QgdG9vIGRpZmZpY3VsdCB0byBmaWd1cmUgb3V0IHRoZSBkaWZmZXJl
bmNlIGJldHdlZW4gdGhlIHR3by4NCg0KSSdtIGFjdHVhbGx5IHF1aXRlIGhhcHB5IGRvbmF0aW5n
IElQUjsgSSBkbyBpdCBhbGwgdGhlIHRpbWUuIFRoZSBYU0YgcG9saWN5IG9uIGNvcHlyaWdodCBp
cyBhbiBhc3NpZ25tZW50IG9uZSwgZm9yIGV4YW1wbGUuDQoNCkkgaGF2ZSBubyBpZGVhIHdoYXQg
dGhlIElQUiBwb2xpY3kgaXMgZm9yIERNQVJDLCBpdCBoYXMgYmVlbiBkZXZlbG9wZWQgb3V0c2lk
ZSB0aGUgSUVURiBwcm9jZXNzLCBhbmQgY2hhbmdlcyB0byBpdCBmcm9tIHRoZSBJRVRGIGFyZSBu
b3Qgd2VsY29tZS4NCg0KTUg6IFRoZSBJUFIgcG9saWN5IGZvciBETUFSQyBmYWxscyB1bmRlciB0
aGUgT1dGIOKAkyBBbGwgb2YgdGhlIHBhcnRpY2lwYXRpbmcgb3JnYW5pemF0aW9ucyBoYXZlIHNp
Z25lZCBhZ3JlZW1lbnRzIGZvciB0aGlzLiBBbnlvbmUgY2FuIGNvbnRyaWJ1dGUgYXMgYW4gaW5k
aXZpZHVhbCBidXQgdGhlIHBhcnRpY2lwYXRpbmcgb3JnYW5pemF0aW9ucyBoYXZlIHNwZWNpZmlj
IGNvbnRyYWN0dWFsIG9ibGlnYXRpb25zLiBUaGVyZSBhcmUgbW9yZSBkZXRhaWxzIG9uIHRoZSBP
V0YgYmFzaXMgZm9yIGFueW9uZSBpbnRlcmVzdGVkIGluIHBhcnRpY2lwYXRpbmcgb3IgY29udHJp
YnV0aW5nIHRocm91Z2ggdGhlIGRtYXJjLWRpc2N1c3MgbGlzdCBhdCBodHRwOi8vd3d3LmRtYXJj
Lm9yZy9ub3RlX3dlbGwuaHRtbC4gIENvbnNpZGVyaW5nIHRoYXQgdGhlcmUgd2VyZSBtdWx0aXBs
ZSBhdHRlbXB0cyB0byBoYW5kIHRoZSBETUFSQyBzcGVjIG92ZXIgdG8gdGhlIElFVEYgSSB0aGlu
ayB0aGUgbGFzdCBwYXJ0IG9mIHlvdXIgc3RhdGVtZW50IGlzIGEgc3RyZXRjaC4gVGhlcmUgd2Vy
ZSBjb25zdHJhaW50cy9jb25zaWRlcmF0aW9ucyB0aGF0IEkgdGhpbmsgY291bGQgaGF2ZSBiZWVu
IHdvcmtlZCBvdXQsIGJ1dCBmb3Igbm93IHRoYXQgaXMgd2F0ZXIgdW5kZXIgdGhlIGJyaWRnZS4N
Cg0KU3BlYWtpbmcgb25seSBmb3IgbXlzZWxmIGJlY2F1c2UgSeKAmW0gbm90IGFueSBvbmVzIG1v
dXRocGllY2UsIEkgYmVsaWV2ZSB0aGF0IGFueSBjb250cmlidXRpb25zIHdoaWNoIGltcHJvdmUg
dGhlIHRlY2huaWNhbCByaWdvciBvZiB0aGUgc3BlY2lmaWNhdGlvbiBhcmUgdmFsdWVkIGFuZCBh
cmUgb2YgYmVuZWZpdCB0byB0aGUgY29tbXVuaXR5IGluIHRoZSBsYXJnZXIgc2Vuc2UuIElmIEkg
YmVsaWV2ZWQgb3RoZXJ3aXNlIEkgd291bGQgbm90IGJlIHBhcnRpY2lwYXRpbmcuDQoNClNvIGZy
b20gbXkgcGVyc3BlY3RpdmUsIGl0J3MgbGlrZSBzYXlpbmcgIkhleSwgd2UnZCBsaWtlIHlvdSB0
byBzcGVuZCB0aW1lIGFuZCBlZmZvcnQgb24gcmV2aWV3aW5nIHRoaXMgc28gd2UgY2FuIHRlbGwg
eW91IHdoeSB3ZSdyZSBub3QgZ29pbmcgdG8gbWFrZSBhbnkgY2hhbmdlcyIuDQoNCk1IOiBJIHJl
c3BlY3QgeW91ciBwZXJzcGVjdGl2ZSBEYXZlLiBJIGNhbiBvbmx5IHBvaW50IHRvIHRoZSBleHBl
cmllbmNlIG9mIG90aGVycyB0aGF0IGhhdmUgdGFrZW4gdGhlIHRpbWUgYW5kIGVmZm9ydCBhbmQg
Zm91bmQgdGhlaXIgc3VnZ2VzdGlvbnMgaW5jb3Jwb3JhdGVkLiBCZWNhdXNlIHRoZSBwYXJ0aWNp
cGF0aW5nIG9yZ2FuaXphdGlvbnMgYXJlIGJvdW5kIGJ5IE9XRiBhbmQgdGhlIHBhcnRpY2lwYXRp
b24gYWdyZWVtZW50LCB0aGVyZSBpcyBhbiBvYmxpZ2F0aW9uIHRvIGZvbGxvdyBjZXJ0YWluIHBy
b2Nlc3Nlcy4gSSB3aWxsIHNheSB0aGF0IGZyb20gbXkgcGVyc3BlY3RpdmUgaXQgd2FzIG5ldmVy
IGFudGljaXBhdGVkIHRoYXQgd2Ugd291bGQgYmUgZ29pbmcgdGhpcyBsb25nIHdpdGhvdXQgYSBo
YW5kb2ZmIHRvIElFVEYuIEnigJltIG5vdCBsb29raW5nIHRvIGRlYmF0ZSB3aGV0aGVyIGl0IHNo
b3VsZCBvciBzaG91bGRu4oCZdCBiZSBvciBob3cgaXQgbWlnaHQgYmUgYXQgdGhpcyBwb2ludCwg
SeKAmW0gb25seSB0cnlpbmcgdG8gcHJvdmlkZSBzb21lIHBlcnNwZWN0aXZlIGludG8gd2h5IHRo
ZSBETUFSQyBwcm9jZXNzIGlzIGN1cnJlbnRseSB0aGUgd2F5IGl0IGlzLg0KDQpSZW1lbWJlciAo
dW5kZXJzdGFuZD8pIHRoYXQgdGhpcyAoRE1BUkMpIHN0YXJ0ZWQgYmVjYXVzZSB2YXJpb3VzIHBh
cnRpY2lwYW50cyBoYWQgcHJpdmF0ZSBiaWxhdGVyYWwgYWdyZWVtZW50cyByZWdhcmRpbmcgcG9s
aWN5IGFzc2VydGlvbnMgYW5kIHJlcG9ydGluZy4gV2hlbiBJIGZpcnN0IHN0YXJ0ZWQgd29ya2lu
ZyBvbiBteSBpbXBsZW1lbnRhdGlvbiAoYW5kIG9wZXJhdGlvbmFsIGNoYW5nZXMpIEkgaGFkIHRv
IGFzayB2YXJpb3VzIG1haWxib3ggcHJvdmlkZXJzIHRvIHByb3ZpZGUgZmVlZGJhY2sgb24gb3Vy
IG1haWwgYW5kIGF1dGhlbnRpY2F0aW9uIGZhaWx1cmVzLCBldGMuIEkgd2FzIGFjY29tbW9kYXRl
ZCB0byB2YXJpb3VzIGRlZ3JlZXMgYmVjYXVzZSBJL215IG9yZ2FuaXphdGlvbiB3YXMgcGVyY2Vp
dmVkIGFzIGFnZ3Jlc3NpdmVseSBtb3ZpbmcgdG8gY29tYmF0IGFidXNlLiBNb3N0IG9mIHRoZSBw
cm92aWRlcnMgdGhhdCByZXNwb25kZWQgaGFkIHRvIG1ha2UgYSBzcGVjaWFsIGVmZm9ydCB0byBw
cm92aWRlIHRoYXQgc29ydCBvZiBpbmZvcm1hdGlvbiBhbmQgdGhlIGZvcm1hdCBhbmQgd2hhdCB3
YXMgaW5jbHVkZWQgdmFyaWVkIGZyb20gcHJvdmlkZXIgdG8gcHJvdmlkZXIuIEl0IHdhcyBhbHNv
IGVhc2llciBmb3Igc29tZSBiZWNhdXNlIHdlIGhhZCBwYXJ0bmVyc2hpcCBvciBvdGhlciBjb250
cmFjdHVhbCBhZ3JlZW1lbnRzIGFscmVhZHkgaW4gcGxhY2UgdGhhdCBhZGRyZXNzZWQgcHJpdmFj
eSBjb25jZXJucy4gSSB3b3VsZCBnZXQgYSBzbGljZSBvZiBkYXRhIGZyb20gb25lIHByb3ZpZGVy
IGFuZCBzcGVuZCBhbiBpbmNyZWRpYmxlIGFtb3VudCBvZiB0aW1lIHRyeWluZyB0byBnZXQgaXQg
dG8gbWVzaCB3aXRoIGEgZGlmZmVyZW50IHNsaWNlIG9mIGRhdGEgZnJvbSBzb21lb25lIGVsc2Uu
IE9uY2Ugd2UgaW1wbGVtZW50ZWQgKHN0cm9uZyBhc3NlcnRpb25zKSBmb3IgU1BGIGFuZCBES0lN
LCBzb21lIG9mIHRoZSBmb2xrcyB3b3JraW5nIG9uIHZhbGlkYXRpb24gaW1wbGVtZW50YXRpb25z
IHVzZWQgb3VyIG1haWwgc3RyZWFtcyBhcyBhIHJlZmVyZW5jZSBjYXNlIGFzIHRoZXkgZGV2ZWxv
cGVkIHRoZWlyIHZhbGlkYXRpb24gaW1wbGVtZW50YXRpb25zIChhbmQgcmVtZW1iZXIsIHRoaXMg
d2FzIHByZS1ETUFSQyBhbmQgZXZlbiBiZWZvcmUgREtJTSB3YXMgZmluYWxpemVkKS4gQXMgcGFy
dGljaXBhbnRzIGluIHRoZSBiaWxhdGVyYWwgZWZmb3J0cyBjb21wYXJlZCBub3RlcyBhbmQgZXhw
ZXJpZW5jZXMgaXQgd2FzIG5hdHVyYWwgdG8gdHJ5IGFuZCBzdGFuZGFyZGl6ZSB0aGUgaW50ZXJh
Y3Rpb25zIGJldHdlZW4gYWxsIHRoZSB2YXJpb3VzIHBsYXllcnMuIEFuZCBvbmNlIHRoYXQgb2Nj
dXJyZWQgdGhlcmUgd2FzIGEgZGVzaXJlIHRvIG1ha2UgaXQgYW4gb3BlbiBzdGFuZGFyZCByYXRo
ZXIgdGhhbiBhIHByaXZhdGUgY2x1YiBiZWNhdXNlIHRoZXJlIHdhcyBhIGJlbGllZiB0aGF0IGl0
IHdhcyBiZW5lZmljaWFsIHRvIHRoZSB3aWRlciBjb21tdW5pdHkg4oCTIHRodXMgRE1BUkMuIFRo
ZXJlIHdlcmUgb3RoZXIgcHJlLURNQVJDIGVmZm9ydHMgdGhhdCBkaWQgbm90IHByb2R1Y2UgYW55
IHZpc2libGUgb3V0Y29tZS4gU29tZSBvZiB0aGVtIEkgcGFydGljaXBhdGVkIGluIGFuZCBvdGhl
cnMgSSBkaWQgbm90IGJlY2F1c2UgSSBmZWx0IHRoZXkgd2VyZSB1bmxpa2VseSB0byBiZSBzdWNj
ZXNzZnVsLiBTbyBhdCB0aGUgZW5kIG9mIHRoZSBkYXksIGlmIHlvdXIgcGVyc3BlY3RpdmUgaXMg
dGhhdCBpdCBpc27igJl0IHdvcnRoIHlvdXIgdGltZSBhbmQgZWZmb3J0LCAgSSBjYW7igJl0IHRo
aW5rIG9mIGFueXRoaW5nIEkgb3IgYW55b25lIGVsc2UgbWlnaHQgc2F5IHRoYXQgd291bGQgY2hh
bmdlIHlvdXIgbWluZC4NCg0KTWlrZQ0K

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D485AEUSCLES544agnaam_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAx
LjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRz
IHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1h
cCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRp
Zl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVy
cGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzow
aW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IERhdmUgQ3JpZGxhbmQgW21haWx0
bzpkYXZlQGNyaWRsYW5kLm5ldF0NCjxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIEFwcmls
IDE2LCAyMDE0IDI6MjQgUE08YnI+DQo8Yj5Ubzo8L2I+IFMgTW9vbmVzYW15PGJyPg0KPGI+Q2M6
PC9iPiBNSCBNaWNoYWVsIEhhbW1lciAoNTMwNCk7IGlldGZAaWV0Zi5vcmcgRGlzY3Vzc2lvbjxi
cj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogTGV0J3MgdGFsayAod2FzOiBETUFSQzogcGVyc3BlY3Rp
dmVzIGZyb20gYSBsaXN0YWRtaW4gb2YgbGFyZ2Ugb3Blbi1zb3VyY2UgbGlzdHMpPG86cD48L286
cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+T24gMTYgQXByaWwgMjAxNCAxODoyNiwgUyBNb29uZXNhbXkgJmx0OzxhIGhyZWY9Im1haWx0
bzpzbSYjNDM7aWV0ZkBlbGFuZHN5cy5jb20iIHRhcmdldD0iX2JsYW5rIj5zbSYjNDM7aWV0ZkBl
bGFuZHN5cy5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPlNwZWFraW5nIGFib3V0IGNhcmVlciBlbmhhbmNpbmcgbW92ZXMsIGNvbW1vbiBzZW5z
ZSBkaWN0YXRlcyB0aGF0IGl0IGlzIHRvIGJlIGFzc3VtZWQgdGhhdCB0aGUgaW5kaXZpZHVhbCBp
cyB0aGUgbW91dGhwaWVjZSBvZiB0aGUgb3JnYW5pemF0aW9uIChJIGFtIG5vdCBpbmZlcnJpbmcg
dGhhdCB5b3UgYXJlKS4gJm5ic3A7SW4gbXkgb3BpbmlvbiByZXZpZXdzIGZyb20gaW5kaXZpZHVh
bHMgYWZmaWxpYXRlZCB3aXRoIHRoZQ0KIGNvbXBhbmllcyBsaXN0ZWQgb24gdGhlIHdlYiBwYWdl
IG1pZ2h0IG5vdCBmaXQgd2l0aGluIHRoZSBvYmplY3Rpdml0eSBndWlkZWxpbmVzLiAmbmJzcDtJ
dCBtYXkgYmUgZGlmZmljdWx0IHRvIGZpbmQgYW4gZXh0ZXJuYWwgcmV2aWV3ZXIgaWYgRGF2ZSBD
cmlkbGFuZCBkb2VzIG5vdCB3aXNoIHRvIGRvbmF0ZSBoaXMgaW50ZWxsZWN0dWFsIHByb3BlcnR5
IHJpZ2h0cy48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPk1IOiBSZXZpZXdzIGZyb20gMzxzdXA+cmQ8L3N1cD4gcGFydGllcyBoYXZlIGJlZW4gYWx3
YXlzIHdlbGNvbWUgYW5kIHdlcmUgc3BlY2lmaWNhbGx5IGFza2VkIGZvciBmcm9tIGEgbnVtYmVy
IG9mIHBlb3BsZSB1bmFmZmlsaWF0ZWQgd2l0aCBkbWFyYy5vcmcuIFRoZXJlDQogd2VyZSBleHRl
cm5hbCByZXZpZXdzIChhbHRob3VnaCBpdCB3b3VsZCBoYXZlIGJlZW4gbmljZSB0byBzZWUgbW9y
ZSkgZnJvbSB2YXJpb3VzIHBlb3BsZS4gSSBub3RlIHRoYXQgSmltIEZlbnRvbiBqdXN0IHBvc3Rl
ZCB0byB0aGUgZG1hcmMtaWV0ZiBsaXN0IGFib3V0IG1hbnkgb2YgaGlzIHN1Z2dlc3Rpb25zIGJl
aW5nIGluY29ycG9yYXRlZC4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3Nh
bnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+V2l0aCByZWdhcmQgdG8gbW91dGhwaWVjZXMs
IHRoZXJlIGFyZSBzb21lIHBlb3BsZSB3aG8gY2xlYXJseSBhcmUgYW5kIG90aGVyIHBlb3BsZSB3
aG8gYXJlIG5vdC4gSXTigJlzIGdlbmVyYWxseSBub3QgdG9vIGRpZmZpY3VsdCB0byBmaWd1cmUg
b3V0IHRoZSBkaWZmZXJlbmNlDQogYmV0d2VlbiB0aGUgdHdvLjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5JJ20gYWN0dWFsbHkgcXVpdGUgaGFwcHkgZG9uYXRpbmcgSVBS
OyBJIGRvIGl0IGFsbCB0aGUgdGltZS4gVGhlIFhTRiBwb2xpY3kgb24gY29weXJpZ2h0IGlzIGFu
IGFzc2lnbm1lbnQgb25lLCBmb3IgZXhhbXBsZS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBoYXZlIG5vIGlkZWEgd2hhdCB0aGUgSVBSIHBv
bGljeSBpcyBmb3IgRE1BUkMsIGl0IGhhcyBiZWVuIGRldmVsb3BlZCBvdXRzaWRlIHRoZSBJRVRG
IHByb2Nlc3MsIGFuZCBjaGFuZ2VzIHRvIGl0IGZyb20gdGhlIElFVEYgYXJlIG5vdCB3ZWxjb21l
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj5NSDogVGhlIElQUiBwb2xpY3kgZm9yIERNQVJDIGZhbGxzIHVuZGVyIHRoZSBPV0Yg4oCT
IEFsbCBvZiB0aGUgcGFydGljaXBhdGluZyBvcmdhbml6YXRpb25zIGhhdmUgc2lnbmVkIGFncmVl
bWVudHMgZm9yIHRoaXMuIEFueW9uZSBjYW4gY29udHJpYnV0ZSBhcyBhbiBpbmRpdmlkdWFsDQog
YnV0IHRoZSBwYXJ0aWNpcGF0aW5nIG9yZ2FuaXphdGlvbnMgaGF2ZSBzcGVjaWZpYyBjb250cmFj
dHVhbCBvYmxpZ2F0aW9ucy4gVGhlcmUgYXJlIG1vcmUgZGV0YWlscyBvbiB0aGUgT1dGIGJhc2lz
IGZvciBhbnlvbmUgaW50ZXJlc3RlZCBpbiBwYXJ0aWNpcGF0aW5nIG9yIGNvbnRyaWJ1dGluZyB0
aHJvdWdoIHRoZSBkbWFyYy1kaXNjdXNzIGxpc3QgYXQNCjxhIGhyZWY9Imh0dHA6Ly93d3cuZG1h
cmMub3JnL25vdGVfd2VsbC5odG1sIj5odHRwOi8vd3d3LmRtYXJjLm9yZy9ub3RlX3dlbGwuaHRt
bDwvYT4uICZuYnNwO0NvbnNpZGVyaW5nIHRoYXQgdGhlcmUgd2VyZSBtdWx0aXBsZSBhdHRlbXB0
cyB0byBoYW5kIHRoZSBETUFSQyBzcGVjIG92ZXIgdG8gdGhlIElFVEYgSSB0aGluayB0aGUgbGFz
dCBwYXJ0IG9mIHlvdXIgc3RhdGVtZW50IGlzIGEgc3RyZXRjaC4gVGhlcmUgd2VyZSBjb25zdHJh
aW50cy9jb25zaWRlcmF0aW9ucw0KIHRoYXQgSSB0aGluayBjb3VsZCBoYXZlIGJlZW4gd29ya2Vk
IG91dCwgYnV0IGZvciBub3cgdGhhdCBpcyB3YXRlciB1bmRlciB0aGUgYnJpZGdlLg0KPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0
OTdEIj5TcGVha2luZyBvbmx5IGZvciBteXNlbGYgYmVjYXVzZSBJ4oCZbSBub3QgYW55IG9uZXMg
bW91dGhwaWVjZSwgSSBiZWxpZXZlIHRoYXQgYW55IGNvbnRyaWJ1dGlvbnMgd2hpY2ggaW1wcm92
ZSB0aGUgdGVjaG5pY2FsIHJpZ29yIG9mIHRoZSBzcGVjaWZpY2F0aW9uIGFyZSB2YWx1ZWQNCiBh
bmQgYXJlIG9mIGJlbmVmaXQgdG8gdGhlIGNvbW11bml0eSBpbiB0aGUgbGFyZ2VyIHNlbnNlLiBJ
ZiBJIGJlbGlldmVkIG90aGVyd2lzZSBJIHdvdWxkIG5vdCBiZSBwYXJ0aWNpcGF0aW5nLg0KPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNvIGZyb20gbXkgcGVyc3BlY3Rp
dmUsIGl0J3MgbGlrZSBzYXlpbmcgJnF1b3Q7SGV5LCB3ZSdkIGxpa2UgeW91IHRvIHNwZW5kIHRp
bWUgYW5kIGVmZm9ydCBvbiByZXZpZXdpbmcgdGhpcyBzbyB3ZSBjYW4gdGVsbCB5b3Ugd2h5IHdl
J3JlIG5vdCBnb2luZyB0byBtYWtlIGFueSBjaGFuZ2VzJnF1b3Q7LjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMx
RjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5NSDogSSByZXNwZWN0
IHlvdXIgcGVyc3BlY3RpdmUgRGF2ZS4gSSBjYW4gb25seSBwb2ludCB0byB0aGUgZXhwZXJpZW5j
ZSBvZiBvdGhlcnMgdGhhdCBoYXZlIHRha2VuIHRoZSB0aW1lIGFuZCBlZmZvcnQgYW5kIGZvdW5k
IHRoZWlyIHN1Z2dlc3Rpb25zIGluY29ycG9yYXRlZC4NCiBCZWNhdXNlIHRoZSBwYXJ0aWNpcGF0
aW5nIG9yZ2FuaXphdGlvbnMgYXJlIGJvdW5kIGJ5IE9XRiBhbmQgdGhlIHBhcnRpY2lwYXRpb24g
YWdyZWVtZW50LCB0aGVyZSBpcyBhbiBvYmxpZ2F0aW9uIHRvIGZvbGxvdyBjZXJ0YWluIHByb2Nl
c3Nlcy4gSSB3aWxsIHNheSB0aGF0IGZyb20gbXkgcGVyc3BlY3RpdmUgaXQgd2FzIG5ldmVyIGFu
dGljaXBhdGVkIHRoYXQgd2Ugd291bGQgYmUgZ29pbmcgdGhpcyBsb25nIHdpdGhvdXQgYSBoYW5k
b2ZmIHRvDQogSUVURi4gSeKAmW0gbm90IGxvb2tpbmcgdG8gZGViYXRlIHdoZXRoZXIgaXQgc2hv
dWxkIG9yIHNob3VsZG7igJl0IGJlIG9yIGhvdyBpdCBtaWdodCBiZSBhdCB0aGlzIHBvaW50LCBJ
4oCZbSBvbmx5IHRyeWluZyB0byBwcm92aWRlIHNvbWUgcGVyc3BlY3RpdmUgaW50byB3aHkgdGhl
IERNQVJDIHByb2Nlc3MgaXMgY3VycmVudGx5IHRoZSB3YXkgaXQgaXMuDQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPlJl
bWVtYmVyICh1bmRlcnN0YW5kPykgdGhhdCB0aGlzIChETUFSQykgc3RhcnRlZCBiZWNhdXNlIHZh
cmlvdXMgcGFydGljaXBhbnRzIGhhZCBwcml2YXRlIGJpbGF0ZXJhbCBhZ3JlZW1lbnRzIHJlZ2Fy
ZGluZyBwb2xpY3kgYXNzZXJ0aW9ucyBhbmQgcmVwb3J0aW5nLiBXaGVuDQogSSBmaXJzdCBzdGFy
dGVkIHdvcmtpbmcgb24gbXkgaW1wbGVtZW50YXRpb24gKGFuZCBvcGVyYXRpb25hbCBjaGFuZ2Vz
KSBJIGhhZCB0byBhc2sgdmFyaW91cyBtYWlsYm94IHByb3ZpZGVycyB0byBwcm92aWRlIGZlZWRi
YWNrIG9uIG91ciBtYWlsIGFuZCBhdXRoZW50aWNhdGlvbiBmYWlsdXJlcywgZXRjLiBJIHdhcyBh
Y2NvbW1vZGF0ZWQgdG8gdmFyaW91cyBkZWdyZWVzIGJlY2F1c2UgSS9teSBvcmdhbml6YXRpb24g
d2FzIHBlcmNlaXZlZCBhcw0KIGFnZ3Jlc3NpdmVseSBtb3ZpbmcgdG8gY29tYmF0IGFidXNlLiBN
b3N0IG9mIHRoZSBwcm92aWRlcnMgdGhhdCByZXNwb25kZWQgaGFkIHRvIG1ha2UgYSBzcGVjaWFs
IGVmZm9ydCB0byBwcm92aWRlIHRoYXQgc29ydCBvZiBpbmZvcm1hdGlvbiBhbmQgdGhlIGZvcm1h
dCBhbmQgd2hhdCB3YXMgaW5jbHVkZWQgdmFyaWVkIGZyb20gcHJvdmlkZXIgdG8gcHJvdmlkZXIu
IEl0IHdhcyBhbHNvIGVhc2llciBmb3Igc29tZSBiZWNhdXNlIHdlIGhhZCBwYXJ0bmVyc2hpcA0K
IG9yIG90aGVyIGNvbnRyYWN0dWFsIGFncmVlbWVudHMgYWxyZWFkeSBpbiBwbGFjZSB0aGF0IGFk
ZHJlc3NlZCBwcml2YWN5IGNvbmNlcm5zLiBJIHdvdWxkIGdldCBhIHNsaWNlIG9mIGRhdGEgZnJv
bSBvbmUgcHJvdmlkZXIgYW5kIHNwZW5kIGFuIGluY3JlZGlibGUgYW1vdW50IG9mIHRpbWUgdHJ5
aW5nIHRvIGdldCBpdCB0byBtZXNoIHdpdGggYSBkaWZmZXJlbnQgc2xpY2Ugb2YgZGF0YSBmcm9t
IHNvbWVvbmUgZWxzZS4gT25jZSB3ZSBpbXBsZW1lbnRlZA0KIChzdHJvbmcgYXNzZXJ0aW9ucykg
Zm9yIFNQRiBhbmQgREtJTSwgc29tZSBvZiB0aGUgZm9sa3Mgd29ya2luZyBvbiB2YWxpZGF0aW9u
IGltcGxlbWVudGF0aW9ucyB1c2VkIG91ciBtYWlsIHN0cmVhbXMgYXMgYSByZWZlcmVuY2UgY2Fz
ZSBhcyB0aGV5IGRldmVsb3BlZCB0aGVpciB2YWxpZGF0aW9uIGltcGxlbWVudGF0aW9ucyAoYW5k
IHJlbWVtYmVyLCB0aGlzIHdhcyBwcmUtRE1BUkMgYW5kIGV2ZW4gYmVmb3JlIERLSU0gd2FzIGZp
bmFsaXplZCkuDQogQXMgcGFydGljaXBhbnRzIGluIHRoZSBiaWxhdGVyYWwgZWZmb3J0cyBjb21w
YXJlZCBub3RlcyBhbmQgZXhwZXJpZW5jZXMgaXQgd2FzIG5hdHVyYWwgdG8gdHJ5IGFuZCBzdGFu
ZGFyZGl6ZSB0aGUgaW50ZXJhY3Rpb25zIGJldHdlZW4gYWxsIHRoZSB2YXJpb3VzIHBsYXllcnMu
IEFuZCBvbmNlIHRoYXQgb2NjdXJyZWQgdGhlcmUgd2FzIGEgZGVzaXJlIHRvIG1ha2UgaXQgYW4g
b3BlbiBzdGFuZGFyZCByYXRoZXIgdGhhbiBhIHByaXZhdGUgY2x1Yg0KIGJlY2F1c2UgdGhlcmUg
d2FzIGEgYmVsaWVmIHRoYXQgaXQgd2FzIGJlbmVmaWNpYWwgdG8gdGhlIHdpZGVyIGNvbW11bml0
eSDigJMgdGh1cyBETUFSQy4gVGhlcmUgd2VyZSBvdGhlciBwcmUtRE1BUkMgZWZmb3J0cyB0aGF0
IGRpZCBub3QgcHJvZHVjZSBhbnkgdmlzaWJsZSBvdXRjb21lLiBTb21lIG9mIHRoZW0gSSBwYXJ0
aWNpcGF0ZWQgaW4gYW5kIG90aGVycyBJIGRpZCBub3QgYmVjYXVzZSBJIGZlbHQgdGhleSB3ZXJl
IHVubGlrZWx5IHRvIGJlDQogc3VjY2Vzc2Z1bC4gU28gYXQgdGhlIGVuZCBvZiB0aGUgZGF5LCBp
ZiB5b3VyIHBlcnNwZWN0aXZlIGlzIHRoYXQgaXQgaXNu4oCZdCB3b3J0aCB5b3VyIHRpbWUgYW5k
IGVmZm9ydCwgJm5ic3A7SSBjYW7igJl0IHRoaW5rIG9mIGFueXRoaW5nIEkgb3IgYW55b25lIGVs
c2UgbWlnaHQgc2F5IHRoYXQgd291bGQgY2hhbmdlIHlvdXIgbWluZC48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7
Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPk1pa2U8
L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D485AEUSCLES544agnaam_--


From nobody Wed Apr 16 13:57:34 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 786391A02E8 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:57:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 bQnuTbvMtYuS for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 13:57:27 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5E4601A02AC for <ietf@ietf.org>; Wed, 16 Apr 2014 13:57:26 -0700 (PDT)
Received: (qmail 11351 invoked from network); 16 Apr 2014 20:57:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=2c56.534eeeb3.k1404; bh=EYdqHImTBaFG/+9zBHBKoYhR5seHxMoqpao/y7+NxT8=; b=npo6wwpKkXmixo33OBYwiMK5GxE20XvPB9WvhHEvlK81MhacfdtmgdF8dxKKL4oCDW4wQ66rrbITEmCM95tnWx9a2W2KC2DQxKa7gRPb1zEiSPLZ8RGql65H/0iE6k5OW7jdiEOdrNa5FcLTtfKHf7yVIHFkPxOBaHKo++vrfF4q7xL/W4Rwn+KkkrilxwCVYcsytFucu00krbfnLXO2dEm2JGAmcp/CEUhRDx2004hGqQbDpXii0rAYfVpGUYky
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=2c56.534eeeb3.k1404; bh=EYdqHImTBaFG/+9zBHBKoYhR5seHxMoqpao/y7+NxT8=; b=Gu0hg4Cz04eS/AcPW3L3I7IBxqi/t7cEa4G0NHuAIAjEpdVMkQpPIMtOlzG/N81mBiXRknkBDQ7jNCcjp1VMSlXhM6BHKG5nB4PrqJLOECFHoRKkUsyoRdfv9Rp5Rb2Unwa7LuijE0miV1QVW9OykLDhyjUVRm4ig7Db8VZLijwrEuGp2dE30FPxtXEGPJmfxL6wbwS7nzIsZDtVimWQgBdfg6K6DkS2NLI6FYm4EbJpuAbOGWr7/R803EukBjxg
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 16 Apr 2014 20:57:23 -0000
Date: 16 Apr 2014 16:57:22 -0400
Message-ID: <alpine.BSF.2.00.1404161654430.2065@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Dave Cridland" <dave@cridland.net>
Subject: Re: (DMARC) Why mailing lists are only sort of special
In-Reply-To: <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LhtHDt51OFVijN0qGYBqi2OVlYg
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 20:57:31 -0000

> This means that mailing lists (and other forwarding cases) are enforced
> into having DMARC records in order to forward DMARC originating messages,
> which seems reasonable, and the Sender addresses must also be relatively
> sensible, which they normally are already.

> I may be missing something.

How do I distinguish the nice mailing lists at ietf.org from random evil 
spammer domains sending spam with List-ID headers?

Every proposal I've seen like this ends up tripping over the fact that 
there is no technical way to distinguish between mail from real mailing 
lists and spam that looks like it's from mailing lists.  Hence you need a 
whitelist for the real mail, at which point all of the mechanism beyond 
the key for the whitelist (probably a DKIM signature) is superfluous.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Wed Apr 16 15:53:53 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A80B01A0359 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 15:53:52 -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, SPF_PASS=-0.001] autolearn=ham
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 ritmtODGNHEl for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 15:53:51 -0700 (PDT)
Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) by ietfa.amsl.com (Postfix) with ESMTP id D33371A023A for <ietf@ietf.org>; Wed, 16 Apr 2014 15:53:50 -0700 (PDT)
Received: by mail-wi0-f182.google.com with SMTP id d1so25480wiv.9 for <ietf@ietf.org>; Wed, 16 Apr 2014 15:53:46 -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:content-type; bh=mZTu2Y5JA5cxKGcIZVj7g/cqNpq6Ja0wNkqWsmP1eHU=; b=YCAfYOG+fC3rrDVcG9jyP1wiJgPZ1sm+cAvIHPjkWyJFhsGIA5+iizg+bXDMhif8y4 ysbEgiB04NEJ2kiiyDgxqrAldbPK7wAZQ+ZJaL+qzcLHWw/K3Tm2GsKzJOIduKhrjdzO u7VZjcxDFDf2QqAzSYbbCxxNdnzyLUGqFlT6xXLS/1bkjHqLMDjSIK2A1vxn6k9+JkL/ BHaxGfVQjApymyNpJYEd4x6D0gnPryd3JVDELMeCrDUXbDygQBMLw3J661fiXm8Qh4z4 uLZt9XOHfrSkkSnjtfZZOAWKGMNvHNStCLpFO8/eE3cfifhbJ5ImAGnrzKqPOlthDQC6 el1A==
MIME-Version: 1.0
X-Received: by 10.180.106.132 with SMTP id gu4mr8825690wib.26.1397688826282; Wed, 16 Apr 2014 15:53:46 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Wed, 16 Apr 2014 15:53:46 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1404161654430.2065@joyce.lan>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan>
Date: Wed, 16 Apr 2014 15:53:46 -0700
Message-ID: <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com>
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=e89a8f3babd3ff484b04f730c918
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9Nd1lCMzH4FKzvgTExrQHMG6XRM
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 22:53:52 -0000

--e89a8f3babd3ff484b04f730c918
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 16, 2014 at 1:57 PM, John R Levine <johnl@taugh.com> wrote:

> How do I distinguish the nice mailing lists at ietf.org from random evil
> spammer domains sending spam with List-ID headers?
>
> Every proposal I've seen like this ends up tripping over the fact that
> there is no technical way to distinguish between mail from real mailing
> lists and spam that looks like it's from mailing lists.  Hence you need a
> whitelist for the real mail, at which point all of the mechanism beyond the
> key for the whitelist (probably a DKIM signature) is superfluous.
>

Let's assume for the moment that a whitelist is the only option.  (Pete
made a different suggestion that I haven't read fully yet, for example.)
Do you envision each operator maintaining its own whitelist, or one or more
public registries of them, or something else?

It may be the case that it's the only way, but if so, then someone needs to
write down some how-tos on this as well.  May as well begin to develop that
idea.

-MSK

--e89a8f3babd3ff484b04f730c918
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Apr 16, 2014 at 1:57 PM, John R Levine <span dir=
=3D"ltr">&lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@tau=
gh.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">How do I distinguish the nice mailing lists =
at <a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a> from random e=
vil spammer domains sending spam with List-ID headers?<br>

<br>
Every proposal I&#39;ve seen like this ends up tripping over the fact that =
there is no technical way to distinguish between mail from real mailing lis=
ts and spam that looks like it&#39;s from mailing lists. =C2=A0Hence you ne=
ed a whitelist for the real mail, at which point all of the mechanism beyon=
d the key for the whitelist (probably a DKIM signature) is superfluous.<br>
</blockquote><div><br></div><div>Let&#39;s assume for the moment that a whi=
telist is the only option.=C2=A0 (Pete made a different suggestion that I h=
aven&#39;t read fully yet, for example.)=C2=A0 Do you envision each operato=
r maintaining its own whitelist, or one or more public registries of them, =
or something else?<br>
<br></div><div>It may be the case that it&#39;s the only way, but if so, th=
en someone needs to write down some how-tos on this as well.=C2=A0 May as w=
ell begin to develop that idea.<br><br></div><div>-MSK</div></div></div></d=
iv>

--e89a8f3babd3ff484b04f730c918--


From nobody Wed Apr 16 15:56:31 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8D81A0375 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 15:56:30 -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, SPF_PASS=-0.001] autolearn=ham
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 QlpCX4gWZNME for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 15:56:29 -0700 (PDT)
Received: from mail-we0-x22a.google.com (mail-we0-x22a.google.com [IPv6:2a00:1450:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 30B701A0299 for <ietf@ietf.org>; Wed, 16 Apr 2014 15:56:29 -0700 (PDT)
Received: by mail-we0-f170.google.com with SMTP id w61so11593618wes.15 for <ietf@ietf.org>; Wed, 16 Apr 2014 15:56:25 -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:content-type; bh=sIAVEwwOeovEAbSmvvpEiWkdjovvJ0OmdoPdsHgvT5Q=; b=V/sM/T50tREJW9qDvU/C7xA1/vp0vbyIg1HFOOSpW0k/EjtL+DOHZr13L8q+gNKawM j2u2KbQ3Mq/Zg+utPGym0yi8PL+aS1eRqXcyyQixfvI8kpNATsg06I7myVcpZXhab2dC H3j9dwlPb9cTe2CtOF3lr0/T9veQ0c/gG1xa/CRzppxp41iu/nrBvSo8HQUqB+osE48g QYqxkUj830GbxZ3VKxthNFTu9o0fSfcHJddb0fHAWSzusKz5ZWnGloo8oY+kg2PZRpwB 50jo9CIUUCU1P0MswzF1I2ATL4VyOHwmX2e3t/2wGddN2i/gUBPtJ0/Z3wu3KVT1i+If GprQ==
MIME-Version: 1.0
X-Received: by 10.180.36.101 with SMTP id p5mr9402863wij.8.1397688985420; Wed, 16 Apr 2014 15:56:25 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Wed, 16 Apr 2014 15:56:25 -0700 (PDT)
In-Reply-To: <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com>
Date: Wed, 16 Apr 2014 15:56:25 -0700
Message-ID: <CAL0qLwaDjMbNta4HJbpjS-3W9pPC45N+HaBCMXL9XcstPaQ5NQ@mail.gmail.com>
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=e89a8f50345e7b8a0f04f730d320
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uKNfArn_lE7BwEHy0Nv9sk00Ir4
Cc: John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 22:56:30 -0000

--e89a8f50345e7b8a0f04f730d320
Content-Type: text/plain; charset=UTF-8

On Wed, Apr 16, 2014 at 1:01 PM, Dave Cridland <dave@cridland.net> wrote:

> Unfortunately, the only option I thought was possibly available isn't
> permissible by the specification - therefore, the only solution involves
> alterations to the deployed base, which has been ruled impossible for over
> a year now.
>

Suppose you had the power to crack that barrier and do the impossible.
What would you do?

--e89a8f50345e7b8a0f04f730d320
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, Apr 16, 2014 at 1:01 PM, Dave Cridland <span dir=
=3D"ltr">&lt;<a href=3D"mailto:dave@cridland.net" target=3D"_blank">dave@cr=
idland.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra">=
Unfortunately, the only option I thought was possibly available isn&#39;t p=
ermissible by the specification - therefore, the only solution involves alt=
erations to the deployed base, which has been ruled impossible for over a y=
ear now.</div>
</div></blockquote><div><br></div><div>Suppose you had the power to crack t=
hat barrier and do the impossible.=C2=A0 What would you do?<br><br></div></=
div></div></div>

--e89a8f50345e7b8a0f04f730d320--


From nobody Wed Apr 16 16:16:39 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 838C21A03FD for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 16:16:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 St-N6V6_D12v for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 16:16:34 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id CC37E1A0359 for <ietf@ietf.org>; Wed, 16 Apr 2014 16:16:34 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 33C02CC0B7 for <ietf@ietf.org>; Wed, 16 Apr 2014 19:16:31 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id h49axiuX5+lS for <ietf@ietf.org>; Wed, 16 Apr 2014 19:16:26 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 62636CC0B6 for <ietf@ietf.org>; Wed, 16 Apr 2014 19:16:26 -0400 (EDT)
Message-ID: <534F0F4A.9010901@meetinghouse.net>
Date: Wed, 16 Apr 2014 19:16:26 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: (DMARC) Why mailing lists are only sort of special
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com>
In-Reply-To: <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/R32hHudRr0prM9rbuchmJccN6Bs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 23:16:38 -0000

Murray S. Kucherawy wrote:
> On Wed, Apr 16, 2014 at 1:57 PM, John R Levine <johnl@taugh.com 
> <mailto:johnl@taugh.com>> wrote:
>
>     How do I distinguish the nice mailing lists at ietf.org
>     <http://ietf.org> from random evil spammer domains sending spam
>     with List-ID headers?
>
>     Every proposal I've seen like this ends up tripping over the fact
>     that there is no technical way to distinguish between mail from
>     real mailing lists and spam that looks like it's from mailing
>     lists.  Hence you need a whitelist for the real mail, at which
>     point all of the mechanism beyond the key for the whitelist
>     (probably a DKIM signature) is superfluous.
>
>
> Let's assume for the moment that a whitelist is the only option.  
> (Pete made a different suggestion that I haven't read fully yet, for 
> example.)  Do you envision each operator maintaining its own 
> whitelist, or one or more public registries of them, or something else?
>
> It may be the case that it's the only way, but if so, then someone 
> needs to write down some how-tos on this as well.  May as well begin 
> to develop that idea.
>
>
Well... yahoo, aol, and others DO keep whitelists now - and various 
mechanisms for getting on them.  Yahoo doesn't, however, seem to apply 
their whitelisting methods to their own mail that's passed through 
DMARC.  Hmmm.....

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Wed Apr 16 16:26:06 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 247D71A004B for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 16:26:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 KCT7KNijg5wr for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 16:26:02 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1DC021A0408 for <ietf@ietf.org>; Wed, 16 Apr 2014 16:26:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397690759; x=1429226759; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=4A7kUMynv9POHxPy7DzoyIZZ5gwNu66+RNbGfdGIoOA=; b=g46spJYHYp2Rus1QqQEcSSiLMHhGOiGHo7GERzkP89im48VEeQkADWxC HMrw3pOS2zXchY5GBMkqMOgOtnwnlsUNqLJCqZSYmR6C8E2hdrm8uRDhy ECS+GqnT8e9XaDkhYkFZPOtn14KZkKuV8JkQ+HMAkYnnb/dFOCLe4BfDu 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,7410"; a="62079895"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth01.qualcomm.com with ESMTP; 16 Apr 2014 16:25:59 -0700
X-IronPort-AV: E=Sophos;i="4.97,875,1389772800"; d="scan'208";a="626583613"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 16 Apr 2014 16:25:58 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 16 Apr 2014 16:25:57 -0700
Message-ID: <534F1183.6060702@qti.qualcomm.com>
Date: Wed, 16 Apr 2014 18:25:55 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: (DMARC) Why mailing lists are only sort of special
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1404161654430.2065@joyce.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AqSUfYEc1EIJyAgcFUCqRY8lqi8
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 23:26:04 -0000

Replying to two in one. They're sorta related.

On 4/16/14 7:58 AM, Michael Richardson wrote:

> It's clear to me that we need at least a non-WG mailing list for this
> *technical* discussion.

Yeah, we are starting to move into solution space, which needs to be 
discussed in a specific technical forum. I'll try to keep it short.

> so, what you are saying is that based upon the (SMTP) To: address, the sender
> needs a signal that this is a mailing list, and some way to react.
> Maybe this could be combined with various SMTP DANE mechanisms, or at least,
> maybe "Additional RR" could return that kind of information.
>    

The originator (well, more to the point, the originator's mail server) 
doesn't need a signal that it's a mailing list; it's simply that the 
destination makes an "if I forward the mail, I'll be including this" 
piece of data available, and the originator's server can then include 
that in the signature of the message. I was thinking this could be in 
some special kind of DMARC (or whatever) record that lived in the 
mailing list's domain and could be queried by the originator's server.

> Running code.  we need someone to fund and participate in an experiment.
>   (cf: other thread about not participating in SDOs anymore)
>    

Bah. I do need to respond in that other thread, but I've become more 
sanguine about standardization after Vidya's article: I agree with a 
good deal of what she says, and I think she's categorized the problem 
correctly. Her having done that, I now see paths forward. More on the 
other thread.

On 4/16/14 3:57 PM, John R Levine wrote:

> How do I distinguish the nice mailing lists at ietf.org from random 
> evil spammer domains sending spam with List-ID headers?
>
> Every proposal I've seen like this ends up tripping over the fact that 
> there is no technical way to distinguish between mail from real 
> mailing lists and spam that looks like it's from mailing lists.

At least in the back-of-the-envelope scheme I suggested, the receiver 
doesn't need to distinguish mailing lists: The originator's system finds 
out where the mail is going, gets some information from the destination, 
and signs that and sends it with the message. The mailing list sends 
that along to the recipients. When my (one of the recipient's) server 
looks at that info, it determines that the originator sent the message 
directly to the mailing list, and I can tell that the mailing list sent 
it to me. My server doesn't need to determine whether the mailing list 
is "evil"; it knows that the person with the (e.g.) yahoo.com address 
sent to that mailing list from a yahoo.com server. That's what it cares 
about.

(And again, anyone can choose to continue to say, "No redistributing 
this message". The mailing list, or the eventual recipients if the 
mailing list doesn't play, should bounce the message in that case.)

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Wed Apr 16 16:31:21 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D97341A0410; Wed, 16 Apr 2014 16:31:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 DzgEx2SxbtlP; Wed, 16 Apr 2014 16:31:13 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 27E6A1A040F; Wed, 16 Apr 2014 16:31:12 -0700 (PDT)
Received: from maildlpprd06.lss.emc.com (maildlpprd06.lss.emc.com [10.253.24.38]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3GNV7C1003223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 16 Apr 2014 19:31:08 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s3GNV7C1003223
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397691068; bh=v3EwX5/iElkqecTL8cKXJGphWVY=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=pfeRnmVgmn7BlgDHfYP1Npst+unTEj122jtCF8Fu/TMZeLbg+uoUKnuTYia3agmwO EWzfwTZYp0cTEjSeXczyOxPNC6JEEw486ONQylWX15QvyIh3dsbzYuaBnZnb/gKDhQ P1TPDMXa0ezF81zdRhwGggv8nbUK4y6OVaqhkjmM=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s3GNV7C1003223
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd06.lss.emc.com (RSA Interceptor); Wed, 16 Apr 2014 16:30:59 -0700
Received: from mxhub33.corp.emc.com (mxhub33.corp.emc.com [10.254.93.81]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3GNUv2n006543 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 16 Apr 2014 19:30:58 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub33.corp.emc.com ([::1]) with mapi; Wed, 16 Apr 2014 19:30:57 -0400
From: "Black, David" <david.black@emc.com>
To: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "zali@cisco.com" <zali@cisco.com>, "nobo@cisco.com" <nobo@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Wed, 16 Apr 2014 19:30:56 -0400
Subject: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpA==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/O3on-oIOj5eidGt8H2FAmXbzREQ
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 23:31:18 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments
you may receive.

Document: draft-ietf-bfd-mib-17
Reviewer: David L. Black
Review Date: April 16, 2014
IETF LC End Date: April 28, 2014

Summary: This draft is on the right track, but has open issues
		described in the review.

This draft is a MIB module for the BFD protocol, which is an important low-
level routing protocol.  The draft is reasonable for a MIB draft; one needs
to go read the protocol documents to understand how the protocol works, and
significant portions of the text are derived from the usual MIB "boilerplat=
e"
as one would expect.  The "Brief Description of MIB Objects" is indeed
brief, but reasonable.  The shepherd writeup indicates that there are
multiple implementations.

Major issues:

This MIB contains many writable objects, so the authors should
take note of the IESG statement on writable MIB modules:

	http://www.ietf.org/iesg/statement/writable-mib-module.html

I did not see this mentioned in the shepherd writeup.  If the OPS Area
has not been consulted, I strongly suggest doing so during IETF Last
Call, e.g., starting with Benoit Claise (AD).

Minor issues:

The security considerations section includes considerations for
unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
but omits the corresponding considerations for bfdAdminStatus and
bfdSessNotificationsEnable.  Both of the latter objects are global,
so significant damage can be inflicted via these objects with a
small number of unauthorized modifications, so they need to be
included in the first list of sensitive objects.

I suggest that the authors recheck the entire MIB to ensure that
every object or table that should be included in the security
considerations section is appropriately included.

Also, as a General Variable, would bfdSessNotificationsEnable be better
named bfdNotificationsEnable, as it's not in the BFD Session Table?

I did not see a compliance requirement for a system that only
implements BFD protocol version 0.  That absence should at least be
mentioned somewhere.  For example, if this reflects a considered and
deliberate decision by the WG, that should be mentioned in the
introduction.

Nits/editorial comments:

In the security considerations for authentication-related objects:

OLD
   In order for these sensitive information
   from being improperly accessed, implementers MAY wish to disallow
   access to these objects.
NEW
   In order to prevent this sensitive information
   from being improperly accessed, implementers MAY disallow
   access to these objects.

idnits 2.13.01 found a truly minor nit that should be corrected when
the draft is next revised:

  =3D=3D Outdated reference: A later version (-05) exists of
     draft-ietf-bfd-tc-mib-04

it also generated a warning that probably does not reflect an actual proble=
m:

  -- The document seems to lack a disclaimer for pre-RFC5378 work, but may
     have content which was first submitted before 10 November 2008.  If yo=
u
     have contacted all the original authors and they are all willing to gr=
ant
     the BCP78 rights to the IETF Trust, then this is fine, and you can ign=
ore
     this comment.  If not, you may need to add the pre-RFC5378 disclaimer.=
=20
     (See the Legal Provisions document at
     http://trustee.ietf.org/license-info for more information.)

Thanks,
--David
----------------------------------------------------
David L. Black, Distinguished Engineer
EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
+1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-778=
6
david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
----------------------------------------------------


From nobody Wed Apr 16 16:32:15 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2378E1A040F for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 16:32:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.974
X-Spam-Level: 
X-Spam-Status: No, score=-0.974 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_14=0.6, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 i-l0-_XtnCPO for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 16:32:08 -0700 (PDT)
Received: from thunk.org (dfwtest.thunk.org [IPv6:2600:3c00::f03c:91ff:fe69:c5da]) by ietfa.amsl.com (Postfix) with ESMTP id 6F5AA1A0410 for <ietf@ietf.org>; Wed, 16 Apr 2014 16:32:08 -0700 (PDT)
Received: from tytso by thunk.org with local (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WaZSr-0004qJ-GS; Wed, 16 Apr 2014 23:42:01 +0000
Date: Wed, 16 Apr 2014 23:42:01 +0000
From: tytso@mit.edu
To: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: (DMARC) Why mailing lists are only sort of special
Message-ID: <20140416234201.GA18480@thunk.org>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com> <534F0F4A.9010901@meetinghouse.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <534F0F4A.9010901@meetinghouse.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/92ZVFGKPmkv4Rf9sLAUT4XKnT3Q
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 23:32:09 -0000

On Wed, Apr 16, 2014 at 07:16:26PM -0400, Miles Fidelman wrote:
> Well... yahoo, aol, and others DO keep whitelists now - and various
> mechanisms for getting on them.  Yahoo doesn't, however, seem to
> apply their whitelisting methods to their own mail that's passed
> through DMARC.  Hmmm.....

All of the major mail providers are almost certainly using some kind
of machine-learning that takes multiple things into account, including
SPF and DKIM results, message body filtering, etc.

The problem is that this only helps people who are receiving mail at
yahoo.com or gmail.com, etc.  The problem that Yahoo seems to be
fixated on, at least with respect to their desire to enable DMARC
p=reject, is that they don't trust that *other* people will have good
enough spam detection schemes such that they can detect messages sent
to other mail destinations (for example, such as alice@hotmail.com)
where the recipient claims to be bob@yahoo.com.

So the problem is not yahoo maintaining a set of whitelists, it's
everybody *else* needing to have a good enough machine learning
algorithms so they can detect bad e-mail.  If everyone did, then you
wouldn't need any DMARC policy other than p=none.  They could all look
at the SPF and DKIM, the message body, their ML algorithms that have
led them to conclude that ietf@ietf.org is a valid email list, and not
a spammer trying to look like a mailing list, and make the appropriate
ham vs spam determination.

In some sense the DMARC p=reject is basically Yahoo saying, "I don't
trust your spam algorithms, so please use a really bone-headed
algorithm which rejects any message claiming to be from
username@yahoo.com if the sender and the from field don't match."

Regards,

							- Ted


From nobody Wed Apr 16 17:39:17 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D24E1A0325 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 17:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 xnjUIPL95JCa for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 17:39:09 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 7CAE01A0368 for <ietf@ietf.org>; Wed, 16 Apr 2014 17:39:08 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id BA0F0CC0B9 for <ietf@ietf.org>; Wed, 16 Apr 2014 20:39:04 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id p612h3TDZwaL for <ietf@ietf.org>; Wed, 16 Apr 2014 20:38:58 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7D341CC099 for <ietf@ietf.org>; Wed, 16 Apr 2014 20:38:58 -0400 (EDT)
Message-ID: <534F22A2.20303@meetinghouse.net>
Date: Wed, 16 Apr 2014 20:38:58 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC: perspectives from a listadmin of large open-source lists
References: <534B524F.4050206@dcrocker.net> <alpine.BSF.2.00.1404132327560.26258@joyce.lan> <E0B7196CB2603B80BBEC21AF@JcK-HP8200.jck.com> <alpine.BSF.2.00.1404132346420.26386@joyce.lan> <1EBDF5239EEE5202D3837D25@JcK-HP8200.jck.com> <534B9760.90301@dougbarton.us> <6C80882F19CCEDFE15E987CA@JcK-HP8200.jck.com> <534BEF75.5060804@bbiw.net> <534DB093.5020507@qti.qualcomm.com> <534DBA0F.2050507@gmail.com> <20140415231720.GQ4456@thunk.org> <534E6AC1.7030709@qti.qualcomm.com> <18443.1397653096@sandelman.ca>
In-Reply-To: <18443.1397653096@sandelman.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YFyrYvE0LAbjrdWv_36JLAcvsUI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 00:39:14 -0000

Michael Richardson wrote:
> It's clear to me that we need at least a non-WG mailing list for this
> *technical* discussion.  Fixing the mailing list problem may require
> fundamental changes in how things work; and I think that is okay.
> Maybe we could try this NNTP thinkg I've heard about :-)
>
> P

well there is dmarc-ietf.org :-)

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Wed Apr 16 17:41:09 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E2CF1A0409 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 17:41:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 BMz3CHKWY3Ng for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 17:41:07 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 160671A0325 for <ietf@ietf.org>; Wed, 16 Apr 2014 17:41:07 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id AC661CC0BA for <ietf@ietf.org>; Wed, 16 Apr 2014 20:41:03 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kP92nM6osu4x for <ietf@ietf.org>; Wed, 16 Apr 2014 20:40:55 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id E8837CC0B7 for <ietf@ietf.org>; Wed, 16 Apr 2014 20:40:54 -0400 (EDT)
Message-ID: <534F2316.8030409@meetinghouse.net>
Date: Wed, 16 Apr 2014 20:40:54 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <534E57BC.1060501@cs.tcd.ie> <CE39F90A45FF0C49A1EA229FC9899B0507D47D69@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D47D69@USCLES544.agna.amgreetings.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PLp3VTpptP-1zHq5yfP9LlPS28Q
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 00:41:08 -0000

MH Michael Hammer (5304) wrote:
>
> I think a "guaranteed not to publish p=reject" logo should be offered up by IETF as a branding mechanism. In fact, I like this idea so much I am going to have a designer friend of mine create it. IETF prominently in the middle with "guaranteed not to publish p=reject" around the perimeter of the circular logo. Participating mailbox providers could display it prominently on their websites and in their marketing materials. Just to be clear for anyone wanting to jump in claiming trademark infringement, this falls under the heading of parody - unless of course Y'all want to take the proposal seriously in which case you can have the logo.
>
>
Can't tell if you're serious or not - but I like it :-)

Kind of like "Best Viewed with Any Browser"

Cheers,

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Wed Apr 16 18:39:45 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 734631A03AC for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 18:39:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 gzGkDg8hyqoG for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 18:39:40 -0700 (PDT)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.137]) by ietfa.amsl.com (Postfix) with ESMTP id C5BAC1A03A9 for <ietf@ietf.org>; Wed, 16 Apr 2014 18:39:39 -0700 (PDT)
Received: from [195.245.231.67:5338] by server-1.bemta-5.messagelabs.com id E0/ED-10259-7D03F435; Thu, 17 Apr 2014 01:39:35 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-82.messagelabs.com!1397698775!13765773!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13371 invoked from network); 17 Apr 2014 01:39:35 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-15.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 17 Apr 2014 01:39:35 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.54]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 17 Apr 2014 02:39:34 +0100
From: <l.wood@surrey.ac.uk>
To: <mfidelman@meetinghouse.net>, <ietf@ietf.org>
Date: Thu, 17 Apr 2014 02:39:03 +0100
Subject: RE: DMARC and yahoo
Thread-Topic: DMARC and yahoo
Thread-Index: Ac9Z1cWELixmkwPoQtCrYG33J0QwQwACAq27
Message-ID: <290E20B455C66743BE178C5C84F1240847E9989B8D@EXMB01CMS.surrey.ac.uk>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <534E57BC.1060501@cs.tcd.ie> <CE39F90A45FF0C49A1EA229FC9899B0507D47D69@USCLES544.agna.amgreetings.com>, <534F2316.8030409@meetinghouse.net>
In-Reply-To: <534F2316.8030409@meetinghouse.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cBPabG3ADcR6Y4QW_hbEklG-2A4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 01:39:44 -0000

> I think a "guaranteed not to publish p=3Dreject" logo should be offered u=
p by IETF as a branding mechanism.=20

... for expired internet-drafts.


Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Miles Fidelman [mfidelman@m=
eetinghouse.net]
Sent: 17 April 2014 01:40
To: ietf@ietf.org
Subject: Re: DMARC and yahoo

MH Michael Hammer (5304) wrote:
>
> I think a "guaranteed not to publish p=3Dreject" logo should be offered u=
p by IETF as a branding mechanism. In fact, I like this idea so much I am g=
oing to have a designer friend of mine create it. IETF prominently in the m=
iddle with "guaranteed not to publish p=3Dreject" around the perimeter of t=
he circular logo. Participating mailbox providers could display it prominen=
tly on their websites and in their marketing materials. Just to be clear fo=
r anyone wanting to jump in claiming trademark infringement, this falls und=
er the heading of parody - unless of course Y'all want to take the proposal=
 seriously in which case you can have the logo.
>
>
Can't tell if you're serious or not - but I like it :-)

Kind of like "Best Viewed with Any Browser"

Cheers,

Miles

--
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Wed Apr 16 20:02:54 2014
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD9F1A03F7 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 20:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.173
X-Spam-Level: 
X-Spam-Status: No, score=-7.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 dc6j9QbXfQxF for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 20:02:49 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) by ietfa.amsl.com (Postfix) with ESMTP id A6F7F1A00C2 for <ietf@ietf.org>; Wed, 16 Apr 2014 20:02:49 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id 142B42383D5; Thu, 17 Apr 2014 03:02:33 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 2F2C6160054; Thu, 17 Apr 2014 03:04:44 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id F1766160030; Thu, 17 Apr 2014 03:04:43 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 860BB13F6F28; Thu, 17 Apr 2014 13:02:29 +1000 (EST)
To: tytso@mit.edu
From: Mark Andrews <marka@isc.org>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com> <534F0F4A.9010901@meetinghouse.net> <20140416234201.GA18480@thunk.org>
Subject: Re: (DMARC) Why mailing lists are only sort of special
In-reply-to: Your message of "Wed, 16 Apr 2014 23:42:01 +0000." <20140416234201.GA18480@thunk.org>
Date: Thu, 17 Apr 2014 13:02:29 +1000
Message-Id: <20140417030229.860BB13F6F28@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aiAaFzzEtnMAHFOkeYrZmwzdPKY
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 03:02:52 -0000

Part of the problem is that DKIM requires that email passes through
the signer's MTA to get the signature added.  Per user certs chained
to the published cert would address this issue.

This would allow someone using gmail to send as @yahoo.com.  Yes,
it requires all the PKI stuff like CRL's for compromised accounts.
You report spam that passes DKIM to @yahoo.com who then revoke the
cert.  The CRL could be a DNS entry with a low negative TTL for
non-existing entries.  Note these CERT's don't need to be tied to
account names.  Yahoo would know who they were issued to but no one
else.  Multiple users could in theory use the same CERT.  Vetted
mailing list could use a CERT after re-writting Subject, attaching
footers etc.  This CERT would be marked as "on behalf of" indicating
that it is not the actual user that is signing the message but a
proxy.

This still requires a mailing list to sign the outgoing email and
have a collection of CERTS to do this with.  Mailing lists without
a CERT would reject incoming messages which would fail DKIM reporting
back to Yahoo why.  This would be a trigger to get a mailing list
CERT.  The yahoo user would need to sign off that they intended to
send to a mailing list before a CERT was issued.  This step could
be automated, but would be a brake on process abuse.

The email would have contain the necessary linkage information in
the headers to get back to the Yahoo's public key.

This isn't a perfect system but it would allow Yahoo to control who
gets to send email as user@yahoo.com.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Wed Apr 16 21:03:13 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F370E1A044B for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 21:03:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 mlUA00so0dWa for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 21:03:06 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id D6D361A043C for <ietf@ietf.org>; Wed, 16 Apr 2014 21:03:05 -0700 (PDT)
Received: (qmail 74483 invoked from network); 17 Apr 2014 04:03:01 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=122f2.534f5275.k1404; bh=yLi4j+k3OfhF8KlKUNAKZ1gxQtyszGwUoij3uPqbriY=; b=Ygmou+v4tJw61L134vV4TTr7FGqk8psHLyQkcXF42X7FcZHJ5eQX0FTavgZKXeUDA0M6frgIGJLIW9uUscI02LA7GIQ99QHJwZJ7H3415IYOM5BE/bn110V29R16fk+sDgZoqX5T6ksCkjb/a3S6OIIufaujQehXnh9SrydU6HLOf4VJmE5d3Zk2z7uhHGaW75IvgvnnunIX91e4ldbEIx1A2RmkMFPFZZyCKHlY8OQiXMHsXhcnMfQ8V0BQlcNB
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=122f2.534f5275.k1404; bh=yLi4j+k3OfhF8KlKUNAKZ1gxQtyszGwUoij3uPqbriY=; b=34/7thQHwqjBy6RQUNgXDb8G2HZcgfbXhTTfIAEz0hA0/7h1+q5FAP4xjzAoBm9SetGczdJpI66jUO8jEb4+NHS7l5OrM7/pmaOm4JWktoPiUV1kCStL71FloARKVl3rpL1ZrHkCebFjcbCSbx4PvAn/dqAsYOmWS2Gz4f+YcCRy+6lT6nIuWkK2dMyAIvLtzJynqJrsOGMQotrKQzocByukmEczoTZ8wi2Js1ngvTYKp1I8acR+yoJrEO3XrocI
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 17 Apr 2014 04:03:01 -0000
Date: 17 Apr 2014 00:03:00 -0400
Message-ID: <alpine.BSF.2.00.1404162346400.2194@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Pete Resnick" <presnick@qti.qualcomm.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <534F1183.6060702@qti.qualcomm.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-506175694-1397707381=:2194"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/C6iwUEt3ZSHJQ_q_d1Em5yJ8_I4
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 04:03:11 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-506175694-1397707381=:2194
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> The originator (well, more to the point, the originator's mail server) 
> doesn't need a signal that it's a mailing list; it's simply that the 
> destination makes an "if I forward the mail, I'll be including this" piece of 
> data available, and the originator's server can then include that in the 
> signature of the message. I was thinking this could be in some special kind 
> of DMARC (or whatever) record that lived in the mailing list's domain and 
> could be queried by the originator's server.

We argued at great length about this issue when we were doing DKIM.  The 
magic token has to be cryptographically tied to the contents of the 
original message, or bad guys can take the token from a real message and 
replace the body with spam.  So that means a token tied to a hash of the 
contents of the message which is, of course, a DKIM signature.  This 
scheme is equivalent to requiring that lists preserve DKIM signatures, 
which they don't.

Every attempt to create a signing scheme that is flexible enough to deal 
with all the routine stuff that lists do (e.g., reorder, discard, or 
flatten MIME parts while adding the usual subject tags and body footers) 
while being robust enough to prevent bad guys from replacing the message 
with spam has completely failed.  We can try again, but I don't see any 
reason to think that the result would be any different.

Hence you can only accept mutated messages from sources you trust, i.e., a 
whitelist, and once you have a whitelist, you might as well just deliver 
the whitelisted mail.  Maybe I'm missing something here, but we've gone 
around this barn an awful lot of times over the past decade and always 
ended up in the same place.

R's,
John
--3825401791-506175694-1397707381=:2194
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIII7gYJKoZIhvcNAQcCoIII3zCCCNsCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBh8wggYbMIIFA6ADAgECAgMJWEYwDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xNDAzMTgxOTQ3NDdaFw0xNTAzMjAwMDU2MDBaMDoxGDAW
BgNVBAMMD2pvaG5sQHRhdWdoLmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxA
dGF1Z2guY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnMGH
52DBxB4jb86Sxi3VvgOjirvLveIVP7zvqxBDpJzxrF02wCYwnQuxi3S3U5ge
3iHihzhM9qP+N03frkr4KH6Spgec88YjMioVQStTQZcrogTdHweZOgT8tckg
HEmHCF8uHBjD0HbfDk+9zYFtaE3QPk5aGm02Id0fNNM5WmSQSxVwF0Ddryq5
vIU0AHbB/1kok1zJpwWA06SgHenlnYngnSpNWlOn+SxboiD28m2XTWDP5ULL
e1b040VtkQMzpuVXzAHWVQYQWUevJ4y8mrUsqAyGuYSb5pTU28D+NExVAYxn
WD94rzgBpkXgC4Xxcp3TmyfMaLMF4M9ef0nu+QIDAQABo4IC1TCCAtEwCQYD
VR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSpNAr06FueusUfmbDdecnZ1kznsTAfBgNVHSME
GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0
YXVnaC5jb20wggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIB
KjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5
LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3Vl
ZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJl
bWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25s
eSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0
aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmg
J4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYI
KwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRz
c2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRw
Oi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5j
YS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0G
CSqGSIb3DQEBCwUAA4IBAQC3OSsHtuc1se2JPbLqI1b31i0EER3UX6Ep2Zuy
FkACIpk/i8mPi0KIfMWWiDlNmqeQEq8308i0/2mVcMVdgKWIUMJdZb3CmNfs
3qtTlrdXXYXT7ZLjL6a1Bbh/lKUm35JYRH8zf3rqDbLkpiA92vc7uTQcbDay
1sQ4CSTvOWuq0CIwMXqJePhHf/runG7ndDuX2yFagHlxhsvn7raw5NQuu4Sj
ofwbNiszwkryB7ZYUxq2Pg2i1m2XlgMbNEfw8deAZOyHGKKGz25Ei1KvJofH
1izh0WDU+ueJum6RHm8/o/i53MbYZN4Il64aBD1HPqQow3jHQBhAc8XN85hH
csS2MYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZp
Y2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCVhGMAkGBSsOAwIaBQCggdgw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQw
NDE3MDQwMzAwWjAjBgkqhkiG9w0BCQQxFgQUd2ksfL2lCU+ECKJ/GRkRYOhs
SsEweQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEW
MAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEggEAEt1z9uTBZBIEqLyQ7VmmRz+5Shhi9TFCwdsTnEIzEO8XhlWN
Miy+++PwZxVy3PyXwD1XO0PdEKWIQ0watTlKO37U7Q81LYRg05LgLSpI4l94
kkOy+/dhzyzhnHyXZ+mxYUx2Wm1WEt+woCAHjhbKi4wNWZ/nijbbTPllwe2o
C6ILdrXJDdkc6YGDGsyniQ3UDhMy2LzhKUXaFIkWVOQvTIkztbHOsUWOdovq
EjbeiAbFpCCn7PaAjPtiqbKiQiqa06vExrp2smkmGr0vNBAL/33QW4rtY5Zq
4awMoWyvYoCCEYYErIP4evPqQHIT3ODAg/HKqojuOQsAKqNYsrYc1w==

--3825401791-506175694-1397707381=:2194--


From nobody Wed Apr 16 21:13:12 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 061311A03FE for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 21:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 5TLKVIScaGqH for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 21:13:04 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 872DE1A0054 for <ietf@ietf.org>; Wed, 16 Apr 2014 21:13:04 -0700 (PDT)
Received: (qmail 76071 invoked from network); 17 Apr 2014 04:13:00 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=12926.534f54cc.k1404; bh=LVvQnMgsOP6yBPVeHNDULrL8IQPisdao2FhmFaHEUl4=; b=Ep2jNL2LZOcTaib9hvjhWXPqsqeeiIsrfKw6vjl2zoS5bqQD/g80BcOlUcx0l1QcJMw2ist5WslfnW0ONZUDJepev6xAhyvJ3YU6Lo3W91dIghkg3L7OKRp6Y8Nk/PeZvNF6ACMfAHfO7XNbTiuDF3ZNo9WwCrkp0nCNnvIvDoArWAVqsJBSC6QGrOAFLeH90AxTlN6zI+cD1wYtE56N538g5TyQ4HLD0gZGBNxjqvnu0qeseRbLVHSM+kbkj1Ys
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=12926.534f54cc.k1404; bh=LVvQnMgsOP6yBPVeHNDULrL8IQPisdao2FhmFaHEUl4=; b=ChsVtdscmz83owxrf/BdWEoIai4pClv5BVQ6ZNdRYqOiNQa+P+xcMHt4dYHgZAGkI+6jXqgu3u7H/VE3mm7kh5d4mDRREPzJnI6ucTIsY0KLXV7BN23IxUsFaPyhtdYZmEFIN2SMu3WDPX9NCgFOf1DOd6vstLdgG4JGuYCDxlYZTuMIFxYiP6h+GnuJKCZzDvju7Goz5whUTPa/VMGbMhANWmi8SGGpTf5nSUCWTjl2j04NFtV9OfvqkzjtGvsD
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 17 Apr 2014 04:13:00 -0000
Date: 17 Apr 2014 00:12:59 -0400
Message-ID: <alpine.BSF.2.00.1404170008470.2194@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: (DMARC) How a whitelist would work, was Why mailing lists
In-Reply-To: <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-808331804-1397707980=:2194"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zxUiLGhmaGJ_a_M50oyeYakftfI
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 04:13:09 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-808331804-1397707980=:2194
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> Do you envision each operator maintaining its own whitelist, or one or more
> public registries of them, or something else?

On the assumption that we have reasonably good agreement about what would 
qualify for DMARC whitelisting, I'd think you'd want a small set (maybe 
only one) of public whitelists.

If each receiver has to do its own whitelist, that means that nobody bug a 
big gorilla who can afford to create a whitelist can apply DMARC policies.

R's,
John
--3825401791-808331804-1397707980=:2194
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIII7gYJKoZIhvcNAQcCoIII3zCCCNsCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBh8wggYbMIIFA6ADAgECAgMJWEYwDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xNDAzMTgxOTQ3NDdaFw0xNTAzMjAwMDU2MDBaMDoxGDAW
BgNVBAMMD2pvaG5sQHRhdWdoLmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxA
dGF1Z2guY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnMGH
52DBxB4jb86Sxi3VvgOjirvLveIVP7zvqxBDpJzxrF02wCYwnQuxi3S3U5ge
3iHihzhM9qP+N03frkr4KH6Spgec88YjMioVQStTQZcrogTdHweZOgT8tckg
HEmHCF8uHBjD0HbfDk+9zYFtaE3QPk5aGm02Id0fNNM5WmSQSxVwF0Ddryq5
vIU0AHbB/1kok1zJpwWA06SgHenlnYngnSpNWlOn+SxboiD28m2XTWDP5ULL
e1b040VtkQMzpuVXzAHWVQYQWUevJ4y8mrUsqAyGuYSb5pTU28D+NExVAYxn
WD94rzgBpkXgC4Xxcp3TmyfMaLMF4M9ef0nu+QIDAQABo4IC1TCCAtEwCQYD
VR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSpNAr06FueusUfmbDdecnZ1kznsTAfBgNVHSME
GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0
YXVnaC5jb20wggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIB
KjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5
LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3Vl
ZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJl
bWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25s
eSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0
aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmg
J4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYI
KwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRz
c2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRw
Oi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5j
YS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0G
CSqGSIb3DQEBCwUAA4IBAQC3OSsHtuc1se2JPbLqI1b31i0EER3UX6Ep2Zuy
FkACIpk/i8mPi0KIfMWWiDlNmqeQEq8308i0/2mVcMVdgKWIUMJdZb3CmNfs
3qtTlrdXXYXT7ZLjL6a1Bbh/lKUm35JYRH8zf3rqDbLkpiA92vc7uTQcbDay
1sQ4CSTvOWuq0CIwMXqJePhHf/runG7ndDuX2yFagHlxhsvn7raw5NQuu4Sj
ofwbNiszwkryB7ZYUxq2Pg2i1m2XlgMbNEfw8deAZOyHGKKGz25Ei1KvJofH
1izh0WDU+ueJum6RHm8/o/i53MbYZN4Il64aBD1HPqQow3jHQBhAc8XN85hH
csS2MYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZp
Y2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCVhGMAkGBSsOAwIaBQCggdgw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQw
NDE3MDQxMjU5WjAjBgkqhkiG9w0BCQQxFgQUB2DdHOTaKJHdw9RmSZp/OBki
WxEweQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEW
MAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEggEAgFh6Whdiq31/REcSSgynoUmYjIp6hf/NhpOVEUE/6zkNM852
kDlOijWORXTEab15/sf5Uit210FRudIPwBHnxYXgNx4r95inJwYTij7v9jgJ
KrCaIcH01DzYEmq6JuypMOKTCHRnXHwXa4fU1zUtS8SGPNKZt1LQ81gPsxrN
+e06/9MimQEqXspMSE9vu0MzynUQAlHBt7jmDc3wTSO28WgvPk9BWEujjWEV
1L2lccZqN9aaT2nn4RPtpHVnBhATdEXdNl/qBO43Ya4zthFdHUkz0KFPxQ3R
4PLo/9K6C84dpOISfIGt33zHuxtgQXws5oTOdwQcoTNGcXefvOOmdQ==

--3825401791-808331804-1397707980=:2194--


From nobody Wed Apr 16 21:54:11 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0EC4B1A0458 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 21:54:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level: 
X-Spam-Status: No, score=-4.573 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 V-C8rYsl_8QF for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 21:54:07 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 839E61A0454 for <ietf@ietf.org>; Wed, 16 Apr 2014 21:54:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397710444; x=1429246444; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=rk+ooJq3WVRrTDb06jYRWAREyOArtu4n3eumoSEGlrE=; b=o9rOHz8Pu+DMRjVMlDGiwud2zp1yArQsKguZGMK7BC6rYAcu31Y6zRJH cmf73Ik6wC5wenUJWI0l6n2JP4arC4VyANhZq88TaaTug8/72nQhQEt28 qHRZQNUdx4xWD+sl47eH/em6ZVyoxwIPb6WvuU6XCp4ZLNt4bYCqc0TVj A=;
X-IronPort-AV: E=McAfee;i="5400,1158,7410"; a="120400675"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine02.qualcomm.com with ESMTP; 16 Apr 2014 21:54:03 -0700
X-IronPort-AV: E=Sophos;i="4.97,876,1389772800"; d="scan'208";a="650347367"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 16 Apr 2014 21:54:03 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 16 Apr 2014 21:54:03 -0700
Message-ID: <534F5E67.1010307@qti.qualcomm.com>
Date: Wed, 16 Apr 2014 23:53:59 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com> <alpine.BSF.2.00.1404162346400.2194@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1404162346400.2194@joyce.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lE_UlZ9-PrIhNoMTC_bqXH91tho
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 04:54:10 -0000

On 4/16/14 11:03 PM, John R Levine wrote:
>> The originator (well, more to the point, the originator's mail 
>> server) doesn't need a signal that it's a mailing list; it's simply 
>> that the destination makes an "if I forward the mail, I'll be 
>> including this" piece of data available, and the originator's server 
>> can then include that in the signature of the message. I was thinking 
>> this could be in some special kind of DMARC (or whatever) record that 
>> lived in the mailing list's domain and could be queried by the 
>> originator's server.
>
> The magic token has to be cryptographically tied to the contents of 
> the original message

No it doesn't. It has to be cryptographically tied to the mailing list's 
re-sending of the message. How to do that with asymmetric keys should be 
discussed somewhere other than on this list.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Wed Apr 16 23:23:29 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DE3E1A03D6 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 23:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.794
X-Spam-Level: **
X-Spam-Status: No, score=2.794 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 KY1359IdR4pM for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 23:23:22 -0700 (PDT)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 942291A0025 for <ietf@ietf.org>; Wed, 16 Apr 2014 23:23:22 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6QCN4KXLC006LNP@mauve.mrochek.com> for ietf@ietf.org; Wed, 16 Apr 2014 23:18:17 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6O0FD8M9S00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 16 Apr 2014 23:18:07 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6QCMYYMJ000004W@mauve.mrochek.com>
Date: Wed, 16 Apr 2014 23:00:42 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Mon, 14 Apr 2014 10:53:42 -0700" <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9DhqT44K-SMn9OD2vJ66TrVpvtg
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 06:23:26 -0000

> On Sat, Apr 12, 2014 at 4:35 PM, <ned+ietf@mauve.mrochek.com> wrote:

> > The underlying technical issue is that the two technologies DMARC is built
> > on -
> > DKIM and SPF - both attach additional/restrictive semantics to
> > longstanding mail
> > system fields. (Broadly speaking, From: for DKIM and MAIL FROM for SPF.)
> >

> Something's amiss here.  What new semantics does DKIM attach to From:?  As
> far as I know, it only requires that the field be signed.  It doesn't
> require that it be interpreted in a particular way or that it contain any
> particular value.

I was trying to be brief. Yes, I'm well aware that DKIM can be used in other
ways. This entire discussion is within the context of DMARC here. Do you
disagree that DMARC's use of DKIM and SPF assign additional semantics to header
and envelope from fields respectively?

> > Like it or not, the IETF published a draft that defines certain mechanisms
> > which, if used improperly by a large provider, cause serious problems for a
> > large number of people. The text describing the consequences of the use of
> > those mechansisms in the drafts is, IMO, entirely inadequate.
> >

> It's the same document that was posted on other web sites for some time,
> and was in use by a number of operators (including Yahoo) long before it
> went into the datatracker.

So?

> As it's only a draft, there's ample opportunity to make such improvements.

You're missing the point. When Yahoo made this change wouldn't it have been
nice to be able to point to the draft and say, "This is explicitly contrary
to what the draft says"?

> Also: By "the IETF published a draft", are you talking about an RFC, or the
> DMARC base draft?

The draft, of course.

> It seems extreme to lay blame on the IETF in general
> merely for having an open mechanism by which to post a draft for all to see
> and discuss.  A "Request For Comment", as it were. 

You may think it extreme. I don't. I think the IETF's politics have led to  it
inching closer to moral hazard territory for a long time, and with this
incident it has stepped in it.

> Are you suggesting that
> process should be closed or moderated somehow?

What I suggested is that we need to have a serious discussion of what, if
anything can be done to ameliorate the damage in this case. Others have
suggested that we also need to look at how to prevent this from happening
in the future. I concur.

> > And it's not like we didn't know. As others have pointed out, this issue
> > existed in the earlier ADSP proposal. It was given insufficient attention
> > there as well.

> As with any draft, its content is only as good as its contributions and the
> reviews it got.

I hope you're not saying that this is now fault of the people who failed to
contribute to the draft.

> > Of course the IETF can fall back on the usual excuses, including, but not
> > limited to:
> >
> >     Yahoo, of all ISPs, should have known better
> >     We don't tell people what to do
> >     It was just a draft
> >     It was never intended to be a standard
> >     We're not the Internet Protocol Police
> >     etc.
> >
> > I'm sorry, but this time none of these dogs are hunting for me. An
> > attractive
> > nuisance is an attractive nuisance, and this is what the IETF has, albeit
> > with
> > the best of intentions, managed to create.
> >

> I would add to this that, by its ultimate inaction in the face of a
> protracted period of abuse and attempts by participants to solve that
> problem within its procedures, the IETF has abdicated any authority it may
> have had.

That may be your assessment. Given subsequent comments from other people,  mine
is now that this effort was looking for a rubber stamp, didn't like it when
that didn't happen, and proceeded to skirt around the edges of the process.

With disasterous results.

				Ned


From nobody Wed Apr 16 23:35:41 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D813D1A0492 for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 23:35:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 Wmx893FaIXTR for <ietf@ietfa.amsl.com>; Wed, 16 Apr 2014 23:35:33 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 9F5B01A006D for <ietf@ietf.org>; Wed, 16 Apr 2014 23:35:33 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id wn1so21571obc.37 for <ietf@ietf.org>; Wed, 16 Apr 2014 23:35:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i0+/2gn+06ogmXcGQLaHixSOo5YsLewtQgxNIgRSv8U=; b=WzYDPUwo5dXG/BKZka7IHbt6VhdMH3JeJ6ikvN6yoPAqFiTd5KXoAoXRTAQ44XmVpF W9NDPq+d2SOWuep5CIIMN0IXbjxEll8poUZlomCY8+q8csBYm/xqGlx14e1sAAwNhTZF 7ONJCxOaFOs/WwTskTWTVReobKiiPxRhyHl3M=
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:content-type; bh=i0+/2gn+06ogmXcGQLaHixSOo5YsLewtQgxNIgRSv8U=; b=ZCYX2JMyCaSAOpeRIMJMnXiooENwQi7HGE91K1jlWmLFDaatcouBJEyKhIRZsNz6lY A2hk34+TDIBn3XwC1vMfYVx2ddE75aN9gg3cv5SDfS4lnAQ2Lt5kcNgyWaG+TlWhRcEQ LFdu5tqLxLwKKnLt1Rs7DYckFhfQqmjypQ7ItNmWGAf9mlN5mLH0s/gU+Cqx2+EzFZfl 8e+miuoWB4UagHi8+dWdNANVkzJyMNaQBlI7UEN0/6G2wSfg5zZqWh037G6B9KEmId6F ZYgrMHfQgdyzXztpILhvnrikwXPwCCj+lGRioSW2rrTfcHZbT4CeemAYsDEvDwNLHyah rnHw==
X-Gm-Message-State: ALoCoQlmUFa23sd2QJXLblZqVgMEjM3D0U4SpdZW/bljGSCIcqsXKio0qq452y2qnb8A8a7EqXcV
MIME-Version: 1.0
X-Received: by 10.60.37.166 with SMTP id z6mr10422943oej.22.1397716530190; Wed, 16 Apr 2014 23:35:30 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Wed, 16 Apr 2014 23:35:30 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1404161654430.2065@joyce.lan>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan>
Date: Thu, 17 Apr 2014 07:35:30 +0100
Message-ID: <CAKHUCzwZ29TAAjJ3_w+0aaoN-L2o+CGHYaMQ=TOEqYdVn5rQHg@mail.gmail.com>
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: Dave Cridland <dave@cridland.net>
To: John R Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=089e013c6856477fb004f7373de5
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PhaFMQ5p8lUskK6qQUG4Q_OTaig
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 06:35:38 -0000

--089e013c6856477fb004f7373de5
Content-Type: text/plain; charset=UTF-8

On 16 April 2014 21:57, John R Levine <johnl@taugh.com> wrote:

> This means that mailing lists (and other forwarding cases) are enforced
>> into having DMARC records in order to forward DMARC originating messages,
>> which seems reasonable, and the Sender addresses must also be relatively
>> sensible, which they normally are already.
>>
>
>  I may be missing something.
>>
>
> How do I distinguish the nice mailing lists at ietf.org from random evil
> spammer domains sending spam with List-ID headers?
>
> Every proposal I've seen like this ends up tripping over the fact that
> there is no technical way to distinguish between mail from real mailing
> lists and spam that looks like it's from mailing lists.  Hence you need a
> whitelist for the real mail, at which point all of the mechanism beyond the
> key for the whitelist (probably a DKIM signature) is superfluous.
>
>
There's no more need for whitelist here than on DMARC mail as things stand,
of course, but it does mean that senders need tracking as well as authors,
and senders need to be explicit and reliable. I'd assume reputation
services (of which whitelists are just an extreme case) would be in play
regardless.

Let's consider the message to which I am replying.

Right now, my MUA treats this as a message "From John R Levine <
johnl@taugh.com>". This means that any policy on the message origination
comes from looking solely at the taugh.com domain. We'll pretend it has a
DMARC policy. Herein lies the Yahoo/DMARC issue, because unless your policy
essentially stipulates that the IETF is allowed to spoof you, we're stuck.

What I'm suggesting is not that, but that my MUA notes that the poloicy of
taugh.com allows different senders, and switches to considering the sender
domain - in this case, ietf.org. Any p or sp tag in the ietf.org policy is
ignored, however, and treated as p=reject/sp=reject; in addition since
taugh.com has a DMARC policy, it must also have one to forward taugh.comemail.

My spam filtering now has two cases to consider: Firstly, it needs to
decide whether ietf.org is behaving legitimately, and secondly whether I
want to read mail from you.

You can put it another way, too - my proposal is essentially saying that
the From dictates failure policy, reporting, and handling, but the Sender
is used for enforcement.

One additional thing is required from MUAs, though, which is to ensure the
UI clearly shows that the message is not sent by you (directly, at least);
this allows a human reader to easily see it's a mailing list message - or
for that matter easily see it's from an unexpected sender.

Dave.

--089e013c6856477fb004f7373de5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
6 April 2014 21:57, John R Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:j=
ohnl@taugh.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
This means that mailing lists (and other forwarding cases) are enforced<br>
into having DMARC records in order to forward DMARC originating messages,<b=
r>
which seems reasonable, and the Sender addresses must also be relatively<br=
>
sensible, which they normally are already.<br>
</blockquote>
<br>
</div><div class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I may be missing something.<br>
</blockquote>
<br></div>
How do I distinguish the nice mailing lists at <a href=3D"http://ietf.org" =
target=3D"_blank">ietf.org</a> from random evil spammer domains sending spa=
m with List-ID headers?<br>
<br>
Every proposal I&#39;ve seen like this ends up tripping over the fact that =
there is no technical way to distinguish between mail from real mailing lis=
ts and spam that looks like it&#39;s from mailing lists. =C2=A0Hence you ne=
ed a whitelist for the real mail, at which point all of the mechanism beyon=
d the key for the whitelist (probably a DKIM signature) is superfluous.<div=
 class=3D"HOEnZb">
<div class=3D"h5"><br></div></div></blockquote><div><br></div><div>There&#3=
9;s no more need for whitelist here than on DMARC mail as things stand, of =
course, but it does mean that senders need tracking as well as authors, and=
 senders need to be explicit and reliable. I&#39;d assume reputation servic=
es (of which whitelists are just an extreme case) would be in play regardle=
ss.</div>
<div><br></div><div>Let&#39;s consider the message to which I am replying.<=
/div><div><br></div><div>Right now, my MUA treats this as a message &quot;F=
rom John R Levine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a=
>&gt;&quot;. This means that any policy on the message origination comes fr=
om looking solely at the <a href=3D"http://taugh.com">taugh.com</a> domain.=
 We&#39;ll pretend it has a DMARC policy. Herein lies the Yahoo/DMARC issue=
, because unless your policy essentially stipulates that the IETF is allowe=
d to spoof you, we&#39;re stuck.</div>
<div><br></div><div>What I&#39;m suggesting is not that, but that my MUA no=
tes that the poloicy of <a href=3D"http://taugh.com">taugh.com</a> allows d=
ifferent senders, and switches to considering the sender domain - in this c=
ase, <a href=3D"http://ietf.org">ietf.org</a>. Any p or sp tag in the <a hr=
ef=3D"http://ietf.org">ietf.org</a> policy is ignored, however, and treated=
 as p=3Dreject/sp=3Dreject; in addition since <a href=3D"http://taugh.com">=
taugh.com</a> has a DMARC policy, it must also have one to forward <a href=
=3D"http://taugh.com">taugh.com</a> email.</div>
<div><br></div><div>My spam filtering now has two cases to consider: Firstl=
y, it needs to decide whether <a href=3D"http://ietf.org">ietf.org</a> is b=
ehaving legitimately, and secondly whether I want to read mail from you.</d=
iv>
<div><br></div><div>You can put it another way, too - my proposal is essent=
ially saying that the From dictates failure policy, reporting, and handling=
, but the Sender is used for enforcement.</div><div><br></div><div>One addi=
tional thing is required from MUAs, though, which is to ensure the UI clear=
ly shows that the message is not sent by you (directly, at least); this all=
ows a human reader to easily see it&#39;s a mailing list message - or for t=
hat matter easily see it&#39;s from an unexpected sender.</div>
<div><br></div><div>Dave.</div></div></div></div>

--089e013c6856477fb004f7373de5--


From nobody Thu Apr 17 00:08:21 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77BF01A0464 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 00:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 OxAJhJo1B6DC for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 00:08:14 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 088451A0083 for <ietf@ietf.org>; Thu, 17 Apr 2014 00:08:13 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id uo5so57940pbc.4 for <ietf@ietf.org>; Thu, 17 Apr 2014 00:08:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=8keqasVNCv9owhQD/cc8GQgfQxW0TmjCkccBUsGJlME=; b=yn2v3230l4Vot/U6c2l73TLF9+728dgwU4aTx8+A3qsaJctp1KMuwLN2pZi2zSsl2+ BQ7fJOdmUKNO9gNJCJbAyt71YJAlmXaS7fKt5qpo4ZNMj9ocQp5lGDLDgBumPC2mdR6d TMojxjEzuYWcpqFA0FqMgJZxuhSJcoRC5AQubqJAYDvP+QXI6a+mzo7K3HOSLA7zOYpl 4W82sgg/daWz96UAeJihJRDRfq1JAPMIvM1ET3CwUs47k7hl2qTYE8RWhBGMR/tVSj/l ttIUraC/tA7gpYs1m3f0buWaAbH6mG/mhWCN6bW+G16Pj4g5t3L4n/dLiN/iLm+eMvmB t3Gw==
X-Received: by 10.66.180.34 with SMTP id dl2mr13746865pac.124.1397718490630; Thu, 17 Apr 2014 00:08:10 -0700 (PDT)
Received: from ?IPv6:2601:9:7680:203:c911:e11e:917b:b094? ([2601:9:7680:203:c911:e11e:917b:b094]) by mx.google.com with ESMTPSA id vg1sm51438523pbc.44.2014.04.17.00.08.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 00:08:09 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <01P6QCMYYMJ000004W@mauve.mrochek.com>
Date: Thu, 17 Apr 2014 00:08:08 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <833BDCD2-1157-4914-B385-C300AF33E2D4@gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CsRuzKj_bkSgGr-YED6jJgCJnCU
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 07:08:19 -0000

On Apr 16, 2014, at 11:00 PM, ned+ietf@mauve.mrochek.com wrote:

>> On Sat, Apr 12, 2014 at 4:35 PM, <ned+ietf@mauve.mrochek.com> wrote:
>=20
>>> The underlying technical issue is that the two technologies DMARC is =
built
>>> on -
>>> DKIM and SPF - both attach additional/restrictive semantics to
>>> longstanding mail
>>> system fields. (Broadly speaking, From: for DKIM and MAIL FROM for =
SPF.)
>>>=20
>=20
>> Something's amiss here.  What new semantics does DKIM attach to =
From:?  As
>> far as I know, it only requires that the field be signed.  It doesn't
>> require that it be interpreted in a particular way or that it contain =
any
>> particular value.
>=20
> I was trying to be brief. Yes, I'm well aware that DKIM can be used in =
other
> ways. This entire discussion is within the context of DMARC here. Do =
you
> disagree that DMARC's use of DKIM and SPF assign additional semantics =
to header
> and envelope from fields respectively?

Dear Ned,

Murray is correct. DKIM does not create special =46rom header field =
semantics.  However, DMARC semantics are similar to those of ADSP while =
avoiding some shortcomings.
=20
>>> Like it or not, the IETF published a draft that defines certain =
mechanisms
>>> which, if used improperly by a large provider, cause serious =
problems for a
>>> large number of people. The text describing the consequences of the =
use of
>>> those mechansisms in the drafts is, IMO, entirely inadequate.
>>>=20
>=20
>> It's the same document that was posted on other web sites for some =
time,
>> and was in use by a number of operators (including Yahoo) long before =
it
>> went into the datatracker.
>=20
> So?
>=20
>> As it's only a draft, there's ample opportunity to make such =
improvements.
>=20
> You're missing the point. When Yahoo made this change wouldn't it have =
been
> nice to be able to point to the draft and say, "This is explicitly =
contrary
> to what the draft says"?

Agreed.

>> Also: By "the IETF published a draft", are you talking about an RFC, =
or the
>> DMARC base draft?
>=20
> The draft, of course.
>=20
>> It seems extreme to lay blame on the IETF in general
>> merely for having an open mechanism by which to post a draft for all =
to see
>> and discuss.  A "Request For Comment", as it were.=20
>=20
> You may think it extreme. I don't. I think the IETF's politics have =
led to  it
> inching closer to moral hazard territory for a long time, and with =
this
> incident it has stepped in it.

This disruption should be shared with the provider that has already =
enumerated 30,000 mailing-lists but made no effort to establish a means =
to verify these sources and to safely assert specific exceptions to =
DMARC alignment requirements. This ability is desperately needed before =
applying DMARC reject on user accounts.  I'll be happy to modify either =
ATP or ATPS to permit these exceptions without the need to alter =
mailing-list.=20

>> Are you suggesting that
>> process should be closed or moderated somehow?
>=20
> What I suggested is that we need to have a serious discussion of what, =
if
> anything can be done to ameliorate the damage in this case. Others =
have
> suggested that we also need to look at how to prevent this from =
happening
> in the future. I concur.
>=20
>>> And it's not like we didn't know. As others have pointed out, this =
issue
>>> existed in the earlier ADSP proposal. It was given insufficient =
attention
>>> there as well.
>=20
>> As with any draft, its content is only as good as its contributions =
and the
>> reviews it got.
>=20
> I hope you're not saying that this is now fault of the people who =
failed to
> contribute to the draft.

These comments were made more than one year ago and ignored.

>>> Of course the IETF can fall back on the usual excuses, including, =
but not
>>> limited to:
>>>=20
>>>    Yahoo, of all ISPs, should have known better
>>>    We don't tell people what to do
>>>    It was just a draft
>>>    It was never intended to be a standard
>>>    We're not the Internet Protocol Police
>>>    etc.
>>>=20
>>> I'm sorry, but this time none of these dogs are hunting for me. An
>>> attractive
>>> nuisance is an attractive nuisance, and this is what the IETF has, =
albeit
>>> with
>>> the best of intentions, managed to create.
>>>=20
>=20
>> I would add to this that, by its ultimate inaction in the face of a
>> protracted period of abuse and attempts by participants to solve that
>> problem within its procedures, the IETF has abdicated any authority =
it may
>> have had.
>=20
> That may be your assessment. Given subsequent comments from other =
people,  mine
> is now that this effort was looking for a rubber stamp, didn't like it =
when
> that didn't happen, and proceeded to skirt around the edges of the =
process.
>=20
> With disasterous results.

Agreed. They seemed motivated into creating a system finely tuned for =
bulk senders while ignoring needs of individual users.  After all, bulk =
mailers contribute to their bottom line, but they may find users voting =
with their feet which may have the effect of reducing ad revenues due to =
fewer eyeballs.

Regards,
Douglas Otis=


From nobody Thu Apr 17 00:57:43 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66F771A0011 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 00:57:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.872
X-Spam-Level: 
X-Spam-Status: No, score=-2.872 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 rSreUDTz0sWS for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 00:57:38 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3275A1A0100 for <ietf@ietf.org>; Thu, 17 Apr 2014 00:57:34 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WahCI-000A8s-Hk; Thu, 17 Apr 2014 03:57:26 -0400
Date: Thu, 17 Apr 2014 03:57:21 -0400
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Message-ID: <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com>
In-Reply-To: <01P6QCMYYMJ000004W@mauve.mrochek.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MPerzicgaIiBhdhkVjeL5BtE-oc
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 07:57:42 -0000

--On Wednesday, April 16, 2014 23:00 -0700
ned+ietf@mauve.mrochek.com wrote:

>> It seems extreme to lay blame on the IETF in general
>> merely for having an open mechanism by which to post a draft
>> for all to see and discuss.  A "Request For Comment", as it
>> were. 
> 
> You may think it extreme. I don't. I think the IETF's politics
> have led to  it inching closer to moral hazard territory for a
> long time, and with this incident it has stepped in it.

Indeed.  We have had warnings about where the ability of anyone
to post anything and then claim IETF approval in external
contexts without any fear of meaningful pushback would lead for
a long time.  It hasn't been significantly damaging before
because (i) we have been lucky and (ii) attempts to manipulate
the mechanisms have come from outsiders, not insiders.  With
DMARC, the ability to claim IETF responsibility when that is
handy and that the IETF has no control when _that_ is handy have
now been utilized by insiders.  That comes after a history of
the less effective approach of bringing specs into IETF WGs and
then claiming that fundamentals cannot be changed because they
were developed by experts in another forum.  As I think Ned
suggested, the ADSP issue and how it was handled should have
been another warning sign.  And, with Yahoo's move and its
consequences (whether they anticipated them or not), we also ran
out of luck.

>> Are you suggesting that
>> process should be closed or moderated somehow?
> 
> What I suggested is that we need to have a serious discussion
> of what, if anything can be done to ameliorate the damage in
> this case. Others have suggested that we also need to look at
> how to prevent this from happening in the future. I concur.

agreed.

>...
>> I would add to this that, by its ultimate inaction in the
>> face of a protracted period of abuse and attempts by
>> participants to solve that problem within its procedures, the
>> IETF has abdicated any authority it may have had.
> 
> That may be your assessment. Given subsequent comments from
> other people,  mine is now that this effort was looking for a
> rubber stamp, didn't like it when that didn't happen, and
> proceeded to skirt around the edges of the process.

> With disasterous results.

Exactly.

I'm also concerned that several of these efforts represent back
door approaches to deprecating multi-hop email.  Certainly many
things are more convenient in a single hop environment.  They
would become even more convenient if all email were to be
handled by a small oligarchy of providers.  To the degree to
which one simultaneously believes in openness and privacy, those
would be very sad outcomes.

    john



From nobody Thu Apr 17 03:04:03 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8FEA1A009E for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 03:04:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 umJwa52XIZGP for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 03:03:58 -0700 (PDT)
Received: from st11p02mm-asmtp002.mac.com (st11p02mm-asmtp002.mac.com [17.172.220.237]) by ietfa.amsl.com (Postfix) with ESMTP id EC4051A0090 for <ietf@ietf.org>; Thu, 17 Apr 2014 03:03:57 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N4600M646M6VE00@st11p02mm-asmtp002.mac.com> for ietf@ietf.org; Thu, 17 Apr 2014 10:03:52 +0000 (GMT)
Subject: Re: What I've been wondering about the DMARC problem
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <534EE9EA.9060403@gmail.com>
Date: Thu, 17 Apr 2014 11:03:41 +0100
Message-id: <09B6AA22-9D1D-4EE4-AB27-2506A1E08EDA@me.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <2478F2D1-2E08-45D7-86A2-36443959E272@me.com> <534EE9EA.9060403@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaEhEKTEMXGx0EGx0YBBIZBBscEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsbGmJCH2lmGH8bGXhzB xliGxoaGVseEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGxwQGx4aHxsRCl5ZF2FCf19 AEQpMRhdia2sRCkNaFxgbGQQbGBkEGxMYBBkaEQpEWBcZEQpESRcYEQpCRRdmUH1dH21kGgVIY xEKQk4XbHBgeUAdYlJpGmIRCkJMF2dJH215aRh+ckJNEQpCbBdlaGUYbU0cGENGThEKQkAXZxx nXkJkY1Ibc2QRCnBnF2ZCHX1MfBtIZlBMEQpwaBdge1pQcBtCWVlrRhEKcGgXbkZ8fmxMZmRnT 0ARCnBoF2wYZVJkbGEaQ3tdEQpwaBdoHGgaHn5texJ/RREKcGgXaFNJZUlvUlNibUQRCnB/F2h LZ3xle0VbWkx8EQpwXxdnQF1oR2N9axpAZBEKcGwXa2ZOa0FlX2ZTZwERCnBMF2caU2xAa0BtH 0NaEQ==
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-17_03:2014-04-17,2014-04-17,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404170150
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OzaTvOBhyuZTe_5hehpCP0UtReI
Cc: Jim Fenton <fenton@bluepopcorn.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 10:04:02 -0000

On 16 Apr 2014, at 21:36, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> On 16/04/2014 18:58, Sabahattin Gucukoglu wrote:
>> On 15 Apr 2014, at 21:38, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>> The mailman fix is worse than the disease. I think the .INVALID fix is
>>> much better, because Reply-all will still work.
>> 
>> Reply-all should still work with the Mailman fix; 
> 
> It doesn't work *properly*. Firstly, this message wouldn't be sent
> to you with CC to the list, which is the correct semantic.
> If you weren't a subscriber, you would never see it. Secondly,

Sorry, but I appear to be confused.

The Reply-To: field is adjusted to be the author's address, on a discussion list like this where replies go back to the authors.  Just in case we're talking across purposes somehow and to avoid all doubt, the fix we are talking about is described here:
http://www.dmarc.org/supplemental/mailman-project-mlm-dmarc-reqs.html

Unless your MUA is doing something very unusual, and some do, then pressing "Reply all" should produce a message addressed to me, with a CC that contains the remainder of the recipient addresses.  The From: is completely irrelevant.

I'm just waiting to be told that I've missed the obvious. :)

Now, FWIW, a better way is as has been suggested here, namely to synthesise addresses for each subscriber.  That's how I'd do it: every mailing list post has its From: rewritten, like:
ietf-resend+brian.e.carpenter=gmail.com@ietf.org

That address remails to you, first checking that a subscriber of the list is recognised.  In the process, it performs the same transformation on the From: field of the message, so as to pass SPF alignment.  It is hoped that your interlocutor happens to be on the list, also, or that you are still on the list when he is trying to contact you.

> the first line above would read:
> 
> On 16/04/2014 18:58, IETF discussion list wrote:
> 
> which is untrue.

It isn't necessary to change the personal name.  Some MUAs may very cleverly add one in the absence of one, or store it in an address book, though, incorrectly.  With the resend method above this issue is less problematic; furthermore the list software can add "(via listname)" to make the distinction less confusing.

No, none of these suggestions are perfect.  I'm not looking for a perfect solution though, I'm looking for one that works, for now.  Throwing people off my lists *is not* an option.

Cheers,
Sabahattin


From nobody Thu Apr 17 03:50:44 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DB6B1A00ED for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 03:50:42 -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, SPF_PASS=-0.001] autolearn=ham
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 vP6v88tCSMxa for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 03:50:37 -0700 (PDT)
Received: from mail-we0-x233.google.com (mail-we0-x233.google.com [IPv6:2a00:1450:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0F11A004D for <ietf@ietf.org>; Thu, 17 Apr 2014 03:50:37 -0700 (PDT)
Received: by mail-we0-f179.google.com with SMTP id x48so266010wes.24 for <ietf@ietf.org>; Thu, 17 Apr 2014 03:50:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=otXWgoX0UMYM4gLQLugpE2SgVluv3QqluuTFuHS9Ei0=; b=z0L4RoWxPEikJjmOeqew1EuxLiql3yCejjGk457zfqtRbQ9Le57lHC/IlYPVQ7vxbe uTcpus3bkWQ5SJiMFDN7+YTudCqASA3YFTZckYrUVggUbXoHbBVka28uedsEedtSvpcD rTISJPm69TE4xPiPgtcj/nyWaCSp+xyEnk3QDGa3gw7u3V4blSAP4ALU6ColrXDJhrXz WKntHsHsfViuZ9kb+FDzo2XmV50YUf0kzDd7JbehZ9p5XUCTN3UYltvW63GtRfRAYKEh xac8bUvAWhIf24XmYG3lPCq/AAxY2yN8B/ZExQbWqhH9y1IHdQfgyrSGeeKInjbaUtp/ I1YA==
X-Received: by 10.180.93.226 with SMTP id cx2mr23922277wib.16.1397731833344; Thu, 17 Apr 2014 03:50:33 -0700 (PDT)
Received: from [172.24.248.99] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id f1sm4112255wic.19.2014.04.17.03.50.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 03:50:32 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_DCFEA808-620C-440E-8462-CFBB1D82F7DA"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CAKHUCzwZ29TAAjJ3_w+0aaoN-L2o+CGHYaMQ=TOEqYdVn5rQHg@mail.gmail.com>
Date: Thu, 17 Apr 2014 13:50:30 +0300
Message-Id: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAKHUCzwZ29TAAjJ3_w+0aaoN-L2o+CGHYaMQ=TOEqYdVn5rQHg@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JMImcrFG1qz--B0STIJJXgvz_LI
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 10:50:42 -0000

--Apple-Mail=_DCFEA808-620C-440E-8462-CFBB1D82F7DA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 17, 2014, at 9:35 AM, Dave Cridland <dave@cridland.net> wrote:

> On 16 April 2014 21:57, John R Levine <johnl@taugh.com> wrote:
> This means that mailing lists (and other forwarding cases) are =
enforced
> into having DMARC records in order to forward DMARC originating =
messages,
> which seems reasonable, and the Sender addresses must also be =
relatively
> sensible, which they normally are already.
>=20
> I may be missing something.
>=20
> How do I distinguish the nice mailing lists at ietf.org from random =
evil spammer domains sending spam with List-ID headers?
>=20
> Every proposal I've seen like this ends up tripping over the fact that =
there is no technical way to distinguish between mail from real mailing =
lists and spam that looks like it's from mailing lists.  Hence you need =
a whitelist for the real mail, at which point all of the mechanism =
beyond the key for the whitelist (probably a DKIM signature) is =
superfluous.
>=20
>=20
> There's no more need for whitelist here than on DMARC mail as things =
stand, of course, but it does mean that senders need tracking as well as =
authors, and senders need to be explicit and reliable. I'd assume =
reputation services (of which whitelists are just an extreme case) would =
be in play regardless.
>=20
> Let's consider the message to which I am replying.
>=20
> Right now, my MUA treats this as a message "=46rom John R Levine =
<johnl@taugh.com>". This means that any policy on the message =
origination comes from looking solely at the taugh.com domain. We'll =
pretend it has a DMARC policy. Herein lies the Yahoo/DMARC issue, =
because unless your policy essentially stipulates that the IETF is =
allowed to spoof you, we're stuck.

<disclaimer> speaking only as an end-user here </disclaimer>

Then perhaps this is what needs to change. John R Levine did not send =
you a message. He sent a message to the list. It is the list software =
that sent you a message. So perhaps the =46rom field should have been =
=93From: IETF Mailing list on behalf of John R Levine <ietf@ietf.org>=94. =
The Reply-To could be set to either John=92s real address or the mailing =
list address, depending on what we think users mean when they click =
=93Reply=94 - reply to John or reply to the list.

Yoav



--Apple-Mail=_DCFEA808-620C-440E-8462-CFBB1D82F7DA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Apr 17, 2014, at 9:35 AM, Dave =
Cridland &lt;<a =
href=3D"mailto:dave@cridland.net">dave@cridland.net</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_extra"><div =
class=3D"gmail_quote">On 16 April 2014 21:57, John R Levine <span =
dir=3D"ltr">&lt;<a href=3D"mailto:johnl@taugh.com" =
target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br><blockquote =
class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
<div class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">
This means that mailing lists (and other forwarding cases) are =
enforced<br>
into having DMARC records in order to forward DMARC originating =
messages,<br>
which seems reasonable, and the Sender addresses must also be =
relatively<br>
sensible, which they normally are already.<br>
</blockquote>
<br>
</div><div class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I may be missing something.<br>
</blockquote>
<br></div>
How do I distinguish the nice mailing lists at <a =
href=3D"http://ietf.org/" target=3D"_blank">ietf.org</a> from random =
evil spammer domains sending spam with List-ID headers?<br>
<br>
Every proposal I've seen like this ends up tripping over the fact that =
there is no technical way to distinguish between mail from real mailing =
lists and spam that looks like it's from mailing lists. &nbsp;Hence you =
need a whitelist for the real mail, at which point all of the mechanism =
beyond the key for the whitelist (probably a DKIM signature) is =
superfluous.<div class=3D"HOEnZb">
<div class=3D"h5"><br></div></div></blockquote><div><br></div><div>There's=
 no more need for whitelist here than on DMARC mail as things stand, of =
course, but it does mean that senders need tracking as well as authors, =
and senders need to be explicit and reliable. I'd assume reputation =
services (of which whitelists are just an extreme case) would be in play =
regardless.</div>
<div><br></div><div>Let's consider the message to which I am =
replying.</div><div><br></div><div>Right now, my MUA treats this as a =
message "=46rom John R Levine &lt;<a =
href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt;". This means =
that any policy on the message origination comes from looking solely at =
the <a href=3D"http://taugh.com/">taugh.com</a> domain. We'll pretend it =
has a DMARC policy. Herein lies the Yahoo/DMARC issue, because unless =
your policy essentially stipulates that the IETF is allowed to spoof =
you, we're stuck.</div>
</div></div></div></blockquote><br></div><div>&lt;disclaimer&gt; =
speaking only as an end-user here =
&lt;/disclaimer&gt;</div><div><br></div><div>Then perhaps this is what =
needs to change. John R Levine did not send you a message. He sent a =
message to the list. It is the list software that sent you a message. So =
perhaps the =46rom field should have been =93From: IETF Mailing list on =
behalf of John R Levine &lt;<a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&gt;=94. The Reply-To =
could be set to either John=92s real address or the mailing list =
address, depending on what we think users mean when they click =93Reply=94=
 - reply to John or reply to the =
list.</div><div><br></div><div>Yoav</div><div><br></div><br></body></html>=

--Apple-Mail=_DCFEA808-620C-440E-8462-CFBB1D82F7DA--


From nobody Thu Apr 17 05:16:24 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58BA71A012B for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 05:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.071
X-Spam-Level: **
X-Spam-Status: No, score=2.071 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_06_12=1.543, RP_MATCHES_RCVD=-0.272] autolearn=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 yVHYeH6fmpb8 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 05:16:16 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 65DAA1A0118 for <ietf@ietf.org>; Thu, 17 Apr 2014 05:16:16 -0700 (PDT)
Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 8D63F276BB8F; Thu, 17 Apr 2014 08:16:12 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_E3BF1549-9A63-45F6-BDA0-4222A64FA4D7"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
Date: Wed, 16 Apr 2014 20:49:50 -0400
Message-Id: <1E0D0E62-CF56-4FEC-9771-206758C80BB6@lucidvision.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com>
To: David Meyer <dmm@1-4-5.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BrDwudC6vjAsq34fyq-TnGUnRWY
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 12:16:21 -0000

--Apple-Mail=_E3BF1549-9A63-45F6-BDA0-4222A64FA4D7
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 14, 2014:11:57 AM, at 11:57 AM, David Meyer <dmm@1-4-5.net> =
wrote:

> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes =
<wesley.george@twcable.com> wrote:
>> I=92m surprised that no one has sent this out yet:
>> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>>=20
>> "Summary: After contributing to standards organizations for more than =
seven
>> years, engineer Vidya Narayanan decided it was time to move on. =
Although she
>> still believes that these organizations make the Internet a better =
place,
>> she wonders about the pace of change versus the pace of =
organizations."
>>=20
>> My thoughts-
>>=20
>> There are some nuggets of truth in what she says in this article, and =
in
>> some of the comments. I think that the problems are real, so there=92s =
value
>> in taking the criticism constructively, despite the fact that the =
author
>> chose to focus on the problems without any suggestions of solutions.
>>=20
>> "while the pace at which standards are written hasn=92t changed in =
many years,
>> the pace at which the real world adopts software has become orders of
>> magnitude faster."
>> =85
>> "Running code and rough consensus, the motto of the IETF, used to be
>> realizable at some point. =85 In the name of consensus, we debate =
frivolous
>> details forever. In the name of patents, we never finish.=94
>> =85
>> "Unless these standards organizations make radical shifts towards
>> practicality, their relevance will soon be questionable.=94
>>=20
>> I don=92t have too many big ideas how to fix these problems, but I=92ll=
 at least
>> take a crack at it in order to spur discussion. My paraphrase of the =
problem
>> and some discussion follows.
>>=20
>> - We=92ve lost sight of consensus and are too often derailed by a =
vocal
>> minority of those willing to endlessly debate a point.
>>=20
>> Part of the solution to that is reiterating what consensus is and is =
not,
>> such as draft-resnick-on-consensus so that we don=92t confuse a need =
for
>> consensus with a need for unanimity. Part of the solution is IETF =
leadership
>> helping to identify when we have rough consensus encumbered by a =
debate that
>> will never resolve itself, without quieting actual disagreement that =
needs
>> continued discussion in order to find a compromise. I don=92t have =
good
>> suggestions on how to make that second half better.
>>=20
>> - We don=92t have nearly enough focus on running code as the thing =
that helps
>> to ensure that we=92re using our limited cycles on getting the right =
things
>> out expediently, and either getting the design right the first time, =
or
>> failing quickly and iterating to improve
>>=20
>> The solution here may be that we need to be much more aggressive at
>> expecting any standards track documents to have running code much =
earlier in
>> the process. The other part of that is to renew our focus on actual =
interop
>> standards work, probably by charter or in-group feedback, shift focus =
away
>> from BCP and info documents. Perhaps when considering whether to =
proceed
>> with a given document, we need test as to whether it=92s actively
>> helpful/needed and ensure that we know what audience would be looking =
at it,
>> rather than simply ensuring that it is =93not harmful=94 and mostly =
within the
>> WG=92s chartered focus.
>=20
> My friend @colin_dixon pointed this out to me yesterday, and I've been
> giving it quite a bit of thought since then (I have a nascent blog on
> the topic of how open source and standards orgs might
> productively/efficiently work together; follow up to
> =
http://www.sdncentral.com/education/david-meyer-reflections-opendaylight-o=
pen-source-project-brocade/2014/03).
>=20
> What I can say is that after seeing the kind of progress that several
> open source communities make (they do epitomize the best of the IETF's
> running code/rough consensus ethic), one does have to wonder if
> traditional standards making is either obsolete or in dire need of a
> make over. What is needed, IMO, is a reimagining of how the standards
> process interacts with the open source movement specifically focused
> on how they can compliment one another.
>=20
> --dmm

	I think its the latter - a make-over or an adjustment are needed =
to how we work within this organization. The pendulum has clearly swung =
so far into the direction of over-caution, over-thinking, and =
over-design (i.e.: requirements, problem statements, architectures and =
frameworks) that the real cost is too high in terms of real dollars =
invested on the process, as well as real product development delay where =
people have to wait for the process to maybe put something out years =
from its onset. We also need to directly address the interference in the =
process by individuals and organizations who will never implement the =
things they are here to "work" on things in theory. In open source, code =
is the coin of the realm, so its very much a "put up or shut up" model; =
opinions don't count for much if anything. So if what you bring to the =
party is a code patch that everyone agrees on, thats cool, but if you =
just say "hey I'd like to add option X or lets do this another way", you =
really are out in the cold. We need to get back to a model where the =
opinions of those implementing things and those really deploying those =
things is what really is what matters.

	Until then, the most important observation is that the process =
has ground nearly to a halt in many areas which has resulted in a severe =
reduction in the speed of innovation. The market has responded and gone =
elsewhere. That is a fact, and denying it is unrealistic. Take note: =
many of us have seen and are involved in real examples of this from even =
traditional service providers, who are now actively demanding open =
source-based products and/or are even trying to launch their own =
agile/open source-based initiatives to foster rapid, collaborative AND =
interoperable product creation in leu of the IETF process.  But we need =
to get back to running code and rough consensus driving the process, =
rather than how things are now.

	--Tom






--Apple-Mail=_E3BF1549-9A63-45F6-BDA0-4222A64FA4D7
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTTyUuAAoJEPcO+I7eiUJZWywP/0mZ2aBpLKI0Vq3QvlMl3ZqV
xqVso5UqQ9uzsUFnCgnZgtWGbEZqCUsEk7PZK4G6oTE0aRgnSpMZ8/JDfRH+GOo6
KWznRT0dPS5BB2Pe0vrDsJ7L69HUwbpjA2Z/z/H3r3Z6XQe0I7WoXVWlL66Cx8Sm
E8BE76X48YnISz9kurnANWOrPP/xfUQu7MpDqxqy9CR9Gy6TA1hbu7zKZmCii7kK
C4Vwm6UpY57IfpzAKQ+HzllI7/RrVXOHIIg50PwGkOPbUJWuYWC7wqt5e/GM/M+G
CM4vw3NnUiq6jtgzyWz70IO3k0JOWa3Y2vS+r4JCNWL1/BGPan3qYQowfJ35q5K3
8724qupSfHxcZQtzzPyuQ3Q7gKSZdMZUqtoaCB9zMsDbkOiEiPRWlJ9Rt6avVzV1
TBWV3xUs1R/B0lyH4rliIduo4I9Zjg4u39/Yh6UTEte9FiAi7V9WwYvckglfdbYF
Hkc2/1YU6qd6eNi5HlvDI2uE5gTlCyMTyKVdW07Vhbf9P+a3IFArWPZ33j6wZsvt
H8F4guLDorRWZb/2qCX5s8yjFeDDHic46KWPu2WXgQij36JT4MeP69Mg79UFVUzc
EtcnQSEZyxFSpBjfLAu6B/XQAkat0cMDuAfVYWcWuy/zrkO/moJgYZSdUq4nByjR
eTWmn6b7DtNVxfnLdC66
=m/fZ
-----END PGP SIGNATURE-----

--Apple-Mail=_E3BF1549-9A63-45F6-BDA0-4222A64FA4D7--


From nobody Thu Apr 17 05:16:26 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6A81F1A0118 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 05:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.071
X-Spam-Level: **
X-Spam-Status: No, score=2.071 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DATE_IN_PAST_06_12=1.543, RP_MATCHES_RCVD=-0.272] autolearn=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 yYlyA2nh9MdU for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 05:16:16 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 679E41A0126 for <ietf@ietf.org>; Thu, 17 Apr 2014 05:16:16 -0700 (PDT)
Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id 59783276BB8A; Thu, 17 Apr 2014 08:16:12 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_F36416B1-8A48-415E-8C82-535EFB19E3B5"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com>
Date: Wed, 16 Apr 2014 20:28:22 -0400
Message-Id: <27F3F43E-683F-440D-9761-DD56CD8FD096@lucidvision.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com> <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com>
To: Alia Atlas <akatlas@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nGmapCy_iyEMniepda0T-z3fn8w
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 12:16:21 -0000

--Apple-Mail=_F36416B1-8A48-415E-8C82-535EFB19E3B5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 14, 2014:12:07 PM, at 12:07 PM, Alia Atlas <akatlas@gmail.com> =
wrote:

> On Mon, Apr 14, 2014 at 11:57 AM, David Meyer <dmm@1-4-5.net> wrote:
>> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes =
<wesley.george@twcable.com> wrote:
>>> I=92m surprised that no one has sent this out yet:
>>> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>>>=20
>>> "Summary: After contributing to standards organizations for more =
than seven
>>> years, engineer Vidya Narayanan decided it was time to move on. =
Although she
>>> still believes that these organizations make the Internet a better =
place,
>>> she wonders about the pace of change versus the pace of =
organizations."
>>>=20
>>> My thoughts-
>>>=20
>>> There are some nuggets of truth in what she says in this article, =
and in
>>> some of the comments. I think that the problems are real, so there=92s=
 value
>>> in taking the criticism constructively, despite the fact that the =
author
>>> chose to focus on the problems without any suggestions of solutions.
>>>=20
>>> "while the pace at which standards are written hasn=92t changed in =
many years,
>>> the pace at which the real world adopts software has become orders =
of
>>> magnitude faster."
>>> =85
>>> "Running code and rough consensus, the motto of the IETF, used to be
>>> realizable at some point. =85 In the name of consensus, we debate =
frivolous
>>> details forever. In the name of patents, we never finish.=94
>>> =85
>>> "Unless these standards organizations make radical shifts towards
>>> practicality, their relevance will soon be questionable.=94
>>>=20
>>> I don=92t have too many big ideas how to fix these problems, but =
I=92ll at least
>>> take a crack at it in order to spur discussion. My paraphrase of the =
problem
>>> and some discussion follows.
>>>=20
>>> - We=92ve lost sight of consensus and are too often derailed by a =
vocal
>>> minority of those willing to endlessly debate a point.
>>>=20
>>> Part of the solution to that is reiterating what consensus is and is =
not,
>>> such as draft-resnick-on-consensus so that we don=92t confuse a need =
for
>>> consensus with a need for unanimity. Part of the solution is IETF =
leadership
>>> helping to identify when we have rough consensus encumbered by a =
debate that
>>> will never resolve itself, without quieting actual disagreement that =
needs
>>> continued discussion in order to find a compromise. I don=92t have =
good
>>> suggestions on how to make that second half better.
>>>=20
>>> - We don=92t have nearly enough focus on running code as the thing =
that helps
>>> to ensure that we=92re using our limited cycles on getting the right =
things
>>> out expediently, and either getting the design right the first time, =
or
>>> failing quickly and iterating to improve
>>>=20
>>> The solution here may be that we need to be much more aggressive at
>>> expecting any standards track documents to have running code much =
earlier in
>>> the process. The other part of that is to renew our focus on actual =
interop
>>> standards work, probably by charter or in-group feedback, shift =
focus away
>>> from BCP and info documents. Perhaps when considering whether to =
proceed
>>> with a given document, we need test as to whether it=92s actively
>>> helpful/needed and ensure that we know what audience would be =
looking at it,
>>> rather than simply ensuring that it is =93not harmful=94 and mostly =
within the
>>> WG=92s chartered focus.
>>=20
>> My friend @colin_dixon pointed this out to me yesterday, and I've =
been
>> giving it quite a bit of thought since then (I have a nascent blog on
>> the topic of how open source and standards orgs might
>> productively/efficiently work together; follow up to
>> =
http://www.sdncentral.com/education/david-meyer-reflections-opendaylight-o=
pen-source-project-brocade/2014/03).
>>=20
>> What I can say is that after seeing the kind of progress that several
>> open source communities make (they do epitomize the best of the =
IETF's
>> running code/rough consensus ethic), one does have to wonder if
>> traditional standards making is either obsolete or in dire need of a
>> make over. What is needed, IMO, is a reimagining of how the standards
>> process interacts with the open source movement specifically focused
>> on how they can compliment one another.
>=20
> [Alia] It would be very useful to have a functional model for how the
> two can compliment each other.  We also tend to talk about open-source
> as a single monolith - when it can have very different models for
> accepting in changes, how and who runs the community, who is really
> participating (open source doesn't mean non-corporate) etc.   Some of
> what the IETF does is the architecture and requirements thinking about
> how the solution should fit in - while some of the open-source is
> about getting a solution implemented ASAP.   IMHO, a spiral is useful
> with an easy way of interaction.  With I2RS, as a WG chair, I
> suggested having experimental drafts describing solutions that were
> being implemented - but haven't seen any.   A question is what is
> needed to encourage the interactions.

	I think this is where things (start to) go wrong with the =
existing IETF model. We need drafts of everything is an axiom here that =
we should challenge. In open source, the code, its associated wiki pages =
and perhaps auto-gen docs are the draft and implementation =
agreement/documentation in question.=20

	I would also challenge what has become the common new WG =
"formula" these days. That is the notion that requirements, problem =
statements or architectures are always needed and must come before the =
WG can work on any protocols/solutions. These are heavy burdens that =
have a price of slowing things down. If we want to pay that price, we'd =
better get something good in return. However, the road is littered with =
many examples of recent WGs getting nowhere after several years of work. =
These groups often end up in this state because frankly many of the =
people involved in those efforts are completely disconnected from the =
reality of building the things they are apparently designing. In many =
cases they never have built anything either, so much of the effort goes =
into explaining to them why things need to be a certain way/etc... =
Unfortunately their "veto" or influence in the process also dilutes the =
simplicity that an implementation would reveal (i.e.: useless options).  =
Its clearly the difference between theory and practice, which I think we =
all understand is a real thing.   The end result is that this impedance =
is one quantifiable reason why people have looked to over avenues such =
as open source, to build interoperable systems/tools/etc... quickly.  =20=


	The solution: join the IETF process to the open source =
communities *where it makes sense, but not otherwise*. Open source BTW =
is what we used to call a rough-concensus + running code around here!
If we stick to interfaces that need "on the wire" interoperability, we =
are in the sweet spot. If we wade into areas where there is little value =
added - such as requirements/problem statements/architectures, lets not =
waste our time. For example, there are clearly cases where an RFC =
standard for something does not makes sense. Something like Open stack =
is a good example. The APIs are there, implemented in code you can see =
and documented. There is a well defined change process that identifies =
stable release points and also allows for quick iteration on that =
code/interfaces to evolve that works very quickly. Why would anyone =
every need an RFC for these things?  Now there really are cases where =
formal standardization makes sense. As I said if we stick to interfaces =
that need "on the wire" interop, we are squarely somewhere both open =
source and the IETF can add value. For example, there is a lot of code =
generation in open source based on yang models these days. Many of the =
experts around the model creation are at the IETF and not necessarily in =
those communities, so joining those folks to model creation can help =
that running code. In cases where vendors really want interop at the =
model level, then lets get together the vendors/operators that care, and =
not only build running code to test/prove those models make sense, but =
then run them through the IETF process in parallel.

	--Tom



> [Alia] Diversity of implementation is important as is stability of a
> standard and it being understood how to change/upgrade for different
> versions.  These don't come automatically via open-source.
>=20
> Regards,
> Alia
>=20
>=20


--Apple-Mail=_F36416B1-8A48-415E-8C82-535EFB19E3B5
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTTyAmAAoJEPcO+I7eiUJZD9cP/iKoTpnx8D6xgBwDMuOnKVOj
8LZyOq88EXJb0bQ9Idpk5ZgGpebdJoX+K6+oHaxGtB10UQ+rNtRuzRJbpcG/Re18
fqsTJT2yC0hdBt64DSai2Pb9JVWtrJup5QtUkDbPPlHBBsvISDpT5NN5nXWRNEZ6
nutvCSzMQfeV93uw9QcLLswXh64L8fsaEDGSeqbUSww5O8BrUnY+zEpC8hN6t8D9
EPbPIamGLAJLVZArKnB7n1QhYzv7UBUnFHu1LT9h1BH8LmC2957Afkic1lFj7v5q
FGNASSOAWWdlRUJjOubtM1S18jSTGiMhzCIX0exw31OHRAFBAPWg/xSUFWHTwW5O
RL37RI8UYvAY0rSpr7elTB1bEQR48vJzU6Q/01e/puUE5mS9IurN/fFYTpBTOwdM
WAe8B4zDAoOrh4+FUnJ+xesZTEwsb1tYmo7rdSOaP1LWzJfJv2WbHkDjcT874+Mm
QeqBDpjJbQiwsJ1TkiSrT8v7OEflgIBqUpm2lVkMWrYm+ynDeoKNaUDNt3kfHrs9
m3qOGtcDB/VGSnrNQ0taWemzt2BnrIPdFbpi+5uzHXC1wHTcmUTLZ/4vXnQQkIHA
IedpO61/p8mVuXEpDIL3+2jb0B5gTD7K368CIrmGFHx9g0FLoVrGb9hqiA3zLe2Y
QG4hHTSbLch+w1rp23lr
=ONXb
-----END PGP SIGNATURE-----

--Apple-Mail=_F36416B1-8A48-415E-8C82-535EFB19E3B5--


From nobody Thu Apr 17 05:29:21 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDCA71A012B for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 05:29:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 yGgqyBmdHi26 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 05:29:15 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8D8861A0123 for <ietf@ietf.org>; Thu, 17 Apr 2014 05:29:14 -0700 (PDT)
Received: (qmail 74852 invoked from network); 17 Apr 2014 12:29:09 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=12463.534fc915.k1404; bh=LqFz0qXV9zuue1N+AEOjy+E0iPGkgAn6DpvEibNDc1E=; b=fzXfv+Jwr1Iqg/GNcq1/9a8Wa6xTKyJI/Zg3r8GmYhBI872X/VBR79G8RFfdjb3J3C/v1xRc/yaK31eFjrnHSpnnBvJmK51ZljTuCDV5TSkJ78ffyzPoRMjghEfBNDJboUutR8WZFnZn57T6Ob2i0iNj1+D/kXdumT+px+qwHxFaNPJVgRjG+e9r+kJY5X0cbXiT2tokrvuqQDYvCaQFpRWaLomRAqXN5ajjCBOF3zXhgWwv1jNY3hEXYZsRr1jx
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=12463.534fc915.k1404; bh=LqFz0qXV9zuue1N+AEOjy+E0iPGkgAn6DpvEibNDc1E=; b=S2nEJWpbz9x1c9iq1FBWuQx4GF98kPq6nryy967bn3kjXMfZUw3lrivw+W5Bg1Z2nMFdATz7Kz2rjuPDkIfZZrQoFk8yo827rbpdeyEOHKaX9a+CITaad/ub+jdE+VXN8mAuYnoOgZLjZbh972nEZurGxto6Rtq4TnydbJrGg1jaOoG1VVHbOrohWGhFnWtDIHVOaRTXAfd4Dq5uHHP1nsnjJg2XdKxGvaH/B7Lr6OWs5yg7wJD9xP7uiUwz4K6A
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 17 Apr 2014 12:29:09 -0000
Date: 17 Apr 2014 08:29:08 -0400
Message-ID: <alpine.BSF.2.00.1404170824350.2692@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Pete Resnick" <presnick@qti.qualcomm.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <534F5E67.1010307@qti.qualcomm.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com> <alpine.BSF.2.00.1404162346400.2194@joyce.lan> <534F5E67.1010307@qti.qualcomm.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-475502795-1397737749=:2692"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OkM5wmr-aNoa33LBr2N4tJxqC8M
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 12:29:19 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-475502795-1397737749=:2692
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

>> The magic token has to be cryptographically tied to the contents of the 
>> original message
>
> No it doesn't. It has to be cryptographically tied to the mailing list's 
> re-sending of the message. How to do that with asymmetric keys should be 
> discussed somewhere other than on this list.

Now I'm totally confused.  How does that help me as a sender distinguish 
between a good mailing list that is resending real mail from Yahoo and an 
evil mailing list that is sending phishes?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
--3825401791-475502795-1397737749=:2692
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIII7gYJKoZIhvcNAQcCoIII3zCCCNsCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBh8wggYbMIIFA6ADAgECAgMJWEYwDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xNDAzMTgxOTQ3NDdaFw0xNTAzMjAwMDU2MDBaMDoxGDAW
BgNVBAMMD2pvaG5sQHRhdWdoLmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxA
dGF1Z2guY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnMGH
52DBxB4jb86Sxi3VvgOjirvLveIVP7zvqxBDpJzxrF02wCYwnQuxi3S3U5ge
3iHihzhM9qP+N03frkr4KH6Spgec88YjMioVQStTQZcrogTdHweZOgT8tckg
HEmHCF8uHBjD0HbfDk+9zYFtaE3QPk5aGm02Id0fNNM5WmSQSxVwF0Ddryq5
vIU0AHbB/1kok1zJpwWA06SgHenlnYngnSpNWlOn+SxboiD28m2XTWDP5ULL
e1b040VtkQMzpuVXzAHWVQYQWUevJ4y8mrUsqAyGuYSb5pTU28D+NExVAYxn
WD94rzgBpkXgC4Xxcp3TmyfMaLMF4M9ef0nu+QIDAQABo4IC1TCCAtEwCQYD
VR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSpNAr06FueusUfmbDdecnZ1kznsTAfBgNVHSME
GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0
YXVnaC5jb20wggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIB
KjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5
LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3Vl
ZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJl
bWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25s
eSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0
aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmg
J4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYI
KwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRz
c2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRw
Oi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5j
YS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0G
CSqGSIb3DQEBCwUAA4IBAQC3OSsHtuc1se2JPbLqI1b31i0EER3UX6Ep2Zuy
FkACIpk/i8mPi0KIfMWWiDlNmqeQEq8308i0/2mVcMVdgKWIUMJdZb3CmNfs
3qtTlrdXXYXT7ZLjL6a1Bbh/lKUm35JYRH8zf3rqDbLkpiA92vc7uTQcbDay
1sQ4CSTvOWuq0CIwMXqJePhHf/runG7ndDuX2yFagHlxhsvn7raw5NQuu4Sj
ofwbNiszwkryB7ZYUxq2Pg2i1m2XlgMbNEfw8deAZOyHGKKGz25Ei1KvJofH
1izh0WDU+ueJum6RHm8/o/i53MbYZN4Il64aBD1HPqQow3jHQBhAc8XN85hH
csS2MYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZp
Y2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCVhGMAkGBSsOAwIaBQCggdgw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQw
NDE3MTIyOTA4WjAjBgkqhkiG9w0BCQQxFgQUhLtA7JXBO0GVkm7W6n0XAmbV
3igweQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEW
MAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEggEAYY3ZHbDAweshcatLYXughXkgZ3LT5Se5StGALvJXfvBqJa1X
NGsJPVX9muJIQhQaMSO19g2XLjlBFsew5ht57JJEwPZSyNJa1eXQ33mbchIv
/+iUZ/ApWEFqKNjzC92wgnwo1HFm2UP5jTHvirRPz4KxJ+ORkNzNxF91PbtA
ljOfrLXut5qSl1FoSprdYkOyRb5GmkfEA0Q9B49a6v5NsvV4CZFRXQ+XH2Vv
dfE7Y7cJ7YpXkajVGydQk6cvCtph+CTlNx4M3kh+F6SrbS02kB+J1D8KlbQc
R18xE+BavyR95qRjDg1HIGuI8xruvUgYmgDN3iU0G5+/guKPaqnRyQ==

--3825401791-475502795-1397737749=:2692--


From nobody Thu Apr 17 06:11:48 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 325DA1A0168 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 06:11:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 sZq15Ul56BKg for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 06:11:40 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 417DB1A013C for <ietf@ietf.org>; Thu, 17 Apr 2014 06:11:40 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s3HDBYvT028190 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Apr 2014 15:11:34 +0200 (MEST)
Subject: Re: (DMARC) Why mailing lists are only sort of special
In-Reply-To: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Date: Thu, 17 Apr 2014 15:11:34 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140417131134.5CEFC1ACCF@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/l7-hGTZEgzWysDGwy3mFUnnfMiI
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 13:11:47 -0000

Yoav Nir wrote:
> 
> On Apr 17, 2014, at 9:35 AM, Dave Cridland <dave@cridland.net> wrote:
>> 
>> Right now, my MUA treats this as a message
>> "From John R Levine <johnl@taugh.com>". This means that any policy
>> on the message origination comes from looking solely at the taugh.com
>> domain. We'll pretend it has a DMARC policy. Herein lies the
>> Yahoo/DMARC issue, because unless your policy essentially stipulates
>> that the IETF is allowed to spoof you, we're stuck.
> 
> Then perhaps this is what needs to change. John R Levine did not send
> you a message. He sent a message to the list. It is the list software
> that sent you a message. So perhaps the From field should have been
> ?From: IETF Mailing list on behalf of John R Levine <ietf@ietf.org>?.

But that is EXACTLY what the IETF mailing list exploder *IS* doing
exactly as it has been specified for ages:

https://tools.ietf.org/html/rfc822#section-4.4.2
https://tools.ietf.org/html/rfc822#appendix-A.2

https://tools.ietf.org/html/rfc5322#section-3.6.2

            The "From:" field specifies the author(s) of the message,
   that is, the mailbox(es) of the person(s) or system(s) responsible
   for the writing of the message.  The "Sender:" field specifies the
   mailbox of the agent responsible for the actual transmission of the
   message. 

  From: Yoav Nir <ynir.ietf@gmail.com>
  Subject: Re: (DMARC) Why mailing lists are only sort of special
  Errors-To: ietf-bounces@ietf.org
  Sender: ietf <ietf-bounces@ietf.org>
  Date: Thu, 17 Apr 2014 13:50:30 +0300
  Message-ID: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
  To: Dave Cridland <dave@cridland.net>
  CC: "ietf@ietf.org" <ietf@ietf.org>


Something as old as Outlook 2003 will properly display a message
that is received with a "Sender:" as "<Sender> on behalf of <From>"


-Martin


From nobody Thu Apr 17 06:27:06 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 007D31A013C for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 06:27:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 WLbPe1aMEx8c for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 06:26:59 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 80DA91A015A for <ietf@ietf.org>; Thu, 17 Apr 2014 06:26:59 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id z2so814363wiv.6 for <ietf@ietf.org>; Thu, 17 Apr 2014 06:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=z7VaWQJp6kRXZrBQPk3sXqop8RgMD1vG1un9lszHuyY=; b=Q2CEnHKxWcXvvNUinhbFsMJn8CBzDw7Gx203w2YejnLSLVjAvtR8rhg3qRZH1z7mUo YrBrBCEphC0lbp6cQa6IFFulqSTPJ8WaTxZVVHy03DONVQWUU5XFWo22eVoCBAc8y+/p p0172evYaXXmuS/wro30ECrCvoUmWbTLXklduccN0EoJcrbCDXJFnIOnFb3YxUUfCggq TTUuAhaalJFyTq50nl8plBYLIESPT4GW2ltysFxph2JtuL/FsWeWorcF0rhHndf4tk6B vOK6tgxejA38vAFHM7BmCB9/QQnZmLgmdCFpXyj0Rr6e7W6uihb29ZeyyOIdEAZ3AXEm Puig==
X-Received: by 10.180.206.36 with SMTP id ll4mr7508706wic.57.1397741215443; Thu, 17 Apr 2014 06:26:55 -0700 (PDT)
Received: from [172.24.248.99] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id bj5sm4904680wib.3.2014.04.17.06.26.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 06:26:54 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <20140417131134.5CEFC1ACCF@ld9781.wdf.sap.corp>
Date: Thu, 17 Apr 2014 16:26:52 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <3DA69075-C8DB-4E40-8B2C-849AE05CCFF1@gmail.com>
References: <20140417131134.5CEFC1ACCF@ld9781.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/a7OmVGUy0QgsZgQxONmYrvIizcc
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 13:27:04 -0000

On Apr 17, 2014, at 4:11 PM, Martin Rex <mrex@sap.com> wrote:

> Yoav Nir wrote:
>>=20
>> On Apr 17, 2014, at 9:35 AM, Dave Cridland <dave@cridland.net> wrote:
>>>=20
>>> Right now, my MUA treats this as a message
>>> "=46rom John R Levine <johnl@taugh.com>". This means that any policy
>>> on the message origination comes from looking solely at the =
taugh.com
>>> domain. We'll pretend it has a DMARC policy. Herein lies the
>>> Yahoo/DMARC issue, because unless your policy essentially stipulates
>>> that the IETF is allowed to spoof you, we're stuck.
>>=20
>> Then perhaps this is what needs to change. John R Levine did not send
>> you a message. He sent a message to the list. It is the list software
>> that sent you a message. So perhaps the =46rom field should have been
>> ?From: IETF Mailing list on behalf of John R Levine <ietf@ietf.org>?.
>=20
> But that is EXACTLY what the IETF mailing list exploder *IS* doing
> exactly as it has been specified for ages:
>=20
> https://tools.ietf.org/html/rfc822#section-4.4.2
> https://tools.ietf.org/html/rfc822#appendix-A.2
>=20
> https://tools.ietf.org/html/rfc5322#section-3.6.2
>=20
>            The "From:" field specifies the author(s) of the message,
>   that is, the mailbox(es) of the person(s) or system(s) responsible
>   for the writing of the message.  The "Sender:" field specifies the
>   mailbox of the agent responsible for the actual transmission of the
>   message.=20
>=20
>  From: Yoav Nir <ynir.ietf@gmail.com>
>  Subject: Re: (DMARC) Why mailing lists are only sort of special
>  Errors-To: ietf-bounces@ietf.org
>  Sender: ietf <ietf-bounces@ietf.org>
>  Date: Thu, 17 Apr 2014 13:50:30 +0300
>  Message-ID: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
>  To: Dave Cridland <dave@cridland.net>
>  CC: "ietf@ietf.org" <ietf@ietf.org>
>=20
>=20
> Something as old as Outlook 2003 will properly display a message
> that is received with a "Sender:" as "<Sender> on behalf of <From>=94

A client as new as Mail.app on Mac OS X 10.9 does not.=20

Obviously the Sender: field is not where the DMARC implementations use =
for checking policy.

Yoav=


From nobody Thu Apr 17 06:39:06 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7A631A015A for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 06:39:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.368
X-Spam-Level: 
X-Spam-Status: No, score=-1.368 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=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 ef4lBlyIPwa6 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 06:38:57 -0700 (PDT)
Received: from mail-oa0-x22b.google.com (mail-oa0-x22b.google.com [IPv6:2607:f8b0:4003:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 154F91A010A for <ietf@ietf.org>; Thu, 17 Apr 2014 06:38:57 -0700 (PDT)
Received: by mail-oa0-f43.google.com with SMTP id eb12so451064oac.16 for <ietf@ietf.org>; Thu, 17 Apr 2014 06:38:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=u6p2dPN51LzexSXSSrO8e5ebWbxPulKZT3y5XHEHP0Q=; b=AAPQcRjMaAMKtCnT2Rxt/mm2r1hCiVAXXKGIDZHu0/bGlNvg/TbfMdHcfM9Zd5UZrt AfzFUGDi5imagTV5ZXvjiayZJcy1J7314wwr2SaSNUtTD31S5u215azc0IoZafOyFHLH Tf6l/Gmsvi3YLW5AMTIfy3jq78mIqm1dVPeaE=
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:content-type; bh=u6p2dPN51LzexSXSSrO8e5ebWbxPulKZT3y5XHEHP0Q=; b=ANRSGokbqymMgy5surEPgIhyOh4pXcb4JNv7PYW+EJkWOGYIxY/hrIUt924xoiZc4V AwdFqgxpDBbycnM3mztcYrl7zluAZLt4D91vrvBhumKc86QVOeHPexV87XP+/nYAFZHZ f+SMdRPvxDJVzdM9bB3+s924t0czNxreKQJH6i2muEVc2N1f3TU9ttqSXemwoUZrZGvZ GZfrEeUoahdG14P3rIfN91oWYOrPnqfcoUF22WyYstQ7BlLkkv7gGaaaJ4NsQIv2g3nX +HBGYdv5Fqaj7ybqjQQ3AVRR5h7r6WBEUfssY30NWsGFzQczbXKFIH/CqfXUVzmQQEPw neUg==
X-Gm-Message-State: ALoCoQlK+WSabjf04uo3D1dCU7eEvwkuFRMQYemNSuFOG4KzPVo2qs4i1Wln1kJphrUvuRKnpc7h
MIME-Version: 1.0
X-Received: by 10.60.34.65 with SMTP id x1mr11897220oei.6.1397741933439; Thu, 17 Apr 2014 06:38:53 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Thu, 17 Apr 2014 06:38:53 -0700 (PDT)
In-Reply-To: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAKHUCzwZ29TAAjJ3_w+0aaoN-L2o+CGHYaMQ=TOEqYdVn5rQHg@mail.gmail.com> <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
Date: Thu, 17 Apr 2014 14:38:53 +0100
Message-ID: <CAKHUCzz3TRnxMi706j2Hh3dOHKwvuxL-r+7J4Vnr1xp7GxrwVQ@mail.gmail.com>
Subject: Re: (DMARC) Why mailing lists are only sort of special
From: Dave Cridland <dave@cridland.net>
To: Yoav Nir <ynir.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=089e0111bf726e41cf04f73d27b1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/y5q0GR74k0y6IJUg6C7ND1YcuHk
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 13:39:01 -0000

--089e0111bf726e41cf04f73d27b1
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 17 April 2014 11:50, Yoav Nir <ynir.ietf@gmail.com> wrote:

> Then perhaps this is what needs to change. John R Levine did not send you
> a message. He sent a message to the list. It is the list software that se=
nt
> you a message. So perhaps the From field should have been =E2=80=9CFrom: =
IETF
> Mailing list on behalf of John R Levine <ietf@ietf.org>=E2=80=9D. The Rep=
ly-To
> could be set to either John=E2=80=99s real address or the mailing list ad=
dress,
> depending on what we think users mean when they click =E2=80=9CReply=E2=
=80=9D - reply to
> John or reply to the list.
>
>
What you're changing there, as Martin Rex hints, is not the semantics of
mailing lists, but the semantics of RFC 822 and successors. I could go
along with this if RFC 5322 were demonstrably broken; but in practise, it's
not.

John R Levine, in this instance, did indeed not send me the message - which
is why the Sender header field doesn't have his name or email address
present.

He did, however, write the message, which is why the From header field does=
.

If you want explicit handling, what we'd need to do is individually (and
visibly) authenticate each transaction - this has knock-on effects in how
we handle blind carbon-copies (in particular, we'd need to send them as a
separate transaction). This has some nasty implications for unsuspecting
MUAs; but some MUAs do this anyway for other related reasons. Also, I
suspect this model would have serious implications for DMARC - that is, I
don't think it fits the DMARC model closely enough to satisfy even
"minimal" changes to the deployed base.

But what this would do, loosely, is have a verifiable chain of
Levine->list; list->me. I would then look at the policies for Levine, and
for the list, and somehow combine them to a decision.

Dave.

--089e0111bf726e41cf04f73d27b1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
7 April 2014 11:50, Yoav Nir <span dir=3D"ltr">&lt;<a href=3D"mailto:ynir.i=
etf@gmail.com" target=3D"_blank">ynir.ietf@gmail.com</a>&gt;</span> wrote:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">
<div style=3D"word-wrap:break-word"><div class=3D"">Then perhaps this is wh=
at needs to change. John R Levine did not send you a message. He sent a mes=
sage to the list. It is the list software that sent you a message. So perha=
ps the From field should have been =E2=80=9CFrom: IETF Mailing list on beha=
lf of John R Levine &lt;<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">=
ietf@ietf.org</a>&gt;=E2=80=9D. The Reply-To could be set to either John=E2=
=80=99s real address or the mailing list address, depending on what we thin=
k users mean when they click =E2=80=9CReply=E2=80=9D - reply to John or rep=
ly to the list.<br>
</div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br></div></font>=
</span></div></blockquote><div><br></div><div>What you&#39;re changing ther=
e, as Martin Rex hints, is not the semantics of mailing lists, but the sema=
ntics of RFC 822 and successors. I could go along with this if RFC 5322 wer=
e demonstrably broken; but in practise, it&#39;s not.</div>
<div><br></div><div>John R Levine, in this instance, did indeed not send me=
 the message - which is why the Sender header field doesn&#39;t have his na=
me or email address present.</div><div><br></div><div>He did, however, writ=
e the message, which is why the From header field does.</div>
<div><br></div><div>If you want explicit handling, what we&#39;d need to do=
 is individually (and visibly) authenticate each transaction - this has kno=
ck-on effects in how we handle blind carbon-copies (in particular, we&#39;d=
 need to send them as a separate transaction). This has some nasty implicat=
ions for unsuspecting MUAs; but some MUAs do this anyway for other related =
reasons. Also, I suspect this model would have serious implications for DMA=
RC - that is, I don&#39;t think it fits the DMARC model closely enough to s=
atisfy even &quot;minimal&quot; changes to the deployed base.</div>
<div><br></div><div>But what this would do, loosely, is have a verifiable c=
hain of Levine-&gt;list; list-&gt;me. I would then look at the policies for=
 Levine, and for the list, and somehow combine them to a decision.</div>
<div><br></div><div>Dave.</div></div></div></div>

--089e0111bf726e41cf04f73d27b1--


From nobody Thu Apr 17 07:14:43 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D74D1A017D for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:14:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.873
X-Spam-Level: 
X-Spam-Status: No, score=-12.873 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 tVvnWhssOqD8 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:14:36 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3341A015F for <ietf@ietf.org>; Thu, 17 Apr 2014 07:14:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23334; q=dns/txt; s=iport; t=1397744072; x=1398953672; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=UHc7D/q6qtV57pft94Aih0v20odQ6XKcldgB7APnBNE=; b=VbHKVmr44SEDZ5pXFqmJeD7Sc21Jxa+PmQtaKs3RXwFAGKX2pzpn01sf fzCBE0UEOs67CxehnaC36+zoFIi+yXyXjR3GQ0fNpof++CV0iFXJwXA1L /Q3jmRackKyZi/03qSVNWbU0hlyHGZULB1A4xzp/qKppVA0fZdYj/w/TP k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgoFAALhT1OrRDoJ/2dsb2JhbABPCoJCRDvENYElFnSCJQEBAQR4ARALGAkWAQcHCQMCAQIBNBEGDQEFAgEBF4dgDspoF44GBFgHhDgElQCDboE3hSGLdYMzO4Es
X-IronPort-AV: E=Sophos;i="4.97,879,1389744000";  d="scan'208,217";a="318268558"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by rcdn-iport-1.cisco.com with ESMTP; 17 Apr 2014 14:14:30 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3HEESpE016069; Thu, 17 Apr 2014 14:14:28 GMT
Message-ID: <534FE1C3.3070103@cisco.com>
Date: Thu, 17 Apr 2014 16:14:27 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Andy Bierman <andy@yumaworks.com>, "George, Wes" <wesley.george@twcable.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com>
In-Reply-To: <CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070201070206090709040104"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MUANlyldovkYSo4jX_aWzZzmkU4
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 14:14:41 -0000

This is a multi-part message in MIME format.
--------------070201070206090709040104
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 14/04/2014 18:11, Andy Bierman wrote:
>
>
>
> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes 
> <wesley.george@twcable.com <mailto:wesley.george@twcable.com>> wrote:
>
>     I'm surprised that no one has sent this out yet:
>     http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>
>     "Summary: After contributing to standards organizations for more
>     than seven years, engineer Vidya Narayanan decided it was time to
>     move on. Although she still believes that these organizations make
>     the Internet a better place, she wonders about the pace of change
>     versus the pace of organizations."
>
>     My thoughts-
>
>     There are some nuggets of truth in what she says in this article,
>     and in some of the comments. I think that the problems are real,
>     so there's value in taking the criticism constructively, despite
>     the fact that the author chose to focus on the problems without
>     any suggestions of solutions.
>
>         "while the pace at which standards are written hasn't changed
>         in many years, the pace at which the real world adopts
>         software has become orders of magnitude faster."
>         ...
>
>
> I think this issue (used to be called "timeliness") is critical and 
> continues to be overlooked.
> The charter milestones are just not that relevant to the process, and 
> it shows.
We discussed during the milestones during one of the last plenaries.
The discussion was around: the milestones are indications and not deadlines.
In Open Source project, these are deadlines.
In the IETF, I would love to find a middle ground between the two.
In the IETF, the only "deadlines" are the meetings, or to be more 
precise, the submission deadlines just before the meetings.
> It takes a long time to go from individual I-D -00 to RFC.
Exactly, and we should understand why!
I like this tool: 
http://www.arkko.com/tools/lifecycle/<draft-name>-timing.html
For example: 
http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-interfaces-cfg-timing.html
Where is the bottleneck? Is this a process issue? The 
authors/shepherd/IESG/RFC-editors?
I don't want to finger point, but understand what we should improve.
>
> IMO all WGs behind schedule should be taking steps to finish faster, like
> monthly virtual interim meetings, real interim meetings, etc.  More remote
> meeting and project management tools might help some.
Fully agreed.
That would effectively some extra deadlines.
>
>
>         "Running code and rough consensus, the motto of the IETF, used
>         to be realizable at some point. ... In the name of consensus,
>         we debate frivolous details forever. In the name of patents,
>         we never finish."
>         ...
>         "Unless these standards organizations make radical shifts
>         towards practicality, their relevance will soon be questionable."
>
>     I don't have too many big ideas how to fix these problems, but
>     I'll at least take a crack at it in order to spur discussion. My
>     paraphrase of the problem and some discussion follows.
>
>     - We've lost sight of consensus and are too often derailed by a
>     vocal minority of those willing to endlessly debate a point.
>
>     Part of the solution to that is reiterating what consensus is and
>     is not, such as draft-resnick-on-consensus so that we don't
>     confuse a need for consensus with a need for unanimity. Part of
>     the solution is IETF leadership helping to identify when we have
>     rough consensus encumbered by a debate that will never resolve
>     itself, without quieting actual disagreement that needs continued
>     discussion in order to find a compromise. I don't have good
>     suggestions on how to make that second half better.
>
>
> Consensus is the real commodity here.
> Perhaps vendors are figuring out they can get a better outcome by 
> contributing
> to corporate open-source projects instead of SDOs.
> Customers just want software that works with their equipment.
>
> Vendor engineers just want to work together to produce a solution
> that meets the requirements for the specific upcoming release.
> There is no way for "bad actors" who want to stall or delay the
> effort to have any influence on the engineering.  There is no
> tail-heavy review process to introduce extraordinary delays.
>
>     - We don't have nearly enough focus on running code as the thing
>     that helps to ensure that we're using our limited cycles on
>     getting the right things out expediently, and either getting the
>     design right the first time, or failing quickly and iterating to
>     improve
>
>
> With the open-source approach to consensus, running code is the entire 
> focus.
> This is a bug and a feature.  The documentation quality is much higher 
> in the IETF.
yes.
IETF is about running code and consensus. Well, sadly, more about 
consensus than running-code these days.
And open source is more about running code and less about consensus
>
>     The solution here may be that we need to be much more aggressive
>     at expecting any standards track documents to have running code
>     much earlier in the process. The other part of that is to renew
>     our focus on actual interop standards work, probably by charter or
>     in-group feedback, shift focus away from BCP and info documents.
>     Perhaps when considering whether to proceed with a given document,
>     we need test as to whether it's actively helpful/needed and ensure
>     that we know what audience would be looking at it, rather than
>     simply ensuring that it is "not harmful" and mostly within the
>     WG's chartered focus.
>
>
> Generally it is very time-consuming to implement a protocol I-D in 
> progress.
> The draft will change so radically and so often before the final RFC 
> is published,
> that lots of code will get re-written in the effort.  People are told 
> "too bad, it's
> just a work-in-progress", but that doesn't help promote early 
> implementations.
>
> The IETF needs to reduce the cost of consensus somehow.
+1.

Questions for all: practically, how?

Regards, Benoit
>
>
>     Thanks,
>
>     Wes George
>
>
>
> Andy
>


--------------070201070206090709040104
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 14/04/2014 18:11, Andy Bierman
      wrote:<br>
    </div>
    <blockquote
cite="mid:CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">On Mon, Apr 14, 2014 at 8:08 AM,
            George, Wes <span dir="ltr">&lt;<a moz-do-not-send="true"
                href="mailto:wesley.george@twcable.com" target="_blank">wesley.george@twcable.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div
style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  I&#8217;m surprised that no one has sent this out yet:&nbsp;<a
                    moz-do-not-send="true"
href="http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/"
                    target="_blank">http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/</a></div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  <br>
                </div>
                <div style="">"Summary:&nbsp;<span
                    style="line-height:22px;color:rgb(42,46,51);font-style:italic">After
                    contributing to standards organizations for more
                    than seven years, engineer Vidya Narayanan decided
                    it was time to move on. Although she still believes
                    that these organizations make the Internet a better
                    place, she wonders about the pace of change versus
                    the pace of organizations."</span></div>
                <div style=""><br>
                </div>
                <div style="">My thoughts-</div>
                <div style=""><br>
                </div>
                <div style="">There are some nuggets of truth in what
                  she says in this article, and in some of the comments.
                  I think that the problems are real, so there&#8217;s value
                  in taking the criticism constructively, despite the
                  fact that the author chose to focus on the problems
                  without any suggestions of solutions.</div>
                <div style=""><br>
                </div>
                <blockquote style="margin:0px 0px 0px
                  40px;border:none;padding:0px">
                  <div style="">"while the pace at which standards are
                    written hasn&#8217;t changed in many years, the pace at
                    which the real world adopts software has become
                    orders of magnitude faster."</div>
                  <div style="">&#8230;</div>
                </blockquote>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>I think this issue (used to be called "timeliness") is
              critical and continues to be overlooked.</div>
            <div>The charter milestones are just not that relevant to
              the process, and it shows.</div>
          </div>
        </div>
      </div>
    </blockquote>
    We discussed during the milestones during one of the last plenaries.<br>
    The discussion was around: the milestones are indications and not
    deadlines.<br>
    In Open Source project, these are deadlines. <br>
    In the IETF, I would love to find a middle ground between the two.<br>
    In the IETF, the only "deadlines" are the meetings, or to be more
    precise, the submission deadlines just before the meetings.<br>
    <blockquote
cite="mid:CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>It takes a long time to go from individual I-D -00 to
              RFC.</div>
          </div>
        </div>
      </div>
    </blockquote>
    Exactly, and we should understand why!<br>
    I like this tool:
    <a class="moz-txt-link-freetext" href="http://www.arkko.com/tools/lifecycle/">http://www.arkko.com/tools/lifecycle/</a>&lt;draft-name&gt;-timing.html<br>
    For example:
<a class="moz-txt-link-freetext" href="http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-interfaces-cfg-timing.html">http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-interfaces-cfg-timing.html</a><br>
    Where is the bottleneck? Is this a process issue? The
    authors/shepherd/IESG/RFC-editors?<br>
    I don't want to finger point, but understand what we should improve.<br>
    <blockquote
cite="mid:CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div>IMO all WGs behind schedule should be taking steps to
              finish faster, like</div>
            <div>monthly virtual interim meetings, real interim
              meetings, etc. &nbsp;More remote</div>
            <div>meeting and project management tools might help some.</div>
          </div>
        </div>
      </div>
    </blockquote>
    Fully agreed.<br>
    That would effectively some extra deadlines. <br>
    <blockquote
cite="mid:CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div
style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
                <blockquote style="margin:0px 0px 0px
                  40px;border:none;padding:0px">
                  <div>"<span style=""><font color="#2a2e33"><span
                          style="line-height:22px">Running code and
                          rough consensus, the motto of the IETF, used
                          to be realizable at some point.&nbsp;&#8230;&nbsp;In the name
                          of consensus, we debate frivolous details
                          forever. In the name of patents, we never
                          finish.</span></font></span><font
                      color="#2a2e33"><span style="line-height:22px">&#8221;</span></font></div>
                  <div><font color="#2a2e33"><span
                        style="line-height:22px">&#8230;</span></font></div>
                  <div style="">
                    <div>"Unless these standards organizations make
                      radical shifts towards practicality, their
                      relevance will soon be questionable.&#8221;</div>
                  </div>
                  <div style=""><br>
                  </div>
                </blockquote>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  I don&#8217;t have too many big ideas how to fix these
                  problems, but I&#8217;ll at least take a crack at it in
                  order to spur discussion. My paraphrase of the problem
                  and some discussion follows.</div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  <br>
                </div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  - We&#8217;ve lost sight of consensus and are too often
                  derailed by a vocal minority of those willing to
                  endlessly debate a point.</div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  <br>
                </div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  Part of the solution to that is reiterating what
                  consensus is and is not, such as
                  draft-resnick-on-consensus so that we don&#8217;t confuse a
                  need for consensus with a need for unanimity. Part of
                  the solution is IETF leadership helping to identify
                  when we have rough consensus encumbered by a debate
                  that will never resolve itself, without quieting
                  actual disagreement that needs continued discussion in
                  order to find a compromise. I don&#8217;t have good
                  suggestions on how to make that second half better.</div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  <br>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Consensus is the real commodity here.</div>
            <div>Perhaps vendors are figuring out they can get a better
              outcome by contributing</div>
            <div>to corporate open-source projects instead of SDOs.</div>
            <div>Customers just want software that works with their
              equipment.<br>
            </div>
            <div><br>
            </div>
            <div>Vendor engineers just want to work together to produce
              a solution</div>
            <div>that meets the requirements for the specific upcoming
              release.</div>
            <div>There is no way for "bad actors" who want to stall or
              delay the</div>
            <div>effort to have any influence on the engineering. &nbsp;There
              is no</div>
            <div>tail-heavy review process to introduce extraordinary
              delays.</div>
            <div><br>
            </div>
            <div>&nbsp;</div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div
style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                </div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  - We don&#8217;t have nearly enough focus on running code as
                  the thing that helps to ensure that we&#8217;re using our
                  limited cycles on getting the right things out
                  expediently, and either getting the design right the
                  first time, or failing quickly and iterating to
                  improve</div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  <br>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>With the open-source approach to consensus, running
              code is the entire focus.</div>
            <div>This is a bug and a feature. &nbsp;The documentation quality
              is much higher in the IETF.</div>
          </div>
        </div>
      </div>
    </blockquote>
    yes. <br>
    IETF is about running code and consensus. Well, sadly, more about
    consensus than running-code these days.<br>
    And open source is more about running code and less about consensus<br>
    <blockquote
cite="mid:CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>&nbsp;</div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div
style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                </div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  The solution here may be that we need to be much more
                  aggressive at expecting any standards track documents
                  to have running code much earlier in the process. The
                  other part of that is to renew our focus on actual
                  interop standards work, probably by charter or
                  in-group feedback, shift focus away from BCP and info
                  documents. Perhaps when considering whether to proceed
                  with a given document, we need test as to whether it&#8217;s
                  actively helpful/needed and ensure that we know what
                  audience would be looking at it, rather than simply
                  ensuring that it is &#8220;not harmful&#8221; and mostly within
                  the WG&#8217;s chartered focus.</div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  <br>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Generally it is very time-consuming to implement a
              protocol I-D in progress.</div>
            <div>The draft will change so radically and so often before
              the final RFC is published,</div>
            <div>that lots of code will get re-written in the effort.
              &nbsp;People are told "too bad, it's</div>
            <div>just a work-in-progress", but that doesn't help promote
              early implementations.</div>
            <div><br>
            </div>
            <div>
              The IETF needs to reduce the cost of consensus somehow.</div>
          </div>
        </div>
      </div>
    </blockquote>
    +1.<br>
    <br>
    Questions for all: practically, how?<br>
    <br>
    Regards, Benoit<br>
    <blockquote
cite="mid:CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div><br>
            </div>
            <div><br>
            </div>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
              <div
style="font-size:14px;font-family:Calibri,sans-serif;word-wrap:break-word">
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                </div>
                <div
                  style="font-size:14px;font-family:Calibri,sans-serif">
                  <p class="MsoNormal" style="margin:0in 0in
                    0.0001pt;font-size:11pt">Thanks,</p>
                  <p class="MsoNormal" style="margin:0in 0in
                    0.0001pt;font-size:11pt">&nbsp;<span
                      style="font-size:11pt">&nbsp;</span></p>
                  <p class="MsoNormal" style="margin:0in 0in
                    0.0001pt;font-size:11pt">Wes George</p>
                  <p class="MsoNormal" style="margin:0in 0in
                    0.0001pt;font-size:11pt"><span
                      style="color:rgb(127,127,127);font-size:11pt"><br>
                    </span></p>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>Andy</div>
            <div><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------070201070206090709040104--


From nobody Thu Apr 17 07:20:56 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24DD81A00A3 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.873
X-Spam-Level: 
X-Spam-Status: No, score=-7.873 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 LQS-sfiH8CeX for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:20:49 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) by ietfa.amsl.com (Postfix) with ESMTP id D2BB11A0088 for <ietf@ietf.org>; Thu, 17 Apr 2014 07:20:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19017; q=dns/txt; s=iport; t=1397744445; x=1398954045; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=UksW3Ep7w7CKd7sNszwVOjXuwc+knICVjxYSKgKqmPk=; b=RO5GC0YZA+YjCRoMhZ/EgGlufbDveQBoLS/TWpwfP8URP7Ih7eO+oP75 XPO0c0O0O4uSYAvksKi+lFoC05zYbfl7my2cam6mjrECGfixOBrKPP8m4 1zmaXFmP2IJ8Vh5noZSACjoSLHVxxRC+BQXIF6Y9vR9QJ9D788A10ZNZJ k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AggFAPPhT1OrRDoI/2dsb2JhbABZgwbEcIElFnSCJQEBAQMBbgsFCQILGAkeBw8CCisRBgEMAQUCAQEVAodZB8p2FwSJOYRNWAeEOAEDi3SMeoZYi3WDMzuBLA
X-IronPort-AV: E=Sophos; i="4.97,879,1389744000"; d="scan'208,217"; a="36621044"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by alln-iport-1.cisco.com with ESMTP; 17 Apr 2014 14:20:43 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by mtv-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s3HEKePA009229; Thu, 17 Apr 2014 14:20:41 GMT
Message-ID: <534FE338.90004@cisco.com>
Date: Thu, 17 Apr 2014 16:20:40 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Simon Pietro Romano <spromano@unina.it>, Michael Richardson <mcr+ietf@sandelman.ca>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <19983.1397493280@sandelman.ca> <8B56205B-8143-4B5B-B2FD-22FABE95ED16@unina.it>
In-Reply-To: <8B56205B-8143-4B5B-B2FD-22FABE95ED16@unina.it>
Content-Type: multipart/alternative; boundary="------------060702040703040602070504"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-aVaZ2n90RJpaF1LMyLatLR5jhc
Cc: "ietf@ietf.org list" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 14:20:54 -0000

This is a multi-part message in MIME format.
--------------060702040703040602070504
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit

On 14/04/2014 19:01, Simon Pietro Romano wrote:
> Hi,
>
> I read the post from Vidya and I have to say I totally agree with her. 
> As to running code, in particular, my impression is that if you are 
> used to implement prototypes of ongoing standards and you're neither a 
> big company nor a member of the IETF elite of gurus, the best you can 
> buck for is an informational "call flows" RFC. Standards Track stuff 
> is left to those who (seem to) do the high-level specification work. 
> This happens because people seem to rush for editing documents as soon 
> as a new WG is chartered, but then they progressively reduce efforts 
> when such a WG starts to lose momentum and is not latest fashion any 
> longer.
Or when they made to the famous authors list of the WG document, which 
is considered at THE major achievement.
I've seen that problem a few times and it's very annoying.
I would be in favor to re-evaluate who really contributed to the 
document full life cycle when the document leaves the WG.

Regards, B.

> Finally, coming to interoperability, it is hard to work on it if your 
> implementation is the only one available. In the long run, I do 
> acknowledge the fact that you get tired of doing all that hard work 
> and investing so many cycles in a highly underestimated engineering 
> activity.
>
> My two cents,
>
> Simon
>
>
> On 14/apr/2014, at 18:34, Michael Richardson wrote:
>
>>
>> George, Wes <wesley.george@twcable.com 
>> <mailto:wesley.george@twcable.com>> wrote:
>>> - We don’t have nearly enough focus on running code as the thing 
>>> that helps to
>>> ensure that we’re using our limited cycles on getting the right 
>>> things out
>>> expediently, and either getting the design right the first time, or 
>>> failing
>>> quickly and iterating to improve
>>
>>> The solution here may be that we need to be much more aggressive at 
>>> expecting
>>> any standards track documents to have running code much earlier in the
>>> process.
>>
>> For instance, had DMARC proponents and/or Yahoo, spent some time 
>> making sure
>> that there was some running code for mailing list use, life would be 
>> better.
>>
>> I'm not entirely clear how it was that we produced/funded (more) 
>> running code in the
>> 1990s.  Maybe this is a false idea; it could be that there was less 
>> code then
>> than there is now.   I will posit several factors:
>>  1) there was less working occuring, and perhaps over a longer time 
>> period
>>     (where time is subject to perception as well as reality), such that
>>     code became mature sooner in the specification process, and/or there
>>     were simply more volunteers willing to produce it.
>>
>>  2) many companies were much smaller, and it was easier to get line 
>> managers
>>     to see why they wanted to be directly involved, even lead, efforts.
>>
>>  3) it wasn't so much the dotcom boom which made money available via VCs,
>>     but rather that the (ultimately unstainable) revenue doubling, 
>> quarter
>>     over quarter which made resources available for prototypes.
>>
>>  4) there were some clear institutions (MIT, CMU, Berkeley, LLBL, UW) 
>> where
>>     some good reference implementations were developed by students, 
>> faculty,
>>     staff.  And don't forget WIDE and USAGI!!!
>>
>> When I founded Xelerance, it was with the idea that multiple large
>> organizations were shipping IPsec code on Linux, and would rather pay a
>> company a maintenance fee than attempt to manage the process internally.
>> We got some work funded, but we never got enough funding to get ahead of
>> the standardization process and write code will an ID was still young.
>> Overall, that effort failed.
>>
>> --
>> Michael Richardson <mcr+IETF@sandelman.ca 
>> <mailto:mcr+IETF@sandelman.ca>>, Sandelman Software Works
>> -= IPv6 IoT consulting =-
>>
>>
>>
>
>   _\\|//_
>       ( O-O )
>  ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~
> Simon Pietro Romano
> Universita' di Napoli Federico II
>      Computer Engineering Department
>       Phone: +39 081 7683823 -- Fax: +39 081 7683816
>  e-mail: spromano@unina.it <mailto:spromano@unina.it>
>
> <<Molti mi dicono che lo scoraggiamento è l'alibi degli
>  idioti. Ci rifletto un istante; e mi scoraggio>>. Magritte.
>                      oooO
>   ~~~~~~~~~~~~~~~~~~~~~~~( )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~
>            \ (            (   )
>                             \_)          ) /
>                              (_/
>
>
>
>
>
>


--------------060702040703040602070504
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta content="text/html; charset=windows-1252"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 14/04/2014 19:01, Simon Pietro
      Romano wrote:<br>
    </div>
    <blockquote cite="mid:8B56205B-8143-4B5B-B2FD-22FABE95ED16@unina.it"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      Hi,
      <div><br>
      </div>
      <div>I read the post from Vidya and I have to say I totally agree
        with her. As to running code, in particular, my impression is
        that if you are used to implement prototypes of ongoing
        standards and you're neither a big company nor a member of the
        IETF elite of gurus, the best you can buck for is an
        informational "call flows" RFC. Standards Track stuff is left to
        those who (seem to) do the high-level specification work. This
        happens because people seem to rush for editing documents as
        soon as a new WG is chartered, but then they progressively
        reduce efforts when such a WG starts to lose momentum and is not
        latest fashion any longer.</div>
    </blockquote>
    Or when they made to the famous authors list of the WG document,
    which is considered at THE major achievement.<br>
    I've seen that problem a few times and it's very annoying. <br>
    I would be in favor to re-evaluate who really contributed to the
    document full life cycle when the document leaves the WG. <br>
    <br>
    Regards, B.<br>
    <br>
    <blockquote cite="mid:8B56205B-8143-4B5B-B2FD-22FABE95ED16@unina.it"
      type="cite">
      <div>Finally, coming to interoperability, it is hard to work on it
        if your implementation is the only one available. In the long
        run, I do acknowledge the fact that you get tired of doing all
        that hard work and investing so many cycles in a highly
        underestimated engineering activity.</div>
      <div><br>
      </div>
      <div>My two cents,</div>
      <div><br>
      </div>
      <div>Simon</div>
      <div><br>
      </div>
      <div><br>
        <div>
          <div>On 14/apr/2014, at 18:34, Michael Richardson wrote:</div>
          <br class="Apple-interchange-newline">
          <blockquote type="cite">
            <div><br>
              George, Wes &lt;<a moz-do-not-send="true"
                href="mailto:wesley.george@twcable.com">wesley.george@twcable.com</a>&gt;
              wrote:<br>
              <blockquote type="cite">- We don’t have nearly enough
                focus on running code as the thing that helps to<br>
              </blockquote>
              <blockquote type="cite">ensure that we’re using our
                limited cycles on getting the right things out<br>
              </blockquote>
              <blockquote type="cite">expediently, and either getting
                the design right the first time, or failing<br>
              </blockquote>
              <blockquote type="cite">quickly and iterating to improve<br>
              </blockquote>
              <br>
              <blockquote type="cite">The solution here may be that we
                need to be much more aggressive at expecting<br>
              </blockquote>
              <blockquote type="cite">any standards track documents to
                have running code much earlier in the<br>
              </blockquote>
              <blockquote type="cite">process.<br>
              </blockquote>
              <br>
              For instance, had DMARC proponents and/or Yahoo, spent
              some time making sure<br>
              that there was some running code for mailing list use,
              life would be better.<br>
              <br>
              I'm not entirely clear how it was that we produced/funded
              (more) running code in the<br>
              1990s.  Maybe this is a false idea; it could be that there
              was less code then<br>
              than there is now.   I will posit several factors:<br>
               1) there was less working occuring, and perhaps over a
              longer time period<br>
                  (where time is subject to perception as well as
              reality), such that<br>
                  code became mature sooner in the specification
              process, and/or there<br>
                  were simply more volunteers willing to produce it.<br>
              <br>
               2) many companies were much smaller, and it was easier to
              get line managers<br>
                  to see why they wanted to be directly involved, even
              lead, efforts.<br>
              <br>
               3) it wasn't so much the dotcom boom which made money
              available via VCs,<br>
                  but rather that the (ultimately unstainable) revenue
              doubling, quarter<br>
                  over quarter which made resources available for
              prototypes.<br>
              <br>
               4) there were some clear institutions (MIT, CMU,
              Berkeley, LLBL, UW) where<br>
                  some good reference implementations were developed by
              students, faculty,<br>
                  staff.  And don't forget WIDE and USAGI!!!<br>
              <br>
              When I founded Xelerance, it was with the idea that
              multiple large<br>
              organizations were shipping IPsec code on Linux, and would
              rather pay a<br>
              company a maintenance fee than attempt to manage the
              process internally.<br>
              We got some work funded, but we never got enough funding
              to get ahead of<br>
              the standardization process and write code will an ID was
              still young.<br>
              Overall, that effort failed.<br>
              <br>
              --<br>
              Michael Richardson &lt;<a moz-do-not-send="true"
                href="mailto:mcr+IETF@sandelman.ca">mcr+IETF@sandelman.ca</a>&gt;,
              Sandelman Software Works<br>
              -= IPv6 IoT consulting =-<br>
              <br>
              <br>
              <br>
            </div>
          </blockquote>
        </div>
        <br>
        <div apple-content-edited="true">
          <span class="Apple-style-span" style="border-collapse:
            separate; color: rgb(0, 0, 0); font-family: Helvetica;
            font-style: normal; font-variant: normal; font-weight:
            normal; letter-spacing: normal; line-height: normal;
            orphans: 2; text-align: -webkit-auto; text-indent: 0px;
            text-transform: none; white-space: normal; widows: 2;
            word-spacing: 0px; -webkit-border-horizontal-spacing: 0px;
            -webkit-border-vertical-spacing: 0px;
            -webkit-text-decorations-in-effect: none;
            -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
            0px; font-size: medium; "><span class="Apple-style-span"
              style="border-collapse: separate; color: rgb(0, 0, 0);
              font-family: Helvetica; font-style: normal; font-variant:
              normal; font-weight: normal; letter-spacing: normal;
              line-height: normal; orphans: 2; text-align: -webkit-auto;
              text-indent: 0px; text-transform: none; white-space:
              normal; widows: 2; word-spacing: 0px;
              -webkit-border-horizontal-spacing: 0px;
              -webkit-border-vertical-spacing: 0px;
              -webkit-text-decorations-in-effect: none;
              -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
              0px; font-size: medium; ">
              <div style="word-wrap: break-word; -webkit-nbsp-mode:
                space; -webkit-line-break: after-white-space; "><span
                  class="Apple-style-span" style="border-collapse:
                  separate; color: rgb(0, 0, 0); font-family: Helvetica;
                  font-style: normal; font-variant: normal; font-weight:
                  normal; letter-spacing: normal; line-height: normal;
                  orphans: 2; text-align: -webkit-auto; text-indent:
                  0px; text-transform: none; white-space: normal;
                  widows: 2; word-spacing: 0px;
                  -webkit-border-horizontal-spacing: 0px;
                  -webkit-border-vertical-spacing: 0px;
                  -webkit-text-decorations-in-effect: none;
                  -webkit-text-size-adjust: auto;
                  -webkit-text-stroke-width: 0px; font-size: medium; ">
                  <div style="word-wrap: break-word; -webkit-nbsp-mode:
                    space; -webkit-line-break: after-white-space; "><span
                      class="Apple-style-span" style="border-collapse:
                      separate; color: rgb(0, 0, 0); font-family:
                      Helvetica; font-style: normal; font-variant:
                      normal; font-weight: normal; letter-spacing:
                      normal; line-height: normal; orphans: 2;
                      text-align: -webkit-auto; text-indent: 0px;
                      text-transform: none; white-space: normal; widows:
                      2; word-spacing: 0px;
                      -webkit-border-horizontal-spacing: 0px;
                      -webkit-border-vertical-spacing: 0px;
                      -webkit-text-decorations-in-effect: none;
                      -webkit-text-size-adjust: auto;
                      -webkit-text-stroke-width: 0px; font-size: medium;
                      ">
                      <div style="word-wrap: break-word;
                        -webkit-nbsp-mode: space; -webkit-line-break:
                        after-white-space; ">
                        <div>
                          <div>                     <span
                              class="Apple-tab-span" style="white-space:
                              pre; "> </span><span
                              class="Apple-converted-space"> </span>   
                              _\\|//_</div>
                          <div>                           <span
                              class="Apple-tab-span" style="white-space:
                              pre; "> </span>      ( O-O )</div>
                          <div> 
                             ~~~~~~~~~~~~~~~~~~~~~~o00~~(_)~~00o~~~~~~~~~~~~~~~~~~~~~~~~</div>
                          <div>                   <span
                              class="Apple-converted-space"> </span><span
                              class="Apple-tab-span" style="white-space:
                              pre; "> </span>Simon Pietro Romano</div>
                          <div>             <span class="Apple-tab-span"
                              style="white-space: pre; "> </span><span
                              class="Apple-converted-space"> </span>Universita'
                            di Napoli Federico II</div>
                          <div>                <span
                              class="Apple-tab-span" style="white-space:
                              pre; "> </span>     Computer Engineering
                            Department </div>
                          <div><span class="Apple-tab-span"
                              style="white-space: pre; "> </span>      
                                  Phone: +39 081 7683823 -- Fax: +39 081
                            7683816</div>
                          <div>                                         
                             e-mail: <a moz-do-not-send="true"
                              href="mailto:spromano@unina.it">spromano@unina.it</a></div>
                          <div><br>
                          </div>
                          <div><span class="Apple-tab-span"
                              style="white-space: pre; "> </span>   
                            &lt;&lt;Molti mi dicono che lo
                            scoraggiamento è l'alibi degli </div>
                          <div><span class="Apple-tab-span"
                              style="white-space: pre; "> </span>  
                             idioti. Ci rifletto un istante; e mi
                            scoraggio&gt;&gt;. Magritte.</div>
                          <div>              <span
                              class="Apple-converted-space"> </span><span
                              class="Apple-tab-span" style="white-space:
                              pre; "> </span>                     oooO</div>
                          <div>  ~~~~~~~~~~~~~~~~~~~~~~~(  
                            )~~~ Oooo~~~~~~~~~~~~~~~~~~~~~~~~~</div>
                          <div><span class="Apple-tab-span"
                              style="white-space: pre; "> </span>     
                                       \ (            (   )</div>
                          <div><span class="Apple-tab-span"
                              style="white-space: pre; "> </span>     
                                                        \_)          ) /</div>
                          <div>                                         
                                                         (_/</div>
                        </div>
                        <div><br>
                        </div>
                      </div>
                    </span><br class="Apple-interchange-newline">
                  </div>
                </span><br class="Apple-interchange-newline">
              </div>
            </span><br class="Apple-interchange-newline">
          </span><br class="Apple-interchange-newline">
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------060702040703040602070504--


From nobody Thu Apr 17 07:26:47 2014
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01BB71A00E6 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level: 
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 WzjaYn6WqZIf for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:26:40 -0700 (PDT)
Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 669BF1A00A3 for <ietf@ietf.org>; Thu, 17 Apr 2014 07:26:40 -0700 (PDT)
Received: by mail-ob0-f173.google.com with SMTP id wn1so522090obc.18 for <ietf@ietf.org>; Thu, 17 Apr 2014 07:26:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=hWjBu0qzDq0W1VFTUNwPu+OPzDLasG6A5skckpIvyzg=; b=KczLDad0K1UMc3FEXcOq65YfOYeZDjwquhgqs6dQF6OkRNoaQoYHi5tuePsCoAgzOb A8GMh1R0D6c47Y9pgW9r8CQxjz/iCRmc2VgGwARuwcstga+Y2yb4zjGXA3qp/1xSccxm hZnbn/YLj+u1S4SfkyYKgaTOpdvnIAoTVGjNs=
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:content-type; bh=hWjBu0qzDq0W1VFTUNwPu+OPzDLasG6A5skckpIvyzg=; b=MpC2ff6Vfen9VWYxBczViNXD6SmdxhgsOAedKeesxWWGG6w8335XR/CU+Gfzk8c3t0 nPefqr+kWn6W5kCZmDsU5M+QP4D0uyRx2pOCPFq/S6SHLtZb5FO8CSa2HPkFtvycaFJH X155Lw3dmGEebC7927YAk7WIwyVGvkK6M7nf54XdTUQaiPg70mFUStp7yZ8tlRu8rSeu SmaLUpTz5Gtn27lSSDwakSCObWE0amaA6H9HL63UjAK0uG16znyyNCgWr8SJuVoL5UyY dF0FzLYgpJoTqJp4dr9rAWXq+urUjFjwvVspiNUlJ/Wq2dMmw+wkw2nSkJHF7UNqSyHR a14Q==
X-Gm-Message-State: ALoCoQnOYdTeiJ9LZZDw9ssOynNZj6eW6bHS4vz6NCDL5JvpKQBZULmaAqzEHXBYmlZJlAQHC/Mk
MIME-Version: 1.0
X-Received: by 10.182.104.101 with SMTP id gd5mr2267851obb.54.1397744796830; Thu, 17 Apr 2014 07:26:36 -0700 (PDT)
Received: by 10.60.93.6 with HTTP; Thu, 17 Apr 2014 07:26:36 -0700 (PDT)
In-Reply-To: <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org>
Date: Thu, 17 Apr 2014 15:26:36 +0100
Message-ID: <CAKHUCzzzsTLmcnRkyCobkimg5z4bAiCfpnsTuZ+PBksTjRKsBg@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: Dave Cridland <dave@cridland.net>
To: Thomas Clausen <ietf@thomasclausen.org>
Content-Type: multipart/alternative; boundary=089e0115ec141a24ea04f73dd27b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GxSsDRn7uIF1BPrAYw53sAT92sc
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 14:26:45 -0000

--089e0115ec141a24ea04f73dd27b
Content-Type: text/plain; charset=UTF-8

On 16 April 2014 14:31, Thomas Clausen <ietf@thomasclausen.org> wrote:

> And, convincing the IESG to start treating "Experimental" as exactly what
> you describe (and what, I believe, they were intended for) is simply not
> doable?
>
> FWIW, my personal belief is that "running code" should be a requirement
> for anything going std. track -- and that a (mandatory) period as
> Experimental prior to go std. track would yield the stable spec against
> which to reasonably build code, and run (interoperability) tests, fix bugs,
> etc. If after (pulling a number out my hat here) a year as Experimental
> there's no running code, then that's probably a good indicator, also, as to
> if this is something the IETF should bother doing....
>
>
Instead of Experimental, maybe a state before the standards-track proper,
called "Proposed Standard", might work, beyond which you'd need two
interoperable implementations to demonstrate utility and functionality.

I appreciate it's a radical suggestion.

Dave.

--089e0115ec141a24ea04f73dd27b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On 1=
6 April 2014 14:31, Thomas Clausen <span dir=3D"ltr">&lt;<a href=3D"mailto:=
ietf@thomasclausen.org" target=3D"_blank">ietf@thomasclausen.org</a>&gt;</s=
pan> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><spa=
n style=3D"color:rgb(34,34,34)">And, convincing the IESG to start treating =
&quot;Experimental&quot; as exactly what you describe (and what, I believe,=
 they were intended for) is simply not doable?</span><br>
</div></div>
<br>
FWIW, my personal belief is that &quot;running code&quot; should be a requi=
rement for anything going std. track -- and that a (mandatory) period as Ex=
perimental prior to go std. track would yield the stable spec against which=
 to reasonably build code, and run (interoperability) tests, fix bugs, etc.=
 If after (pulling a number out my hat here) a year as Experimental there&#=
39;s no running code, then that&#39;s probably a good indicator, also, as t=
o if this is something the IETF should bother doing....<br>

<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Instead of Experime=
ntal, maybe a state before the standards-track proper, called &quot;Propose=
d Standard&quot;, might work, beyond which you&#39;d need two interoperable=
 implementations to demonstrate utility and functionality.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I appreciat=
e it&#39;s a radical suggestion.</div><div class=3D"gmail_extra"><br></div>=
<div class=3D"gmail_extra">Dave.</div></div>

--089e0115ec141a24ea04f73dd27b--


From nobody Thu Apr 17 07:31:08 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 720561A011E for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:31:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.773
X-Spam-Level: 
X-Spam-Status: No, score=-14.773 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_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 JC6zT10qGBoi for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:30:57 -0700 (PDT)
Received: from mtv-iport-2.cisco.com (mtv-iport-2.cisco.com [173.36.130.13]) by ietfa.amsl.com (Postfix) with ESMTP id 47D821A0169 for <ietf@ietf.org>; Thu, 17 Apr 2014 07:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9763; q=dns/txt; s=iport; t=1397745054; x=1398954654; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=vzTTzsG6GjsFTlPFomobH42dwsag5okpD8B9OQueY44=; b=bmqNtFi7/j/rrdQEiN7MzaDn1te//qBfkDCqDFWWJaYQhhLRDnHoj/LB DwdcWjdfVzeREtgNAgy7sD1TI4jJ2iL94w283X0eZGq8LowV0wbG4fa0n +aQEGKE8v26q1pNRCE3Bh0oPMsuMUjuiCOwH3S97+tcbEjzLvVUexBoSb k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgkFADblT1OrRDoJ/2dsb2JhbABPCoMGO8Q2gSUWdIIlAQEBBDgzDQEQCw4EBgkWDwkDAgECAQ8oDgYBDAEFAgEBEAIFh00DEA7EAg2GWxeJPYMMgT0EJTMHhDgBA5UAggCBboE3hSGGJYVQgzM7gSw
X-IronPort-AV: E=Sophos;i="4.97,879,1389744000"; d="scan'208";a="110597807"
Received: from mtv-core-4.cisco.com ([171.68.58.9]) by mtv-iport-2.cisco.com with ESMTP; 17 Apr 2014 14:30:53 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by mtv-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3HEUoqa008025; Thu, 17 Apr 2014 14:30:51 GMT
Message-ID: <534FE599.5020001@cisco.com>
Date: Thu, 17 Apr 2014 16:30:49 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Thomas Nadeau <tnadeau@lucidvision.com>, Alia Atlas <akatlas@gmail.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com> <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com> <27F3F43E-683F-440D-9761-DD56CD8FD096@lucidvision.com>
In-Reply-To: <27F3F43E-683F-440D-9761-DD56CD8FD096@lucidvision.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Eo9cIb2qKiOv1k7EBsVbDG0BU-0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 14:31:03 -0000

On 17/04/2014 02:28, Thomas Nadeau wrote:
> On Apr 14, 2014:12:07 PM, at 12:07 PM, Alia Atlas <akatlas@gmail.com> w=
rote:
>
>> On Mon, Apr 14, 2014 at 11:57 AM, David Meyer <dmm@1-4-5.net> wrote:
>>> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.c=
om> wrote:
>>>> I=92m surprised that no one has sent this out yet:
>>>> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>>>>
>>>> "Summary: After contributing to standards organizations for more tha=
n seven
>>>> years, engineer Vidya Narayanan decided it was time to move on. Alth=
ough she
>>>> still believes that these organizations make the Internet a better p=
lace,
>>>> she wonders about the pace of change versus the pace of organization=
s."
>>>>
>>>> My thoughts-
>>>>
>>>> There are some nuggets of truth in what she says in this article, an=
d in
>>>> some of the comments. I think that the problems are real, so there=92=
s value
>>>> in taking the criticism constructively, despite the fact that the au=
thor
>>>> chose to focus on the problems without any suggestions of solutions.=

>>>>
>>>> "while the pace at which standards are written hasn=92t changed in m=
any years,
>>>> the pace at which the real world adopts software has become orders o=
f
>>>> magnitude faster."
>>>> =85
>>>> "Running code and rough consensus, the motto of the IETF, used to be=

>>>> realizable at some point. =85 In the name of consensus, we debate fr=
ivolous
>>>> details forever. In the name of patents, we never finish.=94
>>>> =85
>>>> "Unless these standards organizations make radical shifts towards
>>>> practicality, their relevance will soon be questionable.=94
>>>>
>>>> I don=92t have too many big ideas how to fix these problems, but I=92=
ll at least
>>>> take a crack at it in order to spur discussion. My paraphrase of the=
 problem
>>>> and some discussion follows.
>>>>
>>>> - We=92ve lost sight of consensus and are too often derailed by a vo=
cal
>>>> minority of those willing to endlessly debate a point.
>>>>
>>>> Part of the solution to that is reiterating what consensus is and is=
 not,
>>>> such as draft-resnick-on-consensus so that we don=92t confuse a need=
 for
>>>> consensus with a need for unanimity. Part of the solution is IETF le=
adership
>>>> helping to identify when we have rough consensus encumbered by a deb=
ate that
>>>> will never resolve itself, without quieting actual disagreement that=
 needs
>>>> continued discussion in order to find a compromise. I don=92t have g=
ood
>>>> suggestions on how to make that second half better.
>>>>
>>>> - We don=92t have nearly enough focus on running code as the thing t=
hat helps
>>>> to ensure that we=92re using our limited cycles on getting the right=
 things
>>>> out expediently, and either getting the design right the first time,=
 or
>>>> failing quickly and iterating to improve
>>>>
>>>> The solution here may be that we need to be much more aggressive at
>>>> expecting any standards track documents to have running code much ea=
rlier in
>>>> the process. The other part of that is to renew our focus on actual =
interop
>>>> standards work, probably by charter or in-group feedback, shift focu=
s away
>>>> from BCP and info documents. Perhaps when considering whether to pro=
ceed
>>>> with a given document, we need test as to whether it=92s actively
>>>> helpful/needed and ensure that we know what audience would be lookin=
g at it,
>>>> rather than simply ensuring that it is =93not harmful=94 and mostly =
within the
>>>> WG=92s chartered focus.
>>> My friend @colin_dixon pointed this out to me yesterday, and I've bee=
n
>>> giving it quite a bit of thought since then (I have a nascent blog on=

>>> the topic of how open source and standards orgs might
>>> productively/efficiently work together; follow up to
>>> http://www.sdncentral.com/education/david-meyer-reflections-opendayli=
ght-open-source-project-brocade/2014/03).
>>>
>>> What I can say is that after seeing the kind of progress that several=

>>> open source communities make (they do epitomize the best of the IETF'=
s
>>> running code/rough consensus ethic), one does have to wonder if
>>> traditional standards making is either obsolete or in dire need of a
>>> make over. What is needed, IMO, is a reimagining of how the standards=

>>> process interacts with the open source movement specifically focused
>>> on how they can compliment one another.
>> [Alia] It would be very useful to have a functional model for how the
>> two can compliment each other.  We also tend to talk about open-source=

>> as a single monolith - when it can have very different models for
>> accepting in changes, how and who runs the community, who is really
>> participating (open source doesn't mean non-corporate) etc.   Some of
>> what the IETF does is the architecture and requirements thinking about=

>> how the solution should fit in - while some of the open-source is
>> about getting a solution implemented ASAP.   IMHO, a spiral is useful
>> with an easy way of interaction.  With I2RS, as a WG chair, I
>> suggested having experimental drafts describing solutions that were
>> being implemented - but haven't seen any.   A question is what is
>> needed to encourage the interactions.
> 	I think this is where things (start to) go wrong with the existing IET=
F model. We need drafts of everything is an axiom here that we should cha=
llenge. In open source, the code, its associated wiki pages and perhaps a=
uto-gen docs are the draft and implementation agreement/documentation in =
question.
>
> 	I would also challenge what has become the common new WG "formula" the=
se days. That is the notion that requirements, problem statements or arch=
itectures are always needed and must come before the WG can work on any p=
rotocols/solutions. These are heavy burdens that have a price of slowing =
things down. If we want to pay that price, we'd better get something good=
 in return. However, the road is littered with many examples of recent WG=
s getting nowhere after several years of work. These groups often end up =
in this state because frankly many of the people involved in those effort=
s are completely disconnected from the reality of building the things the=
y are apparently designing. In many cases they never have built anything =
either, so much of the effort goes into explaining to them why things nee=
d to be a certain way/etc... Unfortunately their "veto" or influence in t=
he process also dilutes the simplicity that an implementation would revea=
l (i.e.: useless options).  Its clearly the difference between theory and=
 practice, which I think we all understand is a real thing.   The end res=
ult is that this impedance is one quantifiable reason why people have loo=
ked to over avenues such as open source, to build interoperable systems/t=
ools/etc... quickly.
>
> 	The solution: join the IETF process to the open source communities *wh=
ere it makes sense, but not otherwise*. Open source BTW is what we used t=
o call a rough-concensus + running code around here!
> If we stick to interfaces that need "on the wire" interoperability, we =
are in the sweet spot. If we wade into areas where there is little value =
added - such as requirements/problem statements/architectures, lets not w=
aste our time.
> For example, there are clearly cases where an RFC standard for somethin=
g does not makes sense. Something like Open stack is a good example. The =
APIs are there, implemented in code you can see and documented. There is =
a well defined change process that identifies stable release points and a=
lso allows for quick iteration on that code/interfaces to evolve that wor=
ks very quickly. Why would anyone every need an RFC for these things?  No=
w there really are cases where formal standardization makes sense. As I s=
aid if we stick to interfaces that need "on the wire" interop, we are squ=
arely somewhere both open source and the IETF can add value. For example,=
 there is a lot of code generation in open source based on yang models th=
ese days. Many of the experts around the model creation are at the IETF a=
nd not necessarily in those communities, so joining those folks to model =
creation can help that running code. In cases where vendors really want i=
nterop at the model level, then lets get together the vendors/operators t=
hat care, and not only build running code to test/prove those models make=
 sense, but then run them through the IETF process in parallel.
If a WG can't agree on which problem(s) it want to solve, then there is=20
a problem, no?
And not sure if Open Source is the solution, unless everybody says:=20
"here is my view of the problem, let me provide some code for it"

Note: I've been involved in a couple of WGs where defining a terminology =

was a time-consuming but well-worth effort, in order to produce the=20
requirements/problem statement and architecture document. We're all=20
engineers, and the fun part is to design protocols or write code.
However, I agree that requirements/problem statement/architecture RFCs=20
should be produced way faster within the IETF. And maybe, the IESG=20
should be stricter regarding deadlines for problem statements: if the WG =

can't agree on the problem statement by date D, the WG is closed.


Regards, Benoit

>
> 	--Tom
>
>
>
>> [Alia] Diversity of implementation is important as is stability of a
>> standard and it being understood how to change/upgrade for different
>> versions.  These don't come automatically via open-source.
>>
>> Regards,
>> Alia
>>
>>



From nobody Thu Apr 17 07:44:02 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D5B41A01D8 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:44:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_65=0.6, SPF_PASS=-0.001] autolearn=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 zRJa-HkuAblI for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:43:56 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.4]) by ietfa.amsl.com (Postfix) with ESMTP id F10A21A01B0 for <ietf@ietf.org>; Thu, 17 Apr 2014 07:43:55 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES532.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Thu, 17 Apr 2014 10:43:51 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Yoav Nir <ynir.ietf@gmail.com>, "mrex@sap.com" <mrex@sap.com>
Subject: RE: (DMARC) Why mailing lists are only sort of special
Thread-Topic: (DMARC) Why mailing lists are only sort of special
Thread-Index: AQHPWRoxnodbH1Opo0yBe6XfZ9Wz4JsU18QAgAAWRwCAAApxAIAABUoAgAChhwCAAEc/AIAAJ2oAgAAERgD//8KkEA==
Date: Thu, 17 Apr 2014 14:43:50 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D491B9@USCLES544.agna.amgreetings.com>
References: <20140417131134.5CEFC1ACCF@ld9781.wdf.sap.corp> <3DA69075-C8DB-4E40-8B2C-849AE05CCFF1@gmail.com>
In-Reply-To: <3DA69075-C8DB-4E40-8B2C-849AE05CCFF1@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RlslFYoaGVI96fObv42bAKgaJq0
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 14:44:00 -0000

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Yoav Nir
> Sent: Thursday, April 17, 2014 9:27 AM
> To: mrex@sap.com
> Cc: ietf@ietf.org
> Subject: Re: (DMARC) Why mailing lists are only sort of special
>=20
>=20
> On Apr 17, 2014, at 4:11 PM, Martin Rex <mrex@sap.com> wrote:
>=20
> > Yoav Nir wrote:
> >>
> >> On Apr 17, 2014, at 9:35 AM, Dave Cridland <dave@cridland.net> wrote:
> >>>
> >>> Right now, my MUA treats this as a message "From John R Levine
> >>> <johnl@taugh.com>". This means that any policy on the message
> >>> origination comes from looking solely at the taugh.com domain. We'll
> >>> pretend it has a DMARC policy. Herein lies the Yahoo/DMARC issue,
> >>> because unless your policy essentially stipulates that the IETF is
> >>> allowed to spoof you, we're stuck.
> >>
> >> Then perhaps this is what needs to change. John R Levine did not send
> >> you a message. He sent a message to the list. It is the list software
> >> that sent you a message. So perhaps the From field should have been
> >> ?From: IETF Mailing list on behalf of John R Levine <ietf@ietf.org>?.
> >
> > But that is EXACTLY what the IETF mailing list exploder *IS* doing
> > exactly as it has been specified for ages:
> >
> > https://tools.ietf.org/html/rfc822#section-4.4.2
> > https://tools.ietf.org/html/rfc822#appendix-A.2
> >
> > https://tools.ietf.org/html/rfc5322#section-3.6.2
> >
> >            The "From:" field specifies the author(s) of the message,
> >   that is, the mailbox(es) of the person(s) or system(s) responsible
> >   for the writing of the message.  The "Sender:" field specifies the
> >   mailbox of the agent responsible for the actual transmission of the
> >   message.
> >
> >  From: Yoav Nir <ynir.ietf@gmail.com>
> >  Subject: Re: (DMARC) Why mailing lists are only sort of special
> >  Errors-To: ietf-bounces@ietf.org
> >  Sender: ietf <ietf-bounces@ietf.org>
> >  Date: Thu, 17 Apr 2014 13:50:30 +0300
> >  Message-ID: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
> >  To: Dave Cridland <dave@cridland.net>
> >  CC: "ietf@ietf.org" <ietf@ietf.org>
> >
> >
> > Something as old as Outlook 2003 will properly display a message that
> > is received with a "Sender:" as "<Sender> on behalf of <From>"
>=20
> A client as new as Mail.app on Mac OS X 10.9 does not.
>=20
> Obviously the Sender: field is not where the DMARC implementations use
> for checking policy.
>=20
Yoav, this is by design.=20

There is no reliable way to determine the relationship between the Sender:f=
ield and the From: field from an authentication and authorization perspecti=
ve at the domain level unless both are within the same domain space. Other =
than "I say so", how do we know that the Sender IS truly acting on behalf o=
f the author in the From field where they are not both in the same domain s=
pace? This is the crux of the debate that has been going on for quite a few=
 years. As a receiver, on what basis can I trust the sender is authorized i=
n this circumstance? John says, "trust the mail (is on behalf of the author=
 because you trust me". This actually has worked in the real world for some=
 time but has been under increasing pressure due to abuse. While mailing li=
sts have not been a significant vector in the past (John says never, I say =
I have seen abusive mail passed through lists so never is not true), that i=
s not to say they will not be a significant vector.

Some people are unhappy that DMARC ties identity to the From:field. Identit=
y could just as easily have been tied to the Mail From:field but there stil=
l would have been a need for alignment ( going the other way) and ultimatel=
y there still would have been an issue with the Sender:field if the goal is=
 to provide a model for authentication/authorization that does not have sig=
nificant defects allowing abuse (and again we are only talking about the pr=
oblem space of direct domain abuse, not phishing or spam in general). The o=
nly reason for alignment is because of the use of both IP based (transport =
layer) and message based (requiring examination of the message body) authen=
tication.

The problem with an approach of trying to identify trust relationships betw=
een domains (let alone authors and domains acting on behalf of individual a=
uthors at other domains) is that it is not a linear relationship. That is, =
the complexity of potential trust relationships does not increase in a line=
ar fashion as we add more users and domains to the equation. There are othe=
r/easier ways of approaching the stated goal of authentication/authorizatio=
n.

In going back and re reading RFC 822 (1982), RFC 2822 (2001) and RFC 5322 (=
2008), I notice a small but important change between RFC 822 and RFC 2822. =
RFC 822 actually specified "This field contains the authenticated identity.=
.." for both the From:field and Sender:field among others. I followed the d=
iscussion for RFC2822 but was not an active participant. I don't remember s=
ignificant discussion on this change but there may have been some. If this =
requirement had been maintained AND had been implemented, it is quite possi=
ble we would be having a different discussion today.

In the examples given in RFC822 for use of Sender:Field, where a domain nam=
e is used, all of the Sender:field email address Domains (someone please va=
lidate this as I went through the "A." examples once and somewhat quickly) =
were the same as the From:field email address domains although there were e=
xamples where the Sender:Field display name domain was different. On a side=
 note, for the next update it might be appropriate to drop the word "secret=
ary" and substitute "assistant" in the example given - a nit but appropriat=
e nonetheless.=20

So it's clear that contrary to some assertions that we have today's issues =
with email because authentication/security was not thought of, there was in=
 fact some consideration given to authentication/security in the original s=
pecification.=20

Just a few thoughts.

Mike


From nobody Thu Apr 17 07:49:58 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 919281A01E3 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level: 
X-Spam-Status: No, score=-4.573 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 LEx60tdAknv2 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 07:49:52 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 86C2B1A01E1 for <ietf@ietf.org>; Thu, 17 Apr 2014 07:49:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1397746189; x=1429282189; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=Ey36L/Rta8E9vAtMiSnQyTQtWnXTwYQY58zOVx0/XO8=; b=mCOYMH0RvSRMC9JU+0pY/y+J+M63jxKziivXliiK42OjGZ+AfNFXKJKU Ary9c13iPNnrniSWsEzXrGstgRSL4UIaee2UNaSOu/RMwjSAuFCwsk7eL A9a1oWnVEARpRyyewNbKsOnMVYYDcpYZNV6laAaNbwrB3HWa+njY3wDu4 U=;
X-IronPort-AV: E=McAfee;i="5400,1158,7410"; a="29415880"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 17 Apr 2014 07:49:49 -0700
X-IronPort-AV: E=Sophos;i="4.97,879,1389772800"; d="scan'208";a="650580433"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 17 Apr 2014 07:49:48 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 17 Apr 2014 07:49:48 -0700
Message-ID: <534FEA0A.4050607@qti.qualcomm.com>
Date: Thu, 17 Apr 2014 09:49:46 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John R Levine <johnl@taugh.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com> <alpine.BSF.2.00.1404162346400.2194@joyce.lan> <534F5E67.1010307@qti.qualcomm.com> <alpine.BSF.2.00.1404170824350.2692@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1404170824350.2692@joyce.lan>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Xn1Q-b3aIUZvOCcLOvjkPIn30fA
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 14:49:56 -0000

On 4/17/14 7:29 AM, John R Levine wrote:
> Now I'm totally confused.  How does that help me as a sender 
> distinguish between a good mailing list that is resending real mail 
> from Yahoo and an evil mailing list that is sending phishes?

We're now *way* into technical discussion. Let's take those to 
https://www.ietf.org/mailman/listinfo/dmarc shall we?

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Thu Apr 17 08:04:16 2014
Return-Path: <aaronyiding@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8B241A02F1; Thu, 17 Apr 2014 01:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.423
X-Spam-Level: *
X-Spam-Status: No, score=1.423 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 23oQYo7MOe4F; Thu, 17 Apr 2014 01:59:10 -0700 (PDT)
Received: from mail-ob0-x232.google.com (mail-ob0-x232.google.com [IPv6:2607:f8b0:4003:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 511F81A0108; Thu, 17 Apr 2014 01:59:10 -0700 (PDT)
Received: by mail-ob0-f178.google.com with SMTP id wn1so152825obc.37 for <multiple recipients>; Thu, 17 Apr 2014 01:59:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=xvkuxSHXzikSKgYqxO+yDH6JJoiiLRAHDiOtjf/5rSY=; b=VCfl20YlTGPjNMZPA9PLKXJa3sH7VcJWmJtxxp7lXhvqK6Ug9KPuAcmBRDRfZZ0264 RDIvX6bo1MVJ1DRqnpp300IKTq8tB9D6iY5j+KdHOY3l0I/2ZJE6/zYdAIDw9fpCLvxV fi/lbNY+oS4GMKqdxYtuajUQGsv4c8ehQyiJOtwo9qOSyLfSeQ9WD6/XnZu5nxkHb6uA +ORH+Ez1bqUsF0zsg21epErfYwMifjBTyetlKs9RyzToe0ix+moFmn6e2BnXTdy4uoH0 By9dc/mpXDpys5BWfDjvKMVfFVJusBjnBaHpEfNierhfpRPic4yF+gdk7wuRWZheIp1W bZgg==
MIME-Version: 1.0
X-Received: by 10.60.135.106 with SMTP id pr10mr10967404oeb.15.1397725146721;  Thu, 17 Apr 2014 01:59:06 -0700 (PDT)
Sender: aaronyiding@gmail.com
Received: by 10.182.8.42 with HTTP; Thu, 17 Apr 2014 01:59:06 -0700 (PDT)
Date: Thu, 17 Apr 2014 11:59:06 +0300
X-Google-Sender-Auth: darjmAH6vsQ20r19HbM_dkzJfW0
Message-ID: <CANqPRgyAQ2tmrSV8DhorbYTNVGH9qGL8jhBFWJrjG2p+prozFw@mail.gmail.com>
Subject: IETFer's work received ACM Computing Review
From: Aaron Yi DING <Aaron.Ding@cl.cam.ac.uk>
To: ietf@ietf.org, irtf-discuss@irtf.org, diversity@ietf.org
Content-Type: multipart/alternative; boundary=047d7b41791ddd30df04f7393ed3
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/E52-MXpyAOxzQCq_zt39kD99bvo
X-Mailman-Approved-At: Thu, 17 Apr 2014 08:04:14 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 08:59:15 -0000

--047d7b41791ddd30df04f7393ed3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

picked up by the Computing Review, by a couple of ietfers (e.g., Jouni
Korhonen, J=C3=B6rg Ott, Jon Crowcroft)

http://www.computingreviews.com/Browse/Browse_titles2.cfm?journal_id=3D6052

Bridging the gap between Internet standardization and networking research

---------------------------------------
ACM Computing Review
"
Bridging the gap between the network research community and Internet
standards is an important topic. Most network research has not been turned
into an Internet standard, while some research comes a long way in order to
become an Internet standard. Very few studies investigate this issue
because it extends beyond purely technical concerns.

The authors have an advantage in investigating this issue since they have
tightly collaborated on projects with academic researchers and industrial
professionals. They thoroughly present their observations and share their
experiences in this paper. The challenges for this gap are defined in two
parts: technical challenges and nontechnical challenges. A good point is
that the authors share the nontechnical challenges that might be ignored by
researchers and industrial professionals. The authors, aware of the gap,
also find two major opportunities that can extend research works to
standardization contributions, which is encouraging to networking
researchers.

Based on their past experiences, the authors share two concrete case
studies: mobile traffic offloading and Internet protocol version 6 (IPv6)
transition technologies. The mobile traffic offloading case shows
substantial scientific results, but it also shows an under-performing
standardization effort. This case proves that the proposal, which does not
fit in an existing mindset, is usually a failure. On the other hand, the
case of IPv6 transition technologies shows good results in both academia
and industry, because the research proposal has extensibility and minimum
impact on the existing infrastructure. The authors then share their lessons
and suggestions to bridge the gap. These are honest and useful to both
academia and industry. Readers will see the potential for comprehensive
collaboration between networking research and Internet standardization.
"

----------------------
ACM SIGCOMM CCR chief editor:

"Its focus is to identify ways to bridge the gap between the networking
community and the Internet standardization bodies. The authors, from
Broadcom, Nokia, University of Cambridge, Aalto University and University
of Helsinki, are describing the differences and similarities between how
the two communities operate. They further provide interesting data on the
participation of academic and industrial researchers in standardization
bodies. They discuss ways to minimize the friction that may exist as a
particular technology is making the leap from the scientific community into
the industry."


Two cents,
Aaron

-----------
http://www.cl.cam.ac.uk/~ad707/

--047d7b41791ddd30df04f7393ed3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">picked up by the Computing Review, by a couple of ietfers =
(e.g., Jouni Korhonen, J=C3=B6rg Ott, Jon Crowcroft)<br>
<br>
<a href=3D"http://www.computingreviews.com/Browse/Browse_titles2.cfm?journa=
l_id=3D6052">http://www.computingreviews.com/Browse/Browse_titles2.cfm?jour=
nal_id=3D6052</a><br>
<br>
Bridging the gap between Internet standardization and networking research<b=
r>
<br>
---------------------------------------<br>
ACM Computing Review<br>
&quot;<br>
Bridging the gap between the network research community and Internet=20
standards is an important topic. Most network research has not been=20
turned into an Internet standard, while some research comes a long way=20
in order to become an Internet standard. Very few studies investigate=20
this issue because it extends beyond purely technical concerns.<br>
<br>
The
 authors have an advantage in investigating this issue since they have=20
tightly collaborated on projects with academic researchers and=20
industrial professionals. They thoroughly present their observations and
 share their experiences in this paper. The challenges for this gap are=20
defined in two parts: technical challenges and nontechnical challenges. A
 good point is that the authors share the nontechnical challenges that=20
might be ignored by researchers and industrial professionals. The=20
authors, aware of the gap, also find two major opportunities that can=20
extend research works to standardization contributions, which is=20
encouraging to networking researchers.<br>
<br>
Based on their past=20
experiences, the authors share two concrete case studies: mobile traffic
 offloading and Internet protocol version 6 (IPv6) transition=20
technologies. The mobile traffic offloading case shows substantial=20
scientific results, but it also shows an under-performing=20
standardization effort. This case proves that the proposal, which does=20
not fit in an existing mindset, is usually a failure. On the other hand,
 the case of IPv6 transition technologies shows good results in both=20
academia and industry, because the research proposal has extensibility=20
and minimum impact on the existing infrastructure. The authors then=20
share their lessons and suggestions to bridge the gap. These are honest=20
and useful to both academia and industry. Readers will see the potential
 for comprehensive collaboration between networking research and=20
Internet standardization.<br>
&quot;<br>
<br>
----------------------<br>
ACM SIGCOMM CCR chief editor: <br>
<br>
&quot;Its focus is to identify ways to bridge the gap between the networkin=
g=20
community and the Internet standardization bodies. The authors, from=20
Broadcom, Nokia, University of Cambridge, Aalto University and=20
University of Helsinki, are describing the differences and similarities=20
between how the two communities operate. They further provide=20
interesting data on the participation of academic and industrial=20
researchers in standardization bodies. They discuss ways to minimize the
 friction that may exist as a particular technology is making the leap=20
from the scientific community into the industry.&quot;<br>
<br>
<br>
Two cents,<br>
Aaron=C2=A0<br><div dir=3D"ltr"><br>-----------<br><a href=3D"http://www.cl=
.cam.ac.uk/%7Ead707/" target=3D"_blank">http://www.cl.cam.ac.uk/~ad707/</a>=
</div>
</div>

--047d7b41791ddd30df04f7393ed3--


From nobody Thu Apr 17 08:04:43 2014
Return-Path: <tglassey@earthlink.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89CE91A0284; Wed, 16 Apr 2014 13:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.428
X-Spam-Level: 
X-Spam-Status: No, score=0.428 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 w9VYCgRwlR7y; Wed, 16 Apr 2014 13:28:12 -0700 (PDT)
Received: from elasmtp-spurfowl.atl.sa.earthlink.net (elasmtp-spurfowl.atl.sa.earthlink.net [209.86.89.66]) by ietfa.amsl.com (Postfix) with ESMTP id D851F1A0304; Wed, 16 Apr 2014 13:28:11 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=rkJnMPFx3XNspdnC4TVZV69vgEFb3uXTE08chU1eITrT3R9qL503fzFIkcT4/RVT; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.134.155] (helo=[192.168.0.4]) by elasmtp-spurfowl.atl.sa.earthlink.net with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1WaWRB-0007A3-BL; Wed, 16 Apr 2014 16:28:05 -0400
Message-ID: <534EE7EE.7090401@earthlink.net>
Date: Wed, 16 Apr 2014 13:28:30 -0700
From: TGLASSEY <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ipr@ietf.org, ietf@ietf.org
Subject: We need to add the ability to upload attachments to the IPR Filings.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec7930ca9faf95e1c7e26a30b7ef890708d0350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.134.155
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qnm6K1Qmjk_e9oNkTlaoB9E0I0s
X-Mailman-Approved-At: Thu, 17 Apr 2014 08:04:38 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Apr 2014 20:28:13 -0000

In any number of instances the simple attachment of a sublicensing 
agreement or assignment contract which is already on file with the PTO 
to a IETF filing to ease parties doing diligence on these IP's would be 
a stroke of brilliance here.

It also would allow the IETF to take a more arms-length approach because 
it is accepting IP Statements in both its framework and language as 
described by BCP78 and 79 but also in adding the ability to reference a 
directly uploaded content document as part of the publication of the IP 
notice.

Todd

-- 
-------------

Personal Email - Disclaimers Apply


From nobody Thu Apr 17 08:31:02 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CD331A0271 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 08:31:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.281
X-Spam-Level: 
X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_65=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 0hJR_MyKbv0x for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 08:30:56 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4AA7A1A01DE for <ietf@ietf.org>; Thu, 17 Apr 2014 08:30:53 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 23851CC091 for <ietf@ietf.org>; Thu, 17 Apr 2014 11:30:50 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id EGnMhBeWtu6P for <ietf@ietf.org>; Thu, 17 Apr 2014 11:30:45 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 97753CC094 for <ietf@ietf.org>; Thu, 17 Apr 2014 11:30:44 -0400 (EDT)
Message-ID: <534FF3A3.2070504@meetinghouse.net>
Date: Thu, 17 Apr 2014 11:30:43 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: (DMARC) Why mailing lists are only sort of special
References: <20140417131134.5CEFC1ACCF@ld9781.wdf.sap.corp> <3DA69075-C8DB-4E40-8B2C-849AE05CCFF1@gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D491B9@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D491B9@USCLES544.agna.amgreetings.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8xaAd4ibs6YN9pZsqNTM8a9B-Ts
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 15:31:00 -0000

MH Michael Hammer (5304) wrote:
>
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Yoav Nir
>> Sent: Thursday, April 17, 2014 9:27 AM
>> To: mrex@sap.com
>> Cc: ietf@ietf.org
>> Subject: Re: (DMARC) Why mailing lists are only sort of special
>>
>>
>> On Apr 17, 2014, at 4:11 PM, Martin Rex <mrex@sap.com> wrote:
>>
>>> Yoav Nir wrote:
>>>> On Apr 17, 2014, at 9:35 AM, Dave Cridland <dave@cridland.net> wrote:
>>>>> Right now, my MUA treats this as a message "From John R Levine
>>>>> <johnl@taugh.com>". This means that any policy on the message
>>>>> origination comes from looking solely at the taugh.com domain. We'll
>>>>> pretend it has a DMARC policy. Herein lies the Yahoo/DMARC issue,
>>>>> because unless your policy essentially stipulates that the IETF is
>>>>> allowed to spoof you, we're stuck.
>>>> Then perhaps this is what needs to change. John R Levine did not send
>>>> you a message. He sent a message to the list. It is the list software
>>>> that sent you a message. So perhaps the From field should have been
>>>> ?From: IETF Mailing list on behalf of John R Levine <ietf@ietf.org>?.
>>> But that is EXACTLY what the IETF mailing list exploder *IS* doing
>>> exactly as it has been specified for ages:
>>>
>>> https://tools.ietf.org/html/rfc822#section-4.4.2
>>> https://tools.ietf.org/html/rfc822#appendix-A.2
>>>
>>> https://tools.ietf.org/html/rfc5322#section-3.6.2
>>>
>>>             The "From:" field specifies the author(s) of the message,
>>>    that is, the mailbox(es) of the person(s) or system(s) responsible
>>>    for the writing of the message.  The "Sender:" field specifies the
>>>    mailbox of the agent responsible for the actual transmission of the
>>>    message.
>>>
>>>   From: Yoav Nir <ynir.ietf@gmail.com>
>>>   Subject: Re: (DMARC) Why mailing lists are only sort of special
>>>   Errors-To: ietf-bounces@ietf.org
>>>   Sender: ietf <ietf-bounces@ietf.org>
>>>   Date: Thu, 17 Apr 2014 13:50:30 +0300
>>>   Message-ID: <B3467912-BDCA-4AE8-9939-60013DA99267@gmail.com>
>>>   To: Dave Cridland <dave@cridland.net>
>>>   CC: "ietf@ietf.org" <ietf@ietf.org>
>>>
>>>
>>> Something as old as Outlook 2003 will properly display a message that
>>> is received with a "Sender:" as "<Sender> on behalf of <From>"
>> A client as new as Mail.app on Mac OS X 10.9 does not.
>>
>> Obviously the Sender: field is not where the DMARC implementations use
>> for checking policy.
>>
> Yoav, this is by design.
>
> There is no reliable way to determine the relationship between the Sender:field and the From: field from an authentication and authorization perspective at the domain level unless both are within the same domain space. Other than "I say so", how do we know that the Sender IS truly acting on behalf of the author in the From

Well - if the originating system were to include To: in the signature, 
and it matched Sender: that would go a long way.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Thu Apr 17 08:34:46 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F4721A02A0 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 08:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.794
X-Spam-Level: **
X-Spam-Status: No, score=2.794 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 gAqKLvbzwH9d for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 08:34:40 -0700 (PDT)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id C9ECD1A01B9 for <ietf@ietf.org>; Thu, 17 Apr 2014 08:34:35 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6QVVK84IO005H9Q@mauve.mrochek.com> for ietf@ietf.org; Thu, 17 Apr 2014 08:29:30 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6O0FD8M9S00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 17 Apr 2014 08:29:23 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6QVVGQA4W00004W@mauve.mrochek.com>
Date: Thu, 17 Apr 2014 07:41:25 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Thu, 17 Apr 2014 03:57:21 -0400" <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/F8UfLBj6GMWI96DHEOqPUfDLV8A
Cc: ned+ietf@mauve.mrochek.com, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 15:34:44 -0000

John Klensin writes:

> --On Wednesday, April 16, 2014 23:00 -0700
> ned+ietf@mauve.mrochek.com wrote:

> >> It seems extreme to lay blame on the IETF in general
> >> merely for having an open mechanism by which to post a draft
> >> for all to see and discuss.  A "Request For Comment", as it
> >> were.
> >
> > You may think it extreme. I don't. I think the IETF's politics
> > have led to  it inching closer to moral hazard territory for a
> > long time, and with this incident it has stepped in it.

> Indeed.  We have had warnings about where the ability of anyone
> to post anything and then claim IETF approval in external
> contexts without any fear of meaningful pushback would lead for
> a long time.  It hasn't been significantly damaging before
> because (i) we have been lucky and (ii) attempts to manipulate
> the mechanisms have come from outsiders, not insiders.

Nicely put. I completely agree.

> With DMARC, the ability to claim IETF responsibility when that is
> handy and that the IETF has no control when _that_ is handy have
> now been utilized by insiders.

Or by people with better access to insiders. It's hard to tell, and I'm not
sure it really matters.

> That comes after a history of
> the less effective approach of bringing specs into IETF WGs and
> then claiming that fundamentals cannot be changed because they
> were developed by experts in another forum.  As I think Ned
> suggested, the ADSP issue and how it was handled should have
> been another warning sign.  And, with Yahoo's move and its
> consequences (whether they anticipated them or not), we also ran
> out of luck.

An onimous phrase, isn't it? But an accurate one, I fear.

> >> Are you suggesting that
> >> process should be closed or moderated somehow?
> >
> > What I suggested is that we need to have a serious discussion
> > of what, if anything can be done to ameliorate the damage in
> > this case. Others have suggested that we also need to look at
> > how to prevent this from happening in the future. I concur.

> agreed.

> >...
> >> I would add to this that, by its ultimate inaction in the
> >> face of a protracted period of abuse and attempts by
> >> participants to solve that problem within its procedures, the
> >> IETF has abdicated any authority it may have had.
> >
> > That may be your assessment. Given subsequent comments from
> > other people,  mine is now that this effort was looking for a
> > rubber stamp, didn't like it when that didn't happen, and
> > proceeded to skirt around the edges of the process.

> > With disasterous results.

> Exactly.

> I'm also concerned that several of these efforts represent back
> door approaches to deprecating multi-hop email.  Certainly many
> things are more convenient in a single hop environment.  They
> would become even more convenient if all email were to be
> handled by a small oligarchy of providers.  To the degree to
> which one simultaneously believes in openness and privacy, those
> would be very sad outcomes.

It's not just multi-hop email - although I agree it's in danger - it's various
semantics of email that happen not be to be useful to commercial email of
various sorts, and whose presence makes the problem more challenging. John
Levine refers to all this as "send on behalf of", which isn't exactly right but
is probably close enough for purposes of this discussion.

I also find it particularly revealing that one of the arguments being made here
is along of the lines of, "Everything else has had to change, why are those
stodgy old mailing list thingies somehow exempt?" Except that's not it at all -
the approach was always essentially, "We're going to screw you, how about you
do X or Y to mitigate the damage a little?" To which the answer, predictably,
was less than enthusiastic.

				Ned


From nobody Thu Apr 17 08:58:03 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 177F51A01CD for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 08:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.895
X-Spam-Level: 
X-Spam-Status: No, score=0.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 yNPRuLNPCT7o for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 08:57:48 -0700 (PDT)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id CB14D1A011C for <ietf@ietf.org>; Thu, 17 Apr 2014 08:57:47 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6QWPB175C005OB3@mauve.mrochek.com> for ietf@ietf.org; Thu, 17 Apr 2014 08:52:42 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6O0FD8M9S00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 17 Apr 2014 08:52:35 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6QWP7AI2G00004W@mauve.mrochek.com>
Date: Thu, 17 Apr 2014 08:46:53 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Thu, 17 Apr 2014 00:08:08 -0700" <833BDCD2-1157-4914-B385-C300AF33E2D4@gmail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <833BDCD2-1157-4914-B385-C300AF33E2D4@gmail.com>
To: Douglas Otis <doug.mtview@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Lsid-soQhgBSyVPcL1T3SqlaPSY
Cc: ned+ietf@mauve.mrochek.com, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 15:57:52 -0000

> On Apr 16, 2014, at 11:00 PM, ned+ietf@mauve.mrochek.com wrote:

> >> On Sat, Apr 12, 2014 at 4:35 PM, <ned+ietf@mauve.mrochek.com> wrote:
> >
> >>> The underlying technical issue is that the two technologies DMARC is built
> >>> on -
> >>> DKIM and SPF - both attach additional/restrictive semantics to
> >>> longstanding mail
> >>> system fields. (Broadly speaking, From: for DKIM and MAIL FROM for SPF.)
> >>>
> >
> >> Something's amiss here.  What new semantics does DKIM attach to From:?  As
> >> far as I know, it only requires that the field be signed.  It doesn't
> >> require that it be interpreted in a particular way or that it contain any
> >> particular value.
> >
> > I was trying to be brief. Yes, I'm well aware that DKIM can be used in other
> > ways. This entire discussion is within the context of DMARC here. Do you
> > disagree that DMARC's use of DKIM and SPF assign additional semantics to header
> > and envelope from fields respectively?

> Murray is correct. DKIM does not create special From header field semantics. 

Actually, by requiring that the signature cover the From: field, it sort
of does. But that's beside the point. Again, I was talking about DMARC's 
use of DKIM, not DKIM usage in general.

> However, DMARC semantics are similar to those of ADSP while avoiding some
> shortcomings.
 
But both of them attach additional semantics to From:. (Not that they had
a choice; as I pointed out previously, in order to acheieve the stated
goal they have to attach the check to the identity users actually see.)

> ...

> >> Also: By "the IETF published a draft", are you talking about an RFC, or the
> >> DMARC base draft?
> >
> > The draft, of course.
> >
> >> It seems extreme to lay blame on the IETF in general
> >> merely for having an open mechanism by which to post a draft for all to see
> >> and discuss.  A "Request For Comment", as it were.
> >
> > You may think it extreme. I don't. I think the IETF's politics have led to  it
> > inching closer to moral hazard territory for a long time, and with this
> > incident it has stepped in it.

> This disruption should be shared with the provider that has already
> enumerated 30,000 mailing-lists but made no effort to establish a means to
> verify these sources and to safely assert specific exceptions to DMARC
> alignment requirements. This ability is desperately needed before applying
> DMARC reject on user accounts.  I'll be happy to modify either ATP or ATPS to
> permit these exceptions without the need to alter mailing-list.

I'm by no means sure that ATP or ATPS is the right answer, but I certainly
agree that we need to at least try and address the situation that's been
created.

Sigh. We have a lot of work to do, don't we?

				Ned


From nobody Thu Apr 17 09:21:08 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48E7B1A00FB for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 09:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.895
X-Spam-Level: 
X-Spam-Status: No, score=0.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 q-JTb3GUdGR1 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 09:21:06 -0700 (PDT)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7764A1A00A3 for <ietf@ietf.org>; Thu, 17 Apr 2014 09:21:06 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6QXI8ARLS006P6S@mauve.mrochek.com> for ietf@ietf.org; Thu, 17 Apr 2014 09:16:01 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6O0FD8M9S00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 17 Apr 2014 09:15:53 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6QXI47QVW00004W@mauve.mrochek.com>
Date: Thu, 17 Apr 2014 09:11:55 -0700 (PDT)
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-reply-to: "Your message dated Thu, 17 Apr 2014 09:49:46 -0500" <534FEA0A.4050607@qti.qualcomm.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com> <alpine.BSF.2.00.1404162346400.2194@joyce.lan> <534F5E67.1010307@qti.qualcomm.com> <alpine.BSF.2.00.1404170824350.2692@joyce.lan> <534FEA0A.4050607@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cKksI4PS-1yOhH0U-w0KTZNC6pA
Cc: John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 16:21:07 -0000

> On 4/17/14 7:29 AM, John R Levine wrote:
> > Now I'm totally confused.  How does that help me as a sender
> > distinguish between a good mailing list that is resending real mail
> > from Yahoo and an evil mailing list that is sending phishes?

> We're now *way* into technical discussion. Let's take those to
> https://www.ietf.org/mailman/listinfo/dmarc shall we?

How about we take it some place else? I really don't want this intermingled
with discussions of things like how to revise the current DMARC specifications
that hopefully are taking place on that list.

This is especially true if you're talking about what I think you're talking
about: Senders discovering additional semantics of the recipients they are
sending to and then decorating the message accordingly. This is a fairly
radical idea which, if it pans out, may well have utility extending far beyond
DMARC.

				Ned


From nobody Thu Apr 17 09:28:12 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30C151A01E6 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 09:28:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 vgbznE90Rauj for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 09:28:10 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 052951A01DE for <ietf@ietf.org>; Thu, 17 Apr 2014 09:28:09 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 406F1CC0A7 for <ietf@ietf.org>; Thu, 17 Apr 2014 12:28:06 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id cwAFt0-dgd8i for <ietf@ietf.org>; Thu, 17 Apr 2014 12:28:01 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7EB32CC0B0 for <ietf@ietf.org>; Thu, 17 Apr 2014 12:28:01 -0400 (EDT)
Message-ID: <53500111.5000205@meetinghouse.net>
Date: Thu, 17 Apr 2014 12:28:01 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com> <alpine.BSF.2.00.1404162346400.2194@joyce.lan> <534F5E67.1010307@qti.qualcomm.com> <alpine.BSF.2.00.1404170824350.2692@joyce.lan> <534FEA0A.4050607@qti.qualcomm.com> <01P6QXI47QVW00004W@mauve.mrochek.com>
In-Reply-To: <01P6QXI47QVW00004W@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YXXjv0FsDW2_tA-EQMUC57lKz2g
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 16:28:11 -0000

ned+ietf@mauve.mrochek.com wrote:
>> On 4/17/14 7:29 AM, John R Levine wrote:
>> > Now I'm totally confused.  How does that help me as a sender
>> > distinguish between a good mailing list that is resending real mail
>> > from Yahoo and an evil mailing list that is sending phishes?
>
>> We're now *way* into technical discussion. Let's take those to
>> https://www.ietf.org/mailman/listinfo/dmarc shall we?
>
> How about we take it some place else? I really don't want this 
> intermingled
> with discussions of things like how to revise the current DMARC 
> specifications
> that hopefully are taking place on that list.

Any proposal as to where?

For that matter, any proposal on where to take the parallel discussion 
of process issues and IETF role?

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Thu Apr 17 10:35:18 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 29B5A1A0078 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 10:35:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.275
X-Spam-Level: 
X-Spam-Status: No, score=-0.275 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 l3a3X94IwUdh for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 10:35:12 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id A29331A0066 for <ietf@ietf.org>; Thu, 17 Apr 2014 10:35:11 -0700 (PDT)
Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id ADC75276C8D1; Thu, 17 Apr 2014 13:35:07 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_8C2CFB12-FE1F-4E05-8AFD-9C677054C5F8"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <534FE599.5020001@cisco.com>
Date: Thu, 17 Apr 2014 13:35:06 -0400
Message-Id: <1936431F-C9FB-4620-8CF6-B66F590A833B@lucidvision.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com> <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com> <27F3F43E-683F-440D-9761-DD56CD8FD096@lucidvision.com> <534FE599.5020001@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EXq3WSKr9cZQ3nszZDHoVdNPxNo
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 17:35:17 -0000

--Apple-Mail=_8C2CFB12-FE1F-4E05-8AFD-9C677054C5F8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 17, 2014:10:30 AM, at 10:30 AM, Benoit Claise <bclaise@cisco.com> =
wrote:

> On 17/04/2014 02:28, Thomas Nadeau wrote:
>> On Apr 14, 2014:12:07 PM, at 12:07 PM, Alia Atlas <akatlas@gmail.com> =
wrote:
>>=20
>>> On Mon, Apr 14, 2014 at 11:57 AM, David Meyer <dmm@1-4-5.net> wrote:
>>>> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes =
<wesley.george@twcable.com> wrote:
>>>>> I=92m surprised that no one has sent this out yet:
>>>>> =
http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>>>>>=20
>>>>> "Summary: After contributing to standards organizations for more =
than seven
>>>>> years, engineer Vidya Narayanan decided it was time to move on. =
Although she
>>>>> still believes that these organizations make the Internet a better =
place,
>>>>> she wonders about the pace of change versus the pace of =
organizations."
>>>>>=20
>>>>> My thoughts-
>>>>>=20
>>>>> There are some nuggets of truth in what she says in this article, =
and in
>>>>> some of the comments. I think that the problems are real, so =
there=92s value
>>>>> in taking the criticism constructively, despite the fact that the =
author
>>>>> chose to focus on the problems without any suggestions of =
solutions.
>>>>>=20
>>>>> "while the pace at which standards are written hasn=92t changed in =
many years,
>>>>> the pace at which the real world adopts software has become orders =
of
>>>>> magnitude faster."
>>>>> =85
>>>>> "Running code and rough consensus, the motto of the IETF, used to =
be
>>>>> realizable at some point. =85 In the name of consensus, we debate =
frivolous
>>>>> details forever. In the name of patents, we never finish.=94
>>>>> =85
>>>>> "Unless these standards organizations make radical shifts towards
>>>>> practicality, their relevance will soon be questionable.=94
>>>>>=20
>>>>> I don=92t have too many big ideas how to fix these problems, but =
I=92ll at least
>>>>> take a crack at it in order to spur discussion. My paraphrase of =
the problem
>>>>> and some discussion follows.
>>>>>=20
>>>>> - We=92ve lost sight of consensus and are too often derailed by a =
vocal
>>>>> minority of those willing to endlessly debate a point.
>>>>>=20
>>>>> Part of the solution to that is reiterating what consensus is and =
is not,
>>>>> such as draft-resnick-on-consensus so that we don=92t confuse a =
need for
>>>>> consensus with a need for unanimity. Part of the solution is IETF =
leadership
>>>>> helping to identify when we have rough consensus encumbered by a =
debate that
>>>>> will never resolve itself, without quieting actual disagreement =
that needs
>>>>> continued discussion in order to find a compromise. I don=92t have =
good
>>>>> suggestions on how to make that second half better.
>>>>>=20
>>>>> - We don=92t have nearly enough focus on running code as the thing =
that helps
>>>>> to ensure that we=92re using our limited cycles on getting the =
right things
>>>>> out expediently, and either getting the design right the first =
time, or
>>>>> failing quickly and iterating to improve
>>>>>=20
>>>>> The solution here may be that we need to be much more aggressive =
at
>>>>> expecting any standards track documents to have running code much =
earlier in
>>>>> the process. The other part of that is to renew our focus on =
actual interop
>>>>> standards work, probably by charter or in-group feedback, shift =
focus away
>>>>> from BCP and info documents. Perhaps when considering whether to =
proceed
>>>>> with a given document, we need test as to whether it=92s actively
>>>>> helpful/needed and ensure that we know what audience would be =
looking at it,
>>>>> rather than simply ensuring that it is =93not harmful=94 and =
mostly within the
>>>>> WG=92s chartered focus.
>>>> My friend @colin_dixon pointed this out to me yesterday, and I've =
been
>>>> giving it quite a bit of thought since then (I have a nascent blog =
on
>>>> the topic of how open source and standards orgs might
>>>> productively/efficiently work together; follow up to
>>>> =
http://www.sdncentral.com/education/david-meyer-reflections-opendaylight-o=
pen-source-project-brocade/2014/03).
>>>>=20
>>>> What I can say is that after seeing the kind of progress that =
several
>>>> open source communities make (they do epitomize the best of the =
IETF's
>>>> running code/rough consensus ethic), one does have to wonder if
>>>> traditional standards making is either obsolete or in dire need of =
a
>>>> make over. What is needed, IMO, is a reimagining of how the =
standards
>>>> process interacts with the open source movement specifically =
focused
>>>> on how they can compliment one another.
>>> [Alia] It would be very useful to have a functional model for how =
the
>>> two can compliment each other.  We also tend to talk about =
open-source
>>> as a single monolith - when it can have very different models for
>>> accepting in changes, how and who runs the community, who is really
>>> participating (open source doesn't mean non-corporate) etc.   Some =
of
>>> what the IETF does is the architecture and requirements thinking =
about
>>> how the solution should fit in - while some of the open-source is
>>> about getting a solution implemented ASAP.   IMHO, a spiral is =
useful
>>> with an easy way of interaction.  With I2RS, as a WG chair, I
>>> suggested having experimental drafts describing solutions that were
>>> being implemented - but haven't seen any.   A question is what is
>>> needed to encourage the interactions.
>> 	I think this is where things (start to) go wrong with the =
existing IETF model. We need drafts of everything is an axiom here that =
we should challenge. In open source, the code, its associated wiki pages =
and perhaps auto-gen docs are the draft and implementation =
agreement/documentation in question.
>>=20
>> 	I would also challenge what has become the common new WG =
"formula" these days. That is the notion that requirements, problem =
statements or architectures are always needed and must come before the =
WG can work on any protocols/solutions. These are heavy burdens that =
have a price of slowing things down. If we want to pay that price, we'd =
better get something good in return. However, the road is littered with =
many examples of recent WGs getting nowhere after several years of work. =
These groups often end up in this state because frankly many of the =
people involved in those efforts are completely disconnected from the =
reality of building the things they are apparently designing. In many =
cases they never have built anything either, so much of the effort goes =
into explaining to them why things need to be a certain way/etc... =
Unfortunately their "veto" or influence in the process also dilutes the =
simplicity that an implementation would reveal (i.e.: useless options).  =
Its clearly the difference between theory and practice, which I think we =
all understand is a real thing.   The end result is that this impedance =
is one quantifiable reason why people have looked to over avenues such =
as open source, to build interoperable systems/tools/etc... quickly.
>>=20
>> 	The solution: join the IETF process to the open source =
communities *where it makes sense, but not otherwise*. Open source BTW =
is what we used to call a rough-concensus + running code around here!
>> If we stick to interfaces that need "on the wire" interoperability, =
we are in the sweet spot. If we wade into areas where there is little =
value added - such as requirements/problem statements/architectures, =
lets not waste our time.
>> For example, there are clearly cases where an RFC standard for =
something does not makes sense. Something like Open stack is a good =
example. The APIs are there, implemented in code you can see and =
documented. There is a well defined change process that identifies =
stable release points and also allows for quick iteration on that =
code/interfaces to evolve that works very quickly. Why would anyone =
every need an RFC for these things?  Now there really are cases where =
formal standardization makes sense. As I said if we stick to interfaces =
that need "on the wire" interop, we are squarely somewhere both open =
source and the IETF can add value. For example, there is a lot of code =
generation in open source based on yang models these days. Many of the =
experts around the model creation are at the IETF and not necessarily in =
those communities, so joining those folks to model creation can help =
that running code. In cases where vendors really want interop at the =
model level, then lets get together the vendors/operators that care, and =
not only build running code to test/prove those models make sense, but =
then run them through the IETF process in parallel.
> If a WG can't agree on which problem(s) it want to solve, then there =
is a problem, no?
> And not sure if Open Source is the solution, unless everybody says: =
"here is my view of the problem, let me provide some code for it"

	That is precisely how things work in open source; people huddle =
together to solve a problem and write code to solve it. There is not =
much "management" needed here, nor are there any hard requirements to =
write problem statements, architectures, frameworks, etc.. before that =
process of code construction can begin.  That is what I am getting at: =
we need to get back to writing more code around here. Code that is used =
to build some goal. That is ultimately what defines what can be done.  =
As we iterate though that process, we arrive at the goal.=20

> Note: I've been involved in a couple of WGs where defining a =
terminology was a time-consuming but well-worth effort, in order to =
produce the requirements/problem statement and architecture document. =
We're all engineers, and the fun part is to design protocols or write =
code.
> However, I agree that requirements/problem statement/architecture RFCs =
should be produced way faster within the IETF. And maybe, the IESG =
should be stricter regarding deadlines for problem statements: if the WG =
can't agree on the problem statement by date D, the WG is closed.

	Its important to understand what needs to be done but not =
necessarily how in too much detail ahead of time before real work =
begins; that is what is broken here in the process - we wait for =
literally years before we can do any real work. The IETF's process is =
analogous to waterfall software design and open source is more like =
agile development.  Anyone skilled in the art of modern software =
engineering knows the trade-offs between these two approaches, as well =
as what is used by modern software engineering done on a large scale.

	--Tom


>=20
>=20
> Regards, Benoit
>=20
>>=20
>> 	--Tom
>>=20
>>=20
>>=20
>>> [Alia] Diversity of implementation is important as is stability of a
>>> standard and it being understood how to change/upgrade for different
>>> versions.  These don't come automatically via open-source.
>>>=20
>>> Regards,
>>> Alia
>>>=20
>>>=20
>=20
>=20
>=20


--Apple-Mail=_8C2CFB12-FE1F-4E05-8AFD-9C677054C5F8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTUBDKAAoJEPcO+I7eiUJZ0bUP/R+Kc2p0ddToe7sSNVE8K20U
jWum5XxC8alZ5Z4qsUEdOwRfX6HFJuqxyn0J7EZIvKE+B0+UWkwPBbzWgx0T9DAJ
dO565bSk+L+sF7Vf9zOFlf8kIFb/RHHzXlN1u+71sPS+XRhqrEzbNKhI1uB0d2K0
enoYXIqhx5dpmvymJjpFfuxu6pM5j1l4tBL5VvZWNpKbM5XfzOtbqI5J7g/Uk4Oq
IWZHbBlswO/9YZQlHogHDEV5V5ykDDTpAMDkYlglmHe6/UeQnMumpNSKijdhnriK
2XKsu10dFCXrNaiUuiAlBzTIKoOIb2CCVVnPxGS8wqfx+cb04US3IfgOAFQ7celM
TQKhsi4CyxxqMl2VBvd5yHtXt5AJTDtZqFNsRAAeFlkU4q1GjSkcXkOA6Y64+8ek
AJ8vssUwCnfqn1N85iTAvgFyFLJZXCgtewpntc/fgFYnClv6NCxhY+3bsKvAtOaK
lO+OhWFCYyCBGQOTHRB+nY2ronwx77SYBKkb2vRUtpfyBwsR0clSy0aYxpEfWo/W
PMV+pFinhD5mQcympYOWBqoicJ01v//YV4ERQffJ+lrnpDe6skaQGHVA7f8Cq+j5
OMvrsuRDBs71obTja6spT/uMtjGIeykoNo7WG/EiNTZ/+C4uhKsNhPS+ww2Ae+Kv
lMmZremc9BHkaRh8RCYT
=YGYU
-----END PGP SIGNATURE-----

--Apple-Mail=_8C2CFB12-FE1F-4E05-8AFD-9C677054C5F8--


From nobody Thu Apr 17 10:42:39 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2728E1A017C; Thu, 17 Apr 2014 10:42:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 kTYpQGp48fjk; Thu, 17 Apr 2014 10:42:31 -0700 (PDT)
Received: from mail-ee0-x236.google.com (mail-ee0-x236.google.com [IPv6:2a00:1450:4013:c00::236]) by ietfa.amsl.com (Postfix) with ESMTP id 560D51A0169; Thu, 17 Apr 2014 10:42:31 -0700 (PDT)
Received: by mail-ee0-f54.google.com with SMTP id d49so928069eek.27 for <multiple recipients>; Thu, 17 Apr 2014 10:42:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1Ca6BxJo3tE1mncnJkM+vZt51+XtswwzjUKrFM3ZzR8=; b=zhKZc+busMIG9OibELkbLk5YiuXVhYUSCkorv76ndogDVhRHDtxBmW3vpVM7emZA/5 XFp90RI0wv09Z/2mx+lGx23tpJg9EK9BWthYId1OkZ4QLaYxy1K/AA2NeEabP0iKE8F5 l61ve2ZcR3BACwAoyav+1iajIAACCuhtgTK7sQBPCtKlzFNU7P4zhbMWgJSJxu0xApP6 YpUK/Uff3/Pp99brCIpaMZ3aI2jJm3dvqiGTctmsWqk/bYqYTNHiuaglWS99XA1nw0dQ sXb2ibXP8LgfYKATrmdqiGiekrjraKhm+MVoWOWlXmT2QgTO0jvVUN4Cqrn15Or1O1VC vFfg==
X-Received: by 10.14.241.139 with SMTP id g11mr15808458eer.49.1397756547023; Thu, 17 Apr 2014 10:42:27 -0700 (PDT)
Received: from [192.168.1.101] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id w1sm69218854eel.16.2014.04.17.10.42.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 10:42:26 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standard
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <14BE57EA00BC0C469E17B5AD698FE67766664CE4@FR711WXCHMBA01.zeu.alcatel-lucent.com>
Date: Thu, 17 Apr 2014 20:42:23 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <B12490A2-2D31-4E32-9D9E-ACB80C91FB8C@gmail.com>
References: <20140404202750.31367.2461.idtracker@ietfa.amsl.com> <14BE57EA00BC0C469E17B5AD698FE67766664CE4@FR711WXCHMBA01.zeu.alcatel-lucent.com>
To: "PUTMAN, Tony (Tony)" <tony.putman@alcatel-lucent.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PB4MM7vGRXoI0uIDJg9NGMmMjVg
Cc: "ipsec@ietf.org" <ipsec@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 17:42:36 -0000

Hi, Tony

Thanks for the review.

I assume you mean that you don=92t sign with public keys. Replacing =
=93sign=94 with =93validate=94 makes for a strange sentence, because the =
sentence is about sending (and presumably signing) rather than receiving =
(and validating).

How about:
=93If multiple certificate are sent, the first MUST contain the public =
key associated with the private key used to sign the AUTH payload=94

Yoav


On Apr 17, 2014, at 8:23 PM, PUTMAN, Tony (Tony) =
<tony.putman@alcatel-lucent.com> wrote:

> All,
>=20
> In section 3.6 (top of page 94), there is the statement,
>  "If multiple certificates
>   are sent, the first certificate MUST contain the public key used to
>   sign the AUTH payload."
>=20
> "sign" should be "validate".
>=20
> Regards,
> Tony
> --
> Tony Putman
> Alcatel-Lucent Technologies
>=20
> -----Original Message-----
> From: IPsec [mailto:ipsec-bounces@ietf.org] On Behalf Of The IESG
> Sent: Friday, April 04, 2014 9:28 PM
> To: IETF-Announce
> Cc: ipsec@ietf.org
> Subject: [IPsec] Last Call: =
<draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> (Internet Key Exchange =
Protocol Version 2 (IKEv2)) to Internet Standard
>=20
>=20
> The IESG has received a request from the IP Security Maintenance and
> Extensions WG (ipsecme) to consider the following document:
> - 'Internet Key Exchange Protocol Version 2 (IKEv2)'
>  <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> as Internet Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-04-18. Exceptionally, comments may =
be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>=20
> Abstract
>=20
>=20
>   This document describes version 2 of the Internet Key Exchange (IKE)
>   protocol.  IKE is a component of IPsec used for performing mutual
>   authentication and establishing and maintaining Security =
Associations
>   (SAs).  This document replaces and updates RFC 5996, and includes =
all
>   of the errata for it, and it is intended to update IKEv2 to be
>   Internet Standard.
>=20
>=20
>=20
>=20
> The file can be obtained via
> =
http://datatracker.ietf.org/doc/draft-kivinen-ipsecme-ikev2-rfc5996bis/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-kivinen-ipsecme-ikev2-rfc5996bis/bal=
lot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>=20
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec


From nobody Thu Apr 17 11:03:13 2014
Return-Path: <rpelletier@isoc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2CA51A0220; Thu, 17 Apr 2014 11:03:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.003
X-Spam-Level: 
X-Spam-Status: No, score=-100.003 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 JG46l5awX4XH; Thu, 17 Apr 2014 11:02:44 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0144.outbound.protection.outlook.com [207.46.163.144]) by ietfa.amsl.com (Postfix) with ESMTP id BBB831A0149; Thu, 17 Apr 2014 11:02:43 -0700 (PDT)
Received: from [192.168.0.3] (69.131.53.57) by BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20) with Microsoft SMTP Server (TLS) id 15.0.921.12; Thu, 17 Apr 2014 18:02:38 +0000
Subject: Re: [Recentattendees] ACTION: 2014 Meeting Venue Preference Survey
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Content-Type: text/plain; charset="us-ascii"
From: Ray Pelletier <rpelletier@isoc.org>
In-Reply-To: <64CD3EF7-611D-4822-97CA-BE8AAAB00027@isoc.org>
Date: Thu, 17 Apr 2014 14:02:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <99AC5C93-6AA7-44D0-B83F-DEDC6987CD8D@isoc.org>
References: <64CD3EF7-611D-4822-97CA-BE8AAAB00027@isoc.org>
To: <recentattendees@ietf.org>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [69.131.53.57]
X-ClientProxiedBy: BL2PR08CA0040.namprd08.prod.outlook.com (10.255.170.158) To BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20)
X-Forefront-PRVS: 01842C458A
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6009001)(6049001)(428001)(51704005)(377454003)(43784003)(199002)(189002)(53434003)(24454002)(87976001)(50986999)(83072002)(87286001)(50466002)(74502001)(43066001)(36756003)(86362001)(77982001)(53806999)(92726001)(80976001)(97756001)(88136002)(93916002)(83322001)(23726002)(46102001)(19580395003)(85852003)(19580405001)(79102001)(99396002)(42186004)(76482001)(66066001)(15975445006)(57306001)(19273905006)(81342001)(19300405004)(4396001)(80022001)(76176999)(50226001)(74662001)(33656001)(20776003)(83716003)(77156001)(89996001)(62966002)(47776003)(81542001)(46406003)(82746002)(562404015)(563064011); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB234; H:[192.168.0.3]; FPR:A6F2F1FF.FE209799.21ED2048.4FE2F17A.202C3; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received-SPF: None (: isoc.org does not designate permitted sender hosts)
X-OriginatorOrg: isoc.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5DV5fQgBBmmy2zx5278x5tL4aAY
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IETF Discussion <ietf@ietf.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 18:03:01 -0000

All;

Thank you for your participation in the survey.

We received 659 responses.

The top 5 venue preferences for each region are:

Asia-Pacific=09
Sydney		329
Hong Kong	326
Tokyo		322
Singapore	261
Auckland		250

Europe
Barcelona	351
Rome		261
Paris		249
Berlin		244
Prague		224

US & Canada=09
San Francisco	335
Vancouver	301
New York		270
Boston		266
Montreal		252

You can find all the results for the 15 venues per region here:  =
<https://www.ietf.org/meeting/>

Just a reminder about the survey:
The purpose of the 2014 Meeting Venue Preference Survey is to inform the =
IAOC during  its=20
IETF meeting venue selection process of the community's preferred future =
meeting venues.

While being guided by this information, the IAOC will select actual =
venues following its due diligence,=20
including site visits of specific hotel and conference facilities and =
other factors.   Other factors include=20
cost, travel burden, venue surroundings, access, safety, risks, etc.   =
The IAOC is currently (March 2014)=20
reviewing venues for 2017.=20

We are still missing T-Shirt pictures for the T-Shirt Picture Gallery: =20=

<https://www.ietf.org/meeting/gallery/gallery.py>

Submit your entries here:  =
<http://www.ietf.org/meeting/gallery/submit.py>

Thanks again for your guidance.

Ray
IAD


On Mar 27, 2014, at 8:07 PM, Ray Pelletier <rpelletier@isoc.org> wrote:

> All;
>=20
> The purpose of this anonymous, 7 question 2014 Meeting Venue =
Preference Survey is to inform the IAOC during  its IETF meeting venue =
selection process of the community's preferred future meeting venues.
>=20
> While being guided by this information, the IAOC will select actual =
venues following its due diligence, including site visits, of specific =
hotel and conference facilities and other factors.   Other factors =
include cost, travel burden, venue surroundings, access, safety, risks, =
etc.   The IAOC is currently reviewing venues for 2017.=20
>=20
> https://www.surveymonkey.com/s/YNRSNLD
>=20
> Thanks for your continuing guidance and support.
>=20
> Ray
> IETF Administrative Director
> _______________________________________________
> Recentattendees mailing list
> Recentattendees@ietf.org
> https://www.ietf.org/mailman/listinfo/recentattendees


From nobody Thu Apr 17 11:13:19 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BC5A1A0188 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 11:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 AtEssxALMc3T for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 11:13:15 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id BCFCF1A014B for <ietf@ietf.org>; Thu, 17 Apr 2014 11:13:15 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id A680BCC0BD for <ietf@ietf.org>; Thu, 17 Apr 2014 14:13:11 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id E8sBAuS44F1J for <ietf@ietf.org>; Thu, 17 Apr 2014 14:13:02 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 9285CCC099 for <ietf@ietf.org>; Thu, 17 Apr 2014 14:13:02 -0400 (EDT)
Message-ID: <535019AE.4080903@meetinghouse.net>
Date: Thu, 17 Apr 2014 14:13:02 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <CAHiKxWjiSHH9nn_CjC-n8Rp4jnwF4X5+Ct+tAad_q+JeG=Qfkw@mail.gmail.com> <CAG4d1rfFKB-8CRbj21ZOrGKps9ctz88m-4=yYYCVmYp3ks1ryg@mail.gmail.com> <27F3F43E-683F-440D-9761-DD56CD8FD096@lucidvision.com> <534FE599.5020001@cisco.com> <1936431F-C9FB-4620-8CF6-B66F590A833B@lucidvision.com>
In-Reply-To: <1936431F-C9FB-4620-8CF6-B66F590A833B@lucidvision.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PbgYfAe8pPf3qGk2kDuunGSwWto
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 18:13:16 -0000

Thomas Nadeau wrote:
> run them through the IETF process in parallel.
>> If a WG can't agree on which problem(s) it want to solve, then there is a problem, no?
>> And not sure if Open Source is the solution, unless everybody says: "here is my view of the problem, let me provide some code for it"
> 	That is precisely how things work in open source; people huddle together to solve a problem and write code to solve it. There is not much "management" needed here, nor are there any hard requirements to write problem statements, architectures, frameworks, etc.. before that process of code construction can begin.  That is what I am getting at: we need to get back to writing more code around here. Code that is used to build some goal. That is ultimately what defines what can be done.  As we iterate though that process, we arrive at the goal.
>

Well, wait a minute.  That might be how small projects work - but not 
big ones, with large impact - like say the Linux Kernel, or Debian, or 
Apache.  Those projects have policies, procedures, configuration control 
processes, authorized committers -- it's not like a change makes it into 
the Linux kernel without going through multiple levels of review.  Not 
to mention processes for bug reporting and patching.

And... I expect that, in the aftermath of Heartbleed, a number of open 
source projects are going to be taking another look at release processes.

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Thu Apr 17 11:18:25 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F3901A01B3 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 11:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 gAPznAiEG1tq for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 11:18:20 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 6BF421A018D for <ietf@ietf.org>; Thu, 17 Apr 2014 11:18:20 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s3HIIFFQ003939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Apr 2014 20:18:15 +0200 (MEST)
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <alpine.BSF.2.00.1404162346400.2194@joyce.lan>
To: John R Levine <johnl@taugh.com>
Date: Thu, 17 Apr 2014 20:18:15 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rUcQXlLnwy6A5deHmht7t_-yMF8
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 18:18:23 -0000

John R Levine wrote:
> > The originator (well, more to the point, the originator's mail server) 
> > doesn't need a signal that it's a mailing list; it's simply that the 
> > destination makes an "if I forward the mail, I'll be including this" piece of 
> > data available, and the originator's server can then include that in the 
> > signature of the message. I was thinking this could be in some special kind 
> > of DMARC (or whatever) record that lived in the mailing list's domain and 
> > could be queried by the originator's server.
> 
> We argued at great length about this issue when we were doing DKIM.  The 
> magic token has to be cryptographically tied to the contents of the 
> original message, or bad guys can take the token from a real message and 
> replace the body with spam.  So that means a token tied to a hash of the 
> contents of the message which is, of course, a DKIM signature.  This 
> scheme is equivalent to requiring that lists preserve DKIM signatures, 
> which they don't.
> 
> Every attempt to create a signing scheme that is flexible enough to deal 
> with all the routine stuff that lists do (e.g., reorder, discard, or 
> flatten MIME parts while adding the usual subject tags and body footers) 
> while being robust enough to prevent bad guys from replacing the message 
> with spam has completely failed.  We can try again, but I don't see any 
> reason to think that the result would be any different.


I fail to understand where the problem comes from.  The idea/architecture
of the rfc822 "sent on behalf of" (Sender:) seems clear.  If anything
should be authenticated at all, then it is what _the_sender_ decides
to send.

The sender might be asserting the authorship of the message (plus or
minus a few bits) to someone else by including the authors name in
a From: field that differs from the Sender: field.

A technology that is obsessed about the contents of the From:-Field
of an rfc822/2822/5322 Email message that ignores the semantics of
the Sender: field appears broken to me.  A sender that received
the original EMail with a signature might indicate so (and authenticate
this indication), but unless the original message is included verbatim
an opaque blob, the original signature may no longer work -- such as
when a mailing list software cleans/streamlines submissions, so the
original signature should be stripped.

MUAs which are not implementing the rfc822/2822/5322 "on behalf of"
semantics of a message that carries both From: and Sender: header
fields ought to be FIXED.  Standards that build on rfc822/2822/5322
and do not respect "on behalf of" semantics of messages with
both "Sender:" and "From:" also need to be FIXED.


-Martin


From nobody Thu Apr 17 11:28:40 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34B331A01C7 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 11:28:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.702
X-Spam-Level: 
X-Spam-Status: No, score=-98.702 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 5oxZZVwkUTmW for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 11:28:34 -0700 (PDT)
Received: from ntbbs.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 70D3D1A0149 for <ietf@ietf.org>; Thu, 17 Apr 2014 11:28:34 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5692; t=1397759305; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=n+RlgPWnHtCOdRleAAqbnTSOeX4=; b=ZNT6TT8R1XCxn7T6qqnL i+ka3qqdIwRNySA1EGI6hRYLxH5MdGXuY1CDJBxGTakgqNo08XH90bcmylEjmDFj EKFJh3K4warbfzKexA/pKScSG54h49KAKcrEz9ZCdCPP+vWtOUe0CtIANuCniHn5 2fWPbV7hRWIO2aRXPYC/v+Y=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 17 Apr 2014 14:28:25 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 867880159.3603.3900; Thu, 17 Apr 2014 14:28:24 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5692; t=1397759234; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=4HoxZne 9Q8UtCfMl+hmu8QJ3w/JKk8vtPOSqHImma6A=; b=o5atYLOR6HJey///5ZRmL8+ QAj93DFK9QCIdnLYYpxzdTy9WNnmw4VVaorZ8fH3vcM+UPmykAESfJ+ZUI/BhdU4 335CpK2uSbjP8sjdcOAhQOvlxsrq8Kr7LFfgJRvfu7SHH0tsEnU43tVzwimp8lFy +pQJCOmibveAUHD0jyoU=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Thu, 17 Apr 2014 14:27:14 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 887409890.9.8440; Thu, 17 Apr 2014 14:27:13 -0400
Message-ID: <53501D49.8050201@isdg.net>
Date: Thu, 17 Apr 2014 14:28:25 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com, Douglas Otis <doug.mtview@gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <833BDCD2-1157-4914-B385-C300AF33E2D4@gmail.com> <01P6QWP7AI2G00004W@mauve.mrochek.com>
In-Reply-To: <01P6QWP7AI2G00004W@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/z7VQyNy8oPYcw5ApfMNmu53YuEg
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 18:28:39 -0000

Ned,

I don't see this as a big technical problem.  The engineering has been 
done. For the most part, not to over simplify, this was a battle 
between two camps:

    DKIM + POLICY (1st party author domain) framework
    DKIM + TRUST (3rd party signer domain) framework

DKIM is a trust model. It was unfortunate, by design, the Policy 
Semantics were pulled.  The trust advocates "won the war" by finally 
making ADSP historic to make room for DMARC where the focus was mostly 
about Reporting.  Even with ADSP, we were collecting information but 
it lacked the reporting part, unlike early versions of the policy 
proposals. But DMARC reporting was richer.

But this DMARC did have a similar handling logic it learned from SSP, 
DSAP and ADSP. It was odd but I presume the IETF believed DMARC 
p=reject will not be used as much as they strongly believed the 
equivalent ADSP dkim=discardable policy would never be used or 
honored, and if so, in a small insignificant way.

YAHOO changed that mindset and reality. Did they ever! In my book, as 
I always knew this lost of policy focus would have to be corrected 
some day.  Yahoo has forced the issue. Policy wins.

To me, both TRUST and POLICY are needed.

POLICY is just a first level filter of the most obvious domain 
practice faults. After policy passes the test, the trust layer comes 
in. After all, for DKIM trust query to be activated, the signature 
must exist and be valid per specification.

But just with using trust, Yahoo could of used the signer domain as 
the DKIM specs wanted it to do in the first place to lookup some 
"trusted" whitelist or 3rd party service to see if the signer domain 
is a "good guy."  It could of also accepted and quarantined the 
message allowing the user to white list the signer domain.  Yahoo 
online mail UI can offer the user a "DKIM whitelist" input field. 
Yahoo can keep this to itself or it can create public ATPS records, if 
it makes sense.

DKIM also has the Agent or User Id (AUID), the i= tag in 
DKIM-signature, that can be used as some MLM signing method.  I think 
we need to explore this again.

But ultimately, the author domain policies should be honored as the 
first layer check before trust can even come into play.  That mindset 
needs to be accepted.

The hard part is going to be getting the same folks to change their 
tune about how the Author Domain fits in with DKIM specification.  The 
DKIM abstract says:

    DKIM separates the question of the identity of
    the Signer of the message from the purported author
    of the message.

Impossible. I always wanted to know which "question" that was. 
5322.From is the sole single technical requirement to be hash bound to 
the signature.  There will always be an authorization relationship.

-- 
HLS

On 4/17/2014 11:46 AM, ned+ietf@mauve.mrochek.com wrote:
>
>> On Apr 16, 2014, at 11:00 PM, ned+ietf@mauve.mrochek.com wrote:
>
>>>> On Sat, Apr 12, 2014 at 4:35 PM, <ned+ietf@mauve.mrochek.com> wrote:
>>>
>>>>> The underlying technical issue is that the two technologies DMARC is built
>>>>> on -
>>>>> DKIM and SPF - both attach additional/restrictive semantics to
>>>>> longstanding mail
>>>>> system fields. (Broadly speaking, From: for DKIM and MAIL FROM for SPF.)
>>>>>
>>>
>>>> Something's amiss here.  What new semantics does DKIM attach to From:?  As
>>>> far as I know, it only requires that the field be signed.  It doesn't
>>>> require that it be interpreted in a particular way or that it contain any
>>>> particular value.
>>>
>>> I was trying to be brief. Yes, I'm well aware that DKIM can be used in other
>>> ways. This entire discussion is within the context of DMARC here. Do you
>>> disagree that DMARC's use of DKIM and SPF assign additional semantics to header
>>> and envelope from fields respectively?
>
>> Murray is correct. DKIM does not create special From header field semantics.
>
> Actually, by requiring that the signature cover the From: field, it sort
> of does. But that's beside the point. Again, I was talking about DMARC's
> use of DKIM, not DKIM usage in general.
>
>> However, DMARC semantics are similar to those of ADSP while avoiding some
>> shortcomings.
>
> But both of them attach additional semantics to From:. (Not that they had
> a choice; as I pointed out previously, in order to acheieve the stated
> goal they have to attach the check to the identity users actually see.)
>
>> ...
>
>>>> Also: By "the IETF published a draft", are you talking about an RFC, or the
>>>> DMARC base draft?
>>>
>>> The draft, of course.
>>>
>>>> It seems extreme to lay blame on the IETF in general
>>>> merely for having an open mechanism by which to post a draft for all to see
>>>> and discuss.  A "Request For Comment", as it were.
>>>
>>> You may think it extreme. I don't. I think the IETF's politics have led to  it
>>> inching closer to moral hazard territory for a long time, and with this
>>> incident it has stepped in it.
>
>> This disruption should be shared with the provider that has already
>> enumerated 30,000 mailing-lists but made no effort to establish a means to
>> verify these sources and to safely assert specific exceptions to DMARC
>> alignment requirements. This ability is desperately needed before applying
>> DMARC reject on user accounts.  I'll be happy to modify either ATP or ATPS to
>> permit these exceptions without the need to alter mailing-list.
>
> I'm by no means sure that ATP or ATPS is the right answer, but I certainly
> agree that we need to at least try and address the situation that's been
> created.
>
> Sigh. We have a lot of work to do, don't we?
>
> 				Ned
>
>
>



From nobody Thu Apr 17 11:40:48 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E56FB1A02A9 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 11:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.895
X-Spam-Level: 
X-Spam-Status: No, score=0.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 oNuzpkN-WaAO for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 11:40:43 -0700 (PDT)
Received: from mauve.mrochek.com (unknown [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 329961A02A3 for <ietf@ietf.org>; Thu, 17 Apr 2014 11:40:43 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6R2EA2AA80059HT@mauve.mrochek.com> for ietf@ietf.org; Thu, 17 Apr 2014 11:35:35 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6O0FD8M9S00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 17 Apr 2014 11:35:30 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6R2E7L0T800004W@mauve.mrochek.com>
Date: Thu, 17 Apr 2014 11:33:56 -0700 (PDT)
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-reply-to: "Your message dated Thu, 17 Apr 2014 12:28:01 -0400" <53500111.5000205@meetinghouse.net>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com> <alpine.BSF.2.00.1404162346400.2194@joyce.lan> <534F5E67.1010307@qti.qualcomm.com> <alpine.BSF.2.00.1404170824350.2692@joyce.lan> <534FEA0A.4050607@qti.qualcomm.com> <01P6QXI47QVW00004W@mauve.mrochek.com> <53500111.5000205@meetinghouse.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/V7mlBqXIQlpJJ3VrrOQxyNdLelw
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 18:40:47 -0000

> ned+ietf@mauve.mrochek.com wrote:
> >> On 4/17/14 7:29 AM, John R Levine wrote:
> >> > Now I'm totally confused.  How does that help me as a sender
> >> > distinguish between a good mailing list that is resending real mail
> >> > from Yahoo and an evil mailing list that is sending phishes?
> >
> >> We're now *way* into technical discussion. Let's take those to
> >> https://www.ietf.org/mailman/listinfo/dmarc shall we?
> >
> > How about we take it some place else? I really don't want this
> > intermingled
> > with discussions of things like how to revise the current DMARC
> > specifications
> > that hopefully are taking place on that list.

> Any proposal as to where?

Not really. AFAIK there isn't an IETF list devoted to the discussion
of anything closely related to this topic. Of course we could use
an existing list like ietf-822 or even the appsarea list, but they
somehow don't seem quite appropriate.

				Ned


From nobody Thu Apr 17 12:20:56 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 608981A0193 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 12:20:53 -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, SPF_PASS=-0.001] autolearn=ham
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 EWcDIJoobpAk for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 12:20:45 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 1DF921A00FB for <ietf@ietf.org>; Thu, 17 Apr 2014 12:20:45 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id kl14so689912pab.32 for <ietf@ietf.org>; Thu, 17 Apr 2014 12:20:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=01Q9A9O8QxTZu9qBeXWUADUtRmX9JFVyP+EiVvzmcWo=; b=Jz5CqP6xSNiEuZ7fDA5ZdnEm2ZA+yKtQOe+FmXgFfMxN7T6ScXnJ56l/g5kSGciFyX oQDuIwXNEiboRxnV844GvVI5TH9X3aBMMQcJMPz/lttVV4gPyqdRERsZZw2B4zMSKPxy t/vlXLWXu4cX0lAYPt2o5ahkAyQPrpFWsGU2szP31Yg+c1sbZgtZdusa6kXfTwu7WuqU k2mRhKWq12jEuIG8mdK8eyucr37474fO8AOGxzfIjYFM2kiwXXkYSD9lWH7MjYa5rPPi 5P6TGWz2ZKRRtcHbo/hucqGXDkBHK1wa8rwSTlL/FS+z+1rG5xcnIYmNx6m55Vl2qBa9 gtbw==
X-Received: by 10.68.239.137 with SMTP id vs9mr17760345pbc.84.1397762441501; Thu, 17 Apr 2014 12:20:41 -0700 (PDT)
Received: from ?IPv6:2601:9:1b80:1046:d5d2:6efc:7b10:3c95? ([2601:9:1b80:1046:d5d2:6efc:7b10:3c95]) by mx.google.com with ESMTPSA id ci4sm55175922pbb.50.2014.04.17.12.20.39 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 12:20:40 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_EAAF6363-17B1-4204-8DB0-0CF29F74142A"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: (DMARC) We've been here before, was Why mailing lists
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp>
Date: Thu, 17 Apr 2014 12:20:40 -0700
Message-Id: <7E18CCC2-AB08-448A-A6B4-940413FF553D@gmail.com>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp>
To: mrex@sap.com
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_vK9NCplB9qHNakJK5mhrmenKbc
Cc: Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 19:20:53 -0000

--Apple-Mail=_EAAF6363-17B1-4204-8DB0-0CF29F74142A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Apr 17, 2014, at 11:18 AM, Martin Rex <mrex@sap.com> wrote:
>=20
> MUAs which are not implementing the rfc822/2822/5322 "on behalf of"
> semantics of a message that carries both From: and Sender: header
> fields ought to be FIXED.  Standards that build on rfc822/2822/5322
> and do not respect "on behalf of" semantics of messages with
> both "Sender:" and "From:" also need to be FIXED.

Dear Martin,

Merging Sender and =46rom header fields by MUAs offers no protection =
when actual sources of messages remain unknown.  ESPs would rather see =
various authorization schemes than actually offering a means to =
authenticate their domain responsible for introducing the message.  When =
there is phishing or spoofing detected, those introducing messages into =
the public mail stream must respond by removing access, but they would =
rather push the problem onto their recipients.

John Klensin has already indicated TLS has a problem at authenticating =
sending MTAs, the clients.  We now have =
http://tools.ietf.org/html/draft-ietf-dane-smtp-with-dane. The next step =
should be to permit DANE verification of the sending MTA and allow SMTP =
to become fully federated.

In the meantime, there is a way for =46rom header field domains to =
publish a list of third-party services employed by their users.  This =
can be done in the form of hash labels that can even be secured using =
DNSSEC.  This information could then be used to permit meaningful policy =
exceptions where each provider is expected to act responsibly.

The actions of a few ESPs should not result in such meaningless =
reaction.

Regards,
Douglas Otis












--Apple-Mail=_EAAF6363-17B1-4204-8DB0-0CF29F74142A
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;"><br>On Apr 17, 2014, at 11:18 =
AM, Martin Rex &lt;<a href=3D"mailto:mrex@sap.com">mrex@sap.com</a>&gt; =
wrote:<br><blockquote type=3D"cite"><br>MUAs which are not implementing =
the rfc822/2822/5322 "on behalf of"<br>semantics of a message that =
carries both From: and Sender: header<br>fields ought to be FIXED. =
&nbsp;Standards that build on rfc822/2822/5322<br>and do not respect "on =
behalf of" semantics of messages with<br>both "Sender:" and "From:" also =
need to be FIXED.<br></blockquote><div><br></div><div>Dear =
Martin,</div><div><br></div><div>Merging Sender and =46rom header fields =
by MUAs offers no protection when actual sources of messages remain =
unknown. &nbsp;ESPs would rather see various authorization schemes than =
actually offering a means to authenticate their domain responsible for =
introducing the message. &nbsp;When there is phishing or spoofing =
detected, those introducing messages into the public mail stream must =
respond by removing access, but they would rather push the problem onto =
their recipients.</div><div><br></div><div>John Klensin has already =
indicated TLS has a problem at authenticating sending MTAs, the clients. =
&nbsp;We now have&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-ietf-dane-smtp-with-dane">http://=
tools.ietf.org/html/draft-ietf-dane-smtp-with-dane</a>. The next step =
should be to permit DANE verification of the sending MTA and allow SMTP =
to become fully federated.</div><div><br></div><div>In the meantime, =
there is a way for =46rom header field domains to publish a list of =
third-party services employed by their users. &nbsp;This can be done in =
the form of hash labels that can even be secured using DNSSEC. =
&nbsp;This information could then be used to permit meaningful policy =
exceptions where each provider is expected to act =
responsibly.</div><div><br></div><div>The actions of a few ESPs should =
not result in such meaningless =
reaction.</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div><div><br></div><div><br></div><div><br></div><div=
><br></div><div><br></div><div><br></div><div><br></div><div><br></div><br=
><br></body></html>=

--Apple-Mail=_EAAF6363-17B1-4204-8DB0-0CF29F74142A--


From nobody Thu Apr 17 13:06:41 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C28A11A00E6 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:06:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 hkxMemRD7z_L for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:06:34 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 52EB01A00D1 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:06:34 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id rd3so728246pab.39 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:06:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=t9KDDLSRrOdHQYmg0sRQlUlcgIC+mXZ7z0/LojsHzB8=; b=cI3lAW2lHDpHfYTloU8xUCfIP0CpgNd9cFbCd3s5FJabn/W8t3FIAQ9iEx+GX/MV1Z HlInd8Oq5DrzhBuXy/iA4GCSWPYVwK0JwUrSVLoosOOWWwZNugrYsOHUiZb+4DkDOonr xOX/KuESg10ZLGr/sZaKBJk9TG/nMmomhoD6C/Ja35M3+J3D+Dv3JIjdCshWcM8v3Ir8 wZEu47012XYfixctPN+LEy8Mvoi10tbGmj+4UoQLVSd6eNg1ejYU2LUUViE3HDn9gVHt BfNsytNV+qsPPwBjQS5vn71cfFkLBtmpxEGycCIG3rJnCxVbkzUR3RUFchxj6tg72w6R QfKw==
X-Received: by 10.69.26.103 with SMTP id ix7mr17626579pbd.41.1397765190758; Thu, 17 Apr 2014 13:06:30 -0700 (PDT)
Received: from [192.168.178.20] (34.199.69.111.dynamic.snap.net.nz. [111.69.199.34]) by mx.google.com with ESMTPSA id bz4sm55373848pbb.12.2014.04.17.13.06.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 13:06:29 -0700 (PDT)
Message-ID: <5350344B.1000400@gmail.com>
Date: Fri, 18 Apr 2014 08:06:35 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Sabahattin Gucukoglu <listsebby@me.com>
Subject: Re: What I've been wondering about the DMARC problem
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <2478F2D1-2E08-45D7-86A2-36443959E272@me.com> <534EE9EA.9060403@gmail.com> <09B6AA22-9D1D-4EE4-AB27-2506A1E08EDA@me.com>
In-Reply-To: <09B6AA22-9D1D-4EE4-AB27-2506A1E08EDA@me.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rdyg8bbxpvNWvOBQoxgu6bf7_V8
Cc: Jim Fenton <fenton@bluepopcorn.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 20:06:39 -0000

On 17/04/2014 22:03, Sabahattin Gucukoglu wrote:
> On 16 Apr 2014, at 21:36, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> On 16/04/2014 18:58, Sabahattin Gucukoglu wrote:
>>> On 15 Apr 2014, at 21:38, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>> The mailman fix is worse than the disease. I think the .INVALID fix is
>>>> much better, because Reply-all will still work.
>>> Reply-all should still work with the Mailman fix; 
>> It doesn't work *properly*. Firstly, this message wouldn't be sent
>> to you with CC to the list, which is the correct semantic.
>> If you weren't a subscriber, you would never see it. Secondly,
> 
> Sorry, but I appear to be confused.
> 
> The Reply-To: field is adjusted to be the author's address, 

Oh, OK. Most UAs will probably do what you describe, but I think
there are exceptions. However, if I want to reply to the author
alone, it's now the simple Reply that will fail me, because it
will reply to the list. And in my mail folders, messages will
all appear to come from the list; if I want to find the message
that Sabahattin sent me two years ago, I can't, because my UA
doesn't allow for searching on the Reply-To field.

It's still got very poor semantics.

    Brian

> on a discussion list like this where replies go back to the authors.  Just in case we're talking across purposes somehow and to avoid all doubt, the fix we are talking about is described here:
> http://www.dmarc.org/supplemental/mailman-project-mlm-dmarc-reqs.html
> 
> Unless your MUA is doing something very unusual, and some do, then pressing "Reply all" should produce a message addressed to me, with a CC that contains the remainder of the recipient addresses.  The From: is completely irrelevant.
> 
> I'm just waiting to be told that I've missed the obvious. :)
> 
> Now, FWIW, a better way is as has been suggested here, namely to synthesise addresses for each subscriber.  That's how I'd do it: every mailing list post has its From: rewritten, like:
> ietf-resend+brian.e.carpenter=gmail.com@ietf.org
> 
> That address remails to you, first checking that a subscriber of the list is recognised.  In the process, it performs the same transformation on the From: field of the message, so as to pass SPF alignment.  It is hoped that your interlocutor happens to be on the list, also, or that you are still on the list when he is trying to contact you.
> 
>> the first line above would read:
>>
>> On 16/04/2014 18:58, IETF discussion list wrote:
>>
>> which is untrue.
> 
> It isn't necessary to change the personal name.  Some MUAs may very cleverly add one in the absence of one, or store it in an address book, though, incorrectly.  With the resend method above this issue is less problematic; furthermore the list software can add "(via listname)" to make the distinction less confusing.
> 
> No, none of these suggestions are perfect.  I'm not looking for a perfect solution though, I'm looking for one that works, for now.  Throwing people off my lists *is not* an option.
> 
> Cheers,
> Sabahattin
> 
> 


From nobody Thu Apr 17 13:23:10 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02A251A00FE for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:23:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 dJnrRKAUY-gb for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:23:04 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 585891A0162 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:23:04 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s3HKMx8U023752 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Apr 2014 22:22:59 +0200 (MEST)
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <7E18CCC2-AB08-448A-A6B4-940413FF553D@gmail.com>
To: Douglas Otis <doug.mtview@gmail.com>
Date: Thu, 17 Apr 2014 22:22:59 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140417202259.2AA1D1ACD1@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZfUVMuXi8XlmqXJQ2uS6wPjYunc
Cc: Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 20:23:09 -0000

Douglas Otis <doug.mtview@gmail.com> wrote:
> 
> Martin Rex <mrex@sap.com> wrote:
>> 
>> MUAs which are not implementing the rfc822/2822/5322 "on behalf of"
>> semantics of a message that carries both From: and Sender: header
>> fields ought to be FIXED.  Standards that build on rfc822/2822/5322
>> and do not respect "on behalf of" semantics of messages with
>> both "Sender:" and "From:" also need to be FIXED.
> 
> Merging Sender and From header fields by MUAs offers no protection
> when actual sources of messages remain unknown.

This is *NOT* about protection or authentication, this is purely about
rfc822/2822/5322 message semantics.  Something that has been well-defined
and constant for decades.

At the beginning of this Email there are two quotations with assertions
of authorship.  There really is no difference to the name in the From:
field of an EMail that is carried with a different Sender (and envelope
MAIL FROM:) through an SMTP transport system.

There is no difference in semantics between the assertions above
and the rfc822-header assertion in "From:", when an rfc822 message
is transferred through an SMTP MTA system in an "on behalf of" scenario
with a differing Envelope "MAIL FROM" & matching Sender: rfc822-header.


-Martin


From nobody Thu Apr 17 13:25:21 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 558BF1A00E6 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:25:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 Zy8h9Dtl7uXi for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:25:14 -0700 (PDT)
Received: from mail-ee0-x22f.google.com (mail-ee0-x22f.google.com [IPv6:2a00:1450:4013:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 7BA961A0054 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:25:14 -0700 (PDT)
Received: by mail-ee0-f47.google.com with SMTP id b15so1025855eek.20 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:25:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=OsSvoqW8LHa2AABj5kNTZQ2DALytEGeAlOZzuf+5OdM=; b=IsB4nA7QWt/JPjRSERx1qeUQ8io4QBTLre59xlov5zVkbHA4dWN1/9VrWWeEBG8iOX Abc1ThGnGZw9Uu2NH8/vo8iAhaAv+ggSmoZmYDriGkTAVECmpQxwXC32VYUJetiqj0EZ jJORdxfs/VXx6oow2LIWh+faP9YdcB4nSCKcomVdzHRzVYyj0AvTNJRVIP+/R4dih6xe KKT59Vluh9+mEhh/7l3ik3qsNQjfq8c7rC7FqzA3RHMfGGrKhuVSXXHj82AYMbhTWQ+E kRDPz18IUDlinV9QGh8p/xyi4l9TYb9IQe4FrLo7Wl4IYvwGg+XEJjwNpU5cwThLW1Zp LWqQ==
X-Received: by 10.15.82.132 with SMTP id a4mr16424191eez.47.1397766310377; Thu, 17 Apr 2014 13:25:10 -0700 (PDT)
Received: from [192.168.1.101] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id p8sm70310082eef.26.2014.04.17.13.25.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 13:25:09 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <CAKHUCzzzsTLmcnRkyCobkimg5z4bAiCfpnsTuZ+PBksTjRKsBg@mail.gmail.com>
Date: Thu, 17 Apr 2014 23:25:07 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <F80E4CA0-4DE4-4F1B-8FA2-CAE6906C00DD@gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <201404142144.s3ELipR8014504@hobgoblin.ariadne.com> <C16CB48C-9462-4514-B675-D750D4DC9357@piuha.net> <534DB785.7040609@gmail.com> <EF72D31A-8134-42DB-B750-D5C3831869EE@tzi.org> <534DC46C.60703@gmail.com> <8962F23C-1486-4F52-AD58-BE64CFBC3B4A@thomasclausen.org> <CAKHUCzzzsTLmcnRkyCobkimg5z4bAiCfpnsTuZ+PBksTjRKsBg@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0bzYYjZSKjjwWa-qGn02XgcXjds
Cc: Carsten Bormann <cabo@tzi.org>, "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 20:25:19 -0000

On Apr 17, 2014, at 5:26 PM, Dave Cridland <dave@cridland.net> wrote:

>=20
> Instead of Experimental, maybe a state before the standards-track =
proper, called "Proposed Standard", might work, beyond which you'd need =
two interoperable implementations to demonstrate utility and =
functionality.
>=20
> I appreciate it's a radical suggestion.

That=92s not radical. Radical would be getting to this =93proposed =
standard=94 of which you speak in a few months rather than a few years, =
and without achieving perfection or even Pete=92s definition of rough =
consensus.

Yoav



From nobody Thu Apr 17 13:34:41 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBA5B1A012D for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:34:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 ZIrWah6Udb-6 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:34:35 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD241A0045 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:34:34 -0700 (PDT)
Received: (qmail 70788 invoked from network); 17 Apr 2014 20:34:31 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:mime-version:subject:references:in-reply-to:content-type:content-transfer-encoding:user-agent; s=11483.53503ad7.k1404; i=johnl-iecc.com@submit.iecc.com; bh=DQPDvyzHtrQmKc60RI8vr5S/FwFJ2kUN/enzmMPZjNk=; b=oPXIxADnehtJh9LkqO0ZRAkpbELRNq2HrQnRxqwUZg0wSvFTshdXV4kMA94Mqtrbu2zibmRxecJx1WLFnbcEcoxqTQ0w/WAlCqKV1oS4Vd8403e9fSvV2tQElQaQrfJWM3FM9oiF6DEEnUPzjLJnfkV3Cc9DaEnts25/gYIIFv5VsB7OYtMZm1/QoFDkWQvq/EmN1CIYvBg84d5goy2pzFutLFcw+ykGB/Wkoh84Y7kqdjB7jnCmLpnHwDZ0VfNy
Received: from jlevine.local ([216.146.45.247]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 17 Apr 2014 20:34:30 -0000
Date: 17 Apr 2014 16:34:25 -0400
Message-ID: <53503AD1.3000505@iecc.com>
From: "John Levine" <johnl@iecc.com>
To: mrex@sap.com, "Douglas Otis" <doug.mtview@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <20140417202259.2AA1D1ACD1@ld9781.wdf.sap.corp>
In-Reply-To: <20140417202259.2AA1D1ACD1@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5QFMNa-g58g7fEy4g6eBV8if_IU
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 20:34:40 -0000

> This is *NOT* about protection or authentication, this is purely about
> rfc822/2822/5322 message semantics.  Something that has been well-defined
> and constant for decades.

I have considerable sympathy in theory for your viewpoint, but in 
practice, the Sender header was deprecated a long time ago.  Most MUAs 
ignore it, the few that don't display it in a way that just confuses people.

-- 
Regards,
John Levine, johnl@iecc.com, http://jl.ly
Please consider the environment before reading this e-mail.


From nobody Thu Apr 17 13:39:11 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A08E1A00FE for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:39:10 -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, SPF_PASS=-0.001] autolearn=ham
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 dn31oBThcJXn for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:39:06 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id E416E1A0045 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:39:05 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id p61so922771wes.11 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:39:01 -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:content-type; bh=0Pyyi8mKvI6QSrGsUeDtaAo32aDW/lWqVlIs+6WceGo=; b=H3c00ykW0EsHMDsk44MlOtD5Huhfjrh0oIs/fJRMFVio2gdxc2cAGO7WlCSYNzR6Z5 OCqzPcNo4gaND1o6wUliS89horlkOEpiDAwjLKz8awMD5IuyWFXKA2rLs8hlzSgxIFtF NgrW8b2IuS+6VfFNDc2Y2hhLXBkr1qgB/Koaaej1XVpSfFYivIlkd1a4U32+t/rI3OUF BxA7P8fan9nM6MjLcF79V1sJ3fnFZKbG4JCju1pcQKlXNHssuOb2EbDZIqGrCAWeCdW3 +dMuShnq9HbfORtx3aqHpWxBm4S2Rdza4s9gHENy/gbsgZTeKGxBzQWpK+GE0DAxa1ji QO1w==
MIME-Version: 1.0
X-Received: by 10.180.84.129 with SMTP id z1mr25257008wiy.8.1397767141844; Thu, 17 Apr 2014 13:39:01 -0700 (PDT)
Received: by 10.180.90.140 with HTTP; Thu, 17 Apr 2014 13:39:01 -0700 (PDT)
In-Reply-To: <534FEA0A.4050607@qti.qualcomm.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <534F1183.6060702@qti.qualcomm.com> <alpine.BSF.2.00.1404162346400.2194@joyce.lan> <534F5E67.1010307@qti.qualcomm.com> <alpine.BSF.2.00.1404170824350.2692@joyce.lan> <534FEA0A.4050607@qti.qualcomm.com>
Date: Thu, 17 Apr 2014 13:39:01 -0700
Message-ID: <CAL0qLwatX3hm-j+J-RmFp_VShZmZ2y1t0hf45qHhFv8S9opvdg@mail.gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Content-Type: multipart/alternative; boundary=f46d043bdec0f7ee1304f7430594
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9FlCORWecFwdiAtWdtZFKaLCBXw
Cc: John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 20:39:10 -0000

--f46d043bdec0f7ee1304f7430594
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 17, 2014 at 7:49 AM, Pete Resnick <presnick@qti.qualcomm.com>wrote:

> On 4/17/14 7:29 AM, John R Levine wrote:
>
>> Now I'm totally confused.  How does that help me as a sender distinguish
>> between a good mailing list that is resending real mail from Yahoo and an
>> evil mailing list that is sending phishes?
>>
>
> We're now *way* into technical discussion. Let's take those to
> https://www.ietf.org/mailman/listinfo/dmarc shall we?
>
>
>
Just sent you the formal request for a non-WG mailing list, so as Ned
suggests (and I agree) the discussion can be separate.

-MSK

--f46d043bdec0f7ee1304f7430594
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Apr 17, 2014 at 7:49 AM, Pete Resnick <span dir=3D=
"ltr">&lt;<a href=3D"mailto:presnick@qti.qualcomm.com" target=3D"_blank">pr=
esnick@qti.qualcomm.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"=
><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">On 4/17/14 7:29 AM, John R L=
evine wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Now I&#39;m totally confused. =C2=A0How does that help me as a sender disti=
nguish between a good mailing list that is resending real mail from Yahoo a=
nd an evil mailing list that is sending phishes?<br>
</blockquote>
<br></div>
We&#39;re now *way* into technical discussion. Let&#39;s take those to <a h=
ref=3D"https://www.ietf.org/mailman/listinfo/dmarc" target=3D"_blank">https=
://www.ietf.org/mailman/<u></u>listinfo/dmarc</a> shall we?<div class=3D"HO=
EnZb">
<div class=3D"h5"><br><br></div></div></blockquote><div><br></div><div>Just=
 sent you the formal request for a non-WG mailing list, so as Ned suggests =
(and I agree) the discussion can be separate.<br><br></div><div>-MSK <br>
</div></div><br></div></div>

--f46d043bdec0f7ee1304f7430594--


From nobody Thu Apr 17 13:47:42 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D53101A01BB for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:47:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 aA0wWIevHIdV for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:47:36 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 78E811A013A for <ietf@ietf.org>; Thu, 17 Apr 2014 13:47:36 -0700 (PDT)
Received: (qmail 73351 invoked from network); 17 Apr 2014 20:47:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:mime-version:subject:references:in-reply-to:content-type:content-transfer-encoding:user-agent; s=11e86.53503de4.k1404; i=johnl-iecc.com@submit.iecc.com; bh=O8yn262K3awSQCRoznEexAIgB71L0QyCPTnsuigtdR4=; b=S957m88NTwbOW/CTMPa8EYjlbQ/CQySWt+weE2lGl1E1y45T+nGKujumniZH4XEeGBR/jtIKpT/qN5ImAGCVc8x78gH2s2XNIXKg9snoFhpBZjNHpYn4Up0CFpSs+4WpiDsN/oidWPg40VYhsrzU4MEqDEr++pwumlkfpApFIRu5a5Q3uA9mFd5aXeWlzalo6E8zfQrfGvRXldF00mNXq9gyQdGY0u2R4SaG41LYwMb6NnoFzyo9I2mj1GfEDIE/
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:mime-version:subject:references:in-reply-to:content-type:content-transfer-encoding:user-agent; s=11e86.53503de4.k1404; olt=johnl-iecc.com@submit.iecc.com; bh=O8yn262K3awSQCRoznEexAIgB71L0QyCPTnsuigtdR4=; b=HDznjL+7dgoDgD8tI2T8m3/XHxTH75TZKXslMmY9s36L9aklHXh1H2khEbdEhmwzIBKOGXl6bMKl/j8sarXHzCyQGzM9V0MCDZgrqxuFeKMqPSI4EAi25Uhn7g9ktJC7cLKgTLAAQJktVUy2y/yggI3k8lQRcw2BK9YhKwjn6KjcVbVjc2OovJ0d8NF+5TGhXeiPwM6kzKpgxnrzH1Xox9QqAfJtiygu+9pehRBcDLCSD5PbfnQwcYISUDGkZ/Zk
Received: from jlevine.local ([216.146.45.247]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 17 Apr 2014 20:47:32 -0000
Date: 17 Apr 2014 16:47:26 -0400
Message-ID: <53503DDE.8090002@taugh.com>
From: "John Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, "Pete Resnick" <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com>	<20140414214949.32126.qmail@joyce.lan>	<CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com>	<alpine.BSF.2.00.1404142150430.32657@joyce.lan>	<CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com>	<alpine.BSF.2.00.1404151832460.38826@joyce.lan>	<CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com>	<CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com>	<CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com>	<alpine.BSF.2.00.1404161654430.2065@joyce.lan>	<534F1183.6060702@qti.qualcomm.com>	<alpine.BSF.2.00.1404162346400.2194@joyce.lan>	<534F5E67.1010307@qti.qualcomm.com>	<alpine.BSF.2.00.1404170824350.2692@joyce.lan>	<534FEA0A.4050607@qti.qualcomm.com> <CAL0qLwatX3hm-j+J-RmFp_VShZmZ2y1t0hf45qHhFv8S9opvdg@mail.gmail.com>
In-Reply-To: <CAL0qLwatX3hm-j+J-RmFp_VShZmZ2y1t0hf45qHhFv8S9opvdg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dRL6Jcg7SVrcq1OUavAJEZXowRU
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 20:47:41 -0000

How about ietf-smtp?  It already exists and isn't very busy.

> Just sent you the formal request for a non-WG mailing list, so as Ned
> suggests (and I agree) the discussion can be separate.
>
> -MSK
>


From nobody Thu Apr 17 13:53:43 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66C3E1A0192 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:53:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.274
X-Spam-Level: 
X-Spam-Status: No, score=-0.274 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 iWUORYI1YUBS for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:53:37 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 673741A0109 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:53:37 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WatJM-0002wG-Rb; Thu, 17 Apr 2014 20:53:32 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 39093580598; Thu, 17 Apr 2014 16:53:32 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397768012; bh=NBhUUztUX8k895F9skyxuSEdN2+pmWZcXL44mLFA2IA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=AT0rv0Aucrkc1ny/VDppe/c6qsqznwzesp46H4I9iUkSjjZ60Du4h1imD12EsXZE7 H5/YEGxuIypGbdGokBnU6ltk4o7INholHM65faNk6Nh8lLpnTLqyfEKDErrDTSJLLt CHE+z/zMDpdglMOv7llqoeAuUVpYRbSTznylRNmI=
Date: Thu, 17 Apr 2014 16:53:32 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: What I've been wondering about the DMARC problem
Message-ID: <20140417205332.GB4979@thunk.org>
References: <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <2478F2D1-2E08-45D7-86A2-36443959E272@me.com> <534EE9EA.9060403@gmail.com> <09B6AA22-9D1D-4EE4-AB27-2506A1E08EDA@me.com> <5350344B.1000400@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5350344B.1000400@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ir_jHttOZYZs-n9kWlAogKPu6Cw
Cc: Jim Fenton <fenton@bluepopcorn.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 20:53:42 -0000

On Fri, Apr 18, 2014 at 08:06:35AM +1200, Brian E Carpenter wrote:
> > 
> > The Reply-To: field is adjusted to be the author's address, 
> 
> Oh, OK. Most UAs will probably do what you describe, but I think
> there are exceptions. However, if I want to reply to the author
> alone, it's now the simple Reply that will fail me, because it
> will reply to the list. And in my mail folders, messages will
> all appear to come from the list; if I want to find the message
> that Sabahattin sent me two years ago, I can't, because my UA
> doesn't allow for searching on the Reply-To field.
> 
> It's still got very poor semantics.

It's all about semantics, isn't?

Suppose we made the mailing list software take the contents of the
>From field, and moved it to something like "X-Originally-From: ", and
changed the From field to be "ietf@ietf.org".  That would be what the
DMARC people would want, right?

Except then, a couple of years later, because users might actually
want to find the message that was written by "Brian Carpenter", or
"Sabahattin Gucukoglu", and not from "ietf@ietf.org", MUA's might
start using the Originally-From field in the summary field, and start
emphasizing the "Originally-From" from field in the UI.  At which
point, the spammer/scammer/whatever could start forging the the
"Originally-From" field, and then Lo!  There will be a DMARC II,
demanding that "Originally-From" field be aligned with the From field,
and we're right back to where we started.

It was the same argument about why a DKIM or DMARC couldn't just
verify the Sender field, and call it a day.  The problem is that the
>From field is what people pay attention to.

And this is true of whatever solution we want to better support
mailing lists.  Suppose the answer is to rewrite the from field to
something like this:


From: ietf-resend+brian.e.carpenter=gmail.com@ietf.org

Or this:

From: ietf@ietf.org (Originally from Brian E Carpenter: brian.e.carpenter@gmail.com)

It doesn't matter.  Eventually, the UA's will start emphasizing and
parsing out the original From field information, because that's what
people will want to be automatically added to their address book, and
not ietf@ietf.org, and that's what they will want to see in their
e-mail summary.  And then the DMARC folk will say, "Oh, Noes!
Spammers and scammers and bears, oh my!  They are using this loophole
to fool the naive user."  We must have DMARC II... and DMARC
III.... and DMARC IV.... and it will never end.

					- Ted


From nobody Thu Apr 17 13:55:28 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AB281A0194 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:55:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.552
X-Spam-Level: 
X-Spam-Status: No, score=-8.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 eUIlzhrED8-1 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 13:55:24 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 4BDA11A0109 for <ietf@ietf.org>; Thu, 17 Apr 2014 13:55:24 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s3HKsxPY028311 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 17 Apr 2014 22:54:59 +0200 (MEST)
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <53503AD1.3000505@iecc.com>
To: John Levine <johnl@iecc.com>
Date: Thu, 17 Apr 2014 22:54:59 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140417205459.785251ACD1@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/L6S8ljLve_0RNC5s7RqRGrq_NcU
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 20:55:26 -0000

John Levine wrote:
>> 
>> This is *NOT* about protection or authentication, this is purely about
>> rfc822/2822/5322 message semantics.  Something that has been well-defined
>> and constant for decades.
> 
> I have considerable sympathy in theory for your viewpoint, but in 
> practice, the Sender header was deprecated a long time ago.  Most MUAs 
> ignore it, the few that don't display it in a way that just confuses people.


According to _what_ standard do MUAs interpret the semantics of
EMail then?

AFAIK, the relevant standard that the IETF published for this
purpose is rfc5322, and in that specification, Sender: is alive
and kicking just the way it has been since rfc822.

  https://tools.ietf.org/html/rfc5322#section-3.6.2


                   If the originator of the message can be indicated
   by a single mailbox and the author and transmitter are identical, the
   "Sender:" field SHOULD NOT be used.  Otherwise, both fields SHOULD
   appear.


Now if you're wonding what that "SHOULD" in there means,
there is a reference to rfc2119 at the beginning of rfc5322,
(a pretty common reference in IETF specifications...)

  https://tools.ietf.org/html/rfc5322#section-1.2.1

   1.2.1.  Requirements Notation

   This document occasionally uses terms that appear in capital letters.
   When the terms "MUST", "SHOULD", "RECOMMENDED", "MUST NOT", "SHOULD
   NOT", and "MAY" appear capitalized, they are being used to indicate
   particular requirements of this specification.  A discussion of the
   meanings of these terms appears in [RFC2119].


which leads to

   https://tools.ietf.org/html/rfc2119#section-3

   3. SHOULD   This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.


MUAs that goof the semantics of the "Sender:" header field are either
not implementing EMail the way it has been specified by the IETF,
or they goofed the second part of the above explanation for SHOULD.



-Martin


From nobody Thu Apr 17 14:02:11 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2C61A0130 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 14:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 t1KZNxl49O04 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 14:02:03 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6F7851A0054 for <ietf@ietf.org>; Thu, 17 Apr 2014 14:02:03 -0700 (PDT)
Received: (qmail 75931 invoked from network); 17 Apr 2014 21:01:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:mime-version:subject:references:in-reply-to:content-type:content-transfer-encoding:user-agent; s=1289a.53504147.k1404; i=johnl-iecc.com@submit.iecc.com; bh=sZWwr0dVxzcHdVOWF7HnihKUEnsL66IgbUq0y+/LK10=; b=f/hZS1NrhMRGiaO+ZY3q4rgmPchJE/LAP1PurMQM4R1F330WI+xCiywSjmBZxH8YWG7S+snSZAvG2fHohOxLKx3Pcx1JpijSFNXqrJA+3xsRfrXwl7qt86H+DY9cPS4mViO/xGjI7CVQTC3hu6SEdEev/NDqekGTw8qp2L3VptgM4SGksmJD61dNky/m/iOq+F8S9pLDNkLEIbvNWvKm05Y20MOmsOsK0iLoPjvwM7eH1m1zgOkIzy1N4vKWRzyv
Received: from jlevine.local ([216.146.45.247]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 17 Apr 2014 21:01:59 -0000
Date: 17 Apr 2014 17:01:52 -0400
Message-ID: <53504140.2020506@iecc.com>
From: "John Levine" <johnl@iecc.com>
To: mrex@sap.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <20140417205459.785251ACD1@ld9781.wdf.sap.corp>
In-Reply-To: <20140417205459.785251ACD1@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yvbGsYws9hLMTSTxnc2CssvYbY4
Cc: Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 21:02:08 -0000

> MUAs that goof the semantics of the "Sender:" header field are either
> not implementing EMail the way it has been specified by the IETF,
> or they goofed the second part of the above explanation for SHOULD.

I wouldn't disagree.  If you can find an Internet where everyone 
correctly implements every RFC, I'd sure like to see it.  In the 
meantime, we're stuck with the one we have.

-- 
Regards,
John Levine, johnl@iecc.com, http://jl.ly
Please consider the environment before reading this e-mail.


From nobody Thu Apr 17 14:09:40 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1FA11A013A for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 14:09:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.281
X-Spam-Level: 
X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 Z0G7MFyAOJ-i for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 14:09:37 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 287D81A0133 for <ietf@ietf.org>; Thu, 17 Apr 2014 14:09:37 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id E9AC6CC0B9 for <ietf@ietf.org>; Thu, 17 Apr 2014 17:09:32 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id iXoab+ToQecC for <ietf@ietf.org>; Thu, 17 Apr 2014 17:09:24 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 2CC35CC0A5 for <ietf@ietf.org>; Thu, 17 Apr 2014 17:09:24 -0400 (EDT)
Message-ID: <53504303.3000507@meetinghouse.net>
Date: Thu, 17 Apr 2014 17:09:23 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF discussion list <ietf@ietf.org>
Subject: Re: What I've been wondering about the DMARC problem
References: <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <2478F2D1-2E08-45D7-86A2-36443959E272@me.com> <534EE9EA.9060403@gmail.com> <09B6AA22-9D1D-4EE4-AB27-2506A1E08EDA@me.com> <5350344B.1000400@gmail.com> <20140417205332.GB4979@thunk.org>
In-Reply-To: <20140417205332.GB4979@thunk.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PCWhnL9snIeVwqiNR9V7fcQEh_c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 21:09:39 -0000

Theodore Ts'o wrote:

> Suppose we made the mailing list software take the contents of the
> >From field, and moved it to something like "X-Originally-From: ", and
> changed the From field to be "ietf@ietf.org".  That would be what the
> DMARC people would want, right?
>
> Except then, a couple of years later, because users might actually
> want to find the message that was written by "Brian Carpenter", or
<snip>

Worse than that.  That would any authentication back to the original author.

Personally, on my incoming mail, I really don't care if a message passed 
through a mailing list or not - if it says it's From: <foo>, what I 
really care about is that it really is from <foo> and that it's the 
message that <foo> originally sent (modulo things like subject tags, and 
list headers/footers) -- if some random mail list wants to forward the 
mail to me, and it comes through intact - do I really care about the 
legitimacy of the list server (other than not wanting it to become a 
spam or attack vector)?

Not sure that's completely clear.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Thu Apr 17 14:18:43 2014
Return-Path: <nobo@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E519A1A0168; Thu, 17 Apr 2014 14:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.773
X-Spam-Level: 
X-Spam-Status: No, score=-114.773 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_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 w6XFA6VeeC2l; Thu, 17 Apr 2014 14:18:34 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id 135CD1A0054; Thu, 17 Apr 2014 14:18:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6800; q=dns/txt; s=iport; t=1397769510; x=1398979110; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=hLKYK5Tid4Oymx7mWHA3JWXrFKs8DPKGdfamuUTiTOw=; b=ONWRRAQZXfZt/cLeHmsVHE371nt7WfIarDx/E8judYe+J8CvEXPeaSaQ M/UEDFThlYNkKA+k2V0PcXFLBos4irsS/R4YWyhmQxZqkIN4SRKCtdTA+ c7ROZAx4hwCEYcvDX6gAYGLbe6lZlop1N0n6XDWi6i0lJu+NHON9uhUVg 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAGNEUFOtJA2K/2dsb2JhbABWA4JlITtXw2eBJxZ0giUBAQEDAXkMBAIBCBEDAQEBCx0HMhQJCAEBBAENBQgBh2sIAQzMHBeMb4FCIRACBQYLgxOBFASIdDaLVoUlkRaDMYIr
X-IronPort-AV: E=Sophos;i="4.97,881,1389744000"; d="scan'208";a="318644398"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-4.cisco.com with ESMTP; 17 Apr 2014 21:18:30 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s3HLITFG025344 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Apr 2014 21:18:29 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 16:18:29 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Black, David" <david.black@emc.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "Zafar Ali (zali)" <zali@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAAiJosQ
Date: Thu, 17 Apr 2014 21:18:28 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.212.138]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ICtj5Qc8_GVY_j-lxpygE53kGlY
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 21:18:41 -0000

Hi David,

Thank you for thorough review of this document.
Please see replies in-line.

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Wednesday, April 16, 2014 7:31 PM
> To: tnadeau@lucidvision.com; Zafar Ali (zali); Nobo Akiya (nobo); General
> Area Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on Gen-
> ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-bfd-mib-17
> Reviewer: David L. Black
> Review Date: April 16, 2014
> IETF LC End Date: April 28, 2014
>=20
> Summary: This draft is on the right track, but has open issues
> 		described in the review.
>=20
> This draft is a MIB module for the BFD protocol, which is an important lo=
w-
> level routing protocol.  The draft is reasonable for a MIB draft; one nee=
ds to
> go read the protocol documents to understand how the protocol works, and
> significant portions of the text are derived from the usual MIB "boilerpl=
ate"
> as one would expect.  The "Brief Description of MIB Objects" is indeed br=
ief,
> but reasonable.  The shepherd writeup indicates that there are multiple
> implementations.
>=20
> Major issues:
>=20
> This MIB contains many writable objects, so the authors should take note =
of
> the IESG statement on writable MIB modules:
>=20
> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
>=20
> I did not see this mentioned in the shepherd writeup.  If the OPS Area ha=
s
> not been consulted, I strongly suggest doing so during IETF Last Call, e.=
g.,
> starting with Benoit Claise (AD).

I remember seeing the statement from IESG, which I agree is a good directio=
n for new charter items. [This] BFD MIB, on the other hand, is almost 10 ye=
ars old, with several implementations already around. I highly suspect the =
WG will not want to see *change of direction* at this point. With that said=
, let me take this up with the AD and the Shepherd.

>=20
> Minor issues:
>=20
> The security considerations section includes considerations for
> unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
> but omits the corresponding considerations for bfdAdminStatus and
> bfdSessNotificationsEnable.  Both of the latter objects are global, so
> significant damage can be inflicted via these objects with a small number=
 of
> unauthorized modifications, so they need to be included in the first list=
 of
> sensitive objects.

Good point. I will add bfdAdminStatus and bfdOperStatus in the security con=
siderations section.

>=20
> I suggest that the authors recheck the entire MIB to ensure that every ob=
ject
> or table that should be included in the security considerations section i=
s
> appropriately included.

I've gone through them. There are set of objects which really should not be=
 modified once a session is functioning. I've added this in the security co=
nsiderations section.

   o  Some management objects define the BFD session whilst other
      management objects define the parameter of the BFD session.  It is
      particularly important to control the support for SET access to
      those management objects that define the BFD session, as changes
      to them can be disruptive.  Implementation SHOULD NOT allow
      changes to following management objects when bfdSessState is
      up(4):

      *  bfdSessVersionNumber
      *  bfdSessType
      *  bfdSessDestinationUdpPort
      *  bfdSessMultipointFlag
      *  bfdSessInterface
      *  bfdSessSrcAddrType
      *  bfdSessSrcAddr
      *  bfdSessDstAddrType
      *  bfdSessDstAddr

>=20
> Also, as a General Variable, would bfdSessNotificationsEnable be better
> named bfdNotificationsEnable, as it's not in the BFD Session Table?

That's true. Renamed as suggested.

>=20
> I did not see a compliance requirement for a system that only implements
> BFD protocol version 0.  That absence should at least be mentioned
> somewhere.  For example, if this reflects a considered and deliberate
> decision by the WG, that should be mentioned in the introduction.

Good point. If I remember correctly, BFD version 0 had a problem in the sta=
te machine that can cause the two ends to fall into a deadlock. It would be=
, therefore, very bad for anybody to have BFD version 0 deployed out there,=
 and asking for any MIB compliance requirement for such. Consensus on absen=
ce of compliance requirement for BFD version 0 was never polled in the WG, =
but I can say that there shouldn't be any desire for that.

I will add a short statement on lack of BFD version 0 compliance requiremen=
t in the introduction section, as you suggested.

>=20
> Nits/editorial comments:
>=20
> In the security considerations for authentication-related objects:
>=20
> OLD
>    In order for these sensitive information
>    from being improperly accessed, implementers MAY wish to disallow
>    access to these objects.
> NEW
>    In order to prevent this sensitive information
>    from being improperly accessed, implementers MAY disallow
>    access to these objects.

Thanks for the text. Updated in local copy.

>=20
> idnits 2.13.01 found a truly minor nit that should be corrected when the
> draft is next revised:
>=20
>   =3D=3D Outdated reference: A later version (-05) exists of
>      draft-ietf-bfd-tc-mib-04

Agree, non-issue.

>=20
> it also generated a warning that probably does not reflect an actual
> problem:
>=20
>   -- The document seems to lack a disclaimer for pre-RFC5378 work, but ma=
y
>      have content which was first submitted before 10 November 2008.  If =
you
>      have contacted all the original authors and they are all willing to =
grant
>      the BCP78 rights to the IETF Trust, then this is fine, and you can i=
gnore
>      this comment.  If not, you may need to add the pre-RFC5378 disclaime=
r.
>      (See the Legal Provisions document at
>      http://trustee.ietf.org/license-info for more information.)

Agree, non-issue.

Thanks again!

-Nobo

>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From nobody Thu Apr 17 14:31:55 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D0441A0167; Thu, 17 Apr 2014 14:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 YQaQqrcGVipN; Thu, 17 Apr 2014 14:31:49 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 26B9F1A0133; Thu, 17 Apr 2014 14:31:48 -0700 (PDT)
Received: from maildlpprd54.lss.emc.com (maildlpprd54.lss.emc.com [10.106.48.158]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3HLVfcP030891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2014 17:31:41 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3HLVfcP030891
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397770302; bh=g4RSLBFR0A8YAd4iJhfH78ibJFY=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=VSrAbX62azadSl/bgkEfACJ7xVeub5vI5M3Ugi92nd2h0sePVXA1gcelbhYer755Y kGc+z2mIUaO89oz5n3fqp6XiiX3FVyfT+efO8QP61R4dQMYSTccSSTLINc3pZHDJCE 2TSVbGebcEpHqbGjy7lr6NENVl/WPQ/WEKGzM75U=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3HLVfcP030891
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd54.lss.emc.com (RSA Interceptor); Thu, 17 Apr 2014 17:31:25 -0400
Received: from mxhub18.corp.emc.com (mxhub18.corp.emc.com [10.254.93.47]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3HLVPUI006105 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Apr 2014 17:31:25 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub18.corp.emc.com ([10.254.93.47]) with mapi; Thu, 17 Apr 2014 17:31:25 -0400
From: "Black, David" <david.black@emc.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "Zafar Ali (zali)" <zali@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Thu, 17 Apr 2014 17:31:23 -0400
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAAiJosQAAum6hA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C2EC413@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rNWfsW-CbXB5mgggKGYxgbzEb-Y
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 21:31:53 -0000

Hi Nobo,

> > This MIB contains many writable objects, so the authors should take not=
e of
> > the IESG statement on writable MIB modules:
> >
> > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> >
> > I did not see this mentioned in the shepherd writeup.  If the OPS Area =
has
> > not been consulted, I strongly suggest doing so during IETF Last Call, =
e.g.,
> > starting with Benoit Claise (AD).
>=20
> I remember seeing the statement from IESG, which I agree is a good direct=
ion
> for new charter items. [This] BFD MIB, on the other hand, is almost 10 ye=
ars
> old, with several implementations already around. I highly suspect the WG=
 will
> not want to see *change of direction* at this point. With that said, let =
me
> take this up with the AD and the Shepherd.

I have no problem with "running code" as a good reason to continue with
writable objects in this MIB; taking this topic up with your AD and Shepher=
d
should suffice.

> > I suggest that the authors recheck the entire MIB to ensure that every =
object
> > or table that should be included in the security considerations section=
 is
> > appropriately included.
>=20
> I've gone through them. There are set of objects which really should not =
be
> modified once a session is functioning. I've added this in the security
> considerations section.

Good - thank you for doing that.

Everything else is fine with me, and I appreciate the prompt response.

Thanks,
--David

> -----Original Message-----
> From: Nobo Akiya (nobo) [mailto:nobo@cisco.com]
> Sent: Thursday, April 17, 2014 5:18 PM
> To: Black, David; tnadeau@lucidvision.com; Zafar Ali (zali); General Area
> Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> Hi David,
>=20
> Thank you for thorough review of this document.
> Please see replies in-line.
>=20
> > -----Original Message-----
> > From: Black, David [mailto:david.black@emc.com]
> > Sent: Wednesday, April 16, 2014 7:31 PM
> > To: tnadeau@lucidvision.com; Zafar Ali (zali); Nobo Akiya (nobo); Gener=
al
> > Area Review Team (gen-art@ietf.org)
> > Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> > Subject: Gen-ART review of draft-ietf-bfd-mib-17
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on Ge=
n-
> > ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-bfd-mib-17
> > Reviewer: David L. Black
> > Review Date: April 16, 2014
> > IETF LC End Date: April 28, 2014
> >
> > Summary: This draft is on the right track, but has open issues
> > 		described in the review.
> >
> > This draft is a MIB module for the BFD protocol, which is an important =
low-
> > level routing protocol.  The draft is reasonable for a MIB draft; one n=
eeds
> to
> > go read the protocol documents to understand how the protocol works, an=
d
> > significant portions of the text are derived from the usual MIB
> "boilerplate"
> > as one would expect.  The "Brief Description of MIB Objects" is indeed
> brief,
> > but reasonable.  The shepherd writeup indicates that there are multiple
> > implementations.
> >
> > Major issues:
> >
> > This MIB contains many writable objects, so the authors should take not=
e of
> > the IESG statement on writable MIB modules:
> >
> > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> >
> > I did not see this mentioned in the shepherd writeup.  If the OPS Area =
has
> > not been consulted, I strongly suggest doing so during IETF Last Call, =
e.g.,
> > starting with Benoit Claise (AD).
>=20
> I remember seeing the statement from IESG, which I agree is a good direct=
ion
> for new charter items. [This] BFD MIB, on the other hand, is almost 10 ye=
ars
> old, with several implementations already around. I highly suspect the WG=
 will
> not want to see *change of direction* at this point. With that said, let =
me
> take this up with the AD and the Shepherd.
>=20
> >
> > Minor issues:
> >
> > The security considerations section includes considerations for
> > unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
> > but omits the corresponding considerations for bfdAdminStatus and
> > bfdSessNotificationsEnable.  Both of the latter objects are global, so
> > significant damage can be inflicted via these objects with a small numb=
er of
> > unauthorized modifications, so they need to be included in the first li=
st of
> > sensitive objects.
>=20
> Good point. I will add bfdAdminStatus and bfdOperStatus in the security
> considerations section.
>=20
> >
> > I suggest that the authors recheck the entire MIB to ensure that every
> object
> > or table that should be included in the security considerations section=
 is
> > appropriately included.
>=20
> I've gone through them. There are set of objects which really should not =
be
> modified once a session is functioning. I've added this in the security
> considerations section.
>=20
>    o  Some management objects define the BFD session whilst other
>       management objects define the parameter of the BFD session.  It is
>       particularly important to control the support for SET access to
>       those management objects that define the BFD session, as changes
>       to them can be disruptive.  Implementation SHOULD NOT allow
>       changes to following management objects when bfdSessState is
>       up(4):
>=20
>       *  bfdSessVersionNumber
>       *  bfdSessType
>       *  bfdSessDestinationUdpPort
>       *  bfdSessMultipointFlag
>       *  bfdSessInterface
>       *  bfdSessSrcAddrType
>       *  bfdSessSrcAddr
>       *  bfdSessDstAddrType
>       *  bfdSessDstAddr
>=20
> >
> > Also, as a General Variable, would bfdSessNotificationsEnable be better
> > named bfdNotificationsEnable, as it's not in the BFD Session Table?
>=20
> That's true. Renamed as suggested.
>=20
> >
> > I did not see a compliance requirement for a system that only implement=
s
> > BFD protocol version 0.  That absence should at least be mentioned
> > somewhere.  For example, if this reflects a considered and deliberate
> > decision by the WG, that should be mentioned in the introduction.
>=20
> Good point. If I remember correctly, BFD version 0 had a problem in the s=
tate
> machine that can cause the two ends to fall into a deadlock. It would be,
> therefore, very bad for anybody to have BFD version 0 deployed out there,=
 and
> asking for any MIB compliance requirement for such. Consensus on absence =
of
> compliance requirement for BFD version 0 was never polled in the WG, but =
I can
> say that there shouldn't be any desire for that.
>=20
> I will add a short statement on lack of BFD version 0 compliance requirem=
ent
> in the introduction section, as you suggested.
>=20
> >
> > Nits/editorial comments:
> >
> > In the security considerations for authentication-related objects:
> >
> > OLD
> >    In order for these sensitive information
> >    from being improperly accessed, implementers MAY wish to disallow
> >    access to these objects.
> > NEW
> >    In order to prevent this sensitive information
> >    from being improperly accessed, implementers MAY disallow
> >    access to these objects.
>=20
> Thanks for the text. Updated in local copy.
>=20
> >
> > idnits 2.13.01 found a truly minor nit that should be corrected when th=
e
> > draft is next revised:
> >
> >   =3D=3D Outdated reference: A later version (-05) exists of
> >      draft-ietf-bfd-tc-mib-04
>=20
> Agree, non-issue.
>=20
> >
> > it also generated a warning that probably does not reflect an actual
> > problem:
> >
> >   -- The document seems to lack a disclaimer for pre-RFC5378 work, but =
may
> >      have content which was first submitted before 10 November 2008.  I=
f you
> >      have contacted all the original authors and they are all willing t=
o
> grant
> >      the BCP78 rights to the IETF Trust, then this is fine, and you can
> ignore
> >      this comment.  If not, you may need to add the pre-RFC5378 disclai=
mer.
> >      (See the Legal Provisions document at
> >      http://trustee.ietf.org/license-info for more information.)
>=20
> Agree, non-issue.
>=20
> Thanks again!
>=20
> -Nobo
>=20
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer
> > EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------
>=20


From nobody Thu Apr 17 14:55:15 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 623391A0100 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 14:55:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 2G9aH8SpXoBf for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 14:55:07 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AAC4E1A0045 for <ietf@ietf.org>; Thu, 17 Apr 2014 14:55:07 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.145.222]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3HLsgc6004864 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2014 14:54:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397771695; bh=+4iTWoFJsV5SONg3aub3927choZHl+ghwP6cOWMS5GQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=W3X3LVim3uF7m69q9F5O34la70pxikEt/6CePVotHCo/t4CwrkkS9hfqjTRKcBvJ/ 7VX9Px5xTkmiAasSDEMYWSeDIrk9VOL+n8GHnc2VY8vRwmAsjxGsY6lgGwTr1ZmKmQ GC2JQX9lxSpfNt7T5yNjwi+7wzXL9t6npR9+4988=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397771695; i=@elandsys.com; bh=+4iTWoFJsV5SONg3aub3927choZHl+ghwP6cOWMS5GQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=m5tXqKGkybtqN6rUAen/5Qy5NWOWBb7LdIiDInp1oVcryxEzaQV7SpfmBrPsUW4jR r3K55Fxm3JbTLkmw6nYdL6aUiE0aXhmIe9P1tXb1XaKiq3l3Q1ru2D1Of9Le4ygY2m EUig60yc3mxakeWerhe1hioTRMqMygcrjUL7TMvk=
Message-Id: <6.2.5.6.2.20140417112406.0b7c9b70@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 17 Apr 2014 13:48:31 -0700
To: Benoit Claise <bclaise@cisco.com>, Andy Bierman <andy@yumaworks.com>, "George, Wes" <wesley.george@twcable.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: "why I quit writing internet standards"
In-Reply-To: <534FE1C3.3070103@cisco.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com> <534FE1C3.3070103@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nhx0-COX7TD7vQ6_-BZDjPySQKE
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 21:55:13 -0000

Hi Benoit,
At 07:14 17-04-2014, Benoit Claise wrote:
>We discussed during the milestones during one of the last plenaries.

Yes.

>The discussion was around: the milestones are indications and not deadlines.
>In Open Source project, these are deadlines.
>In the IETF, I would love to find a middle ground between the two.
>In the IETF, the only "deadlines" are the meetings, or to be more 
>precise, the submission deadlines just before the meetings.

Lisa used to send monthly progress reports.  It provided some 
visibility into what was happening within the area.

A milestone can be an estimate of when X can be completed.  I might 
suggest one and the group decides whether everyone can target that 
date and plan accordingly.  There are times when deadlines may be 
needed as an effort can end up in failure.

>Exactly, and we should understand why!
>I like this tool: 
><http://www.arkko.com/tools/lifecycle/>http://www.arkko.com/tools/lifecycle/<draft-name>-timing.html
>For example: 
><http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-interfaces-cfg-timing.html>http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-interfaces-cfg-timing.html
>Where is the bottleneck? Is this a process issue? The 
>authors/shepherd/IESG/RFC-editors?
>I don't want to finger point, but understand what we should improve.

Let's see. :-)  The shepherd write-up does not provide me with much 
information.  There's three years from the first -00 to the latest 
version of the draft.  The author activity looks okay.  There is less 
activity from the document shepherd (there is an explanation for 
that).  There was a Last Call in April 2013.  The AD asked for a 
revised I-D in May 2013.  There was another Last Call in December 
2013.  The IESG didn't like something in the draft and it took seven 
months to address that.

There's still the two and a half years.  There are seven months 
between the date in the charter and the first Last Call.  It would 
take some effort to figure out what happened during the first two 
years.  It looks like the working group was the bottleneck.

Regards,
S. Moonesamy  


From nobody Thu Apr 17 14:55:33 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86D601A01D6; Thu, 17 Apr 2014 14:55:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 cESKme936dPR; Thu, 17 Apr 2014 14:55:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 4B72C1A01CE; Thu, 17 Apr 2014 14:55:30 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3HLtKmr011886; Thu, 17 Apr 2014 22:55:20 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3HLtJQ1011877 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 17 Apr 2014 22:55:19 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Black, David'" <david.black@emc.com>, <tnadeau@lucidvision.com>, <zali@cisco.com>, <nobo@cisco.com>, "'General Area Review Team'" <gen-art@ietf.org>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
Date: Thu, 17 Apr 2014 22:55:18 +0100
Message-ID: <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHXstybkl3Rj5QCVQi0ErrtVmSSApsFo67A
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.0.0.1014-20640.002
X-TM-AS-Result: No--7.041-10.0-31-10
X-imss-scan-details: No--7.041-10.0-31-10
X-TMASE-MatchedRID: QfHZjzml1E+nykMun0J1wpmug812qIbzC/ExpXrHizxXopZjyO6CZaem Jq66qqv9A72lF8jbwSm+h2+kRiP1Xo4a2rhHAtuZoMfp2vHck9WHxi2fvkKUM8izgKND8Lm5VZ8 xQvqztISd5Vi9MggDmL1DgIPIkgsZSWKSZniod93ThGbP9qB93B9fNWA7SFWqWltirZ/iPP4Duw Qv5f82WF/nw1MAso95JvN5sPGL1gQqCxvBy34zX2gws6g0ewz2moKXVHfiMM8gcyGevtftJ6PFj JEFr+olqYB+kyCYtxRcLc3sLtjOt+TCMddcL/gjOwBXM346/+zID5XcD4FtapcOFu+rNPoeDEFa KkIPel+133QqrH6lMVsi4ALUpd8T
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/L_WNhrp0DXBkNdr6cyYKxYv98aY
Cc: rtg-bfd@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 21:55:32 -0000

Hi David,

Thanks for the review.

To pick out one of your points:

> This MIB contains many writable objects, so the authors should
> take note of the IESG statement on writable MIB modules:
> 
> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> 
> I did not see this mentioned in the shepherd writeup.  If the OPS Area
> has not been consulted, I strongly suggest doing so during IETF Last
> Call, e.g., starting with Benoit Claise (AD).

The OPS Directorate and the MIB Doctors will have been alerted to this document
by the last call and we can expect their comments.

But this question was discussed between the AD and the authors, and the AD was
unlikely to agree to sponsor the document if he felt it went against the IESG
statement. Our discussion resulted in some reduction of writeable objects.

I think there are several points to consider:
1. This document had already been completed and publication requested (i.e.
shepherd write-up written) at the time of the IESG statement. It would be
unreasonable to make the statement retrospective.
2. There are already various implementations in equipment (not just management
stations) of proprietary modules approximating to this document and these
support write-access.
3. This is a low-level component protocol of the sort that is used on dumber
devices and that is an area where write-access is more common.

Cheers,
Adrian



From nobody Thu Apr 17 15:06:51 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A974F1A01AD; Thu, 17 Apr 2014 15:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.273
X-Spam-Level: 
X-Spam-Status: No, score=-2.273 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 qlcU0EXzAanW; Thu, 17 Apr 2014 15:06:42 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 5A1BF1A01A5; Thu, 17 Apr 2014 15:06:41 -0700 (PDT)
Received: from maildlpprd01.lss.emc.com (maildlpprd01.lss.emc.com [10.253.24.33]) by mailuogwprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3HM6WCl028810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2014 18:06:33 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s3HM6WCl028810
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1397772394; bh=x5lPp3hwEyXiFe09SBaiImx5+CQ=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=DUr7XRUrSxNEVBasvsv0aoBRzweKYySNTspmpf2P6t97h4d+7kpT2fEAkcCjzMQK8 PJ8AsSk6sI5BsAZjUKZCkLDdt8jnKwFEZOwpNGxu2SFMVcURN4U6BpxTP3mg+mJHYl LdAG7S8UalWA7VJlISkl+eOQR5EaP0h/CmTS/5bI=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd04.lss.emc.com s3HM6WCl028810
Received: from mailusrhubprd54.lss.emc.com (mailusrhubprd54.lss.emc.com [10.106.48.19]) by maildlpprd01.lss.emc.com (RSA Interceptor); Thu, 17 Apr 2014 18:06:22 -0400
Received: from mxhub28.corp.emc.com (mxhub28.corp.emc.com [10.254.110.184]) by mailusrhubprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3HM6Lqn009455 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Apr 2014 18:06:21 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub28.corp.emc.com ([10.254.110.184]) with mapi; Thu, 17 Apr 2014 18:06:21 -0400
From: "Black, David" <david.black@emc.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "zali@cisco.com" <zali@cisco.com>, "nobo@cisco.com" <nobo@cisco.com>, "'General Area Review Team'" <gen-art@ietf.org>
Date: Thu, 17 Apr 2014 18:06:20 -0400
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: AQHXstybkl3Rj5QCVQi0ErrtVmSSApsFo67AgAAGUSA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C2EC421@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
In-Reply-To: <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd54.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Jbx3lbreEHZY1vSdyf5bnR-dDOo
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 22:06:45 -0000

Hi Adrian,

As clarified in my response to Nobo, I raised the concern about writable
MIB modules primarily as a process check (I was expecting to find something
on this topic in the shepherd writeup, and didn't).  In particular, this
concern was not intended as a strong reason not to publish, and I have no
disagreements with any of the points in your message below.

With you on top of this and the OPS folks sure to notice, I have no doubt
that this will get suitably addressed, although it might be simpler to
ensure that the OPS Area is ok now rather than waiting for IESG Evaluation.

Thanks,
--David (in part, wearing his OPS Directorate member "hat").

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Thursday, April 17, 2014 5:55 PM
> To: Black, David; tnadeau@lucidvision.com; zali@cisco.com; nobo@cisco.com=
;
> 'General Area Review Team'
> Cc: rtg-bfd@ietf.org; ietf@ietf.org
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> Hi David,
>=20
> Thanks for the review.
>=20
> To pick out one of your points:
>=20
> > This MIB contains many writable objects, so the authors should
> > take note of the IESG statement on writable MIB modules:
> >
> > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> >
> > I did not see this mentioned in the shepherd writeup.  If the OPS Area
> > has not been consulted, I strongly suggest doing so during IETF Last
> > Call, e.g., starting with Benoit Claise (AD).
>=20
> The OPS Directorate and the MIB Doctors will have been alerted to this
> document
> by the last call and we can expect their comments.
>=20
> But this question was discussed between the AD and the authors, and the A=
D was
> unlikely to agree to sponsor the document if he felt it went against the =
IESG
> statement. Our discussion resulted in some reduction of writeable objects=
.
>=20
> I think there are several points to consider:
> 1. This document had already been completed and publication requested (i.=
e.
> shepherd write-up written) at the time of the IESG statement. It would be
> unreasonable to make the statement retrospective.
> 2. There are already various implementations in equipment (not just manag=
ement
> stations) of proprietary modules approximating to this document and these
> support write-access.
> 3. This is a low-level component protocol of the sort that is used on dum=
ber
> devices and that is an area where write-access is more common.
>=20
> Cheers,
> Adrian
>=20
>=20


From nobody Thu Apr 17 15:11:47 2014
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45E821A0100; Thu, 17 Apr 2014 15:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 u9_pYKbvpYtm; Thu, 17 Apr 2014 15:11:22 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id D3D081A00FE; Thu, 17 Apr 2014 15:11:21 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id rr13so817177pbb.25 for <multiple recipients>; Thu, 17 Apr 2014 15:11:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LFXLyYpahXiiwnMu44Nc1E4R1kYqRN49rDIcE/QeGfo=; b=hEaJUEsbwsaPkVvXJvmykvB/SjKfpBJPXbck3oieXVwQndHu9UX3k/h3KV7TjJLNw0 yC9HyPHV/BlJ1J32NbDXcd8P4Mlv/essuIDn30UsHqGNa7Hi69ApxJECNkGfFX2QTowQ p3DTjEbzG2xlrzryaJ04J4lYqgBF5viHgYpztCIf9r0B+QooxMum2JuJjqN7Pu9SIjgR QAbRvEtB7+d9fnkVPlNIYPFT1EVh8sbmwjhb9mpl0vOaioZ2o/dj5KJWEO/l5g1vFRiR CZOuUBR3c0QtSh0oau/iwFrAisF6vbG96ABDHYfWdno2+bJSo3V3Kn7LlGyUGwevVIHn 9GLg==
X-Received: by 10.68.254.103 with SMTP id ah7mr18009827pbd.159.1397772678265;  Thu, 17 Apr 2014 15:11:18 -0700 (PDT)
Received: from [192.168.1.7] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id pl10sm55697899pbb.56.2014.04.17.15.11.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 15:11:17 -0700 (PDT)
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
In-Reply-To: <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
Date: Thu, 17 Apr 2014 15:11:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
To: adrian@olddog.co.uk
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/H9UNmPMX489GXS8lTfUw23nCJKU
Cc: ietf@ietf.org, "'Black, David'" <david.black@emc.com>, rtg-bfd@ietf.org, zali@cisco.com, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 22:11:33 -0000

Hi Adrian,

One comment inline.

On Apr 17, 2014, at 2:55 PM, Adrian Farrel wrote:

> Hi David,
>=20
> Thanks for the review.
>=20
> To pick out one of your points:
>=20
>> This MIB contains many writable objects, so the authors should
>> take note of the IESG statement on writable MIB modules:
>>=20
>> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
>>=20
>> I did not see this mentioned in the shepherd writeup.  If the OPS =
Area
>> has not been consulted, I strongly suggest doing so during IETF Last
>> Call, e.g., starting with Benoit Claise (AD).
>=20
> The OPS Directorate and the MIB Doctors will have been alerted to this =
document
> by the last call and we can expect their comments.
>=20
> But this question was discussed between the AD and the authors, and =
the AD was
> unlikely to agree to sponsor the document if he felt it went against =
the IESG
> statement. Our discussion resulted in some reduction of writeable =
objects.
>=20
> I think there are several points to consider:
> 1. This document had already been completed and publication requested =
(i.e.
> shepherd write-up written) at the time of the IESG statement. It would =
be
> unreasonable to make the statement retrospective.
> 2. There are already various implementations in equipment (not just =
management
> stations) of proprietary modules approximating to this document and =
these
> support write-access.

%sam - If this MIB allows write access, do you/WG anticipate, any =
extension to the MIB should also provide write-access as well? For =
example: http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ =
augments this base MIB to support MPLS. It adds more confusion than =
solving the issue as base MIB supports write-access, but augmented/ MIB =
extension doesn't.=20

As the BFD MIB authors were not supportive of write-access objects in =
the MIBs, why to have them in the first place?=20

cheers
-sam
> 3. This is a low-level component protocol of the sort that is used on =
dumber
> devices and that is an area where write-access is more common.
>=20
> Cheers,
> Adrian
>=20
>=20


From nobody Thu Apr 17 15:15:19 2014
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0945D1A0100; Thu, 17 Apr 2014 15:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 C1saCmvMvMKx; Thu, 17 Apr 2014 15:15:14 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id CF17F1A011D; Thu, 17 Apr 2014 15:15:14 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 37915C2A3; Thu, 17 Apr 2014 18:15:11 -0400 (EDT)
Date: Thu, 17 Apr 2014 18:15:11 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Message-ID: <20140417221511.GC29430@pfrc>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-kBlc1d8sC1eP-2uIbsFcRqx36E
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 22:15:16 -0000

On Thu, Apr 17, 2014 at 09:18:28PM +0000, Nobo Akiya (nobo) wrote:
> > I did not see a compliance requirement for a system that only implements
> > BFD protocol version 0.  That absence should at least be mentioned
> > somewhere.  For example, if this reflects a considered and deliberate
> > decision by the WG, that should be mentioned in the introduction.
> 
> Good point. If I remember correctly, BFD version 0 had a problem in the state machine that can cause the two ends to fall into a deadlock. It would be, therefore, very bad for anybody to have BFD version 0 deployed out there, and asking for any MIB compliance requirement for such. Consensus on absence of compliance requirement for BFD version 0 was never polled in the WG, but I can say that there shouldn't be any desire for that.

With respect to v0 vs. v1 from a MIB perspective, the only user-visible
detail was the additional state in the state machine.  That means that the
MIB in its current form should be able to accommodate bfd v0.

This does suggest, however, that the TC mib could use a comment in the
DESCRIPTION toward the point that failing(5) is only valid for BFD v0.

A conformance clause indicating that those so foolish as to deploy BFD v0
would better be served by the determinism of a five-year-old child flipping
a coin is probably out of scope for the draft.  But if someone has
sufficiently proscriptive text to add to say "don't do bfd v0" that is
acceptable to the reviewers, I'm fine with that.

-- Jeff


From nobody Thu Apr 17 15:16:44 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B39001A0134 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 15:16:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level: 
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 TUCiKYYDezPU for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 15:16:39 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 0DA881A0130 for <ietf@ietf.org>; Thu, 17 Apr 2014 15:16:39 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 3ED6520029; Thu, 17 Apr 2014 18:16:59 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id E525063ABD; Thu, 17 Apr 2014 18:16:32 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id CEB3B63ABA; Thu, 17 Apr 2014 18:16:32 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: mrex@sap.com
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 17 Apr 2014 18:16:32 -0400
Message-ID: <9451.1397772992@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EGhFVTiN5Lto-Zic4teAMhCQrsc
Cc: Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 22:16:44 -0000

--=-=-=


Martin Rex <mrex@sap.com> wrote:
    >> Every attempt to create a signing scheme that is flexible enough to deal
    >> with all the routine stuff that lists do (e.g., reorder, discard, or
    >> flatten MIME parts while adding the usual subject tags and body footers)
    >> while being robust enough to prevent bad guys from replacing the message
    >> with spam has completely failed.  We can try again, but I don't see any
    >> reason to think that the result would be any different.


    > I fail to understand where the problem comes from.  The idea/architecture
    > of the rfc822 "sent on behalf of" (Sender:) seems clear.  If anything
    > should be authenticated at all, then it is what _the_sender_ decides
    > to send.

    > The sender might be asserting the authorship of the message (plus or
    > minus a few bits) to someone else by including the authors name in
    > a From: field that differs from the Sender: field.

So, the bug is that Yahoo/DMARC/ are authenticating the From:, when it should
really be authenticating the Sender:. DMARC should key it's policy from
Sender: rather than From, and if it did that then:
  1) we could leave the From: intact, which is what's good for the end
     users.
  2) the list would change the Sender:, which is what we would establish
     the reputation of the list, not the From:
  3) MUAs would compare the From: and Sender:, and if they differed,
     could say useful things like:

     "From: Mrex@sap.com via ietf@ietf.org".

(I was also wondering this morning on my commute if a layer of message/rfc822
added by the mailing list might be a useful interim hack)

    > A technology that is obsessed about the contents of the From:-Field
    > of an rfc822/2822/5322 Email message that ignores the semantics of
    > the Sender: field appears broken to me.  A sender that received
    > the original EMail with a signature might indicate so (and authenticate
    > this indication), but unless the original message is included verbatim
    > an opaque blob, the original signature may no longer work -- such as
    > when a mailing list software cleans/streamlines submissions, so the
    > original signature should be stripped.

    > MUAs which are not implementing the rfc822/2822/5322 "on behalf of"
    > semantics of a message that carries both From: and Sender: header
    > fields ought to be FIXED.  Standards that build on rfc822/2822/5322
    > and do not respect "on behalf of" semantics of messages with
    > both "Sender:" and "From:" also need to be FIXED.

Is "on behalf of" part of the specification...  not literally using those
words, which is a shame, because I think that it's really good wording.
section 3.3.6 says:

   The resent originator fields indicate the mailbox of the person(s) or
   system(s) that resent the message.  As with the regular originator
   fields, there are two forms: a simple "Resent-From:" form, which
   contains the mailbox of the individual doing the resending, and the
   more complex form, when one individual (identified in the "Resent-
   Sender:" field) resends a message on behalf of one or more others
   (identified in the "Resent-From:" field).

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        | network architect  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [



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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU1BSwIqHRg3pndX9AQJvkAQAkVgb54wskNkzap0AtsAYz716sNzbJLXE
Js0+2jwfxTcMTE+5/wBZMtHK+Erb3FkhhXF27aVw8dcbiwZDD4RlqXO0SSrwZzXd
HEjhv0zBxM6POeDVgwdtFEYe8FwP+ttgoyAwP/XDNEyLLF2hhsUjjg4w9xbpsIIn
+YgHURWZ1Ns=
=6xjo
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Apr 17 15:18:02 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60C811A0100 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 15:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level: 
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 vKyiH5LItbe9 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 15:17:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.252.184]) by ietfa.amsl.com (Postfix) with ESMTP id 245231A00D1 for <ietf@ietf.org>; Thu, 17 Apr 2014 15:17:56 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id C5D8B20029; Thu, 17 Apr 2014 18:18:17 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 67F0363ABD; Thu, 17 Apr 2014 18:17:52 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 4F71D63ABA; Thu, 17 Apr 2014 18:17:52 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "John R Levine" <johnl@taugh.com>
Subject: Re: (DMARC) How a whitelist would work, was Why mailing lists
In-Reply-To: <alpine.BSF.2.00.1404170008470.2194@joyce.lan>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com> <alpine.BSF.2.00.1404170008470.2194@joyce.lan>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 17 Apr 2014 18:17:52 -0400
Message-ID: <9760.1397773072@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QDooEE3K8hU4Mn65akDrqEp_DaQ
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 22:18:00 -0000

--=-=-=


John R Levine <johnl@taugh.com> wrote:
    >> Do you envision each operator maintaining its own whitelist, or one or more
    >> public registries of them, or something else?

    > On the assumption that we have reasonably good agreement about what would
    > qualify for DMARC whitelisting, I'd think you'd want a small set (maybe only
    > one) of public whitelists.

    > If each receiver has to do its own whitelist, that means that nobody bug a
    > big gorilla who can afford to create a whitelist can apply DMARC policies.

I don't understand whitelists.

Are you saying that gmail and yahoo have to know about my lists.sandelman.ca
before I can have gmail/yahoo members on my little local list?

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU1BTEIqHRg3pndX9AQKXXAQA6fIGQksJb/I6ooajXM4qgee8PlgM/466
AFEhFiDaXRCjE7vX2xQTYoDol7LxG21XchOvMYPWBQf5M6u8um7UUojJUw4i+/o/
BEAwxUEtgZeKZB4RZl4k1YZBPDz1Kwwq54g51NhDSP7tW/s84EUFGsv0J/D/Lfq3
5as0Hd2za3Y=
=YXTk
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Apr 17 15:18:59 2014
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4F6F1A00D1; Thu, 17 Apr 2014 15:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.84
X-Spam-Level: 
X-Spam-Status: No, score=-1.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 uxxf6ice03wp; Thu, 17 Apr 2014 15:18:54 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 6449C1A0173; Thu, 17 Apr 2014 15:18:54 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id CB696C2A3; Thu, 17 Apr 2014 18:18:50 -0400 (EDT)
Date: Thu, 17 Apr 2014 18:18:50 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Message-ID: <20140417221850.GD29430@pfrc>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yQwleR4O8uDJQm7DR-Zp4sesKWY
Cc: ietf@ietf.org, "'Black, David'" <david.black@emc.com>, adrian@olddog.co.uk, rtg-bfd@ietf.org, zali@cisco.com, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 22:18:55 -0000

Sam,

On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
> %sam - If this MIB allows write access, do you/WG anticipate, any extension to the MIB should also provide write-access as well? For example: http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments this base MIB to support MPLS. It adds more confusion than solving the issue as base MIB supports write-access, but augmented/ MIB extension doesn't. 
> 
> As the BFD MIB authors were not supportive of write-access objects in the MIBs, why to have them in the first place? 

As noted in earlier mailing list chatter, there is some support for write
access in existing implementations.  Given the lack of significant detail
when pressed for the name of such an implementation, I'm suspecting smaller
vendor or internal implementation.  That's still sufficient to leave write
available.

Given that one of the original contexts of asking if we could remove write
was whether IETF was being asked to provide such a thing for MPLS-TP with
related impact on your extension MIB and the answer was "no", that shouldn't
be the main criteria.  

My suspicion is that if we were to ship the base MIB with writeable objects,
we may be forced to consider similar things for the extension MIB(s).

-- Jeff


From nobody Thu Apr 17 15:20:56 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A78311A0194 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 15:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.163
X-Spam-Level: 
X-Spam-Status: No, score=-2.163 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 fkjFtfn90kUq for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 15:20:49 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 49FF31A0135 for <ietf@ietf.org>; Thu, 17 Apr 2014 15:20:49 -0700 (PDT)
Received: from sandelman.ca (desk.marajade.sandelman.ca [209.87.252.247]) by tuna.sandelman.ca (Postfix) with ESMTP id D916920029; Thu, 17 Apr 2014 18:21:10 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 64E4863ABD; Thu, 17 Apr 2014 18:20:45 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 4F79D63ABA; Thu, 17 Apr 2014 18:20:45 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Dave Cridland <dave@cridland.net>
Subject: Re: (DMARC) Why mailing lists are only sort of special
In-Reply-To: <CAKHUCzwZ29TAAjJ3_w+0aaoN-L2o+CGHYaMQ=TOEqYdVn5rQHg@mail.gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAKHUCzwZ29TAAjJ3_w+0aaoN-L2o+CGHYaMQ=TOEqYdVn5rQHg@mail.gmail.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Thu, 17 Apr 2014 18:20:45 -0400
Message-ID: <10364.1397773245@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/U-D4m1gtFDe7_cw3zznep2Evzac
Cc: John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 22:20:53 -0000

--=-=-=


Dave Cridland <dave@cridland.net> wrote:
    > Right now, my MUA treats this as a message "From John R Levine <johnl@taugh.com
    >> ". This means that any policy on the message origination comes from looking
    > solely at the taugh.com domain. We'll pretend it has a DMARC policy. Herein
    > lies the Yahoo/DMARC issue, because unless your policy essentially stipulates
    > that the IETF is allowed to spoof you, we're stuck.

If, when sending to ietf@ietf.org, taugh.com knew that it was a mailing list,
then it could include, in the message, a signed delegation saying that it was
okay for *this message* for ietf.org to impersonate him.

This is a simple application of cryptographic methods.  Keynote and SPKI
(and I think SASL) define ways to do this.

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU1BTvYqHRg3pndX9AQLj+AQAhdqJqReGQ23tm794aomb6IAY2wardxc1
mYHL030/CW3Q41pvBxrKTqSWdONUDhtSk9VME277lCDYEeKMNLgO4QaWmjRdKzXj
nUVtpE+bVDiNFTtV4QM2JiLOY0mVwMhTH8spxGhsNjbP3NBzmC/5yZq3Ps8PFsU8
QnLoO3Eb2sg=
=b4PW
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Apr 17 15:40:28 2014
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE9291A0188; Thu, 17 Apr 2014 15:40:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 eR_prD7fdVy2; Thu, 17 Apr 2014 15:40:23 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 521771A0176; Thu, 17 Apr 2014 15:40:23 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id p10so819849pdj.31 for <multiple recipients>; Thu, 17 Apr 2014 15:40:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gvbubcSt5auUHsa6TpP/bsQ7HxWk9Ll6lcrsfEFtZM4=; b=Wa90Z3SjJ5EUcQ0Zhw5maeny+KUACTiXLvadWHgr64xSZRd+xJMfswJPBdOk8qse/U las9lpQ1UcnZkWWahW9X/DQJONUwOO8kVFws5P1dyk88AiOhHRE+J7dKuya8m01gags3 pam2RY55WXalW+8GyKNmRYVJN/sM3dsOhhgYGmQ5V2A8aRffe8PRXmmjseKjvkIju3of M06loibhYLTEsmdbx11A+d8dWQB8+w9YRGw3srC6bgMiqrCUS9qdpoTfQcvOZvEDV0ZY kbFfkLE1LjwFYx6zZ3hvXL6x2NBZ3WzvzOy70NYpDMuzDzasVvC/CexWuqqYKnH4YdZJ S7qA==
X-Received: by 10.66.253.33 with SMTP id zx1mr18534581pac.28.1397774419692; Thu, 17 Apr 2014 15:40:19 -0700 (PDT)
Received: from [192.168.1.7] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id q10sm55812565pbl.29.2014.04.17.15.40.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 15:40:17 -0700 (PDT)
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
In-Reply-To: <20140417221850.GD29430@pfrc>
Date: Thu, 17 Apr 2014 15:40:15 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc>
To: Jeffrey Haas <jhaas@pfrc.org>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bwOrtU8ovlZvZRxDI-N_ct3d-0E
Cc: ietf@ietf.org, "'Black, David'" <david.black@emc.com>, adrian@olddog.co.uk, rtg-bfd@ietf.org, zali@cisco.com, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 22:40:25 -0000

Hi Jeff,

Comments inline.

On Apr 17, 2014, at 3:18 PM, Jeffrey Haas wrote:

> Sam,
>=20
> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>> %sam - If this MIB allows write access, do you/WG anticipate, any =
extension to the MIB should also provide write-access as well? For =
example: http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ =
augments this base MIB to support MPLS. It adds more confusion than =
solving the issue as base MIB supports write-access, but augmented/ MIB =
extension doesn't.=20
>>=20
>> As the BFD MIB authors were not supportive of write-access objects in =
the MIBs, why to have them in the first place?=20
>=20
> As noted in earlier mailing list chatter, there is some support for =
write
> access in existing implementations.  Given the lack of significant =
detail
> when pressed for the name of such an implementation, I'm suspecting =
smaller
> vendor or internal implementation.  That's still sufficient to leave =
write
> available.
>=20
> Given that one of the original contexts of asking if we could remove =
write
> was whether IETF was being asked to provide such a thing for MPLS-TP =
with
> related impact on your extension MIB and the answer was "no", that =
shouldn't
> be the main criteria. =20
No. The context of my question is not related to MPLS-TP as such, but =
write-access support in general.=20
I should have added 'clarification' in my earlier email.
>=20
> My suspicion is that if we were to ship the base MIB with writeable =
objects,
> we may be forced to consider similar things for the extension MIB(s).
Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE =
and BFD-MIB respectively,  with write-access. Had to do write-access =
because of the reason you've mentioned above, which is base MIB. It =
would be painful to publish/support write-access MIB's when there is no =
clear interest. Hence my clarification question.=20

-sam

>=20
> -- Jeff


From nobody Thu Apr 17 17:10:40 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63A1A1A00E6 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 17:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 2IpXs5vCjDTa for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 17:10:33 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id AAE981A0049 for <ietf@ietf.org>; Thu, 17 Apr 2014 17:10:32 -0700 (PDT)
Received: (qmail 8717 invoked from network); 18 Apr 2014 00:10:27 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=220c.53506d73.k1404; bh=zS23qKAQs1UDsNVkk49D8wqO7WPU2CU9GlOqPQOQ93I=; b=HWG+Z9R+MrxxUIxZm8czB06YpL/hZmqx0WrnOoniQBAvj8nhsvtysfPB/LlQhi4hHX5tRH+BVZL8ALZx7m0HxdZU8HQCtZk9swZz1oqi4xC1NuEHkLHJdQfvDlx2zXXLhaovpEVOOVQde2tZO3Ouk511rV8AMGRdhPRbKiFsHmz9Gh4qEfcLjMkfH8Ty8+VFh9og5Q3RID/DbXL0MoQxm1ri3BMpXCcvLUihKK0CWjSHss5KWjfpyMqi/HsjpPeV
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=220c.53506d73.k1404; bh=zS23qKAQs1UDsNVkk49D8wqO7WPU2CU9GlOqPQOQ93I=; b=mJLY0sX4QAC7ij3LbB6hF7tXqGYGKzISi3KE0L4F1JiKCP9EgFXM8WQ90l8OSqGG54domV9Jamk22VaQqi3VKY/1lPK4Ci4r+gvuZPg6Lh71rYSeReDidTpBNDxR7RCarxtKcRCjnVQudAMRJ3x3pJMGZpKINUdPnFxbpbx130YxzzvxDP7Kd9P9PTslrDn4YbY1EDjKJB+hDzMMw9p2EGqzo90TGSn7ARSSnneNm0uxzXxHOcfnC9P90v8rjAoP
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 18 Apr 2014 00:10:27 -0000
Date: 17 Apr 2014 20:10:29 -0400
Message-ID: <alpine.BSF.2.00.1404172008250.2116@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Michael Richardson" <mcr+ietf@sandelman.ca>
Subject: Re: (DMARC) How a whitelist would work, was Why mailing lists
In-Reply-To: <9760.1397773072@sandelman.ca>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com> <alpine.BSF.2.00.1404170008470.2194@joyce.lan> <9760.1397773072@sandelman.ca>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tvbeqNncqmOg0N1ifaQrsENY3TA
Cc: "ietf\\@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 00:10:37 -0000

> Are you saying that gmail and yahoo have to know about my lists.sandelman.ca
> before I can have gmail/yahoo members on my little local list?

Yeah.  It's clear from the DMARC summary reports I'm getting that the big 
mail systems already have a pretty good idea of where the mailing lists 
are, so it should be possible to pre-seed a whitelist so most people 
won't have to explicitly apply unless something screws up.

I agree this idea is not great, but all the plausible alternatives seem 
even less great.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Thu Apr 17 18:05:05 2014
Return-Path: <nobo@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 313A91A01E6; Thu, 17 Apr 2014 18:04:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.773
X-Spam-Level: 
X-Spam-Status: No, score=-114.773 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_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 ZeXP7-RUyS0X; Thu, 17 Apr 2014 18:04:53 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 64AF41A0134; Thu, 17 Apr 2014 18:04:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2616; q=dns/txt; s=iport; t=1397783090; x=1398992690; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=9hS/2W9x/fYLzWcVQQBs8PLMW9/qgJipIGCwZA11CS4=; b=Gbbr6rbJEMvUI99IFDb0d2WuHYwwTQbxY+49cHnHU5ALla0fTaM4xOOd IswlHGRFWT8aX/am45/2A/xJkK39KedYO0AJulmagwTWSb9YLwlllCz2Q ILtINXXtQiczeUHqMXU26uJIccTUOsiEWNLILzTO6KHX8v/xjXLpPFQrg E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAJd5UFOtJV2Z/2dsb2JhbABZgmUhO1fDaIEjFnSCJQEBAQMBOjQLEAIBCBgKFBAyJQEBBAENDQELh2AIAQzMFBeOABACAR4xAgWDJIEUBJolkRaDMYIr
X-IronPort-AV: E=Sophos;i="4.97,882,1389744000"; d="scan'208";a="318620035"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by rcdn-iport-5.cisco.com with ESMTP; 18 Apr 2014 01:04:49 +0000
Received: from xhc-rcd-x06.cisco.com (xhc-rcd-x06.cisco.com [173.37.183.80]) by rcdn-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s3I14nIr011776 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Apr 2014 01:04:49 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x06.cisco.com ([173.37.183.80]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 20:04:48 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>, Jeffrey Haas <jhaas@pfrc.org>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAA5br4AAACOm4AAAEPMAAAAv3uAAAaLVxA=
Date: Fri, 18 Apr 2014 01:04:47 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com>
In-Reply-To: <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.242.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/k0luW5FcPC46YSyIZ0zb-prwfr4
Cc: "ietf@ietf.org" <ietf@ietf.org>, "'Black, David'" <david.black@emc.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 01:04:58 -0000

Hi Sam,

> > On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
> >> %sam - If this MIB allows write access, do you/WG anticipate, any
> extension to the MIB should also provide write-access as well? For exampl=
e:
> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments this
> base MIB to support MPLS. It adds more confusion than solving the issue a=
s
> base MIB supports write-access, but augmented/ MIB extension doesn't.
> >>
> >> As the BFD MIB authors were not supportive of write-access objects in
> the MIBs, why to have them in the first place?
> >
> > As noted in earlier mailing list chatter, there is some support for
> > write access in existing implementations.  Given the lack of
> > significant detail when pressed for the name of such an
> > implementation, I'm suspecting smaller vendor or internal
> > implementation.  That's still sufficient to leave write available.
> >
> > Given that one of the original contexts of asking if we could remove
> > write was whether IETF was being asked to provide such a thing for
> > MPLS-TP with related impact on your extension MIB and the answer was
> > "no", that shouldn't be the main criteria.
> No. The context of my question is not related to MPLS-TP as such, but wri=
te-
> access support in general.
> I should have added 'clarification' in my earlier email.
> >
> > My suspicion is that if we were to ship the base MIB with writeable
> > objects, we may be forced to consider similar things for the extension
> MIB(s).
> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE and
> BFD-MIB respectively,  with write-access. Had to do write-access because =
of
> the reason you've mentioned above, which is base MIB. It would be painful
> to publish/support write-access MIB's when there is no clear interest. He=
nce
> my clarification question.

This mentions three vendors wanting to implement MIB as writable.

http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html

And one more vendor voicing for writable.

http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html

I agree that defining & wording writable MIB is much more painful than all =
read-only MIB. But above thread indicates the desire by multiple vendors to=
 implement writable BFD MIB. Therefore it does seem that there are interest=
s, and going forward with write-access will benefit the community. And with=
 *ReadOnlyCompliance defined, BFD MIB can also accommodate those implementi=
ng them as just read-only.

-Nobo

>=20
> -sam
>=20
> >
> > -- Jeff


From nobody Thu Apr 17 18:11:45 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FA041A021A for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 18:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.281
X-Spam-Level: 
X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 AVVc5BvUH26o for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 18:11:41 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id E69421A0218 for <ietf@ietf.org>; Thu, 17 Apr 2014 18:11:40 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id D4B35CC0A8 for <ietf@ietf.org>; Thu, 17 Apr 2014 21:11:36 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id zONPcB3hTXse for <ietf@ietf.org>; Thu, 17 Apr 2014 21:11:31 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 69FC2CC0A5 for <ietf@ietf.org>; Thu, 17 Apr 2014 21:11:31 -0400 (EDT)
Message-ID: <53507BC3.6060308@meetinghouse.net>
Date: Thu, 17 Apr 2014 21:11:31 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf\\@ietf.org" <ietf@ietf.org>
Subject: Re: (DMARC) How a whitelist would work, was Why mailing lists
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com> <alpine.BSF.2.00.1404170008470.2194@joyce.lan> <9760.1397773072@sandelman.ca> <alpine.BSF.2.00.1404172008250.2116@joyce.lan>
In-Reply-To: <alpine.BSF.2.00.1404172008250.2116@joyce.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TMkHzyNK22_heUB8XfHpNQeRE_g
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 01:11:43 -0000

John R Levine wrote:
>> Are you saying that gmail and yahoo have to know about my 
>> lists.sandelman.ca
>> before I can have gmail/yahoo members on my little local list?
>
> Yeah.  It's clear from the DMARC summary reports I'm getting that the 
> big mail systems already have a pretty good idea of where the mailing 
> lists are, so it should be possible to pre-seed a whitelist so most 
> people won't have to explicitly apply unless something screws up.
>
The big buys already have whitelists - and an awful lot of our mailing 
lists are already on them.  (Every 6 months or so, some large site 
blocks our IP, I go to their postmaster site, fill in the form, and 
every is copacetic again).  The folks who are honoring DMARC p=reject 
are clearly ignoring whitelists that THEY ALREADY HAVE!

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Thu Apr 17 18:24:32 2014
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B6CD1A018F; Thu, 17 Apr 2014 18:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 NdC8r-4JTAZc; Thu, 17 Apr 2014 18:24:28 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7B96F1A0057; Thu, 17 Apr 2014 18:24:28 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id kq14so958280pab.38 for <multiple recipients>; Thu, 17 Apr 2014 18:24:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=35aHL2qacWZN28WEqFB9sF9D1eRAX7ZaqHAhqbfSSZ8=; b=LmBGZd1Ai2g4tjRlc47UHbYKa5zPK4ykWzA+m/68o1aeQEBgmxPhejTD1FxPy451b+ nuFWtJUtwVbRE959WgzC0wghGxfi4cqFSTUVD839yocc31w1S6Ejkmwadz0pxmmMBzw/ b/xrwLyS7B2M9/7JWFk9i5jN/HbC6F6Qdsf5XKFlcW3XwZC4ewHtckiRuXjpztrvYJkq LEmJyG0YxHVh4pvEFEG3gwtgey9cg74VmNoaoffPoe4QCiQS46MeiX0wxNjYtWDr9Jqg P0vCk0QQB6uI8BTDEvH9tAV1aBROO3m6yVZAI+u/5Xa6KbgGX6I1TTOsdv0kriYqYSJU YIFw==
X-Received: by 10.68.139.71 with SMTP id qw7mr19092420pbb.68.1397784264847; Thu, 17 Apr 2014 18:24:24 -0700 (PDT)
Received: from [192.168.1.7] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id pv4sm56277102pbb.55.2014.04.17.18.24.23 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 18:24:24 -0700 (PDT)
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com>
Date: Thu, 17 Apr 2014 18:24:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JKSK87LcXDww7v-1T17khxmFLyk
Cc: "ietf@ietf.org" <ietf@ietf.org>, "'Black, David'" <david.black@emc.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 01:24:30 -0000

Hi Nobo,
[sorry for the top post]

Yes, this is an old MIB and was in existence for a long time.=20
My only concern is with the new extension MIB's. If the base MIB (this =
MIB) has write access, future extension MIB's may be forced to support =
write-access. And that is the painful part, where community at large has =
not shown interest in developing write-access MIB's at IETF, lest =
implementation.=20

I want to re-iterate again, I am not objecting or proposing an =
alternative option. Just wanted to get clarification, so that, we don't =
have to burn cycles and do the exercise again, when we have to review =
these new extension MIB's.

-sam

On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:

> Hi Sam,
>=20
>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>> %sam - If this MIB allows write access, do you/WG anticipate, any
>> extension to the MIB should also provide write-access as well? For =
example:
>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments =
this
>> base MIB to support MPLS. It adds more confusion than solving the =
issue as
>> base MIB supports write-access, but augmented/ MIB extension doesn't.
>>>>=20
>>>> As the BFD MIB authors were not supportive of write-access objects =
in
>> the MIBs, why to have them in the first place?
>>>=20
>>> As noted in earlier mailing list chatter, there is some support for
>>> write access in existing implementations.  Given the lack of
>>> significant detail when pressed for the name of such an
>>> implementation, I'm suspecting smaller vendor or internal
>>> implementation.  That's still sufficient to leave write available.
>>>=20
>>> Given that one of the original contexts of asking if we could remove
>>> write was whether IETF was being asked to provide such a thing for
>>> MPLS-TP with related impact on your extension MIB and the answer was
>>> "no", that shouldn't be the main criteria.
>> No. The context of my question is not related to MPLS-TP as such, but =
write-
>> access support in general.
>> I should have added 'clarification' in my earlier email.
>>>=20
>>> My suspicion is that if we were to ship the base MIB with writeable
>>> objects, we may be forced to consider similar things for the =
extension
>> MIB(s).
>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE =
and
>> BFD-MIB respectively,  with write-access. Had to do write-access =
because of
>> the reason you've mentioned above, which is base MIB. It would be =
painful
>> to publish/support write-access MIB's when there is no clear =
interest. Hence
>> my clarification question.
>=20
> This mentions three vendors wanting to implement MIB as writable.
>=20
> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>=20
> And one more vendor voicing for writable.
>=20
> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>=20
> I agree that defining & wording writable MIB is much more painful than =
all read-only MIB. But above thread indicates the desire by multiple =
vendors to implement writable BFD MIB. Therefore it does seem that there =
are interests, and going forward with write-access will benefit the =
community. And with *ReadOnlyCompliance defined, BFD MIB can also =
accommodate those implementing them as just read-only.
>=20
> -Nobo
>=20
>>=20
>> -sam
>>=20
>>>=20
>>> -- Jeff
>=20


From nobody Thu Apr 17 18:30:09 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7234E1A0079 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 18:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 8qAgfSxXesSK for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 18:30:02 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id B0D6B1A0057 for <ietf@ietf.org>; Thu, 17 Apr 2014 18:30:01 -0700 (PDT)
Received: (qmail 20953 invoked from network); 18 Apr 2014 01:29:57 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 18 Apr 2014 01:29:57 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=aa9.53508015.k1404; i=johnl@user.iecc.com; bh=h+tupGPWa5/+gO2TJ1j9l3Pm3TOwZkiUpUqGos4KLjw=; b=TDyjLEX5fVBFgIStYH7e/K0Z+xL5h3t4AJ0wYcqvScRRWe5U6ii2C1tZs36SJRsTeK/ZtlNj5jX/eICctmScC/ZmauzBnHgQtxK5NwWjfK8LfTI4yFG0oCIBcAnS1CAxeMOHcb9mx665+kfliCGCGV6hOl7ujDcvPCx++jKQlv/m9GBCy48Cte65j7oSaccti/ay/ylYGBNqFV1xpV4s6QsOp9oPO7fufoICuFyqZWVWeXK0AJDTVrLpAUQFWLrW
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=aa9.53508015.k1404; olt=johnl@user.iecc.com; bh=h+tupGPWa5/+gO2TJ1j9l3Pm3TOwZkiUpUqGos4KLjw=; b=Fs2iLVtYI9G1AE0q2ZIJAnNf9cG+5Ntt+0w6SzhYdk7gb/TIAHPTf8+ua+6zQjrByxoT2zNojSBfFmXlCgip+BLA8Bn8edCgvmb4qDkilsJQCxnFn/+/Zm30Re5UXzOTRyhVJvj4rWJ4f5bgKzrbfr2tH8rZCDZDPXZSWFtUmPwUMpG2WrnoS5fn2jeUfPHdeJT64FdL05a5OPuulwp9seB9J3cDoA4puq2+6oXiY+YLEIYpcyWL6Y0Oyv41OQaY
Date: 18 Apr 2014 01:29:34 -0000
Message-ID: <20140418012934.2728.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf-822@ietf.org
Subject: Re: (DMARC) Why mailing lists are only sort of special
In-Reply-To: <534F1183.6060702@qti.qualcomm.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Vq7K_JPDUsjoFGMdlun4QE5o76I
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 01:30:07 -0000

>At least in the back-of-the-envelope scheme I suggested, the receiver 
>doesn't need to distinguish mailing lists: The originator's system finds 
>out where the mail is going, gets some information from the destination, 
>and signs that and sends it with the message. The mailing list sends 
>that along to the recipients. When my (one of the recipient's) server 
>looks at that info, it determines that the originator sent the message 
>directly to the mailing list, and I can tell that the mailing list sent 
>it to me.

I still think it has security holes but it's worth arguing about, so
I'll follow up on ietf-822, which seems relevant and hasn't been very
busy.

R's,
John


From nobody Thu Apr 17 18:35:02 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 377841A01AD for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 18:35:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 L-AiS8dnM07R for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 18:35:00 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 421921A003A for <ietf@ietf.org>; Thu, 17 Apr 2014 18:35:00 -0700 (PDT)
Received: (qmail 21616 invoked from network); 18 Apr 2014 01:34:56 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 18 Apr 2014 01:34:56 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=acc.53508140.k1404; i=johnl@user.iecc.com; bh=yMqiDTuVXwnznv+OxsLaXUndhBLNYY/LLzzutwTrHHQ=; b=krh6Xo8/u6xoZirlA8BB02BthVPmQaz3757NiuUGCYvHiQa9G/xLhYiJYdcECUkDCGf2t1J+Akf03eQ08ZNCDW7BRJO87NEXC0i8eareFENldEBbG02w4jlY2gT4eeH3XRM8BAA/Qzr3nVpU8Ifi4q/ktXKr6TqQje8QAv4Udzvq6oN1UUqmPOSiPSfb2kUXXmisQi0KmCHRcFM1lOsh1yFVcJFhz5shGZ/Cab7S7dn6f8huI3/8n7ocCGBoAAEh
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=acc.53508140.k1404; olt=johnl@user.iecc.com; bh=yMqiDTuVXwnznv+OxsLaXUndhBLNYY/LLzzutwTrHHQ=; b=o5PU4SxoRO72K7iwqh7Pg/IBN5sf3k386HaptUNegQk3DuSE+qg9Pq3YYkhA4b7YyrJTiM3SX65D3tfeykxvf5sPAUTdZb9fIa8oexaKZ1pJ0wyAO3ioSC5eJaILjwCsQBAMU+KlkHb96tKQVV6fOuwsm2J/ljA9RVVIAa1ada3mFdYPYRPKFc/Di59toQBn66E1+JSeLspEAxbJqyb0rzidy2qmP0/Mwxjmv7V+sIxLJAnkjZ6gHAksaI3DmSwn
Date: 18 Apr 2014 01:34:33 -0000
Message-ID: <20140418013433.2763.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: What I've been wondering about the DMARC problem
In-Reply-To: <534ED376.8060303@bluepopcorn.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AtSO97dsC5jio-t42vv9UT_LTcc
Cc: fenton@bluepopcorn.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 01:35:01 -0000

>> The mailman fix is worse than the disease. I think the .INVALID fix is
>> much better, because Reply-all will still work.
>
>>From the latest DMARC draft, section 8:
>
>"If the RFC5322.From domain does not exist in the DNS, Mail Receivers
>SHOULD direct the receiving SMTP server to reject the message."

As far as I can tell, that bit of poor advice hasn't been implemented.


>So if a receiver that is implementing DMARC is faithful to the draft,
>that won't work very well (nobody has gotten a TLD allocation for
>.invalid, I hope?)

See RFC 2606.

R's,
John

PS: I did a few experiments, and putting two addresses on the From:
line works remarkably well to avoid inappropriate policy failures,
e.g.

 From: Marissa <marissam@yahoo.com>, foo-list@ietf.org
 Subject: whatever
 ...


From nobody Thu Apr 17 18:38:04 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B50F1A01D4 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 18:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 nPFk-UK0NidA for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 18:38:00 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id C29F01A021F for <ietf@ietf.org>; Thu, 17 Apr 2014 18:37:59 -0700 (PDT)
Received: (qmail 22177 invoked from network); 18 Apr 2014 01:37:55 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 18 Apr 2014 01:37:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ae4.535081f3.k1404; i=johnl@user.iecc.com; bh=xI4Q9fA/refsOLIPiJtYgIg4JpO01fSqgTQrJuiQN+M=; b=cbwd7lf5YzeMPuUrGO+1Q68ecoRVe5FJO3rNFuTQCWCFvQdAnOJRmZN3JTYy8b9dUVS1UNpdJb/tPDrPXku/+cjdLYfDA/gJque5GbsFF5N1WkKdANraD4zJL9ZBmcDfQ8Xy9XrqxFHqr049QmVnul9nZsUSmUg496fIxyUtslnNig/jKfRwhIASTCdhPbeOhGmH0B6H55jRP2NyU/v0ObREWaFcuyCrBWuePrUu9l3v/8r9a1wtzmR5uPawZxeF
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:reply-to:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ae4.535081f3.k1404; olt=johnl@user.iecc.com; bh=xI4Q9fA/refsOLIPiJtYgIg4JpO01fSqgTQrJuiQN+M=; b=ceHcDD8vx5H9meFdC4CzSq76aGvsb5qMXehROpCjhwXL6HYpDj4pSk47TbA2KURbGuM55iIdlxheClO7WCepbhOKzdGAXkCuGXxxn2smzifOQeTuMg2+4eizw//CM3tv+K18XfP9C4Dh4j26pOWwK3iAqQRy8qKSc/WFig2111SQdA6d92HPA2pvgX4c8lqSqHcEoacNMlyjSMwHspkOqEGon/aVsJHorSAHepi2PMuh8cNjPZERLgXUUIKyfc8n
Date: 18 Apr 2014 01:37:33 -0000
Message-ID: <20140418013733.2787.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf-822@ietf.org
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <01P6QXI47QVW00004W@mauve.mrochek.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bZbTDZKCHc9GYSiKd00_KkQn8_E
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf-822@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 01:38:02 -0000

>> We're now *way* into technical discussion. Let's take those to
>> https://www.ietf.org/mailman/listinfo/dmarc shall we?
>
>How about we take it some place else? I really don't want this intermingled
>with discussions of things like how to revise the current DMARC specifications
>that hopefully are taking place on that list.

Let's take it to ietf-822 since it seems to be about stuff we'd stick
into message headers.

R's,
John


From nobody Thu Apr 17 18:41:52 2014
Return-Path: <nobo@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22E931A0247; Thu, 17 Apr 2014 18:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.773
X-Spam-Level: 
X-Spam-Status: No, score=-109.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 X-EJv6ivQlcP; Thu, 17 Apr 2014 18:41:45 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) by ietfa.amsl.com (Postfix) with ESMTP id 50A341A0242; Thu, 17 Apr 2014 18:41:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2257; q=dns/txt; s=iport; t=1397785302; x=1398994902; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=b6TQy5UOH1kB4k7F1+x4znplvvUu1wHmVZ+W4zYEsxw=; b=M8na4kgIknpOEp3py/dhLy0NcS3l1vNngH03Atc3rd55Iv16wtgmYHz3 Ud0a/RQCmoBIDwIBRu0d4r1kYtDor0SUJRTUIN7Hq7j4TEu2JoZOlxgi0 HGup9gX6YQLHIAeoX0yalPSHJcdkXRUFsoW9DeEOh9EHWS52M9KfOZRL0 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAASCUFOtJA2M/2dsb2JhbABZgmUhgRLDaIEjFnSCJQEBAQMBOj8MBAIBCA4DBAEBAQoUCQcyFAkIAQEEDgUIh2wIAcwjF44xMQcGgx6BFAEDqzuDMYIr
X-IronPort-AV: E=Sophos;i="4.97,882,1389744000"; d="scan'208";a="36817188"
Received: from alln-core-7.cisco.com ([173.36.13.140]) by alln-iport-4.cisco.com with ESMTP; 18 Apr 2014 01:41:41 +0000
Received: from xhc-aln-x13.cisco.com (xhc-aln-x13.cisco.com [173.36.12.87]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id s3I1ffI5020901 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Apr 2014 01:41:41 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x13.cisco.com ([173.36.12.87]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 20:41:40 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAAiJosQABf5+IAAA1d10A==
Date: Fri, 18 Apr 2014 01:41:40 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E10BDEA@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E10B9F3@xmb-aln-x01.cisco.com> <20140417221511.GC29430@pfrc>
In-Reply-To: <20140417221511.GC29430@pfrc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.242.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/V5STtnrmMWxZQWrGRJ8JMXHD0eU
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 01:41:49 -0000

Hi Jeff,

> -----Original Message-----
> From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> Sent: Thursday, April 17, 2014 6:15 PM
> To: Nobo Akiya (nobo)
> Cc: Black, David; tnadeau@lucidvision.com; Zafar Ali (zali); General Area
> Review Team (gen-art@ietf.org); rtg-bfd@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> On Thu, Apr 17, 2014 at 09:18:28PM +0000, Nobo Akiya (nobo) wrote:
> > > I did not see a compliance requirement for a system that only
> > > implements BFD protocol version 0.  That absence should at least be
> > > mentioned somewhere.  For example, if this reflects a considered and
> > > deliberate decision by the WG, that should be mentioned in the
> introduction.
> >
> > Good point. If I remember correctly, BFD version 0 had a problem in the
> state machine that can cause the two ends to fall into a deadlock. It wou=
ld
> be, therefore, very bad for anybody to have BFD version 0 deployed out
> there, and asking for any MIB compliance requirement for such. Consensus
> on absence of compliance requirement for BFD version 0 was never polled
> in the WG, but I can say that there shouldn't be any desire for that.
>=20
> With respect to v0 vs. v1 from a MIB perspective, the only user-visible d=
etail
> was the additional state in the state machine.  That means that the MIB i=
n its
> current form should be able to accommodate bfd v0.
>=20
> This does suggest, however, that the TC mib could use a comment in the
> DESCRIPTION toward the point that failing(5) is only valid for BFD v0.

Agree, and it's already there :)

[snip]
    IANAbfdSessStateTC ::=3D TEXTUAL-CONVENTION
    STATUS         current
    DESCRIPTION
        "BFD session state. State failing(5) is only applicable if
         corresponding session is running in BFD version 0."
[snip]

-Nobo

>=20
> A conformance clause indicating that those so foolish as to deploy BFD v0
> would better be served by the determinism of a five-year-old child flippi=
ng
> a coin is probably out of scope for the draft.  But if someone has suffic=
iently
> proscriptive text to add to say "don't do bfd v0" that is acceptable to t=
he
> reviewers, I'm fine with that.
>=20
> -- Jeff


From nobody Thu Apr 17 19:11:28 2014
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE5021A0252; Thu, 17 Apr 2014 19:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham
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 yCpnFKqBmsTi; Thu, 17 Apr 2014 19:11:19 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id 46F1E1A0237; Thu, 17 Apr 2014 19:11:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 33CCD1E12A7; Thu, 17 Apr 2014 19:10:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 70Byjs99tRHp; Thu, 17 Apr 2014 19:10:38 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) by c8a.amsl.com (Postfix) with ESMTPSA id B1E691E12A4; Thu, 17 Apr 2014 19:10:37 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Call for Review of draft-iab-itat-report, "Report from the IAB workshop on Internet Technology Adoption and Transition (ITAT)"
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Thu, 17 Apr 2014 22:11:13 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OQOu_a-0v4wFIaRt9qv_mAQ7GiA
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IAB <iab@iab.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 02:11:25 -0000

This is a call for review of "Report from the IAB workshop on Internet =
Technology Adoption and Transition (ITAT)" prior to potential approval =
as an IAB stream RFC.

The document is available for inspection here:
https://datatracker.ietf.org/doc/draft-iab-itat-report-/

The Call for Review will last until 16 May 2014.  Please send comments =
to iab@iab.org.=20

On behalf of the IAB,
Russ Housley
IAB Chair


From nobody Thu Apr 17 19:17:39 2014
Return-Path: <nobo@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5FB91A00B4; Thu, 17 Apr 2014 19:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -114.773
X-Spam-Level: 
X-Spam-Status: No, score=-114.773 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_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 g-aiWU41Ab9d; Thu, 17 Apr 2014 19:17:34 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) by ietfa.amsl.com (Postfix) with ESMTP id B08EA1A001B; Thu, 17 Apr 2014 19:17:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4382; q=dns/txt; s=iport; t=1397787450; x=1398997050; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=b6+yzgHZCagbonRihcCu34WjcP/VyaXKFjyYVKTH4qk=; b=PlJgFkx2jkRNiSNuYtVvORSxqOLgie8yzRJ/A2jcMGEMml/OGPbedR8R lazdMe1RuH0TwhfTX9aJrXdEhOg+JeuLvWaSGdb0ijbpMC54A4D2rKJby YfaOTKrqStDqhyjD7MjPQ4WA6/EfSM3aS6XuTatJr/CbjsjBjrwBCFkkC Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgUFAK6JUFOtJV2b/2dsb2JhbABZgmUhO1fDaIEjFnSCJQEBAQQ6NAsMBAIBCBEEAQEBChQJByERFAkIAgQOBQgBC4dUAxEBDMUiDYZrF4xJgTcQAgEeMQIFBoMegRQElwCDJYtGhVCDMYIr
X-IronPort-AV: E=Sophos;i="4.97,882,1389744000"; d="scan'208";a="318435662"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-1.cisco.com with ESMTP; 18 Apr 2014 02:17:29 +0000
Received: from xhc-aln-x04.cisco.com (xhc-aln-x04.cisco.com [173.36.12.78]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3I2HT3j007371 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 18 Apr 2014 02:17:29 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x04.cisco.com ([173.36.12.78]) with mapi id 14.03.0123.003; Thu, 17 Apr 2014 21:17:29 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-17
Thread-Index: Ac9Zy+Zk0qHspTLsTUq2+7kL82/PpAA5br4AAACOm4AAAEPMAAAAv3uAAAaLVxD///l/AIAATS4g
Date: Fri, 18 Apr 2014 02:17:28 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com>
In-Reply-To: <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.242.20]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HLKK_V430P4-ySU6kb0klFAm8zI
Cc: "ietf@ietf.org" <ietf@ietf.org>, "'Black, David'" <david.black@emc.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 02:17:38 -0000

Hi Sam,

> -----Original Message-----
> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
> Sent: Thursday, April 17, 2014 9:24 PM
> To: Nobo Akiya (nobo)
> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; adrian@olddog.co.uk; rtg=
-
> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> Hi Nobo,
> [sorry for the top post]
>=20
> Yes, this is an old MIB and was in existence for a long time.
> My only concern is with the new extension MIB's. If the base MIB (this MI=
B)
> has write access, future extension MIB's may be forced to support write-
> access. And that is the painful part, where community at large has not
> shown interest in developing write-access MIB's at IETF, lest
> implementation.
>=20
> I want to re-iterate again, I am not objecting or proposing an alternativ=
e
> option. Just wanted to get clarification, so that, we don't have to burn =
cycles
> and do the exercise again, when we have to review these new extension
> MIB's.

That's a good point, it would be good to have this clarified for future wor=
k.

IMO:

For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if gets i=
ncluded in the charter) should look into NETCONF/YANG (i.e. not extension t=
o the BFD base MIB).

For currently chartered BFD tasks, the BFD WG should continue with writable=
 MIB. Large part of that is the BFD base & MPLS MIBs which [painful] writab=
le effort is mostly done already.

-Nobo

>=20
> -sam
>=20
> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>=20
> > Hi Sam,
> >
> >>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
> >>>> %sam - If this MIB allows write access, do you/WG anticipate, any
> >> extension to the MIB should also provide write-access as well? For
> example:
> >> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
> >> this base MIB to support MPLS. It adds more confusion than solving
> >> the issue as base MIB supports write-access, but augmented/ MIB
> extension doesn't.
> >>>>
> >>>> As the BFD MIB authors were not supportive of write-access objects
> >>>> in
> >> the MIBs, why to have them in the first place?
> >>>
> >>> As noted in earlier mailing list chatter, there is some support for
> >>> write access in existing implementations.  Given the lack of
> >>> significant detail when pressed for the name of such an
> >>> implementation, I'm suspecting smaller vendor or internal
> >>> implementation.  That's still sufficient to leave write available.
> >>>
> >>> Given that one of the original contexts of asking if we could remove
> >>> write was whether IETF was being asked to provide such a thing for
> >>> MPLS-TP with related impact on your extension MIB and the answer was
> >>> "no", that shouldn't be the main criteria.
> >> No. The context of my question is not related to MPLS-TP as such, but
> >> write- access support in general.
> >> I should have added 'clarification' in my earlier email.
> >>>
> >>> My suspicion is that if we were to ship the base MIB with writeable
> >>> objects, we may be forced to consider similar things for the
> >>> extension
> >> MIB(s).
> >> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE
> >> and BFD-MIB respectively,  with write-access. Had to do write-access
> >> because of the reason you've mentioned above, which is base MIB. It
> >> would be painful to publish/support write-access MIB's when there is
> >> no clear interest. Hence my clarification question.
> >
> > This mentions three vendors wanting to implement MIB as writable.
> >
> > http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
> >
> > And one more vendor voicing for writable.
> >
> > http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
> >
> > I agree that defining & wording writable MIB is much more painful than =
all
> read-only MIB. But above thread indicates the desire by multiple vendors =
to
> implement writable BFD MIB. Therefore it does seem that there are
> interests, and going forward with write-access will benefit the community=
.
> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
> those implementing them as just read-only.
> >
> > -Nobo
> >
> >>
> >> -sam
> >>
> >>>
> >>> -- Jeff
> >


From nobody Thu Apr 17 19:19:11 2014
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC17B1A00B4; Thu, 17 Apr 2014 19:19:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 sZ4x4Yn91-kt; Thu, 17 Apr 2014 19:19:06 -0700 (PDT)
Received: from mail-pb0-x230.google.com (mail-pb0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id A93BC1A001B; Thu, 17 Apr 2014 19:19:06 -0700 (PDT)
Received: by mail-pb0-f48.google.com with SMTP id md12so994256pbc.21 for <multiple recipients>; Thu, 17 Apr 2014 19:19:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kIw2nM3r6y6FniSxk3XSE9wIBRMAQ+U6ypzHYqbDpU0=; b=rg8tuoOHlgTXMMoFIjrTCDqvEPOIcJEqCgsf8FqmnqKlkR66kiZyxGuZ7/8zc8qUMt 6w3rp2bUZJG2FyGUSIGGK3/xjHwoxiWuOeYsr2u6B+0BY9pgfQFAQG0R3jC6ms5Mknxp u5S1tYAqAV4A9203h/Ui44kZJItnf4yb6DOFyq2hSXU+YOq/zTxg574nh4B/f9macORV Jd9ypy1GSj9Bnn+k3+bILaJB/7Va7hRXhCwfpjGd7gam8aYfx2N+kSwrB74d7Ea13m8o NG51RED13+PFoiiNGTZOHGAnYVtnOkL8xPEjku97v9g938IQsOJjZcLC/RRTd5H+XcMA aYmQ==
X-Received: by 10.66.197.135 with SMTP id iu7mr18967003pac.149.1397787543040;  Thu, 17 Apr 2014 19:19:03 -0700 (PDT)
Received: from [192.168.1.5] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id xo9sm133063879pab.18.2014.04.17.19.19.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 19:19:02 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
From: Sam Aldrin <aldrin.ietf@gmail.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
Date: Thu, 17 Apr 2014 19:19:00 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <D48D4ED0-BA1B-49E6-9E6F-4052C59B83FE@gmail.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_Bb053hnuRquVJl-RHNbaPVaaCI
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, General Area Review Team <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 02:19:08 -0000

Thanks, Nobo. Much appreciated.

-sam
On Apr 17, 2014, at 7:17 PM, Nobo Akiya (nobo) <nobo@cisco.com> wrote:

> Hi Sam,
>=20
>> -----Original Message-----
>> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
>> Sent: Thursday, April 17, 2014 9:24 PM
>> To: Nobo Akiya (nobo)
>> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; adrian@olddog.co.uk; =
rtg-
>> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>>=20
>> Hi Nobo,
>> [sorry for the top post]
>>=20
>> Yes, this is an old MIB and was in existence for a long time.
>> My only concern is with the new extension MIB's. If the base MIB =
(this MIB)
>> has write access, future extension MIB's may be forced to support =
write-
>> access. And that is the painful part, where community at large has =
not
>> shown interest in developing write-access MIB's at IETF, lest
>> implementation.
>>=20
>> I want to re-iterate again, I am not objecting or proposing an =
alternative
>> option. Just wanted to get clarification, so that, we don't have to =
burn cycles
>> and do the exercise again, when we have to review these new extension
>> MIB's.
>=20
> That's a good point, it would be good to have this clarified for =
future work.
>=20
> IMO:
>=20
> For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if =
gets included in the charter) should look into NETCONF/YANG (i.e. not =
extension to the BFD base MIB).
>=20
> For currently chartered BFD tasks, the BFD WG should continue with =
writable MIB. Large part of that is the BFD base & MPLS MIBs which =
[painful] writable effort is mostly done already.
>=20
> -Nobo
>=20
>>=20
>> -sam
>>=20
>> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>>=20
>>> Hi Sam,
>>>=20
>>>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>>>> %sam - If this MIB allows write access, do you/WG anticipate, any
>>>> extension to the MIB should also provide write-access as well? For
>> example:
>>>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
>>>> this base MIB to support MPLS. It adds more confusion than solving
>>>> the issue as base MIB supports write-access, but augmented/ MIB
>> extension doesn't.
>>>>>>=20
>>>>>> As the BFD MIB authors were not supportive of write-access =
objects
>>>>>> in
>>>> the MIBs, why to have them in the first place?
>>>>>=20
>>>>> As noted in earlier mailing list chatter, there is some support =
for
>>>>> write access in existing implementations.  Given the lack of
>>>>> significant detail when pressed for the name of such an
>>>>> implementation, I'm suspecting smaller vendor or internal
>>>>> implementation.  That's still sufficient to leave write available.
>>>>>=20
>>>>> Given that one of the original contexts of asking if we could =
remove
>>>>> write was whether IETF was being asked to provide such a thing for
>>>>> MPLS-TP with related impact on your extension MIB and the answer =
was
>>>>> "no", that shouldn't be the main criteria.
>>>> No. The context of my question is not related to MPLS-TP as such, =
but
>>>> write- access support in general.
>>>> I should have added 'clarification' in my earlier email.
>>>>>=20
>>>>> My suspicion is that if we were to ship the base MIB with =
writeable
>>>>> objects, we may be forced to consider similar things for the
>>>>> extension
>>>> MIB(s).
>>>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, =
MPLS-TE
>>>> and BFD-MIB respectively,  with write-access. Had to do =
write-access
>>>> because of the reason you've mentioned above, which is base MIB. It
>>>> would be painful to publish/support write-access MIB's when there =
is
>>>> no clear interest. Hence my clarification question.
>>>=20
>>> This mentions three vendors wanting to implement MIB as writable.
>>>=20
>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>>>=20
>>> And one more vendor voicing for writable.
>>>=20
>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>>>=20
>>> I agree that defining & wording writable MIB is much more painful =
than all
>> read-only MIB. But above thread indicates the desire by multiple =
vendors to
>> implement writable BFD MIB. Therefore it does seem that there are
>> interests, and going forward with write-access will benefit the =
community.
>> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
>> those implementing them as just read-only.
>>>=20
>>> -Nobo
>>>=20
>>>>=20
>>>> -sam
>>>>=20
>>>>>=20
>>>>> -- Jeff
>>>=20
>=20


From nobody Thu Apr 17 19:48:12 2014
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A7A31A0194; Thu, 17 Apr 2014 19:48:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.6
X-Spam-Level: 
X-Spam-Status: No, score=-0.6 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 SXJNWw-pUZP6; Thu, 17 Apr 2014 19:48:09 -0700 (PDT)
Received: from elasmtp-mealy.atl.sa.earthlink.net (elasmtp-mealy.atl.sa.earthlink.net [209.86.89.69]) by ietfa.amsl.com (Postfix) with ESMTP id ABBAE1A001E; Thu, 17 Apr 2014 19:48:06 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=jk6KUMFGWhs0UB7t4U3v6bBAIYZ23zc1Fsy516gl3MSoVGCn9U/AHLlwE5XG0hMM; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.39] (helo=elwamui-little.atl.sa.earthlink.net) by elasmtp-mealy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WayqJ-0007yr-En; Thu, 17 Apr 2014 22:47:55 -0400
Received: from 99.23.160.116 by webmail.earthlink.net with HTTP; Thu, 17 Apr 2014 22:47:55 -0400
Message-ID: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
Date: Thu, 17 Apr 2014 19:47:55 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>,  "Nobo Akiya (nobo)" <nobo@cisco.com>
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbc8c1f0f3881847dfdf761c2c2f8dbc85f350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.39
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZvHI_9LjdZFacovb-kGIDIkqvmg
Cc: "ietf@ietf.org" <ietf@ietf.org>, "'Black, David'" <david.black@emc.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 02:48:10 -0000

Hi -

>From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
>Sent: Apr 17, 2014 6:24 PM
...
>Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
...
>My only concern is with the new extension MIB's.
>If the base MIB (this MIB) has write access,
>future extension MIB's may be forced to support
>write-access.

And how, exactly, does the fact that a base MIB module
permits write access force extension MIB modules to
require (or even permit) write access?

It's perfectly reasonable SMI to define an AUGMENTS
table consisting entirely of read-only objects.

Randy


From nobody Thu Apr 17 20:53:35 2014
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B60861A0147; Thu, 17 Apr 2014 20:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 Rp9kF1SqukfW; Thu, 17 Apr 2014 20:53:30 -0700 (PDT)
Received: from mail-pa0-x234.google.com (mail-pa0-x234.google.com [IPv6:2607:f8b0:400e:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 339291A00C0; Thu, 17 Apr 2014 20:53:30 -0700 (PDT)
Received: by mail-pa0-f52.google.com with SMTP id rd3so1066974pab.39 for <multiple recipients>; Thu, 17 Apr 2014 20:53:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IPL7jibdZfBm/MKJUWytg45glowdrHwo43dKe8MCkCw=; b=KdIt143+7azLk0RP+nlVOLdWO0Pm2VVRrmwI2EFJuF551H5RcHLnGJybuhjv5wpiHJ tR7/xzCNU11kCd+KPrCZtyxevuYRuRJ4OGVp2qHSijjeinouqXuzqvFcPCz48h8Yecwm MHBHe6BsbDCaMb3oWBm7KAV6OtHIYz2YBbKc+ucEChFBZ1KWEsFv0EbqwO+zu9f2nb6R MSeP33Xfidoj+6Ij9aLUztdYlnx6I+LVr/5KOVj0t1AHmqsChFn+4iZ94xEBPtkYs6j1 eNCa3qkzQkpeWnmkA7JUkU3Jd0rJKRe5Ux9Pr+mBZ4W2opLGvRpwfidx4bDppnBEIkNA GJ0g==
X-Received: by 10.68.178.66 with SMTP id cw2mr19692869pbc.89.1397793206554; Thu, 17 Apr 2014 20:53:26 -0700 (PDT)
Received: from [192.168.1.7] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id ha2sm56880842pbb.8.2014.04.17.20.53.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 20:53:25 -0700 (PDT)
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
In-Reply-To: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
Date: Thu, 17 Apr 2014 20:53:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B03C974-91FE-48CC-AF82-A82517E106C0@gmail.com>
References: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BEBY8m1EiZOuHYkI3FGjTfCvIds
Cc: "ietf@ietf.org" <ietf@ietf.org>, "'Black, David'" <david.black@emc.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 03:53:31 -0000

Hi Randy,

Inline for my comments.
On Apr 17, 2014, at 7:47 PM, Randy Presuhn wrote:

> Hi -
>=20
>> From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
>> Sent: Apr 17, 2014 6:24 PM
> ...
>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
> ...
>> My only concern is with the new extension MIB's.
>> If the base MIB (this MIB) has write access,
>> future extension MIB's may be forced to support
>> write-access.
>=20
> And how, exactly, does the fact that a base MIB module
> permits write access force extension MIB modules to
> require (or even permit) write access?
>=20
> It's perfectly reasonable SMI to define an AUGMENTS
> table consisting entirely of read-only objects.

True, you could add only read-only objects.=20
But the point is, not with syntax or what could be added or augmented.
In order to support new functionality, we are extending/augmenting =
existing base MIB and in addition some write-access objects as well. If =
we make those new ones read-only objects, then only some objects or =
tables could be used with write-access and these new objects (read-only) =
have to be configured differently. In other words, full functionality =
cannot be provided. This got nothing to do with SMI.

The point we are extending or re-using the base MIB is not to re-define =
new objects altogether and also to re-use the applications. Atleast that =
is what we have done in this case.

Hope this clarifies.

cheers
-sam
>=20
> Randy


From nobody Thu Apr 17 21:28:54 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDD2D1A0132 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 21:28:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.375
X-Spam-Level: 
X-Spam-Status: No, score=-0.375 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Ar288V43-50r for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 21:28:48 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id C83A81A0101 for <ietf@ietf.org>; Thu, 17 Apr 2014 21:28:48 -0700 (PDT)
Received: from [192.168.2.11] (unknown [99.17.29.183]) by dougbarton.us (Postfix) with ESMTPSA id 19FEB22B1A for <ietf@ietf.org>; Fri, 18 Apr 2014 04:28:44 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397795324; bh=y3vV2/nX+Q5N1ZzV7s79t82aSzuPZIChLK2s7Ddf4V8=; h=Date:From:To:Subject:References:In-Reply-To; b=jZOigkFPnvWmvWmfbRPrFoCL2CDmks7nnvHFLYPUUqXsrofF6a8+NgV7wx+aqD0EZ x6J3apmSAlhoAG8MLobZBKgcJB+/7Slduxl+lb0GnZbiL2Og8IEgJo1un9dgvuJx26 2V4kSQTBX0Xm4+GXAqiBJksKl0VpwTjPZwgwWRxU=
Message-ID: <5350A9FB.9010307@dougbarton.us>
Date: Thu, 17 Apr 2014 21:28:43 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com>
In-Reply-To: <01P6QVVGQA4W00004W@mauve.mrochek.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UBNYrjiOoprqId3r2pmTkR_XK1c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 04:28:53 -0000

On 04/17/2014 07:41 AM, ned+ietf@mauve.mrochek.com wrote:
> I also find it particularly revealing that one of the arguments being
> made here is along of the lines of, "Everything else has had to
> change, why are those stodgy old mailing list thingies somehow
> exempt?" Except that's not it at all - the approach was always
> essentially, "We're going to screw you, how about you do X or Y to
> mitigate the damage a little?" To which the answer, predictably, was
> less than enthusiastic.

Another way to look at this is that the IETF, which ostensibly is 
interested in "input from operators," received pretty clear "input" from 
the operators of the largest mail systems on the planet, and 
collectively stuck their fingers in their ears and sang "la la la la la, 
I can't hear you" because it didn't like what was being said.

The message was pretty clearly, "We think DMARC is valuable enough to us 
that we plan to deploy it even though it has the unfortunate side effect 
of causing problems for mailing lists." Rather than throwing up our 
hands and telling the DMARC folks that we refuse to work with them 
unless their solution solves the problem of our anachronistic use case 
that that constitutes only a tiny percentage of their overall traffic; a 
more rational approach would have been to recognize that the tail is not 
going to wag the dog here and start working with mailing list authors to 
solve the problem of how to live in a world that includes DMARC.

When people talk about how the IETF is out of touch with the operator 
community and increasingly irrelevant, this is exactly the kind of thing 
that they are talking about. We ignore this lesson at our peril.

Doug


From nobody Thu Apr 17 21:35:15 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F05D1A0101 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 21:35:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 YCesCy8O5kcG for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 21:35:08 -0700 (PDT)
Received: from mail-ee0-x22e.google.com (mail-ee0-x22e.google.com [IPv6:2a00:1450:4013:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id AD30D1A0088 for <ietf@ietf.org>; Thu, 17 Apr 2014 21:35:07 -0700 (PDT)
Received: by mail-ee0-f46.google.com with SMTP id t10so1198696eei.19 for <ietf@ietf.org>; Thu, 17 Apr 2014 21:35:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=u6LmbUjMoPNGf3Y2WJ9SuMUV1yRUX5dqLo0W7YtBpyc=; b=T2kYMkGcQR2s9zpYBZq2Zt6g8Q4UrEo7nG2nuMwlPtW99P63ZzWBpWn1JWiIhvujJQ 1rIAoSV0NmgRpjgGKtdL2Z7aMyGY5HDsqqyE8qwLIXercSwX1HUmFjFZ2AoCM8sojvzx gnFYU4DoR5xefblGHNEGk8eB1jXrb9xobNy7xnIxmTXNuvdjIq4/cGHiJ8uPkrljm4ik us9UAPfK1y+bSvO96O4w7a7A+GpBcWVaisSsSJXpEfzIaOiYCma1DusrLanBFJZ6Ld5c oPSFEhPygkPotwQuk0b+LThlzcL0191klDpcz00eZpO37KYleBMPQFlAF98k+4prXawE XZ5w==
X-Received: by 10.14.47.133 with SMTP id t5mr1390092eeb.67.1397795703438; Thu, 17 Apr 2014 21:35:03 -0700 (PDT)
Received: from [192.168.1.101] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id g3sm73023182eet.35.2014.04.17.21.35.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 21:35:02 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: (DMARC) How a whitelist would work, was Why mailing lists
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <alpine.BSF.2.00.1404172008250.2116@joyce.lan>
Date: Fri, 18 Apr 2014 07:35:02 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <29834711-2D38-4D7D-97FA-69CB602AC5C3@gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com> <alpine.BSF.2.00.1404170008470.2194@joyce.lan> <9760.1397773072@sandelman.ca> <alpine.BSF.2.00.1404172008250.2116@joyce.lan>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8kKuS4F2He-fcIryukOX5k0aNyU
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf\\@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 04:35:13 -0000

On Apr 18, 2014, at 3:10 AM, John R Levine <johnl@taugh.com> wrote:

>> Are you saying that gmail and yahoo have to know about my =
lists.sandelman.ca
>> before I can have gmail/yahoo members on my little local list?
>=20
> Yeah.  It's clear from the DMARC summary reports I'm getting that the =
big mail systems already have a pretty good idea of where the mailing =
lists are,=20

They know about big lists. Maybe even IETF lists. But do they know about =
sandelman.ca? Do they know about @irtf.org?

I really don=92t like specs that work well only for large companies.

Yoav



From nobody Thu Apr 17 21:38:00 2014
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5D4D1A0101; Thu, 17 Apr 2014 21:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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] autolearn=ham
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 ZEgl1aKCfVJI; Thu, 17 Apr 2014 21:37:57 -0700 (PDT)
Received: from elasmtp-banded.atl.sa.earthlink.net (elasmtp-banded.atl.sa.earthlink.net [209.86.89.70]) by ietfa.amsl.com (Postfix) with ESMTP id 29C2F1A0088; Thu, 17 Apr 2014 21:37:56 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=TgJQePhp8ZEIoouz1h65UWPyEZqrEqCSR+hDr1FY+UMXONUTjvyPVsyCjSjNwJHk; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [99.23.160.116] (helo=oemcomputer) by elasmtp-banded.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1Wb0Yh-0004Eg-GT; Fri, 18 Apr 2014 00:37:51 -0400
Message-ID: <007101cf5ab8$77cf7280$6b01a8c0@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
References: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net> <4B03C974-91FE-48CC-AF82-A82517E106C0@gmail.com>
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Date: Thu, 17 Apr 2014 21:43:46 -0600
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbcc293d221268b88ce71ccdfb8fd2a570a350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 99.23.160.116
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/q-bksWWgbpoujfPP0kDEfuNhZPY
Cc: ietf@ietf.org, "'Black, David'" <david.black@emc.com>, adrian@olddog.co.uk, rtg-bfd@ietf.org, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 04:37:58 -0000

Hi -

> From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
...
> Sent: Thursday, April 17, 2014 9:53 PM
> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
...
> In order to support new functionality, we are extending/augmenting existing base
> MIB and in addition some write-access objects as well. If we make those new
> ones read-only objects, then only some objects or tables could be used with
> write-access and these new objects (read-only) have to be configured differently.
> In other words, full functionality cannot be provided. This got nothing to do with SMI.

Then what's the problem?  If the WG has consensus to add functionality, and
that functionality logically requires a read-write MIB module of extension,
the IESG policy already allows for such cases.

Randy


From nobody Thu Apr 17 21:50:45 2014
Return-Path: <aldrin.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B93B1A0140; Thu, 17 Apr 2014 21:50:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 3cn9wfGe_k4M; Thu, 17 Apr 2014 21:50:40 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id EBF7C1A0130; Thu, 17 Apr 2014 21:50:39 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id kl14so1103677pab.32 for <multiple recipients>; Thu, 17 Apr 2014 21:50:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=l2MfswrE2Co/PzLnz2IWz81pjYeDLiPL72wg2NcwRfo=; b=szJHJG1zo6gUy7R/UnnmbDbuYZUvlCxfrws3Rzdk3dPWqjAevjtUQ7lB1RXheJp6As C8iJgGPxX1IJuK4nXB+n1G6iAjJOFG8p1XjIVBHdaOFdfvnETF7jCkpEIFF/VoVFyS73 NJ12GYVZpDrNFMdDLgc3tQKwh3G/J7ua3XlL0s2M0eUAQY5lMfDfr3AiwINj/YBE2uw/ NQB6kFS6Zz/eAksoe4Q3DzfBjAqlfd6Gp1ECFNsGbik+sZMe6onOgalpXLqJ2ZuxftD3 GA+vSJE/CvIBaGjn7sJXc8gjsFpnoHKJdfa1L1TzK4DF8nGsnbqI/dJpjJhBgAxO82wj uXXw==
X-Received: by 10.66.150.169 with SMTP id uj9mr19900037pab.148.1397796635882;  Thu, 17 Apr 2014 21:50:35 -0700 (PDT)
Received: from [192.168.1.5] (c-107-3-154-60.hsd1.ca.comcast.net. [107.3.154.60]) by mx.google.com with ESMTPSA id vd8sm135850111pac.12.2014.04.17.21.50.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 17 Apr 2014 21:50:35 -0700 (PDT)
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Content-Type: text/plain; charset=iso-8859-1
From: Sam Aldrin <aldrin.ietf@gmail.com>
X-Priority: 3
In-Reply-To: <007101cf5ab8$77cf7280$6b01a8c0@oemcomputer>
Date: Thu, 17 Apr 2014 21:50:33 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <7A35F863-6CBB-447B-9232-B353141E4D9A@gmail.com>
References: <25276146.1397789275400.JavaMail.root@elwamui-little.atl.sa.earthlink.net> <4B03C974-91FE-48CC-AF82-A82517E106C0@gmail.com> <007101cf5ab8$77cf7280$6b01a8c0@oemcomputer>
To: Randy Presuhn <randy_presuhn@mindspring.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/A8GSMRpBH5ccimjJqHEud-WtI9M
Cc: ietf@ietf.org, "Black, David" <david.black@emc.com>, adrian@olddog.co.uk, rtg-bfd@ietf.org, "Zafar Ali \(zali\)" <zali@cisco.com>, General Area Review Team <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 04:50:42 -0000

Hi Randy,

On Apr 17, 2014, at 8:43 PM, Randy Presuhn =
<randy_presuhn@mindspring.com> wrote:

> Hi -
>=20
>> From: "Sam K. Aldrin" <aldrin.ietf@gmail.com>
> ...
>> Sent: Thursday, April 17, 2014 9:53 PM
>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
> ...
>> In order to support new functionality, we are extending/augmenting =
existing base
>> MIB and in addition some write-access objects as well. If we make =
those new
>> ones read-only objects, then only some objects or tables could be =
used with
>> write-access and these new objects (read-only) have to be configured =
differently.
>> In other words, full functionality cannot be provided. This got =
nothing to do with SMI.
>=20
> Then what's the problem?  If the WG has consensus to add =
functionality, and
> that functionality logically requires a read-write MIB module of =
extension,
> the IESG policy already allows for such cases.

Yes, that is what I wanted to clarify, when I sent my email, to find if =
there is WG consensus to go with write-access objects, as this base MIB =
will have implication on the other MIB in the pipeline?

We had quite a big thread on MPLS list on this very subject and wanted =
to avoid the repeat.
http://www.ietf.org/mail-archive/web/mpls/current/msg11598.html

cheers
-sam
>=20
> Randy
>=20


From nobody Thu Apr 17 21:53:16 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 981421A0130 for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 21:53:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.773
X-Spam-Level: 
X-Spam-Status: No, score=-5.773 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 ZcORYSlBkNUX for <ietf@ietfa.amsl.com>; Thu, 17 Apr 2014 21:53:10 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 6D61D1A0088 for <ietf@ietf.org>; Thu, 17 Apr 2014 21:53:10 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 18 Apr 2014 00:53:06 -0400
Received: from d01dlp02.pok.ibm.com (9.56.250.167) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 18 Apr 2014 00:53:04 -0400
Received: from b01cxnp22033.gho.pok.ibm.com (b01cxnp22033.gho.pok.ibm.com [9.57.198.23]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 740BB6E801B for <ietf@ietf.org>; Fri, 18 Apr 2014 00:52:57 -0400 (EDT)
Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by b01cxnp22033.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s3I4r4gX2556236 for <ietf@ietf.org>; Fri, 18 Apr 2014 04:53:04 GMT
Received: from d01av03.pok.ibm.com (localhost [127.0.0.1]) by d01av03.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s3I4r3lB024000 for <ietf@ietf.org>; Fri, 18 Apr 2014 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av03.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s3I4r3YX023997 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 18 Apr 2014 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s3I4r3Fk032416 for <ietf@ietf.org>; Fri, 18 Apr 2014 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s3I4r3RI032374 for ietf@ietf.org; Fri, 18 Apr 2014 00:53:03 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201404180453.s3I4r3RI032374@rotala.raleigh.ibm.com>
Date: Fri, 18 Apr 2014 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14041804-7182-0000-0000-00000A612956
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qwcJfQ5peVafsREzTqPDz6SEuYo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 04:53:15 -0000

Total of 333 messages in the last 7 days.
 
script run at: Fri Apr 18 00:53:02 EDT 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 13.81% |   46 | 11.01% |   352055 | mfidelman@meetinghouse.net
  6.61% |   22 |  5.18% |   165582 | johnl@taugh.com
  5.71% |   19 |  5.46% |   174711 | superuser@gmail.com
  3.60% |   12 |  5.39% |   172371 | mhammer@ag.com
  4.80% |   16 |  3.45% |   110360 | tytso@mit.edu
  3.30% |   11 |  4.11% |   131557 | dave@cridland.net
  3.90% |   13 |  3.18% |   101792 | brian.e.carpenter@gmail.com
  3.30% |   11 |  3.53% |   112824 | hsantos@isdg.net
  0.30% |    1 |  5.94% |   189934 | kathleen.moriarty.ietf@gmail.com
  2.70% |    9 |  2.02% |    64650 | mcr+ietf@sandelman.ca
  2.40% |    8 |  2.09% |    66759 | sm+ietf@elandsys.com
  2.40% |    8 |  2.03% |    64900 | ned+ietf@mauve.mrochek.com
  2.10% |    7 |  1.65% |    52708 | dougb@dougbarton.us
  1.20% |    4 |  2.48% |    79209 | seth.p.johnson@gmail.com
  1.50% |    5 |  2.03% |    64985 | doug.mtview@gmail.com
  1.80% |    6 |  1.60% |    51254 | ynir.ietf@gmail.com
  0.90% |    3 |  2.14% |    68602 | bclaise@cisco.com
  1.50% |    5 |  1.38% |    44016 | aldrin.ietf@gmail.com
  1.50% |    5 |  1.32% |    42297 | presnick@qti.qualcomm.com
  1.50% |    5 |  1.28% |    40930 | listsebby@me.com
  1.20% |    4 |  1.52% |    48654 | abdussalambaryun@gmail.com
  1.50% |    5 |  1.19% |    38044 | scott@kitterman.com
  1.20% |    4 |  1.47% |    47008 | david.black@emc.com
  1.50% |    5 |  1.11% |    35519 | john-ietf@jck.com
  1.50% |    5 |  1.06% |    34047 | dhc@dcrocker.net
  1.20% |    4 |  1.32% |    42162 | nobo@cisco.com
  1.20% |    4 |  1.12% |    35760 | rwfranks@acm.org
  0.90% |    3 |  1.39% |    44407 | tnadeau@lucidvision.com
  0.90% |    3 |  1.32% |    42195 | douglasroyer@gmail.com
  1.20% |    4 |  1.02% |    32589 | spencerdawkins.ietf@gmail.com
  1.20% |    4 |  0.84% |    26839 | mrex@sap.com
  1.20% |    4 |  0.80% |    25569 | dcrocker@bbiw.net
  0.60% |    2 |  1.27% |    40515 | andy@yumaworks.com
  0.90% |    3 |  0.77% |    24542 | ietf@thomasclausen.org
  0.90% |    3 |  0.70% |    22302 | johnl@iecc.com
  0.90% |    3 |  0.69% |    22132 | hallam@gmail.com
  0.90% |    3 |  0.66% |    21029 | ted.lemon@nominum.com
  0.90% |    3 |  0.65% |    20882 | l.wood@surrey.ac.uk
  0.90% |    3 |  0.60% |    19332 | wes@mti-systems.com
  0.60% |    2 |  0.72% |    23107 | dmm@1-4-5.net
  0.60% |    2 |  0.47% |    14985 | marka@isc.org
  0.60% |    2 |  0.46% |    14738 | worley@ariadne.com
  0.60% |    2 |  0.45% |    14302 | vesely@tana.it
  0.60% |    2 |  0.41% |    13155 | cabo@tzi.org
  0.60% |    2 |  0.39% |    12408 | jhaas@pfrc.org
  0.30% |    1 |  0.68% |    21632 | cdel@firsthand.net
  0.60% |    2 |  0.35% |    11148 | iab-chair@iab.org
  0.30% |    1 |  0.64% |    20386 | wesley.george@twcable.com
  0.30% |    1 |  0.62% |    19676 | spromano@unina.it
  0.30% |    1 |  0.58% |    18645 | r.e.sonneveld@sonnection.nl
  0.30% |    1 |  0.49% |    15752 | hector.santos45@yahoo.com
  0.30% |    1 |  0.44% |    14225 | mars.techno.cat@gmail.com
  0.30% |    1 |  0.37% |    11767 | aaron.ding@cl.cam.ac.uk
  0.30% |    1 |  0.36% |    11543 | tjw.ietf@gmail.com
  0.30% |    1 |  0.34% |    10882 | akatlas@gmail.com
  0.30% |    1 |  0.29% |     9374 | narten@us.ibm.com
  0.30% |    1 |  0.27% |     8622 | warren@kumari.net
  0.30% |    1 |  0.26% |     8352 | rpelletier@isoc.org
  0.30% |    1 |  0.25% |     8136 | agmalis@gmail.com
  0.30% |    1 |  0.25% |     8108 | jari.arkko@piuha.net
  0.30% |    1 |  0.25% |     7942 | fergie@people.ops-trust.net
  0.30% |    1 |  0.24% |     7758 | serrhini@mail.ru
  0.30% |    1 |  0.24% |     7644 | rwfranks@gmail.com
  0.30% |    1 |  0.23% |     7428 | thomas@thomasclausen.org
  0.30% |    1 |  0.23% |     7405 | melinda.shore@gmail.com
  0.30% |    1 |  0.22% |     7161 | scott.brim@gmail.com
  0.30% |    1 |  0.22% |     6953 | hartmans-ietf@mit.edu
  0.30% |    1 |  0.21% |     6806 | stephen.farrell@cs.tcd.ie
  0.30% |    1 |  0.21% |     6744 | fenton@bluepopcorn.net
  0.30% |    1 |  0.21% |     6679 | adrian@olddog.co.uk
  0.30% |    1 |  0.21% |     6619 | jelte.jansen@sidn.nl
  0.30% |    1 |  0.21% |     6576 | abhishekv.verma@gmail.com
  0.30% |    1 |  0.20% |     6503 | olejacobsen@me.com
  0.30% |    1 |  0.20% |     6336 | bzeeb-lists@lists.zabbadoz.net
  0.30% |    1 |  0.20% |     6249 | randy_presuhn@mindspring.com
  0.30% |    1 |  0.19% |     6134 | syedalisuleman@gmail.com
  0.30% |    1 |  0.18% |     5874 | tglassey@earthlink.net
  0.30% |    1 |  0.17% |     5476 | randy@psg.com
  0.30% |    1 |  0.16% |     5249 | kent@bbn.com
  0.30% |    1 |  0.16% |     5020 | rjsparks@nostrum.com
--------+------+--------+----------+------------------------
100.00% |  333 |100.00% |  3198522 | Total


From nobody Thu Apr 17 22:11:11 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D5A01A0088; Thu, 17 Apr 2014 22:11:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.523
X-Spam-Level: 
X-Spam-Status: No, score=-1.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 SLI_LlfkQkmY; Thu, 17 Apr 2014 22:11:09 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 81F671A0166; Thu, 17 Apr 2014 22:11:08 -0700 (PDT)
Received: from [192.168.1.65] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id F11701FDD6; Fri, 18 Apr 2014 07:11:03 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_512DE7AD-E4CE-486A-8290-682B83AF8F9C"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Call for Review of draft-iab-itat-report, "Report from the IAB workshop on Internet Technology Adoption and Transition (ITAT)"
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org>
Date: Fri, 18 Apr 2014 07:10:58 +0200
Message-Id: <25D7E426-D21C-4EA3-A5A5-3742A8C41F81@frobbit.se>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org>
To: ietf@ietf.org, IAB <iab@iab.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bnB-74lAA-0LIvI374_1v-G2YsM
Cc: IETF Announce <ietf-announce@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 05:11:10 -0000

--Apple-Mail=_512DE7AD-E4CE-486A-8290-682B83AF8F9C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On 18 apr 2014, at 04:11, IAB Chair <iab-chair@iab.org> wrote:

> This is a call for review of "Report from the IAB workshop on Internet =
Technology Adoption and Transition (ITAT)" prior to potential approval =
as an IAB stream RFC.
>=20
> The document is available for inspection here:
> https://datatracker.ietf.org/doc/draft-iab-itat-report-/

FWIW, the correct URL is:

<https://datatracker.ietf.org/doc/draft-iab-itat-report/>

> The Call for Review will last until 16 May 2014.  Please send comments =
to iab@iab.org.=20
>=20
> On behalf of the IAB,
> Russ Housley
> IAB Chair

   Patrik


--Apple-Mail=_512DE7AD-E4CE-486A-8290-682B83AF8F9C
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFTULPkrMabGguI180RAifgAJwO/VZF0QcRus2773Qt+BwdxqsR7ACgggVj
BbqqJA3Sw02js6SZALPv0mI=
=Ogkb
-----END PGP SIGNATURE-----

--Apple-Mail=_512DE7AD-E4CE-486A-8290-682B83AF8F9C--


From nobody Thu Apr 17 23:13:29 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DB481A018F; Thu, 17 Apr 2014 23:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.272
X-Spam-Level: 
X-Spam-Status: No, score=-2.272 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 twwv43eft0FU; Thu, 17 Apr 2014 23:13:20 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 95B601A00D4; Thu, 17 Apr 2014 23:13:20 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.145.222]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3I6D3tg010829 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2014 23:13:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397801594; bh=4vH2YZBSUP9ZolzYePMEjSvpNgNzDRHOUuSqi3zMoFA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=tsFqFB9PRbQcHygPKD6xeCBhVzGnPyvKlNBDCdoHkfmXXJYrlhejnsGc43DFNp+qK RDC0xsQYBYESfMcIMPuZWpTmNP80at7L7iyoL0/jGWL6ucAeNFEhXxm/Qg90QX/ya+ eEbKE/ruh9dD4h0hKXPnL7+LzHtq/kPx/BAFRVTU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397801594; i=@elandsys.com; bh=4vH2YZBSUP9ZolzYePMEjSvpNgNzDRHOUuSqi3zMoFA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZkfOrVV8XStk+Ce7OkHd+K4M9unfw4PwjtwQ3q4U+/CirMiCLnB/JLVp/Omu6OrHp PhsXYawfgqNZiXQhl3fg1CLRYqgG8AXNxRzsDtOH4mrg/3eJlU/sDPxHMcf92sIdu6 DBN4HLpVWnRnfLgo8n4HhIF6l+ksr6Wh0BFOhG8I=
Message-Id: <6.2.5.6.2.20140417215305.0dc8c008@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 17 Apr 2014 23:11:31 -0700
To: iab@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Internet Technology Adoption and Transition
In-Reply-To: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TENcaevBAlePtenIeYlc4hVMUbA
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 06:13:25 -0000

Hello,
At 19:11 17-04-2014, IAB Chair wrote:
>This is a call for review of "Report from the IAB workshop on 
>Internet Technology Adoption and Transition (ITAT)" prior to 
>potential approval as an IAB stream RFC.
>
>The document is available for inspection here:
>https://datatracker.ietf.org/doc/draft-iab-itat-report-/

I read the report.  Section 2 mentions that SMTP and IMAP in the 
applications space have continued to evolve.  I have not see much 
evolution in the SMTP space.  I'll leave the relevant people to 
comment about IMAP.  As a nit, the reference for IPv6 is incorrect.

Section 5.1 mentioned that the workshop looked at patents as a means 
to improve interoperability.  Are there any papers about the two 
sides of the argument?

Section 7 mentions that the role of the IAB (in respect to working 
group formation) consists of providing guidance to the IESG on which 
birds of a feather sessions should be held, review of proposed 
working group charters, and shepherding some work so that it can 
reach a suitable stage for standardization.  What is the role of the 
IAB in respect to technology adoption?  A protocol, as viewed by the 
IETF, is one part of the technology.  How does the IAB communicate 
that "big picture" to the average IETF participant?  How does the IAB 
reach out to governments?

Section 7.3 mentions that "As we considered work in the workshop, our 
partners such as ICANN and the RIRs can continue to play a role in 
encouraging deployment of protocols through their policies".  That's 
names and numbers.  Is it the view of members of the IAB (in an 
individual capacity) that these bodies can provide incentives for 
IPv6 adoption?

The reports mentions that IETF working groups could leverage graduate 
students in many universities around the world in helping review 
documents (drafts, RFCs etc.).  I personally do not think that it 
would help the review workload.  Anyway, what's the technology 
adoption angle here?

The questions which were asked recently is who takes (some) 
responsibility for the technology and how things are being done 
outside the IETF.  The report does not provide new light about 
that.  I did not find the report interesting as it discussed about 
the same old stuff and the conclusion is that the topics deserve 
further exploration.  The same conclusion could be reached if a 
similar workshop was organized next year.  The report does not 
discussion about transition in any way.  How does the IETF move from 
Technology X to Technology Y?  What are the impediments created by 
the IETF?  Does the IETF even have the ability to influence the 
deployment of the technology?

Regards,
S. Moonesamy 


From nobody Fri Apr 18 00:58:00 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DE601A02AD for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 00:57:57 -0700 (PDT)
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_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham
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 v9Tuv-QmPz01 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 00:57:51 -0700 (PDT)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.119]) by ietfa.amsl.com (Postfix) with ESMTP id 8715D1A02A2 for <ietf@ietf.org>; Fri, 18 Apr 2014 00:57:51 -0700 (PDT)
Received: from [193.109.255.147:25913] by server-15.bemta-14.messagelabs.com id 9B/1E-15813-AFAD0535; Fri, 18 Apr 2014 07:57:46 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-72.messagelabs.com!1397807866!11520342!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.11.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17824 invoked from network); 18 Apr 2014 07:57:46 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-4.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 18 Apr 2014 07:57:46 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.54]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Fri, 18 Apr 2014 08:57:46 +0100
From: <l.wood@surrey.ac.uk>
To: <sm+ietf@elandsys.com>, <iab@iab.org>
Date: Fri, 18 Apr 2014 08:57:46 +0100
Subject: RE: Internet Technology Adoption and Transition
Thread-Topic: Internet Technology Adoption and Transition
Thread-Index: Ac9azWZgTTZW+cRaQduZ94iznyK2RAADWPFx
Message-ID: <290E20B455C66743BE178C5C84F1240847E9989B8E@EXMB01CMS.surrey.ac.uk>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org>, <6.2.5.6.2.20140417215305.0dc8c008@resistor.net>
In-Reply-To: <6.2.5.6.2.20140417215305.0dc8c008@resistor.net>
Accept-Language: en-US, en-GB
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US, en-GB
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xoVjJip0-AYJhgROxG0VCB1gBTg
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 07:57:57 -0000

the correct url is
https://datatracker.ietf.org/doc/draft-iab-itat-report/
no trailing minus. why cite a broken url?

evolution in the smtp space? Um, DMARC?

for thoughts on http as an hourglass waist, see
http://personal.ee.surrey.ac.uk/Personal/L.Wood/publications/internet-draft=
s/draft-wood-dtnrg-http-dtn-delivery/lloyd-wood-turning-http-into-a-standal=
one-layer-ietf-75-tsvarea-slides.pdf
- it's a little hard to see http as a waist when it's so tightly coupled to=
 tcp. That is unlikely to change, as the benefits of uncoupling are for edg=
e cases.

many involved in the ietf, myself included, began contributing as grad stud=
ents. As with academic paper review, it's how the interested/enthusiastic/u=
npaid learn.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of S Moonesamy [sm+ietf@elands=
ys.com]
Sent: 18 April 2014 07:11
To: iab@iab.org
Cc: ietf@ietf.org
Subject: Internet Technology Adoption and Transition

Hello,
At 19:11 17-04-2014, IAB Chair wrote:
>This is a call for review of "Report from the IAB workshop on
>Internet Technology Adoption and Transition (ITAT)" prior to
>potential approval as an IAB stream RFC.
>
>The document is available for inspection here:
>https://datatracker.ietf.org/doc/draft-iab-itat-report-/

I read the report.  Section 2 mentions that SMTP and IMAP in the
applications space have continued to evolve.  I have not see much
evolution in the SMTP space.  I'll leave the relevant people to
comment about IMAP.  As a nit, the reference for IPv6 is incorrect.

Section 5.1 mentioned that the workshop looked at patents as a means
to improve interoperability.  Are there any papers about the two
sides of the argument?

Section 7 mentions that the role of the IAB (in respect to working
group formation) consists of providing guidance to the IESG on which
birds of a feather sessions should be held, review of proposed
working group charters, and shepherding some work so that it can
reach a suitable stage for standardization.  What is the role of the
IAB in respect to technology adoption?  A protocol, as viewed by the
IETF, is one part of the technology.  How does the IAB communicate
that "big picture" to the average IETF participant?  How does the IAB
reach out to governments?

Section 7.3 mentions that "As we considered work in the workshop, our
partners such as ICANN and the RIRs can continue to play a role in
encouraging deployment of protocols through their policies".  That's
names and numbers.  Is it the view of members of the IAB (in an
individual capacity) that these bodies can provide incentives for
IPv6 adoption?

The reports mentions that IETF working groups could leverage graduate
students in many universities around the world in helping review
documents (drafts, RFCs etc.).  I personally do not think that it
would help the review workload.  Anyway, what's the technology
adoption angle here?

The questions which were asked recently is who takes (some)
responsibility for the technology and how things are being done
outside the IETF.  The report does not provide new light about
that.  I did not find the report interesting as it discussed about
the same old stuff and the conclusion is that the topics deserve
further exploration.  The same conclusion could be reached if a
similar workshop was organized next year.  The report does not
discussion about transition in any way.  How does the IETF move from
Technology X to Technology Y?  What are the impediments created by
the IETF?  Does the IETF even have the ability to influence the
deployment of the technology?

Regards,
S. Moonesamy


From nobody Fri Apr 18 02:38:21 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A08971A02D5; Fri, 18 Apr 2014 02:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 1qmc2Iv3_E6j; Fri, 18 Apr 2014 02:38:16 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 1F0D61A0095; Fri, 18 Apr 2014 02:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1625; q=dns/txt; s=iport; t=1397813892; x=1399023492; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ykFJxg01yjpmcg96OyitluycaXNWhMs2sfg+HnqdycU=; b=ZgtY1TgtgcIVl+CuO9JdKix2RVaE/5ubTiD+pBfF9vu0ydyX0Pgf2o5G dWMRCp6z4awe6W+NSer+LiWPGYzQUfRrtaD0I09CfBbQCworLNcwqOlL/ W3fSzUnqR5OHb0dzgjStu3dSQhGFIrS7o7ssx7Lnr0vS2iq9b6R8gmuT2 E=;
X-IronPort-AV: E=Sophos;i="4.97,883,1389744000"; d="scan'208";a="18997933"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 18 Apr 2014 09:38:11 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3I9cB6J004547; Fri, 18 Apr 2014 09:38:11 GMT
Message-ID: <5350F283.1070907@cisco.com>
Date: Fri, 18 Apr 2014 11:38:11 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: adrian@olddog.co.uk, "'Black, David'" <david.black@emc.com>, tnadeau@lucidvision.com, zali@cisco.com, nobo@cisco.com, "'General Area Review Team'" <gen-art@ietf.org>
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
In-Reply-To: <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JfqM4BVpijU-KPk0PVilpBFW5hM
Cc: rtg-bfd@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 09:38:20 -0000

Hi Adrian,
> Hi David,
>
> Thanks for the review.
>
> To pick out one of your points:
>
>> This MIB contains many writable objects, so the authors should
>> take note of the IESG statement on writable MIB modules:
>>
>> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
>>
>> I did not see this mentioned in the shepherd writeup.  If the OPS Area
>> has not been consulted, I strongly suggest doing so during IETF Last
>> Call, e.g., starting with Benoit Claise (AD).
> The OPS Directorate and the MIB Doctors will have been alerted to this document
> by the last call and we can expect their comments.
>
> But this question was discussed between the AD and the authors, and the AD was
> unlikely to agree to sponsor the document if he felt it went against the IESG
> statement. Our discussion resulted in some reduction of writeable objects.
>
> I think there are several points to consider:
> 1. This document had already been completed and publication requested (i.e.
> shepherd write-up written) at the time of the IESG statement. It would be
> unreasonable to make the statement retrospective.
> 2. There are already various implementations in equipment (not just management
> stations) of proprietary modules approximating to this document and these
> support write-access.
> 3. This is a low-level component protocol of the sort that is used on dumber
> devices and that is an area where write-access is more common.
Thanks for the explanation. That makes sense to me.
This would be a useful addition to the writeup.

Regards, Benoit
>
> Cheers,
> Adrian
>
>
> .
>


From nobody Fri Apr 18 02:41:19 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 152DE1A02ED; Fri, 18 Apr 2014 02:41:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 l0KikSbirRsL; Fri, 18 Apr 2014 02:41:15 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 8EB151A02E6; Fri, 18 Apr 2014 02:41:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4493; q=dns/txt; s=iport; t=1397814071; x=1399023671; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=bjzfSWuLPBsKnl2k8kCmV3tXHQglzz7edw/goZL3YpI=; b=i3LqvAO0Jye998umRel+XO8l4895jWEp6XTwgfqR3ut9MibP8viqED2I 4SlRWtpPuJ6tIujeNW6Yq/DThuKTNwQ1SAiVevdq6nU65aSR2blC4e80Q xHpG/MrzwkX/1wR10KS/KBUxoBD+2zxQ9T/qgk4V5m3PRjYao2aiBdmke c=;
X-IronPort-AV: E=Sophos;i="4.97,883,1389744000"; d="scan'208";a="18999086"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 18 Apr 2014 09:41:10 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3I9f9m5007414; Fri, 18 Apr 2014 09:41:09 GMT
Message-ID: <5350F335.8020309@cisco.com>
Date: Fri, 18 Apr 2014 11:41:09 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: "Nobo Akiya (nobo)" <nobo@cisco.com>, "Sam K. Aldrin" <aldrin.ietf@gmail.com>
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NouwzU58XkSVKZI_sTxMCsTR0rQ
Cc: "ietf@ietf.org" <ietf@ietf.org>, "'Black, David'" <david.black@emc.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, 'General Area Review Team' <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 09:41:17 -0000

On 18/04/2014 04:17, Nobo Akiya (nobo) wrote:
> Hi Sam,
>
>> -----Original Message-----
>> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
>> Sent: Thursday, April 17, 2014 9:24 PM
>> To: Nobo Akiya (nobo)
>> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; adrian@olddog.co.uk; rtg-
>> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>>
>> Hi Nobo,
>> [sorry for the top post]
>>
>> Yes, this is an old MIB and was in existence for a long time.
>> My only concern is with the new extension MIB's. If the base MIB (this MIB)
>> has write access, future extension MIB's may be forced to support write-
>> access. And that is the painful part, where community at large has not
>> shown interest in developing write-access MIB's at IETF, lest
>> implementation.
>>
>> I want to re-iterate again, I am not objecting or proposing an alternative
>> option. Just wanted to get clarification, so that, we don't have to burn cycles
>> and do the exercise again, when we have to review these new extension
>> MIB's.
> That's a good point, it would be good to have this clarified for future work.
>
> IMO:
>
> For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if gets included in the charter) should look into NETCONF/YANG (i.e. not extension to the BFD base MIB).
>
> For currently chartered BFD tasks, the BFD WG should continue with writable MIB. Large part of that is the BFD base & MPLS MIBs which [painful] writable effort is mostly done already.
This is in essence what 
https://www.ietf.org/iesg/statement/writable-mib-module.html says.

Regards, Benoit.
>
> -Nobo
>
>> -sam
>>
>> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>>
>>> Hi Sam,
>>>
>>>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>>>> %sam - If this MIB allows write access, do you/WG anticipate, any
>>>> extension to the MIB should also provide write-access as well? For
>> example:
>>>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
>>>> this base MIB to support MPLS. It adds more confusion than solving
>>>> the issue as base MIB supports write-access, but augmented/ MIB
>> extension doesn't.
>>>>>> As the BFD MIB authors were not supportive of write-access objects
>>>>>> in
>>>> the MIBs, why to have them in the first place?
>>>>> As noted in earlier mailing list chatter, there is some support for
>>>>> write access in existing implementations.  Given the lack of
>>>>> significant detail when pressed for the name of such an
>>>>> implementation, I'm suspecting smaller vendor or internal
>>>>> implementation.  That's still sufficient to leave write available.
>>>>>
>>>>> Given that one of the original contexts of asking if we could remove
>>>>> write was whether IETF was being asked to provide such a thing for
>>>>> MPLS-TP with related impact on your extension MIB and the answer was
>>>>> "no", that shouldn't be the main criteria.
>>>> No. The context of my question is not related to MPLS-TP as such, but
>>>> write- access support in general.
>>>> I should have added 'clarification' in my earlier email.
>>>>> My suspicion is that if we were to ship the base MIB with writeable
>>>>> objects, we may be forced to consider similar things for the
>>>>> extension
>>>> MIB(s).
>>>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE
>>>> and BFD-MIB respectively,  with write-access. Had to do write-access
>>>> because of the reason you've mentioned above, which is base MIB. It
>>>> would be painful to publish/support write-access MIB's when there is
>>>> no clear interest. Hence my clarification question.
>>> This mentions three vendors wanting to implement MIB as writable.
>>>
>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>>>
>>> And one more vendor voicing for writable.
>>>
>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>>>
>>> I agree that defining & wording writable MIB is much more painful than all
>> read-only MIB. But above thread indicates the desire by multiple vendors to
>> implement writable BFD MIB. Therefore it does seem that there are
>> interests, and going forward with write-access will benefit the community.
>> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
>> those implementing them as just read-only.
>>> -Nobo
>>>
>>>> -sam
>>>>
>>>>> -- Jeff
> .
>


From nobody Fri Apr 18 03:13:02 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5AD1A0259 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 03:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 w8VADNbSjMne for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 03:12:53 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id 05C601A01F7 for <ietf@ietf.org>; Fri, 18 Apr 2014 03:12:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2458; q=dns/txt; s=iport; t=1397815969; x=1399025569; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=oLY1V1tCheU1nmy91+m0gOYUpAUjFK9kHU8UmzVxKeY=; b=J8HDePKJqY65sh6IppILAbmlv+aOO5aWLrA64y9By2MJltcjSuUzHKuT ksPhHv1myBPOu+vjwNHvSvfiY90Dj8S+J3eDlqtjcgB3ehblYwz6nXfFj Y2q92s1JrnpLamZDBM4+pZunvTzcsRfmcch5UITepoMLVpjQRvBIztlSv w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqEEAED6UFOtJssW/2dsb2JhbABag1XESIEzdIIlAQEBAwE4QAEQCxgJFg8JAwIBAgFFBgEMAQcBAYg1CA3MPxeOYgeEOAEDmG6GWIt3gzM7
X-IronPort-AV: E=Sophos;i="4.97,883,1389744000"; d="scan'208";a="19668205"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 18 Apr 2014 10:12:48 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3IACm4h025956; Fri, 18 Apr 2014 10:12:48 GMT
Message-ID: <5350FAA0.1050607@cisco.com>
Date: Fri, 18 Apr 2014 12:12:48 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, Andy Bierman <andy@yumaworks.com>, "George, Wes" <wesley.george@twcable.com>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com> <534FE1C3.3070103@cisco.com> <6.2.5.6.2.20140417112406.0b7c9b70@resistor.net>
In-Reply-To: <6.2.5.6.2.20140417112406.0b7c9b70@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VbnYGLEM9Qq3_Tp7bbCfPVamyk8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 10:12:58 -0000

Hi,
> Hi Benoit,
> At 07:14 17-04-2014, Benoit Claise wrote:
>> We discussed during the milestones during one of the last plenaries.
>
> Yes.
>
>> The discussion was around: the milestones are indications and not 
>> deadlines.
>> In Open Source project, these are deadlines.
>> In the IETF, I would love to find a middle ground between the two.
>> In the IETF, the only "deadlines" are the meetings, or to be more 
>> precise, the submission deadlines just before the meetings.
>
> Lisa used to send monthly progress reports.  It provided some 
> visibility into what was happening within the area.
>
> A milestone can be an estimate of when X can be completed.  I might 
> suggest one and the group decides whether everyone can target that 
> date and plan accordingly.  There are times when deadlines may be 
> needed as an effort can end up in failure.
>
>> Exactly, and we should understand why!
>> I like this tool: 
>> <http://www.arkko.com/tools/lifecycle/>http://www.arkko.com/tools/lifecycle/<draft-name>-timing.html
>> For example: 
>> <http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-interfaces-cfg-timing.html>http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-interfaces-cfg-timing.html
>> Where is the bottleneck? Is this a process issue? The 
>> authors/shepherd/IESG/RFC-editors?
>> I don't want to finger point, but understand what we should improve.
>
> Let's see. :-)  The shepherd write-up does not provide me with much 
> information.  There's three years from the first -00 to the latest 
> version of the draft.  The author activity looks okay. There is less 
> activity from the document shepherd (there is an explanation for 
> that).  There was a Last Call in April 2013.  The AD asked for a 
> revised I-D in May 2013.  There was another Last Call in December 
> 2013.  The IESG didn't like something in the draft and it took seven 
> months to address that.
>
> There's still the two and a half years.  There are seven months 
> between the date in the charter and the first Last Call.  It would 
> take some effort to figure out what happened during the first two 
> years.  It looks like the working group was the bottleneck.
Thanks.
I'm more after analyzing trend than inspecting this particular document.
For example, https://datatracker.ietf.org/iesg/discusses/ doesn't look 
like a very long list to me.

Regards, Benoit

>
> Regards,
> S. Moonesamy
> .
>


From nobody Fri Apr 18 04:51:24 2014
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 180EC1A01D9; Fri, 18 Apr 2014 04:51:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ticfNNMf88AU; Fri, 18 Apr 2014 04:51:17 -0700 (PDT)
Received: from lucidvision.com (lucidvision.com [72.71.250.34]) by ietfa.amsl.com (Postfix) with ESMTP id 747EA1A01BB; Fri, 18 Apr 2014 04:51:17 -0700 (PDT)
Received: from [192.168.1.112] (static-72-71-250-38.cncdnh.fast04.myfairpoint.net [72.71.250.38]) by lucidvision.com (Postfix) with ESMTP id ED2B9276E09A; Fri, 18 Apr 2014 07:51:12 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_CA1BA98C-0029-484D-835E-D8BB0151E3E9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <5350F335.8020309@cisco.com>
Date: Fri, 18 Apr 2014 07:51:11 -0400
Message-Id: <33B44E73-320B-4FC9-8438-E471F605F318@lucidvision.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com> <5350F335.8020309@cisco.com>
To: Benoit Claise <bclaise@cisco.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UZcr2iTlItoXmU6Y0p5BHyY_7xw
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, Farrel Adrian <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, General Area Review Team <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 11:51:22 -0000

--Apple-Mail=_CA1BA98C-0029-484D-835E-D8BB0151E3E9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Apr 18, 2014:5:41 AM, at 5:41 AM, Benoit Claise <bclaise@cisco.com> =
wrote:

> On 18/04/2014 04:17, Nobo Akiya (nobo) wrote:
>> Hi Sam,
>>=20
>>> -----Original Message-----
>>> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
>>> Sent: Thursday, April 17, 2014 9:24 PM
>>> To: Nobo Akiya (nobo)
>>> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; =
adrian@olddog.co.uk; rtg-
>>> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
>>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>>>=20
>>> Hi Nobo,
>>> [sorry for the top post]
>>>=20
>>> Yes, this is an old MIB and was in existence for a long time.
>>> My only concern is with the new extension MIB's. If the base MIB =
(this MIB)
>>> has write access, future extension MIB's may be forced to support =
write-
>>> access. And that is the painful part, where community at large has =
not
>>> shown interest in developing write-access MIB's at IETF, lest
>>> implementation.
>>>=20
>>> I want to re-iterate again, I am not objecting or proposing an =
alternative
>>> option. Just wanted to get clarification, so that, we don't have to =
burn cycles
>>> and do the exercise again, when we have to review these new =
extension
>>> MIB's.
>> That's a good point, it would be good to have this clarified for =
future work.
>>=20
>> IMO:
>>=20
>> For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if =
gets included in the charter) should look into NETCONF/YANG (i.e. not =
extension to the BFD base MIB).
>>=20
>> For currently chartered BFD tasks, the BFD WG should continue with =
writable MIB. Large part of that is the BFD base & MPLS MIBs which =
[painful] writable effort is mostly done already.
> This is in essence what =
https://www.ietf.org/iesg/statement/writable-mib-module.html says.
>=20
> Regards, Benoit.

	Yes, this is why we left the writable stuff in - and why I =
recently spent about 4 hours doing Adrian's edits around support of such =
things.  Lets please put the discussion around read-write to bed for =
these two modules as they clearly were well under way and complete by =
the time the statement came out.

	--Tom



>>=20
>> -Nobo
>>=20
>>> -sam
>>>=20
>>> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>>>=20
>>>> Hi Sam,
>>>>=20
>>>>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>>>>> %sam - If this MIB allows write access, do you/WG anticipate, =
any
>>>>> extension to the MIB should also provide write-access as well? For
>>> example:
>>>>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
>>>>> this base MIB to support MPLS. It adds more confusion than solving
>>>>> the issue as base MIB supports write-access, but augmented/ MIB
>>> extension doesn't.
>>>>>>> As the BFD MIB authors were not supportive of write-access =
objects
>>>>>>> in
>>>>> the MIBs, why to have them in the first place?
>>>>>> As noted in earlier mailing list chatter, there is some support =
for
>>>>>> write access in existing implementations.  Given the lack of
>>>>>> significant detail when pressed for the name of such an
>>>>>> implementation, I'm suspecting smaller vendor or internal
>>>>>> implementation.  That's still sufficient to leave write =
available.
>>>>>>=20
>>>>>> Given that one of the original contexts of asking if we could =
remove
>>>>>> write was whether IETF was being asked to provide such a thing =
for
>>>>>> MPLS-TP with related impact on your extension MIB and the answer =
was
>>>>>> "no", that shouldn't be the main criteria.
>>>>> No. The context of my question is not related to MPLS-TP as such, =
but
>>>>> write- access support in general.
>>>>> I should have added 'clarification' in my earlier email.
>>>>>> My suspicion is that if we were to ship the base MIB with =
writeable
>>>>>> objects, we may be forced to consider similar things for the
>>>>>> extension
>>>>> MIB(s).
>>>>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, =
MPLS-TE
>>>>> and BFD-MIB respectively,  with write-access. Had to do =
write-access
>>>>> because of the reason you've mentioned above, which is base MIB. =
It
>>>>> would be painful to publish/support write-access MIB's when there =
is
>>>>> no clear interest. Hence my clarification question.
>>>> This mentions three vendors wanting to implement MIB as writable.
>>>>=20
>>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>>>>=20
>>>> And one more vendor voicing for writable.
>>>>=20
>>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>>>>=20
>>>> I agree that defining & wording writable MIB is much more painful =
than all
>>> read-only MIB. But above thread indicates the desire by multiple =
vendors to
>>> implement writable BFD MIB. Therefore it does seem that there are
>>> interests, and going forward with write-access will benefit the =
community.
>>> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
>>> those implementing them as just read-only.
>>>> -Nobo
>>>>=20
>>>>> -sam
>>>>>=20
>>>>>> -- Jeff
>> .
>>=20
>=20
>=20


--Apple-Mail=_CA1BA98C-0029-484D-835E-D8BB0151E3E9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTURGvAAoJEPcO+I7eiUJZZdUP/2hj6JdK+vrnJ453vcz5vMtQ
hUDqYKBE+thw5IfQ8M8dzqEm0cCEn885BVskoq/VPSfbmeWFTDUhcuQKjY5Oaf2E
tAQZkr1erB3MxhI4iUr6on2pzHaNXfvJ3Q7pb16wK/mq+e7MILbNPYX3CdfpdKR5
LiJIAi40qA+1l2noIArF1kFc58HRqlZqj2tx51CVk0f4G/8TL+fT3kBcEa67QWdv
HTirCYJU+zyEBEZkA5YXWYQJZW98eXa+2ta8rdR4hJ8C2o9sRAwgxmPjrfldUPVg
DZkj99welxc4tAV1j7D3LrIuVYBrlM5SXXaeP90qVhWbLWlRI+B7oUB8L+QsT31e
KaLb10AY8W7y/OkwOEjkqMt41Udx7GhkCr8VAdOHVV+Nq0Zwl3tA7373odf48Xxl
DWkTyLdaZUJ1sj0oIEaWtYbmTowcpNW3ZRSob9GdLCgv9QYm4JQSPii1/2gCutMm
wiqN3Uwfn/Hi4BAy/IT3IUajQ9YCPzB18GrnEWTAiFlrAfqlzjKo+/8JX6d5BVxc
bVX0bWPVC/g61+ScskzqluSVXGgE+4dOr52/dHQ3/AJdrTdUT6kRHMGowW8KPP85
HvF+/+I4bjKrDrkAA2U9LIFmQedcf7KZ4EhMTSGY1wUWPXNkjDVwmRI8k8F1Ba2a
Vm3F1kdHtkHwB2M3H6sm
=AeIB
-----END PGP SIGNATURE-----

--Apple-Mail=_CA1BA98C-0029-484D-835E-D8BB0151E3E9--


From nobody Fri Apr 18 05:06:58 2014
Return-Path: <bclaise@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C05931A01F6; Fri, 18 Apr 2014 05:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.773
X-Spam-Level: 
X-Spam-Status: No, score=-9.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 bZXkzubpP6WY; Fri, 18 Apr 2014 05:06:50 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6B91A0208; Fri, 18 Apr 2014 05:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5179; q=dns/txt; s=iport; t=1397822806; x=1399032406; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=WMcgKt5iEVVOziy2T0Qu/vnY+NvLYvE0yk6xHct/scg=; b=DvcK+m+JKy2TbUZducgPC4glzQRmHCKUUID1pFs0yI7Vth6DUiRgvQaV D1YhdSRFveJARXZP7R5nd/sRxIOE3R9Dlxydz2qsozi7sGMPdBwyvVFZC grN2V16vzmQHTTDgjCDLRxWj9/YKIQCZ9qd31wU+eF1S7/GLtnjM3fTCv 0=;
X-IronPort-AV: E=Sophos;i="4.97,884,1389744000"; d="scan'208";a="14946174"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 18 Apr 2014 12:06:45 +0000
Received: from [10.60.67.86] (ams-bclaise-8915.cisco.com [10.60.67.86]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s3IC6i88025687; Fri, 18 Apr 2014 12:06:44 GMT
Message-ID: <53511554.2000402@cisco.com>
Date: Fri, 18 Apr 2014 14:06:44 +0200
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Thomas Nadeau <tnadeau@lucidvision.com>
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
References: <8D3D17ACE214DC429325B2B98F3AE712076C2EC24D@MX15A.corp.emc.com> <051b01cf5a87$b92a84d0$2b7f8e70$@olddog.co.uk> <33536B2D-46AF-4828-9C2E-0F2349A80E44@gmail.com> <20140417221850.GD29430@pfrc> <8BA1120C-3C89-4F73-A937-D7C118704553@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BDAE@xmb-aln-x01.cisco.com> <7B5FD180-D744-415B-AA0E-12EB11AF7245@gmail.com> <CECE764681BE964CBE1DFF78F3CDD3941E10BE1F@xmb-aln-x01.cisco.com> <5350F335.8020309@cisco.com> <33B44E73-320B-4FC9-8438-E471F605F318@lucidvision.com>
In-Reply-To: <33B44E73-320B-4FC9-8438-E471F605F318@lucidvision.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VYXKdgDMd6Gxd6Vj8kQf7wtS5SQ
Cc: "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>, Farrel Adrian <adrian@olddog.co.uk>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, General Area Review Team <gen-art@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 12:06:55 -0000

On 18/04/2014 13:51, Thomas Nadeau wrote:
> On Apr 18, 2014:5:41 AM, at 5:41 AM, Benoit Claise <bclaise@cisco.com> wrote:
>
>> On 18/04/2014 04:17, Nobo Akiya (nobo) wrote:
>>> Hi Sam,
>>>
>>>> -----Original Message-----
>>>> From: Sam K. Aldrin [mailto:aldrin.ietf@gmail.com]
>>>> Sent: Thursday, April 17, 2014 9:24 PM
>>>> To: Nobo Akiya (nobo)
>>>> Cc: Jeffrey Haas; ietf@ietf.org; 'Black, David'; adrian@olddog.co.uk; rtg-
>>>> bfd@ietf.org; Zafar Ali (zali); 'General Area Review Team'
>>>> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-17
>>>>
>>>> Hi Nobo,
>>>> [sorry for the top post]
>>>>
>>>> Yes, this is an old MIB and was in existence for a long time.
>>>> My only concern is with the new extension MIB's. If the base MIB (this MIB)
>>>> has write access, future extension MIB's may be forced to support write-
>>>> access. And that is the painful part, where community at large has not
>>>> shown interest in developing write-access MIB's at IETF, lest
>>>> implementation.
>>>>
>>>> I want to re-iterate again, I am not objecting or proposing an alternative
>>>> option. Just wanted to get clarification, so that, we don't have to burn cycles
>>>> and do the exercise again, when we have to review these new extension
>>>> MIB's.
>>> That's a good point, it would be good to have this clarified for future work.
>>>
>>> IMO:
>>>
>>> For new charters, IESG encourages NETCONF/YANG. This means S-BFD (if gets included in the charter) should look into NETCONF/YANG (i.e. not extension to the BFD base MIB).
>>>
>>> For currently chartered BFD tasks, the BFD WG should continue with writable MIB. Large part of that is the BFD base & MPLS MIBs which [painful] writable effort is mostly done already.
>> This is in essence what https://www.ietf.org/iesg/statement/writable-mib-module.html says.
>>
>> Regards, Benoit.
> 	Yes, this is why we left the writable stuff in - and why I recently spent about 4 hours doing Adrian's edits around support of such things.  Lets please put the discussion around read-write to bed for these two modules as they clearly were well under way and complete by the time the statement came out.
No disagreement.

Regards, B.
>
> 	--Tom
>
>
>
>>> -Nobo
>>>
>>>> -sam
>>>>
>>>> On Apr 17, 2014, at 6:04 PM, Nobo Akiya (nobo) wrote:
>>>>
>>>>> Hi Sam,
>>>>>
>>>>>>> On Thu, Apr 17, 2014 at 03:11:15PM -0700, Sam K. Aldrin wrote:
>>>>>>>> %sam - If this MIB allows write access, do you/WG anticipate, any
>>>>>> extension to the MIB should also provide write-access as well? For
>>>> example:
>>>>>> http://datatracker.ietf.org/doc/draft-ietf-bfd-mpls-mib/ augments
>>>>>> this base MIB to support MPLS. It adds more confusion than solving
>>>>>> the issue as base MIB supports write-access, but augmented/ MIB
>>>> extension doesn't.
>>>>>>>> As the BFD MIB authors were not supportive of write-access objects
>>>>>>>> in
>>>>>> the MIBs, why to have them in the first place?
>>>>>>> As noted in earlier mailing list chatter, there is some support for
>>>>>>> write access in existing implementations.  Given the lack of
>>>>>>> significant detail when pressed for the name of such an
>>>>>>> implementation, I'm suspecting smaller vendor or internal
>>>>>>> implementation.  That's still sufficient to leave write available.
>>>>>>>
>>>>>>> Given that one of the original contexts of asking if we could remove
>>>>>>> write was whether IETF was being asked to provide such a thing for
>>>>>>> MPLS-TP with related impact on your extension MIB and the answer was
>>>>>>> "no", that shouldn't be the main criteria.
>>>>>> No. The context of my question is not related to MPLS-TP as such, but
>>>>>> write- access support in general.
>>>>>> I should have added 'clarification' in my earlier email.
>>>>>>> My suspicion is that if we were to ship the base MIB with writeable
>>>>>>> objects, we may be forced to consider similar things for the
>>>>>>> extension
>>>>>> MIB(s).
>>>>>> Both, bfd-mpls and mpls-TP MIB's are extensions to base MIBs, MPLS-TE
>>>>>> and BFD-MIB respectively,  with write-access. Had to do write-access
>>>>>> because of the reason you've mentioned above, which is base MIB. It
>>>>>> would be painful to publish/support write-access MIB's when there is
>>>>>> no clear interest. Hence my clarification question.
>>>>> This mentions three vendors wanting to implement MIB as writable.
>>>>>
>>>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01382.html
>>>>>
>>>>> And one more vendor voicing for writable.
>>>>>
>>>>> http://www.ietf.org/mail-archive/web/rtg-bfd/current/msg01397.html
>>>>>
>>>>> I agree that defining & wording writable MIB is much more painful than all
>>>> read-only MIB. But above thread indicates the desire by multiple vendors to
>>>> implement writable BFD MIB. Therefore it does seem that there are
>>>> interests, and going forward with write-access will benefit the community.
>>>> And with *ReadOnlyCompliance defined, BFD MIB can also accommodate
>>>> those implementing them as just read-only.
>>>>> -Nobo
>>>>>
>>>>>> -sam
>>>>>>
>>>>>>> -- Jeff
>>> .
>>>
>>


From nobody Fri Apr 18 05:30:46 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC7011A021C for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 05:30:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 vhwRA9QSXGED for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 05:30:39 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 537B11A0220 for <ietf@ietf.org>; Fri, 18 Apr 2014 05:30:39 -0700 (PDT)
Received: (qmail 15456 invoked from network); 18 Apr 2014 12:30:34 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=3c5f.53511aea.k1404; bh=q02hhWESyovYFbBh/ccVLrYrfHy8oyPhdCMxvPx8THo=; b=Gved6T+S+fLuzbGFPH1IPetMoSoetI16fj4fDgdYVJUvHR07jv/aNC8oE9Te8ZOJlJlyl8bw2kilVHQuK7GU9jsLWqb73BF33Kay6wBn+Vrsg7CgBbw9jP795h7wK/6CsmliTEXeRfhpePtj5PnbwhluO6WBCh/31667Ji+DgdNaSmSo/A/cj8fWxBvO9U29g6rf28a+XIKAdNlCUm4exZ3CNw2aGCnk1UapzrAVhddU+OcU0VruDumhZM4ZYV74
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=3c5f.53511aea.k1404; bh=q02hhWESyovYFbBh/ccVLrYrfHy8oyPhdCMxvPx8THo=; b=VWb7NBqrSBKYt4J1nt0AJN2LdMjruTwPbMOrTQQ4WbJbbPLZlEeoP6SDcgCDU6vr2FYyfUp8H3msNsVMQV/J+msyCMFqtysFqjbxZpZcS+RMAHRtHN+Ib4COZGZhQWvDZDv7FkMTz2bgd12NelaMP1x6BOBOigJbfKfigA/gPU+C5u1z1a0nEULe3QGmBq8QTtgv4RDP3drPFZVubXeHG+toVqkkMpTsTWV/HiS2fapIDsWMDEL/h/7JtB9dDCmi
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 18 Apr 2014 12:30:34 -0000
Date: 18 Apr 2014 08:30:35 -0400
Message-ID: <alpine.BSF.2.00.1404180829280.3551@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Yoav Nir" <ynir.ietf@gmail.com>
Subject: Re: (DMARC) How a whitelist would work, was Why mailing lists
In-Reply-To: <29834711-2D38-4D7D-97FA-69CB602AC5C3@gmail.com>
References: <CE39F90A45FF0C49A1EA229FC9899B0507D45766@USCLES544.agna.amgreetings.com> <20140414214949.32126.qmail@joyce.lan> <CE39F90A45FF0C49A1EA229FC9899B0507D460CB@USCLES544.agna.amgreetings.com> <alpine.BSF.2.00.1404142150430.32657@joyce.lan> <CAL0qLwbPMm_i0fqNSGQPv=xZaiNASy=icsRNudaNJ_3PNtX3Og@mail.gmail.com> <alpine.BSF.2.00.1404151832460.38826@joyce.lan> <CAL0qLwZUptJVw85T2FjB2HRGoOvcOUHKiQXeadM0QE9BsFVM9w@mail.gmail.com> <CAKHUCzxpwS+nR9wRGOzU_83f7XabMr0pwB5x-MHrqM-28r80kw@mail.gmail.com> <CAKHUCzzw9mufrTCOBQOkRrZU6wOM21X8Y=FUEKf=qnzS9VESjA@mail.gmail.com> <alpine.BSF.2.00.1404161654430.2065@joyce.lan> <CAL0qLwYT_y5ksCP5DpHGXEK084zVg=6HfpJ2B2khkK7jDByZmQ@mail.gmail.com> <alpine.BSF.2.00.1404170008470.2194@joyce.lan> <9760.1397773072@sandelman.ca> <alpine.BSF.2.00.1404172008250.2116@joyce.lan> <29834711-2D38-4D7D-97FA-69CB602AC5C3@gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1604439040-1397824236=:3551"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lfDsZRgWObhohx3KMMOZQDbBnNI
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 12:30:44 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1604439040-1397824236=:3551
Content-Type: MULTIPART/MIXED; BOUNDARY="3825401791-883066916-1397824236=:3551"

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-883066916-1397824236=:3551
Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
Content-Transfer-Encoding: QUOTED-PRINTABLE

>> Yeah.  It's clear from the DMARC summary reports I'm getting that the bi=
g mail systems already have a pretty good idea of where the mailing lists a=
re,
>
> They know about big lists. Maybe even IETF lists. But do they know about =
sandelman.ca? Do they know about @irtf.org?

Based on the DMARC reports I get (which are quite useful, independent of=20
the policy stuff), I'm fairly sure they know about my tiny lists.

> I really don=E2=80=99t like specs that work well only for large companies=
=2E

Of course.  Who's suggesting that, other than perhaps Yahoo?

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
--3825401791-883066916-1397824236=:3551--
--3825401791-1604439040-1397824236=:3551
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIII7gYJKoZIhvcNAQcCoIII3zCCCNsCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBh8wggYbMIIFA6ADAgECAgMJWEYwDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xNDAzMTgxOTQ3NDdaFw0xNTAzMjAwMDU2MDBaMDoxGDAW
BgNVBAMMD2pvaG5sQHRhdWdoLmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxA
dGF1Z2guY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnMGH
52DBxB4jb86Sxi3VvgOjirvLveIVP7zvqxBDpJzxrF02wCYwnQuxi3S3U5ge
3iHihzhM9qP+N03frkr4KH6Spgec88YjMioVQStTQZcrogTdHweZOgT8tckg
HEmHCF8uHBjD0HbfDk+9zYFtaE3QPk5aGm02Id0fNNM5WmSQSxVwF0Ddryq5
vIU0AHbB/1kok1zJpwWA06SgHenlnYngnSpNWlOn+SxboiD28m2XTWDP5ULL
e1b040VtkQMzpuVXzAHWVQYQWUevJ4y8mrUsqAyGuYSb5pTU28D+NExVAYxn
WD94rzgBpkXgC4Xxcp3TmyfMaLMF4M9ef0nu+QIDAQABo4IC1TCCAtEwCQYD
VR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSpNAr06FueusUfmbDdecnZ1kznsTAfBgNVHSME
GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0
YXVnaC5jb20wggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIB
KjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5
LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3Vl
ZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJl
bWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25s
eSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0
aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmg
J4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYI
KwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRz
c2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRw
Oi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5j
YS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0G
CSqGSIb3DQEBCwUAA4IBAQC3OSsHtuc1se2JPbLqI1b31i0EER3UX6Ep2Zuy
FkACIpk/i8mPi0KIfMWWiDlNmqeQEq8308i0/2mVcMVdgKWIUMJdZb3CmNfs
3qtTlrdXXYXT7ZLjL6a1Bbh/lKUm35JYRH8zf3rqDbLkpiA92vc7uTQcbDay
1sQ4CSTvOWuq0CIwMXqJePhHf/runG7ndDuX2yFagHlxhsvn7raw5NQuu4Sj
ofwbNiszwkryB7ZYUxq2Pg2i1m2XlgMbNEfw8deAZOyHGKKGz25Ei1KvJofH
1izh0WDU+ueJum6RHm8/o/i53MbYZN4Il64aBD1HPqQow3jHQBhAc8XN85hH
csS2MYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZp
Y2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCVhGMAkGBSsOAwIaBQCggdgw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQw
NDE4MTIzMDM2WjAjBgkqhkiG9w0BCQQxFgQUa88L8ROfQhayR1OECYgxbY4y
Yd8weQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEW
MAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEggEAILvpJ0SoJcda9X9Uy6BrYF8ecFrhGoItnkB2/w+BrM9S0vri
hYOO0LkU+OLYivNtl7aVhLuhTd339lbloW8iavyDAO2sedUz2+4NN+yNLwXQ
oTXtgFKCpL1QTsgnZMhO28UJYX2Fx9MHOhKvOPzfa4S3IRs+lKDIsR3j2oPN
YGPMNB1hiTniNI7PAgYuMRhuuitJctC1UWF0RfgwA4ducPF5Jo4kfdQFxrXL
AWS6v9MtarBORz3+jLyGtb8AJqFurGKnmq9DJvLX1+8GCMEQk7ox4LeMdz0C
pFpDe3/n3HzRGH+eKja0HK5hfJq0+aFoLzncdVC65UadGuPtMq3ipA==

--3825401791-1604439040-1397824236=:3551--


From nobody Fri Apr 18 07:43:53 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7FB71A01BB; Fri, 18 Apr 2014 07:43:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 plWKq2p6OEUn; Fri, 18 Apr 2014 07:43:46 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BBB41A01B6; Fri, 18 Apr 2014 07:43:46 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.151.248]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3IEhSUJ020157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 18 Apr 2014 07:43:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1397832221; bh=fZ9LunEsDF0x30RseqQIy1Iv5b2TRrex+CO5luKAVqk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Xv7yKcDXgd8969ktDjZIjPFEUXLAnvVR6XZeRubNDQK/3fdWUio4kCbdb8ZEP+N09 yWN9rfpRSAtMqfoCGH/0FTwmKVwnyTYRjSMnV7HHxij5sqgS1OomAdxoVUKvPZS+wn rEYFV199IBgFZnRliXsPQp+4FMYKK/hmSRYSIHic=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1397832221; i=@elandsys.com; bh=fZ9LunEsDF0x30RseqQIy1Iv5b2TRrex+CO5luKAVqk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iuWaxlg3peP6YZ34kr2AOcvr1wHANxqtkrWnS0SMfZdD1h1P3D/5VjJz/F4BlSvO7 +lVUrcyiHt9CcYBshHBzIxUruxvqP+HCDy2hvl6JQCblQLfXN3qUPI/2rsuRCmVTQ+ XaGIGGyep/ea22YPOymWzMtBnnJ/k4+t2COdm40s=
Message-Id: <6.2.5.6.2.20140418054044.0cb13980@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 18 Apr 2014 06:41:13 -0700
To: l.wood@surrey.ac.uk, iab@iab.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: Internet Technology Adoption and Transition
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E9989B8E@EXMB01CMS.surre y.ac.uk>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org> <6.2.5.6.2.20140417215305.0dc8c008@resistor.net> <290E20B455C66743BE178C5C84F1240847E9989B8E@EXMB01CMS.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/q7AI4y18x7uV0kaX41ojAphuEHY
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 14:43:51 -0000

Hi Lloyd,
At 00:57 18-04-2014, l.wood@surrey.ac.uk wrote:
>the correct url is
>https://datatracker.ietf.org/doc/draft-iab-itat-report/
>no trailing minus. why cite a broken url?

I should have removed the URL instead of citing it.

>evolution in the smtp space? Um, DMARC?

I am reading "SMTP" narrowly and did not consider DMARC as part of the space.

 From 
<http://www.iab.org/wp-content/IAB-uploads/2013/06/itat-2013_submission_5.docx>http://www.iab.org/wp-content/IAB-uploads/2013/06/itat-2013_submission_5.docx 
examples of DNSSEC-based applications are mentioned and there is the following:

    "The DMARC wg is working on higher-level use of DKIM and SPF."

The technology for those two specifications is mostly related to DNS.

>for thoughts on http as an hourglass waist, see
>http://personal.ee.surrey.ac.uk/Personal/L.Wood/publications/internet-drafts/draft-wood-dtnrg-http-dtn-delivery/lloyd-wood-turning-http-into-a-standalone-layer-ietf-75-tsvarea-slides.pdf
>- it's a little hard to see http as a waist when it's so tightly 
>coupled to tcp. That is unlikely to change, as the benefits of 
>uncoupling are for edge cases.

Thanks for the URL.  I would say yes to the comment about tightly 
coupled.  I'd say that they are seen as the transport and you end up 
with other protocols being designed on top of that.

>many involved in the ietf, myself included, began contributing as 
>grad students. As with academic paper review, it's how the 
>interested/enthusiastic/unpaid learn.

Yes.

Regards,
S. Moonesamy 


From nobody Fri Apr 18 08:04:13 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C2A91A0152 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:04:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.774
X-Spam-Level: 
X-Spam-Status: No, score=-0.774 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 xMQSoP5yPDqA for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:04:06 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id EC27B1A01AF for <ietf@ietf.org>; Fri, 18 Apr 2014 08:04:05 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6S941AUJK0067VF@mauve.mrochek.com> for ietf@ietf.org; Fri, 18 Apr 2014 07:58:57 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6S7SNS3SW00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 18 Apr 2014 07:58:51 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6S93XQ9TI00004W@mauve.mrochek.com>
Date: Fri, 18 Apr 2014 07:47:22 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Thu, 17 Apr 2014 21:28:43 -0700" <5350A9FB.9010307@dougbarton.us>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oxzE5Ics99cRN8oKXIK0DPGkg0M
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:04:11 -0000

> On 04/17/2014 07:41 AM, ned+ietf@mauve.mrochek.com wrote:
> > I also find it particularly revealing that one of the arguments being
> > made here is along of the lines of, "Everything else has had to
> > change, why are those stodgy old mailing list thingies somehow
> > exempt?" Except that's not it at all - the approach was always
> > essentially, "We're going to screw you, how about you do X or Y to
> > mitigate the damage a little?" To which the answer, predictably, was
> > less than enthusiastic.

> Another way to look at this is that the IETF, which ostensibly is
> interested in "input from operators," received pretty clear "input" from
> the operators of the largest mail systems on the planet, and
> collectively stuck their fingers in their ears and sang "la la la la la,
> I can't hear you" because it didn't like what was being said.

... except that would be wildly incorrect. In particular, the "operator
community" consists of a lot more than just the proponents of DMARC. Many of
those other operators - including some of comparable size - are now struggling
to deal with the consequences of DMARC.

> The message was pretty clearly, "We think DMARC is valuable enough to us
> that we plan to deploy it even though it has the unfortunate side effect
> of causing problems for mailing lists."

Allow me to rephrase: "We think getting our commerical mail through is worth
sacrificing all sorts of personal mail functionality users depend on. And we
don't care who it hurts, including some shops as large or larger than we are."

> Rather than throwing up our
> hands and telling the DMARC folks that we refuse to work with them
> unless their solution solves the problem of our anachronistic use case
> that that constitutes only a tiny percentage of their overall traffic;

Again with the traffic size as justification for poor behavior. Not all
messages are created equal, and some functions have utility entirely
disproportionate to the amount of bandwidth they use.

> a more rational approach would have been to recognize that the tail is not
> going to wag the dog here and start working with mailing list authors to
> solve the problem of how to live in a world that includes DMARC.

And suppose that would have required some tweaks to DMARC and maybe even
DKIM to accomplish. What part of "no changes" is hard to understand?

> When people talk about how the IETF is out of touch with the operator
> community and increasingly irrelevant, this is exactly the kind of thing
> that they are talking about. We ignore this lesson at our peril.

Well, here we sort of agree. The IETF is indeed out of touch with the operator
community. But not because it fails to talk to the DMARC proponents - which it
actually does do - but rather because it fails to talk to lots of other
operators.

				Ned


From nobody Fri Apr 18 08:21:09 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C27141A03AE for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:21:05 -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, SPF_PASS=-0.001] autolearn=ham
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 OaRpHv1Qmsm2 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:21:01 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id D7A8D1A01AF for <ietf@ietf.org>; Fri, 18 Apr 2014 08:21:00 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id x12so602295wgg.18 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:20:55 -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:content-type; bh=943BlK5Ui662Pz9WBkdc8NU/5X/23w7glEDp1THibRQ=; b=e4adGdUFxt08wdvzN6WdZ6RCbk/1CM60022FHGwMotwKWwLynenzyetL2bV3wIDDPl TbTqvgxjgGYBzqtHmOpi9um3cQINcJRonK3PnWxLpgd2C+8FtFNO2tdPK/2zBaPZHMqE qNskwzuHJSrXAGvM+oZ4LsqoAZZdMy5H6X5yWYoaVjkCrbX1td1P//Sd9Z3qbT1h1okh FgJN4o7LP4ooIcEjqb8flvXa7jQbKbUbzlPz5PguWuj6KU419f1Gb/VbNuA9bXAN6SmO uFOzkbJleQEaYs0fG9nKUGYSSTNTlMudWehjOb/hTuJvvZLANWqCoBCn70+lGe0Cv0XJ pIVQ==
MIME-Version: 1.0
X-Received: by 10.180.78.41 with SMTP id y9mr2808356wiw.26.1397834455431; Fri, 18 Apr 2014 08:20:55 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Fri, 18 Apr 2014 08:20:55 -0700 (PDT)
In-Reply-To: <9451.1397772992@sandelman.ca>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca>
Date: Fri, 18 Apr 2014 08:20:55 -0700
Message-ID: <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Content-Type: multipart/alternative; boundary=f46d043894772bc3bb04f752b230
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/y2WWjlfUfupKQl1FFV7q8FsZyp8
Cc: Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:21:06 -0000

--f46d043894772bc3bb04f752b230
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 17, 2014 at 3:16 PM, Michael Richardson
<mcr+ietf@sandelman.ca>wrote:

> So, the bug is that Yahoo/DMARC/ are authenticating the From:, when it
> should
> really be authenticating the Sender:. DMARC should key it's policy from
> Sender: rather than From, and if it did that then:
>   1) we could leave the From: intact, which is what's good for the end
>      users.
>   2) the list would change the Sender:, which is what we would establish
>      the reputation of the list, not the From:
>   3) MUAs would compare the From: and Sender:, and if they differed,
>      could say useful things like:
>
>      "From: Mrex@sap.com via ietf@ietf.org".
>
> (I was also wondering this morning on my commute if a layer of
> message/rfc822
> added by the mailing list might be a useful interim hack)
>

http://tools.ietf.org/html/draft-kucherawy-dmarc-base-04#section-15.1

One of the key points about DMARC's design is that it's concerned
specifically with From:.  The reason is that the content of From: is what's
typically shown to the recipient by MUAs.  If DMARC keyed off Sender:
instead, then this would work:

MAIL FROM: haha@badguy.example.com

From: security@paypal.com
Sender: haha@badguy.example.com
DKIM-Signature: v=1; d=badguy.example.com; ...

If DMARC pays attention to Sender: in favor of From:, then this passes, but
what the user is shown that the message is from security@paypal.com with a
DMARC pass.  Not good.

Using Sender: as the authentication key was suggested and ultimately
abandoned during both DomainKeys (RFC 4870, the predecessor to DKIM) and
Sender-ID (RFC 4406, pretty much never implemented) for this sort of reason.

    > MUAs which are not implementing the rfc822/2822/5322 "on behalf of"
>     > semantics of a message that carries both From: and Sender: header
>     > fields ought to be FIXED.  Standards that build on rfc822/2822/5322
>     > and do not respect "on behalf of" semantics of messages with
>     > both "Sender:" and "From:" also need to be FIXED.
>

I don't believe that's standardized.  I'm also not sure we (the IETF) want
to enter into user space like MUAs, an area we have historically avoided
because we don't really have such expertise.

-MSK

--f46d043894772bc3bb04f752b230
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Apr 17, 2014 at 3:16 PM, Michael Richardson <span =
dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" target=3D"_blank">=
mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><=
div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">So, the bug is that Yahoo=
/DMARC/ are authenticating the From:, when it should<br>
really be authenticating the Sender:. DMARC should key it&#39;s policy from=
<br>
Sender: rather than From, and if it did that then:<br>
=C2=A0 1) we could leave the From: intact, which is what&#39;s good for the=
 end<br>
=C2=A0 =C2=A0 =C2=A0users.<br>
=C2=A0 2) the list would change the Sender:, which is what we would establi=
sh<br>
=C2=A0 =C2=A0 =C2=A0the reputation of the list, not the From:<br>
=C2=A0 3) MUAs would compare the From: and Sender:, and if they differed,<b=
r>
=C2=A0 =C2=A0 =C2=A0could say useful things like:<br>
<br>
=C2=A0 =C2=A0 =C2=A0&quot;From: <a href=3D"mailto:Mrex@sap.com">Mrex@sap.co=
m</a> via <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>&quot;.<br>
<br>
(I was also wondering this morning on my commute if a layer of message/rfc8=
22<br>
added by the mailing list might be a useful interim hack)<br></blockquote><=
div><br><a href=3D"http://tools.ietf.org/html/draft-kucherawy-dmarc-base-04=
#section-15.1">http://tools.ietf.org/html/draft-kucherawy-dmarc-base-04#sec=
tion-15.1</a><br>
<br></div>One of the key points about DMARC&#39;s design is that it&#39;s c=
oncerned specifically with From:.=C2=A0 The reason is that the content of F=
rom: is what&#39;s typically shown to the recipient by MUAs.=C2=A0 If DMARC=
 keyed off Sender: instead, then this would work:<br>
<div><br></div><div>MAIL FROM: <a href=3D"mailto:haha@badguy.example.com">h=
aha@badguy.example.com</a><br><br></div><div>From: <a href=3D"mailto:securi=
ty@paypal.com">security@paypal.com</a><br></div><div>Sender: <a href=3D"mai=
lto:haha@badguy.example.com">haha@badguy.example.com</a><br>
</div><div>DKIM-Signature: v=3D1; d=3D<a href=3D"http://badguy.example.com"=
>badguy.example.com</a>; ...<br><br></div>If DMARC pays attention to Sender=
: in favor of From:, then this passes, but what the user is shown that the =
message is from <a href=3D"mailto:security@paypal.com">security@paypal.com<=
/a> with a DMARC pass.=C2=A0 Not good.<br>
<br></div><div class=3D"gmail_quote">Using Sender: as the authentication ke=
y was suggested and ultimately abandoned during both DomainKeys (RFC 4870, =
the predecessor to DKIM) and Sender-ID (RFC 4406, pretty much never impleme=
nted) for this sort of reason.<br>
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=3D"">=C2=A0 =C2=A0 &gt; MUAs which are not implementing the rfc8=
22/2822/5322 &quot;on behalf of&quot;<br>
=C2=A0 =C2=A0 &gt; semantics of a message that carries both From: and Sende=
r: header<br>
=C2=A0 =C2=A0 &gt; fields ought to be FIXED. =C2=A0Standards that build on =
rfc822/2822/5322<br>
=C2=A0 =C2=A0 &gt; and do not respect &quot;on behalf of&quot; semantics of=
 messages with<br>
=C2=A0 =C2=A0 &gt; both &quot;Sender:&quot; and &quot;From:&quot; also need=
 to be FIXED.<br></div></blockquote><div><br></div><div>I don&#39;t believe=
 that&#39;s standardized.=C2=A0 I&#39;m also not sure we (the IETF) want to=
 enter into user space like MUAs, an area we have historically avoided beca=
use we don&#39;t really have such expertise.<br>
<br></div><div>-MSK<br> </div></div></div></div>

--f46d043894772bc3bb04f752b230--


From nobody Fri Apr 18 08:26:33 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B0C8B1A03BD for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 VUN_3254-yzX for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:26:28 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 36D9E1A0256 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:26:28 -0700 (PDT)
Received: (qmail 47083 invoked from network); 18 Apr 2014 15:26:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=b7ea.5351441f.k1404; bh=kP8+g2A06pZrvBUCu/E+jsNK7xEJYIWwQVeQB8Z6SgU=; b=SzYL6cGVDSDf2wHScfJCtsX2EcPmbSp23GxQ94pCoxQ3fHrSND0Ubek9p65hvQ8HPM+8mrLFimM5d+/HxXh7djlqhfW2V04GDlXl0XQ2l2LpZdjCWFP3xHKR8dz+FaOzkPRirsw7gpbcjPT4DShq4ntmQfP2qWy6reFtNasluaApb0mbN4xnZahZYpGYpnn1092H2NI1t/F0Vj5HzxQnW8a8bMrkr2f1vAyaXkCev7H5PwR5g020/8s9gSryDedh
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=b7ea.5351441f.k1404; bh=kP8+g2A06pZrvBUCu/E+jsNK7xEJYIWwQVeQB8Z6SgU=; b=UfqEZJ8RRWvTv2Z70LRaNVWSNDMpYfgFXSikxJ2IFPlsk8qTyGGMElDDwiO38rhCL7ZfuCwwfK3mCu5M+005vjiTTvMHlJJts+43oNDANNOzSO64Aqa56WgW/Xq7qX1DZVwgTVfTTVAmOfFl2VGtxq4jkrUt5Eqlutg+kUlK2vtNFUE4F31fGyIamX6gC9GkGdDcYIH9vpn2kE4418ZTMRR9d5olRqdfflXpLZovwPwWwcEUBcfzOaM/28wOOt7s
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 18 Apr 2014 15:26:23 -0000
Date: 18 Apr 2014 11:26:22 -0400
Message-ID: <alpine.BSF.2.00.1404181123260.4704@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: MULTIPART/signed; protocol="application/pkcs7-signature"; micalg=sha1; BOUNDARY="3825401791-1333165044-1397834783=:4704"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Gj-Zb_aghbS1AEdAyfSs6wgTZEA
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:26:32 -0000

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--3825401791-1333165044-1397834783=:4704
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

> Using Sender: as the authentication key was suggested and ultimately
> abandoned during both DomainKeys (RFC 4870, the predecessor to DKIM) and
> Sender-ID (RFC 4406, pretty much never implemented) for this sort of reason.

Yup.  The patent license didn't help, but the fundamental problem is that 
it didn't do what users needed it to do.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.
--3825401791-1333165044-1397834783=:4704
Content-Type: APPLICATION/pkcs7-signature; name=smime.p7s
Content-Transfer-Encoding: BASE64
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename=smime.p7s

MIII7gYJKoZIhvcNAQcCoIII3zCCCNsCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCBh8wggYbMIIFA6ADAgECAgMJWEYwDQYJKoZIhvcNAQELBQAw
gYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYD
VQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTAeFw0xNDAzMTgxOTQ3NDdaFw0xNTAzMjAwMDU2MDBaMDoxGDAW
BgNVBAMMD2pvaG5sQHRhdWdoLmNvbTEeMBwGCSqGSIb3DQEJARYPam9obmxA
dGF1Z2guY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAnMGH
52DBxB4jb86Sxi3VvgOjirvLveIVP7zvqxBDpJzxrF02wCYwnQuxi3S3U5ge
3iHihzhM9qP+N03frkr4KH6Spgec88YjMioVQStTQZcrogTdHweZOgT8tckg
HEmHCF8uHBjD0HbfDk+9zYFtaE3QPk5aGm02Id0fNNM5WmSQSxVwF0Ddryq5
vIU0AHbB/1kok1zJpwWA06SgHenlnYngnSpNWlOn+SxboiD28m2XTWDP5ULL
e1b040VtkQMzpuVXzAHWVQYQWUevJ4y8mrUsqAyGuYSb5pTU28D+NExVAYxn
WD94rzgBpkXgC4Xxcp3TmyfMaLMF4M9ef0nu+QIDAQABo4IC1TCCAtEwCQYD
VR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSpNAr06FueusUfmbDdecnZ1kznsTAfBgNVHSME
GDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAaBgNVHREEEzARgQ9qb2hubEB0
YXVnaC5jb20wggFMBgNVHSAEggFDMIIBPzCCATsGCysGAQQBgbU3AQIDMIIB
KjAuBggrBgEFBQcCARYiaHR0cDovL3d3dy5zdGFydHNzbC5jb20vcG9saWN5
LnBkZjCB9wYIKwYBBQUHAgIwgeowJxYgU3RhcnRDb20gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkwAwIBARqBvlRoaXMgY2VydGlmaWNhdGUgd2FzIGlzc3Vl
ZCBhY2NvcmRpbmcgdG8gdGhlIENsYXNzIDEgVmFsaWRhdGlvbiByZXF1aXJl
bWVudHMgb2YgdGhlIFN0YXJ0Q29tIENBIHBvbGljeSwgcmVsaWFuY2Ugb25s
eSBmb3IgdGhlIGludGVuZGVkIHB1cnBvc2UgaW4gY29tcGxpYW5jZSBvZiB0
aGUgcmVseWluZyBwYXJ0eSBvYmxpZ2F0aW9ucy4wNgYDVR0fBC8wLTAroCmg
J4YlaHR0cDovL2NybC5zdGFydHNzbC5jb20vY3J0dTEtY3JsLmNybDCBjgYI
KwYBBQUHAQEEgYEwfzA5BggrBgEFBQcwAYYtaHR0cDovL29jc3Auc3RhcnRz
c2wuY29tL3N1Yi9jbGFzczEvY2xpZW50L2NhMEIGCCsGAQUFBzAChjZodHRw
Oi8vYWlhLnN0YXJ0c3NsLmNvbS9jZXJ0cy9zdWIuY2xhc3MxLmNsaWVudC5j
YS5jcnQwIwYDVR0SBBwwGoYYaHR0cDovL3d3dy5zdGFydHNzbC5jb20vMA0G
CSqGSIb3DQEBCwUAA4IBAQC3OSsHtuc1se2JPbLqI1b31i0EER3UX6Ep2Zuy
FkACIpk/i8mPi0KIfMWWiDlNmqeQEq8308i0/2mVcMVdgKWIUMJdZb3CmNfs
3qtTlrdXXYXT7ZLjL6a1Bbh/lKUm35JYRH8zf3rqDbLkpiA92vc7uTQcbDay
1sQ4CSTvOWuq0CIwMXqJePhHf/runG7ndDuX2yFagHlxhsvn7raw5NQuu4Sj
ofwbNiszwkryB7ZYUxq2Pg2i1m2XlgMbNEfw8deAZOyHGKKGz25Ei1KvJofH
1izh0WDU+ueJum6RHm8/o/i53MbYZN4Il64aBD1HPqQow3jHQBhAc8XN85hH
csS2MYIClzCCApMCAQEwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZp
Y2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1h
cnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCVhGMAkGBSsOAwIaBQCggdgw
GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQw
NDE4MTUyNjIzWjAjBgkqhkiG9w0BCQQxFgQURr2OnYrbTifBU9chjLLX79fw
cOEweQYJKoZIhvcNAQkPMWwwajALBglghkgBZQMEASowCwYJYIZIAWUDBAEW
MAsGCWCGSAFlAwQBAjAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwDQYJKoZIhvcN
AQEBBQAEggEAIVm19vmtAznjF1xpQQT9bx6UGjZqE7q7UN8Yo8v/CUZXOGgo
KZW5HUt5ySfAqklRxA5lcoZvXU/EiwFGEUcae4OMrcDtPF48CPO98CL7Clab
Y7wAoF03k+ZXxzovhnY1NbXYIWzroO/QgR6eDoGx435kKvroELbiBQ0aIVA1
NGcK2VMMNdFgYrRqCO189UDVGPZkmN1ReIuzu+jikdX7iu96vbkbEcaHiHrN
/lB1QF5ZaYV72qzwLkYIHNdyzOvg0c813ucdix9WttIuFoomcNLcpfX3zV0M
CHJTt6ZbMHfIyMih+UW9skPsG0giwbkC+1hqXZxFQHWpEuvjEOZBvg==

--3825401791-1333165044-1397834783=:4704--


From nobody Fri Apr 18 08:28:47 2014
Return-Path: <tony.putman@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379BD1A0214; Thu, 17 Apr 2014 10:23:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 XrzxdEas0Ufi; Thu, 17 Apr 2014 10:23:22 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC301A0135; Thu, 17 Apr 2014 10:23:22 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s3HHNHN1025666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 17 Apr 2014 12:23:18 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s3HHNGs8019997 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 17 Apr 2014 19:23:16 +0200
Received: from FR711WXCHMBA01.zeu.alcatel-lucent.com ([169.254.1.223]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Thu, 17 Apr 2014 19:23:16 +0200
From: "PUTMAN, Tony (Tony)" <tony.putman@alcatel-lucent.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standard
Thread-Topic: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standard
Thread-Index: AQHPUER+0n62SMALMEq7nBB2qf17BpsWIUEw
Date: Thu, 17 Apr 2014 17:23:15 +0000
Message-ID: <14BE57EA00BC0C469E17B5AD698FE67766664CE4@FR711WXCHMBA01.zeu.alcatel-lucent.com>
References: <20140404202750.31367.2461.idtracker@ietfa.amsl.com>
In-Reply-To: <20140404202750.31367.2461.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cw-88M1TeS8eXeQyPCyLcrud-FU
X-Mailman-Approved-At: Fri, 18 Apr 2014 08:28:46 -0700
Cc: "ipsec@ietf.org" <ipsec@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Apr 2014 17:23:25 -0000

All,

In section 3.6 (top of page 94), there is the statement,
  "If multiple certificates
   are sent, the first certificate MUST contain the public key used to
   sign the AUTH payload."

"sign" should be "validate".

Regards,
Tony
--
Tony Putman
Alcatel-Lucent Technologies

-----Original Message-----
From: IPsec [mailto:ipsec-bounces@ietf.org] On Behalf Of The IESG
Sent: Friday, April 04, 2014 9:28 PM
To: IETF-Announce
Cc: ipsec@ietf.org
Subject: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt>=
 (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standard


The IESG has received a request from the IP Security Maintenance and
Extensions WG (ipsecme) to consider the following document:
- 'Internet Key Exchange Protocol Version 2 (IKEv2)'
  <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> as Internet Standard

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2014-04-18. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the
beginning of the Subject line to allow automated sorting.

Abstract


   This document describes version 2 of the Internet Key Exchange (IKE)
   protocol.  IKE is a component of IPsec used for performing mutual
   authentication and establishing and maintaining Security Associations
   (SAs).  This document replaces and updates RFC 5996, and includes all
   of the errata for it, and it is intended to update IKEv2 to be
   Internet Standard.




The file can be obtained via
http://datatracker.ietf.org/doc/draft-kivinen-ipsecme-ikev2-rfc5996bis/

IESG discussion can be tracked via
http://datatracker.ietf.org/doc/draft-kivinen-ipsecme-ikev2-rfc5996bis/ball=
ot/


No IPR declarations have been submitted directly on this I-D.


_______________________________________________
IPsec mailing list
IPsec@ietf.org
https://www.ietf.org/mailman/listinfo/ipsec


From nobody Fri Apr 18 08:41:23 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C93B21A03D7 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:41:19 -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, SPF_PASS=-0.001] autolearn=ham
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 TJFGhNJYKFBg for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:41:11 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) by ietfa.amsl.com (Postfix) with ESMTP id 2FFB71A03A1 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:41:11 -0700 (PDT)
Received: by mail-wi0-f180.google.com with SMTP id q5so835162wiv.7 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:41:06 -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:content-type; bh=5sFK6yw3OwqjITMtBPljd6QJwoL2lGqYE/XUsMJ8fD0=; b=LG9PKs/eTfMkMS2157YK1UMVGSv1J95erDWsbyIW6lb238j0MKKIOufQje9Wxr7yVs t6rhf4QTZcFlEQPu7FW8qLsaM+GcDB0QwC63EQVicaPKZ8i34sehApuHG0fs4WduuQbj Z7RKp03HbtsSLXY2Ix9qSbBUrD3yPfguMX5/+kwzt4tKycA6kczFwsMZUMtpA4rvDBkW VCyoB6jAa03mcFj41LZ3I2pnXPKlUq8M26Y6QLx89EGAK4LOJdcNgT3FEZyWAG/8+lJO TFzeFrCe8v+GB4/Quwpy78Qn/3ZJhzL6tLqYIsIUqQHkhfSpVhCTxQ4r/ogG5ALnSL6F 6hjg==
MIME-Version: 1.0
X-Received: by 10.194.60.146 with SMTP id h18mr14622765wjr.26.1397835666580; Fri, 18 Apr 2014 08:41:06 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Fri, 18 Apr 2014 08:41:06 -0700 (PDT)
In-Reply-To: <01P6S93XQ9TI00004W@mauve.mrochek.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com>
Date: Fri, 18 Apr 2014 08:41:06 -0700
Message-ID: <CAL0qLwbeouNWWAyanTdUHACLUds=5ZQcG0TMCW-AmMNmuE6qrw@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Content-Type: multipart/alternative; boundary=047d7b86dc405c6c5004f752faea
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yvJocfGED4cT-2fRfvio8cO9Fgg
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:41:20 -0000

--047d7b86dc405c6c5004f752faea
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 18, 2014 at 7:47 AM, <ned+ietf@mauve.mrochek.com> wrote:

>
>  The message was pretty clearly, "We think DMARC is valuable enough to us
>> that we plan to deploy it even though it has the unfortunate side effect
>> of causing problems for mailing lists."
>>
>
> Allow me to rephrase: "We think getting our commerical mail through is
> worth
> sacrificing all sorts of personal mail functionality users depend on. And
> we
> don't care who it hurts, including some shops as large or larger than we
> are."


I'm not so sure delivery is the primary goal.  Rather, "We're tired of the
fact that we are unable to control who generates mail that appear to come
from our domain(s), and it's hurting us" is how that should at least
start.  A tarnished domain name has repercussions beyond just delivery of
email.

-MSK

--047d7b86dc405c6c5004f752faea
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Apr 18, 2014 at 7:47 AM,  <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:ned+ietf@mauve.mrochek.com" target=3D"_blank">ned+ietf@mauv=
e.mrochek.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><br>
<div class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
The message was pretty clearly, &quot;We think DMARC is valuable enough to =
us<br>
that we plan to deploy it even though it has the unfortunate side effect<br=
>
of causing problems for mailing lists.&quot;<br>
</blockquote>
<br></div>
Allow me to rephrase: &quot;We think getting our commerical mail through is=
 worth<br>
sacrificing all sorts of personal mail functionality users depend on. And w=
e<br>
don&#39;t care who it hurts, including some shops as large or larger than w=
e are.&quot;</blockquote><div><br></div><div>I&#39;m not so sure delivery i=
s the primary goal.=C2=A0 Rather, &quot;We&#39;re tired of the fact that we=
 are unable to control who generates mail that appear to come from our doma=
in(s), and it&#39;s hurting us&quot; is how that should at least start.=C2=
=A0 A tarnished domain name has repercussions beyond just delivery of email=
.<br>
<br></div>-MSK<br></div></div></div>

--047d7b86dc405c6c5004f752faea--


From nobody Fri Apr 18 08:42:08 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D6B651A03CA for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:42:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 t9s6eu1A8SzP for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:42:02 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 7728E1A022A for <ietf@ietf.org>; Fri, 18 Apr 2014 08:42:02 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WbAvN-00035U-F9; Fri, 18 Apr 2014 15:41:57 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id CBD60580598; Fri, 18 Apr 2014 11:41:56 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397835716; bh=Lx+I59O3+Hq51CTG1aXLTzSkuljbY2ATc2WXgcCdKm0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=uYv3/EQGiHLRMy95Ss+DvcaDYEG9ervILlybFsN5lTGGZy/djJDjV5Xt2l66+a+P7 OlxRjAL56wVLw5if2h73dyuoVljObg8IZ/FrhssKUGRkwmq+xZ3n1fG5Rx8NQ0nrOv /4oHWT8iEe+si+keu8qV60viV44kLnY43uirdzzE=
Date: Fri, 18 Apr 2014 11:41:56 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
Message-ID: <20140418154156.GB31301@thunk.org>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gp3fPqE2d7ePaP2TQ1lvjNfJZt8
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:42:07 -0000

On Fri, Apr 18, 2014 at 08:20:55AM -0700, Murray S. Kucherawy wrote:
> 
> http://tools.ietf.org/html/draft-kucherawy-dmarc-base-04#section-15.1
> 
> One of the key points about DMARC's design is that it's concerned
> specifically with From:.  The reason is that the content of From: is what's
> typically shown to the recipient by MUAs.  If DMARC keyed off Sender:
> instead, then this would work:
> 
> MAIL FROM: haha@badguy.example.com
> 
> From: security@paypal.com
> Sender: haha@badguy.example.com
> DKIM-Signature: v=1; d=badguy.example.com; ...
> 
> If DMARC pays attention to Sender: in favor of From:, then this passes, but
> what the user is shown that the message is from security@paypal.com with a
> DMARC pass.  Not good.

So what happens if MUA's, because users don't want to see the "From: "
line when it's been reset to a mailing list address, ends up showing
the users what they want, which is the original sender of the mailing
list post?  It doesn't matter how or where we encode this information,
whether it's in a comment in the rewritten From: field, or in a
"X-Really-From: " header, or in the body of the message.  If there's a
convention, whether it is in a standard or de facto, there **will** be
cases when the users really want the original From header, and then
what will the DMARC promoters do then?

Try to ram through DMARC II that forces alignment of the
"X-Really-From: " header, or whatever else we end up using?

		  	     	      	      	  - Ted


From nobody Fri Apr 18 08:45:51 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 329461A0422 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:45:50 -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, SPF_PASS=-0.001] autolearn=ham
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 TGwgw2RIIcYC for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:45:49 -0700 (PDT)
Received: from mail-we0-x235.google.com (mail-we0-x235.google.com [IPv6:2a00:1450:400c:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id AF4841A038D for <ietf@ietf.org>; Fri, 18 Apr 2014 08:45:48 -0700 (PDT)
Received: by mail-we0-f181.google.com with SMTP id q58so1666353wes.40 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:45:44 -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:content-type; bh=MNnDf4ruf9p7dRsoMqR4iCfvf6fiuK0xwWKaWA+mSLE=; b=Wunl/MF6+qgAzKBQ8uMHEMBxfiuHeZX8fC8SKveFsDv2Hd4hkPffOKo7KKB6iz8y3q 8wkgm9e+1soWFwSqZfcTEdPe//ahcwU7STtEz9xjwVvvxYwcqjC/OUfUfVW046d1PT38 nCyAd1rwvOZnvfBjxz1B/u/VMpfPemS6eyBFBc2CTgCKGDj819bM7pGea4WvzbTxNw19 UHCpPxPzLCtZlXFWQ6wI6b4AVpYhtDNGLR6Mna3/s31FvwtXZr0Z8m9LgdaKTrrnKRzo wco2zpmyaW+uQZ2oM9DrQs3Zktx2k4YN1N1qYkxA7/W8cZB3tHVOe4UeQivULulr/qNN 18fw==
MIME-Version: 1.0
X-Received: by 10.180.76.146 with SMTP id k18mr2843415wiw.5.1397835944307; Fri, 18 Apr 2014 08:45:44 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Fri, 18 Apr 2014 08:45:44 -0700 (PDT)
In-Reply-To: <20140418013433.2763.qmail@joyce.lan>
References: <534ED376.8060303@bluepopcorn.net> <20140418013433.2763.qmail@joyce.lan>
Date: Fri, 18 Apr 2014 08:45:44 -0700
Message-ID: <CAL0qLwY4xVrPwABRhv90JSRF8wta0P5OCw_UWzVYOyUZk2-W4Q@mail.gmail.com>
Subject: Re: What I've been wondering about the DMARC problem
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=f46d04374995ea30ce04f7530aba
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/a2fsli3txdHfZf1NRK67lpsCoxc
Cc: Jim Fenton <fenton@bluepopcorn.net>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:45:50 -0000

--f46d04374995ea30ce04f7530aba
Content-Type: text/plain; charset=UTF-8

On Thu, Apr 17, 2014 at 6:34 PM, John Levine <johnl@taugh.com> wrote:

> >"If the RFC5322.From domain does not exist in the DNS, Mail Receivers
> >SHOULD direct the receiving SMTP server to reject the message."
>
> As far as I can tell, that bit of poor advice hasn't been implemented.
>

Why is that poor advice?  It's not uncommon for an MTA receiving mail to
confirm that the message is replyable, at least insofar as an A and MX are
available for whatever comes after the "@".

-MSK


>
> PS: I did a few experiments, and putting two addresses on the From:
> line works remarkably well to avoid inappropriate policy failures,
> e.g.
>
>  From: Marissa <marissam@yahoo.com>, foo-list@ietf.org
>  Subject: whatever
>  ...
>
>
Huh, interesting.  Likely accidental, alas.

-MSK

--f46d04374995ea30ce04f7530aba
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Thu, Apr 17, 2014 at 6:34 PM, John Levine <span dir=3D"=
ltr">&lt;<a href=3D"mailto:johnl@taugh.com" target=3D"_blank">johnl@taugh.c=
om</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">
<div class=3D"">&gt;&quot;If the RFC5322.From domain does not exist in the =
DNS, Mail Receivers<br>
&gt;SHOULD direct the receiving SMTP server to reject the message.&quot;<br=
>
<br>
</div>As far as I can tell, that bit of poor advice hasn&#39;t been impleme=
nted.<br></blockquote><div><br></div><div>Why is that poor advice?=C2=A0 It=
&#39;s not uncommon for an MTA receiving mail to confirm that the message i=
s replyable, at least insofar as an A and MX are available for whatever com=
es after the &quot;@&quot;.<br>
<br></div><div>-MSK<br>=C2=A0<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
PS: I did a few experiments, and putting two addresses on the From:<br>
line works remarkably well to avoid inappropriate policy failures,<br>
e.g.<br>
<br>
=C2=A0From: Marissa &lt;<a href=3D"mailto:marissam@yahoo.com">marissam@yaho=
o.com</a>&gt;, <a href=3D"mailto:foo-list@ietf.org">foo-list@ietf.org</a><b=
r>
=C2=A0Subject: whatever<br>
=C2=A0...<br>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Huh, interesting.=
=C2=A0 Likely accidental, alas.<br><br></div><div class=3D"gmail_extra">-MS=
K<br></div></div>

--f46d04374995ea30ce04f7530aba--


From nobody Fri Apr 18 08:48:35 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CAE91A0388 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:48:33 -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, SPF_PASS=-0.001] autolearn=ham
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 H4aL4wo7A3ED for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:48:29 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 77F8B1A0417 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:48:28 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id y13so1535734pdi.5 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:48:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=0cxYkysFTFGaChUuD2X47S8reOvfuYA5bheGUvdL7yA=; b=Qdpp1Qsx4UQhu+MFs45FpTUSQjBMfOkKR7URz77bmNkGouYy3/6xpslnmHwINXcm8K 04cdYkNrtS+obpooDERy9FxFVYutj98vU42i2ZDIGFI7ZlfpkriHOzI0QR5+HFQ0MYfj zfyoHyMcy6swFDHYHRXRMZU3OdjzPfVsHTaW4YsGG8oePdyOyAImhAqSfZ9x7gRSBY0t l0cPxIKeRyt/69j5qmR0kpxLUi+Y64vIAwzbyEkFYcpgRxOUqMkEhkyxHLJt1WCCUeyW +guShWEwOFD7nzwNWPxnIFAi4e16ToissfU6Soo61SDsHho8pId3buo3XSzewWbW+FmM Kjvg==
X-Received: by 10.68.240.99 with SMTP id vz3mr22629484pbc.93.1397836104604; Fri, 18 Apr 2014 08:48:24 -0700 (PDT)
Received: from dhcp150.priv.bungi.com (c-24-4-159-60.hsd1.ca.comcast.net. [24.4.159.60]) by mx.google.com with ESMTPSA id ha2sm60673627pbb.8.2014.04.18.08.48.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Apr 2014 08:48:23 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1BC6D4A8-3F90-47BD-A754-B74ABAC3F9AC"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: (DMARC) We've been here before, was Why mailing lists
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
Date: Fri, 18 Apr 2014 08:48:22 -0700
Message-Id: <865517EA-29BD-4A6A-B1A2-F4C7653745A6@gmail.com>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HRnwyLmyAmdQIhlyqiQgDkWz20g
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:48:33 -0000

--Apple-Mail=_1BC6D4A8-3F90-47BD-A754-B74ABAC3F9AC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Apr 18, 2014, at 8:20 AM, Murray S. Kucherawy <superuser@gmail.com> =
wrote:

> On Thu, Apr 17, 2014 at 3:16 PM, Michael Richardson =
<mcr+ietf@sandelman.ca> wrote:
> So, the bug is that Yahoo/DMARC/ are authenticating the From:, when it =
should
> really be authenticating the Sender:. DMARC should key it's policy =
from
> Sender: rather than From, and if it did that then:
>   1) we could leave the From: intact, which is what's good for the end
>      users.
>   2) the list would change the Sender:, which is what we would =
establish
>      the reputation of the list, not the From:
>   3) MUAs would compare the From: and Sender:, and if they differed,
>      could say useful things like:
>=20
>      "From: Mrex@sap.com via ietf@ietf.org".
>=20
> (I was also wondering this morning on my commute if a layer of =
message/rfc822
> added by the mailing list might be a useful interim hack)
>=20
> http://tools.ietf.org/html/draft-kucherawy-dmarc-base-04#section-15.1
>=20
> One of the key points about DMARC's design is that it's concerned =
specifically with From:.  The reason is that the content of From: is =
what's typically shown to the recipient by MUAs.  If DMARC keyed off =
Sender: instead, then this would work:
>=20
> MAIL FROM: haha@badguy.example.com
>=20
> From: security@paypal.com
> Sender: haha@badguy.example.com
> DKIM-Signature: v=3D1; d=3Dbadguy.example.com; ...
>=20
> If DMARC pays attention to Sender: in favor of From:, then this =
passes, but what the user is shown that the message is from =
security@paypal.com with a DMARC pass.  Not good.
>=20
> Using Sender: as the authentication key was suggested and ultimately =
abandoned during both DomainKeys (RFC 4870, the predecessor to DKIM) and =
Sender-ID (RFC 4406, pretty much never implemented) for this sort of =
reason.
>=20
>     > MUAs which are not implementing the rfc822/2822/5322 "on behalf =
of"
>     > semantics of a message that carries both From: and Sender: =
header
>     > fields ought to be FIXED.  Standards that build on =
rfc822/2822/5322
>     > and do not respect "on behalf of" semantics of messages with
>     > both "Sender:" and "From:" also need to be FIXED.
>=20
> I don't believe that's standardized.  I'm also not sure we (the IETF) =
want to enter into user space like MUAs, an area we have historically =
avoided because we don't really have such expertise.

Dear Murray,

Agreed.  The intent behind DMARC is to protect recipients wanting to =
trust specific =46rom header fields.   Not protecting them will cause =
customer loss for high value transactional domains.  Most just don't =
want the flood of spoofing reaching their inbox these high value domains =
attract.=20

Yahoo has had other problems where many of their accounts have become =
compromised.  Perhaps DMARC is also seen as a method to curb complaints =
caused by spoofed addresses so they can better address accounts actually =
compromised by leveraging DMARC feedback.  This would be a poor choice =
in my view.

Regards,
Douglas Otis

=20

>=20
> -MSK


--Apple-Mail=_1BC6D4A8-3F90-47BD-A754-B74ABAC3F9AC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Apr 18, 2014, at 8:20 AM, Murray S. =
Kucherawy &lt;<a =
href=3D"mailto:superuser@gmail.com">superuser@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr">On Thu, Apr 17, 2014 at 3:16 PM, Michael =
Richardson <span dir=3D"ltr">&lt;<a href=3D"mailto:mcr+ietf@sandelman.ca" =
target=3D"_blank">mcr+ietf@sandelman.ca</a>&gt;</span> wrote:<br><div =
class=3D"gmail_extra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">So, the =
bug is that Yahoo/DMARC/ are authenticating the From:, when it =
should<br>
really be authenticating the Sender:. DMARC should key it's policy =
from<br>
Sender: rather than From, and if it did that then:<br>
&nbsp; 1) we could leave the From: intact, which is what's good for the =
end<br>
&nbsp; &nbsp; &nbsp;users.<br>
&nbsp; 2) the list would change the Sender:, which is what we would =
establish<br>
&nbsp; &nbsp; &nbsp;the reputation of the list, not the From:<br>
&nbsp; 3) MUAs would compare the From: and Sender:, and if they =
differed,<br>
&nbsp; &nbsp; &nbsp;could say useful things like:<br>
<br>
&nbsp; &nbsp; &nbsp;"From: <a =
href=3D"mailto:Mrex@sap.com">Mrex@sap.com</a> via <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>".<br>
<br>
(I was also wondering this morning on my commute if a layer of =
message/rfc822<br>
added by the mailing list might be a useful interim =
hack)<br></blockquote><div><br><a =
href=3D"http://tools.ietf.org/html/draft-kucherawy-dmarc-base-04#section-1=
5.1">http://tools.ietf.org/html/draft-kucherawy-dmarc-base-04#section-15.1=
</a><br>
<br></div>One of the key points about DMARC's design is that it's =
concerned specifically with From:.&nbsp; The reason is that the content =
of From: is what's typically shown to the recipient by MUAs.&nbsp; If =
DMARC keyed off Sender: instead, then this would work:<br>
<div><br></div><div>MAIL FROM: <a =
href=3D"mailto:haha@badguy.example.com">haha@badguy.example.com</a><br><br=
></div><div>From: <a =
href=3D"mailto:security@paypal.com">security@paypal.com</a><br></div><div>=
Sender: <a =
href=3D"mailto:haha@badguy.example.com">haha@badguy.example.com</a><br>
</div><div>DKIM-Signature: v=3D1; d=3D<a =
href=3D"http://badguy.example.com/">badguy.example.com</a>; =
...<br><br></div>If DMARC pays attention to Sender: in favor of From:, =
then this passes, but what the user is shown that the message is from <a =
href=3D"mailto:security@paypal.com">security@paypal.com</a> with a DMARC =
pass.&nbsp; Not good.<br>
<br></div><div class=3D"gmail_quote">Using Sender: as the authentication =
key was suggested and ultimately abandoned during both DomainKeys (RFC =
4870, the predecessor to DKIM) and Sender-ID (RFC 4406, pretty much =
never implemented) for this sort of reason.<br>
<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=3D"">&nbsp; &nbsp; &gt; MUAs which are not implementing the =
rfc822/2822/5322 "on behalf of"<br>
&nbsp; &nbsp; &gt; semantics of a message that carries both From: and =
Sender: header<br>
&nbsp; &nbsp; &gt; fields ought to be FIXED. &nbsp;Standards that build =
on rfc822/2822/5322<br>
&nbsp; &nbsp; &gt; and do not respect "on behalf of" semantics of =
messages with<br>
&nbsp; &nbsp; &gt; both "Sender:" and "From:" also need to be =
FIXED.<br></div></blockquote><div><br></div><div>I don't believe that's =
standardized.&nbsp; I'm also not sure we (the IETF) want to enter into =
user space like MUAs, an area we have historically avoided because we =
don't really have such =
expertise.<br></div></div></div></div></blockquote><div><br></div><div>Dea=
r Murray,</div><div><br></div><div>Agreed. &nbsp;The intent behind DMARC =
is to protect recipients wanting to trust specific =46rom header fields. =
&nbsp; Not protecting them will cause customer loss for high value =
transactional domains. &nbsp;Most just don't want the flood of spoofing =
reaching their inbox these high value domains =
attract.&nbsp;</div><div><br></div><div>Yahoo has had other problems =
where many of their accounts have become compromised. &nbsp;Perhaps =
DMARC is also seen as a method to curb complaints caused by spoofed =
addresses so they can better address accounts actually compromised by =
leveraging DMARC feedback. &nbsp;This would be a poor choice in my =
view.</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div><div>&nbsp;</div><br><blockquote =
type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_extra"><div =
class=3D"gmail_quote"><div>
<br></div><div>-MSK<br> </div></div></div></div>
</blockquote></div><br></body></html>=

--Apple-Mail=_1BC6D4A8-3F90-47BD-A754-B74ABAC3F9AC--


From nobody Fri Apr 18 08:48:41 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 172AC1A042C for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:48:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_21=0.6, SPF_PASS=-0.001] autolearn=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 diI2psUJZ0wZ for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:48:36 -0700 (PDT)
Received: from mail-wg0-x231.google.com (mail-wg0-x231.google.com [IPv6:2a00:1450:400c:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 0595F1A03AE for <ietf@ietf.org>; Fri, 18 Apr 2014 08:48:35 -0700 (PDT)
Received: by mail-wg0-f49.google.com with SMTP id a1so644584wgh.20 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:48:31 -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:content-type; bh=dxCuQLf2n0IxTTsnYJHcTyIs0m59BlRTCBxFS5Jmu/s=; b=Nk9g7nT0rjfEpGR0c8lWx6NgSa9qi+ZbtB3bd0XKF+AXECMkfCZpoJwIBWolYzMZke FNe2IYErwVSoNOs8mogKs7vwvUKAIDSQlFwDd6gswx2KlwaXp+etMTrpsQ8nOEQlRArL tBzyq80cdlHeHmDS/kfgQBnFUPJ7xMP5rY2TDXxZF/ul0Zp6tmzjUKN0GNzeDQiDCcAd dJ31c7MD0ZH4eG7AAMSOENORc0XTAN5heXT4ZBwbQAo7i6q2FbaJOeAWSfrH/4jbiy3s bMHSxw/vYW7eYgr51kXX69Qp5VPCwkfwHm6UErDMSy6y3nEYNlLvoXvA8EV63ZfvqAce sGsQ==
MIME-Version: 1.0
X-Received: by 10.194.92.7 with SMTP id ci7mr17002836wjb.7.1397836111606; Fri, 18 Apr 2014 08:48:31 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Fri, 18 Apr 2014 08:48:31 -0700 (PDT)
In-Reply-To: <20140418154156.GB31301@thunk.org>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <20140418154156.GB31301@thunk.org>
Date: Fri, 18 Apr 2014 08:48:31 -0700
Message-ID: <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=089e01494602e2f8aa04f753148e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1-SBawBt-2tP1urqTtcXNw1PrpU
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:48:37 -0000

--089e01494602e2f8aa04f753148e
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 18, 2014 at 8:41 AM, Theodore Ts'o <tytso@mit.edu> wrote:

> So what happens if MUA's, because users don't want to see the "From: "
> line when it's been reset to a mailing list address, ends up showing
> the users what they want, which is the original sender of the mailing
> list post?  It doesn't matter how or where we encode this information,
> whether it's in a comment in the rewritten From: field, or in a
> "X-Really-From: " header, or in the body of the message.  If there's a
> convention, whether it is in a standard or de facto, there **will** be
> cases when the users really want the original From header, and then
> what will the DMARC promoters do then?
>
> Try to ram through DMARC II that forces alignment of the
> "X-Really-From: " header, or whatever else we end up using?
>

Any answer I give to that would be speculation.  How about this: If MUAs
evolve as a result of all of this, I would hope it's in a direction that
doesn't just create whack-a-mole for the problem DMARC is trying to solve.

-MSK

--089e01494602e2f8aa04f753148e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Apr 18, 2014 at 8:41 AM, Theodore Ts&#39;o <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:tytso@mit.edu" target=3D"_blank">tytso@mit=
.edu</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmai=
l_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">So what happens if MUA&#39;s=
, because users don&#39;t want to see the &quot;From: &quot;<br></div>
line when it&#39;s been reset to a mailing list address, ends up showing<br=
>
the users what they want, which is the original sender of the mailing<br>
list post? =C2=A0It doesn&#39;t matter how or where we encode this informat=
ion,<br>
whether it&#39;s in a comment in the rewritten From: field, or in a<br>
&quot;X-Really-From: &quot; header, or in the body of the message. =C2=A0If=
 there&#39;s a<br>
convention, whether it is in a standard or de facto, there **will** be<br>
cases when the users really want the original From header, and then<br>
what will the DMARC promoters do then?<br>
<br>
Try to ram through DMARC II that forces alignment of the<br>
&quot;X-Really-From: &quot; header, or whatever else we end up using?<br></=
blockquote><div><br></div><div>Any answer I give to that would be speculati=
on.=C2=A0 How about this: If MUAs evolve as a result of all of this, I woul=
d hope it&#39;s in a direction that doesn&#39;t just create whack-a-mole fo=
r the problem DMARC is trying to solve.<br>
<br></div><div>-MSK<br></div></div></div></div>

--089e01494602e2f8aa04f753148e--


From nobody Fri Apr 18 08:52:04 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 708591A042D for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:52:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 8oUL1uLQ4m1O for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 08:52:00 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 1F3661A0433 for <ietf@ietf.org>; Fri, 18 Apr 2014 08:52:00 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id B6B37CC0A8 for <ietf@ietf.org>; Fri, 18 Apr 2014 11:51:55 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 1s0OEX2O3wlM for <ietf@ietf.org>; Fri, 18 Apr 2014 11:51:47 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 08715CC09D for <ietf@ietf.org>; Fri, 18 Apr 2014 11:51:47 -0400 (EDT)
Message-ID: <53514A12.1040802@meetinghouse.net>
Date: Fri, 18 Apr 2014 11:51:46 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <CAL0qLwbeouNWWAyanTdUHACLUds=5ZQcG0TMCW-AmMNmuE6qrw@mail.gmail.com>
In-Reply-To: <CAL0qLwbeouNWWAyanTdUHACLUds=5ZQcG0TMCW-AmMNmuE6qrw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D-kAItzebPMkhGq65bGncgm4jZM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 15:52:03 -0000

Murray S. Kucherawy wrote:
> On Fri, Apr 18, 2014 at 7:47 AM, <ned+ietf@mauve.mrochek.com 
> <mailto:ned+ietf@mauve.mrochek.com>> wrote:
>
>
>         The message was pretty clearly, "We think DMARC is valuable
>         enough to us
>         that we plan to deploy it even though it has the unfortunate
>         side effect
>         of causing problems for mailing lists."
>
>
>     Allow me to rephrase: "We think getting our commerical mail
>     through is worth
>     sacrificing all sorts of personal mail functionality users depend
>     on. And we
>     don't care who it hurts, including some shops as large or larger
>     than we are."
>
>
> I'm not so sure delivery is the primary goal.  Rather, "We're tired of 
> the fact that we are unable to control who generates mail that appear 
> to come from our domain(s), and it's hurting us" is how that should at 
> least start.  A tarnished domain name has repercussions beyond just 
> delivery of email.
>

Given the amount of spam and other malicious mail that comes from real, 
honest-to-god, Yahoo accounts -- be it generated by spammers who obtain 
Yahoo accounts, or botnets that have obtained access to legitimate 
accounts -- perhaps Yahoo might have started closer to home in 
addressing the "tarnished brand" problem.

Pretty much the ONLY malicious mail, from Yahoo, that has ever made it 
through our spam filters, and onto any of our mailing lists, has been 
from compromised Yahoo accounts -- and that was BEFORE DMARC.

On the other hand, the only mail that ever seems to end up in my Yahoo 
mailbox (which I rarely check), is spam.

What Yahoo has just done is tarnished their brand by "breaking every 
email list in the world" - and causing pain to every one of their users 
who subscribes to mailing lists.

Kind of shooting yourself in the foot, if you ask me.  (Or blowing up 
yourself, along with your target.)

Miles Fidelman




-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Apr 18 09:03:11 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD191A043C for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 09:03:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 2z5dc34h3ABl for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 09:03:03 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 9F3FF1A015D for <ietf@ietf.org>; Fri, 18 Apr 2014 09:03:03 -0700 (PDT)
Received: (qmail 54179 invoked from network); 18 Apr 2014 16:02:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=d39e.53514cb3.k1404; bh=4fyDsN94dczhs3oEaiayUyloKc0EQ6bfabicVUcMQdw=; b=NIRGRlfa6NfZct+lqH/WvN7pYYZF2fEXpuglfkGFTxrZ+zviFzMQPfFrpJswRb+GZWf2e4C3OKy/VYvodlcQP6LvKE7Q1StY4GjKarfwiHzC3091lYxP8Q5rFfGfQ/CyQE+9rHnxMQEQRf1TJk3ttot6IJjGd7HowUScNLlF/qZbeXjKul9FCi6NSVCB189SWikajqSGB6yE/w23hXG/jBMGVqPhnDiVHtYzepbRC4QO818SESg+4DiMQ491wSp9
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=d39e.53514cb3.k1404; bh=4fyDsN94dczhs3oEaiayUyloKc0EQ6bfabicVUcMQdw=; b=Y8927JQsWnqFYYojqhgHjYbR1HCecSbWQrhfZ8rPnYHU5nC8vVTmSW12XM80qZJ1dAYEjLNfIXZnuAPUjkJM5vX06nl+7ecvXmWALKUr9aCOUO3YspPnojr9hpapG+f4N0tXSpYbgUmfCMrikpeRgJPKf9i7BY4OxDE6CKCLsWeuOogx3C1lfezayO6j5yWldeXFllkZnyChb25SOVeZz/hgtcwzBMfBo5I0tPO6WaPexPayw+lwO8SSAn0pqyKp
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 18 Apr 2014 16:02:59 -0000
Date: 18 Apr 2014 12:02:58 -0400
Message-ID: <alpine.BSF.2.00.1404181201460.4704@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
In-Reply-To: <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <20140418154156.GB31301@thunk.org> <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5FFYya3BPmg2Xf_uMxVB_GF2N6Y
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 16:03:09 -0000

> Any answer I give to that would be speculation.  How about this: If MUAs
> evolve as a result of all of this, I would hope it's in a direction that
> doesn't just create whack-a-mole for the problem DMARC is trying to solve.

That suggests it would be in the DMARC cartel's interest to avoid putting 
evolutionary pressure on MUAs to do things they won't like.  See you in 
ietf-822.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Fri Apr 18 09:12:44 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCE011A03C9 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 09:12:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 Fyfx1WHrZ58N for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 09:12:39 -0700 (PDT)
Received: from st11p02mm-asmtp002.mac.com (st11p02mm-asmtp002.mac.com [17.172.220.237]) by ietfa.amsl.com (Postfix) with ESMTP id 124941A0228 for <ietf@ietf.org>; Fri, 18 Apr 2014 09:12:38 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N4800JJBICNI350@st11p02mm-asmtp002.mac.com> for ietf@ietf.org; Fri, 18 Apr 2014 16:12:25 +0000 (GMT)
Subject: Re: What I've been wondering about the DMARC problem
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <5350344B.1000400@gmail.com>
Date: Fri, 18 Apr 2014 17:12:22 +0100
Message-id: <B433F153-C2E7-499C-9A9A-3C3D3783B2D6@me.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAKW6Ri5f5KZyJeL7RTG2T000Qd+t61KCofNmG2JZv+nKi94Uug@mail.gmail.com> <534C0078.3070808@meetinghouse.net> <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534C2262.1070507@meetinghouse.net> <CAL0qLwb5p_V3i-NGhKJZBeO0qKHm1xiAq1E3nYkBzVUAXkRPpQ@mail.gmail.com> <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <2478F2D1-2E08-45D7-86A2-36443959E272@me.com> <534EE9EA.9060403@gmail.com> <09B6AA22-9D1D-4EE4-AB27-2506A1E08EDA@me.com> <5350344B.1000400@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXWV4bG1oaGkdHB0lGUkdDRl5PWBoaGxEKTEMXGx0EGx0YBBIZBBsdEBseGh8 aEQpYTRdLEQptfhcaEQpMWRcbGhsbEQpZSRcRClleF2hjeREKQ04XSxsYGmJCH2lpHFxgGXhzB xljGxwbGHpjEQpYXBcZBBoEHQdNSx0SSEkcTAUbHQQbHRgEEhkEGx0QGx4aHxsRCl5ZF2FCXGV vEQpMRhdia2sRCkNaFxgbGQQbGBkEGxMYBBkaEQpEWBcZEQpESRcYEQpCRRdmUH1dH21kGgVIY xEKQk4XbHBgeUAdYlJpGmIRCkJMF2dJH215aRh+ckJNEQpCbBdlaGUYbU0cGENGThEKQkAXZxx nXkJkY1Ibc2QRCnBoF2hmYklyRWNbf1xCEQpwaBdlGUdLYVB8ZEZGThEKcGgXYHtaUHAbQllZa 0YRCnBoF21fT2llQnwZc2xaEQpwaBdsGGVSZGxhGkN7XREKcGwXa2ZOa0FlX2ZTZwERCnBMF2c aU2xAa0BtH0NaEQ==
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-18_01:2014-04-18,2014-04-18,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404180279
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/73NgN8vZSFKr6nQRTSZFXYBh2yM
Cc: Jim Fenton <fenton@bluepopcorn.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 16:12:41 -0000

On 17 Apr 2014, at 21:06, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
> On 17/04/2014 22:03, Sabahattin Gucukoglu wrote:
>> On 16 Apr 2014, at 21:36, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>> On 16/04/2014 18:58, Sabahattin Gucukoglu wrote:
>>>> On 15 Apr 2014, at 21:38, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>>>>> The mailman fix is worse than the disease. I think the .INVALID fix is
>>>>> much better, because Reply-all will still work.
>>>> Reply-all should still work with the Mailman fix; 
>>> It doesn't work *properly*. Firstly, this message wouldn't be sent
>>> to you with CC to the list, which is the correct semantic.
>>> If you weren't a subscriber, you would never see it. Secondly,
>> 
>> Sorry, but I appear to be confused.
>> 
>> The Reply-To: field is adjusted to be the author's address, 
> 
> Oh, OK. Most UAs will probably do what you describe, but I think
> there are exceptions. However, if I want to reply to the author
> alone, it's now the simple Reply that will fail me, because it
> will reply to the list. And in my mail folders, messages will
> all appear to come from the list; if I want to find the message
> that Sabahattin sent me two years ago, I can't, because my UA
> doesn't allow for searching on the Reply-To field.
> 
> It's still got very poor semantics.

Precisely right, and especially +1 to the concluding paragraph.

Is now the time to discuss making it policy for mail receivers to supply user-modifiable signer-domain bypasses?  Or is "Whitelisting" still considered a dirty word and "Not scalable"? :)

Cheers,
Sabahattin


From nobody Fri Apr 18 11:33:53 2014
Return-Path: <listsebby@me.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF42E1A03C9 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 11:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.601
X-Spam-Level: 
X-Spam-Status: No, score=-3.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham
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 RsGn3-veD5qO for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 11:33:48 -0700 (PDT)
Received: from nk11p04mm-asmtp002.mac.com (nk11p04mm-asmtp002.mac.com [17.158.236.237]) by ietfa.amsl.com (Postfix) with ESMTP id F38A91A0220 for <ietf@ietf.org>; Fri, 18 Apr 2014 11:33:47 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII
Received: from [192.168.1.6] (natbox.sabahattin-gucukoglu.com [213.123.192.30]) by nk11p04mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N4800IDWOW4K290@nk11p04mm-asmtp002.mac.com> for ietf@ietf.org; Fri, 18 Apr 2014 18:33:43 +0000 (GMT)
Subject: Re: What I've been wondering about the DMARC problem
From: Sabahattin Gucukoglu <listsebby@me.com>
In-reply-to: <20140417205332.GB4979@thunk.org>
Date: Fri, 18 Apr 2014 19:33:39 +0100
Message-id: <3B5401D0-13B3-4067-BC9D-15C4FBEB1224@me.com>
References: <CAKW6Ri5HWMaGMa_oLKwq5fzSUzJG=jAL1qojY1i6_tibEAxq8w@mail.gmail.com> <CAL0qLwaik1ft+AcACoc+kvKtCRt_gGvM6ov7c2yj_Uwyy3drNw@mail.gmail.com> <CAKW6Ri5_=GyOQijZMM+mqAoaEQzePGysBy9WVjN9yHO1zf3d2w@mail.gmail.com> <534C8F2B.9060903@gmail.com> <534D5516.7060902@dcrocker.net> <534D98CC.9080400@gmail.com> <2478F2D1-2E08-45D7-86A2-36443959E272@me.com> <534EE9EA.9060403@gmail.com> <09B6AA22-9D1D-4EE4-AB27-2506A1E08EDA@me.com> <5350344B.1000400@gmail.com> <20140417205332.GB4979@thunk.org>
To: Theodore Ts'o <tytso@mit.edu>
X-Mailer: Apple Mail (2.1510)
X-MANTSH: 1TEIXREEbG1oaGkdHB0lGUkdDRl5PWBoaHREKTEMXGx0EGx8SBBscHwQdGBAbHho fGhEKWE0XSxEKbX4XGhEKTFkXGxobGxEKWUkXEQpZXhdoY3kRCkNOF0sbGBpiTk0dWhl/ZBl4c wcZYxsSGRlCGBEKWFwXGQQaBB0HTUsdEkhJHEwFGx0EGx8SBBscHwQdGBAbHhofGxEKXlkXYUJ SeUMRCkxGF2xraxEKQ1oXGBsZBBsYGQQbExgEGRoRCkRYFx4RCkRJFxkRCkJFF2ZQfV0fbWQaB UhjEQpCThdscGB5QB1iUmkaYhEKQkwXZ0kfbXlpGH5yQk0RCkJsF2VoZRhtTRwYQ0ZOEQpCQBd nHGdeQmRjUhtzZBEKcGcXZkIdfUx8G0hmUEwRCnBoF29LAR9sSE99SX4bEQpwaBdgfmRGQUIcR 05JBREKcGgXZG9AYXx/f39BTmsRCnBoF2kZAUMaa39oY2dJEQpwaBdiH31tSUZneEh6aBEKcGw Xa2ZOa0FlX2ZTZwERCnBMF2xSGBkFWkVlWn9CEQ==
X-CLX-Spam: false
X-CLX-Score: 1011
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.96,1.0.14,0.0.0000 definitions=2014-04-18_01:2014-04-18,2014-04-18,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1402240000 definitions=main-1404180313
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VBzYzHlb4aiPjJl4zA-cPJSaLCY
Cc: Jim Fenton <fenton@bluepopcorn.net>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 18:33:50 -0000

On 17 Apr 2014, at 21:53, Theodore Ts'o <tytso@mit.edu> wrote:
> Suppose we made the mailing list software take the contents of the
> From field, and moved it to something like "X-Originally-From: ", and
> changed the From field to be "ietf@ietf.org".  That would be what the
> DMARC people would want, right?

Probably.  I mean, the alternative is to upgrade DMARC so it recognises the Originally-From field as From when it is present, but that would actually require maintaining compatibility with decades-old software which didn't know that From was the arbiter of all truth. :)

> Except then, a couple of years later, because users might actually
> want to find the message that was written by "Brian Carpenter", or
> "Sabahattin Gucukoglu", and not from "ietf@ietf.org", MUA's might
> start using the Originally-From field in the summary field, and start
> emphasizing the "Originally-From" from field in the UI.  At which
> point, the spammer/scammer/whatever could start forging the the
> "Originally-From" field, and then Lo!  There will be a DMARC II,
> demanding that "Originally-From" field be aligned with the From field,
> and we're right back to where we started.
> 
> It was the same argument about why a DKIM or DMARC couldn't just
> verify the Sender field, and call it a day.  The problem is that the
> From field is what people pay attention to.

Precisely.

Of course, if we're starting just now, there's something we could try differently: write it into Internet law that "NO MUA SHALL PROMOTE FOO TO THE DEFAULT HEADER DISPLAY", where "foo" is whatever we come up with.  Then MUA software, when presented with a known-good and known-aligned authentication results for From: could start displaying the green bar or whatever nonsense they come up with to signal that all is good, just so long as the part to the right of the @ is the domain the user thought the mail was really from.  However the MUA could continue to provide conveniences such as address autocomplete, address book memorisation, search or reply that were all using our new foo.

> And this is true of whatever solution we want to better support
> mailing lists.  Suppose the answer is to rewrite the from field to
> something like this:
> 
> 
> From: ietf-resend+brian.e.carpenter=gmail.com@ietf.org
> 
> Or this:
> 
> From: ietf@ietf.org (Originally from Brian E Carpenter: brian.e.carpenter@gmail.com)
> 
> It doesn't matter.  Eventually, the UA's will start emphasizing and
> parsing out the original From field information, because that's what
> people will want to be automatically added to their address book, and
> not ietf@ietf.org, and that's what they will want to see in their
> e-mail summary.  And then the DMARC folk will say, "Oh, Noes!
> Spammers and scammers and bears, oh my!  They are using this loophole
> to fool the naive user."  We must have DMARC II... and DMARC
> III.... and DMARC IV.... and it will never end.

Indeed.  Of course, none of that helps the mailing lists of yesteryear, I mean today.  Right now, we're all screwed without one of these hacks. :(

Cheers,
Sabahattin


From nobody Fri Apr 18 12:07:29 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A31D1A0468 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 12:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 rLgOMqATYE5s for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 12:07:22 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id BBBA61A043F for <ietf@ietf.org>; Fri, 18 Apr 2014 12:07:22 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WbE85-0004lx-5s; Fri, 18 Apr 2014 19:07:17 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 876A4580598; Fri, 18 Apr 2014 15:07:16 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397848036; bh=3xhPVP7yxLPN0Z3ZasFSghQJZhH7/eny4PdVwcrdRQ4=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=c/d3QZPG06Nlsi1E4gxdAyWTVxSfTbVD/hUC7id0Kqjb9qJ3Q+7NuW7P3j85wPQLI rZfKewadC19Q9c4yOUWHSO6tW2mholtPm5T1Yz47BHsC+rnlwXkuGIlEo4yGmQ4G7r 8XHia5m78aGw/qTrxoh6+2cYpXyI3L5/wHekBtH4=
Date: Fri, 18 Apr 2014 15:07:16 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
Message-ID: <20140418190716.GA23005@thunk.org>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <20140418154156.GB31301@thunk.org> <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tjO1C3wRkUGPteNGk_G1DqPzrL4
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 19:07:27 -0000

On Fri, Apr 18, 2014 at 08:48:31AM -0700, Murray S. Kucherawy wrote:
> 
> Any answer I give to that would be speculation.  How about this: If MUAs
> evolve as a result of all of this, I would hope it's in a direction that
> doesn't just create whack-a-mole for the problem DMARC is trying to solve.

And I'd suggest that if MUA's do evolve in that manner, maybe it's a
hint that the problem which the DMARC cheerleaders tried to sweep away
as "not a problem" really *is* a problem that users really care about.
And I would hope that in the future, they don't once again try to do
something that only meets their own parochial interests, and ignores
everyone elses' concerns.

					- Ted


From nobody Fri Apr 18 12:42:34 2014
Return-Path: <jari.arkko@piuha.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D0071A01F6 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 12:42:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.955
X-Spam-Level: 
X-Spam-Status: No, score=0.955 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.793] autolearn=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 9tvM7UUh9Kn7 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 12:42:28 -0700 (PDT)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 854591A01F0 for <ietf@ietf.org>; Fri, 18 Apr 2014 12:42:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 4F0152CCD0; Fri, 18 Apr 2014 22:42:23 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3Bgb86T_xTsu; Fri, 18 Apr 2014 22:42:22 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 3A2092CC48; Fri, 18 Apr 2014 22:42:22 +0300 (EEST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: I-D Action: draft-resnick-on-consensus-07.txt
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <20140415165420.12029.87582.idtracker@ietfa.amsl.com>
Date: Fri, 18 Apr 2014 22:42:21 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <A674FF20-F58C-446D-972E-13045EB67519@piuha.net>
References: <20140415165420.12029.87582.idtracker@ietfa.amsl.com>
To: "ietf@ietf.org List" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XB5sZ-Y-oEL_6nd-qHS5IP3MgJU
Cc: Pete Resnick <presnick@qti.qualcomm.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 19:42:30 -0000

> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
> ...
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-resnick-on-consensus/
>=20
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=3Ddraft-resnick-on-consensus-07

For your information, there is a new version of this draft. The IESG had =
approved it earlier, but there were some comments from the IESG reviews =
(particularly from Adrian) as well as from a review by Dave Crocker. I =
wanted to give Pete an opportunity to address those comments, and after =
discussion with me he and decided that these changes are appropriate. =
The main changes relate to pointing out that resolving disagreements is =
not the only thing that is needed for a successful consensus, and =
clarifying limitations of humming.

I plan to send the document to the RFC editor in the next week or so.

Jari


From nobody Fri Apr 18 13:10:44 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD2851A01BB for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:10:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 6nyIm8FNP0Yy for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:10:39 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.41]) by ietfa.amsl.com (Postfix) with ESMTP id 981541A002E for <ietf@ietf.org>; Fri, 18 Apr 2014 13:10:39 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES531.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Fri, 18 Apr 2014 16:10:35 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>, "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Subject: RE: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Thread-Topic: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Thread-Index: AQHPWr6uPWZYqrDS0kS5LDODiAAGHZsXeXikgABNUQCAAAUTQA==
Date: Fri, 18 Apr 2014 20:10:34 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D4DB17@USCLES544.agna.amgreetings.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <CAL0qLwbeouNWWAyanTdUHACLUds=5ZQcG0TMCW-AmMNmuE6qrw@mail.gmail.com>
In-Reply-To: <CAL0qLwbeouNWWAyanTdUHACLUds=5ZQcG0TMCW-AmMNmuE6qrw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.254.231]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_CE39F90A45FF0C49A1EA229FC9899B0507D4DB17USCLES544agnaam_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fu0MjXk915jUNuAqlC1dLtDHEa4
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 20:10:43 -0000

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D4DB17USCLES544agnaam_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

DQoNCkZyb206IGlldGYgW21haWx0bzppZXRmLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBP
ZiBNdXJyYXkgUy4gS3VjaGVyYXd5DQpTZW50OiBGcmlkYXksIEFwcmlsIDE4LCAyMDE0IDExOjQx
IEFNDQpUbzogbmVkK2lldGZAbWF1dmUubXJvY2hlay5jb20NCkNjOiBpZXRmDQpTdWJqZWN0OiBS
ZTogRE1BUkMgZnJvbSB0aGUgcGVyc3BlY3RpdmUgb2YgdGhlIGxpc3RhZG1pbiBvZiBhIGJ1bmNo
IG9mIFNNQUxMIGNvbW11bml0eSBsaXN0cw0KDQpPbiBGcmksIEFwciAxOCwgMjAxNCBhdCA3OjQ3
IEFNLCA8bmVkK2lldGZAbWF1dmUubXJvY2hlay5jb208bWFpbHRvOm5lZCtpZXRmQG1hdXZlLm1y
b2NoZWsuY29tPj4gd3JvdGU6DQoNClRoZSBtZXNzYWdlIHdhcyBwcmV0dHkgY2xlYXJseSwgIldl
IHRoaW5rIERNQVJDIGlzIHZhbHVhYmxlIGVub3VnaCB0byB1cw0KdGhhdCB3ZSBwbGFuIHRvIGRl
cGxveSBpdCBldmVuIHRob3VnaCBpdCBoYXMgdGhlIHVuZm9ydHVuYXRlIHNpZGUgZWZmZWN0DQpv
ZiBjYXVzaW5nIHByb2JsZW1zIGZvciBtYWlsaW5nIGxpc3RzLiINCg0KQWxsb3cgbWUgdG8gcmVw
aHJhc2U6ICJXZSB0aGluayBnZXR0aW5nIG91ciBjb21tZXJpY2FsIG1haWwgdGhyb3VnaCBpcyB3
b3J0aA0Kc2FjcmlmaWNpbmcgYWxsIHNvcnRzIG9mIHBlcnNvbmFsIG1haWwgZnVuY3Rpb25hbGl0
eSB1c2VycyBkZXBlbmQgb24uIEFuZCB3ZQ0KZG9uJ3QgY2FyZSB3aG8gaXQgaHVydHMsIGluY2x1
ZGluZyBzb21lIHNob3BzIGFzIGxhcmdlIG9yIGxhcmdlciB0aGFuIHdlIGFyZS4iDQoNCkknbSBu
b3Qgc28gc3VyZSBkZWxpdmVyeSBpcyB0aGUgcHJpbWFyeSBnb2FsLiAgUmF0aGVyLCAiV2UncmUg
dGlyZWQgb2YgdGhlIGZhY3QgdGhhdCB3ZSBhcmUgdW5hYmxlIHRvIGNvbnRyb2wgd2hvIGdlbmVy
YXRlcyBtYWlsIHRoYXQgYXBwZWFyIHRvIGNvbWUgZnJvbSBvdXIgZG9tYWluKHMpLCBhbmQgaXQn
cyBodXJ0aW5nIHVzIiBpcyBob3cgdGhhdCBzaG91bGQgYXQgbGVhc3Qgc3RhcnQuICBBIHRhcm5p
c2hlZCBkb21haW4gbmFtZSBoYXMgcmVwZXJjdXNzaW9ucyBiZXlvbmQganVzdCBkZWxpdmVyeSBv
ZiBlbWFpbC4NCk1IOiBJ4oCZbSBnb2luZyB0byBkaXNhZ3JlZSB3aXRoIE11cnJheSBvbiB0aGUg
ZmFjdCB0aGF0IGl04oCZcyBodXJ0aW5nIHVzLCB0aGUgY29tcGFueSBhcyB0aGUgbW90aXZhdG9y
LCBhdCBsZWFzdCBmcm9tIG15IHBlcnNwZWN0aXZlLiBJIHNlZSBpdCBhcyBwcmV2ZW50aW5nIGVu
ZCB1c2VycyBmcm9tIGdldHRpbmcgaHVydCBmcm9tIHRoaXMgcGFydGljdWxhciB1c2UgY2FzZSAo
ZGlyZWN0IGRvbWFpbiBhYnVzZSkuIFRoZSBmdXJ0aGVyIHdlIChmb3Igc29tZSBkZWZpbml0aW9u
IG9mIHdlKSBjYW4gcHVzaCBiYWQgYWN0b3JzIGZyb20gcmVhbGl0eSAoZnJvbSB0aGUgdXNlcnMg
cGVyc3BlY3RpdmUpLCB0aGUgbGVzcyBsaWtlbHkgdGhleSBhcmUgdG8gZmFsbCBmb3IgY2VydGFp
biB0eXBlcyBvZiBzb2NpYWwgZW5naW5lZXJpbmcuIEkgd291bGQgaHlwb3RoZXNpemUgdGhhdCBp
bmNyZWFzZWQgYWJ1c2Ugb2YgdGhlIHR5cGUgWWFob28gaGFzIGJlZW4gc2VlaW5nIG1heSBiZSBp
biBwYXJ0IGR1ZSB0byBpbmNyZWFzZWQgZGlmZmljdWx0eSBvbiB0aGUgcGFydCBvZiBtYWxpY2lv
dXMgaW5kaXZpZHVhbHMgaW4gYWJ1c2luZyBicmFuZHMgaW1wbGVtZW50aW5nIERNQVJDIHdpdGgg
cD1yZWplY3QuIFAgdG8gUCBtYWlsIGJlY29tZXMgaW5jcmVhc2luZ2x5IGF0dHJhY3RpdmUgYW5k
IHRoZSB1c2Ugb2Ygc3RvbGVuIGFkZHJlc3MgYm9va3Mgb3IgdXNlciBlbWFpbCBhZGRyZXNzZXMg
YW5kIGluZm9ybWF0aW9uIGZyb20gc3RvcmVkIG1lc3NhZ2VzIGNhbiBiZSB1c2VkIHRvIGltcHJv
dmUgdGhlIGVmZmVjdGl2ZW5lc3Mgb2YgdGhlIHNvY2lhbCBlbmdpbmVlci4NCg0KTWlrZQ0K

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D4DB17USCLES544agnaam_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNv
LXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5z
LXNlcmlmIjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAx
LjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRz
IHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1h
cCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRp
Zl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVy
cGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGluZzow
aW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7VGFob21hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9z
cGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IGlldGYgW21haWx0bzppZXRmLWJv
dW5jZXNAaWV0Zi5vcmddDQo8Yj5PbiBCZWhhbGYgT2YgPC9iPk11cnJheSBTLiBLdWNoZXJhd3k8
YnI+DQo8Yj5TZW50OjwvYj4gRnJpZGF5LCBBcHJpbCAxOCwgMjAxNCAxMTo0MSBBTTxicj4NCjxi
PlRvOjwvYj4gbmVkJiM0MztpZXRmQG1hdXZlLm1yb2NoZWsuY29tPGJyPg0KPGI+Q2M6PC9iPiBp
ZXRmPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBETUFSQyBmcm9tIHRoZSBwZXJzcGVjdGl2ZSBv
ZiB0aGUgbGlzdGFkbWluIG9mIGEgYnVuY2ggb2YgU01BTEwgY29tbXVuaXR5IGxpc3RzPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIEZyaSwg
QXByIDE4LCAyMDE0IGF0IDc6NDcgQU0sICZsdDs8YSBocmVmPSJtYWlsdG86bmVkJiM0MztpZXRm
QG1hdXZlLm1yb2NoZWsuY29tIiB0YXJnZXQ9Il9ibGFuayI+bmVkJiM0MztpZXRmQG1hdXZlLm1y
b2NoZWsuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEu
MHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJp
Z2h0OjBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxk
aXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0ND
Q0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21h
cmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIG1lc3NhZ2Ugd2FzIHBy
ZXR0eSBjbGVhcmx5LCAmcXVvdDtXZSB0aGluayBETUFSQyBpcyB2YWx1YWJsZSBlbm91Z2ggdG8g
dXM8YnI+DQp0aGF0IHdlIHBsYW4gdG8gZGVwbG95IGl0IGV2ZW4gdGhvdWdoIGl0IGhhcyB0aGUg
dW5mb3J0dW5hdGUgc2lkZSBlZmZlY3Q8YnI+DQpvZiBjYXVzaW5nIHByb2JsZW1zIGZvciBtYWls
aW5nIGxpc3RzLiZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPkFsbG93IG1lIHRvIHJlcGhyYXNlOiAmcXVvdDtXZSB0aGluayBnZXR0aW5nIG91ciBj
b21tZXJpY2FsIG1haWwgdGhyb3VnaCBpcyB3b3J0aDxicj4NCnNhY3JpZmljaW5nIGFsbCBzb3J0
cyBvZiBwZXJzb25hbCBtYWlsIGZ1bmN0aW9uYWxpdHkgdXNlcnMgZGVwZW5kIG9uLiBBbmQgd2U8
YnI+DQpkb24ndCBjYXJlIHdobyBpdCBodXJ0cywgaW5jbHVkaW5nIHNvbWUgc2hvcHMgYXMgbGFy
Z2Ugb3IgbGFyZ2VyIHRoYW4gd2UgYXJlLiZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1
b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206
MTIuMHB0Ij5JJ20gbm90IHNvIHN1cmUgZGVsaXZlcnkgaXMgdGhlIHByaW1hcnkgZ29hbC4mbmJz
cDsgUmF0aGVyLCAmcXVvdDtXZSdyZSB0aXJlZCBvZiB0aGUgZmFjdCB0aGF0IHdlIGFyZSB1bmFi
bGUgdG8gY29udHJvbCB3aG8gZ2VuZXJhdGVzIG1haWwgdGhhdCBhcHBlYXIgdG8gY29tZSBmcm9t
IG91ciBkb21haW4ocyksIGFuZCBpdCdzIGh1cnRpbmcgdXMmcXVvdDsgaXMgaG93IHRoYXQgc2hv
dWxkDQogYXQgbGVhc3Qgc3RhcnQuJm5ic3A7IEEgdGFybmlzaGVkIGRvbWFpbiBuYW1lIGhhcyBy
ZXBlcmN1c3Npb25zIGJleW9uZCBqdXN0IGRlbGl2ZXJ5IG9mIGVtYWlsLjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVv
dDs7Y29sb3I6IzFGNDk3RCI+TUg6IEnigJltIGdvaW5nIHRvIGRpc2FncmVlIHdpdGggTXVycmF5
IG9uIHRoZSBmYWN0IHRoYXQgaXTigJlzIGh1cnRpbmcgdXMsIHRoZSBjb21wYW55IGFzIHRoZSBt
b3RpdmF0b3IsIGF0IGxlYXN0IGZyb20gbXkgcGVyc3BlY3RpdmUuIEkgc2VlIGl0IGFzIHByZXZl
bnRpbmcgZW5kDQogdXNlcnMgZnJvbSBnZXR0aW5nIGh1cnQgZnJvbSB0aGlzIHBhcnRpY3VsYXIg
dXNlIGNhc2UgKGRpcmVjdCBkb21haW4gYWJ1c2UpLiBUaGUgZnVydGhlciB3ZSAoZm9yIHNvbWUg
ZGVmaW5pdGlvbiBvZiB3ZSkgY2FuIHB1c2ggYmFkIGFjdG9ycyBmcm9tIHJlYWxpdHkgKGZyb20g
dGhlIHVzZXJzIHBlcnNwZWN0aXZlKSwgdGhlIGxlc3MgbGlrZWx5IHRoZXkgYXJlIHRvIGZhbGwg
Zm9yIGNlcnRhaW4gdHlwZXMgb2Ygc29jaWFsIGVuZ2luZWVyaW5nLg0KIEkgd291bGQgaHlwb3Ro
ZXNpemUgdGhhdCBpbmNyZWFzZWQgYWJ1c2Ugb2YgdGhlIHR5cGUgWWFob28gaGFzIGJlZW4gc2Vl
aW5nIG1heSBiZSBpbiBwYXJ0IGR1ZSB0byBpbmNyZWFzZWQgZGlmZmljdWx0eSBvbiB0aGUgcGFy
dCBvZiBtYWxpY2lvdXMgaW5kaXZpZHVhbHMgaW4gYWJ1c2luZyBicmFuZHMgaW1wbGVtZW50aW5n
IERNQVJDIHdpdGggcD1yZWplY3QuIFAgdG8gUCBtYWlsIGJlY29tZXMgaW5jcmVhc2luZ2x5IGF0
dHJhY3RpdmUgYW5kIHRoZQ0KIHVzZSBvZiBzdG9sZW4gYWRkcmVzcyBib29rcyBvciB1c2VyIGVt
YWlsIGFkZHJlc3NlcyBhbmQgaW5mb3JtYXRpb24gZnJvbSBzdG9yZWQgbWVzc2FnZXMgY2FuIGJl
IHVzZWQgdG8gaW1wcm92ZSB0aGUgZWZmZWN0aXZlbmVzcyBvZiB0aGUgc29jaWFsIGVuZ2luZWVy
LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+TWlr
ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D4DB17USCLES544agnaam_--


From nobody Fri Apr 18 13:15:20 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98BAE1A01BB for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:15:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_21=0.6, SPF_PASS=-0.001] autolearn=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 HeInXhu0-ftH for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:15:09 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 707B91A0139 for <ietf@ietf.org>; Fri, 18 Apr 2014 13:15:09 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id hm4so1056533wib.8 for <ietf@ietf.org>; Fri, 18 Apr 2014 13:15:05 -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:content-type; bh=JeE+sMXEIXJq4P224JtCi8nmjj+3VNbagHPUM85ypbw=; b=BgnIW8LMubvPVG8DHCe3C5Z9REAy5Wps1UHuZ1IuD23OAdJztNNnxs3hjztz4NMbh3 W00De+8IwNxHyxqNqAt3tkJD+bmGsjgOi+b814V4qh43k2g4sZtV3RDRtCcD/sTLXjRT Bsp5hRme+tr65JHlRsjTfSCtkdvqQEMeVM4c6Y0GXu1UYp2NOKDd1pwIgv9XJcUM9mxK Y88Zb0AiPXdGvze8pSaTn7HV2LNLe4Wk3DWaxMAeJ9XgLiTgPAQzgZTKXHd4QLBL9hfi DdDTeidgj02SZbsJtEubxQNRKe9f+UcnwVYPs4JnN1abtQNdbrrJ/mtHx2eoeorZTrGr j1IQ==
MIME-Version: 1.0
X-Received: by 10.180.106.132 with SMTP id gu4mr3712175wib.26.1397852104921; Fri, 18 Apr 2014 13:15:04 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Fri, 18 Apr 2014 13:15:04 -0700 (PDT)
In-Reply-To: <20140418190716.GA23005@thunk.org>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <20140418154156.GB31301@thunk.org> <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com> <20140418190716.GA23005@thunk.org>
Date: Fri, 18 Apr 2014 13:15:04 -0700
Message-ID: <CAL0qLwYd9aACZ1abcuBMXO6RVJYn0uMnquAbig8oLfVnJVJoog@mail.gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=e89a8f3babd329999704f756ce27
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YjV9_GF9hh_dr-b3T1ShnPAp52g
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 20:15:10 -0000

--e89a8f3babd329999704f756ce27
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 18, 2014 at 12:07 PM, Theodore Ts'o <tytso@mit.edu> wrote:

> And I'd suggest that if MUA's do evolve in that manner, maybe it's a
> hint that the problem which the DMARC cheerleaders tried to sweep away
> as "not a problem" really *is* a problem that users really care about.
> And I would hope that in the future, they don't once again try to do
> something that only meets their own parochial interests, and ignores
> everyone elses' concerns.
>

There are some rather broad brush strokes here, and I'm running out of
steam trying to keep the record straight.  I'll try once more:

As John and others have already said, DMARC works fine for specific use
cases.  It's already been in use by other large operators like Bank of
America, PayPal, Facebook, and others for quite some time, with no visible
impact.  The results for them have been very positive.  Google also has it
turned on part-way for the domain their employees use.

The difference here is that Yahoo has users that send mail where those
others do not.

-MSK

--e89a8f3babd329999704f756ce27
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Apr 18, 2014 at 12:07 PM, Theodore Ts&#39;o <span =
dir=3D"ltr">&lt;<a href=3D"mailto:tytso@mit.edu" target=3D"_blank">tytso@mi=
t.edu</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gma=
il_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">And I&#39;d suggest that if MUA&#39;s do evo=
lve in that manner, maybe it&#39;s a<br>
hint that the problem which the DMARC cheerleaders tried to sweep away<br>
as &quot;not a problem&quot; really *is* a problem that users really care a=
bout.<br>
And I would hope that in the future, they don&#39;t once again try to do<br=
>
something that only meets their own parochial interests, and ignores<br>
everyone elses&#39; concerns.<br></blockquote><div><br></div><div>There are=
 some rather broad brush strokes here, and I&#39;m running out of steam try=
ing to keep the record straight.=C2=A0 I&#39;ll try once more:<br><br></div=
>
<div>As John and others have already said, DMARC works fine for specific us=
e cases.=C2=A0 It&#39;s already been in use by other large operators like B=
ank of America, PayPal, Facebook, and others for quite some time, with no v=
isible impact.=C2=A0 The results for them have been very positive.=C2=A0 Go=
ogle also has it turned on part-way for the domain their employees use.<br>
<br>The difference here is that Yahoo has users that send mail where those =
others do not.<br><br></div><div>-MSK<br></div></div></div></div>

--e89a8f3babd329999704f756ce27--


From nobody Fri Apr 18 13:29:02 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 617381A024F for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:29:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.573
X-Spam-Level: 
X-Spam-Status: No, score=-1.573 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=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 uRUZZWDScwB7 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:28:59 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id A442E1A002E for <ietf@ietf.org>; Fri, 18 Apr 2014 13:28:59 -0700 (PDT)
Received: from tytso by imap.thunk.org with local (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WbFP1-0005ES-Pe; Fri, 18 Apr 2014 20:28:51 +0000
Date: Fri, 18 Apr 2014 20:28:51 +0000
From: tytso@mit.edu
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
Message-ID: <20140418202851.GD13642@thunk.org>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <20140418154156.GB31301@thunk.org> <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com> <20140418190716.GA23005@thunk.org> <CAL0qLwYd9aACZ1abcuBMXO6RVJYn0uMnquAbig8oLfVnJVJoog@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL0qLwYd9aACZ1abcuBMXO6RVJYn0uMnquAbig8oLfVnJVJoog@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rp_LN4_jcPTr63G8Jt7QaB_PqHc
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 20:29:00 -0000

On Fri, Apr 18, 2014 at 01:15:04PM -0700, Murray S. Kucherawy wrote:
> On Fri, Apr 18, 2014 at 12:07 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> 
> > And I'd suggest that if MUA's do evolve in that manner, maybe it's a
> > hint that the problem which the DMARC cheerleaders tried to sweep away
> > as "not a problem" really *is* a problem that users really care about.
> > And I would hope that in the future, they don't once again try to do
> > something that only meets their own parochial interests, and ignores
> > everyone elses' concerns.
> >
> 
> There are some rather broad brush strokes here, and I'm running out of
> steam trying to keep the record straight.  I'll try once more:
> 
> As John and others have already said, DMARC works fine for specific use
> cases.  It's already been in use by other large operators like Bank of
> America, PayPal, Facebook, and others for quite some time, with no visible
> impact.  The results for them have been very positive.  Google also has it
> turned on part-way for the domain their employees use.
> 
> The difference here is that Yahoo has users that send mail where those
> others do not.

This sounds like the, "Once the rockets go up, who cares *where* they
come down; it's not my department, says Werner von Braun" defense.

Like it or not, the (mis)-application of DMARC has caused some
significant pain for some parts of the Internet.  Maybe *you* don't
care about it, but some of us have to deal with the distruction that
yahoo.com has wrought.

						- Ted


From nobody Fri Apr 18 13:37:06 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B63AC1A01CB for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:37:02 -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, SPF_PASS=-0.001] autolearn=ham
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 ogHgyfh4kS8j for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:37:01 -0700 (PDT)
Received: from mail-wg0-x22e.google.com (mail-wg0-x22e.google.com [IPv6:2a00:1450:400c:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E6B701A002E for <ietf@ietf.org>; Fri, 18 Apr 2014 13:37:00 -0700 (PDT)
Received: by mail-wg0-f46.google.com with SMTP id b13so864836wgh.5 for <ietf@ietf.org>; Fri, 18 Apr 2014 13:36:56 -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:content-type; bh=kbh8bguiYkMzakeNgDBffFmiFtg/eZBRq+C+e4YFNS8=; b=bq4+0Ih6NhvhSPkUWnWAAh1XPTpEHlcdB1atmizzsn6XbwLe1etNTEgbz5PGnbYgqi WZE+fT7KggNwzHbiNBelzP2VPqCQqFovymSjKXXFfqFFS8yeFL6jdzpQv8JklqZjy234 5DztmgUuvD26t7Y6936NkuZpJE+2lnsfgBJ06rTQfJ6Gp12kg9iZQoaGvu3A7MbZJgNN tQIXoz9YbTHMFcwo4SkGtN+TEnbGg6ZhfM2JZuI/7MgENjSwP2gTl8q3j3OSJ05yAAvA pyGjhd++l7Z0AmUsC1663EVuhccnSs9/8s5lW8/QeqILyRURF4dPlGiEGN8ZefUl5a3U KXJw==
MIME-Version: 1.0
X-Received: by 10.194.186.140 with SMTP id fk12mr3370403wjc.47.1397853416366;  Fri, 18 Apr 2014 13:36:56 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Fri, 18 Apr 2014 13:36:56 -0700 (PDT)
In-Reply-To: <20140418202851.GD13642@thunk.org>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <20140418154156.GB31301@thunk.org> <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com> <20140418190716.GA23005@thunk.org> <CAL0qLwYd9aACZ1abcuBMXO6RVJYn0uMnquAbig8oLfVnJVJoog@mail.gmail.com> <20140418202851.GD13642@thunk.org>
Date: Fri, 18 Apr 2014 13:36:56 -0700
Message-ID: <CAL0qLwbne8e8jPVFKz2vuByfYabzdvYu=vcG-N23MfC+fcC_dg@mail.gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=047d7bea451854a9db04f7571c25
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/d4cGZJNYXeXpveI3MP6j6dZ7Fcs
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 20:37:02 -0000

--047d7bea451854a9db04f7571c25
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 18, 2014 at 1:28 PM, <tytso@mit.edu> wrote:

> This sounds like the, "Once the rockets go up, who cares *where* they
> come down; it's not my department, says Werner von Braun" defense.
>
> Like it or not, the (mis)-application of DMARC has caused some
> significant pain for some parts of the Internet.  Maybe *you* don't
> care about it, but some of us have to deal with the distruction that
> yahoo.com has wrought.
>

I didn't say anything close to "I don't care about it", or any of the other
things you're saying above.  I'd really appreciate it if you stopped
putting words in my mouth.

-MSK

--047d7bea451854a9db04f7571c25
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Apr 18, 2014 at 1:28 PM,  <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:tytso@mit.edu" target=3D"_blank">tytso@mit.edu</a>&gt;</spa=
n> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">
This sounds like the, &quot;Once the rockets go up, who cares *where* they<=
br>
come down; it&#39;s not my department, says Werner von Braun&quot; defense.=
<br>
<br>
Like it or not, the (mis)-application of DMARC has caused some<br>
significant pain for some parts of the Internet. =C2=A0Maybe *you* don&#39;=
t<br>
care about it, but some of us have to deal with the distruction that<br>
<a href=3D"http://yahoo.com" target=3D"_blank">yahoo.com</a> has wrought.<b=
r></blockquote><div><br></div><div>I didn&#39;t say anything close to &quot=
;I don&#39;t care about it&quot;, or any of the other things you&#39;re say=
ing above.=C2=A0 I&#39;d really appreciate it if you stopped putting words =
in my mouth.<br>
<br></div><div>-MSK <br></div></div></div></div>

--047d7bea451854a9db04f7571c25--


From nobody Fri Apr 18 13:42:00 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83BB01A02F2 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:41:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 ltJXAQpUZcGe for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:41:57 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 492CF1A02EB for <ietf@ietf.org>; Fri, 18 Apr 2014 13:41:57 -0700 (PDT)
Received: from tytso by imap.thunk.org with local (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WbFbb-0005HB-04; Fri, 18 Apr 2014 20:41:51 +0000
Date: Fri, 18 Apr 2014 20:41:50 +0000
From: tytso@mit.edu
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
Message-ID: <20140418204150.GF13642@thunk.org>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <20140418154156.GB31301@thunk.org> <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com> <20140418190716.GA23005@thunk.org> <CAL0qLwYd9aACZ1abcuBMXO6RVJYn0uMnquAbig8oLfVnJVJoog@mail.gmail.com> <20140418202851.GD13642@thunk.org> <CAL0qLwbne8e8jPVFKz2vuByfYabzdvYu=vcG-N23MfC+fcC_dg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAL0qLwbne8e8jPVFKz2vuByfYabzdvYu=vcG-N23MfC+fcC_dg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Rn_Eb6durFc7TNZYIPi9juV4C9Q
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 20:41:58 -0000

On Fri, Apr 18, 2014 at 01:36:56PM -0700, Murray S. Kucherawy wrote:
> 
> I didn't say anything close to "I don't care about it", or any of the other
> things you're saying above.  I'd really appreciate it if you stopped
> putting words in my mouth.

That was an inference I made given your apparent lack of remorse in
your statements.  I apologize if that's not actually how you feel
about the situation.

Regards,

					- Ted


From nobody Fri Apr 18 13:47:35 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A621D1A03BA for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 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, FREEMAIL_REPLY=1, SPF_PASS=-0.001] autolearn=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 YJpzL9cgVSC2 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:47:32 -0700 (PDT)
Received: from mail-pb0-x232.google.com (mail-pb0-x232.google.com [IPv6:2607:f8b0:400e:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id DA0451A02EB for <ietf@ietf.org>; Fri, 18 Apr 2014 13:47:32 -0700 (PDT)
Received: by mail-pb0-f50.google.com with SMTP id md12so1791661pbc.23 for <ietf@ietf.org>; Fri, 18 Apr 2014 13:47:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XiXLjN4IJAE8Ubua6ooKChb/H0YqXYq0hCF880j2vTg=; b=bFR+3XfQE6wlo+6+NhQHo+Ub97zr+rpwSmrMi4WRD7wFNyVwsdgjCuIXShqoNzsS8Y DfR7dsvRu8IIuyZ5Z6BiNvY8gWJK1DvBDwNlvvP2Qs9Y25gm0PkxPyTwjkyzRX2EkMrz Ma5qzGVgwCIYqwJjLCx6ZP+tUgMDwhAtBATraAcds6MU1QLqbjI4sCC+zIqxG+ZN7mi2 85rQXaEdZqbJ1XROAdYJw5a4cGVT2X70Aem4yufql5wCqaf5nLJvqmRLm6IRGhDe86NG T/y7rf7glMCNFFA+CwRxojSaz3bWOWMKvdN2JCjThb7PPFgHznp2VHtak/tYVZTCDTR2 GC5g==
X-Received: by 10.68.200.133 with SMTP id js5mr24280049pbc.138.1397854048989;  Fri, 18 Apr 2014 13:47:28 -0700 (PDT)
Received: from [192.168.178.20] (225.195.69.111.dynamic.snap.net.nz. [111.69.195.225]) by mx.google.com with ESMTPSA id vg1sm61744685pbc.44.2014.04.18.13.47.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 18 Apr 2014 13:47:28 -0700 (PDT)
Message-ID: <53518F69.90703@gmail.com>
Date: Sat, 19 Apr 2014 08:47:37 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
In-Reply-To: <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/O8pYlCq221Il--JFBVNsjlYNHIk
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 20:47:33 -0000

On 19/04/2014 03:20, Murray S. Kucherawy wrote:
...
> One of the key points about DMARC's design is that it's concerned
> specifically with From:.  The reason is that the content of From: is what's
> typically shown to the recipient by MUAs.  If DMARC keyed off Sender:
> instead, then this would work:
> 
> MAIL FROM: haha@badguy.example.com
> 
> From: security@paypal.com
> Sender: haha@badguy.example.com
> DKIM-Signature: v=1; d=badguy.example.com; ...

So, if the From says

From: goodguy@yahoo.com <haha@badguy.example.com>

many UAs would show only goodguy@yahoo.com as the sender,
but badguy could have passed DMARC, no?

This would not exactly enhance goodguy's reputation,
or Yahoo's for that matter. I realise it isn't the exploit
that Yahoo is trying to stop, but it suggests to me that
DMARC is only plugging one small hole in a very leaky dam.

    Brian


From nobody Fri Apr 18 13:51:14 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E3611A0387 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 AzqyZEz98Pdx for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 13:51:12 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0D35A1A02F2 for <ietf@ietf.org>; Fri, 18 Apr 2014 13:51:11 -0700 (PDT)
Received: by mail-wg0-f47.google.com with SMTP id x12so846024wgg.18 for <ietf@ietf.org>; Fri, 18 Apr 2014 13:51:07 -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:content-type; bh=xddWEENSoOPZHoAv0PA3IU0FW0al1X3FaNuEV6uxTdk=; b=dVREf/yMf3PQKk/6y/35ZpecYK77/6h8bSmc9C9JJkRcV9fJXI2nOoqMmV5j/Nz+a0 Vo5QCnavMo4D4HeQdUVx0Rav7pUjzD80XpZLccGflmBTqeRleSIWirapEX2iPmggYeUO 3CcC6ospnAOD6KpdcMRo5ZBvmDrNDlXQ96pbPinDEx1SoRMMLv1Nt+RTGqUK+g/gFseo zTnva2KaIfOIj1PIGB7ynoGby3YwD+ziydty52348YrXMk8Zx20bvtqMPiIOvpGxRv5e iLD77jgK/TlScWyyTG+8rU6nvsxM8dEujUTS0F5C7JkmYBylf3CWKULdfk+jKQgG8mt0 RPrA==
MIME-Version: 1.0
X-Received: by 10.180.36.232 with SMTP id t8mr3971323wij.1.1397854267539; Fri, 18 Apr 2014 13:51:07 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Fri, 18 Apr 2014 13:51:07 -0700 (PDT)
In-Reply-To: <53518F69.90703@gmail.com>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <53518F69.90703@gmail.com>
Date: Fri, 18 Apr 2014 13:51:07 -0700
Message-ID: <CAL0qLwabz5Hi=4zJRW0bcYNCj7dFH6xtK5EyFzRGRhyBmjKAWg@mail.gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=e89a8f64714b1086c604f7574f96
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/W2sgN151kNsH7ssCoXD5nVtQu_s
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 20:51:13 -0000

--e89a8f64714b1086c604f7574f96
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 18, 2014 at 1:47 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> So, if the From says
>
> From: goodguy@yahoo.com <haha@badguy.example.com>
>
> many UAs would show only goodguy@yahoo.com as the sender,
> but badguy could have passed DMARC, no?
>
> This would not exactly enhance goodguy's reputation,
> or Yahoo's for that matter. I realise it isn't the exploit
> that Yahoo is trying to stop, but it suggests to me that
> DMARC is only plugging one small hole in a very leaky dam.
>

Yes indeed.  The DMARC base document discusses this already, by admitting
it's not a problem DMARC can solve right away:

http://tools.ietf.org/html/draft-kucherawy-dmarc-base-04#section-17.4

It's also something that was brought up as a proposed work item for the
IETF.

-MSK

--e89a8f64714b1086c604f7574f96
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Apr 18, 2014 at 1:47 PM, Brian E Carpenter <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_bl=
ank">brian.e.carpenter@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gma=
il_extra">
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">So, if the From says<br>
<br>
From: <a href=3D"mailto:goodguy@yahoo.com">goodguy@yahoo.com</a> &lt;<a hre=
f=3D"mailto:haha@badguy.example.com">haha@badguy.example.com</a>&gt;<br>
<br>
many UAs would show only <a href=3D"mailto:goodguy@yahoo.com">goodguy@yahoo=
.com</a> as the sender,<br>
but badguy could have passed DMARC, no?<br>
<br>
This would not exactly enhance goodguy&#39;s reputation,<br>
or Yahoo&#39;s for that matter. I realise it isn&#39;t the exploit<br>
that Yahoo is trying to stop, but it suggests to me that<br>
DMARC is only plugging one small hole in a very leaky dam.<br>
<span class=3D""></span></blockquote><div><br></div><div>Yes indeed.=C2=A0 =
The DMARC base document discusses this already, by admitting it&#39;s not a=
 problem DMARC can solve right away:<br><br><a href=3D"http://tools.ietf.or=
g/html/draft-kucherawy-dmarc-base-04#section-17.4">http://tools.ietf.org/ht=
ml/draft-kucherawy-dmarc-base-04#section-17.4</a><br>
<br></div><div>It&#39;s also something that was brought up as a proposed wo=
rk item for the IETF.<br><br></div><div>-MSK<br></div></div></div></div>

--e89a8f64714b1086c604f7574f96--


From nobody Fri Apr 18 14:04:41 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2011A0468 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:04:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 SwBFt2lePn5Q for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:04:35 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 12D8B1A043B for <ietf@ietf.org>; Fri, 18 Apr 2014 14:04:35 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WbFxV-0005av-GH; Fri, 18 Apr 2014 21:04:29 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id D61C75801C3; Fri, 18 Apr 2014 17:04:28 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397855068; bh=0VNnvvK767ayu6WriFwbeJuKrw95nGbSIcfObcPq2sk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ne/HooW8E7ENKLIxv8XjPWcoXEcPtDQ5zp5vNsVKVjqQ2bzWCoRTMndhVektvncgm tYIOgfy54+F6+U3t9ajz6q+HsHlb6WAmsgIb4Gux57wNxrVFvn1gBFGpfX7HKQF/Cu EEnkXM/t3EUkZp1zU6w0+/cl3lpel0soVt03TQfA=
Date: Fri, 18 Apr 2014 17:04:28 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: (DMARC) We've been here before, was Why mailing lists
Message-ID: <20140418210428.GC23005@thunk.org>
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <53518F69.90703@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53518F69.90703@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/C0YFUmCEHdd9s0p84QJ2ARvCb00
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Pete Resnick <presnick@qti.qualcomm.com>, "ietf@ietf.org" <ietf@ietf.org>, John R Levine <johnl@taugh.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 21:04:39 -0000

On Sat, Apr 19, 2014 at 08:47:37AM +1200, Brian E Carpenter wrote:
> 
> So, if the From says
> 
> From: goodguy@yahoo.com <haha@badguy.example.com>
> 
> many UAs would show only goodguy@yahoo.com as the sender,
> but badguy could have passed DMARC, no?
> 
> This would not exactly enhance goodguy's reputation,
> or Yahoo's for that matter. I realise it isn't the exploit
> that Yahoo is trying to stop, but it suggests to me that
> DMARC is only plugging one small hole in a very leaky dam.

Iif the problem is trying to protect goodguy or yahoo.com's
reputation, I wonder if a better approach would have been to have
yahoo.com issue all of its users S/MIME certificates, and then had a
DMARC-like policy requesting recipients: "if the e-mail has the From:
field of yahoo.com, and it's not an S/MIME-signed e-mail with a
yahoo.com certificate, reject the e-mail".

After all, we know S/MIME successfully passes through mailing lists,
and if in fact the message was appropriately signed using an S/MIME
cert, it would be quite natural to have the UA's display the
information from the Common Name field of the cert.

That would solve a host of problems, including the hand-wringing
around how S/MIME has lots of deployed users, but very few deployed
certs.

						- Ted


From nobody Fri Apr 18 14:05:01 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B58741A04A1 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:04:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 AlPyoCC38R9I for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:04:55 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id BCDF41A043B for <ietf@ietf.org>; Fri, 18 Apr 2014 14:04:53 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 9F67ACC09C for <ietf@ietf.org>; Fri, 18 Apr 2014 17:04:49 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id szXYsMIJDnYb for <ietf@ietf.org>; Fri, 18 Apr 2014 17:04:41 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A4D21CC0C6 for <ietf@ietf.org>; Fri, 18 Apr 2014 17:04:40 -0400 (EDT)
Message-ID: <53519368.5060607@meetinghouse.net>
Date: Fri, 18 Apr 2014 17:04:40 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: "ietf@ietf.org" <ietf@ietf.org>
Subject: [off-off-track] Re: (DMARC) We've been here before, was Why mailing lists
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <20140418154156.GB31301@thunk.org> <CAL0qLwb81CuZBv112Mj-SDmRx2WfmJPepThn-ebKx8NYaUbi-g@mail.gmail.com> <20140418190716.GA23005@thunk.org> <CAL0qLwYd9aACZ1abcuBMXO6RVJYn0uMnquAbig8oLfVnJVJoog@mail.gmail.com> <20140418202851.GD13642@thunk.org>
In-Reply-To: <20140418202851.GD13642@thunk.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0ivRoBREfTQgBCm3xl1r-3GjKhk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 21:04:58 -0000

tytso@mit.edu wrote:
> On Fri, Apr 18, 2014 at 01:15:04PM -0700, Murray S. Kucherawy wrote:
>>
>> The difference here is that Yahoo has users that send mail where those
>> others do not.
> This sounds like the, "Once the rockets go up, who cares *where* they
> come down; it's not my department, says Werner von Braun" defense.
>

I believe the quote is ""The rocket worked perfectly except for landing 
on the wrong planet."  (or as it has been suggested "we aimed for the 
Moon, but we hit London.")

:-)


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Apr 18 14:12:34 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3B3D1A010E for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.281
X-Spam-Level: 
X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 9gHfVUr0uX8G for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:12:32 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id DD77D1A007B for <ietf@ietf.org>; Fri, 18 Apr 2014 14:12:31 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id A1867CC0BD for <ietf@ietf.org>; Fri, 18 Apr 2014 17:12:27 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id tuvrFZ1UuTLZ for <ietf@ietf.org>; Fri, 18 Apr 2014 17:12:19 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id C72C9CC09C for <ietf@ietf.org>; Fri, 18 Apr 2014 17:12:18 -0400 (EDT)
Message-ID: <53519532.5070205@meetinghouse.net>
Date: Fri, 18 Apr 2014 17:12:18 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <CAL0qLwbeouNWWAyanTdUHACLUds=5ZQcG0TMCW-AmMNmuE6qrw@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D4DB17@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D4DB17@USCLES544.agna.amgreetings.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Zp2lyytj8-g-yIXTVQ6_8N1oi80
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 21:12:33 -0000

MH Michael Hammer (5304) wrote:
>
> MH: Iâ€™m going to disagree with Murray on the fact that itâ€™s hurting 
> us, the company as the motivator, at least from my perspective. I see 
> it as preventing end users from getting hurt from this particular use 
> case (direct domain abuse). The further we (for some definition of we) 
> can push bad actors from reality (from the users perspective), the 
> less likely they are to fall for certain types of social engineering. 
> I would hypothesize that increased abuse of the type Yahoo has been 
> seeing may be in part due to increased difficulty on the part of 
> malicious individuals in abusing brands implementing DMARC with 
> p=reject. P to P mail becomes increasingly attractive and the use of 
> stolen address books or user email addresses and information from 
> stored messages can be used to improve the effectiveness of the social 
> engineer.
>

At least from the perspective of our lists, and spam traps - abuse of 
stolen address  books and such has been a much larger problem than email 
from forged addresses -- at least where Yahoo is concerned, our normal 
spam traps (spamassassin with lots of checks) caught (and continue to 
catch) most incoming spam -- EXCEPT for the stuff that comes form 
legitimate addresses.

I.e., botnets that have access to address books and legitimate login 
credentials have been the main problem we've seen.  At least so far, 
p=reject hasn't led to an increase in that.

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Apr 18 14:19:22 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5833B1A043E for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:19:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level: 
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 EQjcgSEZwxMc for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:19:19 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.41]) by ietfa.amsl.com (Postfix) with ESMTP id 173661A007B for <ietf@ietf.org>; Fri, 18 Apr 2014 14:19:18 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES531.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Fri, 18 Apr 2014 17:19:14 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: RE: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Thread-Topic: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Thread-Index: AQHPWr6uPWZYqrDS0kS5LDODiAAGHZsXeXikgABNUQCAAAUTQIAAV3cA//+9bDA=
Date: Fri, 18 Apr 2014 21:19:13 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D4DBFD@USCLES544.agna.amgreetings.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <CAL0qLwbeouNWWAyanTdUHACLUds=5ZQcG0TMCW-AmMNmuE6qrw@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D4DB17@USCLES544.agna.amgreetings.com> <53519532.5070205@meetinghouse.net>
In-Reply-To: <53519532.5070205@meetinghouse.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.254.231]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DfW9gBnGlUgLPSK24Z1XyWm240s
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 21:19:20 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0ZiBbbWFpbHRvOmll
dGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIE1pbGVzIEZpZGVsbWFuDQo+IFNlbnQ6
IEZyaWRheSwgQXByaWwgMTgsIDIwMTQgNToxMiBQTQ0KPiBDYzogaWV0Zg0KPiBTdWJqZWN0OiBS
ZTogRE1BUkMgZnJvbSB0aGUgcGVyc3BlY3RpdmUgb2YgdGhlIGxpc3RhZG1pbiBvZiBhIGJ1bmNo
IG9mDQo+IFNNQUxMIGNvbW11bml0eSBsaXN0cw0KPiANCj4gTUggTWljaGFlbCBIYW1tZXIgKDUz
MDQpIHdyb3RlOg0KPiA+DQo+ID4gTUg6IEnigJltIGdvaW5nIHRvIGRpc2FncmVlIHdpdGggTXVy
cmF5IG9uIHRoZSBmYWN0IHRoYXQgaXTigJlzIGh1cnRpbmcNCj4gPiB1cywgdGhlIGNvbXBhbnkg
YXMgdGhlIG1vdGl2YXRvciwgYXQgbGVhc3QgZnJvbSBteSBwZXJzcGVjdGl2ZS4gSSBzZWUNCj4g
PiBpdCBhcyBwcmV2ZW50aW5nIGVuZCB1c2VycyBmcm9tIGdldHRpbmcgaHVydCBmcm9tIHRoaXMg
cGFydGljdWxhciB1c2UNCj4gPiBjYXNlIChkaXJlY3QgZG9tYWluIGFidXNlKS4gVGhlIGZ1cnRo
ZXIgd2UgKGZvciBzb21lIGRlZmluaXRpb24gb2Ygd2UpDQo+ID4gY2FuIHB1c2ggYmFkIGFjdG9y
cyBmcm9tIHJlYWxpdHkgKGZyb20gdGhlIHVzZXJzIHBlcnNwZWN0aXZlKSwgdGhlDQo+ID4gbGVz
cyBsaWtlbHkgdGhleSBhcmUgdG8gZmFsbCBmb3IgY2VydGFpbiB0eXBlcyBvZiBzb2NpYWwgZW5n
aW5lZXJpbmcuDQo+ID4gSSB3b3VsZCBoeXBvdGhlc2l6ZSB0aGF0IGluY3JlYXNlZCBhYnVzZSBv
ZiB0aGUgdHlwZSBZYWhvbyBoYXMgYmVlbg0KPiA+IHNlZWluZyBtYXkgYmUgaW4gcGFydCBkdWUg
dG8gaW5jcmVhc2VkIGRpZmZpY3VsdHkgb24gdGhlIHBhcnQgb2YNCj4gPiBtYWxpY2lvdXMgaW5k
aXZpZHVhbHMgaW4gYWJ1c2luZyBicmFuZHMgaW1wbGVtZW50aW5nIERNQVJDIHdpdGgNCj4gPiBw
PXJlamVjdC4gUCB0byBQIG1haWwgYmVjb21lcyBpbmNyZWFzaW5nbHkgYXR0cmFjdGl2ZSBhbmQg
dGhlIHVzZSBvZg0KPiA+IHN0b2xlbiBhZGRyZXNzIGJvb2tzIG9yIHVzZXIgZW1haWwgYWRkcmVz
c2VzIGFuZCBpbmZvcm1hdGlvbiBmcm9tDQo+ID4gc3RvcmVkIG1lc3NhZ2VzIGNhbiBiZSB1c2Vk
IHRvIGltcHJvdmUgdGhlIGVmZmVjdGl2ZW5lc3Mgb2YgdGhlIHNvY2lhbA0KPiA+IGVuZ2luZWVy
Lg0KPiA+DQo+IA0KPiBBdCBsZWFzdCBmcm9tIHRoZSBwZXJzcGVjdGl2ZSBvZiBvdXIgbGlzdHMs
IGFuZCBzcGFtIHRyYXBzIC0gYWJ1c2Ugb2YNCj4gc3RvbGVuIGFkZHJlc3MgIGJvb2tzIGFuZCBz
dWNoIGhhcyBiZWVuIGEgbXVjaCBsYXJnZXIgcHJvYmxlbSB0aGFuIGVtYWlsDQo+IGZyb20gZm9y
Z2VkIGFkZHJlc3NlcyAtLSBhdCBsZWFzdCB3aGVyZSBZYWhvbyBpcyBjb25jZXJuZWQsIG91ciBu
b3JtYWwNCj4gc3BhbSB0cmFwcyAoc3BhbWFzc2Fzc2luIHdpdGggbG90cyBvZiBjaGVja3MpIGNh
dWdodCAoYW5kIGNvbnRpbnVlIHRvDQo+IGNhdGNoKSBtb3N0IGluY29taW5nIHNwYW0gLS0gRVhD
RVBUIGZvciB0aGUgc3R1ZmYgdGhhdCBjb21lcyBmb3JtDQo+IGxlZ2l0aW1hdGUgYWRkcmVzc2Vz
Lg0KPiANCj4gSS5lLiwgYm90bmV0cyB0aGF0IGhhdmUgYWNjZXNzIHRvIGFkZHJlc3MgYm9va3Mg
YW5kIGxlZ2l0aW1hdGUgbG9naW4NCj4gY3JlZGVudGlhbHMgaGF2ZSBiZWVuIHRoZSBtYWluIHBy
b2JsZW0gd2UndmUgc2Vlbi4gIEF0IGxlYXN0IHNvIGZhciwNCj4gcD1yZWplY3QgaGFzbid0IGxl
ZCB0byBhbiBpbmNyZWFzZSBpbiB0aGF0Lg0KPiANCg0KVGhlIGFzc2VydGlvbiBoYXMgYmVlbiBt
YWRlIHRoYXQgdGhlIG1haWwgYWJ1c2luZyB0aGUgc3RvbGVuIGFkZHJlc3MgYm9va3Mgd2FzIGJl
aW5nIHNlbnQgZnJvbSBwbGFjZXMgb3RoZXIgdGhhbiB5YWhvby5jb20gYnV0IGNsYWltaW5nIHRv
IGJlIGZyb20gY29tcHJvbWlzZWR1c2VyQHlhaG9vLmNvbS4gSW4gdGhpcyBzY2VuYXJpbyBwPXJl
amVjdCB3b3VsZCBoYXZlIGFuIGltcGFjdCBpbiBtaXRpZ2F0aW5nIHRoYXQgdHlwZSBvZiBhYnVz
ZSBmb3IgbWFpbGJveCBwcm92aWRlcnMgdmFsaWRhdGluZyBETUFSQyAobm90d2l0aHN0YW5kaW5n
IHRoZSBkYW1hZ2UgZG9uZSB0byBtYWlsaW5nIGxpc3RzIGFuZCBvdGhlciAzcmQgcGFydGllcyku
DQoNCk1pa2UNCg==


From nobody Fri Apr 18 14:30:12 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D675B1A01CB for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.281
X-Spam-Level: 
X-Spam-Status: No, score=-0.281 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 oRqNdCU_sXlg for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 14:30:11 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id DF75D1A0109 for <ietf@ietf.org>; Fri, 18 Apr 2014 14:30:10 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id DAB41CC0BD for <ietf@ietf.org>; Fri, 18 Apr 2014 17:30:06 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IUVvaGWlL6-n for <ietf@ietf.org>; Fri, 18 Apr 2014 17:29:58 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 1EC53CC0B3 for <ietf@ietf.org>; Fri, 18 Apr 2014 17:29:58 -0400 (EDT)
Message-ID: <53519955.9050102@meetinghouse.net>
Date: Fri, 18 Apr 2014 17:29:57 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf <ietf@ietf.org>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <CAL0qLwbeouNWWAyanTdUHACLUds=5ZQcG0TMCW-AmMNmuE6qrw@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D4DB17@USCLES544.agna.amgreetings.com> <53519532.5070205@meetinghouse.net> <CE39F90A45FF0C49A1EA229FC9899B0507D4DBFD@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D4DBFD@USCLES544.agna.amgreetings.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lT5Kq1zS6JznmPVjbyQR2sJshHA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 21:30:12 -0000

MH Michael Hammer (5304) wrote:
>
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Miles Fidelman
>> Sent: Friday, April 18, 2014 5:12 PM
>> Cc: ietf
>> Subject: Re: DMARC from the perspective of the listadmin of a bunch of
>> SMALL community lists
>>
>> MH Michael Hammer (5304) wrote:
>>> MH: Iâ€™m going to disagree with Murray on the fact that itâ€™s hurting
>>> us, the company as the motivator, at least from my perspective. I see
>>> it as preventing end users from getting hurt from this particular use
>>> case (direct domain abuse). The further we (for some definition of we)
>>> can push bad actors from reality (from the users perspective), the
>>> less likely they are to fall for certain types of social engineering.
>>> I would hypothesize that increased abuse of the type Yahoo has been
>>> seeing may be in part due to increased difficulty on the part of
>>> malicious individuals in abusing brands implementing DMARC with
>>> p=reject. P to P mail becomes increasingly attractive and the use of
>>> stolen address books or user email addresses and information from
>>> stored messages can be used to improve the effectiveness of the social
>>> engineer.
>>>
>> At least from the perspective of our lists, and spam traps - abuse of
>> stolen address  books and such has been a much larger problem than email
>> from forged addresses -- at least where Yahoo is concerned, our normal
>> spam traps (spamassassin with lots of checks) caught (and continue to
>> catch) most incoming spam -- EXCEPT for the stuff that comes form
>> legitimate addresses.
>>
>> I.e., botnets that have access to address books and legitimate login
>> credentials have been the main problem we've seen.  At least so far,
>> p=reject hasn't led to an increase in that.
>>
> The assertion has been made that the mail abusing the stolen address books was being sent from places other than yahoo.com but claiming to be from compromiseduser@yahoo.com. In this scenario p=reject would have an impact in mitigating that type of abuse for mailbox providers validating DMARC (notwithstanding the damage done to mailing lists and other 3rd parties).
>
>

All I can report is what I see in our logs, and after-the-fact analysis 
of mail that has actually made onto the lists we run.

Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Apr 18 15:35:20 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 858C51A01B5 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 15:35:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.874
X-Spam-Level: 
X-Spam-Status: No, score=-0.874 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 QuikLTBzmwnr for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 15:35:14 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id 253391A014D for <ietf@ietf.org>; Fri, 18 Apr 2014 15:35:14 -0700 (PDT)
Received: from [192.168.2.18] (unknown [99.17.29.183]) by dougbarton.us (Postfix) with ESMTPSA id D88C922B1A; Fri, 18 Apr 2014 22:35:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1397860510; bh=+WRsr1thi5Tyimv74G0XvN1VN9CaTu7wqu94MNyKW4k=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=qHezMtNcbpKVWaPC733IiR8cXgywIrp7ycyMUIDGlXq0f4bI8j3OfwAEPdN0JSP6m Ql/4SGVKF2lUX1gQgO6LeBtgxubJHcCj/dHbbirZuGZ02JBKcCemXK1cqfJdLel+gC 9t8+wEm95s/5ae1L5LxbtzE0rZnHonC8oL4K8VjU=
Message-ID: <5351A89D.7000700@dougbarton.us>
Date: Fri, 18 Apr 2014 15:35:09 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com>
In-Reply-To: <01P6S93XQ9TI00004W@mauve.mrochek.com>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zg_Y9gd-mcolobzkIF7VDYgaonQ
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 22:35:18 -0000

On 04/18/2014 07:47 AM, Ned Freed wrote:
 >> I said:
>> Rather than throwing up our
>> hands and telling the DMARC folks that we refuse to work with them
>> unless their solution solves the problem of our anachronistic use case
>> that that constitutes only a tiny percentage of their overall traffic;
>
> Again with the traffic size as justification for poor behavior. Not all
> messages are created equal, and some functions have utility entirely
> disproportionate to the amount of bandwidth they use.

Right, so the input here from the operators is, "Mailing list traffic is 
not important enough to us to prevent us from deploying an anti-spam 
solution that solves the vast majority of our problems with little cost 
or difficulty. The MLM software authors will have to deal with this 
problem on their end." And your response is to stamp your feet and 
shout, "But my mailing list traffic IS important! It is, IT IS!!!!!"

I'm glad that you feel that way, we should all have things that we're 
proud of after all. But in terms of actually listening to and acting on 
the input we've received from the operator community about this topic, 
the IETF has failed. The fact that people like you don't recognize this 
as a failure is a clear sign that our slippery slope into irrlevance is 
well greased.

Doug


From nobody Fri Apr 18 16:03:35 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61DED1A01F0 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 16:03:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 DtMDU4nISQkS for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 16:03:29 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id B392E1A01B5 for <ietf@ietf.org>; Fri, 18 Apr 2014 16:03:29 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WbHob-0006Ls-5l; Fri, 18 Apr 2014 23:03:25 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 88BDA5801C3; Fri, 18 Apr 2014 19:03:24 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1397862204; bh=Fo3rATCv6hSnaUR/CgTHl27VLuBITTGSv83JF0q02V0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Ft1yq3j9vcrGE0R1++ZG/7v2vZLZ+OF/pzsp+s4RMHF1v8nco5yW647rN0Y8PRFhK zkV98+EV/+3hBwSsDwpoUqmHWeTwixlCdO5SDvISeHDemSoTiF471Ux1Z0zfFQoEdE j5hO8J+30dt6Iawn4n+mnDTrKxLy5+IKHF3aNOpE=
Date: Fri, 18 Apr 2014 19:03:24 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Doug Barton <dougb@dougbarton.us>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Message-ID: <20140418230324.GB6166@thunk.org>
References: <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5351A89D.7000700@dougbarton.us>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/X3kOsYM3J5Hj17uhsv5GX8YjlZg
Cc: Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 23:03:34 -0000

On Fri, Apr 18, 2014 at 03:35:09PM -0700, Doug Barton wrote:
> 
> Right, so the input here from the operators is, "Mailing list traffic is not
> important enough to us to prevent us from deploying an anti-spam solution
> that solves the vast majority of our problems with little cost or
> difficulty. The MLM software authors will have to deal with this problem on
> their end." 

... and then the operators should not be surprised if the people
modifying the MLM software do something which is best for them, and
which not necessarily best for the interest of the users of certain
operators.

Which is the default when neither side is willing compromise, and
everyone is reduced to taking unilateral action.

If you want to call that a failure of the standards process, I can
only agree.  I suspect the only difference is how the blame for the
failure gets allocated.  But at the end of the day, it is what it is.
Some people will use one kind of messaging, and say it's all the
mailing list people's fault, and some other people will use a
different messaging, and say it's all Yahoo's fault.

And the users will be stuck in the middle....  and presumably they as
their own indpendent actors, will do what is in their best interest.

Cheers,

					- Ted


From nobody Fri Apr 18 16:24:39 2014
Return-Path: <randy@psg.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 348791A04F6 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 16:24:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 yK1jHGxR7p9r for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 16:24:36 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 377651A0484 for <ietf@ietf.org>; Fri, 18 Apr 2014 16:24:36 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.76) (envelope-from <randy@psg.com>) id 1WbI90-0004yh-QW; Fri, 18 Apr 2014 23:24:31 +0000
Date: Sat, 19 Apr 2014 08:24:29 +0900
Message-ID: <m2zjjiuspe.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <20140418230324.GB6166@thunk.org>
References: <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <20140418230324.GB6166@thunk.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MfpnyOUUS3HD4K1b2GHGhp79vyk
Cc: IETF Disgust <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Apr 2014 23:24:37 -0000

> ... and then the operators should not be surprised if the people
> modifying the MLM software do something which is best for them, and
> which not necessarily best for the interest of the users of certain
> operators.
> 
> Which is the default when neither side is willing compromise, and
> everyone is reduced to taking unilateral action.
> 
> If you want to call that a failure of the standards process, I can
> only agree.

it is a failure of the internet and internet operations.  the failure
of the standards process just enables an excuse.

randy


From nobody Fri Apr 18 17:53:33 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48E9B1A01BF for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 17:53:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 wItHEay2FG28 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 17:53:27 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 08BED1A0167 for <ietf@ietf.org>; Fri, 18 Apr 2014 17:53:26 -0700 (PDT)
Received: (qmail 46741 invoked from network); 19 Apr 2014 00:53:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:mime-version:subject:references:in-reply-to:content-type:content-transfer-encoding:user-agent; s=b694.5351c901.k1404; i=johnl-iecc.com@submit.iecc.com; bh=OXGmk+EsmuIPp8JNkM9EZrfGlOlUGPQ/pGH/m4tT7vQ=; b=Mg7rUE+X27Eraj6LrBFlH4cYll8mCtoB9ROMHuCgU/6B3SfBhsuOAV7RQgfNFWtpV6tPGzb8l9/7UaWzJ6iVBp6n3+61axEPUpHf0Cn7Zh8sLQrLMYKQxaEJmm0770UXErOUDK4Gjk11D0UiDCsOjf0urXGIvmEbqv3VtE6HVqKEN3Sd58Gu3o2mOMgr1wfx+uFxMo6vJSHMD39TQADpwrNqyE3D0cMfxAeGvEeAkdUwE5cnQr8rYOtG223UrAxq
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:mime-version:subject:references:in-reply-to:content-type:content-transfer-encoding:user-agent; s=b694.5351c901.k1404; olt=johnl-iecc.com@submit.iecc.com; bh=OXGmk+EsmuIPp8JNkM9EZrfGlOlUGPQ/pGH/m4tT7vQ=; b=C2eYzn7x46JKNYfrT6+We5EHkLgVjfQMYNvZKIM6cJg7LRSnU8lJeCwPo2PIaqaR6PpwpwbkQHSIqpRceYHnPn67JfM8ejhR6zsAbPhBVmZYp6/pwpFkVXMAMvRquVgx89YDhgY+F/yZhAwcNNNykJb9HyhTtrssUg078YOFvogn4QjJqPoukOVf3ucfd2MPzLsT4Wkz8qwKdjPv6aMT/mwLh5QmRJRZxOckg/IxwbDCp7ofwMnrR/zpKy3xhqDs
Received: from jlevine.local ([65.114.90.17]) by imap.iecc.com ([64.57.183.75]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 19 Apr 2014 00:53:21 -0000
Date: 18 Apr 2014 19:53:20 -0500
Message-ID: <5351C900.1060803@taugh.com>
From: "John Levine" <johnl@taugh.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
Subject: Re: (DMARC) We've been here before, was Why mailing lists
References: <20140417181815.8A5871ACD1@ld9781.wdf.sap.corp> <9451.1397772992@sandelman.ca> <CAL0qLwa0a4nDAdCHkkMJdeemsj+cezcmH3+59CvhF8q7B72ryg@mail.gmail.com> <53518F69.90703@gmail.com>
In-Reply-To: <53518F69.90703@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fmm0z6N4v9OuK_FWEVjRS_rlHgI
Cc: Pete Resnick <presnick@qti.qualcomm.com>, John R Levine <johnl@taugh.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 00:53:31 -0000

> This would not exactly enhance goodguy's reputation,
> or Yahoo's for that matter. I realise it isn't the exploit
> that Yahoo is trying to stop, but it suggests to me that
> DMARC is only plugging one small hole in a very leaky dam.

No kidding.  DMARC is only useful because most spammers and phishers are 
remarkably stupid.  But not all of them.

R's,
John


From nobody Fri Apr 18 17:56:09 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 734E01A0549 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 17:56:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 lYfP7QU4V2EE for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 17:56:07 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5BA0C1A0217 for <ietf@ietf.org>; Fri, 18 Apr 2014 17:56:07 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6STS3NZ9C006DZF@mauve.mrochek.com> for ietf@ietf.org; Fri, 18 Apr 2014 17:51:02 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SSBIBCPC00004X@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 18 Apr 2014 17:50:55 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6STS0F6I600004X@mauve.mrochek.com>
Date: Fri, 18 Apr 2014 17:33:08 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Fri, 18 Apr 2014 15:35:09 -0700" <5351A89D.7000700@dougbarton.us>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Hqdsjgx1imr5IR9pEJEzEbp320Q
Cc: Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 00:56:08 -0000

> On 04/18/2014 07:47 AM, Ned Freed wrote:
>  >> I said:
> >> Rather than throwing up our
> >> hands and telling the DMARC folks that we refuse to work with them
> >> unless their solution solves the problem of our anachronistic use case
> >> that that constitutes only a tiny percentage of their overall traffic;
> >
> > Again with the traffic size as justification for poor behavior. Not all
> > messages are created equal, and some functions have utility entirely
> > disproportionate to the amount of bandwidth they use.

> Right, so the input here from the operators is, "Mailing list traffic is
> not important enough to us to prevent us from deploying an anti-spam
> solution that solves the vast majority of our problems with little cost
> or difficulty. The MLM software authors will have to deal with this
> problem on their end." And your response is to stamp your feet and
> shout, "But my mailing list traffic IS important! It is, IT IS!!!!!"

I really have to wonder where you got enough straw to build a strawman of this
size. If you actually, you know, read what I've been saying, it has been that
this was handled extremely poorly by the IETF. Just not in the way you happen
to believe.

Your view of what happened, who the operators actually are and what their
positions are, and what the likely consequences are going to be are somewhere
between a gross oversimplifications and looney tunes. But I must say they are
amusing.

> I'm glad that you feel that way, we should all have things that we're
> proud of after all. But in terms of actually listening to and acting on
> the input we've received from the operator community about this topic,
> the IETF has failed.

Wrong again. The evidence shows clearly that the IETF did listen, to this group
at least. Where the IETF failed was in not looking at the big picture and
likely consequences, which I'm afraid is not laid out along the axis of "big
operators all supporting DMARC" versus "tiny insignificant list maintainer
stick-in-the-muds".

Oh, and not that it matters, but I personally have only been tangentially
involved in most of this. This is because a lot of it happened when I wasn't
unable to participate. Kidney transplants and heavy standards involvement don't
mix very well.

> The fact that people like you don't recognize this
> as a failure is a clear sign that our slippery slope into irrlevance is
> well greased.

I've been saying from the start that this was a failure on the IETF's part.

It's just not the kind of failure you think it was.

				Ned


From nobody Fri Apr 18 18:09:33 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAF441A0574 for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 18:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 TEIMWi7uM-7G for <ietf@ietfa.amsl.com>; Fri, 18 Apr 2014 18:09:30 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id C6AF91A0203 for <ietf@ietf.org>; Fri, 18 Apr 2014 18:09:29 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 661ADCC0BF for <ietf@ietf.org>; Fri, 18 Apr 2014 21:09:25 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id grRBdt7FTp3B for <ietf@ietf.org>; Fri, 18 Apr 2014 21:09:16 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 6A8B4CC0BD for <ietf@ietf.org>; Fri, 18 Apr 2014 21:09:16 -0400 (EDT)
Message-ID: <5351CCBC.4070901@meetinghouse.net>
Date: Fri, 18 Apr 2014 21:09:16 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com>
In-Reply-To: <01P6STS0F6I600004X@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KU36qsZh1cmJ51F0r3cknaki1UQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 01:09:32 -0000

ned+ietf@mauve.mrochek.com wrote:
>> On 04/18/2014 07:47 AM, Ned Freed wrote:
>>  >> I said:
>> >> Rather than throwing up our
>> >> hands and telling the DMARC folks that we refuse to work with them
>> >> unless their solution solves the problem of our anachronistic use 
>> case
>> >> that that constitutes only a tiny percentage of their overall 
>> traffic;
>> >
>> > Again with the traffic size as justification for poor behavior. Not 
>> all
>> > messages are created equal, and some functions have utility entirely
>> > disproportionate to the amount of bandwidth they use.
>
>> Right, so the input here from the operators is, "Mailing list traffic is
>> not important enough to us to prevent us from deploying an anti-spam
>> solution that solves the vast majority of our problems with little cost
>> or difficulty. The MLM software authors will have to deal with this
>> problem on their end." And your response is to stamp your feet and
>> shout, "But my mailing list traffic IS important! It is, IT IS!!!!!"
>
> I really have to wonder where you got enough straw to build a strawman 
> of this
> size. If you actually, you know, read what I've been saying, it has 
> been that
> this was handled extremely poorly by the IETF. Just not in the way you 
> happen
> to believe.
>
> Your view of what happened, who the operators actually are and what their
> positions are, and what the likely consequences are going to be are 
> somewhere
> between a gross oversimplifications and looney tunes. But I must say 
> they are
> amusing.
>
>> I'm glad that you feel that way, we should all have things that we're
>> proud of after all. But in terms of actually listening to and acting on
>> the input we've received from the operator community about this topic,
>> the IETF has failed.
>
> Wrong again. The evidence shows clearly that the IETF did listen, to 
> this group
> at least. Where the IETF failed was in not looking at the big picture and
> likely consequences, which I'm afraid is not laid out along the axis 
> of "big
> operators all supporting DMARC" versus "tiny insignificant list 
> maintainer
> stick-in-the-muds".
>
> Oh, and not that it matters, but I personally have only been tangentially
> involved in most of this. This is because a lot of it happened when I 
> wasn't
> unable to participate. Kidney transplants and heavy standards 
> involvement don't
> mix very well.

Wow... hope all is well now.  (History of kidney issues in our family - 
never has led to a transplant.  I feel for you.)
>
>> The fact that people like you don't recognize this
>> as a failure is a clear sign that our slippery slope into irrlevance is
>> well greased.
>
> I've been saying from the start that this was a failure on the IETF's 
> part.
>
> It's just not the kind of failure you think it was.
>

Any suggestions on how we might approach making changes?  I guess 
overall architecture, process, and policy are IAB's purview - but how 
does one get folks to pay attention - I haven't seen any IAB members 
commenting here, for example. (Note: My own IETF involvement has always 
been one step removed - mostly in my days at BBN, where I sat next to a 
lot of active IETF participants, but spent more of my time on system 
design and application of protocols.  My direct standards involvement 
has always seemed to end up in other forums - mostly military and 
security stuff that ran under funny venues. These days, I'm more on the 
tail end of being effected by such things as this current debacle - 
which are kind of motivating me to get more seriously involved.)

Miles Fidelman

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Sat Apr 19 03:24:43 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4C3C1A0121 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 03:24:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 OU_1z035xrtC for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 03:24:36 -0700 (PDT)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 549501A00D8 for <ietf@ietf.org>; Sat, 19 Apr 2014 03:24:36 -0700 (PDT)
Received: by mail-yk0-f173.google.com with SMTP id 10so2057158ykt.18 for <ietf@ietf.org>; Sat, 19 Apr 2014 03:24:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=LMlQqYabIwbbrfqxoBnDcI1Y3/YGd7VbzMbSjwSXPWs=; b=DTMUD3q42g7RTywxYR4/2G5eenwPAgqAIJE6Ut9VXFcI6BCQHb0zuh9aywtRsygmI5 q58m01fTVNLi2SmM/KdsBvTjwEH3gjxa/Gt9Pv5v1rvd0TJ1sAJNrkmcMH0EcY68lGjs tINenJ1ZL0MqTAijg7V/TK5ldAfW2CtjRo0PhG6XSQryvDRYPmIGUrR0RVA/TDQJp5W/ /S9SOS/PJWwN6wrIhxyDNrNPK/6SQA8UXD6Qa/n6/5aE21vLtaDy4IS6Uv57IYswW0BK q3wlmeZIUAFXFqCUEPFMjWr/ejUKrCGa26vb1vgJ4HukfWAEOlGdCvnWwQaiGc+Tm6mu 3V0Q==
MIME-Version: 1.0
X-Received: by 10.236.129.43 with SMTP id g31mr840155yhi.115.1397903071922; Sat, 19 Apr 2014 03:24:31 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Sat, 19 Apr 2014 03:24:31 -0700 (PDT)
Date: Sat, 19 Apr 2014 12:24:31 +0200
Message-ID: <CADnDZ88QR+v3amW3Gr57oEtNM3YmRbbL-1G8kGoZAhT8Ji+o_g@mail.gmail.com>
Subject: Open source running code or closed industry code (was Re: "why I quit writing internet standards")
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pE8jPNAFIjEK-wGvy_jhsKDRALo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 10:24:42 -0000

Hi IETFers,

Firstly, IETF standards need to be more available to community through
open sources, specially the security standards to help the community
to avoid attacks from big organisations. I suggest that a new IETF
Area to be open for Open Source. We need to make comments on all our
standards that are not available open sources. In IETF it is still not
clear its standards implementation practices in the community, we need
informational documents that decsribe its standards' tests and
possible scenario failures.

Secondly, the industry is running codes (closed source) of our
standards but no much feedback about their performance in IETF. The
IETF should get more input from open source communities that can help
to make IETF more driven by user-engineers than industries.

Thirdly, both people and organisations, that volunteer their running
codes into the new IETF area will help to build a better Internet
future. If we get open source volunteers into IETF with their
input/code/documents, then we will get better performance in our
standards and in the future directions.

Comments below,

On 4/14/14, Alia Atlas <akatlas@gmail.com> wrote:
> On Mon, Apr 14, 2014 at 11:57 AM, David Meyer <dmm@1-4-5.net> wrote:
>> On Mon, Apr 14, 2014 at 8:08 AM, George, Wes <wesley.george@twcable.com>
>> wrote:
>>> I=E2=80=99m surprised that no one has sent this out yet:
>>> http://gigaom.com/2014/04/12/why-i-quit-writing-internet-standards/
>>>
>>> "Summary: After contributing to standards organizations for more than
>>> seven
>>> years, engineer Vidya Narayanan decided it was time to move on. Althoug=
h
>>> she
>>> still believes that these organizations make the Internet a better
>>> place,
>>> she wonders about the pace of change versus the pace of organizations."
>>>
>>> My thoughts-
>>>
>>> There are some nuggets of truth in what she says in this article, and i=
n
>>> some of the comments. I think that the problems are real, so there=E2=
=80=99s
>>> value
>>> in taking the criticism constructively, despite the fact that the autho=
r
>>> chose to focus on the problems without any suggestions of solutions.
>>>
>>> "while the pace at which standards are written hasn=E2=80=99t changed i=
n many
>>> years,
>>> the pace at which the real world adopts software has become orders of
>>> magnitude faster."
>>> =E2=80=A6
>>> "Running code and rough consensus, the motto of the IETF, used to be
>>> realizable at some point. =E2=80=A6 In the name of consensus, we debate
>>> frivolous
>>> details forever. In the name of patents, we never finish.=E2=80=9D
>>> =E2=80=A6
>>> "Unless these standards organizations make radical shifts towards
>>> practicality, their relevance will soon be questionable.=E2=80=9D
>>>
>>> I don=E2=80=99t have too many big ideas how to fix these problems, but =
I=E2=80=99ll at
>>> least
>>> take a crack at it in order to spur discussion. My paraphrase of the
>>> problem
>>> and some discussion follows.
>>>
>>> - We=E2=80=99ve lost sight of consensus and are too often derailed by a=
 vocal
>>> minority of those willing to endlessly debate a point.
>>>
>>> Part of the solution to that is reiterating what consensus is and is
>>> not,
>>> such as draft-resnick-on-consensus so that we don=E2=80=99t confuse a n=
eed for
>>> consensus with a need for unanimity. Part of the solution is IETF
>>> leadership
>>> helping to identify when we have rough consensus encumbered by a debate
>>> that
>>> will never resolve itself, without quieting actual disagreement that
>>> needs
>>> continued discussion in order to find a compromise. I don=E2=80=99t hav=
e good
>>> suggestions on how to make that second half better.
>>>
>>> - We don=E2=80=99t have nearly enough focus on running code as the thin=
g that
>>> helps
>>> to ensure that we=E2=80=99re using our limited cycles on getting the ri=
ght
>>> things
>>> out expediently, and either getting the design right the first time, or
>>> failing quickly and iterating to improve
>>>
>>> The solution here may be that we need to be much more aggressive at
>>> expecting any standards track documents to have running code much earli=
er
>>> in
>>> the process. The other part of that is to renew our focus on actual
>>> interop
>>> standards work, probably by charter or in-group feedback, shift focus
>>> away
>>> from BCP and info documents. Perhaps when considering whether to procee=
d
>>> with a given document, we need test as to whether it=E2=80=99s actively
>>> helpful/needed and ensure that we know what audience would be looking a=
t
>>> it,
>>> rather than simply ensuring that it is =E2=80=9Cnot harmful=E2=80=9D an=
d mostly within
>>> the
>>> WG=E2=80=99s chartered focus.

I recommend to separate between designers and implementers. Each have
different challenges and different tasks, so I suggest different
WGs/DTs or a new IETF Area. The way IETF was doing in the past is
excellent process because we have designers interactions, but we need
more volunteer implementers and we may need implementers to have more
interaction within IETF.

>>
>> My friend @colin_dixon pointed this out to me yesterday, and I've been
>> giving it quite a bit of thought since then (I have a nascent blog on
>> the topic of how open source and standards orgs might
>> productively/efficiently work together; follow up to
>> http://www.sdncentral.com/education/david-meyer-reflections-opendaylight=
-open-source-project-brocade/2014/03).
>>

Thanks, it is an important draft for the IETF General Area to
consider. I suggested before that the IETF general Area should have
some WGs for important issues because the area is not performing well,
and many issues are not getting good conclusions by the community.
IESG will like to leave every thing general for only its input and we
as community have no input only if IESG decides. However, if we do
like you and write our own draft it may get attention from existing
participants, but who left IETF like Vidya Narayanan or may be many
others (who unsubscribed from IETF list) will not get chance to say
their opinion because there was no convincing community system for
general works in IETF General Area.

>> What I can say is that after seeing the kind of progress that several
>> open source communities make (they do epitomize the best of the IETF's
>> running code/rough consensus ethic), one does have to wonder if
>> traditional standards making is either obsolete or in dire need of a
>> make over. What is needed, IMO, is a reimagining of how the standards
>> process interacts with the open source movement specifically focused
>> on how they can compliment one another.

I agree with you, but IMO the way of doing that needs to be within
IETF organisation not outside IETF. Those open source community should
be welcomed to join WGs within one new IETF Area. Maybe there are
problems within IETF management with those communities management,
which may delay movements.

>
> [Alia] It would be very useful to have a functional model for how the
> two can compliment each other.  We also tend to talk about open-source
> as a single monolith - when it can have very different models for
> accepting in changes, how and who runs the community, who is really
> participating (open source doesn't mean non-corporate) etc.

The IETF should be running its running code, some of community are
sending messages to WG asking of code sources but they may get no
respond, isn't that a shame of IETF to have no clue what to respond or
to have no document related to running code tests. The IETF runs the
standards for the community, so I expect the IETF to help community to
participate in its standards by making an IETF area available for
community to run the IETF standards.

>  Some of
> what the IETF does is the architecture and requirements thinking about
> how the solution should fit in - while some of the open-source is
> about getting a solution implemented ASAP.

Yes, but after the IETF standard is published don't we think we need
to implement publicly (i.e. openly) that so the IETF vision is
targeted to make the Internet better place for users or community.
Does IETF leave the industry to manage/influence the change of
technology?

>  IMHO, a spiral is useful
> with an easy way of interaction.  With I2RS, as a WG chair, I
> suggested having experimental drafts describing solutions that were
> being implemented - but haven't seen any.   A question is what is
> needed to encourage the interactions.

Mostly industries don't do volunteering open source only for specific
reasons, but people may do volunteering open sources just to fulfill
the IETF vision.

>
> [Alia] Diversity of implementation is important as is stability of a
> standard and it being understood how to change/upgrade for different
> versions.  These don't come automatically via open-source.

IETF General Area still did not solve the diversity problem overall,
but for implementation diversity, IMO, we need a new IETF area that is
responsible to manage IETF open sources of its running code in the
community.

Best Wishes,

AB


From nobody Sat Apr 19 08:30:57 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD321A0019 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 08:30:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ANbgLleTryG4 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 08:30:55 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0C5841A0007 for <ietf@ietf.org>; Sat, 19 Apr 2014 08:30:55 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6TOCLSZI80065LF@mauve.mrochek.com> for ietf@ietf.org; Sat, 19 Apr 2014 08:25:47 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 19 Apr 2014 08:25:39 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6TOCIJM0W00004W@mauve.mrochek.com>
Date: Sat, 19 Apr 2014 08:17:44 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Fri, 18 Apr 2014 21:09:16 -0400" <5351CCBC.4070901@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0ntD84dFYdhf_Q7rBNO3SwQFSUE
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 15:30:56 -0000

> > I've been saying from the start that this was a failure on the IETF's
> > part.

> > It's just not the kind of failure you think it was.

> Any suggestions on how we might approach making changes?  I guess
> overall architecture, process, and policy are IAB's purview - but how
> does one get folks to pay attention - I haven't seen any IAB members
> commenting here, for example. (Note: My own IETF involvement has always
> been one step removed - mostly in my days at BBN, where I sat next to a
> lot of active IETF participants, but spent more of my time on system
> design and application of protocols.  My direct standards involvement
> has always seemed to end up in other forums - mostly military and
> security stuff that ran under funny venues. These days, I'm more on the
> tail end of being effected by such things as this current debacle -
> which are kind of motivating me to get more seriously involved.)

I've been thinking about it, and I think this needs to be addressed on at least
two different fronts. First, I've come to believe that the IETF needs to say
something, in  some capacity, about the political aspects of the DMARC
situation specifically.

I also think the time has come to try and address the more general problem
of misunderstanding and/or misrepresentation of the status of various
documents. This probably needs to be addressed through a combination of
automatic labeling as well as some explicit statements here and there.

And this really needs to be spearheaded by the IESG, not the IAB. I hope the
IESG is already considering taking action. If not, they should be.

				Ned


From nobody Sat Apr 19 09:00:38 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19A0A1A0035 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 09:00:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.872
X-Spam-Level: 
X-Spam-Status: No, score=-2.872 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 Xh-vmXsE1Vb7 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 09:00:33 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 037261A0020 for <ietf@ietf.org>; Sat, 19 Apr 2014 09:00:33 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WbXgq-000FDz-BP; Sat, 19 Apr 2014 12:00:28 -0400
Date: Sat, 19 Apr 2014 12:00:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com, Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Message-ID: <56CF13B8250F8BE24F6F10CC@JcK-HP8200.jck.com>
In-Reply-To: <01P6TOCIJM0W00004W@mauve.mrochek.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net> <01P6TOCIJM0W00004W@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6YfRNiqkpNabOXCm-iM-HYcXo6k
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 16:00:35 -0000

--On Saturday, April 19, 2014 08:17 -0700
ned+ietf@mauve.mrochek.com wrote:

> I've been thinking about it, and I think this needs to be
> addressed on at least
> two different fronts. First, I've come to believe that the
> IETF needs to say
> something, in  some capacity, about the political aspects of
> the DMARC situation specifically.
> 
> I also think the time has come to try and address the more
> general problem
> of misunderstanding and/or misrepresentation of the status of
> various
> documents. This probably needs to be addressed through a
> combination of
> automatic labeling as well as some explicit statements here
> and there.

Ned,

I agree, but I also think there is another element of the
situation that got us here, and that has led us close to other
problems in the past.  When the RFC Editor is asked to publish a
non-WG document (i.e., either an individual submission through
the IETF stream or as an independent submission) that could be
construed as some sort of standard (whether actually standards
track or not) or approval of an IANA parameter registration is
on the basis of expert review, there as a potential for the
appearance of conflicts of interest.   Those conflicts need not
be of the traditional legal or financial variety.  They can
occur (or be perceived to occur) when someone's institutional or
organizational relationships outside the IETF might lead people
to suspect that review and decision-making might not be as
careful, unbiased, or primarily reflective of the interest of
the IETF or the broader Internet community as we would like it
to assume it always is.  For situations where troublesome
relationships exist or might be inferred (even by those
suffering from mild paranoid), we need to get much more careful
about disclosure of the relationships involved.

> And this really needs to be spearheaded by the IESG, not the
> IAB. I hope the IESG is already considering taking action. 
> If not, they should be.

Indeed.

    john






From nobody Sat Apr 19 10:12:16 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF82B1A0040 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 10:12:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 sseGLsEJTiaP for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 10:12:09 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7D7101A0032 for <ietf@ietf.org>; Sat, 19 Apr 2014 10:12:07 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6TRV44UTC006RIU@mauve.mrochek.com> for ietf@ietf.org; Sat, 19 Apr 2014 10:06:59 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 19 Apr 2014 10:06:53 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6TRV1PBB000004W@mauve.mrochek.com>
Date: Sat, 19 Apr 2014 08:31:52 -0700 (PDT)
Subject: Re: What I've been wondering about the DMARC problem
In-reply-to: "Your message dated Fri, 18 Apr 2014 08:45:44 -0700" <CAL0qLwY4xVrPwABRhv90JSRF8wta0P5OCw_UWzVYOyUZk2-W4Q@mail.gmail.com>
References: <534ED376.8060303@bluepopcorn.net> <20140418013433.2763.qmail@joyce.lan> <CAL0qLwY4xVrPwABRhv90JSRF8wta0P5OCw_UWzVYOyUZk2-W4Q@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RrhGIqVKKoFEhZtzgTzQUBvummA
Cc: Jim Fenton <fenton@bluepopcorn.net>, John Levine <johnl@taugh.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 17:12:11 -0000

> On Thu, Apr 17, 2014 at 6:34 PM, John Levine <johnl@taugh.com> wrote:

> > >"If the RFC5322.From domain does not exist in the DNS, Mail Receivers
> > >SHOULD direct the receiving SMTP server to reject the message."
> >
> > As far as I can tell, that bit of poor advice hasn't been implemented.

> Why is that poor advice?  It's not uncommon for an MTA receiving mail to
> confirm that the message is replyable, at least insofar as an A and MX are
> available for whatever comes after the "@".

It's outrageously poor advice, for the simple reason that there's all kinds of
legitimate email that's sent for all kinds of different reasons that you don't
want people to be able to reply to. And the sooner they get a failure when they
try and reply, the better.

As such, the ability to reply to the RFC5322.From tells you almost nothing
about its legitimacy.

It's yet another case where a failure to consider the multiple semamtics
field like RFC5322.From has, and designing to a subset of those designs,
ends up screwing things up.

				Ned


From nobody Sat Apr 19 11:03:12 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47D701A0065 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 11:03:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Yo3F2yzTwnkZ for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 11:03:02 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6D9ED1A0055 for <ietf@ietf.org>; Sat, 19 Apr 2014 11:03:02 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6TTN6I1S0003SXB@mauve.mrochek.com> for ietf@ietf.org; Sat, 19 Apr 2014 10:57:52 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sat, 19 Apr 2014 10:57:42 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6TTN1ILCQ00004W@mauve.mrochek.com>
Date: Sat, 19 Apr 2014 10:08:31 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Sat, 19 Apr 2014 12:00:23 -0400" <56CF13B8250F8BE24F6F10CC@JcK-HP8200.jck.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net> <01P6TOCIJM0W00004W@mauve.mrochek.com> <56CF13B8250F8BE24F6F10CC@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/69uaUfNKzDIss-0o2E0CgI97MHY
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 18:03:07 -0000

> --On Saturday, April 19, 2014 08:17 -0700
> ned+ietf@mauve.mrochek.com wrote:

> > I've been thinking about it, and I think this needs to be
> > addressed on at least
> > two different fronts. First, I've come to believe that the
> > IETF needs to say
> > something, in  some capacity, about the political aspects of
> > the DMARC situation specifically.
> >
> > I also think the time has come to try and address the more
> > general problem
> > of misunderstanding and/or misrepresentation of the status of
> > various
> > documents. This probably needs to be addressed through a
> > combination of
> > automatic labeling as well as some explicit statements here
> > and there.

> Ned,

> I agree, but I also think there is another element of the
> situation that got us here, and that has led us close to other
> problems in the past.  When the RFC Editor is asked to publish a
> non-WG document (i.e., either an individual submission through
> the IETF stream or as an independent submission) that could be
> construed as some sort of standard (whether actually standards
> track or not) or approval of an IANA parameter registration is
> on the basis of expert review, there as a potential for the
> appearance of conflicts of interest.   Those conflicts need not
> be of the traditional legal or financial variety.  They can
> occur (or be perceived to occur) when someone's institutional or
> organizational relationships outside the IETF might lead people
> to suspect that review and decision-making might not be as
> careful, unbiased, or primarily reflective of the interest of
> the IETF or the broader Internet community as we would like it
> to assume it always is.  For situations where troublesome
> relationships exist or might be inferred (even by those
> suffering from mild paranoid), we need to get much more careful
> about disclosure of the relationships involved.

Good point, and I agree.

These waters are going to be difficult to nagivate, but I don't see any
alternative.

				Ned


From nobody Sat Apr 19 11:13:57 2014
Return-Path: <andy@yumaworks.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE9561A0077 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 11:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 xJspnKlILELG for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 11:13:53 -0700 (PDT)
Received: from mail-qc0-f171.google.com (mail-qc0-f171.google.com [209.85.216.171]) by ietfa.amsl.com (Postfix) with ESMTP id 559571A0072 for <ietf@ietf.org>; Sat, 19 Apr 2014 11:13:53 -0700 (PDT)
Received: by mail-qc0-f171.google.com with SMTP id c9so2772706qcz.30 for <ietf@ietf.org>; Sat, 19 Apr 2014 11:13:48 -0700 (PDT)
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:content-type; bh=XJ//HEQ1tP2YQTVOhw86/A9eB/Q1ffa3O23k1MxWZUk=; b=cuXK5V5ZdxppgilIjr7U2cuUXdFCjGMnxIcqdaxWALDM7Xgs1cZj3IkKP+5+pxmvH2 f4T12elXBkJUZN4lfkJvwuYLQ6GsxxfO2CRq/qYwMjk6BHoqf21kFZaQdMEebF3de3UM 2GSwvfDXvlGytF6tUiblTNDLf9tBVM2attC8qBL3ucNOs33U7UTmCbB3tw9lI31X/13F 5ZCU6ste8RidSuJRdtO6V1tiJfT69DrOx40MiOyDSwYH0SNP8JObvnzhGRa2VQyuUIs+ YqluxBxnMYtxfvspE6vbv4d8GW3wAj2EE7/fIN0tag6NMNv4dHDfXVM2OG8uUhkZnPtY PY6A==
X-Gm-Message-State: ALoCoQk8L3+3itFZY2DwwHJ/Q5/NJrZwGOpInICj5ai/VALkL+1nAwd9VIGUPEHiviNyipyRpj9j
MIME-Version: 1.0
X-Received: by 10.140.92.99 with SMTP id a90mr14887772qge.34.1397931228781; Sat, 19 Apr 2014 11:13:48 -0700 (PDT)
Received: by 10.140.41.134 with HTTP; Sat, 19 Apr 2014 11:13:48 -0700 (PDT)
In-Reply-To: <5350FAA0.1050607@cisco.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <CABCOCHQU0H5wCei+1OROYdoMCorPLNxpmmfk4aphR9kkrv5MJw@mail.gmail.com> <534FE1C3.3070103@cisco.com> <6.2.5.6.2.20140417112406.0b7c9b70@resistor.net> <5350FAA0.1050607@cisco.com>
Date: Sat, 19 Apr 2014 11:13:48 -0700
Message-ID: <CABCOCHQPjNGxzXUdABpDC6fRmXOE35zhCZi+7R6xn3bO1jX+zw@mail.gmail.com>
Subject: Re: "why I quit writing internet standards"
From: Andy Bierman <andy@yumaworks.com>
To: Benoit Claise <bclaise@cisco.com>
Content-Type: multipart/alternative; boundary=001a113abfd84ff34a04f7693a43
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6RjKRkZand9sVEG0uJGGS1Xbpv8
Cc: S Moonesamy <sm+ietf@elandsys.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 18:13:56 -0000

--001a113abfd84ff34a04f7693a43
Content-Type: text/plain; charset=ISO-8859-1

On Fri, Apr 18, 2014 at 3:12 AM, Benoit Claise <bclaise@cisco.com> wrote:

> Hi,
>
>> Hi Benoit,
>> At 07:14 17-04-2014, Benoit Claise wrote:
>>
>>> We discussed during the milestones during one of the last plenaries.
>>>
>>
>> Yes.
>>
>>  The discussion was around: the milestones are indications and not
>>> deadlines.
>>> In Open Source project, these are deadlines.
>>> In the IETF, I would love to find a middle ground between the two.
>>> In the IETF, the only "deadlines" are the meetings, or to be more
>>> precise, the submission deadlines just before the meetings.
>>>
>>
>> Lisa used to send monthly progress reports.  It provided some visibility
>> into what was happening within the area.
>>
>> A milestone can be an estimate of when X can be completed.  I might
>> suggest one and the group decides whether everyone can target that date and
>> plan accordingly.  There are times when deadlines may be needed as an
>> effort can end up in failure.
>>
>>  Exactly, and we should understand why!
>>> I like this tool: <http://www.arkko.com/tools/lifecycle/>
>>> http://www.arkko.com/tools/lifecycle/<draft-name>-timing.html
>>> For example: <http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-
>>> interfaces-cfg-timing.html>http://www.arkko.com/tools/
>>> lifecycle/draft-ietf-netmod-interfaces-cfg-timing.html
>>> Where is the bottleneck? Is this a process issue? The
>>> authors/shepherd/IESG/RFC-editors?
>>> I don't want to finger point, but understand what we should improve.
>>>
>>
>> Let's see. :-)  The shepherd write-up does not provide me with much
>> information.  There's three years from the first -00 to the latest version
>> of the draft.  The author activity looks okay. There is less activity from
>> the document shepherd (there is an explanation for that).  There was a Last
>> Call in April 2013.  The AD asked for a revised I-D in May 2013.  There was
>> another Last Call in December 2013.  The IESG didn't like something in the
>> draft and it took seven months to address that.
>>
>> There's still the two and a half years.  There are seven months between
>> the date in the charter and the first Last Call.  It would take some effort
>> to figure out what happened during the first two years.  It looks like the
>> working group was the bottleneck.
>>
> Thanks.
> I'm more after analyzing trend than inspecting this particular document.
> For example, https://datatracker.ietf.org/iesg/discusses/ doesn't look
> like a very long list to me.
>
>

I wonder if this NETMOD draft is typical of other WGs or not.
The idstats say it has been a WG draft for 388 days.
I think the original charter was about 160 days, but I can't tell since
all the relevant milestones were deleted from the WG charter page last week.

The problem is obvious.  The WG spent lots of energy going over and over
the same issues as more new people read the draft for the first time.
 These people
often brought genuine concerns and new insights to the current solution,
and the
WG was quite willing to ignore the milestones and accommodate the new
feature
requests.


Regards, Benoit
>
>
>> Regards,
>> S. Moonesamy
>> .
>>
>>
>
Andy

--001a113abfd84ff34a04f7693a43
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Fri, Apr 18, 2014 at 3:12 AM, Benoit Claise <span dir=3D"ltr">&l=
t;<a href=3D"mailto:bclaise@cisco.com" target=3D"_blank">bclaise@cisco.com<=
/a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi,<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hi Benoit,<br>
At 07:14 17-04-2014, Benoit Claise wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
We discussed during the milestones during one of the last plenaries.<br>
</blockquote>
<br>
Yes.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The discussion was around: the milestones are indications and not deadlines=
.<br>
In Open Source project, these are deadlines.<br>
In the IETF, I would love to find a middle ground between the two.<br>
In the IETF, the only &quot;deadlines&quot; are the meetings, or to be more=
 precise, the submission deadlines just before the meetings.<br>
</blockquote>
<br>
Lisa used to send monthly progress reports. =A0It provided some visibility =
into what was happening within the area.<br>
<br>
A milestone can be an estimate of when X can be completed. =A0I might sugge=
st one and the group decides whether everyone can target that date and plan=
 accordingly. =A0There are times when deadlines may be needed as an effort =
can end up in failure.<br>

<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Exactly, and we should understand why!<br>
I like this tool: &lt;<a href=3D"http://www.arkko.com/tools/lifecycle/" tar=
get=3D"_blank">http://www.arkko.com/tools/<u></u>lifecycle/</a>&gt;<a href=
=3D"http://www.arkko.com/tools/lifecycle/" target=3D"_blank">http://www.ark=
ko.<u></u>com/tools/lifecycle/</a>&lt;draft-<u></u>name&gt;-timing.html<br>

For example: &lt;<a href=3D"http://www.arkko.com/tools/lifecycle/draft-ietf=
-netmod-interfaces-cfg-timing.html" target=3D"_blank">http://www.arkko.com/=
tools/<u></u>lifecycle/draft-ietf-netmod-<u></u>interfaces-cfg-timing.html<=
/a>&gt;<a href=3D"http://www.arkko.com/tools/lifecycle/draft-ietf-netmod-in=
terfaces-cfg-timing.html" target=3D"_blank">htt<u></u>p://www.arkko.com/too=
ls/<u></u>lifecycle/draft-ietf-netmod-<u></u>interfaces-cfg-timing.html</a>=
<br>

Where is the bottleneck? Is this a process issue? The authors/shepherd/IESG=
/RFC-<u></u>editors?<br>
I don&#39;t want to finger point, but understand what we should improve.<br=
>
</blockquote>
<br>
Let&#39;s see. :-) =A0The shepherd write-up does not provide me with much i=
nformation. =A0There&#39;s three years from the first -00 to the latest ver=
sion of the draft. =A0The author activity looks okay. There is less activit=
y from the document shepherd (there is an explanation for that). =A0There w=
as a Last Call in April 2013. =A0The AD asked for a revised I-D in May 2013=
. =A0There was another Last Call in December 2013. =A0The IESG didn&#39;t l=
ike something in the draft and it took seven months to address that.<br>

<br>
There&#39;s still the two and a half years. =A0There are seven months betwe=
en the date in the charter and the first Last Call. =A0It would take some e=
ffort to figure out what happened during the first two years. =A0It looks l=
ike the working group was the bottleneck.<br>

</blockquote>
Thanks.<br>
I&#39;m more after analyzing trend than inspecting this particular document=
.<br>
For example, <a href=3D"https://datatracker.ietf.org/iesg/discusses/" targe=
t=3D"_blank">https://datatracker.ietf.org/<u></u>iesg/discusses/</a> doesn&=
#39;t look like a very long list to me.<br>
<br></blockquote><div><br></div><div><br></div><div>I wonder if this NETMOD=
 draft is typical of other WGs or not.</div><div>The idstats say it has bee=
n a WG draft for 388 days.<br></div><div>I think the original charter was a=
bout 160 days, but I can&#39;t tell since</div>
<div>all the relevant milestones were deleted from the WG charter page last=
 week.</div><div><br></div><div>The problem is obvious. =A0The WG spent lot=
s of energy going over and over</div><div>the same issues as more new peopl=
e read the draft for the first time. =A0These people</div>
<div>often brought genuine concerns and new insights to the current solutio=
n, and the</div><div>WG was quite willing to ignore the milestones and acco=
mmodate the new feature</div><div>requests.</div><div><br></div><div><br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">
Regards, Benoit<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Regards,<br>
S. Moonesamy<br>
.<br>
<br>
</blockquote>
<br>
</blockquote></div><br></div><div class=3D"gmail_extra">Andy</div><div clas=
s=3D"gmail_extra"><br></div></div>

--001a113abfd84ff34a04f7693a43--


From nobody Sat Apr 19 12:17:30 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFE8E1A006E for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 12:17:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.302
X-Spam-Level: 
X-Spam-Status: No, score=-99.302 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 tz3wROMWyvfy for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 12:17:23 -0700 (PDT)
Received: from news.winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 7398F1A0024 for <ietf@ietf.org>; Sat, 19 Apr 2014 12:17:22 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=5310; t=1397935035; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=NTyT+QeDdS2euskRtFJ66g1pePs=; b=lzbVsgskW7bajkgDJ1eg /XWAGgQSRi/242DKRE2pftdqnmYYwm25g/pQftSkpCWO8J+4Dm5yeifDKkzMc+uK ZlwY6S+ZOHQgSf9ppMsw9jff9/x1SB2/pt1rt4Bsxe7hizUNF5x9u+GbT/jLgfSX W7duTGKA0rWOfE3LvflIO0U=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 19 Apr 2014 15:17:15 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1043607563.7140.3876; Sat, 19 Apr 2014 15:17:14 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=5310; t=1397934961; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=rzqhqMm epocj0zYIGLQi4XtcV1d3n/wO1F9J6BdBz2w=; b=cHuNh6w/w+lknAAWdt9ZBEa 0BOiQA38uZ1ClIhRROYKnKkawbMiD1+/DpyVlpeDSMPlKM4kBS7mHNsUQIIThw6m 9rGdcsitbtxDxaTPHj2lhBIsTjqwUZjmHDY4+01W5esoHDm+2298yMExz2fjZdgz qgCiRRYccma0y7gXFUZA=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 19 Apr 2014 15:16:01 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1063137046.9.3384; Sat, 19 Apr 2014 15:16:00 -0400
Message-ID: <5352CBBE.3000400@isdg.net>
Date: Sat, 19 Apr 2014 15:17:18 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com, John C Klensin <john-ietf@jck.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net> <01P6TOCIJM0W00004W@mauve.mrochek.com> <56CF13B8250F8BE24F6F10CC@JcK-HP8200.jck.com> <01P6TTN1ILCQ00004W@mauve.mrochek.com>
In-Reply-To: <01P6TTN1ILCQ00004W@mauve.mrochek.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aCJTlX3xPSo7JPX29sckPWWd2WY
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 19:17:29 -0000

On 4/19/2014 1:08 PM, ned+ietf@mauve.mrochek.com wrote:
>
>> I agree, but I also think there is another element of the
>> situation that got us here, and that has led us close to other
>> problems in the past.  When the RFC Editor is asked to publish a
>> non-WG document (i.e., either an individual submission through
>> the IETF stream or as an independent submission) that could be
>> construed as some sort of standard (whether actually standards
>> track or not) or approval of an IANA parameter registration is
>> on the basis of expert review, there as a potential for the
>> appearance of conflicts of interest.   Those conflicts need not
>> be of the traditional legal or financial variety.  They can
>> occur (or be perceived to occur) when someone's institutional or
>> organizational relationships outside the IETF might lead people
>> to suspect that review and decision-making might not be as
>> careful, unbiased, or primarily reflective of the interest of
>> the IETF or the broader Internet community as we would like it
>> to assume it always is.  For situations where troublesome
>> relationships exist or might be inferred (even by those
>> suffering from mild paranoid), we need to get much more careful
>> about disclosure of the relationships involved.
>
> Good point, and I agree.
>
> These waters are going to be difficult to nagivate, but I don't see any
> alternative.
>

Maybe I should of followed with my gut instinct and followed through 
with my appeal a few years back when this whole situation we have 
today was the crux of the main philosophical debates of TRUST vs 
POLICY DKIM framework and a deemphasis of policy and lost of a 
standard track WG ADSP policy proposal was going down the drain with 
conflictive trust interest dominating the direction of DKIM.

But with seeing the WG chairs and ADs interest also being in conflict 
as well, including one AD recusing himself from my initial appeal 
interest AD/chairs contact, I knew it was time to give up. In a chat 
with Eric, who lead the early DKIM policy framework work, when 
Levine's poison pill ADSP hijacked the policy work, he said it was 
over as far as an IETF standard work item. It will have to be 
revisited from outside the IETF with some trade group.  DMARC is a result.

In that vain, I am partially the blame for backing off. How much 
talking can you do? At this point, now I am being excommunicated. It 
wasn't fun.  Its not like the chairs and the Ads were not aware of the 
concerns. But I guess I didn't have enough influence. I didn't attend 
meetings. I didn't have get to know the folks or them me.

But I knew this was going to be a major problem when the IETF was now 
abandoning ADSP for the same reasons you are seeing now with DMARC. 
Essentially both lacked 3rd party semantics.  So its somewhat surreal 
that DMARC would be now marketed by the IETF when the same ADSP 
problem did not get addressed. It can't be made any more simpler than 
that.

Overall, the technical issues were obvious. But there was two basic 
attitudes that was hard to overcome and I think still needs to be 
overcome:

   1) A mindset that REJECTION is bad.  Accept all mail and let users 
decide was
      the prevailing mindset.  It was a SYSTEM wide vs USER filtering 
design
      issue. As a developer, it means BOTH options would be available 
for the
      operators to work with.   But overall, the ideas of 
deterministic system
      wide rejection was too little too much for many of the IETF mail 
vets.

   2) The 3rd party Trust/Reputation Market potential was too great to 
allow
      self-signing policy based system marginalized this trust market 
potential.
      New ventures had started by the leads of the DKIM project. 
Again, brought
      up but what were you going to do.  For me, lead the way, trust 
and policy
      do co-exist and we would be better for it, if others vendors 
refused to
      see that. But no, POLICY had to go!  there was no compromising 
whatsoever.

Anyway, I'm somewhat tired of it.  Much development time was put into 
DKIM, ADSP, ATPS over the 9+.  If the attitudes don't change now that 
DMARC is here, well, I don't see any hope with this issue unless fresh 
new synergism and policy support advocates folks get involved. We got 
the usual typical relatively few people that appear to be considered 
the main leads with these IETF mail related projects and that has to 
improve or in this case, finally change a few key folks position on 
DKIM + POLICY and help lead the way with 3rd party policy support that 
is workable, acceptable for all.

If DMARC is the going to be the "method," the "language" then it can 
be fine tuned with IETF based extensions that the silly DMARC.ORG 
folks, whoever they are, can not stop from happening in the same way 
we somewhat tried to keep ADSP alive with the ATPS extension.

If thats a problem, then how about this>

      I proposed ADSP to be remove from Historic status, and 
reestablished
      as a Proposed Standard.

Why does this make sense?  Well, there are systems that support ADSP, 
there is APIs, there is running code, and its still too early with 
DMARC to completely eliminate ADSP.  Since its not perfect, a 
competing ADSP may actually get the DMARC.ORG to be more agreeable 
with IETF related concerns.

-- 
HLS



From nobody Sat Apr 19 13:16:19 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33EF21A0068 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 13:16:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.872
X-Spam-Level: 
X-Spam-Status: No, score=-2.872 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 qNtkLKNoIYq3 for <ietf@ietfa.amsl.com>; Sat, 19 Apr 2014 13:16:12 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B74B41A0055 for <ietf@ietf.org>; Sat, 19 Apr 2014 13:16:12 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WbbgC-000FZR-Fh; Sat, 19 Apr 2014 16:16:04 -0400
Date: Sat, 19 Apr 2014 16:16:04 -0400
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Message-ID: <8647B94D503D57B710D99D7E@[192.168.1.128]>
In-Reply-To: <01P6TTN1ILCQ00004W@mauve.mrochek.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net> <01P6TOCIJM0W00004W@mauve.mrochek.com> <56CF13B8250F8BE24F6F10CC@JcK-HP8200.jck.com> <01P6TTN1ILCQ00004W@mauve.mrochek.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YQQYBjf6L1ELKMKawwQy5nmHQhM
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Apr 2014 20:16:17 -0000

--On Saturday, 19 April, 2014 10:08 -0700
ned+ietf@mauve.mrochek.com wrote:

>...
>> there as a potential for the appearance of conflicts of
>> interest.   Those conflicts need not be of the traditional
>> legal or financial variety.  They can occur (or be perceived
>> to occur) when someone's institutional or organizational
>> relationships outside the IETF might lead people to suspect
>> that review and decision-making might not be as careful,
>> unbiased, or primarily reflective of the interest of the IETF
>> or the broader Internet community as we would like it to
>> assume it always is.  For situations where troublesome
>> relationships exist or might be inferred (even by those
>> suffering from mild paranoid), we need to get much more
>> careful about disclosure of the relationships involved.
> 
> Good point, and I agree.
> 
> These waters are going to be difficult to nagivate, but I
> don't see any alternative.

Yes.  However, I see some parallel to the IPR situation.  We
could presumably treat members of the community like adults (I
think almost all are) and say "if you have an outside-the-IETF
relationship to the developers, or developing organization, of a
spec, you must at least disclose it", it would go a long way
and, IMO, not be particularly difficult.   Unlike the IPR
situation, this one is unlikely to require involving lawyers in
what one could or could not say/ disclose.   The waters get
difficult only if we feel a need to take the next steps toward
forced recusal or worse.  Maybe, if we just demanded disclosure
as an expected professional courtesy and act of honesty toward
the rest of the community and understood that either an
undisclosed conflict or a disclosed one that seemed to distort a
decision could be reasonable grounds for appeals, we could get
away without a requirement for a lot of hair-splitting rules.

    john




From nobody Sun Apr 20 05:49:28 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B63E91A01C0 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 05:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable
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 I-wZ3U9HTbL2 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 05:48:55 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [4.31.198.40]) by ietfa.amsl.com (Postfix) with ESMTP id D90CD1A01BE for <ietf@ietf.org>; Sun, 20 Apr 2014 05:48:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 377121E12A2; Sun, 20 Apr 2014 05:48:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o0htXVZXN5yP; Sun, 20 Apr 2014 05:48:04 -0700 (PDT)
Received: from [10.30.0.148] (unknown [83.150.71.93]) by c8a.amsl.com (Postfix) with ESMTPSA id 9230C1DF11E; Sun, 20 Apr 2014 05:48:03 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: NetMundial
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Sun, 20 Apr 2014 15:48:48 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E6B5379-FD6C-4034-810B-348E95E7E2CF@ietf.org>
To: "internetgovtech@iab.org" <internetgovtech@iab.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BhFnaaMkmtOX7Kyb7ThRUuZFetw
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "internetgovtech@iab.org" <internetgovtech@iab.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 12:49:01 -0000

I wanted to highlight that next week the NetMundial meeting =
(http://netmundial.br) will be run in Sao Paulo, Brazil. Pointers to =
agendas, draft outcome documents, etc. can be found from my blog:

http://www.ietf.org/blog/2014/04/netmundial/

Jari Arkko, IETF Chair


From nobody Sun Apr 20 07:57:32 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82E3D1A018F for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 07:57:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level: 
X-Spam-Status: No, score=-4.573 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 1wzbNr6AShR8 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 07:57:22 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 854251A0004 for <ietf@ietf.org>; Sun, 20 Apr 2014 07:57:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1398005838; x=1429541838; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=xf7P7I5ao+dTSCAQZB5ZinNJZ2LbE7BJu752E3IjTnQ=; b=TQlqEIeisHikLSfi4R8pzFSOTyyuR9Ur5EsKPD1rMXcgUaxBWgebGUIX nsuqYssPOtcARJNa2qTzE2DciwE8+MpnnaVSBKZqGccD/CqDOen1mUFG8 5oRkloqpyme/FPcnSBUL7scov9t60oisBDX1KdYUPX5vH+bTJHZYBEbkT s=;
X-IronPort-AV: E=McAfee;i="5400,1158,7413"; a="29924520"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by wolverine01.qualcomm.com with ESMTP; 20 Apr 2014 07:57:18 -0700
X-IronPort-AV: E=Sophos;i="4.97,892,1389772800"; d="scan'208";a="651940867"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 20 Apr 2014 07:57:17 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 20 Apr 2014 07:57:17 -0700
Message-ID: <5353E048.5020001@qti.qualcomm.com>
Date: Sun, 20 Apr 2014 09:57:12 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <ned+ietf@mauve.mrochek.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net> <01P6TOCIJM0W00004W@mauve.mrochek.com>
In-Reply-To: <01P6TOCIJM0W00004W@mauve.mrochek.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/S8d-wcp1Lgrg5LeHyaSldzA6I6g
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 14:57:28 -0000

On 4/19/14 10:17 AM, ned+ietf@mauve.mrochek.com wrote:
> I also think the time has come to try and address the more general 
> problem
> of misunderstanding and/or misrepresentation of the status of various
> documents. This probably needs to be addressed through a combination of
> automatic labeling as well as some explicit statements here and there.
>
> And this really needs to be spearheaded by the IESG, not the IAB. I 
> hope the
> IESG is already considering taking action. If not, they should be.

The timing has been impeccable. The IESG had been privately talking 
about the "IETF relevance" issue, including why people are bringing 
"done" work to the IETF instead of working inside of the IETF. And 
related to "done" work, we have also been discussing the relative merits 
of AD-sponsored documents vs. ISE documents and what the appropriate use 
of IESG and IETF time is for these things. We've had all of that on our 
agenda for our upcoming retreat in a couple of weeks, and planned to 
discuss it with the IAB during a joint meeting. Then this DMARC thing 
happens, and Vidya published her article on "why I quit writing internet 
standards". It could not have been timed better.

I'm trying to get my head around what we should have done differently on 
this, both tactically and strategically, so that I can summarize it for 
the discussion. But I can say pretty confidently that this is a topic 
frontmost in the minds of IESG folks.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Sun Apr 20 09:53:12 2014
Return-Path: <jaltman@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2311D1A0026 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 09:53:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FROM=0.001, J_CHICKENPOX_21=0.6, SPF_PASS=-0.001] autolearn=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 Z20TYouxWN14 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 09:53:07 -0700 (PDT)
Received: from mail-qc0-x230.google.com (mail-qc0-x230.google.com [IPv6:2607:f8b0:400d:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id BA3731A0025 for <ietf@ietf.org>; Sun, 20 Apr 2014 09:53:07 -0700 (PDT)
Received: by mail-qc0-f176.google.com with SMTP id m20so3271130qcx.21 for <ietf@ietf.org>; Sun, 20 Apr 2014 09:53:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Xt3JDbT66RAL/VRquvho5xxJHzG70wWsLzMTHZpWpS4=; b=R28DIWiJKTA/f80+quzNw6tW/xJuMitTVauiC3Zs0r3RJhJRVgIuZ6wTKPJsTT0f/5 mT4fimhX4EKRa+0xCOGjWi93BSK00J68bGdyzr2mN8yqhuaAWHxpyWtvcMkTuyL2fpyu zdPk/bKIeuSEsyb9e4oxdvt1Yi2MOl1QMROlTTDthq3tH518oU8nj2S9gbjhLe+FrT1f fECag84CowJD+mtwjZuxi1NUYYSYLdf9FZrBeHq2jaiBWTz979Honf3n7EvJ8PcfYg3+ vAS1cgkjyYoDmntUbH3+KuOrzJs/dVwbWqaO5159ZqmvKaSk9Bi4WYrKPLymcsZ10LW6 kGww==
X-Received: by 10.140.46.36 with SMTP id j33mr31931344qga.27.1398012782574; Sun, 20 Apr 2014 09:53:02 -0700 (PDT)
Received: from [10.29.24.213] (mobile-198-228-204-204.mycingular.net. [198.228.204.204]) by mx.google.com with ESMTPSA id k9sm68455131qat.18.2014.04.20.09.53.01 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Apr 2014 09:53:01 -0700 (PDT)
Sender: Jeffrey Altman <jaltman@gmail.com>
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: DMARC and yahoo
From: Jeffrey Altman <jaltman@secure-endpoints.com>
X-Mailer: iPad Mail (11D167)
In-Reply-To: <20140416023813.GA21807@thunk.org>
Date: Sun, 20 Apr 2014 12:52:59 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org>
To: Theodore Ts'o <tytso@mit.edu>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TBqS36Vo_7NZYXwGPw1OWjZ6erU
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 16:53:09 -0000

Jeffrey Altman


> On Apr 15, 2014, at 10:38 PM, Theodore Ts'o <tytso@mit.edu> wrote:
>=20
>> On Tue, Apr 15, 2014 at 10:23:22PM -0400, Michael Richardson wrote:
>> So, as a WG chair, a person known to me just tried to post to the list
>> =46rom a brand new yahoo.com mail account.  They aren't subscribed with t=
hat
>> address.  I would normally just approve, and add them...
>>=20
>> It seems to me that I must now actually reject, because it would affect o=
ther
>> subscribers.
>>=20
>> I'm now thinking that we need to remove all the @yahoo.com addresses from=

>> posting to ietf mailing lists.
>=20
> So on my mailman configuration (which I believe is the default), if
> alice@hotmail.com receives 5 hard fail bounces she will get
> automatically suspended from the mailing list.  So a single e-mail
> from a @yahoo.com address won't cause damage, and if seven days go by
> without any further bounce messages, the "bounce counter" gets reset
> to zero.  The problem comes if you have many e-mail messages from
> yahoo.com users (which according to yahoo and the DMARC cheerleaders,
> shouldn't happen happen, because mailing list traffic is
> "insignificant" :-).

I took a different approach.  I left the bounce detection on but switched al=
l @yahoo.com accounts to digest mode.  Since the mail now comes from the lis=
t instead of the @yahoo.com sender there are no rejections.   Not a perfect s=
olution but it prevents harm to non-@yahoo.com list participants.

Jeffrey Altman=


From nobody Sun Apr 20 10:10:28 2014
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 739541A0031 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:10:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
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 uG6PH619zxHd for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:10:22 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0883A1A0027 for <ietf@ietf.org>; Sun, 20 Apr 2014 10:10:21 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3KHADYH012503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 20 Apr 2014 10:10:17 -0700
Message-ID: <5353FEF7.2060708@bbiw.net>
Date: Sun, 20 Apr 2014 10:08:07 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <534C067D.8080506@meetinghouse.net> <CAL0qLwa5CRwxn0V=7D84KFv9K_u5W5L+PPUXc3KPkD0YHkNo1w@mail.gmail.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320>
In-Reply-To: <4756885.Eo3b3po9Vj@scott-latitude-e6320>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Sun, 20 Apr 2014 10:10:17 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OemWzAtjWjeuOpPX4pL3VCiVzhw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:10:26 -0000

On 4/14/2014 8:28 PM, Scott Kitterman wrote:
> If that's true, it's my impression it's true because the DMARC proponents
> insisted any possible working group charter preclude meaningful changes to the
> base specification because the work was already done.


That statement is incorrect.

What we pressed for was to get community rough consensus on the kinds of 
technical work that needed to be done to the -base (core) specification, 
/before/ chartering the effort.

This was explicitly to avoid the trap of declaring the existing spec 
unstable -- and that's what starting an open-ended development effort 
automatically does -- when there was no demonstrated need to do that.

In spite of repeated efforts -- in at least two venues -- to get folks 
to state what work they thought was needed and to get community support 
for that work, no tasks were produced.

That meant that any wg charter permitting changes to the protocol would 
have been entirely without any foundation based on need.

In fact, it would have a foundation of NON-need.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Apr 20 10:15:25 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A055B1A0035 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:15:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 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] autolearn=ham
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 33J5hhH-jdoe for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:15:23 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 3C5DB1A0027 for <ietf@ietf.org>; Sun, 20 Apr 2014 10:15:23 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 1DC649560F7; Sun, 20 Apr 2014 13:15:18 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1398014118; bh=GbE9D6F08jjU+M6j6X5+qtdljtFsm7V55/FOrhAku/4=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JCSEP/N/381ZhX5Rrm6Ovi9WzszL2EfeiSWGSqEzflPYMs3jTDj0q6KOiJdkXOwgU 5+gjxU+qX0QW/RszDMUjzM1U4YdsojmGxjnk4Ud/uUUJeefRGSz41uSbK2fsLF5xfI Z0GfkhXMcRc372QaRyp2ve0kvBoE1afUxaoI7WSQ=
Received: from scott-latitude-e6320.localnet (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id DC6A2D043A5; Sun, 20 Apr 2014 13:15:17 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: "why I quit writing internet standards"
Date: Sun, 20 Apr 2014 13:15:16 -0400
Message-ID: <2438778.l2fkdhtpfX@scott-latitude-e6320>
User-Agent: KMail/4.13 (Linux/3.13.0-24-generic; KDE/4.13.0; x86_64; ; )
In-Reply-To: <5353FEF7.2060708@bbiw.net>
References: <CF71721A.180A9%wesley.george@twcable.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320> <5353FEF7.2060708@bbiw.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_HyUEKa2XCdKojhCExnFnpFJCQI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:15:24 -0000

On Sunday, April 20, 2014 10:08:07 Dave Crocker wrote:
> On 4/14/2014 8:28 PM, Scott Kitterman wrote:
> > If that's true, it's my impression it's true because the DMARC proponents
> > insisted any possible working group charter preclude meaningful changes to
> > the base specification because the work was already done.
> 
> That statement is incorrect.
> 
> What we pressed for was to get community rough consensus on the kinds of
> technical work that needed to be done to the -base (core) specification,
> /before/ chartering the effort.
> 
> This was explicitly to avoid the trap of declaring the existing spec
> unstable -- and that's what starting an open-ended development effort
> automatically does -- when there was no demonstrated need to do that.
> 
> In spite of repeated efforts -- in at least two venues -- to get folks
> to state what work they thought was needed and to get community support
> for that work, no tasks were produced.
> 
> That meant that any wg charter permitting changes to the protocol would
> have been entirely without any foundation based on need.
> 
> In fact, it would have a foundation of NON-need.

Right.  The alternate defense against a WG charter that allowed for anything 
more than wordsmithing was to insist that proponents of a working group go do 
the work of a working group to evaluate the protocol and figure out if it 
needed any changes before such a working group would be chartered.

That didn't make any more sense.

Scott K


From nobody Sun Apr 20 10:19:15 2014
Return-Path: <lrosen@rosenlaw.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4658B1A0035 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:19:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.734
X-Spam-Level: *
X-Spam-Status: No, score=1.734 tagged_above=-999 required=5 tests=[BAYES_60=1.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 3oOLCAMh1TSy for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:19:09 -0700 (PDT)
Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) by ietfa.amsl.com (Postfix) with SMTP id 16E9E1A0027 for <ietf@ietf.org>; Sun, 20 Apr 2014 10:19:09 -0700 (PDT)
Received: (qmail 26957 invoked by uid 0); 20 Apr 2014 17:19:03 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy3.mail.unifiedlayer.com with SMTP; 20 Apr 2014 17:19:03 -0000
Received: from box597.bluehost.com ([66.147.242.197]) by CMOut01 with  id sHJx1n00U4GF2VN01HK00u; Sun, 20 Apr 2014 11:19:03 -0600
X-Authority-Analysis: v=2.1 cv=EOmVjTpC c=1 sm=1 tr=0 a=NRJ8aB/FPT4S3utBguGD+g==:117 a=NRJ8aB/FPT4S3utBguGD+g==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=qiyaGL18aqoA:10 a=7xXQEuv9rCMA:10 a=CAIbOuo8jNoA:10 a=4F77bVRYAAAA:8 a=FxJxCPAPh0wA:10 a=AqkBdCNi7UMA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10 a=L76QRiJ-AAAA:8 a=1VpVyRb2AAAA:8 a=t57HkFW4pF0Q_llFcNAA:9 a=CjuIK1q_8ugA:10 a=SqxYWZjetj4A:10 a=TImqNlVd7iMA:10 a=nUHtMES9Q_IA:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=_cBuHmD8xkDdiJ2ufy4A:9 a=_wCxm8EmcjRp5m8w:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=rosenlaw.com; s=default;  h=Content-Type:MIME-Version:Message-ID:Date:Subject:Cc:To:From:Reply-To; bh=0TSZYhfwIWR0Ng2K3bAmUPCC+/gPFhoYKyuKUvTgLZ4=;  b=FvUb7vTc+CUKNSvXj9yuI/0D1riVrw4JwR/tQ/kg2KyV5TY4bxU4bCWyfa0oe2xVTHjM4IKMzF9GI4eW+9fYYXFj5E9uTR4EhO2IhLsXc/937x0xA9839Ci7lVOQAe61;
Received: from [70.36.224.178] (port=26098 helo=Lawrencei) by box597.bluehost.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from <lrosen@rosenlaw.com>) id 1WbvOH-0002G1-H7; Sun, 20 Apr 2014 11:18:53 -0600
From: "Lawrence Rosen" <lrosen@rosenlaw.com>
To: <ietf@ietf.org>
Subject: Author disclosures and conflict of interest
Date: Sun, 20 Apr 2014 10:18:11 -0700
Message-ID: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0035_01CF5C81.D6C53A20"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: Ac9cuQfV+jrpfzgqRbStoWgGRsCahQ==
Content-Language: en-us
X-Identified-User: {1397:box597.bluehost.com:rosenla1:rosenlaw.com} {sentby:smtp auth 70.36.224.178 authed with lrosen@rosenlaw.com}
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/F4chLD2lQLmMRs-M8liwE6T67to
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: lrosen@rosenlaw.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:19:13 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0035_01CF5C81.D6C53A20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I've been skimming recent threads  on this list relating to work done (or
not done) at IETF and was reminded of this from Science Magazine
<http://www.sciencemag.org/site/feature/contribinfo/prep/coi.xhtml> :

 


Authorship Form and Conflict-of-Interest Statement


To meet its responsibility to readers and to the public to provide clear and
unbiased scientific results and analyses, Science believes that manuscripts
(including Brevia, Essays, Perspectives, Policy Forums, Reports, Research
Articles, Reviews, and Viewpoints) should be accompanied by clear
disclosures from all authors of the nature and level of their contribution
to the article, their understanding regarding the obligation to share data
and materials, and any affiliations, funding sources, or financial holdings
that might raise questions about possible sources of bias. Before manuscript
acceptance, therefore, authors will be asked to sign an
authorship/conflict-of-interest form. Specific information will be sent to
most authors at the time of manuscript revision.

 <http://www.sciencemag.org/site/feature/contribinfo/prep/coi.pdf>
Authorship Form and Statement of Conflicts of Interest [PDF]

 

Part IV regarding "Conflict of Interest" is particularly relevant to
standards organizations such as IETF. Such a disclosure requirement would
further encourage everyone to trust and implement IETF specifications. 

 

This document follows the recommendations in On Being a Scientist: A Guide
to Responsible Conduct in Research
<http://www.nap.edu/catalog.php?record_id=12192> , The National Academies
Press, Third Edition (2009). 

 

/Larry

 

Lawrence Rosen

Rosenlaw & Einschlag (www.rosenlaw.com <http://www.rosenlaw.com/> ) 

3001 King Ranch Road, Ukiah, CA 95482

Cell: 707-478-8932   Fax: 707-485-1243

 


------=_NextPart_000_0035_01CF5C81.D6C53A20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii"><meta name=3DGenerator content=3D"Microsoft Word 15 =
(filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:inherit;
	panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
h1
	{mso-style-priority:9;
	mso-style-link:"Heading 1 Char";
	margin-top:12.0pt;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:0in;
	margin-bottom:.0001pt;
	page-break-after:avoid;
	font-size:16.0pt;
	font-family:"Calibri Light","sans-serif";
	color:#2E74B5;
	mso-fareast-language:EN-US;
	font-weight:normal;}
h2
	{mso-style-priority:9;
	mso-style-link:"Heading 2 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:18.0pt;
	font-family:"Times New Roman","serif";
	font-weight:bold;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.Heading2Char
	{mso-style-name:"Heading 2 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 2";
	font-family:"Times New Roman","serif";
	mso-fareast-language:EN-GB;
	font-weight:bold;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
span.Heading1Char
	{mso-style-name:"Heading 1 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 1";
	font-family:"Calibri Light","sans-serif";
	color:#2E74B5;}
span.copyrightyear
	{mso-style-name:copyright_year;}
.MsoChpDefault
	{mso-style-type:export-only;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1317613911;
	mso-list-template-ids:865653110;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:"Courier New";
	mso-bidi-font-family:"Times New Roman";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal>I&#8217;ve been skimming recent threads &nbsp;on this =
list relating to work done (or not done) at IETF and was reminded of =
this from <i><a =
href=3D"http://www.sciencemag.org/site/feature/contribinfo/prep/coi.xhtml=
">Science Magazine</a></i>:<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'mso-element:para-border-div;border:none;border-bottom:solid =
#CCCCCC 1.0pt;padding:0in 0in 3.0pt =
0in;background:white;margin-left:.5in;margin-right:0in'><h2 =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;marg=
in-left:0in;background:white;vertical-align:baseline;border:none;padding:=
0in'><span =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:#666666'=
>Authorship Form and Conflict-of-Interest =
Statement<o:p></o:p></span></h2></div><p =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;background:white;vertical-align:baseline=
;outline-style: none;text-align:start;orphans: auto;widows: =
auto;-webkit-text-stroke-width: 0px;word-spacing:0px'><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333'=
>To meet its responsibility to readers and to the public to provide =
clear and unbiased scientific results and analyses,</span><span =
class=3Dapple-converted-space><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333'=
>&nbsp;</span></span><em><span =
style=3D'font-size:10.0pt;font-family:"inherit","serif";color:#333333;bor=
der:none windowtext 1.0pt;padding:0in'>Science</span></em><span =
class=3Dapple-converted-space><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333'=
>&nbsp;</span></span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333'=
>believes that manuscripts (including Brevia, Essays, Perspectives, =
Policy Forums, Reports, Research Articles, Reviews, and Viewpoints) =
should be accompanied by clear disclosures from all authors of the =
nature and level of their contribution to the article, their =
understanding regarding the obligation to share data and materials, and =
any affiliations, funding sources, or financial holdings that might =
raise questions about possible sources of bias. Before manuscript =
acceptance, therefore, authors will be asked to sign an =
authorship/conflict-of-interest form. Specific information will be sent =
to most authors at the time of manuscript =
revision.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in;line-height:12.5pt;background:white;vertical-al=
ign:baseline'><span =
style=3D'font-size:10.0pt;font-family:"inherit","serif";color:#333333'><a=
 =
href=3D"http://www.sciencemag.org/site/feature/contribinfo/prep/coi.pdf">=
<span style=3D'color:#2E6D8F;border:none windowtext =
1.0pt;padding:0in'>Authorship Form and Statement of Conflicts of =
Interest</span></a><span =
class=3Dapple-converted-space>&nbsp;</span>[PDF]<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Part IV regarding &#8220;Conflict of Interest&#8221; =
is particularly relevant to standards organizations such as IETF. Such a =
disclosure requirement would further encourage everyone to trust and =
implement IETF specifications. <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>This =
document follows the recommendations in <i><a =
href=3D"http://www.nap.edu/catalog.php?record_id=3D12192">On Being a =
Scientist: A Guide to Responsible Conduct in Research</a></i>, The =
National Academies Press, Third Edition (2009). <o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>/Larry<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;mso-fareast-language:EN-GB'>Lawrence =
Rosen<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;mso-fareast-language:EN-GB'>Rosenlaw &amp; =
Einschlag (<a href=3D"http://www.rosenlaw.com/">www.rosenlaw.com</a>) =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:9.0pt;mso-fareast-language:EN-GB'>3001 King Ranch =
Road, Ukiah, CA 95482<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US style=3D'font-size:9.0pt;mso-fareast-language:EN-GB'>Cell: =
707-478-8932&nbsp;&nbsp; Fax: 707-485-1243<o:p></o:p></span></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0035_01CF5C81.D6C53A20--


From nobody Sun Apr 20 10:19:28 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 191831A010C for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 9GfC9mmRbW5c for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:19:22 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id A8F761A00FD for <ietf@ietf.org>; Sun, 20 Apr 2014 10:19:21 -0700 (PDT)
Received: (qmail 20350 invoked from network); 20 Apr 2014 17:19:16 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 20 Apr 2014 17:19:16 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=c6e9.53540194.k1404; i=johnl@user.iecc.com; bh=7lLp0Nq8oaYh9K9nLd8L05K6X1lBiUP8o0wqGKR2pmg=; b=hKy3KssM4G2eOufmsX0FO28lfDR1dLxWkHcmjb0QgLcFy84Act1yFPLjQQJQQXlkSbd77OJKFcWj5JaWXGW+652LfAWBrECt/MbMArLshZFhE1iOi8WMP4DfaGFbafTH8fwR5FY2MIXRwUomuvpBwzG0uNpTIwBwuBhoU77fSNJpKPQh9XMbLHlFGVWiEFwzYq5PjeqTyGD8OKHFaemcWcCuKroM8P0LbI8Bw2U++jJU738TgHPxlgOLOmcCeKQr
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=c6e9.53540194.k1404; olt=johnl@user.iecc.com; bh=7lLp0Nq8oaYh9K9nLd8L05K6X1lBiUP8o0wqGKR2pmg=; b=vY08B9mzepBKtlZTGPEAKZOpzobv7dRuZ5+ovMWep8HorGZvhJiu/44TpbSd4KLRgm3C08e+xPIFTlbfLk8LqnDYSldxuRy87QO5YjWnS9VTT3Dm/Z0dJikiOAbBOdM4A98bsL+4+NiRlgAOgON5dlasOpUutg3+GU/QC5PXXygyCJv0cGMm4jZZmQxnfPNwXBf3P9aynmElyrH6+7RA64/gliqlxBEv3yZEsiC7dHeTMkWk4p9ET0zj7Wz8Juwe
Date: 20 Apr 2014 17:18:52 -0000
Message-ID: <20140420171852.50632.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC and yahoo
In-Reply-To: <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/x7mJkA-27D-Dr9VOnJlgYbqzrK8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:19:26 -0000

>I took a different approach.  I left the bounce detection on but switched all @yahoo.com accounts to digest mode. 
>Since the mail now comes from the list instead of the @yahoo.com sender there are no rejections.   Not a perfect
>solution but it prevents harm to non-@yahoo.com list participants.

I don't see how that helps.  The problems occur when a list message
with "From: blah@yahoo.com" is delivered to a Gmail or Hotmail or
Comcast address which follows the DMARC advice and bounces the
message.

R's,
John


From nobody Sun Apr 20 10:21:07 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36EA11A003D for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:21:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 PXFSD-zCXLDO for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:21:05 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 1B1531A0027 for <ietf@ietf.org>; Sun, 20 Apr 2014 10:21:04 -0700 (PDT)
Received: (qmail 20554 invoked from network); 20 Apr 2014 17:20:59 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 20 Apr 2014 17:20:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=df50.535401fb.k1404; i=johnl@user.iecc.com; bh=usXJjbYyIOTYhsxxchkUJ84zJZd5QVXsqHLO+sqwjco=; b=UlM+QNf0eyxVHhQO+r6CgGN+askSGecideqMK7h/UD/gOmRLLDoFZQCCSJ3p0nP726mV8UP97skfjcXZajHGQJDAp6Stf8u/kJlfxS00y/Kgi1nCjTvkUv8VBCSlF0lK1LCSfFXNg7CKusd3kwVBsWxi8huU1HEONh3OIRhTSiW86YTWNdGmo3hgIyU0Rgt9OORavniDxTYmc1dQkP4pbcrlo4p09fPNVcG6yVCZfm8IN+XBloDhTCAOOu5j5U1z
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=df50.535401fb.k1404; olt=johnl@user.iecc.com; bh=usXJjbYyIOTYhsxxchkUJ84zJZd5QVXsqHLO+sqwjco=; b=4pFCXorYv8rYluVaNeh5cAc9ZSPu9aLDt6VFYIrn6kVDjxS97o2l9LAd20EMD1IWv0BwOaaLusNpiPtbiNOpsHPs34zPJ8NywwwwPpEvH5qD2GhIstmfFDNoPn9ncr7sNCbqFmckid3M7OqgG3xS1Zjz169vAKRlFyHwdzQ2Vq9sOjhtGdyJr/hVfJgLYJ4itAfEvijZd0J71cytG1HK3wiChpKTSHam4mGkPWegyZvIRx7HbwOhp1ZCf7oROaIV
Date: 20 Apr 2014 17:20:37 -0000
Message-ID: <20140420172037.57167.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC not-WG, was "why I quit writing internet standards"
In-Reply-To: <5353FEF7.2060708@bbiw.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JKwrgdQ3dvfGjr0-QClK0SMvvLc
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:21:06 -0000

>In spite of repeated efforts -- in at least two venues -- to get folks 
>to state what work they thought was needed and to get community support 
>for that work, no tasks were produced.

My strong impression is that the DMARC cartel considered fixing the
fundamental problems to be out of scope, so that's kind of
tautological.

R's,
John


From nobody Sun Apr 20 10:23:32 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA641A0029 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.138
X-Spam-Level: 
X-Spam-Status: No, score=-101.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 Qwk8maqF56Ol for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:23:26 -0700 (PDT)
Received: from listserv.winserver.com (catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 68A821A0027 for <ietf@ietf.org>; Sun, 20 Apr 2014 10:23:26 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1214; t=1398014598; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=BEsUfqWI2nU42J26r8NRhnrL4iw=; b=tJ4m4q9wpQGiRmJM/qNh 3w+EpR4RWTfOM7WWj8D+ppwZD9FUWayTpcwdAbsHgsA7qtym1LJWVz4gpFgHCZeq C2EoHohRm2jH5YB3jZGHaHR3lmGzm5Zxn1TCeJ2Y02XbFihhdrOcG9WV1PuP3FjL Wa1EQO+FI70jbrl9ZSJOUzs=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 20 Apr 2014 13:23:18 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1123169399.9381.2552; Sun, 20 Apr 2014 13:23:17 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1214; t=1398014519; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=/VdVxPJ Zw9aiSY4zmf8lU61Cnddrhz/QTDwhX2BltGU=; b=jc+6EpxaA8qoTtSCko5HUAE 8gkQaKFZ7bwC8vcpex9iyjhSWTQVlWNYVjA3qXfDO+YoHeRq3q5zJRrt0q2EGac5 rblSpbrZQ3vWK1WghWsrwxqJ0udH4V8mXqgQ1ufhGtplkR9kO8nMzP6qSyFGYMw1 3ZUlEVT2SiizYUPfwkH0=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 20 Apr 2014 13:21:59 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1142695671.9.12016; Sun, 20 Apr 2014 13:21:58 -0400
Message-ID: <5354027E.4090701@isdg.net>
Date: Sun, 20 Apr 2014 13:23:10 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Jeffrey Altman <jaltman@secure-endpoints.com>,  Theodore Ts'o <tytso@mit.edu>
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com>
In-Reply-To: <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/IFkXNep-fBZ-dPBHwkm0TM0shYE
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:23:31 -0000

On 4/20/2014 12:52 PM, Jeffrey Altman wrote:

>
> I took a different approach.  I left the bounce detection on but switched all @yahoo.com accounts to digest mode.  Since the mail now comes from the list instead of the @yahoo.com sender there are no rejections.   Not a perfect solution but it prevents harm to non-@yahoo.com list participants.
>

Thats a good tip (Digest Mode) to pass on to our list operators.  Thanks.

However, what you going to do with when other domains begin to flip on 
the strict DMARC policy switch.  There will be more domains doing this 
now that Yahoo is showing the payoff is high in increasing the 
security quality of their domain.

Keep in mind that this is just about dealing with the legacy existing 
user accounts. You SHOULD still honor the policy for at least new 
subscribers from yahoo.com accounts.  You SHOULD also honor the policy 
for new submissions. But you believe you MAY ignore it and do some 
things to get around the domain's security policy.

The key is how to do all this in an automated protocol fashion, and it 
should begin with first honoring and correcting the DMARC draft 
specification for 3rd party resigner operations which it lacks.

-- 
HLS



From nobody Sun Apr 20 10:26:58 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF65A1A0035 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:26:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.872
X-Spam-Level: 
X-Spam-Status: No, score=-2.872 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 ZoSTu2p7OeEL for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:26:52 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C0C201A0029 for <ietf@ietf.org>; Sun, 20 Apr 2014 10:26:52 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WbvVn-000Hu6-08; Sun, 20 Apr 2014 13:26:39 -0400
Date: Sun, 20 Apr 2014 13:26:38 -0400
From: John C Klensin <john-ietf@jck.com>
To: Jeffrey Altman <jaltman@secure-endpoints.com>
Subject: Re: DMARC and yahoo
Message-ID: <4948F093F369F051CAF0B810@[192.168.1.128]>
In-Reply-To: <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gYIP6pZQ7utkaOahp4V590FQgt8
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Theodore Ts'o <tytso@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:26:57 -0000

--On Sunday, 20 April, 2014 12:52 -0400 Jeffrey Altman
<jaltman@secure-endpoints.com> wrote:

>...
> I took a different approach.  I left the bounce detection on
> but switched all @yahoo.com accounts to digest mode.  Since
> the mail now comes from the list instead of the @yahoo.com
> sender there are no rejections.   Not a perfect solution but
> it prevents harm to non-@yahoo.com list participants.

IMO, this is quite elegant.  The Yahoo users continue to get the
messages, you don't get cluttered by rejection-related
complaints, and those Yahoo users who don't like the digest form
can take it up with Yahoo or find other accounts to use.

   john
 




From nobody Sun Apr 20 10:36:26 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 828931A0040 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:36:24 -0700 (PDT)
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] autolearn=ham
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 s_thZOSs2O2i for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:36:20 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 531291A0029 for <ietf@ietf.org>; Sun, 20 Apr 2014 10:36:20 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3KHaCfH013141 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 20 Apr 2014 10:36:15 -0700
Message-ID: <5354050D.4050007@dcrocker.net>
Date: Sun, 20 Apr 2014 10:34:05 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: DMARC not-WG, was "why I quit writing internet standards"
References: <20140420172037.57167.qmail@joyce.lan>
In-Reply-To: <20140420172037.57167.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 20 Apr 2014 10:36:15 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6Z06zc0S6aHvaIFVTT-u-1_3YKQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:36:24 -0000

On 4/20/2014 10:20 AM, John Levine wrote:
>> In spite of repeated efforts -- in at least two venues -- to get folks
>> to state what work they thought was needed and to get community support
>> for that work, no tasks were produced.
>
> My strong impression is that the DMARC cartel considered fixing the
> fundamental problems to be out of scope, so that's kind of
> tautological.


John,

I have no idea what you are referring to.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Apr 20 10:52:35 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5CE11A0029 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:52:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.138
X-Spam-Level: 
X-Spam-Status: No, score=-101.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 snSScjkSpHui for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 10:52:28 -0700 (PDT)
Received: from listserv.winserver.com (mail.catinthebox.net [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 1951A1A0035 for <ietf@ietf.org>; Sun, 20 Apr 2014 10:52:28 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=519; t=1398016333; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=d2L+jBQWTkZNEGlC5ENcfWlOkzs=; b=oCz7/Ud9kdEtHHpT/N/Z gBg5/CT42AA7u1vIHuBd6KwgsWxyig+NZuZJHalxIINqWSJjb821VEhiaUNbnub1 QmdrXxzX63YxD9/52vFnRwuM7fWL36ihx3LL4I/x9OOJQniTbFsZHXfr+1XEgFdV mJ7ReZkptaGHEccBRnalDAw=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 20 Apr 2014 13:52:13 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1124904520.9381.3208; Sun, 20 Apr 2014 13:52:12 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=519; t=1398016258; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=lzAZzPf tEcG2QGUfgJYsWqOLF203MPyxcKRosObRMfI=; b=Ur9R9BpGzitIyLK0oMx3Fvc fJ6WVNGhZLYwA9j1bW8svNTk8430bYkzCdYZJpUucREVSkYxlikRFWPWBuWfLTt2 OSEaqjUGAgQj8UDNdlKsoMOAoqWLrRPTdCsN/juQi4ulbE/IaaFkLSDd1FF7LWO4 p7Z1Jz/vf+O9vYjJcppw=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 20 Apr 2014 13:50:58 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1144433937.9.12272; Sun, 20 Apr 2014 13:50:57 -0400
Message-ID: <53540949.5080601@isdg.net>
Date: Sun, 20 Apr 2014 13:52:09 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC not-WG, was "why I quit writing internet standards"
References: <20140420172037.57167.qmail@joyce.lan>
In-Reply-To: <20140420172037.57167.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QwkvefmXv-dBnCAaVX4OTaCTyIA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 17:52:32 -0000

>> In spite of repeated efforts -- in at least two venues -- to get folks
>> to state what work they thought was needed and to get community support
>> for that work, no tasks were produced.
>
> My strong impression is that the DMARC cartel considered fixing the
> fundamental problems to be out of scope, so that's kind of
> tautological.

I also got the impression that the "IETF DKIM cartel" considered 
fixing fundamental problems of author domain signing practices to be 
out of scope as well.

-- 
HLS



From nobody Sun Apr 20 11:20:30 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C81291A003D for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 11:20:27 -0700 (PDT)
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] autolearn=ham
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 pz72309vBtZw for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 11:20:23 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0506A1A002A for <ietf@ietf.org>; Sun, 20 Apr 2014 11:20:22 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3KIKEmY013713 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 20 Apr 2014 11:20:18 -0700
Message-ID: <53540F60.7080909@dcrocker.net>
Date: Sun, 20 Apr 2014 11:18:08 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320> <5353FEF7.2060708@bbiw.net> <2438778.l2fkdhtpfX@scott-latitude-e6320>
In-Reply-To: <2438778.l2fkdhtpfX@scott-latitude-e6320>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 20 Apr 2014 11:20:18 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BLcThrvSddiM5u5WIfdJLTlkSIg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 18:20:28 -0000

On 4/20/2014 10:15 AM, Scott Kitterman wrote:
> Right.  The alternate defense against a WG charter that allowed for anything
> more than wordsmithing was to insist that proponents of a working group go do
> the work of a working group to evaluate the protocol and figure out if it
> needed any changes before such a working group would be chartered.


Defense is an interest choice of words.  It tends to imply an obligation 
to start a working group even when there is no work known to be needed.

Working groups are expensive.  The costs they incur are justified only 
when there is known to be a need.

Requiring clear statements about the need is not 'defensive'; it is 
merely being professional and responsible.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Apr 20 11:26:04 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8C171A005A for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 11:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_42=0.6, SPF_PASS=-0.001] autolearn=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 v8SBHsfS7RWt for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 11:26:01 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com [IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 818AA1A0029 for <ietf@ietf.org>; Sun, 20 Apr 2014 11:26:01 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id lf10so3029198pab.13 for <ietf@ietf.org>; Sun, 20 Apr 2014 11:25:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CY9x4oJ85Ac/wFoOhwsVJUHQ9X5XXxNQzDG6c9AYY+E=; b=jDVKYsF97waK8X8+gw91W3HqobQzebyy5/Y653cb1Yq9+sBQU+xB1w2LxJQ91U0IBV w7y7Wwem6S1LEu3ANQIR497bLGTiq4Q6DcF2E1K8VhylMf1/IALrScnQ1/jW+gCCS1V/ UcOGTy+k8bgZrvtYxMMhQxHo5z1MOPNq4pvsT/n3AcySUIQ4pOBgwqsnCnXdykbL+cWb 5bIMRBzRWNc2DFYTKm5lktz6AmJ5e51EOUx1WFsA1olY1NLlH0ycGlSLS32ewMqOaybv WSct7KRtvPIFBawbVqp+A+QnXGp0t7XrasFZmuxTNEFQETlTKYREOMqCy9PLVZSrWe41 dB4w==
X-Received: by 10.68.221.42 with SMTP id qb10mr33858639pbc.65.1398018356855; Sun, 20 Apr 2014 11:25:56 -0700 (PDT)
Received: from ?IPv6:2601:9:7680:203:959f:4446:19b2:81ad? ([2601:9:7680:203:959f:4446:19b2:81ad]) by mx.google.com with ESMTPSA id ei4sm73038825pbb.42.2014.04.20.11.25.55 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Apr 2014 11:25:55 -0700 (PDT)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <5353FEF7.2060708@bbiw.net>
Date: Sun, 20 Apr 2014 11:25:56 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB5D3900-BB09-4C4A-B52C-46349C086927@gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <534C067D.8080506@meetinghouse.net> <CAL0qLwa5CRwxn0V=7D84KFv9K_u5W5L+PPUXc3KPkD0YHkNo1w@mail.gmail.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320> <5353FEF7.2060708@bbiw.net>
To: Dave Crocker <dcrocker@bbiw.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gT8_pEEv4zGVjpSogb4vL6L7R-M
Cc: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 18:26:03 -0000

On Apr 20, 2014, at 10:08 AM, Dave Crocker <dcrocker@bbiw.net> wrote:

> On 4/14/2014 8:28 PM, Scott Kitterman wrote:
>> If that's true, it's my impression it's true because the DMARC =
proponents
>> insisted any possible working group charter preclude meaningful =
changes to the
>> base specification because the work was already done.
>=20
>=20
> That statement is incorrect.
>=20
> What we pressed for was to get community rough consensus on the kinds =
of technical work that needed to be done to the -base (core) =
specification, /before/ chartering the effort.
>=20
> This was explicitly to avoid the trap of declaring the existing spec =
unstable -- and that's what starting an open-ended development effort =
automatically does -- when there was no demonstrated need to do that.
>=20
> In spite of repeated efforts -- in at least two venues -- to get folks =
to state what work they thought was needed and to get community support =
for that work, no tasks were produced.
>=20
> That meant that any wg charter permitting changes to the protocol =
would have been entirely without any foundation based on need.
>=20
> In fact, it would have a foundation of NON-need.

Dear Dave,

Each group sees need differently.  The need driving DMARC was to prevent =
recipients being flooded by an onslaught of transactional phishing =
attempts that also involved establishing improved feedback to facilitate =
take-downs.  Without this protection, there would be a high rate of =
customer loss, at least according to numbers provided by PayPal.  They =
felt handling their domain's email policy by setting up arrangements =
with each ESP did not scale.

That said, DMARC was never intended to address needs beyond the narrow =
scope of high value transactional email. There were early warning signs =
as well. Even Paypal employees initially posted to mailing-lists in =
clear conflict with their DMARC policy.  That behavior was then replaced =
by linkedin.com, e-ngine.nl, junc.eu, and yahoo.com.  There should have =
been clear warnings rather than expecting ESPs to deal with a flood of =
complaints. =20

There is not enough header or transactional bandwidth to expect each =
email to authorize individual third-parties.  The original TPA =
specification would have been able to address this with very low =
overhead.  Is it reasonable to expect user desired third-party services =
to carry a high cryptographic burden for each unique message =
destination.  It seems better to expect these services to simply verify =
their domain by currently available means.  It is also common to find =
List-ID header fields declaring the path taken that can also be =
specified using TPA. TPA use could the be declared in conjunction with =
DMARC to allow each domain seeking protection from DMARC to make =
specific exceptions and effectively react to abuse.

Had SMTP been properly federated, none of this would have become a =
problem, and it would have also avoided pervasive monitoring.=20

Regards,
Douglas Otis



From nobody Sun Apr 20 12:44:08 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D5B31A0007 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 12:44:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.602
X-Spam-Level: 
X-Spam-Status: No, score=-100.602 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 38PJPr_PHWkZ for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 12:44:00 -0700 (PDT)
Received: from news.winserver.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 2D1EC1A0002 for <ietf@ietf.org>; Sun, 20 Apr 2014 12:43:59 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1895; t=1398023028; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=wTrMAII3dpERXB2eHoHIDXBK/rA=; b=wlS7/TM0BH5U/WpkKwj1 rub98qBbNMTs80AVd2EQvBarYeZHo6xAwm21xpdoyYoYslloJ7xWsq8mj1cGM+Xk e1qibFpENl1n0MaZ6r0qy00fJ/aILK2Vr3nHhqyQwrM8KeQbFgbjGYOVlbxnxyy3 E4soLZiu1w7mZeNuaoLFhqk=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 20 Apr 2014 15:43:48 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1131599974.9381.1388; Sun, 20 Apr 2014 15:43:47 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1895; t=1398022953; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=MqNkUTh +Sfk+GFi3eKjhslSM1R0AUFZ+uNC8TxUGWLo=; b=zLYI+wn89jRzmhdJxFgmCBy Y5C4VVkcLVfRRqTVrzsbxCH2jzIPs+DKMX9IkWq4XpfxOwMdQK5KhID88su63s85 rhBBTbGW9FswpwKTEdFb2BXvgE5B64i9wDIoEG6k0VotcN9KlL5QFiq7B6gTkDIt EWid6nZ6g98hxSYNocAk=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 20 Apr 2014 15:42:32 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1151128984.9.10960; Sun, 20 Apr 2014 15:42:32 -0400
Message-ID: <53542370.9040409@isdg.net>
Date: Sun, 20 Apr 2014 15:43:44 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>,  Dave Crocker <dcrocker@bbiw.net>
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <534C067D.8080506@meetinghouse.net> <CAL0qLwa5CRwxn0V=7D84KFv9K_u5W5L+PPUXc3KPkD0YHkNo1w@mail.gmail.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320> <5353FEF7.2060708@bbiw.net> <AB5D3900-BB09-4C4A-B52C-46349C086927@gmail.com>
In-Reply-To: <AB5D3900-BB09-4C4A-B52C-46349C086927@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/E3zZ5NdRfJq69mEeB8z9juGLVMM
Cc: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 19:44:05 -0000

On 4/20/2014 2:25 PM, Douglas Otis wrote:
>
> That said, DMARC was never intended to address needs beyond the
>narrow scope of high value transactional email.

And unfortunately, this attitude was always wrong. Hate to say, but "I 
told you so."   What the design attitude says is this:

     If the domain is high value, then only applied policy.
     For all others, ignore it.

Well, is is "high value?"  How do you distinguish "value" in an 
anonymous world?  Must everyone have a profile in some Good Reputation 
Databases?  Fee based?  Even if we want this, we are not there yet!!

The seed to all this author domain brush back was born in the 
unfortunate RFC5016 DKIM Signing Practice requirements document last 
minute addition of item 10 in section 5.3 where it strongly mandates 
that a 1st party policy MUST NOT override the 3rd party policy.

    RFC 5016, Section 5.3

    10. SSP MUST NOT provide a mechanism that impugns the existence of
        non-first party signatures in a message.  A corollary of this
        requirement is that the protocol MUST NOT link practices of first
        party signers with the practices of third party signers.

          INFORMATIVE NOTE: the main thrust of this requirement is that
          practices should only be published for that which the publisher
          has control, and should not meddle in what is ultimately the
          local policy of the receiver.

          Refs: Deployment Consideration, Section 4.3.

Just replace the term SSP for DMARC and you have the same thing.  This 
is where all the resistance towards author domain policies began with 
this written stone functional requirement.  This attitude is still 
among us.  Not saying its completely wrong, but it certainly not right 
either.  Yahoo proved it for us.

The irony?

Rather than try to honor policy to keep the security high, we are 
looking for ways to circumvent it.  Ignoring Policy no longer works.

-- 
HLS



From nobody Sun Apr 20 13:27:16 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7711A0030 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 13:27:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 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, FREEMAIL_REPLY=1, SPF_PASS=-0.001] autolearn=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 HjL6f10r6MIp for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 13:27:13 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 6C3B51A002E for <ietf@ietf.org>; Sun, 20 Apr 2014 13:27:13 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id rp16so3063423pbb.12 for <ietf@ietf.org>; Sun, 20 Apr 2014 13:27:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vGLczNEbaVbhtRtIHU2LwogyCs7AB5pmmHWX5OZPrcM=; b=BQ8ZkMyaPXlxAtx1k7sOYf+2PB3d7ZY+MXLurN1yotCKIdHLsqWeRMoBLBNYlyPQ6H USClz1ehc4JJGPjjCn4dxZzWbVR0upw126sagK2cSUmGvnjF5SIOG+anFaUGZuqfIlvG BLPyGIg5nmlWfYp9RjJcAkTXTMfcMqniEhQhcZQ2vddOeY7PRHMuTCL1yPCDpvnR2sJs HyGvIisWE3eRQPLn53ZYO2Fj/2xS9A5kzU5jZX+HSSiexrC34Vr5dxPfeDKrzDqGgDI5 ttuUMWs80/Z0LQ6RnXozKLTvHHjdqqmLKT5CS0tTQgvNEo/mOdPPwASlugwTjc9YaDKN bnUA==
X-Received: by 10.68.132.68 with SMTP id os4mr82589pbb.129.1398025628760; Sun, 20 Apr 2014 13:27:08 -0700 (PDT)
Received: from [192.168.178.20] (136.197.69.111.dynamic.snap.net.nz. [111.69.197.136]) by mx.google.com with ESMTPSA id yv7sm175443227pac.33.2014.04.20.13.27.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Apr 2014 13:27:08 -0700 (PDT)
Message-ID: <53542D90.8030709@gmail.com>
Date: Mon, 21 Apr 2014 08:26:56 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]>
In-Reply-To: <4948F093F369F051CAF0B810@[192.168.1.128]>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cyGCs9yoH8PXMoLhXVtZ9zHuFi4
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Theodore Ts'o <tytso@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 20:27:14 -0000

On 21/04/2014 05:26, John C Klensin wrote:
> 
> --On Sunday, 20 April, 2014 12:52 -0400 Jeffrey Altman
> <jaltman@secure-endpoints.com> wrote:
> 
>> ...
>> I took a different approach.  I left the bounce detection on
>> but switched all @yahoo.com accounts to digest mode.  Since
>> the mail now comes from the list instead of the @yahoo.com
>> sender there are no rejections.   Not a perfect solution but
>> it prevents harm to non-@yahoo.com list participants.
> 
> IMO, this is quite elegant.  The Yahoo users continue to get the
> messages, you don't get cluttered by rejection-related
> complaints, and those Yahoo users who don't like the digest form
> can take it up with Yahoo or find other accounts to use.

Unfortunately they can switch themselves back to normal mode
too. Digest mode is user-settable, and is very annoying because
it munges the Subject header. What's really needed is a DMARC-safe
mode (per subscriber) that optionally rewrites the From.

    Brian


From nobody Sun Apr 20 13:37:46 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC8671A0023 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 13:37:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 juxyvGS2DlKw for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 13:37:42 -0700 (PDT)
Received: from mail-pd0-x235.google.com (mail-pd0-x235.google.com [IPv6:2607:f8b0:400e:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 054CE1A001C for <ietf@ietf.org>; Sun, 20 Apr 2014 13:37:41 -0700 (PDT)
Received: by mail-pd0-f181.google.com with SMTP id p10so2995688pdj.26 for <ietf@ietf.org>; Sun, 20 Apr 2014 13:37:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=wrIc/qNG9CGWGxldtjEYbCGRKjQw/SLMBNU9WjsQMVM=; b=jvu9HiEK8miyTiyPzKzoUMVFrnF4BKmfprUdCY3vrC/L9HyPfFIMdlIGabBcJXt1Ft adpFNkhhcbu+XCsskklp2PTqZNYz3ZQcFae8B/P1RQtR+e8J7crydwdPnL210KdTeyea 5jIDjyNdM7WimI4RSP5hxFS88sHGGsKb7ceXXh0WQ4/KVekJAN53n0HXSJQYcVVeQHEL JN0lRaAXsXulB7K39/Ted/Hfx2d0NZmsLydjJyH5C6GAnnHYF8nwRu6b7KMLF++6W6ez PvFCzgCmB1euwGsr3aqSPZ1uh5DhQK+ZDBQ7IbdFKAesTWuNmijO/jwP00aZ/oihg+Sg 3xGA==
X-Received: by 10.69.20.107 with SMTP id hb11mr33652892pbd.99.1398026257388; Sun, 20 Apr 2014 13:37:37 -0700 (PDT)
Received: from [192.168.178.20] (136.197.69.111.dynamic.snap.net.nz. [111.69.197.136]) by mx.google.com with ESMTPSA id qh2sm175659714pab.13.2014.04.20.13.37.35 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Apr 2014 13:37:36 -0700 (PDT)
Message-ID: <5354300D.2090805@gmail.com>
Date: Mon, 21 Apr 2014 08:37:33 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: One size doesn't fit all [Re: DMARC ....]
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net> <01P6TOCIJM0W00004W@mauve.mrochek.com> <5353E048.5020001@qti.qualcomm.com>
In-Reply-To: <5353E048.5020001@qti.qualcomm.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/F5EpSOh9XzfLG8T2ZYu3S5FhMSw
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 20:37:43 -0000

On 21/04/2014 02:57, Pete Resnick wrote:
> On 4/19/14 10:17 AM, ned+ietf@mauve.mrochek.com wrote:
>> I also think the time has come to try and address the more general
>> problem
>> of misunderstanding and/or misrepresentation of the status of various
>> documents. This probably needs to be addressed through a combination of
>> automatic labeling as well as some explicit statements here and there.
>>
>> And this really needs to be spearheaded by the IESG, not the IAB. I
>> hope the
>> IESG is already considering taking action. If not, they should be.
> 
> The timing has been impeccable. The IESG had been privately talking
> about the "IETF relevance" issue, including why people are bringing
> "done" work to the IETF instead of working inside of the IETF. 

Allow me to repeat something I said a few days ago that probably
got lost in the heat and dust of the "why I quit..." discussion:

We have at least 3 modes of working, each of which has its value:

1. Preemptive standardisation: problem statement first,
then requirements, then design, then standardise, then sit
back and wait for implementation.

2. Parallel standardisation: there's some design work and
maybe some code, then retro-fit requirements, write the specs
as the code evolves, then standardise and hope that the code is
updated to match the spec.

3. Retroactive standardisation: there's some running code that
got itself deployed; write the v1 spec to be compatible with
the code, call it a standard, then develop v1.1 or v2 and
hope the code is updated.

We've done all three, and all with varying degrees of success.
I could give examples, but that would just start arguments ;-).
It isn't reasonable to expect all standards to fit the same
model. And people who don't have the desire to work in any
of these models may well prefer to quit standards work (but
still contribute code to one of the three models).

    Brian

And
> related to "done" work, we have also been discussing the relative merits
> of AD-sponsored documents vs. ISE documents and what the appropriate use
> of IESG and IETF time is for these things. We've had all of that on our
> agenda for our upcoming retreat in a couple of weeks, and planned to
> discuss it with the IAB during a joint meeting. Then this DMARC thing
> happens, and Vidya published her article on "why I quit writing internet
> standards". It could not have been timed better.
> 
> I'm trying to get my head around what we should have done differently on
> this, both tactically and strategically, so that I can summarize it for
> the discussion. But I can say pretty confidently that this is a topic
> frontmost in the minds of IESG folks.
> 
> pr
> 


From nobody Sun Apr 20 13:44:05 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66ABF1A0032 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 13:44:03 -0700 (PDT)
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] autolearn=ham
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 JLTXyHMresbC for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 13:43:58 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D623E1A0030 for <ietf@ietf.org>; Sun, 20 Apr 2014 13:43:58 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3KKhnCt015945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 20 Apr 2014 13:43:53 -0700
Message-ID: <53543107.5090105@dcrocker.net>
Date: Sun, 20 Apr 2014 13:41:43 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com, "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com>
In-Reply-To: <01P6QCMYYMJ000004W@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 20 Apr 2014 13:43:53 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vlNMW3-EGOQQ01jcPRjbY9gg83c
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 20:44:03 -0000

reference quibble...



On 4/16/2014 11:00 PM, ned+ietf@mauve.mrochek.com wrote:
>> On Sat, Apr 12, 2014 at 4:35 PM, <ned+ietf@mauve.mrochek.com> wrote:
>>> The underlying technical issue is that the two technologies DMARC is built
>>> on -
>>> DKIM and SPF - both attach additional/restrictive semantics to
>>> longstanding mail
>>> system fields. (Broadly speaking, From: for DKIM and MAIL FROM for SPF.)
>
>> Something's amiss here.  What new semantics does DKIM attach to From:?  As
>> far as I know, it only requires that the field be signed.  It doesn't
>> require that it be interpreted in a particular way or that it contain any
>> particular value.
>
> I was trying to be brief. Yes, I'm well aware that DKIM can be used in other
> ways. This entire discussion is within the context of DMARC here. Do you
> disagree that DMARC's use of DKIM and SPF assign additional semantics to header
> and envelope from fields respectively?


Not really.  In fact, I fear that that's a bit like saying that TCP 
makes IP a reliable, byte-sequenced protocol...

Rather, DMARC defines its /own, additional/ meaning, but it does not 
change DKIM or SPF.  They do what they've been doing for quite awhile. 
DMARC does something /more/.

Essentially, DMARC takes the domain name used in DKIM d= and/or SPF 
"protected" rfc2321.MailFrom and invents a new requirement, namely that 
that domain name be the one used in the author's rfc2822.From field's 
addr-spec's <domain>.



d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Apr 20 13:55:12 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFA771A0032 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 13:55:08 -0700 (PDT)
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] autolearn=ham
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 VTyXR1Wgy9kP for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 13:55:07 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0C07B1A0023 for <ietf@ietf.org>; Sun, 20 Apr 2014 13:55:07 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3KKswmC016248 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 20 Apr 2014 13:55:01 -0700
Message-ID: <535433A3.5060102@dcrocker.net>
Date: Sun, 20 Apr 2014 13:52:51 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, ned+ietf@mauve.mrochek.com, "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Somebody always claims something (was Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists)
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com>
In-Reply-To: <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 20 Apr 2014 13:55:01 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/80fNreqqrov7jmqTsMbcoORbQBs
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 20:55:09 -0000

On 4/17/2014 12:57 AM, John C Klensin wrote:
> Indeed.  We have had warnings about where the ability of anyone
> to post anything and then claim IETF approval in external
> contexts without any fear of meaningful pushback would lead for
> a long time.  It hasn't been significantly damaging before
> because (i) we have been lucky and (ii) attempts to manipulate
> the mechanisms have come from outsiders, not insiders.  With
> DMARC, the ability to claim IETF responsibility when that is
> handy and that the IETF has no control when _that_ is handy have
> now been utilized by insiders.

We are constantly confusing someone's attempted effect with their actual 
effect.

We need to stop giving other people control over the IETF that way.

Merely by making a claim, the get us to we scurry into fearful action, 
believing we have to prevent such claims.  We are allowing them to 
conduct a denial of service attack on us.  Or rather, by us on ourselves.


 >  That comes after a history of
> the less effective approach of bringing specs into IETF WGs and
> then claiming that fundamentals cannot be changed because they
> were developed by experts in another forum.  As I think Ned
> suggested, the ADSP issue and how it was handled should have
> been another warning sign.  And, with Yahoo's move and its
> consequences (whether they anticipated them or not), we also ran
> out of luck.

With some regularity, over the decades, a large vendor or provider has 
applied a standard -- or modified it -- in a way other than it was 
designed to cover.


>> What I suggested is that we need to have a serious discussion
>> of what, if anything can be done to ameliorate the damage in
>> this case. Others have suggested that we also need to look at
>> how to prevent this from happening in the future. I concur.
>
> agreed.

The IETF has no leverage for preventing the independent and 
consequential actions of a large player in the market.


> I'm also concerned that several of these efforts represent back
> door approaches to deprecating multi-hop email.

Well, that's a substantive point.  And unfortunately I agree with the 
concern.  In fact, it has been impressive to see how readily some 
industry folk dismiss concerns about more complex uses of email, such as 
multi-administration handling of mail in transit.

One /can/ imagine the IETF producing a BCP about the consequences of 
applying it's technologies in various ways that change email's utility.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Apr 20 14:23:56 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05AAE1A0039 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 14:23:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.674
X-Spam-Level: 
X-Spam-Status: No, score=-1.674 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 jzhIIR9UdOTb for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 14:23:50 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [208.79.90.218]) by ietfa.amsl.com (Postfix) with ESMTP id DE5111A003B for <ietf@ietf.org>; Sun, 20 Apr 2014 14:23:50 -0700 (PDT)
Received: from [192.168.2.25] (unknown [99.17.30.3]) by dougbarton.us (Postfix) with ESMTPSA id 0056C22B20 for <ietf@ietf.org>; Sun, 20 Apr 2014 21:23:45 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1398029026; bh=O4QWH7cQSFeAc7auJ77OJlpK20Xb3YobUvI70tpAEFQ=; h=Date:From:To:Subject:References:In-Reply-To; b=VyTA760CFmBYg55I8Gf0P22LVqEzAGpDf8r+8dudBnZPG9+oX43Vi2rpn5Llj1/IK MMvSj6cUWrY5RI5pdYiRH91ruZFDfP9aQ4/J0F4p0yjKAl7R/798l5CNRY+E9qjT+v PN4oTugbGCSq3e83qC+UD8BHxZi7UikmSEgR+b2Q=
Message-ID: <53543ADA.8010204@dougbarton.us>
Date: Sun, 20 Apr 2014 14:23:38 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]>
In-Reply-To: <4948F093F369F051CAF0B810@[192.168.1.128]>
X-Enigmail-Version: 1.6
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9Mb7M3k8PRjawoNcl58X-s6D8ww
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 21:23:55 -0000

On 04/20/2014 10:26 AM, John C Klensin wrote:
>
>
> --On Sunday, 20 April, 2014 12:52 -0400 Jeffrey Altman
> <jaltman@secure-endpoints.com> wrote:
>
>> ...
>> I took a different approach.  I left the bounce detection on
>> but switched all @yahoo.com accounts to digest mode.  Since
>> the mail now comes from the list instead of the @yahoo.com
>> sender there are no rejections.   Not a perfect solution but
>> it prevents harm to non-@yahoo.com list participants.
>
> IMO, this is quite elegant.  The Yahoo users continue to get the
> messages, you don't get cluttered by rejection-related
> complaints, and those Yahoo users who don't like the digest form
> can take it up with Yahoo or find other accounts to use.

The issue with @yahoo.com and DMARC is not the @yahoo.com users' ability 
to receive mail, it's their ability to send mail to the list with From: 
*@yahoo.com and have it be received by list subscribers who implement 
strict DMARC policies which honor Yahoo!'s p=reject.

It's not clear how setting the @yahoo.com users to digest mode helps 
this situation at all.

Doug


From nobody Sun Apr 20 14:30:52 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7711A003B for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 14:30:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 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] autolearn=ham
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 WBaVfvvAb2hd for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 14:30:46 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id A75D71A0039 for <ietf@ietf.org>; Sun, 20 Apr 2014 14:30:46 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id AA64AD0445A; Sun, 20 Apr 2014 17:30:41 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1398029441; bh=PoVbycJ2AP9ctueuJD3Iy2KUk4ccofM3Tfplr/9qhWg=; h=In-Reply-To:References:Subject:From:Date:To:From; b=d6DYQOuZPFJsUgrje7DTWd3+8ol3HZj5/ZyQaKDb1F+LVf2RyiXl/vRfaKMfQK+/v wr0Wm4eNFQrIfbE72Pjt3PAofjJsJyWUYdcpUdIvj9Qi4mpoGj5/QPhA11upEVdvjf arHs6l6IzNRjGJzKVTFDcFRMwYa5PvW6G1U/k7P8=
Received: from [192.168.111.116] (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 6B3F9D04102; Sun, 20 Apr 2014 17:30:41 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <53540F60.7080909@dcrocker.net>
References: <CF71721A.180A9%wesley.george@twcable.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320> <5353FEF7.2060708@bbiw.net> <2438778.l2fkdhtpfX@scott-latitude-e6320> <53540F60.7080909@dcrocker.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Subject: Re: "why I quit writing internet standards"
From: Scott Kitterman <scott@kitterman.com>
Date: Sun, 20 Apr 2014 17:30:39 -0400
To: ietf@ietf.org
Message-ID: <2f32f665-ce89-44eb-bce1-fd95a4d8fc5f@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tC32i-fXZz1MV_6HVQYY_1Im3MU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 21:30:51 -0000

On April 20, 2014 2:18:08 PM EDT, Dave Crocker <dhc@dcrocker.net> wrote:
>On 4/20/2014 10:15 AM, Scott Kitterman wrote:
>> Right.  The alternate defense against a WG charter that allowed for
>anything
>> more than wordsmithing was to insist that proponents of a working
>group go do
>> the work of a working group to evaluate the protocol and figure out
>if it
>> needed any changes before such a working group would be chartered.
>
>
>Defense is an interest choice of words.  It tends to imply an
>obligation 
>to start a working group even when there is no work known to be needed.
>
>Working groups are expensive.  The costs they incur are justified only 
>when there is known to be a need.
>
>Requiring clear statements about the need is not 'defensive'; it is 
>merely being professional and responsible.

That's one theory. Considering the current state of play in which DMARC isn't even being submitted to the IETF, the alternative theory that the developers of DMARC were not interested in anything other than a rubber stamp approval from the IETF seems to me to be much more consistent with the available information. 

I think I'm done with this argument. 

Scott K


From nobody Sun Apr 20 14:37:40 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA84C1A0051 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 14:37:37 -0700 (PDT)
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] autolearn=ham
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 x7GEo1R0cCrk for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 14:37:36 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4A0B51A004B for <ietf@ietf.org>; Sun, 20 Apr 2014 14:37:36 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3KLbSJ9016932 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 20 Apr 2014 14:37:31 -0700
Message-ID: <53543D99.3040604@dcrocker.net>
Date: Sun, 20 Apr 2014 14:35:21 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
Subject: Re: "why I quit writing internet standards"
References: <CF71721A.180A9%wesley.george@twcable.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320> <5353FEF7.2060708@bbiw.net> <2438778.l2fkdhtpfX@scott-latitude-e6320> <53540F60.7080909@dcrocker.net> <2f32f665-ce89-44eb-bce1-fd95a4d8fc5f@email.android.com>
In-Reply-To: <2f32f665-ce89-44eb-bce1-fd95a4d8fc5f@email.android.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sun, 20 Apr 2014 14:37:31 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6zivnipky9h-e6fZ8be1nAxHFjA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 21:37:38 -0000

On 4/20/2014 2:30 PM, Scott Kitterman wrote:

> On April 20, 2014 2:18:08 PM EDT, Dave Crocker <dhc@dcrocker.net>
> wrote:
>> Requiring clear statements about the need is not 'defensive'; it
>> is merely being professional and responsible.
>
> That's one theory. Considering the current state of play in which
> DMARC isn't even being submitted to the IETF, the alternative theory
> that the developers of DMARC were not interested in anything other
> than a rubber stamp approval from the IETF seems to me to be much
> more consistent with the available information.
>
> I think I'm done with this argument.


Yes, it's always good to end with an attack on other people's integrity.

So much more comforting than dealing with the substance of the issue.
Definitely better to dismiss that out of hand.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Apr 20 15:12:58 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11EF61A0066 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 15:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level: 
X-Spam-Status: No, score=-2.002 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] autolearn=ham
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 TlDsVFqaEkzr for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 15:12:48 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id BC9241A0062 for <ietf@ietf.org>; Sun, 20 Apr 2014 15:12:48 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 95ECCD04580; Sun, 20 Apr 2014 18:12:43 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1398031963; bh=81MZ9P2Dh/qdbUZdFo1a+VAjQY1dNKEtBUq9alk+E5Q=; h=In-Reply-To:References:Subject:From:Date:To:From; b=ZGmoU0YtK+wjVJ8UvkmL+nPFACw/caIy3EEPR7MyaNl+5w1JOTaeLNK7V2ua/nYbG QchwL3KSjkI/aZ6DnpP9GuXexSlKiwjPGYb6cVILQJ+bnuOc6HLIzI8NaY29hMfpe0 FSqrTqtn7Y/DWOosGaUZRYIKSngf1FfDhiPQA5F0=
Received: from [192.168.111.116] (static-72-81-252-21.bltmmd.fios.verizon.net [72.81.252.21]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id 4ECC6D04152; Sun, 20 Apr 2014 18:12:43 -0400 (EDT)
User-Agent: K-9 Mail for Android
In-Reply-To: <53543D99.3040604@dcrocker.net>
References: <CF71721A.180A9%wesley.george@twcable.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320> <5353FEF7.2060708@bbiw.net> <2438778.l2fkdhtpfX@scott-latitude-e6320> <53540F60.7080909@dcrocker.net> <2f32f665-ce89-44eb-bce1-fd95a4d8fc5f@email.android.com> <53543D99.3040604@dcrocker.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Subject: Re: "why I quit writing internet standards"
From: Scott Kitterman <scott@kitterman.com>
Date: Sun, 20 Apr 2014 18:12:41 -0400
To: ietf@ietf.org
Message-ID: <76f887f0-7ef2-4576-a15c-59d537bb85b9@email.android.com>
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qaa52hGmjWwHwKP6UHo4PI6dT7M
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 22:12:54 -0000

On April 20, 2014 5:35:21 PM EDT, Dave Crocker <dhc@dcrocker.net> wrote:
>On 4/20/2014 2:30 PM, Scott Kitterman wrote:
>
>> On April 20, 2014 2:18:08 PM EDT, Dave Crocker <dhc@dcrocker.net>
>> wrote:
>>> Requiring clear statements about the need is not 'defensive'; it
>>> is merely being professional and responsible.
>>
>> That's one theory. Considering the current state of play in which
>> DMARC isn't even being submitted to the IETF, the alternative theory
>> that the developers of DMARC were not interested in anything other
>> than a rubber stamp approval from the IETF seems to me to be much
>> more consistent with the available information.
>>
>> I think I'm done with this argument.
>
>
>Yes, it's always good to end with an attack on other people's
>integrity.
>
>So much more comforting than dealing with the substance of the issue.
>Definitely better to dismiss that out of hand.

Sigh.  Okay. One more.

I gave my opinion.   

There's a substantial body of discussion on both public DMARC lists and the IETF DMARC list about how we got where we are. I'm sure there were plenty of private discussions too.

Anyone who cares can review the public portions of the record and form their own opinion.   Having a difference of opinion over how it should've been done is not an attack on anyone's integrity. 

I'm certainly not the one who (I'm paraphrasing from memory, so this may not be exactly right) accused unnamed IETF insiders of subverting IETF processes.  That struck me as an attack on someone's integrity, but it wasn't me doing it.

You and I haven't and won't agree on this, so I don't see the point of wasting everyone's time continuing to argue about it. To the extent that there's a substantive issue or question at stake, I think people who care should go read the lists' archives and reach their own conclusions. 

Scott K


From nobody Sun Apr 20 15:21:09 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FF221A0063 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 15:21:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.402
X-Spam-Level: 
X-Spam-Status: No, score=-101.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 fPt5FJmS44kS for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 15:21:04 -0700 (PDT)
Received: from mail.santronics.com (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 98EFD1A0059 for <ietf@ietf.org>; Sun, 20 Apr 2014 15:21:04 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1886; t=1398032449; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=tE7xwKOlbF4aZTqQKR45I6+uyCM=; b=vR8iWQmuklOTfB6dXJJ4 Y0kjbn2XnOHYjje0MQTiiFcSLOMvfewvizyddZf5n2DU2stDUpjKQojUQg5Y6ZEo b4LwwnzGsxpOm6qx0eCb5OOEefj/xhGQdHZsAyNFdCSuPJ7OJ4rAbnC7qyGP4kg3 4s7yPR3sAFKEICDge/5NLHY=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 20 Apr 2014 18:20:49 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from hector.wildcatblog.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1141020734.9381.1356; Sun, 20 Apr 2014 18:20:48 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1886; t=1398032374; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=AP0egvF Aem1KqW/XJINrvvvH3cYkVyeaOfX45eqVbBM=; b=p52GA7v6dRgNrWUuJ9xBAVQ akorx9Y/EcbH00GeS6uryP+PV96TOm+UcgmrBsoY3KvBxQjj8ovXBGkfjzTpTxFJ lRu7KZI/1dk28Wa9OzKZ/kFY+CF+TQ/EEFLwF0XkeSoeFbKgViKwp6oTPDQbuEOq NunJvv8/5EyQDJD3rcnQ=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sun, 20 Apr 2014 18:19:34 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1160550718.9.11368; Sun, 20 Apr 2014 18:19:33 -0400
Message-ID: <5354483E.2080806@isdg.net>
Date: Sun, 20 Apr 2014 18:20:46 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Doug Barton <dougb@dougbarton.us>, ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]> <53543ADA.8010204@dougbarton.us>
In-Reply-To: <53543ADA.8010204@dougbarton.us>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tjl2pF4vU610K9APOOGGpmAAqQ0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 22:21:08 -0000

On 4/20/2014 5:23 PM, Doug Barton wrote:

> The issue with @yahoo.com and DMARC is not the @yahoo.com users'
> ability to receive mail, it's their ability to send mail to the list
> with From: *@yahoo.com and have it be received by list subscribers who
> implement strict DMARC policies which honor Yahoo!'s p=reject.

Or basically, anyone with a p=reject policy will be rejected by
DMARC compliant receivers if its not signed by the author domain.  We 
have been calling this 3rd party signatures. See RFC5016 (Requirements 
for a DKIM Signing Practices Protocol) for the definition:

    http://tools.ietf.org/html/rfc5016#page-3

    o  First Party Address: for DKIM, a first party address is defined to
       be the [RFC2822].From address in the message header; a first party
       address is also known as an Author address.

    o  First Party Signature: a first party signature is a valid
       signature where the signing identity (the d= tag or the more
       specific identity i= tag) matches the first party address.
       "Matches" in this context is defined in [RFC4871].

    o  Third Party Signature: a third party signature is a valid
       signature that does not qualify as a first party signature.  Note
       that a DKIM third party signature is not required to correspond to
       a header field address such as the contents of Sender or List-Id,
       etc.

DMARC has no such separation support. Thats the problem. You know, for 
the IETF purist, this is an violation of RFC5016 if it uses the term 
DKIM in its documentation as a conforming solution.  Either that, or 
it fell thru the crack.  Lets hope its the latter and we can fix this 
problem.

> It's not clear how setting the @yahoo.com users to digest mode helps
> this situation at all.

For our MLS digest mode, the signed digest message is 5322.From the 
list domain.  Can't tell you off hand how other MLS will do this.


-- 
HLS



From nobody Sun Apr 20 16:12:19 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DBB471A007B for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 16:12:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 818b2FM_ifrv for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 16:12:12 -0700 (PDT)
Received: from mail-pb0-x235.google.com (mail-pb0-x235.google.com [IPv6:2607:f8b0:400e:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 23A451A0072 for <ietf@ietf.org>; Sun, 20 Apr 2014 16:12:12 -0700 (PDT)
Received: by mail-pb0-f53.google.com with SMTP id rp16so3126014pbb.12 for <ietf@ietf.org>; Sun, 20 Apr 2014 16:12:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CzX+ZHqXdpBlQeBucrih+1vq9k1gxRn21XY/YA9y4Jw=; b=VbynKQDJXZehgFfb3sBQKnA0RXzyLlSbhTv68DSKU6lTBB6mFmAytUgCxmajV2Kthm e62a7wH5OBj6QORL/x41s8c0pHMYtfEhetvd3ulmxoym2RdzM26CNECpeb2IH8evgmRR 7V+v0lodtwxBYpRBroD4JbQ1GtgE9Tn6cPlQF4jpUW/W6nNxBTiia8F1N6zs5cXNzJMk bcBtPNwRfQpaqXyDq4uTE+AMl7QR8q6Iw3gQKStOq5+CosN+SLfgFVMi1bp4r2fNwlFP yWm+PBuZijsndpah/VPBd0+QZ8vehnWYCBAKCM8DkW/mmFGxeM/XeLuo+v0sM3hCTHhx Rc0Q==
X-Received: by 10.66.219.6 with SMTP id pk6mr34916360pac.9.1398035527486; Sun, 20 Apr 2014 16:12:07 -0700 (PDT)
Received: from [192.168.2.116] (c-67-188-1-12.hsd1.ca.comcast.net. [67.188.1.12]) by mx.google.com with ESMTPSA id my6sm73864398pbc.36.2014.04.20.16.12.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 20 Apr 2014 16:12:05 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: "why I quit writing internet standards"
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <53542370.9040409@isdg.net>
Date: Sun, 20 Apr 2014 16:12:11 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <8274AE7B-A6A0-4253-B103-6EB6EC17F017@gmail.com>
References: <CF71721A.180A9%wesley.george@twcable.com> <534C067D.8080506@meetinghouse.net> <CAL0qLwa5CRwxn0V=7D84KFv9K_u5W5L+PPUXc3KPkD0YHkNo1w@mail.gmail.com> <4756885.Eo3b3po9Vj@scott-latitude-e6320> <5353FEF7.2060708@bbiw.net> <AB5D3900-BB09-4C4A-B52C-46349C086927@gmail.com> <53542370.9040409@isdg.net>
To: Hector Santos <hsantos@isdg.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MI7-pEJdq_mmW6RSegEWmxTwWGw
Cc: Scott Kitterman <scott@kitterman.com>, Dave Crocker <dcrocker@bbiw.net>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Apr 2014 23:12:17 -0000

On Apr 20, 2014, at 12:43 PM, Hector Santos <hsantos@isdg.net> wrote:

> On 4/20/2014 2:25 PM, Douglas Otis wrote:
>>=20
>> That said, DMARC was never intended to address needs beyond the
>> narrow scope of high value transactional email.
>=20
> And unfortunately, this attitude was always wrong. Hate to say, but "I =
told you so."   What the design attitude says is this:
>=20
>    If the domain is high value, then only applied policy.
>    For all others, ignore it.

Dear Hector,

You missed an important term, "transactional". Transactional email is =
normally NOT relayed through things like mailing-lists for example.

"high value" are messages likely to invoke responses which in turn =
invites a high level of phishing.  In such limited scenarios, DMARC =
makes very good sense.

> Rather than try to honor policy to keep the security high, we are =
looking for ways to circumvent it.  Ignoring Policy no longer works.

Locking the =46rom header field to a specific source for general user =
mail clearly does not work and those asserting DMARC policy should know =
better.  If this continues, at some point many will ignore DMARC when it =
costs more than it is worth.  I too think we can do better, but the =
senders should be expected to do the heavy lifting.  Only they know =
which third-party services their users send messages. The TPA strategy =
is based on the premise third-party paths can be quickly verified by the =
recipients without a steep user learning curve.  TPA also creates little =
impact on how email is normally handled.=20

Email security should be structured to support a federated service and =
not depend on peer to peer communications.=20

Regards,
Douglas otis


From nobody Sun Apr 20 18:00:30 2014
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FBCA1A00ED for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 18:00:28 -0700 (PDT)
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, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 iB_JthaGRjLv for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 18:00:23 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0206.outbound.protection.outlook.com [207.46.163.206]) by ietfa.amsl.com (Postfix) with ESMTP id A21181A00FE for <ietf@ietf.org>; Sun, 20 Apr 2014 18:00:23 -0700 (PDT)
Received: from BLUPR03MB424.namprd03.prod.outlook.com (10.141.78.152) by BLUPR03MB422.namprd03.prod.outlook.com (10.141.78.143) with Microsoft SMTP Server (TLS) id 15.0.921.12; Mon, 21 Apr 2014 01:00:18 +0000
Received: from BLUPR03MB424.namprd03.prod.outlook.com ([10.141.78.152]) by BLUPR03MB424.namprd03.prod.outlook.com ([10.141.78.152]) with mapi id 15.00.0921.000; Mon, 21 Apr 2014 01:00:18 +0000
From: Christian Huitema <huitema@microsoft.com>
To: Doug Barton <dougb@dougbarton.us>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: DMARC and yahoo
Thread-Topic: DMARC and yahoo
Thread-Index: AQHPWQufPRozOu2//Em9ol77DALEOZsTcnaAgAARHwCAAAQmgIAHOCWAgAAJZwCAAEI4AIAAOEyw
Date: Mon, 21 Apr 2014 01:00:17 +0000
Message-ID: <0da8874469c14960a6b21719ebd4770b@BLUPR03MB424.namprd03.prod.outlook.com>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]> <53543ADA.8010204@dougbarton.us>
In-Reply-To: <53543ADA.8010204@dougbarton.us>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [24.16.156.113]
x-forefront-prvs: 0188D66E61
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(189002)(199002)(51704005)(4396001)(99286001)(99396002)(19580405001)(19580395003)(83322001)(50986999)(76176999)(54356999)(77096999)(80976001)(77982001)(92566001)(85852003)(20776003)(79102001)(66066001)(80022001)(74502001)(74662001)(31966008)(86362001)(15202345003)(86612001)(74316001)(81342001)(81542001)(46102001)(33646001)(76576001)(15975445006)(76482001)(83072002)(2656002)(87936001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB422; H:BLUPR03MB424.namprd03.prod.outlook.com; FPR:FCDCF5D9.F1A9C05.2B559DCB.4AF5BD61.20290; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2DVUZ8Ev-GPh8YT1PueMq_c9eXE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 01:00:28 -0000

> The issue with @yahoo.com and DMARC is not the @yahoo.com users' ability=
=20
> to receive mail, it's their ability to send mail to the list with From:=20
> *@yahoo.com and have it be received by list subscribers who implement=20
> strict DMARC policies which honor Yahoo!'s p=3Dreject.
>
> It's not clear how setting the @yahoo.com users to digest mode helps=20
> this situation at all.

It probably does not. Trying analyze the various positions with a cool head=
, the obvious conclusion is that hard problems don't have easy answers.

The current mailing list practice has the mailing list as sender, and the o=
riginal message composer described in the From field. The receiver sees som=
ething like:

   Sender: ietf <ietf-bounces@ietf.org>=20
   From: Christian Huitema <huitema@microsoft.com>=20
   =85

Of course, that particular construct could easily be abused. A phishing mes=
sage does not differ much from a mailing list message:

   Sender: postmaster <postmaster@phishing-domain.com>=20
   From: Christian Huitema <huitema@microsoft.com>=20
   =85

I understand that the DMARC "alignment" policy is meant to protect against =
that by requesting that sender domain and from field match. The problem is =
that a mailing list would then have to invent a new from field, letting the=
 recipient see something like:

   From: Christian Huitema <ietf-christian-huitema@ietf.org>
   Reply-To: Christian Huitema <huitema@microsoft.com>
   =85

The obvious issue is that this particular construct is also quite friendly =
to phishing. The phishing message would look like:

   From: Christian Huitema <christian-huitema@phishing-domain.com>
   Reply-To: Christian Huitema <huitema@microsoft.com>
   =85

If we teach users to ignore the bizarre email address for the mail list mes=
sages, we are also teaching them to ignore the bizarre email address in the=
 phishing messages. I doubt that this was the intent of the DMARC authors.=
=20

-- Christian Huitema

(I wrote a longer version of this email at http://huitema.wordpress.com/.)


From nobody Sun Apr 20 20:52:41 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C931F1A0182 for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 20:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 s4-yWBECcdfz for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 20:52:36 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2908B1A0096 for <ietf@ietf.org>; Sun, 20 Apr 2014 20:52:36 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6VSJKM1CG006N4P@mauve.mrochek.com> for ietf@ietf.org; Sun, 20 Apr 2014 20:47:30 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 20 Apr 2014 20:47:25 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6VSJIRAPQ00004W@mauve.mrochek.com>
Date: Sun, 20 Apr 2014 20:45:00 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Sat, 19 Apr 2014 16:16:04 -0400" <8647B94D503D57B710D99D7E@[192.168.1.128]>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net> <01P6TOCIJM0W00004W@mauve.mrochek.com> <56CF13B8250F8BE24F6F10CC@JcK-HP8200.jck.com> <01P6TTN1ILCQ00004W@mauve.mrochek.com> <8647B94D503D57B710D99D7E@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0u1mTtF_nfmTQVPcmtFgucT2oHQ
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 03:52:38 -0000

> >> there as a potential for the appearance of conflicts of
> >> interest.   Those conflicts need not be of the traditional
> >> legal or financial variety.  They can occur (or be perceived
> >> to occur) when someone's institutional or organizational
> >> relationships outside the IETF might lead people to suspect
> >> that review and decision-making might not be as careful,
> >> unbiased, or primarily reflective of the interest of the IETF
> >> or the broader Internet community as we would like it to
> >> assume it always is.  For situations where troublesome
> >> relationships exist or might be inferred (even by those
> >> suffering from mild paranoid), we need to get much more
> >> careful about disclosure of the relationships involved.
> >
> > Good point, and I agree.
> >
> > These waters are going to be difficult to nagivate, but I
> > don't see any alternative.

> Yes.  However, I see some parallel to the IPR situation.  We
> could presumably treat members of the community like adults (I
> think almost all are) and say "if you have an outside-the-IETF
> relationship to the developers, or developing organization, of a
> spec, you must at least disclose it", it would go a long way
> and, IMO, not be particularly difficult.

I concur.

> Unlike the IPR
> situation, this one is unlikely to require involving lawyers in
> what one could or could not say/ disclose.

I suppose it could pose difficulties for consultants in certain sorts of mixed
roles, but to be honest I don't really have much sympathy for people doing
that.

> The waters get
> difficult only if we feel a need to take the next steps toward
> forced recusal or worse.  Maybe, if we just demanded disclosure
> as an expected professional courtesy and act of honesty toward
> the rest of the community and understood that either an
> undisclosed conflict or a disclosed one that seemed to distort a
> decision could be reasonable grounds for appeals, we could get
> away without a requirement for a lot of hair-splitting rules.

Indeed. Something for the IESG to consider, that's for sure.

				Ned


From nobody Sun Apr 20 22:07:41 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6FC11A012E for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 22:07:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 ht9KYtdW30gv for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 22:07:37 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7C8931A002D for <ietf@ietf.org>; Sun, 20 Apr 2014 22:07:37 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6VV5MFTEO006PCP@mauve.mrochek.com> for ietf@ietf.org; Sun, 20 Apr 2014 22:02:32 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Sun, 20 Apr 2014 22:02:28 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6VV5KC6JK00004W@mauve.mrochek.com>
Date: Sun, 20 Apr 2014 21:47:17 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Sun, 20 Apr 2014 09:57:12 -0500" <5353E048.5020001@qti.qualcomm.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5351CCBC.4070901@meetinghouse.net> <01P6TOCIJM0W00004W@mauve.mrochek.com> <5353E048.5020001@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nl1sUEHKMqAQTcIWvN-vzqxoUdQ
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 05:07:38 -0000

> On 4/19/14 10:17 AM, ned+ietf@mauve.mrochek.com wrote:
> > I also think the time has come to try and address the more general
> > problem
> > of misunderstanding and/or misrepresentation of the status of various
> > documents. This probably needs to be addressed through a combination of
> > automatic labeling as well as some explicit statements here and there.
> >
> > And this really needs to be spearheaded by the IESG, not the IAB. I
> > hope the
> > IESG is already considering taking action. If not, they should be.

> The timing has been impeccable. The IESG had been privately talking
> about the "IETF relevance" issue, including why people are bringing
> "done" work to the IETF instead of working inside of the IETF. And
> related to "done" work, we have also been discussing the relative merits
> of AD-sponsored documents vs. ISE documents and what the appropriate use
> of IESG and IETF time is for these things. We've had all of that on our
> agenda for our upcoming retreat in a couple of weeks, and planned to
> discuss it with the IAB during a joint meeting. Then this DMARC thing
> happens, and Vidya published her article on "why I quit writing internet
> standards". It could not have been timed better.

> I'm trying to get my head around what we should have done differently on
> this, both tactically and strategically, so that I can summarize it for
> the discussion. But I can say pretty confidently that this is a topic
> frontmost in the minds of IESG folks.

On the misunderstanding/misrepresentation issue, I'm not sure asking what
could have been "done differently this time" is the right question. Our
processes were followed AFAIK. The misunderstanding/misrepresentation 
of the (preliminary) result of that process is not really a result of
what was done there, but rather the context in which the process operates.

But to my other point - what came out of the process - yes, I entirely
agree we need to look at what could have been done differently.

And on that score I'm not going to presume to offer specific advice. What I
will say is that I think you need to widen your scope to consider other
specifications. I already pointed out on the ietf-822 list how the SPFBIS
specifications contains what I consider to be totally inadequate advice on how
to address a similar, albeit less serious and far easier to address, issue. 

In fact I think some examination of how similar issues have been handled in
other recent documents is warranted.

				Ned


From nobody Sun Apr 20 23:50:09 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2BC61A010C for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 23:50:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.472
X-Spam-Level: 
X-Spam-Status: No, score=-1.472 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 0B3T07p9bZ7L for <ietf@ietfa.amsl.com>; Sun, 20 Apr 2014 23:50:05 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 363091A00B1 for <ietf@ietf.org>; Sun, 20 Apr 2014 23:50:05 -0700 (PDT)
Received: from localhost ([::1]) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Wc833-000JD9-TK; Mon, 21 Apr 2014 02:49:49 -0400
Date: Mon, 21 Apr 2014 02:49:49 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: DMARC and yahoo
Message-ID: <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/w98unFVwFSkEomIBJPxu2SHnxSw
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Theodore Ts'o <tytso@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 06:50:07 -0000

--On Monday, 21 April, 2014 08:26 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

>> IMO, this is quite elegant.  The Yahoo users continue to get
>> the messages, you don't get cluttered by rejection-related
>> complaints, and those Yahoo users who don't like the digest
>> form can take it up with Yahoo or find other accounts to use.
> 
> Unfortunately they can switch themselves back to normal mode
> too. Digest mode is user-settable, and is very annoying because
> it munges the Subject header. What's really needed is a
> DMARC-safe mode (per subscriber) that optionally rewrites the
> From.

Brian, I think there are several ways to look at this and that
there are some largely separable issues.  One of them, perhaps
unreasonable and perhaps not, is that DMARC was developed by a
collection of organizations who have a shared vision of how
email should work, what is important, and what isn't.  Yahoo is
a supporter/participant in that group, as are several people
with sufficient IETF history and leadership roles to be
knowledgeable about how to facilitate getting a document through
the system.  

I think that raises some issues for the IETF and RFC Editor
about how specifications developed entirely in other bodies --
traditionally, a category known as "specifications developed
elsewhere and republished for the convenience of the Internet
community" -- should be handled.   While it no longer applies in
the DMARC case, there are also some issues associated with
moving stable specifications developed elsewhere through the
IETF Standards Track (whether one calls that "fast track",
"rubber stamp", or something more complementary).   Pete has
mentioned that the IETF is looking at some of the issues
involved; I hope the ISE, and RFC Editor Function more
generally, are too.

As far as the mailman hack is concerned, I think there are two
different relevant audiences/ affected communities:

(i) Receivers who happen to have addresses associated with DMARC
supporters, such as Yahoo, that have adopted a
highly-restrictive policy.  Forcing them into Digest mode, and
warning them that, if they turn it off, they are unlikely to
receive any more list mail and will likely be dropped from the
list seems to be to be appropriate.  It was with that audience
in mind that I claimed that Jeffrey's action was elegant.  I
still think so, YMMD.

(ii) Senders who have chosen to send messages from mail
providers who have adopted restrictive, DMARC-based, policies.
>From my point of view, those providers have made a decision that
they aren't interested in having their mail users post messages
to mailing lists.  If a mail providers wants to effectively
restrict the types of mail their users can send, I think we have
to defend their right to do that.  It is also reasonable to hope
that users who think those services are useful will go elsewhere
and for mailing list managers to protect themselves by denying
posting privileges to such users or remove them from lists.   I
think it would be a great deal more ethical and professional if
those providers took responsibility for that decision with an
explicit announcement to their users, but that is really not an
IETF problem.  

As to your "DMARC-safe mode", I'm inclined to assume that Yahoo
knew exactly what would happen if they made this move.  To
believe otherwise raises significant questions about the quality
of development and review of the DMARC spec and hence whether
the IETF or ISE should publish it in any form, at least in the
absence of a rebuttal or public review and commentary.  The
belief that it was intentional is also reinforced by the
observation that this problem has now been known for quite a
while (in Internet time) and Yahoo has not chosen to modify
their preferences to some other option.  Given that, I think we
should be very cautious about recommending a technique to
subvert their intentions: such actions have too much history of
leading to counter-actions that have even worse effects.

    best,
      john


From nobody Mon Apr 21 00:29:34 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91E301A0188 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 00:29:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level: 
X-Spam-Status: No, score=-0.4 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, FREEMAIL_REPLY=1, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 BUpEeuhYhe10 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 00:29:28 -0700 (PDT)
Received: from mail-ee0-x231.google.com (mail-ee0-x231.google.com [IPv6:2a00:1450:4013:c00::231]) by ietfa.amsl.com (Postfix) with ESMTP id 760431A0180 for <ietf@ietf.org>; Mon, 21 Apr 2014 00:29:28 -0700 (PDT)
Received: by mail-ee0-f49.google.com with SMTP id c41so3409361eek.36 for <ietf@ietf.org>; Mon, 21 Apr 2014 00:29:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date :content-transfer-encoding:message-id:references:to; bh=ZYW6SYbuHg87zNdqnhLeWmeu0RnK+PX7eVF9q150krQ=; b=HJ7JPkXfT37ZC66gzSgzcQBzarN+o7j8qtioDfmboRwdwRPYqJNbfpxjZQyK3MlJhX cdyvvRcd9xdUhE1v4T3+Sv2mGH03f02oLUFb17DcnqhQOwuTjG+Vt6nDmrH4GFvn0CXA uqcJwL+dPL2hET0QydIlqQodlhlNwNxgmLwDjpjTN5wPPxCAHfkL0G9dI9UGZDYdcM2S memC4pjEG+OYpgC+GtUR2PH+olkfKHgkgwbJFsPLuhi3lTWWjEho8bgE8vw/5Q0m86pK rM14OV+K6vQt8SC+e79ESI9eRfHb3aUnImyJItlnhqd4cMGWhCQ71IOf3jf3kn4VMYA6 pFWw==
X-Received: by 10.14.225.132 with SMTP id z4mr171472eep.92.1398065363125; Mon, 21 Apr 2014 00:29:23 -0700 (PDT)
Received: from [192.168.1.102] (bzq-84-109-50-18.red.bezeqint.net. [84.109.50.18]) by mx.google.com with ESMTPSA id o5sm101134535eeg.8.2014.04.21.00.29.21 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Apr 2014 00:29:22 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC and yahoo
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <0da8874469c14960a6b21719ebd4770b@BLUPR03MB424.namprd03.prod.outlook.com>
Date: Mon, 21 Apr 2014 10:29:18 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF48768A-90D8-4634-A5E0-9C343A849F5A@gmail.com>
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]> <53543ADA.8010204@dougbarton.us> <0da8874469c14960a6b21719ebd4770b@BLUPR03MB424.namprd03.prod.outlook.com>
To: "ietf@ietf.org" <ietf@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CWuzoxVnGjLlLMzYVnadxEL4yHI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 07:29:32 -0000

On Apr 21, 2014, at 4:00 AM, Christian Huitema <huitema@microsoft.com> =
wrote:

>> The issue with @yahoo.com and DMARC is not the @yahoo.com users' =
ability=20
>> to receive mail, it's their ability to send mail to the list with =
From:=20
>> *@yahoo.com and have it be received by list subscribers who implement=20=

>> strict DMARC policies which honor Yahoo!'s p=3Dreject.
>>=20
>> It's not clear how setting the @yahoo.com users to digest mode helps=20=

>> this situation at all.
>=20
> It probably does not. Trying analyze the various positions with a cool =
head, the obvious conclusion is that hard problems don't have easy =
answers.
>=20
> The current mailing list practice has the mailing list as sender, and =
the original message composer described in the =46rom field. The =
receiver sees something like:
>=20
>   Sender: ietf <ietf-bounces@ietf.org>=20
>   From: Christian Huitema <huitema@microsoft.com>=20
>   =85
>=20
> Of course, that particular construct could easily be abused. A =
phishing message does not differ much from a mailing list message:
>=20
>   Sender: postmaster <postmaster@phishing-domain.com>=20
>   From: Christian Huitema <huitema@microsoft.com>=20
>   =85

Right. As a mailing list provider, we have a way to make our lists work:

 From: IETF mailing list on behalf of Christian Huitema <ietf@ietf.org>

 ...

The downside is that clicking =93Reply=94 sends a message to the list =
rather than to Christian, which seems OK, but is a change of behavior. =
In fact it gives no natural way to reply directly (and off-list) to =
Christian, unless the original sender is added in CC: or Reply-To: =
fields.

Yoav


From nobody Mon Apr 21 02:02:18 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5274B1A01E5 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 02:02:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 UgagpoTS6F1W for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 02:02:12 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id F2A061A01CD for <ietf@ietf.org>; Mon, 21 Apr 2014 02:02:11 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id rr13so3575133pbb.1 for <ietf@ietf.org>; Mon, 21 Apr 2014 02:02:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vvMUf/LHPPymjio9pZ2ILn5FFibyHWXQ4cK1YZTOhT0=; b=vax1wKnMB+lh+akhnA5Gg3RL28Ct/Ht9tscYNGmN4dS++IA3UyzWntnFoozNMpYzby eabgRlem5hTXNZoW8jqtoBQezV9m9sBifIE5cVXw2URlNjSoucHunT+VkZd5miVr5H4q FmGkm2e90xr4JGOJfjjRr6jYWzioHqeNH2lLtMxeMXdAnQhoAwMYNnNDBxmxjP4vxCrK JV7MhacvHMrO0YndloE4E/np8u1roTQ1B5wIufK2siftxY+Bd6ScaxZ/cfVQNq6Uz17i OSrfgoOWkCc25SFS9lmfKe/GPy6JdtvCTGWyR3sDx/usaAHlhiZtsAbciD4tA4wf6XW+ edaw==
X-Received: by 10.69.15.2 with SMTP id fk2mr2378282pbd.123.1398070927168; Mon, 21 Apr 2014 02:02:07 -0700 (PDT)
Received: from ?IPv6:2601:9:7680:203:959f:4446:19b2:81ad? ([2601:9:7680:203:959f:4446:19b2:81ad]) by mx.google.com with ESMTPSA id x5sm76616525pbw.26.2014.04.21.02.02.04 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Apr 2014 02:02:06 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC and yahoo
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]>
Date: Mon, 21 Apr 2014 02:02:22 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <946A20BF-9735-46D6-8B2A-593935EA27E0@gmail.com>
References: <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8REnj0ZR3VfmiMjuNNjXvPpKeOY
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Theodore Ts'o <tytso@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 09:02:16 -0000

On Apr 20, 2014, at 11:49 PM, John C Klensin <john-ietf@jck.com> wrote:

>=20
>=20
> --On Monday, 21 April, 2014 08:26 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>=20
>> Unfortunately they can switch themselves back to normal mode
>> too. Digest mode is user-settable, and is very annoying because
>> it munges the Subject header. What's really needed is a
>> DMARC-safe mode (per subscriber) that optionally rewrites the
>> From.
>=20
> Brian, I think there are several ways to look at this and that
> there are some largely separable issues.  One of them, perhaps
> unreasonable and perhaps not, is that DMARC was developed by a
> collection of organizations who have a shared vision of how
> email should work, what is important, and what isn't.  Yahoo is
> a supporter/participant in that group, as are several people
> with sufficient IETF history and leadership roles to be
> knowledgeable about how to facilitate getting a document through
> the system. =20
>=20
> I think that raises some issues for the IETF and RFC Editor
> about how specifications developed entirely in other bodies --
> traditionally, a category known as "specifications developed
> elsewhere and republished for the convenience of the Internet
> community" -- should be handled.   While it no longer applies in
> the DMARC case, there are also some issues associated with
> moving stable specifications developed elsewhere through the
> IETF Standards Track (whether one calls that "fast track",
> "rubber stamp", or something more complementary).   Pete has
> mentioned that the IETF is looking at some of the issues
> involved; I hope the ISE, and RFC Editor Function more
> generally, are too.
>=20
> As far as the mailman hack is concerned, I think there are two
> different relevant audiences/ affected communities:
>=20
> (i) Receivers who happen to have addresses associated with DMARC
> supporters, such as Yahoo, that have adopted a
> highly-restrictive policy.  Forcing them into Digest mode, and
> warning them that, if they turn it off, they are unlikely to
> receive any more list mail and will likely be dropped from the
> list seems to be to be appropriate.  It was with that audience
> in mind that I claimed that Jeffrey's action was elegant.  I
> still think so, YMMD.
>=20
> (ii) Senders who have chosen to send messages from mail
> providers who have adopted restrictive, DMARC-based, policies.
> =46rom my point of view, those providers have made a decision that
> they aren't interested in having their mail users post messages
> to mailing lists.  If a mail providers wants to effectively
> restrict the types of mail their users can send, I think we have
> to defend their right to do that.  It is also reasonable to hope
> that users who think those services are useful will go elsewhere
> and for mailing list managers to protect themselves by denying
> posting privileges to such users or remove them from lists.   I
> think it would be a great deal more ethical and professional if
> those providers took responsibility for that decision with an
> explicit announcement to their users, but that is really not an
> IETF problem. =20
>=20
> As to your "DMARC-safe mode", I'm inclined to assume that Yahoo
> knew exactly what would happen if they made this move.  To
> believe otherwise raises significant questions about the quality
> of development and review of the DMARC spec and hence whether
> the IETF or ISE should publish it in any form, at least in the
> absence of a rebuttal or public review and commentary.  The
> belief that it was intentional is also reinforced by the
> observation that this problem has now been known for quite a
> while (in Internet time) and Yahoo has not chosen to modify
> their preferences to some other option.  Given that, I think we
> should be very cautious about recommending a technique to
> subvert their intentions: such actions have too much history of
> leading to counter-actions that have even worse effects.

Dear John,

Well put.

May I say the TPA remedy is under the control of sending domains without =
impacting mailing list operation, assuming third-party SPF or DKIM or =
whatever verification benefits from a domain specific authorization.

Employing SRS or vouching like schemes removes control from senders =
since neither DKIM nor SPF capture intended recipients.  As such, this =
may have trouble gaining cooperation or retaining delivery integrity =
with tokens and return-paths arranged like an unmanageable collection of =
Matryoshka dolls.  TPA can be quickly implemented once a sender =
expresses a desire to have all needed exceptions under their control.

Regards,
Douglas Otis
=20


From nobody Mon Apr 21 06:52:36 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A476B1A01F8 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 06:52:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.873
X-Spam-Level: 
X-Spam-Status: No, score=-0.873 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 43Jx5pe5meuH for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 06:52:30 -0700 (PDT)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 1755C1A01F4 for <ietf@ietf.org>; Mon, 21 Apr 2014 06:52:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1398088346; x=1429624346; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=kX/wHnF4Etv7mt7HjL5G4eIBlQbw2pV8BuophT0rFqs=; b=dTH1vXxBLUXj/RvKc04E+PLQ6FjQk+AMEy8MVWpn89zacOTylEJUJnJ7 arCxy9EueKDRwU3ayVRuluz0/57wtkgUtjs3K+3SJBCXXCuy43/RFnq5N mOrum2BLoH+xodqlgFiYPB19d3BWcqDhm6WWEQWsoEdXzeiQuWKHywBYn 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,7414"; a="62278893"
Received: from ironmsg03-l.qualcomm.com ([172.30.48.18]) by sabertooth01.qualcomm.com with ESMTP; 21 Apr 2014 06:52:25 -0700
X-IronPort-AV: E=Sophos;i="4.97,896,1389772800"; d="scan'208";a="652316929"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 21 Apr 2014 06:52:25 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 21 Apr 2014 06:52:24 -0700
Message-ID: <53552294.5030504@qti.qualcomm.com>
Date: Mon, 21 Apr 2014 08:52:20 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Logging into the datatracker
References: <534C0366.10600@nostrum.com> <201404142149.s3ELnH4R015020@hobgoblin.ariadne.com>
In-Reply-To: <201404142149.s3ELnH4R015020@hobgoblin.ariadne.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xKYM19fbebqe9ACluNjB4a-RWDA
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 13:52:34 -0000

On 4/14/14 4:49 PM, Dale R. Worley wrote:
>> From: Robert Sparks<rjsparks@nostrum.com>
>>      
>    
>> Today's datatracker release changed the way you sign in, and has added
>> the ability to sign out.
>>
>> See<https://datatracker.ietf.org/release/>  for details.
>>      
>    
>> "This release changes user authentication for the datatracker from
>> basic http auth to Django's built-in authentication."
>>      
> No doubt this is all for the best in practice, but it does eliminate
> the one and only web site I've ever used that uses HTTP
> authentication.  R.I.P. RFC 2617.
>    

I was never thrilled about the fact that the old way didn't ask for the 
credentials every time, instead making me click on the Sign In link 
every time the credentials expired. But I've got to say that after a 
week of using it (as us ADs use it more than most), I'm pretty annoyed 
by the new UI. With HTTP auth, Safari happily recognized that it had the 
credentials, so clicking the Sign In link was effectively just a 
re-load. Now I get presented with a web form. Though Safari will fill in 
the credentials in the new web form, I have to do an extra click on a 
Sign In button. So we moved from mildly annoying to slightly more 
annoying. What else is new in the advancement of the web? :-/

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Mon Apr 21 09:36:59 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 927881A0010 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 09:36:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.542
X-Spam-Level: *
X-Spam-Status: No, score=1.542 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 l4xTmEbCp3ki for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 09:36:52 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 2F98B1A0181 for <ietf@ietf.org>; Mon, 21 Apr 2014 09:36:51 -0700 (PDT)
Received: (qmail 20120 invoked from network); 21 Apr 2014 16:36:44 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 21 Apr 2014 16:36:44 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=71ef.5355491c.k1404; i=johnl@user.iecc.com; bh=HZ94e2M/e7rTz/Vpy3kG33TL7eEcI4vRm+IHi9f5K/c=; b=XAjCBDKEVjYORSAJ6uAz3mUqFclB373nCrtU7MTwUBAZnsC++1EhvXe1e5JEuKv7zuYHl7NkgxJSmvESobfKijga6S4jvnRYK5jtG+mXxaahIxSfIhIpTh/mzREnSMSz9wy0K80EuZ0aS+MAU1Uac3ke7M6uStJ79XXNTTc0nrTQlWzn8vRfDvZnycG1MsnLkCjAK+GV6dUlv2STHE0JMJxRC2PvTcFKP90aWHVB0SDDlq60C7bix1eAlU2fyM/b
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=71ef.5355491c.k1404; olt=johnl@user.iecc.com; bh=HZ94e2M/e7rTz/Vpy3kG33TL7eEcI4vRm+IHi9f5K/c=; b=F449tGw3SOdn0sDsPO4iBf7Z7Z/jSlwI5dqKcRLpu59P6GoOiHt6BSzrKza+RJxZZyzCSoBNT8zQeUElZSRQoylF71Y0sMjEhF2g7RrJhbCNO7+Y+Dv+aZwUcCHCdWWjhi8rvlLtMwMKo4Lm//prjH8MMBSqdEZsdzrVNq5tBaUEe0M6s9G/kCRmcGtnby+AM3i5wbZoMxgiLsEeU5tBLBwS3ovRUrCtQTMBPhL8T70a6Sk1rxASRdmPZmwO7fJk
Date: 21 Apr 2014 16:36:21 -0000
Message-ID: <20140421163621.29166.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC and yahoo
In-Reply-To: <DF48768A-90D8-4634-A5E0-9C343A849F5A@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GSwgP-TfLF_bzh6fvijA6g3KO-U
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 16:36:56 -0000

>Right. As a mailing list provider, we have a way to make our lists work:
>
> From: IETF mailing list on behalf of Christian Huitema <ietf@ietf.org>

It is certainly possible to create mailing-list-like things that avoid
the damage from DMARC.  The question remains why it is our job to
screw up our systems to fix their problems.  They could fix it if they
wanted, e.g., by arranging to whitelist mail sources that don't match
DMARC's authentication model but send mail people want.  This is not
just mailing lists, of course.

I subscribe to a few lists that put the list's address on the From:
line, due I think to administrative confusion, not anything
deliberate, and it is much worse than normal list mail.  When I look
at normal list mail in my inbox, I pick out the ones from people I
know first.  On the lists where it's all the same, I tend to look at
the subject and if it's not obviously interesting, dump the whole
thread.

R's,
John


From nobody Mon Apr 21 09:44:59 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68CB91A0231 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 09:44:56 -0700 (PDT)
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] autolearn=ham
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 QdHhZ4QtTb78 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 09:44:52 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0B5B81A0223 for <ietf@ietf.org>; Mon, 21 Apr 2014 09:44:52 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3LGihpU012735 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 21 Apr 2014 09:44:46 -0700
Message-ID: <53554A7B.20006@dcrocker.net>
Date: Mon, 21 Apr 2014 09:42:35 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <20140421163621.29166.qmail@joyce.lan>
In-Reply-To: <20140421163621.29166.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 21 Apr 2014 09:44:47 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CWc9srltjTn2Rnv0XyCzMc5NZzs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 16:44:56 -0000

On 4/21/2014 9:36 AM, John Levine wrote:
> They could fix it if they
> wanted, e.g., by arranging to whitelist mail sources that don't match
> DMARC's authentication model but send mail people want.  This is not
> just mailing lists, of course.


Sorry, but I'm not quite understanding what additional mechanism you 
have in mind.

Exactly who does exactly what?

Who has to adopt it?

How will it scale?


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 21 10:25:13 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40B6E1A0031 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 10:25:11 -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, SPF_PASS=-0.001] autolearn=ham
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 vEnDQWp4t-QK for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 10:25:06 -0700 (PDT)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com [IPv6:2a00:1450:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id 4CF811A0015 for <ietf@ietf.org>; Mon, 21 Apr 2014 10:25:06 -0700 (PDT)
Received: by mail-we0-f180.google.com with SMTP id k48so828443wev.11 for <ietf@ietf.org>; Mon, 21 Apr 2014 10:25:00 -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:content-type; bh=OWG1Nk0KSCOWtFKrmNcl+ZaBvFVLvFAIeec1uue6Tb0=; b=VlbErSXpDusnvCwB0Ir1B2LSdS2WwbKyEvSHZLQp+J0J+gM1y8nvZTXZGMkLgAWEYD yIimWTVLeGDJcx0f+fOp1o0DjRmTB3uN7zhhSRr+Knz5Ugjlus6At8+ki1PZgr5CvuLG d0Qc5W6T27QXDi2KCP0fXVDdlW22Nmoiaxf6Q/z6+6Lu3SCVMhtRKSfP1huuewaZpX1+ z4cmDb2/83lNlTcUnY8DK/nKzUYczgRdSjKTl7JUAT2l4l9hp+qWFnKU0kWPLKOa5D3G uffcMa+ONz0nPh9YuPeJDILVDycoSAv5agEJa/D0vE8Jjf4LNhnFdGvC1SCwgllm7gY7 qb1A==
MIME-Version: 1.0
X-Received: by 10.180.211.116 with SMTP id nb20mr14746640wic.5.1398101100727;  Mon, 21 Apr 2014 10:25:00 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Mon, 21 Apr 2014 10:25:00 -0700 (PDT)
In-Reply-To: <01P6TRV1PBB000004W@mauve.mrochek.com>
References: <534ED376.8060303@bluepopcorn.net> <20140418013433.2763.qmail@joyce.lan> <CAL0qLwY4xVrPwABRhv90JSRF8wta0P5OCw_UWzVYOyUZk2-W4Q@mail.gmail.com> <01P6TRV1PBB000004W@mauve.mrochek.com>
Date: Mon, 21 Apr 2014 10:25:00 -0700
Message-ID: <CAL0qLwbordSBeAhEuwsb2GBkoiickdOebz7TwZODXDgw8EfezA@mail.gmail.com>
Subject: Re: What I've been wondering about the DMARC problem
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: multipart/alternative; boundary=001a11c26ab478128304f790c7f4
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lVmtIhWGmiiZ1dSkDnhOFvXlPrc
Cc: Jim Fenton <fenton@bluepopcorn.net>, John Levine <johnl@taugh.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 17:25:11 -0000

--001a11c26ab478128304f790c7f4
Content-Type: text/plain; charset=UTF-8

On Sat, Apr 19, 2014 at 8:31 AM, Ned Freed <ned.freed@mrochek.com> wrote:

>
> > > >"If the RFC5322.From domain does not exist in the DNS, Mail Receivers
> > > >SHOULD direct the receiving SMTP server to reject the message."
> > >
> > > As far as I can tell, that bit of poor advice hasn't been implemented.
>
> > Why is that poor advice?  It's not uncommon for an MTA receiving mail to
> > confirm that the message is replyable, at least insofar as an A and MX
> are
> > available for whatever comes after the "@".
>
> It's outrageously poor advice, for the simple reason that there's all
> kinds of
> legitimate email that's sent for all kinds of different reasons that you
> don't
> want people to be able to reply to. And the sooner they get a failure when
> they
> try and reply, the better.
>
> As such, the ability to reply to the RFC5322.From tells you almost nothing
> about its legitimacy.
>
> It's yet another case where a failure to consider the multiple semamtics
> field like RFC5322.From has, and designing to a subset of those designs,
> ends up screwing things up.
>

If you say so, but I can't think of an example off the top of my head.  Is
that still a currently-used tactic?  Most of the examples I can think of
involve a valid address that produces an automated response when someone
replies, rather than using something that is completely unreachable.

I seem to recall common use of From: field validation back when that
capability was introduced into open source sendmail as an anti-spam tactic,
though it was never supported by the vendor directly.  Maybe it's less
common now.

-MSK

--001a11c26ab478128304f790c7f4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Sat, Apr 19, 2014 at 8:31 AM, Ned Freed <span dir=3D"lt=
r">&lt;<a href=3D"mailto:ned.freed@mrochek.com" target=3D"_blank">ned.freed=
@mrochek.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D""><br>
&gt; &gt; &gt;&quot;If the RFC5322.From domain does not exist in the DNS, M=
ail Receivers<br>
&gt; &gt; &gt;SHOULD direct the receiving SMTP server to reject the message=
.&quot;<br>
&gt; &gt;<br>
&gt; &gt; As far as I can tell, that bit of poor advice hasn&#39;t been imp=
lemented.<br>
<br>
&gt; Why is that poor advice? =C2=A0It&#39;s not uncommon for an MTA receiv=
ing mail to<br>
&gt; confirm that the message is replyable, at least insofar as an A and MX=
 are<br>
&gt; available for whatever comes after the &quot;@&quot;.<br>
<br>
</div>It&#39;s outrageously poor advice, for the simple reason that there&#=
39;s all kinds of<br>
legitimate email that&#39;s sent for all kinds of different reasons that yo=
u don&#39;t<br>
want people to be able to reply to. And the sooner they get a failure when =
they<br>
try and reply, the better.<br>
<br>
As such, the ability to reply to the RFC5322.From tells you almost nothing<=
br>
about its legitimacy.<br>
<br>
It&#39;s yet another case where a failure to consider the multiple semamtic=
s<br>
field like RFC5322.From has, and designing to a subset of those designs,<br=
>
ends up screwing things up.<br>
<span class=3D"HOEnZb"></span></blockquote><div><br></div><div>If you say s=
o, but I can&#39;t think of an example off the top of my head.=C2=A0 Is tha=
t still a currently-used tactic?=C2=A0 Most of the examples I can think of =
involve a valid address that produces an automated response when someone re=
plies, rather than using something that is completely unreachable.<br>
<br></div><div>I seem to recall common use of From: field validation back w=
hen that capability was introduced into open source sendmail as an anti-spa=
m tactic, though it was never supported by the vendor directly.=C2=A0 Maybe=
 it&#39;s less common now.<br>
<br></div><div>-MSK<br></div></div></div></div>

--001a11c26ab478128304f790c7f4--


From nobody Mon Apr 21 11:04:21 2014
Return-Path: <douglasroyer@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E42611A0224 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 11:04:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1
X-Spam-Level: 
X-Spam-Status: No, score=-1 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, FREEMAIL_REPLY=1, SPF_PASS=-0.001] autolearn=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 1bIDFd8XzW7C for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 11:04:15 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 7078F1A022B for <ietf@ietf.org>; Mon, 21 Apr 2014 11:04:15 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id p10so3937542pdj.3 for <ietf@ietf.org>; Mon, 21 Apr 2014 11:04:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=YXUzpC58el++r2Yd8QfwGBUzcuy2LJWgwvXVL7eCMBQ=; b=JerBjrUydGXIES8IbU6681DAC/bHmKMG+FVhcVcxD3ajredfCzJBeNL2GTMjoy63Ws W0ThjkZsYKp0v5rrEgmJ+uaDtEaS2ls7avWB+m4zupGGb2n86ASwprTci/YH2G+S9VZX EtnePSOC+EAhnuJ+SNqvR9hWFPRGlnhmVD7/UMwE0+ikvyivi/pG4rvel7HVA4VSPyJZ OtCPKZo50ZFolXpz4G2rST2sO7m7iE+wPoB/xzP3UGgmtUmlcZ0f/QdeQzTfHxIWte8p gDFycSa+hd00ZAFLZFcpPTAtdUPRK6sJV+HpSw891NZuokkhw0wkD6qQZbNnsSwpZNEt lKjg==
X-Received: by 10.67.29.131 with SMTP id jw3mr4521628pad.141.1398103450459; Mon, 21 Apr 2014 11:04:10 -0700 (PDT)
Received: from [192.168.15.4] (184-76-96-188.war.clearwire-wmx.net. [184.76.96.188]) by mx.google.com with ESMTPSA id oa3sm79513112pbb.15.2014.04.21.11.04.07 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Apr 2014 11:04:08 -0700 (PDT)
Message-ID: <53555D90.7050709@gmail.com>
Date: Mon, 21 Apr 2014 12:04:00 -0600
From: Doug Royer <douglasroyer@gmail.com>
Organization: http://SoftwareAndServices.NET
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]> <53542D90.8030709@gmail.com>
In-Reply-To: <53542D90.8030709@gmail.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms080200070900060301080502"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DEIND809yymdhUygBN6l17zjxu0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 18:04:20 -0000

This is a cryptographically signed message in MIME format.

--------------ms080200070900060301080502
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable


If yahoo sends out an email from list-name@yahoo, then that is where the =

email is from.

So it would be correct to set the from/sender in the email to be=20
list-name@yahoo.com.
Why try to make it fake anything?

If you want to preserve any digital signature in the original message,=20
then send the original email as a mime body part in the forwarded message=
=2E


--=20

Doug Royer - (K7DMR.us / DougRoyer.com)
DouglasRoyer@gmail.com
714-989-6135



--------------ms080200070900060301080502
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMhzCC
BjQwggQcoAMCAQICAR4wDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoT
DVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNp
Z25pbmcxKTAnBgNVBAMTIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3
MTAyNDIxMDE1NVoXDTE3MTAyNDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1T
dGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWdu
aW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENs
aWVudCBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOr
lr6KMoOMpohBllVHrdRvEg/q6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSM
zR0t6ndl0TWBuUr/UXBhPk+Kmy7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6
qJR+xjOhV+VHzQMALuGYn5KZmc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSD
kOkikZB1xtB4ZqtXThaABSONdfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95
m4JgrM3Y/w7YX9d7YAL9jvN4SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMB
Af8wDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNV
HSMEGDAWgBROC+8apEBbpRdphzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUH
MAGGG2h0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3
dy5zdGFydHNzbC5jb20vc2ZzY2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tL3Nmc2NhLmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20v
c2ZzY2EuY3JsMIGABgNVHSAEeTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqD
CH14qywGXLhjjF6uHLkjd02hcdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy
6QMVQjbbMXltUfO4n4bGGdKo3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPI
zKKR9tQW8gGK+2+RHxkUCTbYFnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKf
KSETEPrHh7p5shuuNktvsv6hxHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HOR
z9v3vQwR4e3ksLc2JZOAFK+ssS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9
sIPP7ON0fz095HdThKjiVJe6vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCie
uoBJ9OlqmsVWQvifIYf40dJPZkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7t
w1sEhF0n/qpA2r0GpvkLRDmcSwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQ
G2EdJCB6luQ57GEnTA/yKZSTKI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGSzCCBTOgAwIBAgIDCXp9MA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTQwMzMwMTMwMjIz
WhcNMTUwMzMwMjMzNjMxWjBjMRkwFwYDVQQNExBDclhsb0tOcDhuNUxjMW53MR8wHQYDVQQD
DBZEb3VnbGFzUm95ZXJAZ21haWwuY29tMSUwIwYJKoZIhvcNAQkBFhZEb3VnbGFzUm95ZXJA
Z21haWwuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvgDR3UbGHtnMaqNw
FtsXf5VxjGKQWuVUhAJoKnxzI7Hf/gH7fFN/uGYB1HQiPDUOF/X2aIapC98ycdsZeHZ1iRIz
Qe5ag581kNFxztRWdqvPtK/nnXiB1qw8sVahmkC9JpZeh0KjymnB1D9vCHGJ+4l1bs9SB/aU
1pQ+zZVU+1bZJyUm9D7RN1+jrzkWbYqBAV99XoNodSbENuEB+skUGFMwxKZmAFWgAVIKMzWf
5rs3tP0Do2p1O+OaPkvxzkgo3thX/RPmMYPhpuewURcq+HQ6YRW+r7oZ97H9PaOrrwslKBu4
70sAAhbfd0LmCv3gXRnRTWMRnNVotY1jjqfapQIDAQABo4IC3DCCAtgwCQYDVR0TBAIwADAL
BgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQWBBSQ
5w5XWt3QI8FUbPINB9XajsHB6DAfBgNVHSMEGDAWgBRTcu2SnODaywFcfH6WNU7y1LhRgjAh
BgNVHREEGjAYgRZEb3VnbGFzUm95ZXJAZ21haWwuY29tMIIBTAYDVR0gBIIBQzCCAT8wggE7
BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29t
L3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24g
QXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5n
IHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENv
bSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGlu
IGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQv
MC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsG
AQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIv
Y2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20v
Y2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cu
c3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEARwipb/dALl2bQ7lZoavGzjro5vv3
yZ5PU2a+ZPLJaOOio6C1qfzoVmrwITTphp2VNACjbHJ9RHXbUi1WhMafgIw/YMXOj8cOlUFJ
2qz8R1WiK2Gt+aOVlgiin91pOpHlWUBlkhgH4yk1BAz1wcuZ5AWgm2r9g1DYX+NBLh6/IyPv
+1Imc9LoDJVwcatovbsa+zEEU3psvXEELJpwS4QPxWSYbDcuTL8jvA1HvXR1i8YtYJjm8A/u
VyxgNpve4UxrmNyya+vGMmRkOYAYt7ck4tuqe1L2NyErDhk7PIst1nxnEUPbRGTmSH2eQarV
lkDKXqdsl6bxWL72jZ0Kt+xgRDGCA90wggPZAgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQG
A1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNh
dGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVk
aWF0ZSBDbGllbnQgQ0ECAwl6fTAJBgUrDgMCGgUAoIICHTAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDA0MjExODA0MDBaMCMGCSqGSIb3DQEJBDEWBBRH
kBEwtv+cUUbzmD9UqaCB2UQm7jBsBgkqhkiG9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcG
BSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkrBgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYT
AklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBD
ZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkg
SW50ZXJtZWRpYXRlIENsaWVudCBDQQIDCXp9MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDEL
MAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBE
aWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEg
UHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMJen0wDQYJKoZIhvcNAQEBBQAEggEA
id49mdx7R1MLqk4FBgkjZa9KIYCSj68Y2Nbqq1Q2vPodLNBJ2T+/DhaaH0xOM/00GmzR3YdS
qTvMKMs09bgIw6e9RTNxuHUTeRbh0+37N5njpp8tpwwZXrNHehDCUcG1qbO3jrOPAQ4hcp8F
d5KtDbNPSJwcXAQ9KVwszwhJQ7I/xhEVoZ07d+WhBYi21XfPl3e3PD0mf70EHtjN3x+6epWH
lbm3ibfSFMDSwTqMQYxoYeBRg5W+5A2QHoHLiIFTomoV2JWLqynBPe+EezeD9kY3J+DKYHNZ
ScPPJ9xKRKEEty0/olEh5CmG2KAhKGARz2S2e+s0BprL5FC679+PTwAAAAAAAA==
--------------ms080200070900060301080502--


From nobody Mon Apr 21 11:54:10 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5FE11A0241 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 11:54:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 4qWfK7TBBpaP for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 11:54:03 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0DF331A0240 for <ietf@ietf.org>; Mon, 21 Apr 2014 11:54:03 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WO15JLCW006A4L@mauve.mrochek.com> for ietf@ietf.org; Mon, 21 Apr 2014 11:48:57 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 21 Apr 2014 11:48:48 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6WO10FRGY00004W@mauve.mrochek.com>
Date: Mon, 21 Apr 2014 11:42:25 -0700 (PDT)
Subject: Re: What I've been wondering about the DMARC problem
In-reply-to: "Your message dated Mon, 21 Apr 2014 10:25:00 -0700" <CAL0qLwbordSBeAhEuwsb2GBkoiickdOebz7TwZODXDgw8EfezA@mail.gmail.com>
References: <534ED376.8060303@bluepopcorn.net> <20140418013433.2763.qmail@joyce.lan> <CAL0qLwY4xVrPwABRhv90JSRF8wta0P5OCw_UWzVYOyUZk2-W4Q@mail.gmail.com> <01P6TRV1PBB000004W@mauve.mrochek.com> <CAL0qLwbordSBeAhEuwsb2GBkoiickdOebz7TwZODXDgw8EfezA@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oRF0g9EFbEPHhPclw_TbD7lA5rY
Cc: Jim Fenton <fenton@bluepopcorn.net>, John Levine <johnl@taugh.com>, Ned Freed <ned.freed@mrochek.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 18:54:07 -0000

> On Sat, Apr 19, 2014 at 8:31 AM, Ned Freed <ned.freed@mrochek.com> wrote:

> >
> > > > >"If the RFC5322.From domain does not exist in the DNS, Mail Receivers
> > > > >SHOULD direct the receiving SMTP server to reject the message."
> > > >
> > > > As far as I can tell, that bit of poor advice hasn't been implemented.
> >
> > > Why is that poor advice?  It's not uncommon for an MTA receiving mail to
> > > confirm that the message is replyable, at least insofar as an A and MX
> > are
> > > available for whatever comes after the "@".
> >
> > It's outrageously poor advice, for the simple reason that there's all
> > kinds of
> > legitimate email that's sent for all kinds of different reasons that you
> > don't
> > want people to be able to reply to. And the sooner they get a failure when
> > they
> > try and reply, the better.
> >
> > As such, the ability to reply to the RFC5322.From tells you almost nothing
> > about its legitimacy.
> >
> > It's yet another case where a failure to consider the multiple semamtics
> > field like RFC5322.From has, and designing to a subset of those designs,
> > ends up screwing things up.
> >

> If you say so, but I can't think of an example off the top of my head.

What planet are you on? I get mail with intentionally invalid From: fields all
the time. The domain usuall (but not always) exists, but the mailbox returns an
error.

I also get mail that says something like "this goes to a mailbox that's
unmonitored" somewhere in the message. But rather less of that.

> Is
> that still a currently-used tactic?  Most of the examples I can think of
> involve a valid address that produces an automated response when someone
> replies, rather than using something that is completely unreachable.

Autoresponders for such things produce blowback spam. Not good. If the mailbox
is valid, it's usually a black hole.

Indeed, while I cannot talk about the details, I know there was a lawsuit
against an ISP that was doing this sort of checking very aggressively and
blocking lots of legitimate email. The ISP lost and was forced to remove this
check.

> I seem to recall common use of From: field validation back when that
> capability was introduced into open source sendmail as an anti-spam tactic,
> though it was never supported by the vendor directly.  Maybe it's less
> common now.

A lot less common. See above.

				Ned


From nobody Mon Apr 21 11:56:57 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E13141A024B for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 11:56:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 O80tlA-bZqOg for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 11:56:48 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 2E78A1A0261 for <ietf@ietf.org>; Mon, 21 Apr 2014 11:56:48 -0700 (PDT)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WcJOU-0001jX-S2; Mon, 21 Apr 2014 18:56:42 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 25F7B5804E2; Mon, 21 Apr 2014 14:56:42 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=ef5046eb; t=1398106602; bh=FbKYv+F+tLnv5nRnkrPEFRoQXno8uHXB2OsQ8lqRt+g=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=t9GRMM6qMWqgwCU0hc//NSIYkK/hTWq1lGDL4tfY11aaN3ejiFJwIiOqqUFKxclMx uWGEOYELOARH5C5M9uwCOZdU23+K3i1/aR5lY/lRjIituZDQCPvP0cs/1f5Wqzuo+i xCkq9Nj4qDxwgCZ+Hu96WZ+Nf8nmFbskqNTa2LaA=
Date: Mon, 21 Apr 2014 14:56:42 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Doug Royer <douglasroyer@gmail.com>
Subject: Re: DMARC and yahoo
Message-ID: <20140421185642.GB5105@thunk.org>
References: <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]> <53542D90.8030709@gmail.com> <53555D90.7050709@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <53555D90.7050709@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yqrCqGvMhz-UIg6HdfzXMj9Vu7Q
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 18:56:54 -0000

On Mon, Apr 21, 2014 at 12:04:00PM -0600, Doug Royer wrote:
> 
> If yahoo sends out an email from list-name@yahoo, then that is where the
> email is from.
> 
> So it would be correct to set the from/sender in the email to be
> list-name@yahoo.com.
> Why try to make it fake anything?
> 
> If you want to preserve any digital signature in the original message, then
> send the original email as a mime body part in the forwarded message.

Because this message that you just sent was sent _from_ Doug Royer, in
the sense that it was authored by Doug Royer.  It was not authored by
"ietf@ietf.org", and that's in fact what most users would find more
interesting, since they have other ways of determining that a
particular message was sent via a particular mailing list reflector.

Fundamentally, this is going to be main issue.  For mailing list
users, when they are following a particular conversation, they want to
be able to easily identify which e-mails were contributed by which
participant.  This has historically been done via the "From" field.
It's possible to reinvent some other field, to indicate who had
originally authored the message --- say, adding a
"X-Originally-Authored-By".  But the fundamental issue is that it's
useful and interesting and wanted that people be able to get the
"originally authored by" message.  And so eventually, MUA are going to
be responsive to users' needs.

The fact that spammers could then use this confuse naive users is not
likely going to stop them, because if you are having a multi-user
conversation via e-mail, to make all of them appear to come from
"mailing-list@host.org" is just not acceptable to the users of that
mailing list.  They will want to know who originally authored the each
e-mail message.

	   	       	    	  - Ted



From nobody Mon Apr 21 12:15:38 2014
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E57171A0250 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 12:15:36 -0700 (PDT)
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] autolearn=ham
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 8mKQUxKEtBLM for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 12:15:32 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 15D2C1A0262 for <ietf@ietf.org>; Mon, 21 Apr 2014 12:15:26 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3LJFGoM016393 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 21 Apr 2014 12:15:19 -0700
Message-ID: <53556DC4.3050209@bbiw.net>
Date: Mon, 21 Apr 2014 12:13:08 -0700
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Doug Royer <douglasroyer@gmail.com>, ietf@ietf.org
Subject: Re: DMARC and yahoo
References: <CAKW6Ri6OUmxGaBOGR2hoWpDOGWsVQ9tQ2Q9ogkT5wzFhFJLBbQ@mail.gmail.com> <534D9C2C.8010606@gmail.com> <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]> <53542D90.8030709@gmail.com> <53555D90.7050709@gmail.com>
In-Reply-To: <53555D90.7050709@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Mon, 21 Apr 2014 12:15:19 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1igIfbX18LxmkC8Wd8Xgp9LAR0s
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 19:15:37 -0000

On 4/21/2014 11:04 AM, Doug Royer wrote:
>
> If yahoo sends out an email from list-name@yahoo, then that is where the
> email is from.

Unfortunately, email is more complicated than that.  There are multiple 
actors, taking multiple roles.  The most important one to represent 
properly in the message is the author, shown in the rfc5322.from header 
field.

At the top level, an author is communicating with recipients, and often 
they need to be able to reply to to that author, without copying the 
other recipients.  Mess with the original From field and the ability to 
reply is typically affected.

A mailing list is a mediator to this exchange, such that, yes, it takes 
formal delivery and formally posts a new message.  However the 
'original' author and the 'final' recipients still treat this as an 
exchange between them.  The recipients are aware of the role of the 
mailing list, but they do not consider the mail to be 'from' the mailing 
list.

The mailing list is an originator, in formal terms, which is typically 
represented by the rfc5322.sender field.

Changing the rfc5322.From field to be different than what the original 
author created alters communication among the the participants.


> So it would be correct to set the from/sender in the email to be

from/sender?  those are two different fields.


> list-name@yahoo.com.
> Why try to make it fake anything?
>
> If you want to preserve any digital signature in the original message,
> then send the original email as a mime body part in the forwarded message.

Encapsulating the original message into a subordinate message has some 
appeal.  It also well might have some additional attack vectors.  In any 
event, it's an end-to-end change, probably affecting every entity 
handling the message.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 21 12:20:20 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CEAB1A027C for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 12:20:18 -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, SPF_PASS=-0.001] autolearn=ham
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 f1rn5Zc29iXl for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 12:20:14 -0700 (PDT)
Received: from mail-pb0-x22d.google.com (mail-pb0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 0B45F1A027B for <ietf@ietf.org>; Mon, 21 Apr 2014 12:20:13 -0700 (PDT)
Received: by mail-pb0-f45.google.com with SMTP id uo5so4037926pbc.18 for <ietf@ietf.org>; Mon, 21 Apr 2014 12:20:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=mOkVnvjxWijeyQ4wUTVTgkl8V60JIaJewiLF0b1Mdlw=; b=qR+qXovBflDFvRcYg2h6pIsUdZ6+rqGwLb0Ef+0MuNW4uUShn9Z5P+5zF56oSI1Hby Nfu2yeHg8YcAXw0QDVyufzzqG8JCSGbzNfZWLXRFY+USyCDzl0uS7c2aVm/RbL2cYqZA GJCE/nhasQ8B70MT2bCy4ROGjzRvBN+UazFQovfX5cLTd+t8W4v9+UXe1FAkhDSrMF4W /vmYvnLCbOWFO6lnqlNHTCFeZ8C3tBH4b0UIg16Bca4cqIdlqzC0cjnoBL3bIhLJqcmf cNUgvDT42pv1Actx7V4kIORBZ9a6MUEP7alJLaA9uJZMQ+fFyiu8Xp5nT355rG/GDYwQ WauA==
X-Received: by 10.66.250.161 with SMTP id zd1mr4945334pac.136.1398108009059; Mon, 21 Apr 2014 12:20:09 -0700 (PDT)
Received: from ?IPv6:2601:9:7680:203:b54f:4381:6ca8:f934? ([2601:9:7680:203:b54f:4381:6ca8:f934]) by mx.google.com with ESMTPSA id lr3sm37842156pab.4.2014.04.21.12.20.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Apr 2014 12:20:07 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_33CBD5A5-AF8D-4D29-8147-49214F3901B9"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC and yahoo
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <53554A7B.20006@dcrocker.net>
Date: Mon, 21 Apr 2014 12:20:10 -0700
Message-Id: <5A812333-040A-4EF0-946A-8996D2E4B7EB@gmail.com>
References: <20140421163621.29166.qmail@joyce.lan> <53554A7B.20006@dcrocker.net>
To: dcrocker@bbiw.net
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4w9EmoJBhRBKY45l4Utq0CbzAhY
Cc: John Levine <johnl@taugh.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 19:20:18 -0000

--Apple-Mail=_33CBD5A5-AF8D-4D29-8147-49214F3901B9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Apr 21, 2014, at 9:42 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 4/21/2014 9:36 AM, John Levine wrote:
>> They could fix it if they
>> wanted, e.g., by arranging to whitelist mail sources that don't match
>> DMARC's authentication model but send mail people want.  This is not
>> just mailing lists, of course.
>=20
>=20
> Sorry, but I'm not quite understanding what additional mechanism you =
have in mind.
>=20
> Exactly who does exactly what?
>=20
> Who has to adopt it?
>=20
> How will it scale?

Dear Dave,

Each domain can simply point to their desired white-list. This can be =
one published directly or simply referenced as described in:

http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8

This has elements from the moribund ADSP.  The sender wishing to protect =
a domain while also applying policy like that of ADSP or DMARC can offer =
receivers a rapid and scalable method to check third-party domain =
authorizations.  This means senders are always able to defend recipients =
who trust messages from their domain.  Please note, authorizations can =
also require presence of a List-ID.  Other schemes, such as SRS, end up =
treating third-parties the same, which never works.=20

Perhaps being a bit crass, those who have decided to adopt DMARC for =
their user accounts have a vested interest in seeing mailing-lists fail. =
 Their revenue is often based on ads displayed in a user's browser.  =
Forcing use of some social web site has an advantage of injecting ads =
while also balkanizing group efforts.  Is the IETF ready to offer their =
own version of a social website or start an email version of a =
three-card monte game of "Where is the From?  Must all other group =
endeavors demand some social allegiance or can these sites become =
federated using something like XMPP and give up on email?

Regards,
Douglas Otis












--Apple-Mail=_33CBD5A5-AF8D-4D29-8147-49214F3901B9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;"><br>On Apr 21, 2014, at 9:42 AM, =
Dave Crocker &lt;<a =
href=3D"mailto:dhc@dcrocker.net">dhc@dcrocker.net</a>&gt; =
wrote:<br><br><blockquote type=3D"cite">On 4/21/2014 9:36 AM, John =
Levine wrote:<br><blockquote type=3D"cite">They could fix it if =
they<br>wanted, e.g., by arranging to whitelist mail sources that don't =
match<br>DMARC's authentication model but send mail people want. =
&nbsp;This is not<br>just mailing lists, of =
course.<br></blockquote><br><br>Sorry, but I'm not quite understanding =
what additional mechanism you have in mind.<br><br>Exactly who does =
exactly what?<br><br>Who has to adopt it?<br><br>How will it =
scale?<br></blockquote><br><div>Dear Dave,</div><div><br></div><div>Each =
domain can simply point to their desired white-list. This can be one =
published directly or simply referenced as described =
in:</div><div><br></div><div><a =
href=3D"http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8">ht=
tp://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8</a></div><div=
><br></div><div>This has elements from the moribund ADSP. &nbsp;The =
sender wishing to protect a domain while also applying policy like that =
of ADSP or DMARC can offer receivers a rapid and scalable method to =
check third-party domain authorizations. &nbsp;This means senders are =
always able to defend recipients who trust messages from their domain. =
&nbsp;Please note, authorizations can also require presence of a =
List-ID. &nbsp;Other schemes, such as SRS, end up treating third-parties =
the same, which never works.&nbsp;</div><div><br></div><div>Perhaps =
being a bit crass, those who have decided to adopt DMARC for their user =
accounts have a vested interest in seeing mailing-lists fail. =
&nbsp;Their revenue is often based on ads displayed in a user's browser. =
&nbsp;Forcing use of some social web site has an advantage of injecting =
ads while also balkanizing group efforts. &nbsp;Is the IETF ready to =
offer their own version of a social website or start an email version of =
a three-card monte game of "Where is the From? &nbsp;Must all other =
group endeavors demand some social allegiance or can these sites become =
federated using something like XMPP and give up on =
email?</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div><div><br></div><div><br></div><div><br></div><div=
><br></div><div><br></div><div><br></div><div><br></div><div><br></div><di=
v><br></div><div><br></div></body></html>=

--Apple-Mail=_33CBD5A5-AF8D-4D29-8147-49214F3901B9--


From nobody Mon Apr 21 12:53:46 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595C41A0277 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 12:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.943
X-Spam-Level: *
X-Spam-Status: No, score=1.943 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, MANGLED_SPAM=2.3, SPF_NEUTRAL=0.779] autolearn=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 YLOjMZ-pO3Jg for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 12:53:39 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id A8A7C1A0257 for <ietf@ietf.org>; Mon, 21 Apr 2014 12:53:38 -0700 (PDT)
Received: (qmail 97043 invoked from network); 21 Apr 2014 19:53:32 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 21 Apr 2014 19:53:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=711c.5355773c.k1404; i=johnl@user.iecc.com; bh=oxAsZ6QpIPfbnZVkiVTNJU+DtEyLJxpoWcCHuqZ1C80=; b=jFSHv6DolYOjPLnWGe9k6GxUDwaQxeBC1BoAaPr4f/khVcS/0chBxIS34EW0tdGGGYMT5E+Ls5Q4XP8uvZ493Jy9ABZw1k4VCyJT+oF51z0C9nXTB1cB5MXimUw9G8153/DXmzhvQTfj0Iuu0sxoWkV+n6Uk3VYfc8dQaJ2+eRWc6CMGKGlHIVrhdiHVA3NLWItMYfir9OdzokzeIx9hUDr/1fBY5EZ6sr+wD3bhMb2xD6JFyZx6ZPw5SiSoly6+
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=711c.5355773c.k1404; olt=johnl@user.iecc.com; bh=oxAsZ6QpIPfbnZVkiVTNJU+DtEyLJxpoWcCHuqZ1C80=; b=3DauLaIr7VMm4Uxhous1LklkFzEGQhlNu8HlmXbWXBkbguMtMOaFgSDJtZUUZg5SQaWmnj0eAx/U3tvslQndbUjUbK2vSSrmc1gqaACt0uVkpAdn4xLrnzP928mHPfkfa43xS5DS86sdZhnVUIZFAjOG1jaUcvI1/2vcUevaCWE/4nLsTgLrJzMxsJB+8gAy0b3T+SORo/onGh1tysZXJGNeUnwYWmycX8AgNYOPAyhvySWGXetTRcVuen4CHdSn
Date: 21 Apr 2014 19:53:08 -0000
Message-ID: <20140421195308.28955.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: What I've been wondering about the DMARC problem
In-Reply-To: <CAL0qLwbordSBeAhEuwsb2GBkoiickdOebz7TwZODXDgw8EfezA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BBhuqg0zDNTDcWtgIWbmbs0F3ak
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 19:53:43 -0000

>> As such, the ability to reply to the RFC5322.From tells you almost nothing
>> about its legitimacy. ...

>I seem to recall common use of From: field validation back when that
>capability was introduced into open source sendmail as an anti-spam tactic,
>though it was never supported by the vendor directly.  Maybe it's less
>common now.

If people start rejecting because .INVALID is on the From: line, it
is the work of a moment to adjust it to something like this:

 From: Marissa <marissa@yahoo.com.not.sp.am>

and the work of about three moments to spin up a fake MTA that accepts
any RCPT TO and rejects at DATA.  Or I suppose it could just be an
open relay.  

This of course trains people to be phished, by telling them that
<security@paypal.com.some.thing> is the same as <security@paypal.com>.

R's,
John


From nobody Mon Apr 21 13:07:44 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C13D71A028F for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 13:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.4
X-Spam-Level: 
X-Spam-Status: No, score=-0.4 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, FREEMAIL_REPLY=1, J_CHICKENPOX_21=0.6, SPF_PASS=-0.001] autolearn=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 7HrsdQxkZgLw for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 13:07:38 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 9EE8D1A028B for <ietf@ietf.org>; Mon, 21 Apr 2014 13:07:38 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id v10so4041962pde.29 for <ietf@ietf.org>; Mon, 21 Apr 2014 13:07:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=cyurktB3jSGIOMfRXPwuHi5ikEYJDgIpBTzsMC2mwC8=; b=PNhvib35k5VrVArmMeyfJhWETis3VvRq+Td/FxC7D+/QYXx1XHqNDUQuvVzr77Fql9 8detnRCLhaefj/OZRCH0rCsuzCPJQTnX/l0pmbYsbNPh0KIgbWYCzCe/y1bRttSE2Asi KLMHp6VaZXs8CD5BrA+QpDyDHNSOItw4uASRW071rRFYZLI04PhBPSqDRX6UdqZ2kNh4 2KPiBRcdRl2K/bFsyPYdcLKAV75XvsY8b80frkY34wL/blj64aKkSs1xoa1qKqMi9Se9 9qu90F1Ck1GB6FubEZCqv2VkshvkX/z5mrkMy5cm9PvUuU2FKJoIwg9X2rXn1A5iF1/U qiDQ==
X-Received: by 10.66.184.239 with SMTP id ex15mr5232935pac.122.1398110853505;  Mon, 21 Apr 2014 13:07:33 -0700 (PDT)
Received: from [192.168.178.20] (240.199.69.111.dynamic.snap.net.nz. [111.69.199.240]) by mx.google.com with ESMTPSA id vg1sm79910386pbc.44.2014.04.21.13.07.31 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Apr 2014 13:07:32 -0700 (PDT)
Message-ID: <53557A7D.4060003@gmail.com>
Date: Tue, 22 Apr 2014 08:07:25 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: DMARC and yahoo
References: <20140415214348.GL4456@thunk.org> <1397607352.389753533@f361.i.mail.ru> <534DCFFB.4080102@gmail.com> <20140416012205.GC12078@thunk.org> <24986.1397615002@sandelman.ca> <20140416023813.GA21807@thunk.org> <C8A2B0B4-5FA4-4BFE-AECE-C61667ECF2FB@secure-endpoints.com> <4948F093F369F051CAF0B810@[192.168.1.128]> <53542D90.8030709@gmail.com> <53555D90.7050709@gmail.com> <20140421185642.GB5105@thunk.org>
In-Reply-To: <20140421185642.GB5105@thunk.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BjY4v5pdYTOEosy7wz7SpRUnbaE
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 20:07:40 -0000

On 22/04/2014 06:56, Theodore Ts'o wrote:
> On Mon, Apr 21, 2014 at 12:04:00PM -0600, Doug Royer wrote:
>> If yahoo sends out an email from list-name@yahoo, then that is where the
>> email is from.
>>
>> So it would be correct to set the from/sender in the email to be
>> list-name@yahoo.com.
>> Why try to make it fake anything?
>>
>> If you want to preserve any digital signature in the original message, then
>> send the original email as a mime body part in the forwarded message.
> 
> Because this message that you just sent was sent _from_ Doug Royer, in
> the sense that it was authored by Doug Royer.  It was not authored by
> "ietf@ietf.org", and that's in fact what most users would find more
> interesting, since they have other ways of determining that a
> particular message was sent via a particular mailing list reflector.
> 
> Fundamentally, this is going to be main issue.  For mailing list
> users, when they are following a particular conversation, they want to
> be able to easily identify which e-mails were contributed by which
> participant.  This has historically been done via the "From" field.
> It's possible to reinvent some other field, to indicate who had
> originally authored the message --- say, adding a
> "X-Originally-Authored-By".  But the fundamental issue is that it's
> useful and interesting and wanted that people be able to get the
> "originally authored by" message.  And so eventually, MUA are going to
> be responsive to users' needs.
> 
> The fact that spammers could then use this confuse naive users is not
> likely going to stop them, because if you are having a multi-user
> conversation via e-mail, to make all of them appear to come from
> "mailing-list@host.org" is just not acceptable to the users of that
> mailing list.  They will want to know who originally authored the each
> e-mail message.

In fact it's a lie: the message is *not* from the mailing list, it's
from its originator. I have no doubt some ingenious lawyer could
discover a tort in the lie, so it might even be legally dangerous for
the mailing list operator to tell this lie on every message.

Among other things, it makes it virtually impossible to filter trolls.
I am on a couple of lists at the moment where troll filtering is
essential for one's sanity (and where DMARC has been discussed too, as
it happens).

   Brian


From nobody Mon Apr 21 13:48:46 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 223B21A02AC for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 13:48:44 -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, SPF_PASS=-0.001] autolearn=ham
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 Ka0pPxLOWqw1 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 13:48:42 -0700 (PDT)
Received: from mail-wi0-x22c.google.com (mail-wi0-x22c.google.com [IPv6:2a00:1450:400c:c05::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 71F641A02A3 for <ietf@ietf.org>; Mon, 21 Apr 2014 13:48:42 -0700 (PDT)
Received: by mail-wi0-f172.google.com with SMTP id hi2so2304219wib.11 for <ietf@ietf.org>; Mon, 21 Apr 2014 13:48:36 -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:content-type; bh=FduG5PunqGK6idSxCjFId/FH4pQo8HsWdjYEZ03x6hk=; b=ybPZembwhbU6Ox9RWXtujfPbLY1HmjALg6NFSH2OB5e5lQHCnvSemgTeyUvM7SKicw DDuUTcIrBmIXido3k9FB7hpUsefd4JDQf1nZiPWXgVeN11MtDOY3dF5cevEsHKbY6pIS f7T8cR5CWT2Up+goL2hTex+C30y/7TVy354SN1DqgjHoxhlXBdpHLUgGpw1HXQ4idrtD Yx0a3u7fkBUBwD0H7xQcSoFHydhx70bAScxgKL+TaSGxsDmdpIHpQ7iWBm0Jc2v3riqm 2csFi7JCj/pLT5RoIsnyoT5CYKVkT5M+X1umAFJGUKepcbuyr0lL6U7elPOLk/D7zmB2 De3w==
MIME-Version: 1.0
X-Received: by 10.194.63.236 with SMTP id j12mr30431815wjs.5.1398113316862; Mon, 21 Apr 2014 13:48:36 -0700 (PDT)
Received: by 10.180.211.40 with HTTP; Mon, 21 Apr 2014 13:48:36 -0700 (PDT)
In-Reply-To: <01P6WO10FRGY00004W@mauve.mrochek.com>
References: <534ED376.8060303@bluepopcorn.net> <20140418013433.2763.qmail@joyce.lan> <CAL0qLwY4xVrPwABRhv90JSRF8wta0P5OCw_UWzVYOyUZk2-W4Q@mail.gmail.com> <01P6TRV1PBB000004W@mauve.mrochek.com> <CAL0qLwbordSBeAhEuwsb2GBkoiickdOebz7TwZODXDgw8EfezA@mail.gmail.com> <01P6WO10FRGY00004W@mauve.mrochek.com>
Date: Mon, 21 Apr 2014 13:48:36 -0700
Message-ID: <CAL0qLwYXbTqkyzPqK2O2p5t_C-E+LhgdxfSscp0Pxxqqud4sZQ@mail.gmail.com>
Subject: Re: What I've been wondering about the DMARC problem
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Ned Freed <ned.freed@mrochek.com>
Content-Type: multipart/alternative; boundary=047d7ba982949b7fcb04f7939f6f
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/T0LM65GpFgrpzPYzomSDdufKwmc
Cc: Jim Fenton <fenton@bluepopcorn.net>, John Levine <johnl@taugh.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 20:48:44 -0000

--047d7ba982949b7fcb04f7939f6f
Content-Type: text/plain; charset=UTF-8

On Mon, Apr 21, 2014 at 11:42 AM, Ned Freed <ned.freed@mrochek.com> wrote:

> > If you say so, but I can't think of an example off the top of my head.
>
> What planet are you on? I get mail with intentionally invalid From: fields
> all
> the time. The domain usuall (but not always) exists, but the mailbox
> returns an
> error.
>

Rudeness aside, I'm on a planet where I can't remember the last time I got
a message where the stuff after the "@" was a domain name that doesn't
exist.  Maybe you get them, but I don't.  Sorry to burst your blustery
bubble.


> I also get mail that says something like "this goes to a mailbox that's
> unmonitored" somewhere in the message. But rather less of that.
>

Yes, I get those too.

-MSK

--047d7ba982949b7fcb04f7939f6f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Mon, Apr 21, 2014 at 11:42 AM, Ned Freed <span dir=3D"l=
tr">&lt;<a href=3D"mailto:ned.freed@mrochek.com" target=3D"_blank">ned.free=
d@mrochek.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"">&gt; If you say so, but I ca=
n&#39;t think of an example off the top of my head.<br>
<br>
</div>What planet are you on? I get mail with intentionally invalid From: f=
ields all<br>
the time. The domain usuall (but not always) exists, but the mailbox return=
s an<br>
error.<br></blockquote><div><br></div><div>Rudeness aside, I&#39;m on a pla=
net where I can&#39;t remember the last time I got a message where the stuf=
f after the &quot;@&quot; was a domain name that doesn&#39;t exist.=C2=A0 M=
aybe you get them, but I don&#39;t.=C2=A0 Sorry to burst your blustery bubb=
le.<br>
=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
I also get mail that says something like &quot;this goes to a mailbox that&=
#39;s<br>
unmonitored&quot; somewhere in the message. But rather less of that.<br></b=
lockquote><div><br></div><div>Yes, I get those too. <br><br></div><div>-MSK=
<br></div></div></div></div>

--047d7ba982949b7fcb04f7939f6f--


From nobody Mon Apr 21 14:05:25 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 110451A028E for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 14:05:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 smanwG2TI5ZW for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 14:05:16 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 704E51A0291 for <ietf@ietf.org>; Mon, 21 Apr 2014 14:05:16 -0700 (PDT)
Received: by mail-lb0-f171.google.com with SMTP id w7so3639320lbi.30 for <ietf@ietf.org>; Mon, 21 Apr 2014 14:05:10 -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:content-type:content-transfer-encoding; bh=xBchzQauohVNmCXAsKFbPbcN2mpzFUlm80p7hq5NDic=; b=DidZ40ERMTy4ZAo1Jp7etuLX5GOgHaYk+lXBsHRqgheOk9uVG/NZen/M/fTSIoXlF/ aurq88X7oWoUaeI8MJ0jStjPKdlzLMovqrxvY1o4ggu/7zNenq9gp6870yekrqmKc+Z4 FpLXVzkuo1qtpohMpDUkUVlvVqn6edDthXe8Q4M9eXIi59Z9U9ulBZVacrlIKkw4ymlo Lg6+Uh2mULLWobjjmu14SPisTs5/SpIrl9POviVhtvBraNBZv0nk4hlkxObe751wWdbJ 0Y+ZhRMvyhXZ2hAHaC12TbCs0efh1BMx/aogeKka+Op93Lk3WVgKcnC1nR7fG6U0kiwi cZVQ==
MIME-Version: 1.0
X-Received: by 10.152.10.72 with SMTP id g8mr2505117lab.50.1398114310698; Mon, 21 Apr 2014 14:05:10 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Mon, 21 Apr 2014 14:05:10 -0700 (PDT)
In-Reply-To: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>
Date: Mon, 21 Apr 2014 17:05:10 -0400
Message-ID: <CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com>
Subject: Re: Author disclosures and conflict of interest
From: Phillip Hallam-Baker <hallam@gmail.com>
To: lrosen@rosenlaw.com
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DcJ6gT6KiPTcY1geNt_s00qgiak
Cc: IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 21:05:22 -0000

Like the question 'are you a spy' which they used to ask when people
entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc
problem.

The people who are being paid to subvert the standards aren't going to say.

They might not even know that the objective is subversion.


Like many IETF participants I have substantial financial interests in
several Internet companies besides my employer. Am I meant to put
those in a blind trust?

And even if I did all that people would still assume that I am working
as an agent of the New World Order. Though quite how the other folk on
the conference call worked out that the helicopter is black still
puzzles me.


On Sun, Apr 20, 2014 at 1:18 PM, Lawrence Rosen <lrosen@rosenlaw.com> wrote=
:
> I=E2=80=99ve been skimming recent threads  on this list relating to work =
done (or
> not done) at IETF and was reminded of this from Science Magazine:
>
>
>
> Authorship Form and Conflict-of-Interest Statement
>
> To meet its responsibility to readers and to the public to provide clear =
and
> unbiased scientific results and analyses, Science believes that manuscrip=
ts
> (including Brevia, Essays, Perspectives, Policy Forums, Reports, Research
> Articles, Reviews, and Viewpoints) should be accompanied by clear
> disclosures from all authors of the nature and level of their contributio=
n
> to the article, their understanding regarding the obligation to share dat=
a
> and materials, and any affiliations, funding sources, or financial holdin=
gs
> that might raise questions about possible sources of bias. Before manuscr=
ipt
> acceptance, therefore, authors will be asked to sign an
> authorship/conflict-of-interest form. Specific information will be sent t=
o
> most authors at the time of manuscript revision.
>
> Authorship Form and Statement of Conflicts of Interest [PDF]
>
>
>
> Part IV regarding =E2=80=9CConflict of Interest=E2=80=9D is particularly =
relevant to
> standards organizations such as IETF. Such a disclosure requirement would
> further encourage everyone to trust and implement IETF specifications.
>
>
>
> This document follows the recommendations in On Being a Scientist: A Guid=
e
> to Responsible Conduct in Research, The National Academies Press, Third
> Edition (2009).
>
>
>
> /Larry
>
>
>
> Lawrence Rosen
>
> Rosenlaw & Einschlag (www.rosenlaw.com)
>
> 3001 King Ranch Road, Ukiah, CA 95482
>
> Cell: 707-478-8932   Fax: 707-485-1243
>
>



--=20
Website: http://hallambaker.com/


From nobody Mon Apr 21 14:07:51 2014
Return-Path: <R.E.Sonneveld@sonnection.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 595501A0296 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 14:07:49 -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
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 Sju0RbNKI90T for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 14:07:44 -0700 (PDT)
Received: from mx10.mailtransaction.com (mx10.mailtransaction.com [88.198.59.241]) by ietfa.amsl.com (Postfix) with ESMTP id 6694B1A028E for <ietf@ietf.org>; Mon, 21 Apr 2014 14:07:44 -0700 (PDT)
Received: from mx24.mailtransaction.com (mx21.mailtransaction.com [78.46.16.236]) by mx10.mailtransaction.com (Postfix) with ESMTP id 3gCL8V48jQz5Mh9k; Mon, 21 Apr 2014 23:07:38 +0200 (CEST)
Received: from jaguar.sonnection.nl (D57E1702.static.ziggozakelijk.nl [213.126.23.2]) by mx24.mailtransaction.com (Postfix) with ESMTP id 3gCL8V2k4Hz1L8cK; Mon, 21 Apr 2014 23:07:38 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by jaguar.sonnection.nl (Postfix) with ESMTP id F1CCC12316E; Mon, 21 Apr 2014 23:07:37 +0200 (CEST)
X-Virus-Scanned: amavisd-new at sonnection.nl
Received: from jaguar.sonnection.nl ([127.0.0.1]) by localhost (jaguar.sonnection.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 42KjBsLBRdQC; Mon, 21 Apr 2014 23:07:31 +0200 (CEST)
Received: from [192.168.1.49] (unknown [192.168.1.49]) by jaguar.sonnection.nl (Postfix) with ESMTPSA id C7DA2122EB0; Mon, 21 Apr 2014 23:07:30 +0200 (CEST)
Message-ID: <53558891.5080503@sonnection.nl>
Date: Mon, 21 Apr 2014 23:07:29 +0200
From: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
Organization: Sonnection B.V.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Douglas Otis <doug.mtview@gmail.com>
Subject: Re: DMARC and yahoo
References: <20140421163621.29166.qmail@joyce.lan> <53554A7B.20006@dcrocker.net> <5A812333-040A-4EF0-946A-8996D2E4B7EB@gmail.com>
In-Reply-To: <5A812333-040A-4EF0-946A-8996D2E4B7EB@gmail.com>
Content-Type: multipart/alternative; boundary="------------030000040900080902030108"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sonnection.nl; s=2009; t=1398114458; bh=Xazu/kPp0qe3lw6/n5pd1BMKV2FPkD8MFtMXWhKZu/4=; h=Message-ID:Date:From:To:Subject:From; b=ghI76bvT0Zf8S8L4/9IRpzMLOckvFMA38YZyOhch+Lu0wMqcWBe30zCFyGolGsaCQ A87MlZAjr8DfOfrghyXAdYv5LPuK/OEuUnWEK91TBP9jWRHGTiCNsS7IbRIUi7zM1Y NsHSHHyb0/4rXBI61YY9qU+ANko8r9kXLhJIP/xU=
DKIM-Filter: OpenDKIM Filter v2.8.2 mx10.mailtransaction.com 3gCL8V48jQz5Mh9k
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZoU1ShpRiDdjweWOS-2pY8n4UTM
Cc: John Levine <johnl@taugh.com>, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: R.E.Sonneveld@sonnection.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 21:07:49 -0000

This is a multi-part message in MIME format.
--------------030000040900080902030108
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi, Doug,

On 04/21/2014 09:20 PM, Douglas Otis wrote:
>
> On Apr 21, 2014, at 9:42 AM, Dave Crocker <dhc@dcrocker.net 
> <mailto:dhc@dcrocker.net>> wrote:
>
>> On 4/21/2014 9:36 AM, John Levine wrote:
>>> They could fix it if they
>>> wanted, e.g., by arranging to whitelist mail sources that don't match
>>> DMARC's authentication model but send mail people want.  This is not
>>> just mailing lists, of course.
>>
>>
>> Sorry, but I'm not quite understanding what additional mechanism you 
>> have in mind.
>>
>> Exactly who does exactly what?
>>
>> Who has to adopt it?
>>
>> How will it scale?
>
> Dear Dave,
>
> Each domain can simply point to their desired white-list. This can be 
> one published directly or simply referenced as described in:
>
> http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8
>
> This has elements from the moribund ADSP.  The sender wishing to 
> protect a domain while also applying policy like that of ADSP or DMARC 
> can offer receivers a rapid and scalable method to check third-party 
> domain authorizations.  This means senders are always able to defend 
> recipients who trust messages from their domain.  Please note, 
> authorizations can also require presence of a List-ID.

This doesn't answer Dave's questions: who has to adopt it and how will 
it scale.

Adoption: of course the owner of the sending domain has to adopt it, but 
is there also a role for the owners of mailing lists, invite services 
etc.? How will the sending domain ever know whether a mailing list is 
open or closed for example? How will it know which invite services will 
need a TPA exemption?

Scaling: how does the owner of the sending domain (potentially very 
large numbers of users) know to what mailing lists its users are 
subscribed, what invite services will potentially need this TPA 
authorization etc.? Furthermore, will it scale if mailing lists can be 
members of mailing lists and how will the sending domain know about this 
hierarchy or chain of mailing lists? So the technical howto might be the 
easy part of the solution, while the organizational howto will 
definitely be the difficult part...

/rolf

--------------030000040900080902030108
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">Hi, Doug,<br>
      <br>
      On 04/21/2014 09:20 PM, Douglas Otis wrote:<br>
    </div>
    <blockquote
      cite="mid:5A812333-040A-4EF0-946A-8996D2E4B7EB@gmail.com"
      type="cite"><br>
      On Apr 21, 2014, at 9:42 AM, Dave Crocker &lt;<a
        moz-do-not-send="true" href="mailto:dhc@dcrocker.net">dhc@dcrocker.net</a>&gt;
      wrote:<br>
      <br>
      <blockquote type="cite">On 4/21/2014 9:36 AM, John Levine wrote:<br>
        <blockquote type="cite">They could fix it if they<br>
          wanted, e.g., by arranging to whitelist mail sources that
          don't match<br>
          DMARC's authentication model but send mail people want. &nbsp;This
          is not<br>
          just mailing lists, of course.<br>
        </blockquote>
        <br>
        <br>
        Sorry, but I'm not quite understanding what additional mechanism
        you have in mind.<br>
        <br>
        Exactly who does exactly what?<br>
        <br>
        Who has to adopt it?<br>
        <br>
        How will it scale?<br>
      </blockquote>
      <br>
      <div>Dear Dave,</div>
      <div><br>
      </div>
      <div>Each domain can simply point to their desired white-list.
        This can be one published directly or simply referenced as
        described in:</div>
      <div><br>
      </div>
      <div><a moz-do-not-send="true"
          href="http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8">http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8</a></div>
      <div><br>
      </div>
      <div>This has elements from the moribund ADSP. &nbsp;The sender wishing
        to protect a domain while also applying policy like that of ADSP
        or DMARC can offer receivers a rapid and scalable method to
        check third-party domain authorizations. &nbsp;This means senders are
        always able to defend recipients who trust messages from their
        domain. &nbsp;Please note, authorizations can also require presence
        of a List-ID.&nbsp; <br>
      </div>
    </blockquote>
    <br>
    This doesn't answer Dave's questions: who has to adopt it and how
    will it scale.<br>
    <br>
    Adoption: of course the owner of the sending domain has to adopt it,
    but is there also a role for the owners of mailing lists, invite
    services etc.? How will the sending domain ever know whether a
    mailing list is open or closed for example? How will it know which
    invite services will need a TPA exemption?<br>
    <br>
    Scaling: how does the owner of the sending domain (potentially very
    large numbers of users) know to what mailing lists its users are
    subscribed, what invite services will potentially need this TPA
    authorization etc.? Furthermore, will it scale if mailing lists can
    be members of mailing lists and how will the sending domain know
    about this hierarchy or chain of mailing lists? So the technical
    howto might be the easy part of the solution, while the
    organizational howto will definitely be the difficult part...<br>
    <br>
    /rolf<br>
  </body>
</html>

--------------030000040900080902030108--


From nobody Mon Apr 21 16:11:38 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FD61A0309 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 16:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 SCq2o9Og1dc8 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 16:11:25 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id C23971A0304 for <ietf@ietf.org>; Mon, 21 Apr 2014 16:11:23 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WX087FOW006UYF@mauve.mrochek.com> for ietf@ietf.org; Mon, 21 Apr 2014 16:06:18 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; CHARSET=US-ASCII
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 21 Apr 2014 16:06:09 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6WX05ELUG00004W@mauve.mrochek.com>
Date: Mon, 21 Apr 2014 15:50:29 -0700 (PDT)
Subject: Re: What I've been wondering about the DMARC problem
In-reply-to: "Your message dated Mon, 21 Apr 2014 13:48:36 -0700" <CAL0qLwYXbTqkyzPqK2O2p5t_C-E+LhgdxfSscp0Pxxqqud4sZQ@mail.gmail.com>
References: <534ED376.8060303@bluepopcorn.net> <20140418013433.2763.qmail@joyce.lan> <CAL0qLwY4xVrPwABRhv90JSRF8wta0P5OCw_UWzVYOyUZk2-W4Q@mail.gmail.com> <01P6TRV1PBB000004W@mauve.mrochek.com> <CAL0qLwbordSBeAhEuwsb2GBkoiickdOebz7TwZODXDgw8EfezA@mail.gmail.com> <01P6WO10FRGY00004W@mauve.mrochek.com> <CAL0qLwYXbTqkyzPqK2O2p5t_C-E+LhgdxfSscp0Pxxqqud4sZQ@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/y7fCR1wIzFwhA8R9UxjugpyiDc0
Cc: Jim Fenton <fenton@bluepopcorn.net>, John Levine <johnl@taugh.com>, Ned Freed <ned.freed@mrochek.com>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 23:11:35 -0000

> On Mon, Apr 21, 2014 at 11:42 AM, Ned Freed <ned.freed@mrochek.com> wrote:

> > > If you say so, but I can't think of an example off the top of my head.
> >
> > What planet are you on? I get mail with intentionally invalid From: fields
> > all
> > the time. The domain usuall (but not always) exists, but the mailbox
> > returns an
> > error.
> >

> Rudeness aside, I'm on a planet where I can't remember the last time I got
> a message where the stuff after the "@" was a domain name that doesn't
> exist.  Maybe you get them, but I don't.  Sorry to burst your blustery
> bubble.
                                                                       
And have you bothered to read what I actually said, you would have noticed that
my statement and your "bubble burster" are not very far apart. To repeat, I
said that in my experience "the domain usually (but not always) exists".

You might also want to consider that people have implemented the .invalid hack.
I'm not hearing any reports of widespread message rejection because of it. Are
you?

				Ned


From nobody Mon Apr 21 18:16:40 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF431A010B for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 18:16:38 -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, SPF_PASS=-0.001] autolearn=ham
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 r79b9DWOQEfb for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 18:16:33 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 954551A00C2 for <ietf@ietf.org>; Mon, 21 Apr 2014 18:16:33 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id p10so4235357pdj.17 for <ietf@ietf.org>; Mon, 21 Apr 2014 18:16:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=8tqUU5r+8aow2LIQyyt1APcDPj93ZDY9v74l+xd2kaI=; b=DG3AEM3zo+Ds6JsU2v7EtEkEajdIVY3zYxsvvB8/cvRbDY7Qjg81zNlbCH9QAELe08 IOXrdKfOGIN8pfatzsXKnBOPhmIzzKsmqO4uR+wZH0bhUmrWYnNruPh/ObXMXV1uJRVG spmI9ccxcyj6nKH//2G+AdrAjDl+iwDHpHz9dGqFCFSR3/zvHtKDGQAR+8uIxNyPxN3E 9Bsq4b9JIExSpkRWWMdJAqd7G/ZlmttSgabnXj+/badkGwnOHW0NSV+stYOKrfi3mnfF fr21p/9998vUMyjlXb/pviDvIuI6Sn3XVa2CE/lhQk5uK0uIBBgXYpLEtfaTSlvdf1cb ZWeQ==
X-Received: by 10.68.181.165 with SMTP id dx5mr41593838pbc.38.1398129388442; Mon, 21 Apr 2014 18:16:28 -0700 (PDT)
Received: from [192.168.2.116] (c-67-188-1-12.hsd1.ca.comcast.net. [67.188.1.12]) by mx.google.com with ESMTPSA id id10sm80874023pbc.35.2014.04.21.18.16.26 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 21 Apr 2014 18:16:27 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_533A3416-3BAD-4CCC-9AC3-F8AEF8941B58"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC and yahoo
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <53558891.5080503@sonnection.nl>
Date: Mon, 21 Apr 2014 18:16:36 -0700
Message-Id: <34F5F7D7-9226-4D6F-9CF4-F8A84444E38A@gmail.com>
References: <20140421163621.29166.qmail@joyce.lan> <53554A7B.20006@dcrocker.net> <5A812333-040A-4EF0-946A-8996D2E4B7EB@gmail.com> <53558891.5080503@sonnection.nl>
To: R.E.Sonneveld@sonnection.nl
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2HFR5u4-ch_SVrF59aNbZVRWwKA
Cc: John Levine <johnl@taugh.com>, dcrocker@bbiw.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 01:16:38 -0000

--Apple-Mail=_533A3416-3BAD-4CCC-9AC3-F8AEF8941B58
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On Apr 21, 2014, at 2:07 PM, Rolf E. Sonneveld =
<R.E.Sonneveld@sonnection.nl> wrote:

> Hi, Doug,
>=20
> On 04/21/2014 09:20 PM, Douglas Otis wrote:
>>=20
>> On Apr 21, 2014, at 9:42 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>>=20
>>> On 4/21/2014 9:36 AM, John Levine wrote:
>>>> They could fix it if they
>>>> wanted, e.g., by arranging to whitelist mail sources that don't =
match
>>>> DMARC's authentication model but send mail people want.  This is =
not
>>>> just mailing lists, of course.
>>>=20
>>>=20
>>> Sorry, but I'm not quite understanding what additional mechanism you =
have in mind.
>>>=20
>>> Exactly who does exactly what?
>>>=20
>>> Who has to adopt it?
>>>=20
>>> How will it scale?
>>=20
>> Dear Dave,
>>=20
>> Each domain can simply point to their desired white-list. This can be =
one published directly or simply referenced as described in:
>>=20
>> http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8
>>=20
>> This has elements from the moribund ADSP.  The sender wishing to =
protect a domain while also applying policy like that of ADSP or DMARC =
can offer receivers a rapid and scalable method to check third-party =
domain authorizations.  This means senders are always able to defend =
recipients who trust messages from their domain.  Please note, =
authorizations can also require presence of a List-ID. =20
>=20
> This doesn't answer Dave's questions: who has to adopt it and how will =
it scale.

Dear Rolf,

Sorry, I thought the scheme was easy to understand.

The basic white-list hash-label publication scheme is a single and small =
DNS query referenced at a _tpa subdomain within the sender's domain in =
much the same manner _dmarc  and other policy schemes operate.  RRs TTL =
can be set at levels that provide sustainable query burdens.  DNS can =
also scale using anycast and support very high query rates.  DMARC =
senders would need to publish their white-list indicating support of =
this protocol and of course it could also be signaled within DMARC.  =
Since this list offers a low overhead service for recipients there =
should be quick implementation at the other end of the exchange by =
recipient ESPs.  This also affords senders full control over all of =
their desired policy exceptions. If there is a problem, senders would =
only have themselves to blame.

Please note, MLM software or =46rom header fields do not change at all.  =
The major portion of the effort would be by sending domains having a =
goal of offering better protection while preserving desired use.  The =
white-list can also be shared with other DMARC domains who trust the =
list's administration. Technically, this should be seen as a change to =
DKIM and SPF in a similar manner as ATSP did.  Of course, the change can =
be appended to existing processes.  There were necessary elements =
missing from ATPS which also required DKIM signatures to change that =
made deployment impractical.

> Adoption: of course the owner of the sending domain has to adopt it, =
but is there also a role for the owners of mailing lists, invite =
services etc.? How will the sending domain ever know whether a mailing =
list is open or closed for example? How will it know which invite =
services will need a TPA exemption?

At one time, we provided a reputation list that answered that very =
question, but there has not been a need for the MLM list for several =
years now.  If a sender receives any report of abuse, they can notify =
the list.  If there is not a timely response, the MLM can be =
de-authorized by the sender. Quick and painless.

> Scaling: how does the owner of the sending domain (potentially very =
large numbers of users) know to what mailing lists its users are =
subscribed, what invite services will potentially need this TPA =
authorization etc.?

Perhaps senders could ask their users which MLM they wish to use.  They =
could also monitor their DMARC feedback as well.

> Furthermore, will it scale if mailing lists can be members of mailing =
lists and how will the sending domain know about this hierarchy or chain =
of mailing lists? So the technical howto might be the easy part of the =
solution, while the organizational howto will definitely be the =
difficult part...

There is nothing wrong in having all the trusted MLMs listed to then =
permit list to list traffic.  It would not involve any complex changes =
to message signing or header field use either.   Use of TPA would have =
dramatically lower overhead than that caused by reverse DNS queries or =
that of chained SPF records.=20

Regards,
Douglas Otis=

--Apple-Mail=_533A3416-3BAD-4CCC-9AC3-F8AEF8941B58
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Diso-8859-1"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Apr 21, 2014, at 2:07 PM, Rolf E. =
Sonneveld &lt;<a =
href=3D"mailto:R.E.Sonneveld@sonnection.nl">R.E.Sonneveld@sonnection.nl</a=
>&gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">
 =20
    <meta content=3D"text/html; charset=3DISO-8859-1" =
http-equiv=3D"Content-Type">
 =20
  <div bgcolor=3D"#FFFFFF" text=3D"#000000">
    <div class=3D"moz-cite-prefix">Hi, Doug,<br>
      <br>
      On 04/21/2014 09:20 PM, Douglas Otis wrote:<br>
    </div>
    <blockquote =
cite=3D"mid:5A812333-040A-4EF0-946A-8996D2E4B7EB@gmail.com" =
type=3D"cite"><br>
      On Apr 21, 2014, at 9:42 AM, Dave Crocker &lt;<a =
moz-do-not-send=3D"true" =
href=3D"mailto:dhc@dcrocker.net">dhc@dcrocker.net</a>&gt;
      wrote:<br>
      <br>
      <blockquote type=3D"cite">On 4/21/2014 9:36 AM, John Levine =
wrote:<br>
        <blockquote type=3D"cite">They could fix it if they<br>
          wanted, e.g., by arranging to whitelist mail sources that
          don't match<br>
          DMARC's authentication model but send mail people want. =
&nbsp;This
          is not<br>
          just mailing lists, of course.<br>
        </blockquote>
        <br>
        <br>
        Sorry, but I'm not quite understanding what additional mechanism
        you have in mind.<br>
        <br>
        Exactly who does exactly what?<br>
        <br>
        Who has to adopt it?<br>
        <br>
        How will it scale?<br>
      </blockquote>
      <br>
      <div>Dear Dave,</div>
      <div><br>
      </div>
      <div>Each domain can simply point to their desired white-list.
        This can be one published directly or simply referenced as
        described in:</div>
      <div><br>
      </div>
      <div><a moz-do-not-send=3D"true" =
href=3D"http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8">ht=
tp://tools.ietf.org/html/draft-otis-dkim-tpa-label-06#page-8</a></div>
      <div><br>
      </div>
      <div>This has elements from the moribund ADSP. &nbsp;The sender =
wishing
        to protect a domain while also applying policy like that of ADSP
        or DMARC can offer receivers a rapid and scalable method to
        check third-party domain authorizations. &nbsp;This means =
senders are
        always able to defend recipients who trust messages from their
        domain. &nbsp;Please note, authorizations can also require =
presence
        of a List-ID.&nbsp; <br>
      </div>
    </blockquote>
    <br>
    This doesn't answer Dave's questions: who has to adopt it and how
    will it scale.<br></div></blockquote><div><br></div><div>Dear =
Rolf,</div><div><br></div><div>Sorry, I thought the scheme was easy to =
understand.</div><div><br></div><div>The basic white-list hash-label =
publication scheme is a single and small DNS query referenced at a _tpa =
subdomain within the sender's domain in much the same manner _dmarc =
&nbsp;and other policy schemes operate. &nbsp;RRs TTL can be set at =
levels that provide sustainable query burdens. &nbsp;DNS can also scale =
using anycast and support very high query rates. &nbsp;DMARC senders =
would need to publish their white-list indicating support of this =
protocol and of course it could also be signaled within DMARC. =
&nbsp;Since this list offers a low overhead service for recipients there =
should be quick implementation at the other end of the exchange by =
recipient ESPs. &nbsp;This also affords senders full control over all of =
their desired policy exceptions. If there is a problem, senders would =
only have themselves to blame.</div><div><br></div><div>Please note, MLM =
software or =46rom header fields do not change at all. &nbsp;The major =
portion of the effort would be by sending domains having a goal of =
offering better protection while preserving desired use. &nbsp;The =
white-list can also be shared with other DMARC domains who trust the =
list's administration. Technically, this should be seen as a change to =
DKIM and SPF in a similar manner as ATSP did. &nbsp;Of course, the =
change can be appended to existing processes. &nbsp;There were necessary =
elements missing from ATPS which also required DKIM signatures to change =
that made deployment impractical.</div><div><br></div><blockquote =
type=3D"cite"><div bgcolor=3D"#FFFFFF" text=3D"#000000">
   =20
    Adoption: of course the owner of the sending domain has to adopt it,
    but is there also a role for the owners of mailing lists, invite
    services etc.? How will the sending domain ever know whether a
    mailing list is open or closed for example? How will it know which
    invite services will need a TPA =
exemption?<br></div></blockquote><div><br></div><div>At one time, we =
provided a reputation list that answered that very question, but there =
has not been a need for the MLM list for several years now. &nbsp;If a =
sender receives any report of abuse, they can notify the list. &nbsp;If =
there is not a timely response, the MLM can be de-authorized by the =
sender. Quick and painless.</div><br><blockquote type=3D"cite"><div =
bgcolor=3D"#FFFFFF" text=3D"#000000">
   =20
    Scaling: how does the owner of the sending domain (potentially very
    large numbers of users) know to what mailing lists its users are
    subscribed, what invite services will potentially need this TPA
    authorization etc.? </div></blockquote><div><br></div><div>Perhaps =
senders could ask their users which MLM they wish to use. &nbsp;They =
could also monitor their DMARC feedback as well.</div><br><blockquote =
type=3D"cite"><div bgcolor=3D"#FFFFFF" text=3D"#000000">Furthermore, =
will it scale if mailing lists can
    be members of mailing lists and how will the sending domain know
    about this hierarchy or chain of mailing lists? So the technical
    howto might be the easy part of the solution, while the
    organizational howto will definitely be the difficult =
part...<br></div></blockquote><div><br></div><div>There is nothing wrong =
in having all the trusted MLMs listed to then permit list to list =
traffic. &nbsp;It would not involve any complex changes to message =
signing or header field use either. &nbsp; Use of TPA would have =
dramatically lower overhead than that caused by reverse DNS queries or =
that of chained SPF =
records.&nbsp;</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div></div></body></html>=

--Apple-Mail=_533A3416-3BAD-4CCC-9AC3-F8AEF8941B58--


From nobody Mon Apr 21 20:02:23 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01AD71A0025 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 20:02:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.526
X-Spam-Level: *
X-Spam-Status: No, score=1.526 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_SCAM_N13=3.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 yCzrbSenPj_y for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 20:02:17 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id AD0A91A0020 for <ietf@ietf.org>; Mon, 21 Apr 2014 20:02:17 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6X52IBLQO0000C5@mauve.mrochek.com> for ietf@ietf.org; Mon, 21 Apr 2014 19:57:11 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WZAZ2YYO000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Mon, 21 Apr 2014 19:57:05 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6X52G5HZM000052@mauve.mrochek.com>
Date: Mon, 21 Apr 2014 18:13:13 -0700 (PDT)
Subject: Re: DMARC and yahoo
In-reply-to: "Your message dated Mon, 21 Apr 2014 02:49:49 -0400" <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]>
References: <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]>
To: John C Klensin <john-ietf@jck.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tvujbBFVIZ1SSIhBih_Q_cMUoB8
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Theodore Ts'o <tytso@mit.edu>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 03:02:22 -0000

John Klensin writes:

> --On Monday, 21 April, 2014 08:26 +1200 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:

> >> IMO, this is quite elegant.  The Yahoo users continue to get
> >> the messages, you don't get cluttered by rejection-related
> >> complaints, and those Yahoo users who don't like the digest
> >> form can take it up with Yahoo or find other accounts to use.
> >
> > Unfortunately they can switch themselves back to normal mode
> > too. Digest mode is user-settable, and is very annoying because
> > it munges the Subject header. What's really needed is a
> > DMARC-safe mode (per subscriber) that optionally rewrites the
> > From.

As others have pointed out, the only way digest mode solves the problem at hand
is if you force it on every message *from* a domain with a p=reject
policy regardless of recipient.

> Brian, I think there are several ways to look at this and that
> there are some largely separable issues.  One of them, perhaps
> unreasonable and perhaps not, is that DMARC was developed by a
> collection of organizations who have a shared vision of how
> email should work, what is important, and what isn't.  Yahoo is
> a supporter/participant in that group, as are several people
> with sufficient IETF history and leadership roles to be
> knowledgeable about how to facilitate getting a document through
> the system.

> I think that raises some issues for the IETF and RFC Editor
> about how specifications developed entirely in other bodies --
> traditionally, a category known as "specifications developed
> elsewhere and republished for the convenience of the Internet
> community" -- should be handled.   While it no longer applies in
> the DMARC case, there are also some issues associated with
> moving stable specifications developed elsewhere through the
> IETF Standards Track (whether one calls that "fast track",
> "rubber stamp", or something more complementary).   Pete has
> mentioned that the IETF is looking at some of the issues
> involved; I hope the ISE, and RFC Editor Function more
> generally, are too.

Good point.

> As far as the mailman hack is concerned, I think there are two
> different relevant audiences/ affected communities:

> (i) Receivers who happen to have addresses associated with DMARC
> supporters, such as Yahoo, that have adopted a
> highly-restrictive policy.  Forcing them into Digest mode, and
> warning them that, if they turn it off, they are unlikely to
> receive any more list mail and will likely be dropped from the
> list seems to be to be appropriate.  It was with that audience
> in mind that I claimed that Jeffrey's action was elegant.  I
> still think so, YMMD.

It's not receivers who have implemented restrictive policies, it's any
receiver who implements DMARC and follows its recommendations for
other domains that implement such policies.

Good luck on determining who those are. As such, enabling conventional
digest mode for some subset of recipients doesn't solve anything.

> (ii) Senders who have chosen to send messages from mail
> providers who have adopted restrictive, DMARC-based, policies.
> From my point of view, those providers have made a decision that
> they aren't interested in having their mail users post messages
> to mailing lists.  If a mail providers wants to effectively
> restrict the types of mail their users can send, I think we have
> to defend their right to do that.

That really depends on whether or not they make that policy clear to people
signing up for their service. Has Yahoo done this?

> It is also reasonable to hope
> that users who think those services are useful will go elsewhere
> and for mailing list managers to protect themselves by denying
> posting privileges to such users or remove them from lists.

That's assuming they understand what's causing the issue and have the technical
acumen to make an account switch.

> I think it would be a great deal more ethical and professional if
> those providers took responsibility for that decision with an
> explicit announcement to their users, but that is really not an
> IETF problem.

It becomes one when they can point to an IETF document and say, "Nothing in
here comes right now and says what we're doing is wrong."

> As to your "DMARC-safe mode", I'm inclined to assume that Yahoo
> knew exactly what would happen if they made this move.

I'm not. There are far too many examples of organizations engaging in
groupthink and proceeeding down what turns out to be a distasterous path that
winds up costing them major $$$. (Watch "Waterworld" some time.)

Mind you, I'm not saying that this is what has happened at Yahoo. Rather, I'm
saying that absent convincing evidence to the contrary - and the one PR
statement I'm familiar with doesn't even come close to meeting that burden - we
should not make such assumptions.

I also note that other domains that operate in what I'll call "mixed use" (that
is, they're used to send out both personal and business transactional mail,
each of which call for a different DMARC profile) have addressed this issue
through the use of subdomains. For example, Paypal seems to use paypal.com
(with a p=reject DMARC record) for business transaction messages and
e.paypal.com (DKIM but no DMARC record) for everything else. ("e" for email?)

Of course implementing such a scheme on top of existing mixed use allocations
is unpalatable, to say the least. (Unless you were to begin preparing back when
the issues with mixed use domains became clear.) Or it may be that e.yahoo.com
is too close to yahoo.com (but yahoo.e.com presumably is not). Whatever. My
point is that there other alternatives to a blanket p=reject policy choice.

> To believe otherwise raises significant questions about the quality
> of development and review of the DMARC spec and hence whether
> the IETF or ISE should publish it in any form, at least in the
> absence of a rebuttal or public review and commentary.

I'm afraid I interpret several comments made on this list as asking - and some
answering - those questions already.

But the real question is how do we proceed. If publication of DMARC proceeds
as-is I think a "DMARC Considered Harmful" document is the least unpalatable
outcome. Beyond that things get very ugly indeed.

> The belief that it was intentional is also reinforced by the
> observation that this problem has now been known for quite a
> while (in Internet time) and Yahoo has not chosen to modify
> their preferences to some other option.  Given that, I think we
> should be very cautious about recommending a technique to
> subvert their intentions: such actions have too much history of
> leading to counter-actions that have even worse effects.

Sorry, I'm afraid I disagree. In fact I think it's exactly the opposite.
At a minimum we need to:

(0) Document that the choice of a p=reject is inapproriate for anything
    but a domain devoted to business transaction email and fully describe the
    consequences of using such a policy on other sorts of domains.
(1) Document alternatives to labeling your mixed mode domain with p=reject.
(2) Describe the various mitigation strategies - and their consequences - for
    agents dealing with poor DMARC policy choices, including but not limited to
    advice to MLMs.

And let's keep in mind that this is far more than a simple game of tit-for-tat.
For one thing, DMARC is utterly dependent not only on the willingness of
senders to set up policies, but also on receivers to enforce those policies.
That alone places huge constraints on what is possible.

And for another, by abdicating our responsibilities to do (2), we not only lose
the opportunity to help MLMs choose the best option for their situation, we
also lose the opporunity to explain the consequences of poor choices on their
part. 

				Ned


From nobody Mon Apr 21 20:43:23 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 839121A003D for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 20:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.5
X-Spam-Level: 
X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_SCAM_N13=3.1, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-2.3] autolearn=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 PlXznJj-Lfi4 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 20:43:17 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7AB881A002F for <ietf@ietf.org>; Mon, 21 Apr 2014 20:43:17 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3M3h9Gv025017 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 21 Apr 2014 20:43:12 -0700
Message-ID: <5355E4CB.3060008@dcrocker.net>
Date: Mon, 21 Apr 2014 20:40:59 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com
Subject: Re: DMARC and yahoo
References: <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]> <01P6X52G5HZM000052@mauve.mrochek.com>
In-Reply-To: <01P6X52G5HZM000052@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 21 Apr 2014 20:43:12 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CdcbGuWPsocw7dzm2IQ3zu6Wkxg
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 03:43:21 -0000

On 4/21/2014 6:13 PM, ned+ietf@mauve.mrochek.com wrote:
> Sorry, I'm afraid I disagree. In fact I think it's exactly the opposite.
> At a minimum we need to:
>
> (0) Document that the choice of a p=reject is inapproriate for anything
>      but a domain devoted to business transaction email and fully describe the
>      consequences of using such a policy on other sorts of domains.
> (1) Document alternatives to labeling your mixed mode domain with p=reject.
> (2) Describe the various mitigation strategies - and their consequences - for
>      agents dealing with poor DMARC policy choices, including but not limited to
>      advice to MLMs.


There already is a first-round internet-draft formulated to be a BCP 
that could be a reasonable home for including such statements:

      http://tools.ietf.org/html/draft-crocker-dmarc-bcp-03

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Apr 22 03:33:46 2014
Return-Path: <ynir.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E6711A0366 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 03:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 WF1BxHIQYycW for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 03:33:37 -0700 (PDT)
Received: from mail-wg0-x230.google.com (mail-wg0-x230.google.com [IPv6:2a00:1450:400c:c00::230]) by ietfa.amsl.com (Postfix) with ESMTP id A23D81A0362 for <ietf@ietf.org>; Tue, 22 Apr 2014 03:33:37 -0700 (PDT)
Received: by mail-wg0-f48.google.com with SMTP id l18so3659972wgh.31 for <ietf@ietf.org>; Tue, 22 Apr 2014 03:33:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=k7h3AlgvqbnhvG9zd4BfOxmoCdcJ+GMOFo3Z2UTZJEI=; b=DdjwR+c0e/fDMnB9O3yDqBFnmF35WcHG/l2oxrefXpRrjORR2CDqjHFJTqphpjSc8H ftFCY86vsPK/RKqImWZuPLcenp2YUK5JwkhqhE7i4BDoaWblK+0B9DqHmo622sF7BFf1 ItgPan8WWTYV5LuLQdlyOA5M5i7JhPHQ2n3I382kLzAS1Zw+6bbe+v2cArb9nOoB2l5k KCXf9ZICI2vs0rOoeY9ncOCQBbYYjBYkCk1v6mQ0hwvsbW7l3KCxRK3ffOmaVozH5nIP Pazl2ObzChxsCF2mIaqomIgrxWgqAZx6N3ADwWP1y/h3DZgDsVLGhJu0Ahvi8K91qFg4 8e+Q==
X-Received: by 10.180.207.10 with SMTP id ls10mr18121564wic.22.1398162811727;  Tue, 22 Apr 2014 03:33:31 -0700 (PDT)
Received: from [172.24.248.99] (dyn32-131.checkpoint.com. [194.29.32.131]) by mx.google.com with ESMTPSA id uc3sm21779071wib.10.2014.04.22.03.33.30 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Apr 2014 03:33:30 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_24C1F93B-72D0-472B-825D-F9A4450A5386"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC and yahoo
From: Yoav Nir <ynir.ietf@gmail.com>
In-Reply-To: <01P6X52G5HZM000052@mauve.mrochek.com>
Date: Tue, 22 Apr 2014 13:33:28 +0300
Message-Id: <28455CFF-203A-43FC-B248-F48785AB10CC@gmail.com>
References: <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]> <01P6X52G5HZM000052@mauve.mrochek.com>
To: ned+ietf@mauve.mrochek.com
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SNgPpcKi1lHeO5MzpBXPy5LhWQ8
Cc: "ietf\\@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 10:33:42 -0000

--Apple-Mail=_24C1F93B-72D0-472B-825D-F9A4450A5386
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Apr 22, 2014, at 4:13 AM, ned+ietf@mauve.mrochek.com wrote:

> John Klensin writes:
>=20
>> --On Monday, 21 April, 2014 08:26 +1200 Brian E Carpenter
>> <brian.e.carpenter@gmail.com> wrote:
>=20
>>>> IMO, this is quite elegant.  The Yahoo users continue to get
>>>> the messages, you don't get cluttered by rejection-related
>>>> complaints, and those Yahoo users who don't like the digest
>>>> form can take it up with Yahoo or find other accounts to use.
>>>=20
>>> Unfortunately they can switch themselves back to normal mode
>>> too. Digest mode is user-settable, and is very annoying because
>>> it munges the Subject header. What's really needed is a
>>> DMARC-safe mode (per subscriber) that optionally rewrites the
>>> From.
>=20
> As others have pointed out, the only way digest mode solves the =
problem at hand
> is if you force it on every message *from* a domain with a p=3Dreject
> policy regardless of recipient.

That=92s one way to deal with it. The MLM software could identify such =
messages, and send them to the list recipients Looking like a forwarded =
message:

From: ietf <ietf-bounces@ietf.org>
To: ietf@ietf.org
CC: Joe Blow <joeblow@yahoo.com>
Subject Re: DMARC and yahoo

Joe Blow <joeblow@yahoo.com> sent a message from a domain with a =
p=3Dreject policy. To learn more about this issue, go to =
https://www.ietf.org/mailman/dmarc-issue

Begin forwarded message:=20

> From: Joe Blow <joeblow@yahoo.com>
> Sent: Tuesday, April 22, 2014 12:30 PM
> To: ietf@ietf.org
> Subject: Re: DMARC and yahoo
>
> I think you guys are making too much of this whole DMARC issue with =
Yahoo.



--Apple-Mail=_24C1F93B-72D0-472B-825D-F9A4450A5386
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Apr 22, 2014, at 4:13 AM, <a =
href=3D"mailto:ned+ietf@mauve.mrochek.com">ned+ietf@mauve.mrochek.com</a> =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div style=3D"font-size: 12px; font-style: normal; =
font-variant: normal; font-weight: normal; letter-spacing: normal; =
line-height: normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-stroke-width: 0px;">John Klensin =
writes:<br><br><blockquote type=3D"cite">--On Monday, 21 April, 2014 =
08:26 +1200 Brian E Carpenter<br>&lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a=
>&gt; wrote:<br></blockquote><br><blockquote type=3D"cite"><blockquote =
type=3D"cite"><blockquote type=3D"cite">IMO, this is quite elegant. =
&nbsp;The Yahoo users continue to get<br>the messages, you don't get =
cluttered by rejection-related<br>complaints, and those Yahoo users who =
don't like the digest<br>form can take it up with Yahoo or find other =
accounts to use.<br></blockquote><br>Unfortunately they can switch =
themselves back to normal mode<br>too. Digest mode is user-settable, and =
is very annoying because<br>it munges the Subject header. What's really =
needed is a<br>DMARC-safe mode (per subscriber) that optionally rewrites =
the<br>From.<br></blockquote></blockquote><br>As others have pointed =
out, the only way digest mode solves the problem at hand<br>is if you =
force it on every message *from* a domain with a p=3Dreject<br>policy =
regardless of recipient.<br></div></blockquote></div><br><div>That=92s =
one way to deal with it. The MLM software could identify such messages, =
and send them to the list recipients Looking like a forwarded =
message:</div><div><br></div><div>From: ietf &lt;<a =
href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org</a>&gt;</div><=
div>To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a></div><div>CC: =
Joe Blow &lt;<a =
href=3D"mailto:joeblow@yahoo.com">joeblow@yahoo.com</a>&gt;</div><div>Subj=
ect Re: DMARC and yahoo</div><div><br></div><div>Joe Blow &lt;<a =
href=3D"mailto:joeblow@yahoo.com">joeblow@yahoo.com</a>&gt; sent a =
message from a domain with a p=3Dreject policy. To learn more about this =
issue, go to <a =
href=3D"https://www.ietf.org/mailman/dmarc-issue">https://www.ietf.org/mai=
lman/dmarc-issue</a></div><div><br></div><div>Begin forwarded =
message:&nbsp;</div><div><br></div><div>&gt; From: Joe Blow &lt;<a =
href=3D"mailto:joeblow@yahoo.com">joeblow@yahoo.com</a>&gt;</div><div>&gt;=
 Sent: Tuesday, April 22, 2014 12:30 PM</div><div>&gt; To: <a =
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a></div><div>&gt; Subject: =
Re: DMARC and yahoo</div><div>&gt;</div><div>&gt; I think you guys are =
making too much of this whole DMARC issue with =
Yahoo.</div><div><br></div><div><br></div></body></html>=

--Apple-Mail=_24C1F93B-72D0-472B-825D-F9A4450A5386--


From nobody Tue Apr 22 07:12:58 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34EAD1A0406 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 07:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.526
X-Spam-Level: *
X-Spam-Status: No, score=1.526 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HK_SCAM_N13=3.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 ppBjmfY4wRSc for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 07:12:50 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id EAF721A03FF for <ietf@ietf.org>; Tue, 22 Apr 2014 07:12:49 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6XSHX26WG00015L@mauve.mrochek.com> for ietf@ietf.org; Tue, 22 Apr 2014 07:07:45 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WZAZ2YYO000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 22 Apr 2014 07:07:40 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6XSHUZT9K000052@mauve.mrochek.com>
Date: Tue, 22 Apr 2014 07:03:44 -0700 (PDT)
Subject: Re: DMARC and yahoo
In-reply-to: "Your message dated Mon, 21 Apr 2014 20:40:59 -0700" <5355E4CB.3060008@dcrocker.net>
References: <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]> <01P6X52G5HZM000052@mauve.mrochek.com> <5355E4CB.3060008@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/odsmvBpiVCFTyQw9esBxw_3W7_Y
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 14:12:54 -0000

> On 4/21/2014 6:13 PM, ned+ietf@mauve.mrochek.com wrote:
> > Sorry, I'm afraid I disagree. In fact I think it's exactly the opposite.
> > At a minimum we need to:
> >
> > (0) Document that the choice of a p=reject is inapproriate for anything
> >      but a domain devoted to business transaction email and fully describe the
> >      consequences of using such a policy on other sorts of domains.
> > (1) Document alternatives to labeling your mixed mode domain with p=reject.
> > (2) Describe the various mitigation strategies - and their consequences - for
> >      agents dealing with poor DMARC policy choices, including but not limited to
> >      advice to MLMs.


> There already is a first-round internet-draft formulated to be a BCP
> that could be a reasonable home for including such statements:

>       http://tools.ietf.org/html/draft-crocker-dmarc-bcp-03

Yes, that's the obvious place to put this material, rather than putting it
in the base specification. But then the base specification has to reference
this in a normative fashion.

Of course "formulated to be a BCP" doesn't imply actual publication as a BCP,
but even so there would be something a bit odd about having DMARC base as 
independent publication and the DMARC BCP as IETF work.

				Ned


From nobody Tue Apr 22 08:07:09 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 23FDF1A0515 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 08:07:08 -0700 (PDT)
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] autolearn=ham
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 e9SvY-fVOPK4 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 08:07:03 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3FAD31A0227 for <ietf@ietf.org>; Tue, 22 Apr 2014 08:07:03 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3MF6sYB014860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 22 Apr 2014 08:06:57 -0700
Message-ID: <5356850D.70206@dcrocker.net>
Date: Tue, 22 Apr 2014 08:04:45 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: DMARC and yahoo
References: <DFC043AEFFD831DBABB4A5D9@[192.168.1.128]> <01P6X52G5HZM000052@mauve.mrochek.com> <5355E4CB.3060008@dcrocker.net> <01P6XSHUZT9K000052@mauve.mrochek.com>
In-Reply-To: <01P6XSHUZT9K000052@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 22 Apr 2014 08:06:58 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YXvMYoxR5MA78qn-MhygLnpb4yk
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 15:07:08 -0000

On 4/22/2014 7:03 AM, Ned Freed wrote:
> Yes, that's the obvious place to put this material, rather than putting it
> in the base specification. But then the base specification has to reference
> this in a normative fashion.


While it's plausible and reasonable that a technical specification could 
contain usage guidance like this, it's not at all required.

I believe it for more often that "implications" are typically put into 
BCP-like documents.

For example:

    DomainKeys Identified Mail (DKIM) and Mailing Lists
    https://tools.ietf.org/html/rfc6377

As for doing a BCP on a document that isn't an IETF consensus document, 
we do versions of that periodically, for work developed outside that is 
used by, or affects, IETF-based specs.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Apr 22 08:08:33 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B8531A0329 for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 17:11:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.664
X-Spam-Level: 
X-Spam-Status: No, score=0.664 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_SOFTFAIL=0.665] autolearn=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 ypoG-JycslwL for <ietf@ietfa.amsl.com>; Mon, 21 Apr 2014 17:11:44 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 708DD1A0321 for <ietf@ietf.org>; Mon, 21 Apr 2014 17:11:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id E3841206D7 for <ietf@ietf.org>; Mon, 21 Apr 2014 20:10:50 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GhB4UpJ4GPhh for <ietf@ietf.org>; Mon, 21 Apr 2014 20:10:45 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-50-177-27-27.hsd1.ma.comcast.net [50.177.27.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS for <ietf@ietf.org>; Mon, 21 Apr 2014 20:10:45 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 787B981B8A; Mon, 21 Apr 2014 20:11:33 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: ietf@ietf.org
Subject: Thanks for improved editing function over at the rfc-editor
Date: Mon, 21 Apr 2014 20:11:33 -0400
Message-ID: <tsloazuxlxm.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XRLxnaSg2spcwo0h-Tj_ZXSInZQ
X-Mailman-Approved-At: Tue, 22 Apr 2014 08:08:31 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 00:11:45 -0000

I've been through a number of auth48s lately and I just noticed that the
editing process that the RFC editor is using introduces significantly
fewer errors than it used to.
Back ind the 2004-2007 era, it was actually very common to see authors
objecting to a number of auth48 changes.  I saw this in my own documents
as well as documents in my area.

I see fewer documents these days, but I do see enough documents that I
have confidence in my claim that the auth48 process seems to be much
smoother than it used to be.

This is really nice.  Thanks for the ongoing great work.


From nobody Tue Apr 22 08:08:47 2014
Return-Path: <tony.putman@alcatel-lucent.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D45531A02D7; Tue, 22 Apr 2014 02:57:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham
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 uf7e3JXpFr_5; Tue, 22 Apr 2014 02:57:00 -0700 (PDT)
Received: from hoemail2.alcatel.com (hoemail2.alcatel.com [192.160.6.149]) by ietfa.amsl.com (Postfix) with ESMTP id C08A91A01D9; Tue, 22 Apr 2014 02:56:55 -0700 (PDT)
Received: from fr712usmtp2.zeu.alcatel-lucent.com (h135-239-2-42.lucent.com [135.239.2.42]) by hoemail2.alcatel.com (8.13.8/IER-o) with ESMTP id s3M9ulVi025546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Tue, 22 Apr 2014 04:56:49 -0500 (CDT)
Received: from FR711WXCHHUB02.zeu.alcatel-lucent.com (fr711wxchhub02.zeu.alcatel-lucent.com [135.239.2.112]) by fr712usmtp2.zeu.alcatel-lucent.com (GMO) with ESMTP id s3M9ul0U008820 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 22 Apr 2014 11:56:47 +0200
Received: from FR711WXCHMBA01.zeu.alcatel-lucent.com ([169.254.1.223]) by FR711WXCHHUB02.zeu.alcatel-lucent.com ([135.239.2.112]) with mapi id 14.02.0247.003; Tue, 22 Apr 2014 11:56:47 +0200
From: "PUTMAN, Tony (Tony)" <tony.putman@alcatel-lucent.com>
To: Yoav Nir <ynir.ietf@gmail.com>
Subject: RE: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standard
Thread-Topic: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standard
Thread-Index: AQHPUER+0n62SMALMEq7nBB2qf17BpsWIUEw///ldYCAB3nA4A==
Date: Tue, 22 Apr 2014 09:56:46 +0000
Message-ID: <14BE57EA00BC0C469E17B5AD698FE67766664FCB@FR711WXCHMBA01.zeu.alcatel-lucent.com>
References: <20140404202750.31367.2461.idtracker@ietfa.amsl.com> <14BE57EA00BC0C469E17B5AD698FE67766664CE4@FR711WXCHMBA01.zeu.alcatel-lucent.com> <B12490A2-2D31-4E32-9D9E-ACB80C91FB8C@gmail.com>
In-Reply-To: <B12490A2-2D31-4E32-9D9E-ACB80C91FB8C@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.239.27.38]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BdG2MLW8e45T2Af3dB-3NHW6E4Y
X-Mailman-Approved-At: Tue, 22 Apr 2014 08:08:46 -0700
Cc: "ipsec@ietf.org" <ipsec@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 09:57:05 -0000

Hi Yoav,

Yes, that's what I meant; your suggestion is fine with me.  To be honest, I=
 wasn't sure whether this was a "substantive comment" or not, but the quest=
ion was raised to me by a colleague and I thought that I should pass it on.=
  Apologies if my comment was too brief (and for the late follow-up).

Tony

-----Original Message-----
From: Yoav Nir [mailto:ynir.ietf@gmail.com]
Sent: Thursday, April 17, 2014 6:42 PM
To: PUTMAN, Tony (Tony)
Cc: ietf@ietf.org; ipsec@ietf.org
Subject: Re: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.=
txt> (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standar=
d

Hi, Tony

Thanks for the review.

I assume you mean that you don=92t sign with public keys. Replacing =93sign=
=94 with =93validate=94 makes for a strange sentence, because the sentence =
is about sending (and presumably signing) rather than receiving (and valida=
ting).

How about:
=93If multiple certificate are sent, the first MUST contain the public key =
associated with the private key used to sign the AUTH payload=94

Yoav


On Apr 17, 2014, at 8:23 PM, PUTMAN, Tony (Tony) <tony.putman@alcatel-lucen=
t.com> wrote:

> All,
>
> In section 3.6 (top of page 94), there is the statement,
>  "If multiple certificates
>   are sent, the first certificate MUST contain the public key used to
>   sign the AUTH payload."
>
> "sign" should be "validate".
>
> Regards,
> Tony
> --
> Tony Putman
> Alcatel-Lucent Technologies
>
> -----Original Message-----
> From: IPsec [mailto:ipsec-bounces@ietf.org] On Behalf Of The IESG
> Sent: Friday, April 04, 2014 9:28 PM
> To: IETF-Announce
> Cc: ipsec@ietf.org
> Subject: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.tx=
t> (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standard
>
>
> The IESG has received a request from the IP Security Maintenance and
> Extensions WG (ipsecme) to consider the following document:
> - 'Internet Key Exchange Protocol Version 2 (IKEv2)'
>  <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> as Internet Standard
>
> The IESG plans to make a decision in the next few weeks, and solicits
> final comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2014-04-18. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>   This document describes version 2 of the Internet Key Exchange (IKE)
>   protocol.  IKE is a component of IPsec used for performing mutual
>   authentication and establishing and maintaining Security Associations
>   (SAs).  This document replaces and updates RFC 5996, and includes all
>   of the errata for it, and it is intended to update IKEv2 to be
>   Internet Standard.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-kivinen-ipsecme-ikev2-rfc5996bis/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-kivinen-ipsecme-ikev2-rfc5996bis/ba=
llot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec
>
> _______________________________________________
> IPsec mailing list
> IPsec@ietf.org
> https://www.ietf.org/mailman/listinfo/ipsec


From nobody Tue Apr 22 12:21:18 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 173831A003D for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 12:21:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.638
X-Spam-Level: 
X-Spam-Status: No, score=0.638 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 f1b62LsU9EEq for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 12:21:11 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4613E1A022B for <ietf@ietf.org>; Tue, 22 Apr 2014 12:21:11 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.143.153]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3MJKiY7025282 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Apr 2014 12:20:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398194459; bh=v6FE9CzTsmXG15QAKf7YM6ePN1hnJkISyuGg31RpWKM=; h=Date:To:From:Subject:Cc; b=g58nBUGgzN1oK48WL1T0PfRBlPqfwJZlwGxdTg5EDVqkbuHDh49b5YhmiiczKub7t /bQJZ62dKtqKxPsC5iVRVpbcvPIumocsVIzE84LKilNb3F3t33vVfCyH9/vMU6dGfa N/E/T+TQAfn/qxZXHpj74xe8gPV6+H1s2lfuc4WU=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398194459; i=@elandsys.com; bh=v6FE9CzTsmXG15QAKf7YM6ePN1hnJkISyuGg31RpWKM=; h=Date:To:From:Subject:Cc; b=dTSjxMSJOHD2uCZIkz6kDySiWUPwiBnkIPcOR1m/Z1Sdn/Z96yASaWeiVsSjEO/Gc hNffNOazAzYpugn+qDCGOKAyh9JSyxjzjBLy5C9Qx2dMbWcPQY+oqiY+HrN/9aGJtx bDUtfSUI0r7+ltKhInTAWJ8E+OT+uhar+moDzzuc=
Message-Id: <6.2.5.6.2.20140422074852.0d368728@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 22 Apr 2014 11:53:19 -0700
To: Nevil Brownlee <rfc-ise@rfc-editor.org>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Review of draft-kucherawy-dmarc-base-04
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/igV1Rx3kynNeZQtXNqs36wjFHrs
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 19:21:17 -0000

Hi Nevil,

I reviewed draft-kucherawy-dmarc-base-04.  I am copying the review to 
Murray as a courtesy, and ietf@ietf.org as there has been a lot of 
discussion about the matter on that mailing list.  I presume that a 
healthy technical dialog with the authors is appropriate.  I'll defer 
to you on how to handle the review.

draft-kucherawy-dmarc-base-04 proposes a scalable mechanism by which 
a mail sending organization can express, using the Domain Name 
System, domain-level policies and preferences for message validation, 
disposition, and reporting, and a mail receiving organization can use 
those policies and preferences to improve mail handling.  It's a 
length document (76 pages).  The mechanism builds upon IETF 
specifications such as DKIM, SPF and ARF.  I'll use the soon-to-be 
published specification for SPF as a reference instead of the 
reference listed in the document.

In my opinion the document is not ready for publication in the 
Independent Submissions Stream.  Overall, the is more discussion 
about policy, anti-abuse, etc. compared to technical material.  There 
is a significant amount of tutorial material in the document.  My 
suggestion is to explain how the mechanism works, then provide the 
details without getting into lengthy details unless the intention is 
to set best common practices.  The usage of RFC 2119 key words comes 
out as prescribing requirements instead of focusing on 
interoperability.  The IANA requests seem problematic as it might not 
fit the assertion of IANA allocations not requiring IETF action.

The main issue is that the proposed mechanism extends SPF to cover a 
header field.  That may work well with personal messages, 
notifications about bank payments, etc.  It can be overly restrictive 
in cases where a MUA is not being used, e.g. someone entering his/her 
email address for use as the author of a notification (see 
https://mailarchive.ietf.org/arch/msg/httpbisa/CUCtnKhz133AXM_b9tVHZmn2O2Y ).

 From Section 1:

   "DMARC differs from previous approaches to policy advertisement (e.g.,
    [SPF] and [ADSP]) in that:

    o  Authentication technologies are:

       1.  decoupled from any technology-specific policy mechanisms; and

       2.  used solely to establish reliable per-message domain-level
           identifiers.

    o  Multiple authentication technologies are used to:

       1.  reduce the impact of transient authentication errors

       2.  reduce the impact of site-specific configuration errors and
           deployment gaps

       3.  enable more use cases than any individual technology supports
           alone"

I read the following:
http://forums.cpanel.net/f43/yahoos-new-dmarc-policy-causing-mailman-bounces-402751.html
http://digest.sialia.com/?rm=message;id=849627

It's difficult to determine whether there was a reduction in impact 
compared to previous email authentication initiatives.  DMARC 
actually couples two email policy mechanisms instead of decoupling them.

DMARC attempts to solve the phishing problem (see Section 1.2) by 
preventing bad people from sending mail which claims to come from 
legitimate senders.  Section 1.2 sounds like a mix between problem 
definition and marketing.  The following sentence is difficult to understand:

   "Thus, DMARC is significantly informed by ongoing efforts to enact
    large-scale, Internet-wide, anti-phishing measures."

The document then states that:

   "Although DMARC can only be used to combat specific forms of exact-
    domain spoofing directly, the DMARC mechanism is a substantial step
    towards the creation of reliable and defensible message streams."

The above sentence tries to sell the technology.

 From Section 2.1:

   "One common attack on Internet users involves imitating mail from a
    reputable mail sender while including malicious content of some kind.
    The most damaging version of this attack, both to end-users and to
    organizations, uses the RFC5322 From: address of the reputable
    sender."

In simple terms, the technology is about protecting the email address 
that is visible to the end-user.

According to Section 3, the document uses terminology from RFC 
5598.  I suggest further review of the document to ensure consistent 
usage of the terminology in that RFC.

 From Section 4:

   "A Mail Receiver MUST consider an arriving message to pass the DMARC
    test if and only if one or more of the underlying message
    authentication mechanisms pass with proper identifier alignment."

The above sets a requirement based on underlying message 
authentication mechanisms.  I gather that it is the mechanisms 
defined in Section 3.1.1.

 From Section 6:

   "Mail Receivers MAY choose to reject or quarantine email even if email
    passes the DMARC mechanism check."

The above can be interpreted in two ways:

   (a) The specification is getting into local (receiver) policy.

   (b) The organization advertising a DMARC policy takes responsibility
       for all messages that pass the DMARC mechanism check.


   "Mail Receivers are encouraged to maintain anti-abuse technologies
    to combat the possibility of DMARC-enabled criminal campaigns."

The above sentence does not belong in a document that defines a 
mechanism.  Who determines what is a criminal compaign?

   "Mail Receivers need to make a best effort not to increase the likelihood
    of accepting abusive mail if they choose not to comply with a Domain
    Owner's reject, against policy."

The above sounds like preaching for anti-abuse.

   "At a minimum, addition of the Authentication-Results header field
   (see [AUTH-RESULTS]) is RECOMMENDED when delivery of failing mail
    is done."

Why is that header field recommended as a minimum?

   "Mail Receivers are only obligated to report reject or quarantine
    policy actions in aggregate feedback reports that are due to DMARC
    policy."

The above sentence binds or compels mail receivers.  I don't think 
that it is the purpose of a technical specification to set moral or 
legal obligations.

  "If local policy information is exposed, abusers can gain insight
   into the effectiveness and delivery rates of spam campaigns."

It sounds like the document is also trying to mitigate spam problems.

   "Mail Receivers SHOULD also implement reporting instructions of DMARC
    in place of any extensions to SPF or DKIM that might enable such
    reporting."

The above recommendation is to replace extensions defined in IETF 
specifications with what is defined in the document.

 From Section 7.3.1:

   "Operators implementing this specification also implement an augmented
    version of [AFRF] as follows:"

The above extends an IETF specification.

In Section 7.4:

   "These reports SHOULD include as much of the message and message header
    as is reasonable to support the Domain Owner's investigation into what
    caused the message to fail authentication and track down the sender."

The recommendation looks like what one would usually see in a legal document.

In Section 8:

   "If the RFC5322.From domain does not exist in the DNS, Mail Receivers
    SHOULD direct the receiving SMTP server to reject the message."

Why is there such a recommendation?  What is a mail receiver?  I am 
asking the question as there is "receiving SMTP server" in that sentence.

In Section 10.1:

   "Have no RFC5322.From field (which is also forbidden under RFC 5322
    [MAIL])"

Where is it stated in RFC 5322 that it is forbidden?  That RFC 
specifies a syntax for the Internet Message Format.

   "Such messages SHOULD be rejected."

Why should such messages be rejected?

   "Heuristics applied in the absence of use by a Domain Owner of either
    SPF or DKIM (e.g., [Best-Guess-SPF]) SHOULD NOT be used, as it may be
    the case that the Domain Owner wishes a Message Receiver not to
    consider the results of that underlying authentication protocol at
    all."

This is more of a reminder that there was agreement in some IETF 
working group not to say anything about Best-Guess-SPF.

In Section 10.3:

   "If email is subject to the DMARC policy of "quarantine", the Mail
    Receiver SHOULD quarantine the message."

The above prescribes what the mail receiver should do.

   "If email is subject to the DMARC policy of "reject", the Mail
    Receiver SHOULD reject the message (see Section 15.4)."

The above has been a subject of debate on several mailing lists.

Section 14 is about privacy considerations.  The mechanism proposed 
in this document enables the domain name registrant to track usage of 
its domain name in email across DMARC-compliant sites on the internet 
without prior agreement between the relevant entities.  Based on my 
reading of RFC 6591 I think that the privacy considerations does not 
explain the extent of the data exposure.  The reader may construe 
"sender and recipient identifiers" as the email addresses of the 
sender and recipient only.

In Section 14.4:

   "This document encourages use of secure transport mechanisms to
    prevent loss of private data to third parties that may be able to
    monitor such transmissions.  Unencrypted mechanisms should be
    avoided."

Given the state spying reports an encouragement to use secure 
transport mechanisms sounds like a feeble attempt at securing the 
private data which will be sent across the internet.

 From Section 15.4:

   "550 5.7.1 Email rejected per DMARC policy for example.com"

I note that the company that has been mentioned in DMARC discussions 
does not follow the example given.

Section 16 describes IANA registry updates.  I suggest contacting the 
IETF Application Directors for information about the procedure to be 
followed for the registry updates.

Section 16.4 defines a DMARC Tag Registry.  The proposed registry 
policy for new entries is to have "a published RFC that has had IETF 
Review".  I suggest that the authors contact the IESG for advice 
about this registry.  It is highly unusual to have a RFC in the 
Independent Submissions Stream requesting the creation of a (IANA) registry.

 From Section 17.4:

   "Generally, display name attacks are out of scope for DMARC"

Are display name attacks out of scope or not?  The above can be 
interpreted as display attacks are out of scope when it is convenient 
to say that.  Section 17.4 discusses about mechanisms to mitigate 
these attacks.

I read the appendices quickly.  Appendix A.1 explains why S/MIME is 
bad.  Appendix B explains how SMTP works.  Appendix C proposes a XML 
Schema and descriptions of
PolicyOverrideTypes.

Regards,
S. Moonesamy


From nobody Tue Apr 22 12:32:08 2014
Return-Path: <martin.thomson@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 621DC1A010B for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 12:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 hbj52BDL_Ai2 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 12:32:06 -0700 (PDT)
Received: from mail-wg0-x232.google.com (mail-wg0-x232.google.com [IPv6:2a00:1450:400c:c00::232]) by ietfa.amsl.com (Postfix) with ESMTP id 0F47D1A003D for <ietf@ietf.org>; Tue, 22 Apr 2014 12:32:05 -0700 (PDT)
Received: by mail-wg0-f50.google.com with SMTP id x13so4303294wgg.21 for <ietf@ietf.org>; Tue, 22 Apr 2014 12:32:00 -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:content-type; bh=NfcIusWTsp+v5ip8akioWi0J4PcvLD3xEabS1s8U9jw=; b=kReXLEHeHhp9lLtc0MK8sE2u/dIAeWJETJNj3O7d+UInjXVbGmqgFBGef74Fu1lcg5 NJoIm5gWzlCszo8ejBDkvsgVLVrCJz5b6RyWCMN04W0mT3wO0jKy2cTdlSpYSf4yI5W2 koYbTlqaxWhCTY1EqBb4s4CP5kWxN3rBiQ00HULYhjOjNIwgj6dvMzcx35WkUBMjjklA 8/hiC6jlP830gNsw2Gyi6KOu6jWvj89J1fFUwNtsl5zaPov/Z0uEq+rOynuFZRXjtkbw lgOEnzCuaASyetjT4IqlKXxuwjmH2Dp9ar4ekwz5B5UZJcO7xK7+Zbd+nuC6z+gDln1i oRPQ==
MIME-Version: 1.0
X-Received: by 10.194.94.39 with SMTP id cz7mr220939wjb.78.1398195120084; Tue, 22 Apr 2014 12:32:00 -0700 (PDT)
Received: by 10.227.144.132 with HTTP; Tue, 22 Apr 2014 12:32:00 -0700 (PDT)
In-Reply-To: <tsloazuxlxm.fsf@mit.edu>
References: <tsloazuxlxm.fsf@mit.edu>
Date: Tue, 22 Apr 2014 12:32:00 -0700
Message-ID: <CABkgnnUk1TLPZk0T3v2CzwQX2xa8W49iK9gs66tpCJ8qSjzrxA@mail.gmail.com>
Subject: Re: Thanks for improved editing function over at the rfc-editor
From: Martin Thomson <martin.thomson@gmail.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vMoOMgeR7CpFefIyqgau9Lrn_T4
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 19:32:07 -0000

On 21 April 2014 17:11, Sam Hartman <hartmans-ietf@mit.edu> wrote:
> I see fewer documents these days, but I do see enough documents that I
> have confidence in my claim that the auth48 process seems to be much
> smoother than it used to be.

I can second that.

I recently had a (minor) technical error caught by the editor;
something I and the working group missed in several reviews.  I don't
know about improvement - I haven't seen any mistakes personally - but
the editor team is definitely doing a great job.


From nobody Tue Apr 22 14:02:11 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC791A026B for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 14:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.401
X-Spam-Level: *
X-Spam-Status: No, score=1.401 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, J_CHICKENPOX_16=0.6] autolearn=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 5ATnpdjjgOqC for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 14:02:04 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.41]) by ietfa.amsl.com (Postfix) with ESMTP id D03851A0226 for <ietf@ietf.org>; Tue, 22 Apr 2014 14:01:58 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES531.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Tue, 22 Apr 2014 17:01:52 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Don't shoot the messenger... AOL is publishing DMARC p=reject as of today.
Thread-Topic: Don't shoot the messenger... AOL is publishing DMARC p=reject as of today.
Thread-Index: Ac9ebhT/nqzghZMeQpedheyzgjO2Zg==
Date: Tue, 22 Apr 2014 21:01:51 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D521D3@USCLES544.agna.amgreetings.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.221]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_CE39F90A45FF0C49A1EA229FC9899B0507D521D3USCLES544agnaam_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qd2zL7hv5EIslOYSSLWl7WfTmdY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 21:02:09 -0000

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D521D3USCLES544agnaam_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As I had indicated in a previous post, I expected that AOL might follow Yah=
oo in publishing p=3Dreject as a means of mitigating a specific type of abu=
se they were experiencing.

http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-=
reject/

Mike

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D521D3USCLES544agnaam_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">As I had indicated in a previous post, I expected th=
at AOL might follow Yahoo in publishing p=3Dreject as a means of mitigating=
 a specific type of abuse they were experiencing.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><a href=3D"http://postmaster-blog.aol.com/2014/04/22=
/aol-mail-updates-dmarc-policy-to-reject/">http://postmaster-blog.aol.com/2=
014/04/22/aol-mail-updates-dmarc-policy-to-reject/</a><o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Mike<o:p></o:p></p>
</div>
</body>
</html>

--_000_CE39F90A45FF0C49A1EA229FC9899B0507D521D3USCLES544agnaam_--


From nobody Tue Apr 22 15:04:38 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24E711A0283 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 15:04:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.943
X-Spam-Level: **
X-Spam-Status: No, score=2.943 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_16=0.6, SPF_NEUTRAL=0.779] autolearn=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 OUF5K5b0vPuZ for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 15:04:31 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 409AA1A0278 for <ietf@ietf.org>; Tue, 22 Apr 2014 15:04:31 -0700 (PDT)
Received: (qmail 38684 invoked from network); 22 Apr 2014 22:04:25 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 22 Apr 2014 22:04:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=125d9.5356e768.k1404; i=johnl@user.iecc.com; bh=zFWkx1Y7bcDkA8V3QMZG2gx+jpJT1jVswVcSyIM3KWo=; b=FKb7pgqu5pLapGfcpAHXTJFj9O4BIYAdQF317Yg+D4pFAA5Ss8lLAdJLeO7a7kttaIasbpps4a62AErry+DMNcXY3IjhdQe/ZmDs+m0e8gPlpQB0q96zzfVb9rqhFQhhP/7jEW6ZObP7RMLpz6gFW7Px8BsCKK0aa8zsPnxDFpCOLHEu6feRj2oAtjbvVp0RREgHT+4in3NlPvVTxWcTFBcYOzwXRh0k8l1t1QgAVK1ZQR/sg9ByiRogXNmF+xyv
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=125d9.5356e768.k1404; olt=johnl@user.iecc.com; bh=zFWkx1Y7bcDkA8V3QMZG2gx+jpJT1jVswVcSyIM3KWo=; b=WaQvmqTsaAagvwB8sJs9hU+JeqfIMmKG3uKheKh1j9zXTyx3bzT3RfVYZLwAk19HSMyKRq8wnTboY9eU1+0lZ/tXRa7v/ASwGv1XTm4B3Ea5AeukYR1Vz9l/AeqEVduE1qQKrh7Ur9QT0X9Pj61h1JCeqDAljI1dBBQocFiQNvCsbBpmfVv7e81I9BbfrbIaprhWT5yzbmRB7BILmJnyxNqrOfdHf/sfvhAoAUYWDbLaEbd9i4ZMnbkeE0F2JpLw
Date: 22 Apr 2014 22:04:02 -0000
Message-ID: <20140422220402.75224.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Don't shoot the messenger... AOL is publishing DMARC p=reject as of today.
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D521D3@USCLES544.agna.amgreetings.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/29hy-iXy2j5egAAJHT7ggNXZkyc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 22:04:36 -0000

>As I had indicated in a previous post, I expected that AOL might follow Yahoo in publishing p=reject as a means of mitigating a
>specific type of abuse they were experiencing.
>
>http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-policy-to-reject/

This certainly confirms the theory that the members of the DMARC
cartel believe that they have sufficient market power to force
everyone else to bear the costs of the collateral damage of their
poorly targeted anti-abuse efforts.  Who knows, they might even be
right.  

In AOL's case, I presume it's because it's become painfully apparent
that crooks are stealing vast numbers of AOL address books and
spamming to them from the matching AOL user addresses. This is loudly
slamming the barn door after the horse left.  Too bad for all the
people whose feet were crushed as they did so.

R's,
John


From nobody Tue Apr 22 15:50:54 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1FE41A0289 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 15:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.026
X-Spam-Level: *
X-Spam-Status: No, score=1.026 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 i5FNUiQQsfl7 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 15:50:45 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id A34E91A0039 for <ietf@ietf.org>; Tue, 22 Apr 2014 15:50:45 -0700 (PDT)
Received: from [192.168.2.25] (adsl-99-17-30-3.dsl.lsan03.sbcglobal.net [99.17.30.3]) by dougbarton.us (Postfix) with ESMTPSA id 1BEFB22B20 for <ietf@ietf.org>; Tue, 22 Apr 2014 22:50:40 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1398207040; bh=WLqSFcs9hVOy/sgHaNOnb1M/xqC4n4rCiyaC1FUhkAA=; h=Date:From:To:Subject:References:In-Reply-To; b=TR78CQSqrNKUX1YJasgcPIdRYHmLuAn8lxCJmV0j5a+fxuhLsOZHgz2npxsNo3r1c ZoTeM5zTRjh4F50iBswOhZ5nhfBx9QrD3yAEXraZEogg16XBLsQG/MbnIcRX0zrT4/ lzhMeKtd82esiKlEWPMDL0YC0z6BvboM/8gFkU/4=
Message-ID: <5356F23F.40909@dougbarton.us>
Date: Tue, 22 Apr 2014 15:50:39 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com>
In-Reply-To: <01P6STS0F6I600004X@mauve.mrochek.com>
X-Enigmail-Version: 1.7a1pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/P08buUexppnyTV6cUBriI_Bv9iE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 22:50:49 -0000

On 04/18/2014 05:33 PM, Ned Freed wrote:
>> On 04/18/2014 07:47 AM, Ned Freed wrote:
>>>> I said: Rather than throwing up our hands and telling the DMARC
>>>> folks that we refuse to work with them unless their solution
>>>> solves the problem of our anachronistic use case that that
>>>> constitutes only a tiny percentage of their overall traffic;
>>>
>>> Again with the traffic size as justification for poor behavior.
>>> Not all messages are created equal, and some functions have
>>> utility entirely disproportionate to the amount of bandwidth they
>>> use.
>
>> Right, so the input here from the operators is, "Mailing list
>> traffic is not important enough to us to prevent us from deploying
>> an anti-spam solution that solves the vast majority of our problems
>> with little cost or difficulty. The MLM software authors will have
>> to deal with this problem on their end." And your response is to
>> stamp your feet and shout, "But my mailing list traffic IS
>> important! It is, IT IS!!!!!"
>
> I really have to wonder where you got enough straw to build a
> strawman of this size. If you actually, you know, read what I've been
> saying, it has been that this was handled extremely poorly by the
> IETF. Just not in the way you happen to believe.
>
> Your view of what happened, who the operators actually are and what
> their positions are, and what the likely consequences are going to be
> are somewhere between a gross oversimplifications and looney tunes.
> But I must say they are amusing.

First, I acknowledge that you seem to be interested in addressing the 
IETF's failings, the problem is that small matter of disagreement on 
what those failings are. You say that my version of events is "looney 
tunes," and yet there is "rough consensus and running code" backing it 
up. Even before AOL joined the p=reject team, but much more so now.

It's incredibly obvious that the IETF either didn't listen to, or didn't 
act on clear messages from the operator community on this topic. Trying 
to re-paint the failure as one of process (or whatever weird rathole you 
appear to be willing to travel) doesn't help the situation at all.

For this issue what would help is for the IETF to admit its failure, and 
take in hand the problem of solving mailing list delivery for DMARC 
protected domains (along with the MLM software authors of course). If 
there are other places where DMARC has weaknesses that can be shored up, 
let's tackle those too.

What won't help is sitting on the sidelines and whinging that the "DMARC 
cabal" "doesn't get it" and has to listen to us about how it should 
conduct their business. Because not only do they clearly not have to do 
that, they are not doing it. You will see more and more large mail 
providers implementing p=reject because it's good for them, and the 
fallout from Yahoo!'s implementation has been marginal (from their 
perspective).

 From a larger perspective it would be very useful for the IETF to take 
this message to heart in other areas, like say ... DHCPv6. But I digress. :)

> Wrong again. The evidence shows clearly that the IETF did listen, to
>  this group at least. Where the IETF failed was in not looking at the
> big picture and likely consequences, which I'm afraid is not laid out
> along the axis of "big operators all supporting DMARC" versus "tiny
> insignificant list maintainer stick-in-the-muds".

I'm not sure who you're defining as "the IETF" in this context, but the 
record seems to show that there was a non-zero number of people telling 
the DMARC folks that their spec should not be implemented because it 
doesn't solve the mailing list problem, among others. So rather than 
listening to the operators and working to solve the MLM problem, there 
was whinging, and intransigence. I don't care how you want to 
characterize the problem, the failures of communication and inaction are 
pretty clear.

Doug


From nobody Tue Apr 22 16:56:08 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EE791A0296 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 16:56:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.652
X-Spam-Level: 
X-Spam-Status: No, score=-2.652 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_EQ_DE=0.35, J_CHICKENPOX_16=0.6, J_CHICKENPOX_54=0.6, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 iJwrEtsEsE5q for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 16:56:04 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id 5F2A71A0283 for <ietf@ietf.org>; Tue, 22 Apr 2014 16:56:04 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s3MNtvbI027954 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 23 Apr 2014 01:55:57 +0200 (MEST)
Subject: Re: Don't shoot the messenger... AOL is publishing DMARC p=reject as of today.
In-Reply-To: <20140422220402.75224.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
Date: Wed, 23 Apr 2014 01:55:57 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140422235557.3CE511ACDC@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wdfO8AseiXRWM2Lx6NUIN8D4b0o
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 23:56:06 -0000

John Levine wrote:
> 
> In AOL's case, I presume it's because it's become painfully apparent
> that crooks are stealing vast numbers of AOL address books and
> spamming to them from the matching AOL user addresses. This is loudly
> slamming the barn door after the horse left.  Too bad for all the
> people whose feet were crushed as they did so.

I received spam EMail from a friend with @yahoo.com account on 26-Mar-2014
based on what appears to be a stolen address book.

It did not come through any yahoo mail servers, carried 19 additional 
email addresses from my friends address book in Cc: and contained an
URL to some aggressive advertisement site besides the first+last real name
of my friend (subject was also only my friends first+last name).

I don't know whether that site also served any malware along with the
aggressive advertisement, I opened it in a virtual environment with
a browser having active content disabled.  The advertisement was
shown in my local language (German) although I was the only German
among the visible recipients.


Btw. I can successfully send myself EMail with fake @yahoo.com in From:
to my work Email account (where I originally received that spam),
and there is no problem in receiving. (Our comany email does not seem
to perform any of the crazy DMARC processing).


-Martin


From nobody Tue Apr 22 17:31:11 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED6281A02B9 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 17:31:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 TZi8ngXMeomv for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 17:31:09 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id BD66E1A02AE for <ietf@ietf.org>; Tue, 22 Apr 2014 17:31:08 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s3N0UkS6018771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 23 Apr 2014 02:30:46 +0200 (MEST)
Subject: Re: Review of draft-kucherawy-dmarc-base-04
In-Reply-To: <6.2.5.6.2.20140422074852.0d368728@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Date: Wed, 23 Apr 2014 02:30:45 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_C23rWNA2DtzMfSjmVGFr8XOrms
Cc: ietf@ietf.org, Nevil Brownlee <rfc-ise@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 00:31:10 -0000

S Moonesamy wrote:
> 
> In Section 8:
> 
>    "If the RFC5322.From domain does not exist in the DNS, Mail Receivers
>     SHOULD direct the receiving SMTP server to reject the message."
> 
> Why is there such a recommendation?  What is a mail receiver?  I am 
> asking the question as there is "receiving SMTP server" in that sentence.

That would be silly.  RFC5322.From might contain no DNS domain to begin with.


> 
> In Section 10.1:
> 
>    "Have no RFC5322.From field (which is also forbidden under RFC 5322
>     [MAIL])"
> 
> Where is it stated in RFC 5322 that it is forbidden?  That RFC 
> specifies a syntax for the Internet Message Format.

Some MTAs (sendmail?) seem to recreate an RFC5322.From from the Envelope,
in case that it is missing in the message.

-Martin


From nobody Tue Apr 22 19:33:28 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 131981A02EC for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 19:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 IOXuuBYNrrrX for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 19:33:26 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 06BA31A02D6 for <ietf@ietf.org>; Tue, 22 Apr 2014 19:33:26 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6YID25S4G0003FF@mauve.mrochek.com> for ietf@ietf.org; Tue, 22 Apr 2014 19:28:18 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WZAZ2YYO000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 22 Apr 2014 19:28:13 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6YID0EMJ2000052@mauve.mrochek.com>
Date: Tue, 22 Apr 2014 19:14:10 -0700 (PDT)
Subject: Re: Review of draft-kucherawy-dmarc-base-04
In-reply-to: "Your message dated Wed, 23 Apr 2014 02:30:45 +0200 (CEST)" <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp>
References: <6.2.5.6.2.20140422074852.0d368728@elandnews.com> <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp>
To: mrex@sap.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AZ9F5YxA281toZkF4x1CuCrVfKo
Cc: S Moonesamy <sm+ietf@elandsys.com>, Nevil Brownlee <rfc-ise@rfc-editor.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 02:33:27 -0000

Do we really want to be discussing changes to this draft on the main 
IETF list?

> S Moonesamy wrote:
> >
> > In Section 8:
> >
> >    "If the RFC5322.From domain does not exist in the DNS, Mail Receivers
> >     SHOULD direct the receiving SMTP server to reject the message."
> >
> > Why is there such a recommendation?  What is a mail receiver?  I am
> > asking the question as there is "receiving SMTP server" in that sentence.

> That would be silly.  RFC5322.From might contain no DNS domain to begin with.

It has to contain a domain. If it doesn't it's syntactically invalid. Here's
the relevant ABNF:

 from            =   "From:" mailbox-list CRLF
 mailbox-list    =   (mailbox *("," mailbox)) / obs-mbox-list
 obs-mbox-list   =   *([CFWS] ",") mailbox *("," [mailbox / CFWS])
 mailbox         =   name-addr / addr-spec
 name-addr       =   [display-name] angle-addr
 angle-addr      =   [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr
 obs-angle-addr  =   [CFWS] "<" obs-route addr-spec ">" [CFWS]
 addr-spec       =   local-part "@" domain

There's no way through that doesn't include at least one addr-space, which in
turn contains a domain.

> >
> > In Section 10.1:
> >
> >    "Have no RFC5322.From field (which is also forbidden under RFC 5322
> >     [MAIL])"
> >
> > Where is it stated in RFC 5322 that it is forbidden?  That RFC
> > specifies a syntax for the Internet Message Format.

See the table in section 3.6. It says that the minimum number of from fields
in the header is 1.

> Some MTAs (sendmail?) seem to recreate an RFC5322.From from the Envelope,
> in case that it is missing in the message.

Indeed they do. It's a reasonable action to take on message submission.
Relay is more ... interesting.

				Ned


From nobody Tue Apr 22 20:03:24 2014
Return-Path: <mitch@telmate.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3CF241A0009 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 20:03:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham
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 X_zyjQnoFnal for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 20:03:14 -0700 (PDT)
Received: from mail-oa0-f45.google.com (mail-oa0-f45.google.com [209.85.219.45]) by ietfa.amsl.com (Postfix) with ESMTP id 049D41A0007 for <ietf@ietf.org>; Tue, 22 Apr 2014 20:03:13 -0700 (PDT)
Received: by mail-oa0-f45.google.com with SMTP id eb12so389680oac.4 for <ietf@ietf.org>; Tue, 22 Apr 2014 20:03:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:content-transfer-encoding:from :mime-version:subject:date:message-id:references:cc:in-reply-to:to; bh=gwlf4u4dHZjz1oNBrkU6pBZNtcrrwa3Icwk78ouodSw=; b=hodBcJCf04XNsQ2RByt4R+h7kS6krQHYK9EF7IYl81lCBDPuNsjIDP4iYzD7rRJF8F YSBkOzm3QLT2YosykrJGfoubKHsXS+sAWSAv3Ir8KvPYrIudJvBbGOIbHLtTglLSl7FR pPUJz4F2lBUnU8SalxkbTvGJb5dJzqMhQ6v607xRMTuDoFwX5T53kTBsdmOYoUoJPWVD bpPVHtiuAgLWqHk8XmCUXCRB1udWERRlIL7xpUl3OoUY9z+lrr2Y4sRX9xRfEowRhO1I Hdw6g5ybYF4Q+lRrF4blEPxdgMkOyXeVDS0SlOCjT2TB6nccHv5gQNLODmmArl/S6sJ+ Fcig==
X-Gm-Message-State: ALoCoQkVlyiWevgkHC9Wv8v9QyYfRTX91+BSfBw4sWU4wofFTW7pHXR3Ec3DxBcbmbbTLJ9t0ro6
X-Received: by 10.60.62.178 with SMTP id z18mr48611oer.61.1398222188400; Tue, 22 Apr 2014 20:03:08 -0700 (PDT)
Received: from [51.219.160.77] (66-87-118-77.pools.spcsdns.net. [66.87.118.77]) by mx.google.com with ESMTPSA id y10sm80506177obk.4.2014.04.22.20.03.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 22 Apr 2014 20:03:07 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-2C19AE88-4B8B-421A-9837-9B7FA06E2FE2
Content-Transfer-Encoding: 7bit
From: Mitch Rodrigues <mitch@telmate.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Review of draft-kucherawy-dmarc-base-04
Date: Tue, 22 Apr 2014 20:02:59 -0700
Message-Id: <D52EE5A7-CCCA-4579-BF49-950F259CE6D6@telmate.com>
References: <6.2.5.6.2.20140422074852.0d368728@elandnews.com> <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp> <01P6YID0EMJ2000052@mauve.mrochek.com>
In-Reply-To: <01P6YID0EMJ2000052@mauve.mrochek.com>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
X-Mailer: iPhone Mail (11D167)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PgUULJR3P6dSo-Gkg82m1D_-6LY
Cc: S Moonesamy <sm+ietf@elandsys.com>, Nevil Brownlee <rfc-ise@rfc-editor.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 03:03:20 -0000

--Apple-Mail-2C19AE88-4B8B-421A-9837-9B7FA06E2FE2
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable


I don't see why we wouldn't, discussions regarding this draft have been goin=
g for quite some time. Might as well get community support regarding this, p=
lus if nothing else it's fairly interesting subject.


Mitch Rodrigues / Software Engineer
Telmate
655 Montgomery Street, 18th Floor
San Francisco, CA 94111
Email =20
Office www.Telmate.com |www.GettingOut.com | GettingOut Facebook




> On Apr 22, 2014, at 7:14 PM, ned+ietf@mauve.mrochek.com wrote:
>=20
> Do we really want to be discussing changes to this draft on the main=20
> IETF list?
>=20
>> S Moonesamy wrote:
>>>=20
>>> In Section 8:
>>>=20
>>>   "If the RFC5322.=46rom domain does not exist in the DNS, Mail Receiver=
s
>>>    SHOULD direct the receiving SMTP server to reject the message."
>>>=20
>>> Why is there such a recommendation?  What is a mail receiver?  I am
>>> asking the question as there is "receiving SMTP server" in that sentence=
.
>=20
>> That would be silly.  RFC5322.=46rom might contain no DNS domain to begin=
 with.
>=20
> It has to contain a domain. If it doesn't it's syntactically invalid. Here=
's
> the relevant ABNF:
>=20
> from            =3D   "From:" mailbox-list CRLF
> mailbox-list    =3D   (mailbox *("," mailbox)) / obs-mbox-list
> obs-mbox-list   =3D   *([CFWS] ",") mailbox *("," [mailbox / CFWS])
> mailbox         =3D   name-addr / addr-spec
> name-addr       =3D   [display-name] angle-addr
> angle-addr      =3D   [CFWS] "<" addr-spec ">" [CFWS] / obs-angle-addr
> obs-angle-addr  =3D   [CFWS] "<" obs-route addr-spec ">" [CFWS]
> addr-spec       =3D   local-part "@" domain
>=20
> There's no way through that doesn't include at least one addr-space, which=
 in
> turn contains a domain.
>=20
>>>=20
>>> In Section 10.1:
>>>=20
>>>   "Have no RFC5322.=46rom field (which is also forbidden under RFC 5322
>>>    [MAIL])"
>>>=20
>>> Where is it stated in RFC 5322 that it is forbidden?  That RFC
>>> specifies a syntax for the Internet Message Format.
>=20
> See the table in section 3.6. It says that the minimum number of from fiel=
ds
> in the header is 1.
>=20
>> Some MTAs (sendmail?) seem to recreate an RFC5322.=46rom from the Envelop=
e,
>> in case that it is missing in the message.
>=20
> Indeed they do. It's a reasonable action to take on message submission.
> Relay is more ... interesting.
>=20
>                Ned
>=20

--Apple-Mail-2C19AE88-4B8B-421A-9837-9B7FA06E2FE2
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div style=3D"-webkit-text-size-adjust: aut=
o;"><br></div><div style=3D"-webkit-text-size-adjust: auto;">I don't see why=
 we wouldn't, discussions regarding this draft have been going for quite som=
e time. Might as well get community support regarding this, plus if nothing e=
lse it's fairly interesting subject.</div><div style=3D"-webkit-text-size-ad=
just: auto;"><br></div><div style=3D"-webkit-text-size-adjust: auto;"><br></=
div><div><div id=3D"preview" style=3D"box-sizing: border-box; margin: 0px; p=
adding: 0px; border: 0px rgb(225, 225, 225); vertical-align: baseline;"><spa=
n style=3D"-webkit-text-size-adjust: auto; background-color: rgba(255, 255, 2=
55, 0);"><font style=3D"box-sizing: border-box; text-align: -webkit-auto;"><=
big style=3D"box-sizing: border-box; margin: 0px; padding: 0px; border: 0px r=
gb(225, 225, 225); font-style: inherit; font-variant: inherit; vertical-alig=
n: baseline;"><b style=3D"box-sizing: border-box; margin: 0px; padding: 0px;=
 border: 0px rgb(225, 225, 225); font-style: inherit; font-variant: inherit;=
 vertical-align: baseline;">Mitch Rodrigues / Software Engineer</b></big><br=
 style=3D"box-sizing: border-box;"></font><font style=3D"box-sizing: border-=
box; text-align: -webkit-auto;"><big style=3D"box-sizing: border-box; margin=
: 0px; padding: 0px; border: 0px rgb(225, 225, 225); font-style: inherit; fo=
nt-variant: inherit; vertical-align: baseline;"><font style=3D"box-sizing: b=
order-box;"><b style=3D"box-sizing: border-box; margin: 0px; padding: 0px; b=
order: 0px rgb(225, 225, 225); font-style: inherit; font-variant: inherit; v=
ertical-align: baseline;">Telmate</b></font></big><br style=3D"box-sizing: b=
order-box;">655 Montgomery Street, 18th Floor<br style=3D"box-sizing: border=
-box;">San Francisco, CA 94111<br style=3D"box-sizing: border-box;">Email<sp=
an style=3D"box-sizing: border-box; margin: 0px; padding: 0px; border: 0px r=
gb(225, 225, 225); font-style: inherit; font-variant: inherit; vertical-alig=
n: baseline;">&nbsp;</span><a href=3D"mailto:" style=3D"box-sizing: border-b=
ox; margin: 0px; padding: 0px; border: 0px rgb(225, 225, 225); font-style: i=
nherit; font-variant: inherit; vertical-align: baseline; outline: 0px; max-w=
idth: 100%;">&nbsp;</a><br style=3D"box-sizing: border-box;">Office<span sty=
le=3D"box-sizing: border-box; margin: 0px; padding: 0px; border: 0px rgb(225=
, 225, 225); font-style: inherit; font-variant: inherit; vertical-align: bas=
eline;">&nbsp;</span><a href=3D"tel:" value=3D"+" target=3D"_blank" style=3D=
"box-sizing: border-box; margin: 0px; padding: 0px; border: 0px rgb(225, 225=
, 225); font-style: inherit; font-variant: inherit; vertical-align: baseline=
; outline: 0px; max-width: 100%;"></a><a href=3D"http://www.telmate.com/" st=
yle=3D"box-sizing: border-box; margin: 0px; padding: 0px; border: 0px rgb(22=
5, 225, 225); font-style: inherit; font-variant: inherit; vertical-align: ba=
seline; outline: 0px; max-width: 100%;">www.Telmate.com</a>&nbsp;|<a href=3D=
"http://www.gettingout.com/" style=3D"box-sizing: border-box; margin: 0px; p=
adding: 0px; border: 0px rgb(225, 225, 225); font-style: inherit; font-varia=
nt: inherit; vertical-align: baseline; outline: 0px; max-width: 100%;">www.G=
ettingOut.com</a>&nbsp;|&nbsp;<a href=3D"https://www.facebook.com/pages/Gett=
ingout/494201843984720" style=3D"box-sizing: border-box; margin: 0px; paddin=
g: 0px; border: 0px rgb(225, 225, 225); font-style: inherit; font-variant: i=
nherit; vertical-align: baseline; outline: 0px; max-width: 100%;">GettingOut=
 Facebook</a></font><font style=3D"box-sizing: border-box; text-align: -webk=
it-auto;"><br clear=3D"all" style=3D"box-sizing: border-box;"><br clear=3D"a=
ll" style=3D"box-sizing: border-box;"></font><a href=3D"http://www.telmate.c=
om/" style=3D"box-sizing: border-box; margin: 0px; padding: 0px; border: 0px=
 rgb(225, 225, 225); font-style: inherit; font-variant: inherit; vertical-al=
ign: baseline; outline: 0px; max-width: 100%;"><img src=3D"http://www.telmat=
e.com/media/images/logos/telmate_100x25.png" width=3D"100" height=3D"25" alt=
=3D"Telmate" border=3D"0" style=3D"box-sizing: border-box; margin: 0px; padd=
ing: 0px; border: none rgb(225, 225, 225); font-style: inherit; font-variant=
: inherit; vertical-align: baseline; display: inline-block; max-width: 100%;=
 height: auto; image-rendering: optimizequality;"></a></span></div><div id=3D=
"preview" style=3D"box-sizing: border-box; margin: 0px; padding: 0px; border=
: 0px rgb(225, 225, 225); vertical-align: baseline;"><br></div><div id=3D"pr=
eview" style=3D"box-sizing: border-box; margin: 0px; padding: 0px; border: 0=
px rgb(225, 225, 225); vertical-align: baseline;"><br></div>On Apr 22, 2014,=
 at 7:14 PM, <a href=3D"mailto:ned+ietf@mauve.mrochek.com">ned+ietf@mauve.mr=
ochek.com</a> wrote:<br><br></div><blockquote type=3D"cite" style=3D"-webkit=
-text-size-adjust: auto;"><div><span>Do we really want to be discussing chan=
ges to this draft on the main </span><br><span>IETF list?</span><br><span></=
span><br><blockquote type=3D"cite"><span>S Moonesamy wrote:</span><br></bloc=
kquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></span><br>=
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite=
"><span>In Section 8:</span><br></blockquote></blockquote><blockquote type=3D=
"cite"><blockquote type=3D"cite"><span></span><br></blockquote></blockquote>=
<blockquote type=3D"cite"><blockquote type=3D"cite"><span> &nbsp;&nbsp;"If t=
he RFC5322.=46rom domain does not exist in the DNS, Mail Receivers</span><br=
></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cit=
e"><span> &nbsp;&nbsp;&nbsp;SHOULD direct the receiving SMTP server to rejec=
t the message."</span><br></blockquote></blockquote><blockquote type=3D"cite=
"><blockquote type=3D"cite"><span></span><br></blockquote></blockquote><bloc=
kquote type=3D"cite"><blockquote type=3D"cite"><span>Why is there such a rec=
ommendation? &nbsp;What is a mail receiver? &nbsp;I am</span><br></blockquot=
e></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>ask=
ing the question as there is "receiving SMTP server" in that sentence.</span=
><br></blockquote></blockquote><span></span><br><blockquote type=3D"cite"><s=
pan>That would be silly. &nbsp;RFC5322.=46rom might contain no DNS domain to=
 begin with.</span><br></blockquote><span></span><br><span>It has to contain=
 a domain. If it doesn't it's syntactically invalid. Here's</span><br><span>=
the relevant ABNF:</span><br><span></span><br><span> from &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D &nbsp;&nbsp;"From:" mail=
box-list CRLF</span><br><span> mailbox-list &nbsp;&nbsp;&nbsp;=3D &nbsp;&nbs=
p;(mailbox *("," mailbox)) / obs-mbox-list</span><br><span> obs-mbox-list &n=
bsp;&nbsp;=3D &nbsp;&nbsp;*([CFWS] ",") mailbox *("," [mailbox / CFWS])</spa=
n><br><span> mailbox &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D &nb=
sp;&nbsp;name-addr / addr-spec</span><br><span> name-addr &nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;=3D &nbsp;&nbsp;[display-name] angle-addr</span><br><span>=
 angle-addr &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D &nbsp;&nbsp;[CFWS] "&lt;" addr=
-spec "&gt;" [CFWS] / obs-angle-addr</span><br><span> obs-angle-addr &nbsp;=3D=
 &nbsp;&nbsp;[CFWS] "&lt;" obs-route addr-spec "&gt;" [CFWS]</span><br><span=
> addr-spec &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=3D &nbsp;&nbsp;local-part "=
@" domain</span><br><span></span><br><span>There's no way through that doesn=
't include at least one addr-space, which in</span><br><span>turn contains a=
 domain.</span><br><span></span><br><blockquote type=3D"cite"><blockquote ty=
pe=3D"cite"><span></span><br></blockquote></blockquote><blockquote type=3D"c=
ite"><blockquote type=3D"cite"><span>In Section 10.1:</span><br></blockquote=
></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span></sp=
an><br></blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D=
"cite"><span> &nbsp;&nbsp;"Have no RFC5322.=46rom field (which is also forbi=
dden under RFC 5322</span><br></blockquote></blockquote><blockquote type=3D"=
cite"><blockquote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;[MAIL])"</span><br>=
</blockquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite=
"><span></span><br></blockquote></blockquote><blockquote type=3D"cite"><bloc=
kquote type=3D"cite"><span>Where is it stated in RFC 5322 that it is forbidd=
en? &nbsp;That RFC</span><br></blockquote></blockquote><blockquote type=3D"c=
ite"><blockquote type=3D"cite"><span>specifies a syntax for the Internet Mes=
sage Format.</span><br></blockquote></blockquote><span></span><br><span>See t=
he table in section 3.6. It says that the minimum number of from fields</spa=
n><br><span>in the header is 1.</span><br><span></span><br><blockquote type=3D=
"cite"><span>Some MTAs (sendmail?) seem to recreate an RFC5322.=46rom from t=
he Envelope,</span><br></blockquote><blockquote type=3D"cite"><span>in case t=
hat it is missing in the message.</span><br></blockquote><span></span><br><s=
pan>Indeed they do. It's a reasonable action to take on message submission.<=
/span><br><span>Relay is more ... interesting.</span><br><span></span><br><s=
pan> &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;Ned</span><br><s=
pan></span><br></div></blockquote></body></html>=

--Apple-Mail-2C19AE88-4B8B-421A-9837-9B7FA06E2FE2--


From nobody Tue Apr 22 20:16:01 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC3271A0012 for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 20:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Noqg6dHwQ1NU for <ietf@ietfa.amsl.com>; Tue, 22 Apr 2014 20:15:52 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2E7DB1A000C for <ietf@ietf.org>; Tue, 22 Apr 2014 20:15:52 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6YJTR7P400003IB@mauve.mrochek.com> for ietf@ietf.org; Tue, 22 Apr 2014 20:10:46 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WZAZ2YYO000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 22 Apr 2014 20:10:42 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6YJTPN8MO000052@mauve.mrochek.com>
Date: Tue, 22 Apr 2014 19:53:37 -0700 (PDT)
Subject: Re: Internet Technology Adoption and Transition
In-reply-to: "Your message dated Thu, 17 Apr 2014 23:11:31 -0700" <6.2.5.6.2.20140417215305.0dc8c008@resistor.net>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org> <6.2.5.6.2.20140417215305.0dc8c008@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Vbd7A0n_SokAEMqX6t2XRwAd-3Y
Cc: iab@iab.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 03:15:57 -0000

> Hello,
> At 19:11 17-04-2014, IAB Chair wrote:
> >This is a call for review of "Report from the IAB workshop on
> >Internet Technology Adoption and Transition (ITAT)" prior to
> >potential approval as an IAB stream RFC.
> >
> >The document is available for inspection here:
> >https://datatracker.ietf.org/doc/draft-iab-itat-report-/

> I read the report.  Section 2 mentions that SMTP and IMAP in the
> applications space have continued to evolve.  I have not see much
> evolution in the SMTP space.  I'll leave the relevant people to
> comment about IMAP.  As a nit, the reference for IPv6 is incorrect.

I'm not sure what the report means by "evolve", but by any reasonable
definition, I believe SMTP continues to evolve.

If you're talking about standards work, the IESG just approved the RRVS
document which specifies a new SMTP extension. In recent times we've approved
other extensions such as MT-PRIORITY. And let's not forget about EAI, which is
a pretty major evolution of the protocol.

And this process continues. I rather expect we'll see changes in the 
STARTTLS space in the not too distant future.

If you're talking about implementations, the first thing to note is that
given the relatively small number of implementations in wide use, a change
to even one or two of them is significant. And while progess is slow,
it's pretty constant from my perspective.

As for actual deployment, things are even more skewed, which makes them
difficult to measure. For example, if a major wireless vendor implements the
BINARY extension in both their client and their own server, that can affect a
huge swath of traffic without any need for anyone else to change.

The deployment of older extensions also changes over time, and it doesn't
always increase. I'm fairly sure I'm seeing more of ENHANCEDSTATUSCODES but
less of NOTARY. (And yeah, I know given the relationship between the two that's
wierd. I'm just reporing what I've observed.)

Moreover, there can be evolutionary changes having nothing to do with
extensions per se. For example, it seems that not only is use of STARTTLS on
the rise, what cipher suites are enabled seems to be changing, probably because
a lot of sites are actually paying attention to such details when prior to the
Snoden thing they care.

				Ned


From nobody Wed Apr 23 00:24:49 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 068411A00B5 for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 00:24:47 -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, SPF_PASS=-0.001] autolearn=ham
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 joFAUWATjzsx for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 00:24:42 -0700 (PDT)
Received: from mail-wi0-x22f.google.com (mail-wi0-x22f.google.com [IPv6:2a00:1450:400c:c05::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 0F8B81A0055 for <ietf@ietf.org>; Wed, 23 Apr 2014 00:24:41 -0700 (PDT)
Received: by mail-wi0-f175.google.com with SMTP id cc10so4419572wib.2 for <ietf@ietf.org>; Wed, 23 Apr 2014 00:24:36 -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:content-type; bh=O5F9tuJk7Rqv1UinvW01+vrgEh6/dMZfslldxsXNqRE=; b=hIHkB861oim+jlmvCbTgc6Bw/NEmGOZrL9ZSkO+u8A0LKg3W+sxAWHfb1Nj7IjFMRC OG36VRmLQfgUR/kOAtst5QSlCGkq2dC8npQKnnSpm2nxS6ggQuq2a+OoedJzDpjWWcUM tjQGKHotpNWOgZrXYHKfzuLj2BCkAt/TWeUYbv7QzziG55w5RDEs5CN7DFiCBFewjKw7 SfPlg8d1CpK9E9UbMvggj6gGBF/0PkD3l1pF5tNHz8OUKc6kfXvlrkZaMMqdwei1ZAbT VQtNF2g4nMsOqbrqHHQ6cAkeg4sJgeZ+xs3BzWCgzdmmefNAONzo7/soksz4e4G83cvk cBaQ==
MIME-Version: 1.0
X-Received: by 10.180.76.146 with SMTP id k18mr493263wiw.5.1398237875967; Wed, 23 Apr 2014 00:24:35 -0700 (PDT)
Received: by 10.180.210.194 with HTTP; Wed, 23 Apr 2014 00:24:35 -0700 (PDT)
In-Reply-To: <D52EE5A7-CCCA-4579-BF49-950F259CE6D6@telmate.com>
References: <6.2.5.6.2.20140422074852.0d368728@elandnews.com> <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp> <01P6YID0EMJ2000052@mauve.mrochek.com> <D52EE5A7-CCCA-4579-BF49-950F259CE6D6@telmate.com>
Date: Wed, 23 Apr 2014 00:24:35 -0700
Message-ID: <CAL0qLwYy_1A_YT-d3-WEUMd1CGomcpzRHGPJo3OR6sSBi0VNoQ@mail.gmail.com>
Subject: Re: Review of draft-kucherawy-dmarc-base-04
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Mitch Rodrigues <mitch@telmate.com>
Content-Type: multipart/alternative; boundary=f46d04374995e89f4e04f7b09f3b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7GLIIbY979VWtKEF4kpG7P5iS4o
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, S Moonesamy <sm+ietf@elandsys.com>, Nevil Brownlee <rfc-ise@rfc-editor.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 07:24:47 -0000

--f46d04374995e89f4e04f7b09f3b
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 22, 2014 at 8:02 PM, Mitch Rodrigues <mitch@telmate.com> wrote:

> I don't see why we wouldn't, discussions regarding this draft have been
> going for quite some time. Might as well get community support regarding
> this, plus if nothing else it's fairly interesting subject.
>

Might I suggest dmarc@ietf.org?

-MSK

--f46d04374995e89f4e04f7b09f3b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Apr 22, 2014 at 8:02 PM, Mitch Rodrigues <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mitch@telmate.com" target=3D"_blank">mitch@t=
elmate.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=
=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"auto"><div>I don&#39;t see why w=
e wouldn&#39;t, discussions regarding this draft have been going for quite =
some time. Might as well get community support regarding this, plus if noth=
ing else it&#39;s fairly interesting subject.</div>
</div></blockquote><div><br></div><div>Might I suggest <a href=3D"mailto:dm=
arc@ietf.org">dmarc@ietf.org</a>?<br><br></div><div>-MSK<br></div></div></d=
iv></div>

--f46d04374995e89f4e04f7b09f3b--


From nobody Wed Apr 23 00:57:10 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDF481A00E1 for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 00:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 CZ4rIy89M_HT for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 00:57:03 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id F3AF51A00CF for <ietf@ietf.org>; Wed, 23 Apr 2014 00:57:02 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.149.29]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3N7uUkZ027800 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 23 Apr 2014 00:56:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398239803; bh=z4AImPPuLWQhrORSk1CLp1ODTkO2I29q7XarJaO3+0g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=V8o4HGJNzvYv66pWFenBZm3TdkwxBzoPbjoWiLtA6Cl96Ivcf6SN38eB9dtoA1F7F Z0gJfw3PdXk8qSEwBlLQ7e8v+eIsFZzKW/2Mg2Ia2ca5ltrdPlnwab20I5GkjOc2Jh e9UaVwjIVUeRJabSR7wBQN89NAe2BeSVrqiBELm8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398239803; i=@elandsys.com; bh=z4AImPPuLWQhrORSk1CLp1ODTkO2I29q7XarJaO3+0g=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Dm+FFCIzre/fMzSva5PUUua86MkTzu7hgR2jJL8pw2e/j4dx7D5AcZNafoMlSDnav cVR+ZrxPxXdGB5v+uFwZwb+ZEyAr891afXAneQoES//8JxwPAo2X3b4Kbf5GJPsoer Jrdmlw+DEHLcO4r9mokrGPkNB6FuLkuJ5Qvl64DQ=
Message-Id: <6.2.5.6.2.20140422231138.0d2221f0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 23 Apr 2014 00:54:16 -0700
To: Mitch Rodrigues <mitch@telmate.com>, "Murray S. Kucherawy" <superuser@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Review of draft-kucherawy-dmarc-base-04
In-Reply-To: <D52EE5A7-CCCA-4579-BF49-950F259CE6D6@telmate.com>
References: <6.2.5.6.2.20140422074852.0d368728@elandnews.com> <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp> <01P6YID0EMJ2000052@mauve.mrochek.com> <D52EE5A7-CCCA-4579-BF49-950F259CE6D6@telmate.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/avvcQJSKv5F8wW9OHHZHJoiUfio
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 07:57:08 -0000

Hi Mitch,
At 20:02 22-04-2014, Mitch Rodrigues wrote:
>I don't see why we wouldn't, discussions regarding this draft have 
>been going for quite some time. Might as well get community support 
>regarding this, plus if nothing else it's fairly interesting subject.

The review was for a draft being processed as an Independent 
submission.  Publication is intended to be done outside the IETF 
process.  Although the subject is interesting it would not be 
productive to discuss about it on the main IETF mailing list given 
the IETF is not taking a decision about that.

It would make life easier for the authors (of the draft) if the main 
IETF mailing list was not used to get community support.  That 
mailing list is well-known for unmanaged discussions; that can turn 
into an unpleasant experience.

At 00:24 23-04-2014, Murray S. Kucherawy wrote:
>Might I suggest dmarc@ietf.org?

I am okay with that.

Regards,
S. Moonesamy 


From nobody Wed Apr 23 10:37:45 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA8A11A042B for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 10:37:42 -0700 (PDT)
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] autolearn=ham
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 1jdEQx6ja4ZO for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 10:37:41 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 901301A042F for <ietf@ietf.org>; Wed, 23 Apr 2014 10:37:41 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3NHbT7b023808 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 23 Apr 2014 10:37:33 -0700
Message-ID: <5357F9D7.3050203@dcrocker.net>
Date: Wed, 23 Apr 2014 10:35:19 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: Review of draft-kucherawy-dmarc-base-04
References: <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp>
In-Reply-To: <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 23 Apr 2014 10:37:36 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CBg-t4Or-PmrfWwZnsy5OIE5sxE
Cc: ietf@ietf.org, Nevil Brownlee <rfc-ise@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 17:37:42 -0000

On 4/22/2014 5:30 PM, Martin Rex wrote:
>> Why is there such a recommendation?  What is a mail receiver?  I am 
>> > asking the question as there is "receiving SMTP server" in that sentence.
> That would be silly.  RFC5322.From might contain no DNS domain to begin with.


That was legal for RFC 733.  Apparently I dropped it for RFC 822.

The idea of an online surrogate (Sender:) for an offline author (From:)
was a friendly construct, but it didn't prove useful.

So a From: field address with no domain name has never been valid for
"Internet" email.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Apr 23 11:29:19 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECB4F1A023A for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 11:29:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level: 
X-Spam-Status: No, score=-4.573 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 sfbPAsR-SymO for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 11:29:13 -0700 (PDT)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 66D791A03E5 for <ietf@ietf.org>; Wed, 23 Apr 2014 11:29:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1398277748; x=1429813748; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=KpO+AFzKqjPebB3ZoAZ9c4YDeNnC0O1utxRr4keGevc=; b=b143NidrgYTYAUxG2gYMR5ZnKlUInebmBxndOy2hANH8af36B11AzzQk LgXShzI82OboadTfE/JnAGR7w0BodWrPuRoUSVDevmi/vZbhtiwy7CIM+ eDaclGTnDGptE4q/HQGgs1kGDz8YdUmLIn7kVI0YusCiklerkdZ6KT2Ic M=;
X-IronPort-AV: E=McAfee;i="5400,1158,7417"; a="30680444"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine01.qualcomm.com with ESMTP; 23 Apr 2014 11:29:07 -0700
X-IronPort-AV: E=Sophos;i="4.97,913,1389772800"; d="scan'208";a="720580288"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Apr 2014 11:29:09 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 23 Apr 2014 11:29:06 -0700
Message-ID: <5358066A.3040003@qti.qualcomm.com>
Date: Wed, 23 Apr 2014 13:28:58 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <dcrocker@bbiw.net>
Subject: Re: Review of draft-kucherawy-dmarc-base-04
References: <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp> <5357F9D7.3050203@dcrocker.net>
In-Reply-To: <5357F9D7.3050203@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TeHpL0JU5L9NpciOPb9d3bYCw-Y
Cc: ietf@ietf.org, Nevil Brownlee <rfc-ise@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 18:29:16 -0000

On 4/23/14 12:35 PM, Dave Crocker wrote:
> On 4/22/2014 5:30 PM, Martin Rex wrote:
>    
>> RFC5322.From might contain no DNS domain to begin with.
>>      
> So a From: field address with no domain name has never been valid for
> "Internet" email.
>    

Well, except http://tools.ietf.org/html/rfc6854

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Wed Apr 23 11:42:48 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF651A04AA for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 11:42:45 -0700 (PDT)
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] autolearn=ham
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 oFJfsbQK2qAM for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 11:42:44 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6822C1A04A9 for <ietf@ietf.org>; Wed, 23 Apr 2014 11:42:44 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3NIgZAP025514 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 23 Apr 2014 11:42:38 -0700
Message-ID: <53580918.10601@dcrocker.net>
Date: Wed, 23 Apr 2014 11:40:24 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Review of draft-kucherawy-dmarc-base-04
References: <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp> <5357F9D7.3050203@dcrocker.net> <5358066A.3040003@qti.qualcomm.com>
In-Reply-To: <5358066A.3040003@qti.qualcomm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Wed, 23 Apr 2014 11:42:38 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bAZF2SpQsao8PGA4YnFfcHNrKBs
Cc: ietf@ietf.org, Nevil Brownlee <rfc-ise@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 18:42:45 -0000

On 4/23/2014 11:28 AM, Pete Resnick wrote:
> On 4/23/14 12:35 PM, Dave Crocker wrote:
>> On 4/22/2014 5:30 PM, Martin Rex wrote:
>>> RFC5322.From might contain no DNS domain to begin with.
>> So a From: field address with no domain name has never been valid for
>> "Internet" email.
>
> Well, except http://tools.ietf.org/html/rfc6854


You seem to be saying that that doc counters my assertion.

This is a classic example of the problem with such a generic pointer: 
it leaves the reader to search through the document to find the 
essential bit of text.  And alas in my case, I failed.

I do not see anything in that doc that makes it valid to have a From 
field with no domain name.


d/

ps.  If indeed that doc re-introduced that bit of flexibility, it needs 
to be fixed.

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Apr 23 12:01:52 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 120BE1A04E7 for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 12:01:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level: 
X-Spam-Status: No, score=-4.573 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 dTDfrkmPmfLP for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 12:01:49 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF071A04C5 for <ietf@ietf.org>; Wed, 23 Apr 2014 12:01:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1398279704; x=1429815704; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=oiKne4xkVPXuKQy8f/NCspY0fgTQf3TiLZgW0afTIXM=; b=Z61i1CjkyknVGb8EXzzPCcOOwbcqPlyz8h3QOiPYbqkGUtdUTHvOhWD9 SB6tW78bTvAlqjw9HAcS2sV7Jq9C2GREHJXur0FQRzrWxG+I0dj9O7XrY 95wZn77rCjK9/5L1jfMLHdmgk/o2HduS9iPz3dHC+ZgPFzv4+JvGZL/E5 I=;
X-IronPort-AV: E=McAfee;i="5400,1158,7417"; a="121798004"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine02.qualcomm.com with ESMTP; 23 Apr 2014 12:01:43 -0700
X-IronPort-AV: E=Sophos;i="4.97,913,1389772800"; d="scan'208";a="29509355"
Received: from nasanexhc08.na.qualcomm.com ([172.30.39.7]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 23 Apr 2014 12:01:43 -0700
Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.7) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 23 Apr 2014 12:01:42 -0700
Message-ID: <53580E15.7050109@qti.qualcomm.com>
Date: Wed, 23 Apr 2014 14:01:41 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: <dcrocker@bbiw.net>
Subject: Re: Review of draft-kucherawy-dmarc-base-04
References: <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp> <5357F9D7.3050203@dcrocker.net> <5358066A.3040003@qti.qualcomm.com> <53580918.10601@dcrocker.net>
In-Reply-To: <53580918.10601@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bFFWRXyST8O0JsdiRG75mMaWZlA
Cc: ietf@ietf.org, Nevil Brownlee <rfc-ise@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 19:01:51 -0000

On 4/23/14 1:40 PM, Dave Crocker wrote:
> On 4/23/2014 11:28 AM, Pete Resnick wrote:
>> On 4/23/14 12:35 PM, Dave Crocker wrote:
>>> On 4/22/2014 5:30 PM, Martin Rex wrote:
>>>> RFC5322.From might contain no DNS domain to begin with.
>>> So a From: field address with no domain name has never been valid for
>>> "Internet" email.
>>
>> Well, except http://tools.ietf.org/html/rfc6854
>
> You seem to be saying that that doc counters my assertion.
>
> This is a classic example of the problem with such a generic pointer: 
> it leaves the reader to search through the document to find the 
> essential bit of text.  And alas in my case, I failed.
>
> I do not see anything in that doc that makes it valid to have a From 
> field with no domain name.

Sorry for being obscure. 6854 says:

    from = "From:" (mailbox-list / address-list) CRLF

And from 5322:

    address-list    =   (address *("," address)) / obs-addr-list
    mailbox-list    =   (mailbox *("," mailbox)) / obs-mbox-list
    address         =   mailbox / group
    mailbox         =   name-addr / addr-spec
    name-addr       =   [display-name] angle-addr
    angle-addr      =   [CFWS] "<" addr-spec ">" [CFWS] /
                        obs-angle-addr
    group           =   display-name ":" [group-list] ";" [CFWS]
    display-name    =   phrase

Which makes the following legal (from the examples in 6854):

       From: Nightly Monitor Robot:;

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Wed Apr 23 12:04:11 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3665E1A0424 for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 12:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 wCUwmbz8Ve0n for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 12:04:08 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id AE73C1A0422 for <ietf@ietf.org>; Wed, 23 Apr 2014 12:04:07 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6ZGYDH4000005C2@mauve.mrochek.com> for ietf@ietf.org; Wed, 23 Apr 2014 11:59:00 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6WZAZ2YYO000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Wed, 23 Apr 2014 11:58:56 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P6ZGYC0JUK000052@mauve.mrochek.com>
Date: Wed, 23 Apr 2014 11:52:44 -0700 (PDT)
Subject: Re: Review of draft-kucherawy-dmarc-base-04
In-reply-to: "Your message dated Wed, 23 Apr 2014 11:40:24 -0700" <53580918.10601@dcrocker.net>
References: <20140423003045.EBE6F1ACDC@ld9781.wdf.sap.corp> <5357F9D7.3050203@dcrocker.net> <5358066A.3040003@qti.qualcomm.com> <53580918.10601@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xIQE9CQXjVQ6yK2rQpfrGU6qPUo
Cc: Pete Resnick <presnick@qti.qualcomm.com>, ietf@ietf.org, Nevil Brownlee <rfc-ise@rfc-editor.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 19:04:09 -0000

> On 4/23/2014 11:28 AM, Pete Resnick wrote:
> > On 4/23/14 12:35 PM, Dave Crocker wrote:
> >> On 4/22/2014 5:30 PM, Martin Rex wrote:
> >>> RFC5322.From might contain no DNS domain to begin with.
> >> So a From: field address with no domain name has never been valid for
> >> "Internet" email.
> >
> > Well, except http://tools.ietf.org/html/rfc6854

Pete's right; I forgot about this update.

> You seem to be saying that that doc counters my assertion.

It does. RFC 6854 changes the syntax of From: header fields to allow an
address-list. The ABNF from there is:

  address-list    =   (address *("," address)) / obs-addr-list

  address         =   mailbox / group

  group           =   display-name ":" [group-list] ";" [CFWS]

Note that group list is optional, so something like:

  From: group: ;

is now legal. In fact RFC 6854 contains this example:

  From: Nightly Monitor Robot:;

I don't see a domain in there. Do you? I note that RFC 6854 exists precisly
because of the legitimate applications I've been talking about that need a way
to generate a legitimate message.

And IMO DMARC needs to take such usage into account.

				Ned


From nobody Wed Apr 23 15:54:25 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2221A029F for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 15:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 DJjRxESd3YaI for <ietf@ietfa.amsl.com>; Wed, 23 Apr 2014 15:54:22 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 93E5F1A070E for <ietf@ietf.org>; Wed, 23 Apr 2014 15:54:22 -0700 (PDT)
Received: (qmail 80016 invoked from network); 23 Apr 2014 22:54:15 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 23 Apr 2014 22:54:15 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=6fe1.53584497.k1404; i=johnl@user.iecc.com; bh=+IR7fNRP+DcCLAGAHnrDDzcKYQB0TFmYE/S/w3kfOls=; b=W6KC9LXRTD393H/bo4T9Imxqazt3zk/SvuWGqxrj0vTE/v+NswrwCKRtky++wN2BJVg1mySttXgqbq9k7cS97sggDKkRagkg1eQ7QsNkHP5+sHl8Dt59XQITGVh7cFStXlzgWF8u0IcXeNYtZ+6PjKtPH+H6UdCWNCqm7rUDWvyktYX2Gak6c2KHCq+mxLSwmqjVcW8xQpREZkTERZoLsi+KOR6tIJxp3zKGEJoOZN7GRyhCTQn3m3+VcNtocbXZ
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=6fe1.53584497.k1404; olt=johnl@user.iecc.com; bh=+IR7fNRP+DcCLAGAHnrDDzcKYQB0TFmYE/S/w3kfOls=; b=i+JqYFn8TsIXHx6W67ZzKLAh4gpdhHH3FpV8yPtDi7u21HWbsQix94zgVPllWFrcFqfS5K9fRJrKfkx+zHxOc5UozWqRam2SEs+P0s+dM6057KHXMYpbk5GQxmYCHks+EWXfS+xEUCgUKfdpr0wjWwPds3uSb2cGxOv6zW/n7Ochjvzq6k1nqkMgyeN/eyLl74nSmpuh0vhS7ABbDRk0TqGLnIyqMB7pLteec/42awjjYkxXTZOgQQCtJKnTBSnH
Date: 23 Apr 2014 22:53:53 -0000
Message-ID: <20140423225353.28640.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: empty from, was Review of draft-kucherawy-dmarc-base-04
In-Reply-To: <53580918.10601@dcrocker.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CPWsDLY5fioB6a-4FDJZkSz82uo
Cc: dcrocker@bbiw.net
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 22:54:24 -0000

>> Well, except http://tools.ietf.org/html/rfc6854

>I do not see anything in that doc that makes it valid to have a From 
>field with no domain name.

Section 2.1:

   from = "From:" (mailbox-list / address-list) CRLF

In RFC 5322 sec 3.4:

   address-list    =   (address *("," address)) / obs-addr-list
   address         =   mailbox / group
   group           =   display-name ":" [group-list] ";" [CFWS]

So this is valid:

 From:  Redacted for your own good :;

That's deliberate; the use case we had in mind is EAI mail downgraded
by a POP or IMAP server where there's no way to turn the EAI address
into an ASCII address.


R's,
John


From nobody Wed Apr 23 21:18:12 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E28141A029F; Wed, 23 Apr 2014 21:18:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.172
X-Spam-Level: 
X-Spam-Status: No, score=-0.172 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 PCUkx0cdciAQ; Wed, 23 Apr 2014 21:18:04 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B196E1A0025; Wed, 23 Apr 2014 21:18:04 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WdB6j-000OV3-9t; Thu, 24 Apr 2014 00:17:57 -0400
Date: Thu, 24 Apr 2014 00:17:52 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Subject: Re: [precis] Last Call: <draft-ietf-precis-framework-15.txt> (PRECIS Framework: Preparation and Comparison of Internationalized Strings in Application Protocols) to Proposed Standard
Message-ID: <6C520F47E0BA6CEF00EF649B@JcK-HP8200.jck.com>
In-Reply-To: <20140409190744.15518.7195.idtracker@ietfa.amsl.com>
References: <20140409190744.15518.7195.idtracker@ietfa.amsl.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/u4yH0GXQxIX6GSo_04VQr_mSgpg
Cc: precis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 04:18:08 -0000

--On Wednesday, April 09, 2014 12:07 -0700 The IESG
<iesg-secretary@ietf.org> wrote:

> The IESG has received a request from the Preparation and
> Comparison of Internationalized Strings WG (precis) to
> consider the following document: - 'PRECIS Framework:
> Preparation and Comparison of Internationalized    Strings in
> Application Protocols'
>   <draft-ietf-precis-framework-15.txt> as Proposed Standard
> 
> The IESG plans to make a decision in the next few weeks, and
> solicits final comments on this action. Please send
> substantive comments to the ietf@ietf.org mailing lists by
> 2014-04-23.

IESG,

I have deliberately waited until the end of the Last Call period
as posted [1], hoping that you would get (or generate) more
focused comments on the draft in the interim.  The issues
discussed in this note were raised while what became the PRECIS
WG (originally known by names like "Stringprep-bis") was being
discussed and chartered and again on several occasions during
the meetings of the WG.   At least in my opinion, they were
never discussed seriously: the WG made one important improvement
(shifting to a rule-based inclusion approach) but has
essentially ignored the fundamental problem.  Because the
predecessors of this note have not been actively considered in
the WG or while its charter was being created, I don't actually
expect it to accomplish anything other than to get some issues
on the record.  But I think the circumstances require one last
try.

This note consists of a high-level summary with details in
footnotes on its various points.  It is as short as I cam make
it without leaving out issues and explanations that I believe
are important.

Summary:

I see fundamental problems with approval of this specification
and some issues with the decisions it includes.  The first of
these is temporary; the second more fundamental.  

(1) After the PRECIS WG task list settled down into its charter
[2], the goal became, in essence, to replace Stringprep with
something more explicitly rule-based and to update (or advise
on) the various uses of Stringprep profiles.  As described in
the PRECIS charter, that approach noted the relationships among
the various parts of the PRECIS work and called for handling the
"framework, profile replacements, and guidelines ... in parallel
as much as possible".  The interrelated nature of the pieces
makes it inappropriate for the IESG to approve the "framework"
document for publication on the standards track at this time
because doing so would foreclose some reasonable discussion of
issues with the other specs -- exactly the situation the charter
language was intended, at least in my recollection, to prevent.
The approval and publication of RFC 6885 over a year ago has
already been used that way.

Some of the decisions reflected in the current draft
illustration why more testing against specific profile examples
and guidelines is important [5].

Recommendation: Tentatively approve the document now if that
seems otherwise justified (I suggest below that it is not) but
do not issue a Protocol Action Notice or handoff to the RFC
Editor until after a sufficient number of of "profile
replacements" and "guidelines" have been completed and examined
through the IETF Last Call process to validate the "framework"
provisions.  The analogy of such a request to "running code"
requirements should be obvious.

(2) The longer-term problem is the one that PRECIS simply
refused to address.  When designing systems with direct effects
on and interactions with users, predictability based on prior
user experience and expectations is vital.  That predictability
is often expressed as the Law of Least Astonishment.  In the
case of use of non-ASCII characters in Internet applications,
"least astonishment" implies, first, that rules should be
intuitive and easily understood to the extent possible.  Second
and more important, if a user understands the rules of one
application, she should be able to accurately extrapolate from
that application to others.  If there is a reason why that
extrapolation does not work, the reasons should be clearly
expressed and sufficiently comprehensible to be easily
incorporated into the user's cognitive framework... and there
should be few such cases.

With the addition of "IdentifierClass" and "FreeformClass" to
what, in its language, might be called "IDNA2008Class", we
already have between one and two "Classes" too many for good
user predictability.  The language that indicates that
additional classes might be defined in future specifications is
not nearly strong enough in discouraging additional classes and
explaining the reasons why.

The PRECIS framework appears to fail those tests.  It can be
read as actively encouraging multiple profiles [3].  This is
true even though the third bullet under "It is expected that
this framework will yield..." explicitly acknowledges "more
accurate expectations about the characters that are acceptable
in various contexts" as an explicit objective.

Recommendation: Hold this document until the various categories
are exercised by at least a sampling of applicable profiles.
Make the problems with excessive profiles explicit; impose
requirements on additional profiles that include an explanation
of why they are needed given the user-level interoperability and
astonishment problems that can result from even three of them
and require a higher level of review and consensus for creating
new ones than "expert review".  Modify the Security
Considerations section to identify user astonishment and
consequent confusion about what rules are being applied in a
given PRECIS-User protocol as a risk and possible attack vector.

thanks,
    john

  -----------------------------


[1] Despite the apparently-automatic announcement dated April
23, 2014 00:07 -0700 and indicating that the last call period
had ended and the document state changed, the announcement,
quoted above, says "by 2014-04-23".  To the best of my
knowledge, there has never been an announcement to the
community, much less one backed by community discussion and
consensus, that "by <date>" now means "00:07 California time on
that date".  If anything, we have tended to interpret "by
<date>" as COB on that date or the last minute of that date
anywhere in the world.

[2] http://datatracker.ietf.org/wg/precis/charter/

[3] Not only should multiple profiles be discouraged for this
type of case by the Law of Least Astonishment, but general IETF
experience indicates that profiles are a bad idea and that
protocols that depend on them (and use a significant variety)
tend to be less successful than those that do not.  

[4] Sections 3.2.2 and 3.3.2 of -15.

[5] There are issues with the two classes that are defined in
this document that have not, I believe, been carefully addressed
in the WG.  At a minimum, they need to be considered more
carefully in context with specific examples without preempting
the choices to be made for those examples.  The following are
examples, not an exclusive list:

(i) The "Contextual Rule" categories of IDNA2008 have proven to
be extremely problematic, confusing, and controversial enough to
be one of the key issues in the UTR 46 battles that have impeded
IDNA2008 adoption in some important communities.  While I still
believe that the IDNA2008 decision was the right one, inclusion
of those characters as Valid for both classes [4] should, given
those bad experiences, require significantly more explanation
and/or justification than this draft appears to provide.  If the
intent of incorporating this list in PRECIS is to provide for
compatibility with IDNA2008, the list should be incorporated by
reference (either to RFC 5892 and its successors or to a
separate documents that updates and replaces the list in RFC
5892 as well as being used for PRECIS),  not be provided as a
list of code points that could cause the two definitions to
diverge if changes are made to one or the other.  The issue may
apply more generally to the other characters listed in Section
7.6 and to other IDNA-derived elements of Section 7.

(ii) Characters with compatibility equivalents are problematic,
in large measure because of a Unicode issue that has been
extensively discussed in the past.  Basically the compatibility
equivalency category mixes several unrelated and incompatible
(sic) groups of things under a single label.  One extreme is
occupied by characters used with East Asian scripts that are
distinguished only by their widths.  If the Unicode design
principles of "characters, not glyphs" and "plain text" had been
followed, these different-width variations would never have been
assigned different code points.  As a contrasting example, the
relevance of, and distinctions among, special mathematical code
points distinguished by mathematical use and specific type
styles is less clear: treating them as separate characters may
be justified under some circumstances.  A more extreme example
occurs with some Chinese characters that Unicode treats as
compatibility equivalents for other characters.  That treatment
is usually (and perhaps always) appropriate when the "meaning"
of the characters is intended.  But some of those characters
are, or historically have been, used in personal names.  To the
extent to which those names are used as identifiers, e.g., for a
person thus named, treating them as invalid is inappropriate and
applying a compatibility mapping to them only slightly less bad.

(iii) Experience with IDNA strongly suggests that
"DefaultIgnorable" is a bad idea.  Forbidding some (or perhaps
all) of these characters may be reasonable; treating them as if
they were not present impedes possibly-reasonable future
extensions and provides an attack vector for phishing and other
types of unpleasant behavior that do not appear to be called out
in Security Considerations.  It is also worth noting that one
difference between IDNA2008 and this specification is that the
former is not profiled (except by registries providing their own
subsetting rules) while the latter is intended as a base for
profiling.  While the order in which categorization rules is
applied in Section 8 provides some protection (perhaps
sufficient protection if the spec is never updated or used as
the basis for a different profile), it is worth noting that some
code points appear in more than one category (e.g., the
notorious ZWJ and ZWNJ in both JoinControl (Section 7.8) and
PrecisIgnorableProperties (Section 7.13)) and that this should
at least be called out explicitly.



From nobody Thu Apr 24 08:05:18 2014
Return-Path: <franck@peachymango.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7951A073C; Wed, 23 Apr 2014 16:43:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 fLvvWIpeeCRz; Wed, 23 Apr 2014 16:43:05 -0700 (PDT)
Received: from smtp.01.com (smtp.01.com [199.36.142.181]) by ietfa.amsl.com (Postfix) with ESMTP id 1CD821A0734; Wed, 23 Apr 2014 16:43:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id D131039AAA9; Wed, 23 Apr 2014 18:42:58 -0500 (CDT)
X-Virus-Scanned: amavisd-new at smtp-out-2.01.com
Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cZA9yLGz4RSS; Wed, 23 Apr 2014 18:42:58 -0500 (CDT)
Received: from smtp.01.com (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id AE5B939AAB8; Wed, 23 Apr 2014 18:42:58 -0500 (CDT)
Received: from localhost (localhost [127.0.0.1]) by smtp-out-2.01.com (Postfix) with ESMTP id 977BD39AAB3; Wed, 23 Apr 2014 18:42:58 -0500 (CDT)
X-Virus-Scanned: amavisd-new at smtp-out-2.01.com
Received: from smtp.01.com ([127.0.0.1]) by localhost (smtp-out-2.01.com [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id U8UI9MCVw0Vj; Wed, 23 Apr 2014 18:42:58 -0500 (CDT)
Received: from mail-2.01.com (mail.01.com [172.18.30.178]) by smtp-out-2.01.com (Postfix) with ESMTP id 7556239AAA9; Wed, 23 Apr 2014 18:42:58 -0500 (CDT)
Date: Wed, 23 Apr 2014 18:42:57 -0500 (CDT)
From: Franck Martin <franck@peachymango.org>
To: dmarc@ietf.org
Message-ID: <1302891628.92012.1398296577196.JavaMail.zimbra@peachymango.org>
In-Reply-To: <1825854784.91854.1398296066545.JavaMail.zimbra@peachymango.org>
Subject: Re: empty from, was Review of draft-kucherawy-dmarc-base-04
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_92011_1247733592.1398296577195"
X-Originating-IP: [216.3.18.37]
X-Mailer: Zimbra 8.0.5_GA_5839 (ZimbraWebClient - FF28 (Mac)/8.0.5_GA_5839)
Thread-Topic: empty from, was Review of draft-kucherawy-dmarc-base-04
Thread-Index: 16PKek0xlYm3XB4aNjMz0DMQhd9OoQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/laEN8xRnKwOlq3XOdsGPnopzX1s
X-Mailman-Approved-At: Thu, 24 Apr 2014 08:05:08 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Apr 2014 23:43:07 -0000

------=_Part_92011_1247733592.1398296577195
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

If you read carefully http://tools.ietf.org/html/rfc6854#section-3=20
Mailbox syntax is the normal syntax to use in the "From:" and
   "Sender:" header fields; the address syntax defined in Section 2.1 ,
   which allows the specification of a group, is only for Limited Use
   (see RFC 2026 [RFC2026], Section=C2=A03.3 , item (d)) for the reasons
   described below.=20
You will see that an empty from is not encouraged and to be used only when =
you have a specific EAI need.=20

Basically if your MTA does EAI, it can reject emails (more or less safely) =
from another, EAI aware or not, MTA.=20

More over if you do DMARC, I think it is perfectly fine to ignore this RFC,=
 like people ignore SMTP over IPv6...=20

If I recall, I pushed this change during the last call of the document, bec=
ause the From: header with no domain in fact weakens anti-spam measures, an=
d I don't think the IETF vision is "less security".=20



------=_Part_92011_1247733592.1398296577195
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div>If you read carefully <a href="http://tools.ietf.org/html/rfc6854#section-3"><a>http://tools.ietf.org/html/rfc6854#section-3</a></a> </div><div><pre class="newpage">Mailbox syntax is the normal syntax to use in the "From:" and
   "Sender:" header fields; the address syntax defined in <a href="http://tools.ietf.org/html/rfc6854#section-2.1" data-mce-href="http://tools.ietf.org/html/rfc6854#section-2.1">Section 2.1</a>,
   which allows the specification of a group, is only for Limited Use
   (see <a href="http://tools.ietf.org/html/rfc2026" data-mce-href="http://tools.ietf.org/html/rfc2026">RFC 2026</a> <a href="http://tools.ietf.org/html/rfc2026#section-3.3" data-mce-href="http://tools.ietf.org/html/rfc2026#section-3.3">[RFC2026], Section&nbsp;3.3</a>, item (d)) for the reasons
   described below.</pre></div><div>You will see that an empty from is not encouraged and to be used only when you have a specific EAI need.<br></div><div><br></div><div>Basically if your MTA does EAI, it can reject emails (more or less safely) from another, EAI aware or not, MTA.<br></div><div><br></div><div>More over if you do DMARC, I think it is perfectly fine to ignore this RFC, like people ignore SMTP over IPv6...<br></div><div><br></div><div>If I recall, I pushed this change during the last call of the document, because the From: header with no domain in fact weakens anti-spam measures, and I don't think the IETF vision is "less security".<br></div><div><br></div><div><br></div></div></body></html>
------=_Part_92011_1247733592.1398296577195--


From nobody Thu Apr 24 08:18:46 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A41851A0397 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 08:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.872
X-Spam-Level: 
X-Spam-Status: No, score=-0.872 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 kdEmiBqHqkS4 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 08:18:40 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 817F01A02C1 for <ietf@ietf.org>; Thu, 24 Apr 2014 08:18:40 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.235.12]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3OFIMYx005751 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 24 Apr 2014 08:18:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398352713; bh=GS+c0N4hI19+uBjWaqLzYm5tadhbX5gS65jcviF16OQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xtQaT/Ljh8XtT1NrHtU+eUNZFS51XghnAopqVah7ll++Dfk16BjF+6jvqhlVxIdFW TSZc1+LYGsPKcX4uZA5qTdkHMvRvTEcdTsHz6alpsY1X03Ss38FoZb4+5DY1yKDNv0 xdYbABbNh5oeAi6dMUakM1PipRtRitT3DPz60p+Q=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398352713; i=@elandsys.com; bh=GS+c0N4hI19+uBjWaqLzYm5tadhbX5gS65jcviF16OQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=DUkccMteGXXMcZBiqlTxjQciHd6rHfT6tWZi4h2bb03nANBvp5IgdqyfOjAW7dO+V 4PgMFwuEC+CBrGCSIjuQJFvTmcfFsZX/yKZEnsFV0Q3lLShuQvm7Eio7i3IZ2b1CId U9S9zqzcw5k1qorLW8x2ocwP1KVrpCm96WsPIjoM=
Message-Id: <6.2.5.6.2.20140424071559.0b636398@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 24 Apr 2014 08:05:43 -0700
To: Ned Freed <ned.freed@mrochek.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Internet Technology Adoption and Transition
In-Reply-To: <01P6YJTPN8MO000052@mauve.mrochek.com>
References: <2D34F9A8-98B9-4FBD-A3CD-B3C4A4EA7CD5@iab.org> <6.2.5.6.2.20140417215305.0dc8c008@resistor.net> <01P6YJTPN8MO000052@mauve.mrochek.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aPyO-5lw18xCnYNQa0WxJtCcT8g
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 15:18:42 -0000

Hi Ned,
At 19:53 22-04-2014, Ned Freed wrote:
>I'm not sure what the report means by "evolve", but by any reasonable
>definition, I believe SMTP continues to evolve.

Ok.

>If you're talking about standards work, the IESG just approved the RRVS
>document which specifies a new SMTP extension. In recent times we've approved
>other extensions such as MT-PRIORITY. And let's not forget about EAI, which is
>a pretty major evolution of the protocol.
>
>And this process continues. I rather expect we'll see changes in the 
>STARTTLS space in the not too distant future.
>
>If you're talking about implementations, the first thing to note is that
>given the relatively small number of implementations in wide use, a change
>to even one or two of them is significant. And while progess is slow,
>it's pretty constant from my perspective.

I was looking at it in terms of what is implemented and what is 
deployed.  There has been standards work; some of examples are 
mentioned above.  I agree that EAI is a pretty major evolution of the protocol.

>As for actual deployment, things are even more skewed, which makes them
>difficult to measure. For example, if a major wireless vendor implements the
>BINARY extension in both their client and their own server, that can affect a
>huge swath of traffic without any need for anyone else to change.

There are different ways to look at usage.  As an example, BINARY may 
be about 25% of what's deployed (please treat that figure as unverified).

>The deployment of older extensions also changes over time, and it doesn't
>always increase. I'm fairly sure I'm seeing more of ENHANCEDSTATUSCODES but
>less of NOTARY. (And yeah, I know given the relationship between the 
>two that's
>wierd. I'm just reporing what I've observed.)

The statistics I looked at show a little more of ENHANCEDSTATUSCODES.

>Moreover, there can be evolutionary changes having nothing to do with
>extensions per se. For example, it seems that not only is use of STARTTLS on
>the rise, what cipher suites are enabled seems to be changing, 
>probably because
>a lot of sites are actually paying attention to such details when prior to the
>Snoden thing they care.

I haven't look into the STARTTLS statistics recently to be able to 
compare the figures with the ones before the Snow thing.

Regards,
S. Moonesamy 


From nobody Thu Apr 24 10:40:58 2014
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75EF41A0332; Thu, 24 Apr 2014 10:40:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.573
X-Spam-Level: 
X-Spam-Status: No, score=-4.573 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, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 0fKvJqfbNuHG; Thu, 24 Apr 2014 10:40:54 -0700 (PDT)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id E94B11A0227; Thu, 24 Apr 2014 10:40:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1398361248; x=1429897248; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=RCxtqtKQyDpOoa6gDv6xG91a2Ki042l7MOjtBAkXMec=; b=pp4DVCsMWwfRRexxA5axyQO4CPjuukZEK5qq9a06aCou4PBAuJc4vo5M eG/Q1HMKF7f3w98K+oAnXvGw3bjroW82PcqG9jZpSBmOqPyjsGSzhxgn4 lX27zE2TLd221okr6T34pnKqWfo5QnNyJ9vObYye+RG8f/FsvL1fZ5HNT 4=;
X-IronPort-AV: E=McAfee;i="5400,1158,7418"; a="122056722"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine02.qualcomm.com with ESMTP; 24 Apr 2014 10:40:47 -0700
X-IronPort-AV: E=Sophos;i="4.97,920,1389772800"; d="scan'208";a="29518320"
Received: from nasanexhc15.na.qualcomm.com ([129.46.52.215]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 24 Apr 2014 10:40:47 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by nasanexhc15.na.qualcomm.com (129.46.52.215) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Apr 2014 10:40:47 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Apr 2014 10:40:46 -0700
Message-ID: <53594C9C.1080507@qti.qualcomm.com>
Date: Thu, 24 Apr 2014 12:40:44 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: [precis] Last Call: <draft-ietf-precis-framework-15.txt> (PRECIS Framework: Preparation and Comparison of Internationalized Strings in Application Protocols) to Proposed Standard
References: <20140409190744.15518.7195.idtracker@ietfa.amsl.com> <6C520F47E0BA6CEF00EF649B@JcK-HP8200.jck.com>
In-Reply-To: <6C520F47E0BA6CEF00EF649B@JcK-HP8200.jck.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JRsuKlwaX_NTZJpFrxefYjjIAHU
Cc: ietf@ietf.org, precis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 17:40:56 -0000

John,

Peter has had a start on answering these meat of the issues, and unless 
there are objections (by you, or anyone else), I'd ask that the 
remainder of the technical discussion be taken to the precis mailing 
list alone. That said, a couple process points that I think are 
appropriate to discuss here:

On 4/23/14 11:17 PM, John C Klensin wrote:

> I have deliberately waited until the end of the Last Call period
> as posted [1], hoping that you would get (or generate) more
> focused comments on the draft in the interim.

Please don't do that in the future. In this particular case (and mea 
culpa for this), I completely missed this note before the IESG telechat 
started, and wish we could have had this discussion going before the 
IESG got the document. In the end, the outcome is as per your first 
recommendation anyway:

> Recommendation: Tentatively approve the document now if that
> seems otherwise justified (I suggest below that it is not) but
> do not issue a Protocol Action Notice or handoff to the RFC
> Editor until after a sufficient number of of "profile
> replacements" and "guidelines" have been completed and examined
> through the IETF Last Call process to validate the "framework"
> provisions.

The IESG tentatively approved the document today, but it's announcement 
is contingent on a final review by me and a writeup. (In the 
datatracker, you'll see this recorded as "Approved::Point Raised".) I 
was going to do that anyway to deal with other comments that came up 
during AD Evaluation and Last Call, but I'll take your comments into 
account as well. If we end up in a place where I think we need to bring 
it back to the IESG, I can always do that.

But I do want to comment on the overall process issue:

> The issues
> discussed in this note were raised while what became the PRECIS
> WG (originally known by names like "Stringprep-bis") was being
> discussed and chartered and again on several occasions during
> the meetings of the WG.   At least in my opinion, they were
> never discussed seriously: the WG made one important improvement
> (shifting to a rule-based inclusion approach) but has
> essentially ignored the fundamental problem.  Because the
> predecessors of this note have not been actively considered in
> the WG or while its charter was being created, I don't actually
> expect it to accomplish anything other than to get some issues
> on the record.  But I think the circumstances require one last
> try.
>    

As much as we've failed in many ways to keep the spirit of our 
procedures alive, they do still exist. The IETF is *not* supposed to be 
another of the "formal review" SDOs where nothing happens until formal 
last calls and final reviews. We are supposed to be running a process 
where consensus is *built* during document creation, and importantly 
where failures are identified early and throughout the process, not 
late. Part of the way the IETF operates is that we *don't* wait until 
it's a big formal deal to address problems. Part of the social contract 
is that participants take responsibility for that and make their 
concerns known while consensus building is still going on. We talk a lot 
in the IESG about how to push things back earlier in the process, to not 
have late surprises and to not rely on things like formal DISCUSSes of 
the IESG for getting good work out of the IETF. Participants have to be 
part of that as well and use the tools we have to make sure that our 
process operates effectively.

RFC 2026, Section 6.5.1, defines what to do if a participant's views 
have not been adequately considered by the Working Group or that the 
Working Group has made an incorrect technical choice. In particular, the 
first step is to approach the chairs directly, at which point the chairs 
are supposed to figure out how to resolve the matter, bringing in other 
members of the WG (or the WG as a whole) when needed. If that doesn't 
work, *then* you bring that concern to the AD to attempt to resolve. 
(And of course, after that you can appeal to the IESG.)

The PRECIS WG has been discussing this document for round about three 
years. The WG made the decision to send this document to the IESG two 
months ago. I do not know whether you discussed this matter directly 
with the chairs, but I know that you have not discussed it directly with 
me. If you hadn't come to the conclusion that things had gone off the 
rails until recently, there's not much that you could have done 
differently, but my sense from your message is that you have had this 
concern for quite some time and that the WG has been missing it. 
(Indeed, I have been following PRECIS better than some of my WGs, and I 
know I've been in the room at f2f sessions, and *I* missed that you had 
this concern.)

This concern should have been escalated long ago. You should have 
followed 2026/6.5.1 and brought this to the chairs, and then to me as 
the AD if you weren't getting heard. The IETF only works when all 
participants take the responsibility to raise concerns during the 
process. If the senior members of the community aren't going to take 
that responsibility, why are we surprised when people are discouraged 
about how our processes work?

As I said, I'll review these concerns, and I'll take the document back 
to the IESG (or even the WG) if that is warranted. But this isn't the 
way the process is supposed to work.

Disappointedly,

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From nobody Thu Apr 24 11:35:49 2014
Return-Path: <lrosen@rosenlaw.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAC071A03A3 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 11:35:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.033
X-Spam-Level: *
X-Spam-Status: No, score=1.033 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=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 5JzTfjgDi6Np for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 11:35:46 -0700 (PDT)
Received: from gproxy3-pub.mail.unifiedlayer.com (gproxy3-pub.mail.unifiedlayer.com [69.89.30.42]) by ietfa.amsl.com (Postfix) with SMTP id 64F2E1A01DB for <ietf@ietf.org>; Thu, 24 Apr 2014 11:35:46 -0700 (PDT)
Received: (qmail 7157 invoked by uid 0); 24 Apr 2014 18:35:32 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy3.mail.unifiedlayer.com with SMTP; 24 Apr 2014 18:35:32 -0000
Received: from box597.bluehost.com ([66.147.242.197]) by cmgw4 with  id tubS1n00g4GF2VN01ubVdv; Thu, 24 Apr 2014 12:35:32 -0600
X-Authority-Analysis: v=2.1 cv=CpMsLBID c=1 sm=1 tr=0 a=NRJ8aB/FPT4S3utBguGD+g==:117 a=NRJ8aB/FPT4S3utBguGD+g==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=qDS3CPt326AA:10 a=7xXQEuv9rCMA:10 a=CAIbOuo8jNoA:10 a=IkcTkHD0fZMA:10 a=4F77bVRYAAAA:8 a=FxJxCPAPh0wA:10 a=AqkBdCNi7UMA:10 a=pGLkceISAAAA:8 a=WOIJDy4HAAAA:8 a=pj-9fKN_caVvFKEtpwwA:9 a=U42Q-hmp9tQprG1B:21 a=nj1fQRHSBLokDjF6:21 a=QEXdDO2ut3YA:10 a=SqxYWZjetj4A:10 a=TImqNlVd7iMA:10 a=MSl-tDqOz04A:10 a=B0a0FVVDmlMA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=rosenlaw.com; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From:Reply-To; bh=4xO4qQmpi+JL5e0pb8XGZFUI95H4Bdx0zp/UEU+tzfI=;  b=f4dof/PfePElU9mgnSJU9neuFkDTPmiqNwhyBQQZ/y+DHg7KfyQhip952GJw3vlstu33xFdr+AxxNM2l63w4SHL2AZDFNANhW2Zvm5IyeXf+cs3yChUVh9EO64v15HgE;
Received: from [70.36.224.178] (port=53032 helo=Lawrencei) by box597.bluehost.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from <lrosen@rosenlaw.com>) id 1WdOUT-0004IT-OP; Thu, 24 Apr 2014 12:35:21 -0600
From: "Lawrence Rosen" <lrosen@rosenlaw.com>
To: "IETF" <ietf@ietf.org>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com>
In-Reply-To: <CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com>
Subject: RE: Author disclosures and conflict of interest
Date: Thu, 24 Apr 2014 11:35:19 -0700
Message-ID: <037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQKXcE4LMzjvYQvi+4zFEB3vA0KOeQJHdvB/mX66AqA=
Content-Language: en-us
X-Identified-User: {1397:box597.bluehost.com:rosenla1:rosenlaw.com} {sentby:smtp auth 70.36.224.178 authed with lrosen@rosenlaw.com}
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LHShOs0GghZ5F1NBKbD91_qjTUo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: lrosen@rosenlaw.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 18:35:48 -0000

Phillip Hallam-Baker wrote:
> Like the question 'are you a spy' which they used to ask when people=20
> entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc =
problem.

The question actually is: Do you agree to the ethical rules for =
scientists and engineers?=20

By the way, those ethical rules require only disclosure, not recusal.

/Larry


-----Original Message-----
From: Phillip Hallam-Baker [mailto:hallam@gmail.com]=20
Sent: Monday, April 21, 2014 2:05 PM
To: lrosen@rosenlaw.com
Cc: IETF Discussion Mailing List
Subject: Re: Author disclosures and conflict of interest

Like the question 'are you a spy' which they used to ask when people =
entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc =
problem.

The people who are being paid to subvert the standards aren't going to =
say.

They might not even know that the objective is subversion.


Like many IETF participants I have substantial financial interests in =
several Internet companies besides my employer. Am I meant to put those =
in a blind trust?

And even if I did all that people would still assume that I am working =
as an agent of the New World Order. Though quite how the other folk on =
the conference call worked out that the helicopter is black still =
puzzles me.


On Sun, Apr 20, 2014 at 1:18 PM, Lawrence Rosen <lrosen@rosenlaw.com> =
wrote:
> I=E2=80=99ve been skimming recent threads  on this list relating to =
work done=20
> (or not done) at IETF and was reminded of this from Science Magazine:
>
>
>
> Authorship Form and Conflict-of-Interest Statement
>
> To meet its responsibility to readers and to the public to provide=20
> clear and unbiased scientific results and analyses, Science believes=20
> that manuscripts (including Brevia, Essays, Perspectives, Policy=20
> Forums, Reports, Research Articles, Reviews, and Viewpoints) should be =

> accompanied by clear disclosures from all authors of the nature and=20
> level of their contribution to the article, their understanding=20
> regarding the obligation to share data and materials, and any=20
> affiliations, funding sources, or financial holdings that might raise=20
> questions about possible sources of bias. Before manuscript=20
> acceptance, therefore, authors will be asked to sign an=20
> authorship/conflict-of-interest form. Specific information will be =
sent to most authors at the time of manuscript revision.
>
> Authorship Form and Statement of Conflicts of Interest [PDF]
>
>
>
> Part IV regarding =E2=80=9CConflict of Interest=E2=80=9D is =
particularly relevant to=20
> standards organizations such as IETF. Such a disclosure requirement=20
> would further encourage everyone to trust and implement IETF =
specifications.
>
>
>
> This document follows the recommendations in On Being a Scientist: A=20
> Guide to Responsible Conduct in Research, The National Academies=20
> Press, Third Edition (2009).
>
>
>
> /Larry
>
>
>
> Lawrence Rosen
>
> Rosenlaw & Einschlag (www.rosenlaw.com)
>
> 3001 King Ranch Road, Ukiah, CA 95482
>
> Cell: 707-478-8932   Fax: 707-485-1243
>
>



--
Website: http://hallambaker.com/


From nobody Thu Apr 24 13:54:07 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9ED61A0265 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 13:54:06 -0700 (PDT)
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_50=0.8,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 zgXk7CG8FCME for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 13:54:03 -0700 (PDT)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 10CC51A03E2 for <ietf@ietf.org>; Thu, 24 Apr 2014 13:54:02 -0700 (PDT)
Received: by mail-la0-f53.google.com with SMTP id ec20so2417357lab.40 for <ietf@ietf.org>; Thu, 24 Apr 2014 13:53:56 -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:content-type:content-transfer-encoding; bh=bK7NHlcVQLe2z2NGffXRsGjT0fDontYSm0HzkOjnaDE=; b=mdWm2NMMx6QkN9X0HYO5X11JnDDQUuhBgbwrOGg7ib6t7uqhZ9glKWBQGuEb5Yc8gg 16pBMrzODaIpLdPwqC8p6ec9Wq5hv0z/7CZ1+7tBk2V15AR3vw0mMyPWVoTOfT1pQQMr aH0pqy3CmStIvRMMGTxEsXyPaRXJmy86xE7HEFb8ioHvPVdbd4dWBWXE7aapzp8l4Mnc w4RidvbeJkR3KJNa+JUEAWJXgx30+x2P/Rrqp+OluKCqEwmSRgVQPGNT9b7uXDb25VSj pegXxGXLHvLZNVK9149qWDNN5lEIDYGbdrdnmA5ayIzceom7TpeEUgbNZwTnPQeezU0w oMIw==
MIME-Version: 1.0
X-Received: by 10.152.2.225 with SMTP id 1mr2599850lax.37.1398372836027; Thu, 24 Apr 2014 13:53:56 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Thu, 24 Apr 2014 13:53:55 -0700 (PDT)
In-Reply-To: <037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com> <037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com>
Date: Thu, 24 Apr 2014 16:53:55 -0400
Message-ID: <CAMm+LwhO4a3=O_=xp4Ge8AsFFXnojdH=YKQNoQRsGXiMr88e+g@mail.gmail.com>
Subject: Re: Author disclosures and conflict of interest
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Lawrence Rosen <lrosen@rosenlaw.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CvvKUSD3b83SZvjR3PIx9Pyr5fg
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 20:54:06 -0000

So there is only one set of ethical rules for scientists and engineers then=
?

Thats news to me.

On Thu, Apr 24, 2014 at 2:35 PM, Lawrence Rosen <lrosen@rosenlaw.com> wrote=
:
> Phillip Hallam-Baker wrote:
>> Like the question 'are you a spy' which they used to ask when people
>> entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc pr=
oblem.
>
> The question actually is: Do you agree to the ethical rules for scientist=
s and engineers?
>
> By the way, those ethical rules require only disclosure, not recusal.
>
> /Larry
>
>
> -----Original Message-----
> From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
> Sent: Monday, April 21, 2014 2:05 PM
> To: lrosen@rosenlaw.com
> Cc: IETF Discussion Mailing List
> Subject: Re: Author disclosures and conflict of interest
>
> Like the question 'are you a spy' which they used to ask when people ente=
red the US, I fail to see how this helps with the NSA/FSB/PLA/etc problem.
>
> The people who are being paid to subvert the standards aren't going to sa=
y.
>
> They might not even know that the objective is subversion.
>
>
> Like many IETF participants I have substantial financial interests in sev=
eral Internet companies besides my employer. Am I meant to put those in a b=
lind trust?
>
> And even if I did all that people would still assume that I am working as=
 an agent of the New World Order. Though quite how the other folk on the co=
nference call worked out that the helicopter is black still puzzles me.
>
>
> On Sun, Apr 20, 2014 at 1:18 PM, Lawrence Rosen <lrosen@rosenlaw.com> wro=
te:
>> I=E2=80=99ve been skimming recent threads  on this list relating to work=
 done
>> (or not done) at IETF and was reminded of this from Science Magazine:
>>
>>
>>
>> Authorship Form and Conflict-of-Interest Statement
>>
>> To meet its responsibility to readers and to the public to provide
>> clear and unbiased scientific results and analyses, Science believes
>> that manuscripts (including Brevia, Essays, Perspectives, Policy
>> Forums, Reports, Research Articles, Reviews, and Viewpoints) should be
>> accompanied by clear disclosures from all authors of the nature and
>> level of their contribution to the article, their understanding
>> regarding the obligation to share data and materials, and any
>> affiliations, funding sources, or financial holdings that might raise
>> questions about possible sources of bias. Before manuscript
>> acceptance, therefore, authors will be asked to sign an
>> authorship/conflict-of-interest form. Specific information will be sent =
to most authors at the time of manuscript revision.
>>
>> Authorship Form and Statement of Conflicts of Interest [PDF]
>>
>>
>>
>> Part IV regarding =E2=80=9CConflict of Interest=E2=80=9D is particularly=
 relevant to
>> standards organizations such as IETF. Such a disclosure requirement
>> would further encourage everyone to trust and implement IETF specificati=
ons.
>>
>>
>>
>> This document follows the recommendations in On Being a Scientist: A
>> Guide to Responsible Conduct in Research, The National Academies
>> Press, Third Edition (2009).
>>
>>
>>
>> /Larry
>>
>>
>>
>> Lawrence Rosen
>>
>> Rosenlaw & Einschlag (www.rosenlaw.com)
>>
>> 3001 King Ranch Road, Ukiah, CA 95482
>>
>> Cell: 707-478-8932   Fax: 707-485-1243
>>
>>
>
>
>
> --
> Website: http://hallambaker.com/
>



--=20
Website: http://hallambaker.com/


From nobody Thu Apr 24 14:35:33 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6953C1A03F5 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 14:35:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.952
X-Spam-Level: 
X-Spam-Status: No, score=-5.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 coM81O-C8Nfi for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 14:35:28 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id CE53F1A03F2 for <ietf@ietf.org>; Thu, 24 Apr 2014 14:35:27 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s3OLZGmH008191 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 Apr 2014 23:35:16 +0200 (MEST)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <5356F23F.40909@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
Date: Thu, 24 Apr 2014 23:35:16 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140424213516.722041ACE0@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HC3lyOGSiJdooBjpiqPXDn2IAzo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 21:35:30 -0000

Doug Barton wrote:
> 
> What won't help is sitting on the sidelines and whinging that the "DMARC 
> cabal" "doesn't get it" and has to listen to us about how it should 
> conduct their business. Because not only do they clearly not have to do 
> that, they are not doing it.

But that is exactly what happens here, they obviously don't get it at all.

In case you didn't know or realize, what DMARC specifies for p=reject
is actually a real felony crime in Germany (no kidding!), and this may
apply to all over Europe (since the basic idea was spread out all over
europe with a EU directive), unless each individual receipient(!!) has
explicitly opted-in for this to happen.  It should be fairly easy 
to get a cease-and-desist order against European ISPs for blocking
EMail on DMARC p=reject.

It also should stop since it is technically wrong.  It is the tail
trying to wag the dog and some form of company-level bullying.

Get all those stupid MUAs fixed that misrepresent the meaning of rfc5322.From,
and in particular the meaning of rfc5322.From when a rfc5322.Sender is
present in the same message.


-Martin


From nobody Thu Apr 24 15:18:13 2014
Return-Path: <dougb@dougbarton.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42B0A1A03F8 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 15:18:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.026
X-Spam-Level: *
X-Spam-Status: No, score=1.026 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 m4iobmRqSFZ9 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 15:18:10 -0700 (PDT)
Received: from dougbarton.us (dougbarton.us [IPv6:2607:f2f8:ab14::2]) by ietfa.amsl.com (Postfix) with ESMTP id 3F3661A03EF for <ietf@ietf.org>; Thu, 24 Apr 2014 15:18:10 -0700 (PDT)
Received: from [192.168.2.22] (adsl-99-146-28-213.dsl.lsan03.sbcglobal.net [99.146.28.213]) by dougbarton.us (Postfix) with ESMTPSA id 0099322B20; Thu, 24 Apr 2014 22:18:03 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dougbarton.us; s=dougbarton.us; t=1398377884; bh=8Gy0zIOHMpE7A1ImoET/kp/GqG63N3zfTtIqR+Ij8cM=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=V1FlyS75ayfd/J9LCAXpaLF/IaKoR8uCr8fzkTQg1KdtB2zkeqaQQQP/dkDdCfmgN fenGrMNVBnwlFwh670XiWCVdZUhXaNr7LbblvTusxCmXvpDS4AN3qzCH9Tl8zO65PD r8aMcWrc5jo0jGHONV6mADHsH1Hflkv3ilsDu/mE=
Message-ID: <53598D9B.8030708@dougbarton.us>
Date: Thu, 24 Apr 2014 15:18:03 -0700
From: Doug Barton <dougb@dougbarton.us>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: mrex@sap.com
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <20140424213516.722041ACE0@ld9781.wdf.sap.corp>
In-Reply-To: <20140424213516.722041ACE0@ld9781.wdf.sap.corp>
X-Enigmail-Version: 1.7a1pre
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/l5sOWcco3mltejIVySdIoP5QZpw
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 22:18:11 -0000

On 04/24/2014 02:35 PM, Martin Rex wrote:
> Doug Barton wrote:
>>
>> What won't help is sitting on the sidelines and whinging that the "DMARC
>> cabal" "doesn't get it" and has to listen to us about how it should
>> conduct their business. Because not only do they clearly not have to do
>> that, they are not doing it.
>
> But that is exactly what happens here, they obviously don't get it at all.

... and yet the DMARC rollout continues. My point being that complaining 
about it has been ineffective so far, and is likely to continue to be 
ineffective.

> In case you didn't know or realize, what DMARC specifies for p=reject
> is actually a real felony crime in Germany (no kidding!),

I can't comment intelligently on that point. However I would assume that 
the high-powered attorneys at the large multi-national corporations 
(Yahoo! and AOL) who have already deployed it don't think you're right. 
OTOH if you are right, it will make an interesting side show. :)

> It also should stop since it is technically wrong.

That's your opinion, and the opinion of a non-trivial number of people 
on this list. But again, even if you're right, the thing is being 
deployed anyway. So fixing the mailing list software is the right thing 
to do regardless.

> It is the tail trying to wag the dog

You have "the tail" and "the dog" reversed. Mailing list traffic is a 
tiny fraction of what the big providers carry. IT is the tail.

Doug


From nobody Thu Apr 24 16:30:14 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7226D1A041D for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 16:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.419
X-Spam-Level: **
X-Spam-Status: No, score=2.419 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 qUI7HButmLfV for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 16:30:12 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 4171E1A0294 for <ietf@ietf.org>; Thu, 24 Apr 2014 16:30:12 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 75EF4CC0A1 for <ietf@ietf.org>; Thu, 24 Apr 2014 19:30:05 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id uGeexrgvBS3H for <ietf@ietf.org>; Thu, 24 Apr 2014 19:29:20 -0400 (EDT)
Received: from [10.3.107.182] (unknown [70.42.157.30]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 7A94CCC097 for <ietf@ietf.org>; Thu, 24 Apr 2014 19:28:41 -0400 (EDT)
Message-ID: <53599E14.7070901@meetinghouse.net>
Date: Thu, 24 Apr 2014 19:28:20 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <20140424213516.722041ACE0@ld9781.wdf.sap.corp>
In-Reply-To: <20140424213516.722041ACE0@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D9mSOFQCdxpDxYFF_EijgXgW3G8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 23:30:13 -0000

Martin,

Martin Rex wrote:
> In case you didn't know or realize, what DMARC specifies for p=reject
> is actually a real felony crime in Germany (no kidding!), and this may
> apply to all over Europe (since the basic idea was spread out all over
> europe with a EU directive), unless each individual receipient(!!) has
> explicitly opted-in for this to happen.  It should be fairly easy
> to get a cease-and-desist order against European ISPs for blocking
> EMail on DMARC p=reject.
>
Can you provide a legal citation?  That would be really cool!

 From where I sit, it also looks like a violation of the US Computer 
Fraud and Abuse Act (effectively, knowingly causing damage to other 
systems - which has been applied to DDoS attacks).  But I haven't heard 
any lawyers or prosecutors stand up and confirm that.

Miles Fidelman


From nobody Thu Apr 24 16:41:31 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52A7A1A042B for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 16:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.419
X-Spam-Level: 
X-Spam-Status: No, score=0.419 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 tE5ol1jjuzuN for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 16:41:28 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 50DDC1A0294 for <ietf@ietf.org>; Thu, 24 Apr 2014 16:41:28 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 73375CC09B for <ietf@ietf.org>; Thu, 24 Apr 2014 19:41:21 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4D688ehj5JDF for <ietf@ietf.org>; Thu, 24 Apr 2014 19:24:52 -0400 (EDT)
Received: from [10.3.107.182] (unknown [70.42.157.30]) by server1.neighborhoods.net (Postfix) with ESMTPSA id D9B37CC093 for <ietf@ietf.org>; Thu, 24 Apr 2014 19:24:51 -0400 (EDT)
Message-ID: <53599D30.3050904@meetinghouse.net>
Date: Thu, 24 Apr 2014 19:24:32 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <20140424213516.722041ACE0@ld9781.wdf.sap.corp> <53598D9B.8030708@dougbarton.us>
In-Reply-To: <53598D9B.8030708@dougbarton.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9dnS-PnaSrjNZYiiDayVt4G0SHw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 23:41:30 -0000

Doug Barton wrote:
> On 04/24/2014 02:35 PM, Martin Rex wrote:
>> Doug Barton wrote:
>>>
>>> What won't help is sitting on the sidelines and whinging that the 
>>> "DMARC
>>> cabal" "doesn't get it" and has to listen to us about how it should
>>> conduct their business. Because not only do they clearly not have to do
>>> that, they are not doing it.
>>
>> But that is exactly what happens here, they obviously don't get it at 
>> all.
>
> ... and yet the DMARC rollout continues. My point being that 
> complaining about it has been ineffective so far, and is likely to 
> continue to be ineffective.
>
>> In case you didn't know or realize, what DMARC specifies for p=reject
>> is actually a real felony crime in Germany (no kidding!),
>
> I can't comment intelligently on that point. However I would assume 
> that the high-powered attorneys at the large multi-national 
> corporations (Yahoo! and AOL) who have already deployed it don't think 
> you're right. OTOH if you are right, it will make an interesting side 
> show. :)
>
>> It also should stop since it is technically wrong.
>
> That's your opinion, and the opinion of a non-trivial number of people 
> on this list. But again, even if you're right, the thing is being 
> deployed anyway. So fixing the mailing list software is the right 
> thing to do regardless.
>
>> It is the tail trying to wag the dog
>
> You have "the tail" and "the dog" reversed. Mailing list traffic is a 
> tiny fraction of what the big providers carry. IT is the tail.
>
Is that really true, after you eliminate all of the spam, and the ads 
that fall just this side of "legitimate?"

Given that spam is now, what, 80+ percent of net traffic (some sources 
claim >90%), I wonder what the real breakdown is between:
- personal email
- work email
- notifications from social media sites
- "real" commercial traffic (bills, statements, order confirmations)
- list traffic (including work/company/university lists, user support, 
project-specific, affinity groups, churches, one's kids' schools, etc.)

And then I wonder how that differs for:
- personal mailboxes
- work mailboxes
- separate mailboxes set up to insulate one's personal mailbox from 
things other than personal and work traffic

In that later regard, I see an awful lot of people who set up mailboxes 
on free services, specifically for list-related traffic.

Speaking personally for a moment, and I'm certainly atypical, what I see is:
- personal account (been around a long time, highly visible, aggregates 
a lot of older accounts, a lot of admin traffic is routed to it as well)
--- 5000 messages a day
--- 4500, automatically filtered to /dev/null (spam, admin traffic I 
really don't want to look at, some old lists)
--- of the remaining traffic:
------ 200 or so - spam that gets past loose spam traps, deleted by eyeball
------ 225 or so - admin and list traffic (more these days, given the 
DMARC and IANAxfr discussions)
------ 25 - a mix of personal, notifications, various other stuff

- AOL and Yahoo accounts - rarely used - whenever I check, ALL spam
- work account: mostly 1-1 and some professional newsletters (1-way lists)

I'd be really interested in profiles of typical user accounts from big 
providers who claim that most of what they handle isn't list traffic.

Miles Fidelman








From nobody Thu Apr 24 17:26:34 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D051A043A for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 17:26:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.952
X-Spam-Level: 
X-Spam-Status: No, score=-5.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 RPhcySoLWQry for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 17:26:30 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFE51A02B8 for <ietf@ietf.org>; Thu, 24 Apr 2014 17:26:30 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s3P0QNkX013788 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Apr 2014 02:26:23 +0200 (MEST)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <53599E14.7070901@meetinghouse.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Date: Fri, 25 Apr 2014 02:26:22 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eGhpZ6_5t2SNWP7YjGo85M7g9Dk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 00:26:32 -0000

Miles Fidelman wrote:
>=20
> Martin Rex wrote:
>> In case you didn't know or realize, what DMARC specifies for p=3Dreject
>> is actually a real felony crime in Germany (no kidding!), and this may
>> apply to all over Europe (since the basic idea was spread out all over
>> europe with a EU directive), unless each individual receipient(!!) has
>> explicitly opted-in for this to happen.  It should be fairly easy
>> to get a cease-and-desist order against European ISPs for blocking
>> EMail on DMARC p=3Dreject.
>
> Can you provide a legal citation?  That would be really cool!

1. Blocking EMail based on DMARC policy is illegal per =A7206 Abs. 2 Nr. 2 =
StGB.

2. Actually, even looking at rfc5322.From (rather than MAIL FROM:) for
   the purpose of looking up DMARC policy records=20
   is illegal per =A7206 Abs. 2 Nr. 1 StGB.

3. Any DMARC-triggered reporting about forwarded emails is also illegal
   per =A7206 Abs. 1 StGB and =A788 TKG.

And while I'm currently not sure whether the first two are similar
all over europe, the last one DEFINITELY is under the current EU data
protection directive.

Technically, EMail is an issue between a sender of a telecommunication,
a receiver of a telecommunication and a telecommunication service provider.

If an MTA is relaying (or delivering to a mailbox), then the sender is
whoever talks at the other end of the TCP connection that is used to
transfer the EMail to the MTA on port 25.  The receiver is what is
named by the sender in the RCPT TO: command (the mail contents is off limit=
s),
and the MTA is an agent of the telecommunications provider.

What appears in the rfc5322.from of the message is legally, none of the
MTAs business.  And even if is be an attribution of authorship
of some third party in rfc5322.from, this party has absolutely no say
in what contents sender transfers to receiver.  It is also illegal
for the telecommunications service provider to reveal the fact of
this communication to other parties. This even applies to failed
communication attempts.  The only party to which the telecommunications
provider would be allowed to report a failed delivery is the address
(if any) supplied by the sender (i.e. the MAIL FROM: envelope address).


>=20
>  From where I sit, it also looks like a violation of the US Computer=20
> Fraud and Abuse Act (effectively, knowingly causing damage to other=20
> systems - which has been applied to DDoS attacks).  But I haven't heard=
=20
> any lawyers or prosecutors stand up and confirm that.


The DMARC policy scheme is actually censoring of a telecommunication=20
between a messge sender and a message receiver through a telecommunications
provider by some _outside_ third party.  So in the US a p=3Dreject DMARC po=
licy
might potentially be freedom of speech (1st Amendment) violation.


-Martin


From nobody Thu Apr 24 17:44:52 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2366D1A0447 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 17:44:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 8iSC_woqSNc7 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 17:44:46 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [IPv6:2607:f0d0:3001:aa::2]) by ietfa.amsl.com (Postfix) with ESMTP id CEE491A0442 for <ietf@ietf.org>; Thu, 24 Apr 2014 17:44:46 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 1DC5BD0453C; Thu, 24 Apr 2014 20:44:40 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1398386680; bh=saOo2lmv+UoXmRkRYQpI6l2RYua+ftPG5WVWv/ynQUw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vxmvwNAtzHoy2FUeH+NLovZD5vdKsPTlzwSa8qTk68ublqTGAnJzYKIpI5d6dNFo0 Wb3Lgh5ZD2HS13VYsO+pqbMS4HBktthKC9uD11UbYZb2JQ9KgXJUNp8PIBelpnjNnZ NJvOSEflu2xaLtKsbpLYScd5FTToRQISJCo0dIW0=
Received: from scott-latitude-e6320.localnet (63-253-113-202.ip.mcleodusa.net [63.253.113.202]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id C7E30D04183; Thu, 24 Apr 2014 20:44:39 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Date: Thu, 24 Apr 2014 20:44:37 -0400
Message-ID: <7859156.ek3Qf5sxiO@scott-latitude-e6320>
User-Agent: KMail/4.13 (Linux/3.13.0-24-generic; KDE/4.13.0; x86_64; ; )
In-Reply-To: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp>
References: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vpGrysc1AddFzhgyKw-BH6LUtvo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 00:44:48 -0000

On Friday, April 25, 2014 02:26:22 Martin Rex wrote:
...
> The DMARC policy scheme is actually censoring of a telecommunication
> between a messge sender and a message receiver through a telecommunications
> provider by some _outside_ third party.  So in the US a p=reject DMARC
> policy might potentially be freedom of speech (1st Amendment) violation.

No idea about the rest of it, but this is nonsense.  The 1st Amendment to the 
constitution is a restriction on government action, not on private action.  
See http://xkcd.com/1357/ .

Scott K


From nobody Thu Apr 24 17:51:44 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF7D31A0448 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 17:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.952
X-Spam-Level: 
X-Spam-Status: No, score=-5.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 dfd5J2-SgzXr for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 17:51:40 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 32B8F1A02AA for <ietf@ietf.org>; Thu, 24 Apr 2014 17:51:40 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s3P0pXfd018050 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Apr 2014 02:51:33 +0200 (MEST)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <7859156.ek3Qf5sxiO@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
Date: Fri, 25 Apr 2014 02:51:33 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140425005133.50CE01ACE0@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7IkWa84vND-Ca2mdm4nbsJnS72k
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 00:51:41 -0000

Scott Kitterman wrote:
> On Friday, April 25, 2014 02:26:22 Martin Rex wrote:
>>
>> The DMARC policy scheme is actually censoring of a telecommunication
>> between a messge sender and a message receiver through a telecommunications
>> provider by some _outside_ third party.  So in the US a p=reject DMARC
>> policy might potentially be freedom of speech (1st Amendment) violation.
> 
> No idea about the rest of it, but this is nonsense.  The 1st Amendment to the 
> constitution is a restriction on government action, not on private action.  
> See http://xkcd.com/1357/ .

OK.  I'm terribly sorry for you across the pond then.

In the German constitution and in the European Human Rights Convention
this is a basic right, and it protects not just from your own government,
but also from private actors and other governments.

-Martin


From nobody Thu Apr 24 18:17:48 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE15F1A01B5 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 18:17:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.142
X-Spam-Level: **
X-Spam-Status: No, score=2.142 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_16=0.6, SPF_NEUTRAL=0.779] autolearn=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 6CKJ4z4C3oer for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 18:17:45 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5432C1A0197 for <ietf@ietf.org>; Thu, 24 Apr 2014 18:17:44 -0700 (PDT)
Received: (qmail 66099 invoked from network); 25 Apr 2014 01:17:38 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 25 Apr 2014 01:17:38 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=11325.5359b7b2.k1404; i=johnl@user.iecc.com; bh=ArQ0VzyS6O5M+EkD/i3ktlFp2XM6veh97NzdcXsPUR4=; b=QWquCxHib8tgc1rF4JDZNsrR5SHGx5k2IVkp3WfbgGX0FgyIH4OLXqyAQUMtoaXePP775Wy1f5aZRtBqw53t1jyQ+jKPgxDhWMV+lJzO7lgmad57P05o1j4qPIbro2w+s40PsTO48QI6s/Yxq6mWXFQSFSLzB7d00XVCtB8D2HgGIu9JdC/yKhpP5r5+UvCoIgss960310WLlRTjHmMHthQk2H8t8zwFDonDP+fUfw9JD2457O9zkatVcYxkBfVg
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=11325.5359b7b2.k1404; olt=johnl@user.iecc.com; bh=ArQ0VzyS6O5M+EkD/i3ktlFp2XM6veh97NzdcXsPUR4=; b=YxxcKzn3K50fwvteaudX0TfnGkNZFvSCFZ21mbY6ybldoGxATlxvVWv5zHLigaf5OArvzzBEs0hHapffMbgmMECnBq10G/AcjfNk/K1c4Xsl9kEVhwGu+ofWJ9/a+EOD9GLPtcLAHDUczlLkZNwBW3st5Wyy7XcpljLXCQdlJg5eAaujUcU7Bc3MQUEVvqCxgABNNyoPg3PDQarXRI00SdbyGVAJOEV8UHCatBnVmglQndYdrwgOe5hN1ZHljxQk
Date: 25 Apr 2014 01:17:16 -0000
Message-ID: <20140425011716.70436.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2WFmawQVR25cDCK7xa9DN-8gkNo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 01:17:47 -0000

>> Can you provide a legal citation?  That would be really cool!
>
>1. Blocking EMail based on DMARC policy is illegal per §206 Abs. 2 Nr. 2 StGB.
>
>2. Actually, even looking at rfc5322.From (rather than MAIL FROM:) for
>   the purpose of looking up DMARC policy records 
>   is illegal per §206 Abs. 2 Nr. 1 StGB.
>
>3. Any DMARC-triggered reporting about forwarded emails is also illegal
>   per §206 Abs. 1 StGB and §88 TKG.

If that's true, how can spam filtering be legal?  The phrase "without
authorization" is pretty elastic, and all the ISPs I know consider themselves
authorized to mange user mail any way they want.


>The DMARC policy scheme is actually censoring of a telecommunication 
>between a messge sender and a message receiver through a telecommunications
>provider by some _outside_ third party.  So in the US a p=reject DMARC policy
>might potentially be freedom of speech (1st Amendment) violation.

Uh, no.  The First Amendment does not affect private entities, and
case law (White Buffalo vs. Texas) says that government entities have
broad discretion to do network management when acting as ISPs.

R's,
John


From nobody Thu Apr 24 18:41:24 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0BE41A035C for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 18:41:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 B5uyutjDaCvm for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 18:41:17 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by ietfa.amsl.com (Postfix) with ESMTP id 086EC1A02B9 for <ietf@ietf.org>; Thu, 24 Apr 2014 18:41:16 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id v10so2550511pde.25 for <ietf@ietf.org>; Thu, 24 Apr 2014 18:41:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=63kcW5tmfI148lILuJ1sgCsKUKEj2QnI5QP3llygQIw=; b=lq9yvpdHINSlzwMEyxhQ16rZs588qr+EAu+Ie+prVVHTWfGlKFOnTOpkbPSIdKYqS3 2NKF8B0+22hrrm8Cumn5ov32VxmY6ckYLBoMwTlUCrbVFfrfNNWHb2cGgaqt1madFNW5 W/ar92jiSPoVWXJcoCAyy2koDXCYB3LiWCvrT9owkRKLxzLHJAwqakSRccrGwHVQYyeR rdqHMPZfy38qrq8FNgCwr1jnINm0UayhxaA6qDjjfIN9AH6m8WvkfTLsPB4YkStrO5wO I2hK8FCzRTOB0XfvIYfb29+1gWVyp3Ofg5Ki3xnii6MB8w3zzPIrUKpsXjx6xP76fcGp uS/w==
X-Received: by 10.66.230.193 with SMTP id ta1mr4240937pac.29.1398390070856; Thu, 24 Apr 2014 18:41:10 -0700 (PDT)
Received: from ?IPv6:2601:9:1b80:1046:11f8:ef05:2ff8:3d6c? ([2601:9:1b80:1046:11f8:ef05:2ff8:3d6c]) by mx.google.com with ESMTPSA id ei4sm11979857pbb.42.2014.04.24.18.41.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 24 Apr 2014 18:41:09 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <7859156.ek3Qf5sxiO@scott-latitude-e6320>
Date: Thu, 24 Apr 2014 18:41:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <57E35BDB-30DF-4829-A6CE-F1132E0C2EFC@gmail.com>
References: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp> <7859156.ek3Qf5sxiO@scott-latitude-e6320>
To: Scott Kitterman <scott@kitterman.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dwzIbUfd-76s1PIZ_aO5BWipjm0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 01:41:22 -0000

On Apr 24, 2014, at 5:44 PM, Scott Kitterman <scott@kitterman.com> =
wrote:

> On Friday, April 25, 2014 02:26:22 Martin Rex wrote:
> ...
>> The DMARC policy scheme is actually censoring of a telecommunication
>> between a messge sender and a message receiver through a =
telecommunications
>> provider by some _outside_ third party.  So in the US a p=3Dreject =
DMARC
>> policy might potentially be freedom of speech (1st Amendment) =
violation.
>=20
> No idea about the rest of it, but this is nonsense.  The 1st Amendment =
to the=20
> constitution is a restriction on government action, not on private =
action. =20
> See http://xkcd.com/1357/ .

Dear Scott,

Strongly disagree.  The US government failed to protect citizen's rights =
by not declaring ISPs common carriers.  People's ability to meet and =
freely associate is now being steadily eroded by policies hostile to =
decades of neighborhood and small communities' normal meeting practices. =
This has nothing to do with someone being abusive and shunned.  This is =
about ISPs taking greater control over content carried on the Internet.  =
The usurping of control over Internet use is very likely to put =
democracy in greater peril as content control is taken over by an =
oligarchy.

The TPA scheme would have allowed DMARC to shun abusers without =
impacting perfectly legitimate communication methods being used in =
support of our growing communities.

Regards,
Douglas Otis=20


From nobody Thu Apr 24 18:50:46 2014
Return-Path: <scott@kitterman.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EBD31A03BA for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 18:50:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Level: 
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_16=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 B6tb0LJE5saQ for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 18:50:36 -0700 (PDT)
Received: from mailout03.controlledmail.com (mailout03.controlledmail.com [208.43.65.50]) by ietfa.amsl.com (Postfix) with ESMTP id 81C041A03BC for <ietf@ietf.org>; Thu, 24 Apr 2014 18:50:36 -0700 (PDT)
Received: from mailout03.controlledmail.com (localhost [127.0.0.1]) by mailout03.controlledmail.com (Postfix) with ESMTP id 15F7AD0453D; Thu, 24 Apr 2014 21:50:30 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kitterman.com; s=2014-01; t=1398390630; bh=EZgoSC1OCJCezUf6VNUN63bCdHw+Yop3VX0KfBnwNAk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=3DeZAw0BuGcG5w2FbAtgJ9Tx8a1ZlI5Y7PDboviAHl4t5+OCoMnA0Vh+Ipv5NZdj5 nYcWaVeLmx9y+XUXg2NFX0/G3TQtkVxx4GHdqv4MZW4ViLsxUMEuQmlBWTeJ6txLmz S5CmFyiqPWYqsdY7x78VdVHPcaVLYrx2bErU754A=
Received: from scott-latitude-e6320.localnet (63-253-113-202.ip.mcleodusa.net [63.253.113.202]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout03.controlledmail.com (Postfix) with ESMTPSA id C2521D04328; Thu, 24 Apr 2014 21:50:29 -0400 (EDT)
From: Scott Kitterman <scott@kitterman.com>
To: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
Date: Thu, 24 Apr 2014 21:50:28 -0400
Message-ID: <1880086.yRGn2NtzXo@scott-latitude-e6320>
User-Agent: KMail/4.13 (Linux/3.13.0-24-generic; KDE/4.13.0; x86_64; ; )
In-Reply-To: <57E35BDB-30DF-4829-A6CE-F1132E0C2EFC@gmail.com>
References: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp> <7859156.ek3Qf5sxiO@scott-latitude-e6320> <57E35BDB-30DF-4829-A6CE-F1132E0C2EFC@gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
X-AV-Checked: ClamAV using ClamSMTP
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/V6H9SDamoGLqTyJ6W-LiqOzJimI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 01:50:43 -0000

On Thursday, April 24, 2014 18:41:12 Douglas Otis wrote:
> On Apr 24, 2014, at 5:44 PM, Scott Kitterman <scott@kitterman.com> wrote:
> > On Friday, April 25, 2014 02:26:22 Martin Rex wrote:
> > ...
> > 
> >> The DMARC policy scheme is actually censoring of a telecommunication
> >> between a messge sender and a message receiver through a
> >> telecommunications
> >> provider by some _outside_ third party.  So in the US a p=reject DMARC
> >> policy might potentially be freedom of speech (1st Amendment) violation.
> > 
> > No idea about the rest of it, but this is nonsense.  The 1st Amendment to
> > the constitution is a restriction on government action, not on private
> > action. See http://xkcd.com/1357/ .
> 
> Dear Scott,
> 
> Strongly disagree.  The US government failed to protect citizen's rights by
> not declaring ISPs common carriers.  People's ability to meet and freely
> associate is now being steadily eroded by policies hostile to decades of
> neighborhood and small communities' normal meeting practices. This has
> nothing to do with someone being abusive and shunned.  This is about ISPs
> taking greater control over content carried on the Internet.  The usurping
> of control over Internet use is very likely to put democracy in greater
> peril as content control is taken over by an oligarchy.

I didn't say it was a good idea.  I said it wasn't unconstitutional.  No all 
constitutional ideas are good ones.  It's a case of law, not fundamental 
rights.

Scott K


From nobody Thu Apr 24 19:02:22 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84CF21A03F7 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 19:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 QNQL30wfddRz for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 19:02:16 -0700 (PDT)
Received: from smtpde02.sap-ag.de (smtpde02.sap-ag.de [155.56.68.140]) by ietfa.amsl.com (Postfix) with ESMTP id EE7C41A03CB for <ietf@ietf.org>; Thu, 24 Apr 2014 19:02:15 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde02.sap-ag.de (26) with ESMTP id s3P228oN017209 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Apr 2014 04:02:08 +0200 (MEST)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <20140425011716.70436.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
Date: Fri, 25 Apr 2014 04:02:08 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20140425020208.24FB61ACE0@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/sfx93TmoZn15-RvI50n765sCcLU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 02:02:18 -0000

John Levine wrote:
[ Charset UTF-8 unsupported, converting... ]
> >> Can you provide a legal citation?  That would be really cool!
> >
> >1. Blocking EMail based on DMARC policy is illegal per ?206 Abs. 2 Nr. 2 StGB.
> >
> >2. Actually, even looking at rfc5322.From (rather than MAIL FROM:) for
> >   the purpose of looking up DMARC policy records 
> >   is illegal per ?206 Abs. 2 Nr. 1 StGB.
> >
> >3. Any DMARC-triggered reporting about forwarded emails is also illegal
> >   per ?206 Abs. 1 StGB and ?88 TKG.
> 
> If that's true, how can spam filtering be legal?  The phrase "without
> authorization" is pretty elastic, and all the ISPs I know consider themselves
> authorized to mange user mail any way they want.

"without authorization" is a quite well-defined concept in telecommunication
legalese in Europe.  Only the sender, and the recipients specified by the
sender are authorized.  The telecommunications service provider is NOT
authorized, and neither is an employer.

SPAM filtering MUST be implemented as voluntary opt-in, otherwise it will be
illegal, as you correctly notice.  Spam-filtering can only be legal when
it is performed strictly on behalf of the recipient, the receipient is
in full control over the behaviour all the time, and the blocking or
deletion of any messages is performed with explicit and voluntary
(i.e. condition-free) consent of the receipient himself.

A preselection to tag Mails as potential spam or to store potential
spam in a second inbox might be permissible, a preselection to block
or delete potential spam would certainly be illegal.


-Martin


From nobody Thu Apr 24 19:10:45 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC4D1A03CB for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 19:10:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 Ih_nwLXPoGCC for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 19:10:40 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5531D1A02CF for <ietf@ietf.org>; Thu, 24 Apr 2014 19:10:40 -0700 (PDT)
Received: (qmail 74903 invoked from network); 25 Apr 2014 02:10:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=12495.5359c418.k1404; bh=6XkWkKQgAkYiA6nR4JKq4fmmA0ijqDUPl6mWdlnQgKo=; b=B4uMhSBXwc9GLYSZ4QbQqW/ZxZBUeRyY9t4wHHYM7kq1vZeh7AYVgJN6SG63QkM/F1FaXIu/8cCwOC2To3Ov7BTCCNYlnqLnWA7FkHu5jHkoVNEtKKjW2U29dw7RcNoSmKRX6/lYG/VkoN7rPI0l/OweejgEq2m64rIj72jxbWWCw7nn5ZlFBHQUIULJnkTw6Pz5UeT7BfqGSYXAiNALAoz25f2Bo+u5Maj4HIaOt7rc2ODoRANH90Sni8HcrACx
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=12495.5359c418.k1404; bh=6XkWkKQgAkYiA6nR4JKq4fmmA0ijqDUPl6mWdlnQgKo=; b=vXIHKtcMBu/LhhziTI3PFF03Tb/MJ7ijjzUMJKYryUaLB415VCC7SkTeoJx+ArNsbLyv++VeaN92uYrZcklhInrNEz2WCV1Jq+rV8pM9lyRew4gUQnlqOaquUlc1X29HvwEbi2o3OXmdDH2j3Su+OR6WyyxRQpzx3ntbFazBrspNyi3inb3I+x+TpRG5UT9pHpXOv0azIg96BmYB+foiSNJp1/dJIcG9ixlWi74KAa5D17daaTLiFMa2bH0TCnt+
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 25 Apr 2014 02:10:32 -0000
Date: 24 Apr 2014 22:10:31 -0400
Message-ID: <alpine.BSF.2.00.1404242208020.36815@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Martin Rex" <mrex@sap.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <20140425020208.24FB61ACE0@ld9781.wdf.sap.corp>
References: <20140425020208.24FB61ACE0@ld9781.wdf.sap.corp>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lckm83J2JJ7AiycIhnurOi9h4h0
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 02:10:41 -0000

> SPAM filtering MUST be implemented as voluntary opt-in, otherwise it will be
> illegal, as you correctly notice.  Spam-filtering can only be legal when
> it is performed strictly on behalf of the recipient, the receipient is
> in full control over the behaviour all the time, and the blocking or
> deletion of any messages is performed with explicit and voluntary
> (i.e. condition-free) consent of the receipient himself.

If that were true, there would be no Gmail, Hotmail, or Yahoo mail users 
in Germany, since they offer only limited control over spam filtering, and 
some stuff, e.g. DNSBL blocks, is unconditional.

I expect that the mail systems make it a condition of subscription that 
the recipients consent to the mail system doing whatever it has to do to 
filter incoming mail.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Thu Apr 24 19:24:54 2014
Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C93C81A02D4 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 19:24:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.172
X-Spam-Level: 
X-Spam-Status: No, score=-2.172 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 ssN5FIXgWjcE for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 19:24:51 -0700 (PDT)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 797A51A028F for <ietf@ietf.org>; Thu, 24 Apr 2014 19:24:51 -0700 (PDT)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 6FE7A1B8087 for <ietf@ietf.org>; Thu, 24 Apr 2014 19:24:45 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 339EB19005C; Thu, 24 Apr 2014 19:24:45 -0700 (PDT)
Received: from [10.0.10.40] (192.168.1.10) by CAS-02.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 24 Apr 2014 19:24:44 -0700
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <57E35BDB-30DF-4829-A6CE-F1132E0C2EFC@gmail.com>
Date: Thu, 24 Apr 2014 22:23:58 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <DC6E3687-2567-42D3-B6E3-B594132A3BCD@nominum.com>
References: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp> <7859156.ek3Qf5sxiO@scott-latitude-e6320> <57E35BDB-30DF-4829-A6CE-F1132E0C2EFC@gmail.com>
To: Douglas Otis <doug.mtview@gmail.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/F82uKIaJA44zqtW6pVMdU-5ecXk
Cc: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 02:24:53 -0000

On Apr 24, 2014, at 9:41 PM, Douglas Otis <doug.mtview@gmail.com> wrote:
> The US government failed to protect citizen's rights by not declaring =
ISPs common carriers.

Is this conversation really appropriate for the IETF mailing list?


From nobody Thu Apr 24 20:17:19 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CEF41A02F4 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 20:17:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.226
X-Spam-Level: ****
X-Spam-Status: No, score=4.226 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HK_SCAM_N13=3.1, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 VE1gmGrhC9Ky for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 20:17:12 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9611A0107 for <ietf@ietf.org>; Thu, 24 Apr 2014 20:17:12 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P71CGZK25C00084M@mauve.mrochek.com> for ietf@ietf.org; Thu, 24 Apr 2014 20:12:02 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P714CWLY4W000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 24 Apr 2014 20:11:57 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P71CGX4VD8000052@mauve.mrochek.com>
Date: Thu, 24 Apr 2014 19:45:02 -0700 (PDT)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-reply-to: "Your message dated Tue, 22 Apr 2014 15:50:39 -0700" <5356F23F.40909@dougbarton.us>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us>
To: Doug Barton <dougb@dougbarton.us>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Uw1bdiNkhv_MgAbTB2y09axhttM
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 03:17:13 -0000

> On 04/18/2014 05:33 PM, Ned Freed wrote:
> >> On 04/18/2014 07:47 AM, Ned Freed wrote:
> >>>> I said: Rather than throwing up our hands and telling the DMARC
> >>>> folks that we refuse to work with them unless their solution
> >>>> solves the problem of our anachronistic use case that that
> >>>> constitutes only a tiny percentage of their overall traffic;
> >>>
> >>> Again with the traffic size as justification for poor behavior.
> >>> Not all messages are created equal, and some functions have
> >>> utility entirely disproportionate to the amount of bandwidth they
> >>> use.
> >
> >> Right, so the input here from the operators is, "Mailing list
> >> traffic is not important enough to us to prevent us from deploying
> >> an anti-spam solution that solves the vast majority of our problems
> >> with little cost or difficulty. The MLM software authors will have
> >> to deal with this problem on their end." And your response is to
> >> stamp your feet and shout, "But my mailing list traffic IS
> >> important! It is, IT IS!!!!!"
> >
> > I really have to wonder where you got enough straw to build a
> > strawman of this size. If you actually, you know, read what I've been
> > saying, it has been that this was handled extremely poorly by the
> > IETF. Just not in the way you happen to believe.
> >
> > Your view of what happened, who the operators actually are and what
> > their positions are, and what the likely consequences are going to be
> > are somewhere between a gross oversimplifications and looney tunes.
> > But I must say they are amusing.

> First, I acknowledge that you seem to be interested in addressing the
> IETF's failings, the problem is that small matter of disagreement on
> what those failings are. You say that my version of events is "looney
> tunes," and yet there is "rough consensus and running code" backing it
> up.

What is this "rough consensus and running code of which you speak?" My
understanding of that phrase has always been that it refers to the assessment
of documents within the IETF process. Exactly how is that supposed to apply
to independent documents such as this one?

And if you're talking about there being a consensus among serevice providers
regarding the use of p=reject in the fashion of AOL and Yahoo, I've seen
absolutely no evidence of that. Indeed, I've seen exactly the opposite. Our
customers tend to be very large concerns, and while I cannot get into specifics
for obvious reasons, I can assure you that they are not all hunkey-dorey with
what Yahoo and AOL are doing.

> Even before AOL joined the p=reject team, but much more so now.

Seriously? A move by a single provider, now joined by another, represents some
sort of industry consensus?

> It's incredibly obvious that the IETF either didn't listen to, or didn't
> act on clear messages from the operator community on this topic.

Well, here I sort of agree. What the IETF didn't do is react to the danger this
posed in a timely way. Either on a technical or political level.

> Trying
> to re-paint the failure as one of process (or whatever weird rathole you
> appear to be willing to travel) doesn't help the situation at all.

And that means... what, exactly? Of course fixing process issues after the fact
aren't going to help the present situation any.

> For this issue what would help is for the IETF to admit its failure, and
> take in hand the problem of solving mailing list delivery for DMARC
> protected domains (along with the MLM software authors of course). If
> there are other places where DMARC has weaknesses that can be shored up,
> let's tackle those too.

Again, what part of "unwilling to make any changes" did you not understand?

> What won't help is sitting on the sidelines and whinging that the "DMARC
> cabal" "doesn't get it" and has to listen to us about how it should
> conduct their business.

Of course it wouldn't help. Which is why I never did that.

> Because not only do they clearly not have to do
> that, they are not doing it. You will see more and more large mail
> providers implementing p=reject because it's good for them, and the
> fallout from Yahoo!'s implementation has been marginal (from their
> perspective).

I have no doubt that some other providers who have mixed business transaction
mail on the same domain with personal email will follow suit. I'm skeptical
this will extend to those like Google who have kept them separate, or providers
that focus on providing personal mail accounts.

Only time will tell.

>  From a larger perspective it would be very useful for the IETF to take
> this message to heart in other areas, like say ... DHCPv6. But I digress. :)

> > Wrong again. The evidence shows clearly that the IETF did listen, to
> >  this group at least. Where the IETF failed was in not looking at the
> > big picture and likely consequences, which I'm afraid is not laid out
> > along the axis of "big operators all supporting DMARC" versus "tiny
> > insignificant list maintainer stick-in-the-muds".

> I'm not sure who you're defining as "the IETF" in this context, but the
> record seems to show that there was a non-zero number of people telling
> the DMARC folks that their spec should not be implemented because it
> doesn't solve the mailing list problem, among others. So rather than
> listening to the operators and working to solve the MLM problem, there
> was whinging, and intransigence. I don't care how you want to
> characterize the problem, the failures of communication and inaction are
> pretty clear.

Suffice it to say I don't see it that way.

And with this reply I'm done with this conversation. You have a view of the
email world as well as the events that have transpired that is so completely at
odds with reality that this is no point in further discussion with you.

				Ned


From nobody Thu Apr 24 20:26:15 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B3A71A0439 for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 20:26:12 -0700 (PDT)
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] autolearn=ham
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 JOK6PLFsQ51Z for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 20:26:10 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 933BF1A02F9 for <ietf@ietf.org>; Thu, 24 Apr 2014 20:26:10 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3P3Q02Z022953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 24 Apr 2014 20:26:03 -0700
Message-ID: <5359D543.5070900@dcrocker.net>
Date: Thu, 24 Apr 2014 20:23:47 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ned+ietf@mauve.mrochek.com, Doug Barton <dougb@dougbarton.us>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com>
In-Reply-To: <01P71CGX4VD8000052@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Thu, 24 Apr 2014 20:26:03 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zz9UQhitillhAo2cetGA23ZlHHo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 03:26:12 -0000

On 4/24/2014 7:45 PM, ned+ietf@mauve.mrochek.com wrote:
>> It's incredibly obvious that the IETF either didn't listen to, or
>> didn't act on clear messages from the operator community on this
>> topic.
>
> Well, here I sort of agree. What the IETF didn't do is react to the
> danger this posed in a timely way. Either on a technical or political
> level.


The fundamental flaw in this sort of view is that the IETF initiates 
organization efforts. Or that it acts on "messages".  It doesn't.  It 
provides an environment for workers from the community to organize open 
standards efforts.

In other words, the failure is of the industry to formulate an effort 
and bring it to the IETF.  Other than SPF, DKIM and DMARC, of course, 
which have variously been brought to the IETF.  (I'm not trying to 
re-open a debate on the details of those three, but merely to note that 
they are examples.)

Were there examples of efforts to bring work to the IETF and have it be 
rejected, that might be the IETF's 'fault'.  DMARC is the closest 
example to that and, as has been thoroughly hashed and re-hashed, it did 
not match the usual IETF model for doing work.

So sorry, but no, there have been essentially no 'clear messages from 
the operator community' and more importantly, no /efforts/ other than 
SPF, DKIM and DMARC.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Thu Apr 24 20:55:05 2014
Return-Path: <mrex@sap.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B39B21A02ED for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 20:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.552
X-Spam-Level: 
X-Spam-Status: No, score=-6.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 nXhIOo5gSqsm for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 20:54:58 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by ietfa.amsl.com (Postfix) with ESMTP id 15C401A0115 for <ietf@ietf.org>; Thu, 24 Apr 2014 20:54:57 -0700 (PDT)
Received: from mail05.wdf.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id s3P3soRq022082 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 25 Apr 2014 05:54:50 +0200 (MEST)
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
In-Reply-To: <alpine.BSF.2.00.1404242208020.36815@joyce.lan>
To: John R Levine <johnl@taugh.com>
Date: Fri, 25 Apr 2014 05:54:50 +0200 (CEST)
X-Mailer: ELM [version 2.4ME+ PL125 (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="ISO-8859-1"
Message-Id: <20140425035450.7400C1ACE0@ld9781.wdf.sap.corp>
From: mrex@sap.com (Martin Rex)
X-SAP: out
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OYxBAxdl4_0hPUZAm1rmarCRUBQ
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: mrex@sap.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 03:54:59 -0000

John R Levine wrote:
>
>> SPAM filtering MUST be implemented as voluntary opt-in, otherwise it wil=
l be
>> illegal, as you correctly notice.  Spam-filtering can only be legal when
>> it is performed strictly on behalf of the recipient, the receipient is
>> in full control over the behaviour all the time, and the blocking or
>> deletion of any messages is performed with explicit and voluntary
>> (i.e. condition-free) consent of the receipient himself.
>=20
> If that were true, there would be no Gmail, Hotmail, or Yahoo mail users=
=20
> in Germany, since they offer only limited control over spam filtering, an=
d=20
> some stuff, e.g. DNSBL blocks, is unconditional.

Why?  Germans are allowed to use/subscribe to services that hosted/operated
outside of Europe and under foreign jurisdiction, i.e. without the
protections that European and national jurisdiction provides.
But we do not have to.  So it would be unreasonable to do so,
where viable local alternatives exist.  But certainly it is permitted.


>=20
> I expect that the mail systems make it a condition of subscription that=
=20
> the recipients consent to the mail system doing whatever it has to do to=
=20
> filter incoming mail.

What telecommunication service providers can legally offer depends on the
jurisdiction under which they're operating.

Fortunately our legislators are not that naive.  The statue explicitly says,
that pretty much all such "under the condition" consent agreements signed by
the subscriber will be legally void.  (=A795 Abs. 5 TKG)


Under German jurisdiction, at least, telecommunication service providers
that (a) offer their services to the public and (b) connect to public
communication networks and (c) enable communication between at least
one of their own subscribers and any public communication networks
becomes subject to the exact same regulations as all big TelCos,
and MUST respect the protection of the telecommunication privacy for
*ALL* of their subscribers and all communications between subscribers
(own subscribers as well as subscribers of other service providers).


-Martin


From nobody Thu Apr 24 21:53:20 2014
Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA2361A02ED for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 21:53:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.773
X-Spam-Level: 
X-Spam-Status: No, score=-5.773 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 KmlAneOXiAxr for <ietf@ietfa.amsl.com>; Thu, 24 Apr 2014 21:53:13 -0700 (PDT)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 20B2F1A0323 for <ietf@ietf.org>; Thu, 24 Apr 2014 21:53:13 -0700 (PDT)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Fri, 25 Apr 2014 00:53:06 -0400
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 25 Apr 2014 00:53:05 -0400
Received: from b01cxnp23034.gho.pok.ibm.com (b01cxnp23034.gho.pok.ibm.com [9.57.198.29]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 5375338C804F for <ietf@ietf.org>; Fri, 25 Apr 2014 00:53:04 -0400 (EDT)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp23034.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s3P4r4UN54984868 for <ietf@ietf.org>; Fri, 25 Apr 2014 04:53:04 GMT
Received: from d01av01.pok.ibm.com (localhost [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s3P4r3O3010353 for <ietf@ietf.org>; Fri, 25 Apr 2014 00:53:04 -0400
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.222.27]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s3P4r3ZT010335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 25 Apr 2014 00:53:03 -0400
Received: from rotala.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by rotala.raleigh.ibm.com (8.14.7/8.12.5) with ESMTP id s3P4r3jo015064 for <ietf@ietf.org>; Fri, 25 Apr 2014 00:53:03 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s3P4r2FB015025 for ietf@ietf.org; Fri, 25 Apr 2014 00:53:02 -0400
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201404250453.s3P4r2FB015025@rotala.raleigh.ibm.com>
Date: Fri, 25 Apr 2014 00:53:02 -0400
To: ietf@ietf.org
Subject: Weekly posting summary for ietf@ietf.org
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14042504-7182-0000-0000-00000A6E30F3
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MHoJN6w6kQOUcOgT6CrGkmmsMrg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 04:53:17 -0000

Total of 150 messages in the last 7 days.
 
script run at: Fri Apr 25 00:53:02 EDT 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.00% |   15 |  9.52% |   117575 | ned+ietf@mauve.mrochek.com
  8.00% |   12 |  7.05% |    87042 | johnl@taugh.com
  6.67% |   10 |  7.03% |    86794 | superuser@gmail.com
  7.33% |   11 |  5.60% |    69076 | dhc@dcrocker.net
  4.67% |    7 |  6.28% |    77524 | doug.mtview@gmail.com
  4.67% |    7 |  4.43% |    54625 | mfidelman@meetinghouse.net
  4.67% |    7 |  3.82% |    47095 | tytso@mit.edu
  4.67% |    7 |  3.61% |    44576 | mrex@sap.com
  3.33% |    5 |  3.72% |    45920 | sm+ietf@elandsys.com
  3.33% |    5 |  3.67% |    45292 | john-ietf@jck.com
  3.33% |    5 |  3.57% |    44027 | hsantos@isdg.net
  3.33% |    5 |  3.30% |    40684 | presnick@qti.qualcomm.com
  3.33% |    5 |  3.01% |    37095 | dougb@dougbarton.us
  3.33% |    5 |  2.78% |    34340 | scott@kitterman.com
  2.67% |    4 |  3.02% |    37327 | bclaise@cisco.com
  2.67% |    4 |  2.55% |    31465 | brian.e.carpenter@gmail.com
  2.00% |    3 |  2.57% |    31778 | mhammer@ag.com
  2.00% |    3 |  2.08% |    25651 | ynir.ietf@gmail.com
  1.33% |    2 |  2.23% |    27554 | lrosen@rosenlaw.com
  1.33% |    2 |  1.46% |    17973 | listsebby@me.com
  1.33% |    2 |  1.40% |    17322 | hallam@gmail.com
  1.33% |    2 |  1.39% |    17137 | tony.putman@alcatel-lucent.com
  1.33% |    2 |  1.09% |    13510 | dcrocker@bbiw.net
  0.67% |    1 |  1.47% |    18168 | mitch@telmate.com
  0.67% |    1 |  1.18% |    14514 | abdussalambaryun@gmail.com
  0.67% |    1 |  1.14% |    14133 | andy@yumaworks.com
  0.67% |    1 |  1.05% |    12918 | douglasroyer@gmail.com
  0.67% |    1 |  0.98% |    12055 | r.e.sonneveld@sonnection.nl
  0.67% |    1 |  0.94% |    11622 | tnadeau@lucidvision.com
  0.67% |    1 |  0.90% |    11072 | narten@us.ibm.com
  0.67% |    1 |  0.76% |     9372 | l.wood@surrey.ac.uk
  0.67% |    1 |  0.70% |     8622 | franck@peachymango.org
  0.67% |    1 |  0.68% |     8401 | huitema@microsoft.com
  0.67% |    1 |  0.62% |     7675 | jaltman@secure-endpoints.com
  0.67% |    1 |  0.60% |     7427 | aldrin.ietf@gmail.com
  0.67% |    1 |  0.51% |     6254 | jari.arkko@piuha.net
  0.67% |    1 |  0.50% |     6195 | randy_presuhn@mindspring.com
  0.67% |    1 |  0.50% |     6183 | paf@frobbit.se
  0.67% |    1 |  0.49% |     6023 | ted.lemon@nominum.com
  0.67% |    1 |  0.47% |     5822 | martin.thomson@gmail.com
  0.67% |    1 |  0.46% |     5636 | hartmans-ietf@mit.edu
  0.67% |    1 |  0.45% |     5575 | randy@psg.com
  0.67% |    1 |  0.44% |     5377 | chair@ietf.org
--------+------+--------+----------+------------------------
100.00% |  150 |100.00% |  1234426 | Total


From nobody Thu Apr 24 22:30:32 2014
Return-Path: <peter@akayla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B286D1A030B; Thu, 24 Apr 2014 22:30:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 DN7jsYcV5HsT; Thu, 24 Apr 2014 22:30:26 -0700 (PDT)
Received: from p3plsmtpa06-04.prod.phx3.secureserver.net (p3plsmtpa06-04.prod.phx3.secureserver.net [173.201.192.105]) by ietfa.amsl.com (Postfix) with ESMTP id AD8071A02F9; Thu, 24 Apr 2014 22:30:26 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by p3plsmtpa06-04.prod.phx3.secureserver.net with  id u5WG1n00F1huGat015WHe1; Thu, 24 Apr 2014 22:30:19 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-eastlake-iana-cfm-considerations.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-eastlake-iana-cfm-considerations-01
Date: Thu, 24 Apr 2014 22:30:22 -0700
Message-ID: <009d01cf6047$760de3c0$6229ab40$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac9gNrW6VZ0N8bbSRQGXqYGcN4aAIQ==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XK92pGYLi4-ciA1ToLOuIbSywy8
Cc: gen-art@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 05:30:28 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>

Please resolve these comments along with any other Last Call comments you
may receive.

Document: draft-eastlake-iana-cfm-considerations-01
Reviewer: Peter Yee
Review Date: April-24-2014
IETF LC End Date: May-21-2014
IESG Telechat date: TBD

Summary: This draft is basically ready for publication as a Best Current
Practice, but has some nits that should be fixed before publication. [Ready
with nits.]

This document provides the IANA Considerations for two registries covering
the IEEE Std 802.1Q-2011 CFM OpCode and TLV Type blocks assigned to the
IETF.

Nits:

Most comments that follow are for alignment with the terminology and usage
found in IEEE Std 802.1Q-2011.

General: globally replace "Continuity" with "Connectivity".

General: globally replace "Codepoints" with "Code Points".

General: globally replace "Op-Code" with "OpCode".

Page 3, 2nd paragraph, 2nd sentence: change "IANA Consideration" to "IANA
Considerations".

Page 5, 1st paragraph: end the reference with a period.

Page 5, 2nd paragraph: replace "Mansfield, S." with "and S. Mansfield" to
match http://www.rfc-editor.org/in-notes/rfc-ref.txt.  Hey, I'm running out
of nits to pick here. :-)

		-Peter Yee



From nobody Fri Apr 25 02:13:23 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDE391A020C for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 02:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 AfD-iSnqqHKR for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 02:13:15 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id B3E0E1A02D0 for <ietf@ietf.org>; Fri, 25 Apr 2014 02:13:15 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id rd3so2955919pab.37 for <ietf@ietf.org>; Fri, 25 Apr 2014 02:13:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Lr0n+UsvNRlesrAfTv2BH0U6t4SR7wwdJGYiRE/BJGs=; b=AEKsy4xWqthsAufvxE1rAZ0VVKd1ZQVdeXmTn9qUEOS96LAlY25iCjFzEOoAsaVsnA tjAaiXYLAzggVcXgt0JRpcMB0PjOwws7DQGsHBj8+/DrRXhP+U2xGkLlf76nV/8rRqxt HLOGdhS+D0e563il1TKrpWjOVwL+2fRdiKFln7jCaTTDGYQoFLpiiOwJ4GCPm+KwauI7 EV2aViSIxj0Wy5oV18n9h4q2sFNjhacrlZ1AkTBZ2nKHbw9y8BziIMGXHWuPgWkhgHbd WvWWnlS1wad1MRqSlwzxuBkk91BEC0iaHoytg2y3C7nUaAGU2jqvLQUG3hZdzsvYHi6E C5pQ==
X-Received: by 10.66.160.34 with SMTP id xh2mr6364459pab.109.1398417189472; Fri, 25 Apr 2014 02:13:09 -0700 (PDT)
Received: from [192.168.1.150] (c-24-4-159-60.hsd1.ca.comcast.net. [24.4.159.60]) by mx.google.com with ESMTPSA id z3sm35012186pas.15.2014.04.25.02.13.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Apr 2014 02:13:07 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <DC6E3687-2567-42D3-B6E3-B594132A3BCD@nominum.com>
Date: Fri, 25 Apr 2014 02:13:07 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B627E61C-D207-4932-A6A4-BB611505FC0B@gmail.com>
References: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp> <7859156.ek3Qf5sxiO@scott-latitude-e6320> <57E35BDB-30DF-4829-A6CE-F1132E0C2EFC@gmail.com> <DC6E3687-2567-42D3-B6E3-B594132A3BCD@nominum.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rHmbC9bdQgnoK3y9fNWuT2589sg
Cc: Scott Kitterman <scott@kitterman.com>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 09:13:19 -0000

On Apr 24, 2014, at 7:23 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> On Apr 24, 2014, at 9:41 PM, Douglas Otis <doug.mtview@gmail.com> =
wrote:
>> The US government failed to protect citizen's rights by not declaring =
ISPs common carriers.
>=20
> Is this conversation really appropriate for the IETF mailing list?

Dear Ted,

Protocols related to pervasive monitoring, reduced security, or granting =
overwhelming control to a select few at an expense of many should be =
valid topics within the IETF.  These larger questions can and should =
provide some guidance in setting group priorities.

Regards,
Douglas Otis=


From nobody Fri Apr 25 03:28:57 2014
Return-Path: <chair@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A32F1A03A6 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 03:28:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.799
X-Spam-Level: 
X-Spam-Status: No, score=0.799 tagged_above=-999 required=5 tests=[BAYES_50=0.8, SPF_PASS=-0.001] autolearn=unavailable
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 EqcBrBtNwKmX for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 03:28:53 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 10BFD1A0380 for <ietf@ietf.org>; Fri, 25 Apr 2014 03:28:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id A727B1E1890; Fri, 25 Apr 2014 03:27:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BhISl2prsDgZ; Fri, 25 Apr 2014 03:27:39 -0700 (PDT)
Received: from [172.17.149.25] (unknown [179.189.232.26]) by c8a.amsl.com (Postfix) with ESMTPSA id 0C7541E12A7; Fri, 25 Apr 2014 03:27:38 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: NetMundial
From: IETF Chair <chair@ietf.org>
In-Reply-To: <9E6B5379-FD6C-4034-810B-348E95E7E2CF@ietf.org>
Date: Fri, 25 Apr 2014 07:28:44 -0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <D48E26F2-A3B2-434E-9D30-FFD7D0A2CEF3@ietf.org>
References: <9E6B5379-FD6C-4034-810B-348E95E7E2CF@ietf.org>
To: "internetgovtech@iab.org" <internetgovtech@iab.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/n29cH_3zmJ4vqYiGaryv0OhZ5QU
Cc: "ietf@ietf.org List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 10:28:54 -0000

An outcome document can be found here: =
http://netmundial.br/wp-content/uploads/2014/04/NETmundial-Multistakeholde=
r-Document.pdf

This is the result of a panel editing a draft, based on discussions =
before and during the meeting.=20

I will post more information and some of my own observations about this =
topic in the next couple of days.

Jari Arkko
IETF Chair


From nobody Fri Apr 25 05:27:59 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F1421A0191 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 05:27:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.101
X-Spam-Level: 
X-Spam-Status: No, score=-98.101 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_45=0.6, J_CHICKENPOX_46=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 j7qlmO2KleZo for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 05:27:54 -0700 (PDT)
Received: from groups.winserver.com (mail.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 918611A048C for <ietf@ietf.org>; Fri, 25 Apr 2014 05:27:53 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3678; t=1398428860; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:Subject:To: List-ID; bh=v+/2a0b2n5xP8vwgtkPNgAUplHY=; b=XT6lMZnmXYuk+N/GoPFi J65ePuJdnkgnX4sW4ApyRRGcOYQVFCe9mf8qWr3AHuNvGG6NSZ7PTT59P9oChQnM y9nOoRjPvRaBNnxbJrGY8EcZdx+1nu/KuXQO867nBC0qQ4jG3m9SxwQgFthy+fXa 9vefy6pZNRd/SzQ+YbFogaE=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 25 Apr 2014 08:27:40 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1537426903.3014.2720; Fri, 25 Apr 2014 08:27:39 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3678; t=1398428773; h=Received:Received: Message-ID:Date:From:Organization:Subject:To:List-ID; bh=BBatvhs 5ec151egT11S3zLjreT1y7iB63wNkIGkfhyQ=; b=AKQj9bA3IlxeeNtt1qU3YC7 0Jg8iEuAEK92YizRmwLIiyJ6G/OuNIWU5toIYTAKJ8NU4GqsfYo9dfUh/gGb4neV CgIK0Dm2PyNknm9tHab7Ds6sl8f4WAIvOZs/6vnubBOYxl1vVTrq+WBHdCFjTKVz 1QM7Qfxy8IbY/XerAZUY=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 25 Apr 2014 08:26:13 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1556949359.9.13572; Fri, 25 Apr 2014 08:26:12 -0400
Message-ID: <535A54BB.2020506@isdg.net>
Date: Fri, 25 Apr 2014 08:27:39 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net>
In-Reply-To: <5359D543.5070900@dcrocker.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Comment: Missing recipient address appended by wcSMTP router.
To: ietf@ietf.org
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vKGNTFwN-d8tV0UTB2i-DnsUEQ0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 12:27:57 -0000

On 4/24/2014 11:23 PM, Dave Crocker wrote:
> On 4/24/2014 7:45 PM, ned+ietf@mauve.mrochek.com wrote:
>>> It's incredibly obvious that the IETF either didn't listen to, or
>>> didn't act on clear messages from the operator community on this
>>> topic.
>>
>> Well, here I sort of agree. What the IETF didn't do is react to the
>> danger this posed in a timely way. Either on a technical or political
>> level.
>
>
> The fundamental flaw in this sort of view is that the IETF initiates
> organization efforts. Or that it acts on "messages".  It doesn't.  It
> provides an environment for workers from the community to organize
> open standards efforts.
>
> In other words, the failure is of the industry to formulate an effort
> and bring it to the IETF.  Other than SPF, DKIM and DMARC, of course,
> which have variously been brought to the IETF.  (I'm not trying to
> re-open a debate on the details of those three, but merely to note
> that they are examples.)
>
> ....
>
> So sorry, but no, there have been essentially no 'clear messages from
> the operator community' and more importantly, no /efforts/ other than
> SPF, DKIM and DMARC.
>

Dave, you were involved in all this.  You resisted POLICY and threw 
out ADSP, yet you supported DMARC without resolving any of the exact 
policy concerns involving middle ware.

Your approach was to just allow the problem to continue to exist as if 
it was only a small use case.  You blindly and also intentionally and 
neglectfully ignored everything that had to do with this issue.  You 
told others to also ignore these concerns. Yet, you are now promoting 
DMARC which has the same exact problem.  It doesn't make any sense.

No, I'm sorry to say. you can't push this issue on any one else but 
yourself.  You were the KEY COG in this entire DKIM+POLICY+TRUST 
effort.  But you  didn't CHAMPION POLICY, nor did the author of ADSP 
and it suffered the consequences.  You can't expect high quality in 
work when the author doesn't champion his own work.  When others cited 
interest to take it over, it was ignored as well.  We can blames the 
chairs and ADs of the DKIM-WG too for allowing this to happen.

All the concerns, desires, integration issues, are in the archives and 
also in I-Ds and also RFCs.  Instead, you had a policy of intentional 
ignorance, filtering mail you just didn't wish to read.  Not important 
in your book. You also used INFORMATIONAL non-wg fast tracked 
documents to change proposed standard track items and the course of 
their WG direction, in the case of ADSP - down the tubes.  You made it 
historic. Perhaps millions of combine IETF-MAN-YEARS wasted down the 
tubes, and for what?  To get DMARC which had the same 3rd party 
signature problem that you desperately need to get working in order 
for the DKIM+TRUST framework to work.  You don't need to explain 
yourself but please don't you dare put this on others in the 
community, including myself, who worked hard for the past 9+ years on 
all this and yes even implemented all these protocols with "running 
code" only for you to say, it doesn't matter, too small, lets get rid 
of it!!

Ok, put all that past stuff away. What are you going to do NOW!?  How 
are you going to help lead the way?  If not, you need to allow others 
begin to solve the problem without all this interfering philosophical 
b-llsh-t that has held back the IETF DKIM+POLICY efforts and hurt its 
reputation - big time.   You are a highly respected person, but you 
were completely wrong with how your were pushing DKIM.  You didn't 
help with its original policy framework and now DMARC has forced the 
issue.  What are you going to do now?

-- 
HLS



From nobody Fri Apr 25 08:14:23 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CEAB1A02A6 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.174
X-Spam-Level: 
X-Spam-Status: No, score=-2.174 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 lKVQAHM3NtJi for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:14:19 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id AF3671A0300 for <ietf@ietf.org>; Fri, 25 Apr 2014 08:14:19 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P721I1GFRK00091L@mauve.mrochek.com> for ietf@ietf.org; Fri, 25 Apr 2014 08:09:09 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P714CWLY4W000052@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Fri, 25 Apr 2014 08:09:00 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P721HY5XZO000052@mauve.mrochek.com>
Date: Fri, 25 Apr 2014 07:56:54 -0700 (PDT)
Subject: The IETF environment (was: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists)
In-reply-to: "Your message dated Thu, 24 Apr 2014 20:23:47 -0700" <5359D543.5070900@dcrocker.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net>
To: Dave Crocker <dhc@dcrocker.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5YgEOLzL1lTBf02zJO3pUO5lkO8
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 15:14:21 -0000

I'm done with the original thread on this topic, but there's a bit here that
warrants a separate response.

> On 4/24/2014 7:45 PM, ned+ietf@mauve.mrochek.com wrote:
> >> It's incredibly obvious that the IETF either didn't listen to, or
> >> didn't act on clear messages from the operator community on this
> >> topic.
> >
> > Well, here I sort of agree. What the IETF didn't do is react to the
> > danger this posed in a timely way. Either on a technical or political
> > level.

> The fundamental flaw in this sort of view is that the IETF initiates
> organization efforts. Or that it acts on "messages".  It doesn't.  It
> provides an environment for workers from the community to organize open
> standards efforts.

You may want to argue that's how the IETF should work, but I'm afraid I don't
see it matching up with how it actually works.

An obvious counterexample is what recently happened in perpass and the various
works it has started. Regardless of what anyone thinks of perpass or its
outcome, a fair characterization is that it was an IETF repsonse to the
message delivered by Snoden et al.

And maybe something has changed since the four years I spent going to IESG
retreats, but I recall lots of discussion of how the IETF as an organization
should respond to various industry trends.

Now, I suppose you could characterize both of these as "people  coming together
to work on stuff", with the IETF just providing the environment. But it seems
pretty clear that people regard the IETF as a bit more than that. Maybe they
shouldn't, but they do.

				Ned


From nobody Fri Apr 25 08:24:18 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C2681A050E for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:24:12 -0700 (PDT)
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] autolearn=ham
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 Qiw38h6n6qRT for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:24:08 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 598FD1A0345 for <ietf@ietf.org>; Fri, 25 Apr 2014 08:24:08 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3PFNvWp004240 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 25 Apr 2014 08:24:01 -0700
Message-ID: <535A7D87.6080200@dcrocker.net>
Date: Fri, 25 Apr 2014 08:21:43 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com>
In-Reply-To: <01P721HY5XZO000052@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 25 Apr 2014 08:24:01 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xk72xDH3_TVxRAlV8UAozSiVkyM
Cc: ned+ietf@mauve.mrochek.com, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 15:24:12 -0000

On 4/25/2014 7:56 AM, Ned Freed wrote:
> An obvious counterexample is what recently happened in perpass and
> the various works it has started. Regardless of what anyone thinks of
> perpass or its outcome, a fair characterization is that it was an
> IETF repsonse to the message delivered by Snoden et al.

Yup.  It's a singular example, but that's the point.  It's not what the 
IETF (usually) does.

It's fine that it's being attempted and it might (or might not) prove 
useful.  But there is no pattern of the IETF doing such a thing.

My point was not meant as a statement of philosophy or criticism of the 
IETF, but a description of the long-term operational model that covers 
its actual history.

That model is for initiatives to come from the grass roots of the 
community, seeking facilitation within the IETF.  These do not depend 
upon strategic management directions being set.


> And maybe something has changed since the four years I spent going to
> IESG retreats, but I recall lots of discussion of how the IETF as an
>  organization should respond to various industry trends.

Yes, we often have such discussions.  My observation is that it has 
typically had little or no effect on what work is actually done, absent 
initiative from the community.

With respect to getting work done, this is a bottom-up organization, not 
a top-down one.  (That's why I think Area "Director" is a serious 
misnomer and Area "Facilitator" would be far more accurate.)


>  But it seems pretty clear that people regard the IETF as
> a bit more than that. Maybe they shouldn't, but they do.

Yes, there is quite a bit of mythology about the IETF.  Sometimes it 
borders on mysticism...

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Apr 25 08:32:04 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 037271A031A for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:32:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 5_n6Jfh_6a4m for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:32:01 -0700 (PDT)
Received: from asmtp4.iomartmail.com (asmtp4.iomartmail.com [62.128.201.175]) by ietfa.amsl.com (Postfix) with ESMTP id DDFCE1A02E4 for <ietf@ietf.org>; Fri, 25 Apr 2014 08:32:00 -0700 (PDT)
Received: from asmtp4.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3PFVqXN014325 for <ietf@ietf.org>; Fri, 25 Apr 2014 16:31:53 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp4.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3PFVoPg014258 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Fri, 25 Apr 2014 16:31:50 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net>
In-Reply-To: <535A7D87.6080200@dcrocker.net>
Subject: RE: The IETF environment
Date: Fri, 25 Apr 2014 16:31:47 +0100
Message-ID: <054a01cf609b$7a186450$6e492cf0$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQMYynDcUJdmzo2382SfaGT/uBNq1QHbApq8AuyDjpgCbJF5BgIK8uviAlNsxYUB9LjA+gH5v3C6AcaDqyIDkMbF3wGF+wG1AjYi1SkCjhMJ9gJu3sI4AkBU67ACH7HBigJ8C6NYAoohJMuXV+UUEA==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1017-20654.007
X-TM-AS-Result: No--0.003-10.0-31-10
X-imss-scan-details: No--0.003-10.0-31-10
X-TMASE-MatchedRID: cgbqQT5W8hdzgDEqoQageksRvyNDI5heGSqdEmeD/nUJW4Re2U2pywN1 up/aduX0L0s35rGGaw713CZJV94f5avO4E+4XCpCbBu6+EIezdwHdYH++bm0GJnWR7UNiELsQAf vkuM3e6yXixFTPTh0Lm8ekbfXCYUOLlr/gbBDYhZ7k1ZHmKLF7fadpZP6uSy6pK7cHOZhIcyjxY yRBa/qJX3mXSdV7KK4OubYLCVnBVFYF3qW3Je6+2+pbyDFVnffKFDzvCzFnhZPakhP93vnRwf9g SlRzNPeyHkrXVXA9+nT1r5/YLbiGqe1E7P+EoeIn+Dfa8UvAl2tJG3bt/GS1U3+9BzFCkVzNAW8 3zYDw/v1OlCIPxKfizngMRAgrdeEPYigHtZ0QM5+3BndfXUhXQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9QnLpMcytMQdgmeBV01PNTVOWys
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 15:32:03 -0000

This is a handy thread and brings into question what the 'S' in IESG is supposed
to mean.

On the whole I take it as Dave to mean that the IESG should facilitate. That may
mean spotting when people have focus and energy for a topic and helping to put
them together and make space for the work. But it also may mean spotting when
work "needs to be done" and encouraging people to get together to do that work.

(Internet Engineering Spotter Group?)

Adrian

> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Dave Crocker
> 
> My point was not meant as a statement of philosophy or criticism of the
> IETF, but a description of the long-term operational model that covers
> its actual history.
> 
> That model is for initiatives to come from the grass roots of the
> community, seeking facilitation within the IETF.  These do not depend
> upon strategic management directions being set.

> With respect to getting work done, this is a bottom-up organization, not
> a top-down one.  (That's why I think Area "Director" is a serious
> misnomer and Area "Facilitator" would be far more accurate.)


From nobody Fri Apr 25 08:56:47 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E77361A03B3 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:56:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 SZzjI5gi4ulH for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 08:56:43 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id C29611A032D for <ietf@ietf.org>; Fri, 25 Apr 2014 08:56:43 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id D0687CC09F for <ietf@ietf.org>; Fri, 25 Apr 2014 11:56:34 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id mTX7EBmAP8Wi for <ietf@ietf.org>; Fri, 25 Apr 2014 11:56:26 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 03DEACC09B for <ietf@ietf.org>; Fri, 25 Apr 2014 11:56:25 -0400 (EDT)
Message-ID: <535A85A9.4030609@meetinghouse.net>
Date: Fri, 25 Apr 2014 11:56:25 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net>
In-Reply-To: <535A7D87.6080200@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tHbZKD4dRTMT9YZfBtRkcMLVjmM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 15:56:45 -0000

Dave Crocker wrote:
>
> With respect to getting work done, this is a bottom-up organization, 
> not a top-down one.  (That's why I think Area "Director" is a serious 
> misnomer and Area "Facilitator" would be far more accurate.)
>
>>  But it seems pretty clear that people regard the IETF as
>> a bit more than that. Maybe they shouldn't, but they do.
>
> Yes, there is quite a bit of mythology about the IETF.  Sometimes it 
> borders on mysticism...
>
Bottom up is generally a good thing, and that's certainly been IETF's 
traditional modus operandi.  But... in that IETF is the official 
standard body for the Internet - and it's ultimately the standards that 
hold the Internet together -- isn't the real discussion about:

1. Are the emerging scale, scope, complexity, and issues involved in 
Internet operation/management/<your favorite term> highlighting the 
limits of that bottom-up (or perhaps, arms-length) approach to the way 
IETF is playing its role?

2. Are there changes needed?

Miles Fidelman



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Apr 25 09:05:34 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58B551A0653 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 09:05:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 hdapuxJxJPoP for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 09:05:29 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 04BBA1A0652 for <ietf@ietf.org>; Fri, 25 Apr 2014 09:05:18 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 20CE9CC0B3 for <ietf@ietf.org>; Fri, 25 Apr 2014 12:05:12 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id KQYDoS8x969B for <ietf@ietf.org>; Fri, 25 Apr 2014 12:05:03 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 4C50ECC0B0 for <ietf@ietf.org>; Fri, 25 Apr 2014 12:05:03 -0400 (EDT)
Message-ID: <535A87AF.8080000@meetinghouse.net>
Date: Fri, 25 Apr 2014 12:05:03 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net>
In-Reply-To: <535A7D87.6080200@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BiOZIgPRJQRXNArGay4tx2E-VLg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 16:05:30 -0000

Dave Crocker wrote:
> On 4/25/2014 7:56 AM, Ned Freed wrote:
>> An obvious counterexample is what recently happened in perpass and
>> the various works it has started. Regardless of what anyone thinks of
>> perpass or its outcome, a fair characterization is that it was an
>> IETF repsonse to the message delivered by Snoden et al.
>
> Yup.  It's a singular example, but that's the point.  It's not what 
> the IETF (usually) does.
>

Silly question, but perhaps relevant in the context of the IANAxfr 
discussions:
So, a lot of what IANA does is covered by an MOU between IETF and IANA.  
What happens if IANA doesn't honor it's end of the MOU?  I don't believe 
it has any recourse measures spelled out.  Beyond that, how would "the 
IETF" actually notice and respond? (Both informally and formally.)

Seems to be another example of a key role that belongs to the IETF that 
contrasts a bit with its historical way of operating.

Miles Fidelman



-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Apr 25 09:18:11 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 822E81A0682 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 09:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.419
X-Spam-Level: **
X-Spam-Status: No, score=2.419 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 v0AfV7o6d1Fc for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 09:18:06 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 8CA9F1A06DB for <ietf@ietf.org>; Fri, 25 Apr 2014 09:17:01 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id AC142CC09F for <ietf@ietf.org>; Fri, 25 Apr 2014 12:16:54 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WnfjKyKanvMK for <ietf@ietf.org>; Fri, 25 Apr 2014 12:16:47 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id A3EAECC09B for <ietf@ietf.org>; Fri, 25 Apr 2014 12:16:47 -0400 (EDT)
Message-ID: <535A8A6F.3040903@meetinghouse.net>
Date: Fri, 25 Apr 2014 12:16:47 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp>
In-Reply-To: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qz1ZienWvnGrPtSxlOupWcqwOP8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 16:18:08 -0000

Thanks for the citation!  Also see below...

Martin Rex wrote:
> Miles Fidelman wrote:
>> Martin Rex wrote:
>>> In case you didn't know or realize, what DMARC specifies for p=reject
>>> is actually a real felony crime in Germany (no kidding!), and this may
>>> apply to all over Europe (since the basic idea was spread out all over
>>> europe with a EU directive), unless each individual receipient(!!) has
>>> explicitly opted-in for this to happen.  It should be fairly easy
>>> to get a cease-and-desist order against European ISPs for blocking
>>> EMail on DMARC p=reject.
>> Can you provide a legal citation?  That would be really cool!
> 1. Blocking EMail based on DMARC policy is illegal per Â§206 Abs. 2 Nr. 2 StGB.
>
> 2. Actually, even looking at rfc5322.From (rather than MAIL FROM:) for
>     the purpose of looking up DMARC policy records
>     is illegal per Â§206 Abs. 2 Nr. 1 StGB.
>
> 3. Any DMARC-triggered reporting about forwarded emails is also illegal
>     per Â§206 Abs. 1 StGB and Â§88 TKG.
>
> And while I'm currently not sure whether the first two are similar
> all over europe, the last one DEFINITELY is under the current EU data
> protection directive.
>
> Technically, EMail is an issue between a sender of a telecommunication,
> a receiver of a telecommunication and a telecommunication service provider.
>
> If an MTA is relaying (or delivering to a mailbox), then the sender is
> whoever talks at the other end of the TCP connection that is used to
> transfer the EMail to the MTA on port 25.  The receiver is what is
> named by the sender in the RCPT TO: command (the mail contents is off limits),
> and the MTA is an agent of the telecommunications provider.
>
> What appears in the rfc5322.from of the message is legally, none of the
> MTAs business.  And even if is be an attribution of authorship
> of some third party in rfc5322.from, this party has absolutely no say
> in what contents sender transfers to receiver.  It is also illegal
> for the telecommunications service provider to reveal the fact of
> this communication to other parties. This even applies to failed
> communication attempts.  The only party to which the telecommunications
> provider would be allowed to report a failed delivery is the address
> (if any) supplied by the sender (i.e. the MAIL FROM: envelope address).
>
>
>>   From where I sit, it also looks like a violation of the US Computer
>> Fraud and Abuse Act (effectively, knowingly causing damage to other
>> systems - which has been applied to DDoS attacks).  But I haven't heard
>> any lawyers or prosecutors stand up and confirm that.
>
> The DMARC policy scheme is actually censoring of a telecommunication
> between a messge sender and a message receiver through a telecommunications
> provider by some _outside_ third party.  So in the US a p=reject DMARC policy
> might potentially be freedom of speech (1st Amendment) violation.
>
Not 1st amendment - as others pointed out, it's not an action of Government.

To elaborate on the CFAA, however - I copied this from: 
http://www.technicallylegal.org/the-legality-of-denial-of-service-attacks/ 
-- it's from a discussion of what laws might apply against a DDoS 
attack, but it sure seems to sound like what those who set DMARC 
p=reject are doing:


In terms of criminal violations, thereâ€™s the Computer Fraud and Abuse 
Act <http://en.wikipedia.org/wiki/Computer_fraud_and_abuse_act> (the 
â€œCFAAâ€�), which prohibits a person from â€œknowingly caus[ing] the 
transmission of a program, information code, or command, and as a result 
of such conduct, intentionally causes damages without authorization to a 
protected computerâ€� (see 18 U.S.C. Â§ 1030(a)(5)(A) 
<http://www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00001030----000-.html#a_5>). 
The requisite â€œdamageâ€� element under the CFAA is â€œany impairment to the 
integrity or availability of data, a program, a system, or informationâ€� 
(see 18 U.S.C. Â§ 1030(e)(8) 
<http://www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00001030----000-.html#e_8>) 
and a â€œprotected computerâ€� is defined as a computer â€œwhich is used in or 
affecting interstate or foreign commerce, including a computer located 
outside the United States that is used in a manner that affects 
interstate or foreign commerce or communicationâ€� (see 18 U.S.C. Â§ 
1030(e)(2)(B) 
<http://www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00001030----000-.html#e_2>). 


DoS attacks almost unquestionably fall under the broadly-worded 
prohibited activity in this portion of the CFAA (â€œtransmitting â€¦ 
information, code, or commandâ€�) and would likely meet the low standard 
of damage (â€œany impairment to the integrity or availability of data, 
program, system, or informationâ€�). The CFAA may also apply to 
unsuccessful attempts (see 18 U.S.C. Â§ 1030(b) 
<http://www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00001030----000-.html#b>).

The CFAA also has a civil component that permits â€œ[a]ny person who 
suffers damage or loss by reason of a violation of this section may 
maintain a civil action against the violator to obtain compensatory 
damages and injunction relief.â€� In other words, the target of the DoS 
attack can sue the individual(s) who were responsible for the damages 
incurred as a result of the attack (e.g., server downtime, costs to 
repair, and in some lost revenue (see 18 U.S.C. Â§ 1030(g) 
<http://www.law.cornell.edu/uscode/html/uscode18/usc_sec_18_00001030----000-.html#g>). 
There is a limitation that requires the damages exceed $5,000; however, 
some courts have liberally construed its calculation to include 
consultation services (e.g., IT/security persons) used to assess the 
extent of damage caused by the attack.  Also, this provision does not 
require that a person ever be convicted before being sued for damages.

--------
That last paragraph kinda makes me think about a civil lawsuit :-)




-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Fri Apr 25 09:40:11 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A60C1A0639 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 09:40:08 -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, SPF_PASS=-0.001] autolearn=ham
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 GUKpQ0xUeF9C for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 09:40:05 -0700 (PDT)
Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) by ietfa.amsl.com (Postfix) with ESMTP id 19B111A0649 for <ietf@ietf.org>; Fri, 25 Apr 2014 09:40:04 -0700 (PDT)
Received: by mail-wi0-f169.google.com with SMTP id hm4so2915211wib.2 for <ietf@ietf.org>; Fri, 25 Apr 2014 09:39:58 -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:content-type; bh=vvkbVywF2fho44se30WocC2KI5pUZ88i4B8MiTFIuAI=; b=foVWvSrTb8o/jBX86iSiesNZEt/symOjG8REoZzvePwYvH/xsuNI9FYgydKo8nZyYP N3cVLBL9w97q0foLsWYUraBvR4gnZyAYgOZPNZmolF8tNrUkJL2dC7YUEgJqw0qlz/n+ OgGDdmPFh89D7nYGT7SMpkCz0/qi8cfCFeupckKmxbWQa2e6aQU28XX08oNcIUbmv7bC 5DyvPGmI/Pzuu5c+QQpSEwHhENZ6Fk+PnRtJsaJ7cd1Wx2R9HwEQK4Ju6UVx28eRN3H8 /w818IXgYzrUgHlTFm2r4VLn0BHEX6IZrCFeuRBDnHPBrpm+KYvvm5TEALheqYj9/ZO3 OvrA==
MIME-Version: 1.0
X-Received: by 10.180.218.35 with SMTP id pd3mr4512137wic.26.1398443578378; Fri, 25 Apr 2014 09:32:58 -0700 (PDT)
Received: by 10.180.210.194 with HTTP; Fri, 25 Apr 2014 09:32:58 -0700 (PDT)
In-Reply-To: <535A8A6F.3040903@meetinghouse.net>
References: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp> <535A8A6F.3040903@meetinghouse.net>
Date: Fri, 25 Apr 2014 09:32:58 -0700
Message-ID: <CAL0qLwbLpaKXggK5EpF1XtDYXCvs9K5cqUHo-tDZQFN=TO6QYw@mail.gmail.com>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=001a113467fcba90cf04f7e08497
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rRI8GWkNES5MFLfXB5U9JO0jlbc
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 16:40:08 -0000

--001a113467fcba90cf04f7e08497
Content-Type: text/plain; charset=UTF-8

On Fri, Apr 25, 2014 at 9:16 AM, Miles Fidelman
<mfidelman@meetinghouse.net>wrote:

> Thanks for the citation!  Also see below...


I'm just curious: Is anyone on this thread a lawyer?

-MSK

--001a113467fcba90cf04f7e08497
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Fri, Apr 25, 2014 at 9:16 AM, Miles Fidelman <span dir=
=3D"ltr">&lt;<a href=3D"mailto:mfidelman@meetinghouse.net" target=3D"_blank=
">mfidelman@meetinghouse.net</a>&gt;</span> wrote:<br><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Thanks for the citation! =C2=A0Also see belo=
w...</blockquote><div><br></div><div>I&#39;m just curious: Is anyone on thi=
s thread a lawyer?<br>
<br></div><div>-MSK<br></div></div></div></div>

--001a113467fcba90cf04f7e08497--


From nobody Fri Apr 25 09:53:01 2014
Return-Path: <lrosen@rosenlaw.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D4811A0584 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 09:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.033
X-Spam-Level: *
X-Spam-Status: No, score=1.033 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, SPF_PASS=-0.001] autolearn=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 syhfJHzGIOfs for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 09:52:56 -0700 (PDT)
Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) by ietfa.amsl.com (Postfix) with SMTP id 8CCE31A031E for <ietf@ietf.org>; Fri, 25 Apr 2014 09:52:56 -0700 (PDT)
Received: (qmail 32224 invoked by uid 0); 25 Apr 2014 16:52:45 -0000
Received: from unknown (HELO cmgw4) (10.0.90.85) by gproxy4.mail.unifiedlayer.com with SMTP; 25 Apr 2014 16:52:45 -0000
Received: from box597.bluehost.com ([66.147.242.197]) by cmgw4 with  id uGsa1n0054GF2VN01GsdSk; Fri, 25 Apr 2014 10:52:45 -0600
X-Authority-Analysis: v=2.1 cv=CpMsLBID c=1 sm=1 tr=0 a=NRJ8aB/FPT4S3utBguGD+g==:117 a=NRJ8aB/FPT4S3utBguGD+g==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=qDS3CPt326AA:10 a=7xXQEuv9rCMA:10 a=CAIbOuo8jNoA:10 a=IkcTkHD0fZMA:10 a=4F77bVRYAAAA:8 a=FxJxCPAPh0wA:10 a=AqkBdCNi7UMA:10 a=pGLkceISAAAA:8 a=WOIJDy4HAAAA:8 a=rwmqMtevH814MOuPN5kA:9 a=VISYv2K6WGP9cvje:21 a=eqsGZhTbB-JAwZBo:21 a=QEXdDO2ut3YA:10 a=SqxYWZjetj4A:10 a=TImqNlVd7iMA:10 a=MSl-tDqOz04A:10 a=B0a0FVVDmlMA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=rosenlaw.com; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From:Reply-To; bh=/JQfQOMDTIxJIzKNZyRJW/NmmZ4LSjsNG5LO9sUyfGY=;  b=Z2TcWzeY6YHOKdSU4Bdi4GSg7He+EwLEgtulim82rZx/zKLGXhCTAtPnDcKbNA/JOp8eKKiFWZZZbwSO7esIWaczqZb1+X/5DqSk5jkjytGK466bZ6hoG8dM4869bajb;
Received: from [70.36.224.178] (port=53849 helo=Lawrencei) by box597.bluehost.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from <lrosen@rosenlaw.com>) id 1WdjMT-0002lk-BF; Fri, 25 Apr 2014 10:52:29 -0600
From: "Lawrence Rosen" <lrosen@rosenlaw.com>
To: "'IETF'" <ietf@ietf.org>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>	<CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com>	<037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com> <CAMm+LwhO4a3=O_=xp4Ge8AsFFXnojdH=YKQNoQRsGXiMr88e+g@mail.gmail.com>
In-Reply-To: <CAMm+LwhO4a3=O_=xp4Ge8AsFFXnojdH=YKQNoQRsGXiMr88e+g@mail.gmail.com>
Subject: RE: Author disclosures and conflict of interest
Date: Fri, 25 Apr 2014 09:52:27 -0700
Message-ID: <04ae01cf60a6$bf805510$3e80ff30$@rosenlaw.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQKXcE4LMzjvYQvi+4zFEB3vA0KOeQJHdvB/AVPihlICWIgRzJliyg4g
Content-Language: en-us
X-Identified-User: {1397:box597.bluehost.com:rosenla1:rosenlaw.com} {sentby:smtp auth 70.36.224.178 authed with lrosen@rosenlaw.com}
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/udn77PjdXsj6hRkZM9xOXfbdMRA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: lrosen@rosenlaw.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 16:52:58 -0000

Phillip Hallam-Baker asked:
> So there is only one set of ethical rules for scientists and engineers =
then?

Of course not. But before you reject the ethical rules proposed by the =
National Academies (of Science, Engineering, Medicine, and the National =
Research Council), you ought to have a better argument than "I don't =
wanna...."

This attitude, unfortunately, diminishes respect for IETF and its =
standards. And nothing confirms that disrespect better than the almost =
complete silence here whenever topics such as this are brought up. It is =
as if IETF standards are generated in an ethical vacuum where "caveat =
emptor" prevails.=20

/Larry


-----Original Message-----
From: Phillip Hallam-Baker [mailto:hallam@gmail.com]=20
Sent: Thursday, April 24, 2014 1:54 PM
To: Lawrence Rosen
Cc: IETF
Subject: Re: Author disclosures and conflict of interest

So there is only one set of ethical rules for scientists and engineers =
then?

Thats news to me.

On Thu, Apr 24, 2014 at 2:35 PM, Lawrence Rosen <lrosen@rosenlaw.com> =
wrote:
> Phillip Hallam-Baker wrote:
>> Like the question 'are you a spy' which they used to ask when people=20
>> entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc =
problem.
>
> The question actually is: Do you agree to the ethical rules for =
scientists and engineers?
>
> By the way, those ethical rules require only disclosure, not recusal.
>
> /Larry
>
>
> -----Original Message-----
> From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
> Sent: Monday, April 21, 2014 2:05 PM
> To: lrosen@rosenlaw.com
> Cc: IETF Discussion Mailing List
> Subject: Re: Author disclosures and conflict of interest
>
> Like the question 'are you a spy' which they used to ask when people =
entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc =
problem.
>
> The people who are being paid to subvert the standards aren't going to =
say.
>
> They might not even know that the objective is subversion.
>
>
> Like many IETF participants I have substantial financial interests in =
several Internet companies besides my employer. Am I meant to put those =
in a blind trust?
>
> And even if I did all that people would still assume that I am working =
as an agent of the New World Order. Though quite how the other folk on =
the conference call worked out that the helicopter is black still =
puzzles me.
>
>
> On Sun, Apr 20, 2014 at 1:18 PM, Lawrence Rosen <lrosen@rosenlaw.com> =
wrote:
>> I=E2=80=99ve been skimming recent threads  on this list relating to =
work done=20
>> (or not done) at IETF and was reminded of this from Science Magazine:
>>
>>
>>
>> Authorship Form and Conflict-of-Interest Statement
>>
>> To meet its responsibility to readers and to the public to provide=20
>> clear and unbiased scientific results and analyses, Science believes=20
>> that manuscripts (including Brevia, Essays, Perspectives, Policy=20
>> Forums, Reports, Research Articles, Reviews, and Viewpoints) should=20
>> be accompanied by clear disclosures from all authors of the nature=20
>> and level of their contribution to the article, their understanding=20
>> regarding the obligation to share data and materials, and any=20
>> affiliations, funding sources, or financial holdings that might raise =

>> questions about possible sources of bias. Before manuscript=20
>> acceptance, therefore, authors will be asked to sign an=20
>> authorship/conflict-of-interest form. Specific information will be =
sent to most authors at the time of manuscript revision.
>>
>> Authorship Form and Statement of Conflicts of Interest [PDF]
>>
>>
>>
>> Part IV regarding =E2=80=9CConflict of Interest=E2=80=9D is =
particularly relevant to=20
>> standards organizations such as IETF. Such a disclosure requirement=20
>> would further encourage everyone to trust and implement IETF =
specifications.
>>
>>
>>
>> This document follows the recommendations in On Being a Scientist: A=20
>> Guide to Responsible Conduct in Research, The National Academies=20
>> Press, Third Edition (2009).
>>
>>
>>
>> /Larry
>>
>>
>>
>> Lawrence Rosen
>>
>> Rosenlaw & Einschlag (www.rosenlaw.com)
>>
>> 3001 King Ranch Road, Ukiah, CA 95482
>>
>> Cell: 707-478-8932   Fax: 707-485-1243
>>
>>
>
>
>
> --
> Website: http://hallambaker.com/
>



--
Website: http://hallambaker.com/


From nobody Fri Apr 25 10:10:49 2014
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AEB61A0275; Thu, 24 Apr 2014 08:46:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham
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 bjSJdSYwEDbq; Thu, 24 Apr 2014 08:46:36 -0700 (PDT)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 3F1DD1A020F; Thu, 24 Apr 2014 08:46:36 -0700 (PDT)
Received: from aither.local (unknown [24.8.129.242]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id B374340427; Thu, 24 Apr 2014 09:46:27 -0600 (MDT)
Message-ID: <535931D3.1060002@stpeter.im>
Date: Thu, 24 Apr 2014 09:46:27 -0600
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: [precis] Last Call: <draft-ietf-precis-framework-15.txt> (PRECIS Framework: Preparation and Comparison of Internationalized Strings in Application Protocols) to Proposed Standard
References: <20140409190744.15518.7195.idtracker@ietfa.amsl.com> <6C520F47E0BA6CEF00EF649B@JcK-HP8200.jck.com>
In-Reply-To: <6C520F47E0BA6CEF00EF649B@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/M140lwubnatDPdpt_aZExeYM6F4
X-Mailman-Approved-At: Fri, 25 Apr 2014 10:10:44 -0700
Cc: precis@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2014 15:46:39 -0000

On 4/23/14, 10:17 PM, John C Klensin wrote:
>
>
> --On Wednesday, April 09, 2014 12:07 -0700 The IESG
> <iesg-secretary@ietf.org> wrote:
>
>> The IESG has received a request from the Preparation and
>> Comparison of Internationalized Strings WG (precis) to
>> consider the following document: - 'PRECIS Framework:
>> Preparation and Comparison of Internationalized    Strings in
>> Application Protocols'
>>    <draft-ietf-precis-framework-15.txt> as Proposed Standard
>>
>> The IESG plans to make a decision in the next few weeks, and
>> solicits final comments on this action. Please send
>> substantive comments to the ietf@ietf.org mailing lists by
>> 2014-04-23.
>
> IESG,
>
> I have deliberately waited until the end of the Last Call period
> as posted [1], hoping that you would get (or generate) more
> focused comments on the draft in the interim.

John, that seems like an exceedingly unrealistic hope. You know better 
than anyone that internationalization expertise is spread very thinly in 
the IETF (and elsewhere). Folks from the IETF community who care about 
i18n are already likely to have provided feedback on the PRECIS 
documents. We just don't have very many such people.

> The issues
> discussed in this note were raised while what became the PRECIS
> WG (originally known by names like "Stringprep-bis") was being
> discussed and chartered and again on several occasions during
> the meetings of the WG.   At least in my opinion, they were
> never discussed seriously: the WG made one important improvement
> (shifting to a rule-based inclusion approach) but has
> essentially ignored the fundamental problem.  Because the
> predecessors of this note have not been actively considered in
> the WG or while its charter was being created, I don't actually
> expect it to accomplish anything other than to get some issues
> on the record.  But I think the circumstances require one last
> try.

Ignored might be a bit strong. Perhaps those active in the WG did not 
see a way to achieve the high goal you have set here. Throwing up our 
hands and doing nothing (and thus remaining stuck on Stringprep and 
Unicode 3.2) seems like it would have been a worse outcome.

> This note consists of a high-level summary with details in
> footnotes on its various points.  It is as short as I cam make
> it without leaving out issues and explanations that I believe
> are important.
>
> Summary:
>
> I see fundamental problems with approval of this specification
> and some issues with the decisions it includes.  The first of
> these is temporary; the second more fundamental.
>
> (1) After the PRECIS WG task list settled down into its charter
> [2], the goal became, in essence, to replace Stringprep with
> something more explicitly rule-based and to update (or advise
> on) the various uses of Stringprep profiles.  As described in
> the PRECIS charter, that approach noted the relationships among
> the various parts of the PRECIS work and called for handling the
> "framework, profile replacements, and guidelines ... in parallel
> as much as possible".  The interrelated nature of the pieces
> makes it inappropriate for the IESG to approve the "framework"
> document for publication on the standards track at this time
> because doing so would foreclose some reasonable discussion of
> issues with the other specs -- exactly the situation the charter
> language was intended, at least in my recollection, to prevent.
> The approval and publication of RFC 6885 over a year ago has
> already been used that way.
>
> Some of the decisions reflected in the current draft
> illustration why more testing against specific profile examples
> and guidelines is important [5].

We have 5 profiles in a quite advanced state, specified in 3 I-Ds 
(draft-ietf-precis-saslprepbis, draft-ietf-

> Recommendation: Tentatively approve the document now if that
> seems otherwise justified (I suggest below that it is not) but
> do not issue a Protocol Action Notice or handoff to the RFC
> Editor until after a sufficient number of of "profile
> replacements" and "guidelines" have been completed and examined
> through the IETF Last Call process to validate the "framework"
> provisions.  The analogy of such a request to "running code"
> requirements should be obvious.

IMHO we are close to having that running code, but we haven't pushed all 
the documents forward at exactly the same time.

> (2) The longer-term problem is the one that PRECIS simply
> refused to address.

It's a hard problem. Refused might be a bit strong.

> When designing systems with direct effects
> on and interactions with users, predictability based on prior
> user experience and expectations is vital.  That predictability
> is often expressed as the Law of Least Astonishment.  In the
> case of use of non-ASCII characters in Internet applications,
> "least astonishment" implies, first, that rules should be
> intuitive and easily understood to the extent possible.  Second
> and more important, if a user understands the rules of one
> application, she should be able to accurately extrapolate from
> that application to others.  If there is a reason why that
> extrapolation does not work, the reasons should be clearly
> expressed and sufficiently comprehensible to be easily
> incorporated into the user's cognitive framework... and there
> should be few such cases.

That sounds ideal, but unfortunately we are dealing with a quite messy 
reality in which we have many different kinds of identifiers - domain 
names, email addresses, file names, chatrooms, IM handles, nicknames, 
etc. Reducing them all to one thing seems unrealistic to me. I would 
love to achieve that, but I don't see it happening anytime soon.

> With the addition of "IdentifierClass" and "FreeformClass" to
> what, in its language, might be called "IDNA2008Class", we
> already have between one and two "Classes" too many for good
> user predictability.  The language that indicates that
> additional classes might be defined in future specifications is
> not nearly strong enough in discouraging additional classes and
> explaining the reasons why.
>
> The PRECIS framework appears to fail those tests.  It can be
> read as actively encouraging multiple profiles [3].

Because we have a world with multiple identifiers.

> This is
> true even though the third bullet under "It is expected that
> this framework will yield..." explicitly acknowledges "more
> accurate expectations about the characters that are acceptable
> in various contexts" as an explicit objective.
>
> Recommendation: Hold this document until the various categories
> are exercised by at least a sampling of applicable profiles.

See above. We have 5 profiles very close to done.

Also: hold in what sense?

These documents are going forward to Proposed Standard. IMHO we need 
further experience with them, in the field, and possible revision in the 
future. But we have a stronger basis for that now (with PRECIS) than we 
ever would have had with Stringprep.

I think the WG realizes that PRECIS is not perfect as it is. I doubt 
that perfection can be achieved in the messy domain of i18n, though.

> Make the problems with excessive profiles explicit; impose
> requirements on additional profiles that include an explanation
> of why they are needed given the user-level interoperability and
> astonishment problems that can result from even three of them
> and require a higher level of review and consensus for creating
> new ones than "expert review".  Modify the Security
> Considerations section to identify user astonishment and
> consequent confusion about what rules are being applied in a
> given PRECIS-User protocol as a risk and possible attack vector.

Those do seem like good things.

I am out of time right now to reply to the topics from your footnotes.

Peter

>
> thanks,
>      john
>
>    -----------------------------

> [3] Not only should multiple profiles be discouraged for this
> type of case by the Law of Least Astonishment, but general IETF
> experience indicates that profiles are a bad idea and that
> protocols that depend on them (and use a significant variety)
> tend to be less successful than those that do not.
>
> [4] Sections 3.2.2 and 3.3.2 of -15.
>
> [5] There are issues with the two classes that are defined in
> this document that have not, I believe, been carefully addressed
> in the WG.  At a minimum, they need to be considered more
> carefully in context with specific examples without preempting
> the choices to be made for those examples.  The following are
> examples, not an exclusive list:
>
> (i) The "Contextual Rule" categories of IDNA2008 have proven to
> be extremely problematic, confusing, and controversial enough to
> be one of the key issues in the UTR 46 battles that have impeded
> IDNA2008 adoption in some important communities.  While I still
> believe that the IDNA2008 decision was the right one, inclusion
> of those characters as Valid for both classes [4] should, given
> those bad experiences, require significantly more explanation
> and/or justification than this draft appears to provide.  If the
> intent of incorporating this list in PRECIS is to provide for
> compatibility with IDNA2008, the list should be incorporated by
> reference (either to RFC 5892 and its successors or to a
> separate documents that updates and replaces the list in RFC
> 5892 as well as being used for PRECIS),  not be provided as a
> list of code points that could cause the two definitions to
> diverge if changes are made to one or the other.  The issue may
> apply more generally to the other characters listed in Section
> 7.6 and to other IDNA-derived elements of Section 7.
>
> (ii) Characters with compatibility equivalents are problematic,
> in large measure because of a Unicode issue that has been
> extensively discussed in the past.  Basically the compatibility
> equivalency category mixes several unrelated and incompatible
> (sic) groups of things under a single label.  One extreme is
> occupied by characters used with East Asian scripts that are
> distinguished only by their widths.  If the Unicode design
> principles of "characters, not glyphs" and "plain text" had been
> followed, these different-width variations would never have been
> assigned different code points.  As a contrasting example, the
> relevance of, and distinctions among, special mathematical code
> points distinguished by mathematical use and specific type
> styles is less clear: treating them as separate characters may
> be justified under some circumstances.  A more extreme example
> occurs with some Chinese characters that Unicode treats as
> compatibility equivalents for other characters.  That treatment
> is usually (and perhaps always) appropriate when the "meaning"
> of the characters is intended.  But some of those characters
> are, or historically have been, used in personal names.  To the
> extent to which those names are used as identifiers, e.g., for a
> person thus named, treating them as invalid is inappropriate and
> applying a compatibility mapping to them only slightly less bad.
>
> (iii) Experience with IDNA strongly suggests that
> "DefaultIgnorable" is a bad idea.  Forbidding some (or perhaps
> all) of these characters may be reasonable; treating them as if
> they were not present impedes possibly-reasonable future
> extensions and provides an attack vector for phishing and other
> types of unpleasant behavior that do not appear to be called out
> in Security Considerations.  It is also worth noting that one
> difference between IDNA2008 and this specification is that the
> former is not profiled (except by registries providing their own
> subsetting rules) while the latter is intended as a base for
> profiling.  While the order in which categorization rules is
> applied in Section 8 provides some protection (perhaps
> sufficient protection if the spec is never updated or used as
> the basis for a different profile), it is worth noting that some
> code points appear in more than one category (e.g., the
> notorious ZWJ and ZWNJ in both JoinControl (Section 7.8) and
> PrecisIgnorableProperties (Section 7.13)) and that this should
> at least be called out explicitly.
>
>
> _______________________________________________
> precis mailing list
> precis@ietf.org
> https://www.ietf.org/mailman/listinfo/precis
>


From nobody Fri Apr 25 10:11:42 2014
Return-Path: <kivinen@iki.fi>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F5451A04B1; Fri, 25 Apr 2014 05:38:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.173
X-Spam-Level: 
X-Spam-Status: No, score=-2.173 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001] autolearn=ham
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 vQjRtYJ9fi1S; Fri, 25 Apr 2014 05:38:49 -0700 (PDT)
Received: from mail.kivinen.iki.fi (fireball.kivinen.iki.fi [IPv6:2001:1bc8:100d::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6FB9D1A04A8; Fri, 25 Apr 2014 05:38:49 -0700 (PDT)
Received: from fireball.kivinen.iki.fi (localhost [127.0.0.1]) by mail.kivinen.iki.fi (8.14.7/8.14.7) with ESMTP id s3PCbowj029281 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 25 Apr 2014 15:37:50 +0300 (EEST)
Received: (from kivinen@localhost) by fireball.kivinen.iki.fi (8.14.7/8.14.7/Submit) id s3PCbofu022482; Fri, 25 Apr 2014 15:37:50 +0300 (EEST)
X-Authentication-Warning: fireball.kivinen.iki.fi: kivinen set sender to kivinen@iki.fi using -f
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Message-ID: <21338.22302.684230.594132@fireball.kivinen.iki.fi>
Date: Fri, 25 Apr 2014 15:37:50 +0300
From: Tero Kivinen <kivinen@iki.fi>
To: Yoav Nir <ynir.ietf@gmail.com>
Subject: Re: [IPsec] Last Call: <draft-kivinen-ipsecme-ikev2-rfc5996bis-02.txt> (Internet Key Exchange Protocol Version 2 (IKEv2)) to Internet Standard
In-Reply-To: <B12490A2-2D31-4E32-9D9E-ACB80C91FB8C@gmail.com>
References: <20140404202750.31367.2461.idtracker@ietfa.amsl.com> <14BE57EA00BC0C469E17B5AD698FE67766664CE4@FR711WXCHMBA01.zeu.alcatel-lucent.com> <B12490A2-2D31-4E32-9D9E-ACB80C91FB8C@gmail.com>
X-Mailer: VM 8.2.0b under 24.3.1 (x86_64--netbsd)
X-Edit-Time: 1 min
X-Total-Time: 0 min
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fGGBxKmW2BCEnbA8I13aNecySq0
X-Mailman-Approved-At: Fri, 25 Apr 2014 10:11:39 -0700
Cc: "ipsec@ietf.org" <ipsec@ietf.org>, "PUTMAN, Tony \(Tony\)" <tony.putman@alcatel-lucent.com>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 12:38:53 -0000

Yoav Nir writes:
> I assume you mean that you don=E2=80=99t sign with public keys. Repla=
cing
> =E2=80=9Csign=E2=80=9D with =E2=80=9Cvalidate=E2=80=9D makes for a st=
range sentence, because the
> sentence is about sending (and presumably signing) rather than
> receiving (and validating).=20
>=20
> How about:
> =E2=80=9CIf multiple certificate are sent, the first MUST contain the=
 public
> key associated with the private key used to sign the AUTH payload=E2=80=
=9D=20

Changed text to :

If multiple certificates are sent, the first certificate MUST contain
the public key associated with the private key used to sign the AUTH
payload.

--=20
kivinen@iki.fi


From nobody Fri Apr 25 10:18:43 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 804921A0659 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 10:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001] autolearn=ham
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 4gDjY5KDZOuN for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 10:18:36 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.31]) by ietfa.amsl.com (Postfix) with ESMTP id 634491A064B for <ietf@ietf.org>; Fri, 25 Apr 2014 10:18:36 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES533.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Fri, 25 Apr 2014 13:18:29 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: "lrosen@rosenlaw.com" <lrosen@rosenlaw.com>, 'IETF' <ietf@ietf.org>
Subject: RE: Author disclosures and conflict of interest
Thread-Topic: Author disclosures and conflict of interest
Thread-Index: AQHPXaVts8aOHEzuUkCbV4vEa8DWG5shX6aAgAAmuYCAAU7egP//w23Q
Date: Fri, 25 Apr 2014 17:18:28 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D579EC@USCLES544.agna.amgreetings.com>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com> <037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com> <CAMm+LwhO4a3=O_=xp4Ge8AsFFXnojdH=YKQNoQRsGXiMr88e+g@mail.gmail.com> <04ae01cf60a6$bf805510$3e80ff30$@rosenlaw.com>
In-Reply-To: <04ae01cf60a6$bf805510$3e80ff30$@rosenlaw.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.200]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hFL9jF339fZnXw3w4sLscbb9HRY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 17:18:42 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0ZiBbbWFpbHRvOmll
dGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIExhd3JlbmNlIFJvc2VuDQo+IFNlbnQ6
IEZyaWRheSwgQXByaWwgMjUsIDIwMTQgMTI6NTIgUE0NCj4gVG86ICdJRVRGJw0KPiBTdWJqZWN0
OiBSRTogQXV0aG9yIGRpc2Nsb3N1cmVzIGFuZCBjb25mbGljdCBvZiBpbnRlcmVzdA0KPiANCj4g
UGhpbGxpcCBIYWxsYW0tQmFrZXIgYXNrZWQ6DQo+ID4gU28gdGhlcmUgaXMgb25seSBvbmUgc2V0
IG9mIGV0aGljYWwgcnVsZXMgZm9yIHNjaWVudGlzdHMgYW5kIGVuZ2luZWVycyB0aGVuPw0KPiAN
Cj4gT2YgY291cnNlIG5vdC4gQnV0IGJlZm9yZSB5b3UgcmVqZWN0IHRoZSBldGhpY2FsIHJ1bGVz
IHByb3Bvc2VkIGJ5IHRoZQ0KPiBOYXRpb25hbCBBY2FkZW1pZXMgKG9mIFNjaWVuY2UsIEVuZ2lu
ZWVyaW5nLCBNZWRpY2luZSwgYW5kIHRoZSBOYXRpb25hbA0KPiBSZXNlYXJjaCBDb3VuY2lsKSwg
eW91IG91Z2h0IHRvIGhhdmUgYSBiZXR0ZXIgYXJndW1lbnQgdGhhbiAiSSBkb24ndA0KPiB3YW5u
YS4uLi4iDQo+IA0KPiBUaGlzIGF0dGl0dWRlLCB1bmZvcnR1bmF0ZWx5LCBkaW1pbmlzaGVzIHJl
c3BlY3QgZm9yIElFVEYgYW5kIGl0cyBzdGFuZGFyZHMuDQo+IEFuZCBub3RoaW5nIGNvbmZpcm1z
IHRoYXQgZGlzcmVzcGVjdCBiZXR0ZXIgdGhhbiB0aGUgYWxtb3N0IGNvbXBsZXRlDQo+IHNpbGVu
Y2UgaGVyZSB3aGVuZXZlciB0b3BpY3Mgc3VjaCBhcyB0aGlzIGFyZSBicm91Z2h0IHVwLiBJdCBp
cyBhcyBpZiBJRVRGDQo+IHN0YW5kYXJkcyBhcmUgZ2VuZXJhdGVkIGluIGFuIGV0aGljYWwgdmFj
dXVtIHdoZXJlICJjYXZlYXQgZW1wdG9yIg0KPiBwcmV2YWlscy4NCj4gDQo+IC9MYXJyeQ0KPiAN
Cg0KSSB0b29rIHRoZSB0aW1lIHRvIGxvb2sgYXQgdGhlIHdlYnNpdGUgaHR0cDovL3d3dy5vbmxp
bmVldGhpY3Mub3JnLyByZWxhdGVkIHRvIGV0aGljcyBhcyBpbmRpY2F0ZWQgYnkgdGhlIE5hdGlv
bmFsIEFjYWRlbXkgb2YgRW5naW5lZXJpbmcuIEkgZGlkbid0IGZpbmQgYSBjb2RlIG9mIGV0aGlj
cyBmcm9tIHRoZSBBY2FkZW15IGJ1dCBpbnN0ZWFkIGZvdW5kIGxpbmtzIHRvIGEgd2hvbGUgYnVu
Y2ggb2Ygb3RoZXIgc2l0ZXMgLSBodHRwOi8vd3d3Lm9ubGluZWV0aGljcy5vcmcvUmVzb3VyY2Vz
L2V0aGNvZGVzL0VuZ2xpc2hDb2Rlcy5hc3B4LiBUaGUgbmljZSB0aGluZyBhYm91dCBzdGFuZGFy
ZHMgaXMgdGhhdCB0aGVyZSBhcmUgc28gbWFueSB0byBjaG9vc2UgZnJvbS4gVGhlIG5pY2UgdGhp
bmcgYWJvdXQgY29kZXMgb2YgZXRoaWNzIGlzIHRoYXQgdGhlcmUgYXJlIHNvIG1hbnkgdG8gY2hv
b3NlIGZyb20uIFdoaWNoIG9uZSBhcmUgd2Ugc3VwcG9zZWQgdG8gYmUgbG9va2luZyBhdD8NCg0K
TWlrZQ0KDQo+IA0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBQaGlsbGlw
IEhhbGxhbS1CYWtlciBbbWFpbHRvOmhhbGxhbUBnbWFpbC5jb21dDQo+IFNlbnQ6IFRodXJzZGF5
LCBBcHJpbCAyNCwgMjAxNCAxOjU0IFBNDQo+IFRvOiBMYXdyZW5jZSBSb3Nlbg0KPiBDYzogSUVU
Rg0KPiBTdWJqZWN0OiBSZTogQXV0aG9yIGRpc2Nsb3N1cmVzIGFuZCBjb25mbGljdCBvZiBpbnRl
cmVzdA0KPiANCj4gU28gdGhlcmUgaXMgb25seSBvbmUgc2V0IG9mIGV0aGljYWwgcnVsZXMgZm9y
IHNjaWVudGlzdHMgYW5kIGVuZ2luZWVycyB0aGVuPw0KPiANCj4gVGhhdHMgbmV3cyB0byBtZS4N
Cj4gDQo+IE9uIFRodSwgQXByIDI0LCAyMDE0IGF0IDI6MzUgUE0sIExhd3JlbmNlIFJvc2VuIDxs
cm9zZW5Acm9zZW5sYXcuY29tPg0KPiB3cm90ZToNCj4gPiBQaGlsbGlwIEhhbGxhbS1CYWtlciB3
cm90ZToNCj4gPj4gTGlrZSB0aGUgcXVlc3Rpb24gJ2FyZSB5b3UgYSBzcHknIHdoaWNoIHRoZXkg
dXNlZCB0byBhc2sgd2hlbiBwZW9wbGUNCj4gPj4gZW50ZXJlZCB0aGUgVVMsIEkgZmFpbCB0byBz
ZWUgaG93IHRoaXMgaGVscHMgd2l0aCB0aGUgTlNBL0ZTQi9QTEEvZXRjDQo+IHByb2JsZW0uDQo+
ID4NCj4gPiBUaGUgcXVlc3Rpb24gYWN0dWFsbHkgaXM6IERvIHlvdSBhZ3JlZSB0byB0aGUgZXRo
aWNhbCBydWxlcyBmb3Igc2NpZW50aXN0cyBhbmQNCj4gZW5naW5lZXJzPw0KPiA+DQo+ID4gQnkg
dGhlIHdheSwgdGhvc2UgZXRoaWNhbCBydWxlcyByZXF1aXJlIG9ubHkgZGlzY2xvc3VyZSwgbm90
IHJlY3VzYWwuDQo+ID4NCj4gPiAvTGFycnkNCj4gPg0KPiA+DQo+ID4gLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBQaGlsbGlwIEhhbGxhbS1CYWtlciBbbWFpbHRvOmhhbGxh
bUBnbWFpbC5jb21dDQo+ID4gU2VudDogTW9uZGF5LCBBcHJpbCAyMSwgMjAxNCAyOjA1IFBNDQo+
ID4gVG86IGxyb3NlbkByb3Nlbmxhdy5jb20NCj4gPiBDYzogSUVURiBEaXNjdXNzaW9uIE1haWxp
bmcgTGlzdA0KPiA+IFN1YmplY3Q6IFJlOiBBdXRob3IgZGlzY2xvc3VyZXMgYW5kIGNvbmZsaWN0
IG9mIGludGVyZXN0DQo+ID4NCj4gPiBMaWtlIHRoZSBxdWVzdGlvbiAnYXJlIHlvdSBhIHNweScg
d2hpY2ggdGhleSB1c2VkIHRvIGFzayB3aGVuIHBlb3BsZQ0KPiBlbnRlcmVkIHRoZSBVUywgSSBm
YWlsIHRvIHNlZSBob3cgdGhpcyBoZWxwcyB3aXRoIHRoZSBOU0EvRlNCL1BMQS9ldGMNCj4gcHJv
YmxlbS4NCj4gPg0KPiA+IFRoZSBwZW9wbGUgd2hvIGFyZSBiZWluZyBwYWlkIHRvIHN1YnZlcnQg
dGhlIHN0YW5kYXJkcyBhcmVuJ3QgZ29pbmcgdG8gc2F5Lg0KPiA+DQo+ID4gVGhleSBtaWdodCBu
b3QgZXZlbiBrbm93IHRoYXQgdGhlIG9iamVjdGl2ZSBpcyBzdWJ2ZXJzaW9uLg0KPiA+DQo+ID4N
Cj4gPiBMaWtlIG1hbnkgSUVURiBwYXJ0aWNpcGFudHMgSSBoYXZlIHN1YnN0YW50aWFsIGZpbmFu
Y2lhbCBpbnRlcmVzdHMgaW4gc2V2ZXJhbA0KPiBJbnRlcm5ldCBjb21wYW5pZXMgYmVzaWRlcyBt
eSBlbXBsb3llci4gQW0gSSBtZWFudCB0byBwdXQgdGhvc2UgaW4gYSBibGluZA0KPiB0cnVzdD8N
Cj4gPg0KPiA+IEFuZCBldmVuIGlmIEkgZGlkIGFsbCB0aGF0IHBlb3BsZSB3b3VsZCBzdGlsbCBh
c3N1bWUgdGhhdCBJIGFtIHdvcmtpbmcgYXMgYW4NCj4gYWdlbnQgb2YgdGhlIE5ldyBXb3JsZCBP
cmRlci4gVGhvdWdoIHF1aXRlIGhvdyB0aGUgb3RoZXIgZm9sayBvbiB0aGUNCj4gY29uZmVyZW5j
ZSBjYWxsIHdvcmtlZCBvdXQgdGhhdCB0aGUgaGVsaWNvcHRlciBpcyBibGFjayBzdGlsbCBwdXp6
bGVzIG1lLg0KPiA+DQo+ID4NCj4gPiBPbiBTdW4sIEFwciAyMCwgMjAxNCBhdCAxOjE4IFBNLCBM
YXdyZW5jZSBSb3NlbiA8bHJvc2VuQHJvc2VubGF3LmNvbT4NCj4gd3JvdGU6DQo+ID4+IEnigJl2
ZSBiZWVuIHNraW1taW5nIHJlY2VudCB0aHJlYWRzICBvbiB0aGlzIGxpc3QgcmVsYXRpbmcgdG8g
d29yayBkb25lDQo+ID4+IChvciBub3QgZG9uZSkgYXQgSUVURiBhbmQgd2FzIHJlbWluZGVkIG9m
IHRoaXMgZnJvbSBTY2llbmNlIE1hZ2F6aW5lOg0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+PiBBdXRo
b3JzaGlwIEZvcm0gYW5kIENvbmZsaWN0LW9mLUludGVyZXN0IFN0YXRlbWVudA0KPiA+Pg0KPiA+
PiBUbyBtZWV0IGl0cyByZXNwb25zaWJpbGl0eSB0byByZWFkZXJzIGFuZCB0byB0aGUgcHVibGlj
IHRvIHByb3ZpZGUNCj4gPj4gY2xlYXIgYW5kIHVuYmlhc2VkIHNjaWVudGlmaWMgcmVzdWx0cyBh
bmQgYW5hbHlzZXMsIFNjaWVuY2UgYmVsaWV2ZXMNCj4gPj4gdGhhdCBtYW51c2NyaXB0cyAoaW5j
bHVkaW5nIEJyZXZpYSwgRXNzYXlzLCBQZXJzcGVjdGl2ZXMsIFBvbGljeQ0KPiA+PiBGb3J1bXMs
IFJlcG9ydHMsIFJlc2VhcmNoIEFydGljbGVzLCBSZXZpZXdzLCBhbmQgVmlld3BvaW50cykgc2hv
dWxkDQo+ID4+IGJlIGFjY29tcGFuaWVkIGJ5IGNsZWFyIGRpc2Nsb3N1cmVzIGZyb20gYWxsIGF1
dGhvcnMgb2YgdGhlIG5hdHVyZQ0KPiA+PiBhbmQgbGV2ZWwgb2YgdGhlaXIgY29udHJpYnV0aW9u
IHRvIHRoZSBhcnRpY2xlLCB0aGVpciB1bmRlcnN0YW5kaW5nDQo+ID4+IHJlZ2FyZGluZyB0aGUg
b2JsaWdhdGlvbiB0byBzaGFyZSBkYXRhIGFuZCBtYXRlcmlhbHMsIGFuZCBhbnkNCj4gPj4gYWZm
aWxpYXRpb25zLCBmdW5kaW5nIHNvdXJjZXMsIG9yIGZpbmFuY2lhbCBob2xkaW5ncyB0aGF0IG1p
Z2h0IHJhaXNlDQo+ID4+IHF1ZXN0aW9ucyBhYm91dCBwb3NzaWJsZSBzb3VyY2VzIG9mIGJpYXMu
IEJlZm9yZSBtYW51c2NyaXB0DQo+ID4+IGFjY2VwdGFuY2UsIHRoZXJlZm9yZSwgYXV0aG9ycyB3
aWxsIGJlIGFza2VkIHRvIHNpZ24gYW4NCj4gPj4gYXV0aG9yc2hpcC9jb25mbGljdC1vZi1pbnRl
cmVzdCBmb3JtLiBTcGVjaWZpYyBpbmZvcm1hdGlvbiB3aWxsIGJlIHNlbnQgdG8NCj4gbW9zdCBh
dXRob3JzIGF0IHRoZSB0aW1lIG9mIG1hbnVzY3JpcHQgcmV2aXNpb24uDQo+ID4+DQo+ID4+IEF1
dGhvcnNoaXAgRm9ybSBhbmQgU3RhdGVtZW50IG9mIENvbmZsaWN0cyBvZiBJbnRlcmVzdCBbUERG
XQ0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+PiBQYXJ0IElWIHJlZ2FyZGluZyDigJxDb25mbGljdCBv
ZiBJbnRlcmVzdOKAnSBpcyBwYXJ0aWN1bGFybHkgcmVsZXZhbnQgdG8NCj4gPj4gc3RhbmRhcmRz
IG9yZ2FuaXphdGlvbnMgc3VjaCBhcyBJRVRGLiBTdWNoIGEgZGlzY2xvc3VyZSByZXF1aXJlbWVu
dA0KPiA+PiB3b3VsZCBmdXJ0aGVyIGVuY291cmFnZSBldmVyeW9uZSB0byB0cnVzdCBhbmQgaW1w
bGVtZW50IElFVEYNCj4gc3BlY2lmaWNhdGlvbnMuDQo+ID4+DQo+ID4+DQo+ID4+DQo+ID4+IFRo
aXMgZG9jdW1lbnQgZm9sbG93cyB0aGUgcmVjb21tZW5kYXRpb25zIGluIE9uIEJlaW5nIGEgU2Np
ZW50aXN0OiBBDQo+ID4+IEd1aWRlIHRvIFJlc3BvbnNpYmxlIENvbmR1Y3QgaW4gUmVzZWFyY2gs
IFRoZSBOYXRpb25hbCBBY2FkZW1pZXMNCj4gPj4gUHJlc3MsIFRoaXJkIEVkaXRpb24gKDIwMDkp
Lg0KPiA+Pg0KPiA+Pg0KPiA+Pg0KPiA+PiAvTGFycnkNCj4gPj4NCj4gPj4NCj4gPj4NCj4gPj4g
TGF3cmVuY2UgUm9zZW4NCj4gPj4NCj4gPj4gUm9zZW5sYXcgJiBFaW5zY2hsYWcgKHd3dy5yb3Nl
bmxhdy5jb20pDQo+ID4+DQo+ID4+IDMwMDEgS2luZyBSYW5jaCBSb2FkLCBVa2lhaCwgQ0EgOTU0
ODINCj4gPj4NCj4gPj4gQ2VsbDogNzA3LTQ3OC04OTMyICAgRmF4OiA3MDctNDg1LTEyNDMNCj4g
Pj4NCj4gPj4NCj4gPg0KPiA+DQo+ID4NCj4gPiAtLQ0KPiA+IFdlYnNpdGU6IGh0dHA6Ly9oYWxs
YW1iYWtlci5jb20vDQo+ID4NCj4gDQo+IA0KPiANCj4gLS0NCj4gV2Vic2l0ZTogaHR0cDovL2hh
bGxhbWJha2VyLmNvbS8NCg0K


From nobody Fri Apr 25 10:34:27 2014
Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E4FE1A02C8 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 10:34:24 -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, SPF_PASS=-0.001] autolearn=ham
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 u99lS9pqkVBO for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 10:34:22 -0700 (PDT)
Received: from mail-yh0-x233.google.com (mail-yh0-x233.google.com [IPv6:2607:f8b0:4002:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id AEF5E1A026D for <ietf@ietf.org>; Fri, 25 Apr 2014 10:34:22 -0700 (PDT)
Received: by mail-yh0-f51.google.com with SMTP id f10so3855605yha.24 for <ietf@ietf.org>; Fri, 25 Apr 2014 10:34:16 -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:content-type; bh=IF/Z1YcnJB6LW0b5WqylyV+4yPOkOu4uG1NLsTLffck=; b=FG3us244Jmm3Zh+jZDQHFS9XlqAOnyfrp4OVQVWWY7jvN9qB4X9T0iNui+5dxq24ts vA3riHxcQNf+WZS4/ioJ5Qdevlk/mf5UQef5auhhmuc7pNrp23EVrj0jquPgauTGAQyy wl2rlfF9NK/zQbpUO1iFTp7ulAbS5iVi808IOMKSHVKJ1EtKzJUG3VUVcW/bySKy6Ek0 4WH1b2YtM11iIfxAmK1ZCW2Jl8wtw5ka5yhKjUUGwp9ICgFcIkeNppOngtIB/EQCQNEf wn1f8JA63rnUBJulbAYKp0bMs/PJrO6pvK1gNhGKyE1KL+mbwDPQ7YMwcFV9pNs0ItSb NoEw==
MIME-Version: 1.0
X-Received: by 10.236.65.202 with SMTP id f50mr3688395yhd.160.1398447255918; Fri, 25 Apr 2014 10:34:15 -0700 (PDT)
Received: by 10.170.87.135 with HTTP; Fri, 25 Apr 2014 10:34:15 -0700 (PDT)
In-Reply-To: <535A85A9.4030609@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <535A85A9.4030609@meetinghouse.net>
Date: Fri, 25 Apr 2014 18:34:15 +0100
Message-ID: <CADnDZ8-6ZRFSuHTiasavnqYwZ-eCd6_d078WFUC+sXuWDrdyPQ@mail.gmail.com>
Subject: Re: The IETF environment
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Miles Fidelman <mfidelman@meetinghouse.net>
Content-Type: multipart/alternative; boundary=001a1132e036ed385f04f7e15f93
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8bxFlAwbWrHHa8ty7aeBNq_Q8mM
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 17:34:24 -0000

--001a1132e036ed385f04f7e15f93
Content-Type: text/plain; charset=UTF-8

On Friday, April 25, 2014, Miles Fidelman wrote:

> Dave Crocker wrote:
>
>>
>> With respect to getting work done, this is a bottom-up organization, not
>> a top-down one.  (That's why I think Area "Director" is a serious misnomer
>> and Area "Facilitator" would be far more accurate.)
>>
>>   But it seems pretty clear that people regard the IETF as
>>> a bit more than that. Maybe they shouldn't, but they do.
>>>
>>
>> Yes, there is quite a bit of mythology about the IETF.  Sometimes it
>> borders on mysticism...
>>
>>  Bottom up is generally a good thing, and that's certainly been IETF's
> traditional modus operandi.  But... in that IETF is the official standard
> body for the Internet - and it's ultimately the standards that hold the
> Internet together -- isn't the real discussion about:
>
> 1. Are the emerging scale, scope, complexity, and issues involved in
> Internet operation/management/<your favorite term> highlighting the limits
> of that bottom-up (or perhaps, arms-length) approach to the way IETF is
> playing its role?


That role is done by IETF WGs, that makes WGs very important to represent
the approach of bottom-up-decision-making. Just or General Area has no
WGs!!!


>
> 2. Are there changes needed?


We need to think of our IETF areas more seriously, and we need some WGs in
the IETF general area to represent bottom-up-consultations. WGs that make
more procedure drafts for IETF within the big changes of the internet in
future.

AB


>
>
>

--001a1132e036ed385f04f7e15f93
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<br><br>On Friday, April 25, 2014, Miles Fidelman  wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">Dave Crocker wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
With respect to getting work done, this is a bottom-up organization, not a =
top-down one. =C2=A0(That&#39;s why I think Area &quot;Director&quot; is a =
serious misnomer and Area &quot;Facilitator&quot; would be far more accurat=
e.)<br>

<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0But it seems pretty clear that people regard the IETF as<br>
a bit more than that. Maybe they shouldn&#39;t, but they do.<br>
</blockquote>
<br>
Yes, there is quite a bit of mythology about the IETF. =C2=A0Sometimes it b=
orders on mysticism...<br>
<br>
</blockquote>
Bottom up is generally a good thing, and that&#39;s certainly been IETF&#39=
;s traditional modus operandi. =C2=A0But... in that IETF is the official st=
andard body for the Internet - and it&#39;s ultimately the standards that h=
old the Internet together -- isn&#39;t the real discussion about:<br>

<br>
1. Are the emerging scale, scope, complexity, and issues involved in Intern=
et operation/management/&lt;your favorite term&gt; highlighting the limits =
of that bottom-up (or perhaps, arms-length) approach to the way IETF is pla=
ying its role?</blockquote>
<div><br></div><div>That role is done by IETF WGs, that makes WGs very impo=
rtant to represent the approach of bottom-up-decision-making. Just or Gener=
al Area has no WGs!!!</div><div>=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
2. Are there changes needed?</blockquote><div><br></div><div>We need to thi=
nk of our IETF areas more seriously, and we need some WGs in the IETF=C2=A0=
general area to represent bottom-up-consultations. WGs that make more proce=
dure drafts for IETF within the big changes of the internet in future.=C2=
=A0</div>
<div><br></div><div>AB</div><div><br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br><br><br>
</blockquote>

--001a1132e036ed385f04f7e15f93--


From nobody Fri Apr 25 10:40:46 2014
Return-Path: <lrosen@rosenlaw.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA301A02F2 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 10:40:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.233
X-Spam-Level: 
X-Spam-Status: No, score=0.233 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, SPF_PASS=-0.001] autolearn=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 M-ZCLENQnWXh for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 10:40:42 -0700 (PDT)
Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) by ietfa.amsl.com (Postfix) with SMTP id E7E641A02CC for <ietf@ietf.org>; Fri, 25 Apr 2014 10:40:41 -0700 (PDT)
Received: (qmail 22775 invoked by uid 0); 25 Apr 2014 17:40:26 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy4.mail.unifiedlayer.com with SMTP; 25 Apr 2014 17:40:26 -0000
Received: from box597.bluehost.com ([66.147.242.197]) by cmgw3 with  id uHgM1n00f4GF2VN01HgQaK; Fri, 25 Apr 2014 11:40:26 -0600
X-Authority-Analysis: v=2.1 cv=XPOjF2RE c=1 sm=1 tr=0 a=NRJ8aB/FPT4S3utBguGD+g==:117 a=NRJ8aB/FPT4S3utBguGD+g==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=qDS3CPt326AA:10 a=7xXQEuv9rCMA:10 a=CAIbOuo8jNoA:10 a=4F77bVRYAAAA:8 a=FxJxCPAPh0wA:10 a=AqkBdCNi7UMA:10 a=DAwyPP_o2Byb1YXLmDAA:9 a=Zr7miEi8wWIA:10 a=cKsnjEOsciEA:10 a=L76QRiJ-AAAA:8 a=gL33619KAAAA:8 a=48vgC7mUAAAA:8 a=FKLyZgRAAAAA:8 a=pGLkceISAAAA:8 a=WOIJDy4HAAAA:8 a=MA8e0qxkI0qvhbQPm2cA:9 a=8yl0A4KgvVh_NeZ-:21 a=UNhzjuV_CSAMBaBV:21 a=QEXdDO2ut3YA:10 a=SqxYWZjetj4A:10 a=TImqNlVd7iMA:10 a=GY4jvMCSLq0A:10 a=nsjucRHcZRwA:10 a=B0a0FVVDmlMA:10 a=lZB815dzVvQA:10 a=MSl-tDqOz04A:10 a=yMhMjlubAAAA:8 a=SSmOFEACAAAA:8 a=xmfBnyGqlckOLh4pzpYA:9 a=HM4TSTZPfkpE32cu:21 a=cntQiU5kO4TeuEwY:21 a=SLuDnR3FzosoKbtY:21 a=gKO2Hq4RSVkA:10 a=UiCQ7L4-1S4A:10 a=hTZeC7Yk6K0A:10 a=frz4AuCg-hUA:10 a=1RozqU9qb5sA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=rosenlaw.com; s=default;  h=Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From:Reply-To; bh=g7JJxUPpsDforAdLd0RM2M8TsUFGT4ndJAoKvLRTzQM=;  b=um2QWdVd+KGLg7QuKg8gjTeLBvDksi/YLpZhBW48Rs8W8EPdrgu/JCrZZEYaPYpTzVOShMWEaoAj0LlpqhMnFCffHBusZH7Qkl/okvyObc3BH5D+6HgfZN+IkxVX/6PC;
Received: from [70.36.224.178] (port=19456 helo=Lawrencei) by box597.bluehost.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from <lrosen@rosenlaw.com>) id 1Wdk6j-0004ef-3Y; Fri, 25 Apr 2014 11:40:17 -0600
From: "Lawrence Rosen" <lrosen@rosenlaw.com>
To: "'IETF'" <ietf@ietf.org>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>	<CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com>	<037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com> <CAMm+LwhO4a3=O_=xp4Ge8AsFFXnojdH=YKQNoQRsGXiMr88e+g@mail.gmail.com> <04ae01cf60a6$bf805510$3e80ff30$@rosenlaw.com> <CE39F90A45FF0C49A1EA229FC9899B0507D579EC@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D579EC@USCLES544.agna.amgreetings.com>
Subject: RE: Author disclosures and conflict of interest
Date: Fri, 25 Apr 2014 10:40:15 -0700
Message-ID: <04de01cf60ad$6cd48730$467d9590$@rosenlaw.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_04DF_01CF6072.C079A6D0"
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQKXcE4LMzjvYQvi+4zFEB3vA0KOeQJHdvB/AVPihlICWIgRzAGk3ij1AasZyCyZSFkNoA==
Content-Language: en-us
X-Identified-User: {1397:box597.bluehost.com:rosenla1:rosenlaw.com} {sentby:smtp auth 70.36.224.178 authed with lrosen@rosenlaw.com}
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QP5avZk96zqwyxHDRJA7FGmW_4Q
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: lrosen@rosenlaw.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 17:40:44 -0000

This is a multipart message in MIME format.

------=_NextPart_000_04DF_01CF6072.C079A6D0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Mike Hammer asked:

> The nice thing about codes of ethics is that there are so many to =
choose from.=20

> Which one are we supposed to be looking at?

=20

This one from Science Magazine =
<http://www.sciencemag.org/site/feature/contribinfo/prep/coi.xhtml>  is =
the one I suggested in my initial email in this thread:

=20


Authorship Form and Conflict-of-Interest Statement


To meet its responsibility to readers and to the public to provide clear =
and unbiased scientific results and analyses, Science believes that =
manuscripts (including Brevia, Essays, Perspectives, Policy Forums, =
Reports, Research Articles, Reviews, and Viewpoints) should be =
accompanied by clear disclosures from all authors of the nature and =
level of their contribution to the article, their understanding =
regarding the obligation to share data and materials, and any =
affiliations, funding sources, or financial holdings that might raise =
questions about possible sources of bias. Before manuscript acceptance, =
therefore, authors will be asked to sign an =
authorship/conflict-of-interest form. Specific information will be sent =
to most authors at the time of manuscript revision.

 <http://www.sciencemag.org/site/feature/contribinfo/prep/coi.pdf> =
Authorship Form and Statement of Conflicts of Interest [PDF]

=20

As you say, there are others=E2=80=A6.

=20

/Larry

=20

=20

-----Original Message-----
From: MH Michael Hammer (5304) [mailto:MHammer@ag.com]=20
Sent: Friday, April 25, 2014 10:18 AM
To: lrosen@rosenlaw.com; 'IETF'
Subject: RE: Author disclosures and conflict of interest

=20

=20

=20

> -----Original Message-----

> From: ietf [ <mailto:ietf-bounces@ietf.org> =
mailto:ietf-bounces@ietf.org] On Behalf Of Lawrence Rosen

> Sent: Friday, April 25, 2014 12:52 PM

> To: 'IETF'

> Subject: RE: Author disclosures and conflict of interest

>=20

> Phillip Hallam-Baker asked:

> > So there is only one set of ethical rules for scientists and =
engineers then?

>=20

> Of course not. But before you reject the ethical rules proposed by the =


> National Academies (of Science, Engineering, Medicine, and the=20

> National Research Council), you ought to have a better argument than=20

> "I don't wanna...."

>=20

> This attitude, unfortunately, diminishes respect for IETF and its =
standards.

> And nothing confirms that disrespect better than the almost complete=20

> silence here whenever topics such as this are brought up. It is as if=20

> IETF standards are generated in an ethical vacuum where "caveat =
emptor"

> prevails.

>=20

> /Larry

>=20

=20

I took the time to look at the website  <http://www.onlineethics.org/> =
http://www.onlineethics.org/ related to ethics as indicated by the =
National Academy of Engineering. I didn't find a code of ethics from the =
Academy but instead found links to a whole bunch of other sites -  =
<http://www.onlineethics.org/Resources/ethcodes/EnglishCodes.aspx> =
http://www.onlineethics.org/Resources/ethcodes/EnglishCodes.aspx. The =
nice thing about standards is that there are so many to choose from. The =
nice thing about codes of ethics is that there are so many to choose =
from. Which one are we supposed to be looking at?

=20

Mike

=20

>=20

> -----Original Message-----

> From: Phillip Hallam-Baker [ <mailto:hallam@gmail.com> =
mailto:hallam@gmail.com]

> Sent: Thursday, April 24, 2014 1:54 PM

> To: Lawrence Rosen

> Cc: IETF

> Subject: Re: Author disclosures and conflict of interest

>=20

> So there is only one set of ethical rules for scientists and engineers =
then?

>=20

> Thats news to me.

>=20

> On Thu, Apr 24, 2014 at 2:35 PM, Lawrence Rosen < =
<mailto:lrosen@rosenlaw.com> lrosen@rosenlaw.com>

> wrote:

> > Phillip Hallam-Baker wrote:

> >> Like the question 'are you a spy' which they used to ask when=20

> >> people entered the US, I fail to see how this helps with the=20

> >> NSA/FSB/PLA/etc

> problem.

> >

> > The question actually is: Do you agree to the ethical rules for=20

> > scientists and

> engineers?

> >

> > By the way, those ethical rules require only disclosure, not =
recusal.

> >

> > /Larry

> >

> >

> > -----Original Message-----

> > From: Phillip Hallam-Baker [ <mailto:hallam@gmail.com> =
mailto:hallam@gmail.com]

> > Sent: Monday, April 21, 2014 2:05 PM

> > To:  <mailto:lrosen@rosenlaw.com> lrosen@rosenlaw.com

> > Cc: IETF Discussion Mailing List

> > Subject: Re: Author disclosures and conflict of interest

> >

> > Like the question 'are you a spy' which they used to ask when people

> entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc=20

> problem.

> >

> > The people who are being paid to subvert the standards aren't going =
to say.

> >

> > They might not even know that the objective is subversion.

> >

> >

> > Like many IETF participants I have substantial financial interests=20

> > in several

> Internet companies besides my employer. Am I meant to put those in a=20

> blind trust?

> >

> > And even if I did all that people would still assume that I am=20

> > working as an

> agent of the New World Order. Though quite how the other folk on the=20

> conference call worked out that the helicopter is black still puzzles =
me.

> >

> >

> > On Sun, Apr 20, 2014 at 1:18 PM, Lawrence Rosen=20

> > < <mailto:lrosen@rosenlaw.com> lrosen@rosenlaw.com>

> wrote:

> >> I=E2=80=99ve been skimming recent threads  on this list relating to =
work=20

> >> done (or not done) at IETF and was reminded of this from Science =
Magazine:

> >>

> >>

> >>

> >> Authorship Form and Conflict-of-Interest Statement

> >>

> >> To meet its responsibility to readers and to the public to provide=20

> >> clear and unbiased scientific results and analyses, Science=20

> >> believes that manuscripts (including Brevia, Essays, Perspectives,=20

> >> Policy Forums, Reports, Research Articles, Reviews, and Viewpoints) =


> >> should be accompanied by clear disclosures from all authors of the=20

> >> nature and level of their contribution to the article, their=20

> >> understanding regarding the obligation to share data and materials, =


> >> and any affiliations, funding sources, or financial holdings that=20

> >> might raise questions about possible sources of bias. Before=20

> >> manuscript acceptance, therefore, authors will be asked to sign an=20

> >> authorship/conflict-of-interest form. Specific information will be=20

> >> sent to

> most authors at the time of manuscript revision.

> >>

> >> Authorship Form and Statement of Conflicts of Interest [PDF]

> >>

> >>

> >>

> >> Part IV regarding =E2=80=9CConflict of Interest=E2=80=9D is =
particularly relevant=20

> >> to standards organizations such as IETF. Such a disclosure=20

> >> requirement would further encourage everyone to trust and implement =


> >> IETF

> specifications.

> >>

> >>

> >>

> >> This document follows the recommendations in On Being a Scientist:=20

> >> A Guide to Responsible Conduct in Research, The National Academies=20

> >> Press, Third Edition (2009).

> >>

> >>

> >>

> >> /Larry

> >>

> >>

> >>

> >> Lawrence Rosen

> >>

> >> Rosenlaw & Einschlag ( <http://www.rosenlaw.com> www.rosenlaw.com)

> >>

> >> 3001 King Ranch Road, Ukiah, CA 95482

> >>

> >> Cell: 707-478-8932   Fax: 707-485-1243

> >>

> >>

> >

> >

> >

> > --

> > Website:  <http://hallambaker.com/> http://hallambaker.com/

> >

>=20

>=20

>=20

> --

> Website:  <http://hallambaker.com/> http://hallambaker.com/

=20


------=_NextPart_000_04DF_01CF6072.C079A6D0
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta =
http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta =
name=3DGenerator content=3D"Microsoft Word 15 (filtered =
medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:inherit;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
h2
	{mso-style-priority:9;
	mso-style-link:"Heading 2 Char";
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:18.0pt;
	font-family:"Times New Roman","serif";
	font-weight:bold;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri","sans-serif";}
span.Heading2Char
	{mso-style-name:"Heading 2 Char";
	mso-style-priority:9;
	mso-style-link:"Heading 2";
	font-family:"Times New Roman","serif";
	mso-fareast-language:EN-GB;
	font-weight:bold;}
span.apple-converted-space
	{mso-style-name:apple-converted-space;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri","sans-serif";
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-GB =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoPlainText>Mike Hammer asked:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; The nice thing about codes of ethics is that =
there are so many to choose from. <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Which one are we supposed to be looking =
at?<o:p></o:p></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>This one from <i><a =
href=3D"http://www.sciencemag.org/site/feature/contribinfo/prep/coi.xhtml=
">Science Magazine</a> </i>is the one I suggested in my initial email in =
this thread:<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><h2 =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:6.0pt;marg=
in-left:.5in;background:white;vertical-align:baseline'><span =
style=3D'font-size:12.0pt;font-family:"Arial","sans-serif";color:#666666'=
>Authorship Form and Conflict-of-Interest =
Statement<o:p></o:p></span></h2><p =
style=3D'mso-margin-top-alt:0in;margin-right:0in;margin-bottom:0in;margin=
-left:.5in;margin-bottom:.0001pt;background:white;vertical-align:baseline=
;outline-style: none;text-align:start;orphans: auto;widows: =
auto;-webkit-text-stroke-width: 0px;word-spacing:0px'><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333'=
>To meet its responsibility to readers and to the public to provide =
clear and unbiased scientific results and analyses,<span =
class=3Dapple-converted-space>&nbsp;</span></span><em><span =
style=3D'font-size:10.0pt;font-family:inherit;color:#333333;border:none =
windowtext 1.0pt;padding:0in'>Science</span></em><span =
class=3Dapple-converted-space><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333'=
>&nbsp;</span></span><span =
style=3D'font-size:10.0pt;font-family:"Arial","sans-serif";color:#333333'=
>believes that manuscripts (including Brevia, Essays, Perspectives, =
Policy Forums, Reports, Research Articles, Reviews, and Viewpoints) =
should be accompanied by clear disclosures from all authors of the =
nature and level of their contribution to the article, their =
understanding regarding the obligation to share data and materials, and =
any affiliations, funding sources, or financial holdings that might =
raise questions about possible sources of bias. Before manuscript =
acceptance, therefore, authors will be asked to sign an =
authorship/conflict-of-interest form. Specific information will be sent =
to most authors at the time of manuscript =
revision.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:.5in;line-height:12.5pt;background:white;vertical-al=
ign:baseline'><span =
style=3D'font-size:10.0pt;font-family:inherit;color:#333333'><a =
href=3D"http://www.sciencemag.org/site/feature/contribinfo/prep/coi.pdf">=
<span style=3D'color:#2E6D8F;border:none windowtext =
1.0pt;padding:0in'>Authorship Form and Statement of Conflicts of =
Interest</span></a><span =
class=3Dapple-converted-space>&nbsp;</span>[PDF]</span><span =
style=3D'font-size:10.0pt;font-family:inherit;color:#333333'><o:p></o:p><=
/span></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>As you say, there are =
others=E2=80=A6.<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>/Larry<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText><span =
lang=3DEN-US style=3D'mso-fareast-language:EN-GB'>-----Original =
Message-----<br>From: MH Michael Hammer (5304) [mailto:MHammer@ag.com] =
<br>Sent: Friday, April 25, 2014 10:18 AM<br>To: lrosen@rosenlaw.com; =
'IETF'<br>Subject: RE: Author disclosures and conflict of =
interest</span></p><p class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>&gt; =
-----Original Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
From: ietf [<a href=3D"mailto:ietf-bounces@ietf.org"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:ietf-bounces@ietf.=
org</span></a>] On Behalf Of Lawrence Rosen<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Sent: Friday, April 25, 2014 12:52 =
PM<o:p></o:p></p><p class=3DMsoPlainText>&gt; To: =
'IETF'<o:p></o:p></p><p class=3DMsoPlainText>&gt; Subject: RE: Author =
disclosures and conflict of interest<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
Phillip Hallam-Baker asked:<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt; So there is only one set of ethical rules for scientists and =
engineers then?<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; Of course not. But before =
you reject the ethical rules proposed by the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; National Academies (of Science, Engineering, =
Medicine, and the <o:p></o:p></p><p class=3DMsoPlainText>&gt; National =
Research Council), you ought to have a better argument than =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &quot;I don't =
wanna....&quot;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; This attitude, =
unfortunately, diminishes respect for IETF and its =
standards.<o:p></o:p></p><p class=3DMsoPlainText>&gt; And nothing =
confirms that disrespect better than the almost complete =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; silence here whenever topics =
such as this are brought up. It is as if <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; IETF standards are generated in an ethical =
vacuum where &quot;caveat emptor&quot;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; prevails.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
/Larry<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>I took =
the time to look at the website <a =
href=3D"http://www.onlineethics.org/"><span =
style=3D'color:windowtext;text-decoration:none'>http://www.onlineethics.o=
rg/</span></a> related to ethics as indicated by the National Academy of =
Engineering. I didn't find a code of ethics from the Academy but instead =
found links to a whole bunch of other sites - <a =
href=3D"http://www.onlineethics.org/Resources/ethcodes/EnglishCodes.aspx"=
><span =
style=3D'color:windowtext;text-decoration:none'>http://www.onlineethics.o=
rg/Resources/ethcodes/EnglishCodes.aspx</span></a>. The nice thing about =
standards is that there are so many to choose from. The nice thing about =
codes of ethics is that there are so many to choose from. Which one are =
we supposed to be looking at?<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p =
class=3DMsoPlainText>Mike<o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; -----Original =
Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt; From: Phillip =
Hallam-Baker [<a href=3D"mailto:hallam@gmail.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:hallam@gmail.com</=
span></a>]<o:p></o:p></p><p class=3DMsoPlainText>&gt; Sent: Thursday, =
April 24, 2014 1:54 PM<o:p></o:p></p><p class=3DMsoPlainText>&gt; To: =
Lawrence Rosen<o:p></o:p></p><p class=3DMsoPlainText>&gt; Cc: =
IETF<o:p></o:p></p><p class=3DMsoPlainText>&gt; Subject: Re: Author =
disclosures and conflict of interest<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; So =
there is only one set of ethical rules for scientists and engineers =
then?<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Thats news to me.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; On =
Thu, Apr 24, 2014 at 2:35 PM, Lawrence Rosen &lt;<a =
href=3D"mailto:lrosen@rosenlaw.com"><span =
style=3D'color:windowtext;text-decoration:none'>lrosen@rosenlaw.com</span=
></a>&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
wrote:<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; Phillip =
Hallam-Baker wrote:<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; =
Like the question 'are you a spy' which they used to ask when =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; people entered the =
US, I fail to see how this helps with the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; NSA/FSB/PLA/etc<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; problem.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; The question actually is: Do you agree to =
the ethical rules for <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; =
scientists and<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
engineers?<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; By the way, those =
ethical rules require only disclosure, not recusal.<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; /Larry<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; -----Original =
Message-----<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; From: =
Phillip Hallam-Baker [<a href=3D"mailto:hallam@gmail.com"><span =
style=3D'color:windowtext;text-decoration:none'>mailto:hallam@gmail.com</=
span></a>]<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; Sent: Monday, =
April 21, 2014 2:05 PM<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; =
To: <a href=3D"mailto:lrosen@rosenlaw.com"><span =
style=3D'color:windowtext;text-decoration:none'>lrosen@rosenlaw.com</span=
></a><o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; Cc: IETF =
Discussion Mailing List<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; =
Subject: Re: Author disclosures and conflict of =
interest<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; Like the question =
'are you a spy' which they used to ask when people<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; entered the US, I fail to see how this helps =
with the NSA/FSB/PLA/etc <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
problem.<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; The people who are =
being paid to subvert the standards aren't going to =
say.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; They might not even know that the =
objective is subversion.<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; Like many IETF participants I have =
substantial financial interests <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; in several<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Internet companies besides my employer. Am I =
meant to put those in a <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
blind trust?<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; And even if I did =
all that people would still assume that I am <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; working as an<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; agent of the New World Order. Though quite how =
the other folk on the <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
conference call worked out that the helicopter is black still puzzles =
me.<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; On Sun, Apr 20, 2014 at 1:18 PM, Lawrence =
Rosen <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt; &lt;<a =
href=3D"mailto:lrosen@rosenlaw.com"><span =
style=3D'color:windowtext;text-decoration:none'>lrosen@rosenlaw.com</span=
></a>&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
wrote:<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; I=E2=80=99ve =
been skimming recent threads=C2=A0 on this list relating to work =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; done (or not done) =
at IETF and was reminded of this from Science Magazine:<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; Authorship Form and =
Conflict-of-Interest Statement<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; To meet its responsibility to readers =
and to the public to provide <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt; clear and unbiased scientific results and analyses, Science =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; believes that =
manuscripts (including Brevia, Essays, Perspectives, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; Policy Forums, Reports, Research =
Articles, Reviews, and Viewpoints) <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; should be accompanied by clear =
disclosures from all authors of the <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; nature and level of their =
contribution to the article, their <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; understanding regarding the =
obligation to share data and materials, <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; and any affiliations, funding =
sources, or financial holdings that <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; might raise questions about possible =
sources of bias. Before <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt; manuscript acceptance, therefore, authors will be asked to sign =
an <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; =
authorship/conflict-of-interest form. Specific information will be =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; sent =
to<o:p></o:p></p><p class=3DMsoPlainText>&gt; most authors at the time =
of manuscript revision.<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; Authorship =
Form and Statement of Conflicts of Interest [PDF]<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; Part IV regarding =E2=80=9CConflict =
of Interest=E2=80=9D is particularly relevant <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; to standards organizations such as =
IETF. Such a disclosure <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt; requirement would further encourage everyone to trust and =
implement <o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; =
IETF<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
specifications.<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; This =
document follows the recommendations in On Being a Scientist: =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; A Guide to =
Responsible Conduct in Research, The National Academies =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; Press, Third =
Edition (2009).<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; =
/Larry<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; Lawrence =
Rosen<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; Rosenlaw =
&amp; Einschlag (<a href=3D"http://www.rosenlaw.com"><span =
style=3D'color:windowtext;text-decoration:none'>www.rosenlaw.com</span></=
a>)<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt; 3001 King Ranch Road, Ukiah, CA =
95482<o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; &gt;&gt; Cell: =
707-478-8932=C2=A0=C2=A0 Fax: 707-485-1243<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;&gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt;<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; --<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; &gt; Website: <a =
href=3D"http://hallambaker.com/"><span =
style=3D'color:windowtext;text-decoration:none'>http://hallambaker.com/</=
span></a><o:p></o:p></p><p class=3DMsoPlainText>&gt; =
&gt;<o:p></o:p></p><p class=3DMsoPlainText>&gt; <o:p></o:p></p><p =
class=3DMsoPlainText>&gt; <o:p></o:p></p><p class=3DMsoPlainText>&gt; =
<o:p></o:p></p><p class=3DMsoPlainText>&gt; --<o:p></o:p></p><p =
class=3DMsoPlainText>&gt; Website: <a =
href=3D"http://hallambaker.com/"><span =
style=3D'color:windowtext;text-decoration:none'>http://hallambaker.com/</=
span></a><o:p></o:p></p><p =
class=3DMsoPlainText><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_04DF_01CF6072.C079A6D0--


From nobody Fri Apr 25 10:48:31 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 722201A03C5 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 10:48:28 -0700 (PDT)
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] autolearn=ham
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 NhqtpeJMUYXU for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 10:48:24 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 26B371A0386 for <ietf@ietf.org>; Fri, 25 Apr 2014 10:48:24 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3PHmEa8008239 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 25 Apr 2014 10:48:17 -0700
Message-ID: <535A9F58.1080105@dcrocker.net>
Date: Fri, 25 Apr 2014 10:46:00 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: lrosen@rosenlaw.com, ietf@ietf.org
Subject: Re: Author disclosures and conflict of interest
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>
In-Reply-To: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 25 Apr 2014 10:48:17 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EHFZpNNTEfJXc0uyfkxOzZ2RKsw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 17:48:28 -0000

On 4/20/2014 10:18 AM, Lawrence Rosen wrote:
> Such a disclosure requirement would further encourage everyone to trust
> and implement IETF specifications.


Probably not.

Although the IETF has participation from the full range of academia, 
research-ia, and industry, it's really and industry-driven environment, 
since successful output of the IETF results in products and services.

The proper model for such an environment is that everyone who 
participates is biased and has an agenda.

Seriously.  Expecting anything is frankly naive.

What mitigates that realistic view is balance among competing biases and 
competing goals, and of course transparency in the processes and in the 
details of what is produced.

Intellectual property is really the only area of potential opacity that 
should (and does) concern us.

Trust in IETF work comes from timely utility, not abstract disclosures.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Apr 25 11:25:29 2014
Return-Path: <lrosen@rosenlaw.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AEF41A06BB for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:25:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.033
X-Spam-Level: *
X-Spam-Status: No, score=1.033 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, SPF_PASS=-0.001] autolearn=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 5qggyVMbEBFf for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:25:25 -0700 (PDT)
Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) by ietfa.amsl.com (Postfix) with SMTP id DB7BA1A03B3 for <ietf@ietf.org>; Fri, 25 Apr 2014 11:25:24 -0700 (PDT)
Received: (qmail 14599 invoked by uid 0); 25 Apr 2014 18:25:17 -0000
Received: from unknown (HELO CMOut01) (10.0.90.82) by gproxy4.mail.unifiedlayer.com with SMTP; 25 Apr 2014 18:25:16 -0000
Received: from box597.bluehost.com ([66.147.242.197]) by CMOut01 with  id uJRC1n00w4GF2VN01JRFpa; Fri, 25 Apr 2014 12:25:16 -0600
X-Authority-Analysis: v=2.1 cv=EOmVjTpC c=1 sm=1 tr=0 a=NRJ8aB/FPT4S3utBguGD+g==:117 a=NRJ8aB/FPT4S3utBguGD+g==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=qDS3CPt326AA:10 a=7xXQEuv9rCMA:10 a=CAIbOuo8jNoA:10 a=8nJEP1OIZ-IA:10 a=4F77bVRYAAAA:8 a=FxJxCPAPh0wA:10 a=AqkBdCNi7UMA:10 a=b8OvNEjoAAAA:8 a=48vgC7mUAAAA:8 a=k7Ga1wGzAAAA:8 a=fXoRIVcCAy0no2r3a44A:9 a=oxI6iyhCo0vkgK1z:21 a=avtQ2T0QmzC21Ykf:21 a=wPNLvfGTeEIA:10 a=x3I_HB9Tk8MA:10 a=E1Snkw02GREA:10 a=B0a0FVVDmlMA:10 a=lZB815dzVvQA:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=rosenlaw.com; s=default;  h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject:In-Reply-To:References:Cc:To:From:Reply-To; bh=0kAk3Kb+3F6LhTdZAcWQiACXtSJvpYrphNDvepoQK+c=;  b=IX/+naKOQMqfyzM+SGIglnzaR/uCfynRNKcdnYaHkrCrRVXwid+2+nrw4vh1JLkC5e/h5AT+kE7/IutQA9ppuoicSOECWSNm1yFdL5OarXAyJTwmRuxymM6UsL/Kpbt+;
Received: from [70.36.224.178] (port=59287 helo=Lawrencei) by box597.bluehost.com with esmtpsa (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.82) (envelope-from <lrosen@rosenlaw.com>) id 1Wdko7-0004AS-H0; Fri, 25 Apr 2014 12:25:07 -0600
From: "Lawrence Rosen" <lrosen@rosenlaw.com>
To: <ietf@ietf.org>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net>
In-Reply-To: <535A9F58.1080105@dcrocker.net>
Subject: RE: Author disclosures and conflict of interest
Date: Fri, 25 Apr 2014 11:25:05 -0700
Message-ID: <04ee01cf60b3$b079f9b0$116ded10$@rosenlaw.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 15.0
Thread-Index: AQKXcE4LMzjvYQvi+4zFEB3vA0KOeQHP60eTmYQB90A=
Content-Language: en-us
X-Identified-User: {1397:box597.bluehost.com:rosenla1:rosenlaw.com} {sentby:smtp auth 70.36.224.178 authed with lrosen@rosenlaw.com}
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ueRfQReh-oJHKN4_n58r0HIQQr8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: lrosen@rosenlaw.com
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 18:25:26 -0000

Dave Crocker wrote:
> The proper model for such an environment is that everyone=20
> who participates is biased and has an agenda.

Dave, thanks for engaging in this important topic.

We all expect bias in standards organizations -- indeed it is a =
irreducible
factor in science and engineering and all human endeavors (and =
particularly
so in my profession, law!). I don't think anyone here is na=EFve about =
that.

Please don't demand more than is possible out of an ethics policy. But =
also
please don't give up the moral high ground just because we all fall =
short of
moral perfection. There is a middle way: Disclosure of potential =
conflicts
of interest that allows each of us to judge those biases for ourselves.=20

We should be expected to sign our contributions and disclose our =
potential
biases and conflicts of interest. Then the buyers will have reason to =
trust
the sellers.

/Larry


-----Original Message-----
From: Dave Crocker [mailto:dhc@dcrocker.net]=20
Sent: Friday, April 25, 2014 10:46 AM
To: lrosen@rosenlaw.com; ietf@ietf.org
Subject: Re: Author disclosures and conflict of interest

On 4/20/2014 10:18 AM, Lawrence Rosen wrote:
> Such a disclosure requirement would further encourage everyone to=20
> trust and implement IETF specifications.


Probably not.

Although the IETF has participation from the full range of academia,
research-ia, and industry, it's really and industry-driven environment,
since successful output of the IETF results in products and services.

The proper model for such an environment is that everyone who =
participates
is biased and has an agenda.

Seriously.  Expecting anything is frankly naive.

What mitigates that realistic view is balance among competing biases and
competing goals, and of course transparency in the processes and in the
details of what is produced.

Intellectual property is really the only area of potential opacity that
should (and does) concern us.

Trust in IETF work comes from timely utility, not abstract disclosures.

d/


--
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Fri Apr 25 11:41:12 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3259B1A03D7 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:41:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] autolearn=ham
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 Y5VP_H545nO4 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:41:06 -0700 (PDT)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id C28941A03B1 for <ietf@ietf.org>; Fri, 25 Apr 2014 11:41:05 -0700 (PDT)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3PIerKL008633; Fri, 25 Apr 2014 19:40:53 +0100
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s3PIeoB8008592 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 25 Apr 2014 19:40:51 +0100
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <lrosen@rosenlaw.com>, <ietf@ietf.org>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net> <04ee01cf60b3$b079f9b0$116ded10$@rosenlaw.com>
In-Reply-To: <04ee01cf60b3$b079f9b0$116ded10$@rosenlaw.com>
Subject: RE: Author disclosures and conflict of interest
Date: Fri, 25 Apr 2014 19:40:48 +0100
Message-ID: <05b701cf60b5$e08c6c80$a1a54580$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKXcE4LMzjvYQvi+4zFEB3vA0KOeQHP60eTAa2oi6SZdp4g0A==
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.0.0.1014-20656.001
X-TM-AS-Result: No--19.928-10.0-31-10
X-imss-scan-details: No--19.928-10.0-31-10
X-TMASE-MatchedRID: PL66URbwWA+31G6CKdUG1VaOpp/sV5nVVFkYZI44OnXfUZT83lbkEPgJ 7PLy+87Ehf6Z8sM1SefRm8OCEr6UNh3ZJC2sAO0hjhXy0Khej9LmaPAcl23KINp1biJhIyNRz+m 0nV5FTn21kB/SQf7sdRcglY7+3ZaO/QrQ/Vfk7iYmtTGirqG/D34yToAKzDgmqPm/sjj9KBj3V0 u7p177xDNHiUkn07NS5NU4Qjc7gnYowx1wS2cVSK9SgVZ49rQMSNmpTpsmB/fKULV0s51bAl721 f1Z1L9K1CWk1XCvfFWjGZWeaayx6JO7ij3TaTVLRsqQuQlRTh+EQiKo28GuY7rtDe4+j0ojedkw TmcwLcN7q6VMoN/8zH51/Ce39OcTS3h2ayN9L5RNEMH4f8YUIbZrDHFV+TcHoCT08tx7PefNjNu 8vtqNIAyl34DsFe0ANFVUJkUpWvb9PPAAyZQHSgArNgt5xpQYGSqdEmeD/nXqkRQFroo+H9CxMp 7rS1/94vM1YF6AJbZijRMo49h+pnczv8nPF99x3QfwsVk0UbslCGssfkpInQ==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iBwBV4hUjcS4Bbyawv1xJwU91BQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 18:41:09 -0000

Larry,

Is this as simple as adding to the "by submitting this draft, all =
authors
confirm..." text?

I know that is not "signing" but when an I-D is posted with your details =
on it
as an author, you do get an automatic email so you have a chance to =
scream "it
wasn't me."

Adrian

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Lawrence Rosen
> Sent: 25 April 2014 19:25
> To: ietf@ietf.org
> Subject: RE: Author disclosures and conflict of interest
>=20
> Dave Crocker wrote:
> > The proper model for such an environment is that everyone
> > who participates is biased and has an agenda.
>=20
> Dave, thanks for engaging in this important topic.
>=20
> We all expect bias in standards organizations -- indeed it is a =
irreducible
> factor in science and engineering and all human endeavors (and =
particularly
> so in my profession, law!). I don't think anyone here is na=EFve about =
that.
>=20
> Please don't demand more than is possible out of an ethics policy. But =
also
> please don't give up the moral high ground just because we all fall =
short of
> moral perfection. There is a middle way: Disclosure of potential =
conflicts
> of interest that allows each of us to judge those biases for =
ourselves.
>=20
> We should be expected to sign our contributions and disclose our =
potential
> biases and conflicts of interest. Then the buyers will have reason to =
trust
> the sellers.
>=20
> /Larry
>=20
>=20
> -----Original Message-----
> From: Dave Crocker [mailto:dhc@dcrocker.net]
> Sent: Friday, April 25, 2014 10:46 AM
> To: lrosen@rosenlaw.com; ietf@ietf.org
> Subject: Re: Author disclosures and conflict of interest
>=20
> On 4/20/2014 10:18 AM, Lawrence Rosen wrote:
> > Such a disclosure requirement would further encourage everyone to
> > trust and implement IETF specifications.
>=20
>=20
> Probably not.
>=20
> Although the IETF has participation from the full range of academia,
> research-ia, and industry, it's really and industry-driven =
environment,
> since successful output of the IETF results in products and services.
>=20
> The proper model for such an environment is that everyone who =
participates
> is biased and has an agenda.
>=20
> Seriously.  Expecting anything is frankly naive.
>=20
> What mitigates that realistic view is balance among competing biases =
and
> competing goals, and of course transparency in the processes and in =
the
> details of what is produced.
>=20
> Intellectual property is really the only area of potential opacity =
that
> should (and does) concern us.
>=20
> Trust in IETF work comes from timely utility, not abstract =
disclosures.
>=20
> d/
>=20
>=20
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From nobody Fri Apr 25 11:45:47 2014
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DEB01A065A for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 aqwFgmcSScLx for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:45:42 -0700 (PDT)
Received: from qmta12.westchester.pa.mail.comcast.net (qmta12.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:227]) by ietfa.amsl.com (Postfix) with ESMTP id 75C5E1A063E for <ietf@ietf.org>; Fri, 25 Apr 2014 11:45:38 -0700 (PDT)
Received: from omta11.westchester.pa.mail.comcast.net ([76.96.62.36]) by qmta12.westchester.pa.mail.comcast.net with comcast id uJjQ1n0020mv7h05CJlXHd; Fri, 25 Apr 2014 18:45:31 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta11.westchester.pa.mail.comcast.net with comcast id uJlX1n00A1KKtkw3XJlX1J; Fri, 25 Apr 2014 18:45:31 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s3PIjV7j023686 for <ietf@ietf.org>; Fri, 25 Apr 2014 14:45:31 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s3PIjV2C023685; Fri, 25 Apr 2014 14:45:31 -0400
Date: Fri, 25 Apr 2014 14:45:31 -0400
Message-Id: <201404251845.s3PIjV2C023685@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <535A9F58.1080105@dcrocker.net> (dhc@dcrocker.net)
Subject: Re: Author disclosures and conflict of interest
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1398451531; bh=EFyowmumdRPzyioDer+xKGmOT9VTPnq+0LiFw9E3abY=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=VtaAciElzgTScii/5mX8VP8WnEIr/6lE6NVeDCL3oXITM9jy9Q/YKGCDhN3nzE9w8 zaD/N6Q7b9MAHefs2x6yalPAKTjR8tcUY135ZAIr0/GJgnDsR4ANStfguc+uP0JUop JI/w1BDxDUAFORLgGOB5bZkYoAzHGZXpz1y5EzQYDdf6zUFtARXBG3DqJpiXdplGZX 6nivbCv7/ZIDtXisCMGNycVw0F2IDCBPv/WDpoSe+ydNQAr+B/FEZJ6OhJWi2fkIw5 8S4nsylvEdTgQ/ZmXNfeIwG4ZQxUpjIMB3zagJ0ifID34zczDCHfy7k8cYUIHr+uWz HiAxyOi6E/4zA==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Scs2zkvC_Hm0hmHle8xg1ja2WBI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 18:45:45 -0000

> From: Dave Crocker <dhc@dcrocker.net>

> Although the IETF has participation from the full range of academia, 
> research-ia, and industry, it's really and industry-driven environment, 
> since successful output of the IETF results in products and services.
> 
> The proper model for such an environment is that everyone who 
> participates is biased and has an agenda.
> 
> Seriously.  Expecting anything is frankly naive.

This seems to me to be common sense (after attending a few IETFs and
getting to know people).  If someone is working in a given area, it's
at least a 50% chance that (1) he has been sent there by an employer,
(2) that employer is producing products in the area, and (3) the
employer has a commercial interests that are affected by the work.
Beyond that, you have to get to know people and their behavior to
determine the degree to which those commercial interests conflict with
producing good standards and the degree to which that affects the
behavior of each person.

This is true as well of working group chairs and area directors.

Need we put this in the Note Well statement?

Dale


From nobody Fri Apr 25 11:54:38 2014
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DC1F1A0298 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
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 OSFHRe_oj-BR for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 11:54:34 -0700 (PDT)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:96]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8641A031D for <ietf@ietf.org>; Fri, 25 Apr 2014 11:54:34 -0700 (PDT)
Received: from omta19.westchester.pa.mail.comcast.net ([76.96.62.98]) by qmta09.westchester.pa.mail.comcast.net with comcast id uHip1n00227AodY59JuUUt; Fri, 25 Apr 2014 18:54:28 +0000
Received: from hobgoblin.ariadne.com ([24.34.72.61]) by omta19.westchester.pa.mail.comcast.net with comcast id uJuT1n00t1KKtkw3fJuTQJ; Fri, 25 Apr 2014 18:54:27 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id s3PIsRII024162 for <ietf@ietf.org>; Fri, 25 Apr 2014 14:54:27 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id s3PIsRld024161; Fri, 25 Apr 2014 14:54:27 -0400
Date: Fri, 25 Apr 2014 14:54:27 -0400
Message-Id: <201404251854.s3PIsRld024161@hobgoblin.ariadne.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: ietf@ietf.org
In-reply-to: <054a01cf609b$7a186450$6e492cf0$@olddog.co.uk> (adrian@olddog.co.uk)
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <054a01cf609b$7a186450$6e492cf0$@olddog.co.uk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1398452068; bh=eq+HlogP24UQUfs77S8fGrg9pH276UqA/2GS5E1uYLk=; h=Received:Received:Received:Received:Date:Message-Id:From:To: Subject; b=LZyFyvLg0JJqSwdT+HB2AJ4+J5JTAKr/Bm/9fnhvgn9MuzqO3ah1Cd+DuiX24v9lq /GXJzjgfLn6Ce5AeGKG1NIf5LgJqgZrz2PsfL6PzWU1aTxkDop9yd9LFuk0A2BP42Z ZxpaJhwlvjLrcBTobniEiBpG8/9YJa1+JaVnFenZdg5hYu4kLa309RFxgcb/I77Ahb wJLhVbDCXJ3xv+B5AmIiF/As82acPkig/Y7rNm++2KKkLvtCJDi9AzXPesZ+Ix0Gn+ DFiLZyjBUxzYNnS6GI4yqJlHtYMQcaxOUMo2o+Q+ulIRLh4ijdFYIpcRs0xAPU/Kw8 H1liV/+GM+d1Q==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/kciyhrGqrawtuoU03WXd1NTQJoo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 18:54:36 -0000

> From: "Adrian Farrel" <adrian@olddog.co.uk>

> This is a handy thread and brings into question what the 'S' in IESG
> is supposed to mean.

As far as I can see, the IETF primarily develops protocols.  Work
which does not revolve around developing protocols does not happen in
the IETF.  Perpass is an example of this, because although it
*considers* pervasive monitoring, its *purpose* is the development of
protocols that are resistant to monitoring and creating an attitude
that monitoring must be considered in the development of other
protocols.  Perpass *exists* because a critical mass of people want to
work on such protocols.

In regard to the IESG, it "steers" by deciding whether or not to
charter working groups.  But its biggest job is reviewing standards
developed by the working groups.  It certainly does not "allocate
resources", that is, decide that some topic needs to be worked on and
recruit people to do the work.

Dale


From nobody Fri Apr 25 12:32:16 2014
Return-Path: <matthew.kaufman@skype.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 582781A0661 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 12:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
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 iSYpTXlR3sID for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 12:32:09 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1blp0184.outbound.protection.outlook.com [207.46.163.184]) by ietfa.amsl.com (Postfix) with ESMTP id 691811A06C1 for <ietf@ietf.org>; Fri, 25 Apr 2014 12:32:08 -0700 (PDT)
Received: from BL2PR03CA022.namprd03.prod.outlook.com (10.141.66.30) by BL2PR03MB164.namprd03.prod.outlook.com (10.255.230.148) with Microsoft SMTP Server (TLS) id 15.0.929.12; Fri, 25 Apr 2014 19:31:59 +0000
Received: from BY2FFO11FD051.protection.gbl (2a01:111:f400:7c0c::181) by BL2PR03CA022.outlook.office365.com (2a01:111:e400:c1b::30) with Microsoft SMTP Server (TLS) id 15.0.929.12 via Frontend Transport; Fri, 25 Apr 2014 19:31:59 +0000
Received: from mail.microsoft.com (131.107.125.37) by BY2FFO11FD051.mail.protection.outlook.com (10.1.15.188) with Microsoft SMTP Server (TLS) id 15.0.929.8 via Frontend Transport; Fri, 25 Apr 2014 19:31:59 +0000
Received: from TK5EX14MBXC298.redmond.corp.microsoft.com ([169.254.1.224]) by TK5EX14HUBC103.redmond.corp.microsoft.com ([157.54.86.9]) with mapi id 14.03.0181.007; Fri, 25 Apr 2014 19:31:20 +0000
From: "Matthew Kaufman (SKYPE)" <matthew.kaufman@skype.net>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "lrosen@rosenlaw.com" <lrosen@rosenlaw.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Author disclosures and conflict of interest
Thread-Topic: Author disclosures and conflict of interest
Thread-Index: Ac9cuQfV+jrpfzgqRbStoWgGRsCahQD9TBUAAAOhrlA=
Date: Fri, 25 Apr 2014 19:31:19 +0000
Message-ID: <AE1A6B5FD507DC4FB3C5166F3A05A484504E055F@TK5EX14MBXC298.redmond.corp.microsoft.com>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net>
In-Reply-To: <535A9F58.1080105@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.33]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:CAL; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(438001)(189002)(199002)(51704005)(558084003)(50466002)(46102001)(2656002)(74502001)(4396001)(85806002)(66066001)(87936001)(80022001)(23726002)(85852003)(83072002)(31966008)(74662001)(6806004)(44976005)(84676001)(2201001)(92566001)(92726001)(83322001)(54356999)(76176999)(80976001)(46406003)(50986999)(2009001)(33656001)(55846006)(76482001)(81542001)(86362001)(99396002)(81342001)(97736001)(97756001)(77982001)(20776003)(47776003)(79102001); DIR:OUT; SFP:1101; SCL:1; SRVR:BL2PR03MB164; H:mail.microsoft.com; FPR:F08A1415.DC0CC700.6F11FBB.44ED1939.200C8; MLV:sfv; PTR:InfoDomainNonexistent; MX:1; A:1; LANG:en; 
X-O365ENT-EOP-Header: Message processed by -  O365_ENT: Allow from ranges (Engineering ONLY)
X-Forefront-PRVS: 0192E812EC
Received-SPF: Pass (: domain of skype.net designates 131.107.125.37 as permitted sender) receiver=; client-ip=131.107.125.37; helo=mail.microsoft.com;
X-OriginatorOrg: skype.net
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ebGcX7T7u5KqEQE_9EArTn5fXsA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 19:32:14 -0000

Dave Crocker:
>
> The proper model for such an environment is that everyone who participate=
s
> is biased and has an agenda.
>=20

And (with the exception of a few individuals who self-fund their attendance=
 or come from very small orgs) has a legal team back at the home office.

Matthew Kaufman


From nobody Fri Apr 25 13:00:32 2014
Return-Path: <bmanning@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC2FC1A03D7 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 13:00:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.072
X-Spam-Level: 
X-Spam-Status: No, score=-3.072 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 B_PGOR6XSNts for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 13:00:28 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by ietfa.amsl.com (Postfix) with ESMTP id E71F91A03C9 for <ietf@ietf.org>; Fri, 25 Apr 2014 13:00:27 -0700 (PDT)
Received: from [192.168.0.13] (cpe-23-241-118-60.socal.res.rr.com [23.241.118.60]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id s3PJxYru025805 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 25 Apr 2014 12:59:44 -0700 (PDT)
Subject: Re: Author disclosures and conflict of interest
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Content-Type: text/plain; charset=windows-1252
From: manning bill <bmanning@isi.edu>
In-Reply-To: <04ae01cf60a6$bf805510$3e80ff30$@rosenlaw.com>
Date: Fri, 25 Apr 2014 12:59:32 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <75888B3F-B7B2-4D24-A0B6-1148D4CD6687@isi.edu>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>	<CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com>	<037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com> <CAMm+LwhO4a3=O_=xp4Ge8AsFFXnojdH=YKQNoQRsGXiMr88e+g@mail.gmail.com> <04ae01cf60a6$bf805510$3e80ff30$@rosenlaw.com>
To: lrosen@rosenlaw.com
X-Mailer: Apple Mail (2.1874)
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dEWOE9LQJCkwKrKrK4j6g8iK2vY
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 20:00:30 -0000

I=92m going to presume your reference to the National Academies is =
specific to the United States of America.
Since participation in the IETF is from a global perspective,  this begs =
the question of the existence of ethical
rules for engineers & scientists in other jurisdictions, and where they =
do exist, are they in harmony with US=20
standards?


/bill
Neca eos omnes.  Deus suos agnoscet.

On 25April2014Friday, at 9:52, Lawrence Rosen <lrosen@rosenlaw.com> =
wrote:

> Phillip Hallam-Baker asked:
>> So there is only one set of ethical rules for scientists and =
engineers then?
>=20
> Of course not. But before you reject the ethical rules proposed by the =
National Academies (of Science, Engineering, Medicine, and the National =
Research Council), you ought to have a better argument than "I don't =
wanna...."
>=20
> This attitude, unfortunately, diminishes respect for IETF and its =
standards. And nothing confirms that disrespect better than the almost =
complete silence here whenever topics such as this are brought up. It is =
as if IETF standards are generated in an ethical vacuum where "caveat =
emptor" prevails.=20
>=20
> /Larry
>=20
>=20
> -----Original Message-----
> From: Phillip Hallam-Baker [mailto:hallam@gmail.com]=20
> Sent: Thursday, April 24, 2014 1:54 PM
> To: Lawrence Rosen
> Cc: IETF
> Subject: Re: Author disclosures and conflict of interest
>=20
> So there is only one set of ethical rules for scientists and engineers =
then?
>=20
> Thats news to me.
>=20
> On Thu, Apr 24, 2014 at 2:35 PM, Lawrence Rosen <lrosen@rosenlaw.com> =
wrote:
>> Phillip Hallam-Baker wrote:
>>> Like the question 'are you a spy' which they used to ask when people=20=

>>> entered the US, I fail to see how this helps with the =
NSA/FSB/PLA/etc problem.
>>=20
>> The question actually is: Do you agree to the ethical rules for =
scientists and engineers?
>>=20
>> By the way, those ethical rules require only disclosure, not recusal.
>>=20
>> /Larry
>>=20
>>=20
>> -----Original Message-----
>> From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
>> Sent: Monday, April 21, 2014 2:05 PM
>> To: lrosen@rosenlaw.com
>> Cc: IETF Discussion Mailing List
>> Subject: Re: Author disclosures and conflict of interest
>>=20
>> Like the question 'are you a spy' which they used to ask when people =
entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc =
problem.
>>=20
>> The people who are being paid to subvert the standards aren't going =
to say.
>>=20
>> They might not even know that the objective is subversion.
>>=20
>>=20
>> Like many IETF participants I have substantial financial interests in =
several Internet companies besides my employer. Am I meant to put those =
in a blind trust?
>>=20
>> And even if I did all that people would still assume that I am =
working as an agent of the New World Order. Though quite how the other =
folk on the conference call worked out that the helicopter is black =
still puzzles me.
>>=20
>>=20
>> On Sun, Apr 20, 2014 at 1:18 PM, Lawrence Rosen <lrosen@rosenlaw.com> =
wrote:
>>> I=92ve been skimming recent threads  on this list relating to work =
done=20
>>> (or not done) at IETF and was reminded of this from Science =
Magazine:
>>>=20
>>>=20
>>>=20
>>> Authorship Form and Conflict-of-Interest Statement
>>>=20
>>> To meet its responsibility to readers and to the public to provide=20=

>>> clear and unbiased scientific results and analyses, Science believes=20=

>>> that manuscripts (including Brevia, Essays, Perspectives, Policy=20
>>> Forums, Reports, Research Articles, Reviews, and Viewpoints) should=20=

>>> be accompanied by clear disclosures from all authors of the nature=20=

>>> and level of their contribution to the article, their understanding=20=

>>> regarding the obligation to share data and materials, and any=20
>>> affiliations, funding sources, or financial holdings that might =
raise=20
>>> questions about possible sources of bias. Before manuscript=20
>>> acceptance, therefore, authors will be asked to sign an=20
>>> authorship/conflict-of-interest form. Specific information will be =
sent to most authors at the time of manuscript revision.
>>>=20
>>> Authorship Form and Statement of Conflicts of Interest [PDF]
>>>=20
>>>=20
>>>=20
>>> Part IV regarding =93Conflict of Interest=94 is particularly =
relevant to=20
>>> standards organizations such as IETF. Such a disclosure requirement=20=

>>> would further encourage everyone to trust and implement IETF =
specifications.
>>>=20
>>>=20
>>>=20
>>> This document follows the recommendations in On Being a Scientist: A=20=

>>> Guide to Responsible Conduct in Research, The National Academies=20
>>> Press, Third Edition (2009).
>>>=20
>>>=20
>>>=20
>>> /Larry
>>>=20
>>>=20
>>>=20
>>> Lawrence Rosen
>>>=20
>>> Rosenlaw & Einschlag (www.rosenlaw.com)
>>>=20
>>> 3001 King Ranch Road, Ukiah, CA 95482
>>>=20
>>> Cell: 707-478-8932   Fax: 707-485-1243
>>>=20
>>>=20
>>=20
>>=20
>>=20
>> --
>> Website: http://hallambaker.com/
>>=20
>=20
>=20
>=20
> --
> Website: http://hallambaker.com/
>=20


From nobody Fri Apr 25 13:13:58 2014
Return-Path: <randy_presuhn@mindspring.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B15911A031D for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 13:13:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 jZXW2B-EeS18 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 13:13:54 -0700 (PDT)
Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by ietfa.amsl.com (Postfix) with ESMTP id E9D561A02F2 for <ietf@ietf.org>; Fri, 25 Apr 2014 13:13:53 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=mindspring.com; b=qrVW93j6WqP1frIFCqzXGDHW0u7uZJy/9SxmWVFPgn1j6P3cgcZlQi851JhRnLAe; h=Message-ID:Date:From:Reply-To:To:Subject:Cc:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Mailer:X-ELNK-Trace:X-Originating-IP;
Received: from [209.86.224.45] (helo=elwamui-polski.atl.sa.earthlink.net) by elasmtp-dupuy.atl.sa.earthlink.net with esmtpa (Exim 4.67) (envelope-from <randy_presuhn@mindspring.com>) id 1WdmVD-0007sQ-JQ; Fri, 25 Apr 2014 16:13:43 -0400
Received: from 76.254.55.64 by webmail.earthlink.net with HTTP; Fri, 25 Apr 2014 16:13:42 -0400
Message-ID: <20335284.1398456823404.JavaMail.root@elwamui-polski.atl.sa.earthlink.net>
Date: Fri, 25 Apr 2014 13:13:42 -0700 (GMT-07:00)
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: manning bill <bmanning@isi.edu>, lrosen@rosenlaw.com
Subject: Re: Author disclosures and conflict of interest
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-Mailer: EarthLink Zoo Mail 1.0
X-ELNK-Trace: 4488c18417c9426da92b9037bc8bcf44d4c20f6b8d69d88891b749bef7332bbc2f884744ff8facdf6920c559bc4d419c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 209.86.224.45
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0esa6SCeDQDvHV1k6M94pMSzhko
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Randy Presuhn <randy_presuhn@mindspring.com>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 20:13:56 -0000

Hi -

>From: manning bill <bmanning@isi.edu>
>Sent: Apr 25, 2014 12:59 PM
>To: lrosen@rosenlaw.com
>Cc: IETF <ietf@ietf.org>
>Subject: Re: Author disclosures and conflict of interest
...
>Since participation in the IETF is from a global perspective,
>this begs the question of the existence of ethical
>rules for engineers & scientists in other jurisdictions,
>and where they do exist, are they in harmony with US 
>standards?

Perhaps it would make sense to start with
two global professional organizations in the field,
such as http://www.acm.org/about/code-of-ethics
or http://www.ieee.org/about/corporate/governance/p7-8.html

I'd think that a fair number of IETF participants might
belong to one or both of these professional societies.

Randy


From nobody Fri Apr 25 13:44:56 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CA5B1A03DF for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 13:44:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 uVaeU2Z9Fb0o for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 13:44:50 -0700 (PDT)
Received: from mail-pa0-x235.google.com (mail-pa0-x235.google.com [IPv6:2607:f8b0:400e:c03::235]) by ietfa.amsl.com (Postfix) with ESMTP id 530CD1A0354 for <ietf@ietf.org>; Fri, 25 Apr 2014 13:44:50 -0700 (PDT)
Received: by mail-pa0-f53.google.com with SMTP id ld10so3554462pab.40 for <ietf@ietf.org>; Fri, 25 Apr 2014 13:44:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=YmFNQ8z1J8VDEClZpoqDw4pqt3dkc/8k5prg2z8P5qM=; b=Qv+D409Na7p8LPwYvITfZkt3FGGR5sQH8n7rYOKEpWkGKKbj1XwszEXm7fEPJe6tYH HRAQY9FFAkFiQq2aF+Q6B7U+wbZXe2NSHBsAlzD4IXaMxmHxrisi49f11szljyvfAJ+a mqNj4aduap0kz1Afa4rO01C4ltll7Ylq2S8VXY2OOPt2ZIFDfYn4pYgKGy4CD5h1U5yS 05J+m+vZa9kJhjP4S2qZUQmR8RzEUPvCosdrnB12ZyjRKAn4KOiKBDFV0OXVD0UwEFgP Go5+fMOJl1QdMt6H/aSrUioF0l+Cau8+a3IQqCT0Waqr4QeDPIPFmEuJvMn8OiHA9GYD jSPw==
X-Received: by 10.66.181.70 with SMTP id du6mr10484271pac.23.1398458683935; Fri, 25 Apr 2014 13:44:43 -0700 (PDT)
Received: from [192.168.178.20] (65.199.69.111.dynamic.snap.net.nz. [111.69.199.65]) by mx.google.com with ESMTPSA id qw8sm17939941pbb.27.2014.04.25.13.44.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Apr 2014 13:44:43 -0700 (PDT)
Message-ID: <535AC944.10900@gmail.com>
Date: Sat, 26 Apr 2014 08:44:52 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Presuhn <randy_presuhn@mindspring.com>
Subject: Re: Author disclosures and conflict of interest
References: <20335284.1398456823404.JavaMail.root@elwamui-polski.atl.sa.earthlink.net>
In-Reply-To: <20335284.1398456823404.JavaMail.root@elwamui-polski.atl.sa.earthlink.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tIdlr4ZDwm3L7uB7y7knfOxkHKQ
Cc: IETF <ietf@ietf.org>, manning bill <bmanning@isi.edu>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 20:44:53 -0000

On 26/04/2014 08:13, Randy Presuhn wrote:
> Hi -
> 
>> From: manning bill <bmanning@isi.edu>
>> Sent: Apr 25, 2014 12:59 PM
>> To: lrosen@rosenlaw.com
>> Cc: IETF <ietf@ietf.org>
>> Subject: Re: Author disclosures and conflict of interest
> ...
>> Since participation in the IETF is from a global perspective,
>> this begs the question of the existence of ethical
>> rules for engineers & scientists in other jurisdictions,
>> and where they do exist, are they in harmony with US 
>> standards?
> 
> Perhaps it would make sense to start with
> two global professional organizations in the field,
> such as http://www.acm.org/about/code-of-ethics
> or http://www.ieee.org/about/corporate/governance/p7-8.html
> 
> I'd think that a fair number of IETF participants might
> belong to one or both of these professional societies.

ISOC also has a code of conduct:
http://www.internetsociety.org/get-involved/join-community/individuals/code-conduct
It was written after looking at various other codes, including IEEE, ACM
and IFIP. Among other things, it says:

"In the case of financial or material conflict between personal and
professional interests, or between two professional interests, declare
this conflict to all interested parties and if appropriate in public."

Full disclosure: I had a hand in drafting this, while on the ISOC Board.

   Brian


From nobody Fri Apr 25 13:50:52 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BDA11A06A8 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 13:50:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 Wlsr_f-6Uvs2 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 13:50:47 -0700 (PDT)
Received: from mail-pb0-x22a.google.com (mail-pb0-x22a.google.com [IPv6:2607:f8b0:400e:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BA7071A03DF for <ietf@ietf.org>; Fri, 25 Apr 2014 13:50:47 -0700 (PDT)
Received: by mail-pb0-f42.google.com with SMTP id un15so3608356pbc.29 for <ietf@ietf.org>; Fri, 25 Apr 2014 13:50:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=yReoD3XzukiCRi3Ts1SjcrHLwVT9pPtUxOD+dM8pS2s=; b=r7+Jzsv53AFh+mdJoU/E47+/iIafsQYEtDoHbGwgzGYVo6qyZRUZK13LeoRPZdO6KV FNcBm9DnihQEJswGOKOmlD6BwS98V+pvOn+DJAR3aiepY7dRoY7/9MgHs6wT/EipNXlS qPSs/h5TbWqOGfROnrFLtpqFTwO4uCkUlvxGhUVvofMMk9Jku/dbgcP+I9MeY9cmuSSB hxrWtStV76d7BxVOqACUgV9BJUcz7qNqHdqNXSY2ZfbjIzycy0tpkS2Hi4C7wz+2jaVO 9iwZiWh1vmmTvVQ+W1OsPb4d1mT1S7rVm+YRM4uboFiKQW+srMem0slQ7bmHwqncBKUq 0sYg==
X-Received: by 10.68.227.4 with SMTP id rw4mr13986671pbc.3.1398459041387; Fri, 25 Apr 2014 13:50:41 -0700 (PDT)
Received: from [192.168.178.20] (65.199.69.111.dynamic.snap.net.nz. [111.69.199.65]) by mx.google.com with ESMTPSA id di3sm17980483pbc.11.2014.04.25.13.50.38 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Apr 2014 13:50:40 -0700 (PDT)
Message-ID: <535ACAAA.10001@gmail.com>
Date: Sat, 26 Apr 2014 08:50:50 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: Author disclosures and conflict of interest
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net>
In-Reply-To: <535A9F58.1080105@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pkIPMi0JUBT1iCajtKHBz1tygNU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 20:50:49 -0000

On 26/04/2014 05:46, Dave Crocker wrote:
...
> The proper model for such an environment is that everyone who
> participates is biased and has an agenda.

Which is, I believe, one of the fundamental reasons why we don't
vote in the IETF and do attempt to judge consensus on the basis
of technical arguments rather than head counts.

    Brian


From nobody Fri Apr 25 14:29:16 2014
Return-Path: <farmer@umn.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB6731A03D9 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 14:29:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.472
X-Spam-Level: 
X-Spam-Status: No, score=-4.472 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 wCUipo9EWiCB for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 14:29:01 -0700 (PDT)
Received: from vs-m.tc.umn.edu (vs-m.tc.umn.edu [134.84.135.97]) by ietfa.amsl.com (Postfix) with ESMTP id 215C61A03D8 for <ietf@ietf.org>; Fri, 25 Apr 2014 14:29:00 -0700 (PDT)
Received: from mail-ig0-f177.google.com (mail-ig0-f177.google.com [209.85.213.177]) by vs-m.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Fri, 25 Apr 2014 16:28:49 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ig0-f177.google.com [209.85.213.177] #+LO+TS+TR
X-Umn-Classification: local
Received: by mail-ig0-f177.google.com with SMTP id h3so2719070igd.16 for <ietf@ietf.org>; Fri, 25 Apr 2014 14:28:49 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=Ol7xP9t6Xux3l7Qc5R40NTZIu2JjEsoipj3qOlAa/KM=; b=bZ4azyEOdsfPyftAcVN3SPDfAn93ZMAfhWXxMqg+E6w+L+nVVXGzIhVrm7911rZRdc R+IlHLppokAfxtPOOeX9g+OT66GXYr5cZI2LyT/x6gYVyR5F4ZUQu1oxl3EQhGY/PfPa fd9dTS+rWL/20i69ayGz6Pincbd5/JPo/e31b4XpgIScIcLqe2ZD+ETUyMdDSCB3oy04 smKgw84Xfk2ej5CiIYmx/JVCYL2+XA6MtftBQaQlSVJsqXbjNNqCJJ0oo4gJXFPVTZUK eo07EndJ0bt90Mv4S3HIXxFE4GjE4FUlE7CFpna2GlyWdedXXZT+y4czOSNcoVjLS45j Zf7w==
X-Gm-Message-State: ALoCoQkn2RbsPu4D6U16FoGOyi4Dc3vfU/HrFCaj+pvi/QQAi5m1oJZIxlOCpR6m7teRazmJr1gHmVeq2wzQHPxlHYuwoBlgV+7DTvhC2cjYrRLl8LcUM/U=
X-Received: by 10.50.32.70 with SMTP id g6mr8065074igi.0.1398461329095; Fri, 25 Apr 2014 14:28:49 -0700 (PDT)
X-Received: by 10.50.32.70 with SMTP id g6mr8065038igi.0.1398461328697; Fri, 25 Apr 2014 14:28:48 -0700 (PDT)
Received: from x-128-101-235-107.uofm-secure.wireless.umn.edu (x-128-101-235-107.uofm-secure.wireless.umn.edu. [128.101.235.107]) by mx.google.com with ESMTPSA id qh3sm11874032igb.17.2014.04.25.14.28.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Apr 2014 14:28:47 -0700 (PDT)
Message-ID: <535AD38E.4030703@umn.edu>
Date: Fri, 25 Apr 2014 16:28:46 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: lrosen@rosenlaw.com, 'IETF' <ietf@ietf.org>
Subject: Re: Author disclosures and conflict of interest
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com>	<CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com>	<037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com> <CAMm+LwhO4a3=O_=xp4Ge8AsFFXnojdH=YKQNoQRsGXiMr88e+g@mail.gmail.com> <04ae01cf60a6$bf805510$3e80ff30$@rosenlaw.com> <CE39F90A45FF0C49A1EA229FC9899B0507D579EC@USCLES544.agna.amgreetings.com> <04de01cf60ad$6cd48730$467d9590$@rosenlaw.com>
In-Reply-To: <04de01cf60ad$6cd48730$467d9590$@rosenlaw.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-aPHz6dLg8px0xQE9GQh0zEyoOs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Apr 2014 21:29:11 -0000

So, in the IETF this is intended to be at least partially addressed by 
participants making known their name and affiliations, when they talk at 
the mic, author's affiliations are included in documents, etc... 
Participation in the IETF is not suppose to be anonymous, even though 
that side of this discussion comes up from time to time as well.

I think this works for the most part, most of the time.  When you 
introduce yourself as John Doe, Mega Network Vendor, or David Farmer, 
University of Minnesota, that gives you some clue of the interests being 
represented to one extent or another.  However there is a bit of problem 
comes with Joe Shmoe, Nonsense-word Consultants, what or who's interests 
is Joe representing is frequently not obvious.

I'll also note that some authors cover part of this issue in the 
acknowledgments section, especially in the case of funded research, by 
acknowledging and disclosing that funding.

Another side of the discussion, what kind of barrier to participation 
would formal disclosure requirements for authors create?  This is just 
as much a concern as what biased or agenda an author may have.

I personally appreciate you raising the question, but as with most 
ethical questions, there isn't an easy answer one way or the other.  I 
fear formal author disclosure requirements are likely to be onerous, and 
create a barrier to participation.  Because of the consensus basis of 
the IETF processes, easy and open participation is equally important as 
disclosure of conflicts of interest.

I think the best we can do is encourage everyone to voluntarily disclose 
the interests they represent and for authors in particular to 
acknowledge non-obvious interests they may be representing; being any 
interests that are not be obvious from their stated affiliation.

Thanks

On 4/25/14, 12:40 , Lawrence Rosen wrote:
> Mike Hammer asked:
>
>  > The nice thing about codes of ethics is that there are so many to
> choose from.
>
>  > Which one are we supposed to be looking at?
>
> This one from /Science Magazine
> <http://www.sciencemag.org/site/feature/contribinfo/prep/coi.xhtml> /is
> the one I suggested in my initial email in this thread:
>
>
>     Authorship Form and Conflict-of-Interest Statement
>
> To meet its responsibility to readers and to the public to provide clear
> and unbiased scientific results and analyses,/Science/believes that
> manuscripts (including Brevia, Essays, Perspectives, Policy Forums,
> Reports, Research Articles, Reviews, and Viewpoints) should be
> accompanied by clear disclosures from all authors of the nature and
> level of their contribution to the article, their understanding
> regarding the obligation to share data and materials, and any
> affiliations, funding sources, or financial holdings that might raise
> questions about possible sources of bias. Before manuscript acceptance,
> therefore, authors will be asked to sign an
> authorship/conflict-of-interest form. Specific information will be sent
> to most authors at the time of manuscript revision.
>
> Authorship Form and Statement of Conflicts of Interest
> <http://www.sciencemag.org/site/feature/contribinfo/prep/coi.pdf>[PDF]
>
> As you say, there are othersâ€¦.
>
> /Larry
>
> -----Original Message-----
> From: MH Michael Hammer (5304) [mailto:MHammer@ag.com]
> Sent: Friday, April 25, 2014 10:18 AM
> To: lrosen@rosenlaw.com; 'IETF'
> Subject: RE: Author disclosures and conflict of interest
>
>  > -----Original Message-----
>
>  > From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Lawrence Rosen
>
>  > Sent: Friday, April 25, 2014 12:52 PM
>
>  > To: 'IETF'
>
>  > Subject: RE: Author disclosures and conflict of interest
>
>  >
>
>  > Phillip Hallam-Baker asked:
>
>  > > So there is only one set of ethical rules for scientists and
> engineers then?
>
>  >
>
>  > Of course not. But before you reject the ethical rules proposed by the
>
>  > National Academies (of Science, Engineering, Medicine, and the
>
>  > National Research Council), you ought to have a better argument than
>
>  > "I don't wanna...."
>
>  >
>
>  > This attitude, unfortunately, diminishes respect for IETF and its
> standards.
>
>  > And nothing confirms that disrespect better than the almost complete
>
>  > silence here whenever topics such as this are brought up. It is as if
>
>  > IETF standards are generated in an ethical vacuum where "caveat emptor"
>
>  > prevails.
>
>  >
>
>  > /Larry
>
>  >
>
> I took the time to look at the website http://www.onlineethics.org/
> related to ethics as indicated by the National Academy of Engineering. I
> didn't find a code of ethics from the Academy but instead found links to
> a whole bunch of other sites -
> http://www.onlineethics.org/Resources/ethcodes/EnglishCodes.aspx. The
> nice thing about standards is that there are so many to choose from. The
> nice thing about codes of ethics is that there are so many to choose
> from. Which one are we supposed to be looking at?
>
> Mike
>
>  >
>
>  > -----Original Message-----
>
>  > From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
>
>  > Sent: Thursday, April 24, 2014 1:54 PM
>
>  > To: Lawrence Rosen
>
>  > Cc: IETF
>
>  > Subject: Re: Author disclosures and conflict of interest
>
>  >
>
>  > So there is only one set of ethical rules for scientists and
> engineers then?
>
>  >
>
>  > Thats news to me.
>
>  >
>
>  > On Thu, Apr 24, 2014 at 2:35 PM, Lawrence Rosen <lrosen@rosenlaw.com
> <mailto:lrosen@rosenlaw.com>>
>
>  > wrote:
>
>  > > Phillip Hallam-Baker wrote:
>
>  > >> Like the question 'are you a spy' which they used to ask when
>
>  > >> people entered the US, I fail to see how this helps with the
>
>  > >> NSA/FSB/PLA/etc
>
>  > problem.
>
>  > >
>
>  > > The question actually is: Do you agree to the ethical rules for
>
>  > > scientists and
>
>  > engineers?
>
>  > >
>
>  > > By the way, those ethical rules require only disclosure, not recusal.
>
>  > >
>
>  > > /Larry
>
>  > >
>
>  > >
>
>  > > -----Original Message-----
>
>  > > From: Phillip Hallam-Baker [mailto:hallam@gmail.com]
>
>  > > Sent: Monday, April 21, 2014 2:05 PM
>
>  > > To: lrosen@rosenlaw.com <mailto:lrosen@rosenlaw.com>
>
>  > > Cc: IETF Discussion Mailing List
>
>  > > Subject: Re: Author disclosures and conflict of interest
>
>  > >
>
>  > > Like the question 'are you a spy' which they used to ask when people
>
>  > entered the US, I fail to see how this helps with the NSA/FSB/PLA/etc
>
>  > problem.
>
>  > >
>
>  > > The people who are being paid to subvert the standards aren't going
> to say.
>
>  > >
>
>  > > They might not even know that the objective is subversion.
>
>  > >
>
>  > >
>
>  > > Like many IETF participants I have substantial financial interests
>
>  > > in several
>
>  > Internet companies besides my employer. Am I meant to put those in a
>
>  > blind trust?
>
>  > >
>
>  > > And even if I did all that people would still assume that I am
>
>  > > working as an
>
>  > agent of the New World Order. Though quite how the other folk on the
>
>  > conference call worked out that the helicopter is black still puzzles me.
>
>  > >
>
>  > >
>
>  > > On Sun, Apr 20, 2014 at 1:18 PM, Lawrence Rosen
>
>  > > <lrosen@rosenlaw.com <mailto:lrosen@rosenlaw.com>>
>
>  > wrote:
>
>  > >> Iâ€™ve been skimming recent threads  on this list relating to work
>
>  > >> done (or not done) at IETF and was reminded of this from Science
> Magazine:
>
>  > >>
>
>  > >>
>
>  > >>
>
>  > >> Authorship Form and Conflict-of-Interest Statement
>
>  > >>
>
>  > >> To meet its responsibility to readers and to the public to provide
>
>  > >> clear and unbiased scientific results and analyses, Science
>
>  > >> believes that manuscripts (including Brevia, Essays, Perspectives,
>
>  > >> Policy Forums, Reports, Research Articles, Reviews, and Viewpoints)
>
>  > >> should be accompanied by clear disclosures from all authors of the
>
>  > >> nature and level of their contribution to the article, their
>
>  > >> understanding regarding the obligation to share data and materials,
>
>  > >> and any affiliations, funding sources, or financial holdings that
>
>  > >> might raise questions about possible sources of bias. Before
>
>  > >> manuscript acceptance, therefore, authors will be asked to sign an
>
>  > >> authorship/conflict-of-interest form. Specific information will be
>
>  > >> sent to
>
>  > most authors at the time of manuscript revision.
>
>  > >>
>
>  > >> Authorship Form and Statement of Conflicts of Interest [PDF]
>
>  > >>
>
>  > >>
>
>  > >>
>
>  > >> Part IV regarding â€œConflict of Interestâ€� is particularly relevant
>
>  > >> to standards organizations such as IETF. Such a disclosure
>
>  > >> requirement would further encourage everyone to trust and implement
>
>  > >> IETF
>
>  > specifications.
>
>  > >>
>
>  > >>
>
>  > >>
>
>  > >> This document follows the recommendations in On Being a Scientist:
>
>  > >> A Guide to Responsible Conduct in Research, The National Academies
>
>  > >> Press, Third Edition (2009).
>
>  > >>
>
>  > >>
>
>  > >>
>
>  > >> /Larry
>
>  > >>
>
>  > >>
>
>  > >>
>
>  > >> Lawrence Rosen
>
>  > >>
>
>  > >> Rosenlaw & Einschlag (www.rosenlaw.com <http://www.rosenlaw.com>)
>
>  > >>
>
>  > >> 3001 King Ranch Road, Ukiah, CA 95482
>
>  > >>
>
>  > >> Cell: 707-478-8932   Fax: 707-485-1243
>
>  > >>
>
>  > >>
>
>  > >
>
>  > >
>
>  > >
>
>  > > --
>
>  > > Website: http://hallambaker.com/
>
>  > >
>
>  >
>
>  >
>
>  >
>
>  > --
>
>  > Website: http://hallambaker.com/
>


-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================


From nobody Fri Apr 25 21:15:35 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50A11A044B for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 21:15:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 CmpOku-gRjP4 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 21:15:31 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id AB2391A02FB for <ietf@ietf.org>; Fri, 25 Apr 2014 21:15:31 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id x10so395249pdj.15 for <ietf@ietf.org>; Fri, 25 Apr 2014 21:15:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=G0Nh+RzezWW8wqdRtlENhEZo2zZ+BLhqgB4dbWWBrWs=; b=UzRLMgFFoM5Va6cqAyFmtksxEuT6vZU1X5H3CtTbFWWJqUHrFMyYxfHZzNsLblrInV y/uGDdOcymhFbRDf1t1h9AGf3UQbdu7QinqsKXV5c26SD5UdogWKb/+2bHS5maveIOwT LUuMDz/G/2v451nOPCS2dojl/1jR0Nwgrz8YaHj4oI6Qv0nMHbOR7TLWqK6EpORMP5F2 sV/ouWtDRle5ZXK98lyN9OWgnelxOyvbahL0x7jvbhmx8xI9FAuVC1nkJqtio/Hh/wIk ZeB4nyAee+FCcr/2uOCcs96R+Nq3SYK8Qs67fRQzD3xV20f+N28InzJoVxUeqlXhN9Bx qBNg==
X-Received: by 10.68.96.225 with SMTP id dv1mr15767154pbb.30.1398485725113; Fri, 25 Apr 2014 21:15:25 -0700 (PDT)
Received: from [192.168.178.20] (65.199.69.111.dynamic.snap.net.nz. [111.69.199.65]) by mx.google.com with ESMTPSA id et3sm19483839pbc.52.2014.04.25.21.15.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 25 Apr 2014 21:15:24 -0700 (PDT)
Message-ID: <535B32E7.10105@gmail.com>
Date: Sat, 26 Apr 2014 16:15:35 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net>
In-Reply-To: <535A7D87.6080200@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Q6sn-XrQdzd7wV2Dh5o9-evIN4c
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2014 04:15:33 -0000

On 26/04/2014 03:21, Dave Crocker wrote:
> On 4/25/2014 7:56 AM, Ned Freed wrote:

...
>> And maybe something has changed since the four years I spent going to
>> IESG retreats, but I recall lots of discussion of how the IETF as an
>>  organization should respond to various industry trends.
> 
> Yes, we often have such discussions.  My observation is that it has
> typically had little or no effect on what work is actually done, absent
> initiative from the community.

I don't think that's completely fair. Yes, of course nothing will
get done unless there are people willing to do it. But if the
IAB holds a workshop on ploomdoogleblits, which will undoubtedly
include some IESG members and some people who aren't members of
the I* at all, some ideas will emerge about how the IETF should
respond to the ploomdoogleblit work that is going on in academia or
industry. Drafts will appear, apparently from the "bottom", and
a BOF proposal maybe - which certain IESG members will be ready
to pay attention to, because they were at the ploomdoogleblit
workshop.

Of course that's not the only path to getting work into the
IETF, but it's one of the paths, and it happens. (Maybe it
would happen more if the IAB became the Internet Innovation
Board.)

    Brian


From nobody Fri Apr 25 22:02:08 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 674E01A06F7 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 22:01:51 -0700 (PDT)
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] autolearn=ham
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 idGuBjAfvu8g for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 22:01:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id CBC091A06FA for <ietf@ietf.org>; Fri, 25 Apr 2014 22:01:48 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3Q51bJA020480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 25 Apr 2014 22:01:41 -0700
Message-ID: <535B3D2B.3030503@dcrocker.net>
Date: Fri, 25 Apr 2014 21:59:23 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <535B32E7.10105@gmail.com>
In-Reply-To: <535B32E7.10105@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Fri, 25 Apr 2014 22:01:41 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fJyKKZd3h9T6uWL_1kAMjTi3jHA
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2014 05:01:51 -0000

On 4/25/2014 9:15 PM, Brian E Carpenter wrote:
>   But if the
> IAB holds a workshop on ploomdoogleblits, which will undoubtedly
> include some IESG members and some people who aren't members of
> the I* at all, some ideas will emerge about how the IETF should
> respond to the ploomdoogleblit work that is going on in academia or
> industry. Drafts will appear,


It could be interesting to document this presumed cause/effect relationship.

Start with a listing of every workshop.  Then indicate the related I-Ds 
that were initiated afterwards.  Then indicate which ones made it to RFC.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sat Apr 26 07:22:37 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65ACD1A0651 for <ietf@ietfa.amsl.com>; Sat, 26 Apr 2014 07:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.062
X-Spam-Level: 
X-Spam-Status: No, score=-2.062 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.272, T_DKIM_INVALID=0.01] autolearn=ham
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 8xtjSl_hw1yK for <ietf@ietfa.amsl.com>; Sat, 26 Apr 2014 07:22:31 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B6451A04B9 for <ietf@ietf.org>; Sat, 26 Apr 2014 07:22:31 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.141.17]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3QEM8Z0007391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 26 Apr 2014 07:22:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398522140; bh=/IdAIAlQoau/BbZgUch1Cq18TA9BV05wlE0bW6oG2/0=; h=Date:To:From:Subject:In-Reply-To:References; b=XCeJcDh6dJia1484bag0c1v/2GzPuX76raQpXaaGf8Y+SNyRLwZCD7WzwolCrDbgG U3xlYJlNJxZ5ZrOjpj5lEUOUX1jCy75XcR0Gs61tI/tZ4b60Q8EgeVYZiXXn262Hqc 8NrCH37cgCFsiZ94qojZWKQ0TZu58VfysB79+/Q4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398522140; i=@elandsys.com; bh=/IdAIAlQoau/BbZgUch1Cq18TA9BV05wlE0bW6oG2/0=; h=Date:To:From:Subject:In-Reply-To:References; b=L46EwTcU+nyyp66usmOKDQUnuKRX5Xb9v1YG1Xuk7nV7SOtUYwcba9pYQfTc/PUG/ 5T6ilJpWJXMszfakuMcn0+UqXSLa1rG5DIDpWH8zb4oWDSl1UiGYJrNhBIxX35q7Ob KmvI7kPvrW/QtclbABaxiX5ro7gZWjRT5HOfuO9E=
Message-Id: <6.2.5.6.2.20140426052032.0af9e9a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 26 Apr 2014 06:50:49 -0700
To: lrosen@rosenlaw.com, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: RE: Author disclosures and conflict of interest
In-Reply-To: <04ee01cf60b3$b079f9b0$116ded10$@rosenlaw.com>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net> <04ee01cf60b3$b079f9b0$116ded10$@rosenlaw.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RQUKFqpzaLQoom3BKc-FOl_0efQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2014 14:22:35 -0000

Hi Larry,
At 11:25 25-04-2014, Lawrence Rosen wrote:
>We all expect bias in standards organizations -- indeed it is a irreducible
>factor in science and engineering and all human endeavors (and particularly
>so in my profession, law!). I don't think anyone here is na=EFve about=
 that.
>
>Please don't demand more than is possible out of an ethics policy. But also
>please don't give up the moral high ground just because we all fall short=
 of
>moral perfection. There is a middle way: Disclosure of potential conflicts
>of interest that allows each of us to judge those biases for ourselves.

I chose three companies from various parts of the world.

http://www.ntt.co.jp/csr_e/compliance.html
http://www.raytheon.com/ourcompany/ourculture/ethics/index.html
http://www.teliasonera.com/en/about-us/

They all mentioned ethics.  I assume that=20
companies which consider themselves as reputable=20
would ensure that their employees and people=20
under contract with them will follow their ethics=20
policy.  If the policy covers disclosure of=20
potential conflicts of interest it can be assumed=20
that the employees participating in the IETF will=20
make the information publicly known.  If there=20
isn't such a policy it can be assumed that the=20
company's reputation is based on some marketing trick.

The above does not try to find any moral high=20
ground.  It avoids the standards organization=20
problem as the IETF does not have a=20
membership.  The IESG response at=20
http://www.ietf.org/iesg/appeal/response-to-masotta-2013-11-14.html=20
may be of interest as ethics and conflict of interest are mentioned.

Regards,
S. Moonesamy



From nobody Sat Apr 26 10:29:03 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C28DF1A0639 for <ietf@ietfa.amsl.com>; Sat, 26 Apr 2014 10:29:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 Td1VubbvKEVp for <ietf@ietfa.amsl.com>; Sat, 26 Apr 2014 10:29:00 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id E5E581A0268 for <ietf@ietf.org>; Sat, 26 Apr 2014 10:28:59 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id pn19so3894096lab.6 for <ietf@ietf.org>; Sat, 26 Apr 2014 10:28:52 -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:content-type; bh=OqEfAYxqkVWid6hAGbT4luphs27ERpf37OWPQXqJ66E=; b=tEQEWyywWv1WlAVWEz2hm5VWeoOooqk6GeD/LXB5V/+NxbyELP6+LBOIXGdeivhl8j cK3+4juL1bRqOY3xqss0pGKQERXiXDovIUl1gdbwAXBHvicDPlQXYo97sXJ+d1c/oYXm 0+hwFYkrCeb1aH6NUybgE5M2ZjmsdOA9X8BirGajuPp4ghyfshNEfr08m9pFgFUmaceV 4j7fQMhrQwuV+WmsR9pL8f4xklKLlD/vl0T/NyJwF72AjKG1TWtWBnOFMtS7+r3LP17n vQhlOXcHpuHRJepTAX/2lGoj8KS4U6dL9m3NWL/8tHwejuU3N5OMoODsyfxWc4gXME7c tH9g==
MIME-Version: 1.0
X-Received: by 10.152.42.144 with SMTP id o16mr11035924lal.9.1398533332430; Sat, 26 Apr 2014 10:28:52 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Sat, 26 Apr 2014 10:28:52 -0700 (PDT)
In-Reply-To: <535A7D87.6080200@dcrocker.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net>
Date: Sat, 26 Apr 2014 13:28:52 -0400
Message-ID: <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.gmail.com>
Subject: Re: The IETF environment
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tScZNQcx-POf7H0lt8huE6QidZY
Cc: ned+ietf@mauve.mrochek.com, Ned Freed <ned.freed@mrochek.com>, IETF Discussion Mailing List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2014 17:29:02 -0000

On Fri, Apr 25, 2014 at 11:21 AM, Dave Crocker <dhc@dcrocker.net> wrote:
> On 4/25/2014 7:56 AM, Ned Freed wrote:
>>
>> An obvious counterexample is what recently happened in perpass and
>> the various works it has started. Regardless of what anyone thinks of
>> perpass or its outcome, a fair characterization is that it was an
>> IETF repsonse to the message delivered by Snoden et al.
>
>
> Yup.  It's a singular example, but that's the point.  It's not what the IETF
> (usually) does.
>
> It's fine that it's being attempted and it might (or might not) prove
> useful.  But there is no pattern of the IETF doing such a thing.

There is really no precedent for discovering that a rogue agency was
conspiring to sabotage efforts to provide Internet security.

It is not just the IETF that has ben responding in unusual ways.

For the past thirty years we have been building a technology trap that
civilization now depends on. And anyone who looks into the structure
of that technology trap will realize that all the critical
infrastructure is now linked to the net in ways that can create
enormous amounts of fear and panic albeit with little risk of
catastrophic consequences.

Fear and panic are themselves capable of creating serious
consequences, consider that the response to 9/11 was to start not just
one but two wars.

And now we find that the government agency charged with COMSEC
assurance was actually committing resources to subverting COMSEC
efforts. In many cases efforts that were funded by other parts of the
US government.

This is really not a usual situation at all.

-- 
Website: http://hallambaker.com/


From nobody Sat Apr 26 15:16:57 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B0171A0663 for <ietf@ietfa.amsl.com>; Sat, 26 Apr 2014 15:16:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.973
X-Spam-Level: 
X-Spam-Status: No, score=-0.973 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.272] autolearn=ham
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 l81c0pWErfFQ for <ietf@ietfa.amsl.com>; Sat, 26 Apr 2014 15:16:53 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5C6E61A0676 for <ietf@ietf.org>; Sat, 26 Apr 2014 15:16:53 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WeAtd-0003M3-0T; Sat, 26 Apr 2014 18:16:33 -0400
Date: Sat, 26 Apr 2014 18:16:27 -0400
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>, lrosen@rosenlaw.com, ietf@ietf.org
Subject: RE: Author disclosures and conflict of interest
Message-ID: <5565517810D977C4F53EC65F@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20140426052032.0af9e9a0@resistor.net>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net> <04ee01cf60b3$b079f9b0$116ded10$@rosenlaw.com> <6.2.5.6.2.20140426052032.0af9e9a0@resistor.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GZO9iFM4cZRRjqfuvod97T7RudY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2014 22:16:55 -0000

--On Saturday, April 26, 2014 06:50 -0700 S Moonesamy
<sm+ietf@elandsys.com> wrote:

> Hi Larry,
> At 11:25 25-04-2014, Lawrence Rosen wrote:
>> We all expect bias in standards organizations -- indeed it is
>> a irreducible factor in science and engineering and all human
>> endeavors (and particularly so in my profession, law!). I
>> don't think anyone here is na=C3=AFve about that.
>...
> I chose three companies from various parts of the world.
>...
> They all mentioned ethics.  I assume that companies which
> consider themselves as reputable would ensure that their
> employees and people under contract with them will follow
>...

Hi.

I think there is a useful discussion in this area that the IETF
should be having.  I also think that discussion is easily
diverted into ratholes, whether through good intentions or a
desire to head off any action.

Referring back to comments I made early in this thread or what
lead to it, I don't think we need more procedural rules here.
One the reasons for that is that an attempt to get to them leads
us straight into the hairsplitting debate into which the latest
notes seem to point.

I think what I believe was Larry's core point is well-taken: a
large fraction of us have already committed to various
statements of professional ethics and the rest of us should, as
a matter of professionalism and good relationships, behave as if
we had.  I'm also not particularly concerned about the
situations in which an employee of Company XYZ is promoting a
protocol in which Company XYZ is a known advocate or stands to
profit.  Most of the important elements of those situations are
covered by our IPR rules and most of the rest are pretty
obvious.   Where I think we have a potential problem involves
situations in which the core work to produce a standard (or
other specification) may be going on in an industry consortium
whose membership and participation (including, e.g., consulting
and seconded personnel relationship) are not obvious. =20

If the work of such a consortium is public or generally
available for use without specific licensing, there are no IPR
issues (and disclosures probably identify the consortium, not
the contributors).  But suppose the IETF is asked to approve the
results, an AD sponsors a document, the RFC Editor is asked to
publish them or parts of them in _any_ stream, IANA registries
are created or used, expert reviewers are appointed and review
requests, or similar actions are proposed or taken.   I think
the community should then know involvements that might be
associated with biases or conflicts of assumptions, and that
those disclosures should occur as a matter of personal integrity
and ethics. =20

    john


From nobody Sun Apr 27 16:26:10 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE9581A07CA for <ietf@ietfa.amsl.com>; Sun, 27 Apr 2014 16:26:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.352
X-Spam-Level: 
X-Spam-Status: No, score=-1.352 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 k7K-iOQtZJ3U for <ietf@ietfa.amsl.com>; Sun, 27 Apr 2014 16:26:07 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 5301C1A07C8 for <ietf@ietf.org>; Sun, 27 Apr 2014 16:26:07 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WeYSM-0004v4-CV; Sun, 27 Apr 2014 19:25:58 -0400
Date: Sun, 27 Apr 2014 19:25:53 -0400
From: John C Klensin <john-ietf@jck.com>
To: David Farmer <farmer@umn.edu>, lrosen@rosenlaw.com, 'IETF' <ietf@ietf.org>
Subject: Re: Author disclosures and conflict of interest
Message-ID: <CFB91D00CC725FE7FF75442D@JcK-HP8200.jck.com>
In-Reply-To: <535AD38E.4030703@umn.edu>
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <CAMm+LwgEa0Sgax16987Xdbxi8k03VK5gb9QR=MKZrsi5kVKreA@mail.gmail.com> <037c01cf5feb$f3696e40$da3c4ac0$@rosenlaw.com> <CAMm+LwhO4a3=O_=xp4Ge8AsFFXnojdH=YKQNoQRsGXiMr88e+g@mail.gmail.com> <04ae01cf60a6$bf805510$3e80ff30$@rosenlaw.com> <CE39F90A45FF0C49A1EA229FC9899B0507D579EC@USCLES544.agna.amgreetings.com> <04de01cf60ad$6cd48730$467d9590$@rosenlaw.com> <535AD38E.4030703@umn.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/drAaWXxfg4QreswSLHnowgvYfbI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Apr 2014 23:26:09 -0000

--On Friday, April 25, 2014 16:28 -0500 David Farmer
<farmer@umn.edu> wrote:

>...
> I think the best we can do is encourage everyone to
> voluntarily disclose the interests they represent and for
> authors in particular to acknowledge non-obvious interests
> they may be representing; being any interests that are not be
> obvious from their stated affiliation.

Agreed, but I think "authors" needs to be extended to include
anyone in a decision or consensus-determining role.  That
includes at least WG Chairs, ADs, appointed experts of various
sorts.  And I think we probably ought to have at least an
informal norm that decisions made under circumstances in which
there were no disclosures of important relationships that might
have made a difference are, to the extent practicable,
appeal-able whenever those relationships become known.

   john




From nobody Mon Apr 28 05:26:05 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FAE11A09E6 for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 05:26:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.301
X-Spam-Level: 
X-Spam-Status: No, score=-99.301 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 ZhRT2MhoSQJD for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 05:25:59 -0700 (PDT)
Received: from groups.winserver.com (listserv.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 730001A0710 for <ietf@ietf.org>; Mon, 28 Apr 2014 05:25:58 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1307; t=1398687950; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=w7nfsJKBb6oddul+pnv+rIKdIcE=; b=HKXMIRx78xHJ9h8H2Saf nWRUJFxJPp/UumrR6Wzx0F5p6jThBB+gmGSpqntSJJO0wmmh1J/cm3iZA76WOuqo KxVHpBkv914wBnPhmtoc4x1PaDfffif32K+ZxrFODjh1QxM+dRN+XJVv1FMIFlL5 WnLX++E2j1lvQyybJ5o1+TA=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 28 Apr 2014 08:25:50 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (opensite.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1796514767.7985.2420; Mon, 28 Apr 2014 08:25:50 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1307; t=1398687859; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=VlhNrna Qjfp0OeHKukgY6/kGdAY2jTAdNx7+kHrsbTw=; b=OnZutmDUQvb89353xyP3fS6 Wb7Vf4n8n0qMJbcdMYHazlHrHClECODlKyKjHCB1TS4eAXQALaKvlBkRQmwjX8zE ZrN2Lv9yLeyHkgBM51gIcG8Zy0XvusOJQkILhyz+QfL8UrmqoF11vVi92WfYTVlp EcAW6cuqeabuYBrzifcU=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Mon, 28 Apr 2014 08:24:19 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1816035375.9.1856; Mon, 28 Apr 2014 08:24:18 -0400
Message-ID: <535E48C7.7010600@isdg.net>
Date: Mon, 28 Apr 2014 08:25:43 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Murray S. Kucherawy" <superuser@gmail.com>,  Miles Fidelman <mfidelman@meetinghouse.net>
Subject: Re: DMARC from the perspective of the listadmin of a bunch of SMALL community lists
References: <20140425002622.E6DFA1ACE0@ld9781.wdf.sap.corp> <535A8A6F.3040903@meetinghouse.net> <CAL0qLwbLpaKXggK5EpF1XtDYXCvs9K5cqUHo-tDZQFN=TO6QYw@mail.gmail.com>
In-Reply-To: <CAL0qLwbLpaKXggK5EpF1XtDYXCvs9K5cqUHo-tDZQFN=TO6QYw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ah4bvVaBpH-dHpetvMRTJtfTDLE
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 12:26:02 -0000

On 4/25/2014 12:32 PM, Murray S. Kucherawy wrote:
> On Fri, Apr 25, 2014 at 9:16 AM, Miles Fidelman
> <mfidelman@meetinghouse.net <mailto:mfidelman@meetinghouse.net>> wrote:
>
>     Thanks for the citation!  Also see below...
>
>
> I'm just curious: Is anyone on this thread a lawyer?
>
> -MSK

Murray,

You don't need to be a lawyer to understand one's ethical engineering 
obligations. Generally, it would the product development engineer that 
recognizes ethical design issues and product liability issues and it 
would be him/her that would bring a particular issue with their legal 
council.   There has been similar (mail blocks) court/lawsuits 
precedence for what has been described in this thread.

Keep in mind what DMARC purports to offer.  If someone intentionally 
and neglectfully ignores it knowing full well that it can be used as a 
highly reliable fraud detection mechanism which the domain owner has 
given you full authorization to apply ("reject"), if you don't, well, 
that will put you at risk -- despite local policy overrides. Don't let 
yourself hide behind local policy. It may ultimately excuse you with 
the changes in some laws in the past decade, but it won't eliminate 
you from risk.

---
Hector Santos/CTO
Santronics Software, Inc.
http://www.santronics.com



From nobody Mon Apr 28 07:21:01 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE88D1A0A18; Mon, 28 Apr 2014 07:20:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.952
X-Spam-Level: 
X-Spam-Status: No, score=-4.952 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, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 JPjx954n08Zr; Mon, 28 Apr 2014 07:20:40 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id DD51B1A047E; Mon, 28 Apr 2014 07:20:39 -0700 (PDT)
Received: from maildlpprd55.lss.emc.com (maildlpprd55.lss.emc.com [10.106.48.159]) by mailuogwprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3SEKZxV016338 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Apr 2014 10:20:37 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3SEKZxV016338
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1398694837; bh=ifxQuMJFdVKke3no56uo8mXGgoI=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=db0MLgTiIUMLR66yqA5EFBQEm9S+RSrDcLf5EzY9oX3hQ/+xcLBCBTv+9tAs+Vot3 p2Y9MP/Sevioz1sT04Vz8G8ZN59T/waqhDC2pD4mpuI8pmM8Me2eXogG5vyFr3mntF 2YcTMaE69Q3mfkAyJWCKb2OG5PVyWyRs9c/f1Suo=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd52.lss.emc.com s3SEKZxV016338
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd55.lss.emc.com (RSA Interceptor); Mon, 28 Apr 2014 10:20:26 -0400
Received: from mxhub35.corp.emc.com (mxhub35.corp.emc.com [10.254.93.83]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3SEKPDB001656 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Apr 2014 10:20:26 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub35.corp.emc.com ([::1]) with mapi; Mon, 28 Apr 2014 10:20:25 -0400
From: "Black, David" <david.black@emc.com>
To: "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "zali@cisco.com" <zali@cisco.com>, "nobo@cisco.com" <nobo@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Mon, 28 Apr 2014 10:20:23 -0400
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/Lw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/L6jxcO2zboamEQ32HahjRbNfe1Q
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 14:20:46 -0000

The -18 version of this draft responds to all of the comments in the
Gen-ART review of -17, including the request for coordination w/the
OPS area, although I wasn't exactly expecting that to occur on the
main IETF list.

The -18 version is ready with one small nit - The following text has
been added to the introduction:

   This memo does not define a compliance requirement for a system that=09
   only implements BFD version 0. This is a reflection of a considered=09
   and deliberate decision by the BFD WG.

An explanation of the rationale for that decision would help - I suggest
adding the following text and a suitable reference to the end of the text
above:
 =20
   because the BFD version 0 protocol may deadlock and hence SHOULD NOT
   be used, as explained further in [RFCxxxx].

Thanks,
--David

> -----Original Message-----
> From: Black, David
> Sent: Wednesday, April 16, 2014 7:31 PM
> To: tnadeau@lucidvision.com; zali@cisco.com; nobo@cisco.com; General Area
> Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> Subject: Gen-ART review of draft-ietf-bfd-mib-17
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Please resolve these comments along with any other Last Call comments
> you may receive.
>=20
> Document: draft-ietf-bfd-mib-17
> Reviewer: David L. Black
> Review Date: April 16, 2014
> IETF LC End Date: April 28, 2014
>=20
> Summary: This draft is on the right track, but has open issues
> 		described in the review.
>=20
> This draft is a MIB module for the BFD protocol, which is an important lo=
w-
> level routing protocol.  The draft is reasonable for a MIB draft; one nee=
ds
> to go read the protocol documents to understand how the protocol works, a=
nd
> significant portions of the text are derived from the usual MIB "boilerpl=
ate"
> as one would expect.  The "Brief Description of MIB Objects" is indeed
> brief, but reasonable.  The shepherd writeup indicates that there are
> multiple implementations.
>=20
> Major issues:
>=20
> This MIB contains many writable objects, so the authors should
> take note of the IESG statement on writable MIB modules:
>=20
> 	http://www.ietf.org/iesg/statement/writable-mib-module.html
>=20
> I did not see this mentioned in the shepherd writeup.  If the OPS Area
> has not been consulted, I strongly suggest doing so during IETF Last
> Call, e.g., starting with Benoit Claise (AD).
>=20
> Minor issues:
>=20
> The security considerations section includes considerations for
> unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
> but omits the corresponding considerations for bfdAdminStatus and
> bfdSessNotificationsEnable.  Both of the latter objects are global,
> so significant damage can be inflicted via these objects with a
> small number of unauthorized modifications, so they need to be
> included in the first list of sensitive objects.
>=20
> I suggest that the authors recheck the entire MIB to ensure that
> every object or table that should be included in the security
> considerations section is appropriately included.
>=20
> Also, as a General Variable, would bfdSessNotificationsEnable be better
> named bfdNotificationsEnable, as it's not in the BFD Session Table?
>=20
> I did not see a compliance requirement for a system that only
> implements BFD protocol version 0.  That absence should at least be
> mentioned somewhere.  For example, if this reflects a considered and
> deliberate decision by the WG, that should be mentioned in the
> introduction.
>=20
> Nits/editorial comments:
>=20
> In the security considerations for authentication-related objects:
>=20
> OLD
>    In order for these sensitive information
>    from being improperly accessed, implementers MAY wish to disallow
>    access to these objects.
> NEW
>    In order to prevent this sensitive information
>    from being improperly accessed, implementers MAY disallow
>    access to these objects.
>=20
> idnits 2.13.01 found a truly minor nit that should be corrected when
> the draft is next revised:
>=20
>   =3D=3D Outdated reference: A later version (-05) exists of
>      draft-ietf-bfd-tc-mib-04
>=20
> it also generated a warning that probably does not reflect an actual prob=
lem:
>=20
>   -- The document seems to lack a disclaimer for pre-RFC5378 work, but ma=
y
>      have content which was first submitted before 10 November 2008.  If =
you
>      have contacted all the original authors and they are all willing to =
grant
>      the BCP78 rights to the IETF Trust, then this is fine, and you can i=
gnore
>      this comment.  If not, you may need to add the pre-RFC5378 disclaime=
r.
>      (See the Legal Provisions document at
>      http://trustee.ietf.org/license-info for more information.)
>=20
> Thanks,
> --David
> ----------------------------------------------------
> David L. Black, Distinguished Engineer
> EMC Corporation, 176 South St., Hopkinton, MA=A0 01748
> +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293-7=
786
> david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> ----------------------------------------------------


From nobody Mon Apr 28 07:22:38 2014
Return-Path: <hartmans@mit.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4421A06E7 for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 17:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.165
X-Spam-Level: 
X-Spam-Status: No, score=0.165 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, SPF_SOFTFAIL=0.665] autolearn=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 TgSZTemPCUmd for <ietf@ietfa.amsl.com>; Fri, 25 Apr 2014 17:21:48 -0700 (PDT)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id C6DFE1A06EE for <ietf@ietf.org>; Fri, 25 Apr 2014 17:21:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 1FE7C206E4; Fri, 25 Apr 2014 20:20:43 -0400 (EDT)
Received: from mail.painless-security.com ([127.0.0.1]) by localhost (mail.suchdamage.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y6Y7BN78mglx; Fri, 25 Apr 2014 20:20:38 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org (c-50-177-27-27.hsd1.ma.comcast.net [50.177.27.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "laptop", Issuer "laptop" (not verified)) by mail.painless-security.com (Postfix) with ESMTPS; Fri, 25 Apr 2014 20:20:38 -0400 (EDT)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id 8F63481895; Fri, 25 Apr 2014 20:21:33 -0400 (EDT)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: adrian@olddog.co.uk
Subject: Re: Author disclosures and conflict of interest
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net> <04ee01cf60b3$b079f9b0$116ded10$@rosenlaw.com> <05b701cf60b5$e08c6c80$a1a54580$@olddog.co.uk>
Date: Fri, 25 Apr 2014 20:21:33 -0400
In-Reply-To: <05b701cf60b5$e08c6c80$a1a54580$@olddog.co.uk> (Adrian Farrel's message of "Fri, 25 Apr 2014 19:40:48 +0100")
Message-ID: <tsl8uqtq6sy.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WJHOdyfIlYqVkUWU-nJ4-uGeNT8
X-Mailman-Approved-At: Mon, 28 Apr 2014 07:22:36 -0700
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2014 00:21:50 -0000

>>>>> "Adrian" == Adrian Farrel <adrian@olddog.co.uk> writes:

    Adrian> Larry,
    Adrian> Is this as simple as adding to the "by submitting this draft, all authors
    Adrian> confirm..." text?

no.
We need to actually develop a culture of disclosing our interests and
demanding that of our contributors.

Somewhere I should have needed to say that my attendance is funded by
Painless Security, who has two particular clients funding the work.
Perhaps a few sentences more than that.

Today, though, people use gmail addresses, it's fairly difficult to find
out who is funding them and in some cases people actively try to hide
that.

There are numerous cases where leaders have taken on very dubious roles
while being resistent to perceived conflicts that were raised by nomcom,
by members of the IESG, etc.

no, adding boiler plate is not the solution here.


From nobody Mon Apr 28 07:50:56 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E99611A0A22 for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 07:50:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 GPTptW3FguIQ for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 07:50:52 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6EF0E1A0A13 for <ietf@ietf.org>; Mon, 28 Apr 2014 07:50:52 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.135.94]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3SEoMdO015347 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Apr 2014 07:50:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398696638; bh=oE0gfjOUCkzelBvSY2Wuj55x5sOUUTRL7vXnEdNHlMc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=F12fCm6ynEENuia0498iXYbsJx04FSrh4xXD6hb+dsoGp1YvaVdnY63muZi+x8G5O k+rVxowPUZ5VWNDdkzp0+8v/aI/lwcfYdBiQj1ncgEeE/4XgiovCKOoLmIBwLO2JGF XajgQos9vIqMnNxkm0q5DWzjQDKyBomxkOscorNw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398696638; i=@elandsys.com; bh=oE0gfjOUCkzelBvSY2Wuj55x5sOUUTRL7vXnEdNHlMc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UPvX8JN0zUerpef11CM3LPDr8LpnNZLpTEXfdCzs4ykJ3W69I3Uxv9K/R7+ci/Gj3 zx9L1GfhRGApLq92R5kM0zsQzRyG/wvU+mexlrgDael0DS/9mLZBQUYgSd5K4igEzr 7VXMoIgoS1NnKwHm25Vz7nFCJ2wHJJnSI6QL0gV0=
Message-Id: <6.2.5.6.2.20140428055512.0d3d6088@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 28 Apr 2014 07:45:25 -0700
To: Phillip Hallam-Baker <hallam@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The IETF environment
In-Reply-To: <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.g mail.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CyMmFvWDU7PTWpK9CUUGMu54nko
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 14:50:54 -0000

Hi Phillip,
At 10:28 26-04-2014, Phillip Hallam-Baker wrote:
>There is really no precedent for discovering that a rogue agency was
>conspiring to sabotage efforts to provide Internet security.

The IETF have been considering security in its protocols for the last 
11 years.  It has also been considering cryptography for use on the 
Internet.  About a year ago it was found that all does not provide 
the security one would expect.  There hasn't been such a 
precedent.  Perpass is an unusual occurrence.

The comments on the thread describe the IETF environment as "people 
coming together
to work on stuff" whereas people from the outside consider the IETF 
as more than that.  The question which has not been discussed is 
whether the IETF accepts the responsibility for all aspects of its 
protocols.  If the answer to that question is "yes" it would be up to 
the IESG to figure out how to solve the problem(s) in a timely manner.

Regards,
S. Moonesamy 


From nobody Mon Apr 28 08:24:50 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A6E71A04C5 for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 08:24:49 -0700 (PDT)
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] autolearn=ham
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 zL2zCOxz4GG1 for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 08:24:48 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 19D221A08C5 for <ietf@ietf.org>; Mon, 28 Apr 2014 08:24:48 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3SFOTGJ001202 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 28 Apr 2014 08:24:32 -0700
Message-ID: <535E72AC.9070802@dcrocker.net>
Date: Mon, 28 Apr 2014 08:24:28 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.gmail.com> <6.2.5.6.2.20140428055512.0d3d6088@resistor.net>
In-Reply-To: <6.2.5.6.2.20140428055512.0d3d6088@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Mon, 28 Apr 2014 08:24:32 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XeX5hse86o5YoA37yw6AdKBH3-A
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 15:24:49 -0000

On 4/28/2014 7:45 AM, S Moonesamy wrote:
> The IETF have been considering security in its protocols for the last 11
> years.

Picking an historical nit:  More like 20-25 years.

Not sure whether anything pre-dates PEM, but that will do as a start.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Apr 28 08:28:05 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C2811A09F5 for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 08:28:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 fHco2qKt1Vxu for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 08:28:02 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD531A0842 for <ietf@ietf.org>; Mon, 28 Apr 2014 08:28:02 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 33452CC0AB for <ietf@ietf.org>; Mon, 28 Apr 2014 11:28:01 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id H5mcj-iE49xi for <ietf@ietf.org>; Mon, 28 Apr 2014 11:27:52 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 60BBCCC0AA for <ietf@ietf.org>; Mon, 28 Apr 2014 11:27:52 -0400 (EDT)
Message-ID: <535E7378.7040401@meetinghouse.net>
Date: Mon, 28 Apr 2014 11:27:52 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.gmail.com> <6.2.5.6.2.20140428055512.0d3d6088@resistor.net>
In-Reply-To: <6.2.5.6.2.20140428055512.0d3d6088@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dJe3ITrk1jH7bpkHGvPFKzYYo1w
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 15:28:03 -0000

S Moonesamy wrote:
> Hi Phillip,
> At 10:28 26-04-2014, Phillip Hallam-Baker wrote:
>> There is really no precedent for discovering that a rogue agency was
>> conspiring to sabotage efforts to provide Internet security.
>
> The IETF have been considering security in its protocols for the last 
> 11 years.  It has also been considering cryptography for use on the 
> Internet.  About a year ago it was found that all does not provide the 
> security one would expect.  There hasn't been such a precedent.  
> Perpass is an unusual occurrence.
>
> The comments on the thread describe the IETF environment as "people 
> coming together
> to work on stuff" whereas people from the outside consider the IETF as 
> more than that.  The question which has not been discussed is whether 
> the IETF accepts the responsibility for all aspects of its protocols.  
> If the answer to that question is "yes" it would be up to the IESG to 
> figure out how to solve the problem(s) in a timely manner.

I think it's more accurate to say that the IETF has an "official role" 
as the standards body for Internet protocols - and there may be a 
mismatch between:

- how that role is "officially defined" (such that it is)

- what responsibilities go with such a role (based on expectations and 
experience with analogous environments and standards bodies that have a 
longer history - such as IEEE, ANSI, ISO, ITU, ...)

- how IETF understands and executes its role (and given the somewhat 
bottom-up, ad hoc nature of IETF - how it's organization, policies, and 
operating procedures map onto exercising "official" roles and 
responsibilities"

- what holes there are that might need to be plugged, and how they might 
be plugged

Miles Fidelman


-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 28 10:03:58 2014
Return-Path: <huitema@microsoft.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A08B1A6F42 for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 10:03:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 n_Y7ltMCEYJC for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 10:03:45 -0700 (PDT)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0239.outbound.protection.outlook.com [207.46.163.239]) by ietfa.amsl.com (Postfix) with ESMTP id 9172B1A6FAE for <ietf@ietf.org>; Mon, 28 Apr 2014 10:03:45 -0700 (PDT)
Received: from BLUPR03MB424.namprd03.prod.outlook.com (10.141.78.152) by BLUPR03MB424.namprd03.prod.outlook.com (10.141.78.152) with Microsoft SMTP Server (TLS) id 15.0.929.12; Mon, 28 Apr 2014 17:03:44 +0000
Received: from BLUPR03MB424.namprd03.prod.outlook.com ([10.141.78.152]) by BLUPR03MB424.namprd03.prod.outlook.com ([10.141.78.152]) with mapi id 15.00.0929.001; Mon, 28 Apr 2014 17:03:44 +0000
From: Christian Huitema <huitema@microsoft.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, S Moonesamy <sm+ietf@elandsys.com>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: RE: The IETF environment
Thread-Topic: The IETF environment
Thread-Index: AQHPYJp08PyIu07EeUKmJWGHnVLBhZskKMYAgAL4o0aAAAlFAIAAGJBA
Date: Mon, 28 Apr 2014 17:03:44 +0000
Message-ID: <8cef8ebd02484dc989e79d33eb37f897@BLUPR03MB424.namprd03.prod.outlook.com>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.gmail.com> <6.2.5.6.2.20140428055512.0d3d6088@resistor.net> <535E72AC.9070802@dcrocker.net>
In-Reply-To: <535E72AC.9070802@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e0:ed43::3]
x-forefront-prvs: 01952C6E96
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(6009001)(428001)(189002)(199002)(51704005)(4396001)(54356999)(92566001)(83322001)(50986999)(80976001)(101416001)(80022001)(2656002)(87936001)(46102001)(77096999)(76176999)(76482001)(76576001)(81542001)(86362001)(33646001)(99286001)(99396002)(81342001)(20776003)(85852003)(31966008)(83072002)(74662001)(74316001)(77982001)(79102001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR03MB424; H:BLUPR03MB424.namprd03.prod.outlook.com; FPR:7CBAC835.8CA68089.21EF16B0.98A1C29C.201AD; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
received-spf: None (: microsoft.com does not designate permitted sender hosts)
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MbDz3L3hx81OT6j8KVF0Wnt0Cg4
Cc: "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 17:03:52 -0000

>> The IETF have been considering security in its protocols for the last=20
>> 11 years.
>
> Picking an historical nit:  More like 20-25 years.
>=20
> Not sure whether anything pre-dates PEM, but that will do as a start.

RFC 1636 was published 20 years ago. From the introduction:

   In summary, the objectives of this workshop were (1) to explore the
   interconnections between security and the rest of the Internet
   architecture, and (2) to develop recommendations for the Internet
   community on future directions with respect to security.  These
   objectives arose from a conviction in the IAB that the two most
   important problem areas for the Internet architecture are scaling and
   security.  While the scaling problems have led to a flood of
   activities on IPng, there has been less effort devoted to security.

Time passes...

-- Christian Huitema



From nobody Mon Apr 28 10:46:35 2014
Return-Path: <nobo@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 042971A6F46; Mon, 28 Apr 2014 10:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.152
X-Spam-Level: 
X-Spam-Status: No, score=-110.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 p7-YSXwmlJCl; Mon, 28 Apr 2014 10:46:31 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id E62E71A6F54; Mon, 28 Apr 2014 10:46:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6446; q=dns/txt; s=iport; t=1398707190; x=1399916790; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JyCIPF2EoPy9QGYyxwF75PYSuSCAvEUjofgznu3yey0=; b=aXuU9KPUVVM1bf4PfNkZTps9C5+lI7gec250ERi64ySPEhWfgza9BuyP 33/j5tLRGh+am9hokuD4MmSM6bZ0FuWLIEx2f6xaM2hpKlbpwF6vK8dX2 EFQ9A5sqaPCRHuIq9ooWx6IrXHcdXUqBnVapSXGfRQ9LJl/7tbTDvmu6i o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAHqTXlOtJV2b/2dsb2JhbABWA4JlIU9XxGmBGRZ0giUBAQEDAXkMBAIBCBEDAQEBCx0HMhQJCAEBBAENBQgBiDAIAQzIMheMZ4FBIRACBQYLgxOBFQSIfziLY4UskSSDMYIr
X-IronPort-AV: E=Sophos;i="4.97,945,1389744000"; d="scan'208";a="39406939"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 28 Apr 2014 17:46:28 +0000
Received: from xhc-rcd-x03.cisco.com (xhc-rcd-x03.cisco.com [173.37.183.77]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3SHkS6e015443 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 28 Apr 2014 17:46:28 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x03.cisco.com ([173.37.183.77]) with mapi id 14.03.0123.003; Mon, 28 Apr 2014 12:46:28 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Black, David" <david.black@emc.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "Zafar Ali (zali)" <zali@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/LwAG2CxA
Date: Mon, 28 Apr 2014 17:46:28 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [161.44.212.215]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nXja6vL4AVwQYFGk63tupSqbWf8
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 17:46:33 -0000

Hi David,

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Monday, April 28, 2014 10:20 AM
> To: tnadeau@lucidvision.com; Zafar Ali (zali); Nobo Akiya (nobo); General
> Area Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
>=20
> The -18 version of this draft responds to all of the comments in the Gen-=
ART
> review of -17, including the request for coordination w/the OPS area,
> although I wasn't exactly expecting that to occur on the main IETF list.

Thanks, they were very good comments.

>=20
> The -18 version is ready with one small nit - The following text has been
> added to the introduction:
>=20
>    This memo does not define a compliance requirement for a system that
>=20
>    only implements BFD version 0. This is a reflection of a considered
>    and deliberate decision by the BFD WG.
>=20
> An explanation of the rationale for that decision would help - I suggest
> adding the following text and a suitable reference to the end of the text
> above:
>=20
>    because the BFD version 0 protocol may deadlock and hence SHOULD NOT
>    be used, as explained further in [RFCxxxx].

Unfortunately the problem with BFD version 0 is not documented in any RFCs,=
 and MIB is probably not the right place to start this documentation either=
. If this should be documented in a RFC, possibly a new info document or ra=
ise errata on RFC5880 ... I'm not sure what would be a reasonable/recommend=
ed path here. In any case, my vote for the MIB document(s) is to keep the c=
urrent text to proceed. Would that be ok with you?

-Nobo

>=20
> Thanks,
> --David
>=20
> > -----Original Message-----
> > From: Black, David
> > Sent: Wednesday, April 16, 2014 7:31 PM
> > To: tnadeau@lucidvision.com; zali@cisco.com; nobo@cisco.com; General
> > Area Review Team (gen-art@ietf.org)
> > Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> > Subject: Gen-ART review of draft-ietf-bfd-mib-17
> >
> > I am the assigned Gen-ART reviewer for this draft. For background on
> > Gen-ART, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Please resolve these comments along with any other Last Call comments
> > you may receive.
> >
> > Document: draft-ietf-bfd-mib-17
> > Reviewer: David L. Black
> > Review Date: April 16, 2014
> > IETF LC End Date: April 28, 2014
> >
> > Summary: This draft is on the right track, but has open issues
> > 		described in the review.
> >
> > This draft is a MIB module for the BFD protocol, which is an important
> > low- level routing protocol.  The draft is reasonable for a MIB draft;
> > one needs to go read the protocol documents to understand how the
> > protocol works, and significant portions of the text are derived from t=
he
> usual MIB "boilerplate"
> > as one would expect.  The "Brief Description of MIB Objects" is indeed
> > brief, but reasonable.  The shepherd writeup indicates that there are
> > multiple implementations.
> >
> > Major issues:
> >
> > This MIB contains many writable objects, so the authors should take
> > note of the IESG statement on writable MIB modules:
> >
> > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> >
> > I did not see this mentioned in the shepherd writeup.  If the OPS Area
> > has not been consulted, I strongly suggest doing so during IETF Last
> > Call, e.g., starting with Benoit Claise (AD).
> >
> > Minor issues:
> >
> > The security considerations section includes considerations for
> > unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus,
> > but omits the corresponding considerations for bfdAdminStatus and
> > bfdSessNotificationsEnable.  Both of the latter objects are global, so
> > significant damage can be inflicted via these objects with a small
> > number of unauthorized modifications, so they need to be included in
> > the first list of sensitive objects.
> >
> > I suggest that the authors recheck the entire MIB to ensure that every
> > object or table that should be included in the security considerations
> > section is appropriately included.
> >
> > Also, as a General Variable, would bfdSessNotificationsEnable be
> > better named bfdNotificationsEnable, as it's not in the BFD Session Tab=
le?
> >
> > I did not see a compliance requirement for a system that only
> > implements BFD protocol version 0.  That absence should at least be
> > mentioned somewhere.  For example, if this reflects a considered and
> > deliberate decision by the WG, that should be mentioned in the
> > introduction.
> >
> > Nits/editorial comments:
> >
> > In the security considerations for authentication-related objects:
> >
> > OLD
> >    In order for these sensitive information
> >    from being improperly accessed, implementers MAY wish to disallow
> >    access to these objects.
> > NEW
> >    In order to prevent this sensitive information
> >    from being improperly accessed, implementers MAY disallow
> >    access to these objects.
> >
> > idnits 2.13.01 found a truly minor nit that should be corrected when
> > the draft is next revised:
> >
> >   =3D=3D Outdated reference: A later version (-05) exists of
> >      draft-ietf-bfd-tc-mib-04
> >
> > it also generated a warning that probably does not reflect an actual
> problem:
> >
> >   -- The document seems to lack a disclaimer for pre-RFC5378 work, but
> may
> >      have content which was first submitted before 10 November 2008.  I=
f
> you
> >      have contacted all the original authors and they are all willing t=
o grant
> >      the BCP78 rights to the IETF Trust, then this is fine, and you can=
 ignore
> >      this comment.  If not, you may need to add the pre-RFC5378 disclai=
mer.
> >      (See the Legal Provisions document at
> >      http://trustee.ietf.org/license-info for more information.)
> >
> > Thanks,
> > --David
> > ----------------------------------------------------
> > David L. Black, Distinguished Engineer EMC Corporation, 176 South St.,
> > Hopkinton, MA=A0 01748
> > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 293=
-7786
> > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > ----------------------------------------------------


From nobody Mon Apr 28 11:53:04 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A46151A701D for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 11:53:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 91DPKG95NH7d for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 11:52:58 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 983561A6FE8 for <ietf@ietf.org>; Mon, 28 Apr 2014 11:52:58 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.135.94]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3SIqjRY006918 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Apr 2014 11:52:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398711177; bh=aaOvkPa5T7RRNF80qLm5lhI0z+NSbQzCe0NLHSkq5Zg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=RnFpHcAvJG6I9ICgdWLfvPvqMJIvbzrJpBcFdvqIbV/CH3mJIjz/hDmWREMrxyvFr 92vVFqr+9NMtUhjx3T6YJC+HN5NzR8eq5byr+oSg5mYP0iBg4390crcJw+zqkjwIY5 3hdFtOGJisM/JJHMOsxRP/VHTcWPFHGfCKW/V2Mo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398711177; i=@elandsys.com; bh=aaOvkPa5T7RRNF80qLm5lhI0z+NSbQzCe0NLHSkq5Zg=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=P90jMEd0MM/lXQTSFuG7WKnEaScIjq3uKCpr9O/PZ4DG1dlOeheFKiyyUotbLcPm4 +qMrtkhqWrYSQbttDEnG0Ksa6a7wFltlEaJaYEB7qxJFngwpua4D3ucT89Qkmz+Ycw ou2J6qerNtnpDAtdA/Fk0hka6vREG9Q/D+yldKXo=
Message-Id: <6.2.5.6.2.20140428101558.0d859f50@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 28 Apr 2014 11:28:15 -0700
To: Miles Fidelman <mfidelman@meetinghouse.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: The IETF environment
In-Reply-To: <535E7378.7040401@meetinghouse.net>
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.gmail.com> <6.2.5.6.2.20140428055512.0d3d6088@resistor.net> <535E7378.7040401@meetinghouse.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JVNtlRuIjMVe4p6aXpvMRwVv7kk
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 18:53:00 -0000

Hi Miles,
At 08:27 28-04-2014, Miles Fidelman wrote:
>I think it's more accurate to say that the IETF has an "official 
>role" as the standards body for Internet protocols - and there may 
>be a mismatch between:

I was looking at the matter from an appeals perspective.  I think 
that it might be more effective than discussing about "official role".

>- how that role is "officially defined" (such that it is)
>
>- what responsibilities go with such a role (based on expectations 
>and experience with analogous environments and standards bodies that 
>have a longer history - such as IEEE, ANSI, ISO, ITU, ...)

I'll leave the above questions to people with expertise about these topics.

>- how IETF understands and executes its role (and given the somewhat 
>bottom-up, ad hoc nature of IETF - how it's organization, policies, 
>and operating procedures map onto exercising "official" roles and 
>responsibilities"

That's an IETF governance question. :-)

>- what holes there are that might need to be plugged, and how they 
>might be plugged

The missing question in the above is "who is going to do the work".

Regards,
S. Moonesamy 


From nobody Mon Apr 28 12:16:36 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2AF761A067C for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 12:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.881
X-Spam-Level: 
X-Spam-Status: No, score=-0.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 vnzIY7w8tH4Y for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 12:16:33 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 3BA831A064C for <ietf@ietf.org>; Mon, 28 Apr 2014 12:16:33 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id E6AA7CC0AB for <ietf@ietf.org>; Mon, 28 Apr 2014 15:16:31 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id v7cHfGfof2A7 for <ietf@ietf.org>; Mon, 28 Apr 2014 15:16:23 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 01B56CC0AC for <ietf@ietf.org>; Mon, 28 Apr 2014 15:16:22 -0400 (EDT)
Message-ID: <535EA906.7000900@meetinghouse.net>
Date: Mon, 28 Apr 2014 15:16:22 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: ietf@ietf.org
Subject: Re: The IETF environment
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <CAMm+LwgVjd7V08OHkV90QeJDwkEdA7S+yvwenO4K2hrDxV-icg@mail.gmail.com> <6.2.5.6.2.20140428055512.0d3d6088@resistor.net> <535E7378.7040401@meetinghouse.net> <6.2.5.6.2.20140428101558.0d859f50@resistor.net>
In-Reply-To: <6.2.5.6.2.20140428101558.0d859f50@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lgcc5DTameiRUoCJO6DMMXztbZk
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 19:16:34 -0000

S Moonesamy wrote:
> Hi Miles,
> At 08:27 28-04-2014, Miles Fidelman wrote:
>> I think it's more accurate to say that the IETF has an "official 
>> role" as the standards body for Internet protocols - and there may be 
>> a mismatch between:
>
> I was looking at the matter from an appeals perspective.  I think that 
> it might be more effective than discussing about "official role".
>
>> - how that role is "officially defined" (such that it is)
>>
>> - what responsibilities go with such a role (based on expectations 
>> and experience with analogous environments and standards bodies that 
>> have a longer history - such as IEEE, ANSI, ISO, ITU, ...)
>
> I'll leave the above questions to people with expertise about these 
> topics.
>
>> - how IETF understands and executes its role (and given the somewhat 
>> bottom-up, ad hoc nature of IETF - how it's organization, policies, 
>> and operating procedures map onto exercising "official" roles and 
>> responsibilities"
>
> That's an IETF governance question. :-)
>
>> - what holes there are that might need to be plugged, and how they 
>> might be plugged
>
> The missing question in the above is "who is going to do the work".

Well, that's kind of implied :-)

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Mon Apr 28 12:38:05 2014
Return-Path: <avri@acm.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 121341A064C for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 12:38:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.465
X-Spam-Level: *
X-Spam-Status: No, score=1.465 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=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 OA-2yqAXxema for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 12:38:00 -0700 (PDT)
Received: from atl4mhob02.myregisteredsite.com (atl4mhob02.myregisteredsite.com [209.17.115.40]) by ietfa.amsl.com (Postfix) with ESMTP id BC99B1A6F0A for <ietf@ietf.org>; Mon, 28 Apr 2014 12:38:00 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.205]) by atl4mhob02.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s3SJbwmZ020033 for <ietf@ietf.org>; Mon, 28 Apr 2014 15:37:58 -0400
Received: (qmail 22074 invoked by uid 0); 28 Apr 2014 19:37:58 -0000
X-TCPREMOTEIP: 69.38.252.85
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@69.38.252.85) by 0 with ESMTPA; 28 Apr 2014 19:37:46 -0000
Message-ID: <535EADD3.3010300@acm.org>
Date: Mon, 28 Apr 2014 16:36:51 -0300
From: Avri Doria <avri@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Author disclosures and conflict of interest
References: <003401cf5cbc$8321ef40$8965cdc0$@rosenlaw.com> <535A9F58.1080105@dcrocker.net>
In-Reply-To: <535A9F58.1080105@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 140428-0, 04/28/2014), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zOP9FAvAhhoarxkjSjQe7YWUluA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 19:38:02 -0000

On 25-Apr-14 14:46, Dave Crocker wrote:

> Seriously.  Expecting anything is frankly naive.

Actually having hung out in the den of battling interests called ICANN,
I find that requiring people to list their interests (they call them
statements of interest, not conflict of interest) as a condition of
participating in working groups results in people actually listing their
interests.  And in a few case where people try to hide it, someone is
sure to point that out to.  I also find it useful to know where people
might be coming from when they suggest ideas.

Now, expecting that to work in the IETF might be naive, but i am naive
enough to not understand why.  Sure it would require learning new
tricks, but I bet we could do it if we had the will to do it.

I am also old enough to remember an IETF when the drive of industry
wasn't quite as strong and where people were allowed to develop
technology if there was a general interest in the work even without an
a-priori guarantee that some company was going to deploy.  It is sad
that the technology drive has been replaced with an industry drive.
Then again, I am naive enough to believe that even this could be fixed
if there was a will to do so.

avri


From nobody Mon Apr 28 13:53:11 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7F011A6FBB for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 13:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level: 
X-Spam-Status: No, score=-1.4 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, J_CHICKENPOX_44=0.6, SPF_PASS=-0.001] autolearn=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 yEGICn_ofKVr for <ietf@ietfa.amsl.com>; Mon, 28 Apr 2014 13:53:07 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id F1EEC1A6FA0 for <ietf@ietf.org>; Mon, 28 Apr 2014 13:53:06 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id fp1so3955716pdb.6 for <ietf@ietf.org>; Mon, 28 Apr 2014 13:53:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=DzJZNJGJ/E2nK1fB4EvWZmnbZuu4eQsXHxHwpav2Y68=; b=s57/xVR7K3cOWXZ+83vKkxyigZYmqOADHhZov+BxZtzdxHB3q12aAYEFzST8suNK+x dJe97RElyIDwhyESyBbExjzeUEfJqIcCiFmDmDGK3eVwGAQlNvQ+EcGkEx1foCw02zeU ihK6z+Wdh6NtZGIknt42qLXaPbef6y0/O/03eCnrDnpsf/4pLlBUSfMp1tr8/gbA7OkW UmVSAIPxnpCJutnHkkK46RHJrx26XQ4Cx2N7tFh0cfkSdeWnT3Pt4Q4FAfMbFaJ86+an icq6Ms0Ezu0CUPUwm42/dUx9VVxMEKJ8dou520R14Exms2/m/kgwoH4sLEr3ougKCMwG CfYA==
X-Received: by 10.68.196.226 with SMTP id ip2mr31270926pbc.106.1398718386264;  Mon, 28 Apr 2014 13:53:06 -0700 (PDT)
Received: from [192.168.178.20] (19.201.69.111.dynamic.snap.net.nz. [111.69.201.19]) by mx.google.com with ESMTPSA id ek2sm37009799pbd.30.2014.04.28.13.53.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 28 Apr 2014 13:53:05 -0700 (PDT)
Message-ID: <535EBFB0.2040400@gmail.com>
Date: Tue, 29 Apr 2014 08:53:04 +1200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: dcrocker@bbiw.net
Subject: Workshop effects [Re: The IETF environment]
References: <53499A5E.9020805@meetinghouse.net> <5349A261.9040500@dcrocker.net> <5349AE35.2000908@meetinghouse.net> <5349BCDA.7080701@gmail.com> <01P6L9JZF5SC00004W@mauve.mrochek.com> <CAL0qLwZr=wVX6eD+yGVOaxkSy5fJbuAErTshOG+2BywUvkDfAA@mail.gmail.com> <01P6QCMYYMJ000004W@mauve.mrochek.com> <6EF4DECC078B08C89F163155@JcK-HP8200.jck.com> <01P6QVVGQA4W00004W@mauve.mrochek.com> <5350A9FB.9010307@dougbarton.us> <01P6S93XQ9TI00004W@mauve.mrochek.com> <5351A89D.7000700@dougbarton.us> <01P6STS0F6I600004X@mauve.mrochek.com> <5356F23F.40909@dougbarton.us> <01P71CGX4VD8000052@mauve.mrochek.com> <5359D543.5070900@dcrocker.net> <01P721HY5XZO000052@mauve.mrochek.com> <535A7D87.6080200@dcrocker.net> <535B32E7.10105@gmail.com> <535B3D2B.3030503@dcrocker.net>
In-Reply-To: <535B3D2B.3030503@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9QnBY3JTGat49WJLwOF4t1wqqlU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 20:53:07 -0000

On 26/04/2014 16:59, Dave Crocker wrote:
> On 4/25/2014 9:15 PM, Brian E Carpenter wrote:
>>   But if the
>> IAB holds a workshop on ploomdoogleblits, which will undoubtedly
>> include some IESG members and some people who aren't members of
>> the I* at all, some ideas will emerge about how the IETF should
>> respond to the ploomdoogleblit work that is going on in academia or
>> industry. Drafts will appear,
> 
> 
> It could be interesting to document this presumed cause/effect
> relationship.
> 
> Start with a listing of every workshop.  Then indicate the related I-Ds
> that were initiated afterwards.  Then indicate which ones made it to RFC.

It may be more subtle than that. Other possible effects of workshops
include *preventing* work, or diverting work to another SDO. And the
sample size is low - I certainly didn't mean to imply that this is
the major source of IETF innovation. Also, counting drafts and RFCs
doesn't measure value.

Another thing is timescale. Let me give you an example which is not
IAB related. In December 1998 there was an ad hoc workshop on
middleware, reported in RFC 2768 in 2000. It was part of the thread
of activity that led to the Globus toolkit and the Global Grid Forum
(now the Open Grid Forum) and then to this stuff called Cloud Computing.
So for *big* innovations, we're talking about very complex threads of
activity and timescales of more than a decade. Picking apart the
contribution of a single workshop is going to be very hard.

On balance I decline to make an amateur analysis of all this. I think
it needs a much deeper study by someone who is an expert in tracking
the history of technology.

One thing I'm fairly sure of. Some of what the IRTF+IETF does is
R&D, and R&D is allowed to fail. If there's no risk of abject failure,
there's also no chance of great success.

    Brian


From nobody Mon Apr 28 23:00:44 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CEEA1A8876; Mon, 28 Apr 2014 23:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.352
X-Spam-Level: 
X-Spam-Status: No, score=-3.352 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_LOW=-0.7, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 TGSTr96EXk8U; Mon, 28 Apr 2014 23:00:31 -0700 (PDT)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 269D91A883C; Mon, 28 Apr 2014 23:00:30 -0700 (PDT)
Received: from maildlpprd05.lss.emc.com (maildlpprd05.lss.emc.com [10.253.24.37]) by mailuogwprd03.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3T60QPg008071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Apr 2014 02:00:28 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s3T60QPg008071
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1398751228; bh=cAqupTYVpHhHWClD9b5xnOOQOIg=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=W7VZGD6Y738hFaqZHi2lCPSt5KAMLiXZbmpNiC3fCpDcHq3Z/ZNbOwzPQSLeYq7Hb i8XXPQKDVZdiaaP7MAa/vZIifhaYbOoyPoDq9Ge6XzNZMnx9UWEXWjql1YImBSMn0H V7wncUiOuUCSKdGO6fxYDcEuegqm7BI7WQ9av73E=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd03.lss.emc.com s3T60QPg008071
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd05.lss.emc.com (RSA Interceptor); Tue, 29 Apr 2014 02:00:14 -0400
Received: from mxhub15.corp.emc.com (mxhub15.corp.emc.com [128.222.70.236]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3T60C17030349 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 Apr 2014 02:00:13 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub15.corp.emc.com ([128.222.70.236]) with mapi; Tue, 29 Apr 2014 02:00:12 -0400
From: "Black, David" <david.black@emc.com>
To: "Nobo Akiya (nobo)" <nobo@cisco.com>, "tnadeau@lucidvision.com" <tnadeau@lucidvision.com>, "Zafar Ali (zali)" <zali@cisco.com>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Tue, 29 Apr 2014 02:00:05 -0400
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/LwAG2CxAABnaMYA=
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com>
In-Reply-To: <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/d1ZRuUsJiWbz-shdtbdofCrY9zU
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 06:00:38 -0000

Hi Nobo,

With respect to the MIB, this concern is a nit, so I'm ok with going ahead =
without
making this change ...

... However ...

Your WG chairs and AD should be concerned that this significant flaw in
BFD version 0 (justifying a "SHOULD NOT use" recommendation) is undocumente=
d.

Thanks,
--David

> -----Original Message-----
> From: Nobo Akiya (nobo) [mailto:nobo@cisco.com]
> Sent: Monday, April 28, 2014 1:46 PM
> To: Black, David; tnadeau@lucidvision.com; Zafar Ali (zali); General Area
> Review Team (gen-art@ietf.org)
> Cc: rtg-bfd@ietf.org; ietf@ietf.org
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
>=20
> Hi David,
>=20
> > -----Original Message-----
> > From: Black, David [mailto:david.black@emc.com]
> > Sent: Monday, April 28, 2014 10:20 AM
> > To: tnadeau@lucidvision.com; Zafar Ali (zali); Nobo Akiya (nobo); Gener=
al
> > Area Review Team (gen-art@ietf.org)
> > Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> > Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
> >
> > The -18 version of this draft responds to all of the comments in the Ge=
n-ART
> > review of -17, including the request for coordination w/the OPS area,
> > although I wasn't exactly expecting that to occur on the main IETF list=
.
>=20
> Thanks, they were very good comments.
>=20
> >
> > The -18 version is ready with one small nit - The following text has be=
en
> > added to the introduction:
> >
> >    This memo does not define a compliance requirement for a system that
> >
> >    only implements BFD version 0. This is a reflection of a considered
> >    and deliberate decision by the BFD WG.
> >
> > An explanation of the rationale for that decision would help - I sugges=
t
> > adding the following text and a suitable reference to the end of the te=
xt
> > above:
> >
> >    because the BFD version 0 protocol may deadlock and hence SHOULD NOT
> >    be used, as explained further in [RFCxxxx].
>=20
> Unfortunately the problem with BFD version 0 is not documented in any RFC=
s,
> and MIB is probably not the right place to start this documentation eithe=
r. If
> this should be documented in a RFC, possibly a new info document or raise
> errata on RFC5880 ... I'm not sure what would be a reasonable/recommended=
 path
> here. In any case, my vote for the MIB document(s) is to keep the current=
 text
> to proceed. Would that be ok with you?
>=20
> -Nobo
>=20
> >
> > Thanks,
> > --David
> >
> > > -----Original Message-----
> > > From: Black, David
> > > Sent: Wednesday, April 16, 2014 7:31 PM
> > > To: tnadeau@lucidvision.com; zali@cisco.com; nobo@cisco.com; General
> > > Area Review Team (gen-art@ietf.org)
> > > Cc: rtg-bfd@ietf.org; ietf@ietf.org; Black, David
> > > Subject: Gen-ART review of draft-ietf-bfd-mib-17
> > >
> > > I am the assigned Gen-ART reviewer for this draft. For background on
> > > Gen-ART, please see the FAQ at
> > >
> > > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> > >
> > > Please resolve these comments along with any other Last Call comments
> > > you may receive.
> > >
> > > Document: draft-ietf-bfd-mib-17
> > > Reviewer: David L. Black
> > > Review Date: April 16, 2014
> > > IETF LC End Date: April 28, 2014
> > >
> > > Summary: This draft is on the right track, but has open issues
> > > 		described in the review.
> > >
> > > This draft is a MIB module for the BFD protocol, which is an importan=
t
> > > low- level routing protocol.  The draft is reasonable for a MIB draft=
;
> > > one needs to go read the protocol documents to understand how the
> > > protocol works, and significant portions of the text are derived from=
 the
> > usual MIB "boilerplate"
> > > as one would expect.  The "Brief Description of MIB Objects" is indee=
d
> > > brief, but reasonable.  The shepherd writeup indicates that there are
> > > multiple implementations.
> > >
> > > Major issues:
> > >
> > > This MIB contains many writable objects, so the authors should take
> > > note of the IESG statement on writable MIB modules:
> > >
> > > 	http://www.ietf.org/iesg/statement/writable-mib-module.html
> > >
> > > I did not see this mentioned in the shepherd writeup.  If the OPS Are=
a
> > > has not been consulted, I strongly suggest doing so during IETF Last
> > > Call, e.g., starting with Benoit Claise (AD).
> > >
> > > Minor issues:
> > >
> > > The security considerations section includes considerations for
> > > unauthorized modification of bfdSessAdminStatus and bfdSessOperStatus=
,
> > > but omits the corresponding considerations for bfdAdminStatus and
> > > bfdSessNotificationsEnable.  Both of the latter objects are global, s=
o
> > > significant damage can be inflicted via these objects with a small
> > > number of unauthorized modifications, so they need to be included in
> > > the first list of sensitive objects.
> > >
> > > I suggest that the authors recheck the entire MIB to ensure that ever=
y
> > > object or table that should be included in the security consideration=
s
> > > section is appropriately included.
> > >
> > > Also, as a General Variable, would bfdSessNotificationsEnable be
> > > better named bfdNotificationsEnable, as it's not in the BFD Session T=
able?
> > >
> > > I did not see a compliance requirement for a system that only
> > > implements BFD protocol version 0.  That absence should at least be
> > > mentioned somewhere.  For example, if this reflects a considered and
> > > deliberate decision by the WG, that should be mentioned in the
> > > introduction.
> > >
> > > Nits/editorial comments:
> > >
> > > In the security considerations for authentication-related objects:
> > >
> > > OLD
> > >    In order for these sensitive information
> > >    from being improperly accessed, implementers MAY wish to disallow
> > >    access to these objects.
> > > NEW
> > >    In order to prevent this sensitive information
> > >    from being improperly accessed, implementers MAY disallow
> > >    access to these objects.
> > >
> > > idnits 2.13.01 found a truly minor nit that should be corrected when
> > > the draft is next revised:
> > >
> > >   =3D=3D Outdated reference: A later version (-05) exists of
> > >      draft-ietf-bfd-tc-mib-04
> > >
> > > it also generated a warning that probably does not reflect an actual
> > problem:
> > >
> > >   -- The document seems to lack a disclaimer for pre-RFC5378 work, bu=
t
> > may
> > >      have content which was first submitted before 10 November 2008. =
 If
> > you
> > >      have contacted all the original authors and they are all willing=
 to
> grant
> > >      the BCP78 rights to the IETF Trust, then this is fine, and you c=
an
> ignore
> > >      this comment.  If not, you may need to add the pre-RFC5378
> disclaimer.
> > >      (See the Legal Provisions document at
> > >      http://trustee.ietf.org/license-info for more information.)
> > >
> > > Thanks,
> > > --David
> > > ----------------------------------------------------
> > > David L. Black, Distinguished Engineer EMC Corporation, 176 South St.=
,
> > > Hopkinton, MA=A0 01748
> > > +1 (508) 293-7953=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 FAX: +1 (508) 2=
93-7786
> > > david.black@emc.com=A0=A0=A0=A0=A0=A0=A0 Mobile: +1 (978) 394-7754
> > > ----------------------------------------------------
>=20


From nobody Tue Apr 29 02:58:28 2014
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9A971A06DF; Tue, 29 Apr 2014 02:58:24 -0700 (PDT)
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, LOTS_OF_MONEY=0.001] autolearn=ham
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 Nv10q6uasVfS; Tue, 29 Apr 2014 02:58:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 35D461A0273; Tue, 29 Apr 2014 02:58:23 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: CORRECTIONS: Nominations Sought for 2014 Jonathan B. Postel Service Award are extended to 16 May 2014.
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140429095823.17080.94823.idtracker@ietfa.amsl.com>
Date: Tue, 29 Apr 2014 02:58:23 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/18gNNNxqMJaLPLKVsSMnypPqU-Q
Cc: iaoc@ietf.org, iab@iab.org, ietf@ietf.org, wgchairs@ietf.org, iesg@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 09:58:25 -0000

The Internet Society is soliciting nominations of qualified candidates for the 2014 Jonathan B. Postel 
Service Award by 16 May. This annual award is presented to an individual or organization that has 
made outstanding contributions in service to the data communications community. The award, which
 includes a presentation crystal and a USD 20,000 prize, is scheduled to be presented during the 
90th Internet Engineering Task Force (IETF) meeting in Toronto, ON, Canada, 20 -25 July 2014. 
Extension Deadline for nominations is 16 May 2014.


More About the Award

The Jonathan B. Postel Service Award was established by the Internet Society to honor a person who 
has made outstanding contributions in service to the data communications community. The award is 
focused on sustained and substantial technical contributions, service to the community, and 
leadership. With respect to leadership, the award committee places particular emphasis on 
candidates who have supported and enabled others in addition to their own specific actions.

 
The award is named for Dr. Jonathan B. Postel to recognize and commemorate the extraordinary 
stewardship exercised by Jon over the course of a thirty year career in networking. He served as the 
editor of the RFC series of notes from its inception in 1969 until 1998. He also served as the 
ARPANET â€œnumbers Czarâ€� and Internet Assigned Numbers Authority over the same period of time. He 
was a founding member of the Internet Architecture (nee Activities) Board and the first individual 
member of the Internet Society, which he also served as a Trustee.


Find out more

â€¢Jon Postelâ€™s life an contributions 
https://www.internetsociety.org/what-we-do/grants-and-awards/awards/postel-service-award

â€¢Award nomination procedures and online submission forms 
https://www.internetsociety.org/what-we-do/grants-and-awards/awards/postel-service-award/procedures

For any questions please contact postel@isoc.org


Best Regards,


Internet Society Team


From nobody Tue Apr 29 04:11:06 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CB011A082F for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 04:11:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.574
X-Spam-Level: 
X-Spam-Status: No, score=-0.574 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Zfd1a9Be5UOH for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 04:11:01 -0700 (PDT)
Received: from wmail.tana.it (www.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id AA5D61A0821 for <ietf@ietf.org>; Tue, 29 Apr 2014 04:11:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1398769859; bh=ijwweVPsWuB4Vcv3WCCJJYFEgH9e7bnMFy8T2qXPG6k=; l=1515; h=Date:From:To; b=po4hay8mlkhQaKgGgNIuTfFpeyd/LVO3gDrqpKgt/bW/rxw62/7AdGt/8eHcnj6SI Gph/FE0pXuIq6x87lSOZ3ro/46ri3vGPOw8gcXmGEA147RtX2yhKyuXtp1445EiKeg uv0WBVdfGJxw/04LJxLAs2oDf0MInzanxQvHW/KI=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Tue, 29 Apr 2014 13:10:59 +0200 id 00000000005DC033.00000000535F88C3.00002C46
Message-ID: <535F88C3.4060002@tana.it>
Date: Tue, 29 Apr 2014 13:10:59 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0
MIME-Version: 1.0
To: "ietf" <ietf@ietf.org>
Subject: Will mailing lists survive DMARC?
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/YYso5X9IIBaeOTtDR4A0x8YV97I
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 11:11:03 -0000

There has been some discussion on what should the IETF do about the
collateral damage experienced by several mailing lists when major
mailbox providers switch their DMARC policies to p=reject.

Mailing lists used to be a legitimate use of email.  Albeit they are
the workhorse of many organizations which are vital for the Internet
itself, such as the IETF and several software projects, statistically
they are a minor Internet feature.  I can understand that after
decades of failed attempts to control email abuse, their disappearance
is not the main concern of "p=reject" proponents.

The discussion on ietf-822 brought some mailing list assumptions
--much needed, since ML were never formally standardized-- as well as
a few proposals.  Now the discussion seems to be fading out, even if
no actionable result was reached.  The solutions proposed, in order of
decreasing ease (IMHO), are:

* Whitelisting,
* weak signatures,
* permission to re-sign, and
* exchange of cryptographic data.

All of those solutions require that originators' relays know whether a
message is destined to a mailing list.  That is a delicate subject in
itself, as it involves privacy considerations --does a subscriber
consent to allowing her or his mailbox providers to know which lists
she or he is on?

The DMARC draft is currently in "AD Followup" state.  A review was
posted here last week, a process which doesn't seem to affect
deployment much.

How is the IETF going to proceed on this issue?

Ale


From nobody Tue Apr 29 04:22:37 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 804B71A0858 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 04:22:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.002
X-Spam-Level: 
X-Spam-Status: No, score=-4.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 iy4y_rcLpaTe for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 04:22:33 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1C61A083B for <ietf@ietf.org>; Tue, 29 Apr 2014 04:22:33 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 87BD3A5; Tue, 29 Apr 2014 13:22:31 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1398770551; bh=/wyOCbXQ8wSveISyyR9+msDScELhSyUolXBkDuu4Q7M=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=LMWiIU0uDgrZhGtq7p4hqFozLsXTbJMmkuvzY0/G0U0/oGAZXKm6CU23Sa5/aQsGD rqL3SLm+whf2t0q911tZdNumR1JYlPdDRUJ812KMD8XUTuSbDSN8oVL2XHI5EV9bkN +x5PkBIR7Wwl++rJXnEDqrAkVRcaDnGCG0Mrn3tk=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 7E9DDA2; Tue, 29 Apr 2014 13:22:31 +0200 (CEST)
Date: Tue, 29 Apr 2014 13:22:31 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Alessandro Vesely <vesely@tana.it>
Subject: Re: Will mailing lists survive DMARC?
In-Reply-To: <535F88C3.4060002@tana.it>
Message-ID: <alpine.DEB.2.02.1404291317510.29282@uplift.swm.pp.se>
References: <535F88C3.4060002@tana.it>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/emueak90oTwYnN89lK8JrVfYvNM
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 11:22:35 -0000

On Tue, 29 Apr 2014, Alessandro Vesely wrote:

> There has been some discussion on what should the IETF do about the
> collateral damage experienced by several mailing lists when major
> mailbox providers switch their DMARC policies to p=reject.
>
> Mailing lists used to be a legitimate use of email.  Albeit they are
> the workhorse of many organizations which are vital for the Internet
> itself, such as the IETF and several software projects, statistically
> they are a minor Internet feature.  I can understand that after
> decades of failed attempts to control email abuse, their disappearance
> is not the main concern of "p=reject" proponents.

Actually, I can't. Not fixing the mailing list and calling it "collateral 
damage but that's ok" is for me totally out of the question. On the other 
hand, this will primarily cause direct problems to users/customers of the 
organisations that decide to do "p=reject" as their participation in 
mailing lists will be crippled.

> The DMARC draft is currently in "AD Followup" state.  A review was
> posted here last week, a process which doesn't seem to affect
> deployment much.
>
> How is the IETF going to proceed on this issue?

I would really like to see the standards process for this mechanism be 
stopped until the mailing list problem has been sorted out. I don't really 
understand how it got that far with this problem unsolved.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Tue Apr 29 04:28:42 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFCCF1A0840 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 04:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 T9bmJxNN1hA2 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 04:28:40 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 7616D1A082F for <ietf@ietf.org>; Tue, 29 Apr 2014 04:28:40 -0700 (PDT)
Received: from [IPv6:2a01:3f0:1::8dff:f286:505f:5921] (unknown [IPv6:2a01:3f0:1:0:8dff:f286:505f:5921]) by mail.frobbit.se (Postfix) with ESMTPSA id 94874205B8; Tue, 29 Apr 2014 13:28:38 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_25E861EE-ACE9-4B4E-BA26-032C84A33ED9"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Will mailing lists survive DMARC?
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <alpine.DEB.2.02.1404291317510.29282@uplift.swm.pp.se>
Date: Tue, 29 Apr 2014 13:28:38 +0200
Message-Id: <0B08F94B-FD02-462F-9E74-E6CE7F85ECC9@frobbit.se>
References: <535F88C3.4060002@tana.it> <alpine.DEB.2.02.1404291317510.29282@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XwbMV5C38irtD8dm_bQ7A3ZSkQs
Cc: ietf <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 11:28:42 -0000

--Apple-Mail=_25E861EE-ACE9-4B4E-BA26-032C84A33ED9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 29 apr 2014, at 13:22, Mikael Abrahamsson <swmike@swm.pp.se> wrote:

> On the other hand, this will primarily cause direct problems to =
users/customers of the organisations that decide to do "p=3Dreject" as =
their participation in mailing lists will be crippled.

As Mikael says, this is a problem for people in those organisations that =
choose to have such filter policy together with the de-facto =
functionality of mailing lists out there.

I ask myself as well what the problem is.

If there was collateral damage on third parties, that would for me have =
been a different thing. As far as I see here, there is not. The damage =
is on the people that have chosen to have such policy (or customers of =
them).

If I have completely misunderstood the situation, my apologies and I'll =
go back and re-read the flood of email on the topic... :-)

   Patrik


--Apple-Mail=_25E861EE-ACE9-4B4E-BA26-032C84A33ED9
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFTX4zmrMabGguI180RAv86AJ9IFEeRsqPz4+fVmGBmz8xeqjHjSwCeKHsA
8iMciqUqx2zXb2Au+5K/zPI=
=jLHW
-----END PGP SIGNATURE-----

--Apple-Mail=_25E861EE-ACE9-4B4E-BA26-032C84A33ED9--


From nobody Tue Apr 29 05:44:12 2014
Return-Path: <marka@isc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B6C1A08C0 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 05:44:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.252
X-Spam-Level: 
X-Spam-Status: No, score=-2.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 G-vgDk0SCoPl for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 05:44:09 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) by ietfa.amsl.com (Postfix) with ESMTP id CA88B1A08BB for <ietf@ietf.org>; Tue, 29 Apr 2014 05:44:09 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP id 5B0E23493B2; Tue, 29 Apr 2014 12:44:07 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id D2C9C160064; Tue, 29 Apr 2014 12:47:12 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 9F99A16005A; Tue, 29 Apr 2014 12:47:12 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 9EAC614C3A5C; Tue, 29 Apr 2014 22:44:03 +1000 (EST)
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
From: Mark Andrews <marka@isc.org>
References: <535F88C3.4060002@tana.it> <alpine.DEB.2.02.1404291317510.29282@uplift.swm.pp.se> <0B08F94B-FD02-462F-9E74-E6CE7F85ECC9@frobbit.se>
Subject: Re: Will mailing lists survive DMARC?
In-reply-to: Your message of "Tue, 29 Apr 2014 13:28:38 +0200." <0B08F94B-FD02-462F-9E74-E6CE7F85ECC9@frobbit.se>
Date: Tue, 29 Apr 2014 22:44:03 +1000
Message-Id: <20140429124403.9EAC614C3A5C@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EoEPxbm_vEVhwQcb0M-ycyvK1qo
Cc: Alessandro Vesely <vesely@tana.it>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 12:44:11 -0000

In message <0B08F94B-FD02-462F-9E74-E6CE7F85ECC9@frobbit.se>, =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= writes:
>
> On 29 apr 2014, at 13:22, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> > On the other hand, this will primarily cause direct problems to
> users/customers of the organisations that decide to do "p=reject" as
> their participation in mailing lists will be crippled.
>
> As Mikael says, this is a problem for people in those organisations that
> choose to have such filter policy together with the de-facto
> functionality of mailing lists out there.
>
> I ask myself as well what the problem is.
>
> If there was collateral damage on third parties, that would for me have
> been a different thing. As far as I see here, there is not. The damage is
> on the people that have chosen to have such policy (or customers of them).
>
> If I have completely misunderstood the situation, my apologies and I'll
> go back and re-read the flood of email on the topic... :-)
>
>    Patrik

There is also collateral damage to anyone elso on the mailing list
who implement DMARC as the SMTP rejections of the mailing list
messages cause them to be unsubscribed from the mailing list.

There is also collateral damage as administrators of the mail list
have to remove the offending members.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Apr 29 05:45:36 2014
Return-Path: <ajs@anvilwalrusden.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 48C191A08C3 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 05:45:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.345
X-Spam-Level: *
X-Spam-Status: No, score=1.345 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FAKE_REPLY_C=1.486, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=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 8FKJSEsF2ESe for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 05:45:34 -0700 (PDT)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 657D61A075D for <ietf@ietf.org>; Tue, 29 Apr 2014 05:45:34 -0700 (PDT)
Received: from mx1.yitter.info (69-165-131-253.dsl.teksavvy.com [69.165.131.253]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id A1B108A031 for <ietf@ietf.org>; Tue, 29 Apr 2014 12:45:32 +0000 (UTC)
Date: Tue, 29 Apr 2014 08:45:28 -0400
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
Message-ID: <20140429124528.GA1324@mx1.yitter.info>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <0B08F94B-FD02-462F-9E74-E6CE7F85ECC9@frobbit.se> <alpine.DEB.2.02.1404291317510.29282@uplift.swm.pp.se>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/I4dxuKtshfEGuCYozBthvNKd530
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 12:45:35 -0000

On Tue, Apr 29, 2014 at 01:22:31PM +0200, Mikael Abrahamsson wrote:

> I would really like to see the standards process for this mechanism
> be stopped 

Since it's an ISE stream document and its intended status is
"Informational", there is no standards process.  (If one thinks, "Yes,
but everyone treats RFCs as standards," then that's a different
discussion to the current one.)


On Tue, Apr 29, 2014 at 01:28:38PM +0200, Patrik FÃ¤ltstrÃ¶m wrote:
> 
> I ask myself as well what the problem is.
> 
> If there was collateral damage on third parties, that would for me have been a different thing. 

The issue is that the operators in this case are externalizing their
problem.  The operator makes the decision and establishes a policy
that causes mailing list postings from addresses inside the operator's
domain of control to bounce.  The person who has to cope with those
bounces is the mailing list manager, and _not_ the mail domain
operator.  The cost of the side effect is not actually borne by the
mail domain operator.  So there certainly is damage to someone other
than the operator of the mail domain (or its customers).

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Tue Apr 29 05:55:57 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AD9F1A08CD for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 05:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 qDhssNOAyqD8 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 05:55:54 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id AC10C1A08CB for <ietf@ietf.org>; Tue, 29 Apr 2014 05:55:54 -0700 (PDT)
Received: from dyn-fg142.sth.netnod.se (dyn-fg142.sth.netnod.se [77.72.226.142]) by mail.frobbit.se (Postfix) with ESMTPSA id 9E66B1FE5A; Tue, 29 Apr 2014 14:55:52 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_BA1112BD-AC86-4836-98A4-8E7A5FBD8833"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Will mailing lists survive DMARC?
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <20140429124528.GA1324@mx1.yitter.info>
Date: Tue, 29 Apr 2014 14:55:52 +0200
Message-Id: <6778109B-953A-45F4-92C9-1543E80A7F9C@frobbit.se>
References: <20140429124528.GA1324@mx1.yitter.info>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/E9FzRreGUIQShESiBqMjaNAao7U
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 12:55:56 -0000

--Apple-Mail=_BA1112BD-AC86-4836-98A4-8E7A5FBD8833
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Ok, one more mail...but the last one (I claim)... ;-)

On 29 apr 2014, at 14:45, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:

> The issue is that the operators in this case are externalizing their
> problem.  The operator makes the decision and establishes a policy
> that causes mailing list postings from addresses inside the operator's
> domain of control to bounce.  The person who has to cope with those
> bounces is the mailing list manager, and _not_ the mail domain
> operator.  The cost of the side effect is not actually borne by the
> mail domain operator.  So there certainly is damage to someone other
> than the operator of the mail domain (or its customers).

The problem exists if A is publishing such a policy, B is acknowledging =
the policy, B is generating a bounce, and the bounce is hitting the =
mailing list provider.

I do not understand why a bounce should be generated (and not the =
incoming mail to B would be tagged as spam and/or null-routed).

That said, the result of the above is that B is unsubscribed from the =
mailing list due to large number of bounces, but that is because B is =
recognizing the policy A is publishing.

Do I get this right?

   Patrik


--Apple-Mail=_BA1112BD-AC86-4836-98A4-8E7A5FBD8833
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD4DBQFTX6FYrMabGguI180RAtOAAJdF1CFw7GVDDdnHjeXS249PbVURAJ9ekZPt
z4pOy90a9nWR1CtJy1KAgQ==
=fc3f
-----END PGP SIGNATURE-----

--Apple-Mail=_BA1112BD-AC86-4836-98A4-8E7A5FBD8833--


From nobody Tue Apr 29 06:03:56 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 361C31A08D2 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:03:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.302
X-Spam-Level: 
X-Spam-Status: No, score=-2.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 MCx1MEWV8-P8 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:03:51 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id DE1641A08C6 for <ietf@ietf.org>; Tue, 29 Apr 2014 06:03:50 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 4F9A8A9; Tue, 29 Apr 2014 15:03:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1398776629; bh=OFxf/8PFB6aCVcH5Q3h7eHg4QCoeelHaSmVgQoDvlDg=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=n/ikq04SdhO+cT+FmcujLxmjxgkjcrQBMxcJTzoRh8xfMpnas1vd3Ymk1H5TeK9GO +NyyZwgAVDqwCpxkxT+1jm/FN7zbfmuZhlf+piSHbM93fHGvdDvseIHxJDoUNB1TVr 7V3i2zUxqmXL23ni/zFcPwY6cZHU+XGTowFGb6FA=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 4BA0DA7; Tue, 29 Apr 2014 15:03:49 +0200 (CEST)
Date: Tue, 29 Apr 2014 15:03:49 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Will mailing lists survive DMARC?
In-Reply-To: <20140429124528.GA1324@mx1.yitter.info>
Message-ID: <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se>
References: <20140429124528.GA1324@mx1.yitter.info>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yeuOKIZmDLBJReVuctqideZByaU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 13:03:53 -0000

On Tue, 29 Apr 2014, Andrew Sullivan wrote:

> On Tue, Apr 29, 2014 at 01:22:31PM +0200, Mikael Abrahamsson wrote:
>
>> I would really like to see the standards process for this mechanism
>> be stopped
>
> Since it's an ISE stream document and its intended status is
> "Informational", there is no standards process.  (If one thinks, "Yes,
> but everyone treats RFCs as standards," then that's a different
> discussion to the current one.)

I quickly went through 
https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/?include_text=1 
which I guess is the draft we're discussing? As far as I can tell, it 
doesn't "inform" about the problem DMARC causes in conjunction with quite 
prevalent mailing list functionality.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Tue Apr 29 06:21:26 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2C5701A08E0 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:21:24 -0700 (PDT)
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] autolearn=ham
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 wW1VX-7aTCOv for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:21:17 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 400581A08DE for <ietf@ietf.org>; Tue, 29 Apr 2014 06:21:17 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3TDLAuM031008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 29 Apr 2014 06:21:14 -0700
Message-ID: <535FA739.3060608@dcrocker.net>
Date: Tue, 29 Apr 2014 06:20:57 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>, Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Will mailing lists survive DMARC?
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 29 Apr 2014 06:21:14 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/st3y5ZM5K72cEZvRUeo79i47Pm8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 13:21:24 -0000

On 4/29/2014 6:03 AM, Mikael Abrahamsson wrote:
> I quickly went through
> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/?include_text=1
> which I guess is the draft we're discussing? As far as I can tell, it
> doesn't "inform" about the problem DMARC causes in conjunction with
> quite prevalent mailing list functionality.


Well, it does, but not in the most pedagogical fashion one might wish 
for.  "Obscure" wouldn't be an inappropriate characterization...

    Appendix C.  DMARC XML Schema
    ...
    Descriptions of the PolicyOverrideTypes:
    ...
    mailing_list:  Local heuristics determined that the message arrived
       via a mailing list, and thus authentication of the original
       message was not expected to succeed.

The draft BCP is another opportunity to clarify such issues, and already 
has some text:

      http://tools.ietf.org/html/draft-crocker-dmarc-bcp-03

      11. DMARC Commentary -- What were they thinking of...?
      ...
      Why doesn't DMARC solve its problem with mailing lists/gatewats?

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Apr 29 06:29:18 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92E591A08EB for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:29:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.602
X-Spam-Level: 
X-Spam-Status: No, score=-4.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 GuBB4ZCwaOGf for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:29:14 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) by ietfa.amsl.com (Postfix) with ESMTP id 123011A08DD for <ietf@ietf.org>; Tue, 29 Apr 2014 06:29:13 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E1BFFA6; Tue, 29 Apr 2014 15:29:11 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1398778151; bh=2AuyGpifSm8FcptqZ2r4gv30zUH2k4w+QHEr4a6wAjQ=; h=Date:From:To:Subject:In-Reply-To:References:From; b=g7ngPKGG43lsfDjvCmp3abF9/r3kOg7+OvbaUd+gHpGnupWyWj2IW3BJ6sw0c4qpS gjixd4jaGOR37ZzH8Evka78E4a7AtyBdJR/64NYGk5usoI1etldlvQHevbW3oK5SHa mbYZl1wk74WuNujDjGF5XXwBqkRDTZh3oDrEsx2o=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id D975EA5 for <ietf@ietf.org>; Tue, 29 Apr 2014 15:29:11 +0200 (CEST)
Date: Tue, 29 Apr 2014 15:29:11 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
In-Reply-To: <535FA739.3060608@dcrocker.net>
Message-ID: <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se>
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se> <535FA739.3060608@dcrocker.net>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ynq6FC3MhPFibTQa09oqfQPI8A4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 13:29:16 -0000

On Tue, 29 Apr 2014, Dave Crocker wrote:

> On 4/29/2014 6:03 AM, Mikael Abrahamsson wrote:
>> I quickly went through
>> https://datatracker.ietf.org/doc/draft-kucherawy-dmarc-base/?include_text=1
>> which I guess is the draft we're discussing? As far as I can tell, it
>> doesn't "inform" about the problem DMARC causes in conjunction with
>> quite prevalent mailing list functionality.
>
>
> Well, it does, but not in the most pedagogical fashion one might wish for. 
> "Obscure" wouldn't be an inappropriate characterization...
>
>   Appendix C.  DMARC XML Schema
>   ...
>   Descriptions of the PolicyOverrideTypes:
>   ...
>   mailing_list:  Local heuristics determined that the message arrived
>      via a mailing list, and thus authentication of the original
>      message was not expected to succeed.

I also found text in the A.3:

"A.3.  Sender Header Field

    It has been suggested in several message authentication efforts that
    the Sender header field be checked for an identifier of interest, as
    the standards indicate this as the proper way to indicate a re-
    mailing of content such as through a mailing list.  Most recently, it
    was a protocol-level option for DomainKeys, but on evolution to DKIM,
    this property was removed.

    The DMARC development team considered this and decided not to include
    support for doing so, for two primary reasons:
...
2.  Although it is certainly true that this is what Sender is for,
        its use in this way is also unreliable, making it a poor
        candidate for inclusion in the DMARC evaluation algorithm."

So... just because this is a hard problem to solve doesn't mean it's a 
good idea to just gloss over it and say "screw it" for mailing lists.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Tue Apr 29 06:41:08 2014
Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01F081A08DC for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:41:06 -0700 (PDT)
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] autolearn=ham
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 6UC_wA2V2LHc for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:41:05 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 010871A08D0 for <ietf@ietf.org>; Tue, 29 Apr 2014 06:41:05 -0700 (PDT)
Received: from [192.168.1.66] (76-218-8-156.lightspeed.sntcca.sbcglobal.net [76.218.8.156]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3TDf0aC031407 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 29 Apr 2014 06:41:04 -0700
Message-ID: <535FABE9.5060103@dcrocker.net>
Date: Tue, 29 Apr 2014 06:40:57 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>, ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se> <535FA739.3060608@dcrocker.net> <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Tue, 29 Apr 2014 06:41:04 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LBfe_NfSnIICDmc8-ggDQ1xhO0U
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 13:41:06 -0000

On 4/29/2014 6:29 AM, Mikael Abrahamsson wrote:
>
> So... just because this is a hard problem to solve doesn't mean it's a
> good idea to just gloss over it and say "screw it" for mailing lists.


A counter-argument is the classic "Don't let perfect be the enemy of 
good".  DMARC works well for a very popular -- albeit very constrained 
-- scenario.

For any mechanism, there is always the possibility that someone will 
apply it for scenarios beyond what was originally envisioned.  Often 
that is a large benefit.  Often is not always.

The distinctive issue now is that that extension is being done by very 
large players.  The phrase "Too big to ignore" has been rattling around 
in my brain for the last few weeks...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Apr 29 06:52:22 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7CA11A08E3 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:52:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.873
X-Spam-Level: 
X-Spam-Status: No, score=-1.873 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 6SSD49lCYjS1 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 06:52:18 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id A578F1A08D5 for <ietf@ietf.org>; Tue, 29 Apr 2014 06:52:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1398779536; bh=K7dVNAG4TKtTWMGbFOZ9lax1mWlRHjbZWXqSUIYHmeM=; l=1008; h=Date:From:To:References:In-Reply-To; b=VtvHhY7ogE0RwiygJt2UAnHJvgTmYPmSgQLrDSXPQ8kUSf3OvzZgQyvQKQNzBpJ/z JvTIAsPJUZwBPb98TZXzlFUerYv+1poX2OxjsOqV7zUViq/Fl5ZCBkO5clJ1eHvlWg eVWeGjDZD1H5kXtyKawDSDiP87616W44VVSmOW7I=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Tue, 29 Apr 2014 15:52:16 +0200 id 00000000005DC035.00000000535FAE90.000036CF
Message-ID: <535FAE90.90209@tana.it>
Date: Tue, 29 Apr 2014 15:52:16 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
References: <20140429124528.GA1324@mx1.yitter.info> <6778109B-953A-45F4-92C9-1543E80A7F9C@frobbit.se>
In-Reply-To: <6778109B-953A-45F4-92C9-1543E80A7F9C@frobbit.se>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MzsY32TkerR7wxWZMzkf7g5g1uQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 13:52:21 -0000

On Tue 29/Apr/2014 14:55:52 +0200 Patrik FÃ¤ltstrÃ¶m wrote:
> 
> The problem exists if A is publishing such a policy, B is 
> acknowledging the policy, B is generating a bounce, and the 
> bounce is hitting the mailing list provider.
> 
> I do not understand why a bounce should be generated (and not the
> incoming mail to B would be tagged as spam and/or null-routed).

There is also a p=quarantine policy.  Yahoo! and AOL, as well as
PayPal, LinkedIn, Facebook, etcetera use p=reject, though.

> That said, the result of the above is that B is unsubscribed from
> the mailing list due to large number of bounces, but that is
> because B is recognizing the policy A is publishing.

B's domain need to do so in order to reject scams claiming to be
from banks or social networks.

> Do I get this right?

More or less.  Many people set up forwarding to an address at a
domain different from theirs, typically large providers, so there
are multiple places where the bounce may occur.

Ale


From nobody Tue Apr 29 07:39:21 2014
Return-Path: <mansaxel@besserwisser.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A0211A090C for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 07:39:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.252
X-Spam-Level: 
X-Spam-Status: No, score=-2.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 T6Zs_VFHjkNg for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 07:39:15 -0700 (PDT)
Received: from jaja.besserwisser.org (jaja.besserwisser.org [IPv6:2a01:298:4:0:211:43ff:fe36:1299]) by ietfa.amsl.com (Postfix) with ESMTP id 016EE1A0905 for <ietf@ietf.org>; Tue, 29 Apr 2014 07:39:15 -0700 (PDT)
Received: by jaja.besserwisser.org (Postfix, from userid 1004) id 36E729D22; Tue, 29 Apr 2014 16:39:11 +0200 (CEST)
Date: Tue, 29 Apr 2014 16:39:11 +0200
From: =?utf-8?B?TcOlbnM=?= Nilsson <mansaxel@besserwisser.org>
To: dcrocker@bbiw.net
Subject: Re: Will mailing lists survive DMARC?
Message-ID: <20140429143910.GN13966@besserwisser.org>
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se> <535FA739.3060608@dcrocker.net> <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se> <535FABE9.5060103@dcrocker.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MSd2ShuMixI0uVaZ"
Content-Disposition: inline
In-Reply-To: <535FABE9.5060103@dcrocker.net>
X-URL: http://vvv.besserwisser.org
X-Purpose: More of everything NOW!
X-happyness: Life is good.
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EQ_TXiOAkDnTW0rtY86apJuRdIo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 14:39:18 -0000

--MSd2ShuMixI0uVaZ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Subject: Re: Will mailing lists survive DMARC? Date: Tue, Apr 29, 2014 at 0=
6:40:57AM -0700 Quoting Dave Crocker (dhc@dcrocker.net):
=20
> For any mechanism, there is always the possibility that someone will
> apply it for scenarios beyond what was originally envisioned.  Often
> that is a large benefit.  Often is not always.

Mailing lists are hardly an obscure corner case in email.=20
=20
> The distinctive issue now is that that extension is being done by
> very large players.  The phrase "Too big to ignore" has been
> rattling around in my brain for the last few weeks...

The problem would be big enough if even a minor actor did this and
it affected niche lists. The IETF endorsing FSVO endorsing a method
that breaks mailing lists if implemented in a way that suits systems
processing large amounts of email is simply not good enough.

--=20
M=C3=A5ns Nilsson     primary/secondary/besserwisser/machina
MN-1334-RIPE                             +46 705 989668
Are we THERE yet?

--MSd2ShuMixI0uVaZ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlNfuY4ACgkQ02/pMZDM1cU8jgCcC+lspHuWk5su6lg6EMP3k7Da
MpsAn0CpuvxoN4ycOj7bLbMlrOuyGNae
=GsGD
-----END PGP SIGNATURE-----

--MSd2ShuMixI0uVaZ--


From nobody Tue Apr 29 07:39:30 2014
Return-Path: <john-ietf@jck.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DDC11A0915 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 07:39:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.251
X-Spam-Level: 
X-Spam-Status: No, score=-3.251 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 HlyG6I4FQLFc for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 07:39:25 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4F8C81A0914 for <ietf@ietf.org>; Tue, 29 Apr 2014 07:39:25 -0700 (PDT)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1Wf9Br-00091Y-Fy for ietf@ietf.org; Tue, 29 Apr 2014 10:39:23 -0400
Date: Tue, 29 Apr 2014 10:39:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
Message-ID: <14DE2BC840FF3B8AA4A167EC@JcK-HP8200.jck.com>
In-Reply-To: <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se>
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se> <535FA739.3060608@dcrocker.net> <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.115
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NH3VKqwQ1RwncAcZoVf-RUCsmDQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 14:39:27 -0000

An odd, and somewhat nasty, thought...

So far, the two organizations (at least of which I'm aware) that
have made more or less public announcements of their intentions
to use the sort of restrictive policies that cause mailing list
problems are not only large providers of email but also large
providers of online forums, social group discussions, etc.  So
are several of the other member-contributor organizations to
dmarc.org.  As far as can be observed from the outside, those
forums and discussion groups make considerable contributions to
the bottom lines of those providers -- in most cases, they allow
those organizations to sell advertising and/or to sell their
users and their interest profiles to advertisers.   Email, by
contrast, is typically a service they provide in conjunction
with those other services but is not, itself, generally a profit
center.

For many of the users and uses of the extended Internet, mailing
lists are the historical predecessor, and sometimes a
contemporary alternative, to those forums and centralized
"social network" discussions.  

If one examines those relationships, there is a case to be made
that the problems they cause to mailing lists is not "collateral
damage" at all.  Even if the effects were discovered by
accident, continued use of DMARC with restrictive policies has
the consequence of driving traffic away from mailing lists,
perhaps especially mailing lists operated by smaller providers
and non-profits, toward use of the for-profit systems operated
by those same (to quote another recent comment) "too big to
ignore" operators with a positive effect on their bottom line to
the detriment of  other operators and ways of doing things.

Behaviors by large ("dominant", "too big to ignore", etc.)
industry actors that have the effect of driving alternate
solutions or providers out by mechanisms other than fair
competition in the marketplace, especially when those mechanisms
come out of collaborations among such actors, are, if other
conditions are met, rather seriously illegal in many countries.
If intent can be demonstrated, they are even more so.

So, as a purely hypothetical set of questions (I am not
recommending anything), I wonder what would happen if some of
the people who have been claiming they or the general public are
harmed by this would, instead of asking what the IETF can do
about something that is not an IETF Standard, went to their
local "competitiveness" or "antitrust" authorities, explained
the situation and started complaining?   I also wonder whether
the IETF and ISOC have, or should seek, legal advice about how
to keep adequate distance between themselves and this situation
should some relevant jurisdiction initiate an investigation or
enforcement action.

Just curious.
    john


From nobody Tue Apr 29 07:58:34 2014
Return-Path: <jhaas@slice.pfrc.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F27DC1A0928; Tue, 29 Apr 2014 07:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.219
X-Spam-Level: 
X-Spam-Status: No, score=-2.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 x2WRFYNd8foT; Tue, 29 Apr 2014 07:58:25 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id A5A6F1A0925; Tue, 29 Apr 2014 07:58:25 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 870EBC220; Tue, 29 Apr 2014 10:58:24 -0400 (EDT)
Date: Tue, 29 Apr 2014 10:58:24 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: "Black, David" <david.black@emc.com>
Subject: Re: Gen-ART review of draft-ietf-bfd-mib-18
Message-ID: <20140429145824.GR1256@pfrc>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/S3--T7JavuN_nM2FDKCRjPB-_p4
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 14:58:30 -0000

On Tue, Apr 29, 2014 at 02:00:05AM -0400, Black, David wrote:
> With respect to the MIB, this concern is a nit, so I'm ok with going ahead without
> making this change ...
> 
> ... However ...
> 
> Your WG chairs and AD should be concerned that this significant flaw in
> BFD version 0 (justifying a "SHOULD NOT use" recommendation) is undocumented.

And also un-RFCed.

It was a "work in progress" that never fully saw the light of full
deployment.  Vendors very quickly moved to version 1 which fixed a critical
issue in the state machine.  If any version 0 survives, it's historical and
likely to be a source of operational agony rather than a useful feature.

-- Jeff


From nobody Tue Apr 29 08:02:59 2014
Return-Path: <iad@ietf.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F91F1A6F9E; Mon, 28 Apr 2014 10:50:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.801
X-Spam-Level: 
X-Spam-Status: No, score=0.801 tagged_above=-999 required=5 tests=[BAYES_50=0.8, LOTS_OF_MONEY=0.001] autolearn=ham
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 JuTOmLpMk1FK; Mon, 28 Apr 2014 10:50:43 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 377D01A6FBB; Mon, 28 Apr 2014 10:50:43 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Extension of Call for Nominations: Jonathan B. Postel Service Award
X-Test-IDTracker: no
X-IETF-IDTracker: 5.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140428175043.26026.47649.idtracker@ietfa.amsl.com>
Date: Mon, 28 Apr 2014 10:50:43 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/M09evMwb39UfnMy0PYlTtblgrmM
X-Mailman-Approved-At: Tue, 29 Apr 2014 08:02:55 -0700
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Apr 2014 17:50:47 -0000

Nominations Sought for 2014 Jonathan B. Postel Service Award are extended to 16 May 2014.

The Internet Society is soliciting nominations of qualified candidates for the 2014 Jonathan
B. Postel Service Award by 7 May. This annual award is presented to an individual or organization 
that has made outstanding contributions in service to the data communications community. The 
award, which includes a presentation crystal and a USD 20,000 prize, is scheduled to be presented 
during the 90th Internet Engineering Task Force (IETF) meeting in Toronto, ON, Canada, 20 -25 
July 2014. 

Extension Deadline for nominations is 16 May 2014.

More About the Award

The Jonathan B. Postel Service Award was established by the Internet Society to honor a person 
who has made outstanding contributions in service to the data communications community. The 
award is focused on sustained and substantial technical contributions, service to the community, 
and leadership. With respect to leadership, the award committee places particular emphasis on candidates 
who have supported and enabled others in addition to their own specific actions.
 
The award is named for Dr. Jonathan B. Postel to recognize and commemorate the extraordinary stewardship 
exercised by Jon over the course of a thirty year career in networking. He served as the editor of the RFC 
series of notes from its inception in 1969 until 1998. He also served as the ARPANET â€œnumbers Czarâ€� and Internet 
Assigned Numbers Authority over the same period of time. He was a founding member of the Internet Architecture 
(nee Activities) Board and the first individual member of the Internet Society, which he also served as a Trustee.
 
Find out more
â€¢	Learn more about Jon Postelâ€™s life and contributions.
â€¢	Find the out more on the award, nomination procedures, and online submission forms.
â€¢	I'm ready to nominate someone!

For any questions please contact postel@isoc.org

Best Regards,

Internet Society Team


From nobody Tue Apr 29 08:10:53 2014
Return-Path: <jason_livingood@cable.comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4A61A08CF for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 08:10:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.484
X-Spam-Level: 
X-Spam-Status: No, score=-3.484 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_MODEMCABLE=1.368, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 tYgvpMVc8ZKW for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 08:10:45 -0700 (PDT)
Received: from cable.comcast.com (copdcavout01.cable.comcast.com [76.96.32.253]) by ietfa.amsl.com (Postfix) with ESMTP id 8ED841A04AC for <ietf@ietf.org>; Tue, 29 Apr 2014 08:10:45 -0700 (PDT)
Received: from ([24.40.56.115]) by copdcavout01.cable.comcast.com with ESMTP  id C7WM3M1.129968753; Tue, 29 Apr 2014 09:10:39 -0600
Received: from PACDCEXMB06.cable.comcast.com ([169.254.8.10]) by PACDCEXHUB02.cable.comcast.com ([fe80::2816:661:c294:c863%16]) with mapi id 14.03.0181.006; Tue, 29 Apr 2014 11:10:39 -0400
From: "Livingood, Jason" <Jason_Livingood@cable.comcast.com>
To: John C Klensin <john-ietf@jck.com>, Alessandro Vesely <vesely@tana.it>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Will mailing lists survive DMARC?
Thread-Topic: Will mailing lists survive DMARC?
Thread-Index: AQHPY6jlKGNv0Oe2H022Uh2NO1iYyJso0qiAgAAEyoCAAAJNgIAAE5cA///FsAA=
Date: Tue, 29 Apr 2014 15:10:18 +0000
Message-ID: <CF853909.CEDD0%jason_livingood@cable.comcast.com>
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se> <535FA739.3060608@dcrocker.net> <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se> <14DE2BC840FF3B8AA4A167EC@JcK-HP8200.jck.com>
In-Reply-To: <14DE2BC840FF3B8AA4A167EC@JcK-HP8200.jck.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.4.1.140326
x-originating-ip: [68.87.16.249]
Content-Type: multipart/alternative; boundary="_000_CF853909CEDD0jasonlivingoodcablecomcastcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/EagDFq5qu_3QORlCOzXqbofArMU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 15:10:48 -0000

--_000_CF853909CEDD0jasonlivingoodcablecomcastcom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

FWIW, we at Comcast just posted on this subject on our Postmaster page at h=
ttp://postmaster.comcast.net/dmarcupdate.html.

- Jason

Pasted here as well:
Background

Comcast recently emplemented the Domain-based Authentication, Reporting, an=
d Conformance (DMARC)<http://dmarc.org/> specification as a new way to help=
 prevent phishing messages from reaching our customers=92 mailboxes. DMARC =
enables a domain to publicly indicate (via DNS) what action should be taken=
 for mail claiming to be from that domain that does not pass authentication=
 and get reports about phishing and spam messages that did not come from ap=
proved mail servers.

Recent History
Recently, the policies that AOL and Yahoo published instructed mail servers=
 that use DMARC to reject mail if it claims to be from aol.com or yahoo.com=
 but failed authentication =96 meaning the mail did not originate from an a=
pproved mail server run by AOL or Yahoo, respectively. This has reportedly =
caused issues for some people using AOL or Yahoo addresses with email discu=
ssion lists and other mail sending tools. More information from AOL was pos=
ted here<http://postmaster-blog.aol.com/2014/04/22/aol-mail-updates-dmarc-p=
olicy-to-reject/>.

While AOL and Yahoo may be addressing spam and phishing issues in making th=
is change, it does not yet appear to be typical DMARC usage. We have been a=
sked whether Comcast plans to make similar changes soon, and we can confirm=
 we have no such plans.

Comcast=92s Future DMARC Plans
To help us improve our detection of those who use the comcast.net domain ma=
liciously we have published a DMARC record for comcast.net, but that change=
 WILL NOT disrupt legitimate messaging. This policy will not ask other serv=
ices to reject messages that did not originate from us, but rather report t=
hose instances to us for research. We will also publish DMARC reject polici=
es in the coming months for the domains used by our Xfinity Billing, Xfinit=
y Home, and Customer Security Assurance notifications. These originate from=
 specific domains and servers that we maintain. This will not negatively af=
fect email discussion lists but will help us prevent some of phishing messa=
ges that might attempt to target our customers.

If You Have Been Negatively Affected by AOL=92s and Yahoo=92s Changes
If you are an Xfinity Internet customer, use an AOL or Yahoo email account =
regularly, and are having problems getting email from email discussion list=
s or other tools at those addresses, we invite you consider activating or u=
sing your comcast.net email account.

To signup, add, or change your email account - Click Here<http://customer.c=
omcast.com/help-and-support/internet/stay-connected-with-email/>

Once your email address is registered, you can access it in several ways:
For webmail users - Click Here<http://customer.comcast.com/help-and-support=
/internet/using-xfinity-connect-for-comcast-email/>
For email client users - Click Here<http://customer.comcast.com/help-and-su=
pport/internet/email-client-programs-with-xfinity-email/>
For mobile email users - Click Here<http://customer.comcast.com/help-and-su=
pport/internet/comcast-email-mobile-devices/>


On 4/29/14, 10:39 AM, "John C Klensin" <john-ietf@jck.com<mailto:john-ietf@=
jck.com>> wrote:

An odd, and somewhat nasty, thought...

So far, the two organizations (at least of which I'm aware) that
have made more or less public announcements of their intentions
to use the sort of restrictive policies that cause mailing list
problems are not only large providers of email but also large
providers of online forums, social group discussions, etc.  So
are several of the other member-contributor organizations to
dmarc.org.  As far as can be observed from the outside, those
forums and discussion groups make considerable contributions to
the bottom lines of those providers -- in most cases, they allow
those organizations to sell advertising and/or to sell their
users and their interest profiles to advertisers.   Email, by
contrast, is typically a service they provide in conjunction
with those other services but is not, itself, generally a profit
center.

For many of the users and uses of the extended Internet, mailing
lists are the historical predecessor, and sometimes a
contemporary alternative, to those forums and centralized
"social network" discussions.

If one examines those relationships, there is a case to be made
that the problems they cause to mailing lists is not "collateral
damage" at all.  Even if the effects were discovered by
accident, continued use of DMARC with restrictive policies has
the consequence of driving traffic away from mailing lists,
perhaps especially mailing lists operated by smaller providers
and non-profits, toward use of the for-profit systems operated
by those same (to quote another recent comment) "too big to
ignore" operators with a positive effect on their bottom line to
the detriment of  other operators and ways of doing things.

Behaviors by large ("dominant", "too big to ignore", etc.)
industry actors that have the effect of driving alternate
solutions or providers out by mechanisms other than fair
competition in the marketplace, especially when those mechanisms
come out of collaborations among such actors, are, if other
conditions are met, rather seriously illegal in many countries.
If intent can be demonstrated, they are even more so.

So, as a purely hypothetical set of questions (I am not
recommending anything), I wonder what would happen if some of
the people who have been claiming they or the general public are
harmed by this would, instead of asking what the IETF can do
about something that is not an IETF Standard, went to their
local "competitiveness" or "antitrust" authorities, explained
the situation and started complaining?   I also wonder whether
the IETF and ISOC have, or should seek, legal advice about how
to keep adequate distance between themselves and this situation
should some relevant jurisdiction initiate an investigation or
enforcement action.

Just curious.
    john



--_000_CF853909CEDD0jasonlivingoodcablecomcastcom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <7E11007C3E287A4C98F458F9BD58567E@cable.comcast.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 16px; font-fami=
ly: Calibri, sans-serif;">
<div>
<div>
<div>FWIW, we at Comcast just posted on this subject on our Postmaster page=
 at&nbsp;<a href=3D"http://postmaster.comcast.net/dmarcupdate.html">http://=
postmaster.comcast.net/dmarcupdate.html</a>.</div>
<div><br>
</div>
<div>- Jason</div>
<div><br>
</div>
<div>Pasted here as well:</div>
<div>
<h2 style=3D"margin: 0px 0px 10px; padding: 0px; line-height: 24px; font-fa=
mily: Arial, Tahoma, Helvetica, sans-serif; background-color: rgb(255, 255,=
 255);">
<b style=3D"font-size: 14px; line-height: 18px; margin: 0px; padding: 0px;"=
>Background</b></h2>
<p style=3D"margin: 0px 0px 15px; padding: 0px; font-size: 14px; font-famil=
y: Arial, Tahoma, Helvetica, sans-serif; line-height: 18px; background-colo=
r: rgb(255, 255, 255);">
Comcast recently emplemented the&nbsp;<a href=3D"http://dmarc.org/" style=
=3D"color: rgb(50, 89, 244); margin: 0px; padding: 0px; font-size: 0.9em; f=
ont-weight: bold;">Domain-based Authentication, Reporting, and Conformance =
(DMARC)</a>&nbsp;specification as a new way to help
 prevent phishing messages from reaching our customers=92 mailboxes. DMARC =
enables a domain to publicly indicate (via DNS) what action should be taken=
 for mail claiming to be from that domain that does not pass authentication=
 and get reports about phishing and
 spam messages that did not come from approved mail servers.&nbsp;<br style=
=3D"margin: 0px; padding: 0px;">
<br style=3D"margin: 0px; padding: 0px;">
<b style=3D"margin: 0px; padding: 0px;">Recent History</b><br style=3D"marg=
in: 0px; padding: 0px;">
Recently, the policies that AOL and Yahoo published instructed mail servers=
 that use DMARC to reject mail if it claims to be from aol.com or yahoo.com=
 but failed authentication =96 meaning the mail did not originate from an a=
pproved mail server run by AOL or
 Yahoo, respectively. This has reportedly caused issues for some people usi=
ng AOL or Yahoo addresses with email discussion lists and other mail sendin=
g tools. More information from&nbsp;<a href=3D"http://postmaster-blog.aol.c=
om/2014/04/22/aol-mail-updates-dmarc-policy-to-reject/" style=3D"color: rgb=
(50, 89, 244); margin: 0px; padding: 0px; font-size: 0.9em; font-weight: bo=
ld;">AOL
 was posted here</a>.&nbsp;<br style=3D"margin: 0px; padding: 0px;">
<br style=3D"margin: 0px; padding: 0px;">
While AOL and Yahoo may be addressing spam and phishing issues in making th=
is change, it does not yet appear to be typical DMARC usage.&nbsp;<font col=
or=3D"#ff0000">We have been asked whether Comcast plans to make similar cha=
nges soon, and we can confirm we have no
 such plans.</font>&nbsp;<br style=3D"margin: 0px; padding: 0px;">
<br style=3D"margin: 0px; padding: 0px;">
<b style=3D"margin: 0px; padding: 0px;">Comcast=92s Future DMARC Plans</b><=
br style=3D"margin: 0px; padding: 0px;">
To help us improve our detection of those who use the comcast.net domain ma=
liciously we have published a DMARC record for comcast.net, but that change=
 WILL NOT disrupt legitimate messaging. This policy will not ask other serv=
ices to reject messages that did
 not originate from us, but rather report those instances to us for researc=
h. We will also publish DMARC reject policies in the coming months for the =
domains used by our Xfinity Billing, Xfinity Home, and Customer Security As=
surance notifications. These originate
 from specific domains and servers that we maintain. This will not negative=
ly affect email discussion lists but will help us prevent some of phishing =
messages that might attempt to target our customers.&nbsp;<br style=3D"marg=
in: 0px; padding: 0px;">
<br style=3D"margin: 0px; padding: 0px;">
<b style=3D"margin: 0px; padding: 0px;">If You Have Been Negatively Affecte=
d by AOL=92s and Yahoo=92s Changes</b><br style=3D"margin: 0px; padding: 0p=
x;">
If you are an Xfinity Internet customer, use an AOL or Yahoo email account =
regularly, and are having problems getting email from email discussion list=
s or other tools at those addresses, we invite you consider activating or u=
sing your comcast.net email account.&nbsp;<br style=3D"margin: 0px; padding=
: 0px;">
<br style=3D"margin: 0px; padding: 0px;">
To signup, add, or change your email account -&nbsp;<a href=3D"http://custo=
mer.comcast.com/help-and-support/internet/stay-connected-with-email/" style=
=3D"color: rgb(50, 89, 244); margin: 0px; padding: 0px; font-size: 0.9em; f=
ont-weight: bold;">Click Here</a><br style=3D"margin: 0px; padding: 0px;">
<br style=3D"margin: 0px; padding: 0px;">
Once your email address is registered, you can access it in several ways:<b=
r style=3D"margin: 0px; padding: 0px;">
For webmail users -&nbsp;<a href=3D"http://customer.comcast.com/help-and-su=
pport/internet/using-xfinity-connect-for-comcast-email/" style=3D"color: rg=
b(50, 89, 244); margin: 0px; padding: 0px; font-size: 0.9em; font-weight: b=
old;">Click Here</a><br style=3D"margin: 0px; padding: 0px;">
For email client users -&nbsp;<a href=3D"http://customer.comcast.com/help-a=
nd-support/internet/email-client-programs-with-xfinity-email/" style=3D"col=
or: rgb(50, 89, 244); margin: 0px; padding: 0px; font-size: 0.9em; font-wei=
ght: bold;">Click Here</a><br style=3D"margin: 0px; padding: 0px;">
For mobile email users -&nbsp;<a href=3D"http://customer.comcast.com/help-a=
nd-support/internet/comcast-email-mobile-devices/" style=3D"color: rgb(50, =
89, 244); margin: 0px; padding: 0px; font-size: 0.9em; font-weight: bold;">=
Click Here</a></p>
</div>
</div>
</div>
<div><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 16px;"><br>
</div>
<div style=3D"font-family: Consolas, monospace; font-size: 16px;">On 4/29/1=
4, 10:39 AM, &quot;John C Klensin&quot; &lt;<a href=3D"mailto:john-ietf@jck=
.com">john-ietf@jck.com</a>&gt; wrote:</div>
<div style=3D"font-family: Consolas, monospace; font-size: 16px;"><br>
</div>
<blockquote id=3D"MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE" style=3D"font-family:=
 Consolas, monospace; font-size: 16px; border-left-color: rgb(181, 196, 223=
); border-left-width: 5px; border-left-style: solid; padding: 0px 0px 0px 5=
px; margin: 0px 0px 0px 5px;">
<div>An odd, and somewhat nasty, thought...</div>
<div><br>
</div>
<div>So far, the two organizations (at least of which I'm aware) that</div>
<div>have made more or less public announcements of their intentions</div>
<div>to use the sort of restrictive policies that cause mailing list</div>
<div>problems are not only large providers of email but also large</div>
<div>providers of online forums, social group discussions, etc.&nbsp;&nbsp;=
So</div>
<div>are several of the other member-contributor organizations to</div>
<div>dmarc.org.&nbsp;&nbsp;As far as can be observed from the outside, thos=
e</div>
<div>forums and discussion groups make considerable contributions to</div>
<div>the bottom lines of those providers -- in most cases, they allow</div>
<div>those organizations to sell advertising and/or to sell their</div>
<div>users and their interest profiles to advertisers.&nbsp;&nbsp; Email, b=
y</div>
<div>contrast, is typically a service they provide in conjunction</div>
<div>with those other services but is not, itself, generally a profit</div>
<div>center.</div>
<div><br>
</div>
<div>For many of the users and uses of the extended Internet, mailing</div>
<div>lists are the historical predecessor, and sometimes a</div>
<div>contemporary alternative, to those forums and centralized</div>
<div>&quot;social network&quot; discussions.&nbsp;&nbsp;</div>
<div><br>
</div>
<div>If one examines those relationships, there is a case to be made</div>
<div>that the problems they cause to mailing lists is not &quot;collateral<=
/div>
<div>damage&quot; at all.&nbsp;&nbsp;Even if the effects were discovered by=
</div>
<div>accident, continued use of DMARC with restrictive policies has</div>
<div>the consequence of driving traffic away from mailing lists,</div>
<div>perhaps especially mailing lists operated by smaller providers</div>
<div>and non-profits, toward use of the for-profit systems operated</div>
<div>by those same (to quote another recent comment) &quot;too big to</div>
<div>ignore&quot; operators with a positive effect on their bottom line to<=
/div>
<div>the detriment of&nbsp;&nbsp;other operators and ways of doing things.<=
/div>
<div><br>
</div>
<div>Behaviors by large (&quot;dominant&quot;, &quot;too big to ignore&quot=
;, etc.)</div>
<div>industry actors that have the effect of driving alternate</div>
<div>solutions or providers out by mechanisms other than fair</div>
<div>competition in the marketplace, especially when those mechanisms</div>
<div>come out of collaborations among such actors, are, if other</div>
<div>conditions are met, rather seriously illegal in many countries.</div>
<div>If intent can be demonstrated, they are even more so.</div>
<div><br>
</div>
<div>So, as a purely hypothetical set of questions (I am not</div>
<div>recommending anything), I wonder what would happen if some of</div>
<div>the people who have been claiming they or the general public are</div>
<div>harmed by this would, instead of asking what the IETF can do</div>
<div>about something that is not an IETF Standard, went to their</div>
<div>local &quot;competitiveness&quot; or &quot;antitrust&quot; authorities=
, explained</div>
<div>the situation and started complaining?&nbsp;&nbsp; I also wonder wheth=
er</div>
<div>the IETF and ISOC have, or should seek, legal advice about how</div>
<div>to keep adequate distance between themselves and this situation</div>
<div>should some relevant jurisdiction initiate an investigation or</div>
<div>enforcement action.</div>
<div><br>
</div>
<div>Just curious.</div>
<div>&nbsp;&nbsp;&nbsp;&nbsp;john</div>
<div><br>
</div>
<div><br>
</div>
</blockquote>
</body>
</html>

--_000_CF853909CEDD0jasonlivingoodcablecomcastcom_--


From nobody Tue Apr 29 08:28:28 2014
Return-Path: <d3e3e3@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 997311A0913; Tue, 29 Apr 2014 08:28:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 odRdtdvjG1vp; Tue, 29 Apr 2014 08:28:23 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 631FA1A092A; Tue, 29 Apr 2014 08:28:21 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id wp4so416521obc.35 for <multiple recipients>; Tue, 29 Apr 2014 08:28:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=5/CuRQhyHM3HLgIv75WtmRMsElLM2d17fnrNFr9r9PY=; b=NS2wWR/vxmw7EVgPAejDRxYgyHO53Im4aLHxzMa+/uBSN8X0uJUkDsdP2wUqdG7Iw+ vawhbugBGKNppLbxOWQeQthQ9ZUCJA7ZQHdS2hGmNdycNzAK0wewkrPfDkvg6P1q3WMK UB29XwsMm+aVPcfJD+lDyqJy9Sf0ZbqsAlmGRKwwrGClJEoFjmJS/zeEsMNAnPY2xy1d pBYE+6x10wEKW4lmze/o+PoFqsJEBNwi1R20w6+mpfPHitGhX286jWq0IxPGg+Vx+L+H I6MihVyBbS1ciYHliWyLYCYcXj5j9M5AIApOZ3t4dwAadtBKvbw5f1Exrs6AVEEv/uAy TnCA==
X-Received: by 10.60.57.164 with SMTP id j4mr112918oeq.24.1398785300242; Tue, 29 Apr 2014 08:28:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.25.41 with HTTP; Tue, 29 Apr 2014 08:28:00 -0700 (PDT)
In-Reply-To: <009d01cf6047$760de3c0$6229ab40$@akayla.com>
References: <009d01cf6047$760de3c0$6229ab40$@akayla.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 29 Apr 2014 11:28:00 -0400
Message-ID: <CAF4+nEEq2LmPm37i-TWTTwGQYgNTRf-JJjo+_34K4Mrd_nCxtQ@mail.gmail.com>
Subject: Re: Gen-ART LC review of draft-eastlake-iana-cfm-considerations-01
To: Peter Yee <peter@akayla.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fhNDSBMKKOqaIRwbp0RqNfqNhlE
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-eastlake-iana-cfm-considerations.all@tools.ietf.org, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 15:28:25 -0000

Hi Peter,

I'm fine with all of your suggestion. Thanks for the review.

Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Fri, Apr 25, 2014 at 1:30 AM, Peter Yee <peter@akayla.com> wrote:
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>
> Please resolve these comments along with any other Last Call comments you
> may receive.
>
> Document: draft-eastlake-iana-cfm-considerations-01
> Reviewer: Peter Yee
> Review Date: April-24-2014
> IETF LC End Date: May-21-2014
> IESG Telechat date: TBD
>
> Summary: This draft is basically ready for publication as a Best Current
> Practice, but has some nits that should be fixed before publication. [Ready
> with nits.]
>
> This document provides the IANA Considerations for two registries covering
> the IEEE Std 802.1Q-2011 CFM OpCode and TLV Type blocks assigned to the
> IETF.
>
> Nits:
>
> Most comments that follow are for alignment with the terminology and usage
> found in IEEE Std 802.1Q-2011.
>
> General: globally replace "Continuity" with "Connectivity".
>
> General: globally replace "Codepoints" with "Code Points".
>
> General: globally replace "Op-Code" with "OpCode".
>
> Page 3, 2nd paragraph, 2nd sentence: change "IANA Consideration" to "IANA
> Considerations".
>
> Page 5, 1st paragraph: end the reference with a period.
>
> Page 5, 2nd paragraph: replace "Mansfield, S." with "and S. Mansfield" to
> match http://www.rfc-editor.org/in-notes/rfc-ref.txt.  Hey, I'm running out
> of nits to pick here. :-)
>
>                 -Peter Yee
>
>


From nobody Tue Apr 29 08:37:56 2014
Return-Path: <david.black@emc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24D721A091D; Tue, 29 Apr 2014 08:37:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.952
X-Spam-Level: 
X-Spam-Status: No, score=-4.952 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, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 o92jOI376Ijw; Tue, 29 Apr 2014 08:37:53 -0700 (PDT)
Received: from mailuogwdur.emc.com (mailuogwdur.emc.com [128.221.224.79]) by ietfa.amsl.com (Postfix) with ESMTP id 2D78C1A01DF; Tue, 29 Apr 2014 08:37:52 -0700 (PDT)
Received: from maildlpprd53.lss.emc.com (maildlpprd53.lss.emc.com [10.106.48.157]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3TFbmDT024855 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Apr 2014 11:37:49 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com s3TFbmDT024855
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1398785870; bh=XDdtEZPUnWQK32BO3jrDItmfWrQ=; h=From:To:CC:Date:Subject:Message-ID:References:In-Reply-To: Content-Type:Content-Transfer-Encoding:MIME-Version; b=JDw7ZcIrygsEoH1M/ed5ImfNsp+5Pu9Ul7yGhRsCMIiVRrvOjJyJRjJziGBJmnXJw YdNG3UG+ECbWnE5SU2hHGUU9A6+FNbv9MN6e8UEVQKc3Vi+h2bN0Q9CcwGkAXQhB40 PgvX4stbA2K7mhh6L8ZRTq5IWUhqzAAUAmsHwzPc=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com s3TFbmDT024855
Received: from mailusrhubprd04.lss.emc.com (mailusrhubprd04.lss.emc.com [10.253.24.22]) by maildlpprd53.lss.emc.com (RSA Interceptor); Tue, 29 Apr 2014 11:37:42 -0400
Received: from mxhub01.corp.emc.com (mxhub01.corp.emc.com [10.254.141.103]) by mailusrhubprd04.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s3TFbfU1015605 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 Apr 2014 11:37:41 -0400
Received: from mx15a.corp.emc.com ([169.254.1.64]) by mxhub01.corp.emc.com ([10.254.141.103]) with mapi; Tue, 29 Apr 2014 11:37:40 -0400
From: "Black, David" <david.black@emc.com>
To: Jeffrey Haas <jhaas@pfrc.org>
Date: Tue, 29 Apr 2014 11:37:39 -0400
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9ju3y+7+r2M3cwRuClVDsxPJjgywAAKutg
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712076C437F73@MX15A.corp.emc.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com> <20140429145824.GR1256@pfrc>
In-Reply-To: <20140429145824.GR1256@pfrc>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd04.lss.emc.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZqP0J22hVRbDN_qOL2_U-8JJJac
Cc: "ietf@ietf.org" <ietf@ietf.org>, "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, "Black, David" <david.black@emc.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 15:37:55 -0000

Jeff - could you work w/Nobo to get the word "historical" included in
the MIB draft as a characterization of BFD version 0 ?  For example,
the following text could be added to the introduction:

   because the BFD version 0 protocol is primarily of historical interest
   by comparison to the widespread deployment of the BFD version 1 protocol=
.

Thanks,
--David


> -----Original Message-----
> From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> Sent: Tuesday, April 29, 2014 10:58 AM
> To: Black, David
> Cc: Nobo Akiya (nobo); tnadeau@lucidvision.com; Zafar Ali (zali); General=
 Area
> Review Team (gen-art@ietf.org); rtg-bfd@ietf.org; ietf@ietf.org
> Subject: Re: Gen-ART review of draft-ietf-bfd-mib-18
>=20
> On Tue, Apr 29, 2014 at 02:00:05AM -0400, Black, David wrote:
> > With respect to the MIB, this concern is a nit, so I'm ok with going ah=
ead
> without
> > making this change ...
> >
> > ... However ...
> >
> > Your WG chairs and AD should be concerned that this significant flaw in
> > BFD version 0 (justifying a "SHOULD NOT use" recommendation) is
> undocumented.
>=20
> And also un-RFCed.
>=20
> It was a "work in progress" that never fully saw the light of full
> deployment.  Vendors very quickly moved to version 1 which fixed a critic=
al
> issue in the state machine.  If any version 0 survives, it's historical a=
nd
> likely to be a source of operational agony rather than a useful feature.
>=20
> -- Jeff


From nobody Tue Apr 29 09:48:29 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCF1D1A092F for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 09:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 Vb7Y6cI9WPQd for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 09:48:24 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8768D1A08EB for <ietf@ietf.org>; Tue, 29 Apr 2014 09:48:24 -0700 (PDT)
Received: (qmail 61493 invoked from network); 29 Apr 2014 16:48:22 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 29 Apr 2014 16:48:22 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9fd.535fd7d6.k1404; i=johnl@user.iecc.com; bh=yvZJlo/1DVh1aUJdMBrPC0AdcMdsu5efv+DVbT4zFBE=; b=EBfN7A7bUDv95PUZGhlZRTl22LpUeVKbrv6Fcr3bRnNoDWcv4OHpPjsLM0e/+m6M5rlluNIa52TrZQV7kFKVWV5ErYIgBgdkDSS6ZDad37puL+ydHqGxuDTGVkyvXx4m1zuH6g74ZhcEcjVWq48tI0zk2P6SD8ExWewDxploFnMa2HH1aKdyRggaxFVs/wYCaQcOV0dSmRz7wlQaxqvG7HiDhX+0N1Es7CsloHScWQgZb5ySmy6hLePGxH5X+45b
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=9fd.535fd7d6.k1404; olt=johnl@user.iecc.com; bh=yvZJlo/1DVh1aUJdMBrPC0AdcMdsu5efv+DVbT4zFBE=; b=HvYMFOVcfOIKg6UADU7jj3Q3HzKwtisrJKBmWvAFkON3VaMtNdYZbT2NH4OdzeQqzFOzfK0SAIq+iFwGYNxE3ObQdYCPGw/pEzeEk6X95PcbdffmPVGX4cpyFsFbAMSgUidlDmUU6d9Kn3VjCISU5aFVlHranBT86uHgrlhCdU0SOGDi9c9IGsYsK7BtzdAhmCnx1Rd2cb58AOwoP/V29KYXlMCHPthUu+8b+wmr8Zfqvsmx3RgKs2g8bP9ZADN7
Date: 29 Apr 2014 16:47:59 -0000
Message-ID: <20140429164759.2556.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
In-Reply-To: <14DE2BC840FF3B8AA4A167EC@JcK-HP8200.jck.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/b3nF6_IdYXoOmek8lnjpzp5QA2w
Cc: john-ietf@jck.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 16:48:26 -0000

In article <14DE2BC840FF3B8AA4A167EC@JcK-HP8200.jck.com> you write:
>An odd, and somewhat nasty, thought...
>
>So far, the two organizations (at least of which I'm aware) that
>have made more or less public announcements of their intentions
>to use the sort of restrictive policies that cause mailing list
>problems are not only large providers of email but also large
>providers of online forums, social group discussions, etc. ...

You're not the first to suggest this, but simpler explanations
explain the situation.  I blogged about it here:

http://jl.ly/Email/aoldmarc.html

R's,
John


From nobody Tue Apr 29 10:49:52 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 660621A0947 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 10:49:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.541
X-Spam-Level: 
X-Spam-Status: No, score=-1.541 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, J_CHICKENPOX_16=0.6, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=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 4G6MggpQ6hVy for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 10:49:48 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AFE81A0948 for <ietf@ietf.org>; Tue, 29 Apr 2014 10:49:48 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.143.98]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3THnLml022427 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Apr 2014 10:49:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398793776; bh=CHwyLcZJiprl5OKhQ+kgJJOuoNK5wlDDVNwhDRTAH/0=; h=Date:To:From:Subject; b=zWw0lcaXdYOIY/4Ys2kEipLq0Y+xKlSk5WKDFjsEx9J6KC0YG9Of2+0tH+Nt96cnc dgpd5seQ+f3CHi+8biQ96ra8eEO1+hY2MYlkaPOmGwJVt/6PGvUbQ46qlr6pDm/+gn dbw6mrWKFBwYsJtr9KR+tQtUZvzoSMPWWaKd7FKc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398793776; i=@elandsys.com; bh=CHwyLcZJiprl5OKhQ+kgJJOuoNK5wlDDVNwhDRTAH/0=; h=Date:To:From:Subject; b=gNZe2toBINQzAF+drENeli/6osb431BS9r/p9F77Kyy+nvxMam+F0X9bRDmqCRXN4 GI8KTzfnbMmZgacjlURMAe/GUiMJ1SVnWpxPoPX1vzS8SpaccVkGHejZ7FBYRAuDUj 6b7kgQhUFopQrNN8I5G+bYL5QTmQlG38c813atQI=
Message-Id: <6.2.5.6.2.20140429085037.0bbf48a8@elandsys.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 29 Apr 2014 09:25:16 -0700
To: Alessandro Vesely <vesely@tana.it>, ietf@ietf.org, Mikael Abrahamsson <swmike@swm.pp.se>, Patrik  =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>, John C Klensin <john-ietf@jck.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Will mailing lists survive DMARC?
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KL2hR9D2gLR3EMjmqCpFxtLg1QE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 17:49:49 -0000

Hi Alessandro, Mikael, Patrik, John,
At 04:10 29-04-2014, Alessandro Vesely wrote:
>There has been some discussion on what should the IETF do about the
>collateral damage experienced by several mailing lists when major
>mailbox providers switch their DMARC policies to p=3Dreject.

[snip]

>The DMARC draft is currently in "AD Followup" state.  A review was
>posted here last week, a process which doesn't seem to affect
>deployment much.

My review was sent to the ISE.  It was copied to=20
the ietf@ietf.org mailing list for informational=20
purposes.  I did not expect the review to affect deployment.

>How is the IETF going to proceed on this issue?

The above question could be ignored as it is=20
addressed to everybody and nobody on this mailing list. :-)

At 04:22 29-04-2014, Mikael Abrahamsson wrote:
>I would really like to see the standards process=20
>for this mechanism be stopped until the mailing=20
>list problem has been sorted out. I don't really=20
>understand how it got that far with this problem unsolved.

It is likely because only a few persons tried to=20
do something when it was possible to do so.  A=20
significant number of possible (IETF) issues go=20
unnoticed as it is not always clear whether they will cause problems.

At 05:55 29-04-2014, Patrik F=E4ltstr=F6m wrote:
>The problem exists if A is publishing such a=20
>policy, B is acknowledging the policy, B is=20
>generating a bounce, and the bounce is hitting the mailing list provider.
>
>I do not understand why a bounce should be=20
>generated (and not the incoming mail to B would=20
>be tagged as spam and/or null-routed).

I posted a simplified example of the problem at=20
http://www.ietf.org/mail-archive/web/ietf/current/msg87286.html=20
Silently dropping messages (null-routed) creates mail blackholes.

At 07:39 29-04-2014, John C Klensin wrote:
>So, as a purely hypothetical set of questions (I am not
>recommending anything), I wonder what would happen if some of
>the people who have been claiming they or the general public are
>harmed by this would, instead of asking what the IETF can do
>about something that is not an IETF Standard, went to their
>local "competitiveness" or "antitrust" authorities, explained
>the situation and started complaining?   I also wonder whether

The regulator might start an investigation.  The=20
(lack of) results can be used as input for governance issues.

There is someone from the European Union reading=20
this mailing list.  The person might be able to comment to help Alessandro.

Regards,
S. Moonesamy =20


From nobody Tue Apr 29 10:56:46 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF92A1A0949 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 10:56:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.243
X-Spam-Level: **
X-Spam-Status: No, score=2.243 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, SPF_NEUTRAL=0.779] autolearn=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 en7_1gZSeHwd for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 10:56:30 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCF31A08DB for <ietf@ietf.org>; Tue, 29 Apr 2014 10:56:30 -0700 (PDT)
Received: (qmail 72014 invoked from network); 29 Apr 2014 17:56:28 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 29 Apr 2014 17:56:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=b29.535fe7cc.k1404; i=johnl@user.iecc.com; bh=ejEqWrfhAhgkjacB/WsGq6JKXrNseb6NfWpFdKqLhXs=; b=YyIYdKlxcpuGLagolGPJMKKXRTdBQm4IR+zyVKB2A6ZQw+RqKzQZCCdNnWWdY5vXETCiWYKX4d2L0mt5+WWCGVG6sQB4ETuyCU+RWBhY73MJD6ce+NmH1kEc3RW0Y62LEUOQkDgGxvFoQWWAb3rBWD4vwjJYf7C4jQ1zUlIjB8W/G+cjsvHt0TQqKqAcGaF1GCZnm+gQkIYlporaDbH+SXOHfXAw758U1KtsRFo1hdCRl0p4FSmQEBOj5wcyNAxO
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=b29.535fe7cc.k1404; olt=johnl@user.iecc.com; bh=ejEqWrfhAhgkjacB/WsGq6JKXrNseb6NfWpFdKqLhXs=; b=pWO3Sv7ZQYwLHKns+k8ezRzF6cqgFSKBYK50whLRQZTKN8SUtE/ZhfVnBlSaYFcSVVlq4FpTlOOnj6/lpMfvmkl5Q2tH008CrJuMmXqkuRBLAFdEw623YGYX8FtQe0e3bcaITZPYtqLkfoJwxmQHlUVs6DTVfBR6euFe9UkkrzH8CKGb3uM5Xvjsft6Pp//QacofLwb/o+KVpWXT6BoShn8mYjVYaeaPsyrTdpO1jRluy51aziGVrXMa0fTKyIBV
Date: 29 Apr 2014 17:56:06 -0000
Message-ID: <20140429175606.2856.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
In-Reply-To: <6778109B-953A-45F4-92C9-1543E80A7F9C@frobbit.se>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8TplYDhposjX_W0kcuDLnDC99sg
Cc: paf@frobbit.se
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 17:56:31 -0000

>The problem exists if A is publishing such a policy, B is acknowledging the policy, B is
>generating a bounce, and the bounce is hitting the mailing list provider.
>
>I do not understand why a bounce should be generated (and not the incoming mail to B would
>be tagged as spam and/or null-routed).

DMARC lets you say p=reject or p=quarantine.  For whatever reason, AOL
and Yahoo are saying reject.  Using that p=quarantine would be nearly
as bad, with list mail eternally vanishing into spam folders.

>That said, the result of the above is that B is unsubscribed from the mailing list due to
>large number of bounces, but that is because B is recognizing the policy A is publishing.

Yes, but there are complicating factors.

One is that it's entirely possible to use DMARC responsibly.  It's
been around for a year, domains like paypal.com have published
p=reject, with no problems because nobody sends real paypal.com mail
via mailing lists or mail-an-article or the other stuff that is broken
by DMARC reject.

What changed is that two of the largest consumer mail providers had
huge security breaches where crooks stole user info including their
address books (both admit it, no conspiracizing needed) and used DMARC
as a sledgehammer to try and mitigate the damage.  I don't think
anyone is opposed to mitigating damage, but these particular efforts
had the predictable side effect of dumping costs on unrelated third
parties which AOL and Yahoo have so far done nothing to address.
Yahoo's blog admits that they are affecting 30,000 other providers, so
they know this is not a trivial problem.

Finally, the DMARC group includes the largest mail providers in the
world (I've seen DMARC bounces from Gmail, Yahoo, Hotmail, AOL, and
Comcast), who have such a large market share and so much market power
that it is not realistic to exclude users at those providers and tell
them to take their business elsewhere, no matter how well deserved
that advice might be.

R's,
John


From nobody Tue Apr 29 11:05:13 2014
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9452C1A0933 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 11:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 wI4dfSBO1pUE for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 11:05:10 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 2C4C41A0939 for <ietf@ietf.org>; Tue, 29 Apr 2014 11:05:10 -0700 (PDT)
Received: from [192.168.1.22] (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id D9F79232E1; Tue, 29 Apr 2014 20:05:07 +0200 (CEST)
Content-Type: multipart/signed; boundary="Apple-Mail=_37BAFE7E-ED40-45C0-9462-62498968CED8"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Will mailing lists survive DMARC?
From: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
In-Reply-To: <6.2.5.6.2.20140429085037.0bbf48a8@elandsys.com>
Date: Tue, 29 Apr 2014 20:05:07 +0200
Message-Id: <216E796D-AF3A-4278-AE1E-918F364ABDA9@frobbit.se>
References: <6.2.5.6.2.20140429085037.0bbf48a8@elandsys.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VPGXy4lbSSoXGJxgBC3IjgVpKF0
Cc: John Klensin <john-ietf@jck.com>, ietf <ietf@ietf.org>, Alessandro Vesely <vesely@tana.it>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 18:05:11 -0000

--Apple-Mail=_37BAFE7E-ED40-45C0-9462-62498968CED8
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1


On 29 apr 2014, at 18:25, S Moonesamy <sm+ietf@elandsys.com> wrote:

> At 05:55 29-04-2014, Patrik F=E4ltstr=F6m wrote:
>> The problem exists if A is publishing such a policy, B is =
acknowledging the policy, B is generating a bounce, and the bounce is =
hitting the mailing list provider.
>>=20
>> I do not understand why a bounce should be generated (and not the =
incoming mail to B would be tagged as spam and/or null-routed).
>=20
> I posted a simplified example of the problem at =
http://www.ietf.org/mail-archive/web/ietf/current/msg87286.html Silently =
dropping messages (null-routed) creates mail blackholes.

Yes, correct, but I already see lots of this.

I.e. just like any >N points in spamassassin.

Anyway, I do now understand the issue and thank everyone that onlist and =
offlist have explained the issue to me.

   Patrik


--Apple-Mail=_37BAFE7E-ED40-45C0-9462-62498968CED8
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org

iD8DBQFTX+nTrMabGguI180RAt1pAJsFF6l1CGM+qjb3oJnyhP6nt2OfLACeMYez
idFa26V6lnqrXG2KwWfqL6w=
=KVwv
-----END PGP SIGNATURE-----

--Apple-Mail=_37BAFE7E-ED40-45C0-9462-62498968CED8--


From nobody Tue Apr 29 11:12:06 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90BD31A04AF for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 11:11:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.479
X-Spam-Level: 
X-Spam-Status: No, score=-100.479 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_46=0.6, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 W_5zM6xF_QsQ for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 11:11:50 -0700 (PDT)
Received: from ftp.catinthebox.net (ntbbs.santronics.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 478FC1A04E8 for <ietf@ietf.org>; Tue, 29 Apr 2014 11:11:50 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=3797; t=1398795098; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=Ic//Dx5rr3Fh8Z7i3Wnsc90dtxI=; b=mVmqCl5n5oLbmP2AG8Ur oj1dtOyWQWRyrBaLM2Loz5tAS3tKs4skUu65gqOT/WXmBsPF9XnyxPK6xzbLOFWu ef3XN4S5z7X2SMmm1yjbOYlVYlI10Y/n+XWY7FF5REWp5GDhnPwVt3dcjp0PXqqO 0nHvUAlyPCvS73X35TLyeSI=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 29 Apr 2014 14:11:38 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from beta.winserver.com (hector.wildcatblog.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1903661215.9062.4080; Tue, 29 Apr 2014 14:11:37 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=3797; t=1398795007; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=ExlSrRk V3hDZpouX+s5QiLR5gbpureGLpJrDchZjnig=; b=D+5qOpyLr8dkUlykrqrjmfo URFaJ6I+O0Cn3RUD/Jr0ltFnWVAVto6Fol4z4G0SUtWU9VUEYdGBFrToL0kJGcOA 2A+iLTETKwKufk8FyxFYTCvwm56nvgGY5OZ788hB34a2cqYQ8FJkYXJ+OCyKja/r wBdLKex/8nixulCeXPFo=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 29 Apr 2014 14:10:07 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1923182796.9.13188; Tue, 29 Apr 2014 14:10:06 -0400
Message-ID: <535FEB58.5060508@isdg.net>
Date: Tue, 29 Apr 2014 14:11:36 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>, ietf <ietf@ietf.org>
Subject: Re: Will mailing lists survive DMARC?
References: <535F88C3.4060002@tana.it>
In-Reply-To: <535F88C3.4060002@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ol5_o0Vxo4w22aRwgLXdXf4poAs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 18:11:52 -0000

On 4/29/2014 7:10 AM, Alessandro Vesely wrote:

>
> The discussion on ietf-822 brought some mailing list assumptions
> --much needed, since ML were never formally standardized-- as well as
> a few proposals.  Now the discussion seems to be fading out, even if
> no actionable result was reached.  The solutions proposed, in order of
> decreasing ease (IMHO), are:
>
> * Whitelisting,
> * weak signatures,
> * permission to re-sign, and
> * exchange of cryptographic data.
>
> All of those solutions require that originators' relays know whether a
> message is destined to a mailing list.  That is a delicate subject in
> itself, as it involves privacy considerations --does a subscriber
> consent to allowing her or his mailbox providers to know which lists
> she or he is on?

You keep thinking this is MLM problem.  NO, this is for all systems to 
follow. Even a BANK for example:

    "Ok, we need your email address for our new eBanking service!"

    "hmmmmm, oh, I'm sorry, your email domain receiver doesn't
     support DMARC so you will alway be open to fraud problems
     with your email address.  Have another address?"

    "Ok, hmmmm, oh, I'm sorry, that one too is no good to use."

    "No Problem, you can use our ONLINE service, with our EMAIL
     address or you can go another ESP mail service that offers
     DMARC operations."

It doesn't have to be a mailing list.

> The DMARC draft is currently in "AD Followup" state.  A review was
> posted here last week, a process which doesn't seem to affect
> deployment much.
>
> How is the IETF going to proceed on this issue?

Get control of the DMARC draft with greater policy design advocate 
participation and begin to get operational policy discussions going in 
order to define new mail handling policy options.

Overall, the first principle thing is to:

    * HONOR THE PROTOCOL FIRST

This has the been the fundamental issue with the middle-ware market. 
Its not just the mailing list system. It could be any mail hosting 
service who may wish to begin (re)sign mail.

In all cases, the remailer has to check author domain signing policies 
and so far, they have refused to do so.  They prefer to do this in an 
unrestricted way that doesn't require the author domain permission. 
They wanted to change in order to ADD DKIM, but not change to ADD 
POLICY.  Its not just about the mailing list but any 3rd party 
resigner.   This is burned into the DKIM abstract:

    DKIM separates the question of the identity of
    the Signer of the message from the purported author
    of the message.

This was a fundamental flaw since it was not possible to separate the 
author from the message without violating the signer's signature of 
the message.  This would be another suggestion to do an DKIM RFC6376 
errata to remove this conceptual flaw and update the DKIM Assessor 
input requirements that would include the Author Domain Identity 
RFC6376 intentionally, refused to recognize or defined in the document.

I think the middle-ware operations who would be doing DKIM will do the 
right thing and add the DKIM+POLICY layer its been sourly missing if 
the IETF can correct DMARC or even ADSP to allow the resigner to exist 
in a proper protocol defined way.   All we had was IETF resistance to 
allowing policy to exist.  It made ADSP historic!  DMARC snuck in. 
Disaster!

There was a fundamental error in making ADSP historic so perhaps we 
should revisit why and learn from the engineering that was done and/or 
explored in order to update DMARC with the 9 years of multiple RFC 
development and insights.

I have an ethical engineering problem with ignoring protocol policies 
with offering by-passing suggestions.  The DMARC drafts needs to be 
updated if we want the middleware to coexist with it.

-- 
HLS



From nobody Tue Apr 29 12:06:54 2014
Return-Path: <nobo@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCCAC1A097F; Tue, 29 Apr 2014 12:06:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.152
X-Spam-Level: 
X-Spam-Status: No, score=-110.152 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=ham
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 0md08NaBolkX; Tue, 29 Apr 2014 12:06:49 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 17CE41A0792; Tue, 29 Apr 2014 12:06:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2317; q=dns/txt; s=iport; t=1398798408; x=1400008008; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=JAJOJ90lUsDTAnSqJwPDqTxu8hZxx9IW/Tk7n3KX5EQ=; b=iAyNGn3Splg/6W1CjJUmWX+XA4CuHDDyf1kUBFL+OE+eUpqmqGhuVTa9 liuwxMygUc3LzG0IeXWksZ5r1bVy+VLjkiIR5E9g9n5e9nWVIQlyCR5Yy EB5PA45xKigZSyjjSR65yzrbeZk+CFOm023YfvnGefnsDbg7lh8/3GWqS g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjwHAC/3X1OtJV2b/2dsb2JhbABZgmUhT1EGxQ+BJhZ0giUBAQEEOj8MBAIBCBEEAQEBChQJBzIUCQgBAQQBDQUIAYg4AQcFyTMXjh4xBwaDHoEVBJpMkSaDMYIr
X-IronPort-AV: E=Sophos;i="4.97,952,1389744000"; d="scan'208";a="39747614"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-3.cisco.com with ESMTP; 29 Apr 2014 19:06:47 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s3TJ6ljS015380 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 29 Apr 2014 19:06:47 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Tue, 29 Apr 2014 14:06:47 -0500
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Black, David" <david.black@emc.com>, Jeffrey Haas <jhaas@pfrc.org>
Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Topic: Gen-ART review of draft-ietf-bfd-mib-18
Thread-Index: Ac9i7PyERuk5jZsyQOKSHRHy2Ij/LwAG2CxAABnaMYAAHWa2AAABXuyAAAM2hqA=
Date: Tue, 29 Apr 2014 19:06:46 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941E11775C@xmb-aln-x01.cisco.com>
References: <8D3D17ACE214DC429325B2B98F3AE712076C437CE3@MX15A.corp.emc.com> <CECE764681BE964CBE1DFF78F3CDD3941E114938@xmb-aln-x01.cisco.com> <8D3D17ACE214DC429325B2B98F3AE712076C437EA9@MX15A.corp.emc.com> <20140429145824.GR1256@pfrc> <8D3D17ACE214DC429325B2B98F3AE712076C437F73@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712076C437F73@MX15A.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.244.77]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JUdbstD7A-9QcsobCxKVDK1Sd3Q
Cc: "General Area Review Team \(gen-art@ietf.org\)" <gen-art@ietf.org>, "Zafar Ali \(zali\)" <zali@cisco.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 19:06:51 -0000

Hi David,

BFD-MIB-19 with suggested text has just been published.

URL:            http://www.ietf.org/internet-drafts/draft-ietf-bfd-mib-19.t=
xt
Status:         https://datatracker.ietf.org/doc/draft-ietf-bfd-mib/
Htmlized:       http://tools.ietf.org/html/draft-ietf-bfd-mib-19
Diff:           http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-bfd-mib-19

Thanks again!

-Nobo

> -----Original Message-----
> From: Black, David [mailto:david.black@emc.com]
> Sent: Tuesday, April 29, 2014 11:38 AM
> To: Jeffrey Haas
> Cc: Nobo Akiya (nobo); tnadeau@lucidvision.com; Zafar Ali (zali); General
> Area Review Team (gen-art@ietf.org); rtg-bfd@ietf.org; ietf@ietf.org; Bla=
ck,
> David
> Subject: RE: Gen-ART review of draft-ietf-bfd-mib-18
>=20
> Jeff - could you work w/Nobo to get the word "historical" included in the
> MIB draft as a characterization of BFD version 0 ?  For example, the foll=
owing
> text could be added to the introduction:
>=20
>    because the BFD version 0 protocol is primarily of historical interest
>    by comparison to the widespread deployment of the BFD version 1
> protocol.
>=20
> Thanks,
> --David
>=20
>=20
> > -----Original Message-----
> > From: Jeffrey Haas [mailto:jhaas@pfrc.org]
> > Sent: Tuesday, April 29, 2014 10:58 AM
> > To: Black, David
> > Cc: Nobo Akiya (nobo); tnadeau@lucidvision.com; Zafar Ali (zali);
> > General Area Review Team (gen-art@ietf.org); rtg-bfd@ietf.org;
> > ietf@ietf.org
> > Subject: Re: Gen-ART review of draft-ietf-bfd-mib-18
> >
> > On Tue, Apr 29, 2014 at 02:00:05AM -0400, Black, David wrote:
> > > With respect to the MIB, this concern is a nit, so I'm ok with going
> > > ahead
> > without
> > > making this change ...
> > >
> > > ... However ...
> > >
> > > Your WG chairs and AD should be concerned that this significant flaw
> > > in BFD version 0 (justifying a "SHOULD NOT use" recommendation) is
> > undocumented.
> >
> > And also un-RFCed.
> >
> > It was a "work in progress" that never fully saw the light of full
> > deployment.  Vendors very quickly moved to version 1 which fixed a
> > critical issue in the state machine.  If any version 0 survives, it's
> > historical and likely to be a source of operational agony rather than a
> useful feature.
> >
> > -- Jeff


From nobody Tue Apr 29 12:16:18 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E3B101A0939 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:16:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.843
X-Spam-Level: 
X-Spam-Status: No, score=0.843 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, SPF_NEUTRAL=0.779] autolearn=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 fNz_9a2k6A5x for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:16:09 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id C4F0B1A048C for <ietf@ietf.org>; Tue, 29 Apr 2014 12:16:08 -0700 (PDT)
Received: (qmail 83947 invoked from network); 29 Apr 2014 19:16:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=147ea.535ffa76.k1404; bh=uiuoYTbv/LN7B4Nn53CCxyItKGJI9H09GaXuQQ4UQqs=; b=Y20MQokJy0CFRVJlXJKD5we/FclQwPhqhHsmPPwkKm09C5gTg/9d8eIbGY4phsxyFk0MCZZMDXOTxMUmj2bMjefYxpAMBJbnfZ1ktfMXVidtswZ2JQsNSQbd/dTSSQvVRPQsEfWgfKGuE0mdGuL9jdIAad5CfqTcQyY+ciYuiuHIZHjfx8gg5s6MTYHe5IG0IR116clK1HU57nYou2HY1AB6uCBiCu2ay0uoA9fS43Ppm3/ZPnljbBFYNv2JGr2K
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:mime-version:content-type:user-agent:cleverness; s=147ea.535ffa76.k1404; bh=uiuoYTbv/LN7B4Nn53CCxyItKGJI9H09GaXuQQ4UQqs=; b=UE54bwv0QIMLZ12bLtZXVybtg653tVyvRdgRZUzIJ9XIZ8NpWeV1dskzTLU5/oaEkjoKO+vYfUt5USzLM7sKbnpk62DiBd/Xw9CuiZAwod8E7OrECoOOnI+lqBi3H8wx0j7hcg8vXl9bc8Qbc4sjDXPEQ+D9GC6pZp4xRaEk+dArKU6VXTXs8lG+7AYcIXZWtsx0b/eJ5yirPcXZJtQwoVqkT1bzA52+YIfcldX4N/MJJaXzT3WHiTH7Kc/SF7ah
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 29 Apr 2014 19:16:05 -0000
Date: 29 Apr 2014 15:16:05 -0400
Message-ID: <alpine.BSF.2.00.1404291512550.3309@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "IETF general list" <ietf@ietf.org>
Subject: Google.com hops on the DMARC bandwagon
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3ITRnqV1jwKQbMWyhtHz18pM4cM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 19:16:13 -0000

I see that google.com now publishes a DMARC policy of p=quarantine.

While this won't bounce people off lists like p=reject does, it still 
makes it fairly pointless to post to this or any other list from a 
google.com address, since no recipients hosted at Google, Hotmail, Yahoo, 
AOL, Comcast, or other large providers will see it.

If you're at Google, you might want to find yourself a less broken 
address, and perhaps ask the people in your mail team if their intention 
was to tell you not to particpate in the IETF on work time.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Tue Apr 29 12:30:37 2014
Return-Path: <christopher.morrow@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC2201A0972 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:30:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.8
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 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, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 eSUDoPGAbLM7 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:30:32 -0700 (PDT)
Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) by ietfa.amsl.com (Postfix) with ESMTP id CCD541A04F1 for <ietf@ietf.org>; Tue, 29 Apr 2014 12:30:31 -0700 (PDT)
Received: by mail-lb0-f172.google.com with SMTP id p9so511401lbv.17 for <ietf@ietf.org>; Tue, 29 Apr 2014 12:30:30 -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:message-id:subject :from:to:cc:content-type; bh=FbjBhtAX/WSuWCTGizakBGliFK/C0YhqUc0HBrdBIQo=; b=JRsHYDeWqbDj0l9lRwDYKU/NziBsdFEiYa3ei+ng7jKus8fwhbCKtLYAphCqj3hKq8 gzRr7m+P29anqFlEyCF15lyl3mz4JmAH81igqsY2uJzGmRGJZA65yF/gLB6RcvQdJmn6 8EEvdlgaZpfWlN8DFS9v88b18761G3Rh3r3J6o+QAedexS70nH+ZkRWdqezOvMWS/RMg UPck6kWUkGnyD5DSSjlWNkeFO7F0VhX0BfLbBSC2q7YykwxdHh4EX7d8GV4P7Lc67h85 PS4Wnf56xpZHojtxwU5YkpuvyQQH2w5MestudMxcyncZ8nV+548V1pG/2ZsfcGMj9njt 3N1g==
MIME-Version: 1.0
X-Received: by 10.112.137.5 with SMTP id qe5mr707077lbb.16.1398799829921; Tue, 29 Apr 2014 12:30:29 -0700 (PDT)
Sender: christopher.morrow@gmail.com
Received: by 10.114.95.74 with HTTP; Tue, 29 Apr 2014 12:30:29 -0700 (PDT)
In-Reply-To: <alpine.BSF.2.00.1404291512550.3309@joyce.lan>
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan>
Date: Tue, 29 Apr 2014 15:30:29 -0400
X-Google-Sender-Auth: yLH8Lx-yKf4UbeKL07XUKUKBbVI
Message-ID: <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com>
Subject: Re: Google.com hops on the DMARC bandwagon
From: Christopher Morrow <morrowc.lists@gmail.com>
To: John R Levine <johnl@taugh.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/15z_Y6katyNTm8Brb6GWGnJyghQ
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 19:30:33 -0000

On Tue, Apr 29, 2014 at 3:16 PM, John R Levine <johnl@taugh.com> wrote:
> I see that google.com now publishes a DMARC policy of p=quarantine.
>
> While this won't bounce people off lists like p=reject does, it still makes
> it fairly pointless to post to this or any other list from a google.com

google.com or gmail.com ?

(corporate users or regular-old-consumer-gmail-users)

> address, since no recipients hosted at Google, Hotmail, Yahoo, AOL, Comcast,
> or other large providers will see it.
>
> If you're at Google, you might want to find yourself a less broken address,
> and perhaps ask the people in your mail team if their intention was to tell
> you not to particpate in the IETF on work time.
>
> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.
>


From nobody Tue Apr 29 12:33:07 2014
Return-Path: <fergie@people.ops-trust.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF4D61A09C0 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:33:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.353
X-Spam-Level: 
X-Spam-Status: No, score=-1.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 2TnOE3Z5zKU0 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:33:03 -0700 (PDT)
Received: from people.ops-trust.net (people.usa5.ops-trust.net [199.168.91.182]) by ietfa.amsl.com (Postfix) with ESMTP id D498E1A09B5 for <ietf@ietf.org>; Tue, 29 Apr 2014 12:33:03 -0700 (PDT)
Received: from [192.168.10.155] (unknown [64.122.169.98]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: fergie) by people.ops-trust.net (Postfix) with ESMTPSA id 61F701468003; Tue, 29 Apr 2014 19:33:01 +0000 (UTC)
Message-ID: <535FFE6C.3040006@people.ops-trust.net>
Date: Tue, 29 Apr 2014 12:33:00 -0700
From: Paul Ferguson <fergie@people.ops-trust.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Christopher Morrow <morrowc.lists@gmail.com>,  John R Levine <johnl@taugh.com>
Subject: Re: Google.com hops on the DMARC bandwagon
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com>
In-Reply-To: <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VdWcvV1nt2UmLmyIdUf9-BHju40
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 19:33:05 -0000

Below:

On 4/29/2014 12:30 PM, Christopher Morrow wrote:

> On Tue, Apr 29, 2014 at 3:16 PM, John R Levine <johnl@taugh.com> wrote:
>> I see that google.com now publishes a DMARC policy of p=quarantine.
>>
>> While this won't bounce people off lists like p=reject does, it still makes
>> it fairly pointless to post to this or any other list from a google.com
> 
> google.com or gmail.com ?
> 
> (corporate users or regular-old-consumer-gmail-users)

google.com:

https://dmarcian.com/dmarc-inspector/google.com

- ferg

> 
>> address, since no recipients hosted at Google, Hotmail, Yahoo, AOL, Comcast,
>> or other large providers will see it.
>>
>> If you're at Google, you might want to find yourself a less broken address,
>> and perhaps ask the people in your mail team if their intention was to tell
>> you not to particpate in the IETF on work time.
>>
>> Regards,
>> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
>> Please consider the environment before reading this e-mail.
>>
> 


-- 
Paul Ferguson
VP Threat Intelligence, IID
PGP Public Key ID: 0x54DC85B2


From nobody Tue Apr 29 12:33:33 2014
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B76391A09C5 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_110=0.6, J_CHICKENPOX_14=0.6, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 3hxurWiFWjsY for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:33:25 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.4]) by ietfa.amsl.com (Postfix) with ESMTP id 816EF1A09C4 for <ietf@ietf.org>; Tue, 29 Apr 2014 12:33:25 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES532.agna.amgreetings.com ([::1]) with mapi id 14.03.0158.001;  Tue, 29 Apr 2014 15:33:23 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: Christopher Morrow <morrowc.lists@gmail.com>, John R Levine <johnl@taugh.com>
Subject: RE: Google.com hops on the DMARC bandwagon
Thread-Topic: Google.com hops on the DMARC bandwagon
Thread-Index: AQHPY9+DSMV5W6CvEEmqi04fVoCH6JspPkOA//+9pHA=
Date: Tue, 29 Apr 2014 19:33:22 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com>
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com>
In-Reply-To: <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.15.231]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rigBI3kzMu_rluXEBbESCIh7GTk
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 19:33:27 -0000

DQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0ZiBbbWFpbHRvOmll
dGYtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIENocmlzdG9waGVyIE1vcnJvdw0KPiBT
ZW50OiBUdWVzZGF5LCBBcHJpbCAyOSwgMjAxNCAzOjMwIFBNDQo+IFRvOiBKb2huIFIgTGV2aW5l
DQo+IENjOiBJRVRGIGdlbmVyYWwgbGlzdA0KPiBTdWJqZWN0OiBSZTogR29vZ2xlLmNvbSBob3Bz
IG9uIHRoZSBETUFSQyBiYW5kd2Fnb24NCj4gDQo+IE9uIFR1ZSwgQXByIDI5LCAyMDE0IGF0IDM6
MTYgUE0sIEpvaG4gUiBMZXZpbmUgPGpvaG5sQHRhdWdoLmNvbT4gd3JvdGU6DQo+ID4gSSBzZWUg
dGhhdCBnb29nbGUuY29tIG5vdyBwdWJsaXNoZXMgYSBETUFSQyBwb2xpY3kgb2YgcD1xdWFyYW50
aW5lLg0KPiA+DQo+ID4gV2hpbGUgdGhpcyB3b24ndCBib3VuY2UgcGVvcGxlIG9mZiBsaXN0cyBs
aWtlIHA9cmVqZWN0IGRvZXMsIGl0IHN0aWxsDQo+ID4gbWFrZXMgaXQgZmFpcmx5IHBvaW50bGVz
cyB0byBwb3N0IHRvIHRoaXMgb3IgYW55IG90aGVyIGxpc3QgZnJvbSBhDQo+ID4gZ29vZ2xlLmNv
bQ0KPiANCj4gZ29vZ2xlLmNvbSBvciBnbWFpbC5jb20gPw0KPiANCj4gKGNvcnBvcmF0ZSB1c2Vy
cyBvciByZWd1bGFyLW9sZC1jb25zdW1lci1nbWFpbC11c2VycykNCj4gDQoNCkdtYWlsLmNvbSBp
cyBzdGlsbCBwPW5vbmUuDQoNCj4gPiBhZGRyZXNzLCBzaW5jZSBubyByZWNpcGllbnRzIGhvc3Rl
ZCBhdCBHb29nbGUsIEhvdG1haWwsIFlhaG9vLCBBT0wsDQo+ID4gQ29tY2FzdCwgb3Igb3RoZXIg
bGFyZ2UgcHJvdmlkZXJzIHdpbGwgc2VlIGl0Lg0KPiA+DQo+ID4gSWYgeW91J3JlIGF0IEdvb2ds
ZSwgeW91IG1pZ2h0IHdhbnQgdG8gZmluZCB5b3Vyc2VsZiBhIGxlc3MgYnJva2VuDQo+ID4gYWRk
cmVzcywgYW5kIHBlcmhhcHMgYXNrIHRoZSBwZW9wbGUgaW4geW91ciBtYWlsIHRlYW0gaWYgdGhl
aXINCj4gPiBpbnRlbnRpb24gd2FzIHRvIHRlbGwgeW91IG5vdCB0byBwYXJ0aWNwYXRlIGluIHRo
ZSBJRVRGIG9uIHdvcmsgdGltZS4NCj4gPg0KPiA+IFJlZ2FyZHMsDQo+ID4gSm9obiBMZXZpbmUs
IGpvaG5sQHRhdWdoLmNvbSwgVGF1Z2hhbm5vY2sgTmV0d29ya3MsIFRydW1hbnNidXJnIE5ZDQo+
ID4gUGxlYXNlIGNvbnNpZGVyIHRoZSBlbnZpcm9ubWVudCBiZWZvcmUgcmVhZGluZyB0aGlzIGUt
bWFpbC4NCj4gPg0KDQo=


From nobody Tue Apr 29 12:55:30 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E7F91A09D8 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:54:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.421
X-Spam-Level: 
X-Spam-Status: No, score=0.421 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, MISSING_HEADERS=1.021, SPF_PASS=-0.001] autolearn=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 UFffV6Otezw4 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 12:54:58 -0700 (PDT)
Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3931A09D7 for <ietf@ietf.org>; Tue, 29 Apr 2014 12:54:57 -0700 (PDT)
Received: by mail-la0-f54.google.com with SMTP id e16so521490lan.41 for <ietf@ietf.org>; Tue, 29 Apr 2014 12:54:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:cc:content-type; bh=teTVFFmJZo/hp2Iox3GTjJM4fpA/NzkammIB+ucz3ek=; b=LEzZzatYnSxCBOrtJqS8mYQpBxIZkCBHuocXcsQToeijtdbbP3LM+7YaOsBi/yfOEK qPB6HOac0XtACT3x+2RBsiLzJ7zFAtyV3jPtaIPwrqzSo79v2Hm49FV0ceNv6UJpr0aF EGVl2YS/XQCKVgNEyWW01x1TWCSPbuR+S/E/foXCErFJTKj8DMQtJe8T1e9hKym6xVac 6jYBW8c6+ZiUrt06uzoFOOtx8NMuDIzONxnKirx08QfGQ+bPlJmfo2exMnmGVD3/iqg9 1k2HEHvU8ePtv5Hf/pvHI99jnXTAIfevC5e6khDqgoZP1w/7RCa4GEhAKOPB6jg30sRU sBQw==
MIME-Version: 1.0
X-Received: by 10.112.156.105 with SMTP id wd9mr4653lbb.68.1398801295443; Tue, 29 Apr 2014 12:54:55 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Tue, 29 Apr 2014 12:54:55 -0700 (PDT)
Date: Tue, 29 Apr 2014 15:54:55 -0400
Message-ID: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com>
Subject: Enough DMARC whinging
From: Phillip Hallam-Baker <hallam@gmail.com>
Cc: IETF general list <ietf@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NJ-w04RJ9575Nr6IDjj0kCkuU7k
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 19:54:59 -0000

I am finding it rather hard to follow the DMARC discussion. Some folk
have managed to convince me that they are upset but working out why
would require rather a lot of spec crunching.

My best theory so far is that DMARC is some sort of email policy
statement and that either (1) some companies are now publishing a
policy that states 'reject all mail that purports to come from this
address that does not have authentication Y' or (2) some companies are
now rejecting mail not in compliance with said policy or (3) both.

There is a simple truth about DNS names: Whoever owns them makes the
rules for their use [1]. If you don't like the rules for google.com
then choose another domain to post from.


If people want email to work with mailing lists, then don't complain
about reasonable choices people want to make. Work out a way to fix
mailing lists so that they work properly.

There is no reason we can't change the way From works. Or add new from headers.

Are we engineers or curators of the past?


[1] Thus be rather suspicious of folk who claim that we merely rent
the use on terms of their choosing.

-- 
Website: http://hallambaker.com/


From nobody Tue Apr 29 13:55:47 2014
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 020D71A063B for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 13:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.919
X-Spam-Level: 
X-Spam-Status: No, score=0.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_110=0.6, J_CHICKENPOX_14=0.6, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 S9kYCs5IZrRA for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 13:55:45 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 087DD1A03FC for <ietf@ietf.org>; Tue, 29 Apr 2014 13:55:44 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id 19240CC0AD for <ietf@ietf.org>; Tue, 29 Apr 2014 16:55:43 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id kCN+ItNaUAVC for <ietf@ietf.org>; Tue, 29 Apr 2014 16:55:34 -0400 (EDT)
Received: from new-host.home (pool-173-76-155-14.bstnma.fios.verizon.net [173.76.155.14]) by server1.neighborhoods.net (Postfix) with ESMTPSA id 80C44CC0B3 for <ietf@ietf.org>; Tue, 29 Apr 2014 16:55:25 -0400 (EDT)
Message-ID: <536011BD.3050704@meetinghouse.net>
Date: Tue, 29 Apr 2014 16:55:25 -0400
From: Miles Fidelman <mfidelman@meetinghouse.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:28.0) Gecko/20100101 Firefox/28.0 SeaMonkey/2.25
MIME-Version: 1.0
CC: IETF general list <ietf@ietf.org>
Subject: Re: Google.com hops on the DMARC bandwagon
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com>
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/AkdU2i1wTn3HmoctqIEzD-70IlA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 20:55:46 -0000

MH Michael Hammer (5304) wrote:
>
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Christopher Morrow
>> Sent: Tuesday, April 29, 2014 3:30 PM
>> To: John R Levine
>> Cc: IETF general list
>> Subject: Re: Google.com hops on the DMARC bandwagon
>>
>> On Tue, Apr 29, 2014 at 3:16 PM, John R Levine <johnl@taugh.com> wrote:
>>> I see that google.com now publishes a DMARC policy of p=quarantine.
>>>
>>> While this won't bounce people off lists like p=reject does, it still
>>> makes it fairly pointless to post to this or any other list from a
>>> google.com
>> google.com or gmail.com ?
>>
>> (corporate users or regular-old-consumer-gmail-users)
>>
> Gmail.com is still p=none.
>

Ahh... so we can't expect to see Vint in any of the ietf discussions in 
the near future!

Hmmm.... Miles

-- 
In theory, there is no difference between theory and practice.
In practice, there is.   .... Yogi Berra


From nobody Tue Apr 29 14:00:52 2014
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C8F51A093B for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 14:00:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.33
X-Spam-Level: 
X-Spam-Status: No, score=-0.33 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.651] autolearn=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 BHlc2ZGJ3cpn for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 14:00:48 -0700 (PDT)
Received: from egssmtp01.att.com (egssmtp01.att.com [144.160.112.12]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE2F1A08D8 for <ietf@ietf.org>; Tue, 29 Apr 2014 14:00:48 -0700 (PDT)
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by egssmtp01.att.com ( egs 8.14.5/8.14.5) with ESMTP id s3TL0j5s017220 for <ietf@ietf.org>; Tue, 29 Apr 2014 16:00:46 -0500
Received: from vpn-135-70-100-208.vpn.swst.att.com ([135.70.100.208]) by maillennium.att.com (mailgw1) with ESMTP id <20140429210044gw100j0cole>; Tue, 29 Apr 2014 21:00:44 +0000
X-Originating-IP: [135.70.100.208]
Message-ID: <536012FC.9020803@att.com>
Date: Tue, 29 Apr 2014 17:00:44 -0400
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
CC: IETF general list <ietf@ietf.org>
Subject: Re: Google.com hops on the DMARC bandwagon
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com> <536011BD.3050704@meetinghouse.net>
In-Reply-To: <536011BD.3050704@meetinghouse.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/d1gz60nut4aHprww3DI1oyClIIo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 21:00:49 -0000

On 4/29/14, 4:55 PM, Miles Fidelman wrote:
>
>>>
>>> On Tue, Apr 29, 2014 at 3:16 PM, John R Levine <johnl@taugh.com> wrote:
>>>> I see that google.com now publishes a DMARC policy of p=quarantine.
>>>>
>>>> While this won't bounce people off lists like p=reject does, it still
>>>> makes it fairly pointless to post to this or any other list from a
>>>> google.com
>>>
>
> Ahh... so we can't expect to see Vint in any of the ietf discussions 
> in the near future!

Anyone with mail servers that look at the dmarc settings won't see 
postings. People behind mail servers that do NOT look at the dmarc 
settings will see the postings just fine.

     Tony Hansen


From nobody Tue Apr 29 14:28:49 2014
Return-Path: <R.E.Sonneveld@sonnection.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAFCE1A0792 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 14:28:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=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 fXnbkOFPprR8 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 14:28:41 -0700 (PDT)
Received: from mx10.mailtransaction.com (mx10.mailtransaction.com [88.198.59.241]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD491A02AC for <ietf@ietf.org>; Tue, 29 Apr 2014 14:28:41 -0700 (PDT)
Received: from mx24.mailtransaction.com (mx21.mailtransaction.com [78.46.16.236]) by mx10.mailtransaction.com (Postfix) with ESMTP id 3gJGDz5YX0z5Mhcx; Tue, 29 Apr 2014 23:28:35 +0200 (CEST)
Received: from jaguar.sonnection.nl (D57E1702.static.ziggozakelijk.nl [213.126.23.2]) by mx24.mailtransaction.com (Postfix) with ESMTP id 3gJGDz4GtNz1L8cK; Tue, 29 Apr 2014 23:28:35 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by jaguar.sonnection.nl (Postfix) with ESMTP id A1E43122F03; Tue, 29 Apr 2014 23:13:32 +0200 (CEST)
X-Virus-Scanned: amavisd-new at sonnection.nl
Received: from jaguar.sonnection.nl ([127.0.0.1]) by localhost (jaguar.sonnection.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id ZcEeG5xLrL9w; Tue, 29 Apr 2014 23:13:28 +0200 (CEST)
Received: from [192.168.1.49] (unknown [192.168.1.49]) by jaguar.sonnection.nl (Postfix) with ESMTPSA id BB1DC122E88; Tue, 29 Apr 2014 23:13:27 +0200 (CEST)
Message-ID: <536015F7.2070100@sonnection.nl>
Date: Tue, 29 Apr 2014 23:13:27 +0200
From: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
Organization: Sonnection B.V.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Tony Hansen <tony@att.com>
Subject: Re: Google.com hops on the DMARC bandwagon
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com> <536011BD.3050704@meetinghouse.net> <536012FC.9020803@att.com>
In-Reply-To: <536012FC.9020803@att.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sonnection.nl; s=2009; t=1398806915; bh=I52XgbtbYxTWAf67bD20/f2POaPBi2803C3LPxMjRJQ=; h=Message-ID:Date:From:To:Subject:From; b=XsLcpBebyVOmfwFofO8d9f1i5ZfWP80x+pdZifNbCVuMn9tSl86nrsLuW5vsRX2Ta 3m88RN5V/myB61WcM7WscwiI+EuLwlSEwOolfs5yEKT1CpBEGk3uP7Viq3ej6w9P1G PohchbMZV3y/7S23ooEdUgnkJo0VYpVwMw3Cekdk=
DKIM-Filter: OpenDKIM Filter v2.8.2 mx10.mailtransaction.com 3gJGDz5YX0z5Mhcx
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tD074n0h3-a2vYT9EZOT6WHKBFg
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: R.E.Sonneveld@sonnection.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 21:28:44 -0000

On 04/29/2014 11:00 PM, Tony Hansen wrote:
> On 4/29/14, 4:55 PM, Miles Fidelman wrote:
>>
>>>>
>>>> On Tue, Apr 29, 2014 at 3:16 PM, John R Levine <johnl@taugh.com> 
>>>> wrote:
>>>>> I see that google.com now publishes a DMARC policy of p=quarantine.
>>>>>
>>>>> While this won't bounce people off lists like p=reject does, it still
>>>>> makes it fairly pointless to post to this or any other list from a
>>>>> google.com
>>>>
>>
>> Ahh... so we can't expect to see Vint in any of the ietf discussions 
>> in the near future!
>
> Anyone with mail servers that look at the dmarc settings won't see 
> postings. People behind mail servers that do NOT look at the dmarc 
> settings will see the postings just fine.

To paraphrase: WYPIWYG (What You Publish Is What You Get).

/rolf

And, yes, there are a number of other meanings that fit the same acronym 
[1].

[1] http://acronyms.thefreedictionary.com/WYPIWYG


From nobody Tue Apr 29 14:49:46 2014
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50C6D1A09A1; Tue, 29 Apr 2014 14:49:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.601
X-Spam-Level: 
X-Spam-Status: No, score=-1.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 h8g-QI-72zUJ; Tue, 29 Apr 2014 14:49:39 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2F91A09B0; Tue, 29 Apr 2014 14:49:39 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 8E6E11E45BC; Tue, 29 Apr 2014 14:49:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6noV-kbzWSbN; Tue, 29 Apr 2014 14:49:24 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) by c8a.amsl.com (Postfix) with ESMTPSA id E9D381E45BB; Tue, 29 Apr 2014 14:49:23 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Subject: =?windows-1252?Q?IAB_Sends_Comments_to_ICANN_on_the_Transition_N?= =?windows-1252?Q?TIA=92s_Stewardship_of_the_IANA_Functions?=
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Tue, 29 Apr 2014 17:49:36 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <CBFECA14-4ADD-4C2C-828D-3000FCB965A7@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4xkj06AcJ5GsnoluvQqj8-9bifw
Cc: internetgovtech@iab.org, IAB <iab@iab.org>, IETF <ietf@ietf.org>, ianatransition@icann.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: internetgovtech@iab.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 21:49:41 -0000

Today, the IAB sent comments regarding the =93Draft Proposal, Based on =
Initial Community Feedback, of the Principles and Mechanisms and the =
Process to Develop a Proposal to Transition NTIA=92s Stewardship of the =
IANA Functions=94.  The comments are on the IAB web site:
=
http://www.iab.org/wp-content/IAB-uploads/2014/04/iab-response-to-20140408=
-20140428a.pdf

Thanks for your consideration,
  Russ Housley
  IAB Chair=


From nobody Tue Apr 29 14:56:28 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61661A09C6 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 14:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.353
X-Spam-Level: 
X-Spam-Status: No, score=-1.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 VDMJuK9zRWvy for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 14:56:26 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 33EDD1A09A9 for <ietf@ietf.org>; Tue, 29 Apr 2014 14:56:26 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P780Q6SJBK0013GU@mauve.mrochek.com> for ietf@ietf.org; Tue, 29 Apr 2014 14:51:25 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P77SH5U06O000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 29 Apr 2014 14:51:19 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P780Q4IQVA000054@mauve.mrochek.com>
Date: Tue, 29 Apr 2014 14:36:28 -0700 (PDT)
Subject: Re: Google.com hops on the DMARC bandwagon
In-reply-to: "Your message dated Tue, 29 Apr 2014 23:13:27 +0200" <536015F7.2070100@sonnection.nl>
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com> <536011BD.3050704@meetinghouse.net> <536012FC.9020803@att.com> <536015F7.2070100@sonnection.nl>
To: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XqnlSpmngb4NM4F2i8GhdvGqYPI
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 21:56:27 -0000

> On 04/29/2014 11:00 PM, Tony Hansen wrote:
> > On 4/29/14, 4:55 PM, Miles Fidelman wrote:
> >>
> >>>>
> >>>> On Tue, Apr 29, 2014 at 3:16 PM, John R Levine <johnl@taugh.com>
> >>>> wrote:
> >>>>> I see that google.com now publishes a DMARC policy of p=quarantine.
> >>>>>
> >>>>> While this won't bounce people off lists like p=reject does, it still
> >>>>> makes it fairly pointless to post to this or any other list from a
> >>>>> google.com
> >>>>
> >>
> >> Ahh... so we can't expect to see Vint in any of the ietf discussions
> >> in the near future!
> >
> > Anyone with mail servers that look at the dmarc settings won't see
> > postings. People behind mail servers that do NOT look at the dmarc
> > settings will see the postings just fine.

No, because those postings will bounce, and cause those users to get
unsubscribed from the list. In order to protect such subscribers from that, the
list owner has limited options, none of which are good. For example, one of
them is to block all users from that domain from posting.

> To paraphrase: WYPIWYG (What You Publish Is What You Get).

I think a paraphrase of Brian Reid is more in order here:

WYPIWYD (What You Publish Is What You Deserve)

				Ned


From nobody Tue Apr 29 15:00:17 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C32A1A09CA for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 15:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 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, J_CHICKENPOX_16=0.6, SPF_PASS=-0.001] autolearn=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 DJ8ESXue0X6l for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 15:00:16 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) by ietfa.amsl.com (Postfix) with ESMTP id F29031A09DB for <ietf@ietf.org>; Tue, 29 Apr 2014 15:00:15 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id fp1so755317pdb.34 for <ietf@ietf.org>; Tue, 29 Apr 2014 15:00:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=DZdT947uplZSEluDPmvqajKMti5IY3bTWkwvv8DGuA0=; b=M/ol3201v1TxImPadm3UuKAClDjosYsxp2F6fbOi2KnZy38jw92OAVe9om6dSs8HNb ZWmoV4wVGx86FH17fwuYzZ3fWMoFr3lqt5cW5GWe13FeH+HDWj/kD3PQEnxYhcawTEU9 7LY2Cu6ZOJ7PSbGQra5kdZiTWANQhXFSKFvxKX/UJnzoF2fX7XUDb+kVgG2jjtG8qazE eMgVhr+AeoXiJUtzdP0da1QXd7J0OkhBW383F1rM74NUwq0HmNKsFsCATuBd5Vu9TprM YUUjFLISV6ke5/fxHdgoKTTfWb+w7pD/dcPqtyeZkWi1t7oVMWSsDuKePDQty2RYr5eB GUEg==
X-Received: by 10.66.164.5 with SMTP id ym5mr1001229pab.50.1398808814666; Tue, 29 Apr 2014 15:00:14 -0700 (PDT)
Received: from [192.168.0.54] (107-0-5-6-ip-static.hfc.comcastbusiness.net. [107.0.5.6]) by mx.google.com with ESMTPSA id ck10sm88651504pac.0.2014.04.29.15.00.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Apr 2014 15:00:13 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_7405A57C-4389-4A85-B818-7FE566476BED"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Will mailing lists survive DMARC?
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <20140429175606.2856.qmail@joyce.lan>
Date: Tue, 29 Apr 2014 15:00:12 -0700
Message-Id: <0A46725A-D80C-4F64-BACE-B2C73A04782D@gmail.com>
References: <20140429175606.2856.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XJh0Z_sOoPRU8IxK22nqUBI79ts
Cc: ietf@ietf.org, paf@frobbit.se
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 22:00:17 -0000

--Apple-Mail=_7405A57C-4389-4A85-B818-7FE566476BED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Apr 29, 2014, at 10:56 AM, John Levine <johnl@taugh.com> wrote:

> What changed is that two of the largest consumer mail providers had
> huge security breaches where crooks stole user info including their
> address books (both admit it, no conspiracizing needed) and used DMARC
> as a sledgehammer to try and mitigate the damage.  I don't think
> anyone is opposed to mitigating damage, but these particular efforts
> had the predictable side effect of dumping costs on unrelated third
> parties which AOL and Yahoo have so far done nothing to address.
> Yahoo's blog admits that they are affecting 30,000 other providers, so
> they know this is not a trivial problem.

Dear John,

=46rom our experience, similar security problems affect social websites =
due to poor browser plugin vetting or poor cookie management.  Being =
highly balkanized, no equivalent DMARC policy will likely impact social =
websites since damage to privacy or security seldom become public.

No cryptographic mailing-list token or a list of trustworthy =
mailing-lists by outside vendors can remedy this problem due to =
liability risks.  Companies that deployed p=3Dreject against user =
accounts neglected serious security issues for years.  In many cases, =
their services are on behalf of other ISPs.  Fortunately, gmail.com has =
not asserted p=3Dreject.

Redirecting responsibility by using DKIM or SPF is at the crux and the =
basis for DMARC.  Neither of these schemes authenticate the domain =
introducing the message and ignore intended recipients. This indirection =
has become endemic and makes it difficult to scale for IPv6 or to permit =
valid third-party services.

One viable method agnostic to verification schemes is =
http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06 (TPA).  Yahoo =
and AOL can compile their needed TPA exceptions.  This scheme should =
scale better than other extensions in use, especially DKIM or SPF. =20

There will be an effort made to better generalize the TPA expired draft. =
  http://tools.ietf.org/html/rfc6541 (ATPS) was hostile to existing =
mailing-list services and, as such, could not be deployed.  Nor was it =
more suitable for high volume email services.  An effort to change =46rom =
header fields will have users guessing which field indicates who =
authored the message and in the end will provide no benefit.

Regards,
Douglas Otis  =20=

--Apple-Mail=_7405A57C-4389-4A85-B818-7FE566476BED
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space;"><br>On Apr 29, 2014, at 10:56 =
AM, John Levine &lt;<a =
href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt; =
wrote:<br><br><blockquote type=3D"cite">What changed is that two of the =
largest consumer mail providers had<br>huge security breaches where =
crooks stole user info including their<br>address books (both admit it, =
no conspiracizing needed) and used DMARC<br>as a sledgehammer to try and =
mitigate the damage. &nbsp;I don't think<br>anyone is opposed to =
mitigating damage, but these particular efforts<br>had the predictable =
side effect of dumping costs on unrelated third<br>parties which AOL and =
Yahoo have so far done nothing to address.<br>Yahoo's blog admits that =
they are affecting 30,000 other providers, so<br>they know this is not a =
trivial problem.<br></blockquote><br><div>Dear =
John,</div><div><br></div><div>=46rom our experience, similar security =
problems affect social websites due to poor browser plugin vetting or =
poor cookie management. &nbsp;Being highly balkanized, no equivalent =
DMARC policy will likely impact social websites since damage to privacy =
or security seldom become public.</div><div><br></div><div>No =
cryptographic mailing-list token or a list of trustworthy mailing-lists =
by outside vendors can remedy this problem due to liability risks. =
&nbsp;Companies that deployed p=3Dreject against user accounts neglected =
serious security issues for years. &nbsp;In many cases, their services =
are on behalf of other ISPs. &nbsp;Fortunately, <a =
href=3D"http://gmail.com">gmail.com</a> has not asserted =
p=3Dreject.</div><div><br></div><div>Redirecting responsibility by using =
DKIM or SPF is at the crux and the basis for DMARC. &nbsp;Neither of =
these schemes authenticate the domain introducing the message and ignore =
intended recipients. This indirection has become endemic and makes it =
difficult to scale for IPv6 or to permit valid third-party =
services.</div><div><br></div><div>One viable method agnostic to =
verification schemes is&nbsp;<a =
href=3D"http://tools.ietf.org/html/draft-otis-dkim-tpa-label-06">http://to=
ols.ietf.org/html/draft-otis-dkim-tpa-label-06</a>&nbsp;(TPA). =
&nbsp;Yahoo and AOL can compile their needed TPA exceptions. &nbsp;This =
scheme should scale better than other extensions in use, especially DKIM =
or SPF. &nbsp;</div><div><br></div><div>There will be an effort made to =
better generalize the TPA expired draft. &nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc6541">http://tools.ietf.org/html/rfc=
6541</a>&nbsp;(ATPS) was hostile to existing mailing-list services and, =
as such, could not be deployed. &nbsp;Nor was it more suitable for high =
volume email services. &nbsp;An effort to change =46rom header fields =
will have users guessing which field indicates who authored the message =
and in the end will provide no =
benefit.</div><div><br></div><div>Regards,</div><div>Douglas Otis =
&nbsp;&nbsp;</div></body></html>=

--Apple-Mail=_7405A57C-4389-4A85-B818-7FE566476BED--


From nobody Tue Apr 29 15:15:21 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB1441A0971 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 15:15:18 -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, SPF_PASS=-0.001] autolearn=ham
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 FZw1wUbSLyYu for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 15:15:17 -0700 (PDT)
Received: from mail-qg0-x234.google.com (mail-qg0-x234.google.com [IPv6:2607:f8b0:400d:c04::234]) by ietfa.amsl.com (Postfix) with ESMTP id 0B68B1A0953 for <ietf@ietf.org>; Tue, 29 Apr 2014 15:15:16 -0700 (PDT)
Received: by mail-qg0-f52.google.com with SMTP id j5so988917qga.39 for <ietf@ietf.org>; Tue, 29 Apr 2014 15:15:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=wopCs0zcwpQD+7qIqQJ1H2mGPUrW3cCUB6zOvmnR/ig=; b=xfDAkhfJifoM7eMUbJovH90zXgjTARP6DDnW4vAo+PX/47mD8c7nEKpkDpwrm6BFQO DkDi7uaX+L5uhtsOMNeWCFnIKMsYc+JdVzVjUdAdrftV/0eNV15jxULq9E6s7YR7K+OV tkcw91GD/H2Z919QY+OemTmrIIo4iLd+AJQ18IzgZhYomsxShvd/G8m0BoW6dAo3Us/U zYFDK5yL4QpctCHxiiEumRU4spfR0Egie2rUQOWTrcX5H5G+gLPNAmPHEBRCyYBoVASP JWS9CQY5AayUsC8iINtYGvpe7d5Bhl7pzI6MM5BYGOvTeumG+ysaZvKmemsNcZdzrv3z cDEw==
X-Received: by 10.229.66.133 with SMTP id n5mr806487qci.0.1398809715679; Tue, 29 Apr 2014 15:15:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.205.69 with HTTP; Tue, 29 Apr 2014 15:14:55 -0700 (PDT)
In-Reply-To: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com>
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Tue, 29 Apr 2014 18:14:55 -0400
Message-ID: <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com>
Subject: Re: Enough DMARC whinging
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2ffee3625e504f835c409
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dhFAoQKWzGDBqAffHj3jc4cP8i0
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 22:15:19 -0000

--001a11c2ffee3625e504f835c409
Content-Type: text/plain; charset=UTF-8

Philip,

Here are the effects that I see. I use this gmail account for my IETF
mailing lists. I am now consistently seeing email sent from Yahoo users end
up in my spam folder with the following embedded warning message:

*Be careful with this message.* Our systems couldn't verify that this
message was really sent by yahoo.com. You might want to avoid clicking
links or replying with personal information.  Learn
more<http://support.google.com/mail/bin/answer.py?hl=en&answer=1366858&ctx=mail&authuser=1&expand=2>

The sender, of course, is completely unaware of what is happening on the
receiver's end, so they have no reason to want to change from Yahoo to
another domain for posting.

So this is imposing pain on the receiver, since I now have to consistently
check my spam folder for valid IETF email.

I see that you also use gmail, so you should start checking your spam
folder as well.

Cheers,
Andy


On Tue, Apr 29, 2014 at 3:54 PM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

> I am finding it rather hard to follow the DMARC discussion. Some folk
> have managed to convince me that they are upset but working out why
> would require rather a lot of spec crunching.
>
> My best theory so far is that DMARC is some sort of email policy
> statement and that either (1) some companies are now publishing a
> policy that states 'reject all mail that purports to come from this
> address that does not have authentication Y' or (2) some companies are
> now rejecting mail not in compliance with said policy or (3) both.
>
> There is a simple truth about DNS names: Whoever owns them makes the
> rules for their use [1]. If you don't like the rules for google.com
> then choose another domain to post from.
>
>
> If people want email to work with mailing lists, then don't complain
> about reasonable choices people want to make. Work out a way to fix
> mailing lists so that they work properly.
>
> There is no reason we can't change the way From works. Or add new from
> headers.
>
> Are we engineers or curators of the past?
>
>
> [1] Thus be rather suspicious of folk who claim that we merely rent
> the use on terms of their choosing.
>
> --
> Website: http://hallambaker.com/
>
>

--001a11c2ffee3625e504f835c409
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Philip,<div><br></div><div>Here are the effects that I see=
. I use this gmail account for my IETF mailing lists. I am now consistently=
 seeing email sent from Yahoo users end up in my spam folder with the follo=
wing embedded warning message:</div>

<div><br></div><div><b style=3D"color:rgb(85,85,85);font-family:arial,sans-=
serif;font-size:13px;line-height:21px;background-color:rgb(255,241,168)">Be=
 careful with this message.</b><span style=3D"color:rgb(85,85,85);font-fami=
ly:arial,sans-serif;font-size:13px;line-height:21px;background-color:rgb(25=
5,241,168)">=C2=A0Our systems couldn&#39;t verify that this message was rea=
lly sent by <a href=3D"http://yahoo.com">yahoo.com</a>. You might want to a=
void clicking links or replying with personal information.=C2=A0=C2=A0</spa=
n><a class=3D"acT" target=3D"_blank" href=3D"http://support.google.com/mail=
/bin/answer.py?hl=3Den&amp;answer=3D1366858&amp;ctx=3Dmail&amp;authuser=3D1=
&amp;expand=3D2" style=3D"font-family:arial,sans-serif;font-size:13px;line-=
height:21px;background-color:rgb(255,241,168)">Learn more</a><br>

</div><div><br></div><div>The sender, of course, is completely unaware of w=
hat is happening on the receiver&#39;s end, so they have no reason to want =
to change from Yahoo to another domain for posting.</div><div><br></div>

<div>So this is imposing pain on the receiver, since I now have to consiste=
ntly check my spam folder for valid IETF email.</div><div><br></div><div>I =
see that you also use gmail, so you should start checking your spam folder =
as well.</div>

<div><br></div><div>Cheers,</div><div>Andy</div></div><div class=3D"gmail_e=
xtra"><br><br><div class=3D"gmail_quote">On Tue, Apr 29, 2014 at 3:54 PM, P=
hillip Hallam-Baker <span dir=3D"ltr">&lt;<a href=3D"mailto:hallam@gmail.co=
m" target=3D"_blank">hallam@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">I am finding it rather hard to follow the DM=
ARC discussion. Some folk<br>
have managed to convince me that they are upset but working out why<br>
would require rather a lot of spec crunching.<br>
<br>
My best theory so far is that DMARC is some sort of email policy<br>
statement and that either (1) some companies are now publishing a<br>
policy that states &#39;reject all mail that purports to come from this<br>
address that does not have authentication Y&#39; or (2) some companies are<=
br>
now rejecting mail not in compliance with said policy or (3) both.<br>
<br>
There is a simple truth about DNS names: Whoever owns them makes the<br>
rules for their use [1]. If you don&#39;t like the rules for <a href=3D"htt=
p://google.com" target=3D"_blank">google.com</a><br>
then choose another domain to post from.<br>
<br>
<br>
If people want email to work with mailing lists, then don&#39;t complain<br=
>
about reasonable choices people want to make. Work out a way to fix<br>
mailing lists so that they work properly.<br>
<br>
There is no reason we can&#39;t change the way From works. Or add new from =
headers.<br>
<br>
Are we engineers or curators of the past?<br>
<br>
<br>
[1] Thus be rather suspicious of folk who claim that we merely rent<br>
the use on terms of their choosing.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Website: <a href=3D"http://hallambaker.com/" target=3D"_blank">http://halla=
mbaker.com/</a><br>
<br>
</font></span></blockquote></div><br></div>

--001a11c2ffee3625e504f835c409--


From nobody Tue Apr 29 15:19:58 2014
Return-Path: <R.E.Sonneveld@sonnection.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D57931A09FA for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 15:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.501
X-Spam-Level: 
X-Spam-Status: No, score=-1.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=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 hL9kKlhT9TuU for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 15:19:55 -0700 (PDT)
Received: from mx10.mailtransaction.com (mx10.mailtransaction.com [88.198.59.241]) by ietfa.amsl.com (Postfix) with ESMTP id B44D91A0953 for <ietf@ietf.org>; Tue, 29 Apr 2014 15:19:55 -0700 (PDT)
Received: from mx24.mailtransaction.com (mx21.mailtransaction.com [78.46.16.236]) by mx10.mailtransaction.com (Postfix) with ESMTP id 3gJHN961ZLz5Mhcx; Wed, 30 Apr 2014 00:19:53 +0200 (CEST)
Received: from jaguar.sonnection.nl (D57E1702.static.ziggozakelijk.nl [213.126.23.2]) by mx24.mailtransaction.com (Postfix) with ESMTP id 3gJHN94xskz1L8cK; Wed, 30 Apr 2014 00:19:53 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by jaguar.sonnection.nl (Postfix) with ESMTP id 6AC441230CF; Wed, 30 Apr 2014 00:19:53 +0200 (CEST)
X-Virus-Scanned: amavisd-new at sonnection.nl
Received: from jaguar.sonnection.nl ([127.0.0.1]) by localhost (jaguar.sonnection.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GXrneXonVm39; Wed, 30 Apr 2014 00:19:48 +0200 (CEST)
Received: from [192.168.1.49] (unknown [192.168.1.49]) by jaguar.sonnection.nl (Postfix) with ESMTPSA id EEACD122ED5; Wed, 30 Apr 2014 00:19:47 +0200 (CEST)
Message-ID: <53602583.4060003@sonnection.nl>
Date: Wed, 30 Apr 2014 00:19:47 +0200
From: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
Organization: Sonnection B.V.
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Google.com hops on the DMARC bandwagon
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com> <536011BD.3050704@meetinghouse.net> <536012FC.9020803@att.com> <536015F7.2070100@sonnection.nl> <01P780Q4IQVA000054@mauve.mrochek.com>
In-Reply-To: <01P780Q4IQVA000054@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sonnection.nl; s=2009; t=1398809993; bh=LTNi6nw01RiHlB8OjzHX4F+KHardOY/iooJyeUq7OKQ=; h=Message-ID:Date:From:To:Subject:From; b=LZWFW6EIJDofbYD0voEfRVZW/6b8B5R/l+XNKAQqPvXFLNbs5Pz7WFSrUM9abRool +/qCNsV1T/kZ5n5yEtXqLrzruLVJ3p1yG2ZKD4eyyo20DelhjceU31jPy61CRVZgFv Lx9xSADmBYECLMKb22XWCRzSwWlOrq2EIRWL4CQQ=
DKIM-Filter: OpenDKIM Filter v2.8.2 mx10.mailtransaction.com 3gJHN961ZLz5Mhcx
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bg65y889mQzxBVX8QM0ld8PBSVc
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: R.E.Sonneveld@sonnection.nl
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 22:19:57 -0000

On 04/29/2014 11:36 PM, Ned Freed wrote:
>> On 04/29/2014 11:00 PM, Tony Hansen wrote:
>> > On 4/29/14, 4:55 PM, Miles Fidelman wrote:
>> >>
>> >>>>
>> >>>> On Tue, Apr 29, 2014 at 3:16 PM, John R Levine <johnl@taugh.com>
>> >>>> wrote:
>> >>>>> I see that google.com now publishes a DMARC policy of 
>> p=quarantine.
>> >>>>>
>> >>>>> While this won't bounce people off lists like p=reject does, it 
>> still
>> >>>>> makes it fairly pointless to post to this or any other list from a
>> >>>>> google.com
>> >>>>
>> >>
>> >> Ahh... so we can't expect to see Vint in any of the ietf discussions
>> >> in the near future!
>> >
>> > Anyone with mail servers that look at the dmarc settings won't see
>> > postings. People behind mail servers that do NOT look at the dmarc
>> > settings will see the postings just fine.
>
> No, because those postings will bounce, and cause those users to get
> unsubscribed from the list. 

But in this case, we're talking about the p=quarantine policy that 
Google published for google.com... No bouncing (and hence no automatic 
unsubscription, unless a receiver interprets p=quarantine as 'please 
reject').

/rolf


From nobody Tue Apr 29 15:42:13 2014
Return-Path: <ned+ietf@mauve.mrochek.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD2701A0997 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 15:42:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.953
X-Spam-Level: 
X-Spam-Status: No, score=-1.953 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_110=0.6, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Y6t3RaDkJI4t for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 15:42:11 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8A81A0991 for <ietf@ietf.org>; Tue, 29 Apr 2014 15:42:11 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P782BVV2I80007XH@mauve.mrochek.com> for ietf@ietf.org; Tue, 29 Apr 2014 15:37:10 -0700 (PDT)
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=iso-8859-1; format=flowed
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P77SH5U06O000054@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 29 Apr 2014 15:37:03 -0700 (PDT)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P782BTLB96000054@mauve.mrochek.com>
Date: Tue, 29 Apr 2014 15:36:34 -0700 (PDT)
Subject: Re: Google.com hops on the DMARC bandwagon
In-reply-to: "Your message dated Wed, 30 Apr 2014 00:19:47 +0200" <53602583.4060003@sonnection.nl>
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com> <536011BD.3050704@meetinghouse.net> <536012FC.9020803@att.com> <536015F7.2070100@sonnection.nl> <01P780Q4IQVA000054@mauve.mrochek.com> <53602583.4060003@sonnection.nl>
To: "Rolf E. Sonneveld" <R.E.Sonneveld@sonnection.nl>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9l_CdDrVENbnLzDqOKzWuUMTO5w
Cc: Ned Freed <ned.freed@mrochek.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 22:42:12 -0000

> > No, because those postings will bounce, and cause those users to get
> > unsubscribed from the list.

> But in this case, we're talking about the p=quarantine policy that
> Google published for google.com... No bouncing (and hence no automatic
> unsubscription, unless a receiver interprets p=quarantine as 'please
> reject').

Fair point. My observation about the appropriate acronym stands, however.

				Ned


From nobody Tue Apr 29 16:11:27 2014
Return-Path: <tytso@thunk.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A9C71A09D7 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 16:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.952
X-Spam-Level: 
X-Spam-Status: No, score=-1.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, J_CHICKENPOX_110=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
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 Sy9d4Fv53jmn for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 16:11:16 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id BE6401A09D4 for <ietf@ietf.org>; Tue, 29 Apr 2014 16:11:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org;  s=ef5046eb;  h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=j1vVTa/wkLtzMJkWJ7td3geBNlw4jmefCKfGO+Wm62A=;  b=ekFJz399VMbXHrJ9OcLEf8157zjUyv8RtYQ5UvmWFOrfy4yhPfS2avm9HGxUrM5Qq/iKry5iwforiwsuTyYZqmCOWG3Vz/8OftTBfokiFH7Qf4JuVCzw3ZL0qnf6Ros/3VqMpHUfeJKnbYca9cvEPegMwsQNrW0S0LrE0DGu5KI=;
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WfHBC-0006FI-1J; Tue, 29 Apr 2014 23:11:14 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 7BE54580734; Tue, 29 Apr 2014 19:11:13 -0400 (EDT)
Date: Tue, 29 Apr 2014 19:11:13 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: ned+ietf@mauve.mrochek.com
Subject: Re: Google.com hops on the DMARC bandwagon
Message-ID: <20140429231113.GB28966@thunk.org>
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com> <536011BD.3050704@meetinghouse.net> <536012FC.9020803@att.com> <536015F7.2070100@sonnection.nl> <01P780Q4IQVA000054@mauve.mrochek.com> <53602583.4060003@sonnection.nl> <01P782BTLB96000054@mauve.mrochek.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <01P782BTLB96000054@mauve.mrochek.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4jNx0eAwUz2my6i3Tumq8P79ddI
Cc: Ned Freed <ned.freed@mrochek.com>, IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 23:11:18 -0000

On Tue, Apr 29, 2014 at 03:36:34PM -0700, ned+ietf@mauve.mrochek.com wrote:
> >> No, because those postings will bounce, and cause those users to get
> >> unsubscribed from the list.
> 
> >But in this case, we're talking about the p=quarantine policy that
> >Google published for google.com... No bouncing (and hence no automatic
> >unsubscription, unless a receiver interprets p=quarantine as 'please
> >reject').
> 
> Fair point. My observation about the appropriate acronym stands, however.

And some of us have already pointed out internally that this might
cause engineers at Google (including folks like Vint) to not be able
to participate on external mailing lists as effectively, since some
percentage of the mailing list recipients might not receive their
message.

And if that means a Google engineer tries to send a patch to an
upstream open source maintainer via a mailing list, and the maintainer
doesn't see the patch or bug report because it got silently dropped by
their MTA (or put in some spam/junk folder), well, that's Google's
loss, and not necessarily the open source project's problem.

Me, I use a non-google.com e-mail address for my external mailing list
discussions, so it's not going to be a problem for me.  :-)

					- Ted


From nobody Tue Apr 29 16:54:39 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7CE81A0953 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 16:54:38 -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, SPF_PASS=-0.001] autolearn=ham
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 jvfcfaZjbo3f for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 16:54:37 -0700 (PDT)
Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 25D021A0948 for <ietf@ietf.org>; Tue, 29 Apr 2014 16:54:36 -0700 (PDT)
Received: by mail-we0-f172.google.com with SMTP id u57so949641wes.31 for <ietf@ietf.org>; Tue, 29 Apr 2014 16:54:35 -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:content-type; bh=oqUprYaS6orHYSQjFJVoeBe15jLKUmZks2fbBH7Enzs=; b=ZqbJ803517ctQeeinJH3kuJuMTWgu9BcCpvQIOcqtGYRKApnQT3E4IfL4vv997Ry+c 1YqJnfH73n427tmcT2kkgAM+LBVlZ6Mxb9bkbdSo9eeztLGFGmsWv9vZ2NrGf8Fd1fBm ea6634LAeJfFplAsW8Jn59yZ1eu1VMws+iVzGM/Wjfmvzz8I1F83ivJD57lAb8pa4OnB UWVGwH0kT/m4UMpTizRo0aN11+zkdksUXZJqcr5/ZjAk9u1OlJOhsi8tPEyZ0fbCLdMl kOfAHrF1kK+kNCnIPVmCvlzbDimzNFAHcTuMacIAm55Hg5smhgj4V1WbnviB+xV5G6Wm Xcxw==
MIME-Version: 1.0
X-Received: by 10.194.109.227 with SMTP id hv3mr874000wjb.10.1398815675338; Tue, 29 Apr 2014 16:54:35 -0700 (PDT)
Received: by 10.180.210.194 with HTTP; Tue, 29 Apr 2014 16:54:35 -0700 (PDT)
In-Reply-To: <0A46725A-D80C-4F64-BACE-B2C73A04782D@gmail.com>
References: <20140429175606.2856.qmail@joyce.lan> <0A46725A-D80C-4F64-BACE-B2C73A04782D@gmail.com>
Date: Tue, 29 Apr 2014 16:54:35 -0700
Message-ID: <CAL0qLwaNcFHq0bpZaN3FUibo+EK1cRggRqZrtgJbEOKQSG+Evg@mail.gmail.com>
Subject: Re: Will mailing lists survive DMARC?
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Douglas Otis <doug.mtview@gmail.com>
Content-Type: multipart/alternative; boundary=089e0102ee286f5d4f04f837278b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/o7wiE6BJmZWw4CZQtOlTd3bAKLs
Cc: John Levine <johnl@taugh.com>, ietf <ietf@ietf.org>, =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Apr 2014 23:54:39 -0000

--089e0102ee286f5d4f04f837278b
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 29, 2014 at 3:00 PM, Douglas Otis <doug.mtview@gmail.com> wrote:

> There will be an effort made to better generalize the TPA expired draft.
> http://tools.ietf.org/html/rfc6541 (ATPS) was hostile to existing
> mailing-list services and, as such, could not be deployed.  Nor was it more
> suitable for high volume email services.  An effort to change From header
> fields will have users guessing which field indicates who authored the
> message and in the end will provide no benefit.
>

ATPS was deployed as part of an open source package since before it was
published.  It has seen negligible use, and I suspect that's because there
has not to date been any demand for third-party signing mechanisms of any
kind.  In particular, nobody has said anything even a little bit like "I
would use ATPS if only it were changed in the following way(s): ...",
including (and especilaly) the large messaging providers that use that open
source package.

To me, this may lend credence to John Levine's claim that the list signing
the message is as good or better than the author signing the message.

In any case, ATPS, TPA, and its variants all run up against a whitelisting
scaling problem.  I think that's the more interesting thing to discuss.

-MSK

--089e0102ee286f5d4f04f837278b
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Apr 29, 2014 at 3:00 PM, Douglas Otis <span dir=3D=
"ltr">&lt;<a href=3D"mailto:doug.mtview@gmail.com" target=3D"_blank">doug.m=
tview@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div style=3D"word-wrap:break-word">There wi=
ll be an effort made to better generalize the TPA expired draft. =C2=A0=C2=
=A0<a href=3D"http://tools.ietf.org/html/rfc6541" target=3D"_blank">http://=
tools.ietf.org/html/rfc6541</a>=C2=A0(ATPS) was hostile to existing mailing=
-list services and, as such, could not be deployed. =C2=A0Nor was it more s=
uitable for high volume email services. =C2=A0An effort to change From head=
er fields will have users guessing which field indicates who authored the m=
essage and in the end will provide no benefit.</div>
</blockquote><div><br></div><div>ATPS was deployed as part of an open sourc=
e package since before it was published.=C2=A0 It has seen negligible use, =
and I suspect that&#39;s because there has not to date been any demand for =
third-party signing mechanisms of any kind.=C2=A0 In particular, nobody has=
 said anything even a little bit like &quot;I would use ATPS if only it wer=
e changed in the following way(s): ...&quot;, including (and especilaly) th=
e large messaging providers that use that open source package.<br>
<br></div><div>To me, this may lend credence to John Levine&#39;s claim tha=
t the list signing the message is as good or better than the author signing=
 the message.<br><br></div><div>In any case, ATPS, TPA, and its variants al=
l run up against a whitelisting scaling problem.=C2=A0 I think that&#39;s t=
he more interesting thing to discuss.<br>
<br></div><div>-MSK <br></div></div><br></div></div>

--089e0102ee286f5d4f04f837278b--


From nobody Tue Apr 29 17:03:17 2014
Return-Path: <superuser@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD5B21A0948 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 17:03:15 -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, SPF_PASS=-0.001] autolearn=ham
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 JeD5BOTHVJe9 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 17:03:14 -0700 (PDT)
Received: from mail-wi0-x233.google.com (mail-wi0-x233.google.com [IPv6:2a00:1450:400c:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 0C66A1A0290 for <ietf@ietf.org>; Tue, 29 Apr 2014 17:03:13 -0700 (PDT)
Received: by mail-wi0-f179.google.com with SMTP id z2so1328611wiv.0 for <ietf@ietf.org>; Tue, 29 Apr 2014 17:03:12 -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:content-type; bh=UVDpFnmkq//eEs07I76Y5/VRvcseVxMZruKrV0eu2vg=; b=izLzS/V64s7iQY21VKdwh6yl+DifVCDsj1zWui7O7/2d7sfwlYBqMlRHas6ixF9toR txryc5Kp9S4vI62BM5Z9DKdx6IncRnfshFMoD7gImOjeofv7/utxFVlpTc6ybiGMVvgj Xt8vu3Ve3Bl4WjOeMEtbpjLrHnwyCw4XiUXYjGPjsulJJRLqEzZ6ilHY9qRu5VanL6uo 1M+l/uzK2rYilhjKcWcYNTl+YpLqU6DXZdZFDOo443XZwCyEq9o2WcURNpB0RDCdKuJy dh3zhhdMULhwJysfwNsXBBKQWusnFiH5i/GpdyEm5LBy475i3Q92f0TFAgOTuUyWIxzf S0iA==
MIME-Version: 1.0
X-Received: by 10.194.109.227 with SMTP id hv3mr902216wjb.10.1398816192185; Tue, 29 Apr 2014 17:03:12 -0700 (PDT)
Received: by 10.180.210.194 with HTTP; Tue, 29 Apr 2014 17:03:12 -0700 (PDT)
In-Reply-To: <535F88C3.4060002@tana.it>
References: <535F88C3.4060002@tana.it>
Date: Tue, 29 Apr 2014 17:03:12 -0700
Message-ID: <CAL0qLwb4r1nqQqe03FwRiTqmcinLE32y84aiq=eX+EG9Newk6g@mail.gmail.com>
Subject: Re: Will mailing lists survive DMARC?
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Alessandro Vesely <vesely@tana.it>
Content-Type: multipart/alternative; boundary=089e0102ee283dcdb604f837467e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dC6UjGB0pN4fCUMR3uhUznEgemM
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 00:03:15 -0000

--089e0102ee283dcdb604f837467e
Content-Type: text/plain; charset=UTF-8

On Tue, Apr 29, 2014 at 4:10 AM, Alessandro Vesely <vesely@tana.it> wrote:

> The DMARC draft is currently in "AD Followup" state.  A review was
> posted here last week, a process which doesn't seem to affect
> deployment much.
>

The ISE asked me for a revision to correct a couple of IANA things.  That
revision was posted the same day.  My understanding is that it's now just
waiting for its turn ISE's queue.

As I understand it, there's no responsible AD in the ISE stream, except
maybe as an IESG liaison thing.

-MSK

--089e0102ee283dcdb604f837467e
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, Apr 29, 2014 at 4:10 AM, Alessandro Vesely <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:vesely@tana.it" target=3D"_blank">vesely@t=
ana.it</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gm=
ail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">The DMARC draft is currently in &quot;AD Fol=
lowup&quot; state. =C2=A0A review was<br>
posted here last week, a process which doesn&#39;t seem to affect<br>
deployment much.<br></blockquote><div><br></div><div>The ISE asked me for a=
 revision to correct a couple of IANA things.=C2=A0 That revision was poste=
d the same day.=C2=A0 My understanding is that it&#39;s now just waiting fo=
r its turn ISE&#39;s queue.<br>
<br>As I understand it, there&#39;s no responsible AD in the ISE stream, ex=
cept maybe as an IESG liaison thing.<br><br></div><div>-MSK<br><br></div></=
div></div></div>

--089e0102ee283dcdb604f837467e--


From nobody Tue Apr 29 18:11:33 2014
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E80471A099F for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 18:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.357
X-Spam-Level: 
X-Spam-Status: No, score=-0.357 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, SPF_NEUTRAL=0.779] autolearn=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 CqJmeDLtw9Ch for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 18:11:26 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id C13771A0909 for <ietf@ietf.org>; Tue, 29 Apr 2014 18:11:25 -0700 (PDT)
Received: (qmail 28199 invoked from network); 30 Apr 2014 01:11:23 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=6e26.53604dbb.k1404; bh=5SlKGePi30OJfcXJHlZwLB/uxJJgvmqIIPM/Jn3zKoI=; b=ODV1/g+A16fr94S5RNU40Pqg5IRZv6asy41th5a+NP2N7IlSbxVa5UeKNiikSVPyxgUpbVWMfzdLEomx0meM/lhEXv029gLigjMFm6mTzLcrwegmm7WUW+h/PxV1N/0cWG0GPIz33A3RkuB2HkKq4Vw4d0061wtfR1GOba7h9CLPAzVZr36IKRIMa1YoZ/hdOBC7F9BXu0B2T7y3cvUzaHbCBp9Jp1L1JbggO0C5y9jHwMXKydOcBMdAxic9cOU6
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent:cleverness; s=6e26.53604dbb.k1404; bh=5SlKGePi30OJfcXJHlZwLB/uxJJgvmqIIPM/Jn3zKoI=; b=fuOjloTPIACQHjzSiEcoogO/XnY6h+03gkRHFqn8angwfxpgIXkhZR2ATpK6QeWahvx0Csel7pZfqggHDfzy64us0rUWUqFpX0eN8RAPZuwCbRG+GAY9ldUCQh2xP1tMyxqiAipONokfkrp/BjLKZzVTOwxl2yVbBuPlEAq4DM0UtkiVsqg6wWpfPOQKFKgmoXxe2a0wzF75Nf7/CqStzyi3spkNO4agTrLu2PE5E6fP7cB7cY3EqSyr3AT33bVm
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 30 Apr 2014 01:11:22 -0000
Date: 29 Apr 2014 21:11:22 -0400
Message-ID: <alpine.BSF.2.00.1404292103520.2126@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Subject: Re: Will mailing lists survive DMARC?
In-Reply-To: <CAL0qLwaNcFHq0bpZaN3FUibo+EK1cRggRqZrtgJbEOKQSG+Evg@mail.gmail.com>
References: <20140429175606.2856.qmail@joyce.lan> <0A46725A-D80C-4F64-BACE-B2C73A04782D@gmail.com> <CAL0qLwaNcFHq0bpZaN3FUibo+EK1cRggRqZrtgJbEOKQSG+Evg@mail.gmail.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
Cleverness: None detected
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eTNHSRr8M0nKrqIR3nbtkk-Oew0
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 01:11:27 -0000

> In any case, ATPS, TPA, and its variants all run up against a whitelisting
> scaling problem.  I think that's the more interesting thing to discuss.

I completely agree.  Dunno if that belongs in ietf-822 or ietf-smtp.

It seems to me that the way you scale is to limit the number of 
whitelists, and leverage the information that large players already have, 
e.g., the 30,000 mail hosts that Yahoo said they knew they broke.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.


From nobody Tue Apr 29 18:31:02 2014
Return-Path: <doug.mtview@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EDB61A09C2 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 18:30:56 -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, SPF_PASS=-0.001] autolearn=ham
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 0JX-MapDHgNc for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 18:30:53 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) by ietfa.amsl.com (Postfix) with ESMTP id 87FAF1A09C3 for <ietf@ietf.org>; Tue, 29 Apr 2014 18:30:53 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id y13so974594pdi.0 for <ietf@ietf.org>; Tue, 29 Apr 2014 18:30:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=krRXzcjGRu66rqR/2nqJS8xdfgkF5hTs57ofzrOz7Pw=; b=K25KPpSPeVjDjFvXEEJWMyNhxmOTC4zP5uUs68B4KCwoQLlbJEUFdFgKPefSNsWSfh rqVKysA4PbCyB8gop8qOpLaUrFmWjWSrtQBhEOEOfk+sIH9RA2fSu3AeUn/1Zwc0BYF4 078KGNlUv4i2afpAvf3qJWAxkR9iYLA32huN2tn9iIB60W3H9m15Yrx5fR+Cd6KJz1bt q98pe5DSI92PWT7ami41Ejey8UevKJwGGWE0wxOrlGVkzQhMdcA6ZufTTGfzJO9t2+UZ rZXt41ahhpkKeLrsE89bLAha9A4uyHoU1MhFJyY3HBERk2YsDBaIQbiR6DU9bT0X4faG XekA==
X-Received: by 10.66.140.104 with SMTP id rf8mr2375708pab.107.1398821452267; Tue, 29 Apr 2014 18:30:52 -0700 (PDT)
Received: from [192.168.0.54] (107-0-5-6-ip-static.hfc.comcastbusiness.net. [107.0.5.6]) by mx.google.com with ESMTPSA id lr3sm122769519pab.4.2014.04.29.18.30.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 29 Apr 2014 18:30:51 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_0BC75631-D52A-4D5A-86DE-1C9F98C9EEFB"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Will mailing lists survive DMARC?
From: Douglas Otis <doug.mtview@gmail.com>
In-Reply-To: <CAL0qLwaNcFHq0bpZaN3FUibo+EK1cRggRqZrtgJbEOKQSG+Evg@mail.gmail.com>
Date: Tue, 29 Apr 2014 18:30:54 -0700
Message-Id: <400EB7EB-EE07-4526-8E76-904AF561CA00@gmail.com>
References: <20140429175606.2856.qmail@joyce.lan> <0A46725A-D80C-4F64-BACE-B2C73A04782D@gmail.com> <CAL0qLwaNcFHq0bpZaN3FUibo+EK1cRggRqZrtgJbEOKQSG+Evg@mail.gmail.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hn2PvEV6hmbZU1LwFPJO9S9ALbw
Cc: John Levine <johnl@taugh.com>, ietf <ietf@ietf.org>, =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 01:30:56 -0000

--Apple-Mail=_0BC75631-D52A-4D5A-86DE-1C9F98C9EEFB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Apr 29, 2014, at 4:54 PM, Murray S. Kucherawy <superuser@gmail.com> =
wrote:

> On Tue, Apr 29, 2014 at 3:00 PM, Douglas Otis <doug.mtview@gmail.com> =
wrote:
> There will be an effort made to better generalize the TPA expired =
draft.   http://tools.ietf.org/html/rfc6541 (ATPS) was hostile to =
existing mailing-list services and, as such, could not be deployed.  Nor =
was it more suitable for high volume email services.  An effort to =
change =46rom header fields will have users guessing which field =
indicates who authored the message and in the end will provide no =
benefit.
>=20
> ATPS was deployed as part of an open source package since before it =
was published.  It has seen negligible use, and I suspect that's because =
there has not to date been any demand for third-party signing mechanisms =
of any kind.  In particular, nobody has said anything even a little bit =
like "I would use ATPS if only it were changed in the following way(s): =
...", including (and especilaly) the large messaging providers that use =
that open source package.
>=20
> To me, this may lend credence to John Levine's claim that the list =
signing the message is as good or better than the author signing the =
message.
>=20
> In any case, ATPS, TPA, and its variants all run up against a =
whitelisting scaling problem.  I think that's the more interesting thing =
to discuss.

Dear Murray,

Two significant changes from TPA occurred during the development of ATPS =
that made its use impossible.=20

1) Unique DKIM signatures became necessary to enable third-party =
services.  (IESG requirement as I understand.)
 =20
This special signature requirement expects all services to change before =
ATPS becomes usable. (Impossible impediment deliberately imposed.)

2) Optional labeling scheme requiring domain unique references. =
(Requiring a reference to determine label encoding???)
 =20
Variable labeling makes scaling or exchanging data time consuming and =
difficult.

TPA offered a functional scheme without any third-party services first =
changing.  These third-party services could sign using DKIM, authorize =
outbound MTA using SPF, depend on EHLO validation, or whatever =
validation condoned by the Author Domain.   TPA even add a required =
List-ID alignment to further constrain authorizations for mailing-lists =
or specific Senders to selectively enable other types of third-party =
services.  TPA did not even require DKIM (nor does DMARC for that =
matter).

I agree with you and John about list management, but those seeking to =
defend their Author domain must be able to decide which exceptions are =
permitted as a means to foreclose on abuse. =20

TPA scales better than restful JSON or other technologies or protocols =
currently available.  The author domain would publish concise static =
information that only changes in response to reports of abuse.  This =
approach was used to report on thousands of MTAs for very large ESPs =
where their recipients added a unique label to the query since this was =
to establish a paid service to fund largely legal expenses.  Once a too =
big to ignore domain using DMARC, ADSP, or yet to be determined =
restrictive policy implements TPA (which uses consistent labeling), =
other domains being similarly managed could share the same _tpa =
subdomain.  The scaling issue that you describe would involve mostly =
static resources based on feedback monitoring to allow exceptions after =
confirming management of third-party services.=20

TPA does not shift the senders problems on to recipients as DMARC does =
when applied against user accounts. TPA does not demand third-party =
services make changes in their process as did ATPS.=20

Stop being concerned about scale.  Much much more than 30,000 =
third-party services can be trivially supported using the TPA single =
query scheme.      =20

Regards,
Douglas Otis




=20



--Apple-Mail=_0BC75631-D52A-4D5A-86DE-1C9F98C9EEFB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;"><br><div><div>On Apr 29, 2014, at 4:54 PM, Murray S. =
Kucherawy &lt;<a =
href=3D"mailto:superuser@gmail.com">superuser@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr">On Tue, Apr 29, 2014 at 3:00 PM, Douglas =
Otis <span dir=3D"ltr">&lt;<a href=3D"mailto:doug.mtview@gmail.com" =
target=3D"_blank">doug.mtview@gmail.com</a>&gt;</span> wrote:<br><div =
class=3D"gmail_extra"><div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
style=3D"word-wrap:break-word">There will be an effort made to better =
generalize the TPA expired draft. &nbsp;&nbsp;<a =
href=3D"http://tools.ietf.org/html/rfc6541" =
target=3D"_blank">http://tools.ietf.org/html/rfc6541</a>&nbsp;(ATPS) was =
hostile to existing mailing-list services and, as such, could not be =
deployed. &nbsp;Nor was it more suitable for high volume email services. =
&nbsp;An effort to change =46rom header fields will have users guessing =
which field indicates who authored the message and in the end will =
provide no benefit.</div>
</blockquote><div><br></div><div>ATPS was deployed as part of an open =
source package since before it was published.&nbsp; It has seen =
negligible use, and I suspect that's because there has not to date been =
any demand for third-party signing mechanisms of any kind.&nbsp; In =
particular, nobody has said anything even a little bit like "I would use =
ATPS if only it were changed in the following way(s): ...", including =
(and especilaly) the large messaging providers that use that open source =
package.<br>
<br></div><div>To me, this may lend credence to John Levine's claim that =
the list signing the message is as good or better than the author =
signing the message.<br><br></div><div>In any case, ATPS, TPA, and its =
variants all run up against a whitelisting scaling problem.&nbsp; I =
think that's the more interesting thing to =
discuss.<br></div></div></div></div></blockquote></div><br><div>Dear =
Murray,</div><div><br></div><div>Two significant changes from TPA =
occurred during the development of ATPS that made its use =
impossible.&nbsp;</div><div><br></div><div>1) Unique DKIM signatures =
became necessary to enable third-party services. &nbsp;(IESG requirement =
as I understand.)</div><div>&nbsp;&nbsp;</div><div>This special =
signature requirement expects all services to change before ATPS becomes =
usable. (Impossible impediment deliberately =
imposed.)</div><div><br></div><div>2) Optional labeling scheme requiring =
domain unique references. (Requiring a reference to determine label =
encoding???)</div><div>&nbsp;&nbsp;</div><div>Variable labeling makes =
scaling or exchanging data time consuming and =
difficult.</div><div><br></div><div>TPA offered a functional scheme =
without any third-party services first changing. &nbsp;These third-party =
services could sign using DKIM, authorize outbound MTA using SPF, depend =
on EHLO validation, or whatever validation condoned by the Author =
Domain. &nbsp; TPA even add a required List-ID alignment to further =
constrain authorizations for mailing-lists or specific Senders to =
selectively enable other types of third-party services. &nbsp;TPA did =
not even require DKIM (nor does DMARC for that =
matter).</div><div><br></div><div>I agree with you and John about list =
management, but those seeking to defend their Author domain must be able =
to decide which exceptions are permitted as a means to foreclose on =
abuse. &nbsp;</div><div><br></div><div>TPA scales better than restful =
JSON or other technologies or protocols currently available. &nbsp;The =
author domain would publish concise static information that only changes =
in response to reports of abuse. &nbsp;This approach was used to report =
on thousands of MTAs for very large ESPs where their recipients added a =
unique label to the query since this was to establish a paid service to =
fund largely legal expenses. &nbsp;Once a too big to ignore domain using =
DMARC, ADSP, or yet to be determined restrictive policy implements TPA =
(which uses consistent labeling), other domains being similarly managed =
could share the same _tpa subdomain. &nbsp;The scaling issue that you =
describe would involve mostly static resources based on feedback =
monitoring to allow exceptions after confirming management of =
third-party services.&nbsp;</div><div><br></div><div>TPA does not shift =
the senders problems on to recipients as DMARC does when applied against =
user accounts. TPA does not demand third-party services make changes in =
their process as did ATPS.&nbsp;</div><div><br></div><div>Stop being =
concerned about scale. &nbsp;Much much more than 30,000 third-party =
services can be trivially supported using the TPA single query scheme. =
&nbsp; &nbsp; =
&nbsp;&nbsp;</div><div><br></div><div>Regards,</div><div>Douglas =
Otis</div><div><br></div><div><br></div><div><br></div><div><br></div><div=
>&nbsp;</div><div><br></div><div><br></div></body></html>=

--Apple-Mail=_0BC75631-D52A-4D5A-86DE-1C9F98C9EEFB--


From nobody Tue Apr 29 18:37:43 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 754921A09CC for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 18:37:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.079
X-Spam-Level: 
X-Spam-Status: No, score=-101.079 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_NET=0.611, HOST_MISMATCH_COM=0.311, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 pJpnhqD7Lz8c for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 18:37:36 -0700 (PDT)
Received: from ftp.catinthebox.net (mail.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 30C1F1A09BB for <ietf@ietf.org>; Tue, 29 Apr 2014 18:37:35 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2168; t=1398821849; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=CaoWSgTfX2BbHyUu8k3Zq971EA0=; b=Zp0wQadJrISlnhvD+l9x lZoA6nX/nxFi+O3jGoe9sE5mxcT4Hi1Wy3vqrx6KM9OsHT6etO/ct5qWQdzmZfdM mmizGnC6zGAh//JwNNkuxLlbz3vUPNhwntl0+Rm+iqb0dYfXDi6SmdQ0r4Wn2ob5 pYIUQtY34sRwpSCu6S8K88Q=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 29 Apr 2014 21:37:29 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1930411705.9688.3432; Tue, 29 Apr 2014 21:37:28 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2168; t=1398821757; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=JuEAAqg +/1tOgDJCN/P5GzHTgrMqB3PRByk7wn9Im7Y=; b=e3e7OPQpaYmNwc7tDUGdKXw VgNv1TyY95XFSfHwj69GvnKfKHogfskn20gs81b7/mcGySNHjxmHL+9tsnweWZMv dlOsFmBWMPi+U6xY/tpBSz5tExngRzyzPOeOv102CUczRo5io48j8J1vy5+pKxWn 6fzcL6od91HI3mujEc7o=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Tue, 29 Apr 2014 21:35:57 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1949932609.9.13272; Tue, 29 Apr 2014 21:35:55 -0400
Message-ID: <536053D7.1010507@isdg.net>
Date: Tue, 29 Apr 2014 21:37:27 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf <ietf@ietf.org>
Subject: Re: Will mailing lists survive DMARC?
References: <20140429175606.2856.qmail@joyce.lan> <0A46725A-D80C-4F64-BACE-B2C73A04782D@gmail.com> <CAL0qLwaNcFHq0bpZaN3FUibo+EK1cRggRqZrtgJbEOKQSG+Evg@mail.gmail.com>
In-Reply-To: <CAL0qLwaNcFHq0bpZaN3FUibo+EK1cRggRqZrtgJbEOKQSG+Evg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5nbvmcjpn8IagvK_bVurPUWT81c
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 01:37:38 -0000

On 4/29/2014 7:54 PM, Murray S. Kucherawy wrote:
> On Tue, Apr 29, 2014 at 3:00 PM, Douglas Otis <doug.mtview@gmail.com
> <mailto:doug.mtview@gmail.com>> wrote:
>
>     There will be an effort made to better generalize the TPA expired
>     draft. http://tools.ietf.org/html/rfc6541 (ATPS) was hostile to
>     existing mailing-list services and, as such, could not be
>     deployed.  Nor was it more suitable for high volume email
>     services.  An effort to change From header fields will have users
>     guessing which field indicates who authored the message and in the
>     end will provide no benefit.
>
>
> ATPS was deployed as part of an open source package since before it
> was published.  It has seen negligible use, and I suspect that's
> because there has not to date been any demand for third-party signing
> mechanisms of any kind.

Disagree, because you went at it half-hearted. You made it 
experimental and your abstract even stated that it probably means 
nothing. More importantly, Levine and Crocker didn't support the 
effort, so it didn't have a chance at all.

Its call marketing just as it was done with DMARC which is less 
flexible than any other policy system.  If you don't champion it, it 
goes nowhere.

> In any case, ATPS, TPA, and its variants all run up against a
> whitelisting scaling problem.  I think that's the more interesting
> thing to discuss.

It was already discussed. Unless you are sharing this "Whitelist" in 
some centralized fashion, it won't be a persistent and consistent 
protocol solution.  What it will promote is targeted abuse at those 
sites that do not have the same whitelist -- You ware making it so 
that "Batteries Required" in order to function.

We been thru this already.  We need a standard consistent and 
persistent domain based solution all can apply equally and one that 
you don't need to buy "Batteries" to get any payoff.  Even with all 
the "small use cases" belief that is being proven wrong about policy, 
you guys are still in denial about policy.   Everyone is telling you 
guys you got it all wrong, and you still won't listen. This thing will 
never be solved with a status quo.

-- 
HLS



From nobody Tue Apr 29 19:32:52 2014
Return-Path: <johnl@iecc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25C8D1A09EE for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 19:32:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.843
X-Spam-Level: 
X-Spam-Status: No, score=0.843 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, SPF_NEUTRAL=0.779] autolearn=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 X8wi-8YqwQ6S for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 19:32:50 -0700 (PDT)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) by ietfa.amsl.com (Postfix) with ESMTP id 043D51A09E9 for <ietf@ietf.org>; Tue, 29 Apr 2014 19:32:49 -0700 (PDT)
Received: (qmail 37109 invoked from network); 30 Apr 2014 02:32:47 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 30 Apr 2014 02:32:47 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ae1.536060ce.k1404; i=johnl@user.iecc.com; bh=xitoS/L2uPuCt4op008IZvLw71/9S+Nh1+Ez9cWio9Y=; b=XoDXpkTN5uT3hW2SxoKkSiLA+sa3TBkB5Ch3ztwWPsuxfVF+sJ4J4WjHRwFKA/+A3Pzvu79JGrxLvCzi6W5T7XcJ4ATUarfhKgZ9bu1MhM18Q3Qbn0wQ16msq7nlDBioOkW5sZjWdL3j1itBNTYv+LdXnUjy7uvmfl3ScLOW2SAKAADq2eYbFNSmDXUWP2jYub3TUEL9F2qvQWrpfToGS168uPhZQAuaGC/ml9etf4hSbi78SeTqbKVmt5zXwtaP
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=ae1.536060ce.k1404; olt=johnl@user.iecc.com; bh=xitoS/L2uPuCt4op008IZvLw71/9S+Nh1+Ez9cWio9Y=; b=pGzfp5D9aIfO2EKt0lAN90csfLSZp381Li0gBVLM5C9XYuMHC7CVrumAjHYznzItMzw9uJNop3WbbaORdz73+dd/6xUuqJj9zX+olE+yefBGor6DjDiy1MNXNgK9ubOqnjw7LBpLE8lEHYvhQj85yAapVFVJ2dGX31DAEYi95Y1h2a4lfouWHk6Sw6iAkPS8KVwioi6LLatT8iAIg4rEEyoNHWkOwHSzcEh/FpFdr4wcEhc560NeYnGIKbSVba3/
Date: 30 Apr 2014 02:32:24 -0000
Message-ID: <20140430023224.2784.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Google.com hops on the DMARC bandwagon
In-Reply-To: <01P782BTLB96000054@mauve.mrochek.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/httatFWhVDmGvssn31uqWR1y7zU
Cc: ned+ietf@mauve.mrochek.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 02:32:51 -0000

>> But in this case, we're talking about the p=quarantine policy that
>> Google published for google.com... No bouncing (and hence no automatic
>> unsubscription, unless a receiver interprets p=quarantine as 'please
>> reject').
>
>Fair point. My observation about the appropriate acronym stands, however.

Actually, mail with google.com From: addresses is bouncing.  I see
bounces from mxlogic among others.  No, I don't know why they're
treating p=quarantine as though it were p=reject, but they are.

The acronym is more appropriate than ever.

R's,
John


From nobody Tue Apr 29 23:20:34 2014
Return-Path: <cdel@firsthand.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD1021A6EE2 for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 23:20:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.39
X-Spam-Level: 
X-Spam-Status: No, score=-0.39 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, HELO_MISMATCH_UK=1.749, HOST_MISMATCH_NET=0.311, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.651] autolearn=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 PSOinQ9JQEph for <ietf@ietfa.amsl.com>; Tue, 29 Apr 2014 23:20:23 -0700 (PDT)
Received: from bmtwo.vm.bytemark.co.uk (mail.firsthand.net [IPv6:2001:41c8:1:6062::d46e:bc35]) by ietfa.amsl.com (Postfix) with ESMTP id 3CE521A6EE0 for <ietf@ietf.org>; Tue, 29 Apr 2014 23:20:22 -0700 (PDT)
X-No-Relay: not in my network
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=firsthand.net;  b=g52WH/PLhPJNL4+aTY4GsbKDur1U/pNg2QAaUM9KLPlxoMmi0lwWyo2xE0piCSb1f2aaWFH0cHadOYD0s+hgXB3Vu2sOnuIRLARerPGMADuCsLklcuLTKxzHwQ7+AIsr; h=X-No-Relay:X-No-Relay:X-No-Relay:Received:Message-ID:Date:From:Reply-To:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:X-Enigmail-Version:Content-Type;
X-No-Relay: not in my network
X-No-Relay: not in my network
X-No-Relay: not in my network
Received: from orionlocal.local (host-2-100-187-232.as13285.net [2.100.187.232]) by bmtwo.vm.bytemark.co.uk (Postfix) with ESMTPSA id 88ADFE0102; Wed, 30 Apr 2014 06:20:18 +0100 (BST)
Message-ID: <53609621.8070704@firsthand.net>
Date: Wed, 30 Apr 2014 07:20:17 +0100
From: Christian de Larrinaga <cdel@firsthand.net>
User-Agent: Postbox 3.0.9 (Macintosh/20140129)
MIME-Version: 1.0
To: "Andrew G. Malis" <agmalis@gmail.com>
Subject: Re: Enough DMARC whinging
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com>
In-Reply-To: <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="------------enig568D2BD1FA2F5271647BE28B"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6W6-qoDsZHRnynq-XZhkAOhJQJ4
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: cdel@firsthand.net
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 06:20:28 -0000

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig568D2BD1FA2F5271647BE28B
Content-Type: multipart/alternative;
 boundary="------------050102060202000700070204"

This is a multi-part message in MIME format.
--------------050102060202000700070204
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

IETF could recommend people using Yahoo or AOL wanting to be read should
resubscribe to IETF lists from another domain?

Andrew G. Malis wrote:
> Philip,
>
> Here are the effects that I see. I use this gmail account for my IETF
> mailing lists. I am now consistently seeing email sent from Yahoo
> users end up in my spam folder with the following embedded warning
> message:
>
> *Be careful with this message.* Our systems couldn't verify that this
> message was really sent by yahoo.com <http://yahoo.com>. You might
> want to avoid clicking links or replying with personal
> information.  Learn more
> <http://support.google.com/mail/bin/answer.py?hl=3Den&answer=3D1366858&=
ctx=3Dmail&authuser=3D1&expand=3D2>
>
> The sender, of course, is completely unaware of what is happening on
> the receiver's end, so they have no reason to want to change from
> Yahoo to another domain for posting.
>
> So this is imposing pain on the receiver, since I now have to
> consistently check my spam folder for valid IETF email.
>
> I see that you also use gmail, so you should start checking your spam
> folder as well.
>
> Cheers,
> Andy
>
>
> On Tue, Apr 29, 2014 at 3:54 PM, Phillip Hallam-Baker
> <hallam@gmail.com <mailto:hallam@gmail.com>> wrote:
>
>     I am finding it rather hard to follow the DMARC discussion. Some fo=
lk
>     have managed to convince me that they are upset but working out why=

>     would require rather a lot of spec crunching.
>
>     My best theory so far is that DMARC is some sort of email policy
>     statement and that either (1) some companies are now publishing a
>     policy that states 'reject all mail that purports to come from this=

>     address that does not have authentication Y' or (2) some companies =
are
>     now rejecting mail not in compliance with said policy or (3) both.
>
>     There is a simple truth about DNS names: Whoever owns them makes th=
e
>     rules for their use [1]. If you don't like the rules for
>     google.com <http://google.com>
>     then choose another domain to post from.
>
>
>     If people want email to work with mailing lists, then don't complai=
n
>     about reasonable choices people want to make. Work out a way to fix=

>     mailing lists so that they work properly.
>
>     There is no reason we can't change the way From works. Or add new
>     from headers.
>
>     Are we engineers or curators of the past?
>
>
>     [1] Thus be rather suspicious of folk who claim that we merely rent=

>     the use on terms of their choosing.
>
>     --
>     Website: http://hallambaker.com/
>
>

--=20
Christian de Larrinaga
FBCS, CITP, MCMA
-------------------------
@ FirstHand
-------------------------
+44 7989 386778
cdel@firsthand.net
-------------------------

--------------050102060202000700070204
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<html><head>
<meta content=3D"text/html; charset=3DUTF-8" http-equiv=3D"Content-Type">=

</head><body style=3D"font-family: Optima; font-size: 12pt;"=20
bgcolor=3D"#FFFFFF" text=3D"#000000"><div style=3D"font-size:=20
12pt;font-family: Optima;"><span style=3D"font-family: Optima;">IETF coul=
d
 recommend people using Yahoo or AOL wanting to be read should=20
resubscribe to IETF lists from another domain?</span><br><br>Andrew G.=20
Malis wrote:<blockquote=20
cite=3D"mid:CAA=3DduU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gm=
ail.com"
 type=3D"cite"><div dir=3D"ltr">Philip,<div><br></div><div>Here are the=20
effects that I see. I use this gmail account for my IETF mailing lists. I=

 am now consistently seeing email sent from Yahoo users end up in my=20
spam folder with the following embedded warning message:</div>

<div><br></div><div><b=20
style=3D"color:rgb(85,85,85);font-family:arial,sans-serif;font-size:13px;=
line-height:21px;background-color:rgb(255,241,168)">Be
 careful with this message.</b><span=20
style=3D"color:rgb(85,85,85);font-family:arial,sans-serif;font-size:13px;=
line-height:21px;background-color:rgb(255,241,168)">=C2=A0Our
 systems couldn't verify that this message was really sent by <a=20
moz-do-not-send=3D"true" href=3D"http://yahoo.com">yahoo.com</a>. You mig=
ht=20
want to avoid clicking links or replying with personal information.=C2=A0=
=C2=A0</span><a
 moz-do-not-send=3D"true" class=3D"acT" target=3D"_blank"=20
href=3D"http://support.google.com/mail/bin/answer.py?hl=3Den&amp;answer=3D=
1366858&amp;ctx=3Dmail&amp;authuser=3D1&amp;expand=3D2"
=20
style=3D"font-family:arial,sans-serif;font-size:13px;line-height:21px;bac=
kground-color:rgb(255,241,168)">Learn
 more</a><br>

</div><div><br></div><div>The sender, of course, is completely unaware=20
of what is happening on the receiver's end, so they have no reason to=20
want to change from Yahoo to another domain for posting.</div><div><br></=
div>

<div>So this is imposing pain on the receiver, since I now have to=20
consistently check my spam folder for valid IETF email.</div><div><br></d=
iv><div>I
 see that you also use gmail, so you should start checking your spam=20
folder as well.</div>

<div><br></div><div>Cheers,</div><div>Andy</div></div><div=20
class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Tue, Apr 29, =

2014 at 3:54 PM, Phillip Hallam-Baker <span dir=3D"ltr">&lt;<a=20
moz-do-not-send=3D"true" href=3D"mailto:hallam@gmail.com" target=3D"_blan=
k">hallam@gmail.com</a>&gt;</span>
 wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px
 #ccc solid;padding-left:1ex">I am finding it rather hard to follow the=20
DMARC discussion. Some folk<br>
have managed to convince me that they are upset but working out why<br>
would require rather a lot of spec crunching.<br>
<br>
My best theory so far is that DMARC is some sort of email policy<br>
statement and that either (1) some companies are now publishing a<br>
policy that states 'reject all mail that purports to come from this<br>
address that does not have authentication Y' or (2) some companies are<br=
>
now rejecting mail not in compliance with said policy or (3) both.<br>
<br>
There is a simple truth about DNS names: Whoever owns them makes the<br>
rules for their use [1]. If you don't like the rules for <a=20
moz-do-not-send=3D"true" href=3D"http://google.com" target=3D"_blank">goo=
gle.com</a><br>
then choose another domain to post from.<br>
<br>
<br>
If people want email to work with mailing lists, then don't complain<br>
about reasonable choices people want to make. Work out a way to fix<br>
mailing lists so that they work properly.<br>
<br>
There is no reason we can't change the way From works. Or add new from=20
headers.<br>
<br>
Are we engineers or curators of the past?<br>
<br>
<br>
[1] Thus be rather suspicious of folk who claim that we merely rent<br>
the use on terms of their choosing.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--<br>
Website: <a moz-do-not-send=3D"true" href=3D"http://hallambaker.com/"=20
target=3D"_blank">http://hallambaker.com/</a><br>
<br>
</font></span></blockquote></div><br></div></blockquote><br><div=20
class=3D"moz-signature">-- <br>Christian de Larrinaga <br>
FBCS, CITP, MCMA <br>
-------------------------<br>
 <span style=3D"font-weight: bold;">@ FirstHand</span><br=20
style=3D"font-weight: bold;">
-------------------------<br>
+44 7989 386778<br>
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:cdel@firsthand.net">=
cdel@firsthand.net</a> <br>
-------------------------<br>
</div></div></body></html>

--------------050102060202000700070204--

--------------enig568D2BD1FA2F5271647BE28B
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBCgAGBQJTYJYiAAoJEO8NEF3l27YrhPAIAKFokB2vwlCg1aAR6Eefhrux
Ix6vSxbiH2CkivldhmopSPA9QG/mNrrTJaF6iz7VrPHSSNCyLXxxMaHY+CRIudpx
3CQdeClGwUZoPauxFjzUoMuOqXoJq6dwCnmNIsMJv7hhobPczbxheP6esSXTH1jO
rFMT8nh7LpOr/g4ePn+1vGcov7gcfUzsjblyBBRoQ7B1XdBsSbE8vf3E/S7wOJ+q
41QUifpiVsGBR8lM1vg0+5udyoKV4gH7pCXQWp7SKfWA0SW5OUzPI/Jr+s3ZQgCj
6rYKObAxgUY+90o91qlE4riUVfNbE5l91JrGsMXNkwHkGHaYtNwuQkldJw7dx/4=
=mzZv
-----END PGP SIGNATURE-----

--------------enig568D2BD1FA2F5271647BE28B--


From nobody Wed Apr 30 01:45:33 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E440C1A0317 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 01:45:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.441
X-Spam-Level: 
X-Spam-Status: No, score=-2.441 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.651, T_DKIM_INVALID=0.01] autolearn=ham
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 iZpOurAB-pEV for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 01:45:27 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD771A0764 for <ietf@ietf.org>; Wed, 30 Apr 2014 01:45:27 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.232.234]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3U8j6TD009844 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Apr 2014 01:45:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398847519; bh=imI9K/VBF7KJX1cWHt86qBstkW8U+U9FENcFveLyKT8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Ct3KtHymstMCLvo4eTaaPkHFyaD1zE/i0dofjsrQ3HAfFlewPOTwk0jFzvkvMfWd9 tmjbjsCWWNN1j4nqkvH7RIQChuB7YuWDFFKzx+LMQeq6rxAi1otv/cHIQG+dC2/bmU Zy2CtYhEtluJ+J6Dnagj0mSKUwLnGXpx8baCZ+44=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398847519; i=@elandsys.com; bh=imI9K/VBF7KJX1cWHt86qBstkW8U+U9FENcFveLyKT8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=y23Kp2Q4QfzuWreq6VCyY3OKKyWDU+rHHLUk3n4810prTKn6GFPF37s+JiRqbiklJ hGZQKa96VZAr8Nr6bnOvdyFxiJdLTHyzkBFVWCip8GuLzt0GucdyZHzvdpGNjttzpU NlRW4AzuUBRiN30zC8NnoADmmna1vFjMjSI68qiQ=
Message-Id: <6.2.5.6.2.20140430005644.0afcefe8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Apr 2014 01:32:50 -0700
To: Jari Arkko <jari.arkko@piuha.net>, Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
In-Reply-To: <E8D78AA7-1BDB-4A35-8773-2513880EFB4C@piuha.net>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net> <A5CE78BA-5805-4922-9E1A-A30D3B5AA4CA@piuha.net> <6.2.5.6.2.20140410034359.0bc89d30@elandnews.com> <E8D78AA7-1BDB-4A35-8773-2513880EFB4C@piuha.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1y2U4msce7ujjDhb8N9aMGyV5PU
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 08:45:29 -0000

Hi Jari, Stephen,
At 11:08 10-04-2014, Jari Arkko wrote:
> > I suggested to Stephen to start the Last Call as it would take a 
> month.  That does not prevent the gathering of input from folks who do crypto.
>
>FWIW, I would be fine with this.

I am following up on this as the CFRG meeting has held 
yesterday.  There was a message (msg-id: 
m3tx9ehlf4.fsf@carbon.jhcloos.org) to the ietf-ssh mailing list about 
getting an early assignment for using ED25519 in SSHFP.

Would it be possible to start the Last Call for 
draft-moonesamy-sshfp-ed25519-01 [1]?

I'll disclose that I made this request as there is already code in an 
open source software (OpenSSH).  I have not derived any financial 
benefit in doing this work.

Thanks,
S. Moonesamy

1. http://tools.ietf.org/html/draft-moonesamy-sshfp-ed25519-01   


From nobody Wed Apr 30 01:54:20 2014
Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFE91A6F27 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 01:54:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 ahGfJY01G09r for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 01:54:10 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id CEE8E1A6F33 for <ietf@ietf.org>; Wed, 30 Apr 2014 01:54:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 8917FBE68; Wed, 30 Apr 2014 09:54:07 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K41IxCnCpH0P; Wed, 30 Apr 2014 09:54:07 +0100 (IST)
Received: from [134.226.36.180] (stephen-think.dsg.cs.tcd.ie [134.226.36.180]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 688A1BE63; Wed, 30 Apr 2014 09:54:07 +0100 (IST)
Message-ID: <5360BA2F.6050402@cs.tcd.ie>
Date: Wed, 30 Apr 2014 09:54:07 +0100
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net> <A5CE78BA-5805-4922-9E1A-A30D3B5AA4CA@piuha.net> <6.2.5.6.2.20140410034359.0bc89d30@elandnews.com> <E8D78AA7-1BDB-4A35-8773-2513880EFB4C@piuha.net> <6.2.5.6.2.20140430005644.0afcefe8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20140430005644.0afcefe8@elandnews.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7Y9cUE45F10eVdddjSiX-goagoo
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 08:54:15 -0000

Hiya,

On 30/04/14 09:32, S Moonesamy wrote:
> Hi Jari, Stephen, At 11:08 10-04-2014, Jari Arkko wrote:
>>> I suggested to Stephen to start the Last Call as it would take a
>> month.  That does not prevent the gathering of input from folks who
>> do crypto.
>> 
>> FWIW, I would be fine with this.
> 
> I am following up on this as the CFRG meeting has held yesterday.
> There was a message (msg-id: m3tx9ehlf4.fsf@carbon.jhcloos.org) to
> the ietf-ssh mailing list about getting an early assignment for
> using ED25519 in SSHFP.
> 
> Would it be possible to start the Last Call for 
> draft-moonesamy-sshfp-ed25519-01 [1]?

Yes. The CFRG meeting didn't raise any objection to this,
so I'll move it along now. (Well, tomorrow.)

Cheers,
S.

> 
> I'll disclose that I made this request as there is already code in
> an open source software (OpenSSH).  I have not derived any financial 
> benefit in doing this work.
> 
> Thanks, S. Moonesamy
> 
> 1. http://tools.ietf.org/html/draft-moonesamy-sshfp-ed25519-01
> 
> 


From nobody Wed Apr 30 02:23:37 2014
Return-Path: <sm@elandsys.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4FAC1A6F33 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 02:23:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level: 
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 Jh1LDzwYoQ5x for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 02:23:30 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A8F601A6F2B for <ietf@ietf.org>; Wed, 30 Apr 2014 02:23:30 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.226.232.234]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s3U9NEvA004350 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 30 Apr 2014 02:23:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1398849805; bh=lrdCeg4IWhlZohRLnq097f580qTArYe0/WIK1JZbgJk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JCBMOc0VTXMFXdBf/9Ou3f1yDz9AbbnrCLKnzuRZcCUKHlSdp1gIMHucH7SrWrl1B osHbG54yNyvlUCui89B+kfbndJdmgjv/DsjxTVKEAYm9vAcwSjiz5e4qun6/tRTxj0 E6ZL9mJ5I1zp1WWJY0YZbBLAken1BGdiFmhQfzw8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1398849805; i=@elandsys.com; bh=lrdCeg4IWhlZohRLnq097f580qTArYe0/WIK1JZbgJk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=AcfMb6T//p9AgXL12vEXG+/M2iY/ACRpmb74MHS/Qd7B2uYaoIw7tg2GsR767MQeQ +6IPLeSVF9FqTi9FIvPhHuWjKh9Si0BIwbg3vmKm90oaDebOpZ7LXyZ1hltDIF3/oF iiTm9du3bYR7bFdTM2BUBT13Dbla44OWO+VTteOU=
Message-Id: <6.2.5.6.2.20140430015953.0c47a318@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 30 Apr 2014 02:22:38 -0700
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Request for a code point assignment for ED25519 - draft-moonesamy-sshfp-ed25519-01
In-Reply-To: <5360BA2F.6050402@cs.tcd.ie>
References: <6.2.5.6.2.20140408174055.0ceb1810@elandnews.com> <6.2.5.6.2.20140410001913.0bc63b50@resistor.net> <A5CE78BA-5805-4922-9E1A-A30D3B5AA4CA@piuha.net> <6.2.5.6.2.20140410034359.0bc89d30@elandnews.com> <E8D78AA7-1BDB-4A35-8773-2513880EFB4C@piuha.net> <6.2.5.6.2.20140430005644.0afcefe8@elandnews.com> <5360BA2F.6050402@cs.tcd.ie>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gAYdLzisWVJN8CAqKvE1vaK-1J8
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 09:23:31 -0000

Hi Stephen,
At 01:54 30-04-2014, Stephen Farrell wrote:
>Yes. The CFRG meeting didn't raise any objection to this,
>so I'll move it along now. (Well, tomorrow.)

Thanks for the quick reply.

For the record, I am not aware of any IPR related to 
draft-moonesamy-sshfp-ed25519-01.

Regards,
S. Moonesamy 


From nobody Wed Apr 30 04:24:20 2014
Return-Path: <vesely@tana.it>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08DF41A081E for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 04:24:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.073
X-Spam-Level: 
X-Spam-Status: No, score=-3.073 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 kknL439qz1zB for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 04:24:05 -0700 (PDT)
Received: from wmail.tana.it (mail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id A05FD1A081F for <ietf@ietf.org>; Wed, 30 Apr 2014 04:24:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1398857042; bh=zws07yjCVjrE/HpI0piGT8iEgeuD2P8oJLvUrQAX85Q=; l=3300; h=Date:From:To:References:In-Reply-To; b=LEW/mfgeomhi7ALHoVP6Jv4WNpmnGVhVFvElNm7rh/MADSWNdv3wBQx4L9gDe2jfu oOpk0E9wqMM4i5aoVw3FxfKrjlAm58Qf24D9ihW/LQvxBSZSteXRMLY2f0ffEbuLy/ BGYX4xggoMXxELIxnc2R7Lk5guWrKRhAy7JB3Avo=
Authentication-Results: tana.it; auth=pass (details omitted)
Received: from [172.25.197.88] (pcale.tana [172.25.197.88]) (AUTH: CRAM-MD5 uXDGrn@SYT0/k) by wmail.tana.it with ESMTPA; Wed, 30 Apr 2014 13:24:02 +0200 id 00000000005DC039.000000005360DD52.000079A3
Message-ID: <5360DD52.1020108@tana.it>
Date: Wed, 30 Apr 2014 13:24:02 +0200
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.4.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se> <535FA739.3060608@dcrocker.net> <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se> <14DE2BC840FF3B8AA4A167EC@JcK-HP8200.jck.com>
In-Reply-To: <14DE2BC840FF3B8AA4A167EC@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/FiAhPs7NcE3jKF4qnBU_tF0h55s
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 11:24:11 -0000

Hi,

On Tue 29/Apr/2014 16:39:18 +0200 John C Klensin wrote:
> 
> If one examines those relationships, there is a case to be made
> that the problems they cause to mailing lists is not "collateral
> damage" at all.  Even if the effects were discovered by
> accident, continued use of DMARC with restrictive policies has
> the consequence of driving traffic away from mailing lists,
> perhaps especially mailing lists operated by smaller providers
> and non-profits, toward use of the for-profit systems operated
> by those same (to quote another recent comment) "too big to
> ignore" operators with a positive effect on their bottom line to
> the detriment of  other operators and ways of doing things.
> 
> Behaviors by large ("dominant", "too big to ignore", etc.)
> industry actors that have the effect of driving alternate
> solutions or providers out by mechanisms other than fair
> competition in the marketplace, especially when those mechanisms
> come out of collaborations among such actors, are, if other
> conditions are met, rather seriously illegal in many countries.
> If intent can be demonstrated, they are even more so.

That picture can get even more compelling by comparing DMARC's core
with SPF policies as historically proposed.  It was well known that
SPF breaks forwarding while ADSP breaks mailing lists.  DMARC chose to
err on the ADSP side, by confining SPF to an auxiliary author's domain
verification role.  One might malign that forwarding is requisite for
free-mail providers who draw users among people who already own a
mailbox somewhere.

However, I'm for a teleonomic view, where chance and necessity
determine the selection of fitter coalitions of structures and
functions.  The outcome favors for-profit systems because that is
(still) what our society is built upon.  If IETF, ISOC, or open-source
movements aim at promoting a different model of human cooperation, I
regret to conclude that the likely negative answer to the question in
the subject is to be considered something of a defeat.  Some competed
for an alternative evolution (recall the endless discussions since
MARID) but found no consensus.

> So, as a purely hypothetical set of questions (I am not
> recommending anything), I wonder what would happen if some of
> the people who have been claiming they or the general public are
> harmed by this would, instead of asking what the IETF can do
> about something that is not an IETF Standard, went to their
> local "competitiveness" or "antitrust" authorities, explained
> the situation and started complaining?

I'm neither a lawyer nor an ML admin, so I'm not going to claim
damage.  Yet, like most of us, I'll be harmed if MLs stop working well.

> I also wonder whether the IETF and ISOC have, or should seek, legal
> advice about how to keep adequate distance between themselves and
> this situation should some relevant jurisdiction initiate an
> investigation or enforcement action.

Rather than rebuffing responsibility, I'd expect the IETF to invent
something new, which works much like ML used to, but is compatible
with DMARC.  Yes, we may continue to call them "mailing lists".  The
alternative, to blame domains which follow the leading trend, doesn't
seem to be very promising...

Ale


From nobody Wed Apr 30 06:13:55 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B29E81A0684 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 06:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.602
X-Spam-Level: 
X-Spam-Status: No, score=-99.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_110=0.6, J_CHICKENPOX_14=0.6, J_CHICKENPOX_16=0.6, J_CHICKENPOX_46=0.6, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=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 SzcgIoZEvs9T for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 06:13:41 -0700 (PDT)
Received: from mail.santronics.com (secure.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 669211A047D for <ietf@ietf.org>; Wed, 30 Apr 2014 06:13:40 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=4090; t=1398863616; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=zcF8R0GPQ6XSDxXzqpRzS+KNNaA=; b=OrNoUBA2weE0JIZiaGKM oX8ONFsDnTygyENP0wBbJ7HnsiAGStovihw8ICf7F7pliwuf4h8H50BvYrN4MpIH ueq8rh+dLwTK9rsAgeYQ+Us615jkjvs4v9alHTpCmV1QHuSQZjolFJlUtcOXCGFb H+mGmfWrmolvqrIdqeH7U5Y=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 30 Apr 2014 09:13:36 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1972177353.3.2064; Wed, 30 Apr 2014 09:13:34 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=4090; t=1398863520; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=TzbWowt 2ZVxiZafsXNyKjE6kvC91x+ojmpah/JqXVL4=; b=b6jIiLpHIJoygdeqPHKcCPY t0DG4SzRTQPkxQTZXA0XkEngUvGGL7kmRwUx6GINnUZkTGzV4CMIeoCN1J5RTSPO g5fjhTjG64xKagMvObfApzXRherD3fGbiDm4IgRL9gha9cAtJNtPSNHze28gz11G vf5uxguzv9QjS8k+AQMA=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 30 Apr 2014 09:12:00 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 1991697015.9.11956; Wed, 30 Apr 2014 09:12:00 -0400
Message-ID: <5360F6FD.1030502@isdg.net>
Date: Wed, 30 Apr 2014 09:13:33 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Alessandro Vesely <vesely@tana.it>, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
Subject: Re: Will mailing lists survive DMARC?
References: <20140429124528.GA1324@mx1.yitter.info> <alpine.DEB.2.02.1404291502320.29282@uplift.swm.pp.se> <535FA739.3060608@dcrocker.net> <alpine.DEB.2.02.1404291524500.29282@uplift.swm.pp.se> <14DE2BC840FF3B8AA4A167EC@JcK-HP8200.jck.com> <5360DD52.1020108@tana.it>
In-Reply-To: <5360DD52.1020108@tana.it>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/c1DY5dwqpYNr-W19YG63yNeXZrE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 13:13:43 -0000

On 4/30/2014 7:24 AM, Alessandro Vesely wrote:

>> So, as a purely hypothetical set of questions (I am not
>> recommending anything), I wonder what would happen if some of
>> the people who have been claiming they or the general public are
>> harmed by this would, instead of asking what the IETF can do
>> about something that is not an IETF Standard, went to their
>> local "competitiveness" or "antitrust" authorities, explained
>> the situation and started complaining?
>
> I'm neither a lawyer nor an ML admin, so I'm not going to claim
> damage.  Yet, like most of us, I'll be harmed if MLs stop working well.
>

This was only a surprise to the people we were resistance to adding 
policy support.  Author Domain Policies had the same "know your 
network" migration issues SPF did.  Domains had to adjust by switching 
to more relaxed domains to participate in a public networking arena. 
I did the same. I remove all public usage of company's exclusive 
domains santronics.com and winserver.com and switched them to isdg.net 
where its a more relaxed author domain policy and one I can use to 
explore with.   Everyone serious about this stuff were aware of this 
stuff for nearly 9 years.

Besides, it was written in the DKIM abstract with its questionable 
"responsibility" semantics which I kept saying it really needs to get 
removed or get rephrased.

    DomainKeys Identified Mail (DKIM) permits a person, role, or
    organization that owns the signing domain to claim some
    responsibility for a message by associating the domain with the
    message.

If you are going to ask domains to begin signing, put investment in 
it, then why would anyone thing they would not want to invest in 
protecting the signature, and thus the message?

The only way to do this was with the original proof of concept -- 
AUTHOR DOMAIN SIGNING POLICIES!  Hate yelling it but is seems to be a 
central key point in all this forgotten.

Of course, the other argument could be that we don't want such strong 
and food for legal eagles semantics in our docs.  We continue to face 
this passÃ© mail design attitude for relaxation, incremental changes, 
yet, the problems do not get resolved this way.  Without the strong 
semantics, you can't deal with the legacy abuse mail operations. You 
lack a payoff. DMARC has forced that "relaxed" mail design mentality 
to change for the IETF.

>> I also wonder whether the IETF and ISOC have, or should seek, legal
>> advice about how to keep adequate distance between themselves and
>> this situation should some relevant jurisdiction initiate an
>> investigation or enforcement action.
>
> Rather than rebuffing responsibility, I'd expect the IETF to invent
> something new, which works much like ML used to, but is compatible
> with DMARC.  Yes, we may continue to call them "mailing lists".  The
> alternative, to blame domains which follow the leading trend, doesn't
> seem to be very promising...

They keep saying they don't think think the MLS needs to change, too 
historic. Its ok to add DKIM, but not Policy?  I don't buy it. I'm a 
long time MLS developer we have hundreds of operators with list 
operations.  It didn't make sense to me why you would add something 
that was half-ass complete.  Probably explains I'm one of the few 
implementators, if not the only one, of DKIM+POLICY (ADSP, ATPS) n a 
mailing list server product.

Adding DMARC is not going to be a problem.   It remains the same, it 
will be just like before with ADSP with the end of the day setup 
semantics:

     p=reject     is only for EXCLUSIVE domains for SYSTEM-WIDE 
application.
     p=quarantine is only for EXCLUSIVE domains for PER USER (junk 
bins) application.
     p=none       is for all, but with unknown handling.

If that is how it needs to be doc for my sysops, so be it.

The only issue would be to add a deployment option for p=reject

   [X] Enable DMARC

    (o) p=none
    (_) p=quarantine
    (_) p=reject
        (o) SMTP Reject with response ____________________
        (_) Accept and discard
        (_) Accept and keep


Or something like that.

-- 
HLS



From nobody Wed Apr 30 07:39:28 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D077D1A08DF for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 07:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 aU2vLroQRzKG for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 07:39:24 -0700 (PDT)
Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 24C591A08D7 for <ietf@ietf.org>; Wed, 30 Apr 2014 07:39:23 -0700 (PDT)
Received: by mail-la0-f43.google.com with SMTP id c6so1297913lan.2 for <ietf@ietf.org>; Wed, 30 Apr 2014 07:39:22 -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:content-type; bh=t46kVF45OV1wMofJnhFj274eSZdDhYAea4JqDQVB70o=; b=yKKKEYehQA+3rdhvlseuUiF5s3R3zDGEgbKtKWK9wIgzgAa+QDbWiGFbg9dpAJBtsB 0rFKcRtCrMwNqjehgpdADXeKd2zTmBeavbs+LToWcf1LQ0NGOqM+7Tij44NdoOuF/obN TgJexPdFly3DIoxDBLbxPrCFtarix6VVOVvWpGIhsUKhszF7b/2+/C1AedV4/R0d2Jzd QdkOXdHeph0VpOjzqOdL+zBrJ4AsIvaVts2Cf1j2gUjhXnSYi6HPWebJmBkVs/gJ0+qd OKNg73FzXqKnBkig5AR92bhRPrBwfyWyNTBBJwW91ylwVuY035/DeV9hABRX60h7H27h PQLg==
MIME-Version: 1.0
X-Received: by 10.112.24.172 with SMTP id v12mr158898lbf.74.1398868761955; Wed, 30 Apr 2014 07:39:21 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Wed, 30 Apr 2014 07:39:21 -0700 (PDT)
In-Reply-To: <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com>
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com>
Date: Wed, 30 Apr 2014 10:39:21 -0400
Message-ID: <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com>
Subject: Re: Enough DMARC whinging
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GaH28v3u443C4A9lieOMCwMwDfQ
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 14:39:25 -0000

If there is a problem, I am not seeing it on gmail.

I have checked my spam filters, no mail to any IETF list there. So
unless gmail is doing a hard reject on this, I am not seeing issues.

Of course the way to make mailing lists work with DMARC would be to
look at the headers and treat messages with mailing list headers
differently. Perhaps the issue isn't in DMARC but how the information
from DMARC is applied.

With all email filtering technologies, the results of any
authentication or policy check is merely advice, not a requirement.
The sender can't impose any requirements on the receiver. Folk who get
hot under the collar about mail filtering tech tend to do so because
they don't understand that.


On Tue, Apr 29, 2014 at 6:14 PM, Andrew G. Malis <agmalis@gmail.com> wrote:
> Philip,
>
> Here are the effects that I see. I use this gmail account for my IETF
> mailing lists. I am now consistently seeing email sent from Yahoo users end
> up in my spam folder with the following embedded warning message:
>
> Be careful with this message. Our systems couldn't verify that this message
> was really sent by yahoo.com. You might want to avoid clicking links or
> replying with personal information.  Learn more
>
> The sender, of course, is completely unaware of what is happening on the
> receiver's end, so they have no reason to want to change from Yahoo to
> another domain for posting.
>
> So this is imposing pain on the receiver, since I now have to consistently
> check my spam folder for valid IETF email.
>
> I see that you also use gmail, so you should start checking your spam folder
> as well.
>
> Cheers,
> Andy
>
>
> On Tue, Apr 29, 2014 at 3:54 PM, Phillip Hallam-Baker <hallam@gmail.com>
> wrote:
>>
>> I am finding it rather hard to follow the DMARC discussion. Some folk
>> have managed to convince me that they are upset but working out why
>> would require rather a lot of spec crunching.
>>
>> My best theory so far is that DMARC is some sort of email policy
>> statement and that either (1) some companies are now publishing a
>> policy that states 'reject all mail that purports to come from this
>> address that does not have authentication Y' or (2) some companies are
>> now rejecting mail not in compliance with said policy or (3) both.
>>
>> There is a simple truth about DNS names: Whoever owns them makes the
>> rules for their use [1]. If you don't like the rules for google.com
>> then choose another domain to post from.
>>
>>
>> If people want email to work with mailing lists, then don't complain
>> about reasonable choices people want to make. Work out a way to fix
>> mailing lists so that they work properly.
>>
>> There is no reason we can't change the way From works. Or add new from
>> headers.
>>
>> Are we engineers or curators of the past?
>>
>>
>> [1] Thus be rather suspicious of folk who claim that we merely rent
>> the use on terms of their choosing.
>>
>> --
>> Website: http://hallambaker.com/
>>
>



-- 
Website: http://hallambaker.com/


From nobody Wed Apr 30 08:03:41 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A779E1A08F1 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 08:03: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, SPF_PASS=-0.001] autolearn=ham
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 14RKs7Phv5Ip for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 08:03:38 -0700 (PDT)
Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 5975D1A08E8 for <ietf@ietf.org>; Wed, 30 Apr 2014 08:03:38 -0700 (PDT)
Received: by mail-qa0-f46.google.com with SMTP id w8so1734986qac.19 for <ietf@ietf.org>; Wed, 30 Apr 2014 08:03:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=IoPHOk/U/smI5Tbn9CugDcbTFuABGUOp3v7tKPwFB4I=; b=haUAuHVrCDOW8wl4CalfklUD/0hO8T7WgOIfU5Fq16wtF7SVIPLZAMabKkaPPQnJN3 PPszDi7v18Bndcdx8GY4DnJ6PZH/+Deyka2Bszj4OBF40MX//+LLlRuBJrYXm2zj9kGb pelOQ+l07W6c2JkfpmvwyEgHUEA/JpbBPTDzZyqpAN+Up51wia+egDnB3BNWOsRdQ3/f jIs0aDDtysrFxO5qwtYu0EqB3Oz8udnwCgYHNbRwS7gamNugGm8cytb9DxMpXs4w3e1J mpkFFuy3AuAv4v18howLKop0y9FNTtUvtaQnChyLMheYWyfaIaiZG6Robzfrg9STFn53 Bczw==
X-Received: by 10.224.66.4 with SMTP id l4mr6037226qai.70.1398870216551; Wed, 30 Apr 2014 08:03:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.205.69 with HTTP; Wed, 30 Apr 2014 08:03:15 -0700 (PDT)
In-Reply-To: <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com>
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com> <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 30 Apr 2014 11:03:15 -0400
Message-ID: <CAA=duU3scwm=j2BJ6jq4k5zRQPkXOVOR1UscQqZZ8tG5HEZTwQ@mail.gmail.com>
Subject: Re: Enough DMARC whinging
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c290585831ae04f843dadf
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2H9bAXqRexOh7xYmZZMBQnVDZqw
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 15:03:39 -0000

--001a11c290585831ae04f843dadf
Content-Type: text/plain; charset=UTF-8

Phillip,

Of course the way to make mailing lists work with DMARC would be to
> look at the headers and treat messages with mailing list headers
> differently. Perhaps the issue isn't in DMARC but how the information
> from DMARC is applied.
>

>From my reading of sections 10.2, 5.2, and 15.4 of
draft-kucherawy-dmarc-base-04,
you can't do that and still claim receiver conformance with that draft
(although there's the question of whether one should claim conformance to
an informational draft in the first place).

Cheers,
Andy

--001a11c290585831ae04f843dadf
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra">Phillip,</div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><di=
v id=3D":1i2" class=3D"a3s" style=3D"overflow:hidden">

Of course the way to make mailing lists work with DMARC would be to<br>
look at the headers and treat messages with mailing list headers<br>
differently. Perhaps the issue isn&#39;t in DMARC but how the information<b=
r>
from DMARC is applied.<br></div></blockquote></div><br>From my reading of s=
ections 10.2, 5.2, and 15.4 of=C2=A0<font color=3D"#000000"><span style=3D"=
line-height:1.2em">draft-kucherawy-dmarc-base-04, you can&#39;t do that and=
 still=C2=A0</span><span style=3D"line-height:15px">claim receiver conforma=
nce with that draft (although there&#39;s the question of whether one shoul=
d claim conformance to an informational draft in the first place).</span></=
font></div>

<div class=3D"gmail_extra"><font color=3D"#000000"><span style=3D"line-heig=
ht:15px"><br></span></font></div><div class=3D"gmail_extra"><font color=3D"=
#000000"><span style=3D"line-height:15px">Cheers,</span></font></div><div c=
lass=3D"gmail_extra">

<font color=3D"#000000"><span style=3D"line-height:15px">Andy</span></font>=
</div><div class=3D"gmail_extra"><font color=3D"#000000"><span style=3D"lin=
e-height:15px"><br></span></font></div></div>

--001a11c290585831ae04f843dadf--


From nobody Wed Apr 30 08:16:14 2014
Return-Path: <dcrocker@bbiw.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 970611A08F9 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 08:16:13 -0700 (PDT)
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] autolearn=ham
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 ayQLZdDe1yvi for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 08:16:12 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 2A7F91A08D3 for <ietf@ietf.org>; Wed, 30 Apr 2014 08:16:12 -0700 (PDT)
Received: from [10.168.69.12] (pool-71-164-185-121.dllstx.fios.verizon.net [71.164.185.121]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s3UFG5G1002979 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 30 Apr 2014 08:16:09 -0700
Message-ID: <536113B1.5070309@bbiw.net>
Date: Wed, 30 Apr 2014 10:16:01 -0500
From: Dave Crocker <dcrocker@bbiw.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: "Andrew G. Malis" <agmalis@gmail.com>
Subject: Re: Enough DMARC whinging
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com> <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com> <CAA=duU3scwm=j2BJ6jq4k5zRQPkXOVOR1UscQqZZ8tG5HEZTwQ@mail.gmail.com>
In-Reply-To: <CAA=duU3scwm=j2BJ6jq4k5zRQPkXOVOR1UscQqZZ8tG5HEZTwQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.67]); Wed, 30 Apr 2014 08:16:09 -0700 (PDT)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yRgLi0JX5qK1kHAAIXPraXyLgtI
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 15:16:13 -0000

On 4/30/2014 10:03 AM, Andrew G. Malis wrote:
> Phillip,
>
>     Of course the way to make mailing lists work with DMARC would be to
>     look at the headers and treat messages with mailing list headers
>     differently. Perhaps the issue isn't in DMARC but how the information
>     from DMARC is applied.
>
>
>  From my reading of sections 10.2, 5.2, and 15.4 of
> draft-kucherawy-dmarc-base-04, you can't do that and still claim
> receiver conformance with that draft (although there's the question of
> whether one should claim conformance to an informational draft in the
> first place).


(Conformance is voluntary.  People choose the specs they want to 
support, no matter the formal status.)


To the extent that varying from -base produces better results at 
reasonable cost, then receivers will do it.  The challenge is to offer 
clear and compelling guidance about that variance and gain support for 
its use.

For example, using the mere presence of List-* header fields as a basis 
for deviating from a domain owner's DMARC policy request would seem an 
easy attack vector by bad actors.

On the other hand, using the presence of the fields, combined perhaps 
the list signing the message (and covering those fields) and with the 
receiver's knowing that the list operator has a good reputation might 
make quite a bit of sense...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Apr 30 08:20:43 2014
Return-Path: <iab-chair@iab.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F09A91A6F7B; Wed, 30 Apr 2014 08:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=unavailable
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 TmnjWiqrXJYu; Wed, 30 Apr 2014 08:20:36 -0700 (PDT)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1900:3001:11::28]) by ietfa.amsl.com (Postfix) with ESMTP id 2A6011A6F88; Wed, 30 Apr 2014 08:20:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 44C9D1E4366; Wed, 30 Apr 2014 08:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pAVY0I5C3Uhy; Wed, 30 Apr 2014 08:20:16 -0700 (PDT)
Received: from [192.168.2.100] (pool-96-241-160-129.washdc.fios.verizon.net [96.241.160.129]) by c8a.amsl.com (Postfix) with ESMTPSA id D45961E41B7; Wed, 30 Apr 2014 08:20:15 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Subject: Call for volunteers for C/C++ API liaison manager
Mime-Version: 1.0 (Apple Message framework v1085)
From: IAB Chair <iab-chair@iab.org>
Date: Wed, 30 Apr 2014 11:20:31 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zwmOETryLR7UxstvAIfAHhEfJUk
Cc: IAB <iab@iab.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IAB <iab@iab.org>
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 15:20:40 -0000

We often see proposals for APIs (most commonly C APIs) discussed in the =
IETF.  ISO/IEC JTC1/SC22 is the standards body for various programming =
languages, notably including C (WG14) and C++ (WG21), and those groups =
have been working on APIs for various IETF technologies, including URIs, =
sockets, IP addresses, etc.  The IAB is considering whether to request a =
liaison relationship with ISO/IEC JTC1/SC22 and is seeking to determine =
if there are candidates willing to serve as a liaison manager before =
determining whether to request the relationship.  For details on what a =
liaison manager position entails, see RFC 4052, RFC 4053, and RFC 4691.
=20
Volunteers are requested to send email to iab@iab.org by May 28, 2014.

On behalf of the IAB,
Russ Housley
IAB Chair=


From nobody Wed Apr 30 09:52:57 2014
Return-Path: <hallam@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61C4C1A08E3 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 09:52:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 RyaT-exB5CAA for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 09:52:54 -0700 (PDT)
Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) by ietfa.amsl.com (Postfix) with ESMTP id C4BB21A802D for <ietf@ietf.org>; Wed, 30 Apr 2014 09:52:53 -0700 (PDT)
Received: by mail-lb0-f182.google.com with SMTP id l4so1445373lbv.13 for <ietf@ietf.org>; Wed, 30 Apr 2014 09:52:51 -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:content-type; bh=IE9qQXF10+WO8TKESRk6BZIx9Pg7zlQL6gVjzUDz9Fs=; b=pehO2YczXs6KoU/EgVN8q/a+6nCqSpLHbcnVANxy5aKiET7++RSXDMVkKIGuCU+6eJ sR3sbgFC+M52v26SdZHullBZTGIPRudur7/D7WEfoByEQqqNKVk2XaJp2JZpBbg7faBg LpTiLlkHPla+XbbVBypyN7TFtq7xDKH+hvyqL2e9MqWIPKYa8D9kOyWNwtale2g0PH9P D2k65kH+BRXwp9lSwsxFwWPMSqQnUHppR2QjQ68ykpHezJzNsrOc61nn8T+cVovm8vDd j6R3Us6sqX520f+b/4bmBGxswXX+3ULunuOADer1uvqZ/PCXVrJELCz0DX10zCqIosqQ Z2zQ==
MIME-Version: 1.0
X-Received: by 10.152.87.176 with SMTP id az16mr2005390lab.43.1398876771435; Wed, 30 Apr 2014 09:52:51 -0700 (PDT)
Received: by 10.112.234.229 with HTTP; Wed, 30 Apr 2014 09:52:51 -0700 (PDT)
In-Reply-To: <CAA=duU3scwm=j2BJ6jq4k5zRQPkXOVOR1UscQqZZ8tG5HEZTwQ@mail.gmail.com>
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com> <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com> <CAA=duU3scwm=j2BJ6jq4k5zRQPkXOVOR1UscQqZZ8tG5HEZTwQ@mail.gmail.com>
Date: Wed, 30 Apr 2014 12:52:51 -0400
Message-ID: <CAMm+LwhtHRPmnoyXojHCtO10wCdQAGaCZPXztSrYZRLNiXQDmQ@mail.gmail.com>
Subject: Re: Enough DMARC whinging
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SwoaNs883uVV1SofQLVtD3bbmxw
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 16:52:55 -0000

On Wed, Apr 30, 2014 at 11:03 AM, Andrew G. Malis <agmalis@gmail.com> wrote:
> Phillip,
>
>> Of course the way to make mailing lists work with DMARC would be to
>> look at the headers and treat messages with mailing list headers
>> differently. Perhaps the issue isn't in DMARC but how the information
>> from DMARC is applied.
>
>
> From my reading of sections 10.2, 5.2, and 15.4 of
> draft-kucherawy-dmarc-base-04, you can't do that and still claim receiver
> conformance with that draft (although there's the question of whether one
> should claim conformance to an informational draft in the first place).


Given a choice between conformance with a draft and conformance with
reality, I favor the second over the first.



-- 
Website: http://hallambaker.com/


From nobody Wed Apr 30 10:22:06 2014
Return-Path: <mcr@sandelman.ca>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B51321A0919 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 10:22:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.352
X-Spam-Level: 
X-Spam-Status: No, score=-1.352 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_110=0.6, J_CHICKENPOX_16=0.6, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=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 VUQzFDhLeZcX for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 10:22:01 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3::184]) by ietfa.amsl.com (Postfix) with ESMTP id 6A72C1A70E1 for <ietf@ietf.org>; Wed, 30 Apr 2014 10:22:01 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id ED1042002F; Wed, 30 Apr 2014 13:23:06 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id D34C563ABD; Wed, 30 Apr 2014 13:21:53 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id BE26463AA2; Wed, 30 Apr 2014 13:21:53 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Tony Hansen <tony@att.com>
Subject: Re: Google.com hops on the DMARC bandwagon
In-Reply-To: <536012FC.9020803@att.com>
References: <alpine.BSF.2.00.1404291512550.3309@joyce.lan> <CAL9jLaZhoWkaKpscm4YA4F-kSpt9tvjhax8f6soJzaY-Q0SsnA@mail.gmail.com> <CE39F90A45FF0C49A1EA229FC9899B0507D5DE7D@USCLES544.agna.amgreetings.com> <536011BD.3050704@meetinghouse.net> <536012FC.9020803@att.com>
X-Mailer: MH-E 8.2; nmh 1.3-dev; GNU Emacs 23.4.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<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Wed, 30 Apr 2014 13:21:53 -0400
Message-ID: <27426.1398878513@sandelman.ca>
Sender: mcr@sandelman.ca
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MkAWRBinlD-m6t01WoWmV1F1Vgo
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 17:22:02 -0000

--=-=-=
Content-Transfer-Encoding: quoted-printable


Tony Hansen <tony@att.com> wrote:
    >>>> On Tue, Apr 29, 2014 at 3:16 PM, John R Levine <johnl@taugh.com>
    >>>> wrote:
    >>>>> I see that google.com now publishes a DMARC policy of p=3Dquarant=
ine.
    >>>>>
    >>>>> While this won't bounce people off lists like p=3Dreject does, it
    >>>>> still makes it fairly pointless to post to this or any other list
    >>>>> from a google.com
    >>>>

    >> Ahh... so we can't expect to see Vint in any of the ietf discussions
    >> in the near future!

    > Anyone with mail servers that look at the dmarc settings won't see
    > postings. People behind mail servers that do NOT look at the dmarc
    > settings will see the postings just fine.

@google.com people will get kicked off mailing lists due to bounces
From=20other @google.com people.

So, you can have Vint on the list, or Lorenzo, or Harald, but not both :-)

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




--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQCVAwUBU2ExMYqHRg3pndX9AQKZmAP9FdfL3n+uy64KUUa7XSuESdEPzaMHEdiI
YNn8QnZENxG8d0A9QB6/qfMlVtLI1OpSxaQFkbhYXKofIcB5DsfVJGjpDhhE6eXM
UQC1nL5qhiN2WK6vhOZZaOCpCqZ210XCavevWmJU5g8rP7rnKBGs6qWZCwAJ8FY7
f+q+ZPZDB44=
=Hoh6
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Apr 30 11:17:04 2014
Return-Path: <mitch@telmate.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6927F1A885F for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 11:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 DQfZ5Nf3p0a0 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 11:16:55 -0700 (PDT)
Received: from mail-ob0-f181.google.com (mail-ob0-f181.google.com [209.85.214.181]) by ietfa.amsl.com (Postfix) with ESMTP id 7CB321A86E7 for <ietf@ietf.org>; Wed, 30 Apr 2014 11:16:53 -0700 (PDT)
Received: by mail-ob0-f181.google.com with SMTP id gq1so2366935obb.26 for <ietf@ietf.org>; Wed, 30 Apr 2014 11:16:52 -0700 (PDT)
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:content-type; bh=cKwB7TDcML0VGmzoB+64z6M2RhXeqKF6ppnqjQ0VI3c=; b=U/69lKDyiaFIWcTL/lLC+uqO4UYVvFB6b7GzPL45WuWs4RTFdLA0356pmxGer7/0Uz PmwBn0YkJLyx/PFTyZ02KzasD+/VygvnL9Kr1tACnXUM8oI+KHifwR89DHXEyKhD6SQa uGXNHMPhqkzgoz2kh1fxoivroumUShJsW1lD9QfCK0F8xS5IgkBLcVmsJvFg/+A4FSOI EIcLpzUY5nh08CYNVvlLDXc61d8kQG5q+YjqT3TwcgPnmYPUWwI7Sq4nGteQCojXqAxN qEBgZi5Dk6ud41bFHFCzVgSpq++VEqkdZWXkIonuxwtBO4PIGHqoQTm3Dv8e4rip5a8+ wJPQ==
X-Gm-Message-State: ALoCoQmWRPj5TL1+v+Vu9QHKMExR6ZMA40yDFFaFJfTWzx6bR8wptYZlPZPHK9Ckl05U+CLCFuEK
MIME-Version: 1.0
X-Received: by 10.60.55.97 with SMTP id r1mr6856489oep.5.1398881812012; Wed, 30 Apr 2014 11:16:52 -0700 (PDT)
Received: by 10.182.4.209 with HTTP; Wed, 30 Apr 2014 11:16:51 -0700 (PDT)
In-Reply-To: <CAMm+LwhtHRPmnoyXojHCtO10wCdQAGaCZPXztSrYZRLNiXQDmQ@mail.gmail.com>
References: <CAMm+Lwh0Sc2wtvjEAjOMi4emDzyF4JWmmzYr5QEFcmyoKtkTAA@mail.gmail.com> <CAA=duU0i1Ppc-nMeWL-ipms4E4b0wpsSRZdLG+2YhujPgH-ZPQ@mail.gmail.com> <CAMm+LwikJhO5R6UqWx8qUswMptgTw_wF6E6_9Ok=SRYTBChYgA@mail.gmail.com> <CAA=duU3scwm=j2BJ6jq4k5zRQPkXOVOR1UscQqZZ8tG5HEZTwQ@mail.gmail.com> <CAMm+LwhtHRPmnoyXojHCtO10wCdQAGaCZPXztSrYZRLNiXQDmQ@mail.gmail.com>
Date: Wed, 30 Apr 2014 11:16:51 -0700
Message-ID: <CADune5ZceY6R+kqppRhb0yDYHQ3ezxH_PqAOL+v0LcnDWO7o1w@mail.gmail.com>
Subject: Re: Enough DMARC whinging
From: Mitch Rodrigues <mitch@telmate.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=089e0115f08a7d0e2704f8468dab
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rx-2bLao2G07UfdH9R4QLUzSeu0
Cc: IETF general list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 18:17:00 -0000

--089e0115f08a7d0e2704f8468dab
Content-Type: text/plain; charset=UTF-8

Here is what I gather from all this talk.

I do not think DMARC is going anywhere and will continue to gain support
and popularity is it an inconvenience definitely, however going forward, I
feel it is our responsibility to make sure it is standards compliant, or
come up with new standards so everything does not go boom in the night.
With this said,
I also see a lot of traffic being spammed now for what appears to be no
apparent reason (Mostly from Yahoo domains), but hey thats less email i
have to read through.

And as for Google.com, If google wants to use it for their internal emails,
that is totally their choice, and will go one of two ways. A) It will work
flawlessly for their needs. or B) It will break things, and force them to
refine the strategy a bit more so it can be useable in the wild.


Mitch






On Wed, Apr 30, 2014 at 9:52 AM, Phillip Hallam-Baker <hallam@gmail.com>wrote:

> On Wed, Apr 30, 2014 at 11:03 AM, Andrew G. Malis <agmalis@gmail.com>
> wrote:
> > Phillip,
> >
> >> Of course the way to make mailing lists work with DMARC would be to
> >> look at the headers and treat messages with mailing list headers
> >> differently. Perhaps the issue isn't in DMARC but how the information
> >> from DMARC is applied.
> >
> >
> > From my reading of sections 10.2, 5.2, and 15.4 of
> > draft-kucherawy-dmarc-base-04, you can't do that and still claim receiver
> > conformance with that draft (although there's the question of whether one
> > should claim conformance to an informational draft in the first place).
>
>
> Given a choice between conformance with a draft and conformance with
> reality, I favor the second over the first.
>
>
>
> --
> Website: http://hallambaker.com/
>
>

--089e0115f08a7d0e2704f8468dab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Here is what I gather from all this talk.=C2=A0<div><br></=
div><div>I do not think DMARC is going anywhere and will continue to gain s=
upport and popularity is it an inconvenience definitely, however going forw=
ard, I feel it is our responsibility to make sure it is standards compliant=
, or come up with new standards so everything does not go boom in the night=
. With this said,=C2=A0</div>
<div>I also see a lot of traffic being spammed now for what appears to be n=
o apparent reason (Mostly from Yahoo domains), but hey thats less email i h=
ave to read through.</div><div><br></div><div>And as for Google.com, If goo=
gle wants to use it for their internal emails, that is totally their choice=
, and will go one of two ways. A) It will work flawlessly for their needs. =
or B) It will break things, and force them to refine the strategy a bit mor=
e so it can be useable in the wild.</div>
<div><br></div><div><br></div><div>Mitch</div><div><br></div><div><br></div=
><div><br></div><div><br></div></div><div class=3D"gmail_extra"><br><br><di=
v class=3D"gmail_quote">On Wed, Apr 30, 2014 at 9:52 AM, Phillip Hallam-Bak=
er <span dir=3D"ltr">&lt;<a href=3D"mailto:hallam@gmail.com" target=3D"_bla=
nk">hallam@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">On W=
ed, Apr 30, 2014 at 11:03 AM, Andrew G. Malis &lt;<a href=3D"mailto:agmalis=
@gmail.com">agmalis@gmail.com</a>&gt; wrote:<br>

&gt; Phillip,<br>
&gt;<br>
&gt;&gt; Of course the way to make mailing lists work with DMARC would be t=
o<br>
&gt;&gt; look at the headers and treat messages with mailing list headers<b=
r>
&gt;&gt; differently. Perhaps the issue isn&#39;t in DMARC but how the info=
rmation<br>
&gt;&gt; from DMARC is applied.<br>
&gt;<br>
&gt;<br>
&gt; From my reading of sections 10.2, 5.2, and 15.4 of<br>
&gt; draft-kucherawy-dmarc-base-04, you can&#39;t do that and still claim r=
eceiver<br>
&gt; conformance with that draft (although there&#39;s the question of whet=
her one<br>
&gt; should claim conformance to an informational draft in the first place)=
.<br>
<br>
<br>
</div></div>Given a choice between conformance with a draft and conformance=
 with<br>
reality, I favor the second over the first.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
<br>
<br>
--<br>
Website: <a href=3D"http://hallambaker.com/" target=3D"_blank">http://halla=
mbaker.com/</a><br>
<br>
</font></span></blockquote></div><br></div>

--089e0115f08a7d0e2704f8468dab--


From nobody Wed Apr 30 16:48:57 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61F21A6F65; Wed, 30 Apr 2014 16:48:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 Q47huSdCK_sd; Wed, 30 Apr 2014 16:48:51 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 6DA1A1A6F63; Wed, 30 Apr 2014 16:48:51 -0700 (PDT)
Received: from [128.9.184.196] ([128.9.184.196]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s3UNmi5T001440 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 30 Apr 2014 16:48:44 -0700 (PDT)
Message-ID: <53618BDD.1080900@isi.edu>
Date: Wed, 30 Apr 2014 16:48:45 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: IAB <iab@iab.org>, IETF Announce <ietf-announce@ietf.org>
Subject: Re: Call for volunteers for C/C++ API liaison manager
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org>
In-Reply-To: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MXwgClJez2WOeHlS5tkDx09y2nk
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Apr 2014 23:48:53 -0000

On 4/30/2014 8:20 AM, IAB Chair wrote:
> We often see proposals for APIs (most commonly C APIs) discussed in
> the IETF.

A protocol "API" isn't language-specific; it describes (or ought to) the 
upper and lower layer interactions, e.g., as was done in RFC793.

When we propose an API in the IETF, it should be for that protocol API, 
not for a language API (which is an instance, specific to a language and 
also often an OS, of that protocol API).

(that doesn't preclude the benefit of a liason to a language-standards 
group, but we shouldn't be seeing IETF proposals for such instances IMO).

Joe


From nobody Wed Apr 30 19:28:54 2014
Return-Path: <chaitanyabd@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27D571A09DD; Wed, 30 Apr 2014 19:28:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 EIPXXPJgq8g4; Wed, 30 Apr 2014 19:28:51 -0700 (PDT)
Received: from mail-qc0-x22f.google.com (mail-qc0-x22f.google.com [IPv6:2607:f8b0:400d:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 882F31A09D9; Wed, 30 Apr 2014 19:28:51 -0700 (PDT)
Received: by mail-qc0-f175.google.com with SMTP id w7so1313622qcr.20 for <multiple recipients>; Wed, 30 Apr 2014 19:28:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:from:date:message-id:subject:to:cc:content-type;  bh=2RnryNmFC2pwkkG6GJvHXIqg6fn3QJw+cxpFkREG/Fw=; b=hmwph2Or+BF1+r6EIcp6nowSjqXWj2w0ANaSCtAHb3Zecboc4pY4sNnMy8ccV0WTzO fD0EsvKWYqoqWfcGRVQgf13jmBdhZQqUSJxkKGzLCKIYp71vzCkZZe6Okjex2pn4SOYs Qc+NAu9t2+PS74ReZAxBRHq0jQyr+DYqOYv7ugBslUOMzQN2BiE6Pz/kA9eiIYt0AweR PrGesWBefTUXryrztlv6w1aNNNFT7zCiLSJ+5TbzkvzeiOCS5/uZpUImYyHAw1ZpCMuU 6kWtAHuDO1B0x+80T3ixo+II7XXKQhwlNRUqdAznUViiAnR9n2AGPvvg5U9rirflb6Zy wwKg==
X-Received: by 10.224.0.142 with SMTP id 14mr10366505qab.72.1398911329611; Wed, 30 Apr 2014 19:28:49 -0700 (PDT)
MIME-Version: 1.0
From: Chaitanya Dhareshwar <chaitanyabd@gmail.com>
Date: Wed, 30 Apr 2014 19:28:49 -0700
Message-ID: <2576075144611874116@unknownmsgid>
Subject: RE: Call for volunteers for C/C++ API liaison manager
To: Joe Touch <touch@isi.edu>, IAB <iab@iab.org>, IETF Announce <ietf-announce@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wRv2PntgsWdGpbNWWXzbbqAMVKs
Cc: IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 02:28:53 -0000

+1 Joe.

Chaitanya Dhareshwar

Mobile: +91.9820760253
From: Joe Touch
Sent: 5/1/2014 5:19
To: IAB; IETF Announce
Cc: IETF
Subject: Re: Call for volunteers for C/C++ API liaison manager


On 4/30/2014 8:20 AM, IAB Chair wrote:
> We often see proposals for APIs (most commonly C APIs) discussed in
> the IETF.

A protocol "API" isn't language-specific; it describes (or ought to) the
upper and lower layer interactions, e.g., as was done in RFC793.

When we propose an API in the IETF, it should be for that protocol API,
not for a language API (which is an instance, specific to a language and
also often an OS, of that protocol API).

(that doesn't preclude the benefit of a liason to a language-standards
group, but we shouldn't be seeing IETF proposals for such instances IMO).

Joe


From nobody Wed Apr 30 19:37:04 2014
Return-Path: <melinda.shore@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280F41A0949 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 19:36:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 FavMmCV9vVfO for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 19:36:54 -0700 (PDT)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 44FF71A092F for <ietf@ietf.org>; Wed, 30 Apr 2014 19:36:54 -0700 (PDT)
Received: by mail-ie0-f176.google.com with SMTP id rd18so3050529iec.35 for <ietf@ietf.org>; Wed, 30 Apr 2014 19:36:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=/6giRfS+ZKahjqowBoYcSPH6yTW0pfdpJIXTp3DKzDc=; b=bylinnNLETxDsElRkHGXWoCXdSL/BLbKqlEUL84vWVl69RdCoQ6N9+yswlR3QBywx5 fy4ON1wwMrmUKmSgPdkf1nX0nQTgNdzxPRst5PEdB59gO7NiuQd8cCA1Gnc5RBiRjJFj cYNOENc7HcxF4+/cCdOkzYe5LBulOPnyF6+8KPV8ApI4K3MvDCbIFu2yfU62+xFjrgUN eyOSMPS74JF7dEPVMvsVv0YLnCEhwpx0GzHqfhpHycyy5I/rNCe285zvgzqvtfuLRAsO toCpR/xUpqoRCl0+LHVXamYUPSKNQlK9l8GUXESrAz+qtMZ4cmnuqO+A5ovY++3sGD4U nXEQ==
X-Received: by 10.50.43.136 with SMTP id w8mr187867igl.20.1398911812544; Wed, 30 Apr 2014 19:36:52 -0700 (PDT)
Received: from spandex.local (209-112-214-47-rb1.nwc.dsl.dynamic.acsalaska.net. [209.112.214.47]) by mx.google.com with ESMTPSA id j9sm3392289igu.10.2014.04.30.19.36.50 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Apr 2014 19:36:51 -0700 (PDT)
Message-ID: <5361B341.4000200@gmail.com>
Date: Wed, 30 Apr 2014 18:36:49 -0800
From: Melinda Shore <melinda.shore@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Call for volunteers for C/C++ API liaison manager
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org> <53618BDD.1080900@isi.edu>
In-Reply-To: <53618BDD.1080900@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0Ajl1MaHAIS8o400bF5P4uYRUaM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 02:36:57 -0000

On 4/30/14 3:48 PM, Joe Touch wrote:
> (that doesn't preclude the benefit of a liason to a language-standards
> group, but we shouldn't be seeing IETF proposals for such instances IMO).

Probably not, but it seems pretty clear that deployment
of some IETF protocols has suffered from either the lack
of a comprehensive API, or crappy API.  I'm thinking of
IPSec, newer DNS features, etc.  I think it's very much
in the interest of the IETF to have someone around who
can talk to some of the language standards bodies about
how to expose protocol features, how to deal with options,
etc.

Melinda


From nobody Wed Apr 30 20:05:57 2014
Return-Path: <hsantos@isdg.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 798C61A09DD for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 20:05:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.002
X-Spam-Level: 
X-Spam-Status: No, score=-102.002 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, USER_IN_WHITELIST=-100] autolearn=ham
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 b2ptz6NknR5g for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 20:05:46 -0700 (PDT)
Received: from listserv.winserver.com (dkim.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 882141A09DC for <ietf@ietf.org>; Wed, 30 Apr 2014 20:05:46 -0700 (PDT)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=1071; t=1398913538; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=B4mCKTkhggcg7+jWS+AZRu9v8DI=; b=HVj261bs+JhTi7vEWwUR 2kJJ7WY53hBD6meQKUDnFcb0ltH+cImcpLsiKTuPkJkj/5FAwV3AP2YNccdiIA0Q I85fioWqV6WKVN3ejdRNCFXEahLPdrYgV4pfTZJdZFJ6eMhe6gLt8TXj7CWEjpy5 7CUhVT8c87hpiE0EvfBYZyc=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 30 Apr 2014 23:05:38 -0400
Authentication-Results: dkim.winserver.com; dkim=pass header.d=beta.winserver.com header.s=tms1 header.i=beta.winserver.com;  adsp=pass policy=all author.d=isdg.net asl.d=beta.winserver.com;
Received: from opensite.winserver.com (beta.winserver.com [208.247.131.23]) by winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2022099389.3.3564; Wed, 30 Apr 2014 23:05:37 -0400
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=1071; t=1398913441; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=1HZEXjn TwQNWHVnBNk/pAP2p23XIo+KizQdR7UYstFU=; b=ui+Os/MiDM4RWOdM2wwX8DL qa10US++HaCOSMT4X5Ih+gvAJwBl8PfBi2gUnu8vDzFvwzUZSARoy6QHv094kUpj P5O2bwYgr0i201vOp+RLXTZNa/fIRefdSNGdl9Jc+FCwpcwJj3rPajO3w3TLTpFq QOrQysQUeb8EITuOks2I=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Wed, 30 Apr 2014 23:04:01 -0400
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2041617765.9.13700; Wed, 30 Apr 2014 23:04:01 -0400
Message-ID: <5361B9FF.4020107@isdg.net>
Date: Wed, 30 Apr 2014 23:05:35 -0400
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Call for volunteers for C/C++ API liaison manager
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org> <53618BDD.1080900@isi.edu> <5361B341.4000200@gmail.com>
In-Reply-To: <5361B341.4000200@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D9mNrYFbC85c-5DCcqX_w83qkh8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 03:05:51 -0000

On 4/30/2014 10:36 PM, Melinda Shore wrote:
> On 4/30/14 3:48 PM, Joe Touch wrote:
>> (that doesn't preclude the benefit of a liason to a language-standards
>> group, but we shouldn't be seeing IETF proposals for such instances IMO).
>
> Probably not, but it seems pretty clear that deployment
> of some IETF protocols has suffered from either the lack
> of a comprehensive API, or crappy API.  I'm thinking of
> IPSec, newer DNS features, etc.  I think it's very much
> in the interest of the IETF to have someone around who
> can talk to some of the language standards bodies about
> how to expose protocol features, how to deal with options,
> etc.

Its a good idea, but you have to watch out for a dependency that would 
exclude other languages and also platforms out there, especially with 
higher level languages, server-side scripting languages.  If your 
liaison manager is experienced with many languages, that would be a 
plus. Its a difficult task to manage a multiple language API for 
examples of IETF protocols.  But it can be done.

-- 
HLS



From nobody Wed Apr 30 20:16:51 2014
Return-Path: <dwm@xpasc.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93BAC1A083C for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 20:16:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.546
X-Spam-Level: 
X-Spam-Status: No, score=-0.546 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, MISSING_HEADERS=1.021, SPF_PASS=-0.001] autolearn=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 ZgPn_o31uas8 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 20:16:48 -0700 (PDT)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 01D251A0839 for <ietf@ietf.org>; Wed, 30 Apr 2014 20:16:47 -0700 (PDT)
Received: from xpasc.com (h-68-164-244-186.snva.ca.megapath.net [68.164.244.186]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 1FB903FAA0 for <ietf@ietf.org>; Thu,  1 May 2014 03:15:29 +0000 (UTC)
Received: from egate.xpasc.com (egate.xpasc.com [10.1.2.49]) by xpasc.com (8.13.8/8.13.8) with ESMTP id s413GiNY000392 for <ietf@ietf.org>; Wed, 30 Apr 2014 20:16:44 -0700
Date: Wed, 30 Apr 2014 20:16:44 -0700 (PDT)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: Call for volunteers for C/C++ API liaison manager
In-Reply-To: <5361B341.4000200@gmail.com>
Message-ID: <alpine.LRH.2.01.1404302013540.8611@egate.xpasc.com>
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org> <53618BDD.1080900@isi.edu> <5361B341.4000200@gmail.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KHNacLRCpkm_iFxKxDj6PswtRsg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 03:16:48 -0000

And the language standards bodies don't define many of the
APIs AFAICT ... the defined to a major degree by the groups
implementing the network libraries. If OpenSSL and someone else
implement an SSL API, it would be really good for it to be the
same C/C++ etc. API.

On Wed, 30 Apr 2014, Melinda Shore wrote:

> On 4/30/14 3:48 PM, Joe Touch wrote:
> > (that doesn't preclude the benefit of a liason to a language-standards
> > group, but we shouldn't be seeing IETF proposals for such instances IMO).
>
> Probably not, but it seems pretty clear that deployment
> of some IETF protocols has suffered from either the lack
> of a comprehensive API, or crappy API.  I'm thinking of
> IPSec, newer DNS features, etc.  I think it's very much
> in the interest of the IETF to have someone around who
> can talk to some of the language standards bodies about
> how to expose protocol features, how to deal with options,
> etc.
>
> Melinda
>


From nobody Wed Apr 30 20:22:13 2014
Return-Path: <touch@isi.edu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FFED1A083C for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 20:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.551
X-Spam-Level: 
X-Spam-Status: No, score=-2.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.651] autolearn=ham
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 gnbzN0j58DNj for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 20:22:02 -0700 (PDT)
Received: from darkstar.isi.edu (darkstar.isi.edu [128.9.128.127]) by ietfa.amsl.com (Postfix) with ESMTP id 24C381A0839 for <ietf@ietf.org>; Wed, 30 Apr 2014 20:22:02 -0700 (PDT)
Received: from [192.168.1.93] (pool-71-105-87-112.lsanca.dsl-w.verizon.net [71.105.87.112]) (authenticated bits=0) by darkstar.isi.edu (8.13.8/8.13.8) with ESMTP id s413Lbv8001486 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 30 Apr 2014 20:21:41 -0700 (PDT)
Message-ID: <5361BDC2.9020409@isi.edu>
Date: Wed, 30 Apr 2014 20:21:38 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
Subject: Re: Call for volunteers for C/C++ API liaison manager
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org> <53618BDD.1080900@isi.edu> <5361B341.4000200@gmail.com>
In-Reply-To: <5361B341.4000200@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/M5SBQt3EglQ-ucqFV-HcOSDltOg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 03:22:06 -0000

On 4/30/2014 7:36 PM, Melinda Shore wrote:
> On 4/30/14 3:48 PM, Joe Touch wrote:
>> (that doesn't preclude the benefit of a liason to a language-standards
>> group, but we shouldn't be seeing IETF proposals for such instances IMO).
>
> Probably not, but it seems pretty clear that deployment
> of some IETF protocols has suffered from either the lack
> of a comprehensive API, or crappy API.

+1

However, somewhere along the line, AFAICT the IETF started thinking of 
protocol APIs as language implementations, and decided (rightly) that 
the latter was out of scope, and threw the baby out with the bathwater.

IMO, a protocol is *incomplete* without its protocol API.

> I'm thinking of
> IPSec, newer DNS features, etc.  I think it's very much
> in the interest of the IETF to have someone around who
> can talk to some of the language standards bodies about
> how to expose protocol features, how to deal with options,
> etc.

It is, if you can find someone who knows both and can attend both ;-)

Joe


From nobody Wed Apr 30 21:36:26 2014
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C06A1A09B9 for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 21:36:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 1MYLhAENpgle for <ietf@ietfa.amsl.com>; Wed, 30 Apr 2014 21:36:22 -0700 (PDT)
Received: from mail-ob0-x230.google.com (mail-ob0-x230.google.com [IPv6:2607:f8b0:4003:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id 9CD191A0851 for <ietf@ietf.org>; Wed, 30 Apr 2014 21:36:22 -0700 (PDT)
Received: by mail-ob0-f176.google.com with SMTP id wp4so3115846obc.7 for <ietf@ietf.org>; Wed, 30 Apr 2014 21:36:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=9ASixMOHUZk9lySt/N8bSRGAU4KcsapIwvWSbxc6L4w=; b=zHisvHkmyxwM41zSAT+AeM+Wq0MOrZImRUCM1s+rZhdWAUXq3nSNjfEcITUTj0F3Nb /wD0Tgz9zIlAhEllJCXq3U3T2847YHscEXJkuWvpCs8nzX6DLWXip3cHZK5NbwcyLvmT npurpVFQaUDHpI0H+D14wqZpQo3YiBKn7PVWt/vXARE+9U0EtASrSDmR8FhQZxiY/81a Go/Icv9n8B/gjrgti8hhnohIgcsMuUL4rHUUYczXCH69ob/4uVai67PR0JH4dO3zTO/2 ABSfNJ2iU8wLS2cdM0GGPg81s8mWgWH4fomziM11IbKuaz8+XCkEUDKjWJpXicAR9sT/ qsJA==
X-Received: by 10.60.115.129 with SMTP id jo1mr9300001oeb.0.1398918980770; Wed, 30 Apr 2014 21:36:20 -0700 (PDT)
Received: from [192.168.0.13] (cpe-76-187-7-89.tx.res.rr.com. [76.187.7.89]) by mx.google.com with ESMTPSA id zc8sm56610512obc.1.2014.04.30.21.36.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 30 Apr 2014 21:36:20 -0700 (PDT)
Message-ID: <5361CF41.3030105@gmail.com>
Date: Wed, 30 Apr 2014 23:36:17 -0500
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.4.0
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>, Melinda Shore <melinda.shore@gmail.com>,  ietf@ietf.org
Subject: Re: Call for volunteers for C/C++ API liaison manager
References: <EB423B81-41F2-480D-B1EE-80E1753E1CDB@iab.org> <53618BDD.1080900@isi.edu> <5361B341.4000200@gmail.com> <5361BDC2.9020409@isi.edu>
In-Reply-To: <5361BDC2.9020409@isi.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3NsCac2CBMBvA7syTTY1lf4KEfs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 May 2014 04:36:24 -0000

On 04/30/2014 10:21 PM, Joe Touch wrote:
>
>
> On 4/30/2014 7:36 PM, Melinda Shore wrote:
>> On 4/30/14 3:48 PM, Joe Touch wrote:
>>> (that doesn't preclude the benefit of a liason to a language-standards
>>> group, but we shouldn't be seeing IETF proposals for such instances 
>>> IMO).
>>
>> Probably not, but it seems pretty clear that deployment
>> of some IETF protocols has suffered from either the lack
>> of a comprehensive API, or crappy API.
>
> +1
>
> However, somewhere along the line, AFAICT the IETF started thinking of 
> protocol APIs as language implementations, and decided (rightly) that 
> the latter was out of scope, and threw the baby out with the bathwater.
>
> IMO, a protocol is *incomplete* without its protocol API.

FWIW, Martin and I understand this, and that's one of the points I've 
been stressing about the IETF 89 TAPS BOF.

I'd like to throw the baby back in. The bathwater can stay gone.

Spencer, who is really disturbed at the word picture he just drew ;-)

