
From hsantos@isdg.net  Sat Feb  1 09:41:28 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 0EF681A03EC for <ietf@ietfa.amsl.com>; Sat,  1 Feb 2014 09:41:28 -0800 (PST)
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 Xz8L0dwbiwd5 for <ietf@ietfa.amsl.com>; Sat,  1 Feb 2014 09:41:25 -0800 (PST)
Received: from groups.winserver.com (winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id 0EA081A0395 for <ietf@ietf.org>; Sat,  1 Feb 2014 09:41:24 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=2699; t=1391276474; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=9G50jckj9ffAtpqEBQwsm1ynRc8=; b=Mvka1Tty6/9tY1ZlQquf OIoxihcJF0euyPDz1ZWLBAptD2tFFP9Fp6Vv5clFMBXhBtSMh60olpBUzL2O0XvM dird4d8Vj4xHizwH8quqHMhiVZKYnNbhLr3XVcutGM70/nW2885uASyqLsQcsUUe d/hpTPrDwkOLSOWoGOIwi0s=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 01 Feb 2014 12:41:14 -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 558958485.7116.3364; Sat, 01 Feb 2014 12:41:13 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=2699; t=1391275875; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=LmRMUr0 wm7KvGxz8Po6/ChWqU3gcQxyMTJh18Ia8Y7U=; b=QVNDgObgk3vkR/8fcACPTsr 9kRm1uYt0k/RkQnj7NUT0jexnZ0+esxvx+SEfRIEy8Hv19VkfEhEkSugyGhB0aRK 5rXj11Sw0MnPLG8QHmjbgoixhfPjUEt/FyD64d1GXz/H406SqFUcBosDCcXu1r8Z ASY1o5WLxI9nPvkyyiqw=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Sat, 01 Feb 2014 12:31:15 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 5254818.9.8780; Sat, 01 Feb 2014 12:31:15 -0500
Message-ID: <52ED31BB.8080906@isdg.net>
Date: Sat, 01 Feb 2014 12:41:15 -0500
From: Hector Santos <hsantos@isdg.net>
Organization: Santronics Software, Inc.
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Subject: Re: Make it a Proposed Method rather than Proposed Standard [Re: When is an idea a good idea?]
References: <52E80FA9.5020704@gmail.com> <52E826A3.3040605@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40245F28@GLKXM0002V.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30D40245F28@GLKXM0002V.GREENLNK.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 01 Feb 2014 17:41:28 -0000

Hi Chris,

How does the IETF feel about having "multiple standards" of the same 
thing, in other words, redundancy?

I don't think we generally want that, and I don't think we want "bad" 
ideas becoming standards because it becomes harder and costly to undue.

However, we do need to document them too as well to allow people to 
try them out.  So if the authors don't wish to make it, EXPERIMENTAL, 
BCP or INFORMATIONAL,  a better option is to further it as a Proposed 
Method rather than get bounce around, wasting so much time as a 
Proposed Standard where Rough Consensus decisions is more problematic 
than ever before.  Keep in mind there is also the "politics" part of 
it too of getting things pushed and supported. Once a proposed 
standard starts, you might as well "forget" about other possible 
solutions.  They might not be allowed.  However, I am seen them also 
used to weaken and even destroy PS efforts - raises doubt, etc, which 
is good when it shouldn't had been a PS in the first place.

A PM would be easier I feel to pursue with less "politics," IMO.  A 
lesser peer review process. Experimental and informational are too 
weak.  If we took "Best" out of BCP, then perhaps a CP would be closer 
to a PM or Internet Method (IM).  It just isn't the only, close-ended 
standard.

Perhaps it should be made clearer that a BCP or Proposed Standard is 
not absolute in the IETF as far as solutions are concern.  The 
suggestion is to provide a way to document strong multiple solutions 
which may not necessary the "standard" or "best" solution.

Personally, I would write more documents, get involved more with PM 
documents. PS are too hard. Too stressful and time consuming and the 
others, like BCP is just the wrong category. Maybe take away the B 
from CP and we got it. :)

Thanks for your feedback.

-- 
HLS

On 1/29/2014 5:29 AM, Dearlove, Christopher (UK) wrote:
> I'm not sure more categories is what we want.
>
> I have observed all of the following (not at the same time, though some were) from people not familiar with the IETF and RFCs, although invested in or using RFCs:
> - Assuming that all RFCs are standards.
> - Assuming that only Standards matter, that Proposed Standards and Draft standards aren't important.
> - Assuming that Draft Standard is a category below Proposed Standard.
> - Recognising that there are standards and not-standards, but not distinguishing in any way between Standard, Draft Standard and Proposed Standard (calling all of them Standards).
> - Just plain confused.
>
> (And the concept of BCP is probably completely unknown to anyone thinking any of the above.)
>
> Another category isn't going to help here.
>




From john-ietf@jck.com  Sat Feb  1 11:23:15 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 7EF5A1A05DE for <ietf@ietfa.amsl.com>; Sat,  1 Feb 2014 11:23:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YLwLhotO7F_m for <ietf@ietfa.amsl.com>; Sat,  1 Feb 2014 11:23:13 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 400DC1A042F for <ietf@ietf.org>; Sat,  1 Feb 2014 11:23:11 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W9g9K-0002aW-Cd; Sat, 01 Feb 2014 14:22:42 -0500
Date: Sat, 01 Feb 2014 14:22:37 -0500
From: John C Klensin <john-ietf@jck.com>
To: Hector Santos <hsantos@isdg.net>, "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
Subject: Re: Make it a Proposed Method rather than Proposed Standard [Re: When is an idea a good idea?]
Message-ID: <9219A45C6F6780DB47C168C4@JcK-HP8200.jck.com>
In-Reply-To: <52ED31BB.8080906@isdg.net>
References: <52E80FA9.5020704@gmail.com> <52E826A3.3040605@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40245F28@GLKXM0002V.GREENLNK.net> <52ED31BB.8080906@isdg.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
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: Sat, 01 Feb 2014 19:23:15 -0000

--On Saturday, February 01, 2014 12:41 -0500 Hector Santos
<hsantos@isdg.net> wrote:

> Hi Chris,
> 
> How does the IETF feel about having "multiple standards" of
> the same thing, in other words, redundancy?
> 
> I don't think we generally want that, and I don't think we
> want "bad" ideas becoming standards because it becomes harder
> and costly to undue.
> 
> However, we do need to document them too as well to allow
> people to try them out.  So if the authors don't wish to make
> it, EXPERIMENTAL, BCP or INFORMATIONAL,  a better option is to
> further it as a Proposed Method rather than get bounce around,
> wasting so much time as a Proposed Standard where Rough
>...

Hector,

While "proposed method" may be better terminology, this most
recent explanation sounds to me as if you are reinvention what
"Proposed Standard" was supposed to be, with "real"
standardization (and recommendations about adoption, non-test
deployment, and use) coming only with "Draft Standard".  Sadly
that hasn't worked for many years.  One could debate whether it
ever really worked consistently.

>From observations of a number of standards bodies that do work
in so-called "high technology" areas (not just networking), part
of the problem is that companies are most likely to send
design-level engineers with real product involvement to meetings
when the technology is still new and being designed.  Once there
is a design and organizations have made a commitment to
production-quality implementations, deployment, aales and
marketing, or operations, the tendency is for those the time of
those design-level engineers to be considered too valuable to
spend on standardization and participation shifts toward those
whose roles have more to do with protecting company interests,
worrying about process rather than technology details, and doing
the kind of fine-tuning and second-guessing that are often
described in terms of second (or third) system effects.   

That pattern is independent of whatever one calls the first
stage in the process -- the folks with the most design knowledge
and experience participate actively early-on (if at all) and
things evolve after that toward professional standardizers over
time.

The IETF has been much more successful than average at avoiding
or minimizing that pattern (although I think we are worse at it
than we were a few decades ago when Internet fundamentals were
still being designed and tested).  But the tendencies are there
and I think it is extremely unlikely that fiddling around with
names will have little lasting effect.

best,
   john


From Ted.Lemon@nominum.com  Sat Feb  1 13:07: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 DFE0E1ABD2A for <ietf@ietfa.amsl.com>; Sat,  1 Feb 2014 13:07:30 -0800 (PST)
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 YV4mRIS4etrg for <ietf@ietfa.amsl.com>; Sat,  1 Feb 2014 13:07:29 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8271A1F76 for <ietf@ietf.org>; Sat,  1 Feb 2014 13:07:29 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUu1iDQeTCKgp0SVPe7U205pXEZF3y3CE@postini.com; Sat, 01 Feb 2014 13:07:25 PST
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 186EC1B82F4 for <ietf@ietf.org>; Sat,  1 Feb 2014 13:07:25 -0800 (PST)
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 F3C17190052; Sat,  1 Feb 2014 13:07:24 -0800 (PST)
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; Sat, 1 Feb 2014 13:07:24 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Gen-ART LC review of draft-ietf-pcp-description-option-03
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52E67F34.1050404@viagenie.ca>
Date: Sat, 1 Feb 2014 16:07:22 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <FB1343A5-63DE-42FF-BE11-4B4CB82CE8C9@nominum.com>
References: <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <CF0B68F0.8395%repenno@cisco.com> <035301cf1b46$d54ba980$7fe2fc80$@gmail.com> <52E67F34.1050404@viagenie.ca>
To: Simon Perreault <simon.perreault@viagenie.ca>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
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, 01 Feb 2014 21:07:31 -0000

On Jan 27, 2014, at 10:45 AM, Simon Perreault =
<simon.perreault@viagenie.ca> wrote:
> Example use case: you have several hosts in your home that do PCP =
automatically. For example, you start up Transmission, a BitTorrent =
client, and that automatically fires a PCP request to create a mapping. =
Transmission could set a description such as "Transmission BitTorrent =
client running on Roni Even's MacBook Pro". This is useful when you =
access your home router's administration web interface and see the list =
of mappings created with PCP. You can immediately understand what it is =
that is opening holes in your firewall/NAT.

Any reason not to add some text to the document that talks about this?   =
I have to admit that I wasn't confused by this after reading the =
document, but if Roni was, that's an indication that at least something =
ought to be tweaked, since there will be other readers who similarly =
lack context.


From john-ietf@jck.com  Sat Feb  1 15:18: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 379051A0007; Sat,  1 Feb 2014 15:18:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: 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-fgo53oVrdX; Sat,  1 Feb 2014 15:18:32 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 19E8B1A0005; Sat,  1 Feb 2014 15:18:31 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W9jpM-0002nn-30; Sat, 01 Feb 2014 18:18:20 -0500
Date: Sat, 01 Feb 2014 18:18:11 -0500
From: John C Klensin <john-ietf@jck.com>
To: iesg@ietf.org
Subject: Agenda, security, and monitoring
Message-ID: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.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
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, 01 Feb 2014 23:18:36 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi.

After looking through the agenda and thinking about end to end
confidentiality mechanisms, a few questions/suggestions:

(1) Other than a probably-appropriate level of general paranoia,
do we have
any reason to believe that PGP (Symantec and/or GNUPG versions)
has been
sufficiently compromised to not provide a good defense against
either
pervasive surveillance or general snooping?

(2) If the answer is "no, they are probably ok" or better,
should we be
doing a key signing in London?  That would facilitate longer
keys for those
who would benefit from that and getting the facilities more
generally
available to relative newcomers [1].

(3) If the answer is "yes, they have to be treated with great
suspicion",
they why are there not BOFs or other sessions on the agenda to
consider
whether the IETF standards should be upgraded or, if that is not
feasible,
deprecated?

(4) If we are going to do a key signing, would there be enough
interest in
signing of CACERT X.509 keys to see if there are enough people
with the
right credentials who will be in London to certify those too (in
spite of
the non-presence of the CACERT root keys in various browsers,
etc.)?

If we are really serious about preventing monitoring, especially
at the
application layer and doing so within our own community as an
example, this
should be obvious.  Indeed, it might be interesting as a first
step to fix
the IETF list so it wouldn't accept unsigned messages.
Conversely, if it
is not obvious, maybe we are not really that serious.

   best,
    john

[1] Some people will sign PGP keys on the basis of documents
(like
passports) alone, others won't.  But, even if most people won't,
it has
been a sufficiently long time since we've done a key-signing at
IETF that I
imagine there are a number of no-longer-newcomers around who
might benefit
and who are reasonably well known to others .

-----BEGIN PGP SIGNATURE-----
Version: Encryption Desktop 10.3.0 (Build 8741)
Charset: utf-8

wj8DBQFS7YCK5pJ/EbOJ8NoRAku9AJ9hDPLM7pUN8FbhcTWcq9Ipx42qDACdFSLW
Nfly1Cdbie7k7ANPxuRZtA0=
=ft5+
-----END PGP SIGNATURE-----

From dhc@dcrocker.net  Sat Feb  1 15:35:24 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 548AC1A0007; Sat,  1 Feb 2014 15:35:24 -0800 (PST)
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 hykVKsYFBjQI; Sat,  1 Feb 2014 15:35:23 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 477B01A0005; Sat,  1 Feb 2014 15:35:23 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s11NZFri002318 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Feb 2014 15:35:19 -0800
Message-ID: <52ED8496.6000006@dcrocker.net>
Date: Sat, 01 Feb 2014 15:34:46 -0800
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.2.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, iesg@ietf.org
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com>
In-Reply-To: <19A23B84A41C1D4EA513F2C8@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]); Sat, 01 Feb 2014 15:35:19 -0800 (PST)
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, 01 Feb 2014 23:35:24 -0000

On 2/1/2014 3:18 PM, John C Klensin wrote:
> (1) Other than a probably-appropriate level of general paranoia,
> do we have
> any reason to believe that PGP (Symantec and/or GNUPG versions)
> has been
> sufficiently compromised to not provide a good defense against
> either
> pervasive surveillance or general snooping?


1. It has demonstrated unacceptable usability for average users.

2. It does not protect the header or the envelope, to the extent anyone 
cares about divulging the Subject or other message meta-data...

3. It's packaging in the body is ugly. (See #1)

For sufficiently motivated and technical individuals, it's clear the 
technology is extremely useful as a discrete capability.

However any focus on PGP or S/MIME in their current forms will be a 
distraction that well might seduce the IETF community into thinking it's 
doing something useful for the Internet that actually isn't.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Sat Feb  1 16:35: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 0D9AD1A0018; Sat,  1 Feb 2014 16:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LP7TvzLbbD5M; Sat,  1 Feb 2014 16:35:48 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 020751A0017; Sat,  1 Feb 2014 16:35:47 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W9l2A-0002rk-5i; Sat, 01 Feb 2014 19:35:38 -0500
Date: Sat, 01 Feb 2014 19:35:33 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net, iesg@ietf.org
Subject: Re: Agenda, security, and monitoring
Message-ID: <3EAA52D5BE6B9B73B3B1E716@JcK-HP8200.jck.com>
In-Reply-To: <52ED8496.6000006@dcrocker.net>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.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
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, 02 Feb 2014 00:35:50 -0000

--On Saturday, February 01, 2014 15:34 -0800 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 2/1/2014 3:18 PM, John C Klensin wrote:
>> (1) Other than a probably-appropriate level of general
>> paranoia, do we have
>> any reason to believe that PGP (Symantec and/or GNUPG
>> versions) has been
>> sufficiently compromised to not provide a good defense against
>> either
>> pervasive surveillance or general snooping?
> 
> 
> 1. It has demonstrated unacceptable usability for average
> users.

Agree completely, but that wasn't the question.  

Noting the email systems with which we are both familiar as
examples and the history of attacks (whether technical or
legal-judicial) on intermediate systems (relays and otherwise),
if we are asked today what our best end to end technology
options are, those are it.  The acceptability part is, at least
IMO, a combination of a "not needed enough to be worth the
trouble" and the difficulties of managing public, and especially
private, keys.  For the first, I suspect that there are a lot
more people in the world who care enough to go to extra trouble
than was the case a year or so ago.  We could debate whether "a
lot" is actually large enough to be a significant number, but
even if I agreed that it was not, I would rather tell a
concerned user "the best technology we have is annoying  and
will require you and your correspondents to learn more, and fuss
more, than you would probably like" than "if you can't trust
your email provider, its choice of relays, and any relevant
governments, you are screwed and the IETF is ok with that".

> 2. It does not protect the header or the envelope, to the
> extent anyone cares about divulging the Subject or other
> message meta-data...

Extending from and building on my comments above, is your
preferred alternative "sending email is hopeless; if you don't
want to be monitored, you should go back to something secure
like smoke signals (uh, whoops)".  For many purposes, if one has
a choice between solid content protection with no or weak
envelope protection and no protection at all, the answer is
obvious.  Conversely if one had good envelope protection that
provided only hop-by-hop content protection, the two sets of
methods could be combined if that were felt to be needed.

> 3. It's packaging in the body is ugly. (See #1)

Yep.  And if one didn't want to tolerate ugly in order to get
more privacy, then one doesn't need the privacy enough.  See
above.

> For sufficiently motivated and technical individuals, it's
> clear the technology is extremely useful as a discrete
> capability.
> 
> However any focus on PGP or S/MIME in their current forms will
> be a distraction that well might seduce the IETF community
> into thinking it's doing something useful for the Internet
> that actually isn't.

Because of my concerns about compromised mail system operators,
relay servers and even submission and delivery servers, plus the
vast majority of users who do not control the domains they user
for email, I could say much the same thing about all of the work
that is going on about hop-by-hop methods, especially
domain-dependent ones.  But I don't feel that way: I don't think
there are any completely effective methods out there (in terms
of, e.g., protection of both envelope and content against
attackers with legal authority).  So, for me, the choice is
between deploying a variety of mechanisms, understanding and
being clear about the applicability and limitations of each, and
saying things that amount to "hopeless".  

All of that said, I wasn't proposing a "focus on PGP or S/MIME"
or anything like it.  I was proposing a convenience and enabler
for those members of our community who felt like using those
methods or, if the techniques we have standardized are actually
defective, that we either fix them or, depending on the level of
risk, either generate Applicability Statements or deprecate the
things.  Certainly having IETF standardized security-related
protocols out there that we consider unacceptable without doing
something about it is inconsistent with our claimed interest in
mitigating pervasive surveillance.  And that is really all I
said.

regards,
   john



From randy@psg.com  Sat Feb  1 17:03:06 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 E0ECC1A0018; Sat,  1 Feb 2014 17:03:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QYe4YI7RDQki; Sat,  1 Feb 2014 17:03:05 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 8BEE31A0012; Sat,  1 Feb 2014 17:03:05 -0800 (PST)
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 1W9lSd-00059S-6a; Sun, 02 Feb 2014 01:02:59 +0000
Date: Sun, 02 Feb 2014 10:02:57 +0900
Message-ID: <m2ob2qs4vy.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Agenda, security, and monitoring
In-Reply-To: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.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: multipart/signed; boundary="pgp-sign-Multipart_Sun_Feb__2_10:02:51_2014-1"; micalg=pgp-sha512; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7bit
Cc: IESG <iesg@ietf.org>, 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: Sun, 02 Feb 2014 01:03:07 -0000

--pgp-sign-Multipart_Sun_Feb__2_10:02:51_2014-1
Content-Type: text/plain; charset=US-ASCII

i support pgp key signing even though pgp and signed mail are not
perfect or make cash fall from the sky.  one day at a time.

i am not sure how well the normal signing party will scale to the
crowd likely to be attracted at an ietf meeting.  perhaps a more
distributed asynchronous protocol?  though i personally get a lot
of value in seeing how rigorously alice checks bob's credentials,
and mark my trust in alice accordingly.

there are folk who are good at key signing parties/protocols, so i
will not presume to grab management of this.  but if i can help,
holler.

randy


--pgp-sign-Multipart_Sun_Feb__2_10:02:51_2014-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (Darwin)
Comment: GPGTools - http://gpgtools.org

iQEcBAABCgAGBQJS7Zk/AAoJEMzMBey4OgLtPxsH/jTCZbJOYWnOKQFF+8bgX8Ys
kbOiDHG91sHxKyQxb0VUnlnxatF5eHCkXpsLXmu/Detr0TQW3FeidcDX8FmdA3hL
Qhyv1skI//EkRcBMB1I4eNvwm3Yw1YXWTBsR8JdcUcuE+S2e80QA7YvzBUaNKKLk
i4bCviaP+TUd4RfKy9JRGfa/Ie4af4I8Vt+u457qDO/sCTh3EqNEMJKwt3IxP319
LcSXrZISzLmK5RqhwAQHLzkEscVzAsqmj1ib1oYulZUJ/jtrBWaUcq4fgeonL4Kn
bzxx2QQ2pk9iCX26wvWS7BE3KobG0+yJ797z3YfAvKgXwzNzxpQAwqfmPv4B4e8=
=2AfI
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Sun_Feb__2_10:02:51_2014-1--

From stephen.farrell@cs.tcd.ie  Sat Feb  1 18:27: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 738761A0027; Sat,  1 Feb 2014 18:27:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zcQ6Dtam3JDo; Sat,  1 Feb 2014 18:27:40 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 725FB1A0028; Sat,  1 Feb 2014 18:27:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 43B26BE4D; Sun,  2 Feb 2014 02:27:35 +0000 (GMT)
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 5BHN8nqmtCCD; Sun,  2 Feb 2014 02:27:33 +0000 (GMT)
Received: from [10.87.48.10] (unknown [86.46.30.212]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id BA9EDBE38; Sun,  2 Feb 2014 02:27:33 +0000 (GMT)
Message-ID: <52EDAD15.6060504@cs.tcd.ie>
Date: Sun, 02 Feb 2014 02:27:33 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, iesg@ietf.org
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com>
In-Reply-To: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 02 Feb 2014 02:27:43 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi John,

On 02/01/2014 11:18 PM, John C Klensin wrote:
> Hi.
> 
> After looking through the agenda and thinking about end to end 
> confidentiality mechanisms, a few questions/suggestions:
> 
> (1) Other than a probably-appropriate level of general paranoia, do
> we have any reason to believe that PGP (Symantec and/or GNUPG
> versions) has been sufficiently compromised to not provide a good
> defense against either pervasive surveillance or general snooping?

That's two questions. IMO, neither S/MIME nor PGP provide
highly effective protection against pervasive monitoring (PM).
Either can be pretty good against "general snooping." In
both cases the protocol crypto is, as far as we know, just
fine. Both protocols (PGP and S/MIME) however were designed
in a different time, when an enterprise security mode was
far more often an accurate description of most Internet users'
reality, so that's not that surprising.

So there's no yes/no answer to your question(s) #1.

> 
> (2) If the answer is "no, they are probably ok" or better, should
> we be doing a key signing in London?  That would facilitate longer 
> keys for those who would benefit from that and getting the
> facilities more generally available to relative newcomers [1].

I'm fine to help get a room, if someone else takes on the
organising.

> 
> (3) If the answer is "yes, they have to be treated with great 
> suspicion", they why are there not BOFs or other sessions on the
> agenda to consider whether the IETF standards should be upgraded
> or, if that is not feasible, deprecated?

I think the lack of BoFs is because end-to-end interpersonal
messaging and how to make that resistant to PM is a
significantly hard problem. And there is also the issue that
there are plenty of reasons why various folks (e.g. advertisers,
not just govt.) would rather that interpersonal messaging were
not secured end to end, so it seems the people with significant
deployment also lack motivation, to say the least.

I do however think the XMPP folks are doing the right things
as far as I can see.

We are however having a workshop [1] before IETF-89 that will
discuss this and other topics related to PM. (Sorry, its
already oversubscribed, but we'll be reporting on it at the
saag session.)

  [1] https://www.w3.org/2014/strint/

> (4) If we are going to do a key signing, would there be enough 
> interest in signing of CACERT X.509 keys to see if there are enough
> people with the right credentials who will be in London to certify
> those too (in spite of the non-presence of the CACERT root keys in
> various browsers, etc.)?

No idea personally.

> If we are really serious about preventing monitoring, especially at
> the application layer and doing so within our own community as an 
> example, this should be obvious.

I disagree as it happens. Putting an emphasis on identification
and authentication seems backwards to me. First, we ought try
provide means to communicate that resist PM, (which requires
confidentiality and can use some help from Mr. Data Minimisation:-)
and after we have that nicely unerway, we can then see how to
establish various kinds of authentication.

I don't believe that starting from authentication is at all
the right approach.

But, I might be wrong, so happy to see people signing keys.

> Indeed, it might be interesting as a first step to fix the IETF
> list so it wouldn't accept unsigned messages.

Wasn't that debated a few months ago. I don't think that
would be at all useful for anyone.

> Conversely, if it is not obvious, maybe we are not really that
> serious.

No. Being serious about PM does not mean wanting to start
by identifying and authenticating everything in sight. I've
deliberately put that in an argumentative way, but I hope
it makes it clear why we really need to start from
confidentiality and mechanisms like minimising the PII in
our protocols.

Cheers,
S.


> 
> best, john
> 
> [1] Some people will sign PGP keys on the basis of documents (like 
> passports) alone, others won't.  But, even if most people won't, it
> has been a sufficiently long time since we've done a key-signing
> at IETF that I imagine there are a number of no-longer-newcomers
> around who might benefit and who are reasonably well known to
> others .
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQEcBAEBAgAGBQJS7a0VAAoJEC88hzaAX42i+6MH/An544gWl1H6dvAnfMuW9/2I
fLI4D3fwvVRzXXRU0ElLhfNZwjQaA+Ofu0EmshCoenmHOy845wugRUnFOB3+pedq
n2g3c60zbR0VMI6GzkjViC1dj6W0Z0L2CKJrIYTzA4ve1suMjoMqDCDg7ZsoWIsn
sXjx7gL9ubsyOm7TtmWHvamV/oaDrZGuqEYzxKIVZnyooEYKa1xplapPCrFpsIK2
18B/YfCRfYzKqdFxHFZQC2A3P/Iw7phbKUwOL2OoZTePZw5LjhK9HF39p+Al0neL
crXRpn8WObY0OLqiV89cYHafOAZex2bfgd8jZBJfpxOceFbSjE7GizuTENl6Wmg=
=RYeX
-----END PGP SIGNATURE-----

From dhc@dcrocker.net  Sat Feb  1 18:38:55 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 4B74F1A0029; Sat,  1 Feb 2014 18:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.701
X-Spam-Level: 
X-Spam-Status: No, score=-3.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, 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 oGGS-7Jd2FkP; Sat,  1 Feb 2014 18:38:54 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4D06D1A0027; Sat,  1 Feb 2014 18:38:54 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s122ckGU003797 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Feb 2014 18:38:50 -0800
Message-ID: <52EDAF9A.7070706@dcrocker.net>
Date: Sat, 01 Feb 2014 18:38:18 -0800
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.2.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>, John C Klensin <john-ietf@jck.com>
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <m2ob2qs4vy.wl%randy@psg.com>
In-Reply-To: <m2ob2qs4vy.wl%randy@psg.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]); Sat, 01 Feb 2014 18:38:50 -0800 (PST)
Cc: IESG <iesg@ietf.org>, 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, 02 Feb 2014 02:38:55 -0000

On 2/1/2014 5:02 PM, Randy Bush wrote:
> i support pgp key signing even though pgp and signed mail are not
> perfect or make cash fall from the sky.  one day at a time.


After twenty years of one day at a time, it's demonstrably not the 
vehicle for mass-adoption, nor is there any basis for viewing it as the 
foundation of the vehicle.

If you think otherwise, please offer an explanation of how to get from 
the small-scale, long-term here to the the necessarily very large-scale 
there that we need to reach.

Again, putting energy into PGP or S/MIME -- in anything like their 
current form -- incurs extremely expensive opportunity costs for the 
IETF community.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From stephen.farrell@cs.tcd.ie  Sat Feb  1 18:44: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 86BFD1A0029; Sat,  1 Feb 2014 18:44:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yPrJq0aW_ElC; Sat,  1 Feb 2014 18:44:42 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id 9433E1A0027; Sat,  1 Feb 2014 18:44:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id EEAFDBE50; Sun,  2 Feb 2014 02:44:37 +0000 (GMT)
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 mK6hgOrB8iAV; Sun,  2 Feb 2014 02:44:37 +0000 (GMT)
Received: from [10.87.48.10] (unknown [86.46.30.212]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D8F24BE38; Sun,  2 Feb 2014 02:44:36 +0000 (GMT)
Message-ID: <52EDB114.2020807@cs.tcd.ie>
Date: Sun, 02 Feb 2014 02:44:36 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, Randy Bush <randy@psg.com>,  John C Klensin <john-ietf@jck.com>
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <m2ob2qs4vy.wl%randy@psg.com> <52EDAF9A.7070706@dcrocker.net>
In-Reply-To: <52EDAF9A.7070706@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: IESG <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: Sun, 02 Feb 2014 02:44:43 -0000

On 02/02/2014 02:38 AM, Dave Crocker wrote:
> On 2/1/2014 5:02 PM, Randy Bush wrote:
>> i support pgp key signing even though pgp and signed mail are not
>> perfect or make cash fall from the sky.  one day at a time.
> 
> 
> After twenty years of one day at a time, it's demonstrably not the
> vehicle for mass-adoption, nor is there any basis for viewing it as the
> foundation of the vehicle.
> 
> If you think otherwise, please offer an explanation of how to get from
> the small-scale, long-term here to the the necessarily very large-scale
> there that we need to reach.
> 
> Again, putting energy into PGP or S/MIME -- in anything like their
> current form -- incurs extremely expensive opportunity costs for the
> IETF community.

You may be right, but I'm not so clear about that, as stated.

If someone wanted to propose using PGP or S/MIME (aka CMS) formats
to provide closer-to-end-to-end confidentiality protection for email
messages that covered most headers in a way that might get deployment
then I think that would not match your description. I do suspect
that that is not likely to happen.

If OTOH, we spent a lot of time debating email message origin
authentication then I fully agree with you that we'd just be
distracting ourselves pointlessly.

S.


> 
> d/
> 

From dhc@dcrocker.net  Sat Feb  1 19:22:07 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 BB7C51A003C; Sat,  1 Feb 2014 19:22:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.701
X-Spam-Level: 
X-Spam-Status: No, score=-3.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, 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 QLL-fX1KfJBJ; Sat,  1 Feb 2014 19:22:06 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 72C8C1A0027; Sat,  1 Feb 2014 19:22:06 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s123LtA0004135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 1 Feb 2014 19:21:58 -0800
Message-ID: <52EDB9B7.3040309@dcrocker.net>
Date: Sat, 01 Feb 2014 19:21:27 -0800
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.2.0
MIME-Version: 1.0
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, dcrocker@bbiw.net, Randy Bush <randy@psg.com>, John C Klensin <john-ietf@jck.com>
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <m2ob2qs4vy.wl%randy@psg.com> <52EDAF9A.7070706@dcrocker.net> <52EDB114.2020807@cs.tcd.ie>
In-Reply-To: <52EDB114.2020807@cs.tcd.ie>
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, 01 Feb 2014 19:21:59 -0800 (PST)
Cc: IESG <iesg@ietf.org>, 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, 02 Feb 2014 03:22:07 -0000

On 2/1/2014 6:44 PM, Stephen Farrell wrote:
> If someone wanted to propose using PGP or S/MIME (aka CMS) formats
> to provide closer-to-end-to-end confidentiality protection for email
> messages that covered most headers in a way that might get deployment
> then I think that would not match your description. I do suspect
> that that is not likely to happen.

1.  Very much not likely.

2.  It's unrelated to the parts of such a service that appear to be the 
major barriers to large-scale use

3.  It's the wrong level of design discussion, at this stage.


> If OTOH, we spent a lot of time debating email message origin
> authentication then I fully agree with you that we'd just be
> distracting ourselves pointlessly.

+1

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Sat Feb  1 21:18:29 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 C6FF91A0031; Sat,  1 Feb 2014 21:18:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SdwxJn1JfCSI; Sat,  1 Feb 2014 21:18:28 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EB73E1A0018; Sat,  1 Feb 2014 21:18:27 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1W9pRj-0003DI-Fe; Sun, 02 Feb 2014 00:18:19 -0500
Date: Sun, 02 Feb 2014 00:18:14 -0500
From: John C Klensin <john-ietf@jck.com>
To: Stephen Farrell <stephen.farrell@cs.tcd.ie>, iesg@ietf.org
Subject: Re: Agenda, security, and monitoring
Message-ID: <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com>
In-Reply-To: <52EDAD15.6060504@cs.tcd.ie>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie>
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
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, 02 Feb 2014 05:18:30 -0000

--On Sunday, February 02, 2014 02:27 +0000 Stephen Farrell
<stephen.farrell@cs.tcd.ie> wrote:

>...
>> If we are really serious about preventing monitoring,
>> especially at the application layer and doing so within our
>> own community as an  example, this should be obvious.
> 
> I disagree as it happens. Putting an emphasis on identification
> and authentication seems backwards to me. First, we ought try
> provide means to communicate that resist PM, (which requires
> confidentiality and can use some help from Mr. Data
> Minimisation:-) and after we have that nicely unerway, we can
> then see how to establish various kinds of authentication.
> 
> I don't believe that starting from authentication is at all
> the right approach.
> 
> But, I might be wrong, so happy to see people signing keys.
> 
>> Indeed, it might be interesting as a first step to fix the
>> IETF list so it wouldn't accept unsigned messages.
> 
> Wasn't that debated a few months ago. I don't think that
> would be at all useful for anyone.

Sorry, I wasn't clear.  At least in this particular context, I
have no interest at all in authentication.  My interest was in a
demonstration of the ability to handle encryption.  For S/MIME
and PGP, if I can sign a message, I can decrypt a message that
is sent to me.  From a privacy or surveillance resistance
standpoint, the latter, and a way to demonstration That
capability, are important.  Authentication is irrelevant and, as
you say, not helpful in that context.

   john


From paf@frobbit.se  Sun Feb  2 00:48:36 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 2A2A01A0090; Sun,  2 Feb 2014 00:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.786
X-Spam-Level: 
X-Spam-Status: No, score=-1.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.535, 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 mxzc_ptewFI5; Sun,  2 Feb 2014 00:48:35 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 08C941A008A; Sun,  2 Feb 2014 00:48:35 -0800 (PST)
Received: from ix-2.local (unknown [IPv6:2a02:80:3ffc:0:9cd4:1178:4e7c:3d63]) by mail.frobbit.se (Postfix) with ESMTPSA id EE61F20217; Sun,  2 Feb 2014 09:48:29 +0100 (CET)
Message-ID: <52EE065B.1050707@frobbit.se>
Date: Sun, 02 Feb 2014 09:48:27 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>, iesg@ietf.org
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net>
In-Reply-To: <52ED8496.6000006@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="emKoVTJ9g1UrpTcGpFBonFahhULIWskvt"
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, 02 Feb 2014 08:48:36 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--emKoVTJ9g1UrpTcGpFBonFahhULIWskvt
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-02 00:34, Dave Crocker wrote:
> 1. It has demonstrated unacceptable usability for average users.

At last my view and experience is that latest Enigmail and MacGPG is
making it usable.

The key exchange is hard, but works really well in Enigmail+Thunderbird,
as key management is directly from mail read/compose window. Not in a
separate application.

> 2. It does not protect the header or the envelope, to the extent anyone=

> cares about divulging the Subject or other message meta-data...

Correct. It only protects what it protects.

> 3. It's packaging in the body is ugly. (See #1)

Huh?

It is using multipart/signed just like other security mechanisms that
protects the body.

   Patrik



--emKoVTJ9g1UrpTcGpFBonFahhULIWskvt
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.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFS7gZdrMabGguI180RAtyVAJ966Gfcnz7XDJtXCbP5u3F0uhKPEwCfRTAW
TkrHtsw8OCQ/v3xLmHRK1zU=
=IOS3
-----END PGP SIGNATURE-----

--emKoVTJ9g1UrpTcGpFBonFahhULIWskvt--

From dhc@dcrocker.net  Sun Feb  2 00:54: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 5A59A1A0092; Sun,  2 Feb 2014 00:54:44 -0800 (PST)
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 I9-ptqivwUy9; Sun,  2 Feb 2014 00:54:43 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3AC9C1A0091; Sun,  2 Feb 2014 00:54:43 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s128sWvR007433 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sun, 2 Feb 2014 00:54:35 -0800
Message-ID: <52EE07AC.2020701@dcrocker.net>
Date: Sun, 02 Feb 2014 00:54:04 -0800
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.2.0
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>, John C Klensin <john-ietf@jck.com>, iesg@ietf.org
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <52EE065B.1050707@frobbit.se>
In-Reply-To: <52EE065B.1050707@frobbit.se>
Content-Type: text/plain; charset=ISO-8859-1; 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]); Sun, 02 Feb 2014 00:54:35 -0800 (PST)
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, 02 Feb 2014 08:54:44 -0000

On 2/2/2014 12:48 AM, Patrik Fältström wrote:
> On 2014-02-02 00:34, Dave Crocker wrote:
>> 1. It has demonstrated unacceptable usability for average users.
>
> At last my view and experience is that latest Enigmail and MacGPG is
> making it usable.
>
> The key exchange is hard, but works really well in Enigmail+Thunderbird,
> as key management is directly from mail read/compose window. Not in a
> separate application.

You think that's a system that can and will be convenient and used by 
the mass market???

So why isn't it already?


>> 2. It does not protect the header or the envelope, to the extent anyone
>> cares about divulging the Subject or other message meta-data...
>
> Correct. It only protects what it protects.
>
>> 3. It's packaging in the body is ugly. (See #1)
>
> Huh?
>
> It is using multipart/signed just like other security mechanisms that
> protects the body.

Take a look at the message that John posted, opening this thread.  That 
some systems use multipart/signed is fine, but it's not what's most 
common for PGP.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From paf@frobbit.se  Sun Feb  2 01:00:23 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 211A71A0096; Sun,  2 Feb 2014 01:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.786
X-Spam-Level: 
X-Spam-Status: No, score=-1.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.535, 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 80X6-XPpVc5H; Sun,  2 Feb 2014 01:00:22 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3F81A0095; Sun,  2 Feb 2014 01:00:22 -0800 (PST)
Received: from ix-2.local (unknown [IPv6:2a02:80:3ffc:0:9cd4:1178:4e7c:3d63]) by mail.frobbit.se (Postfix) with ESMTPSA id 45CC520296; Sun,  2 Feb 2014 10:00:17 +0100 (CET)
Message-ID: <52EE0921.40005@frobbit.se>
Date: Sun, 02 Feb 2014 10:00:17 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, John C Klensin <john-ietf@jck.com>, iesg@ietf.org
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <52EE065B.1050707@frobbit.se> <52EE07AC.2020701@dcrocker.net>
In-Reply-To: <52EE07AC.2020701@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="N7OnNSRO7u457hFIDfNswd3XScFsMDiIu"
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, 02 Feb 2014 09:00:23 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--N7OnNSRO7u457hFIDfNswd3XScFsMDiIu
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-02 09:54, Dave Crocker wrote:
> On 2/2/2014 12:48 AM, Patrik F=E4ltstr=F6m wrote:
>> On 2014-02-02 00:34, Dave Crocker wrote:
>>> 1. It has demonstrated unacceptable usability for average users.
>>
>> At last my view and experience is that latest Enigmail and MacGPG is
>> making it usable.
>>
>> The key exchange is hard, but works really well in Enigmail+Thunderbir=
d,
>> as key management is directly from mail read/compose window. Not in a
>> separate application.
>=20
> You think that's a system that can and will be convenient and used by
> the mass market???
>=20
> So why isn't it already?

Several reasons, but specifically two:

A. Even people like we engineers (just look at your message) is unaware
of the good software that is out there

B. It is not supported by Microsoft/Outlook out of the box

>>> 2. It does not protect the header or the envelope, to the extent anyo=
ne
>>> cares about divulging the Subject or other message meta-data...
>>
>> Correct. It only protects what it protects.
>>
>>> 3. It's packaging in the body is ugly. (See #1)
>>
>> Huh?
>>
>> It is using multipart/signed just like other security mechanisms that
>> protects the body.
>=20
> Take a look at the message that John posted, opening this thread.  That=

> some systems use multipart/signed is fine, but it's not what's most
> common for PGP.

I disagree.

   Patrik



--N7OnNSRO7u457hFIDfNswd3XScFsMDiIu
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.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFS7gkhrMabGguI180RAtSQAKCN7GcglpyC4JypLzckeYErmGrBIwCfSofS
OC31RAwyqIEEOfDJh7hz5JA=
=Kbg8
-----END PGP SIGNATURE-----

--N7OnNSRO7u457hFIDfNswd3XScFsMDiIu--

From dhc@dcrocker.net  Sun Feb  2 01:17: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 846481A0097 for <ietf@ietfa.amsl.com>; Sun,  2 Feb 2014 01:17:30 -0800 (PST)
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 QMMAP7vARMIx for <ietf@ietfa.amsl.com>; Sun,  2 Feb 2014 01:17:28 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA141A0096 for <ietf@ietf.org>; Sun,  2 Feb 2014 01:17:28 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s129HKGH007614 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Sun, 2 Feb 2014 01:17:24 -0800
Message-ID: <52EE0D04.6050509@dcrocker.net>
Date: Sun, 02 Feb 2014 01:16:52 -0800
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.2.0
MIME-Version: 1.0
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <3EAA52D5BE6B9B73B3B1E716@JcK-HP8200.jck.com>
In-Reply-To: <3EAA52D5BE6B9B73B3B1E716@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, 02 Feb 2014 01:17:24 -0800 (PST)
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, 02 Feb 2014 09:17:30 -0000

On 2/1/2014 4:35 PM, John C Klensin wrote:
> --On Saturday, February 01, 2014 15:34 -0800 Dave Crocker
> <dhc@dcrocker.net> wrote:
>> On 2/1/2014 3:18 PM, John C Klensin wrote:
>>> (1) Other than a probably-appropriate level of general paranoia,
>>> do we have any reason to believe that PGP (Symantec and/or GNUPG
>>> versions) has been sufficiently compromised to not provide a good
>>> defense against either pervasive surveillance or general
>>> snooping?
>>
>> 1. It has demonstrated unacceptable usability for average
>> users.
>
> Agree completely, but that wasn't the question.

Yeah, effectively it was.  You suggested activities such as PGP 
key-signing.  My point is that that has nothing to do with providing 
meaningful PM protections for the Internet.

You almost asked whether the PGP/SMIME model and algorithms were still 
believed to be sufficient.  That, of course, would be useful background 
for meaningful technical work on PM, but that's a very focused and very 
brief question and not at all the path the rest of your message went down.


> Noting the email systems with which we are both familiar as
> examples and the history of attacks (whether technical or
> legal-judicial) on intermediate systems (relays and otherwise),
> if we are asked today what our best end to end technology
> options are, those are it.

Being able to demonstrate that we know how to encrypt the message body 
is fine, but in terms of current concerns over PM and the nature of what 
needs to be done, it seems like a point working very hard for 
triviality, along with being able to say that we can send data reliably. 
  Essential, but not noteworthy.


>     For the first, I suspect that there are a lot
> more people in the world who care enough to go to extra trouble
> than was the case a year or so ago.  We could debate whether "a
> lot" is actually large enough to be a significant number, but

It isn't, but more significantly, it doesn't matter.

We have plenty of experience with events at the level of catastrophes 
that then produced no meaningful change in operator or user behavior. 
In other words, the lesson was not learned.  I'll point to the study 
done a year after the Morris Worm as an early example, in a far more 
tech-savvy Internet operations world:  No significant change in server 
protection.


>> 2. It does not protect the header or the envelope, to the
>> extent anyone cares about divulging the Subject or other
>> message meta-data...
>
> Extending from and building on my comments above, is your
> preferred alternative "sending email is hopeless;

No.

More specifically, my preferred alternative is that we focus on creating 
solutions, rather than worrying about spending energy on mechanisms that 
have already failed to scale.

I've more than once registered this preferred alternative generally, 
which is to look at this topic in an integrated fashion, identify 
system-level requirements and system-level barriers to adoption.

And since earlier this evening a private exchange prompted my fleshing 
this out a bit, here's what I mean, in more detail:

    1.  What information needs to be protected?

      "Raw payload" is the least interesting answer.  Not that it's 
wrong, but it's the most obvious.  Saying PGP is a version of saying raw 
payload.  That's why I pushed back so strongly on that.

     I'd expect the interesting discussion to be about

        a)  Describing information that is used for identity correlation

        b)  Packaging/header/envelope protection

        c)  Traffic/activity analysis protection

    2.  What are the broad strokes of mechanism(s) that will protect 
what needs protecting?

     This is somewhere between a conceptual requirements statement and a 
functional spec.  It's most certainly not a detailed statement.  The 
intent is to define the solution space, to guide the specification effort.


    3.  On the premise that we already have extensive experience with 
all of the relevant component technologies (keys, key management, 
encryption, authentication, etc., etc.) then what appears to be the 
major barriers for large-scale solutions?  In the realm of key 
management, it well might be that we do /not/ have sufficient experience 
with usable solutions.


    4.  How do we overcome #3?


That's probably a good, high-level start.  If we make progress on these, 
we will have quite a bit of guidance for detailed design efforts, or at 
least experiments.



>> 3. It's packaging in the body is ugly. (See #1)
>
> Yep.  And if one didn't want to tolerate ugly in order to get
> more privacy, then one doesn't need the privacy enough.  See
> above.

When I constantly  comment that the IETF needs to stay away from making 
assertions that touch on usability topics, it's always nice to get such 
solid demonstrations of why.

Such dismissals of mass-market adoption and use realities really does 
more to show the IETF community's failings, far more than end users'.


>> However any focus on PGP or S/MIME in their current forms will
>> be a distraction that well might seduce the IETF community
>> into thinking it's doing something useful for the Internet
>> that actually isn't.
>
> Because of my concerns about compromised mail system operators,
> relay servers and even submission and delivery servers, plus the
> vast majority of users who do not control the domains they user
> for email, I could say much the same thing about all of the work
> that is going on about hop-by-hop methods, especially

Yup.


>   So, for me, the choice is
> between deploying a variety of mechanisms, understanding and
> being clear about the applicability and limitations of each, and
> saying things that amount to "hopeless".

You appear to be applying a constraint of having to work with what 
exists.  If we had sufficient solutions available that would be fine, 
but we already know we don't.

So wouldn't it be really nice if there were a savvy engineering 
community that might actually focus on developing /new/ techniques to 
deal with PM?

Where might we look for such a group?


> All of that said, I wasn't proposing a "focus on PGP or S/MIME"
> or anything like it.  I was proposing a convenience and enabler
> for those members of our community who felt like using those

Oh.  You weren't concerned with the larger Internet.  You just wanted 
IETF folk to feel more secure (when talking with other IETF folk?)


> methods or, if the techniques we have standardized are actually
> defective, that we either fix them or, depending on the level of
> risk, either generate Applicability Statements or deprecate the

Glad to hear that we can resolve the considerable concerns about PM with 
some applicability statements and no actual engineering.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From abdussalambaryun@gmail.com  Sun Feb  2 02:27:32 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 87C8C1A00A6 for <ietf@ietfa.amsl.com>; Sun,  2 Feb 2014 02:27:32 -0800 (PST)
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 frVGrf5yqX80 for <ietf@ietfa.amsl.com>; Sun,  2 Feb 2014 02:27:29 -0800 (PST)
Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) by ietfa.amsl.com (Postfix) with ESMTP id B14E01A009E for <ietf@ietf.org>; Sun,  2 Feb 2014 02:27:29 -0800 (PST)
Received: by mail-yk0-f177.google.com with SMTP id 19so33164689ykq.8 for <ietf@ietf.org>; Sun, 02 Feb 2014 02:27:25 -0800 (PST)
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=usj0jTrb/uxb+IEyAR6gpnNNwFD6okinB2hXxvLHtYE=; b=eBWdghuvDjxnJT+NbVsnxCKd/PMVUKy20OgupvIZOHNIXUedh0qepsK/fusKuGbsdL UmktvChpzxAB1C4Wr6fqUWrJD/BjYjfso6fiD4YaqrZxXEhVobvCC8gH9fyX6UhZJ9CF LmjW76O3ybe6uvlSIFryKJlBzSM/RpQQ5xYoJ67kD0vLkDffHsvp36oRpFAUhVxmmKVC xwmtucnd1PUTuqrZeXmX6SiQVHDmYrFE8dnVWJHKYpbY4gjQfdUl7MrGiMDs4sGqpOSI yTSY9uIHmMKms2lh2u89Px4f9eUzZV1xe+2FmayorxrsFU1t9Tp90uD1xVs7iaiZpI/1 Sjog==
MIME-Version: 1.0
X-Received: by 10.236.139.234 with SMTP id c70mr27888579yhj.26.1391336845211;  Sun, 02 Feb 2014 02:27:25 -0800 (PST)
Received: by 10.170.220.213 with HTTP; Sun, 2 Feb 2014 02:27:25 -0800 (PST)
In-Reply-To: <52ED31BB.8080906@isdg.net>
References: <52E80FA9.5020704@gmail.com> <52E826A3.3040605@isdg.net> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40245F28@GLKXM0002V.GREENLNK.net> <52ED31BB.8080906@isdg.net>
Date: Sun, 2 Feb 2014 11:27:25 +0100
Message-ID: <CADnDZ8_uFMP0ewXqsF=Fc2Z55Zntcv0O9-DR3Y22ReXW31kx9Q@mail.gmail.com>
Subject: Re: Make it a Proposed Method rather than Proposed Standard [Re: When is an idea a good idea?]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Hector Santos <hsantos@isdg.net>
Content-Type: multipart/alternative; boundary=485b397dceab6bfeee04f169da4f
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: Sun, 02 Feb 2014 10:27:32 -0000

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

On Saturday, February 1, 2014, Hector Santos wrote:

> Hi Chris,
>
> How does the IETF feel about having "multiple standards" of the same
> thing, in other words, redundancy?


How many? It depends on the use case, so for one use case the IETF SHOULD
have a one decision proposal.


> I don't think we generally want that, and I don't think we want "bad"
> ideas becoming standards because it becomes harder and costly to undue.


There may be bad ideas backed by experts and evaluated good just because
presented by experts or known persons.

>
> However, we do need to document them too as well to allow people to try
> them out.  So if the authors don't wish to make it, EXPERIMENTAL, BCP or
> INFORMATIONAL,  a better option is to further it as a Proposed Method
> rather than get bounce around, wasting so much time as a Proposed Standard
> where Rough Consensus decisions is more problematic than ever before.


IMHO making it start as method directly may be allowed only in the general
area. For other areas any new method should start as informational and
passed then updated to method proposal. Any informational method need an
approved standard pointed to.


> Keep in mind there is also the "politics" part of it too of getting things
> pushed and supported. Once a proposed standard starts, you might as well
> "forget" about other possible solutions.  They might not be allowed.
>  However, I am seen them also used to weaken and even destroy PS efforts -
> raises doubt, etc, which is good when it shouldn't had been a PS in the
> first place.


We SHOULD solve the politics problem in IETF because it is a BAD behaviour
as you mentioned its influences. The general area should solve that by
new BCPs.


> A PM would be easier I feel to pursue with less "politics," IMO.  A lesser
> peer review process. Experimental and informational are too weak.


IMHO, They are not weak, that is part of politics may be as well.


>   If we took "Best" out of BCP, then perhaps a CP would be closer to a PM
> or Internet Method (IM).  It just isn't the only, close-ended standard.


Agree but it needs some new process procedure.


>
> Perhaps it should be made clearer that a BCP or Proposed Standard is not
> absolute in the IETF as far as solutions are concern.


Disagree.


> The suggestion is to provide a way to document strong multiple solutions
> which may not necessary the "standard" or "best" solution.


You may mean strong possible multiple solutions related to possible
applicability statements.

no solution method proposed only if it is related to an
IETF standard or BCP. Each method should need informational document
related passed the updated to method.

>
> Personally, I would write more documents, get involved more with PM
> documents. PS are too hard. Too stressful and time consuming and the
> others, like BCP is just the wrong category. Maybe take away the B from CP
> and we got it. :)


Yes agree,


> Thanks for your feedback.
>
> --
> HLS
>
> On 1/29/2014 5:29 AM, Dearlove, Christopher (UK) wrote:
>
>> I'm not sure more categories is what we want.
>>
>> I have observed all of the following (not at the same time, though some
>> were) from people not familiar with the IETF and RFCs, although invested in
>> or using RFCs:
>> - Assuming that all RFCs are standards.
>> - Assuming that only Standards matter, that Proposed Standards and Draft
>> standards aren't important.
>> - Assuming that Draft Standard is a category below Proposed Standard.
>> - Recognising that there are standards and not-standards, but not
>> distinguishing in any way between Standard, Draft Standard and Proposed
>> Standard (calling all of them Standards).
>> - Just plain confused.
>>
>> (And the concept of BCP is probably completely unknown to anyone thinking
>> any of the above.)
>>
>> Another category isn't going to help here.
>>
>>
>
>
>

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

<br><br>On Saturday, February 1, 2014, Hector Santos  wrote:<br><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex">Hi Chris,<br>
<br>
How does the IETF feel about having &quot;multiple standards&quot; of the s=
ame thing, in other words, redundancy?</blockquote><div><br></div><div>How =
many? It depends on the use case, so for one use case the IETF SHOULD have =
a one decision proposal.=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">
<br>
I don&#39;t think we generally want that, and I don&#39;t think we want &qu=
ot;bad&quot; ideas becoming standards because it becomes harder and costly =
to undue.</blockquote><div><br></div><div>There may be bad ideas backed by =
experts and evaluated good just because presented by experts or known perso=
ns.=A0=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
However, we do need to document them too as well to allow people to try the=
m out. =A0So if the authors don&#39;t wish to make it, EXPERIMENTAL, BCP or=
 INFORMATIONAL, =A0a better option is to further it as a Proposed Method ra=
ther than get bounce around, wasting so much time as a Proposed Standard wh=
ere Rough Consensus decisions is more problematic than ever before. =A0</bl=
ockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"></blockquote><div><br></div><div>IMHO making=
 it start as method directly may be allowed only in the general area. For o=
ther areas any new method should start as informational and passed then upd=
ated to method proposal. Any informational method need an approved standard=
 pointed to.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Keep in mind there is also the=
 &quot;politics&quot; part of it too of getting things pushed and supported=
. Once a proposed standard starts, you might as well &quot;forget&quot; abo=
ut other possible solutions. =A0They might not be allowed. =A0However, I am=
 seen them also used to weaken and even destroy PS efforts - raises doubt, =
etc, which is good when it shouldn&#39;t had been a PS in the first place.<=
/blockquote>
<div><br></div><div>We SHOULD solve the politics problem in IETF because it=
 is a BAD behaviour as you mentioned its influences. The general area shoul=
d solve that by new=A0BCPs.=A0=A0=A0</div><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

<br>
A PM would be easier I feel to pursue with less &quot;politics,&quot; IMO. =
=A0A lesser peer review process. Experimental and informational are too wea=
k.</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
</blockquote><div><br></div><div>IMHO,=A0They are not weak, that is part of=
 politics may be as well.=A0</div><div>=A0</div><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">=A0=A0If we took &quot;Best&quot; out of BCP, then perhaps a CP would b=
e closer to a PM or Internet Method (IM). =A0It just isn&#39;t the only, cl=
ose-ended standard.</blockquote>
<div><br></div><div>Agree but it needs some new=A0process procedure.=A0</di=
v><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
<br>
Perhaps it should be made clearer that a BCP or Proposed Standard is not ab=
solute in the IETF as far as solutions are concern. =A0</blockquote><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">
</blockquote><div><br></div><div>Disagree.=A0</div><div>=A0</div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">The suggestion is to provide a way to document strong =
multiple solutions which may not necessary the &quot;standard&quot; or &quo=
t;best&quot; solution.</blockquote>
<div><br></div><div>You may mean strong possible multiple solutions related=
 to possible applicability statements.=A0=A0</div><div><br></div><div>no so=
lution=A0method proposed=A0only if it is=A0related to an IETF=A0standard=A0=
or=A0BCP. Each method should need informational document related=A0passed t=
he updated to method.=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Personally, I would write more documents, get involved more with PM documen=
ts. PS are too hard. Too stressful and time consuming and the others, like =
BCP is just the wrong category. Maybe take away the B from CP and we got it=
. :)</blockquote>
<div><br></div><div>Yes agree,=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">
<br>
Thanks for your feedback.<br>
<br>
-- <br>
HLS<br>
<br>
On 1/29/2014 5:29 AM, Dearlove, Christopher (UK) wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
I&#39;m not sure more categories is what we want.<br>
<br>
I have observed all of the following (not at the same time, though some wer=
e) from people not familiar with the IETF and RFCs, although invested in or=
 using RFCs:<br>
- Assuming that all RFCs are standards.<br>
- Assuming that only Standards matter, that Proposed Standards and Draft st=
andards aren&#39;t important.<br>
- Assuming that Draft Standard is a category below Proposed Standard.<br>
- Recognising that there are standards and not-standards, but not distingui=
shing in any way between Standard, Draft Standard and Proposed Standard (ca=
lling all of them Standards).<br>
- Just plain confused.<br>
<br>
(And the concept of BCP is probably completely unknown to anyone thinking a=
ny of the above.)<br>
<br>
Another category isn&#39;t going to help here.<br>
<br>
</blockquote>
<br>
<br>
<br>
</blockquote>

--485b397dceab6bfeee04f169da4f--

From joe@cdt.org  Sun Feb  2 05:55:03 2014
Return-Path: <joe@cdt.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 E4A201A00E6; Sun,  2 Feb 2014 05:55:03 -0800 (PST)
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 1X0mkoI0CkYl; Sun,  2 Feb 2014 05:55:02 -0800 (PST)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id C2F991A00DA; Sun,  2 Feb 2014 05:55:01 -0800 (PST)
X-Footer: Y2R0Lm9yZw==
Received: from [10.0.1.133] ([173.66.171.101]) (authenticated user jhall@cdt.org) by mail.maclaboratory.net (using TLSv1 with cipher AES128-SHA (128 bits)); Sun, 2 Feb 2014 08:54:55 -0500
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com>
Mime-Version: 1.0 (1.0)
In-Reply-To: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <D2E0F924-2661-48C1-9FC5-2205AF9BFF2F@cdt.org>
X-Mailer: iPad Mail (11B554a)
From: Joseph Lorenzo Hall <joe@cdt.org>
Subject: Re: Agenda, security, and monitoring
Date: Sun, 2 Feb 2014 08:54:58 -0500
To: John C Klensin <john-ietf@jck.com>
Cc: "iesg@ietf.org" <iesg@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: Sun, 02 Feb 2014 13:55:04 -0000

> On Feb 1, 2014, at 18:18, John C Klensin <john-ietf@jck.com> wrote:
>=20
> Indeed, it might be interesting as a first
> step to fix
> the IETF list so it wouldn't accept unsigned messages.

I don't think this is a good idea.

First, it would raise technical barriers to participation; now one would hav=
e to install software other than email software, configure it correctly and p=
oint ietf to the signing key (no?)... (unless the list doesn't do an actual s=
ig check, in which case what's the point?). Second, while I and others are c=
omfortable with a default-sign policy, I know many more people that are very=
 picky with non-repudiability and things they cryptographically sign. Finall=
y, I'm not comfortable keeping keys on mobile devices (signing or otherwise)=
, which would mean emails I send from those devices like this one will not b=
e signed.

Am I missing something? I can imagine many of us have longer keys since the l=
ast IETF, so I'd definitely be interested in a signing event.

best, Joe

--
Joseph Lorenzo Hall
Chief Technologist
Center for Democracy & Technology
https://www.cdt.org/=


From hallam@gmail.com  Sun Feb  2 07:34:54 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 0EBD11A00E4; Sun,  2 Feb 2014 07:34:54 -0800 (PST)
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_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, LOTS_OF_MONEY=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 wq8P6ik11BtZ; Sun,  2 Feb 2014 07:34:51 -0800 (PST)
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 73B861A00D9; Sun,  2 Feb 2014 07:34:50 -0800 (PST)
Received: by mail-la0-f44.google.com with SMTP id hr13so1064118lab.31 for <multiple recipients>; Sun, 02 Feb 2014 07:34:45 -0800 (PST)
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=RKmJ+ke/O52ORii1zpz5dlnUXGtjnm/Wl29JEIUCCZc=; b=f8h/l4ZzfMGPBUIpb2cwd4Y1AWKClUsQBcLxVO7gxTDEe/TRwqb4Fexce3MlOasFCB bxaTIYqW6PNW6uDHS+YA0ruW6ulO6zM3nkEVEZrHcwe8awk5eGOBzzfygef7Guum8Fu7 24e/YIZZH/onFrINfLNXQIV8sBRBVe+sOTwLGrovvJzz9z382RA1/qJV/gAwqG3XVCYy XTDSoCJlbeTpB6TjqMxqflrjdk01iyHSvU6J/Qpxi0Oz9F1TyTTFdydQj3HrPX4LVHDn JKsuLHn0TagI8GQmz9gW0tjUJs2QsV6DSjHeug4qzEJD3UvscmKDduJ+FczAKYUYOZvC JLDg==
MIME-Version: 1.0
X-Received: by 10.152.161.234 with SMTP id xv10mr1336130lab.41.1391355285334;  Sun, 02 Feb 2014 07:34:45 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Sun, 2 Feb 2014 07:34:45 -0800 (PST)
In-Reply-To: <52EE07AC.2020701@dcrocker.net>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <52EE065B.1050707@frobbit.se> <52EE07AC.2020701@dcrocker.net>
Date: Sun, 2 Feb 2014 10:34:45 -0500
Message-ID: <CAMm+LwjF_E7q1vbef6-sQ9wXYbtBsJEgny768iv4aNh1e5SSmw@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=001a11345a0889f09f04f16e25c1
Cc: John C Klensin <john-ietf@jck.com>, IETF Discussion Mailing List <ietf@ietf.org>, "iesg@ietf.org" <iesg@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: Sun, 02 Feb 2014 15:34:54 -0000

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

On Sun, Feb 2, 2014 at 3:54 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 2/2/2014 12:48 AM, Patrik F=E4ltstr=F6m wrote:
>
>> On 2014-02-02 00:34, Dave Crocker wrote:
>>
>>> 1. It has demonstrated unacceptable usability for average users.
>>>
>>
>> At last my view and experience is that latest Enigmail and MacGPG is
>> making it usable.
>>
>> The key exchange is hard, but works really well in Enigmail+Thunderbird,
>> as key management is directly from mail read/compose window. Not in a
>> separate application.
>>
>
> You think that's a system that can and will be convenient and used by the
> mass market???
>
> So why isn't it already?


I address that in my video. Sorry, its not in text yet, but the argument is
not really part of the technical specifications.

The part that you don't state by name but imply is 'what is the business
model'. We are talking about a multi-million dollar change to the email
infrastructure. That is only justified if we can show a multi-billion
dollar return on the investment.

I think that there is such a return. If my bank, my doctor, my brokerage
can send mail and be assured that the transport is confidential end to end,
they can use email in more ways. SSL made Web commerce possible and added
roughly five trillion dollars to global GDP according to one estimate.
Email security can make Internet commerce better and simpler and sustain
that growth. Even if the additional benefits from making the other Internet
killer application secure are 1% of the Web benefits, that is a lot of
potential.


I see S/MIME and PGP as being 95% right respectively. The problem is that
Internet applications don't take off if they are 'pretty good' back in 1992
they had to be extremely good. And now they have to be exceptionally good.

Most of us have a box full of smartphones we bought before the iPhone came
out. The Palm Treo, HP iPaq and the Rim pager. They were all functional but
none of them had the real web, they were all walled gardens. Remember that
before the iphone the industry was flushing a billion dollars a year down
the WAP toilet in the confused belief that what cell phone users really
wanted was a dumbed down version of the Web with more adverts.

That missing 5% is critical. Specifically any new security scheme has to be
frictionless:

* Key Management: Has to make starting a key set simple and intuitive. The
user cannot be required to perform annual maintenance to replace expired
certificates. Everything has to be completely automatic.

* Multiple devices: It must be really easy to read the encrypted mail on
the many devices real users use today. I have eight machines that I
regularly read email on. Making it possible to read mail on a new device
has to be a one or two clicks affair.

* Transparent: Sending mail securely has to take no more effort that
insecure mail. That means that the mail client (or a proxy) has to decide
whether to send mail in cleartext or encrypted. Which in turn means that
there has to be a mechanism for specifying security policy.


S/MIME already supports an enveloping mode that protects the headers and
metadata. It just isn't fully supported by the deployed base. So there has
to be a way for a receiver to tell the sender what they support. Which is
why we can't use the PGP or S/MIME infrastructure just as is, we need to
add a little policy glue.

Take a look at the message that John posted, opening this thread.  That
> some systems use multipart/signed is fine, but it's not what's most commo=
n
> for PGP.


One of the biggest problems we have is that rather than tell PGP and S/MIME
to use a common packaging format and compete on the trust model, both
groups were told they could go ahead independently (although Jeff Schiller
told me that PGP was "not allowed to develop a PKI" then he rolled his
eyes).

End-to-end email has stalled in part because of the S/MIME vs PGP standards
war. PGP has ended up with all the mindshare, S/MIME has the deployed base.
When I was at VeriSign I had some long discussions with Jon Callas about
what might we do to fix things and come to a common platform. The division
was particularly silly when PGP had one of the best S/MIME platforms in the
market. That effort was overtaken by events and DKIM. The industry didn't
have bandwidth for two email crypto efforts at once. When I left VeriSign I
lobbied PGP inc to start a CA precisely to see if we could start to heal
the rift. Not that it helped. Symantec now own both companies and that
hasn't helped either.


If people want to move forward on this, something that would be very
helpful is for the naysayers to put all their objections into an Internet
Draft. Then those of us looking to solve the problem can go through and see
what we have solved and what is left to do.

I wrote a set of IDs as design documents before starting work on the code:

http://tools.ietf.org/html/draft-hallambaker-prismproof-req-00
http://tools.ietf.org/html/draft-hallambaker-prismproof-key-00
http://tools.ietf.org/html/draft-hallambaker-prismproof-dep-00
http://tools.ietf.org/html/draft-hallambaker-prismproof-trust-00

I now have code that is incomplete but shows proof of concept:
http://sourceforge.net/projects/prismproof/

There are two phases to the code:

Phase One is a scheme that employs a direct trust model and requires no
trusted third parties or infrastructure beyond the existing email
infrastructure and access to a Web Server to publish the Phingerprint
Blocks. This scheme uses the 'strong email address' which is essentially a
PGP fingerprint prepended to a mail address.

Phase Two allows people who have not met directly to exchange secure mail.
This scheme allows people to use their normal email address without any
visible cryptogunk. It necessarily relies on some form of infrastructure
but does not force a peer-to-peer or hierarchical model.

Right now the proxy can generate and manage keys, accept outbound mail,
encrypt it and forward it to the actual outbound mail server. I hope to get
the code to the point where it can make the decision to encrypt or not and
pull keys from a web server before London.


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

--001a11345a0889f09f04f16e25c1
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 S=
un, Feb 2, 2014 at 3:54 AM, Dave Crocker <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;</span> w=
rote:<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 class=3D"im">On 2/2/2014 12:48 AM, Patrik F=E4ltstr=
=F6m 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">
On 2014-02-02 00:34, Dave Crocker 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">
1. It has demonstrated unacceptable usability for average users.<br>
</blockquote>
<br>
At last my view and experience is that latest Enigmail and MacGPG is<br>
making it usable.<br>
<br>
The key exchange is hard, but works really well in Enigmail+Thunderbird,<br=
>
as key management is directly from mail read/compose window. Not in a<br>
separate application.<br>
</blockquote>
<br></div>
You think that&#39;s a system that can and will be convenient and used by t=
he mass market???<br>
<br>
So why isn&#39;t it already?</blockquote><div><br></div><div>I address that=
 in my video. Sorry, its not in text yet, but the argument is not really pa=
rt of the technical specifications.</div><div><br></div><div>The part that =
you don&#39;t state by name but imply is &#39;what is the business model&#3=
9;. We are talking about a multi-million dollar change to the email infrast=
ructure. That is only justified if we can show a multi-billion dollar retur=
n on the investment.</div>
<div><br></div><div>I think that there is such a return. If my bank, my doc=
tor, my brokerage can send mail and be assured that the transport is confid=
ential end to end, they can use email in more ways. SSL made Web commerce p=
ossible and added roughly five trillion dollars to global GDP according to =
one estimate. Email security can make Internet commerce better and simpler =
and sustain that growth. Even if the additional benefits from making the ot=
her Internet killer application secure are 1% of the Web benefits, that is =
a lot of potential.</div>
<div><br></div><div><br></div><div>I see S/MIME and PGP as being 95% right =
respectively. The problem is that Internet applications don&#39;t take off =
if they are &#39;pretty good&#39; back in 1992 they had to be extremely goo=
d. And now they have to be exceptionally good.</div>
<div><br></div><div>Most of us have a box full of smartphones we bought bef=
ore the iPhone came out. The Palm Treo, HP iPaq and the Rim pager. They wer=
e all functional but none of them had the real web, they were all walled ga=
rdens. Remember that before the iphone the industry was flushing a billion =
dollars a year down the WAP toilet in the confused belief that what cell ph=
one users really wanted was a dumbed down version of the Web with more adve=
rts.</div>
<div><br></div><div>That missing 5% is critical. Specifically any new secur=
ity scheme has to be frictionless:</div><div><br></div><div>* Key Managemen=
t: Has to make starting a key set simple and intuitive. The user cannot be =
required to perform annual maintenance to replace expired certificates. Eve=
rything has to be completely automatic.</div>
<div><br></div><div>* Multiple devices: It must be really easy to read the =
encrypted mail on the many devices real users use today. I have eight machi=
nes that I regularly read email on. Making it possible to read mail on a ne=
w device has to be a one or two clicks affair.</div>
<div><br></div><div>* Transparent: Sending mail securely has to take no mor=
e effort that insecure mail. That means that the mail client (or a proxy) h=
as to decide whether to send mail in cleartext or encrypted. Which in turn =
means that there has to be a mechanism for specifying security policy.</div=
>
<div><br></div><div><br></div><div>S/MIME already supports an enveloping mo=
de that protects the headers and metadata. It just isn&#39;t fully supporte=
d by the deployed base. So there has to be a way for a receiver to tell the=
 sender what they support. Which is why we can&#39;t use the PGP or S/MIME =
infrastructure just as is, we need to add a little policy glue.</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
Take a look at the message that John posted, opening this thread. =A0That s=
ome systems use multipart/signed is fine, but it&#39;s not what&#39;s most =
common for PGP.</blockquote></div><div class=3D"gmail_extra"><br></div>One =
of the biggest problems we have is that rather than tell PGP and S/MIME to =
use a common packaging format and compete on the trust model, both groups w=
ere told they could go ahead independently (although Jeff Schiller told me =
that PGP was &quot;not allowed to develop a PKI&quot; then he rolled his ey=
es).</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">End-to-end =
email has stalled in part because of the S/MIME vs PGP standards war. PGP h=
as ended up with all the mindshare, S/MIME has the deployed base. When I wa=
s at VeriSign I had some long discussions with Jon Callas about what might =
we do to fix things and come to a common platform. The division was particu=
larly silly when PGP had one of the best S/MIME platforms in the market. Th=
at effort was overtaken by events and DKIM. The industry didn&#39;t have ba=
ndwidth for two email crypto efforts at once. When I left VeriSign I lobbie=
d PGP inc to start a CA precisely to see if we could start to heal the rift=
. Not that it helped. Symantec now own both companies and that hasn&#39;t h=
elped either.</div>
<div class=3D"gmail_extra"><br clear=3D"all"><div><br></div><div>If people =
want to move forward on this, something that would be very helpful is for t=
he naysayers to put all their objections into an Internet Draft. Then those=
 of us looking to solve the problem can go through and see what we have sol=
ved and what is left to do.</div>
<div><br></div><div>I wrote a set of IDs as design documents before startin=
g work on the code:</div><div><br></div><div><a href=3D"http://tools.ietf.o=
rg/html/draft-hallambaker-prismproof-req-00">http://tools.ietf.org/html/dra=
ft-hallambaker-prismproof-req-00</a><br>
</div><div><a href=3D"http://tools.ietf.org/html/draft-hallambaker-prismpro=
of-key-00">http://tools.ietf.org/html/draft-hallambaker-prismproof-key-00</=
a><br></div><div><a href=3D"http://tools.ietf.org/html/draft-hallambaker-pr=
ismproof-dep-00">http://tools.ietf.org/html/draft-hallambaker-prismproof-de=
p-00</a><br>
</div><div><a href=3D"http://tools.ietf.org/html/draft-hallambaker-prismpro=
of-trust-00">http://tools.ietf.org/html/draft-hallambaker-prismproof-trust-=
00</a><br></div><div><br></div><div>I now have code that is incomplete but =
shows proof of concept:</div>
<div><a href=3D"http://sourceforge.net/projects/prismproof/">http://sourcef=
orge.net/projects/prismproof/</a><br></div><div><br></div><div>There are tw=
o phases to the code:</div><div><br></div><div>Phase One is a scheme that e=
mploys a direct trust model and requires no trusted third parties or infras=
tructure beyond the existing email infrastructure and access to a Web Serve=
r to publish the Phingerprint Blocks. This scheme uses the &#39;strong emai=
l address&#39; which is essentially a PGP fingerprint prepended to a mail a=
ddress.</div>
<div><br></div><div>Phase Two allows people who have not met directly to ex=
change secure mail. This scheme allows people to use their normal email add=
ress without any visible cryptogunk. It necessarily relies on some form of =
infrastructure but does not force a peer-to-peer or hierarchical model.=A0<=
/div>
<div><br></div><div>Right now the proxy can generate and manage keys, accep=
t outbound mail, encrypt it and forward it to the actual outbound mail serv=
er. I hope to get the code to the point where it can make the decision to e=
ncrypt or not and pull keys from a web server before London.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11345a0889f09f04f16e25c1--

From scott.brim@gmail.com  Sun Feb  2 07:55:09 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 330B21A001B; Sun,  2 Feb 2014 07:55:09 -0800 (PST)
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, FH_RANDOM_SURE=0.499, 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 CGPg_ABqf6YJ; Sun,  2 Feb 2014 07:55:08 -0800 (PST)
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 475DD1A0015; Sun,  2 Feb 2014 07:55:08 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id j17so7183560oag.14 for <multiple recipients>; Sun, 02 Feb 2014 07:55:03 -0800 (PST)
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=q6MkHH6SNUK8K8zFF9d3ziVjBpQCiFueD2myLMLH3YU=; b=ctyIY+zZUBZ2XU01Chxtd1DIqqPFPNt3NzXtnKcwYoclQUNxUVI7QQEH3oRsZS6Hvl pc6snCpltnfTOlW6MBWB4ABUh9Nnbib++eFd8XAxf3OXvWYb4a43SNO1L9+SEIKVhTaJ TuyM3vW3E+Xcixis6itN+xb0IH0GG4Ekl2arJ13FwoTJCHq5/fIlcveAG1ODvOEYjz2n 8HcZLFq8jAWJfpBHpZ6j5zrl5x54JuQpojsOrgZsOztfuL15f3heQ++Z3bWE/Qkdz8xh cPbBwvRkXxLpzbYluqctEdgcWYTL1ctSIVmqWgsrUZxEVUn/umQbAYuSRwfDXXw4brGW qFBg==
X-Received: by 10.182.160.102 with SMTP id xj6mr4931699obb.19.1391356503663; Sun, 02 Feb 2014 07:55:03 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Sun, 2 Feb 2014 07:54:43 -0800 (PST)
In-Reply-To: <52EDAF9A.7070706@dcrocker.net>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <m2ob2qs4vy.wl%randy@psg.com> <52EDAF9A.7070706@dcrocker.net>
From: Scott Brim <scott.brim@gmail.com>
Date: Sun, 2 Feb 2014 10:54:43 -0500
Message-ID: <CAPv4CP9LPV1ocCcCtMMTqxqv72n62hKnjXFLbPdWfTiYt0V=AA@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: John C Klensin <john-ietf@jck.com>, IESG <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: Sun, 02 Feb 2014 15:55:09 -0000

Even if it's easy to use (and I'm grateful for enigmail and other
tools), PGP still has the problem of trust dilution.

From Ted.Lemon@nominum.com  Sun Feb  2 08:04: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 BB3161A00F0; Sun,  2 Feb 2014 08:04:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.701
X-Spam-Level: 
X-Spam-Status: No, score=-3.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, 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 rfkHJ5faRwpq; Sun,  2 Feb 2014 08:04:09 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id A01D71A00DC; Sun,  2 Feb 2014 08:04:08 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUu5sdGGnQSdDq+aOdHDz54tlq4nsBu+2@postini.com; Sun, 02 Feb 2014 08:04:04 PST
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 467C41B830E; Sun,  2 Feb 2014 08:04:04 -0800 (PST)
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 0A051190052; Sun,  2 Feb 2014 08:04:04 -0800 (PST)
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; Sun, 2 Feb 2014 08:04:03 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Agenda, security, and monitoring
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAPv4CP9LPV1ocCcCtMMTqxqv72n62hKnjXFLbPdWfTiYt0V=AA@mail.gmail.com>
Date: Sun, 2 Feb 2014 11:04:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <C7D52347-F359-44B4-87D3-1B5974423E31@nominum.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <m2ob2qs4vy.wl%randy@psg.com> <52EDAF9A.7070706@dcrocker.net> <CAPv4CP9LPV1ocCcCtMMTqxqv72n62hKnjXFLbPdWfTiYt0V=AA@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, 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: Sun, 02 Feb 2014 16:04:11 -0000

On Feb 2, 2014, at 10:54 AM, Scott Brim <scott.brim@gmail.com> wrote:
> Even if it's easy to use (and I'm grateful for enigmail and other
> tools), PGP still has the problem of trust dilution.

Trust dilution really isn't a problem for most of the things you'd want =
to use PGP for if it were ubiquitous.   For the cases where it is, like =
bank transactions, stronger key validation is (a) needed and (b) =
possible, because its use cases provide the leverage needed to make it =
work.

The problem with PGP now is that it's _not_ ubiquitous, so the only =
thing you can use it for is use cases where you really need strong =
trust.


From hallam@gmail.com  Sun Feb  2 08:26: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 84AEE1A00A8; Sun,  2 Feb 2014 08:26:30 -0800 (PST)
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_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RANDOM_SURE=0.499, 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 FITT-YNrGVvg; Sun,  2 Feb 2014 08:26:29 -0800 (PST)
Received: from mail-lb0-x230.google.com (mail-lb0-x230.google.com [IPv6:2a00:1450:4010:c04::230]) by ietfa.amsl.com (Postfix) with ESMTP id 876531A0094; Sun,  2 Feb 2014 08:26:28 -0800 (PST)
Received: by mail-lb0-f176.google.com with SMTP id w7so4607128lbi.7 for <multiple recipients>; Sun, 02 Feb 2014 08:26:23 -0800 (PST)
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=tPozem3LnwWTpzfwDPt50/MeUQSe0+N3mt6eMLAGKZM=; b=zK8FGfrK1UAj6PuviSBzz1ck6B2x9ZlZ4RLmzcFoc5qBqux22SKRdbtI3HkgFA1Cgm 1ZRjTZdD2qaAv0p3xYd1rkPZHCoDqly+loZ+M1Vo0OWpRAksq1Mbn32pc63rCEv6Qs7O El8SV+wWi6AMg/wfI+p0lKnmi3jltNlaWlNKEKOPW4WSsogVU1fqw6ZWixZnw6V2Vnw0 /iMj4S6admTwgtPTcFxq7ix6VF07XapWTG+jimrwe0kSlUzER3YMX3YY+k+KMcSpew4I Gx65FuOJ0D0bL/PzSFTJDWEHIgky0ZfIW0AGbZPlta+bGWGi4Tx0rtozYjR+pGmx+KqY Thhw==
MIME-Version: 1.0
X-Received: by 10.152.236.72 with SMTP id us8mr22082725lac.11.1391358383418; Sun, 02 Feb 2014 08:26:23 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Sun, 2 Feb 2014 08:26:23 -0800 (PST)
In-Reply-To: <CAPv4CP9LPV1ocCcCtMMTqxqv72n62hKnjXFLbPdWfTiYt0V=AA@mail.gmail.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <m2ob2qs4vy.wl%randy@psg.com> <52EDAF9A.7070706@dcrocker.net> <CAPv4CP9LPV1ocCcCtMMTqxqv72n62hKnjXFLbPdWfTiYt0V=AA@mail.gmail.com>
Date: Sun, 2 Feb 2014 11:26:23 -0500
Message-ID: <CAMm+LwicWY9J9FRB51tj5i8uEnfZTZ2HKn825S+dePUQ1hF9ow@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: multipart/alternative; boundary=001a1136c0ba32f1df04f16ede80
Cc: John C Klensin <john-ietf@jck.com>, IETF <ietf@ietf.org>, Dave Crocker <dcrocker@bbiw.net>, 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: Sun, 02 Feb 2014 16:26:30 -0000

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

On Sun, Feb 2, 2014 at 10:54 AM, Scott Brim <scott.brim@gmail.com> wrote:

> Even if it's easy to use (and I'm grateful for enigmail and other
> tools), PGP still has the problem of trust dilution.
>

We can change the trust model.

The PGP model does not meet enterprise needs. If I am sending a mail to an
IETF mailing list it is from me. But if my bank manager is sending me an
email it is coming from the bank not me. So there is a requirement for a
hierarchical trust model to support hierarchical organizations.

The S/MIME model requires trusted third parties but does not give them an
opportunity to add a lot of value unless the network of secure mail users
is a lot larger than it is.


PGP and S/MIME both present a false dichotomy between two trust models when
we actually need both. And saying that it is possible to kinda-sorta use
one to support the use of the other really doesn't fly. Its trying to use a
screwdriver as a hammer.

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

--001a1136c0ba32f1df04f16ede80
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 S=
un, Feb 2, 2014 at 10:54 AM, Scott Brim <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:scott.brim@gmail.com" target=3D"_blank">scott.brim@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">Even if it&#39;s easy to use (and I&#39;m gr=
ateful for enigmail and other<br>
tools), PGP still has the problem of trust dilution.<br>
</blockquote></div><br>We can change the trust model.</div><div class=3D"gm=
ail_extra"><br></div><div class=3D"gmail_extra">The PGP model does not meet=
 enterprise needs. If I am sending a mail to an IETF mailing list it is fro=
m me. But if my bank manager is sending me an email it is coming from the b=
ank not me. So there is a requirement for a hierarchical trust model to sup=
port hierarchical organizations.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The S/MIME =
model requires trusted third parties but does not give them an opportunity =
to add a lot of value unless the network of secure mail users is a lot larg=
er than it is.</div>
<div class=3D"gmail_extra"><br clear=3D"all"><div><br></div><div>PGP and S/=
MIME both present a false dichotomy between two trust models when we actual=
ly need both. And saying that it is possible to kinda-sorta use one to supp=
ort the use of the other really doesn&#39;t fly. Its trying to use a screwd=
river as a hammer.=A0</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--001a1136c0ba32f1df04f16ede80--

From prvs=0103a957d5=johnl@taugh.com  Sun Feb  2 12:38:32 2014
Return-Path: <prvs=0103a957d5=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 B55441A0106 for <ietf@ietfa.amsl.com>; Sun,  2 Feb 2014 12:38:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.702
X-Spam-Level: 
X-Spam-Status: No, score=-1.702 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, 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 5inJBza5Rgkt for <ietf@ietfa.amsl.com>; Sun,  2 Feb 2014 12:38:31 -0800 (PST)
Received: from leila.iecc.com (leila6.iecc.com [IPv6:2001:470:1f07:1126:0:4c:6569:6c61]) by ietfa.amsl.com (Postfix) with ESMTP id 98FA11A010C for <ietf@ietf.org>; Sun,  2 Feb 2014 12:38:30 -0800 (PST)
Received: (qmail 33653 invoked from network); 2 Feb 2014 20:38:22 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 2 Feb 2014 20:38: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:user-agent; s=c17c.52eeacbc.k1402; i=johnl-iecc.com@submit.iecc.com; bh=CXPTkGICmp0MJMwN92BO62OWCrqG2b2x2bGgdZBvPMc=; b=SWyS0JFTgXTluY3HYDbjSWozsnF7CSJQJpcvaAZ8J6g7j5KlGhah//fD1gOvIC0RVqeugfB4MGO2Io4kWB5cgl5Ajp6CRUFKE72ETeQXQ0bkqtdeDkdcBOnVFsvP7W+R3FvLQKzOFnl7wgvpxPbF88uQ/DO482o9boud3+CIBXEq6SbZuA9iBc644+Yaooo/kWvV4OsUCoQ39puajoOiVxNKckMPliQuFiqYa25HEHmlHTWIeCru/y1P7uHJzG0v
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:user-agent; s=c17c.52eeacbc.k1402; olt=johnl-iecc.com@submit.iecc.com; bh=CXPTkGICmp0MJMwN92BO62OWCrqG2b2x2bGgdZBvPMc=; b=R+YE/Nkaj6Jhc6sC1ErC9Q2cHgvdi1Q8WxdqIdYdXaP/S9+WFdLeg51cGapRdHVT+Xc7iMYx57FTuRrt8AsaTGUFJ0sAYOGFPDUh9pnbspuDMF6cFGWDHRzCKtQnbN9FNU73UM7fGK4fQYh2lMM9s+JJx/wDjQDOJWmY3zLfpyS31LAZZMCVlGdmHxCbV5t1/o4x1qIMEbeGx4IjgGii9Ibyeb7tmZruouNLau5aCq4iPNNErta1ZJZPcS0gaKVM
Received: from [192.168.80.128] ([24.59.92.2]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 02 Feb 2014 20:38:19 -0000
Date: 2 Feb 2014 15:38:17 -0500
Message-ID: <CF141659.5C0%johnl@taugh.com>
From: "John Levine" <johnl@taugh.com>
To: "Patrik =?ISO-8859-1?B?RuRsdHN0cvZt?=" <paf@frobbit.se>
User-Agent: Microsoft-MacOutlook/14.3.8.130913
Subject: Re: Agenda, security, and monitoring
Thread-Topic: Agenda, security, and monitoring
In-Reply-To: <52EE0921.40005@frobbit.se>
Mime-version: 1.0
Content-type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha512; boundary="B_3474200297_16004353"
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, 02 Feb 2014 20:38:32 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3474200297_16004353
Content-type: text/plain;
	charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable


>A. Even people like we engineers (just look at your message) is unaware
>of the good software that is out there
>
>B. It is not supported by Microsoft/Outlook out of the box

Hi, Outlook 365 user here, signing my mail with S/MIME, no plugins or
anything needed. Where=B9s all the rest of the signed mail?

Of course, getting the fripping cert into Outlook was quite exciting, and
involved sending at least one crash report to Microsoft. Perhaps there are
other issues, some of which may even have been discussed to death over the
past 15 years.

R=B9s,
John

--B_3474200297_16004353
Content-type: application/pkcs7-signature; name="smime.p7s"
Content-transfer-encoding: base64
Content-disposition: attachment;
	filename="smime.p7s"

MIIWhQYJKoZIhvcNAQcCoIIWdjCCFnICAQExDzANBglghkgBZQMEAgMFADALBgkqhkiG9w0B
BwGgghP9MIIGNjCCBR6gAwIBAgIDBi8sMA0GCSqGSIb3DQEBBQUAMIGMMQswCQYDVQQGEwJJ
TDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2Vy
dGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20gQ2xhc3MgMSBQcmltYXJ5IElu
dGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTMwMzE2MTk0NDA3WhcNMTQwMzE4MTIyODM1WjBV
MRkwFwYDVQQNExBxWjF0bjkwbjJHVTg2c3pmMRgwFgYDVQQDDA9qb2hubEB0YXVnaC5jb20x
HjAcBgkqhkiG9w0BCQEWD2pvaG5sQHRhdWdoLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEP
ADCCAQoCggEBAL3v+DRTG7r7Q+kErlwKGENEpGjvbA4jRwOLGiTVdDiF3enbTPO8OzhEylll
atuAG+r0GmIdtfKAhdRg3S7+hIkQfKC9ZPbCtr+9IgFU/N7xJ5mo+v4UFXASOpmSR+i18goG
Ej9nucgUKibvoYC7Xm3YO5DiltrW/d+4w5/SmEVRSJRFNP4rv2/wbsKt2oYNgbBt74PdmZPg
7+VTjUAyxPMfMHYtXKK+6gWP0REcODty16N+uODlNLeikt2kMS61xL1mRx7y4bALtQY2Gwvq
nUnXQ09bfmnRJ2avf8DITRoT1gnf7hQ2Wp0qcjPdd2+3iNUNmjYANHHHIxIAbKfCIqcCAwEA
AaOCAtUwggLRMAkGA1UdEwQCMAAwCwYDVR0PBAQDAgSwMB0GA1UdJQQWMBQGCCsGAQUFBwMC
BggrBgEFBQcDBDAdBgNVHQ4EFgQUi3Y0Q1vDaRmSY5YY2dEi4HtIQr4wHwYDVR0jBBgwFoAU
U3Ltkpzg2ssBXHx+ljVO8tS4UYIwGgYDVR0RBBMwEYEPam9obmxAdGF1Z2guY29tMIIBTAYD
VR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUHAgEWImh0dHA6Ly93
d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHqMCcWIFN0YXJ0Q29t
IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRpZmljYXRlIHdhcyBp
c3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24gcmVxdWlyZW1lbnRz
IG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkgZm9yIHRoZSBpbnRl
bmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcgcGFydHkgb2JsaWdh
dGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRzc2wuY29tL2NydHUx
LWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0dHA6Ly9vY3NwLnN0
YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcwAoY2aHR0cDovL2Fp
YS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2EuY3J0MCMGA1UdEgQc
MBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUFAAOCAQEAjKYHDqcU
SWsz8xAWJ4RhDbkKs13i8gN2vFy+2GsWgCcFe7nA1ZMkB7t+T1BJIb1YCCp8aujfVsR4juhi
v4pncEty61AW7PtL/veZumISb+mX7wB08ky6q6M11KIUeTURXi9KdTnytZZZ5fyO9RXvyTYM
SRw59abs7BaCQ982AioDXUk9xTzSG9r/8SIrm7gfObYiUllJXOejpAnQSt2YAZ8GFfC8RZqT
pcHnWhwurMSJNa7LlwR20SCcCxcti6lbTZtDOTcwVcj0H+9pT5/2miS26mOQw5uP5UsveEfg
il2mxOpVmp+8Zm6nQw5TMRm6TEVldgsYuTjaeLjYDXMCOjCCBjQwggQcoAMCAQICAR4wDQYJ
KoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzAp
BgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxKTAnBgNVBAMTIFN0
YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTA3MTAyNDIxMDE1NVoXDTE3MTAy
NDIxMDE1NVowgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQuMSswKQYD
VQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQDEy9TdGFy
dENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQTCCASIwDQYJKoZI
hvcNAQEBBQADggEPADCCAQoCggEBAMcJg8zOLdgasSmkLhOrlr6KMoOMpohBllVHrdRvEg/q
6r8jR+EK75xCGhR8ToREoqe7zM9/UnC6TS2y9UKTpT1v7RSMzR0t6ndl0TWBuUr/UXBhPk+K
my7bI4yW4urC+y7P3/1/X7U8ocb8VpH/Clt+4iq7nirMcNh6qJR+xjOhV+VHzQMALuGYn5KZ
mc1NbJQYclsGkDxDz2UbFqE2+6vIZoL+jb9x4Pa5gNf1TwSDkOkikZB1xtB4ZqtXThaABSON
dfmv/Z1pua3FYxnCFmdr/+N2JLKutIxMYqQOJebr/f/h5t95m4JgrM3Y/w7YX9d7YAL9jvN4
SydHsU6n65cCAwEAAaOCAa0wggGpMA8GA1UdEwEB/wQFMAMBAf8wDgYDVR0PAQH/BAQDAgEG
MB0GA1UdDgQWBBRTcu2SnODaywFcfH6WNU7y1LhRgjAfBgNVHSMEGDAWgBROC+8apEBbpRdp
hzDKNGhD0EGu8jBmBggrBgEFBQcBAQRaMFgwJwYIKwYBBQUHMAGGG2h0dHA6Ly9vY3NwLnN0
YXJ0c3NsLmNvbS9jYTAtBggrBgEFBQcwAoYhaHR0cDovL3d3dy5zdGFydHNzbC5jb20vc2Zz
Y2EuY3J0MFsGA1UdHwRUMFIwJ6AloCOGIWh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3Nmc2Nh
LmNybDAnoCWgI4YhaHR0cDovL2NybC5zdGFydHNzbC5jb20vc2ZzY2EuY3JsMIGABgNVHSAE
eTB3MHUGCysGAQQBgbU3AQIBMGYwLgYIKwYBBQUHAgEWImh0dHA6Ly93d3cuc3RhcnRzc2wu
Y29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL2lu
dGVybWVkaWF0ZS5wZGYwDQYJKoZIhvcNAQEFBQADggIBAAqDCH14qywGXLhjjF6uHLkjd02h
cdh9hrw+VUsv+q1eeQWB21jWj3kJ96AUlPCoEGZ/ynJNScWy6QMVQjbbMXltUfO4n4bGGdKo
3awPWp61tjAFgraLJgDk+DsSvUD6EowjMTNx25GQgyYJ5RPIzKKR9tQW8gGK+2+RHxkUCTbY
FnL6kl8Ch507rUdPPipJ9CgJFws3kDS3gOS5WFMxcjO5DwKfKSETEPrHh7p5shuuNktvsv6h
xHTLhiMKX893gxdT3XLS9OKmCv87vkINQcNEcIIoFWbP9HORz9v3vQwR4e3ksLc2JZOAFK+s
sS5XMEoznzpihEP0PLc4dCBYjbvSD7kxgDwZ+Aj8Q9PkbvE9sIPP7ON0fz095HdThKjiVJe6
vofq+n6b1NBc8XdrQvBmunwxD5nvtTW4vtN6VY7mUCmxsCieuoBJ9OlqmsVWQvifIYf40dJP
Zkk9YgGTzWLpXDSfLSplbY2LL9C9U0ptvjcDjefLTvqSFc7tw1sEhF0n/qpA2r0GpvkLRDmc
SwVyPvmjFBGqUp/pNy8ZuPGQmHwFi2/14+xeSUDG2bwnsYJQG2EdJCB6luQ57GEnTA/yKZST
KI8dDQa8Sd3zfXb19mOgSF0bBdXbuKhEpuP9wirslFe6fQ1t5j5R0xi72MZ8ikMu1RQZKCyD
bMwazlHiMIIHhzCCBW+gAwIBAgIBLTANBgkqhkiG9w0BAQsFADB9MQswCQYDVQQGEwJJTDEW
MBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlm
aWNhdGUgU2lnbmluZzEpMCcGA1UEAxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3Jp
dHkwHhcNMDYwOTE3MTk0NjM3WhcNMzYwOTE3MTk0NjM2WjB9MQswCQYDVQQGEwJJTDEWMBQG
A1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNh
dGUgU2lnbmluZzEpMCcGA1UEAxMgU3RhcnRDb20gQ2VydGlmaWNhdGlvbiBBdXRob3JpdHkw
ggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDBiNsJvGxGfHiflXu1M5DycmLWwTYg
IiRezul38kMKogZkpMyONvg45iPwbm2xPN1yo4UcodM9tDMr0y+v/uqwQVlntsQGfQqedIXW
eUyAN3rfOQVSWff0G0ZDpNKFhdLDcfN1YjS6LIp/Ho/u7TTQEceWzVI9ujPW3U3eCztKS5/C
Ji/6tRYccjV3yjxd5srhJosaNnZcAdt0FCX+7bWgiA/deMotHweXMAEtcnn6RtYTKqi5pquD
SR3l8u/d5AGOGAqPY1MWhWKpDhk6zLVmpsJrdAfkK+F2PrRt2PZE4XNiHzvEvqBTViVsUQn3
qqvKv3b9bZvzndu/PWa8DFaqr5hIlTpL36dYUNk4dalb6kMMAv+Z6+hsTXBbKWWc3apdzK8B
MewM69KN6Oqce+Zu9ydmDBpI125C4z/eIT574Q1w+2OqqGwaVLRcJXrJosmLFqa7LH4XXgVN
WG4SHQHuEhANxjJ/GP/89PrNbpHoNkm+Gkhpi8KWTRoSsmkXwQqQ1vp5Iki/untp+HDH+no3
2NgN0nZPV/+Qt+OR0t3vwmC3Zzrd/qqc8NSLf3Iizsafl7b4r4qgEKjZ+xjGtrVcUjyJthkq
cwEKDwOzEmDyei+B26Nu/yYwl/WL3YlXtq09s68rxbd2AvCl1iuahhQqcvbjM4xdCUsT37uM
dBNSSwIDAQABo4ICEDCCAgwwDwYDVR0TAQH/BAUwAwEB/zAOBgNVHQ8BAf8EBAMCAQYwHQYD
VR0OBBYEFE4L7xqkQFulF2mHMMo0aEPQQa7yMB8GA1UdIwQYMBaAFE4L7xqkQFulF2mHMMo0
aEPQQa7yMIIBWgYDVR0gBIIBUTCCAU0wggFJBgsrBgEEAYG1NwEBATCCATgwLgYIKwYBBQUH
AgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwNAYIKwYBBQUHAgEWKGh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL2ludGVybWVkaWF0ZS5wZGYwgc8GCCsGAQUFBwICMIHC
MCcWIFN0YXJ0IENvbW1lcmNpYWwgKFN0YXJ0Q29tKSBMdGQuMAMCAQEagZZMaW1pdGVkIExp
YWJpbGl0eSwgcmVhZCB0aGUgc2VjdGlvbiAqTGVnYWwgTGltaXRhdGlvbnMqIG9mIHRoZSBT
dGFydENvbSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSBQb2xpY3kgYXZhaWxhYmxlIGF0IGh0
dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwEQYJYIZIAYb4QgEBBAQDAgAHMDgG
CWCGSAGG+EIBDQQrFilTdGFydENvbSBGcmVlIFNTTCBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0
eTANBgkqhkiG9w0BAQsFAAOCAgEAjo/n3JR5fPGFf59Jb2vKXfuM/gTFwWLRfUKKvFO3lANm
MD+x5wqnUCBVJX92ehQN6wQOQOY+2IirByeDqXWmN3PH/UvSTa0XQMhGvjt/UfzDtgUx3M2F
Ik5xt/JxXrAaxrqTi3iSSoX4eA+D/i+tLPfkpLst0OcNOrg+zvZ49q5HJMqjNTbOx8aHmNrs
++myziebiMMEofYLWWivydsQD032ZGNcpRJvkrKTlMeIFw6Ttn5ii5B/q06f/ON1FE8qMt9b
DeD1e5MNq6HPh+GlBEXoPBKlCcWw0bdT82AUuoVpaiF8H3VhFyAXe2w7QSlc4axa0c2Mm+tg
HRns9+Ww2vl5GKVFP0lDV9LdJNUso/2RjSe15esUBppMeyG7Oq0wBhjA2MFrLH9ZXF2RsXAi
V+uKa0hK1Q8p7MZAwC+ITGgBF3f0JBlPvfrhsiAhS90a2Cl9qrjeVOwhVYBsHvUwyKMQ5bLm
KhQxw4UtjJixhlpPiVktucf3HMiKf8CdBUrmQk9io20ppB+Fq9vlgcitKj1MXVuEJnHEhV5x
JMqlG2zYYdMa4FTbzrqpMrUi9nNBCV24F10OD5mQ1kfabwo6YigUZ4LZ8dCAWZvLMdibD4x3
TrVoivJs9iQOLWxwxXPR3hTQcY+203sC9uO41Alua551hDnmfyWl8kgAwKQB2j8xggJMMIIC
SAIBATCBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0Q29tIEx0ZC4xKzApBgNV
BAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcxODA2BgNVBAMTL1N0YXJ0
Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50IENBAgMGLywwDQYJYIZI
AWUDBAIDBQCggYkwTwYJKoZIhvcNAQkEMUIEQL4wBmD7CQX3bvY7uaBRgFA+N9OOpLnVBv0D
mQMJqTwHchK20eGvWa7pUKe/s3pxmXbb1NgLQwni45fdDolEtAswGAYJKoZIhvcNAQkDMQsG
CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTQwMjAyMjAzODE3WjANBgkqhkiG9w0BAQEF
AASCAQBKwguimT8Gf/Q0bT/qG8pD/vpi6CWX9v93WslLy6QT+r8Ynd8Xf1eE/eaphwrUReBN
sJAqeULzUAKlsp0tTH3eMIQ3tli8nJrNyC1idTXzsraOkZMvWJj2VN8rDrB3Om25x/brTze8
v4vaLcwGdxfwh7qK7A9a+wJpNGvXkG4oA3klwScn0Kg9zShZHqyAWUVJXom/ZiEhw1gzLlfa
tN5H8sIydHYUijtEJi1EPR9M+TERByouJ89Iop4HT6KKRlLyFrfuiwpa/e14+qfij0xfBJDJ
B3MAPBVZL2u9OQqBvEld4DF55/85yRuny9dClBLt6RLi75jmwp48OhTkS4JX

--B_3474200297_16004353--



From tytso@thunk.org  Sun Feb  2 13:47:06 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 7B4421A00D8; Sun,  2 Feb 2014 13:47:06 -0800 (PST)
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_40=-0.001, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.535, 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 mwTptO2XmhmR; Sun,  2 Feb 2014 13:47:04 -0800 (PST)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id EE7BA1A00D6; Sun,  2 Feb 2014 13:47:03 -0800 (PST)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WA4sT-0006u8-1H; Sun, 02 Feb 2014 21:46:57 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 1FB2B580356; Sun,  2 Feb 2014 16:46:56 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1391377616; bh=Z6dAA63nyIB6hAfPb7shAvHWeha7iJClQEVAUxdLZp0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vuSAE8j247D8+KXlT9rl/4ZMZiKtbysLYIT+oF1lhgyEwYllQ6RBdzuYgRgDVOYro Ua03ZuoFBLLDl411ToNrrLfuw5VpzG6gmxJXhjcB6qp+ADv4Esz5ZsE95XG06ZYFeD J8/VhGt7y3peWtWxqeozk593lAep1ZKlpSYMi1Qw=
Date: Sun, 2 Feb 2014 16:46:56 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: dcrocker@bbiw.net
Subject: Re: Agenda, security, and monitoring
Message-ID: <20140202214656.GA960@thunk.org>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XsQoSWH+UP9D9v3l"
Content-Disposition: inline
In-Reply-To: <52ED8496.6000006@dcrocker.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 imap.thunk.org); SAEximRunCond expanded to false
Cc: John C Klensin <john-ietf@jck.com>, iesg@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, 02 Feb 2014 21:47:06 -0000

--XsQoSWH+UP9D9v3l
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Feb 01, 2014 at 03:34:46PM -0800, Dave Crocker wrote:
>=20
> 1. It has demonstrated unacceptable usability for average users.

This is much more of an integration issue than anything else, I think.

For example, both S/MIME and GPG support is well integrated into mutt,
such that it is quite easy to use.  It's literally 2 or 3 keystrokes
to request that a message be PGP signed or encrypted.

If you haven't looked to see how the implementations have gotten
better over the past couple of years, you may be quite surprised how
much better things have gotten.  For example, I was extremely
pleasantly surprised to find out how easy it was to buy[1] a 16 Euro
OpenGPG smartcard[2], and to start using it.  I didn't have to do any
driver configuration or software recompilation.  It just worked[tm].

[1] http://shop.kernelconcepts.de/product_info.php?cPath=3D1_26&products_id=
=3D42
[2] http://g10code.com/p-card.html

So now my GPG private key is stored on a smartcard, and is no longer
on my laptop hard drive.  (The same is true for my ssh private key ---
the gpg-agent also will handle ssh keys.  Major win!)


> 2. It does not protect the header or the envelope, to the extent
> anyone cares about divulging the Subject or other message
> meta-data...

This is true for both S/MIME and GPG.


> 3. It's packaging in the body is ugly. (See #1)

You can package up PGP signatures using PGP/MIME, at which point it is
just as ugly as MIME (and S/MIME) happens to be.  Which is to say, if
you have a mail agent which supports the MIME format (I use mutt), you
won't see the ugliness at all.

The one pain point is that if I know I'm exchanging encrypted mail
with someone for which I happen to know their mail agent doesn't
understand PGP/MIME, I have to go slightly out of my way to select the
legacy "BEGIN PGP MESSAGE" body format.

But then again, if I want to exchange encrypted mail with someone
whose mail user agent doesn't support S/MIME (or who didn't feel like
paying $$$ to some certifying authority, many of which have failed
spectactular in the past), I don't have any recourse at all.  At list
with PGP/GPG I have my choice of either PGP/MIME or the traditional
inline body format.

> However any focus on PGP or S/MIME in their current forms will be a
> distraction that well might seduce the IETF community into thinking
> it's doing something useful for the Internet that actually isn't.

If more internet developers actually used GPG or S/MIME, maybe we
could start focusing on the real problem, which isn't in how we do the
crypto, but how we do the key management, and/or figuring out how to
solve the CA "race to the bottom" problem.

						- Ted

P.S.  I would **really** strongly suggest that people consider
experimenting with the OpenPGP smart card.  If you have a Lenovo
laptop which you configured with the extra $20 smartcard reader
option, it's amazingly convenient from a hardware usage standpoint,
and as I mentioned, I was amazed how little work I needed to do to
make my Debian laptop use it.

If you need to purchase an external $20 USB smartcard reader (and
there are portable ones that when folded are only 48mm x 20mm x 12mm
-- see [2]) it's a little bit less convenient, but the piece of mind
in knowing that your crypto keys are very well protected is well worth
it IMHO.

[2] https://www.scbsolutions.com/express/product_info.php?cPath=3D1&product=
s_id=3D119&SCBtid=3D34f590521dbb61a86a0476833b38413c

The one annoying thing is that the cards are shipped from Germany.
Maybe someone would be willing to do a bulk buy and bring them to the
next IETF meeting, if there is sufficient interest.  As I mentioned,
it can be used to protect both your PGP and SSH private keys.

--XsQoSWH+UP9D9v3l
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

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

iQIcBAEBCAAGBQJS7rzNAAoJENNvdpvBGATwz7MP/3x2DOfhXW3+7Ie1FPYe8Z9B
Ke8r3KmN5F4d0L5pY9q+UmQtbQROpOLxV3GJw3mmNa9kdqcXb3H11Vfx6njYF3Ly
2Zh6aPltaJ/XOH6OtVis+RMIoIYyijndzWg8+dktlqeyRcEmafFfXFKTHA1JE+9f
oYwX9kG/LjDCIcHp65Cny/hoNL+byXfHkVSXqzGI0mnaVygKpQEmFB3ksk7yaBvA
VLsg9twh56oBnFl8AqPrbT6MZKEjr6hTY5dAc5ssFawxwyGeGaxZxswUQI/wTrdy
XAdsTEJITI5eHStYg3llsoHy7YWI2l0tALYBbpk/inUFqDyFmv/K7iGuNWn2aF0V
lBspJoDtfjRuDnS8WWLdE1JgEwbI5jYLUe3EJ4H3Vj0KZo37ADuyvpZt/jl4xfTm
h1XK0o17WwSw1JB885J/LVuuiTpZxSQqWawfChSydrwDZPwBPd23IyGwH6puBgIQ
5BEssmCbfBE/+6cW0AVsnS6ev2xH3P7wpzzbPMgU+8f1O15KF1wBfZneSpfYXt6u
sZhv7nnJTSZCY659IZWXddhtFdNjGv4zdqxrNqv9TgfYvq33XVyhkXHFoSRI6yxy
qJbKwKNsv+BQh4XqJ4zG7McsZXNvMZDshELeVj3nW60ih88UbMhM3uvWK9C7F144
wDh8uzfpTymbp5WWZDZg
=GQyt
-----END PGP SIGNATURE-----

--XsQoSWH+UP9D9v3l--

From gdaley@au.logicalis.com  Sun Feb  2 15:33:01 2014
Return-Path: <gdaley@au.logicalis.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C9541A013B; Sun,  2 Feb 2014 15:33:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.442
X-Spam-Level: 
X-Spam-Status: No, score=-1.442 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RELAY_IS_203=0.994, RP_MATCHES_RCVD=-0.535, 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 1xqbq1I-33_H; Sun,  2 Feb 2014 15:32:58 -0800 (PST)
Received: from smtp2.au.logicalis.com (smtp2.au.logicalis.com [203.8.7.133]) by ietfa.amsl.com (Postfix) with ESMTP id 5A31A1A0139; Sun,  2 Feb 2014 15:32:57 -0800 (PST)
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of gdaley@au.logicalis.com) identity=mailfrom; client-ip=203.8.7.161; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="gdaley@au.logicalis.com"; x-conformance=spf_only
Received-SPF: None (smtp2.au.logicalis.com: no sender authenticity information available from domain of postmaster@sdcexchht.au.logicalis.com) identity=helo; client-ip=203.8.7.161; receiver=smtp2.au.logicalis.com; envelope-from="gdaley@au.logicalis.com"; x-sender="postmaster@sdcexchht.au.logicalis.com"; x-conformance=spf_only
Received: from unknown (HELO sdcexchht.au.logicalis.com) ([203.8.7.161]) by smtp2.au.logicalis.com with ESMTP; 03 Feb 2014 10:32:53 +1100
Received: from SDCEXCHMS.au.logicalis.com ([10.18.196.50]) by sdcexchht.au.logicalis.com ([fe80::68b7:8880:fefb:f742%12]) with mapi id 14.02.0347.000; Mon, 3 Feb 2014 10:32:51 +1100
From: Greg Daley <gdaley@au.logicalis.com>
To: "'l.wood@surrey.ac.uk'" <l.wood@surrey.ac.uk>, "stbryant@cisco.com" <stbryant@cisco.com>, "jnc@mercury.lcs.mit.edu" <jnc@mercury.lcs.mit.edu>, "ietf@ietf.org" <ietf@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Topic: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsulating MPLS in UDP) to Proposed Standard
Thread-Index: AQHPHfHxZzPPQlRcgk6ua2U45NfiYJqd1tSwgAAZgQCAAAuhgIAEl8gA
Date: Sun, 2 Feb 2014 23:32:50 +0000
Message-ID: <72381AF1F18BAE4F890A0813768D992817FDD8F3@sdcexchms.au.logicalis.com>
References: <20140130193200.7BBD018C1C1@mercury.lcs.mit.edu> <72381AF1F18BAE4F890A0813768D992817FDAB19@sdcexchms.au.logicalis.com>, <52EB800E.2090102@cisco.com> <290E20B455C66743BE178C5C84F1240847E63346FE@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E63346FE@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.18.196.187]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Feb 2014 23:33:01 -0000

I think it is feasible, but I haven't looked too hard into whether people w=
ant to achieve this, and what the impact is on the control plane.

Greg Daley

> -----Original Message-----
> From: l.wood@surrey.ac.uk [mailto:l.wood@surrey.ac.uk]
> Sent: Friday, 31 January 2014 10:33 PM
> To: stbryant@cisco.com; Greg Daley; jnc@mercury.lcs.mit.edu; ietf@ietf.or=
g;
> mpls@ietf.org
> Subject: RE: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting
> MPLS in UDP) to Proposed Standard
>=20
> RFC 6773. which requires a full udp checksum for nat traversal.
>=20
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant
> [stbryant@cisco.com]
> Sent: 31 January 2014 10:50
> To: Greg Daley; 'Noel Chiappa'; ietf@ietf.org; mpls@ietf.org
> Subject: Re: [mpls] Last Call: <draft-ietf-mpls-in-udp-04.txt> (Encapsula=
ting
> MPLS in UDP) to Proposed Standard
>=20
> On 30/01/2014 22:44, Greg Daley wrote:
> > Of course, in order to get the protocols to pass legacy firewall
> > inspection, UDP encapsulation may be required, and companies would
> > have to actually implement the protocol... Greg Daley
> > gdaley@au.logicalis.com
> So UDP/DCCP/MPLS ?
>=20
> Stewart

From tobias.gondrom@gondrom.org  Sun Feb  2 16:28:42 2014
Return-Path: <tobias.gondrom@gondrom.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 64E711A0142; Sun,  2 Feb 2014 16:28:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.536
X-Spam-Level: 
X-Spam-Status: No, score=-102.536 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.535, 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 pQeqxMZ0HUIQ; Sun,  2 Feb 2014 16:28:40 -0800 (PST)
Received: from www.gondrom.org (www.gondrom.org [91.250.114.153]) by ietfa.amsl.com (Postfix) with ESMTP id 04A2B1A0141; Sun,  2 Feb 2014 16:28:39 -0800 (PST)
X-No-Relay: not in my network
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=DTTvydd730HF7J7RWU3uexftjwxAMneAslo0QOJV4zZepO9F+BmhHU9gsewpf936kKiUnwtHKGCM/jsTTuhk9E5oGNouVxFjnbl+zuPaGxirxhQq3EH8Mmn8jSfwLsUA07b3l861ScqwzGa6qh7m/++B9kc5PGBqeYaj3ZKRiNE=; h=X-No-Relay:X-No-Relay:X-No-Relay:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:X-Priority:References:In-Reply-To:X-Enigmail-Version:Content-Type:Content-Transfer-Encoding;
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.0.6] (2e40e8bc.skybroadband.com [46.64.232.188]) by www.gondrom.org (Postfix) with ESMTPSA id E296B1539000D; Mon,  3 Feb 2014 01:28:33 +0100 (CET)
Message-ID: <52EEE2B1.5070302@gondrom.org>
Date: Mon, 03 Feb 2014 00:28:33 +0000
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, john-ietf@jck.com, iesg@ietf.org
Subject: Re: Agenda, security, and monitoring
X-Priority: 4 (Low)
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net>
In-Reply-To: <52ED8496.6000006@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
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, 03 Feb 2014 00:28:42 -0000

Hi all,

this might be a totally stupid question, but I am gonna ask it anyway:
I know it is not as sexy as end point encryption, but we could also
concentrate on just filling the last gaps of a fully functional
encryption on all hops (clientA->mailserverA->mailserverB-clientB).
Recently, I get the feeling the maturity of mail-servers, DNS etc. could
actually allow for a worldwide deployment of this. And current levels of
spam and mass surveillance might be the trigger points needed to get
that widely deployed if we fill in a few minor gaps.
Today, basic client to server encryption is fairly trivial and already
widely in use.
And we could also work to get a predominant mail-server to mail-server
encrypted connection for all nodes, using TLS and certs pinned for the
domain read from DNS (or DNSSEC) or on first connect. That could
probably raise the efforts for pervasive mail eavesdropping quite a bit.

I know it is not as good as end-point to end-point encryption, and your
mail server and the recipient's mail server would still need to be
trusted systems, but it would be totally transparent for normal users
(which PGP is not) and the effort to get this done and deploy this
worldwide might be reasonable low. Plus it might have the added benefit
of reducing spam as well.

Just a thought.

Tobias



On 01/02/14 23:34, Dave Crocker wrote:
> On 2/1/2014 3:18 PM, John C Klensin wrote:
>> (1) Other than a probably-appropriate level of general paranoia,
>> do we have
>> any reason to believe that PGP (Symantec and/or GNUPG versions)
>> has been
>> sufficiently compromised to not provide a good defense against
>> either
>> pervasive surveillance or general snooping?
>
>
> 1. It has demonstrated unacceptable usability for average users.
>
> 2. It does not protect the header or the envelope, to the extent
> anyone cares about divulging the Subject or other message meta-data...
>
> 3. It's packaging in the body is ugly. (See #1)
>
> For sufficiently motivated and technical individuals, it's clear the
> technology is extremely useful as a discrete capability.
>
> However any focus on PGP or S/MIME in their current forms will be a
> distraction that well might seduce the IETF community into thinking
> it's doing something useful for the Internet that actually isn't.
>
> d/
>


From presnick@qti.qualcomm.com  Sun Feb  2 16:45:08 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 ADA681A0141; Sun,  2 Feb 2014 16:45:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.836
X-Spam-Level: 
X-Spam-Status: No, score=-4.836 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.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZTbzTjiABQaI; Sun,  2 Feb 2014 16:45:07 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id E68501A0143; Sun,  2 Feb 2014 16:45:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1391388302; x=1422924302; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=MxYYx2ayqrjF7Qd2ggJ5gT66B0j/aApl4FdWYK8NsB4=; b=VGmviv5yqzBMMWZcQ/g46iVg6UlCZhzEEjmp9B8eMYevrl8T+YUdnOzJ oP4ECIp5rf8lve2RJg2pKRtyAoQ/uMdAegxgzBMQgBP2C253uZ/FvOvPv fpxtzu3RZtwVlU5mwO/RMBgbf03YzmIJ29jO1ubh4E3rRlLfk5Mgfuhfb E=;
X-IronPort-AV: E=McAfee;i="5400,1158,7337"; a="102651737"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by wolverine02.qualcomm.com with ESMTP; 02 Feb 2014 16:45:02 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7337"; a="26449829"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 02 Feb 2014 16:45:01 -0800
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, 2 Feb 2014 16:45:01 -0800
Message-ID: <52EEE68A.4070509@qti.qualcomm.com>
Date: Sun, 2 Feb 2014 18:44:58 -0600
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: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com>
In-Reply-To: <BDD8B7355B350BB55CC3722F@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]
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, 03 Feb 2014 00:45:08 -0000

On 2/1/14 11:18 PM, John C Klensin wrote:

> Sorry, I wasn't clear.  At least in this particular context, I
> have no interest at all in authentication.  My interest was in a
> demonstration of the ability to handle encryption.  For S/MIME
> and PGP, if I can sign a message, I can decrypt a message that
> is sent to me.  From a privacy or surveillance resistance
> standpoint, the latter, and a way to demonstration That
> capability, are important.  Authentication is irrelevant and, as
> you say, not helpful in that context.
>    

I agree that authentication is irrelevant in this context. But that's 
leads me to agree with Dave on a central point (hence the little I-D 
we've been banging on and submitted to the STRINT folks): The problem 
with PGP and S/MIME is that they require authentication in order to 
start using encryption, and since authentication is both irrelevant to 
this *and* a pain to do, I don't think it's likely that mechanisms that 
require authentication to get started are good candidates to address PM, 
let alone be a terribly good demonstration that we can do encryption. I 
can't get torqued about people participating in a key signing: If you're 
interested in using those tools, go for it. But I do think that if we 
want to make headway on the PM problem and convince people that we can 
address pieces of it, we need to start looking at different sorts of 
mechanisms.

I suspect Ted might be right and this is simply an integration problem. 
I'm not sure whether Dave agrees or disagrees with me on this, but I 
think we've got the tools in our toolbox already: The bones (and much of 
the meat) of PGP or S/MIME might be perfectly suitable with some 
re-working. But I think until that re-working is done, we're not likely 
to have a good demonstration of this stuff actually working, especially 
if "the best technology we have is annoying  and will require you and 
your correspondents to learn more, and fuss more, than you would 
probably like".

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From paf@frobbit.se  Sun Feb  2 17:18:47 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 800E01A014D; Sun,  2 Feb 2014 17:18:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.186
X-Spam-Level: 
X-Spam-Status: No, score=-1.186 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, J_CHICKENPOX_21=0.6, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.535, 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 IEJIY8ulQRWR; Sun,  2 Feb 2014 17:18:46 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 57D411A014E; Sun,  2 Feb 2014 17:18:46 -0800 (PST)
Received: from ix-2.local (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 54E032029B; Mon,  3 Feb 2014 02:18:41 +0100 (CET)
Message-ID: <52EEEE6E.7090906@frobbit.se>
Date: Mon, 03 Feb 2014 02:18:38 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Theodore Ts'o <tytso@mit.edu>, dcrocker@bbiw.net
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <20140202214656.GA960@thunk.org>
In-Reply-To: <20140202214656.GA960@thunk.org>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="82JvSTP9NKIhPsvngw5sJBP9AahWUL50A"
Cc: John C Klensin <john-ietf@jck.com>, iesg@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, 03 Feb 2014 01:18:47 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--82JvSTP9NKIhPsvngw5sJBP9AahWUL50A
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-02 22:46, Theodore Ts'o wrote:
> P.S.  I would **really** strongly suggest that people consider
> experimenting with the OpenPGP smart card.  If you have a Lenovo
> laptop which you configured with the extra $20 smartcard reader
> option, it's amazingly convenient from a hardware usage standpoint,
> and as I mentioned, I was amazed how little work I needed to do to
> make my Debian laptop use it.

I want to point at the Youbikey that start to get some interesting
features. Many of you know Simon Josefsson that works with this, and
some even know Stina Ehrensv=E4rd, nowadays living in northern CA.

<http://www.yubico.com/2012/12/yubikey-neo-openpgp/>

Seems you John triggered some interest in at least some sharing and
hacking of "interesting things" that (which I strongly support) makes us
who are "geeks" try the various new things that exists. And that way we
will as always in IETF hopefully bring more usable tools and features
into whatever systems we work with.

   Patrik



--82JvSTP9NKIhPsvngw5sJBP9AahWUL50A
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.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFS7u5xrMabGguI180RAm2jAJ4pwl74HAfQFbtu4YicsWmUs5q1CgCgiQvX
KkPOJ0vSU7VMImLi6fOkaQA=
=Nop0
-----END PGP SIGNATURE-----

--82JvSTP9NKIhPsvngw5sJBP9AahWUL50A--

From joelja@bogus.com  Sun Feb  2 23:29:07 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D05751A017C; Sun,  2 Feb 2014 23:29:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5nFHJtrV1PyW; Sun,  2 Feb 2014 23:29:06 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 36A7D1A017A; Sun,  2 Feb 2014 23:29:06 -0800 (PST)
Received: from mb-aye.local (c-50-174-18-221.hsd1.ca.comcast.net [50.174.18.221]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s137T1W4097568 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 3 Feb 2014 07:29:01 GMT (envelope-from joelja@bogus.com)
Message-ID: <52EF4537.5030501@bogus.com>
Date: Sun, 02 Feb 2014 23:28:55 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-alto-protocol-25.txt> (ALTO Protocol) to Proposed Standard
References: <20140121123422.16733.7314.idtracker@ietfa.amsl.com>
In-Reply-To: <20140121123422.16733.7314.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Uq4CHUH9ticP29VpVPkHfx85WBjkC3xSm"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Mon, 03 Feb 2014 07:29:01 +0000 (UTC)
Cc: alto@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Feb 2014 07:29:08 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Uq4CHUH9ticP29VpVPkHfx85WBjkC3xSm
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Section 12.3

http://tools.ietf.org/html/draft-ietf-alto-protocol-25#section-12.3

seems ripe for inadvertent information disclosure and or deliberate
abuse. it's certainly not something that I would ask my ISP.

On 1/21/14, 4:34 AM, The IESG wrote:
>=20
> The IESG has received a request from the Application-Layer Traffic
> Optimization WG (alto) to consider the following document:
> - 'ALTO Protocol'
>   <draft-ietf-alto-protocol-25.txt> as Proposed 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-02-04. 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
>    Applications using the Internet already have access to some topology=

>    information of Internet Service Provider (ISP) networks.  For
>    example, views to Internet routing tables at looking glass servers
>    are available and can be practically downloaded to many network
>    application clients.  What is missing is knowledge of the underlying=

>    network topologies from the point of view of ISPs.  In other words,
>    what an ISP prefers in terms of traffic optimization -- and a way to=

>    distribute it.
>=20
>    The Application-Layer Traffic Optimization (ALTO) Service provides
>    network information (e.g., basic network location structure and
>    preferences of network paths) with the goal of modifying network
>    resource consumption patterns while maintaining or improving
>    application performance.  The basic information of ALTO is based on
>    abstract maps of a network.  These maps provide a simplified view,
>    yet enough information about a network for applications to
>    effectively utilize them.  Additional services are built on top of
>    the maps.
>=20
>    This document describes a protocol implementing the ALTO Service.
>    Although the ALTO Service would primarily be provided by ISPs, other=

>    entities such as content service providers could also operate an ALT=
O
>    Service.  Applications that could use this service are those that
>    have a choice to which end points to connect.  Examples of such
>    applications are peer-to-peer (P2P) and content delivery networks.
>=20
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-alto-protocol/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-alto-protocol/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20



--Uq4CHUH9ticP29VpVPkHfx85WBjkC3xSm
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 Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlLvRTgACgkQ8AA1q7Z/VrIa/gCePZGCowgvCqj50nqAZR9HJylN
00AAn0YlXiFjnfq+FfFtkUBobYoiAtUt
=4/lE
-----END PGP SIGNATURE-----

--Uq4CHUH9ticP29VpVPkHfx85WBjkC3xSm--

From enrico.marocco@telecomitalia.it  Mon Feb  3 00:21:05 2014
Return-Path: <enrico.marocco@telecomitalia.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 7C8D31A0170; Mon,  3 Feb 2014 00:21:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.978
X-Spam-Level: 
X-Spam-Status: No, score=0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_EQ_IT=0.635, RDNS_NONE=0.793, 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 IB1j2-NnxMZJ; Mon,  3 Feb 2014 00:21:03 -0800 (PST)
Received: from TELEDG001RM001.telecomitalia.it (unknown [217.169.121.18]) by ietfa.amsl.com (Postfix) with ESMTP id C75A51A0099; Mon,  3 Feb 2014 00:21:01 -0800 (PST)
Received: from grfhub703rm001.griffon.local (10.19.3.10) by TELEDG001RM001.telecomitalia.it (10.19.3.111) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 3 Feb 2014 09:20:53 +0100
Received: from MacLab.local (163.162.173.12) by smtp.telecomitalia.it (10.19.9.236) with Microsoft SMTP Server (TLS) id 8.3.342.0; Mon, 3 Feb 2014 09:20:47 +0100
Message-ID: <52EF515E.2020307@telecomitalia.it>
Date: Mon, 3 Feb 2014 09:20:46 +0100
From: Enrico Marocco <enrico.marocco@telecomitalia.it>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: joel jaeggli <joelja@bogus.com>, <ietf@ietf.org>
Subject: Re: [alto] Last Call: <draft-ietf-alto-protocol-25.txt> (ALTO Protocol) to Proposed Standard
References: <20140121123422.16733.7314.idtracker@ietfa.amsl.com> <52EF4537.5030501@bogus.com>
In-Reply-To: <52EF4537.5030501@bogus.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms090807070205090001070107"
X-TI-Disclaimer: Disclaimer1
Cc: alto@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Feb 2014 08:21:05 -0000

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

On 03/02/14 08:28, joel jaeggli wrote:
> Section 12.3
>=20
> http://tools.ietf.org/html/draft-ietf-alto-protocol-25#section-12.3
>=20
> seems ripe for inadvertent information disclosure and or deliberate
> abuse. it's certainly not something that I would ask my ISP.

=2E.. and the document tries to do its job by warning against it, in
section 15.4 ("Privacy for ALTO Users"), and pointing to the problem
statement part that deals with the issue in detail (RFC 6708, S. 5.2).

Just to confirm that client information inadvertent disclosure is a well
perceived issue (whose severity varies on a case by case basis though,
as probably one wouldn't care much if such sharing was done by the
Spotify app running on their laptop). Do you have any text
change/addition to suggest to make it even clearer?

Enrico



--------------ms090807070205090001070107
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIMojCC
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
5j5R0xi72MZ8ikMu1RQZKCyDbMwazlHiMIIGZjCCBU6gAwIBAgIDByD0MA0GCSqGSIb3DQEB
BQUAMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UECxMi
U2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRDb20g
Q2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0EwHhcNMTMwNzI0MTg1NjUz
WhcNMTQwNzI1MTExMzEwWjB1MRkwFwYDVQQNExBJcWRVZVdCRExxaEZ2N1hrMSgwJgYDVQQD
DB9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MS4wLAYJKoZIhvcNAQkBFh9lbnJp
Y28ubWFyb2Njb0B0ZWxlY29taXRhbGlhLml0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIB
CgKCAQEA078rvuWkIkHhL41Zi2MjXjy5TU71hLgnrstLepYUATbwALhWSs0Kk6l8FhKrOyCl
MPT8NMR5OPG91nEIloDY/AJL7GahjQXomtyqCPXWoRQL95sh+QhlCktlmGhVXm98YAcFWm8E
WoanJmv7UxKhJ6bdXLADn/dtxZGNiACG2U+fBaSyUT0Sa12SQ+u59yOZNWoaLRi2tos0hbZx
eKKVk7a+vxaIS5IIsvUUgJ3tGwFTsz+o3AFWLI/8U1u2LitbpKF/G91ReDA9bb10k5ay43r+
o1TigZEdHd683i7j4DIdjkY3FybFibDtzx+O054BPx5v4C4Nk8vHOHtif2czMwIDAQABo4IC
5TCCAuEwCQYDVR0TBAIwADALBgNVHQ8EBAMCBLAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsG
AQUFBwMEMB0GA1UdDgQWBBSjX2uvKQFc1dKQOjONZZ1hVH42cTAfBgNVHSMEGDAWgBRTcu2S
nODaywFcfH6WNU7y1LhRgjAqBgNVHREEIzAhgR9lbnJpY28ubWFyb2Njb0B0ZWxlY29taXRh
bGlhLml0MIIBTAYDVR0gBIIBQzCCAT8wggE7BgsrBgEEAYG1NwECAzCCASowLgYIKwYBBQUH
AgEWImh0dHA6Ly93d3cuc3RhcnRzc2wuY29tL3BvbGljeS5wZGYwgfcGCCsGAQUFBwICMIHq
MCcWIFN0YXJ0Q29tIENlcnRpZmljYXRpb24gQXV0aG9yaXR5MAMCAQEagb5UaGlzIGNlcnRp
ZmljYXRlIHdhcyBpc3N1ZWQgYWNjb3JkaW5nIHRvIHRoZSBDbGFzcyAxIFZhbGlkYXRpb24g
cmVxdWlyZW1lbnRzIG9mIHRoZSBTdGFydENvbSBDQSBwb2xpY3ksIHJlbGlhbmNlIG9ubHkg
Zm9yIHRoZSBpbnRlbmRlZCBwdXJwb3NlIGluIGNvbXBsaWFuY2Ugb2YgdGhlIHJlbHlpbmcg
cGFydHkgb2JsaWdhdGlvbnMuMDYGA1UdHwQvMC0wK6ApoCeGJWh0dHA6Ly9jcmwuc3RhcnRz
c2wuY29tL2NydHUxLWNybC5jcmwwgY4GCCsGAQUFBwEBBIGBMH8wOQYIKwYBBQUHMAGGLWh0
dHA6Ly9vY3NwLnN0YXJ0c3NsLmNvbS9zdWIvY2xhc3MxL2NsaWVudC9jYTBCBggrBgEFBQcw
AoY2aHR0cDovL2FpYS5zdGFydHNzbC5jb20vY2VydHMvc3ViLmNsYXNzMS5jbGllbnQuY2Eu
Y3J0MCMGA1UdEgQcMBqGGGh0dHA6Ly93d3cuc3RhcnRzc2wuY29tLzANBgkqhkiG9w0BAQUF
AAOCAQEAQ9Ff1giJV3UOk090vsVroHHsBy4J4eITcDLGg+wJ+M+4kULtKS7i+kJjfd5VZb1e
ZsnezvgmhmAaJRy+xl/j7l3UKbSVXfUcnKQ1IVnPVedA+4g6L8nA2cBTGj+vFScEC03HSFqy
Q2Shh3AkCo1L6HLoohHxTvSi7+A4P4uayaHSC0OSdVOXWyDOrjnkSWKQiPX4jc0nJofA7b+H
TppvjgzM5t+c9EQ0v8ldDfP4Pl6HhJ/xwMAETn3VG3hVuT321Gx/BXCS1TDMyUnXVf5BB+S8
vGlgwoPfX2o2ti0/ZXSt/VRUOmBF5kiePNIJ7MLOa15cbxI/2bF0xXKHEjBcETGCA90wggPZ
AgEBMIGUMIGMMQswCQYDVQQGEwJJTDEWMBQGA1UEChMNU3RhcnRDb20gTHRkLjErMCkGA1UE
CxMiU2VjdXJlIERpZ2l0YWwgQ2VydGlmaWNhdGUgU2lnbmluZzE4MDYGA1UEAxMvU3RhcnRD
b20gQ2xhc3MgMSBQcmltYXJ5IEludGVybWVkaWF0ZSBDbGllbnQgQ0ECAwcg9DAJBgUrDgMC
GgUAoIICHTAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0xNDAy
MDMwODIwNDZaMCMGCSqGSIb3DQEJBDEWBBRdQR138+go3q/CQJ/Hf8shif4ekDBsBgkqhkiG
9w0BCQ8xXzBdMAsGCWCGSAFlAwQBKjALBglghkgBZQMEAQIwCgYIKoZIhvcNAwcwDgYIKoZI
hvcNAwICAgCAMA0GCCqGSIb3DQMCAgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMIGlBgkr
BgEEAYI3EAQxgZcwgZQwgYwxCzAJBgNVBAYTAklMMRYwFAYDVQQKEw1TdGFydENvbSBMdGQu
MSswKQYDVQQLEyJTZWN1cmUgRGlnaXRhbCBDZXJ0aWZpY2F0ZSBTaWduaW5nMTgwNgYDVQQD
Ey9TdGFydENvbSBDbGFzcyAxIFByaW1hcnkgSW50ZXJtZWRpYXRlIENsaWVudCBDQQIDByD0
MIGnBgsqhkiG9w0BCRACCzGBl6CBlDCBjDELMAkGA1UEBhMCSUwxFjAUBgNVBAoTDVN0YXJ0
Q29tIEx0ZC4xKzApBgNVBAsTIlNlY3VyZSBEaWdpdGFsIENlcnRpZmljYXRlIFNpZ25pbmcx
ODA2BgNVBAMTL1N0YXJ0Q29tIENsYXNzIDEgUHJpbWFyeSBJbnRlcm1lZGlhdGUgQ2xpZW50
IENBAgMHIPQwDQYJKoZIhvcNAQEBBQAEggEAI+pBIV7q2YbHVrLA07kuusY8Uq9L6hL7bP4S
YHcfeag7u56rs960nHOvpzA5Qq3E52SVCAyZeWKSO/PmzicRs0GttKfO6sbP83eU4+6qZIeB
93JD8W0FIWDHOKdBC73ZTxaLC8KDJYMaA55cC3CetYfJOqTF4AlnGJ5ypP7F6dVv/vWXykGk
8D3urE3xapS88JnYyMD/jKnimeAOWw2ITnKM1ZvSCYKrqj+x7jJA2EJpTWAAsF4VBCPLbC25
0jOiqUU/uNwaXd32Glo2TnNGG7G5BkhSypjAfkmUGERxtXlROPGxjeQMObL4JZF1NYiiNJ+9
W8QYOLfx5iyz6oUy8QAAAAAAAA==
--------------ms090807070205090001070107--

From john-ietf@jck.com  Mon Feb  3 01:44:23 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 905F71A01A0; Mon,  3 Feb 2014 01:44:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.236
X-Spam-Level: 
X-Spam-Status: No, score=-1.236 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oeE4Z0DRlBiB; Mon,  3 Feb 2014 01:44:20 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 51B1E1A0199; Mon,  3 Feb 2014 01:44:20 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WAG4X-0005sV-MV; Mon, 03 Feb 2014 04:44:09 -0500
Date: Mon, 03 Feb 2014 04:44:04 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Agenda, security, and monitoring
Message-ID: <2E69BB29C9BE8847097BBBDC@JcK-HP8200.jck.com>
In-Reply-To: <52EEE68A.4070509@qti.qualcomm.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.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
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, 03 Feb 2014 09:44:23 -0000

--On Sunday, February 02, 2014 18:44 -0600 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

> The problem with PGP and S/MIME is that they require
> authentication in order to start using encryption, and since
> authentication is both irrelevant to this *and* a pain to do,
> I don't think it's likely that mechanisms that require
> authentication to get started are good candidates to address
> PM, let alone be a terribly good demonstration that we can do
> encryption.

Pete,

Perhaps I'm missing something, but it seems to me that, if one
is willing to rely sufficiently on the email system to say "this
will get to the intended person (or at least mailbox), and, if
it does, the person who opens it will either have the relevant
key to be able to read it or not and, if they don't that is ok",
then all that is needed is a self-signed key (or self-signed
X.509 cert).  That is basically "key but no authentication".
Put differently, we _always_ rely on authentication -- if I send
mail to "presnick@qti.qualcomm.com", I'm making a whole series
of assumptions that it is you, that such mail will reach you and
only trust-able others, and so on.  Those assumptions are fairly
weak and certainly don't involve independent certification, but
that is about the strength and quality of the authentication,
not whether authentication is assumed or not.

Put differently, unless my 30 second approximation to a threat
analysis missed something, it provides about the same level of
authentication as "I can buy a domain name without showing any
identity evidence other than the ability to make payment, I can
get a certificate issued on the basis of being able to set a
mailbox and appropriate DNS records to receive mail at that
domain and/or can publish keys as part of that domain record".
Like those [other] domain-based approaches, it is going to be
pretty good in practice unless an attacker has the ability to
either subvert a registrar [1] or, perhaps, to intercept and
divert (or copy) traffic en route [2].

Again, with either PGP or S/MIME (and X.509) with a self-signed
cert or key, authentication is not needed to start using
encryption, only a (perhaps implicit) belief on the part of the
sender that, if the recipient can advertise a public key, it
probably has the private one and that the key-advertiser is not
the proverbial entity-in-the-middle.

Of course, those of us who prefer a somewhat higher degree
(and/or out of band) of assurance than the entity we are
communicating with is the intended one will need authentication
and authentication strong enough to be convincing for our
purposes.  That is, as you suggest, a separate issue and more of
a pain.  It may be inconsistent with legitimate anonymity.  For
those who want it, bringing people together for key signing may
be helpful.  It may be especially helpful for anyone who
believes that "appears to be human, has a face, registered for
IETF, and can find the room in which a key-signing is to occur"
[3] is a better minimal credential than "was able to obtain a
domain name" [4].
 
best,
   john

  -----------------

Snarky notes:

[1] While there are clearly exceptions, there is considerable
evidence that "Honest and Careful Registrar" is an oxymoron and
even that a complete lack of scruples, or at least aggressive
and deliberate ignorance about registrant credentials, are
encouraged by ICANN policies.  If that be the case, then
authentication methods that ultimately depend on the
identity-quality of domain "purchase" and registration are
effective only to the extent to which an attacker is lacking in
motivation... unless one knows the domain of the relevant
individual and server with some independent certainty (that
notion of independent authentication again) and that the FQDN
string is spoof-proof.

[2] Of course, if the attacker cannot, or isn't willing to
invest the resources to, intercept and capture or divert an
in-transit data stream (or fake DNS records) then I don't quite
understand the threat model that unauthenticated (or very low
quality authentication) encryption protects against.

[3] If someone shows up at a key signing whom I've never seen
before and hands around a passport that says "Republic of Lower
Slobbovia" on the cover and has a picture and name inside,
whether a potential signer knows more about that individual's
identity than "appears to be human, etc.".  Few of us have ever
seen a Lower Slobbovian passport much less know how to
authenticate one.  So, again, authentication and quality of
credentials covers a broad spectrum.  The question isn't
"authentication or no authentication", it is what sort of
credentials are good enough for an intended purpose (and in
context with other methods).

[4] Note too that any sort of credential that draws on the DNS
for authenticity or key integrity and binding works a lot better
for domain-per-individual or domain-per-activity than it does
for domain-per-group-or-enterprise because, to some extent, such
methods depend on one's trusting everyone who is either a
legitimate user of the domain or who can compromise it.


From derhoermi@gmx.net  Mon Feb  3 06:02:18 2014
Return-Path: <derhoermi@gmx.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 92F9C1A01C9 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 06:02:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 247TYDfIpfZI for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 06:02:16 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.18]) by ietfa.amsl.com (Postfix) with ESMTP id 17D741A0233 for <ietf@ietf.org>; Mon,  3 Feb 2014 06:00:50 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.31.191]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0MVNWU-1VkXdO2ExC-00YeeG for <ietf@ietf.org>; Mon, 03 Feb 2014 15:00:49 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Agenda, security, and monitoring
Date: Mon, 03 Feb 2014 15:00:47 +0100
Message-ID: <mt7ve9hqusq2k5gr9jumu34mnaajs594qt@hive.bjoern.hoehrmann.de>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com> <2E69BB29C9BE8847097BBBDC@JcK-HP8200.jck.com>
In-Reply-To: <2E69BB29C9BE8847097BBBDC@JcK-HP8200.jck.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:kSg1XdgPaLG6OEYrecvpuHvXzUHy2NHO5fKSiZMzU2C/JiKQsa5 t4J1Y6V2GZDpomU6sO1WvZwQ9F+4oe91DL/TF+fGMtpBD1MMDZSWnbDJR+FWNok2cjsw2pM cwyxrpJBUAHUY8pfEtHzP6CO+FIHzb0YfEM3TGFZSoLmu+G+3dGVZZBux3I4J2Bc7JFAZrE /9JgBf3kgGye5lqEcBDMQ==
Cc: Pete Resnick <presnick@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: Mon, 03 Feb 2014 14:02:18 -0000

* John C Klensin wrote:
>Perhaps I'm missing something, but it seems to me that, if one
>is willing to rely sufficiently on the email system to say "this
>will get to the intended person (or at least mailbox), and, if
>it does, the person who opens it will either have the relevant
>key to be able to read it or not and, if they don't that is ok",
>then all that is needed is a self-signed key (or self-signed
>X.509 cert).

You do not need keys or certificates in that scenario.

>Again, with either PGP or S/MIME (and X.509) with a self-signed
>cert or key, authentication is not needed to start using
>encryption, only a (perhaps implicit) belief on the part of the
>sender that, if the recipient can advertise a public key, it
>probably has the private one and that the key-advertiser is not
>the proverbial entity-in-the-middle.

Without entities in the middle, encryption is unnecessary.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From tytso@thunk.org  Mon Feb  3 06:07: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 62B291A0172; Mon,  3 Feb 2014 06:07:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.326
X-Spam-Level: 
X-Spam-Status: No, score=-2.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.535, 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 YsZaF4qZXcs4; Mon,  3 Feb 2014 06:07:55 -0800 (PST)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id BA0DE1A021C; Mon,  3 Feb 2014 06:05:51 -0800 (PST)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WAK9k-0002yd-Oj; Mon, 03 Feb 2014 14:05:48 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 0338F580356; Mon,  3 Feb 2014 09:05:47 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1391436348; bh=BzKAPNt58vneuQnr9e8L+P5sBzyJJdcBLkZ5Nxg24Xw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LCSiRAOGWSwAfHguUsqqNXN6TYF4vK1kNYgpldTPUMhz+NdnhNLNU907nIN9dYrYQ 8pHWrUhSBO9p43FUOtv9LNX80Vt8APBz/kuaxf2mXC5gmi0ffNFEBe/YiISeDTEoD8 izJX0iZI1t98iN1oh1/2OtUeI8tWwsvNgkapzUZk=
Date: Mon, 3 Feb 2014 09:05:47 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Agenda, security, and monitoring
Message-ID: <20140203140547.GB25865@thunk.org>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52EEE68A.4070509@qti.qualcomm.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
Cc: John C Klensin <john-ietf@jck.com>, 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, 03 Feb 2014 14:07:57 -0000

On Sun, Feb 02, 2014 at 06:44:58PM -0600, Pete Resnick wrote:
> I agree that authentication is irrelevant in this context. But
> that's leads me to agree with Dave on a central point (hence the
> little I-D we've been banging on and submitted to the STRINT folks):
> The problem with PGP and S/MIME is that they require authentication
> in order to start using encryption, and since authentication is both
> irrelevant to this *and* a pain to do...

We should be a bit careful about our terms here.  If we don't care
about authentication at all, one solution is to just do hop-by-hop
diffie hellman (or TLS with completely unchecked certificates).
That's actually pretty easy, and it's not a bad thing to do whether or
not we do anything else, since it makes pervasive monitoring more
expensive by requiring the attacker to forgo passive eavesdropping and
have to do active M-I-T-M attacks.

If instead what we are saying is that we don't really care about
tieing a particular encryption key to a specifically named human
being, but to some other property, then this starts addressing the "do
we really need to have geek-friendly-but-scares-the-civilians PGP key
signing party" problem.  Instead you might want to say, "I don't care
whether this really is Mr. John Doe from Lower Elbonia, but I do want
to know whether this is the same entity who has been corresponding for
the last two months on the wg mailing list --- or is the author of a
particular I-D".

As a specific example, if all you want to do is make sure that someone
really controls the e-mail address named in the PGP key identity, then
you could do an web-automated version of "CAFF" (Certifying Authority
Fire and Forget)[1].

[1] http://manpages.ubuntu.com/manpages/hardy/man1/caff.1.html

So imagine a web service, running on tools.ietf.org, (a) which makes
someone prove that they have control over a specified e-mail address,
by mailing them a URL with a one-time code embedded in it, then (b)
asks them to upload a PGP key, and then (c) it sends back to that
e-mail address their PGP key signed with a registry key --- but the
signature is encrypted so only someone with the private key of the PGP
key can decrypt it.  This basically proves that the submitting entity
has control over both the e-mail address and the private key of the
PGP key that they are requesting be certified.

If this is being done via https, and you trust that the CA for
ietf.org is doing a competent job, and *all* CA's and sub-CA's trusted
by your browser are doing a competent job, then this will basically do
what you want, and it doesn't require people to show up at a PGP
signing party.  The user experience becomes that which is needed when
you sign up for a Google, or Yahoo, or any other web site which
demands that you prove that you have a valid e-mail address.

						- Ted

From daedulus@btconnect.com  Mon Feb  3 06:09:46 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 9B1111A0196 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 06:09:46 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aooBTgJkueKv for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 06:09:44 -0800 (PST)
Received: from co1outboundpool.messaging.microsoft.com (co1ehsobe002.messaging.microsoft.com [216.32.180.185]) by ietfa.amsl.com (Postfix) with ESMTP id 0A4531A0201 for <ietf@ietf.org>; Mon,  3 Feb 2014 02:10:55 -0800 (PST)
Received: from mail93-co1-R.bigfish.com (10.243.78.253) by CO1EHSOBE040.bigfish.com (10.243.66.105) with Microsoft SMTP Server id 14.1.225.22; Mon, 3 Feb 2014 10:10:55 +0000
Received: from mail93-co1 (localhost [127.0.0.1])	by mail93-co1-R.bigfish.com (Postfix) with ESMTP id 4D8AAD00173; Mon,  3 Feb 2014 10:10:55 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -16
X-BigFish: PS-16(zzbb2dI98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah21bch1fc6hzz1de098h1033IL17326ah8275bh8275dh1de097h186068hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h24afh2327h2336h2438h2461h2487h24ach24d7h2516h304l1d11m1155h)
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(24454002)(13464003)(199002)(189002)(51704005)(479174003)(377454003)(94316002)(74876001)(66066001)(65816001)(56816005)(80022001)(74502001)(86362001)(47446002)(47976001)(81542001)(50986001)(23756003)(44736004)(90146001)(89996001)(76482001)(74366001)(49866001)(47736001)(93916002)(61296002)(44716002)(59766001)(79102001)(62236002)(33646001)(94946001)(77982001)(69226001)(74662001)(63696002)(74706001)(47776003)(81342001)(31966008)(62966002)(93136001)(93516002)(50466002)(54316002)(56776001)(87286001)(87266001)(85306002)(85852003)(92566001)(83072002)(92726001)(87976001)(19580405001)(4396001)(51856001)(80976001)(88136002)(14496001)(19580395003)(83322001)(84392001)(76786001)(77096001)(46102001)(76796001)(77156001)(53806001)(42186004)(50226001)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB248; H:AMXPRD0310HT005.eurprd03.prod.outlook.com; CLIP:157.56.248.133; FPR:F87BD134.83CA9BE9.3CE18C7F.42E4FE71.203D2; InfoNoRecordsA:0; MX:1; LANG:en;
Received: from mail93-co1 (localhost.localdomain [127.0.0.1]) by mail93-co1 (MessageSwitch) id 1391422253126830_4895; Mon,  3 Feb 2014 10:10:53 +0000 (UTC)
Received: from CO1EHSMHS010.bigfish.com (unknown [10.243.78.239])	by mail93-co1.bigfish.com (Postfix) with ESMTP id 1B19C2E004C;	Mon,  3 Feb 2014 10:10:53 +0000 (UTC)
Received: from AM2PRD0710HT005.eurprd07.prod.outlook.com (157.56.249.213) by CO1EHSMHS010.bigfish.com (10.243.66.20) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 3 Feb 2014 10:10:53 +0000
Received: from AMSPR07MB248.eurprd07.prod.outlook.com (10.242.19.27) by AM2PRD0710HT005.eurprd07.prod.outlook.com (10.255.165.40) with Microsoft SMTP Server (TLS) id 14.16.411.0; Mon, 3 Feb 2014 10:10:40 +0000
Received: from AMXPRD0310HT005.eurprd03.prod.outlook.com (157.56.248.133) by AMSPR07MB248.eurprd07.prod.outlook.com (10.242.19.27) with Microsoft SMTP Server (TLS) id 15.0.868.8; Mon, 3 Feb 2014 10:10:40 +0000
Message-ID: <00b801cf20c7$8faa09e0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, John C Klensin <john-ietf@jck.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com>
Subject: Re: Agenda, security, and monitoring
Date: Mon, 3 Feb 2014 10:05:53 +0000
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: AMSPR07CA005.eurprd07.prod.outlook.com (10.242.77.173) To AMSPR07MB248.eurprd07.prod.outlook.com (10.242.19.27)
X-Forefront-PRVS: 01110342A5
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 03 Feb 2014 14:09:46 -0000

---- Original Message -----
From: "Pete Resnick" <presnick@qti.qualcomm.com>
To: "John C Klensin" <john-ietf@jck.com>
Cc: <ietf@ietf.org>; <iesg@ietf.org>
Sent: Monday, February 03, 2014 12:44 AM
 On 2/1/14 11:18 PM, John C Klensin wrote:
>
> > Sorry, I wasn't clear.  At least in this particular context, I
> > have no interest at all in authentication.  My interest was in a
> > demonstration of the ability to handle encryption.  For S/MIME
> > and PGP, if I can sign a message, I can decrypt a message that
> > is sent to me.  From a privacy or surveillance resistance
> > standpoint, the latter, and a way to demonstration That
> > capability, are important.  Authentication is irrelevant and, as
> > you say, not helpful in that context.
> >
>
> I agree that authentication is irrelevant in this context. But that's
> leads me to agree with Dave on a central point (hence the little I-D
> we've been banging on and submitted to the STRINT folks): The problem
> with PGP and S/MIME is that they require authentication in order to
> start using encryption, and since authentication is both irrelevant to
> this *and* a pain to do, I don't think it's likely that mechanisms
that
> require authentication to get started are good candidates to address
PM,
> let alone be a terribly good demonstration that we can do encryption.
I
> can't get torqued about people participating in a key signing: If
you're
> interested in using those tools, go for it. But I do think that if we
> want to make headway on the PM problem and convince people that we can
> address pieces of it, we need to start looking at different sorts of
> mechanisms.

Quote from the uta charter
"
- Consider, and possibly define, a standard way for an application
client and server to use unauthenticated encryption through TLS when
server and/or client authentication cannot be achieved.
"

Would that fit the bill?

Tom Petch

> I suspect Ted might be right and this is simply an integration
problem.
> I'm not sure whether Dave agrees or disagrees with me on this, but I
> think we've got the tools in our toolbox already: The bones (and much
of
> the meat) of PGP or S/MIME might be perfectly suitable with some
> re-working. But I think until that re-working is done, we're not
likely
> to have a good demonstration of this stuff actually working,
especially
> if "the best technology we have is annoying  and will require you and
> your correspondents to learn more, and fuss more, than you would
> probably like".
>
> pr
>
> --
> Pete Resnick<http://www.qualcomm.com/~presnick/>
> Qualcomm Technologies, Inc. - +1 (858)651-4478
>
>



From daedulus@btconnect.com  Mon Feb  3 06:10:18 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 E53A91A01E5 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 06:10:18 -0800 (PST)
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 upOYxBPYELkB for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 06:10:17 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe003.messaging.microsoft.com [207.46.163.26]) by ietfa.amsl.com (Postfix) with ESMTP id ADD611A029F for <ietf@ietf.org>; Mon,  3 Feb 2014 02:38:56 -0800 (PST)
Received: from mail149-co9-R.bigfish.com (10.236.132.230) by CO9EHSOBE030.bigfish.com (10.236.130.93) with Microsoft SMTP Server id 14.1.225.22; Mon, 3 Feb 2014 10:38:56 +0000
Received: from mail149-co9 (localhost [127.0.0.1])	by mail149-co9-R.bigfish.com (Postfix) with ESMTP id 01ADE180191;	Mon,  3 Feb 2014 10:38:56 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.249.213; KIP:(null); UIP:(null); IPV:NLI; H:AM2PRD0710HT005.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: 8
X-BigFish: PS8(zze6eIc85fhzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah21bch1fc6hzz1de097hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h24afh2327h2336h2438h2461h2487h24d7h2516h304l1d11m1155h)
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(36944003)(199002)(189002)(94316002)(74876001)(66066001)(65816001)(56816005)(80022001)(74502001)(86362001)(47446002)(47976001)(81542001)(50986001)(23756003)(44736004)(90146001)(89996001)(76482001)(74366001)(47736001)(49866001)(93916002)(512954002)(61296002)(44716002)(59766001)(79102001)(62236002)(33646001)(94946001)(77982001)(69226001)(74662001)(63696002)(74706001)(47776003)(81342001)(31966008)(62966002)(93136001)(93516002)(50466002)(54316002)(56776001)(87286001)(87266001)(85306002)(85852003)(92566001)(83072002)(92726001)(87976001)(4396001)(51856001)(80976001)(88136002)(14496001)(19580395003)(83322001)(84392001)(76786001)(46102001)(77096001)(76796001)(77156001)(53806001)(50226001)(42186004)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:AMSPR07MB248; H:AMXPRD0310HT002.eurprd03.prod.outlook.com; CLIP:157.56.248.133; FPR:BF5E2E15.8CD6D52A.C9F86FCF.44E49EFC.2017F; InfoNoRecordsA:0; MX:1; LANG:en;
Received: from mail149-co9 (localhost.localdomain [127.0.0.1]) by mail149-co9 (MessageSwitch) id 1391423934100883_7044; Mon,  3 Feb 2014 10:38:54 +0000 (UTC)
Received: from CO9EHSMHS003.bigfish.com (unknown [10.236.132.249])	by mail149-co9.bigfish.com (Postfix) with ESMTP id 1370580047;	Mon,  3 Feb 2014 10:38:54 +0000 (UTC)
Received: from AM2PRD0710HT005.eurprd07.prod.outlook.com (157.56.249.213) by CO9EHSMHS003.bigfish.com (10.236.130.13) with Microsoft SMTP Server (TLS) id 14.16.227.3; Mon, 3 Feb 2014 10:38:53 +0000
Received: from AMSPR07MB248.eurprd07.prod.outlook.com (10.242.19.27) by AM2PRD0710HT005.eurprd07.prod.outlook.com (10.255.165.40) with Microsoft SMTP Server (TLS) id 14.16.411.0; Mon, 3 Feb 2014 10:38:42 +0000
Received: from AMXPRD0310HT002.eurprd03.prod.outlook.com (157.56.248.133) by AMSPR07MB248.eurprd07.prod.outlook.com (10.242.19.27) with Microsoft SMTP Server (TLS) id 15.0.868.8; Mon, 3 Feb 2014 10:38:41 +0000
Message-ID: <011801cf20cb$79d84420$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: <ietf@ietf.org>
References: <CABL0ig7_aqQaHa1XTQ7g9aLfX11247r=1zvf7fZH7UfiyCuwuw@mail.gmail.com>
Subject: Email header randon(?) changes
Date: Mon, 3 Feb 2014 10:33:42 +0000
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: AMXPR07CA009.eurprd07.prod.outlook.com (10.242.64.49) To AMSPR07MB248.eurprd07.prod.outlook.com (10.242.19.27)
X-Forefront-PRVS: 01110342A5
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Cc: glen@amsl.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, 03 Feb 2014 14:10:19 -0000

Why does the format of the messages on i-d-announce for I-Ds change
format on a seemingly random basis?

The change that bugs me is the appearance and disappearance of the space
after action and before draft, which completely upsets my filtering, and
given the deluge of e-mails that will appear later this month, that
wastes my time.

Thus
Subject: I-D ACTION:draft-lan-nvo3-qtp-01.txt
versus
Subject: I-D Action: draft-lanthaler-profile-registry-05.txt

The CAPS do not bother me, nor does the switch between

Content-Type: text/plain; charset="us-ascii"
and
Content-Type: multipart/mixed; boundary="NextPart"

but that little old space does.  And this is not new.

Any ideas?

Tom Petch



From hallam@gmail.com  Mon Feb  3 06:32:21 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 DE4A61A00EB; Mon,  3 Feb 2014 06:32:21 -0800 (PST)
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=[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 raAKSGvI6VRu; Mon,  3 Feb 2014 06:32:20 -0800 (PST)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id DEA871A00DF; Mon,  3 Feb 2014 06:32:19 -0800 (PST)
Received: by mail-la0-f46.google.com with SMTP id b8so5479040lan.33 for <multiple recipients>; Mon, 03 Feb 2014 06:32:19 -0800 (PST)
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=IZ2Lp6OJbgO50zT9e+iOK2nPvADKek7SSa4oPG7kk6c=; b=x3CdghHx8YJbXNgueCaX93xcoYMJEUPy5eO4sjSNxppKmuMIjtRL5bI1HZhPmi+v/T 9i8Zn2N7eR90dXYFzYBzpavjpEbWZhJH/aLB0KNN5tjH6aBBwUVio8xcz60snFqJSOak hR/ROU26hOBo5OpIneP/1Ho7W4IkkxQ3zQ1DNwfwNgqlt9eXgA9K1yBBIxlkmLuG4kSa DyPqonPjOs9SvuMxWjcma1v/c3JrjWwtfPHPseSphmu/Kw7Cn+huTdFY87umQmJfpIEW g3UOdSDcbUY8vdrhzux6yUwgREqRXdA7GJW+8DgmEl5YM8gJjELbUkvfUfnT2GCsdXNr a6EQ==
MIME-Version: 1.0
X-Received: by 10.112.180.72 with SMTP id dm8mr13052952lbc.28.1391437938225; Mon, 03 Feb 2014 06:32:18 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 3 Feb 2014 06:32:18 -0800 (PST)
In-Reply-To: <20140203140547.GB25865@thunk.org>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com> <20140203140547.GB25865@thunk.org>
Date: Mon, 3 Feb 2014 09:32:18 -0500
Message-ID: <CAMm+Lwju1C23_ccytF8v8=5e6oNsZg75RM7d4JL-MRbkYMB_Jg@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
From: Phillip Hallam-Baker <hallam@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=089e011836be08f74004f181642b
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, IETF Discussion Mailing List <ietf@ietf.org>, "iesg@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, 03 Feb 2014 14:32:22 -0000

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

On Mon, Feb 3, 2014 at 9:05 AM, Theodore Ts'o <tytso@mit.edu> wrote:

> On Sun, Feb 02, 2014 at 06:44:58PM -0600, Pete Resnick wrote:
> > I agree that authentication is irrelevant in this context. But
> > that's leads me to agree with Dave on a central point (hence the
> > little I-D we've been banging on and submitted to the STRINT folks):
> > The problem with PGP and S/MIME is that they require authentication
> > in order to start using encryption, and since authentication is both
> > irrelevant to this *and* a pain to do...
>
> We should be a bit careful about our terms here.  If we don't care
> about authentication at all, one solution is to just do hop-by-hop
> diffie hellman (or TLS with completely unchecked certificates).


Yes, we need to decide what the threat model is and what the outcomes we
want to achieve are.

We also have to consider if there really are are downsides to having people
use less than perfect encryption. Because a lot of the reason for email
encryption taking so long seems to me to be people worried about doing it
wrong and making a mess. And that is the reason that PGP exists in the
first place: Phil Z. got tired of waiting for perfect and decided that
'Pretty Good' would be enough.


I see two separate sets of reasons for getting the whole IETF to start
doing secure email

1) We need to get people to start eating the dog food so that they
understand the reasons why the customers still refuse to eat it after 20
years.

2) Everyone who is involved in IETF in a significant degree is a target.
Intelligence services go after people who have the information they want.
And we have more of that than most. And its not just the security area
either. The pervasive intercept capability folks must keep a close eye on
technical changes that would affect their capabilities.


For twenty years now we have been arguing over PGP vs S/MIME. Lets stop
that. Both specifications could do with an upgrade. Lets develop an upgrade
that is a worthy successor to both and provides for full backwards
compatibility or as much backwards compatibility as makes sense for both.
-- 
Website: http://hallambaker.com/

--089e011836be08f74004f181642b
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, Feb 3, 2014 at 9:05 AM, Theodore Ts&#39;o <span dir=3D"ltr">&lt;<a href=
=3D"mailto:tytso@mit.edu" target=3D"_blank">tytso@mit.edu</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">
<div class=3D"im">On Sun, Feb 02, 2014 at 06:44:58PM -0600, Pete Resnick wr=
ote:<br>
&gt; I agree that authentication is irrelevant in this context. But<br>
&gt; that&#39;s leads me to agree with Dave on a central point (hence the<b=
r>
&gt; little I-D we&#39;ve been banging on and submitted to the STRINT folks=
):<br>
&gt; The problem with PGP and S/MIME is that they require authentication<br=
>
&gt; in order to start using encryption, and since authentication is both<b=
r>
</div>&gt; irrelevant to this *and* a pain to do...<br>
<br>
We should be a bit careful about our terms here. =A0If we don&#39;t care<br=
>
about authentication at all, one solution is to just do hop-by-hop<br>
diffie hellman (or TLS with completely unchecked certificates).</blockquote=
></div><div><br></div><div>Yes, we need to decide what the threat model is =
and what the outcomes we want to achieve are.</div><div><br></div><div>
We also have to consider if there really are are downsides to having people=
 use less than perfect encryption. Because a lot of the reason for email en=
cryption taking so long seems to me to be people worried about doing it wro=
ng and making a mess. And that is the reason that PGP exists in the first p=
lace: Phil Z. got tired of waiting for perfect and decided that &#39;Pretty=
 Good&#39; would be enough.</div>
<div><br></div><div><br></div><div>I see two separate sets of reasons for g=
etting the whole IETF to start doing secure email</div><div><br></div><div>=
1) We need to get people to start eating the dog food so that they understa=
nd the reasons why the customers still refuse to eat it after 20 years.</di=
v>
<div><br></div><div>2) Everyone who is involved in IETF in a significant de=
gree is a target. Intelligence services go after people who have the inform=
ation they want. And we have more of that than most. And its not just the s=
ecurity area either. The pervasive intercept capability folks must keep a c=
lose eye on technical changes that would affect their capabilities.</div>
<div><br></div><div><br></div><div>For twenty years now we have been arguin=
g over PGP vs S/MIME. Lets stop that. Both specifications could do with an =
upgrade. Lets develop an upgrade that is a worthy successor to both and pro=
vides for full backwards compatibility or as much backwards compatibility a=
s makes sense for both.</div>
-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/=
</a><br>
</div></div>

--089e011836be08f74004f181642b--

From glenams@gmail.com  Mon Feb  3 06:47:28 2014
Return-Path: <glenams@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 1DC061A0035 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 06:47:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.378
X-Spam-Level: 
X-Spam-Status: No, score=-99.378 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=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 QPuIq9OEslrc for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 06:47:27 -0800 (PST)
Received: from mail-vc0-x231.google.com (mail-vc0-x231.google.com [IPv6:2607:f8b0:400c:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id BD6631A002A for <ietf@ietf.org>; Mon,  3 Feb 2014 06:47:26 -0800 (PST)
Received: by mail-vc0-f177.google.com with SMTP id if11so4746151vcb.36 for <ietf@ietf.org>; Mon, 03 Feb 2014 06:47:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=GOXGRWo7b2qKY6b7bpukKx/xPS/Pe7b9L/pNzHAx+e4=; b=kjJCccz4d/kOAK39kwavQx+whE2f4CVOEA6G5/SkcIraIuqdKKBufWe2+/0MX2lCdG /n2pKogTlHOZ+hpbflDIOiAfBhQLXPfxBENQwNVNrnhyItYfDLcbwCUwWs40zjg3iDbk /K7y6Rk294Hc9GS/ttXLMHdpUUDh6IbHBI8HIWjW7hNs3F4xo+ebCXZ/LajsWGBh6YHn Q0PMFLL4/PosF2ZP7ejIEW25iG5FiT6lFyjFScSfcewYItFtc26nKGdW/wyedR/t4aWq PGXfWyDYEXIC/AUz6BKPMqurKvy+nhRD2tfAkXqdft/+h3x/DTDCnUY5+18B/rIyJk7L oK0Q==
MIME-Version: 1.0
X-Received: by 10.52.237.167 with SMTP id vd7mr109023vdc.54.1391438846433; Mon, 03 Feb 2014 06:47:26 -0800 (PST)
Sender: glenams@gmail.com
Received: by 10.58.50.230 with HTTP; Mon, 3 Feb 2014 06:47:26 -0800 (PST)
In-Reply-To: <011801cf20cb$79d84420$4001a8c0@gateway.2wire.net>
References: <CABL0ig7_aqQaHa1XTQ7g9aLfX11247r=1zvf7fZH7UfiyCuwuw@mail.gmail.com> <011801cf20cb$79d84420$4001a8c0@gateway.2wire.net>
Date: Mon, 3 Feb 2014 06:47:26 -0800
X-Google-Sender-Auth: ewVyekXfFLuDW20jlOVw5yvTzyQ
Message-ID: <CABL0ig4_zRhJTuAw5oRZ3fONxx30N6Cgb-iLrXvnY1G47Oi6Ow@mail.gmail.com>
Subject: Re: Email header randon(?) changes
From: Glen <glen@amsl.com>
To: "t.p." <daedulus@btconnect.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: glen@amsl.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, 03 Feb 2014 14:47:28 -0000

Hi Tom -

These messages are generated by the IETF tools, managed by the tools
team.  Although I'm sure many of them are on this list, this list
isn't the most optimal place to submit these requests.

As described here: http://trac.tools.ietf.org/about , ideas for new
tools or for refinement of current tools should be directed to to
tools-discuss@ietf.org.

I hope this information is helpful, and encourage you to reach out to
the tools team with your suggestions.

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)



On Mon, Feb 3, 2014 at 2:33 AM, t.p. <daedulus@btconnect.com> wrote:
> Why does the format of the messages on i-d-announce for I-Ds change
> format on a seemingly random basis?
>
> The change that bugs me is the appearance and disappearance of the space
> after action and before draft, which completely upsets my filtering, and
> given the deluge of e-mails that will appear later this month, that
> wastes my time.
>
> Thus
> Subject: I-D ACTION:draft-lan-nvo3-qtp-01.txt
> versus
> Subject: I-D Action: draft-lanthaler-profile-registry-05.txt
>
> The CAPS do not bother me, nor does the switch between
>
> Content-Type: text/plain; charset="us-ascii"
> and
> Content-Type: multipart/mixed; boundary="NextPart"
>
> but that little old space does.  And this is not new.
>
> Any ideas?
>
> Tom Petch
>
>

From john-ietf@jck.com  Mon Feb  3 07:12:39 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 037C31A0125; Mon,  3 Feb 2014 07:12:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.635
X-Spam-Level: 
X-Spam-Status: No, score=-0.635 tagged_above=-999 required=5 tests=[J_CHICKENPOX_21=0.6, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ov-T3aZeY_C4; Mon,  3 Feb 2014 07:12:36 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id C547F1A011F; Mon,  3 Feb 2014 07:12:36 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WALCN-0006F8-S5; Mon, 03 Feb 2014 10:12:35 -0500
Date: Mon, 03 Feb 2014 10:12:30 -0500
From: John C Klensin <john-ietf@jck.com>
To: Theodore Ts'o <tytso@mit.edu>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Agenda, security, and monitoring
Message-ID: <B4A75313465FBC31D5E1FCB5@JcK-HP8200.jck.com>
In-Reply-To: <20140203140547.GB25865@thunk.org>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com> <20140203140547.GB25865@thunk.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
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, 03 Feb 2014 15:12:39 -0000

--On Monday, February 03, 2014 09:05 -0500 Theodore Ts'o
<tytso@mit.edu> wrote:

> On Sun, Feb 02, 2014 at 06:44:58PM -0600, Pete Resnick wrote:
>> I agree that authentication is irrelevant in this context. But
>> that's leads me to agree with Dave on a central point (hence
>> the little I-D we've been banging on and submitted to the
>> STRINT folks): The problem with PGP and S/MIME is that they
>> require authentication in order to start using encryption,
>> and since authentication is both irrelevant to this *and* a
>> pain to do...
> 
> We should be a bit careful about our terms here.  If we don't
> care about authentication at all, one solution is to just do
> hop-by-hop diffie hellman (or TLS with completely unchecked
> certificates). That's actually pretty easy, and it's not a bad
>...
> As a specific example, if all you want to do is make sure that
> someone really controls the e-mail address named in the PGP
> key identity, then you could do an web-automated version of
> "CAFF" (Certifying Authority Fire and Forget)[1].
> 
> [1] http://manpages.ubuntu.com/manpages/hardy/man1/caff.1.html
> 
> So imagine a web service, running on tools.ietf.org, (a) which
> makes someone prove that they have control over a specified
> e-mail address, by mailing them a URL with a one-time code
> embedded in it, then (b) asks them to upload a PGP key, and
> then (c) it sends back to that e-mail address their PGP key
> signed with a registry key --- but the signature is encrypted
> so only someone with the private key of the PGP key can
> decrypt it.  This basically proves that the submitting entity
> has control over both the e-mail address and the private key
> of the PGP key that they are requesting be certified.
> 
> If this is being done via https, and you trust that the CA for
> ietf.org is doing a competent job, and *all* CA's and sub-CA's
> trusted by your browser are doing a competent job, then this
> will basically do what you want, and it doesn't require people
> to show up at a PGP signing party.  The user experience
> becomes that which is needed when you sign up for a Google, or
> Yahoo, or any other web site which demands that you prove that
> you have a valid e-mail address.

Right.  Very weak authentication of individual identity but,
given the above assumptions, decent-or-better authentication of
ownership of keys, addresses, and identity-persistence.  Whether
that is good enough depends on one's concerns and attack
scenarios -- for the IETF list, I'd imagine almost no one would
care.  And, of course, the requirement of competence by "*all*
CA's and sub-CA's trusted by your browser" doesn't pass a laugh
test these days unless one is paranoid and geeky enough to edit
browser CA lists down to those one actually has reason to trust.

That is why I think it is worthwhile to tease out what we really
want and need, not say blanket things like "no authentication
needed" as Pete's note seemed to.

     john


From kent@bbn.com  Mon Feb  3 07:28:15 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 1D9301A0172; Mon,  3 Feb 2014 07:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.837
X-Spam-Level: 
X-Spam-Status: No, score=-2.837 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, FH_RANDOM_SURE=0.499, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qyup7-ILkMqO; Mon,  3 Feb 2014 07:28:13 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id AC1581A016D; Mon,  3 Feb 2014 07:28:10 -0800 (PST)
Received: from dommiel.bbn.com ([192.1.122.15]:59043 helo=comsec.home) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1WALRI-000MLR-I1; Mon, 03 Feb 2014 10:28:00 -0500
Message-ID: <52EFB580.8070805@bbn.com>
Date: Mon, 03 Feb 2014 10:28:00 -0500
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.2.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, Stephen Farrell <stephen.farrell@cs.tcd.ie>,  Randy Bush <randy@psg.com>, John C Klensin <john-ietf@jck.com>
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <m2ob2qs4vy.wl%randy@psg.com> <52EDAF9A.7070706@dcrocker.net> <52EDB114.2020807@cs.tcd.ie> <52EDB9B7.3040309@dcrocker.net>
In-Reply-To: <52EDB9B7.3040309@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IESG <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: Mon, 03 Feb 2014 15:28:15 -0000

I think the S/MIME tripe wrapping feature may already provide a way to 
conceal
header info not needed to delivery.

Steve
> On 2/1/2014 6:44 PM, Stephen Farrell wrote:
>> If someone wanted to propose using PGP or S/MIME (aka CMS) formats
>> to provide closer-to-end-to-end confidentiality protection for email
>> messages that covered most headers in a way that might get deployment
>> then I think that would not match your description. I do suspect
>> that that is not likely to happen.
>
> 1.  Very much not likely.
>
> 2.  It's unrelated to the parts of such a service that appear to be 
> the major barriers to large-scale use
>
> 3.  It's the wrong level of design discussion, at this stage.
>
>
>> If OTOH, we spent a lot of time debating email message origin
>> authentication then I fully agree with you that we'd just be
>> distracting ourselves pointlessly.
>
> +1
>
> d/
>


From hallam@gmail.com  Mon Feb  3 07:31:11 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 243D21A0160; Mon,  3 Feb 2014 07:31:11 -0800 (PST)
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_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 azdvuSLR1VJ2; Mon,  3 Feb 2014 07:31:09 -0800 (PST)
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 9860D1A0140; Mon,  3 Feb 2014 07:31:08 -0800 (PST)
Received: by mail-lb0-f180.google.com with SMTP id n15so5424211lbi.39 for <multiple recipients>; Mon, 03 Feb 2014 07:31:07 -0800 (PST)
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=p17+O80IaLem8msjikEfbL3xvts+pPEuim2zVOWNYVM=; b=ViECnhQin1OzIpjPMf9scOVPtuj37R8OcofFycldPmJ2Y/MkTB1txn1Qm59bm90fy4 Ut9pheshbMxfDSkFMgj4oFNfDHoW/0dAUMt5Yq4qx0Pwt37RCaWLVTcD7OPhETupYST/ b+bzZC5rucOmVRv4aduXIQLp4t+K02FIuxy1ZGGpnV4TytYfUCQTVw2w7Wnn+JTBmTNM j/gAN5l7S3Md1m7gjamWoxgL3SMhkoLHEq8aGodG7Ux6MUhRpGLuVl3Z8Z2N1qkTxlU1 rkcvFo/8aAJUOh/b8k9beqArDcbXjoxR9QCjt2taTMAXeQkic49IGbHRGgM5mWbMc49Q ai3g==
MIME-Version: 1.0
X-Received: by 10.152.198.201 with SMTP id je9mr94208lac.73.1391441467798; Mon, 03 Feb 2014 07:31:07 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 3 Feb 2014 07:31:07 -0800 (PST)
In-Reply-To: <B4A75313465FBC31D5E1FCB5@JcK-HP8200.jck.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com> <20140203140547.GB25865@thunk.org> <B4A75313465FBC31D5E1FCB5@JcK-HP8200.jck.com>
Date: Mon, 3 Feb 2014 10:31:07 -0500
Message-ID: <CAMm+LwiJS=YW6YQunGdcL-rk_vP7tFKh9d6jvu03cp-M6GB-Lg@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a11348c0469fabc04f18236c0
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Theodore Ts'o <tytso@mit.edu>, IETF Discussion Mailing List <ietf@ietf.org>, "iesg@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, 03 Feb 2014 15:31:11 -0000

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

On Mon, Feb 3, 2014 at 10:12 AM, John C Klensin <john-ietf@jck.com> wrote:

> --On Monday, February 03, 2014 09:05 -0500 Theodore Ts'o
> <tytso@mit.edu> wrote:
> > If this is being done via https, and you trust that the CA for
> > ietf.org is doing a competent job, and *all* CA's and sub-CA's
> > trusted by your browser are doing a competent job, then this
> > will basically do what you want, and it doesn't require people
> > to show up at a PGP signing party.  The user experience
> > becomes that which is needed when you sign up for a Google, or
> > Yahoo, or any other web site which demands that you prove that
> > you have a valid e-mail address.
>
> Right.  Very weak authentication of individual identity but,
> given the above assumptions, decent-or-better authentication of
> ownership of keys, addresses, and identity-persistence.  Whether
> that is good enough depends on one's concerns and attack
> scenarios -- for the IETF list, I'd imagine almost no one would
> care.  And, of course, the requirement of competence by "*all*
> CA's and sub-CA's trusted by your browser" doesn't pass a laugh
> test these days unless one is paranoid and geeky enough to edit
> browser CA lists down to those one actually has reason to trust.
>

On another list we have pretty much agreed that we are not interested in
checking government issued ID in an IETF context.

Now there are many contexts where checking government issued IDs or
employment badges or the like makes a lot of sense and Comodo is one of
many CAs that support that type of enterprise need. But it is clear that we
are not in that situation here.

So what validation process is there for me to validate against? All I can
see is checking the email address with some sort of callback loop.


One of the reasons S/MIME has taken so long to take off is that people
built the toll booths before the highway. In a world in which everyone is
sending encrypted emails there are many ways for CAs to make money but we
are not yet in that world.

The place where I think the CA industry is best placed to add most value is
on the relying party side rather than the subject. Email trust
infrastructures will necessarily be complex and there will be a need for
those trust infrastructures to be curated.

Very few users are going to be 'geeky enough' to weed out their CA list but
there are companies that will do that for them. And its not just CA lists,
it is working out what key services are worth bothering with, evaluating
webs of trust and the like.


I think there are banks who would very much like to be able to send their
customers end-to-end encrypted email provided that the usability issues
with current offerings are addressed.

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

--001a11348c0469fabc04f18236c0
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, Feb 3, 2014 at 10:12 AM, John C Klensin <span dir=3D"ltr">&lt;<a href=
=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.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 Monday, February 03, 2014 09:05 -0500 T=
heodore Ts&#39;o<br>
<div class=3D"im">&lt;<a href=3D"mailto:tytso@mit.edu">tytso@mit.edu</a>&gt=
; wrote:<br></div><div class=3D"im">
&gt; If this is being done via https, and you trust that the CA for<br>
&gt; <a href=3D"http://ietf.org" target=3D"_blank">ietf.org</a> is doing a =
competent job, and *all* CA&#39;s and sub-CA&#39;s<br>
&gt; trusted by your browser are doing a competent job, then this<br>
&gt; will basically do what you want, and it doesn&#39;t require people<br>
&gt; to show up at a PGP signing party. =A0The user experience<br>
&gt; becomes that which is needed when you sign up for a Google, or<br>
&gt; Yahoo, or any other web site which demands that you prove that<br>
&gt; you have a valid e-mail address.<br>
<br>
</div>Right. =A0Very weak authentication of individual identity but,<br>
given the above assumptions, decent-or-better authentication of<br>
ownership of keys, addresses, and identity-persistence. =A0Whether<br>
that is good enough depends on one&#39;s concerns and attack<br>
scenarios -- for the IETF list, I&#39;d imagine almost no one would<br>
care. =A0And, of course, the requirement of competence by &quot;*all*<br>
CA&#39;s and sub-CA&#39;s trusted by your browser&quot; doesn&#39;t pass a =
laugh<br>
test these days unless one is paranoid and geeky enough to edit<br>
browser CA lists down to those one actually has reason to trust.<br></block=
quote><div><br></div><div>On another list we have pretty much agreed that w=
e are not interested in checking government issued ID in an IETF context.</=
div>
<div><br></div><div>Now there are many contexts where checking government i=
ssued IDs or employment badges or the like makes a lot of sense and Comodo =
is one of many CAs that support that type of enterprise need. But it is cle=
ar that we are not in that situation here.</div>
<div><br></div><div>So what validation process is there for me to validate =
against? All I can see is checking the email address with some sort of call=
back loop.</div><div>=A0</div></div><div><br></div><div>One of the reasons =
S/MIME has taken so long to take off is that people built the toll booths b=
efore the highway. In a world in which everyone is sending encrypted emails=
 there are many ways for CAs to make money but we are not yet in that world=
.</div>
<div><br></div><div>The place where I think the CA industry is best placed =
to add most value is on the relying party side rather than the subject. Ema=
il trust infrastructures will necessarily be complex and there will be a ne=
ed for those trust infrastructures to be curated.</div>
<div><br></div><div>Very few users are going to be &#39;geeky enough&#39; t=
o weed out their CA list but there are companies that will do that for them=
. And its not just CA lists, it is working out what key services are worth =
bothering with, evaluating webs of trust and the like.</div>
<div><br></div><div><br></div><div>I think there are banks who would very m=
uch like to be able to send their customers end-to-end encrypted email prov=
ided that the usability issues with current offerings are addressed.</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--001a11348c0469fabc04f18236c0--

From hallam@gmail.com  Mon Feb  3 07:40:49 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 593811A0115 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 07:40:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.479
X-Spam-Level: 
X-Spam-Status: No, score=-0.479 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RANDOM_SURE=0.499, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 yu-2jAncvaj7 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 07:40:47 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 302301A0032 for <ietf@ietf.org>; Mon,  3 Feb 2014 07:40:47 -0800 (PST)
Received: by mail-lb0-f179.google.com with SMTP id l4so5450318lbv.38 for <ietf@ietf.org>; Mon, 03 Feb 2014 07:40:46 -0800 (PST)
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:cc :content-type; bh=brazA8cFtujQsH4A5bYm2JGGo4o4BK0Efio+hw5ethk=; b=kynr6q+KsoVrJxdAEGthsOKOSI1tnySX0FkWuKUQTQNkdhaoFXZXZfrQbX/kaE6IhQ 7Uuov9bD6banqRnpcaTRYwj5fk1LeTZVjwuhIHTZdE8mYYSdKpxCUJCify9T0QLUj56/ 246Up3O7KUJjLz47W1nkOP07qOVvTTKKwBKFKKS8wVq9YfJ0WWTX5CdhC8hkWzImY0tW S0cxU85dUEr9CiYD4UhGDFJLThojTYAKuC2Jev0Qn5Tju1CAiXrHvqPBdX7W50sqtvQ2 JSmDPDRoHEDwTNUrF8BGQH5+ePdDE8OSa2LSUjwFW95FiQPt+UK0e2EfNAH8HIZ1IAdk I1Kg==
MIME-Version: 1.0
X-Received: by 10.152.23.39 with SMTP id j7mr2128456laf.35.1391442046440; Mon, 03 Feb 2014 07:40:46 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 3 Feb 2014 07:40:46 -0800 (PST)
In-Reply-To: <52EFB580.8070805@bbn.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <m2ob2qs4vy.wl%randy@psg.com> <52EDAF9A.7070706@dcrocker.net> <52EDB114.2020807@cs.tcd.ie> <52EDB9B7.3040309@dcrocker.net> <52EFB580.8070805@bbn.com>
Date: Mon, 3 Feb 2014 10:40:46 -0500
Message-ID: <CAMm+LwgseoTtTGoVFHHXq=4Cp4OfHpOaZE3yprxp2kV9SPns=w@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
From: Phillip Hallam-Baker <hallam@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e0158ca04e75b3a04f1825860
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Feb 2014 15:40:49 -0000

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

I looked at the specifications recently. There is certainly support for
concealing the RFC822 From and To headers and the Subject line. There are
two sets of metadata to consider:

1) The SMTP routing data (RFC821)
2) The Message headers (RFC822)

There are two sets of issues, one is what the specifications say, the other
is what the implementations do.

S/MIME does support concealing the RFC 822 header data because it is not
used in routing. Only the RFC821 data is used for routing. The RFC822
header data is only used by the email client to decide how to respond.

I have successfully routed several SMTP messages with no RFC822 routing
data at all. I plan testing support for 'full wrap' as described in the
specs but not for a while. To give a useful answer would require a look at
each and every email client including older versions.


The problem then is not how to achieve this particular capability in the
specification, it is how to make use of it in a way that does not cause
unpleasant user experiences when people have non-compliant software.

People with Outlook 2007 (say) who are happy with it are unlikely to want
to spend $350 to upgrade so that they don't get mysterious encrypted
messages that don't have sender names or subject lines.

On Mon, Feb 3, 2014 at 10:28 AM, Stephen Kent <kent@bbn.com> wrote:

>
> I think the S/MIME tripe wrapping feature may already provide a way to
> conceal
> header info not needed to delivery.
>
> Steve
>
>  On 2/1/2014 6:44 PM, Stephen Farrell wrote:
>>
>>> If someone wanted to propose using PGP or S/MIME (aka CMS) formats
>>> to provide closer-to-end-to-end confidentiality protection for email
>>> messages that covered most headers in a way that might get deployment
>>> then I think that would not match your description. I do suspect
>>> that that is not likely to happen.
>>>
>>
>> 1.  Very much not likely.
>>
>> 2.  It's unrelated to the parts of such a service that appear to be the
>> major barriers to large-scale use
>>
>> 3.  It's the wrong level of design discussion, at this stage.
>>
>>
>>  If OTOH, we spent a lot of time debating email message origin
>>> authentication then I fully agree with you that we'd just be
>>> distracting ourselves pointlessly.
>>>
>>
>> +1
>>
>> d/
>>
>>
>


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

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

<div dir=3D"ltr">I looked at the specifications recently. There is certainl=
y support for concealing the RFC822 From and To headers and the Subject lin=
e. There are two sets of metadata to consider:<div><br></div><div>1) The SM=
TP routing data (RFC821)</div>
<div>2) The Message headers (RFC822)<br><div class=3D"gmail_extra"><br></di=
v><div class=3D"gmail_extra">There are two sets of issues, one is what the =
specifications say, the other is what the implementations do.</div><div cla=
ss=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">S/MIME does support concealing the RFC=
 822 header data because it is not used in routing. Only the RFC821 data is=
 used for routing. The RFC822 header data is only used by the email client =
to decide how to respond.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I have succ=
essfully routed several SMTP messages with no RFC822 routing data at all. I=
 plan testing support for &#39;full wrap&#39; as described in the specs but=
 not for a while. To give a useful answer would require a look at each and =
every email client including older versions.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">The problem then is not how to achieve this parti=
cular capability in the specification, it is how to make use of it in a way=
 that does not cause unpleasant user experiences when people have non-compl=
iant software.</div>
<div class=3D"gmail_extra"><br>People with Outlook 2007 (say) who are happy=
 with it are unlikely to want to spend $350 to upgrade so that they don&#39=
;t get mysterious encrypted messages that don&#39;t have sender names or su=
bject lines.<br>
<br><div class=3D"gmail_quote">On Mon, Feb 3, 2014 at 10:28 AM, Stephen Ken=
t <span dir=3D"ltr">&lt;<a href=3D"mailto:kent@bbn.com" target=3D"_blank">k=
ent@bbn.com</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">
<br>
I think the S/MIME tripe wrapping feature may already provide a way to conc=
eal<br>
header info not needed to delivery.<br>
<br>
Steve<div class=3D"HOEnZb"><div class=3D"h5"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
On 2/1/2014 6:44 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">
If someone wanted to propose using PGP or S/MIME (aka CMS) formats<br>
to provide closer-to-end-to-end confidentiality protection for email<br>
messages that covered most headers in a way that might get deployment<br>
then I think that would not match your description. I do suspect<br>
that that is not likely to happen.<br>
</blockquote>
<br>
1. =A0Very much not likely.<br>
<br>
2. =A0It&#39;s unrelated to the parts of such a service that appear to be t=
he major barriers to large-scale use<br>
<br>
3. =A0It&#39;s the wrong level of design discussion, at this stage.<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If OTOH, we spent a lot of time debating email message origin<br>
authentication then I fully agree with you that we&#39;d just be<br>
distracting ourselves pointlessly.<br>
</blockquote>
<br>
+1<br>
<br>
d/<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
</div></div></div>

--089e0158ca04e75b3a04f1825860--

From abdussalambaryun@gmail.com  Mon Feb  3 07:43:46 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 9410C1A0155; Mon,  3 Feb 2014 07:43:46 -0800 (PST)
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 aligCk7z2i_U; Mon,  3 Feb 2014 07:43:45 -0800 (PST)
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 B44081A0160; Mon,  3 Feb 2014 07:43:44 -0800 (PST)
Received: by mail-yk0-f175.google.com with SMTP id q200so39880571ykb.6 for <multiple recipients>; Mon, 03 Feb 2014 07:43:44 -0800 (PST)
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=0lHh1KIavWv5+1Iwxs3dhSl25SJkD8qsV+x1tzjIudE=; b=Y5thpQhWmiLwAYc3gthLeyb1BRXUImlsOyyGsphXsR1APkj3Tx5RB5UW9WKicghXww Qh7guVCIbr+iX91KEDSRiykAPuD30HrqF2BdKGmd802PFwUk3IXkR+9zdNNlk9K9Ujdf FY3NHuEs+LAFFfLHoPB/M2LQzCofE/s7evE6WEu/+ty6SdLnSLEa+pBwBoxj038Gkw0p 2fGHjerJZOqrplfDauuVL6sm1Fxx+jgwpbceDe3cGq4ldv3MV0mP4MSqm2egLfznNZ9k MddUDv+5fgxNj3/yI7arz/tfZ7xtrlAl0H4V9yOMW+HApgjxoQ0hM0tiz9mHTWo2MzO1 Rs9w==
MIME-Version: 1.0
X-Received: by 10.236.120.135 with SMTP id p7mr172271yhh.155.1391442224432; Mon, 03 Feb 2014 07:43:44 -0800 (PST)
Received: by 10.170.220.213 with HTTP; Mon, 3 Feb 2014 07:43:44 -0800 (PST)
In-Reply-To: <20140203145243.32525.80191.idtracker@ietfa.amsl.com>
References: <20140203145243.32525.80191.idtracker@ietfa.amsl.com>
Date: Mon, 3 Feb 2014 16:43:44 +0100
Message-ID: <CADnDZ89S6=EFjw_jT68-NXg3nTqPhzEBxkv45D7Unr7+OGV6Lw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-dmm-requirements-13.txt> (Requirements for Distributed Mobility Management) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Cc: "iesg@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, 03 Feb 2014 15:43:46 -0000

The draft ignores the IETF MANETs and IETF LLNs and their IETF
protocols, why is that? IMHO, this document should consider all
related protocols used/standarded in IETF. This informational draft
has missing related information (not much related references, only its
WG references) which confuses especially when IETF publishes it,
because it does not consider all IETF distributed protocols, or does
not explain why.

AB

On 2/3/14, The IESG <iesg-secretary@ietf.org> wrote:
>
> The IESG has received a request from the Distributed Mobility Management
> WG (dmm) to consider the following document:
> - 'Requirements for Distributed Mobility Management'
>   <draft-ietf-dmm-requirements-13.txt> as Informational RFC
>
> 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-02-17. 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 defines the requirements for Distributed Mobility
>    Management (DMM) at the network layer.  The hierarchical structure in
>    traditional wireless networks has led primarily to centralized
>    deployment models.  As some wireless networks are evolving away from
>    the hierarchical structure, a distributed model for mobility
>    management can be useful to them.
>
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-dmm-requirements/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-dmm-requirements/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>

From dhc@dcrocker.net  Mon Feb  3 08:33: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 118CF1A010D; Mon,  3 Feb 2014 08:33:59 -0800 (PST)
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 1p7WFzk1mI-T; Mon,  3 Feb 2014 08:33:57 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id C3A841A00E0; Mon,  3 Feb 2014 08:33:57 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s13GXs7X013549 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Feb 2014 08:33:57 -0800
Message-ID: <52EFC4D3.9030305@dcrocker.net>
Date: Mon, 03 Feb 2014 08:33:23 -0800
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.2.0
MIME-Version: 1.0
To: Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com>
In-Reply-To: <52EEE68A.4070509@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]); Mon, 03 Feb 2014 08:33:57 -0800 (PST)
Cc: 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: Mon, 03 Feb 2014 16:33:59 -0000

On 2/2/2014 4:44 PM, Pete Resnick wrote:
> I suspect Ted might be right and this is simply an integration problem.
> I'm not sure whether Dave agrees or disagrees with me on this, but I
> think we've got the tools in our toolbox already:


I don't know either.  Depending upon the specific service goals, it 
probably is more than 'integration', which is why I harp on 'usability'.

But some service goals well might make for simplified usability demands.

Some other recent postings are also noting that these sorts of issues 
depend heavily on the specific protections that are sought.  Absent very 
specific statements about the nature of PM threats a given technique is 
intended to protect against (and is explicitly /not/ intended to protect 
against), along with some indication of community support for such 
protections and exposures, we are just doing a random walk through 
solution space.  Random walks produce random results.

If end users are a factor in a solution, then the real-world of 
mass-market user constraints is a factor.  There is an extensive body of 
knowledge about such users and any proposal needs to pay attention to 
that body.  A place to start is by excluding all IETF participants from 
examples.  Another place to start is by distinguishing reasonable 
behavioral expectations for configuration-time actions, versus 
creation-time, versus posting-time.  They are massively different 
operating contexts.

So:  Define the exact anti-PM service to be sought, define the actors 
needed to implement, and then get community agreement that it's an 
important goal to work towards.  Then we can discuss whether it's 
integration or usability or...

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From johnl@iecc.com  Mon Feb  3 09:57:19 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 6C8551A01C9 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 09:57:19 -0800 (PST)
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 YAAQhmg81YoS for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 09:57:18 -0800 (PST)
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 E9CC61A016D for <ietf@ietf.org>; Mon,  3 Feb 2014 09:57:17 -0800 (PST)
Received: (qmail 29300 invoked from network); 3 Feb 2014 17:57:17 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 3 Feb 2014 17:57:17 -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=52efd87d.xn--btvx9d.k1402; i=johnl@user.iecc.com; bh=4z8qvB0clgJYSsj0n9g1sDYnBuq0ypBQVbfnPfzJeME=; b=Hgeo7p6b2nRW1UYKDqrS5U4rMt4lHKjzzjsbovUmm41chQsZj9PKbbZLWYp3pqVv6+lUdinnwqYPmov69motrOXqN7mre/MGJ8K9YxvWFOVKhqIjuNzeyMKg5qDBETyhE7N3hEr2JiLIvBi9WbkEZAs3hwYRmnucrOKtZp++C7q8YcsJqbv0/jDcBp+Uh0zTLEr/i1iqZDY3zvUzuxTg8bIpl8UncGYlSlWvK/LXPaE34QzVPJilMv+0cW1D/rZL
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=52efd87d.xn--btvx9d.k1402; bh=4z8qvB0clgJYSsj0n9g1sDYnBuq0ypBQVbfnPfzJeME=; b=rHF3xu5Qv5Bhf/5lqtf1XafCDBBcJlm2hpXYD9uF5zWMqtA+jy1FYdQ/CI6KPqMbrQBRWAbmaq5dSSdps5zt7AGxDILA5dhihbHJdfKFyvZ8YxDPgyrKyc//gpVE0Xwrh2VB+sf1lVNqaEqYEfjh7YuQFGSZs7wtA65xGD6ZPs/Sq1kZbRpOcc2UZiWm5DP3Ls3TzIjG5G3OeogrGadeS8wBAy9gwb15IxD9MLpviujl7T3SXcsA38ztAiR42KCy
Date: 3 Feb 2014 17:56:55 -0000
Message-ID: <20140203175655.8511.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Email header randon(?) changes
In-Reply-To: <011801cf20cb$79d84420$4001a8c0@gateway.2wire.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Feb 2014 17:57:19 -0000

>The CAPS do not bother me, nor does the switch between
>
>Content-Type: text/plain; charset="us-ascii"
>and
>Content-Type: multipart/mixed; boundary="NextPart"
>
>but that little old space does.  And this is not new.
>
>Any ideas?

Learn about regular expressions?

Helpfully,
John

PS: the state of the art in the regard seems to be procmail, an amazing
piece of work in daily use around the world, with source code essentially
unchanged in over 20 years.

From worley@shell01.TheWorld.com  Mon Feb  3 11:12:04 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 508D61A01D6 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:12:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.2
X-Spam-Level: 
X-Spam-Status: No, score=-1.2 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, LOTS_OF_MONEY=0.001, 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 CGQ5Ih4BqYPR for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:12:02 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 521401A01CE for <ietf@ietf.org>; Mon,  3 Feb 2014 11:12:02 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s13JBIkd016341; Mon, 3 Feb 2014 14:11:20 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s13J3JC33120994; Mon, 3 Feb 2014 14:03:19 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s13J3Jr04204938; Mon, 3 Feb 2014 14:03:19 -0500 (EST)
Date: Mon, 3 Feb 2014 14:03:19 -0500 (EST)
Message-Id: <201402031903.s13J3Jr04204938@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: Phillip Hallam-Baker <hallam@gmail.com>
In-reply-to: <CAMm+LwjF_E7q1vbef6-sQ9wXYbtBsJEgny768iv4aNh1e5SSmw@mail.gmail.com> (hallam@gmail.com)
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <52EE065B.1050707@frobbit.se> <52EE07AC.2020701@dcrocker.net> <CAMm+LwjF_E7q1vbef6-sQ9wXYbtBsJEgny768iv4aNh1e5SSmw@mail.gmail.com>
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, 03 Feb 2014 19:12:04 -0000

> From: Phillip Hallam-Baker <hallam@gmail.com>

> The part that you don't state by name but imply is 'what is the business
> model'. We are talking about a multi-million dollar change to the email
> infrastructure. That is only justified if we can show a multi-billion
> dollar return on the investment.
> 
> I think that there is such a return. If my bank, my doctor, my brokerage
> can send mail and be assured that the transport is confidential end to end,
> they can use email in more ways. SSL made Web commerce possible and added
> roughly five trillion dollars to global GDP according to one estimate.
> Email security can make Internet commerce better and simpler and sustain
> that growth. Even if the additional benefits from making the other Internet
> killer application secure are 1% of the Web benefits, that is a lot of
> potential.

Unfortunately, "my bank, my doctor, my brokerage" have all implemented
confidential email, but they are horrible webmail systems.  That means
that a considerable amount of the benefit that will be obtainable from
confidential email is already being obtained, making it harder for
proper confidential email to gain acceptance in the market.

Dale

From brian.e.carpenter@gmail.com  Mon Feb  3 11:12:54 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 4C66F1A01CA for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:12:54 -0800 (PST)
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 LJbiqk5XHnQW for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:12:52 -0800 (PST)
Received: from mail-pd0-x22b.google.com (mail-pd0-x22b.google.com [IPv6:2607:f8b0:400e:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE421A01E6 for <ietf@ietf.org>; Mon,  3 Feb 2014 11:12:52 -0800 (PST)
Received: by mail-pd0-f171.google.com with SMTP id g10so7204749pdj.30 for <ietf@ietf.org>; Mon, 03 Feb 2014 11:12:52 -0800 (PST)
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=T3qvIKVs+HMSpt7/HWIbwBk4/jEzSP/Ya0sVfXKfhtI=; b=eF9AVNym6EhL4Puz3b5yve1brhPa3r/q/XXsjCr80zbUf9yILPSLwh3vb5XzAGsRbr uZXZ/STHUk0hCQr8klEkSHcbOsR6EUFEQ/rnp1b4t4eCNPcxj0ykWrsuR7QCq/TCm6gu AupCUCk/B/mkdkHQMZ1+rBrV9vuPgK+EJs+RpQz5qPKn/MDbT5DBs7eZ3ueDuKeW9us4 ewj3zO56O9etqWcfHthqvJy033sI7YM9JGKNlys9qhSEQneMwG+rNKcPFX4rsDh7QIb5 3cKZ1UbPQcNmIvRUplxF6osqPdWulHqLjhYAngjydgFODUyVKV3nl8v5pCMbQZy6rYBM iw3w==
X-Received: by 10.66.65.134 with SMTP id x6mr38497958pas.12.1391454772179; Mon, 03 Feb 2014 11:12:52 -0800 (PST)
Received: from [192.168.178.23] (147.199.69.111.dynamic.snap.net.nz. [111.69.199.147]) by mx.google.com with ESMTPSA id n6sm32130013pbj.22.2014.02.03.11.12.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 11:12:51 -0800 (PST)
Message-ID: <52EFEA34.8030700@gmail.com>
Date: Tue, 04 Feb 2014 08:12:52 +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 Levine <johnl@taugh.com>
Subject: Re: Email header randon(?) changes
References: <20140203175655.8511.qmail@joyce.lan>
In-Reply-To: <20140203175655.8511.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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, 03 Feb 2014 19:12:54 -0000

I believe that there are two formats because one of them
is generated by the automatic posting tool (when successful)
and the other one is generated by an older tool used by
the Secretariat for manual posting (when automatic posting
fails for some reason).

    Brian

On 04/02/2014 06:56, John Levine wrote:
>> The CAPS do not bother me, nor does the switch between
>>
>> Content-Type: text/plain; charset="us-ascii"
>> and
>> Content-Type: multipart/mixed; boundary="NextPart"
>>
>> but that little old space does.  And this is not new.
>>
>> Any ideas?
> 
> Learn about regular expressions?
> 
> Helpfully,
> John
> 
> PS: the state of the art in the regard seems to be procmail, an amazing
> piece of work in daily use around the world, with source code essentially
> unchanged in over 20 years.
> 

From worley@shell01.TheWorld.com  Mon Feb  3 11:16:15 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38E481A016D for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:16:15 -0800 (PST)
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_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 neCpcWvTMdj9 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:16:13 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id 26A021A010F for <ietf@ietf.org>; Mon,  3 Feb 2014 11:16:13 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s13JF9qK028250; Mon, 3 Feb 2014 14:15:11 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s13J2Wlx3904566; Mon, 3 Feb 2014 14:02:32 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s13J2VRK4208381; Mon, 3 Feb 2014 14:02:31 -0500 (EST)
Date: Mon, 3 Feb 2014 14:02:31 -0500 (EST)
Message-Id: <201402031902.s13J2VRK4208381@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: John C Klensin <john-ietf@jck.com>
In-reply-to: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> (john-ietf@jck.com)
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com>
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, 03 Feb 2014 19:16:15 -0000

> From: John C Klensin <john-ietf@jck.com>

> After looking through the agenda and thinking about end to end
> confidentiality mechanisms, a few questions/suggestions:

The recent news reports that I have seen are that the NSA's pervasive
monitoring focuses on "metatada", "who is talking to whom".  And the
trouble with end-to-end confidentiality mechanisms is that they do not
hide the destination address; indeed they can't.  And it seems to me
that almost no confidentiality systems have been focused on
confidentiality of message destinations.

So I think some thought needs to be put into what can be done to
thwart pervasive monitoring when the information to be concealed is
the identity of the endpoints.

Dale

From brian.e.carpenter@gmail.com  Mon Feb  3 11:18:30 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 4234A1A016D for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:18:30 -0800 (PST)
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 rp7mYYFI988q for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:18:28 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 0D1BC1A010F for <ietf@ietf.org>; Mon,  3 Feb 2014 11:18:28 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id kl14so7512187pab.1 for <ietf@ietf.org>; Mon, 03 Feb 2014 11:18:28 -0800 (PST)
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=bbshZDtt7uyNyeXAObdE9+5TSEBNK6qE6IRn72wh1ww=; b=G/OmdyKoAtO2FPU16QDXKm2QUzIceETEXI3V6JkF4V6ZreYOT5zduItmnk6gjjR/gj lo/lB1v6YxofHKIVqo/RsBZKGfC/sXEoPsZlZ5/FAym3mP2o4pVPypUXqMZk/PC8MpyW 3vJmYXmrqyVFufmwJAsPUh6V/UnUzTEF4YM70dUR80EzGmLHT7xZ0H75LpLlg9A1O56L W92/koDdo4xU/ESuA80dz+v+KJLXPYdhZp61W5bQjV5tg+vkha4zovdb4iIl6BVlHImJ 8nR+RCS5yMfVdsCvMbt+H6XqwmwDQPWgnu7af7usbxvVj6dDEfR6jqjkW7pwgU2eqdiT ZwhQ==
X-Received: by 10.66.144.227 with SMTP id sp3mr39397845pab.100.1391455108027;  Mon, 03 Feb 2014 11:18:28 -0800 (PST)
Received: from [192.168.178.23] (147.199.69.111.dynamic.snap.net.nz. [111.69.199.147]) by mx.google.com with ESMTPSA id tu3sm58584397pbc.40.2014.02.03.11.18.25 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 11:18:27 -0800 (PST)
Message-ID: <52EFEB83.7080900@gmail.com>
Date: Tue, 04 Feb 2014 08:18:27 +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: Bjoern Hoehrmann <derhoermi@gmx.net>
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com> <2E69BB29C9BE8847097BBBDC@JcK-HP8200.jck.com> <mt7ve9hqusq2k5gr9jumu34mnaajs594qt@hive.bjoern.hoehrmann.de>
In-Reply-To: <mt7ve9hqusq2k5gr9jumu34mnaajs594qt@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@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: Mon, 03 Feb 2014 19:18:30 -0000

On 04/02/2014 03:00, Bjoern Hoehrmann wrote:
...
>> Again, with either PGP or S/MIME (and X.509) with a self-signed
>> cert or key, authentication is not needed to start using
>> encryption, only a (perhaps implicit) belief on the part of the
>> sender that, if the recipient can advertise a public key, it
>> probably has the private one and that the key-advertiser is not
>> the proverbial entity-in-the-middle.
> 
> Without entities in the middle, encryption is unnecessary.

I'm having difficulty understanding that assertion.Does your
definition of "entity in the middle" include passive wire/fibre taps?

   Brian

From hallam@gmail.com  Mon Feb  3 11:37:08 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 7BD0D1A0207 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:37:08 -0800 (PST)
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 Ulu3TviM--Ee for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:37:06 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 0E17F1A010F for <ietf@ietf.org>; Mon,  3 Feb 2014 11:37:05 -0800 (PST)
Received: by mail-lb0-f179.google.com with SMTP id l4so5584302lbv.24 for <ietf@ietf.org>; Mon, 03 Feb 2014 11:37:05 -0800 (PST)
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=i5MnrP6s5/bFwLKmtgTJS1X/lXP2kYl5gEhW001tino=; b=P4UlXNbtb9Iv0f8iYaEz/u2NUMfR+p+AdtGZmcusYoiGfuhgIBcz9IBXQlvMefEOs7 JtvxCjDBjgxYhR8rNtbUeLu4pA7iOLDYH7Q+AttMgvfwg4b2iMn9jbtUFbvxo5+afkYW E1B2d0wzcCp4CSi9mYHWr5XNbXvmPApkmot6jcBnk+PjThtFjh5/4jnUJDGuqEv5/pa7 Qxd6XLsBtES6N2fJDosiqJdXwqqiQQ++qBshRCL1xUytK4Pl4ji4CjEBw/ub1wROPJhb qz+YWBHGRwmwoMQgMjtue/qiNJdjfth5d3h0JybAItAi0Sk6ZHlAJjsfaGtk0xGtu9BW 5c+A==
MIME-Version: 1.0
X-Received: by 10.112.219.134 with SMTP id po6mr2763427lbc.36.1391456225184; Mon, 03 Feb 2014 11:37:05 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 3 Feb 2014 11:37:05 -0800 (PST)
In-Reply-To: <52EFEB83.7080900@gmail.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com> <2E69BB29C9BE8847097BBBDC@JcK-HP8200.jck.com> <mt7ve9hqusq2k5gr9jumu34mnaajs594qt@hive.bjoern.hoehrmann.de> <52EFEB83.7080900@gmail.com>
Date: Mon, 3 Feb 2014 14:37:05 -0500
Message-ID: <CAMm+LwhbXvdQNPT2U=8QsAFJOC+0mrFaz4TTykpaTs0P2Lm3zQ@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2689405d0c204f185a6c8
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, 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, 03 Feb 2014 19:37:08 -0000

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

On Mon, Feb 3, 2014 at 2:18 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 04/02/2014 03:00, Bjoern Hoehrmann wrote:
> ...
> >> Again, with either PGP or S/MIME (and X.509) with a self-signed
> >> cert or key, authentication is not needed to start using
> >> encryption, only a (perhaps implicit) belief on the part of the
> >> sender that, if the recipient can advertise a public key, it
> >> probably has the private one and that the key-advertiser is not
> >> the proverbial entity-in-the-middle.
> >
> > Without entities in the middle, encryption is unnecessary.
>
> I'm having difficulty understanding that assertion.Does your
> definition of "entity in the middle" include passive wire/fibre taps?
>
>    Brian
>

There are active attacks and passive attacks.

When we talk about man in the middle attacks we are usually talking about
an active man in the middle who can change traffic.

A passive wire tap is not usually considered to be a 'man in the middle'
attack.

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

--001a11c2689405d0c204f185a6c8
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, Feb 3, 2014 at 2:18 PM, Brian E Carpenter <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D"_blank">brian=
.e.carpenter@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 04/02/2014 03:00, Bjoern Hoehrmann wrote:=
<br>
...<br>
<div class=3D"im">&gt;&gt; Again, with either PGP or S/MIME (and X.509) wit=
h a self-signed<br>
&gt;&gt; cert or key, authentication is not needed to start using<br>
&gt;&gt; encryption, only a (perhaps implicit) belief on the part of the<br=
>
&gt;&gt; sender that, if the recipient can advertise a public key, it<br>
&gt;&gt; probably has the private one and that the key-advertiser is not<br=
>
&gt;&gt; the proverbial entity-in-the-middle.<br>
&gt;<br>
&gt; Without entities in the middle, encryption is unnecessary.<br>
<br>
</div>I&#39;m having difficulty understanding that assertion.Does your<br>
definition of &quot;entity in the middle&quot; include passive wire/fibre t=
aps?<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0Brian<br>
</font></span></blockquote></div><br>There are active attacks and passive a=
ttacks.</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra=
">When we talk about man in the middle attacks we are usually talking about=
 an active man in the middle who can change traffic.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">A passive w=
ire tap is not usually considered to be a &#39;man in the middle&#39; attac=
k.<br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"http://hallam=
baker.com/">http://hallambaker.com/</a><br>

</div></div>

--001a11c2689405d0c204f185a6c8--

From brian.e.carpenter@gmail.com  Mon Feb  3 11:46:10 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 BD8A71A0209 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:46:10 -0800 (PST)
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 aKSl-gZavZty for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:46:09 -0800 (PST)
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 9C6471A010F for <ietf@ietf.org>; Mon,  3 Feb 2014 11:46:09 -0800 (PST)
Received: by mail-pa0-f46.google.com with SMTP id rd3so7454150pab.19 for <ietf@ietf.org>; Mon, 03 Feb 2014 11:46:09 -0800 (PST)
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=nCBH2ajwQF7liMvck0e8OczUQ4+rzqkR0QmNNemUVsI=; b=oJHY4o0tD4JfDFoIBVM9wJRpNGk2XR5R1JQMPE0bwyQA425pM5XyGtWj/A5caAf2eg avCAJRv0egHGxFFE44ygC3NGGmnCJnvAWVCXyuaamdIeFvWSNrXcuIlc/R1BSVvXzRB2 ONgvIF79P3QeowN0h0ORBfAA35BBujYPEESa6+EM/QTjW29D6n3vXgcEj/+WJjtqCPNO 5kuC3EXHQrk6k7BfTDH5mSM7CljQOh9I8XYs4Mr2YnKaO1hG6LeZJ353tg1qjOCfX2IR /MMlFnu+6L1flvvwEXO8UcNuIjiqyynnMPx11XarrOjLcQzg8mQ5EkpSrjuLgZRODt+r 5UzQ==
X-Received: by 10.66.149.231 with SMTP id ud7mr39681631pab.8.1391456769685; Mon, 03 Feb 2014 11:46:09 -0800 (PST)
Received: from [192.168.178.23] (147.199.69.111.dynamic.snap.net.nz. [111.69.199.147]) by mx.google.com with ESMTPSA id om6sm58734958pbc.43.2014.02.03.11.46.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 11:46:09 -0800 (PST)
Message-ID: <52EFF201.7090804@gmail.com>
Date: Tue, 04 Feb 2014 08:46:09 +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: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com>	<52EDAD15.6060504@cs.tcd.ie>	<BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com>	<52EEE68A.4070509@qti.qualcomm.com>	<2E69BB29C9BE8847097BBBDC@JcK-HP8200.jck.com>	<mt7ve9hqusq2k5gr9jumu34mnaajs594qt@hive.bjoern.hoehrmann.de>	<52EFEB83.7080900@gmail.com> <CAMm+LwhbXvdQNPT2U=8QsAFJOC+0mrFaz4TTykpaTs0P2Lm3zQ@mail.gmail.com>
In-Reply-To: <CAMm+LwhbXvdQNPT2U=8QsAFJOC+0mrFaz4TTykpaTs0P2Lm3zQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.com>, Bjoern Hoehrmann <derhoermi@gmx.net>, 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, 03 Feb 2014 19:46:11 -0000

On 04/02/2014 08:37, Phillip Hallam-Baker wrote:
> On Mon, Feb 3, 2014 at 2:18 PM, Brian E Carpenter <
> brian.e.carpenter@gmail.com> wrote:
> 
>> On 04/02/2014 03:00, Bjoern Hoehrmann wrote:
>> ...
>>>> Again, with either PGP or S/MIME (and X.509) with a self-signed
>>>> cert or key, authentication is not needed to start using
>>>> encryption, only a (perhaps implicit) belief on the part of the
>>>> sender that, if the recipient can advertise a public key, it
>>>> probably has the private one and that the key-advertiser is not
>>>> the proverbial entity-in-the-middle.
>>> Without entities in the middle, encryption is unnecessary.
>> I'm having difficulty understanding that assertion.Does your
>> definition of "entity in the middle" include passive wire/fibre taps?
>>
>>    Brian
>>
> 
> There are active attacks and passive attacks.
> 
> When we talk about man in the middle attacks we are usually talking about
> an active man in the middle who can change traffic.
> 
> A passive wire tap is not usually considered to be a 'man in the middle'
> attack.

Agreed, but it was the assertion that without one, encryption
is unnecessary that puzzled me.

    Brian

From Ted.Lemon@nominum.com  Mon Feb  3 11:46:48 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 C842C1A021A for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:46:48 -0800 (PST)
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 kDsNGsz3b7Mk for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:46:47 -0800 (PST)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id ADB681A0219 for <ietf@ietf.org>; Mon,  3 Feb 2014 11:46:47 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUu/yJ/dVtPTdeQXF9am0keEXEbL2/z5F@postini.com; Mon, 03 Feb 2014 11:46:48 PST
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 95A1A1B8300 for <ietf@ietf.org>; Mon,  3 Feb 2014 11:46:47 -0800 (PST)
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 8E347190052; Mon,  3 Feb 2014 11:46:47 -0800 (PST)
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, 3 Feb 2014 11:46:47 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Agenda, security, and monitoring
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <201402031903.s13J3Jr04204938@shell01.TheWorld.com>
Date: Mon, 3 Feb 2014 14:46:45 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4B79E458-F241-4C20-B634-B49B1DA09394@nominum.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <52EE065B.1050707@frobbit.se> <52EE07AC.2020701@dcrocker.net> <CAMm+LwjF_E7q1vbef6-sQ9wXYbtBsJEgny768iv4aNh1e5SSmw@mail.gmail.com> <201402031903.s13J3Jr04204938@shell01.TheWorld.com>
To: "Dale R. Worley" <worley@ariadne.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
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, 03 Feb 2014 19:46:49 -0000

On Feb 3, 2014, at 2:03 PM, Dale R. Worley <worley@ariadne.com> wrote:
> Unfortunately, "my bank, my doctor, my brokerage" have all implemented
> confidential email, but they are horrible webmail systems.  That means
> that a considerable amount of the benefit that will be obtainable from
> confidential email is already being obtained, making it harder for
> proper confidential email to gain acceptance in the market.

Actually it's not being obtained.   These systems work quite poorly, and =
typically aren't all that secure.   I do not think they are widely used =
by customers, because their usability is so bad.


From john-ietf@jck.com  Mon Feb  3 11:52:27 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 8A6961A0216 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:52:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JrO5FJyefswY for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:52:24 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D4AB81A015A for <ietf@ietf.org>; Mon,  3 Feb 2014 11:52:23 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WAPZ4-0006am-DQ; Mon, 03 Feb 2014 14:52:18 -0500
Date: Mon, 03 Feb 2014 14:52:10 -0500
From: John C Klensin <john-ietf@jck.com>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Agenda, security, and monitoring
Message-ID: <13F96040032E27327AE0710D@JcK-HP8200.jck.com>
In-Reply-To: <201402031902.s13J2VRK4208381@shell01.TheWorld.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <201402031902.s13J2VRK4208381@shell01.TheWorld.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
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, 03 Feb 2014 19:52:27 -0000

--On Monday, February 03, 2014 14:02 -0500 "Dale R. Worley"
<worley@ariadne.com> wrote:

>...
> So I think some thought needs to be put into what can be done
> to thwart pervasive monitoring when the information to be
> concealed is the identity of the endpoints.

I completely agree.  I just think it is a mistake to become so
obsessed with metadata monitoring (what in PSTN land was often
known as "pen registers" that we ignore data confidentiality.
Similarly, I think it would be a mistake to become so concerned
about the Final Ultimate Solution To Confidentiality Problems
that we stop doing what we can to make known, existing, strong
confidentiality from working effectively and/or better.

In the particular case of metadata/ pen register data it is
probably worth remembering that the most common reason for
collecting such data is to figure out which conversations to try
to capture in more depth, i.e., actually intercept and review
content.  Let's not ignore either threat.

    john






From tytso@thunk.org  Mon Feb  3 11:56: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 A592C1A01DA for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:56:30 -0800 (PST)
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_40=-0.001, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.535, 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 IJMM9OWYUr16 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 11:56:28 -0800 (PST)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 1027B1A0162 for <ietf@ietf.org>; Mon,  3 Feb 2014 11:56:28 -0800 (PST)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WAPd4-0004YF-4P; Mon, 03 Feb 2014 19:56:26 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 6D8D0580356; Mon,  3 Feb 2014 14:56:25 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1391457385; bh=gGRUWTGQtZ2AC/+KZhWGvD++lquoikHH0j1RqfV1TTg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=vLzuEClNcCpCgqx5n5z0m3U6wWE6WXDyhJIGt1/4/vbq5fbz7XbZFnCorB1OCy44F o+mgiO/fKhsZM7qHj1/t0aFuw18nv5hzZkVjLyRSHMo4uNmlGS1nJp8bVi5o4DtF5r AdtzdbzEKA01XRF4Ti5P09TorHSo29QqYU3iIrHQ=
Date: Mon, 3 Feb 2014 14:56:25 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: "Dale R. Worley" <worley@ariadne.com>
Subject: Re: Agenda, security, and monitoring
Message-ID: <20140203195625.GA26065@thunk.org>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <201402031902.s13J2VRK4208381@shell01.TheWorld.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201402031902.s13J2VRK4208381@shell01.TheWorld.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
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: Mon, 03 Feb 2014 19:56:31 -0000

On Mon, Feb 03, 2014 at 02:02:31PM -0500, Dale R. Worley wrote:
> 
> The recent news reports that I have seen are that the NSA's pervasive
> monitoring focuses on "metatada", "who is talking to whom".  And the
> trouble with end-to-end confidentiality mechanisms is that they do not
> hide the destination address; indeed they can't.  And it seems to me
> that almost no confidentiality systems have been focused on
> confidentiality of message destinations.

That's what NSA is doing for telephones, and briefly using e-mail
analyzing communications between US preson under their authorities
(or claimed authorities) under section 215 of the Patriot Act.

It would be a mistake to assume this is *all* they are doing.  Indeed,
it's likely that the NSA is actually doing keyword based filtering of
content, for communications that are between non-US persons and where
the endpoints are outside of the US.  This is done under their
authorities granted to them under Executive Order 12003.

Given that the FBI wanted to drop "Carnivore" servers in US data
centers to do this kind of keyword based filtering many years ago,
it's certainly within the capabilities the US Intelligence Community.

So to the extent that non-US persons want the same level of privacy
that apparently US persons have (unless there is some other secret
court order with some other secret law interpretation we're not aware
of which is enabling the FBI to do this kind of snooping, and we just
don't know about it yet), it's not surprising people are interested in
encrypting e-mail bodies.

Encrypting the endpoint identities is a lot more difficult, since you
need to route the information somehow.  There are solutions such as
onion routing, but they ease of use isn't quite there, and I don't
think they currently would scale well if huge numbers of people were
using them.

Certainly hiding the RFC-822 headers, including the subject lines,
inside the encrypted body would certainly be a good start, but of
course that doesn't solve the issue of the SMTP envelop information.

       	    	    	      	    - Ted

From housley@vigilsec.com  Mon Feb  3 12:20:59 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7F621A015A for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 12:20:58 -0800 (PST)
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 Ljh0xzSrTxQE for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 12:20:54 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 080DF1A020C for <ietf@ietf.org>; Mon,  3 Feb 2014 12:20:52 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id E00B99A42ED; Mon,  3 Feb 2014 15:20:41 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id oiEtsFcELs5L; Mon,  3 Feb 2014 15:20:40 -0500 (EST)
Received: from [142.131.239.161] (unknown [142.131.239.161]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 807399A42AD; Mon,  3 Feb 2014 15:20:40 -0500 (EST)
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <52E6D628.80103@umn.edu>
Date: Mon, 3 Feb 2014 15:20:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <7DA9D44B-1B9D-43BE-B41D-290684A41972@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk> <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com> <028c01cf1a0a$048899d0$0d99cd70$@olddog.co.uk> <52E6D628.80103@umn.edu>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.1085)
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, 03 Feb 2014 20:20:59 -0000

David:

With respect to the AS Special purpose Registry, I might sit more =
comfortably in its own document, and then it could be referenced from =
this document. At this point, I'm concerned that he delay to this =
document would be quite unfortunate.  Do you believe that such a =
document can be produced and approved rapidly?  If not, then I'd like to =
see this document move forward and a subsequent document could make an =
update if there is community consensus to evolve the form of the =
special-purpose AS number registry.

Russ



> On 1/25/14, 14:14 , Adrian Farrel wrote:
>> Hi Russ,
>>=20
>> Thanks for this. The -03 revision just posted addresses my comments.
>>=20
>> Adrian
>=20
> Russ,
>=20
> I also like the -03 revision, its has generally moved everything in =
the right direction.  But I have a few comments on it.
>=20
> 1. The part about RFC2860 in Section 1 seems like an incomplete =
thought, at the very least it seems awkward to me.  I'm really not sure =
what you are intending to say.  But, I agree RFC2860 is relevant to the =
discussion.  I'm just not sure you have nailed what to say about it.
>=20
> 2. I really like the idea of creating a "Special-Purpose AS Number =
Registry".  However, it may be a better idea to spin-off the creation of =
a "Special-Purpose AS Number Registry" into a separate draft.  I'm =
concerned that trying to do two important things in the same document =
will fail to achieve one or both of the important things.  For instance =
the simple section 3 you have currently worries me.  I'd really think =
RFC6890 is the template to use for creating a "Special-Purpose AS Number =
Registry", more below.
>=20
> If you spin-off the creation of a "Special-Purpose AS Number =
Registry", the following items are for that draft.
>=20
> 3. There is a draft in WG Last Call in the IDR that documents the =
reservations of ASNs 65535 and 4294967295, the "Last ASNs".
> http://tools.ietf.org/html/draft-ietf-idr-last-as-reservation-01
>=20
> 4. As I said, I like the idea of creating a "Special-Purpose AS Number =
Registry", but it should have certain information recoded about each AS =
number range.  This information should be similar to the format =
described in Section 2.2.1 of RFC6890 for the "Special-Purpose IP =
Address Registries" for IPv4 and IPv6, that you reference elsewhere in =
the draft.
>=20
> First, there should be general information describing each of the =
special-purpose ASN ranges, essentially the first half of the columns =
specified in Section 2.2.1 of RFC6890;
>=20
> o AS Number Range - An AS number or range of AS numbers that has been
>   registered for a special purpose.
>=20
> o Name - A descriptive name for the special-purpose AS number range.
>=20
> o RFC - The RFC through which the special-purpose AS number range was
>   requested.
>=20
> o Allocation Date - The date upon which the special-purpose AS number
>   range was allocated.
>=20
> o Termination Date - The date upon which the allocation is to be
>   terminated.  This field is applicable for limited-use allocations
>   only.
>=20
> Then, information specific to how the special-purpose ASNs are to be =
used.  There may be others as well, I but I think these are the minimum.
>=20
> o Local - A boolean value indicating whether an AS number from the
>   allocated special-purpose AS Number range is valid when used as the
>   value of the "My Autonomous System" field of a BGP OPEN message, or
>   equivalently in the Capability Value of the "support for four-octet
>   AS number capability".
>=20
> o Global - A boolean value indicating whether an ASN from the =
allocated
>   special-purpose ASN range is valid in the AS_PATH or AS4_PATH
>   attributes when advertised to the global Internet.
>=20
> o Reserved-by-Protocol - A boolean value indicating whether the
>   special-purpose address block is reserved by BGP, itself.  This
>   value is "TRUE" if the RFC that created the special-purpose ASN
>   range requires all compliant implementations to behave in a special
>   way when this ASN is used.
>=20
> I believe this is the table for these last three items
>=20
>   ASN Range              Local    Global   Reserved-by-Protocol
>   ---------------------  -------  -------  --------------------
>   0                      FALSE    FALSE    TRUE
>   23456                  TRUE[1]  TRUE[1]  TRUE
>   64496-64511            FALSE    FALSE    FALSE
>   64512-65534            TRUE     FALSE    FALSE
>   65535                  FALSE    FALSE    FALSE
>   65536-65551            FALSE    FALSE    FALSE
>   4200000000-4294967294  TRUE     FALSE    FALSE
>   4294967295             FALSE    FALSE    FALSE
>=20
>   [1] Only valid in a BGP OPEN message or AS_PATH, not valid within a
>   four-octet AS number capability negotiation or AS4_PATH.
>=20
>=20
> Thanks.
>=20
> --=20
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 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
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From hallam@gmail.com  Mon Feb  3 13:43:43 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 9CFDB1A0234 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 13:43:43 -0800 (PST)
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 9JY6KQxuURP9 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 13:43:42 -0800 (PST)
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 AEFE11A01EE for <ietf@ietf.org>; Mon,  3 Feb 2014 13:43:41 -0800 (PST)
Received: by mail-lb0-f173.google.com with SMTP id y6so5797175lbh.18 for <ietf@ietf.org>; Mon, 03 Feb 2014 13:43:40 -0800 (PST)
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=aXch4fJlcsGy2fc87WNsY153+KkAquO0C5e8TJCy/zE=; b=JftqDfkTTnbjd2YIbRM8JJIXwwPVaIk3fcBkSOcDSTh0CMn7antNluJQ6tJsZQZwGq P5WotF7jZ40+6k6f3+crUXhH9xzhDe+076JmtSs+rU96H7fDDGOJ8PAMxaYcD3IDpDaq YHuOfZEJUbzdOXSFVtkmEMOu6bA+Af8n2vCQFzgghfwxua9wkxvB4fW7Fym66YhOYygc fPehLMEb/EE7SctstykMXv72sTl/USbfFfw6VWqklMCmpF6cbNp0M4C8BginvfT4hxk4 MBin/+HvLEK944St4QjR4wRsl/YJRJVmFGeh3ZkORTD62RrgMd+GGbKl+M/crLz6M6Rs IVrg==
MIME-Version: 1.0
X-Received: by 10.112.144.35 with SMTP id sj3mr2966729lbb.44.1391463820669; Mon, 03 Feb 2014 13:43:40 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 3 Feb 2014 13:43:40 -0800 (PST)
In-Reply-To: <4B79E458-F241-4C20-B634-B49B1DA09394@nominum.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <52EE065B.1050707@frobbit.se> <52EE07AC.2020701@dcrocker.net> <CAMm+LwjF_E7q1vbef6-sQ9wXYbtBsJEgny768iv4aNh1e5SSmw@mail.gmail.com> <201402031903.s13J3Jr04204938@shell01.TheWorld.com> <4B79E458-F241-4C20-B634-B49B1DA09394@nominum.com>
Date: Mon, 3 Feb 2014 16:43:40 -0500
Message-ID: <CAMm+LwgCcjs=Znv4CX-bzNaV9Pj8hHeuYy0OL=rr5R4YbKWi1Q@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=047d7b3432bebfb94d04f1876a3e
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, 03 Feb 2014 21:43:43 -0000

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

On Mon, Feb 3, 2014 at 2:46 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Feb 3, 2014, at 2:03 PM, Dale R. Worley <worley@ariadne.com> wrote:
> > Unfortunately, "my bank, my doctor, my brokerage" have all implemented
> > confidential email, but they are horrible webmail systems.  That means
> > that a considerable amount of the benefit that will be obtainable from
> > confidential email is already being obtained, making it harder for
> > proper confidential email to gain acceptance in the market.
>
> Actually it's not being obtained.   These systems work quite poorly, and
> typically aren't all that secure.   I do not think they are widely used by
> customers, because their usability is so bad.
>

They are not secure at present.

But there is considerable money available to make them secure.

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

--047d7b3432bebfb94d04f1876a3e
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, Feb 3, 2014 at 2:46 PM, Ted Lemon <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.c=
om</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"im">On Feb 3, 2014, at 2:03 PM=
, Dale R. Worley &lt;<a href=3D"mailto:worley@ariadne.com">worley@ariadne.c=
om</a>&gt; wrote:<br>

&gt; Unfortunately, &quot;my bank, my doctor, my brokerage&quot; have all i=
mplemented<br>
&gt; confidential email, but they are horrible webmail systems. =A0That mea=
ns<br>
&gt; that a considerable amount of the benefit that will be obtainable from=
<br>
&gt; confidential email is already being obtained, making it harder for<br>
&gt; proper confidential email to gain acceptance in the market.<br>
<br>
</div>Actually it&#39;s not being obtained. =A0 These systems work quite po=
orly, and typically aren&#39;t all that secure. =A0 I do not think they are=
 widely used by customers, because their usability is so bad.<br>
</blockquote></div><br>They are not secure at present.</div><div class=3D"g=
mail_extra"><br></div><div class=3D"gmail_extra">But there is considerable =
money available to make them secure.</div><div class=3D"gmail_extra"><div><=
br>
</div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambake=
r.com/</a><br>
</div></div>

--047d7b3432bebfb94d04f1876a3e--

From Ted.Lemon@nominum.com  Mon Feb  3 13:59:06 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 BD2AC1A01EE for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 13:59:06 -0800 (PST)
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 AgbFRM2-qWmY for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 13:59:05 -0800 (PST)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id 18F311A0218 for <ietf@ietf.org>; Mon,  3 Feb 2014 13:59:05 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUvARKeRjiykq8LR2cA1lAhK8G6tHZSLh@postini.com; Mon, 03 Feb 2014 13:59:05 PST
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 EAF041B82FF for <ietf@ietf.org>; Mon,  3 Feb 2014 13:59:04 -0800 (PST)
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 DFF6D190043; Mon,  3 Feb 2014 13:59:04 -0800 (PST)
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, 3 Feb 2014 13:59:04 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Agenda, security, and monitoring
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAMm+LwgCcjs=Znv4CX-bzNaV9Pj8hHeuYy0OL=rr5R4YbKWi1Q@mail.gmail.com>
Date: Mon, 3 Feb 2014 16:59:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <BCF4112A-2980-4152-850E-48E58F6166E8@nominum.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <52EE065B.1050707@frobbit.se> <52EE07AC.2020701@dcrocker.net> <CAMm+LwjF_E7q1vbef6-sQ9wXYbtBsJEgny768iv4aNh1e5SSmw@mail.gmail.com> <201402031903.s13J3Jr04204938@shell01.TheWorld.com> <4B79E458-F241-4C20-B634-B49B1DA09394@nominum.com> <CAMm+LwgCcjs=Znv4CX-bzNaV9Pj8hHeuYy0OL=rr5R4YbKWi1Q@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
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, 03 Feb 2014 21:59:06 -0000

On Feb 3, 2014, at 4:43 PM, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:
> But there is considerable money available to make them secure.

Sure, but as long as there is no regulatory pressure to do so and the =
end-user has to pay for the occasional slip-up, nothing will change.   =
During that period, the opportunity exists to improve the state of the =
art in email security.   Should we succeed before the first really big =
bank security disaster, it is possible that our solution will appear =
expedient.



From hallam@gmail.com  Mon Feb  3 14:21:43 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 47D571A0264 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 14:21:43 -0800 (PST)
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 5-7bJKW-giqH for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 14:21:41 -0800 (PST)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id 31FD41A0248 for <ietf@ietf.org>; Mon,  3 Feb 2014 14:21:40 -0800 (PST)
Received: by mail-la0-f46.google.com with SMTP id b8so5934160lan.33 for <ietf@ietf.org>; Mon, 03 Feb 2014 14:21:40 -0800 (PST)
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=NzcMeDrUMnTfH3fQQzwNHNwue5sMiUWDdLxSuX/tmGc=; b=E1gPN5v4AhV+t9oHPMCYPvQSyHkDYQm/jU/KtklFfJUFXtKcbio9w3K5cLgVbciW3G FJuWAP4BTwUXMJMbxIuYIbW3F4nCtrgnFJBP3dlDvNOSwMYPTjlsY1VuqlwKO6k0v/oJ BVBtkHyax5THTpYGDay305QXlPMtHIrFjh4BGEKT9L/waNdotaqx4FW4SRWLZ2I9O0Lz h9L+BOoFbLwOxZj4W8vwMqvnm6bwfmZQnPNxfQ7KRddgzhWXyWx6gJePh3Rq8jJDUVz0 LRWZjS9GUW4fx4jIfnC+McCp0k8L58bGxD3kVOXgnL5ld36Yuv0Qw6D2DYh9hTYcHt0q 0RcA==
MIME-Version: 1.0
X-Received: by 10.152.121.105 with SMTP id lj9mr3282788lab.37.1391466100342; Mon, 03 Feb 2014 14:21:40 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 3 Feb 2014 14:21:40 -0800 (PST)
In-Reply-To: <BCF4112A-2980-4152-850E-48E58F6166E8@nominum.com>
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52ED8496.6000006@dcrocker.net> <52EE065B.1050707@frobbit.se> <52EE07AC.2020701@dcrocker.net> <CAMm+LwjF_E7q1vbef6-sQ9wXYbtBsJEgny768iv4aNh1e5SSmw@mail.gmail.com> <201402031903.s13J3Jr04204938@shell01.TheWorld.com> <4B79E458-F241-4C20-B634-B49B1DA09394@nominum.com> <CAMm+LwgCcjs=Znv4CX-bzNaV9Pj8hHeuYy0OL=rr5R4YbKWi1Q@mail.gmail.com> <BCF4112A-2980-4152-850E-48E58F6166E8@nominum.com>
Date: Mon, 3 Feb 2014 17:21:40 -0500
Message-ID: <CAMm+LwiAv+NZHHbgk_=zuu8XeY-HJLgGd=UTH=UTks6odt4piw@mail.gmail.com>
Subject: Re: Agenda, security, and monitoring
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=089e01227716a0c23d04f187f2ca
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, 03 Feb 2014 22:21:43 -0000

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

On Mon, Feb 3, 2014 at 4:59 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Feb 3, 2014, at 4:43 PM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> > But there is considerable money available to make them secure.
>
> Sure, but as long as there is no regulatory pressure to do so and the
> end-user has to pay for the occasional slip-up, nothing will change.
> During that period, the opportunity exists to improve the state of the art
> in email security.   Should we succeed before the first really big bank
> security disaster, it is possible that our solution will appear expedient
>


You mean before the London Whale loses $2 billion in rogue trading
losses...

I am just waiting for one of these mega trading losses due to fraud to
cause the likes of a Citi to go under.

At least Alexander had the decency to (eventually) offer his resignation
after the consequences of his incompetence became apparent. The city types
give themselves bonuses. Large ones.

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

--089e01227716a0c23d04f187f2ca
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, Feb 3, 2014 at 4:59 PM, Ted Lemon <span dir=3D"ltr">&lt;<a =
href=3D"mailto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.c=
om</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"im">On Feb 3, 2014, at 4:43 PM=
, Phillip Hallam-Baker &lt;<a href=3D"mailto:hallam@gmail.com">hallam@gmail=
.com</a>&gt; wrote:<br>

&gt; But there is considerable money available to make them secure.<br>
<br>
</div>Sure, but as long as there is no regulatory pressure to do so and the=
 end-user has to pay for the occasional slip-up, nothing will change. =A0 D=
uring that period, the opportunity exists to improve the state of the art i=
n email security. =A0 Should we succeed before the first really big bank se=
curity disaster, it is possible that our solution will appear expedient<br>
</blockquote><div><br></div><div><br></div><div>You mean before the London =
Whale loses $2 billion in rogue trading losses...=A0</div></div><div><br></=
div><div>I am just waiting for one of these mega trading losses due to frau=
d to cause the likes of a Citi to go under.</div>
<div><br></div><div>At least Alexander had the decency to (eventually) offe=
r his resignation after the consequences of his incompetence became apparen=
t. The city types give themselves bonuses. Large ones.</div><div><br></div>
-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/=
</a><br>
</div></div>

--089e01227716a0c23d04f187f2ca--

From rjsparks@nostrum.com  Mon Feb  3 15:11: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 48AA71A0290 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 15:11:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.036
X-Spam-Level: 
X-Spam-Status: No, score=-1.036 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553, 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 aEFQy03vvKz0 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 15:11:00 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 77C8B1A0265 for <ietf@ietf.org>; Mon,  3 Feb 2014 15:11:00 -0800 (PST)
Received: from unnumerable.local (pool-173-71-10-88.dllstx.fios.verizon.net [173.71.10.88]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id s13NB0Sa047746 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=OK) for <ietf@ietf.org>; Mon, 3 Feb 2014 17:11:00 -0600 (CST) (envelope-from rjsparks@nostrum.com)
Message-ID: <52F0220D.6090304@nostrum.com>
Date: Mon, 03 Feb 2014 17:11:09 -0600
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.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Email header randon(?) changes
References: <20140203175655.8511.qmail@joyce.lan> <52EFEA34.8030700@gmail.com>
In-Reply-To: <52EFEA34.8030700@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Received-SPF: pass (shaman.nostrum.com: 173.71.10.88 is authenticated by a trusted mechanism)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 03 Feb 2014 23:11:01 -0000

But it shouldn't be too hard to make them the same.
I'll add that to things someone could pick up at the next codesprint.

RjS

On 2/3/14, 1:12 PM, Brian E Carpenter wrote:
> I believe that there are two formats because one of them
> is generated by the automatic posting tool (when successful)
> and the other one is generated by an older tool used by
> the Secretariat for manual posting (when automatic posting
> fails for some reason).
>
>      Brian
>
> On 04/02/2014 06:56, John Levine wrote:
>>> The CAPS do not bother me, nor does the switch between
>>>
>>> Content-Type: text/plain; charset="us-ascii"
>>> and
>>> Content-Type: multipart/mixed; boundary="NextPart"
>>>
>>> but that little old space does.  And this is not new.
>>>
>>> Any ideas?
>> Learn about regular expressions?
>>
>> Helpfully,
>> John
>>
>> PS: the state of the art in the regard seems to be procmail, an amazing
>> piece of work in daily use around the world, with source code essentially
>> unchanged in over 20 years.
>>


From joe@cdt.org  Mon Feb  3 17:21:25 2014
Return-Path: <joe@cdt.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 D416D1A02E6 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 17:21:25 -0800 (PST)
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_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 fqyXHCDBJ64s for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 17:21:24 -0800 (PST)
Received: from mail.maclaboratory.net (mail.maclaboratory.net [209.190.215.232]) by ietfa.amsl.com (Postfix) with ESMTP id 4867C1A02DF for <ietf@ietf.org>; Mon,  3 Feb 2014 17:21:24 -0800 (PST)
X-Footer: Y2R0Lm9yZw==
Received: from [10.0.1.2] ([173.66.171.101]) (authenticated user jhall@cdt.org) by mail.maclaboratory.net (using TLSv1 with cipher AES128-SHA (128 bits)); Mon, 3 Feb 2014 20:21:22 -0500
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <201402031902.s13J2VRK4208381@shell01.TheWorld.com> <20140203195625.GA26065@thunk.org>
Mime-Version: 1.0 (1.0)
In-Reply-To: <20140203195625.GA26065@thunk.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-Id: <249FA1C6-29F3-489A-B2F9-92CA0EE7D637@cdt.org>
X-Mailer: iPhone Mail (11B554a)
From: Joseph Lorenzo Hall <joe@cdt.org>
Subject: Re: Agenda, security, and monitoring
Date: Mon, 3 Feb 2014 20:21:21 -0500
To: Theodore Ts'o <tytso@mit.edu>
Cc: John C Klensin <john-ietf@jck.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, 04 Feb 2014 01:21:26 -0000

It's Executive Order 12333 not 12003, which is quite different.

Also, we have sources that say they do the same bulk collection with credit c=
ard purchase transaction metadata (WSJ reported the Thursday of the week las=
t June that began the Snowden disclosures). Although that's not commsec.

Responding to and earlier email on this thread out of order (sorry Theodore)=
, I think devaluing the power of metadata and traffic analysis is a bad path=
 to start down on. Content often has to be further interpreted and in many c=
ases context can be inferred from metadata. Matt Blaze has a great Wired opi=
nion article that makes a number of very good points with respect to what on=
e can learn via metadata. best, Joe

> On Feb 3, 2014, at 14:56, Theodore Ts'o <tytso@mit.edu> wrote:
>=20
>> On Mon, Feb 03, 2014 at 02:02:31PM -0500, Dale R. Worley wrote:
>>=20
>> The recent news reports that I have seen are that the NSA's pervasive
>> monitoring focuses on "metatada", "who is talking to whom".  And the
>> trouble with end-to-end confidentiality mechanisms is that they do not
>> hide the destination address; indeed they can't.  And it seems to me
>> that almost no confidentiality systems have been focused on
>> confidentiality of message destinations.
>=20
> That's what NSA is doing for telephones, and briefly using e-mail
> analyzing communications between US preson under their authorities
> (or claimed authorities) under section 215 of the Patriot Act.
>=20
> It would be a mistake to assume this is *all* they are doing.  Indeed,
> it's likely that the NSA is actually doing keyword based filtering of
> content, for communications that are between non-US persons and where
> the endpoints are outside of the US.  This is done under their
> authorities granted to them under Executive Order 12003.
>=20
> Given that the FBI wanted to drop "Carnivore" servers in US data
> centers to do this kind of keyword based filtering many years ago,
> it's certainly within the capabilities the US Intelligence Community.
>=20
> So to the extent that non-US persons want the same level of privacy
> that apparently US persons have (unless there is some other secret
> court order with some other secret law interpretation we're not aware
> of which is enabling the FBI to do this kind of snooping, and we just
> don't know about it yet), it's not surprising people are interested in
> encrypting e-mail bodies.
>=20
> Encrypting the endpoint identities is a lot more difficult, since you
> need to route the information somehow.  There are solutions such as
> onion routing, but they ease of use isn't quite there, and I don't
> think they currently would scale well if huge numbers of people were
> using them.
>=20
> Certainly hiding the RFC-822 headers, including the subject lines,
> inside the encrypted body would certainly be a good start, but of
> course that doesn't solve the issue of the SMTP envelop information.
>=20
>                                         - Ted


From farmer@umn.edu  Mon Feb  3 17:51:19 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 A08F91A0346 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 17:51:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ENn8hJVpZX59 for <ietf@ietfa.amsl.com>; Mon,  3 Feb 2014 17:51:17 -0800 (PST)
Received: from vs-w.tc.umn.edu (vs-w.tc.umn.edu [134.84.135.88]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB111A0345 for <ietf@ietf.org>; Mon,  3 Feb 2014 17:51:17 -0800 (PST)
Received: from mail-ig0-f182.google.com (mail-ig0-f182.google.com [209.85.213.182]) by vs-w.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Mon, 3 Feb 2014 19:51:12 -0600 (CST)
X-Umn-Remote-Mta: [N] mail-ig0-f182.google.com [209.85.213.182] #+LO+TS+TR
X-Umn-Classification: local
Received: by mail-ig0-f182.google.com with SMTP id uy17so5928686igb.3 for <ietf@ietf.org>; Mon, 03 Feb 2014 17:51:12 -0800 (PST)
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=VgzoC6zyQ7QoS3CTQVDAxluKZzkw5ACAxhKk+fd7w5w=; b=bRNBlGt/Z7ocJ7EJy6Yc2J+RGvSfahtIXYXsaAZkj/ohIQzEczG2qz2Rjh7GRjKWRB KMXURY/1B8eYHX+W3N7FR3l72f5/qMGfVSKRfMavBUN6mw+n0jS9s1irRWaPmOFi6dpe NXMQBdog9EJOw0coOV9pDR1FhnOcWgNUED9xxgZIFTq0C4WxAaFLBP5/oJ58u8fsrWY7 TqQGzHPGyiI1nNAWg1TBvsjs2Vw+3n/pA2jDHc0WsQrfjAwtLjaW/G5Vannmpcp4oLqY I8GyohRul3qZY53b/k8f2VaRx4HaeulgGaSep2A2kfMIPURV296CzgXF2PvNIrsnoKRw LmKw==
X-Gm-Message-State: ALoCoQnb6lFDjxgWj9Eh1TOjaL2nB+/RkkmWTNHaNf9BrDDOPkJPIwNB/m9eQug3v1rCDzLDXKVhmOvSlPtzIQ8Q8b6WpedraabfNWfCxSdN3RFq+0X4yg7gf+mrwvS+WFN9/0JKbw1S
X-Received: by 10.42.61.4 with SMTP id s4mr100640ich.58.1391478672058; Mon, 03 Feb 2014 17:51:12 -0800 (PST)
X-Received: by 10.42.61.4 with SMTP id s4mr100633ich.58.1391478671871; Mon, 03 Feb 2014 17:51:11 -0800 (PST)
Received: from x-160-94-249-74.uofm-secure.wireless.umn.edu ([2607:ea00:104:2000:892d:8e4a:7234:9eb]) by mx.google.com with ESMTPSA id y7sm35996967igl.8.2014.02.03.17.51.10 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 03 Feb 2014 17:51:11 -0800 (PST)
Message-ID: <52F0478D.2020701@umn.edu>
Date: Mon, 03 Feb 2014 19:51:09 -0600
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.2.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk> <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com> <028c01cf1a0a$048899d0$0d99cd70$@olddog.co.uk> <52E6D628.80103@umn.edu> <7DA9D44B-1B9D-43BE-B41D-290684A41972@vigilsec.com>
In-Reply-To: <7DA9D44B-1B9D-43BE-B41D-290684A41972@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
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: Tue, 04 Feb 2014 01:51:19 -0000

I believe if RFC 6890 were used as a template, a Draft could be put 
together quickly, I'm personally willing to help.  I don't see why it 
should be controversial within the community, but unfortunately those 
can be famous last words. :)

On 2/3/14, 14:20 , Russ Housley wrote:
> David:
>
> With respect to the AS Special purpose Registry, I might sit more comfortably in its own document, and then it could be referenced from this document. At this point, I'm concerned that he delay to this document would be quite unfortunate.  Do you believe that such a document can be produced and approved rapidly?  If not, then I'd like to see this document move forward and a subsequent document could make an update if there is community consensus to evolve the form of the special-purpose AS number registry.
>
> Russ
>
>
>
>> On 1/25/14, 14:14 , Adrian Farrel wrote:
>>> Hi Russ,
>>>
>>> Thanks for this. The -03 revision just posted addresses my comments.
>>>
>>> Adrian
>>
>> Russ,
>>
>> I also like the -03 revision, its has generally moved everything in the right direction.  But I have a few comments on it.
>>
>> 1. The part about RFC2860 in Section 1 seems like an incomplete thought, at the very least it seems awkward to me.  I'm really not sure what you are intending to say.  But, I agree RFC2860 is relevant to the discussion.  I'm just not sure you have nailed what to say about it.
>>
>> 2. I really like the idea of creating a "Special-Purpose AS Number Registry".  However, it may be a better idea to spin-off the creation of a "Special-Purpose AS Number Registry" into a separate draft.  I'm concerned that trying to do two important things in the same document will fail to achieve one or both of the important things.  For instance the simple section 3 you have currently worries me.  I'd really think RFC6890 is the template to use for creating a "Special-Purpose AS Number Registry", more below.
>>
>> If you spin-off the creation of a "Special-Purpose AS Number Registry", the following items are for that draft.
>>
>> 3. There is a draft in WG Last Call in the IDR that documents the reservations of ASNs 65535 and 4294967295, the "Last ASNs".
>> http://tools.ietf.org/html/draft-ietf-idr-last-as-reservation-01
>>
>> 4. As I said, I like the idea of creating a "Special-Purpose AS Number Registry", but it should have certain information recoded about each AS number range.  This information should be similar to the format described in Section 2.2.1 of RFC6890 for the "Special-Purpose IP Address Registries" for IPv4 and IPv6, that you reference elsewhere in the draft.
>>
>> First, there should be general information describing each of the special-purpose ASN ranges, essentially the first half of the columns specified in Section 2.2.1 of RFC6890;
>>
>> o AS Number Range - An AS number or range of AS numbers that has been
>>    registered for a special purpose.
>>
>> o Name - A descriptive name for the special-purpose AS number range.
>>
>> o RFC - The RFC through which the special-purpose AS number range was
>>    requested.
>>
>> o Allocation Date - The date upon which the special-purpose AS number
>>    range was allocated.
>>
>> o Termination Date - The date upon which the allocation is to be
>>    terminated.  This field is applicable for limited-use allocations
>>    only.
>>
>> Then, information specific to how the special-purpose ASNs are to be used.  There may be others as well, I but I think these are the minimum.
>>
>> o Local - A boolean value indicating whether an AS number from the
>>    allocated special-purpose AS Number range is valid when used as the
>>    value of the "My Autonomous System" field of a BGP OPEN message, or
>>    equivalently in the Capability Value of the "support for four-octet
>>    AS number capability".
>>
>> o Global - A boolean value indicating whether an ASN from the allocated
>>    special-purpose ASN range is valid in the AS_PATH or AS4_PATH
>>    attributes when advertised to the global Internet.
>>
>> o Reserved-by-Protocol - A boolean value indicating whether the
>>    special-purpose address block is reserved by BGP, itself.  This
>>    value is "TRUE" if the RFC that created the special-purpose ASN
>>    range requires all compliant implementations to behave in a special
>>    way when this ASN is used.
>>
>> I believe this is the table for these last three items
>>
>>    ASN Range              Local    Global   Reserved-by-Protocol
>>    ---------------------  -------  -------  --------------------
>>    0                      FALSE    FALSE    TRUE
>>    23456                  TRUE[1]  TRUE[1]  TRUE
>>    64496-64511            FALSE    FALSE    FALSE
>>    64512-65534            TRUE     FALSE    FALSE
>>    65535                  FALSE    FALSE    FALSE
>>    65536-65551            FALSE    FALSE    FALSE
>>    4200000000-4294967294  TRUE     FALSE    FALSE
>>    4294967295             FALSE    FALSE    FALSE
>>
>>    [1] Only valid in a BGP OPEN message or AS_PATH, not valid within a
>>    four-octet AS number capability negotiation or AS4_PATH.
>>
>>
>> Thanks.
>>
>> --
>> ================================================
>> 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
>> ================================================
>


-- 
================================================
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 nomcom-chair-2013@ietf.org  Mon Feb  3 17:56:51 2014
Return-Path: <nomcom-chair-2013@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 2FB291A022A; Mon,  3 Feb 2014 17:56:51 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id I0wSSZO17FMu; Mon,  3 Feb 2014 17:56:50 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 452F21A01C0; Mon,  3 Feb 2014 17:56:50 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2013 <nomcom-chair-2013@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: NOMCOM - IAOC Appointment
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140204015649.23220.95999.idtracker@ietfa.amsl.com>
Date: Mon, 03 Feb 2014 17:56:49 -0800
Cc: IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: Nomcom Chair 2013 <nomcom-chair-2013@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, 04 Feb 2014 01:56:51 -0000

The 2013-14 IETF Nominating Committee (Nomcom) is pleased to announce its
selection to serve on the IETF  Administrative Oversight Committee (IAOC)/
IETF Trust.

The Nomcom has selected Chris Griffiths to take up a two year term on the 
IAOC. This  selection has been confirmed by the IESG in its role as the
confirming body for the Nomcom's IAOC selection.  

The members of the Nomcom, voting and non-voting, are thankful to Chris 
for agreeing to continue his service, as well as to the many talented and
qualified members of the community who offered to serve on the IAOC. 

Additionally, our thanks go out to the many members of the community
who have supported the Nomcom process.

Allison, for the Nomcom

From vesely@tana.it  Tue Feb  4 05:01:08 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 9840A1A0383 for <ietf@ietfa.amsl.com>; Tue,  4 Feb 2014 05:01:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.257
X-Spam-Level: 
X-Spam-Status: No, score=-0.257 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, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535, 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 TdVwoAkQeVe7 for <ietf@ietfa.amsl.com>; Tue,  4 Feb 2014 05:01:07 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 40A311A036D for <ietf@ietf.org>; Tue,  4 Feb 2014 05:01:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1391518864; bh=91q2nAzT1wD1xqq9WXJssdIJvKNsB4ZjT+qKsi42P2M=; l=1477; h=Date:From:To:References:In-Reply-To; b=l7cXKeg2o1AyGHHugCQ2J6+sqC6qigtRYKAm2m6NjOXM1Pn4XcDG0eohzEjitJJvl icjhyDMfkhBEEuUMvKl+KikIYCxgJ1y8n/YFBmqKNoFUDizgKIlKHlrJnKk9NusBfC QASjXR5Kwu6hDwAwCQZdv18LbbbKoN6Q97POO4uM=
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, 04 Feb 2014 14:01:04 +0100 id 00000000005DC033.0000000052F0E490.00007578
Message-ID: <52F0E48F.10308@tana.it>
Date: Tue, 04 Feb 2014 14:01:03 +0100
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: Agenda, security, and monitoring
References: <19A23B84A41C1D4EA513F2C8@JcK-HP8200.jck.com> <52EDAD15.6060504@cs.tcd.ie> <BDD8B7355B350BB55CC3722F@JcK-HP8200.jck.com> <52EEE68A.4070509@qti.qualcomm.com> <52EFC4D3.9030305@dcrocker.net>
In-Reply-To: <52EFC4D3.9030305@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Feb 2014 13:01:08 -0000

On Mon 03/Feb/2014 17:33:23 +0100 Dave Crocker wrote:
> 
> So:  Define the exact anti-PM service to be sought, define the actors
> needed to implement, and then get community agreement that it's an
> important goal to work towards.  Then we can discuss whether it's
> integration or usability or...

+1, we take for granted that PM is dangerous, but I haven't seen a
convincing explanation of that threat.  I read Matt Blaze's "Phew, NSA
Is Just Collecting Metadata. (You Should Still Worry)" and I was
worried already.  Yet, I'm unable to say why everybody else should be
worried too:  They can work out my private habits and my circles, so what?

Is there risk of contamination, like with AIDS?  Hm... We can argue
that psychological profiles can ease political campaigns, so those who
are entitled to vote have the moral duty to protect their independence
of thought, for the sake of democracy.  That's not a convincing
explanation for most people, though.

Using PGP augments metadata by bringing in a signature and the whole
circle of those who signed it.  Keysigning parties build a kind of
social network, which is transparent to interceptors.

Trust in CAs is not obvious, and easily it ends up adding "spend more"
to the already great "the best technology we have is annoying  and
will require you and your correspondents to learn more, and fuss
more, than you would probably like".

And encrypted messages cannot be checked against viruses.

Ale

From drc@virtualized.org  Tue Feb  4 05:26:01 2014
Return-Path: <drc@virtualized.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 A44EC1A041E for <ietf@ietfa.amsl.com>; Tue,  4 Feb 2014 05:26:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, 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 6U0L-MX75FmB for <ietf@ietfa.amsl.com>; Tue,  4 Feb 2014 05:25:59 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id 274731A0438 for <ietf@ietf.org>; Tue,  4 Feb 2014 05:25:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 761AB84B43; Tue,  4 Feb 2014 08:25:58 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 11019-05; Tue,  4 Feb 2014 08:25:58 -0500 (EST)
Received: from [192.168.6.215] (ip-64-134-151-141.public.wayport.net [64.134.151.141]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 84F248445C; Tue,  4 Feb 2014 08:25:57 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_E9AF93E9-F76C-4464-8661-DD23ADF78688"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
From: David Conrad <drc@virtualized.org>
In-Reply-To: <52E6D628.80103@umn.edu>
Date: Tue, 4 Feb 2014 06:25:54 -0700
Message-Id: <232790DB-8FA2-40E4-A278-6E398B3F82E6@virtualized.org>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk> <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com> <028c01cf1a0a$048899d0$0d99cd70$@olddog.co.uk> <52E6D628.80103@umn.edu>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.1827)
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, 04 Feb 2014 13:26:01 -0000

--Apple-Mail=_E9AF93E9-F76C-4464-8661-DD23ADF78688
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

David,

On Jan 27, 2014, at 4:56 PM, David Farmer <farmer@umn.edu> wrote:
> 1. The part about RFC2860 in Section 1 seems like an incomplete =
thought, at the very least it seems awkward to me.  I'm really not sure =
what you are intending to say.  But, I agree RFC2860 is relevant to the =
discussion.  I'm just not sure you have nailed what to say about it.

I suspect it might be a bit hard for Russ to take action on this point =
without a bit more info as to what you feel is awkward or what's =
missing.

> 2. I really like the idea of creating a "Special-Purpose AS Number =
Registry".  However, it may be a better idea to spin-off the creation of =
a "Special-Purpose AS Number Registry" into a separate draft.  I'm =
concerned that trying to do two important things in the same document =
will fail to achieve one or both of the important things.=20

While I don't oppose splitting the docs, I'm not sure it's necessary as =
I don't believe there's anything controversial in Russ's draft. What do =
you foresee as blocking the document or causing it to fail in either of =
its goals?

> For instance the simple section 3 you have currently worries me.  I'd =
really think RFC6890 is the template to use for creating a =
"Special-Purpose AS Number Registry", more below.

Seem's a bit of overkill to me (I like short documents).

Regards,
-drc


--Apple-Mail=_E9AF93E9-F76C-4464-8661-DD23ADF78688
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

iQEcBAEBAgAGBQJS8OpjAAoJENV6ebf0/4rX8MQH/3Jlf3E4ccMDX2wZcxDeYyVj
lmz1eMnQ/RYwBatqbwn9oL9kt5JOL5JE+8eNrsABDohgjQAlWuGybW4sEEH63bCF
yRlD2+JAruUWh2MjF3eoRbeNqHSg7WX86jHwkhW37yzlM9nt3JB2bEMVKqrZNKF9
iHttaACll2FwtC9MDIcgi5vRg7m5BlOm5acJA7m0tx9iqL+zVmuIaA3j+MhWxVbD
2ShpPMoH/iz6ECxQ/982c5Xu1Rg+67uiKrVIFcf7VTsbVWbQyqQQo2QxozWThbxr
fO29AmTsue66m7kWG/22uWG49LGgeYTidp87BcJVPceHW1yLvrriqAH/KZAUFgM=
=vM8J
-----END PGP SIGNATURE-----

--Apple-Mail=_E9AF93E9-F76C-4464-8661-DD23ADF78688--

From hallam@gmail.com  Tue Feb  4 06:23:43 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 15C911A00FD for <ietf@ietfa.amsl.com>; Tue,  4 Feb 2014 06:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.921
X-Spam-Level: 
X-Spam-Status: No, score=0.921 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, 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 n-LS4-k_x26Q for <ietf@ietfa.amsl.com>; Tue,  4 Feb 2014 06:23:41 -0800 (PST)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id 21FEB1A00EE for <ietf@ietf.org>; Tue,  4 Feb 2014 06:23:40 -0800 (PST)
Received: by mail-lb0-f169.google.com with SMTP id q8so6624244lbi.28 for <ietf@ietf.org>; Tue, 04 Feb 2014 06:23:40 -0800 (PST)
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=x+8ymJOLT3G2B9mKOW7UpjKcQOk3G4F8alXlg2O2l6I=; b=jWU15cmbV4k84dcp6LERBoSNizbhnDt2ZKtYo0YTnjZi0ziJJSwIhxIaVv8f4L9jki cOz7ZqKTW5J0fY00WSkZInzyDY2c78sdMi7feAh8xJEhgmJP8qgyyd56OL/J9EDCjjqQ 0WrlU20bO48WlaHdLSL9Q2GBzVaXInlNa0M3se48JcGdn+f6AT+vqAjqXD8gQljVOP14 tPHWCqRboTlvuqN2v//tHyl6ZJMAl6CjSpQWGOr/vnRPoV3OQcv2GH2y7HaJj4uPUE0p OO81y2/VbHOZ3eqWzz96lt0PSJYmI8Q62yCS/yfVhgumDCzgVk3chU90v6vCfWRQsj/x mfFQ==
MIME-Version: 1.0
X-Received: by 10.152.4.68 with SMTP id i4mr14092672lai.8.1391523819888; Tue, 04 Feb 2014 06:23:39 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Tue, 4 Feb 2014 06:23:39 -0800 (PST)
Date: Tue, 4 Feb 2014 09:23:39 -0500
Message-ID: <CAMm+Lwi7LWNzp5cqnjZhNPSYHXe4mtJjeqBK187sQ_P1rWqHAA@mail.gmail.com>
Subject: Setting Priorities, MetaData vs Confidentiality (Was Agenda etc.)
From: Phillip Hallam-Baker <hallam@gmail.com>
Cc: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e01493d46fb235f04f1956218
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Feb 2014 14:23:43 -0000

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

There has been some discussion here about the 'fact' that the NSA is
looking at MetaData and people are discussing PGP and S/MIME as solutions.

I don't see any contradiction here. The NSA is attacking us on multiple
fronts and at multiple levels, the response has to be on multiple fronts
and multiple levels.

Deploying S/MIME does not in any way reduce or eliminate the need for
STARTTLS. We need encryption at both layers, it is not an either/or
situation.


In my ideal configuration, all traffic would be triple encrypted:

Link Layer: The connections between each router node should be encrypted
and flood fill so that an observer cannot perform traffic analysis to guess
the path a packet takes through the network.

Transport Layer: All TCP connections should be over TCP with an
authenticated key exchange under keys bound to the DNS domain of at least
the responder (i.e. server).

Message Layer: All static content data should be encrypted under the
encryption key of the intended recipient.


Note that even this approach does not eliminate every possible attack.
Traffic analysis is still possible but now requires collusion of the
parties running the network nodes. But this is sufficient to meet my
objective which is to prevent warrantless wiretap and to limit the
resources available in the next episode of elite panic.

The reason I am concentrating on end-to-end message security are that this
is where I see the biggest gap and this is the only way the individuals can
take personal control of any aspect of their privacy.

There are some improvements possible in STARTTLS but the low hanging fruit
has been taken. We have a spec, it works. We can improve it a little but
not by a lot.

The gap here is deployment which is something I have no control over
whatsoever as an email user. I can choose to use S/MIME++ but I can't
choose to use STARTTLS or Link layer flood fill. I depend on the
infrastructure providers to do that for me.

>From a movement perspective, the biggest problem I see in the reaction to
Snowdonia is that at present there is no ask. We could easily get thousands
of people to storm the Apple stores and Microsoft stores in the malls. But
what would they be asking Apple or Microsoft to do? We have deep support
among the population at large, they want to do something to protest being
spied on by the US and UK militaries.

S/MIME and PGP are much closer to being right than is commonly thought. If
we put in the effort to make them really right there are millions of people
who will insist on using them just as a fuck-you to Clapper and Alexander
and all the other patronizing men in uniforms who calmly tell us how
trustworthy they are.

Whichever ones of us get asked to appear in Congress should take along
pictures of Abut Ghraib. Those photographs and the determined efforts to
avoid prosecuting those really responsible shows exactly how trustworthy
and honorable the US military is.


End-to-end email is not the only privacy technology we need to deploy but
it is the only ask we can make of the public at large.

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

<div dir=3D"ltr"><div class=3D"gmail_extra">There has been some discussion =
here about the &#39;fact&#39; that the NSA is looking at MetaData and peopl=
e are discussing PGP and S/MIME as solutions.
</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I don=
&#39;t see any contradiction here. The NSA is attacking us on multiple fron=
ts and at multiple levels, the response has to be on multiple fronts and mu=
ltiple levels.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Deploying S=
/MIME does not in any way reduce or eliminate the need for STARTTLS. We nee=
d encryption at both layers, it is not an either/or situation.</div><div cl=
ass=3D"gmail_extra">
<br></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">I=
n my ideal configuration, all traffic would be triple encrypted:</div><div =
class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Link Layer: The =
connections between each router node should be encrypted and flood fill so =
that an observer cannot perform traffic analysis to guess the path a packet=
 takes through the network.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Transport L=
ayer: All TCP connections should be over TCP with an authenticated key exch=
ange under keys bound to the DNS domain of at least the responder (i.e. ser=
ver).</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Message Lay=
er: All static content data should be encrypted under the encryption key of=
 the intended recipient.</div><div class=3D"gmail_extra"><br></div><div cla=
ss=3D"gmail_extra">
<br></div><div class=3D"gmail_extra">Note that even this approach does not =
eliminate every possible attack. Traffic analysis is still possible but now=
 requires collusion of the parties running the network nodes. But this is s=
ufficient to meet my objective which is to prevent warrantless wiretap and =
to limit the resources available in the next episode of elite panic.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The reason =
I am concentrating on end-to-end message security are that this is where I =
see the biggest gap and this is the only way the individuals can take perso=
nal control of any aspect of their privacy.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">There are s=
ome improvements possible in STARTTLS but the low hanging fruit has been ta=
ken. We have a spec, it works. We can improve it a little but not by a lot.=
</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">The gap her=
e is deployment which is something I have no control over whatsoever as an =
email user. I can choose to use S/MIME++ but I can&#39;t choose to use STAR=
TTLS or Link layer flood fill. I depend on the infrastructure providers to =
do that for me.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">From a move=
ment perspective, the biggest problem I see in the reaction to Snowdonia is=
 that at present there is no ask. We could easily get thousands of people t=
o storm the Apple stores and Microsoft stores in the malls. But what would =
they be asking Apple or Microsoft to do? We have deep support among the pop=
ulation at large, they want to do something to protest being spied on by th=
e US and UK militaries.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">S/MIME and =
PGP are much closer to being right than is commonly thought. If we put in t=
he effort to make them really right there are millions of people who will i=
nsist on using them just as a fuck-you to Clapper and Alexander and all the=
 other patronizing men in uniforms who calmly tell us how trustworthy they =
are.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Whichever o=
nes of us get asked to appear in Congress should take along pictures of Abu=
t Ghraib. Those photographs and the determined efforts to avoid prosecuting=
 those really responsible shows exactly how trustworthy and honorable the U=
S military is.=A0</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><br></div><=
div class=3D"gmail_extra">End-to-end email is not the only privacy technolo=
gy we need to deploy but it is the only ask we can make of the public at la=
rge.</div>
</div>

--089e01493d46fb235f04f1956218--

From tjc@ecs.soton.ac.uk  Wed Feb  5 02:48:01 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 AD3531A00D3 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 02:48:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level: 
X-Spam-Status: No, score=0.945 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, RP_MATCHES_RCVD=-0.535, SPF_NEUTRAL=0.779] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YMHGm0vzEO1I for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 02:47:58 -0800 (PST)
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 9E0A91A00CF for <ietf@ietf.org>; Wed,  5 Feb 2014 02:47:57 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s15AlUYo021280; Wed, 5 Feb 2014 10:47:30 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s15AlUYo021280
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1391597250; bh=rrQklH6A2VQKRuLSR/8FRGG9/XU=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=dmN6/79MKc+viajBuu3QFPJgPbn66lZ4v07VaUxi0L80ep4UYiYo29OgiItAFyT03 mqUbuxa47ZDkawHh64YIZLDH2XxEAs3J5JExkGQR7hckBNzyXcuObPPSTAX+zOkD9M FZqZNgeViA9HY35nkJKz+6m52dgRP/CQHtdv8AOw=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id q14AlU0959613751Nv ret-id none; Wed, 05 Feb 2014 10:47:30 +0000
Received: from dhcp-160-219.wireless.soton.ac.uk (dhcp-160-219.wireless.soton.ac.uk [152.78.160.219] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s15AlQ7P005834 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Feb 2014 10:47:26 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_E1E51A4B-73C8-46B4-B7EA-BC31C58F90C2"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IETF 89 London - Enquiry
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <1391180744.24761.1834.camel@mightyatom>
Date: Wed, 5 Feb 2014 10:47:25 +0000
Message-ID: <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q14AlY095961375100; tid=q14AlU0959613751Nv; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s15AlUYo021280
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Cc: "antony@it.bw" <antony@it.bw>, John 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, 05 Feb 2014 10:48:01 -0000

--Apple-Mail=_E1E51A4B-73C8-46B4-B7EA-BC31C58F90C2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1251

On 31 Jan 2014, at 15:05, Elwyn Davies <elwynd@dial.pipex.com> wrote:

> On Fri, 2014-01-31 at 13:51 +0000, Tim Chown wrote:
>> On 31 Jan 2014, at 13:23, Dearlove, Christopher (UK) =
<chris.dearlove@baesystems.com> wrote:
>>=20
>>> John Levine
>>>> It's, ah, quite informal.  Tee shirts and sandals are common when =
the weather is warm enough.
>>>=20
>>> London. March. Expect rain. (The March was almost redundant there.)
>>=20
>> Indeed. Large chunks of England are underwater=85 it=92s been raining =
for some time.
>>=20
>> Tim
>=20
> But in the best traditions of the interactions of British Politics and
> British Weather, a Minister for Floods will have been appointed just =
in
> time for the floods to disappear and we will be experiencing the start
> of a months long heat wave and drought by then.  Never take anything =
for
> granted!=20

Yeah, nothing like the environment minister turning up to a village =
three weeks after it's become an island and wondering why he's getting a =
bit of abuse...

London is fine, just check if you plan on any trips to the country, e.g. =
to see stonehenge, you should check the status.  The BBC has good =
coverage and updates, e.g. http://www.bbc.co.uk/news/uk-25629479.

The only disruption in March may be more tube strikes. You may have to =
walk places on the surface streets....

> Green wellies are de rigueur in place of sandals for flood wear in the
> UK.  Could have done with them back at IETF 65 in Dallas!

I don't think wellies would have helped in Dallas - now THAT was a =
flood. Whole cars were underwater.  Everything's bigger in Texas!

Tim

>=20
> /E
>=20


--Apple-Mail=_E1E51A4B-73C8-46B4-B7EA-BC31C58F90C2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1251

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1251"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space; =
"><div><div>On 31 Jan 2014, at 15:05, Elwyn Davies &lt;<a =
href=3D"mailto:elwynd@dial.pipex.com">elwynd@dial.pipex.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">On Fri, 2014-01-31 at 13:51 +0000, Tim Chown =
wrote:<br><blockquote type=3D"cite">On 31 Jan 2014, at 13:23, Dearlove, =
Christopher (UK) &lt;<a =
href=3D"mailto:chris.dearlove@baesystems.com">chris.dearlove@baesystems.co=
m</a>&gt; wrote:<br><br><blockquote type=3D"cite">John =
Levine<br><blockquote type=3D"cite">It's, ah, quite informal. &nbsp;Tee =
shirts and sandals are common when the weather is warm =
enough.<br></blockquote><br>London. March. Expect rain. (The March was =
almost redundant there.)<br></blockquote><br>Indeed. Large chunks of =
England are underwater=85 it=92s been raining for some =
time.<br><br>Tim<br></blockquote><br>But in the best traditions of the =
interactions of British Politics and<br>British Weather, a Minister for =
Floods will have been appointed just in<br>time for the floods to =
disappear and we will be experiencing the start<br>of a months long heat =
wave and drought by then. &nbsp;Never take anything for<br>granted! =
<br></blockquote><div><br></div>Yeah, nothing like the environment =
minister turning up to a village three weeks after it's become an island =
and wondering why he's getting a bit of =
abuse...</div><div><br></div><div>London is fine, just check if you plan =
on any trips to the country, e.g. to see stonehenge, you should check =
the status. &nbsp;The BBC has good coverage and updates, e.g.&nbsp;<a =
href=3D"http://www.bbc.co.uk/news/uk-25629479">http://www.bbc.co.uk/news/u=
k-25629479</a>.</div><div><br></div><div>The only disruption in March =
may be more tube strikes. You may have to walk places on the surface =
streets....</div><div><br></div><div><blockquote type=3D"cite">Green =
wellies are de rigueur in place of sandals for flood wear in the<br>UK. =
&nbsp;Could have done with them back at IETF 65 in =
Dallas!<br></blockquote><div><br></div>I don't think wellies would have =
helped in Dallas - now THAT was a flood. Whole cars were underwater. =
&nbsp;Everything's bigger in =
Texas!</div><div><br></div><div>Tim</div><div><br><blockquote =
type=3D"cite"><br>/E<br><br></blockquote></div><br></body></html>=

--Apple-Mail=_E1E51A4B-73C8-46B4-B7EA-BC31C58F90C2--

From alexandru.petrescu@gmail.com  Wed Feb  5 04:30:39 2014
Return-Path: <alexandru.petrescu@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 70E4F1A00F3 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 04:30:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: 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_ApbAZhLpIW for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 04:30:37 -0800 (PST)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) by ietfa.amsl.com (Postfix) with ESMTP id CCA4E1A00F2 for <ietf@ietf.org>; Wed,  5 Feb 2014 04:30:36 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s15CUZCG020919 for <ietf@ietf.org>; Wed, 5 Feb 2014 13:30:35 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id C6416203048 for <ietf@ietf.org>; Wed,  5 Feb 2014 13:30:55 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id BEDA6202EC9 for <ietf@ietf.org>; Wed,  5 Feb 2014 13:30:55 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s15CUVHN005967 for <ietf@ietf.org>; Wed, 5 Feb 2014 13:30:35 +0100
Message-ID: <52F22EE7.5040809@gmail.com>
Date: Wed, 05 Feb 2014 13:30:31 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF 89 London - Enquiry
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 12:30:39 -0000

Le 05/02/2014 11:47, Tim Chown a Ã©crit :
> On 31 Jan 2014, at 15:05, Elwyn Davies <elwynd@dial.pipex.com
> <mailto:elwynd@dial.pipex.com>> wrote:
>
>> On Fri, 2014-01-31 at 13:51 +0000, Tim Chown wrote:
>>> On 31 Jan 2014, at 13:23, Dearlove, Christopher (UK)
>>> <chris.dearlove@baesystems.com
>>> <mailto:chris.dearlove@baesystems.com>> wrote:
>>>
>>>> John Levine
>>>>> It's, ah, quite informal.  Tee shirts and sandals are common
>>>>> when the weather is warm enough.
>>>>
>>>> London. March. Expect rain. (The March was almost redundant
>>>> there.)
>>>
>>> Indeed. Large chunks of England are underwaterâ€¦ itâ€™s been raining
>>> for some time.
>>>
>>> Tim
>>
>> But in the best traditions of the interactions of British Politics
>> and British Weather, a Minister for Floods will have been appointed
>> just in time for the floods to disappear and we will be
>> experiencing the start of a months long heat wave and drought by
>> then.  Never take anything for granted!
>
> Yeah, nothing like the environment minister turning up to a village
> three weeks after it's become an island and wondering why he's
> getting a bit of abuse...
>
> London is fine, just check if you plan on any trips to the country,
> e.g. to see stonehenge, you should check the status.  The BBC has
> good coverage and updates, e.g.
> http://www.bbc.co.uk/news/uk-25629479.

Predictions are hmm engineering.

Accurate reporting of recent events may also be helpful.

Rain radars with a 15minute delay at meteox.com. (this is still a very
good performance in terms of free Internet access, delay of reporting,
fine-grained minute report).

> The only disruption in March may be more tube strikes. You may have
> to walk places on the surface streets....

Could one check the on-strike announcements somewhere? (I guess the law
mandates announcements that amount of time in advance).

Alex

>
>> Green wellies are de rigueur in place of sandals for flood wear in
>> the UK.  Could have done with them back at IETF 65 in Dallas!
>
> I don't think wellies would have helped in Dallas - now THAT was a
> flood. Whole cars were underwater.  Everything's bigger in Texas!
>
> Tim
>
>>
>> /E
>>
>



From tjc@ecs.soton.ac.uk  Wed Feb  5 04:47:21 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 C71061A00F4 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 04:47:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.755
X-Spam-Level: 
X-Spam-Status: No, score=-1.755 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, RP_MATCHES_RCVD=-0.535, SPF_NEUTRAL=0.779] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bTPyiPu-O_xI for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 04:47:19 -0800 (PST)
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 14F2E1A00DD for <ietf@ietf.org>; Wed,  5 Feb 2014 04:47:18 -0800 (PST)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s15ClH7P032751; Wed, 5 Feb 2014 12:47:17 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s15ClH7P032751
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1391604437; bh=eeMN+9K/PEYehYK8a6jW9dW9eT0=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=ySn2cUMcPQr/vvZW1oI+laX2++ULt0P6crG70me94uV12oPjElD5cyvRBOLJWPpFf eYSjPb+pLzBiyMgooKxIGi/JHV8lRR4EhtTJadCgxC6BevM/JlT543Rz5zTIXUKczK uzsz36qs1xYmuuMneDyDiOkO0BfZLBLF6WAodJ+k=
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 q14ClH0959615685YO ret-id none; Wed, 05 Feb 2014 12:47:17 +0000
Received: from dhcp-162-42.wireless.soton.ac.uk (dhcp-162-42.wireless.soton.ac.uk [152.78.162.42] (may be forged)) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s15ClFTX007020 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Feb 2014 12:47:15 GMT
Content-Type: multipart/alternative; boundary="Apple-Mail=_BC79E368-F8D5-4423-BD2B-ECEF224D6383"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IETF 89 London - Tube strikes
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <52F22EE7.5040809@gmail.com>
Date: Wed, 5 Feb 2014 12:46:35 +0000
Message-ID: <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1510)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q14ClH095961568500; tid=q14ClH0959615685YO; client=relay,ipv6; mail=; rcpt=; nrcpt=2:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s15ClH7P032751
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
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, 05 Feb 2014 12:47:22 -0000

--Apple-Mail=_BC79E368-F8D5-4423-BD2B-ECEF224D6383
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

(trimmed to the tube issue)

On 5 Feb 2014, at 12:30, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:

> Le 05/02/2014 11:47, Tim Chown a =E9crit :
>=20
>> The only disruption in March may be more tube strikes. You may have
>> to walk places on the surface streets....
>=20
> Could one check the on-strike announcements somewhere? (I guess the =
law
> mandates announcements that amount of time in advance).

So the best site is probably Transport for London, which is more than =
just tubes, see http://www.tfl.gov.uk/.

There's a few free (or very cheap) tube apps. I've used one called =
London Tube Status which is OK (and free). Obviously getting live info =
while in the tube has issues :)

The London underground is generally a very good system.  It's obviously =
busy at the start and end of working day rush hours.  It suffers a =
little from early adopter issues, but the coverage is very good.

The dispute is over the proposed closure of all ticket offices, and I =
expect it may drag on into March and beyond.

Tim=

--Apple-Mail=_BC79E368-F8D5-4423-BD2B-ECEF224D6383
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; =
">Hi,<div><br></div><div>(trimmed to the tube =
issue)</div><div><br><div><div>On 5 Feb 2014, at 12:30, Alexandru =
Petrescu &lt;<a =
href=3D"mailto:alexandru.petrescu@gmail.com">alexandru.petrescu@gmail.com<=
/a>&gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Le 05/02/2014 11:47, Tim Chown a =E9crit =
:<br><br><blockquote type=3D"cite">The only disruption in March may be =
more tube strikes. You may have<br>to walk places on the surface =
streets....<br></blockquote><br>Could one check the on-strike =
announcements somewhere? (I guess the law<br>mandates announcements that =
amount of time in advance).<br></blockquote><div><br></div>So the best =
site is probably Transport for London, which is more than just tubes, =
see&nbsp;<a =
href=3D"http://www.tfl.gov.uk/">http://www.tfl.gov.uk/</a>.</div><div><br>=
</div><div>There's a few free (or very cheap) tube apps. I've used one =
called London Tube Status which is OK (and free). Obviously getting live =
info while in the tube has issues :)</div><div><br></div><div>The London =
underground is generally a very good system. &nbsp;It's obviously busy =
at the start and end of working day rush hours. &nbsp;It suffers a =
little from early adopter issues, but the coverage is very =
good.</div><div><br></div><div>The dispute is over the proposed closure =
of all ticket offices, and I expect it may drag on into March and =
beyond.</div><div><br></div><div>Tim</div></div></body></html>=

--Apple-Mail=_BC79E368-F8D5-4423-BD2B-ECEF224D6383--

From elwynd@dial.pipex.com  Wed Feb  5 05:51:37 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 34BDB1A012D for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 05:51:37 -0800 (PST)
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 LopKIfTrAQA7 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 05:51:34 -0800 (PST)
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 F3E781A0139 for <ietf@ietf.org>; Wed,  5 Feb 2014 05:51:33 -0800 (PST)
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 1WB2t1-0000nW-At; Wed, 05 Feb 2014 13:51:31 +0000
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
In-Reply-To: <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Wed, 05 Feb 2014 13:51:29 +0000
Message-Id: <1391608289.24761.4682.camel@mightyatom>
Mime-Version: 1.0
X-Mailer: Evolution 2.26.3 
Content-Transfer-Encoding: quoted-printable
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 13:51:37 -0000

While we are on the subject of the Tube (and buses)... it is well
worthwhile buying a Visitor's Oyster card either in advance (although
time is getting a bit short for postal delivery) or at the Heathrow
*underground* station - or pretty much any other underground station
until they shut the booking offices which is what the strike is about.
More info here:
http://visitorshop.tfl.gov.uk/help-centre/oyster-card-help.html
http://www.tripadvisor.co.uk/Travel-g186338-c75899/London:United-Kingdom:Oy=
ster.Cards.Travelcards.And.Tickets.html
There's a one-off fee of 3GBP but the card is good for ever and can be
topped up as often as need be at almost any ticket machine.
=20
Oyster is the usual kind of contactless/RFID card that can be used to
pay bus fares and tube fares as well as for local train services.  It is
cheaper with Oyster than buying paper tickets and if you use it a lot on
a given day the total amount you are charged is automatically capped at
the cost of a daily Travelcard. [You learn something every day!]

If you don't mind taking a bit longer to get from Heathrow into central
London, the underground is a *lot* cheaper than the Heathrow Express
(about a factor of five! - HE is 21-26GBP single - Taxi to "central"
London is 45-85GBP depending on time of day and how central) and isn't
that much slower unless your hotel is real close to Paddington Station.
Note that the Oyster is not usable for either the Heathrow Express or
the Gatwick Express trains.

Regards,
Elwyn


On Wed, 2014-02-05 at 12:46 +0000, Tim Chown wrote:
> Hi,
>=20
>=20
> (trimmed to the tube issue)
>=20
> On 5 Feb 2014, at 12:30, Alexandru Petrescu
> <alexandru.petrescu@gmail.com> wrote:
>=20
> > Le 05/02/2014 11:47, Tim Chown a =E9crit :
> >=20
> > > The only disruption in March may be more tube strikes. You may
> > > have
> > > to walk places on the surface streets....
> >=20
> > Could one check the on-strike announcements somewhere? (I guess the
> > law
> > mandates announcements that amount of time in advance).
>=20
>=20
> So the best site is probably Transport for London, which is more than
> just tubes, see http://www.tfl.gov.uk/.
>=20
>=20
> There's a few free (or very cheap) tube apps. I've used one called
> London Tube Status which is OK (and free). Obviously getting live info
> while in the tube has issues :)
>=20
>=20
> The London underground is generally a very good system.  It's
> obviously busy at the start and end of working day rush hours.  It
> suffers a little from early adopter issues, but the coverage is very
> good.
>=20
>=20
> The dispute is over the proposed closure of all ticket offices, and I
> expect it may drag on into March and beyond.
>=20
>=20
> Tim


From Ted.Lemon@nominum.com  Wed Feb  5 05:59:10 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 15D921A013C for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 05:59:10 -0800 (PST)
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 ODz27oEtaf2y for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 05:59:08 -0800 (PST)
Received: from exprod7og111.obsmtp.com (exprod7og111.obsmtp.com [64.18.2.175]) by ietfa.amsl.com (Postfix) with ESMTP id C77841A0134 for <ietf@ietf.org>; Wed,  5 Feb 2014 05:59:08 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob111.postini.com ([64.18.6.12]) with SMTP ID DSNKUvJDrA5GoOb/6elDv3TfGzpgEn+PCGta@postini.com; Wed, 05 Feb 2014 05:59:08 PST
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 2D0581B82DF for <ietf@ietf.org>; Wed,  5 Feb 2014 05:59:08 -0800 (PST)
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 2661E190052; Wed,  5 Feb 2014 05:59:08 -0800 (PST)
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, 5 Feb 2014 05:59:07 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <1391608289.24761.4682.camel@mightyatom>
Date: Wed, 5 Feb 2014 08:59:05 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <E13DC59F-E4DF-4482-82BB-F533D740BE2B@nominum.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 13:59:10 -0000

On Feb 5, 2014, at 8:51 AM, Elwyn Davies <elwynd@dial.pipex.com> wrote:
> If you don't mind taking a bit longer to get from Heathrow into =
central
> London, the underground is a *lot* cheaper than the Heathrow Express
> (about a factor of five! - HE is 21-26GBP single - Taxi to "central"
> London is 45-85GBP depending on time of day and how central) and isn't
> that much slower unless your hotel is real close to Paddington =
Station.

The tube ride from Heathrow to central London is interminable.   It's =
fun if you want to people-watch, and it _is_ cheaper, but Heathrow =
Express is really a treat if you just got off a transatlantic flight, =
and the Metropole is literally five blocks from the station.   I took a =
cab from Paddington last time because I hadn't had time to do the =
research, and it was actually kind of fun, since the driver was very =
polite about it, but it was a little embarrassing when the ride ended in =
less than two minutes.  :)

There is absolutely no reason to take a cab from Heathrow=97it will take =
forever, and you'll get motion sickness.   If you really want to be =
coddled, take Heathrow Express, and take a cab from Paddington.   It'll =
cost a bit less, and be much more pleasant.   Only take the tube if you =
are short on cash or want a somewhat boring adventure.

BTW, doesn't this belong on 89-attendees?


From mary.h.barnes@gmail.com  Wed Feb  5 06:21:20 2014
Return-Path: <mary.h.barnes@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 446781A015B for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 06:21:20 -0800 (PST)
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 XHG_k3IRNKLM for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 06:21:17 -0800 (PST)
Received: from mail-vb0-x235.google.com (mail-vb0-x235.google.com [IPv6:2607:f8b0:400c:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 08DCB1A015D for <ietf@ietf.org>; Wed,  5 Feb 2014 06:21:16 -0800 (PST)
Received: by mail-vb0-f53.google.com with SMTP id p17so322776vbe.26 for <ietf@ietf.org>; Wed, 05 Feb 2014 06:21:16 -0800 (PST)
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=vDMaBkRhMavJqYJRhiffwTed1MpLxL+R4Q2ZaAqS7Lg=; b=SToklf1FCNN+C9J3AnBKTMEYUZROyzOpG+mgS+ATnQrnp/rnlVzamAu9KwdUmmsF+m kk5hdRK6Vr+5z8pl3s4I7dT44pMdAbBEaONIHQwYzuHD2MT/mNECxqbX+e6pCzpJd4on JaMt+gMSZl598o+G50/OGd8z0qSm08VKeBCwqTxvvNpHx3VOitNp9O533L/XIHkYlJEz ooqJxhfCASYV6rkrZXX19rT/pnpt0iWfwxanMR+GOdlpeYAysR/FPcTlWuTCXZfK2dpr 1g7Z8k1vtkO6ey0jDXQ0Z70IfJQnWnBOppKk6aUQdObl0v2xb/JkYcK3LiPiySpwm78i hCjA==
MIME-Version: 1.0
X-Received: by 10.220.196.82 with SMTP id ef18mr39192vcb.78.1391610076053; Wed, 05 Feb 2014 06:21:16 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Wed, 5 Feb 2014 06:21:15 -0800 (PST)
In-Reply-To: <E13DC59F-E4DF-4482-82BB-F533D740BE2B@nominum.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <E13DC59F-E4DF-4482-82BB-F533D740BE2B@nominum.com>
Date: Wed, 5 Feb 2014 08:21:15 -0600
Message-ID: <CABmDk8njOtBs_CpEW1cSZsA8SFueFKSj+YDF+90_CgzYTrBiEA@mail.gmail.com>
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a1133db9c3ff8fd04f1a978dc
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 14:21:20 -0000

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

On Wed, Feb 5, 2014 at 7:59 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Feb 5, 2014, at 8:51 AM, Elwyn Davies <elwynd@dial.pipex.com> wrote:
> > If you don't mind taking a bit longer to get from Heathrow into central
> > London, the underground is a *lot* cheaper than the Heathrow Express
> > (about a factor of five! - HE is 21-26GBP single - Taxi to "central"
> > London is 45-85GBP depending on time of day and how central) and isn't
> > that much slower unless your hotel is real close to Paddington Station.
>
> The tube ride from Heathrow to central London is interminable.   It's fun
> if you want to people-watch, and it _is_ cheaper, but Heathrow Express is
> really a treat if you just got off a transatlantic flight, and the
> Metropole is literally five blocks from the station.   I took a cab from
> Paddington last time because I hadn't had time to do the research, and it
> was actually kind of fun, since the driver was very polite about it, but it
> was a little embarrassing when the ride ended in less than two minutes.  :)
>
[MB] Another option is to take Heathrow Connect.  It's much less expensive
than the Heathrow Express (19.80 GBP versus 34.00 GBP RT)  and departs from
the same location (the signage for Heathrow Connect isn't nearly as
prevalent as that for the Heathrow Express, so just follow the signs for
the latter).   The train takes about 15 minutes longer because there are 4
or 5 stops.  A handy option for folks that have US credit cards without
chips, and thus can't use machines, is to buy your round trip ticket
(either Heathrow Connect or Express) online ahead of time.  You then just
enter the code on your receipt in one of the machines to retrieve your
tickets upon arrival.
[/MB]


>
> There is absolutely no reason to take a cab from Heathrow--it will take
> forever, and you'll get motion sickness.   If you really want to be
> coddled, take Heathrow Express, and take a cab from Paddington.   It'll
> cost a bit less, and be much more pleasant.   Only take the tube if you are
> short on cash or want a somewhat boring adventure.
>
> BTW, doesn't this belong on 89-attendees?
>
[MB] Yes. [/MB]

--001a1133db9c3ff8fd04f1a978dc
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 W=
ed, Feb 5, 2014 at 7:59 AM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mail=
to:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.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"im">On Feb 5, 2014, at 8:51 AM=
, Elwyn Davies &lt;<a href=3D"mailto:elwynd@dial.pipex.com">elwynd@dial.pip=
ex.com</a>&gt; wrote:<br>

&gt; If you don&#39;t mind taking a bit longer to get from Heathrow into ce=
ntral<br>
&gt; London, the underground is a *lot* cheaper than the Heathrow Express<b=
r>
&gt; (about a factor of five! - HE is 21-26GBP single - Taxi to &quot;centr=
al&quot;<br>
&gt; London is 45-85GBP depending on time of day and how central) and isn&#=
39;t<br>
&gt; that much slower unless your hotel is real close to Paddington Station=
.<br>
<br>
</div>The tube ride from Heathrow to central London is interminable. &nbsp;=
 It&#39;s fun if you want to people-watch, and it _is_ cheaper, but Heathro=
w Express is really a treat if you just got off a transatlantic flight, and=
 the Metropole is literally five blocks from the station. &nbsp; I took a c=
ab from Paddington last time because I hadn&#39;t had time to do the resear=
ch, and it was actually kind of fun, since the driver was very polite about=
 it, but it was a little embarrassing when the ride ended in less than two =
minutes. &nbsp;:)<br>
</blockquote><div>[MB] Another option is to take Heathrow Connect. &nbsp;It=
&#39;s much less expensive than the Heathrow Express (19.80 GBP versus 34.0=
0 GBP RT) &nbsp;and departs from the same location (the signage for Heathro=
w Connect isn&#39;t nearly as prevalent as that for the Heathrow Express, s=
o just follow the signs for the latter). &nbsp; The train takes about 15 mi=
nutes longer because there are 4 or 5 stops. &nbsp;A handy option for folks=
 that have US credit cards without chips, and thus can&#39;t use machines, =
is to buy your round trip ticket (either Heathrow Connect or Express) onlin=
e ahead of time. &nbsp;You then just enter the code on your receipt in one =
of the machines to retrieve your tickets upon arrival. &nbsp;</div>
<div>[/MB]</div><div>&nbsp;</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
There is absolutely no reason to take a cab from Heathrow&mdash;it will tak=
e forever, and you&#39;ll get motion sickness. &nbsp; If you really want to=
 be coddled, take Heathrow Express, and take a cab from Paddington. &nbsp; =
It&#39;ll cost a bit less, and be much more pleasant. &nbsp; Only take the =
tube if you are short on cash or want a somewhat boring adventure.<br>

<br>
BTW, doesn&#39;t this belong on 89-attendees?<br></blockquote><div>[MB] Yes=
. [/MB]&nbsp;</div></div><br></div></div>

--001a1133db9c3ff8fd04f1a978dc--

From avri@acm.org  Wed Feb  5 06:39:33 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 5E69B1A01C0 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 06:39:33 -0800 (PST)
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 Wm_pDi44sbyy for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 06:39:31 -0800 (PST)
Received: from atl4mhob18.myregisteredsite.com (atl4mhob18.myregisteredsite.com [209.17.115.58]) by ietfa.amsl.com (Postfix) with ESMTP id 7E9BA1A019E for <ietf@ietf.org>; Wed,  5 Feb 2014 06:39:31 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.206]) by atl4mhob18.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s15EdTtt020209 for <ietf@ietf.org>; Wed, 5 Feb 2014 09:39:29 -0500
Received: (qmail 21406 invoked by uid 0); 5 Feb 2014 14:39:29 -0000
X-TCPREMOTEIP: 68.15.42.104
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@68.15.42.104) by 0 with ESMTPA; 5 Feb 2014 14:39:29 -0000
Message-ID: <52F24D1F.5040602@acm.org>
Date: Wed, 05 Feb 2014 09:39:27 -0500
From: Avri Doria <avri@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom>
In-Reply-To: <1391608289.24761.4682.camel@mightyatom>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Antivirus: avast! (VPS 140205-0, 02/05/2014), Outbound message
X-Antivirus-Status: Not-Tested
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 14:39:33 -0000

Hi

Did someone give the path for getting from the airport to the hotel via 
the underground?  Guess I should look for it.

Would one have to change trains?  Just wondering how much I can cope 
with at the end of the flight with a suitcase that is always too heavy 
to carry up stairs without strain (IETF is last week of a 3 week trip).

I have to do this trip on a very limited budget, otherwise would do a 
HE+car of some sort.  If i am going to do it on the cheap, figure i 
should do it as cheap as cheap can be.

And as I took a underground to the airport once from a train station, I 
know I can do it.  I think.

avri


On 05-Feb-14 08:51, Elwyn Davies wrote:
> While we are on the subject of the Tube (and buses)... it is well
> worthwhile buying a Visitor's Oyster card either in advance (although
> time is getting a bit short for postal delivery) or at the Heathrow
> *underground* station - or pretty much any other underground station
> until they shut the booking offices which is what the strike is about.
> More info here:
> http://visitorshop.tfl.gov.uk/help-centre/oyster-card-help.html
> http://www.tripadvisor.co.uk/Travel-g186338-c75899/London:United-Kingdom:Oyster.Cards.Travelcards.And.Tickets.html
> There's a one-off fee of 3GBP but the card is good for ever and can be
> topped up as often as need be at almost any ticket machine.
>
> Oyster is the usual kind of contactless/RFID card that can be used to
> pay bus fares and tube fares as well as for local train services.  It is
> cheaper with Oyster than buying paper tickets and if you use it a lot on
> a given day the total amount you are charged is automatically capped at
> the cost of a daily Travelcard. [You learn something every day!]
>
> If you don't mind taking a bit longer to get from Heathrow into central
> London, the underground is a *lot* cheaper than the Heathrow Express
> (about a factor of five! - HE is 21-26GBP single - Taxi to "central"
> London is 45-85GBP depending on time of day and how central) and isn't
> that much slower unless your hotel is real close to Paddington Station.
> Note that the Oyster is not usable for either the Heathrow Express or
> the Gatwick Express trains.
>
> Regards,
> Elwyn
>
>
> On Wed, 2014-02-05 at 12:46 +0000, Tim Chown wrote:
>> Hi,
>>
>>
>> (trimmed to the tube issue)
>>
>> On 5 Feb 2014, at 12:30, Alexandru Petrescu
>> <alexandru.petrescu@gmail.com> wrote:
>>
>>> Le 05/02/2014 11:47, Tim Chown a écrit :
>>>
>>>> The only disruption in March may be more tube strikes. You may
>>>> have
>>>> to walk places on the surface streets....
>>>
>>> Could one check the on-strike announcements somewhere? (I guess the
>>> law
>>> mandates announcements that amount of time in advance).
>>
>>
>> So the best site is probably Transport for London, which is more than
>> just tubes, see http://www.tfl.gov.uk/.
>>
>>
>> There's a few free (or very cheap) tube apps. I've used one called
>> London Tube Status which is OK (and free). Obviously getting live info
>> while in the tube has issues :)
>>
>>
>> The London underground is generally a very good system.  It's
>> obviously busy at the start and end of working day rush hours.  It
>> suffers a little from early adopter issues, but the coverage is very
>> good.
>>
>>
>> The dispute is over the proposed closure of all ticket offices, and I
>> expect it may drag on into March and beyond.
>>
>>
>> Tim
>
>
>

From avri@acm.org  Wed Feb  5 06:41:06 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 7A5EE1A01D1 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 06:41:06 -0800 (PST)
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 dTFNeJbc4xL1 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 06:41:05 -0800 (PST)
Received: from atl4mhob18.myregisteredsite.com (atl4mhob18.myregisteredsite.com [209.17.115.58]) by ietfa.amsl.com (Postfix) with ESMTP id 935991A01C9 for <ietf@ietf.org>; Wed,  5 Feb 2014 06:41:05 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob18.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s15Ef4c5029623 for <ietf@ietf.org>; Wed, 5 Feb 2014 09:41:04 -0500
Received: (qmail 10276 invoked by uid 0); 5 Feb 2014 14:41:04 -0000
X-TCPREMOTEIP: 68.15.42.104
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@68.15.42.104) by 0 with ESMTPA; 5 Feb 2014 14:41:04 -0000
Message-ID: <52F24D7D.4040605@acm.org>
Date: Wed, 05 Feb 2014 09:41:01 -0500
From: Avri Doria <avri@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <52F24D1F.5040602@acm.org>
In-Reply-To: <52F24D1F.5040602@acm.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 140205-0, 02/05/2014), Outbound message
X-Antivirus-Status: Not-Tested
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 14:41:06 -0000

oops.

sorry

avri

From Ted.Lemon@nominum.com  Wed Feb  5 06:46:15 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 673E41A019E for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 06:46:15 -0800 (PST)
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 CxS1OspbE1SH for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 06:46:14 -0800 (PST)
Received: from exprod7og122.obsmtp.com (exprod7og122.obsmtp.com [64.18.2.22]) by ietfa.amsl.com (Postfix) with ESMTP id 729561A0193 for <ietf@ietf.org>; Wed,  5 Feb 2014 06:46:14 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob122.postini.com ([64.18.6.12]) with SMTP ID DSNKUvJOtVmSM7sAGFUqfH+kIvhFZt28YUsf@postini.com; Wed, 05 Feb 2014 06:46:14 PST
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 BF2D41B82EB for <ietf@ietf.org>; Wed,  5 Feb 2014 06:46:13 -0800 (PST)
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 A1EFD190052; Wed,  5 Feb 2014 06:46:13 -0800 (PST)
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, 5 Feb 2014 06:46:13 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <52F24D1F.5040602@acm.org>
Date: Wed, 5 Feb 2014 09:46:11 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <B6E9BD27-ADD3-4B11-97ED-C1A1963BA652@nominum.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <52F24D1F.5040602@acm.org>
To: Avri Doria <avri@acm.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
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, 05 Feb 2014 14:46:15 -0000

It's easy.   Take the tube from Heathrow, get off at Gloucester Road, =
switch to the Circle Line, get off at Edgeware station.   You want a =
train for Edgeware, so this should be easy to identify since that's =
where you're going.   Edgeware is less than a block from the Metropole.


From agmalis@gmail.com  Wed Feb  5 07:00:29 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 B9D7D1A0189; Wed,  5 Feb 2014 07:00:29 -0800 (PST)
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 CftErr0TOILT; Wed,  5 Feb 2014 07:00:28 -0800 (PST)
Received: from mail-qa0-x22b.google.com (mail-qa0-x22b.google.com [IPv6:2607:f8b0:400d:c00::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA571A0176; Wed,  5 Feb 2014 07:00:28 -0800 (PST)
Received: by mail-qa0-f43.google.com with SMTP id o15so683530qap.30 for <multiple recipients>; Wed, 05 Feb 2014 07:00:27 -0800 (PST)
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:content-transfer-encoding; bh=o2FG+xg+CzIHD8zrdY+E0Sshm8nYPDnR7y4ac/ulHJI=; b=aPvZCLIizgESclFNBwlQZ5dgcoQg0gfj1RsbkMr3qirRv69M4c1u0fex/OaurJaXWk V8XVlzcwzj7cV2WMvyhlk5JhZkhaD6uRquO+5a+4zhuZ4NPhOszFLG5m9qYynlPx+fSz hVRvoT43mH2vVV4jFFcsNK4hcjk2MTS4kq++0Z2Ht8sa8YUwRI44LHHo7FFWLG2AzdYu K2bmY2vGBMQCZy1nM5EhcK0iZdUF1BXXVh6bqwcjBZvgMcZ79ojD/1EyCswlLRw2J624 wiYgAH2V5cQ9w0jUN9NyYeRmrP51MarQsfIBn4KEHY0GzEA8sXXep2d86f3p3CUZVoF4 0iXw==
X-Received: by 10.224.87.193 with SMTP id x1mr3319437qal.70.1391612427483; Wed, 05 Feb 2014 07:00:27 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.92.136 with HTTP; Wed, 5 Feb 2014 07:00:07 -0800 (PST)
In-Reply-To: <B6E9BD27-ADD3-4B11-97ED-C1A1963BA652@nominum.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <52F24D1F.5040602@acm.org> <B6E9BD27-ADD3-4B11-97ED-C1A1963BA652@nominum.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 5 Feb 2014 10:00:07 -0500
Message-ID: <CAA=duU2GbmryF7MTMaP63uz800=FEMrt4idwnjN8JSe6=Uv-OA@mail.gmail.com>
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: Avri Doria <avri@acm.org>, IETF <ietf@ietf.org>, 89attendees@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 15:00:29 -0000

Ted,

You have to be careful with exact names of the tube stops. There are
three similarly named stations on the London tube - "Edgware Road",
"Edgware Road (Bakerloo line)", and just plain "Edgware". The first of
the three is the closest, one block from the hotel, the second is a
longer walk across several intersections and only serves the Bakerloo
line, and the third is very far from the hotel. There's an underground
walkway between the hotel and the "Edgware Road (Bakerloo line)"
station, but it never seems very safe or secure, especially at night,
and my wife and I usually walk aboveground instead.

Cheers,
Andy

On Wed, Feb 5, 2014 at 9:46 AM, Ted Lemon <ted.lemon@nominum.com> wrote:
> It's easy.   Take the tube from Heathrow, get off at Gloucester Road, swi=
tch to the Circle Line, get off at Edgeware station.   You want a train for=
 Edgeware, so this should be easy to identify since that's where you're goi=
ng.   Edgeware is less than a block from the Metropole.
>

From scott.brim@gmail.com  Wed Feb  5 07:09:43 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 D02E61A015B for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 07:09:43 -0800 (PST)
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 Gc7cruUCGpbh for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 07:09:42 -0800 (PST)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 255DC1A017B for <ietf@ietf.org>; Wed,  5 Feb 2014 07:09:42 -0800 (PST)
Received: by mail-ob0-f170.google.com with SMTP id va2so554019obc.1 for <ietf@ietf.org>; Wed, 05 Feb 2014 07:09:41 -0800 (PST)
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=0r0GwLqPe6dRewINMe25HP/qmHmQQJzvV2ZN3j9Dsrg=; b=0H6lKVzd2vjX/ziKhIHS1XyYku6LU84A/9wGpDsj8uAHjh+Ei2U5oSJXKXMq+QZO0c EpbUiFajD/g7DdpMffT41bpulsCv68E6lx0BqAGi1UzGBQRbeR2hj4tQ65zX1tBbWejw 5lF1uYdqNv3Erl/mq3j38oVi1SLunnxkMxJGmrAhzRuEtb4igWOpi5Dv8ihpfjYy6Uko kBEze7l3X+AzzCNC3wopLe1vQVZPNeoLGtQEybLBym/lvUAB4ruRXvxZ4F/cgsVmHQnv rrj1YIwt/ev/aNorwMriBe8wXxn4sLS8YjIowPIdUhbLgrb2/iox/1qPKx9ouZ72GpzG pMUw==
X-Received: by 10.60.56.200 with SMTP id c8mr831826oeq.80.1391612981270; Wed, 05 Feb 2014 07:09:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Wed, 5 Feb 2014 07:09:20 -0800 (PST)
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 5 Feb 2014 10:09:20 -0500
Message-ID: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
To: Elwyn Davies <elwynd@dial.pipex.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 15:09:43 -0000

On Wed, Feb 5, 2014 at 8:51 AM, Elwyn Davies <elwynd@dial.pipex.com> wrote:
> If you don't mind taking a bit longer to get from Heathrow into central
> London, the underground is a *lot* cheaper than the Heathrow Express
> (about a factor of five! - HE is 21-26GBP single - Taxi to "central"
> London is 45-85GBP depending on time of day and how central) and isn't
> that much slower unless your hotel is real close to Paddington Station.
> Note that the Oyster is not usable for either the Heathrow Express or
> the Gatwick Express trains.

How long does it take by tube? I land at 9:25 pm and would prefer to
get to the hotel by midnight.

Cheers ... Scott

From rdroms.ietf@gmail.com  Wed Feb  5 07:12:44 2014
Return-Path: <rdroms.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 EA2E01A01E4 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 07:12:44 -0800 (PST)
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 nNFY8dqhA7Io for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 07:12:43 -0800 (PST)
Received: from mail-qa0-x22f.google.com (mail-qa0-x22f.google.com [IPv6:2607:f8b0:400d:c00::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 3DA841A0192 for <ietf@ietf.org>; Wed,  5 Feb 2014 07:12:43 -0800 (PST)
Received: by mail-qa0-f47.google.com with SMTP id j5so706677qaq.34 for <ietf@ietf.org>; Wed, 05 Feb 2014 07:12:42 -0800 (PST)
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=9QS5gnFB8vhzT8GuT2A1aH55HiWnkiGxOFNBxFqHJBo=; b=C6Ju/nZzSrviJo1YoqsLQoz7O7IijUlSx73spHzXiHCYevo4Bp8FBIJo0BtkcBnex8 1zsqfCi3vDMtBoI5r53/bcUWf47F49TtR5/h6+Oe0YkUiaAGCun6tXLdBARlPo4gATom F8g2PqoqVp29LAAwLcZpz1GnFhOXpQTjQeWzaF2yXW0nV7fVlboqlYl124/xGS03jShZ fX/Tf7nEvVkWKD33yAYo79GESOh3MQyi7qO2tQ84RiwN8HqEIFUZLkuQ7b4eOGVgq6vD n6znTxFEzC0+kiiCXiEGhl7eIQtcDfNOpSPzHRWIuJuZoGhohjTIxeGWZIm43ZEZ7jLA RSeg==
X-Received: by 10.224.7.10 with SMTP id b10mr3494546qab.50.1391613162446; Wed, 05 Feb 2014 07:12:42 -0800 (PST)
Received: from [10.86.245.208] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id f5sm77746877qas.11.2014.02.05.07.12.40 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Feb 2014 07:12:40 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com>
Date: Wed, 5 Feb 2014 10:12:38 -0500
Content-Transfer-Encoding: 7bit
Message-Id: <9300D219-6E29-42A3-BCA8-48242A17B754@gmail.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1510)
Cc: Chown Tim <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 15:12:45 -0000

On Feb 5, 2014, at 10:09 AM 2/5/14, Scott Brim <scott.brim@gmail.com> wrote:

> On Wed, Feb 5, 2014 at 8:51 AM, Elwyn Davies <elwynd@dial.pipex.com> wrote:
>> If you don't mind taking a bit longer to get from Heathrow into central
>> London, the underground is a *lot* cheaper than the Heathrow Express
>> (about a factor of five! - HE is 21-26GBP single - Taxi to "central"
>> London is 45-85GBP depending on time of day and how central) and isn't
>> that much slower unless your hotel is real close to Paddington Station.
>> Note that the Oyster is not usable for either the Heathrow Express or
>> the Gatwick Express trains.
> 
> How long does it take by tube? I land at 9:25 pm and would prefer to
> get to the hotel by midnight.

I'd estimate 1h15m.

- Ralph

> 
> Cheers ... Scott


From mary.h.barnes@gmail.com  Wed Feb  5 07:13:48 2014
Return-Path: <mary.h.barnes@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 9E83C1A01D3 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 07:13:48 -0800 (PST)
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 UOX1qRtFtvN0 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 07:13:46 -0800 (PST)
Received: from mail-vc0-x234.google.com (mail-vc0-x234.google.com [IPv6:2607:f8b0:400c:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id B46CD1A0192 for <ietf@ietf.org>; Wed,  5 Feb 2014 07:13:46 -0800 (PST)
Received: by mail-vc0-f180.google.com with SMTP id ks9so388176vcb.11 for <ietf@ietf.org>; Wed, 05 Feb 2014 07:13:45 -0800 (PST)
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=AN1KVUOfQYCXPVWRpTgoFXPxdIJbqlNsu6vIu3yaSRU=; b=0H93trOKy4c5bdXwC/nv9nOOijt83O/QmFIxNgEepN3fJXPsrdi+5y483uV0vchdvf 6GROFRd3dUNSAxWBioGAdYaQoPsOPkrLEjgymNBlfgLTPY/+IhTz4lmNTFn8Y+4pRSFX HqaSX9zoOn0cof1KX7ZiEpLR7rMjcELibrDwt5FSjVRnYg2lIuRKIdZye56LWmmPYU5Y AQfAUOfIWnmgPU2OvPTRS+e4xzdGxlOanxMG6SyZGA27NN9Y99O1PZ3L2wIvaKl4k9qB xExI9rSWD1rosKV8XSpOMVUkVDjaH118+6Nn44f0RpxSiqGAoF5VJBv0k28M2EyobqbY EQKA==
MIME-Version: 1.0
X-Received: by 10.220.175.198 with SMTP id bb6mr1064347vcb.31.1391613225817; Wed, 05 Feb 2014 07:13:45 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Wed, 5 Feb 2014 07:13:45 -0800 (PST)
In-Reply-To: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com>
Date: Wed, 5 Feb 2014 09:13:45 -0600
Message-ID: <CABmDk8mBHF-_e4tLmr6T+sujgNFeX7dahuesxsYgTud5Gg-o9g@mail.gmail.com>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c18c1afd5af404f1aa33c8
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 15:13:48 -0000

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

The tube will take at least an hour.  You'll save about 4GBP (each way)
using the underground versus Heathrow Connect (a 30 minute ride).    The
tube is fine if you are staying on the Picadilly line but to get to the
Metropole you will have to make a change.



On Wed, Feb 5, 2014 at 9:09 AM, Scott Brim <scott.brim@gmail.com> wrote:

> On Wed, Feb 5, 2014 at 8:51 AM, Elwyn Davies <elwynd@dial.pipex.com>
> wrote:
> > If you don't mind taking a bit longer to get from Heathrow into central
> > London, the underground is a *lot* cheaper than the Heathrow Express
> > (about a factor of five! - HE is 21-26GBP single - Taxi to "central"
> > London is 45-85GBP depending on time of day and how central) and isn't
> > that much slower unless your hotel is real close to Paddington Station.
> > Note that the Oyster is not usable for either the Heathrow Express or
> > the Gatwick Express trains.
>
> How long does it take by tube? I land at 9:25 pm and would prefer to
> get to the hotel by midnight.
>
> Cheers ... Scott
>

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

<div dir=3D"ltr">The tube will take at least an hour. =A0You&#39;ll save ab=
out 4GBP (each way) using the underground versus Heathrow Connect (a 30 min=
ute ride). =A0 =A0The tube is fine if you are staying on the Picadilly line=
 but to get to the Metropole you will have to make a change.=A0<div>
<br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quot=
e">On Wed, Feb 5, 2014 at 9:09 AM, Scott Brim <span dir=3D"ltr">&lt;<a href=
=3D"mailto:scott.brim@gmail.com" target=3D"_blank">scott.brim@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 Wed, Feb 5, 2014 at 8:51 AM, Elwyn Davies=
 &lt;<a href=3D"mailto:elwynd@dial.pipex.com">elwynd@dial.pipex.com</a>&gt;=
 wrote:<br>

&gt; If you don&#39;t mind taking a bit longer to get from Heathrow into ce=
ntral<br>
&gt; London, the underground is a *lot* cheaper than the Heathrow Express<b=
r>
&gt; (about a factor of five! - HE is 21-26GBP single - Taxi to &quot;centr=
al&quot;<br>
&gt; London is 45-85GBP depending on time of day and how central) and isn&#=
39;t<br>
&gt; that much slower unless your hotel is real close to Paddington Station=
.<br>
&gt; Note that the Oyster is not usable for either the Heathrow Express or<=
br>
&gt; the Gatwick Express trains.<br>
<br>
How long does it take by tube? I land at 9:25 pm and would prefer to<br>
get to the hotel by midnight.<br>
<br>
Cheers ... Scott<br>
</blockquote></div><br></div>

--001a11c18c1afd5af404f1aa33c8--

From dhc@dcrocker.net  Wed Feb  5 07:43:56 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 E371D1A00FD for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 07:43:56 -0800 (PST)
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 MaVJm3X6BbqN for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 07:43:56 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id E6C6F1A0193 for <ietf@ietf.org>; Wed,  5 Feb 2014 07:43:55 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s15FhlBn024811 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 5 Feb 2014 07:43:51 -0800
Message-ID: <52F25C12.5080407@dcrocker.net>
Date: Wed, 05 Feb 2014 07:43:14 -0800
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.2.0
MIME-Version: 1.0
To: Mary Barnes <mary.h.barnes@gmail.com>, Ted Lemon <ted.lemon@nominum.com>
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <E13DC59F-E4DF-4482-82BB-F533D740BE2B@nominum.com> <CABmDk8njOtBs_CpEW1cSZsA8SFueFKSj+YDF+90_CgzYTrBiEA@mail.gmail.com>
In-Reply-To: <CABmDk8njOtBs_CpEW1cSZsA8SFueFKSj+YDF+90_CgzYTrBiEA@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]); Wed, 05 Feb 2014 07:43:51 -0800 (PST)
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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: Wed, 05 Feb 2014 15:43:57 -0000

On 2/5/2014 6:21 AM, Mary Barnes wrote:
> Another option is to take Heathrow Connect.  It's much less expensive
> than the Heathrow Express (19.80 GBP versus 34.00 GBP RT)

Right.  As I recall, it has a couple of extra stops.  It's intended for 
use by folk who /work/ at Heathrow.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From mary.h.barnes@gmail.com  Wed Feb  5 08:04:31 2014
Return-Path: <mary.h.barnes@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 A23521A019C for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 08:04:31 -0800 (PST)
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 E82cQWCB61qg for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 08:04:30 -0800 (PST)
Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 4A1381A010A for <ietf@ietf.org>; Wed,  5 Feb 2014 08:04:30 -0800 (PST)
Received: by mail-ve0-f169.google.com with SMTP id oy12so463881veb.0 for <ietf@ietf.org>; Wed, 05 Feb 2014 08:04:29 -0800 (PST)
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=UnAHRQBO7IoU8tdc8bar8U06np8Q1qSrEM3MJB16ULk=; b=tMZFbuoKBdAbi0lLPaxlxHK2kUy09aadtMrdT2GLlKVuwX8QmackLgKQo8nYMTeGgr zWr8ewAwfiQhBetxgDkoSLKughZRIuMB4OaW/fUEHTH4BnfgI19/ZKp2P8m/gDra1ypd ZM6ndNWFPTMeSHIIsAqnP81+5MNIFZgl+L09yhn4FCAqhWB6tkE+A3tIIWPNRO0WFUXA +iwEOrWuOL50z8oehdOt2Gq/T8HDhAhaFUUfjVPm0rnKYc5ICvw0PFlAFLFEBGJ8V217 iGndPEtTRkXwgE4dpx3GMe+v7UAfKKVDN2DRRo91axSUcY3S3xabJBU+XBTnYYYe0IeP ySLA==
MIME-Version: 1.0
X-Received: by 10.58.161.46 with SMTP id xp14mr568545veb.37.1391616269450; Wed, 05 Feb 2014 08:04:29 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Wed, 5 Feb 2014 08:04:29 -0800 (PST)
In-Reply-To: <52F25C12.5080407@dcrocker.net>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <E13DC59F-E4DF-4482-82BB-F533D740BE2B@nominum.com> <CABmDk8njOtBs_CpEW1cSZsA8SFueFKSj+YDF+90_CgzYTrBiEA@mail.gmail.com> <52F25C12.5080407@dcrocker.net>
Date: Wed, 5 Feb 2014 10:04:29 -0600
Message-ID: <CABmDk8m-Co_pWQt8MfmTrhjx2iFktxJqSRTUfa+i+qJDAecM4w@mail.gmail.com>
Subject: Re: IETF 89 London - Tube strikes and Oyster cards
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7b6dc5a46785ba04f1aae9c4
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 16:04:31 -0000

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

On Wed, Feb 5, 2014 at 9:43 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 2/5/2014 6:21 AM, Mary Barnes wrote:
>
>> Another option is to take Heathrow Connect.  It's much less expensive
>> than the Heathrow Express (19.80 GBP versus 34.00 GBP RT)
>>
>
> Right.  As I recall, it has a couple of extra stops.  It's intended for
> use by folk who /work/ at Heathrow.

[MB] While the might be one intent, there's certainly nothing that prevents
the average person from using it and it's clearly advertised as an option
on the Heathrow airport webpage:
http://www.heathrowairport.com/transport-and-directions/getting-into-london
It's also MUCH more practical for families that are traveling as there is a
special rate - you pay the same rate for kids on Heathrow Express as you do
for an adult.  It also has luggage storage space. IMHO, Heathrow Express is
intended for riders that are willing to pay a premium to save 15 minutes.
For those of us that have to pay out of pocket, the savings is worth the
extra time, in particular if you are arriving early in the morning and are
far less likely to get into your hotel room at that time anyways. [/MB]

>


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

--047d7b6dc5a46785ba04f1aae9c4
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 Wed, Feb 5, 2014 at 9:43 AM, Dave Crocker <span dir=3D"ltr">&lt;=
<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.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"><div class=3D"im">On 2/5/2014 6:21 AM, Mary Barnes 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">
Another option is to take Heathrow Connect. =A0It&#39;s much less expensive=
<br>
than the Heathrow Express (19.80 GBP versus 34.00 GBP RT)<br>
</blockquote>
<br></div>
Right. =A0As I recall, it has a couple of extra stops. =A0It&#39;s intended=
 for use by folk who /work/ at Heathrow.</blockquote><div>[MB] While the mi=
ght be one intent, there&#39;s certainly nothing that prevents the average =
person from using it and it&#39;s clearly advertised as an option on the He=
athrow airport webpage: =A0<a href=3D"http://www.heathrowairport.com/transp=
ort-and-directions/getting-into-london">http://www.heathrowairport.com/tran=
sport-and-directions/getting-into-london</a></div>
<div>It&#39;s also MUCH more practical for families that are traveling as t=
here is a special rate - you pay the same rate for kids on Heathrow Express=
 as you do for an adult. =A0It also has luggage storage space. IMHO, Heathr=
ow Express is intended for riders that are willing to pay a premium to save=
 15 minutes. For those of us that have to pay out of pocket, the savings is=
 worth the extra time, in particular if you are arriving early in the morni=
ng and are far less likely to get into your hotel room at that time anyways=
. [/MB]</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-left-style:solid;p=
adding-left:1ex">=A0</blockquote><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,2=
04,204);border-left-style:solid;padding-left:1ex">
<span class=3D""><font color=3D"#888888"><br>
<br>
d/<br>
<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</font></span></blockquote></div><br></div></div>

--047d7b6dc5a46785ba04f1aae9c4--

From nomcom-chair-2013@ietf.org  Wed Feb  5 11:04:08 2014
Return-Path: <nomcom-chair-2013@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 783F11A011B; Wed,  5 Feb 2014 11:04:08 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bxPnXu2lSpW9; Wed,  5 Feb 2014 11:04:07 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B06801A001A; Wed,  5 Feb 2014 11:04:07 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2013 <nomcom-chair-2013@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: NOMCOM - IESG Appointments
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140205190407.31735.37913.idtracker@ietfa.amsl.com>
Date: Wed, 05 Feb 2014 11:04:07 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: Nomcom Chair 2013 <nomcom-chair-2013@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: Wed, 05 Feb 2014 19:04:08 -0000

The 2013-14 IETF Nomcom is pleased to announce its selection of the
IESG members whose two year terms start at IETF 89 in March 2014.

The Nomcom has selected the following people to serve as Area 
Directors in the IESG, and they have been confirmed by the IAB in
its role as confirming body.

Applications: Barry Leiba
Internet: Brian Haberman
Operations and Management: Benoit Claise
Real-time Applications and Infrastructure: Alissa Cooper
Routing: Alia Atlas
Security: Kathleen Moriarty
Transport: Martin Stiemerling

The Nomcom wishes to be the first to thank the incumbents not
returning to the IESG for their years of serving the community:
   Stewart Bryant: Routing
   Gonzalo Camarillo: RAI
   Sean Turner:  Security

The Nomcom also thanks the many and talented members of the community 
who accepted nominations (with and without our exhortations).  We thank 
the IETF community for its enthusiastic support of the Nomcom process.
Finally, we thank the individuals named above for agreeing to serve the 
community on the IESG.  

For your reference, the 2014-2015 IESG full listing is:

Applications: Barry Leiba and Pete Resnick
Internet: Brian Haberman and Ted Lemon
Operations and Management: Benoit Claise and Joel Jaeggli
Real-time Applications and Infrastructure: Alissa Cooper and Richard Barnes
Routing: Alia Atlas and Adrian Farrel
Security: Kathleen Moriarty and Stephen Farrell
Transport: Martin Stiemerling and Spencer Dawkins

The Nomcom did take note of the affiliation of the Routing Area
selection, and considered it carefully with respect to this particular
circumstance.


From Ted.Lemon@nominum.com  Wed Feb  5 12:46:34 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 D03461A01D1 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 12:46:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_03_06=1.592, 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 sgZhjoLzl8QO for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 12:46:33 -0800 (PST)
Received: from exprod7og128.obsmtp.com (exprod7og128.obsmtp.com [64.18.2.121]) by ietfa.amsl.com (Postfix) with ESMTP id C037C1A01CC for <ietf@ietf.org>; Wed,  5 Feb 2014 12:46:33 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob128.postini.com ([64.18.6.12]) with SMTP ID DSNKUvKjKcOwYTq0yGyS8CT6fmfrzv3wSbxB@postini.com; Wed, 05 Feb 2014 12:46:33 PST
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 DF32E1B82F0 for <ietf@ietf.org>; Wed,  5 Feb 2014 12:46:32 -0800 (PST)
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 9B8AF190064; Wed,  5 Feb 2014 12:46:32 -0800 (PST)
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, 5 Feb 2014 12:46:32 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com>
Date: Wed, 5 Feb 2014 10:14:58 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com>
To: Scott Brim <scott.brim@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 20:46:35 -0000

On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
> How long does it take by tube? I land at 9:25 pm and would prefer to
> get to the hotel by midnight.

Take Heathrow Express.   You won't be sorry.   That's a really long tube =
ride at 9:25 pm.


From rcallon@juniper.net  Wed Feb  5 13:01:27 2014
Return-Path: <rcallon@juniper.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 6DDEA1A0215 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:01:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNRESOLVED_TEMPLATE=1.252] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3SRCUaj1gJKV for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:01:25 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe001.messaging.microsoft.com [207.46.163.24]) by ietfa.amsl.com (Postfix) with ESMTP id 511CF1A021C for <ietf@ietf.org>; Wed,  5 Feb 2014 13:01:25 -0800 (PST)
Received: from mail159-co9-R.bigfish.com (10.236.132.253) by CO9EHSOBE003.bigfish.com (10.236.130.66) with Microsoft SMTP Server id 14.1.225.22; Wed, 5 Feb 2014 21:01:24 +0000
Received: from mail159-co9 (localhost [127.0.0.1])	by mail159-co9-R.bigfish.com (Postfix) with ESMTP id 34FAB260268;	Wed,  5 Feb 2014 21:01:24 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -22
X-BigFish: VPS-22(z579ehz98dI9371I542I4015Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de098h1033IL8275bh1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24d7h2516h2545h9a9j1155h)
Received-SPF: pass (mail159-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=rcallon@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(164054003)(199002)(189002)(13464003)(24454002)(74706001)(93516002)(63696002)(92566001)(2656002)(53806001)(54356001)(83072002)(80022001)(81816001)(79102001)(76482001)(85852003)(46102001)(85306002)(94316002)(94946001)(59766001)(65816001)(86362001)(74876001)(54316002)(51856001)(93136001)(56776001)(77982001)(90146001)(87266001)(87936001)(66066001)(81686001)(33646001)(56816005)(4396001)(81342001)(31966008)(76796001)(49866001)(47736001)(74502001)(80976001)(81542001)(47976001)(50986001)(19580395003)(83322001)(74662001)(76576001)(74366001)(19580405001)(47446002)(74316001)(76786001)(69226001)(95416001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR05MB636; H:CO2PR05MB636.namprd05.prod.outlook.com; CLIP:66.129.241.12; FPR:3CEFC66E.A862EFCA.B9D2BFF6.9EC4CD0D.201F6; InfoNoRecordsA:1; MX:1; LANG:en;
Received: from mail159-co9 (localhost.localdomain [127.0.0.1]) by mail159-co9 (MessageSwitch) id 1391634082551086_12651; Wed,  5 Feb 2014 21:01:22 +0000 (UTC)
Received: from CO9EHSMHS001.bigfish.com (unknown [10.236.132.247])	by mail159-co9.bigfish.com (Postfix) with ESMTP id 6D90AC0046;	Wed,  5 Feb 2014 21:01:22 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS001.bigfish.com (10.236.130.11) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 5 Feb 2014 21:01:21 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com (10.141.199.24) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.411.0; Wed, 5 Feb 2014 21:01:16 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com (10.141.199.24) by CO2PR05MB636.namprd05.prod.outlook.com (10.141.199.24) with Microsoft SMTP Server (TLS) id 15.0.868.8; Wed, 5 Feb 2014 21:01:07 +0000
Received: from CO2PR05MB636.namprd05.prod.outlook.com ([10.141.199.24]) by CO2PR05MB636.namprd05.prod.outlook.com ([10.141.199.24]) with mapi id 15.00.0868.013; Wed, 5 Feb 2014 21:01:07 +0000
From: Ross Callon <rcallon@juniper.net>
To: Ted Lemon <ted.lemon@nominum.com>, Scott Brim <scott.brim@gmail.com>
Subject: RE: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
Thread-Topic: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
Thread-Index: AQHPIoRZIXhUcFh+4kaQddNUF1yev5qmxQcAgABeuoA=
Date: Wed, 5 Feb 2014 21:01:07 +0000
Message-ID: <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com>
In-Reply-To: <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.12]
x-forefront-prvs: 01136D2D90
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CRA-Verdict: 157.56.240.101$ecs.soton.ac.uk%0%1%DuplicateDomain-c684c95e-93ad-459f-9d80-96fa46cd75af.juniper.net%False%False%0$
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%0$Dn%ECS.SOTON.AC.UK$RO%1$TLS%0$FQDN%$TlsDn%
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 21:01:27 -0000

Is there any danger of the Heathrow Express being shut down if there is a T=
ube strike?=20

Also, looking at Google maps, it looks like one should just walk from the P=
addington Station to the Metropole (9 minute walk, straight up Praed street=
 to Edgware Rd).  For those of us in good health with wheels on our suitcas=
e and arriving during daylight, is there any reason not to just walk it?=20

Thanks, Ross

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Wednesday, February 05, 2014 10:15 AM
To: Scott Brim
Cc: Tim Chown; IETF discussion list
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster ca=
rds)

On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
> How long does it take by tube? I land at 9:25 pm and would prefer to
> get to the hotel by midnight.

Take Heathrow Express.   You won't be sorry.   That's a really long tube ri=
de at 9:25 pm.





From tbray@textuality.com  Wed Feb  5 13:04:52 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 236C01A020A for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:04:52 -0800 (PST)
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 er4bHm9y7Pes for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:04:50 -0800 (PST)
Received: from mail-ve0-f175.google.com (mail-ve0-f175.google.com [209.85.128.175]) by ietfa.amsl.com (Postfix) with ESMTP id 6CBC41A01FC for <ietf@ietf.org>; Wed,  5 Feb 2014 13:04:50 -0800 (PST)
Received: by mail-ve0-f175.google.com with SMTP id c14so780167vea.34 for <ietf@ietf.org>; Wed, 05 Feb 2014 13:04:49 -0800 (PST)
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=JqE4B3PYfBECD6/reze/O2nVm+eQFtRMnEyYEmzWSnw=; b=OsnN8uBjyGdJZ34Hci70yJx1y2ce/9sJvUx+fh2YT1ofeqDGqEBFSmLypkByQKrrD8 8j1qgIDJ5UdEJ6/CkFUKMfIC53HB5ghyffy2QaP0ScAJI0ctOhQUIj4YtE8iA9HwbqbR iEcGC/6IQg6qKSTW37VkBoQUj02jvHkAZ3m6xzK+TH/xva1xAHFCpntbBSfQEB6mSv6B mWtW51d+gmL32652fzbfDQoqQ2tq3lnLuUHiGx1RWHtB+jI3uEHhSVr29gq+8xkyh9WH zPwOmpZ7By9vKJoHXYPrMVI7HZmY09fVM4x49N+CoFZwzk+ADA/fssx5u40qf8iXB+vR 2vHw==
X-Gm-Message-State: ALoCoQltcK4jYc0BX554xNkN96gYpmJ1bXLbWH9GkrvIHrXXeZOpH1WVtj4TloTAfP7pYw3kXsQY
MIME-Version: 1.0
X-Received: by 10.52.166.9 with SMTP id zc9mr2037058vdb.16.1391634289513; Wed, 05 Feb 2014 13:04:49 -0800 (PST)
Received: by 10.220.98.73 with HTTP; Wed, 5 Feb 2014 13:04:49 -0800 (PST)
X-Originating-IP: [209.121.225.185]
Received: by 10.220.98.73 with HTTP; Wed, 5 Feb 2014 13:04:49 -0800 (PST)
In-Reply-To: <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com>
Date: Wed, 5 Feb 2014 13:04:49 -0800
Message-ID: <CAHBU6iv3Zhvxhk0=tmw-9CTNaD2hJmhxs7in6JzrY=iw+xwj5g@mail.gmail.com>
Subject: RE: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Tim Bray <tbray@textuality.com>
To: Ross Callon <rcallon@juniper.net>
Content-Type: multipart/alternative; boundary=001a11c2d9927bea9904f1af1b55
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 21:04:52 -0000

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

No reason, just walk it.  After that many hours on planes and trains,
probably therapeutic too
On Feb 5, 2014 1:01 PM, "Ross Callon" <rcallon@juniper.net> wrote:

> Is there any danger of the Heathrow Express being shut down if there is a
> Tube strike?
>
> Also, looking at Google maps, it looks like one should just walk from the
> Paddington Station to the Metropole (9 minute walk, straight up Praed
> street to Edgware Rd).  For those of us in good health with wheels on our
> suitcase and arriving during daylight, is there any reason not to just walk
> it?
>
> Thanks, Ross
>
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
> Sent: Wednesday, February 05, 2014 10:15 AM
> To: Scott Brim
> Cc: Tim Chown; IETF discussion list
> Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster
> cards)
>
> On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
> > How long does it take by tube? I land at 9:25 pm and would prefer to
> > get to the hotel by midnight.
>
> Take Heathrow Express.   You won't be sorry.   That's a really long tube
> ride at 9:25 pm.
>
>
>
>
>

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

<p dir=3D"ltr">No reason, just walk it.=C2=A0 After that many hours on plan=
es and trains, probably therapeutic too</p>
<div class=3D"gmail_quote">On Feb 5, 2014 1:01 PM, &quot;Ross Callon&quot; =
&lt;<a href=3D"mailto:rcallon@juniper.net">rcallon@juniper.net</a>&gt; wrot=
e:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Is there any danger of the Heathrow Express being shut down if there is a T=
ube strike?<br>
<br>
Also, looking at Google maps, it looks like one should just walk from the P=
addington Station to the Metropole (9 minute walk, straight up Praed street=
 to Edgware Rd). =C2=A0For those of us in good health with wheels on our su=
itcase and arriving during daylight, is there any reason not to just walk i=
t?<br>

<br>
Thanks, Ross<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 Ted Lemon<br>
Sent: Wednesday, February 05, 2014 10:15 AM<br>
To: Scott Brim<br>
Cc: Tim Chown; IETF discussion list<br>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster ca=
rds)<br>
<br>
On Feb 5, 2014, at 10:09 AM, Scott Brim &lt;<a href=3D"mailto:scott.brim@gm=
ail.com">scott.brim@gmail.com</a>&gt; wrote:<br>
&gt; How long does it take by tube? I land at 9:25 pm and would prefer to<b=
r>
&gt; get to the hotel by midnight.<br>
<br>
Take Heathrow Express. =C2=A0 You won&#39;t be sorry. =C2=A0 That&#39;s a r=
eally long tube ride at 9:25 pm.<br>
<br>
<br>
<br>
<br>
</blockquote></div>

--001a11c2d9927bea9904f1af1b55--

From rifaat.ietf@gmail.com  Wed Feb  5 13:12:58 2014
Return-Path: <rifaat.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 4FC2E1A01FC for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:12:58 -0800 (PST)
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 CYa6pVxVXQfU for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:12:56 -0800 (PST)
Received: from mail-ea0-x22a.google.com (mail-ea0-x22a.google.com [IPv6:2a00:1450:4013:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 8D3021A01CC for <ietf@ietf.org>; Wed,  5 Feb 2014 13:12:56 -0800 (PST)
Received: by mail-ea0-f170.google.com with SMTP id k10so494704eaj.15 for <ietf@ietf.org>; Wed, 05 Feb 2014 13:12:55 -0800 (PST)
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=4oC9THkg2ZmhHlQ5nV2OkIr4pwpSDks/Jwl2m8t9IIw=; b=Xx+MVR6CPasjlD7S7NJY0Ny2Ghj+oqTfgUUgCuJSDgYOap/wQIfyVzOWGtymeZVprX iEn+K+dRBhIElmTIzbYPtN1FX/LINBiX+CiZaFKtDDsYgB3azf4n/Ayip49gzbbqFj2N N3yRdnWYGVuvY5IkHlqCgvIKuTDt9rxoLX87H7bvrcnmYtfkg3bf2t81MeAL9zhbQLZ6 l87ZpnJ9LROYDnOo/hSX9BGr0QRCliARz4xaT16BHx6eGt0TPRKfCD4wLUCnY0uYepV6 Q8sm8BSOw4wh7F3AR3UHT3GZD6ALg/5m2PhwbPQD3X88KpptOtUo5n2HYGYZBuYhHAm3 3DIg==
MIME-Version: 1.0
X-Received: by 10.14.216.193 with SMTP id g41mr4505471eep.13.1391634775381; Wed, 05 Feb 2014 13:12:55 -0800 (PST)
Received: by 10.14.149.6 with HTTP; Wed, 5 Feb 2014 13:12:55 -0800 (PST)
In-Reply-To: <CAHBU6iv3Zhvxhk0=tmw-9CTNaD2hJmhxs7in6JzrY=iw+xwj5g@mail.gmail.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com> <CAHBU6iv3Zhvxhk0=tmw-9CTNaD2hJmhxs7in6JzrY=iw+xwj5g@mail.gmail.com>
Date: Wed, 5 Feb 2014 16:12:55 -0500
Message-ID: <CAGL6epK2qbuZNh0Tgt1Aj2wXvf3JggY+UZJiq_DCgMGNgtnWGA@mail.gmail.com>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: multipart/alternative; boundary=047d7b622072719b7804f1af38d2
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 21:12:58 -0000

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

Is is a safe walk at night too?

Thanks,
 Rifaat



On Wed, Feb 5, 2014 at 4:04 PM, Tim Bray <tbray@textuality.com> wrote:

> No reason, just walk it.  After that many hours on planes and trains,
> probably therapeutic too
> On Feb 5, 2014 1:01 PM, "Ross Callon" <rcallon@juniper.net> wrote:
>
>> Is there any danger of the Heathrow Express being shut down if there is a
>> Tube strike?
>>
>> Also, looking at Google maps, it looks like one should just walk from the
>> Paddington Station to the Metropole (9 minute walk, straight up Praed
>> street to Edgware Rd).  For those of us in good health with wheels on our
>> suitcase and arriving during daylight, is there any reason not to just walk
>> it?
>>
>> Thanks, Ross
>>
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
>> Sent: Wednesday, February 05, 2014 10:15 AM
>> To: Scott Brim
>> Cc: Tim Chown; IETF discussion list
>> Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster
>> cards)
>>
>> On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
>> > How long does it take by tube? I land at 9:25 pm and would prefer to
>> > get to the hotel by midnight.
>>
>> Take Heathrow Express.   You won't be sorry.   That's a really long tube
>> ride at 9:25 pm.
>>
>>
>>
>>
>>

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

<div dir=3D"ltr">Is is a safe walk at night too?<div><br></div><div>Thanks,=
</div><div>=A0Rifaat</div><div><br></div></div><div class=3D"gmail_extra"><=
br><br><div class=3D"gmail_quote">On Wed, Feb 5, 2014 at 4:04 PM, Tim Bray =
<span dir=3D"ltr">&lt;<a href=3D"mailto:tbray@textuality.com" target=3D"_bl=
ank">tbray@textuality.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"><p dir=3D"ltr">No reason, just walk it.=A0 A=
fter that many hours on planes and trains, probably therapeutic too</p><div=
 class=3D"HOEnZb">
<div class=3D"h5">
<div class=3D"gmail_quote">On Feb 5, 2014 1:01 PM, &quot;Ross Callon&quot; =
&lt;<a href=3D"mailto:rcallon@juniper.net" target=3D"_blank">rcallon@junipe=
r.net</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>

Is there any danger of the Heathrow Express being shut down if there is a T=
ube strike?<br>
<br>
Also, looking at Google maps, it looks like one should just walk from the P=
addington Station to the Metropole (9 minute walk, straight up Praed street=
 to Edgware Rd). =A0For those of us in good health with wheels on our suitc=
ase and arriving during daylight, is there any reason not to just walk it?<=
br>


<br>
Thanks, Ross<br>
<br>
-----Original Message-----<br>
From: ietf [mailto:<a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blan=
k">ietf-bounces@ietf.org</a>] On Behalf Of Ted Lemon<br>
Sent: Wednesday, February 05, 2014 10:15 AM<br>
To: Scott Brim<br>
Cc: Tim Chown; IETF discussion list<br>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster ca=
rds)<br>
<br>
On Feb 5, 2014, at 10:09 AM, Scott Brim &lt;<a href=3D"mailto:scott.brim@gm=
ail.com" target=3D"_blank">scott.brim@gmail.com</a>&gt; wrote:<br>
&gt; How long does it take by tube? I land at 9:25 pm and would prefer to<b=
r>
&gt; get to the hotel by midnight.<br>
<br>
Take Heathrow Express. =A0 You won&#39;t be sorry. =A0 That&#39;s a really =
long tube ride at 9:25 pm.<br>
<br>
<br>
<br>
<br>
</blockquote></div>
</div></div></blockquote></div><br></div>

--047d7b622072719b7804f1af38d2--

From david.misell@icloud.com  Wed Feb  5 07:06:35 2014
Return-Path: <david.misell@icloud.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39A951A016E; Wed,  5 Feb 2014 07:06:35 -0800 (PST)
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, 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 hyB-4mhp3arO; Wed,  5 Feb 2014 07:06:32 -0800 (PST)
Received: from nk11p14im-asmtp001.me.com (nk11p14im-asmtp001.me.com [17.158.72.160]) by ietfa.amsl.com (Postfix) with ESMTP id CC2221A019E; Wed,  5 Feb 2014 07:06:31 -0800 (PST)
Received: from unknown-b8-e8-56-34-a1-fc.home (host109-153-125-155.range109-153.btcentralplus.com [109.153.125.155]) by nk11p14im-asmtp001.mac.com (Oracle Communications Messaging Server 7u4-27.08(7.0.4.27.7) 64bit (built Aug 22 2013)) with ESMTPSA id <0N0J00BWY3A8CI50@nk11p14im-asmtp001.mac.com>; Wed, 05 Feb 2014 15:06:13 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87,1.0.14,0.0.0000 definitions=2014-02-05_05:2014-02-05,2014-02-05,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-1308280000 definitions=main-1402050062
Content-type: multipart/alternative; boundary="Apple-Mail=_D206E058-4B1D-4F51-A5D6-63771A69882C"
MIME-version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: [89attendees] IETF 89 London - Tube strikes and Oyster cards
From: David Misell <david.misell@icloud.com>
In-reply-to: <CAA=duU2GbmryF7MTMaP63uz800=FEMrt4idwnjN8JSe6=Uv-OA@mail.gmail.com>
Date: Wed, 05 Feb 2014 15:06:09 +0000
Message-id: <CFDDA56F-A0B4-4204-9E78-DCE782874DAD@icloud.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <52F24D1F.5040602@acm.org> <B6E9BD27-ADD3-4B11-97ED-C1A1963BA652@nominum.com> <CAA=duU2GbmryF7MTMaP63uz800=FEMrt4idwnjN8JSe6=Uv-OA@mail.gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Mailman-Approved-At: Wed, 05 Feb 2014 13:13:04 -0800
Cc: Avri Doria <avri@acm.org>, 89attendees@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, 05 Feb 2014 15:08:56 -0000

--Apple-Mail=_D206E058-4B1D-4F51-A5D6-63771A69882C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Also we have tube strikes at the moment.

The hotel is served by several 24hour and night buses, one stops near =
Paddington station and goes to Heathrow.

www.tfl.gov.uk/tfl/gettingaround/maps/buses/pdf/paddington-2201.pdf=20


If you have any queries the tfl.gov.uk web site will answer them but =
ensure above all else you have an oyster card or bank/credit card with =
the wifi enabled which reduces the bus fare to =A31.40, with a cap of 3 =
journeys allowing unlimited travel over the day until 0400 for journey =
start the next day

Also there are railcard and group travel discounts on the heathrow =
express:
www.heathrowexpress.com/GroupSaver
Online Exclusive: Save 1/3 When 3 Adults Or More Travel Together.


On 5 Feb 2014, at 15:00, Andrew G. Malis <agmalis@gmail.com> wrote:

> Ted,
>=20
> You have to be careful with exact names of the tube stops. There are
> three similarly named stations on the London tube - "Edgware Road",
> "Edgware Road (Bakerloo line)", and just plain "Edgware". The first of
> the three is the closest, one block from the hotel, the second is a
> longer walk across several intersections and only serves the Bakerloo
> line, and the third is very far from the hotel. There's an underground
> walkway between the hotel and the "Edgware Road (Bakerloo line)"
> station, but it never seems very safe or secure, especially at night,
> and my wife and I usually walk aboveground instead.
>=20
> Cheers,
> Andy
>=20
> On Wed, Feb 5, 2014 at 9:46 AM, Ted Lemon <ted.lemon@nominum.com> =
wrote:
>> It's easy.   Take the tube from Heathrow, get off at Gloucester Road, =
switch to the Circle Line, get off at Edgeware station.   You want a =
train for Edgeware, so this should be easy to identify since that's =
where you're going.   Edgeware is less than a block from the Metropole.
>>=20
> _______________________________________________
> 89attendees mailing list
> 89attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/89attendees


--Apple-Mail=_D206E058-4B1D-4F51-A5D6-63771A69882C
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;">Also =
we have tube strikes at the moment.<div><br></div><div>The hotel is =
served by several 24hour and night buses, one stops near Paddington =
station and goes to Heathrow.</div><div><br></div><div><cite =
style=3D"color: rgb(0, 144, 48); font-style: normal; word-wrap: =
break-word; font-family: Arial, Helvetica, sans-serif; font-size: small; =
line-height: 15px;">www.<span style=3D"font-weight: 700;"><a =
href=3D"http://tfl.gov.uk">tfl.gov.uk</a></span>/tfl/gettingaround/maps/<s=
pan style=3D"font-weight: 700;">buses</span>/pdf/<span =
style=3D"font-weight: 700;">paddington</span>-2201.pdf</cite><span =
style=3D"color: rgb(119, 119, 119); font-family: Arial, Helvetica, =
sans-serif; font-size: small; line-height: =
15px;">&nbsp;</span></div><div><span style=3D"color: rgb(119, 119, 119); =
font-family: Arial, Helvetica, sans-serif; font-size: small; =
line-height: 15px;"><br></span></div><div><br></div><div>If you have any =
queries the <a href=3D"http://tfl.gov.uk">tfl.gov.uk</a> web site will =
answer them but ensure above all else you have an oyster card or =
bank/credit card with the wifi enabled which reduces the bus fare to =
=A31.40, with a cap of 3 journeys allowing unlimited travel over the day =
until 0400 for journey start the next day</div><div><br></div><div>Also =
there are railcard and group travel discounts on the heathrow =
express:</div><div><div class=3D"sb_dul" style=3D"padding-top: 1px; =
color: rgb(64, 64, 64); font-family: Arial, Helvetica, sans-serif; =
font-size: small; background-color: rgb(249, 252, 247);"><cite =
style=3D"color: rgb(0, 128, 48); font-style: normal; word-wrap: =
break-word; margin-left: 0px; display: inline; padding: 1px 0px =
0px;">www.<span style=3D"font-weight: 700;">heathrow</span><a =
href=3D"http://express.com/GroupSaver">express.com/GroupSaver</a></cite></=
div><div style=3D"border: 0px; border-collapse: collapse; =
border-spacing: 0px; list-style: none; margin: 0px; padding: 2px 0px =
0px; color: rgb(48, 48, 48); font-family: Arial, Helvetica, sans-serif; =
font-size: small; background-color: rgb(249, 252, 247); position: =
static; z-index: auto;">Online Exclusive: Save 1/3 When 3 Adults Or More =
Travel Together.</div></div><div style=3D"border: 0px; border-collapse: =
collapse; border-spacing: 0px; list-style: none; margin: 0px; padding: =
2px 0px 0px; color: rgb(48, 48, 48); font-family: Arial, Helvetica, =
sans-serif; font-size: small; background-color: rgb(249, 252, 247); =
position: static; z-index: auto;"><br></div><div><br><div><div>On 5 Feb =
2014, at 15:00, Andrew G. Malis &lt;<a =
href=3D"mailto:agmalis@gmail.com">agmalis@gmail.com</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">Ted,<br><br>You have to be careful with exact names of the =
tube stops. There are<br>three similarly named stations on the London =
tube - "Edgware Road",<br>"Edgware Road (Bakerloo line)", and just plain =
"Edgware". The first of<br>the three is the closest, one block from the =
hotel, the second is a<br>longer walk across several intersections and =
only serves the Bakerloo<br>line, and the third is very far from the =
hotel. There's an underground<br>walkway between the hotel and the =
"Edgware Road (Bakerloo line)"<br>station, but it never seems very safe =
or secure, especially at night,<br>and my wife and I usually walk =
aboveground instead.<br><br>Cheers,<br>Andy<br><br>On Wed, Feb 5, 2014 =
at 9:46 AM, Ted Lemon &lt;<a =
href=3D"mailto:ted.lemon@nominum.com">ted.lemon@nominum.com</a>&gt; =
wrote:<br><blockquote type=3D"cite">It's easy. &nbsp;&nbsp;Take the tube =
from Heathrow, get off at Gloucester Road, switch to the Circle Line, =
get off at Edgeware station. &nbsp;&nbsp;You want a train for Edgeware, =
so this should be easy to identify since that's where you're going. =
&nbsp;&nbsp;Edgeware is less than a block from the =
Metropole.<br><br></blockquote>___________________________________________=
____<br>89attendees mailing list<br><a =
href=3D"mailto:89attendees@ietf.org">89attendees@ietf.org</a><br>https://w=
ww.ietf.org/mailman/listinfo/89attendees<br></blockquote></div><br></div><=
/body></html>=

--Apple-Mail=_D206E058-4B1D-4F51-A5D6-63771A69882C--

From mstjohns@comcast.net  Wed Feb  5 13:14:29 2014
Return-Path: <mstjohns@comcast.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 B5D2B1A01CC for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.037
X-Spam-Level: 
X-Spam-Status: No, score=-2.037 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, MISSING_MID=0.497, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l5-eWG5f8930 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:14:28 -0800 (PST)
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 B52EE1A0231 for <ietf@ietf.org>; Wed,  5 Feb 2014 13:14:24 -0800 (PST)
Received: from omta21.westchester.pa.mail.comcast.net ([76.96.62.72]) by qmta09.westchester.pa.mail.comcast.net with comcast id NcX91n0011ZXKqc59lEPVq; Wed, 05 Feb 2014 21:14:23 +0000
Received: from Mike-T530ssd.comcast.net ([68.34.113.195]) by omta21.westchester.pa.mail.comcast.net with comcast id NlEP1n00A4D0RQL3hlEPPn; Wed, 05 Feb 2014 21:14:23 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Wed, 05 Feb 2014 16:14:33 -0500
To: Tim Bray <tbray@textuality.com>,Ross Callon <rcallon@juniper.net>
From: Michael StJohns <mstjohns@comcast.net>
Subject: RE: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
In-Reply-To: <CAHBU6iv3Zhvxhk0=tmw-9CTNaD2hJmhxs7in6JzrY=iw+xwj5g@mail.g mail.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com> <CAHBU6iv3Zhvxhk0=tmw-9CTNaD2hJmhxs7in6JzrY=iw+xwj5g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="=====================_693410856==.ALT"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1391634863; bh=0jS1it18sTMtAaajkr4imvRzrw9vV/LYzCPDxtPqzm0=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=IZK49bOQg+IpDsO6Eb8ugakcV8hVDqaUe2kDkh4ygUxzbQz7zaVKeQNT1PkrCDghW M5NZPcs9Wk6Ehrt32bXW34DgdeqX8JMPKA5dsox3bzwwrlxM7qSP7IEgtvPXTf9Edo /S4pk3j5pG/PR43mMPCH0xeqoLgLa4mUdlvbxC386/7QdRGhZY4QVW4ykItj3vyG58 GvHmHZ90OhizGANH8CNPqeMV82V6tUhKmp7P4TeKjAtfRG7sym+8gWW8FNmz3rNYL7 8r7wY2mEtXJ7bz2CJw3YxAGCJLHb3LQPsIpWC5QXNyZEXx3dSGdiOENPSxI08IUAze +TBZiCHcUtGrg==
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 05 Feb 2014 21:14:30 -0000

--=====================_693410856==.ALT
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

It's almost a longer walk to go from the track to the taxi queue.

At 04:04 PM 2/5/2014, Tim Bray wrote:

>No reason, just walk it.=C2  After that many hours on planes and trains,=
 probably therapeutic too
>On Feb 5, 2014 1:01 PM, "Ross Callon"=
 <<mailto:rcallon@juniper.net>rcallon@juniper.net> wrote:
>Is there any danger of the Heathrow Express being shut down if there is a=
 Tube strike?
>
>Also, looking at Google maps, it looks like one should just walk from the=
 Paddington Station to the Metropole (9 minute walk, straight up Praed=
 street to Edgware Rd). =C2 For those of us in good health with wheels on=
 our suitcase and arriving during daylight, is there any reason not to just=
 walk it?
>
>Thanks, Ross
>
>-----Original Message-----
>From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
>Sent: Wednesday, February 05, 2014 10:15 AM
>To: Scott Brim
>Cc: Tim Chown; IETF discussion list
>Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster=
 cards)
>
>On Feb 5, 2014, at 10:09 AM, Scott Brim=
 <<mailto:scott.brim@gmail.com>scott.brim@gmail.com> wrote:
>> How long does it take by tube? I land at 9:25 pm and would prefer to
>> get to the hotel by midnight.
>
>Take Heathrow Express. =C2  You won't be sorry. =C2  That's a really long=
 tube ride at 9:25 pm.
>
>
>


--=====================_693410856==.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<body>
It's almost a longer walk to go from the track to the taxi
queue.<br><br>
At 04:04 PM 2/5/2014, Tim Bray wrote:<br><br>
<blockquote type=3Dcite class=3Dcite cite=3D"">No reason, just walk it.=C2&n=
bsp;
After that many hours on planes and trains, probably therapeutic too<br>
On Feb 5, 2014 1:01 PM, &quot;Ross Callon&quot;
&lt;<a href=3D"mailto:rcallon@juniper.net">rcallon@juniper.net</a>&gt;
wrote:<br>

<dl>
<dd>Is there any danger of the Heathrow Express being shut down if there
is a Tube strike?<br><br>

<dd>Also, looking at Google maps, it looks like one should just walk from
the Paddington Station to the Metropole (9 minute walk, straight up Praed
street to Edgware Rd). =C2 For those of us in good health with wheels on
our suitcase and arriving during daylight, is there any reason not to
just walk it?<br><br>

<dd>Thanks, Ross<br><br>

<dd>-----Original Message-----<br>

<dd>From: ietf
[<a href=3D"mailto:ietf-bounces@ietf.org" eudora=3D"autourl">
mailto:ietf-bounces@ietf.org</a>] On Behalf Of Ted Lemon<br>

<dd>Sent: Wednesday, February 05, 2014 10:15 AM<br>

<dd>To: Scott Brim<br>

<dd>Cc: Tim Chown; IETF discussion list<br>

<dd>Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and
Oyster cards)<br><br>

<dd>On Feb 5, 2014, at 10:09 AM, Scott Brim
&lt;<a href=3D"mailto:scott.brim@gmail.com">scott.brim@gmail.com</a>&gt;
wrote:<br>

<dd>&gt; How long does it take by tube? I land at 9:25 pm and would
prefer to<br>

<dd>&gt; get to the hotel by midnight.<br><br>

<dd>Take Heathrow Express. =C2&nbsp; You won't be sorry. =C2&nbsp; That's a
really long tube ride at 9:25 pm.<br><br>
<br><br>

</dl></blockquote></body>
<br>
</html>

--=====================_693410856==.ALT--


From warren@kumari.net  Wed Feb  5 13:30:43 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 EA3901A0243 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:30:43 -0800 (PST)
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, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_57=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 mFPIP65LL8zx for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:30:42 -0800 (PST)
Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by ietfa.amsl.com (Postfix) with ESMTP id 42B201A0235 for <ietf@ietf.org>; Wed,  5 Feb 2014 13:30:42 -0800 (PST)
Received: by mail-wi0-f170.google.com with SMTP id hi5so974144wib.3 for <ietf@ietf.org>; Wed, 05 Feb 2014 13:30:40 -0800 (PST)
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=n3yFgcp7eYWVVXI2XFGO30ICIqiInSG+ATglLdRTbhI=; b=V0Eni7ddd+xEbzoGj+aUdBIRXJ84HFxwNVJmBmu4JStiYhgZUcIGtZ5YVefOTItJjk egSd6vpO+Op4i7JWV2uAH0aBxhI3WXOHR9KLM87AGP3x6FPckewCpuEF+QsSr+/G0zt8 QP572yRyuHOcYdcIBgXRJSSexeOze9Nk0S/57K9z5jsQAO7zOzJzenQ7ZjX78npsZo/1 F0SCNOnlvJ6IuRwNNMU458SCE+A7lBNlYcq8FgR87k0y7ypdL9nRfNX5mp3ZHA6z4PSX vsm4cF2y6/Te8v4PCuJhGhtFMNYd2vsttqvgtmq88StdjsXizsnuG0NENFBDrpidee0P cMCA==
X-Gm-Message-State: ALoCoQkXphLO/wdPzIGTn6ttcLJIfSYE0NVIj9DXF2wmKCLHJQT2LbPuweBtH4FDT+IODnGM/bDj
MIME-Version: 1.0
X-Received: by 10.194.22.129 with SMTP id d1mr3165320wjf.22.1391635840821; Wed, 05 Feb 2014 13:30:40 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Wed, 5 Feb 2014 13:30:40 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com>
Date: Wed, 5 Feb 2014 16:30:40 -0500
Message-ID: <CAHw9_iLSB1zBY9kpiZw5_iD0oRJz57Bv9rGzvL1Os=sAqY2ZQg@mail.gmail.com>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Warren Kumari <warren@kumari.net>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: "89attendees@ietf.org" <89attendees@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 21:30:44 -0000

[ + 89attendees]
>From a thread on 89attendees (where this really should be...):
http://www.ietf.org/mail-archive/web/89attendees/current/msg00012.html

Getting from Paddington to the Hilton:
You could take a cab, but the hotel is 0.4mile away, and an easy, flat
walk. Took me <7 minutes.
Google Maps link: http://goo.gl/maps/XIAE7

Walk out onto Praed street - it's the "main" entrance - basically
continue walking in the same direction the train was going, up a ramp
/ closed road.
Turn left when you get onto the actual road. You will walk past
Garfunkels bar and a Mercure hotel. On the 2nd or 3rd block, just
before the big metal gates for St Mary's, look up  -- this is where Sir
Alexander Flemming discovered Penicillium mould. Say a quick "Thanks",
life would be substantially worse without this. I would also lose my
primary excuse for keeping a messy desk.
http://en.wikipedia.org/wiki/Alexander_Fleming

Continue walking along Praed. The hotel shows up on your left, just
after a Carphone Warehouse (they sell SIMs -
http://www.carphonewarehouse.com/sims. I haven't checked if this is a
good deal). If you reach Marks&Spenser you have walked right past it.
Turn 180 degrees and walk in.

On Wed, Feb 5, 2014 at 4:01 PM, Ross Callon <rcallon@juniper.net> wrote:
> Is there any danger of the Heathrow Express being shut down if there is a=
 Tube strike?
>
> Also, looking at Google maps, it looks like one should just walk from the=
 Paddington Station to the Metropole (9 minute walk, straight up Praed stre=
et to Edgware Rd).  For those of us in good health with wheels on our suitc=
ase and arriving during daylight, is there any reason not to just walk it?
>
> Thanks, Ross
>
> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
> Sent: Wednesday, February 05, 2014 10:15 AM
> To: Scott Brim
> Cc: Tim Chown; IETF discussion list
> Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster =
cards)
>
> On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
>> How long does it take by tube? I land at 9:25 pm and would prefer to
>> get to the hotel by midnight.
>
> Take Heathrow Express.   You won't be sorry.   That's a really long tube =
ride at 9:25 pm.
>
>
>
>

From johnl@iecc.com  Wed Feb  5 13:38:37 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 B951D1A0101 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:38:37 -0800 (PST)
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 UE4jlvV3W0CW for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:38:36 -0800 (PST)
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 52E721A002B for <ietf@ietf.org>; Wed,  5 Feb 2014 13:38:36 -0800 (PST)
Received: (qmail 54222 invoked from network); 5 Feb 2014 21:38:35 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 5 Feb 2014 21:38: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:mime-version:content-type:content-transfer-encoding; s=52f2af5b.xn--btvx9d.k1402; i=johnl@user.iecc.com; bh=t7tSWrPGbg/+8Dx6xYjeGYxBt9b04ijCstC5NxYCc40=; b=mLqsRqzNhm+yCtk6dI2BjDvpeNMsVb/cn9mpTPP7CCb+BHJ8gadRQ1vGsifYeteU/Jy5VT9tKK9V1OIvH+JyQaQmYsjj4he6sf5oBFydkt9zZF+xmki501YGRU7bVb5kAhOmpl5oxGYtjqVsmLQvNJYGmcls68hzbEHSy2TKWezssHrflLR1hYkGNLETG94yQyoJu4ecxoR/kVD9Qs+dvXj3fbYFBZTDuFAZrz0Kghv+2z2PJ+WgGHCkEgniBRoX
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=52f2af5b.xn--btvx9d.k1402; bh=t7tSWrPGbg/+8Dx6xYjeGYxBt9b04ijCstC5NxYCc40=; b=mcNl4b6KDoq960Fu9dyltUJ0cqEZWS48LQGUG+mvOCGBs4LGeZQwD8LrxLNlXUBjhgEMngyEbY5H9t0GOnzVRUGdQMKCdzvjWIp00C/JRsf315mGFummZ4PnO7EJFmm/gHsh7ANuPqlwEnrDaI3LpgpECOGvFH556n2a9XxGLkgs4tgUWq3i0p/XFyN6Gyw3cRkO3ED3X2xVQj8C221vvI54xDVmE5bDVp/4MedtPbKp0bGQNfx39Et6oZeJXqyT
Date: 5 Feb 2014 21:38:12 -0000
Message-ID: <20140205213812.80492.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [89attendees] Mobile phone service in London
In-Reply-To: <D611770F-B061-4FBB-85F1-9F9C3AEC070B@gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 21:38:37 -0000

In article <D611770F-B061-4FBB-85F1-9F9C3AEC070B@gmail.com> you write:
>Thanks, Stuart.  This SIM seems to be better deal than the Vodafone SIM I've used in the past.
>
>It appears that online ordering and delivery is only available in the UK.  Do you know if I'm missing
>something?

Nope.  Maybe you can have them send it to your hotel.

Note that "Three" stands for 3G, and their network only works with 3G
and 4G phones.  For those of us with beat up old quad band phones, we're
stuck with someone else.

I have a prepaid sim from Orange (now merged into the pretentiously
named Everything Everywhere) with the "Camel" plan, in which each
topup includes a bunch of free international minutes I can use to call
home and assure people that it's still raining heavily and I'm not
having any fun at all.

>> In other news, I recently switched my US phone to the T-Mobile "Simple Choice Plan".

It's great where it works.  Unfortunately, in large parts of the U.S.,
such as where I live, T-Mo has no coverage at all and no schedule to
provide it.

R's,
John

From johnl@iecc.com  Wed Feb  5 13:49: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 697831A0129 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:49:32 -0800 (PST)
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 Gkskc0S-2MWZ for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:49:31 -0800 (PST)
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 1CCAD1A002B for <ietf@ietf.org>; Wed,  5 Feb 2014 13:49:31 -0800 (PST)
Received: (qmail 56264 invoked from network); 5 Feb 2014 21:49:30 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 5 Feb 2014 21:49:30 -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=52f2b1ea.xn--yuvv84g.k1402; i=johnl@user.iecc.com; bh=Kz8YDGK8n+jUm2pdCinXpJAsfAaxDWwYP6x+FbPBS3U=; b=Q1POozD/PLp8kvakjruwOngxoH4irm/ffK/sPhH1BBFgH9vr+yxPYUgN2Bq2OyEk0FUZD9Ntss2bhuSDztcV1UGY47BDIJIB9iBCV+BYlt4CxWs83sOZUD6E7twOYL2HZLl4QWsGBRuFK8uC7GXbKf8PRJPjOJlm4OHHpnzT4yLe9XxDXDWlb/TTtB6B9sPmh6MtrVY8J6J1pqx9zq49CXEucUM9LFedkokigfmwaUH+9lV8HgYly8p1xceo6jaY
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=52f2b1ea.xn--yuvv84g.k1402; bh=Kz8YDGK8n+jUm2pdCinXpJAsfAaxDWwYP6x+FbPBS3U=; b=lye3vQWOxwg0SqPBISshk5RLmB0SSCYBsF3mhy+6mcxHfi+8eywMoRpReakDWBhXTi9zdiAEuXQN5IwryRZcd2W1J5mwObS2On17YFLh2apzSuExh8jSe5CkjETI52+g8wG1I0ENtkNVxoSxM5MIYwkFi2xou5GnpCbWFNF3awZSsXuSPJDec8v5lyDeULkhd18U8aro6c0wtxVTu7xV3LKXR/w4kmgJJrgcyiOICu2Czvll23y0mXQu7O8nWcrs
Date: 5 Feb 2014 21:49:07 -0000
Message-ID: <20140205214907.80539.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [89attendees] IETF 89 London - Tube strikes and Oyster cards
In-Reply-To: <8218A806-F4A0-4A3D-993B-CF019052D47D@vidyo.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: jonathan@vidyo.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, 05 Feb 2014 21:49:32 -0000

>I have an Oyster card that I got when I was in London in 2007 -- I don't recall whether it was
>explicitly a "Visitor" Oyster card.  Is it likely to still work?

Probably.  You can set up an online account on the TfL website,
register your card to it. It'll tell you what your balance is, and you
can top up from a credit card.  As I recall, online topups with US
plastic works.

If it demands a UK address, use your hotel's.

https://account.tfl.gov.uk/oyster

R's,
John

From johnl@iecc.com  Wed Feb  5 13:57: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 3A6651A019C for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:57:09 -0800 (PST)
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 ePc2NvChQtb6 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 13:57:08 -0800 (PST)
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 D11701A012F for <ietf@ietf.org>; Wed,  5 Feb 2014 13:57:07 -0800 (PST)
Received: (qmail 57580 invoked from network); 5 Feb 2014 21:57:06 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 5 Feb 2014 21:57:06 -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=52f2b3b2.xn--30v786c.k1402; i=johnl@user.iecc.com; bh=gbzMOawY6pI0y4gggD2CP3fEOY7eMF1kJvpnusDXx9U=; b=wq5xL9nEub/vzrxBmVrwYunyYKz3AtCHWBpzguD0PoQSm1U2iXUCOqNUc6h8RK1so+6fzLFWQiM0o/WqD1o6Y9RunjQYtWroZmOZKr4nawdaS12m7ngE6lJUuC1z3ABTk6BxIDCkSsFE6cwGSVOsE5hyLu+3KcnQmCLH6otFuFOzxvQ53csWrp4gNFjfoBfovXH8fzw8wXRfixTXrhXtsF+lehoTcva3ZZeHLLhXyJNs0kKJf2TD5FpNX3+dWeUM
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=52f2b3b2.xn--30v786c.k1402; bh=gbzMOawY6pI0y4gggD2CP3fEOY7eMF1kJvpnusDXx9U=; b=CJ5AD6coHdmHTtWRsFaSOhlzMbeLmZ0FjjBBTOULVZ86C5XnwcbS7T7427pJlg1HGXED3yh6cHurFLvL8HbFVtCsZnjcWgu5AxJAozO0m0o7LcKHIZSkw+ZB1dWonIqA+nKKsx5GDO8GssTO2+Us0XjcBi5FX17TEFCvpr/oALxCVWEYmSdZd0IfXvOSwXPMETK0MWGhvwR4nvPPaW1zQU0jSjb22IyaboIwiCjQ2zdwfxreLv5DX2Q1Mn5gDEzQ
Date: 5 Feb 2014 21:56:44 -0000
Message-ID: <20140205215644.80620.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: [89attendees] Mobile phone service in London
In-Reply-To: <220FA160-CB28-43BA-A932-C5A19963905E@vpnc.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Cc: paul.hoffman@vpnc.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 21:57:09 -0000

>> http://shop.tescomobile.com/mobile-phones/pay-as-you-go#price-min=0&price-max=1000&sort-by=phone-price-low
>> 
>> (* for those unfamiliar with the UK, Tesco is the largest supermarket chain)
>
>This should be just fine. Any chance that there is a Tesco at Heathrow?

Nope, just the SIM vending machines near the exits from customs, the
SIM Local store in Terminal 1, and the Vodafone store in Terminal 5.

For what you want, any SIM should work OK.  Remember that incoming
calls are paid by the caller (not really "free"), so the only
difference is the outgoing cost. I doubt you will make £10 of calls
during the week no matter what carrier or plan you have.  I've never
seen them more than 20p/min, so that's at least 50 min of outgoing
calls.

R's,
John

From hallam@gmail.com  Wed Feb  5 13:59:59 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 2FA001A022F; Wed,  5 Feb 2014 13:59:59 -0800 (PST)
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_57=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 w0jSob3A13_q; Wed,  5 Feb 2014 13:59:57 -0800 (PST)
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 9B9A31A022E; Wed,  5 Feb 2014 13:59:56 -0800 (PST)
Received: by mail-la0-f54.google.com with SMTP id y1so841061lam.13 for <multiple recipients>; Wed, 05 Feb 2014 13:59:55 -0800 (PST)
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=r9EsymVuuY4g6BGeTyF/+Y+7OqTvJUDJ5B4UbYl9HmM=; b=Ig+YSxA+seVg0AWyT2Fx8jbDc8UjgQJ9U18tirGrVeYgLF/b0PJLc/4Peo3S2siBlF 0hnVfcfH3QBGUsJHY2wpoXiQQVd55TpWXidY8q2XMwBgELJd06OFMEVBk9UZf/dxlwpQ c9/GeVbO+aWrKmSw6MjzolvaYZsFm05XkiqJtoxwPzYfCc0E/9h3Y3BnySQ+n9Ht583J 7nwAK0b/iA0BluLFy2ZbvKrBrlb3uQqPrJzofDfBLcTfMVQgEzX1SU9V3hgzb4UkDugR yS8JoooC/HNSyRK2cqBAalAUbtSt5J5VwuAjY54pDWwQrzhI16un3ursmi/LUjSWvbO9 QVnw==
MIME-Version: 1.0
X-Received: by 10.152.27.100 with SMTP id s4mr2714613lag.18.1391637595097; Wed, 05 Feb 2014 13:59:55 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Wed, 5 Feb 2014 13:59:55 -0800 (PST)
In-Reply-To: <CAHw9_iLSB1zBY9kpiZw5_iD0oRJz57Bv9rGzvL1Os=sAqY2ZQg@mail.gmail.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com> <CAHw9_iLSB1zBY9kpiZw5_iD0oRJz57Bv9rGzvL1Os=sAqY2ZQg@mail.gmail.com>
Date: Wed, 5 Feb 2014 16:59:55 -0500
Message-ID: <CAMm+Lwg+JePxbyZ48sScR9hcZXKfzuXG4ams7zx70f48R6ppog@mail.gmail.com>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=089e0160b88e830fc704f1afe093
Cc: IETF discussion list <ietf@ietf.org>, "89attendees@ietf.org" <89attendees@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 21:59:59 -0000

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

+1

I have walked that route many times with luggage. That hotel is the one
they often hold the RSA Europe conference in.


On Wed, Feb 5, 2014 at 4:30 PM, Warren Kumari <warren@kumari.net> wrote:

> [ + 89attendees]
> From a thread on 89attendees (where this really should be...):
> http://www.ietf.org/mail-archive/web/89attendees/current/msg00012.html
>
> Getting from Paddington to the Hilton:
> You could take a cab, but the hotel is 0.4mile away, and an easy, flat
> walk. Took me <7 minutes.
> Google Maps link: http://goo.gl/maps/XIAE7
>
> Walk out onto Praed street - it's the "main" entrance - basically
> continue walking in the same direction the train was going, up a ramp
> / closed road.
> Turn left when you get onto the actual road. You will walk past
> Garfunkels bar and a Mercure hotel. On the 2nd or 3rd block, just
> before the big metal gates for St Mary's, look up  -- this is where Sir
> Alexander Flemming discovered Penicillium mould. Say a quick "Thanks",
> life would be substantially worse without this. I would also lose my
> primary excuse for keeping a messy desk.
> http://en.wikipedia.org/wiki/Alexander_Fleming
>
> Continue walking along Praed. The hotel shows up on your left, just
> after a Carphone Warehouse (they sell SIMs -
> http://www.carphonewarehouse.com/sims. I haven't checked if this is a
> good deal). If you reach Marks&Spenser you have walked right past it.
> Turn 180 degrees and walk in.
>
> On Wed, Feb 5, 2014 at 4:01 PM, Ross Callon <rcallon@juniper.net> wrote:
> > Is there any danger of the Heathrow Express being shut down if there is
> a Tube strike?
> >
> > Also, looking at Google maps, it looks like one should just walk from
> the Paddington Station to the Metropole (9 minute walk, straight up Praed
> street to Edgware Rd).  For those of us in good health with wheels on our
> suitcase and arriving during daylight, is there any reason not to just walk
> it?
> >
> > Thanks, Ross
> >
> > -----Original Message-----
> > From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
> > Sent: Wednesday, February 05, 2014 10:15 AM
> > To: Scott Brim
> > Cc: Tim Chown; IETF discussion list
> > Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster
> cards)
> >
> > On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
> >> How long does it take by tube? I land at 9:25 pm and would prefer to
> >> get to the hotel by midnight.
> >
> > Take Heathrow Express.   You won't be sorry.   That's a really long tube
> ride at 9:25 pm.
> >
> >
> >
> >
>



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

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

<div dir=3D"ltr">+1<div><br></div><div>I have walked that route many times =
with luggage. That hotel is the one they often hold the RSA Europe conferen=
ce in.</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">
On Wed, Feb 5, 2014 at 4:30 PM, Warren Kumari <span dir=3D"ltr">&lt;<a href=
=3D"mailto:warren@kumari.net" target=3D"_blank">warren@kumari.net</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
[ + 89attendees]<br>
>From a thread on 89attendees (where this really should be...):<br>
<a href=3D"http://www.ietf.org/mail-archive/web/89attendees/current/msg0001=
2.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/89attendees/=
current/msg00012.html</a><br>
<br>
Getting from Paddington to the Hilton:<br>
You could take a cab, but the hotel is 0.4mile away, and an easy, flat<br>
walk. Took me &lt;7 minutes.<br>
Google Maps link: <a href=3D"http://goo.gl/maps/XIAE7" target=3D"_blank">ht=
tp://goo.gl/maps/XIAE7</a><br>
<br>
Walk out onto Praed street - it&#39;s the &quot;main&quot; entrance - basic=
ally<br>
continue walking in the same direction the train was going, up a ramp<br>
/ closed road.<br>
Turn left when you get onto the actual road. You will walk past<br>
Garfunkels bar and a Mercure hotel. On the 2nd or 3rd block, just<br>
before the big metal gates for St Mary&#39;s, look up =A0-- this is where S=
ir<br>
Alexander Flemming discovered Penicillium mould. Say a quick &quot;Thanks&q=
uot;,<br>
life would be substantially worse without this. I would also lose my<br>
primary excuse for keeping a messy desk.<br>
<a href=3D"http://en.wikipedia.org/wiki/Alexander_Fleming" target=3D"_blank=
">http://en.wikipedia.org/wiki/Alexander_Fleming</a><br>
<br>
Continue walking along Praed. The hotel shows up on your left, just<br>
after a Carphone Warehouse (they sell SIMs -<br>
<a href=3D"http://www.carphonewarehouse.com/sims" target=3D"_blank">http://=
www.carphonewarehouse.com/sims</a>. I haven&#39;t checked if this is a<br>
good deal). If you reach Marks&amp;Spenser you have walked right past it.<b=
r>
Turn 180 degrees and walk in.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Wed, Feb 5, 2014 at 4:01 PM, Ross Callon &lt;<a href=3D"mailto:rcallon@j=
uniper.net">rcallon@juniper.net</a>&gt; wrote:<br>
&gt; Is there any danger of the Heathrow Express being shut down if there i=
s a Tube strike?<br>
&gt;<br>
&gt; Also, looking at Google maps, it looks like one should just walk from =
the Paddington Station to the Metropole (9 minute walk, straight up Praed s=
treet to Edgware Rd). =A0For those of us in good health with wheels on our =
suitcase and arriving during daylight, is there any reason not to just walk=
 it?<br>

&gt;<br>
&gt; Thanks, Ross<br>
&gt;<br>
&gt; -----Original Message-----<br>
&gt; From: ietf [mailto:<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounc=
es@ietf.org</a>] On Behalf Of Ted Lemon<br>
&gt; Sent: Wednesday, February 05, 2014 10:15 AM<br>
&gt; To: Scott Brim<br>
&gt; Cc: Tim Chown; IETF discussion list<br>
&gt; Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyst=
er cards)<br>
&gt;<br>
&gt; On Feb 5, 2014, at 10:09 AM, Scott Brim &lt;<a href=3D"mailto:scott.br=
im@gmail.com">scott.brim@gmail.com</a>&gt; wrote:<br>
&gt;&gt; How long does it take by tube? I land at 9:25 pm and would prefer =
to<br>
&gt;&gt; get to the hotel by midnight.<br>
&gt;<br>
&gt; Take Heathrow Express. =A0 You won&#39;t be sorry. =A0 That&#39;s a re=
ally long tube ride at 9:25 pm.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
</div>

--089e0160b88e830fc704f1afe093--

From hallam@gmail.com  Wed Feb  5 14:14: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 3BE601A019C for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 14:14:37 -0800 (PST)
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 0VTrGPlh_1Lx for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 14:14:35 -0800 (PST)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 073EF1A0130 for <ietf@ietf.org>; Wed,  5 Feb 2014 14:14:34 -0800 (PST)
Received: by mail-lb0-f175.google.com with SMTP id p9so827835lbv.20 for <ietf@ietf.org>; Wed, 05 Feb 2014 14:14:33 -0800 (PST)
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=SNB5NTgrL8rIx68OBhfKElRuwu5qGC3SalZN8o50MUg=; b=LbfSrJbyr3bacslROCY45zGKYIqsC169R5qYjGTBfuYgVVCjOZlO9ON2yTnVrx1b2R RVa2Yug/TQsx/jOr0k5Siy5ZgtNNK/KnQhzfE2UzHfzydcokNsxQ751DQ91CWblhkMLn EEXPUd1x10PHOPDTVQI8D6RvcAfHi0iyhCPX0zRbcAVgKio53ujt+VvoeMTdON/zMhdj 8Q5JMxjpFG8PJ+yvwU1X8l4EeMW0RZbbUrVZlxAtBtHakEdZiCVObo/nFz+6aTt0Qyw1 peoGGM07AubF+AZrMusONLHvvbGTsOWghzPq+uQQ74leBl7Nqyz5pppeVxwNEEg/Vcc8 bcZA==
MIME-Version: 1.0
X-Received: by 10.112.138.233 with SMTP id qt9mr2584147lbb.34.1391638473482; Wed, 05 Feb 2014 14:14:33 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Wed, 5 Feb 2014 14:14:33 -0800 (PST)
In-Reply-To: <20140205215644.80620.qmail@joyce.lan>
References: <220FA160-CB28-43BA-A932-C5A19963905E@vpnc.org> <20140205215644.80620.qmail@joyce.lan>
Date: Wed, 5 Feb 2014 17:14:33 -0500
Message-ID: <CAMm+LwhOFAymD_YAG62pSvrOCX0rso5GnuCWuvB_0rkGCZJZMg@mail.gmail.com>
Subject: Re: [89attendees] Mobile phone service in London
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=089e01229710de25f104f1b01477
Cc: IETF Discussion Mailing List <ietf@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 22:14:37 -0000

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

There are shops along the Edgeware road that can provide you with SIMs in
any size or shape or carrier you might need.

They can also assist you if the equipment provided by your US carrier has
certain standards incompatibilities that prevent use on other carrier's
networks.


On Wed, Feb 5, 2014 at 4:56 PM, John Levine <johnl@taugh.com> wrote:

>
> >>
> http://shop.tescomobile.com/mobile-phones/pay-as-you-go#price-min=3D0&pri=
ce-max=3D1000&sort-by=3Dphone-price-low
> >>
> >> (* for those unfamiliar with the UK, Tesco is the largest supermarket
> chain)
> >
> >This should be just fine. Any chance that there is a Tesco at Heathrow?
>
> Nope, just the SIM vending machines near the exits from customs, the
> SIM Local store in Terminal 1, and the Vodafone store in Terminal 5.
>
> For what you want, any SIM should work OK.  Remember that incoming
> calls are paid by the caller (not really "free"), so the only
> difference is the outgoing cost. I doubt you will make =A310 of calls
> during the week no matter what carrier or plan you have.  I've never
> seen them more than 20p/min, so that's at least 50 min of outgoing
> calls.
>
> R's,
> John
>



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

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

<div dir=3D"ltr">There are shops along the Edgeware road that can provide y=
ou with SIMs in any size or shape or carrier you might need.<div><br></div>=
<div>They can also assist you if the equipment provided by your US carrier =
has certain standards incompatibilities that prevent use on other carrier&#=
39;s networks.<br>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Feb 5=
, 2014 at 4:56 PM, John Levine <span dir=3D"ltr">&lt;<a href=3D"mailto:john=
l@taugh.com" target=3D"_blank">johnl@taugh.com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">
<br>
&gt;&gt; <a href=3D"http://shop.tescomobile.com/mobile-phones/pay-as-you-go=
#price-min=3D0&amp;price-max=3D1000&amp;sort-by=3Dphone-price-low" target=
=3D"_blank">http://shop.tescomobile.com/mobile-phones/pay-as-you-go#price-m=
in=3D0&amp;price-max=3D1000&amp;sort-by=3Dphone-price-low</a><br>

&gt;&gt;<br>
&gt;&gt; (* for those unfamiliar with the UK, Tesco is the largest supermar=
ket chain)<br>
&gt;<br>
&gt;This should be just fine. Any chance that there is a Tesco at Heathrow?=
<br>
<br>
Nope, just the SIM vending machines near the exits from customs, the<br>
SIM Local store in Terminal 1, and the Vodafone store in Terminal 5.<br>
<br>
For what you want, any SIM should work OK. =A0Remember that incoming<br>
calls are paid by the caller (not really &quot;free&quot;), so the only<br>
difference is the outgoing cost. I doubt you will make =A310 of calls<br>
during the week no matter what carrier or plan you have. =A0I&#39;ve never<=
br>
seen them more than 20p/min, so that&#39;s at least 50 min of outgoing<br>
calls.<br>
<br>
R&#39;s,<br>
John<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></div></div>

--089e01229710de25f104f1b01477--

From mary.h.barnes@gmail.com  Wed Feb  5 14:39:04 2014
Return-Path: <mary.h.barnes@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 2E0981A0224 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 14:39:04 -0800 (PST)
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 jOaXpLuEItZl for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 14:39:02 -0800 (PST)
Received: from mail-ve0-x234.google.com (mail-ve0-x234.google.com [IPv6:2607:f8b0:400c:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5781A021F for <ietf@ietf.org>; Wed,  5 Feb 2014 14:39:02 -0800 (PST)
Received: by mail-ve0-f180.google.com with SMTP id db12so873464veb.11 for <ietf@ietf.org>; Wed, 05 Feb 2014 14:39:01 -0800 (PST)
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=ztDdKnCObGDnEl4wygYUKbDAoc/dK1jh1c6TwA6h/NU=; b=RW/tiPCRTLndeSVjVS+PYykmFDfKlVZaAmi8CtxTWEjwPLCehfDkhPkV0mE1Ksq7j4 zSSxrOQ3E9CN2arEsVe1/D17SkQ0wSC6tBa49pBwyKigKLUCzQCFJzmACPbWLb3LJRrF B7ZLzCrvU/HiPobidi1QBNKcWQYuLcc/k+mi5AygVBio8RCxW/fwAAVVUB3HuNOI06/d RHRbLBhL2U9gYoTnMd5Rd8izgIkfzkvBeG2FBvZUeLBfZ9Z0YQB38VXyld/8+HWXqGI3 Y84+oQQEgGGJVhdchfz96f2GHruaPYUvahvT7Bn33g8umZGXECsv2bzCEZS3fMhtB0IR 8+6A==
MIME-Version: 1.0
X-Received: by 10.58.4.138 with SMTP id k10mr2675144vek.8.1391639941335; Wed, 05 Feb 2014 14:39:01 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Wed, 5 Feb 2014 14:39:01 -0800 (PST)
In-Reply-To: <CAGL6epK2qbuZNh0Tgt1Aj2wXvf3JggY+UZJiq_DCgMGNgtnWGA@mail.gmail.com>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com> <CAHBU6iv3Zhvxhk0=tmw-9CTNaD2hJmhxs7in6JzrY=iw+xwj5g@mail.gmail.com> <CAGL6epK2qbuZNh0Tgt1Aj2wXvf3JggY+UZJiq_DCgMGNgtnWGA@mail.gmail.com>
Date: Wed, 5 Feb 2014 16:39:01 -0600
Message-ID: <CABmDk8=fNBX6XOAu7gCCQxHCnFE8zs0H9+rEZkfMV1YZnY_CxQ@mail.gmail.com>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=047d7b5d2dc65cf1a904f1b06c81
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Tim Bray <tbray@textuality.com>, 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, 05 Feb 2014 22:39:04 -0000

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

Yes.  Overall, you will find that Central London is quite safe.  I've
walked from Covent Garden area up to the Metropole in the evening by myself
with no issues at all.  While not heavily populated at nite, you should
still have no issues at all on Praed Street.  Although just like any large
city that attracts lots of tourists, pick pockets abound in any crowded
area such as the underground or museums and of course, jet lagged tourists
are always good targets.

Mary.


On Wed, Feb 5, 2014 at 3:12 PM, Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>wrote:

> Is is a safe walk at night too?
>
> Thanks,
>  Rifaat
>
>
>
> On Wed, Feb 5, 2014 at 4:04 PM, Tim Bray <tbray@textuality.com> wrote:
>
>> No reason, just walk it.  After that many hours on planes and trains,
>> probably therapeutic too
>>  On Feb 5, 2014 1:01 PM, "Ross Callon" <rcallon@juniper.net> wrote:
>>
>>> Is there any danger of the Heathrow Express being shut down if there is
>>> a Tube strike?
>>>
>>> Also, looking at Google maps, it looks like one should just walk from
>>> the Paddington Station to the Metropole (9 minute walk, straight up Praed
>>> street to Edgware Rd).  For those of us in good health with wheels on our
>>> suitcase and arriving during daylight, is there any reason not to just walk
>>> it?
>>>
>>> Thanks, Ross
>>>
>>> -----Original Message-----
>>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
>>> Sent: Wednesday, February 05, 2014 10:15 AM
>>> To: Scott Brim
>>> Cc: Tim Chown; IETF discussion list
>>> Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster
>>> cards)
>>>
>>> On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
>>> > How long does it take by tube? I land at 9:25 pm and would prefer to
>>> > get to the hotel by midnight.
>>>
>>> Take Heathrow Express.   You won't be sorry.   That's a really long tube
>>> ride at 9:25 pm.
>>>
>>>
>>>
>>>
>>>
>

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

<div dir=3D"ltr">Yes. =A0Overall, you will find that Central London is quit=
e safe. =A0I&#39;ve walked from Covent Garden area up to the Metropole in t=
he evening by myself with no issues at all. =A0While not heavily populated =
at nite, you should still have no issues at all on Praed Street. =A0Althoug=
h just like any large city that attracts lots of tourists, pick pockets abo=
und in any crowded area such as the underground or museums and of course, j=
et lagged tourists are always good targets.=A0<div>
<br></div><div>Mary.</div></div><div class=3D"gmail_extra"><br><br><div cla=
ss=3D"gmail_quote">On Wed, Feb 5, 2014 at 3:12 PM, Rifaat Shekh-Yusef <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:rifaat.ietf@gmail.com" target=3D"_blank"=
>rifaat.ietf@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">Is is a safe walk at night =
too?<div><br></div><div>Thanks,</div><div>=A0Rifaat</div><div><br></div></d=
iv><div class=3D"HOEnZb">
<div class=3D"h5"><div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">On Wed, Feb 5, 2014 at 4:04 PM, Tim Bray <span dir=3D"ltr">&lt;<a href=
=3D"mailto:tbray@textuality.com" target=3D"_blank">tbray@textuality.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"><p dir=3D"ltr">No reason, just walk it.=A0 A=
fter that many hours on planes and trains, probably therapeutic too</p><div=
>
<div>
<div class=3D"gmail_quote">On Feb 5, 2014 1:01 PM, &quot;Ross Callon&quot; =
&lt;<a href=3D"mailto:rcallon@juniper.net" target=3D"_blank">rcallon@junipe=
r.net</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>


Is there any danger of the Heathrow Express being shut down if there is a T=
ube strike?<br>
<br>
Also, looking at Google maps, it looks like one should just walk from the P=
addington Station to the Metropole (9 minute walk, straight up Praed street=
 to Edgware Rd). =A0For those of us in good health with wheels on our suitc=
ase and arriving during daylight, is there any reason not to just walk it?<=
br>



<br>
Thanks, Ross<br>
<br>
-----Original Message-----<br>
From: ietf [mailto:<a href=3D"mailto:ietf-bounces@ietf.org" target=3D"_blan=
k">ietf-bounces@ietf.org</a>] On Behalf Of Ted Lemon<br>
Sent: Wednesday, February 05, 2014 10:15 AM<br>
To: Scott Brim<br>
Cc: Tim Chown; IETF discussion list<br>
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster ca=
rds)<br>
<br>
On Feb 5, 2014, at 10:09 AM, Scott Brim &lt;<a href=3D"mailto:scott.brim@gm=
ail.com" target=3D"_blank">scott.brim@gmail.com</a>&gt; wrote:<br>
&gt; How long does it take by tube? I land at 9:25 pm and would prefer to<b=
r>
&gt; get to the hotel by midnight.<br>
<br>
Take Heathrow Express. =A0 You won&#39;t be sorry. =A0 That&#39;s a really =
long tube ride at 9:25 pm.<br>
<br>
<br>
<br>
<br>
</blockquote></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--047d7b5d2dc65cf1a904f1b06c81--

From mary.h.barnes@gmail.com  Wed Feb  5 14:40:33 2014
Return-Path: <mary.h.barnes@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 9E06A1A021F for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 14:40:33 -0800 (PST)
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 rMBhyBSVBcvp for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 14:40:31 -0800 (PST)
Received: from mail-ve0-x229.google.com (mail-ve0-x229.google.com [IPv6:2607:f8b0:400c:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 684E31A0274 for <ietf@ietf.org>; Wed,  5 Feb 2014 14:40:31 -0800 (PST)
Received: by mail-ve0-f169.google.com with SMTP id oy12so862818veb.14 for <ietf@ietf.org>; Wed, 05 Feb 2014 14:40:30 -0800 (PST)
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=Wg4KwwI7NAXP3UW+zXUWA+oTbQ2+7kVcLCAeMMbJ+pc=; b=oRb8NL7XXU8gDNMXzk8IdZ6z0WTP/FzR3GTO2HYxD9qk4fIL8kue3Tn8dD4M5SyGhY HhWJJ6JzH6GU9vks/ix2lYNqHA1m47E5qG6hqyUDJKg20RPj9kkde8URIPSjC2LBYsVI dH53xP8Y4It4eeeKfeeAVVGFSIruCJCtfrOIUOUmKRR4xBKQnpuQetH2wUbmKb3HhxRA 3K6fBQ/YBL7Gvu648vg5SCCKulQ7CPSDz5vD0mWxQoLZ9eMkQiRHALecfs2gWDHBrr0u QaSlsAOytlGPoAmakRTzQCHFZFLvxqqFD0ie6s/yfv891mFzKuN7jNphEh1ADa3IMrMM DxCw==
MIME-Version: 1.0
X-Received: by 10.52.170.241 with SMTP id ap17mr2210617vdc.13.1391640030519; Wed, 05 Feb 2014 14:40:30 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Wed, 5 Feb 2014 14:40:30 -0800 (PST)
In-Reply-To: <20140205214907.80539.qmail@joyce.lan>
References: <8218A806-F4A0-4A3D-993B-CF019052D47D@vidyo.com> <20140205214907.80539.qmail@joyce.lan>
Date: Wed, 5 Feb 2014 16:40:30 -0600
Message-ID: <CABmDk8n1CmNiFPVVryjFOvK00Tw3=QX1uToLg7Lq4yRTeLkD9Q@mail.gmail.com>
Subject: Re: [89attendees] IETF 89 London - Tube strikes and Oyster cards
From: Mary Barnes <mary.h.barnes@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=047d7b33d050aca84d04f1b07175
Cc: jonathan@vidyo.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, 05 Feb 2014 22:40:33 -0000

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

On Wed, Feb 5, 2014 at 3:49 PM, John Levine <johnl@taugh.com> wrote:

> >I have an Oyster card that I got when I was in London in 2007 -- I don't
> recall whether it was
> >explicitly a "Visitor" Oyster card.  Is it likely to still work?
>
> Probably.  You can set up an online account on the TfL website,
> register your card to it. It'll tell you what your balance is, and you
> can top up from a credit card.  As I recall, online topups with US
> plastic works.
>
[MB] In my experience, US credit cards (without chips) don't work at any of
the machines in the train or tube stations.  They will of course work at
the counters with real people.  [/MB]

>
> If it demands a UK address, use your hotel's.
>
> https://account.tfl.gov.uk/oyster
>
> R's,
> John
>

--047d7b33d050aca84d04f1b07175
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 Wed, Feb 5, 2014 at 3:49 PM, John 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:1p=
x #ccc solid;padding-left:1ex">&gt;I have an Oyster card that I got when I =
was in London in 2007 -- I don&#39;t recall whether it was<br>
&gt;explicitly a &quot;Visitor&quot; Oyster card. =A0Is it likely to still =
work?<br>
<br>
Probably. =A0You can set up an online account on the TfL website,<br>
register your card to it. It&#39;ll tell you what your balance is, and you<=
br>
can top up from a credit card. =A0As I recall, online topups with US<br>
plastic works.<br></blockquote><div>[MB] In my experience, US credit cards =
(without chips) don&#39;t work at any of the machines in the train or tube =
stations. =A0They will of course work at the counters with real people. =A0=
[/MB]</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
If it demands a UK address, use your hotel&#39;s.<br>
<br>
<a href=3D"https://account.tfl.gov.uk/oyster" target=3D"_blank">https://acc=
ount.tfl.gov.uk/oyster</a><br>
<br>
R&#39;s,<br>
John<br>
</blockquote></div><br></div></div>

--047d7b33d050aca84d04f1b07175--

From mary.h.barnes@gmail.com  Wed Feb  5 14:43:34 2014
Return-Path: <mary.h.barnes@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 96B3F1A0282 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 14:43:34 -0800 (PST)
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 MbeOLHxkoEq9 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 14:43:30 -0800 (PST)
Received: from mail-vc0-x230.google.com (mail-vc0-x230.google.com [IPv6:2607:f8b0:400c:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 79FB61A0275 for <ietf@ietf.org>; Wed,  5 Feb 2014 14:43:30 -0800 (PST)
Received: by mail-vc0-f176.google.com with SMTP id la4so821079vcb.21 for <ietf@ietf.org>; Wed, 05 Feb 2014 14:43:29 -0800 (PST)
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=Nq9KslvZ57oHOUPzxLVJOv+ArAxAAR34ifynItFJsek=; b=XVJGbZ9/ng/kT3HIGCPjKFndzvVZ3kjMi3tGT1Karqx1antqKQ/u9oW9mCX2B6/k6p 9Oh8Q+Z+hKHSREdXckKHE4OTNaGr40/v40u5RbIU6USzZTmuhEguFLDOPmalhea6shpi AS9ggonu732gL04GRmMXulnLr0pnb8465jkYCcKtYmS6AZ2ykYtIvu0FK72Wa1ID3Jxp ULm+uXC066tYRGjf92rS+1xmZmlwhwRO5AiCINNI3gsiZYYJwdydb/4EAkqzAbPOeEm9 NN57HtLEmJ+AxnmKL8brLoXraGofnmhdCaxfv9y17ssGIjwh2elSPWY7Rt+T4ktexLIf EsPQ==
MIME-Version: 1.0
X-Received: by 10.52.166.9 with SMTP id zc9mr2257722vdb.16.1391640209540; Wed, 05 Feb 2014 14:43:29 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Wed, 5 Feb 2014 14:43:29 -0800 (PST)
In-Reply-To: <CABmDk8n1CmNiFPVVryjFOvK00Tw3=QX1uToLg7Lq4yRTeLkD9Q@mail.gmail.com>
References: <8218A806-F4A0-4A3D-993B-CF019052D47D@vidyo.com> <20140205214907.80539.qmail@joyce.lan> <CABmDk8n1CmNiFPVVryjFOvK00Tw3=QX1uToLg7Lq4yRTeLkD9Q@mail.gmail.com>
Date: Wed, 5 Feb 2014 16:43:29 -0600
Message-ID: <CABmDk8nr+JYdpKcXJ2DpKNfV3xVA5824YP3MSmyWMM7-a-uowg@mail.gmail.com>
Subject: Re: [89attendees] IETF 89 London - Tube strikes and Oyster cards
From: Mary Barnes <mary.h.barnes@gmail.com>
To: John Levine <johnl@taugh.com>
Content-Type: multipart/alternative; boundary=001a11c2d992584b2504f1b07c85
Cc: jonathan@vidyo.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, 05 Feb 2014 22:43:35 -0000

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

On Wed, Feb 5, 2014 at 4:40 PM, Mary Barnes <mary.h.barnes@gmail.com> wrote:

>
>
>
> On Wed, Feb 5, 2014 at 3:49 PM, John Levine <johnl@taugh.com> wrote:
>
>> >I have an Oyster card that I got when I was in London in 2007 -- I don't
>> recall whether it was
>> >explicitly a "Visitor" Oyster card.  Is it likely to still work?
>>
>> Probably.  You can set up an online account on the TfL website,
>> register your card to it. It'll tell you what your balance is, and you
>> can top up from a credit card.  As I recall, online topups with US
>> plastic works.
>>
> [MB] In my experience, US credit cards (without chips) don't work at any
> of the machines in the train or tube stations.  They will of course work at
> the counters with real people.  [/MB]
>
[MB] Oops. I read (and responded) too fast, you are referring to being on
the Internet and using a credit card to top-up once you have the Oyster
card.  I buy my Heathrow Connect tickets before I go online with my US
credit card. That should work fine - I was talking about trying to top up
at the machines in the tube stations which theoretically you can do, but it
doesn't work with US credit cards.  Some of the machines take bills and
give change. Some do not.  [/MB]

>
>> If it demands a UK address, use your hotel's.
>>
>> https://account.tfl.gov.uk/oyster
>>
>> R's,
>> John
>>
>
>

--001a11c2d992584b2504f1b07c85
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 Wed, Feb 5, 2014 at 4:40 PM, Mary Barnes <span dir=3D"ltr">&lt;<=
a href=3D"mailto:mary.h.barnes@gmail.com" target=3D"_blank">mary.h.barnes@g=
mail.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 dir=3D"ltr"><br><div class=3D"gmail_extra"><br><br><d=
iv class=3D"gmail_quote">
<div class=3D"im">On Wed, Feb 5, 2014 at 3:49 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>
<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">&gt;I have an Oyster card that I got when I was in London =
in 2007 -- I don&#39;t recall whether it was<br>

&gt;explicitly a &quot;Visitor&quot; Oyster card. =A0Is it likely to still =
work?<br>
<br>
Probably. =A0You can set up an online account on the TfL website,<br>
register your card to it. It&#39;ll tell you what your balance is, and you<=
br>
can top up from a credit card. =A0As I recall, online topups with US<br>
plastic works.<br></blockquote></div><div>[MB] In my experience, US credit =
cards (without chips) don&#39;t work at any of the machines in the train or=
 tube stations. =A0They will of course work at the counters with real peopl=
e. =A0[/MB]</div>
</div></div></div></blockquote><div>[MB] Oops. I read (and responded) too f=
ast, you are referring to being on the Internet and using a credit card to =
top-up once you have the Oyster card.=A0=A0I buy my Heathrow Connect ticket=
s before I go online with my US credit card.=A0That=A0should work fine - I =
was talking about trying to top up at the machines in the tube stations whi=
ch=A0theoretically you can do, but it doesn&#39;t work with US credit cards=
. =A0Some of the machines take bills and give change. Some do not. =A0[/MB]=
=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-left-style:solid;p=
adding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"=
gmail_quote">
<div class=3D"im">
<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">
<br>
If it demands a UK address, use your hotel&#39;s.<br>
<br>
<a href=3D"https://account.tfl.gov.uk/oyster" target=3D"_blank">https://acc=
ount.tfl.gov.uk/oyster</a><br>
<br>
R&#39;s,<br>
John<br>
</blockquote></div></div><br></div></div>
</blockquote></div><br></div></div>

--001a11c2d992584b2504f1b07c85--

From smb@cs.columbia.edu  Wed Feb  5 14:49:09 2014
Return-Path: <smb@cs.columbia.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 2764C1A021C; Wed,  5 Feb 2014 14:49:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.835
X-Spam-Level: 
X-Spam-Status: No, score=-1.835 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_57=0.6, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U3oEYrZuU4pO; Wed,  5 Feb 2014 14:49:07 -0800 (PST)
Received: from eloi.cs.columbia.edu (eloi.cs.columbia.edu [128.59.21.107]) by ietfa.amsl.com (Postfix) with ESMTP id F37D91A021A; Wed,  5 Feb 2014 14:49:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by eloi.cs.columbia.edu (Postfix) with ESMTP id B6B665A2228; Wed,  5 Feb 2014 17:49:05 -0500 (EST)
X-Virus-Scanned: amavisd-new at eloi.cs.columbia.edu
Received: from eloi.cs.columbia.edu ([127.0.0.1]) by localhost (eloi.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Y_3buBtSgHzj; Wed,  5 Feb 2014 17:49:04 -0500 (EST)
Received: from [192.168.2.12] (50-78-158-98-static.hfc.comcastbusiness.net [50.78.158.98]) by eloi.cs.columbia.edu (Postfix) with ESMTPSA id D88165A221E; Wed,  5 Feb 2014 17:49:03 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Steven Bellovin <smb@cs.columbia.edu>
In-Reply-To: <CAHw9_iLSB1zBY9kpiZw5_iD0oRJz57Bv9rGzvL1Os=sAqY2ZQg@mail.gmail.com>
Date: Wed, 5 Feb 2014 17:49:01 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <10E6B94E-5F9E-475A-80E0-16D65AE96680@cs.columbia.edu>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com> <CAHw9_iLSB1zBY9kpiZw5_iD0oRJz57Bv9rGzvL1Os=sAqY2ZQg@mail.gmail.com>
To: Warren Kumari <warren@kumari.net>
X-Mailer: Apple Mail (2.1827)
Cc: IETF discussion list <ietf@ietf.org>, "89attendees@ietf.org" <89attendees@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Feb 2014 22:49:09 -0000

Speaking of SIMs -- where is a good place to buy a local data-enabled =
SIM?

On Feb 5, 2014, at 4:30 40PM, Warren Kumari <warren@kumari.net> wrote:

> [ + 89attendees]
> =46rom a thread on 89attendees (where this really should be...):
> http://www.ietf.org/mail-archive/web/89attendees/current/msg00012.html
>=20
> Getting from Paddington to the Hilton:
> You could take a cab, but the hotel is 0.4mile away, and an easy, flat
> walk. Took me <7 minutes.
> Google Maps link: http://goo.gl/maps/XIAE7
>=20
> Walk out onto Praed street - it's the "main" entrance - basically
> continue walking in the same direction the train was going, up a ramp
> / closed road.
> Turn left when you get onto the actual road. You will walk past
> Garfunkels bar and a Mercure hotel. On the 2nd or 3rd block, just
> before the big metal gates for St Mary's, look up  -- this is where =
Sir
> Alexander Flemming discovered Penicillium mould. Say a quick "Thanks",
> life would be substantially worse without this. I would also lose my
> primary excuse for keeping a messy desk.
> http://en.wikipedia.org/wiki/Alexander_Fleming
>=20
> Continue walking along Praed. The hotel shows up on your left, just
> after a Carphone Warehouse (they sell SIMs -
> http://www.carphonewarehouse.com/sims. I haven't checked if this is a
> good deal). If you reach Marks&Spenser you have walked right past it.
> Turn 180 degrees and walk in.
>=20
> On Wed, Feb 5, 2014 at 4:01 PM, Ross Callon <rcallon@juniper.net> =
wrote:
>> Is there any danger of the Heathrow Express being shut down if there =
is a Tube strike?
>>=20
>> Also, looking at Google maps, it looks like one should just walk from =
the Paddington Station to the Metropole (9 minute walk, straight up =
Praed street to Edgware Rd).  For those of us in good health with wheels =
on our suitcase and arriving during daylight, is there any reason not to =
just walk it?
>>=20
>> Thanks, Ross
>>=20
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
>> Sent: Wednesday, February 05, 2014 10:15 AM
>> To: Scott Brim
>> Cc: Tim Chown; IETF discussion list
>> Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and =
Oyster cards)
>>=20
>> On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
>>> How long does it take by tube? I land at 9:25 pm and would prefer to
>>> get to the hotel by midnight.
>>=20
>> Take Heathrow Express.   You won't be sorry.   That's a really long =
tube ride at 9:25 pm.
>>=20
>>=20
>>=20
>>=20
>=20


		--Steve Bellovin, https://www.cs.columbia.edu/~smb






From johnl@taugh.com  Wed Feb  5 15:04: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 0ECB11A0280 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 15:04:32 -0800 (PST)
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 ofSWbrAUE-Sb for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 15:04:31 -0800 (PST)
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 C20751A0224 for <ietf@ietf.org>; Wed,  5 Feb 2014 15:04:30 -0800 (PST)
Received: (qmail 68882 invoked from network); 5 Feb 2014 23:04:29 -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=10d11.52f2c37d.k1402; i=johnl-iecc.com@submit.iecc.com; bh=g5HPqthEFukequRHNGfKlSgDQTGEmqJbgTnKhZAUcGQ=; b=eTebVixPjXRTQJycUxaBl2R1Qv497pcHsarJyrKcqP45rL1J1AsNI+WsPIQ6WqKweA/qnRCj3D5oAZ6H+eLaGRlrxH/KtKN1ydIS3MIvU/3S0eRkr8be1qqQ+KJ9VDZPiQzWat2ibimTn3c04irmC2qTYGNU5AKCpc1TfbQrK1VuNc/11JSNBGzTiSLYIO0GRHk0Qsh4iZH1WspJEDVEt9bmfGpmb6tLHoGoDcASiKrJd6o8/roMH+oZzGAIDUEF
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=10d11.52f2c37d.k1402; olt=johnl-iecc.com@submit.iecc.com; bh=g5HPqthEFukequRHNGfKlSgDQTGEmqJbgTnKhZAUcGQ=; b=LMpby6pvaCK3QHqUjCPbCSAYAjupo3Ttm7oubAYGTocMO1Lvju53Oy/Q91Vr5vDPfp/eugCJImFNvGcL38rLWEP+PLTu3KIAp+OAiUPTWHTj3JgZwax5XnYCC09wS85q5ZcgQ/e+QJJpKUACSpO9FahPbl5OIeeHcNbTCn+iHBSc/Dn3oNq0lDFLVuBhMHwxuLJZ4RpHzpzZKOWzvbkIqVsOrRwFVxSlSNEBkH9Mpqte9pBX3nU8dkROnSg0CiLr
Received: from joyce.lan ([24.59.92.2]) by nimap.iecc.com ([64.57.183.76]) with ESMTPSA (TLS1.0/X.509/SHA1, johnl@iecc.com) via TCP; 05 Feb 2014 23:04:29 -0000
Date: 5 Feb 2014 18:04:28 -0500
Message-ID: <alpine.BSF.2.00.1402051758480.80421@joyce.lan>
From: "John R Levine" <johnl@taugh.com>
To: "Mary Barnes" <mary.h.barnes@gmail.com>
Subject: Re: [89attendees] IETF 89 London - Tube strikes and Oyster cards
In-Reply-To: <CABmDk8nr+JYdpKcXJ2DpKNfV3xVA5824YP3MSmyWMM7-a-uowg@mail.gmail.com>
References: <8218A806-F4A0-4A3D-993B-CF019052D47D@vidyo.com> <20140205214907.80539.qmail@joyce.lan> <CABmDk8n1CmNiFPVVryjFOvK00Tw3=QX1uToLg7Lq4yRTeLkD9Q@mail.gmail.com> <CABmDk8nr+JYdpKcXJ2DpKNfV3xVA5824YP3MSmyWMM7-a-uowg@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
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, 05 Feb 2014 23:04:32 -0000

> card.  I buy my Heathrow Connect tickets before I go online with my US
> credit card. That should work fine - I was talking about trying to top up
> at the machines in the tube stations which theoretically you can do, but it
> doesn't work with US credit cards.

The machines want a Chip+PIN card.  This amazing spreadsheet at Google 
Docs has every Chip+PIN or Chip+Signature (not as good) card available 
from US banks.  It's a bit late to be getting one for the IETF, but it'll 
come in handy in Berlin.

https://docs.google.com/spreadsheet/ccc?key=0Ani-u3tGk5hedGRvcE1ELVg5UmlGZk01SHZvTUMxdUE

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

PS: I have a Chip+PIN Amex card, which was a major pain in the patoot to 
get.

From mnot@mnot.net  Wed Feb  5 15:09:07 2014
Return-Path: <mnot@mnot.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 F3FEE1A0275 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 15:09:06 -0800 (PST)
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 ML58aPk0wFM8 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 15:09:03 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF071A015A for <ietf@ietf.org>; Wed,  5 Feb 2014 15:09:03 -0800 (PST)
Received: from [192.168.1.55] (unknown [118.209.71.195]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 473EE22E1FA for <ietf@ietf.org>; Wed,  5 Feb 2014 18:09:00 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <10E6B94E-5F9E-475A-80E0-16D65AE96680@cs.columbia.edu>
Date: Thu, 6 Feb 2014 10:08:57 +1100
Content-Transfer-Encoding: 7bit
Message-Id: <E04B17D1-77C3-4CC7-92F4-9AE31905C86A@mnot.net>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com> <CAHw9_iLSB1zBY9kpiZw5_iD0oRJz57Bv9rGzvL1Os=sAqY2ZQg@mail.gmail.com> <10E6B94E-5F9E-475A-80E0-16D65AE96680@cs.columbia.edu>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1827)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "89attendees@ietf.org" <89attendees@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: Wed, 05 Feb 2014 23:09:07 -0000

Could folks please move this thread to the attendees list?

Thanks...


--
Mark Nottingham   http://www.mnot.net/




From paul.hoffman@vpnc.org  Wed Feb  5 15:18:38 2014
Return-Path: <paul.hoffman@vpnc.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 E9F2A1A021F for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 15:18:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id maDTvB94F413 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 15:18:38 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 226C71A021A for <ietf@ietf.org>; Wed,  5 Feb 2014 15:18:38 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s15MwXWB039086 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 5 Feb 2014 15:58:34 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: [89attendees] Mobile phone service in London
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20140205215644.80620.qmail@joyce.lan>
Date: Wed, 5 Feb 2014 15:18:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B4139952-28D3-4C9B-8695-5447E05EA3D5@vpnc.org>
References: <20140205215644.80620.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.1827)
Cc: "ietf@ietf.org 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, 05 Feb 2014 23:18:39 -0000

On Feb 5, 2014, at 1:56 PM, John Levine <johnl@taugh.com> wrote:

> Nope, just the SIM vending machines near the exits from customs, the
> SIM Local store in Terminal 1, and the Vodafone store in Terminal 5.
>=20
> For what you want, any SIM should work OK. =20

Not if the one phone I have that is SIMable is kinda crappy. That's what =
I said in my earlier message. And you have even seen that phone. :-)

--Paul Hoffman=

From iad@ietf.org  Wed Feb  5 16:47:33 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 EFE061A0274; Wed,  5 Feb 2014 16:47:32 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fRdhhFU-U3oV; Wed,  5 Feb 2014 16:47:30 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D230C1A01BC; Wed,  5 Feb 2014 16:47:30 -0800 (PST)
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: Proposed Changes to IAOC Communications Plan; Request for Community Input
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140206004730.12491.71674.idtracker@ietfa.amsl.com>
Date: Wed, 05 Feb 2014 16:47:30 -0800
Cc: iaoc@ietf.org, iab@iab.org, ietf@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: Thu, 06 Feb 2014 00:47:33 -0000

All;

The IAOC is seeking community feedback on proposed changes to the IAOC 
Communications Plan.

In 2007 the IAOC adopted a Communications Plan in recognition of its responsibility 
under BCP 101 to operate IASA in a transparent manner.  The Plan identifies the 
information to be communicated, the desired frequency and the mode of those communications.  

The Plan can found here:  <http://iaoc.ietf.org/documents/IAOC_Communications_Plan_7-12-07.pdf>.

A markup of the Plan with the proposed changes can be found here: 
<http://iaoc.ietf.org/documents/IAOC-Communications-Plan-2014-Revisions-03.pdf>  The matrix at 
the end of the current plan will be modified to reflect changes adopted by the IAOC following community 
input.

The IAOC is proposing the substantive changes set out below.

The IAOC welcomes your feedback.  All comments received by 17 February will be considered for the 
proposed changes.

Thanks.

Ray
IAD

A.  Proposed Revisions to the Plan
B.  Proposed Additions to the Plan
C.  Proposed Deletions to the Plan

A.  Proposed Revisions to the Plan

	5.2.2 Unaudited Financial Report

	FROM

	The Unaudited Financial Report will provide an
	unaudited review of the financial performance of IASA
	against the previous yearâ€™s Budget in March or April of the
	following year. The unaudited report will not be available
	publicly, but will serve to inform the IAOC in anticipation of
	the audited financial report. The report is prepared by the
	Internet Society.

	TO 

	The unaudited Financial Report, prepared by the Internet
	Society, will provide a review of the annual financial
	performance of IASA against budget. This report will be
	available as soon after the end of the calendar year as
	possible, and will be made public. [RFC 4071, Â§6, 7]

	Reason for Change:  Conformance with ISOC practices.  
	Plus the addition of making the Report public.

5.2.6. Financial Forecast

	FROM

	A financial forecast will be prepared quarterly
	and for ISOC Board of Trustee meetings as required.  [RFC
	4071, Â§6]

	TO

	5.2.6. Financial Forecast
	Year-End Forecasts shall be prepared by the IAD using the
	financial statements prepared following the first and second
	IETF meetings of the year as advice to the Internet Society,
	and for the IAOC and IAD to manage operations against the
	current annual budget and take appropriate actions. [RFC
	4071, Â§6]

	Reason for Change: The YEFs are addressed in the IAOC Budget 
	Process & Calendar <http://iaoc.ietf.org/budget-and-finance.html>

B.  Proposed Additions to the Plan

	5.4.1 Subpoenas and Other Legal Requests

	All subpoenas and other legal requests received by the IAOC 
	or the IETF will be published on the IAOC website together
	with their responses. 

	Reason for Change:  Greater transparency.

C.  Proposed Deletions to the Plan

	4.3. IETF Journal
	Periodically the IAOC shall provide reports in the IETF
	Journal. Reports in the Journal shall also be posted on the
	IAOC website.

	Reason for Change: This reporting is redundant with 
	Plenary reports and other online reports on the IAOC site.
	<http://www.internetsociety.org/fr/publications/ietf-journal>

	5.2.3. Audited Financial Report

	The Audited Financial Report will provide an audited review
	of the financial performance of IASA against the Budget.
	The audited report will be available from the Internet
	Society by June of each year. [RFC 4071, Â§6, 7]

	Reason for Change: IASA is not eligible for a separate audit or audited
	financial statement. IASA financial results are audited as a
	part of Internet Societyâ€™s financial audit and therefore
	combined in the consolidated financial statements of
	Internet Society. Therefore, ISOC recommends that section 
	5.2.3 be removed.

	5.3.6. IASA Annual Review
	In March of each year the IAOC shall publish an IASA
	Annual Review reporting on the financial and operational
	health of the organization, as well as its success in meeting its
	goals for the year.

	Reason for Change: Report has not been prepared as it was considered 
	that 3 Plenary reports a year provided the same information.

	5.3.13. Audit Procedures

	The IAOC and ISOC shall agree upon and publish
	procedures for reporting and auditing of the IASA accounts.
	[RFC 4071, Â§5.1]

	Reason for Change: IASA is not eligible for a separate audit or audited
	financial statement. IASA financial results are audited as a part of Internet 
	Societyâ€™s financial audit and therefore 	combined in the consolidated 
	financial statements of 	Internet Society. Therefore, ISOC recommends 
	that section 5.3.13 be removed.

From bob.hinden@gmail.com  Wed Feb  5 17:35:08 2014
Return-Path: <bob.hinden@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 BB5E81A02F5 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 17:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.889
X-Spam-Level: 
X-Spam-Status: No, score=-0.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, 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 4SSX8QlocsxG for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 17:35:07 -0800 (PST)
Received: from mail-qa0-x22c.google.com (mail-qa0-x22c.google.com [IPv6:2607:f8b0:400d:c00::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 7C2E21A02F2 for <ietf@ietf.org>; Wed,  5 Feb 2014 17:35:07 -0800 (PST)
Received: by mail-qa0-f44.google.com with SMTP id w5so1845431qac.31 for <ietf@ietf.org>; Wed, 05 Feb 2014 17:35:06 -0800 (PST)
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=H0aY3H9jnukNrnEW4QY2RcSrYol6EmQEXzAjD5IyhAw=; b=j3RWH6BCWpUjJh5xUJwV5iT7ec25fX2Q14DgtBQjlrVP2Ft0n/xwWi+UtUWbH2gW8H 5B1CK3GI0PIbVTSNjcVNuVVyhZfUQmUzyyevhGt3oA4/g/NAZnI+82NwjN+3GFqdu2dX I7C+B65EAItU2MHcRtEpZlTLhDHFdFAExcHSoYg6pi6wWak0mOIsl7HE9R6y1zRDeCr+ dRyoO4/t2rYsw/OfyYvQaBbLMoZVRVdICbeTmKXegIWXst0V0rP60lZYICQOZ5eNiZe3 RJjSMVkTtoslmA7qKzYsH7BjNEWLb1YqWiR6/e0IHHpKN5vWc+bSSLUgreT5FMAT/ekE xyrQ==
X-Received: by 10.140.91.23 with SMTP id y23mr7719869qgd.3.1391650506576; Wed, 05 Feb 2014 17:35:06 -0800 (PST)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id k61sm22370262qge.12.2014.02.05.17.35.00 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Feb 2014 17:35:00 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_2703A445-E2FC-4058-9927-1BB24BDE7E45"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Please use 89attendees@ietf.org [was Re: IETF 89 London - Tube strikes and Oyster cards]
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <CABmDk8m-Co_pWQt8MfmTrhjx2iFktxJqSRTUfa+i+qJDAecM4w@mail.gmail.com>
Date: Wed, 5 Feb 2014 17:34:58 -0800
Message-Id: <35F86904-07BE-42B5-9317-ABDB53EFD7E8@gmail.com>
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <E13DC59F-E4DF-4482-82BB-F533D740BE2B@nominum.com> <CABmDk8njOtBs_CpEW1cSZsA8SFueFKSj+YDF+90_CgzYTrBiEA@mail.gmail.com> <52F25C12.5080407@dcrocker.net> <CABmDk8m-Co_pWQt8MfmTrhjx2iFktxJqSRTUfa+i+qJDAec M4w@mail.gmail.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: Bob Hinden <bob.hinden@gmail.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, 06 Feb 2014 01:35:09 -0000

--Apple-Mail=_2703A445-E2FC-4058-9927-1BB24BDE7E45
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

Could we all please use the IETF 89 attendee list instead of the IETF =
list to discuss IETF89 local stuff.  It is:

  89attendees@ietf.org

Thanks,
Bob


--Apple-Mail=_2703A445-E2FC-4058-9927-1BB24BDE7E45
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

iQEcBAEBCgAGBQJS8ubDAAoJEK7rdBF357uotysH/0WBJOX3oN1zCA7xSJPAxvZ+
lBdVyepo7l6X3ajYabXoGB0mmGZZDNZljBQdc8JScLbiPQ2jjIJ5PduGiaD8whe2
J+Nl9OYfqsK1OQCql+X/dO2K4UJxOoV1F+pcgY9OHViXHfK7419xUCBUXfl1oWEJ
zgv/EID4ffbweXoISBAyGGioU7grkQ7vdHgszSmZTNulbz8SEYjXAg10/YWaaY0U
W2ICuqoDX4k2cbcnJ30zoV/ChPoo3AK7m9UDfHwSHVo8t61YyNWhphhm9WR+aZhD
w93TBPqP3PpI2Zgqs/010ITG3m8zOL/EfQ0eDqHjKOFrgzZ+d14Oj3H1SRcxlxE=
=zbnz
-----END PGP SIGNATURE-----

--Apple-Mail=_2703A445-E2FC-4058-9927-1BB24BDE7E45--

From dwm@xpasc.com  Wed Feb  5 19:36:50 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 CBD501A0352 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.567
X-Spam-Level: 
X-Spam-Status: No, score=-1.567 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 AUGJpEAFs3D5 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:36:50 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8E51A034E for <ietf@ietf.org>; Wed,  5 Feb 2014 19:36:49 -0800 (PST)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id D64BD4094D for <ietf@ietf.org>; Thu,  6 Feb 2014 03:36:47 +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 s163akpD029478 for <ietf@ietf.org>; Wed, 5 Feb 2014 19:36:47 -0800
Date: Wed, 5 Feb 2014 19:36:46 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
In-Reply-To: <20140206004730.12491.71674.idtracker@ietfa.amsl.com>
Message-ID: <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com>
References: <20140206004730.12491.71674.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2014 03:36:51 -0000

On Wed, 5 Feb 2014, IETF Administrative Director wrote:

> B.  Proposed Additions to the Plan
>
> 	5.4.1 Subpoenas and Other Legal Requests
>
> 	All subpoenas and other legal requests received by the IAOC
> 	or the IETF will be published on the IAOC website together
> 	with their responses.
>
> 	Reason for Change:  Greater transparency.

Some such requests may include the requirement that they not be revealed.
I don't think it wise to have a published policy which doesn't allow for
such a legal restriction.

From randy@psg.com  Wed Feb  5 19:44:54 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 973901A0358 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:44:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DMqsZ4N7LZEI for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:44:53 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id BD1D41A0357 for <ietf@ietf.org>; Wed,  5 Feb 2014 19:44:53 -0800 (PST)
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 1WBFtS-00069R-I9; Thu, 06 Feb 2014 03:44:50 +0000
Date: Thu, 06 Feb 2014 12:44:49 +0900
Message-ID: <m2bnykgb0u.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Morris <dwm@xpasc.com>
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
In-Reply-To: <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com>
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@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
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, 06 Feb 2014 03:44:54 -0000

>> B.  Proposed Additions to the Plan
>>
>> 	5.4.1 Subpoenas and Other Legal Requests
>>
>> 	All subpoenas and other legal requests received by the IAOC
>> 	or the IETF will be published on the IAOC website together
>> 	with their responses.
>>
>> 	Reason for Change:  Greater transparency.
> 
> Some such requests may include the requirement that they not be
> revealed.

they should be rejected out of hand.  "we can not read your email"

From ajs@anvilwalrusden.com  Wed Feb  5 19:46:43 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 F21481A0361 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:46:42 -0800 (PST)
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 PVmT7ybDkSg2 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:46:42 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id EC0BC1A035D for <ietf@ietf.org>; Wed,  5 Feb 2014 19:46:41 -0800 (PST)
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 DD0658A031 for <ietf@ietf.org>; Thu,  6 Feb 2014 03:46:40 +0000 (UTC)
Date: Wed, 5 Feb 2014 22:46:39 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
Message-ID: <20140206034638.GE21114@mx1.yitter.info>
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2014 03:46:43 -0000

On Wed, Feb 05, 2014 at 07:36:46PM -0800, David Morris wrote:
> Some such requests may include the requirement that they not be revealed.
> I don't think it wise to have a published policy which doesn't allow for
> such a legal restriction.

I agree that we need to have a way to conform to a legal requirement.
Are there cases (I imagine that this is one for Jorge) where the mere
fact that a subpoena was received, the matter of which was (legally)
forbidden to publish, is also itself forbidden to publish?  (That is,
do people get subpoenas that not only specify withholding the details,
but prevent the fact of subpoena from being divulged?)  If not,
perhaps the rules could be amended to allow "Cannot publish before
$date due to legal constraint."

If so, boy are we in trouble.

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From brian.e.carpenter@gmail.com  Wed Feb  5 19:54: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 3C8F01A0362 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:54:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.501
X-Spam-Level: 
X-Spam-Status: No, score=-3.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RANDOM_SURE=0.499, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pw2YIMo_7nCI for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:54:10 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 11EDF1A035B for <ietf@ietf.org>; Wed,  5 Feb 2014 19:54:09 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id kl14so1171791pab.29 for <ietf@ietf.org>; Wed, 05 Feb 2014 19:54:09 -0800 (PST)
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=B48VCZ5Qbx2iwmkq2frCuG7vP7JlMj9abXaKpOJ+dlY=; b=Ug6y9qEUb8M97Z9WK6KRSXlFO+iw91tIlyw4cDh2GtO9IDXJ7qlIAE1UzqfkyuK/am pTg9leL8cGQFQ58mRbt4N+xDtv2AXxtm6Ioa+INekTv200NEatTkmuVK/NNUnUbJr3eV ruk5+Qni2QpEDw85DG7LrNF3SuRJskUJEtfTZHT7ZVtXi0pSMLlIsXIb5ifLO6zMugGQ toDVkinfHxMu7821PBySbLY2qZigo8T8q1JHQfOhn9RdViBttws7BiGqwNfR+dI3aNGd Sh5v9Jfd1GAJIYYSCebRhYwQ1k0NpWcH7qRZN2pjq7otQq5+YAs+rr7cCicmVBsOi886 Tp6Q==
X-Received: by 10.68.203.102 with SMTP id kp6mr8598358pbc.14.1391658849255; Wed, 05 Feb 2014 19:54:09 -0800 (PST)
Received: from [192.168.178.23] (80.199.69.111.dynamic.snap.net.nz. [111.69.199.80]) by mx.google.com with ESMTPSA id xs1sm210805474pac.7.2014.02.05.19.54.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 05 Feb 2014 19:54:08 -0800 (PST)
Message-ID: <52F30767.1070401@gmail.com>
Date: Thu, 06 Feb 2014 16:54:15 +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: Randy Bush <randy@psg.com>
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com> <m2bnykgb0u.wl%randy@psg.com>
In-Reply-To: <m2bnykgb0u.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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, 06 Feb 2014 03:54:11 -0000

On 06/02/2014 16:44, Randy Bush wrote:
>>> B.  Proposed Additions to the Plan
>>>
>>> 	5.4.1 Subpoenas and Other Legal Requests
>>>
>>> 	All subpoenas and other legal requests received by the IAOC
>>> 	or the IETF will be published on the IAOC website together
>>> 	with their responses.
>>>
>>> 	Reason for Change:  Greater transparency.
>> Some such requests may include the requirement that they not be
>> revealed.
> 
> they should be rejected out of hand.  "we can not read your email"

Does that work for National Security Letters too?

From randy@psg.com  Wed Feb  5 19:56:45 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 7A2661A035B for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:56:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.936
X-Spam-Level: 
X-Spam-Status: No, score=-3.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oz8qXsxhM28g for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 19:56:44 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id C51EE1A0363 for <ietf@ietf.org>; Wed,  5 Feb 2014 19:56:41 -0800 (PST)
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 1WBG4t-0006BN-BJ; Thu, 06 Feb 2014 03:56:39 +0000
Date: Thu, 06 Feb 2014 12:56:38 +0900
Message-ID: <m28utogah5.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
In-Reply-To: <52F30767.1070401@gmail.com>
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com> <m2bnykgb0u.wl%randy@psg.com> <52F30767.1070401@gmail.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
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, 06 Feb 2014 03:56:45 -0000

>>>> B.  Proposed Additions to the Plan
>>>>
>>>> 	5.4.1 Subpoenas and Other Legal Requests
>>>>
>>>> 	All subpoenas and other legal requests received by the IAOC
>>>> 	or the IETF will be published on the IAOC website together
>>>> 	with their responses.
>>>>
>>>> 	Reason for Change:  Greater transparency.
>>> Some such requests may include the requirement that they not be
>>> revealed.
>> 
>> they should be rejected out of hand.  "we can not read your email"
> 
> Does that work for National Security Letters too?

i was thinking of them specifically.  and yes, i have gone to jail for
my political beliefs in the past and would do so again.

randy

From dwm@xpasc.com  Wed Feb  5 20:49:04 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 D78E61A0277 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 20:49:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.271
X-Spam-Level: 
X-Spam-Status: No, score=-0.271 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, FH_RELAY_NODNS=1.451, GB_I_LETTER=-2, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.793, 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 oINfkHM-uyDS for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 20:49:04 -0800 (PST)
Received: from c2w3p-2.abacamail.com (unknown [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 02BA81A029D for <ietf@ietf.org>; Wed,  5 Feb 2014 20:49:03 -0800 (PST)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id D54E040366 for <ietf@ietf.org>; Thu,  6 Feb 2014 04:49:01 +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 s164n1Dn030056 for <ietf@ietf.org>; Wed, 5 Feb 2014 20:49:01 -0800
Date: Wed, 5 Feb 2014 20:49:01 -0800 (PST)
From: David Morris <dwm@xpasc.com>
To: ietf@ietf.org
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
In-Reply-To: <m28utogah5.wl%randy@psg.com>
Message-ID: <alpine.LRH.2.01.1402052045540.29416@egate.xpasc.com>
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com> <m2bnykgb0u.wl%randy@psg.com> <52F30767.1070401@gmail.com> <m28utogah5.wl%randy@psg.com>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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, 06 Feb 2014 04:49:05 -0000

On Thu, 6 Feb 2014, Randy Bush wrote:

> >>>> B.  Proposed Additions to the Plan
> >>>>
> >>>> 	5.4.1 Subpoenas and Other Legal Requests
> >>>>
> >>>> 	All subpoenas and other legal requests received by the IAOC
> >>>> 	or the IETF will be published on the IAOC website together
> >>>> 	with their responses.
> >>>>
> >>>> 	Reason for Change:  Greater transparency.
> >>> Some such requests may include the requirement that they not be
> >>> revealed.
> >>
> >> they should be rejected out of hand.  "we can not read your email"
> >
> > Does that work for National Security Letters too?
>
> i was thinking of them specifically.  and yes, i have gone to jail for
> my political beliefs in the past and would do so again.

As an individual, I laud your willingness to do that, but we can't
ask our administrative staff or volunteer leaders to do that as
a matter of policy. Nor do I think we can afford the legal costs
associated with a court battle.

From randy@psg.com  Wed Feb  5 21:45:06 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 7B0BC1A0373 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 21:45:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.936
X-Spam-Level: 
X-Spam-Status: No, score=-1.936 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GBMpegLesXN7 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 21:45:05 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 3EE681A0365 for <ietf@ietf.org>; Wed,  5 Feb 2014 21:45:05 -0800 (PST)
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 1WBHln-0006Ns-6Q; Thu, 06 Feb 2014 05:45:03 +0000
Date: Thu, 06 Feb 2014 14:45:02 +0900
Message-ID: <m2wqh8eqw1.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: David Morris <dwm@xpasc.com>
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
In-Reply-To: <alpine.LRH.2.01.1402052045540.29416@egate.xpasc.com>
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com> <m2bnykgb0u.wl%randy@psg.com> <52F30767.1070401@gmail.com> <m28utogah5.wl%randy@psg.com> <alpine.LRH.2.01.1402052045540.29416@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
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: Thu, 06 Feb 2014 05:45:06 -0000

maybe we should not focus our policies and procedures on ephemeral fear
based corner case aberrations of one country, which i suspect they will
look back on as they now look back on putting japanese americans in
concentration camps.

randy

From tbray@textuality.com  Wed Feb  5 21:53:52 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 5C39A1A0033 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 21:53:52 -0800 (PST)
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 FDBqdSQ9TWHd for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 21:53:51 -0800 (PST)
Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by ietfa.amsl.com (Postfix) with ESMTP id D4E4D1A0030 for <ietf@ietf.org>; Wed,  5 Feb 2014 21:53:50 -0800 (PST)
Received: by mail-vc0-f182.google.com with SMTP id id10so1079504vcb.41 for <ietf@ietf.org>; Wed, 05 Feb 2014 21:53:49 -0800 (PST)
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=II494AIS6BBYkdnsx39vB8JN8UiKebxbXusdeFnTdIg=; b=LqalJstzp5LYzM9wd39MGCJEmDG9HmN929WEAySFbfIZ78oNipCQr5C2bOeScu4KVe O5Il+xVoPvciS81PPFcpCvHcIpq2vQeAXgbSUn3j8GaqcPZ/ldEI0J6xsa/68Yva5J5O i6G9sqizz4+fw9ljAqJDWRSmMZ/yJtDozHqEvv8uADEAnOqXoL/kj7fkpML9lCcdDULh FwVpIyyjQbY4Jjgnp1N4V+7at4VJz93vAL6EcF/dw1NPqMXjnuR0rpSzB+MuEnS4WDC9 NDlMeat8C60iGF1Wux2n3SeN3tBHRKv2iaGdC1PqCWHNnF46ZCdQtlAKo40fLjTPbaeR nAvw==
X-Gm-Message-State: ALoCoQldmMfEC3Xnr3ywgrbrEs2dXGkH/V8kfjHEASwFyAylz8YxAyOgZ3DsrbCntTYL1B7AiJBu
MIME-Version: 1.0
X-Received: by 10.58.86.230 with SMTP id s6mr4297999vez.16.1391666029790; Wed, 05 Feb 2014 21:53:49 -0800 (PST)
Received: by 10.220.98.73 with HTTP; Wed, 5 Feb 2014 21:53:49 -0800 (PST)
X-Originating-IP: [24.114.54.44]
In-Reply-To: <B4139952-28D3-4C9B-8695-5447E05EA3D5@vpnc.org>
References: <20140205215644.80620.qmail@joyce.lan> <B4139952-28D3-4C9B-8695-5447E05EA3D5@vpnc.org>
Date: Wed, 5 Feb 2014 21:53:49 -0800
Message-ID: <CAHBU6iuFAjvTAxg6fu6NgJzPeDeThDoKPsnOLLkyG+xsDmyY+A@mail.gmail.com>
Subject: Re: [89attendees] Mobile phone service in London
From: Tim Bray <tbray@textuality.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: multipart/alternative; boundary=047d7b6d95085a1df104f1b67f09
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org 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, 06 Feb 2014 05:53:52 -0000

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

In most Heathrow Terminals you can buy a =E2=80=9C3 Network=E2=80=9D SIM fr=
om a vending
machine with your credit card before you even get to customs.  It=E2=80=99s=
 maybe a
little pricy at =C2=A320 but it has plenty of data to get you through a few=
 days.


On Wed, Feb 5, 2014 at 3:18 PM, Paul Hoffman <paul.hoffman@vpnc.org> wrote:

> On Feb 5, 2014, at 1:56 PM, John Levine <johnl@taugh.com> wrote:
>
> > Nope, just the SIM vending machines near the exits from customs, the
> > SIM Local store in Terminal 1, and the Vodafone store in Terminal 5.
> >
> > For what you want, any SIM should work OK.
>
> Not if the one phone I have that is SIMable is kinda crappy. That's what =
I
> said in my earlier message. And you have even seen that phone. :-)
>
> --Paul Hoffman

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

<div dir=3D"ltr">In most Heathrow Terminals you can buy a =E2=80=9C3 Networ=
k=E2=80=9D SIM from a vending machine with your credit card before you even=
 get to customs. =C2=A0It=E2=80=99s maybe a little pricy at=C2=A0=C2=A320 b=
ut it has plenty of data to get you through a few days.</div>
<div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Feb 5=
, 2014 at 3:18 PM, Paul Hoffman <span dir=3D"ltr">&lt;<a href=3D"mailto:pau=
l.hoffman@vpnc.org" target=3D"_blank">paul.hoffman@vpnc.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"><div class=3D"im">On Feb 5, 2014, at 1:56 PM=
, John Levine &lt;<a href=3D"mailto:johnl@taugh.com">johnl@taugh.com</a>&gt=
; wrote:<br>

<br>
&gt; Nope, just the SIM vending machines near the exits from customs, the<b=
r>
&gt; SIM Local store in Terminal 1, and the Vodafone store in Terminal 5.<b=
r>
&gt;<br>
&gt; For what you want, any SIM should work OK.<br>
<br>
</div>Not if the one phone I have that is SIMable is kinda crappy. That&#39=
;s what I said in my earlier message. And you have even seen that phone. :-=
)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
--Paul Hoffman</font></span></blockquote></div><br></div>

--047d7b6d95085a1df104f1b67f09--

From paf@frobbit.se  Wed Feb  5 21:55:20 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 4E6391A02B2 for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 21:55:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.287
X-Spam-Level: 
X-Spam-Status: No, score=-3.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, GB_I_LETTER=-2, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nLAg2-q8h9zt for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 21:55:17 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 7ACEC1A0030 for <ietf@ietf.org>; Wed,  5 Feb 2014 21:55:17 -0800 (PST)
Received: from ix-2.local (frobbit.cust.teleservice.net [85.30.128.225]) by mail.frobbit.se (Postfix) with ESMTPSA id 01DE2202E8; Thu,  6 Feb 2014 06:55:15 +0100 (CET)
Message-ID: <52F323C0.609@frobbit.se>
Date: Thu, 06 Feb 2014 06:55:12 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com> <m2bnykgb0u.wl%randy@psg.com> <52F30767.1070401@gmail.com> <m28utogah5.wl%randy@psg.com>
In-Reply-To: <m28utogah5.wl%randy@psg.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5lBU9gW19gFF6Ue41fF29E9wSNKJpuX2J"
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, 06 Feb 2014 05:55:20 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--5lBU9gW19gFF6Ue41fF29E9wSNKJpuX2J
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-06 04:56, Randy Bush wrote:
>>>>> B.  Proposed Additions to the Plan
>>>>> >>>>
>>>>> >>>> 	5.4.1 Subpoenas and Other Legal Requests
>>>>> >>>>
>>>>> >>>> 	All subpoenas and other legal requests received by the IAOC
>>>>> >>>> 	or the IETF will be published on the IAOC website together
>>>>> >>>> 	with their responses.
>>>>> >>>>
>>>>> >>>> 	Reason for Change:  Greater transparency.
>>>> >>> Some such requests may include the requirement that they not be
>>>> >>> revealed.
>>> >>=20
>>> >> they should be rejected out of hand.  "we can not read your email"=

>> >=20
>> > Does that work for National Security Letters too?
>
> i was thinking of them specifically.  and yes, i have gone to jail for
> my political beliefs in the past and would do so again.

A "we have problems here" response for me would trigger a request to
review under what jurisdiction IETF operate.

We are a standards body that writes documents.

Not an operator or such that deals with operational issues.

   Patrik



--5lBU9gW19gFF6Ue41fF29E9wSNKJpuX2J
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.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFS8yPDrMabGguI180RAs9SAJ9L9RCV5xQmrCmPkHk+1pcrJNrN0QCfaYcb
zC5V2pxCmcxqIo+ygk9Gleo=
=KO0h
-----END PGP SIGNATURE-----

--5lBU9gW19gFF6Ue41fF29E9wSNKJpuX2J--

From dwm@xpasc.com  Wed Feb  5 22:50:34 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 02AE71A037F for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 22:50:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.447
X-Spam-Level: 
X-Spam-Status: No, score=-1.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RANDOM_SURE=0.499, GB_I_LETTER=-2, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_15=0.6, 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 K9Rb-Xpl72ts for <ietf@ietfa.amsl.com>; Wed,  5 Feb 2014 22:50:33 -0800 (PST)
Received: from c2w3p-2.abacamail.com (c2w3p-2.abacamail.com [67.231.154.153]) by ietfa.amsl.com (Postfix) with ESMTP id 36E231A0046 for <ietf@ietf.org>; Wed,  5 Feb 2014 22:50:32 -0800 (PST)
Received: from xpasc.com (h-68-164-244-188.snva.ca.megapath.net [68.164.244.188]) by c2w3p-2.abacamail.com (Postfix) with ESMTP id 3D9DA408B0 for <ietf@ietf.org>; Thu,  6 Feb 2014 06:50:31 +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 s166oUXH030890 for <ietf@ietf.org>; Wed, 5 Feb 2014 22:50:30 -0800
Date: Wed, 5 Feb 2014 22:50:30 -0800 (PST)
From: David Morris <dwm@xpasc.com>
cc: ietf@ietf.org
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
In-Reply-To: <52F323C0.609@frobbit.se>
Message-ID: <alpine.LRH.2.01.1402052233450.29416@egate.xpasc.com>
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com> <m2bnykgb0u.wl%randy@psg.com> <52F30767.1070401@gmail.com> <m28utogah5.wl%randy@psg.com> <52F323C0.609@frobbit.se>
User-Agent: Alpine 2.01 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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, 06 Feb 2014 06:50:34 -0000

On Thu, 6 Feb 2014, Patrik F?ltstr?m wrote:

> On 2014-02-06 04:56, Randy Bush wrote:
> >>>>> B.  Proposed Additions to the Plan
> >>>>> >>>>
> >>>>> >>>> 	5.4.1 Subpoenas and Other Legal Requests
> >>>>> >>>>
> >>>>> >>>> 	All subpoenas and other legal requests received by the IAOC
> >>>>> >>>> 	or the IETF will be published on the IAOC website together
> >>>>> >>>> 	with their responses.
> >>>>> >>>>
> >>>>> >>>> 	Reason for Change:  Greater transparency.
> >>>> >>> Some such requests may include the requirement that they not be
> >>>> >>> revealed.
> >>> >>
> >>> >> they should be rejected out of hand.  "we can not read your email"
> >> >
> >> > Does that work for National Security Letters too?
> >
> > i was thinking of them specifically.  and yes, i have gone to jail for
> > my political beliefs in the past and would do so again.
>
> A "we have problems here" response for me would trigger a request to
> review under what jurisdiction IETF operate.
>
> We are a standards body that writes documents.
>
> Not an operator or such that deals with operational issues.

But we have administrative services, servers, etc. in the United States.
We can argue philosophically about what we are, but if our administrative
support folks or leadership is served with a NSL or FBI warrantless
supoena which stipulates non-disclosure the folks served will have a
hard time with non-compliance. And if our communications Plan stipulates
we always disclose the legal requests, then we have less transparency
than if we have a plan that requires disclosure unless legally prohibited.

If we have the funding or pro-bono legal help to challenge such requests,
then a policy which provides a framework for evaluating which requests
to challenge.

From adrian@olddog.co.uk  Thu Feb  6 00:31:34 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 487CC1A0090; Thu,  6 Feb 2014 00:31:34 -0800 (PST)
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 vE2WHsaSyHiY; Thu,  6 Feb 2014 00:31:32 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id D5B941A006A; Thu,  6 Feb 2014 00:31:31 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s168VRXt026754; Thu, 6 Feb 2014 08:31:27 GMT
Received: from 950129200 (idanet5.ida.ing.tu-bs.de [134.169.115.102]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s168VQWu026742 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Feb 2014 08:31:26 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>, <routing-discussion@ietf.org>
Subject: Handling the situation with two Juniper routing ADs
Date: Thu, 6 Feb 2014 08:31:22 -0000
Message-ID: <00b401cf2315$d25e3b30$771ab190$@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: Ac8jFaz50+gj4WZoTWaSyYKgNq/nHw==
Content-Language: en-gb
Cc: Alia Atlas <akatlas@juniper.net>, iesg@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, 06 Feb 2014 08:31:34 -0000

All,

It is relatively unusual for two ADs in the same area to have the same company
affiliation. Although, of course, ADs discard their affiliations in
consideration of all elements of their AD role, we are aware that this situation
may cause some concern and unease. Therefore we have decided to err on the side
of caution, remind everyone of the normal practices that take into account
affiliations, and put in place some operating guidelines that we will endeavor
to follow while this situation exists.

We should note that this situation will not last for more than the next year:
Adrian absolutely will not be seeking reselection as an AD at the end of this
year (March 2015).

First, whenever anyone has a concern of actual or potential bias by us as ADs,
we will encourage such a concern to be reported to us and to the IETF chair. In
such circumstances, we will supply the chair with as much information as we have
and will abide by the chair's decision as to what action we should take.

We would like to remind you of the following standard practices:

- As has become the normal practice in the Routing Area, the ADs will depend
  heavily on the diverse Routing Area Directorate to provide public, non-biased
  and critical reviews of all Routing Area documents.   We will be conscious of
  the affiliation of the reviewers when requesting reviews.

- Different affiliations between the working group chairs of any single
  working group is always considered desirable. 

Here are our additional operating guidelines for the following rare cases:

- When a document has authors with only one affiliation and that is ours, even
  though there is a mitigating effect of WG chairs and document shepherds, we
will
  ask another AD to act as responsible AD. This may have the effect of slowing
the
  progress of such documents.

- Whenever there are contentious IPR issues related to a document in the Routing
  Area we will seek public guidance from another AD. Whenever the contentious 
  IPR is owned by Juniper we will ask another AD to act as responsible AD.

- Whenever there is significant disagreement within a working group in which
there
  is a strong view held by participants affiliated with Juniper, and where the
AD
  is called upon to guide or instruct the chairs, we will always seek public
input
  from another AD.

- In the event of any complaints made against WG chairs in the Routing Area
where
  those chairs are affiliated to Juniper we will always seek input from other
  another AD with as much public visibility as the complaint.

Please be aware that for Adrian this represents a change in normal automatic
processing that he has developed over 5 years. For Alia the challenge is that
she will be on the steep learning curve that all new ADs go through. Please
excuse any fumbles, draw them to our attention and allow us to rectify them.

May we both take this opportunity to thanks Stewart for his excellent service as
an AD over the last four years.

Alia and Adrian


From daedulus@btconnect.com  Thu Feb  6 02:37:48 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 EEBDD1A00BC for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 02:37:47 -0800 (PST)
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 o4_vqOjqVcFb for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 02:37:45 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe006.messaging.microsoft.com [216.32.180.16]) by ietfa.amsl.com (Postfix) with ESMTP id 92E531A0362 for <ietf@ietf.org>; Thu,  6 Feb 2014 02:37:45 -0800 (PST)
Received: from mail15-va3-R.bigfish.com (10.7.14.248) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.22; Thu, 6 Feb 2014 10:37:44 +0000
Received: from mail15-va3 (localhost [127.0.0.1])	by mail15-va3-R.bigfish.com (Postfix) with ESMTP id 0FBFEC0194; Thu,  6 Feb 2014 10:37:44 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.253.85; KIP:(null); UIP:(null); IPV:NLI; H:DB3PRD0710HT002.eurprd07.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -14
X-BigFish: PS-14(zz9371Ie0f1h542I1432Id799hzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h20f7h2189h1d1ah1d2ah21bch1fc6hzz1de098h1033IL8275bh8275dh1de097h186068hz2dh2a8h5a9h839h947hd24hf0ah1177h1179h1288h12a5h12a9h12bdh137ah139eh13b6h1441h1504h1537h162dh1631h1758h17f1h184fh1898h18e1h1946h19b5h19ceh19f0h1ad9h1b0ah2222h224fh1d0ch1d2eh1d3fh1dfeh1dffh1e1dh1e23h2218h2216h226dh22d0h24afh2327h2336h2438h2461h2487h24ach24d7h2516h2545h304l1d11m1155h)
Received: from mail15-va3 (localhost.localdomain [127.0.0.1]) by mail15-va3 (MessageSwitch) id 1391683061315335_30177; Thu,  6 Feb 2014 10:37:41 +0000 (UTC)
Received: from VA3EHSMHS020.bigfish.com (unknown [10.7.14.250])	by mail15-va3.bigfish.com (Postfix) with ESMTP id 3623A32004B;	Thu,  6 Feb 2014 10:37:41 +0000 (UTC)
Received: from DB3PRD0710HT002.eurprd07.prod.outlook.com (157.56.253.85) by VA3EHSMHS020.bigfish.com (10.7.99.30) with Microsoft SMTP Server (TLS) id 14.16.227.3; Thu, 6 Feb 2014 10:37:36 +0000
Received: from pc6 (86.156.141.19) by pod51017.outlook.com (10.255.75.37) with Microsoft SMTP Server (TLS) id 14.16.411.0; Thu, 6 Feb 2014 10:37:33 +0000
Message-ID: <021d01cf2326$cd603f00$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: John R Levine <johnl@taugh.com>
References: <8218A806-F4A0-4A3D-993B-CF019052D47D@vidyo.com> <20140205214907.80539.qmail@joyce.lan> <CABmDk8n1CmNiFPVVryjFOvK00Tw3=QX1uToLg7Lq4yRTeLkD9Q@mail.gmail.com> <CABmDk8nr+JYdpKcXJ2DpKNfV3xVA5824YP3MSmyWMM7-a-uowg@mail.gmail.com> <alpine.BSF.2.00.1402051758480.80421@joyce.lan>
Subject: Re: [89attendees] IETF 89 London - Tube strikes and Oyster cards
Date: Thu, 6 Feb 2014 10:32:52 +0000
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: [86.156.141.19]
X-OriginatorOrg: btconnect.com
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
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, 06 Feb 2014 10:37:48 -0000

----- Original Message -----
From: "John R Levine" <johnl@taugh.com>
To: "Mary Barnes" <mary.h.barnes@gmail.com>
Cc: <ietf@ietf.org>
Sent: Wednesday, February 05, 2014 11:04 PM
>
> The machines want a Chip+PIN card.  This amazing spreadsheet at Google
> Docs has every Chip+PIN or Chip+Signature (not as good) card available
> from US banks.  It's a bit late to be getting one for the IETF, but
it'll
> come in handy in Berlin.
>
>
https://docs.google.com/spreadsheet/ccc?key=0Ani-u3tGk5hedGRvcE1ELVg5Uml
GZk01SHZvTUMxdUE

Chip and pin has been punted as the answer to all fraud problems for so
long in the UK now that you do get businesses that refuse to take
chipless cards - although that is not likely in the touristy parts of
London which realise that not all countries have gone down that road..

The other quirk is one that came up on this list six months ago of
Faraday cages, given the aggressive rollout in the UK of contactless
cards.  Here it is not that you need the technology, rather that the
technology will try to debit your account without you noticing, as I
witnessed while queueing (another quirk of the UK) last week when the
terminal reported that the amount was too great for the card because the
limit for contactless operation is currently 20 pounds and the
transaction was for 50 - the customer was waiting to insert his card for
chip and pin operation but the contactless machine had got there first.
If you have more than one card, then this can be a problem

Tom Petch.











> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
> Please consider the environment before reading this e-mail.
>
> PS: I have a Chip+PIN Amex card, which was a major pain in the patoot
to
> get.
>



From christer.holmberg@ericsson.com  Thu Feb  6 02:42:11 2014
Return-Path: <christer.holmberg@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 5A0471A00C4 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 02:42:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.299
X-Spam-Level: **
X-Spam-Status: No, score=2.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_IS_IT_OUR_ACCOUNT=4.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 Jk-eSWOB52gk for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 02:42:10 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 7D6571A00BC for <ietf@ietf.org>; Thu,  6 Feb 2014 02:42:09 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-a9-52f366ffa6f3
Received: from ESESSHC008.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id A5.46.04249.FF663F25; Thu,  6 Feb 2014 11:42:07 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC008.ericsson.se ([153.88.183.42]) with mapi id 14.02.0387.000; Thu, 6 Feb 2014 11:42:07 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: t.p. <daedulus@btconnect.com>, John R Levine <johnl@taugh.com>
Subject: RE: [89attendees] IETF 89 London - Tube strikes and Oyster cards
Thread-Topic: [89attendees] IETF 89 London - Tube strikes and Oyster cards
Thread-Index: AQHPIyeOS0QTtLUwf0Kt/ygPQhkJIZqoCarg
Date: Thu, 6 Feb 2014 10:42:06 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D15F081@ESESSMB209.ericsson.se>
References: <8218A806-F4A0-4A3D-993B-CF019052D47D@vidyo.com> <20140205214907.80539.qmail@joyce.lan> <CABmDk8n1CmNiFPVVryjFOvK00Tw3=QX1uToLg7Lq4yRTeLkD9Q@mail.gmail.com> <CABmDk8nr+JYdpKcXJ2DpKNfV3xVA5824YP3MSmyWMM7-a-uowg@mail.gmail.com> <alpine.BSF.2.00.1402051758480.80421@joyce.lan> <021d01cf2326$cd603f00$4001a8c0@gateway.2wire.net>
In-Reply-To: <021d01cf2326$cd603f00$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrCLMWRmVeSWpSXmKPExsUyM+Jvje7/tM9BBnemmFusOmBn8WzjfBaL 0z1rmByYPXYd/cHusWTJTyaPe1tCA5ijuGxSUnMyy1KL9O0SuDJefDrPUnBeoGL7ZOMGxvm8 XYycHBICJhKXZj5hg7DFJC7cWw9kc3EICRxhlFg9/xsjhLOIUaLr6SGWLkYODjYBC4nuf9og DSICThLnDz8Ha2YWUJZ4umkOE4gtLOAp8WvtdVaIGi+J5jfP2EBaRQSMJLZM1gAJswioSNx9 doEFxOYV8JVY1DaDGWLVLSaJPS/PMIMkOAXsJQ5sfgk2hxHouO+n1jBB7BKXuPVkPhPE0QIS S/acZ4awRSVePv7HCmErSfzYcIkFol5HYsHuT1B3akssW/iaGWKxoMTJmU9YJjCKzUIydhaS lllIWmYhaVnAyLKKkaM4tTgpN93IYBMjMGYObvltsYPx8l+bQ4zSHCxK4rwf3zoHCQmkJ5ak ZqemFqQWxReV5qQWH2Jk4uCUamAMYLv5908D2xTmDZe3rdG8Kpf94PIyC9lKpk0VF9I9+38E qBimyom/kY3YKNf8P23LMnfXWw9m9e437vr2oLdfN2kBz7oeziMBZTt5OabLu02u6n+Uuup/ qbUQ/6NfrOqP7BmWeQd3Prr4I7eoeU1t39/ZR0SuMhnuefQ1Le/G3nUXSm73nShRYinOSDTU Yi4qTgQAV0dp4WcCAAA=
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, 06 Feb 2014 10:42:11 -0000

Could you PLEASE keep this discussion on the attendees list.

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of t.p.
Sent: 6. helmikuuta 2014 12:33
To: John R Levine
Cc: ietf@ietf.org
Subject: Re: [89attendees] IETF 89 London - Tube strikes and Oyster cards

----- Original Message -----
From: "John R Levine" <johnl@taugh.com>
To: "Mary Barnes" <mary.h.barnes@gmail.com>
Cc: <ietf@ietf.org>
Sent: Wednesday, February 05, 2014 11:04 PM
>
> The machines want a Chip+PIN card.  This amazing spreadsheet at Google=20
> Docs has every Chip+PIN or Chip+Signature (not as good) card available=20
> from US banks.  It's a bit late to be getting one for the IETF, but
it'll
> come in handy in Berlin.
>
>
https://docs.google.com/spreadsheet/ccc?key=3D0Ani-u3tGk5hedGRvcE1ELVg5Uml
GZk01SHZvTUMxdUE

Chip and pin has been punted as the answer to all fraud problems for so lon=
g in the UK now that you do get businesses that refuse to take chipless car=
ds - although that is not likely in the touristy parts of London which real=
ise that not all countries have gone down that road..

The other quirk is one that came up on this list six months ago of Faraday =
cages, given the aggressive rollout in the UK of contactless cards.  Here i=
t is not that you need the technology, rather that the technology will try =
to debit your account without you noticing, as I witnessed while queueing (=
another quirk of the UK) last week when the terminal reported that the amou=
nt was too great for the card because the limit for contactless operation i=
s currently 20 pounds and the transaction was for 50 - the customer was wai=
ting to insert his card for chip and pin operation but the contactless mach=
ine had got there first.
If you have more than one card, then this can be a problem

Tom Petch.











> Regards,
> John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY=20
> Please consider the environment before reading this e-mail.
>
> PS: I have a Chip+PIN Amex card, which was a major pain in the patoot
to
> get.
>



From lear@cisco.com  Thu Feb  6 04:37:53 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 A806B1A03B7 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 04:37:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.036
X-Spam-Level: 
X-Spam-Status: No, score=-10.036 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.535, 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 TgTzsHBo4YJU for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 04:37:52 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id D309F1A03AF for <IETF@ietf.org>; Thu,  6 Feb 2014 04:37:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=542; q=dns/txt; s=iport; t=1391690271; x=1392899871; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=m1FqhvgdWlrT9yTX8alXc7Ufrb5HjJCEDX7ayFjHtJs=; b=loj2DErRk94zVuwkJd1tEAJynG/WJhX30jqBZ5FpoAAgIn6MFlnGDBz+ +drh/d0ZSTrPFFM6fPgCoNl7kvx4XFpnVCK7fdwMfKBjwwcQPvKDCxcKh 6R4Sr6C8j/OGw9c7LVBJZiEC/KiqATzvdpKs66A5XnJQ5HukpbrH79kFE 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlgFAMCB81KQ/khR/2dsb2JhbABZgww4g1i7IYFZFnSCJwEFAQEgMSQuCAIFFgsCCwMCAQIBFRYMCBkIAQGIAQ2dd48VoSITBIEpjW6CWYFJBJgrkiGDLjs
X-IronPort-AV: E=Sophos;i="4.95,793,1384300800";  d="scan'208";a="4074442"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 06 Feb 2014 12:37:49 +0000
Received: from mctiny.local ([10.61.198.139]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s16CbmM4016915 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <IETF@ietf.org>; Thu, 6 Feb 2014 12:37:49 GMT
Message-ID: <52F3821D.2070807@cisco.com>
Date: Thu, 06 Feb 2014 13:37:49 +0100
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.3.0
MIME-Version: 1.0
To: IETF@ietf.org
Subject: discussion of governance principles
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2014 12:37:53 -0000

Hi everyone,

The IAB has a list called internetgovtech to discuss key issues relating
to policy and the Internet architecture.  I have kicked off a discussion
about principles of Internet governance on that list as relates to the
IETF on that list.  The list specifically not meant to supplant other
lists on the general discussion of principles, as ISOC and /1net (among
others) have lists for that.  Rather, what are the big issues for us?

If you want to join...

https://www.iab.org/mailman/listinfo/internetgovtech

Eliot

From Chris.Dearlove@baesystems.com  Thu Feb  6 05:41:49 2014
Return-Path: <Chris.Dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A48D21A00F2 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 05:41:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.435
X-Spam-Level: 
X-Spam-Status: No, score=-7.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XITGPePdAjh1 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 05:41:45 -0800 (PST)
Received: from ukmta3.baesystems.com (ukmta3.baesystems.com [20.133.40.55]) by ietfa.amsl.com (Postfix) with ESMTP id 575561A0116 for <ietf@ietf.org>; Thu,  6 Feb 2014 05:41:45 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="347214196"
Received: from unknown (HELO baemasodc005.greenlnk.net) ([10.108.52.29]) by Baemasodc001ir.sharelnk.net with ESMTP; 06 Feb 2014 13:41:43 +0000
From: "Dearlove, Christopher (UK)" <Chris.Dearlove@baesystems.com>
X-IronPort-AV: E=Sophos;i="4.95,793,1384300800"; d="scan'208";a="45292218"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasodc005.greenlnk.net with ESMTP; 06 Feb 2014 13:41:43 +0000
Received: from GLKXM0002V.GREENLNK.net ([169.254.5.106]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.03.0174.001; Thu, 6 Feb 2014 13:41:43 +0000
To: Ross Callon <rcallon@juniper.net>, Ted Lemon <ted.lemon@nominum.com>, Scott Brim <scott.brim@gmail.com>
Subject: RE: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
Thread-Topic: IETF 89 London - Tube from LHR (was Tube strikes and Oyster cards)
Thread-Index: AQHPIoRxYXyzxtiglUu6V8FqgX0uxZqmxQcAgABgt4CAARcwIA==
Date: Thu, 6 Feb 2014 13:41:43 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30D4024F2C0@GLKXM0002V.GREENLNK.net>
References: <CAPv4CP-RcqnKCxV1ChqZrh4ZPWuGMV1Kr-1OT44dT8vrMAqT2Q@mail.gmail.com> <4A4447A2-2DDC-4B16-BDA7-D8D1E081B923@nominum.com> <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com>
In-Reply-To: <b1a89449efdc4180a2f6757666b5498d@CO2PR05MB636.namprd05.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, 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, 06 Feb 2014 13:41:49 -0000

Shouldn't be. Different organisations.

-- =

Christopher Dearlove
Senior Principal Engineer, Communications Group
Communications, Networks and Image Analysis Capability
BAE Systems Advanced Technology Centre
West Hanningfield Road, Great Baddow, Chelmsford, CM2 8HN, UK
Tel: +44 1245 242194=A0|  Fax: +44 1245 242124
chris.dearlove@baesystems.com | http://www.baesystems.com

BAE Systems (Operations) Limited
Registered Office: Warwick House, PO Box 87, Farnborough Aerospace Centre, =
Farnborough, Hants, GU14 6YU, UK
Registered in England & Wales No: 1996687

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ross Callon
Sent: 05 February 2014 21:01
To: Ted Lemon; Scott Brim
Cc: Tim Chown; IETF discussion list
Subject: RE: IETF 89 London - Tube from LHR (was Tube strikes and Oyster ca=
rds)

----------------------! WARNING ! ---------------------- This message origi=
nates from outside our organisation, either from an external partner or fro=
m the internet.
Consider carefully whether you should click on any links, open any attachme=
nts or reply.
Follow the 'Report Suspicious Emails' link on IT matters for instructions o=
n reporting suspicious email messages.
--------------------------------------------------------

Is there any danger of the Heathrow Express being shut down if there is a T=
ube strike? =


Also, looking at Google maps, it looks like one should just walk from the P=
addington Station to the Metropole (9 minute walk, straight up Praed street=
 to Edgware Rd).  For those of us in good health with wheels on our suitcas=
e and arriving during daylight, is there any reason not to just walk it? =


Thanks, Ross

-----Original Message-----
From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Ted Lemon
Sent: Wednesday, February 05, 2014 10:15 AM
To: Scott Brim
Cc: Tim Chown; IETF discussion list
Subject: Re: IETF 89 London - Tube from LHR (was Tube strikes and Oyster ca=
rds)

On Feb 5, 2014, at 10:09 AM, Scott Brim <scott.brim@gmail.com> wrote:
> How long does it take by tube? I land at 9:25 pm and would prefer to =

> get to the hotel by midnight.

Take Heathrow Express.   You won't be sorry.   That's a really long tube ri=
de at 9:25 pm.





********************************************************************
This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender.
You should not copy it or use it for any purpose nor disclose or
distribute its contents to any other person.
********************************************************************


From chelliot@gmail.com  Thu Feb  6 09:31:49 2014
Return-Path: <chelliot@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 9A4781A01FD for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 09:31:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.178
X-Spam-Level: 
X-Spam-Status: No, score=-2.178 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FH_RANDOM_SURE=0.499, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YSRXgaWM895T for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 09:31:47 -0800 (PST)
Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 54C4F1A01E2 for <ietf@ietf.org>; Thu,  6 Feb 2014 09:31:47 -0800 (PST)
Received: by mail-la0-f45.google.com with SMTP id b8so1748699lan.32 for <ietf@ietf.org>; Thu, 06 Feb 2014 09:31:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=39h4YsJVajEWB0siS/LwYVSIqbG6MK4NbAzIJhI4D+Y=; b=kWMI7M+LkBOptw4j72oy7gruL972VxZKMi8JVDoUkSaXdc8dYrzkHr3BwKUVZCdbuZ ZNekZ4qhhhUq9bGfkuJ115TmJAmRCncC0R7cBA7pmBa8Nf2rEOsbKjHSVR/qAJqn2SPi gQ/yKDOx5xlOd74npKlGtzPZaRCmUjILeoxvrat6DUXxxOAI+m4BuFX4W15j66X7GkyT 37NdMvsvQGa0fLX8DDiOjj2CvM/NLKLDvnwirR9wozPMvWwS07hteBfj2QLlde4sfgsh lFXogHSvLxmKjEbuSA3hWR/nWFBwrI71SZR5iKLGPDIZbBpADRmXFPNB0OOVcXDsenM6 WnnQ==
MIME-Version: 1.0
X-Received: by 10.112.164.35 with SMTP id yn3mr2196001lbb.45.1391707905541; Thu, 06 Feb 2014 09:31:45 -0800 (PST)
Sender: chelliot@gmail.com
Received: by 10.114.65.11 with HTTP; Thu, 6 Feb 2014 09:31:45 -0800 (PST)
In-Reply-To: <alpine.LRH.2.01.1402052233450.29416@egate.xpasc.com>
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com> <m2bnykgb0u.wl%randy@psg.com> <52F30767.1070401@gmail.com> <m28utogah5.wl%randy@psg.com> <52F323C0.609@frobbit.se> <alpine.LRH.2.01.1402052233450.29416@egate.xpasc.com>
Date: Thu, 6 Feb 2014 12:31:45 -0500
X-Google-Sender-Auth: 14w0x6JrRNglZrvjhhJJxtGM8wk
Message-ID: <CAO_RpcK4C89vwG9T-rF32+=1YTKm_vr3SxD_FPLq3QbfqJ3Bwg@mail.gmail.com>
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
From: Chris Elliott <chelliot@pobox.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c335305749e904f1c03f92
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chelliot@pobox.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, 06 Feb 2014 17:31:49 -0000

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

On Thursday, February 6, 2014, David Morris <dwm@xpasc.com> wrote:

>
>
> On Thu, 6 Feb 2014, Patrik F?ltstr?m wrote:
>
> > On 2014-02-06 04:56, Randy Bush wrote:
> > >>>>> B.  Proposed Additions to the Plan
> > >>>>> >>>>
> > >>>>> >>>>    5.4.1 Subpoenas and Other Legal Requests
> > >>>>> >>>>
> > >>>>> >>>>    All subpoenas and other legal requests received by the IAOC
> > >>>>> >>>>    or the IETF will be published on the IAOC website together
> > >>>>> >>>>    with their responses.
> > >>>>> >>>>
> > >>>>> >>>>    Reason for Change:  Greater transparency.
> > >>>> >>> Some such requests may include the requirement that they not be
> > >>>> >>> revealed.
> > >>> >>
> > >>> >> they should be rejected out of hand.  "we can not read your email"
> > >> >
> > >> > Does that work for National Security Letters too?
> > >
> > > i was thinking of them specifically.  and yes, i have gone to jail for
> > > my political beliefs in the past and would do so again.
> >
> > A "we have problems here" response for me would trigger a request to
> > review under what jurisdiction IETF operate.
> >
> > We are a standards body that writes documents.
> >
> > Not an operator or such that deals with operational issues.
>
> But we have administrative services, servers, etc. in the United States.
> We can argue philosophically about what we are, but if our administrative
> support folks or leadership is served with a NSL or FBI warrantless
> supoena which stipulates non-disclosure the folks served will have a
> hard time with non-compliance. And if our communications Plan stipulates
> we always disclose the legal requests, then we have less transparency
> than if we have a plan that requires disclosure unless legally prohibited.


Some companies have announced that they are taking the reverse
approach--reporting on a periodic basis that they have received no requests
that they cannot disclose over the last period. It's obvious what happens
if one or more are received.

Chris.


> If we have the funding or pro-bono legal help to challenge such requests,
> then a policy which provides a framework for evaluating which requests
> to challenge.



-- 
Chris Elliott
chelliot@pobox.com

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

On Thursday, February 6, 2014, David Morris &lt;<a href=3D"mailto:dwm@xpasc=
.com">dwm@xpasc.com</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
On Thu, 6 Feb 2014, Patrik F?ltstr?m wrote:<br>
<br>
&gt; On 2014-02-06 04:56, Randy Bush wrote:<br>
&gt; &gt;&gt;&gt;&gt;&gt; B. =A0Proposed Additions to the Plan<br>
&gt; &gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A05.4.1 Subpoenas and Other=
 Legal Requests<br>
&gt; &gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0All subpoenas and other l=
egal requests received by the IAOC<br>
&gt; &gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0or the IETF will be publi=
shed on the IAOC website together<br>
&gt; &gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0with their responses.<br>
&gt; &gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt;<br>
&gt; &gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0Reason for Change: =A0Gre=
ater transparency.<br>
&gt; &gt;&gt;&gt;&gt; &gt;&gt;&gt; Some such requests may include the requi=
rement that they not be<br>
&gt; &gt;&gt;&gt;&gt; &gt;&gt;&gt; revealed.<br>
&gt; &gt;&gt;&gt; &gt;&gt;<br>
&gt; &gt;&gt;&gt; &gt;&gt; they should be rejected out of hand. =A0&quot;we=
 can not read your email&quot;<br>
&gt; &gt;&gt; &gt;<br>
&gt; &gt;&gt; &gt; Does that work for National Security Letters too?<br>
&gt; &gt;<br>
&gt; &gt; i was thinking of them specifically. =A0and yes, i have gone to j=
ail for<br>
&gt; &gt; my political beliefs in the past and would do so again.<br>
&gt;<br>
&gt; A &quot;we have problems here&quot; response for me would trigger a re=
quest to<br>
&gt; review under what jurisdiction IETF operate.<br>
&gt;<br>
&gt; We are a standards body that writes documents.<br>
&gt;<br>
&gt; Not an operator or such that deals with operational issues.<br>
<br>
But we have administrative services, servers, etc. in the United States.<br=
>
We can argue philosophically about what we are, but if our administrative<b=
r>
support folks or leadership is served with a NSL or FBI warrantless<br>
supoena which stipulates non-disclosure the folks served will have a<br>
hard time with non-compliance. And if our communications Plan stipulates<br=
>
we always disclose the legal requests, then we have less transparency<br>
than if we have a plan that requires disclosure unless legally prohibited.<=
/blockquote><div><br></div><div>Some companies have announced that they are=
=A0taking=A0the reverse approach--reporting=A0on a periodic=A0basis that th=
ey=A0have received no requests that they=A0cannot disclose over the last pe=
riod. It&#39;s obvious what happens if one or more are received<span></span=
>.</div>
<div><br></div><div>Chris.</div><div>=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">
If we have the funding or pro-bono legal help to challenge such requests,<b=
r>
then a policy which provides a framework for evaluating which requests<br>
to challenge.=A0</blockquote><br><br>-- <br>Chris Elliott<br><a href=3D"mai=
lto:chelliot@pobox.com">chelliot@pobox.com</a><br><br>

--001a11c335305749e904f1c03f92--

From rlb@ipv.sx  Thu Feb  6 11:12:11 2014
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 650DD1A03F9 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:12:11 -0800 (PST)
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 B_EBl37sxgZj for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:12:09 -0800 (PST)
Received: from mail-ob0-f169.google.com (mail-ob0-f169.google.com [209.85.214.169]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEF11A00C9 for <ietf@ietf.org>; Thu,  6 Feb 2014 11:12:09 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id wo20so2747260obc.14 for <ietf@ietf.org>; Thu, 06 Feb 2014 11:12:08 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=1zyn0JFfEN+fwus9SY8+kwwutcL7rwOUKSnGlNcfIZE=; b=Lv0qiXEhqbhCnnf2aIoVwBLH/ej3GqqGXAsES9VAf9s7slUskH7DqID80ad2rja4+b lLA431SahzWsBtflXU5TQBtAOGm8sGOREcHCnr2Bs9TI3P3YZZbJu9+On0AuNKZ//un8 cLHqjqApMbBcH4H95gcTGCHLew2/1MqmMLbacZuVVufPgMdTEFHu2Zk9EiQp2Q0e0ghU tfCigZqzYr3qW4isM7lOpsY2SglTgGfgWG6JO/gZ8ewcO/yHPb2SzfZir4Ru174SzISY 2FqQcSUtORhoDBqF/Txll5dS9wsL039BfMAkFXbPGhNVphvnbc6b1wPQG2ry0eBKm/rZ stgg==
X-Gm-Message-State: ALoCoQlClbrEsrSxEUdQrZ1avTwCIuAWm5LZSfugDLPZA0q6DxyiSuSPzCBQN5pRp96JvtCK3SSq
MIME-Version: 1.0
X-Received: by 10.60.98.40 with SMTP id ef8mr8713965oeb.13.1391713928278; Thu, 06 Feb 2014 11:12:08 -0800 (PST)
Received: by 10.60.69.102 with HTTP; Thu, 6 Feb 2014 11:12:08 -0800 (PST)
Date: Thu, 6 Feb 2014 14:12:08 -0500
Message-ID: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
Subject: Revision to Note Well
From: Richard Barnes <rlb@ipv.sx>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e013a182253127704f1c1a661
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2014 19:12:11 -0000

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

The IESG would like to put forward a revision to the proposed new Note
Well, after some discussion both on the IETF list [1] and within the IESG.

The revised text can be found on the IESG wiki:
<http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>

The only change is the following:
OLD: "..., you must disclose that fact"
NEW: "..., you must disclose that fact, *or not participate in the
discussion*"

This is intended to reflect that BCP 79's requirements for disclosure apply
to "Any individual participating in an IETF discussion", as opposed to all
IETF participants.

If you have any further comments on this text, please reply in this thread.

Thanks,
--Richard


[1] <http://www.ietf.org/mail-archive/web/ietf/current/msg85658.html>
[2] <http://tools.ietf.org/html/bcp79#section-6.1.2>

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

<div dir=3D"ltr">The IESG would like to put forward a revision to the propo=
sed new Note Well, after some discussion both on the IETF list [1] and with=
in the IESG.<div><br></div><div>The revised text can be found on the IESG w=
iki:</div>
<div>&lt;<a href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNo=
teWellSummary">http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWel=
lSummary</a>&gt;</div><div><br></div><div>The only change is the following:=
</div>
<div>OLD: &quot;..., you must disclose that fact&quot;</div><div>NEW: &quot=
;..., you must disclose that fact, <b>or not participate in the discussion<=
/b>&quot;</div><div><br></div><div>This is intended to reflect that BCP 79&=
#39;s requirements for disclosure apply to &quot;<span style=3D"color:rgb(0=
,0,0);font-size:1em">Any individual participating in an IETF discussion&quo=
t;, as opposed to all IETF participants.</span></div>
<div><span style=3D"color:rgb(0,0,0);font-size:1em"><br></span></div><div><=
span style=3D"color:rgb(0,0,0);font-size:1em">If you have any further comme=
nts on this text, please reply in this thread.</span></div><div><span style=
=3D"color:rgb(0,0,0);font-size:1em"><br>
</span></div><div><span style=3D"color:rgb(0,0,0);font-size:1em">Thanks,</s=
pan></div><div><span style=3D"color:rgb(0,0,0);font-size:1em">--Richard</sp=
an></div><div><br></div><div><br></div><div>[1] &lt;<a href=3D"http://www.i=
etf.org/mail-archive/web/ietf/current/msg85658.html">http://www.ietf.org/ma=
il-archive/web/ietf/current/msg85658.html</a>&gt;</div>
<div>[2] &lt;<a href=3D"http://tools.ietf.org/html/bcp79#section-6.1.2">htt=
p://tools.ietf.org/html/bcp79#section-6.1.2</a>&gt;</div></div>

--089e013a182253127704f1c1a661--

From fluffy@cisco.com  Thu Feb  6 11:18:31 2014
Return-Path: <fluffy@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 036231A044C for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:18:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.036
X-Spam-Level: 
X-Spam-Status: No, score=-110.036 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.535, 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 mI2JLnRnyp7l for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:18:29 -0800 (PST)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) by ietfa.amsl.com (Postfix) with ESMTP id 20B5A1A03F5 for <ietf@ietf.org>; Thu,  6 Feb 2014 11:18:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1060; q=dns/txt; s=iport; t=1391714308; x=1392923908; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=fqjQYcOY95XNKD6Ft8Xnsv2+C0XVrp9g3iXzzdSilpc=; b=G7oSOROI/hEmWXy7Evj/WFTyPcZMuq2L+7AqQLcpWgBGjITp8kqCXC21 PlKma0oB9NtyM5AbUUMBS9sPQwtqTXxdhckd/+j3jHN/wl1OevV73hq7u T6sn9F6rkBUQNhr2ajuomVwn/wBLiTM9lsCpTPNz+vrxNd9ySZ3n8ab2i U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFAMje81KtJV2c/2dsb2JhbABZgww4V75ygQ0WdIIlAQEBAwF5BQsCAQgOODIlAgQOBQmHdAgNzQwXjikBARwzAgWDJIEUBIkRjxqBMpBvgy2BcTk
X-IronPort-AV: E=Sophos;i="4.95,795,1384300800"; d="scan'208";a="18530666"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-3.cisco.com with ESMTP; 06 Feb 2014 19:18:27 +0000
Received: from xhc-aln-x05.cisco.com (xhc-aln-x05.cisco.com [173.36.12.79]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s16JIRaf016906 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 6 Feb 2014 19:18:28 GMT
Received: from xmb-aln-x02.cisco.com ([169.254.5.180]) by xhc-aln-x05.cisco.com ([173.36.12.79]) with mapi id 14.03.0123.003; Thu, 6 Feb 2014 13:18:27 -0600
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Richard Barnes <rlb@ipv.sx>
Subject: Re: Revision to Note Well
Thread-Topic: Revision to Note Well
Thread-Index: AQHPI3A2mSAEYHHEjUKFXLi8LPfvpw==
Date: Thu, 6 Feb 2014 19:18:27 +0000
Message-ID: <EFE82A45-BF2D-48A6-ABE7-1B13CC90FE0E@cisco.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
In-Reply-To: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.20.249.164]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F3246181C766E34595D5D90CE113D902@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.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, 06 Feb 2014 19:18:31 -0000

This looks excellent and address my concern. I would be very happy with thi=
s change.=20

On Feb 6, 2014, at 12:12 PM, Richard Barnes <rlb@ipv.sx> wrote:

> The IESG would like to put forward a revision to the proposed new Note We=
ll, after some discussion both on the IETF list [1] and within the IESG.
>=20
> The revised text can be found on the IESG wiki:
> <http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>
>=20
> The only change is the following:
> OLD: "..., you must disclose that fact"
> NEW: "..., you must disclose that fact, or not participate in the discuss=
ion"
>=20
> This is intended to reflect that BCP 79's requirements for disclosure app=
ly to "Any individual participating in an IETF discussion", as opposed to a=
ll IETF participants.
>=20
> If you have any further comments on this text, please reply in this threa=
d.
>=20
> Thanks,
> --Richard
>=20
>=20
> [1] <http://www.ietf.org/mail-archive/web/ietf/current/msg85658.html>
> [2] <http://tools.ietf.org/html/bcp79#section-6.1.2>


From ned+ietf@mauve.mrochek.com  Thu Feb  6 11:29:31 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 E53BE1A03E2 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:29:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, 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 Oh-2wyBr1V6B for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:29:30 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 7E0A41A045F for <ietf@ietf.org>; Thu,  6 Feb 2014 11:29:30 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P419LCG7E8004R4R@mauve.mrochek.com> for ietf@ietf.org; Thu, 6 Feb 2014 11:24:28 -0800 (PST)
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 <01P4121FJD800000CD@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 6 Feb 2014 11:24:24 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P419LA1LWU0000CD@mauve.mrochek.com>
Date: Thu, 06 Feb 2014 11:22:17 -0800 (PST)
Subject: Re: Revision to Note Well
In-reply-to: "Your message dated Thu, 06 Feb 2014 14:12:08 -0500" <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
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, 06 Feb 2014 19:29:32 -0000

This new text doesn't fix the main problem, which is the failure to distinguish
between your/your employer's IP and third party IP. As such, it's still wrong
and needs further work.

				Ned

> The IESG would like to put forward a revision to the proposed new Note
> Well, after some discussion both on the IETF list [1] and within the IESG.

> The revised text can be found on the IESG wiki:
> <http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>

> The only change is the following:
> OLD: "..., you must disclose that fact"
> NEW: "..., you must disclose that fact, *or not participate in the
> discussion*"

> This is intended to reflect that BCP 79's requirements for disclosure apply
> to "Any individual participating in an IETF discussion", as opposed to all
> IETF participants.

> If you have any further comments on this text, please reply in this thread.

> Thanks,
> --Richard


> [1] <http://www.ietf.org/mail-archive/web/ietf/current/msg85658.html>
> [2] <http://tools.ietf.org/html/bcp79#section-6.1.2>

From christer.holmberg@ericsson.com  Thu Feb  6 11:30:29 2014
Return-Path: <christer.holmberg@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 C17D51A046A for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:30:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level: 
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, 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 S3GgvXRFel_n for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:30:27 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id DDFF91A045A for <ietf@ietf.org>; Thu,  6 Feb 2014 11:30:25 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-03-52f3e2cf9b97
Received: from ESESSHC016.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 27.7C.04853.FC2E3F25; Thu,  6 Feb 2014 20:30:23 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC016.ericsson.se ([153.88.183.66]) with mapi id 14.02.0387.000; Thu, 6 Feb 2014 20:30:23 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Richard Barnes <rlb@ipv.sx>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Revision to Note Well
Thread-Topic: Revision to Note Well
Thread-Index: AQHPI29ivWIs27wq6UWxxOdw1KoqoJqom/6K
Date: Thu, 6 Feb 2014 19:30:22 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D1608E9@ESESSMB209.ericsson.se>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
In-Reply-To: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.147]
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrPLMWRmVeSWpSXmKPExsUyM+Jvje75R5+DDDquWFk82zifxWJqn60D k8eSJT+ZPCZvnMUSwBTFZZOSmpNZllqkb5fAlbGm+QJ7wQ2WintrtRsY7zN3MXJySAiYSMxf 9JgRwhaTuHBvPVsXIxeHkMAJRok79ycxQTiLGCU6XraydjFycLAJWEh0/9MGaRARcJB48HUl O4gtLKAkMf/MCTaIuLLEgTPHWSFsI4lLr9+C2SwCKhIb5v8AW8wr4CvRNm0pWL2QQIDEpD9z wOZwCgRK7NjSBVbPCHTQ91NrmEBsZgFxiVtP5jNBHCogsWTPeagHRCVePv4HdpoE0A3TtqZB lBtIvD83nxnC1pZYtvA11FpBiZMzn7BMYBSdhWTqLCQts5C0zELSsoCRZRWjZHFqcXFuupGB Xm56bolealFmcnFxfp5eceomRmCkHNzy22gH48k99ocYpTlYlMR5r7PWBAkJpCeWpGanphak FsUXleakFh9iZOLglGpg3L5k6vVJC/TPfej8618/MTbyLkuSRE/UnM/uN9v3u27i41Z1N2yq njep5eyfQAup55nWbtGVIls1jS9t/s7Svn7B0xvzo7nK129lONj28OOGCVpl3/0DPr+SOX/J zvVu0mMHm/8e8Stjpic66nqarrl8/ugnbce40/M9Dd7ZC5i/VPtZqqxioMRSnJFoqMVcVJwI AOG7OFtiAgAA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2014 19:30:29 -0000

Hi,

>The only change is the following:
>OLD: "..., you must disclose that fact"
>NEW: "..., you must disclose that fact, or not participate in the discussi=
on"

The bullet text now says:

"=95If you are aware that any contribution (something written, said, or dis=
cussed in any IETF context) is covered by patents or patent applications, y=
ou must disclose that fact, or not participate in the discussion."

What discussion???=20

Should the text say "contribution (something written, said, or discussed in=
 any IETF context) TO A DISCUSSION is covered"

Regards,

Christer

From brian.e.carpenter@gmail.com  Thu Feb  6 11:35:15 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 8359B1A0454 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:35:15 -0800 (PST)
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 Ny4-2FbqF3dc for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:35:13 -0800 (PST)
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 356511A03F9 for <ietf@ietf.org>; Thu,  6 Feb 2014 11:35:13 -0800 (PST)
Received: by mail-pd0-f175.google.com with SMTP id w10so2119024pde.20 for <ietf@ietf.org>; Thu, 06 Feb 2014 11:35:12 -0800 (PST)
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=l6mP7i56M8Ub71Z/IZGve/Dk+SIrRp5BclzfejT1/Fk=; b=fCgHYtJ+O08qq+RdYFhqZxlRZyAAKF5aOc55eF1BW0+J4qNrXFWn5IoFtHI+VJI/Wf qcIuiZ4c0czgbk+IDzbhnj4JkUd63cQU5QIKoQ6L4H4uq8hT12+gyLkFqUZx0zfGKKdS LuvAelDmFnfjA4D0yco04at/Kc2iG/Xa8Aj+83SARy9JFTO7+a9EuXtODNPg2o/LKk6w wmQQ6Z/TWbregXbwZLQ7yKRtb/l4HzIsjVMscIXx8TOItayAHQ7WZ62dDdC8rRugqXX2 6vDTBjHUNC1FWIrqdtbJkDUwPnZ9EIABRWZKyUMTgNEx7DGvPP0YwG04xGP9HfgV7AS8 BaYQ==
X-Received: by 10.66.129.169 with SMTP id nx9mr2548828pab.130.1391715311231; Thu, 06 Feb 2014 11:35:11 -0800 (PST)
Received: from [192.168.178.23] (33.195.69.111.dynamic.snap.net.nz. [111.69.195.33]) by mx.google.com with ESMTPSA id x5sm6112784pbw.26.2014.02.06.11.35.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 06 Feb 2014 11:35:10 -0800 (PST)
Message-ID: <52F3E3F6.7010705@gmail.com>
Date: Fri, 07 Feb 2014 08:35:18 +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: Richard Barnes <rlb@ipv.sx>
Subject: Re: Revision to Note Well
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
In-Reply-To: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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, 06 Feb 2014 19:35:15 -0000

On 07/02/2014 08:12, Richard Barnes wrote:
> The IESG would like to put forward a revision to the proposed new Note
> Well, after some discussion both on the IETF list [1] and within the IESG.
> 
> The revised text can be found on the IESG wiki:
> <http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>
> 
> The only change is the following:
> OLD: "..., you must disclose that fact"
> NEW: "..., you must disclose that fact, *or not participate in the
> discussion*"
> 
> This is intended to reflect that BCP 79's requirements for disclosure apply
> to "Any individual participating in an IETF discussion", as opposed to all
> IETF participants.

"If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or
patent applications, you must disclose that fact, or not participate in the discussion."

That is still wrong, because it doesn't distinguish the case of 3rd party
disclosures, which are optional, from 1st party disclosures, which are
mandatory. This would be more accurate, by excluding the 3rd party case:

"If you are aware that any contribution (something written, said, or discussed in any IETF context) is covered by patents or
patent applications by you or your employer or sponsor, you must disclose that fact, or not participate in the discussion."

If you want to include the third party case, you'd need an extra sentence.

I still *much* prefer the old version. Summarising complex legal rules
is a dangerous game and I'm certain that a clever litigator could
exploit subtle differences between the summary and the full text.

    Brian

From ned+ietf@mauve.mrochek.com  Thu Feb  6 11:48:21 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 957421A03F3 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:48:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, 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 ob1ugS2RspAs for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:48:20 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 99CC31A03ED for <ietf@ietf.org>; Thu,  6 Feb 2014 11:48:20 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P41A9O52C0004PIN@mauve.mrochek.com> for ietf@ietf.org; Thu, 6 Feb 2014 11:43:18 -0800 (PST)
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 <01P4121FJD800000CD@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 6 Feb 2014 11:43:15 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P41A9MVYLO0000CD@mauve.mrochek.com>
Date: Thu, 06 Feb 2014 11:42:48 -0800 (PST)
Subject: Re: Revision to Note Well
In-reply-to: "Your message dated Fri, 07 Feb 2014 08:35:18 +1300" <52F3E3F6.7010705@gmail.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
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, 06 Feb 2014 19:48:21 -0000

> I still *much* prefer the old version. Summarising complex legal rules
> is a dangerous game and I'm certain that a clever litigator could
> exploit subtle differences between the summary and the full text.

+1

				Ned

From salvatore.loreto@ericsson.com  Thu Feb  6 11:56:48 2014
Return-Path: <salvatore.loreto@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 4AA551A0460 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:56:48 -0800 (PST)
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, 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 fY4ltEYNy3Ou for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:56:42 -0800 (PST)
Received: from sesbmg20.ericsson.net (sesbmg20.ericsson.net [193.180.251.56]) by ietfa.amsl.com (Postfix) with ESMTP id 968A81A045B for <ietf@ietf.org>; Thu,  6 Feb 2014 11:56:41 -0800 (PST)
X-AuditID: c1b4fb38-b7f418e000001099-0d-52f3e8f7984c
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by sesbmg20.ericsson.net (Symantec Mail Security) with SMTP id FD.3F.04249.7F8E3F25; Thu,  6 Feb 2014 20:56:39 +0100 (CET)
Received: from ESESSMB109.ericsson.se ([169.254.9.236]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0387.000; Thu, 6 Feb 2014 20:56:39 +0100
From: Salvatore Loreto <salvatore.loreto@ericsson.com>
To: Richard Barnes <rlb@ipv.sx>
Subject: Re: Revision to Note Well
Thread-Topic: Revision to Note Well
Thread-Index: AQHPI29b2GjF/+EvokKP5DJAXsnwN5qok3aA
Date: Thu, 6 Feb 2014 19:56:38 +0000
Message-ID: <8505C544-A278-4A32-BFC5-EA229B98F420@ericsson.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
In-Reply-To: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: multipart/alternative; boundary="_000_8505C544A2784A32BFC5EA229B98F420ericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrPLMWRmVeSWpSXmKPExsUyM+Jvje73F5+DDA7ftrR4tnE+i8XUPlsH Jo8lS34yeUzeOIslgCmKyyYlNSezLLVI3y6BK+ND/2m2gkfSFfs/XGdtYOyQ6GLk5JAQMJE4 dXoZK4QtJnHh3no2EFtI4AijxP23/F2MXED2YkaJqSeesYAk2ATMJJ4/3MIMYosIyEucvv4A rJlZQFni6aY5TCC2sICSRMf5C1A1yhIHzhxnhbCNJI6sfAIU5+BgEVCR+LvPAyTMK2AvcXf2 B3aIvQESk/7MAbM5BQIldmzpAmtlBLrt+6k1TBCrxCVuPZnPBHGzgMSSPeeZIWxRiZeP/0H9 oiTRuOQJ1GnJEi9nfGOC2CUocXLmE5YJjKKzkIyahaRsFpIyiLiexI2pU9ggbG2JZQtfM0PY uhIz/h2CqrGWeHTsPTuymgWMHKsYOYpTi5Ny040MNjECI+3glt8WOxgv/7U5xCjNwaIkzvvx rXOQkEB6YklqdmpqQWpRfFFpTmrxIUYmDk6pBsbuk5z9Fqwrb1/TndN1Skd4i1XVml6B3sRK hgX/dF46lCqrX3xYdsbli3lmep7v3tP5rTxT7981v7Eo21tAuHLFPA25H9sOGMhX3FD3ml17 739c0EGp3tur2E5uK+7qnpu/lenFbDWvo5M7E9e5//05Z+uyKPt60edr5UWU5+6siJURfm3s cFeJpTgj0VCLuag4EQAvFKHxggIAAA==
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, 06 Feb 2014 19:56:48 -0000

--_000_8505C544A2784A32BFC5EA229B98F420ericssoncom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

works for me

/Sal

On Feb 6, 2014, at 9:12 PM, Richard Barnes <rlb@ipv.sx<mailto:rlb@ipv.sx>> =
wrote:

The IESG would like to put forward a revision to the proposed new Note Well=
, after some discussion both on the IETF list [1] and within the IESG.

The revised text can be found on the IESG wiki:
<http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>

The only change is the following:
OLD: "..., you must disclose that fact"
NEW: "..., you must disclose that fact, or not participate in the discussio=
n"

This is intended to reflect that BCP 79's requirements for disclosure apply=
 to "Any individual participating in an IETF discussion", as opposed to all=
 IETF participants.

If you have any further comments on this text, please reply in this thread.

Thanks,
--Richard


[1] <http://www.ietf.org/mail-archive/web/ietf/current/msg85658.html>
[2] <http://tools.ietf.org/html/bcp79#section-6.1.2>


--_000_8505C544A2784A32BFC5EA229B98F420ericssoncom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <56A4DF043D326C4183293D8BD4C213CD@ericsson.com>
Content-Transfer-Encoding: quoted-printable

<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-lin=
e-break: after-white-space; ">
works for me
<div><br>
</div>
<div>/Sal</div>
<div><br>
<div>
<div>On Feb 6, 2014, at 9:12 PM, Richard Barnes &lt;<a href=3D"mailto:rlb@i=
pv.sx">rlb@ipv.sx</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div dir=3D"ltr">The IESG would like to put forward a revision to the propo=
sed new Note Well, after some discussion both on the IETF list [1] and with=
in the IESG.
<div><br>
</div>
<div>The revised text can be found on the IESG wiki:</div>
<div>&lt;<a href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNo=
teWellSummary">http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWel=
lSummary</a>&gt;</div>
<div><br>
</div>
<div>The only change is the following:</div>
<div>OLD: &quot;..., you must disclose that fact&quot;</div>
<div>NEW: &quot;..., you must disclose that fact, <b>or not participate in =
the discussion</b>&quot;</div>
<div><br>
</div>
<div>This is intended to reflect that BCP 79's requirements for disclosure =
apply to &quot;<span style=3D"font-size: 1em; ">Any individual participatin=
g in an IETF discussion&quot;, as opposed to all IETF participants.</span><=
/div>
<div><span style=3D"font-size: 1em; "><br>
</span></div>
<div><span style=3D"font-size: 1em; ">If you have any further comments on t=
his text, please reply in this thread.</span></div>
<div><span style=3D"font-size: 1em; "><br>
</span></div>
<div><span style=3D"font-size: 1em; ">Thanks,</span></div>
<div><span style=3D"font-size: 1em; ">--Richard</span></div>
<div><br>
</div>
<div><br>
</div>
<div>[1] &lt;<a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/m=
sg85658.html">http://www.ietf.org/mail-archive/web/ietf/current/msg85658.ht=
ml</a>&gt;</div>
<div>[2] &lt;<a href=3D"http://tools.ietf.org/html/bcp79#section-6.1.2">htt=
p://tools.ietf.org/html/bcp79#section-6.1.2</a>&gt;</div>
</div>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_8505C544A2784A32BFC5EA229B98F420ericssoncom_--

From dhc@dcrocker.net  Thu Feb  6 12:09: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 DE6751A0471; Thu,  6 Feb 2014 12:09:50 -0800 (PST)
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 0dnhQ9Mm7izw; Thu,  6 Feb 2014 12:09:49 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 342CA1A0458; Thu,  6 Feb 2014 12:09:49 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s16K9iCd025616 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 6 Feb 2014 12:09:48 -0800
Message-ID: <52F3EBE6.9090907@dcrocker.net>
Date: Thu, 06 Feb 2014 12:09:10 -0800
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.2.0
MIME-Version: 1.0
To: iesg <iesg@ietf.org>
Subject: Re: Revision to Note Well
X-Priority: 2 (High)
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <01P419LA1LWU0000CD@mauve.mrochek.com>
In-Reply-To: <01P419LA1LWU0000CD@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, 06 Feb 2014 12:09:48 -0800 (PST)
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, 06 Feb 2014 20:09:51 -0000

On 2/6/2014 11:22 AM, ned+ietf@mauve.mrochek.com wrote:
> This new text doesn't fix the main problem,


A number of people have have raised very specific and and very serious 
concerns with current and proposed Note Well text.

These concerns need to get direct, public, expert responses before the 
IESG imposes any further changes.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From derhoermi@gmx.net  Thu Feb  6 12:18:35 2014
Return-Path: <derhoermi@gmx.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 BED7A1A0484 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 12:18:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.435
X-Spam-Level: 
X-Spam-Status: No, score=-2.435 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 56y2izWkiVNt for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 12:18:33 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.19]) by ietfa.amsl.com (Postfix) with ESMTP id 3FB3C1A0473 for <ietf@ietf.org>; Thu,  6 Feb 2014 12:18:33 -0800 (PST)
Received: from netb.Speedport_W_700V ([91.35.11.52]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0LtmK9-1VCUXC1i0z-011Bo8 for <ietf@ietf.org>; Thu, 06 Feb 2014 21:18:31 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Richard Barnes <rlb@ipv.sx>
Subject: Re: Revision to Note Well
Date: Thu, 06 Feb 2014 21:18:34 +0100
Message-ID: <nip7f91llg6k2i2nuar43nel897sf2ms3a@hive.bjoern.hoehrmann.de>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
In-Reply-To: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:vmsHenzwTzo5mhcczuUbzmrprP9v0+VGdjnqB8HJr2Hy7YnELhD vKBENBwP2FfRNEw8PurDfoWhKm3WfFVqL+mEp4DEWnDFZ8ZB9Gnn/+0C5o8AnU1wxtHdvjz 9Ib1ULTI5TH5LwULjvfJcvgM7mTMRKRR2o+XmqddBV+vxO4rFPQbfVhSFpCBjmHXY3OVYXY iz/PeC6Bim/KzFhZsTuqQ==
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, 06 Feb 2014 20:18:36 -0000

* Richard Barnes wrote:
>The IESG would like to put forward a revision to the proposed new Note
>Well, after some discussion both on the IETF list [1] and within the IESG.
>
>The revised text can be found on the IESG wiki:
><http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>

I like http://www.ietf.org/about/note-well.html better by an order of
magnitude or so. I would suggest taking the old version and adding the
parentheticals like in "BCP 79 (on patents covering IETF documents)",
though perhaps as "(on patents and patent disclosure obligations)".

As an example,

  A participant in any IETF activity acknowledges that written, audio
  and video records of meetings may be made and may be available to 
  the public.

versus

  You understand that meetings might be recorded or broadcast (audio
  or video), photographed, and publicly archived.

The current version makes me think about whether I want to give my per-
mission, while the latter just informs me of an obvious possibility.

(As an aside, 'summary "Note Well"' does not make it clear if this is
supposed to be a replacement of the "Note Well", or a summary of it.)
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 

From mary.h.barnes@gmail.com  Thu Feb  6 12:28:03 2014
Return-Path: <mary.h.barnes@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 950691A046C for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 12:28:03 -0800 (PST)
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 MepwfliTKwaj for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 12:28:01 -0800 (PST)
Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 44A121A0462 for <ietf@ietf.org>; Thu,  6 Feb 2014 12:28:01 -0800 (PST)
Received: by mail-vc0-f182.google.com with SMTP id id10so1853714vcb.41 for <ietf@ietf.org>; Thu, 06 Feb 2014 12:28:00 -0800 (PST)
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=yY6VHSD/VazFDhRA89alGRwicMMGL2VjnEUKjHHADpk=; b=h5+jdoF6HmCiMC/J9Srm9MvThb98LrR4EfpfsLOUTC2SZEDCz0dux1sfUkKDlv9F+t j4lbn0JZpBhBWBrTcYDosDpGoXAdj+YgtnbYmQtvpnlpvdBVYciLFXoGlDJThaRJjZn1 DAFZRW5OVy3ldI2qAIQwzYL2zbTW7MbBdoa7NRRZUCUV9q0O639eT8MOIzwGSQak5kZO rrG8ufcL9VNSgcxj6Qkv26m+eVATAiEsbo+Fv0++2UL+QRDZq6ghVHWnDqBHYUMTmLZC en3aiDP8Mfdx6QAmPvZ0M46+dJBKkCccyghOSU+0kHHVE6jvWs3NkxcY7+L6HhZbH4Ea xDFw==
MIME-Version: 1.0
X-Received: by 10.220.109.1 with SMTP id h1mr7229309vcp.20.1391718479996; Thu, 06 Feb 2014 12:27:59 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Thu, 6 Feb 2014 12:27:59 -0800 (PST)
In-Reply-To: <52F3E3F6.7010705@gmail.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com>
Date: Thu, 6 Feb 2014 14:27:59 -0600
Message-ID: <CABmDk8kU8Cg6WNGCHOYVmT3n_r9icVEKgFPZamArJpqUrJ=b2A@mail.gmail.com>
Subject: Re: Revision to Note Well
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c308d6a0b36b04f1c2b581
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, 06 Feb 2014 20:28:03 -0000

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

I also do not believe that this change addresses the concerns that have
been raised.  As I said previously, I never totally understood why we
needed a new note well summary was even needed.   I believe the previous
version was more than adequate and certainly more correct.

Mary.


On Thu, Feb 6, 2014 at 1:35 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 07/02/2014 08:12, Richard Barnes wrote:
> > The IESG would like to put forward a revision to the proposed new Note
> > Well, after some discussion both on the IETF list [1] and within the
> IESG.
> >
> > The revised text can be found on the IESG wiki:
> > <http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>
> >
> > The only change is the following:
> > OLD: "..., you must disclose that fact"
> > NEW: "..., you must disclose that fact, *or not participate in the
> > discussion*"
> >
> > This is intended to reflect that BCP 79's requirements for disclosure
> apply
> > to "Any individual participating in an IETF discussion", as opposed to
> all
> > IETF participants.
>
> "If you are aware that any contribution (something written, said, or
> discussed in any IETF context) is covered by patents or
> patent applications, you must disclose that fact, or not participate in
> the discussion."
>
> That is still wrong, because it doesn't distinguish the case of 3rd party
> disclosures, which are optional, from 1st party disclosures, which are
> mandatory. This would be more accurate, by excluding the 3rd party case:
>
> "If you are aware that any contribution (something written, said, or
> discussed in any IETF context) is covered by patents or
> patent applications by you or your employer or sponsor, you must disclose
> that fact, or not participate in the discussion."
>
> If you want to include the third party case, you'd need an extra sentence.
>
> I still *much* prefer the old version. Summarising complex legal rules
> is a dangerous game and I'm certain that a clever litigator could
> exploit subtle differences between the summary and the full text.
>
>     Brian
>

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

<div dir=3D"ltr">I also do not believe that this change addresses the conce=
rns that have been raised. =A0As I said previously, I never totally underst=
ood why we needed a new note well summary was even needed. =A0 I believe th=
e previous version was more than adequate and certainly more correct.=A0<di=
v>
<br></div><div>Mary.=A0</div></div><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Thu, Feb 6, 2014 at 1:35 PM, Brian E Carpenter <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" target=3D=
"_blank">brian.e.carpenter@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"im">On 07/02/2014 08:12, Richa=
rd Barnes wrote:<br>
&gt; The IESG would like to put forward a revision to the proposed new Note=
<br>
&gt; Well, after some discussion both on the IETF list [1] and within the I=
ESG.<br>
&gt;<br>
&gt; The revised text can be found on the IESG wiki:<br>
&gt; &lt;<a href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNo=
teWellSummary" target=3D"_blank">http://trac.tools.ietf.org/group/iesg/trac=
/wiki/DraftNoteWellSummary</a>&gt;<br>
&gt;<br>
&gt; The only change is the following:<br>
&gt; OLD: &quot;..., you must disclose that fact&quot;<br>
</div>&gt; NEW: &quot;..., you must disclose that fact, *or not participate=
 in the<br>
&gt; discussion*&quot;<br>
<div class=3D"im">&gt;<br>
&gt; This is intended to reflect that BCP 79&#39;s requirements for disclos=
ure apply<br>
&gt; to &quot;Any individual participating in an IETF discussion&quot;, as =
opposed to all<br>
&gt; IETF participants.<br>
<br>
</div><div class=3D"im">&quot;If you are aware that any contribution (somet=
hing written, said, or discussed in any IETF context) is covered by patents=
 or<br>
</div>patent applications, you must disclose that fact, or not participate =
in the discussion.&quot;<br>
<br>
That is still wrong, because it doesn&#39;t distinguish the case of 3rd par=
ty<br>
disclosures, which are optional, from 1st party disclosures, which are<br>
mandatory. This would be more accurate, by excluding the 3rd party case:<br=
>
<div class=3D"im"><br>
&quot;If you are aware that any contribution (something written, said, or d=
iscussed in any IETF context) is covered by patents or<br>
</div>patent applications by you or your employer or sponsor, you must disc=
lose that fact, or not participate in the discussion.&quot;<br>
<br>
If you want to include the third party case, you&#39;d need an extra senten=
ce.<br>
<br>
I still *much* prefer the old version. Summarising complex legal rules<br>
is a dangerous game and I&#39;m certain that a clever litigator could<br>
exploit subtle differences between the summary and the full text.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0 Brian<br>
</font></span></blockquote></div><br></div>

--001a11c308d6a0b36b04f1c2b581--

From presnick@qti.qualcomm.com  Thu Feb  6 12:53:01 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 9CEDC1A04FD for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 12:53:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 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, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M37oXH0ixMJP for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 12:52:59 -0800 (PST)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id 5B8191A045C for <ietf@ietf.org>; Thu,  6 Feb 2014 12:52:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1391719978; x=1423255978; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=PwhHEabvuhwh18A09hVW/VG1PmL6rUtshqOcqMRi7wc=; b=j0BurBzE7pgU2pfJlyH+BMfOvjBESFvTzjAUaJ3JMAFzQhLGTQpFCC8V rCsRoSv15Q1vGhjo1d2yfih5MsP0RMZ+yvCyki1OGV6+FQWKp6JyPT/Ok tly9g3efvSX/9887FbM7zq1JlZyWFATINZ+eKbSA39wT0lrdsY5gHi4ld o=;
X-IronPort-AV: E=McAfee;i="5400,1158,7341"; a="59105789"
Received: from ironmsg04-l.qualcomm.com ([172.30.48.19]) by sabertooth02.qualcomm.com with ESMTP; 06 Feb 2014 12:52:58 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7341"; a="589781998"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg04-L.qualcomm.com with ESMTP/TLS/RC4-SHA; 06 Feb 2014 12:52:58 -0800
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; Thu, 6 Feb 2014 12:52:57 -0800
Message-ID: <52F3F627.4060308@qti.qualcomm.com>
Date: Thu, 6 Feb 2014 14:52:55 -0600
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: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Revision to Note Well
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com>
In-Reply-To: <52F3E3F6.7010705@gmail.com>
Content-Type: multipart/alternative; boundary="------------080308000101020906070208"
X-Originating-IP: [172.30.39.5]
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, 06 Feb 2014 20:53:01 -0000

--------------080308000101020906070208
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit

Speaking as me, not as AD (except insofar as some of this makes my life 
as an AD a pain).

On 2/6/14 1:35 PM, Brian E Carpenter wrote:
> I still*much*  prefer the old version.

Let's first separate what goes on the web site (and importantly, the 
registration page) from what gets put on a slide in the room. I have no 
quarrel with legalese appearing on the registration page; it's not 
particularly useful to the participants, but it's legal 
rear-end-covering, for whatever that's worth. It's really between you 
and your corporate attorney what to make of it.

But the old (currently posted) version on a slide in the room is, 
pragmatically speaking, content-free and useless to the IETF and to the 
participants. It gives no notice whatsoever that what is contained in 
the referenced documents has anything to do with intellectual property. 
And really, we know that almost nobody reads the Note Well in the room, 
and we have ample evidence (in the form of late disclosures and bogus 
disclosures) that many people don't know what it means. Unlike on the 
registration page, the point of making the statement in the room is to 
avoid late surprises for the WG in their work.

So, I really do not find the current Note Well useful on a slide in the 
room at all.

But I do see a point in having the chair say (or display) in the room, 
"Just in case you didn't actually read what is posted on the web page[1] 
that you acknowledged when you registered, please note: You've got IPR 
disclosure responsibilities if you participate in this discussion at all 
(including writing, speaking, singing or otherwise). If you or your 
employer has IPR on this stuff, get with it!"

If we're not going to have simple text available in the room, let's at 
least stop with the charade that posting the Note Well is meaningful, 
and the chairs and shepherds and the IESG will simply have to continue 
to deal with the regular stream of late disclosures.

pr

[1] "...just like you ignore every other EULA that you click through on 
the Interwebs..."

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


--------------080308000101020906070208
Content-Type: text/html; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Speaking as me, not as AD (except insofar as some of this makes my life
as an AD a pain).<br>
<br>
On 2/6/14 1:35 PM, Brian E Carpenter wrote:
<blockquote cite="mid:52F3E3F6.7010705@gmail.com" type="cite">
  <pre wrap="">I still <b class="moz-txt-star"><span class="moz-txt-tag">*</span>much<span
 class="moz-txt-tag">*</span></b> prefer the old version.</pre>
</blockquote>
<br>
Let's first separate what goes on the web site (and importantly, the
registration page) from what gets put on a slide in the room. I have no
quarrel with legalese appearing on the registration page; it's not
particularly useful to the participants, but it's legal
rear-end-covering, for whatever that's worth. It's really between you
and your corporate attorney what to make of it.<br>
<br>
But the old (currently posted) version on a slide in the room is,
pragmatically speaking, content-free and useless to the IETF and to the
participants. It gives no notice whatsoever that what is contained in
the referenced documents has anything to do with intellectual property.
And really, we know that almost nobody reads the Note Well in the room,
and we have ample evidence (in the form of late disclosures and bogus
disclosures) that many people don't know what it means. Unlike on the
registration page, the point of making the statement in the room is to
avoid late surprises for the WG in their work.<br>
<br>
So, I really do not find the current Note Well useful on a slide in the
room at all.<br>
<br>
But I do see a point in having the chair say (or display) in the room,
"Just in case you didn't actually read what is posted on the web
page[1] that you acknowledged when you registered, please note: You've
got IPR disclosure responsibilities if you participate in this
discussion at all (including writing, speaking, singing or otherwise).
If you or your employer has IPR on this stuff, get with it!"<br>
<br>
If we're not going to have simple text available in the room, let's at
least stop with the charade that posting the Note Well is meaningful,
and the chairs and shepherds and the IESG will simply have to continue
to deal with the regular stream of late disclosures.<br>
<br>
pr<br>
<br>
[1] "...just like you ignore every other EULA that you click through on
the Interwebs..."
<pre class="moz-signature" cols="72">-- 
Pete Resnick <a class="moz-txt-link-rfc2396E" href="http://www.qualcomm.com/~presnick/">&lt;http://www.qualcomm.com/~presnick/&gt;</a>
Qualcomm Technologies, Inc. - +1 (858)651-4478</pre>
</body>
</html>

--------------080308000101020906070208--

From paul.hoffman@vpnc.org  Thu Feb  6 13:04:27 2014
Return-Path: <paul.hoffman@vpnc.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 90F031A01C0 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 13:04:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VvpSN80eZ-rZ for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 13:04:26 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 4A6D81A020C for <ietf@ietf.org>; Thu,  6 Feb 2014 13:04:26 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id s16KiKu2086115 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 6 Feb 2014 13:44:21 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Revision to Note Well
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <52F3F627.4060308@qti.qualcomm.com>
Date: Thu, 6 Feb 2014 13:04:22 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <8BB33B5F-4856-4412-B92A-5E3E916C12EF@vpnc.org>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <52F3F627.4060308@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.1827)
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, 06 Feb 2014 21:04:27 -0000

On Feb 6, 2014, at 12:52 PM, Pete Resnick <presnick@qti.qualcomm.com> =
wrote:

> Let's first separate what goes on the web site (and importantly, the =
registration page) from what gets put on a slide in the room.

That's good; that's now what was sent in this thread.

> I have no quarrel with legalese appearing on the registration page; =
it's not particularly useful to the participants, but it's legal =
rear-end-covering, for whatever that's worth. It's really between you =
and your corporate attorney what to make of it.

No, it's more than that. It is also a way of saying "here's what we =
really mean".

> But the old (currently posted) version on a slide in the room is, =
pragmatically speaking, content-free and useless to the IETF and to the =
participants. It gives no notice whatsoever that what is contained in =
the referenced documents has anything to do with intellectual property. =
And really, we know that almost nobody reads the Note Well in the room, =
and we have ample evidence (in the form of late disclosures and bogus =
disclosures) that many people don't know what it means.

All true. So instead of making the engineering mistake of "let's =
optimize and everything will be fine", maybe make the different =
engineering mistake of "let's use a level of indirection and assume it =
will get dereferenced". That is, the note in the room is "you already =
agreed to the Note Well when you registered; it said important things =
for this meeting".

> Unlike on the registration page, the point of making the statement in =
the room is to avoid late surprises for the WG in their work.

That is one of the main points for both the registration and in the =
room.

> So, I really do not find the current Note Well useful on a slide in =
the room at all.

Fully agree. Replacing it with a worse one is not the answer.

> But I do see a point in having the chair say (or display) in the room, =
"Just in case you didn't actually read what is posted on the web page[1] =
that you acknowledged when you registered, please note: You've got IPR =
disclosure responsibilities if you participate in this discussion at all =
(including writing, speaking, singing or otherwise). If you or your =
employer has IPR on this stuff, get with it!"

Or: "Just in case you didn't actually read what is posted on the web =
page[1] that you acknowledged when you registered, please note: You've =
got IPR disclosure responsibilities if you participate in this =
discussion at all (including writing, speaking, singing or otherwise). =
It is in everyone's best interest, including yours and your companies, =
if everyone has read it." Your last sentence above is legal advice from =
a chair who is likely to be below average among chairs at communication =
skills and below average among chairs at understanding IETF procedures.

> If we're not going to have simple text available in the room, let's at =
least stop with the charade that posting the Note Well is meaningful, =
and the chairs and shepherds and the IESG will simply have to continue =
to deal with the regular stream of late disclosures.

Works for me.

--Paul Hoffman=

From ajs@anvilwalrusden.com  Thu Feb  6 13:06:58 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 EE4891A0133 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 13:06:57 -0800 (PST)
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 Fhh9n17C8ri3 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 13:06:57 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id E9D8F1A012B for <ietf@ietf.org>; Thu,  6 Feb 2014 13:06:56 -0800 (PST)
Received: from mx1.yitter.info (nat-08-mht.dyndns.com [216.146.45.247]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id B4B058A031 for <ietf@ietf.org>; Thu,  6 Feb 2014 21:06:54 +0000 (UTC)
Date: Thu, 6 Feb 2014 16:06:49 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Revision to Note Well
Message-ID: <20140206210648.GI22360@mx1.yitter.info>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <52F3F627.4060308@qti.qualcomm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <52F3F627.4060308@qti.qualcomm.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Feb 2014 21:06:58 -0000

On Thu, Feb 06, 2014 at 02:52:55PM -0600, Pete Resnick wrote:
> But I do see a point in having the chair say (or display) in the
> room, "Just in case you didn't actually read what is posted on the
> web page[1] that you acknowledged when you registered, please note:
> You've got IPR disclosure responsibilities if you participate in
> this discussion at all (including writing, speaking, singing or
> otherwise). If you or your employer has IPR on this stuff, get with
> it!"

So use _that_.  The complaint that several people seemed to have about
the new proposal was that it tried to summarize, and did so badly.
The above text doesn't do that. 

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com

From gtw@gtwassociates.com  Thu Feb  6 13:44:13 2014
Return-Path: <gtw@gtwassociates.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8BE71A03C4 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 13:44:13 -0800 (PST)
X-Quarantine-ID: <vxkyQAphayiJ>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam-Report: ...that system for details.\n \n Content previ[...]
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, HTML_MESSAGE=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vxkyQAphayiJ for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 13:44:11 -0800 (PST)
Received: from s6.mail.rcig.net (s6.mail.rcig.net [216.87.38.206]) by ietfa.amsl.com (Postfix) with ESMTP id 8A9E11A015B for <ietf@ietf.org>; Thu,  6 Feb 2014 13:44:11 -0800 (PST)
Received: from pool-108-28-107-161.washdc.fios.verizon.net ([108.28.107.161]:55130 helo=GTWPC) by s6.mail.rcig.net with esmtpa (Exim 4.72) (envelope-from <gtw@gtwassociates.com>) id 1WBWjq-0002XT-68; Thu, 06 Feb 2014 15:44:10 -0600
Message-ID: <D7E05CE517FE4296B0DA7CE16195D55E@GTWPC>
From: "GTW" <gtw@gtwassociates.com>
To: "Mary Barnes" <mary.h.barnes@gmail.com>, "Brian E Carpenter" <brian.e.carpenter@gmail.com>, <ietf@ietf.org>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <CABmDk8kU8Cg6WNGCHOYVmT3n_r9icVEKgFPZamArJpqUrJ=b2A@mail.gmail.com>
In-Reply-To: <CABmDk8kU8Cg6WNGCHOYVmT3n_r9icVEKgFPZamArJpqUrJ=b2A@mail.gmail.com>
Subject: Re: Revision to Note Well
Date: Thu, 6 Feb 2014 16:43:56 -0500
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07F1_01CF235A.A076E910"
X-Priority: 3
X-MSMail-Priority: Normal
Importance: Normal
X-Mailer: Microsoft Windows Live Mail 16.4.3508.205
X-MimeOLE: Produced By Microsoft MimeOLE V16.4.3508.205
X-ACL-Warn: X-The email account used to send this email was: gtw@gtwassociates.com
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: GTW <gtw@gtwassociates.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, 06 Feb 2014 21:44:14 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_07F1_01CF235A.A076E910
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

I agree with those who have stated the problem with the proposed text =
such as expressed below.

Mary has asked a good question that I tried to ask before:  What is the =
problem we are striving to solve?

Is IETF experiencing issues of non-disclosure of IP that our rules =
indicate should have been disclosed?=20

If so it would be helpful to better understand any such instances in =
order that we can propose responsive solutions.

My experience is that the vast majority of current =
=E2=80=9Cproblems=E2=80=9D related to IP in standards has to do with =
disagreements over meaning of license assurances made as a part of =
disclosure.  I am not aware of current problems about =
=E2=80=9Cnon-disclosure=E2=80=9D

George T. Willingmyre, P.E.
President GTW Associates

From: Mary Barnes=20
Sent: Thursday, February 06, 2014 3:27 PM
To: Brian E Carpenter=20
Cc: ietf@ietf.org=20
Subject: Re: Revision to Note Well

I also do not believe that this change addresses the concerns that have =
been raised.  As I said previously, I never totally understood why we =
needed a new note well summary was even needed.   I believe the previous =
version was more than adequate and certainly more correct. =20

Mary.=20



On Thu, Feb 6, 2014 at 1:35 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

  On 07/02/2014 08:12, Richard Barnes wrote:
  > The IESG would like to put forward a revision to the proposed new =
Note
  > Well, after some discussion both on the IETF list [1] and within the =
IESG.
  >
  > The revised text can be found on the IESG wiki:
  > =
<http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>
  >
  > The only change is the following:
  > OLD: "..., you must disclose that fact"

  > NEW: "..., you must disclose that fact, *or not participate in the
  > discussion*"

  >
  > This is intended to reflect that BCP 79's requirements for =
disclosure apply
  > to "Any individual participating in an IETF discussion", as opposed =
to all
  > IETF participants.


  "If you are aware that any contribution (something written, said, or =
discussed in any IETF context) is covered by patents or

  patent applications, you must disclose that fact, or not participate =
in the discussion."

  That is still wrong, because it doesn't distinguish the case of 3rd =
party
  disclosures, which are optional, from 1st party disclosures, which are
  mandatory. This would be more accurate, by excluding the 3rd party =
case:


  "If you are aware that any contribution (something written, said, or =
discussed in any IETF context) is covered by patents or

  patent applications by you or your employer or sponsor, you must =
disclose that fact, or not participate in the discussion."

  If you want to include the third party case, you'd need an extra =
sentence.

  I still *much* prefer the old version. Summarising complex legal rules
  is a dangerous game and I'm certain that a clever litigator could
  exploit subtle differences between the summary and the full text.

      Brian


------=_NextPart_000_07F1_01CF235A.A076E910
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>I agree with those who have stated the problem with the proposed =
text such=20
as expressed below.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Mary has asked a good question that I tried to ask before:&nbsp; =
What is=20
the problem we are striving to solve?</DIV>
<DIV>&nbsp;</DIV>
<DIV>Is IETF experiencing issues of non-disclosure of IP that our rules =
indicate=20
should have been disclosed? </DIV>
<DIV>&nbsp;</DIV>
<DIV>If so it would be helpful to better understand any such instances =
in order=20
that we can propose responsive solutions.</DIV>
<DIV>&nbsp;</DIV>
<DIV>My experience is that the vast majority of current =
=E2=80=9Cproblems=E2=80=9D related to IP=20
in standards has to do with disagreements over meaning of license =
assurances=20
made as a part of disclosure.&nbsp; I am not aware of current problems =
about=20
=E2=80=9Cnon-disclosure=E2=80=9D</DIV>
<DIV>&nbsp;</DIV>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: =
#000000">George T.=20
Willingmyre, P.E.<BR>President GTW Associates</DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV style=3D"FONT: 10pt tahoma">
<DIV>&nbsp;</DIV>
<DIV style=3D"BACKGROUND: #f5f5f5">
<DIV style=3D"font-color: black"><B>From:</B> <A =
title=3Dmary.h.barnes@gmail.com=20
href=3D"mailto:mary.h.barnes@gmail.com">Mary Barnes</A> </DIV>
<DIV><B>Sent:</B> Thursday, February 06, 2014 3:27 PM</DIV>
<DIV><B>To:</B> <A title=3Dbrian.e.carpenter@gmail.com=20
href=3D"mailto:brian.e.carpenter@gmail.com">Brian E Carpenter</A> </DIV>
<DIV><B>Cc:</B> <A title=3Dietf@ietf.org=20
href=3D"mailto:ietf@ietf.org">ietf@ietf.org</A> </DIV>
<DIV><B>Subject:</B> Re: Revision to Note Well</DIV></DIV></DIV>
<DIV>&nbsp;</DIV></DIV>
<DIV=20
style=3D'FONT-SIZE: small; TEXT-DECORATION: none; FONT-FAMILY: =
"Calibri"; FONT-WEIGHT: normal; COLOR: #000000; FONT-STYLE: normal; =
DISPLAY: inline'>
<DIV dir=3Dltr>I also do not believe that this change addresses the =
concerns that=20
have been raised.&nbsp; As I said previously, I never totally understood =
why we=20
needed a new note well summary was even needed.&nbsp;&nbsp; I believe =
the=20
previous version was more than adequate and certainly more =
correct.&nbsp;=20
<DIV>&nbsp;</DIV>
<DIV>Mary. </DIV></DIV>
<DIV class=3Dgmail_extra><BR><BR>
<DIV class=3Dgmail_quote>On Thu, Feb 6, 2014 at 1:35 PM, Brian E =
Carpenter <SPAN=20
dir=3Dltr>&lt;<A href=3D"mailto:brian.e.carpenter@gmail.com"=20
target=3D_blank>brian.e.carpenter@gmail.com</A>&gt;</SPAN> wrote:<BR>
<BLOCKQUOTE class=3Dgmail_quote=20
style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc =
1px solid">
  <DIV class=3Dim>On 07/02/2014 08:12, Richard Barnes wrote:<BR>&gt; The =
IESG=20
  would like to put forward a revision to the proposed new Note<BR>&gt; =
Well,=20
  after some discussion both on the IETF list [1] and within the=20
  IESG.<BR>&gt;<BR>&gt; The revised text can be found on the IESG =
wiki:<BR>&gt;=20
  &lt;<A=20
  =
href=3D"http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSumm=
ary"=20
  =
target=3D_blank>http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNote=
WellSummary</A>&gt;<BR>&gt;<BR>&gt;=20
  The only change is the following:<BR>&gt; OLD: "..., you must disclose =
that=20
  fact"<BR></DIV>&gt; NEW: "..., you must disclose that fact, *or not=20
  participate in the<BR>&gt; discussion*"<BR>
  <DIV class=3Dim>&gt;<BR>&gt; This is intended to reflect that BCP 79's =

  requirements for disclosure apply<BR>&gt; to "Any individual =
participating in=20
  an IETF discussion", as opposed to all<BR>&gt; IETF=20
participants.<BR><BR></DIV>
  <DIV class=3Dim>"If you are aware that any contribution (something =
written,=20
  said, or discussed in any IETF context) is covered by patents=20
  or<BR></DIV>patent applications, you must disclose that fact, or not=20
  participate in the discussion."<BR><BR>That is still wrong, because it =
doesn't=20
  distinguish the case of 3rd party<BR>disclosures, which are optional, =
from 1st=20
  party disclosures, which are<BR>mandatory. This would be more =
accurate, by=20
  excluding the 3rd party case:<BR>
  <DIV class=3Dim><BR>"If you are aware that any contribution (something =
written,=20
  said, or discussed in any IETF context) is covered by patents=20
  or<BR></DIV>patent applications by you or your employer or sponsor, =
you must=20
  disclose that fact, or not participate in the discussion."<BR><BR>If =
you want=20
  to include the third party case, you'd need an extra =
sentence.<BR><BR>I still=20
  *much* prefer the old version. Summarising complex legal rules<BR>is a =

  dangerous game and I'm certain that a clever litigator =
could<BR>exploit subtle=20
  differences between the summary and the full text.<BR><SPAN =
class=3DHOEnZb><FONT=20
  color=3D#888888><BR>&nbsp;&nbsp;&nbsp; =
Brian<BR></FONT></SPAN></BLOCKQUOTE></DIV>
<DIV>&nbsp;</DIV></DIV></DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_07F1_01CF235A.A076E910--


From ned+ietf@mauve.mrochek.com  Thu Feb  6 14:04:33 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 635D91A045F for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 14:04:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.535, 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 BABaik1LdmNP for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 14:04:31 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id DF5981A0453 for <ietf@ietf.org>; Thu,  6 Feb 2014 14:04:30 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P41F0I55KG004PQU@mauve.mrochek.com> for ietf@ietf.org; Thu, 6 Feb 2014 13:59:28 -0800 (PST)
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 <01P4121FJD800000CD@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Thu, 6 Feb 2014 13:59:25 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P41F0GTO540000CD@mauve.mrochek.com>
Date: Thu, 06 Feb 2014 13:52:44 -0800 (PST)
Subject: Re: Revision to Note Well
In-reply-to: "Your message dated Thu, 06 Feb 2014 14:52:55 -0600" <52F3F627.4060308@qti.qualcomm.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <52F3F627.4060308@qti.qualcomm.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
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, 06 Feb 2014 22:04:33 -0000

> But I do see a point in having the chair say (or display) in the room,
> "Just in case you didn't actually read what is posted on the web page[1]
> that you acknowledged when you registered, please note: You've got IPR
> disclosure responsibilities if you participate in this discussion at all
> (including writing, speaking, singing or otherwise). If you or your
> employer has IPR on this stuff, get with it!"

Then why not use this text or something equivalent to it? As opposed to what
started this discussion, or the update the IESG has now proposed that fails to
address the issues people have raised?

The fact that you can write this demonstrates it is possible to come up with
something that is both accurate and meets your additional criteria of being
simple and direct.

> If we're not going to have simple text available in the room, let's at
> least stop with the charade that posting the Note Well is meaningful,
> and the chairs and shepherds and the IESG will simply have to continue
> to deal with the regular stream of late disclosures.

... and this is nothing but a strawman. I strongly doubt anyone objecting here
is opposed to "simple" text as long as said text doesn't misstate what our IP
rules are.

				Ned

From warren@kumari.net  Thu Feb  6 17:11:09 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 8ABDF1A0596 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 17:11:09 -0800 (PST)
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 uBr7kTyOUx9S for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 17:11:07 -0800 (PST)
Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) by ietfa.amsl.com (Postfix) with ESMTP id 5A14C1A0594 for <ietf@ietf.org>; Thu,  6 Feb 2014 17:11:07 -0800 (PST)
Received: by mail-wg0-f53.google.com with SMTP id y10so1860389wgg.32 for <ietf@ietf.org>; Thu, 06 Feb 2014 17:11:05 -0800 (PST)
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=7+L+hTZ+FFFCDQMrXKisem6uauyFtncG2ua9YMV/AcQ=; b=AGMbxl826UWNTdRJaDAAaQ9x/8bRxsXeC4BfZy3/+SnU36yRbp0C0G/iDP6e+sNAUE Sp0FA3+s9kEkAV8FvaVWKKCCEXUmfnU1CpwzQlN5WZK4t1gvOl8x3hxx0XJrNIvwq81/ QrDUH9+IVRCaVFFL/4PSyY3LUnlUYUlxpgxh5ZXgGQUsW3zBSIcIfmmBTQqSTIxtTIL+ PBLlz27l8mwt9+BpzyKbVzG4yPixmUAJcSL2mLQvuhzuNK37+vokENV534zCETUPTJa+ mRoAJUxMVhEzViOAGNf77nWChg3ljxPlyyHdKf6/e32Xmgzii1O36fRmpvZg7TmhfuVB DGIQ==
X-Gm-Message-State: ALoCoQmE/KIssgSWrgnRyzvdFZzeUDDf5Q1O+zDtZMhxRNti5CkuMWa13WKaPhLEOLF2r/4KEo6G
MIME-Version: 1.0
X-Received: by 10.180.77.74 with SMTP id q10mr1574829wiw.39.1391735465623; Thu, 06 Feb 2014 17:11:05 -0800 (PST)
Received: by 10.194.54.167 with HTTP; Thu, 6 Feb 2014 17:11:05 -0800 (PST)
X-Originating-IP: [98.244.98.35]
In-Reply-To: <01P41F0GTO540000CD@mauve.mrochek.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <52F3F627.4060308@qti.qualcomm.com> <01P41F0GTO540000CD@mauve.mrochek.com>
Date: Thu, 6 Feb 2014 20:11:05 -0500
Message-ID: <CAHw9_i+BVYNnDJJVVLhN+AeQPVvJCKts=xYHmWgcBs7uKiTF+A@mail.gmail.com>
Subject: Re: Revision to Note Well
From: Warren Kumari <warren@kumari.net>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Content-Type: multipart/alternative; boundary=f46d043bdf6a0cda8804f1c6aa7f
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: Fri, 07 Feb 2014 01:11:09 -0000

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

Oh gods, I was desperately trying to stay out of this conversation...

Seeing as I'm still unclear on what the actual *problem* is, this may or
may not be a reasonable suggestion.

I liked the old Note Well, but I get that not everyone reads it when it is
flashed up on a slide. I also get that the summarized versions miss some
subtleties / edge cases...

So, how about we simply present *both*.
"Here is an incomplete summary of our IPR stuff, but it should give you an
overview. <click> This is the longer, more detailed and correct version. It
is also posted online and you agreed to it when signing up. IANAL. If you
have any concerns / don't understand what this says, go talk to *your*
lawyer. <click> Now, agenda bashing..."
I just timed this - takes < 15 seconds to say (or <4 if you are EKR ;-)).

W

On Thursday, February 6, 2014, <ned+ietf@mauve.mrochek.com> wrote:

> But I do see a point in having the chair say (or display) in the room,
>> "Just in case you didn't actually read what is posted on the web page[1]
>> that you acknowledged when you registered, please note: You've got IPR
>> disclosure responsibilities if you participate in this discussion at all
>> (including writing, speaking, singing or otherwise). If you or your
>> employer has IPR on this stuff, get with it!"
>>
>
> Then why not use this text or something equivalent to it? As opposed to
> what
> started this discussion, or the update the IESG has now proposed that
> fails to
> address the issues people have raised?
>
> The fact that you can write this demonstrates it is possible to come up
> with
> something that is both accurate and meets your additional criteria of being
> simple and direct.
>
>  If we're not going to have simple text available in the room, let's at
>> least stop with the charade that posting the Note Well is meaningful,
>> and the chairs and shepherds and the IESG will simply have to continue
>> to deal with the regular stream of late disclosures.
>>
>
> ... and this is nothing but a strawman. I strongly doubt anyone objecting
> here
> is opposed to "simple" text as long as said text doesn't misstate what our
> IP
> rules are.
>
>                                 Ned
>

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

Oh gods, I was desperately trying to stay out of this conversation...<div><=
br></div><div>Seeing as I&#39;m still unclear on what the actual *problem* =
is, this may or may not be a reasonable suggestion.</div><div><br></div>
<div>I liked the old Note Well, but I get that not everyone reads it when i=
t is flashed up on a slide. I also get that the summarized versions miss so=
me subtleties / edge cases...</div><div><br></div><div>So, how about we sim=
ply present *both*.</div>
<div>&quot;Here is an incomplete summary of our IPR stuff, but it should gi=
ve you an overview. &lt;click&gt; This is the longer, more detailed and cor=
rect version. It is also posted online and you agreed to it when signing up=
. IANAL. If you have any concerns / don&#39;t understand what this says, go=
 talk to *your* lawyer. &lt;click&gt; Now, agenda bashing...&quot;</div>
<div>I just timed this - takes &lt; 15 seconds to say (or &lt;4 if you are =
EKR ;-)).=A0</div><div><br></div><div>W<span></span><br><br>On Thursday, Fe=
bruary 6, 2014,  &lt;<a href=3D"mailto:ned%2Bietf@mauve.mrochek.com">ned+ie=
tf@mauve.mrochek.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But I do see a point in having the chair say (or display) in the room,<br>
&quot;Just in case you didn&#39;t actually read what is posted on the web p=
age[1]<br>
that you acknowledged when you registered, please note: You&#39;ve got IPR<=
br>
disclosure responsibilities if you participate in this discussion at all<br=
>
(including writing, speaking, singing or otherwise). If you or your<br>
employer has IPR on this stuff, get with it!&quot;<br>
</blockquote>
<br>
Then why not use this text or something equivalent to it? As opposed to wha=
t<br>
started this discussion, or the update the IESG has now proposed that fails=
 to<br>
address the issues people have raised?<br>
<br>
The fact that you can write this demonstrates it is possible to come up wit=
h<br>
something that is both accurate and meets your additional criteria of being=
<br>
simple and direct.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If we&#39;re not going to have simple text available in the room, let&#39;s=
 at<br>
least stop with the charade that posting the Note Well is meaningful,<br>
and the chairs and shepherds and the IESG will simply have to continue<br>
to deal with the regular stream of late disclosures.<br>
</blockquote>
<br>
... and this is nothing but a strawman. I strongly doubt anyone objecting h=
ere<br>
is opposed to &quot;simple&quot; text as long as said text doesn&#39;t miss=
tate what our IP<br>
rules are.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ned<br>
</blockquote></div>

--f46d043bdf6a0cda8804f1c6aa7f--

From ggm@algebras.org  Thu Feb  6 17:20:04 2014
Return-Path: <ggm@algebras.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 CDBD31A058E for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 17:20:04 -0800 (PST)
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 NBhtNaREfQDd for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 17:20:02 -0800 (PST)
Received: from mail-pb0-f42.google.com (mail-pb0-f42.google.com [209.85.160.42]) by ietfa.amsl.com (Postfix) with ESMTP id 64A831A0585 for <ietf@ietf.org>; Thu,  6 Feb 2014 17:20:02 -0800 (PST)
Received: by mail-pb0-f42.google.com with SMTP id jt11so2541287pbb.29 for <ietf@ietf.org>; Thu, 06 Feb 2014 17:20:01 -0800 (PST)
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=s5zSUhg7faA/GnJLSP+xZ8CzikI9LFLkS95YNuIrH5s=; b=F1d/IWKRmdlbsICexHNu4MHB/a5SnNlyVm8MexICSj9n2BBL+AktXxqrYAFJ1BUPVh NWKFbg4Pr0aCElSClm3igvg0k+FGuKb5qYVbLUX0cbWrSKenWgs38y38JQkqer34dIRY KOG/2ks2OMxmgz22F+W/nmkMTFScOQglhkJfF1WuzeIl7bPpJyv7KygNT4Yj+/E5WUXM GhbEOfx26oe1587fLuF39gNvY0iPb7ZkWVP74uQ45cNLiA4HZf2ai+22Y4MBMOFHysHw RZGGs/++IyA6/3e7MFpSVj6d1gjsVCHSvKIQaL1iBGAzubD8X0C67YqlieFktpnYFUY1 EAUw==
X-Gm-Message-State: ALoCoQn7VDoid1xCQlkiryO6CWiZQmFEBWfFnQiQNLK4qbzJ0MDsp0ssqUrRXm0Le2DVi+J0SHZx
MIME-Version: 1.0
X-Received: by 10.66.176.143 with SMTP id ci15mr4272656pac.35.1391736001284; Thu, 06 Feb 2014 17:20:01 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Thu, 6 Feb 2014 17:20:01 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:1c08:5396:33b6:f78b]
In-Reply-To: <CAHw9_i+BVYNnDJJVVLhN+AeQPVvJCKts=xYHmWgcBs7uKiTF+A@mail.gmail.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <52F3F627.4060308@qti.qualcomm.com> <01P41F0GTO540000CD@mauve.mrochek.com> <CAHw9_i+BVYNnDJJVVLhN+AeQPVvJCKts=xYHmWgcBs7uKiTF+A@mail.gmail.com>
Date: Fri, 7 Feb 2014 11:20:01 +1000
Message-ID: <CAKr6gn2x2W0dUc1Z0gdrOEDTQ2W0NEc-dS_WL+YDQb5=b7oyuw@mail.gmail.com>
Subject: Re: Revision to Note Well
From: George Michaelson <ggm@algebras.org>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=047d7bd75160fa62c804f1c6c9e5
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, 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: Fri, 07 Feb 2014 01:20:05 -0000

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

+1. formalisms have to be done for legal reasons. the actual information is
what we already do, plus "read the detals" warnings. thats one extra slide,
maybe one extra line on the current one slide teaser.



On Fri, Feb 7, 2014 at 11:11 AM, Warren Kumari <warren@kumari.net> wrote:

> Oh gods, I was desperately trying to stay out of this conversation...
>
> Seeing as I'm still unclear on what the actual *problem* is, this may or
> may not be a reasonable suggestion.
>
> I liked the old Note Well, but I get that not everyone reads it when it is
> flashed up on a slide. I also get that the summarized versions miss some
> subtleties / edge cases...
>
> So, how about we simply present *both*.
> "Here is an incomplete summary of our IPR stuff, but it should give you an
> overview. <click> This is the longer, more detailed and correct version. It
> is also posted online and you agreed to it when signing up. IANAL. If you
> have any concerns / don't understand what this says, go talk to *your*
> lawyer. <click> Now, agenda bashing..."
> I just timed this - takes < 15 seconds to say (or <4 if you are EKR ;-)).
>
> W
>
>
> On Thursday, February 6, 2014, <ned+ietf@mauve.mrochek.com> wrote:
>
>> But I do see a point in having the chair say (or display) in the room,
>>> "Just in case you didn't actually read what is posted on the web page[1]
>>> that you acknowledged when you registered, please note: You've got IPR
>>> disclosure responsibilities if you participate in this discussion at all
>>> (including writing, speaking, singing or otherwise). If you or your
>>> employer has IPR on this stuff, get with it!"
>>>
>>
>> Then why not use this text or something equivalent to it? As opposed to
>> what
>> started this discussion, or the update the IESG has now proposed that
>> fails to
>> address the issues people have raised?
>>
>> The fact that you can write this demonstrates it is possible to come up
>> with
>> something that is both accurate and meets your additional criteria of
>> being
>> simple and direct.
>>
>>  If we're not going to have simple text available in the room, let's at
>>> least stop with the charade that posting the Note Well is meaningful,
>>> and the chairs and shepherds and the IESG will simply have to continue
>>> to deal with the regular stream of late disclosures.
>>>
>>
>> ... and this is nothing but a strawman. I strongly doubt anyone objecting
>> here
>> is opposed to "simple" text as long as said text doesn't misstate what
>> our IP
>> rules are.
>>
>>                                 Ned
>>
>

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

<div dir=3D"ltr">+1. formalisms have to be done for legal reasons. the actu=
al information is what we already do, plus &quot;read the detals&quot; warn=
ings. thats one extra slide, maybe one extra line on the current one slide =
teaser.<div>
<br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quot=
e">On Fri, Feb 7, 2014 at 11:11 AM, Warren Kumari <span dir=3D"ltr">&lt;<a =
href=3D"mailto:warren@kumari.net" target=3D"_blank">warren@kumari.net</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">Oh gods, I was desperately trying to stay ou=
t of this conversation...<div><br></div><div>Seeing as I&#39;m still unclea=
r on what the actual *problem* is, this may or may not be a reasonable sugg=
estion.</div>
<div><br></div>
<div>I liked the old Note Well, but I get that not everyone reads it when i=
t is flashed up on a slide. I also get that the summarized versions miss so=
me subtleties / edge cases...</div><div><br></div><div>So, how about we sim=
ply present *both*.</div>

<div>&quot;Here is an incomplete summary of our IPR stuff, but it should gi=
ve you an overview. &lt;click&gt; This is the longer, more detailed and cor=
rect version. It is also posted online and you agreed to it when signing up=
. IANAL. If you have any concerns / don&#39;t understand what this says, go=
 talk to *your* lawyer. &lt;click&gt; Now, agenda bashing...&quot;</div>

<div>I just timed this - takes &lt; 15 seconds to say (or &lt;4 if you are =
EKR ;-)).=A0</div><span class=3D"HOEnZb"><font color=3D"#888888"><div><br><=
/div></font></span><div><span class=3D"HOEnZb"><font color=3D"#888888">W</f=
ont></span><div>
<div class=3D"h5"><span></span><br><br>On Thursday, February 6, 2014,  &lt;=
<a href=3D"mailto:ned%2Bietf@mauve.mrochek.com" target=3D"_blank">ned+ietf@=
mauve.mrochek.com</a>&gt; wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But I do see a point in having the chair say (or display) in the room,<br>
&quot;Just in case you didn&#39;t actually read what is posted on the web p=
age[1]<br>
that you acknowledged when you registered, please note: You&#39;ve got IPR<=
br>
disclosure responsibilities if you participate in this discussion at all<br=
>
(including writing, speaking, singing or otherwise). If you or your<br>
employer has IPR on this stuff, get with it!&quot;<br>
</blockquote>
<br>
Then why not use this text or something equivalent to it? As opposed to wha=
t<br>
started this discussion, or the update the IESG has now proposed that fails=
 to<br>
address the issues people have raised?<br>
<br>
The fact that you can write this demonstrates it is possible to come up wit=
h<br>
something that is both accurate and meets your additional criteria of being=
<br>
simple and direct.<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If we&#39;re not going to have simple text available in the room, let&#39;s=
 at<br>
least stop with the charade that posting the Note Well is meaningful,<br>
and the chairs and shepherds and the IESG will simply have to continue<br>
to deal with the regular stream of late disclosures.<br>
</blockquote>
<br>
... and this is nothing but a strawman. I strongly doubt anyone objecting h=
ere<br>
is opposed to &quot;simple&quot; text as long as said text doesn&#39;t miss=
tate what our IP<br>
rules are.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ned<br>
</blockquote></div></div></div>
</blockquote></div><br></div>

--047d7bd75160fa62c804f1c6c9e5--

From scott.brim@gmail.com  Thu Feb  6 17:37:43 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 CB4CA1A0593 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 17:37:43 -0800 (PST)
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 amDuqrOucDZx for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 17:37:42 -0800 (PST)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 3D3641A0591 for <ietf@ietf.org>; Thu,  6 Feb 2014 17:37:42 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id n16so3434803oag.9 for <ietf@ietf.org>; Thu, 06 Feb 2014 17:37:40 -0800 (PST)
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=FdNao33cpZwLnLi1fCMgXcyUcfJnRWyfDCybTbeaz7M=; b=XcnIIFZ8Z/AJH6fXAl8xilwuhdZJxcD4wgVBvAW2vdcJZCDRcO/tPa4kitTPfewK7+ H0f8EphpeTTkRVqsLB3cWNGPdVk0kCghbpb6jfgm0NAWlWv2Ep0A5/RN6HCiEyNB3ivs z2BlX7lMc/kdls6wv3Y66CZzseX/4sNirTv83qxnQXTV3UCsv0j7ik1YFatpGv97dl1F bve79/4m/OWipYndnZenSRx3gr3Lg9WHWRiNXzNwvUaGXcDDwePLyblhgY7p8V9speyh e1nBcdaIp3uKf6qVn4CAIh+lZL4q+xh8pR9mRYBXHj4mhgmoIYXfXUVqLKb/CeGYvVff so8Q==
MIME-Version: 1.0
X-Received: by 10.60.15.131 with SMTP id x3mr10104747oec.15.1391737060852; Thu, 06 Feb 2014 17:37:40 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 6 Feb 2014 17:37:40 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Thu, 6 Feb 2014 17:37:40 -0800 (PST)
In-Reply-To: <CAHw9_i+BVYNnDJJVVLhN+AeQPVvJCKts=xYHmWgcBs7uKiTF+A@mail.gmail.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <52F3F627.4060308@qti.qualcomm.com> <01P41F0GTO540000CD@mauve.mrochek.com> <CAHw9_i+BVYNnDJJVVLhN+AeQPVvJCKts=xYHmWgcBs7uKiTF+A@mail.gmail.com>
Date: Thu, 6 Feb 2014 20:37:40 -0500
Message-ID: <CAPv4CP_PtmSQi59qzpVThGBfbHwweYiy8gunx8_JN2gqs+6irw@mail.gmail.com>
Subject: Re: Revision to Note Well
From: Scott Brim <scott.brim@gmail.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary=089e015365e6220cb804f1c709de
Cc: ned+ietf <ned+ietf@mauve.mrochek.com>, Pete Resnick <presnick@qti.qualcomm.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: Fri, 07 Feb 2014 01:37:44 -0000

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

On Feb 6, 2014 8:11 PM, "Warren Kumari" <warren@kumari.net> wrote:
> So, how about we simply present *both*.
> "Here is an incomplete summary of our IPR stuff, but it should give you
an overview. <click> This is the longer, more detailed and correct version.
It is also posted online and you agreed to it when signing up.

I was thinking this is exactly what I would do.

--089e015365e6220cb804f1c709de
Content-Type: text/html; charset=ISO-8859-1

<p dir="ltr"><br>
On Feb 6, 2014 8:11 PM, &quot;Warren Kumari&quot; &lt;<a href="mailto:warren@kumari.net">warren@kumari.net</a>&gt; wrote:<br>
&gt; So, how about we simply present *both*.<br>
&gt; &quot;Here is an incomplete summary of our IPR stuff, but it should give you an overview. &lt;click&gt; This is the longer, more detailed and correct version. It is also posted online and you agreed to it when signing up. </p>

<p dir="ltr">I was thinking this is exactly what I would do. </p>

--089e015365e6220cb804f1c709de--

From geoff.ietf@mulligan.com  Thu Feb  6 18:07:02 2014
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C1071A0599; Thu,  6 Feb 2014 18:07:02 -0800 (PST)
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, HTML_MESSAGE=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HkGrwWkVmnAi; Thu,  6 Feb 2014 18:07:00 -0800 (PST)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 144081A058F; Thu,  6 Feb 2014 18:07:00 -0800 (PST)
Received: from [192.168.1.3] (pool-173-73-43-58.washdc.fios.verizon.net [173.73.43.58]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 7B5C724127; Thu,  6 Feb 2014 19:06:52 -0700 (MST)
Message-ID: <52F43FC1.3070507@mulligan.com>
Date: Thu, 06 Feb 2014 19:06:57 -0700
From: Geoff Mulligan <geoff.ietf@mulligan.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: David Misell <david.misell@icloud.com>,  "Andrew G. Malis" <agmalis@gmail.com>
Subject: Re: [89attendees] IETF 89 London - Tube strikes and Oyster cards
References: <019701cf1d83$fed5a7d0$fc80f770$@it.bw> <20140130201807.16038.qmail@joyce.lan> <B31EEDDDB8ED7E4A93FDF12A4EECD30D40249BC4@GLKXM0002V.GREENLNK.net> <7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <EMEW3|ef6593e53a130175eab554c6f8e48345q0UDpD03tjc|ecs.soton.ac.uk|7777B4D5-C19A-422F-8178-6D3C9CE48826@ecs.soton.ac.uk> <1391180744.24761.1834.camel@mightyatom> <C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <EMEW3|2549e0977efb70696f5f06218f50f01bq14AlU03tjc|ecs.soton.ac.uk|C27E3A94-182A-4DD6-BA1C-BD4ABA01FA72@ecs.soton.ac.uk> <52F22EE7.5040809@gmail.com> <455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <EMEW3|b655b6a77f860861eff41b83382febd1q14ClH03tjc|ecs.soton.ac.uk|455C51CA-61A3-494C-9CB5-F820B4D2E157@ecs.soton.ac.uk> <1391608289.24761.4682.camel@mightyatom> <52F24D1F.5040602@acm.org> <B6E9BD27-ADD3-4B11-97ED-C1A1963BA652@nominum.com> <CAA=duU2GbmryF7MTMaP63uz800=FEMrt4idwnjN8JSe6=Uv-OA@mail.gmail.com> <CFDDA56F-A0B4-4204-9E78-DCE782874DAD@icloud.com>
In-Reply-To: <CFDDA56F-A0B4-4204-9E78-DCE782874DAD@icloud.com>
Content-Type: multipart/alternative; boundary="------------090400060304000708050703"
Cc: Avri Doria <avri@acm.org>, IETF <ietf@ietf.org>, 89attendees@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2014 02:07:02 -0000

This is a multi-part message in MIME format.
--------------090400060304000708050703
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit

Does anyone know if the tube strikes effect rail travel.  I plan to take 
the train from Brussels to London.

Geoff

*Geoff Mulligan | Presidential Innovation Fellow | Executive Office of 
the President | 301.975.6283*


On 02/05/2014 08:06 AM, David Misell wrote:
> Also we have tube strikes at the moment.
>
> The hotel is served by several 24hour and night buses, one stops near 
> Paddington station and goes to Heathrow.
>
> www.tfl.gov.uk 
> <http://tfl.gov.uk>/tfl/gettingaround/maps/buses/pdf/paddington-2201.pdf
>
>
> If you have any queries the tfl.gov.uk <http://tfl.gov.uk> web site 
> will answer them but ensure above all else you have an oyster card or 
> bank/credit card with the wifi enabled which reduces the bus fare to 
> £1.40, with a cap of 3 journeys allowing unlimited travel over the day 
> until 0400 for journey start the next day
>
> Also there are railcard and group travel discounts on the heathrow 
> express:
> www.heathrowexpress.com/GroupSaver <http://express.com/GroupSaver>
> Online Exclusive: Save 1/3 When 3 Adults Or More Travel Together.
>
>
> On 5 Feb 2014, at 15:00, Andrew G. Malis <agmalis@gmail.com 
> <mailto:agmalis@gmail.com>> wrote:
>
>> Ted,
>>
>> You have to be careful with exact names of the tube stops. There are
>> three similarly named stations on the London tube - "Edgware Road",
>> "Edgware Road (Bakerloo line)", and just plain "Edgware". The first of
>> the three is the closest, one block from the hotel, the second is a
>> longer walk across several intersections and only serves the Bakerloo
>> line, and the third is very far from the hotel. There's an underground
>> walkway between the hotel and the "Edgware Road (Bakerloo line)"
>> station, but it never seems very safe or secure, especially at night,
>> and my wife and I usually walk aboveground instead.
>>
>> Cheers,
>> Andy
>>
>> On Wed, Feb 5, 2014 at 9:46 AM, Ted Lemon <ted.lemon@nominum.com 
>> <mailto:ted.lemon@nominum.com>> wrote:
>>> It's easy.   Take the tube from Heathrow, get off at Gloucester 
>>> Road, switch to the Circle Line, get off at Edgeware station.   You 
>>> want a train for Edgeware, so this should be easy to identify since 
>>> that's where you're going.   Edgeware is less than a block from the 
>>> Metropole.
>>>
>> _______________________________________________
>> 89attendees mailing list
>> 89attendees@ietf.org <mailto:89attendees@ietf.org>
>> https://www.ietf.org/mailman/listinfo/89attendees
>


--------------090400060304000708050703
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">
    Does anyone know if the tube strikes effect rail travel.&nbsp; I plan to
    take the train from Brussels to London.<br>
    <br>
    Geoff<br>
    <br>
    <b><small><font face="serif">Geoff Mulligan | Presidential
          Innovation Fellow | Executive Office of the President |
          301.975.6283</font></small></b><br>
    <br>
    <br>
    <div class="moz-cite-prefix">On 02/05/2014 08:06 AM, David Misell
      wrote:<br>
    </div>
    <blockquote
      cite="mid:CFDDA56F-A0B4-4204-9E78-DCE782874DAD@icloud.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      Also we have tube strikes at the moment.
      <div><br>
      </div>
      <div>The hotel is served by several 24hour and night buses, one
        stops near Paddington station and goes to Heathrow.</div>
      <div><br>
      </div>
      <div><cite style="color: rgb(0, 144, 48); font-style: normal;
          word-wrap: break-word; font-family: Arial, Helvetica,
          sans-serif; font-size: small; line-height: 15px;">www.<span
            style="font-weight: 700;"><a moz-do-not-send="true"
              href="http://tfl.gov.uk">tfl.gov.uk</a></span>/tfl/gettingaround/maps/<span
            style="font-weight: 700;">buses</span>/pdf/<span
            style="font-weight: 700;">paddington</span>-2201.pdf</cite><span
          style="color: rgb(119, 119, 119); font-family: Arial,
          Helvetica, sans-serif; font-size: small; line-height: 15px;">&nbsp;</span></div>
      <div><span style="color: rgb(119, 119, 119); font-family: Arial,
          Helvetica, sans-serif; font-size: small; line-height: 15px;"><br>
        </span></div>
      <div><br>
      </div>
      <div>If you have any queries the <a moz-do-not-send="true"
          href="http://tfl.gov.uk">tfl.gov.uk</a> web site will answer
        them but ensure above all else you have an oyster card or
        bank/credit card with the wifi enabled which reduces the bus
        fare to &pound;1.40, with a cap of 3 journeys allowing unlimited
        travel over the day until 0400 for journey start the next day</div>
      <div><br>
      </div>
      <div>Also there are railcard and group travel discounts on the
        heathrow express:</div>
      <div>
        <div class="sb_dul" style="padding-top: 1px; color: rgb(64, 64,
          64); font-family: Arial, Helvetica, sans-serif; font-size:
          small; background-color: rgb(249, 252, 247);"><cite
            style="color: rgb(0, 128, 48); font-style: normal;
            word-wrap: break-word; margin-left: 0px; display: inline;
            padding: 1px 0px 0px;">www.<span style="font-weight: 700;">heathrow</span><a
              moz-do-not-send="true"
              href="http://express.com/GroupSaver">express.com/GroupSaver</a></cite></div>
        <div style="border: 0px; border-collapse: collapse;
          border-spacing: 0px; list-style: none; margin: 0px; padding:
          2px 0px 0px; color: rgb(48, 48, 48); font-family: Arial,
          Helvetica, sans-serif; font-size: small; background-color:
          rgb(249, 252, 247); position: static; z-index: auto;">Online
          Exclusive: Save 1/3 When 3 Adults Or More Travel Together.</div>
      </div>
      <div style="border: 0px; border-collapse: collapse;
        border-spacing: 0px; list-style: none; margin: 0px; padding: 2px
        0px 0px; color: rgb(48, 48, 48); font-family: Arial, Helvetica,
        sans-serif; font-size: small; background-color: rgb(249, 252,
        247); position: static; z-index: auto;"><br>
      </div>
      <div><br>
        <div>
          <div>On 5 Feb 2014, at 15:00, Andrew G. Malis &lt;<a
              moz-do-not-send="true" href="mailto:agmalis@gmail.com">agmalis@gmail.com</a>&gt;
            wrote:</div>
          <br class="Apple-interchange-newline">
          <blockquote type="cite">Ted,<br>
            <br>
            You have to be careful with exact names of the tube stops.
            There are<br>
            three similarly named stations on the London tube - "Edgware
            Road",<br>
            "Edgware Road (Bakerloo line)", and just plain "Edgware".
            The first of<br>
            the three is the closest, one block from the hotel, the
            second is a<br>
            longer walk across several intersections and only serves the
            Bakerloo<br>
            line, and the third is very far from the hotel. There's an
            underground<br>
            walkway between the hotel and the "Edgware Road (Bakerloo
            line)"<br>
            station, but it never seems very safe or secure, especially
            at night,<br>
            and my wife and I usually walk aboveground instead.<br>
            <br>
            Cheers,<br>
            Andy<br>
            <br>
            On Wed, Feb 5, 2014 at 9:46 AM, Ted Lemon &lt;<a
              moz-do-not-send="true" href="mailto:ted.lemon@nominum.com">ted.lemon@nominum.com</a>&gt;
            wrote:<br>
            <blockquote type="cite">It's easy. &nbsp;&nbsp;Take the tube from
              Heathrow, get off at Gloucester Road, switch to the Circle
              Line, get off at Edgeware station. &nbsp;&nbsp;You want a train for
              Edgeware, so this should be easy to identify since that's
              where you're going. &nbsp;&nbsp;Edgeware is less than a block from
              the Metropole.<br>
              <br>
            </blockquote>
            _______________________________________________<br>
            89attendees mailing list<br>
            <a moz-do-not-send="true" href="mailto:89attendees@ietf.org">89attendees@ietf.org</a><br>
            <a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/89attendees">https://www.ietf.org/mailman/listinfo/89attendees</a><br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------090400060304000708050703--

From narten@us.ibm.com  Thu Feb  6 21:53:35 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 DB6F41A05AC for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 21:53:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.637
X-Spam-Level: 
X-Spam-Status: No, score=-4.637 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.535, SPF_PASS=-0.001, TO_IN_SUBJ=2.799] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7qVzOTEcwPXF for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 21:53:33 -0800 (PST)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 912091A0375 for <ietf@ietf.org>; Thu,  6 Feb 2014 21:53:33 -0800 (PST)
Received: from /spool/local by e34.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, 6 Feb 2014 22:53:32 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 6 Feb 2014 22:53:29 -0700
Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id DDB9419D8036 for <ietf@ietf.org>; Thu,  6 Feb 2014 22:53:28 -0700 (MST)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by b03cxnp08025.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s175rTM910420676 for <ietf@ietf.org>; Fri, 7 Feb 2014 06:53:29 +0100
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s175rDj3030493 for <ietf@ietf.org>; Thu, 6 Feb 2014 22:53:13 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av04.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s175rDg7030206 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 6 Feb 2014 22:53:13 -0700
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 s175r2P3004494 for <ietf@ietf.org>; Fri, 7 Feb 2014 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s175r2oq004446 for ietf@ietf.org; Fri, 7 Feb 2014 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201402070553.s175r2oq004446@rotala.raleigh.ibm.com>
Date: Fri, 07 Feb 2014 00:53:02 -0500
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: 14020705-1542-0000-0000-000005D90B18
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2014 05:53:36 -0000

Total of 157 messages in the last 7 days.
 
script run at: Fri Feb  7 00:53:02 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.01% |   11 |  9.83% |   122088 | hallam@gmail.com
  5.73% |    9 |  4.74% |    58906 | dhc@dcrocker.net
  4.46% |    7 |  5.54% |    68815 | mary.h.barnes@gmail.com
  4.46% |    7 |  4.12% |    51189 | john-ietf@jck.com
  4.46% |    7 |  3.68% |    45680 | ted.lemon@nominum.com
  3.82% |    6 |  3.71% |    46127 | johnl@taugh.com
  3.18% |    5 |  2.70% |    33568 | brian.e.carpenter@gmail.com
  3.18% |    5 |  2.13% |    26448 | randy@psg.com
  2.55% |    4 |  2.74% |    34065 | daedulus@btconnect.com
  2.55% |    4 |  2.08% |    25863 | paf@frobbit.se
  2.55% |    4 |  2.03% |    25263 | scott.brim@gmail.com
  1.91% |    3 |  2.44% |    30288 | abdussalambaryun@gmail.com
  1.91% |    3 |  2.20% |    27373 | tjc@ecs.soton.ac.uk
  1.91% |    3 |  2.05% |    25427 | tytso@mit.edu
  1.91% |    3 |  1.63% |    20265 | avri@acm.org
  1.91% |    3 |  1.42% |    17688 | dwm@xpasc.com
  1.91% |    3 |  1.34% |    16676 | ned+ietf@mauve.mrochek.com
  1.27% |    2 |  1.52% |    18862 | warren@kumari.net
  1.27% |    2 |  1.48% |    18332 | presnick@qti.qualcomm.com
  1.27% |    2 |  1.32% |    16435 | tbray@textuality.com
  1.27% |    2 |  1.30% |    16124 | stephen.farrell@cs.tcd.ie
  1.27% |    2 |  1.19% |    14724 | christer.holmberg@ericsson.com
  1.27% |    2 |  1.14% |    14176 | chris.dearlove@baesystems.com
  1.27% |    2 |  1.13% |    14070 | elwynd@dial.pipex.com
  1.27% |    2 |  1.13% |    14035 | vesely@tana.it
  1.27% |    2 |  1.08% |    13406 | joe@cdt.org
  1.27% |    2 |  1.07% |    13288 | paul.hoffman@vpnc.org
  0.64% |    1 |  1.69% |    21040 | bclaise@cisco.com
  1.27% |    2 |  1.03% |    12785 | rdroms.ietf@gmail.com
  1.27% |    2 |  0.99% |    12327 | derhoermi@gmx.net
  1.27% |    2 |  0.94% |    11622 | worley@ariadne.com
  1.27% |    2 |  0.87% |    10762 | ajs@anvilwalrusden.com
  1.27% |    2 |  0.85% |    10591 | nomcom-chair-2013@ietf.org
  0.64% |    1 |  1.17% |    14500 | geoff.ietf@mulligan.com
  0.64% |    1 |  1.10% |    13635 | gtw@gtwassociates.com
  0.64% |    1 |  1.03% |    12798 | david.misell@icloud.com
  0.64% |    1 |  0.99% |    12281 | ggm@algebras.org
  0.64% |    1 |  0.99% |    12250 | farmer@umn.edu
  0.64% |    1 |  0.98% |    12131 | sm+ietf@elandsys.com
  0.64% |    1 |  0.95% |    11847 | enrico.marocco@telecomitalia.it
  0.64% |    1 |  0.91% |    11312 | chelliot@pobox.com
  0.64% |    1 |  0.83% |    10293 | housley@vigilsec.com
  0.64% |    1 |  0.83% |    10264 | fred@cisco.com
  0.64% |    1 |  0.79% |     9778 | narten@us.ibm.com
  0.64% |    1 |  0.75% |     9341 | rifaat.ietf@gmail.com
  0.64% |    1 |  0.75% |     9287 | rcallon@juniper.net
  0.64% |    1 |  0.74% |     9177 | salvatore.loreto@ericsson.com
  0.64% |    1 |  0.73% |     9093 | mstjohns@comcast.net
  0.64% |    1 |  0.72% |     8925 | hsantos@isdg.net
  0.64% |    1 |  0.71% |     8794 | iad@ietf.org
  0.64% |    1 |  0.67% |     8268 | joelja@bogus.com
  0.64% |    1 |  0.64% |     7945 | alexandru.petrescu@gmail.com
  0.64% |    1 |  0.64% |     7934 | adrian@olddog.co.uk
  0.64% |    1 |  0.63% |     7861 | rlb@ipv.sx
  0.64% |    1 |  0.63% |     7827 | smb@cs.columbia.edu
  0.64% |    1 |  0.62% |     7742 | bob.hinden@gmail.com
  0.64% |    1 |  0.61% |     7617 | drc@virtualized.org
  0.64% |    1 |  0.60% |     7489 | tobias.gondrom@gondrom.org
  0.64% |    1 |  0.59% |     7301 | gdaley@au.logicalis.com
  0.64% |    1 |  0.58% |     7172 | agmalis@gmail.com
  0.64% |    1 |  0.57% |     7047 | fluffy@cisco.com
  0.64% |    1 |  0.54% |     6697 | glen@amsl.com
  0.64% |    1 |  0.53% |     6597 | andrewf@plixer.com
  0.64% |    1 |  0.51% |     6319 | l.wood@surrey.ac.uk
  0.64% |    1 |  0.50% |     6192 | stbryant@cisco.com
  0.64% |    1 |  0.47% |     5882 | lear@cisco.com
  0.64% |    1 |  0.47% |     5835 | rjsparks@nostrum.com
  0.64% |    1 |  0.46% |     5739 | andrew.hutton@unify.com
  0.64% |    1 |  0.45% |     5615 | kent@bbn.com
  0.64% |    1 |  0.44% |     5455 | hartmans-ietf@mit.edu
  0.64% |    1 |  0.41% |     5077 | mnot@mnot.net
  0.64% |    1 |  0.36% |     4479 | agenda@ietf.org
--------+------+--------+----------+------------------------
100.00% |  157 |100.00% |  1242104 | Total


From lars@netapp.com  Fri Feb  7 00:14:48 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF4461A039D for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 00:14:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, 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 OdA7jPsMFYH0 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 00:14:47 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 5EA0D1A05CA for <ietf@ietf.org>; Fri,  7 Feb 2014 00:14:45 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,799,1384329600";  d="asc'?scan'208";a="100586603"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx11-out.netapp.com with ESMTP; 07 Feb 2014 00:14:43 -0800
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.211]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Fri, 7 Feb 2014 00:05:40 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Revision to Note Well
Thread-Topic: Revision to Note Well
Thread-Index: AQHPI29lDICETuQWaU6hgge24FM4c5qpJF8AgADRnwA=
Date: Fri, 7 Feb 2014 08:05:39 +0000
Message-ID: <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com>
In-Reply-To: <52F3E3F6.7010705@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.106.53.51]
Content-Type: multipart/signed; boundary="Apple-Mail=_DF750E27-A8DB-49C0-8C82-9C2A6B5D604E"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.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: Fri, 07 Feb 2014 08:14:49 -0000

--Apple-Mail=_DF750E27-A8DB-49C0-8C82-9C2A6B5D604E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2014-2-6, at 20:35, Brian E Carpenter <brian.e.carpenter@gmail.com> =
wrote:
> "If you are aware that any contribution (something written, said, or =
discussed in any IETF context) is covered by patents or
> patent applications, you must disclose that fact, or not participate =
in the discussion."
>=20
> That is still wrong, because it doesn't distinguish the case of 3rd =
party
> disclosures, which are optional, from 1st party disclosures, which are
> mandatory.

Exactly. The new text does not address the issue.

Lars

PS: I'll again point to the IRTF statement, which does: =
http://irtf.org/ipr. We'll make it available to the IETF for the low, =
low price of a round of beers for the IRSG :-)

--Apple-Mail=_DF750E27-A8DB-49C0-8C82-9C2A6B5D604E
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-----

iQCVAwUBUvSTztZcnpRveo1xAQJMNwP+OH64rYjnDWYlXKjrpN1h8d/t2qRSD7wh
upDFuSlqgS5jAjzK97rFj1Ikb5EbOZCIiE7xhtsxRZcVf/mTB6nTns+5i6GSLTOR
u47oHNxPkvmvI87Q67VktvovkVugi+G3XiOClp2kA1gQz/4zJe7di7hFLFXqctFm
3CwcgZjGA0s=
=mGza
-----END PGP SIGNATURE-----

--Apple-Mail=_DF750E27-A8DB-49C0-8C82-9C2A6B5D604E--

From dhc@dcrocker.net  Fri Feb  7 07:17:07 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 C0D901A8026 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 07:17:07 -0800 (PST)
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 UtCcxvxzbbhi for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 07:17:06 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 90D801A1F7B for <ietf@ietf.org>; Fri,  7 Feb 2014 07:17:06 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s17FGvh5001074 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Feb 2014 07:17:01 -0800
Message-ID: <52F4F8C5.7030200@dcrocker.net>
Date: Fri, 07 Feb 2014 07:16:21 -0800
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.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Revision to Note Well
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com>
In-Reply-To: <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.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, 07 Feb 2014 07:17:01 -0800 (PST)
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: Fri, 07 Feb 2014 15:17:07 -0000

On 2/7/2014 12:05 AM, Eggert, Lars wrote:
> Exactly. The new text does not address the issue.
>
> Lars
>
> PS: I'll again point to the IRTF statement, which does:http://irtf.org/ipr. We'll make it available to the IETF for the low, low price of a round of beers for the IRSG:-)


1. Has the text been vetted by the IETF's attorney?

2. How does this 'summary' avoid the danger that has been cited, of 
providing a potential ambiguity argument through exploitation of any 
differences between the summary source text?

3. How does any of this resolve the much deeper problem that this 
lengthy thread has served to demonstrate that we very clearly have 
extensive community confusion about on what the current IPR rules are or 
mean?

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From housley@vigilsec.com  Fri Feb  7 07:53:24 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D605F1A01E8 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 07:53:24 -0800 (PST)
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 HqXljvrwi8zt for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 07:53:22 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 360C71AC4AC for <ietf@ietf.org>; Fri,  7 Feb 2014 07:53:22 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 8E784F2409A; Fri,  7 Feb 2014 10:53:12 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id P8QEgAWMgi+l; Fri,  7 Feb 2014 10:52:50 -0500 (EST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 3E442F2409B; Fri,  7 Feb 2014 10:52:51 -0500 (EST)
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <52F0478D.2020701@umn.edu>
Date: Fri, 7 Feb 2014 10:52:39 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <9162EF70-3F2A-4C5D-B744-7C65D4FE16B6@vigilsec.com>
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk> <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com> <028c01cf1a0a$048899d0$0d99cd70$@olddog.co.uk> <52E6D628.80103@umn.edu> <7DA9D44B-1B9D-43BE-B41D-290684A41972@vigilsec.com> <52F0478D.2020701@umn.edu>
To: David Farmer <farmer@umn.edu>
X-Mailer: Apple Mail (2.1085)
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, 07 Feb 2014 15:53:25 -0000

I am posting an update that includes some of your comments.  If a =
document comes along that defines a special-purpose AS number registry =
before this document becomes and RFC, I wouldgladly reference it.  If =
not, such a document can revise the registry that this document =
establishes.

Russ


On Feb 3, 2014, at 8:51 PM, David Farmer wrote:

> I believe if RFC 6890 were used as a template, a Draft could be put =
together quickly, I'm personally willing to help.  I don't see why it =
should be controversial within the community, but unfortunately those =
can be famous last words. :)
>=20
> On 2/3/14, 14:20 , Russ Housley wrote:
>> David:
>>=20
>> With respect to the AS Special purpose Registry, I might sit more =
comfortably in its own document, and then it could be referenced from =
this document. At this point, I'm concerned that he delay to this =
document would be quite unfortunate.  Do you believe that such a =
document can be produced and approved rapidly?  If not, then I'd like to =
see this document move forward and a subsequent document could make an =
update if there is community consensus to evolve the form of the =
special-purpose AS number registry.
>>=20
>> Russ
>>=20
>>=20
>>=20
>>> On 1/25/14, 14:14 , Adrian Farrel wrote:
>>>> Hi Russ,
>>>>=20
>>>> Thanks for this. The -03 revision just posted addresses my =
comments.
>>>>=20
>>>> Adrian
>>>=20
>>> Russ,
>>>=20
>>> I also like the -03 revision, its has generally moved everything in =
the right direction.  But I have a few comments on it.
>>>=20
>>> 1. The part about RFC2860 in Section 1 seems like an incomplete =
thought, at the very least it seems awkward to me.  I'm really not sure =
what you are intending to say.  But, I agree RFC2860 is relevant to the =
discussion.  I'm just not sure you have nailed what to say about it.
>>>=20
>>> 2. I really like the idea of creating a "Special-Purpose AS Number =
Registry".  However, it may be a better idea to spin-off the creation of =
a "Special-Purpose AS Number Registry" into a separate draft.  I'm =
concerned that trying to do two important things in the same document =
will fail to achieve one or both of the important things.  For instance =
the simple section 3 you have currently worries me.  I'd really think =
RFC6890 is the template to use for creating a "Special-Purpose AS Number =
Registry", more below.
>>>=20
>>> If you spin-off the creation of a "Special-Purpose AS Number =
Registry", the following items are for that draft.
>>>=20
>>> 3. There is a draft in WG Last Call in the IDR that documents the =
reservations of ASNs 65535 and 4294967295, the "Last ASNs".
>>> http://tools.ietf.org/html/draft-ietf-idr-last-as-reservation-01
>>>=20
>>> 4. As I said, I like the idea of creating a "Special-Purpose AS =
Number Registry", but it should have certain information recoded about =
each AS number range.  This information should be similar to the format =
described in Section 2.2.1 of RFC6890 for the "Special-Purpose IP =
Address Registries" for IPv4 and IPv6, that you reference elsewhere in =
the draft.
>>>=20
>>> First, there should be general information describing each of the =
special-purpose ASN ranges, essentially the first half of the columns =
specified in Section 2.2.1 of RFC6890;
>>>=20
>>> o AS Number Range - An AS number or range of AS numbers that has =
been
>>>   registered for a special purpose.
>>>=20
>>> o Name - A descriptive name for the special-purpose AS number range.
>>>=20
>>> o RFC - The RFC through which the special-purpose AS number range =
was
>>>   requested.
>>>=20
>>> o Allocation Date - The date upon which the special-purpose AS =
number
>>>   range was allocated.
>>>=20
>>> o Termination Date - The date upon which the allocation is to be
>>>   terminated.  This field is applicable for limited-use allocations
>>>   only.
>>>=20
>>> Then, information specific to how the special-purpose ASNs are to be =
used.  There may be others as well, I but I think these are the minimum.
>>>=20
>>> o Local - A boolean value indicating whether an AS number from the
>>>   allocated special-purpose AS Number range is valid when used as =
the
>>>   value of the "My Autonomous System" field of a BGP OPEN message, =
or
>>>   equivalently in the Capability Value of the "support for =
four-octet
>>>   AS number capability".
>>>=20
>>> o Global - A boolean value indicating whether an ASN from the =
allocated
>>>   special-purpose ASN range is valid in the AS_PATH or AS4_PATH
>>>   attributes when advertised to the global Internet.
>>>=20
>>> o Reserved-by-Protocol - A boolean value indicating whether the
>>>   special-purpose address block is reserved by BGP, itself.  This
>>>   value is "TRUE" if the RFC that created the special-purpose ASN
>>>   range requires all compliant implementations to behave in a =
special
>>>   way when this ASN is used.
>>>=20
>>> I believe this is the table for these last three items
>>>=20
>>>   ASN Range              Local    Global   Reserved-by-Protocol
>>>   ---------------------  -------  -------  --------------------
>>>   0                      FALSE    FALSE    TRUE
>>>   23456                  TRUE[1]  TRUE[1]  TRUE
>>>   64496-64511            FALSE    FALSE    FALSE
>>>   64512-65534            TRUE     FALSE    FALSE
>>>   65535                  FALSE    FALSE    FALSE
>>>   65536-65551            FALSE    FALSE    FALSE
>>>   4200000000-4294967294  TRUE     FALSE    FALSE
>>>   4294967295             FALSE    FALSE    FALSE
>>>=20
>>>   [1] Only valid in a BGP OPEN message or AS_PATH, not valid within =
a
>>>   four-octet AS number capability negotiation or AS4_PATH.
>>>=20
>>>=20
>>> Thanks.
>>>=20
>>> --
>>> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>> 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
>>> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>>=20
>=20
>=20
> --=20
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> 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
> =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=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


From dhc@dcrocker.net  Fri Feb  7 08:22:35 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 E6EDA1A045C; Fri,  7 Feb 2014 08:22:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.179
X-Spam-Level: 
X-Spam-Status: No, score=-3.179 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, 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 7I3im0bIn0QY; Fri,  7 Feb 2014 08:22:32 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 5FA741A0177; Fri,  7 Feb 2014 08:22:32 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s17GMT6u002295 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Feb 2014 08:22:32 -0800
Message-ID: <52F50821.9070700@dcrocker.net>
Date: Fri, 07 Feb 2014 08:21:53 -0800
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.2.0
MIME-Version: 1.0
Subject: Improving IESG & IAB engagement when IETF comments are solicited
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, 07 Feb 2014 08:22:32 -0800 (PST)
Cc: IETF Discussion <ietf@ietf.org>, iesg <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, 07 Feb 2014 16:22:36 -0000

For documents from working groups or individuals, it is typical -- and
generally considered to be required -- to have public review proceed in
a manner that fully responds to concerns that are posted.  This can be a
laborious and even frustrating process, but the community considers it
an important validation process for work carrying the IETF impimatur.

This diligent process is applied to working group Last Call and IETF
Last Call.  "Fully responding" does not mandate agreeing with the
concerns or ensuring that those with concerns agree with the outcome, of
course, but it does mean doing the work of responding in detail and
attempting to find resolution.


There is a decades-long pattern to the process of an IAB or IESG query
for community comments, about IAB or IESG actions that do not require
formal IETF rough consensus -- and sometimes even actions by them that do:

      1.  The IAB or IESG sends a note to the IETF mailing list,
          soliciting comments.

      2.  A variety of comments are made.

      3.  The IAB or IESG very selectively responds to comments, often
          only through one round of response.

      4.  The IAB or IESG publishes its decision

The details of the process can vary, of course.  Sometimes the process
looks very much like a Last Call from a working group, where the IAB or
IESG engages fully, with those making comments, so that the concerns are
fully explored.

But typically, the process is dramatically more constrained.

Simply put, comments often are entirely ignored, or receive at most a
basic response, with no followup.

The latest sequence about IPR issues and the Note Well demonstrate
exactly this problem.  The only exceptional aspect this time is that
quite a few people are pressing back for better engagement.

There is a basic difference between an obligation to discuss issues
diligently, versus an obligation to obtain some form of consensus.  The
former can be done without having the latter.  In effect, the former
calls for 'seeking' a consensus, while the latter demands achieving it.


Here's a different model the IAB and IESG should be following:

    1.  When a decision is not straightforward and reasonably warrants
        review by the IETF community, the IAB or IESG circulates its
        description of the issue, possibly noting the likely decision.
        (I believe that describes existing practice; no change is being
        suggested to this gating step.)

    2.  When comments are posted, each concern or suggestion that is
        raised should be treated as an item for explicit discussion,
        with a goal of trying to resolve it.  This is exactly the model
        typically followed for Last Call items and often followed within
        working groups, during regular development.  So we are all
        familiar with how to handle this process.

    3.  This imposes the burden of /fully/ tracking and discussing each
        concern /and/ of seeking resolution to the concerns that satisfy
        those raising them.  However, absent community consensus that
        the decision must seek IETF rough consensus, this process does
        not change who has final authority over the decision.


This sequence is substantially more work than what has typically been
done.


It's worth it.



d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From john-ietf@jck.com  Fri Feb  7 08:54:45 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 767DB1A0425; Fri,  7 Feb 2014 08:54:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bi1Bdd92cTbd; Fri,  7 Feb 2014 08:54:42 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2709A1A01F5; Fri,  7 Feb 2014 08:54:41 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WBoh3-000EjU-Ds; Fri, 07 Feb 2014 11:54:21 -0500
Date: Fri, 07 Feb 2014 11:54:16 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: Improving IESG & IAB engagement when IETF comments are solicited
Message-ID: <067C750939DA32AA60CACC2C@JcK-HP8200.jck.com>
In-Reply-To: <52F50821.9070700@dcrocker.net>
References: <52F50821.9070700@dcrocker.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
Cc: IETF Discussion <ietf@ietf.org>, 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, 07 Feb 2014 16:54:45 -0000

--On Friday, February 07, 2014 08:21 -0800 Dave Crocker
<dhc@dcrocker.net> wrote:

> For documents from working groups or individuals, it is
> typical -- and
> generally considered to be required -- to have public review
> proceed in
> a manner that fully responds to concerns that are posted.
> This can be a
> laborious and even frustrating process, but the community
> considers it
> an important validation process for work carrying the IETF
> impimatur.
>...
> Simply put, comments often are entirely ignored, or receive at
> most a basic response, with no followup.
>...
> This sequence is substantially more work than what has
> typically been
> done.
> 
> It's worth it.

For whatever it is worth, I'm in complete agreement with Dave's
problem description and plan of action.  We might disagree (or
not) about two things:

(1) I am, generally and in this case, opposed to more rigid
rules.  I think that willingness and effectiveness at engagement
with the community are important attributes for anyone on the
IESG, IAB, or even IAOC and that those who behave as if such
engagement and responsiveness are not important should be the
subject of discussion with the Nomcom or, if necessary,
demonstrations that the recall procedure is really workable.  I
note that, if rigid rules were made, the community's recourse if
they are disregarded is exactly the same: discussions with the
Nomcom or recalls.   (Of course, appeals about specific actions
are possible in either case.)

(2) It seems to me that applying the review process Dave
suggests to individual submissions of non-standards track
documents could help clarify the appropriate uses of that
process just by making the burdens on the IESG and community of
AD sponsorship more clear to all involved.

best,
   john




From paul@nohats.ca  Thu Feb  6 11:15:30 2014
Return-Path: <paul@nohats.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 2C7F61A0432 for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:15:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 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.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kMXMzZ8YY0_m for <ietf@ietfa.amsl.com>; Thu,  6 Feb 2014 11:15:25 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id C784D1A0428 for <ietf@ietf.org>; Thu,  6 Feb 2014 11:15:25 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 83037800AA; Thu,  6 Feb 2014 14:15:23 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1391714123; bh=b8PpXopczRNCAzloKse5eAaMeV/GfhX2M5TKVeKMK+E=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=ibwpm9NtRIzPJYjEqQ31upLu6kJX3PyXwYsRUrztecrWX5PcasTuHmpkFhcDOoCQE KE6o1GlDrcXoc3NGKNjgre3XlC09wfveqob3Mo4LLKNUiST5BXqS5/B9NptDxPv9a9 7Q7MZjiLu3rQ/xzCzYV3qnngErr/yZCzD02b6N/c=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s16JFMNo004244; Thu, 6 Feb 2014 14:15:23 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Thu, 6 Feb 2014 14:15:22 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: Richard Barnes <rlb@ipv.sx>
Subject: Re: Revision to Note Well
In-Reply-To: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
Message-ID: <alpine.LFD.2.10.1402061414320.21252@bofh.nohats.ca>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Mailman-Approved-At: Fri, 07 Feb 2014 09:10:28 -0800
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, 06 Feb 2014 19:15:30 -0000

On Thu, 6 Feb 2014, Richard Barnes wrote:

> The IESG would like to put forward a revision to the proposed new Note Well, after some discussion both on the IETF list [1]
> and within the IESG.
> The revised text can be found on the IESG wiki:
> <http://trac.tools.ietf.org/group/iesg/trac/wiki/DraftNoteWellSummary>
> 
> The only change is the following:
> OLD: "..., you must disclose that fact"
> NEW: "..., you must disclose that fact, or not participate in the discussion"
> 
> This is intended to reflect that BCP 79's requirements for disclosure apply to "Any individual participating in an IETF
> discussion", as opposed to all IETF participants.

Does sitting inside a meeting room and being quiet count as "participate
in the discussion"?

Paul

From scott.brim@gmail.com  Fri Feb  7 09:13:19 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 118271A0425 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:13:19 -0800 (PST)
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 3_Kn2_wIHJAL for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:13:17 -0800 (PST)
Received: from mail-ob0-x22a.google.com (mail-ob0-x22a.google.com [IPv6:2607:f8b0:4003:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id BB4881A01FA for <ietf@ietf.org>; Fri,  7 Feb 2014 09:13:17 -0800 (PST)
Received: by mail-ob0-f170.google.com with SMTP id va2so4321643obc.1 for <ietf@ietf.org>; Fri, 07 Feb 2014 09:13:17 -0800 (PST)
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=PpMHjWmoSedKtJoLrLTdk+Oye0zcUW+eFKlGk8JcdQ8=; b=agEekfE1PKqVwSHW2ZsybboUilAwnQNQ06e9QJdc/WnnIBYBDGMgT2gA9zMXlNlfvA WvoKrDykZdclySowHmUg4wv5sCmUIWCjWT8oK6cw4tXE+uybZy4DvXzhTEhwIa8AKKHX usiiVCsgsyx0oeLzv7bkoJIfWCPBBaE41J0Ce0RWNC52O1TGAh5i+YN+6GlUNY3wLA+v ycKlmmIxkW4tjmUTWtY7JzUFCc52BUg2uNyelLdPmnpJwaiRQgxz37XrQkefimrvKWAw okT4c6eqON5XN5Iw5be6/2+350n7QBt+MjcqzE6+m6z31TWDFS5MFWYMr8y5kyuolUS3 7vDA==
X-Received: by 10.60.50.202 with SMTP id e10mr13629362oeo.39.1391793197483; Fri, 07 Feb 2014 09:13:17 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 7 Feb 2014 09:12:57 -0800 (PST)
In-Reply-To: <alpine.LFD.2.10.1402061414320.21252@bofh.nohats.ca>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <alpine.LFD.2.10.1402061414320.21252@bofh.nohats.ca>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 7 Feb 2014 12:12:57 -0500
Message-ID: <CAPv4CP9fn570wRSQmF9xB9Lidk=qWFkmfxCddNgdUZPPmj7FhQ@mail.gmail.com>
Subject: Re: Revision to Note Well
To: Paul Wouters <paul@nohats.ca>
Content-Type: text/plain; charset=ISO-8859-1
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, 07 Feb 2014 17:13:19 -0000

On Thu, Feb 6, 2014 at 2:15 PM, Paul Wouters <paul@nohats.ca> wrote:
> Does sitting inside a meeting room and being quiet count as "participate
> in the discussion"?

Do you stomp around and roll your eyes while facing other people?

From sob@sobco.com  Fri Feb  7 09:17:29 2014
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 063911A041B for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:17:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.897
X-Spam-Level: 
X-Spam-Status: No, score=0.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 6jyFyxuo3DOI for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:17:27 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 74FD21A0416 for <ietf@ietf.org>; Fri,  7 Feb 2014 09:17:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id D8BB9625CEA for <ietf@ietf.org>; Fri,  7 Feb 2014 12:17:26 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GSFa0sMlb-j5 for <ietf@ietf.org>; Fri,  7 Feb 2014 12:17:26 -0500 (EST)
Received: from [136.248.127.175] (unknown [136.248.127.175]) by sobco.sobco.com (Postfix) with ESMTPSA id DEAE3625CD9 for <ietf@ietf.org>; Fri,  7 Feb 2014 12:17:25 -0500 (EST)
From: "Scott O. Bradner" <sob@sobco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_7E451F4E-13B0-4D7E-A466-2482FAF0727E"; protocol="application/pgp-signature"; micalg=pgp-sha512
Message-Id: <FB05AAF5-D590-4D3F-885F-82B4F853B0D5@sobco.com>
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Revision to Note Well
Date: Fri, 7 Feb 2014 12:17:24 -0500
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com>
To: "ietf@ietf.org" <ietf@ietf.org>
In-Reply-To: <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com>
X-Mailer: Apple Mail (2.1827)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2014 17:17:29 -0000

--Apple-Mail=_7E451F4E-13B0-4D7E-A466-2482FAF0727E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

maybe the IESG has too strong a NIH phobia to do the simple thing and =
adopt what the IRTF did=20

in any case the question of =93participation=94 was debated long and =
hard in two IPR BOFs and on the IPR working list
with the result was to replace the idea participation with "any activity =
that was intended to affect the IETF Standards Process=94

see draft-bradner-rfc3979bis-06.txt

Scott

On Feb 7, 2014, at 3:05 AM, Eggert, Lars <lars@netapp.com> wrote:

> On 2014-2-6, at 20:35, Brian E Carpenter <brian.e.carpenter@gmail.com> =
wrote:
>> "If you are aware that any contribution (something written, said, or =
discussed in any IETF context) is covered by patents or
>> patent applications, you must disclose that fact, or not participate =
in the discussion."
>>=20
>> That is still wrong, because it doesn't distinguish the case of 3rd =
party
>> disclosures, which are optional, from 1st party disclosures, which =
are
>> mandatory.
>=20
> Exactly. The new text does not address the issue.
>=20
> Lars
>=20
> PS: I'll again point to the IRTF statement, which does: =
http://irtf.org/ipr. We'll make it available to the IETF for the low, =
low price of a round of beers for the IRSG :-)


--Apple-Mail=_7E451F4E-13B0-4D7E-A466-2482FAF0727E
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

iQEcBAEBCgAGBQJS9RUkAAoJEGfrUQgIbw1kuCEH/0C/3j/jYRgfm35gXf6qdBwy
jJF2uOnuiUEq1WehzkRbOOI0clAV4ScXsO/7RrnQkz6JMTr5alBqTrC7Hxo7Z7yc
Vi3UVqMqozSBNwqCpGgNa/M7aIc+eLQX4ENf9Fz0dr0Pmw/f0Z+Wfjiqrt7OIIiB
IrwiPtS8Kaz6/Y861PqYs0GpDdm302PIl8Le8GHDh7jOoWH+Bj4ias31Bf0XPUFV
AJ6cr5Todt0kEukkv9po5SCvCiqDogXSGyVUf1qw8uaUyrc7i8tXyjX+21rjqFF4
dfmv50NCme2I3AlztfFF+S9ZM3wRMkUQONUrfjvHj3iQvx1E6DKnC46omWtfTMU=
=TifU
-----END PGP SIGNATURE-----

--Apple-Mail=_7E451F4E-13B0-4D7E-A466-2482FAF0727E--

From presnick@qti.qualcomm.com  Fri Feb  7 09:28:42 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 2F8731A0416 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:28:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level: 
X-Spam-Status: No, score=-2.536 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.535, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22ydtQaOGhA0 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:28:40 -0800 (PST)
Received: from sabertooth01.qualcomm.com (sabertooth01.qualcomm.com [65.197.215.72]) by ietfa.amsl.com (Postfix) with ESMTP id 640521A017B for <ietf@ietf.org>; Fri,  7 Feb 2014 09:28:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1391794120; x=1423330120; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=3WRtBYtdEsGBM8PCXt71xxyB9rgdY5+qGgo0pBuBE1g=; b=Mju+2Os3krV9yd79B0IlkdhDpM//DtvYseuWQNfj1yfHfK6SKdJMXOSq a3AlfSRvlSFsDXPczFZcr85M2H/88IkF8zbhqRSIntCd7+AVn///dNUvK CbmK26/yMiIhkt6BwXtNJoQshKN9hLWAMRxaNArsdrEK9u53RK01NtVS/ c=;
X-IronPort-AV: E=McAfee;i="5400,1158,7341"; a="59052345"
Received: from ironmsg03-r.qualcomm.com ([172.30.46.17]) by sabertooth01.qualcomm.com with ESMTP; 07 Feb 2014 09:28:40 -0800
X-IronPort-AV: E=McAfee;i="5400,1158,7341"; a="626068640"
Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by Ironmsg03-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 07 Feb 2014 09:28:40 -0800
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; Fri, 7 Feb 2014 09:28:39 -0800
Message-ID: <52F517C2.1050609@qti.qualcomm.com>
Date: Fri, 7 Feb 2014 11:28:34 -0600
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: "Eggert, Lars" <lars@netapp.com>
Subject: Re: Revision to Note Well
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com>
In-Reply-To: <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.39.5]
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, 07 Feb 2014 17:28:42 -0000

On 2/7/14 2:05 AM, Eggert, Lars wrote:
> I'll again point to the IRTF statement, which does:http://irtf.org/ipr. We'll make it available to the IETF for the low, low price of a round of beers for the IRSG:-)
>    

FWIW, I like the IRTF statement and think it would be a fine 
addition/replacement *for what's on the web site*. It's not short enough 
IMO for the face-to-face in-room reminder, particularly if a chair were 
going to actually *say* it, but maybe if something of this nature 
appeared on the web site, the in-room reminder wouldn't be as necessary.

(And to answer an earlier question, yes, we've had a bunch of late 
disclosures. They seem to come in waves. That's what motivated some of 
us to push for some kind of "plain language" thing that could be grasped 
easily in f2f meetings. But again, maybe if we had something along the 
lines of the IRTF statement plastered everywhere, people would start to 
"get it" and we wouldn't need a one-liner to get people sitting in a f2f 
meeting to notice.)

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478


From alexandru.petrescu@gmail.com  Fri Feb  7 09:42:55 2014
Return-Path: <alexandru.petrescu@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 938C31AC829 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:42:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Ha2dbwZtSlM for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:42:53 -0800 (PST)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) by ietfa.amsl.com (Postfix) with ESMTP id 287E91A0128 for <ietf@ietf.org>; Fri,  7 Feb 2014 09:42:53 -0800 (PST)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s17HgqRD009227 for <ietf@ietf.org>; Fri, 7 Feb 2014 18:42:52 +0100
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id F1BF120444A for <ietf@ietf.org>; Fri,  7 Feb 2014 18:43:15 +0100 (CET)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E79A3203650 for <ietf@ietf.org>; Fri,  7 Feb 2014 18:43:15 +0100 (CET)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s17HgoiH018103 for <ietf@ietf.org>; Fri, 7 Feb 2014 18:42:52 +0100
Message-ID: <52F51B1A.3010304@gmail.com>
Date: Fri, 07 Feb 2014 18:42:50 +0100
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-v6ops-64share-09.txt> (Extending an IPv6 /64 Prefix from a 3GPP Mobile Interface to a LAN link) to Informational RFC
References: <20140207152042.31823.59103.idtracker@ietfa.amsl.com>
In-Reply-To: <20140207152042.31823.59103.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2014 17:42:55 -0000

The draft says:
> R-4: The UE MUST decrement the TTL when passing packets between IPv6
>       links across the UE.

It should say Hop Limit instead.

>   The LAN link originated RA message carries a copy of the following
>    3GPP radio link received RA message option fields:
>
>    o  MTU (if not provided by the 3GPP network, the UE will provide its
>       3GPP link MTU size)
>    o  Prefix Information

I doubt the MTU on the LAN should the same as on the WAN... they're 
different in nature.

> Below is the general procedure for this scenario:
>
>    1.  The user activates router functionality for a LAN on the UE.

but continues to act as a Host when receiving an RA to configure a next 
hop for the default route.

Alex

Le 07/02/2014 16:20, The IESG a écrit :
>
> The IESG has received a request from the IPv6 Operations WG (v6ops) to
> consider the following document:
> - 'Extending an IPv6 /64 Prefix from a 3GPP Mobile Interface to a LAN
>     link'
>    <draft-ietf-v6ops-64share-09.txt> as Informational RFC
>
> 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-02-21. 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 requirements for extending an IPv6 /64 prefix
>     from a User Equipment 3GPP radio interface to a LAN link as well as
>     two implementation examples.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-64share/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-v6ops-64share/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>



From sm@elandsys.com  Fri Feb  7 09:56:26 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 44B531A03F1 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:56:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.535
X-Spam-Level: 
X-Spam-Status: No, score=-2.535 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.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WDV_b89qdtD5 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 09:56:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 78DA61A03E1 for <ietf@ietf.org>; Fri,  7 Feb 2014 09:56:25 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.147.117]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s17HuBLT007816 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 7 Feb 2014 09:56:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1391795784; bh=Z2QQk6kU9i8Ixn/xaygx1cR8tFbNWAQ3n0nryp+D2y4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UVJrvTcckEXv7IztD698WBBs1CvThsY8rUfCGdLE8MEhKFQQWHnWxD9SMyugghr+/ KYWQRZl6qfNSvlJCcKpcEA66MPR7CKCGlu0eVZ17RU0bkESeT8Vtu9iu4E+zSry2q0 UNsYRNDVAoZo48YSedeVrHFgC3nApiLsppiO5jBM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1391795784; i=@elandsys.com; bh=Z2QQk6kU9i8Ixn/xaygx1cR8tFbNWAQ3n0nryp+D2y4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ms3Siv3U9QJ/7PQvsYYlrHjvGwQuqgYvtRjCvZse0m5Z24ZgXSEjScwVFu6begKe2 6raUctvCf2ovYhX5EwdWi/Lua5odFSgDDKd/IfNqvmdHMsL/WYwRj3Tfl4aG4UWgia PHnt8ZVPnKU8BA8gqoKsjCxwIZsmysQ/yYJV+Ze8=
Message-Id: <6.2.5.6.2.20140207095510.0b3ad000@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 07 Feb 2014 09:56:01 -0800
To: Paul Wouters <paul@nohats.ca>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Revision to Note Well
In-Reply-To: <alpine.LFD.2.10.1402061414320.21252@bofh.nohats.ca>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <alpine.LFD.2.10.1402061414320.21252@bofh.nohats.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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, 07 Feb 2014 17:56:26 -0000

Hi Paul,
At 11:15 06-02-2014, Paul Wouters wrote:
>Does sitting inside a meeting room and being quiet count as "participate
>in the discussion"?

No.

Regards,
S. Moonesamy 


From john-ietf@jck.com  Fri Feb  7 10:10:39 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 3415B1A019E for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 10:10:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yvY97OGf_Vw for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 10:10:37 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id D458E1A00F0 for <ietf@ietf.org>; Fri,  7 Feb 2014 10:10:36 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WBprp-000EoX-Ay; Fri, 07 Feb 2014 13:09:33 -0500
Date: Fri, 07 Feb 2014 13:09:28 -0500
From: John C Klensin <john-ietf@jck.com>
To: Pete Resnick <presnick@qti.qualcomm.com>, "Eggert, Lars" <lars@netapp.com>
Subject: Re: Revision to Note Well
Message-ID: <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com>
In-Reply-To: <52F517C2.1050609@qti.qualcomm.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.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
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, 07 Feb 2014 18:10:39 -0000

--On Friday, February 07, 2014 11:28 -0600 Pete Resnick
<presnick@qti.qualcomm.com> wrote:

> On 2/7/14 2:05 AM, Eggert, Lars wrote:
>> I'll again point to the IRTF statement, which
>> does:http://irtf.org/ipr. We'll make it available to the IETF
>> for the low, low price of a round of beers for the IRSG:-)
>>    
> 
> FWIW, I like the IRTF statement and think it would be a fine
> addition/replacement *for what's on the web site*. It's not
> short enough IMO for the face-to-face in-room reminder,
> particularly if a chair were going to actually *say* it, but
> maybe if something of this nature appeared on the web site,
> the in-room reminder wouldn't be as necessary.

Pete, 

As others have suggested, if you want to raise a "please pay
attention to things you have presumably read" flag in meetings
and especially if you think the current version is too long or
complicated, just do that with one of many versions of the "if
you or your organization have IPR in this topic you had best
either understand the BCP provisions or leave" statement, with
or without a second "if know of someone else's, you should be
paying attention to the BCPs too" remark. 

Don't try to summarize.  You can't get it right in a sentence or
four and will just create risks without improving understanding
or, most likely, compliance.

> (And to answer an earlier question, yes, we've had a bunch of
> late disclosures. They seem to come in waves.
>...

Let me then suggest a small bit of research.  You know who the
responsible parties are.  Have you asked them whether additional
notices would have made any difference and, if so, of what sort
and where?  Obviously some will be unwilling (or unable) to
respond accurately.  But it would be nice to have at least a
shred of evidence that more investment in fine-tuning
announcements would actually improve the rate of timely
disclosures.

In addition, there is a more interesting question than "have
their been late disclosures".  It is "how many of the late
disclosures were defended on the basis of ignorance about the
rules?".  If the number of those is non-zero, it would also be
interesting to know whether (and how often) that claim has been
made under oath in an actual proceeding rather than informal
remarks to the IESG.
  
Unless there have been serious claims that the reason for
non-disclosure is ignorance of the rules or our failure to have
enough notices, I'm not sure what problem you are trying to
solve that is important enough to justify the costs of this
discussion.

best,
     john


From scott.brim@gmail.com  Fri Feb  7 10:39:33 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 E4DB41A0416 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 10:39:33 -0800 (PST)
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 mlDGU2z8ErvY for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 10:39:32 -0800 (PST)
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 0F7F61A03CD for <ietf@ietf.org>; Fri,  7 Feb 2014 10:39:32 -0800 (PST)
Received: by mail-oa0-f52.google.com with SMTP id i4so4690666oah.11 for <ietf@ietf.org>; Fri, 07 Feb 2014 10:39:31 -0800 (PST)
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=U4a+qgvlp2ZegwnEDyOPRniaoB3IMKkhMXgFIwHOrsA=; b=fC7aMQLkc2oA6fxcohGeVUMn8FChM3eNX+rGXXkqBaiJZXC4SpJG/n8YarakTi7KoU wBAuWl7VCSEuQxFgb0WbM2tmpNzNFlBDOn2LDCE1q0Ru6f5umFsv+CR8kuEvCT8CohjV 2R7CdFk7nyM8SOSZK9+q3LxTJx4jsPSl4XkIl4Ll2cdQMbPFiKPoZt2NP6BTM4CwdAy3 HasmqtiDdOTPfTTUExW77ebhdOHMa2N5qhWHH2uf2KJZlsh6X2632LV4VsThUGVUOiSz Z8djwt1syAnJdhXxXsiYvJHI98FzZlC9TDux5ZuK+8uQY2Wu57fMJZx1TJr4RUaPEV1E G9kw==
X-Received: by 10.182.246.39 with SMTP id xt7mr14072777obc.16.1391798371857; Fri, 07 Feb 2014 10:39:31 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Fri, 7 Feb 2014 10:39:11 -0800 (PST)
In-Reply-To: <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Fri, 7 Feb 2014 13:39:11 -0500
Message-ID: <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com>
Subject: Re: Revision to Note Well
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Pete Resnick <presnick@qti.qualcomm.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: Fri, 07 Feb 2014 18:39:34 -0000

I'm concerned that any abbreviated form will inadequately represent
the nuances of the full policy, and that if we create a single uniform
abbreviated version that must be shown at f2f meetings, that opens
loopholes. For example, possibly: "Well, yes I agreed to the Note
Well, but then in the meeting they showed a different version that
didn't cover X. I thought that took precedence."

There are many ways the full Note Well is dealt with at this time,
most of them good. I don't think you'll get more attention paid to the
IPR policy by showing an abbreviated form.

Scott

From brian.e.carpenter@gmail.com  Fri Feb  7 11:21: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 36B691ACCFA for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:21:11 -0800 (PST)
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 wbU8BK8rvtV7 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:21:09 -0800 (PST)
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 BB3971A01D2 for <ietf@ietf.org>; Fri,  7 Feb 2014 11:21:09 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id rp16so3631942pbb.6 for <ietf@ietf.org>; Fri, 07 Feb 2014 11:21:09 -0800 (PST)
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=UGCgWJ1IUGVGKyU0sKd3REANunZvB1NMm8d0vw2cEz0=; b=JbH4f382v9EvmwbqntkV+BQiKGhPlFBOQgXp1KTeemyyLIxDe0f4v8veDaPtAr44gN dBV8Dx4rrEueqaulJTzTwWrFm0oqHOaf7ZnWeudBsVLTSG2GOIJa9OHzbHS3ShiU4mma zrf+upfazPiFGkwAzvQVucFSr72Nj87XjtNXexttXjhxQL8ZMHaqQ5VgvUHe+ESbGNgx JTRami8uH9lz/iQzAZZX+bfaWQyiH8eSwXvvo3bYP90JfDK2VLSFS84Lj9RSPIqGiIrc tKQRDEl1XfUu5kVtqfkeYfe0Fzr1A9r7DkPIGmV444BD20YrIIuX5zBrFV1bvVHb/r1q 3+CA==
X-Received: by 10.68.87.98 with SMTP id w2mr21753167pbz.2.1391800869723; Fri, 07 Feb 2014 11:21:09 -0800 (PST)
Received: from [192.168.178.23] (208.199.69.111.dynamic.snap.net.nz. [111.69.199.208]) by mx.google.com with ESMTPSA id zc6sm40060971pab.18.2014.02.07.11.21.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Feb 2014 11:21:08 -0800 (PST)
Message-ID: <52F5322F.1060002@gmail.com>
Date: Sat, 08 Feb 2014 08:21:19 +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: Scott Brim <scott.brim@gmail.com>
Subject: Re: Revision to Note Well
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com>
In-Reply-To: <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: John C Klensin <john-ietf@jck.com>, Pete Resnick <presnick@qti.qualcomm.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: Fri, 07 Feb 2014 19:21:11 -0000

On 08/02/2014 07:39, Scott Brim wrote:
> I'm concerned that any abbreviated form will inadequately represent
> the nuances of the full policy, and that if we create a single uniform
> abbreviated version that must be shown at f2f meetings, that opens
> loopholes. For example, possibly: "Well, yes I agreed to the Note
> Well, but then in the meeting they showed a different version that
> didn't cover X. I thought that took precedence."
> 
> There are many ways the full Note Well is dealt with at this time,
> most of them good. I don't think you'll get more attention paid to the
> IPR policy by showing an abbreviated form.

Indeed, I suspect that many IETF participants simply shut down
their ears as soon as the subject of IPR is mentioned, and click
through the Note Well (and through this thread) without reading.
For them, the form of words is irrelevant. For the ones who take
notice, the form of words is probably irrelevant too, since all
forms ultimately lead to the BCP and that's what counts.

So if there is a basic problem, it's getting people to pay attention
to the topic at all.

I would theorise that the people who ignore the topic actually
find it rather unpleasant and want it to go away.

   Brian

From john-ietf@jck.com  Fri Feb  7 11:22:54 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 CB4C81AD10A for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:22:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SbhTMKa97fWI for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:22:53 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id DF5E51AD1F5 for <ietf@ietf.org>; Fri,  7 Feb 2014 11:22:49 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WBqza-000EtC-Ms; Fri, 07 Feb 2014 14:21:38 -0500
Date: Fri, 07 Feb 2014 14:21:33 -0500
From: John C Klensin <john-ietf@jck.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Revision to Note Well
Message-ID: <26B22F83E14E067E472D274E@JcK-HP8200.jck.com>
In-Reply-To: <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.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
Cc: Pete Resnick <presnick@qti.qualcomm.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: Fri, 07 Feb 2014 19:22:54 -0000

--On Friday, February 07, 2014 13:39 -0500 Scott Brim
<scott.brim@gmail.com> wrote:

> I'm concerned that any abbreviated form will inadequately
> represent the nuances of the full policy, and that if we
> create a single uniform abbreviated version that must be shown
> at f2f meetings, that opens loopholes. For example, possibly:
> "Well, yes I agreed to the Note Well, but then in the meeting
> they showed a different version that didn't cover X. I thought
> that took precedence."

I think we are in violent agreement.  That is precisely why I'm
more in favor of a cautionary pointer to the actual rules than
to any "abbreviated form" or "summary".  If we are not in
agreement, I'd really appreciate any hints that would improve my
understanding.

> There are many ways the full Note Well is dealt with at this
> time, most of them good. I don't think you'll get more
> attention paid to the IPR policy by showing an abbreviated
> form.

I think I agree but note that someone who "conforms to" the Note
Well rather than the relevant BCPs is likely to either get
themselves in trouble or discover loopholes that permit them to
claim that they followed the rules as they understood them.  The
"full" Note Well is lots better in that regard than the proposed
simplified replacements.  But the reality is that any summary
statements that go very far beyond "the IETF has IPR policies,
they apply, or may apply, to you if any of these conditions (and
maybe some others) are applicable, and, by sitting here and/or
opening your mouth, you have agreed that you are bound by them
and better understand what you are committed to" is likely to be
problematic.  What is notable about that sort of statement is
that it does not try to explain, in summary, abbreviated, or
other form, what those policies are.  It just announces that
there are policies, that they are binding on those who
participate, and, preferably, provides a pointer.

best,
   john






From spencerdawkins.ietf@gmail.com  Fri Feb  7 11:26:00 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 D64701A01D2 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:26:00 -0800 (PST)
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 4iAr720MaqOC for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:25:59 -0800 (PST)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 707981A013C for <ietf@ietf.org>; Fri,  7 Feb 2014 11:25:59 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id g12so4717601oah.3 for <ietf@ietf.org>; Fri, 07 Feb 2014 11:25:59 -0800 (PST)
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=sWdTOwR0QCY0GGw4QUtK7bbBAbYZEXxodEYdXWi8QmU=; b=BZQc6kqZZV0kMheryFt+lcokGWUO36IKKWK4vvrZiHmSlQgSd8rFeGJmykQ2w7oHLn QssY8lpTRKBInOU2jFGiq+rIgjyYZptF+Y89hVgXGKQGXwrvyo/pwjeponc0qOofJdFz D1tA6wcT6M2bX85JtBVoDt+PoF4vJKTGaFBfz7o6S+vI5HUBA/0rA0jRx53DBmsxI/O+ /Lc3Z55eMCyGeDuyEyGpVGDrtes69JpH4Tkx54KCIbXivuZxnarUP0TVElmUjUb91/pf NNJjeZIpwnZN5fCeCWTuXvhGGjsk4FuAI4NCILVgbTN7vrVE8/yFbMxLi39YH1uvSw6H SAVQ==
X-Received: by 10.60.98.174 with SMTP id ej14mr14220277oeb.16.1391801159201; Fri, 07 Feb 2014 11:25:59 -0800 (PST)
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 o6sm33030948oel.4.2014.02.07.11.25.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Feb 2014 11:25:58 -0800 (PST)
Message-ID: <52F53343.30901@gmail.com>
Date: Fri, 07 Feb 2014 13:25:55 -0600
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: "Eggert, Lars" <lars@netapp.com>,  Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Revision to Note Well
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com>
In-Reply-To: <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 07 Feb 2014 19:26:01 -0000

On 02/07/2014 02:05 AM, Eggert, Lars wrote:
>   PS: I'll again point to the IRTF statement, which does: 
> http://irtf.org/ipr. We'll make it available to the IETF for the low, 
> low price of a round of beers for the IRSG :-) 

Just so people have full information for this discussion, at least one 
member of the IRSG doesn't drink beer, so Lars's suggested price is 
cheaper than you think from looking at http://irtf.org/irsg ...

From sob@sobco.com  Fri Feb  7 11:43:41 2014
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 911951A03DC for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:43:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.897
X-Spam-Level: 
X-Spam-Status: No, score=0.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 yoaZ1DSXuTNG for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:43:40 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id EFD951A01D2 for <ietf@ietf.org>; Fri,  7 Feb 2014 11:43:39 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 735E9626990 for <ietf@ietf.org>; Fri,  7 Feb 2014 14:43:39 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YsLmaj8onTjk for <ietf@ietf.org>; Fri,  7 Feb 2014 14:43:38 -0500 (EST)
Received: from newdev.cadm.harvard.edu (newdev.cadm.harvard.edu [128.103.229.199]) by sobco.sobco.com (Postfix) with ESMTPSA id B86A9626980 for <ietf@ietf.org>; Fri,  7 Feb 2014 14:43:38 -0500 (EST)
From: "Scott O. Bradner" <sob@sobco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_199AD835-1C5E-48DA-8A84-482AA583335D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Message-Id: <78070B4D-C747-46AD-8ECF-75F3E240E922@sobco.com>
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Revision to Note Well (some history)
Date: Fri, 7 Feb 2014 14:43:37 -0500
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com>
To: IETF discussion list <ietf@ietf.org>
In-Reply-To: <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com>
X-Mailer: Apple Mail (2.1827)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2014 19:43:42 -0000

--Apple-Mail=_199AD835-1C5E-48DA-8A84-482AA583335D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

something that is being missed in this discussion

the old =93Note Well=94 does not do, nor was it intended to do, what =
people have assumed it did

the Note Well was developed, starting in about April 2000, to provide =
classification
on what should be considered a =93contribution=94 to the IETF - at the =
time there
was a lot of confusion - some people thought the 2026 IPR rules only =
applied to
Internet Draft submission and others thought it covered mailing list and=20=

microphone statements - the Note Well was developed by me and the then =
IETF lawyer,
Geoff Stewart, with the help of Steve Coya and initially discussed at an =
IESG retreat.

a common feature of the proposed revisions (the IERTF one as well as the =
IESG ones)
is to expand the mission of the Note Well to actually say what you =
should DO if you
have IPR that an IETF working group would be better off knowing about

note well that the above is a history lesson for context and should not =
discus the
current discussion thread other than to perhaps forestall a return to =
the good old
Note Well that was not, by itself, actionable

Scott

On Feb 7, 2014, at 1:39 PM, Scott Brim <scott.brim@gmail.com> wrote:

> I'm concerned that any abbreviated form will inadequately represent
> the nuances of the full policy, and that if we create a single uniform
> abbreviated version that must be shown at f2f meetings, that opens
> loopholes. For example, possibly: "Well, yes I agreed to the Note
> Well, but then in the meeting they showed a different version that
> didn't cover X. I thought that took precedence."
>=20
> There are many ways the full Note Well is dealt with at this time,
> most of them good. I don't think you'll get more attention paid to the
> IPR policy by showing an abbreviated form.
>=20
> Scott


--Apple-Mail=_199AD835-1C5E-48DA-8A84-482AA583335D
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

iQEcBAEBCgAGBQJS9TdpAAoJEGfrUQgIbw1kBdsIAIA+sXl21Y+MsWy0xML+v6cv
M6+pEHqnjIPJwopMSpebqahZVCBpeMQSd3zZecZGCU11OGlXqo/7JBUb7CRffqcd
cB5IAIHpojDMC9b9OoybqaMlEzwdiI/yhHa2wWpHHODDjrnxE1J6ktrACqAwV37n
kG0G41bPhiO6ETi2nVjuEgMxTAGetw/wiaWxkDU+Po1+JJE4Z7bw5wSzh0hhjOGJ
aLCAJIkNQFIl5GphZNS+kc4vLpPdo1tFDgzwDyaaQbGPz6M7JVaxN5FBopmuw98g
vnc+Bo6b5eYRJ9S67Fbsfm6VaOWG8S+t4T9CBZZGq90LNFZnDkDctLL2iI9mfZk=
=70Ui
-----END PGP SIGNATURE-----

--Apple-Mail=_199AD835-1C5E-48DA-8A84-482AA583335D--

From sob@sobco.com  Fri Feb  7 11:46:20 2014
Return-Path: <sob@sobco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF60E1ACCE3 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:46:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.897
X-Spam-Level: 
X-Spam-Status: No, score=0.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, 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 YkJzHvIgm9ml for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 11:46:19 -0800 (PST)
Received: from sobco.sobco.com (unknown [136.248.127.164]) by ietfa.amsl.com (Postfix) with ESMTP id 660CB1A04F5 for <ietf@ietf.org>; Fri,  7 Feb 2014 11:46:19 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by sobco.sobco.com (Postfix) with ESMTP id 346A46269BE for <ietf@ietf.org>; Fri,  7 Feb 2014 14:46:19 -0500 (EST)
X-Virus-Scanned: amavisd-new at sobco.com
Received: from sobco.sobco.com ([127.0.0.1]) by localhost (sobco.sobco.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CwbAo5Pizbvg for <ietf@ietf.org>; Fri,  7 Feb 2014 14:46:17 -0500 (EST)
Received: from newdev.cadm.harvard.edu (newdev.cadm.harvard.edu [128.103.229.199]) by sobco.sobco.com (Postfix) with ESMTPSA id B23E46269A9 for <ietf@ietf.org>; Fri,  7 Feb 2014 14:46:17 -0500 (EST)
From: "Scott O. Bradner" <sob@sobco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6413B3E0-C490-45AF-8FD8-C9F278997582"; protocol="application/pgp-signature"; micalg=pgp-sha512
Message-Id: <3F608B59-7C5E-4FDA-B09A-EF7F801EBC6A@sobco.com>
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Revision to Note Well (some history) - updated
Date: Fri, 7 Feb 2014 14:46:17 -0500
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com> <78070B4D-C747-46AD-8ECF-75F3E240E922@sobco.com>
To: IETF discussion list <ietf@ietf.org>
In-Reply-To: <78070B4D-C747-46AD-8ECF-75F3E240E922@sobco.com>
X-Mailer: Apple Mail (2.1827)
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2014 19:46:21 -0000

--Apple-Mail=_6413B3E0-C490-45AF-8FD8-C9F278997582
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

oops - reviewing my logs, it was Jorge Contreras not Geoff Stewart, and =
John Klensin was part of
the initial (to blame) group

Scott

On Feb 7, 2014, at 2:43 PM, Scott O. Bradner <sob@sobco.com> wrote:

> something that is being missed in this discussion
>=20
> the old =93Note Well=94 does not do, nor was it intended to do, what =
people have assumed it did
>=20
> the Note Well was developed, starting in about April 2000, to provide =
classification
> on what should be considered a =93contribution=94 to the IETF - at the =
time there
> was a lot of confusion - some people thought the 2026 IPR rules only =
applied to
> Internet Draft submission and others thought it covered mailing list =
and=20
> microphone statements - the Note Well was developed by me and the then =
IETF lawyer,
> Geoff Stewart, with the help of Steve Coya and initially discussed at =
an IESG retreat.
>=20
> a common feature of the proposed revisions (the IERTF one as well as =
the IESG ones)
> is to expand the mission of the Note Well to actually say what you =
should DO if you
> have IPR that an IETF working group would be better off knowing about
>=20
> note well that the above is a history lesson for context and should =
not discus the
> current discussion thread other than to perhaps forestall a return to =
the good old
> Note Well that was not, by itself, actionable
>=20
> Scott
>=20
> On Feb 7, 2014, at 1:39 PM, Scott Brim <scott.brim@gmail.com> wrote:
>=20
>> I'm concerned that any abbreviated form will inadequately represent
>> the nuances of the full policy, and that if we create a single =
uniform
>> abbreviated version that must be shown at f2f meetings, that opens
>> loopholes. For example, possibly: "Well, yes I agreed to the Note
>> Well, but then in the meeting they showed a different version that
>> didn't cover X. I thought that took precedence."
>>=20
>> There are many ways the full Note Well is dealt with at this time,
>> most of them good. I don't think you'll get more attention paid to =
the
>> IPR policy by showing an abbreviated form.
>>=20
>> Scott
>=20


--Apple-Mail=_6413B3E0-C490-45AF-8FD8-C9F278997582
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

iQEcBAEBCgAGBQJS9TgJAAoJEGfrUQgIbw1kMVUH+QEzP00gPhsehZglgMR+a9uA
5k62JPaPWAh6RTurPvthdAE5/1jgfXvCXOn5GoIAT1CJGUxHVJD+qw5QW1HOqKJ/
so7mkyNdBUrstuHfG24brc/xG0xPKbWowAGJCEKSSA/HOqfXs/lB8mkgBNOPqRwS
nB18joeSmJqUbCVZtsWeZ9ZiTmqLORwcQxpXD+/RDVmBem1QEEe20IOXSoyC6u0l
MS23zQJ599aY+Unc7a7Sa7VZDMtO3HJAUl28vO44x6sBquGvLg9+46D6jojCd1QJ
Vro1f+lvaPr/fAEBvoLhgwL+oShvY7qpOwaxO+6qDfsTtZ/6aj8VX/AIr2H8CAk=
=3Uif
-----END PGP SIGNATURE-----

--Apple-Mail=_6413B3E0-C490-45AF-8FD8-C9F278997582--

From lars@netapp.com  Fri Feb  7 13:05:32 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC7CC1A0428 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 13:05:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.535, 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 Difp5LJSd7rt for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 13:05:31 -0800 (PST)
Received: from mx11.netapp.com (mx11.netapp.com [216.240.18.76]) by ietfa.amsl.com (Postfix) with ESMTP id 5822D1A01E3 for <ietf@ietf.org>; Fri,  7 Feb 2014 13:05:31 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.95,802,1384329600";  d="asc'?scan'208";a="100749614"
Received: from vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) by mx11-out.netapp.com with ESMTP; 07 Feb 2014 13:05:31 -0800
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.211]) by vmwexceht01-prd.hq.netapp.com ([10.106.76.239]) with mapi id 14.03.0123.003; Fri, 7 Feb 2014 12:57:41 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: Dave Crocker <dcrocker@bbiw.net>
Subject: Re: Revision to Note Well
Thread-Topic: Revision to Note Well
Thread-Index: AQHPI29lDICETuQWaU6hgge24FM4c5qpJF8AgADRnwCAAHhcgIAAX1oA
Date: Fri, 7 Feb 2014 20:57:40 +0000
Message-ID: <08516FF9-9AB1-44F7-A104-D29286980B7E@netapp.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F4F8C5.7030200@dcrocker.net>
In-Reply-To: <52F4F8C5.7030200@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.104.60.115]
Content-Type: multipart/signed; boundary="Apple-Mail=_06F40FBC-DAE3-455C-84FD-3CFED0D79F9E"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.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: Fri, 07 Feb 2014 21:05:33 -0000

--Apple-Mail=_06F40FBC-DAE3-455C-84FD-3CFED0D79F9E
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Hi,

On 2014-2-7, at 16:16, Dave Crocker <dhc@dcrocker.net> wrote:
> On 2/7/2014 12:05 AM, Eggert, Lars wrote:
>> Exactly. The new text does not address the issue.
>>=20
>> Lars
>>=20
>> PS: I'll again point to the IRTF statement, which =
does:http://irtf.org/ipr. We'll make it available to the IETF for the =
low, low price of a round of beers for the IRSG:-)
>=20
> 1. Has the text been vetted by the IETF's attorney?

yes.

> 2. How does this 'summary' avoid the danger that has been cited, of =
providing a potential ambiguity argument through exploitation of any =
differences between the summary source text?

Not sure how to answer that, other than saying that Jorge was OK with =
it? (It does point at the BCP for the detailed rules.)

> 3. How does any of this resolve the much deeper problem that this =
lengthy thread has served to demonstrate that we very clearly have =
extensive community confusion about on what the current IPR rules are or =
mean?

It doesn't - that's a much broader question, which I agree we need to =
somehow tackle.

Lars

--Apple-Mail=_06F40FBC-DAE3-455C-84FD-3CFED0D79F9E
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-----

iQCVAwUBUvVIw9ZcnpRveo1xAQLf6AQApWL1ROVRUXyF9SZljom/spcoQv1ufw3e
JfXN9w8cd5GJgx1Xsh+WlF1ivmNddxvor5WherboKS169zJtztJ6wZJRqFGvdCRk
sbgbeaxlPA0PTdLECmNTQHxaAu4XjUyrAe8LmydvM857bfa+mqFjIHFWwvXGmZtp
ZQOjQzkV/O4=
=QQLZ
-----END PGP SIGNATURE-----

--Apple-Mail=_06F40FBC-DAE3-455C-84FD-3CFED0D79F9E--

From agenda@ietf.org  Fri Feb  7 14:58:21 2014
Return-Path: <agenda@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 5089C1AD694; Fri,  7 Feb 2014 14:58:21 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ppwdLqkueE1h; Fri,  7 Feb 2014 14:58:19 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6288E1AD687; Fri,  7 Feb 2014 14:58:19 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Agenda <agenda@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: IETF 89 Final Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140207225819.10526.35592.idtracker@ietfa.amsl.com>
Date: Fri, 07 Feb 2014 14:58:19 -0800
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: IETF Agenda <agenda@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, 07 Feb 2014 22:58:21 -0000

89th IETF Meeting - London, England
March 2 - 7, 2014

The final agenda has been posted.

https://datatracker.ietf.org/meeting/89/agenda.html
https://datatracker.ietf.org/meeting/89/agenda.txt

While this is considered the final agenda for printing, changes may be made to the agenda up until and during the meeting. Updates will be reflected on the web version of the agenda. 

Information about the 89th IETF meeting in London, England can be found here: https://www.ietf.org/meeting/89/index.html

Thank you and see you in London!

Sincerely,

The IETF Secretariat

From dhc@dcrocker.net  Fri Feb  7 15:33: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 6D8241AD68A for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 15:33:30 -0800 (PST)
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 CrpbiUAnjwkg for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 15:33:29 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1C8A61AD6A4 for <ietf@ietf.org>; Fri,  7 Feb 2014 15:33:29 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s17NXPZi009073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Fri, 7 Feb 2014 15:33:29 -0800
Message-ID: <52F56D21.9090602@dcrocker.net>
Date: Fri, 07 Feb 2014 15:32:49 -0800
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.3.0
MIME-Version: 1.0
To: IETF discussion list <ietf@ietf.org>
Subject: Re: Revision to Note Well
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com>
In-Reply-To: <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@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]); Fri, 07 Feb 2014 15:33:29 -0800 (PST)
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, 07 Feb 2014 23:33:30 -0000

On 2/7/2014 10:39 AM, Scott Brim wrote:
> I'm concerned that any abbreviated form will inadequately represent
> the nuances of the full policy, and that if we create a single uniform
> abbreviated version that must be shown at f2f meetings, that opens
> loopholes.

Exactly.  Any form of redundancy -- like a 'summary' -- creates an 
opportunity for misunderstanding.

Also let's be careful about the nature of the problem here.  Some folks 
want to find an excuse to avoid the responsibility the IETF is imposing. 
  Such folk will not be satisfied, no matter what we do.

Some other folk really do need legitimate guidance.  While I'd argue 
that anyone who misunderstands the basic nature of IETF policy, after 
seeing/hearing the existing Note Well, is probably working at that 
misunderstanding.

Still, we could make things both simpler and stronger.


Here's what I suggest:



                            NOTE WELL

      PARTICIPATION IN THE IETF CARRIES ESSENTIAL OBLIGATIONS.

      IT IS YOUR RESPONSIBILITY TO BECOME FAMILIAR WITH THE DETAILS OF
      THOSE OBLIGATIONS AND TO ENSURE THAT YOU SATISFY THEM:

      *  IETF IPR Disclosures Policy, as specified in BCP 79

      *  IETF Anti-harassment Policy, as specified in
         ietf.org/iesg/statement/ietf-anti-harassment-policy.html



In each case these need to be a single pointer to to a single document.


Of course, Jorge needs to vet this, but I believe this accomplishes only 
and exactly the stated goal, with none of the problems created by 
current or other proposed text.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From christer.holmberg@ericsson.com  Fri Feb  7 15:42:09 2014
Return-Path: <christer.holmberg@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 D072A1AD682 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 15:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.851
X-Spam-Level: 
X-Spam-Status: No, score=-3.851 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, 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 pt22-rF7W3rT for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 15:42:08 -0800 (PST)
Received: from mailgw2.ericsson.se (mailgw2.ericsson.se [193.180.251.37]) by ietfa.amsl.com (Postfix) with ESMTP id D9C521A0566 for <ietf@ietf.org>; Fri,  7 Feb 2014 15:42:07 -0800 (PST)
X-AuditID: c1b4fb25-b7f038e000005d01-0c-52f56f4e18d3
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw2.ericsson.se (Symantec Mail Security) with SMTP id 48.5A.23809.E4F65F25; Sat,  8 Feb 2014 00:42:07 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.02.0387.000; Sat, 8 Feb 2014 00:42:05 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, IETF discussion list <ietf@ietf.org>
Subject: RE: Revision to Note Well
Thread-Topic: Revision to Note Well
Thread-Index: AQHPJF0OPgILfSAQz0q+WzBtDNHZ5ZqqcrMY
Date: Fri, 7 Feb 2014 23:42:05 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D163AC6@ESESSMB209.ericsson.se>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com>, <52F56D21.9090602@dcrocker.net>
In-Reply-To: <52F56D21.9090602@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrHLMWRmVeSWpSXmKPExsUyM+Jvja5//tcgg//pFr8/fWCzeLZxPosD k8elnSfZPJYs+ckUwBTFZZOSmpNZllqkb5fAlbHhr0zBVYGKFQumMTcwfubpYuTkkBAwkTi2 +Sw7hC0mceHeejYQW0jgEKNEzzOgOBeQvYhR4se5NUAJDg42AQuJ7n/aIDUiAsESl040MILY wgJKEvPPnGCDiCtLHDhznBXCNpI4s/InmM0ioCKxc/pdMJtXwFfix7EPTBDzHzBJrDx6iQkk wSmgI7FsyWZmEJsR6KDvp9aAxZkFxCVuPZnPBHGogMSSPeeZIWxRiZeP/7FC2IoSH1/tY4So 15FYsPsTG4StLbFs4WtmiMWCEidnPmGZwCg6C8nYWUhaZiFpmYWkZQEjyypG9tzEzJz0cqNN jMA4OLjlt+oOxjvnRA4xSnOwKInzfnjrHCQkkJ5YkpqdmlqQWhRfVJqTWnyIkYmDU6qB0cfX em+eV83tNaqvHt98VMr60zf67ft3KwPTjRYXbVGNcP8X0F7dxKA/+/jh8+W1Ifcv3lgvtm6G 1H/3UAmeELbqjaauguvcpwXmbFm6Y57SzKNrv/5edkz27XK1lAbxk97S5xYFvpilZV9UIduu 4yVUnpkds0zTOGlJ6r2abpV7JtK9bW+tlViKMxINtZiLihMBy7m6+lECAAA=
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2014 23:42:10 -0000

Hi,

I think the text that Dave suggests looks good.

However, it's probably good to have a link to where the meaning of "Partici=
pation" is defined, because that discussion also comes up every now and the=
n...

Regards,

Christer

________________________________________
From: ietf [ietf-bounces@ietf.org] on behalf of Dave Crocker [dhc@dcrocker.=
net]
Sent: Saturday, 08 February 2014 1:32 AM
To: IETF discussion list
Subject: Re: Revision to Note Well

On 2/7/2014 10:39 AM, Scott Brim wrote:
> I'm concerned that any abbreviated form will inadequately represent
> the nuances of the full policy, and that if we create a single uniform
> abbreviated version that must be shown at f2f meetings, that opens
> loopholes.

Exactly.  Any form of redundancy -- like a 'summary' -- creates an
opportunity for misunderstanding.

Also let's be careful about the nature of the problem here.  Some folks
want to find an excuse to avoid the responsibility the IETF is imposing.
  Such folk will not be satisfied, no matter what we do.

Some other folk really do need legitimate guidance.  While I'd argue
that anyone who misunderstands the basic nature of IETF policy, after
seeing/hearing the existing Note Well, is probably working at that
misunderstanding.

Still, we could make things both simpler and stronger.


Here's what I suggest:



                            NOTE WELL

      PARTICIPATION IN THE IETF CARRIES ESSENTIAL OBLIGATIONS.

      IT IS YOUR RESPONSIBILITY TO BECOME FAMILIAR WITH THE DETAILS OF
      THOSE OBLIGATIONS AND TO ENSURE THAT YOU SATISFY THEM:

      *  IETF IPR Disclosures Policy, as specified in BCP 79

      *  IETF Anti-harassment Policy, as specified in
         ietf.org/iesg/statement/ietf-anti-harassment-policy.html



In each case these need to be a single pointer to to a single document.


Of course, Jorge needs to vet this, but I believe this accomplishes only
and exactly the stated goal, with none of the problems created by
current or other proposed text.


d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From farmer@umn.edu  Fri Feb  7 19:57:46 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 AC4D01A05A3 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 19:57:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.735
X-Spam-Level: 
X-Spam-Status: No, score=-4.735 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oYrSZGUe52QL for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 19:57:45 -0800 (PST)
Received: from vs-a.tc.umn.edu (vs-a.tc.umn.edu [134.84.135.107]) by ietfa.amsl.com (Postfix) with ESMTP id 0A1F81A0349 for <ietf@ietf.org>; Fri,  7 Feb 2014 19:57:44 -0800 (PST)
Received: from mail-ie0-f170.google.com (mail-ie0-f170.google.com [209.85.223.170]) by vs-a.tc.umn.edu (UMN smtpd) with ESMTP for <ietf@ietf.org>; Fri, 7 Feb 2014 21:57:39 -0600 (CST)
X-Umn-Remote-Mta: [N] mail-ie0-f170.google.com [209.85.223.170] #+LO+TS+TR
X-Umn-Classification: local
Received: by mail-ie0-f170.google.com with SMTP id u16so2297840iet.29 for <ietf@ietf.org>; Fri, 07 Feb 2014 19:57:38 -0800 (PST)
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=/LKEV7ntym8knwV0yLFI3v8qWJu0eUTlFMpp0Y8tiz4=; b=bExFLmFVIELa6xLyvWy8FLr+CQGyeM4tSKtf+s++0piFwr+E7pkYGfVO/lcFt2XVcm t9ZrFxTYroUfrAK/su7JfiZn/lAoe0cg0Wqp/kqSi37wuQLfXLHW1OYax51slbiW031e NWCfTHTD6dzp1vEhmRfDsjPIwak/VT+NWpwPNosjoJ24dUObu2AejNFn0QIqYvakSo5F xitWgsB/xfPrR37C5CYpbWG2d3A/liaONs9ZZI9gqVgCihRMC0vpY90vOKqjcIT3+v3T Q9b1q7xV2QgvDyMV7LxGpRzhBh7MzGBaZKofYFt2kAz434ZNIcE9V0tyPL98QXRDLYL0 sO0w==
X-Gm-Message-State: ALoCoQl+8ytcLl7Ye3sGgz6KwOFM4rHO6mh49hMNF3VV6gY3cSExndvXW74cnNrHJZun8GejtqlGZ9flMRIqGli8XClbLMAwpxsvARjoQhXti7JbRFk3pMyaQfnxnVPVg42U3UOd7ugO
X-Received: by 10.43.171.194 with SMTP id nv2mr10174500icc.7.1391831858862; Fri, 07 Feb 2014 19:57:38 -0800 (PST)
X-Received: by 10.43.171.194 with SMTP id nv2mr10174491icc.7.1391831858708; Fri, 07 Feb 2014 19:57:38 -0800 (PST)
Received: from x-134-84-88-50.nts.umn.edu ([2607:ea00:101:2001:ec5d:6b7d:87c0:6647]) by mx.google.com with ESMTPSA id t4sm16711073igm.10.2014.02.07.19.57.36 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Feb 2014 19:57:37 -0800 (PST)
Message-ID: <52F5AB2F.2060401@umn.edu>
Date: Fri, 07 Feb 2014 21:57:35 -0600
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.2.0
MIME-Version: 1.0
To: Russ Housley <housley@vigilsec.com>
Subject: Re: Last Call: <draft-housley-number-registries-02.txt> (Internet Numbers Registries) to Informational RFC
References: <20131216175534.1390.8446.idtracker@ietfa.amsl.com> <07d701cf1547$782166f0$686434d0$@olddog.co.uk> <323768A6-88D0-4012-A48C-C112E98A4112@vigilsec.com> <028c01cf1a0a$048899d0$0d99cd70$@olddog.co.uk> <52E6D628.80103@umn.edu> <7DA9D44B-1B9D-43BE-B41D-290684A41972@vigilsec.com> <52F0478D.2020701@umn.edu> <9162EF70-3F2A-4C5D-B744-7C65D4FE16B6@vigilsec.com>
In-Reply-To: <9162EF70-3F2A-4C5D-B744-7C65D4FE16B6@vigilsec.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: IETF <ietf@ietf.org>
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: Sat, 08 Feb 2014 03:57:46 -0000

On 2/7/14, 09:52 , Russ Housley wrote:
> I am posting an update that includes some of your comments.  If a document comes along that defines a special-purpose AS number registry before this document becomes and RFC, I wouldgladly reference it.  If not, such a document can revise the registry that this document establishes.
>
> Russ

I have no objection to that.

As for the -04 revision, I'd prefer to see 
[draft-ietf-idr-last-as-reservation] as the reference for AS65535 in the 
table and not [RFC1930].  Another option, less preferred by me, is to 
reference both [draft-ietf-idr-last-as-reservation] and [RFC1930] for 
AS65535.  By the way, draft-ietf-idr-last-as-reservation successfully 
completed WGLC in IDR.

While it is true that RFC1930 reserved AS65535, the text of RFC1930, 
section 10, identifies AS65535 as part of the Private Use range. 
However, the IANA AS Numbers registry had listed AS65535 separately from 
that range for sometime, well before RFC6996, and maybe back to RFC1997 
or even before RFC1930, I don't know for sure.  RFC1997 indirectly uses 
AS65535 for the well-known BGP communities.  RFC6996 updates that part 
of RFC1930 to clarify that AS65535 is not properly part of the Private 
Use range.  Then draft-ietf-idr-last-as-reservation will clarify the 
purpose of and formalizes the reservations for both AS65535 and 
AS4294967295, and discusses RFC1997's use of AS65535.

I did a some searching for any other ASNs specified for a 
special-purposes in RFCs, the only thing I found that isn't already 
covered is; RFC6304, which specifies the use of AS112 to provide a 
distributed sink for DNS reverse queries of RFC1918 blocks and other 
similar queries.  However, since the IPv4 prefix also specified isn't 
listed in the IANA IPv4 Special-Purpose Address Registry, I don't think 
its necessary to list the ASN either.  But, I thought I would mention it 
just in case someone feels differently.

Finally, should the Abstract and Introduction also include the fact that 
the IANA Special-Purpose AS Numbers Registry is established by this 
document.

Thanks

-- 
================================================
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 cntreras@gmail.com  Fri Feb  7 20:34:44 2014
Return-Path: <cntreras@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 CE04E1A0354 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 20:34:44 -0800 (PST)
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 gWBnFYftqPqS for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 20:34:42 -0800 (PST)
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 E8D291A034F for <ietf@ietf.org>; Fri,  7 Feb 2014 20:34:41 -0800 (PST)
Received: by mail-ee0-f49.google.com with SMTP id d17so1864151eek.22 for <ietf@ietf.org>; Fri, 07 Feb 2014 20:34:41 -0800 (PST)
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=UaN2Wp5OfRsd73kTUdx4gsZPq8P9XznJnqYQBvpcjto=; b=ijwCQvGiCK2KFv5oEEPeeT0WIh0ltBjYpDChZ5fuJPUbi03AmbMrIW7rPKiaHDfy+f SSbRvSyiOsivm7+6mRCKgmCKqJCflfUlGTkQ6UbG3UfDH3bjue09D+QJuqhjgoPCajZl d5z3+Id2HuSEr906dsgJ4d2/Bn/xjW2NYx9whEgsiRGgaMYmYYgzPa583DG3YImCPAn+ iNF3qq2SvNQHg6jhsZH7JcJjGzBoj91X7nFOkVAPJenPS53IIUevhy6I0QQwWaacCHlr Mq3DZr/o15sCzJIm/MwqPXcbq7V4F6A8//9XPLRX01UcPCVq5KEIPNGnX37Y253DkV6N cD4A==
MIME-Version: 1.0
X-Received: by 10.15.26.199 with SMTP id n47mr20844009eeu.30.1391834081127; Fri, 07 Feb 2014 20:34:41 -0800 (PST)
Received: by 10.14.108.72 with HTTP; Fri, 7 Feb 2014 20:34:41 -0800 (PST)
In-Reply-To: <3F608B59-7C5E-4FDA-B09A-EF7F801EBC6A@sobco.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com> <78070B4D-C747-46AD-8ECF-75F3E240E922@sobco.com> <3F608B59-7C5E-4FDA-B09A-EF7F801EBC6A@sobco.com>
Date: Fri, 7 Feb 2014 22:34:41 -0600
Message-ID: <CAP0PwYa1wrgBnoOionuW0M9vUE_C+-Wwg4PU_3aJmgnyjSf69w@mail.gmail.com>
Subject: Re: Revision to Note Well (some history) - updated
From: Jorge Contreras <cntreras@gmail.com>
To: "Scott O. Bradner" <sob@sobco.com>
Content-Type: multipart/alternative; boundary=089e01681bfefdf11a04f1dd9f0c
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: Sat, 08 Feb 2014 04:34:45 -0000

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

This is essentially a repeat of a discussion that has happened every few
years since the late 1990s.  The original idea for the Note Well (at least
*my* original idea) was that it should simply be a pointer to the IETF IPR
policy, which has many pages of explanation and answers most of the
questions that people have been raising on this thread.  It should be
obvious, I think, that a complex process like the IETF's IPR disclosure
procedure can't be fully explained in a couple of sentences.  Any such
attempt is bound to be incomplete.

This being said, there has been a strong desire by many to have a summary
statement that also serves as a pointer to the real policy.  That's what
the current Note Well is supposed to be.  It is NOT a statement of the
IETF's IPR rules.  Those are contained in BCP 78/79, and anyone who is
responsible for his/her company's IPR and/or compliance needs to read those
and not rely on the summary statement/pointer contained in Note Well.

Jorge


On Fri, Feb 7, 2014 at 1:46 PM, Scott O. Bradner <sob@sobco.com> wrote:

> oops - reviewing my logs, it was Jorge Contreras not Geoff Stewart, and
> John Klensin was part of
> the initial (to blame) group
>
> Scott
>
> On Feb 7, 2014, at 2:43 PM, Scott O. Bradner <sob@sobco.com> wrote:
>
> > something that is being missed in this discussion
> >
> > the old "Note Well" does not do, nor was it intended to do, what people
> have assumed it did
> >
> > the Note Well was developed, starting in about April 2000, to provide
> classification
> > on what should be considered a "contribution" to the IETF - at the time
> there
> > was a lot of confusion - some people thought the 2026 IPR rules only
> applied to
> > Internet Draft submission and others thought it covered mailing list and
> > microphone statements - the Note Well was developed by me and the then
> IETF lawyer,
> > Geoff Stewart, with the help of Steve Coya and initially discussed at an
> IESG retreat.
> >
> > a common feature of the proposed revisions (the IERTF one as well as the
> IESG ones)
> > is to expand the mission of the Note Well to actually say what you
> should DO if you
> > have IPR that an IETF working group would be better off knowing about
> >
> > note well that the above is a history lesson for context and should not
> discus the
> > current discussion thread other than to perhaps forestall a return to
> the good old
> > Note Well that was not, by itself, actionable
> >
> > Scott
> >
> > On Feb 7, 2014, at 1:39 PM, Scott Brim <scott.brim@gmail.com> wrote:
> >
> >> I'm concerned that any abbreviated form will inadequately represent
> >> the nuances of the full policy, and that if we create a single uniform
> >> abbreviated version that must be shown at f2f meetings, that opens
> >> loopholes. For example, possibly: "Well, yes I agreed to the Note
> >> Well, but then in the meeting they showed a different version that
> >> didn't cover X. I thought that took precedence."
> >>
> >> There are many ways the full Note Well is dealt with at this time,
> >> most of them good. I don't think you'll get more attention paid to the
> >> IPR policy by showing an abbreviated form.
> >>
> >> Scott
> >
>
>

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

<div dir=3D"ltr">This is essentially a repeat of a discussion that has happ=
ened every few years since the late 1990s. &nbsp;The original idea for the =
Note Well (at least *my* original idea) was that it should simply be a poin=
ter to the IETF IPR policy, which has many pages of explanation and answers=
 most of the questions that people have been raising on this thread. &nbsp;=
It should be obvious, I think, that a complex process like the IETF&#39;s I=
PR disclosure procedure can&#39;t be fully explained in a couple of sentenc=
es. &nbsp;Any such attempt is bound to be incomplete. &nbsp;<div>
<br></div><div>This being said, there has been a strong desire by many to h=
ave a summary statement that also serves as a pointer to the real policy. &=
nbsp;That&#39;s what the current Note Well is supposed to be. &nbsp;It is N=
OT a statement of the IETF&#39;s IPR rules. &nbsp;Those are contained in BC=
P 78/79, and anyone who is responsible for his/her company&#39;s IPR and/or=
 compliance needs to read those and not rely on the summary statement/point=
er contained in Note Well.<div>
<br></div><div>Jorge</div></div></div><div class=3D"gmail_extra"><br><br><d=
iv class=3D"gmail_quote">On Fri, Feb 7, 2014 at 1:46 PM, Scott O. Bradner <=
span dir=3D"ltr">&lt;<a href=3D"mailto:sob@sobco.com" target=3D"_blank">sob=
@sobco.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">oops - reviewing my logs, it was Jorge Contr=
eras not Geoff Stewart, and John Klensin was part of<br>
the initial (to blame) group<br>
<br>
Scott<br>
<br>
On Feb 7, 2014, at 2:43 PM, Scott O. Bradner &lt;<a href=3D"mailto:sob@sobc=
o.com">sob@sobco.com</a>&gt; wrote:<br>
<br>
&gt; something that is being missed in this discussion<br>
&gt;<br>
&gt; the old &ldquo;Note Well&rdquo; does not do, nor was it intended to do=
, what people have assumed it did<br>
&gt;<br>
&gt; the Note Well was developed, starting in about April 2000, to provide =
classification<br>
&gt; on what should be considered a &ldquo;contribution&rdquo; to the IETF =
- at the time there<br>
&gt; was a lot of confusion - some people thought the 2026 IPR rules only a=
pplied to<br>
&gt; Internet Draft submission and others thought it covered mailing list a=
nd<br>
&gt; microphone statements - the Note Well was developed by me and the then=
 IETF lawyer,<br>
&gt; Geoff Stewart, with the help of Steve Coya and initially discussed at =
an IESG retreat.<br>
&gt;<br>
&gt; a common feature of the proposed revisions (the IERTF one as well as t=
he IESG ones)<br>
&gt; is to expand the mission of the Note Well to actually say what you sho=
uld DO if you<br>
&gt; have IPR that an IETF working group would be better off knowing about<=
br>
&gt;<br>
&gt; note well that the above is a history lesson for context and should no=
t discus the<br>
&gt; current discussion thread other than to perhaps forestall a return to =
the good old<br>
&gt; Note Well that was not, by itself, actionable<br>
&gt;<br>
&gt; Scott<br>
&gt;<br>
&gt; On Feb 7, 2014, at 1:39 PM, Scott Brim &lt;<a href=3D"mailto:scott.bri=
m@gmail.com">scott.brim@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; I&#39;m concerned that any abbreviated form will inadequately repr=
esent<br>
&gt;&gt; the nuances of the full policy, and that if we create a single uni=
form<br>
&gt;&gt; abbreviated version that must be shown at f2f meetings, that opens=
<br>
&gt;&gt; loopholes. For example, possibly: &quot;Well, yes I agreed to the =
Note<br>
&gt;&gt; Well, but then in the meeting they showed a different version that=
<br>
&gt;&gt; didn&#39;t cover X. I thought that took precedence.&quot;<br>
&gt;&gt;<br>
&gt;&gt; There are many ways the full Note Well is dealt with at this time,=
<br>
&gt;&gt; most of them good. I don&#39;t think you&#39;ll get more attention=
 paid to the<br>
&gt;&gt; IPR policy by showing an abbreviated form.<br>
&gt;&gt;<br>
&gt;&gt; Scott<br>
&gt;<br>
<br>
</blockquote></div><br></div>

--089e01681bfefdf11a04f1dd9f0c--

From john-ietf@jck.com  Fri Feb  7 22:48:23 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 0CDB51ADE85 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 22:48:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.135
X-Spam-Level: 
X-Spam-Status: No, score=-3.135 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.535] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qyFCiFSLZoyn for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 22:48:21 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2CBD91A05A8 for <ietf@ietf.org>; Fri,  7 Feb 2014 22:48:21 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WC1i5-0000uw-Rg; Sat, 08 Feb 2014 01:48:17 -0500
Date: Sat, 08 Feb 2014 01:48:12 -0500
From: John C Klensin <john-ietf@jck.com>
To: Jorge Contreras <cntreras@gmail.com>, "Scott O. Bradner" <sob@sobco.com>
Subject: Re: Revision to Note Well (some history) - updated
Message-ID: <013CF4B3553CB72AC1FE8D74@JcK-HP8200.jck.com>
In-Reply-To: <CAP0PwYa1wrgBnoOionuW0M9vUE_C+-Wwg4PU_3aJmgnyjSf69w@mail.gmail.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com> <78070B4D-C747-46AD-8ECF-75F3E240E922@sobco.com> <3F608B59-7C5E-4FDA-B09A-EF7F801EBC6A@sobco.com> <CAP0PwYa1wrgBnoOionuW0M9vUE_C+-Wwg4PU_3aJmgnyjSf69w@mail.gmail.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
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: Sat, 08 Feb 2014 06:48:23 -0000

--On Friday, February 07, 2014 22:34 -0600 Jorge Contreras
<cntreras@gmail.com> wrote:

> This is essentially a repeat of a discussion that has happened
> every few years since the late 1990s.  The original idea for
> the Note Well (at least *my* original idea) was that it should
> simply be a pointer to the IETF IPR policy, which has many
> pages of explanation and answers most of the questions that
> people have been raising on this thread.  It should be
> obvious, I think, that a complex process like the IETF's IPR
> disclosure procedure can't be fully explained in a couple of
> sentences.  Any such attempt is bound to be incomplete.

And that, of course, reprises most of the late 1990s (or
thereabouts) discussion to which Scott refers.  We also
discussed two other things that have come up on this most recent
thread in slightly different form:

* The enforceability risks inherent in what we referred to in
that conversation as a "shrink wrap" license, i.e., a "you are
sitting here and hence you have agreed" situation.   My
recollection is that these various notices and reminders
scattered around the registration process, mailing lists, etc.,
arose from that part of the conversation and were attempts to be
able to get a slightly stronger and more defensible agreement.

* The question of whether, if we provided a superficial summary,
someone could argue that it was the "real" agreement or that it
was all they had agreed to, thereby creating loopholes in an
otherwise complex, but carefully explained, policy.

> This being said, there has been a strong desire by many to
> have a summary statement that also serves as a pointer to the
> real policy.  That's what the current Note Well is supposed to
> be.  It is NOT a statement of the IETF's IPR rules.  Those are
> contained in BCP 78/79, and anyone who is responsible for
> his/her company's IPR and/or compliance needs to read those
> and not rely on the summary statement/pointer contained in
> Note Well.

But, again, that is a reprise of a very old discussion and,
based in large measure on that discussion, represents a tradeoff
between the desire for and advantages of such a summary and the
risks of someone being able to successfully claim that, despite
our intentions, the summary really is the policy.  It seems to
me --from a public policy perspective, not a legal one-- that
the more the summary departs from or exaggerates the actual
rules, the greater that risk becomes.  The latter was, IMO, the
main objection to the IESG's proposed change (and to Pete's "ask
for more than the policy actually requires" formulation in
particular) this time, but it seems to me that trimming things
back to a different summary still doesn't solve the potential
problem even if it might improve the risk-benefit ratio.

    john



> On Fri, Feb 7, 2014 at 1:46 PM, Scott O. Bradner
> <sob@sobco.com> wrote:
> 
>> oops - reviewing my logs, it was Jorge Contreras not Geoff
>> Stewart, and John Klensin was part of
>> the initial (to blame) group





From rpelletier@isoc.org  Sat Feb  8 03:02:51 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 9DAA91A05EF; Sat,  8 Feb 2014 03:02:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.602
X-Spam-Level: 
X-Spam-Status: No, score=-102.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, 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 4bsw4M4E-Cfp; Sat,  8 Feb 2014 03:02:49 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2lp0242.outbound.protection.outlook.com [207.46.163.242]) by ietfa.amsl.com (Postfix) with ESMTP id 036A11A01FB; Sat,  8 Feb 2014 03:02:49 -0800 (PST)
Received: from [192.168.0.19] (69.131.53.114) by BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20) with Microsoft SMTP Server (TLS) id 15.0.868.8; Sat, 8 Feb 2014 11:02:46 +0000
Content-Type: text/plain; charset="windows-1252"
Subject: Fwd: IPR Tool SOW for Community Input
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ray Pelletier <rpelletier@isoc.org>
Date: Sat, 8 Feb 2014 06:02:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <D8CA518B-88FA-4C52-81BF-195D5FA28FE5@isoc.org>
References: <20140204203441.10232.96698.idtracker@ietfa.amsl.com>
To: "iab@iab.org IAB" <iab@iab.org>, ietf Discussion <ietf@ietf.org>, The IESG <iesg@ietf.org>, Working Group Chairs <wgchairs@ietf.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [69.131.53.114]
X-ClientProxiedBy: BLUPR08CA019.namprd08.prod.outlook.com (10.141.30.39) To BY2PR06MB234.namprd06.prod.outlook.com (10.242.47.20)
X-Forefront-PRVS: 01165471DB
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6049001)(6009001)(377454003)(199002)(189002)(51704005)(2473001)(87286001)(85306002)(87266001)(43066001)(87976001)(36756003)(83716003)(77156001)(47776003)(74706001)(77096001)(76796001)(79102001)(76786001)(46102001)(65816001)(66066001)(80022001)(74366001)(93516002)(74502001)(76482001)(94316002)(94946001)(93916002)(86362001)(57306001)(80976001)(56776001)(59766001)(33656001)(54316002)(19580405001)(19580395003)(42186004)(51856001)(77982001)(90146001)(23746002)(50466002)(83322001)(47446002)(69226001)(47976001)(50986001)(88136002)(74876001)(85852003)(83072002)(81342001)(81542001)(50226001)(4396001)(74662001)(47736001)(93136001)(49866001)(63696002)(89996001)(56816005)(81686001)(81816001)(82746002)(92726001)(62966002)(95416001)(24704002)(387614004); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR06MB234; H:[192.168.0.19]; CLIP:69.131.53.114; FPR:A8D440EC.981397D1.39FFA586.D8E6C15D.20310; InfoNoRecordsA:1; MX:1; LANG:en; 
X-OriginatorOrg: isoc.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: Sat, 08 Feb 2014 11:02:51 -0000

Begin forwarded message:

> From: IETF Administrative Director <iad@ietf.org>
> Subject: IPR Tool SOW for Community Input
> Date: February 4, 2014 at 3:34:41 PM EST
> To: IETF Announcement List <ietf-announce@ietf.org>
> Reply-To: <ietf@ietf.org>
>=20
> Based upon community and IESG requests, the IAOC intends to seek bids =
on a revision to the IPR Tool=20
> and desires community input on a  draft IPR Tool Statement of Work.  =
The SOW is located here: =20
> <http://iaoc.ietf.org/rfps.html>.
>=20
> The community comment period ends 17 February 2014.  The IAOC will =
consider all comments received=20
> during this period.
>=20
> The IETF desires to improve the IPR component of the datatracker to =
remove or better isolate artifacts=20
> from earlier implementations, allow submitters to update more than one =
disclosure at a time, and better=20
> support the IETF Secretariat=92s administrative actions.
>=20
> Deliverables include:
> 1	Provide existing functionality using revised models (except =
where the functionality is being=20
> 	changed by the remaining deliverables)
> 2	Migrate existing data to new models
> 3	Provide full admin interface support for the new models, with =
reasonable configurations for=20
> 	list_display, search_field, ordering, etc.
> 4	Improve the Secretariat=92s navigation between IPR document =
views/search results and the=20
> 	administrative pages to edit IPR documents.
> 5	Add the ability for a disclosure submission to indicate it is =
updating more than one existing=20
> 	disclosure.
> 6	Improve the Secretariat=92s management interface for the waiting =
for approval queue, including=20
> 	adding the ability to park disclosures that are waiting for =
approval.
> 7	Add a Secretariat management interface for rejected and removed =
disclosures.=20
> 8	Implement simplified forms for Secretariat updates to a =
disclosure.=20
> 9	Add the ability to manage email communication necessary for =
processing a submission.=20
>=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


From rpelletier@isoc.org  Sat Feb  8 03:04:07 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 69B791A05FA; Sat,  8 Feb 2014 03:04:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.902
X-Spam-Level: 
X-Spam-Status: No, score=-101.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, 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 EAnT3majDjTo; Sat,  8 Feb 2014 03:04:05 -0800 (PST)
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 34F3E1A00B4; Sat,  8 Feb 2014 03:04:05 -0800 (PST)
Received: from [192.168.0.19] (69.131.53.114) by BN1PR06MB231.namprd06.prod.outlook.com (10.242.215.143) with Microsoft SMTP Server (TLS) id 15.0.873.15; Sat, 8 Feb 2014 11:04:01 +0000
Content-Type: text/plain; charset="windows-1252"
Subject: Fwd: IETF Returning to Berlin for IETF 96
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Ray Pelletier <rpelletier@isoc.org>
Date: Sat, 8 Feb 2014 06:03:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <3ABBBE55-4365-41B7-90E2-71B72066D4CC@isoc.org>
References: <20140204181027.11643.12019.idtracker@ietfa.amsl.com>
To: ietf Discussion <ietf@ietf.org>, Working Group Chairs <wgchairs@ietf.org>,  The IESG <iesg@ietf.org>, "iab@iab.org IAB" <iab@iab.org>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [69.131.53.114]
X-ClientProxiedBy: BLUPR07CA034.namprd07.prod.outlook.com (10.141.20.49) To BN1PR06MB231.namprd06.prod.outlook.com (10.242.215.143)
X-Forefront-PRVS: 01165471DB
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019001)(6049001)(6009001)(199002)(189002)(2473001)(51704005)(377454003)(83716003)(88136002)(74706001)(74876001)(50466002)(36756003)(50986001)(49866001)(47736001)(47976001)(80022001)(65816001)(87286001)(87266001)(63696002)(79102001)(57306001)(47776003)(66066001)(77156001)(87976001)(4396001)(77982001)(50226001)(74366001)(59766001)(77096001)(76796001)(76786001)(56776001)(54316002)(81342001)(95416001)(19580395003)(19580405001)(83322001)(85852003)(83072002)(93916002)(86362001)(80976001)(94946001)(46102001)(69226001)(82746002)(23746002)(76482001)(47446002)(81542001)(42186004)(74502001)(51856001)(92726001)(94316002)(81816001)(43066001)(74662001)(81686001)(89996001)(90146001)(93136001)(56816005)(85306002)(33656001)(62966002)(93516002)(24704002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN1PR06MB231; H:[192.168.0.19]; CLIP:69.131.53.114; FPR:FC87F5ED.AA7A9790.33D39DB3.7DAE1C1.20446; InfoNoRecordsA:1; MX:1; LANG:en; 
X-OriginatorOrg: isoc.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: Sat, 08 Feb 2014 11:04:07 -0000

Begin forwarded message:

> From: IETF Administrative Director <iad@ietf.org>
> Subject: IETF Returning to Berlin for IETF 96
> Date: February 4, 2014 at 1:10:27 PM EST
> To: IETF Announcement List <ietf-announce@ietf.org>
> Reply-To: <ietf@ietf.org>
>=20
> The IAOC is pleased to announce the IETF will be returning to Berlin =
for IETF 96,=20
> July 17 - 22, 2016.  If you attended IETF 87 in Berlin you were asked =
in the=20
> meeting survey whether you would like to return to the Berlin =
InterContinental for=20
> an IETF meeting.  96% of the respondents said Yes!  We are happy to =
oblige!=20
>=20
> We are looking for a Host and some sponsors for this meeting.  Contact =
Drew=20
> Dvorshak, dvorshak at isoc.org, if you have any interest.
>=20
> Other News - IETFs 95, 96 & 97 in 2016
>=20
> The IAOC adopted a policy that we would select the IETF meeting venues =
three years=20
> in advance.  So, ordinarily we would have made announcements for the =
first 2 of the
> 3 meetings for 2016 in 2013, but 2013 turned out to be a challenging =
year for=20
> contracting.  The target regions for 2016 were Europe, the Americas, =
and Asia in that
> order, and work began early in the year to identify and qualify venues =
for those=20
> regions.  Typically, arrangements for the third meeting carry over =
into the first=20
> quarter of the next year. =20
>=20
> There was interest in having an IETF meeting in Latin America. Due =
diligence=20
> included a site visit there in late February, followed by a Meetings =
Committee and=20
> IAOC review of the feasibility, and a decision to discuss the =
possibility with the=20
> community was made by the IAOC. =20
>=20
> The IAOC authorized negotiations in Buenos Aires to began in earnest =
on 20 June for
> IETF 95 in April 2016 after receiving feedback from the community from =
a survey and=20
> comments on the list.  I wish I could tell you that we have a =
contract.  However,=20
> economic uncertainty in the country, among other things, has made it =
difficult to=20
> close on a deal.  But we are still at it, including looking at other =
options in Buenos=20
> Aires.=20
>=20
> Moving the Americas to April meant we needed to move Europe to July =
2016.  The=20
> successful meeting in Berlin and the attendees strong desire to return =
greatly=20
> influenced the decision to return.  However, we could not close on a =
contract with the
> hotel until all the VAT administrative work was completed and that =
didn=92t happen=20
> until 19 December.
>=20
> As for Asia I expect we will have something to announce at or before =
IETF 90 in=20
> Toronto. =20
>=20
> Only 26 days until IETF 89 in London!  Register here:=20
> <https://www.ietf.org/meeting/89/index.html>.=20
>=20
> See you there!
>=20
> Ray Pelletier
> IETF Administrative Director
>=20
> 2014
>=20
> IETF 89  London  Hilton Metropole  March 2 - 7  Host:  ICANN
> IETF 90  Toronto  Fairmont Royal York Hotel  July 20 - 25  Host:  In=20=

> Discussions
> IETF 91  Honolulu  Hilton Hawaiian Village  Nov 9 - 14  Host: Cisco
>=20
> 2015
>=20
> IETF 92  Dallas  March 22 - 27  Host:  Your Name Here
> IETF 93  Prague	  July 19 - 24  Host:  Your Name Here
> IETF 94  Yokohama  Nov 1 - 6  Host:  WIDE


From dhc@dcrocker.net  Sat Feb  8 07:21:58 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 C3AA61A0398 for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 07:21:58 -0800 (PST)
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 0kxsqd9OO4_3 for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 07:21:57 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD641A0339 for <ietf@ietf.org>; Sat,  8 Feb 2014 07:21:57 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s18FLrko003199 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 8 Feb 2014 07:21:56 -0800
Message-ID: <52F64B6C.1090902@dcrocker.net>
Date: Sat, 08 Feb 2014 07:21:16 -0800
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.3.0
MIME-Version: 1.0
To: Jorge Contreras <cntreras@gmail.com>
Subject: Re: Revision to Note Well (some history) - updated
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com> <78070B4D-C747-46AD-8ECF-75F3E240E922@sobco.com> <3F608B59-7C5E-4FDA-B09A-EF7F801EBC6A@sobco.com> <CAP0PwYa1wrgBnoOionuW0M9vUE_C+-Wwg4PU_3aJmgnyjSf69w@mail.gmail.com>
In-Reply-To: <CAP0PwYa1wrgBnoOionuW0M9vUE_C+-Wwg4PU_3aJmgnyjSf69w@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]); Sat, 08 Feb 2014 07:21:56 -0800 (PST)
Cc: IETF discussion list <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, 08 Feb 2014 15:21:59 -0000

On 2/7/2014 8:34 PM, Jorge Contreras wrote:
> The original idea for the Note Well (at least *my* original idea)
> wasthat it should simply be a pointer to the IETF IPR policy
...
> This being said, there has been a strong desire by many to have a
> summary statement that also serves as a pointer to the real policy.
>   That's what the current Note Well is supposed to be.  It is NOT a
> statement of the IETF's IPR rules.


Jorge,

You might have noticed that there is currently also quite a strong
concern by many that the approach that has been taken by the Note Well
invites confusion or, at least, arguments of confusion.

I believe that that line of concern leads to exactly what you originally
proposed.

That's why I just circulated some text that says nothing about the
substance of IETF IPR, but makes strong statements about participant
obligations.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From rlb@ipv.sx  Sat Feb  8 10:47:39 2014
Return-Path: <rlb@ipv.sx>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79ED21A03E6 for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 10:47:39 -0800 (PST)
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 5kboROYZZGdc for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 10:47:37 -0800 (PST)
Received: from mail-oa0-f43.google.com (mail-oa0-f43.google.com [209.85.219.43]) by ietfa.amsl.com (Postfix) with ESMTP id 300BC1A019E for <ietf@ietf.org>; Sat,  8 Feb 2014 10:47:37 -0800 (PST)
Received: by mail-oa0-f43.google.com with SMTP id h16so5808419oag.30 for <ietf@ietf.org>; Sat, 08 Feb 2014 10:47:37 -0800 (PST)
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=GumKIPvDcnQeFEO6fAzunw/yuNVSOPYpY+nBCsHscVk=; b=HKvTBpAZt3Hpt6PC1PivAPJx3U0wA39G7SQFBoKqXudCRYlZtrITH8ldG/Y6rnYCfk RHIjKmbGdDB92cuCGiUS3AgFXxeS1afVCuwg1JPSdpqO60u24Qpc3EN1lJS0IEtpVu7H fBn4Aa04puG2FS406TNhCjhBfJTgq5PL8ygyjZU5TjO505ZEpRxlHdQ74beAFYbeheX8 29+Y85E+giPh8TmONv4nG6mvRPdRD5BuVzI+UsvpPmyRpJLZMBRdWwsbQXqv7978Q3AU 5UNYmjNekeabnycilUESAPlsa59p29UCOUb9324+iZ2AhBGeLhrOoxvIfH/aQHqtcZVe NCjA==
X-Gm-Message-State: ALoCoQmBi8NkEUQie/cJB5VMhkYosHg6ykVHYWMQ93ItfzTLcWLC058Q0tQTD5qeL1bECI5wHe+5
MIME-Version: 1.0
X-Received: by 10.60.74.105 with SMTP id s9mr2528682oev.49.1391885257458; Sat, 08 Feb 2014 10:47:37 -0800 (PST)
Received: by 10.60.69.102 with HTTP; Sat, 8 Feb 2014 10:47:37 -0800 (PST)
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D163AC6@ESESSMB209.ericsson.se>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com> <52F56D21.9090602@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B1D163AC6@ESESSMB209.ericsson.se>
Date: Sat, 8 Feb 2014 13:47:37 -0500
Message-ID: <CAL02cgQjF6-7UuvfYUy_CVMpqJ2SFNoTmh2UQ43mvg=tOn6cNg@mail.gmail.com>
Subject: Re: Revision to Note Well
From: Richard Barnes <rlb@ipv.sx>
To: Christer Holmberg <christer.holmberg@ericsson.com>
Content-Type: multipart/alternative; boundary=001a1134d10056dc8b04f1e98a46
Cc: "dcrocker@bbiw.net" <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: Sat, 08 Feb 2014 18:47:39 -0000

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

How about, "IF YOU ARE SEEING THIS TEXT, THEN YOU ARE A PARTICIPANT" :)

--Richard


On Fri, Feb 7, 2014 at 6:42 PM, Christer Holmberg <
christer.holmberg@ericsson.com> wrote:

>
> Hi,
>
> I think the text that Dave suggests looks good.
>
> However, it's probably good to have a link to where the meaning of
> "Participation" is defined, because that discussion also comes up every now
> and then...
>
> Regards,
>
> Christer
>
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] on behalf of Dave Crocker [
> dhc@dcrocker.net]
> Sent: Saturday, 08 February 2014 1:32 AM
> To: IETF discussion list
> Subject: Re: Revision to Note Well
>
> On 2/7/2014 10:39 AM, Scott Brim wrote:
> > I'm concerned that any abbreviated form will inadequately represent
> > the nuances of the full policy, and that if we create a single uniform
> > abbreviated version that must be shown at f2f meetings, that opens
> > loopholes.
>
> Exactly.  Any form of redundancy -- like a 'summary' -- creates an
> opportunity for misunderstanding.
>
> Also let's be careful about the nature of the problem here.  Some folks
> want to find an excuse to avoid the responsibility the IETF is imposing.
>   Such folk will not be satisfied, no matter what we do.
>
> Some other folk really do need legitimate guidance.  While I'd argue
> that anyone who misunderstands the basic nature of IETF policy, after
> seeing/hearing the existing Note Well, is probably working at that
> misunderstanding.
>
> Still, we could make things both simpler and stronger.
>
>
> Here's what I suggest:
>
>
>
>                             NOTE WELL
>
>       PARTICIPATION IN THE IETF CARRIES ESSENTIAL OBLIGATIONS.
>
>       IT IS YOUR RESPONSIBILITY TO BECOME FAMILIAR WITH THE DETAILS OF
>       THOSE OBLIGATIONS AND TO ENSURE THAT YOU SATISFY THEM:
>
>       *  IETF IPR Disclosures Policy, as specified in BCP 79
>
>       *  IETF Anti-harassment Policy, as specified in
>          ietf.org/iesg/statement/ietf-anti-harassment-policy.html
>
>
>
> In each case these need to be a single pointer to to a single document.
>
>
> Of course, Jorge needs to vet this, but I believe this accomplishes only
> and exactly the stated goal, with none of the problems created by
> current or other proposed text.
>
>
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>

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

<div dir=3D"ltr">How about, &quot;IF YOU ARE SEEING THIS TEXT, THEN YOU ARE=
 A PARTICIPANT&quot; :)<div><br></div><div>--Richard</div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Fri, Feb 7, 2014 at =
6:42 PM, Christer Holmberg <span dir=3D"ltr">&lt;<a href=3D"mailto:christer=
.holmberg@ericsson.com" target=3D"_blank">christer.holmberg@ericsson.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"><br>
Hi,<br>
<br>
I think the text that Dave suggests looks good.<br>
<br>
However, it&#39;s probably good to have a link to where the meaning of &quo=
t;Participation&quot; is defined, because that discussion also comes up eve=
ry now and then...<br>
<br>
Regards,<br>
<br>
Christer<br>
<br>
________________________________________<br>
From: ietf [<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf.org<=
/a>] on behalf of Dave Crocker [<a href=3D"mailto:dhc@dcrocker.net">dhc@dcr=
ocker.net</a>]<br>
Sent: Saturday, 08 February 2014 1:32 AM<br>
To: IETF discussion list<br>
<div class=3D"im HOEnZb">Subject: Re: Revision to Note Well<br>
<br>
</div><div class=3D"HOEnZb"><div class=3D"h5">On 2/7/2014 10:39 AM, Scott B=
rim wrote:<br>
&gt; I&#39;m concerned that any abbreviated form will inadequately represen=
t<br>
&gt; the nuances of the full policy, and that if we create a single uniform=
<br>
&gt; abbreviated version that must be shown at f2f meetings, that opens<br>
&gt; loopholes.<br>
<br>
Exactly. =A0Any form of redundancy -- like a &#39;summary&#39; -- creates a=
n<br>
opportunity for misunderstanding.<br>
<br>
Also let&#39;s be careful about the nature of the problem here. =A0Some fol=
ks<br>
want to find an excuse to avoid the responsibility the IETF is imposing.<br=
>
=A0 Such folk will not be satisfied, no matter what we do.<br>
<br>
Some other folk really do need legitimate guidance. =A0While I&#39;d argue<=
br>
that anyone who misunderstands the basic nature of IETF policy, after<br>
seeing/hearing the existing Note Well, is probably working at that<br>
misunderstanding.<br>
<br>
Still, we could make things both simpler and stronger.<br>
<br>
<br>
Here&#39;s what I suggest:<br>
<br>
<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 NOTE WELL<br>
<br>
=A0 =A0 =A0 PARTICIPATION IN THE IETF CARRIES ESSENTIAL OBLIGATIONS.<br>
<br>
=A0 =A0 =A0 IT IS YOUR RESPONSIBILITY TO BECOME FAMILIAR WITH THE DETAILS O=
F<br>
=A0 =A0 =A0 THOSE OBLIGATIONS AND TO ENSURE THAT YOU SATISFY THEM:<br>
<br>
=A0 =A0 =A0 * =A0IETF IPR Disclosures Policy, as specified in BCP 79<br>
<br>
=A0 =A0 =A0 * =A0IETF Anti-harassment Policy, as specified in<br>
=A0 =A0 =A0 =A0 =A0<a href=3D"http://ietf.org/iesg/statement/ietf-anti-hara=
ssment-policy.html" target=3D"_blank">ietf.org/iesg/statement/ietf-anti-har=
assment-policy.html</a><br>
<br>
<br>
<br>
In each case these need to be a single pointer to to a single document.<br>
<br>
<br>
Of course, Jorge needs to vet this, but I believe this accomplishes only<br=
>
and exactly the stated goal, with none of the problems created by<br>
current or other proposed text.<br>
<br>
<br>
d/<br>
--<br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
</div></div></blockquote></div><br></div>

--001a1134d10056dc8b04f1e98a46--

From christer.holmberg@ericsson.com  Sat Feb  8 11:58:06 2014
Return-Path: <christer.holmberg@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 8490B1A013C for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 11:58:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.24
X-Spam-Level: 
X-Spam-Status: No, score=-1.24 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, 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 ZvHWeVc9qA_k for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 11:58:04 -0800 (PST)
Received: from sessmg20.mgmt.ericsson.se (sessmg20.ericsson.net [193.180.251.50]) by ietfa.amsl.com (Postfix) with ESMTP id 6810A1A00FE for <ietf@ietf.org>; Sat,  8 Feb 2014 11:58:04 -0800 (PST)
X-AuditID: c1b4fb32-b7f4c8e0000012f5-67-52f68c4b2693
Received: from ESESSHC021.ericsson.se (Unknown_Domain [153.88.253.124]) by sessmg20.mgmt.ericsson.se (Symantec Mail Security) with SMTP id 38.19.04853.B4C86F25; Sat,  8 Feb 2014 20:58:04 +0100 (CET)
Received: from ESESSMB209.ericsson.se ([169.254.9.99]) by ESESSHC021.ericsson.se ([153.88.183.81]) with mapi id 14.02.0387.000; Sat, 8 Feb 2014 20:58:03 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Richard Barnes <rlb@ipv.sx>
Subject: RE: Revision to Note Well
Thread-Topic: Revision to Note Well
Thread-Index: AQHPJF0OPgILfSAQz0q+WzBtDNHZ5ZqqcrMYgAEwSICAACRRcg==
Date: Sat, 8 Feb 2014 19:58:03 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B1D164B42@ESESSMB209.ericsson.se>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com> <52F56D21.9090602@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B1D163AC6@ESESSMB209.ericsson.se>, <CAL02cgQjF6-7UuvfYUy_CVMpqJ2SFNoTmh2UQ43mvg=tOn6cNg@mail.gmail.com>
In-Reply-To: <CAL02cgQjF6-7UuvfYUy_CVMpqJ2SFNoTmh2UQ43mvg=tOn6cNg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.146]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrGLMWRmVeSWpSXmKPExsUyM+Jvja5Pz7cggytXuSx+f/rAZvFs43wW i6l9tg7MHpd2nmTzWLLkJ5PH5I2zWAKYo7hsUlJzMstSi/TtErgy3k1xLvgkWvFg0lf2BsYN gl2MnBwSAiYSs/fPZoewxSQu3FvP1sXIxSEkcIJRYnrjVCYIZxGjRN/+1SxdjBwcbAIWEt3/ tEEaRATkJU5ff8AKYjMLBEtsatvOCGILCyhJzD9zgg2iRlniwJnjrBC2k8Shq7dZQGwWARWJ yWs6mUFG8gr4SqxcqAqx6jWzxLRFi8HmcAoESpxZeQHsOEag476fWsMEsUtc4taT+UwQRwtI LNlznhnCFpV4+fgfK4StJPFjwyUWiHodiQW7P7FB2NoSyxa+BqvnFRCUODnzCcsERrFZSMbO QtIyC0nLLCQtCxhZVjFKFqcWF+emGxno5abnluilFmUmFxfn5+kVp25iBMbVwS2/jXYwntxj f4hRmoNFSZz3OmtNkJBAemJJanZqakFqUXxRaU5q8SFGJg5OqQbG2GOlXfMuNm/aGDjpsUVj rIbaiZjcQ096q45Mvhx7NWmX/u3jkjmRab9nzNh57HVJ2l3bie2/fZ/26M/tO+q4RrtsepHZ mcNTXE4u37wm+7ra+drp2iLHipQuVbaqfXgUan9bQCKF9Ze0SNlhx5Um/0/NW1pzZ7Lwe1eX EKHyqQ88fyVdsGfsVmIpzkg01GIuKk4EAH047yR5AgAA
Cc: "dcrocker@bbiw.net" <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: Sat, 08 Feb 2014 19:58:06 -0000

I thought it applies also to e-mail participants :)

Regards,

Christer
________________________________________
From: Richard Barnes [rlb@ipv.sx]
Sent: Saturday, 08 February 2014 8:47 PM
To: Christer Holmberg
Cc: dcrocker@bbiw.net; IETF discussion list
Subject: Re: Revision to Note Well

How about, "IF YOU ARE SEEING THIS TEXT, THEN YOU ARE A PARTICIPANT" :)

--Richard


On Fri, Feb 7, 2014 at 6:42 PM, Christer Holmberg <christer.holmberg@ericss=
on.com<mailto:christer.holmberg@ericsson.com>> wrote:

Hi,

I think the text that Dave suggests looks good.

However, it's probably good to have a link to where the meaning of "Partici=
pation" is defined, because that discussion also comes up every now and the=
n...

Regards,

Christer

________________________________________
From: ietf [ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org>] on behalf =
of Dave Crocker [dhc@dcrocker.net<mailto:dhc@dcrocker.net>]
Sent: Saturday, 08 February 2014 1:32 AM
To: IETF discussion list
Subject: Re: Revision to Note Well

On 2/7/2014 10:39 AM, Scott Brim wrote:
> I'm concerned that any abbreviated form will inadequately represent
> the nuances of the full policy, and that if we create a single uniform
> abbreviated version that must be shown at f2f meetings, that opens
> loopholes.

Exactly.  Any form of redundancy -- like a 'summary' -- creates an
opportunity for misunderstanding.

Also let's be careful about the nature of the problem here.  Some folks
want to find an excuse to avoid the responsibility the IETF is imposing.
  Such folk will not be satisfied, no matter what we do.

Some other folk really do need legitimate guidance.  While I'd argue
that anyone who misunderstands the basic nature of IETF policy, after
seeing/hearing the existing Note Well, is probably working at that
misunderstanding.

Still, we could make things both simpler and stronger.


Here's what I suggest:



                            NOTE WELL

      PARTICIPATION IN THE IETF CARRIES ESSENTIAL OBLIGATIONS.

      IT IS YOUR RESPONSIBILITY TO BECOME FAMILIAR WITH THE DETAILS OF
      THOSE OBLIGATIONS AND TO ENSURE THAT YOU SATISFY THEM:

      *  IETF IPR Disclosures Policy, as specified in BCP 79

      *  IETF Anti-harassment Policy, as specified in
         ietf.org/iesg/statement/ietf-anti-harassment-policy.html<http://ie=
tf.org/iesg/statement/ietf-anti-harassment-policy.html>



In each case these need to be a single pointer to to a single document.


Of course, Jorge needs to vet this, but I believe this accomplishes only
and exactly the stated goal, with none of the problems created by
current or other proposed text.


d/
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net<http://bbiw.net>


From paul.hoffman@vpnc.org  Sat Feb  8 14:03:09 2014
Return-Path: <paul.hoffman@vpnc.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 C714B1A060E for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 14:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level: 
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NMkL9L5pRE8w for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 14:03:08 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id D00651A04CA for <ietf@ietf.org>; Sat,  8 Feb 2014 14:03:08 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s18M37Be005147 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 8 Feb 2014 15:03:08 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-1-98-67.dsl.dynamic.sonic.net [50.1.98.67] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Revision to Note Well
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAL02cgQjF6-7UuvfYUy_CVMpqJ2SFNoTmh2UQ43mvg=tOn6cNg@mail.gmail.com>
Date: Sat, 8 Feb 2014 14:03:06 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C274F73A-DFDF-4CC9-BCBB-F24BD9820F7F@vpnc.org>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com> <52F56D21.9090602@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B1D163AC6@ESESSMB209.ericsson.se> <CAL02cgQjF6-7UuvfYUy_CVMpqJ2SFNoTmh2UQ43mvg=tOn6cNg@mail.gmail.com>
To: Richard Barnes <rlb@ipv.sx>
X-Mailer: Apple Mail (2.1827)
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: Sat, 08 Feb 2014 22:03:10 -0000

> How about, "IF YOU ARE SEEING THIS TEXT, THEN YOU ARE A PARTICIPANT" =
:)

Is that true? I don't get that sense from the BCPs.

Your smiley is not terribly helpful here: it's not clear if it means =
"this is clever, yes?" or "what I just said is obviously a joke".

--Paul Hoffman=

From sandy@WEIJax.net  Sat Feb  8 14:06:02 2014
Return-Path: <sandy@WEIJax.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 7DA6E1A0627 for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 14:06:02 -0800 (PST)
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 kGMZ28OipUyx for <ietf@ietfa.amsl.com>; Sat,  8 Feb 2014 14:06:00 -0800 (PST)
Received: from homiemail-a70.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfa.amsl.com (Postfix) with ESMTP id 34F311A0622 for <ietf@ietf.org>; Sat,  8 Feb 2014 14:06:00 -0800 (PST)
Received: from homiemail-a70.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTP id B743476805C for <ietf@ietf.org>; Sat,  8 Feb 2014 14:06:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=WEIJax.net; h=message-id :date:from:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; s=weijax.net; bh=jzdD++ YFUYJx8K0IbvTWDqwTvOY=; b=VPTathQT1JBCJ5TKUMfG9ijW976UnnNB3DhMS+ rPhBLAQ91VLrwWOVEVNSGoT1JV6c7yRznvg0vJbGXboKrF1vleIwYKaMPBmnHiGl dC0JnTcO+f39vwyG/Dp9YvSoXrbUpMzobz9gdVbj6lCb0bkBg3qRIvZ5nFuctKYt I1c88=
Received: from [192.168.1.101] (unknown [207.98.159.191]) (Authenticated sender: sandy@weijax.net) by homiemail-a70.g.dreamhost.com (Postfix) with ESMTPA id 71196768057 for <ietf@ietf.org>; Sat,  8 Feb 2014 14:06:00 -0800 (PST)
Message-ID: <52F6AA42.4080801@WEIJax.net>
Date: Sat, 08 Feb 2014 17:05:54 -0500
From: Sandy Wills <sandy@WEIJax.net>
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: Revision to Note Well
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAPv4CP-L5gdKnzYy=CZ+FwkRurXtmo-mtecSKrx3-7710R9wtA@mail.gmail.com> <52F56D21.9090602@dcrocker.net> <7594FB04B1934943A5C02806D1A2204B1D163AC6@ESESSMB209.ericsson.se>, <CAL02cgQjF6-7UuvfYUy_CVMpqJ2SFNoTmh2UQ43mvg=tOn6cNg@mail.gmail.com> <7594FB04B1934943A5C02806D1A2204B1D164B42@ESESSMB209.ericsson.se>
In-Reply-To: <7594FB04B1934943A5C02806D1A2204B1D164B42@ESESSMB209.ericsson.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Feb 2014 22:06:02 -0000

IF YOU SEE THIS, WHETHER IN A PRESENTATION OR IN A DOCUMENT, YOU ARE.....

I am minded of Jeff Foxworthy's wisdom here.

-Sandy Wills

On 2/8/2014 2:58 PM, Christer Holmberg wrote:
>
> I thought it applies also to e-mail participants :)
>
> Regards,
>
> Christer
> ________________________________________
> From: Richard Barnes [rlb@ipv.sx]
> Sent: Saturday, 08 February 2014 8:47 PM
> To: Christer Holmberg
> Cc: dcrocker@bbiw.net; IETF discussion list
> Subject: Re: Revision to Note Well
>
> How about, "IF YOU ARE SEEING THIS TEXT, THEN YOU ARE A PARTICIPANT" :)
>
> --Richard
>
>
> On Fri, Feb 7, 2014 at 6:42 PM, Christer Holmberg <christer.holmberg@ericsson.com<mailto:christer.holmberg@ericsson.com>> wrote:
>
> Hi,
>
> I think the text that Dave suggests looks good.
>
> However, it's probably good to have a link to where the meaning of "Participation" is defined, because that discussion also comes up every now and then...
>
> Regards,
>
> Christer
>
> ________________________________________
> From: ietf [ietf-bounces@ietf.org<mailto:ietf-bounces@ietf.org>] on behalf of Dave Crocker [dhc@dcrocker.net<mailto:dhc@dcrocker.net>]
> Sent: Saturday, 08 February 2014 1:32 AM
> To: IETF discussion list
> Subject: Re: Revision to Note Well
>
> On 2/7/2014 10:39 AM, Scott Brim wrote:
>> I'm concerned that any abbreviated form will inadequately represent
>> the nuances of the full policy, and that if we create a single uniform
>> abbreviated version that must be shown at f2f meetings, that opens
>> loopholes.
>
> Exactly.  Any form of redundancy -- like a 'summary' -- creates an
> opportunity for misunderstanding.
>
> Also let's be careful about the nature of the problem here.  Some folks
> want to find an excuse to avoid the responsibility the IETF is imposing.
>    Such folk will not be satisfied, no matter what we do.
>
> Some other folk really do need legitimate guidance.  While I'd argue
> that anyone who misunderstands the basic nature of IETF policy, after
> seeing/hearing the existing Note Well, is probably working at that
> misunderstanding.
>
> Still, we could make things both simpler and stronger.
>
>
> Here's what I suggest:
>
>
>
>                              NOTE WELL
>
>        PARTICIPATION IN THE IETF CARRIES ESSENTIAL OBLIGATIONS.
>
>        IT IS YOUR RESPONSIBILITY TO BECOME FAMILIAR WITH THE DETAILS OF
>        THOSE OBLIGATIONS AND TO ENSURE THAT YOU SATISFY THEM:
>
>        *  IETF IPR Disclosures Policy, as specified in BCP 79
>
>        *  IETF Anti-harassment Policy, as specified in
>           ietf.org/iesg/statement/ietf-anti-harassment-policy.html<http://ietf.org/iesg/statement/ietf-anti-harassment-policy.html>
>
>
>
> In each case these need to be a single pointer to to a single document.
>
>
> Of course, Jorge needs to vet this, but I believe this accomplishes only
> and exactly the stated goal, with none of the problems created by
> current or other proposed text.
>
>
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net<http://bbiw.net>
>
>


-- 
Unable to locate coffee.
Operator halted.

From jari.arkko@piuha.net  Sun Feb  9 01:35: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 96F2F1A06BF; Sun,  9 Feb 2014 01:35:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id thsawfz4yJY5; Sun,  9 Feb 2014 01:35:46 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id C098F1A06BC; Sun,  9 Feb 2014 01:35:45 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C18C92CEAE; Sun,  9 Feb 2014 11:35:45 +0200 (EET)
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 dX7BxCwc2wHx; Sun,  9 Feb 2014 11:35:45 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 055012CC48; Sun,  9 Feb 2014 11:35:45 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Subject: Code Sprint in London
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Jari Arkko <jari.arkko@piuha.net>
Date: Sun, 9 Feb 2014 11:35:44 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9D815CD-9EF8-4F86-BBE3-DE13CF010C15@piuha.net>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "ietf@ietf.org Mailing List" <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, 09 Feb 2014 09:35:50 -0000

We will once again have a Code Sprint in London prior to IETF-89. Please =
support the tools team with your time and expertise! Or come and build =
the feature that you always wanted to have :-)

When: Saturday, March 1, 2014, beginning at 9:30 AM and running until 6 =
PM

Where: The IETF meeting hotel (Hilton London Metropole), meeting rooms =
13-17

What:  A bunch of hackers get together to work on code for the IETF data =
tracker, web site and other tools.  Some people may be working on =
improvements in existing functionality, others may be adding exciting =
new functionality.  All code will become part of the open source IETF =
tools.

Who: Hopefully you can help

Henrik and Robert will be coordinating the efforts. Please support the =
tools development effort, join the volunteer team and contribute!

The wiki for the sprint, along with a sign-up sheet, is at =
https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF89Sprint

Jari Arkko
IETF Chair=

From chair@ietf.org  Sun Feb  9 01:58:16 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 763EC1A06C2; Sun,  9 Feb 2014 01:58:16 -0800 (PST)
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 83fUcMOhNwnr; Sun,  9 Feb 2014 01:58:14 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id ACB0C1A00AE; Sun,  9 Feb 2014 01:58:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 127D59FF82; Sun,  9 Feb 2014 01:58:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8xGL3JSzpLj2; Sun,  9 Feb 2014 01:58:11 -0800 (PST)
Received: from [IPv6:2001:14b8:400:f33:3dd9:9fd4:950d:eb03] (unknown [IPv6:2001:14b8:400:f33:3dd9:9fd4:950d:eb03]) by c9a.amsl.com (Postfix) with ESMTPSA id E8A8B9FB4C; Sun,  9 Feb 2014 01:58:10 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: IAOC appointment by the IESG
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Sun, 9 Feb 2014 11:58:11 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <D72E02C3-A908-44BF-BBB2-2B79671FACB0@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "ietf@ietf.org Mailing List" <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, 09 Feb 2014 09:58:16 -0000

The IESG is responsible for filling one seat on the IAOC every other =
year. The IESG has now completed this process to fill the seat from =
March 2014 to March 2016. John Levine will be the new IAOC member.

I would like to congratulate John and thank him for volunteering for =
this task. I would also like to thank all the volunteers; the selection =
was difficult, as we had so many excellent candidates. I would also like =
to thank those who provided feedback for the IESG on this selection. =
Last but not least, I would like to thank Ole Jacobsen who is the =
outgoing member, and who has served in the IAOC from 2008. Your years of =
service in this (often not so easy) task have been very much appreciated =
- Thank you!

Jari Arkko for the IESG


From chair@ietf.org  Sun Feb  9 02:00:03 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 4E9441A06C5; Sun,  9 Feb 2014 02:00:03 -0800 (PST)
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 AqqRKxP1ae_7; Sun,  9 Feb 2014 02:00:01 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id B0EED1A06C2; Sun,  9 Feb 2014 02:00:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 180349FF82; Sun,  9 Feb 2014 01:59:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4yEdaLDH-Zh; Sun,  9 Feb 2014 01:59:59 -0800 (PST)
Received: from [10.30.0.101] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id DE7879FB4C; Sun,  9 Feb 2014 01:59:57 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Code Sprint in London
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Sun, 9 Feb 2014 11:59:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2F6A007-82EC-40E4-8780-EB342AD3B6AD@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1510)
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "ietf@ietf.org Mailing List" <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, 09 Feb 2014 10:00:03 -0000

We will once again have a Code Sprint in London prior to IETF-89. Please =
support the tools team with your time and expertise! Or come and build =
the feature that you always wanted to have :-)

When: Saturday, March 1, 2014, beginning at 9:30 AM and running until 6 =
PM

Where: The IETF meeting hotel (Hilton London Metropole), meeting rooms =
13-17

What:  A bunch of hackers get together to work on code for the IETF data =
tracker, web site and other tools.  Some people may be working on =
improvements in existing functionality, others may be adding exciting =
new functionality.  All code will become part of the open source IETF =
tools.

Who: Hopefully you can help

Henrik and Robert will be coordinating the efforts. Please support the =
tools development effort, join the volunteer team and contribute!

The wiki for the sprint, along with a sign-up sheet, is at =
https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF89Sprint

Jari Arkko
IETF Chair=

From l.wood@surrey.ac.uk  Sun Feb  9 16:11:03 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 B840B1A061F for <ietf@ietfa.amsl.com>; Sun,  9 Feb 2014 16:11:03 -0800 (PST)
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 XV9Wu8v2wTuB for <ietf@ietfa.amsl.com>; Sun,  9 Feb 2014 16:10:57 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) by ietfa.amsl.com (Postfix) with ESMTP id 386FB1A061B for <ietf@ietf.org>; Sun,  9 Feb 2014 16:10:56 -0800 (PST)
Received: from [85.158.136.51:2449] by server-13.bemta-5.messagelabs.com id 46/70-18801-01918F25; Mon, 10 Feb 2014 00:10:56 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-49.messagelabs.com!1391991055!18518749!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24802 invoked from network); 10 Feb 2014 00:10:56 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-9.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 10 Feb 2014 00:10:55 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Mon, 10 Feb 2014 00:10:54 +0000
From: <l.wood@surrey.ac.uk>
To: <ietf@ietf.org>
Date: Mon, 10 Feb 2014 00:10:25 +0000
Subject: RE: Code Sprint in London
Thread-Topic: Code Sprint in London
Thread-Index: Ac8lemmch2LTntbeT/2T/OnNsgNEIQAehVtc
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334706@EXMB01CMS.surrey.ac.uk>
References: <D9D815CD-9EF8-4F86-BBE3-DE13CF010C15@piuha.net>
In-Reply-To: <D9D815CD-9EF8-4F86-BBE3-DE13CF010C15@piuha.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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Feb 2014 00:11:03 -0000

Excellent.

Make the IETF Code Sprint part of the UK Year of Code...

http://adrianshort.org/2014/02/09/lottie-dexter-quit-year-of-code/

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Jari Arkko [jari.arkko@piuh=
a.net]
Sent: 09 February 2014 09:35
To: ietf-announce@ietf.org
Cc: ietf@ietf.org Mailing List
Subject: Code Sprint in London

We will once again have a Code Sprint in London prior to IETF-89. Please su=
pport the tools team with your time and expertise! Or come and build the fe=
ature that you always wanted to have :-)

When: Saturday, March 1, 2014, beginning at 9:30 AM and running until 6 PM

Where: The IETF meeting hotel (Hilton London Metropole), meeting rooms 13-1=
7

What:  A bunch of hackers get together to work on code for the IETF data tr=
acker, web site and other tools.  Some people may be working on improvement=
s in existing functionality, others may be adding exciting new functionalit=
y.  All code will become part of the open source IETF tools.

Who: Hopefully you can help

Henrik and Robert will be coordinating the efforts. Please support the tool=
s development effort, join the volunteer team and contribute!

The wiki for the sprint, along with a sign-up sheet, is at https://trac.too=
ls.ietf.org/tools/ietfdb/wiki/IETF89Sprint

Jari Arkko
IETF Chair=

From yangkun2005@gmail.com  Sun Feb  9 19:52:52 2014
Return-Path: <yangkun2005@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 88AD41A079B for <ietf@ietfa.amsl.com>; Sun,  9 Feb 2014 19:52:52 -0800 (PST)
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 S075hSOPXQd6 for <ietf@ietfa.amsl.com>; Sun,  9 Feb 2014 19:52:51 -0800 (PST)
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 321EF1A0799 for <ietf@ietf.org>; Sun,  9 Feb 2014 19:52:51 -0800 (PST)
Received: by mail-ob0-f182.google.com with SMTP id wm4so6646484obc.41 for <ietf@ietf.org>; Sun, 09 Feb 2014 19:52:51 -0800 (PST)
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=CFevAtEisWZBoze7npG98qw8tjE4T/o+YYP+dussAmk=; b=TYIt17rX+5EPuCNLc2EQkAAVovg0LIGdjqZssWARIIbynYdCsx8kq/8MOKOmNXxuxO rrlNn4vzvev5i5dmdJ4WK7gSQvGxGv/Tex+lemQqt9nNJB/J4iX4qwZkkFXse/+Bhk4b 0y9DD6ACy0v9Iw6eHWlSFgNo8bY2u9cVfqeu/80aqZgXJo0C0T75jJMKUGqmxI9f2Em+ iQDI+Pe5uRQD6ziJ58Z3cYz8larGRqjHD4NzPNFdYQu9JiI7NgKPloxDTAUCv55VKkuy MU/C8OvxSufLkB5SVFvVixYhj8Mvg/9jBsSn142OhTdXyRD8gV38sg7wuvxW68BoSyEo NjEQ==
MIME-Version: 1.0
X-Received: by 10.182.226.202 with SMTP id ru10mr24642177obc.7.1392004371155;  Sun, 09 Feb 2014 19:52:51 -0800 (PST)
Received: by 10.76.85.131 with HTTP; Sun, 9 Feb 2014 19:52:51 -0800 (PST)
Date: Mon, 10 Feb 2014 11:52:51 +0800
Message-ID: <CAAby8wRujLUz-YPjNikm-CGVB60uKBt=EGt68X4XX61a1_QXNQ@mail.gmail.com>
Subject: Please remove my account from ietf
From: Kun Yang <yangkun2005@gmail.com>
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a11c32efa1190a904f20546dc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Feb 2014 03:52:52 -0000

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

To whom may concern,

Please remove my account yangkun2005@gmail.com from ietf. Thanks!

Kun Yang

--001a11c32efa1190a904f20546dc
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">To whom may concern,<div><br></div><div>Please remove my account <a href="mailto:yangkun2005@gmail.com">yangkun2005@gmail.com</a> from ietf. Thanks!</div><div><br></div><div>Kun Yang</div></div>

--001a11c32efa1190a904f20546dc--

From cntreras@gmail.com  Mon Feb 10 06:24:50 2014
Return-Path: <cntreras@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 E09A11A0881 for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 06:24:50 -0800 (PST)
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 xlf0cOg31KLK for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 06:24:46 -0800 (PST)
Received: from mail-ee0-x235.google.com (mail-ee0-x235.google.com [IPv6:2a00:1450:4013:c00::235]) by ietfa.amsl.com (Postfix) with ESMTP id C0A721A087D for <ietf@ietf.org>; Mon, 10 Feb 2014 06:13:49 -0800 (PST)
Received: by mail-ee0-f53.google.com with SMTP id t10so2935391eei.26 for <ietf@ietf.org>; Mon, 10 Feb 2014 06:13:48 -0800 (PST)
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=uUgT10hv7hNxA4ncOmASgthfrHtotRKSO8zaZ+QT5Us=; b=nKHQXdiFlSTRkb4oMI0XwcAZvfatoqNuLcxvl/WSZjxeXVBunBw0Hrzaxcuj2t4h7r /xE7oBpJT3v6ex4fvc9kSEVI1i25mgw9qBUwHdhgLUZ3/+ztRZb/o4OM6y9MNiZjXsTx Nmh8Yk46NTmPAZ4YlNdOOxX5HzUpGb2ejVYEeHkmNrcmz3Y7NZrkph7nN4pQSrQLwQw8 7EKK7MivKojW+/N1NbaZqG+/A9oYFZscw59El7y+4ELkDFQgc3B9wvuI+PONZTrhbnwm KSQFFuEjpaAg7llzXb52hD98AFUnaEBNDR5DSMzeltnrMU7k31iJuVfzXq3jyl3dYB4/ Ne2Q==
MIME-Version: 1.0
X-Received: by 10.14.216.193 with SMTP id g41mr37224367eep.13.1392041628876; Mon, 10 Feb 2014 06:13:48 -0800 (PST)
Received: by 10.14.108.72 with HTTP; Mon, 10 Feb 2014 06:13:48 -0800 (PST)
In-Reply-To: <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com>
Date: Mon, 10 Feb 2014 09:13:48 -0500
Message-ID: <CAP0PwYb-88_JsB=X+0aPLdQ5DAoUcYkPkxBQ58B9eTVE0nE2zw@mail.gmail.com>
Subject: Re: Revision to Note Well
From: Jorge Contreras <cntreras@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=047d7b622072cd44ef04f20df222
Cc: Pete Resnick <presnick@qti.qualcomm.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: Mon, 10 Feb 2014 14:24:51 -0000

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

This is a healthy discussion.  However, if you really care about these
issues (i.e., what constitutes "participation" in an IETF discussion for
purposes of triggering an IPR disclosure) then debating it in the context
of the "Note Well" language is, to put it mildly, a waste of time.  The
actual "rules" that govern this issue are contained in BCP79, which is in
the process of being revised right now.  This exact issue has been
discussed repeatedly in the IPR WG and the rules in BCP79 are being amended
*right now* to deal with concerns that were raised.  If you care and want
to discuss in some way that may actually affect the IETF rules, rather than
a non-substantive pointer to the rules (i.e., "Note Well"), please take a
look at the latest I-D implementing these rules and comment on it:

https://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/

The relevant Sections are 1.c ("Contribution") and 1.k, which actually
defines "Participating in an IETF Discussion or Activity".

Enjoy!

Jorge


On Fri, Feb 7, 2014 at 1:09 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Friday, February 07, 2014 11:28 -0600 Pete Resnick
> <presnick@qti.qualcomm.com> wrote:
>
> > On 2/7/14 2:05 AM, Eggert, Lars wrote:
> >> I'll again point to the IRTF statement, which
> >> does:http://irtf.org/ipr. We'll make it available to the IETF
> >> for the low, low price of a round of beers for the IRSG:-)
> >>
> >
> > FWIW, I like the IRTF statement and think it would be a fine
> > addition/replacement *for what's on the web site*. It's not
> > short enough IMO for the face-to-face in-room reminder,
> > particularly if a chair were going to actually *say* it, but
> > maybe if something of this nature appeared on the web site,
> > the in-room reminder wouldn't be as necessary.
>
> Pete,
>
> As others have suggested, if you want to raise a "please pay
> attention to things you have presumably read" flag in meetings
> and especially if you think the current version is too long or
> complicated, just do that with one of many versions of the "if
> you or your organization have IPR in this topic you had best
> either understand the BCP provisions or leave" statement, with
> or without a second "if know of someone else's, you should be
> paying attention to the BCPs too" remark.
>
> Don't try to summarize.  You can't get it right in a sentence or
> four and will just create risks without improving understanding
> or, most likely, compliance.
>
> > (And to answer an earlier question, yes, we've had a bunch of
> > late disclosures. They seem to come in waves.
> >...
>
> Let me then suggest a small bit of research.  You know who the
> responsible parties are.  Have you asked them whether additional
> notices would have made any difference and, if so, of what sort
> and where?  Obviously some will be unwilling (or unable) to
> respond accurately.  But it would be nice to have at least a
> shred of evidence that more investment in fine-tuning
> announcements would actually improve the rate of timely
> disclosures.
>
> In addition, there is a more interesting question than "have
> their been late disclosures".  It is "how many of the late
> disclosures were defended on the basis of ignorance about the
> rules?".  If the number of those is non-zero, it would also be
> interesting to know whether (and how often) that claim has been
> made under oath in an actual proceeding rather than informal
> remarks to the IESG.
>
> Unless there have been serious claims that the reason for
> non-disclosure is ignorance of the rules or our failure to have
> enough notices, I'm not sure what problem you are trying to
> solve that is important enough to justify the costs of this
> discussion.
>
> best,
>      john
>
>

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

<div dir=3D"ltr"><div><div>This is a healthy discussion.=A0 However, if you=
 really care about these issues (i.e., what constitutes &quot;participation=
&quot; in an IETF discussion for purposes of triggering an IPR disclosure) =
then debating it in the context of the &quot;Note Well&quot; language is, t=
o put it mildly, a waste of time.=A0 The actual &quot;rules&quot; that gove=
rn this issue are contained in BCP79, which is in the process of being revi=
sed right now.=A0 This exact issue has been discussed repeatedly in the IPR=
 WG and the rules in BCP79 are being amended *right now* to deal with conce=
rns that were raised.=A0 If you care and want to discuss in some way that m=
ay actually affect the IETF rules, rather than a non-substantive pointer to=
 the rules (i.e., &quot;Note Well&quot;), please take a look at the latest =
I-D implementing these rules and comment on it:<br>
<br><a href=3D"https://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/">=
https://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/</a><br><br></div=
>The relevant Sections are 1.c (&quot;Contribution&quot;) and 1.k, which ac=
tually defines &quot;Participating in an IETF Discussion or Activity&quot;.=
<br>
<br>Enjoy!<br><br></div>Jorge<br></div><div class=3D"gmail_extra"><br><br><=
div class=3D"gmail_quote">On Fri, Feb 7, 2014 at 1:09 PM, John C Klensin <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">=
john-ietf@jck.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"><br>
<br>
--On Friday, February 07, 2014 11:28 -0600 Pete Resnick<br>
<div class=3D"">&lt;<a href=3D"mailto:presnick@qti.qualcomm.com">presnick@q=
ti.qualcomm.com</a>&gt; wrote:<br>
<br>
&gt; On 2/7/14 2:05 AM, Eggert, Lars wrote:<br>
&gt;&gt; I&#39;ll again point to the IRTF statement, which<br>
&gt;&gt; does:<a href=3D"http://irtf.org/ipr" target=3D"_blank">http://irtf=
.org/ipr</a>. We&#39;ll make it available to the IETF<br>
&gt;&gt; for the low, low price of a round of beers for the IRSG:-)<br>
&gt;&gt;<br>
&gt;<br>
&gt; FWIW, I like the IRTF statement and think it would be a fine<br>
&gt; addition/replacement *for what&#39;s on the web site*. It&#39;s not<br=
>
&gt; short enough IMO for the face-to-face in-room reminder,<br>
&gt; particularly if a chair were going to actually *say* it, but<br>
&gt; maybe if something of this nature appeared on the web site,<br>
&gt; the in-room reminder wouldn&#39;t be as necessary.<br>
<br>
</div>Pete,<br>
<br>
As others have suggested, if you want to raise a &quot;please pay<br>
attention to things you have presumably read&quot; flag in meetings<br>
and especially if you think the current version is too long or<br>
complicated, just do that with one of many versions of the &quot;if<br>
you or your organization have IPR in this topic you had best<br>
either understand the BCP provisions or leave&quot; statement, with<br>
or without a second &quot;if know of someone else&#39;s, you should be<br>
paying attention to the BCPs too&quot; remark.<br>
<br>
Don&#39;t try to summarize. =A0You can&#39;t get it right in a sentence or<=
br>
four and will just create risks without improving understanding<br>
or, most likely, compliance.<br>
<div class=3D""><br>
&gt; (And to answer an earlier question, yes, we&#39;ve had a bunch of<br>
&gt; late disclosures. They seem to come in waves.<br>
</div>&gt;...<br>
<br>
Let me then suggest a small bit of research. =A0You know who the<br>
responsible parties are. =A0Have you asked them whether additional<br>
notices would have made any difference and, if so, of what sort<br>
and where? =A0Obviously some will be unwilling (or unable) to<br>
respond accurately. =A0But it would be nice to have at least a<br>
shred of evidence that more investment in fine-tuning<br>
announcements would actually improve the rate of timely<br>
disclosures.<br>
<br>
In addition, there is a more interesting question than &quot;have<br>
their been late disclosures&quot;. =A0It is &quot;how many of the late<br>
disclosures were defended on the basis of ignorance about the<br>
rules?&quot;. =A0If the number of those is non-zero, it would also be<br>
interesting to know whether (and how often) that claim has been<br>
made under oath in an actual proceeding rather than informal<br>
remarks to the IESG.<br>
<br>
Unless there have been serious claims that the reason for<br>
non-disclosure is ignorance of the rules or our failure to have<br>
enough notices, I&#39;m not sure what problem you are trying to<br>
solve that is important enough to justify the costs of this<br>
discussion.<br>
<br>
best,<br>
=A0 =A0 =A0john<br>
<br>
</blockquote></div><br></div>

--047d7b622072cd44ef04f20df222--

From hansensmart@gmail.com  Fri Feb  7 10:05:27 2014
Return-Path: <hansensmart@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 8CD321AC7F2 for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 10:05:27 -0800 (PST)
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 aXMQgOPGCgUo for <ietf@ietfa.amsl.com>; Fri,  7 Feb 2014 10:05:25 -0800 (PST)
Received: from mail-la0-x234.google.com (mail-la0-x234.google.com [IPv6:2a00:1450:4010:c03::234]) by ietfa.amsl.com (Postfix) with ESMTP id B0B591A0176 for <ietf@ietf.org>; Fri,  7 Feb 2014 10:05:24 -0800 (PST)
Received: by mail-la0-f52.google.com with SMTP id c6so2900247lan.39 for <ietf@ietf.org>; Fri, 07 Feb 2014 10:05:23 -0800 (PST)
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=auLutlrhO0aCrshNIR0gQjn1Uty9+CvmHzQ/fpfdvvQ=; b=KHoFZ2euH0haz6YQne4i7WDAZFjhBZA6QXT+1UXQcU12uwPu3qxNGrkTN6Km535d4u Yp8IaJEEbLoQCNLG/Wp+BzrIR4ujqOhxhKOjQl/LKMR+dTG8sZtXBVQgUjorOtNLW3qb wPpy4GJYf+y56pSRznUPIjJZ7bg/saAvf178s3CQyDcjN+sTUXE+v3qFtss+shxAg4Mi Ge8NNAaoZm9irEpKoiUUYsgbEhf57SVFPgRTEHBNgoFeT45ca4VGBwyk5S5N4erkj7xh ee9oipeMxdT0oMAt2hRcKZAWJWxkmrUntTMe8yiCoYYyjm4C9LA2/sXKvPOx93xHQwhT zOOA==
X-Received: by 10.152.234.3 with SMTP id ua3mr1238647lac.63.1391796323878; Fri, 07 Feb 2014 10:05:23 -0800 (PST)
MIME-Version: 1.0
Received: by 10.112.236.35 with HTTP; Fri, 7 Feb 2014 10:05:03 -0800 (PST)
In-Reply-To: <20140207180258.26073.51442.idtracker@ietfa.amsl.com>
References: <20140207180258.26073.51442.idtracker@ietfa.amsl.com>
From: Farooq247 <hansensmart@gmail.com>
Date: Fri, 7 Feb 2014 18:05:03 +0000
Message-ID: <CANPNYgywFeGB-0BiP6xGgvC=r6NMx4iG0QXoAeto_SFJwCAWuw@mail.gmail.com>
Subject: Re: WG Action: Rechartered Transport Layer Security (tls)
To: ietf@ietf.org
Content-Type: multipart/alternative; boundary=001a1134342c7c0b9404f1d4d503
X-Mailman-Approved-At: Mon, 10 Feb 2014 07:23:30 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Feb 2014 18:05:27 -0000

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

Oh no rechartered - please keep me informed.

with best

Hansen


On 7 February 2014 18:02, The IESG <iesg-secretary@ietf.org> wrote:

> The Transport Layer Security (tls) working group in the Security Area of
> the IETF has been rechartered. For additional information please contact
> the Area Directors or the WG Chairs.
>
> Transport Layer Security (tls)
> ------------------------------------------------
> Current Status: Active WG
>
> Chairs:
>   Eric Rescorla <ekr@networkresonance.com>
>   Joseph Salowey <jsalowey@cisco.com>
>   Eric Rescorla <ekr@rtfm.com>
>
> Technical advisors:
>   Allison Mankin <mankin@psg.com>
>
> Assigned Area Director:
>   Sean Turner <turners@ieca.com>
>
> Mailing list
>   Address: tls@ietf.org
>   To Subscribe: https://www.ietf.org/mailman/listinfo/tls
>   Archive: http://www.ietf.org/mail-archive/web/tls/
>
> Charter:
>
> The TLS (Transport Layer Security) working group was
> established in 1996 to standardize a 'transport layer'
> security protocol.  The basis for the work was SSL
> (Secure Socket Layer) v3.0.  The TLS working group has
> completed a series of specifications that describe the
> TLS protocol v1.0, v1.1, and v1.2 and DTLS
> (Datagram TLS) v1.2 as well as extensions to the
> protocols and ciphersuites.
>
> The primary purpose of the working group is to develop
> (D)TLS v1.3.  Some of the main design goals are as follows,
> in no particular order:
>
> o Develop a mode that encrypts as much of the handshake as
> is possible to reduce the amount of observable data to
> both passive and active attackers.
>
> o Develop modes to reduce handshake latency, which primarily
> support HTTP-based applications, aiming for one roundtrip
> for a full handshake and one or zero roundtrip for repeated
> handshakes.   The aim is also to maintain current security
> features.
>
> o Update record payload protection cryptographic
> mechanisms and algorithms to address known weaknesses
> in the CBC block cipher modes and to replace RC4.
>
> o Reevaluate handshake contents, e.g.,: Is time needed in
> client hello?  Should signature in server key exchange
> cover entire handshake?  Are bigger randoms required?
> Should there be distinct cipher list for each version?  Are
> additional mechanisms needed to prevent version rollback
> needed?
>
> o The WG will consider the privacy implications of
> TLS1.3 and where possible (balancing with other requirements)
> will aim to make TLS1.3 more privacy-friendly, e.g. via more
> consistent application traffic padding, more considered use
> of long term identifying values, etc.
>
> A secondary purpose is to maintain previous version of
> the (D)TLS protocols as well as to specify the use of
> (D)TLS, recommendations for use of (D)TLS, extensions to
> (D)TLS, and cipher suites.  However, changes or additions
> to older versions of (D)TLS whether via extensions or
> ciphersuites are discouraged and require significant
> justification to be taken on as work items.
>
> With these objectives in mind, the TLS WG will also place a priority
> in minimizing gratuitous changes to TLS.
>
> Milestones:
>   Jan 2014 - CBC Fixes to IESG
>   May 2014 - RC4 replacement to IESG
>   Nov 2014 - (D)TLS 1.3 to IESG
>
>
>

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

<div dir=3D"ltr">Oh no rechartered - please keep me informed.<div><br></div=
><div>with best=A0</div><div><br></div><div>Hansen</div></div><div class=3D=
"gmail_extra"><br><br><div class=3D"gmail_quote">On 7 February 2014 18:02, =
The IESG <span dir=3D"ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org" t=
arget=3D"_blank">iesg-secretary@ietf.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">The Transport Layer Security (tls) working g=
roup in the Security Area of<br>
the IETF has been rechartered. For additional information please contact<br=
>
the Area Directors or the WG Chairs.<br>
<br>
Transport Layer Security (tls)<br>
------------------------------------------------<br>
Current Status: Active WG<br>
<br>
Chairs:<br>
=A0 Eric Rescorla &lt;<a href=3D"mailto:ekr@networkresonance.com">ekr@netwo=
rkresonance.com</a>&gt;<br>
=A0 Joseph Salowey &lt;<a href=3D"mailto:jsalowey@cisco.com">jsalowey@cisco=
.com</a>&gt;<br>
=A0 Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt;<=
br>
<br>
Technical advisors:<br>
=A0 Allison Mankin &lt;<a href=3D"mailto:mankin@psg.com">mankin@psg.com</a>=
&gt;<br>
<br>
Assigned Area Director:<br>
=A0 Sean Turner &lt;<a href=3D"mailto:turners@ieca.com">turners@ieca.com</a=
>&gt;<br>
<br>
Mailing list<br>
=A0 Address: <a href=3D"mailto:tls@ietf.org">tls@ietf.org</a><br>
=A0 To Subscribe: <a href=3D"https://www.ietf.org/mailman/listinfo/tls" tar=
get=3D"_blank">https://www.ietf.org/mailman/listinfo/tls</a><br>
=A0 Archive: <a href=3D"http://www.ietf.org/mail-archive/web/tls/" target=
=3D"_blank">http://www.ietf.org/mail-archive/web/tls/</a><br>
<br>
Charter:<br>
<br>
The TLS (Transport Layer Security) working group was<br>
established in 1996 to standardize a &#39;transport layer&#39;<br>
security protocol. =A0The basis for the work was SSL<br>
(Secure Socket Layer) v3.0. =A0The TLS working group has<br>
completed a series of specifications that describe the<br>
TLS protocol v1.0, v1.1, and v1.2 and DTLS<br>
(Datagram TLS) v1.2 as well as extensions to the<br>
protocols and ciphersuites.<br>
<br>
The primary purpose of the working group is to develop<br>
(D)TLS v1.3. =A0Some of the main design goals are as follows,<br>
in no particular order:<br>
<br>
o Develop a mode that encrypts as much of the handshake as<br>
is possible to reduce the amount of observable data to<br>
both passive and active attackers.<br>
<br>
o Develop modes to reduce handshake latency, which primarily<br>
support HTTP-based applications, aiming for one roundtrip<br>
for a full handshake and one or zero roundtrip for repeated<br>
handshakes. =A0 The aim is also to maintain current security<br>
features.<br>
<br>
o Update record payload protection cryptographic<br>
mechanisms and algorithms to address known weaknesses<br>
in the CBC block cipher modes and to replace RC4.<br>
<br>
o Reevaluate handshake contents, e.g.,: Is time needed in<br>
client hello? =A0Should signature in server key exchange<br>
cover entire handshake? =A0Are bigger randoms required?<br>
Should there be distinct cipher list for each version? =A0Are<br>
additional mechanisms needed to prevent version rollback<br>
needed?<br>
<br>
o The WG will consider the privacy implications of<br>
TLS1.3 and where possible (balancing with other requirements)<br>
will aim to make TLS1.3 more privacy-friendly, e.g. via more<br>
consistent application traffic padding, more considered use<br>
of long term identifying values, etc.<br>
<br>
A secondary purpose is to maintain previous version of<br>
the (D)TLS protocols as well as to specify the use of<br>
(D)TLS, recommendations for use of (D)TLS, extensions to<br>
(D)TLS, and cipher suites. =A0However, changes or additions<br>
to older versions of (D)TLS whether via extensions or<br>
ciphersuites are discouraged and require significant<br>
justification to be taken on as work items.<br>
<br>
With these objectives in mind, the TLS WG will also place a priority<br>
in minimizing gratuitous changes to TLS.<br>
<br>
Milestones:<br>
=A0 Jan 2014 - CBC Fixes to IESG<br>
=A0 May 2014 - RC4 replacement to IESG<br>
=A0 Nov 2014 - (D)TLS 1.3 to IESG<br>
<br>
<br>
</blockquote></div><br></div>

--001a1134342c7c0b9404f1d4d503--

From johnl@iecc.com  Mon Feb 10 08:26: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 9F6F31A0320 for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 08:26:46 -0800 (PST)
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 CDGAppHSJweb for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 08:26:45 -0800 (PST)
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 F413C1A017E for <ietf@ietf.org>; Mon, 10 Feb 2014 08:26:44 -0800 (PST)
Received: (qmail 44688 invoked from network); 10 Feb 2014 16:26:43 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 10 Feb 2014 16:26:43 -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=52f8fdc3.xn--3zv.k1402; i=johnl@user.iecc.com; bh=rxC1G3SAKYq8vq/UvXpv2BH118MNg4mJ8y6hirkG8wU=; b=FGVSssi5pn9G41o9RLNLIUxryL3pjBpLxC+KF28yMRrwlwb1Zk64Gs2guQB6GWfBbiAXcB/WsHep5Y2vlY8ksBMZ3E+hvUPk68wfBduV3jlrx1i0OGzF7wSU2QzBX6igIRY5J8VjQepU/W9oDJkqRJmxuLECA0OuNzg0YuKSbUXPq+gidiAow5JfbmTJzme5YLgZ2YnvmQw3ZzP69j7GhksRUqMFj4obV/L8NwNeXQBWUB+npAmHZjmN6YjkeONB
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=52f8fdc3.xn--3zv.k1402; bh=rxC1G3SAKYq8vq/UvXpv2BH118MNg4mJ8y6hirkG8wU=; b=P051sUhOHac0FX0AHFzRr7jBYDRbZCm43GS4bPRYRUfqVff2Tuyfj7auOeyAXOZvzFtcTtpbttDdbU2ZqjsJLyQYC9X+Xp37jm3g2LQG1hrhpq9WP35dickfXI7i7Qd8YMf6P9RSBB2ln/RmtgkRDYRdKJwBTCpdRqd9Z5RwHzkg6UEnX1XOuMtRRbPe0rqAKaCoUwk2nysF2QXkKzPJJzIXmKpXe4OS1krUBazyuUrodu0rDPUWwJM0VfBaT/l/
Date: 10 Feb 2014 16:26:21 -0000
Message-ID: <20140210162621.46609.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: you can lead a horse to water, was Revision to Note Well
In-Reply-To: <CAP0PwYb-88_JsB=X+0aPLdQ5DAoUcYkPkxBQ58B9eTVE0nE2zw@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Feb 2014 16:26:46 -0000

>This is a healthy discussion.  However, if you really care about these
>issues (i.e., what constitutes "participation" in an IETF discussion for
>purposes of triggering an IPR disclosure) then debating it in the context
>of the "Note Well" language is, to put it mildly, a waste of time.  The
>actual "rules" that govern this issue are contained in BCP79, ...

I leared a long time ago that it is futile to try to make people pay
attention when they don't want to.  (Any parent of a teenager or of a
toddler can confirm this.)  So I don't see much point in a notice
beyond something like this:

		       This is an IETF meeting.

     The rules you agreed to when you registered, including those
      about conduct and about intellectual property apply here.

R's,
John

From dhc@dcrocker.net  Mon Feb 10 08:50: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 E79821A07E5 for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 08:50:01 -0800 (PST)
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 vtiPYHASaC7p for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 08:49:58 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4167E1A07E6 for <ietf@ietf.org>; Mon, 10 Feb 2014 08:49:56 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1AGnqiI007973 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 10 Feb 2014 08:49:56 -0800
Message-ID: <52F90309.5060503@dcrocker.net>
Date: Mon, 10 Feb 2014 08:49:13 -0800
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.3.0
MIME-Version: 1.0
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: you can lead a horse to water, was Revision to Note Well
References: <20140210162621.46609.qmail@joyce.lan>
In-Reply-To: <20140210162621.46609.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, 10 Feb 2014 08:49:56 -0800 (PST)
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, 10 Feb 2014 16:50:02 -0000

On 2/10/2014 8:26 AM, John Levine wrote:
> I leared a long time ago that it is futile to try to make people pay
> attention when they don't want to.
...
>                This is an IETF meeting.
>
>       The rules you agreed to when you registered, including those
>        about conduct and about intellectual property apply here.


This has nothing to do with 'want'.  The folks who don't 'want' to be 
responsible and play according to the rules won't, and they will find 
excuses to justify it.

The issue here is about doing proper due diligence that conforms to the 
the ability of average, well-intentioned folk to read and process a 
slide in real-time.  The limitations to that exercise are human 
cognition and attention, not free will.

And it is about the dangers of creating alternate versions of 
information, thereby inviting disparity in the message.

That's why I suggested a slide that is somewhat more informative than 
you offer, mostly by giving explicit pointers:


                              NOTE WELL

      PARTICIPATION IN THE IETF CARRIES ESSENTIAL OBLIGATIONS.

      IT IS YOUR RESPONSIBILITY TO BECOME FAMILIAR WITH THE DETAILS OF
      THOSE OBLIGATIONS AND TO ENSURE THAT YOU SATISFY THEM:

      *  IETF IPR Disclosures Policy, as specified in BCP 79

      *  IETF Anti-harassment Policy, as specified in
         ietf.org/iesg/statement/ietf-anti-harassment-policy.html




d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

From iad@ietf.org  Mon Feb 10 14:46:34 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 212961A05F2; Mon, 10 Feb 2014 14:46:34 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 22ZlGVuHXg32; Mon, 10 Feb 2014 14:46:31 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A16981A0459; Mon, 10 Feb 2014 14:46:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Administrative Director <iad@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: Ericsson to Host IETF 90 in Toronto!
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140210224631.12423.78795.idtracker@ietfa.amsl.com>
Date: Mon, 10 Feb 2014 14:46:31 -0800
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: Mon, 10 Feb 2014 22:46:34 -0000

The IAOC is pleased to announce that Ericsson will be the Host for IETF 90 in Toronto.  The 
meeting will be at the Fairmont Royal York from July 20 - 25, 2014.  
<http://www.fairmont.com/royal-york-toronto/>

You may recall Ericsson hosted IETF 66 in Montreal in 2006.  

Thanks Ericsson.  We cannot support the RFC Editor, Secretariat and the IETF meetings without 
the commitment and contributions of our many Hosts and Sponsors.  

Many sponsorship opportunities are still available:  
http://iaoc.ietf.org/documents/IETF-Sponsorship-Opportunities-20132002.pdf

If interested contact Andrew Dvorshak, dvorshak@isoc.org.

Just 20 days until IETF 89 in London!
Registration is open for IETF 89 at: http://www.ietf.org/meetings/89/

Once again, thank you Ericsson! 

See you in London!

Ray
IAD

2014 Meeting Venues

IETF 89  London  Hilton Metropole  March 2 - 7  Host:  ICANN
IETF 90  Toronto  Fairmont Royal York Hotel  July 20 - 25  Host:  Ericsson
IETF 91  Honolulu  Hilton Hawaiian Village  Nov 9 - 14  Host: Cisco

2015

IETF 92  Dallas  March 22 - 27  Host:  Your Name Here
IETF 93  Prague	  July 19 - 24  Host:  Your Name Here
IETF 94  Yokohama  Nov 1 - 6  Host:  WIDE


From mnot@mnot.net  Mon Feb 10 15:12:41 2014
Return-Path: <mnot@mnot.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 AABBA1A05F2 for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 15:12:41 -0800 (PST)
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 LtqqAWxlF6D0 for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 15:12:39 -0800 (PST)
Received: from mxout-07.mxes.net (mxout-07.mxes.net [216.86.168.182]) by ietfa.amsl.com (Postfix) with ESMTP id 7D0C01A02A1 for <ietf@ietf.org>; Mon, 10 Feb 2014 15:12:39 -0800 (PST)
Received: from [192.168.1.55] (unknown [118.209.47.254]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 4BC7322E2CB; Mon, 10 Feb 2014 18:12:31 -0500 (EST)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Invalid TLS certificates on example.[org,net,com]
Date: Tue, 11 Feb 2014 10:12:26 +1100
Message-Id: <D953B342-1789-4F05-8B2C-161124C29612@mnot.net>
To: IANA <iana@iana.org>
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
X-Mailer: Apple Mail (2.1827)
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: Mon, 10 Feb 2014 23:12:41 -0000

Hello,

The TLS certificates presented for example.org, example.net and =
example.com are not valid for those respective domains, resulting in a =
certificate error when navigated to from browsers. E.g.,

  https://example.org/

I'm getting feedback from the outside world that this is causing people =
*not* to use these domains as examples (e.g., in books) because it sends =
a bad message about security best practices.

Given the IETF's desire to a) promote good security practices, and b) =
promote the use of these domains as per RFC2606, could we please get =
these served with a valid certificate?

Thanks!

--
Mark Nottingham   http://www.mnot.net/




From hallam@gmail.com  Mon Feb 10 16:12: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 821761A066E for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 16:12:37 -0800 (PST)
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 j2lHkZd2MTpb for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 16:12:34 -0800 (PST)
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 6D4A31A060E for <ietf@ietf.org>; Mon, 10 Feb 2014 16:12:34 -0800 (PST)
Received: by mail-la0-f47.google.com with SMTP id hr17so5277231lab.6 for <ietf@ietf.org>; Mon, 10 Feb 2014 16:12:33 -0800 (PST)
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=eV++hepKtu1QbmBAaveAhY4LZ0yUUQMI6J6ZIFysj3Q=; b=CgV/Wsm88MdwD3J8H+9H1Q/mlHTqUJSv/B7mHDc6VBPb4hjALTYMgjNX+tuvznJuVD VNEyunkshqqlk5U0VfcnZFE2efs6zrv32I0sPEdhbs4HrxpojuADT9ek0Dl970qO7k9p VVpcwj/ijYDS8qklHs7T+qJXaMpTUcjI94PVEt70bI9QzpAsxVHeBphl2uSkQO51nZWJ fFnN6lHyUdSO0xueb0Xgz8lTsA0lvL1s8dOJc/f9aEnynr4J4Rhe9gYhYiPuoOPf/XR9 NNlIvlYVYj/HJUfYCZaQFGchoU+JmjxQx4DzAxv8KTFs0hEOSvH4rnAV0MrqV/Wt9+Mu IFxQ==
MIME-Version: 1.0
X-Received: by 10.112.158.131 with SMTP id wu3mr22737384lbb.6.1392077553254; Mon, 10 Feb 2014 16:12:33 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 10 Feb 2014 16:12:33 -0800 (PST)
In-Reply-To: <D953B342-1789-4F05-8B2C-161124C29612@mnot.net>
References: <D953B342-1789-4F05-8B2C-161124C29612@mnot.net>
Date: Mon, 10 Feb 2014 19:12:33 -0500
Message-ID: <CAMm+LwjSLN-HFc-ogqU5zVKy4fzSXG7Kjhf8Q-ACLdCOv2WZRA@mail.gmail.com>
Subject: Re: Invalid TLS certificates on example.[org,net,com]
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary=001a11c37b320fc63404f2165043
Cc: IANA <iana@iana.org>, 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, 11 Feb 2014 00:12:37 -0000

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

On Mon, Feb 10, 2014 at 6:12 PM, Mark Nottingham <mnot@mnot.net> wrote:

> Hello,
>
> The TLS certificates presented for example.org, example.net and
> example.com are not valid for those respective domains, resulting in a
> certificate error when navigated to from browsers. E.g.,
>
>   https://example.org/
>
> I'm getting feedback from the outside world that this is causing people
> *not* to use these domains as examples (e.g., in books) because it sends a
> bad message about security best practices.
>
> Given the IETF's desire to a) promote good security practices, and b)
> promote the use of these domains as per RFC2606, could we please get these
> served with a valid certificate?
>

I don't think they know they have SSL on those domains, let alone intended
to deploy.

SSL has a protocol boo-boo in that the original designer didn't realize
IPv4 exhaustion was going to be an issue. So the original SSL protocol did
not include the domain the client is trying to connect to in the handshake
(since fixed).

As a result it is possible to use https to connect to about 80% of the
sites on the net if you will accept a cert for a completely different
domain.

Peter Eckersley at the EFF is currently trying to use this for his 'ssl
everywhere' hack. Which is great for blocking pervasive intercept and no
good against an active attack or to establish accountability.



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

--001a11c37b320fc63404f2165043
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, Feb 10, 2014 at 6:12 PM, Mark Nottingham <span dir=3D"ltr">=
&lt;<a href=3D"mailto:mnot@mnot.net" target=3D"_blank">mnot@mnot.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">Hello,<br>
<br>
The TLS certificates presented for <a href=3D"http://example.org" target=3D=
"_blank">example.org</a>, <a href=3D"http://example.net" target=3D"_blank">=
example.net</a> and <a href=3D"http://example.com" target=3D"_blank">exampl=
e.com</a> are not valid for those respective domains, resulting in a certif=
icate error when navigated to from browsers. E.g.,<br>

<br>
=A0 <a href=3D"https://example.org/" target=3D"_blank">https://example.org/=
</a><br>
<br>
I&#39;m getting feedback from the outside world that this is causing people=
 *not* to use these domains as examples (e.g., in books) because it sends a=
 bad message about security best practices.<br>
<br>
Given the IETF&#39;s desire to a) promote good security practices, and b) p=
romote the use of these domains as per RFC2606, could we please get these s=
erved with a valid certificate?<br></blockquote><div><br></div><div>I don&#=
39;t think they know they have SSL on those domains, let alone intended to =
deploy.</div>
<div><br></div><div>SSL has a protocol boo-boo in that the original designe=
r didn&#39;t realize IPv4 exhaustion was going to be an issue. So the origi=
nal SSL protocol did not include the domain the client is trying to connect=
 to in the handshake (since fixed).</div>
<div><br></div><div>As a result it is possible to use https to connect to a=
bout 80% of the sites on the net if you will accept a cert for a completely=
 different domain.</div><div><br></div><div>Peter Eckersley at the EFF is c=
urrently trying to use this for his &#39;ssl everywhere&#39; hack. Which is=
 great for blocking pervasive intercept and no good against an active attac=
k or to establish accountability.</div>
<div>=A0</div></div><br clear=3D"all"><div><br></div>-- <br>Website: <a hre=
f=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11c37b320fc63404f2165043--


From johnl@iecc.com  Mon Feb 10 20:41:12 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 4B41B1A079C for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 20:41:12 -0800 (PST)
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 WOzE8l_QshvB for <ietf@ietfa.amsl.com>; Mon, 10 Feb 2014 20:41:11 -0800 (PST)
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 CDE9C1A0238 for <ietf@ietf.org>; Mon, 10 Feb 2014 20:41:09 -0800 (PST)
Received: (qmail 55019 invoked from network); 11 Feb 2014 04:41:08 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 11 Feb 2014 04:41:08 -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=52f9a9e4.xn--btvx9d.k1402; i=johnl@user.iecc.com; bh=w9ZZpn09Fzy789j2kzt2WoyJV3fOwwURhl9e2YghLPI=; b=UKMINxpiNB990wIzMCOZKGdnIrvPyzBAWx4V+D0zNG+Nb8t/8EGu8bOZKVTcKwdkMJ93IYcv7OtqFCh8AxJOJGvASIjC8z8e25ZU7zm3vkX1TgTl2DWnCr1jkxvV3RjeMiF95MzmAN74bCgLXiiBuEZcCqABCMT/VyDV1cx9BN2vVUMFG1TRVK2EDDCWW6/1Sht3f8OaGNJIZXN6XPohssh/ECaIfe2XX1W35FVfjgWjaozx1/rlJZHplDVhlzX9
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=52f9a9e4.xn--btvx9d.k1402; bh=w9ZZpn09Fzy789j2kzt2WoyJV3fOwwURhl9e2YghLPI=; b=MHnJiROCqQD+6vs03CyKqy2sN1cXAHzcAfFCSD6O7nJPjf7vPfZuFa9rqV5nsAcSCqmdZC6wFagX8+Qykns5/cFOPhXCBP9LhnTZ46H+znAnMsPf2DQ1lju5ypF/HGdDMWjAT6A7qChuvlxbOLDeLQ6fm6HYSipNmaAqqBZQhepx4ZtO/Wbd9iXti1U8ftWIufxHpZ5ho0fKSIAUoQXfuB6ETqNGHdoTwHNWkWc7elvtVZL3rIR2e9PdpYeLcLu+
Date: 11 Feb 2014 04:40:46 -0000
Message-ID: <20140211044046.49174.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Invalid TLS certificates on example.[org,net,com]
In-Reply-To: <CAMm+LwjSLN-HFc-ogqU5zVKy4fzSXG7Kjhf8Q-ACLdCOv2WZRA@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Feb 2014 04:41:12 -0000

>I don't think they know they have SSL on those domains, let alone intended
>to deploy.

In this case, the cert is from Edgecast, the CDN where the three
domains are hosted.  It looks like a straightforward config error.


From mariainesrobles@googlemail.com  Tue Feb 11 05:00:21 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4A451A008E; Tue, 11 Feb 2014 05:00:21 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 oMop92kH5ecS; Tue, 11 Feb 2014 05:00:18 -0800 (PST)
Received: from mail-vb0-x22d.google.com (mail-vb0-x22d.google.com [IPv6:2607:f8b0:400c:c02::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 4C5D41A01F5; Tue, 11 Feb 2014 05:00:02 -0800 (PST)
Received: by mail-vb0-f45.google.com with SMTP id m10so5925545vbh.32 for <multiple recipients>; Tue, 11 Feb 2014 05:00:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=K/35HLvc2O6vIpnatLchvwSRG/VWJno2aVgUQtZe/og=; b=xQBdslz4wHHp8JwHLAFnmfLEDWaAe5o7b48QrJ6tYBelJ2V2sbH6ZwtkZWFn8Qo7w2 w1s87/gRYRs3tCZrYpTLfDVuugeh7DwKveGwXkPgGYFpduDfxrOZI+yo1xoAFKGpRgdp HpKFeV/ZT9fMZVxoLAaNGFavIbzysCUXMjc7d5Zcl6xwBkn7yTmXJlGjf7Nq2R42gauB 160/poTO0sWdKCM0pkMpBKfuwEcOGqKtuksXWcB16fCjXdRmV1jhvDUPdQoZjFcA4Hxv HLDPbtgnPlprMSJd6aNQFFD1rppCayJcsWydfnWKbuJQ/kcieEUJpRejXE7iUK8lGJnf wDjg==
MIME-Version: 1.0
X-Received: by 10.52.106.107 with SMTP id gt11mr24075848vdb.7.1392123601554; Tue, 11 Feb 2014 05:00:01 -0800 (PST)
Received: by 10.220.49.68 with HTTP; Tue, 11 Feb 2014 05:00:01 -0800 (PST)
In-Reply-To: <CABOxzu1PQ0kDTapvALbiARfDqECSamC8urZm6+B4HjnSTJ3Yqw@mail.gmail.com>
References: <20140124201637.988.3372.idtracker@ietfa.amsl.com> <CABOxzu1PQ0kDTapvALbiARfDqECSamC8urZm6+B4HjnSTJ3Yqw@mail.gmail.com>
Date: Tue, 11 Feb 2014 11:00:01 -0200
Message-ID: <CAP+sJUdiF9oJgL_p-H7_SUGWFs=NFPnWsRQDUV7M5-n1c-_p-w@mail.gmail.com>
Subject: Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-06.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
From: Ines  Robles <mariainesrobles@googlemail.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Content-Type: multipart/alternative; boundary=001a1133ccf6c112d404f2210874
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, 11 Feb 2014 13:00:22 -0000

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

Thank you Kerry for your comments,

It will be addressed by the authors.

Kind Regards,


2014-02-10 16:44 GMT-03:00 Kerry Lynn <kerlyn@ieee.org>:

> Hi Jonathan,
>
> I apologize for the fact that these comments/questions are late but offer
> them anyway...
>
>
> 3. Applicability Statement
>
> OLD:
>
>    Operationally, the scope of this protocol is administratively
>    determined.  In other words, the scope of dissemination is determined
>    by routers configured to disallow transmission or reception of MPL
>    messages on a subset of interfaces.
>
>
> This language predates the alignment with I-D.ietf-6man-multicast-scopes
> and I suspect
> it is no longer generally true.  I recommend deleting it.
>
>
> 4.1.  MPL Domains
>
> OLD:
>
>    When MPL is used in deployments that use administratively defined
>    scopes that cover, for example, multiple subnets based on different
>    underlying network technologies, Admin-Local scope (scop value 4) and
>    /or Site-Local scope (scop value 5) SHOULD be used.
>
>
> I'm not clear on whether, in deployments where scop values 4 and/or 5 are
> in use, a node
> should participate in the ALL_MPL_FORWARDERS multicast address for each
> multicast
> scope in use or just the highest scope in use.
>
>
> 5.4  MPL Forwarder Parameters
>
> OLD:
>
>    PROACTIVE_FORWARDING  A boolean value that indicates whether the MPL
>       Forwarder schedules MPL Data Message transmissions after receiving
>       them for the first time.  It is RECOMMENDED that all MPL
>       Interfaces attached to the same link of a given MPL Domain use the
>       same value for PROACTIVE_FORWARDING and has a default value of
>       TRUE.  The mechanism for setting PROACTIVE_FORWARDING is not
>       specified within this document.
>
>    SEED_SET_ENTRY_LIFETIME  The minimum lifetime for an entry in the
>       Seed Set.  SEED_SET_ENTRY_LIFETIME has a default value of 30
>       minutes.  It is RECOMMENDED that all MPL Forwarders use the same
>       value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and has a
>       default value of 30 minutes.  The mechanism for setting
>       SEED_SET_ENTRY_LIFETIME is not specified within this document.
>
>
> NEW:
>
>       ...
>       PROACTIVE_FORWARDING has a default value of TRUE.
>
>       ...
>       It is RECOMMENDED that all MPL Forwarders use the same
>       value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and *use* a
>       default value of 30 minutes.
>
> I think you were already planning to delete the RECOMMEND that all MPL
> Interfaces
> on the same link use the same value for PROACTIVE_FORWARDING.  The second
> suggestion is just grammatical.
>
> Regards, -K-
>
>
>
>
> On Fri, Jan 24, 2014 at 3:16 PM, The IESG <iesg-secretary@ietf.org> wrote:
>
>> The IESG has received a request from the Routing Over Low power and Lossy
>> networks WG (roll) to consider the following document:
>> - 'Multicast Protocol for Low power and Lossy Networks (MPL)'
>>   <draft-ietf-roll-trickle-mcast-06.txt> as Proposed Standard
>>
>> This is a second last call, the first one having been abandoned to send
>> the document back to the working group. But the latest revision addresses
>> comments that were received during the first last call.
>>
>> 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-02-07. 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 specifies the Multicast Protocol for Low power and
>>    Lossy Networks (MPL) that provides IPv6 multicast forwarding in
>>    constrained networks.  MPL avoids the need to construct or maintain
>>    any multicast forwarding topology, disseminating messages to all MPL
>>    Forwarders in an MPL Domain.  MPL uses the Trickle algorithm to
>>    manage message transmissions for both control and data-plane
>>    messages.  Different Trickle parameter configurations allow MPL to
>>    trade between dissemination latency and transmission efficiency.
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ballot/
>>
>>
>> The following IPR Declarations may be related to this I-D:
>>
>>    http://datatracker.ietf.org/ipr/1858/
>>
>>
>>
>> _______________________________________________
>> Roll mailing list
>> Roll@ietf.org
>> https://www.ietf.org/mailman/listinfo/roll
>>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>
>

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

<div dir=3D"ltr">Thank you Kerry for your comments,<div><br></div><div>It w=
ill be addressed by the authors.</div><div><br></div><div>Kind Regards,</di=
v><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">2014-02-10 =
16:44 GMT-03:00 Kerry Lynn <span dir=3D"ltr">&lt;<a href=3D"mailto:kerlyn@i=
eee.org" target=3D"_blank">kerlyn@ieee.org</a>&gt;</span>:<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><div><div><div>Hi Jonathan,<br></div><div><br>I apologize for the f=
act that these comments/questions are late but offer them anyway...<br>
<br><br></div>3. Applicability Statement<br>
</div><div><br></div>OLD:<br><pre>   Operationally, the scope of this proto=
col is administratively
   determined.  In other words, the scope of dissemination is determined
   by routers configured to disallow transmission or reception of MPL
   messages on a subset of interfaces.

</pre>This language predates the alignment with I-D.ietf-6man-multicast-sco=
pes and I suspect<br>it is no longer generally true.=A0 I recommend deletin=
g it.<br></div></div><br><br></div>4.1.=A0 MPL Domains<br><br></div>OLD:<br=
>


<pre>   When MPL is used in deployments that use administratively defined
   scopes that cover, for example, multiple subnets based on different
   underlying network technologies, Admin-Local scope (scop value 4) and
   /or Site-Local scope (scop value 5) SHOULD be used.<br>=A0</pre></div>I&=
#39;m not clear on whether, in deployments where scop values 4 and/or 5 are=
 in use, a node<br>should participate in the ALL_MPL_FORWARDERS multicast a=
ddress for each multicast<br>


</div>scope in use or just the highest scope in use.<br><br><br></div>5.4=
=A0 MPL Forwarder Parameters<br><br></div>OLD:<br><pre>   PROACTIVE_FORWARD=
ING  A boolean value that indicates whether the MPL
      Forwarder schedules MPL Data Message transmissions after receiving
      them for the first time.  It is RECOMMENDED that all MPL
      Interfaces attached to the same link of a given MPL Domain use the
      same value for PROACTIVE_FORWARDING and has a default value of
      TRUE.  The mechanism for setting PROACTIVE_FORWARDING is not
      specified within this document.

   SEED_SET_ENTRY_LIFETIME  The minimum lifetime for an entry in the
      Seed Set.  SEED_SET_ENTRY_LIFETIME has a default value of 30
      minutes.  It is RECOMMENDED that all MPL Forwarders use the same
      value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and has a
      default value of 30 minutes.  The mechanism for setting
      SEED_SET_ENTRY_LIFETIME is not specified within this document.
</pre><br><div><div>NEW:<br><pre>      ...<br>      PROACTIVE_FORWARDING ha=
s a default value of TRUE.</pre><pre>      ...<br>      It is RECOMMENDED t=
hat all MPL Forwarders use the same
      value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and <u>use</=
u> a
      default value of 30 minutes.</pre>I think you were already planning t=
o delete the RECOMMEND that all MPL Interfaces<br>on the same link use the =
same value for PROACTIVE_FORWARDING.=A0 The second<br>suggestion is just gr=
ammatical.<br>

</div><div><br>Regards, -K-<br><br><br></div></div></div><div class=3D"HOEn=
Zb"><div class=3D"h5"><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">On Fri, Jan 24, 2014 at 3:16 PM, The IESG <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secretary@i=
etf.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">The IESG has received a request from the Rou=
ting Over Low power and Lossy<br>
networks WG (roll) to consider the following document:<br>
- &#39;Multicast Protocol for Low power and Lossy Networks (MPL)&#39;<br>
=A0 &lt;draft-ietf-roll-trickle-mcast-06.txt&gt; as Proposed Standard<br>
<br>
This is a second last call, the first one having been abandoned to send<br>
the document back to the working group. But the latest revision addresses<b=
r>
comments that were received during the first last call.<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a> mailin=
g lists by 2014-02-07. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a=
> instead. In either case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
=A0 =A0This document specifies the Multicast Protocol for Low power and<br>
=A0 =A0Lossy Networks (MPL) that provides IPv6 multicast forwarding in<br>
=A0 =A0constrained networks. =A0MPL avoids the need to construct or maintai=
n<br>
=A0 =A0any multicast forwarding topology, disseminating messages to all MPL=
<br>
=A0 =A0Forwarders in an MPL Domain. =A0MPL uses the Trickle algorithm to<br=
>
=A0 =A0manage message transmissions for both control and data-plane<br>
=A0 =A0messages. =A0Different Trickle parameter configurations allow MPL to=
<br>
=A0 =A0trade between dissemination latency and transmission efficiency.<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/" =
target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-m=
cast/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ba=
llot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-roll-tr=
ickle-mcast/ballot/</a><br>
<br>
<br>
The following IPR Declarations may be related to this I-D:<br>
<br>
=A0 =A0<a href=3D"http://datatracker.ietf.org/ipr/1858/" target=3D"_blank">=
http://datatracker.ietf.org/ipr/1858/</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org" target=3D"_blank">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/roll</a><br>
</blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/roll</a><br>
<br></blockquote></div><br></div></div>

--001a1133ccf6c112d404f2210874--


From mariainesrobles@googlemail.com  Tue Feb 11 05:25:28 2014
Return-Path: <mariainesrobles@googlemail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346201A02C6 for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 05:25:28 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-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 hJ1eNO1MhCOI for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 05:25:23 -0800 (PST)
Received: from mail-vb0-x235.google.com (mail-vb0-x235.google.com [IPv6:2607:f8b0:400c:c02::235]) by ietfa.amsl.com (Postfix) with ESMTP id 973C51A008E for <ietf@ietf.org>; Tue, 11 Feb 2014 05:25:23 -0800 (PST)
Received: by mail-vb0-f53.google.com with SMTP id p17so5723696vbe.26 for <ietf@ietf.org>; Tue, 11 Feb 2014 05:25:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=HK3JC/t1LQioNrBkoq6p2TVISXqFgrwIshGR8bEaQDE=; b=WYpXDiZvRpWDnwst+CDqacxuFXIRCbIm6bwVhKfchxqejnVVoYWbDo9VG+vrGoTWPu PWZ5T4rHL5iAPAG4KEm/CLzHSIwHkRa5n2cy6FFIyQGusFYTna/KiTEFUzfvgTBrJp18 aV6L3VJIsks4tOU+004T2tD5ZsUewo9UtT3iPY19m6i4zAhshnyHr/2MRQic3s0YtucS mzCxnHt66dWX5AipU/ciHpOY1cZu2xuEZ14mWvPiJYZdP7v2iLRn1YpJ3jJxyFo2A7bH 4SUrG6zxFcF1B/3se5YoyVkF5ibvbcgqckDos/2mK93acP2516YjuOd3WF4QdCmedcPF y50g==
MIME-Version: 1.0
X-Received: by 10.52.187.232 with SMTP id fv8mr49859vdc.60.1392125122970; Tue, 11 Feb 2014 05:25:22 -0800 (PST)
Received: by 10.220.49.68 with HTTP; Tue, 11 Feb 2014 05:25:22 -0800 (PST)
Date: Tue, 11 Feb 2014 11:25:22 -0200
Message-ID: <CAP+sJUf5bjFvYREZGwA_tzWZV1-EUn843cjDpoHKaGmJNwUVcw@mail.gmail.com>
Subject: Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-06.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
From: Ines  Robles <mariainesrobles@googlemail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec548a60370080604f22163a0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Feb 2014 13:25:28 -0000

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

Please disregard this email, I made a mistake

Thanks and Regards,

Ines .

--bcaec548a60370080604f22163a0
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr"><div class="gmail_extra" style>Please disregard this email, I made a mistake</div><div class="gmail_extra" style><br></div><div class="gmail_extra" style>Thanks and Regards,</div><div class="gmail_extra" style>
<br></div><div class="gmail_extra" style>Ines .</div></div>

--bcaec548a60370080604f22163a0--


From jari.arkko@piuha.net  Tue Feb 11 07:41:04 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 8A8941A05D2 for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 07:41:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SgXkD4_vVn33 for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 07:41:02 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 91EAB1A01A8 for <ietf@ietf.org>; Tue, 11 Feb 2014 07:41:01 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C2A512CED5; Tue, 11 Feb 2014 17:41:00 +0200 (EET)
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 EHRo2WtXWIUp; Tue, 11 Feb 2014 17:41:00 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id D5DE32CC48; Tue, 11 Feb 2014 17:40:59 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Revision to Note Well
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAP0PwYb-88_JsB=X+0aPLdQ5DAoUcYkPkxBQ58B9eTVE0nE2zw@mail.gmail.com>
Date: Tue, 11 Feb 2014 10:40:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <287F04BC-376F-4EA1-9851-BBE66DB4D04A@piuha.net>
References: <CAL02cgTb6V7v+mut37eJb0wag8zLFzHU0ABCFLEVJqaQrhuUkg@mail.gmail.com> <52F3E3F6.7010705@gmail.com> <80BECC67-70A2-4A85-9B17-A0E2121353B1@netapp.com> <52F517C2.1050609@qti.qualcomm.com> <C60A2587A4A8D4508287CE0C@JcK-HP8200.jck.com> <CAP0PwYb-88_JsB=X+0aPLdQ5DAoUcYkPkxBQ58B9eTVE0nE2zw@mail.gmail.com>
To: Jorge Contreras <cntreras@gmail.com>
X-Mailer: Apple Mail (2.1510)
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, 11 Feb 2014 15:41:04 -0000

What Jorge said. You can discuss on the IPR list at =
https://www.ietf.org/mailman/listinfo/ipr-wg

Jari

On Feb 10, 2014, at 9:13 AM, Jorge Contreras <cntreras@gmail.com> wrote:

> This is a healthy discussion.  However, if you really care about these =
issues (i.e., what constitutes "participation" in an IETF discussion for =
purposes of triggering an IPR disclosure) then debating it in the =
context of the "Note Well" language is, to put it mildly, a waste of =
time.  The actual "rules" that govern this issue are contained in BCP79, =
which is in the process of being revised right now.  This exact issue =
has been discussed repeatedly in the IPR WG and the rules in BCP79 are =
being amended *right now* to deal with concerns that were raised.  If =
you care and want to discuss in some way that may actually affect the =
IETF rules, rather than a non-substantive pointer to the rules (i.e., =
"Note Well"), please take a look at the latest I-D implementing these =
rules and comment on it:
>=20
> https://datatracker.ietf.org/doc/draft-bradner-rfc3979bis/
>=20
> The relevant Sections are 1.c ("Contribution") and 1.k, which actually =
defines "Participating in an IETF Discussion or Activity".
>=20
> Enjoy!
>=20
> Jorge


From kerlyn2001@gmail.com  Mon Feb 10 11:44:39 2014
Return-Path: <kerlyn2001@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 A8A8E1A0863; Mon, 10 Feb 2014 11:44:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level: 
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, 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 sYZTFIipEj6a; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
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 812F21A03C9; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
Received: by mail-oa0-f54.google.com with SMTP id i4so8029826oah.41 for <multiple recipients>; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
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:content-type; bh=+l5MMlxfcTnmu3jCJZZG/V2FsAccXTcdA9SQDuYOavw=; b=pDF34w7glcnLIyc5nk8oDkOITWTeJumk9qLjBF6TFK21dUhKMaFsVbjZzA01OnrXAf PzcsRkX4rFTnXxUVYQUvsmXACfiHJZExOzCPLIU3TzHoLblyNarekpgfdStwDx1xW5pw SbSTUteZc2D9Pu50EsxkzgllMdmB40lo8a4J1p3XvLOddopqsk5uPAjP0/7fzXNrUTAi kq1qrwD3Y3EB/ZX7UA/T1doLI62r2IzWbh+m/dam5oxrX6I55uKEch1JRCRZbfWg0OeA r7e5ZGV1Mua74sz4m/u/milZiaxG4qG3cuiMm8llKRFT0B0GQLu4Uojp3bE1EjqaZYc9 cyQg==
MIME-Version: 1.0
X-Received: by 10.182.148.106 with SMTP id tr10mr2167834obb.65.1392061476095;  Mon, 10 Feb 2014 11:44:36 -0800 (PST)
Sender: kerlyn2001@gmail.com
Received: by 10.60.83.10 with HTTP; Mon, 10 Feb 2014 11:44:36 -0800 (PST)
In-Reply-To: <20140124201637.988.3372.idtracker@ietfa.amsl.com>
References: <20140124201637.988.3372.idtracker@ietfa.amsl.com>
Date: Mon, 10 Feb 2014 14:44:36 -0500
X-Google-Sender-Auth: KeKhyEm9k2Y5uMX3zv8_-hpAx9I
Message-ID: <CABOxzu1PQ0kDTapvALbiARfDqECSamC8urZm6+B4HjnSTJ3Yqw@mail.gmail.com>
Subject: Re: [Roll] Last Call: <draft-ietf-roll-trickle-mcast-06.txt> (Multicast Protocol for Low power and Lossy Networks (MPL)) to Proposed Standard
From: Kerry Lynn <kerlyn@ieee.org>
To: ietf@ietf.org, Routing Over Low power and Lossy networks <roll@ietf.org>, Jonathan Hui <jonhui@cisco.com>
Content-Type: multipart/alternative; boundary=089e012940d8c9d00804f2129155
X-Mailman-Approved-At: Tue, 11 Feb 2014 08:02:39 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Feb 2014 19:44:39 -0000

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

Hi Jonathan,

I apologize for the fact that these comments/questions are late but offer
them anyway...


3. Applicability Statement

OLD:

   Operationally, the scope of this protocol is administratively
   determined.  In other words, the scope of dissemination is determined
   by routers configured to disallow transmission or reception of MPL
   messages on a subset of interfaces.


This language predates the alignment with I-D.ietf-6man-multicast-scopes
and I suspect
it is no longer generally true.  I recommend deleting it.


4.1.  MPL Domains

OLD:

   When MPL is used in deployments that use administratively defined
   scopes that cover, for example, multiple subnets based on different
   underlying network technologies, Admin-Local scope (scop value 4) and
   /or Site-Local scope (scop value 5) SHOULD be used.


I'm not clear on whether, in deployments where scop values 4 and/or 5 are
in use, a node
should participate in the ALL_MPL_FORWARDERS multicast address for each
multicast
scope in use or just the highest scope in use.


5.4  MPL Forwarder Parameters

OLD:

   PROACTIVE_FORWARDING  A boolean value that indicates whether the MPL
      Forwarder schedules MPL Data Message transmissions after receiving
      them for the first time.  It is RECOMMENDED that all MPL
      Interfaces attached to the same link of a given MPL Domain use the
      same value for PROACTIVE_FORWARDING and has a default value of
      TRUE.  The mechanism for setting PROACTIVE_FORWARDING is not
      specified within this document.

   SEED_SET_ENTRY_LIFETIME  The minimum lifetime for an entry in the
      Seed Set.  SEED_SET_ENTRY_LIFETIME has a default value of 30
      minutes.  It is RECOMMENDED that all MPL Forwarders use the same
      value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and has a
      default value of 30 minutes.  The mechanism for setting
      SEED_SET_ENTRY_LIFETIME is not specified within this document.


NEW:

      ...
      PROACTIVE_FORWARDING has a default value of TRUE.

      ...
      It is RECOMMENDED that all MPL Forwarders use the same
      value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and *use* a
      default value of 30 minutes.

I think you were already planning to delete the RECOMMEND that all MPL
Interfaces
on the same link use the same value for PROACTIVE_FORWARDING.  The second
suggestion is just grammatical.

Regards, -K-




On Fri, Jan 24, 2014 at 3:16 PM, The IESG <iesg-secretary@ietf.org> wrote:

> The IESG has received a request from the Routing Over Low power and Lossy
> networks WG (roll) to consider the following document:
> - 'Multicast Protocol for Low power and Lossy Networks (MPL)'
>   <draft-ietf-roll-trickle-mcast-06.txt> as Proposed Standard
>
> This is a second last call, the first one having been abandoned to send
> the document back to the working group. But the latest revision addresses
> comments that were received during the first last call.
>
> 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-02-07. 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 specifies the Multicast Protocol for Low power and
>    Lossy Networks (MPL) that provides IPv6 multicast forwarding in
>    constrained networks.  MPL avoids the need to construct or maintain
>    any multicast forwarding topology, disseminating messages to all MPL
>    Forwarders in an MPL Domain.  MPL uses the Trickle algorithm to
>    manage message transmissions for both control and data-plane
>    messages.  Different Trickle parameter configurations allow MPL to
>    trade between dissemination latency and transmission efficiency.
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ballot/
>
>
> The following IPR Declarations may be related to this I-D:
>
>    http://datatracker.ietf.org/ipr/1858/
>
>
>
> _______________________________________________
> Roll mailing list
> Roll@ietf.org
> https://www.ietf.org/mailman/listinfo/roll
>

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

<div dir=3D"ltr"><div><div><div><div><div><div><div><div><div><div>Hi Jonat=
han,<br></div><div><br>I apologize for the fact that these comments/questio=
ns are late but offer them anyway...<br><br><br></div>3. Applicability Stat=
ement<br>
</div><div><br></div>OLD:<br><pre>   Operationally, the scope of this proto=
col is administratively
   determined.  In other words, the scope of dissemination is determined
   by routers configured to disallow transmission or reception of MPL
   messages on a subset of interfaces.

</pre>This language predates the alignment with I-D.ietf-6man-multicast-sco=
pes and I suspect<br>it is no longer generally true.=A0 I recommend deletin=
g it.<br></div></div><br><br></div>4.1.=A0 MPL Domains<br><br></div>OLD:<br=
>

<pre>   When MPL is used in deployments that use administratively defined
   scopes that cover, for example, multiple subnets based on different
   underlying network technologies, Admin-Local scope (scop value 4) and
   /or Site-Local scope (scop value 5) SHOULD be used.<br>=A0</pre></div>I&=
#39;m not clear on whether, in deployments where scop values 4 and/or 5 are=
 in use, a node<br>should participate in the ALL_MPL_FORWARDERS multicast a=
ddress for each multicast<br>

</div>scope in use or just the highest scope in use.<br><br><br></div>5.4=
=A0 MPL Forwarder Parameters<br><br></div>OLD:<br><pre>   PROACTIVE_FORWARD=
ING  A boolean value that indicates whether the MPL
      Forwarder schedules MPL Data Message transmissions after receiving
      them for the first time.  It is RECOMMENDED that all MPL
      Interfaces attached to the same link of a given MPL Domain use the
      same value for PROACTIVE_FORWARDING and has a default value of
      TRUE.  The mechanism for setting PROACTIVE_FORWARDING is not
      specified within this document.

   SEED_SET_ENTRY_LIFETIME  The minimum lifetime for an entry in the
      Seed Set.  SEED_SET_ENTRY_LIFETIME has a default value of 30
      minutes.  It is RECOMMENDED that all MPL Forwarders use the same
      value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and has a
      default value of 30 minutes.  The mechanism for setting
      SEED_SET_ENTRY_LIFETIME is not specified within this document.
</pre><br><div><div>NEW:<br><pre>      ...<br>      PROACTIVE_FORWARDING ha=
s a default value of TRUE.</pre><pre>      ...<br>      It is RECOMMENDED t=
hat all MPL Forwarders use the same
      value for SEED_SET_ENTRY_LIFETIME for a given MPL Domain and <u>use</=
u> a
      default value of 30 minutes.</pre>I think you were already planning t=
o delete the RECOMMEND that all MPL Interfaces<br>on the same link use the =
same value for PROACTIVE_FORWARDING.=A0 The second<br>suggestion is just gr=
ammatical.<br>
</div><div><br>Regards, -K-<br><br><br></div></div></div><div class=3D"gmai=
l_extra"><br><br><div class=3D"gmail_quote">On Fri, Jan 24, 2014 at 3:16 PM=
, The IESG <span dir=3D"ltr">&lt;<a href=3D"mailto:iesg-secretary@ietf.org"=
 target=3D"_blank">iesg-secretary@ietf.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">The IESG has received a request from the Rou=
ting Over Low power and Lossy<br>
networks WG (roll) to consider the following document:<br>
- &#39;Multicast Protocol for Low power and Lossy Networks (MPL)&#39;<br>
=A0 &lt;draft-ietf-roll-trickle-mcast-06.txt&gt; as Proposed Standard<br>
<br>
This is a second last call, the first one having been abandoned to send<br>
the document back to the working group. But the latest revision addresses<b=
r>
comments that were received during the first last call.<br>
<br>
The IESG plans to make a decision in the next few weeks, and solicits<br>
final comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2014-02=
-07. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the<br>
beginning of the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
=A0 =A0This document specifies the Multicast Protocol for Low power and<br>
=A0 =A0Lossy Networks (MPL) that provides IPv6 multicast forwarding in<br>
=A0 =A0constrained networks. =A0MPL avoids the need to construct or maintai=
n<br>
=A0 =A0any multicast forwarding topology, disseminating messages to all MPL=
<br>
=A0 =A0Forwarders in an MPL Domain. =A0MPL uses the Trickle algorithm to<br=
>
=A0 =A0manage message transmissions for both control and data-plane<br>
=A0 =A0messages. =A0Different Trickle parameter configurations allow MPL to=
<br>
=A0 =A0trade between dissemination latency and transmission efficiency.<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/" =
target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-m=
cast/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"http://datatracker.ietf.org/doc/draft-ietf-roll-trickle-mcast/ba=
llot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-ietf-roll-tr=
ickle-mcast/ballot/</a><br>
<br>
<br>
The following IPR Declarations may be related to this I-D:<br>
<br>
=A0 =A0<a href=3D"http://datatracker.ietf.org/ipr/1858/" target=3D"_blank">=
http://datatracker.ietf.org/ipr/1858/</a><br>
<br>
<br>
<br>
_______________________________________________<br>
Roll mailing list<br>
<a href=3D"mailto:Roll@ietf.org">Roll@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/roll" target=3D"_blank">ht=
tps://www.ietf.org/mailman/listinfo/roll</a><br>
</blockquote></div><br></div>

--089e012940d8c9d00804f2129155--

From housley@vigilsec.com  Tue Feb 11 13:11:06 2014
Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6821A06DD; Tue, 11 Feb 2014 13:11:06 -0800 (PST)
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 YgA-ngH_73rQ; Tue, 11 Feb 2014 13:11:04 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6FEF81A06F2; Tue, 11 Feb 2014 13:11:02 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 36B0C9A42C4; Tue, 11 Feb 2014 16:10:53 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id 2wXXwafOrHSn; Tue, 11 Feb 2014 16:10:30 -0500 (EST)
Received: from [172.20.40.95] (unknown [12.189.153.253]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 48D2A9A42B0; Tue, 11 Feb 2014 16:10:32 -0500 (EST)
Subject: Re: Last Call: <draft-ietf-sidr-policy-qualifiers-01.txt> (Policy Qualifiers in RPKI Certificates) to Proposed Standard
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <20140211131635.4764.88322.idtracker@ietfa.amsl.com>
Date: Tue, 11 Feb 2014 16:10:24 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C3F924B-EDFF-42BC-9075-D4930636E643@vigilsec.com>
References: <20140211131635.4764.88322.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.1085)
Cc: IETF SIDR <sidr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Feb 2014 21:11:06 -0000

Implementers do not do anything with a CPS pointer in a policy =
qualifier.  So, this addition will not impact interoperability.  That =
said, I understand that some people want this notice in the certificate, =
and I see no reason to prevent this document form moving forward.

Russ


On Feb 11, 2014, at 8:16 AM, The IESG wrote:
>=20
> The IESG has received a request from the Secure Inter-Domain Routing =
WG
> (sidr) to consider the following document:
> - 'Policy Qualifiers in RPKI Certificates'
>  <draft-ietf-sidr-policy-qualifiers-01.txt> as Proposed 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-02-25. 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
>   This document updates RFC 6487 by clarifying the inclusion of policy
>   qualifiers in the certificate policies extension of RPKI resource
>   certificates.
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-ietf-sidr-policy-qualifiers/
>=20
> IESG discussion can be tracked via
> =
http://datatracker.ietf.org/doc/draft-ietf-sidr-policy-qualifiers/ballot/
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20


From randy@psg.com  Tue Feb 11 15:09:41 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 AC3261A07B8; Tue, 11 Feb 2014 15:09:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LobSoQa7-MrN; Tue, 11 Feb 2014 15:09:40 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 067861A0728; Tue, 11 Feb 2014 15:09:40 -0800 (PST)
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 1WDMSQ-0000mj-I2; Tue, 11 Feb 2014 23:09:39 +0000
Date: Wed, 12 Feb 2014 08:09:37 +0900
Message-ID: <m2ha85tff2.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Russ Housley <housley@vigilsec.com>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-policy-qualifiers-01.txt>	(Policy Qualifiers in RPKI Certificates) to Proposed Standard
In-Reply-To: <6C3F924B-EDFF-42BC-9075-D4930636E643@vigilsec.com>
References: <20140211131635.4764.88322.idtracker@ietfa.amsl.com> <6C3F924B-EDFF-42BC-9075-D4930636E643@vigilsec.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
Cc: ietf@ietf.org, IETF SIDR <sidr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Feb 2014 23:09:41 -0000

> Implementers do not do anything with a CPS pointer in a policy
> qualifier.  So, this addition will not impact interoperability.

in other words it has no operational use

> That said, I understand that some people want this notice in the
> certificate, and I see no reason to prevent this document form moving
> forward.

wow, that encourages healthy discussion

randy


From randy@psg.com  Tue Feb 11 22:44:38 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 B01321A0826 for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 22:44:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Yt62xoYY4fxb for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 22:44:37 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 12EC91A0824 for <ietf@ietf.org>; Tue, 11 Feb 2014 22:44:37 -0800 (PST)
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 1WDTYg-00022y-9U for ietf@ietf.org; Wed, 12 Feb 2014 06:44:34 +0000
Date: Wed, 12 Feb 2014 15:44:33 +0900
Message-ID: <m2eh38sucu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Disgust <ietf@ietf.org>
Subject: calls for discussion
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2014 06:44:38 -0000

maybe the result would be slightly improved if chairs did not call for
presentations at wg meetings, but instead called for items needing face
to face discussion?

i sooo want to bring rotten vegetables to wg meetings to throw at people
who think i can't and haven't read their damned draft.  but i will try
to be polite and just walk out of the meeting.

randy


From melinda.shore@gmail.com  Tue Feb 11 22:48: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 09B981A0844 for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 22:48:47 -0800 (PST)
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 2LbT0tYpUZjY for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 22:48:45 -0800 (PST)
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 79D6F1A0826 for <ietf@ietf.org>; Tue, 11 Feb 2014 22:48:45 -0800 (PST)
Received: by mail-pb0-f53.google.com with SMTP id md12so8801994pbc.40 for <ietf@ietf.org>; Tue, 11 Feb 2014 22:48:44 -0800 (PST)
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=O9u/1aAG4vnA/GWi85yeOiH45hn8s80DNGL6ZwLh76g=; b=SJSPXV3ecOtc/PvQTM0b10fXGLHPW+/rI2tGhc5Jpld38NxVDRaJ8lljbX82tT4m44 gKrrPPI4vXjtKXJMuGN6bWFLgu4GP+UPCuowBDVWXc7xuKXdHaHWrU+I8fHztlM3pytB C5RI73/RFXttVIzJuPaMgyZAXyCDv9hVUNyfu8yO4u/Sal1n7R3XR9be8i3BjH97xwRN nGJRoNTtuyKm5xnB25PcEBp8p80Lo9Jd3mRhliEmOgI4bNMTnhXB95BPR5eczNQfISXh 8ETp8G9PCIyqZC/vIF5o2IIB30tKRaBDbNI4ATlS65dj9UfN8Yb4QlFugomLqu8sC/Aw f0CA==
X-Received: by 10.68.0.99 with SMTP id 3mr49166329pbd.68.1392187724943; Tue, 11 Feb 2014 22:48:44 -0800 (PST)
Received: from spandex.local (216-67-29-177-rb2.sol.dsl.dynamic.acsalaska.net. [216.67.29.177]) by mx.google.com with ESMTPSA id ns7sm59970196pbc.32.2014.02.11.22.48.41 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 11 Feb 2014 22:48:42 -0800 (PST)
Message-ID: <52FB1948.2000101@gmail.com>
Date: Tue, 11 Feb 2014 21:48:40 -0900
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: calls for discussion
References: <m2eh38sucu.wl%randy@psg.com>
In-Reply-To: <m2eh38sucu.wl%randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2014 06:48:47 -0000

On 2/11/14 9:44 PM, Randy Bush wrote:
> maybe the result would be slightly improved if chairs did not call for
> presentations at wg meetings, but instead called for items needing face
> to face discussion?

I try but it's an uphill struggle.  I'm hoping against hope
that one of the things that comes out of the wg chairs
training session on consensus is a better understanding of
why this is such a big deal.

Melinda



From randy@psg.com  Tue Feb 11 23:37:05 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 27D601A0874 for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 23:37:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cEPTTYCHenqz for <ietf@ietfa.amsl.com>; Tue, 11 Feb 2014 23:37:03 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC5C1A0873 for <ietf@ietf.org>; Tue, 11 Feb 2014 23:37:03 -0800 (PST)
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 1WDUNR-0002BO-CH; Wed, 12 Feb 2014 07:37:01 +0000
Date: Wed, 12 Feb 2014 16:37:00 +0900
Message-ID: <m28utgsrxf.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Melinda Shore <melinda.shore@gmail.com>
Subject: Re: calls for discussion
In-Reply-To: <52FB1948.2000101@gmail.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.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
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, 12 Feb 2014 07:37:05 -0000

>> maybe the result would be slightly improved if chairs did not call
>> for presentations at wg meetings, but instead called for items
>> needing face to face discussion?
> I try but it's an uphill struggle.  I'm hoping against hope that one
> of the things that comes out of the wg chairs training session on
> consensus is a better understanding of why this is such a big deal.

we waste immense amounts of time of the literate in a hopeless attempt
to insert clue into the lazy or illiterate.  

just say a hard no to "i want to present draft-..."  has your draft been
discussed on the mailing list and has shown serious divergence of views
such that facetime is really needed?

randy


From dave@cridland.net  Wed Feb 12 00:02: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 9CE561A08AB for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 00:02:35 -0800 (PST)
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 ztfCbpxnd3Io for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 00:02:34 -0800 (PST)
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 18BD71A0885 for <ietf@ietf.org>; Wed, 12 Feb 2014 00:02:34 -0800 (PST)
Received: by mail-ob0-f174.google.com with SMTP id uy5so10203905obc.33 for <ietf@ietf.org>; Wed, 12 Feb 2014 00:02:33 -0800 (PST)
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=3U1BPRnxDyF/lg0MAS0TZvGpgr2eMFPjM7QuA/L3tZ4=; b=U0NYhNI5o1JqITtn0BYohhJEZRsnGVbAGrcs/tQmyuu4inx0DqW3hgZYx7BKWO4Xoq zzDqm+tj29sIchXMdLC7BqXNHs/u3EHJBdpri8ApP4kVAa4lr0O3c9Pl1/MbHh1FuYM0 SEW0cm76TBm/ekgiFpCL6My00ud1Fu3n8m0pw=
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=3U1BPRnxDyF/lg0MAS0TZvGpgr2eMFPjM7QuA/L3tZ4=; b=S6cCsQAftzQZ0GuScP19Odtn9zTm+P36RuVMfNsNn7KQcInEwa1KXIAMeocOtCIUl2 imRqb8GxzF1EGQBtDIWE45Ka8+ey/MauiuzuYWfdRNr2CRa9OMAzVG9tdgDyMSYIbYYz raSv/ktXwlKFUk7n/sthzUGavDUVD/u8Yv7z3t3R7SZqEmPx6EFfM8LQkjqLEdaKB8vb VyftZ1cY6QbNYn7qTdN96WmvkzId/hfMb0I8HSdTrybxatD7q+oNJMBUsAtmC5BgntXA txu8ZG1Fge+18sLf90bRv/ETqBz3kmf4V5T+ElGDPKSls0WieC71AgPaupJIHHncoo3i w3RA==
X-Gm-Message-State: ALoCoQmICWLChQ2EWV7d+yYaayo41sj2NviENAztDjNA9EO6IdzXA98Hw+HBFscYcxnq8tjy/umy
MIME-Version: 1.0
X-Received: by 10.182.40.201 with SMTP id z9mr10893440obk.45.1392192153348; Wed, 12 Feb 2014 00:02:33 -0800 (PST)
Received: by 10.60.55.197 with HTTP; Wed, 12 Feb 2014 00:02:33 -0800 (PST)
Received: by 10.60.55.197 with HTTP; Wed, 12 Feb 2014 00:02:33 -0800 (PST)
In-Reply-To: <m28utgsrxf.wl%randy@psg.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>
Date: Wed, 12 Feb 2014 08:02:33 +0000
Message-ID: <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@mail.gmail.com>
Subject: Re: calls for discussion
From: Dave Cridland <dave@cridland.net>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=001a11c33b02c2887f04f230fecb
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, 12 Feb 2014 08:02:35 -0000

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

Sorry, I've not had a chance to read your mail, but perhaps we could
discuss it in the session in London?
On 12 Feb 2014 07:37, "Randy Bush" <randy@psg.com> wrote:

> >> maybe the result would be slightly improved if chairs did not call
> >> for presentations at wg meetings, but instead called for items
> >> needing face to face discussion?
> > I try but it's an uphill struggle.  I'm hoping against hope that one
> > of the things that comes out of the wg chairs training session on
> > consensus is a better understanding of why this is such a big deal.
>
> we waste immense amounts of time of the literate in a hopeless attempt
> to insert clue into the lazy or illiterate.
>
> just say a hard no to "i want to present draft-..."  has your draft been
> discussed on the mailing list and has shown serious divergence of views
> such that facetime is really needed?
>
> randy
>
>

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

<p dir=3D"ltr">Sorry, I&#39;ve not had a chance to read your mail, but perh=
aps we could discuss it in the session in London?</p>
<div class=3D"gmail_quote">On 12 Feb 2014 07:37, &quot;Randy Bush&quot; &lt=
;<a href=3D"mailto:randy@psg.com">randy@psg.com</a>&gt; wrote:<br type=3D"a=
ttribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
&gt;&gt; maybe the result would be slightly improved if chairs did not call=
<br>
&gt;&gt; for presentations at wg meetings, but instead called for items<br>
&gt;&gt; needing face to face discussion?<br>
&gt; I try but it&#39;s an uphill struggle. =A0I&#39;m hoping against hope =
that one<br>
&gt; of the things that comes out of the wg chairs training session on<br>
&gt; consensus is a better understanding of why this is such a big deal.<br=
>
<br>
we waste immense amounts of time of the literate in a hopeless attempt<br>
to insert clue into the lazy or illiterate.<br>
<br>
just say a hard no to &quot;i want to present draft-...&quot; =A0has your d=
raft been<br>
discussed on the mailing list and has shown serious divergence of views<br>
such that facetime is really needed?<br>
<br>
randy<br>
<br>
</blockquote></div>

--001a11c33b02c2887f04f230fecb--


From chelliot@gmail.com  Wed Feb 12 00:45:54 2014
Return-Path: <chelliot@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 0B63F1A070D for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 00:45:54 -0800 (PST)
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 mMWNZ8z1hn3i for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 00:45:51 -0800 (PST)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 89B9E1A08AB for <ietf@ietf.org>; Wed, 12 Feb 2014 00:45:51 -0800 (PST)
Received: by mail-lb0-f175.google.com with SMTP id p9so6738651lbv.6 for <ietf@ietf.org>; Wed, 12 Feb 2014 00:45:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=NZIldHzM0cDtibJ39BnCjEb6jwaqKnSNuvV2fz/q1gM=; b=ay3+Hgm3QoXYZy2fDJF64wtE4JEaWGvy7eoQ6eEKsUiMwbnGKCCn+b+EeQwnMUsj5v iWQVPxw7sPwbu+u+Uelhb4+aBS0lcE5LtpB9ZIB8FeamePx7XLg0EmFZw2jZ8Sh0e1ZS 8DLtHrCWz00RCGYe1e0ncbJc4+DoLZRxruwpFiZdJ1OvsdJ5l7dIatoyIlXLwzpXKy2W gV88AedDmvcxDef9zISv1slnfUz5a+Vo37UfrbMsKmgId32f9UbRrOt0jY0DQ5QJcqXZ jcQQvvWiZpbYK9HoqcxgL/PshnthKCWrOaR/PCbYhwf7fQGDFlvKKbFAuHuflX77M/MK x/ww==
MIME-Version: 1.0
X-Received: by 10.112.209.97 with SMTP id ml1mr29090215lbc.26.1392194750014; Wed, 12 Feb 2014 00:45:50 -0800 (PST)
Sender: chelliot@gmail.com
Received: by 10.114.65.11 with HTTP; Wed, 12 Feb 2014 00:45:49 -0800 (PST)
In-Reply-To: <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@mail.gmail.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@mail.gmail.com>
Date: Wed, 12 Feb 2014 03:45:49 -0500
X-Google-Sender-Auth: lluUAN18ylGczyAgsGKLyNvZ5wk
Message-ID: <CAO_RpcJ9qt6CLmHELTPu0nMNy6E2UtrJ-sEUaXH=Nb8HxjFJhQ@mail.gmail.com>
Subject: calls for discussion
From: Chris Elliott <chelliot@pobox.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=001a11c332428868e104f2319945
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chelliot@pobox.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, 12 Feb 2014 08:45:54 -0000

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

On Wednesday, February 12, 2014, Dave Cridland
<dave@cridland.net<javascript:_e(%7B%7D,'cvml','dave@cridland.net');>>
wrote:

> Sorry, I've not had a chance to read your mail, but perhaps we could
> discuss it in the session in London?
>
I've not had a chance to review your mail either. Would you mind giving a
presentation on it in London? PowerPoint is so much better than just text.
And can you liven it up a bit? Most of the IETF presentations are so dry.
PowerPoint supports colors and animations, you know.

...

Seriously, Randy's point is excellent. Let's stop coddling the folks most
likely to /not/ have useful input and make the meetings worth attending for
the experts we need input from.

I know I haven't always done my homework for every working group meeting
I've attended. I'm more likely to come prepared if I know the meeting will
jump right to points needing discussion, with no time to "catch up" during
the presentations.

Thinking on my fingers...

I know I've had the best of intentions of being prepared, but most of us
have full lives outside the IETF and find ourselves behind at the meeting.
Can we find a way to help this issue, and maybe also help newcomers?

Maybe we could have reading sessions where folks could just sit and read
drafts, with quiet discussion limited to understanding the draft. No ADs or
Chairs required. Document editors would be welcome, but not required. This
could even be done informally in the terminal room, or during breakfast, or
dedicate the first session of the day to this--with an area with
a table set up with a sign for each WG or draft. This time could also be
used by mentors to help newcomers understand drafts and their issues.

Then, later in the day or week, have a to the point WG meeting, possibly
much shorter, but, if not, then the time is spent usefully in discussion of
points of contention.

It's likely that less time would be required overall. This could free up a
significant amount of time for ADs, Chairs, and those that were able to do
their "homework".

Stupid idea, or worth writing a draft?

Chris.


> On 12 Feb 2014 07:37, "Randy Bush" <randy@psg.com> wrote:
>
>> >> maybe the result would be slightly improved if chairs did not call
>> >> for presentations at wg meetings, but instead called for items
>> >> needing face to face discussion?
>> > I try but it's an uphill struggle.  I'm hoping against hope that one
>> > of the things that comes out of the wg chairs training session on
>> > consensus is a better understanding of why this is such a big deal.
>>
>> we waste immense amounts of time of the literate in a hopeless attempt
>> to insert clue into the lazy or illiterate.
>>
>> just say a hard no to "i want to present draft-..."  has your draft been
>> discussed on the mailing list and has shown serious divergence of views
>> such that facetime is really needed?
>>
>> randy
>>
>>

-- 
Chris Elliott
chelliot@pobox.com

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

On Wednesday, February 12, 2014, Dave Cridland &lt;<a href=3D"javascript:_e=
(%7B%7D,&#39;cvml&#39;,&#39;dave@cridland.net&#39;);" target=3D"_blank">dav=
e@cridland.net</a>&gt; wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<p dir=3D"ltr">Sorry, I&#39;ve not had a chance to read your mail, but perh=
aps we could discuss it in the session in London?</p></blockquote><div>I&#3=
9;ve not had a chance to review your mail either. Would you mind giving a p=
resentation on it in London? PowerPoint is so much better than just text. A=
nd can you liven it up a bit? Most of the IETF presentations are so dry. Po=
werPoint supports colors and animations, you know.</div>

<div><br></div><div>...</div><div><br></div><div>Seriously, Randy&#39;s poi=
nt is excellent. Let&#39;s stop coddling the folks most likely to /not/ hav=
e useful input and make the meetings worth attending for the experts we nee=
d input from.</div>

<div><br></div><div>I know I haven&#39;t always done my homework for every =
working group meeting I&#39;ve attended. I&#39;m more likely to come prepar=
ed if I know the meeting will jump right to points needing discussion, with=
 no time to &quot;catch up&quot; during the presentations.</div>

<div><br></div><div>Thinking on my fingers...</div><div><br></div><div>I kn=
ow I&#39;ve had the best of intentions of being prepared, but most of us ha=
ve full lives outside the IETF and find ourselves behind at the meeting. Ca=
n we find a way to help this issue, and maybe also help newcomers?</div>

<div><br></div><div>Maybe we could have reading sessions where folks could =
just sit and read drafts, with quiet discussion limited to understanding th=
e draft.=A0No ADs or Chairs required. Document editors would=A0be welcome, =
but not required. This could even be done informally in the terminal room, =
or during breakfast, or dedicate the first session of the day to this--with=
 an area with a=A0table=A0set up with a sign for each WG or draft. This tim=
e could also be used by mentors to help newcomers understand drafts and the=
ir issues.</div>

<div></div><div><br></div><div>Then, later in the day or=A0week, have a=A0t=
o the point WG meeting, possibly much shorter, but, if not, then the time i=
s spent usefully in discussion of points of contention.</div><div><br></div=
>

<div>It&#39;s likely that less time would be required overall.=A0This could=
 free up a significant amount of time for ADs, Chairs, and those that were =
able to do their &quot;homework&quot;.</div><div><br></div><div>Stupid idea=
, or worth writing a draft?</div>

<div><br></div><div>Chris.<span></span></div><div>=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">
<div class=3D"gmail_quote">On 12 Feb 2014 07:37, &quot;Randy Bush&quot; &lt=
;<a>randy@psg.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">


&gt;&gt; maybe the result would be slightly improved if chairs did not call=
<br>
&gt;&gt; for presentations at wg meetings, but instead called for items<br>
&gt;&gt; needing face to face discussion?<br>
&gt; I try but it&#39;s an uphill struggle. =A0I&#39;m hoping against hope =
that one<br>
&gt; of the things that comes out of the wg chairs training session on<br>
&gt; consensus is a better understanding of why this is such a big deal.<br=
>
<br>
we waste immense amounts of time of the literate in a hopeless attempt<br>
to insert clue into the lazy or illiterate.<br>
<br>
just say a hard no to &quot;i want to present draft-...&quot; =A0has your d=
raft been<br>
discussed on the mailing list and has shown serious divergence of views<br>
such that facetime is really needed?<br>
<br>
randy<br>
<br>
</blockquote></div>
</blockquote>
<br><br>-- <br>Chris Elliott<br><a href=3D"mailto:chelliot@pobox.com">chell=
iot@pobox.com</a><br><br>

--001a11c332428868e104f2319945--


From abdussalambaryun@gmail.com  Wed Feb 12 02:16:39 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 20D031A091B for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 02:16:39 -0800 (PST)
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 MpALzmQqtuKB for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 02:16:37 -0800 (PST)
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 667C51A0916 for <ietf@ietf.org>; Wed, 12 Feb 2014 02:16:37 -0800 (PST)
Received: by mail-yh0-f54.google.com with SMTP id z6so8183309yhz.13 for <ietf@ietf.org>; Wed, 12 Feb 2014 02:16:36 -0800 (PST)
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=yUA47AFMxCdO5JRoFiTuYNjuQO1bscnoxN7E4HMj3Lg=; b=NDZ9qp8I0coYmE2VoJKxynVsAh/iTLHVqggfGEkEH5vbKs/K8C0fCynm1gOwUHuz/p VC9k3Zzjc0oz/wAx+NvzfIJ/+cdFLpPpNJiqt0s37WYB01fSpvn50i9kLEy5gPWFcG5s grs6vsE/cv9jOiW1enGewN7jprI3nW9C+kWtv/o1VY6pKwaa6Um6bTqftJwRtJQH2jfb jhlHFmlYCdi0Sa2MLR5OgZecV+MSIfthSM4Cg2BYxtHVX5PfEuhFdY90x/KwCFYzmwiT rvqW0swIa2Aw9qxscDg63sgqDlHgOhubmnn/Vrjn5wV0H/BEMhmwwHKKcLGnEu0TivcU 2QWQ==
MIME-Version: 1.0
X-Received: by 10.236.204.74 with SMTP id g50mr45298yho.127.1392200196613; Wed, 12 Feb 2014 02:16:36 -0800 (PST)
Received: by 10.170.222.3 with HTTP; Wed, 12 Feb 2014 02:16:36 -0800 (PST)
In-Reply-To: <m28utgsrxf.wl%randy@psg.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>
Date: Wed, 12 Feb 2014 11:16:36 +0100
Message-ID: <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com>
Subject: Re: calls for discussion
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: text/plain; charset=ISO-8859-1
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, 12 Feb 2014 10:16:39 -0000

On 2/12/14, Randy Bush <randy@psg.com> wrote:
> we waste immense amounts of time of the literate in a hopeless attempt
> to insert clue into the lazy or illiterate.

The drafts are requested on the lists to be presented and all have
same chance to present or object to a presentation, chairs SHOULD only
put the request on the list and see priorities and agreements from the
WG.
>
> just say a hard no to "i want to present draft-..."  has your draft been
> discussed on the mailing list and has shown serious divergence of views
> such that facetime is really needed?

No, there can be a chance to start discussions in meetings as well. I
recommend you object the drafts that you think is a waste of your time
and discuss with your WGs, without throwing vegetables.

AB


From abdussalambaryun@gmail.com  Wed Feb 12 02:31:39 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 3ACD51A0922 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 02:31:39 -0800 (PST)
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 AfX3tXayNUsj for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 02:31:37 -0800 (PST)
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 646251A091B for <ietf@ietf.org>; Wed, 12 Feb 2014 02:31:37 -0800 (PST)
Received: by mail-yh0-f46.google.com with SMTP id v1so8149632yhn.5 for <ietf@ietf.org>; Wed, 12 Feb 2014 02:31:36 -0800 (PST)
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=ON6aeUWis7AK9aQRbGDcxz/JFuGCUPrZ+ItrQAFrHUM=; b=h/tF5VH71RqT6euyxXoD3c3ri6ilX8yypIsIvMqlLMu3pTq1S6Ht9TbPDS/YJHOTgq MQL60iUZOcqg+ORoXACfq6GuD87XXK03saYVrfxu0r5UHEkr+mSjlf6PQQFrRDXA/B/Z aDvDBknoIbrAZVsnmyJn9u9e6yATBiGMrhNbzHru/vKhj6E0jufYEEZ1HA46TZVFVw0o a/GL+C6U8yw0rKfAeCjbg9wbjqCLmPGDq48K+NVWNK9VaKAP4g30ZrWdD2mu9uPjfsRa KTDFy8p5if7XZgVBbrYtBmUiuhyFo8nzilyOYFTpSQOHZ4/TgPcbPtl8IAF61Ik6XrDU +W2Q==
MIME-Version: 1.0
X-Received: by 10.236.90.65 with SMTP id d41mr39354686yhf.28.1392201096581; Wed, 12 Feb 2014 02:31:36 -0800 (PST)
Received: by 10.170.222.3 with HTTP; Wed, 12 Feb 2014 02:31:36 -0800 (PST)
Date: Wed, 12 Feb 2014 11:31:36 +0100
Message-ID: <CADnDZ8-V=PVmp2x9mUyeuztwB1ansE4ZAXufNinsbv2+1Sf=Bw@mail.gmail.com>
Subject: Does silence have no value? suggested for draft-resnick-on-consensus-06
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2014 10:31:39 -0000

The draft needs to show that if a wg-chair is presenting (in meeting
or on lists) an individual draft to the WG for adoption, and no
answer/reply comes out, that does not mean against nor agree, I
recommend there is no value of no effort from the WG. Some WG may not
respond for adoption because they had no time for making a decision,
so I hope the Chairs don't misunderstand and make wrong decisions.

AB

On 2/11/14, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> usually in engineering *silence* should always have no
> value. Against SHOULD be with engineering reason, and agreeing MAY be
> with engineering reason.
>
> AB
>


From l.wood@surrey.ac.uk  Wed Feb 12 03:29:25 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 B9CF61A0956 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 03:29:25 -0800 (PST)
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 nLJiaAV8TFg8 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 03:29:23 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) by ietfa.amsl.com (Postfix) with ESMTP id 100681A094E for <ietf@ietf.org>; Wed, 12 Feb 2014 03:29:22 -0800 (PST)
Received: from [195.245.230.131:61899] by server-12.bemta-3.messagelabs.com id 07/98-01674-11B5BF25; Wed, 12 Feb 2014 11:29:21 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-78.messagelabs.com!1392204561!30462087!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17038 invoked from network); 12 Feb 2014 11:29:21 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-8.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 12 Feb 2014 11:29:21 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 12 Feb 2014 11:29:20 +0000
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <randy@psg.com>
Date: Wed, 12 Feb 2014 11:26:13 +0000
Subject: RE: calls for discussion
Thread-Topic: calls for discussion
Thread-Index: Ac8n25Z0U+sjJ9nIRN2/m9JoW8oguQACaXjO
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>, <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com>
In-Reply-To: <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@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
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, 12 Feb 2014 11:29:25 -0000

Starting an idea in the meeting privileges only those who are in the room.

The work of the IETF is on the mailing lists.

You MUST stop using normative language in emails. It carries no weight.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun [abdussal=
ambaryun@gmail.com]
Sent: 12 February 2014 10:16
To: Randy Bush
Cc: IETF Disgust
Subject: Re: calls for discussion

On 2/12/14, Randy Bush <randy@psg.com> wrote:
> we waste immense amounts of time of the literate in a hopeless attempt
> to insert clue into the lazy or illiterate.

The drafts are requested on the lists to be presented and all have
same chance to present or object to a presentation, chairs SHOULD only
put the request on the list and see priorities and agreements from the
WG.
>
> just say a hard no to "i want to present draft-..."  has your draft been
> discussed on the mailing list and has shown serious divergence of views
> such that facetime is really needed?

No, there can be a chance to start discussions in meetings as well. I
recommend you object the drafts that you think is a waste of your time
and discuss with your WGs, without throwing vegetables.

AB


From l.wood@surrey.ac.uk  Wed Feb 12 04:12: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 A15121A096F for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 04:12:17 -0800 (PST)
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 zFXS6C72oN4r for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 04:12:14 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.147]) by ietfa.amsl.com (Postfix) with ESMTP id A053A1A0803 for <ietf@ietf.org>; Wed, 12 Feb 2014 04:12:13 -0800 (PST)
Received: from [195.245.231.67:48628] by server-11.bemta-5.messagelabs.com id 3E/BE-23886-C156BF25; Wed, 12 Feb 2014 12:12:12 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-82.messagelabs.com!1392207131!25013925!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 8267 invoked from network); 12 Feb 2014 12:12:12 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-5.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 12 Feb 2014 12:12:12 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Wed, 12 Feb 2014 12:12:11 +0000
From: <l.wood@surrey.ac.uk>
To: <dave@cridland.net>, <randy@psg.com>
Date: Wed, 12 Feb 2014 12:11:14 +0000
Subject: RE: calls for discussion
Thread-Topic: calls for discussion
Thread-Index: Ac8nyNus18LkesrJRkSgR3LO6XSmEQAIqqyd
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334715@EXMB01CMS.surrey.ac.uk>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>, <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@mail.gmail.com>
In-Reply-To: <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@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
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, 12 Feb 2014 12:12:17 -0000

Can you put together some powerpoints on it for the meeting? About five min=
utes or so?

It's looking to be a busy session, though. Not sure we'll have time for que=
stions.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Dave Cridland [dave@cridlan=
d.net]
Sent: 12 February 2014 08:02
To: Randy Bush
Cc: ietf@ietf.org Discussion
Subject: Re: calls for discussion

Sorry, I've not had a chance to read your mail, but perhaps we could discus=
s it in the session in London?

On 12 Feb 2014 07:37, "Randy Bush" <randy@psg.com<mailto:randy@psg.com>> wr=
ote:
>> maybe the result would be slightly improved if chairs did not call
>> for presentations at wg meetings, but instead called for items
>> needing face to face discussion?
> I try but it's an uphill struggle.  I'm hoping against hope that one
> of the things that comes out of the wg chairs training session on
> consensus is a better understanding of why this is such a big deal.

we waste immense amounts of time of the literate in a hopeless attempt
to insert clue into the lazy or illiterate.

just say a hard no to "i want to present draft-..."  has your draft been
discussed on the mailing list and has shown serious divergence of views
such that facetime is really needed?

randy


From loa@pi.nu  Wed Feb 12 05:09:29 2014
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C60EE1A0985 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 05:09:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qG-5dXHyVnCz for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 05:09:26 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id A47851A0979 for <ietf@ietf.org>; Wed, 12 Feb 2014 05:09:26 -0800 (PST)
Received: from [192.168.1.4] (unknown [119.95.142.126]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id AC93D1802AAD; Wed, 12 Feb 2014 14:09:24 +0100 (CET)
Message-ID: <52FB7278.8020201@pi.nu>
Date: Wed, 12 Feb 2014 21:09:12 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: calls for discussion
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>, <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2014 13:09:30 -0000

All,

First I agree with Lloyd the misuse of normtive language in mails,
jsut look a bit peculiar and does not carry any weight.

Lloyd,
While it is true that most work in the IETF happens on mailing lists,
and should be taken there as fast as is ever possible, it is not true
that all work is is done on mailing lists. If it did everything in
Note Well that does say anything about things that does not happen on
the mailing lists would be moot.

I hope you don't want to real work coming out of chance meetings in
the corridors of the IETF meeting venue. Consider me walking down the
corridor and by chance happens to start talking to the a bright person
from one of my worst competitors about something that has slowly
emerged in my  head over the last few hours. He or she confirms the
same problem has just occurred him/her. After 10 mins of discussion we
have something that can go into a draft.

Do you seriously say that we should be stopped for writing the draft,
just because our discussion took place face to face, rather than on
a mailing list?

/Loa

On 2014-02-12 19:26, l.wood@surrey.ac.uk wrote:
> Starting an idea in the meeting privileges only those who are in the room.
>
> The work of the IETF is on the mailing lists.
>
> You MUST stop using normative language in emails. It carries no weight.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun [abdussalambaryun@gmail.com]
> Sent: 12 February 2014 10:16
> To: Randy Bush
> Cc: IETF Disgust
> Subject: Re: calls for discussion
>
> On 2/12/14, Randy Bush <randy@psg.com> wrote:
>> we waste immense amounts of time of the literate in a hopeless attempt
>> to insert clue into the lazy or illiterate.
>
> The drafts are requested on the lists to be presented and all have
> same chance to present or object to a presentation, chairs SHOULD only
> put the request on the list and see priorities and agreements from the
> WG.
>>
>> just say a hard no to "i want to present draft-..."  has your draft been
>> discussed on the mailing list and has shown serious divergence of views
>> such that facetime is really needed?
>
> No, there can be a chance to start discussions in meetings as well. I
> recommend you object the drafts that you think is a waste of your time
> and discuss with your WGs, without throwing vegetables.
>
> AB
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From dave@cridland.net  Wed Feb 12 06:51:42 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 00A9F1A099B for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 06:51:42 -0800 (PST)
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 ZId87N7Gbsfo for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 06:51:40 -0800 (PST)
Received: from mail-oa0-x22c.google.com (mail-oa0-x22c.google.com [IPv6:2607:f8b0:4003:c02::22c]) by ietfa.amsl.com (Postfix) with ESMTP id 54E861A0340 for <ietf@ietf.org>; Wed, 12 Feb 2014 06:51:40 -0800 (PST)
Received: by mail-oa0-f44.google.com with SMTP id g12so11114905oah.31 for <ietf@ietf.org>; Wed, 12 Feb 2014 06:51:39 -0800 (PST)
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=NAsYYq1BYZ5TKZbOAc7X30WiPOTK64jM/Kd7n1y2vZ0=; b=P2+y0/s7Rjq36R82uxzxpLLpDWJh2ELCmOhp4ehCyNiZKoPKIhR+xrWQ4E9wW5Fcpf emwmXsTWKBY0CJB9s0hp3Vxrpt4O9qThFwyTIyTitFqXYIe2HdRSTlOpXpsXOL06D4A+ /y790o8wdMKhrF2b4Cm9Naw5VEFQJ8XOZ54d4=
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=NAsYYq1BYZ5TKZbOAc7X30WiPOTK64jM/Kd7n1y2vZ0=; b=M/u+i9aM5SYOYRt5VQ5QO1g3mPDoAjC76AHuyaQIQR65CbAzZeZTaih9P7G9zwNVcK mM0TDOauQoTzDElnDkLs0ODpkOu8exDwKpLCVP0qJR0L+sTsrclOzC3Hw19nWm82hRCx U9rFsrOTioS2Pw8ymgVaiHmLPh9AG6Ercb4A8TIyW60XUDlLRV/Zs+UQIhLeNcw02RMz yYhXi1+2rvK86WgW4w+BhqK3iI0mUp022DRjoHeCxpAX6t3not36QLU2uE09wEO37SXE eIqoNdbiI/EL51nNRoP7ZDXgY2MB+qjJw4/fvERyTG91sz0B3lweMCIXBSCLcIEipd/S iLHA==
X-Gm-Message-State: ALoCoQnciL370zGqimOgBrjNU/bAzUJtSC09ZPzDEQb0Bz6thXO6Rh86nxsjHug88QO4PIgcCkjp
MIME-Version: 1.0
X-Received: by 10.182.18.102 with SMTP id v6mr602564obd.71.1392216699353; Wed, 12 Feb 2014 06:51:39 -0800 (PST)
Received: by 10.60.55.197 with HTTP; Wed, 12 Feb 2014 06:51:39 -0800 (PST)
In-Reply-To: <CADnDZ8-V=PVmp2x9mUyeuztwB1ansE4ZAXufNinsbv2+1Sf=Bw@mail.gmail.com>
References: <CADnDZ8-V=PVmp2x9mUyeuztwB1ansE4ZAXufNinsbv2+1Sf=Bw@mail.gmail.com>
Date: Wed, 12 Feb 2014 14:51:39 +0000
Message-ID: <CAKHUCzwpf+MpfmYtYwyfQtf7Hq537yi+Yct=2KdMUvsNQWJKPA@mail.gmail.com>
Subject: Re: Does silence have no value? suggested for draft-resnick-on-consensus-06
From: Dave Cridland <dave@cridland.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c339e6d0d17804f236b555
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, 12 Feb 2014 14:51:42 -0000

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

On Wed, Feb 12, 2014 at 10:31 AM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> The draft needs to show that if a wg-chair is presenting (in meeting
> or on lists) an individual draft to the WG for adoption, and no
> answer/reply comes out, that does not mean against nor agree, I
> recommend there is no value of no effort from the WG. Some WG may not
> respond for adoption because they had no time for making a decision,
> so I hope the Chairs don't misunderstand and make wrong decisions.
>

Calls for adoption are particularly interesting cases, because if there's
no response, then as chairman I have to assume there's no interest. This
could be because of lack of time, of course, but if merely checking the
draft over for adoption isn't worthy of effort, then I can't really expect
that once adopted, people will suddenly find the time to do serious work.

In other cases, however, silence can mean assent, or at least no interest
in arguing against. If a particular open issue in a draft is resolved by a
small group (or even a single person) picking a solution that works for
them, then an absence of complaints, despite not being quite the same, nor
as desirable, as enthusiastic and vocal support, still leads to the same
conclusion.

As for providing engineering reasons... I always prefer strongly to see an
solid technical reason for a position. It helps enormously in judging the
roughness. But if the reasoning is aesthetic, market-related, or a gut
feeling, that's nevertheless useful information. Since we deal in rough
consensus, not perfect agreement, even a real technical issue is not enough
to break rough consensus sometimes, but any reason might be - and in
general terms, I want to encourage open dissent.

This last principle is important for two reasons. The most obvious is that
we want to ensure that self-censorship doesn't cause people to avoid
speaking up when their concern is well-founded - especially true for less
experienced participants who may misjudge the value of their contribution
in either way. The other is that someone voicing just a nagging feeling
that the solution is "somehow wrong" might well jog other people into
noticing some real flaw.

On aesthetic and market-related reasons, two examples:

a) At one stage, the SASL working group were close to abandoning
human-readable names for new, GSSAPI-based, mechanisms. People argued
against this purely on the basis that it would have discouraged people from
implementing these newer mechanisms. This isn't a technical or engineering
argument, it's purely aesthetic, but it's nevertheless important.

b) With the on-going discussions about pervasive encryption, it's important
to recall that for many parts of the world, it's still against export
regulations to allow >56-bit encryption in binary software (ie,
non-open-source) to be exported to certain countries. There are strong
technical arguments against "export grade" encryption.

Dave.
(With apologies for the lack of flippant sarcasm in this message)

--001a11c339e6d0d17804f236b555
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 W=
ed, Feb 12, 2014 at 10:31 AM, Abdussalam Baryun <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:abdussalambaryun@gmail.com" target=3D"_blank">abdussalambaryun=
@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">The draft needs to show that if a wg-chair i=
s presenting (in meeting<br>
or on lists) an individual draft to the WG for adoption, and no<br>
answer/reply comes out, that does not mean against nor agree, I<br>
recommend there is no value of no effort from the WG. Some WG may not<br>
respond for adoption because they had no time for making a decision,<br>
so I hope the Chairs don&#39;t misunderstand and make wrong decisions.<br><=
/blockquote><div><br></div><div>Calls for adoption are particularly interes=
ting cases, because if there&#39;s no response, then as chairman I have to =
assume there&#39;s no interest. This could be because of lack of time, of c=
ourse, but if merely checking the draft over for adoption isn&#39;t worthy =
of effort, then I can&#39;t really expect that once adopted, people will su=
ddenly find the time to do serious work.</div>
<div><br></div><div>In other cases, however, silence can mean assent, or at=
 least no interest in arguing against. If a particular open issue in a draf=
t is resolved by a small group (or even a single person) picking a solution=
 that works for them, then an absence of complaints, despite not being quit=
e the same, nor as desirable, as enthusiastic and vocal support, still lead=
s to the same conclusion.</div>
<div><br></div><div>As for providing engineering reasons... I always prefer=
 strongly to see an solid technical reason for a position. It helps enormou=
sly in judging the roughness. But if the reasoning is aesthetic, market-rel=
ated, or a gut feeling, that&#39;s nevertheless useful information. Since w=
e deal in rough consensus, not perfect agreement, even a real technical iss=
ue is not enough to break rough consensus sometimes, but any reason might b=
e - and in general terms, I want to encourage open dissent.</div>
<div><br></div><div>This last principle is important for two reasons. The m=
ost obvious is that we want to ensure that self-censorship doesn&#39;t caus=
e people to avoid speaking up when their concern is well-founded - especial=
ly true for less experienced participants who may misjudge the value of the=
ir contribution in either way. The other is that someone voicing just a nag=
ging feeling that the solution is &quot;somehow wrong&quot; might well jog =
other people into noticing some real flaw.</div>
<div><br></div><div>On aesthetic and market-related reasons, two examples:<=
/div><div><br></div><div>a) At one stage, the SASL working group were close=
 to abandoning human-readable names for new, GSSAPI-based, mechanisms. Peop=
le argued against this purely on the basis that it would have discouraged p=
eople from implementing these newer mechanisms. This isn&#39;t a technical =
or engineering argument, it&#39;s purely aesthetic, but it&#39;s neverthele=
ss important.</div>
<div><br></div><div>b) With the on-going discussions about pervasive encryp=
tion, it&#39;s important to recall that for many parts of the world, it&#39=
;s still against export regulations to allow &gt;56-bit encryption in binar=
y software (ie, non-open-source) to be exported to certain countries. There=
 are strong technical arguments against &quot;export grade&quot; encryption=
.</div>
<div><br></div><div>Dave.</div><div>(With apologies for the lack of flippan=
t sarcasm in this message)</div></div></div></div>

--001a11c339e6d0d17804f236b555--


From scott.brim@gmail.com  Wed Feb 12 07:09:09 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 AB3951A09C9 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 07:09:09 -0800 (PST)
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 BkNWs8FRaeot for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 07:09:05 -0800 (PST)
Received: from mail-oa0-x22a.google.com (mail-oa0-x22a.google.com [IPv6:2607:f8b0:4003:c02::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 71FB41A09B9 for <ietf@ietf.org>; Wed, 12 Feb 2014 07:09:03 -0800 (PST)
Received: by mail-oa0-f42.google.com with SMTP id i7so11103798oag.1 for <ietf@ietf.org>; Wed, 12 Feb 2014 07:09:02 -0800 (PST)
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=3nY5mjAhewrdHFiWWqes7TtgtgrPY7DxS4wHs4RCaHg=; b=Xo1GevVZcCvSfbE1aVYuaqhQm3T07vLGZJtKcmTXk3ZyozKvo5bLpdbY1GhAJnYSo1 MZmkjzB5c+pQl6ZLShQqppLntVfuhdXXZP0+ebcNJXgC9Vb03ILX1DxHm7LX3ri9pFOQ Pu6vEOa1Lg6A8GTavhonawxwMgioMP9FaFV7SsgqE13zyCiHMw9mM09zuCFqqq8RddZG hp6nJ++m43lTzVJ19YFSqvnQnn09hMCLsXRH5FJOJtwKOdYOXwg+vlHkkNRetYbnmE+L MrHdgOOwSNqARuVP/cRKVV1wPDwdzqADwkd1Q4dT2lzcx8kFfSB0x/ZJZrsmi59lEy9Y o/Nw==
X-Received: by 10.182.153.226 with SMTP id vj2mr38139859obb.26.1392217742507;  Wed, 12 Feb 2014 07:09:02 -0800 (PST)
MIME-Version: 1.0
Received: by 10.182.48.9 with HTTP; Wed, 12 Feb 2014 07:08:42 -0800 (PST)
In-Reply-To: <CAKHUCzwpf+MpfmYtYwyfQtf7Hq537yi+Yct=2KdMUvsNQWJKPA@mail.gmail.com>
References: <CADnDZ8-V=PVmp2x9mUyeuztwB1ansE4ZAXufNinsbv2+1Sf=Bw@mail.gmail.com> <CAKHUCzwpf+MpfmYtYwyfQtf7Hq537yi+Yct=2KdMUvsNQWJKPA@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Wed, 12 Feb 2014 10:08:42 -0500
Message-ID: <CAPv4CP_DGKYMJ-y+qnMBZtFd+7-=zOU0OiUL1PKGfh665+35mg@mail.gmail.com>
Subject: Re: Does silence have no value? suggested for draft-resnick-on-consensus-06
To: Dave Cridland <dave@cridland.net>
Content-Type: text/plain; charset=ISO-8859-1
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, 12 Feb 2014 15:09:09 -0000

On Wed, Feb 12, 2014 at 9:51 AM, Dave Cridland <dave@cridland.net> wrote:
> Calls for adoption are particularly interesting cases, because if there's no
> response, then as chairman I have to assume there's no interest. This could
> be because of lack of time, of course, but if merely checking the draft over
> for adoption isn't worthy of effort, then I can't really expect that once
> adopted, people will suddenly find the time to do serious work.
>
> In other cases, however, silence can mean assent, or at least no interest in
> arguing against. If a particular open issue in a draft is resolved by a
> small group (or even a single person) picking a solution that works for
> them, then an absence of complaints, despite not being quite the same, nor
> as desirable, as enthusiastic and vocal support, still leads to the same
> conclusion.

One thing I've seen in WGs that I like is if there is a lot of
silence, the chair says what s/he assumes silence implies.  "If you're
silent, I'm going to assume that means you don't have any objection",
etc.


From dhc@dcrocker.net  Wed Feb 12 07:23:39 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 1D2851A0359 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 07:23:39 -0800 (PST)
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 evKSfVM0JNpb for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 07:23:36 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 4A3EF1A045D for <ietf@ietf.org>; Wed, 12 Feb 2014 07:23:10 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1CFN6wR005223 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Wed, 12 Feb 2014 07:23:09 -0800
Message-ID: <52FB91B0.5090508@dcrocker.net>
Date: Wed, 12 Feb 2014 07:22:24 -0800
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.3.0
MIME-Version: 1.0
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: calls for discussion
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@mail.gmail.com>
In-Reply-To: <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@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]); Wed, 12 Feb 2014 07:23:09 -0800 (PST)
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, 12 Feb 2014 15:23:39 -0000

On 2/12/2014 12:02 AM, Dave Cridland wrote:
> Sorry, I've not had a chance to read your mail, but perhaps we could
> discuss it in the session in London?


Nicely done.

It highlights what is probably the real basis for poor use of 
face-to-face group meeting time during IETF week:

      People who come to the IETF are used to working a particular way
      and are merely invoking that established model.

      The model is for group work to be done face-to-face.

This also explains why there seems to be an increase in interim meetings.

So,

      If we want meeting time to be used better, we need to get people
      to change their model and to seriously do the major group work
      /between/ meetings and /on the mailing list/.

That has its challenges, but the challenges are not an excuse for giving 
up on mailing lists or calling such folk lazy or illiterate.

And the obligation of IETF management is to ensure that those running 
groups -- and everyone else who is participating in them -- understand 
the nature of this model and understand how to be productive with it.

It's our community culture and we need to impart it with on-going 
supportive shepherding, not the mean-spirited arrogance demonstrated by 
some of the language used in this thread.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From margaretw42@gmail.com  Wed Feb 12 04:32:27 2014
Return-Path: <margaretw42@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 8BC1A1A0918 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 04:32:27 -0800 (PST)
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 wOQHvPTmViSh for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 04:32:25 -0800 (PST)
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 B45571A0987 for <ietf@ietf.org>; Wed, 12 Feb 2014 04:32:25 -0800 (PST)
Received: by mail-qa0-f46.google.com with SMTP id k15so420872qaq.5 for <ietf@ietf.org>; Wed, 12 Feb 2014 04:32:24 -0800 (PST)
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=8CA+3o6R3sdRgymoJN5OEvSRTYWCxPiOxZhiD/lRdyU=; b=l5KR3H0wYD5MhgfNZCvG+loBW/alINPKD9AJmGIcslM5NYMbTNR+A//wXPJNVPNlYF 3k6UjZ7zESkOmFe+klDcEomelmDxJw3jtxXWs/H9V7ioSfEgv2M510z91NprElI+GsqQ vxj7QSsuOCIhyIPDGnOnOgzjNU75xrlaXC4lxEStK3cUFYeLPMXWOwByw8kj881iV10J MFJM2/YD9STGcDoqa/sBSp2/SUXH402kO6Bo91KwNdxaIJ4Xj0NpJPNFXuX8njxHzBmS cFhu2bochodzxhq2r5JxUJVWXGRHzkyYZvY7mfjuGsCrJyeikxeJKyfIRm9tsah8UHlH lLwA==
X-Received: by 10.224.104.8 with SMTP id m8mr67355467qao.87.1392208344573; Wed, 12 Feb 2014 04:32:24 -0800 (PST)
Received: from new-host.home (pool-108-7-235-60.bstnma.fios.verizon.net. [108.7.235.60]) by mx.google.com with ESMTPSA id r13sm62406544qan.7.2014.02.12.04.32.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Feb 2014 04:32:22 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: calls for discussion
From: Margaret Wasserman <margaretw42@gmail.com>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk>
Date: Wed, 12 Feb 2014 07:32:21 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>, <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk>
To: <l.wood@surrey.ac.uk>
X-Mailer: Apple Mail (2.1510)
X-Mailman-Approved-At: Wed, 12 Feb 2014 08:03:05 -0800
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, 12 Feb 2014 12:32:27 -0000

On Feb 12, 2014, at 6:26 AM, <l.wood@surrey.ac.uk> wrote:

> Starting an idea in the meeting privileges only those who are in the =
room.

It is more complicated than that=85

We like to act/think/talk as though "the people in the room" are a =
meaningful subset of "the people on the mailing list", and therefore are =
aware of the discussion on the list and can make tentative decisions =
that are representative of the list (to be confirmed on the list later). =
The fact is that many of the people in the room at an IETF meeting are =
not even subscribed to the mailing list, and many of the people who are =
subscribed to our mailing lists do not read them.  There is also the =
fact that only a tiny number of people in the room have looked at the =
agenda for this meeting beforehand, and even fewer have read the drafts =
on the agenda. =20

In some other standards organizations, there are no (or fewer) big =
plenary meetings, and the meetings of each WG (in person or via =
telechat) are planned on the list and consist of only those people who =
are most active in the work year-round.  In those organizations, it is =
possible for the people in the room (or on the call) to reach some =
consensus that is likely to be representative of the list, and then say =
"Of course Bob and Dave aren't here, so we better run this by the list =
to make sure that we really have consensus."

That's what the rules of the IETF read like, but in reality the group of =
people in the room is almost entirely disjoint from the group of people =
on the list, and in many WGs, _all_ of the most important decisions have =
been made in a meeting room at an IETF plenary meeting (and merely =
"confirmed" on the list) for many years.  In other words, most of our =
work is _not_ done on the mailing lists, or even by people who are =
reading most of the messages that are sent to those lists.

For instance, in many working groups, virtually all new WG work items =
are adopted via a consensus call in a face-to-face meeting, and a WG =
chair may declare "lack of interest" if only 5% of the people in the =
room show interest in something, even if those 5% represent 90% of the =
people who have read the work in question, and 80% of the people who =
have read even a single message on the WG's mailing list in the last =
year.  So, we have created a situation in which it is usually necessary =
to present a compelling overview of your work to a room full of people =
who have never read your work and are not actively participating in the =
WG mailing list, in order to get your work adopted by an IETF WG.

That stinks, but if we want to change it, we need to _do something to =
change it_.  It does not help to keep stating an untruth as if it were =
the truth.

There are some IETF WGs that operate differently.   They do their work =
on the mailing lists and  have "interim" meetings or telechats as needed =
that are organized on their WG mailing list.  Some of them don't even =
meet at IETF meetings, because they see no value in presenting their =
work-in-progress to the masses.  It would have an unfortunate impact on =
our revenue stream if more groups started operating that way, as our =
main sources of income are tied to attendance at plenary meetings, but =
maybe more groups should try this sort of thing, anyway?

Does anyone have any other ideas about how we can get back to a point =
where most of our decisions are made by people who are active on the WG =
mailing list and interested in the work of the group year-round?

Margaret










From loa@pi.nu  Wed Feb 12 08:04:49 2014
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F6871A05D8 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 08:04:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id J37MoR9yrM3u for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 08:04:45 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 570CD1A09E6 for <ietf@ietf.org>; Wed, 12 Feb 2014 08:04:27 -0800 (PST)
Received: from [192.168.1.4] (unknown [119.95.142.126]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 9EC53180158F; Wed, 12 Feb 2014 17:04:25 +0100 (CET)
Message-ID: <52FB9B7D.90408@pi.nu>
Date: Thu, 13 Feb 2014 00:04:13 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: Does silence have no value? suggested for draft-resnick-on-consensus-06
References: <CADnDZ8-V=PVmp2x9mUyeuztwB1ansE4ZAXufNinsbv2+1Sf=Bw@mail.gmail.com> <CAKHUCzwpf+MpfmYtYwyfQtf7Hq537yi+Yct=2KdMUvsNQWJKPA@mail.gmail.com>
In-Reply-To: <CAKHUCzwpf+MpfmYtYwyfQtf7Hq537yi+Yct=2KdMUvsNQWJKPA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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, 12 Feb 2014 16:04:49 -0000

Dave,

On 2014-02-12 22:51, Dave Cridland wrote:
> Calls for adoption are particularly interesting cases, because if
> there's no response, then as chairman I have to assume there's no
> interest. This could be because of lack of time, of course, but if
> merely checking the draft over for adoption isn't worthy of effort, then
> I can't really expect that once adopted, people will suddenly find the
> time to do serious work.

I think there are a couple of questions around that scenarion - wg
poll met by silence.

- the first is of course why a draft that there are no interest for
   ever were poll, at least the chair who started the poll must have
   thought that the draft had a chance to become a working group
   draft, why would it otherwise be polled
- if there are a participants in the working group, my guess is that
   there are 1.5a opinions what silence mean; my take ii is the wg chair
   to know the wg well enough to tell why people are silent
   There are a number of tricky positions around slience:
   First, there are those that won't bother to say anything unless they
   have objections making the draft a wg doc.
   Second, a number of people, quite easily defined does not say anything
   if the believe that the draft being polled will do no harm if it is
   accepted (there might be an overlap between group 1 and 2)
   Third, there are those that genuinely believe that silence means
   agreement, i.e. if I don't say anything at a wg poll it means that
   I agree
   Fourth there are that have not read the draft and therefore (quite
   sensible) don't respond
   Five, there are those that are opposed to make the draft a working
   group document, but are afraid if they say that they are opposed they
   will start a discussion that leads to that the document in the end
   will get accepted
   Six, those who are silent because a colleague and friend are one of
   the co-authors of the draft, but that would have been opposed under
   circumstances.
   Seven there are those that are in favor, but fear that if they say
   so it will generate more work for themselves
   Eight, there is those who always say something regardless of the
   subject, if they are silent it might be an idea to try to find out
   why.
   And variants thereof, but the point is that to the best of their
   abilities wg chairs should know the landscape. Working group rough
   consensus   is not measured by "hum" or "show of hands" it is called
   by the wg chairs using those and other tools.

The other point is that there never are total silence - and yes I admit
that not mails in response is disturbing - but there are some aspect
that chairs hs to consider.

- I assume that there are some discussion on the mailing list before a
   a draft is polled, should give a hint on where the wg are
- I assume the wg chairs review and agree on going ahead with the poll
- Then there are the folks that has be asked to read and comment prior
   the working group poll, I assume that no wg chair without quite a bit
   of discussion would start a wg poll on a document that the reviewers
   say is not ready
- And last there are the authors - very likely the folks that understand
   the subject best - that says that their draft is ready to become a wg
   document

Together this is quite a sizeable group that the wg chair can use to
break the silence.

Explicitly write in the poll that positive opinions are welcome helps
a lot.

Also if there after all no reactions anyway - the poll can always be
extended and a mail sent asking that those who have opinions actually
say so. It is allowed for authors and/or chairs to poke people they know
are up to speed on the subject and have them respond to the poll.


/Loa
-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From Ted.Lemon@nominum.com  Wed Feb 12 08:04:58 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 804DC1A098F for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 08:04:58 -0800 (PST)
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 Kfm33Ll8es1L for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 08:04:51 -0800 (PST)
Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by ietfa.amsl.com (Postfix) with ESMTP id CCA721A0335 for <ietf@ietf.org>; Wed, 12 Feb 2014 08:04:47 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUvubnx8rIWqPWsN9mHSB//zmCrdASfKX@postini.com; Wed, 12 Feb 2014 08:04:47 PST
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 D34ED1B82E3 for <ietf@ietf.org>; Wed, 12 Feb 2014 08:04:46 -0800 (PST)
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 AF1DC190052; Wed, 12 Feb 2014 08:04:46 -0800 (PST)
Received: from [10.16.2.242] (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, 12 Feb 2014 08:04:34 -0800
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: calls for discussion
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAO_RpcJ9qt6CLmHELTPu0nMNy6E2UtrJ-sEUaXH=Nb8HxjFJhQ@mail.gmail.com>
Date: Wed, 12 Feb 2014 11:04:10 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <9035A3FF-4F26-4086-90D4-2A87E7AB4AF5@nominum.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@mail.gmail.com> <CAO_RpcJ9qt6CLmHELTPu0nMNy6E2UtrJ-sEUaXH=Nb8HxjFJhQ@mail.gmail.com>
To: Chris Elliott <chelliot@pobox.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
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, 12 Feb 2014 16:04:58 -0000

On Feb 12, 2014, at 3:45 AM, Chris Elliott <chelliot@pobox.com> wrote:
> Stupid idea, or worth writing a draft?

It's a good idea.   I don't know for sure that it can work, but it =
matches my experience and desire for in-person meetings.   We do have =
some tradition of asking people to be prepared for meetings, but =
presentations typically don't do that.

There _is_ value in sales pitch presentations, but they don't have to be =
fifteen minutes of powerpoint to be useful.   The point of a sales pitch =
presentation is the same as the point of a BoF: to expose people in the =
room to an idea that they otherwise might not have noticed, so as to =
attract more participation.   Working group chairs shouldn't allow =
random presentations of this type=97it should be done when the chairs =
have some reason to believe the working group attendees will actually =
benefit from the presentation.

So you need to take this into account.

Also, be warned: Broadband Forum just does reading sessions, and they =
are difficult not to sleep through.   So don't go to the opposite =
extreme that way either.   There must be a middle path.


From melinda.shore@gmail.com  Wed Feb 12 08:22:37 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 EDF661A040E for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 08:22:36 -0800 (PST)
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 BaPsn96rCH99 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 08:22:35 -0800 (PST)
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 06C451A03AD for <ietf@ietf.org>; Wed, 12 Feb 2014 08:22:35 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id rp16so9397333pbb.6 for <ietf@ietf.org>; Wed, 12 Feb 2014 08:22:34 -0800 (PST)
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=V9BB/uTi5Q7Mo9avsQx5ReLKahi5YTBKJJOtDhuGzlY=; b=bkiQEVfxw5z3Fzk9jsjic1OBWh16zY0jjL4LZVrXx1q9ptUBKn7OvyXHeCY2qSG0+l Jn+8zKCwr09UGqmEQPsK4nquC6Yb5JVoiBgumojXdgDGWHHyKSLYRPjXt1NFA6WLHJu+ 9ujcu+kfxCKUL6WxR+Je5BiJSVw7JHUc6bGuVdjYG6R9G41aMT/alq3gD+NleLBrtr4B 9nQf6sfOvUDVnECqkXe6CdNWNjEuC6lebSAJo+BokDHv1xrL98EWKShCwh+K0jfyQOok avR1sg2s+sNeOn9t2Tg/Tsl9DuIwNHrROtPb4mN6DmSkGxhqYHS5/cHzziOwWT6YW9sk OvKg==
X-Received: by 10.66.164.165 with SMTP id yr5mr39907705pab.63.1392222154287; Wed, 12 Feb 2014 08:22:34 -0800 (PST)
Received: from spandex.local (216-67-29-177-rb2.sol.dsl.dynamic.acsalaska.net. [216.67.29.177]) by mx.google.com with ESMTPSA id y9sm164615482pas.10.2014.02.12.08.22.33 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 12 Feb 2014 08:22:33 -0800 (PST)
Message-ID: <52FB9FC7.6080705@gmail.com>
Date: Wed, 12 Feb 2014 07:22:31 -0900
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: calls for discussion
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>, <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com>
In-Reply-To: <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2014 16:22:37 -0000

On 2/12/14 3:32 AM, Margaret Wasserman wrote:
> Does anyone have any other ideas about how we can get back to a point
> where most of our decisions are made by people who are active on the
> WG mailing list and interested in the work of the group year-round?

I think it's, at core, a cultural problem, and that we're not
doing a very good job of acculturating participants or even our
leadership.

Another problem is that the email situation has deteriorated a
lot over the past couple of decades, and most of us are now
receiving hundreds of pieces of email/day.  It tends to dissolve
into noise.  At meetings, at least people are there to do the
work of the IETF.

And I suppose it's necessary to point out the irony of so
many "participants" spending meeting time reading email,
although I think a lot of those people are bodies-in-chairs
and not active in the working group in session (we've all
been that person, I think).

Melinda


From sm@elandsys.com  Wed Feb 12 09:36: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 AA31B1A05E0 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 09:36:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 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.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JSg8D8ReyCH3 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 09:36:48 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD921A05E5 for <ietf@ietf.org>; Wed, 12 Feb 2014 09:36:48 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.148.158]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1CHaSwO003155 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 12 Feb 2014 09:36:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392226601; bh=fNR92CrljfSHflH8Xeq7WrMKQueABJ7nrFpa9TTQRV8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VnoVBWJ4NKEMv7IQpUtcdugoz/ATVIt9+k9VaImTokC45lME+N1iBmRZQDehg7wrR LY8YXrdkUCutV3ZmPpUTzZiNSDTvZkxHIFxa8z8oTQ4t79IEJuq7k4C/bbp7KTiHs3 Rj+Wn1PKMy2ekJrfqN8vOnoW6LQ7gXB2sIn/S0Ak=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1392226601; i=@elandsys.com; bh=fNR92CrljfSHflH8Xeq7WrMKQueABJ7nrFpa9TTQRV8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YCFQTRLduaMppZK7lYZlGOxEs55VE25ekZoLa4e3Ryw2rs22B7OObzQqkEB99icAv 9iEOs+VDU7UFxwfwqNkuwPxxERzk84/Uok258WqGmJKv7UVv5NeWSEl+wkuNzJP74F IZ6TuskvbZZKS9ou8k8za1cRZR+f1GY5jRmDBsEs=
Message-Id: <6.2.5.6.2.20140212081345.0a7135f0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 12 Feb 2014 09:34:07 -0800
To: Margaret Wasserman <margaretw42@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: calls for discussion
In-Reply-To: <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable
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, 12 Feb 2014 17:36:55 -0000

Hi Margaret,
At 04:32 12-02-2014, Margaret Wasserman wrote:
>It is more complicated than that=85
>
>We like to act/think/talk as though "the people=20
>in the room" are a meaningful subset of "the=20
>people on the mailing list", and therefore are=20
>aware of the discussion on the list and can make=20
>tentative decisions that are representative of=20
>the list (to be confirmed on the list later).=20
>The fact is that many of the people in the room=20
>at an IETF meeting are not even subscribed to=20
>the mailing list, and many of the people who are=20
>subscribed to our mailing lists do not read=20
>them.  There is also the fact that only a tiny=20
>number of people in the room have looked at the=20
>agenda for this meeting beforehand, and even=20
>fewer have read the drafts on the agenda.

Yes.

>of only those people who are most active in the=20
>work year-round.  In those organizations, it is=20
>possible for the people in the room (or on the=20
>call) to reach some consensus that is likely to=20
>be representative of the list, and then say "Of=20
>course Bob and Dave aren't here, so we better=20
>run this by the list to make sure that we really have consensus."
>
>That's what the rules of the IETF read like, but=20
>in reality the group of people in the room is=20
>almost entirely disjoint from the group of=20
>people on the list, and in many WGs, _all_ of=20
>the most important decisions have been made in a=20
>meeting room at an IETF plenary meeting (and=20
>merely "confirmed" on the list) for many=20
>years.  In other words, most of our work is=20
>_not_ done on the mailing lists, or even by=20
>people who are reading most of the messages that are sent to those lists.

[snip]

>That stinks, but if we want to change it, we=20
>need to _do something to change it_.  It does=20
>not help to keep stating an untruth as if it were the truth.

Yes.

>There are some IETF WGs that operate=20
>differently.   They do their work on the mailing=20
>lists and  have "interim" meetings or telechats=20
>as needed that are organized on their WG mailing=20
>list.  Some of them don't even meet at IETF=20
>meetings, because they see no value in=20
>presenting their work-in-progress to the=20
>masses.  It would have an unfortunate impact on=20
>our revenue stream if more groups started=20
>operating that way, as our main sources of=20
>income are tied to attendance at plenary=20
>meetings, but maybe more groups should try this sort of thing, anyway?

It is not worth having a (working group) meeting=20
if there isn't any major issues to discuss=20
about.  I am not keen about having sloppy minutes=20
for that discussion as it does not make it easier=20
for people not in the room to understand what was=20
discussed and it also does not make matters easier for a non-English=
 audience.

>Does anyone have any other ideas about how we=20
>can get back to a point where most of our=20
>decisions are made by people who are active on=20
>the WG mailing list and interested in the work of the group year-round?

I don't think that it is possible to do go back=20
to an old version of the IETF, assuming that=20
version actually existed.  The incentives are=20
such that decisions are taken at meetings; it=20
works to the advantage of people funded by=20
corporations, it is politically appropriate to=20
live with an untruth or a half-truth.

Regards,
S. Moonesamy=20


From hallam@gmail.com  Wed Feb 12 10:48:52 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 3CD581A0649 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 10:48:52 -0800 (PST)
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 cNIJBR7vP1Wn for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 10:48:49 -0800 (PST)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 7B03C1A0502 for <ietf@ietf.org>; Wed, 12 Feb 2014 10:48:49 -0800 (PST)
Received: by mail-la0-f50.google.com with SMTP id ec20so7273359lab.23 for <ietf@ietf.org>; Wed, 12 Feb 2014 10:48:47 -0800 (PST)
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=+705Z3MQ6LaUmd3aaSetXaaMM9Dikb2puBdtUQtXWXw=; b=ssoVIs/BrACsxmHxmLJhHPHytJXzbgY0UPy3yPciua40AoH+ORIh2eM8D4NNKfKjTl GCVp3SKHNYoT8Asvevf5f7+bhTDhHM3XOH/LBvVRrLxAdZ4OcbJXYHFWLAMwDWBduoxR hWrbpmh8xVlc3zr3xUpuhfD5H9KYASPTbkBap8p9ZmfA2GjvMrZYSQK367iSXxU3QDHS JzLb9T2GE2IUCb0MxWGwIANc3thNFqMtVl0b/UBJ5d3gGHRSjX7F+e8sOU2jLftKlelx yQMQBXgBNs0o6rdgm5jydD9eBivOeoaPDlpDY91G6yapmOIvSc/M64413qQQURFzilcC UteA==
MIME-Version: 1.0
X-Received: by 10.152.23.39 with SMTP id j7mr7930981laf.35.1392230927782; Wed, 12 Feb 2014 10:48:47 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Wed, 12 Feb 2014 10:48:47 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140212081345.0a7135f0@resistor.net>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com> <6.2.5.6.2.20140212081345.0a7135f0@resistor.net>
Date: Wed, 12 Feb 2014 13:48:47 -0500
Message-ID: <CAMm+Lwi-NYmmwgo6e2djMAL4QCnR+pHv8MUfuzvX=d8qhnnTVw@mail.gmail.com>
Subject: Re: calls for discussion
From: Phillip Hallam-Baker <hallam@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=089e0158ca04e55df304f23a0583
Cc: Margaret Wasserman <margaretw42@gmail.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: Wed, 12 Feb 2014 18:48:52 -0000

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

The decisions are taken by the stakeholders.

If Cisco does not want to support some new routing protocol then it won't
be deployed. There are many similar gatekeepers.

But Cisco, Google, etc. etc. are managed by people who understand the value
of being open to a wide range of ideas and companies who have not been open
in that fashion have not survived as gatekeepers for very long. The IETF
was formed at a time that IBM was losing that position. Cisco is ultimately
responsive to its customers which are ISPs who are in turn responsive to
their customers, the Internet users. So the IETF is in part a feedback loop
which helps the thoughtful large companies align their interests with those
of their customer's customers.

Another reason they are open to being persuaded is that changing the
Internet is a collective action problem and most of the decision makers
only hold veto power. To change the Internet multiple decision makers have
to agree on a common course of action.

So the IETF is one of the forums where people have an opportunity to
influence the ultimate decision makers. If you attend in person you have
more opportunity to be influential.

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

<div dir=3D"ltr"><div class=3D"gmail_extra">The decisions are taken by the =
stakeholders.
</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">If Ci=
sco does not want to support some new routing protocol then it won&#39;t be=
 deployed. There are many similar gatekeepers.</div><div class=3D"gmail_ext=
ra">
<br></div><div class=3D"gmail_extra">But Cisco, Google, etc. etc. are manag=
ed by people who understand the value of being open to a wide range of idea=
s and companies who have not been open in that fashion have not survived as=
 gatekeepers for very long. The IETF was formed at a time that IBM was losi=
ng that position. Cisco is ultimately responsive to its customers which are=
 ISPs who are in turn responsive to their customers, the Internet users. So=
 the IETF is in part a feedback loop which helps the thoughtful large compa=
nies align their interests with those of their customer&#39;s customers.</d=
iv>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Another rea=
son they are open to being persuaded is that changing the Internet is a col=
lective action problem and most of the decision makers only hold veto power=
. To change the Internet multiple decision makers have to agree on a common=
 course of action.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">So the IETF=
 is one of the forums where people have an opportunity to influence the ult=
imate decision makers. If you attend in person you have more opportunity to=
 be influential.</div>
</div>

--089e0158ca04e55df304f23a0583--


From hallam@gmail.com  Wed Feb 12 11:52:55 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 E05C11A06CF; Wed, 12 Feb 2014 11:52:55 -0800 (PST)
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 PpiNvO4GkCbC; Wed, 12 Feb 2014 11:52:51 -0800 (PST)
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 0665E1A06BE; Wed, 12 Feb 2014 11:52:50 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id c11so7606731lbj.3 for <multiple recipients>; Wed, 12 Feb 2014 11:52:49 -0800 (PST)
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=cXLxHTTxq1GKrHHEuUohpooWoAC+ExqEmN2+hgxa++Y=; b=zsMv3tc2u6HXFIwHRVDlwfis2JpNPwgMixmEXYs+N5AyYyhkC3sG6Xq5/Uv6kmk6Mv WXa6yuog/M1LjV4wYzv6uZM/ZB38++QT8XyLJANZTEfe27xQxSN0+uG6+YDxftSosczd cNVa9gNx87v4TAOSurir8i4AFh/rZ+di47X/pbAG8rGK2+g4OQdiMYLaDfO0iX9AkJ29 soTOfgWRHtUkJ1w675dmgt3CWJ9Ij3sxOupoWdxNpiEqzHSykn1P1GY/Ng411ezvYCFm Pwe+nuB6hq+qhexfiXFjhrF3MQ3JjgFXkXYZwxjQEcqC98Tdxu/CDJ9K1gc1dzKkHM3+ fbmw==
MIME-Version: 1.0
X-Received: by 10.152.43.103 with SMTP id v7mr3183622lal.46.1392234769463; Wed, 12 Feb 2014 11:52:49 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Wed, 12 Feb 2014 11:52:49 -0800 (PST)
In-Reply-To: <m2ha85tff2.wl%randy@psg.com>
References: <20140211131635.4764.88322.idtracker@ietfa.amsl.com> <6C3F924B-EDFF-42BC-9075-D4930636E643@vigilsec.com> <m2ha85tff2.wl%randy@psg.com>
Date: Wed, 12 Feb 2014 14:52:49 -0500
Message-ID: <CAMm+LwgMHVPK3aAp5SCQFFXqKJyhsOFpFk_hwpmShv4YTCzj3Q@mail.gmail.com>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-policy-qualifiers-01.txt> (Policy Qualifiers in RPKI Certificates) to Proposed Standard
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=001a11c34dcae0bcc704f23aea69
Cc: IETF Discussion Mailing List <ietf@ietf.org>, IETF SIDR <sidr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2014 19:52:56 -0000

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

On Tue, Feb 11, 2014 at 6:09 PM, Randy Bush <randy@psg.com> wrote:

> > Implementers do not do anything with a CPS pointer in a policy
> > qualifier.  So, this addition will not impact interoperability.
>
> in other words it has no operational use


It has a legal significance.

The terms and conditions are specified within the four corners of the
certificate. This has huge importance in any legal dispute arising out of
the use or misuse of the certificate and allows the issuer to control their
exposure to litigation risk.

The fact that relying parties choose to ignore the policy information does
not mean that it does not affect their ability to hold the issuer liable.



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

--001a11c34dcae0bcc704f23aea69
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 T=
ue, Feb 11, 2014 at 6:09 PM, Randy Bush <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:randy@psg.com" target=3D"_blank">randy@psg.com</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
<div class=3D"">&gt; Implementers do not do anything with a CPS pointer in =
a policy<br>
&gt; qualifier. =A0So, this addition will not impact interoperability.<br>
<br>
</div>in other words it has no operational use</blockquote><div><br></div><=
div>It has a legal significance.</div><div><br></div><div>The terms and con=
ditions are specified within the four corners of the certificate. This has =
huge importance in any legal dispute arising out of the use or misuse of th=
e certificate and allows the issuer to control their exposure to litigation=
 risk.</div>
<div><br></div><div>The fact that relying parties choose to ignore the poli=
cy information does not mean that it does not affect their ability to hold =
the issuer liable.</div><div>=A0<br></div></div><br clear=3D"all"><div><br>
</div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambake=
r.com/</a><br>
</div></div>

--001a11c34dcae0bcc704f23aea69--


From sra@hactrn.net  Wed Feb 12 13:06:24 2014
Return-Path: <sra@hactrn.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 175341A06B7; Wed, 12 Feb 2014 13:06:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GUv0lOoCqubq; Wed, 12 Feb 2014 13:06:22 -0800 (PST)
Received: from cyteen.hactrn.net (cyteen.hactrn.net [66.92.66.68]) by ietfa.amsl.com (Postfix) with ESMTP id 0BFBE1A0620; Wed, 12 Feb 2014 13:06:22 -0800 (PST)
Received: from thrintun.hactrn.net (thrintun.hactrn.net [IPv6:2002:425c:4242:0:219:d1ff:fe12:5d30]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "thrintun.hactrn.net", Issuer "Grunchweather Associates" (verified OK)) by cyteen.hactrn.net (Postfix) with ESMTPS id 14B7B7304C; Wed, 12 Feb 2014 21:06:20 +0000 (UTC)
Received: from thrintun.hactrn.net (localhost [IPv6:::1]) by thrintun.hactrn.net (Postfix) with ESMTP id BE1EC170A4; Wed, 12 Feb 2014 16:06:19 -0500 (EST)
Date: Wed, 12 Feb 2014 16:06:19 -0500
From: Rob Austein <sra@hactrn.net>
To: IETF Discussion Mailing List <ietf@ietf.org>, IETF SIDR <sidr@ietf.org>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-policy-qualifiers-01.txt> (Policy Qualifiers in RPKI Certificates) to Proposed Standard
In-Reply-To: <CAMm+LwgMHVPK3aAp5SCQFFXqKJyhsOFpFk_hwpmShv4YTCzj3Q@mail.gmail.com>
References: <20140211131635.4764.88322.idtracker@ietfa.amsl.com> <6C3F924B-EDFF-42BC-9075-D4930636E643@vigilsec.com> <m2ha85tff2.wl%randy@psg.com> <CAMm+LwgMHVPK3aAp5SCQFFXqKJyhsOFpFk_hwpmShv4YTCzj3Q@mail.gmail.com>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/23.4 Mule/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII
Message-Id: <20140212210619.BE1EC170A4@thrintun.hactrn.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, 12 Feb 2014 21:06:24 -0000

Since we seem to be re-hashing some of the issues discussed during
WGLC of this draft:

I don't agree that this draft is harmless: I think it's an attractive
nuisance.  Given that we already have an RIR which makes people sign a
non-disclosure agreement (!) to get a copy of their trust anchor
locator, it's not all that far-fetched to imagine that same RIR adding
another contractual requirement in which the user of their trust
anchor locator is also made to promise that they will perform
additional checks outside the core specification using the URI
specified in the policy qualifier.  The draft doesn't rule this out,
it just says that the draft itself adds no such processing
requirements.  I do not find this particularly reassuring.

That said, the RIR in question has already demonstrated that they
don't need policy qualifiers to impose whacky restrictions outside the
scope of the protocol architecture, so denying them use of this policy
qualifier hack wouldn't gain the user community all that much.


From l.wood@surrey.ac.uk  Wed Feb 12 14:17: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 6357F1A0015 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 14:17:48 -0800 (PST)
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 vVq1Qm1rUdQ4 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 14:17:45 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.139]) by ietfa.amsl.com (Postfix) with ESMTP id D0D571A0002 for <ietf@ietf.org>; Wed, 12 Feb 2014 14:17:44 -0800 (PST)
Received: from [85.158.136.51:15643] by server-3.bemta-5.messagelabs.com id E9/27-13671-703FBF25; Wed, 12 Feb 2014 22:17:43 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-49.messagelabs.com!1392243462!26684552!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 14812 invoked from network); 12 Feb 2014 22:17:42 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-10.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 12 Feb 2014 22:17:42 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 12 Feb 2014 22:17:41 +0000
From: <l.wood@surrey.ac.uk>
To: <loa@pi.nu>, <ietf@ietf.org>
Date: Wed, 12 Feb 2014 22:17:41 +0000
Subject: RE: calls for discussion
Thread-Topic: calls for discussion
Thread-Index: Ac8n861Msjxc0tFnShebnggtcxhm9AASlN+g
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334718@EXMB01CMS.surrey.ac.uk>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>, <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk>, <52FB7278.8020201@pi.nu>
In-Reply-To: <52FB7278.8020201@pi.nu>
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
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2014 22:17:48 -0000

There's a distinction between 'privileges some' and 'completely excludes ot=
hers'.

But, to give an example, an interesting comparison: a while back we gave an=
 update on a protocol to an IETF area meeting. We'd written four interrelat=
ed drafts, including discussion of congestion control, exposed it to a coup=
le of working groups over the course of a couple of years, done our mailing=
 list work and homework.

A Rather Large Company gave an update on their protocol in that session as =
well. They hadn't written an internet draft, or discussed it much on IETF m=
ailing lists - because to discuss something, you really need an internet dr=
aft as a common frame of reference. But, hey, Big Company, threatening to d=
eploy and change the world. Much meeting discussion was then given over to =
'will you write an internet draft?' and 'have you considered congestion con=
trol?' Not productive use of facetoface time for most. Beneficial to the co=
mpany, and possibly to others who would be affected by deployment of this p=
rotocol? Well, yes, so including them was worthwhile, and we need to be inc=
lusionary and encourage new ideas. But they were privileged by being in the=
 room. (And I don't think they've written a draft up yet either. Couldn't f=
ind one.)

That is what I mean by privilege. If you can go to meetings, you can skip a=
 lot of understanding of the IETF through mailing lists.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Loa Andersson [loa@pi.nu]
Sent: 12 February 2014 13:09
To: ietf@ietf.org
Cc: Wood L  Dr (Electronic Eng)
Subject: Re: calls for discussion

All,

First I agree with Lloyd the misuse of normtive language in mails,
jsut look a bit peculiar and does not carry any weight.

Lloyd,
While it is true that most work in the IETF happens on mailing lists,
and should be taken there as fast as is ever possible, it is not true
that all work is is done on mailing lists. If it did everything in
Note Well that does say anything about things that does not happen on
the mailing lists would be moot.

I hope you don't want to real work coming out of chance meetings in
the corridors of the IETF meeting venue. Consider me walking down the
corridor and by chance happens to start talking to the a bright person
from one of my worst competitors about something that has slowly
emerged in my  head over the last few hours. He or she confirms the
same problem has just occurred him/her. After 10 mins of discussion we
have something that can go into a draft.

Do you seriously say that we should be stopped for writing the draft,
just because our discussion took place face to face, rather than on
a mailing list?

/Loa

On 2014-02-12 19:26, l.wood@surrey.ac.uk wrote:
> Starting an idea in the meeting privileges only those who are in the room=
.
>
> The work of the IETF is on the mailing lists.
>
> You MUST stop using normative language in emails. It carries no weight.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun [abduss=
alambaryun@gmail.com]
> Sent: 12 February 2014 10:16
> To: Randy Bush
> Cc: IETF Disgust
> Subject: Re: calls for discussion
>
> On 2/12/14, Randy Bush <randy@psg.com> wrote:
>> we waste immense amounts of time of the literate in a hopeless attempt
>> to insert clue into the lazy or illiterate.
>
> The drafts are requested on the lists to be presented and all have
> same chance to present or object to a presentation, chairs SHOULD only
> put the request on the list and see priorities and agreements from the
> WG.
>>
>> just say a hard no to "i want to present draft-..."  has your draft been
>> discussed on the mailing list and has shown serious divergence of views
>> such that facetime is really needed?
>
> No, there can be a chance to start discussions in meetings as well. I
> recommend you object the drafts that you think is a waste of your time
> and discuss with your WGs, without throwing vegetables.
>
> AB
>

--


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From ggm@algebras.org  Wed Feb 12 15:05:34 2014
Return-Path: <ggm@algebras.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 8E8EF1A0023 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 15:05:34 -0800 (PST)
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 OmvOS-nYbS-q for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 15:05:30 -0800 (PST)
Received: from mail-pa0-f43.google.com (mail-pa0-f43.google.com [209.85.220.43]) by ietfa.amsl.com (Postfix) with ESMTP id D92BF1A001F for <ietf@ietf.org>; Wed, 12 Feb 2014 15:05:30 -0800 (PST)
Received: by mail-pa0-f43.google.com with SMTP id rd3so9861145pab.30 for <ietf@ietf.org>; Wed, 12 Feb 2014 15:05:30 -0800 (PST)
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=ryIcS6Vd4FZw5xFzyPchbfuvxQSKvH38FDSMAfcWRCg=; b=jTkJ4XyKLIl3TDPOB53n8ZLfXE8MVcq+ITSmSiGRqt+eBlKDcWQA6yfGcgXkLvoL8S tj6jxZpLFKtQKE12gJ4DuqdKaj431YLhq9hFVzLnO/jrmqJ3MRMSGbzSCwGT3mcXFh97 W3SrUOZ3PSMQPP4ItSo2XYCkjmOqSazKYEXYlilvdg9h9JokpufidHRFxVLiE7S6C/AF b5HuToOY8AExO1tUgrx11DwMmbpjZsaf5Kl/7n1SqJAk9qFft9n1jcCzjbGePZAWFKp2 E4ueUo27+ut2WIBeX/FsoXs6eUtwtqGe6P4WZgJhfD1vVL0xMYdxKIafw9vPKZmD4xT5 koYw==
X-Gm-Message-State: ALoCoQkgFlMQ+uVs3BwfyryjqrzOg182KWveJU7gL+2MqFLymI4D+jvtNbT3IXWpLw15T8u3fi/l
MIME-Version: 1.0
X-Received: by 10.66.119.172 with SMTP id kv12mr42301063pab.34.1392246329973;  Wed, 12 Feb 2014 15:05:29 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Wed, 12 Feb 2014 15:05:29 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:154b:c651:8e62:8ab5]
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334718@EXMB01CMS.surrey.ac.uk>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <52FB7278.8020201@pi.nu> <290E20B455C66743BE178C5C84F1240847E6334718@EXMB01CMS.surrey.ac.uk>
Date: Thu, 13 Feb 2014 09:05:29 +1000
Message-ID: <CAKr6gn2cUPR-VGV-VpsujzkNUK0V45pyk_pSC3e5Onf74WBfFA@mail.gmail.com>
Subject: Re: calls for discussion
From: George Michaelson <ggm@algebras.org>
To: l.wood@surrey.ac.uk
Content-Type: multipart/alternative; boundary=e89a8ffbac1df03e3904f23d9bae
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, 12 Feb 2014 23:05:34 -0000

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

Its a long time since I attended a WG where the simple formalisms of "read
the drafts" and "if not participating, please sit at the back" got applied.

I don't feel objectified being combed out like this, It gives me comfort I
can 'audit' a session without impeding real work, and it makes it clearer
the obligations on me if I chose to speak to the mike, ill prepared.

I realize the best course would be not to be in the room if not able to
contribute, but you will (I hope) understand that being close to a meeting
with potential for interest is hard to subsume. Hence, my suggestion more
WG chairs actively canvas who in the room CAN meaningfully discuss, and
prioritize seating accordingly (or at least suggest it)


On Thu, Feb 13, 2014 at 8:17 AM, <l.wood@surrey.ac.uk> wrote:

> There's a distinction between 'privileges some' and 'completely excludes
> others'.
>
> But, to give an example, an interesting comparison: a while back we gave
> an update on a protocol to an IETF area meeting. We'd written four
> interrelated drafts, including discussion of congestion control, exposed it
> to a couple of working groups over the course of a couple of years, done
> our mailing list work and homework.
>
> A Rather Large Company gave an update on their protocol in that session as
> well. They hadn't written an internet draft, or discussed it much on IETF
> mailing lists - because to discuss something, you really need an internet
> draft as a common frame of reference. But, hey, Big Company, threatening to
> deploy and change the world. Much meeting discussion was then given over to
> 'will you write an internet draft?' and 'have you considered congestion
> control?' Not productive use of facetoface time for most. Beneficial to the
> company, and possibly to others who would be affected by deployment of this
> protocol? Well, yes, so including them was worthwhile, and we need to be
> inclusionary and encourage new ideas. But they were privileged by being in
> the room. (And I don't think they've written a draft up yet either.
> Couldn't find one.)
>
> That is what I mean by privilege. If you can go to meetings, you can skip
> a lot of understanding of the IETF through mailing lists.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: Loa Andersson [loa@pi.nu]
> Sent: 12 February 2014 13:09
> To: ietf@ietf.org
> Cc: Wood L  Dr (Electronic Eng)
> Subject: Re: calls for discussion
>
> All,
>
> First I agree with Lloyd the misuse of normtive language in mails,
> jsut look a bit peculiar and does not carry any weight.
>
> Lloyd,
> While it is true that most work in the IETF happens on mailing lists,
> and should be taken there as fast as is ever possible, it is not true
> that all work is is done on mailing lists. If it did everything in
> Note Well that does say anything about things that does not happen on
> the mailing lists would be moot.
>
> I hope you don't want to real work coming out of chance meetings in
> the corridors of the IETF meeting venue. Consider me walking down the
> corridor and by chance happens to start talking to the a bright person
> from one of my worst competitors about something that has slowly
> emerged in my  head over the last few hours. He or she confirms the
> same problem has just occurred him/her. After 10 mins of discussion we
> have something that can go into a draft.
>
> Do you seriously say that we should be stopped for writing the draft,
> just because our discussion took place face to face, rather than on
> a mailing list?
>
> /Loa
>
> On 2014-02-12 19:26, l.wood@surrey.ac.uk wrote:
> > Starting an idea in the meeting privileges only those who are in the
> room.
> >
> > The work of the IETF is on the mailing lists.
> >
> > You MUST stop using normative language in emails. It carries no weight.
> >
> > Lloyd Wood
> > http://about.me/lloydwood
> > ________________________________________
> > From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun [
> abdussalambaryun@gmail.com]
> > Sent: 12 February 2014 10:16
> > To: Randy Bush
> > Cc: IETF Disgust
> > Subject: Re: calls for discussion
> >
> > On 2/12/14, Randy Bush <randy@psg.com> wrote:
> >> we waste immense amounts of time of the literate in a hopeless attempt
> >> to insert clue into the lazy or illiterate.
> >
> > The drafts are requested on the lists to be presented and all have
> > same chance to present or object to a presentation, chairs SHOULD only
> > put the request on the list and see priorities and agreements from the
> > WG.
> >>
> >> just say a hard no to "i want to present draft-..."  has your draft been
> >> discussed on the mailing list and has shown serious divergence of views
> >> such that facetime is really needed?
> >
> > No, there can be a chance to start discussions in meetings as well. I
> > recommend you object the drafts that you think is a waste of your time
> > and discuss with your WGs, without throwing vegetables.
> >
> > AB
> >
>
> --
>
>
> Loa Andersson                        email: loa@mail01.huawei.com
> Senior MPLS Expert                          loa@pi.nu
> Huawei Technologies (consultant)     phone: +46 739 81 21 64
>
>

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

<div dir=3D"ltr">Its a long time since I attended a WG where the simple for=
malisms of &quot;read the drafts&quot; and &quot;if not participating, plea=
se sit at the back&quot; got applied.<br><div><br></div><div>I don&#39;t fe=
el objectified being combed out like this, It gives me comfort I can &#39;a=
udit&#39; a session without impeding real work, and it makes it clearer the=
 obligations on me if I chose to speak to the mike, ill prepared.</div>
<div><br></div><div>I realize the best course would be not to be in the roo=
m if not able to contribute, but you will (I hope) understand that being cl=
ose to a meeting with potential for interest is hard to subsume. Hence, my =
suggestion more WG chairs actively canvas who in the room CAN meaningfully =
discuss, and prioritize seating accordingly (or at least suggest it)</div>
</div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu,=
 Feb 13, 2014 at 8:17 AM,  <span dir=3D"ltr">&lt;<a href=3D"mailto:l.wood@s=
urrey.ac.uk" target=3D"_blank">l.wood@surrey.ac.uk</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">
There&#39;s a distinction between &#39;privileges some&#39; and &#39;comple=
tely excludes others&#39;.<br>
<br>
But, to give an example, an interesting comparison: a while back we gave an=
 update on a protocol to an IETF area meeting. We&#39;d written four interr=
elated drafts, including discussion of congestion control, exposed it to a =
couple of working groups over the course of a couple of years, done our mai=
ling list work and homework.<br>

<br>
A Rather Large Company gave an update on their protocol in that session as =
well. They hadn&#39;t written an internet draft, or discussed it much on IE=
TF mailing lists - because to discuss something, you really need an interne=
t draft as a common frame of reference. But, hey, Big Company, threatening =
to deploy and change the world. Much meeting discussion was then given over=
 to &#39;will you write an internet draft?&#39; and &#39;have you considere=
d congestion control?&#39; Not productive use of facetoface time for most. =
Beneficial to the company, and possibly to others who would be affected by =
deployment of this protocol? Well, yes, so including them was worthwhile, a=
nd we need to be inclusionary and encourage new ideas. But they were privil=
eged by being in the room. (And I don&#39;t think they&#39;ve written a dra=
ft up yet either. Couldn&#39;t find one.)<br>

<br>
That is what I mean by privilege. If you can go to meetings, you can skip a=
 lot of understanding of the IETF through mailing lists.<br>
<div class=3D""><br>
Lloyd Wood<br>
<a href=3D"http://about.me/lloydwood" target=3D"_blank">http://about.me/llo=
ydwood</a><br>
________________________________________<br>
</div>From: Loa Andersson [<a href=3D"mailto:loa@pi.nu">loa@pi.nu</a>]<br>
Sent: 12 February 2014 13:09<br>
To: <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a><br>
Cc: Wood L =A0Dr (Electronic Eng)<br>
<div class=3D"HOEnZb"><div class=3D"h5">Subject: Re: calls for discussion<b=
r>
<br>
All,<br>
<br>
First I agree with Lloyd the misuse of normtive language in mails,<br>
jsut look a bit peculiar and does not carry any weight.<br>
<br>
Lloyd,<br>
While it is true that most work in the IETF happens on mailing lists,<br>
and should be taken there as fast as is ever possible, it is not true<br>
that all work is is done on mailing lists. If it did everything in<br>
Note Well that does say anything about things that does not happen on<br>
the mailing lists would be moot.<br>
<br>
I hope you don&#39;t want to real work coming out of chance meetings in<br>
the corridors of the IETF meeting venue. Consider me walking down the<br>
corridor and by chance happens to start talking to the a bright person<br>
from one of my worst competitors about something that has slowly<br>
emerged in my =A0head over the last few hours. He or she confirms the<br>
same problem has just occurred him/her. After 10 mins of discussion we<br>
have something that can go into a draft.<br>
<br>
Do you seriously say that we should be stopped for writing the draft,<br>
just because our discussion took place face to face, rather than on<br>
a mailing list?<br>
<br>
/Loa<br>
<br>
On 2014-02-12 19:26, <a href=3D"mailto:l.wood@surrey.ac.uk">l.wood@surrey.a=
c.uk</a> wrote:<br>
&gt; Starting an idea in the meeting privileges only those who are in the r=
oom.<br>
&gt;<br>
&gt; The work of the IETF is on the mailing lists.<br>
&gt;<br>
&gt; You MUST stop using normative language in emails. It carries no weight=
.<br>
&gt;<br>
&gt; Lloyd Wood<br>
&gt; <a href=3D"http://about.me/lloydwood" target=3D"_blank">http://about.m=
e/lloydwood</a><br>
&gt; ________________________________________<br>
&gt; From: ietf [<a href=3D"mailto:ietf-bounces@ietf.org">ietf-bounces@ietf=
.org</a>] On Behalf Of Abdussalam Baryun [<a href=3D"mailto:abdussalambaryu=
n@gmail.com">abdussalambaryun@gmail.com</a>]<br>
&gt; Sent: 12 February 2014 10:16<br>
&gt; To: Randy Bush<br>
&gt; Cc: IETF Disgust<br>
&gt; Subject: Re: calls for discussion<br>
&gt;<br>
&gt; On 2/12/14, Randy Bush &lt;<a href=3D"mailto:randy@psg.com">randy@psg.=
com</a>&gt; wrote:<br>
&gt;&gt; we waste immense amounts of time of the literate in a hopeless att=
empt<br>
&gt;&gt; to insert clue into the lazy or illiterate.<br>
&gt;<br>
&gt; The drafts are requested on the lists to be presented and all have<br>
&gt; same chance to present or object to a presentation, chairs SHOULD only=
<br>
&gt; put the request on the list and see priorities and agreements from the=
<br>
&gt; WG.<br>
&gt;&gt;<br>
&gt;&gt; just say a hard no to &quot;i want to present draft-...&quot; =A0h=
as your draft been<br>
&gt;&gt; discussed on the mailing list and has shown serious divergence of =
views<br>
&gt;&gt; such that facetime is really needed?<br>
&gt;<br>
&gt; No, there can be a chance to start discussions in meetings as well. I<=
br>
&gt; recommend you object the drafts that you think is a waste of your time=
<br>
&gt; and discuss with your WGs, without throwing vegetables.<br>
&gt;<br>
&gt; AB<br>
&gt;<br>
<br>
--<br>
<br>
<br>
Loa Andersson =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0email: <a href=
=3D"mailto:loa@mail01.huawei.com">loa@mail01.huawei.com</a><br>
Senior MPLS Expert =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0<a hr=
ef=3D"mailto:loa@pi.nu">loa@pi.nu</a><br>
Huawei Technologies (consultant) =A0 =A0 phone: <a href=3D"tel:%2B46%20739%=
2081%2021%2064" value=3D"+46739812164">+46 739 81 21 64</a><br>
<br>
</div></div></blockquote></div><br></div>

--e89a8ffbac1df03e3904f23d9bae--


From ggm@algebras.org  Wed Feb 12 15:09:54 2014
Return-Path: <ggm@algebras.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 EECCA1A0026 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 15:09:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 JYdMByjxrpOA for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 15:09:52 -0800 (PST)
Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) by ietfa.amsl.com (Postfix) with ESMTP id 71CAE1A0025 for <ietf@ietf.org>; Wed, 12 Feb 2014 15:09:52 -0800 (PST)
Received: by mail-pd0-f169.google.com with SMTP id v10so9694750pde.28 for <ietf@ietf.org>; Wed, 12 Feb 2014 15:09:51 -0800 (PST)
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=KyrTW4mb/34vTW648aZoKH5g0qrcbgFB+TJgSvXgjgI=; b=PAy+p5y6XZk0ksz6ZxADv2FTRyScxdIN2Ua+wBuC0p1AaSkQdqziqvQoaTojfQaBm4 Azrkt7i38Fhrpdv6EsHo4RNAR4UGWBCYggoKjTNjiDzeXPYqvANU6HAyd/WCwrfhAtCr zhGZ/JDDSlDb6h5TgZkbjNAdd4S88syrRGBZ6QipkaISPV6D7SeVDicAOBpuPmoIst2Q MX4CQjhdavLDvZzFlqGl5SLw/T0Wq52rYV6yazJSuXTtjWEBQUIXXCXPW8S4jzPy0pgt 8Z7NrggBcbfcXMzyrv1Nm3wmivyN1J5JiNpjvdcMWe0ZPGh6I81v3CK/EpXWTgNETUn+ 4YEA==
X-Gm-Message-State: ALoCoQnsOtHMZm45ZUgs996VRYkuDr0woitLwobf2KwK5s6tIauQvVllyUHSZAnEp6C6jyYXwPvL
MIME-Version: 1.0
X-Received: by 10.66.27.201 with SMTP id v9mr26175569pag.136.1392246591564; Wed, 12 Feb 2014 15:09:51 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Wed, 12 Feb 2014 15:09:51 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:154b:c651:8e62:8ab5]
In-Reply-To: <20140212210619.BE1EC170A4@thrintun.hactrn.net>
References: <20140211131635.4764.88322.idtracker@ietfa.amsl.com> <6C3F924B-EDFF-42BC-9075-D4930636E643@vigilsec.com> <m2ha85tff2.wl%randy@psg.com> <CAMm+LwgMHVPK3aAp5SCQFFXqKJyhsOFpFk_hwpmShv4YTCzj3Q@mail.gmail.com> <20140212210619.BE1EC170A4@thrintun.hactrn.net>
Date: Thu, 13 Feb 2014 09:09:51 +1000
Message-ID: <CAKr6gn3stGDKLowcpOz_ZmMENpC8onYpDT-FRyhUvXjkMjfTfQ@mail.gmail.com>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-policy-qualifiers-01.txt> (Policy Qualifiers in RPKI Certificates) to Proposed Standard
From: George Michaelson <ggm@algebras.org>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=bcaec529987d87f69604f23dabcb
Cc: IETF SIDR <sidr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Feb 2014 23:09:54 -0000

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

Whilst I agree it has no operational consequence for current relying party
code, or consumers of the products of certificates embedded in online
systems, I don't agree with Randy's or Rob's conclusions regarding the
desirability or risks of this feature.

I think this is a useful addition to the qualities of information in a
certificate, and I support its status.

Since the drivers are non-operational, I don't feel it useful to try and
suggest there are any. I also think that should not preclude the adoption
of this requirement in certificates.

This is a documentation and risk-minimisation process which makes layer-9
happy.

-George


On Thu, Feb 13, 2014 at 7:06 AM, Rob Austein <sra@hactrn.net> wrote:

> Since we seem to be re-hashing some of the issues discussed during
> WGLC of this draft:
>
> I don't agree that this draft is harmless: I think it's an attractive
> nuisance.  Given that we already have an RIR which makes people sign a
> non-disclosure agreement (!) to get a copy of their trust anchor
> locator, it's not all that far-fetched to imagine that same RIR adding
> another contractual requirement in which the user of their trust
> anchor locator is also made to promise that they will perform
> additional checks outside the core specification using the URI
> specified in the policy qualifier.  The draft doesn't rule this out,
> it just says that the draft itself adds no such processing
> requirements.  I do not find this particularly reassuring.
>
> That said, the RIR in question has already demonstrated that they
> don't need policy qualifiers to impose whacky restrictions outside the
> scope of the protocol architecture, so denying them use of this policy
> qualifier hack wouldn't gain the user community all that much.
>
>

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

<div dir=3D"ltr">Whilst I agree it has no operational consequence for curre=
nt relying party code, or consumers of the products of certificates embedde=
d in online systems, I don&#39;t agree with Randy&#39;s or Rob&#39;s conclu=
sions regarding the desirability or risks of this feature.<div>
<br></div><div>I think this is a useful addition to the qualities of inform=
ation in a certificate, and I support its status.<div><br></div><div>Since =
the drivers are non-operational, I don&#39;t feel it useful to try and sugg=
est there are any. I also think that should not preclude the adoption of th=
is requirement in certificates.</div>
<div><br></div><div>This is a documentation and risk-minimisation process w=
hich makes layer-9 happy.</div><div><br></div><div>-George</div></div></div=
><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Thu, Feb =
13, 2014 at 7:06 AM, Rob Austein <span dir=3D"ltr">&lt;<a href=3D"mailto:sr=
a@hactrn.net" target=3D"_blank">sra@hactrn.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">Since we seem to be re-hashing some of the i=
ssues discussed during<br>
WGLC of this draft:<br>
<br>
I don&#39;t agree that this draft is harmless: I think it&#39;s an attracti=
ve<br>
nuisance. =A0Given that we already have an RIR which makes people sign a<br=
>
non-disclosure agreement (!) to get a copy of their trust anchor<br>
locator, it&#39;s not all that far-fetched to imagine that same RIR adding<=
br>
another contractual requirement in which the user of their trust<br>
anchor locator is also made to promise that they will perform<br>
additional checks outside the core specification using the URI<br>
specified in the policy qualifier. =A0The draft doesn&#39;t rule this out,<=
br>
it just says that the draft itself adds no such processing<br>
requirements. =A0I do not find this particularly reassuring.<br>
<br>
That said, the RIR in question has already demonstrated that they<br>
don&#39;t need policy qualifiers to impose whacky restrictions outside the<=
br>
scope of the protocol architecture, so denying them use of this policy<br>
qualifier hack wouldn&#39;t gain the user community all that much.<br>
<br>
</blockquote></div><br></div>

--bcaec529987d87f69604f23dabcb--


From randy@psg.com  Wed Feb 12 16:22:45 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 2AA081A0063 for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 16:22:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SnR8Il2eTZ6I for <ietf@ietfa.amsl.com>; Wed, 12 Feb 2014 16:22:43 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id E74331A0054 for <ietf@ietf.org>; Wed, 12 Feb 2014 16:22:42 -0800 (PST)
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 1WDk4W-000574-Ug; Thu, 13 Feb 2014 00:22:33 +0000
Date: Thu, 13 Feb 2014 09:22:31 +0900
Message-ID: <m2txc3rhdk.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: calls for discussion
In-Reply-To: <6.2.5.6.2.20140212081345.0a7135f0@resistor.net>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com> <6.2.5.6.2.20140212081345.0a7135f0@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
Cc: Margaret Wasserman <margaretw42@gmail.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, 13 Feb 2014 00:22:45 -0000

> I don't think that it is possible to do go back 
> to an old version of the IETF, assuming that 
> version actually existed.  The incentives are 
> such that decisions are taken at meetings; it 
> works to the advantage of people funded by 
> corporations, it is politically appropriate to 
> live with an untruth or a half-truth.

it's not just meetings.  who has funding to spend a lot of time on ietf
work?  vendors employees.  http://archive.psg.com/051000.ccr-ivtf.html
it's not evil.  it's not collusion.  it's just physics in a capitalist
society.

i go to ietf meetings because i get a lot done.  but little of it is in
wg meetings as they have been drowned in ppt.  which means, among other
things, that it is not recorded in any way useful for folk unable to
attend.

the part i really love is when a serious discussion erupts in a wg
meeting and it gets shut down because the agenda has more ppt on the
schedule.

btw, i think many chairs try to ameliorate this and actually try to make
serious agenda space for discussion.  but the pressure on them "i
deserve to be able to present my ppt" makes it difficult.

and the rush to get one's draft done in time so one can present ppt at
the meeting means that those who actually care enough to read drafts
get hit by a massive load just before the meeting so can not do as high
a quality review as they might like.

randy


From randy@psg.com  Wed Feb 12 17:08:12 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 8003C1A009A; Wed, 12 Feb 2014 17:08:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B2nhmbu2Uly1; Wed, 12 Feb 2014 17:08:11 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 238531A0091; Wed, 12 Feb 2014 17:08:11 -0800 (PST)
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 1WDkme-0005BV-60; Thu, 13 Feb 2014 01:08:08 +0000
Date: Thu, 13 Feb 2014 10:08:06 +0900
Message-ID: <m2ob2brf9l.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: [sidr] Last Call: <draft-ietf-sidr-policy-qualifiers-01.txt> (Policy Qualifiers in RPKI Certificates) to Proposed Standard
In-Reply-To: <CAMm+LwgMHVPK3aAp5SCQFFXqKJyhsOFpFk_hwpmShv4YTCzj3Q@mail.gmail.com>
References: <20140211131635.4764.88322.idtracker@ietfa.amsl.com> <6C3F924B-EDFF-42BC-9075-D4930636E643@vigilsec.com> <m2ha85tff2.wl%randy@psg.com> <CAMm+LwgMHVPK3aAp5SCQFFXqKJyhsOFpFk_hwpmShv4YTCzj3Q@mail.gmail.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
Cc: IETF Discussion Mailing List <ietf@ietf.org>, IETF SIDR <sidr@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Feb 2014 01:08:12 -0000

>>> Implementers do not do anything with a CPS pointer in a policy
>>> qualifier.  So, this addition will not impact interoperability.
>> in other words it has no operational use
> It has a legal significance.

rhetorical question: in what juristiction(s)?

from 2804

   - The IETF, an international standards body, believes itself to be
     the wrong forum for designing protocol or equipment features that
     address needs arising from the laws of individual countries,
     because these laws vary widely across the areas that IETF standards
     are deployed in.  Bodies whose scope of authority correspond to a
     single regime of jurisdiction are more appropriate for this task.

this song has been repeated.

randy


From daedulus@btconnect.com  Thu Feb 13 01:11:41 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 791711A00EB for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 01:11:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.702
X-Spam-Level: 
X-Spam-Status: No, score=-0.702 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 lSwu7tGqjTXR for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 01:11:36 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0012.outbound.protection.outlook.com [213.199.154.12]) by ietfa.amsl.com (Postfix) with ESMTP id 954CE1A01AC for <ietf@ietf.org>; Thu, 13 Feb 2014 01:11:32 -0800 (PST)
Received: from DBXPRD0210HT003.eurprd02.prod.outlook.com (157.56.253.181) by DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153) with Microsoft SMTP Server (TLS) id 15.0.878.16; Thu, 13 Feb 2014 09:11:30 +0000
Message-ID: <001801cf289a$eb69fc60$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Margaret Wasserman <margaretw42@gmail.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>, <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com>
Subject: Re: calls for discussion
Date: Thu, 13 Feb 2014 09:06:25 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
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.253.181]
X-ClientProxiedBy: DB3PR07CA007.eurprd07.prod.outlook.com (10.242.134.47) To DB4PR07MB252.eurprd07.prod.outlook.com (10.242.231.153)
X-Forefront-PRVS: 0121F24F22
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009001)(6009001)(189002)(199002)(377454003)(13464003)(24454002)(85306002)(47446002)(69226001)(74662001)(74502001)(4396001)(77096001)(77156001)(31966008)(76796001)(50986001)(44736004)(87286001)(87266001)(76786001)(50226001)(47976001)(49866001)(47736001)(63696002)(47776003)(83322001)(19580395003)(19580405001)(80976001)(74706001)(23746002)(50466002)(14496001)(56776001)(54316002)(53806001)(51856001)(46102001)(77982001)(59766001)(95416001)(74366001)(84392001)(42186004)(95666001)(76482001)(1411001)(74876001)(94316002)(87976001)(81542001)(62966002)(61296002)(92566001)(56816005)(89996001)(90146001)(88136002)(81342001)(86362001)(66066001)(93916002)(80022001)(65816001)(62236002)(44716002)(79102001)(93516002)(93136001)(94946001)(33646001)(92726001)(83072002)(85852003)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB4PR07MB252; H:DBXPRD0210HT003.eurprd02.prod.outlook.com; CLIP:157.56.253.181; FPR:AC94F75D.B6F257DA.B1F19D4B.48E1F2F1.20334; PTR:InfoNoRecords; MX:1; A:0; LANG:en; 
X-OriginatorOrg: btconnect.com
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, 13 Feb 2014 09:11:41 -0000

----- Original Message -----
From: "Margaret Wasserman" <margaretw42@gmail.com>
To: <l.wood@surrey.ac.uk>
Cc: <ietf@ietf.org>
Sent: Wednesday, February 12, 2014 12:32 PM
On Feb 12, 2014, at 6:26 AM, <l.wood@surrey.ac.uk> wrote:

> Starting an idea in the meeting privileges only those who are in the
room.

It is more complicated than that…

<snip>

There are some IETF WGs that operate differently.   They do their work
on the mailing lists and  have "interim" meetings or telechats as needed
that are organized on their WG mailing list.  Some of them don't even
meet at IETF meetings, because they see no value in presenting their
work-in-progress to the masses.  It would have an unfortunate impact on
our revenue stream if more groups started operating that way, as our
main sources of income are tied to attendance at plenary meetings, but
maybe more groups should try this sort of thing, anyway?

Does anyone have any other ideas about how we can get back to a point
where most of our decisions are made by people who are active on the WG
mailing list and interested in the work of the group year-round?

<tp>
Margaret

You have answered your own question with the preceding paragraph.

Meeting at the IETF plenaries makes the work in the course of a year
tri-modal and very uneven.

Meeting at the IETF plenaries encourages people to 'PowerPoint' when the
approach that works best for the IETF is to write an I-D.

Meeting at an IETF plenary makes people leave it to the day, instead of
getting on with it by e-mail.

The logic is impeccable - do not meet at an IETF plenary and the work
will progress better and faster.  If something comes up that needs
discussion, then do not wait for the next IETF plenary - hold an Interim
Virtual as soon as possible and get back to progress.

We are engineers and can see the logic of this - it is up to the
financiers to address any financial consequences. (And to the
psychologists if the meetings fulfil the need for a jolly:-(.

Tom Petch

Margaret










From abdussalambaryun@gmail.com  Thu Feb 13 04:07:18 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 064351A0212 for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 04:07:18 -0800 (PST)
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 U4wcFg4740ZN for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 04:07:15 -0800 (PST)
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 D590A1A0210 for <ietf@ietf.org>; Thu, 13 Feb 2014 04:07:14 -0800 (PST)
Received: by mail-yh0-f54.google.com with SMTP id z6so9857601yhz.41 for <ietf@ietf.org>; Thu, 13 Feb 2014 04:07:13 -0800 (PST)
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; bh=y89mT9ALEr3715ws5E5fCZPVoyKv2DBSSP6Jfx+2rTc=; b=lxKDh4sA1nW5eiYVoEWHIc5I8FVZErGuDRtnMd1bDyvKz03y/FvthlUVdBqWpZevM7 MV3d+29BkQuSiJR8B4WF8idixVfwGOip1vz6NUa8C3RTxh8HRw5EMCa1/FJ1yzbvdvav NXjtj/Tf/iUeLjLEzFwk382GVTwVNxewIZEGCvBc4icTJ8mEYAi8be/Ox/a02xci2Hbu /6wYsFlPjnNLXIzxgX5x+YP43CYmZlezchWQuornIztyM4D7HayCWn4FUzGhvoD3mI6L C78//SEGt1eWimXl6WYD1ataLtyROZtCkxZVk4Xr2U/tIbyKJW84wS+NhVYbfBZ9Mghs N7QA==
MIME-Version: 1.0
X-Received: by 10.236.5.174 with SMTP id 34mr985998yhl.48.1392293233729; Thu, 13 Feb 2014 04:07:13 -0800 (PST)
Received: by 10.170.222.3 with HTTP; Thu, 13 Feb 2014 04:07:13 -0800 (PST)
In-Reply-To: <52FB91B0.5090508@dcrocker.net>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CAKHUCzxBcvS8XZoo5yrM1kif4+hWRR9hTYQ0=9xg==HVQjU1Rg@mail.gmail.com> <52FB91B0.5090508@dcrocker.net>
Date: Thu, 13 Feb 2014 13:07:13 +0100
Message-ID: <CADnDZ892fzUPcUc25nua6beMDF4RYh2j=WZEjeY_EnDuxawtGA@mail.gmail.com>
Subject: Re: calls for discussion
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Feb 2014 12:07:18 -0000

On 2/12/14, Dave Crocker <dhc@dcrocker.net> wrote:
> So,
>
>       If we want meeting time to be used better, we need to get people
>       to change their model and to seriously do the major group work
>       /between/ meetings and /on the mailing list/.
>
> That has its challenges, but the challenges are not an excuse for giving
> up on mailing lists or calling such folk lazy or illiterate.
>

The other important issue, is not only the WG times but also active
participants, it is important that WGs try to use/involve more
participants (diversity in participation) into work items, the more
cooperative heads/practices into a work makes it better and will
produce best discussions.

The call for discussions within the WG charter, can be amended to call
for Group/WG participation, efficiency, and cooperation.

AB


From nobody Thu Feb 13 10:41: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 CB9341A03BC for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 10:41:16 -0800 (PST)
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 SNugyo180wAb for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 10:41:11 -0800 (PST)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 51F1D1A03AB for <ietf@ietf.org>; Thu, 13 Feb 2014 10:41:11 -0800 (PST)
Received: by mail-pd0-f178.google.com with SMTP id fp1so2167901pdb.37 for <ietf@ietf.org>; Thu, 13 Feb 2014 10:41:10 -0800 (PST)
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=utSHdlT1SeC3RjZLGKPI9OnKxdcyw4CwU0YxafS77AQ=; b=gyQxFm3r0O36RXvt8wzxusLNyudf/UEkQ604rh8IauJqgpj29yKOvUqSZyZ5/can05 H6OT73Fr2Jzi3quEN0U8RJqZjEDVUFlyxla/ZwB0mxULujNF9reivr9k/IOlJIY21840 cQL2ZYwLehurtHp+E2BtJxtJVNSH51HTARisJTDE2sRbvilu9+qh4eJCvL0DWzxDZ2l4 4d2xKqn6FP7Js3HqsM3cPk0iyEWRNh91gCoi5+RD95t51wQd71jo61dKCc5ObkwRb8sY /ds0B83o+7YrmZCVtxnzuuSUsTHlJs/2l9P6BbFQT2OBnF4q2EZukFaq0BiNsT5TYqzg bUQQ==
X-Received: by 10.68.114.163 with SMTP id jh3mr3345329pbb.99.1392316870162; Thu, 13 Feb 2014 10:41:10 -0800 (PST)
Received: from [192.168.1.115] (222-154-169-111.jetstream.xtra.co.nz. [222.154.169.111]) by mx.google.com with ESMTPSA id qs1sm8971063pbb.18.2014.02.13.10.41.07 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 13 Feb 2014 10:41:09 -0800 (PST)
Message-ID: <52FD11C7.9020900@gmail.com>
Date: Fri, 14 Feb 2014 07:41:11 +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: "t.p." <daedulus@btconnect.com>
Subject: Re: calls for discussion
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com>, <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com> <001801cf289a$eb69fc60$4001a8c0@gateway.2wire.net>
In-Reply-To: <001801cf289a$eb69fc60$4001a8c0@gateway.2wire.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/STgTkGkYyTifZHrLboqo4xSd-9s
Cc: Margaret Wasserman <margaretw42@gmail.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, 13 Feb 2014 18:41:17 -0000

> Some of them don't even
> meet at IETF meetings, because they see no value in presenting their
> work-in-progress to the masses. 

Some of us believe that is an arrogant approach that leads to
work coming out of a WG that has not been exposed to IETF-wide
review soon enough, and is therefore at risk of either having
a very hard time during Last Call and IESG review, or of ending
up as a minority solution at best.

It's a fact that humans are driven by deadlines, which is one
reason why interim meetings add value, and there are some topics
that can indeed succeed without meeting at IETF weeks, but for
most topics, IMHO we really need the exposure to the IETF masses.

    Brian


From nobody Thu Feb 13 11:35:56 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B5041A0405 for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 11:35:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKOXraDcvmNq for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 11:35:50 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0B01A03FA for <ietf@ietf.org>; Thu, 13 Feb 2014 11:35:50 -0800 (PST)
Received: from mb-aye.local (pat-WFK.asa1.sv1.corp.equinix.com [216.221.228.7] (may be forged)) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s1DJZmx3010750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Thu, 13 Feb 2014 19:35:49 GMT (envelope-from joelja@bogus.com)
Message-ID: <52FD1E8E.2030609@bogus.com>
Date: Thu, 13 Feb 2014 11:35:42 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com>
In-Reply-To: <20140121123308.17385.36578.idtracker@ietfa.amsl.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="rr621qOmLS5hbj3qbl6tf1W0jT7Mr9jfw"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Thu, 13 Feb 2014 19:35:49 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WGf4tAkstztF_GpVM6qoh3FVa7M
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Feb 2014 19:35:53 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--rr621qOmLS5hbj3qbl6tf1W0jT7Mr9jfw
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

A new version of this document has been released.

this addresses comments recieved during last call.

the diff1 is here

http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-yourtchenk=
o-cisco-ies-10.txt

On 1/21/14, 4:33 AM, The IESG wrote:
>=20
> The IESG has received a request from an individual submitter to conside=
r
> the following document:
> - 'Cisco Specific Information Elements reused in IPFIX'
>   <draft-yourtchenko-cisco-ies-09.txt> as Informational RFC
>=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-02-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 some additional Information Elements of Cisc=
o
>    Systems, Inc. that are not listed in RFC3954.
>=20
>=20
>=20
>=20
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>=20
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20



--rr621qOmLS5hbj3qbl6tf1W0jT7Mr9jfw
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 Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlL9Ho8ACgkQ8AA1q7Z/VrKL2ACfR9dEJi2eVcskCnHR92tBR2To
DMYAoIQwglHjPDNmtPAfx2AN5t8gxNO0
=0GGa
-----END PGP SIGNATURE-----

--rr621qOmLS5hbj3qbl6tf1W0jT7Mr9jfw--


From nobody Thu Feb 13 14:57:00 2014
Return-Path: <nomcom-chair-2013@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 BA5101A0310; Thu, 13 Feb 2014 14:56:59 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMFBt841_tmy; Thu, 13 Feb 2014 14:56:58 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AFF41A0021; Thu, 13 Feb 2014 14:56:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: NomCom Chair 2013 <nomcom-chair-2013@ietf.org>
To: IETF Announcement List <ietf-announce@ietf.org>
Subject: NOMCOM - IAB Slate
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.0.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140213225658.16948.67536.idtracker@ietfa.amsl.com>
Date: Thu, 13 Feb 2014 14:56:58 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/k-kkBkBsO8oWdOMYuqYH2GoDDJs
Cc: IETF Discussion List <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: Nomcom Chair 2013 <nomcom-chair-2013@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, 13 Feb 2014 22:57:00 -0000

The 2013-14 IETF Nomcom is pleased to announce its selection of the
IAB slate whose terms start at IETF 89 in March 2014.

The Nomcom has selected the following people to serve on the IAB,
and they have been confirmed by the ISOC Board of Trustees in its
role as confirming body:
   Mary Barnes
   Marc Blanchet (incumbent)
   Ted Hardie
   Joe Hildebrand
   Eliot Lear (incumbent, 1 year term)
   Brian Trammell   

Thanks to all of these individuals for agreeing to serve the community!

The Nomcom wishes to be the first to thank the incumbents who are
not returning, for their years of serving the community on the IAB: 
   Bernard Aboba
   Ross Callon
   Hannes Tschofenig
   
The Nomcom also thanks Alissa Cooper for her service on the IAB; as of
March 2014, she will resign her IAB position in order to take up an IESG
position, as previously announced.  The appointment of Eliot Lear to his second
1 year term fills the vacant position that will be left by Alissa.

The Nomcom sincerely thanks the awe-inspiring members of the community 
who accepted nominations.   

For your reference, the 2014-2015 IAB full listing is:
    Jari Arkko (IETF Chair)
    Mary Barnes
    Marc Blanchet
    Joel Halpern
    Ted Hardie
    Joe Hildebrand
    Russ Housley
    Eliot Lear
    Xing Li
    Erik Nordmark
    Andrew Sullivan
    Dave Thaler
    Brian Trammell

Finally, since this is the last announcement to be made, the Nomcom 
wishes great terms of service to all the individuals who have agreed to serve
this year.

With best regards,

Allison Mankin
Nomcom Chair 2013-14
For the Nomcom


From nobody Thu Feb 13 15:11:17 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 74B171A04F4; Thu, 13 Feb 2014 15:11:15 -0800 (PST)
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 DE6Qd9JrUFAR; Thu, 13 Feb 2014 15:11:13 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 6A30B1A04F3; Thu, 13 Feb 2014 15:11:13 -0800 (PST)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1DNB9T3016178 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 13 Feb 2014 15:11:12 -0800
Message-ID: <52FD50E1.7010106@dcrocker.net>
Date: Thu, 13 Feb 2014 15:10:25 -0800
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.3.0
MIME-Version: 1.0
To: ietf@ietf.org, Nomcom Chair 2013 <nomcom-chair-2013@ietf.org>
Subject: Re: NOMCOM - IAB Slate
References: <20140213225658.16948.67536.idtracker@ietfa.amsl.com>
In-Reply-To: <20140213225658.16948.67536.idtracker@ietfa.amsl.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, 13 Feb 2014 15:11:12 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DA4aWtdmVK3msCvUZcwDUT4no3w
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, 13 Feb 2014 23:11:15 -0000

On 2/13/2014 2:56 PM, NomCom Chair 2013 wrote:
> The Nomcom has selected the following people to serve on the IAB,
> and they have been confirmed by the ISOC Board of Trustees in its
> role as confirming body:
>     Mary Barnes


congrats!

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Thu Feb 13 21:53: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 9248A1A00F7 for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 21:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.253
X-Spam-Level: 
X-Spam-Status: No, score=-3.253 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, TO_IN_SUBJ=2.796] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FUAGpmIXkAqi for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 21:53:08 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 26A201A00F4 for <ietf@ietf.org>; Thu, 13 Feb 2014 21:53:08 -0800 (PST)
Received: from /spool/local by e32.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, 13 Feb 2014 22:53:06 -0700
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 13 Feb 2014 22:53:04 -0700
Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id A3D673E4003E for <ietf@ietf.org>; Thu, 13 Feb 2014 22:53:03 -0700 (MST)
Received: from d03av05.boulder.ibm.com (d03av05.boulder.ibm.com [9.17.195.85]) by b03cxnp08025.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1E5r3Wm8847640 for <ietf@ietf.org>; Fri, 14 Feb 2014 06:53:03 +0100
Received: from d03av05.boulder.ibm.com (localhost [127.0.0.1]) by d03av05.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s1E5r35U020063 for <ietf@ietf.org>; Thu, 13 Feb 2014 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av05.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s1E5r2LR020055 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 13 Feb 2014 22:53:03 -0700
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 s1E5r2hO026222 for <ietf@ietf.org>; Fri, 14 Feb 2014 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s1E5r1e5026174 for ietf@ietf.org; Fri, 14 Feb 2014 00:53:01 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201402140553.s1E5r1e5026174@rotala.raleigh.ibm.com>
Date: Fri, 14 Feb 2014 00:53:01 -0500
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: 14021405-0928-0000-0000-0000069EA102
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/xpoAzjw1QmR6oj_LMkuf321ccjI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Feb 2014 05:53:10 -0000

Total of 84 messages in the last 7 days.
 
script run at: Fri Feb 14 00:53:01 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.33% |    7 |  6.91% |    44889 | dhc@dcrocker.net
  5.95% |    5 |  4.09% |    26584 | randy@psg.com
  4.76% |    4 |  4.62% |    30037 | l.wood@surrey.ac.uk
  4.76% |    4 |  4.36% |    28356 | john-ietf@jck.com
  3.57% |    3 |  3.90% |    25335 | hallam@gmail.com
  3.57% |    3 |  3.66% |    23785 | sob@sobco.com
  2.38% |    2 |  4.28% |    27791 | ggm@algebras.org
  2.38% |    2 |  4.21% |    27329 | cntreras@gmail.com
  3.57% |    3 |  2.77% |    18006 | scott.brim@gmail.com
  3.57% |    3 |  2.75% |    17857 | abdussalambaryun@gmail.com
  2.38% |    2 |  3.52% |    22861 | mariainesrobles@googlemail.com
  2.38% |    2 |  3.24% |    21074 | dave@cridland.net
  2.38% |    2 |  2.80% |    18205 | housley@vigilsec.com
  2.38% |    2 |  2.65% |    17244 | christer.holmberg@ericsson.com
  2.38% |    2 |  2.63% |    17071 | rpelletier@isoc.org
  2.38% |    2 |  2.47% |    16062 | loa@pi.nu
  2.38% |    2 |  2.28% |    14819 | sm+ietf@elandsys.com
  2.38% |    2 |  2.13% |    13829 | brian.e.carpenter@gmail.com
  2.38% |    2 |  2.06% |    13361 | lars@netapp.com
  2.38% |    2 |  1.94% |    12613 | melinda.shore@gmail.com
  2.38% |    2 |  1.91% |    12382 | jari.arkko@piuha.net
  2.38% |    2 |  1.85% |    12012 | johnl@taugh.com
  2.38% |    2 |  1.74% |    11335 | chair@ietf.org
  1.19% |    1 |  2.43% |    15768 | kerlyn@ieee.org
  1.19% |    1 |  2.00% |    13011 | hansensmart@gmail.com
  1.19% |    1 |  1.95% |    12700 | chelliot@pobox.com
  1.19% |    1 |  1.80% |    11716 | rlb@ipv.sx
  1.19% |    1 |  1.59% |    10322 | narten@us.ibm.com
  1.19% |    1 |  1.45% |     9413 | margaretw42@gmail.com
  1.19% |    1 |  1.39% |     9019 | farmer@umn.edu
  1.19% |    1 |  1.35% |     8792 | sandy@weijax.net
  1.19% |    1 |  1.25% |     8111 | daedulus@btconnect.com
  1.19% |    1 |  1.11% |     7224 | alexandru.petrescu@gmail.com
  1.19% |    1 |  1.09% |     7089 | joelja@bogus.com
  1.19% |    1 |  1.05% |     6844 | ted.lemon@nominum.com
  1.19% |    1 |  1.04% |     6770 | presnick@qti.qualcomm.com
  1.19% |    1 |  0.95% |     6157 | spencerdawkins.ietf@gmail.com
  1.19% |    1 |  0.93% |     6022 | sra@hactrn.net
  1.19% |    1 |  0.90% |     5872 | paul@nohats.ca
  1.19% |    1 |  0.90% |     5822 | nomcom-chair-2013@ietf.org
  1.19% |    1 |  0.86% |     5599 | yangkun2005@gmail.com
  1.19% |    1 |  0.86% |     5572 | paul.hoffman@vpnc.org
  1.19% |    1 |  0.83% |     5376 | iad@ietf.org
  1.19% |    1 |  0.80% |     5183 | mnot@mnot.net
  1.19% |    1 |  0.71% |     4642 | agenda@ietf.org
--------+------+--------+----------+------------------------
100.00% |   84 |100.00% |   649861 | Total


From nobody Fri Feb 14 04:27:46 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 8B2101A0234 for <ietf@ietfa.amsl.com>; Fri, 14 Feb 2014 04:27:43 -0800 (PST)
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, 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 W7HgLSCOf_Zb for <ietf@ietfa.amsl.com>; Fri, 14 Feb 2014 04:27:41 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) by ietfa.amsl.com (Postfix) with ESMTP id A4D641A0228 for <ietf@ietf.org>; Fri, 14 Feb 2014 04:27:40 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1ECRalL004377; Fri, 14 Feb 2014 12:27:36 GMT
Received: from 950129200 (15.21.90.92.rev.sfr.net [92.90.21.15]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1ECRYHc004369 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 14 Feb 2014 12:27:35 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Andrew Yourtchenko'" <ayourtch@cisco.com>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com> <52E77C81.8020803@cisco.com> <050801cf1c6c$0e7fdca0$2b7f95e0$@olddog.co.uk> <alpine.OSX.2.00.1402132103300.73875@ayourtch-mac>
In-Reply-To: <alpine.OSX.2.00.1402132103300.73875@ayourtch-mac>
Subject: RE: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Date: Fri, 14 Feb 2014 12:27:33 -0000
Message-ID: <012f01cf2980$23b179a0$6b146ce0$@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: AQFerF+1MVKpbR9CNhjCMYsURGW24gGF8EmEAuvAeakCKvVZ3wE+B9hsAuBRlUmbP88w0A==
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Xvz2CrTBynMjNFSOL4zcyVMEI-k
Cc: 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: Fri, 14 Feb 2014 12:27:43 -0000

Hi Andrew,

Thanks for the work.

The changes together with the email discussion have clarified the =
situation with
regard to my question.

Cheers,
Adrian

> -----Original Message-----
> From: Andrew Yourtchenko [mailto:ayourtch@cisco.com]
> Sent: 13 February 2014 20:05
> To: Adrian Farrel
> Cc: 'Benoit Claise'; ietf@ietf.org
> Subject: RE: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco =
Specific
> Information Elements reused in IPFIX) to Informational RFC
>=20
> Hello Adrian,
>=20
> I've uploaded today the
> http://tools.ietf.org/html/draft-yourtchenko-cisco-ies-10 that =
hopefully
> took into account the review by changing the text of the Abstract and
> Introduction.
>=20
> Please take a look for the new revision, and let us know what you =
think.
>=20
> Many thanks!
>=20
> --a
>=20
> On Tue, 28 Jan 2014, Adrian Farrel wrote:
>=20
> >
> > Thanks Benoit, that is an important point and is really helpful.
> >
> >
> >
> > So, do I read you right if I say that this document records some =
NetFlow v9
> features and codepoints that were
> > accidentally missed when RFC 3954 was written.
> >
> >
> >
> > Or are these later modifications to NetFlow v9 (let's call it v9.x) =
that use
the
> same code point range but were not
> > actually part of v9?
> >
> >
> >
> > The question might arise as to whether this document is supposed to =
update
> 3954.
> >
> >
> >
> > Thanks,
> >
> > Adrian
> >
> >
> >
> > From: Benoit Claise [mailto:bclaise@cisco.com]
> > Sent: 28 January 2014 09:47
> > To: adrian@olddog.co.uk; ietf@ietf.org; Andrew Yourtchenko
> > Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco =
Specific
> Information Elements reused in IPFIX) to
> > Informational RFC
> >
> >
> >
> > Let me reply to myself: I forgot an important point, which might be =
useful
if
> people start discussing AD sponsoring of
> > this document, without actually having read it.
> >
> > Let me stress the first sentence of the Introduction section.
> >
> > =A0=A0 The section 4 of [RFC7012] defines the IPFIX Information =
Elements in
> >
> > =A0=A0 the range of 1-127 to be compatible with the NetFlow version =
9
> >
> > =A0=A0 fields, as specified in the "Cisco Systems NetFlow Services =
Export
> >
> > =A0=A0 Version 9" [RFC3954].
> >
> > So this draft is clearly linked to the work in IPFIX RFC 7012 (IPFIX
information
> model) and must follow the RFC 7013
> > rules (Guidelines for Authors and Reviewers of IPFIX Information =
Elements),
> therefore would benefit from more reviews.
> >
> > It's probably not too clear from the abstract, and should be =
improved.
> >
> > OLD:
> >
> > =A0=A0 This document describes some additional Information Elements =
of Cisco
> >
> > =A0=A0 Systems, Inc. that are not listed in RFC3954
> >
> >
> >
> > NEW:
> >
> > =A0=A0 This document describes some additional IPFIX Information =
Elements in
> >
> > =A0=A0=A0the range of 1-127, which is the range compatible with =
field types used
> >
> > =A0=A0=A0by NetFlow version 9 in RFC3954, as specified in the IPFIX =
Information
Model
> >
> > =A0=A0 RFC 7012.
> >
> >
> >
> > Regards, Benoit (an as author)
> >
> >
> >
> >       Adrian,
> >
> >       Not an answer to the process question, but some background =
information
> on this draft.
> >       This draft, which is now 3 years old, has been evolving with =
the IPFIX
> standardization.
> >       For example, looking at
http://tools.ietf.org/rfcdiff?url2=3Ddraft-yourtchenko-
> cisco-ies-09.txt, you can see
> >       the interaction with the IPFIX WG document =
ietf-ipfix-data-link-layer-
> monitoring: now that
> >       ietf-ipfix-data-link-layer-monitoring is in the RFC editor =
queue, the
draft has
> been simplified, and some
> >       IPFIX Information Elements in the range 1-127 became =
deprecated.
> >       This explains why the draft has been presented and reviewed =
multiple
times
> in the IPFIX WG, and also why it
> >       would benefit from a wider review than the independent stream.
> >
> >       Regards, Benoit (as draft author)
> >
> >
> >
> >       Hi,
> >
> >       I have a process question on this last call which is not clear =
from
the last
> >       call text.
> >
> >       Are we being asked to consider whether publication of this =
document is
> useful,
> >       or are we being asked for IETF consensus on the *content* of =
the
> document?
> >
> >       It seems from the document that the content is descriptive of
something
> >       implemented by a single vendor. I applaud putting that =
information
into the
> >       public domain, but I don't understand the meaning of IETF =
consensus
with
> respect
> >       to this document.
> >
> >       Thanks,
> >       Adrian
> >
> >
> >       -----Original Message-----
> >       From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On =
Behalf
> Of The
> >       IESG
> >       Sent: 21 January 2014 12:33
> >       To: IETF-Announce
> >       Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> =
(Cisco
Specific
> >       Information Elements reused in IPFIX) to Informational RFC
> >
> >
> >       The IESG has received a request from an individual submitter =
to
consider
> >       the following document:
> >       - 'Cisco Specific Information Elements reused in IPFIX'
> >       =A0=A0 <draft-yourtchenko-cisco-ies-09.txt> as Informational =
RFC
> >
> >       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-02-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
> >
> >
> >       =A0=A0=A0 This document describes some additional Information =
Elements of
Cisco
> >       =A0=A0=A0 Systems, Inc. that are not listed in RFC3954.
> >
> >
> >
> >
> >       The file can be obtained via
> >       http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
> >
> >       IESG discussion can be tracked via
> >       =
http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
> >
> >
> >       No IPR declarations have been submitted directly on this I-D.
> >
> >
> >       .
> >
> >
> >       .
> >
> >
> >
> >
> >


From nobody Fri Feb 14 09:12:40 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 C5ABE1A0318 for <ietf@ietfa.amsl.com>; Fri, 14 Feb 2014 09:12:35 -0800 (PST)
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 1O6-rQskqPtE for <ietf@ietfa.amsl.com>; Fri, 14 Feb 2014 09:12:33 -0800 (PST)
Received: from mail-yh0-x232.google.com (mail-yh0-x232.google.com [IPv6:2607:f8b0:4002:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id E9FD31A0305 for <ietf@ietf.org>; Fri, 14 Feb 2014 09:12:30 -0800 (PST)
Received: by mail-yh0-f50.google.com with SMTP id 29so12017856yhl.9 for <ietf@ietf.org>; Fri, 14 Feb 2014 09:12:29 -0800 (PST)
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=8TILNwtWn9oq4OpOZ6l3fQsxlcijjDJxhhMqeCFu8O4=; b=rQm4KchS1tMsegMmswidowiUVh59L6qNtNTMldkVfM2AQXq49yrI+LvPxWKFtONoJy 9+MAuToylbIWUzxunGm1amYS1mIO+4PtbWoPng3R2vXnbokzRuzDXw9Wzin5bYwdLf68 90Gx1BGQjMmF0lnqGf6BTm5p0aOz0y6g2t0k6TPxscdb61pHtzP6HHj9mr6p67bZYhhT ceOlmSV9l4Fkf/6NTse7cqVaaDcfVZa4pODcEnKGHxsL/hQ2/SXQyO/5k28dBJP7Raw3 X/QXGGaLC0E82D6Ip0AURtUd74jLmQv7cdc04fh+hz4OTy0h2GXYYQNQSaRV/uu60vYs JgtQ==
MIME-Version: 1.0
X-Received: by 10.236.15.102 with SMTP id e66mr2417321yhe.69.1392397949300; Fri, 14 Feb 2014 09:12:29 -0800 (PST)
Received: by 10.170.222.3 with HTTP; Fri, 14 Feb 2014 09:12:29 -0800 (PST)
In-Reply-To: <52FD1E8E.2030609@bogus.com>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <52FD1E8E.2030609@bogus.com>
Date: Fri, 14 Feb 2014 17:12:29 +0000
Message-ID: <CADnDZ89Pis583kJo9mfdXeoByWNGpQ6+ZvbFp1GvCSvoiCPTqg@mail.gmail.com>
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: joel jaeggli <joelja@bogus.com>
Content-Type: multipart/alternative; boundary=089e0122a3d427775504f260e953
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GfovjR4Q7CHfl87l_XZLdDSrxBU
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, 14 Feb 2014 17:12:36 -0000

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

I think the draft should say on top that it updates RFC7012, as it mentions
that the draft extends the information model in 7012. Otherwise please
explain why not?

AB

On Thursday, February 13, 2014, joel jaeggli wrote:

> A new version of this document has been released.
>
> this addresses comments recieved during last call.
>
> the diff1 is here
>
>
> http://tools.ietf.org/rfcdiff?difftype=--hwdiff&url2=draft-yourtchenko-cisco-ies-10.txt
>
> On 1/21/14, 4:33 AM, The IESG wrote:
> >
> > The IESG has received a request from an individual submitter to consider
> > the following document:
> > - 'Cisco Specific Information Elements reused in IPFIX'
> >   <draft-yourtchenko-cisco-ies-09.txt> as Informational RFC
> >
> > 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 <javascript:;> mailing lists by 2014-02-18.
> Exceptionally, comments may be
> > sent to iesg@ietf.org <javascript:;> instead. In either case, please
> retain the
> > beginning of the Subject line to allow automated sorting.
> >
> > Abstract
> >
> >
> >    This document describes some additional Information Elements of Cisco
> >    Systems, Inc. that are not listed in RFC3954.
> >
> >
> >
> >
> > The file can be obtained via
> > http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
> >
> > IESG discussion can be tracked via
> > http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
> >
> >
> > No IPR declarations have been submitted directly on this I-D.
> >
> >
>
>
>

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

I think the draft should say on top=A0that it updates RFC7012, as it mentio=
ns that the draft extends the information model in 7012. Otherwise please e=
xplain why not?<div><br></div><div>AB<br><br>On Thursday, February 13, 2014=
, joel jaeggli  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 version of this document has been rele=
ased.<br>
<br>
this addresses comments recieved during last call.<br>
<br>
the diff1 is here<br>
<br>
<a href=3D"http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&amp;url2=3Ddra=
ft-yourtchenko-cisco-ies-10.txt" target=3D"_blank">http://tools.ietf.org/rf=
cdiff?difftype=3D--hwdiff&amp;url2=3Ddraft-yourtchenko-cisco-ies-10.txt</a>=
<br>
<br>
On 1/21/14, 4:33 AM, The IESG wrote:<br>
&gt;<br>
&gt; The IESG has received a request from an individual submitter to consid=
er<br>
&gt; the following document:<br>
&gt; - &#39;Cisco Specific Information Elements reused in IPFIX&#39;<br>
&gt; =A0 &lt;draft-yourtchenko-cisco-ies-09.txt&gt; as Informational RFC<br=
>
&gt;<br>
&gt; The IESG plans to make a decision in the next few weeks, and solicits<=
br>
&gt; final comments on this action. Please send substantive comments to the=
<br>
&gt; <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, &#39;iet=
f@ietf.org&#39;)">ietf@ietf.org</a> mailing lists by 2014-02-18. Exceptiona=
lly, comments may be<br>
&gt; sent to <a href=3D"javascript:;" onclick=3D"_e(event, &#39;cvml&#39;, =
&#39;iesg@ietf.org&#39;)">iesg@ietf.org</a> instead. In either case, please=
 retain the<br>
&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;<br>
&gt; Abstract<br>
&gt;<br>
&gt;<br>
&gt; =A0 =A0This document describes some additional Information Elements of=
 Cisco<br>
&gt; =A0 =A0Systems, Inc. that are not listed in RFC3954.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The file can be obtained via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies=
/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-yourtchenko-cisc=
o-ies/</a><br>
&gt;<br>
&gt; IESG discussion can be tracked via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies=
/ballot/" target=3D"_blank">http://datatracker.ietf.org/doc/draft-yourtchen=
ko-cisco-ies/ballot/</a><br>
&gt;<br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;<br>
&gt;<br>
<br>
<br>
</blockquote></div>

--089e0122a3d427775504f260e953--


From nobody Fri Feb 14 10:05:29 2014
Return-Path: <ayourtch@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 B66CF1A043F for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 12:05:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.049
X-Spam-Level: 
X-Spam-Status: No, score=-15.049 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.548, 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 RgbnUME6BrZ3 for <ietf@ietfa.amsl.com>; Thu, 13 Feb 2014 12:05:36 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3201A0439 for <ietf@ietf.org>; Thu, 13 Feb 2014 12:05:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5699; q=dns/txt; s=iport; t=1392321935; x=1393531535; h=date:from:to:cc:subject:in-reply-to:message-id: references:mime-version; bh=R2H1F0BQ1d8gkxwIdg0mk4qMX2J3ABTsg5KoIEs23SM=; b=Mh/UDbzymrnzf7w8MwczTQQmFxms26yxCXUmw4c/LQ3X4J8uD9II+3Z+ q7WoFqG/cQzAZ5e4al73YrmN2CI+z2FsbZhV4ztYEVS0v+s2jfdpR+tq+ pHDb++aRn+dFOFP0IlzFONodTwXpuFaQ6ORmBxoismSz1+f6pPK5zhSBc E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnIKAIgk/VKtJV2a/2dsb2JhbABZgwg4VagJA5UFgRsWAXSDfQEBAQMBbgsMBAsRBAEBFg4EB0YJCAYOBYd8CA2/OBePEgcGBIQsBJlGhRWEFYc6gW2BP4Ip
X-IronPort-AV: E=Sophos;i="4.95,840,1384300800"; d="scan'208";a="300918942"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP; 13 Feb 2014 20:05:34 +0000
Received: from xhc-rcd-x13.cisco.com (xhc-rcd-x13.cisco.com [173.37.183.87]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1DK5YV0002016 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 13 Feb 2014 20:05:34 GMT
Received: from [10.61.163.205] (10.61.163.205) by xhc-rcd-x13.cisco.com (173.37.183.87) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 13 Feb 2014 14:05:34 -0600
Date: Thu, 13 Feb 2014 21:05:14 +0100
From: Andrew Yourtchenko <ayourtch@cisco.com>
X-X-Sender: ayourtch@ayourtch-mac
To: Adrian Farrel <adrian@olddog.co.uk>
Subject: RE: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
In-Reply-To: <050801cf1c6c$0e7fdca0$2b7f95e0$@olddog.co.uk>
Message-ID: <alpine.OSX.2.00.1402132103300.73875@ayourtch-mac>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <029b01cf1a0b$707d5c60$51781520$@olddog.co.uk> <52E6F676.9020104@cisco.com> <52E77C81.8020803@cisco.com> <050801cf1c6c$0e7fdca0$2b7f95e0$@olddog.co.uk>
User-Agent: Alpine 2.00 (OSX 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="0-1407312425-1392321934=:73875"
X-Originating-IP: [10.61.163.205]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OVGCjXkKEWOSDlwKLoyHZky7pF0
X-Mailman-Approved-At: Fri, 14 Feb 2014 10:05:28 -0800
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, 13 Feb 2014 20:05:38 -0000

--0-1407312425-1392321934=:73875
Content-Type: text/plain; charset="ISO-8859-15"; format=flowed
Content-Transfer-Encoding: 8BIT

Hello Adrian,

I've uploaded today the 
http://tools.ietf.org/html/draft-yourtchenko-cisco-ies-10 that hopefully 
took into account the review by changing the text of the Abstract and 
Introduction.

Please take a look for the new revision, and let us know what you think.

Many thanks!

--a

On Tue, 28 Jan 2014, Adrian Farrel wrote:

> 
> Thanks Benoit, that is an important point and is really helpful.
>
> 
> 
> So, do I read you right if I say that this document records some NetFlow v9 features and codepoints that were
> accidentally missed when RFC 3954 was written.
>
> 
> 
> Or are these later modifications to NetFlow v9 (let's call it v9.x) that use the same code point range but were not
> actually part of v9?
>
> 
> 
> The question might arise as to whether this document is supposed to update 3954.
>
> 
> 
> Thanks,
> 
> Adrian
>
> 
> 
> From: Benoit Claise [mailto:bclaise@cisco.com]
> Sent: 28 January 2014 09:47
> To: adrian@olddog.co.uk; ietf@ietf.org; Andrew Yourtchenko
> Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to
> Informational RFC
>
> 
> 
> Let me reply to myself: I forgot an important point, which might be useful if people start discussing AD sponsoring of
> this document, without actually having read it.
> 
> Let me stress the first sentence of the Introduction section.
>
>    The section 4 of [RFC7012] defines the IPFIX Information Elements in
>
>    the range of 1-127 to be compatible with the NetFlow version 9
>
>    fields, as specified in the "Cisco Systems NetFlow Services Export
>
>    Version 9" [RFC3954]. 
> 
> So this draft is clearly linked to the work in IPFIX RFC 7012 (IPFIX information model) and must follow the RFC 7013
> rules (Guidelines for Authors and Reviewers of IPFIX Information Elements), therefore would benefit from more reviews.
> 
> It's probably not too clear from the abstract, and should be improved.
> 
> OLD:
>
>    This document describes some additional Information Elements of Cisco
>
>    Systems, Inc. that are not listed in RFC3954
>
> 
> 
> NEW:
>
>    This document describes some additional IPFIX Information Elements in 
>
>    the range of 1-127, which is the range compatible with field types used 
>
>    by NetFlow version 9 in RFC3954, as specified in the IPFIX Information Model
>
>    RFC 7012.
>
> 
> 
> Regards, Benoit (an as author)
>
> 
>
>       Adrian,
>
>       Not an answer to the process question, but some background information on this draft.
>       This draft, which is now 3 years old, has been evolving with the IPFIX standardization.
>       For example, looking at http://tools.ietf.org/rfcdiff?url2=draft-yourtchenko-cisco-ies-09.txt, you can see
>       the interaction with the IPFIX WG document ietf-ipfix-data-link-layer-monitoring: now that
>       ietf-ipfix-data-link-layer-monitoring is in the RFC editor queue, the draft has been simplified, and some
>       IPFIX Information Elements in the range 1-127 became deprecated.
>       This explains why the draft has been presented and reviewed multiple times in the IPFIX WG, and also why it
>       would benefit from a wider review than the independent stream.
>
>       Regards, Benoit (as draft author)
> 
> 
>
>       Hi,
>
>       I have a process question on this last call which is not clear from the last
>       call text.
>
>       Are we being asked to consider whether publication of this document is useful,
>       or are we being asked for IETF consensus on the *content* of the document?
>
>       It seems from the document that the content is descriptive of something
>       implemented by a single vendor. I applaud putting that information into the
>       public domain, but I don't understand the meaning of IETF consensus with respect
>       to this document.
>
>       Thanks,
>       Adrian
> 
>
>       -----Original Message-----
>       From: IETF-Announce [mailto:ietf-announce-bounces@ietf.org] On Behalf Of The
>       IESG
>       Sent: 21 January 2014 12:33
>       To: IETF-Announce
>       Subject: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific
>       Information Elements reused in IPFIX) to Informational RFC
> 
>
>       The IESG has received a request from an individual submitter to consider
>       the following document:
>       - 'Cisco Specific Information Elements reused in IPFIX'
>          <draft-yourtchenko-cisco-ies-09.txt> as Informational RFC
>
>       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-02-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 some additional Information Elements of Cisco
>           Systems, Inc. that are not listed in RFC3954.
> 
> 
> 
>
>       The file can be obtained via
>       http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>
>       IESG discussion can be tracked via
>       http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
> 
>
>       No IPR declarations have been submitted directly on this I-D.
> 
>
>       .
> 
>
>       .
>
> 
> 
> 
>
--0-1407312425-1392321934=:73875--


From nobody Fri Feb 14 10:10:00 2014
Return-Path: <andrewf@plixer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 439521A0270 for <ietf@ietfa.amsl.com>; Fri, 14 Feb 2014 10:09:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xRQTURZbF3Gm for <ietf@ietfa.amsl.com>; Fri, 14 Feb 2014 10:09:55 -0800 (PST)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id 9C0FC1A0349 for <ietf@ietf.org>; Fri, 14 Feb 2014 10:09:55 -0800 (PST)
Received: from PLXRDC01.plxr.local ([::1]) by PLXRDC01.plxr.local ([::1]) with mapi id 14.03.0158.001; Fri, 14 Feb 2014 13:09:52 -0500
From: Andrew Feren <andrewf@plixer.com>
To: joel jaeggli <joelja@bogus.com>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Thread-Topic: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Thread-Index: AQHPKPLajCJ6QYXhpkCj8e3WrQNS4Jq1C2cD
Date: Fri, 14 Feb 2014 18:09:51 +0000
Message-ID: <8E7542283B89BB4DB672EB49CEE5AAB705404ADC@PLXRDC01.plxr.local>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com>, <52FD1E8E.2030609@bogus.com>
In-Reply-To: <52FD1E8E.2030609@bogus.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [24.91.78.244]
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/0lAOHhg5kVCcndNkw5DP5AH1Htg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Feb 2014 18:09:58 -0000

draft-yourtchenko-cisco-ies-10 addresses my earlier last call comments.=0A=
=0A=
-Andrew=0A=
________________________________________=0A=
From: ietf [ietf-bounces@ietf.org] on behalf of joel jaeggli [joelja@bogus.=
com]=0A=
Sent: Thursday, February 13, 2014 2:35 PM=0A=
To: ietf@ietf.org=0A=
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specifi=
c Information Elements reused in IPFIX) to Informational RFC=0A=
=0A=
A new version of this document has been released.=0A=
=0A=
this addresses comments recieved during last call.=0A=
=0A=
the diff1 is here=0A=
=0A=
http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-yourtchenko-=
cisco-ies-10.txt=0A=
=0A=
On 1/21/14, 4:33 AM, The IESG wrote:=0A=
>=0A=
> The IESG has received a request from an individual submitter to consider=
=0A=
> the following document:=0A=
> - 'Cisco Specific Information Elements reused in IPFIX'=0A=
>   <draft-yourtchenko-cisco-ies-09.txt> as Informational RFC=0A=
>=0A=
> The IESG plans to make a decision in the next few weeks, and solicits=0A=
> final comments on this action. Please send substantive comments to the=0A=
> ietf@ietf.org mailing lists by 2014-02-18. Exceptionally, comments may be=
=0A=
> sent to iesg@ietf.org instead. In either case, please retain the=0A=
> beginning of the Subject line to allow automated sorting.=0A=
>=0A=
> Abstract=0A=
>=0A=
>=0A=
>    This document describes some additional Information Elements of Cisco=
=0A=
>    Systems, Inc. that are not listed in RFC3954.=0A=
>=0A=
>=0A=
>=0A=
>=0A=
> The file can be obtained via=0A=
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/=0A=
>=0A=
> IESG discussion can be tracked via=0A=
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/=0A=
>=0A=
>=0A=
> No IPR declarations have been submitted directly on this I-D.=0A=
>=0A=
>=0A=
=0A=
=0A=


From nobody Fri Feb 14 10:31:46 2014
Return-Path: <andrewf@plixer.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 853E91A02AF for <ietf@ietfa.amsl.com>; Fri, 14 Feb 2014 10:31:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C8uWKDmpnHtD for <ietf@ietfa.amsl.com>; Fri, 14 Feb 2014 10:31:42 -0800 (PST)
Received: from mx1.plixer.com (mx1.plixer.com [64.140.243.154]) by ietfa.amsl.com (Postfix) with ESMTP id 9D56F1A0310 for <ietf@ietf.org>; Fri, 14 Feb 2014 10:31:41 -0800 (PST)
Received: from PLXRDC01.plxr.local ([::1]) by PLXRDC01.plxr.local ([::1]) with mapi id 14.03.0158.001; Fri, 14 Feb 2014 13:31:39 -0500
From: Andrew Feren <andrewf@plixer.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, joel jaeggli <joelja@bogus.com>
Subject: RE: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Thread-Topic: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specific Information Elements reused in IPFIX) to Informational RFC
Thread-Index: AQHPKPLajCJ6QYXhpkCj8e3WrQNS4Jq1Uc2A//+8Yus=
Date: Fri, 14 Feb 2014 18:31:38 +0000
Message-ID: <8E7542283B89BB4DB672EB49CEE5AAB705404B45@PLXRDC01.plxr.local>
References: <20140121123308.17385.36578.idtracker@ietfa.amsl.com> <52FD1E8E.2030609@bogus.com>, <CADnDZ89Pis583kJo9mfdXeoByWNGpQ6+ZvbFp1GvCSvoiCPTqg@mail.gmail.com>
In-Reply-To: <CADnDZ89Pis583kJo9mfdXeoByWNGpQ6+ZvbFp1GvCSvoiCPTqg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [24.91.78.244]
Content-Type: multipart/alternative; boundary="_000_8E7542283B89BB4DB672EB49CEE5AAB705404B45PLXRDC01plxrloc_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/b0deMQTMAtSLCbapzt5N2nzW8qE
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, 14 Feb 2014 18:31:44 -0000

--_000_8E7542283B89BB4DB672EB49CEE5AAB705404B45PLXRDC01plxrloc_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi Abdussalam,

This draft doesn't update RFC 7012 it extends the information model.  The d=
raft states this clearly and also mentions how the information model is ext=
ended.

"The IPFIX Protocol ([RFC7011]) has its own
   Information Model ([RFC7012], IANA [IPFIX-IANA]) which is extensible
   upon application to IANA, subject to expert review by IE-doctors
   ([RFC7013]).  This draft extends the IPFIX Information Model."

See also secion 6 "IANA Considerations" as well as RFC 7012 Section 6 "Exte=
nding the Information Model".

-Andrew

________________________________
From: ietf [ietf-bounces@ietf.org] on behalf of Abdussalam Baryun [abdussal=
ambaryun@gmail.com]
Sent: Friday, February 14, 2014 12:12 PM
To: joel jaeggli
Cc: ietf@ietf.org
Subject: Re: Last Call: <draft-yourtchenko-cisco-ies-09.txt> (Cisco Specifi=
c Information Elements reused in IPFIX) to Informational RFC

I think the draft should say on top that it updates RFC7012, as it mentions=
 that the draft extends the information model in 7012. Otherwise please exp=
lain why not?

AB

On Thursday, February 13, 2014, joel jaeggli wrote:
A new version of this document has been released.

this addresses comments recieved during last call.

the diff1 is here

http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&url2=3Ddraft-yourtchenko-=
cisco-ies-10.txt

On 1/21/14, 4:33 AM, The IESG wrote:
>
> The IESG has received a request from an individual submitter to consider
> the following document:
> - 'Cisco Specific Information Elements reused in IPFIX'
>   <draft-yourtchenko-cisco-ies-09.txt> as Informational RFC
>
> 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<UrlBlockedError.aspx> mailing lists by 2014-02-18. Exceptio=
nally, comments may be
> sent to iesg@ietf.org<UrlBlockedError.aspx> instead. In either case, plea=
se retain the
> beginning of the Subject line to allow automated sorting.
>
> Abstract
>
>
>    This document describes some additional Information Elements of Cisco
>    Systems, Inc. that are not listed in RFC3954.
>
>
>
>
> The file can be obtained via
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/
>
> IESG discussion can be tracked via
> http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>



--_000_8E7542283B89BB4DB672EB49CEE5AAB705404B45PLXRDC01plxrloc_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html dir=3D"ltr">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style id=3D"owaParaStyle" type=3D"text/css">P {margin-top:0;margin-bottom:=
0;}</style>
</head>
<body ocsi=3D"0" fpstyle=3D"1">
<div style=3D"direction: ltr;font-family: Tahoma;color: #000000;font-size: =
10pt;">Hi
<font color=3D"#000000" face=3D"Tahoma" size=3D"2">Abdussalam,<br>
<br>
This draft doesn't update RFC 7012 it extends the information model.&nbsp; =
The draft states this clearly and also mentions how the information model i=
s extended.<br>
<br>
&quot;The IPFIX Protocol ([RFC7011]) has its own<br>
&nbsp;&nbsp; Information Model ([RFC7012], IANA [IPFIX-IANA]) which is exte=
nsible<br>
&nbsp;&nbsp; upon application to IANA, subject to expert review by IE-docto=
rs<br>
&nbsp;&nbsp; ([RFC7013]).&nbsp; This draft extends the IPFIX Information Mo=
del.&quot;<br>
<br>
See also secion 6 &quot;IANA Considerations&quot; as well as RFC 7012 Secti=
on 6 &quot;Extending the Information Model&quot;.<br>
<br>
-Andrew<br>
<br>
</font>
<div style=3D"font-family: Times New Roman; color: #000000; font-size: 16px=
">
<hr tabindex=3D"-1">
<div style=3D"direction: ltr;" id=3D"divRpF731327"><font color=3D"#000000" =
face=3D"Tahoma" size=3D"2"><b>From:</b> ietf [ietf-bounces@ietf.org] on beh=
alf of Abdussalam Baryun [abdussalambaryun@gmail.com]<br>
<b>Sent:</b> Friday, February 14, 2014 12:12 PM<br>
<b>To:</b> joel jaeggli<br>
<b>Cc:</b> ietf@ietf.org<br>
<b>Subject:</b> Re: Last Call: &lt;draft-yourtchenko-cisco-ies-09.txt&gt; (=
Cisco Specific Information Elements reused in IPFIX) to Informational RFC<b=
r>
</font><br>
</div>
<div></div>
<div>I think the draft should say on top&nbsp;that it updates RFC7012, as i=
t mentions that the draft extends the information model in 7012. Otherwise =
please explain why not?
<div><br>
</div>
<div>AB<br>
<br>
On Thursday, February 13, 2014, joel jaeggli wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
A new version of this document has been released.<br>
<br>
this addresses comments recieved during last call.<br>
<br>
the diff1 is here<br>
<br>
<a href=3D"http://tools.ietf.org/rfcdiff?difftype=3D--hwdiff&amp;url2=3Ddra=
ft-yourtchenko-cisco-ies-10.txt" target=3D"_blank">http://tools.ietf.org/rf=
cdiff?difftype=3D--hwdiff&amp;url2=3Ddraft-yourtchenko-cisco-ies-10.txt</a>=
<br>
<br>
On 1/21/14, 4:33 AM, The IESG wrote:<br>
&gt;<br>
&gt; The IESG has received a request from an individual submitter to consid=
er<br>
&gt; the following document:<br>
&gt; - 'Cisco Specific Information Elements reused in IPFIX'<br>
&gt; &nbsp; &lt;draft-yourtchenko-cisco-ies-09.txt&gt; as Informational RFC=
<br>
&gt;<br>
&gt; The IESG plans to make a decision in the next few weeks, and solicits<=
br>
&gt; final comments on this action. Please send substantive comments to the=
<br>
&gt; <a href=3D"UrlBlockedError.aspx" target=3D"_blank">ietf@ietf.org</a> m=
ailing lists by 2014-02-18. Exceptionally, comments may be<br>
&gt; sent to <a href=3D"UrlBlockedError.aspx" target=3D"_blank">iesg@ietf.o=
rg</a> instead. In either case, please retain the<br>
&gt; beginning of the Subject line to allow automated sorting.<br>
&gt;<br>
&gt; Abstract<br>
&gt;<br>
&gt;<br>
&gt; &nbsp; &nbsp;This document describes some additional Information Eleme=
nts of Cisco<br>
&gt; &nbsp; &nbsp;Systems, Inc. that are not listed in RFC3954.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The file can be obtained via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies=
/" target=3D"_blank">
http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/</a><br>
&gt;<br>
&gt; IESG discussion can be tracked via<br>
&gt; <a href=3D"http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies=
/ballot/" target=3D"_blank">
http://datatracker.ietf.org/doc/draft-yourtchenko-cisco-ies/ballot/</a><br>
&gt;<br>
&gt;<br>
&gt; No IPR declarations have been submitted directly on this I-D.<br>
&gt;<br>
&gt;<br>
<br>
<br>
</blockquote>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_8E7542283B89BB4DB672EB49CEE5AAB705404B45PLXRDC01plxrloc_--


From nobody Fri Feb 14 14:00:47 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 698C51A041E; Fri, 14 Feb 2014 14:00:44 -0800 (PST)
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 5uuE7Do3Lymm; Fri, 14 Feb 2014 14:00:42 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id B8BB61A03EA; Fri, 14 Feb 2014 14:00:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 41042A0395; Fri, 14 Feb 2014 14:00:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8B3RpPf4EF36; Fri, 14 Feb 2014 14:00:14 -0800 (PST)
Received: from [10.30.0.112] (unknown [83.150.71.93]) by c9a.amsl.com (Postfix) with ESMTPSA id 519B4A02DC; Fri, 14 Feb 2014 14:00:13 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Update on IAOC appointment by the IESG
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Sat, 15 Feb 2014 00:00:36 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE25935F-2958-4F15-A5BC-3C3461639408@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/HouMru7gk6F-OebU8TikyOitDD0
Cc: John R Levine <johnl@taugh.com>, IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IETF discussion list <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, 14 Feb 2014 22:00:44 -0000

Previously, the IESG sent an announcement about filling the seat on the =
IAOC that the IESG is responsible for filling every other year. The =
announcement indicated that the IESG had now completed the process and =
selected John Levine as the new IAOC member. Unfortunately we failed to =
review all the obligations of the position with our appointee and after =
learning more about those obligations he has reluctantly concluded that =
he cannot accept the appointment. My sincere apologies to John and other =
candidates for this mistake.=20

New members do not get seated until the March IETF. Fortunately, we had =
several very strong candidates, so the IESG plans to continue the =
selection process as if no decision had yet been made. Please stay tuned =
for further information.

Jari Arkko for the IESG=


From nobody Sat Feb 15 02:22:13 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 C72CD1A0112; Sat, 15 Feb 2014 02:22:09 -0800 (PST)
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 zKhCS-9XduGh; Sat, 15 Feb 2014 02:22:07 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [64.170.98.21]) by ietfa.amsl.com (Postfix) with ESMTP id 039C81A0107; Sat, 15 Feb 2014 02:22:07 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 352EB9FF82; Sat, 15 Feb 2014 02:21:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ACX4rL4gHWo0; Sat, 15 Feb 2014 02:21:37 -0800 (PST)
Received: from [192.168.43.118] (37-136-114-191.nat.bb.dnainternet.fi [37.136.114.191]) by c9a.amsl.com (Postfix) with ESMTPSA id 5D8329FB53; Sat, 15 Feb 2014 02:21:35 -0800 (PST)
Content-Type: text/plain; charset=windows-1252
Subject: Internet organisations coordination meeting
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Sat, 15 Feb 2014 12:21:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@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/Fs6CO1XPd6SdhfYbxfK2LMtTe6c
Cc: IETF discussion list <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: IETF discussion list <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: Sat, 15 Feb 2014 10:22:10 -0000

For your information, the IETF and IAB chairs participated in a meeting =
where we met with leaders of a number of other Internet organisations. A =
brief statement was issued:

> Leaders of the organizations responsible for coordination of the =
Internet technical infrastructure (loosely referred to as =93I* =
leaders=94) met last week in Santa Monica, California, USA. During the =
2-day meeting, they discussed activities underway and exchanged views =
and updates on a range of topics including:
>=20
> 	=95 IETF and W3C efforts to improve overall Internet privacy and =
security (http://www.ietf.org & http://w3.org)
> 	=95 Globalization of the IANA functions (http://www.iana.org)
> 	=95 The 1net initiative, website and new collaboration forum =
(http://1net.org)
> 	=95 The =93Netmundial=94 =96 Global Multistakeholder Meeting on =
the Future of Internet Governance (http://netmundial.br)
> 	=95 ICANN strategy panels and globalization efforts =
(http://www.icann.org)
> 	=95 Preparations for the 2014 ITU Plenipotentiary Conference =
(http://www.internetsociety.org/plenipotbackground)
> 	=95 Web 25th anniversary and W3C 20th anniversary planning =
(http://w3.org)
>=20
> There was discussion of the significant progress and momentum that has =
developed since our last meeting, and as well as the need for continued =
engagement of all stakeholders in evolution of the Internet ecosystem. =
The leaders were encouraged by the progress made in many areas, and note =
that there is a lot of work happening in our respective communities, =
driven by the participants and handled with the usual community =
processes.
>=20
> The meeting also welcomed Kathy Brown, the incoming CEO of the =
Internet Society, and Carolina Aguerre as a representative of the ccTLD =
registry community.
>=20
> Participating I* Leaders:
>=20
> 	=95 Adiel A. Akplogan, CEO African Network Information Center =
(AFRINIC)
> 	=95 John Curran, CEO American Registry for Internet Numbers =
(ARIN)
> 	=95 Paul Wilson, Director General Asia-Pacific Network =
Information Centre (APNIC)
> 	=95 Russ Housley, Chair Internet Architecture Board (IAB)
> 	=95 Fadi Chehad=E9, President and CEO Internet Corporation for =
Assigned Names and Numbers (ICANN)
> 	=95 Jari Arkko, Chair Internet Engineering Task Force (IETF)
> 	=95 Kathy Brown, President and CEO Internet Society (ISOC)
> 	=95 Ra=FAl Echeberr=EDa, CEO Latin America and Caribbean =
Internet Addresses Registry (LACNIC)
> 	=95 Axel Pawlik, Managing Director R=E9seaux IP Europ=E9ens =
Network Coordination Centre (RIPE NCC)
> 	=95 Jeff Jaffe, CEO World Wide Web Consortium (W3C)
> 	=95 Carolina Aguerre, General Manager, LACTLD (association of =
ccTLD registry operators in Latin America and Caribbean)

(=46rom =
http://www.iab.org/documents/correspondence-reports-documents/2014-2/state=
ment-from-the-i-leaders-coordination-meeting-santa-monica-14-february-2014=
/)


From nobody Sat Feb 15 12:20:06 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 8F5571A02B7 for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 12:20:04 -0800 (PST)
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 K7zFS-oxRIIA for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 12:20:01 -0800 (PST)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) by ietfa.amsl.com (Postfix) with ESMTP id BD9171A02A3 for <ietf@ietf.org>; Sat, 15 Feb 2014 12:20:01 -0800 (PST)
Received: by mail-pd0-f177.google.com with SMTP id x10so13273777pdj.36 for <ietf@ietf.org>; Sat, 15 Feb 2014 12:20:00 -0800 (PST)
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=TmfC80tiDw2CLndP2AiUpii+r27dgPR/a2n6B2PTYoQ=; b=l99ra8HtbB0QKnp6fTWF8d3XlxivY7C5ORO1+FuZxOOGsDXGApQTmKR3QnZAddSyAB 2eVRclhG2qVHeFr9YrcxZ7WZtHEm2/3qCJWaVn5lQ/tCthIWF5LeFCZ+Mvlcu8Q14+HJ GQs0BjWVIXhGL6RbCJcayaYpUlbNB6a8HXphs9a9Y5NB+3P9iLhom2LA50jOvH2ExABa TrcumUfVjEt21zX4WePKF5enAFgid7IdYOnGeVKUGgQFDcZL20jLX5JmyyTCpzaUAxZS 5RRrupoj6WYf2fz6KUnyXKBt3FbsCDR5C9IDQQIRcsYwXQlN77LMU4CMsBOv+wL3iWkT jWQA==
X-Received: by 10.68.194.65 with SMTP id hu1mr3686446pbc.158.1392495599872; Sat, 15 Feb 2014 12:19:59 -0800 (PST)
Received: from [192.168.178.23] (153.200.69.111.dynamic.snap.net.nz. [111.69.200.153]) by mx.google.com with ESMTPSA id q7sm29898304pbc.20.2014.02.15.12.19.58 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 15 Feb 2014 12:19:59 -0800 (PST)
Message-ID: <52FFCBEC.3040602@gmail.com>
Date: Sun, 16 Feb 2014 09:19:56 +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: Internet organisations coordination meeting
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org>
In-Reply-To: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/csxNONr9vrimUMWwJ-fDc4cFlfU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Feb 2014 20:20:04 -0000

Thanks for the update.

I'd really like to push the idea that we stop using the word "leaders"
and start using "spokespeople".

It's something I should have realised many years ago; the enormous
scientific collaborations at CERN who used to be my customers have
used this terminology (or spokesman/spokeswoman) for ever. It really
is closer to what we want to project about our community, isn't it?

Regards
   Brian

On 15/02/2014 23:21, IETF Chair wrote:
> For your information, the IETF and IAB chairs participated in a meeting=
 where we met with leaders of a number of other Internet organisations. A=
 brief statement was issued:
>=20
>> Leaders of the organizations responsible for coordination of the Inter=
net technical infrastructure (loosely referred to as =E2=80=9CI* leaders=E2=
=80=9D) met last week in Santa Monica, California, USA. During the 2-day =
meeting, they discussed activities underway and exchanged views and updat=
es on a range of topics including:
>>
>> 	=E2=80=A2 IETF and W3C efforts to improve overall Internet privacy an=
d security (http://www.ietf.org & http://w3.org)
>> 	=E2=80=A2 Globalization of the IANA functions (http://www.iana.org)
>> 	=E2=80=A2 The 1net initiative, website and new collaboration forum (h=
ttp://1net.org)
>> 	=E2=80=A2 The =E2=80=9CNetmundial=E2=80=9D =E2=80=93 Global Multistak=
eholder Meeting on the Future of Internet Governance (http://netmundial.b=
r)
>> 	=E2=80=A2 ICANN strategy panels and globalization efforts (http://www=
=2Eicann.org)
>> 	=E2=80=A2 Preparations for the 2014 ITU Plenipotentiary Conference (h=
ttp://www.internetsociety.org/plenipotbackground)
>> 	=E2=80=A2 Web 25th anniversary and W3C 20th anniversary planning (htt=
p://w3.org)
>>
>> There was discussion of the significant progress and momentum that has=
 developed since our last meeting, and as well as the need for continued =
engagement of all stakeholders in evolution of the Internet ecosystem. Th=
e leaders were encouraged by the progress made in many areas, and note th=
at there is a lot of work happening in our respective communities, driven=
 by the participants and handled with the usual community processes.
>>
>> The meeting also welcomed Kathy Brown, the incoming CEO of the Interne=
t Society, and Carolina Aguerre as a representative of the ccTLD registry=
 community.
>>
>> Participating I* Leaders:
>>
>> 	=E2=80=A2 Adiel A. Akplogan, CEO African Network Information Center (=
AFRINIC)
>> 	=E2=80=A2 John Curran, CEO American Registry for Internet Numbers (AR=
IN)
>> 	=E2=80=A2 Paul Wilson, Director General Asia-Pacific Network Informat=
ion Centre (APNIC)
>> 	=E2=80=A2 Russ Housley, Chair Internet Architecture Board (IAB)
>> 	=E2=80=A2 Fadi Chehad=C3=A9, President and CEO Internet Corporation f=
or Assigned Names and Numbers (ICANN)
>> 	=E2=80=A2 Jari Arkko, Chair Internet Engineering Task Force (IETF)
>> 	=E2=80=A2 Kathy Brown, President and CEO Internet Society (ISOC)
>> 	=E2=80=A2 Ra=C3=BAl Echeberr=C3=ADa, CEO Latin America and Caribbean =
Internet Addresses Registry (LACNIC)
>> 	=E2=80=A2 Axel Pawlik, Managing Director R=C3=A9seaux IP Europ=C3=A9e=
ns Network Coordination Centre (RIPE NCC)
>> 	=E2=80=A2 Jeff Jaffe, CEO World Wide Web Consortium (W3C)
>> 	=E2=80=A2 Carolina Aguerre, General Manager, LACTLD (association of c=
cTLD registry operators in Latin America and Caribbean)
>=20
> (From http://www.iab.org/documents/correspondence-reports-documents/201=
4-2/statement-from-the-i-leaders-coordination-meeting-santa-monica-14-feb=
ruary-2014/)
>=20
>=20


From nobody Sat Feb 15 12:48:50 2014
Return-Path: <jmamodio@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 9C99D1A02D6 for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 12:48:49 -0800 (PST)
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 JFR-BPc6gWkj for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 12:48:48 -0800 (PST)
Received: from mail-ve0-x235.google.com (mail-ve0-x235.google.com [IPv6:2607:f8b0:400c:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2CC0A1A02E5 for <ietf@ietf.org>; Sat, 15 Feb 2014 12:48:47 -0800 (PST)
Received: by mail-ve0-f181.google.com with SMTP id cz12so10965494veb.12 for <ietf@ietf.org>; Sat, 15 Feb 2014 12:48:45 -0800 (PST)
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=rpBRYILdJ/RBbNl8ouTpuM0K9zK/Y8BlQuyEsxsccfk=; b=HjhiWs94S+8OOSxfFyt2gs/jYiCo91AB4qT120Rrxu4G9ou0h7Fzfm3LcMiO1O8WJd NEGyLM8Lo8tcpL2mMHx3s8Ib6RN7Uvsy/ccTMRZQNTM5gyCVbHS0cEaVp3U0tk6vJmAO YZ6tyvAZEUO/FX4mNWSLcc7QcoI+onsSHfl2sZKB0e7a56O9+gSpUUV/GYO4Lz1LwvUi ACDo2LpasO+R3AjEyon6GvaeWK+DyGy31y6CRyaFppx9KNXbW5xCa/jI6vaPrmN0kSrs nKfCzSV+Jx/LjzD+2eHJlZXMaDMBPgzYa6FZjgvttzEIXeqawOdY/XkuyIXPshwqw8oE pN3Q==
MIME-Version: 1.0
X-Received: by 10.52.156.232 with SMTP id wh8mr5646730vdb.23.1392497325897; Sat, 15 Feb 2014 12:48:45 -0800 (PST)
Received: by 10.58.218.226 with HTTP; Sat, 15 Feb 2014 12:48:45 -0800 (PST)
In-Reply-To: <52FFCBEC.3040602@gmail.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com>
Date: Sat, 15 Feb 2014 14:48:45 -0600
Message-ID: <CAMzo+1aeeN7XpGwA2JZkWUNLk8tPWSDFGjgAmiaSSwXV9Svk1w@mail.gmail.com>
Subject: Re: Internet organisations coordination meeting
From: Jorge Amodio <jmamodio@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Content-Type: multipart/alternative; boundary=089e01633aa875ffe104f2780cdf
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/waKTjS-AMtw53lVWShPg1h7Vuyc
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: Sat, 15 Feb 2014 20:48:49 -0000

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

Agreed, it sounds/feels like a dictatorial junta.

-J

On Sat, Feb 15, 2014 at 2:19 PM, Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Thanks for the update.
>
> I'd really like to push the idea that we stop using the word "leaders"
> and start using "spokespeople".
>

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

<div dir=3D"ltr"><br><div>Agreed, it sounds/feels like a dictatorial junta.=
</div><div><br></div><div>-J</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Sat, Feb 15, 2014 at 2:19 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>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Thanks for the update.<br>
<br>
I&#39;d really like to push the idea that we stop using the word &quot;lead=
ers&quot;<br>
and start using &quot;spokespeople&quot;.<br></blockquote></div></div></div=
>

--089e01633aa875ffe104f2780cdf--


From nobody Sat Feb 15 13:19:45 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 8D67C1A00ED for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 13:19:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a7RMT7JI7rwZ for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 13:19:40 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 7BC141A019C for <ietf@ietf.org>; Sat, 15 Feb 2014 13:19:39 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WEmdy-0006lU-1U; Sat, 15 Feb 2014 16:19:26 -0500
Date: Sat, 15 Feb 2014 16:19:21 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
Subject: Re: Internet organisations coordination meeting
Message-ID: <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>
In-Reply-To: <52FFCBEC.3040602@gmail.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8es-DbIDxm0cwoAwD_fkZOxl4vM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Feb 2014 21:19:43 -0000

--On Sunday, February 16, 2014 09:19 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> Thanks for the update.
> 
> I'd really like to push the idea that we stop using the word
> "leaders" and start using "spokespeople".
> 
> It's something I should have realised many years ago; the
> enormous scientific collaborations at CERN who used to be my
> customers have used this terminology (or
> spokesman/spokeswoman) for ever. It really is closer to what
> we want to project about our community, isn't it?

Brian,

Yes.  The problem is that, while the RIR and ISOC CESs, and
maybe the ICANN one, have the authority and perhaps even a
mandate, to act as spokespeople.  The IAB and IETF Chairs have
no such authority: in the absence of rather specific inquiries
of the community and determination of consensus, they are not
supposed to "speak for", e.g., the IETF.   It is entirely
reasonable, and sometimes necessary, that they be able to speak
as individuals who happen to hold those positions and who have
the perspective that comes with those positions but, in allowing
them to do that, the community trusts that they will make the
distinction as clear as necessary for the particular
circumstances that apply.

Certainly you understand that.  My recollection is that you were
exceptional careful about the distinctions while wearing the
relevant hats.

It is a challenging situation for everyone involved, but I don't
think the terminology change would improve things.  It might
make them worse.

   best,
     john



From nobody Sat Feb 15 14:48: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 BAF231A02C3 for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 14:48:15 -0800 (PST)
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 JndQVpSdmKnN for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 14:48:13 -0800 (PST)
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 A103B1A0133 for <ietf@ietf.org>; Sat, 15 Feb 2014 14:48:13 -0800 (PST)
Received: by mail-pd0-f169.google.com with SMTP id v10so13356748pde.14 for <ietf@ietf.org>; Sat, 15 Feb 2014 14:48:11 -0800 (PST)
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=FTzv9eQzEBHVH/g2FWo1FEhubweT5DGYsMzzT4ZKck4=; b=I+sbpH+uAG/f1komhCs6Sv+hZYfPjd3PALhxZ9HCAm91/Q5flDarEWes+Xcn7yc0W4 KsRpOYzQODpR7yebB/KA6ABYVlzrs8zT1gIBN2HTZFAni9ht9ovlhgYPslMjBijvZel/ CQSb+KrQvxNlpX9B9Bz0mL/W5xxa116O5347b2DA7GCyLOWtPhOFOHtqu168shtWPZ3h siSX7m86KTsUXxTbuGcqv+2zQ/2UMXQP06Yn7QHKf5FgQBpZTXdlMFYBzfhFSsQnjUa6 KlUvG8yyx0pEpD6Th9X+bbh5RY8gD4olxITRViXiLdACPGajasy16+56mhaVtRqt/tXk +KNA==
X-Received: by 10.66.149.7 with SMTP id tw7mr17584926pab.72.1392504491645; Sat, 15 Feb 2014 14:48:11 -0800 (PST)
Received: from [192.168.178.23] (153.200.69.111.dynamic.snap.net.nz. [111.69.200.153]) by mx.google.com with ESMTPSA id nm5sm30547120pbc.29.2014.02.15.14.48.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 15 Feb 2014 14:48:11 -0800 (PST)
Message-ID: <52FFEEA8.3060309@gmail.com>
Date: Sun, 16 Feb 2014 11:48:08 +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: Internet organisations coordination meeting
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>
In-Reply-To: <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/IX3g8UJzPA2HHriYql9kl6eJgfA
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, 15 Feb 2014 22:48:15 -0000

On 16/02/2014 10:19, John C Klensin wrote:
> 
> --On Sunday, February 16, 2014 09:19 +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
> 
>> Thanks for the update.
>>
>> I'd really like to push the idea that we stop using the word
>> "leaders" and start using "spokespeople".
>>
>> It's something I should have realised many years ago; the
>> enormous scientific collaborations at CERN who used to be my
>> customers have used this terminology (or
>> spokesman/spokeswoman) for ever. It really is closer to what
>> we want to project about our community, isn't it?
> 
> Brian,
> 
> Yes.  The problem is that, while the RIR and ISOC CESs, and
> maybe the ICANN one, have the authority and perhaps even a
> mandate, to act as spokespeople.  The IAB and IETF Chairs have
> no such authority: in the absence of rather specific inquiries
> of the community and determination of consensus, they are not
> supposed to "speak for", e.g., the IETF.   It is entirely
> reasonable, and sometimes necessary, that they be able to speak
> as individuals who happen to hold those positions and who have
> the perspective that comes with those positions but, in allowing
> them to do that, the community trusts that they will make the
> distinction as clear as necessary for the particular
> circumstances that apply.
> 
> Certainly you understand that.  My recollection is that you were
> exceptional careful about the distinctions while wearing the
> relevant hats.
> 
> It is a challenging situation for everyone involved, but I don't
> think the terminology change would improve things.  It might
> make them worse.

I think it's all a matter of perception. But of course you're
correct - it's very important that whoever attends such meetings
from our community steers very carefully along those narrow and
invisible lines. I'm not so sure I was always successful myself.

Certainly the physics "spokespeople" I used to deal with were
usually very skilful at such navigation. If not, they had a very
rough time at the next collaboration meeting. Sounds familiar?

    Brian


From nobody Sat Feb 15 15:41:12 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 E71681A00F5 for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 15:41:11 -0800 (PST)
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 PCeghF96PhSX for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 15:41:09 -0800 (PST)
Received: from mail-lb0-x229.google.com (mail-lb0-x229.google.com [IPv6:2a00:1450:4010:c04::229]) by ietfa.amsl.com (Postfix) with ESMTP id 0C16A1A0024 for <ietf@ietf.org>; Sat, 15 Feb 2014 15:41:08 -0800 (PST)
Received: by mail-lb0-f169.google.com with SMTP id q8so10484454lbi.0 for <ietf@ietf.org>; Sat, 15 Feb 2014 15:41:06 -0800 (PST)
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=29uTYl1n2ywEyUHe88OJu4skD3b31SIIDuyQHDpItcI=; b=yiHoGfsNLJlqtCEXJDne/V5AHGVh2jQfhPLL+Ze/k6qfDQYxIZdJKy0gxeibxGMOUe tanAEKdaNz7PUW7bY7YVYyj3N68isAL6BnYS5hvWQanpgVN7VPxXAAxNjf5AKcTceQHN gLsMsxFhzKGYK7bRIZ4RAw0+4AClSoMQ/l2MmtlEDb4TYhbGC+h61ZWLl1d+CsEv8rSS JWikeOIT59R6SR9+gZYsOZj2D/+7Qpd6Nbancmq7ce04yBn6RPCgaSvF7wYqvEYayBRM fpi5OIYvGs4y+eCWw3ih9UUih4PF/N/XpORo6xyRDuMw4O6NOdRKEvoTANgwY1m6Yzxx i/mQ==
MIME-Version: 1.0
X-Received: by 10.152.209.7 with SMTP id mi7mr3375064lac.42.1392507666150; Sat, 15 Feb 2014 15:41:06 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Sat, 15 Feb 2014 15:41:05 -0800 (PST)
In-Reply-To: <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>
Date: Sat, 15 Feb 2014 18:41:05 -0500
Message-ID: <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com>
Subject: Re: Internet organisations coordination meeting
From: Phillip Hallam-Baker <hallam@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=001a113801a0c9b94104f27a74da
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Jo9k08Xx04hy50HSExHoje1nNus
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: Sat, 15 Feb 2014 23:41:12 -0000

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

On Sat, Feb 15, 2014 at 4:19 PM, John C Klensin <john-ietf@jck.com> wrote:

>
>
> --On Sunday, February 16, 2014 09:19 +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com> wrote:
>
> > Thanks for the update.
> >
> > I'd really like to push the idea that we stop using the word
> > "leaders" and start using "spokespeople".
> >
> > It's something I should have realised many years ago; the
> > enormous scientific collaborations at CERN who used to be my
> > customers have used this terminology (or
> > spokesman/spokeswoman) for ever. It really is closer to what
> > we want to project about our community, isn't it?
>
> Brian,
>
> Yes.  The problem is that, while the RIR and ISOC CESs, and
> maybe the ICANN one, have the authority and perhaps even a
> mandate, to act as spokespeople.  The IAB and IETF Chairs have
> no such authority: in the absence of rather specific inquiries
> of the community and determination of consensus, they are not
> supposed to "speak for", e.g., the IETF.


Leader is generally considered to be rather stronger than spokesperson. If
they are not spokespeople they are not leaders either. And in any case
leaders have to have followers.

There might be a cultural issue here. I note in the UK academic system it
would be utterly unthinkable for the Vice-Chancellor of any university to
wade into a public political debate and state the view of their university.
It would be even more unthinkable for them to do that without any
discussion with the faculty. But that happens all the time in the US system.

There is a reason all the 'top' jobs in the UK are irrelevant sinecures.
The university is run by the Vice-Chancellor, not the Chancellor, the
government is run by the Prime Minister, not the Queen and the Archbishop
of Canterbury is theoretically the number 3 in the CoE.


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

--001a113801a0c9b94104f27a74da
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 Sat, Feb 15, 2014 at 4:19 PM, John C Klensin <span dir=3D"ltr">&=
lt;<a href=3D"mailto:john-ietf@jck.com" target=3D"_blank">john-ietf@jck.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"><br>
<br>
--On Sunday, February 16, 2014 09:19 +1300 Brian E Carpenter<br>
<div class=3D"">&lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.=
carpenter@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Thanks for the update.<br>
&gt;<br>
&gt; I&#39;d really like to push the idea that we stop using the word<br>
&gt; &quot;leaders&quot; and start using &quot;spokespeople&quot;.<br>
&gt;<br>
&gt; It&#39;s something I should have realised many years ago; the<br>
&gt; enormous scientific collaborations at CERN who used to be my<br>
&gt; customers have used this terminology (or<br>
&gt; spokesman/spokeswoman) for ever. It really is closer to what<br>
&gt; we want to project about our community, isn&#39;t it?<br>
<br>
</div>Brian,<br>
<br>
Yes. =A0The problem is that, while the RIR and ISOC CESs, and<br>
maybe the ICANN one, have the authority and perhaps even a<br>
mandate, to act as spokespeople. =A0The IAB and IETF Chairs have<br>
no such authority: in the absence of rather specific inquiries<br>
of the community and determination of consensus, they are not<br>
supposed to &quot;speak for&quot;, e.g., the IETF. =A0</blockquote><div><br=
></div><div>Leader is generally considered to be rather stronger than spoke=
sperson. If they are not spokespeople they are not leaders either. And in a=
ny case leaders have to have followers.</div>
<div><br></div><div>There might be a cultural issue here. I note in the UK =
academic system it would be utterly unthinkable for the Vice-Chancellor of =
any university to wade into a public political debate and state the view of=
 their university. It would be even more unthinkable for them to do that wi=
thout any discussion with the faculty. But that happens all the time in the=
 US system.</div>
<div><br></div><div>There is a reason all the &#39;top&#39; jobs in the UK =
are irrelevant sinecures. The university is run by the Vice-Chancellor, not=
 the Chancellor, the government is run by the Prime Minister, not the Queen=
 and the Archbishop of Canterbury is theoretically the number 3 in the CoE.=
</div>
</div><br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"http://ha=
llambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a113801a0c9b94104f27a74da--


From nobody Sat Feb 15 16:38:50 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 EBFDF1A0309 for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 16:38:48 -0800 (PST)
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 BaUsZ_IIL6fZ for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 16:38:47 -0800 (PST)
Received: from atl4mhob13.myregisteredsite.com (atl4mhob13.myregisteredsite.com [209.17.115.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4583B1A030A for <ietf@ietf.org>; Sat, 15 Feb 2014 16:38:47 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.210]) by atl4mhob13.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s1G0ch7K008730 for <ietf@ietf.org>; Sat, 15 Feb 2014 19:38:43 -0500
Received: (qmail 8874 invoked by uid 0); 16 Feb 2014 00:38:43 -0000
X-TCPREMOTEIP: 68.15.42.104
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?127.0.0.1?) (avri@ella.com@68.15.42.104) by 0 with ESMTPA; 16 Feb 2014 00:38:43 -0000
Message-ID: <5300088E.2090005@acm.org>
Date: Sat, 15 Feb 2014 19:38:38 -0500
From: Avri Doria <avri@acm.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet organisations coordination meeting
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com>
In-Reply-To: <52FFCBEC.3040602@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 140215-1, 02/15/2014), Outbound message
X-Antivirus-Status: Not-Tested
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dyrey7hq6d30TuOqL0BwGltz8Bs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Feb 2014 00:38:49 -0000

Hi,

I very much agree.

The word leader has that whole top-down meaning to it.

I like the use of 'spokespeople', with the variants.

avri


On 15-Feb-14 15:19, Brian E Carpenter wrote:
> Thanks for the update.
>
> I'd really like to push the idea that we stop using the word "leaders"
> and start using "spokespeople".
>
> It's something I should have realised many years ago; the enormous
> scientific collaborations at CERN who used to be my customers have
> used this terminology (or spokesman/spokeswoman) for ever. It really
> is closer to what we want to project about our community, isn't it?
>
> Regards
>     Brian
>
> On 15/02/2014 23:21, IETF Chair wrote:
>> >For your information, the IETF and IAB chairs participated in a meeting where we met with leaders of a number of other Internet organisations. A brief statement was issued:
>> >
>>> >>Leaders of the organizations responsible for coordination of the Internet technical infrastructure


From nobody Sat Feb 15 23:32: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 D65FE1A038D for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 23:32:26 -0800 (PST)
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 nOaQ-ADcpJ_B for <ietf@ietfa.amsl.com>; Sat, 15 Feb 2014 23:32:24 -0800 (PST)
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 5FD401A038C for <ietf@ietf.org>; Sat, 15 Feb 2014 23:32:24 -0800 (PST)
Received: by mail-yh0-f42.google.com with SMTP id a41so13335901yho.29 for <ietf@ietf.org>; Sat, 15 Feb 2014 23:32:22 -0800 (PST)
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; bh=NKnjDacYnifoaZTtNAVr44JaDEbW4euqxacL1ud7X9Q=; b=MuNGvtR0Rfa+HsUjfjO00KoLk5+jmGvqScY4upSqmppJkifuJVKpdcPy6UxNhXa5xp 7WHmHc06psfXrqsC1a5G0ws3oa8WzkuD90TCuHAjboG8H87tchi7kv9q4zkdRJYjB+BH 9V/ynFxaCj3XTPqWKi0V5ZGx45P+tMqoND5PleaT8farzIoN7VASm7Y2oG+GSpVHypgb hB+XBNQ1zKT/awH/PlEop80Hzi3erR9U48KcKMrK/jFeKHAV4lMZVIwvBMlOAyc6hnXN shYRLRXCVsb580tihYZmRFKS9PZJamSp2vCv7YImL68MOMeqNgxWfUYgBq+UkxnluZUM uHNA==
MIME-Version: 1.0
X-Received: by 10.236.99.38 with SMTP id w26mr3499300yhf.18.1392535942157; Sat, 15 Feb 2014 23:32:22 -0800 (PST)
Received: by 10.170.222.3 with HTTP; Sat, 15 Feb 2014 23:32:22 -0800 (PST)
In-Reply-To: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org>
Date: Sun, 16 Feb 2014 08:32:22 +0100
Message-ID: <CADnDZ8_M3JHBQb2WYUUNw3x_2KQdJ+iN33yjBpJjOfTqEawDhg@mail.gmail.com>
Subject: Internet organisations coordination meeting
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf3011e0272b58c604f2810a3c
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XH_6JfjXkm6DIp4XVT-X7ouVBrM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Feb 2014 07:32:27 -0000

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

On Saturday, February 15, 2014, IETF Chair wrote:

> For your information, the IETF and IAB chairs participated in a meeting
> where we met with leaders of a number of other Internet organisations.


The meeting results was not clearly specified in the statement, that makes
it lacks some important information. Internet Leaders should provide
followers with current coordination decisions or solutions.

A brief statement was issued:
>
> > Leaders of the organizations responsible for coordination of the
> Internet technical infrastructure (loosely referred to as "I* leaders") met
> last week in Santa Monica, California, USA.


I think the organisations are taking the responsibility of coordination
(not they are totally responsible or they are the only organisations
responsible). So I think it is better to say: ... organisations that are
currently taking responsibility for coordination.....

On Saturday, February 15, 2014, Brian E Carpenter wrote:

> Thanks for the update.
>
> I'd really like to push the idea that we stop using the word "leaders"
> and start using "spokespeople".


I don't mind both titles. The idea of leadership is not only for
organisation heads or directors but may be for others in any organisation.
I disagree that IETF has only assigned leaders but there are others which
are the real leaders of technologies. In IETF I have some of my leaders are
not chairs or directors or authors but just participants.

Leaders need followers or electors, otherwise they are not leaders even if
there was a title, real leaders in organisations have no title but they
have followers, because they had the engineering sense of reasoning and
quality.


Thanking you,
AB

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

On Saturday, February 15, 2014, IETF Chair  wrote:<br><div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">For your information, the IETF and IAB chairs participated i=
n a meeting where we met with leaders of a number of other Internet organis=
ations.&nbsp;</blockquote>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"></blockquote><div><br></div><div>The meeting=
 results was not clearly&nbsp;specified in the statement, that makes it lac=
ks some important information. Internet&nbsp;Leaders should provide followe=
rs with current&nbsp;coordination decisions or solutions.&nbsp;</div>
<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">A brief statement was issued:=
<br>

<br>
&gt; Leaders of the organizations responsible for coordination of the Inter=
net technical infrastructure (loosely referred to as &ldquo;I* leaders&rdqu=
o;) met last week in Santa Monica, California, USA.&nbsp;</blockquote><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex">

</blockquote><div><br></div><div>I think the&nbsp;organisations&nbsp;are ta=
king the&nbsp;responsibility of coordination (not they are totally responsi=
ble or they are the&nbsp;only organisations responsible). So I think it is =
better to say: ...&nbsp;organisations that are currently taking responsibil=
ity for coordination.....</div>
<div><br></div><div><font><span style=3D"background-color:rgba(255,255,255,=
0)">On Saturday, February 15, 2014, Brian E Carpenter&nbsp;wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-w=
idth:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding=
-left:1ex">
Thanks for the update.<br><br>I&#39;d really like to push the idea that we =
stop using the word &quot;leaders&quot;<br>and start using &quot;spokespeop=
le&quot;.</blockquote><div><br></div><div>I don&#39;t mind both titles.&nbs=
p;The idea of leadership is not only for organisation&nbsp;heads or directo=
rs but may be for others in any organisation. I disagree that IETF has only=
 assigned leaders but there are others which are the real leaders of techno=
logies. In IETF I have some of my leaders are not chairs or directors or au=
thors&nbsp;but just participants.&nbsp;</div>
<div><br></div><div>Leaders need followers or electors,&nbsp;otherwise they=
 are not leaders even if there was a title, real leaders in organisations h=
ave no title but they have followers, because they had&nbsp;the engineering=
 sense of reasoning and quality.&nbsp;</div>
<div>&nbsp;</div></span></font></div>
<br><div>Thanking you,</div><div>AB</div></div>

--20cf3011e0272b58c604f2810a3c--


From nobody Sun Feb 16 00:16:33 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 368A21A004B for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 00:16:31 -0800 (PST)
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 r8KFSIgfIwfX for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 00:16:27 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.140]) by ietfa.amsl.com (Postfix) with ESMTP id 620DB1A0046 for <ietf@ietf.org>; Sun, 16 Feb 2014 00:16:27 -0800 (PST)
Received: from [195.245.231.67:56716] by server-4.bemta-5.messagelabs.com id 19/3A-08092-6D370035; Sun, 16 Feb 2014 08:16:22 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-82.messagelabs.com!1392538582!30489170!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 3241 invoked from network); 16 Feb 2014 08:16:22 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-14.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 16 Feb 2014 08:16:22 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Sun, 16 Feb 2014 08:16:21 +0000
From: <l.wood@surrey.ac.uk>
To: <hallam@gmail.com>, <john-ietf@jck.com>
Date: Sun, 16 Feb 2014 08:15:56 +0000
Subject: RE: Internet organisations coordination meeting
Thread-Topic: Internet organisations coordination meeting
Thread-Index: Ac8qp3kYpzZPMCVJQWecc5zAzmR7KgAR9g/7
Message-ID: <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>, <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com>
In-Reply-To: <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@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/zhgmuL1qlp1eLf24uXrWKBjne1w
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, 16 Feb 2014 08:16:31 -0000

Yes, 'leader' is too strong.

'blogger in chief' may be more appropriate...

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Phillip Hallam-Baker [halla=
m@gmail.com]
Sent: 15 February 2014 23:41
To: John C Klensin
Cc: IETF Discussion Mailing List
Subject: Re: Internet organisations coordination meeting

On Sat, Feb 15, 2014 at 4:19 PM, John C Klensin <john-ietf@jck.com<mailto:j=
ohn-ietf@jck.com>> wrote:


--On Sunday, February 16, 2014 09:19 +1300 Brian E Carpenter
<brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>> wrote:

> Thanks for the update.
>
> I'd really like to push the idea that we stop using the word
> "leaders" and start using "spokespeople".
>
> It's something I should have realised many years ago; the
> enormous scientific collaborations at CERN who used to be my
> customers have used this terminology (or
> spokesman/spokeswoman) for ever. It really is closer to what
> we want to project about our community, isn't it?

Brian,

Yes.  The problem is that, while the RIR and ISOC CESs, and
maybe the ICANN one, have the authority and perhaps even a
mandate, to act as spokespeople.  The IAB and IETF Chairs have
no such authority: in the absence of rather specific inquiries
of the community and determination of consensus, they are not
supposed to "speak for", e.g., the IETF.

Leader is generally considered to be rather stronger than spokesperson. If =
they are not spokespeople they are not leaders either. And in any case lead=
ers have to have followers.

There might be a cultural issue here. I note in the UK academic system it w=
ould be utterly unthinkable for the Vice-Chancellor of any university to wa=
de into a public political debate and state the view of their university. I=
t would be even more unthinkable for them to do that without any discussion=
 with the faculty. But that happens all the time in the US system.

There is a reason all the 'top' jobs in the UK are irrelevant sinecures. Th=
e university is run by the Vice-Chancellor, not the Chancellor, the governm=
ent is run by the Prime Minister, not the Queen and the Archbishop of Cante=
rbury is theoretically the number 3 in the CoE.


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


From nobody Sun Feb 16 01:37:12 2014
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D22F1A03C4 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 01:37:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JdIJ-IV2gXjw for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 01:37:05 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 928DB1A03C3 for <ietf@ietf.org>; Sun, 16 Feb 2014 01:37:04 -0800 (PST)
Received: from [10.128.1.195] (node-dac.pool-182-52.dynamic.totbb.net [182.52.67.68]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 088FC180156A for <ietf@ietf.org>; Sun, 16 Feb 2014 10:37:00 +0100 (CET)
Message-ID: <530086B6.8030408@pi.nu>
Date: Sun, 16 Feb 2014 17:36:54 +0800
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Internet organisations coordination meeting
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>, <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E633471B@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/o2EbzVv1uud0PSSdt-xMOPa3em8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Feb 2014 09:37:08 -0000

All,

I have no strong feeling which word is used too describe the folks that
in one way or the other speak for these organizations. I can live with
spokesmen, spokespersons, leaders or chairs.

However it is in the order of ten years since management consultancy
gurus told us to stop using the word "manager" and use "leader" instead.
A leader  was supposed to indicate the leader was one in the group.

About 3 decades before that we were told to stop using "boss" and use
manager instead, "manager" should indicate that the manager were one
of the group.

I can only note that the half-life of these words are decreasing, wonder
what will come after "spokesxxx" in four five years?

If the service these people provide is leadership, call them leaders.
If the service is that they speak, call them "spokesxxx".

/Loa


On 2014-02-16 16:15, l.wood@surrey.ac.uk wrote:
> Yes, 'leader' is too strong.
>
> 'blogger in chief' may be more appropriate...
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of Phillip Hallam-Baker [hallam@gmail.com]
> Sent: 15 February 2014 23:41
> To: John C Klensin
> Cc: IETF Discussion Mailing List
> Subject: Re: Internet organisations coordination meeting
>
> On Sat, Feb 15, 2014 at 4:19 PM, John C Klensin <john-ietf@jck.com<mailto:john-ietf@jck.com>> wrote:
> ;
>
> --On Sunday, February 16, 2014 09:19 +1300 Brian E Carpenter
> <brian.e.carpenter@gmail.com<mailto:brian.e.carpenter@gmail.com>> wrote:
>
>> Thanks for the update.
>>
>> I'd really like to push the idea that we stop using the word
>> "leaders" and start using "spokespeople".
>>
>> It's something I should have realised many years ago; the
>> enormous scientific collaborations at CERN who used to be my
>> customers have used this terminology (or
>> spokesman/spokeswoman) for ever. It really is closer to what
>> we want to project about our community, isn't it?
>
> Brian,
>
> Yes.  The problem is that, while the RIR and ISOC CESs, and
> maybe the ICANN one, have the authority and perhaps even a
> mandate, to act as spokespeople.  The IAB and IETF Chairs have
> no such authority: in the absence of rather specific inquiries
> of the community and determination of consensus, they are not
> supposed to "speak for", e.g., the IETF.
>
> Leader is generally considered to be rather stronger than spokesperson. If they are not spokespeople they are not leaders either. And in any case leaders have to have followers.
>
> There might be a cultural issue here. I note in the UK academic system it would be utterly unthinkable for the Vice-Chancellor of any university to wade into a public political debate and state the view of their university. It would be even more unthinkable for them to do that without any discussion with the faculty. But that happens all the time in the US system.
>
> There is a reason all the 'top' jobs in the UK are irrelevant sinecures. The university is run by the Vice-Chancellor, not the Chancellor, the government is run by the Prime Minister, not the Queen and the Archbishop of Canterbury is theoretically the number 3 in the CoE.
>
>
> --
> Website: http://hallambaker.com/
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From nobody Sun Feb 16 04:20:56 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 DB7551A01C1 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 04:20:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id udnBEMvc3e6X for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 04:20:53 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 382841A01BE for <ietf@ietf.org>; Sun, 16 Feb 2014 04:20:53 -0800 (PST)
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 0663E1B807B for <ietf@ietf.org>; Sun, 16 Feb 2014 04:20:51 -0800 (PST)
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 D5F56190052; Sun, 16 Feb 2014 04:20:50 -0800 (PST)
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; Sun, 16 Feb 2014 04:20:50 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Internet organisations coordination meeting
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <530086B6.8030408@pi.nu>
Date: Sun, 16 Feb 2014 07:20:48 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>, <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu>
To: Loa Andersson <loa@pi.nu>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0UffRcjOahJq_hxdthqfhlJdPI8
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: Sun, 16 Feb 2014 12:20:55 -0000

Folks, as John Klensin said, the reason we do not say "spokesperson" is =
that our leadership do not speak for us.   We only speak as a group =
through the consensus process.   So the term "spokesperson" is simply =
inaccurate.

The term "leader" makes sense as a generic because there were a number =
of organizations, with different leadership structures, some not =
involving the same consensus process that exists in the IETF.   So we =
couldn't for example say "chair," because that term wouldn't apply to =
all the people who signed the statement.

I realize that the term "leader" has its own set of connotations, but I =
don't know of a better word to use.   There is no word that we could use =
that would convey to someone who is not already familiar with IETF =
process what we mean.   Representative is no good for the same reason =
spokesperson is no good.   Avatar doesn't really work either.

I think it's better to just accept that the language is imprecise, and =
think carefully about what is that we might be objecting to, and whether =
the objection _really_ makes sense in the context.   I guess there's =
about zero chance that this won't get discussed to death, and that's =
fine, but I don't think there's a knob to turn here.


From nobody Sun Feb 16 06:48:58 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 A5CAC1A0238 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 06:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.849
X-Spam-Level: 
X-Spam-Status: No, score=-2.849 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iYLziEUbcSiB for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 06:48:56 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 3A3131A0225 for <ietf@ietf.org>; Sun, 16 Feb 2014 06:48:55 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 25BD718C0B3; Sun, 16 Feb 2014 09:48:53 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Internet organisations coordination meeting
Message-Id: <20140216144853.25BD718C0B3@mercury.lcs.mit.edu>
Date: Sun, 16 Feb 2014 09:48:53 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7xwybKyhAHemSO5Ova1-ikGreR4
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: Sun, 16 Feb 2014 14:48:57 -0000

    > From: Ted Lemon <ted.lemon@nominum.com>

    > I realize that the term "leader" has its own set of connotations, but I
    > don't know of a better word to use. There is no word that we could use
    > that would convey to someone who is not already familiar with IETF
    > process what we mean. 

'Hindmost'. (With a tip of the hat to LN and BO.)

	Noel


From nobody Sun Feb 16 07:26:28 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 A37F61A0245 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 07:26:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1U5c3l1iM7qd for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 07:26:24 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 423381A00BC for <ietf@ietf.org>; Sun, 16 Feb 2014 07:26:24 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john@jck.com>) id 1WF3ba-0008VV-82; Sun, 16 Feb 2014 10:26:06 -0500
Date: Sun, 16 Feb 2014 10:26:01 -0500
From: John C Klensin <john@jck.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Internet organisations coordination meeting
Message-ID: <FFFF7F6994A39E3284659420@JcK-HP8200.jck.com>
In-Reply-To: <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>, <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.u k> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_y9vNxXFpFarM7NJkS_bpKC7DhU
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: Sun, 16 Feb 2014 15:26:26 -0000

--On Sunday, February 16, 2014 07:20 -0500 Ted Lemon
<ted.lemon@nominum.com> wrote:

>...
> I think it's better to just accept that the language is
> imprecise, and think carefully about what is that we might be
> objecting to, and whether the objection _really_ makes sense
> in the context.   I guess there's about zero chance that this
> won't get discussed to death, and that's fine, but I don't
> think there's a knob to turn here.

In case it isn't obvious, I agree.  I think it is far more
important that we concentrate or energy on what is being said
(with or without disclaimers) than about social or political
correctness in terminology that almost no one outside will
interpret as significant anyway.

If we come to the conclusion that our "leaders" are not saying
what we want them to say (with or without qualifications about
who they are speaking for), then the correct remedies are to
make them better informed about what we do want said (or not
said) and, in the thoroughly unlikely event that such advice is
ineffective and that is important, direct them to stop
participating in such "leadership" meetings or other events
except possibly as silent observers.

    john




From nobody Sun Feb 16 07:27:18 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 DDA261A03F8 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 07:27:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TrIMGAtUvcT0 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 07:27:15 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 895041A00BC for <ietf@ietf.org>; Sun, 16 Feb 2014 07:27:14 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WF3cZ-0008Vc-DP; Sun, 16 Feb 2014 10:27:07 -0500
Date: Sun, 16 Feb 2014 10:27:02 -0500
From: John C Klensin <john-ietf@jck.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Internet organisations coordination meeting
Message-ID: <91B14EDC39525BDF0B2B531E@JcK-HP8200.jck.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mIvVmkJ7hbnxsH8jmgz14KbQafY
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: Sun, 16 Feb 2014 15:27:17 -0000

(sorry - retransmitting with correct address)

--On Sunday, February 16, 2014 07:20 -0500 Ted Lemon
<ted.lemon@nominum.com> wrote:

>...
> I think it's better to just accept that the language is
> imprecise, and think carefully about what is that we might be
> objecting to, and whether the objection _really_ makes sense
> in the context.   I guess there's about zero chance that this
> won't get discussed to death, and that's fine, but I don't
> think there's a knob to turn here.

In case it isn't obvious, I agree.  I think it is far more
important that we concentrate or energy on what is being said
(with or without disclaimers) than about social or political
correctness in terminology that almost no one outside will
interpret as significant anyway.

If we come to the conclusion that our "leaders" are not saying
what we want them to say (with or without qualifications about
who they are speaking for), then the correct remedies are to
make them better informed about what we do want said (or not
said) and, in the thoroughly unlikely event that such advice is
ineffective and that is important, direct them to stop
participating in such "leadership" meetings or other events
except possibly as silent observers.

    john




From nobody Sun Feb 16 07:58:08 2014
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E10D21A03F3 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 07:58:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.449
X-Spam-Level: 
X-Spam-Status: No, score=-7.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id l7TSDvKosmPk for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 07:58:06 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 4E48D1A002C for <ietf@ietf.org>; Sun, 16 Feb 2014 07:58:05 -0800 (PST)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id s1GFw1os019490; Sun, 16 Feb 2014 17:58:01 +0200
X-CheckPoint: {5300D87B-A-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.228]) by DAG-EX10.ad.checkpoint.com ([169.254.3.110]) with mapi id 14.03.0123.003; Sun, 16 Feb 2014 17:58:02 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Ted Lemon <Ted.Lemon@nominum.com>
Subject: Re: Internet organisations coordination meeting
Thread-Topic: Internet organisations coordination meeting
Thread-Index: AQHPKjf7mBcq6g3BZ0elgXmA/IZeM5q2oJ4AgAAQmoCAACeZgIAAj9kAgAAWnwCAAC3MAIAAPK8A
Date: Sun, 16 Feb 2014 15:58:01 +0000
Message-ID: <606EAF69-0144-4B93-9B34-20DB2A11E853@checkpoint.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com>, <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com>
In-Reply-To: <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.21.121]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <FBBF0D111038DE428F7DEFEFC0C7AEF7@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yO6r93rrvVyghZ9-JSXMtAKJQGE
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: Sun, 16 Feb 2014 15:58:08 -0000

On Feb 16, 2014, at 2:20 PM, Ted Lemon <Ted.Lemon@nominum.com> wrote:

> Folks, as John Klensin said, the reason we do not say "spokesperson" is t=
hat our leadership do not speak for us.   We only speak as a group through =
the consensus process.   So the term "spokesperson" is simply inaccurate.
>=20
> The term "leader" makes sense as a generic because there were a number of=
 organizations, with different leadership structures, some not involving th=
e same consensus process that exists in the IETF.   So we couldn't for exam=
ple say "chair," because that term wouldn't apply to all the people who sig=
ned the statement.

Agree that spokesperson is wrong. Spokespersons (spokespeople?) don't make =
or participate in any decisions, whereas the IETF chair does.

"Leader" and "chair" are both fine. Yes, "chair" is meaningless in other or=
ganizations, but in the days of the cold war, nobody fretted that internati=
onal accords were signed by an American "president", a British "Prime Minis=
ter", a Russian "general secretary", and a Chinese "Chairman". Today when f=
oreign ministers from various countries meet, nobody complains about the Am=
ericans sending a "secretary of state". The world adjusts to different name=
s. I don't see an issue here.

Yoav


From nobody Sun Feb 16 07:58:58 2014
Return-Path: <jmamodio@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 7CA1F1A03FF for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 07:58:56 -0800 (PST)
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 n_b8n5plOtB0 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 07:58:54 -0800 (PST)
Received: from mail-vc0-x22d.google.com (mail-vc0-x22d.google.com [IPv6:2607:f8b0:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 759E31A03FD for <ietf@ietf.org>; Sun, 16 Feb 2014 07:58:54 -0800 (PST)
Received: by mail-vc0-f173.google.com with SMTP id ld13so11018832vcb.32 for <ietf@ietf.org>; Sun, 16 Feb 2014 07:58:52 -0800 (PST)
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=UyIXLbSt9I6xW/QhC/x5LQIJ2EWpF2tuThCBI+blDyI=; b=lir2a+lDqBmCKLfos4UY5edfFJ1P1Z/5qSL6KtZesQ2zwuZlx1CK24imP5KfkSZ8PM ULDD5LPCxxzA1CE95MvAmH14CuK5a2SCNcdViHMT9XZL5QzV0fZ0CBVDyXbNY1cM644K wUscgOhZFl/uiiLHXaiS1eU364l/qJIzzeNLbAs8JdrkDcvYTlEgBO9dB7fHD59H+qbN fw/Wt/gbUUQ6wJXhpbEcngHk5egOmRCJH+qAkHqG+ds7+NFWLSadLSQ03q3DHre8/hAC kL0Ob/rdefm3mf3T1f1mJ728GZpBLdAAfgb8H7Wj9n+a60lOGAgWLtLGGE7RF7+XHeE1 +fdg==
MIME-Version: 1.0
X-Received: by 10.221.53.194 with SMTP id vr2mr1252vcb.41.1392566331795; Sun, 16 Feb 2014 07:58:51 -0800 (PST)
Received: by 10.58.218.226 with HTTP; Sun, 16 Feb 2014 07:58:51 -0800 (PST)
In-Reply-To: <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com>
Date: Sun, 16 Feb 2014 09:58:51 -0600
Message-ID: <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com>
Subject: Re: Internet organisations coordination meeting
From: Jorge Amodio <jmamodio@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11333dfa886e7a04f2881dd8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JaGZmzj6GkuB0suDqbtBWyRdQ_Q
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: Sun, 16 Feb 2014 15:58:56 -0000

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

I agree that "spokesperson" is not either the appropriate term. And leader
is far far away to be representative of their roles and positions.

True that on their role they "lead" the organizations they are involved
with but the Internet community does not follow them as *leaders*,
particularly the CEOs of some organizations such as ICANN, ARIN, etc, that
are just paid employees to play a specific executive role.

I'm really starting to dislike this effort of reverting the bottom-up
process by a group that is starting to behave like a dictatorial junta
making public statements that can be considered or interpreted as
representative of the Internet community and particular organizations such
as IETF.

They are no spokesperson, nor leaders, just they are what they are the CEO
of ICANN, the Chair of IETF, the CEO of ARIN, etc.


My .02
Jorge



On Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <ted.lemon@nominum.com> wrote:

> Folks, as John Klensin said, the reason we do not say "spokesperson" is
> that our leadership do not speak for us.   We only speak as a group through
> the consensus process.   So the term "spokesperson" is simply inaccurate.
>
> The term "leader" makes sense as a generic because there were a number of
> organizations, with different leadership structures, some not involving the
> same consensus process that exists in the IETF.   So we couldn't for
> example say "chair," because that term wouldn't apply to all the people who
> signed the statement.
>
> I realize that the term "leader" has its own set of connotations, but I
> don't know of a better word to use.   There is no word that we could use
> that would convey to someone who is not already familiar with IETF process
> what we mean.   Representative is no good for the same reason spokesperson
> is no good.   Avatar doesn't really work either.
>
> I think it's better to just accept that the language is imprecise, and
> think carefully about what is that we might be objecting to, and whether
> the objection _really_ makes sense in the context.   I guess there's about
> zero chance that this won't get discussed to death, and that's fine, but I
> don't think there's a knob to turn here.
>
>

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

<div dir=3D"ltr"><br><div>I agree that &quot;spokesperson&quot; is not eith=
er the appropriate term. And leader is far far away to be representative of=
 their roles and positions.</div><div><br></div><div>True that on their rol=
e they &quot;lead&quot; the organizations they are involved with but the In=
ternet community does not follow them as *leaders*, particularly the CEOs o=
f some organizations such as ICANN, ARIN, etc, that are just paid employees=
 to play a specific executive role.</div>
<div><br></div><div>I&#39;m really starting to dislike this effort of rever=
ting the bottom-up process by a group that is starting to behave like a dic=
tatorial junta making public statements that can be considered or interpret=
ed as representative of the Internet community and particular organizations=
 such as IETF.</div>
<div><br></div><div>They are no spokesperson, nor leaders, just they are wh=
at they are the CEO of ICANN, the Chair of IETF, the CEO of ARIN, etc.</div=
><div><br></div><div><br></div><div>My .02</div><div>Jorge</div><div><br>
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"=
mailto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.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">Folks, as John Klensin said, the reason we d=
o not say &quot;spokesperson&quot; is that our leadership do not speak for =
us. =A0 We only speak as a group through the consensus process. =A0 So the =
term &quot;spokesperson&quot; is simply inaccurate.<br>

<br>
The term &quot;leader&quot; makes sense as a generic because there were a n=
umber of organizations, with different leadership structures, some not invo=
lving the same consensus process that exists in the IETF. =A0 So we couldn&=
#39;t for example say &quot;chair,&quot; because that term wouldn&#39;t app=
ly to all the people who signed the statement.<br>

<br>
I realize that the term &quot;leader&quot; has its own set of connotations,=
 but I don&#39;t know of a better word to use. =A0 There is no word that we=
 could use that would convey to someone who is not already familiar with IE=
TF process what we mean. =A0 Representative is no good for the same reason =
spokesperson is no good. =A0 Avatar doesn&#39;t really work either.<br>

<br>
I think it&#39;s better to just accept that the language is imprecise, and =
think carefully about what is that we might be objecting to, and whether th=
e objection _really_ makes sense in the context. =A0 I guess there&#39;s ab=
out zero chance that this won&#39;t get discussed to death, and that&#39;s =
fine, but I don&#39;t think there&#39;s a knob to turn here.<br>

<br>
</blockquote></div><br></div>

--001a11333dfa886e7a04f2881dd8--


From nobody Sun Feb 16 12:38:39 2014
Return-Path: <jcurran@istaff.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 EE3E91A0404 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 12:38:37 -0800 (PST)
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, 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 xo97EJStYsf7 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 12:38:35 -0800 (PST)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) by ietfa.amsl.com (Postfix) with ESMTP id DCD461A0289 for <ietf@ietf.org>; Sun, 16 Feb 2014 12:38:34 -0800 (PST)
Received: from pool-108-45-30-69.washdc.fios.verizon.net ([108.45.30.69] helo=[192.168.1.12]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1WF8Tv-000GbN-Hj; Sun, 16 Feb 2014 20:38:32 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 108.45.30.69
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX199ZOux2T42J+erR/nuQ5jD
Content-Type: multipart/alternative; boundary="Apple-Mail=_75897CB2-DB26-43B3-ADBD-B05772130CDF"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Internet organisations coordination meeting
From: John Curran <jcurran@istaff.org>
In-Reply-To: <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com>
Date: Sun, 16 Feb 2014 15:38:25 -0500
Message-Id: <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com>
To: Jorge Amodio <jmamodio@gmail.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8S61617zg8awB0WqCqjvTNIDBDg
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: Sun, 16 Feb 2014 20:38:38 -0000

--Apple-Mail=_75897CB2-DB26-43B3-ADBD-B05772130CDF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Jorge -=20
=20
    This particular group of folks gathered and received updates on =
various activities=20
    going on... e.g.  Jari and Russ spoke of perpass.  It is a =
coordinating function; so=20
    we know about major initiatives going on and can support and/or =
avoid conflicts=20
    as appropriate.

    The only reason for the post-meeting statements (in my view) is =
simply because=20
    people were unaware that these periodic gatherings were going on, =
and indicated
    that we should be make such more visible.

    Note also that there quite a bit of focus on making sure the most =
recent statement
    simply said what happened, i.e.  a gathering of folks received a =
series of updates=20
    from each other on a list of topics of potentially mutual interest. =20=


    As a result, I now realize that W3C is having its 20th anniversary; =
that ICANN's
    various strategy panels have been meeting, and that the "Brazil =
meeting" is now
    know as  =93Netmundial=94 and has its own website =
<http://netmundial.br>.   I don't=20
    really know what the other leaders (for lack of a better term) took =
away, but=20
    would hope that Jari, Russ, etc. found it useful context and =
background for their
    IETF efforts.    I guess that one option would be for the "leaders" =
from the IETF
    community not to attend such gatherings, but that seems to be a =
rather extreme
    response to take due to lack of a better term than "leader" (and one =
hopes it is
    unnecessary so long as care is taken to make nothing more of the =
meetings than
    what they are - a gathering of folks hearing updates so we can =
better coordinate)

FYI,
/John

On Feb 16, 2014, at 10:58 AM, Jorge Amodio <jmamodio@gmail.com> wrote:

>=20
> I agree that "spokesperson" is not either the appropriate term. And =
leader is far far away to be representative of their roles and =
positions.
>=20
> True that on their role they "lead" the organizations they are =
involved with but the Internet community does not follow them as =
*leaders*, particularly the CEOs of some organizations such as ICANN, =
ARIN, etc, that are just paid employees to play a specific executive =
role.
>=20
> I'm really starting to dislike this effort of reverting the bottom-up =
process by a group that is starting to behave like a dictatorial junta =
making public statements that can be considered or interpreted as =
representative of the Internet community and particular organizations =
such as IETF.
>=20
> They are no spokesperson, nor leaders, just they are what they are the =
CEO of ICANN, the Chair of IETF, the CEO of ARIN, etc.
>=20
>=20
> My .02
> Jorge
>=20
>=20
>=20
> On Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <ted.lemon@nominum.com> =
wrote:
> Folks, as John Klensin said, the reason we do not say "spokesperson" =
is that our leadership do not speak for us.   We only speak as a group =
through the consensus process.   So the term "spokesperson" is simply =
inaccurate.
>=20
> The term "leader" makes sense as a generic because there were a number =
of organizations, with different leadership structures, some not =
involving the same consensus process that exists in the IETF.   So we =
couldn't for example say "chair," because that term wouldn't apply to =
all the people who signed the statement.
>=20
> I realize that the term "leader" has its own set of connotations, but =
I don't know of a better word to use.   There is no word that we could =
use that would convey to someone who is not already familiar with IETF =
process what we mean.   Representative is no good for the same reason =
spokesperson is no good.   Avatar doesn't really work either.
>=20
> I think it's better to just accept that the language is imprecise, and =
think carefully about what is that we might be objecting to, and whether =
the objection _really_ makes sense in the context.   I guess there's =
about zero chance that this won't get discussed to death, and that's =
fine, but I don't think there's a knob to turn here.
>=20
>=20


--Apple-Mail=_75897CB2-DB26-43B3-ADBD-B05772130CDF
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">
<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;"><div>Jorge -&nbsp;</div><div>&nbsp;</div><div>&nbsp; =
&nbsp; This particular group of folks gathered and received updates on =
various activities&nbsp;</div><div>&nbsp; &nbsp; going on... e.g. =
&nbsp;Jari and Russ spoke of perpass. &nbsp;It is a coordinating =
function; so&nbsp;</div><div>&nbsp; &nbsp; we know about major =
initiatives going on and can support and/or avoid =
conflicts&nbsp;</div><div>&nbsp; &nbsp; as =
appropriate.</div><div><br></div><div>&nbsp; &nbsp; The only reason for =
the post-meeting statements (in my view) is simply =
because&nbsp;</div><div>&nbsp; &nbsp; people were unaware that these =
periodic gatherings were going on, and indicated</div><div>&nbsp; &nbsp; =
that we should be make such more =
visible.</div><div><br></div><div>&nbsp; &nbsp; Note also that there =
quite a bit of focus on making sure the most recent =
statement</div><div>&nbsp; &nbsp; simply said what happened, i.e. =
&nbsp;a gathering of folks received a series of =
updates&nbsp;</div><div>&nbsp; &nbsp; from each other on a list of =
topics of potentially mutual interest. =
&nbsp;</div><div><br></div><div>&nbsp; &nbsp; As a result, I now realize =
that W3C is having its 20th anniversary; that ICANN's</div><div>&nbsp; =
&nbsp; various strategy panels have been meeting, and that the "Brazil =
meeting" is now</div><div>&nbsp; &nbsp; know as &nbsp;=93Netmundial=94 =
and has its own website &lt;<a =
href=3D"http://netmundial.br">http://netmundial.br</a>&gt;. &nbsp; I =
don't&nbsp;</div><div>&nbsp; &nbsp; really know what the other leaders =
(for lack of a better term) took away, but&nbsp;</div><div>&nbsp; &nbsp; =
would hope that Jari, Russ, etc. found it useful context and background =
for their</div><div>&nbsp; &nbsp; IETF efforts. &nbsp; &nbsp;I guess =
that one option would be for the "leaders" from the =
IETF</div><div>&nbsp; &nbsp; community not to attend such gatherings, =
but that seems to be a rather extreme</div><div>&nbsp; &nbsp; response =
to take due to lack of a better term than "leader" (and one hopes it =
is</div><div>&nbsp; &nbsp; unnecessary so long as care is taken to make =
nothing more of the meetings than</div><div>&nbsp; &nbsp; what they are =
- a gathering of folks hearing updates so we can better =
coordinate)</div><div><br></div><div>FYI,</div><div>/John</div><div><br></=
div>On Feb 16, 2014, at 10:58 AM, Jorge Amodio &lt;<a =
href=3D"mailto:jmamodio@gmail.com">jmamodio@gmail.com</a>&gt; =
wrote:<br><div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><br><div>I agree that "spokesperson" is =
not either the appropriate term. And leader is far far away to be =
representative of their roles and =
positions.</div><div><br></div><div>True that on their role they "lead" =
the organizations they are involved with but the Internet community does =
not follow them as *leaders*, particularly the CEOs of some =
organizations such as ICANN, ARIN, etc, that are just paid employees to =
play a specific executive role.</div>
<div><br></div><div>I'm really starting to dislike this effort of =
reverting the bottom-up process by a group that is starting to behave =
like a dictatorial junta making public statements that can be considered =
or interpreted as representative of the Internet community and =
particular organizations such as IETF.</div>
<div><br></div><div>They are no spokesperson, nor leaders, just they are =
what they are the CEO of ICANN, the Chair of IETF, the CEO of ARIN, =
etc.</div><div><br></div><div><br></div><div>My =
.02</div><div>Jorge</div><div><br>
</div></div><div class=3D"gmail_extra"><br><br><div =
class=3D"gmail_quote">On Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <span =
dir=3D"ltr">&lt;<a href=3D"mailto:ted.lemon@nominum.com" =
target=3D"_blank">ted.lemon@nominum.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">Folks, as John Klensin =
said, the reason we do not say "spokesperson" is that our leadership do =
not speak for us. &nbsp; We only speak as a group through the consensus =
process. &nbsp; So the term "spokesperson" is simply inaccurate.<br>

<br>
The term "leader" makes sense as a generic because there were a number =
of organizations, with different leadership structures, some not =
involving the same consensus process that exists in the IETF. &nbsp; So =
we couldn't for example say "chair," because that term wouldn't apply to =
all the people who signed the statement.<br>

<br>
I realize that the term "leader" has its own set of connotations, but I =
don't know of a better word to use. &nbsp; There is no word that we =
could use that would convey to someone who is not already familiar with =
IETF process what we mean. &nbsp; Representative is no good for the same =
reason spokesperson is no good. &nbsp; Avatar doesn't really work =
either.<br>

<br>
I think it's better to just accept that the language is imprecise, and =
think carefully about what is that we might be objecting to, and whether =
the objection _really_ makes sense in the context. &nbsp; I guess =
there's about zero chance that this won't get discussed to death, and =
that's fine, but I don't think there's a knob to turn here.<br>

<br>
</blockquote></div><br></div>
</blockquote></div><br></body></html>=

--Apple-Mail=_75897CB2-DB26-43B3-ADBD-B05772130CDF--


From nobody Sun Feb 16 13:08:47 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 C216A1A02C1 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 13:08:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.466
X-Spam-Level: *
X-Spam-Status: No, score=1.466 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, 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 1pG-eGzvTJv2 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 13:08:44 -0800 (PST)
Received: from atl4mhob05.myregisteredsite.com (atl4mhob05.myregisteredsite.com [209.17.115.43]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1101A0068 for <ietf@ietf.org>; Sun, 16 Feb 2014 13:08:44 -0800 (PST)
Received: from mailpod.hostingplatform.com ([10.30.71.209]) by atl4mhob05.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id s1GL8eSA001288 for <ietf@ietf.org>; Sun, 16 Feb 2014 16:08:40 -0500
Received: (qmail 28708 invoked by uid 0); 16 Feb 2014 21:08:40 -0000
X-TCPREMOTEIP: 172.56.2.0
X-Authenticated-UID: avri@ella.com
Received: from unknown (HELO ?26.219.166.148?) (avri@ella.com@172.56.2.0) by 0 with ESMTPA; 16 Feb 2014 21:08:40 -0000
Date: Sun, 16 Feb 2014 16:08:37 -0500
Subject: Re: Internet organisations coordination meeting
Message-ID: <xkajdui3my5n236ee625q1k8.1392584917507@email.android.com>
Importance: normal
From: avri <avri@acm.org>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.android.email_10064279276850"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hjLOKSMKH1p38ysb8IawNlZyzyQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Feb 2014 21:08:46 -0000

----_com.android.email_10064279276850
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

QWx0aG91Z2ggSSBoYXZlIGEgcGVyc29uYWwgYXZlcnNpb24gwqB0byB0aGUgdGVybSBsZWFkZXIs
IEkgdGhpbmsgaXQgYSBnb29kIHRoaW5nIHRoYXQgYWxsIHlvdSBsZWFkZXIvY29vcmRpbmF0b3Iv
c3Bva2VycGVyc29ueSB0eXBlIGZvbGtzIGRvIG1lZXQgYW5kIGRvIHJlcG9ydCBvbiB5b3VyIG1l
ZXRpbmdzLgoKCmF2cmkKClNlbnQgZnJvbSBhIFQtTW9iaWxlIDRHIExURSBEZXZpY2U=

----_com.android.email_10064279276850
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keSA+PGRpdj5BbHRob3VnaCBJIGhhdmUg
YSBwZXJzb25hbCBhdmVyc2lvbiAmbmJzcDt0byB0aGUgdGVybSBsZWFkZXIsIEkgdGhpbmsgaXQg
YSBnb29kIHRoaW5nIHRoYXQgYWxsIHlvdSBsZWFkZXIvY29vcmRpbmF0b3Ivc3Bva2VycGVyc29u
eSB0eXBlIGZvbGtzIGRvIG1lZXQgYW5kIGRvIHJlcG9ydCBvbiB5b3VyIG1lZXRpbmdzLjwvZGl2
PjxkaXY+PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZTo3NSUi
PmF2cmk8L2Rpdj48ZGl2IHN0eWxlPSJmb250LXNpemU6NzUlIj48YnI+PC9kaXY+PGRpdiBzdHls
ZT0iZm9udC1zaXplOjc1JSI+U2VudCBmcm9tIGEgVC1Nb2JpbGUgNEcgTFRFIERldmljZTwvZGl2
PjwvYm9keT48L2h0bWw+

----_com.android.email_10064279276850--



From nobody Sun Feb 16 13:39:37 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 A60971A0112 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 13:39:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eHDbV40gO_cB for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 13:39:33 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4F1161A0045 for <ietf@ietf.org>; Sun, 16 Feb 2014 13:39:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 79EA12CEB6; Sun, 16 Feb 2014 23:39:29 +0200 (EET)
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 dg7bzeUio4Qd; Sun, 16 Feb 2014 23:39:29 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 073CE2CC61; Sun, 16 Feb 2014 23:39:28 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Internet organisations coordination meeting
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <91B14EDC39525BDF0B2B531E@JcK-HP8200.jck.com>
Date: Sun, 16 Feb 2014 23:39:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <117AA458-ACD3-4078-9798-393F881154B1@piuha.net>
References: <91B14EDC39525BDF0B2B531E@JcK-HP8200.jck.com>
To: John C Klensin <john-ietf@jck.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/sGu3I2U010ZgzVD0B0A4QE_LurM
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: Sun, 16 Feb 2014 21:39:35 -0000

> If we come to the conclusion that our "leaders" are not saying
> what we want them to say (with or without qualifications about
> who they are speaking for), then the correct remedies =85

Right. This is why the note said, among other thing, that "there is a =
lot of work happening in our respective communities, driven by the =
participants and handled with the usual community processes".

(By the way, I do get a lot of feedback on what I say in various places. =
Please keep that feedback coming. It is helpful.)

Jari


From nobody Sun Feb 16 13:44:14 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 6DA8A1A0045 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 13:44:12 -0800 (PST)
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 g9JeiuerYFs8 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 13:44:10 -0800 (PST)
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 5AF4F1A021E for <ietf@ietf.org>; Sun, 16 Feb 2014 13:44:10 -0800 (PST)
Received: by mail-pd0-f174.google.com with SMTP id z10so13919583pdj.5 for <ietf@ietf.org>; Sun, 16 Feb 2014 13:44:08 -0800 (PST)
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=OHK2U7/JKpNHIK65e24z7I2OoWgIAuoyHroiy0Yl0uM=; b=e1UresqQFF7g6bDNDiW/2uRIMgQneUwK4DIjwS96XKEs1h4xfHxv4tX4X4LRgjMHOk ANnq7Rs5X0Nn25x16p2qYe9vCj9a0JgrCHiq5dawx66vTDp8hA/SDJKii52+EVmwLnJh 4tgvuEbKt6e2eZyjtjKN/XSVfXVib0mwvVzeq7mpXivghqliDQJYHmxiUVccZAx7Rg7n 9TE24qB5t18sdR3H6sZUvlwjaGnKi/NRVFjONBR4QLs9hKR72nPvAIH6Y1cYa949OInj w8P7GdxGgm+JW+WznqTkJtw6R2+qnEJbzeN03ACAu1EfmIzlQ2S4WzG2D4SRbTLwxOOq qZeQ==
X-Received: by 10.66.136.229 with SMTP id qd5mr22789094pab.118.1392587048184;  Sun, 16 Feb 2014 13:44:08 -0800 (PST)
Received: from [192.168.178.23] (22.200.69.111.dynamic.snap.net.nz. [111.69.200.22]) by mx.google.com with ESMTPSA id rb6sm38910694pbb.41.2014.02.16.13.44.06 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Feb 2014 13:44:07 -0800 (PST)
Message-ID: <53013126.2060608@gmail.com>
Date: Mon, 17 Feb 2014 10:44:06 +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 Curran <jcurran@istaff.org>
Subject: Re: Internet organisations coordination meeting
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com> <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org>
In-Reply-To: <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iT4zdt3wOROdvrHsBJ9pgveoSOQ
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: Sun, 16 Feb 2014 21:44:12 -0000

On 17/02/2014 09:38, John Curran wrote:
> Jorge -=20
> =20
>     This particular group of folks gathered and received updates on var=
ious activities=20
>     going on... e.g.  Jari and Russ spoke of perpass.  It is a coordina=
ting function; so=20
>     we know about major initiatives going on and can support and/or avo=
id conflicts=20
>     as appropriate.
>=20
>     The only reason for the post-meeting statements (in my view) is sim=
ply because=20
>     people were unaware that these periodic gatherings were going on, a=
nd indicated
>     that we should be make such more visible.
>=20
>     Note also that there quite a bit of focus on making sure the most r=
ecent statement
>     simply said what happened, i.e.  a gathering of folks received a se=
ries of updates=20
>     from each other on a list of topics of potentially mutual interest.=
 =20
>=20
>     As a result, I now realize that W3C is having its 20th anniversary;=
 that ICANN's
>     various strategy panels have been meeting, and that the "Brazil mee=
ting" is now
>     know as  =E2=80=9CNetmundial=E2=80=9D and has its own website <http=
://netmundial.br>.   I don't=20
>     really know what the other leaders (for lack of a better term) took=
 away, but=20
>     would hope that Jari, Russ, etc. found it useful context and backgr=
ound for their
>     IETF efforts.    I guess that one option would be for the "leaders"=
 from the IETF
>     community not to attend such gatherings, but that seems to be a rat=
her extreme
>     response to take due to lack of a better term than "leader" (and on=
e hopes it is
>     unnecessary so long as care is taken to make nothing more of the me=
etings than
>     what they are - a gathering of folks hearing updates so we can bett=
er coordinate)

And to be clear, I'm very happy that our Chairs attend such meetings
and report back to the community. I was only quibbling about a choice
of words, and I'm sorry to have obscured the real value of the meeting.

    Brian


From nobody Sun Feb 16 14:39:01 2014
Return-Path: <jmamodio@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 584CE1A02D9 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 14:38:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DIET_1=0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vUdZHoL8HGi5 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 14:38:57 -0800 (PST)
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 D09961A02CA for <ietf@ietf.org>; Sun, 16 Feb 2014 14:38:56 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id vb8so16373287obc.31 for <ietf@ietf.org>; Sun, 16 Feb 2014 14:38:54 -0800 (PST)
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=NoQ0MkO3uYujf0KpfISPRV0Q0lHSvUPENTF2kNNnQU8=; b=oy/tUSewg2Lwf1Iv6+4ZVufHxwviSSeLbT8S94jt29OMKduLfXinSKZVGs7IIL3ECt Q1WRaccMgFbzHHkbvC7kCzUGnJno+qo4Rx94L5htg6VhRg13e4fU5Q3OEOIw8z1wBimI m/vUjxppecT3m7yKwkGJ3gM/4DTq9mkjvLyxMw6s+uGlQ7btDnGj2Qft2BTa+Xj6Ieqk owZa42WgD102xu28SSy+d8fNt7r1gRDZhLjyn+ZdyILysKD+5G01tHXki4rbl3aTcH1g rL7kXuqUM04DWsoXcD3BYhwtvTRwJCOkx94uzlSz83vRhZ+VHHw3uJDPSgjFiTWSYHAf 7rgw==
X-Received: by 10.60.63.242 with SMTP id j18mr18043423oes.33.1392590334372; Sun, 16 Feb 2014 14:38:54 -0800 (PST)
Received: from [10.0.2.169] (cpe-67-10-135-163.satx.res.rr.com. [67.10.135.163]) by mx.google.com with ESMTPSA id b2sm92210582oed.7.2014.02.16.14.38.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 16 Feb 2014 14:38:53 -0800 (PST)
Content-Type: multipart/alternative; boundary=Apple-Mail-9F5333ED-3AAE-464F-82EA-15AB112F11E6
Mime-Version: 1.0 (1.0)
Subject: Re: Internet organisations coordination meeting
From: Jorge Amodio <jmamodio@gmail.com>
X-Mailer: iPad Mail (11B554a)
In-Reply-To: <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org>
Date: Sun, 16 Feb 2014 16:38:52 -0600
Content-Transfer-Encoding: 7bit
Message-Id: <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com> <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org>
To: John Curran <jcurran@istaff.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/NE5sKYEaqJhGVigIf2pEPahBjlw
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: Sun, 16 Feb 2014 22:38:59 -0000

--Apple-Mail-9F5333ED-3AAE-464F-82EA-15AB112F11E6
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable


The issue is not participation, engagement and cooperation which I consider v=
ital for a healthy and continuously development of the Internet. The issue I=
MHO is the tag labeling of a group of individuals that perform on an executi=
ve role and how the labeling and some statements are perceived and interpret=
ed particularly by mainstream media in a context where Internet Governance (=
widely misinterpreted by itself ) is on the forefront nowadays.

You may not see it because you are in the midst of it. My concern is with th=
e "I* Leaders" label and how and where what you say can be easily taken out c=
ontext and grossly misinterpreted without exercising some restraint and bett=
er choice of words.=20

I'm not against Jari and Russ participation and having them share what's goi=
ng on at IETF and explore opportunities for more and better cooperation.

I'd strongly recommend to get rid of the "I* Leaders" moniker.

Regards
-Jorge

> On Feb 16, 2014, at 2:38 PM, John Curran <jcurran@istaff.org> wrote:
>=20
> Jorge -=20
> =20
>     This particular group of folks gathered and received updates on variou=
s activities=20
>     going on... e.g.  Jari and Russ spoke of perpass.  It is a coordinatin=
g function; so=20
>     we know about major initiatives going on and can support and/or avoid c=
onflicts=20
>     as appropriate.
>=20
>     The only reason for the post-meeting statements (in my view) is simply=
 because=20
>     people were unaware that these periodic gatherings were going on, and i=
ndicated
>     that we should be make such more visible.
>=20
>     Note also that there quite a bit of focus on making sure the most rece=
nt statement
>     simply said what happened, i.e.  a gathering of folks received a serie=
s of updates=20
>     from each other on a list of topics of potentially mutual interest. =20=

>=20
>     As a result, I now realize that W3C is having its 20th anniversary; th=
at ICANN's
>     various strategy panels have been meeting, and that the "Brazil meetin=
g" is now
>     know as  =E2=80=9CNetmundial=E2=80=9D and has its own website <http://=
netmundial.br>.   I don't=20
>     really know what the other leaders (for lack of a better term) took aw=
ay, but=20
>     would hope that Jari, Russ, etc. found it useful context and backgroun=
d for their
>     IETF efforts.    I guess that one option would be for the "leaders" fr=
om the IETF
>     community not to attend such gatherings, but that seems to be a rather=
 extreme
>     response to take due to lack of a better term than "leader" (and one h=
opes it is
>     unnecessary so long as care is taken to make nothing more of the meeti=
ngs than
>     what they are - a gathering of folks hearing updates so we can better c=
oordinate)
>=20
> FYI,
> /John
>=20
> On Feb 16, 2014, at 10:58 AM, Jorge Amodio <jmamodio@gmail.com> wrote:
>=20
>>=20
>> I agree that "spokesperson" is not either the appropriate term. And leade=
r is far far away to be representative of their roles and positions.
>>=20
>> True that on their role they "lead" the organizations they are involved w=
ith but the Internet community does not follow them as *leaders*, particular=
ly the CEOs of some organizations such as ICANN, ARIN, etc, that are just pa=
id employees to play a specific executive role.
>>=20
>> I'm really starting to dislike this effort of reverting the bottom-up pro=
cess by a group that is starting to behave like a dictatorial junta making p=
ublic statements that can be considered or interpreted as representative of t=
he Internet community and particular organizations such as IETF.
>>=20
>> They are no spokesperson, nor leaders, just they are what they are the CE=
O of ICANN, the Chair of IETF, the CEO of ARIN, etc.
>>=20
>>=20
>> My .02
>> Jorge
>>=20
>>=20
>>=20
>>> On Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <ted.lemon@nominum.com> wrote=
:
>>> Folks, as John Klensin said, the reason we do not say "spokesperson" is t=
hat our leadership do not speak for us.   We only speak as a group through t=
he consensus process.   So the term "spokesperson" is simply inaccurate.
>>>=20
>>> The term "leader" makes sense as a generic because there were a number o=
f organizations, with different leadership structures, some not involving th=
e same consensus process that exists in the IETF.   So we couldn't for examp=
le say "chair," because that term wouldn't apply to all the people who signe=
d the statement.
>>>=20
>>> I realize that the term "leader" has its own set of connotations, but I d=
on't know of a better word to use.   There is no word that we could use that=
 would convey to someone who is not already familiar with IETF process what w=
e mean.   Representative is no good for the same reason spokesperson is no g=
ood.   Avatar doesn't really work either.
>>>=20
>>> I think it's better to just accept that the language is imprecise, and t=
hink carefully about what is that we might be objecting to, and whether the o=
bjection _really_ makes sense in the context.   I guess there's about zero c=
hance that this won't get discussed to death, and that's fine, but I don't t=
hink there's a knob to turn here.
>=20

--Apple-Mail-9F5333ED-3AAE-464F-82EA-15AB112F11E6
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><span></span></div><div><div><br></div=
><div>The issue is not participation, engagement and cooperation which I con=
sider vital for a healthy and continuously development of the Internet. The i=
ssue IMHO is the tag labeling of a group of individuals that perform on an e=
xecutive role and how the labeling and some statements are perceived and int=
erpreted particularly by mainstream media in a context where Internet Govern=
ance (widely misinterpreted by itself ) is on the forefront nowadays.</div><=
div><br></div><div>You may not see it because you are in the midst of it. My=
 concern is with the "I* Leaders" label and how and where what you say can b=
e easily taken out context and grossly misinterpreted without exercising som=
e restraint and better choice of words.&nbsp;<br><br>I'm not against Jari an=
d Russ participation and having them share what's going on at IETF and explo=
re opportunities for more and better cooperation.</div><div><br></div><div>I=
'd strongly recommend to get rid of the "I* Leaders" moniker.</div><div><br>=
</div><div>Regards</div><div>-Jorge</div><div><br>On Feb 16, 2014, at 2:38 P=
M, John Curran &lt;<a href=3D"mailto:jcurran@istaff.org">jcurran@istaff.org<=
/a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><meta http-equiv=3D=
"Content-Type" content=3D"text/html charset=3Dwindows-1252">
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-12=
52"><div>Jorge -&nbsp;</div><div>&nbsp;</div><div>&nbsp; &nbsp; This particu=
lar group of folks gathered and received updates on various activities&nbsp;=
</div><div>&nbsp; &nbsp; going on... e.g. &nbsp;Jari and Russ spoke of perpa=
ss. &nbsp;It is a coordinating function; so&nbsp;</div><div>&nbsp; &nbsp; we=
 know about major initiatives going on and can support and/or avoid conflict=
s&nbsp;</div><div>&nbsp; &nbsp; as appropriate.</div><div><br></div><div>&nb=
sp; &nbsp; The only reason for the post-meeting statements (in my view) is s=
imply because&nbsp;</div><div>&nbsp; &nbsp; people were unaware that these p=
eriodic gatherings were going on, and indicated</div><div>&nbsp; &nbsp; that=
 we should be make such more visible.</div><div><br></div><div>&nbsp; &nbsp;=
 Note also that there quite a bit of focus on making sure the most recent st=
atement</div><div>&nbsp; &nbsp; simply said what happened, i.e. &nbsp;a gath=
ering of folks received a series of updates&nbsp;</div><div>&nbsp; &nbsp; fr=
om each other on a list of topics of potentially mutual interest. &nbsp;</di=
v><div><br></div><div>&nbsp; &nbsp; As a result, I now realize that W3C is h=
aving its 20th anniversary; that ICANN's</div><div>&nbsp; &nbsp; various str=
ategy panels have been meeting, and that the "Brazil meeting" is now</div><d=
iv>&nbsp; &nbsp; know as &nbsp;=E2=80=9CNetmundial=E2=80=9D and has its own w=
ebsite &lt;<a href=3D"http://netmundial.br">http://netmundial.br</a>&gt;. &n=
bsp; I don't&nbsp;</div><div>&nbsp; &nbsp; really know what the other leader=
s (for lack of a better term) took away, but&nbsp;</div><div>&nbsp; &nbsp; w=
ould hope that Jari, Russ, etc. found it useful context and background for t=
heir</div><div>&nbsp; &nbsp; IETF efforts. &nbsp; &nbsp;I guess that one opt=
ion would be for the "leaders" from the IETF</div><div>&nbsp; &nbsp; communi=
ty not to attend such gatherings, but that seems to be a rather extreme</div=
><div>&nbsp; &nbsp; response to take due to lack of a better term than "lead=
er" (and one hopes it is</div><div>&nbsp; &nbsp; unnecessary so long as care=
 is taken to make nothing more of the meetings than</div><div>&nbsp; &nbsp; w=
hat they are - a gathering of folks hearing updates so we can better coordin=
ate)</div><div><br></div><div>FYI,</div><div>/John</div><div><br></div>On Fe=
b 16, 2014, at 10:58 AM, Jorge Amodio &lt;<a href=3D"mailto:jmamodio@gmail.c=
om">jmamodio@gmail.com</a>&gt; wrote:<br><div><br class=3D"Apple-interchange=
-newline"><blockquote type=3D"cite"><div dir=3D"ltr"><br><div>I agree that "=
spokesperson" is not either the appropriate term. And leader is far far away=
 to be representative of their roles and positions.</div><div><br></div><div=
>True that on their role they "lead" the organizations they are involved wit=
h but the Internet community does not follow them as *leaders*, particularly=
 the CEOs of some organizations such as ICANN, ARIN, etc, that are just paid=
 employees to play a specific executive role.</div>
<div><br></div><div>I'm really starting to dislike this effort of reverting t=
he bottom-up process by a group that is starting to behave like a dictatoria=
l junta making public statements that can be considered or interpreted as re=
presentative of the Internet community and particular organizations such as I=
ETF.</div>
<div><br></div><div>They are no spokesperson, nor leaders, just they are wha=
t they are the CEO of ICANN, the Chair of IETF, the CEO of ARIN, etc.</div><=
div><br></div><div><br></div><div>My .02</div><div>Jorge</div><div><br>
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On=
 Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.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">Folks, as John Klensin said, the reason we do n=
ot say "spokesperson" is that our leadership do not speak for us. &nbsp; We o=
nly speak as a group through the consensus process. &nbsp; So the term "spok=
esperson" is simply inaccurate.<br>

<br>
The term "leader" makes sense as a generic because there were a number of or=
ganizations, with different leadership structures, some not involving the sa=
me consensus process that exists in the IETF. &nbsp; So we couldn't for exam=
ple say "chair," because that term wouldn't apply to all the people who sign=
ed the statement.<br>

<br>
I realize that the term "leader" has its own set of connotations, but I don'=
t know of a better word to use. &nbsp; There is no word that we could use th=
at would convey to someone who is not already familiar with IETF process wha=
t we mean. &nbsp; Representative is no good for the same reason spokesperson=
 is no good. &nbsp; Avatar doesn't really work either.<br>

<br>
I think it's better to just accept that the language is imprecise, and think=
 carefully about what is that we might be objecting to, and whether the obje=
ction _really_ makes sense in the context. &nbsp; I guess there's about zero=
 chance that this won't get discussed to death, and that's fine, but I don't=
 think there's a knob to turn here.<br>

<br>
</blockquote></div><br></div>
</blockquote></div><br></div></blockquote></div></body></html>=

--Apple-Mail-9F5333ED-3AAE-464F-82EA-15AB112F11E6--


From nobody Sun Feb 16 15:11:40 2014
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A23E1A02FA for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 15:11:38 -0800 (PST)
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, DIET_1=0.001, 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 uuqY1f2XYIVV for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 15:11:26 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id B411E1A0421 for <ietf@ietf.org>; Sun, 16 Feb 2014 15:11:25 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id B77F01A3C53; Sun, 16 Feb 2014 15:11:23 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-64.clppva.east.verizon.net [70.106.135.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id B79051A3C51; Sun, 16 Feb 2014 15:11:22 -0800 (PST)
Message-ID: <53014599.2070100@joelhalpern.com>
Date: Sun, 16 Feb 2014 18:11:21 -0500
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Jorge Amodio <jmamodio@gmail.com>, John Curran <jcurran@istaff.org>
Subject: Re: Internet organisations coordination meeting
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com> <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org> <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com>
In-Reply-To: <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/dP4O6nen2owpNsgQV7AMSgErmmg
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: Sun, 16 Feb 2014 23:11:39 -0000

Actually Jorge, I would have to disagree with your discription.  Neither 
the IAB Chair nor the IESG Chair are executive roles.  They are however, 
definitely leadership roles.

Yours,
Joel

On 2/16/14, 5:38 PM, Jorge Amodio wrote:
>
> The issue is not participation, engagement and cooperation which I
> consider vital for a healthy and continuously development of the
> Internet. The issue IMHO is the tag labeling of a group of individuals
> that perform on an executive role and how the labeling and some
> statements are perceived and interpreted particularly by mainstream
> media in a context where Internet Governance (widely misinterpreted by
> itself ) is on the forefront nowadays.
>
> You may not see it because you are in the midst of it. My concern is
> with the "I* Leaders" label and how and where what you say can be easily
> taken out context and grossly misinterpreted without exercising some
> restraint and better choice of words.
>
> I'm not against Jari and Russ participation and having them share what's
> going on at IETF and explore opportunities for more and better cooperation.
>
> I'd strongly recommend to get rid of the "I* Leaders" moniker.
>
> Regards
> -Jorge
>
> On Feb 16, 2014, at 2:38 PM, John Curran <jcurran@istaff.org
> <mailto:jcurran@istaff.org>> wrote:
>
>> Jorge -
>>     This particular group of folks gathered and received updates on
>> various activities
>>     going on... e.g.  Jari and Russ spoke of perpass.  It is a
>> coordinating function; so
>>     we know about major initiatives going on and can support and/or
>> avoid conflicts
>>     as appropriate.
>>
>>     The only reason for the post-meeting statements (in my view) is
>> simply because
>>     people were unaware that these periodic gatherings were going on,
>> and indicated
>>     that we should be make such more visible.
>>
>>     Note also that there quite a bit of focus on making sure the most
>> recent statement
>>     simply said what happened, i.e.  a gathering of folks received a
>> series of updates
>>     from each other on a list of topics of potentially mutual interest.
>>
>>     As a result, I now realize that W3C is having its 20th
>> anniversary; that ICANN's
>>     various strategy panels have been meeting, and that the "Brazil
>> meeting" is now
>>     know as  â€œNetmundialâ€� and has its own website
>> <http://netmundial.br>.   I don't
>>     really know what the other leaders (for lack of a better term)
>> took away, but
>>     would hope that Jari, Russ, etc. found it useful context and
>> background for their
>>     IETF efforts.    I guess that one option would be for the
>> "leaders" from the IETF
>>     community not to attend such gatherings, but that seems to be a
>> rather extreme
>>     response to take due to lack of a better term than "leader" (and
>> one hopes it is
>>     unnecessary so long as care is taken to make nothing more of the
>> meetings than
>>     what they are - a gathering of folks hearing updates so we can
>> better coordinate)
>>
>> FYI,
>> /John
>>
>> On Feb 16, 2014, at 10:58 AM, Jorge Amodio <jmamodio@gmail.com
>> <mailto:jmamodio@gmail.com>> wrote:
>>
>>>
>>> I agree that "spokesperson" is not either the appropriate term. And
>>> leader is far far away to be representative of their roles and positions.
>>>
>>> True that on their role they "lead" the organizations they are
>>> involved with but the Internet community does not follow them as
>>> *leaders*, particularly the CEOs of some organizations such as ICANN,
>>> ARIN, etc, that are just paid employees to play a specific executive
>>> role.
>>>
>>> I'm really starting to dislike this effort of reverting the bottom-up
>>> process by a group that is starting to behave like a dictatorial
>>> junta making public statements that can be considered or interpreted
>>> as representative of the Internet community and particular
>>> organizations such as IETF.
>>>
>>> They are no spokesperson, nor leaders, just they are what they are
>>> the CEO of ICANN, the Chair of IETF, the CEO of ARIN, etc.
>>>
>>>
>>> My .02
>>> Jorge
>>>
>>>
>>>
>>> On Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <ted.lemon@nominum.com
>>> <mailto:ted.lemon@nominum.com>> wrote:
>>>
>>>     Folks, as John Klensin said, the reason we do not say
>>>     "spokesperson" is that our leadership do not speak for us.   We
>>>     only speak as a group through the consensus process.   So the
>>>     term "spokesperson" is simply inaccurate.
>>>
>>>     The term "leader" makes sense as a generic because there were a
>>>     number of organizations, with different leadership structures,
>>>     some not involving the same consensus process that exists in the
>>>     IETF.   So we couldn't for example say "chair," because that term
>>>     wouldn't apply to all the people who signed the statement.
>>>
>>>     I realize that the term "leader" has its own set of connotations,
>>>     but I don't know of a better word to use.   There is no word that
>>>     we could use that would convey to someone who is not already
>>>     familiar with IETF process what we mean.   Representative is no
>>>     good for the same reason spokesperson is no good.   Avatar
>>>     doesn't really work either.
>>>
>>>     I think it's better to just accept that the language is
>>>     imprecise, and think carefully about what is that we might be
>>>     objecting to, and whether the objection _really_ makes sense in
>>>     the context.   I guess there's about zero chance that this won't
>>>     get discussed to death, and that's fine, but I don't think
>>>     there's a knob to turn here.
>>>
>>>
>>


From nobody Sun Feb 16 15:27:45 2014
Return-Path: <jcurran@istaff.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 C886B1A02AC for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 15:27:43 -0800 (PST)
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, DIET_1=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 A2YEowaraHOY for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 15:27:41 -0800 (PST)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id BAD211A00B0 for <ietf@ietf.org>; Sun, 16 Feb 2014 15:27:41 -0800 (PST)
Received: from pool-108-45-30-69.washdc.fios.verizon.net ([108.45.30.69] helo=[192.168.1.12]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1WFB7a-0006T5-H1; Sun, 16 Feb 2014 23:27:38 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 108.45.30.69
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX1/ddcAUz6dOVOl2y7Cy5/Sv
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Internet organisations coordination meeting
From: John Curran <jcurran@istaff.org>
In-Reply-To: <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com>
Date: Sun, 16 Feb 2014 18:27:34 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A3F54FE8-4478-4697-9A50-DEE98E159651@istaff.org>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com> <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org> <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com>
To: Jorge Amodio <jmamodio@gmail.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8qZEsEUXCfQbq_RdSKfvBWwwkJo
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: Sun, 16 Feb 2014 23:27:44 -0000

On Feb 16, 2014, at 5:38 PM, Jorge Amodio <jmamodio@gmail.com> wrote:

> The issue is not participation, engagement and cooperation which I =
consider vital for a healthy and continuously development of the =
Internet. The issue IMHO is the tag labeling of a group of individuals =
that perform on an executive role and how the labeling and some =
statements are perceived and interpreted particularly by mainstream =
media in a context where Internet Governance (widely misinterpreted by =
itself ) is on the forefront nowadays.

I believe that was particularly the case with the statement made coming =
out of the
Montevideo meeting, and hopefully everyone has learned quite a bit as a =
result...

> You may not see it because you are in the midst of it. My concern is =
with the "I* Leaders" label and how and where what you say can be easily =
taken out context and grossly misinterpreted without exercising some =
restraint and better choice of words.=20


I believe that appropriate restraint and care was taken in the most =
recent statement.

> I'm not against Jari and Russ participation and having them share =
what's going on at IETF and explore opportunities for more and better =
cooperation.
>=20
> I'd strongly recommend to get rid of the "I* Leaders" moniker.

I think it is fairly easy to avoid the use of "I*" shorthand; it simply =
means consistently=20
saying instead "Leaders of organizations that are currently taking =
responsibility for=20
coordination..." (to use AB's formulation).  =20

It gets a tad more complicated if one doesn't want those attending from =
the IETF to be
referred to as "Leaders" at all.   Someone suggested using the term =
Representatives,=20
but that's potentially even more problematic for some folks.

/John



From nobody Sun Feb 16 15:31: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 66C401A02A7 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 15:31:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level: 
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DIET_1=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OPZ0tAmmF4NQ for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 15:31:55 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8561A0168 for <ietf@ietf.org>; Sun, 16 Feb 2014 15:31:54 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WFBBT-00094G-GQ; Sun, 16 Feb 2014 18:31:39 -0500
Date: Sun, 16 Feb 2014 18:31:34 -0500
From: John C Klensin <john-ietf@jck.com>
To: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: Internet organisations coordination meeting
Message-ID: <4C38999B6932DE18AFF1B484@JcK-HP8200.jck.com>
In-Reply-To: <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.u k> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com> <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org> <7578A603-D089-4AF7-9883-629C7A19965F@gmail.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7XlDlMriTF_hNUzN3-SWvWM5a9c
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: Sun, 16 Feb 2014 23:31:57 -0000

--On Sunday, February 16, 2014 16:38 -0600 Jorge Amodio
<jmamodio@gmail.com> wrote:

>...
> You may not see it because you are in the midst of it. My
> concern is with the "I* Leaders" label and how and where what
> you say can be easily taken out context and grossly
> misinterpreted without exercising some restraint and better
> choice of words. 

> I'm not against Jari and Russ participation and having them
> share what's going on at IETF and explore opportunities for
> more and better cooperation.
> 
> I'd strongly recommend to get rid of the "I* Leaders" moniker.

Jorge,

Because I think it makes no difference what this group (or these
meetings) are called, let me suggest a different distinction.
For this group to meet and exchange ideas and updates is, IMO,
completely reasonable and beneficial for the reasons outlined in
John Curran's note.  If they get together, meet quietly, and
then go back to their respective organizations and report and
discuss topics as appropriate, I think there are considerable
benefits and can't imagine any harm resulting.  Issues arise
when people start issuing group "statements" or press releases
because that is the point at which questions of authority to
issue such statements and the legitimacy of the group as a
decision-making or position-forming entity arise.  

Personally, I don't want us to tell Jari and Russ (or anyone
else) to never issue a statement of press release.  Not only
would that be unreasonable but there may be circumstances in
which the advantages of doing so (or the disadvantages of not
doing so) clearly outweigh any risks.  But, especially after
some of the lurid interpretations of the Montevideo
"declaration" and what it has been used to justify, I'd hope
that the participants in these meetings can go easy on
statement-issuing in the name (whatever that is) of the group.

   best,
    john

p.s.  I hope there is no one attending those meetings who would
stop if they didn't produce publicity, statements, and/or press
releases.  If there is, I would urge our leaders to consider the
implications of that, and even the necessity of having that
person involved, carefully rather than giving in to that sort of
preference.



From nobody Sun Feb 16 16:09:26 2014
Return-Path: <jmamodio@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 F2C981A0168 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 16:09:23 -0800 (PST)
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 TaDsreY4xzcG for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 16:09:22 -0800 (PST)
Received: from mail-ve0-x22d.google.com (mail-ve0-x22d.google.com [IPv6:2607:f8b0:400c:c01::22d]) by ietfa.amsl.com (Postfix) with ESMTP id D88E91A00D3 for <ietf@ietf.org>; Sun, 16 Feb 2014 16:09:21 -0800 (PST)
Received: by mail-ve0-f173.google.com with SMTP id jw12so4309229veb.32 for <ietf@ietf.org>; Sun, 16 Feb 2014 16:09:19 -0800 (PST)
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=4N9vMv/fshjWL2YKfrx9uJSw8UtYNjlXeImCOIRa1BE=; b=AYYp3hhoY3yfgCLX0H5VrACCqGSZVgnkjhQ2i5ydMPC1630DyoRBPimVHabj/AZegp 02zkPb3ThSX0fnHbEt6iTfJIGunKzsEyFZGJmUW5UkMkxBNp7UxMQVUDZU88ioPiEL/J FkHpW0FdHI/fgyE8V6No6HP00j1fh9pjmi8cUNceiu2mUl8OQxeLiQn+O9wscTv+Duna +9UyQdOmxxlZQ4F6HIitczkBrNTnxl3p5jnXv402jOQuV2nvTysmV8pqS4pwISbw/ZqX QfxQfbGej3T3D7lkCETeNi6lc9hdikl/Jlgqy1UxwsAVl5dIrDf7yrJp5+QXBNwA5ikp ooJQ==
MIME-Version: 1.0
X-Received: by 10.220.175.198 with SMTP id bb6mr2721943vcb.31.1392595759313; Sun, 16 Feb 2014 16:09:19 -0800 (PST)
Received: by 10.58.218.226 with HTTP; Sun, 16 Feb 2014 16:09:19 -0800 (PST)
In-Reply-To: <53014599.2070100@joelhalpern.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com> <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org> <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com> <53014599.2070100@joelhalpern.com>
Date: Sun, 16 Feb 2014 18:09:19 -0600
Message-ID: <CAMzo+1bgPy9WV46=qxw+RixwQRnY=VxmXZNw3=HBOp9=t3PoAQ@mail.gmail.com>
Subject: Re: Internet organisations coordination meeting
From: Jorge Amodio <jmamodio@gmail.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Content-Type: multipart/alternative; boundary=001a11c18c1a8cb81804f28ef784
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3wVSDABvRwTT1bP8yqIwDTdxgJQ
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: Mon, 17 Feb 2014 00:09:24 -0000

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

Agreed,

Well, I tried to keep my message generic and not going into individual
descriptions, I know very well that IETF chairs are not "executives" but
the CEO's on the "I* Leaders" group are, and BTW are being paid big bucks
to do their job.

-J


On Sun, Feb 16, 2014 at 5:11 PM, Joel M. Halpern <jmh@joelhalpern.com>wrote:

> Actually Jorge, I would have to disagree with your discription.  Neither
> the IAB Chair nor the IESG Chair are executive roles.  They are however,
> definitely leadership roles.
>
> Yours,
> Joel
>>
>>
>>

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

<div dir=3D"ltr"><div><br></div>Agreed,<div><br><div>Well, I tried to keep =
my message generic and not going into individual descriptions, I know very =
well that IETF chairs are not &quot;executives&quot; but the CEO&#39;s on t=
he &quot;I* Leaders&quot; group are, and BTW are being paid big bucks to do=
 their job.</div>
</div><div><br></div><div>-J</div><div class=3D"gmail_extra"><br><br><div c=
lass=3D"gmail_quote">On Sun, Feb 16, 2014 at 5:11 PM, Joel M. Halpern <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:jmh@joelhalpern.com" target=3D"_blank">j=
mh@joelhalpern.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">Actually Jorge, I would have to disagree wit=
h your discription. =A0Neither the IAB Chair nor the IESG Chair are executi=
ve roles. =A0They are however, definitely leadership roles.<br>

<br>
Yours,<br>
Joel<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div class=3D""><br></div></blockquote><=
/blockquote></div></div></div>

--001a11c18c1a8cb81804f28ef784--


From nobody Sun Feb 16 16:14:20 2014
Return-Path: <jmamodio@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 D94171A016A for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 16:14:18 -0800 (PST)
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 lB6z7a5nb7if for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 16:14:16 -0800 (PST)
Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 9CB501A01CD for <ietf@ietf.org>; Sun, 16 Feb 2014 16:14:16 -0800 (PST)
Received: by mail-vc0-f182.google.com with SMTP id id10so11207584vcb.13 for <ietf@ietf.org>; Sun, 16 Feb 2014 16:14:14 -0800 (PST)
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=+ZX5pUm/S7OFi5uHzQ6dgPMwG3KuIz70UB1SgAeMc/c=; b=C9lxCgXSrV+K4n9N43ywDv8lhExBZgiGmBVcwjJvvJ5QSlM+sfYZCE+ov7OoBrSbT6 LYgaDqf8OgYi2YobWUwytIYLN1Y4CasIY8JfUDzyNb/QizLbG8Ms+kg27PNaJICkhe43 qEdrLeeXfzIWyNZraAfha16OIyHlCX23NzKnkyLFTduC9ZGLtmTHxLzaPBN+QT7jhWfu LuGM2jK4BPXy/AQqxgWtICXUp1clheqQNW3YeizgpGiItuPxD1GRDzTQ9VEb8cBxxvl9 RP6ae351IWFnuVgHaFxygCSk6M5qz0RhIYznqLG0iZiunU+uHaQOYOXzfMGSuIw7gFHi CaJA==
MIME-Version: 1.0
X-Received: by 10.220.250.203 with SMTP id mp11mr14592435vcb.2.1392596054132;  Sun, 16 Feb 2014 16:14:14 -0800 (PST)
Received: by 10.58.218.226 with HTTP; Sun, 16 Feb 2014 16:14:14 -0800 (PST)
In-Reply-To: <4C38999B6932DE18AFF1B484@JcK-HP8200.jck.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com> <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org> <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com> <4C38999B6932DE18AFF1B484@JcK-HP8200.jck.com>
Date: Sun, 16 Feb 2014 18:14:14 -0600
Message-ID: <CAMzo+1ZiP59BiAq48HegdReWvFR+5ugoS+AWSUKavMKx8VhpZQ@mail.gmail.com>
Subject: Re: Internet organisations coordination meeting
From: Jorge Amodio <jmamodio@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=089e013d05021f4b6904f28f09d8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/XmPx0wPXWOQrS1BSWz2FYBzlf00
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: Mon, 17 Feb 2014 00:14:19 -0000

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

>
>
> Because I think it makes no difference what this group (or these
> meetings) are called, let me suggest a different distinction.
> For this group to meet and exchange ideas and updates is, IMO,
> completely reasonable and beneficial for the reasons outlined in
> John Curran's note.  If they get together, meet quietly, and
> then go back to their respective organizations and report and
> discuss topics as appropriate,


Amen.


> I think there are considerable
> benefits and can't imagine any harm resulting.  Issues arise
> when people start issuing group "statements" or press releases
> because that is the point at which questions of authority to
> issue such statements and the legitimacy of the group as a
> decision-making or position-forming entity arise.
>

Bingo !


> Personally, I don't want us to tell Jari and Russ (or anyone
> else) to never issue a statement of press release.  Not only
> would that be unreasonable but there may be circumstances in
> which the advantages of doing so (or the disadvantages of not
> doing so) clearly outweigh any risks.  But, especially after
> some of the lurid interpretations of the Montevideo
> "declaration" and what it has been used to justify, I'd hope
> that the participants in these meetings can go easy on
> statement-issuing in the name (whatever that is) of the group.
>

Agreed.

-J

--089e013d05021f4b6904f28f09d8
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"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><br>
Because I think it makes no difference what this group (or these<br>
meetings) are called, let me suggest a different distinction.<br>
For this group to meet and exchange ideas and updates is, IMO,<br>
completely reasonable and beneficial for the reasons outlined in<br>
John Curran&#39;s note. =A0If they get together, meet quietly, and<br>
then go back to their respective organizations and report and<br>
discuss topics as appropriate,</blockquote><div><br></div><div>Amen.</div><=
div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"> I think there are considerable=
<br>

benefits and can&#39;t imagine any harm resulting. =A0Issues arise<br>
when people start issuing group &quot;statements&quot; or press releases<br=
>
because that is the point at which questions of authority to<br>
issue such statements and the legitimacy of the group as a<br>
decision-making or position-forming entity arise.<br></blockquote><div><br>=
</div><div>Bingo !</div><div>=A0</div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Personally, I don&#39;t want us to tell Jari and Russ (or anyone<br>
else) to never issue a statement of press release. =A0Not only<br>
would that be unreasonable but there may be circumstances in<br>
which the advantages of doing so (or the disadvantages of not<br>
doing so) clearly outweigh any risks. =A0But, especially after<br>
some of the lurid interpretations of the Montevideo<br>
&quot;declaration&quot; and what it has been used to justify, I&#39;d hope<=
br>
that the participants in these meetings can go easy on<br>
statement-issuing in the name (whatever that is) of the group.<br></blockqu=
ote><div><br></div><div>Agreed.</div><div>=A0</div><div>-J</div><div><br></=
div></div></div></div>

--089e013d05021f4b6904f28f09d8--


From nobody Sun Feb 16 19:23:16 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 C8B481A0252; Sun, 16 Feb 2014 19:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 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.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id skrX1SWhA8Yw; Sun, 16 Feb 2014 19:23:04 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id CFF261A0129; Sun, 16 Feb 2014 19:23:03 -0800 (PST)
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 s1H3Mucq029109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 16 Feb 2014 22:22:57 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s1H3Mucq029109
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1392607378; bh=8LXXScS+P6JA9k2uaKBfapUwxGU=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=VKKoqTOlQsXv6b2Naw2nlA287eSxs3SSPn7mytBEihojrrVsK6GiHknINmPtP5Lmk nxZrYHJVp8V8wKgCWqEuFYoLFMyPlmTnUY8Qx7u4jmc/BcUsw4aYvcUCXToMEXLmUl eQ+rAMU9q5Gxl4Fyc+/2ph3/B967JScKNVH96960=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s1H3Mucq029109
Received: from mailusrhubprd02.lss.emc.com (mailusrhubprd02.lss.emc.com [10.253.24.20]) by maildlpprd06.lss.emc.com (RSA Interceptor); Sun, 16 Feb 2014 19:22:46 -0800
Received: from mxhub06.corp.emc.com (mxhub06.corp.emc.com [128.222.70.203]) by mailusrhubprd02.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s1H3MicB000374 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sun, 16 Feb 2014 22:22:45 -0500
Received: from mx15a.corp.emc.com ([169.254.1.167]) by mxhub06.corp.emc.com ([128.222.70.203]) with mapi; Sun, 16 Feb 2014 22:22:45 -0500
From: "Black, David" <david.black@emc.com>
To: "schmidt@informatik.haw-hamburg.de" <schmidt@informatik.haw-hamburg.de>, "shgao@bjtu.edu.cn" <shgao@bjtu.edu.cn>, "hkzhang@bjtu.edu.cn" <hkzhang@bjtu.edu.cn>, "mw@link-lab.net" <mw@link-lab.net>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Date: Sun, 16 Feb 2014 22:22:43 -0500
Subject: Gen-ART review of draft-ietf-multimob-pmipv6-source-07
Thread-Topic: Gen-ART review of draft-ietf-multimob-pmipv6-source-07
Thread-Index: Ac8rj4MZQa2HyqMUS1m6n+2pSS4Syw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712027281E4CC@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: mailusrhubprd02.lss.emc.com
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QAyRd4BmxO6OBtJYvNA2rDDMAsY
Cc: "Black, David" <david.black@emc.com>, "multimob@ietf.org" <multimob@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, 17 Feb 2014 03:23:07 -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-multimob-pmipv6-source-07
Reviewer: David L. Black
Review Date: Feb 16, 2014
IETF LC End Date: Feb 24, 2014

Summary: This draft is basically ready for publication, but has nits that
should be fixed before publication.

This draft describes multicast support for proxy mobile IPv6.  It assumes
significant understanding of multicast and specifically the PIM-SM protocol=
.

Nits/editorial comments:

-- Introduction, 3rd paragraph

Remove the word business from the following text, please:

             Such approaches (partially) follow
   the business model of providing multicast data services in parallel
   to PMIPv6 unicast routing [I-D.ietf-multimob-handover-optimization].

-- 4.3.1

The fact that PIM-SM has three phases could be made somewhat clearer here.=
=20
Suggestion:

OLD
   The granularity of mobility-related routing
   locators required in PIM depends on the complexity (phases) of its
   deployment.

   The following information is needed for all three phases of PIM as
   defined in [RFC4601].
NEW
   The granularity of mobility-related routing
   locators required in PIM depends on the complexity (specific phase)
   of its deployment.

   For all three phases of PIM deployment (see [RFC4601]), the following
   information is needed.

Also, is "deployment" the right word to describe the phases?  It implies
that not all of the phases need to be present in an implementation or
used, even if applicable.

-- 4.3.2 - 4.3.4

I would also suggest including the names of the phases from RFC 4601 in
these section titles, e.g.:

4.3.2.  Operations of PIM in Phase One (RP Tree)

-- idnits

idnits 2.13.01 found an unused reference and a couple of drafts that
have been updated:

  =3D=3D Unused Reference: 'RFC2236' is defined on line 1047, but no explic=
it
     reference was found in the text

  =3D=3D Outdated reference: A later version (-02) exists of
     draft-ietf-multimob-fmipv6-pfmipv6-multicast-01

  =3D=3D Outdated reference: A later version (-07) exists of
     draft-ietf-multimob-handover-optimization-06

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 Sun Feb 16 19:56:42 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 0AB2B1A02C0 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 19:56:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.703
X-Spam-Level: 
X-Spam-Status: No, score=-0.703 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, 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 g9xXqFNWCNfy for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 19:56:39 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0149.outbound.protection.outlook.com [207.46.163.149]) by ietfa.amsl.com (Postfix) with ESMTP id 037501A0031 for <ietf@ietf.org>; Sun, 16 Feb 2014 19:56:38 -0800 (PST)
Received: from DM2PR03CA009.namprd03.prod.outlook.com (10.141.52.157) by DM2PR03MB381.namprd03.prod.outlook.com (10.141.55.11) with Microsoft SMTP Server (TLS) id 15.0.878.16; Mon, 17 Feb 2014 03:56:35 +0000
Received: from BN1BFFO11FD038.protection.gbl (2a01:111:f400:7c10::1:122) by DM2PR03CA009.outlook.office365.com (2a01:111:e400:2414::29) with Microsoft SMTP Server (TLS) id 15.0.878.16 via Frontend Transport; Mon, 17 Feb 2014 03:56:35 +0000
Received: from mail.microsoft.com (131.107.125.37) by BN1BFFO11FD038.mail.protection.outlook.com (10.58.144.101) with Microsoft SMTP Server (TLS) id 15.0.868.13 via Frontend Transport; Mon, 17 Feb 2014 03:56:34 +0000
Received: from TK5EX14MBXC302.redmond.corp.microsoft.com ([169.254.2.226]) by TK5EX14HUBC101.redmond.corp.microsoft.com ([157.54.7.153]) with mapi id 14.03.0174.002; Mon, 17 Feb 2014 03:56:05 +0000
From: Christian Huitema <huitema@microsoft.com>
To: avri <avri@acm.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: RE: Internet organisations coordination meeting
Thread-Topic: Internet organisations coordination meeting
Thread-Index: AQHPK1tCZc9C1wdpO0+Cncb2Og6nTZq40Okg
Date: Mon, 17 Feb 2014 03:56:05 +0000
Message-ID: <C91E67751B1EFF41B857DE2FE1F68ABA3DFC2965@TK5EX14MBXC302.redmond.corp.microsoft.com>
References: <xkajdui3my5n236ee625q1k8.1392584917507@email.android.com>
In-Reply-To: <xkajdui3my5n236ee625q1k8.1392584917507@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.54.51.32]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-EOPAttributedMessage: 0
X-Forefront-Antispam-Report: CIP:131.107.125.37; CTRY:US; IPV:NLI; EFV:NLI; SFV:NSPM; SFS:(10009001)(6009001)(199002)(189002)(20776003)(51856001)(63696002)(77982001)(74876001)(92566001)(53806001)(4396001)(74662001)(79102001)(66066001)(49866001)(77096001)(93516002)(50986001)(59766001)(31966008)(6806004)(47776003)(94946001)(76786001)(92726001)(65816001)(86362001)(93136001)(85306002)(80976001)(54356001)(47976001)(94316002)(47446002)(47736001)(83322001)(76796001)(44976005)(86612001)(90146001)(2656002)(56816005)(87936001)(95666001)(50466002)(23676002)(69226001)(56776001)(85852003)(95416001)(81816001)(76482001)(80022001)(46102001)(87266001)(83072002)(81686001)(81342001)(74366001)(33656001)(54316002)(74502001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR03MB381; H:mail.microsoft.com; CLIP:131.107.125.37; FPR:; MLV: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: 012570D5A0
X-OriginatorOrg: microsoft.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/I6fYIfTKsQvjsfSB_-Q2oCPzeH0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Feb 2014 03:56:41 -0000

PkFsdGhvdWdoIEkgaGF2ZSBhIHBlcnNvbmFsIGF2ZXJzaW9uIMKgdG8gdGhlIHRlcm0gbGVhZGVy
LCBJIHRoaW5rIGl0IGEgZ29vZCB0aGluZyB0aGF0IGFsbCB5b3UgbGVhZGVyL2Nvb3JkaW5hdG9y
L3Nwb2tlcnBlcnNvbnkgDQo+IHR5cGUgZm9sa3MgZG8gbWVldCBhbmQgZG8gcmVwb3J0IG9uIHlv
dXIgbWVldGluZ3MuDQoNCklmIHdlIHdhbnQgbmV3IHZvY2FidWxhcnksIHdlIG1heSBnbyB0byBM
YXRpbiByb290cy4gSW5zdGVhZCBvZiBsZWFkZXIsIHdlIG1heSB3YW50IHRvIHVzZSAiZHV4LCIg
b3IgImR1a2UiIGluIHRoZSBFbmdsaXNoIHRyYW5zbGF0aW9uLiBPciBtYXliZSAiZHVjZSIgYXMg
aW4gSXRhbGlhbi4gV2FpdCwgdGhlcmUgaXMgYmV0dGVyLCB0aGUgVmVuZXRpYW4gdmVyc2lvbiB0
aGF0IGhhcHBlbnMgdG8gYmUgYSByZWFsIEludGVybmV0IG1lbWUgLS0gImRvZ2UuIg0KDQotLSBD
aHJpc3RpYW4gSHVpdGVtYQ0KDQoNCg==


From nobody Sun Feb 16 23:54: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 180BD1A0065 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 23:54:50 -0800 (PST)
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 B2uPzQu_b1GS for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 23:54:47 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) by ietfa.amsl.com (Postfix) with ESMTP id E42471A0041 for <ietf@ietf.org>; Sun, 16 Feb 2014 23:54:46 -0800 (PST)
Received: from [195.245.231.67:55232] by server-13.bemta-5.messagelabs.com id 60/C2-18801-340C1035; Mon, 17 Feb 2014 07:54:43 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-82.messagelabs.com!1392623683!26465496!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6965 invoked from network); 17 Feb 2014 07:54:43 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-9.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 17 Feb 2014 07:54:43 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Mon, 17 Feb 2014 07:54:43 +0000
From: <l.wood@surrey.ac.uk>
To: <huitema@microsoft.com>, <avri@acm.org>, <ietf@ietf.org>
Date: Mon, 17 Feb 2014 07:54:18 +0000
Subject: RE: Internet organisations coordination meeting
Thread-Topic: Internet organisations coordination meeting
Thread-Index: AQHPK1tCZc9C1wdpO0+Cncb2Og6nTZq40OkggABDTBw=
Message-ID: <290E20B455C66743BE178C5C84F1240847E633471D@EXMB01CMS.surrey.ac.uk>
References: <xkajdui3my5n236ee625q1k8.1392584917507@email.android.com>, <C91E67751B1EFF41B857DE2FE1F68ABA3DFC2965@TK5EX14MBXC302.redmond.corp.microsoft.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA3DFC2965@TK5EX14MBXC302.redmond.corp.microsoft.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/9jLgiKL2_MULcbNSuFgYmh-SJnM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Feb 2014 07:54:50 -0000

That would make the leader of the W3C the "Duke of URL"

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Christian Huitema [huitema@=
microsoft.com]
Sent: 17 February 2014 03:56
To: avri; ietf@ietf.org Discussion
Subject: RE: Internet organisations coordination meeting

>Although I have a personal aversion  to the term leader, I think it a good=
 thing that all you leader/coordinator/spokerpersony
> type folks do meet and do report on your meetings.

If we want new vocabulary, we may go to Latin roots. Instead of leader, we =
may want to use "dux," or "duke" in the English translation. Or maybe "duce=
" as in Italian. Wait, there is better, the Venetian version that happens t=
o be a real Internet meme -- "doge."

-- Christian Huitema



From nobody Mon Feb 17 08:42:39 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 DECBC1A0405 for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 08:42:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KxaWrovzAfFB for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 08:42:36 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id A445D1A00B4 for <ietf@ietf.org>; Mon, 17 Feb 2014 08:42:36 -0800 (PST)
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 580E01B81D8 for <ietf@ietf.org>; Mon, 17 Feb 2014 08:42:34 -0800 (PST)
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 4D8CB190043; Mon, 17 Feb 2014 08:42:34 -0800 (PST)
Received: from [10.0.1.29] (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, 17 Feb 2014 08:42:33 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Internet organisations coordination meeting
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <C91E67751B1EFF41B857DE2FE1F68ABA3DFC2965@TK5EX14MBXC302.redmond.corp.microsoft.com>
Date: Mon, 17 Feb 2014 11:42:31 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <28781F78-C864-48D7-B1A6-D57C1FD1AF3F@nominum.com>
References: <xkajdui3my5n236ee625q1k8.1392584917507@email.android.com> <C91E67751B1EFF41B857DE2FE1F68ABA3DFC2965@TK5EX14MBXC302.redmond.corp.microsoft.com>
To: Christian Huitema <huitema@microsoft.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/8ObMV2_jeCwEuosF7qfEkycJIGU
Cc: avri <avri@acm.org>, "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: Mon, 17 Feb 2014 16:42:38 -0000

On Feb 16, 2014, at 10:56 PM, Christian Huitema <huitema@microsoft.com> =
wrote:
> Wait, there is better, the Venetian version that happens to be a real =
Internet meme -- "doge."

I suspect those of us who have studied Venetian history might object to =
this appellation, but it's certainly a fun idea in theory.   :)


From nobody Mon Feb 17 09:18:39 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 BBEF51A0470 for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 09:18:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 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.548, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sB0wX5h7F9eA for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 09:18:34 -0800 (PST)
Received: from mailuogwhop.emc.com (mailuogwhop.emc.com [168.159.213.141]) by ietfa.amsl.com (Postfix) with ESMTP id 647781A00B4 for <ietf@ietf.org>; Mon, 17 Feb 2014 09:18:34 -0800 (PST)
Received: from maildlpprd04.lss.emc.com (maildlpprd04.lss.emc.com [10.253.24.36]) by mailuogwprd01.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s1HHIV4J004182 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Mon, 17 Feb 2014 12:18:31 -0500
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s1HHIV4J004182
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1392657511; bh=3fGC4JoTNncEWftwixAtP9M7+wA=; h=From:To:CC:Date:Subject:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=X2o2achn/vMYw1vhBGjxWzY/kzSnsSzwteEaeByVJ977BjhLABPW7ktebCeJhZ8Zz rC7hhZrNKxwEf6BbXXTtjFTQte4/Y7Y+VKAuq0YKflnPMP3hmRRU+VxM31hST+xjVw QUhUfKxYZ6duCpkjkwf0H/KW/1yvTdlFkGXGbVQs=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd01.lss.emc.com s1HHIV4J004182
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd04.lss.emc.com (RSA Interceptor) for <ietf@ietf.org>; Mon, 17 Feb 2014 09:18:16 -0800
Received: from mxhub11.corp.emc.com (mxhub11.corp.emc.com [10.254.92.106]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.0/Sentrion-MTA-4.3.0) with ESMTP id s1HHIFRF031593 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ietf@ietf.org>; Mon, 17 Feb 2014 12:18:16 -0500
Received: from mx15a.corp.emc.com ([169.254.1.167]) by mxhub11.corp.emc.com ([10.254.92.106]) with mapi; Mon, 17 Feb 2014 12:18:15 -0500
From: "Black, David" <david.black@emc.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Date: Mon, 17 Feb 2014 12:18:14 -0500
Subject: Last Call: <draft-mahalingam-dutt-dcops-vxlan-08.txt>:  4 comments
Thread-Topic: Last Call: <draft-mahalingam-dutt-dcops-vxlan-08.txt>:  4 comments
Thread-Index: Ac8sBD2Yb1K1t5S2SZ+S8WPsx4M0Jw==
Message-ID: <8D3D17ACE214DC429325B2B98F3AE712027281E52C@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
X-RSA-Classifications: public
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/T6zUta553AgxsdYFrgSkMe43vV8
Cc: "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, 17 Feb 2014 17:18:37 -0000

-- Section 4.3:

   VTEPs MUST not fragment VXLAN packets.

Nit: "MUST not" -> "MUST NOT"

-- Section 5:

   IANA has assigned the value 4789 for the VXLAN UDP
   port and this value SHOULD be used by default as the destination UDP
   port.  Some early implementations of VXLAN have used other values
   for the destination port.  To enable interoperability with these
   implementations, the destination port SHOULD be configurable.

Minor issue: Why is this "SHOULD" instead of "MUST"?

   The UDP checksum field SHOULD be transmitted as zero.

Major issue: That's ok for an IPv4 outer header, but for an IPv6
outer header, see, apply and cite RFC 6935 and RFC 6936.  This is
important and also applies to the optionality of UDP checksum
verification for IPv6.

Editorial: It would help if section 5 explained what two Ethertype
values are - 0x0800 is the Ethertype for IPv4, 0x08DD is the
Ethertype for IPv6.

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 Mon Feb 17 14:46:08 2014
Return-Path: <worley@shell01.TheWorld.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FF241A0291 for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 14:46:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.201
X-Spam-Level: 
X-Spam-Status: No, score=-1.201 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 zd8--ms79zee for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 14:46:05 -0800 (PST)
Received: from TheWorld.com (pcls6.std.com [192.74.137.146]) by ietfa.amsl.com (Postfix) with ESMTP id CC50E1A029E for <ietf@ietf.org>; Mon, 17 Feb 2014 14:46:04 -0800 (PST)
Received: from shell.TheWorld.com (svani@shell01.theworld.com [192.74.137.71]) by TheWorld.com (8.14.5/8.14.5) with ESMTP id s1HMjSgk023966 for <ietf@ietf.org>; Mon, 17 Feb 2014 17:45:30 -0500
Received: from shell01.TheWorld.com (localhost.theworld.com [127.0.0.1]) by shell.TheWorld.com (8.13.6/8.12.8) with ESMTP id s1HMjNDu5211808 for <ietf@ietf.org>; Mon, 17 Feb 2014 17:45:23 -0500 (EST)
Received: (from worley@localhost) by shell01.TheWorld.com (8.13.6/8.13.6/Submit) id s1HMjNmi5224677; Mon, 17 Feb 2014 17:45:23 -0500 (EST)
Date: Mon, 17 Feb 2014 17:45:23 -0500 (EST)
Message-Id: <201402172245.s1HMjNmi5224677@shell01.TheWorld.com>
From: worley@ariadne.com (Dale R. Worley)
Sender: worley@ariadne.com (Dale R. Worley)
To: IETF discussion list <ietf@ietf.org>
In-reply-to: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> (chair@ietf.org)
Subject: Re: Internet organisations coordination meeting
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/73j5NyzLY0bRqI4vfhYEYMXWstg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Feb 2014 22:46:07 -0000

I agree with John and Ted that while "leader" often has the
connotations of boss or controller, its actual meaning is quite broad,
really only limited to "when this person does or says something,
others pay attention to it as being important".  All other proposed
terms seem to imply certain *specific* powers, which may not be
accurate for all of them.

Now, as long as the audience for these announcements is the
memberships of the various organizations involved, the terminology
doesn't really matter.  IETFers know what the role of the IAB Chair
is, and the roles of the other "leaders" (if they care).  And such
meetings help to coordinate efforts that are of common interest.

It gets more interesting if the organizations are collectively
attempting to increase their influence in what is called "Internet
governance", the mass of laws, treaties, customs, business
arrangements, etc., etc. that altogether determine how the Internet
actually works from the point view of users.  Of the seven bullet
points mentioned in the announcement, six of them seem to be of this
nature.  For instance, "Preparations for the 2014 ITU Plenipotentiary
Conference".

>From that point of view, some care needs to be taken to ensure that
the words that are used support the political influence that is
desired.

Dale


From nobody Mon Feb 17 15:11:20 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 644901A041E for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 15:11:19 -0800 (PST)
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 SL45dYmil7Fx for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 15:11:13 -0800 (PST)
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 8A58C1A02CA for <ietf@ietf.org>; Mon, 17 Feb 2014 15:11:13 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id gq1so17713826obb.35 for <ietf@ietf.org>; Mon, 17 Feb 2014 15:11:10 -0800 (PST)
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=gyVKMSgHkaKzAEyRnPqB6pdAycc4i9VbrZUjHB8w8W8=; b=0iW1Z/TIGpUigcYNeEgZdAtj/ITQFEBghWeBjWdQuHhkr46LFc/tJenu01irB15JlN CtcKy1LIxtkdXElDx/8RsRPaZCSB73rG4rHLdulZRvQG4p/CaEJy/5Osw8RcD6dcTwiY m/PZ7hc/tvMwN2kKHxj34O9GTaQ+VcFxYi168wmpz/n2sRLNvU9vY/+udJLHcE9wUrQR fpt/Z26vSv/gF1hat5xySWF1jL0omQv0Ymkv/3/1LmPX/IkZJrnT740TqoorTWmweJBa UDrJ5UDK5FOJ7R/gFglOgFYBk4zS66QEOW8X3saAipGWLKXWvkT86EBiqrz1nIeuNkK5 mRPQ==
X-Received: by 10.60.97.193 with SMTP id ec1mr23416892oeb.20.1392678670839; Mon, 17 Feb 2014 15:11:10 -0800 (PST)
MIME-Version: 1.0
Received: by 10.76.23.138 with HTTP; Mon, 17 Feb 2014 15:10:50 -0800 (PST)
In-Reply-To: <201402172245.s1HMjNmi5224677@shell01.TheWorld.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <201402172245.s1HMjNmi5224677@shell01.TheWorld.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Mon, 17 Feb 2014 18:10:50 -0500
Message-ID: <CAF4+nEGd2eA+T+i-ZH=1=Aku=iB-mjTZ=3z-1eEa6jtKgY+kTA@mail.gmail.com>
Subject: Re: Internet organisations coordination meeting
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Hc1f-lbco_F8QU-hY6IV_D_Lrk8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Feb 2014 23:11:19 -0000

I think the term you are all looking for is

   factotum

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


On Mon, Feb 17, 2014 at 5:45 PM, Dale R. Worley <worley@ariadne.com> wrote:
> I agree with John and Ted that while "leader" often has the
> connotations of boss or controller, its actual meaning is quite broad,
> really only limited to "when this person does or says something,
> others pay attention to it as being important".  All other proposed
> terms seem to imply certain *specific* powers, which may not be
> accurate for all of them.
>
> Now, as long as the audience for these announcements is the
> memberships of the various organizations involved, the terminology
> doesn't really matter.  IETFers know what the role of the IAB Chair
> is, and the roles of the other "leaders" (if they care).  And such
> meetings help to coordinate efforts that are of common interest.
>
> It gets more interesting if the organizations are collectively
> attempting to increase their influence in what is called "Internet
> governance", the mass of laws, treaties, customs, business
> arrangements, etc., etc. that altogether determine how the Internet
> actually works from the point view of users.  Of the seven bullet
> points mentioned in the announcement, six of them seem to be of this
> nature.  For instance, "Preparations for the 2014 ITU Plenipotentiary
> Conference".
>
> >From that point of view, some care needs to be taken to ensure that
> the words that are used support the political influence that is
> desired.
>
> Dale
>


From nobody Mon Feb 17 16:37:42 2014
Return-Path: <mgramirez@globe.com.ph>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E26F11A0420 for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 16:37:40 -0800 (PST)
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 cEETP2jdk3P5 for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 16:37:37 -0800 (PST)
Received: from mail-qa0-f53.google.com (mail-qa0-f53.google.com [209.85.216.53]) by ietfa.amsl.com (Postfix) with ESMTP id B6D371A02EE for <ietf@ietf.org>; Mon, 17 Feb 2014 16:37:37 -0800 (PST)
Received: by mail-qa0-f53.google.com with SMTP id cm18so22847361qab.12 for <ietf@ietf.org>; Mon, 17 Feb 2014 16:37:34 -0800 (PST)
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=jKHlbm6keibtJjnlp5K09qBuGFmuC5VhkFDttGuy8O4=; b=BQkFFLjgsaCQ4DdN+KbMfggiL/YLmnuQ2nVWChZ3D0FiMa7UyCVtxqMUj+h2DaI3TG 5gfB6NuYfRryXsl6rwgiID3JD7gUXFXFAQivpiT+v2nyKs9VdBzk6AAUGL/X/8zUu0U3 8CNfG8EVoKJmkyNsbYYH2cqd4urmymOVE0I+F8zAZf3YGu1juWpKr/v5JfCcIb1bPXx5 iSE7CDxI07/1Y/ARqCdnP6kNm/qwjy9OVaLpy2P6ESe0uvU1wvCbRcLZZsTcqbKTD9Tb SfjN7rktNcT2ltVtWWYF8wHe2AliX4dpGo15E3yAWjRn2GKvc0JRsF7GX5rA3ULwORp5 vYzQ==
X-Gm-Message-State: ALoCoQm9mjx6yGqJ9OC4S2ELuOh0rcG6/uSNs2RtkN/6HiCubgzoXgPJQFm35p/DeouwzkehCuoG3+at7pcrIXs+Kg0oHaWTkw==
X-Received: by 10.140.82.8 with SMTP id g8mr6480445qgd.88.1392683854536; Mon, 17 Feb 2014 16:37:34 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.92.73 with HTTP; Mon, 17 Feb 2014 16:37:13 -0800 (PST)
In-Reply-To: <CAF4+nEGd2eA+T+i-ZH=1=Aku=iB-mjTZ=3z-1eEa6jtKgY+kTA@mail.gmail.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <201402172245.s1HMjNmi5224677@shell01.TheWorld.com> <CAF4+nEGd2eA+T+i-ZH=1=Aku=iB-mjTZ=3z-1eEa6jtKgY+kTA@mail.gmail.com>
From: Medel v6 Ramirez <mgramirez@globe.com.ph>
Date: Tue, 18 Feb 2014 08:37:13 +0800
Message-ID: <CALw3TGHrAETWgHce-k4aWyjRqtSaHqp=VTvznHzdMh89Zhs9sg@mail.gmail.com>
Subject: Re: Internet organisations coordination meeting
To: Donald Eastlake <d3e3e3@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c119826f45a004f2a37a69
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/X1mghA7ZUWkJEUjA6wOBwxwDG3o
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, 18 Feb 2014 00:37:41 -0000

--001a11c119826f45a004f2a37a69
Content-Type: text/plain; charset=US-ASCII

agree, much better.



GOOGLE IS IPv6 COMPLIANT !


On Tue, Feb 18, 2014 at 7:10 AM, Donald Eastlake <d3e3e3@gmail.com> wrote:

> I think the term you are all looking for is
>
>    factotum
>
> Thanks,
> Donald
> =============================
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>
>
> On Mon, Feb 17, 2014 at 5:45 PM, Dale R. Worley <worley@ariadne.com>
> wrote:
> > I agree with John and Ted that while "leader" often has the
> > connotations of boss or controller, its actual meaning is quite broad,
> > really only limited to "when this person does or says something,
> > others pay attention to it as being important".  All other proposed
> > terms seem to imply certain *specific* powers, which may not be
> > accurate for all of them.
> >
> > Now, as long as the audience for these announcements is the
> > memberships of the various organizations involved, the terminology
> > doesn't really matter.  IETFers know what the role of the IAB Chair
> > is, and the roles of the other "leaders" (if they care).  And such
> > meetings help to coordinate efforts that are of common interest.
> >
> > It gets more interesting if the organizations are collectively
> > attempting to increase their influence in what is called "Internet
> > governance", the mass of laws, treaties, customs, business
> > arrangements, etc., etc. that altogether determine how the Internet
> > actually works from the point view of users.  Of the seven bullet
> > points mentioned in the announcement, six of them seem to be of this
> > nature.  For instance, "Preparations for the 2014 ITU Plenipotentiary
> > Conference".
> >
> > >From that point of view, some care needs to be taken to ensure that
> > the words that are used support the political influence that is
> > desired.
> >
> > Dale
> >
>
>

-- 
This e-mail message (including attachments, if any) is intended for the use 
of the individual or the entity to whom it is addressed and may contain 
information that is privileged, proprietary, confidential and exempt from 
disclosure. If you are not the intended recipient, you are notified that 
any dissemination, distribution or copying of this communication is 
strictly prohibited. If you have received this communication in error, 
please notify the sender and delete this E-mail message immediately.


--001a11c119826f45a004f2a37a69
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:arial,he=
lvetica,sans-serif;font-size:large">agree, much better.</div><div class=3D"=
gmail_default" style=3D"font-family:arial,helvetica,sans-serif;font-size:la=
rge"><br>

</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif;font-size:large"><br></div></div><div class=3D"gmail_extra"><br cle=
ar=3D"all"><div><div dir=3D"ltr">GOOGLE IS IPv6 COMPLIANT !</div></div>
<br><br><div class=3D"gmail_quote">On Tue, Feb 18, 2014 at 7:10 AM, Donald =
Eastlake <span dir=3D"ltr">&lt;<a href=3D"mailto:d3e3e3@gmail.com" target=
=3D"_blank">d3e3e3@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 think the term you are all looking for is<br>
<br>
=A0 =A0factotum<br>
<br>
Thanks,<br>
Donald<br>
=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<br>
=A0Donald E. Eastlake 3rd =A0 <a href=3D"tel:%2B1-508-333-2270" value=3D"+1=
5083332270">+1-508-333-2270</a> (cell)<br>
=A0155 Beaver Street, Milford, MA 01757 USA<br>
=A0<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a><br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Mon, Feb 17, 2014 at 5:45 PM, Dale R. Worley &lt;<a href=3D"mailto:worle=
y@ariadne.com">worley@ariadne.com</a>&gt; wrote:<br>
&gt; I agree with John and Ted that while &quot;leader&quot; often has the<=
br>
&gt; connotations of boss or controller, its actual meaning is quite broad,=
<br>
&gt; really only limited to &quot;when this person does or says something,<=
br>
&gt; others pay attention to it as being important&quot;. =A0All other prop=
osed<br>
&gt; terms seem to imply certain *specific* powers, which may not be<br>
&gt; accurate for all of them.<br>
&gt;<br>
&gt; Now, as long as the audience for these announcements is the<br>
&gt; memberships of the various organizations involved, the terminology<br>
&gt; doesn&#39;t really matter. =A0IETFers know what the role of the IAB Ch=
air<br>
&gt; is, and the roles of the other &quot;leaders&quot; (if they care). =A0=
And such<br>
&gt; meetings help to coordinate efforts that are of common interest.<br>
&gt;<br>
&gt; It gets more interesting if the organizations are collectively<br>
&gt; attempting to increase their influence in what is called &quot;Interne=
t<br>
&gt; governance&quot;, the mass of laws, treaties, customs, business<br>
&gt; arrangements, etc., etc. that altogether determine how the Internet<br=
>
&gt; actually works from the point view of users. =A0Of the seven bullet<br=
>
&gt; points mentioned in the announcement, six of them seem to be of this<b=
r>
&gt; nature. =A0For instance, &quot;Preparations for the 2014 ITU Plenipote=
ntiary<br>
&gt; Conference&quot;.<br>
&gt;<br>
&gt; &gt;From that point of view, some care needs to be taken to ensure tha=
t<br>
&gt; the words that are used support the political influence that is<br>
&gt; desired.<br>
&gt;<br>
&gt; Dale<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div>

<br>
<div>This e-mail message (including attachments, if any) is intended for th=
e use of the individual or the entity to whom it is addressed and may conta=
in information that is privileged, proprietary, confidential and exempt fro=
m disclosure. If you are not the intended recipient, you are notified that =
any dissemination, distribution or copying of this communication is strictl=
y prohibited. If you have received this communication in error, please noti=
fy the sender and delete this E-mail message immediately.</div><div><br></d=
iv>
--001a11c119826f45a004f2a37a69--


From nobody Tue Feb 18 01:14:42 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 58B371A03FA; Tue, 18 Feb 2014 01:14:40 -0800 (PST)
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 zae4h1hICibf; Tue, 18 Feb 2014 01:14:35 -0800 (PST)
Received: from mail-ea0-x230.google.com (mail-ea0-x230.google.com [IPv6:2a00:1450:4013:c01::230]) by ietfa.amsl.com (Postfix) with ESMTP id C5BF11A0448; Tue, 18 Feb 2014 01:14:34 -0800 (PST)
Received: by mail-ea0-f176.google.com with SMTP id b10so3650920eae.7 for <multiple recipients>; Tue, 18 Feb 2014 01:14:31 -0800 (PST)
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=uFtPujwSzkovtYSWYwjHwql12IUUONqTr7wcMcP4jtw=; b=d1tlm/35nic53BIIsSiUc7vUw9+PLG4FoiPypZFXfLZZFrq2YU17DQ5QzsVHLnU1KY YayiRywHqJpQdPHVMf9PWpZsng7WzFysY5opJgF5phSCMaVWPo3z6TsVbJBVFltHNu5M sfYtWgvoxnvY0032sC6ZJLyjkVhBSDLkJpBJ3Wf4IpynyQGPTkh7J4feGKGTER7C+pTw dMkXLuOnM9zXH6Xsv/2HZLCjI6Whu3iTRSsTcYTbAGvSCy0f4mDvt1hTUtSBUUpyc6uT Zpuy4g/HWmKh99GYbA/9Vqr2mK3dIxXEPfld0ndcTYz50KcnEuVWHBW2kfoVw1QL9dZ/ 3xwg==
X-Received: by 10.14.202.8 with SMTP id c8mr2340923eeo.88.1392714871414; Tue, 18 Feb 2014 01:14:31 -0800 (PST)
Received: from RoniE (bzq-109-67-98-212.red.bezeqint.net. [109.67.98.212]) by mx.google.com with ESMTPSA id u6sm67743636eep.11.2014.02.18.01.14.29 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 18 Feb 2014 01:14:30 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-housley-pkix-oids.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-housley-pkix-oids-00
Date: Tue, 18 Feb 2014 11:14:27 +0200
Message-ID: <031401cf2c89$d4a7c460$7df74d20$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0315_01CF2C9A.983157B0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8sidKRf87DCw65R4apOy5PlRZ42Q==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/K09UQEGBAWSjSW9ufW9H8EPubqw
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, 18 Feb 2014 09:14:40 -0000

This is a multipart message in MIME format.

------=_NextPart_000_0315_01CF2C9A.983157B0
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-housley-pkix-oids-00

Reviewer: Roni Even

Review Date:2014-2-18

IETF LC End Date: 2014-2-28

IESG Telechat date: 

 

Summary: This draft is ready for publication as an Informational RFC.

 

 

Major issues:

 

Minor issues:

 

 

Nits/editorial comments:

In section 3.26 first entry I noticed when comparing to RFC5055 section
3.2.4.2.4 that the description in RFC5055 is id-nvae-name-mismatch. It
caused me a problem when trying to find it in RFC5055, the values are
correct so may not be important (maybe to ASN.1 compiler?) I did not check
all the descriptions but I looked at RFC 5055 to understand the
registration. (BTW: all the names in this table are not the same)

 


------=_NextPart_000_0315_01CF2C9A.983157B0
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'color:black'>draft-housley-pkix-oids-00<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;2-18<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;2-28<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 an Informational 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 3.26 first entry =
I noticed when comparing to RFC5055 section 3.2.4.2.4 that the =
description in RFC5055 is id-nvae-name-mismatch. It caused me a problem =
when trying to find it in RFC5055, the values are correct so may not be =
important (maybe to ASN.1 compiler?) I did not check all the =
descriptions but I looked at RFC 5055 to understand the registration. =
(BTW: all the names in this table are not the same)<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_0315_01CF2C9A.983157B0--


From nobody Tue Feb 18 02:59:03 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 A65281A032F; Tue, 18 Feb 2014 02:58:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 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, RP_MATCHES_RCVD=-0.548, 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 00KW-Nd6mWTg; Tue, 18 Feb 2014 02:58:51 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id 2AA421A00DD; Tue, 18 Feb 2014 02:58:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=18552; q=dns/txt; s=iport; t=1392721128; x=1393930728; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=xwyTrbfesVS7BObpU9JxFRX7ghNcOe2hA0Qj2Ykt6S8=; b=atnW2yfGD+fewoGu0YbXqb3CnKlZrpGYRg/JMLzaymCy7nCcZxwewUJK f9u0xa0iP/AMqn8edTDyQBA8SR4/6UHZSoZWEMvrM10uzoSiEtiJ4g+D5 vkVObNtg1enT0ioIvjnY6WsI8OPvmPR44BHuAhqNylzACrTUeT2aUMBT1 s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmwFAIg8A1OQ/khM/2dsb2JhbABZgwY4iTa2cYEWFnSCJQEBAQMBeAEFCwsUDRYPCQMCAQIBRQYBDAEHAQEQh2kIDcsuF40KgSBGEQeEOASYLIEyhRWLXIMuO4Et
X-IronPort-AV: E=Sophos;i="4.97,501,1389744000"; d="scan'208,217";a="4717563"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-2.cisco.com with ESMTP; 18 Feb 2014 10:58:46 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s1IAwjNg000648; Tue, 18 Feb 2014 10:58:45 GMT
Message-ID: <53033CE5.2000309@cisco.com>
Date: Tue, 18 Feb 2014 11:58:45 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>, General Area Review Team <gen-art@ietf.org>, Tal Mizrahi <talmi@marvell.com>
Subject: Re: Gen-art last call review of draft-ietf-opsawg-oam-overview-08.txt
References: <1358863845.28723.19076.camel@mightyatom>
In-Reply-To: <1358863845.28723.19076.camel@mightyatom>
Content-Type: multipart/alternative; boundary="------------080008020208000101050801"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bvPZvv7co_y4KzybjSJNzGIQVt8
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-opsawg-oam-overview.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Feb 2014 10:58:55 -0000

This is a multi-part message in MIME format.
--------------080008020208000101050801
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Elwyn,

Thanks for your review.
I don't plan to reply for the authors (btw, not sure I've seen a reply 
to this), and but a few clarification questions in line, to engage the 
discussion.

> 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-opsawg-oam-overview-08.txt
> Reviewer: Elwyn Davies
> Review Date: 22 Jan 2013
> IETF LC End Date:25 Jan 2013
> IESG Telechat date: (if known) -
>
> Summary: In my opinion, this draft has serious issues as described
> below.
>
> Major issues:
> General 1: Title vs Abstract vs Section 1 vs actual content:
>
> Here in the UK a well-known brand of varnishes and wood preservative
> paints uses the slogan 'Does what it says on the tin!'.  If my
> understanding and the write-up in RFC 6491, OAM covers a whole lot more
> than the coverage of the specific mechanisms discussed in this
> document .. and there are various other mechanisms such as SNMP and
> Netconf that support the OAM constellation.
Can you provide an example of what you mean here?
Do you mean that SNMP (and NETCONF) can be used to monitor the OAM results?

> I would take the view that
> this document certainly does not 'do what it says on the tin'.
> Accordingly I take issue with the title as it doesn't provide a total
> overview of OAM mechanisms; the abstract closes down the scope of OAM as
> compared with RFC 6491 and s1 restricts it even more - and certainly
> does not summarize all the OAM tools and mechanisms defined in the IETF.
> The last para of s1 claims that 'management aspects are outside the
> scope of this document' - if this is really saying that this 'overview'
> of OAM skips the whole M aspect of OAM then I'm afraid the document is
> badly misnamed.  And it significantly reduces the value of the work.
Ok, the document title could be improved.
>
> General (2): The intended purpose of this document: Back in 2011 Stewart
> Bryant summarized a review of a previous version of this document from
> the routing directorate
> (https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/ entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.
This sentence was added:

       The target audience of this document includes network equipment
        vendors, network operators and standard development organizations,
        and can be used as an index to some of the main OAM tools defined in
        the IETF.

And section 1.2


      1.2
      <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-13#section-1.2>.
      Target Audience



    The target audience of this document includes:

    o Standard development organizations - both IETF working groups and
       non-IETF organizations can benefit from this document when
       designing new OAM protocols, or when looking to reuse existing OAM
       tools for new technologies.

    o Network equipment vendors and network operators - can use this
       document as an index to some of the common IETF OAM tools.

    It should be noted that this document is not necessarily suitable for
    beginners without any background in OAM.


Please let the authors know what you would like to see.

I let the authors/doc. shepherd answer the following points.

Regards, Benoit
>
> General (3): I don't know if Scott Bradner has actually produced a proto
> shpeherd write up, but I would be intrigued to know the level of
> concensus behind this document.  In particular the tool classification
> in s1.1 and terminology in s2 (particularly s2.2.2) is that used
> exclusively in the MPLS-TP work in the IETF which is derived from the
> 802.1ag terminology.  The terminology is presented as if it is common to
> OAM work across the IETF. Does the IETF management community at large
> concur with this expansion of the applicability of the terminology set
> based on 'Management Domains' etc?
>
> General (4): As an overview, I think it would be advisable to point out
> that one reason for the multiplicity of tools is that they support at
> least four different data plane technologies (native IP, vanilla MPLS,
> MPLS-TP and PWE) and note that in several cases the data plane
> technologies rely on distinct (IP-based) management channels to allow
> the information gleaned by the operations in the the data plane to be
> reported back to the application that originated the operation.
>
>
> Minor (or at least less major) issues:
>
> s1, para1: For consistency with  the abstract, s1.1 .. and because I'd
> expect OAM to handle it as well ... OAM deals with performance
> monitoring and statistics gathering as well as dealing with degradation.
>
> s1.1: The section is entitled building blocks but actually only mentions
> one block, i.e., the OAM protocol.  Presumably this section really ought
> to say something about the applications and device drivers that have to
> instantiated in the MPs.  In particular as introduction to the text in
> the following section it should say something about classifying
> applications into continuously running or proactive monitoring and
> on-demand applications (since the latter are introduced without any
> definition in the next section.)
>
>
> s2.2.2/3: I am not familiar with 802.1 management issues and I was
> rather confused by the logical status of MIPs .  The text here seems to
> indicate that they are intermediate and generally don't terminate
> messages but then says in s2.2.3 that messages are 'destined to' MIPs.
> Looking for some additional understanding, I fetched up at Wikipedia
> (now there's a surprise) http://en.wikipedia.org/wiki/IEEE_802.1ag.
> This page mentions the concept of maintenance domains and the
> explanation of MIPs as internal points in the domain that generally
> forward messages within the domain whereas end points (MEPs) are
> effectively on the domain boundary. This makes a whole lot more sense
> and seemed to be a rather better set of term definitions than we have in
> this draft.
> I noticed eventually that the term Management Domain (MD) had appeared
> in the first line of s1.1 but does not appear in s2 at all. If we are
> going to accept the Management Domain terminology set, then MD certainly
> ought to be defined and discussed here.
>
>
> s2.2.3, para1, sentence 1:
>>    either initiates or reacts to OAM messages.
> The following sentences contradict this.  Should be 'initiates and/or
> reacts to OAM messages'.  See comment above.
>
> s3, general: The level of detail regarding the various toolsets is not
> very even.  In particular, the MPLS-TP toolset gets significantly more
> attention than others and the detail in OWAMP/TWAMP may be more than is
> desirable for an overview.
>
> s3.1: A few words about the likely suppression of pings and traceroute
> messages due to ICMP filtering is probably desirable as these limit
> their usefulness in the wider Internet.
>
> s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
> the list in s1.4 but is not mentioned here.
>
> s3.4.1: Talking about what the MPLS working group 'is currently doing'
> will not be helpful for an archival document.
>
> s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean
> RFC 6426 which appears to be the TP variant?
>
> Nits/editorial comments:
> General: For a reader who wants to go on and look at the RFCs that
> define the various tools, it would probably be helpful to use reference
> tags that  either are or include the RFC number.
> s1.3, para 2: s/in several fronts/covering several different approaches/
>
> s2.2.2, last para: Need to expand 'p2mp'.
>
> s3.4.3.8: Should this section reference RFC6375?
>
> s3.5.1: It appears that the basic AC acronym (associated channel) is not
> defined.
>
>


--------------080008020208000101050801
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">Elwyn,<br>
      <br>
      Thanks for your review.<br>
      I don't plan to reply for the authors (btw, not sure I've seen a
      reply to this), and but a few clarification questions in line, to
      engage the discussion.<br>
      <br>
    </div>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<a class="moz-txt-link-rfc2396E" href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.

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

Document: draft-ietf-opsawg-oam-overview-08.txt
Reviewer: Elwyn Davies
Review Date: 22 Jan 2013
IETF LC End Date:25 Jan 2013
IESG Telechat date: (if known) -

Summary: In my opinion, this draft has serious issues as described
below.

Major issues:
General 1: Title vs Abstract vs Section 1 vs actual content:

Here in the UK a well-known brand of varnishes and wood preservative
paints uses the slogan 'Does what it says on the tin!'.  If my
understanding and the write-up in RFC 6491, OAM covers a whole lot more
than the coverage of the specific mechanisms discussed in this
document .. and there are various other mechanisms such as SNMP and
Netconf that support the OAM constellation.  </pre>
    </blockquote>
    Can you provide an example of what you mean here?<br>
    Do you mean that SNMP (and NETCONF) can be used to monitor the OAM
    results?<br>
    <br>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">I would take the view that
this document certainly does not 'do what it says on the tin'.
Accordingly I take issue with the title as it doesn't provide a total
overview of OAM mechanisms; the abstract closes down the scope of OAM as
compared with RFC 6491 and s1 restricts it even more - and certainly
does not summarize all the OAM tools and mechanisms defined in the IETF.</pre>
    </blockquote>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">
The last para of s1 claims that 'management aspects are outside the
scope of this document' - if this is really saying that this 'overview'
of OAM skips the whole M aspect of OAM then I'm afraid the document is
badly misnamed.  And it significantly reduces the value of the work.</pre>
    </blockquote>
    Ok, the document title could be improved.<br>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">

General (2): The intended purpose of this document: Back in 2011 Stewart
Bryant summarized a review of a previous version of this document from
the routing directorate
(<a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/">https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/</a> entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.</pre>
    </blockquote>
    This sentence was added:<br>
    <blockquote>
      <pre>  The target audience of this document includes network equipment
   vendors, network operators and standard development organizations,
   and can be used as an index to some of the main OAM tools defined in
   the IETF.

</pre>
    </blockquote>
    And section 1.2<br>
    <pre class="newpage"><span class="h3"><h3><a class="selflink" name="section-1.2" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-13#section-1.2">1.2</a>. Target Audience</h3></span>

   The target audience of this document includes:

   o Standard development organizations - both IETF working groups and
      non-IETF organizations can benefit from this document when
      designing new OAM protocols, or when looking to reuse existing OAM
      tools for new technologies.

   o Network equipment vendors and network operators - can use this
      document as an index to some of the common IETF OAM tools.

   It should be noted that this document is not necessarily suitable for
   beginners without any background in OAM.</pre>
    <br>
    Please let the authors know what you would like to see.<br>
    <br>
    I let the authors/doc. shepherd answer the following points.<br>
    <br>
    Regards, Benoit <br>
    <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
      type="cite">
      <pre wrap="">

General (3): I don't know if Scott Bradner has actually produced a proto
shpeherd write up, but I would be intrigued to know the level of
concensus behind this document.  In particular the tool classification
in s1.1 and terminology in s2 (particularly s2.2.2) is that used
exclusively in the MPLS-TP work in the IETF which is derived from the
802.1ag terminology.  The terminology is presented as if it is common to
OAM work across the IETF. Does the IETF management community at large
concur with this expansion of the applicability of the terminology set
based on 'Management Domains' etc?

General (4): As an overview, I think it would be advisable to point out
that one reason for the multiplicity of tools is that they support at
least four different data plane technologies (native IP, vanilla MPLS,
MPLS-TP and PWE) and note that in several cases the data plane
technologies rely on distinct (IP-based) management channels to allow
the information gleaned by the operations in the the data plane to be
reported back to the application that originated the operation. 


Minor (or at least less major) issues:

s1, para1: For consistency with  the abstract, s1.1 .. and because I'd 
expect OAM to handle it as well ... OAM deals with performance 
monitoring and statistics gathering as well as dealing with degradation.

s1.1: The section is entitled building blocks but actually only mentions 
one block, i.e., the OAM protocol.  Presumably this section really ought 
to say something about the applications and device drivers that have to 
instantiated in the MPs.  In particular as introduction to the text in 
the following section it should say something about classifying 
applications into continuously running or proactive monitoring and 
on-demand applications (since the latter are introduced without any 
definition in the next section.)


s2.2.2/3: I am not familiar with 802.1 management issues and I was 
rather confused by the logical status of MIPs .  The text here seems to 
indicate that they are intermediate and generally don't terminate 
messages but then says in s2.2.3 that messages are 'destined to' MIPs.  
Looking for some additional understanding, I fetched up at Wikipedia 
(now there's a surprise) <a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/IEEE_802.1ag">http://en.wikipedia.org/wiki/IEEE_802.1ag</a>.  
This page mentions the concept of maintenance domains and the 
explanation of MIPs as internal points in the domain that generally 
forward messages within the domain whereas end points (MEPs) are 
effectively on the domain boundary. This makes a whole lot more sense
and seemed to be a rather better set of term definitions than we have in
this draft.  
I noticed eventually that the term Management Domain (MD) had appeared
in the first line of s1.1 but does not appear in s2 at all. If we are
going to accept the Management Domain terminology set, then MD certainly
ought to be defined and discussed here.   


s2.2.3, para1, sentence 1:
</pre>
      <blockquote type="cite">
        <pre wrap="">  either initiates or reacts to OAM messages.
</pre>
      </blockquote>
      <pre wrap="">The following sentences contradict this.  Should be 'initiates and/or 
reacts to OAM messages'.  See comment above.

s3, general: The level of detail regarding the various toolsets is not
very even.  In particular, the MPLS-TP toolset gets significantly more
attention than others and the detail in OWAMP/TWAMP may be more than is
desirable for an overview.

s3.1: A few words about the likely suppression of pings and traceroute 
messages due to ICMP filtering is probably desirable as these limit
their usefulness in the wider Internet.

s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
the list in s1.4 but is not mentioned here.

s3.4.1: Talking about what the MPLS working group 'is currently doing' 
will not be helpful for an archival document.

s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean 
RFC 6426 which appears to be the TP variant?

Nits/editorial comments:
General: For a reader who wants to go on and look at the RFCs that 
define the various tools, it would probably be helpful to use reference 
tags that  either are or include the RFC number.
s1.3, para 2: s/in several fronts/covering several different approaches/

s2.2.2, last para: Need to expand 'p2mp'.

s3.4.3.8: Should this section reference RFC6375?

s3.5.1: It appears that the basic AC acronym (associated channel) is not 
defined.


</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------080008020208000101050801--


From nobody Tue Feb 18 03:09:25 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 B78C41A0453; Tue, 18 Feb 2014 03:09:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.048
X-Spam-Level: 
X-Spam-Status: No, score=-10.048 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, RP_MATCHES_RCVD=-0.548, 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 Z2nIa9fyMbCR; Tue, 18 Feb 2014 03:09:19 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) by ietfa.amsl.com (Postfix) with ESMTP id B6C611A03D0; Tue, 18 Feb 2014 03:09:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=19630; q=dns/txt; s=iport; t=1392721755; x=1393931355; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=yxNVQbN/w0Wv35HuMiPOmBIDEc7oVTmi6uBjO778dzE=; b=I6zfaym0ubhqfVWUi3eqSzM6OW63nDj9I6o4hAps5AmRSzEYArO+XT8u K1v0JaYLoWCLmLiQCKO0OHC5Uz5CqmJDZWvQyB8FK1yWhURCTaVYwqRLT LnTo8BDKy64atCAU1Trl1VDD/kpiBlKG15L/fps0lV6oeUeGYK63qsCKE s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmsFANE+A1OQ/khR/2dsb2JhbABZgwY4iTa2cYEWFnSCJgEBBHgBEAsUDRYPCQMCAQIBRQYBDAEHAQEQh3ENyzMXjQqBFQsGAT8RB4Q4BJgsgTKFFYtcgy47gS0IFw
X-IronPort-AV: E=Sophos;i="4.97,501,1389744000"; d="scan'208,217";a="4718286"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-2.cisco.com with ESMTP; 18 Feb 2014 11:09:13 +0000
Received: from [10.60.67.85] (ams-bclaise-8914.cisco.com [10.60.67.85]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1IB9D0o004703; Tue, 18 Feb 2014 11:09:13 GMT
Message-ID: <53033F59.9010000@cisco.com>
Date: Tue, 18 Feb 2014 12:09:13 +0100
From: Benoit Claise <bclaise@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Elwyn Davies <elwynd@dial.pipex.com>, General Area Review Team <gen-art@ietf.org>, Tal Mizrahi <talmi@marvell.com>
Subject: Re: Gen-art last call review of draft-ietf-opsawg-oam-overview-08.txt
References: <1358863845.28723.19076.camel@mightyatom> <53033CE5.2000309@cisco.com>
In-Reply-To: <53033CE5.2000309@cisco.com>
Content-Type: multipart/alternative; boundary="------------080003090707070005040706"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/qF6kE_xG_ui_ObL9XT-xl2ibfVU
Cc: "opsawg@ietf.org" <opsawg@ietf.org>, IETF discussion <ietf@ietf.org>, draft-ietf-opsawg-oam-overview.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Feb 2014 11:09:21 -0000

This is a multi-part message in MIME format.
--------------080003090707070005040706
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Elwyn,

Please disregard this email. I wrongly read the date: 22/01/2014 instead 
of 22/01/2013.
My understanding is that the points have been addressed in the version 13.

Regards, Benoit
> Elwyn,
>
> Thanks for your review.
> I don't plan to reply for the authors (btw, not sure I've seen a reply 
> to this), and but a few clarification questions in line, to engage the 
> discussion.
>
>> 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-opsawg-oam-overview-08.txt
>> Reviewer: Elwyn Davies
>> Review Date: 22 Jan 2013
>> IETF LC End Date:25 Jan 2013
>> IESG Telechat date: (if known) -
>>
>> Summary: In my opinion, this draft has serious issues as described
>> below.
>>
>> Major issues:
>> General 1: Title vs Abstract vs Section 1 vs actual content:
>>
>> Here in the UK a well-known brand of varnishes and wood preservative
>> paints uses the slogan 'Does what it says on the tin!'.  If my
>> understanding and the write-up in RFC 6491, OAM covers a whole lot more
>> than the coverage of the specific mechanisms discussed in this
>> document .. and there are various other mechanisms such as SNMP and
>> Netconf that support the OAM constellation.
> Can you provide an example of what you mean here?
> Do you mean that SNMP (and NETCONF) can be used to monitor the OAM 
> results?
>
>> I would take the view that
>> this document certainly does not 'do what it says on the tin'.
>> Accordingly I take issue with the title as it doesn't provide a total
>> overview of OAM mechanisms; the abstract closes down the scope of OAM as
>> compared with RFC 6491 and s1 restricts it even more - and certainly
>> does not summarize all the OAM tools and mechanisms defined in the IETF.
>> The last para of s1 claims that 'management aspects are outside the
>> scope of this document' - if this is really saying that this 'overview'
>> of OAM skips the whole M aspect of OAM then I'm afraid the document is
>> badly misnamed.  And it significantly reduces the value of the work.
> Ok, the document title could be improved.
>> General (2): The intended purpose of this document: Back in 2011 Stewart
>> Bryant summarized a review of a previous version of this document from
>> the routing directorate
>> (https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/  entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.
> This sentence was added:
>
>        The target audience of this document includes network equipment
>         vendors, network operators and standard development organizations,
>         and can be used as an index to some of the main OAM tools defined in
>         the IETF.
>
> And section 1.2
>
>
>       1.2
>       <http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-13#section-1.2>.
>       Target Audience
>
>
>
>     The target audience of this document includes:
>
>     o Standard development organizations - both IETF working groups and
>        non-IETF organizations can benefit from this document when
>        designing new OAM protocols, or when looking to reuse existing OAM
>        tools for new technologies.
>
>     o Network equipment vendors and network operators - can use this
>        document as an index to some of the common IETF OAM tools.
>
>     It should be noted that this document is not necessarily suitable for
>     beginners without any background in OAM.
>
> Please let the authors know what you would like to see.
>
> I let the authors/doc. shepherd answer the following points.
>
> Regards, Benoit
>> General (3): I don't know if Scott Bradner has actually produced a proto
>> shpeherd write up, but I would be intrigued to know the level of
>> concensus behind this document.  In particular the tool classification
>> in s1.1 and terminology in s2 (particularly s2.2.2) is that used
>> exclusively in the MPLS-TP work in the IETF which is derived from the
>> 802.1ag terminology.  The terminology is presented as if it is common to
>> OAM work across the IETF. Does the IETF management community at large
>> concur with this expansion of the applicability of the terminology set
>> based on 'Management Domains' etc?
>>
>> General (4): As an overview, I think it would be advisable to point out
>> that one reason for the multiplicity of tools is that they support at
>> least four different data plane technologies (native IP, vanilla MPLS,
>> MPLS-TP and PWE) and note that in several cases the data plane
>> technologies rely on distinct (IP-based) management channels to allow
>> the information gleaned by the operations in the the data plane to be
>> reported back to the application that originated the operation.
>>
>>
>> Minor (or at least less major) issues:
>>
>> s1, para1: For consistency with  the abstract, s1.1 .. and because I'd
>> expect OAM to handle it as well ... OAM deals with performance
>> monitoring and statistics gathering as well as dealing with degradation.
>>
>> s1.1: The section is entitled building blocks but actually only mentions
>> one block, i.e., the OAM protocol.  Presumably this section really ought
>> to say something about the applications and device drivers that have to
>> instantiated in the MPs.  In particular as introduction to the text in
>> the following section it should say something about classifying
>> applications into continuously running or proactive monitoring and
>> on-demand applications (since the latter are introduced without any
>> definition in the next section.)
>>
>>
>> s2.2.2/3: I am not familiar with 802.1 management issues and I was
>> rather confused by the logical status of MIPs .  The text here seems to
>> indicate that they are intermediate and generally don't terminate
>> messages but then says in s2.2.3 that messages are 'destined to' MIPs.
>> Looking for some additional understanding, I fetched up at Wikipedia
>> (now there's a surprise)http://en.wikipedia.org/wiki/IEEE_802.1ag.
>> This page mentions the concept of maintenance domains and the
>> explanation of MIPs as internal points in the domain that generally
>> forward messages within the domain whereas end points (MEPs) are
>> effectively on the domain boundary. This makes a whole lot more sense
>> and seemed to be a rather better set of term definitions than we have in
>> this draft.
>> I noticed eventually that the term Management Domain (MD) had appeared
>> in the first line of s1.1 but does not appear in s2 at all. If we are
>> going to accept the Management Domain terminology set, then MD certainly
>> ought to be defined and discussed here.
>>
>>
>> s2.2.3, para1, sentence 1:
>>>    either initiates or reacts to OAM messages.
>> The following sentences contradict this.  Should be 'initiates and/or
>> reacts to OAM messages'.  See comment above.
>>
>> s3, general: The level of detail regarding the various toolsets is not
>> very even.  In particular, the MPLS-TP toolset gets significantly more
>> attention than others and the detail in OWAMP/TWAMP may be more than is
>> desirable for an overview.
>>
>> s3.1: A few words about the likely suppression of pings and traceroute
>> messages due to ICMP filtering is probably desirable as these limit
>> their usefulness in the wider Internet.
>>
>> s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
>> the list in s1.4 but is not mentioned here.
>>
>> s3.4.1: Talking about what the MPLS working group 'is currently doing'
>> will not be helpful for an archival document.
>>
>> s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean
>> RFC 6426 which appears to be the TP variant?
>>
>> Nits/editorial comments:
>> General: For a reader who wants to go on and look at the RFCs that
>> define the various tools, it would probably be helpful to use reference
>> tags that  either are or include the RFC number.
>> s1.3, para 2: s/in several fronts/covering several different approaches/
>>
>> s2.2.2, last para: Need to expand 'p2mp'.
>>
>> s3.4.3.8: Should this section reference RFC6375?
>>
>> s3.5.1: It appears that the basic AC acronym (associated channel) is not
>> defined.
>>
>>
>


--------------080003090707070005040706
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">Elwyn,<br>
      <br>
      Please disregard this email. I wrongly read the date: 22/01/2014
      instead of 22/01/2013.<br>
      My understanding is that the points have been addressed in the
      version 13.<br>
      <br>
      Regards, Benoit<br>
    </div>
    <blockquote cite="mid:53033CE5.2000309@cisco.com" type="cite">
      <meta http-equiv="Content-Type" content="text/html;
        charset=ISO-8859-1">
      <div class="moz-cite-prefix">Elwyn,<br>
        <br>
        Thanks for your review.<br>
        I don't plan to reply for the authors (btw, not sure I've seen a
        reply to this), and but a few clarification questions in line,
        to engage the discussion.<br>
        <br>
      </div>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at

<a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq">&lt;http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq&gt;</a>.

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

Document: draft-ietf-opsawg-oam-overview-08.txt
Reviewer: Elwyn Davies
Review Date: 22 Jan 2013
IETF LC End Date:25 Jan 2013
IESG Telechat date: (if known) -

Summary: In my opinion, this draft has serious issues as described
below.

Major issues:
General 1: Title vs Abstract vs Section 1 vs actual content:

Here in the UK a well-known brand of varnishes and wood preservative
paints uses the slogan 'Does what it says on the tin!'.  If my
understanding and the write-up in RFC 6491, OAM covers a whole lot more
than the coverage of the specific mechanisms discussed in this
document .. and there are various other mechanisms such as SNMP and
Netconf that support the OAM constellation.  </pre>
      </blockquote>
      Can you provide an example of what you mean here?<br>
      Do you mean that SNMP (and NETCONF) can be used to monitor the OAM
      results?<br>
      <br>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">I would take the view that
this document certainly does not 'do what it says on the tin'.
Accordingly I take issue with the title as it doesn't provide a total
overview of OAM mechanisms; the abstract closes down the scope of OAM as
compared with RFC 6491 and s1 restricts it even more - and certainly
does not summarize all the OAM tools and mechanisms defined in the IETF.</pre>
      </blockquote>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">The last para of s1 claims that 'management aspects are outside the
scope of this document' - if this is really saying that this 'overview'
of OAM skips the whole M aspect of OAM then I'm afraid the document is
badly misnamed.  And it significantly reduces the value of the work.</pre>
      </blockquote>
      Ok, the document title could be improved.<br>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">
General (2): The intended purpose of this document: Back in 2011 Stewart
Bryant summarized a review of a previous version of this document from
the routing directorate
(<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/">https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-overview/history/</a> entry dated 2011-08-10 referring to version 05 of the document).  IMO the initial section of that review regarding the audience of this document was well targeted and *has not been fixed*.  If this is intended as an introductory overview for people wishing to see what OAM is about in the IETF then it needs further introductory text and some background.  It should also state what its target audience actually is.</pre>
      </blockquote>
      This sentence was added:<br>
      <blockquote>
        <pre>  The target audience of this document includes network equipment
   vendors, network operators and standard development organizations,
   and can be used as an index to some of the main OAM tools defined in
   the IETF.

</pre>
      </blockquote>
      And section 1.2<br>
      <pre class="newpage"><span class="h3"><h3><a moz-do-not-send="true" class="selflink" name="section-1.2" href="http://tools.ietf.org/html/draft-ietf-opsawg-oam-overview-13#section-1.2">1.2</a>. Target Audience</h3></span>

   The target audience of this document includes:

   o Standard development organizations - both IETF working groups and
      non-IETF organizations can benefit from this document when
      designing new OAM protocols, or when looking to reuse existing OAM
      tools for new technologies.

   o Network equipment vendors and network operators - can use this
      document as an index to some of the common IETF OAM tools.

   It should be noted that this document is not necessarily suitable for
   beginners without any background in OAM.</pre>
      <br>
      Please let the authors know what you would like to see.<br>
      <br>
      I let the authors/doc. shepherd answer the following points.<br>
      <br>
      Regards, Benoit <br>
      <blockquote cite="mid:1358863845.28723.19076.camel@mightyatom"
        type="cite">
        <pre wrap="">
General (3): I don't know if Scott Bradner has actually produced a proto
shpeherd write up, but I would be intrigued to know the level of
concensus behind this document.  In particular the tool classification
in s1.1 and terminology in s2 (particularly s2.2.2) is that used
exclusively in the MPLS-TP work in the IETF which is derived from the
802.1ag terminology.  The terminology is presented as if it is common to
OAM work across the IETF. Does the IETF management community at large
concur with this expansion of the applicability of the terminology set
based on 'Management Domains' etc?

General (4): As an overview, I think it would be advisable to point out
that one reason for the multiplicity of tools is that they support at
least four different data plane technologies (native IP, vanilla MPLS,
MPLS-TP and PWE) and note that in several cases the data plane
technologies rely on distinct (IP-based) management channels to allow
the information gleaned by the operations in the the data plane to be
reported back to the application that originated the operation. 


Minor (or at least less major) issues:

s1, para1: For consistency with  the abstract, s1.1 .. and because I'd 
expect OAM to handle it as well ... OAM deals with performance 
monitoring and statistics gathering as well as dealing with degradation.

s1.1: The section is entitled building blocks but actually only mentions 
one block, i.e., the OAM protocol.  Presumably this section really ought 
to say something about the applications and device drivers that have to 
instantiated in the MPs.  In particular as introduction to the text in 
the following section it should say something about classifying 
applications into continuously running or proactive monitoring and 
on-demand applications (since the latter are introduced without any 
definition in the next section.)


s2.2.2/3: I am not familiar with 802.1 management issues and I was 
rather confused by the logical status of MIPs .  The text here seems to 
indicate that they are intermediate and generally don't terminate 
messages but then says in s2.2.3 that messages are 'destined to' MIPs.  
Looking for some additional understanding, I fetched up at Wikipedia 
(now there's a surprise) <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/IEEE_802.1ag">http://en.wikipedia.org/wiki/IEEE_802.1ag</a>.  
This page mentions the concept of maintenance domains and the 
explanation of MIPs as internal points in the domain that generally 
forward messages within the domain whereas end points (MEPs) are 
effectively on the domain boundary. This makes a whole lot more sense
and seemed to be a rather better set of term definitions than we have in
this draft.  
I noticed eventually that the term Management Domain (MD) had appeared
in the first line of s1.1 but does not appear in s2 at all. If we are
going to accept the Management Domain terminology set, then MD certainly
ought to be defined and discussed here.   


s2.2.3, para1, sentence 1:
</pre>
        <blockquote type="cite">
          <pre wrap="">  either initiates or reacts to OAM messages.
</pre>
        </blockquote>
        <pre wrap="">The following sentences contradict this.  Should be 'initiates and/or 
reacts to OAM messages'.  See comment above.

s3, general: The level of detail regarding the various toolsets is not
very even.  In particular, the MPLS-TP toolset gets significantly more
attention than others and the detail in OWAMP/TWAMP may be more than is
desirable for an overview.

s3.1: A few words about the likely suppression of pings and traceroute 
messages due to ICMP filtering is probably desirable as these limit
their usefulness in the wider Internet.

s3.3: What about RFC6374 (MPLS packet loss measurement)? It appears in
the list in s1.4 but is not mentioned here.

s3.4.1: Talking about what the MPLS working group 'is currently doing' 
will not be helpful for an archival document.

s3.4.3.1: The OnDemand-CV reference is for non-TP MPLS... do you mean 
RFC 6426 which appears to be the TP variant?

Nits/editorial comments:
General: For a reader who wants to go on and look at the RFCs that 
define the various tools, it would probably be helpful to use reference 
tags that  either are or include the RFC number.
s1.3, para 2: s/in several fronts/covering several different approaches/

s2.2.2, last para: Need to expand 'p2mp'.

s3.4.3.8: Should this section reference RFC6375?

s3.5.1: It appears that the basic AC acronym (associated channel) is not 
defined.


</pre>
      </blockquote>
      <br>
    </blockquote>
    <br>
  </body>
</html>

--------------080003090707070005040706--


From nobody Tue Feb 18 07:32:51 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 8C4C91A0697 for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 07:32:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Rv0ugWGA6vgd for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 07:32:44 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id F328D1A01E2 for <ietf@ietf.org>; Tue, 18 Feb 2014 07:32:35 -0800 (PST)
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 500611B8175 for <ietf@ietf.org>; Tue, 18 Feb 2014 07:32:33 -0800 (PST)
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 4935C190052; Tue, 18 Feb 2014 07:32:33 -0800 (PST)
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, 18 Feb 2014 07:32:33 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Internet organisations coordination meeting
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <CAF4+nEGd2eA+T+i-ZH=1=Aku=iB-mjTZ=3z-1eEa6jtKgY+kTA@mail.gmail.com>
Date: Tue, 18 Feb 2014 10:32:29 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4C35759C-2BF2-487E-A2DB-FDEBF4C32711@nominum.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <201402172245.s1HMjNmi5224677@shell01.TheWorld.com> <CAF4+nEGd2eA+T+i-ZH=1=Aku=iB-mjTZ=3z-1eEa6jtKgY+kTA@mail.gmail.com>
To: Donald Eastlake <d3e3e3@gmail.com>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/a9C7MxcaBYQJUIpQiDMZkuCjd_M
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, 18 Feb 2014 15:32:49 -0000

On Feb 17, 2014, at 6:10 PM, Donald Eastlake <d3e3e3@gmail.com> wrote:
>   factotum

This may have been intended as tongue-in-cheek, but just in case you are =
serious, no, this is not what IETF "leaders" do, so the word isn't =
appropriate.   That is, we are active participants in the community who =
are responsible for things like facilitating and evaluating the =
consensus process and deciding what work we are willing to do within our =
areas.   There's a great deal more agency here than "factotum" implies.

Really, the notion that leaders are bosses or controllers is mistaken.   =
Even in organizations where leaders perform these roles, it's because =
the participants in the organization decide to follow them to a greater =
or lesser degree, not because they exert any actual control.   The term =
for a person who uses coercion to establish control is "despot," not =
"leader."

My personal experience as an IETF "leader" is that I listen to what =
people say, think about it, occasionally salt it with my own ideas, and =
then repeat it back, and people either agree and go along, or more often =
debate some more.   So to my mind the right term for "leaders" in the =
context of the IETF would be agents provocateurs, but it would probably =
be misinterpreted by the media.

:)


From nobody Tue Feb 18 08:27:10 2014
Return-Path: <jcurran@arin.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 E74D71A0262 for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 11:36:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aIttHiM1eFdX for <ietf@ietfa.amsl.com>; Sun, 16 Feb 2014 11:36:19 -0800 (PST)
Received: from smtp1.arin.net (smtp1.arin.net [IPv6:2001:500:4:13::33]) by ietfa.amsl.com (Postfix) with ESMTP id C10801A025C for <ietf@ietf.org>; Sun, 16 Feb 2014 11:36:18 -0800 (PST)
Received: by smtp1.arin.net (Postfix, from userid 323) id 7945F165291; Sun, 16 Feb 2014 14:36:16 -0500 (EST)
Received: from CHAXCH06.corp.arin.net (chaxch06.corp.arin.net [192.149.252.95]) by smtp1.arin.net (Postfix) with ESMTP id 19749165076; Sun, 16 Feb 2014 14:36:15 -0500 (EST)
Received: from CHAXCH03.corp.arin.net (10.1.30.17) by CHAXCH06.corp.arin.net (192.149.252.95) with Microsoft SMTP Server (TLS) id 14.2.342.3; Sun, 16 Feb 2014 14:36:08 -0500
Received: from CHAXCH01.corp.arin.net ([169.254.1.174]) by CHAXCH03.corp.arin.net ([10.1.30.17]) with mapi id 14.02.0328.009; Sun, 16 Feb 2014 14:36:01 -0500
From: John Curran <jcurran@arin.net>
To: Jorge Amodio <jmamodio@gmail.com>
Subject: Re: Internet organisations coordination meeting
Thread-Topic: Internet organisations coordination meeting
Thread-Index: AQHPK05SKuY0Q9KxoUuTKTxKjwN9kA==
Date: Sun, 16 Feb 2014 19:36:01 +0000
Message-ID: <22E66CB1-0A74-4E8D-A8D4-CEDC5D2B2399@arin.net>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com>
In-Reply-To: <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [192.149.252.96]
Content-Type: multipart/alternative; boundary="_000_22E66CB10A744E8DA8D4CEDC5D2B2399arinnet_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GwJ1hUaE9SwGuxdDZsYyKxaGwvs
X-Mailman-Approved-At: Tue, 18 Feb 2014 08:27:01 -0800
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: Sun, 16 Feb 2014 19:36:22 -0000

--_000_22E66CB10A744E8DA8D4CEDC5D2B2399arinnet_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Jorge -

    This particular group of folks gathered and received updates on various=
 activities
    going on... e.g.  Jari and Russ spoke of perpass.  It is a coordinating=
 function; so
    we know about major initiatives going on and can support and/or avoid c=
onflicts
    as appropriate.

    The only reason for the post-meeting statements (in my view) is simply =
because
    people were unaware that these periodic gatherings were going on, and i=
ndicated
    that we should be make such more visible.

    Note also that there quite a bit of focus on making sure the most recen=
t statement
    simply said what happened, i.e.  a gathering of folks received a series=
 of updates
    from each other on a list of topics of potentially mutual interest.

    As a result, I now realize that W3C is having its 20th anniversary; tha=
t ICANN's
    various strategy panels have been meeting, and that the "Brazil meeting=
" is now
    know as  =93Netmundial=94 and has its own website <http://netmundial.br=
>.   I don't
    really know what the other leaders (for lack of a better term) took awa=
y, but
    would hope that Jari, Russ, etc. found it useful context and background=
 for their
    IETF efforts.    I guess that one option would be for the "leaders" fro=
m the IETF
    community not to attend such gatherings, but that seems to be a rather =
extreme
    response to take due to lack of a better term than "leader" (and one ho=
pes it is
    unnecessary so long as care is taken to make nothing more of the meetin=
gs than
    what they are - a gathering of folks hearing updates so we can better c=
oordinate)

FYI,
/John

On Feb 16, 2014, at 10:58 AM, Jorge Amodio <jmamodio@gmail.com<mailto:jmamo=
dio@gmail.com>> wrote:


I agree that "spokesperson" is not either the appropriate term. And leader =
is far far away to be representative of their roles and positions.

True that on their role they "lead" the organizations they are involved wit=
h but the Internet community does not follow them as *leaders*, particularl=
y the CEOs of some organizations such as ICANN, ARIN, etc, that are just pa=
id employees to play a specific executive role.

I'm really starting to dislike this effort of reverting the bottom-up proce=
ss by a group that is starting to behave like a dictatorial junta making pu=
blic statements that can be considered or interpreted as representative of =
the Internet community and particular organizations such as IETF.

They are no spokesperson, nor leaders, just they are what they are the CEO =
of ICANN, the Chair of IETF, the CEO of ARIN, etc.


My .02
Jorge



On Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <ted.lemon@nominum.com<mailto:te=
d.lemon@nominum.com>> wrote:
Folks, as John Klensin said, the reason we do not say "spokesperson" is tha=
t our leadership do not speak for us.   We only speak as a group through th=
e consensus process.   So the term "spokesperson" is simply inaccurate.

The term "leader" makes sense as a generic because there were a number of o=
rganizations, with different leadership structures, some not involving the =
same consensus process that exists in the IETF.   So we couldn't for exampl=
e say "chair," because that term wouldn't apply to all the people who signe=
d the statement.

I realize that the term "leader" has its own set of connotations, but I don=
't know of a better word to use.   There is no word that we could use that =
would convey to someone who is not already familiar with IETF process what =
we mean.   Representative is no good for the same reason spokesperson is no=
 good.   Avatar doesn't really work either.

I think it's better to just accept that the language is imprecise, and thin=
k carefully about what is that we might be objecting to, and whether the ob=
jection _really_ makes sense in the context.   I guess there's about zero c=
hance that this won't get discussed to death, and that's fine, but I don't =
think there's a knob to turn here.




--_000_22E66CB10A744E8DA8D4CEDC5D2B2399arinnet_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <FEA78A0FDA61854C80B9E5D58AAFA293@corp.arin.net>
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;">
<div>Jorge -&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp; &nbsp; This particular group of folks gathered and received upd=
ates on various activities&nbsp;</div>
<div>&nbsp; &nbsp; going on... e.g. &nbsp;Jari and Russ spoke of perpass. &=
nbsp;It is a coordinating function; so&nbsp;</div>
<div>&nbsp; &nbsp; we know about major initiatives going on and can support=
 and/or avoid conflicts&nbsp;</div>
<div>&nbsp; &nbsp; as appropriate.</div>
<div><br>
</div>
<div>&nbsp; &nbsp; The only reason for the post-meeting statements (in my v=
iew) is simply because&nbsp;</div>
<div>&nbsp; &nbsp; people were unaware that these periodic gatherings were =
going on, and indicated</div>
<div>&nbsp; &nbsp; that we should be make such more visible.</div>
<div><br>
</div>
<div>&nbsp; &nbsp; Note also that there quite a bit of focus on making sure=
 the most recent statement</div>
<div>&nbsp; &nbsp; simply said what happened, i.e. &nbsp;a gathering of fol=
ks received a series of updates&nbsp;</div>
<div>&nbsp; &nbsp; from each other on a list of topics of potentially mutua=
l interest. &nbsp;</div>
<div><br>
</div>
<div>&nbsp; &nbsp; As a result, I now realize that W3C is having its 20th a=
nniversary; that ICANN's</div>
<div>&nbsp; &nbsp; various strategy panels have been meeting, and that the =
&quot;Brazil meeting&quot; is now</div>
<div>&nbsp; &nbsp; know as &nbsp;=93Netmundial=94 and has its own website &=
lt;<a href=3D"http://netmundial.br">http://netmundial.br</a>&gt;. &nbsp; I =
don't&nbsp;</div>
<div>&nbsp; &nbsp; really know what the other leaders (for lack of a better=
 term) took away, but&nbsp;</div>
<div>&nbsp; &nbsp; would hope that Jari, Russ, etc. found it useful context=
 and background for their</div>
<div>&nbsp; &nbsp; IETF efforts. &nbsp; &nbsp;I guess that one option would=
 be for the &quot;leaders&quot; from the IETF</div>
<div>&nbsp; &nbsp; community not to attend such gatherings, but that seems =
to be a rather extreme</div>
<div>&nbsp; &nbsp; response to take due to lack of a better term than &quot=
;leader&quot; (and one hopes it is</div>
<div>&nbsp; &nbsp; unnecessary so long as care is taken to make nothing mor=
e of the meetings than</div>
<div>&nbsp; &nbsp; what they are - a gathering of folks hearing updates so =
we can better coordinate)</div>
<div><br>
</div>
<div>FYI,</div>
<div>/John</div>
<div><br>
</div>
On Feb 16, 2014, at 10:58 AM, Jorge Amodio &lt;<a href=3D"mailto:jmamodio@g=
mail.com">jmamodio@gmail.com</a>&gt; wrote:<br>
<div><br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<div dir=3D"ltr"><br>
<div>I agree that &quot;spokesperson&quot; is not either the appropriate te=
rm. And leader is far far away to be representative of their roles and posi=
tions.</div>
<div><br>
</div>
<div>True that on their role they &quot;lead&quot; the organizations they a=
re involved with but the Internet community does not follow them as *leader=
s*, particularly the CEOs of some organizations such as ICANN, ARIN, etc, t=
hat are just paid employees to play a specific
 executive role.</div>
<div><br>
</div>
<div>I'm really starting to dislike this effort of reverting the bottom-up =
process by a group that is starting to behave like a dictatorial junta maki=
ng public statements that can be considered or interpreted as representativ=
e of the Internet community and
 particular organizations such as IETF.</div>
<div><br>
</div>
<div>They are no spokesperson, nor leaders, just they are what they are the=
 CEO of ICANN, the Chair of IETF, the CEO of ARIN, etc.</div>
<div><br>
</div>
<div><br>
</div>
<div>My .02</div>
<div>Jorge</div>
<div><br>
</div>
</div>
<div class=3D"gmail_extra"><br>
<br>
<div class=3D"gmail_quote">On Sun, Feb 16, 2014 at 6:20 AM, Ted Lemon <span=
 dir=3D"ltr">
&lt;<a href=3D"mailto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@no=
minum.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">
Folks, as John Klensin said, the reason we do not say &quot;spokesperson&qu=
ot; is that our leadership do not speak for us. &nbsp; We only speak as a g=
roup through the consensus process. &nbsp; So the term &quot;spokesperson&q=
uot; is simply inaccurate.<br>
<br>
The term &quot;leader&quot; makes sense as a generic because there were a n=
umber of organizations, with different leadership structures, some not invo=
lving the same consensus process that exists in the IETF. &nbsp; So we coul=
dn't for example say &quot;chair,&quot; because that term
 wouldn't apply to all the people who signed the statement.<br>
<br>
I realize that the term &quot;leader&quot; has its own set of connotations,=
 but I don't know of a better word to use. &nbsp; There is no word that we =
could use that would convey to someone who is not already familiar with IET=
F process what we mean. &nbsp; Representative is no
 good for the same reason spokesperson is no good. &nbsp; Avatar doesn't re=
ally work either.<br>
<br>
I think it's better to just accept that the language is imprecise, and thin=
k carefully about what is that we might be objecting to, and whether the ob=
jection _really_ makes sense in the context. &nbsp; I guess there's about z=
ero chance that this won't get discussed
 to death, and that's fine, but I don't think there's a knob to turn here.<=
br>
<br>
</blockquote>
</div>
<br>
</div>
</blockquote>
</div>
<br>
</body>
</html>

--_000_22E66CB10A744E8DA8D4CEDC5D2B2399arinnet_--


From nobody Tue Feb 18 08:27:18 2014
Return-Path: <paul@nohats.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 3D2591A0211 for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 07:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 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.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BrqSK-TZThpK for <ietf@ietfa.amsl.com>; Mon, 17 Feb 2014 07:25:06 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) by ietfa.amsl.com (Postfix) with ESMTP id 685A01A020C for <ietf@ietf.org>; Mon, 17 Feb 2014 07:25:06 -0800 (PST)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 20588800AA; Mon, 17 Feb 2014 10:25:02 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1392650702; bh=kwl0vAh3G3cxJUOGn7cwHh3qwKCzUKGAzyBRQJGImA4=; h=Date:From:To:cc:Subject; b=a0kC8PHqFGPr3flKyInPla7JaQWT88BXZU/psVbLej3YuO4SDMX7vl6nstTFElqVm PD7TA9du9LPyH0EZRAlzRT9Wpn6zumqEINeO8c6TWLxJchdEFMMiK1F1LevE1cHV8X SVAeWsvqk7igOW//ia06D20cDZmzvXS7iuq1WoaU=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s1HFP0mF005332; Mon, 17 Feb 2014 10:25:00 -0500
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Mon, 17 Feb 2014 10:25:00 -0500 (EST)
From: Paul Wouters <paul@nohats.ca>
To: ietf@ietf.org
Subject: broken tools.ietf.org configuration results in 5xx permentant failure?
Message-ID: <alpine.LFD.2.10.1402171018340.4876@bofh.nohats.ca>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/T4u9p0hIZg2Qspq07Yw3JOYujBA
X-Mailman-Approved-At: Tue, 18 Feb 2014 08:27:16 -0800
Cc: John Gilmore <gnu@toad.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, 17 Feb 2014 15:25:09 -0000

Looks like someone screwed up the configuration of MX servers of
tools.ietf.org?

Please fix,

Paul

The original message was received at Mon, 17 Feb 2014 07:31:26 -0800
from localhost.localdomain [127.0.0.1]

    ----- The following addresses had permanent fatal errors -----
<draft-ietf-tls-oob-pubkey@tools.ietf.org>
     (reason: 550 Rejected)
<tls-chairs@tools.ietf.org>
     (reason: 550 Rejected)
<tls-ads@tools.ietf.org>
     (reason: 550 Rejected)

    ----- Transcript of session follows -----
... while talking to pechora4.icann.org.:
>>> DATA
<<< 451 4.7.1 Greylisting in action, please come back later
<drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
<<< 503 5.0.0 Need RCPT (recipient)
... while talking to pechora3.icann.org.:
>>> DATA
<<< 451 4.7.1 Greylisting in action, please come back later
<drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
<<< 503 5.0.0 Need RCPT (recipient)
... while talking to pechora5.icann.org.:
>>> DATA
<<< 451 4.7.1 Greylisting in action, please come back later
<drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
<<< 503 5.0.0 Need RCPT (recipient)
... while talking to pechora7.icann.org.:
>>> DATA
<<< 451 4.7.1 Greylisting in action, please come back later
<drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
<<< 503 5.0.0 Need RCPT (recipient)
... while talking to pechora1.icann.org.:
>>> DATA
<<< 451 4.7.1 Greylisting in action, please come back later
<drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
<<< 503 5.0.0 Need RCPT (recipient)
... while talking to pechora8.icann.org.:
>>> DATA
<<< 451 4.7.1 Greylisting in action, please come back later
<drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
<<< 503 5.0.0 Need RCPT (recipient)
... while talking to grenache.tools.ietf.org.:
>>> DATA
<<< 451 Please try again later
... while talking to gamay.tools.ietf.org.:
>>> DATA
<<< 550 Rejected
554 5.0.0 Service unavailable


From nobody Tue Feb 18 08:27:38 2014
Return-Path: <prvs=118abc007=schmidt@informatik.haw-hamburg.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 1DE2C1A047F; Mon, 17 Feb 2014 02:41:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MuszvDscQ6bd; Mon, 17 Feb 2014 02:41:16 -0800 (PST)
Received: from mx3.haw-public.haw-hamburg.de (mx3.haw-public.haw-hamburg.de [141.22.6.2]) by ietfa.amsl.com (Postfix) with ESMTP id 8AD501A01CA; Mon, 17 Feb 2014 02:41:15 -0800 (PST)
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail3.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 17 Feb 2014 11:41:12 +0100
Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 423B210679D7; Mon, 17 Feb 2014 11:41:12 +0100 (CET)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1]) by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 13124-09; Mon, 17 Feb 2014 11:41:11 +0100 (CET)
Received: from [172.27.31.57] (unknown [195.37.142.72]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPSA id 7014310679CF;  Mon, 17 Feb 2014 11:41:11 +0100 (CET)
Message-ID: <5301E745.6020109@informatik.haw-hamburg.de>
Date: Mon, 17 Feb 2014 11:41:09 +0100
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>,  "shgao@bjtu.edu.cn" <shgao@bjtu.edu.cn>, "hkzhang@bjtu.edu.cn" <hkzhang@bjtu.edu.cn>,  "mw@link-lab.net" <mw@link-lab.net>, "General Area Review Team (gen-art@ietf.org)" <gen-art@ietf.org>
Subject: Re: Gen-ART review of draft-ietf-multimob-pmipv6-source-07
References: <8D3D17ACE214DC429325B2B98F3AE712027281E4CC@MX15A.corp.emc.com>
In-Reply-To: <8D3D17ACE214DC429325B2B98F3AE712027281E4CC@MX15A.corp.emc.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tfMUDbuaX7SrGgWM24OwNRKgNyE
X-Mailman-Approved-At: Tue, 18 Feb 2014 08:27:37 -0800
Cc: "multimob@ietf.org" <multimob@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, 17 Feb 2014 10:41:20 -0000

Hi David,

many thanks for the review and the feedback.

Please see responses inline.

On 17.02.2014 04:22, Black, David 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-multimob-pmipv6-source-07
> Reviewer: David L. Black
> Review Date: Feb 16, 2014
> IETF LC End Date: Feb 24, 2014
>
> Summary: This draft is basically ready for publication, but has nits that
> should be fixed before publication.
>
> This draft describes multicast support for proxy mobile IPv6.  It assumes
> significant understanding of multicast and specifically the PIM-SM protocol.
>
> Nits/editorial comments:
>
> -- Introduction, 3rd paragraph
>
> Remove the word business from the following text, please:
>
>               Such approaches (partially) follow
>     the business model of providing multicast data services in parallel
>     to PMIPv6 unicast routing [I-D.ietf-multimob-handover-optimization].
>

O.K., done.

> -- 4.3.1
>
> The fact that PIM-SM has three phases could be made somewhat clearer here.
> Suggestion:
>
> OLD
>     The granularity of mobility-related routing
>     locators required in PIM depends on the complexity (phases) of its
>     deployment.
>
>     The following information is needed for all three phases of PIM as
>     defined in [RFC4601].
> NEW
>     The granularity of mobility-related routing
>     locators required in PIM depends on the complexity (specific phase)
>     of its deployment.
>
>     For all three phases of PIM deployment (see [RFC4601]), the following
>     information is needed.
>

O.K., done

> Also, is "deployment" the right word to describe the phases?  It implies
> that not all of the phases need to be present in an implementation or
> used, even if applicable.
>

You're right. We have reworded

     For all three phases in the operation of PIM (see [RFC4601]), the 
following information is needed.


> -- 4.3.2 - 4.3.4
>
> I would also suggest including the names of the phases from RFC 4601 in
> these section titles, e.g.:
>
> 4.3.2.  Operations of PIM in Phase One (RP Tree)
>

Thanks, done.

> -- idnits
>
> idnits 2.13.01 found an unused reference and a couple of drafts that
> have been updated:
>
>    == Unused Reference: 'RFC2236' is defined on line 1047, but no explicit
>       reference was found in the text
>

Oh, a lapse - RFC2236 is listed mainly for historic/compatibility 
reasons. It is referenced now.

>    == Outdated reference: A later version (-02) exists of
>       draft-ietf-multimob-fmipv6-pfmipv6-multicast-01
>
>    == Outdated reference: A later version (-07) exists of
>       draft-ietf-multimob-handover-optimization-06
>

This is due to an update problem of the online tool (ID database), which 
seems fixed now.

Thanks again!

We will update the document as soon as the submission re-opens.

Best regards,

Thomas
-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °


From nobody Tue Feb 18 12:36: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 9EE961A020D for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 12:36:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.548
X-Spam-Level: 
X-Spam-Status: No, score=-2.548 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.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gbJooBzs5X5x for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 12:36:11 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 101801A0136 for <ietf@ietf.org>; Tue, 18 Feb 2014 12:36:11 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.145.241]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1IKZn5B014432 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Feb 2014 12:36:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392755761; bh=OeSRykyuQRg5tTfN2Z37tw0RFWqn2cpbULyGwSQ0Qv8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KwGfe8KlG+U0zpleUYIFGNrqzXo+cpoKyU2QsZHMbW3DqgiarO935GfcegEoHLgyV mmOj4KgToX9TTiDWj2iBzQ5x6gxyW2NOOXAAhi+Z4YaUqy7lxwwPTGPUHEPc55LyeX PEd9Q/Qo0LWtVz/M+LFP4xSn9l6cMurknUHloVaI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1392755761; i=@elandsys.com; bh=OeSRykyuQRg5tTfN2Z37tw0RFWqn2cpbULyGwSQ0Qv8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Ul4qap/jycSMDKYBArIZMu7TN8vVDO0eKuU6DGsL5CucZ6o+T29D+tVG3B0P7GTJL 2WVtLMvnnwUegSEzKhJCObft8tZXuFEKwUPewuw8Ukqtyc9IRPFAXtKpGWQa3+9vYk uz9vcs9OLbcanimj4Z4K9N8eG9PwEeTRIv3Vge4w=
Message-Id: <6.2.5.6.2.20140218105933.0d42eeb0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 18 Feb 2014 12:29:45 -0800
To: Jorge Amodio <jmamodio@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Internet organisations coordination meeting
In-Reply-To: <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com>
References: <FB3A1F64-78F9-417D-B6BA-0C985337D4B3@ietf.org> <52FFCBEC.3040602@gmail.com> <EA6310C39FFD940FDD0B9D37@JcK-HP8200.jck.com> <CAMm+LwgGVDhYgP5xw5Wgq+3zxSW23CVRri5gyzn5Un5revBNpg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E633471B@EXMB01CMS.surrey.ac.uk> <530086B6.8030408@pi.nu> <6C455759-B2B9-4314-A45B-E575EE0D2006@nominum.com> <CAMzo+1ZiCH1Cy5m0FyXB1A0ox6YQX7Fcar-vpHQM+5c1Y7tCMA@mail.gmail.com> <947B53B0-B4AB-43D2-BDCD-E1E6B3334E51@istaff.org> <7578A603-D089-4AF7-9883-629C7A19965F@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1wLE8JzVMnEV7oOAPE-jNhrlQXE
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, 18 Feb 2014 20:36:12 -0000

Hi Jorge,
At 14:38 16-02-2014, Jorge Amodio wrote:
>The issue is not participation, engagement and cooperation which I 
>consider vital for a healthy and continuously development of the 
>Internet. The issue IMHO is the tag labeling of a group of 
>individuals that perform on an executive role and how the labeling 
>and some statements are perceived and interpreted particularly by 
>mainstream media in a context where Internet Governance (widely 
>misinterpreted by itself ) is on the forefront nowadays.

A lot of things that are said in "Internet Governance" discussions 
are neither entirely true nor are they entirely false.  There is room 
for misinterpretation.  Things did not get better over the years.

>You may not see it because you are in the midst of it. My concern is 
>with the "I* Leaders" label and how and where what you say can be 
>easily taken out context and grossly misinterpreted without 
>exercising some restraint and better choice of words.

http://en.wikipedia.org/wiki/Internet_governance mentions 
"Governors". :-)  It also mentions a statement signed by the heads of 
the Internet Engineering Task Force, the Internet Architecture Board, 
and some other organizations.

In my opinion the problem is that the Internet Engineering Task Force 
is undecided about what it wants to be.  The current state of 
confusion (outside the IETF) encourages people to turn to people with labels.

Regards,
S. Moonesamy 


From nobody Tue Feb 18 13:22:35 2014
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0EBA1A025C for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 13:22:30 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yIJju-VqMhfE for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 13:22:27 -0800 (PST)
Received: from mail-yk0-f169.google.com (mail-yk0-f169.google.com [209.85.160.169]) by ietfa.amsl.com (Postfix) with ESMTP id C2BC91A025A for <ietf@ietf.org>; Tue, 18 Feb 2014 13:22:27 -0800 (PST)
Received: by mail-yk0-f169.google.com with SMTP id 142so34895851ykq.0 for <ietf@ietf.org>; Tue, 18 Feb 2014 13:22:24 -0800 (PST)
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:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=iB+DQsfEP8v47H1Rhwz6B8CfWQ67mscsiNSqqNKSJXI=; b=H5Qs5rLsQgK7t9VBbMbiC986/PCrhJL9Nm5MbgLXkjhl2pj1Yfjw7eFfLX7UXZdsbd xAwxtH1Awk/4VmtNaj2PKuFcbkkU+3tEksaL6el/fEnrI3gXgpEH+Z5XdZHzkfosN6XX 9jjPpxWPHmBXP8JZZ8NHbuEoWFuCbdrAjZysdMxDr2RUPiXLbDiOpExHaftQw8nIqFrb WMDpKivtHukw8d6iuG4P0YmakOwLK8t7nZRkuyoOaKnpd2mZMa30EI/IoNgN0RPCrhoo A51nJQLySfDErqqhjrVWsiVLJTiU5y1b4B0wjGh3IOCqBuWWLRoarmN+ZaS2/1mYMfsu 3+ng==
X-Gm-Message-State: ALoCoQl/HQrH0xn5oh5el01GXrkIktRO2SBumq7zreroWJVNAo5GA4KCIBlrUOzMgIKrx30BQEqJ
X-Received: by 10.236.24.196 with SMTP id x44mr26476983yhx.92.1392758544611; Tue, 18 Feb 2014 13:22:24 -0800 (PST)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id b24sm62657134yhl.25.2014.02.18.13.22.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 13:22:23 -0800 (PST)
Message-ID: <5303CF0C.2040109@braga.eti.br>
Date: Tue, 18 Feb 2014 18:22:20 -0300
From: Juliao Braga <juliao@braga.eti.br>
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@ietf.org>
Subject: IETF-LAC Announce: Workshop Pre-IETF in America Latina
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_njJE6mSngc1DmYp_MtJbScgChY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Feb 2014 21:22:31 -0000

[apologies for cross-postings]

Hi all,

I would like to share the information about an activity for promoting
participation in the IETF from LATAM to be held in one of the most
important technical academic events in Brazil in July 2014.

http://iwpietf.lacnog.org/ (in English, Spanish and Portuguese)

Anyone interested in participating can contact us at ietf-lac@lacnog.org
list or privately. All contact information from committee members
contact are included in the webpage.

Best Regards,

Juliao Braga
Local Chair


From nobody Tue Feb 18 14:49:44 2014
Return-Path: <barryleiba@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 48F2D1A04E5 for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 14:49:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 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, 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 2MFGaRTpalx5 for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 14:49:41 -0800 (PST)
Received: from mail-qa0-x22a.google.com (mail-qa0-x22a.google.com [IPv6:2607:f8b0:400d:c00::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 7435A1A0268 for <ietf@ietf.org>; Tue, 18 Feb 2014 14:49:41 -0800 (PST)
Received: by mail-qa0-f42.google.com with SMTP id k4so24482207qaq.15 for <ietf@ietf.org>; Tue, 18 Feb 2014 14:49:38 -0800 (PST)
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=0+lVsjPrAiPQqyHKdb6GTPuoxGFsOwSlyc78LfAJx1k=; b=DQfciTxkPBaaUU6tZTRnWlCov/ufO66oHtMubhRhMPMNNUcfRZHSzealil1laq33kW V5Q14s405TpYhLj7PxGTubfRylw90IMEncn5lzVeBVxr4K4X+TzrdII+GlSZn4R8ynWK V2D8wRmQENN1oSvls/AH7rwcBUtKV+WwNzH78T+WQpsGcMVr6drDqdccqocgvjsLUf8C /UO9Fk5viUbmxPl6aT8WIzHCFGMC6+TVItw/gWzFhMBWxIFILxI0CiI+SjtPhrz6wYYC lyOxN3ARaKD9cWz3lU72jY8LoqrlJpbbFMwH69Yl7kUWcepdPKhJjbeMdaS10ENcLMJ8 7fqQ==
MIME-Version: 1.0
X-Received: by 10.140.30.230 with SMTP id d93mr44511710qgd.51.1392763777992; Tue, 18 Feb 2014 14:49:37 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.224.26.11 with HTTP; Tue, 18 Feb 2014 14:49:37 -0800 (PST)
Date: Tue, 18 Feb 2014 17:49:37 -0500
X-Google-Sender-Auth: -sedV9ZK50uutWaCLvA9sFnNAig
Message-ID: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com>
Subject: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uv8DNQOeW4_m77MQAnuqbUT9I0g
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Feb 2014 22:49:43 -0000

During the November IETF meeting, I received an appeal from Phillip
Hallam-Baker to the publication of CBOR, RFC 7049, on the Standards
Track.  (Procedural note: The appeal was, at this point, to me as the
responsible AD, and has not gone to the IESG.)  Phill is questioning
the process; specifically, Phill's appeal is as follows:

-------------------------- start --------------------------
My issue here is more than a preference for one encoding over another,
the manner in which CBOR was made a standard has negated the value of
having it being proposed as a standard.

There are already five JSON in binary encodings in widespread use.
CBOR offers no particular advantages over any of the existing schemes
and the authors have never been willing to explain why a different
encoding is desirable.

An IETF standard would have had the advantage of being a single choice
that people could use but only if it was capable of meeting all the
requirements that might be raised and only if it was genuinely
supported by IETF consensus.

Using the individual submission process to shortcut the process
suggests that you don't consider the technical differences between
encodings very important. An encoding is a foundational piece f work
that requires an open process because other people are going to be
building on it.

- CBOR is more complex than JSON and introduces a different data
model. It reintroduces features such as definite/indefinite length
encodings that have already been found to be defective in ASN.1.

- CBOR is an alternative to JSON encoding and not as many people
supported on the APPs list, a simple extension that adds in the
functionality of length delimited strings and binary blobs.

- CBOR does not support compression of tags or strings and there is no
way in which it can be extended to support this capability. It can
however be extended to support new intrinsic types such as a new type
of integer or float. Which is precisely the type of extensibility JSON
rejects.

Had there been an open process, those of us who had requirements and
code that depended on the requirements could have raised them and
there would have been a possibility of a single output from the work.
Instead CBOR does nothing to address the problem of multiple encoding
options and only adds another option on the table.
--------------------------- end ---------------------------

I've taken an unusually long time to resolve this, and for that delay
I apologize and appreciate Phill's patience on -- his appeal did come
in within the two-month appeal window after the approval announcement.

As I evaluated the appeal, I reviewed every message in the discussion
threads.  In the end, my conclusion is that I support the appeal.  I
think that Phill is right that we should have had open discussion of
the design criteria before considering a specific proposal for an
encoding.  The result of not having done that was that we approved an
encoding scheme that meets certain use cases and design goals, without
having first discussed what use cases and design goals the community
might want to have covered.

I think it's important for ADs to consider, when deciding to sponsor
non-working-group documents, whether a broader design discussion is
appropriate.  I believe that I made a mistake in not considering that
for this case.

As to a remedy, I do not see that changing the status of RFC 7049 --
for example, moving it from Standards Track to Experimental -- would
be in the best interest of the IETF at this point.  CBOR had a good
deal of interest when it was proposed, and that interest has continued
and is resulting in implementations (see http://cbor.io/impls.html for
one list of what's going on with respect to CBOR implementations).  A
change to RFC 7049 now would not likely change anything, and would
result in time wasted in moving it back to Standards Track at a
suitable time.

I thank Phill for persisting in pointing out what I missed, and I
intend to consider this more strongly in future decisions about
sponsoring potential standards.

Barry, Applications AD


From nobody Tue Feb 18 16:47: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 C92D31A027C for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 16:47:21 -0800 (PST)
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 8yE4YJnd6D2G for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 16:47:18 -0800 (PST)
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 35A7F1A0013 for <ietf@ietf.org>; Tue, 18 Feb 2014 16:47:18 -0800 (PST)
Received: by mail-lb0-f170.google.com with SMTP id u14so12995154lbd.1 for <ietf@ietf.org>; Tue, 18 Feb 2014 16:47:14 -0800 (PST)
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=v/O2kWmy59YrZoyDNv9n3mOsLdl3O43/APPF61RmMwc=; b=qWnt+VLMxlTk5MIljoVcENYTrjWUaN4RqgUNA4SLeZk2tqJyuLdPhOMJRs/pn+6yos HAVaqo15P5znXKFpRYAFaLs1BqVavP5L9i0octGFO9eLEUVrZngVkoJoP0KWuNz3X68l b3Vqy1M/8YdSTSNNcMXMSk1qBdI/4HYFCL416L06dcLtPOR4UBQVCtqYfGAkNwWyDGws /IISp2UV/RYSYoFHKTAYVqmcP8aoywkrbjm8oht7Bhds1brXBwOE1uvJtG/A67XZwkhX Qzf7Y9bswP/BjB8vwKn44e05bP3fceJmqiCa9f/oePIUMUCEFkEqWLK41ZVsul1Kvw4T +Rpg==
MIME-Version: 1.0
X-Received: by 10.113.5.167 with SMTP id cn7mr22265372lbd.1.1392770834314; Tue, 18 Feb 2014 16:47:14 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Tue, 18 Feb 2014 16:47:14 -0800 (PST)
In-Reply-To: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com>
Date: Tue, 18 Feb 2014 19:47:14 -0500
Message-ID: <CAMm+Lwhq88mbb7jHVpkiVj-9UvmVc9F3A=X16AMZq1pDETzDyg@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=001a11347b7cd53a4904f2b7ba43
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hW0V1qzRpDpBzIKpqXjEhaT4xJc
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, 19 Feb 2014 00:47:22 -0000

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

On Tue, Feb 18, 2014 at 5:49 PM, Barry Leiba <barryleiba@computer.org>wrote:

> During the November IETF meeting, I received an appeal from Phillip
> Hallam-Baker to the publication of CBOR, RFC 7049, on the Standards
> Track.  (Procedural note: The appeal was, at this point, to me as the
> responsible AD, and has not gone to the IESG.)  Phill is questioning
> the process; specifically, Phill's appeal is as follows:
>
> -------------------------- start --------------------------
> My issue here is more than a preference for one encoding over another,
> the manner in which CBOR was made a standard has negated the value of
> having it being proposed as a standard.
>
> There are already five JSON in binary encodings in widespread use.
> CBOR offers no particular advantages over any of the existing schemes
> and the authors have never been willing to explain why a different
> encoding is desirable.
>
> An IETF standard would have had the advantage of being a single choice
> that people could use but only if it was capable of meeting all the
> requirements that might be raised and only if it was genuinely
> supported by IETF consensus.
>
> Using the individual submission process to shortcut the process
> suggests that you don't consider the technical differences between
> encodings very important. An encoding is a foundational piece f work
> that requires an open process because other people are going to be
> building on it.
>
> - CBOR is more complex than JSON and introduces a different data
> model. It reintroduces features such as definite/indefinite length
> encodings that have already been found to be defective in ASN.1.
>
> - CBOR is an alternative to JSON encoding and not as many people
> supported on the APPs list, a simple extension that adds in the
> functionality of length delimited strings and binary blobs.
>
> - CBOR does not support compression of tags or strings and there is no
> way in which it can be extended to support this capability. It can
> however be extended to support new intrinsic types such as a new type
> of integer or float. Which is precisely the type of extensibility JSON
> rejects.
>
> Had there been an open process, those of us who had requirements and
> code that depended on the requirements could have raised them and
> there would have been a possibility of a single output from the work.
> Instead CBOR does nothing to address the problem of multiple encoding
> options and only adds another option on the table.
> --------------------------- end ---------------------------
>
> I've taken an unusually long time to resolve this, and for that delay
> I apologize and appreciate Phill's patience on -- his appeal did come
> in within the two-month appeal window after the approval announcement.
>
> As I evaluated the appeal, I reviewed every message in the discussion
> threads.  In the end, my conclusion is that I support the appeal.  I
> think that Phill is right that we should have had open discussion of
> the design criteria before considering a specific proposal for an
> encoding.  The result of not having done that was that we approved an
> encoding scheme that meets certain use cases and design goals, without
> having first discussed what use cases and design goals the community
> might want to have covered.
>
> I think it's important for ADs to consider, when deciding to sponsor
> non-working-group documents, whether a broader design discussion is
> appropriate.  I believe that I made a mistake in not considering that
> for this case.
>
> As to a remedy, I do not see that changing the status of RFC 7049 --
> for example, moving it from Standards Track to Experimental -- would
> be in the best interest of the IETF at this point.  CBOR had a good
> deal of interest when it was proposed, and that interest has continued
> and is resulting in implementations (see http://cbor.io/impls.html for
> one list of what's going on with respect to CBOR implementations).  A
> change to RFC 7049 now would not likely change anything, and would
> result in time wasted in moving it back to Standards Track at a
> suitable time.
>
> I thank Phill for persisting in pointing out what I missed, and I
> intend to consider this more strongly in future decisions about
> sponsoring potential standards.
>
> Barry, Applications AD
>
>
I will just add that I did not appeal because I have my own proposal. I
wrote the JSON-B proposal because I was being told that CBOR was a private
proposal that did not want input from people with different requirements.

https://tools.ietf.org/html/draft-hallambaker-jsonbcd-01

Choice of encoding format has some very important consequences for
security, particularly when working in non-managed languages like C.


Further the reason that I think a specification should start off as
Experimental in this case is that then the promotion from Experimental to
Proposed has significance and can build momentum.

We already had a half dozen 'JSON in binary proposals' before CBOR. The
design choices in CBOR don't seem to me to be noticeably better than BJSON
and the rest. Adding to the pile of me-too proposals does not help matters.
The only thing that could improve matters is if we reached a consensus on
one choice. And that cannot happen when the authors reject ideas or
requirements that are not their own.

Finally there are people suggesting that CBOR is the IETF version of JSON
in Binary. It isn't and now it never can be. Not least because it does not
follow the JSON data model and thus isn't technically interchangeable. It
is not possible to go back and create consensus after people are told 'this
is our ball, we choose who we are going to play with' as happened in this
case.


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

--001a11347b7cd53a4904f2b7ba43
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, Feb 18, 2014 at 5:49 PM, Barry Leiba <span dir=3D"ltr">&lt;=
<a href=3D"mailto:barryleiba@computer.org" target=3D"_blank">barryleiba@com=
puter.org</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">During the November IETF meeting, I received an appeal fro=
m Phillip<br>

Hallam-Baker to the publication of CBOR, RFC 7049, on the Standards<br>
Track. =A0(Procedural note: The appeal was, at this point, to me as the<br>
responsible AD, and has not gone to the IESG.) =A0Phill is questioning<br>
the process; specifically, Phill&#39;s appeal is as follows:<br>
<br>
-------------------------- start --------------------------<br>
My issue here is more than a preference for one encoding over another,<br>
the manner in which CBOR was made a standard has negated the value of<br>
having it being proposed as a standard.<br>
<br>
There are already five JSON in binary encodings in widespread use.<br>
CBOR offers no particular advantages over any of the existing schemes<br>
and the authors have never been willing to explain why a different<br>
encoding is desirable.<br>
<br>
An IETF standard would have had the advantage of being a single choice<br>
that people could use but only if it was capable of meeting all the<br>
requirements that might be raised and only if it was genuinely<br>
supported by IETF consensus.<br>
<br>
Using the individual submission process to shortcut the process<br>
suggests that you don&#39;t consider the technical differences between<br>
encodings very important. An encoding is a foundational piece f work<br>
that requires an open process because other people are going to be<br>
building on it.<br>
<br>
- CBOR is more complex than JSON and introduces a different data<br>
model. It reintroduces features such as definite/indefinite length<br>
encodings that have already been found to be defective in ASN.1.<br>
<br>
- CBOR is an alternative to JSON encoding and not as many people<br>
supported on the APPs list, a simple extension that adds in the<br>
functionality of length delimited strings and binary blobs.<br>
<br>
- CBOR does not support compression of tags or strings and there is no<br>
way in which it can be extended to support this capability. It can<br>
however be extended to support new intrinsic types such as a new type<br>
of integer or float. Which is precisely the type of extensibility JSON<br>
rejects.<br>
<br>
Had there been an open process, those of us who had requirements and<br>
code that depended on the requirements could have raised them and<br>
there would have been a possibility of a single output from the work.<br>
Instead CBOR does nothing to address the problem of multiple encoding<br>
options and only adds another option on the table.<br>
--------------------------- end ---------------------------<br>
<br>
I&#39;ve taken an unusually long time to resolve this, and for that delay<b=
r>
I apologize and appreciate Phill&#39;s patience on -- his appeal did come<b=
r>
in within the two-month appeal window after the approval announcement.<br>
<br>
As I evaluated the appeal, I reviewed every message in the discussion<br>
threads. =A0In the end, my conclusion is that I support the appeal. =A0I<br=
>
think that Phill is right that we should have had open discussion of<br>
the design criteria before considering a specific proposal for an<br>
encoding. =A0The result of not having done that was that we approved an<br>
encoding scheme that meets certain use cases and design goals, without<br>
having first discussed what use cases and design goals the community<br>
might want to have covered.<br>
<br>
I think it&#39;s important for ADs to consider, when deciding to sponsor<br=
>
non-working-group documents, whether a broader design discussion is<br>
appropriate. =A0I believe that I made a mistake in not considering that<br>
for this case.<br>
<br>
As to a remedy, I do not see that changing the status of RFC 7049 --<br>
for example, moving it from Standards Track to Experimental -- would<br>
be in the best interest of the IETF at this point. =A0CBOR had a good<br>
deal of interest when it was proposed, and that interest has continued<br>
and is resulting in implementations (see <a href=3D"http://cbor.io/impls.ht=
ml" target=3D"_blank">http://cbor.io/impls.html</a> for<br>
one list of what&#39;s going on with respect to CBOR implementations). =A0A=
<br>
change to RFC 7049 now would not likely change anything, and would<br>
result in time wasted in moving it back to Standards Track at a<br>
suitable time.<br>
<br>
I thank Phill for persisting in pointing out what I missed, and I<br>
intend to consider this more strongly in future decisions about<br>
sponsoring potential standards.<br>
<br>
Barry, Applications AD<br>
<br>
</blockquote></div><br>I will just add that I did not appeal because I have=
 my own proposal. I wrote the JSON-B proposal because I was being told that=
 CBOR was a private proposal that did not want input from people with diffe=
rent requirements.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><a href=3D"=
https://tools.ietf.org/html/draft-hallambaker-jsonbcd-01">https://tools.iet=
f.org/html/draft-hallambaker-jsonbcd-01</a><br clear=3D"all"><div><br></div=
><div>
Choice of encoding format has some very important consequences for security=
, particularly when working in non-managed languages like C.=A0<br></div><d=
iv><br></div><div><br></div><div>Further the reason that I think a specific=
ation should start off as Experimental in this case is that then the promot=
ion from Experimental to Proposed has significance and can build momentum.<=
/div>
<div><br></div><div>We already had a half dozen &#39;JSON in binary proposa=
ls&#39; before CBOR. The design choices in CBOR don&#39;t seem to me to be =
noticeably better than BJSON and the rest. Adding to the pile of me-too pro=
posals does not help matters. The only thing that could improve matters is =
if we reached a consensus on one choice. And that cannot happen when the au=
thors reject ideas or requirements that are not their own.</div>
<div><br></div><div>Finally there are people suggesting that CBOR is the IE=
TF version of JSON in Binary. It isn&#39;t and now it never can be. Not lea=
st because it does not follow the JSON data model and thus isn&#39;t techni=
cally interchangeable. It is not possible to go back and create consensus a=
fter people are told &#39;this is our ball, we choose who we are going to p=
lay with&#39; as happened in this case.</div>
<div><br></div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker=
.com/">http://hallambaker.com/</a><br>
</div></div>

--001a11347b7cd53a4904f2b7ba43--


From nobody Tue Feb 18 18:49:32 2014
Return-Path: <cntreras@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 3B3331A0263 for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 18:49:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.699
X-Spam-Level: 
X-Spam-Status: No, score=-3.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_LETTER=-2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.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 Tjy9Fw41ycEB for <ietf@ietfa.amsl.com>; Tue, 18 Feb 2014 18:49:28 -0800 (PST)
Received: from mail-ea0-x22b.google.com (mail-ea0-x22b.google.com [IPv6:2a00:1450:4013:c01::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 917A81A01A0 for <ietf@ietf.org>; Tue, 18 Feb 2014 18:49:28 -0800 (PST)
Received: by mail-ea0-f171.google.com with SMTP id f15so51034eak.2 for <ietf@ietf.org>; Tue, 18 Feb 2014 18:49:25 -0800 (PST)
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=rEBEXHujvVNOWP/JcYsplroo0Pwa4mgO4P9XvLFgbTI=; b=zJpTTEZRMfilaRsYrKPe1TJvKk/LM8+iAXvopG3k+CXHvxh2uQEmg2/jKEkWz2KOE/ t8ewxWXJll7/tmy1j+uhJAjF0FMREFL2z/yXTQ1bNTS11Hlc40KB3aOpmqXvKKjzau03 as0hj8SEnOX7AYy+Ostm2oTFuGpNUofs1KU+l+W1RSXZH9yA4qa+ITHlv/vv05Vnogu2 8jcCqMeIDO6SNmk4QVKn3ZnUuB7JPsxbW6fnO31NQXVgGoddv01qdOsay+9/8Miv2odb m1lRSTflhSx+mDZMZ2EDi3041n5rwT8s3iNNyHtVWMLC9jywOht9W10Ph0UF+kvnLmRp 0ALQ==
MIME-Version: 1.0
X-Received: by 10.14.183.132 with SMTP id q4mr484300eem.91.1392778165115; Tue, 18 Feb 2014 18:49:25 -0800 (PST)
Received: by 10.14.108.72 with HTTP; Tue, 18 Feb 2014 18:49:24 -0800 (PST)
In-Reply-To: <52F323C0.609@frobbit.se>
References: <20140206004730.12491.71674.idtracker@ietfa.amsl.com> <alpine.LRH.2.01.1402051934590.29416@egate.xpasc.com> <m2bnykgb0u.wl%randy@psg.com> <52F30767.1070401@gmail.com> <m28utogah5.wl%randy@psg.com> <52F323C0.609@frobbit.se>
Date: Tue, 18 Feb 2014 20:49:24 -0600
Message-ID: <CAP0PwYZxLqnBig53KmSY=myPf8YW-pcZ2gCK-c46N6Sk9Q7gDQ@mail.gmail.com>
Subject: Re: Proposed Changes to IAOC Communications Plan; Request for Community Input
From: Jorge Contreras <cntreras@gmail.com>
To: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
Content-Type: multipart/alternative; boundary=047d7b343898c8647604f2b96f94
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jBVXyIlEpFvKeD5nCZOxbUnDJ64
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, 19 Feb 2014 02:49:31 -0000

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

All - the IAOC has asked me to respond to this list:

I have taken a look at the proposed Section 5.4.1 and the commentary from
various people:

5.4.1 Subpoenas and Other Legal Requests
   All subpoenas and other legal requests received by the IAOC or the IETF
will be published on the IAOC website together with their responses.

What's important to consider are potential protective orders that may cover
material relating to litigation in which IETF receives a subpoena.  As you
know, and can see from the subpoenas that are already posted on the IETF
web site, some courts (and the ITC) issue protective orders limiting the
use and disclosure of materials produced during discovery.  These orders
typically protect the discloser's confidential information (e.g., if IETF
were asked to disclose confidential information (e.g., salary or credit
card info, or sensitive private communications), it could invoke the terms
of the protective order to ensure that this information would not become
part of the public trial record, and would be seen only by some limited set
of persons (e.g., the judge, legal counsel and perhaps some party
representatives or experts).   To my knowledge, IETF has never been asked
to disclose confidential information, but this could certainly change in
the future.  If that happened, and IETF did disclose this information under
protective order, you would probably not want to disclose it publicly on
the subpoena web page.

The second issue to consider is whether something disclosed TO IETF in the
context of a subpoena or other request may itself by covered by a
protective order.  Again, I'm not aware that this has ever happened, but it
is possible.  For example, if documents were requested from IETF and in
order to understand what was being requested we needed to see some other
(confidential) documents produced during the case, we might receive
material subject to a protective order.  If so, it should clearly not be
posted on the web site.

I think there's a relatively simple fix for these concerns, which is to
tweak Section 5.4.1 by adding the words, ", unless disclosure is prohibited
by law, court order, contract or other legal commitment or would compromise
personal, financial or other sensitive information held by IETF."



On Wed, Feb 5, 2014 at 11:55 PM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrot=
e:

> On 2014-02-06 04:56, Randy Bush wrote:
> >>>>> B.  Proposed Additions to the Plan
> >>>>> >>>>
> >>>>> >>>>      5.4.1 Subpoenas and Other Legal Requests
> >>>>> >>>>
> >>>>> >>>>      All subpoenas and other legal requests received by the IA=
OC
> >>>>> >>>>      or the IETF will be published on the IAOC website togethe=
r
> >>>>> >>>>      with their responses.
> >>>>> >>>>
> >>>>> >>>>      Reason for Change:  Greater transparency.
> >>>> >>> Some such requests may include the requirement that they not be
> >>>> >>> revealed.
> >>> >>
> >>> >> they should be rejected out of hand.  "we can not read your email"
> >> >
> >> > Does that work for National Security Letters too?
> >
> > i was thinking of them specifically.  and yes, i have gone to jail for
> > my political beliefs in the past and would do so again.
>
> A "we have problems here" response for me would trigger a request to
> review under what jurisdiction IETF operate.
>
> We are a standards body that writes documents.
>
> Not an operator or such that deals with operational issues.
>
>    Patrik
>
>
>

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

<div dir=3D"ltr">All - the IAOC has asked me to respond to this list:<div><=
br></div><div><blockquote type=3D"cite" style=3D"color:rgb(0,0,0);font-fami=
ly:Calibri;font-size:medium"><div style=3D"word-wrap:break-word;font-size:1=
4px;font-family:Calibri,sans-serif">
<span id=3D"OLK_SRC_BODY_SECTION"><div style=3D"word-wrap:break-word"><bloc=
kquote type=3D"cite"><div style=3D"font-family:&#39;times new roman&#39;,&#=
39;new york&#39;,times,serif;font-size:12pt">I have taken a look at the pro=
posed Section 5.4.1=A0and the commentary from various people:<br>
<br>5.4.1 Subpoenas and Other Legal Requests<br>=A0=A0 All subpoenas and ot=
her legal requests received by the IAOC=A0or the IETF will be published on =
the IAOC website together=A0with their responses.<br><br><span style=3D"fon=
t-size:12pt;color:rgb(34,34,34)">What&#39;s important to consider are poten=
tial protective orders that may cover material relating to litigation in wh=
ich IETF receives a subpoena.=A0 As you know, and can see from the subpoena=
s that are already posted on the IETF web site, some courts (and the ITC) i=
ssue protective orders limiting the use and disclosure of materials produce=
d during discovery.=A0 These orders typically protect the discloser&#39;s c=
onfidential information (e.g., if IETF were asked to disclose confidential =
information (e.g., salary or credit card info, or sensitive private communi=
cations), it could invoke the terms of the protective order to ensure that =
this information would not become part of the public trial record, and woul=
d be seen only by some limited set of persons (e.g., the judge, legal couns=
el and perhaps some party representatives or experts).=A0=A0 To my knowledg=
e, IETF has never been asked to disclose confidential information, but this=
 could certainly change in the future.=A0 If that happened, and IETF did di=
sclose this information under protective order, you would probably not want=
 to disclose it publicly on the subpoena web page.</span><br>
<br>The second issue to consider is whether something disclosed TO IETF in =
the context of a subpoena or other request may itself by covered by a prote=
ctive order.=A0 Again, I&#39;m not aware that this has ever happened, but i=
t is possible.=A0 For example, if documents were requested from IETF and in=
 order to understand what was being requested we needed to see some other (=
confidential) documents produced during the case, we might receive material=
 subject to a protective order.=A0 If so, it should clearly not be posted o=
n the web site.<br>
<br>I think there&#39;s a relatively simple fix for these concerns, which i=
s to tweak Section 5.4.1 by adding the words, &quot;, unless disclosure is =
prohibited by law, court order, contract or other legal commitment or would=
 compromise personal, financial or other sensitive information held by IETF=
.&quot;<br>
</div></blockquote></div></span></div></blockquote></div></div><div class=
=3D"gmail_extra"><br><br><div class=3D"gmail_quote">On Wed, Feb 5, 2014 at =
11:55 PM, Patrik F=E4ltstr=F6m <span dir=3D"ltr">&lt;<a href=3D"mailto:paf@=
frobbit.se" target=3D"_blank">paf@frobbit.se</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"">On 2014-02-06 04:56, Randy B=
ush wrote:<br>
&gt;&gt;&gt;&gt;&gt; B. =A0Proposed Additions to the Plan<br>
&gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A05.4.1 Subpoenas and Other =
Legal Requests<br>
&gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0All subpoenas and other le=
gal requests received by the IAOC<br>
&gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0or the IETF will be publis=
hed on the IAOC website together<br>
&gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0with their responses.<br>
&gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt;&gt; &gt;&gt;&gt;&gt; =A0 =A0 =A0Reason for Change: =A0Grea=
ter transparency.<br>
&gt;&gt;&gt;&gt; &gt;&gt;&gt; Some such requests may include the requiremen=
t that they not be<br>
&gt;&gt;&gt;&gt; &gt;&gt;&gt; revealed.<br>
&gt;&gt;&gt; &gt;&gt;<br>
&gt;&gt;&gt; &gt;&gt; they should be rejected out of hand. =A0&quot;we can =
not read your email&quot;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Does that work for National Security Letters too?<br>
&gt;<br>
&gt; i was thinking of them specifically. =A0and yes, i have gone to jail f=
or<br>
&gt; my political beliefs in the past and would do so again.<br>
<br>
</div>A &quot;we have problems here&quot; response for me would trigger a r=
equest to<br>
review under what jurisdiction IETF operate.<br>
<br>
We are a standards body that writes documents.<br>
<br>
Not an operator or such that deals with operational issues.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
=A0 =A0Patrik<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--047d7b343898c8647604f2b96f94--


From nobody Wed Feb 19 04:17:58 2014
Return-Path: <henrik@levkowetz.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69CD71A05AE for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 04:17:57 -0800 (PST)
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 CSQBts8V-Npp for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 04:17:54 -0800 (PST)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [77.72.230.30]) by ietfa.amsl.com (Postfix) with ESMTP id BFE421A03D4 for <ietf@ietf.org>; Wed, 19 Feb 2014 04:17:53 -0800 (PST)
Received: from tannat.netnod.se ([77.72.226.96]:50270) by grenache.tools.ietf.org with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <henrik@levkowetz.com>) id 1WG65y-0003k9-8e; Wed, 19 Feb 2014 13:17:47 +0100
Message-ID: <5304A0EA.3040001@levkowetz.com>
Date: Wed, 19 Feb 2014 13:17:46 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Paul Wouters <paul@nohats.ca>, ietf@ietf.org
References: <alpine.LFD.2.10.1402171018340.4876@bofh.nohats.ca>
In-Reply-To: <alpine.LFD.2.10.1402171018340.4876@bofh.nohats.ca>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 77.72.226.96
X-SA-Exim-Rcpt-To: paul@nohats.ca, ietf@ietf.org, gnu@toad.com, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
Subject: Broken email timestamp causes email to be classed as spam (was: Re: broken tools.ietf.org configuration results in 5xx permentant failure?)
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:24:06 +0000)
X-SA-Exim-Scanned: Yes (on grenache.tools.ietf.org)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SC0YnR-pvNI49JOuKLbCjdCmemE
Cc: John Gilmore <gnu@toad.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, 19 Feb 2014 12:17:57 -0000

On 2014-02-17 16:25 Paul Wouters said:
> 
> Looks like someone screwed up the configuration of MX servers of
> tools.ietf.org?
> 
> Please fix,

Looks like someone screwed up the time in their outgoing message, causing
it to be timestamped several hours in the future, and therefore being
treated as spam on receiving MTAs.

Please fix!

(And it would have been better to check and fix this *before* bothering
the ietf list with something which could easily be handled by a query to  
postmaster@tools.ietf.org or to the secretariat.)


--------
Received: from new.toad.com ([209.237.225.253])
        by gamay.tools.ietf.org with esmtps (TLS1.0:DHE_RSA_3DES_EDE_CBC_SHA1:192)
        (Exim 4.80)
        (envelope-from <gnu@toad.com>)
        id 1WFIil-0005gk-2v; Mon, 17 Feb 2014 02:34:31 -0500
Received: from new.toad.com (localhost.localdomain [127.0.0.1])
        by new.toad.com (8.12.9/8.12.9) with ESMTP id s1HFVQGl015808;
        Mon, 17 Feb 2014 07:31:26 -0800
Message-Id: <201402171531.s1HFVQGl015808@new.toad.com>
To: drafts-approval@iana.org
cc: draft-ietf-tls-oob-pubkey@tools.ietf.org, tls-chairs@tools.ietf.org,
   tls-ads@tools.ietf.org
Subject: Re: [IANA #743856] Protocol Action: 'Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)' to Proposed Standard (draft-ietf-tls-oob-pubkey-11.txt) 
In-reply-to: <rt-4.0.8-3698-1392025689-1890.743856-7-0@icann.org> 
References: <RT-Ticket-743856@icann.org> <20140206164140.25549.16661.idtracker@ietfa.amsl.com> <rt-4.0.8-3698-1392025689-1890.743856-7-0@icann.org>
Comments: In-reply-to "Amanda Baber via RT" <drafts-approval@iana.org>
   message dated "Mon, 10 Feb 2014 09:48:09 +0000."
Date: Mon, 17 Feb 2014 07:31:26 -0800
From: John Gilmore <gnu@toad.com>
X-SA-Exim-Connect-IP: 209.237.225.253
X-SA-Exim-Rcpt-To: tls-ads@tools.ietf.org, tls-chairs@tools.ietf.org, draft-ietf-tls-oob-pubkey@tools.ietf.org
X-SA-Exim-Mail-From: gnu@toad.com
Subject: Re: [IANA #743856] Protocol Action: 'Using Raw Public Keys in Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)' to Proposed Standard (draft-ietf-tls-oob-pubkey-11.txt) 
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gamay.tools.ietf.org
X-Spam-Flag: YES
X-Spam-Level: *****
X-Spam-Status: Yes, score=6.0 required=3.0 tests=BAYES_50,DATE_IN_FUTURE_06_12,
      MISSING_SUBJECT,RCVD_IN_BRBL_LASTEXT,T_RP_MATCHES_RCVD autolearn=no
      version=3.3.2
X-SA-Exim-Version: 4.2.1 (built Mon, 26 Dec 2011 16:57:07 +0000)
X-SA-Exim-Scanned: Yes (on gamay.tools.ietf.org)
--------


Henrik


> 
> Paul
> 
> The original message was received at Mon, 17 Feb 2014 07:31:26 -0800
> from localhost.localdomain [127.0.0.1]
> 
>     ----- The following addresses had permanent fatal errors -----
> <draft-ietf-tls-oob-pubkey@tools.ietf.org>
>      (reason: 550 Rejected)
> <tls-chairs@tools.ietf.org>
>      (reason: 550 Rejected)
> <tls-ads@tools.ietf.org>
>      (reason: 550 Rejected)
> 
>     ----- Transcript of session follows -----
> ... while talking to pechora4.icann.org.:
>>>> DATA
> <<< 451 4.7.1 Greylisting in action, please come back later
> <drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
> <<< 503 5.0.0 Need RCPT (recipient)
> ... while talking to pechora3.icann.org.:
>>>> DATA
> <<< 451 4.7.1 Greylisting in action, please come back later
> <drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
> <<< 503 5.0.0 Need RCPT (recipient)
> ... while talking to pechora5.icann.org.:
>>>> DATA
> <<< 451 4.7.1 Greylisting in action, please come back later
> <drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
> <<< 503 5.0.0 Need RCPT (recipient)
> ... while talking to pechora7.icann.org.:
>>>> DATA
> <<< 451 4.7.1 Greylisting in action, please come back later
> <drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
> <<< 503 5.0.0 Need RCPT (recipient)
> ... while talking to pechora1.icann.org.:
>>>> DATA
> <<< 451 4.7.1 Greylisting in action, please come back later
> <drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
> <<< 503 5.0.0 Need RCPT (recipient)
> ... while talking to pechora8.icann.org.:
>>>> DATA
> <<< 451 4.7.1 Greylisting in action, please come back later
> <drafts-approval@iana.org>... Deferred: 451 4.7.1 Greylisting in action, please come back later
> <<< 503 5.0.0 Need RCPT (recipient)
> ... while talking to grenache.tools.ietf.org.:
>>>> DATA
> <<< 451 Please try again later
> ... while talking to gamay.tools.ietf.org.:
>>>> DATA
> <<< 550 Rejected
> 554 5.0.0 Service unavailable
> 
> 


From nobody Wed Feb 19 08:39: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 8A3BE1A0596; Wed, 19 Feb 2014 08:39:43 -0800 (PST)
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 Ts0g5efPeC20; Wed, 19 Feb 2014 08:39:40 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id BCED71A0209; Wed, 19 Feb 2014 08:39:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id AA8B5A01FD; Wed, 19 Feb 2014 08:38:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hXI2SOv2Gwij; Wed, 19 Feb 2014 08:38:51 -0800 (PST)
Received: from [192.168.2.110] (pool-71-178-10-80.washdc.fios.verizon.net [71.178.10.80]) by c9a.amsl.com (Postfix) with ESMTPSA id 18224A01EA; Wed, 19 Feb 2014 08:38:51 -0800 (PST)
Subject: Reminder: Call for nominations: IETF appointment to the ISOC Board of Trustees
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset=us-ascii
From: IAB Chair <iab-chair@iab.org>
In-Reply-To: <2771279D-9BDD-46CE-88F5-0728F1B35CBE@iab.org>
Date: Wed, 19 Feb 2014 11:39:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <4BFB41C0-F18B-44BA-9E8A-D94AA6212088@iab.org>
References: <2771279D-9BDD-46CE-88F5-0728F1B35CBE@iab.org>
To: IETF Announce <ietf-announce@ietf.org>
X-Mailer: Apple Mail (2.1085)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1G74LFtFBvff49n9cPsEpsullG0
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, 19 Feb 2014 16:39:43 -0000

This is a reminder that the IAB is seeking nominations for one seat on =
the ISOC Board of Trustees.  The nominations period is unchanged, and =
nominations close on February 27th.

On behalf of the IAB,
Russ Housley
IAB Chair


On Jan 30, 2014, at 10:13 AM, IAB Chair wrote:

>=20
> The Internet Society (ISOC) provides organizational and financial =
support for the IETF. As part of the arrangements between ISOC and the =
IETF, the IETF is called upon to name 3 Trustees to its Board (BoT), =
with staggered 3 year terms. This requires that the IETF select one =
Trustee each year.=20
>=20
> This year, the IAB will select one person for a term ending in =
mid-2017.=20
>=20
> A description of the IAB's process for selecting the Trustee each year =
can be found in RFC 3677, with this year's timeline as follows:=20
>=20
> * January 30, 2014 : Open nomination period
>=20
> * February 27, 2014 : Close of the nomination period=20
>=20
> * No later than April 10, 2014 : IAB selection delivered to IESG for =
confirmation
>=20
> * No later than May 23, 2014 : Delivery of final confirmed selection =
to the ISOC Elections Committee for announcement with the rest of the =
new ISOC BoT slate.=20
>=20
>=20
> Nominations=20
> -----------=20
>=20
> Nominations (including self-nominations) should be sent to the IAB -- =
iab@iab.org.  Please include e-mail contact details with the nomination.=20=

>=20
> Nomination Details=20
> -----------------=20
>=20
> Nominees should be aware that ISOC Trustees are elected to three year =
terms with approximately one third of the Board of Trustees elected each =
year. The responsibilities of a Trustee include fiscal management of the =
Internet Society, fundraising, and participation in Board meetings plus =
conference-call meetings, as detailed by the ISOC Bylaws:
> =
http://www.internetsociety.org/who-we-are/governance-and-policies/amended-=
and-restated-laws-internet-society
>=20
> The desirable characteristics of a candidate that are specific to the =
IETF-selected ISOC BoT member are outlined in section 2 of RFC 3677.=20
>=20
> Nominees are asked to provide to the IAB:=20
>=20
> 1. Confirmation of their willingness to be considered within this =
process.=20
>=20
> 2. Full name and contact information.=20
>=20
> 3. A statement confirming willingness and ability to devote an =
appropriate level of time to activities associated with the position of =
Trustee.=20
>=20
> 4. A brief biography outlining experience and background.=20
>=20
> 5. A statement of interests, concerns about the Internet Society, =
goals as a Trustee, and motivation to serve as a Trustee.=20
>=20
> 6. Any further information that is relevant to the work of the IAB in =
considering your nomination.=20
>=20
> Time Commitment=20
> ---------------=20
>=20
> Trustees are expected to commit the time necessary to perform regular =
board and committee business. Trustees are also expected to allocate =
some time to attend and prepare for meetings.=20
>=20
>=20
> Care of Personal Information=20
> ----------------------------=20
>=20
> The following procedures will be used by the IAB in managing this =
process:=20
>=20
> - The candidate's name will be published, with all other candidate =
names, at the close of the nominations period.
>=20
> - Excerpts of the information provided to the IAB by the nominated =
candidate will be passed to the IESG as part of the confirmation =
process. The IESG will be requested to maintain confidentiality of the =
candidate's information.
>=20
> - Except as noted above, all information provided to the IAB during =
this process will be kept confidential to the IAB.=20
>=20
>=20
> Current IETF-Selected Trustees=20
> ------------------------------
>=20
> The current IETF-Selected ISOC Trustees and their term of appointment =
are:=20
>=20
> - Bert Wijnen 2011 - 2014
> - Eric Burger 2012 - 2015
> - Bob Hinden 2013 - 2016=20
>=20
>=20
> On behalf of the IAB,
> Russ Housley
> IAB Chair


From nobody Wed Feb 19 10:17:18 2014
Return-Path: <hildjj@cursive.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 918DC1A01F0 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 10:17:16 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ISx7hJ84pfSM for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 10:17:15 -0800 (PST)
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 233971A00B8 for <ietf@ietf.org>; Wed, 19 Feb 2014 10:17:15 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id rp16so731534pbb.34 for <ietf@ietf.org>; Wed, 19 Feb 2014 10:17:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cursive.net; s=google;  h=user-agent:date:subject:from:to:cc:message-id:thread-topic :references:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=XaueaTLVAX2uTHZ1adfzt6i7iZkDUk3LKfwQ+AbKOaM=; b=bJ0L5aDzgT4tMRaJQj9TkOIallZ2NwQwp0pYDhfoR8VGO94gKVb7BBoIvxBljJ0fvU 7X/S/OO+w1DEu+9DMdoCicNuR+XhtDp7pd9N39BklU/58CwF6pJuOOyyS7CPxn+mSDhW k+/XAoQ8MwiHYEySle1717TQTMYDC+69zwd9I=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:user-agent:date:subject:from:to:cc:message-id :thread-topic:references:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=XaueaTLVAX2uTHZ1adfzt6i7iZkDUk3LKfwQ+AbKOaM=; b=HK+MSgby6mrIcRiQREjJs2UYgB5w4vJ4vfenBt3kR7Gnx+9m8r67XE0HP2l5EVS4sY mg0umJjFxQ/cBBjSqHBxKK6UE4EMYspUiH7XV89GBXwNHhjbdV4adc81K2xF7M7hF2/c fsbd9DoIrocKWReVTXmdu6mauFpiHtxajQdQzL+UGqiat61Iy4ANGEgymqq6FtwuXtur ML04LoM2havQ+MRc3RX+Jm1TMPGUtRE0GsiMYmzN2xtP3cNWT+FJhDsYNkUjLpFJigmQ BzWjm+5ADMeQLB9x8beCDMhLBYBR+OLkphoOPs+YgddogFcB5xZIwhxwmOcYMnCb36og Lasg==
X-Gm-Message-State: ALoCoQnAfxpcZYHV+mlXwYEGw92TlrqREQ+0lF3lbdxc4zva6eSAtEZ63hyRYqIq/8MX1YmtmzTP
X-Received: by 10.69.31.65 with SMTP id kk1mr41983635pbd.47.1392833831937; Wed, 19 Feb 2014 10:17:11 -0800 (PST)
Received: from [10.129.24.156] (128-107-239-236.cisco.com. [128.107.239.236]) by mx.google.com with ESMTPSA id hb10sm2857167pbd.1.2014.02.19.10.17.04 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 19 Feb 2014 10:17:10 -0800 (PST)
User-Agent: Microsoft-MacOutlook/14.3.9.131030
Date: Wed, 19 Feb 2014 11:16:55 -0700
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Joe Hildebrand <hildjj@cursive.net>
To: Phillip Hallam-Baker <hallam@gmail.com>, Barry Leiba <barryleiba@computer.org>
Message-ID: <CF2A42A5.3A4D1%joe@cursive.net>
Thread-Topic: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <CAMm+Lwhq88mbb7jHVpkiVj-9UvmVc9F3A=X16AMZq1pDETzDyg@mail.gmail.com>
In-Reply-To: <CAMm+Lwhq88mbb7jHVpkiVj-9UvmVc9F3A=X16AMZq1pDETzDyg@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uo18iewZTQbEYnh_LdLjF1o4ZPo
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, 19 Feb 2014 18:17:16 -0000

On 2/18/14 5:47 PM, "Phillip Hallam-Baker" <hallam@gmail.com> wrote:

>Finally there are people suggesting that CBOR is the IETF version of JSON
>in Binary. It isn't and now it never can be. Not least because it does
>not follow the JSON data model and thus isn't technically
>interchangeable. It is not possible to go back and create consensus after
>people are told 'this is our ball, we choose who we are going to play
>with' as happened in this case.

Barry, can you add a little more clarity on this point, please?  Does your
decision mean that we shall not ever normatively reference CBOR in future
protocols?

-- 
Joe Hildebrand





From nobody Wed Feb 19 10:56:12 2014
Return-Path: <barryleiba@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 10A5E1A0504 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 10:56:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 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, 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 nWKe0pt2iVpq for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 10:56:08 -0800 (PST)
Received: from mail-qa0-x233.google.com (mail-qa0-x233.google.com [IPv6:2607:f8b0:400d:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC0C1A04E7 for <ietf@ietf.org>; Wed, 19 Feb 2014 10:56:07 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id f11so1197946qae.10 for <ietf@ietf.org>; Wed, 19 Feb 2014 10:56:04 -0800 (PST)
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=oszSvPDNf/iQo4oUTpu2lBF7Zzb8gsSNH+mEy0wHZZE=; b=PoYSj5lL0Nwn1vWvjmnPueCQXV1sGW0uP6Tu+DW3rH3xhwfcqvYv4/ZWFNpQtZyZ4t gvUdTpfKsseS0RTK38TQVGq4COU2qoUFfs39aonYyi2mPSw9FItZ6+5yIm5VG3q/KZKO dRGA6ycvu7TICnDyax764XluuCvfkCEMuJpwQ2dGHILHXenzziIQXJxCdVqVOvZfyzge mLawcmnjSQwk7qYNnWxz1PlkDLUVA2Cupq83gS1O9/XbLiFM+/nbK7Ajofh4nkiAQxnK 6i8gc7SkTKnME4mrIIf08OB1cXtpIzxi+hqt+ZfHlxyrgZFyicpS/vbmBKOv79oGyI9h jM8g==
MIME-Version: 1.0
X-Received: by 10.229.89.5 with SMTP id c5mr4265165qcm.14.1392836164641; Wed, 19 Feb 2014 10:56:04 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.224.26.11 with HTTP; Wed, 19 Feb 2014 10:56:04 -0800 (PST)
In-Reply-To: <CF2A42A5.3A4D1%joe@cursive.net>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <CAMm+Lwhq88mbb7jHVpkiVj-9UvmVc9F3A=X16AMZq1pDETzDyg@mail.gmail.com> <CF2A42A5.3A4D1%joe@cursive.net>
Date: Wed, 19 Feb 2014 13:56:04 -0500
X-Google-Sender-Auth: EKliqg1JSASNUZzI3VZxEIboszE
Message-ID: <CALaySJ+sWTiGb+PPcmBfUDgWMu1V5o_VvJgV-Bi-b_VBWSpTvw@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Barry Leiba <barryleiba@computer.org>
To: Joe Hildebrand <hildjj@cursive.net>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OFBJIJq4pguEEyur0fq5XALZLHE
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, 19 Feb 2014 18:56:10 -0000

>>Finally there are people suggesting that CBOR is the IETF version of JSON
>>in Binary. It isn't and now it never can be. Not least because it does
>>not follow the JSON data model and thus isn't technically
>>interchangeable. It is not possible to go back and create consensus after
>>people are told 'this is our ball, we choose who we are going to play
>>with' as happened in this case.
>
> Barry, can you add a little more clarity on this point, please?  Does your
> decision mean that we shall not ever normatively reference CBOR in future
> protocols?

It does not mean that.  CBOR does remain as a Proposed Standard.  This
is about process, and the key point is here:

> we should have had open discussion of
> the design criteria before considering a specific proposal for an
> encoding.
...
> I think it's important for ADs to consider, when deciding to sponsor
> non-working-group documents, whether a broader design discussion is
> appropriate.  I believe that I made a mistake in not considering that
> for this case.

Barry


From nobody Wed Feb 19 11:52:21 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 5C8D61A0167 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 11:52:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WVIE57yAM8gr for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 11:52:16 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id EB0ED1A05ED for <ietf@ietf.org>; Wed, 19 Feb 2014 11:52:12 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WGDAO-000G01-Dh; Wed, 19 Feb 2014 14:50:48 -0500
Date: Wed, 19 Feb 2014 14:50:38 -0500
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, Joe Hildebrand <hildjj@cursive.net>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
Message-ID: <24E6ED8EDF7BECFC9B0B5E78@JcK-HP8200.jck.com>
In-Reply-To: <CALaySJ+sWTiGb+PPcmBfUDgWMu1V5o_VvJgV-Bi-b_VBWSpTvw@mail.gmail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <CAMm+Lwhq88mbb7jHVpkiVj-9UvmVc9F3A=X16AMZq1pDETzDyg@mail.gmail.c om> <CF2A42A5.3A4D1%joe@cursive.net> <CALaySJ+sWTiGb+PPcmBfUDgWMu1V5o_VvJgV-Bi-b_VBWSpTvw@mail.gmail.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7TzwtyNMi7SSAdNw_jeP_NyMzQQ
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, 19 Feb 2014 19:52:19 -0000

--On Wednesday, February 19, 2014 13:56 -0500 Barry Leiba
<barryleiba@computer.org> wrote:

>> Barry, can you add a little more clarity on this point,
>> please?  Does your decision mean that we shall not ever
>> normatively reference CBOR in future protocols?
> 
> It does not mean that.  CBOR does remain as a Proposed
> Standard.  This is about process, and the key point is here:

Barry,

Purely as a process clarification (I don't care enough one way
or the other, but I haven't been involved in JSON work), is it
correct that, if someone wanted the state that Joe asked about
(i.e., no normative references to CBOR), they would need to take
one of the following three steps:

(1) Appeal your just-announced decision, asking that the
document be reclassified to Experimental, Informational, or, I
suppose, Historic?

(2) Generate an I-D specifying one of the above four results and
the reasons for it and try to get that I-D approved.

(3) Generate an I-D for an Applicability Statement that would
identify CBOR as "not recommended" and try to get it approved.
While that would not prevent a normative reference requiring
CBOR use, it would certainly touch off an interesting discussion
should anyone try to do it.

In either the second or third cases, the parties involved could
either try to get the I-D through the process as an individual
submission or could try to get some relevant WG, presumably (but
not required to be) JSON, to take it into their work program[me].

Does that correctly summarize the process alternatives?

    john




From nobody Wed Feb 19 12:10:33 2014
Return-Path: <barryleiba@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 3D2D61A04EA for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 12:10:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 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, 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 h5QctLg5oWFa for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 12:10:30 -0800 (PST)
Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id AC1001A0167 for <ietf@ietf.org>; Wed, 19 Feb 2014 12:10:30 -0800 (PST)
Received: by mail-qc0-f169.google.com with SMTP id w7so1507455qcr.14 for <ietf@ietf.org>; Wed, 19 Feb 2014 12:10:27 -0800 (PST)
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=kA7eL+igng0JktTVczUgr73jtTHK+YEHcpulCosbh64=; b=UwXxqNb0QvLa+T2cfMEJaKjYxUpvbbyBMnVjJGeaSNNe/AIHohYAdV82OdBYiRquW0 Y/PSwScLHGmZuCZvHgq1yMAXAnpogzz4QsNSfv7qJ6SXs+C1DGcMuFxWwLZdqSa8kRAt 5sJsfnEWVbDAZeUfV6+1j+dTtdbKoqhfwlWRjwb8HbM4q/ZLe2lf1ibh4ez3ZEmSoszM 1N1594uiA0omUYbc4lG4jPdbE3tlmQ2i//s1e5SUdbAWAXWlI2MMc4nlgesbeOb4pYdi /7CM7qRefVN52tcVTxcUR4bPto/FLhhiK7Hpm+yuoHH8yh6xZ2DcCdD6U9JDV8GWgM1S DKnA==
MIME-Version: 1.0
X-Received: by 10.224.172.133 with SMTP id l5mr53745919qaz.25.1392840627293; Wed, 19 Feb 2014 12:10:27 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.224.26.11 with HTTP; Wed, 19 Feb 2014 12:10:27 -0800 (PST)
In-Reply-To: <24E6ED8EDF7BECFC9B0B5E78@JcK-HP8200.jck.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <CF2A42A5.3A4D1%joe@cursive.net> <CALaySJ+sWTiGb+PPcmBfUDgWMu1V5o_VvJgV-Bi-b_VBWSpTvw@mail.gmail.com> <24E6ED8EDF7BECFC9B0B5E78@JcK-HP8200.jck.com>
Date: Wed, 19 Feb 2014 15:10:27 -0500
X-Google-Sender-Auth: SwuM2EwT47KtugdPGpzHgIQNeFg
Message-ID: <CALaySJL2heLvB0CwE-awmDOpn8WMLmnJN=ZiUYB4pwW+NSh6hA@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/KnJJAOPhG3XjN8Q2LzCTTNJ82CU
Cc: Joe Hildebrand <hildjj@cursive.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, 19 Feb 2014 20:10:32 -0000

> Purely as a process clarification (I don't care enough one way
> or the other, but I haven't been involved in JSON work), is it
> correct that, if someone wanted the state that Joe asked about
> (i.e., no normative references to CBOR), they would need to take
> one of the following three steps:
>
> (1) Appeal your just-announced decision, asking that the
> document be reclassified to Experimental, Informational, or, I
> suppose, Historic?

If someone really thought it was in the best interest of the IETF to
reclassify the document, yes, they could appeal my decision; talking
to the IETF Chair would be the proper path.

> (2) Generate an I-D specifying one of the above four results and
> the reasons for it and try to get that I-D approved.

That would be an alternative path to getting the document reclassified.

Reclassifying the document would not stop anyone from using it as a
normative reference, now that we permit downrefs.

> (3) Generate an I-D for an Applicability Statement that would
> identify CBOR as "not recommended" and try to get it approved.
> While that would not prevent a normative reference requiring
> CBOR use, it would certainly touch off an interesting discussion
> should anyone try to do it.

A "CBOR Considered Harmful" document would be a more extreme case of (2), yes.

> Does that correctly summarize the process alternatives?

It seems like it.  I imagine that, creative sorts that we are, we
could manage to come up with other wrinkles.  As I've said, I think
none of them are in our best interest at this point.

Barry


From nobody Wed Feb 19 13:11:03 2014
Return-Path: <barryleiba@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 B51811A0250 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 13:11:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 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, 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 4HHpIMhhimfo for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 13:11:00 -0800 (PST)
Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 11F251A0226 for <ietf@ietf.org>; Wed, 19 Feb 2014 13:10:59 -0800 (PST)
Received: by mail-qc0-f181.google.com with SMTP id c9so1361991qcz.12 for <ietf@ietf.org>; Wed, 19 Feb 2014 13:10:56 -0800 (PST)
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=UDUt26a2e+HJz6Q2sQ018tvgBW/0pU+vim2f+Zp4kyQ=; b=rWKAmZeBCIu6hoE7PI6gjK/OfTHcJS7I/7nlXA/5eaZRyWXIqL5CqtgUUmqU8E8eDH 7JiBreF8md2yctAVAp6SihKQG927jo1xS760qUSSOXnBaB4WeaEENtPzk7BDiJaHTgqV Qjyet0fjDz2aITfGsJwQoiK5IcO8AUZSNaL23xBdzn3gW1FJnbt0F+v6Txl8dYRH9wwO 15Qa+MsCdiou+TW30dGgkuP71ROXHLBxY3KFUWD3DVdpBio2XqjXfUB0LG1EEzYKYh1N 9tAl8H+bLLLn6EGVlPyNl9zby4abQKnLYtnPR/E9eoBgwL3Xjzu3mj7CAw7ebpibVs6t qQfg==
MIME-Version: 1.0
X-Received: by 10.140.93.111 with SMTP id c102mr50255403qge.53.1392844256466;  Wed, 19 Feb 2014 13:10:56 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.224.26.11 with HTTP; Wed, 19 Feb 2014 13:10:55 -0800 (PST)
In-Reply-To: <tsld2ii3kme.fsf@mit.edu>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu>
Date: Wed, 19 Feb 2014 16:10:55 -0500
X-Google-Sender-Auth: Pi0mbXBjo0asy8iqp0WqlAZMM70
Message-ID: <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Barry Leiba <barryleiba@computer.org>
To: Sam Hartman <hartmans-ietf@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Wx0Nor7zAtIhxjEH9H3_3szloh8
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, 19 Feb 2014 21:11:01 -0000

> As a matter of process, I'm confused about the handling of this appeal.
> It sounds like Phil appealed the approval of RFC 7049.
>
> That, I hope, was a decision made by the IESG, not a decision made by
> one AD.
> So, I'm failing to understand how it makes sense for you to respond to
> this appeal as an AD.

Phill took the first step of addressing his complaint to the
responsible AD (me).  This is my response.  If he or someone else
should choose to pursue a further appeal, the next step would be to
take it to the IESG by way of the Chair.

Barry


From nobody Wed Feb 19 13:57: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 EB7491A0244 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 13:57:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, 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 gq0_I3elQ1Ni for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 13:57:12 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 546FE1A0226 for <ietf@ietf.org>; Wed, 19 Feb 2014 13:57:12 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.132.170]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1JLul4j008455 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Feb 2014 13:56:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392847019; bh=aftn9/j6spGjMUxqUGcXSnO18mQ2DVifoauGs/UOidY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=hFrjD+3HEDl7s4pI/l1v4e75McAiVLTDI2XwrkrCIT/vti0rqcDwrNHw9RedaSvcQ MV9mbEq1GJKjEntEW2XrZU5S3GBQEvReqpWRj/POS+jEOa0YA7DVt2BK/i5xBV/l76 ztWGD2toR4sDudpELBQYBlWIYiPQKMjuVuPGUmlE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1392847019; i=@elandsys.com; bh=aftn9/j6spGjMUxqUGcXSnO18mQ2DVifoauGs/UOidY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=2ANvcx5vAz2ThYVlJCT+sHUqstq1Yfd0jKVSB8fTRsrF/BVfv+R9FdzIzlj1u/n7R /vzyKw3+9NzL0ieBGLssLeOofK/8MU0VD/gFOvj7wvGhTE5l7W+wBs0ooVLgxG8mKp mmd/jRA1Ua+xolH3iD+hJ0VxbzbXTEPusdbe6hIA=
Message-Id: <6.2.5.6.2.20140219132307.0d0155b0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 19 Feb 2014 13:48:52 -0800
To: Barry Leiba <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@mit.edu>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
In-Reply-To: <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.g mail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@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/vsdOGIBVQFHZvYad053K3NYTZ1w
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, 19 Feb 2014 21:57:14 -0000

Hi Barry,
At 13:10 19-02-2014, Barry Leiba wrote:
>Phill took the first step of addressing his complaint to the
>responsible AD (me).  This is my response.  If he or someone else
>should choose to pursue a further appeal, the next step would be to
>take it to the IESG by way of the Chair.

Selective quoting:

   "During the November IETF meeting, I received an appeal from Phillip
    Hallam-Baker to the publication of CBOR, RFC 7049, on the Standards
    Track."

RFC 7049 was published in October 2013.  As Sam Hartman mentioned it 
was a decision of the IESG.

   "Phill is questioning the process;"

That falls under the IESG.

The handling of the appeal is odd.

Regards,
S. Moonesamy 


From nobody Wed Feb 19 14:09:53 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 B168B1A0276; Wed, 19 Feb 2014 14:09:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pUi57moZDwEk; Wed, 19 Feb 2014 14:09:48 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4251A0226; Wed, 19 Feb 2014 14:09:48 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7F2362CEAE; Thu, 20 Feb 2014 00:09:44 +0200 (EET)
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 k7-3FIEw0GgI; Thu, 20 Feb 2014 00:09:44 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 0E0962CC5D; Thu, 20 Feb 2014 00:09:44 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: [Gen-art] Gen-ART LC review of draft-ietf-pcp-description-option-03
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <036401cf1b53$2ec6cdd0$8c546970$@gmail.com>
Date: Wed, 19 Feb 2014 23:09:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <04EE3A4E-6895-43B3-93E6-DA9F155F579C@piuha.net>
References: <02db01cf1a6e$62eb8280$28c28780$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F4736082C@PUEXCB1B.nanterre.francetelecom.fr> <033d01cf1b42$854c10e0$8fe432a0$@gmail.com> <94C682931C08B048B7A8645303FDC9F36F473608DF@PUEXCB1B.nanterre.francetelecom.fr> <036401cf1b53$2ec6cdd0$8c546970$@gmail.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lDUO-8kfFjr3cBNhcdhfeYYZpE8
Cc: gen-art@ietf.org, mohamed.boucadair@orange.com, ietf@ietf.org, draft-ietf-pcp-description-option.all@tools.ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Feb 2014 22:09:49 -0000

I am going through the documents for the upcoming IESG telechat. Roni - =
thank you very much for the review. Mohamed & others - I see that you =
have addressed the comments in -04, thank you for that!

Jari


From nobody Wed Feb 19 16:37:45 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 2A3FF1A0467 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 16:37:30 -0800 (PST)
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 8BcOkDrJhOQt for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 16:37:23 -0800 (PST)
Received: from mail-la0-x230.google.com (mail-la0-x230.google.com [IPv6:2a00:1450:4010:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id 281621A05EB for <ietf@ietf.org>; Wed, 19 Feb 2014 16:37:22 -0800 (PST)
Received: by mail-la0-f48.google.com with SMTP id mc6so833803lab.7 for <ietf@ietf.org>; Wed, 19 Feb 2014 16:37:19 -0800 (PST)
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=9oMB97aHd0dMhPxTTlWQPhBPk285T6gM7XPTktrlgSg=; b=u8U4JfQb6w924MI0e2DiqIG3cNNkWCwGOzOpnrAhIbwRWZAHQNv5VyUoRAv6jRbcEa b7hEaO3l9Fpr4XCr6qooRF+wp/S1S/3Dyy8zWu/sRfqzJXmkuC084v04gaHJeimsTLhX ms8phPmwjajTbZPpR8cMSsJSEiIJTi3qLcXlQHQEePKJbmFjJZWjQ9rQNZ6t/HWrgJFW 2hHnf21ER8HjsBRQklL+jhXFlzu6KX3/1Z/3vQ7WnVV0Kl3H0H/gIGm4AJTD5QvFtet5 arhGVq7IR7kbgJpf10AqxZYmHnExZX5H5ZcGqeaQ1rfFNt5ygkbPXgFiV2fkH1ISFac4 F8hw==
MIME-Version: 1.0
X-Received: by 10.112.74.39 with SMTP id q7mr2737661lbv.64.1392856639053; Wed, 19 Feb 2014 16:37:19 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Wed, 19 Feb 2014 16:37:18 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140219132307.0d0155b0@resistor.net>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <6.2.5.6.2.20140219132307.0d0155b0@resistor.net>
Date: Wed, 19 Feb 2014 19:37:18 -0500
Message-ID: <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Phillip Hallam-Baker <hallam@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=14dae94736b531a3e304f2cbb59f
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/h1hLJgUnhp2n4nBB5uyCYI0NqB4
Cc: Barry Leiba <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@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, 20 Feb 2014 00:37:30 -0000

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

On Wed, Feb 19, 2014 at 4:48 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Barry,
>
> At 13:10 19-02-2014, Barry Leiba wrote:
>
>> Phill took the first step of addressing his complaint to the
>> responsible AD (me).  This is my response.  If he or someone else
>> should choose to pursue a further appeal, the next step would be to
>> take it to the IESG by way of the Chair.
>>
>
> Selective quoting:
>
>
>   "During the November IETF meeting, I received an appeal from Phillip
>    Hallam-Baker to the publication of CBOR, RFC 7049, on the Standards
>    Track."
>
> RFC 7049 was published in October 2013.  As Sam Hartman mentioned it was a
> decision of the IESG.
>
>   "Phill is questioning the process;"
>
> That falls under the IESG.
>
> The handling of the appeal is odd.
>

The whole process has been odd.

I told Jari and Barry that I was appealing the decision in Vancouver. I was
told to raise it with the relevant AD first. By the time he had come to a
decision it was that too much effort had gone into building things on top
of CBOR since to undo the original decision.

I now realize that what I should have done was to simply send the original
appeal to the IETF list and not gone through channels as requested.


The fundamental problem here is that as I see it the protocol world is
rapidly converging on JSON as the encoding of choice and there are many
good reasons why it is a better encoding than any of the text based
alternatives on offer (RFC822, XML). It is thus inevitable that people will
ask if a binary encoding of JSON would be better than ASN.1. Which of
course is true and not just because hitting yourself on the foot repeatedly
with a hammer is better than ASN.1.

JSON is good for a lot of things, but not for passing encrypted objects
around unless they are really small. So JOSE is interesting but only in a
very limited field. If we can encode binary data in JSON without a 33%
inflation in size, JOSE suddenly becomes very interesting indeed.

If JOSE didn't inflate the size of a data object, we could use it for data
level encryption. Drop a content type tag and some other metadata on the
wrapper, encrypt the contents and we can have a CMS like blob that fits the
Internet idiom much better (and there is some soon to expire IP that would
make animating that proposal very interesting).


But now we have a binary encoding published on IETF standards track that is
not a binary encoding of JSON but has a subset that could be used to encode
JSON sitting in that spot. It isn't a consensus document, isn't a product
of open process, it is however on IETF standards track. So the job for
anyone doing the job properly has become harder.

So it is kind of like the Sochi which will always be the OoOo* Olympics.

The only thing that makes an encoding interesting is that a constituency of
users agree to all make use of it. JSON has emerged from a field of
thousands of text encodings because it is the best compromise between
simplicity and functionality that has such a wide user base. So having
random specs given standards status when the designers only attempted to
solve the problems they cared about does not help matters.


My main concern is the process question. I really don't care whether CBOR
is a PROPOSED STANDARD or whatever. What I do care about is if I am told
that I have to use it because that is the IETF standard for binary
encoding. And what I care most about is the risk that this approach of 'its
our ball and only we will decide who gets to play' is going to be repeated.

There are cases where it makes perfect sense for a draft to go straight
onto the standards track. There are plenty of extensions to PKIX that are
important enough to write down but not so important that it is worth
running up a whole working group just to decide them.


But a spec whose only purpose is to provide a platform for other specs
really needs to clear a higher bar than not being idiotic and having some
people willing to implement. There have to be people who want to choose to
build on it.


The way I think the process should work is:

1) The IAB identifies the need for a consensus binary encoding for JSON as
a platform the IETF community can build on (or why call it an architecture
board).

2) People write drafts that elaborate on the requirements and/or propose
schemes that meet them, these are published as either EXPERIMENTAL or
INFORMATIONAL.

3) People who are building applications that build on the platform kick the
tires and decide which ones they like / hate etc. Either a consensus
emerges that one encoding is best in which case we can go to step 4,
otherwise we go back to step 2.

4) PROPOSED STANDARD status is awarded in recognition of the fact that
there is a defacto standard that application protocol designers have
converged on. This may involve spinning up a working group to clean up the
documents or not depending on their quality.


I have seen the shotgun standards approach in the past. BEEP tried that
route, it was a complete failure as a result because it moved through the
standards process so fast it never gained any buy in outside the original
design team. So even though it has features that are very sound and the
HTTP/2.0 WG might well end up re-inventing it was still born because the
proposers thought that standards track was the route to driving adoption
rather than recognition of adoption.

Standards is the process of making decisions that don't matter. It does not
really matter what the HTTP protocol syntax is provided that a decision has
been made to choose one syntax for that task instead of five.

So I would like to see the IAB actually doing the job of an architecture
board and identifying gaps in the IETF stack where convergence on one
particular way of solving a problem would be beneficial. That is not saying
that they should be the people providing the solution.

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

--14dae94736b531a3e304f2cbb59f
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 Wed, Feb 19, 2014 at 4:48 PM, 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> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Hi Barry,<div class=3D""><br>
At 13:10 19-02-2014, Barry Leiba wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Phill took the first step of addressing his complaint to the<br>
responsible AD (me). =A0This is my response. =A0If he or someone else<br>
should choose to pursue a further appeal, the next step would be to<br>
take it to the IESG by way of the Chair.<br>
</blockquote>
<br></div>
Selective quoting:<div class=3D""><br>
<br>
=A0 &quot;During the November IETF meeting, I received an appeal from Phill=
ip<br>
=A0 =A0Hallam-Baker to the publication of CBOR, RFC 7049, on the Standards<=
br>
=A0 =A0Track.&quot;<br>
<br></div>
RFC 7049 was published in October 2013. =A0As Sam Hartman mentioned it was =
a decision of the IESG.<div class=3D""><br>
=A0 &quot;Phill is questioning the process;&quot;<br>
<br></div>
That falls under the IESG.<br>
<br>
The handling of the appeal is odd.<br></blockquote><div><br></div><div>The =
whole process has been odd.=A0</div><div><br></div><div>I told Jari and Bar=
ry that I was appealing the decision in Vancouver. I was told to raise it w=
ith the relevant AD first. By the time he had come to a decision it was tha=
t too much effort had gone into building things on top of CBOR since to und=
o the original decision.</div>
<div><br></div><div>I now realize that what I should have done was to simpl=
y send the original appeal to the IETF list and not gone through channels a=
s requested.</div><div>=A0</div></div><div><br></div><div>The fundamental p=
roblem here is that as I see it the protocol world is rapidly converging on=
 JSON as the encoding of choice and there are many good reasons why it is a=
 better encoding than any of the text based alternatives on offer (RFC822, =
XML). It is thus inevitable that people will ask if a binary encoding of JS=
ON would be better than ASN.1. Which of course is true and not just because=
 hitting yourself on the foot repeatedly with a hammer is better than ASN.1=
.</div>
<div><br></div><div>JSON is good for a lot of things, but not for passing e=
ncrypted objects around unless they are really small. So JOSE is interestin=
g but only in a very limited field. If we can encode binary data in JSON wi=
thout a 33% inflation in size, JOSE suddenly becomes very interesting indee=
d.</div>
<div><br></div><div>If JOSE didn&#39;t inflate the size of a data object, w=
e could use it for data level encryption. Drop a content type tag and some =
other metadata on the wrapper, encrypt the contents and we can have a CMS l=
ike blob that fits the Internet idiom much better (and there is some soon t=
o expire IP that would make animating that proposal very interesting).</div=
>
<div><br></div><div><br></div><div>But now we have a binary encoding publis=
hed on IETF standards track that is not a binary encoding of JSON but has a=
 subset that could be used to encode JSON sitting in that spot. It isn&#39;=
t a consensus document, isn&#39;t a product of open process, it is however =
on IETF standards track. So the job for anyone doing the job properly has b=
ecome harder.</div>
<div><br></div><div>So it is kind of like the Sochi which will always be th=
e OoOo* Olympics.</div><div><br></div><div>The only thing that makes an enc=
oding interesting is that a constituency of users agree to all make use of =
it. JSON has emerged from a field of thousands of text encodings because it=
 is the best compromise between simplicity and functionality that has such =
a wide user base. So having random specs given standards status when the de=
signers only attempted to solve the problems they cared about does not help=
 matters.</div>
<div><br></div><div><br></div><div>My main concern is the process question.=
 I really don&#39;t care whether CBOR is a PROPOSED STANDARD or whatever. W=
hat I do care about is if I am told that I have to use it because that is t=
he IETF standard for binary encoding. And what I care most about is the ris=
k that this approach of &#39;its our ball and only we will decide who gets =
to play&#39; is going to be repeated.</div>
<div><br></div><div>There are cases where it makes perfect sense for a draf=
t to go straight onto the standards track. There are plenty of extensions t=
o PKIX that are important enough to write down but not so important that it=
 is worth running up a whole working group just to decide them.</div>
<div><br></div><div><br></div><div>But a spec whose only purpose is to prov=
ide a platform for other specs really needs to clear a higher bar than not =
being idiotic and having some people willing to implement. There have to be=
 people who want to choose to build on it.</div>
<div><br></div><div><br></div><div>The way I think the process should work =
is:</div><div><br></div><div>1) The IAB identifies the need for a consensus=
 binary encoding for JSON as a platform the IETF community can build on (or=
 why call it an architecture board).</div>
<div><br></div><div>2) People write drafts that elaborate on the requiremen=
ts and/or propose schemes that meet them, these are published as either EXP=
ERIMENTAL or INFORMATIONAL.</div><div><br></div><div>3) People who are buil=
ding applications that build on the platform kick the tires and decide whic=
h ones they like / hate etc. Either a consensus emerges that one encoding i=
s best in which case we can go to step 4, otherwise we go back to step 2.</=
div>
<div><br></div><div>4) PROPOSED STANDARD status is awarded in recognition o=
f the fact that there is a defacto standard that application protocol desig=
ners have converged on. This may involve spinning up a working group to cle=
an up the documents or not depending on their quality.</div>
<div><br></div><div><br></div><div>I have seen the shotgun standards approa=
ch in the past. BEEP tried that route, it was a complete failure as a resul=
t because it moved through the standards process so fast it never gained an=
y buy in outside the original design team. So even though it has features t=
hat are very sound and the HTTP/2.0 WG might well end up re-inventing it wa=
s still born because the proposers thought that standards track was the rou=
te to driving adoption rather than recognition of adoption.</div>
<div><br></div><div>Standards is the process of making decisions that don&#=
39;t matter. It does not really matter what the HTTP protocol syntax is pro=
vided that a decision has been made to choose one syntax for that task inst=
ead of five.</div>
<div><br></div><div>So I would like to see the IAB actually doing the job o=
f an architecture board and identifying gaps in the IETF stack where conver=
gence on one particular way of solving a problem would be beneficial. That =
is not saying that they should be the people providing the solution.</div>
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--14dae94736b531a3e304f2cbb59f--


From nobody Wed Feb 19 16:48:22 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 EE4111A010A for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 16:48:20 -0800 (PST)
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 wLRHYUJkwGJQ for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 16:48:19 -0800 (PST)
Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by ietfa.amsl.com (Postfix) with ESMTP id CCBE61A0536 for <ietf@ietf.org>; Wed, 19 Feb 2014 16:48:18 -0800 (PST)
Received: by mail-vc0-f176.google.com with SMTP id la4so1187884vcb.21 for <ietf@ietf.org>; Wed, 19 Feb 2014 16:48:15 -0800 (PST)
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=MTNgVCC8q8liJgjSUTyR8rrif29lQHzzsY46Jj+pmj0=; b=jO1GmbrBM86Ixics/ykYACMr8tHlIRXc5wCs/dwG+sbXcn3PMDjyAqL/c7I+LmqsV8 bzJj1ZM5mQ/50jgVrfxfDffat0qd8Ay9kDk5E1aZBD6IuPx6NAOJ0Iw9f+M+wnb9e51I vaZTfZZ1gOujCAZBEqkXnpbBWmiSnX5zt6PhnfzDnDeKDvb+jMM0rccnejoA/nXtk+xP HfFrZadnCBW8Jm/jcaWj42a+FziUdjSzAoSbREwMSCC7/sOeRggiph40xCNDiCnTxbVh 6kvKbt9ZDcd1K5LPLOqgB4BkC7NvOrqIRh30p00yWH7RP/KRCodnnP9vxpJkEHDrYYvx /emQ==
X-Gm-Message-State: ALoCoQmVxCHVLByw0I+EJcWmpsSCpXyiEu8itf+5mdANuHKLw84a9bcWUjCWdPMCjZLfGHkeDboW
MIME-Version: 1.0
X-Received: by 10.221.66.73 with SMTP id xp9mr23120888vcb.27.1392857295280; Wed, 19 Feb 2014 16:48:15 -0800 (PST)
Received: by 10.220.98.73 with HTTP; Wed, 19 Feb 2014 16:48:15 -0800 (PST)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <6.2.5.6.2.20140219132307.0d0155b0@resistor.net> <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com>
Date: Wed, 19 Feb 2014 16:48:15 -0800
Message-ID: <CAHBU6itQy=92FW0uUdEuJY021Ua5oPGbA=4FybZM7U5sbGP_RQ@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Tim Bray <tbray@textuality.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: multipart/alternative; boundary=001a113642e64eee8104f2cbdc22
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PumjNlbx3dDlf0oQauLrmro6iNg
Cc: Barry Leiba <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@mit.edu>, S Moonesamy <sm+ietf@elandsys.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: Thu, 20 Feb 2014 00:48:21 -0000

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

On Wed, Feb 19, 2014 at 4:37 PM, Phillip Hallam-Baker <hallam@gmail.com>wro=
te:

>
> The way I think the process should work is:
>
> 1) The IAB identifies the need for a consensus binary encoding for JSON a=
s
> a platform the IETF community can build on (or why call it an architectur=
e
> board).
>

It=E2=80=99s not obvious that such a consensus exists.  In my experience, m=
essage
parsing times are dominated by memory management and network pipes are
congested by multimedia files and wrapping binary blobs in general-purpose
data packaging formats is usually the wrong thing to do anyhow for a
variety of reasons.  Thus, I question the utility of a binary encoding of
JSON.  Examining the trial of tears that went into the attempts to make a
=E2=80=9Cbinary XML=E2=80=9D would be instructive in this context.

--001a113642e64eee8104f2cbdc22
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 W=
ed, Feb 19, 2014 at 4:37 PM, Phillip Hallam-Baker <span dir=3D"ltr">&lt;<a =
href=3D"mailto:hallam@gmail.com" 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"><div dir=3D"ltr"><br><div class=3D"gmail_ext=
ra"><div>The way I think the process should work is:</div><div><br></div><d=
iv>1) The IAB identifies the need for a consensus binary encoding for JSON =
as a platform the IETF community can build on (or why call it an architectu=
re board).</div>
</div></div></blockquote><div><br></div><div>It=E2=80=99s not obvious that =
such a consensus exists. =C2=A0In my experience, message parsing times are =
dominated by memory management and network pipes are congested by multimedi=
a files and wrapping binary blobs in general-purpose data packaging formats=
 is usually the wrong thing to do anyhow for a variety of reasons. =C2=A0Th=
us, I question the utility of a binary encoding of JSON. =C2=A0Examining th=
e trial of tears that went into the attempts to make a =E2=80=9Cbinary XML=
=E2=80=9D would be instructive in this context.</div>
<div><br></div><div><br></div></div></div></div>

--001a113642e64eee8104f2cbdc22--


From nobody Wed Feb 19 16:51: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 6C28A1A05DD for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 16:51:44 -0800 (PST)
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 cJukczx16mTh for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 16:51:41 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.165]) by ietfa.amsl.com (Postfix) with ESMTP id 775F91A0467 for <ietf@ietf.org>; Wed, 19 Feb 2014 16:51:40 -0800 (PST)
Received: from [195.245.230.131:15428] by server-5.bemta-3.messagelabs.com id 2B/3D-04712-89155035; Thu, 20 Feb 2014 00:51:36 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-78.messagelabs.com!1392857495!23971419!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 11615 invoked from network); 20 Feb 2014 00:51:35 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-9.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 20 Feb 2014 00:51:35 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Thu, 20 Feb 2014 00:51:34 +0000
From: <l.wood@surrey.ac.uk>
To: <hallam@gmail.com>, <sm+ietf@elandsys.com>
Date: Thu, 20 Feb 2014 00:51:11 +0000
Subject: RE: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
Thread-Topic: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
Thread-Index: Ac8t1A5/7rzGP0KNTLGFpR4IlTyeoQAAcrTM
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334722@EXMB01CMS.surrey.ac.uk>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <6.2.5.6.2.20140219132307.0d0155b0@resistor.net>, <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com>
In-Reply-To: <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@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/s4dOvwxnH5fGm3ESb8DUAwmy_Io
Cc: barryleiba@computer.org, hartmans-ietf@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: Thu, 20 Feb 2014 00:51:44 -0000

The process has not been odd.

The outcome has been expedient.

Different thing.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Phillip Hallam-Baker [halla=
m@gmail.com]
Sent: 20 February 2014 00:37
To: S Moonesamy
Cc: Barry Leiba; Sam Hartman; IETF Discussion Mailing List
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 704=
9 on the Standards Track

On Wed, Feb 19, 2014 at 4:48 PM, S Moonesamy <sm+ietf@elandsys.com<mailto:s=
m+ietf@elandsys.com>> wrote:
Hi Barry,

At 13:10 19-02-2014, Barry Leiba wrote:
Phill took the first step of addressing his complaint to the
responsible AD (me).  This is my response.  If he or someone else
should choose to pursue a further appeal, the next step would be to
take it to the IESG by way of the Chair.

Selective quoting:


  "During the November IETF meeting, I received an appeal from Phillip
   Hallam-Baker to the publication of CBOR, RFC 7049, on the Standards
   Track."

RFC 7049 was published in October 2013.  As Sam Hartman mentioned it was a =
decision of the IESG.

  "Phill is questioning the process;"

That falls under the IESG.

The handling of the appeal is odd.

The whole process has been odd.

I told Jari and Barry that I was appealing the decision in Vancouver. I was=
 told to raise it with the relevant AD first. By the time he had come to a =
decision it was that too much effort had gone into building things on top o=
f CBOR since to undo the original decision.

I now realize that what I should have done was to simply send the original =
appeal to the IETF list and not gone through channels as requested.


The fundamental problem here is that as I see it the protocol world is rapi=
dly converging on JSON as the encoding of choice and there are many good re=
asons why it is a better encoding than any of the text based alternatives o=
n offer (RFC822, XML). It is thus inevitable that people will ask if a bina=
ry encoding of JSON would be better than ASN.1. Which of course is true and=
 not just because hitting yourself on the foot repeatedly with a hammer is =
better than ASN.1.

JSON is good for a lot of things, but not for passing encrypted objects aro=
und unless they are really small. So JOSE is interesting but only in a very=
 limited field. If we can encode binary data in JSON without a 33% inflatio=
n in size, JOSE suddenly becomes very interesting indeed.

If JOSE didn't inflate the size of a data object, we could use it for data =
level encryption. Drop a content type tag and some other metadata on the wr=
apper, encrypt the contents and we can have a CMS like blob that fits the I=
nternet idiom much better (and there is some soon to expire IP that would m=
ake animating that proposal very interesting).


But now we have a binary encoding published on IETF standards track that is=
 not a binary encoding of JSON but has a subset that could be used to encod=
e JSON sitting in that spot. It isn't a consensus document, isn't a product=
 of open process, it is however on IETF standards track. So the job for any=
one doing the job properly has become harder.

So it is kind of like the Sochi which will always be the OoOo* Olympics.

The only thing that makes an encoding interesting is that a constituency of=
 users agree to all make use of it. JSON has emerged from a field of thousa=
nds of text encodings because it is the best compromise between simplicity =
and functionality that has such a wide user base. So having random specs gi=
ven standards status when the designers only attempted to solve the problem=
s they cared about does not help matters.


My main concern is the process question. I really don't care whether CBOR i=
s a PROPOSED STANDARD or whatever. What I do care about is if I am told tha=
t I have to use it because that is the IETF standard for binary encoding. A=
nd what I care most about is the risk that this approach of 'its our ball a=
nd only we will decide who gets to play' is going to be repeated.

There are cases where it makes perfect sense for a draft to go straight ont=
o the standards track. There are plenty of extensions to PKIX that are impo=
rtant enough to write down but not so important that it is worth running up=
 a whole working group just to decide them.


But a spec whose only purpose is to provide a platform for other specs real=
ly needs to clear a higher bar than not being idiotic and having some peopl=
e willing to implement. There have to be people who want to choose to build=
 on it.


The way I think the process should work is:

1) The IAB identifies the need for a consensus binary encoding for JSON as =
a platform the IETF community can build on (or why call it an architecture =
board).

2) People write drafts that elaborate on the requirements and/or propose sc=
hemes that meet them, these are published as either EXPERIMENTAL or INFORMA=
TIONAL.

3) People who are building applications that build on the platform kick the=
 tires and decide which ones they like / hate etc. Either a consensus emerg=
es that one encoding is best in which case we can go to step 4, otherwise w=
e go back to step 2.

4) PROPOSED STANDARD status is awarded in recognition of the fact that ther=
e is a defacto standard that application protocol designers have converged =
on. This may involve spinning up a working group to clean up the documents =
or not depending on their quality.


I have seen the shotgun standards approach in the past. BEEP tried that rou=
te, it was a complete failure as a result because it moved through the stan=
dards process so fast it never gained any buy in outside the original desig=
n team. So even though it has features that are very sound and the HTTP/2.0=
 WG might well end up re-inventing it was still born because the proposers =
thought that standards track was the route to driving adoption rather than =
recognition of adoption.

Standards is the process of making decisions that don't matter. It does not=
 really matter what the HTTP protocol syntax is provided that a decision ha=
s been made to choose one syntax for that task instead of five.

So I would like to see the IAB actually doing the job of an architecture bo=
ard and identifying gaps in the IETF stack where convergence on one particu=
lar way of solving a problem would be beneficial. That is not saying that t=
hey should be the people providing the solution.

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


From nobody Wed Feb 19 17:00:21 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 126651A05DD for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 17:00:19 -0800 (PST)
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 YoGWuanJCzSd for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 17:00:17 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D8A821A0106 for <ietf@ietf.org>; Wed, 19 Feb 2014 17:00:17 -0800 (PST)
Received: from [172.16.22.13] (64.1.211.245.ptr.us.xo.net [64.1.211.245]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1K105rq023297 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 19 Feb 2014 17:00:08 -0800
Message-ID: <53055362.5000803@dcrocker.net>
Date: Wed, 19 Feb 2014 16:59:14 -0800
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.3.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <6.2.5.6.2.20140219132307.0d0155b0@resistor.net>, <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334722@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334722@EXMB01CMS.surrey.ac.uk>
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, 19 Feb 2014 17:00:08 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9AJ7DoX8SU009SyHVyIlySYSxvA
Cc: barryleiba@computer.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, 20 Feb 2014 01:00:19 -0000

On 2/19/2014 4:51 PM, l.wood@surrey.ac.uk wrote:
> The process has not been odd.
>
> The outcome has been expedient.
>
> Different thing.


Maybe not.  In the IETF, an expedient outcome is pretty odd.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Wed Feb 19 17:28:22 2014
Return-Path: <mnot@mnot.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 B1D0F1A0606 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 17:28:20 -0800 (PST)
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 HzhXjZp54ZBU for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 17:28:18 -0800 (PST)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) by ietfa.amsl.com (Postfix) with ESMTP id BCCBC1A02BB for <ietf@ietf.org>; Wed, 19 Feb 2014 17:28:18 -0800 (PST)
Received: from [192.168.1.55] (unknown [118.209.8.95]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id D956C509B5; Wed, 19 Feb 2014 20:28:12 -0500 (EST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com>
Date: Thu, 20 Feb 2014 12:28:10 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <285DB0AF-7E1C-403E-B204-4F3353175B01@mnot.net>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <6.2.5.6.2.20140219132307.0d0155b0@resistor.net> <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pW84zWZ1Gtwv6pxJD6MCUu7TovU
Cc: Barry Leiba <barryleiba@computer.org>, 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, 20 Feb 2014 01:28:20 -0000

On 20 Feb 2014, at 11:37 am, Phillip Hallam-Baker <hallam@gmail.com> =
wrote:

> My main concern is the process question. I really don't care whether =
CBOR is a PROPOSED STANDARD or whatever. What I do care about is if I am =
told that I have to use it because that is the IETF standard for binary =
encoding. And what I care most about is the risk that this approach of =
'its our ball and only we will decide who gets to play' is going to be =
repeated.

I have to agree with Phillip on this point, and I hope the answer is =
uncontroversial -- that just by virtue of being an IETF standard, we =
don't start requiring people to use something already defined if their =
use case is vaguely similar.=20

When something is a standard, it means you need to use it in the way =
specified; it doesn't mean you have to choose to use it, even in other =
standards.

That's not to say we shouldn't encourage people to examine, improve, =
etc. existing standards when we feel that their uses can be addressed by =
them; it's just that we don't have a "highlander rule," and for the =
health of the Internet I think that's a good thing.

If this is indeed the case, I think Phillip's concerns about the process =
are perhaps notable, but people are still free to define, use and =
standardise other approaches to binary JSON, so it shouldn't be an =
issue.

Regards,

--
Mark Nottingham   http://www.mnot.net/




From nobody Wed Feb 19 20:35:09 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 0FECD1A0547 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 20:35:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, 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 HPz-v5-OVr34 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 20:35:06 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 198E01A0544 for <ietf@ietf.org>; Wed, 19 Feb 2014 20:35:06 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.132.170]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1K4YZV7010339 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Feb 2014 20:34:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392870889; bh=4+bMIrwanqiB03OzvVKm30D+v9r0SA3uM+zILtFAcDU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rieqHRHavwxdd7vyOhawMMtpgvCveoAPdUE+a5LUnj8nQcvAZXd1YXC6qj3Nfl1vd MZkJcY2g6HmtksOljvpaampRQ+cbJnq/9VJOjXyT7tQhZBChPLu9HCbth5KB11kMPW szOowe5e3PXOcwcIKFjEPsSbNdr2VpbGVySPTFEc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1392870889; i=@elandsys.com; bh=4+bMIrwanqiB03OzvVKm30D+v9r0SA3uM+zILtFAcDU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WJajCMM4ioURPR9icvLWudkVMAt3bRL42Nnc5zQ9dup2O5f1/sdTy62jG8yvil7/5 vPvzcIc2J6UEV0OPTer/SCz0W/IKjpTSSTYSArKlnC1LQMw5jTA2SRVtvcq4SC5ZNB 6vtHNu+kZz7MAxi4X7ZDhc/KOyGm3p6oCD8cQ8JA=
Message-Id: <6.2.5.6.2.20140219171931.0d604f08@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 19 Feb 2014 20:18:12 -0800
To: Phillip Hallam-Baker <hallam@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
In-Reply-To: <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.g mail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <6.2.5.6.2.20140219132307.0d0155b0@resistor.net> <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@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/eEA0f_zRF98cuAowrvKh-O5fhNw
Cc: Barry Leiba <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@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: Thu, 20 Feb 2014 04:35:08 -0000

Hi Phillip,
At 16:37 19-02-2014, Phillip Hallam-Baker wrote:
>The whole process has been odd.
>
>I told Jari and Barry that I was appealing the decision in 
>Vancouver. I was told to raise it with the relevant AD first. By the 
>time he had come to a decision it was that too much effort had gone 
>into building things on top of CBOR since to undo the original decision.
>
>I now realize that what I should have done was to simply send the 
>original appeal to the IETF list and not gone through channels as requested.

The RFC was published before the Vancouver meeting.  There was a 
four-weeks Last Call before that.  This was an extremely late 
appeal.  There were some red flags during the Last Call.  I assumed 
that somebody would have noticed them and done something about that.

>But now we have a binary encoding published on IETF standards track 
>that is not a binary encoding of JSON but has a subset that could be 
>used to encode JSON sitting in that spot. It isn't a consensus 
>document, isn't a product of open process, it is however on IETF 
>standards track. So the job for anyone doing the job properly has 
>become harder.

I'll suggest writing a (technical) draft about the topic and getting 
it published by the ISE.

>The way I think the process should work is:
>
>1) The IAB identifies the need for a consensus binary encoding for 
>JSON as a platform the IETF community can build on (or why call it 
>an architecture board).
>
>2) People write drafts that elaborate on the requirements and/or 
>propose schemes that meet them, these are published as either 
>EXPERIMENTAL or INFORMATIONAL.
>
>3) People who are building applications that build on the platform 
>kick the tires and decide which ones they like / hate etc. Either a 
>consensus emerges that one encoding is best in which case we can go 
>to step 4, otherwise we go back to step 2.
>
>4) PROPOSED STANDARD status is awarded in recognition of the fact 
>that there is a defacto standard that application protocol designers 
>have converged on. This may involve spinning up a working group to 
>clean up the documents or not depending on their quality.

[snip]

>So I would like to see the IAB actually doing the job of an 
>architecture board and identifying gaps in the IETF stack where 
>convergence on one particular way of solving a problem would be 
>beneficial. That is not saying that they should be the people 
>providing the solution.

The reason for a charter is to inform people of the work which will 
be done.  In practice, most people do not pay attention to that.

I don't think that (2) and (3) is workable as it can lead to 
polarized discussions where it would be difficult to reach 
agreement.  By the way, (4) is what Internet Standard is supposed to be.

Regards,
S. Moonesamy 


From nobody Wed Feb 19 21:55:08 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 C894F1A0263; Wed, 19 Feb 2014 21:55:05 -0800 (PST)
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, GB_I_INVITATION=-2] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id beoBrZ6foeS4; Wed, 19 Feb 2014 21:55:04 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B5C71A0547; Wed, 19 Feb 2014 21:55:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Chair <chair@ietf.org>
To: 89all@ietf.org
Subject: Invitation to Participate in Mentoring Program
X-Test-IDTracker: no
X-IETF-IDTracker: 5.0.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140220055504.7370.22981.idtracker@ietfa.amsl.com>
Date: Wed, 19 Feb 2014 21:55:04 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5BAWSqK7O3VrHu_pOevQZ0Rl5hM
Cc: ietf@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: Thu, 20 Feb 2014 05:55:06 -0000

All,

At IETF 89 we will once again offer the IETF Mentoring Program. The goal
of the IETF Mentoring Program is to match IETF participants who may be new
or otherwise in need of guidance with experienced IETF mentors. As a
mentoring participant, your mentor will personally introduce you to the
IETF community, help you find your way around the IETF & the meeting,
explain things, and introduce you to other attendees you might like to
meet. Basically, your mentor will be your personal buddy during the
meeting week, and possibly afterwards.

Unlike in the past, at IETF 89 we will accept requests for mentors from
anyone who wants one, regardless of how many meetings they have attended
previously. We cannot guarantee that every request will be honored, but we
will do our best.

If you wish to participate in the IETF Mentoring Program, you can follow
the sign-up procedures described in the program FAQ:

https://www.ietf.org/resources/mentoring-program.html

After you follow the sign-up procedure, we will introduce you to your
mentor by email prior to IETF 89, and invite you to meet up in person at
the IETF Meet & Greet event on Sunday afternoon in London. From there on,
you and your mentor decide on when and where to meet during the rest of
the week and afterwards.

You are of course free to withdraw from the program at any time and for
any reason, no questions asked, should a need arise. But I sincerely
believe the IETF Mentoring Program will be a great way for new
participants to get introduced to the IETF by an experienced participant
with matching interest.

Regards,
Jari Arkko
IETF Chair


From nobody Wed Feb 19 23:05:01 2014
Return-Path: <ggm@algebras.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 4BB3A1A0551 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 23:04:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, 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 6kcYGBb7IB5I for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 23:04:58 -0800 (PST)
Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) by ietfa.amsl.com (Postfix) with ESMTP id 325AA1A0443 for <ietf@ietf.org>; Wed, 19 Feb 2014 23:04:58 -0800 (PST)
Received: by mail-pd0-f182.google.com with SMTP id v10so1436509pde.41 for <ietf@ietf.org>; Wed, 19 Feb 2014 23:04:54 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=OIOErB46+bPGC1RC1RITdRwHg0PHBvfvmCEleJr9ot8=; b=KgC0QFzgzrob/mxveCvThaZZ1d+w2OW4kSjMaYSVQnz1bkB4q5QssxL+GZDquoG/Ip Eyv2lKPD2tbxaxNG4BKTQXLk8Mj4Qs43QFzPRz1G7IAmCKSqUzj73GBN90E18cMiNaNa TtN719+qdpIAFQVDmnPxqfb3n+kkTA4K4pfTNzfEunED1dmAhPCwF//6Qi/8YceG0cL+ kuJSdKlP3mJUqf7v/Jh5ao9O+LHXaaPXutpHiW5UKS3aAA425TIQfHxfRu+SuvXy2iZh jJqRhQ7vciJYQC4N7h3hm1XeRbfI19EbhsPKgo1NB+sYpFEeXknLqC4VBsFdyJWfrpS/ CImg==
X-Gm-Message-State: ALoCoQnbbuHqB6iY1vqVqLgpey3HARhmv4HVtbzVOs/A/RF4VPoTrubSZtfMiX0T57RkxWOJ6xUG
MIME-Version: 1.0
X-Received: by 10.68.201.226 with SMTP id kd2mr103021pbc.157.1392879894805; Wed, 19 Feb 2014 23:04:54 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Wed, 19 Feb 2014 23:04:54 -0800 (PST)
X-Originating-IP: [2001:dc0:a000:4:9c66:6152:d895:8a84]
Date: Thu, 20 Feb 2014 17:04:54 +1000
Message-ID: <CAKr6gn28Myr0uqo545dQ31n8AdeMOKsYwsg1QBMDQm_QVQgqSQ@mail.gmail.com>
Subject: Apple cable swap..
From: George Michaelson <ggm@algebras.org>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=e89a8ff1c37a585aab04f2d11f82
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/M2gOj0hnaxWT4JEft29G0lrlDIo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Feb 2014 07:04:59 -0000

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

If anyone is organising a cable swap again I have several Apple 'Aus/NZ'
cables and plugs I can bring.

Happy to exchange for UK/US/Schuko

--e89a8ff1c37a585aab04f2d11f82
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">If anyone is organising a cable swap again I have several Apple &#39;Aus/NZ&#39; cables and plugs I can bring.<div><br></div><div>Happy to exchange for UK/US/Schuko</div></div>

--e89a8ff1c37a585aab04f2d11f82--


From nobody Wed Feb 19 23:22:49 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 5325C1A0355 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 23:22:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.704
X-Spam-Level: 
X-Spam-Status: No, score=-6.704 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P0ztS8dEGiit for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 23:22:46 -0800 (PST)
Received: from aer-iport-4.cisco.com (unknown [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id CAF461A033F for <ietf@ietf.org>; Wed, 19 Feb 2014 23:22:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1224; q=dns/txt; s=iport; t=1392880962; x=1394090562; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=YlMivOiQtwTgSALTobFkBKzNzRbXJp7xxTtQ/jHd5kc=; b=MpLLa0Otiw1WTBcsOJ76KvlbnrOfJHN0W1nwufwsrJDeE5pirVyEq8xm bq6uQznB8R6UfXlZLaEI4ph5TxX1ounYp1lfBkSulf+Ly5JJWGlsybmaW TpfHNqPsKQuZgFYIgQiJcoWEH3DA8N1DmyNTm0MycBgowaz5w5GE18gKD I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFABKtBVOQ/khR/2dsb2JhbABZgwaEEbx9gRUWdIIlAQEBBCNVARALDgoCAgUWCwICCQMCAQIBDxwaBgEMAQUCAQGHbQMRrHaZQA2HcBeBKYsmghUHgm+BSQEDlkSBbIxehUaBb4E/Ow
X-IronPort-AV: E=Sophos;i="4.97,511,1389744000";  d="scan'208";a="797365"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-4.cisco.com with ESMTP; 20 Feb 2014 07:22:30 +0000
Received: from mctiny.local ([10.61.203.44]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1K7MTWp006310 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Thu, 20 Feb 2014 07:22:30 GMT
Message-ID: <5305AD36.3050209@cisco.com>
Date: Thu, 20 Feb 2014 08:22:30 +0100
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.3.0
MIME-Version: 1.0
To: Mark Nottingham <mnot@mnot.net>, Phillip Hallam-Baker <hallam@gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <6.2.5.6.2.20140219132307.0d0155b0@resistor.net> <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com> <285DB0AF-7E1C-403E-B204-4F3353175B01@mnot.net>
In-Reply-To: <285DB0AF-7E1C-403E-B204-4F3353175B01@mnot.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/3vg31IG2y3sbZMkFKbVupz6peN0
Cc: Barry Leiba <barryleiba@computer.org>, 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, 20 Feb 2014 07:22:47 -0000

<no hat>
On 2/20/14, 2:28 AM, Mark Nottingham wrote:
> On 20 Feb 2014, at 11:37 am, Phillip Hallam-Baker <hallam@gmail.com> wrote:
>
>> My main concern is the process question. I really don't care whether CBOR is a PROPOSED STANDARD or whatever. What I do care about is if I am told that I have to use it because that is the IETF standard for binary encoding. And what I care most about is the risk that this approach of 'its our ball and only we will decide who gets to play' is going to be repeated.
> I have to agree with Phillip on this point, and I hope the answer is uncontroversial -- that just by virtue of being an IETF standard, we don't start requiring people to use something already defined if their use case is vaguely similar. 
>
> When something is a standard, it means you need to use it in the way specified; it doesn't mean you have to choose to use it, even in other standards.

Yeah, we're off the rails here, and it's becoming a bad habit.  People
seem to like playing "what if" games about how bad things can get if
everyone loses their heads.  WGs and spec developers should always use
what makes sense (standard or no).  Rough consensus and running code,
thank you very much.

Eliot


From nobody Thu Feb 20 06:12:06 2014
Return-Path: <rdroms.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 BF01D1A0173 for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 06:12:04 -0800 (PST)
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 LZUM6B4IvR3C for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 06:12:03 -0800 (PST)
Received: from mail-qc0-x22a.google.com (mail-qc0-x22a.google.com [IPv6:2607:f8b0:400d:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id ECD201A0192 for <ietf@ietf.org>; Thu, 20 Feb 2014 06:12:02 -0800 (PST)
Received: by mail-qc0-f170.google.com with SMTP id c9so2971317qcz.15 for <ietf@ietf.org>; Thu, 20 Feb 2014 06:11:59 -0800 (PST)
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=KbxyB/oKVl6CRttQ6VluIVhdEOh3Xx1OSATvOtBavRg=; b=lF/QIgZaimehw2Mmgit09ldG7jj0psLRn4k/JZseGuD04RklyzOIPa4nK1i8cJluXQ IPJknNexTAQ5LI6OAxpNmv4pJpGz2BUjc47jKWC4ZY78EM6SaBzdp9BGg6Ery2DZgGzw 52duWQOd1mpNmI34Q+jC+EL3P2GVEB0fUlqUckhAOhiLlQxklWtOxLan4MkACayyi9hU iQANHA8H7cV+gACGn/DGfjSYHPrfqNElfZZfqsNkFfVHFSEDReTXhm30gPc3kNAMoLks Rjp645WfDYUSdCwvuUvvFvAzkHhp3PCsnDUEHMCNDqZStSBeN6N4awL8OT6SiK2iOAK7 1nYg==
X-Received: by 10.140.20.17 with SMTP id 17mr1756148qgi.28.1392905519236; Thu, 20 Feb 2014 06:11:59 -0800 (PST)
Received: from [10.86.255.189] (198-135-0-233.cisco.com. [198.135.0.233]) by mx.google.com with ESMTPSA id i7sm12402807qan.0.2014.02.20.06.11.56 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Feb 2014 06:11:57 -0800 (PST)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Ralph Droms <rdroms.ietf@gmail.com>
In-Reply-To: <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com>
Date: Thu, 20 Feb 2014 09:11:55 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <A9AB0AA4-7229-4F43-B7D8-75599E2F8F49@gmail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com>
To: IETF discussion list <ietf@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iphkx9BVm8tyox04MTtxM14JJ0E
Cc: Leiba Barry <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@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, 20 Feb 2014 14:12:04 -0000

On Feb 19, 2014, at 4:10 PM 2/19/14, Barry Leiba =
<barryleiba@computer.org> wrote:

>> As a matter of process, I'm confused about the handling of this =
appeal.
>> It sounds like Phil appealed the approval of RFC 7049.
>>=20
>> That, I hope, was a decision made by the IESG, not a decision made by
>> one AD.
>> So, I'm failing to understand how it makes sense for you to respond =
to
>> this appeal as an AD.
>=20
> Phill took the first step of addressing his complaint to the
> responsible AD (me).  This is my response.

So, to clarify the process, Phill did not submit an appeal to the IESG =
under section 6.5 of RFC 2026.  Rather, he took his complaint directly =
to you.

As an aside at this point - is there a formal description of this =
complaint to you as an "appeal"?  If so, where is the process =
documented?

Phill's complaint appears to be directed at the IESG process: "My issue =
here is [...] the manner in which CBOR was made a standard has negated =
the value of having it being proposed as a standard."  You wrote: "his =
appeal did come in within the two-month appeal window after the approval =
announcement."  Yet Phill's complaint/appeal appears to have been =
handled solely by you, rather than through the process described in =
section 6.5 of RFC 2026.

I'm not arguing with what has been described as an expedient outcome.  =
Barry has responded unilaterally to Phill's complaint and not as a part =
of a formal appeal by Phill; Phill is satisfied with that response and =
has not, to date, filed a formal appeal.  If I have that right, then =
Barry should clarify that this complaint/response was not part of the =
formal appeals process.  For example, here:

>  If he or someone else
> should choose to pursue a further appeal, the next step would be to
> take it to the IESG by way of the Chair

Barry should make clear that Phill would be taking up a formal appeal =
under RFC 2026, after following an informal discussion of his complaint =
with the responsible AD.

My concern is that we not establish some de facto extension to our =
processes by labeling this particular example of complaint resolution as =
a formal appeal.

- Ralph


>=20
> Barry
>=20


From nobody Thu Feb 20 06:46:20 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 4AD441A01B9 for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 06:46:18 -0800 (PST)
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 NJOwucRkSEfa for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 06:46:16 -0800 (PST)
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 17EF51A01B0 for <ietf@ietf.org>; Thu, 20 Feb 2014 06:46:07 -0800 (PST)
Received: by mail-la0-f53.google.com with SMTP id e16so1375742lan.26 for <ietf@ietf.org>; Thu, 20 Feb 2014 06:46:03 -0800 (PST)
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=ONCQXZttW4xdiW8wj4JS/pbq8SK0eDlZ2jEJ6hJ4y4o=; b=LBQkKIhTyb0vCW4br/C64yLWXPpxw1otCQOGuBB44Jm8GJw7cDWclvRjVSiVEYbvh9 isWR09HMQCCD5IzveNNDqVxu4RRvunmHJS4ZsLmq4U5fw3as90iKdOGKYWnx90gwFlhY Gxm9mfsLOHYdmriOteBNHUNkn9d7srN+ri5R4nFrcmOU2SJ6crmgOZn8CWKpZT5zE/DQ 5PIXNxhzFCrr/ruavrs/iz7daP0Cm03lZuItQxByTxssmESFekjOt166aCz4p0fjcrW9 OTzroydpM1F4NN0aBxnEufreN2Jh9UoOqqfsYjuTBmwVu6kRya4PSmF6jRzrv20db+Qg JDdA==
MIME-Version: 1.0
X-Received: by 10.112.138.233 with SMTP id qt9mr1368010lbb.34.1392907563815; Thu, 20 Feb 2014 06:46:03 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Thu, 20 Feb 2014 06:46:03 -0800 (PST)
In-Reply-To: <A9AB0AA4-7229-4F43-B7D8-75599E2F8F49@gmail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <A9AB0AA4-7229-4F43-B7D8-75599E2F8F49@gmail.com>
Date: Thu, 20 Feb 2014 09:46:03 -0500
Message-ID: <CAMm+LwhvCtan+hfK5ivHznNbZ0OMjQk23hoD4tqoXK+yLhZS5Q@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Content-Type: multipart/alternative; boundary=089e012297108bd65004f2d790ab
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/BTdMNHbp86T9XXq5D69wCC_-HZ8
Cc: Leiba Barry <barryleiba@computer.org>, Sam Hartman <hartmans-ietf@mit.edu>, 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, 20 Feb 2014 14:46:18 -0000

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

On Thu, Feb 20, 2014 at 9:11 AM, Ralph Droms <rdroms.ietf@gmail.com> wrote:

>
> On Feb 19, 2014, at 4:10 PM 2/19/14, Barry Leiba <barryleiba@computer.org>
> wrote:
>
> >> As a matter of process, I'm confused about the handling of this appeal.
> >> It sounds like Phil appealed the approval of RFC 7049.
> >>
> >> That, I hope, was a decision made by the IESG, not a decision made by
> >> one AD.
> >> So, I'm failing to understand how it makes sense for you to respond to
> >> this appeal as an AD.
> >
> > Phill took the first step of addressing his complaint to the
> > responsible AD (me).  This is my response.
>
> So, to clarify the process, Phill did not submit an appeal to the IESG
> under section 6.5 of RFC 2026.  Rather, he took his complaint directly to
> you.
>
> As an aside at this point - is there a formal description of this
> complaint to you as an "appeal"?  If so, where is the process documented?
>

It was an appeal because I advise the IETF chair that I wished to make an
appeal and I followed the procedure that he advised me to take and the AD
advised me to take.

I don't believe that I should be the one looking through books to find out
what the correct appeals process is.


My complaints are as follows:

1) I was prevented from contributing to what purports to be an IETF
proposed standard.

2) I made complaints about this in last call

3) I was effectively denied the ability to appeal.


So yes, I do insist that this be listed as an appeal in the plenary and
that the outcome is listed as 'it was botched'.


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

--089e012297108bd65004f2d790ab
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 Thu, Feb 20, 2014 at 9:11 AM, Ralph Droms <span dir=3D"ltr">&lt;=
<a href=3D"mailto:rdroms.ietf@gmail.com" target=3D"_blank">rdroms.ietf@gmai=
l.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""><br>
On Feb 19, 2014, at 4:10 PM 2/19/14, Barry Leiba &lt;<a href=3D"mailto:barr=
yleiba@computer.org">barryleiba@computer.org</a>&gt; wrote:<br>
<br>
&gt;&gt; As a matter of process, I&#39;m confused about the handling of thi=
s appeal.<br>
&gt;&gt; It sounds like Phil appealed the approval of RFC 7049.<br>
&gt;&gt;<br>
&gt;&gt; That, I hope, was a decision made by the IESG, not a decision made=
 by<br>
&gt;&gt; one AD.<br>
&gt;&gt; So, I&#39;m failing to understand how it makes sense for you to re=
spond to<br>
&gt;&gt; this appeal as an AD.<br>
&gt;<br>
&gt; Phill took the first step of addressing his complaint to the<br>
&gt; responsible AD (me). =A0This is my response.<br>
<br>
</div>So, to clarify the process, Phill did not submit an appeal to the IES=
G under section 6.5 of RFC 2026. =A0Rather, he took his complaint directly =
to you.<br>
<br>
As an aside at this point - is there a formal description of this complaint=
 to you as an &quot;appeal&quot;? =A0If so, where is the process documented=
?<br></blockquote><div><br></div><div>It was an appeal because I advise the=
 IETF chair that I wished to make an appeal and I followed the procedure th=
at he advised me to take and the AD advised me to take.</div>
<div><br></div><div>I don&#39;t believe that I should be the one looking th=
rough books to find out what the correct appeals process is.</div><div><br>=
</div><div><br></div><div>My complaints are as follows:</div><div><br></div=
>
<div>1) I was prevented from contributing to what purports to be an IETF pr=
oposed standard.</div><div><br></div><div>2) I made complaints about this i=
n last call</div><div><br></div><div>3) I was effectively denied the abilit=
y to appeal.</div>
<div><br></div><div><br></div><div>So yes, I do insist that this be listed =
as an appeal in the plenary and that the outcome is listed as &#39;it was b=
otched&#39;.</div><div><br></div></div><div><br></div>-- <br>Website: <a hr=
ef=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>

</div></div>

--089e012297108bd65004f2d790ab--


From nobody Thu Feb 20 07:40:29 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 841ED1A01CC for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 07:40:28 -0800 (PST)
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 DrbXW1ygmVOR for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 07:40:25 -0800 (PST)
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 B746E1A0170 for <ietf@ietf.org>; Thu, 20 Feb 2014 07:40:24 -0800 (PST)
Received: by mail-la0-f54.google.com with SMTP id y1so1412086lam.41 for <ietf@ietf.org>; Thu, 20 Feb 2014 07:40:20 -0800 (PST)
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=jDkpzq2R3LAQPc3iPzdbEKhaHj3aObui4OIq3M/BQc0=; b=bYmO+GYwLoTZAweTRPshPV+ujxI3mYnKX9w0mHS0J+DoKuGsRXTV5T2m0KC1GXW7Kv mRGJkGoJf/JAzD2OlexICwH9Syc/62egYD9z38ff/O5SW6iUkeH/qqzvQPtFmo6UerhY iCBobZKhUim0EQxHr2s8F/7OSojuiVn/VYrtG7cDo+OyNx66JRi3JQLH8a2ZA7m6Dzgf glhPz4GkgvCDEoXesxNdp4qhYop8eLw6vqfl7rvWQWqQ1dm8lZdQ6J5gYULSi9QjnxH/ nkEG5+owBtyrNeUhm5BOOjqk+vVbJkD8DVVTUi9wBR8dG1Fl/FBCqsNSiDne8I5QNgss BLQA==
MIME-Version: 1.0
X-Received: by 10.152.203.193 with SMTP id ks1mr1624225lac.0.1392910820161; Thu, 20 Feb 2014 07:40:20 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Thu, 20 Feb 2014 07:40:20 -0800 (PST)
In-Reply-To: <5305AD36.3050209@cisco.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <6.2.5.6.2.20140219132307.0d0155b0@resistor.net> <CAMm+Lwjs5CT86N8we9BKS++5+6qufCotoJRSEJt6hedVMd+DUg@mail.gmail.com> <285DB0AF-7E1C-403E-B204-4F3353175B01@mnot.net> <5305AD36.3050209@cisco.com>
Date: Thu, 20 Feb 2014 10:40:20 -0500
Message-ID: <CAMm+Lwi1xbidwLCugcFs_=1QKp1MP=UtM=Mw-8xuvhO=z=qu-A@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Eliot Lear <lear@cisco.com>
Content-Type: multipart/alternative; boundary=001a113470d2a3bf7504f2d8527d
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/h-zK6YBd9_uChey-z_QJgGBczQc
Cc: Mark Nottingham <mnot@mnot.net>, Barry Leiba <barryleiba@computer.org>, 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, 20 Feb 2014 15:40:28 -0000

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

On Thu, Feb 20, 2014 at 2:22 AM, Eliot Lear <lear@cisco.com> wrote:

> <no hat>
> On 2/20/14, 2:28 AM, Mark Nottingham wrote:
> > On 20 Feb 2014, at 11:37 am, Phillip Hallam-Baker <hallam@gmail.com>
> wrote:
> >
> >> My main concern is the process question. I really don't care whether
> CBOR is a PROPOSED STANDARD or whatever. What I do care about is if I am
> told that I have to use it because that is the IETF standard for binary
> encoding. And what I care most about is the risk that this approach of 'its
> our ball and only we will decide who gets to play' is going to be repeated.
> > I have to agree with Phillip on this point, and I hope the answer is
> uncontroversial -- that just by virtue of being an IETF standard, we don't
> start requiring people to use something already defined if their use case
> is vaguely similar.
> >
> > When something is a standard, it means you need to use it in the way
> specified; it doesn't mean you have to choose to use it, even in other
> standards.
>
> Yeah, we're off the rails here, and it's becoming a bad habit.  People
> seem to like playing "what if" games about how bad things can get if
> everyone loses their heads.  WGs and spec developers should always use
> what makes sense (standard or no).  Rough consensus and running code,
> thank you very much.
>

Oddly enough, compact formats for protocol encodings are one specification
that never need to be implemented to have value.

Back in the XKMS vs SCVP days a journalist tried to compare the two specs.
Since all they understood was the message size, that was the basis for
comparison. An SCVP message is maybe 1KB and an XKMS message might be as
much as 3KB (I am guessing here).

Given that both easily fit into an IP packet and they involve public key
cryptography, the size of the message would be completely irrelevant even
if the two protocols were equivalent (which they are not). But the story
was taken up and used as FUD.

If we had has a compact encoding for XML, we could have easily defeated the
FUD by pointing out that people who care can use the efficient encoding
option and the 'problem' goes away.


The issue can also come up at the design stage. Earlier this morning
someone proposed the following as an example of a JSON microformat:

microformat GPSLocation;
   // A GPSLocation is a pair of comma separated floating-point
   // numbers representing longitude and latitude.
   // e.g. "location": "0.0,51.5"

But this is not using JSON encoding at all, it is a string with two decimal
fractions separated by a coma. The JSON encoding would be:

"location" : {"X":0.0,"Y":51.5}

The justification for the microformat is of course byteshaving. And of
course the example being artificial is unrepresentative. In the normal case
the comparison would be

"210.012345,51.52232" vs {"X" : 210.012345,"Y" : 51.52232}

The difference is 3 control bytes versus 9 for the tagged version. Which
isn't actually a lot of overhead for a tagged text format.


But imagine we have an efficient binary encoding that can represent those
numbers in 5 bytes rather than 10. The efficient binary encoding is much
more efficient than the handcoded binary.

Having a compact binary notation about provides a tool that can be swung
when someone is messing about with a microformat that is only going to
cause grief. If a specification is using JSON encoding then it should use
JSON encoding, not JSON plus a bunch of poorly thought out ad hoc hacks
that seemed like a good idea at the time.

When people reach for regular expressions I reach for the sick bag.

Regular expressions are a very powerful tool that can be used to create
more complexity in fewer lines of code than any other language I know
(including APL). They are like using GOTOs. Every non-trivial program
without exception has GOTO statements but in a structured programing
language the programmer does not code them directly or need to.

So one of the challenges in using XML or JSON or any other regular data
encoding in a standards effort is to block attempts to sneak in other
encodings by way of 'microformats' that always looks such a good idea till
they have to be coded.


Having a binary encoding for the data encoding at hand allows the
microformats to the swatted away. Doing better than a text encoding is
pretty easy. Doing better than a well designed binary encoding is actually
hard.


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

--001a113470d2a3bf7504f2d8527d
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 Thu, Feb 20, 2014 at 2:22 AM, Eliot Lear <span dir=3D"ltr">&lt;<=
a href=3D"mailto:lear@cisco.com" target=3D"_blank">lear@cisco.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">&lt;no hat&gt;<br>
<div class=3D"">On 2/20/14, 2:28 AM, Mark Nottingham wrote:<br>
&gt; On 20 Feb 2014, at 11:37 am, Phillip Hallam-Baker &lt;<a href=3D"mailt=
o:hallam@gmail.com">hallam@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; My main concern is the process question. I really don&#39;t care w=
hether CBOR is a PROPOSED STANDARD or whatever. What I do care about is if =
I am told that I have to use it because that is the IETF standard for binar=
y encoding. And what I care most about is the risk that this approach of &#=
39;its our ball and only we will decide who gets to play&#39; is going to b=
e repeated.<br>

&gt; I have to agree with Phillip on this point, and I hope the answer is u=
ncontroversial -- that just by virtue of being an IETF standard, we don&#39=
;t start requiring people to use something already defined if their use cas=
e is vaguely similar.<br>

&gt;<br>
&gt; When something is a standard, it means you need to use it in the way s=
pecified; it doesn&#39;t mean you have to choose to use it, even in other s=
tandards.<br>
<br>
</div>Yeah, we&#39;re off the rails here, and it&#39;s becoming a bad habit=
. =A0People<br>
seem to like playing &quot;what if&quot; games about how bad things can get=
 if<br>
everyone loses their heads. =A0WGs and spec developers should always use<br=
>
what makes sense (standard or no). =A0Rough consensus and running code,<br>
thank you very much.<br></blockquote><div><br></div><div>Oddly enough, comp=
act formats for protocol encodings are one specification that never need to=
 be implemented to have value.</div><div><br></div><div>Back in the XKMS vs=
 SCVP days a journalist tried to compare the two specs. Since all they unde=
rstood was the message size, that was the basis for comparison. An SCVP mes=
sage is maybe 1KB and an XKMS message might be as much as 3KB (I am guessin=
g here).</div>
<div><br></div><div>Given that both easily fit into an IP packet and they i=
nvolve public key cryptography, the size of the message would be completely=
 irrelevant even if the two protocols were equivalent (which they are not).=
 But the story was taken up and used as FUD.</div>
<div><br></div><div>If we had has a compact encoding for XML, we could have=
 easily defeated the FUD by pointing out that people who care can use the e=
fficient encoding option and the &#39;problem&#39; goes away.</div><div>
<br></div><div><br></div><div>The issue can also come up at the design stag=
e. Earlier this morning someone proposed the following as an example of a J=
SON microformat:</div><div><br></div><div><span style=3D"color:rgb(80,0,80)=
;font-family:arial,sans-serif;font-size:12.666666984558105px">microformat G=
PSLocation;</span><br style=3D"color:rgb(80,0,80);font-family:arial,sans-se=
rif;font-size:12.666666984558105px">
<span style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:12=
.666666984558105px">=A0 =A0// A GPSLocation is a pair of comma separated fl=
oating-point</span><br style=3D"color:rgb(80,0,80);font-family:arial,sans-s=
erif;font-size:12.666666984558105px">
<span style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:12=
.666666984558105px">=A0 =A0// numbers representing longitude and latitude.<=
/span><br style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-siz=
e:12.666666984558105px">
<span style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size:12=
.666666984558105px">=A0 =A0// e.g. &quot;location&quot;: &quot;0.0,51.5&quo=
t;</span><br></div><div><br></div><div>But this is not using JSON encoding =
at all, it is a string with two decimal fractions separated by a coma. The =
JSON encoding would be:</div>
<div><br></div><div><span style=3D"font-family:arial,sans-serif;font-size:1=
2.666666984558105px">&quot;location&quot; : {&quot;X&quot;:0.0,&quot;Y&quot=
;:51.5}</span><br></div><div><span style=3D"font-family:arial,sans-serif;fo=
nt-size:12.666666984558105px"><br>
</span></div><div><span style=3D"font-family:arial,sans-serif;font-size:12.=
666666984558105px">The justification for the microformat is of course bytes=
having. And of course the example being artificial is unrepresentative. In =
the normal case the comparison would be=A0</span></div>
<div><span style=3D"font-family:arial,sans-serif;font-size:12.6666669845581=
05px"><br></span></div><div><span style=3D"color:rgb(80,0,80);font-family:a=
rial,sans-serif;font-size:12.666666984558105px">&quot;210.012345,51.52232&q=
uot; vs {&quot;X&quot; :=A0</span><span style=3D"color:rgb(80,0,80);font-fa=
mily:arial,sans-serif;font-size:12.666666984558105px">210.012345,&quot;Y&qu=
ot; : 51.52232}</span><span style=3D"color:rgb(80,0,80);font-family:arial,s=
ans-serif;font-size:12.666666984558105px">=A0</span><span style=3D"font-fam=
ily:arial,sans-serif;font-size:12.666666984558105px"><br>
</span></div><div><br></div><div>The difference is 3 control bytes versus 9=
 for the tagged version. Which isn&#39;t actually a lot of overhead for a t=
agged text format.</div><div><br></div><div><br></div><div>But imagine we h=
ave an efficient binary encoding that can represent those numbers in 5 byte=
s rather than 10. The efficient binary encoding is much more efficient than=
 the handcoded binary.</div>
<div><br></div><div>Having a compact binary notation about provides a tool =
that can be swung when someone is messing about with a microformat that is =
only going to cause grief. If a specification is using JSON encoding then i=
t should use JSON encoding, not JSON plus a bunch of poorly thought out ad =
hoc hacks that seemed like a good idea at the time.</div>
<div><br></div><div>When people reach for regular expressions I reach for t=
he sick bag.</div><div><br></div><div>Regular expressions are a very powerf=
ul tool that can be used to create more complexity in fewer lines of code t=
han any other language I know (including APL). They are like using GOTOs. E=
very non-trivial program without exception has GOTO statements but in a str=
uctured programing language the programmer does not code them directly or n=
eed to.</div>
<div><br></div><div>So one of the challenges in using XML or JSON or any ot=
her regular data encoding in a standards effort is to block attempts to sne=
ak in other encodings by way of &#39;microformats&#39; that always looks su=
ch a good idea till they have to be coded.</div>
<div><br></div><div><br></div><div>Having a binary encoding for the data en=
coding at hand allows the microformats to the swatted away. Doing better th=
an a text encoding is pretty easy. Doing better than a well designed binary=
 encoding is actually hard.</div>
<div><br></div><div><br></div></div>-- <br>Website: <a href=3D"http://halla=
mbaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a113470d2a3bf7504f2d8527d--


From nobody Thu Feb 20 08:01:42 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 F186A1A05F2 for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 12:36:48 -0800 (PST)
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 wrejYyEwnPTD for <ietf@ietfa.amsl.com>; Wed, 19 Feb 2014 12:36:47 -0800 (PST)
Received: from mail.painless-security.com (mail.painless-security.com [23.30.188.241]) by ietfa.amsl.com (Postfix) with ESMTP id 4E12B1A05FB for <ietf@ietf.org>; Wed, 19 Feb 2014 12:36:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.painless-security.com (Postfix) with ESMTP id 7DD4C20685; Wed, 19 Feb 2014 15:32:47 -0500 (EST)
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 qPNuz8AX41m5; Wed, 19 Feb 2014 15:32:47 -0500 (EST)
Received: from carter-zimmerman.suchdamage.org (unknown [10.1.10.106]) (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, 19 Feb 2014 15:32:47 -0500 (EST)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id AB9AF83EF7; Wed, 19 Feb 2014 15:36:41 -0500 (EST)
From: Sam Hartman <hartmans-ietf@mit.edu>
To: Barry Leiba <barryleiba@computer.org>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com>
Date: Wed, 19 Feb 2014 15:36:41 -0500
In-Reply-To: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> (Barry Leiba's message of "Tue, 18 Feb 2014 17:49:37 -0500")
Message-ID: <tsld2ii3kme.fsf@mit.edu>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Fb1-gka6WWGTAM7Tf2vRKZg8Ox0
X-Mailman-Approved-At: Thu, 20 Feb 2014 08:01:38 -0800
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, 19 Feb 2014 20:36:49 -0000

As a matter of process, I'm confused about the handling of this appeal.
It sounds like Phil appealed the approval of RFC 7049.

That, I hope, was a decision made by the IESG, not a decision made by
one AD.
So, I'm failing to understand how it makes sense for you to respond to
this appeal as an AD.


From nobody Thu Feb 20 10:27:26 2014
Return-Path: <barryleiba@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 6BD8C1A01B6 for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 10:27:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level: 
X-Spam-Status: No, score=-1.278 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, 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 zxal5p4n9Jcu for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 10:27:23 -0800 (PST)
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 D32F81A0047 for <ietf@ietf.org>; Thu, 20 Feb 2014 10:27:22 -0800 (PST)
Received: by mail-qa0-f50.google.com with SMTP id cm18so3317961qab.37 for <ietf@ietf.org>; Thu, 20 Feb 2014 10:27:19 -0800 (PST)
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:content-type; bh=FET4CSvcYBXCgA6nGVfngc10kbv4RWbojkQ/fHygegE=; b=k2ywh6jMkujmPsFYw0AQdUg/dGvIk+ZB/S3SgwoVz1ZK/3FfcURL3nY5W9FLjqrqSa cwj2nxL/o9anCaMGfj6ZmddtoJMA0wg9OcAxaSdLCOsw8xhwIeLapkKz2Jq1v030jQry vIUtJNMN5L/pIH6Q2CTR7XeuAcTdp4RJXsuOR3gtxDgJSjdM4Gahx2hgzLh+j2Se1yaB wqeQqFOOw2moWZiqGeHKNG0pOXaGpigi0CkBDiv/L+pdOAD4pJiCuxlxOxpTyZCmQY1X BVZjGQyW+PfsQOIgWgT1Reuvn5I5Ebhk/72q7mBBXqqHHpkrzlHJaTSWnp0xL+c8eaAS UXbA==
MIME-Version: 1.0
X-Received: by 10.140.23.52 with SMTP id 49mr3493788qgo.17.1392920839058; Thu, 20 Feb 2014 10:27:19 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.224.26.11 with HTTP; Thu, 20 Feb 2014 10:27:18 -0800 (PST)
In-Reply-To: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com>
Date: Thu, 20 Feb 2014 13:27:18 -0500
X-Google-Sender-Auth: Hv4ZGN_GZCNPxFr5ZqjAhRjLEMo
Message-ID: <CALaySJLPSNj_io8KeBEpPD8rxhzJi9feJkGL2FLwKnEgQ7f_8Q@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Barry Leiba <barryleiba@computer.org>
To: IETF discussion list <ietf@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mHWL-f9dtRJ8B-PzjvKEqaLsUiA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Feb 2014 18:27:24 -0000

I appreciate people's concerns about how this was handled; let me
explain my view of it a bit more.

In his complaint, Phill re-raised an issue he had raised during last
call (and during earlier discussion).  That all happened well before
the IESG got the document.  I interpreted his complaint, then, as
questioning the decisions I made, rather than the publication decision
that the IESG made.

Now, how to handle that:
RFC 2026 Section 6.5.1 covers complaints about working group issues,
but says nothing about handling non-working group, AD-sponsored stuff.
 I decided that the right path was to go back to basic principles:

1. 2026 does seem to guide us to start all complaints with a review by
the person or body that made the decision, a "please reconsider"
request.

2. We should treat all complaints seriously, and make an honest effort
to understand the complaint and address it fairly.

I believe we did both of those, and that handling this, at the first
level, as a complaint about a decision I made (I accepted the document
for AD sponsorship without having been diligent enoughin my
consideration, or I made a judgment about consensus during last call
without having adequately considered the issues Phill raised... you
pick; they amount to the same thing).  For timing, I considered the
IESG approval announcement as when the clock started, because that was
when it became publicly clear that Phill's concern was not going to be
further addressed.

It's perhaps a valid interpretation that this should have been handled
purely as a process appeal, only involving RFC 2026 Section 6.5.2.
For the reasons above, I didn't, and don't interpret it that way.

What do we call this?  Is it an "appeal"?  Well, 2026 doesn't use the
word "appeal" until the "disagreement" (the word 2026 uses) is taken
to the full IESG.  I think that's a distinction with no substance.
Phill wanted his issue addressed, and *he* called it an appeal.  I'm
happy to call it an appeal as well, and see no value in quibbling
about how we refer to it.  In any case, he was asking us to reconsider
a decision.  He was asked to start that by coming to me.  He did, and
I did.  I think that was right, and not in any way "odd".

By handling it this way, we also have not closed off any other
avenues.  Appeal to the IESG is still an open option -- clearly, I
think it's not the best way at this point, and I appreciate that Phill
is willing to accept my response.

What's said in the plenary is up to Jari, but I certainly encourage
him to list this complaint in the plenary, to call it an appeal and to
summarise my response to it.

Now: can we let this discussion settle down?  We had a complaint from
a participant that was taken seriously.  The decision it involved was
reconsidered and responded to.

(And let's please move technical discussion about binary encodings to
another subject thread.)

Thanks, everyone.
Barry


From nobody Thu Feb 20 11:40: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 4656D1A01D7; Thu, 20 Feb 2014 11:40:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, 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 pekzlamHwoNw; Thu, 20 Feb 2014 11:40:24 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 50F081A0176; Thu, 20 Feb 2014 11:40:24 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.147.147]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1KJdwSn003627 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 20 Feb 2014 11:40:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392925212; bh=6t8u+CRuujADO2GQTWbF+ZIMQdxtPSJIRriQDuaAcm4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=UbTFlpL9dFP5Sm+AagGCXjjx6YrpZzqXfLZMK0D6XnJsli8Z42big4zWLiVmotlM7 HRao4M4i6EPdwVqP2qq7jMZYWjQLHLK2tKHpw4Xc6yey7UlGEfyyywksn5MNWH6eiS 1vXZxJjoGn2LTbdLFFUOsrRvgb+ObRQhUoxaNtK4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1392925212; i=@elandsys.com; bh=6t8u+CRuujADO2GQTWbF+ZIMQdxtPSJIRriQDuaAcm4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=rbjJ+FwimonRYi2dB4OuzoctoK5Z6f7sOPWx+C7IL5/hD9uYiQmnpsIXe/3ViLpTn HHRI25fVM+YweMdZOybOMqyyKK+n6Ee+iC7LoNKt2d3A1JXPxcsBrxMKHdDhKOcLZz dUAAx4bAqga1wg2nTlmx5mSU3QF7o0dMkNp85n8o=
Message-Id: <6.2.5.6.2.20140220104653.0cd98288@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 20 Feb 2014 11:30:39 -0800
To: iesg@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
In-Reply-To: <A9AB0AA4-7229-4F43-B7D8-75599E2F8F49@gmail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <A9AB0AA4-7229-4F43-B7D8-75599E2F8F49@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WojYh6lTjV-5t0nhPLSwGUkRZTg
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, 20 Feb 2014 19:40:27 -0000

Dear IESG,
At 06:11 20-02-2014, Ralph Droms wrote:
>My concern is that we not establish some de facto extension to our 
>processes by labeling this particular example of complaint 
>resolution as a formal appeal.

I share the concern that the IESG will establish the case at 
http://www.ietf.org/mail-archive/web/ietf/current/msg86168.html as a 
extension to the processes if it is labelled as a formal appeal.

There was the following comment from Hadriel Kaplan during the Last 
Call ( http://www.ietf.org/mail-archive/web/ietf/current/msg81414.html ):

   "I think publishing it as Proposed Standard would be ok if there
    wasn't strong disagreement, but it appears there is strong
    disagreement, including on how it came to be."

It was clear to the IESG that there appeared to be strong 
disagreement.  I'll highlight the following from Section 6.5.2 of RFC 2026:

   "The IESG is the principal agent of the IETF for this purpose, and it
   is the IESG that is charged with ensuring that the required procedures
   have been followed, and that any necessary prerequisites to a standards
   action have been met."

I have the following question:

      Is it the responsibility of the IESG to respond to an appeal 
about a process
      issue once a draft has gone through an IETF Last Call?

Regards,
S. Moonesamy 


From nobody Thu Feb 20 12:56: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 499F61A0279 for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 12:56:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vi1uTHZxFAgU for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 12:56:45 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 887A41A0167 for <ietf@ietf.org>; Thu, 20 Feb 2014 12:56:44 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 7B1E42CEC5; Thu, 20 Feb 2014 22:56:40 +0200 (EET)
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 AzqZgX7EOPGk; Thu, 20 Feb 2014 22:56:38 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 531B02CEB1; Thu, 20 Feb 2014 22:56:38 +0200 (EET)
From: Jari Arkko <jari.arkko@piuha.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: anti-harassment procedures
Date: Thu, 20 Feb 2014 21:56:38 +0100
Message-Id: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net>
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rATUCXbSq2X-Kf1L483Sd-QInrM
Cc: "adrian@olddog.co.uk Farrel" <adrian@olddog.co.uk>, 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: Thu, 20 Feb 2014 20:56:49 -0000

The IESG Statement concerning an Anti-Harassment Policy =
(http://www.ietf.org//iesg/statement/ietf-anti-harassment-policy.html) =
gave the general outline of the kinds of behaviors that were not =
acceptable, and stated that we would have an ombudsperson to handle =
complaints. The specific procedures were left open.=20

I asked Pete Resnick and Adrian Farrel to draft a procedures document, =
with the intent that it eventually could become a BCP. They have got =
something now that I think has enough structure for the wider community =
to discuss. Thank you, Pete and Adrian! Nevertheless, this is just a =
drafty "pre-00" proposal, with the specifics still open for discussion, =
but it seems to me the right general direction. I'm sending it here on =
this e-mail, and it will be posted as a draft when the submissions open =
again.

A couple of points before people start discussing it:

- The IESG has seen this, but by no means has agreement on the points. =
They have only agreed that it is a reasonable starting point for =
discussion.

- This is obviously not a technical specification. There will be a lot =
of variables for each situation and we will have rely on the good =
training and judgment of the Ombudsperson to handle things on a =
case-by-case basis. Trying to over-specify everything is unlikely to be =
useful.

- This can be a sensitive topic and a difficult discussion to have on an =
open list like the IETF list. Please try to keep that in mind as you =
make or respond to comments. If you would prefer to send your comments =
instead to the IESG, or directly to me, that is fine. In the end, I'll =
summarize those comments for the list and make sure they get addressed, =
just like other comments made to the list.

I know this topic is hard to discuss. Hopefully there are very few =
situations where these procedures are needed, but they are needed. I =
thank you for your help and respectful input into this difficult but =
important discussion.

Jari

                    IETF Anti-Harassment Procedures
                   draft-farrresnickel-harassment-00

Abstract

   IETF participants must not engage in harassment while at IETF
   meetings, virtual meetings, social events, or on mailing lists.  This
   document lays out procedures for managing and enforcing this policy.

   This initial version is provided as a starting point for discussion
   and does not represent the firm opinions of the authors.
   Furthermore, the ideas presented in this document have not been fully
   discussed and reviewed by the IESG.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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 August 24, 2014.

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The Ombudsperson  . . . . . . . . . . . . . . . . . . . . . .   3
     3.1.  Appointing the Ombudsperson . . . . . . . . . . . . . . .   4
     3.2.  Qualifications and Training . . . . . . . . . . . . . . .   4
     3.3.  Term of Service . . . . . . . . . . . . . . . . . . . . .   4
     3.4.  Recompense  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.5.  Removal . . . . . . . . . . . . . . . . . . . . . . . . .   5
     3.6.  Disputes with the IETF Chair regarding the Ombudsperson .   5
   4.  Handling Reports of Harassment  . . . . . . . . . . . . . . .   5
   5.  Remedies  . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   6.  Disputes with the Ombudsperson  . . . . . . . . . . . . . . .   7
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   0
     8.2.  URIs  . . . . . . . . . . . . . . . . . . . . . . . . . .   8
   Appendix A.  Acknowledgements . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The IETF has general policies for managing disruptive behavior in the
   context of IETF activities.  In particular, [RFC3184] provides a set
   of guidelines for personal interaction in the IETF, and [RFC2418] and
   [RFC3934] give guidelines for how to deal with disruptive behavior
   that occurs in the context of IETF working group face-to-face
   meetings and on mailing lists.

   However, there is other problematic, often more interpersonal,
   behavior that can occur in the context of IETF activities (meetings,
   mailing list discussions, or social events) that does not directly
   disrupt working group progress, but nonetheless is unacceptable
   behavior between IETF participants.  This sort of behavior, described
   in the IESG Statement on an "IETF Anti-Harassment Policy" [1], is not
   easily dealt with by our normal working group guidelines and
   procedures.  Therefore, this document sets forth procedures to deal
   with such harassing behavior.  These procedures are intended to be
   used when other IETF policies and procedures do not apply or have
   been ineffective.

   Nothing in this document should be taken to interfere with the due
   process of law for the legal system under the jurisdiction of which
   any harassment takes place.

2.  Definitions

   The following terms are used in this document:

      Reporter: An IETF participant who reports potential harassment to
      the Ombudsperson.

      Respondent: An IETF participant who is claimed to have engaged in
      harassing behavior.

      Ombudsperson: The person who is selected to take reports of
      harassment, evaluate them, and impose appropriate actions and/or
      remedies to address the circumstance.  This word is used in the
      singular throughout this document although multiple ombudspersons
      might serve at any one time.

      Target: An individual IETF participant to whom the potentially
      harassing behavior was directed.

   This document does not attempt to precisely define behavior that
   falls under the set of procedures identified here.  In general,
   disruptive behavior that occurs in the context of an IETF general or
   working group mailing list, or happens in a face-to-face or virtual
   meeting of a working group or the IETF plenary, can be dealt with by
   our normal procedures, whereas harassing behavior that is
   interpersonal is more easily handled by the procedures described
   here.  However, there are certainly plausible reasons to address
   behaviors that take place during working-group meetings using these
   procedures.  This document gives some guidance to those involved in
   these situations in order to decide how to handle particular
   incidents, but in the end the final decision will involve judgment
   and the guidance of the Ombudsperson.

3.  The Ombudsperson

   This section describes the role of the Ombudsperson in terms of their
   appointment, qualifications and training, the length of the term of
   service, any recompense for their service, and how they may be
   removed from service.  The general operational procedures for the
   Ombudsperson are described in Section 4, Section 5, and Section 6.

3.1.  Appointing the Ombudsperson

   The Ombudsperson is appointed by the IETF Chair.  The appointment is
   solely the responsibility of the IETF Chair although the Chair may
   choose to consult with the IESG, the IAB, and with ISOC.
   Furthermore, the IETF Chair may take opinion from the community.

   The IETF Chair may choose to solicit nominations or advertise the
   post.  This is entirely at the discretion of the IETF Chair.

   The IETF Chair is also free to decide how many people are needed to
   fill the role of Ombudsperson.  This may depend on the skillsets
   available, the work load, and the opinions of the seated
   Ombudsperson.  Furthermore, the IETF Chair may consider elements of
   diversity in making this decision.

3.2.  Qualifications and Training

   It is not expected that there will be candidates with all of the
   necessary ombudsperson skills and training who also have a clear
   understanding and familiarity with the IETF processes and culture.
   The Chair might choose someone with a great deal of professional
   experience evaluating and mediating harassment disputes, but little
   exposure to the IETF, or could select someone with more exposure to
   the IETF community, but without as much experience dealing with
   issues of harassment.  Since all of these attributes may be regarded
   by the IETF Chair as essential for an appointment, the IETF is
   committed to provide funding for necessary training for an appointed
   Ombudsperson.

3.3.  Term of Service

   An Ombudsperson shall be appointed for a two year term.  That is, the
   Ombudsperson is making a commitment to serve for two years.  It is
   understood, however, that circumstances may lead an Ombudsperson to
   resign for personal or other reasons.  See also Section 3.5.

   It is entirely at the discretion of the IETF Chair whether a serving
   Ombudsperson is reappointed at the end of their term.

3.4.  Recompense

   An Ombudsperson shall receive no recompense for their services.  This
   includes, but is not limited to:

      IETF meeting fees

      Remuneration for time spent

      Out-of-pocket expenses (such as telephone charges)

      Travel or accommodation expenses

   The IETF will, however, meet the costs of training when agreed to by
   the IETF Chair as described in Section 3.2.

3.5.  Removal

   The IETF Chair may remove a serving Ombudsperson before the end of
   their term without explanation to the community.  Such an action
   shall not be appealable.  See also Section 6.

3.6.  Disputes with the IETF Chair regarding the Ombudsperson

   If an individual should disagree with an action taken by the IETF
   Chair regarding the appointment, removal, or management of the
   Ombudsperson, that person should first discuss the issue with the
   IESG Chair directly.  If the IESG Chair is unable to resolve the
   issue, the dissatisfied party may appeal to the IESG as a whole.  The
   IESG shall then review the situation and attempt to resolve it in a
   manner of its own choosing.  The procedures of Section 6.5.4 of
   [RFC2026] apply to this sort of appeal.

4.  Handling Reports of Harassment

   Any IETF participant who believes that they or other IETF
   participants have been harassed or may have been harassed may bring
   the concern to the attention of the Ombudsperson.  This can be done
   by email to "ombudsperson@ietf.org" [2], or can be done directly to
   the Ombudsperson.  Direct contact information for the Ombudsperson,
   including the email addresses to which "ombudsperson@ietf.org" is
   forwarded, can be found at https://www.ietf.org/ombudsperson .

   The Ombudsperson is expected to be present at the majority of IETF
   meetings and to be available for face-to-face discussions.

   All information brought to the Ombudsperson shall be kept in strict
   confidence.  Any electronic information (such as email messages) that
   needs to be archived shall be encrypted before it is stored.

   When a Reporter brings an incident of potential harassment to the
   Ombudsperson's attention to, the Ombudsperson will discuss the events
   with the Reporter and may give advice including recommendations on
   how the Reporter can handle the issue on their own and strategies on
   how to prevent the issue from arising again.  The Ombudsperson may
   also indicate that the issue would be best handled using regular IETF
   procedures (such as those for dealing with disruptive behavior)
   outside the context of harassment, and in this case the Ombudsperson
   will provide assistance in using the relevant IETF procedures.  In
   any event, the Ombudsperson will not initiate detailed investigations
   or impose a remedy without agreement to proceed from the Target (or
   the Reporter if there is no individual Target).

   When conducting a detailed investigation of the circumstances
   regarding the complaint of harassment, the Ombudsperson may contact
   the Respondent and request a meeting in person or by a voice call.
   The Respondent is not obliged to cooperate, but the Ombudsperson may
   consider failure to cooperate when determining a remedy (Section 5).

   In all cases the Ombudsperson will strive to maintain confidentiality
   for all parties including the very fact of contact with the
   Ombudsperson.

5.  Remedies

   After examining the circumstances regarding the complaint of
   harassment and determining that harassment has taken place, the
   Ombudsperson is expected to choose a remedy that is appropriate to
   the circumstance.  At one end of the spectrum, the Ombudsperson may
   decide that the misbehavior is best handled with the regular IETF
   procedures for dealing with disruptive behavior and may assist the
   Reporter to bring the issue to the attention of the working group
   chair or IESG member who can deal with the incident.  The
   Ombudsperson might also choose simply to discuss the situation with
   the Respondent and come up with a plan such that there is no repeat
   of the harassment.  With the agreement of both parties, the
   Ombudsperson can also help to mediate a conversation between the
   Respondent and the Target (or the Reporter if there is no individual
   Target) in order to address the issue.  Finally, on the other end of
   the spectrum, the Ombudsperson could decide that the Respondent is no
   longer permitted to participate in a particular IETF activity,
   whether it is a mailing list discussion, virtual meeting, or a face-
   to-face activity, up to and including requiring that the Respondent
   can no longer attend a face-to-face IETF meeting and its associated
   activities, either for the remainder of the present meeting or (in
   the extreme) future meetings.

   In determining the appropriate remedy, the Ombudsperson may
   communicate with the Reporter, Target, and Respondent in order to
   assess the impact that the imposition of a remedy might have on any
   of those parties.  However, the Ombudsperson has ultimate
   responsibility for the choice of remedy.

   In all cases, the Ombudsperson informs the Respondent of the decision
   and imposes the remedy as appropriate.  In cases where the remedy is
   removal from IETF activities, the Ombudsperson will confidentially
   notify the Secretariat of the remedy such that the Secretariat can
   take whatever logistical actions are required to effect the remedy.
   Only the remedy itself shall be disclosed to the Secretariat, not any
   information regarding the nature of the harassment.

6.  Disputes with the Ombudsperson

   If either the Target (or the Reporter if there is no individual
   Target) or the Respondent is dissatisfied with the decision of the
   Ombudsperson, the dissatisfied party should first contact the
   Ombudsperson and discuss the situation.  If the issue cannot be
   resolved through discussion with the Ombudsperson, the issue may be
   raised with the IETF Chair.

   If necessary, the IETF Chair may recuse themself from any part of
   this process and delegate to another member of the IESG.

   The IETF Chair will attempt to resolve the issue in discussion with
   the dissatisfied party and the Ombudsperson.  If this further
   discussion does not bring a satisfactory resolution, the
   Ombudsperson's decision may be formally appealed.  The appeal is
   strictly on the issue of whether the Ombudsperson exercised due
   diligence in both their decision as to whether harassment had taken
   place, as well as in their determination of any appropriate remedy
   that was imposed.  In particular, the purpose of the appeal is not to
   re-investigate the circumstances of the incident.

   All elements of the appeal, including the fact of the appeal, will be
   held in confidence, but will be recorded and held securely for future
   reference.

   The appeal will be evaluated by the IETF Chair and two other members
   of the IESG, selected by the IETF Chair and confirmed by the
   appellant.  This Appeals Group shall convene as quickly as possible
   to evaluate and decide the appeal.  Where the impacts are immediate
   and related to participation in an ongoing meeting, this shall happen
   in no more than 24 hours after receiving the appeal.  The Appeals
   Group may ask the appellant and the Ombudsperson for statements or
   other information to consider.  If the Appeals Group concludes that
   due diligence was exercised by the Ombudsperson, this shall be
   reported to the appellant and the matter is concluded.  If they find
   that due diligence was not exercised, the Appeals Group shall report
   this to the Ombudsperson, and consult with the Ombudsperson on how to
   complete the due diligence.

   Because of the need to keep the information regarding these matters
   as confidential as possible, the Appeals Group's decision is final
   with respect to the question of whether the Ombudsperson has used due
   diligence in their decision.  The only further recourse available is
   to claim that the procedures themselves (i.e., the procedures
   described in this document) are inadequate or insufficient to the
   protection of the rights of all parties.  Such appeals may be made to
   the Internet Society Board of Trustees, as described in Section 6.5.3
   of [RFC2026].  Again, even in this circumstance, the particulars of
   the incident at hand will be held in confidence.

      Note: The authors of this draft chose to use the IETF Chair and
      two IESG members as the Appeals Group.  Though not completely
      arbitrary, there are certainly other plausible choices.  The
      authors also recognize that this is a different sort of appeals
      procedure than normal.  However, the normal appeals procedure
      contemplates an openness about the process that the
      confidentiality issues in these cases simply do not allow.

7.  Security Considerations

   "Human beings the world over need freedom and security that they may
   be able to realize their full potential." -- Aung San Suu Kyi

8.  References

   [RFC2026]  Bradner, S., "The Internet Standards Process -- Revision
              3", BCP 9, RFC 2026, October 1996.

   [RFC2418]  Bradner, S., "IETF Working Group Guidelines and
              Procedures", BCP 25, RFC 2418, September 1998.

   [RFC3184]  Harris, S., "IETF Guidelines for Conduct", BCP 54, RFC
              3184, October 2001.

   [RFC3934]  Wasserman, M., "Updates to RFC 2418 Regarding the
              Management of IETF Mailing Lists", BCP 25, RFC 3934,
              October 2004.

8.2.  URIs

   [1] http://www.ietf.org/iesg/statement/ietf-anti-harassment-
       policy.html

   [2] mailto:ombudsperson@ietf.org

Appendix A.  Acknowledgements

Authors' Addresses

   Pete Resnick
   Qualcomm Technologies, Inc.
   5775 Morehouse Drive
   San Diego, CA  92121
   US

   Phone: +1 858 6511 4478
   Email: presnick@qti.qualcomm.com


   Adrian Farrel
   Juniper Networks

   Email: adrian@olddog.co.uk



From nobody Thu Feb 20 13:08:35 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 3A1F31A02DD; Thu, 20 Feb 2014 13:08:29 -0800 (PST)
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 CvdXzmigJ82o; Thu, 20 Feb 2014 13:08:23 -0800 (PST)
Received: from mail-la0-x233.google.com (mail-la0-x233.google.com [IPv6:2a00:1450:4010:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id AE23B1A0290; Thu, 20 Feb 2014 13:08:22 -0800 (PST)
Received: by mail-la0-f51.google.com with SMTP id c6so1709849lan.38 for <multiple recipients>; Thu, 20 Feb 2014 13:08:18 -0800 (PST)
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=Wn/SHXEW1+KLZvyD3c4UWslHFXiMpJ5D+ga/uQU+VkM=; b=aAsmClAV7VuMqzrDh/rkYmE2KNSDiAqF+hIZk6zrS83tFmx+743BGlLexBO8/vLJH4 X6BovwRkyuM8tV8dLa4tc5olSmFJzim+RRiVgYYC9MINxY8B8o78/v5Vo6XlI/Zs9FBv PSEGErfKJg1PSEM7bPZ9Blsz8MMODFuO1jbK+YJw/ZK8byQDbHKE/LG+dePCwkcL6G9h UPgBJT67ATBU+KOxDLtiXlyZh61jn7FDpBnmIyTxpFC00YEhc8kYrNNFQ/MO+I95vjKK v55i8gysAqo878WcvO7K5FGJ8aT9P94EMNsG0mBfc5V2XuwIA69Ll8pMGh1M71qUh4Mj eA9A==
MIME-Version: 1.0
X-Received: by 10.153.9.97 with SMTP id dr1mr2274640lad.45.1392930498168; Thu, 20 Feb 2014 13:08:18 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Thu, 20 Feb 2014 13:08:17 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140220104653.0cd98288@resistor.net>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <A9AB0AA4-7229-4F43-B7D8-75599E2F8F49@gmail.com> <6.2.5.6.2.20140220104653.0cd98288@resistor.net>
Date: Thu, 20 Feb 2014 16:08:17 -0500
Message-ID: <CAMm+LwiojSW-gMOS6hzScKGtFrAz34ObFGcBRcs2a6tiZPkoSg@mail.gmail.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
From: Phillip Hallam-Baker <hallam@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=001a11381b4e8a4c9a04f2dce722
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bds_0uWb0kLZx36oH24z_1lbseI
Cc: IETF Discussion Mailing List <ietf@ietf.org>, "iesg@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: Thu, 20 Feb 2014 21:08:29 -0000

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

It may have been clear to the IESG that there was disagreement. That is not
a barrier to adoption of a specification.

What is a barrier is when the disagreement comes from a statement from the
original proposers of the project that they are not interested in
addressing a set of requirements that are normally considered for a
proposal of that type and that they will ignore all attempts to raise those
requirements or proposals to meet them regardless of the merits.

It was not clear to the IESG that this was the case because it was not
clear to the AD that it was the case.

The IETF has a long tradition of publishing closed development efforts as
RFCs. But those RFCs are expected to be INFORMATIONAL. Had the AD and IESG
been aware of the nature of the consensus backing CBOR it is unlikely that
it would have agreed on PROPOSED STANDARD.


An appeal was raised. If you think that the process has to be followed or
bad things will result then you should insist that the IESG address the
matter in an official capacity to avoid the setting of the precedent you
want to avoid.


I find it rather interesting that there has been more concern about the
correct way to handle the non-handling of the appeal than there ever was
about the rather minor changes to the specification I proposed that could
have avoided the need for process questions at all.

I also find it rather interesting that people who don't have a need to
efficiently transport binary blobs of data about are so committed to making
it difficult for me to do that with a specification that is as close to
JSON as possible. If I have a 1Gb video file that I want to shove down a
pipe, I certainly don't want to add another 333MB of overhead just to use
JSON. Nor do I want to have a protocol that requires me to deal with two
different data models, two different encoders and two different parsers
when I can meet the exact same need by adding tags to JSON to give me a
length bounded chunk encoding.

Such an encoding is not JSON but it is close enough to JSON that I can use
one set of tools to encode/decode both formats. That is not true if I use
the JSON subset of CBOR.



On Thu, Feb 20, 2014 at 2:30 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Dear IESG,
>
> At 06:11 20-02-2014, Ralph Droms wrote:
>
>> My concern is that we not establish some de facto extension to our
>> processes by labeling this particular example of complaint resolution as a
>> formal appeal.
>>
>
> I share the concern that the IESG will establish the case at
> http://www.ietf.org/mail-archive/web/ietf/current/msg86168.html as a
> extension to the processes if it is labelled as a formal appeal.
>
> There was the following comment from Hadriel Kaplan during the Last Call (
> http://www.ietf.org/mail-archive/web/ietf/current/msg81414.html ):
>
>   "I think publishing it as Proposed Standard would be ok if there
>    wasn't strong disagreement, but it appears there is strong
>    disagreement, including on how it came to be."
>
> It was clear to the IESG that there appeared to be strong disagreement.
>  I'll highlight the following from Section 6.5.2 of RFC 2026:
>
>   "The IESG is the principal agent of the IETF for this purpose, and it
>   is the IESG that is charged with ensuring that the required procedures
>   have been followed, and that any necessary prerequisites to a standards
>   action have been met."
>
> I have the following question:
>
>      Is it the responsibility of the IESG to respond to an appeal about a
> process
>      issue once a draft has gone through an IETF Last Call?
>
> Regards,
> S. Moonesamy
>



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

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

<div dir=3D"ltr">It may have been clear to the IESG that there was disagree=
ment. That is not a barrier to adoption of a specification.<div><br></div><=
div>What is a barrier is when the disagreement comes from a statement from =
the original proposers of the project that they are not interested in addre=
ssing a set of requirements that are normally considered for a proposal of =
that type and that they will ignore all attempts to raise those requirement=
s or proposals to meet them regardless of the merits.</div>
<div><br></div><div>It was not clear to the IESG that this was the case bec=
ause it was not clear to the AD that it was the case.</div><div><br></div><=
div>The IETF has a long tradition of publishing closed development efforts =
as RFCs. But those RFCs are expected to be INFORMATIONAL. Had the AD and IE=
SG been aware of the nature of the consensus backing CBOR it is unlikely th=
at it would have agreed on PROPOSED STANDARD.</div>
<div><br></div><div><br></div><div>An appeal was raised. If you think that =
the process has to be followed or bad things will result then you should in=
sist that the IESG address the matter in an official capacity to avoid the =
setting of the precedent you want to avoid.</div>
<div><br></div><div><br></div><div>I find it rather interesting that there =
has been more concern about the correct way to handle the non-handling of t=
he appeal than there ever was about the rather minor changes to the specifi=
cation I proposed that could have avoided the need for process questions at=
 all.</div>
<div><br></div><div>I also find it rather interesting that people who don&#=
39;t have a need to efficiently transport binary blobs of data about are so=
 committed to making it difficult for me to do that with a specification th=
at is as close to JSON as possible. If I have a 1Gb video file that I want =
to shove down a pipe, I certainly don&#39;t want to add another 333MB of ov=
erhead just to use JSON. Nor do I want to have a protocol that requires me =
to deal with two different data models, two different encoders and two diff=
erent parsers when I can meet the exact same need by adding tags to JSON to=
 give me a length bounded chunk encoding.</div>
<div><br></div><div>Such an encoding is not JSON but it is close enough to =
JSON that I can use one set of tools to encode/decode both formats. That is=
 not true if I use the JSON subset of CBOR.</div><div><br></div></div><div =
class=3D"gmail_extra">
<br><br><div class=3D"gmail_quote">On Thu, Feb 20, 2014 at 2:30 PM, S Moone=
samy <span dir=3D"ltr">&lt;<a href=3D"mailto:sm+ietf@elandsys.com" target=
=3D"_blank">sm+ietf@elandsys.com</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">
Dear IESG,<div class=3D""><br>
At 06:11 20-02-2014, Ralph Droms wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
My concern is that we not establish some de facto extension to our processe=
s by labeling this particular example of complaint resolution as a formal a=
ppeal.<br>
</blockquote>
<br></div>
I share the concern that the IESG will establish the case at <a href=3D"htt=
p://www.ietf.org/mail-archive/web/ietf/current/msg86168.html" target=3D"_bl=
ank">http://www.ietf.org/mail-<u></u>archive/web/ietf/current/<u></u>msg861=
68.html</a> as a extension to the processes if it is labelled as a formal a=
ppeal.<br>

<br>
There was the following comment from Hadriel Kaplan during the Last Call ( =
<a href=3D"http://www.ietf.org/mail-archive/web/ietf/current/msg81414.html"=
 target=3D"_blank">http://www.ietf.org/mail-<u></u>archive/web/ietf/current=
/<u></u>msg81414.html</a> ):<br>

<br>
=A0 &quot;I think publishing it as Proposed Standard would be ok if there<b=
r>
=A0 =A0wasn&#39;t strong disagreement, but it appears there is strong<br>
=A0 =A0disagreement, including on how it came to be.&quot;<br>
<br>
It was clear to the IESG that there appeared to be strong disagreement. =A0=
I&#39;ll highlight the following from Section 6.5.2 of RFC 2026:<br>
<br>
=A0 &quot;The IESG is the principal agent of the IETF for this purpose, and=
 it<br>
=A0 is the IESG that is charged with ensuring that the required procedures<=
br>
=A0 have been followed, and that any necessary prerequisites to a standards=
<br>
=A0 action have been met.&quot;<br>
<br>
I have the following question:<br>
<br>
=A0 =A0 =A0Is it the responsibility of the IESG to respond to an appeal abo=
ut a process<br>
=A0 =A0 =A0issue once a draft has gone through an IETF Last Call?<br>
<br>
Regards,<br>
S. Moonesamy <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>

--001a11381b4e8a4c9a04f2dce722--


From nobody Thu Feb 20 13:22:42 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 F02141A02E6 for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 13:22:40 -0800 (PST)
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 GcyrkB-RFr0R for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 13:22:38 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.109]) by ietfa.amsl.com (Postfix) with ESMTP id A15441A0306 for <ietf@ietf.org>; Thu, 20 Feb 2014 13:22:37 -0800 (PST)
Received: from [193.109.255.147:12584] by server-5.bemta-14.messagelabs.com id 82/4C-16688-91276035; Thu, 20 Feb 2014 21:22:33 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-72.messagelabs.com!1392931352!10233835!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9549 invoked from network); 20 Feb 2014 21:22:33 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-2.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 20 Feb 2014 21:22:33 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Thu, 20 Feb 2014 21:22:32 +0000
From: <l.wood@surrey.ac.uk>
To: <jari.arkko@piuha.net>, <ietf@ietf.org>
Date: Thu, 20 Feb 2014 21:22:32 +0000
Subject: draft naming was RE: anti-harassment procedures
Thread-Topic: draft naming was RE: anti-harassment procedures
Thread-Index: AQHPLoHdwKCsJr6viEuY+XfWYYdQjw==
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net>
In-Reply-To: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.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/BRK7w_OHdj7yERrqNvBlX0r9Jwk
Cc: adrian@olddog.co.uk, 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: Thu, 20 Feb 2014 21:22:41 -0000

An annoying trend:

                   IETF Anti-Harassment Procedures
                   draft-farrresnickel-harassment-00

should have been farrel-resnick

             Opportunistic Encryption in MPLS Networks
          draft-farrelll-mpls-opportunistic-encrypt-00.txt

should have been farrel-farell

When trying to locate drafts by author name, or pick up on primary authors =
for indexing, or indicate drafts from memory, this cutesiness really doesn'=
t help. Cut it out, Adrian.

If you don't actually want your name on a draft (and the need for anonymous=
 draft submission seems as if it could be useful?) 'Smithee,' as used by fi=
lm directors, seems a reasonable thing to adopt.

Alan Smithee
http://en.wikipedia.org/wiki/Alan_Smithee=


From nobody Thu Feb 20 13:31:36 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 214C51A028B for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 13:31:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.217
X-Spam-Level: 
X-Spam-Status: No, score=0.217 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F_Iv2tXmRV7u for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 13:31:33 -0800 (PST)
Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id BB7861A0150 for <ietf@ietf.org>; Thu, 20 Feb 2014 13:31:32 -0800 (PST)
Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1KLVRZG021518; Thu, 20 Feb 2014 21:31:28 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1KLVO1R021477 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 20 Feb 2014 21:31:26 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <l.wood@surrey.ac.uk>, <jari.arkko@piuha.net>, <ietf@ietf.org>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk>
Subject: RE: draft naming was RE: anti-harassment procedures
Date: Thu, 20 Feb 2014 21:31:24 -0000
Message-ID: <01c101cf2e83$1d193b20$574bb160$@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: AQHrcwiwYYNfS7PwrYnCAE47s/QXoQJXuemsmnNhsLA=
Content-Language: en-gb
X-TM-AS-MML: No
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lsJOOSXE3hgUDueMQThBMCqbkGc
Cc: presnick@qti.qualcomm.com
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, 20 Feb 2014 21:31:35 -0000

Oh, whatever, Lloyd.

I use the datatracker to search for documents by author. A nice tool generally
available without subscription.

I also format document names roughly according to recommendations so that there
is only one nametag in the file name.

If this is the most significant thing I do wrong this year, I shall revel in it.

Adrian

> -----Original Message-----
> From: l.wood@surrey.ac.uk [mailto:l.wood@surrey.ac.uk]
> Sent: 20 February 2014 21:23
> To: jari.arkko@piuha.net; ietf@ietf.org
> Cc: adrian@olddog.co.uk; presnick@qti.qualcomm.com
> Subject: draft naming was RE: anti-harassment procedures
> 
> An annoying trend:
> 
>                    IETF Anti-Harassment Procedures
>                    draft-farrresnickel-harassment-00
> 
> should have been farrel-resnick
> 
>              Opportunistic Encryption in MPLS Networks
>           draft-farrelll-mpls-opportunistic-encrypt-00.txt
> 
> should have been farrel-farell
> 
> When trying to locate drafts by author name, or pick up on primary authors for
> indexing, or indicate drafts from memory, this cutesiness really doesn't help.
Cut
> it out, Adrian.
> 
> If you don't actually want your name on a draft (and the need for anonymous
> draft submission seems as if it could be useful?) 'Smithee,' as used by film
> directors, seems a reasonable thing to adopt.
> 
> Alan Smithee
> http://en.wikipedia.org/wiki/Alan_Smithee=


From nobody Thu Feb 20 15:17:48 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 B994A1A0340 for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 15:17:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.148
X-Spam-Level: 
X-Spam-Status: No, score=-3.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ibf2EKFlWTPU for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 15:17:38 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 8EF2C1A0304 for <ietf@ietf.org>; Thu, 20 Feb 2014 15:17:37 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WGcqO-0000NL-0d; Thu, 20 Feb 2014 18:15:52 -0500
Date: Thu, 20 Feb 2014 18:15:39 -0500
From: John C Klensin <john-ietf@jck.com>
To: l.wood@surrey.ac.uk, jari.arkko@piuha.net, ietf@ietf.org
Subject: Re: draft naming was RE: anti-harassment procedures
Message-ID: <D8A2F939F08761DEFEEA946E@JcK-HP8200.jck.com>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk>
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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/00GA4Gs5BKbTLnTH7s-fYqSUT2U
Cc: adrian@olddog.co.uk, 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: Thu, 20 Feb 2014 23:17:40 -0000

--On Thursday, February 20, 2014 21:22 +0000 l.wood@surrey.ac.uk
wrote:

> An annoying trend:
> 
>                    IETF Anti-Harassment Procedures
>                    draft-farrresnickel-harassment-00
> 
> should have been farrel-resnick
>...
> When trying to locate drafts by author name, or pick up on
> primary authors for indexing, or indicate drafts from memory,
> this cutesiness really doesn't help.

Actually, if we were following the historical and IMO very
useful rules, it would be either "draft-farrel-harassment..." or
"draft-resnick-harassment...".   The difficulty with adding
multiple author names becomes obvious as soon as there are three
or four authors.

I've often wished that the submission tool would check a table
for a small number of organizational tags (ietf, iab, etc.) and,
if the first string after "draft-" didn't appear there, check it
against the first author name.  It would be fairly easy to
verify that "draft-ietf-" was followed immediately by a
short-form WG name too.  If documents that didn't satisfy those
criteria went to manual posting and required an explanation to
the secretariat, I think the cutesiness would mostly stop in a
hurry.  If would also stop "draft-<made-up-organization>-..."
which, IMO, would be a real service to the community.

    john



From nobody Thu Feb 20 15:51:52 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 37F5E1A035A for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 15:51:51 -0800 (PST)
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 u08kZV_3cfiR for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 15:51:46 -0800 (PST)
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 29E4B1A02A1 for <ietf@ietf.org>; Thu, 20 Feb 2014 15:51:46 -0800 (PST)
Received: by mail-yk0-f174.google.com with SMTP id 20so3765320yks.5 for <ietf@ietf.org>; Thu, 20 Feb 2014 15:51:42 -0800 (PST)
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=FpNNTo8vtt0rPrMcFyHmQ6tU6sgAWmVhoGmC0P96+Ec=; b=SaAR1Sn6ArX19/SqWQdLjlmGeEAtJT3wWn3cr0jqwQqW3Tka5wCoBhRCOktBGSe4ca 6NSEvLs71Ef7L44wQftrd/n8Xun4tUNy5Di9oBe0XYpcNKtLF8LV4VqPOX3KwIKwETs3 tUqSVON1HaV8Q/dmdJdCmdvgO6PKPbeROnqv+WIovuUuIiUjffrclkVw7zs7Ta7L64li knNxsGjeU5IgFTYSy+NPj+xDDQtregjgTXJsIygTdL9dhLwQo3hemflHwf0Hc3cpvbKx sdFcs3g3gNxkaWeYFioULR6jlVpwTD4rdmY5OGKxuQFDFDSY99dLbHAkzYSjqsKD76hz aLOA==
MIME-Version: 1.0
X-Received: by 10.236.99.38 with SMTP id w26mr7211853yhf.18.1392940302325; Thu, 20 Feb 2014 15:51:42 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Thu, 20 Feb 2014 15:51:42 -0800 (PST)
In-Reply-To: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net>
Date: Fri, 21 Feb 2014 00:51:42 +0100
Message-ID: <CADnDZ88RjanJoFmA5po=QpUXExBCfD5ucWLcFTOMbZckGOpg2Q@mail.gmail.com>
Subject: Re: anti-harassment procedures
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf3011e027e9e12204f2df2f59
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ZWHJv8CbXbQDogKZTqHixw09Cqo
Cc: "adrian@olddog.co.uk Farrel" <adrian@olddog.co.uk>, 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: Thu, 20 Feb 2014 23:51:51 -0000

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

The draft has missing parts, because 1) the levels of harassing was not
defined, 2 ) it may also ignore the real practical society problems that
make harassing occur, 3) it gives a lot of power to IETF chair without
conditions or limits (may be the reason is to make it simple).  The draft
may assume that all ADs can not be part of harassing (not sure, draft is
unclear on this assumption). It should consider to be fair to all, and to
prevent sources of harassing not only solving when occurs. The below
comments are also initial comments.

2.  Definitions
>
>    The following terms are used in this document:
>
>       Reporter: An IETF participant who reports potential harassment to
>       the Ombudsperson.

Please amend to PH Reporter (Potential Harassment).

>
>       Respondent: An IETF participant who is claimed to have engaged in
>       harassing behavior.


This should explain his/her respond and to whom he/she responding to.


>
>       Ombudsperson: The person who is selected to take reports of
>       harassment, evaluate them, and impose appropriate actions and/or
>       remedies to address the circumstance.  This word is used in the
>       singular throughout this document although multiple ombudspersons
>       might serve at any one time.
>
>       Target: An individual IETF participant to whom the potentially
>       harassing behavior was directed.


Why only individual? Why not group of people or race or gender. The target
can be more than one,

Please amend; a group or an individual participant.

>
>    This document does not attempt to precisely define behavior that
>    falls under the set of procedures identified here.


That is good but IMHO still we need its limits defined.

However, you are missing another part of behaviour damage on the IETF
general behaviour.  So we need to define another target, which may be
named; possible future target.

Usually most harassing has two victims or target one is the main and the
other is not intended but affected, because it may become a possible future
target. Wise people avoid groups that has not reported harassing.


In general,
>    disruptive behavior that occurs in the context of an IETF general or
>    working group mailing list, or happens in a face-to-face or virtual
>    meeting of a working group or the IETF plenary, can be dealt with by
>    our normal procedures, whereas harassing behavior that is
>    interpersonal is more easily handled by the procedures described
>    here.  However, there are certainly plausible reasons to address
>    behaviors that take place during working-group meetings using these
>    procedures.  This document gives some guidance to those involved in
>    these situations in order to decide how to handle particular
>    incidents, but in the end the final decision will involve judgment
>    and the guidance of the Ombudsperson.
>
> 3.  The Ombudsperson
>
>    This section describes the role of the Ombudsperson in terms of their
>    appointment, qualifications and training, the length of the term of
>    service, any recompense for their service, and how they may be
>    removed from service.  The general operational procedures for the
>    Ombudsperson are described in Section 4, Section 5, and Section 6.
>
> 3.1.  Appointing the Ombudsperson
>
>    The Ombudsperson is appointed by the IETF Chair.


I think should be appointed by IESG, not the IETF chair, because any
IETF AD is also an individual participant that may possibly be target or
respondent.


> The appointment is
>    solely the responsibility of the IETF Chair


Responsible to the IESG not to the chair.


> although the Chair may
>    choose to consult with the IESG, the IAB, and with ISOC.
>    Furthermore, the IETF Chair may take opinion from the community.
>
>    The IETF Chair may choose to solicit nominations or advertise the
>    post.  This is entirely at the discretion of the IETF Chair.
>
>    The IETF Chair is also free to decide how many people are needed to
>    fill the role of Ombudsperson.  This may depend on the skillsets
>    available, the work load, and the opinions of the seated
>    Ombudsperson.  Furthermore, the IETF Chair may consider elements of
>    diversity in making this decision.


There should be diversity, so if a harassing is related to a race then the
ombudsperson should not be in same race.

>
> 3.2.  Qualifications and Training
>
>    It is not expected that there will be candidates with all of the
>    necessary ombudsperson skills and training who also have a clear
>    understanding and familiarity with the IETF processes and culture.
>    The Chair might choose someone with a great deal of professional
>    experience evaluating and mediating harassment disputes, but little
>    exposure to the IETF, or could select someone with more exposure to
>    the IETF community, but without as much experience dealing with
>    issues of harassment.  Since all of these attributes may be regarded
>    by the IETF Chair as essential for an appointment, the IETF is
>    committed to provide funding for necessary training for an appointed
>    Ombudsperson.
>
> 3.3.  Term of Service
>
>    An Ombudsperson shall be appointed for a two year term.  That is, the
>    Ombudsperson is making a commitment to serve for two years.  It is
>    understood, however, that circumstances may lead an Ombudsperson to
>    resign for personal or other reasons.  See also Section 3.5.
>
>    It is entirely at the discretion of the IETF Chair whether a serving
>    Ombudsperson is reappointed at the end of their term.

IMHO the Chair reports to IESG for approval.

>
> 3.4.  Recompense
>
>    An Ombudsperson shall receive no recompense for their services.  This
>    includes, but is not limited to:
>
>       IETF meeting fees
>
>       Remuneration for time spent
>
>       Out-of-pocket expenses (such as telephone charges)
>
>       Travel or accommodation expenses
>
>    The IETF will, however, meet the costs of training when agreed to by
>    the IETF Chair as described in Section 3.2.
>
> 3.5.  Removal
>
>    The IETF Chair may remove a serving Ombudsperson before the end of
>    their term without explanation to the community.


But it should be explained to IESG.


> Such an action
>    shall not be appealable.  See also Section 6.
>
> 3.6.  Disputes with the IETF Chair regarding the Ombudsperson


There should be conditions for these both roles. Is there a condition that
that chair was not a reporter or a respondent or a target for PH? I think
there should be, because if he/she is part of the harassing issue then
he/she should not be the one to decide or as you mention below unable to
resolve. Also if the IESG has some targets as well what is the procedure?

>
>    If an individual should disagree with an action taken by the IETF
>    Chair regarding the appointment, removal, or management of the
>    Ombudsperson, that person should first discuss the issue with the
>    IESG Chair directly.


I thought that the IETF chair is the IESG chair? But in here they seem
different person.


> If the IESG Chair is unable to resolve the
>    issue, the dissatisfied party may appeal to the IESG as a whole.  The
>    IESG shall then review the situation and attempt to resolve it in a
>    manner of its own choosing.


There should be clear conditions that any member of that IESG should not be
target or reporter or respondent. Otherwise they should not be able to
choose.


> The procedures of Section 6.5.4 of
>    [RFC2026] apply to this sort of appeal.
>
> 4.  Handling Reports of Harassment
>
>    Any IETF participant who believes that they or other IETF
>    participants have been harassed or may have been harassed may bring
>    the concern to the attention of the Ombudsperson.  This can be done
>    by email to "ombudsperson@ietf.org" [2], or can be done directly to
>    the Ombudsperson.  Direct contact information for the Ombudsperson,
>    including the email addresses to which "ombudsperson@ietf.org" is
>    forwarded, can be found at https://www.ietf.org/ombudsperson .
>
>    The Ombudsperson is expected to be present at the majority of IETF
>    meetings and to be available for face-to-face discussions.
>
>    All information brought to the Ombudsperson shall be kept in strict
>    confidence.  Any electronic information (such as email messages) that
>    needs to be archived shall be encrypted before it is stored.
>
>    When a Reporter brings an incident of potential harassment to the
>    Ombudsperson's attention to, the Ombudsperson will discuss the events
>    with the Reporter and may give advice including recommendations on
>    how the Reporter can handle the issue on their own and strategies on
>    how to prevent the issue from arising again.  The Ombudsperson may
>    also indicate that the issue would be best handled using regular IETF
>    procedures (such as those for dealing with disruptive behavior)
>    outside the context of harassment, and in this case the Ombudsperson
>    will provide assistance in using the relevant IETF procedures.  In
>    any event, the Ombudsperson will not initiate detailed investigations
>    or impose a remedy without agreement to proceed from the Target (or
>    the Reporter if there is no individual Target).
>
>    When conducting a detailed investigation of the circumstances
>    regarding the complaint of harassment, the Ombudsperson may contact
>    the Respondent and request a meeting in person or by a voice call.
>    The Respondent is not obliged to cooperate, but the Ombudsperson may
>    consider failure to cooperate when determining a remedy (Section 5).
>
>    In all cases the Ombudsperson will strive to maintain confidentiality
>    for all parties including the very fact of contact with the
>    Ombudsperson.
>
> 5.  Remedies
>
>    After examining the circumstances regarding the complaint of
>    harassment and determining that harassment has taken place, the
>    Ombudsperson is expected to choose a remedy that is appropriate to
>    the circumstance.  At one end of the spectrum, the Ombudsperson may
>    decide that the misbehavior is best handled with the regular IETF
>    procedures for dealing with disruptive behavior and may assist the
>    Reporter to bring the issue to the attention of the working group
>    chair or IESG member who can deal with the incident.  The
>    Ombudsperson might also choose simply to discuss the situation with
>    the Respondent and come up with a plan such that there is no repeat
>    of the harassment.

It is a weak remedy, or it is a plan.
The respondent SHOULD apologies and declare mistaken.


> With the agreement of both parties, the
>    Ombudsperson can also help to mediate a conversation between the
>    Respondent and the Target (or the Reporter if there is no individual
>    Target) in order to address the issue.

Ok.


> Finally, on the other end of
>    the spectrum, the Ombudsperson could decide that the Respondent is no
>    longer permitted to participate in a particular IETF activity,
>    whether it is a mailing list discussion, virtual meeting, or a face-
>    to-face activity, up to and including requiring that the Respondent
>    can no longer attend a face-to-face IETF meeting and its associated
>    activities, either for the remainder of the present meeting or (in
>    the extreme) future meetings.


Disagree, you did not define the limit or level of harassing or even
avoiding to define such behavior, that makes that decision unfair to
the respondent being band from the future of IETF activities (6 months can
be enough, because you don't define the limits).

AB


>
>    In determining the appropriate remedy, the Ombudsperson may
>    communicate with the Reporter, Target, and Respondent in order to
>    assess the impact that the imposition of a remedy might have on any
>    of those parties.  However, the Ombudsperson has u

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

The draft has missing parts, because 1)=A0the levels of harassing was not d=
efined, 2 )=A0it may also ignore the real practical=A0society problems that=
 make harassing occur, 3) it gives a lot of power to IETF chair without con=
ditions or limits (may be the reason is to make it simple).=A0=A0The draft =
may assume=A0that all ADs can=A0not be=A0part of harassing (not sure, draft=
 is unclear on this assumption).=A0It=A0should consider to be fair to all, =
and to prevent sources of harassing not only solving when occurs.=A0The bel=
ow comments are also initial comments.=A0<div>
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
2. =A0Definitions<br>
<br>
=A0 =A0The following terms are used in this document:<br>
<br>
=A0 =A0 =A0 Reporter: An IETF participant who reports potential harassment =
to<br>
=A0 =A0 =A0 the Ombudsperson.</blockquote><div>Please amend to PH Reporter =
(Potential=A0Harassment).=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
=A0 =A0 =A0 Respondent: An IETF participant who is claimed to have engaged =
in<br>
=A0 =A0 =A0 harassing behavior.</blockquote><div><br></div><div>This should=
 explain his/her respond and to whom he/she responding to.=A0</div><div>=A0=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">

<br>
=A0 =A0 =A0 Ombudsperson: The person who is selected to take reports of<br>
=A0 =A0 =A0 harassment, evaluate them, and impose appropriate actions and/o=
r<br>
=A0 =A0 =A0 remedies to address the circumstance. =A0This word is used in t=
he<br>
=A0 =A0 =A0 singular throughout this document although multiple ombudsperso=
ns<br>
=A0 =A0 =A0 might serve at any one time.<br>
<br>
=A0 =A0 =A0 Target: An individual IETF participant to whom the potentially<=
br>
=A0 =A0 =A0 harassing behavior was directed.</blockquote><div><br></div><di=
v>Why only individual? Why not group of people or race or gender. The targe=
t can be more than one, =A0</div><div><br></div><div>Please amend; a=A0grou=
p or an=A0individual participant.=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
=A0 =A0This document does not attempt to precisely define behavior that<br>
=A0 =A0falls under the set of procedures identified here. =A0</blockquote><=
blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px=
 #ccc solid;padding-left:1ex"></blockquote><div><br></div><div>That is good=
 but IMHO=A0still we need its=A0limits defined.=A0=A0</div>
<div><br></div><div>However, you are missing another part of behaviour dama=
ge on the IETF general behaviour. =A0So we need to define another target, w=
hich may be named; possible future target.</div><div><br></div><div>Usually=
 most harassing has two=A0victims or target=A0one=A0is the main and the oth=
er is not intended but affected, because it may become a possible future ta=
rget. Wise people avoid groups=A0that has not reported harassing.=A0</div>
<div><br></div><br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">In general,<br>
=A0 =A0disruptive behavior that occurs in the context of an IETF general or=
<br>
=A0 =A0working group mailing list, or happens in a face-to-face or virtual<=
br>
=A0 =A0meeting of a working group or the IETF plenary, can be dealt with by=
<br>
=A0 =A0our normal procedures, whereas harassing behavior that is<br>
=A0 =A0interpersonal is more easily handled by the procedures described<br>
=A0 =A0here. =A0However, there are certainly plausible reasons to address<b=
r>
=A0 =A0behaviors that take place during working-group meetings using these<=
br>
=A0 =A0procedures. =A0This document gives some guidance to those involved i=
n<br>
=A0 =A0these situations in order to decide how to handle particular<br>
=A0 =A0incidents, but in the end the final decision will involve judgment<b=
r>
=A0 =A0and the guidance of the Ombudsperson.<br>
<br>
3. =A0The Ombudsperson<br>
<br>
=A0 =A0This section describes the role of the Ombudsperson in terms of thei=
r<br>
=A0 =A0appointment, qualifications and training, the length of the term of<=
br>
=A0 =A0service, any recompense for their service, and how they may be<br>
=A0 =A0removed from service. =A0The general operational procedures for the<=
br>
=A0 =A0Ombudsperson are described in Section 4, Section 5, and Section 6.<b=
r>
<br>
3.1. =A0Appointing the Ombudsperson<br>
<br>
=A0 =A0The Ombudsperson is appointed by the IETF Chair. =A0</blockquote><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"></blockquote><div><br></div><div>I think should=
 be appointed by IESG, not the IETF chair,=A0because any IETF=A0AD is also =
an individual participant that may possibly be target or respondent.=A0</di=
v>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">The appointment is<br>
=A0 =A0solely the responsibility of the IETF Chair=A0</blockquote><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex"></blockquote><div><br></div><div>Responsible to the I=
ESG not to=A0the chair.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">although the Chair may<br>
=A0 =A0choose to consult with the IESG, the IAB, and with ISOC.<br>
=A0 =A0Furthermore, the IETF Chair may take opinion from the community.<br>
<br>
=A0 =A0The IETF Chair may choose to solicit nominations or advertise the<br=
>
=A0 =A0post. =A0This is entirely at the discretion of the IETF Chair.<br>
<br>
=A0 =A0The IETF Chair is also free to decide how many people are needed to<=
br>
=A0 =A0fill the role of Ombudsperson. =A0This may depend on the skillsets<b=
r>
=A0 =A0available, the work load, and the opinions of the seated<br>
=A0 =A0Ombudsperson. =A0Furthermore, the IETF Chair may consider elements o=
f<br>
=A0 =A0diversity in making this decision.</blockquote><div><br></div><div>T=
here should be diversity, so if a harassing is related to a=A0race then the=
 ombudsperson should not be in same race.=A0=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">

<br>
3.2. =A0Qualifications and Training<br>
<br>
=A0 =A0It is not expected that there will be candidates with all of the<br>
=A0 =A0necessary ombudsperson skills and training who also have a clear<br>
=A0 =A0understanding and familiarity with the IETF processes and culture.<b=
r>
=A0 =A0The Chair might choose someone with a great deal of professional<br>
=A0 =A0experience evaluating and mediating harassment disputes, but little<=
br>
=A0 =A0exposure to the IETF, or could select someone with more exposure to<=
br>
=A0 =A0the IETF community, but without as much experience dealing with<br>
=A0 =A0issues of harassment. =A0Since all of these attributes may be regard=
ed<br>
=A0 =A0by the IETF Chair as essential for an appointment, the IETF is<br>
=A0 =A0committed to provide funding for necessary training for an appointed=
<br>
=A0 =A0Ombudsperson.<br>
<br>
3.3. =A0Term of Service<br>
<br>
=A0 =A0An Ombudsperson shall be appointed for a two year term. =A0That is, =
the<br>
=A0 =A0Ombudsperson is making a commitment to serve for two years. =A0It is=
<br>
=A0 =A0understood, however, that circumstances may lead an Ombudsperson to<=
br>
=A0 =A0resign for personal or other reasons. =A0See also Section 3.5.<br>
<br>
=A0 =A0It is entirely at the discretion of the IETF Chair whether a serving=
<br>
=A0 =A0Ombudsperson is reappointed at the end of their term.</blockquote><d=
iv>IMHO the=A0Chair reports to IESG for approval.=A0=A0</div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">

<br>
3.4. =A0Recompense<br>
<br>
=A0 =A0An Ombudsperson shall receive no recompense for their services. =A0T=
his<br>
=A0 =A0includes, but is not limited to:<br>
<br>
=A0 =A0 =A0 IETF meeting fees<br>
<br>
=A0 =A0 =A0 Remuneration for time spent<br>
<br>
=A0 =A0 =A0 Out-of-pocket expenses (such as telephone charges)<br>
<br>
=A0 =A0 =A0 Travel or accommodation expenses<br>
<br>
=A0 =A0The IETF will, however, meet the costs of training when agreed to by=
<br>
=A0 =A0the IETF Chair as described in Section 3.2.<br>
<br>
3.5. =A0Removal<br>
<br>
=A0 =A0The IETF Chair may remove a serving Ombudsperson before the end of<b=
r>
=A0 =A0their term without explanation to the community. =A0</blockquote><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"></blockquote><div><br></div><div>But it should =
be explained to IESG.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Such an action<br>
=A0 =A0shall not be appealable. =A0See also Section 6.<br>
<br>
3.6. =A0Disputes with the IETF Chair regarding the Ombudsperson</blockquote=
><div><br></div><div>There should be conditions for these both roles.=A0Is =
there a condition that that chair was not a reporter or a respondent or a t=
arget for PH? I think there should be, because if he/she is part of the har=
assing issue then he/she should not be the one to decide or as you mention =
below unable to resolve. Also if the IESG has some targets as well what is =
the procedure?=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
=A0 =A0If an individual should disagree with an action taken by the IETF<br=
>
=A0 =A0Chair regarding the appointment, removal, or management of the<br>
=A0 =A0Ombudsperson, that person should first discuss the issue with the<br=
>
=A0 =A0IESG Chair directly. =A0</blockquote><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
</blockquote><div><br></div><div>I thought that the IETF chair is the IESG =
chair? But in here they seem different person.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">If the IESG Chair is unable to=
 resolve the<br>
=A0 =A0issue, the dissatisfied party may appeal to the IESG as a whole. =A0=
The<br>
=A0 =A0IESG shall then review the situation and attempt to resolve it in a<=
br>
=A0 =A0manner of its own choosing. =A0</blockquote><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"></blockquote><div><br></div><div>There should be clear conditions th=
at any member of that IESG should not be target or reporter or respondent. =
Otherwise they should not be able to choose.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">The procedures of Section 6.5.=
4 of<br>
=A0 =A0[RFC2026] apply to this sort of appeal.<br>
<br>
4. =A0Handling Reports of Harassment<br>
<br>
=A0 =A0Any IETF participant who believes that they or other IETF<br>
=A0 =A0participants have been harassed or may have been harassed may bring<=
br>
=A0 =A0the concern to the attention of the Ombudsperson. =A0This can be don=
e<br>
=A0 =A0by email to &quot;<a>ombudsperson@ietf.org</a>&quot; [2], or can be =
done directly to<br>
=A0 =A0the Ombudsperson. =A0Direct contact information for the Ombudsperson=
,<br>
=A0 =A0including the email addresses to which &quot;<a>ombudsperson@ietf.or=
g</a>&quot; is<br>
=A0 =A0forwarded, can be found at <a href=3D"https://www.ietf.org/ombudsper=
son" target=3D"_blank">https://www.ietf.org/ombudsperson</a> .<br>
<br>
=A0 =A0The Ombudsperson is expected to be present at the majority of IETF<b=
r>
=A0 =A0meetings and to be available for face-to-face discussions.<br>
<br>
=A0 =A0All information brought to the Ombudsperson shall be kept in strict<=
br>
=A0 =A0confidence. =A0Any electronic information (such as email messages) t=
hat<br>
=A0 =A0needs to be archived shall be encrypted before it is stored.<br>
<br>
=A0 =A0When a Reporter brings an incident of potential harassment to the<br=
>
=A0 =A0Ombudsperson&#39;s attention to, the Ombudsperson will discuss the e=
vents<br>
=A0 =A0with the Reporter and may give advice including recommendations on<b=
r>
=A0 =A0how the Reporter can handle the issue on their own and strategies on=
<br>
=A0 =A0how to prevent the issue from arising again. =A0The Ombudsperson may=
<br>
=A0 =A0also indicate that the issue would be best handled using regular IET=
F<br>
=A0 =A0procedures (such as those for dealing with disruptive behavior)<br>
=A0 =A0outside the context of harassment, and in this case the Ombudsperson=
<br>
=A0 =A0will provide assistance in using the relevant IETF procedures. =A0In=
<br>
=A0 =A0any event, the Ombudsperson will not initiate detailed investigation=
s<br>
=A0 =A0or impose a remedy without agreement to proceed from the Target (or<=
br>
=A0 =A0the Reporter if there is no individual Target).<br>
<br>
=A0 =A0When conducting a detailed investigation of the circumstances<br>
=A0 =A0regarding the complaint of harassment, the Ombudsperson may contact<=
br>
=A0 =A0the Respondent and request a meeting in person or by a voice call.<b=
r>
=A0 =A0The Respondent is not obliged to cooperate, but the Ombudsperson may=
<br>
=A0 =A0consider failure to cooperate when determining a remedy (Section 5).=
<br>
<br>
=A0 =A0In all cases the Ombudsperson will strive to maintain confidentialit=
y<br>
=A0 =A0for all parties including the very fact of contact with the<br>
=A0 =A0Ombudsperson.<br>
<br>
5. =A0Remedies<br>
<br>
=A0 =A0After examining the circumstances regarding the complaint of<br>
=A0 =A0harassment and determining that harassment has taken place, the<br>
=A0 =A0Ombudsperson is expected to choose a remedy that is appropriate to<b=
r>
=A0 =A0the circumstance. =A0At one end of the spectrum, the Ombudsperson ma=
y<br>
=A0 =A0decide that the misbehavior is best handled with the regular IETF<br=
>
=A0 =A0procedures for dealing with disruptive behavior and may assist the<b=
r>
=A0 =A0Reporter to bring the issue to the attention of the working group<br=
>
=A0 =A0chair or IESG member who can deal with the incident. =A0The<br>
=A0 =A0Ombudsperson might also choose simply to discuss the situation with<=
br>
=A0 =A0the Respondent and come up with a plan such that there is no repeat<=
br>
=A0 =A0of the harassment. =A0</blockquote><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></=
blockquote><div>It is a weak remedy, or it is a plan.=A0</div><div>The resp=
ondent SHOULD apologies and declare mistaken.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">With the agreement of both par=
ties, the<br>
=A0 =A0Ombudsperson can also help to mediate a conversation between the<br>
=A0 =A0Respondent and the Target (or the Reporter if there is no individual=
<br>
=A0 =A0Target) in order to address the issue. =A0</blockquote><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"></blockquote><div>Ok.=A0</div><div>=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex">
Finally, on the other end of<br>
=A0 =A0the spectrum, the Ombudsperson could decide that the Respondent is n=
o<br>
=A0 =A0longer permitted to participate in a particular IETF activity,<br>
=A0 =A0whether it is a mailing list discussion, virtual meeting, or a face-=
<br>
=A0 =A0to-face activity, up to and including requiring that the Respondent<=
br>
=A0 =A0can no longer attend a face-to-face IETF meeting and its associated<=
br>
=A0 =A0activities, either for the remainder of the present meeting or (in<b=
r>
=A0 =A0the extreme) future meetings.</blockquote><div><br></div><div>Disagr=
ee, you did not define the limit or level of harassing or even avoiding to =
define such=A0behavior,=A0that makes that decision unfair to the=A0responde=
nt being=A0band from the future of IETF activities (6 months can be enough,=
 because you don&#39;t define the limits).=A0</div>
<div><br></div><div>AB</div><div>=A0</div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
=A0 =A0In determining the appropriate remedy, the Ombudsperson may<br>
=A0 =A0communicate with the Reporter, Target, and Respondent in order to<br=
>
=A0 =A0assess the impact that the imposition of a remedy might have on any<=
br>
=A0 =A0of those parties. =A0However, the Ombudsperson has u</blockquote></d=
iv>

--20cf3011e027e9e12204f2df2f59--


From nobody Thu Feb 20 16:04: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 499CB1A0358 for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 16:04:21 -0800 (PST)
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 tB3gKKUw0IRI for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 16:04:19 -0800 (PST)
Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5CB221A0350 for <ietf@ietf.org>; Thu, 20 Feb 2014 16:04:19 -0800 (PST)
Received: by mail-pd0-f179.google.com with SMTP id fp1so2496204pdb.24 for <ietf@ietf.org>; Thu, 20 Feb 2014 16:04:15 -0800 (PST)
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=4sZ8U44QFqmoniOPU5PtWOf1Hg87lTMh6JquptPXGUg=; b=kBlw1sXT31Ks7UrachrZr+uWFyunf2Srzn6lQimP+gwGsKfoCwInPU022mANnhWQRH BrcphLXXWz4r2pmINSVVgFyzbXqOP9ul+Fxa/FE9Jw4TMHOJTV+3muXqQdxElRKBJGyK tVgxmCy8N+JMzQzCf/QTOxpCxLdAQnf9/z2+DKaIUQq2HP//FwZgkMHHQAhxwKWD76ca 0ZMG315C/VHMxtfbrsU+IxOVhrMbYHGjsqb+J0ey4kWU7KxB6JCwM3nR11+INv7yk3W0 kxlL2xMBCfnjTnL/L3H94W4QDlgbfRaPcxgye2lVEKk20MrM1g53p8V+sq/P9+AEn1TU h4sg==
X-Received: by 10.66.145.199 with SMTP id sw7mr5193514pab.143.1392941055809; Thu, 20 Feb 2014 16:04:15 -0800 (PST)
Received: from [192.168.178.23] (189.201.69.111.dynamic.snap.net.nz. [111.69.201.189]) by mx.google.com with ESMTPSA id yz5sm35935026pac.9.2014.02.20.16.04.12 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Feb 2014 16:04:14 -0800 (PST)
Message-ID: <53069808.3000903@gmail.com>
Date: Fri, 21 Feb 2014 13:04:24 +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: draft naming was RE: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk> <D8A2F939F08761DEFEEA946E@JcK-HP8200.jck.com>
In-Reply-To: <D8A2F939F08761DEFEEA946E@JcK-HP8200.jck.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fyQ8LV_S8wjnaledflarIr-Zpjs
Cc: adrian@olddog.co.uk, presnick@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, 21 Feb 2014 00:04:21 -0000

On 21/02/2014 12:15, John C Klensin wrote:
...
> I've often wished that the submission tool would check a table
> for a small number of organizational tags (ietf, iab, etc.) and,
> if the first string after "draft-" didn't appear there, check it
> against the first author name.  

Why only the first author? I don't think that restriction is called
for.

> It would be fairly easy to
> verify that "draft-ietf-" was followed immediately by a
> short-form WG name too.  

I believe that is already checked, since draft-ietf-*-00 drafts have to
be approved by a WG Chair, and that case is detected automatically.

   Brian

> If documents that didn't satisfy those
> criteria went to manual posting and required an explanation to
> the secretariat, I think the cutesiness would mostly stop in a
> hurry.  If would also stop "draft-<made-up-organization>-..."
> which, IMO, would be a real service to the community.
> 
>     john
> 
> 
> 


From nobody Thu Feb 20 21:53:15 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 837A11A0420 for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 21:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.653
X-Spam-Level: 
X-Spam-Status: No, score=-4.653 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, TO_IN_SUBJ=2.796] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id voTpTllvuV6A for <ietf@ietfa.amsl.com>; Thu, 20 Feb 2014 21:53:10 -0800 (PST)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 6225D1A0312 for <ietf@ietf.org>; Thu, 20 Feb 2014 21:53:10 -0800 (PST)
Received: from /spool/local by e34.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, 20 Feb 2014 22:53:06 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 20 Feb 2014 22:53:04 -0700
Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id CA8A519D8046 for <ietf@ietf.org>; Thu, 20 Feb 2014 22:53:02 -0700 (MST)
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by b03cxnp08025.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1L5r4Oo9699622 for <ietf@ietf.org>; Fri, 21 Feb 2014 06:53:04 +0100
Received: from d03av01.boulder.ibm.com (localhost [127.0.0.1]) by d03av01.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s1L5r395022508 for <ietf@ietf.org>; Thu, 20 Feb 2014 22:53:03 -0700
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d03av01.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s1L5r3gS022463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Thu, 20 Feb 2014 22:53:03 -0700
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 s1L5r2DA013170 for <ietf@ietf.org>; Fri, 21 Feb 2014 00:53:02 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s1L5r2BP013122 for ietf@ietf.org; Fri, 21 Feb 2014 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201402210553.s1L5r2BP013122@rotala.raleigh.ibm.com>
Date: Fri, 21 Feb 2014 00:53:02 -0500
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: 14022105-1542-0000-0000-00000674D368
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HcnDRFSRL8dkVp708mx7_iffDLo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2014 05:53:13 -0000

Total of 84 messages in the last 7 days.
 
script run at: Fri Feb 21 00:53:02 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  7.14% |    6 | 11.18% |    89604 | hallam@gmail.com
  5.95% |    5 |  6.68% |    53530 | jmamodio@gmail.com
  5.95% |    5 |  4.68% |    37546 | barryleiba@computer.org
  3.57% |    3 |  6.81% |    54600 | abdussalambaryun@gmail.com
  5.95% |    5 |  4.00% |    32069 | john-ietf@jck.com
  4.76% |    4 |  4.10% |    32902 | l.wood@surrey.ac.uk
  4.76% |    4 |  3.97% |    31802 | brian.e.carpenter@gmail.com
  2.38% |    2 |  6.08% |    48733 | bclaise@cisco.com
  4.76% |    4 |  3.63% |    29137 | sm+ietf@elandsys.com
  3.57% |    3 |  4.56% |    36550 | jari.arkko@piuha.net
  3.57% |    3 |  2.50% |    20001 | ted.lemon@nominum.com
  3.57% |    3 |  2.42% |    19413 | chair@ietf.org
  2.38% |    2 |  2.82% |    22609 | jcurran@istaff.org
  2.38% |    2 |  2.33% |    18698 | andrewf@plixer.com
  2.38% |    2 |  2.26% |    18110 | adrian@olddog.co.uk
  2.38% |    2 |  2.07% |    16563 | david.black@emc.com
  2.38% |    2 |  1.47% |    11803 | avri@acm.org
  1.19% |    1 |  1.96% |    15674 | jcurran@arin.net
  1.19% |    1 |  1.78% |    14303 | cntreras@gmail.com
  1.19% |    1 |  1.52% |    12169 | ron.even.tlv@gmail.com
  1.19% |    1 |  1.48% |    11851 | mgramirez@globe.com.ph
  1.19% |    1 |  1.45% |    11660 | ayourtch@cisco.com
  1.19% |    1 |  1.39% |    11169 | jmh@joelhalpern.com
  1.19% |    1 |  1.26% |    10123 | henrik@levkowetz.com
  1.19% |    1 |  1.13% |     9085 | schmidt@informatik.haw-hamburg.de
  1.19% |    1 |  1.10% |     8857 | iab-chair@iab.org
  1.19% |    1 |  1.10% |     8844 | narten@us.ibm.com
  1.19% |    1 |  1.04% |     8342 | loa@pi.nu
  1.19% |    1 |  1.04% |     8298 | tbray@textuality.com
  1.19% |    1 |  1.01% |     8069 | rdroms.ietf@gmail.com
  1.19% |    1 |  0.92% |     7340 | lear@cisco.com
  1.19% |    1 |  0.90% |     7239 | huitema@microsoft.com
  1.19% |    1 |  0.90% |     7227 | paul@nohats.ca
  1.19% |    1 |  0.89% |     7101 | hildjj@cursive.net
  1.19% |    1 |  0.88% |     7050 | d3e3e3@gmail.com
  1.19% |    1 |  0.86% |     6875 | ynir@checkpoint.com
  1.19% |    1 |  0.82% |     6542 | mnot@mnot.net
  1.19% |    1 |  0.78% |     6283 | juliao@braga.eti.br
  1.19% |    1 |  0.77% |     6158 | john@jck.com
  1.19% |    1 |  0.76% |     6064 | worley@ariadne.com
  1.19% |    1 |  0.73% |     5826 | ggm@algebras.org
  1.19% |    1 |  0.70% |     5617 | hartmans-ietf@mit.edu
  1.19% |    1 |  0.69% |     5553 | dhc@dcrocker.net
  1.19% |    1 |  0.57% |     4590 | jnc@mercury.lcs.mit.edu
--------+------+--------+----------+------------------------
100.00% |   84 |100.00% |   801579 | Total


From nobody Fri Feb 21 00:00:14 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 9B0BB1A04BF for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 00:00:12 -0800 (PST)
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 rV2aEh5YzKVj for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 00:00:10 -0800 (PST)
Received: from trammell.ch (trammell1.nine.ch [5.148.172.66]) by ietfa.amsl.com (Postfix) with ESMTP id CA9D81A04B2 for <ietf@ietf.org>; Fri, 21 Feb 2014 00:00:09 -0800 (PST)
Received: from [IPv6:2001:470:26:9c2::2] (unknown [IPv6:2001:470:26:9c2::2]) by trammell.ch (Postfix) with ESMTPSA id 3C5191A0330; Fri, 21 Feb 2014 08:59:33 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_11936F7C-49A3-4293-A15F-D52EBF5CB208"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: draft naming was RE: anti-harassment procedures
From: Brian Trammell <ietf@trammell.ch>
In-Reply-To: <53069808.3000903@gmail.com>
Date: Fri, 21 Feb 2014 08:59:31 +0100
Message-Id: <B0547AEF-6B17-495B-B87C-1381B640D038@trammell.ch>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk> <D8A2F939F08761DEFEEA946E@JcK-HP8200.jck.com> <53069808.3000903@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_lzL16EMSDF5-K0MLwt16ZOfW0A
Cc: John C Klensin <john-ietf@jck.com>, Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2014 08:00:12 -0000

--Apple-Mail=_11936F7C-49A3-4293-A15F-D52EBF5CB208
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

As long as (1) we have tools to map authors to documents for search and =
aggregation purposes anyway, (2) we maintain the reserved structure of =
draft-ietf-wg-* and other special second elements, I don't see any =
reason to further restrict the second element of the draft name.

This came in handy recently in IPPM, where we had multiple proposals for =
a performance metrics registry that started pretty widely separated from =
each other. It would have been arbitrary and inaccurate simply to choose =
an author name for each the (individual draft) stages of the =
convergence; the resulting draft-manyfolks-ippm-metric-registry-00 is =
IMO accurately named.=20

A policy strictly restricting element 2 to author names would have =
required us to waste energy on a "what do we want to name the band" =
discussion.

Regards,

Brian

On 21 Feb 2014, at 01:04, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 21/02/2014 12:15, John C Klensin wrote:
> ...
>> I've often wished that the submission tool would check a table
>> for a small number of organizational tags (ietf, iab, etc.) and,
>> if the first string after "draft-" didn't appear there, check it
>> against the first author name. =20
>=20
> Why only the first author? I don't think that restriction is called
> for.
>=20
>> It would be fairly easy to
>> verify that "draft-ietf-" was followed immediately by a
>> short-form WG name too. =20
>=20
> I believe that is already checked, since draft-ietf-*-00 drafts have =
to
> be approved by a WG Chair, and that case is detected automatically.
>=20
>   Brian
>=20
>> If documents that didn't satisfy those
>> criteria went to manual posting and required an explanation to
>> the secretariat, I think the cutesiness would mostly stop in a
>> hurry.  If would also stop "draft-<made-up-organization>-..."
>> which, IMO, would be a real service to the community.
>>=20
>>    john
>>=20
>>=20
>>=20
>=20


--Apple-Mail=_11936F7C-49A3-4293-A15F-D52EBF5CB208
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

iQEcBAEBCgAGBQJTBwdjAAoJENt3nsOmbNJczBYIAMb4MA3ozHJ5CRsDeVlVdk45
3gRhCxUrDuBz4dART8EvsYuVgaKefiLscs97O0yCWDeBk+UyIDiBHcF7jWfiq8Xv
qtjcjzVcjlRJj53lolIcpgrlzuCnpnU1s58FnssFZeBtYThPnpHb9xTFhoRH/9aO
DB9EZ08PUWMzCT6trSJP2Ht/vFdXN2XAkRt5e+5E/i3vWmyn/VQE+bS7oPk5IYaC
jUwi3Z7/PqDQuGTXQt7buDWTuncDFzv/0JlHsf7hOgnD4bHxcMbhOT6pJ5c2eHIb
6rxzllVvel0I+E/+xz0+g3Zm3K3Y/GQ0NuDNqTaiK86+DlJW3L1ZMgE/f+76/10=
=VtGs
-----END PGP SIGNATURE-----

--Apple-Mail=_11936F7C-49A3-4293-A15F-D52EBF5CB208--


From nobody Fri Feb 21 01:32:42 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 22E701A04F6 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 01:32:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, 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 5uKa1rE50rBY for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 01:32:38 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 138B71A0502 for <ietf@ietf.org>; Fri, 21 Feb 2014 01:32:38 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.136.52]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1L9W7oc015180 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Feb 2014 01:32:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1392975144; bh=lwNmE3jX/KC0tV00ArO7S842fL3pkry6T8B8Eb75hc8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=vreIYmTML8OcyZqBND5m7BhhZbEu3mRWdroKfygFCMw23zp38XFGuexozoW032orO sMwJvCmeJdX9aXYvDABqc9fSVuMLHcCTaWNIsUTFhlPCqGZO29zsyLZ6QVwEJE6jd2 rEjY5VpULwVaEeWXcvdWGVsqQsGwAQAazI919Bx8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1392975144; i=@elandsys.com; bh=lwNmE3jX/KC0tV00ArO7S842fL3pkry6T8B8Eb75hc8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZSP4jHIJCmTaErpT+4oia5GS7p95mmAdDr1w00ocPteUeRkx2rlpsvfWOH+EysrEC Kvuo/frDuWTAFImIl1kASnhpdg/K2QNEfTzyj9SO3bLSmehKaSVCoYYj3OLvLf6sv2 3mtEwGNqicW1SkZDdnzPLPAl5xVIIczdIBfGXboE=
Message-Id: <6.2.5.6.2.20140220223554.0bb9bfa0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 21 Feb 2014 01:23:08 -0800
To: Phillip Hallam-Baker <hallam@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Appeal from Phillip Hallam-Baker on the publication of RFC 7049 on the Standards Track
In-Reply-To: <CAMm+LwiojSW-gMOS6hzScKGtFrAz34ObFGcBRcs2a6tiZPkoSg@mail.g mail.com>
References: <CALaySJK8xBz6DeYNVv-Q5ctbSkoqOfZ9ZK-wKdtp3JvfmDbseg@mail.gmail.com> <tsld2ii3kme.fsf@mit.edu> <CALaySJLHCkZA0dpkXta1f9gurdMu+O=8K+6+QUMjEJNcuepU9A@mail.gmail.com> <A9AB0AA4-7229-4F43-B7D8-75599E2F8F49@gmail.com> <6.2.5.6.2.20140220104653.0cd98288@resistor.net> <CAMm+LwiojSW-gMOS6hzScKGtFrAz34ObFGcBRcs2a6tiZPkoSg@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/zt1PDNsIdd_4cN-RwY8uy4dBTF8
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, 21 Feb 2014 09:32:40 -0000

Hi Phillip,
At 13:08 20-02-2014, Phillip Hallam-Baker wrote:
>An appeal was raised. If you think that the process has to be 
>followed or bad things will result then you should insist that the 
>IESG address the matter in an official capacity to avoid the setting 
>of the precedent you want to avoid.

The only way I can insist that the IESG address the matter is if I 
can convince one or more Area Directors that I might be able to 
recall [2] them if they do not address the matter.

>I find it rather interesting that there has been more concern about 
>the correct way to handle the non-handling of the appeal than there 
>ever was about the rather minor changes to the specification I 
>proposed that could have avoided the need for process questions at all.

The only recourse available to me in the case of an arbitrary 
decision [2] is the the appeal process.  I might not get any help if 
I do not know the correct way for an appeal.  If I do not know the 
process the only choice left to me would be to accept an arbitrary decision.

Regards,
S. Moonesamy

1. http://tools.ietf.org/html/draft-moonesamy-nomcom-eligibility-01
2. There is an informative comment at 
http://www.ietf.org/mail-archive/web/diversity/current/msg00269.html 


From nobody Fri Feb 21 02:25:14 2014
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61BEB1A04E5 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 02:25:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2NJzP5pIcsgL for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 02:25:10 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 39AA81A008E for <ietf@ietf.org>; Fri, 21 Feb 2014 02:25:10 -0800 (PST)
Received: from [192.168.1.133] (81-236-221-144-no93.tbcn.telia.com [81.236.221.144]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id D9519180150F; Fri, 21 Feb 2014 11:25:05 +0100 (CET)
Message-ID: <53072981.1020102@pi.nu>
Date: Fri, 21 Feb 2014 11:25:05 +0100
From: Loa Andersson <loa@pi.nu>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, jari.arkko@piuha.net, ietf@ietf.org
Subject: Re: draft naming was RE: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334724@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/zbs_78g1aoyk9FQc0rs7bPem1TE
Cc: adrian@olddog.co.uk, 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, 21 Feb 2014 10:25:12 -0000

Folks,

As wg chair I'm not interested in draft with file-names like
draft-farel-farell-mpls-opportunistic-encrypt, the draft will not show
up on the mpls wg webpage, and I will have to hunt drafts all over the
place. draft-farrelll-mpls-opportunistic-encrypt is much better.

/Loa

On 2014-02-20 22:22, l.wood@surrey.ac.uk wrote:
> An annoying trend:
>
>                     IETF Anti-Harassment Procedures
>                     draft-farrresnickel-harassment-00
>
> should have been farrel-resnick
>
>               Opportunistic Encryption in MPLS Networks
>            draft-farrelll-mpls-opportunistic-encrypt-00.txt
>
> should have been farrel-farell
>
> When trying to locate drafts by author name, or pick up on primary authors for indexing, or indicate drafts from memory, this cutesiness really doesn't help. Cut it out, Adrian.
>
> If you don't actually want your name on a draft (and the need for anonymous draft submission seems as if it could be useful?) 'Smithee,' as used by film directors, seems a reasonable thing to adopt.
>
> Alan Smithee
> http://en.wikipedia.org/wiki/Alan_Smithee
>

-- 


Loa Andersson                        email: loa@mail01.huawei.com
Senior MPLS Expert                          loa@pi.nu
Huawei Technologies (consultant)     phone: +46 739 81 21 64


From nobody Fri Feb 21 06:56:47 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 758DA1A01AD for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 06:56:45 -0800 (PST)
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 klQ439fONAqj for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 06:56:43 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id D1C991A0179 for <ietf@ietf.org>; Fri, 21 Feb 2014 06:56:42 -0800 (PST)
Received: by mail-lb0-f179.google.com with SMTP id l4so2423414lbv.10 for <ietf@ietf.org>; Fri, 21 Feb 2014 06:56:38 -0800 (PST)
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=AX7yso1gaE8SqnOEsODdvIXFzEPZ7uwL4RbcnxQym04=; b=E/tCzpuYK0RvHKf/JudbSNNmCebDt+kaitDY3MWIKpsdJdRz0t2oDcLXgTYtiz4uOy 3a2amH5OBKr5i6wOBikL4RDqLQaybnhVW9L8dMoV8CiQq6lMDe5P3Z0btYc/GqDTjQN1 ZwxsT9rexgW8pm5mXf4DscgnSIRDSoQ5cx2I/rr/Y4/ccan4jWWwxKrmwLRgxiHkvzvf VaO2eGaGnzdL623k7eMs7QWBy24DEFzRHOmUgQPQJV3gC6tnz94uICxuZ54uyPJ1e9r1 K4iTiw/71/sfO0KBZJiJm1gPkCYZ5kqlQnfdZiTWNoZt71Y2O3UMHCnpNBhQftJ2nj2S nNLA==
MIME-Version: 1.0
X-Received: by 10.152.203.193 with SMTP id ks1mr4716858lac.0.1392994598237; Fri, 21 Feb 2014 06:56:38 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Fri, 21 Feb 2014 06:56:38 -0800 (PST)
Date: Fri, 21 Feb 2014 09:56:38 -0500
Message-ID: <CAMm+LwjuroOSm-feRhGXkZgP6rWfYYb7i78jf1TR0LtQ+hXj0g@mail.gmail.com>
Subject: Eating the dog food
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=001a113470d233bc3204f2ebd402
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fH1MilWlQNofDc9dm6L34M3gPF4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2014 14:56:45 -0000

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

We have a lot of security protocols that the IETF does not deploy on its
own sites.

There is thus a push from many quarters to have the IETF eat its own dog
food which is of course an excellent idea.

But could I just point out that the point is not to eat the dog food so as
to convince ourselves just how tasty and yummy it is. The value of a dog
food program comes when the manufacturer realizes that there is a reason
the dogs don't like it and changes the recipe.

Without feedback, the process is like doing usability evaluations in a lab
and taking no notice of the outcomes.

I am seeing a lot of groups demanding the IETF eat the dog food but rather
fewer asking why they dog food isn't being eaten.


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

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

<div dir=3D"ltr">We have a lot of security protocols that the IETF does not=
 deploy on its own sites.<div><br></div><div>There is thus a push from many=
 quarters to have the IETF eat its own dog food which is of course an excel=
lent idea.</div>
<div><br></div><div>But could I just point out that the point is not to eat=
 the dog food so as to convince ourselves just how tasty and yummy it is. T=
he value of a dog food program comes when the manufacturer realizes that th=
ere is a reason the dogs don&#39;t like it and changes the recipe.</div>
<div><br></div><div>Without feedback, the process is like doing usability e=
valuations in a lab and taking no notice of the outcomes.</div><div><br></d=
iv><div>I am seeing a lot of groups demanding the IETF eat the dog food but=
 rather fewer asking why they dog food isn&#39;t being eaten.</div>
<div><br clear=3D"all"><div><br></div>-- <br>Website: <a href=3D"http://hal=
lambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--001a113470d233bc3204f2ebd402--


From nobody Fri Feb 21 07:06:32 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 5D6E51A0198 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 07:06:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.703
X-Spam-Level: 
X-Spam-Status: No, score=-6.703 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id y9gdCGuKRxDs for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 07:06:29 -0800 (PST)
Received: from aer-iport-4.cisco.com (unknown [173.38.203.54]) by ietfa.amsl.com (Postfix) with ESMTP id B7E2B1A0179 for <ietf@ietf.org>; Fri, 21 Feb 2014 07:06:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3728; q=dns/txt; s=iport; t=1392995185; x=1394204785; h=message-id:date:from:mime-version:to:subject:references: in-reply-to; bh=tIhpQMnLmOiZM5++LgcfVz6koMu1scIXIDnI6OwQleo=; b=FmKLr10Blo1z2Px53VctwTgluRFAEO7gLrI9dazDy0l6Z3cHML5VXV/c lKv7Sdv7OcDm+MN8Jn2YRlTszQCZQ0MHLx303kOA86FmeAcmWbMhBKkeR IGmyMR1I/cTCfdA6UcHYCYofqOsIHqB27f9uH8qbAFECnb7xkgxcYKbmH Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgwFAHZqB1OQ/khR/2dsb2JhbABagwY7g1qFXbddgQ4WdIIlAQEBBCNVEQsEFAkWCwICCQMCAQIBKxoGAQwIAQGIAapCoRgXjmuCb4FJBJg0gTKQdYMuOw
X-IronPort-AV: E=Sophos;i="4.97,519,1389744000"; d="scan'208,217";a="929551"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-4.cisco.com with ESMTP; 21 Feb 2014 15:06:24 +0000
Received: from mctiny.local ([10.61.203.44]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1LF6N0w002922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 21 Feb 2014 15:06:24 GMT
Message-ID: <53076B6F.4060603@cisco.com>
Date: Fri, 21 Feb 2014 16:06:23 +0100
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.3.0
MIME-Version: 1.0
To: Phillip Hallam-Baker <hallam@gmail.com>, IETF Discussion Mailing List <ietf@ietf.org>
Subject: Re: Eating the dog food
References: <CAMm+LwjuroOSm-feRhGXkZgP6rWfYYb7i78jf1TR0LtQ+hXj0g@mail.gmail.com>
In-Reply-To: <CAMm+LwjuroOSm-feRhGXkZgP6rWfYYb7i78jf1TR0LtQ+hXj0g@mail.gmail.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/alternative; boundary="------------030308020106010003080105"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WlatcY01PKP62OwBT_UPcHR4NwQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2014 15:06:30 -0000

This is a multi-part message in MIME format.
--------------030308020106010003080105
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi Phill,

We held a workshop about this dogfood "Internet Technology Adoption and
Transition" (ITAT) in December, where we talked a bit about that, not
just from a security perspective.  I'll have a draft of the report
posted when the directory reopens, and there will be a brief BRIEF
report in the tech plenary (which will be busy).

Eliot

On 2/21/14, 3:56 PM, Phillip Hallam-Baker wrote:
> We have a lot of security protocols that the IETF does not deploy on
> its own sites.
>
> There is thus a push from many quarters to have the IETF eat its own
> dog food which is of course an excellent idea.
>
> But could I just point out that the point is not to eat the dog food
> so as to convince ourselves just how tasty and yummy it is. The value
> of a dog food program comes when the manufacturer realizes that there
> is a reason the dogs don't like it and changes the recipe.
>
> Without feedback, the process is like doing usability evaluations in a
> lab and taking no notice of the outcomes.
>
> I am seeing a lot of groups demanding the IETF eat the dog food but
> rather fewer asking why they dog food isn't being eaten.
>
>
> -- 
> Website: http://hallambaker.com/


--------------030308020106010003080105
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">
    Hi Phill,<br>
    <br>
    We held a workshop about this dogfood "Internet Technology Adoption
    and Transition" (ITAT) in December, where we talked a bit about
    that, not just from a security perspective.Â  I'll have a draft of
    the report posted when the directory reopens, and there will be a
    brief BRIEF report in the tech plenary (which will be busy).<br>
    <br>
    Eliot<br>
    <br>
    <div class="moz-cite-prefix">On 2/21/14, 3:56 PM, Phillip
      Hallam-Baker wrote:<br>
    </div>
    <blockquote
cite="mid:CAMm+LwjuroOSm-feRhGXkZgP6rWfYYb7i78jf1TR0LtQ+hXj0g@mail.gmail.com"
      type="cite">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <div dir="ltr">We have a lot of security protocols that the IETF
        does not deploy on its own sites.
        <div><br>
        </div>
        <div>There is thus a push from many quarters to have the IETF
          eat its own dog food which is of course an excellent idea.</div>
        <div><br>
        </div>
        <div>But could I just point out that the point is not to eat the
          dog food so as to convince ourselves just how tasty and yummy
          it is. The value of a dog food program comes when the
          manufacturer realizes that there is a reason the dogs don't
          like it and changes the recipe.</div>
        <div><br>
        </div>
        <div>Without feedback, the process is like doing usability
          evaluations in a lab and taking no notice of the outcomes.</div>
        <div><br>
        </div>
        <div>I am seeing a lot of groups demanding the IETF eat the dog
          food but rather fewer asking why they dog food isn't being
          eaten.</div>
        <div><br clear="all">
          <div><br>
          </div>
          -- <br>
          Website: <a moz-do-not-send="true"
            href="http://hallambaker.com/">http://hallambaker.com/</a><br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------030308020106010003080105--


From nobody Fri Feb 21 08:36:49 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 732961A01DC for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 08:36:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.27
X-Spam-Level: 
X-Spam-Status: No, score=-0.27 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, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548, 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 wP1qfKgCS9Dw for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 08:36:45 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by ietfa.amsl.com (Postfix) with ESMTP id 262BC1A01BC for <ietf@ietf.org>; Fri, 21 Feb 2014 08:36:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tana.it; s=beta; t=1393000599; bh=XFLMcgq8KX42ySDiPNUFg1FKk/9vNTzwzEtrj6Tbx34=; l=4069; h=Date:From:To:References:In-Reply-To; b=aGwgoWZYTVWk+1N7m9PSXl71w7Z1d0HTDyFfTPf4k3WK188vg1TT2OaPGZjvbqoXF WaIxCp0PVld8eZZQSQJ9hMbiSM2hBVKvjHn2VnpSMfdi4iAhXeynY9PxG8/sK3SB4m HcghwYa5FDP7b2XfK0Z/wbeES6Z48LKqUqOn6TVk=
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, 21 Feb 2014 17:36:39 +0100 id 00000000005DC044.0000000053078097.00003595
Message-ID: <53078097.7040803@tana.it>
Date: Fri, 21 Feb 2014 17:36:39 +0100
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: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net>
In-Reply-To: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.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/w_xttRtNo7emv22waQyvyo42FEM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2014 16:36:47 -0000

Hi

On Thu 20/Feb/2014 21:56:38 +0100 Jari Arkko wrote: 
> 
> I know this topic is hard to discuss. Hopefully there are very few
> situations where these procedures are needed, but they are needed.
> I thank you for your help and respectful input into this difficult
> but important discussion.

A couple of comments:

> 
>                     IETF Anti-Harassment Procedures
>                    draft-farrresnickel-harassment-00
> 

>    The following terms are used in this document:
> 
>       Reporter: An IETF participant who reports potential harassment to
>       the Ombudsperson.

You mean "harassment or potential harassment", don't you?

I suggest a fifth definition, grouping the persons --Target(s) or
Reporter(s)-- who started or were involved in a case.  For example:

   Harassed Subject:  The Target or the Reporter if there is no
   individual Target.

> 
>    The Ombudsperson is expected to be present at the majority of IETF
>    meetings and to be available for face-to-face discussions.

In that case, it might be practical to consider Ombudsperson deputies,
nominated by the Ombudsperson directly, possibly for a single
meeting/event only.

>    All information brought to the Ombudsperson shall be kept in strict
>    confidence.

Yes, unless the Harassed Subjects agree to publish it.  I see no
reason to make it necessarily confidential in every case.  In some
cases, public disapprobation can save the day (see below).

>    Any electronic information (such as email messages) that
>    needs to be archived shall be encrypted before it is stored.

Since this is not a technical memo, it could suffice to say that the
Ombudsperson will use adequate precautions when transmitting or
archiving confidential information.

>    When a Reporter brings an incident of potential harassment to the
>    Ombudsperson's attention to, the Ombudsperson will discuss the events
>    with the Reporter and may give advice including recommendations on
>    how the Reporter can handle the issue on their own and strategies on
>    how to prevent the issue from arising again.  The Ombudsperson may
>    also indicate that the issue would be best handled using regular IETF
>    procedures (such as those for dealing with disruptive behavior)
>    outside the context of harassment, and in this case the Ombudsperson
>    will provide assistance in using the relevant IETF procedures.  In
>    any event, the Ombudsperson will not initiate detailed investigations
>    or impose a remedy without agreement to proceed from the Target (or
>    the Reporter if there is no individual Target).

This is yet another place where the fifth definition comes handy.

>    After examining the circumstances regarding the complaint of
>    harassment and determining that harassment has taken place, the
>    Ombudsperson is expected to choose a remedy that is appropriate to
>    the circumstance.  At one end of the spectrum, the Ombudsperson may
>    decide that the misbehavior is best handled with the regular IETF
>    procedures for dealing with disruptive behavior and may assist the
>    Reporter to bring the issue to the attention of the working group
>    chair or IESG member who can deal with the incident.  The
>    Ombudsperson might also choose simply to discuss the situation with
>    the Respondent and come up with a plan such that there is no repeat
>    of the harassment.  With the agreement of both parties, the
>    Ombudsperson can also help to mediate a conversation between the
>    Respondent and the Target (or the Reporter if there is no individual
>    Target) in order to address the issue.

In such circumstances, the Ombudsperson can devise a punishment or
penitence to be inflicted to the Respondent.  Anything like a slap on
the wrist or having the Respondent stand naked on the stage and
publicly apologize for his/her misconduct will do, so long as the
Harassed Subjects agree that it is appropriate.  Of course, the
Ombudsperson has no legal power to enforce a punishment, but the
Respondent's willingness to receive it voluntarily is to be considered
when making further decisions on the case.

jm2c
Ale


From nobody Fri Feb 21 10:01: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 8E6111A0221 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 10:01:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.148
X-Spam-Level: 
X-Spam-Status: No, score=-5.148 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6HyBEj7BHl4I for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 10:01:46 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id E09511A0259 for <ietf@ietf.org>; Fri, 21 Feb 2014 10:01:42 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WGuN2-000ISv-RD; Fri, 21 Feb 2014 12:58:44 -0500
Date: Fri, 21 Feb 2014 12:56:44 -0500
From: John C Klensin <john-ietf@jck.com>
To: Brian Trammell <ietf@trammell.ch>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: draft naming was RE: anti-harassment procedures
Message-ID: <CBCE3D12A02171C641B67A75@JcK-HP8200.jck.com>
In-Reply-To: <B0547AEF-6B17-495B-B87C-1381B640D038@trammell.ch>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk> <D8A2F939F08761DEFEEA946E@JcK-HP8200.jck.com> <53069808.3000903@gmail.com> <B0547AEF-6B17-495B-B87C-1381B640D038@trammell.ch>
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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1SbJgVO6LPohGnLrW2YbiPT0Mmg
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2014 18:01:48 -0000

--On Friday, February 21, 2014 08:59 +0100 Brian Trammell
<ietf@trammell.ch> wrote:

> As long as (1) we have tools to map authors to documents for
> search and aggregation purposes anyway, (2) we maintain the
> reserved structure of draft-ietf-wg-* and other special second
> elements, I don't see any reason to further restrict the
> second element of the draft name.
> 
> This came in handy recently in IPPM, where we had multiple
> proposals for a performance metrics registry that started
> pretty widely separated from each other. It would have been
> arbitrary and inaccurate simply to choose an author name for
> each the (individual draft) stages of the convergence; the
> resulting draft-manyfolks-ippm-metric-registry-00 is IMO
> accurately named. 
> 
> A policy strictly restricting element 2 to author names would
> have required us to waste energy on a "what do we want to name
> the band" discussion.

Brian,

I think this discussion will reach the point of diminishing
returns rather quickly, but I note that:

 - IPPM, or any other WG, has very little control over what an
I-D is called until it is accepted as a draft.  Until then, it
is formally an individual piece of work.  So "what do we want to
name the band" ought to be off-topic unless you want to provide
guidance as to what the draft will be called if the WG adopts
it... and then you get to mess only with what will come after 
  draft-ietf-WGNAME-

- No matter how many authors, collaborations, etc.., are
involved in a particular draft, someone has to push the "submit"
button (or send mail to the Secretariat) on the -00 version.
That individual is a pretty good approximation to "first author"
whether he or she is listed first in the header or not.   Note
that, that person is not listed in the headers and "author
addresses" section as an author, the document is headed for
manual submission anyway.

- The problem with "draft-manyfolks-" is that it is likely to
have an entirely different meaning in some other WG in some
other area than it does in IPPM than it does in IPPM.   Contrast
that with, e.g., some longstanding semi-organizations whose
membership is either constant or fairly well-defined (even if
nominally anonymous) such as draft-ymbk-...  Compared with
"draft-manyfolks-... draft-ABCDEF-..., where "ABCDEF" are the
first letters of the names of the major contributors, or
something similar.   Even if that is unique, I don't think that
(or draft-manyfolks-...) are helpful because, outside the WG,
they communicate no more useful information than
draft-anonymous-..., YMMD.  Of course, you could see if the
powers that be would be happy with "draft-IPPM-manyfolks..."
but, if you have gotten that far, why not just make it a WG
draft and be done with it?

best,
   john









From nobody Fri Feb 21 13:26:41 2014
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 885D61A0297 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 13:26:38 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 c4DarGZ75xYw for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 13:26:36 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 9A9291A0294 for <ietf@ietf.org>; Fri, 21 Feb 2014 13:26:36 -0800 (PST)
Received: from compute4.internal (compute4.nyi.mail.srv.osa [10.202.2.44]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C694E20F9C for <ietf@ietf.org>; Fri, 21 Feb 2014 16:26:31 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute4.internal (MEProxy); Fri, 21 Feb 2014 16:26:32 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=HmRQTreqE2gCCX+k3aciuD 6KpUs=; b=AtVfZLL2CrrzX3XpONE74FHGDESdarCnkozhf9wCL8YTHvcwezBP6e e+Ero9+HBRtJhzX7xlnuzesseC3xrZV8lNPYzCoftMsIizzWJYmFS6GUj6ETg7jA MdECeKud0tIrYI0QLK6JYvucwO5IwQrSSe2M7rP5tdcpSVGZ7DINk=
X-Sasl-enc: NrrFZihkFaPqC9c4w+7rl6BtFD5zO4g+WPusxhUi/fDR 1393017991
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id DE6C4C007AF; Fri, 21 Feb 2014 16:26:30 -0500 (EST)
Message-ID: <5307C481.50003@network-heretics.com>
Date: Fri, 21 Feb 2014 16:26:25 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: draft naming was RE: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk> <D8A2F939F08761DEFEEA946E@JcK-HP8200.jck.com> <53069808.3000903@gmail.com> <B0547AEF-6B17-495B-B87C-1381B640D038@trammell.ch>
In-Reply-To: <B0547AEF-6B17-495B-B87C-1381B640D038@trammell.ch>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VndQVIi1-SJx4CXVmNnaHTPDbd0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Feb 2014 21:26:38 -0000

On 02/21/2014 02:59 AM, Brian Trammell wrote:
> As long as (1) we have tools to map authors to documents for search and aggregation purposes anyway, (2) we maintain the reserved structure of draft-ietf-wg-* and other special second elements, I don't see any reason to further restrict the second element of the draft name.
>
> This came in handy recently in IPPM, where we had multiple proposals for a performance metrics registry that started pretty widely separated from each other. It would have been arbitrary and inaccurate simply to choose an author name for each the (individual draft) stages of the convergence; the resulting draft-manyfolks-ippm-metric-registry-00 is IMO accurately named.
>
> A policy strictly restricting element 2 to author names would have required us to waste energy on a "what do we want to name the band" discussion.

Agree.   We have too many piddly rules that serve little or no purpose 
already.    As long as neither the identifier nor the listed authors in 
the document are misleading, I don't see the need to impose further 
restrictions on them.

Keith


From nobody Fri Feb 21 13:51:39 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 2AA091A0274 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 13:51:37 -0800 (PST)
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 5qaI0hiUO3xS for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 13:51:35 -0800 (PST)
Received: from mail-ob0-x231.google.com (mail-ob0-x231.google.com [IPv6:2607:f8b0:4003:c01::231]) by ietfa.amsl.com (Postfix) with ESMTP id B4A171A0152 for <ietf@ietf.org>; Fri, 21 Feb 2014 13:51:35 -0800 (PST)
Received: by mail-ob0-f177.google.com with SMTP id wp18so4925081obc.22 for <ietf@ietf.org>; Fri, 21 Feb 2014 13:51:31 -0800 (PST)
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=B30cpV3fHnn8qo/flvh/vkyrRnBhphTiDNABHXoveIA=; b=KrqsN9ql1i8L04jq1pglyBHEOmDlHXxsYAjOnDIPh02Kllzonvaw3CisjtX5NPrXqr xPATxartGPxgh2cBGOJ0pLzkUKmYqF7yO5bUw9dV/+NTEizAl6n2FXvl+/J4aWU6Op1v Zs5QbvNBgKNbflFCF/SR3daO3DX1/+dbUueu8=
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=B30cpV3fHnn8qo/flvh/vkyrRnBhphTiDNABHXoveIA=; b=XSsjO6MIxxamOgrizuEkxgUJY6gGnhvtVYJPhQ3JbtJgICW+iA40VVM8Fl2msq0/Ti fJm//5HkrNQNaLKdBLf21k84OE6E6E+wkHsgg/7MZmBuyoy8tSIaEl/Do7TF1IDY+cR7 muAYeL4yD4qVTwaxUp86IZGztVISxElWjJab17Sj493LnIT9ZwmBlVlCGiW99B56YJE4 gkjyOBsD4pRCWJ/9X/UwzR6R6aj02Izg5wzF4BM6G35qh/XfU/hj0QIRspKDjSSYzejq wvTaPKduI450Vbs7BIHs48y9p868URdjtFi9En2rk4b6LmscJeLMj/re6J/XCuMUH9ZF KXEg==
X-Gm-Message-State: ALoCoQlzJn4/OiiU1+k5kk4Avm6PsjX4vyrxfLYpIsGFCt52B2Vnqi5bPiQ4MpTI8e7YgOKxeKkJ
MIME-Version: 1.0
X-Received: by 10.60.116.74 with SMTP id ju10mr12005099oeb.6.1393019491647; Fri, 21 Feb 2014 13:51:31 -0800 (PST)
Received: by 10.60.55.197 with HTTP; Fri, 21 Feb 2014 13:51:31 -0800 (PST)
In-Reply-To: <5307C481.50003@network-heretics.com>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk> <D8A2F939F08761DEFEEA946E@JcK-HP8200.jck.com> <53069808.3000903@gmail.com> <B0547AEF-6B17-495B-B87C-1381B640D038@trammell.ch> <5307C481.50003@network-heretics.com>
Date: Fri, 21 Feb 2014 21:51:31 +0000
Message-ID: <CAKHUCzzq9N3FVkYFjhhQnK9fRhPCKcFerU55w7mmxVFhmj1x1A@mail.gmail.com>
Subject: Re: draft naming was RE: anti-harassment procedures
From: Dave Cridland <dave@cridland.net>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=089e0116150af718a904f2f19ff1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/rtIR_3PUEpBLNLDbMOJgMr8E8c4
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: Fri, 21 Feb 2014 21:51:37 -0000

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

On Fri, Feb 21, 2014 at 9:26 PM, Keith Moore <moore@network-heretics.com>wrote:

> Agree.   We have too many piddly rules that serve little or no purpose
> already.    As long as neither the identifier nor the listed authors in the
> document are misleading, I don't see the need to impose further
> restrictions on them.


I feel very strongly, and furthermore I think it's perfectly self evident -
the form of a draft name, and the number of authors, and - most especially
- the way in which these authors are listed is of vital importance, and
there is no doubt in my mind whatsoever that I have something to say about
it. It's key to note, as a matter of principle.

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

<div dir=3D"ltr">On Fri, Feb 21, 2014 at 9:26 PM, Keith Moore <span dir=3D"=
ltr">&lt;<a href=3D"mailto:moore@network-heretics.com" target=3D"_blank">mo=
ore@network-heretics.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">Agree. =A0 We have too many piddly rules tha=
t serve little or no purpose already. =A0 =A0As long as neither the identif=
ier nor the listed authors in the document are misleading, I don&#39;t see =
the need to impose further restrictions on them.<span class=3D"HOEnZb"><fon=
t color=3D"#888888"></font></span></blockquote>
<div><br></div><div>I feel very strongly, and furthermore I think it&#39;s =
perfectly self evident - the form of a draft name, and the number of author=
s, and - most especially - the way in which these authors are listed is of =
vital importance, and there is no doubt in my mind whatsoever that I have s=
omething to say about it. It&#39;s key to note, as a matter of principle.<b=
r>
</div></div></div></div>

--089e0116150af718a904f2f19ff1--


From nobody Fri Feb 21 13:57:54 2014
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 244221A02DD for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 13:57:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 pqSTl3i_LEky for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 13:57:50 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id 947501A0286 for <ietf@ietf.org>; Fri, 21 Feb 2014 13:57:50 -0800 (PST)
Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 96BB32102A for <ietf@ietf.org>; Fri, 21 Feb 2014 16:57:46 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Fri, 21 Feb 2014 16:57:46 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type; s=smtpout; bh=B2fH /Ry385r8xLFvKzJvGFw7prc=; b=dsJp4xhaInh7t//uiciGaF6tXjhnvR/FqZ2j qv2Wswleg19jkfByruo5R5KmGvKLM7S9cu42EMDOxyJzBHabPD5uHAZ5wdO+lE/K +7CkVKxfJr9WnlonOZLpnY54g8G0HBlF+UPpcfZ5MBF+PMMjhcx/y9Y5Zj/WjUl6 2uNT3G0=
X-Sasl-enc: gId1ZBpHNJhcma8nWNdb04o/ymaOCUiGKEWoaH9PQTvU 1393019866
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id A5860C00005; Fri, 21 Feb 2014 16:57:45 -0500 (EST)
Message-ID: <5307CBD4.4020606@network-heretics.com>
Date: Fri, 21 Feb 2014 16:57:40 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Dave Cridland <dave@cridland.net>
Subject: Re: draft naming was RE: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net>	<290E20B455C66743BE178C5C84F1240847E6334724@EXMB01CMS.surrey.ac.uk>	<D8A2F939F08761DEFEEA946E@JcK-HP8200.jck.com>	<53069808.3000903@gmail.com>	<B0547AEF-6B17-495B-B87C-1381B640D038@trammell.ch>	<5307C481.50003@network-heretics.com> <CAKHUCzzq9N3FVkYFjhhQnK9fRhPCKcFerU55w7mmxVFhmj1x1A@mail.gmail.com>
In-Reply-To: <CAKHUCzzq9N3FVkYFjhhQnK9fRhPCKcFerU55w7mmxVFhmj1x1A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060004080201070008000700"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/4gSlQac1ZjTAcvrKOY1HPmpvBBg
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: Fri, 21 Feb 2014 21:57:53 -0000

This is a multi-part message in MIME format.
--------------060004080201070008000700
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 02/21/2014 04:51 PM, Dave Cridland wrote:
> On Fri, Feb 21, 2014 at 9:26 PM, Keith Moore 
> <moore@network-heretics.com <mailto:moore@network-heretics.com>> wrote:
>
>     Agree. We have too many piddly rules that serve little or no
>     purpose already.    As long as neither the identifier nor the
>     listed authors in the document are misleading, I don't see the
>     need to impose further restrictions on them.
>
>
> I feel very strongly, and furthermore I think it's perfectly self 
> evident - the form of a draft name, and the number of authors, and - 
> most especially - the way in which these authors are listed is of 
> vital importance, and there is no doubt in my mind whatsoever that I 
> have something to say about it. It's key to note, as a matter of 
> principle.
Silly me, I think the draft should be evaluated based on its content, 
rather than on who claims to have written it.

Keith


--------------060004080201070008000700
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 02/21/2014 04:51 PM, Dave Cridland
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAKHUCzzq9N3FVkYFjhhQnK9fRhPCKcFerU55w7mmxVFhmj1x1A@mail.gmail.com"
      type="cite">
      <div dir="ltr">On Fri, Feb 21, 2014 at 9:26 PM, Keith Moore <span
          dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:moore@network-heretics.com" target="_blank">moore@network-heretics.com</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">Agree. &nbsp;
              We have too many piddly rules that serve little or no
              purpose already. &nbsp; &nbsp;As long as neither the identifier nor
              the listed authors in the document are misleading, I don't
              see the need to impose further restrictions on them.<span
                class="HOEnZb"></span></blockquote>
            <div><br>
            </div>
            <div>I feel very strongly, and furthermore I think it's
              perfectly self evident - the form of a draft name, and the
              number of authors, and - most especially - the way in
              which these authors are listed is of vital importance, and
              there is no doubt in my mind whatsoever that I have
              something to say about it. It's key to note, as a matter
              of principle.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    Silly me, I think the draft should be evaluated based on its
    content, rather than on who claims to have written it.<br>
    <br>
    Keith<br>
    <br>
  </body>
</html>

--------------060004080201070008000700--


From nobody Fri Feb 21 17:02:19 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 D427F1A031E for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 17:02:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.439
X-Spam-Level: 
X-Spam-Status: No, score=-2.439 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, GB_I_LETTER=-2, RP_MATCHES_RCVD=-0.548, 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 vMWoUWQFH1Ko for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 17:02:14 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5AE1A030A for <ietf@ietf.org>; Fri, 21 Feb 2014 17:02:14 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.136.52]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1M11rkB013943 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 21 Feb 2014 17:02:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393030927; bh=f4zk81LDJFWrba3wuRWzyKUXqCqZwU5cxp/Job0CdK4=; h=Date:To:From:Subject:Cc; b=F1VuZ57OtxEmzDzU2XLtybou0+9LFRu9AIDo3gpU+PK9BpkDgJYH0V7GcY2xlK2EU W+W3LL3tXkYd+WogDCbrwpwTYJ6Jnu4RSuufc3M0gd1Ept9wSud57Ma9XUoArgEPWG 4tXFe4TkEZ1NP6z6uRUGV2C5pgxf8o1bm4h0+gC8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393030927; i=@elandsys.com; bh=f4zk81LDJFWrba3wuRWzyKUXqCqZwU5cxp/Job0CdK4=; h=Date:To:From:Subject:Cc; b=BGCV1qJxPZdR2Ga+AjqvFcdFoiLP25h0AgfI1XJX/yYLytpEQVVmX3XW4vNLOyfDC 7RCx7YbookcaqlUGYPCwTVORk7vDqdihSKrK+BwboFKc1zUkb4rw83Pzkzt0gt+a+v fKdhVySWkgkyzh6ewBmo1n8xR+BmM40Q/LZjK20g=
Message-Id: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 21 Feb 2014 16:09:51 -0800
To: Pete Resnick <presnick@qti.qualcomm.com>, Adrian Farrel <adrian@olddog.co.uk>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: IETF Anti-Harassment Procedures
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QhdnwlViFKZsEykWlUb4xjwMaDE
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, 22 Feb 2014 01:02:19 -0000

Hi Pete, Adrian,

I have a few comments about draft-farrresnickel-harassment-00.

In Section 1:

   'This sort of behavior, described in the IESG Statement on an "IETF
    Anti-Harassment Policy" [1], is not easily dealt with by our normal
    working group guidelines and procedures."

I assume that this intended BCP, if approved, will replace the 
above-mentioned policy.

   "These procedures are intended to be used when other IETF policies and
    procedures do not apply or have been ineffective."

The above sounds like government legislation where the law is used as 
a matter of convenience instead of the original intent.

   "Nothing in this document should be taken to interfere with the due
    process of law for the legal system under the jurisdiction of which
    any harassment takes place."

What does this mean?  Would an Area Director contact the authorities 
(e.g. 
http://www.hillingdon.gov.uk/article/20737/Anti-social-behaviour-racial-harassment 
) if there is reason to do so?

In Section 2:

   "This document does not attempt to precisely define behavior that
    falls under the set of procedures identified here.  In general,
    disruptive behavior that occurs in the context of an IETF general or
    working group mailing list, or happens in a face-to-face or virtual
    meeting of a working group or the IETF plenary, can be dealt with by
    our normal procedures, whereas harassing behavior that is
    interpersonal is more easily handled by the procedures described
    here."

For what it is worth, there was an interesting comment at 
http://www.ietf.org/mail-archive/web/diversity/current/msg00309.html 
There is a transcript of a (private) conversation at 
http://www.bbc.co.uk/news/world-europe-26079957  The swear word can 
also be heard in one of the IETF's audio recordings.  The point here 
is that it is a matter of context and culture.  Please note that I am 
not arguing for having a definition.

In Section 3.1:

   "The Ombudsperson is appointed by the IETF Chair.  The appointment is
    solely the responsibility of the IETF Chair although the Chair may
    choose to consult with the IESG, the IAB, and with ISOC.
    Furthermore, the IETF Chair may take opinion from the community.

    The IETF Chair may choose to solicit nominations or advertise the
    post.  This is entirely at the discretion of the IETF Chair.

    The IETF Chair is also free to decide how many people are needed to
    fill the role of Ombudsperson.  This may depend on the skillsets
    available, the work load, and the opinions of the seated
    Ombudsperson.  Furthermore, the IETF Chair may consider elements of
    diversity in making this decision."

It would be easier to write:

   The IETF Chair appoints the Ombudspersons.  The number of Ombudspersons
   appointed is at the discretion of the IETF Chair.

The quoted text mentions that the appointment is the sole 
responsibility of the IETF Chair and then gets into 
consultations.  The consultations part does not bring in any 
value.  The text mentions "may consider elements of 
diversity".  Either the entire appointment matter is at the 
discretion of the IETF Chair or it isn't.

In Section 3.2:

   "It is not expected that there will be candidates with all of the
    necessary ombudsperson skills and training who also have a clear
    understanding and familiarity with the IETF processes and culture.
    The Chair might choose someone with a great deal of professional
    experience evaluating and mediating harassment disputes, but little
    exposure to the IETF, or could select someone with more exposure to
    the IETF community, but without as much experience dealing with
    issues of harassment.  Since all of these attributes may be regarded
    by the IETF Chair as essential for an appointment, the IETF is
    committed to provide funding for necessary training for an appointed
    Ombudsperson."

As I read the above my first thought is that it has been drawn from a 
mindset of a particular country and having the person(s) trained to 
follow the values of that particular country.  That section comes out 
as satisfying some compliance requirement instead of trying to find 
someone who can be viewed as an acceptable mediator.

In Section 3.5:

   "The IETF Chair may remove a serving Ombudsperson before the end of
    their term without explanation to the community.  Such an action
    shall not be appealable.  See also Section 6."

That is not transparent at all.

I will defer my comments about Section 3.6.

It is understandable that the names of the parties involved (see 
Section 5) might have to be kept private.  However, keeping the cases 
secret opens the way for gossip or worse.  The approach comes out as 
hiding the issues in a closet instead of trying to find the balance 
between transparency and confidentiality.

In Section 6:

   "All elements of the appeal, including the fact of the appeal, will be
    held in confidence, but will be recorded and held securely for future
    reference."

Is this the IETF's version of a (U.S.) National Security Letter?

I suggest not having zen stuff in the Security Considerations section.

In my opinion the person who is subject to harassment is a victim and 
not a target.  The word "target" does not convey any empathy.  I am 
interested in reading other opinions  about the draft before taking a position.

Regards,
S. Moonesamy


From nobody Fri Feb 21 17:19:41 2014
Return-Path: <tterriberry@mozilla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FFF81A033C for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 17:19:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.056
X-Spam-Level: 
X-Spam-Status: No, score=-3.056 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_SORBS_WEB=0.77, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cKz3R_nboRF7 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 17:19:38 -0800 (PST)
Received: from smtp.mozilla.org (mx1.corp.phx1.mozilla.com [63.245.216.69]) by ietfa.amsl.com (Postfix) with ESMTP id 1FC861A032A for <ietf@ietf.org>; Fri, 21 Feb 2014 17:19:37 -0800 (PST)
Received: from [10.250.6.54] (corp-240.mv.mozilla.com [63.245.220.240]) (Authenticated sender: tterriberry@mozilla.com) by mx1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id 88E87F2F16; Fri, 21 Feb 2014 17:19:33 -0800 (PST)
Message-ID: <5307FB25.8040806@mozilla.com>
Date: Fri, 21 Feb 2014 17:19:33 -0800
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:19.0) Gecko/20100101 SeaMonkey/2.16.2
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>,  "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net>
In-Reply-To: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@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/JexivQcLIdj5pw-2gNyDuVubYgA
Cc: "adrian@olddog.co.uk Farrel" <adrian@olddog.co.uk>, 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: Sat, 22 Feb 2014 01:19:40 -0000

Jari Arkko wrote:
> I know this topic is hard to discuss. Hopefully there are very
> few situations where these procedures are needed, but they are
> needed. I thank you for your help and respectful input into this
> difficult but important discussion.

I want to thank the authors, and the Chair, for doing the work to define 
a harassment policy. Even if it is never used, the fact that it exists 
demonstrates a commitment to dealing with harassment complaints in a 
prompt and fair fashion, and that has a positive effect.

>     This document does not attempt to precisely define behavior that
>     falls under the set of procedures identified here.  In general,

In my view, a successful harassment policy needs to do two things:
1) Clearly establish what is unacceptable behavior.
2) Clearly indicate whom to go to for help.

Section 4 satisfies (2) adequately. This statement, however, indicates 
that you are punting on (1). Earlier, the draft references 
<http://www.ietf.org/iesg/statement/ietf-anti-harassment-policy.html>, 
which uses much more definitive language on what constitutes harassment. 
I would hope we could get IETF consensus on language of that nature, 
defining what is clearly unacceptable, even if we wish to make 
allowances for culture and leave some room for gray areas and borderline 
cases.


From nobody Fri Feb 21 18:41:33 2014
Return-Path: <moore@network-heretics.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDDE01A036E for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 18:41:29 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 vWwngUwyUsjo for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 18:41:27 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by ietfa.amsl.com (Postfix) with ESMTP id AF40E1A0368 for <ietf@ietf.org>; Fri, 21 Feb 2014 18:41:27 -0800 (PST)
Received: from compute5.internal (compute5.nyi.mail.srv.osa [10.202.2.45]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 06B3320AAA for <ietf@ietf.org>; Fri, 21 Feb 2014 21:41:23 -0500 (EST)
Received: from frontend1 ([10.202.2.160]) by compute5.internal (MEProxy); Fri, 21 Feb 2014 21:41:23 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=w9245MmfvBrWNuPNcfTmpx Io4e4=; b=Xh/Tul4TgFkwDlKfi6ocJo0rl5nFz9q4nmw2AkcKnMOAr2TXfnz+6+ ROLBVCZISFh5aCGoYr/gOfXSScEMOXheeZpQ+ZKzAFt2y3WN/bGb3/3snjCljUrM QkjutcSMVqDHwxjWDysVF6jsgsl6nb7AfRmuei1P2t7UVCYLygNQQ=
X-Sasl-enc: qwd7PUPKkbRJYL2x6+Vt6nsE5rMKK9ucVItlnDDjd8Lf 1393036882
Received: from [192.168.1.4] (unknown [65.16.145.177]) by mail.messagingengine.com (Postfix) with ESMTPA id 689B5C0000C; Fri, 21 Feb 2014 21:41:22 -0500 (EST)
Message-ID: <53080E4C.9060602@network-heretics.com>
Date: Fri, 21 Feb 2014 21:41:16 -0500
From: Keith Moore <moore@network-heretics.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <5307FB25.8040806@mozilla.com>
In-Reply-To: <5307FB25.8040806@mozilla.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/297ecHLfMrvF0bUsFpLBjR9jbEY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Feb 2014 02:41:30 -0000

On 02/21/2014 08:19 PM, Timothy B. Terriberry wrote:
> In my view, a successful harassment policy needs to do two things:
> 1) Clearly establish what is unacceptable behavior.
> 2) Clearly indicate whom to go to for help.
>
> Section 4 satisfies (2) adequately. This statement, however, indicates 
> that you are punting on (1). Earlier, the draft references 
> <http://www.ietf.org/iesg/statement/ietf-anti-harassment-policy.html>, 
> which uses much more definitive language on what constitutes 
> harassment. I would hope we could get IETF consensus on language of 
> that nature, defining what is clearly unacceptable, even if we wish to 
> make allowances for culture and leave some room for gray areas and 
> borderline cases.
While I understand the desire to do (1), in my experience with 
discussing harassment policies in other organizations it has been a 
rathole, or at least a slippery slope.   While it's not too hard to 
identify a few obviously harassing or abusive behaviors, it can be very 
hard to draw a bright line between acceptable and unacceptable behaviors 
in general.   Simple policies seem to work much better than complicated 
ones.

Keith


From nobody Fri Feb 21 20:03: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 9C37E1A0388 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 20:03:51 -0800 (PST)
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 veyP3h-KoM01 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 20:03:50 -0800 (PST)
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 D586F1A02E4 for <ietf@ietf.org>; Fri, 21 Feb 2014 20:03:49 -0800 (PST)
Received: (qmail 76929 invoked from network); 22 Feb 2014 04:03:44 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 22 Feb 2014 04:03: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=530821a0.xn--i8sz2z.k1402; i=johnl@user.iecc.com; bh=SXwpSIMLt+xTnbZTIH4vX8w4YpR8ol9pK93srv8MHfg=; b=AdX2ER6EQzncgv7bqwgrU4HCpVcA4s+fEhQwO1Z/VriZN6AHI3KjQXYKSoROjd8KiwJ+Hp+Q5K7+m7z6fYGtXBMRnhvxK/JXdcJCvGizW5YU9XjkXv3+NOa+J3j2Fl8Ho9spN4myN/KJALpAOv5lM6Bemc+6bcZlmK1emG2jc58HAJBO2Jqm4moPJl8pag/Obl3Jl3BHXAgB+Xr95etRva2pnSzKBml5gBWLFborZufsygNEK8Qq1CAa5Tjy0W9Q
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=530821a0.xn--i8sz2z.k1402; bh=SXwpSIMLt+xTnbZTIH4vX8w4YpR8ol9pK93srv8MHfg=;  b=JRlWmkNhkmyY2soHk+xUXw3mwniRnN7GjB+MOVbBzkDX/0wSg03Ah0vdmRnORwVzNFYEq7A128tSxaWFMj+H1eJx6B3quqa/Vr62C2wO0Hc4KudKLy4vltRcP68FSRWSBIGisQifu8JUaUQ5vmThaGXtxTmbw5vP/TSI9ZVn05vw7Uy0QT3pqXcigByw+cDzSeqWAqmYxCv9YaZbNA/TFlViGtrJc8caVK5NwQTeWanEPYvXB3m/s+97UV2WbwAW
Date: 22 Feb 2014 04:03:22 -0000
Message-ID: <20140222040322.30798.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: anti-harassment procedures
In-Reply-To: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.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/7gfVVNM39zw-Vzo8ZqpAVeKaI8E
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Feb 2014 04:03:51 -0000

The process looks fine, if a bit overspecified.  I have some concern
about the choice of ombudsman*, given the extremely poor experience I
had with ICANN's ombudsman a few years back, although the lack of pay
will certainly discourage careerism.

My larger concern is that you need at least some general descriptions
of what would constitute harassment to keep it from being too
arbitrary.  It seems to me that the essence of harassment is unwanted
attention directed to an individual or small group of individuals.  If
the target told the harasser to stop and he continued, that makes the
claim more credible, although there are surely situations where the
situation is threatening enough that it's reasonable not to respond at
the time.

A few general guidelines like that would make the policy a lot more
concrete, and avoid "how could I know X would take that as
harassment?" issues.

R's,
John

* - ombudsperson is unacceptably species-ist, while ombudsman is a
Swedish legal term from the 1950s


From nobody Fri Feb 21 20:40: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 3B0821A039F for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 20:40:14 -0800 (PST)
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 zE-FqwSQvxiW for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 20:40:11 -0800 (PST)
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 DA8B31A01CC for <ietf@ietf.org>; Fri, 21 Feb 2014 20:40:11 -0800 (PST)
Received: by mail-pa0-f52.google.com with SMTP id bj1so4332719pad.39 for <ietf@ietf.org>; Fri, 21 Feb 2014 20:40:07 -0800 (PST)
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=nfeKKaOkd8SgyrTq0xTAfN1pf/bbBuIIVzb3N5YV+eg=; b=HY/1sJ7JfIF2SZ/2OLpnR6vrPXsw2EtpgimcmDY2NtqgwVpLnRBTddtfn3rQc9V2lw +dhBTrDuSSZgGuDRrP4jdhgqDEo/QBJFWmN0adW/8AM+E2ebZY1dKiA41RyyLBJo5z8r +TfgHckqHVzVAea+oCqU+szfi6wRbtUUOECt2VD7AuxZDCvdCBHClW8XLsW2XdSqIZ8p xfFzPBbMUGB4SOZRKqZ6UdTVO/54zuMFrYfGZwUpd8+P+wRV+69lWGZ8SXPXb7PBto+W aeryNjpUjDOs6w3Jdwk94iQaFfVHFCok7SjXU0zoy5rOjGKD7g7mcauSktfdyLE+fpyT RytA==
X-Received: by 10.68.179.98 with SMTP id df2mr9319092pbc.51.1393044007882; Fri, 21 Feb 2014 20:40:07 -0800 (PST)
Received: from [192.168.178.23] (130.192.69.111.dynamic.snap.net.nz. [111.69.192.130]) by mx.google.com with ESMTPSA id nv7sm26794674pbc.31.2014.02.21.20.40.05 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 21 Feb 2014 20:40:07 -0800 (PST)
Message-ID: <53082A34.8040202@gmail.com>
Date: Sat, 22 Feb 2014 17:40:20 +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 Levine <johnl@taugh.com>
Subject: Re: anti-harassment procedures
References: <20140222040322.30798.qmail@joyce.lan>
In-Reply-To: <20140222040322.30798.qmail@joyce.lan>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/x3w2z52OlpdLTv1icNKbEqxtOW0
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, 22 Feb 2014 04:40:14 -0000

On 22/02/2014 17:03, John Levine wrote:
> The process looks fine, if a bit overspecified.  I have some concern
> about the choice of ombudsman*, given the extremely poor experience I
> had with ICANN's ombudsman a few years back, although the lack of pay
> will certainly discourage careerism.
> 
> My larger concern is that you need at least some general descriptions
> of what would constitute harassment to keep it from being too
> arbitrary. 

Yes, I'm afraid that deferring that to an IESG statement isn't
satisfactory; I would assume that at some point the IESG would
update its statement to point to this document, rather than
the other way round. Having the definition split between two
places is the surely the worst solution.


> It seems to me that the essence of harassment is unwanted
> attention directed to an individual or small group of individuals.

One difficulty is that what is "unwanted" is very sensitive
to cultural and linguistic subtleties. Also, if (for example) I
were to repeatedly point out substantive errors in somebody's
IETF work, or even syntax errors in their English, where is the
line between legitimate discussion and review and objectionable
harassment?

I don't think that saying the behaviour is "unwanted" by the
target is sufficient. It needs to be clearly directed at the person
and not at the work, and it needs to be "hostile or intimidating"
as well as unwelcome (as in the IESG statement). But even so,
there's always going to be judgment involved. As long as we have
checks and balances as proposed, I don't see a better approach than
an ombudsman (or something very similar).

http://www.ombudsmanassociation.org/about-the-role-of-an-ombudsman.php

   Brian

> If
> the target told the harasser to stop and he continued, that makes the
> claim more credible, although there are surely situations where the
> situation is threatening enough that it's reasonable not to respond at
> the time.
> 
> A few general guidelines like that would make the policy a lot more
> concrete, and avoid "how could I know X would take that as
> harassment?" issues.
> 
> R's,
> John
> 
> * - ombudsperson is unacceptably species-ist, while ombudsman is a
> Swedish legal term from the 1950s
> 
> 


From nobody Sat Feb 22 00:48:35 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 A3E871A0104 for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 00:48:32 -0800 (PST)
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 Oa0LmNSDR_b7 for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 00:48:30 -0800 (PST)
Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) by ietfa.amsl.com (Postfix) with ESMTP id 119FD1A001A for <ietf@ietf.org>; Sat, 22 Feb 2014 00:48:29 -0800 (PST)
Received: by mail-yk0-f177.google.com with SMTP id q200so8748977ykb.8 for <ietf@ietf.org>; Sat, 22 Feb 2014 00:48:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:cc:content-type;  bh=gpPGjvyZNKf4FcKBafTAtBwh9qhfx1uooWWwNpKeZq8=; b=tfq2gDbC7Y9aJ8y9vlgr2sbo13WlWhuez2c92KJGWxBXtOXw6H4eOh3pKnKCR3Hk5p v8+10yTQNmFTKiQGM3xkXRCi/LdZtF3kAzUJQP3JqI/v4Zrcqrlr1Uu/9H1jaedlBneJ AE9U8DJTQ2IurKcNY+EqtMvxejDskBeo/t3Zv5l4oTFGx7Sgwq0+QuHNSLBUZ6GPScRb pZ8F1NSW/cr64RKtqJpQx1eWJX0Y9jK8rAr6aqZByAYqqdYIa6lJUwDtfNWKi3pX5LhT JGsRbJVJcHbOvf/k5OgpU4BAK/8XWvfSPBTGwkUt4RMh+XVEiLzwek3vpBIbR6DZ/Y5Y pU1A==
MIME-Version: 1.0
X-Received: by 10.236.83.66 with SMTP id p42mr16491008yhe.90.1393058905791; Sat, 22 Feb 2014 00:48:25 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Sat, 22 Feb 2014 00:48:25 -0800 (PST)
Date: Sat, 22 Feb 2014 09:48:25 +0100
Message-ID: <CADnDZ8_DBSAq4bwZnEPWOHcqrhFrCjburoBrotztoZxtcDegJg@mail.gmail.com>
Subject: Social activities under societies (was Re: anti-harassment procedures
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Keith Moore <moore@network-heretics.com>
Content-Type: multipart/alternative; boundary=90e6ba47613b3b3a3804f2facda7
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/baaOy_Dl0gouHQ6l6OyNi3JAGm0
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, 22 Feb 2014 08:48:32 -0000

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

Hi Keith

My comments below,

On Saturday, February 22, 2014, Keith Moore wrote:

> On 02/21/2014 08:19 PM, Timothy B. Terriberry wrote:
>
>> In my view, a successful harassment policy needs to do two things:
>> 1) Clearly establish what is unacceptable behavior.
>> 2) Clearly indicate whom to go to for help.
>>
>> Section 4 satisfies (2) adequately. This statement, however, indicates
>> that you are punting on (1).
>>
>
IMHO the Requirement 1 is a must, to give good reasons for some penalties.


> While I understand the desire to do (1), in my experience with discussing
> harassment policies in other organizations it has been a rathole, or at
> least a slippery slope.


Yes, but only because societies still don't solve it when interacting with
other cultures or minorities. Usually organisations should build a strong
culture related to its vision and policies. In countries,
organisations, universities, etc. they encourage establishing
of clubs/societies to make people interact under social goals or
activities (do we have social societies in IETF?) I think that is missing
or I am not aware because was remotely working.

I know that there is a social event in meetings and hopefully will try to
join if I get availability time in this meeting.


> While it's not too hard to identify a few obviously harassing or abusive
> behaviors, it can be very hard to draw a bright line between acceptable and
> unacceptable behaviors in general.


Yes it is very hard for engineers, so we need external advise which is very
good for this best practice work.

>

> Simple policies seem to work much better than complicated ones.


Yes but if the harassing problem is complicated with many
variable parameters, there is no simple best solution for that. Intelligent
or wise solutions are best and IMHO they are complicated which may need
someone with large experience to achieve.

I like that the authors are very well experts with IETF experience but if
we get an additional author with different experience it will help. I
recommend the authors to get advise some experts outside IETF as
from universities. This problem is never can be solved by expert engineers
without social science experts ;-)

Thanks,

AB

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

<div>Hi Keith</div><div><br></div><div>My comments below,</div><div><br></d=
iv>On Saturday, February 22, 2014, Keith Moore  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">
On 02/21/2014 08:19 PM, Timothy B. Terriberry wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In my view, a successful harassment policy needs to do two things:<br>
1) Clearly establish what is unacceptable behavior.<br>
2) Clearly indicate whom to go to for help.<br>
<br>
Section 4 satisfies (2) adequately. This statement, however, indicates that=
 you are punting on (1).=A0<br>
</blockquote></blockquote><div><br></div><div>IMHO the=A0Requirement 1 is a=
 must, to give good reasons for some=A0penalties.=A0</div><div>=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">

While I understand the desire to do (1), in my experience with discussing h=
arassment policies in other organizations it has been a rathole, or at leas=
t a slippery slope. =A0=A0</blockquote><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
</blockquote><div><br></div><div>Yes, but only because societies still don&=
#39;t solve it when interacting with other cultures=A0or minorities.=A0Usua=
lly organisations should build a strong culture related to its vision and=
=A0policies. In countries, organisations,=A0universities, etc. they encoura=
ge establishing of=A0clubs/societies to make people interact under social g=
oals or activities=A0(do we have social=A0societies in IETF?) I think that =
is missing or I am not aware because was remotely working.=A0</div>
<div><br></div><div>I know that there is a social event in meetings and hop=
efully will try to join if I get availability time in this meeting.=A0</div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">
While it&#39;s not too hard to identify a few obviously harassing or abusiv=
e behaviors, it can be very hard to draw a bright line between acceptable a=
nd unacceptable behaviors in general. =A0=A0</blockquote><div><br></div><di=
v>
Yes it is very hard for engineers, so we need external advise which is very=
 good for this best practice work.=A0=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"></blockquote>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Simple policies seem to work m=
uch better than complicated ones.</blockquote><div><br></div><div>Yes but i=
f the harassing=A0problem is complicated with many variable=A0parameters, t=
here is no simple best=A0solution for that. Intelligent or wise solutions=
=A0are best and IMHO they are complicated which may need someone with large=
 experience to achieve.=A0</div>
<div><br></div><div>I like that the authors are very well experts with IETF=
 experience but if we get an additional author with different experience it=
 will help.=A0I recommend the authors to get=A0advise some experts outside =
IETF as from=A0universities. This problem is never can be solved by expert =
engineers without social science experts=A0;-)</div>
<div><br></div><div>Thanks,</div><div><br></div><div>AB</div>

--90e6ba47613b3b3a3804f2facda7--


From nobody Sat Feb 22 06:50:13 2014
Return-Path: <sama.digitalpolicy@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 B1C041A00F0 for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 06:50:10 -0800 (PST)
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 60Mi4YojW1Em for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 06:50:07 -0800 (PST)
Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5ABFC1A00ED for <ietf@ietf.org>; Sat, 22 Feb 2014 06:50:07 -0800 (PST)
Received: by mail-ig0-f179.google.com with SMTP id r1so1590652igi.0 for <ietf@ietf.org>; Sat, 22 Feb 2014 06:50:03 -0800 (PST)
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=YfKIegW8KLQNJVw6aZb55/FS/pSIL/VBZ8/Mu127cxc=; b=FiRFal1Iw73H7M7jCUMS2d5/qgMWAYzgV673+dxRrSZarnD1rCuKjoBhoKc/k47JJn zwMFV3HFR+jaVSEwwiD8Y9LMIEBcqYIq+f0cF2kEweMJoKzSyXX1efL7M/yQiRZerKWI B3D7UJFnrDC3c5jKmOzFkzBNuFOuYaf850QJB9Jy0elOpGgODg+iRArPDaiH8HUfbcnk GIjCQV0oehz5mev252FThWdasu4ubOQdh/exbaooyRX1dD/vdnPgC6Cs77jNvtCaoT82 SWY+v0XcpKZTIMhZXdlNanWBb89rd6pTrUZfmQmbYlIb+amYlVopvc6WgqKvHuh1Azdx YPUg==
MIME-Version: 1.0
X-Received: by 10.50.79.166 with SMTP id k6mr5299670igx.47.1393080603006; Sat, 22 Feb 2014 06:50:03 -0800 (PST)
Sender: sama.digitalpolicy@gmail.com
Received: by 10.50.178.235 with HTTP; Sat, 22 Feb 2014 06:50:02 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com>
References: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com>
Date: Sat, 22 Feb 2014 15:50:02 +0100
X-Google-Sender-Auth: 5qnp_x-iJpC9OjiNBQeD3fstLIk
Message-ID: <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@mail.gmail.com>
Subject: Re: IETF Anti-Harassment Procedures
From: Andrea Glorioso <andrea@digitalpolicy.it>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=089e013a114e7c5d7304f2ffda51
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CK1V2WRRiDROo24dA4WWz6JG6u8
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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: Sat, 22 Feb 2014 14:50:10 -0000

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

Hi,

On Saturday, February 22, 2014, S Moonesamy <sm+ietf@elandsys.com> wrote:

>
>   "These procedures are intended to be used when other IETF policies and
>    procedures do not apply or have been ineffective."
>
> The above sounds like government legislation where the law is used as a
> matter of convenience instead of the original intent.


Could you please clarify / expand on what you mean exactly?


>   "Nothing in this document should be taken to interfere with the due
>    process of law for the legal system under the jurisdiction of which
>    any harassment takes place."
>
> What does this mean?  Would an Area Director contact the authorities (e.g.
> http://www.hillingdon.gov.uk/article/20737/Anti-social-
> behaviour-racial-harassment ) if there is reason to do so?


The passage seems quite clear to me. An IETF document (whatever its nature)
cannot trump applicable laws. In some countries / jurisdictions, especially
when certain forms of harassment are a criminal offense, not informing
authorities might be itself a violation of the law. The trick is of course
knowing which particular law / legal system would apply. That's not
something that can be solved in this document, though.

So, I guess the answer to your question would be "it depends".

In my opinion the person who is subject to harassment is a victim and not a
> target.  The word "target" does not convey any empathy.
>

Well said.

Best,

Andrea




-- 

--
I speak only for myself. Sometimes I do not even agree with myself. Keep it
in mind.
Twitter: @andreaglorioso
Facebook: https://www.facebook.com/andrea.glorioso
LinkedIn: http://www.linkedin.com/profile/view?id=1749288&trk=tab_pro

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

Hi,<br><br>On Saturday, February 22, 2014, S Moonesamy &lt;<a href=3D"mailt=
o:sm%2Bietf@elandsys.com">sm+ietf@elandsys.com</a>&gt; wrote:<div>=A0<block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">
=A0 &quot;These procedures are intended to be used when other IETF policies=
 and<br>
=A0 =A0procedures do not apply or have been ineffective.&quot;<br>
<br>
The above sounds like government legislation where the law is used as a mat=
ter of convenience instead of the original intent.</blockquote><div><br></d=
iv>Could you please clarify / expand on what you mean exactly?<br><div>
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex">
=A0 &quot;Nothing in this document should be taken to interfere with the du=
e<br>
=A0 =A0process of law for the legal system under the jurisdiction of which<=
br>
=A0 =A0any harassment takes place.&quot;<br>
<br>
What does this mean? =A0Would an Area Director contact the authorities (e.g=
. <a href=3D"http://www.hillingdon.gov.uk/article/20737/Anti-social-behavio=
ur-racial-harassment" target=3D"_blank">http://www.hillingdon.gov.uk/<u></u=
>article/20737/Anti-social-<u></u>behaviour-racial-harassment</a> ) if ther=
e is reason to do so?</blockquote>
<div><br></div><div>The passage seems quite clear to me. An IETF document (=
whatever its=A0nature) cannot trump applicable laws. In some countries / ju=
risdictions, especially when certain forms of harassment are a criminal off=
ense, not informing authorities might be itself a violation of the law. The=
 trick is of course knowing which particular law / legal system would apply=
. That&#39;s not something that can be solved in this document, though.=A0<=
/div>
<div><br></div><div>So, I guess the answer to your question would be &quot;=
it depends&quot;.=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">In =
my opinion the person who is subject to harassment is a victim and not a ta=
rget. =A0The word &quot;target&quot; does not convey any empathy.<br>
</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"></blockquote><div><br></div><di=
v>Well said.=A0</div><div><br></div><div>Best,</div><div><br></div><div>And=
rea=A0</div>
<div>=A0</div><br></div><br><br>-- <br><br>--<br>I speak only for myself. S=
ometimes I do not even agree with myself. Keep it in mind.<br>Twitter: @and=
reaglorioso<br>Facebook: <a href=3D"https://www.facebook.com/andrea.glorios=
o" target=3D"_blank">https://www.facebook.com/andrea.glorioso</a><br>
LinkedIn: <a href=3D"http://www.linkedin.com/profile/view?id=3D1749288&amp;=
trk=3Dtab_pro" target=3D"_blank">http://www.linkedin.com/profile/view?id=3D=
1749288&amp;trk=3Dtab_pro</a><br>

--089e013a114e7c5d7304f2ffda51--


From nobody Sat Feb 22 11:05:24 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 50C3E1A00D7 for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 11:05:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, 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 fzHc-wsu4I-v for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 11:05:20 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id ED3501A00C2 for <ietf@ietf.org>; Sat, 22 Feb 2014 11:05:19 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.136.237]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1MJ4nIY028411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 22 Feb 2014 11:05:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393095906; bh=gfs5HVkZBLk8GeUTZ0+JmgiGYjK/63Q2hnSw3Moq0dY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=fcTDuF8uvK2AvBUTYbmmvQ/UYITai5JiEk7UMlgmw5qguQHKllmvMxaYplTm+RW2E UMwi5GOyAuK/ruPxss85JWmhshs3MqiFwDJJvwkrgqpFiKu1Rmjqe2GZR4JTuovZ8A UGGgaQgP0fErv84sb4jtuCM7F16/H2rjQKz0H2ao=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393095906; i=@elandsys.com; bh=gfs5HVkZBLk8GeUTZ0+JmgiGYjK/63Q2hnSw3Moq0dY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ioevA5WnfoyFHRe1QfwklFxcVZjPh80NgdmBSpAerU/1K29a4VrJPVL1KiGnXhLOB 3m3agGFB4kNjIlrTA9DDjnNwHweSzY0P0eUtvtwZH0a9r87Wyp044pJhQRmJbNRgnb bZUXzDiDunO8xFk0vw4Hx8BseYiATEZw2L3T9WNU=
Message-Id: <6.2.5.6.2.20140222080001.0d7a85e0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 22 Feb 2014 09:39:35 -0800
To: Andrea Glorioso <andrea@digitalpolicy.it>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IETF Anti-Harassment Procedures
In-Reply-To: <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@mail.g mail.com>
References: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com> <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@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/tfQEw38_tlulStzzIrSKh-KQoKk
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@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: Sat, 22 Feb 2014 19:05:22 -0000

Hi Andrea,
At 06:50 22-02-2014, Andrea Glorioso wrote:
>Could you please clarify / expand on what you mean exactly?

The end of the sentence is about using the procedures in 
draft-farrresnickel-harassment-00 when other procedures have been 
ineffective.  As such it allows the procedures to be invoked when the 
other procedures did not produce the desired results.

My preference is to use this intended BCP when a case of harassment 
is reported.  If it a case of, for example, me being rude to you, 
that can be addressed through existing BCPs (unless it is reported as 
harassment).  I prefer not to see this intended BCP used as a 
threat.  That avoids having to get into a lengthy security 
consideration discussion about the misuse of the intended BCP.

>The passage seems quite clear to me. An IETF document (whatever its 
>nature) cannot trump applicable laws. In some countries / 
>jurisdictions, especially when certain forms of harassment are a 
>criminal offense, not informing authorities might be itself a 
>violation of the law. The trick is of course knowing which 
>particular law / legal system would apply. That's not something that 
>can be solved in this document, though.

The question was about whether an Area Director would inform the 
authorities.  There was a question from Fred Baker during a previous 
discussion about the same topic ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg83398.html 
).  There wasn't any response to that question.

As a comment for the Area Directors, 
http://www.ietf.org/iesg/statement/ietf-anti-harassment-policy.html 
has the following:

   "If you believe you have been harassed, notice that someone else is being
    harassed, or have any other concerns, you are encouraged to raise your
    concern in confidence with one of the Ombudspersons."

There isn't any information about who the Ombudspersons are or how to 
contact them.

Regards,
S. Moonesamy  


From nobody Sat Feb 22 13:21:54 2014
Return-Path: <tterriberry@mozilla.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16C0B1A018D for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 13:21:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.826
X-Spam-Level: 
X-Spam-Status: No, score=-3.826 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R20pXc3E_ze8 for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 13:21:50 -0800 (PST)
Received: from smtp.mozilla.org (mx1.corp.phx1.mozilla.com [63.245.216.69]) by ietfa.amsl.com (Postfix) with ESMTP id 27B681A0180 for <ietf@ietf.org>; Sat, 22 Feb 2014 13:21:49 -0800 (PST)
Received: from [172.17.0.43] (50-78-100-113-static.hfc.comcastbusiness.net [50.78.100.113]) (Authenticated sender: tterriberry@mozilla.com) by mx1.mail.corp.phx1.mozilla.com (Postfix) with ESMTPSA id 5445BF2252; Sat, 22 Feb 2014 13:21:45 -0800 (PST)
Message-ID: <530914E8.9040001@mozilla.com>
Date: Sat, 22 Feb 2014 13:21:44 -0800
From: "Timothy B. Terriberry" <tterriberry@mozilla.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:25.0) Gecko/20100101 SeaMonkey/2.22.1
MIME-Version: 1.0
To: Keith Moore <moore@network-heretics.com>, ietf@ietf.org
Subject: Re: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <5307FB25.8040806@mozilla.com> <53080E4C.9060602@network-heretics.com>
In-Reply-To: <53080E4C.9060602@network-heretics.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CuQQ7hm1bs54QIusij5C4-7XnNQ
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Feb 2014 21:21:52 -0000

Keith Moore wrote:
>> harassment. I would hope we could get IETF consensus on language of
>> that nature, defining what is clearly unacceptable, even if we wish to
>> make allowances for culture and leave some room for gray areas and
>> borderline cases.
> [snip]
> rathole, or at least a slippery slope.   While it's not too hard to
> identify a few obviously harassing or abusive behaviors, it can be very
> hard to draw a bright line between acceptable and unacceptable behaviors
> in general.   Simple policies seem to work much better than complicated

I agree completely. That is why I suggested we do the former and not the 
latter.


From nobody Sat Feb 22 13:31: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 D5AE01A0186 for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 13:31:26 -0800 (PST)
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 Py2bjvJWyfUq for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 13:31:25 -0800 (PST)
Received: from mail-yk0-x231.google.com (mail-yk0-x231.google.com [IPv6:2607:f8b0:4002:c07::231]) by ietfa.amsl.com (Postfix) with ESMTP id 24EAC1A0180 for <ietf@ietf.org>; Sat, 22 Feb 2014 13:31:25 -0800 (PST)
Received: by mail-yk0-f177.google.com with SMTP id q200so10095486ykb.8 for <ietf@ietf.org>; Sat, 22 Feb 2014 13:31:19 -0800 (PST)
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=6yPDrRrowfsm0afjuQ5HoteNH1MEZ7Zp+2W+JA+68rk=; b=ssfUJdTfAB6b42cxqkOJnhu0Jjn46qM0YOUksVazujA6mDQwzqLYnfYfQ4C1hwl/B2 Zg86/R9pXSY569Cm29ytwLxUAPHERzIX42OrM7aU1OqXwAdWSarzbX3Di6koGMPGTg8K rRWvZ3lOfRiS99rezpnZQrB4VQ4w15ZEs1sikBD9UXpz+UeMPewjPA0t6oaXGtHxjVia OsnzNHQ7+Z3SaLiR6NScDgTx6tEuj4CSblzsXEZSvVoHPA3S6EIwp7XOaChgvkZ45Kgg rWeRW14WdSAc63J24QZUm6bRuJ2YSodvnEc73ngAEvKeNCjURxwfoxxd9lfq9eWnEvvA uEbQ==
MIME-Version: 1.0
X-Received: by 10.236.72.40 with SMTP id s28mr20115776yhd.160.1393104679694; Sat, 22 Feb 2014 13:31:19 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Sat, 22 Feb 2014 13:31:19 -0800 (PST)
In-Reply-To: <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@mail.gmail.com>
References: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com> <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@mail.gmail.com>
Date: Sat, 22 Feb 2014 22:31:19 +0100
Message-ID: <CADnDZ893aXfZ7LZkUhuZ4REbc676wtH1_cQ7HKZr8XnfE7Aebw@mail.gmail.com>
Subject: IETF Anti-Harassment Procedures
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf300513149176e004f30575a6
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_Sp8vOv_QDZSfHA7M211PgnpPIc
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, S Moonesamy <sm+ietf@elandsys.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: Sat, 22 Feb 2014 21:31:27 -0000

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

On Saturday, February 22, 2014, Andrea Glorioso wrote:

> Hi,
>
> On Saturday, February 22, 2014, S Moonesamy
>
>> In my opinion the person who is subject to harassment is a victim and not
>> a target.  The word "target" does not convey any empathy.
>>
>
> Well said.
>
>
IMHO, Target is suitable term with responder and  reporter, we never no who
is the real victim sometimes if no witnesses.  After investigation we get
to know if target is victim. If you assume witnesses available then
"victim" is the right word replacing "target" but still we need to change
the other two terms.

AB

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

<br><br>On Saturday, February 22, 2014, Andrea Glorioso  wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Hi,<br><br>On Saturday, February 22, 2014, S Moonesa=
my=A0<span></span><div>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">In my opinion the person who is subject to h=
arassment is a victim and not a target. =A0The word &quot;target&quot; does=
 not convey any empathy.<br>


</blockquote><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex"></blockquote><div><br></div><di=
v>Well said.=A0</div><div><br></div></div></blockquote><div><br></div><div>=
IMHO,=A0Target is=A0suitable term=A0with=A0responder and=A0=A0reporter,=A0w=
e never no who is the real victim sometimes if no witnesses. =A0After inves=
tigation we get to know if target is victim.=A0If you assume witnesses avai=
lable=A0then &quot;victim&quot;=A0is the right word replacing &quot;target&=
quot;=A0but still we need to change the other two=A0terms.=A0</div>
<div>=A0</div><div>AB</div>

--20cf300513149176e004f30575a6--


From nobody Sat Feb 22 14:14: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 9E8111A019A for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 14:14:03 -0800 (PST)
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 gd63nESMxENa for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 14:14:00 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D4CCC1A015E for <ietf@ietf.org>; Sat, 22 Feb 2014 14:14:00 -0800 (PST)
Received: from [192.168.1.71] (99-88-197-253.lightspeed.sndgca.sbcglobal.net [99.88.197.253]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1MMDqXT011583 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sat, 22 Feb 2014 14:13:56 -0800
Message-ID: <530920EB.1030505@dcrocker.net>
Date: Sat, 22 Feb 2014 14:12:59 -0800
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.3.0
MIME-Version: 1.0
To: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>
Subject: Basic Issues  (was Re: anti-harassment procedures)
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net>
In-Reply-To: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.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, 22 Feb 2014 14:13:56 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/blZ3Dv6KSC2EpPGk0XyyhOPMSRc
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: Sat, 22 Feb 2014 22:14:03 -0000

Kudos to Adrian and Pete for working on this and producing a thoughtful 
proposal.


I'm separating my comments, and will limit this initial posting to a few 
basic issues.  I'll post pickier quibbles later...



Summary:

      Although reasonable by many measures, the proposal needs more 
complete specification of the standing Ombud function.  It also needs a 
different appeals body.



Background:

      I believe the primary goal, in the IETF's having and processing 
harassment complaints, is to ensure that the IETF is legitimately 
inviting to the widest possible range of participants, and hence to 
encourage their active participation.

      Groups with more diversity produce better work.  Groups that 
suffer harassment of participants inherently reduce real diversity.

      In spite of the IETF's long history of open participation, the 
fact is that daily IETF life often includes explicit and implicit 
tolerance of various forms of harassment.

      The new anti-harassment policy sets quite a good foundation for 
changing this.


However as challenging as it is to produce a policy statement, it is far 
easier than figuring out how to produce a practical implementation of 
the policy...



The Details:

This topic is quite foreign to the experience, skill set and even 
perspective of most IETF participants, touching delicate and painful 
legal and personnel management issues.  Anyone put in a position of 
handling a harassment report needs training, coupled with expert advice. 
  Raw intelligence and good intentions are not enough.

(On the other hand, the principal actors in a harassment complaint are 
not employees of the IETF.  So there might be some additional degrees of 
freedom in the way that IETF-related complaints are handled, compared 
with what a regular company has to do.)


0. Defining Harassment

I think the IESG Statement provides extended text defining and 
describing harassment that is quite reasonable, in tone and scope.  The 
text should be incorporated into an IETF-approved document, which is 
what I'm hoping Adrian and Pete's draft becomes.


1. Ombud Formation

I believe the most critical bit of core work for handling a report of 
harassment is to already have a well-defined and stable Ombud function, 
with good community understanding of the function and approval for it. 
The proposal defers the substance of this issue to the IETF Chair. 
While the Chair is probably the right function for overseeing formation 
of the Ombud, the framework for the office should not be left to the 
vagaries of whoever happens to be Chair and whatever they happen to 
think right at one moment or another.

So the Ombud function needs to be formally defined and according to 
community approval, not merely community review.  Hence the requirements 
and details for the function need separate and stable specification, 
with community support around it.  Then the IETF Chair can reasonably be 
asked to implement it.

It is tempting to suggest assigning the Ombud function to a senior human 
resources professional.

However they will not have the experience with the IETF culture and are, 
instead, likely to apply a classic corporate model for responding to 
harassment complaints, which sometimes includes worrying more about 
protecting the company than about ensuring appropriate handling of 
actual abuse.

So it is better to rest the responsibility for Ombud work on the 
shoulders of experienced IETF volunteers.


2. Appeal

It's reasonable to consider the IESG or IAB as an appeals review board, 
since they already have some IETF appeals responsibilities.  However 
harassment reports call on completely different expertise and completely 
different dynamics.  They also require far greater confidentiality and 
sensitivity than is reasonable to demand from the IESG or IAB.


So, here's a modified proposal...


1. Setup

      a. Formulate a standing Complaints Committee -- called the Ombud 
-- of 3 IETF volunteers.  This is small enough to make efficient and 
coherent workings workings more likely, along with maintain a reasonable 
degree of confidentiality.

      b. Give them the relevant professional manager's training in 
handling harassment complaints.

      c. Recruit a professional HR harassment adviser and a 
harassment-savvy attorney, to act as advisers.


2. Processing:

      a.  On receiving a report, the committee works with the Reporter, 
Target and Respondent to formulate a sanitized summary of the complaint 
and 'defense'.  This will be used if there is an appeal.  It also will 
serve to get the involved parties to focus on the essential details. The 
wordsmithing goal of the sanitization is to produce a version that can 
be shown outside of this initial group.  Possibly only an appeals 
committee but possibly even public.

      b.  The Ombud works with the principals to assess the claimed 
offense and formulate responses they deem appropriate.

      c.  The Ombud modifies the sanitized writeup to include a 
sanitized summary of the decision.

      d.  If any of the principals wishes, they can appeal the Ombud's 
decision. Appeal is to the ISOC Board of Trustees.



3. Appeals:

      For a topic like this, I think one level of appeal is sufficient 
and that the sensitive personnel and legal aspects of this topic warrant 
restricting who is involved, including choosing a venue that already has 
legal strictures in place.  Hence the ISOC Board, rather than the IESG.



4. Addendum:

I'll offer one more item I think basic to discussion of this topic.  For 
now I'm not suggesting specific wording changes, but do want to 
circulate the key point, because I think it has a profound effect upon 
one's thinking about harassment.

We typically think of harassment as being a problem only for the 
Respondent and the Target.  However there is a third, critical 
participant:  The rest of us.

I'll offer a precept that we need to keep in mind:

      Harassment behavior does not merely create a hostile work
      environment for the target(s).

      It creates it for everyone.

To the extent that participants watch others get treated badly and do 
not then see the misbehavior get corrected, there is chilling effect 
across the IETF.


Again, thanks to you both for working on this.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sat Feb 22 16:52:18 2014
Return-Path: <john@jlc.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 326D71A020B for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 16:52:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level: 
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id j2Hiuck7ohS7 for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 16:52:12 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id D65501A01ED for <ietf@ietf.org>; Sat, 22 Feb 2014 16:52:11 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 72643C9509; Sat, 22 Feb 2014 19:52:04 -0500 (EST)
Date: Sat, 22 Feb 2014 19:52:04 -0500
From: John Leslie <john@jlc.net>
To: dcrocker@bbiw.net
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
Message-ID: <20140223005204.GW54716@verdi>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <530920EB.1030505@dcrocker.net>
User-Agent: Mutt/1.4.1i
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/85mKltRjagU7v0Xoyi5TJc0WrtU
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, "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: Sun, 23 Feb 2014 00:52:15 -0000

Dave Crocker <dhc@dcrocker.net> wrote:
> 
> Although reasonable by many measures, the proposal needs more 
> complete specification of the standing Ombud function. It also needs
> a different appeals body.

   I agree with Dave.

> This topic is quite foreign to the experience, skill set and even 
> perspective of most IETF participants, touching delicate and painful 
> legal and personnel management issues.  Anyone put in a position of 
> handling a harassment report needs training, coupled with expert
> advice. 

   I am not familiar with what is available in the way of training;
but I am quite sure that no amount of training will remove the need
for occasional expert advice.

> 1. Ombud Formation
> 
> I believe the most critical bit of core work for handling a report of 
> harassment is to already have a well-defined and stable Ombud function, 
> with good community understanding of the function and approval for it. 

   +1

> The proposal defers the substance of this issue to the IETF Chair. 
> While the Chair is probably the right function for overseeing formation 
> of the Ombud, the framework for the office should not be left to the 
> vagaries of whoever happens to be Chair and whatever they happen to 
> think right at one moment or another.

   I tend to agree with Dave; but my immediate reaction was, "The IETF
Chair function already covers too much. Perhaps Jari can handle it,
but we shouldn't put this much work on IETF chairs thal follow him."

> So the Ombud function needs to be formally defined and according to 
> community approval, not merely community review.

   "Community approval" is judged by the IESG now -- what I see as
important is that we not ask the IESG to propose the changes as we go.

> Hence the requirements and details for the function need separate
> and stable specification, 

   +1

> with community support around it.

   Whatever...

> Then the IETF Chair can reasonably be asked to implement it.

   We really should limit the workload upon future IETF chairs. (I see
nothing wrong with Jari appointing the first Ombud-whatevers.)

> So it is better to rest the responsibility for Ombud work on the 
> shoulders of experienced IETF volunteers.

   Agreed.

> 2. Appeal
> 
> It's reasonable to consider the IESG or IAB as an appeals review board, 
> since they already have some IETF appeals responsibilities.  However 
> harassment reports call on completely different expertise and completely 
> different dynamics.  They also require far greater confidentiality and 
> sensitivity than is reasonable to demand from the IESG or IAB.

   Perhaps the IAB could manage this, but I strongly recommend against
asking the IESG to handle such appeals; and the IAB doesn't feel right
either...

> So, here's a modified proposal...
> 
> 1. Setup
> 
>   a. Formulate a standing Complaints Committee -- called the Ombud 
>      -- of 3 IETF volunteers. This is small enough to make efficient
>      and coherent workings workings more likely, along with maintain a
>      reasonable degree of confidentiality.

   +1

>   b. Give them the relevant professional manager's training in 
>      handling harassment complaints.

   (Someone has to define what that includes. While I trust Jari to
come up with a reasonable definition, I suggest that the definition
be published before appointing the initial board.)

>   c. Recruit a professional HR harassment adviser and a 
>      harassment-savvy attorney, to act as advisers.

   I don't know how hard that will be, but it sounds like a very good
idea.

> 2. Processing:
> 
>   a. On receiving a report, the committee works with the Reporter, 
>      Target and Respondent to formulate a sanitized summary of the
>      complaint and 'defense'.

    I strongly recommend the committee be responsible for re-stating
the complaint, and hopefully the response. Re-stating in clear terms
is often critical to finding a path to resolution.

>      This will be used if there is an appeal.

   It will be essential to establishing a basis for considering an
appeal within the IETF.

>      It also will serve to get the involved parties to focus on the
>      essential details.

   That may be optimistic, but IMHO _some_ basis for shared focus is
essential to the process.

>      The wordsmithing goal of the sanitization is to produce a version
>      that can be shown outside of this initial group.

   This is not always necessary, or even possible; but when practical,
it _will_ be helpful.

>      Possibly only an appeals committee but possibly even public.

   IMHO, even what is shown to an appeals committee needs to be agreed
to by the parties; and the initial re-statement shouldn't require such
agreement.

>   b. The Ombud works with the principals to assess the claimed 
>      offense and formulate responses they deem appropriate.

   +1

>   c. The Ombud modifies the sanitized writeup to include a 
>      sanitized summary of the decision.
> 
>   d. If any of the principals wishes, they can appeal the Ombud's 
>      decision. Appeal is to the ISOC Board of Trustees.

   Appeal directly to ISOC BoT seems reasonable to me. If this becomes
a problem, they seem the right group to propose an alternative.

   Note that none of this concerns the content of RFCs or architecture
of the Internet; so I see no reason to involve the IAB (and I'm quite
opposed to involving the IESG).

> 3. Appeals:
> 
>    For a topic like this, I think one level of appeal is sufficient 
> and that the sensitive personnel and legal aspects of this topic warrant 
> restricting who is involved, including choosing a venue that already has 
> legal strictures in place.  Hence the ISOC Board, rather than the IESG.

   +1

--
John Leslie <john@jlc.net>


From nobody Sat Feb 22 19:56:05 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 46CB11A02D9 for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 19:56:03 -0800 (PST)
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 DoY61vkinlrg for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 19:56:00 -0800 (PST)
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 B3E5C1A02D4 for <ietf@ietf.org>; Sat, 22 Feb 2014 19:56:00 -0800 (PST)
Received: by mail-pd0-f182.google.com with SMTP id v10so4878085pde.41 for <ietf@ietf.org>; Sat, 22 Feb 2014 19:55:56 -0800 (PST)
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=apQfB88yXtnEf7xg8GlAvoalyeKzz7WvxI2Qp4cprKM=; b=IWktWh2i3VkFHGyoIk//RBuoIkfIbAW79a7p0j4WWHJmGbIfvAPGkuQ4OIhj6t5beA Yzw9h70WrCv8GouDdvNnhd4UveOMHtGI3AAqRhxLYORPNSIN1RimTNy2NMfBCfGqfNWQ zZ2Re/0rAm32E6L/bs6Sc+1kZjyxJ1avzTfRVlLTIlJT+uJdZwieHMWaGkKNmqthfKOg zDYnKmCyhqz+/yqC3i9hvneCYt4JiY3tnIGrlai9flPRgd7aI/KFZXIsC5MovfpfhQHS kuXwuZ2XQi5rBaQpyS1+FMoXpw40yXaj1CFvkuDBDnqVVYqAm3MS7/XwX5e2w/shh6Yy R08g==
X-Received: by 10.68.7.66 with SMTP id h2mr6115467pba.91.1393127756028; Sat, 22 Feb 2014 19:55:56 -0800 (PST)
Received: from [192.168.178.23] (158.199.69.111.dynamic.snap.net.nz. [111.69.199.158]) by mx.google.com with ESMTPSA id nv7sm36164233pbc.31.2014.02.22.19.55.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 22 Feb 2014 19:55:55 -0800 (PST)
Message-ID: <53097147.6090409@gmail.com>
Date: Sun, 23 Feb 2014 16:55:51 +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: dcrocker@bbiw.net
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net>
In-Reply-To: <530920EB.1030505@dcrocker.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/OQgHn7Qm6_KH7yH2RN5mm8ReM-Y
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, "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: Sun, 23 Feb 2014 03:56:03 -0000

I too agree with most of Dave's comments. Just a few remarks below:

On 23/02/2014 11:12, Dave Crocker wrote:
...
> It is tempting to suggest assigning the Ombud function to a senior human
> resources professional.
> 
> However they will not have the experience with the IETF culture and are,
> instead, likely to apply a classic corporate model for responding to
> harassment complaints, which sometimes includes worrying more about
> protecting the company than about ensuring appropriate handling of
> actual abuse.
> 
> So it is better to rest the responsibility for Ombud work on the
> shoulders of experienced IETF volunteers.

However, if we end up with an Ombudsteam, I think it would
be worthwhile to find someone with real-life experience in this
area, but outside the IETF, as a member of the team.

...
>      b. Give them the relevant professional manager's training in
> handling harassment complaints.
> 
>      c. Recruit a professional HR harassment adviser and a
> harassment-savvy attorney, to act as advisers.

I am not so sure you want people with an HR background. As I read
http://www.ombudsmanassociation.org/about-the-role-of-an-ombudsman.php,
we are slightly misreading the classical role of an Ombudsman;
that's fine, but we do need advisers or team members with dispute-resolution
and mediation experience.

Also - an attorney familiar with the laws of which jurisdiction
(including the laws of trans-border harassment)? I think counsel
would have to be identified case-by-case, if needed.
...

>      For a topic like this, I think one level of appeal is sufficient
> and that the sensitive personnel and legal aspects of this topic warrant
> restricting who is involved, including choosing a venue that already has
> legal strictures in place.  Hence the ISOC Board, rather than the IESG.

Just a note that up to now, we have strictly reserved the ISOC Board
route for claims that our "procedures themselves ... are claimed
to be inadequate or insufficient to the protection of the
rights of all parties." While I think taking the appeals in a
harassment claim right out of the normal checks and balances
is reasonable (and much better than a system where the "management
chain" can protect its own misbehaviour by bouncing appeals), it
should be noted as a significant change.

> 
> 
> 
> 4. Addendum:
> 
> I'll offer one more item I think basic to discussion of this topic.  For
> now I'm not suggesting specific wording changes, but do want to
> circulate the key point, because I think it has a profound effect upon
> one's thinking about harassment.
> 
> We typically think of harassment as being a problem only for the
> Respondent and the Target.  However there is a third, critical
> participant:  The rest of us.

Related to that, the language needs to include cases where either
the Target or the Respondent is a group of people. Group harassment
is not unknown.

    Brian


From nobody Sat Feb 22 23:16:41 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 134D01A035F for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 23:16:39 -0800 (PST)
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 x4xM58RDZEik for <ietf@ietfa.amsl.com>; Sat, 22 Feb 2014 23:16:35 -0800 (PST)
Received: from mail-yh0-x229.google.com (mail-yh0-x229.google.com [IPv6:2607:f8b0:4002:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 189221A035D for <ietf@ietf.org>; Sat, 22 Feb 2014 23:16:34 -0800 (PST)
Received: by mail-yh0-f41.google.com with SMTP id f73so4089600yha.0 for <ietf@ietf.org>; Sat, 22 Feb 2014 23:16:30 -0800 (PST)
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=pBpYJtZQgKgoCz7srOLeUQ3jlD0tpPs8JZI5S6nOIEQ=; b=nvbHPqUQgt3NDgQcMIiGlosgW6+b4xsawAgx4HAkm+igsgeEI1+7z5U9CAX2RKE14q RQdkK9z7eA8FNovpwAgB5DMgdOlwLeHJBhrkHIWYSI7lw9DBeLKCYBr6RMUG7MP83V5n qKrojQis+XrpdawGd8uuUqjnYCky3YuUg3228C+nTUjoD5z0MUqhT1TVtdojv+nFCvHa 7L+PJcspqWkrS5ccGOfFGHNjuwkRJ/HO96zVVcN+CtuvjNYGqvsxpDKd+DJmlm44xNlv Ddgad9sseKo5fFBjosMC8GZ1QGFPCwqIoxcwQ8D7HJtblWTwNANhEP41xbSLaKTZFecY NEMA==
MIME-Version: 1.0
X-Received: by 10.236.123.193 with SMTP id v41mr21696397yhh.68.1393139790473;  Sat, 22 Feb 2014 23:16:30 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Sat, 22 Feb 2014 23:16:29 -0800 (PST)
In-Reply-To: <530920EB.1030505@dcrocker.net>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net>
Date: Sun, 23 Feb 2014 08:16:29 +0100
Message-ID: <CADnDZ89VnZWwtmH5hSv-oSjJ2oG=VNGV+9dnPJzaYeDOTFKD7Q@mail.gmail.com>
Subject: Re: Basic Issues (was Re: anti-harassment procedures)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=20cf301afb7b556e4204f30da247
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Qsgh3H2oH1F-2q3IHpN3pMDvivk
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, "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: Sun, 23 Feb 2014 07:16:39 -0000

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

Hi Dave,

I support your comments and suggestions. However, I have few
comments/suggestions below,

On Saturday, February 22, 2014, Dave Crocker wrote:

> Kudos to Adrian and Pete for working on this and producing a thoughtful
> proposal.
>
>
> I'm separating my comments, and will limit this initial posting to a few
> basic issues.  I'll post pickier quibbles later...
>
>
>
> Summary:
>
>      Although reasonable by many measures, the proposal needs more
> complete specification of the standing Ombud function.  It also needs a
> different appeals body.
>
>
>
> Background:
>
>      I believe the primary goal, in the IETF's having and processing
> harassment complaints, is to ensure that the IETF is legitimately inviting
> to the widest possible range of participants, and hence to encourage their
> active participation.
>
>      Groups with more diversity produce better work.  Groups that suffer
> harassment of participants inherently reduce real diversity.


Groups should have the IETF vision repeated in meeting as the note well,
because many WGs may forget that.


>      In spite of the IETF's long history of open participation, the fact
> is that daily IETF life often includes explicit and implicit tolerance of
> various forms of harassment.
>
>      The new anti-harassment policy sets quite a good foundation for
> changing this.
>
>
> However as challenging as it is to produce a policy statement, it is far
> easier than figuring out how to produce a practical implementation of the
> policy...
>
>
>
> The Details:
>
> This topic is quite foreign to the experience, skill set and even
> perspective of most IETF participants, touching delicate and painful legal
> and personnel management issues.  Anyone put in a position of handling a
> harassment report needs training, coupled with expert advice.  Raw
> intelligence and good intentions are not enough.
>
> (On the other hand, the principal actors in a harassment complaint are not
> employees of the IETF.  So there might be some additional degrees of
> freedom in the way that IETF-related complaints are handled, compared with
> what a regular company has to do.)
>
>
> 0. Defining Harassment
>
> I think the IESG Statement provides extended text defining and describing
> harassment that is quite reasonable, in tone and scope.  The text should be
> incorporated into an IETF-approved document, which is what I'm hoping
> Adrian and Pete's draft becomes.
>
>
> 1. Ombud Formation
>
> I believe the most critical bit of core work for handling a report of
> harassment is to already have a well-defined and stable Ombud function,
> with good community understanding of the function and approval for it. The
> proposal defers the substance of this issue to the IETF Chair. While the
> Chair is probably the right function for overseeing formation of the Ombud,
> the framework for the office should not be left to the vagaries of whoever
> happens to be Chair and whatever they happen to think right at one moment
> or another.
>
> So the Ombud function needs to be formally defined and according to
> community approval, not merely community review.  Hence the requirements
> and details for the function need separate and stable specification, with
> community support around it.  Then the IETF Chair can reasonably be asked
> to implement it.
>
> It is tempting to suggest assigning the Ombud function to a senior human
> resources professional.
>
> However they will not have the experience with the IETF culture and are,
> instead, likely to apply a classic corporate model for responding to
> harassment complaints, which sometimes includes worrying more about
> protecting the company than about ensuring appropriate handling of actual
> abuse.
>
> So it is better to rest the responsibility for Ombud work on the shoulders
> of experienced IETF volunteers.
>
>
> 2. Appeal
>
> It's reasonable to consider the IESG or IAB as an appeals review board,
> since they already have some IETF appeals responsibilities.  However
> harassment reports call on completely different expertise and completely
> different dynamics.  They also require far greater confidentiality and
> sensitivity than is reasonable to demand from the IESG or IAB.
>
>
> So, here's a modified proposal...
>
>
> 1. Setup
>
>      a. Formulate a standing Complaints Committee -- called the Ombud --
> of 3 IETF volunteers.  This is small enough to make efficient and coherent
> workings workings more likely, along with maintain a reasonable degree of
> confidentiality.
>
>      b. Give them the relevant professional manager's training in handling
> harassment complaints.
>
>      c. Recruit a professional HR harassment adviser and a
> harassment-savvy attorney, to act as advisers.


We may not need to recruit (May get costly) we can outsourcing contract as
pay per file, which I don't believe in IETF we will get more than 2
reported harassing per year, but if I am wrong even after the draft
approved then you point is the right advice to IETF managers to look at the
financial costs trade offs.

>
>
> 2. Processing:
>
>      a.  On receiving a report, the committee works with the Reporter,
> Target and Respondent to formulate a sanitized summary of the complaint and
> 'defense'.  This will be used if there is an appeal.  It also will serve to
> get the involved parties to focus on the essential details. The
> wordsmithing goal of the sanitization is to produce a version that can be
> shown outside of this initial group.  Possibly only an appeals committee
> but possibly even public.
>
>      b.  The Ombud works with the principals to assess the claimed offense
> and formulate responses they deem appropriate.
>
>      c.  The Ombud modifies the sanitized writeup to include a sanitized
> summary of the decision.
>
>      d.  If any of the principals wishes, they can appeal the Ombud's
> decision. Appeal is to the ISOC Board of Trustees.
>
>
>
> 3. Appeals:
>
>      For a topic like this, I think one level of appeal is sufficient and
> that the sensitive personnel and legal aspects of this topic warrant
> restricting who is involved, including choosing a venue that already has
> legal strictures in place.  Hence the ISOC Board, rather than the IESG.


Your very right, ISOC rather than IESG, because IESG were selected mostly
for technical engineering work/problem not social  problem.

>
>
>
> 4. Addendum:
>
> I'll offer one more item I think basic to discussion of this topic.  For
> now I'm not suggesting specific wording changes, but do want to circulate
> the key point, because I think it has a profound effect upon one's thinking
> about harassment.
>
> We typically think of harassment as being a problem only for the
> Respondent and the Target.  However there is a third, critical participant:
>  The rest of us.


Yes I agree and already pointed in my comments posted previously that there
are two targets not one.


>
> I'll offer a precept that we need to keep in mind:
>
>      Harassment behavior does not merely create a hostile work
>      environment for the target(s).
>
>      It creates it for everyone.
>
> To the extent that participants watch others get treated badly and do not
> then see the misbehavior get corrected, there is chilling effect across the
> IETF.


I seen that happen once public misbehaving in one WG and I told my AD
related about that, but he said it was solved privately  but still I was a
target and while I was remotely participating I felt that I am targeted
also, so decided not to become face to face participant in 2012 (now my
first come will be in few days).


>
> Again, thanks to you both for working on this.


Thanks to you and all participants that are working together to solve IETF
problems. If we all work together and respect each other all
times in working and not working, then we will have best documents produced
and published.

AB

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

Hi Dave,<div><br></div><div>I support your comments and suggestions. Howeve=
r, I have few comments/suggestions below,<br><br>On Saturday, February 22, =
2014, Dave Crocker  wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Kudos to Adrian and Pete for working on this and producing a thoughtful pro=
posal.<br>
<br>
<br>
I&#39;m separating my comments, and will limit this initial posting to a fe=
w basic issues. =A0I&#39;ll post pickier quibbles later...<br>
<br>
<br>
<br>
Summary:<br>
<br>
=A0 =A0 =A0Although reasonable by many measures, the proposal needs more co=
mplete specification of the standing Ombud function. =A0It also needs a dif=
ferent appeals body.<br>
<br>
<br>
<br>
Background:<br>
<br>
=A0 =A0 =A0I believe the primary goal, in the IETF&#39;s having and process=
ing harassment complaints, is to ensure that the IETF is legitimately invit=
ing to the widest possible range of participants, and hence to encourage th=
eir active participation.<br>

<br>
=A0 =A0 =A0Groups with more diversity produce better work. =A0Groups that s=
uffer harassment of participants inherently reduce real diversity.</blockqu=
ote><div><br></div><div>Groups should have the IETF vision repeated in meet=
ing as the note well, because many=A0WGs may=A0forget that.=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">
<br>
=A0 =A0 =A0In spite of the IETF&#39;s long history of open participation, t=
he fact is that daily IETF life often includes explicit and implicit tolera=
nce of various forms of harassment.<br>
<br>
=A0 =A0 =A0The new anti-harassment policy sets quite a good foundation for =
changing this.<br>
<br>
<br>
However as challenging as it is to produce a policy statement, it is far ea=
sier than figuring out how to produce a practical implementation of the pol=
icy...<br>
<br>
<br>
<br>
The Details:<br>
<br>
This topic is quite foreign to the experience, skill set and even perspecti=
ve of most IETF participants, touching delicate and painful legal and perso=
nnel management issues. =A0Anyone put in a position of handling a harassmen=
t report needs training, coupled with expert advice. =A0Raw intelligence an=
d good intentions are not enough.<br>

<br>
(On the other hand, the principal actors in a harassment complaint are not =
employees of the IETF. =A0So there might be some additional degrees of free=
dom in the way that IETF-related complaints are handled, compared with what=
 a regular company has to do.)<br>

<br>
<br>
0. Defining Harassment<br>
<br>
I think the IESG Statement provides extended text defining and describing h=
arassment that is quite reasonable, in tone and scope. =A0The text should b=
e incorporated into an IETF-approved document, which is what I&#39;m hoping=
 Adrian and Pete&#39;s draft becomes.<br>

<br>
<br>
1. Ombud Formation<br>
<br>
I believe the most critical bit of core work for handling a report of haras=
sment is to already have a well-defined and stable Ombud function, with goo=
d community understanding of the function and approval for it. The proposal=
 defers the substance of this issue to the IETF Chair. While the Chair is p=
robably the right function for overseeing formation of the Ombud, the frame=
work for the office should not be left to the vagaries of whoever happens t=
o be Chair and whatever they happen to think right at one moment or another=
.<br>

<br>
So the Ombud function needs to be formally defined and according to communi=
ty approval, not merely community review. =A0Hence the requirements and det=
ails for the function need separate and stable specification, with communit=
y support around it. =A0Then the IETF Chair can reasonably be asked to impl=
ement it.<br>

<br>
It is tempting to suggest assigning the Ombud function to a senior human re=
sources professional.<br>
<br>
However they will not have the experience with the IETF culture and are, in=
stead, likely to apply a classic corporate model for responding to harassme=
nt complaints, which sometimes includes worrying more about protecting the =
company than about ensuring appropriate handling of actual abuse.<br>

<br>
So it is better to rest the responsibility for Ombud work on the shoulders =
of experienced IETF volunteers.<br>
<br>
<br>
2. Appeal<br>
<br>
It&#39;s reasonable to consider the IESG or IAB as an appeals review board,=
 since they already have some IETF appeals responsibilities. =A0However har=
assment reports call on completely different expertise and completely diffe=
rent dynamics. =A0They also require far greater confidentiality and sensiti=
vity than is reasonable to demand from the IESG or IAB.<br>

<br>
<br>
So, here&#39;s a modified proposal...<br>
<br>
<br>
1. Setup<br>
<br>
=A0 =A0 =A0a. Formulate a standing Complaints Committee -- called the Ombud=
 -- of 3 IETF volunteers. =A0This is small enough to make efficient and coh=
erent workings workings more likely, along with maintain a reasonable degre=
e of confidentiality.<br>

<br>
=A0 =A0 =A0b. Give them the relevant professional manager&#39;s training in=
 handling harassment complaints.<br>
<br>
=A0 =A0 =A0c. Recruit a professional HR harassment adviser and a harassment=
-savvy attorney, to act as advisers.</blockquote><div><br></div><div>We may=
 not need to recruit (May get=A0costly) we=A0can outsourcing contract as pa=
y per file, which I don&#39;t believe in IETF we will get more than 2 repor=
ted=A0harassing per year,=A0but if I am wrong even after the draft approved=
 then you point is the right advice to IETF managers to look at the financi=
al costs trade offs.=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
<br>
2. Processing:<br>
<br>
=A0 =A0 =A0a. =A0On receiving a report, the committee works with the Report=
er, Target and Respondent to formulate a sanitized summary of the complaint=
 and &#39;defense&#39;. =A0This will be used if there is an appeal. =A0It a=
lso will serve to get the involved parties to focus on the essential detail=
s. The wordsmithing goal of the sanitization is to produce a version that c=
an be shown outside of this initial group. =A0Possibly only an appeals comm=
ittee but possibly even public.<br>

<br>
=A0 =A0 =A0b. =A0The Ombud works with the principals to assess the claimed =
offense and formulate responses they deem appropriate.<br>
<br>
=A0 =A0 =A0c. =A0The Ombud modifies the sanitized writeup to include a sani=
tized summary of the decision.<br>
<br>
=A0 =A0 =A0d. =A0If any of the principals wishes, they can appeal the Ombud=
&#39;s decision. Appeal is to the ISOC Board of Trustees.<br>
<br>
<br>
<br>
3. Appeals:<br>
<br>
=A0 =A0 =A0For a topic like this, I think one level of appeal is sufficient=
 and that the sensitive personnel and legal aspects of this topic warrant r=
estricting who is involved, including choosing a venue that already has leg=
al strictures in place. =A0Hence the ISOC Board, rather than the IESG.</blo=
ckquote>
<div><br></div><div>Your very right, ISOC rather than IESG, because IESG we=
re selected mostly for technical engineering work/problem=A0not social=A0=
=A0problem.=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
<br>
<br>
4. Addendum:<br>
<br>
I&#39;ll offer one more item I think basic to discussion of this topic. =A0=
For now I&#39;m not suggesting specific wording changes, but do want to cir=
culate the key point, because I think it has a profound effect upon one&#39=
;s thinking about harassment.<br>

<br>
We typically think of harassment as being a problem only for the Respondent=
 and the Target. =A0However there is a third, critical participant: =A0The =
rest of us.</blockquote><div><br></div><div>Yes I agree and=A0already point=
ed in my comments posted previously=A0that there are two targets not one.=
=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<br>
I&#39;ll offer a precept that we need to keep in mind:<br>
<br>
=A0 =A0 =A0Harassment behavior does not merely create a hostile work<br>
=A0 =A0 =A0environment for the target(s).<br>
<br>
=A0 =A0 =A0It creates it for everyone.<br>
<br>
To the extent that participants watch others get treated badly and do not t=
hen see the misbehavior get corrected, there is chilling effect across the =
IETF.</blockquote><div><br></div><div>I seen that happen once public misbeh=
aving=A0in one WG and I told my AD related about that, but he said it was s=
olved privately=A0=A0but still I was a target and while I was remotely part=
icipating I felt that I am targeted also, so decided not to become face to =
face participant in 2012 (now my first come will be in few days).=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">
<br>
<br>
Again, thanks to you both for working on this.</blockquote><div><br></div><=
div>Thanks to you and all participants that are working together to solve I=
ETF problems. If we all=A0work together and respect each other all times=A0=
in=A0working and not working,=A0then we will have best documents produced a=
nd published.=A0</div>
<div><br></div><div>AB</div></div>

--20cf301afb7b556e4204f30da247--


From nobody Sun Feb 23 01:23:12 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 76FEA1A0428 for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 01:23:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.938
X-Spam-Level: 
X-Spam-Status: No, score=-0.938 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, 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 5Eqt1mwbRuMl for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 01:23:01 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 511071A042E for <ietf@ietf.org>; Sun, 23 Feb 2014 01:22:50 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.152.195]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1N9MLNW025526 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 23 Feb 2014 01:22:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393147361; bh=d9GPRze9rZur/dKKBCMPP4em43TPZNxj0Z4Y4Km08ts=; h=Date:To:From:Subject:In-Reply-To:References; b=Marq7flatB+aRvIf7JGgB5+tEkr6Qe978wJxdWoyAOsn444Jgjjk7KPMUqaLaVzgd asNXcOBAfZCU6T9p+taOXWrUr9bcDQFgwUjM2ojNZgPD1gK3FSDBStMiDIvx3gvfha E0SmWfnmdw6nsAn2JfBpkFD4TxnBkWmQDSu2742s=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393147361; i=@elandsys.com; bh=d9GPRze9rZur/dKKBCMPP4em43TPZNxj0Z4Y4Km08ts=; h=Date:To:From:Subject:In-Reply-To:References; b=B5EI3IZHqdtq9fuOuLuY1SYtsbx8YljtA/EjLfjtUoTGdCwVswddPyGf/318GULWQ saVq3uAHhCPDdLjqqIMZ5a2ewFniForioZoVoJlxFr/yJFqxGSReGDW8VhHNGhRoF7 S2p7li+rxx5CCInLCr1a9mGb+vpC79EEdsH0DjjM=
Message-Id: <6.2.5.6.2.20140222222203.0bd30788@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 23 Feb 2014 00:58:01 -0800
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IETF Anti-Harassment Procedures
In-Reply-To: <CADnDZ893aXfZ7LZkUhuZ4REbc676wtH1_cQ7HKZr8XnfE7Aebw@mail.g mail.com>
References: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com> <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@mail.gmail.com> <CADnDZ893aXfZ7LZkUhuZ4REbc676wtH1_cQ7HKZr8XnfE7Aebw@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/C03xzpeiF-pEPBfzdmq2-APSRjs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Feb 2014 09:23:04 -0000

Hi Abdussalam,
At 13:31 22-02-2014, Abdussalam Baryun wrote:
>IMHO, Target is suitable term with responder and  reporter, we never 
>no who is the real victim sometimes if no witnesses.  After 
>investigation we get to know if target is victim. If you assume 
>witnesses available then "victim" is the right word replacing 
>"target" but still we need to change the other two terms.

The archive of this mailing list is publicly accessible.  It is 
possible to verify whether this message, which is addressed to you, 
could be considered as offensive.  It is assumed that the mailing 
list moderator will see that message and any other message which 
could be considered as offensive.

The mailing list moderator can intervene if he or she thinks that the 
email exchange is reaching a point where it might be considered as 
abusive or harassment.  An Area Director can assess whether the 
mailing list moderator took an appropriate decision, e.g. by reading 
the mail archive.

There aren't any witnesses or mail archive for a private exchange 
between two persons.  The mailing list moderator will not see those messages.

Person A might send an abusive message to person B if:

   (a) Person A can do that anonymously.

   (b) There isn't anyone to witness that.

   (c) The people witnessing that will remain quiet about it.

   (d) Person B will not complain about it.

   (e) Person B can complain about it but nobody will take any action
       against Person A.

The word "target" depersonalizes the matter.  The need for 
objectivity doesn't prevent one from showing some consideration for Person B.

Regards,
S. Moonesamy 


From nobody Sun Feb 23 01:48:08 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 57EA91A00BC for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 01:48:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level: 
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.548, 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 QdZLKiZQPgBk for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 01:48:05 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [IPv6:2a02:80:3ffe::176]) by ietfa.amsl.com (Postfix) with ESMTP id 13CA01A002B for <ietf@ietf.org>; Sun, 23 Feb 2014 01:48:05 -0800 (PST)
Received: from ix-2.local (unknown [192.165.72.14]) by mail.frobbit.se (Postfix) with ESMTPSA id BF81620611; Sun, 23 Feb 2014 10:47:59 +0100 (CET)
Message-ID: <5309C3CD.9000302@frobbit.se>
Date: Sun, 23 Feb 2014 10:47:57 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, Adrian Farrel <adrian@olddog.co.uk>,  Pete Resnick <presnick@qti.qualcomm.com>
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net>
In-Reply-To: <530920EB.1030505@dcrocker.net>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="eXHJNS0RJW2Sxox5pC3sIWKGMp7fl4FnX"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Qaw4UpTAa7LIOlGRb2Sl6OvvWR8
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: Sun, 23 Feb 2014 09:48:06 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--eXHJNS0RJW2Sxox5pC3sIWKGMp7fl4FnX
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-22 23:12, Dave Crocker wrote:
> 1. Ombud Formation

Please either call this "ombudsman" or come up with a different word.

The word "ombud" in Swedish (where "Ombudsman" comes from) does
definitely not have the same neutral meaning as "ombudsman" has. In
fact, "ombud" is absolutely not neutral but a proxy that acts on behalf
of someone else.

I.e. "ombud" and "ombudsman" are two different words, and you can not
"just" remove the ending "man" that part from meaning "male" also means
"human".

   Patrik



--eXHJNS0RJW2Sxox5pC3sIWKGMp7fl4FnX
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.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTCcPPrMabGguI180RAqGNAJ0c3iv3TAiItz3TvGu2WtBrABqCGACfVt9w
QAqU2vy1ol60JVG/xet3jQU=
=x4dT
-----END PGP SIGNATURE-----

--eXHJNS0RJW2Sxox5pC3sIWKGMp7fl4FnX--


From nobody Sun Feb 23 02:25:25 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 BB9251A002F for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 02:25:22 -0800 (PST)
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 bUWGoYhynN7X for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 02:25:20 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.116]) by ietfa.amsl.com (Postfix) with ESMTP id 15FAA1A002D for <ietf@ietf.org>; Sun, 23 Feb 2014 02:25:19 -0800 (PST)
Received: from [193.109.255.147:44152] by server-12.bemta-14.messagelabs.com id FD/10-17220-A8CC9035; Sun, 23 Feb 2014 10:25:14 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-72.messagelabs.com!1393151114!11466896!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 9719 invoked from network); 23 Feb 2014 10:25:14 -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; 23 Feb 2014 10:25:14 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Sun, 23 Feb 2014 10:25:13 +0000
From: <l.wood@surrey.ac.uk>
To: <paf@frobbit.se>, <dcrocker@bbiw.net>, <adrian@olddog.co.uk>, <presnick@qti.qualcomm.com>
Date: Sun, 23 Feb 2014 10:25:13 +0000
Subject: RE: Basic Issues  (was Re: anti-harassment procedures)
Thread-Topic: Basic Issues  (was Re: anti-harassment procedures)
Thread-Index: Ac8wfGfd0+Jt/cPoT/S7r4AzNT6lKwABGczf
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334728@EXMB01CMS.surrey.ac.uk>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net>,<5309C3CD.9000302@frobbit.se>
In-Reply-To: <5309C3CD.9000302@frobbit.se>
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="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/temAeHcDLVAtBmtJCFr1Y-wtIeU
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, 23 Feb 2014 10:25:23 -0000

In English, your Swedish ombud would be a proctor. but since the Scandanavi=
an countries changed the ombud role over time (etymology according to Wikip=
edia), does this matter?

I think we're back to ombudsentity, though Grand Inquisitor has a nice ring=
 to it.

Lloyd Wood
http://about.me/lloydwood

be pure! be vigilant! behave!
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Patrik F=E4ltstr=F6m [paf@f=
robbit.se]
Sent: 23 February 2014 09:47
To: dcrocker@bbiw.net; Adrian Farrel; Pete Resnick
Cc: ietf@ietf.org Discussion
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)

On 2014-02-22 23:12, Dave Crocker wrote:
> 1. Ombud Formation

Please either call this "ombudsman" or come up with a different word.

The word "ombud" in Swedish (where "Ombudsman" comes from) does
definitely not have the same neutral meaning as "ombudsman" has. In
fact, "ombud" is absolutely not neutral but a proxy that acts on behalf
of someone else.

I.e. "ombud" and "ombudsman" are two different words, and you can not
"just" remove the ending "man" that part from meaning "male" also means
"human".

   Patrik



From nobody Sun Feb 23 05:28:39 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 AA4181A008D for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 05:28:38 -0800 (PST)
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=[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 zJap1gMEr3kq for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 05:28:36 -0800 (PST)
Received: from mail-yk0-x232.google.com (mail-yk0-x232.google.com [IPv6:2607:f8b0:4002:c07::232]) by ietfa.amsl.com (Postfix) with ESMTP id C3E041A04B9 for <ietf@ietf.org>; Sun, 23 Feb 2014 05:28:36 -0800 (PST)
Received: by mail-yk0-f178.google.com with SMTP id 79so11475217ykr.9 for <ietf@ietf.org>; Sun, 23 Feb 2014 05:28:36 -0800 (PST)
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=qqzJ0nvuxHbeCPFoqppWACX4VWln302IwfISq7y7Bac=; b=a6m/GV0mecN1ErP+LpCQbYpCUzCDkhPZgQ/5ikkL1sqKFBYSU3UT9vriCQGMFtf8Sj ma+AO/YGHRI6T3HSRspm7QUYYtEkY+U34SJQ03UyZzGJ7JDfzGSITlR4n7Bg8yIHOAGL X3b0mPe4C0LHL9mjfF/Y/HknrZIg9JXBO3Jryh/1Gl5a0r6N3eQrgrmUyt2+8YKgmn9Q mDhsZxH5PQpv2NWReRdvcCdKVafZ8jywKbmofs06CfzwFa8ZhOfAFjcSdXgdwW+sRgxg bmsJLTIpUowvQRKE6h0heveqLI0H51NLmYcnj9K6pdD/WVQJLlJwC9R58vZBHBoG1ckt B0tA==
MIME-Version: 1.0
X-Received: by 10.236.72.40 with SMTP id s28mr24308423yhd.160.1393162116351; Sun, 23 Feb 2014 05:28:36 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Sun, 23 Feb 2014 05:28:36 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140222222203.0bd30788@elandnews.com>
References: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com> <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@mail.gmail.com> <CADnDZ893aXfZ7LZkUhuZ4REbc676wtH1_cQ7HKZr8XnfE7Aebw@mail.gmail.com> <6.2.5.6.2.20140222222203.0bd30788@elandnews.com>
Date: Sun, 23 Feb 2014 14:28:36 +0100
Message-ID: <CADnDZ8-FWuosDyQPOrP+9QmNM67nUrwM7E0aWBfrDB3mtt9GBg@mail.gmail.com>
Subject: Re: IETF Anti-Harassment Procedures
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=20cf300513140f4a9404f312d5dc
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vKGiJqD-cNxAGo7ecLpUeuayGRY
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: Sun, 23 Feb 2014 13:28:38 -0000

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

Hi S. Moonesamy

On Sunday, February 23, 2014, S Moonesamy wrote:

> Hi Abdussalam,
> At 13:31 22-02-2014, Abdussalam Baryun wrote:
>
>> IMHO, Target is suitable term with responder and  reporter, we never no
>> who is the real victim sometimes if no witnesses.  After investigation we
>> get to know if target is victim. If you assume witnesses available then
>> "victim" is the right word replacing "target" but still we need to change
>> the other two terms.
>>
>
> The archive of this mailing list is publicly accessible.  It is possible
> to verify whether this message, which is addressed to you, could be
> considered as offensive.  It is assumed that the mailing list moderator
> will see that message and any other message which could be considered as
> offensive.


The draft does not say only mailing list, so it is for any IETF activity
including social events.

>
> The mailing list moderator can intervene if he or she thinks that the
> email exchange is reaching a point where it might be considered as abusive
> or harassment.  An Area Director can assess whether the mailing list
> moderator took an appropriate decision, e.g. by reading the mail archive.
>
> There aren't any witnesses or mail archive for a private exchange between
> two persons.  The mailing list moderator will not see those messages.


It will be nice to mention activity channels as the list, the meetings, the
WG rooms, others

>
> Person A might send an abusive message to person B if:
>
>   (a) Person A can do that anonymously.
>
>   (b) There isn't anyone to witness that.
>
>   (c) The people witnessing that will remain quiet about it.
>
>   (d) Person B will not complain about it.
>
>   (e) Person B can complain about it but nobody will take any action
>       against Person A.
>
> The word "target" depersonalizes the matter.


That scenario is correct to not use the word Target because the B is
victim. There are many scenarios in my mind but the draft does not define
limits and levels as I already mentioned in my inputs.


>  The need for objectivity doesn't prevent one from showing some
> consideration for Person B.


Please note that I have been in the B situation, so I understand what you
mean, but I know that this draft to become BCP it will need to be practical
and involve many possible scenarios not only mailing scenarios.

Best Regards

Abdussalam

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

Hi=A0<font><span style=3D"background-color:rgba(255,255,255,0)">S. Moonesam=
y</span></font><br><br>On Sunday, February 23, 2014, S Moonesamy  wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">
Hi Abdussalam,<br>
At 13:31 22-02-2014, 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">
IMHO, Target is suitable term with responder and =A0reporter, we never no w=
ho is the real victim sometimes if no witnesses. =A0After investigation we =
get to know if target is victim. If you assume witnesses available then &qu=
ot;victim&quot; is the right word replacing &quot;target&quot; but still we=
 need to change the other two terms.<br>

</blockquote>
<br>
The archive of this mailing list is publicly accessible. =A0It is possible =
to verify whether this message, which is addressed to you, could be conside=
red as offensive. =A0It is assumed that the mailing list moderator will see=
 that message and any other message which could be considered as offensive.=
</blockquote>
<div><br></div><div>The draft does not say only mailing list, so it is for =
any IETF activity including social events.=A0=A0</div><blockquote class=3D"=
gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-=
left:1ex">

<br>
The mailing list moderator can intervene if he or she thinks that the email=
 exchange is reaching a point where it might be considered as abusive or ha=
rassment. =A0An Area Director can assess whether the mailing list moderator=
 took an appropriate decision, e.g. by reading the mail archive.<br>

<br>
There aren&#39;t any witnesses or mail archive for a private exchange betwe=
en two persons. =A0The mailing list moderator will not see those messages.<=
/blockquote><div><br></div><div>It will be nice to mention activity channel=
s as the list, the meetings, the WG rooms, others=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
Person A might send an abusive message to person B if:<br>
<br>
=A0 (a) Person A can do that anonymously.<br>
<br>
=A0 (b) There isn&#39;t anyone to witness that.<br>
<br>
=A0 (c) The people witnessing that will remain quiet about it.<br>
<br>
=A0 (d) Person B will not complain about it.<br>
<br>
=A0 (e) Person B can complain about it but nobody will take any action<br>
=A0 =A0 =A0 against Person A.<br>
<br>
The word &quot;target&quot; depersonalizes the matter.=A0</blockquote><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"></blockquote><div><br></div><div>That scenario is=
 correct to not use the word Target because the B is victim. There are many=
 scenarios in my mind but the draft does not define limits and levels as I =
already mentioned in my inputs.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">=A0The need for objectivity do=
esn&#39;t prevent one from showing some consideration for Person B.</blockq=
uote>
<div><br></div><div>Please note that I have been in the B situation, so I u=
nderstand what you mean, but I know that this draft to become BCP it will n=
eed to be practical and involve many possible scenarios not only mailing sc=
enarios.=A0</div>
<div><br></div><div>Best Regards</div><div><br></div><div>Abdussalam</div><=
div><br></div>

--20cf300513140f4a9404f312d5dc--


From nobody Sun Feb 23 05:35:42 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 939491A00D8 for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 05:35:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.247
X-Spam-Level: 
X-Spam-Status: No, score=-0.247 tagged_above=-999 required=5 tests=[MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lvYNS2PGgszG for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 05:35:39 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 922A01A00B6 for <ietf@ietf.org>; Sun, 23 Feb 2014 05:35:39 -0800 (PST)
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 7F64F1B826F for <ietf@ietf.org>; Sun, 23 Feb 2014 05:35:39 -0800 (PST)
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 484F7190052; Sun, 23 Feb 2014 05:35:39 -0800 (PST)
Received: from [192.168.1.109] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 23 Feb 2014 05:35:39 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5309C3CD.9000302@frobbit.se>
Date: Sun, 23 Feb 2014 08:35:36 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <51D0FA5F-146D-4A12-8150-0083DD0134DD@nominum.com>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net> <5309C3CD.9000302@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Sv1Jb15WEG0urgyScc__FgkLZ5o
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, Dave Crocker <dcrocker@bbiw.net>, "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: Sun, 23 Feb 2014 13:35:40 -0000

On Feb 23, 2014, at 4:47 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:
> I.e. "ombud" and "ombudsman" are two different words, and you can not
> "just" remove the ending "man" that part from meaning "male" also =
means
> "human".

Andrea proposed ombuddy, but it's probably a bit too irreverant.   What =
about ombudsperson?


From nobody Sun Feb 23 05:41:40 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 9C39E1A00DC for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 05:41:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.102
X-Spam-Level: 
X-Spam-Status: No, score=0.102 tagged_above=-999 required=5 tests=[HELO_EQ_SE=0.35, MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547, 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 g8Myvwmk2Vsk for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 05:41:37 -0800 (PST)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.176]) by ietfa.amsl.com (Postfix) with ESMTP id 70C551A0493 for <ietf@ietf.org>; Sun, 23 Feb 2014 05:41:37 -0800 (PST)
Received: from ix-2.local (unknown [192.165.72.14]) by mail.frobbit.se (Postfix) with ESMTPSA id 569AC1FD2E; Sun, 23 Feb 2014 14:41:36 +0100 (CET)
Message-ID: <5309FA8D.80305@frobbit.se>
Date: Sun, 23 Feb 2014 14:41:33 +0100
From: =?ISO-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net> <5309C3CD.9000302@frobbit.se> <51D0FA5F-146D-4A12-8150-0083DD0134DD@nominum.com>
In-Reply-To: <51D0FA5F-146D-4A12-8150-0083DD0134DD@nominum.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="IUCMDPCGtP87i2aJr9OQjAgP1lfXCNJKO"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/28UmmcrIc8ihFq_6GUqg0yUbNJI
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, Dave Crocker <dcrocker@bbiw.net>, "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: Sun, 23 Feb 2014 13:41:38 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--IUCMDPCGtP87i2aJr9OQjAgP1lfXCNJKO
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2014-02-23 14:35, Ted Lemon wrote:
> On Feb 23, 2014, at 4:47 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> wrot=
e:
>> > I.e. "ombud" and "ombudsman" are two different words, and you can no=
t
>> > "just" remove the ending "man" that part from meaning "male" also me=
ans
>> > "human".
> Andrea proposed ombuddy, but it's probably a bit too irreverant.   What=
 about ombudsperson?

Please do not go down that path at all.

Once again, either "ombudsman" or a word not related to it.

"ombudsman" has in Swedish nothing to do with gender of the person
having that role, but if people do feel it has gender connotation, use a
completely different word.

Yes, we do have these discussions in Sweden as well...

   Patrik



--IUCMDPCGtP87i2aJr9OQjAgP1lfXCNJKO
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.4.9 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iD8DBQFTCfqPrMabGguI180RAs7uAJwNdM0AlcNSA1DYu+ij8W9RDR7uiACdHA/Q
U2453DWyIxcoIXY4zR+n2ug=
=EdKv
-----END PGP SIGNATURE-----

--IUCMDPCGtP87i2aJr9OQjAgP1lfXCNJKO--


From nobody Sun Feb 23 05:50:06 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 800451A00D1 for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 05:50:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.247
X-Spam-Level: 
X-Spam-Status: No, score=-0.247 tagged_above=-999 required=5 tests=[MIME_8BIT_HEADER=0.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id knT_K8w4IjXP for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 05:50:03 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id F17BF1A00C5 for <ietf@ietf.org>; Sun, 23 Feb 2014 05:50:02 -0800 (PST)
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 4E2301B82A5 for <ietf@ietf.org>; Sun, 23 Feb 2014 05:50:02 -0800 (PST)
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 46789190052; Sun, 23 Feb 2014 05:50:02 -0800 (PST)
Received: from [192.168.1.109] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 23 Feb 2014 05:50:02 -0800
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <5309FA8D.80305@frobbit.se>
Date: Sun, 23 Feb 2014 08:49:59 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <B91998C0-EFC3-4EBD-AC9C-6BBE453FEF8B@nominum.com>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net> <5309C3CD.9000302@frobbit.se> <51D0FA5F-146D-4A12-8150-0083DD0134DD@nominum.com> <5309FA8D.80305@frobbit.se>
To: =?iso-8859-1?Q?Patrik_F=E4ltstr=F6m?= <paf@frobbit.se>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CUR0Vvv476sUVruuACz2ChJexz4
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, Dave Crocker <dcrocker@bbiw.net>, "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: Sun, 23 Feb 2014 13:50:04 -0000

On Feb 23, 2014, at 8:41 AM, Patrik F=E4ltstr=F6m <paf@frobbit.se> =
wrote:
> "ombudsman" has in Swedish nothing to do with gender of the person
> having that role, but if people do feel it has gender connotation, use =
a
> completely different word.

This was a common theme in feminist discourse in the previous century in =
the U.S. as well, but I think the consensus at this point is that "man" =
really does have a masculine connotation at least in english.

We've also seen a trend toward the elimination of the -ess suffix, for =
example serious female actors are no longer referred to as actresses.   =
So possibly a -or word might be a better choice, if we could come up =
with one.

I vote for "auror": someone who listens, notwithstanding the different =
meaning in the Harry Potter books.


From nobody Sun Feb 23 06:21:49 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 3FE861A033F for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 06:21:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level: 
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[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 E6a_wDeOMacP for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 06:21:45 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 00DEE1A00BF for <ietf@ietf.org>; Sun, 23 Feb 2014 06:21:44 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1NELfnb013046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf@ietf.org>; Sun, 23 Feb 2014 06:21:45 -0800
Message-ID: <530A03BF.7060403@dcrocker.net>
Date: Sun, 23 Feb 2014 06:20:47 -0800
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.3.0
MIME-Version: 1.0
To: "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net> <5309C3CD.9000302@frobbit.se> <51D0FA5F-146D-4A12-8150-0083DD0134DD@nominum.com> <5309FA8D.80305@frobbit.se> <B91998C0-EFC3-4EBD-AC9C-6BBE453FEF8B@nominum.com>
In-Reply-To: <B91998C0-EFC3-4EBD-AC9C-6BBE453FEF8B@nominum.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, 23 Feb 2014 06:21:45 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gLarZ7S-v7wFmvxovspHhtJQFI0
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, 23 Feb 2014 14:21:46 -0000

> This was a common theme in feminist discourse in the previous century
> in the U.S. as well, but I think the consensus at this point is that
> "man" really does have a masculine connotation at least in english.


To underscore this...

Given the topic of harassment and given the types of behaviors that can
and do qualify under that, the idea that we'd use a title that is
overtly gender-specific strikes me as counter-productively insensitive.

To the point of being impressive, but not in a good way.

d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Sun Feb 23 06:34:17 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 C0D2A1A00DD for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 06:34:16 -0800 (PST)
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 HEULY93sU4wd for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 06:34:15 -0800 (PST)
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 55A251A0056 for <ietf@ietf.org>; Sun, 23 Feb 2014 06:34:15 -0800 (PST)
Received: by mail-wi0-f176.google.com with SMTP id hi5so2220322wib.15 for <ietf@ietf.org>; Sun, 23 Feb 2014 06:34:14 -0800 (PST)
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=AppCGRVrIfVVCXFIIj/k7Qfc4Q2kR6HQl57NjyA8EN4=; b=SfleNmxzPaWAudNP8KxcK8E20IyaGrswo/XgBQY2fjkcWJrdDj5QwXEFJbS1OZPY4K CGziaJovUdfe0/vlDW7NKSgV6U28tIvZNi8Qt+yrFenMR50GVP/Bbz4UIR9TltAQGZD6 GZsMD6aJCbXLBUkkWqmbptUVlXl45BCQ3WZOcWnfBsa3ZCpjNqhnwXAVzZYQwrOXc/ZT YnjPx49NnedR+iipJX8jzmJzlrGD3CaNlkgADWR23hxOBDoSrR3avuXovsVTECYKivE9 NlF62+6xLGvoa71rMDDIMRmkV6mf5O/8wc/FcSFO8KJBlnNHM1DVcLQuaqkv7i5Uui1x E5WQ==
MIME-Version: 1.0
X-Received: by 10.194.22.232 with SMTP id h8mr14740511wjf.53.1393166054643; Sun, 23 Feb 2014 06:34:14 -0800 (PST)
Received: by 10.194.171.106 with HTTP; Sun, 23 Feb 2014 06:34:14 -0800 (PST)
Received: by 10.194.171.106 with HTTP; Sun, 23 Feb 2014 06:34:14 -0800 (PST)
In-Reply-To: <530A03BF.7060403@dcrocker.net>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net> <5309C3CD.9000302@frobbit.se> <51D0FA5F-146D-4A12-8150-0083DD0134DD@nominum.com> <5309FA8D.80305@frobbit.se> <B91998C0-EFC3-4EBD-AC9C-6BBE453FEF8B@nominum.com> <530A03BF.7060403@dcrocker.net>
Date: Sun, 23 Feb 2014 09:34:14 -0500
Message-ID: <CAPv4CP-Uxp5r81h0mPa=D5brB8Kg=bEmJK9RaUoe9TpHGAmZeg@mail.gmail.com>
Subject: Re: Basic Issues (was Re: anti-harassment procedures)
From: Scott Brim <scott.brim@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=047d7b5d22baccf5b304f313bf61
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/U_5b7BqgKDzvGnmvkzFeyhMgH8o
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: Sun, 23 Feb 2014 14:34:17 -0000

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

Yes, lots of public institutions in the USA have gone to ombudsperson, as
has the UN in New York.  But it's a poor portmanteau. Best to start again
with a gender-neutral word in any language.

How about just mediator?

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

<p dir=3D"ltr">Yes, lots of public institutions in the USA have gone to omb=
udsperson, as has the UN in New York.=A0 But it&#39;s a poor portmanteau. B=
est to start again with a gender-neutral word in any language.=A0 </p>
<p dir=3D"ltr">How about just mediator? </p>

--047d7b5d22baccf5b304f313bf61--


From nobody Sun Feb 23 06:48:07 2014
Return-Path: <ynir@checkpoint.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDC691A00EA for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 06:48:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.447
X-Spam-Level: 
X-Spam-Status: No, score=-7.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7Mh23sGiku1x for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 06:48:05 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id 7CED81A0056 for <ietf@ietf.org>; Sun, 23 Feb 2014 06:48:04 -0800 (PST)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id s1NElpPt002196; Sun, 23 Feb 2014 16:47:51 +0200
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.228]) by DAG-EX10.ad.checkpoint.com ([169.254.3.228]) with mapi id 14.03.0123.003; Sun, 23 Feb 2014 16:47:51 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Basic Issues (was Re: anti-harassment procedures)
Thread-Topic: Basic Issues (was Re: anti-harassment procedures)
Thread-Index: AQHPMKRffkLmI6jeckqLQ3nYWKbFbZrCyacA
Date: Sun, 23 Feb 2014 14:47:50 +0000
Message-ID: <E6DA4C80-1ED4-4FAF-A873-6AF276C6FE43@checkpoint.com>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net> <5309C3CD.9000302@frobbit.se> <51D0FA5F-146D-4A12-8150-0083DD0134DD@nominum.com> <5309FA8D.80305@frobbit.se> <B91998C0-EFC3-4EBD-AC9C-6BBE453FEF8B@nominum.com> <530A03BF.7060403@dcrocker.net> <CAPv4CP-Uxp5r81h0mPa=D5brB8Kg=bEmJK9RaUoe9TpHGAmZeg@mail.gmail.com>
In-Reply-To: <CAPv4CP-Uxp5r81h0mPa=D5brB8Kg=bEmJK9RaUoe9TpHGAmZeg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.31.24.46]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: multipart/alternative; boundary="_000_E6DA4C801ED44FAFA8736AF276C6FE43checkpointcom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/nLuA9kB_sO2crMEmIdBlEmYkaV0
Cc: Dave Crocker <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: Sun, 23 Feb 2014 14:48:06 -0000

--_000_E6DA4C801ED44FAFA8736AF276C6FE43checkpointcom_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

They're not mediating between anyone and anything. How about "complaints of=
ficer"

On Feb 23, 2014, at 4:34 PM, Scott Brim <scott.brim@gmail.com<mailto:scott.=
brim@gmail.com>> wrote:


Yes, lots of public institutions in the USA have gone to ombudsperson, as h=
as the UN in New York.  But it's a poor portmanteau. Best to start again wi=
th a gender-neutral word in any language.

How about just mediator?


Email secured by Check Point



--_000_E6DA4C801ED44FAFA8736AF276C6FE43checkpointcom_
Content-Type: text/html; charset="iso-8859-1"
Content-ID: <CA72B86740B58642800F1D15EECE9FCF@ad.checkpoint.com>
Content-Transfer-Encoding: quoted-printable

<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-lin=
e-break: after-white-space; ">
They're not mediating between anyone and anything. How about &quot;complain=
ts officer&quot;
<div><br>
<div>
<div>On Feb 23, 2014, at 4:34 PM, Scott Brim &lt;<a href=3D"mailto:scott.br=
im@gmail.com">scott.brim@gmail.com</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<blockquote type=3D"cite">
<p dir=3D"ltr">Yes, lots of public institutions in the USA have gone to omb=
udsperson, as has the UN in New York.&nbsp; But it's a poor portmanteau. Be=
st to start again with a gender-neutral word in any language.&nbsp;
</p>
<p dir=3D"ltr">How about just mediator? </p>
<br>
<br>
Email secured by Check Point <br>
<br>
</blockquote>
</div>
<br>
</div>
</body>
</html>

--_000_E6DA4C801ED44FAFA8736AF276C6FE43checkpointcom_--


From nobody Sun Feb 23 09:26:32 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 274481A0679 for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 09:26:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.253
X-Spam-Level: 
X-Spam-Status: No, score=0.253 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LsypGGgoS4Oe for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 09:26:29 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id EB57A1A0147 for <ietf@ietf.org>; Sun, 23 Feb 2014 09:26:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 15DE8BEF3; Sun, 23 Feb 2014 17:26:28 +0000 (GMT)
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 CWVAiS+U5Oma; Sun, 23 Feb 2014 17:26:26 +0000 (GMT)
Received: from [10.87.48.14] (unknown [86.45.63.238]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8F969BEF2; Sun, 23 Feb 2014 17:26:26 +0000 (GMT)
Message-ID: <530A2F42.1060401@cs.tcd.ie>
Date: Sun, 23 Feb 2014 17:26:26 +0000
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, dcrocker@bbiw.net
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net> <53097147.6090409@gmail.com>
In-Reply-To: <53097147.6090409@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/-xaCl5VgKli9d2RuGY8gCnDusmQ
Cc: Adrian Farrel <adrian@olddog.co.uk>, Pete Resnick <presnick@qti.qualcomm.com>, "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: Sun, 23 Feb 2014 17:26:31 -0000

On 02/23/2014 03:55 AM, Brian E Carpenter wrote:
>  As I read
> http://www.ombudsmanassociation.org/about-the-role-of-an-ombudsman.php,
> we are slightly misreading the classical role of an Ombudsman;
> that's fine, but we do need advisers or team members with dispute-resolution
> and mediation experience.

Seems to be some good material on that site. We should
copy where we can I'd hope.

S.


From nobody Sun Feb 23 10:42: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 2F67A1A06B2 for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 10:42:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.453
X-Spam-Level: 
X-Spam-Status: No, score=0.453 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, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOtO8uoanUNY for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 10:42:37 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BDCF1A06B9 for <ietf@ietf.org>; Sun, 23 Feb 2014 10:42:37 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.152.195]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1NIg9uS004158 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 23 Feb 2014 10:42:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393180950; bh=dTNYvCSjAuiKF8TMHnTP6P1O6tWZc/XCHOwi7eJXmuw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=XFJQaYQA6dx++9NtgZPGx5qURjx9zfB4IX/XwiBNgBAUWF+va/3pD8A016fSrhex1 Us4MbZcL4AvrUNChHkGUMaiUcUs3K6K0ph/nLzUA5j/1DOsHSDb4w6B01arlj44Dxd jjO9TvDzmJXZzYIadq2RKkgE8HMbKfwNKYI51gLc=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393180950; i=@elandsys.com; bh=dTNYvCSjAuiKF8TMHnTP6P1O6tWZc/XCHOwi7eJXmuw=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=xv84s6vYwGyIV7iTR9QU0l/h9QVlSQ/CNrImvSoW/34S8Ot9O3BbGm4goUeR4RECC sxj8ChD6kqPx3H77ggujsc+7ooitD8AHKJ1hsPKNqyK6WkSiwrHWL7Ga2mYzZ8O6GE cyCXLGV2oF2nj3n7lB6fSXo0ZwbOZMm7S60Yt+FE=
Message-Id: <6.2.5.6.2.20140223093748.0bc45798@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sun, 23 Feb 2014 10:28:44 -0800
To: Patrik =?iso-8859-1?Q?F=E4ltstr=F6m?= <paf@frobbit.se>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Basic Issues  (was Re: anti-harassment procedures)
In-Reply-To: <5309C3CD.9000302@frobbit.se>
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <530920EB.1030505@dcrocker.net> <5309C3CD.9000302@frobbit.se>
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/4jxYi-4ynN0gTJV6tYKCtrOG2Fc
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, 23 Feb 2014 18:42:39 -0000

Hi Patrik,
At 01:47 23-02-2014, Patrik F=E4ltstr=F6m wrote:
>Please either call this "ombudsman" or come up with a different word.
>
>The word "ombud" in Swedish (where "Ombudsman" comes from) does
>definitely not have the same neutral meaning as "ombudsman" has. In
>fact, "ombud" is absolutely not neutral but a proxy that acts on behalf
>of someone else.
>
>I.e. "ombud" and "ombudsman" are two different words, and you can not
>"just" remove the ending "man" that part from meaning "male" also means
>"human".

A quick search displays 7,480,000 hits for=20
"ombudsman" and 679,000 hits for=20
"ombudsperson".  https://www.ombudsman.bc.ca/=20
uses the word=20
"ombudsperson".  http://www.ombudsman.europa.eu=20
uses the word=20
"ombudsman".  http://www.ombudsman.cl/ uses=20
"defensor del pueblo".  The choice is clear if=20
the decision is to be based on factual=20
information.  It is better to choose another word=20
if some people are not comfortable with the word "ombudsman".

On a lighter note, it has been said that "we=20
reject: kings, presidents and voting" [1].  There=20
is a word in there which is not gender-neutral [2].

Regards,
S. Moonesamy

1. http://www.ietf.org/meeting/83/images/submission3_002.jpg
2. "Political correctness differs from more=20
old-fashioned methods of self-censorship.  Before=20
the era of political correctness, people already=20
understood that it was a bad idea to offend or=20
upset people.  They had complex systems of=20
manners that involved a certain amount of=20
dishonesty to spare people's feelings. Some=20
truths were not to be spoken in public, in good=20
company, in front of the servants, etc."


From nobody Sun Feb 23 19:43:19 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 9115E1A07E5 for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 19:43:18 -0800 (PST)
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 IOzHQ5g_-Fc5 for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 19:43:17 -0800 (PST)
Received: from mail-yk0-x22b.google.com (mail-yk0-x22b.google.com [IPv6:2607:f8b0:4002:c07::22b]) by ietfa.amsl.com (Postfix) with ESMTP id CAAB61A07E4 for <ietf@ietf.org>; Sun, 23 Feb 2014 19:43:16 -0800 (PST)
Received: by mail-yk0-f171.google.com with SMTP id q9so13053266ykb.2 for <ietf@ietf.org>; Sun, 23 Feb 2014 19:43:16 -0800 (PST)
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=plUXKn0ZQSIXlsBWcggv5dGCl3Kj1gn8voxfU0z1maQ=; b=pc4dnreq6DYLvOe5kS4JoyFkTpEEQasl3La2hTeETul8qAgezcUpEQUg0Kqo4XR2xC OTGvVamzxyrknEoLTPZNdIftqcfCbradY07YPdP0tId7icjY4wxHeSkykSlTNp35e1kE n5f/uuax0wAtPyHtDitZUF419jtiRm4bpdjnX5JaI2sjfXYg4/h81OrWvHUiTZXbv81Q /2ZQBNzMjnT9r2xOW1qy8bPaX6pNt5sUYlzrEoaYLIvXqPZtpYDDjk2bL5ZxqY5hQR8S Q/QZJXA0fZJzuRfKc1jdoqktPFkWrK5V/HI2rg1i8/w6DZ9gzk8xtaSiX6IrcUPpw5LS xGOg==
MIME-Version: 1.0
X-Received: by 10.236.89.11 with SMTP id b11mr28018953yhf.16.1393213396333; Sun, 23 Feb 2014 19:43:16 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Sun, 23 Feb 2014 19:43:16 -0800 (PST)
Date: Mon, 24 Feb 2014 04:43:16 +0100
Message-ID: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com>
Subject: Policy of WG chairs in organising time for presentations and face2face discussions
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf300e56b795b98904f31ec5cd
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/POeBnDyxpnHLrwTOVW6NW8ALPGE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 03:43:18 -0000

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

Dear IETF WGs' Chairs,

I suggest in London that you assign only maximum 10 minutes present per WG
draft and maximum 5 minute for individual draft (as limit policy). We need
to use more input and have more face2face (F2F) discussion in our meeting.
I remember we discussed this before but it will be nice if we know what
chairs are thinking before few days of the meeting.

Meeting time is money and that we need to improve the use of IETF
times within F2F WG discussions and decisions.  If an author cannot
describe issues of draft in 10 minutes then it will be difficult for the
WG listeners to discuss and make decisions within another 10 minutes per
item. Please comment.

Best wishes,

Abdussalam

WG Meetings are needed for group interactions and group decisions not
individual presentations or individual decisions.

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

Dear IETF WGs&#39; Chairs,<div><br></div><div>I suggest in London=A0that yo=
u assign only maximum 10 minutes present per WG draft and maximum 5 minute =
for individual draft (as limit policy).=A0We need to use more input and hav=
e more face2face (F2F)=A0discussion in our meeting. I remember we discussed=
 this before but it will be nice if we know what chairs are thinking before=
 few days of the meeting.=A0</div>
<div><br></div><div>Meeting=A0time=A0is money and that we need to improve t=
he=A0use of=A0IETF times=A0within F2F=A0WG=A0discussions and decisions.=A0=
=A0If an author cannot describe issues of=A0draft in 10 minutes then it wil=
l be difficult for the WG=A0listeners to discuss and make decisions within =
another 10 minutes per item. Please comment.=A0</div>
<div><br></div><div>Best wishes,</div><div><br></div><div>Abdussalam</div><=
div><br></div><div>WG=A0Meetings are needed for group=A0interactions and gr=
oup decisions=A0not individual=A0presentations or individual decisions.=A0<=
br><br>
</div>

--20cf300e56b795b98904f31ec5cd--


From nobody Sun Feb 23 22:51: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 A01601A0332 for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 22:50:58 -0800 (PST)
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_50=0.8,  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 2U0VH7QBpFLS for <ietf@ietfa.amsl.com>; Sun, 23 Feb 2014 22:50:54 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.174]) by ietfa.amsl.com (Postfix) with ESMTP id 79FB21A01CC for <ietf@ietf.org>; Sun, 23 Feb 2014 22:50:53 -0800 (PST)
Received: from [195.245.230.131:39371] by server-14.bemta-3.messagelabs.com id 95/8C-08196-CCBEA035; Mon, 24 Feb 2014 06:50:52 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-10.tower-78.messagelabs.com!1393224652!29887205!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 24757 invoked from network); 24 Feb 2014 06:50:52 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-10.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 24 Feb 2014 06:50:52 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Mon, 24 Feb 2014 06:50:51 +0000
From: <l.wood@surrey.ac.uk>
To: <abdussalambaryun@gmail.com>, <ietf@ietf.org>
Date: Mon, 24 Feb 2014 06:49:17 +0000
Subject: RE: Policy of WG chairs in organising time for presentations and face2face discussions
Thread-Topic: Policy of WG chairs in organising time for presentations and face2face discussions
Thread-Index: Ac8xEp89cpEZS6BKScOvSGTgCfiMMAAGepYI
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com>
In-Reply-To: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@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/otTvY6nyk9KiiGEioaQuQxOfQwI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 06:50:58 -0000

Abdussalam

you write:
> I suggest in London that you assign only maximum 10 minutes present per W=
G draft and maximum 5 minute for individual draft (as limit policy).
> We need to use more input and have more face2face (F2F) discussion in our=
 meeting.

How many IETF meetings have you attended, and what experience do you base t=
his recommendation on?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun [abdussal=
ambaryun@gmail.com]
Sent: 24 February 2014 03:43
To: ietf
Subject: Policy of WG chairs in organising time for presentations and face2=
face discussions

Dear IETF WGs' Chairs,

I suggest in London that you assign only maximum 10 minutes present per WG =
draft and maximum 5 minute for individual draft (as limit policy). We need =
to use more input and have more face2face (F2F) discussion in our meeting. =
I remember we discussed this before but it will be nice if we know what cha=
irs are thinking before few days of the meeting.

Meeting time is money and that we need to improve the use of IETF times wit=
hin F2F WG discussions and decisions.  If an author cannot describe issues =
of draft in 10 minutes then it will be difficult for the WG listeners to di=
scuss and make decisions within another 10 minutes per item. Please comment=
.

Best wishes,

Abdussalam

WG Meetings are needed for group interactions and group decisions not indiv=
idual presentations or individual decisions.


From nobody Mon Feb 24 02:36:21 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 D46921A0310 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 02:36:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.004
X-Spam-Level: 
X-Spam-Status: No, score=-4.004 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.793, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8wi3S4XwQN9b for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 02:36:18 -0800 (PST)
Received: from aer-iport-3.cisco.com (unknown [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id 8BE451A002B for <IETF@ietf.org>; Mon, 24 Feb 2014 02:36:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=506; q=dns/txt; s=iport; t=1393238178; x=1394447778; h=message-id:date:from:mime-version:to:cc:subject: content-transfer-encoding; bh=+og9LDMj3mDHDH4U78fiE6OCt0s4fpFrZeKrTkMPjR0=; b=Iew+tRtcIRw9vOOfqhSvRREtl5nv6aIKP671DCVVpQRkHyGxO9JclVZd 6maK86tMRT17bGtrAhvFRNgzCHPS2DAMwVRMTwRbkl6MZvllr18TYiGDp /+Wp4kcBhlSeH7JsV+mo5g8Irldgf53dubQ4rwb/4bb18hLgA46h+US32 Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AioFAFsgC1OQ/khN/2dsb2JhbABZgwY7g1q9ZYEUFnSCTzEkATUCBRYLAgsDAgECASstAQcBAQWHfA2lGqB1F4EpjTsdglmBSQSYNJIngy47
X-IronPort-AV: E=Sophos;i="4.97,534,1389744000";  d="scan'208";a="1208133"
Received: from ams-core-4.cisco.com ([144.254.72.77]) by aer-iport-3.cisco.com with ESMTP; 24 Feb 2014 10:36:17 +0000
Received: from mctiny.local ([10.61.165.177]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s1OAaGNt030024 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 24 Feb 2014 10:36:17 GMT
Message-ID: <530B20A0.5050600@cisco.com>
Date: Mon, 24 Feb 2014 11:36:16 +0100
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.3.0
MIME-Version: 1.0
To: IETF@ietf.org
Subject: ITAT workshop blog
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/4V79c8yIafoMbbtAkir3oEKo-B4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 10:36:20 -0000

Hi everyone,

As I mentioned to Phillip in a recent message, we had a really good
workshop on Internet Technology Adoption and Transition in December. 
I'll talk briefly about this in the plenary next week, and we'll have a
draft report up before then, but you can get a taste of how things went
by seeing the IETF blog now.[1]

Thanks, Jari, for prompting me to write the summary and sharing the IETF
blog.

Eliot

[1] http://www.ietf.org/blog/2014/02/views-on-internet-technology-adoption/


From nobody Mon Feb 24 03:41:53 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 907E91A07D7; Mon, 24 Feb 2014 03:41:51 -0800 (PST)
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 fw5hhsPooT6t; Mon, 24 Feb 2014 03:41:49 -0800 (PST)
Received: from mail-ea0-x233.google.com (mail-ea0-x233.google.com [IPv6:2a00:1450:4013:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id BBA671A0740; Mon, 24 Feb 2014 03:41:48 -0800 (PST)
Received: by mail-ea0-f179.google.com with SMTP id q10so3053408ead.24 for <multiple recipients>; Mon, 24 Feb 2014 03:41:47 -0800 (PST)
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=ryJCeBzFaezvH2/jzOyv3gwnXw8fdsqfGXGa29wCdnQ=; b=UVeMIjdgBDghPoGc0Zmir6iJRgoN6EmZQGP9Asj8zIetMfdnbPB9SzvjAyz7d3t1Yu FFZ48sYJqCcg0rT+nBUI6aTebWd9kR/72L+LCbMDxg9wNuk7IykafPP+igJXsr9X+7eB 0TI5Fz2RGHTTr/gL/bpUR2fJH2ytykQxcTa+491k66Q6otuXPB1SkgoGuGGMFcGJVbfu d6Rr80//PYG9N+482GsQyhZMMLEYH16/Xp46Q1PG63+hSoRtmoq13K61JO4lXSDspHsT 0+TLCOJrmWgNYXkbzpFGOKZlVfXymFZIcGrig2x1tlHFtNQu2Z3KtzMk0sQaPV3WhDAl 4BLw==
X-Received: by 10.14.221.201 with SMTP id r49mr24237976eep.104.1393242107768;  Mon, 24 Feb 2014 03:41:47 -0800 (PST)
Received: from RoniE ([109.67.98.212]) by mx.google.com with ESMTPSA id 46sm62776928ees.4.2014.02.24.03.41.44 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 24 Feb 2014 03:41:46 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <draft-ietf-mpls-special-purpose-labels.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-ietf-mpls-special-purpose-labels-05
Date: Mon, 24 Feb 2014 13:41:41 +0200
Message-ID: <07cd01cf3155$64d69780$2e83c680$@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_07CE_01CF3166.28602AD0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: Ac8xVWLYNV4LALsIQoymtX+xVkQDqw==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jWe_o3iAImsjb9GWXOP-k80SW9E
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: Mon, 24 Feb 2014 11:41:51 -0000

This is a multipart message in MIME format.

------=_NextPart_000_07CE_01CF3166.28602AD0
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-special-purpose-labels-05

Reviewer: Roni Even

Review Date:2014-2-24

IETF LC End Date: 2014-3-3

IESG Telechat date: 

 

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

 

 

Major issues:

 

Minor issues:

1.  In section 3.2 (a):  I noticed that the policy to update the registry
according  to section 5 is standard action so it should be the same here
since this is an update to the registry.

 

 

Nits/editorial comments:

1.	In section 3 last sentence "This answer to this" should be "The .."
2.	In section 3.2 item c you have "for for"

 


------=_NextPart_000_07CE_01CF3166.28602AD0
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;}
/* List Definitions */
@list l0
	{mso-list-id:1161195496;
	mso-list-type:hybrid;
	mso-list-template-ids:-1103323742 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1
	{mso-list-id:1462651820;
	mso-list-type:hybrid;
	mso-list-template-ids:-1754494482 67698703 67698713 67698715 67698703 =
67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l1:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;}
@list l1:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
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-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-special-purpose-labels-05</spa=
n><span 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;2-24<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;3-3<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 almost 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 =
style=3D'margin-left:.5in;text-indent:-.25in;mso-list:l1 level1 =
lfo1'><![if !supportLists]><span style=3D'mso-list:Ignore'>1.<span =
style=3D'font:7.0pt "Times New Roman"'>&nbsp; =
</span></span><![endif]><span dir=3DLTR></span><span =
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif"'>In section =
3.2 (a):&nbsp; I noticed that </span>the policy to update the registry =
according&nbsp; to section 5 is standard action so it should be the same =
here since this is an update to the registry.<o:p></o:p></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><ol style=3D'margin-top:0in' start=3D1 =
type=3D1><li class=3DMsoNormal style=3D'mso-list:l0 level1 lfo2'>In =
section 3 last sentence &#8220;This answer to this&#8221; should be =
&#8220;The ..&#8221;<o:p></o:p></li><li class=3DMsoNormal =
style=3D'mso-list:l0 level1 lfo2'>In section 3.2 item c you have =
&#8220;for for&#8221;<o:p></o:p></li></ol><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>
------=_NextPart_000_07CE_01CF3166.28602AD0--


From nobody Mon Feb 24 03:54:59 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 1086F1A0091; Mon, 24 Feb 2014 03:54:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.917
X-Spam-Level: **
X-Spam-Status: No, score=2.917 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DhPCwfbtiJ9y; Mon, 24 Feb 2014 03:54:56 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 7F23B1A0348; Mon, 24 Feb 2014 03:54:56 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1OBsroC024140; Mon, 24 Feb 2014 11:54:53 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1OBsoUa024118 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 24 Feb 2014 11:54:52 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Roni Even'" <ron.even.tlv@gmail.com>, <draft-ietf-mpls-special-purpose-labels.all@tools.ietf.org>
References: <07cd01cf3155$64d69780$2e83c680$@gmail.com>
In-Reply-To: <07cd01cf3155$64d69780$2e83c680$@gmail.com>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-special-purpose-labels-05
Date: Mon, 24 Feb 2014 11:54:51 -0000
Message-ID: <074c01cf3157$3b8b3b90$b2a1b2b0$@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: AQI/FAznYkcQkSVfLg/s3RCyC/ms/Jnkg8nQ
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wwb4vUJFiHlinl2b2tG25AwlTiY
Cc: gen-art@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: Mon, 24 Feb 2014 11:54:58 -0000

Hi Roni,

Thanks for taking the time.

> Minor issues:
> 1. In section 3.2 (a):=A0 I noticed that the policy to update the =
registry
according
>=A0 to section 5 is standard action so it should be the same here since =
this is
an
> update to the registry.

Hmmm, but I don't think so.
Section 5 (and the existing registry) define the procedures to be used =
for
assigning new values from a namespace per 5226. Procedures for
retiring/deprecating values are rarely, if ever, documented and do not =
need to
follow the same rules as are used for assignments.

That said, I think I can see some value in symmetry. but it seems a bit =
OTT to
have a Standards Track RFC saying "this code point is not used". What is =
certain
(and we appear to agree on this) is that IETF consensus is needed =
(presumably as
tested by IETF last call on the relevant I-D).

Since we disagree, but my disagreement is not too strong, I will be =
guided by
the IESG (and specifically our sponsoring AD) as to whether to change:
OLD
       An RFC with at
       least Informational status is required.
NEW
      A Standards=20
      Track RFC is required.
END

> Nits/editorial comments:
> 1. In section 3 last sentence =93This answer to this=94 should be =
=93The ..=94

Ack

> 2. In section 3.2 item c you have =93for for=94

Ack

Cheers,
Adrian


From nobody Mon Feb 24 05:37:05 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 B6C231A040E; Mon, 24 Feb 2014 05:37:02 -0800 (PST)
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 23BWA3RQr3hz; Mon, 24 Feb 2014 05:36:58 -0800 (PST)
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 54C7E1A085C; Mon, 24 Feb 2014 05:36:58 -0800 (PST)
Received: by mail-ee0-f49.google.com with SMTP id d17so3135753eek.8 for <multiple recipients>; Mon, 24 Feb 2014 05:36:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=9ipil7DZOamQD4kGkOHJ4vrCL3WkxivF+T8B4KO+qe8=; b=OX3KoQQjvX/NizU0iMpR/7BuN0tskJKFF7t3le5gARgY5X/S7QR3zYB9zanwRmDsND PF9P6+SGVAb/ME+TFNXDxeqnzSu74m6g8iJyXTt3i/Jr++e472S42AnrusQIu1STrHQk TVLdtC8DyaoqhzN9L/XjTiZp5kL7D3q/WP/Mkxtz3d1FVD+vDHAyPT6QI8EK/zNaSLfx 59gsF8c3LJruzteMsVeKYWgHHecPfVLlROgc8NFaSKj8U8W99Xh83gRxGTiyhGaQGEOz a4NHcOoVZAXxzQdr1igsriaG7K8HiWqlcnEWWiAvZy+KrcQhrEjUGT251IDBX8vSVU6K sB9A==
X-Received: by 10.15.56.130 with SMTP id y2mr24723407eew.17.1393249017215; Mon, 24 Feb 2014 05:36:57 -0800 (PST)
Received: from RoniE ([109.67.98.212]) by mx.google.com with ESMTPSA id x2sm63872874eeo.8.2014.02.24.05.36.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 24 Feb 2014 05:36:55 -0800 (PST)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: <adrian@olddog.co.uk>, <draft-ietf-mpls-special-purpose-labels.all@tools.ietf.org>
References: <07cd01cf3155$64d69780$2e83c680$@gmail.com> <074c01cf3157$3b8b3b90$b2a1b2b0$@olddog.co.uk>
In-Reply-To: <074c01cf3157$3b8b3b90$b2a1b2b0$@olddog.co.uk>
Subject: RE: Gen-ART LC review of draft-ietf-mpls-special-purpose-labels-05
Date: Mon, 24 Feb 2014 15:36:40 +0200
Message-ID: <080e01cf3165$7adb15f0$709141d0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1255"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI/FAznYkcQkSVfLg/s3RCyC/ms/AEVqdCjmdv0qrA=
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/h5timBbnDPpHHWYMPDByK_V1u20
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: Mon, 24 Feb 2014 13:37:03 -0000

Hi Adrian,
I do not have a strong position on this topic ( I can agree that =
deprecating
a code point is a rare case) , I was wondering why the difference and I =
can
agree with any direction that you will choose about the maturity level
needed
Roni

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: 24 February, 2014 1:55 PM
> To: 'Roni Even'; =
draft-ietf-mpls-special-purpose-labels.all@tools.ietf.org
> Cc: ietf@ietf.org; gen-art@ietf.org
> Subject: RE: Gen-ART LC review of
draft-ietf-mpls-special-purpose-labels-05
>=20
> Hi Roni,
>=20
> Thanks for taking the time.
>=20
> > Minor issues:
> > 1. In section 3.2 (a):=A0 I noticed that the policy to update the
> > registry
> according
> >=A0 to section 5 is standard action so it should be the same here =
since
> >this is
> an
> > update to the registry.
>=20
> Hmmm, but I don't think so.
> Section 5 (and the existing registry) define the procedures to be used =
for
> assigning new values from a namespace per 5226. Procedures for
> retiring/deprecating values are rarely, if ever, documented and do not
need to
> follow the same rules as are used for assignments.
>=20
> That said, I think I can see some value in symmetry. but it seems a =
bit
OTT to
> have a Standards Track RFC saying "this code point is not used". What =
is
certain
> (and we appear to agree on this) is that IETF consensus is needed
(presumably
> as tested by IETF last call on the relevant I-D).
>=20
> Since we disagree, but my disagreement is not too strong, I will be =
guided
by
> the IESG (and specifically our sponsoring AD) as to whether to change:
> OLD
>        An RFC with at
>        least Informational status is required.
> NEW
>       A Standards
>       Track RFC is required.
> END
>=20
> > Nits/editorial comments:
> > 1. In section 3 last sentence =93This answer to this=94 should be =
=93The ..=94
>=20
> Ack
>=20
> > 2. In section 3.2 item c you have =93for for=94
>=20
> Ack
>=20
> Cheers,
> Adrian


From nobody Mon Feb 24 05:38:12 2014
Return-Path: <BECHA@ripe.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 D5BED1A040C for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 05:38:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.253
X-Spam-Level: 
X-Spam-Status: No, score=0.253 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7_HRzIoL1Irk for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 05:38:09 -0800 (PST)
Received: from kaka.ripe.net (kaka.ripe.net [IPv6:2001:67c:2e8:11::c100:1347]) by ietfa.amsl.com (Postfix) with ESMTP id 6143B1A00DE for <ietf@ietf.org>; Mon, 24 Feb 2014 05:38:09 -0800 (PST)
Received: from nene.ripe.net ([193.0.23.10]) by kaka.ripe.net with esmtps (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from <BECHA@ripe.net>) id 1WHvjP-0007py-U5; Mon, 24 Feb 2014 14:38:08 +0100
Received: from s258-sslvpn-1.ripe.net ([193.0.20.231] helo=guest24.guestnet.ripe.net) by nene.ripe.net with esmtp (Exim 4.72) (envelope-from <BECHA@ripe.net>) id 1WHvjP-0005mh-Qj; Mon, 24 Feb 2014 14:38:03 +0100
Message-ID: <530B4B3A.9070705@ripe.net>
Date: Mon, 24 Feb 2014 14:38:02 +0100
From: Vesna Manojlovic <BECHA@ripe.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: "Timothy B. Terriberry" <tterriberry@mozilla.com>,  Jari Arkko <jari.arkko@piuha.net>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Subject: Re: anti-harassment procedures
References: <9985017A-3DCF-476B-A4D2-A2D43B335E6A@piuha.net> <5307FB25.8040806@mozilla.com>
In-Reply-To: <5307FB25.8040806@mozilla.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-RIPE-Spam-Level: ---
X-RIPE-Spam-Report: Spam Total Points:   -3.4 points pts rule name              description ---- ---------------------- ------------------------------------ -1.0 ALL_TRUSTED            Passed through trusted hosts only via SMTP -0.5 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1% [score: 0.0000]
X-RIPE-Signature: 63c376d8fe7b052a5a65f88a9765b61a4738a53b250cc40764779d6d46ffe888
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eO9XwC5MDnfBv0S6k5NNPTYZfEs
Cc: "adrian@olddog.co.uk Farrel" <adrian@olddog.co.uk>, 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: Mon, 24 Feb 2014 13:38:11 -0000

Dear all,

On 22-feb.-14 02:19, Timothy B. Terriberry wrote:
> Jari Arkko wrote:
>> I know this topic is hard to discuss. Hopefully there are very
>> few situations where these procedures are needed, but they are
>> needed. I thank you for your help and respectful input into this
>> difficult but important discussion.
>
> I want to thank the authors, and the Chair, for doing the work to define
> a harassment policy. Even if it is never used, the fact that it exists
> demonstrates a commitment to dealing with harassment complaints in a
> prompt and fair fashion, and that has a positive effect.

In this case, I think that even mere "+1" is important to hear.

+1

In addition to the general gratefulness and congratulations,
I want to say that this procedure will also serve as an example
for other communities - conferences, collaboration bodies and 
hackerspaces, to name just a few that come to mind.

Regards,
Vesna


From nobody Mon Feb 24 06:14:53 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 A7AF21A008D for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 06:14:48 -0800 (PST)
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 w6PvI5ARpB5r for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 06:14:44 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id A24D21A00C5 for <ietf@ietf.org>; Mon, 24 Feb 2014 06:14:44 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1OEEdRD003939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 24 Feb 2014 06:14:42 -0800
Message-ID: <530B5398.7070705@dcrocker.net>
Date: Mon, 24 Feb 2014 06:13:44 -0800
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.3.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, abdussalambaryun@gmail.com, ietf@ietf.org
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk>
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, 24 Feb 2014 06:14:42 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/i8evQ1k23vqkGPHv1mIY7hRL-90
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, 24 Feb 2014 14:14:49 -0000

On 2/23/2014 10:49 PM, l.wood@surrey.ac.uk wrote:
> How many IETF meetings have you attended, and what experience do you base this recommendation on?
...
>> From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun [abdussalambaryun@gmail.com]
>> Sent: 24 February 2014 03:43
>> To: ietf
>> Subject: Policy of WG chairs in organising time for presentations and face2face discussions
  ...
>> I suggest in London that you assign only maximum 10 minutes present per WG draft and maximum 5 minute for individual draft (as limit policy).


I'll suggest that that question is primarily ad hominem and even if it 
weren't, it's not a particularly helpful line of response.  It doesn't 
matter what the background is of the person asking the question.

What matters is whether a rigid rule limiting time per topic is helpful.

I think it isn't.  Some topics require more.  Some require less.

The usual focus in IETF discussions about meeting management is, 
instead, about /how/ time is used, rather than how much of it, notably 
pressing to avoid tutorial or reportorial content, instead focusing on 
discussion of pending items, such as those creating an impasse.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Feb 24 06:37:19 2014
Return-Path: <mary.h.barnes@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 6C7AD1A087C for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 06:37:17 -0800 (PST)
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 BGbYgakHwG9E for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 06:37:13 -0800 (PST)
Received: from mail-vc0-x22e.google.com (mail-vc0-x22e.google.com [IPv6:2607:f8b0:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id A0B991A00C6 for <ietf@ietf.org>; Mon, 24 Feb 2014 06:37:13 -0800 (PST)
Received: by mail-vc0-f174.google.com with SMTP id im17so5741013vcb.5 for <ietf@ietf.org>; Mon, 24 Feb 2014 06:37:12 -0800 (PST)
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=S2xRVmF8rziRMSu+maQj4LaPZJvQxuH8F+xdpcyloc8=; b=b9mT80QyrLz8UmUnVjrXrOqMvTXcNzXqp+VoYAYFf+5T/WRlakXjfRLao7YTievwU8 rVf//HxpKan5PDfHq1mg6XSMyhk2yEDUJV+mTt0u/OC4w5Sj+dPrKz1Ef8kFL/m0Sy6G akEjXWV2yJutgLGaxJ4zPyTiZ8i8Y807J25b1I2mHxTEdVpp4MeB1F0W5v+rXw6nBtM0 eZAViePegSTf0KTAXaSC5rcaWGi02nLjGarpnL3moMyE4sYaZfJ96Qj4aOoreydDY20t FPsZXkmaJFZkK0tmt65vd8l7lqgWJs8Ehuu/Ert3qLLTYfvvJPgLIYQ6flj6yFq870cM 61AQ==
MIME-Version: 1.0
X-Received: by 10.220.84.193 with SMTP id k1mr114847vcl.64.1393252632788; Mon, 24 Feb 2014 06:37:12 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Mon, 24 Feb 2014 06:37:12 -0800 (PST)
In-Reply-To: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com>
Date: Mon, 24 Feb 2014 08:37:12 -0600
Message-ID: <CABmDk8nbo_+3eMkZbaWkFSGNWxD0HrC94xuqKywu_PXnuopnXQ@mail.gmail.com>
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c221c042849704f327e88b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JExuKBvWdUVBidMeY9W60-qyHs4
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, 24 Feb 2014 14:37:18 -0000

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

Abdussalam,

We used this approach in the SIPPING WG for a number of years and it's
really not at all effective.   We ended up with lots of WG documents and
very slow progress because we didn't have time to resolve real issues at
the f2f meetings.

In my experience, a model that allows time for critical issues to be more
thoroughly discussed is much more effective.   As you note 10 minutes would
only allow one to summarize issues and wouldn't allow time for getting WG
input to resolve any of those issues.

Regards,
Mary.


On Sun, Feb 23, 2014 at 9:43 PM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> Dear IETF WGs' Chairs,
>
> I suggest in London that you assign only maximum 10 minutes present per WG
> draft and maximum 5 minute for individual draft (as limit policy). We need
> to use more input and have more face2face (F2F) discussion in our meeting.
> I remember we discussed this before but it will be nice if we know what
> chairs are thinking before few days of the meeting.
>
> Meeting time is money and that we need to improve the use of IETF
> times within F2F WG discussions and decisions.  If an author cannot
> describe issues of draft in 10 minutes then it will be difficult for the
> WG listeners to discuss and make decisions within another 10 minutes per
> item. Please comment.
>
> Best wishes,
>
> Abdussalam
>
> WG Meetings are needed for group interactions and group decisions not
> individual presentations or individual decisions.
>
>

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

<div dir=3D"ltr">Abdussalam,<div><br></div><div>We used this approach in th=
e SIPPING WG for a number of years and it&#39;s really not at all effective=
. =A0 We ended up with lots of WG documents and very slow progress because =
we didn&#39;t have time to resolve real issues at the f2f meetings. =A0</di=
v>
<div><br></div><div>In my experience, a model that allows time for critical=
 issues to be more thoroughly discussed is much more effective. =A0 As you =
note 10 minutes would only allow one to summarize issues and wouldn&#39;t a=
llow time for getting WG input to resolve any of those issues.=A0</div>
<div><br></div><div>Regards,</div><div>Mary.=A0</div></div><div class=3D"gm=
ail_extra"><br><br><div class=3D"gmail_quote">On Sun, Feb 23, 2014 at 9:43 =
PM, Abdussalam Baryun <span dir=3D"ltr">&lt;<a href=3D"mailto:abdussalambar=
yun@gmail.com" target=3D"_blank">abdussalambaryun@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">Dear IETF WGs&#39; Chairs,<div><br></div><di=
v>I suggest in London=A0that you assign only maximum 10 minutes present per=
 WG draft and maximum 5 minute for individual draft (as limit policy).=A0We=
 need to use more input and have more face2face (F2F)=A0discussion in our m=
eeting. I remember we discussed this before but it will be nice if we know =
what chairs are thinking before few days of the meeting.=A0</div>

<div><br></div><div>Meeting=A0time=A0is money and that we need to improve t=
he=A0use of=A0IETF times=A0within F2F=A0WG=A0discussions and decisions.=A0=
=A0If an author cannot describe issues of=A0draft in 10 minutes then it wil=
l be difficult for the WG=A0listeners to discuss and make decisions within =
another 10 minutes per item. Please comment.=A0</div>

<div><br></div><div>Best wishes,</div><div><br></div><div>Abdussalam</div><=
div><br></div><div>WG=A0Meetings are needed for group=A0interactions and gr=
oup decisions=A0not individual=A0presentations or individual decisions.=A0<=
br><br>

</div>
</blockquote></div><br></div>

--001a11c221c042849704f327e88b--


From nobody Mon Feb 24 06:39:03 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 7204D1A0874 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 06:39:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.917
X-Spam-Level: **
X-Spam-Status: No, score=2.917 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Jc7OYR9FyGI for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 06:39:01 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 7271A1A088E for <ietf@ietf.org>; Mon, 24 Feb 2014 06:38:59 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1OEcpKh023919; Mon, 24 Feb 2014 14:38:51 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1OEclOj023802 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 24 Feb 2014 14:38:48 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <dcrocker@bbiw.net>, <l.wood@surrey.ac.uk>, <abdussalambaryun@gmail.com>,  <ietf@ietf.org>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk> <530B5398.7070705@dcrocker.net>
In-Reply-To: <530B5398.7070705@dcrocker.net>
Subject: RE: Policy of WG chairs in organising time for presentations and face2face discussions
Date: Mon, 24 Feb 2014 14:38:47 -0000
Message-ID: <07e201cf316e$235bb510$6a131f30$@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: AQEVViyPGbim3PkmC6gLBP8Xgoj11wL4azGjAdHosdOcEduFQA==
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/GW65ekNGYlN4zBVK6XWjeyEKtFU
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: Mon, 24 Feb 2014 14:39:02 -0000

Abdussalam could usefully clarify whether he means "limit the presentation time
of an I-D" or "limit the time spent on an I-D".

But in either case, I think that I would prefer to see the opposite to such
limitations. I would like to see technical topics that the WG needs to discuss
receive plenty of agenda time (and that to include as much presentation time as
is needed to seed the discussion and explain the authors' and others' positions
on a topic), while I would prefer to avoid presentations of "this is the status
of my draft" and "this is what my draft says" which can be mugged up in advance
by reading the I-Ds.

In fact, I am increasingly weary of catalogues of 5 minute presentations (to the
point of wondering whether to fire chairs for this - RTG Area chairs take note!
:-) I know it is "important" to be on an agenda if you are going to travel to an
IETF meeting. I know it is "important" to show that you are making a
contribution to the WG. But we have to get over it!

Adrian

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Dave Crocker
> Sent: 24 February 2014 14:14
> To: l.wood@surrey.ac.uk; abdussalambaryun@gmail.com; ietf@ietf.org
> Subject: Re: Policy of WG chairs in organising time for presentations and
> face2face discussions
> 
> On 2/23/2014 10:49 PM, l.wood@surrey.ac.uk wrote:
> > How many IETF meetings have you attended, and what experience do you base
> this recommendation on?
> ...
> >> From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun
> [abdussalambaryun@gmail.com]
> >> Sent: 24 February 2014 03:43
> >> To: ietf
> >> Subject: Policy of WG chairs in organising time for presentations and
face2face
> discussions
>   ...
> >> I suggest in London that you assign only maximum 10 minutes present per WG
> draft and maximum 5 minute for individual draft (as limit policy).
> 
> 
> I'll suggest that that question is primarily ad hominem and even if it
> weren't, it's not a particularly helpful line of response.  It doesn't
> matter what the background is of the person asking the question.
> 
> What matters is whether a rigid rule limiting time per topic is helpful.
> 
> I think it isn't.  Some topics require more.  Some require less.
> 
> The usual focus in IETF discussions about meeting management is,
> instead, about /how/ time is used, rather than how much of it, notably
> pressing to avoid tutorial or reportorial content, instead focusing on
> discussion of pending items, such as those creating an impasse.
> 
> d/
> 
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From nobody Mon Feb 24 06:39:25 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 AC4731A0874 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 06:39:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.447
X-Spam-Level: 
X-Spam-Status: No, score=-0.447 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BIavAX2LTT1I for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 06:39:22 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 06ECC1A088E for <ietf@ietf.org>; Mon, 24 Feb 2014 06:39:22 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WHwge-0008bX-AU; Mon, 24 Feb 2014 09:39:16 -0500
Date: Mon, 24 Feb 2014 09:38:58 -0500
From: John C Klensin <john-ietf@jck.com>
To: dcrocker@bbiw.net
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
Message-ID: <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com>
In-Reply-To: <530B5398.7070705@dcrocker.net>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.u k> <530B5398.7070705@dcrocker.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/DuXA7R4wVk95ujxr6c4jSDgKo8Q
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, 24 Feb 2014 14:39:23 -0000

--On Monday, February 24, 2014 06:13 -0800 Dave Crocker
<dhc@dcrocker.net> wrote:

> On 2/23/2014 10:49 PM, l.wood@surrey.ac.uk wrote:
>> How many IETF meetings have you attended, and what experience
>> do you base this recommendation on?
> ...
>>> From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam
>>> Baryun [abdussalambaryun@gmail.com] Sent: 24 February 2014
>>> 03:43
>>> To: ietf
>>> Subject: Policy of WG chairs in organising time for
>>> presentations and face2face discussions
>   ...
>>> I suggest in London that you assign only maximum 10 minutes
>>> present per WG draft and maximum 5 minute for individual
>>> draft (as limit policy).
> 
> 
> I'll suggest that that question is primarily ad hominem and
> even if it weren't, it's not a particularly helpful line of
> response.  It doesn't matter what the background is of the
> person asking the question.

Dave, FWIW, I disagree, both about the "primarily ad hominem"
suggestion and about the comment about background.

If Lloyd had said "you are a known <NegativeCategory>, therefore
your suggestion should be ignored" that would be primarily an ad
hominem attack.  Although Lloyd may have intended it more
harshly (I won't guess at his motivations), the question about
background seems to me to be relevant.  Let me try an analogy
that, given some recent postings, shouldn't be too far afield.
Suppose someone had posted a note to the IETF list or some
meeting list saying "during the upcoming meeting, it is really
important that everyone have a proper traditional English
breakfast".  I'd consider "what background, especially in
nutrition and related fields, do you have that justifies your
giving that advice" to be a perfectly reasonable question.  I'd
consider it even more reasonable if I happened to be aware of
recommendations the UK DEFRA and its predecessors had made about
those breakfasts.

best,
   john

p.s. I agree with your conclusion that the suggestion of a
blanket rule in that area is not useful, I just question your
introduction and assertion that Lloyd's question was improper.




From nobody Mon Feb 24 07:01:38 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 C09071A0033 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 07:01:34 -0800 (PST)
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 cL0hABygWk_Z for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 07:01:32 -0800 (PST)
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 05C8A1A0054 for <ietf@ietf.org>; Mon, 24 Feb 2014 07:01:31 -0800 (PST)
Received: by mail-la0-f49.google.com with SMTP id mc6so2332079lab.8 for <ietf@ietf.org>; Mon, 24 Feb 2014 07:01:30 -0800 (PST)
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; bh=OKq0ACKYKM91ckkDY/OftDLxKYGV3gyy3m8X+EctW6U=; b=QgR/nLfr/fyFrHVZ3nFltTN0JYiJ+Wl/Jc0hhYQGQegVOvTc6vcfE4o6GhaIfntDNu obw7ZA753z+mOm6QkwcG5TjkSycgkJzas62C3OFVp07435+BqvM8NfU4ZjcTYA8e7vIB LvJwzQX59sBivOS5v4vrJtCfmjVDQw5rA+4qq9u0/2S5cjeWd4lNZXHQS1ciw5uvEYrv hQZ7UctENvvIljkYwaQELWp7fYN5Om4sHMQsUW7oeuxdkksxvcbbpfiKy77eVpUY57vp 0O5sTAEZwemBCny9ZKwJ9MS5FKvOa7MhKCGLcGor3wM8DyXXbNj7HluEnUENi5rufc2l gpKQ==
MIME-Version: 1.0
X-Received: by 10.152.28.129 with SMTP id b1mr6282451lah.9.1393254090783; Mon, 24 Feb 2014 07:01:30 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 24 Feb 2014 07:01:30 -0800 (PST)
In-Reply-To: <530B5398.7070705@dcrocker.net>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk> <530B5398.7070705@dcrocker.net>
Date: Mon, 24 Feb 2014 10:01:30 -0500
Message-ID: <CAMm+Lwh1moLvkyoXF_faOxAupSs-kDM0V9DnzVvZ-uGbSM6cfA@mail.gmail.com>
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e0160bde029c15704f3283faf
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uwd8yj3ULU295ze0FpQnqksD9Vg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 15:01:35 -0000

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

On Mon, Feb 24, 2014 at 9:13 AM, Dave Crocker <dhc@dcrocker.net> wrote:
>
> The usual focus in IETF discussions about meeting management is, instead,
> about /how/ time is used, rather than how much of it, notably pressing to
> avoid tutorial or reportorial content, instead focusing on discussion of
> pending items, such as those creating an impasse.


The current arrangements are bogus.

Either cross-WG and cross area participation is useful or it is not.

Case One: Cross area participation is considered useful.

Make time for tutorial and introductory presentations because they are
essential if there is going to be cross-area presentation.

Case Two: Cross area participation is not considered useful.

Make WG sessions a day long and schedule 40 at once, don't expect people to
participate in multiple groups. Just like W3C does it.


I find tutorials very useful because most often the reason that a WG is not
going anyplace or about to make a security blunder it is because the people
involved really don't have a comprehensive grasp of what they are trying to
achieve and how.

There are many people who are very much focused on IETF process and getting
documents published. I don't care about the number of documents published,
I care about the number of people who read and take note of them.


So for example we are holding an opening WG for Trans. Let us imagine that
in one scenario we spend the whole meeting working on drafts and getting
them completed a meeting earlier than otherwise. And in a second scenario
we spend part of the meeting introducing the concepts and as a result get
buy in from the Microsoft or Apple rep who wasn't otherwise planning to
support TRANS because they had their own idea.

Which outcome is to be preferred? I know which I would take.


What might work rather better is if we start using this thing called the
Internet to do the tutorial type stuff. Drafts are good but they don't
necessarily communicate the message effectively. I can't really tell from a
draft whether someone is B/S or not but I'll know it pretty soon in a
presentation. So putting up tutorial type presentations on the YouTube is
one way to offload information.


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

--089e0160bde029c15704f3283faf
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, Feb 24, 2014 at 9:13 AM, Dave Crocker <span dir=3D"ltr">&lt;<a href=3D"=
mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;</span> =
wrote:<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex">

The usual focus in IETF discussions about meeting management is, instead, a=
bout /how/ time is used, rather than how much of it, notably pressing to av=
oid tutorial or reportorial content, instead focusing on discussion of pend=
ing items, such as those creating an impasse.</blockquote>
<div><br></div><div>The current arrangements are bogus.</div><div><br></div=
><div>Either cross-WG and cross area participation is useful or it is not.<=
/div><div><br></div><div>Case One: Cross area participation is considered u=
seful.</div>
<div><br></div><div>Make time for tutorial and introductory presentations b=
ecause they are essential if there is going to be cross-area presentation.<=
/div><div><br></div><div>Case Two: Cross area participation is not consider=
ed useful.</div>
<div><br></div><div>Make WG sessions a day long and schedule 40 at once, do=
n&#39;t expect people to participate in multiple groups. Just like W3C does=
 it.</div><div><br></div><div><br></div><div>I find tutorials very useful b=
ecause most often the reason that a WG is not going anyplace or about to ma=
ke a security blunder it is because the people involved really don&#39;t ha=
ve a comprehensive grasp of what they are trying to achieve and how.</div>
<div><br></div><div>There are many people who are very much focused on IETF=
 process and getting documents published. I don&#39;t care about the number=
 of documents published, I care about the number of people who read and tak=
e note of them.</div>
<div><br></div><div><br></div><div>So for example we are holding an opening=
 WG for Trans. Let us imagine that in one scenario we spend the whole meeti=
ng working on drafts and getting them completed a meeting earlier than othe=
rwise. And in a second scenario we spend part of the meeting introducing th=
e concepts and as a result get buy in from the Microsoft or Apple rep who w=
asn&#39;t otherwise planning to support TRANS because they had their own id=
ea.</div>
<div><br></div><div>Which outcome is to be preferred? I know which I would =
take.</div></div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_e=
xtra"><br></div>What might work rather better is if we start using this thi=
ng called the Internet to do the tutorial type stuff. Drafts are good but t=
hey don&#39;t necessarily communicate the message effectively. I can&#39;t =
really tell from a draft whether someone is B/S or not but I&#39;ll know it=
 pretty soon in a presentation. So putting up tutorial type presentations o=
n the YouTube is one way to offload information.</div>
<div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra"><div><br></=
div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.=
com/</a><br>
</div></div>

--089e0160bde029c15704f3283faf--


From nobody Mon Feb 24 07:40:44 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 45F731A013E for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 07:40:42 -0800 (PST)
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, 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 H3GsKAnh1S9s for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 07:40:40 -0800 (PST)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 225981A0123 for <ietf@ietf.org>; Mon, 24 Feb 2014 07:40:40 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id E0288320594; Mon, 24 Feb 2014 07:40:39 -0800 (PST)
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 39996320590; Mon, 24 Feb 2014 07:40:36 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
From: Thomas Clausen <ietf@thomasclausen.org>
In-Reply-To: <07e201cf316e$235bb510$6a131f30$@olddog.co.uk>
Date: Mon, 24 Feb 2014 16:40:33 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <6098F8AC-8DD7-429F-9F56-CD9B8478D803@thomasclausen.org>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk> <530B5398.7070705@dcrocker.net> <07e201cf316e$235bb510$6a131f30$@olddog.co.uk>
To: Adrian Farrel <adrian@olddog.co.uk>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LpUL_975_I1djuqjn8eHOfQSlMI
Cc: IETF Discussion <ietf@ietf.org>, 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: Mon, 24 Feb 2014 15:40:42 -0000

On 24 Feb 2014, at 15:38, Adrian Farrel <adrian@olddog.co.uk> wrote:

> Abdussalam could usefully clarify whether he means "limit the =
presentation time
> of an I-D" or "limit the time spent on an I-D".
>=20
> But in either case, I think that I would prefer to see the opposite to =
such
> limitations. I would like to see technical topics that the WG needs to =
discuss
> receive plenty of agenda time (and that to include as much =
presentation time as
> is needed to seed the discussion and explain the authors' and others' =
positions
> on a topic), while I would prefer to avoid presentations of "this is =
the status
> of my draft" and "this is what my draft says" which can be mugged up =
in advance
> by reading the I-Ds.
>=20
> In fact, I am increasingly weary of catalogues of 5 minute =
presentations (to the
> point of wondering whether to fire chairs for this - RTG Area chairs =
take note!
> :-) I know it is "important" to be on an agenda if you are going to =
travel to an
> IETF meeting. I know it is "important" to show that you are making a
> contribution to the WG. But we have to get over it!
>=20

Adrian,

I can't speak to the "important to be on the agenda" issue, but I will =
say this:=20

F2f time is too valuable to be spent on issues that could have been =
brought up and (attempted) resolved on the mailing-list, as well as =
presentations that just serve to list "so I changed these 42 things =
since last meeting" summaries. They actually are extremely un-productive =
(although I do get a lot of email processed when sitting through one of =
those) ....especially since RFCDIFF is both more precise, and in colour =
;)

I'd probably prefer that all that could be (attempted) resolved on the =
mailing-list should be (attempted) resolved on the mailing-list - and, =
only if that fails is agenda-time for the f2f sessions warranted - and =
on issues, not on "documents".=20

Useful use of f2f time is also "presenting brand new work" - but only =
once - to gain traction and such in order to take it onto the list.

That said, IETF meetings do punctuate and foster some "sprints to finish =
things before a deadline", and so an overview of status probably is =
appreciated. I believe that this (in some WGs) is very well done by the =
WG chairs in their "WG Status" slot - but, even better, actually =
announced on the list in advance (on that note, I want to tip my hat to =
the ROLL WG chairs here: Ines and Michael have whipped their WG to =
submitting slides already, constructed a complete deck for the whole =
meeting, and prepared a handful or so of slides listing the "status": =
active documents, open issues, related, for the beginning - close to =
perfect organisation ...).

One other thing that I occasionally find useful to spend F2F time on: =
summarising out-of-band discussions such as what often happens through =
IESG reviews, especially if managing to get the AD in question to show =
up and argue her/his points.

Best,

Thomas

> Adrian
>=20
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Dave Crocker
>> Sent: 24 February 2014 14:14
>> To: l.wood@surrey.ac.uk; abdussalambaryun@gmail.com; ietf@ietf.org
>> Subject: Re: Policy of WG chairs in organising time for presentations =
and
>> face2face discussions
>>=20
>> On 2/23/2014 10:49 PM, l.wood@surrey.ac.uk wrote:
>>> How many IETF meetings have you attended, and what experience do you =
base
>> this recommendation on?
>> ...
>>>> From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun
>> [abdussalambaryun@gmail.com]
>>>> Sent: 24 February 2014 03:43
>>>> To: ietf
>>>> Subject: Policy of WG chairs in organising time for presentations =
and
> face2face
>> discussions
>>  ...
>>>> I suggest in London that you assign only maximum 10 minutes present =
per WG
>> draft and maximum 5 minute for individual draft (as limit policy).
>>=20
>>=20
>> I'll suggest that that question is primarily ad hominem and even if =
it
>> weren't, it's not a particularly helpful line of response.  It =
doesn't
>> matter what the background is of the person asking the question.
>>=20
>> What matters is whether a rigid rule limiting time per topic is =
helpful.
>>=20
>> I think it isn't.  Some topics require more.  Some require less.
>>=20
>> The usual focus in IETF discussions about meeting management is,
>> instead, about /how/ time is used, rather than how much of it, =
notably
>> pressing to avoid tutorial or reportorial content, instead focusing =
on
>> discussion of pending items, such as those creating an impasse.
>>=20
>> d/
>>=20
>> --
>> Dave Crocker
>> Brandenburg InternetWorking
>> bbiw.net
>=20


From nobody Mon Feb 24 08:07:50 2014
Return-Path: <derhoermi@gmx.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 0E48C1A0169 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 08:07:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.548
X-Spam-Level: 
X-Spam-Status: No, score=-0.548 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VC-Iaqeu6UwS for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 08:07:45 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) by ietfa.amsl.com (Postfix) with ESMTP id 01FBF1A0159 for <ietf@ietf.org>; Mon, 24 Feb 2014 08:07:44 -0800 (PST)
Received: from netb ([47.65.157.53]) by mail.gmx.com (mrgmx101) with ESMTPSA (Nemesis) id 0MIzGn-1WFU9v328f-002YqE for <ietf@ietf.org>; Mon, 24 Feb 2014 17:07:42 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: ietf@ietf.org
Subject: WG name on I-D front matter (1id-guidelines.txt)
Date: Mon, 24 Feb 2014 17:07:55 +0100
Message-ID: <7jqmg91nqgje8v58t95je13de4kb9s72rj@hive.bjoern.hoehrmann.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:T/p76Z0Wdr4pi7DvuRr1l1BJkP6vsqeaiUuSR9XMOgfQ/W+XAHo /gKm4FMIW+b2fNBoCJcpRP0SR/HcVkw0YMPtyaJmQO2VUKcVaYch6/TR+vnUpCZhRvKrnmP wKJ84GY1cUwNe3jpqVsoYKBRA1jhk6AtX13JMQ5gSjhG7hEjtbXPuZzQ1t9Y1ZVxFs0R5iY THno6eY/+GobgntvlnQsg==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/H91zUl2ydCaYMCEy8WaAc4qTOsI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 16:07:48 -0000

Hi,

  http://www.ietf.org/ietf-ftp/1id-guidelines.txt in the 7 December 2010
version says 

   There are differences between the RFC and I-D format.  I-Ds are NOT
   RFCs, and I-Ds are NOT a numbered document series.  The label
   "INTERNET-DRAFT" should appear in the upper left hand corner of the
   first page.  If the I-D is associated with an IETF working group, the
   name of the working group should appear on the line below the
   "INTERNET-DRAFT" label.  The document should NOT refer to itself as
   an RFC or a draft RFC.

The Working Group name appears in the upper left hand corner of the
first page ABOVE and before the "Internet-Draft" label.

(I checked this because some assume when a WG name appears in that spot
then a Working Group has chosen to publish the document, while others
assume I-D authors can put any Working Group name they find suitable
there, making it hard for outsiders to tell individual submissions and
documents that have gained some level of Working Group consensus apart).

regards,
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 


From nobody Mon Feb 24 08:40: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 80FAF1A01F7 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 08:40:20 -0800 (PST)
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 7p-J-AyQ9JL8 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 08:40:19 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BA3761A018C for <ietf@ietf.org>; Mon, 24 Feb 2014 08:40:18 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1OGeAQT007142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 24 Feb 2014 08:40:14 -0800
Message-ID: <530B75B3.7000300@dcrocker.net>
Date: Mon, 24 Feb 2014 08:39:15 -0800
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.3.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.u k> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com>
In-Reply-To: <AF345D44D8B66B87E09D9256@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]); Mon, 24 Feb 2014 08:40:17 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9Uva4YXVbKANw6keh1JzpChzCb4
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, 24 Feb 2014 16:40:20 -0000

On 2/24/2014 6:38 AM, John C Klensin wrote:

> --On Monday, February 24, 2014 06:13 -0800 Dave Crocker
> <dhc@dcrocker.net> wrote:
>> I'll suggest that that question is primarily ad hominem and
>> even if it weren't, it's not a particularly helpful line of
>> response.  It doesn't matter what the background is of the
>> person asking the question.
>
> Dave, FWIW, I disagree, both about the "primarily ad hominem"
> suggestion and about the comment about background.

If you or I had made the suggestion, would that affect its merit?  We 
have extensive IETF meeting experience, but that's irrelevant.

If it's a good suggestion, it doesn't matter who made it.

If it's a bad suggestion, it doesn't matter who made it.

By publicly asking about the background of the person making the 
suggestion, the public exchange moves from the merits of the suggestion 
to the merits of the person making the suggestion.

Moving focus off of the substance and to the speaker is the essence of 
ad hominem.  It either explicitly or implicitly is asserting that the 
nature of the speaker affects the merit of what is spoken, with the 
usual implication that the speaker and their suggestion should be 
discounted.


> If Lloyd had said "you are a known <NegativeCategory>, therefore
> your suggestion should be ignored" that would be primarily an ad
> hominem attack.

So it isn't ad hominem unless it is a direct, frontal and coarse 
assertion of the false factor?  If it is only implied, it doesn't count?


>        the question about
> background seems to me to be relevant.  Let me try an analogy
> that, given some recent postings, shouldn't be too far afield.
> Suppose someone had posted a note to the IETF list or some
> meeting list saying "during the upcoming meeting, it is really
> important that everyone have a proper traditional English
> breakfast".  I'd consider "what background, especially in
> nutrition and related fields,

You are confusing substance with person.

The question that was asked was not "what is the basis for the 
recommendation" but "what is your experience with our meetings".  The 
former is substance and reasonable.  The latter is personal and not.

And this was done in public as an immediate response and without any 
other context.

We make this confusion quite a lot in the IETF.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Feb 24 08:49:38 2014
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDB801A00FD for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 08:49:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.253
X-Spam-Level: 
X-Spam-Status: No, score=0.253 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id oL1vmIGn8foH for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 08:49:34 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id 6DFE21A00F4 for <ietf@ietf.org>; Mon, 24 Feb 2014 08:49:34 -0800 (PST)
Received: from [192.168.1.110] (90-227-238-197-no15.business.telia.com [90.227.238.197]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id C5FF0180156A; Mon, 24 Feb 2014 17:49:31 +0100 (CET)
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk> <530B5398.7070705@dcrocker.net>
In-Reply-To: <530B5398.7070705@dcrocker.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <F4A59F40-EDBE-4E73-BFE1-4CB5E68B64BC@pi.nu>
X-Mailer: iPad Mail (11B651)
From: Loa Andersson <loa@pi.nu>
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
Date: Mon, 24 Feb 2014 17:49:31 +0100
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VbiX5MUZhhfrZ7FrEM015FGOVzk
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, 24 Feb 2014 16:49:37 -0000

Sent from my iPad

> On Feb 24, 2014, at 15:13, Dave Crocker <dhc@dcrocker.net> wrote:
>=20
>> On 2/23/2014 10:49 PM, l.wood@surrey.ac.uk wrote:
>> How many IETF meetings have you attended, and what experience do you base=
 this recommendation on?
> ...
>>> From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun [abdus=
salambaryun@gmail.com]
>>> Sent: 24 February 2014 03:43
>>> To: ietf
>>> Subject: Policy of WG chairs in organising time for presentations and fa=
ce2face discussions
> ...
>>> I suggest in London that you assign only maximum 10 minutes present per W=
G draft and maximum 5 minute for individual draft (as limit policy).
>=20
>=20
> I'll suggest that that question is primarily ad hominem and even if it wer=
en't, it's not a particularly helpful line of response.  It doesn't matter w=
hat the background is of the person asking the question.
>=20
> What matters is whether a rigid rule limiting time per topic is helpful.
>=20
> I think it isn't.  Some topics require more.  Some require less.
>=20
> The usual focus in IETF discussions about meeting management is, instead, a=
bout /how/ time is used, rather than how much of it, notably pressing to avo=
id tutorial or reportorial content, instead focusing on discussion of pendin=
g items, such as those creating an impasse.
>=20
> d/
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


Dave,

While I agree mostly on the line of your response I think that it was not a "=
question" but formulated as an "advise" and coming from someone that we all k=
now have not planned any wg agendas. Of course this does not disqualify him,=
 but if he is at odds with experienced people we should take such advice wit=
h more than a spoonful of salt (is that an English proverb).=20

/Loa
>=20


From nobody Mon Feb 24 08:53:41 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 251621A0145 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 08:53:40 -0800 (PST)
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 OBDQgGlzcgRg for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 08:53:38 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id BAA671A0129 for <ietf@ietf.org>; Mon, 24 Feb 2014 08:53:38 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1OGrX8V007402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 24 Feb 2014 08:53:37 -0800
Message-ID: <530B78D6.20401@dcrocker.net>
Date: Mon, 24 Feb 2014 08:52:38 -0800
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.3.0
MIME-Version: 1.0
To: Loa Andersson <loa@pi.nu>
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk> <530B5398.7070705@dcrocker.net> <F4A59F40-EDBE-4E73-BFE1-4CB5E68B64BC@pi.nu>
In-Reply-To: <F4A59F40-EDBE-4E73-BFE1-4CB5E68B64BC@pi.nu>
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, 24 Feb 2014 08:53:38 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uJpuhmkA2NgUVxvh3sp5ykPBjZ8
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: Mon, 24 Feb 2014 16:53:40 -0000

On 2/24/2014 8:49 AM, Loa Andersson wrote:
> While I agree mostly on the line of your response I think that it was not a "question" but formulated as an "advise" and coming from someone that we all know have not planned any wg agendas. Of course this does not disqualify him, but if he is at odds with experienced people we should take such advice with more than a spoonful of salt (is that an English proverb).


Then the note should have been sent privately.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Feb 24 08:56:12 2014
Return-Path: <apvelan.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 3EF611A01F7; Mon, 24 Feb 2014 08:38:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level: 
X-Spam-Status: No, score=-1.299 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, GB_I_INVITATION=-2, 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 w4IMkS1fQUqH; Mon, 24 Feb 2014 08:38:37 -0800 (PST)
Received: from mail-bk0-x235.google.com (mail-bk0-x235.google.com [IPv6:2a00:1450:4008:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id 2EF8D1A01E9; Mon, 24 Feb 2014 08:38:37 -0800 (PST)
Received: by mail-bk0-f53.google.com with SMTP id my13so1972240bkb.12 for <multiple recipients>; Mon, 24 Feb 2014 08:38:36 -0800 (PST)
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; bh=6cuLjym7+FbDFk234MuP9xjX5ggwLngOAmWOurfNDAI=; b=KCg0tX6QcDEMSGf2NRVd7gayQsIrA+3E2TaVLv5anuFGeFDXpMiV1SkbVuX4cfjV+j XeCEZqbW/hXWn7MhPDHKSPHoK2fXc4QTFC94W3GAFxF0cyxiXOTZHR4m75BMDmLw2T9K r6TxsU2XAX85F/ZKis8RV3C1WZqok0HB7j7IjRAmLKyEgX5e8F24EAfRocPP6mSMq3JB WCHlketwjFLuq0VpFB0UA2hjbkqc5tYNEMC8Z+XwIEwQajxsycww06CtIWQ2bq4ZvNmM nIb1+/er59SOLsgu98NNalt+YGfejyUIjhoEBk+J6WBp8rtac5jPbHh4GLDLHvmEYxxE yk2A==
MIME-Version: 1.0
X-Received: by 10.204.66.142 with SMTP id n14mr79368bki.90.1393259916024; Mon, 24 Feb 2014 08:38:36 -0800 (PST)
Received: by 10.204.242.3 with HTTP; Mon, 24 Feb 2014 08:38:35 -0800 (PST)
In-Reply-To: <20140220055504.7370.22981.idtracker@ietfa.amsl.com>
References: <20140220055504.7370.22981.idtracker@ietfa.amsl.com>
Date: Mon, 24 Feb 2014 22:08:35 +0530
Message-ID: <CABWJYqfr=hh9thaiUc3oJJrRT=JxNxMvRO3DJ5bgAZQoC=7H_A@mail.gmail.com>
Subject: Re: [89all] Invitation to Participate in Mentoring Program
From: Palanivelan Appanasamy <apvelan.ietf@gmail.com>
To: ietf@ietf.org, mentoring-coordinators@ietf.org
Content-Type: multipart/alternative; boundary=001a1132f6cc600e5b04f3299a18
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/UwOXZZxMf1YF0TLxQqPVrurLMkU
X-Mailman-Approved-At: Mon, 24 Feb 2014 08:56:08 -0800
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 16:38:40 -0000

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

Hi,

I like to participate in the mentoring program and here are my details:

Full name: PALANIVELAN APPANASAMY
Email address: apvelan.ietf@gmail.com
Affiliation: DMTS, VERIZON LABS
Country in which you are based: INDIA
Gender: MALE
Are you attending the upcoming IETF meeting in person (note that the
mentoring program is only open to in-person attendees at this time)? YES
Will this meeting be the first IETF meeting that you attend in person? NO
If not, how many IETF meetings have you attended? 03, This will be my
fourth.
What technical topic(s) brought you to the IETF? ROUTING,BFD, L4-L7
IETF area(s) of interest, if known (see
http://www.ietf.org/iesg/area.htmlfor more info): bfd, transport,
applications
IETF working groups of interest, if known: (see http://www.ietf.org/wg/ for
more info): rtg-bfd, httpbis, mptcp
What other SDOs and/or technical activities do you engage in? have couple
of drafts on bfd, one archived after iesg review.
What are your preferred conversational language(s), if not English?
ENGLISH, TAMIL
Would you like to be paired with a mentor who speaks your preferred
language(s), if possible? [Yes/No/Indifferent] -
Do you have a preference as to your mentor's gender? [M/F/Either] Either
Do you plan to attend the newcomers' meet-and-greet on Sunday at 16:00? YES
Do you plan to attend the welcome reception on Sunday at 17:00? YES
Any other info you'd like to share:
I work as a Distinguished MTS Engr. with Verizon Labs. I have previously
worked with Motorola, Lucent, Juniper, Cisco and EMC in their frontline
product engineering teams and been engaged with IETF activities since 2009.
I am a Internet society returning fellow and ietf89 will be my fourth IETF.
I look forward to mentoring new comers @IETF.


Thanks and Regards,
A.Palanivelan


On Thu, Feb 20, 2014 at 11:25 AM, IETF Chair <chair@ietf.org> wrote:

> All,
>
> At IETF 89 we will once again offer the IETF Mentoring Program. The goal
> of the IETF Mentoring Program is to match IETF participants who may be new
> or otherwise in need of guidance with experienced IETF mentors. As a
> mentoring participant, your mentor will personally introduce you to the
> IETF community, help you find your way around the IETF & the meeting,
> explain things, and introduce you to other attendees you might like to
> meet. Basically, your mentor will be your personal buddy during the
> meeting week, and possibly afterwards.
>
> Unlike in the past, at IETF 89 we will accept requests for mentors from
> anyone who wants one, regardless of how many meetings they have attended
> previously. We cannot guarantee that every request will be honored, but we
> will do our best.
>
> If you wish to participate in the IETF Mentoring Program, you can follow
> the sign-up procedures described in the program FAQ:
>
> https://www.ietf.org/resources/mentoring-program.html
>
> After you follow the sign-up procedure, we will introduce you to your
> mentor by email prior to IETF 89, and invite you to meet up in person at
> the IETF Meet & Greet event on Sunday afternoon in London. From there on,
> you and your mentor decide on when and where to meet during the rest of
> the week and afterwards.
>
> You are of course free to withdraw from the program at any time and for
> any reason, no questions asked, should a need arise. But I sincerely
> believe the IETF Mentoring Program will be a great way for new
> participants to get introduced to the IETF by an experienced participant
> with matching interest.
>
> Regards,
> Jari Arkko
> IETF Chair
>
> _______________________________________________
> 89all mailing list
> 89all@ietf.org
> https://www.ietf.org/mailman/listinfo/89all
>

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

<div dir=3D"ltr"><div><div>Hi, <br><br></div>I like to participate in the m=
entoring program and here are my details:<br><br>Full name: PALANIVELAN APP=
ANASAMY<br>Email address: <a href=3D"mailto:apvelan.ietf@gmail.com">apvelan=
.ietf@gmail.com</a><br>
Affiliation: DMTS, VERIZON LABS<br>Country in which you are based: INDIA<br=
>Gender: MALE<br>Are you attending the upcoming IETF meeting in person (not=
e that the mentoring program is only open to in-person attendees at this ti=
me)? YES<br>
Will this meeting be the first IETF meeting that you attend in person? NO<b=
r>If not, how many IETF meetings have you attended? 03, This will be my fou=
rth.<br>What technical topic(s) brought you to the IETF? ROUTING,BFD, L4-L7=
<br>
IETF area(s) of interest, if known (see <a href=3D"http://www.ietf.org/iesg=
/area.html">http://www.ietf.org/iesg/area.html</a> for more info): bfd, tra=
nsport, applications<br>IETF working groups of interest, if known: (see <a =
href=3D"http://www.ietf.org/wg/">http://www.ietf.org/wg/</a> for more info)=
: rtg-bfd, httpbis, mptcp<br>
What other SDOs and/or technical activities do you engage in? have couple o=
f drafts on bfd, one archived after iesg review.<br>What are your preferred=
 conversational language(s), if not English? ENGLISH, TAMIL<br>Would you li=
ke to be paired with a mentor who speaks your preferred language(s), if pos=
sible? [Yes/No/Indifferent] -<br>
Do you have a preference as to your mentor&#39;s gender? [M/F/Either] Eithe=
r<br>Do you plan to attend the newcomers&#39; meet-and-greet on Sunday at 1=
6:00? YES<br>Do you plan to attend the welcome reception on Sunday at 17:00=
? YES<br>
Any other info you&#39;d like to share:<br></div>I work as a Distinguished =
MTS Engr. with Verizon Labs. I have previously worked with Motorola, Lucent=
, Juniper, Cisco and EMC in their frontline product engineering teams and b=
een engaged with IETF activities since 2009. I am a Internet society return=
ing fellow and ietf89 will be my fourth IETF. I look forward to mentoring n=
ew comers @IETF.<br>
<div><div><div><br><br></div><div>Thanks and Regards,<br>A.Palanivelan<br><=
/div></div></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gma=
il_quote">On Thu, Feb 20, 2014 at 11:25 AM, IETF Chair <span dir=3D"ltr">&l=
t;<a href=3D"mailto:chair@ietf.org" target=3D"_blank">chair@ietf.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">All,<br>
<br>
At IETF 89 we will once again offer the IETF Mentoring Program. The goal<br=
>
of the IETF Mentoring Program is to match IETF participants who may be new<=
br>
or otherwise in need of guidance with experienced IETF mentors. As a<br>
mentoring participant, your mentor will personally introduce you to the<br>
IETF community, help you find your way around the IETF &amp; the meeting,<b=
r>
explain things, and introduce you to other attendees you might like to<br>
meet. Basically, your mentor will be your personal buddy during the<br>
meeting week, and possibly afterwards.<br>
<br>
Unlike in the past, at IETF 89 we will accept requests for mentors from<br>
anyone who wants one, regardless of how many meetings they have attended<br=
>
previously. We cannot guarantee that every request will be honored, but we<=
br>
will do our best.<br>
<br>
If you wish to participate in the IETF Mentoring Program, you can follow<br=
>
the sign-up procedures described in the program FAQ:<br>
<br>
<a href=3D"https://www.ietf.org/resources/mentoring-program.html" target=3D=
"_blank">https://www.ietf.org/resources/mentoring-program.html</a><br>
<br>
After you follow the sign-up procedure, we will introduce you to your<br>
mentor by email prior to IETF 89, and invite you to meet up in person at<br=
>
the IETF Meet &amp; Greet event on Sunday afternoon in London. From there o=
n,<br>
you and your mentor decide on when and where to meet during the rest of<br>
the week and afterwards.<br>
<br>
You are of course free to withdraw from the program at any time and for<br>
any reason, no questions asked, should a need arise. But I sincerely<br>
believe the IETF Mentoring Program will be a great way for new<br>
participants to get introduced to the IETF by an experienced participant<br=
>
with matching interest.<br>
<br>
Regards,<br>
Jari Arkko<br>
IETF Chair<br>
<br>
_______________________________________________<br>
89all mailing list<br>
<a href=3D"mailto:89all@ietf.org">89all@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/89all" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/89all</a><br>
</blockquote></div><br></div>

--001a1132f6cc600e5b04f3299a18--


From nobody Mon Feb 24 08:56:27 2014
Return-Path: <dafalla@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 D4FB41A0279 for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 06:14:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.647
X-Spam-Level: 
X-Spam-Status: No, score=-0.647 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, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.548] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h_43rZY7GAnL for <ietf@ietfa.amsl.com>; Fri, 21 Feb 2014 06:14:03 -0800 (PST)
Received: from nm18-vm0.bullet.mail.bf1.yahoo.com (nm18-vm0.bullet.mail.bf1.yahoo.com [98.139.213.138]) by ietfa.amsl.com (Postfix) with ESMTP id E48B41A022F for <ietf@ietf.org>; Fri, 21 Feb 2014 06:14:02 -0800 (PST)
Received: from [98.139.212.152] by nm18.bullet.mail.bf1.yahoo.com with NNFMP;  21 Feb 2014 14:13:58 -0000
Received: from [98.139.212.194] by tm9.bullet.mail.bf1.yahoo.com with NNFMP; 21 Feb 2014 14:13:58 -0000
Received: from [127.0.0.1] by omp1003.mail.bf1.yahoo.com with NNFMP; 21 Feb 2014 14:13:58 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 814426.44126.bm@omp1003.mail.bf1.yahoo.com
Received: (qmail 2713 invoked by uid 60001); 21 Feb 2014 14:13:58 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1392992038; bh=mIJvNSDJky+we7Uju1awb+jYSBUqUAstczMSIUIDBBU=; 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=SkNhqKoPcoU34OH7buOGFply8jWgI1CCQyrtKHyRunMlOEkDwHwBQrCUeNiS1YlV3crH7CuDO5w5FuTStKSvVVQdqIQforXPCLzgk8wkPmXwo+7Be9FSEpd8rER492H8m1IEzIjBb+LtRyPrNYUhWVBLyuVhOJbBUsuxV7TogrU=
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=mLlXx0KFXBO6yZBkjh3OOJTpUhjA8zg7CLLb7Gnb/J4cw0aS27m104zpkEpm/WEOAVFcy1IojygPkFhNY3AhGUlr7vFlS29IZMk0CBzcDERzuW4cm+MjOjVA73T/3UjExN/V0RwdOtVRnEUFlFylwiPe+dQCXNXiME/XbDE3+qg=;
X-YMail-OSG: jnEeSUkVM1kSU0yn91NOtwXugCe5kWfePb8cbtOzpzvVVYy AwPz3kMVqPnr83DU1uwbUtCTWxSuQKWkcuEYNM9tgj8.0aITfQ.Vd1fVcH7L .a0ybHWN5eey1Riy2B_VNvvZL3QeyHppan29NJj_bVN6tE0zpLs_.DbGrcgI b15e75sn6chYldiDYXHCH.Dvtb3ItLhO9.EpNqkpQlyYsdI9WArXw8Vmk3LM X6Cz4LMl98_ylrqGDMHotadu7wfcpAMBWsTKxXHxcUrS0rw1FPL_SPMOBq6X FpDyBwAPF7FazLW.2c1LiueeaeTy7kOt_cIq.hB4RbwLVvrF8FoZ_ojysSqZ UJFHDwlXxv0PjlrvXZDzogzbryIPEBlLVCK1cv2QlbchVtntJPj26W7wmr9g O6BANmsO3qV4YKpb3Zh.PbeEplN4YB8mtCpyptZRTPZGJteUZZD5vA1yBPq5 _vGyY8bPrQRDcCZFNPOQ3ANo41JMxK3BPdHYsKzBpz6sV0sB0qdDXubT66J4 xBl66DbJz1JhykQ4MmtskF6L2X9PY4oQXEfKPkzZqt9.kagUUq5q0sTx.kko 0VrEcVK8k16BOZxuLQSeRVN0QLp5uheFnt6h4MwKykWi6z2WjEStS_EKyLa0 h6mRSPsylwmPJAiqXvZY_kOme77tXT0FqLOZJsjqRgmH29S0Dh4zc859qVEl YJ8ga4aECTQ1Zlb_opV5RQw--
Received: from [46.16.33.120] by web160101.mail.bf1.yahoo.com via HTTP; Fri, 21 Feb 2014 06:13:58 PST
X-Rocket-MIMEInfo: 002.001, RGVhciBSdXNzIEhvdXNsZXk7CgrCoMKgIFRoYW5rIHlvdSB2ZXJ5IG11Y2ggZm9yIHlvdXIgbWVzc2FnZS4gQ2FuIEkgaGF2ZSBhIGNoYW5jZSB0byBub21pbmF0ZSBteSBzZWxmIG9yIHRoaXMgcG9zaXRpb24gaXMgY2xvc2VkIGZvciBJQUIgbWVtYmVyLsKgIFBsZWFzZSByZXBseSBjb25maXJtLgoKCgpUaGFua3MKCkhhZ28gRGFmYWxsYQpTdWRhbgoKCgoKCk9uIFdlZG5lc2RheSwgMTkgRmVicnVhcnkgMjAxNCwgMTk6NDEsIElBQiBDaGFpciA8aWFiLWNoYWlyQGlhYi5vcmc.IHdyb3RlOgogClRoaXMgaXMBMAEBAQE-
X-Mailer: YahooMailWebService/0.8.177.636
References: <2771279D-9BDD-46CE-88F5-0728F1B35CBE@iab.org> <4BFB41C0-F18B-44BA-9E8A-D94AA6212088@iab.org>
Message-ID: <1392992038.55876.YahooMailNeo@web160101.mail.bf1.yahoo.com>
Date: Fri, 21 Feb 2014 06:13:58 -0800 (PST)
From: Hago Dafalla <dafalla@yahoo.com>
Subject: Re: Reminder: Call for nominations: IETF appointment to the ISOC Board of Trustees
To: "ietf@ietf.org" <ietf@ietf.org>, IAB <iab@iab.org>
In-Reply-To: <4BFB41C0-F18B-44BA-9E8A-D94AA6212088@iab.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="1439723771-2089239970-1392992038=:55876"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/z3sGSGUwBvkb89Te8dZZdqTeAbw
X-Mailman-Approved-At: Mon, 24 Feb 2014 08:56:22 -0800
Cc: "dafalla@yahoo.com" <dafalla@yahoo.com>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Hago Dafalla <dafalla@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: Fri, 21 Feb 2014 14:14:06 -0000

--1439723771-2089239970-1392992038=:55876
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear Russ Housley;=0A=0A=A0=A0 Thank you very much for your message. Can I =
have a chance to nominate my self or this position is closed for IAB member=
.=A0 Please reply confirm.=0A=0A=0A=0AThanks=0A=0AHago Dafalla=0ASudan=0A=
=0A=0A=0A=0A=0AOn Wednesday, 19 February 2014, 19:41, IAB Chair <iab-chair@=
iab.org> wrote:=0A =0AThis is a reminder that the IAB is seeking nomination=
s for one seat on the ISOC Board of Trustees.=A0 The nominations period is =
unchanged, and nominations close on February 27th.=0A=0AOn behalf of the IA=
B,=0ARuss Housley=0AIAB Chair=0A=0A=0A=0AOn Jan 30, 2014, at 10:13 AM, IAB =
Chair wrote:=0A=0A> =0A> The Internet Society (ISOC) provides organizationa=
l and financial support for the IETF. As part of the arrangements between I=
SOC and the IETF, the IETF is called upon to name 3 Trustees to its Board (=
BoT), with staggered 3 year terms. This requires that the IETF select one T=
rustee each year. =0A> =0A> This year, the IAB will select one person for a=
 term ending in mid-2017. =0A> =0A> A description of the IAB's process for =
selecting the Trustee each year can be found in RFC 3677, with this year's =
timeline as follows: =0A> =0A> * January 30, 2014 : Open nomination period=
=0A> =0A> * February 27, 2014 : Close of the nomination period =0A> =0A> * =
No later than April 10, 2014 : IAB selection delivered to IESG for confirma=
tion=0A> =0A> * No later than May 23, 2014 : Delivery of final confirmed se=
lection to the ISOC Elections Committee for announcement with the rest of t=
he new ISOC BoT slate. =0A> =0A> =0A> Nominations =0A> ----------- =0A> =0A=
> Nominations (including self-nominations) should be sent to the IAB -- iab=
@iab.org.=A0 Please include e-mail contact details with the nomination. =0A=
> =0A> Nomination Details =0A> ----------------- =0A> =0A> Nominees should =
be aware that ISOC Trustees are elected to three year terms with approximat=
ely one third of the Board of Trustees elected each year. The responsibilit=
ies of a Trustee include fiscal management of the Internet Society, fundrai=
sing, and participation in Board meetings plus conference-call meetings, as=
 detailed by the ISOC Bylaws:=0A> http://www.internetsociety.org/who-we-are=
/governance-and-policies/amended-and-restated-laws-internet-society=0A> =0A=
> The desirable characteristics of a candidate that are specific to the IET=
F-selected ISOC BoT member are outlined in section 2 of RFC 3677. =0A> =0A>=
 Nominees are asked to provide to the IAB: =0A> =0A> 1. Confirmation of the=
ir willingness to be considered within this process. =0A> =0A> 2. Full name=
 and contact information. =0A> =0A> 3. A statement confirming willingness a=
nd ability to devote an appropriate level of time to activities associated =
with the position of Trustee. =0A> =0A> 4. A brief biography outlining expe=
rience and background. =0A> =0A> 5. A statement of interests, concerns abou=
t the Internet Society, goals as a Trustee, and motivation to serve as a Tr=
ustee. =0A> =0A> 6. Any further information that is relevant to the work of=
 the IAB in considering your nomination. =0A> =0A> Time Commitment =0A> ---=
------------ =0A> =0A> Trustees are expected to commit the time necessary t=
o perform regular board and committee business. Trustees are also expected =
to allocate some time to attend and prepare for meetings. =0A> =0A> =0A> Ca=
re of Personal Information =0A> ---------------------------- =0A> =0A> The =
following procedures will be used by the IAB in managing this process: =0A>=
 =0A> - The candidate's name will be published, with all other candidate na=
mes, at the close of the nominations period.=0A> =0A> - Excerpts of the inf=
ormation provided to the IAB by the nominated candidate will be passed to t=
he IESG as part of the confirmation process. The IESG will be requested to =
maintain confidentiality of the candidate's information.=0A> =0A> - Except =
as noted above, all information provided to the IAB during this process wil=
l be kept confidential to the IAB. =0A> =0A> =0A> Current IETF-Selected Tru=
stees =0A> ------------------------------=0A> =0A> The current IETF-Selecte=
d ISOC Trustees and their term of appointment are: =0A> =0A> - Bert Wijnen =
2011 - 2014=0A> - Eric Burger 2012 - 2015=0A> - Bob Hinden 2013 - 2016 =0A>=
 =0A> =0A> On behalf of the IAB,=0A> Russ Housley=0A> IAB Chair
--1439723771-2089239970-1392992038=:55876
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">Dear Russ Housley;<br><br>&nbsp;&nbsp; Thank you very much fo=
r your message. Can I have a chance to nominate my self or this position is=
 closed for IAB member.&nbsp; Please reply confirm.<br><br><br><br>Thanks<b=
r><br>Hago Dafalla<br>Sudan<br><div><span><br></span></div><div style=3D"di=
splay: block;" class=3D"yahoo_quoted"> <br> <br> <div style=3D"font-family:=
 HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, Sans-Serif=
; font-size: 12pt;"> <div style=3D"font-family: HelveticaNeue, Helvetica Ne=
ue, Helvetica, Arial, Lucida Grande, Sans-Serif; font-size: 12pt;"> <div di=
r=3D"ltr"> <font face=3D"Arial" size=3D"2"> On Wednesday, 19 February 2014,=
 19:41, IAB Chair &lt;iab-chair@iab.org&gt; wrote:<br> </font> </div>  <div=
 class=3D"y_msg_container">This is a reminder that the IAB is seeking nomin=
ations for
 one seat on the ISOC Board of Trustees.&nbsp; The nominations period is un=
changed, and nominations close on February 27th.<br clear=3D"none"><br clea=
r=3D"none">On behalf of the IAB,<br clear=3D"none">Russ Housley<br clear=3D=
"none">IAB Chair<br clear=3D"none"><br clear=3D"none"><div class=3D"yqt8309=
912278" id=3D"yqtfd20130"><br clear=3D"none">On Jan 30, 2014, at 10:13 AM, =
IAB Chair wrote:<br clear=3D"none"><br clear=3D"none">&gt; <br clear=3D"non=
e">&gt; The Internet Society (ISOC) provides organizational and financial s=
upport for the IETF. As part of the arrangements between ISOC and the IETF,=
 the IETF is called upon to name 3 Trustees to its Board (BoT), with stagge=
red 3 year terms. This requires that the IETF select one Trustee each year.=
 <br clear=3D"none">&gt; <br clear=3D"none">&gt; This year, the IAB will se=
lect one person for a term ending in mid-2017. <br clear=3D"none">&gt; <br =
clear=3D"none">&gt; A description of the IAB's process for selecting the Tr=
ustee each year can be
 found in RFC 3677, with this year's timeline as follows: <br clear=3D"none=
">&gt; <br clear=3D"none">&gt; * January 30, 2014 : Open nomination period<=
br clear=3D"none">&gt; <br clear=3D"none">&gt; * February 27, 2014 : Close =
of the nomination period <br clear=3D"none">&gt; <br clear=3D"none">&gt; * =
No later than April 10, 2014 : IAB selection delivered to IESG for confirma=
tion<br clear=3D"none">&gt; <br clear=3D"none">&gt; * No later than May 23,=
 2014 : Delivery of final confirmed selection to the ISOC Elections Committ=
ee for announcement with the rest of the new ISOC BoT slate. <br clear=3D"n=
one">&gt; <br clear=3D"none">&gt; <br clear=3D"none">&gt; Nominations <br c=
lear=3D"none">&gt; ----------- <br clear=3D"none">&gt; <br clear=3D"none">&=
gt; Nominations (including self-nominations) should be sent to the IAB -- <=
a shape=3D"rect" ymailto=3D"mailto:iab@iab.org." href=3D"mailto:iab@iab.org=
.">iab@iab.org.</a>&nbsp; Please include e-mail contact details with the no=
mination. <br
 clear=3D"none">&gt; <br clear=3D"none">&gt; Nomination Details <br clear=
=3D"none">&gt; ----------------- <br clear=3D"none">&gt; <br clear=3D"none"=
>&gt; Nominees should be aware that ISOC Trustees are elected to three year=
 terms with approximately one third of the Board of Trustees elected each y=
ear. The responsibilities of a Trustee include fiscal management of the Int=
ernet Society, fundraising, and participation in Board meetings plus confer=
ence-call meetings, as detailed by the ISOC Bylaws:<br clear=3D"none">&gt; =
<a shape=3D"rect" href=3D"http://www.internetsociety.org/who-we-are/governa=
nce-and-policies/amended-and-restated-laws-internet-society" target=3D"_bla=
nk">http://www.internetsociety.org/who-we-are/governance-and-policies/amend=
ed-and-restated-laws-internet-society</a><br clear=3D"none">&gt; <br clear=
=3D"none">&gt; The desirable characteristics of a candidate that are specif=
ic to the IETF-selected ISOC BoT member are outlined in section 2 of RFC 36=
77. <br
 clear=3D"none">&gt; <br clear=3D"none">&gt; Nominees are asked to provide =
to the IAB: <br clear=3D"none">&gt; <br clear=3D"none">&gt; 1. Confirmation=
 of their willingness to be considered within this process. <br clear=3D"no=
ne">&gt; <br clear=3D"none">&gt; 2. Full name and contact information. <br =
clear=3D"none">&gt; <br clear=3D"none">&gt; 3. A statement confirming willi=
ngness and ability to devote an appropriate level of time to activities ass=
ociated with the position of Trustee. <br clear=3D"none">&gt; <br clear=3D"=
none">&gt; 4. A brief biography outlining experience and background. <br cl=
ear=3D"none">&gt; <br clear=3D"none">&gt; 5. A statement of interests, conc=
erns about the Internet Society, goals as a Trustee, and motivation to serv=
e as a Trustee. <br clear=3D"none">&gt; <br clear=3D"none">&gt; 6. Any furt=
her information that is relevant to the work of the IAB in considering your=
 nomination. <br clear=3D"none">&gt; <br clear=3D"none">&gt; Time Commitmen=
t <br clear=3D"none">&gt;
 --------------- <br clear=3D"none">&gt; <br clear=3D"none">&gt; Trustees a=
re expected to commit the time necessary to perform regular board and commi=
ttee business. Trustees are also expected to allocate some time to attend a=
nd prepare for meetings. <br clear=3D"none">&gt; <br clear=3D"none">&gt; <b=
r clear=3D"none">&gt; Care of Personal Information <br clear=3D"none">&gt; =
---------------------------- <br clear=3D"none">&gt; <br clear=3D"none">&gt=
; The following procedures will be used by the IAB in managing this process=
: <br clear=3D"none">&gt; <br clear=3D"none">&gt; - The candidate's name wi=
ll be published, with all other candidate names, at the close of the nomina=
tions period.<br clear=3D"none">&gt; <br clear=3D"none">&gt; - Excerpts of =
the information provided to the IAB by the nominated candidate will be pass=
ed to the IESG as part of the confirmation process. The IESG will be reques=
ted to maintain confidentiality of the candidate's information.<br clear=3D=
"none">&gt; <br
 clear=3D"none">&gt; - Except as noted above, all information provided to t=
he IAB during this process will be kept confidential to the IAB. <br clear=
=3D"none">&gt; <br clear=3D"none">&gt; <br clear=3D"none">&gt; Current IETF=
-Selected Trustees <br clear=3D"none">&gt; ------------------------------<b=
r clear=3D"none">&gt; <br clear=3D"none">&gt; The current IETF-Selected ISO=
C Trustees and their term of appointment are: <br clear=3D"none">&gt; <br c=
lear=3D"none">&gt; - Bert Wijnen 2011 - 2014<br clear=3D"none">&gt; - Eric =
Burger 2012 - 2015<br clear=3D"none">&gt; - Bob Hinden 2013 - 2016 <br clea=
r=3D"none">&gt; <br clear=3D"none">&gt; <br clear=3D"none">&gt; On behalf o=
f the IAB,<br clear=3D"none">&gt; Russ Housley<br clear=3D"none">&gt; IAB C=
hair<br clear=3D"none"></div><br><br></div>  </div> </div>  </div> </div></=
body></html>
--1439723771-2089239970-1392992038=:55876--


From nobody Mon Feb 24 09:21:19 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 207B71A0168 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 09:21:11 -0800 (PST)
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 SMCTSkdwDxBl for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 09:21:08 -0800 (PST)
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 386981A0169 for <ietf@ietf.org>; Mon, 24 Feb 2014 09:21:08 -0800 (PST)
Received: by mail-pa0-f41.google.com with SMTP id fa1so6870236pad.0 for <ietf@ietf.org>; Mon, 24 Feb 2014 09:21:07 -0800 (PST)
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=y9VcUObL6bMFEfoJatSfyFhsuU2DJsZ156h0Gqe8ESs=; b=HfVck1mnM1Et6I1omyjPP54PE6zENosqfZ0YLZ8itrkyNv6yQeqxxdQ58yK13aMbkk aRpKHTU3fjNQlpPlE/zmFsU9IvKvpG7LQ1VONV+7vHqKP6isX+k5yxA7oBj8JqUOXCx2 6LgNnI5p+p7Kbslcn26PhxPRSKD0XvE4CsIdESC100gJqLtGI+g0RV5gwEKRlmhrvrPV WdepXMg4FI4Chq2DmO1UTC9E5Dod3p8LLPU8EjjxCtBFzkLW7QEeWcA0o5E86kmlQUMW EjCdLoEZcMs95diEnsam0dRXFEavo6pVdiS5HjBT+qqFqygoNda0LwMDKKzUp6t27Jt8 UtMw==
X-Received: by 10.66.191.42 with SMTP id gv10mr26467373pac.125.1393262467751;  Mon, 24 Feb 2014 09:21:07 -0800 (PST)
Received: from spandex.local (63-140-68-38-rb2.sol.dsl.dynamic.acsalaska.net. [63.140.68.38]) by mx.google.com with ESMTPSA id g6sm123859753pat.2.2014.02.24.09.21.06 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Feb 2014 09:21:07 -0800 (PST)
Message-ID: <530B7F81.20303@gmail.com>
Date: Mon, 24 Feb 2014 08:21:05 -0900
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: Policy of WG chairs in organising time for presentations and face2face discussions
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.u k> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net>
In-Reply-To: <530B75B3.7000300@dcrocker.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/K8lQXCjZyuJCTLXpZOD5efUUnzA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 17:21:11 -0000

On 2/24/14 7:39 AM, Dave Crocker wrote:
> By publicly asking about the background of the person making the
> suggestion, the public exchange moves from the merits of the suggestion
> to the merits of the person making the suggestion.

I think it matters a lot whether or not someone has first-hand
knowledge of whether or not something they're proposing actually
works in practice.  Or at least it does in general - in this
case we've got a pretty good handle on AB's IETF experience and
the question was unnecessary.

At any rate IETF meetings are working meetings.  They are not
conferences.  AB is hardly alone in his confusion about this.

Melinda


From nobody Mon Feb 24 10:03:02 2014
Return-Path: <loa@pi.nu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 78A781A0177 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 10:03:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MR7QutZCobdJ for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 10:02:59 -0800 (PST)
Received: from pipi.pi.nu (pipi.pi.nu [83.168.239.141]) by ietfa.amsl.com (Postfix) with ESMTP id CB5301A0175 for <ietf@ietf.org>; Mon, 24 Feb 2014 10:02:55 -0800 (PST)
Received: from [192.168.1.110] (90-227-238-197-no15.business.telia.com [90.227.238.197]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: loa@pi.nu) by pipi.pi.nu (Postfix) with ESMTPSA id 1AC0F180156A; Mon, 24 Feb 2014 19:02:55 +0100 (CET)
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk> <530B5398.7070705@dcrocker.net> <F4A59F40-EDBE-4E73-BFE1-4CB5E68B64BC@pi.nu> <530B78D6.20401@dcrocker.net>
In-Reply-To: <530B78D6.20401@dcrocker.net>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <9D7F4D1C-DCD1-496C-A05A-84A5854B2B7A@pi.nu>
X-Mailer: iPad Mail (11B651)
From: Loa Andersson <loa@pi.nu>
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
Date: Mon, 24 Feb 2014 19:02:54 +0100
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6PQ13X5pM7Mot2OtaV0BeD6w-mA
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, 24 Feb 2014 18:03:00 -0000

Sent from my iPad

> On Feb 24, 2014, at 17:52, Dave Crocker <dhc@dcrocker.net> wrote:
>=20
>> On 2/24/2014 8:49 AM, Loa Andersson wrote:
>> While I agree mostly on the line of your response I think that it was not=
 a "question" but formulated as an "advise" and coming from someone that we a=
ll know have not planned any wg agendas. Of course this does not disqualify h=
im, but if he is at odds with experienced people we should take such advice w=
ith more than a spoonful of salt (is that an English proverb).
>=20
>=20
> Then the note should have been sent privately.
>=20
> d/

Or even better - not at all !
>=20
> --=20
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net


From nobody Mon Feb 24 10:42:54 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 A3FEF1A0189 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 10:42:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.363
X-Spam-Level: 
X-Spam-Status: No, score=0.363 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 z5Fc-ZGAv5IB for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 10:42:50 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BF3C1A0140 for <ietf@ietf.org>; Mon, 24 Feb 2014 10:42:49 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.42]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1OIgTNq029485 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Feb 2014 10:42:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393267362; bh=BmnlUV3rTeRV00zbthmtZDAWJkAiDKIlIP0gSzVUwfQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=slQ+b8NznnTqjZrim1eyfx2ml92Ae9k3AwBlK9EUGz2XdnLA2Af8hppr3vraVUV7s 4wc5VS1bnqDSYBCCkPapAs6LM3siHvvCsYPHCW0odzXfD4S1fj0g+m6ke8ar6nmKXY iKjpdNunCy8wg0Gei2qG4e3ih1fkbmpfXv3rkMoo=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393267362; i=@elandsys.com; bh=BmnlUV3rTeRV00zbthmtZDAWJkAiDKIlIP0gSzVUwfQ=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zBNeCtAlYAJYyVrZt07wBXs5r4YByBZRopQRDJz4MCunWFLfONLDtL5cbSZ4AdV7N SInVIep6OICAE8zG7cLr+7tnpnM4td9FNOShooH9GMJC/VVPevDP0bKRqw4s2/LkMI WOzwRpHeT6jp+ozPJOgw4kZBrgsAhnfpSwaz/1MM=
Message-Id: <6.2.5.6.2.20140224084425.0d2a9d18@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 24 Feb 2014 09:34:26 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, John Levine <johnl@taugh.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: anti-harassment procedures
In-Reply-To: <53082A34.8040202@gmail.com>
References: <20140222040322.30798.qmail@joyce.lan> <53082A34.8040202@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oPmWB-horKd3C5JjYNeT8UDZVq0
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, 24 Feb 2014 18:42:53 -0000

Hi Brian,
At 20:40 21-02-2014, Brian E Carpenter wrote:
>One difficulty is that what is "unwanted" is very sensitive
>to cultural and linguistic subtleties. Also, if (for example) I
>were to repeatedly point out substantive errors in somebody's
>IETF work, or even syntax errors in their English, where is the
>line between legitimate discussion and review and objectionable
>harassment?

I am responding to the above as it is one of the difficulties 
encountered in an interaction with another person.

If you repeatedly point out substantive errors in somebody's work, 
that person might perceive that as victimization.  I'd say try and 
keep it impersonal as far as possible.  It is better to avoid point 
out too many syntax errors if you are not sure whether the person 
uses English as a first language.

I'll separate legitimate discussion and review.  In the review you 
can easily point out the substantive errors or syntax errors.  I am 
not sure how to explain how the discussion can be a problem.  I would 
leave that to experience.

Regards,
S. Moonesamy 


From nobody Mon Feb 24 10:48:36 2014
Return-Path: <jmpolk@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 638951A029D for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 10:48:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.348
X-Spam-Level: 
X-Spam-Status: No, score=-12.348 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_HI=-5, RP_MATCHES_RCVD=-0.547, 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 Iod5bWKdng8V for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 10:48:32 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com [173.36.130.12]) by ietfa.amsl.com (Postfix) with ESMTP id D21D41A0290 for <ietf@ietf.org>; Mon, 24 Feb 2014 10:48:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2136; q=dns/txt; s=iport; t=1393267708; x=1394477308; h=message-id:date:to:from:subject:in-reply-to:references: mime-version; bh=yJJAyVrqP9uFeBoyej6VfmxuNjRYVC9/Mxl3BuSIucU=; b=gtJUadEW3FPvCf024FSob2nn3X4ERMezN+B6QuAPSZJFMqZIo2DhFcKv 6/z1pRLsAgqxEk4Fa1wzgxXccDy1DHZdvk3LgUNs0fo+rPnVotUqGvG0i vLRBG9IHHxVt8kdD2odsGABGEWqFgEy1rZ5Mbn+t64+p/RqumfV+jASxw s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmIFAKuSC1OrRDoH/2dsb2JhbABZDoJ4O1HBCoEdFnSCJQEBAQQ4AjQbBwQRBAEBAQkVEA8KCC4IBgESh3EDEAm/Eg2GbheMT4E+A1uEOASJSIx/gx+LLgOFRIFvf14dgS0
X-IronPort-AV: E=Sophos;i="4.97,536,1389744000"; d="scan'208";a="103681569"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by mtv-iport-1.cisco.com with ESMTP; 24 Feb 2014 18:48:28 +0000
Received: from jmpolk-WS.cisco.com (sjc-vpn7-1609.cisco.com [10.21.150.73]) (authenticated bits=0) by mtv-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1OImRa3015130 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Feb 2014 18:48:27 GMT
Message-Id: <201402241848.s1OImRa3015130@mtv-core-2.cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 24 Feb 2014 12:48:25 -0600
To: <l.wood@surrey.ac.uk>, <abdussalambaryun@gmail.com>, <ietf@ietf.org>
From: James Polk <jmpolk@cisco.com>
Subject: RE: Policy of WG chairs in organising time for presentations and face2face discussions
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surre y.ac.uk>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Authenticated-User: jmpolk
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/t9KHCEoH0VicR7HMh8ZlBbqcckM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 18:48:34 -0000

At 12:49 AM 2/24/2014, l.wood@surrey.ac.uk wrote:
>Abdussalam
>
>you write:
> > I suggest in London that you assign only maximum 10 minutes 
> present per WG draft and maximum 5 minute for individual draft (as 
> limit policy).
> > We need to use more input and have more face2face (F2F) 
> discussion in our meeting.
>
>How many IETF meetings have you attended, and what experience do you 
>base this recommendation on?

further, what if there are only two IDs active in a WG and the chairs 
were given an hour or two hour slot because there are LOTS of open 
questions that do not seem to be getting resolved on the mailing list 
even though there have been a fair amount of discussion on both 
drafts on the list? Would you still recommend only 30 minutes of 
total meeting time? Seems like it, or do you give the chairs the 
discretion to allocate time as they see fit?

James
(been a chair for 9 years)


>Lloyd Wood
>http://about.me/lloydwood
>________________________________________
>From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun 
>[abdussalambaryun@gmail.com]
>Sent: 24 February 2014 03:43
>To: ietf
>Subject: Policy of WG chairs in organising time for presentations 
>and face2face discussions
>
>Dear IETF WGs' Chairs,
>
>I suggest in London that you assign only maximum 10 minutes present 
>per WG draft and maximum 5 minute for individual draft (as limit 
>policy). We need to use more input and have more face2face (F2F) 
>discussion in our meeting. I remember we discussed this before but 
>it will be nice if we know what chairs are thinking before few days 
>of the meeting.
>
>Meeting time is money and that we need to improve the use of IETF 
>times within F2F WG discussions and decisions.  If an author cannot 
>describe issues of draft in 10 minutes then it will be difficult for 
>the WG listeners to discuss and make decisions within another 10 
>minutes per item. Please comment.
>
>Best wishes,
>
>Abdussalam
>
>WG Meetings are needed for group interactions and group decisions 
>not individual presentations or individual decisions.


From nobody Mon Feb 24 11:37:19 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 686C41A028B for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 11:37:18 -0800 (PST)
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 i4mdCeiWIo0X for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 11:37:15 -0800 (PST)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 5C3781A0250 for <ietf@ietf.org>; Mon, 24 Feb 2014 11:37:15 -0800 (PST)
Received: by mail-la0-f41.google.com with SMTP id gl10so3434441lab.28 for <ietf@ietf.org>; Mon, 24 Feb 2014 11:37:14 -0800 (PST)
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=qVZXYXXhy/uq9dIeKuD6GVSbngoJby96hDzg7IJ7RPQ=; b=XcwRMa7jlQNaOI8YC7Bx5N8q664kVD/LowXINi3o1sRYrQmMcOALUea9cWb87mwUTL BJB5RixDlAGE29d3xxJ+uLbm+tpM10zH2q9E77nB7NjLH46NxNMLHVBLVUqLMWzUYFgU mgR9ufY0/+tRNa8JWSUi59EbcEoasCrpOR8+v6oLBXLPURG9o0zZiXphznK133ogF3hM Hkl40pIyfZkXcippRY2y5lvGwmcRiPiiSkekD/7RH91mbClf50cKeG3It2jpHBmTSgh7 1QnKymWCw1oNwJBC/FgcxTYOU8d8Uih3UI1ZR+EZd9IUr3AR54D6SfFYh+uDyKpzWmBe 752A==
MIME-Version: 1.0
X-Received: by 10.152.36.70 with SMTP id o6mr13033801laj.7.1393270634078; Mon, 24 Feb 2014 11:37:14 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 24 Feb 2014 11:37:13 -0800 (PST)
In-Reply-To: <530B75B3.7000300@dcrocker.net>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net>
Date: Mon, 24 Feb 2014 14:37:13 -0500
Message-ID: <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com>
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Dave Crocker <dcrocker@bbiw.net>
Content-Type: multipart/alternative; boundary=089e0160b6183866cc04f32c1903
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/o3Vx9Mu_3xpVxbTPaHYAPKOWzVA
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: Mon, 24 Feb 2014 19:37:18 -0000

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

Could we have an RFC to explain what is and what is not a valid ad-hominem
argument?

Almost everyone who raises it gets it wrong.


Ad Hominem is a perfectly valid argument against claims of fact when made
against the authority making the claim. "PT Barnum is a notorious liar' is
a perfectly valid argument against a claim PT Barnum is making about having
found a mermaid.

Ad hominem is not a valid argument against a conclusion drawn from agreed
facts. So if I say 'that must be a bad idea because Dave Crocker supports
it' then I am making an invalid adhominem argument.

But even here, ad hominem can be valid if in the case that it is excluding
the last authority. For example, if we are discussing the situation in
Ukraine and John McBain suggests an immediate US invasion then it is a
perfectly valid argument to state that 'McBain is the only person making
that proposal, McBain always suggests starting a war, the proposal is
ridiculous and is not worth the time to consider'.


The question at issue here is not merely the conclusion but the implied
statement of the facts.




On Mon, Feb 24, 2014 at 11:39 AM, Dave Crocker <dhc@dcrocker.net> wrote:

> On 2/24/2014 6:38 AM, John C Klensin wrote:
>
>  --On Monday, February 24, 2014 06:13 -0800 Dave Crocker
>> <dhc@dcrocker.net> wrote:
>>
>>> I'll suggest that that question is primarily ad hominem and
>>> even if it weren't, it's not a particularly helpful line of
>>> response.  It doesn't matter what the background is of the
>>> person asking the question.
>>>
>>
>> Dave, FWIW, I disagree, both about the "primarily ad hominem"
>> suggestion and about the comment about background.
>>
>
> If you or I had made the suggestion, would that affect its merit?  We have
> extensive IETF meeting experience, but that's irrelevant.
>
> If it's a good suggestion, it doesn't matter who made it.
>
> If it's a bad suggestion, it doesn't matter who made it.
>
> By publicly asking about the background of the person making the
> suggestion, the public exchange moves from the merits of the suggestion to
> the merits of the person making the suggestion.
>
> Moving focus off of the substance and to the speaker is the essence of ad
> hominem.  It either explicitly or implicitly is asserting that the nature
> of the speaker affects the merit of what is spoken, with the usual
> implication that the speaker and their suggestion should be discounted.
>
>
>
>  If Lloyd had said "you are a known <NegativeCategory>, therefore
>> your suggestion should be ignored" that would be primarily an ad
>> hominem attack.
>>
>
> So it isn't ad hominem unless it is a direct, frontal and coarse assertion
> of the false factor?  If it is only implied, it doesn't count?
>
>
>
>         the question about
>> background seems to me to be relevant.  Let me try an analogy
>> that, given some recent postings, shouldn't be too far afield.
>> Suppose someone had posted a note to the IETF list or some
>> meeting list saying "during the upcoming meeting, it is really
>> important that everyone have a proper traditional English
>> breakfast".  I'd consider "what background, especially in
>> nutrition and related fields,
>>
>
> You are confusing substance with person.
>
> The question that was asked was not "what is the basis for the
> recommendation" but "what is your experience with our meetings".  The
> former is substance and reasonable.  The latter is personal and not.
>
> And this was done in public as an immediate response and without any other
> context.
>
> We make this confusion quite a lot in the IETF.
>
>
> d/
>
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>
>


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

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

<div dir=3D"ltr">Could we have an RFC to explain what is and what is not a =
valid ad-hominem argument?<div><br></div><div>Almost everyone who raises it=
 gets it wrong.</div><div><br></div><div><br></div><div>Ad Hominem is a per=
fectly valid argument against claims of fact when made against the authorit=
y making the claim. &quot;PT Barnum is a notorious liar&#39; is a perfectly=
 valid argument against a claim PT Barnum is making about having found a me=
rmaid.</div>
<div><br></div><div>Ad hominem is not a valid argument against a conclusion=
 drawn from agreed facts. So if I say &#39;that must be a bad idea because =
Dave Crocker supports it&#39; then I am making an invalid adhominem argumen=
t.</div>
<div><br></div><div>But even here, ad hominem can be valid if in the case t=
hat it is excluding the last authority. For example, if we are discussing t=
he situation in Ukraine and John McBain suggests an immediate US invasion t=
hen it is a perfectly valid argument to state that &#39;McBain is the only =
person making that proposal, McBain always suggests starting a war, the pro=
posal is ridiculous and is not worth the time to consider&#39;.</div>
<div><br></div><div><br></div><div>The question at issue here is not merely=
 the conclusion but the implied statement of the facts.</div><div><br></div=
><div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmai=
l_quote">
On Mon, Feb 24, 2014 at 11:39 AM, Dave Crocker <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net</a>&gt;</s=
pan> 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"">On 2/24/2014 6:38 AM, John C Klensin wrote:<br>
<br>
</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div class=3D"">
--On Monday, February 24, 2014 06:13 -0800 Dave Crocker<br>
&lt;<a href=3D"mailto:dhc@dcrocker.net" target=3D"_blank">dhc@dcrocker.net<=
/a>&gt; wrote:<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&#39;ll suggest that that question is primarily ad hominem and<br>
even if it weren&#39;t, it&#39;s not a particularly helpful line of<br>
response. =A0It doesn&#39;t matter what the background is of the<br>
person asking the question.<br>
</blockquote>
<br>
Dave, FWIW, I disagree, both about the &quot;primarily ad hominem&quot;<br>
suggestion and about the comment about background.<br>
</div></blockquote>
<br>
If you or I had made the suggestion, would that affect its merit? =A0We hav=
e extensive IETF meeting experience, but that&#39;s irrelevant.<br>
<br>
If it&#39;s a good suggestion, it doesn&#39;t matter who made it.<br>
<br>
If it&#39;s a bad suggestion, it doesn&#39;t matter who made it.<br>
<br>
By publicly asking about the background of the person making the suggestion=
, the public exchange moves from the merits of the suggestion to the merits=
 of the person making the suggestion.<br>
<br>
Moving focus off of the substance and to the speaker is the essence of ad h=
ominem. =A0It either explicitly or implicitly is asserting that the nature =
of the speaker affects the merit of what is spoken, with the usual implicat=
ion that the speaker and their suggestion should be discounted.<div class=
=3D"">
<br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
If Lloyd had said &quot;you are a known &lt;NegativeCategory&gt;, therefore=
<br>
your suggestion should be ignored&quot; that would be primarily an ad<br>
hominem attack.<br>
</blockquote>
<br></div>
So it isn&#39;t ad hominem unless it is a direct, frontal and coarse assert=
ion of the false factor? =A0If it is only implied, it doesn&#39;t count?<di=
v class=3D""><br>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=A0 =A0 =A0 =A0the question about<br>
background seems to me to be relevant. =A0Let me try an analogy<br>
that, given some recent postings, shouldn&#39;t be too far afield.<br>
Suppose someone had posted a note to the IETF list or some<br>
meeting list saying &quot;during the upcoming meeting, it is really<br>
important that everyone have a proper traditional English<br>
breakfast&quot;. =A0I&#39;d consider &quot;what background, especially in<b=
r>
nutrition and related fields,<br>
</blockquote>
<br></div>
You are confusing substance with person.<br>
<br>
The question that was asked was not &quot;what is the basis for the recomme=
ndation&quot; but &quot;what is your experience with our meetings&quot;. =
=A0The former is substance and reasonable. =A0The latter is personal and no=
t.<br>

<br>
And this was done in public as an immediate response and without any other =
context.<br>
<br>
We make this confusion quite a lot in the IETF.<div class=3D"HOEnZb"><div c=
lass=3D"h5"><br>
<br>
d/<br>
<br>
-- <br>
Dave Crocker<br>
Brandenburg InternetWorking<br>
<a href=3D"http://bbiw.net" target=3D"_blank">bbiw.net</a><br>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br=
>
</div>

--089e0160b6183866cc04f32c1903--


From nobody Mon Feb 24 11:43:09 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 00A891A02AD for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 11:43:08 -0800 (PST)
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 JXmtT4iuwi6m for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 11:43:05 -0800 (PST)
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 63FA31A00D7 for <ietf@ietf.org>; Mon, 24 Feb 2014 11:43:05 -0800 (PST)
Received: by mail-pd0-f169.google.com with SMTP id v10so6752435pde.0 for <ietf@ietf.org>; Mon, 24 Feb 2014 11:43:04 -0800 (PST)
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=r0Y0zbDz+KRXU00EKA2lV77q7yvqSkDjmA/lzv8BCpA=; b=DbxcT6RhyeW3L5vb1tzDfNBVTH3hG4LAnBnYiKMQ3e+rGu6Q85oB7u2fgjVu3L2F1/ YuUaB9nKoaGZRG+KXiWuETpFPF+kf8TW7gPcXTT/eHr/CYbDXiz3T3sx4Z8R3DbjtnBT QosHrM6NhzQh0+DwQqOdKL+SY75ooGuMtN8P8Py7Ij52lrTQQfyO+8FjcgKUgjC9Vr6/ i40yOru1+H+Kyx29pui6L/AFm087ZWmvNlfD8r77GMEHPI0PUtH0zQvJC2jvBVsUgqbv CIwHIcaU3i3ZxqQ1ZYzcIhfj8Ocjp2P6ZlESDFqXxVpLvQm+k4Gnto9MHRHKTiZnBbdy IEzQ==
X-Received: by 10.66.149.7 with SMTP id tw7mr27231574pab.72.1393270984879; Mon, 24 Feb 2014 11:43:04 -0800 (PST)
Received: from [192.168.178.23] (129.201.69.111.dynamic.snap.net.nz. [111.69.201.129]) by mx.google.com with ESMTPSA id e3sm2692866pbc.17.2014.02.24.11.43.02 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 24 Feb 2014 11:43:04 -0800 (PST)
Message-ID: <530BA0C7.8070806@gmail.com>
Date: Tue, 25 Feb 2014 08:43:03 +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: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: anti-harassment procedures
References: <20140222040322.30798.qmail@joyce.lan> <53082A34.8040202@gmail.com> <6.2.5.6.2.20140224084425.0d2a9d18@resistor.net>
In-Reply-To: <6.2.5.6.2.20140224084425.0d2a9d18@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_YqZFVpDtIhKFw7wwGNTEFrT0R0
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, 24 Feb 2014 19:43:08 -0000

On 25/02/2014 06:34, S Moonesamy wrote:
> Hi Brian,
> At 20:40 21-02-2014, Brian E Carpenter wrote:
>> One difficulty is that what is "unwanted" is very sensitive
>> to cultural and linguistic subtleties. Also, if (for example) I
>> were to repeatedly point out substantive errors in somebody's
>> IETF work, or even syntax errors in their English, where is the
>> line between legitimate discussion and review and objectionable
>> harassment?
> 
> I am responding to the above as it is one of the difficulties
> encountered in an interaction with another person.
> 
> If you repeatedly point out substantive errors in somebody's work, that
> person might perceive that as victimization.  I'd say try and keep it
> impersonal as far as possible.  It is better to avoid point out too many
> syntax errors if you are not sure whether the person uses English as a
> first language.

Of course. My point was that it's hard to define a precise boundary between
legitimate critical discussion and mild harassment, and we need to be sensitive
to that in the text. It's more important to have a process that deals
effectively with *serious* and highly unpleasant behaviours that we clearly
should not tolerate.

     Brian

> 
> I'll separate legitimate discussion and review.  In the review you can
> easily point out the substantive errors or syntax errors.  I am not sure
> how to explain how the discussion can be a problem.  I would leave that
> to experience.
> 
> Regards,
> S. Moonesamy
> 


From nobody Mon Feb 24 12:15:03 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 6E07A1A0151 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 12:15:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.559
X-Spam-Level: **
X-Spam-Status: No, score=2.559 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 rhJno5B89k7w for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 12:15:00 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 5A5001A0131 for <ietf@ietf.org>; Mon, 24 Feb 2014 12:15:00 -0800 (PST)
Received: from mx1.yitter.info (nat-01-mht.dyndns.com [216.146.45.240]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.yitter.info (Postfix) with ESMTPSA id 7F9428A031 for <ietf@ietf.org>; Mon, 24 Feb 2014 20:14:59 +0000 (UTC)
Date: Mon, 24 Feb 2014 15:14:58 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Message-ID: <20140224201457.GO35396@mx1.yitter.info>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ee6UTFRe2eHmrHDsR_Ws0fUJjTc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 20:15:01 -0000

On Mon, Feb 24, 2014 at 02:37:13PM -0500, Phillip Hallam-Baker wrote:
> Could we have an RFC to explain what is and what is not a valid ad-hominem
> argument?

There are no valid _ad hominem_ arguments.  _Ad hominem_ is a short
name of a fallacious form or reasoning where one attacks the person
making the argument _instead of_ attacking the argument as such.
(More fully, of course, it's known as _argumentum ad hominem_.)

> Ad Hominem is a perfectly valid argument against claims of fact when made
> against the authority making the claim. "PT Barnum is a notorious liar' is
> a perfectly valid argument against a claim PT Barnum is making about having
> found a mermaid.

I think this is only sort of true.  When Barnum is making his
argument, he's offering testimony ("I found a mermaid").  In this
case, pointing out that Barnum is a notorious liar is an attack on the
testimony.  It's therefore not an _ad hominem_ because you're not
attacking the person speaking, but arguing about the premises of
Barnum's original argument from testimony.  Even there, it'd be a
pretty weak argument, until you added, "Also, there are no previous
known cases of mermaids, and PT Barnum has refused to allow anyone
else to examine the alleged mermaid."  Otherwise, you could as easily
use the premise "Barnum is a notorious liar" when Barnum says, "A
contradiction cannot be true."  

The primary consideration is always relevance to the argument at hand.
That's why _ad hominem_ is usually classified as a fallacy of
relevance.  It's also why I prefer to avoid the term _ad hominem_ in
favour of pointing out why something is irrelevant to the argument at
hand.

> The question at issue here is not merely the conclusion but the implied
> statement of the facts.

I disagree.  The question is whether the argument against a given
position is relevant to the truth or falisty of that position (or its
supporting premises).  In the case of an _ad hominem_, the irrelevance
lies with attending to the speaker instead of that which is spoken.

Best regards,

Andrew

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Mon Feb 24 12:41: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 6184C1A0177 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 12:41:05 -0800 (PST)
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 gwnNah0p8bY8 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 12:41:03 -0800 (PST)
Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 91F421A02F4 for <ietf@ietf.org>; Mon, 24 Feb 2014 12:41:03 -0800 (PST)
Received: by mail-la0-f50.google.com with SMTP id y1so2507357lam.37 for <ietf@ietf.org>; Mon, 24 Feb 2014 12:41:02 -0800 (PST)
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=DkZgZnnS8xRsDgNyjvbvf5G4+Y8xiaUrLP9/MgW6hRQ=; b=Sy26uTgdHF+uXAuWeCxX+ArE39DIExeN/E+n9kCA2TXpOLgL/+441RDgYkKNKYPCjv 7N1wmmA47UNaBKSG7evqGr/W5vV7/ndpF3r/SGpNP0gv/oXv+9sbotMDSRrXAEbCnBqe 3F0xNBAEXBZfxZlelnnsnqBT4bdc5ZfJx9smToD2G2Gmztg6BZJTAXpBgcUMB6M5gIyd dPqsAhxQxxmf3rTdWKBVmO5QCDCkS1sgSMOPKGHWU+MUKG0LSxbnjt/TI9mbksCPeM6x e+kTFByGIXuUJ7whmNYgjL+J991SrQ8uhap86gmo14R+y6buXjlSc8V91QMYozrAQxuE W46g==
MIME-Version: 1.0
X-Received: by 10.112.169.42 with SMTP id ab10mr90727lbc.87.1393274462282; Mon, 24 Feb 2014 12:41:02 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Mon, 24 Feb 2014 12:41:02 -0800 (PST)
In-Reply-To: <20140224201457.GO35396@mx1.yitter.info>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info>
Date: Mon, 24 Feb 2014 15:41:02 -0500
Message-ID: <CAMm+LwiqWFpYsW6nTBdat382u_UonP5BuH5ZubqBO_4KmFy2PQ@mail.gmail.com>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Content-Type: multipart/alternative; boundary=001a11c38a9c6628d704f32cfd61
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QUfBM88F74zzTBtEFtKl2Rm-QQ4
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, 24 Feb 2014 20:41:05 -0000

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

On Mon, Feb 24, 2014 at 3:14 PM, Andrew Sullivan <ajs@anvilwalrusden.com>wrote:

> On Mon, Feb 24, 2014 at 02:37:13PM -0500, Phillip Hallam-Baker wrote:
> > Could we have an RFC to explain what is and what is not a valid
> ad-hominem
> > argument?
>
> There are no valid _ad hominem_ arguments.  _Ad hominem_ is a short
> name of a fallacious form or reasoning where one attacks the person
> making the argument _instead of_ attacking the argument as such.
> (More fully, of course, it's known as _argumentum ad hominem_.)
>

My point is that since it seems that almost nobody who asserts ad hominem
gets it right people should instead say 'thats rude' or 'thats
exclusionary'. It is of course perfectly valid from a logical point of view
to ask what the experience of someone is before they make organizational
proposals but it is still bloody rude.

As my old headmaster (an alum of Bletchley Park) used to say Latin
argumentum semper in fraudes.


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

--001a11c38a9c6628d704f32cfd61
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, Feb 24, 2014 at 3:14 PM, Andrew Sullivan <span dir=3D"ltr">=
&lt;<a href=3D"mailto:ajs@anvilwalrusden.com" target=3D"_blank">ajs@anvilwa=
lrusden.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">On Mon, Feb 24, 2014 at 02:37:13PM -0500, Phillip Hallam-B=
aker wrote:<br>

&gt; Could we have an RFC to explain what is and what is not a valid ad-hom=
inem<br>
&gt; argument?<br>
<br>
There are no valid _ad hominem_ arguments. =A0_Ad hominem_ is a short<br>
name of a fallacious form or reasoning where one attacks the person<br>
making the argument _instead of_ attacking the argument as such.<br>
(More fully, of course, it&#39;s known as _argumentum ad hominem_.)<br></bl=
ockquote><div><br></div><div>My point is that since it seems that almost no=
body who asserts ad hominem gets it right people should instead say &#39;th=
ats rude&#39; or &#39;thats exclusionary&#39;. It is of course perfectly va=
lid from a logical point of view to ask what the experience of someone is b=
efore they make organizational proposals but it is still bloody rude.</div>
<div><br></div><div>As my old headmaster (an alum of Bletchley Park) used t=
o say=A0Latin argumentum semper in fraudes.</div><div><br></div></div><div>=
<br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://hallam=
baker.com/</a><br>

</div></div>

--001a11c38a9c6628d704f32cfd61--


From nobody Mon Feb 24 12:42:57 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 C17301A0320 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 12:42:49 -0800 (PST)
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 Ey26R-dFAJGQ for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 12:42:46 -0800 (PST)
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 3B4151A031A for <ietf@ietf.org>; Mon, 24 Feb 2014 12:42:26 -0800 (PST)
Received: by mail-yh0-f46.google.com with SMTP id v1so5923967yhn.5 for <ietf@ietf.org>; Mon, 24 Feb 2014 12:42:25 -0800 (PST)
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=UzlOatGi+YBwQLKY49P/LGlv8xMClSJ9p4U03s2WsXg=; b=tcvTpyxOzj+9n2O2D0zsa9YiVnenQSjJWrkcEmJKoDkLolEfdK65Nin4QERHbH1M2W a/2qsT6klfjFX6fyIjAniCHx7KvwMXRq5BnfWE+ZUH5I6lUUz0367uOxM9Q8V54YL498 fjq4DJ5OUHDYvKwycNPR6y2rofSU5BsPuo5XV3cEub1hC4gzcrJJALXiKTGO1J+SALDg ywiSE5uGfShGszrzK+x0WOjMTH0EazyHap2hSSIAnN6UtNR4xeLQ2pYybESIs+ykDFWe HG4QMP68YxlZwIW2lWG7we0hQpnxCU+To5lqZDMGHV4zvlsGup0MMKm4c4t5enUMvhA7 vS8w==
MIME-Version: 1.0
X-Received: by 10.236.30.2 with SMTP id j2mr981226yha.73.1393274545508; Mon, 24 Feb 2014 12:42:25 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Mon, 24 Feb 2014 12:42:25 -0800 (PST)
In-Reply-To: <07e201cf316e$235bb510$6a131f30$@olddog.co.uk>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334729@EXMB01CMS.surrey.ac.uk> <530B5398.7070705@dcrocker.net> <07e201cf316e$235bb510$6a131f30$@olddog.co.uk>
Date: Mon, 24 Feb 2014 21:42:25 +0100
Message-ID: <CADnDZ8_Y1T86hBmq34FR-OTiVf7HucUTR8GzzwWQQ+ZvdPWqJQ@mail.gmail.com>
Subject: Re: Policy of WG chairs in organising time for presentations and face2face discussions
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>
Content-Type: multipart/alternative; boundary=089e011829cc5c15f904f32d0200
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7i1zIZXPKdi6eVnV-HfqYU20LK4
Cc: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, "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, 24 Feb 2014 20:42:50 -0000

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

Hi Adrian,

On Monday, February 24, 2014, Adrian Farrel wrote:

> Abdussalam could usefully clarify whether he means "limit the presentation
> time
> of an I-D" or "limit the time spent on an I-D".


Yes, I am worried about discussing first presented I-Ds among participants
in the meeting and it takes time of other later presented I-Ds.

 It happens that about 8 I-Ds are discussed within about 2 hours. So I
mostly mean time spent on an I-D while the control of the slot is handed to
who has booked the time and then thinking to limit time of presentation
only if the WG want more explanation to be continued.

Thanks for your comments,

AB

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

Hi Adrian,<br><br>On Monday, February 24, 2014, Adrian Farrel  wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex">Abdussalam could usefully clarify whether he m=
eans &quot;limit the presentation time<br>

of an I-D&quot; or &quot;limit the time spent on an I-D&quot;.</blockquote>=
<div><br></div><div>Yes, I am worried about discussing first presented=A0I-=
Ds=A0among participants in the meeting and it takes time of other later pre=
sented=A0I-Ds.</div>
<div><br></div><div>=A0It happens that about 8 I-Ds are discussed within ab=
out=A02=A0hours. So I mostly mean time spent on an I-D while the control of=
 the slot=A0is handed to who has booked the time and then thinking to limit=
 time of presentation only if=A0the WG want more explanation to be continue=
d.=A0</div>
<div><br></div><div>Thanks for your comments,</div><div><br></div><div>AB</=
div>

--089e011829cc5c15f904f32d0200--


From nobody Mon Feb 24 13:30:34 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 766441A01EE for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 13:30:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.047
X-Spam-Level: 
X-Spam-Status: No, score=-2.047 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sXEiKNEoYmxU for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 13:30:32 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id 08C771A0193 for <ietf@ietf.org>; Mon, 24 Feb 2014 13:30:31 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id C5E6718C126; Mon, 24 Feb 2014 16:30:30 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Message-Id: <20140224213030.C5E6718C126@mercury.lcs.mit.edu>
Date: Mon, 24 Feb 2014 16:30:30 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vxkLq2S2lQwpGwtYEXBfewYjVwU
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: Mon, 24 Feb 2014 21:30:33 -0000

    > From: Andrew Sullivan <ajs@anvilwalrusden.com>

    > On Mon, Feb 24, 2014 at 02:37:13PM -0500, Phillip Hallam-Baker wrote:

    >> Could we have an RFC to explain what is and what is not a valid
    >> ad-hominem argument?

    > There are no valid _ad hominem_ arguments. 

I suspect that he meant was 'can we have a method for properly classifying
things into "ad hominem attacks" and "not ad hominem attacks"'.

    > From: Phillip Hallam-Baker <hallam@gmail.com>

    > It is of course perfectly valid from a logical point of view to ask
    > what the experience of someone is before they make organizational
    > proposals but it is still bloody rude.

You mean, it's rude to ask what someone's experience is?

If so, that's odd: I myself found it 'bloody rude' (well, actually, I'd use a
slightly different term, but hey...) for someone to make suggestions on how
to improve our meeting process when they have really no experience of it.

	Noel


From nobody Mon Feb 24 13:39:53 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 00CC91A020D for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 13:39:53 -0800 (PST)
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 qEcRSX3wxxSe for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 13:39:51 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id D6D9F1A0193 for <ietf@ietf.org>; Mon, 24 Feb 2014 13:39:51 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1OLdm0s025990 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 24 Feb 2014 13:39:51 -0800
Message-ID: <530BBBEC.2010801@dcrocker.net>
Date: Mon, 24 Feb 2014 13:38:52 -0800
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.3.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu>
In-Reply-To: <20140224213030.C5E6718C126@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]); Mon, 24 Feb 2014 13:39:51 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JjxFUM1JZNCmDV0Ald5Wv_IrdfI
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, 24 Feb 2014 21:39:53 -0000

On 2/24/2014 1:30 PM, Noel Chiappa wrote:
> If so, that's odd: I myself found it 'bloody rude' (well, actually, I'd use a
> slightly different term, but hey...) for someone to make suggestions on how
> to improve our meeting process when they have really no experience of it.


You are free to have any reaction you want, about the person or what 
they say.

You are free to have reactions that are well-founded or not.

However you should not be free to voice whatever you want publicly, in a 
professional environment that expects professional demeanor.

In such an environment there need to be constraints on the content of 
speech, and an essential constraint is to largely refrain from ad 
hominems.  Or at least to be extremely careful about introducing 
comments or questions about a speaker.

This does not require a sterile communications environment.  It's 
possible to conform to this constraint while still having a personable 
community.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Feb 24 14:21:05 2014
Return-Path: <geoff.ietf@mulligan.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F4861A0307; Mon, 24 Feb 2014 14:21:01 -0800 (PST)
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, HTML_MESSAGE=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZHUvywixcc3y; Mon, 24 Feb 2014 14:20:58 -0800 (PST)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 99D061A02E4; Mon, 24 Feb 2014 14:20:58 -0800 (PST)
Received: from [199.233.92.4] (unknown [199.233.92.4]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 13F6A20618; Mon, 24 Feb 2014 15:20:56 -0700 (MST)
Message-ID: <530BC5C9.1@mulligan.com>
Date: Mon, 24 Feb 2014 15:20:57 -0700
From: Geoff Mulligan <geoff.ietf@mulligan.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: Okafor Chukwuemeka <directorofsoftwareunibuja@gmail.com>,  Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Re: [89attendees] The SmartAmerica Challenge [update] and Presidential Innovation Fellows - Round 3
References: <igbqgahlngwfi259022x135g.1393062607140@email.android.com>	<53088053.2010704@sunet.se>	<10916FE2-1248-4A27-BBC2-75895BC1E96D@wierenga.net>	<CADnDZ8-EOweed_4ZtGNL-mCh2+5S3hjedVgFhLnPf=6tNssMkA@mail.gmail.com>	<AE8CCC6A-2896-4751-8794-42EB1394F9A6@icloud.com>	<53093CAA.2000404@mulligan.com>	<CADnDZ8_81H3Ltvu3UzFFPrFwWkG3a2ah5ptgDrDTYj2azjkdyg@mail.gmail.com> <CAJbqm+OskWP_dkh1w6m6ee9W71eBH6UDsrdyoet1n_0wRxnA7w@mail.gmail.com>
In-Reply-To: <CAJbqm+OskWP_dkh1w6m6ee9W71eBH6UDsrdyoet1n_0wRxnA7w@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------090306070005090802090000"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_fErZzS9Cz9T4aO4fgXq4gjaDm4
Cc: ietf@ietf.org, "89attendees@ietf.org" <89attendees@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 22:21:01 -0000

This is a multi-part message in MIME format.
--------------090306070005090802090000
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The SmartAmerica Challenge is a Presidential Innovation Fellows project 
to show how combinations of Cyber-Physical Systems testbeds from 
different industry segments can show measurable and tangibenefitsble . 
The Challenge is about taking the research in CPS and building solutions 
that will benefit with new jobs, save lives and improve the economy.

We launched the Challenge on Dec 12 at the White House with 60 
participants and created 12 projects.  At the Feb 11 TechJam held at 
NIST we had briefings on the current 18! projects and since that time we 
have launched 2 more projects.  The projects cover areas of Intelligent 
Transportation, Smart Manufacturing, Smart Energy, Healthcare, High 
Confidence Network fabric (SDN, and Security), and Disaster Response.

Over the next 3 months the teams will be working diligently and 
tirelessly to make their systems and ideas come alive in time for the 
SmartAmerica Summit to be held as a multi-day event in June at the White 
House.

So why am I bothering the list with this...

1) Though the time is short, if you or your company is working on CPS 
and think that you might have something to contribute, there is still 
time to engage in the Challenge - I want to give you more information 
and answer your questions.

2) The Presidential Innovation Fellow program is about the start 
searching for the next round of participants.  I would like to let folks 
know about the program and provide some information about applying

3) The IPSO Alliance has launched the IPSO Challenge 2014 where we are 
searching for cool/innovative/earth-shattering ideas/products/devices.  
We are giving away over $50K USD in prizes and we just require that you 
must be able to build your idea or concept or bring your product or 
device and that it MUST use IP! So I also want to tell folks how they 
can enter the contest and win some money.

Geoff

-- 
*Geoff Mulligan | Presidential Innovation Fellow | Executive Office of 
the President | 301.975.6283*

On 02/23/2014 06:22 PM, Okafor Chukwuemeka wrote:
> Could you share some more info on it... I think I might be interested...
>
> Chuks
>
>
> On Sun, Feb 23, 2014 at 8:35 AM, Abdussalam Baryun 
> <abdussalambaryun@gmail.com <mailto:abdussalambaryun@gmail.com>> wrote:
>
>     Give us small summary or reference to the presentation, the time
>     period, and who is it targeting (is it for only IETF American
>     participants or it is for the IETF world participants?) that
>     information will help me know if I can attend.
>
>     Thanks, and see you in London,
>
>     AB
>
>     On Sunday, February 23, 2014, Geoff Mulligan wrote:
>
>         At a previous IETF I gave a talk about the SmartAmerica
>         Challenge project which is part of the White House's
>         Presidential Innovation Fellows program.  The Challenge has
>         started and we have over 20 projects.
>
>         I would like to give an update if anyone is interested - tell
>         you about the projects and our plans for the next 4 months.
>
>         In addition the White House will soon announce opening the
>         next round of Presidential Innovation Fellows applications.  I
>         would like to spend a few minutes to let you know about the
>         program and hopefully get you interested in serving.
>
>         I have requested a room, but don't know if I'll get one.
>
>         In the mean time please reply directly to me if you would like
>         to attend so that I can work to get an appropriately sized room.
>
>         I am thinking Thursday evening since Bits and Bites is
>         canceled, but possibly Wednesday evening after the plenary.
>
>         Do let me know your preference.
>
>                 Geoff
>
>         Now back to your regularly schedule elevator/cookie discussion....
>
>
>         _______________________________________________
>         89attendees mailing list
>         89attendees@ietf.org
>         https://www.ietf.org/mailman/listinfo/89attendees
>
>
>     _______________________________________________
>     89attendees mailing list
>     89attendees@ietf.org <mailto:89attendees@ietf.org>
>     https://www.ietf.org/mailman/listinfo/89attendees
>
>


--------------090306070005090802090000
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">
    The SmartAmerica Challenge is a Presidential Innovation Fellows
    project to show how combinations of Cyber-Physical Systems testbeds
    from different industry segments can show measurable and
    tangibenefitsble . The Challenge is about taking the research in CPS
    and building solutions that will benefit with new jobs, save lives
    and improve the economy.<span
      style="font-size:12pt;background-color:white;">
      <div style="margin-top:0;margin-bottom:0;"><br>
      </div>
    </span>We launched the Challenge on Dec 12 at the White House with
    60 participants and created 12 projects.&nbsp; At the Feb 11 TechJam held
    at NIST we had briefings on the current 18! projects and since that
    time we have launched 2 more projects.&nbsp; The projects cover areas of
    Intelligent Transportation, Smart Manufacturing, Smart Energy,
    Healthcare, High Confidence Network fabric (SDN, and Security), and
    Disaster Response.<br>
    <br>
    <font color="black" face="Calibri,Arial,Helvetica,sans-serif"
      size="3"><span style="font-size:12pt;background-color:white;"><font
          face="Calibri,Arial,Helvetica,sans-serif" size="2"><span
            style="font-size:16.35px;">Over the next 3 months the teams
            will be working diligently and tirelessly to make their
            systems and ideas come alive in time
            for the SmartAmerica Summit to be held as a multi-day event
            in June at the White House.<br>
            <br>
            So why am I bothering the list with this...<br>
            <br>
            1) Though the time is short, if you or your company is
            working on CPS and think that you might have something to
            contribute, there is still time to engage in the Challenge -
            I want to give you more information and answer your
            questions.<br>
          </span></font></span></font><br>
    2) The Presidential Innovation Fellow program is about the start
    searching for the next round of participants.&nbsp; I would like to let
    folks know about the program and provide some information about
    applying<br>
    <br>
    3) The IPSO Alliance has launched the IPSO Challenge 2014 where we
    are searching for cool/innovative/earth-shattering
    ideas/products/devices.&nbsp; We are giving away over $50K USD in prizes
    and we just require that you must be able to build your idea or
    concept or bring your product or device and that it MUST use IP! So
    I also want to tell folks how they can enter the contest and win
    some money.<br>
    <br>
    Geoff<br>
    <br>
    -- <br>
    <b><small><font face="serif">Geoff Mulligan | Presidential
          Innovation Fellow | Executive Office of the President |
          301.975.6283</font></small></b><br>
    <br>
    <div class="moz-cite-prefix">On 02/23/2014 06:22 PM, Okafor
      Chukwuemeka wrote:<br>
    </div>
    <blockquote
cite="mid:CAJbqm+OskWP_dkh1w6m6ee9W71eBH6UDsrdyoet1n_0wRxnA7w@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>Could you share some more info on it... I think I might be
          interested...<br>
          <br>
        </div>
        Chuks</div>
      <div class="gmail_extra"><br>
        <br>
        <div class="gmail_quote">On Sun, Feb 23, 2014 at 8:35 AM,
          Abdussalam Baryun <span dir="ltr">&lt;<a
              moz-do-not-send="true"
              href="mailto:abdussalambaryun@gmail.com" target="_blank">abdussalambaryun@gmail.com</a>&gt;</span>
          wrote:<br>
          <blockquote class="gmail_quote" style="margin:0 0 0
            .8ex;border-left:1px #ccc solid;padding-left:1ex">Give us
            small summary or reference to the presentation, the time
            period, and who is it targeting (is it for only
            IETF&nbsp;American participants or it is for the IETF&nbsp;world
            participants?) that information will help me know if I can
            attend.&nbsp;
            <div> <br>
            </div>
            <div>Thanks, and see you in London,</div>
            <div><br>
            </div>
            <div>AB</div>
            <div class="HOEnZb">
              <div class="h5">
                <div><br>
                  On Sunday, February 23, 2014, Geoff Mulligan wrote:<br>
                  <blockquote class="gmail_quote" style="margin:0 0 0
                    .8ex;border-left:1px #ccc solid;padding-left:1ex">
                    At a previous IETF I gave a talk about the
                    SmartAmerica Challenge project which is part of the
                    White House's Presidential Innovation Fellows
                    program. &nbsp;The Challenge has started and we have over
                    20 projects.<br>
                    <br>
                    I would like to give an update if anyone is
                    interested - tell you about the projects and our
                    plans for the next 4 months.<br>
                    <br>
                    In addition the White House will soon announce
                    opening the next round of Presidential Innovation
                    Fellows applications. &nbsp;I would like to spend a few
                    minutes to let you know about the program and
                    hopefully get you interested in serving.<br>
                    <br>
                    I have requested a room, but don't know if I'll get
                    one.<br>
                    <br>
                    In the mean time please reply directly to me if you
                    would like to attend so that I can work to get an
                    appropriately sized room.<br>
                    <br>
                    I am thinking Thursday evening since Bits and Bites
                    is canceled, but possibly Wednesday evening after
                    the plenary.<br>
                    <br>
                    Do let me know your preference.<br>
                    <br>
                    &nbsp; &nbsp; &nbsp; &nbsp; Geoff<br>
                    <br>
                    Now back to your regularly schedule elevator/cookie
                    discussion....<br>
                    <br>
                    <br>
                    _______________________________________________<br>
                    89attendees mailing list<br>
                    <a moz-do-not-send="true">89attendees@ietf.org</a><br>
                    <a moz-do-not-send="true"
                      href="https://www.ietf.org/mailman/listinfo/89attendees"
                      target="_blank">https://www.ietf.org/mailman/listinfo/89attendees</a><br>
                  </blockquote>
                </div>
              </div>
            </div>
            <br>
            _______________________________________________<br>
            89attendees mailing list<br>
            <a moz-do-not-send="true" href="mailto:89attendees@ietf.org">89attendees@ietf.org</a><br>
            <a moz-do-not-send="true"
              href="https://www.ietf.org/mailman/listinfo/89attendees"
              target="_blank">https://www.ietf.org/mailman/listinfo/89attendees</a><br>
            <br>
          </blockquote>
        </div>
        <br>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------090306070005090802090000--


From nobody Mon Feb 24 14:43:11 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 0E47E1A030A for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 14:43:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.348
X-Spam-Level: 
X-Spam-Status: No, score=-107.348 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.547, 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 fmuFQ-H7qrGV for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 14:43:07 -0800 (PST)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) by ietfa.amsl.com (Postfix) with ESMTP id 3C5021A0306 for <ietf@ietf.org>; Mon, 24 Feb 2014 14:43:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2749; q=dns/txt; s=iport; t=1393281785; x=1394491385; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=tqJB5ke3Us5zLCHS00trmsrNMioTJDct3KLvq86WaYI=; b=iPzODkl8iY5FWaxc8//yTI58ANiXkQXaLKw7hSZ8dQAAJzARKe6BxAXV InvCRuAR4De/kAGyKU6b2J4h2hoon2JjBFYx6HzDezuQMqwgmgToKVZz2 t7N0KbPeAPDQBXROTIn/UxUdHWea2rQR+olotLK0zm2w2diT9KEnIF3Be M=;
X-Files: signature.asc : 195
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgIFANLJC1OtJXG9/2dsb2JhbABZgwaBEsEtgSAWdIIlAQEBBHkQAgEIDgojCzIlAgQOBQ6Hd8YMF45kB4MkgRQEkEKBM4Y/kieBb4E+gio
X-IronPort-AV: E=Sophos;i="4.97,537,1389744000";  d="asc'?scan'208";a="22853065"
Received: from rcdn-core2-2.cisco.com ([173.37.113.189]) by alln-iport-7.cisco.com with ESMTP; 24 Feb 2014 22:43:05 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core2-2.cisco.com (8.14.5/8.14.5) with ESMTP id s1OMh5Rw017976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 24 Feb 2014 22:43:05 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.247]) by xhc-rcd-x04.cisco.com ([fe80::200:5efe:173.37.183.34%12]) with mapi id 14.03.0123.003; Mon, 24 Feb 2014 16:43:05 -0600
From: "Fred Baker (fred)" <fred@cisco.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Topic: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Index: AQHPMZ0kYKq8E8L/YEygZjqPN59uS5rFZOiA
Date: Mon, 24 Feb 2014 22:43:04 +0000
Message-ID: <00D21295-2E84-4CF1-9ABA-E2024D245580@cisco.com>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info>
In-Reply-To: <20140224201457.GO35396@mx1.yitter.info>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.21.73.233]
Content-Type: multipart/signed; boundary="Apple-Mail=_DBAF5E65-4449-41DF-9A76-2FE699194CFC"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/e5XZO7O8bXkxvaMWvfvGZ0mI5fw
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, 24 Feb 2014 22:43:09 -0000

--Apple-Mail=_DBAF5E65-4449-41DF-9A76-2FE699194CFC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On Feb 24, 2014, at 12:14 PM, Andrew Sullivan <ajs@anvilwalrusden.com> =
wrote:
> On Mon, Feb 24, 2014 at 02:37:13PM -0500, Phillip Hallam-Baker wrote:
>> Could we have an RFC to explain what is and what is not a valid =
ad-hominem
>> argument?
>=20
> There are no valid _ad hominem_ arguments.  _Ad hominem_ is a short
> name of a fallacious form or reasoning where one attacks the person
> making the argument _instead of_ attacking the argument as such.
> (More fully, of course, it's known as _argumentum ad hominem_.)
>=20
>> Ad Hominem is a perfectly valid argument against claims of fact when =
made
>> against the authority making the claim. "PT Barnum is a notorious =
liar' is
>> a perfectly valid argument against a claim PT Barnum is making about =
having
>> found a mermaid.
>=20
> I think this is only sort of true.=20

I think the context is relevant here. In a court of law, discrediting a =
witness is, as you note, a counter-argument to the train of argument =
being made by the side s/he is a witness for. In the book/movie "the =
girl who kicked the hornet's nest", Lisbet is brought up on charges that =
are not only untrue but are in fact an ad hominem on charges she is =
bringing. She demonstrates the factuality of her statements from =
records, and demonstrates that her opponents cannot do the same, and in =
fact have criminal reasons to have her viewpoint suppressed. Yes, she =
demonstrates that one is a pornographer and another is a murderer, and =
12 people are taken into custody as a result of her testimony and =
pre-trial activities. While it is an attack on a person, it is =
demonstrating criminal intent and behavior.

In an IETF meeting, we are not discussing criminal matters; we are =
discussing ideas. Even if the party proposing an idea were a criminal, =
his or her criminal nature would be irrelevant to the idea - it might or =
might not be a good one.=20

So from my perspective, I would agree with your opening statement. Ad =
Hominum arguments have no place in our process.


--Apple-Mail=_DBAF5E65-4449-41DF-9A76-2FE699194CFC
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

iD8DBQFTC8r3bjEdbHIsm0MRAj1DAKC4ajsv5si4ZljFGziHZ1SV6auubgCdHZIc
ZV2zXjuF4gVA8pLjr6FqyyA=
=l57r
-----END PGP SIGNATURE-----

--Apple-Mail=_DBAF5E65-4449-41DF-9A76-2FE699194CFC--


From nobody Mon Feb 24 14:57:28 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 BF06E1A01BB for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 14:57:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 GeYE8QA72Eax for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 14:57:25 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id AD5011A01B7 for <ietf@ietf.org>; Mon, 24 Feb 2014 14:57:25 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.42]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1OMvBbZ007056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 24 Feb 2014 14:57:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393282643; bh=ByWPXN8mYJ2dlUKeQhfmThicyGO9krnfsALOs7WZ1zo=; h=Date:To:From:Subject:In-Reply-To:References; b=vbZPTUSxkz06BfYVwZFf7Iyz16o8h7NQjQI7Qwy0igSr8veacQgjtktNgAuKnLKcZ 6WLSswrOEA+lAKM+QbjQq5DwcHWNNpatK3cXHl1cXtG+Gsc0CHWPAaakSpppKu2n3f 9mdblILvFdx/fcM77KFKRA0Hwuwe5YNYdXXa6ibA=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393282643; i=@elandsys.com; bh=ByWPXN8mYJ2dlUKeQhfmThicyGO9krnfsALOs7WZ1zo=; h=Date:To:From:Subject:In-Reply-To:References; b=dnTO1RcIxWLsaIA+f5CWvTW6PDSRdWaH4sUi1SAwQ3AqSJxRXMocGokVPVNJrd6o1 /zCBovlxuVym7JSgIBYPTqKcAnUWSHVOp9oskRQPuESzC4W4y0D9hM55X7lrHbkmwB 2M/p68GNca3ThLXR53f34VmOAZKLdsb54yu7SB0s=
Message-Id: <6.2.5.6.2.20140224141310.0d564b28@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 24 Feb 2014 14:55:09 -0800
To: jnc@mercury.lcs.mit.edu (Noel Chiappa), ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
In-Reply-To: <20140224213030.C5E6718C126@mercury.lcs.mit.edu>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Tt6xofjcA4IapIJSt1_kU34a3f8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Feb 2014 22:57:26 -0000

Hi Noel,
At 13:30 24-02-2014, Noel Chiappa wrote:
>You mean, it's rude to ask what someone's experience is?
>
>If so, that's odd: I myself found it 'bloody rude' (well, actually, I'd use a
>slightly different term, but hey...) for someone to make suggestions on how
>to improve our meeting process when they have really no experience of it.

There is a message at 
http://www.ietf.org/mail-archive/web/diversity/current/msg00074.html 
I personally do not think that it is a good idea to belittle or 
humiliate a person.

Regards,
S. Moonesamy 


From nobody Mon Feb 24 21:32:05 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 E66E61A02D2 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 21:32:03 -0800 (PST)
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_50=0.8,  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 YexYQ7yizSTP for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 21:32:01 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.170]) by ietfa.amsl.com (Postfix) with ESMTP id 976A81A0274 for <ietf@ietf.org>; Mon, 24 Feb 2014 21:32:00 -0800 (PST)
Received: from [195.245.230.131:6968] by server-10.bemta-3.messagelabs.com id C9/11-07302-FCA2C035; Tue, 25 Feb 2014 05:31:59 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-13.tower-78.messagelabs.com!1393306318!28500489!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 1303 invoked from network); 25 Feb 2014 05:31:58 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-13.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 25 Feb 2014 05:31:58 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Tue, 25 Feb 2014 05:31:58 +0000
From: <l.wood@surrey.ac.uk>
To: <fred@cisco.com>, <ajs@anvilwalrusden.com>
Date: Tue, 25 Feb 2014 05:31:57 +0000
Subject: RE: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Topic: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Index: AQHPMZ0kYKq8E8L/YEygZjqPN59uS5rFZOiAgAAKBHA=
Message-ID: <290E20B455C66743BE178C5C84F1240847E633472B@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info>, <00D21295-2E84-4CF1-9ABA-E2024D245580@cisco.com>
In-Reply-To: <00D21295-2E84-4CF1-9ABA-E2024D245580@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/W-2bPZdLMHSHPWKh_Dt7WGZLdRw
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, 25 Feb 2014 05:32:04 -0000

This ongoing discussion of what constitutes an ad hominem argument is all v=
ery well,
but I'd like to point out that I didn't make an ad hominem argument or asse=
rtion.

I simply asked a question.

On another note, Fred, perhaps I'm in the minority here for not having yet =
read the novels
you refer to, or watched any film adaptations. But if the best argument you=
 can think
of is based on fiction (which is to say, argumentum ad exemplum, quoting a =
sermon to
support a moral point) and giving away the plot, do at least have the court=
esy to prefix
it with a warning saying SPOILER ALERT.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Fred Baker (fred) [fred@cis=
co.com]
Sent: 24 February 2014 22:43
To: Andrew Sullivan
Cc: <ietf@ietf.org>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for p=
resentations and face2face discussions)

On Feb 24, 2014, at 12:14 PM, Andrew Sullivan <ajs@anvilwalrusden.com> wrot=
e:
> On Mon, Feb 24, 2014 at 02:37:13PM -0500, Phillip Hallam-Baker wrote:
>> Could we have an RFC to explain what is and what is not a valid ad-homin=
em
>> argument?
>
> There are no valid _ad hominem_ arguments.  _Ad hominem_ is a short
> name of a fallacious form or reasoning where one attacks the person
> making the argument _instead of_ attacking the argument as such.
> (More fully, of course, it's known as _argumentum ad hominem_.)
>
>> Ad Hominem is a perfectly valid argument against claims of fact when mad=
e
>> against the authority making the claim. "PT Barnum is a notorious liar' =
is
>> a perfectly valid argument against a claim PT Barnum is making about hav=
ing
>> found a mermaid.
>
> I think this is only sort of true.

I think the context is relevant here. In a court of law, discrediting a wit=
ness is, as you note, a counter-argument to the train of argument being mad=
e by the side s/he is a witness for. In the book/movie "the girl who kicked=
 the hornet's nest", Lisbet is brought up on charges that are not only untr=
ue but are in fact an ad hominem on charges she is bringing. She demonstrat=
es the factuality of her statements from records, and demonstrates that her=
 opponents cannot do the same, and in fact have criminal reasons to have he=
r viewpoint suppressed. Yes, she demonstrates that one is a pornographer an=
d another is a murderer, and 12 people are taken into custody as a result o=
f her testimony and pre-trial activities. While it is an attack on a person=
, it is demonstrating criminal intent and behavior.

In an IETF meeting, we are not discussing criminal matters; we are discussi=
ng ideas. Even if the party proposing an idea were a criminal, his or her c=
riminal nature would be irrelevant to the idea - it might or might not be a=
 good one.

So from my perspective, I would agree with your opening statement. Ad Homin=
um arguments have no place in our process.


From nobody Mon Feb 24 21:40:08 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 328511A02E5 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 21:40:06 -0800 (PST)
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 6j36HdEw4wx8 for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 21:40:05 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id EA8C11A0274 for <ietf@ietf.org>; Mon, 24 Feb 2014 21:40:04 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1P5e0BZ004830 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 24 Feb 2014 21:40:03 -0800
Message-ID: <530C2C78.3050602@bbiw.net>
Date: Mon, 24 Feb 2014 21:39:04 -0800
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.3.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk
Subject: Re: Ad hominems
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info>, <00D21295-2E84-4CF1-9ABA-E2024D245580@cisco.com> <290E20B455C66743BE178C5C84F1240847E633472B@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E633472B@EXMB01CMS.surrey.ac.uk>
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, 24 Feb 2014 21:40:04 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_kw_VvY45iFk2eiR8Hxq0JbYpDU
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, 25 Feb 2014 05:40:06 -0000

On 2/24/2014 9:31 PM, l.wood@surrey.ac.uk wrote:
> This ongoing discussion of what constitutes an ad hominem argument is all very well,
> but I'd like to point out that I didn't make an ad hominem argument or assertion.
>
> I simply asked a question.


The form of your note was not the issue.  It was the substance.  The 
substance was directed at a person and was /about/ that person.  It's 
the 'about' that made it ad hominem.

By way of example...

If I responded to your note by "just asking a question" such as:

    So, Lloyd, did you ever go to school?

or

    Didn't your school ever teach you about semantics?

or

    Lloyd, where did you learn your group participation skills?

I'd simply be asking a question.

But I'd also be making a pointed ad hominem attack and no reader will 
miss that fact.

By contrast, if I sent a note that only contained the above first 
paragraph, I'd be focusing on the substance of the issue and would not 
be asking or commenting about you as a person.  (Yes, my first paragraph 
has the word "your" in it.  The presence of the word doesn't make the 
text ad hominem.  The semantics either do or don't.  First paragraph: 
doesn't.  Later questions: do.


d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Feb 24 21:51:26 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 EA2161A02EA for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 21:51:24 -0800 (PST)
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 R0aikYCiq9Ac for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 21:51:23 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.175]) by ietfa.amsl.com (Postfix) with ESMTP id 82C3E1A02E7 for <ietf@ietf.org>; Mon, 24 Feb 2014 21:51:22 -0800 (PST)
Received: from [85.158.137.99:49306] by server-15.bemta-3.messagelabs.com id 18/1A-19263-95F2C035; Tue, 25 Feb 2014 05:51:21 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-3.tower-217.messagelabs.com!1393307480!14487652!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23279 invoked from network); 25 Feb 2014 05:51:20 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-3.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 25 Feb 2014 05:51:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Tue, 25 Feb 2014 05:51:20 +0000
From: <l.wood@surrey.ac.uk>
To: <dcrocker@bbiw.net>
Date: Tue, 25 Feb 2014 05:49:43 +0000
Subject: RE: Ad hominems
Thread-Topic: Ad hominems
Thread-Index: Ac8x7ArwDKy0eoZ8Q7+bl0QDZPQ6yQAAVczU
Message-ID: <290E20B455C66743BE178C5C84F1240847E633472D@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info>, <00D21295-2E84-4CF1-9ABA-E2024D245580@cisco.com> <290E20B455C66743BE178C5C84F1240847E633472B@EXMB01CMS.surrey.ac.uk>, <530C2C78.3050602@bbiw.net>
In-Reply-To: <530C2C78.3050602@bbiw.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/deSOpQZjG9_7UnxmTOfXHB4TGgo
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, 25 Feb 2014 05:51:25 -0000

>      Lloyd, where did you learn your group participation skills?

The IETF!

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Dave Crocker [dcrocker@bbiw.net]
Sent: 25 February 2014 05:39
To: Wood L  Dr (Electronic Eng)
Cc: ietf@ietf.org
Subject: Re: Ad hominems

On 2/24/2014 9:31 PM, l.wood@surrey.ac.uk wrote:
> This ongoing discussion of what constitutes an ad hominem argument is all=
 very well,
> but I'd like to point out that I didn't make an ad hominem argument or as=
sertion.
>
> I simply asked a question.


The form of your note was not the issue.  It was the substance.  The
substance was directed at a person and was /about/ that person.  It's
the 'about' that made it ad hominem.

By way of example...

If I responded to your note by "just asking a question" such as:

    So, Lloyd, did you ever go to school?

or

    Didn't your school ever teach you about semantics?

or

    Lloyd, where did you learn your group participation skills?

I'd simply be asking a question.

But I'd also be making a pointed ad hominem attack and no reader will
miss that fact.

By contrast, if I sent a note that only contained the above first
paragraph, I'd be focusing on the substance of the issue and would not
be asking or commenting about you as a person.  (Yes, my first paragraph
has the word "your" in it.  The presence of the word doesn't make the
text ad hominem.  The semantics either do or don't.  First paragraph:
doesn't.  Later questions: do.


d/

--
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Mon Feb 24 23:36:36 2014
Return-Path: <barryleiba.mailing.lists@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 64D0A1A052E for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 23:36:35 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, 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 aSYttno3B8oI for <ietf@ietfa.amsl.com>; Mon, 24 Feb 2014 23:36:34 -0800 (PST)
Received: from mail-ve0-x22a.google.com (mail-ve0-x22a.google.com [IPv6:2607:f8b0:400c:c01::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 34ADF1A0346 for <ietf@ietf.org>; Mon, 24 Feb 2014 23:36:34 -0800 (PST)
Received: by mail-ve0-f170.google.com with SMTP id c14so13485vea.29 for <ietf@ietf.org>; Mon, 24 Feb 2014 23:36:33 -0800 (PST)
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=cJvjDbPiDWeqPtuOWBqSx25blcxcmSaMC79z3yF8hi4=; b=VNNYmR5RshnOPbF4cJzDM3J7wsnLR2BqoysaRmCGf84LLCpO9dnHTkDNPsBwKMJWOR +pOxV3ywc7zV8tilC4sXqAk7y0By5yWML6cFu9R2d0TGAsFcf6EIBvlSci/HFYE70JZM IsJWvjnUByBHUX97/dRk6ISNgtK8aasbFVUhsE2GAJQVDu53lGXKMfIVNtxdTqgKlI0r tR/o7JSVZuhGH2CucPi5jVPElKYsTsVF00i0cF39Ct0qx6iqGQjHrVLexhvP8H5krvxk tcHoxeef8gCC4hztHAiqC92U/KfDYHls8ApsXI965eyp9+uWMaL2Zsyi5gYLIbZ2HTZz L56g==
MIME-Version: 1.0
X-Received: by 10.220.106.84 with SMTP id w20mr32472vco.18.1393313793263; Mon, 24 Feb 2014 23:36:33 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.19.104 with HTTP; Mon, 24 Feb 2014 23:36:33 -0800 (PST)
In-Reply-To: <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com>
Date: Mon, 24 Feb 2014 23:36:33 -0800
X-Google-Sender-Auth: 2Qfxnm_NaVd6d3CLGgXMbSWVSsY
Message-ID: <CAC4RtVBfMFijaZt8_AhBuic8yFqc+OJAJCWrmpfBqRgJgJ-L4Q@mail.gmail.com>
Subject: Re: calls for discussion
From: Barry Leiba <barryleiba@computer.org>
To: Margaret Wasserman <margaretw42@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hox0BoPxMCz1gdzzyci11DgrQ2s
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: Tue, 25 Feb 2014 07:36:35 -0000

Sorry for being late with this: I'm behind, and catching up.

Margaret says...
> and in many WGs, _all_ of the most important decisions have been made
> in a meeting room at an IETF plenary meeting (and merely "confirmed"
> on the list) for many years.  In other words, most of our work is
> _not_ done on the mailing lists, or even by people who are reading
> most of the messages that are sent to those lists.

Indeed.  When I do my document reviews for IESG telechats, I read the
shepherd writeups (and really appreciate the good ones!), have a look
at the document history in the datatracker and any last-call
discussions, and, depending upon what I find, sometimes go look at the
working group discussions.

There have been times when a search for the document name in the
working group list archive looked something like this:

[lmnop] New Version Notification - draft-ietf-lmnop-banana-07.txt,
internet-drafts
[lmnop] New Version Notification - draft-ietf-lmnop-banana-06.txt,
internet-drafts
[lmnop] New Version Notification - draft-ietf-lmnop-banana-05.txt,
internet-drafts
[lmnop] New Version Notification - draft-ietf-lmnop-banana-04.txt,
internet-drafts
[lmnop] New Version Notification - draft-ietf-lmnop-banana-03.txt,
internet-drafts

In other words, no discussion whatsoever... just document revisions.

I would ask the responsible AD where the discussion was that produced
each of these revs, and the AD would say, well, this is one of those
working groups that does all of its work in the meetings, and they got
a lot done on this document at IETF this, and IETF that.  So I'd go
look at the minutes from those IETF meetings.

Guess what I didn't find.

I'm sure there was discussion in the meetings, but there was little or
nothing documenting it, and no explicit calls for discussion on the
mailing list, at least not with the document name associated with it.
(It's possible that issues were discussed, and the document name
wasn't mentioned, but the chairs and AD didn't help point me at them.)

This hasn't happened in a while.  It gave me a very uneasy feeling,
and I intent to push back harder should it happen again.  I believe
that we need to be having these discussions on the mailing list.  I
believe that discussions that are relied on from the meetings need to
be minuted in a way that those not present can find and review them.
And I believe that we need to have a record of reaching consensus on a
document.  A series of document revs followed by a last call, with
little or no record of discussion, just doesn't make it.

Barry


From nobody Tue Feb 25 00:10:53 2014
Return-Path: <lars@netapp.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 655DD1A040E for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 00:10:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.35
X-Spam-Level: 
X-Spam-Status: No, score=-5.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_08=1.651, HTML_IMAGE_RATIO_02=0.437, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, 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 FmrkVX-6MHFX for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 00:10:47 -0800 (PST)
Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by ietfa.amsl.com (Postfix) with ESMTP id 8EA8E1A03C5 for <ietf@ietf.org>; Tue, 25 Feb 2014 00:10:46 -0800 (PST)
X-IronPort-AV: E=Sophos;i="4.97,538,1389772800";  d="asc'?jpg'145?scan'145,208,217,145";a="145254986"
Received: from vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) by mx12-out.netapp.com with ESMTP; 25 Feb 2014 00:10:45 -0800
Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.211]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.03.0123.003; Tue, 25 Feb 2014 00:10:45 -0800
From: "Eggert, Lars" <lars@netapp.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Ad hominems
Thread-Topic: Ad hominems
Thread-Index: AQHPMewMnq7UojwWCU6Mva6UC3U6nJrF/QeAgAAnZ4A=
Date: Tue, 25 Feb 2014 08:10:45 +0000
Message-ID: <A69B9723-DA0C-462D-92A6-001B7EFE3DE4@netapp.com>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info>, <00D21295-2E84-4CF1-9ABA-E2024D245580@cisco.com> <290E20B455C66743BE178C5C84F1240847E633472B@EXMB01CMS.surrey.ac.uk>, <530C2C78.3050602@bbiw.net> <290E20B455C66743BE178C5C84F1240847E633472D@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E633472D@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.122.105.18]
Content-Type: multipart/signed; boundary="Apple-Mail=_63A6ECF9-E510-4CCA-9FFF-1FDAC57A3B98"; protocol="application/pgp-signature"; micalg=pgp-sha1
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/j8yGJ1zK2GY5GgP96VUVl-5Z7B0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Feb 2014 08:10:49 -0000

--Apple-Mail=_63A6ECF9-E510-4CCA-9FFF-1FDAC57A3B98
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_80F7AF02-A57D-492A-BB1A-EADACB4A44D8"


--Apple-Mail=_80F7AF02-A57D-492A-BB1A-EADACB4A44D8
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

I suggest we use this as the new Note Well.

Lars


--Apple-Mail=_80F7AF02-A57D-492A-BB1A-EADACB4A44D8
Content-Type: multipart/related;
	type="text/html";
	boundary="Apple-Mail=_28390993-0824-4076-9BB4-A393B4240961"


--Apple-Mail=_28390993-0824-4076-9BB4-A393B4240961
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=us-ascii

<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">I suggest we use this as the new Note Well.<div><br></div><div>Lars</div><div><br></div><div><img apple-inline="yes" id="46441195-F5A3-4521-9CD3-8C0CBBFFEA48" height="679" width="637" apple-width="yes" apple-height="yes" src="cid:61260F18-5AA2-412B-B26E-26960AC835C0@hq.netapp.com"></div></body></html>
--Apple-Mail=_28390993-0824-4076-9BB4-A393B4240961
Content-Transfer-Encoding: base64
Content-Disposition: inline;
	filename=1483220_718769974810683_97803309_n.jpg
Content-Type: image/jpg;
	x-unix-mode=0644;
	name="1483220_718769974810683_97803309_n.jpg"
Content-Id: <61260F18-5AA2-412B-B26E-26960AC835C0@hq.netapp.com>

/9j/4AAQSkZJRgABAgAAAQABAAD//gAEKgD/4gIcSUNDX1BST0ZJTEUAAQEAAAIMbGNtcwIQAABt
bnRyUkdCIFhZWiAH3AABABkAAwApADlhY3NwQVBQTAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
9tYAAQAAAADTLWxjbXMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAApkZXNjAAAA/AAAAF5jcHJ0AAABXAAAAAt3dHB0AAABaAAAABRia3B0AAABfAAAABRyWFla
AAABkAAAABRnWFlaAAABpAAAABRiWFlaAAABuAAAABRyVFJDAAABzAAAAEBnVFJDAAABzAAAAEBi
VFJDAAABzAAAAEBkZXNjAAAAAAAAAANjMgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB0ZXh0AAAA
AEZCAABYWVogAAAAAAAA9tYAAQAAAADTLVhZWiAAAAAAAAADFgAAAzMAAAKkWFlaIAAAAAAAAG+i
AAA49QAAA5BYWVogAAAAAAAAYpkAALeFAAAY2lhZWiAAAAAAAAAkoAAAD4QAALbPY3VydgAAAAAA
AAAaAAAAywHJA2MFkghrC/YQPxVRGzQh8SmQMhg7kkYFUXdd7WtwegWJsZp8rGm/fdPD6TD////b
AEMACQYHCAcGCQgICAoKCQsOFw8ODQ0OHBQVERciHiMjIR4gICUqNS0lJzIoICAuPy8yNzk8PDwk
LUJGQTpGNTs8Of/bAEMBCgoKDgwOGw8PGzkmICY5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5
OTk5OTk5OTk5OTk5OTk5OTk5OTk5Of/CABEIAqcCfQMAIgABEQECEQH/xAAbAAACAwEBAQAAAAAA
AAAAAAAAAQIDBQQGB//EABcBAQEBAQAAAAAAAAAAAAAAAAABAgP/xAAXAQEBAQEAAAAAAAAAAAAA
AAAAAQID/9oADAMAAAERAhEAAAHxLiibrCZAJusJkAmQCbrCbrCwrZNQCxQCxQC0rCbqZYoskoBJ
1smQkOVLJOKJCiTcUTcAtUXF90Thp0Wc+oTpfaTK2OIiaiy6zn6eVsqsrzalWd8ycEWRgxuDJqAT
K2ScUSdYNOIMQAAADQNMEwAAAQADTBAAxDlFg0yKkhTTIgAgHKAOSCLTAUh2VdeUq5189Om7n3Gw
3IxENpE0Mldz34oyEtblHeYxkqUoyHGSHGURIBuIABOE4AAGhnh9Az7eA4M/2fQeJ4/ceHPaYuj0
EvG+o86ej6LPPnBb6aR5W301p4+70V55fj9tM8py+6DxtHr6jkw/VB5ej2UjyfP72B4zV1Ljx0PR
2HjdCj1B57b08g4ebR5jO0dq7LzMvS2y+e4/U06nka9XIoU4khMi2g6+XqwlTYsajDo4tyUG9yJJ
CnEJwJFckhpghonCSEANNGrVns0bcgNvFTNCjmR6PzgGr2+dDR7MJmmswNMzQ0ujFD0fPiBp2ZDN
3kzGaRmo9JxZAaVmSjfpx2L0XnWd8eFndueWZs34k+d9N2ePcdHd5+PSXUxdMaFKLAnWStiovlB8
tPm6ubUg0dI4yQ4yQOMhRkBFsg0yUJwAAByIrprKzR5CgYCdpSTgB28YhyIOcBPp5yMpdeXC7+pc
06qyk6Q5i12VRuRBdHPQO0ri4hJImp2RaRXLTj0UVyu1dc1ropE4zENkJwmVyJl81bw1zw6bNTOR
b1lKvpAjITsgRJwCPRSJWKFGSoTQNM0c+cTv0/PM3ubMDs0/OXGp1+b6DT4+Os9BViyOrX87ab3N
lyjcjk1Yvdo+aem7HBsTU7sKs3oYli7FuRHDr7Mawn15XTXTPNeprPAemh3+fvjbxZR53RM+rTaz
uKvc3LsCwu1/OdBtRxOgu0sKo3DDkbcc23jb+vOqjsp4qu836Mew15YV0a9mUYutXnUmzh3RHTIj
njOHWCGCGAAJoYMSYMiyUWyJJkVKB1SUOVqQukAVMTGgCUQm4KLbeYjvOSfO2y5+hUpOOa6D1LoV
1xZV0c+kFJdJN0yJImIcScIBZOMi+VNnGyUYywqtu3OeciIXVC2SoJLVTDS6kjqJwlo4ygDQF1PU
Onr4Tv5erVPNHouYxre3UPNR3OsxOXd5DOlvVmNV3bBhGxZi+aPR1amCvUwrzL9Baeae9aYFOvaY
b9DymUvQh549LE85btXxh26Zm5NPocs4J+j4YzIb6PNnqa9zzMvSZ1cBrUmcblp5yPpuUyDa6Ywr
NyjlcePRraefno9MYstWOmLT6fP1MuO7CshNCgMJKI4ziCYE6w6aYhKUqC8o6ii+iJZbzMsjFFkq
bAdaLba6o6YK3NnyWU7lr57wjX1FUunkIyrZOVAdXTmM0+Km8hKNo5c/Vzsr+W3FpdEdzpsoct/J
ZOSHP28uzsovs6oVR52TVa3RqnUnZXkc9vJ0k7uaW5dBIdtIREgAGNDi4jEw0M+Zr9Hn7jeWAjQ6
8ORq9fnJm/n58TZtxA368ZHoc3PrNbs8/M6trzE42L8iMulZiV6j1cqw7+7AD0VWJA7e7Bma/V52
01+HPD0vNk1HpKce/F7oc0Yp5LqtQtplXQKfOyjZXmklIjKFVk6UukXbyXS9FNtXOvm6+TcjOJ0k
osFODIpggRJIJxlEAQMAYCYgaYmIaJBGcQBA0xAhtSJWUyyv5ukzeePWq5HKG5IQKUWJSQMABl1k
pcdVWwcUVXXbnJ0xlDnCeaq4w3OiFIWzqthU2xK+gkSrsWKuXop3KlNdY1GQSTKyURIYKSHGcRDB
X09BOnRzDu5evTPNP0XMYtvdpnm1t9Zi8W9xma/Q1mJX36Z5+PpLDzD7tY829noMh7fDzvDH0PFG
RR6Q3MKr0VmnmHt3GDVrdp5uen2Hnp+hsjIhu18tYcfQ16mPZtceXDRp9W3nYaGlqYlW+VhVehiY
F984gtKzNyLtmjDINTNiuroZyRku8rlNBBsSsRTMQiYRTiNoBxC+FbLHWFxSidsuYnbVIiqwsmqS
+XOjpjUiV3Myy3nC6/heXbHmUvXCu+K0UbkrOd1ZbyssnROOpVPN6XzywvjBynLKrrm2VL0c4Isj
CB0Khl8qIl6ridNnDblo86ny1Misqar5dZTCyncGlTigky/KFsTF5ozj1ggH38HSbtGbUbPR5mZs
9XmrTR6MOw9DxZNZsWYyOrgtqIthEkgUkJiGiQ0IdtLjur5+rneNdFW5E6GsScsK5TpIOdlJCzaF
KPbLTBqLCNkRtBCYELYWkHGzLokU8dTijSbpsQGpaqeuHScvUrIVd9eS5yPSNNaIGIAkhADAGIYR
GCkmBFgSgEiJIiwaBSTAYJNkbK74mC56nEtiFCfSF3NcnRXJ8tVxnHShRs65UbKxMY5VyJFUhSlW
OTiPp5OjKaur5aUkHHIj2zfOm3FdkLedUVCjlur65UZPRQsrGmgZ1Ea9XHO/l6tU80ei5jGt7dQ8
3Hc6jF5N3jMye/AxY9uweYPSI829fQPOT7eow1vcJnHoLDznRtWxgPZnm4s+6szZ7OZS5/S0Zed6
N3mrNNuWLiQ2p2eXexX1mU/RM89HVsM2O3wnHV6TNMyXoGeclt9J5x7k4xp7dfO5MO/pPPz0u7TE
lsSyw4T566Clk421xTDr59yEZLQQA1Iku/mKZVovKLBXczJ31SIxQSdcSy7nRf1c/KdUabSDrZ10
0h1OiebZLngdMaJ2OdSrq5q7S98so7LM/s5WTgYqdUOkv5qH1lhWi6fOycqw6KVWd/LBF0a0X30S
jtio8NRdT0mU12Xw5Z9JdWFJtEruOzLsqLOWuKMo98pph38F5qduBWb0sW87o8XCb3NyRNWOPA9F
mckT0XNnc5trHDceGGvz50ygQO1W4rhGuItHSOVcwlCQpwAIMn18fdzqHTzs4wNKV2U7lMZw3LVC
QyMhIY62gsc8i4lzs411y2xJFVN9PXMG4aWEWSYAiIXc84hGUaGIYmIAAAAAAABuMgUojQxpBIix
WSeaq0rGBSTBMRZKMiLgA0iXdw9XOyqsqzWrCgovRVTkcseyjchOEtIyU4RbLNlOtc7fSqdSajZS
lZXLCqyneRWR0jODLCINRYpCCMojTQ7ae0rr0M07+Tr1DzJ6PmMazu1DzUdzrMTk3uMzZb9Ziw7+
8x47lp5rq1683Nr0O6zzk97mrMo1+881L0HMYq9EHnn6Kw8yduuecXoazD7Na3LIp078XFe8Hljv
0esw+jp6cXNr3ZZYC31WLZ12GVftcxgQ9EtzzstzErqW7x8rx073FLlnoaemcbm1u7TzVupA4KfS
TPMJgCkEJwBoG0F1cAnKoOhUMlc7zhv5QtjORXKVBZOjsKrCEOqMC5VlXqqJdKkLXGs6DmkWqhll
lKOmull13L1Ytqoni1aGabkZ09GorITzbIkMWwros7ZctsWc7jRVfHSEq69TvqRjVlnM4tonzbzY
6zSwpZa6GDQAglCUQGg0M+Rr9GLI2J4iPQeasgbvJx8p6JYrO+eWj0EMMO/rxyNLv86zZtwVXVfk
2noOXLRs9PnQ6M++gmkCJoQIlFhb083VytcpVSwtlAjONhXZRXqX1wnqRhM0JVKOi3iuzbCDlnV0
RyhV0KiuyFip6ubQA1ENkCUQaBpocZRAAGmIABgmMQ0DQMQCkgk3FQFAwQ0AMQwTUiJJANCZOK5W
uUnGWQMzZ1uFQjI6ZgN1CYCECjbAi2CYi+zmeb1oXK1uZoV3Ecke01ONWm5XGSqLTE2iUXEAAtq0
znp0M07+Tr1DzR6PlMa3t1Dza2usxePe4zNlv1mTX37Gb5W/eLPNGvfWDZ6PKOOrZ7TzJpa0eWPR
uPN2eimebe01xrdnkjMv7OswTciY9mvyRxQ2eaM6r0NfWYJ6HjMt+hqMI32YleyzLjryPPL1FJ53
qo3Tn5e7S5XBhthiFnEdhVZi1zrNCqRqQVk65S8qmMo6gAEki+uyASdJcVsV3OE7ua0UYosnQF13
Hdm2zqnlZRKqrUKJutFl3MFndlqu2nlCyzllqTUI10rnZfOqzFUqbDo51WWQrluWz5gvdCLyhHRX
GQToC6fPMLedHbfRHjq6MAjzdXNuRkjcmoqLLeZx0wqJemEJRTGS6RABoZ8z0nFnRNTowJm/yZUj
bn5yRr8lVRQNA0waQ5JFircTSRJIJIdRUkKcZCTiTi5EAZZZW8WyE1m1wuq1IiNxqQRGEkIHEFMi
E0huucdNd9XPRbGUR5Ovm3IprcGmDIkotiiwcZRAAAABiAAAAABiaYAAJgJgmACGNAAAmDTHFoG4
gAXW0TxZkFBBx0iD1EwGmhxbEDEJgJiamXqBzthUFnPOGohvSLTAENCJIRKLQ0AW1SOvn7OE7+Tq
1TzJ6PmMW3t1Dza2+sxePe4zNfoajFj3a55k9Ijzhsd55593SYNm7MwqNXvPNP0XGZS9NSefPRSP
OHf2mXzaegeclr3mLVpap5d+k5DEl6Gw80vScxjG9wHDb23mJZ6PmMCWzyGe/TUmDLW6DCl07B5a
30WUZy2Og88/T5Bnv0GUcbEAAJg4yiAA3G4gOZB1MuKLyu6dArq6iyMAtlSiy7mtJdOeHRFVFhWF
5zyJzpRbKlHVHnC9Ug76GO3nZfGAS0soLJUInfQix0hc6AtKmdNUAaSLVFFxSi2zlRfUmWToC2uI
dNEQAYgAkgIyiAAaWbM2p4yN6eAivdw7jVv85aX7HnNE7K8eRuX+ZuNuGEzS7cKs3cHo5RAxAwAE
NAAMGAgU4hN1yCIgGhtMIyCJKJKUJjREEwkhDUoiRIiwBiEME0EgAQBKIOMogMEANDE0xAAwGhAx
DEAwENDEAxggAENDEME0A1IQAOINMAAZGQmgaYDcCREGwItwHKIKTQ4yiCGEkyJIEkwBiUgcJRBo
C6nQKqdTJO7l6tU8yej5jFu7dQ81Hc6zF497jM2W/WY0r9Y84eiyyHJ6bnMG7YoMd+iR567V0Dyi
9HwGX06Vx541+880blpjc/pMwzz0fOY0PQ8Bxw9FQYJtcxTy+loMGe9mHNX6LLOB+lpMA9DExFtT
PPWb8Dz63WYXV06R5k9HymPboWGNb6GkwI+hxjnYCaBxlEBoJRZdX38xTKtF4UE7uZk7lzFsYhOV
V5XZVA7eWAX1wC9U9hUUoulQFkYMurUTsqpC5UhbGKL64B0VwCx1ok65FqqC+NUi6pI7qKEXSoCx
0hdGAT6+IL4UhY60XRgHTVUE5VgJMcWDjKIABoZ/Qal+NWbdWSz0vLiwO7px5mvRl9RsVYkzXtwo
Hdr+ZtNW7AmbE8Gw9BzZaOVgA2RJBFTCKbIkkIlECQIbEpMiSQlJkHIItoipxAGRYwGgcQGmAgGm
A4jSmQbCIwcZRAAAAAGJgCBoAaGgAAaAYgGgYmDQDixgiSaEIG4sAAQwlBkmmEWgakAAkRG0DQEo
iGCG0EhITQSTAQAIJOANoHGcAAC6nuK6tTINDk6tU8y/RcxjWd2mecjt9Zice/xmZL0EDEr0Nc8w
/Rh52PoUefltdZ5+dOqZsfQ8xkvQyi+rfiY3PvIw4+nrPO9c0Q5fRIwujc88VHVsmDTvWnnD0GeU
LazjOjvWGAvQ8Rky9DxHBVvSMB7kzz12t0nmTv6zFNzoPNnpInnbNiRiQ9BYebWtmEUwlCURoYpR
ZbDt5iuVQXlDJXc6LLuXpK4xtFKgLLuUOg5w6K6wsnSBZWFhALKWFllAWSpiXOkJwAvOcOmqAF1L
JzqRNQZYoItt5gvqgFpCJO7nDT4qAudAO2pFyqZY6QuVMiyVATUQQSCMogAHfwdBq3efmbnNm1mn
3YLNu3z3QdzyYmxdiSOeIxNMQMBMTAEwBoGmCGIAEwaAEwBgCYJhGSBqURsZFSQgBMkIUiDGIaEx
iaABiABSiNNEoyiAAAxAAAAAADEAANNBJAJoYMBAIBgCaCYmIYREwACUJgmCHEGkMQScWNoCM6yQ
IBoknEbSBNDEDcWSSAaABhGSJQnAABygzqn30GZoZ/cctHpuQxVu8hm37dh5ns3OYwX39xhWbHKZ
l+xAx4+i5jEt3uA4ad6Zhve4DJfpEeeNXQPNPeZ59ejyjPfoOYyH6QPNm30GBXv2nmrNK8wjXtMR
ejmea6NpGAvRc5idVPoTzT9Czzl23M87HbuPPT9HkHJVq9RgPatPP3bnGcFG72HmF28I0BKEog0A
FpGylFigFsp3nJCAdEKryVdQWKAXwrmWJhKqVRYq7hWc6OiusL1UF0+VnQ6AtqiHRZyIudExkIlz
qZIrC7o4WWX87i22m7nSm6ogivpJz53VpXEurgy6uKLVWFllAXwqZ0wpCcABoHGUQGg0s2RsX4dh
v+asgbsMys9DXiVmx1+frPQ2ecvNUzeY3c3iRvTw4m2sYNSvigUIAAJOMiLbIiABgmAIGnIhIBJo
LI9eVatrxY1OHSStpR0ShbzvKujm6RSTqLlEEwbUSSAUoyEIJIYgkKLQAAAAAAAAAAAAwEAMAaaB
xmRUohKMiI0DUhNTIpxJCkIATiDamQBkoyZeSjx0ufs4txxtp3JODLLqL8V09HLEZVz6RwnAGMim
gBgJgIG0ADP/xAAyEAACAgECBQMEAQQDAQADAAABAgADEQQSEBMgIUEFFDEiIzBAMjM0NVAVJEIG
NkNg/9oACAEAAAEFAh8dOZmZmeGfxZ6MzP4szPRnrTMMEsMEzM9SntBH+c8RCeOeGZnq8f6Lx1Dp
HzD8Zjnv+BfmZjnt+h4/0ufwZifO4RzEhg6cwTznEyTO0zB0j8fj9scD+igwsP8AKHrExwEPBvmH
iPx+OjRtp0uWr0xtHpE0Os19mhvLVVPa9+mu0/D070ffNDo/da1NN6frCRg6TR6evSJX6dr0Sqx7
L9JfQF01zo+i1KNfprtPBodSWXRalnsret/+O1m2um22HR6kVU6e2816JR6Wuk1DD2Wp5t1NlDV6
LU2JXTZa40OqKemenDVVro9Q1t+mu0/CvRam1NNpbLtR6xpqNMnpNNd+t11a1ayut7Xu011S0023
M2lvC6pUXQ16HU2oVKk9HmeAJX8HHDx1Dgevx00//jn/AM//AH/p+qus9W0orq05vof06f8Azv8A
e+hEe/8AQa2HqGoIbUatTqPRNBoH1renfZ9N9Kss1Glpser/AOfOpu/4HVu13oPrOoupr9c1N1T+
p1u/q2nZf+T0H0+o+iai3UOrtT6BTbbb6FqrrKfRfUdTcvpmuAuXW311a2hq39b9P1V1nq3pjML/
AE7V7dNra2b03TKraj1nU6irXeofR6p687+99C/yPqYPv/S81+mel2Pfpqtyehq1reiahVb0/wBW
1Ooq1/qTXtqenPDMrjfOMxv48cfpLrrF0Wj1T6S2jV2Uaqj1C+i/U+pW31TRat9HbXe9V93rGptr
mj19+jmp9X1F9ek1dukfUep3XVe8s9mdZZ7JtZY2j1ess1Y1mts1Zt9Svt1H/L3cyv1K6u7RayzR
to9fbpFt9Uvspt1llumv1ll+n1GssvpX1jUBatfdXqqNXZRqaPULqNQvqlws1PqFl9UT1fUKrau1
9Tq9S+qt0mobS2/87qonqOoXU3a+6+n0sstWrvNeh1GsstoT1fUKL7nvtx0Z4ZginB3TxgmMMHEE
78PmYmJ46vH+oPEcF+BmeT9M8/h8L8sMQTOI3z36AekDp8f6wxR9IyYfk/HTmDqPaARo3wMwniJ3
4CHq8dCgsbqXpZF3M+l2JbWarONacxyMGe3biBkupR4KXLQLmJTuGIunYkzM7TsY22YE2TaYlZc8
KkNj9CdyyEORDCuEY9lQsqIXjVlUxwHRjsO/Ad4w5ZCmwppja5nL+01ZVeHzCnafPBENkwZsPDx0
6rJJBB1H9C61n1ClxeyZh/yAJtc2PdU5JUzRnbKzzZXbY1WsLPq3JKJdb7ilrFrt+2yZLavO9bWN
tTc5bmDVaUsunTBVWVra72NdnMprsPLTVEmd3TSLiUtab0L6iq5uZpbHb3ZG+wW6gjd9zeAx3GGy
2vTaxQKrHeuaB2VhfYlf01LqQDqXJK7s20PY9YQiuy1ufX91gy2MLGavVl3uo7KDVTGU0TWu+FsZ
dQDbXLG5QstJcnllPuTAtjXtyD/XxgnsMTx07jCSSSTN7ZFtgQW2KuSWa61puM59xm9oCRNzR7bL
I7M559xiu+0W3QWvlrjk2Njm2Y3NhrbHld7V18195tctVa6RGZJkxmzOY5QblJZiRmWPa0Flqu1t
hj2vZK7LC7ExmJVLbFPMsrIssBVmQ7mMFjrPJutiMRZdqN6PZY43sSS2OZY7ITt3tEfZPk821H3F
iWbcllgQFooMJMywZrGJ7leY2095mEzx+qv8YTn8e4zdMjpHwQDNkXsIZiN+QRIOLibZjiMzz3nz
MiGyZP7Kfxb4/MGM3xD3MHDOIDCwgMzmWHvM9eYIJ4WZ2zMMyRARGM+RnhuAm+ZMPT46K0ax7KSi
ou5n0uxLazVZxrQ2WEYM9u3Edy6lGlXct8fgesp0jo3ETfB9UtUqZ8n5O2MpMwZjgBkuux+J6EhG
S42u64bGTjEPeKpcEz5hQhOHn8NCu9lrDYQQdR/b3Ws+pUuL2TMP+QBNrmx7qnyUM0Z2ys82V2WN
VrWZtU9ze4rY2NpydgwsvYNTY1h16tm4sHHa83uGptsZtRrLHdA1lVWpYU1aPatOQdScrcRvspLX
VBrXquKZ3ObXduXv+vWEF6Awmi/uac2rY4auy0jVbTmnLR7Gs0mmsK08tve3NzNJa7e4r3uulXFY
us5QALowawWOatW5OqsYodV3m5lvDiJZc63FAdY5iMXq32WJ1eOhHZC11rwksSSRvbItsCLbYq7i
Sb7Wm4w33Gb2mSJuaPa9kdmc72yHeJbYobcVeyx5fqbLW3Nl7Hc2XWWR7bHG9s72KrbYgydqMyEu
8W2xYtzbrdRuWzUhqzZYU3vua6xoltnMbLMLLcVvse212jWO6Cxw3MZi7vMEhGtpm45a+1pVZ9y2
wvGssyMze2S9mdxw25juYwkmC6xVLFo19hHNdkYkzc21rLGB6vHWlZccEpZoRg9SrnjsPLgMWo2O
UOzgyFUldLWw6f6XUp+CpGsdlwyUM42/Uvxmf/rfOVaeMnGRBPHLgXvjbGJjd4c7Z2gXDTOJnPE8
M8cdB4eOjQ/3PubfaPmu1gvPAHN1bBkqscobDdXeUylh51tjW6OgrXpT9DudmobMBrU2uV0iO3sS
XOp0eQVdufvtfRvkqWtV6QpoZWgVwv02022MLaGfmUbQNV9oUsyMGa+k/XS9xazRO1c025XQ7TpA
UO6xBWBbSzZob+ME3TaIJnsTBMwDt2jPMk8AY0+TjEI4eDCIOB6vHQpKnJwt1qnmWGCxxHdnK2Oo
3GG2wpvfOThLHriW2IebYCbLGPNsCZJAdgDbZsR3rPNsM3swa60zmWhdzQuzRrTh7rbIbbGgvtA3
Ngks29s7iB7i4zcYGIAvuA3tFutADvs5g2M5aNBwUGKvZY0Aye8PaAzGZ8T4nhcw/A7TvG/lO8E8
CGDq8fsg4PzMbgQYAYeodaiZneDvLBiDMxF7Q9yBDmYxF+M95mYEIneKvAifMbKkcT3/AA+P2l7T
IncgR8GMMdR6sT4gMaFS0XGGhyAsLAQvD3mZunyM8PBPEdge0cHAhh4Dhno8dVaNY9lJrRBuZ9Ns
S6s1Wca0L2YwZyG4gZLqUbrrrLqyGsz5L8LKyh4hCy8D8QDgeDd5UrMVQu4Q7HgbHBKy/BE3uw2t
KgbGuQpLKzW2O6gk54OJ4PAwdXjh46KVd2s+rRkYOo/oXWs+pUuL2TMP9+DzXNjXVPkoZoztlf3Z
XZY1etLNqnQ+8yXQGtTpDi9Dus9xb7R8122fz1Pyrnnhd1d1jVV2uTaXuFn0VBn5envY2pprHXTK
XW/R7Rq0t/6+dsRjyw+FRwgxyUZuWFdt+kYjUnUWLpGKq2s2l6tsUmmV/dlLNYFK11apfv0j/q3P
W2sL/XY2ywvbXHxWs7xvg/HA8Bxxx2meOgEgtbY5JJJJI3tkW2BBbYq7jlrrWm4w33Gb2gJE3NHt
eyMxcm60jnWbObYEBKk3Ws247Rbap5rzdmM7ZrscKxJjb8860BbXQZOGutZUdkgtsCKxUrY9crvZ
E3sStjqEd0m51JJhsZW3HJdnnMdWLFiC2OY03NhrrGKWuh3HCW7UyQwtsUC+0Guwx33T442CDqzM
8EmZ4/G9RraAbiybeLoU/JngG75hXr7mfHH4heZjn6oOHjoAgnn54oYPmZmRMZcQifJ6FUmAYijv
gtPHRo1BtoLW1WNzaXtLWZSt03AL91PrdOa1jKx3V/eitbdU9pazUdq/yDghgjiEY4gZmBtm2eDF
yZtneH56BDwPxjh4gEPwkXgYIZ2E7zZmEYJ4CuFeBPYmeOil1Rr7zZGusY7jObZs3tuN9xi22JPc
XbudbkuxjXWMUbBsc2P+dWxPkHtNvcJ2yJjvmFhw+YOw7zJEIzx+OGYfj4IGZ8TM857wxO5+Bk57
gssVp/KfE7zOYyQDbAYewLLx8fr56R1A4hbt8DME7Qnv8Ssz5jT4ncwcMw/PD/zMz54+cwRPlpjE
xmCeQe+7ce4mIvwZ2jMOjx/ogvADMIxBCp4fMAwBGm6Hh48dB6yMSr5mZng38hBwzwMAzNv4rKWr
RF3M+l2JbWarONal7GGDPbtDwAyXBRulELxqyqQ9AqLEptUfB7xQeVvgaD4YTuIP4KIZt28TwHBo
tW6vb9Lo1Z8Z4/AUbjX8mY+lO5bGTlmKbWWZ7sJuAh7zx8ww9pmHp04Q26pc0EEHU/0LrWfUqXW9
kzD/AJAE2ubGurfJQzRnbK/uyuyxqtYWfVuSUDZtoax61T7d5TOgdkYXWJXsFprfm67L2MSx1OS6
VsVer6ppy9ga1rKdKXXTf1E1B2GnM07HZTu2lGItdq0tYmzO2KeZHayzQoz1aSw8tFwW1TK6b7Kq
r22U1dtM9rjU6zJhe5bMqDewemy1ufWxsbTMdi/QivsGCuuR9i96tVbYyxATq0YJXf8AzHBWhzwY
fSRPHTuaEkkkkb2yLbAi22KuSWa61puM59xm9oCRNxj22WR3Zzz7jEf7l2o3o1tjg2WFFYod7GJd
tSp+Xa91lk32FedZs5hVjYTDdYx3GLY6Sq77xJZ+daAltgC2WCBmVSSZkxnaK+DdqN6V2Oh3mB3B
Ls7JZYsycAnHNsEZ2cvqbGhJw1llk3tkM4lVtggZlAsauZ7pY6FTDYxPOdQttiTcds+YYrmDuTMZ
njp9qQLqjUeLLt47G2WVmqzq5bA8Nh5fETbiCHtw88PHD5h7RTD8QzEeDgOrx0Dgv8pjvFEPaZzw
HQfifEDbierRf1iQmnbaHO17Ki91SPdZTbZy42Zqmc6aoty1tOoS11xpfpRGc06aocuxubTfYbKd
Q7b1LpqUdkNhHI4gYnzCQs+Zjr88RCcTMaYx+YAmKuOBhnxLO/DE89Qm+eOip+W41FyhbHVkt+4+
pDtbqSy7iRVcFN9vNbm2AZOGtscI7I1modi1jsXtssj3WWRrHac2zZvbNlm4cB2nyS/HPDxBG6B8
9uDZJHaZmAY6iEHhn8AXM244Z4Z77p2lvb8Jg4eP2hDCeHjrPFfkmMYePcRofgp1+NvQYeAncSz8
J4+P2MT4g/Ov8vmYhijMZcDcREMLd+82wr0bTBMYmYpm+eTAJjEOY3xB+Lx0VobHsr2BF3M+l2Jb
WarONa8ywjBnt24gZLqUeWVmuKNxiCbDi1DXw2HlhCa+rPT5QM7BftFe2ZZ/GeQRFOY3wTAsIE2k
Ush2d8pXumZniajM942I/wAKmURS44bDy7UNVmenx0aXcLrBzNKQQdR/QutZ9QC4vZMw/wCQB5rm
xrqnyUM0Z2ys82V2WNVqyW1l7XczuH/lbS7ItljNTprHGmWxvcaQskd3XR6RnXSphkGyyxTffLm5
mldD7zJdAUU6Q4vA5jadntHPfkrg2V2ffFtqaa4DFlhOoRnGq0i51NGb1se+xbXuFqDdq6mxFfK/
+tQ1jaIvdXprSlIe0qFLi8FZe4ekqVZmZW0x2wXPL1+xY3KdmsrXQZBo+8uoZX062P8A8fdYz6gF
FPR46ASC1tjsSSSSRvbItsCLbYq5JLX2tNxhvuM3tASJuaPbZZGdnJtsKC2xWFrw2GbmiuyTe2Rd
Yq82yJY6TmOWax2Z7bWLX2tOdaV51uwW2BAxUtbY7NbY5ycB23b2Z97NGZpvbcupFSjObLHsLW2W
AtYaw9qqGYQM6ne25rGeLa4iuyDvOZYqlsx7bHjubHLuCGM7iJY4htsVha+Q7LHssdmsewhmA3tn
muE6PH46qWth0p4lCE5Z5JrIq4VadrI1KqqLvYjB6yhCZ/AYvyADwJ7D5fgqZnxBMxY7QNMiHGIP
ntCBNvBu4HabswEiN3X8I69EAb1N+olzczSuh95kugNakg4o+lkuqDbn5rFuRrLH2M6VaY7S9Ob0
ey+2ushLKtrWbu1DMK6sVikJZrN194P11EHnMW5OUrd+2jg/BX/KCGYhAM+CvBe0ZhiGDhvJg+e0
2xe87zE29u4gGZ8HH0wfi8dAOI1tjlrrWhutK863YLbAm4lTadka2x1NtjKzswLEze257HdjdYxQ
kKLHVjbYRzrNgtsVMx7bHLX2tGuseG6xl5tmy1+Y34UGZ2jHEEExid4CAGaEkwcD057ZBg+O0OYc
zbP4w5J/8mZ/F4/U8fp4ijHA/PxBHm6d+Bg4nqEBnzw+Y0Q9/OzMIP4vH6ax/wBHEAgAhMA6FzHm
BD+M8Qe+OBxFh+JjMwJtm3r8dCIbHspKKi7mfS7EtrNVvGtDZYRgz27cVGSVKM3BUJr41obH5Z5X
ViFZidoyFJ5srNT5g78EUuQYRlmUozQdKjJKEVgZWyo1saircaqWshqCzGZZWa3zGg+OkiYmOPjo
0GPcOBZpiCDqf6F1rPqQXF7JmH/IAm1zY11TklTNG22VnmyuyxqtUzHVs2dV9L2aZ7bERPt3tdzA
UU+nsV1nPtTSHara3BspBBTG3NrVMp92thF6Nz0vYNTbYzajVWsV32V1ax3rhTmvqGBrssZtTomZ
W3WLXb9vWnN995VlJf3WizmnNqVM9lZJtmead9lel1A+xecNczNcCinTt9DKyyj6WTbbYp5i0uxg
+ivVn/sK2IHEyOoGAdzieOgdo1tjkkkliRvbItsCLbYq5JLXWtNxnPuM3tASJuaPa9kLs5DNlndi
bLHDPYwNthUWWbB2LMzBbGDMSxFtuN/dr9ycyzDO2d3ZrXsG9872Kra6qLrVZGbdn6AzZVmUrZYs
ec1yxZsG2zZTbyo1juXssePbY8a61ottiwu0LsYbHwLbAi22qpLbTadiHE5lhnMsQJayQjtxzibp
unzPiEw/GZ46UrLh12siFxACxZSrcShCdIMOIIYYBibpuneD4zgboXm4/gSNPPjdGPfgeGeGPxfE
J7hocz/zMTPVmbpuWeOjRqDZp2stq3utXMaut8ylnLGy0U3NyhzW9wmPb2n/AKn4N03TcZmbjM/h
8cVE+Z8RuDHPWOnHS2Z8TuYvwT2z1Y6fHQpKk3WsUtsQbjgWOH5r71utWZON7ZssBW1+Y36w6Fnw
eLcR+btwyJ5Yfk8f6bPFI3wIfkCHoHA8R1iGAdu07COe34/H+iHWDiFpuhaBv0i839t8LQnt+Px0
Iu5rKClaLuZ9LsS2s1Wca05lhGDPbtxHcupR+lELxqyqRULKiF/wZ4WVGroC5U9A6q6y/AjA6QMl
l2NbWarJWhsf8njoAydX/WIIOp/oXWs+pUut7JmH/IAm1zY11T5KmaM7ZWedK7LGq1hZ9W+SgbNt
L2PWifbvKZ0Durc+xE70yxmrbQbgdP8AeX7d0d9RajklEQnW6djsrxVXWtZ13MtdfUHZr1LreyZl
zmuqnHts2e4V29xvsqqvPKrckqlje4DW11oRXTql+/pyU0/3Cas508Oot9prf7p7m9xWTa1CkUNY
zDWMzaqxrG1wNan09iusNzjRuh94DWp0QB1GnZrZqLC9nV46AcTcdxJJLEze2RbYEW2xVySWutab
jOfcZvaAkTc2Hsssjuzk33GJZh7tRvRrrXhtsKKxQlmMF1onNs3K7LGtdi9j2FrbHBvuMF1oC3WI
qW2II1tjhiSRbYEWyxVLMZk49yAm9sra6DJwb7TN7ZS2xBW71wWMFR3Ql3JF1oG9pk4JLHcxgdhH
tsePbZZGdnLXWlebYEBILO7TnWkC2wJ8FrbGPX46K0NljDDBCa+Ow8u2h6krQ2OFy/Vsbl8K0Nj/
ALefxY/S8dHpzFdZS9gq1AwbjzVvKZIImxec4S6hLLV1Gn7V1b11IscMzFK7m5QyViuV1FLPsrVj
S153qWe5u56D+mZ46/H4T+Tx0KSpW2xFNjtGutZTbYULM0ttNk3HButYZODqgE3tlLbK5k4N9xG9
s8x8G6xjuOBaQn+mP6Pj/ajhn9jx/wDx/jorRrHspKKihmfS7EtrNVnGtDZYRgz27cQMl1KNbWar
OC0OW4CsmvjZWazxWotX0VVGziBkupRpZWayVwOHIfMAJLKUdhtbp2HluNrRBubjyHzxFZNcZcdf
jo0IzqbsWaQgg6n+hdaz6lS63smYf8gCbXNjXVPkoZoztlZ50rssarWszapyUut76jVfSVtc3VN7
hL3DU6VnXTd3p042rzrfbWfTNwD6ljZp99lVWpbZRpS66ZWPKa25Uv8AsK7tWmjlBLxLXemx3B1f
dVtb3Gnnubfaaz6dY9r89C9sdyatYzNqnfl3apcakNZ7xEJ1lRWulLBWLjYmmuyjAkLWxsi2tXXZ
upTXZXVPa/Pq+9NS4fT1s9WkcPy3yVB2kX2S1MP0eOgHBe2xySSSxM3tkW2BFtsVcklrrWm4zn3G
b2gJE3NHtssjuzkXWq1V2LGJZuY4GTh7bHCWPXObZvNthKWPXBbYG3tnJwltiDJxVcaqzY7FLbEC
WPWdxisVJtsLZOOdbvZix3tnewmTgksTY5CuwjW2NGdnItsVixZqdS6EXWhUssQJbZXA7wWuHNjk
h2E3GU3BJdZzLOY5m44ex7JXY9c3NOfcZvabmm5iOjx0fM9qQLqjUeDVlU41VczpqrNrHserkNt/
2njo0X9YkJp7+0qXlQ22ii0hY7BX1TF6VNtYvs2UafdXpCxWs2X5tPKFljUjSHYqvEVLKkf7Vjio
WO7VL9sfx1H+mPSPw+Oip+W41FwC22K29zEtsQLbarbmhJMFtirk4GoZa97GC2xVS2yubjjJwLbA
m47Utsrm44N1jLz7SDaeX+Yfpj9Px/sDB+94/eH5x0D97x0Vo1j2UlFQbmfS7EtrNVnGtDZYRgz2
7cQMl1KP1qheNS6yxDWSMLUnNssQpHrKIi73aoqnQ9DpDSwErQ2PVQbRwZCqcRWTKkNjnp8NWVTg
67WEqrNr9aoWVl29Xjo0ZIus2DREEHU/0LrWfUguL2TMP+QBNrmx7qnyUM0Z2ys86V22NVrCz6t8
lMl0yXRFJ1tVjIGc2VXlMqzLKLrTQtje4q+kalmNZJM3tZZQz2hFVoHtdSoI5mxtYCL677ebZc6z
uXVj7g2WZ0ZAvVABz7FT6KUduWNYdxR2SzQsfdIX1FVrczTahjamnc16XOZeS+mpAIoPPXdc9N2a
2Xm8z5t0QzfWbLzussS2xm1C2N7iorXSzGqoPcq/BoJeO73aQ5B4eOgHBax3JJYliRvbItsCLbYq
kks11rTcYb7jN7QEibjHsssjuzk33Gc6zZzrNgutC7mm5sGywpEdkm9twdpZY9hm5obbHJLYa2xx
zHiWWISSxjWO0FtinmWGOSxm9zNzRbbFO5oSTN7hgWBDMA11rRrrGXccb3y7tYdzQ2uzWakGsW2B
xbYHNtsGRHseyNbY43tne25bbEFdj1xXdTvbLW2FgzCEknh46W0ti1csirrNR4VobH/33jo0X9ZX
Fa8rlvSXvRrmt0+kblp/Tj4DIzmnT14rWyw6Y55wcjVnufzn9EcDB+146Kn5bkkzmPuNtjNk7Uts
riW2IVsdXs1DsTbYTvYK11jwWkD9rH+k8f7Afv8Aj/bnpH6fjoUFjZRZW9mnZFAyfafRbWaz0W1m
qyLp2bosQ1tGQqijcx7GIheNWVSBGZUrLj8eeLLjiR26aqzY/HkNnjVWbWPY8FXMZCg6GQoHrKr+
MH/torJUylS39gtre43WVVatAK9aMavUMbUutZ9TTnNE0P8Ac1N7isWWuvqDM2oLWrZUCRnmA2NV
p7XJu0DsrC+xK+9MsZqzoN2dP95c13R31FqOSVRSdbp2OyvbVWFDay5uZpdKWXTKx5SPhGsNVFrk
2htjgfXqyrpUdo1f11Gy2vS6nNCtuRO700AhdLuSM/K0v1Vs9r8+r70DK7JZlRZi3fbXXewpruKA
6b+Otsd0qsZBZYXpZT7zJdNZY7JzLa9LZspGrx7jj46SSY9tjhmLHcdu9spbYgS2yuEli11rLvbI
vuA3vASp3Ha9tjhnZoLbAgdxDdaZuJG9sqzIS7GC61ZzbMqzJGssdnseyPbY459xgutCrdYirZYg
+I11rSu41Vmx2K2WINxxvbIscMbbC7uzne0sseye4da0tsQ13siB7d+bDA1gVy5lrmxjY+NxjW2M
y2Mjb2yttlYydptsKAkQuxXc03NOdaV51uwuxVbrECWOhJz0eOitDY/RVS1sOlPRZWaz0gZNtfKd
aya7UNVnBULJ+kJ26VXM+IJ8cDmfyhGP1fHR6exXV85xo3Q+8BrUkHFH0tWwNS/bC2FdSvNrlpV5
an3xi5K3ssp3PzVsK6nQHbqaTYQwVraS0vYpEVr5vDr0D9NRmHhnEMzA26LnLDtg/lEPV46ASCzu
051pUW2BCxI57gPbZZOfcRvbK3WIu5scx963sWv1HMRrbHXe2QSIt1irzLCVutVRdaItgSprPt/l
8dR4YgwB2jHHSrQmN3Xjj9Dx/ovP5cSv+MIM+ZiZmeC9p8zEf54ePz//xAAdEQACAgMBAQEAAAAA
AAAAAAABEUBQABAgMGCQ/9oACAECEQE/AZJqDyKgaNQYq0qxYoCjPHCch+roV0aYaMZQj92pIpXC
fwI2qUVjpBwuVwZY8HyaV8KS4aozt46Q/lAdjD5f/8QAIxEAAgIBBQEAAwEBAAAAAAAAAAECERAS
IDAxQCFBUFFxkP/aAAgBAREBPwH0P6yK+7ZEe/0En8ER2y/QtXhbZ9CIv3tmoW19Yj5LNRZqLLXO
t98l4oorFlmo1LDdIuxb2J5bo1ljYuT879JoY1RY7Yoke98l9KNTSLGaWaBJLla+8WhFDxe2z847
FErw3XFJjs/GLaFMci286rIeRPheIjQxYoSRIRHyNCdGre3jVSG7H/BRZpGIcsR8rwt2nD7NO2ih
/BPytWUfUJ3sbx9I9b5YoUqE7y2PxVpYmaiz6Xwy6O8NUf4KX9JS/gmxLxPKRLril0LLQ8RrxXhR
HESof3FcDKEiyhR/o4iFK/A2UJbJWsLgfQnhIrLidc7Yo7piVlClubG2xRxHra1fNYlvmIsao6FL
FjkUKOLI9eJ/RcDR0V9w4lViissSF4WLhk8fkboci/6JPCFLP0j14GLin3ixmmxKsUOOLLER9Vjw
uyt7jj8FmsteSy8NGkooXfDWNJTwizVxssT2UzTsfYxLjjiijSVy0VwPvC4UMh62vpTFw0yhKv8A
hRY5MUmX+kk6EJFDuxff0f5IZkR4v//EAEYQAAEDAwEFBAcFBAgGAwEAAAEAAhEDEiExBBMiQVEQ
MmFxICMwQEKBsTNSkaHBUHKS8BRDU2BidKLRBXBzguHxJDRj0v/aAAgBAAAGPwL9pT7KP7hx/d/T
+4WnYf2HO0sL6caBHa/6M6wcpz9UG0qDhTsMhx5/iqjqdB+7DjCspsLndAvW03N8+wVNpiwjDQUa
Uwxsk+SqUdna5lVow6dVBX9L2yS091oT20m7iqNJW7Ywud0CmrSc0IPbScWkxICax1F9ztMaob2m
WzpKDdy+SJTqYouuGuFY9ha7oVd/R3wnWMLrdfBbw0XhnWFFJhfHRbQ+rSisx3P5JhbRcb9Mardb
l9/RW1WFp8Ve2i8t8lZTYXO6K8UH2+SqPqB4EcBHNGkKLrxqOi9bTc3svZQeW9VurTM8Xgmtp0HD
P2hOqbTqtubBwqrGCGtdhW02lzugQ3tNzQiKLC+Oic51JwDdcaKkRszmO/tDo5XsouLVDsHofaT7
tU8/1X/YVVY6oSzi4ei259xZ61wLmjICr0t7Xr8w5zTg+fY//pn6hVxzIP1TpHcaZVRzdC4wtndT
zZFwH4J1pta3mVtlSkZqAxPgtrZXc59O3V2UXMNrrtR5oVN47eTF3PVUXvNzrtT81sopVCyRJhUN
28txJhbNuoFS3Uq1+11KtbILQIbov+IQq7K1QvEc019Ew5zuIjzVc1SXQYBPTC2XduLSYEhbK5tR
wc+JI10X/DDVzeRd+SF21VmFsRTaMIvY1zZp5ubGVVY6oSzi4eQX/EGAm1pNo6ZKrDaG1ix5zWby
+avo7VvtnadHDI+apNd3S8Aprab3MaALQFsjmm174ujzRbcbYGJTfIqvj4ltVWn9rotqZWeX07dX
ZV1AkOJ4iNVVNUk5wT0wv+Htd3TUaCmMpOc0AC1o0Ku2im2nULdB7PPu52UNZYefNbymGkxHEjtD
Q28zroqlVlvrDLmnRbq1lOnzDBr2GpTDSSI4lvmGHzKLIpsu1LRnsO7ItPwnRGnDWA62oupEZ1B0
KNINp02HUMGq/okNsmZ5obJDbAZnmm7LDd20zPNU94GiwQITDUDRaIEKnX4WvZpAW8bRoNdzNuqr
VQ2nNXvYTnUw03COJFjbXMPwuT6JbTsd0Gip7OQ2ynpGqpUHBttPSFSpODQKWBCFzKT3DRzhlO2n
DqjvvI7Q0NuM66KpWZbNTJB0VR1lO2pqyOFbmxlOl91gjsaHMpVC3RzhlDaHm54IK3jw0HwQqsAL
h1Xco/gf90+u22X95sYK3Yaykw6hg1TxS2oMqf2b9Cn0q1ZtSvUPw8kzZyG2Uzg80Lm06hbo5wyj
UqGXH+5mfajs19PT9s+HuQ90gCT4INeIJEqC4N8Sg416WRI1z+SdTdq3HoNYNXGER07DkYZf8u2E
WnUGOxjYy8SO10fCJ7A37wuCjswtOzn2kSBAJz22t6H0Y6qw6gx2scfi0RATncm6o28hKY46P09j
qpVrtUA3JRYwj97l2CpyJhMM97PoAyM/l6BjkJ9lR5ndhQcFbN+4fqtqpHuBrsKhRYPUuDcRg9Vs
tgkSR/qRhl3re71yqbw8uDaze+3LVtDXZtItHTK2im4k2N7obDW+Sd/lh+iru5in+oVB7+J8PieZ
Gi3lQ8TagDXfVVJ+9AW0U3EmxvdDYa3yWycRgtV5eQXv+BsuK2h1MQ+8acgnmuI9VmNShH2ccEdF
s8mfVk5+aZvs+tAyqgO8cWnEsAtW0OZrw56aoVXzvbDkDOuqouhzja/LhF2EC4vYXO77W6+BTrID
94Q4tVVwhr+CfAwmO5uZk9VussO77hHCcaqq5uagbwqk+q0d18HrjmmXQ54qgC5VSXOfa4QS2I8l
XghrKU/DMKg8gudY4i8d48lTe/k+A7mtqe5zg8PiWjIGVUcGm7czxDx1W8fPFzWz7uczoNcohjf6
3l5BbW1piGt/RVLT/Vn6LZbTrM+PEnlrnt9a4cDZTg1tvgVtFNxLrG6BsNb5KnTgfZBwEautTHVf
7duStqJHT6ram4taCQI0K2d9XLrXcteioEl7zvhxOaB8lWk93LfDK5nhH0VZ3RuPmmMdULXghzoa
q7mDjFS2egVBtTv2y75plH4GM4vHElUG0B3xJMalRQgbyqbT4LaxjdgaRzlVDA9XSDfmf5KpOq8T
gxztJ8lRu3juObntAwqj8ZeLcd1FztW0eL+H/wArPZrHpg3HGikmSUATpoibjJ1MqwVHBvSVa17g
08gVM56oXVXmNJKOTnVZqv8AxXeOka8kYOuqGTjTwXG9zo6lS9xcfFZqv/iQ4nQ3TOiPrH51zqrr
3T1lEyTOudVE4HJRe6BplRJjohc9zo6lPa2QXEGQdFeXOu6zlXF7rusrhqObPQwpa9zZ6FEScqJl
W7x9vSVwyHeCuL3F3WUBJxn5o+te7rJV4e4O6ysvceeq43ud5lX7x93WUTJzrnVBvIKG1HgeDkbH
ubPQ6ouD3A6TKlriD1CEuOES17gTqQdez7V/TvJrny+PFWC/WSXukqHVHHzKJuMnXOqGTjTwQc57
iRoSUcld92nVOj4hCl2UXCo8E6mVLiT5om4ydTOqtD3Bp5ApvEeHTwRknOqOTxa+KGTjTOiuL3T1
lRJ8kWmZPecefZKwf2LlYPafYa+469mFn2Gn7K17J9DT3OF+vsMFY9oGN1KDrmuacS0qLg3xKDjX
pZEjXP5JzHRLfQawauMIjsORhl/y7YTmnUY7IkDzR9i2fiEj2WUI5otOo9DVT6ACcwxLTHp5UqEW
nlhRIMcx2a9jgIFguKx2Nfydp7W1hgnn4IUaQJbMyfiKgiCtm/cP1W1Uj3A12FQosHqXBuIweq2W
wSJI/wBSPBd6zu9cqm8PLg2s3D2wWraGu0aRaOmVtFNxJsb3Q2Gt8k7/ACw/RV3cxT/UKg9/E+Hx
PMjRbyoeJtQBrvqqt33itqbi1oJAjQ9Vs73ZcWvk/iqNOSwu8Ja/zWy0jFrsO8eJVQ7eOLTiWAWp
9Fw9TzEYiNVSpnu7oOiNTaqRh9VwqYvaBPgmFzy5gqgEPbBCqg7xxacSwC1bVSPctdhULjIslUNz
8WuO8ZTxSgTVcJ+QVV8ua4EZaJICbg2uZ6y4RjqnOaQ2kynwmJx181QcZc6xxF4y48k3+kab5okr
ad6MCOXdyq1P1ha1phtggdCqTG2gCmHGR/hVGpc8u3kXOELaXuc8Oa+JAkgJtodJbmREoUnExu+6
1vDom4BOcfJf/IyA9oE/RVA7eGOrQLVWwbGz3NW+KNYEPfu5Ybc6qlUqiX8evMWq9xlzamD8kJL2
XP74Ez5rdwy6/wCSqkuc+HDJbAHktptAmmDYI/ErZzUHEd588KkSNdoaq5wLXC3Hd8lvDN+6BkDn
1VM8RMOy8a4TXl3E2oIKqXThxW1FuDe39Ux3xOZkqjSYJpOAxGD1Wy0/geTceouW0ir3Q3p3cqtT
4ywAw2wQOhVOmIDbGk/gtkZUPAXkH8ltArDDRjHdM+0lji09QULqr3R1ciSZJQBJxoibjJ1MqwPc
G9JVrXuA6AqZz1QuqPMaZRyc6rNV/wDEu8dI15IwYnVDJxouN7nR1Kl7i4+KJuMnXOqEOONMqxtR
wHQFCZgKHvc6OpT+JwYT3ZwgZMjRS57nR1K46jnR1Khz3OA6lE3GTqZQaXG0aCUQx7mg9CrZMdFL
HFp8CncR4tc6oWvcI0gobwueAZguQbD3CZN7plOa2/i+++YHgrDUdb0nCDg4yNDK4qjjPUq7evu6
3KZJ80Gh7xGnForolcTi6OpQl7nR1KuuN3WVcXOu6zlXF7i7rKtExrC4XubPQqeaN1R5nqVc65x6
h0FMi4W5kukypNRxPi5RJg6oQTjQgq4udPWVClxLj4rJdnWStVYHut6ShnRQajyPNWl7rekrUlWS
63ogH1HOA5E+3dEcIu7af/6G0KPTOQIHPt3nwzHaGt1KL+QMdrHYh+nZw+XzTi2ox9uoCbPxCR7A
NGpUBwd4hMIjjfYER07b/GOzKwtPTwh70McnfQoPu474u5wtoqA2CQJa2T8lUL7gDQBOM8k93wCn
NK0Tj/dU3cZdnicIlbEJNu8/ULaBUPC0iPDKrU/WFrWmG2CB0KpU8WGkJbGvCg55lwqRPyQeHPaS
+CWtlV6jZpNkDu8Uovtf9kJcBxN8U95cHB1HBiDrzVOn6wsLBwhgg4VBjYFzTPjkotu4d4B8lVou
HqADiMARgp7wQLW6xMeS2V0u4hkuGTlOBccvC2im4k2N7obDW+SZSotBplgwRh2FRj7a11k6aqSD
nmVs7aR4mtNXzP8AIVSqKe7e2O7oVXc7i3TbWg9cKmH1HSRe4NbqPErZ65GnCB4z/shR5zc7zWyU
m4nid+P+ye3EOqNawdFVbc5ww0C2GgzyW1NxumtIj8gqrwYtYVTa57s8bg1mo1yVRP3Kbqv8/kqT
LjpcQ1vLxVIUG94T5olwAax8ujp/IVR5+OoP19HGe3K0UHtHvMgkK2cdEXNqPBOplZe7SNUIe4W6
Z0UucXHxUB7gJnVHJzqrC91vSVNxkY1UTjouB7m+RRLXuaTrBQIqOkaGUS57iTrlWB7rek4QE6aI
gOIB1EqzeOt+7OFLHFp8Fmo4wZ1R43S7XOq+0fp95bu91vScIcR4dPBcTifMqnGCzEhcdRzvMrie
4+ZQAqvAGglDiOMhSTJKm4yMarXxWar/AOJHJzqiJ11QAqvgaZXedpGvJAb14A0yoD3AdJW7YCJy
SeaDYhrRHoYUn25/ZEhePZp7tHblc1qpC8FntH7N8eyF4+5RC8Vr6OOzHoaehhA+5BrdUHXNc04l
qguDfEoONelkSNc/knUzq3HoNYNXGER07DkYZf8ALtjqi06gx7BxHwiUAYyJ9ETzaHeg5w0br7Ix
yEpobqt71MLPa8iOESewMGpMIjp2WhMEjIlWk8pUowNBKx2T7nazvQU21lkPiPvKCIWzfun6raqR
7ga7Co0mD1Lg3EYd1WyhgkSR/qRht3rO71yqTw8uDazcPbkLaGuzaRaOmVtFNxJsb3Q2Gt8k7/LD
9FXdzFP9QqD3w58PiecaLeVDxNqANd9VVu+8VtRjFjlugSw7vuOHCcaqnT9YWFg4QwQcIG26J81S
q37wcY4m50TX3cd8Xc4W0VAbBIEtbJ+SqayaIOfkmf8ATb9FSp/CWNkdcLZbRP8A7TzTMHfOytqp
Y3YaSGwtmY0cDmNxHeVMU3PhxPdZN2Ud2Ims4Z6YVYSRbk03t7vkVtAaeQ+qoUWD1Lg3EYd1XUQ7
54K3pe4PLoJYwFbU6k0tIt5aLeOA3hpHUf4hBVI3VJfra0G4yiG3023mHAT8incTmu3hBNNq2hzB
blvLRSDl1GT4lMzklBwcQ41DnnoFXfJa7hy1sxITTDu7mREptY/1rRTPn/IT2DWnR/OQqD38T4fE
840TXVckVW2kovDntcahBLWynljCANcaKoR3nuDFutwHZDJuPkqtUOLQ59gtbJT++2YbvAMzC2kz
BkN4Uyv1YGt89J91kGCgXPc4jSSpJk9UAScaIm4ydTKsFR1vSVa17g3oCpnKF1V5jTKOTnVfav8A
4l3jpGvJYJEocRxp4Lje53mVLnFx8Srd4+OkqzePs6SrA91nScKQSCrnVHE+aicIubUeCdTKy92k
arWUOIyOcotD3gdAVBJ1lE3OzrnVW7x8dJUNqOaD0KieHorXVHFvQlcLi3yKsFRwb0nCwYXA5zZ6
FPa2bnEG6VLnvLjqiGvcB4GFwvc3yMLhe5vkVqcoQ5wIGDOimTPVcTnHnkq8PcHdZUuMnxUXGNYR
Nxk651Q4jjRAmo8kaSdES17hPQo8R4tc6os6kEHorpz1RDHuaDrBU72oCfFHLoPeg6oACGtEALw9
rlcvavaXNlhjz7IGpT5IlpiO1v8AiE+2z2ePsZ93z2ZRWPTjsn0iYutaSB1KZvxN9SBjUIiajpcA
2WABpW1NxumtIj8gt0N4WNbloYIONVs9FsAlpc6RyTLnOeDVEXNiBzhMs+0qVS9W3SykLi5zZlbO
657jxOlwgwqIq5NWoSfGFVFQcOA0Ro6eS2puN01pEfkFs7eYZ+vt8+yxr7vhZX07c+hleHsZcCfI
wQmxdDepkoF1RxI0JOiOTnVWbx1nScIOuMjQys1X/wASFr3CNIKBNapI0NyB3j5GmVlxMIF1RxI0
k6LMlp1E6oudqfctFhSfRlT6Me4YUqR2YUnsg5WOzw7NP2XHusdo7Y7Mfs7Po3e94PsceyY53x6K
Lg3xKDjXpZEjXP5J1N2rfQawauMIjsORhl/y7YCLTqDHpG3kJTHff09KGkO4bsIGQZ/LslPeI4Tn
0MejMg+XsHVJAAx5omRhWnX0okDxPb4qNB1K/wBlHVFrtQYKwFHbPsxvCA3xVI7xr3EnScqCIK2b
9w/VbVSPcDXYVCiwepcG4jB6rZQwSJI/1Iwy71vd65VN4eXBtZuHty1bQ12bSLR0ytopuJNje6Gw
1vknf5Yfoq7ulP8AUKg9/G+HxPMjRbyoeJtQBrvqqk/eIW0U3EmxvdDYa3yVKnA+yDojvOtwmOq/
27MkLarhAkD81Wp+sLQDDbBA6FVbT/Vn6LZYMTM+PEn0tN1VJ/7eaY/rUH1W0U6w9W0Hl3eiq0XD
1ABxGAIwVugSw7vuFvCcaqGGPUfotnnLrXkA8zlNdWyRVbaStoDtGxb4ZW0OZqLflqmNf36zCP8A
+U2l9xufNCkSfs+61vDoqNPLC7TEtf5qlSywnGktetlAz/7TrDB3zsraGfAG92E4iJFAfoqTncT4
fE8yNE51TXeAA/ig6l3i8hxVZzYbU9XPgYW9d39zdIEnXVU3cRdnicIlbPufi1x3jKrMYeAVYj8V
WI1Bb+qe515ApjLdW6ZTHXXXNwYg/NbNTa3gcxuI7y2ekI3bnEHxFxVUHeOLTiWAWram4taCQI5r
Znvy4tfJ/FUafEwnThlr/NUoL86hrQbjKIbfTaXmHAT8imtxipmPNfFTl54miZ8CoxcHfCtpd8Qe
ACeWqoY1Y0n8FRgv4tbWg3GU4tBsujt8+yPYjJxp4KSZJQBJxoibjJ1MqwVHBvSVa2o4N6AqZz1Q
uqvMaZ0Ryc6rNV/8S7x0jXkjB1QycaLje50dSpe4uPivtX/imudL48VYL9ZJe6SuKo93mVYXuLek
qWuIPUIS440yqmpqPwXTyTHxNplQXut5CVYXus+7KsvfZ0nCm53gZWpMaIFz3EjTOiOTnVS1zm+R
W8qXVCMjKl2pQAqvgacWitbUeAfFWh7gOgKtDnBvQFZJPzXeOfFd4/jyUnia3QSrBecyS90lcD3N
noUcnOqBuMjTOil7i49SjY9zQehVsmNVE4QO8fw6ZVznFx8SgGuc0WhpE6oCcDRQ57nAdSibjLtc
6oQ440zorRUcG9AVDXOE9CuF7m+RV055Lhe4TrB7Dc9x8yg0VHQOVyIa9wB6FW3G3p7Yl1Wm2DGZ
1QkgyJBHP0BkHHLtv5TCcw6t6em0OIbcJz238pj9uXfcaXfgFRa6jvCZfqU55ltlNtrQJslUyQ57
wxzuNve6Jgr5vqADxCrXjBhrcaEnktpqNjLwxvyRqRdVZRb+J5qjvO+6TPOOS2SlPA43Hyn/AMKr
vDwue0Dwkqu31ljRFtgAb0VWoBL2DHh4pjqmXw9/jphUm1B9pUnzACI9Y+XANlgABTi3uggWOHcP
gtouMimyweeEyi0RRAF2MEcytlpU8XZPzKrOGj6vD+foStFHtMej190HuM64IUCtUA6XK5rnB3WU
X1LnHrdkJktc5jersn5oNaX4My50lRJjVEvvLvvNdBCnkBAzKAvdA0Eq2cdFDnuIHIlSxxaeoTCC
4Oa2JnKlz3H5rje50dShfUc6OpXE9xnqVZe63pOEHXGRplNAw1ug9HHt4Wvbj3DXtH7dn2Q9GO3R
D9rD0Cp9nop7MrCntx7mGDUr7Rjv3SouDfEoONelkSNc/knMOrenoNYNXGER2HIwy/5dsdUWnUGO
wTzAcokDz7XOGjdUJ5gHs3nwzCc8RDY9qGMHEVvOUwibgsduFlYWnbhbzGsJjvvdjjhoaJk+i8gh
zWcwsdspzo7uqcR8Intv5TCdTOo9mCxtxAOPkhU3bWvvtFoiVBwVs37h+q2qke5a7CoUWD1Lg3EY
PVbLYJEkf6kYZd63u9cqk8PLg2s3vty1bQ12bSLR0ytopuJNje6Gw1vknf5Yfoq7uYp/qFQe/iqQ
+J5kaLeVDxNqANd9VUvPxQq9ING6aDjkB1QeCBbQbmJjyWzuNxJY7Lhk6rY2t0d3vHiW0A6MItHR
bRaToPqqFL4HU2yOuFs7biL82tb3s81VYDwirEeGVtDmai35aptWp9tuyZAzrqqToc59roL297oq
d4a71kAu+nkqpLnPtcMlsAeS2oxixy3QJYd33HN4TjVU6frCwsHAGCDhA2F0TpqqdS7ed625uZjR
MdWyRVaGkqufuuFuO75LeOm/ch0gSZ6rZy28k4LnCJCBu4zUOfkFXxqWFbQw9yDhUKbB6swYjHms
iTBIHih/Sc+saAT9FUFUcDSJn4fJVqbWjdNGnIDqqED4Gn8lsjRGTnx4lVfc4FpAFre6E57Qd4KU
5H5x5KmXzN5z1Wz2SJnIHinFpczjg2Nn5LarJaIGPHCoUmD1Lg3EYd1Wy0sbtx4j1Fyqg7xxacSw
C1Q4ELaw0kf+1WOJs/ULZzdl3ePXK4W/1pVXvM7ovZqMLaeIZa13CI6KsWiTuymPrZfJtMZOEDNR
zru85oHyTgDi+FtVM9wNdhU6frCwsHCGCDj2UgwUC57iRoSUSTJKAJ00RNxk6mVYHus6SrW1HBp5
AqZz1QuqvMaSUcnOqzVf/Eu8dI15IwYnVDJxp4Lje50dSpc4uPirC91vSVcHuB0mVmo78UM6aeCP
Ec6rhcW+SDrjI0MqwVHBvSU7jdxd7Oq4Hub5FX3uv6zlXOc4u6ygXPcSNJKN1R5nGSrd4+OkqzeO
s6SrL3W9JwpBg+Cl73EjqUC6o4kaSdFEnOqBuMjQzori8l3UlcTifnKOXH5om4ydc6psNfI5X8M9
YUrje50dSgHPc6OpVjqjrfuyg3ePDRyuQycaeCuDnA9Qrrjd1nK4nk+ZlQ2o4eTlLXOB8CjxHi18
VYHuDOk4QzpogHPc4DqVc7VXXuBPOVg6ocRxpnREh7hPQ6oua9wPWUXXuk6mVwuI8lc97iRzJXG9
zvMogOIB1E6ouuMnUyrL3W9J9xx1A+acG1Kb3N1APa1x0dot5iLrU2oYgmB2sggXzE+CnfU3eAlN
YNXGAiPYNfyd7jnsz2x26duVp6Xip9x0kwSB4wqd7Wu9ZAc76eSqkuc+1wglsR5LazGLHLdAlh3f
cc3hONVTp+sLCwcIYIOFMGDotm+61pqn+fkvV0y1z8XOdMKvTc22gwEWxgdE5g4TTZxU3DHmFRpk
4DAVQY+kHky/WFSApjgpF4ZrlM/pGZqC39f0Tg5gtLoGND4KodW0adnz/mVc2m2mKYuOrlSqEucQ
Hvlwg+CbSHA+0ugjheFQY01JcLiGsBuQbHAXaKwtFrnBokd0+CqtuJbhgFsNBnktrrWw1oLR9E9g
4TTZxU3DHmFuvWFjW8TQwQcaqkOrnH6ezx2z6UD0YPZhZ9Lkso+4yEC6o4kaSVxVHmepVu8fHSVZ
vHWdJVge63pOEGyYGgTQJEC3zHYGue4gciVY6o4t6SgHOJjSeSySVdcbhzlXPe5x6koOdUcSNJKO
cFS1xaeoWajj81ZvHWdJVgqODek9gL3udHUriqvPmVxVHO8yrTUcW9JVhe+zpKnQDAHQe3/RadmP
cMftnw9HHunn+2x7lPuga3Uq65rm6S0qLg3xKDjXpZEjXP5J1N2renoNYNXGER07DkYZf8u2Oqc0
6gx2ufybHoBjdShUxBNvseXYCeYkKEWHksLl2GOQnsEc0WnUY9MCQPEq+RF1qJkY5J7S5stP4pzX
EAgT6GMZA+aPr6ZI5Cf9uwsmSNfc8iZa4fkr90GOD7RaNVBwVs37h+q2qke4GuwqFFg9S4NxGD1W
yhgkSR/qRht3rO71yqTw8uDaze+3IW0Ndo0i3wytopuJNjdA2Gt8k7/LD9FXd0p/qFQe/ifD4nmR
ot5UPE2oA131CqXfeIW0A43cltrZ+apOhzn2ugvA4uimrn1zMlbVcIEgfmq9ING6aDjkB1VOn6ws
LBwhgg4VODqYVwdDzVOfkFXflruHLGzGE0gGS3MiJQouJjd9xreHRbLTMWu73jxLaN4NB00ytpxi
1yp08WboSI14VR3xn10fJVZ3joOJYBatppnuBrsKheSRZKoCiMO1x3jKe6lgmqQ4p1GIcQx5HQ8/
qn7QB9oLf5+QW00jG7DXcKqWn4CqO6+LXxMr1eIcq9F2t8j8U7aNBUFn5/7BVaLh6gA4jAHIqtaJ
duzCY+qLqkmyeeFdVbvC2oLZ5+Ca8E1Q2oOB7YPkqbry4Nqtw9uQnOp49cc9FUJEPIYXeeVtZGoe
1V7sxRx+Sp0/WFhYOAMEHCo0hLC7Thlr/NZGOq2bo1hqn+fkg1tFjTrOSmXF7gag7wiBzhfEx1R0
h0TPgUCC9r3uM7ts/JPtEdmfTj2ILnuJGklEkySgCdNETcZOplWB7g3pKta9wb0BV056oXVXmNJK
OTnVZqv/AIl3jpGvJGDEoZONFxvc7zKl7i4+K3lxu6zlXOcSesrjqOPmVx1Hu8yrC91vSVYHut6S
pGPJcTnHPMq65wd1nKkmT1QG9fjxQniA6lOaA/P3nzHkoNR8DlKm4z5qJx0QDnuMdTKJuMnUyg0u
No0Eohr3AHkCi4VHgnUyi64h3VW3GOiJuMnnKkEg+CNr3CdYcgri913WVbJgclZvHW9Jwnxq5seS
ue9xI5koXPc6OpQvqOdGklC6o8xpJXDUc3yKMuPFr4oy4mdc6rvu0jVWB7rek4Ra2o5o6AoNJMDQ
JgyIFvmFIMEdFmo/+JWsc4DoCuFzmz90x7DVY7PP2DiPhElESD4hOIjhEnsAHNFp1HoNfyd6Ueyj
9oc/SJi61pcB1Q32Q6oACRy1KFSkOOq8yQPyVeoWta9zg3CdUi6qyk38+a2d9T7TiPjam1GTvKjj
c7n5Ks8ReS1vzjKtOjaU1Md7hVGu7SnI8zy+qpzq57nfT3zPvJ9xlpIPgpNR5PmiGPc0HoVE4V4e
67rKvvdf1nKNtRwnWCokx0RNxk651TabQRTGddSp0AwB0H9657B2T7nPZj9sRC0Wnuei0Wi09yi4
N8Sr72OExgoC4N8Sg416WRI1z+ScwxLfQawauMIjsORhl/y7YCLTqDHpGOQlMcdH6djnDRuqfHwt
n2QBIkiY6egTIxy9m4j4RPY0yDPpQEWnUGEWGJHTsDG6n3KFuW6U+EKCIK2b9w/VbVSPctdhUKLB
6lwbiMHqtlsEiSP9SMMu9b3euVTeHlwbWb325atoa7IaRb4ZW0U3EmxvdDYa3yTv8sP0Vd3Sn+oV
B7+KpD4nnGi3lQ8TagDXfVVJ1uIC2im4k2N7obDW+SpUwB9kHARq63CY6r/bsyVtVwgSB+arU/WF
rWmG2CB0KqWn+rP0WyhpiZnx4k+1xYDVIFjZJW2tZgax81WtEu3Z/RMfWy+TaY1wqV5e/wBaBc9o
HyVRr2i0Hn8PktopuJNje6Gw1vktmxixp/JUaWaZdpwy1/mqIBfxa2sBuMoN0p7zQqvvcbvIx3TK
yZgD6KhRYPUuDcRg9VstgkSR/qVS2ATWeJVafvN/VV6ceqax0CMARhUKWN26m24dcKhuB3tcamdE
9tKBNZzfLRbRTcSbG90NhrfJUKXwOptkdcLZxQHf1x3jKLpcx28IO7bPyVQtYQOeNFVqU++CBPQK
qagAcaP45QouJ+z7jW8OnNbLj4H/AKoPu474ujMJ8dVtTcWtBIEaHqtmc7Ly14nrqmnd3euGOqFR
tRxtqDvtyFUu+8U+k8epzIjERqqdP1hYWDhDBBwqdp1MK743VCCfkFtZjFjlTp+sLCwcIYIOFpJg
loPMwmOrZIrNDSfzCM6DAHtJCukz1UkySgCTjRE3GTqZVgqODekq1r3BvQFTOULqrzGklHJzqs1X
/wAS7x0jXkjBIlDJxouN7neZUucXHxWar/4k1z5dHirBfrJL3SVDqjz5lWF7rek4UtJB6hCXHGiM
VHi7XOqu3jpiJlS1xB8Fc97nEcyVxvc7zKh73OA6lfav/iQaKjwBylWtqODegKIa9zQeh7IfUc4D
kSpJlWB7rek4VrXuDTyBWXE5lRJgohrXjEQXy1vkgbjI0MqGVHNB6FRJjWF9q/8AiQNxkIhlRzQe
hXA9zfIp4+/qpY4tPgUSXGTqZ1QG9fA0yu87HionCkmT4om4y7XOqHEcaZ0XE9x8yuOo53mVLnFx
8Si01XkdJVge63pOFIMFcTieeSrd4+OkqwPdb0nCwgXVHEjQk6e1axupMKLg7xCc/k2PQvOkwPFM
c6OP8k1g1cYVtzR48vTv+GY7Qwan9u04OpW8LyC9+rGy4rawB8bcKq2S23Wm5vd8iq1L1ha0GG2C
B0KEgiU3efY0GNlYql/rZJLYiVWFsUaQPDGnRV39GR+KZSaPUBoLsYONVs1NmHP4nHzKvoCDUqOy
PoqzwG3ktb84yqrXvJsYbgG8MplHFjGcfjiVslIk2uJcR8//AAqryM1XBoW1RG7YIAjnK2O8y7vE
+E/+Ef25IJB8EQ17gDyBWXuM+KtdUeW9CVYajrekoSSYwENYgSJ6IicHVQajyNNVE4KIph4kRBfI
b5IOuMjTK4HubPQqJMdFG9fGmqJuMnXKAvdDdM6KTUeTrqiJOdURmSLZ6D/m6GN1KD7muacS0qC4
N8Sg416WRI1z+Scx2rfQawauMIjsORhl/wAu2Ai06gwiw6jp2tbgXNuHa5+IbHoCebQ70HVJAAxn
n6LjIAaJJPbARadQY7BMZAKBkZ7XgxLG3H+fn2R1RadQYREg+I9K/wCGYREh0cx2RIHifQeDEsbc
f5+foOfybHYMg4nHtG+EnzQtp7uKkWjmoIgrZv3D9VtVI9y12FQosHqXBuIweq2WwSJI/wBSMMu9
b3euVTeHlwbWb325atoa74SLR0ytopuJNje6Gw1vknf5Yfoq7uYp/qFQe/iqQ+J5kaLeVDxNqANd
9Qqt33iFtNS6wXAXAS5bsj7akNfvJlL+zbnz5rZrjI3ROfIqnvjPrgPkqodvHFpxLALVtDmai35a
q5w9Y6kfnkLZrm8qhzzwhVYeNz4cQPwCdUdcyoGs7rdMKo9oN24nibqZ1VF7su4hKobj4tcd4zoq
9Nh4BViPxW0OYOIW56arfPA3m6Oo/wAQgqiaX9Zl2O8ZTzs+PWkEjl4LaLeE2NLgORxKquaJe1kt
VGpVEv49fiFqY8u4m1QAfBbVUH2jXxPRuVRe77RzeJUKXwOptkdcLZcDuP8A1Qfdx3xdzhPLcZlV
zOlERP8A2rZ6hgv4pLhOio1Lnk7yLnCFVu+8QtoPE0XDjZyXERxQZAhVKUeqaHQIwBGFs8DFjfoq
EF/FqGsm4yiG30mmoYcBM+BVanOlWOHTmtqfT+0DgJ6Bb0gb00CTj/FgrZ3vy6HifktkDDE6+PEn
GgIO9cDH5BT3XAN08lXM6URE/wDatnfU4ncfLWNEDNRzru85oHyTX0cOLyHEfktpD2hrrmYC2im4
k2N7obDW+Sc4RI2YfotlM5f3j1ynwOEOj2UhAuqOJGklSTJKAJ00RNxk6mVYHut6SrWvcG9AVM56
oXVXmNJKOTnVZqv/AIl3jpGvJGDEoZONFxvc6OpUvcXHxRcKjwTqZTX1Ln293KJOpQF7oGmVE46I
Bz3OA6lcD3N8ir73X/enKk1HT5rge5vkVcKjrtJlE3GXa51UTgKGPc0HoVbJjontbILiDIOiJL3E
nXKhj3NB6FcD3N8ijxHi18VLSQeoVxe4u6yrZMdFfvH3dZUuJJ6lB1xkaZQ4jjTKtnHRSTJUF7oi
NeSEOcLdM6LiqOM9Spc4uPiUXNqODjzlSSSUJc5zRPDPgrRUeAOUqGvc0HoVwVHNnoUQHO4tc6q8
Pdd1lElzpOudUIccaZQycaeCddvLjq5r4JRfEeCgvdERryQycaeC43ud5lcD3N8ijk518Vmq/p3l
3jpGvJDiONPBRcYmfZkuq02wbczqgCQQRII59rHGOPT0HG4Na3Un0YBAxJJ5LWfTBkZaXAeX7au+
40u/AKi11HeEy/Uqq6Iik0Bv3ZVG4d1jqpH0VN7O+8kSBp4JznEteLWSxsxiVVq28TaYBuHMqgXm
XkEz4KgygO+JJjUqqKZhj6pA8v5Kq1WjNwbPRb2oAaopZkdTj8lQ3WtQSTHeKu2Yd+o7I+i2hzTa
7haY+9zVapANrYE9SqPFUueJNrAbkTHqqdQuPkm1LntqVXHLGT8ltFRjYJeGiRp1VRujmN42OGPP
zVSmXEinTNzQ3hUcqVGD+H+5/bU64IUCtUA6XK5r3AnmCsudpGqIa9zQdYKLm1HgnUyjxHOvihJm
FYHuDekoCcBMZTJZE5B1Rlxzr4qwPcG9JRse5s9CokwiJwVYHuDekotkweShj3NB6FRJjorHVHFv
SVG9f01RbmXGXEnX/m1a3VB1zXNPNqi4N8Sg416WRI1z+SdTdq3GPQawauMIjsORhl/y7Y6otOoM
ewdHwiSqk/1feQnm0OTTIM8kGAgT1Tcg3CcJriRxZA5wmsGrjCvxF1vo5+9b81UJj1Zg9gY3UoEP
YOK3J7WOOj8j0IBB4bsK0emx2OPTtIkHxHZYI9g5w0bqhkHHL2eG3SCCPCFbTD81MXc8KDgrZv3D
9VtVI9y12FQosHqXBuIweq2UMEiSP9SMMu9b3euVTeHlwbWb325atoa7RpFo6ZW0U3EmxvdDYa3y
Tv8ALD9FXdzFP9QqD38VSHxPMjRbyoeJtQBrvqFUnW6AtopuJNjdA2Gt8lugSw7vuObwnGq3QJYd
33HN4TjVbNAxY0/ktja3R2vjxKu1/dY4W/4VWp+sLWgw2wQOhRtMSIK2k3kmAfzVCl8DqbQR1wtm
Nl0Ndp81TqioXDIkiHLK2cO4vVFwB5uymuq5LazbSUwP7p2gyq++0YJGO6ZT4H/2ct/Cfqqo4mtb
DN4zlCMwZAOBCbNR3elbY6eIVAAemqFaQDuZc6JK2RwLpcIJcMnKkuMpoOjuE/NMa4f/AF+J34St
ltMXTPjxJ5a57PWuEsbPyW0upi0yzUaaqk8951ME+K4TH/x5/JAno76FMuhzt6ALlUJc58PES2AP
JVhJFutN7e75FV3N70tz01W9iau4u05zqqdSp37iJ6hbNiTY8gdTlA7Rn1jQCfzC2rejujpplbU+
n3w8CegRqvtYRTkutk+fmtnfxEljsuGTqtJMEgeMKlvxLN5Fx18ltArDDRjHdMraqR+ztdhUKXwO
ptuHXCoWl/FqGsm4yi7Z5E1SD1HQLaxAY6AYai5o420Glqo1Kol/Hr8QtUu4nCpA/BQRB9hIQc57
iRzJUkySgCdNEXXGTqZVgqODekq1tRwb0BUznqhdVeY0ko5OdVmq/wDiXeOka8kYMShk408Fxvc6
OpUucXHxWar/AOJWbx1nSVZvH2dJwrRUeAOUocR4dPBHJzqrC91vSezhcW+RQNxkaGUIceHTOi43
ud5nsGTjRAuqOJGknRRJjVQ+o5wHIlN4zw6Z0Use5p8CpcST49nE9xnqUC17gQI1Ql7jGdVJJJ6n
scbzxa51QyeHREtqOBOsFESc6rJ0QcHukaGVcCZ6rU9VxVXmcZKtdUcW9CVE4PJAhxlumdFL3Fx8
UMnGiBqOL45OKc1t/F958wPBXh7g7rKvD3X9ZyvtHfipC43ud5lQ57nAciUTcZOplB1xkaGVDXua
D0K4Hub5FEtc4E6wUHXGRoZVxe4u6yoBOsqSZJ9i+piGGChU5Ex7B8EEM1I7Awan+4l33Gl34BbO
x/deCX/P/wBKnScLnUqbnx1Kp7/PrRbPTmq7nd24WjonHibcYFRomFWe821L7bqbZVSo1p3jGDvD
n1THVBL4e/TOmFRDh9pVn5BGDG+qx/P4ra61sNaC0fRUaAw1lt3yyj/cOdcELJJV17rusq41HF3W
VbOOi4HubPQolj3NJ6FXte4O6ymEFwc1sTOVJqOnzVocbei46jneZT9S9+C49P8AnJABJ8E1jhxO
5IuuY63DrTogJhB/9Io2kxz/ANkAYyAfRdTdEtxjsp5HGCR8vQtdr2MdiHoCQJ5ntNvISmOxD8js
c7k3VOiOEXe3GQccu0GQZ5elaNfQeDHA24/z8/QtEDnJWs9pyBAnKbPxCR6LZ+ISExx0f7TZCfut
W1XCMR85UEEHxVP/AKh+gVCl8DqbQR1wqG4+LXHeM6JwpjArHTyCIjp9FWAJFuTTe3u+RW1Uj3A1
2E2i4n7PuNbw6c1sv7j/ANUOeHfQqnvjPrgPkq+9xu8jHdMriPIR+CZSpNBplgxydjK2WIw1xyJ6
rZnkuf66LnCESwwd87P4LaqWN2GkhsKpaf6s/RbKGmJmfHiT7XFgNUgWNklba1mB0Hmq1ol26P6J
j6+X3G0xrhUry9/rQLnNj5Ko17RAPP4fJbRTcSbG6BsNb5LZ8Ysb9FRp5pl2nDLX+aogF/FrawG4
yrKY+PAcqpLnPtcMlsAeS2hzBxC3PRb1wG83R1H+IQVRNz5qZdawG4yiaPD653nGFtNLG7DCQ2EH
Wu+xbxN1b4o1XPu9VLXBmdeipu4y7PE4RK2Y2XcLtNeaZUvvGRLhDls26xM5A1ynGhwk1IdHLGn1
VdzGxUhhdA7p5q9w9Y6kZ8chbNI13n0WztuIDzNrG655o24mq4T4YWhBCrmdKIj8ls76vE7j5axo
qBJqOO+HE5oHyVZ5JaWkAWN7oTiy4E0STIiSqG5+PXHeMpwpwAazhPQQFWp+sLWtMNsEDoVX/wCn
+oVC4kiyVsbW6O18eJbQDoxwtHRbWYxY5boEsO77jm8JxqqFxJFkrZt3iZ0GuU4sLmG+DY2eWida
0jwPssmYQD6jnAdSpcST4q2cdEHXGRoZRDHuaD0KNj3NnWCpJkq11Rxb0JRNxk6mUAKr4GmdEOM4
8VIJBVs46KHVHOA6lC5xMaSVYKjrOkoQ4i3TOizUeeeqgkxqibjJ1zqpa4g9QhLjjRGKjxdrnVXb
x0xEyuFxHkrnPcSOZK43ud5lAPe5wHUrNV/8SDRUeB0lWtqODegKIa9zQehUhcVR5nGSntbIJIMg
6IkvcSdc6ohr3AHoVE46Im4ydc6oOD3AjEyr73XdZype4uPihDjw6Z0XG9zj4lMYxzmWiDB1ypY9
zfIp4BNziDdK3m8df1nKk1HT5q0VXBvSVxOJz1VztVF7tI15IZONEHOe4kaEnRXNc5p6gouuMnnK
IZUc0eBUSY6Kwvdb0lYMSg242jQShxHh08EcnOqt3j46SrN46zpKDS42jlKhtR48nLhe5s6wfZBj
dT6OMZA+adbVpvLckCfQAPMA+kAOatua4jWE5/JpATmGJbjHa533f21Tg6mFd8bqhk/ILazGLHKn
T9YWFg4QwQcKYMHRbN0a01T/AD8lXLaO6Nvfk/gqlMuJFOmbmhvCmUcWMZx+OJKoMoDviSY1T6pH
DRqH6CEWCLqrrzP3QmXuc8OqgC5sfgqu9w3DW47sqvTc2KDGkWxp0TKOLGM4/HElNd92SUwmo4Pr
H4G5PJMaBwvrl3yH8lB17muruJFjZP4ou2cQalR2QPyW0McGtdIJjl1W0vGGBgY38fecejn3yQYK
4nE88lW7x8dJVl7rek4QbJgaBMtJa5oiQVx1Hu8yo3r+mqJuMnUyrW1HgdAVFxg8lfe67rKmqXVG
8wXKwXxMy90lBrqjiByJRNxk6mVgwrRUcG9AVN7p81a2o4N6Ap0VHi7XOqcGg3uw4zyQpjA1Pife
o9Of7jn0592//8QAKhABAAICAQMEAQUBAQEBAAAAAQARITFBEFFxIGGBoZEwscHR8PFA4VD/2gAI
AQAAAT8hdLyS5cuXL6LdS+i4suXLly5cvHRcuXHoX0zFgy5cuL06S5cvouXLgwWMIp1O7tF+WZm8
xV6BZcuyXPhIP/2A3zL5HMcJfEevuXAcy76iy4suLOXn9K5cvrfW+ty+r6Ll1L6a6mXK9ZblyzA3
HUVoqv6n4UHpcuDEnzLnftgU9u0BW4GDLNw6XF616CV6OXn/AM9+jjq9TPV6CJslx1n0kZJbx2ho
zMtT39IjGX0sTugwXXzHYlQ7DNcLB3nMb7dcupHPW579efn9Q/Xp6tuhj9AMxbfQSpwG5XP0la3q
aHxxFfEKjrrrphMH2m9tTS+GZCx9uID556vic9HxNsrH6HL05wc7t/kg207ZyqBmNlC7bhpgxBwP
3LMNwXKatdIw9FyS+1bfeBerBN0Y2/SySvzHcKRpn53ko+ctpUP3ONB0XAzFymJXGwsWwOLTyhAd
rGGFjEGOIxHrcIvJeDMP2JZ/G5SN9qRjeF+xHq7amo29wGwmP7QUFtINNWC8OO85XOUlp6yJtFpb
smYzYHMG3vAjzcTVpaPtKbO6Uw/MuduAU34hImRSsm6Vit+mYmDiXIFG1cS4egO0ON3BcVNKt1Fh
21IstKWF/wDJEERz2DjMKKxY1vxExJbwJOyPSveVCU9FjDn5h8IFbPMS/axGJb11NwMzNvXy+PV9
l+yb/wDGo9aIE4o4qCZ5dQTivyysBpRu10N3SBL4KA9Ch7W6m8SvC4RNfaFCoUiTJYvtDkJgTNDf
7sNGrW4NMdfgGwuCZY39PdELe7HYm9BJq6qC9+rtW+85JwDYUuYA6MD6/wA+YrA03+8aRr07qJi4
jpkfwRHMilr/AIYkX6LTVMJq1tS8pzNCebLTks4LP5mdEZR5dn4j1ogTocVNgGzjsJyIQToFP4fm
IUm3y75cz6mULi95l0PxzFYCSXVlN/7iMSpQ1DW6h/3cTZO/E1ELlWQo/thataxo08sd8t47P/Ij
P91bf/U+lsDMu4mGvh57SrMF8p329KNyu01xL5l/PS2o7GBzqzzOaKDDF6mVjY7lDLETM1Ae8Go1
K6nVbHz6HpZMdtHlfeZPSoGo4uqQO3zEAygLd/8AZVqjdJ8ulkIuilWPHiBKcgkI1RTlvvowHZEb
tBhh1GWV4Ao9w4Sj3Fby+g8r7xXYcHlfeLfGFHkvf3hhpov3n2idbEX+4pQurVV72xK6OvPzbnAD
ZVHjMYTWKL+zBmz6NkF7x05XsZhd6ZBtjnMKHrEG3FZzDnUKW9VnPtCPtLqNisppiviOb3EDt8wt
riN3XLctV/arUHgZvDM5xOcEViAQHbMY0eIrcQMcQK0JRszGmcqGVfwKLOJI/KWQ/oPLLCz6Vhx+
NfcHFsAP5Zhl2b9OTbWaQMS+8udgVOcykDvjpgLt5ijaUBwy2IYZxOU23LzK2jSfaVUPeYg9utTl
/wChIR6Zj0Fm+l+qupOToZjgXzKHBjzGq0rzEcMRbtFxCX0dwLlVNytQxAsuIPPEz+F4nBf/ACeZ
8w5EzcUmBuYMQ32gz8xZZlmmpx15ef8A1MIR6cS+jr0V0463DooMuZKJXmY0MHaWylwzKYlQajad
kpTMzuJj3mdynjzDSqW5gxZOz5nGNyjxMlcRzmOqjZlHREnEVsJ536OXpGuTQLWUIlr2gESe7R+J
YJGpZGYFLJr0IrAAv3jc4q6I9i78q+89KjkNrU2D5eeg/HKdn+OjeyW1cu5WtczFYVRcUX/Uw0fa
A05hRofmcDSDgVBf3MtrmJcX4hKVwq6Lx03LdAqZ9i/4nHoFI2qIj25eZhqm33i4eNR89qtNgNSr
8hBMYR+TUTA3vwRAChfZTX8Rw09AVklVniUJHGJwwYEwQN1mMRKKhX9wxlcEswTkw7xmWuVZPfH/
AGL0UUHzX8ROhFBmeA58o4wTEVWZXEWlO9TJVdFPeXa8+kUbFGc1T59xkCGEZ/ud8akWCuBDfmCx
bLQpk/cxaUBOcpwzN/AhiaEoudD2joARV7WJ3HKlCeXTzgAUpZdMEJDWGpYZZheozm6Qqat7O14n
cGqUJ5RwtTv3yy1fBdpAxvUDVwFjLXf3UeZi1OCzL7w2+E8X/wBd4lMcbRam/vG7wE14xH1IYS71
v6gYYui/cmDq9RWUMO9XGrlw9Fuz9zUFAEwMHt/MsDoba1QdjcUqgdTYrrtM5Ner3O44LsDdyiae
YmDs7Gslv4jTDkTJtFnnJGKTXjEbWMj7Yh+WxZZZCz3gNHYEQvInfQSfI8Q0pKFs91e2Y8miEW0q
h8RsglVY3GujBexbE5xmwadH5uNIWdHfBlvwq47mEBaM2Pc3LbjZQoGjeCNSCmAM1nWszueRqE8o
VJKoLtLmR7CFlM48RvYCLTmT8QzUCZ8znDy5KL+UEBRMY52zxNeCAD2sSgONNaKWzHDNfyB/LKHo
qzPBd8fzC9cdL3P3KkUNam1z70EvYA61wzIRXNctm0+xN4DwNDBX3DJRxUU0F+dsDOhdnY/uMVzR
JOaw5qllkuyrAOzDLNyAaZZVIlY5Xuv/AMCCtyvmM1eCZ5YcvPqtchir1GbkWq2sMRQUF1FW6/YY
+Rdl1+I23cSEWGlt5ZuPtF3ZwwpGLvb8xoW6KLeo+V/pPEpyFKo7JiGLPL6RgV9Lmp7skVsaguis
rUohcWbUvaCcc7+B48mruu0yFtz9neJFvFbBAATsoKi573byxBgNoI1FACFTC/7l9i919pao0s7l
p3kPaLKjZUWO4jJL35iZUqoF4mB+T1+IyqBpVVMNUqzv8xUpLaPwZnlgqy47Rii7Kt+ZQ45pbw94
wLJq5qMElKz3XmJUvwXB794/3OpnvCFZOEI0Q97CGAgsHaQyZ6SmZhXC3XMf2/gPlG1Wucr3jwtc
UtYIIAYVcxxTxKm/hZKtHjLKYtxSstStpbeUwnzX0jnTlBSaAXvO5x6ab4O3iIB3DNVm/wCIlyW3
a7nA2Q7fMbYtbVy2XHuIRc2pT8S3ge75YiAU8xe/McZdtn7QYVpytfhLOdas1qNmsXZbE5ototpo
lB3ncYH7k/p+nvqS+tSmX1VotKjrow6a6X0qXKIZWJogVxzHOJZcOCgn/wBpvD8Ryw/mG+8TxMMV
n25mGcH34nA2hG9XA+Z5ZfE2bld25xC3eyczvUpdYgqLDAcRoOJS/LiVuO35gl/CGuxFTAn4gfLK
Mc95nBS+I4d2Z/4gfknYhbpcdPx+m/ovUtfGLle/S+t3GXLl+kmvymOye4MWIQK6X7kt+OWA7vli
nMB3eIDjB/MeyX3l9npg6HuYljmKmBBXozuNAC2U4fbuYjG3yx5lyl2l3KG4VYTLWp5X8zkHhluF
Vx2im2+iovHV29Jo3C/rtgD2hExPdo/EuEjUsjNJKa103KiAlAX7y7NjXSnsX5q+89QkMriYi1V5
6Eu821iZYvVXvNz2gSP7N/j0V0YlrODvDG37SqYJ4isKukFzIj5JgxyQ+IgGkuNXAuYkeSUWdWZA
tq3RHcJCTUHU1PhlEWVqopXeX8oEcGMQq3BFJUt/CI1J4LL+5LaBZnEPJ2ighlOc/wD2KGkth+GZ
Ph/2H/yGY90enOIJqOnz6TNGN2qqZv4hTsuLOjUZIDCPE/1O+JCLBXAhd+YLFutCmT9zApUE5ynH
FX/AhqaHIToe0ZEUKvaxH3GqUJ5dHVwCyll0wSoNYamDLcLlGc3SWAVAL7XC8ezUCflFnpSbaKRZ
BjXPPy9ogrHVrS2L7R/CGEu9b+pQjQ/5B5gHgFIV1vPiUp9FQudvE5wkKfF9omoDCXet/UqIqhXA
hd+Zdah+VsGzgrW2Vh+KgKBhF0ZAmLZNXIf65RjdZW8GuPmC4UDuG6f5zAHPYEBeRGoWqBSmceIa
VGM104Ia/ghO2N/9nI+ubTb3ijlIHSUfUVhYA7F/ozHcAFEl3oiLDZ7wtbywFBUV7spinYAVSufC
ogjoqtV639QZ4kg2H+eY3rNxTgtO9XFUGEI1cu+YfpgcwWx9S8HRx+uOX/ZzBgqu/wDaLgm3KmIU
dwB0bPkq476byZ44uEaNkRYQjp3X7I942JdLp3qU31+lbdmIyQOUEyTJogL7XEiKAa1FrlUHuNsM
ri9SmT9wjaVHuSi4SaUuGjB/uJwFmTtjfjzKQ8DDbSMFSl1Q0Jyza1MKg+5xEfMcTcwTc5efT4PK
mbZSyxpjFkWq5YsACgupe3X7DFybsuvxFbftIMUWlt5ZuNtV2l4faYTi72/MEBNFZWp3c/8ASeIV
TAVR2TEcWeWvESL/AEuanBJLdsVWo0tvKAweeGl7l9H5ISgLgF6lcW0FalQW1xoshqBXqtQcu0Ua
lEBaDsBacCtRtufNhlwn2ATehgUuLZAN5Yucetupisn/AMjNWe5JUU+RAb733gGUF79NHjLCK4u5
Lr8CCFTpqAgPGGRC0LVtrcTeFOa68wMaXasymmeFqjmpSb7lREpsC9qdkKCtRGT7bv8AML0jnP8A
aI7AWd15mld8ji5aHNLyOIUtd83AxSqbWyVI18gXvfeZIJuQVzfwRLwIim+82r3RuWsd9oR3ze3L
q3bdXjzU1xm3bLS5U7zzCqugVu6jEJ7Lr8QgqdAvUwaqqXVRtIHfr8TJuBWXia4r3nhZpaQtCLg1
MzcIjzK95VL9BtQzr7f564fRlV5x/cZ+Q10xDpWelF7h7vYjdS8Qt0w/LK95cV9TME2LmHd35idH
TgL8GoYh99wPdaJShzd2w75My2Gvw046VPbovaLKF7qLhtVO5T+Y0GgPfH1mCLA2qyLT2lBZXNjJ
B4JRtG3JZMHA97g28sWWNRdHhmmtwemeZ4CJNBzBtc+0rjUtY3E5PMqyIWoj2sbua5gd7mAGPb0p
CFuuYlmpeXpdKhrE6lRyyaFKDXiUJ65FS/CUd0Mn/aCuJwtWMg+VwtWsjo8afOYlWwvxRBqKBr2s
fEFwyE7Y3/2BrtpsN2ZYuoU0cI4Fgt6KMvmK82ElwjIF0S2szkWNad4VcJcsx07wmKQ94Td+c8Sk
AsayNUvxFhXCG4ZU7eDA+syn9uc7IMO8qJ1ikHuje2E37jH3PqUJ5RviXMMl+bhSs8Ftb77TR6zg
33hQj5oP5xD3w8m9dVHxoJOLUv6ZiMIDVF/ixqIJ/aH+yfqEB1XlaPg/eOib2so6fhMOdZ6G3FVA
Onw7rmhjgMLhPMQeH5Tg/eKzo6wnKe3tMCUNHZbqGSdjH1ZzXOJgMzaN7cPsROQe0Ro+nzEzNqBx
Rp+SEMjiVEmmN7H6nIsI0br23MtElT/CZfsiEpSLTmDbxM0dpjsS4GBbnZjOIZJRG25U+8C9wLE7
ZRz069oul3uXUv1rQjVjU5pneWLmgiY7Y7g7i12ifMFfonufVWzRcAEF95hGLVe/MAJnTdfiFHHK
Owdpz7O8sXFnI7uLm0HBS5jUtWbIYQKSrTtBAt8V9IsCQ0F1MeywoPmKKU6Sj3TK6YuFKhbw958z
y/y7xKl9C1BsG93fSUV+U+kPoMVyOXcQVjoTi7/llTi9WtS5ztXY3Wpq6COiNVhVF6e8QKRarllY
NJR2rtA0HQ4Xz3im1vlAaYu9uBBBovcAoygdEc95re7s8Q56GHiBbLlvp+JyCRS7f1uKAqQe/eY2
EFnjohwiZD7w6tHlmnaBkijIWoVEjRMna+ItY2R9kcsT3RYcTC/JmbuGClC6eWCghL/CXykzs4nv
i6Ez6Xb1V146G+gRxDpU1L6+eoZi3T5Haf5NQDFN2qBGmGNyu0Oq3HfWjmDnM3mYCVCuYcgbirep
h5gWpcadw1zLVHHMp4nBhls1jvEFrRxNg2IVdjj6hbKUpXtfxMljntEtmz4jbSj7lRZmYEFlbuUr
MtqoFFXFaulYqVU4l+hK/D0HQ11ZuGIzMGV0ZcZxLx6kuyLAkHKjrSmDBULswlMpjOJTiXicS8QS
kg/cBQM01NlnNxhkw95yH5nYCcSr37agsMPXDOUJZg+5bZuPvFx1E1yS6DQjghpi2B2l2itZllZV
At3qUU7+Ycm5VX8mIQxX7Q5o3AkHEHePQ9VOh0+k0i3eXzchrL7QyJPdo/ExiGpZEpFrVqEeiKAA
Xq2Ns5VLlZbC78q+89MRjG1UwnqXk6Vjr56fMXUM2+0TxV49mK1beJ7jHxxxCFqMRXZOlcwIcmEf
k11FDpYnRxU9pbL9oKcxfEzxNqUiCnPfH/Y+FRxEF/ELW2AI5d5D+YGKjr8ILq4qO1UNXMNO6ug7
syoOv2ZluUquLLh7xmnxU9iNoocPxM34Rt9k2GHe9x5h5Ys+ZV8RO19Ew6MdvSrWrW6srJMuml5s
m/OIjKRhHif7XfEhFgrgQu/MH63WgTJ+5mxUE5y/iYVuf+BFAYGle6HtGxAijGrEfcapQnl085AF
KWXTBtfphuLDLOLlGc3SWkVAL7XOApbrGsTz8e7FE08wkKQ94Td/fEql1KiqY2e5uJqmDVvae5Eu
ScRSg14lAeuBUvliLjCSlK93vO7g4LOrxblHuFrNe+cRDRniVsAwwHGfM3vVyArNwdRtEchTntUr
J0nCymEImHwTPiiSykx4EGi3WgTJ+4MEDpvhBkK3hgBRxRLFsG2b3triZjGF2VYf7iVuljVOA5+p
YJqqv7HtHgBUPajLg3LDXzgVTfiV1V6GwvMzdwn3lyYKsFG0cUhY+MxhwUqNLvR7VEqJVm4WF/A/
MrkbOOSfz9RajWGwwe8uxDmzvJ+0Iyi9exll1IpDS1e2sygX6Fl/gmWEFqXXYRL4Fbuu2ccR7nAk
gZWfMBojYFF9/wAH3Gl394PgH2R72Tyhtym0XUCUI5glSo/lPaGJbxLy6X1JIDScTf3oqkdORtXM
XABVnUbbp9h8xMC9l1HbdtIMsbS27vNx9ou7NpmEYtV7lJa0UWtS33/6TxBWgFNOyYhgd5fSJDW6
uanDtLsgFMSi2qnw4z1BAtcX9IZMNI0kJA5QrsJyLO6vFzWRYeYK5R3Gu0tW3TGWAQPRZiInG00z
LHeBeXnzEg2Y2yEHwTKy1Uab0CAx3ajZbFwUTaSkSVpKWiyMFXi7fEsLrVjPbtOK4khqCiVf9y1K
NK7s94gA7G+kvgp3cGDSw7ULgBMKznb7zmiAL8I197eWYNytsme8ONJor/MToTasspcG0tgYq4Ez
/clAUGQvXibm6lWHg+ypcpEq/wCpGCvADSi/7mMsLeeb8zWhkpcdDEFHmULe1L5SyhfJuezlnqXG
GGsJ0Zjc1eZ5aj7mWdwO0AOEwyQbeer6a67mc3Av6TbHMrSiLQe0tl8dQE0lOumum4ldeYsJaNy8
tvExIpisvSVn0ZISuHEOBtmI1qCL22QPeIvfSVaTFaijMQF+JzN9EdTDDqBDeuoldGLQntfcrEPm
mZtqeyQiW1Ke4j8EqskvroZmo3i5+DFuFHE5dL6VGQUi8BiBmIWUQLTxdQb453I0Z7cQUUOUxeE8
xtC61i2Tf3HccnZeTX4IjNZAkBfBM+dq7Vz+8RTes8dWHziX9Y0+ia8YZgZmVwAB+8pVWwywY+Fw
QUOVwuE8w2nJflJ9McekL9XHRllLyCK+cQ3MTbpWImkCtKNEuDZfaOaClKm1udzqY5W4YeI295mj
9oNHtMsH5m036DC9xVY1NYizuKlMIUJzgvPaO8S21VxJ3V3gxR8l3MHsfcLuMR8qPkPDMZvpE0Yj
IVdTnMVZyl+hGGrDeO4x00WI3z3X4Jk+6ixjOLvb8xe3yv6QEB49gljYvuu1Ri3irJRMpHMLJzWF
V7FiY8Ut1zMmzUr8Iu+GKnzi1fwdL9uly7mo59FYlSuIkt+Ij9u0Ul3rQTyQoM+CvEqVvG5W7oZs
8zLyPEpb3SlQXX3LT29ovumveWLHc4tKXBK2ZbCkGEOYncS0pxKOyVpxAGmJsxNh4hUo6d2T4myH
5iDbhiBTxOHCV3jBzaYaDKW4jnGZUOYRY5grvKKr4lzl5j6SL6n02HpK6LrpVdFmpeYvBPaJXRsy
WY7g6JliDNBFLZLjORMQFfMShA47RGK5IkWDmklroJbbpVl9C37StT8pzqY1K0SNCmIo/pMtMS+e
IPImrLxYpA9hUtaiqtndhOdSxNIzNsM8x/TX0I+t6V6h6XWIs1FuXLtGolI57+Iz/wBiWKXPHRUt
GbTOMXeLE8j4ImufxOegY89LgRYJVwxjme0rTDEq2uYkK/hFBnvfwQ79eJZYw3ZqLOZVg1jOPaF6
yMvFzE5xE/tHJtm5V3KqmfMWx9QTABRzCJie7R+JcJGpZGYFKa16K1AAXuxFOGoynsX5q+89TFsW
pt/S8wl9SNkXe/BGnSBaezX8QlI66D7TBBWW0Vf5g+xwfui/hMmFcS1FAO7P/JZM/mUc4gu/zUsz
h7TBLbc6hXdGJvEAtkv2e0FWu37zEdhLxUzYuaqAjKPzLl2PxANGwKXL4iEwAL8ly1/lLE9/mWzN
kpnfzbiBnaGw2mHcT4IrQ45gDG1UfEnARGqJ2GRxCMkEZZgpWT5g+PdmQOv5ggtLTRr29NeIztS8
GI3zfOPGIyQGEeJ/md8aEWCuBDfmCRbrQpk/czIqCG8v4h0lV/AhiYGhc6HtG5Aij2sR9xqlCeXR
ykAVUsumDaw0hqWHvL8LlGc3SBbVqX2vE7glShPKKLWE+YILt4DMTOI4qghrUg4Zydsb8eYFMWuO
5hDXese5hmvh4Bv7KPzLWA1OxwmJJQMBXpCyHZ4YH1mFOFz25RNPMBJSXHtjBolQGlp9xRKCDO8k
ZTMhXtYgsZsqt7ktCmYO1HL+JjPFXly/18RFb7OobWveKAmPdz8vaIXLId+559oLdCxrveIthgGe
Jj3YQYDjMHuBgnPKOGGsLqYfmHStgmXGEwPiMyYKP3jGkCqb1ddor43NHZg071AMsMOj8PmUrUrW
3ZP1Gp+iGgqx+YnAkx7QSmCIymD/AHMKOTZlhfDvNhJdWGbi/g4+CL7R4yGEu9b+oPjWagJnzEQq
SbaKSmUVyFx+XtEF3dG8BthKqyq/se38ywcwOGLwvFiD2H+3Kbg3xgzAjRKTvmk7WCtxmr6DOA2/
Uui5Qxr2uay001M6OCCzAHsy+XHEsN/MqcanLz6qvK5fSO3ZCrlioAKC6l7dfsMXIuy6/EVM20hG
4ptanNx9oO7PKaVR3t+Y0LdFZWp8/wD0niGWSlNOyYTid5a8RgeEXNTg8lq2NS1oot6igIY0sxxT
xN7cbJVo8ZYsCKqlYIAdN0fEOmekpjkD+BzAxCFGFt47ziUad6ZcO3tWhAh8cnX4joD3f0lYSaoF
YSsbmVlxN3Xy18IUi7ivfme8M0RDuiOZq/aMEyW+8S8aVqh5sMDBgtn7SEectJCLVlLp5d451t2b
Z8wGNpSW+HiCV/IR+O0PGCLJVo8ZYuWdri5lKw7F7feCc8KPonvyQtho2wOXPfBY4uBYQtl4ZYGw
Ur4PaN+6FjCKXxdUKloNDB4hxogK1F1PgX7kxA5+RuWLptIMeBdhQZirbYxf4hnsyyHPmLPdxLll
3tzMvDu1utTOBrAqIJt8ELh3AXli5qbe0oEDjZGZ34jog+E5efSCtG5Us2b8Fpg4gIHcNg9HeMHL
Xt1Gx/z4xIpT7uhH0VIVNWK/x0r3mTjS/wDGP5hHoLZZZ3M0rjcybZdwNLlUYI5xxHKzBqJZmcLm
LEe6ck5CXbgZbiOYr8k0WbRxDb0CVUvM9okCkq45miZPTITiNrXUZklN58XTKHab1qBM4IrmQA/a
NKouOn0gLy6PyiSu/cgba48QafEL8Xt/MoFu0D4hzzCNy0lIZTxdTA2g2uIr4SgGyqtFs/RHaso1
eT9gyuuRUUtLfce12x9n/wBJRQENUOz9hm7aA0XuuaHDmXk1+ECXZEyClvlZoJxK/wCgsq6zKZWj
PaNOiz80/EXdBW91H9mE6Udh2n3EjvkVnsfiokwCU8f/AESq8xKlYmLtNc0mIGY2rZ3Q3FxXMMQM
E9qJuYtf4nGUg1r8TWmZaqx0vAqE9gdxeRhFuXXE5zDUwuI4jL7zmcdRnspB/t0VQm+IXnsnIKl1
xPdPwm9T260HT2QRvM5enWaWDuJUCmJQFRPYdCjK7HGtG7jMhYYvZ592vxDVQc/prPFRtTWwvnvL
ypVfmqOaEpDZXu8wBQuoVFznud5YuGdfkoT3NKUzCfUZm1W/mAkA2KmowPDLmpRCtL2oO6Ndjdam
z7e/6QHEalsEolXr9x6GWW1RhWQlVm/eBZcxPw6H4RZ3HRkNzmfUWEyzcsC1i1HiW0J8XCrq7h76
WMKYAtmoLvPwwSUQu5szz0IoxC7l94PeVC2K85eTgj/8ZDuLlLPFygBNxQ6fcGpnpcVRVM9ycvP/
AIk6ViVjriNdA8E74jGaiuowlV4Zi+00lYGeYMfM0XAoR/EVY/Puw3MXi4GWpR9koGzLGqwr2iJh
6EzU1LOJ2m5h3Sqq6xBvPxMTA8dpg5anvF2tl5LTO3eZCpXU1LuX3xMcM16UTl/5a6VKnshQjC7j
voReldTZOZbBlfXWFt7RFa1O6bDUJxuc5WC4jacwK5zfErhuMXU1iZrUp+ZVslKKT7Q3DxUaY28s
Q4V+0SaTZTz0XFXMa7SjmK6fMuB06iU9CZfacTMC4EucvPpr9touCSW/cqAbE92j8S4SNSyM2KU8
PQ6IAC/eXZsa6U9i/NX3npcYhtVNg+XnokWYyuzK3n8rEzADVsXNER9ltRYsXG9kvplUwz+8dayH
vm/66XLo9FoFzI5OlMFBW4TjSXyxKKstb5o/udnNUcsNbfE/cimmXVopUM94EACYCt2yzZL1WiUK
D+c/7LNTFQH3qUBZhwzeLsFrdS3EV3lwS5boItsOaxNH06LT8QgBzKYsEfk1K1d++1//AGO4wvVx
Pzj8itNa6HMOlM5efSyi4G7yhMdqA129v5jIENjxP9zviEiUK4EN+YbFutCmT9zEpQE5yh1mb+BH
AaEoudD2lWIRR7WI+41ShPLo5yAKUsumDVxqDUwZfheozm6S/DDt2Ll66kZhaHvCqixzsAw7x5cv
WwUuUwGDDS2GICaKwbTEDBZPoTLZUV8ucAUC2dO6xCR4FSARzK6t7kzCMAVFAp3q5sokAuHC85nA
wD8w14S5QxGQtEusaxPPx5sUTTzC6pDkHJu/OeIxtEq0Y2e5uauaOMzYXeYEzhnLkhnZepbL8Jbt
pj0Bp3qOrNoVfmlhxbcoGcBYV3pYyRR8cCZvzLoBcwKt8rgUCCvSBqJPAElLd34agkc0Fb6hphVM
wdD3jWSn2kLgRxe5iWpRAlya17ZljTsFYrfBcZcyhGRRFPQGxeWI0WWpUaO7BdwpV7uBSbYlrWy0
CZP3DAZIo5NFxpSGEu9b+pZIdkh3zDR4SsOBo1qHcUrBZwplNdB48FSyJdcArwrt/UKRKByLcq4a
mEJYKvknFsbWpv8ANMdIVTGKztniBe0NPamP2XBXAhd+YXFIe+Ju/viaZb1W/wAPSSQGkm4PwKR2
yLVcsXChoLqWt1+wx0Gtl1+Ii3MSEbmm95ZuJtB3ZwzCcXe35ghZootany/9J4goSiqOyYhidi/p
GB49c1OLKWrYKbPN1+ISGSgVh2icvcpbwu4fB3vt/CXAwd7fmXS0lN6xPbnbBPaqt1LPtT8u8R9w
0RvfmX2lCo5WZsb4RqYMota2RBTEotqp+5rr8SgD999IRcGlVUBauKKTZc+qw3MJYXvzBnMasfhN
xpsWfM1eSyoVTIq8viK3PEtoYeAjJ3IeDdwp2Rc1Ar+gjUtgjSdQGZABUS8+OfLHae+UimHkxmo+
Z5C82UwS9ZSWRoysXKeAGi+7mZczZdogCk0LqA6OBGptxgfjEXHAkO3zMkY0aauWxQ/wHadxH2kY
MeKKBIeOxbLlb1lUEaDWEhxZNZppbyUIX+QoYKAnxdficbm4kxHK/U4AFFeVohEGFWvG9nUOt34T
neE5urj4Wwc4/wC9cmJCzgWviMjX90/kjZ2DyMzINNWdK9BLqYjNh4T/AB0Hoax0NxX0hGuNM1if
yMTB1Fe6mVqbKqY0MSznIg3jED71fDBqmYi5jwccSm7BThzMbRV3e3Sl01k7w3F7kQNe0zOBeIB/
KOzSXWJ7s3uHePXEvEXR0+kXgTrkKpRcAF5g2sZH2xHAEt1jWJ5+PNiiaeYTFIe8Ju/viCFTcTcq
VPl9z/SOTKnFHdYI/wCgDA3dRVtUeJ2d+ZdO1T3c/swKAZHS2uPEPbcUKt53wym6dcpSmniHACBh
7UU2K4XQpp/KwbnguzjS+80XpNQFfC5YSGRdrPxGUwQBfur8Tt+f2cEeMXkLNQr6+RvQ7vM5kFDl
w+oq6qLnss78xUDZaRbJv7mfbN8Yfx0GPQsqY6ftRUdKqBWJX27S1kEX8wx4JZU4l77zmcExnuWu
48TBnmUIIRkqZbECbfcQ3QS7NJqc1lWMorKF/slOFudxqXBHsSpmoS5zmVKlTl6UQlJpJvjYVSWp
SqbWyAExKLaCfua6/EoFvi/pFQbmMEasjpHY3X300geShD4JpuoGjNBXT2lTiCi26JjdmbCBAHVh
max6VqAFuUvDDRriymPgpu7fP/J+7rr8R4q7LqCMmIqG0VagaWJTawqitUrCpppOpcGvf1HwqXRF
9KI1H0Zncgrt4lDES6mkfyQKvhubDDcxlGfbrTEuPTDvI0u8pkbGZaS+0HdKD2gKLJ9nEWhrMavU
7pbtDXvOOlEYy8RYs5ef1jrmV0Mx4f8Ai46W7TZvMRxSU+4lwmNmZm8XHSPDLuMIm17gR8Tul8wz
nmKVj0JUSamrgJ2DuNFXL0mD3JlXFNLrBxOQYTEDDLlx1K6OujOX6h+hi5griv1TqwTqBzcA3uW4
BmT3/aPYmbnmAafiHIvoDG5m6jTAIjxBohmVEg4qoYYrhLYhhAc7iY9kq2YmGQomSzArUpkkW2Rz
wxZx+JUroPRZdr0lFbUEP3Z2APaEbE92j8SwQNSyMAKU8OpKBAAv3l28q6I9i/NX3nrRjaogJt5U
8k7O3QXpeHvm/wCpfRh6W9E2W1BzYD/MqMKlxhfEH2lGLv8AaYOvylJrJNNea4nsYjT2ummVIVuE
Tvj34hwC0ZfB0MMZwJuPVRYrperlm7A1Zgmf27B5P+wavsZbfErBEVf0htN5O9a/MeuZoKK8rRKu
+6RGHmOYJpcQyzHiorJz1xZL4M/xHJ3/AGnLR+Y9sXWnpc5efTq4AHdtiYxUsDMcV7RECGx4n+Z3
xIRYK4EN+YbFstCmT9ziRBOcpYrc/wDAhgaEovdD2jYigaxqxO4dWoTy6OYgCrVl0wasNYalh7y3
C9RnNwvWtEvtcO9ABBDZdOWc85BWD3ZzMpQCF7tkUVQQpqb19YzC0PeF1SFjlN35zxLgjI9yALLJ
XMAPbjoINmu2YBVBYku9DEssj7ktbyytcYXWtsQyeCC6Xpgl5MTa7mJk8XAtmZdKu19hjxBhsWEq
9GfqUHXBXFnPmWcg/K2a2lwtlYfqI3xBMmCj94NOOArQfW0AYVkrTbf+OZmEAUxZm/MOlM+OcYgs
titS87D9YjM6lJXGYHVaLeAo/T9SkQGPbK/8cxQUp9AMH1mVoQMKvklSAHTmt6981B1RJxdrjPEF
SfY6qXNPTSvdDyTI1VpM4EKqBwKy/wCI2LIj23D1IDKbupCgOzd/fEe4vAOXXy9plEyQ4NSpK+d3
P9I78OybQL1NCVkQFvglEWjPR/EjLcQD+5BVU3kQM8694t57JLNMq8kW/E5uVzcrOCWXylnCBOCc
vPpShGk0k3x8K1HTZCrliYEFBdS9r49h8xc27Lr8RO3bSDFlJbeWbj7RdpcMpDi72/MalmijLU+V
/pPEFsUU07JiOJ3lrxKpfNXNT36A7i9T72Xme6TSWV7R7WPTCVSsEpnm6/ExhPi6/EKCKMjtNmG2
zPeU/WVVwgXttm/mAMBkF6PE+jra7Tthbqt19JYWMQnRAYIFDsH/ACXzrnli4VH0FpGyvj2GLgci
YE3cUSDNYIx2+ZUHbDli72Bq2CW7y+xhM65VJPKmguPNP+RvZpWe6iCrqy2I0te+/pHwHAo05Df1
BmgyFIqntF2p58QtRdqu7LTM/wA1lInM2uz9p3f232RZFzSrXbxKBb4v6TmaVIS0FuHBFhUdI7G6
+4quchUkvN6+6gimbSEtgXa20zHklVLnEGMLLc5lJQDAxKcMnvF1EFjcW714ht59TKAZ7zX8zRv5
cMcQGe81/MuZClUTYq09blzjIHsn+PVhtKNMohUuOJRcTcYdhKX7ROHM4HiO4hSWOCp7kcnQfRqc
phVRzhAqzPpLIYa8dBe+m72zLoPE46e0KIsuc4gGzqW+ycDBltIv4Yj2mly0uUwlwU0y8LUJ0XP0
o4px5BicNigafRgl7Rmcfb7TCoVGBMv7EVqSrJeV+wYtjkrWRLz+GLcjBLwqvZK9l2gYzV+YneOA
Mss/RDUBGr3bH+cRM+/jGH7j6q6WnMumaYI0ExVL3FJbVy8xj1HEv2l+3pbo6YTAYkoIWOviWIS5
+8bmuisnEvEdV1BmATEqqlDubeZad/iL8Ib4Ohbl9d9FE5lPSqXpHlWlUk94ML8TYhAQubNZXV4u
U4O2rn7uL7TyN5Ljn8i8sXF1ONLbyi+9sNlOY+FS/QQ9D1VPeXcIR6qnvKi+biPYg485jXMvhxKX
6HLFjllckvqmJnc5j0H2l8vuLez7gFGD5hjzIFLA6s46b6a6YnL/AMR0vpfoX0XL6YiVBj6Vypa4
it4mu0ue7U2KVs8dbxKMagqGemk95fS55IzaXvGL94BdMkK8y0yr9pZF9PianEbgz3l9LnL/AMNd
K/R10r1F6Vj0VKrcwg0gzW0vikqovIR7ziJ2mp71FagR9odomMdL6eZUMS6BgIKZDLG40qidpqe9
Rh6eOnLz6TLNctEF33kswGRPdo/EJEjUsjFpKa16EQgAX7y7NjXSnsX5q+89SnsWiYB1Lz6nwbsf
gjJFC09mv46DdhH5NQ1IM2+1h/Por0EbZcHIhd2Lz0uEsEsMnL46KldMpz0JU1A2G/fb/MxOZNwb
PM3Ax03AiluWo+3peSMLZp4dCst6Ju5rHQgROlS/Ry8+lAG3ExGXFHLy/m4iUGEeJ/md8aEShXAh
vzBIt1oUyfuYnABOcodZVfwIYmhKLnQ9o2ogFe1iLudUoTy6eWgCqll0wamNQbjB7y/C9RnN0hQ1
yjteIu41ShPKLSsqLFshP3gCymcRRVBDWpBwyE7Y348wFYtcdzCHscr3MMM/Q7643qLKkgBqxcSd
QwVfMYNqNrNb/NMtD2oB528RgQZhV71HcEqUJ5RkL8JFaJTRy6+XtEXzapNgpt+ojiynsXqFBUHC
xqCVt8H+EGi2WhTJ+5gcAE5ylZcDGQoxAuJtj7TSBYlY4BTy5wF4CtbZ2XxUIjRDWlWCdwypQnlN
D1FfPnMbALsysP1LuGmFe22t+YCC9IaWr21mcNFhnJn81BtOnG8GX3lb0ZOiytXuULUctJuRD2zR
Sg14hAQA2o8QvDM1An5TOXdywpGvkrftcQpYRKL7wPaXCVAL7XM1QJP8DvCYpD3hN398S6AyPcmh
rkmahwJLdY1iExTHvCbv74gqwXGAqh+AUs5f6JgwKiMB049PLz6UQiJpJ7pbyzfeO1ItXbAkAaC6
lrdfsPmPkXZdRU3bSDFlpbd3m4u0HdnDCkYu9vzGpZootan+9ezxNKBTTsmAxZ5alYumrmpwfS1b
KSzRRa1KFDhSxriniV9vCyVaPthNJqsrCSZ039IdO9JTHrHuOoSTFdX+UrVF2W2naM8JWqhfRJCk
LKJrNUNasDNSkFaKLWpkbkB0RIzbSE2B4FBlQnqQlCWtLutxQG9lw72cSDDa7kPPeVI8gXuLACzk
AppKQ11bBG2xAxcxXk7MX3lML0UWtSvF6hvJNkSBQZbNju4uEFfLvNz3HJVFE8Ni/KDcdIdEpRNw
Oy9xc3Z3V4vvGqk5WYqfWL9yYCP+gimXu8rKYCNXNT3rpYxUR2mjCgt9/wCkJIDScTur8jPeJKYl
FtVKBb4r6QUFImkm3p4r4RVzH0E+Jy9PHllw2ADuU/mGtLw98/8APRVjCoO+6axjAOdN/kmgkD5l
riLyeHr4n+X1YHhL79L9DDpfor0GfRfS76OJvquZldK6HSrlI+ipg9QeglXOXpwTYHxLUdGSQMeI
JeH86PVarqtmqC4RSdsb8eZpwLLNkeMJe9S6+VjFYrpl8vaGi0TRT911M/7Hyg/a4vZugclR6BtA
y8Xipx7AbQvAmTRpoozP8y1pOaqct5bYPKY6uN1xnvBQDA+0peJdcrb+0wBrOrADFegz/cf2hWjl
/WcdCX0Y9RrpGvWzHoe0O0yR9A9Gv0Hry9Ikw0qkm4PyAZdahd7VqAyLkpASJ03X4moYyN0doMFF
DQUVf4gJWal4ZjPOC6qBsqwUvDLxubBbpMMMqWxCEG2HLm7yLyxcEJAYL1LeLq2YGcEsWy9oUOGi
vD3nGJ2L3M6mcvwnpvrfp49Ny/TcO0vMu9wOh0uX0rvxF7y5vqC5qXDMublem+tzl/4rnH6HHXXr
v1XNzUvpiVUqcx6CL0OSG+t9KOtXE6jGMPQdeXn/ANdfq8egal30vq9PiB03LO0HMU6KV1Iyjokr
odKI9SXHpy9Jq3ql/HbAHtAZJ7tH4lwkalkboUprXoYEAC/eXZsa6I9i/NX3nqx7FqAfnLyRhxWn
h1yOGseAf6ehCe2QnOb/AK6sIWNRXZL9DGfnuOx+PSD2PhOOOqHsWibT8vPQpara7JcyNdps8yum
gAM3GP6dAQ2qm4dLzNY3wsx02TZ01vD859M4sINzb7HS4XNQAZOMf06bl4hfS8PfP/ITBZg9j2mp
z0rozl6UprYoN0HHzEhX2BGnvmyoyQGEeJ/md8aEShXAhvzBItloUyfuYtKAnOUwpM38CGJoSi50
PaNiIir2sR9xqlCeXTzkAUpZdMGpTUGpYe8twvUZzcLCKgL7XCpU/BYZxKOwdBThYvvZ9zAOA8mf
6fEbOC7CxueLbe414jaEMJd639Qncyur9yZe9eMgqf3/ABLzYNLglDIAEsAPg3EYQNSUuVHGY73Q
QMDT8RR7bOSCV+8BYwVrbKy+otR0Y0FJPzM5I0W9yAuTd5KsD/amQ5shbKw/WI3cQ5nSvDcKFedV
awuVmkLrJb+Lggl4EaeXfMtjVRyIyRq1KaZu0+pcCFvCry0/iZLKivlzlBVmWk3KHPZoUoNeJpJA
FcO4dNl1WoBQQ4o9nNQZlsHVUfUuIqEvtcwc4qhfbXZ/iNkoNqCbrhmOfvSCx9fmM6trWIMT50B4
Db9TFNFp9h7RcELAMBF+IhuqIM5sn1FI1wexg71GXXqW0MP3g4M+ulsMVuhsZA+jceGEVDTSDXa9
Vq4QtFF5KF+UaIVTGKztniYACFkwU/eIQ+zSOYu51ShPKUwsJZeecr1bKqLONMZ63LVjxK9HL0oS
Imkm3thWozci1dsDQQ0F1LW6/YYuDey6/EVN20gxZaW3lm4u0HdnDKQlWq9xqWaKMtT/ACr2eJlR
RTTsmI4neWowLulzU4PJatmpWY7Z3AsOrd/iKHaWsDc7KXouc2zvLFzQjAVqdyC9E/e8/aWGcsr5
3Hlud4rg4kGB3XaLqcKfB7xYtugvBG2zApc78W8sXFpCFRpf9wpw0lZIq2YFLjxZd4rn88ftC5Xp
KSYn5VndSvmN5YuHYLWe68xu1bS1nHOpbEMIdU7F7nNM7yxccKTatsthaK/h4nd+K/RDXJrbW2e9
NLJviQHbGjltW1lEFATrKP5hDPIDoijfgQGXIVtcXBBI0n2RMGtlX+YgkNJ+yVQeWGl7mE/NfSCb
Dfgg94zGSg7AKIms9Ffw8QrMWeW3tHhZNZostzvFGoNTvL7RIWaKZajl5f6TxD96/wBJctVYXhe8
cwldOXpBVGWVKNq/BaYOJZg0dg6slQKOauvQgoRduvr0uaitACEQAB2c+sTzySln9nqR/wDJcPRx
HEvE1L6cejUWaIkvo9KnHp5efSAvLo/KJK79Sw21x4gaHyIxj9/zKJztX4/YTwTl40e24faeEtyV
2tX8QHLBGK208TLYCbyo/ZlCqsls2n2ItTnTVTP7I7psVL5K/tEFUnIdqCBZKXkVT7FajtWqV20O
BAFocRYv9jLh0EYsD+4gi4pgebeuJgy7mXCj6r5g5KNF4bY8QAFEDILVa3FwvO+9r7sywNJS3rlv
Lc5W30IdX0X+mwmujCePTxL9NdNoT2m4/pOXn06zSwdxKg8xKAqIy2WQLG4quy9jtNBcCFzSBMds
WCpe8tveC2KKLdEeruy6YslOgvBG4zTSyr+o5U3uzt7xiubLpgAG2HLnu8urxcDKjYXhj5d2XX4g
ICzNsMKdmBi5s8i8sXCoLptIiJSsL6i7SzmPYeg6HSvRUegjv1cQ9L0YdGCMvrUr076mpXXM5ef/
AHMOh6bm5fS+p6F6T0vzL7xg5jL9B0eh6HpcvpzPicvP/wCAeleqv0TucpfqC5qEc+gly5v9Tc5/
HpNGW7tBL8uq6y+0M2J7tH4lwkalkagUtw9CAAAX7y7OGuiPYu/KvvPViG1U2D5efRXoOX8GigBp
4ZqGLMRXZLg+wacnmOk+q6JldZNte3mW35/cn1HcgAXrMspyfmSok1OJhK3/AJfcp4Un75/roPlv
RLyRgyXV/wAS4x8ih+Br+OuWL4XbbRV/mCnBpc+xf8dVYz1uGi0C/BqBKxKNr8uHoAKFFz7F/oBd
hH8qlgZ4cte3ovHTl6QopMWlWVQaJdhnJePkjIEMI8T/ADO+NCJQrgQu/MNi2WhTJ+5xIgnOU45m
/gQxNCUXOh7RlRQo9rEXcapQnl0c5AFKWXTBqU1BqWGWYXqM5uAW1ts7XiPutWoTymOj5zYomnme
ehzYomnmZ0eExDmAlY6Wwx1DFg0tMfEFfwUnbG/HmZU6RydpbBUO3Q/aZbMQ+XOKnV2lL3ke5Lkq
H4899xG0tFZ7QTN6mxo/sS98SbO8n7QjWK3ggiKymmFQQtP+Fg/KpUjE4C0fstxeeaciztwxToxy
edX+JkzYgyL1l4mTEjdWHeDeXUQe6OdmVc1lKZyk/iwgHbr79p/YExZyMe5hmRBdCqNZOoazxQKq
3iNtAPdaX9SqNY4dzGbFNjcrPHbGKTXjETPHXPMZQCYd7o4pgABlMws0CkO7A+VTZzAjNZ/MsUki
4GkTHQTZbv4NTiSAXS9cEQXVQGc2T5qOmhQYF1hC32R6mDaAeAOs2FUpOp/4mI79tamFQfcqYohX
Ahd+ZqOop584YDzoDwG36gdWkqwx/JFZYLUKlwKWSirzi3zVwYS8CNPLvmCXoHrNKxApQYR468vS
gIiaSaabIUjFyLV2xMCCgupazX7DHyLsuvxFTNtIMUNLbyzcXaLuzhlIcXe35ghbootam3/aY8QQ
JRTTsmMYneX0jgv6XNTg+lq2Ugmii1qfu66/E/dx/SCssgOifzV+kwGLvb8wwmdN1+JUSVpKWiya
T4tggWr7P0QcsnN3Sy+Y8teJvnaVfCKsa2F894b1IShALH+UrtFbBtouOUnaruaZb6VdjdalZUBF
g7RullRXh7xa9bS1mtS0lu1+yYB8xrxN/TSizFgnYvbKexpRbogcAqBWEUhZ4OcypBF4Dz3l5gVr
WyByTkpAGVyWwwIrCkaPae7bHbNH5vXid9VywUuLvS6/AiZd2VbF5a3db5isq0rl87iQRE0kWFk1
mqHteEoS9uv2GYRX1sEZ78Cgy2XXdxc2hQULAyGdbBMD8qzuoJTGgee8duRau3rpekFaMstAwGOR
/wDlkUdL5Ocf9/QDajrWM9ujCmkvv+lfrvp89eeieq5dvS+l45ly+gXKzXo9onW5fWul9DpXp5ef
SAvzR+USO5+FHV/RjQXsFta/YiAsrAzQX46lLtgowlXHwS3aSuBnFfMxdKbDTHu4uNe9WjZ454qb
JRHIFLfKzGZyeT/+sBFK/CswcowU0uP1KtSOpvZcdo0vq46nqvoPSegjCEWLfUvHUSGpv0XiN11q
Wxb6nR/Q5enWaWDuJX8yvxhRbdEULQa3HzMR0qzupzDO8sXL3v64ubGsKFz2IDyndPqZtVv5gBkX
ld53B0tNpcXCqC1SsclyQW9359HHSvXqV0v36V6ePSTos3KlTxL6GDppj04m8QubZx0qL7zHRz03
0qG5qPTjpy8/+p9PPU68dbhfHo3NT36uempvq9Ocy06XOJV9HqS89Ll9Oehfo5ef/Nx08+pK9B1r
HovHQIzGpVxh6TB1yOvaM26cxJv9DfTiHo5ekS4aBazG9hOeeJT4Kiy/vCUFmrdEQIsAb3hFFW12
S/S3CS3Dpi22nld/j0LSoA/kvo62gp8NQMgFcBBYWPudEyDO/BGS0Gj2a/joZzCPyajKttfaz++p
H0J0v2ly03KqWdmH2e0b6V42aOTz1pJcMwE4IXPsX010RriGbjH9J+0x36WUoFaADMzAFOTnokoe
/Bv2PePBr8N/jpUrosH9i/xEeKFK9muvPRjr0ijY0wR/GVfMvGoHfs/1PYiArpkTbMQ+XOBsYK1t
lZfUx3TrhwR9mA18JQQ53J4o0IsFcCG/MpajN0WVrv8Az0XUdADU6liMS2nI14lA6DhY1BM+EPrI
25IZsyPzcVs+vhTw5jdmoBpMfUv7YYZqox4DDAcZgexa47mE9hSvcwwz9Dvrjeo9qVIGrFxhahAq
+Y4OBazW/wA0wQdUFjzt4jChzCr3qO4ZWoTyjiNTahQUhA5d+XtEPzapNgptgoNNdTempqzlypiM
vI0W7Zmd5u8lWH+4g7VgB4jn6nExBopTCY3ABgOM+ZrwzU8GEJQJ8ESq5hisZFR40+cyh1V0pyyP
cib+6HamHvE4OC2LWxEJiCnsfhbFV3c4B+ELNrVsgqf3/EwoUXxDsdgDXurGCRYFkphEBdGcmSBb
Zdc1cq2g5ZKF+UqYNMI52zxDrXbFy6/uI/ckUA00RqTkstlYfrExTIRewCXnwwnbG/vmEU98ApAf
lbHMBEx0thlHeosZpicYa3WNYnn482KJp5gKoPytiquKbstbELtzU6tO7BazWjjAFNZwQh05eqns
oot0TWggVqe96lbLRZVsti5hldWwTbhgcuADuwFy8LuLcBk3JSXt1+wwDjSHUVW5Vdl7nvhAanIM
7yxcH61CoQMBmsiiLCVxdfiOtbafRHbUsyezTG1K2C894qpxpbeUMmekplkT3HXMIN4ur/KZ4F2W
3XaOWy4tVDGmyFI8KJpumnDArUSFmisrUBGcgdESO20hN5eBQYKhETSS3wq1rZHgDFRpf9w7g0lY
TfnwcGKZ1W8sXF7GNLbyh4yoFYdpYLnvfae55FbA1j7P0RcfMqpnahK8k/zGSR2oXMGrhkVf9xH5
FxdG8s253OT61QTSjk3bLzFiXgfgqLCc0q+HiJgxOxembcPivhPFCQxtldTsY4CbGLm5ot5YuAkz
puvxLeyimnZE6uxwIavlfpMBxd7fmICYlFtVP3NdfiJU6HgSuNqqQj5c2IXLFqq8+jl59J6W9Hp3
AFFeVogMW1O1G9noQUvC8CX6nNWqglx74ND2gZTyBX/kctJbh1IVVVT2WvSSuhMe01M9K6FzJE6U
56joSx7QJzfMwOIvbMpJR7GI89My5frqHQj016OXn03VGR7kexNUzUOAJbrGsQmqY94Td/fEEKm4
m4aoX7vOf6SrOPY+3eWBpKW9ct5bgYpjq45kY1yZLXXT7EUAuw70B/JKC7uhYZKr3z+CV+rxDgbP
ZoiyR21WypD4uPtIiP7LqBimOrjmRBGgeEFy+KUbSOTeDEAgKqmxbIKTNZTgmHFTlYcfynsCNlGl
93AgUg+FfsvqK9AdxlvoqXjEthK6VLj36Xs6mtCpigMsbPeKW4lCtiAWfmWU/GIk0x7HQ9LGjzLv
0NpxNzXXl59JJQZE4ndf5Ge8SExKLaqICb4v6RKNuHBMj9Y5S7/mHUT2diQkAwvqWt1+wzJI7shM
3MrbYWYGB1uPmZaZaG+/mKPMli7fG5rBchCXtr62GWt1imnZMlUuyEbiwvNrzuZDJdkI+rxdX+UG
IGz3NH1LDaX+Q9JLJz6Vl46tw30YSnHSzKt1iabi4mXKuZ1KScKSqmoW5jt79NyszTcSuuj13MkX
iJUNTl5/8h+jx6KhK063xPbqNS+ldDcPaZMNW5jnw1BEYcYU6LEigNsGpknfcww5g5l8dG4lSr/U
Z//aAAwDAAABEQIRAAAQ4s0g088s488ccA0YkQs080g62v8AAPJL4DEIMDPPOBNPNLGNPAPMPJAK
MINPPAKPKWrnHDMIgG/CEOFHPFPLPLPHAFHAECICOOALIEMCHXKcPIIN9rrOBILENHPNKHLPPHGD
NPKOFEDHEOANOhwoKFEHXLDCHLOOLFPMGANENNMOMK6MHPdYDLJNhtJHFFFMDk4GNNNEG8NOFFHE
CJHHBbTK3/BRwsbPXdqEHIJKCd8LGfhSWQGOONGMHOOHD1rPPGJw75IeQxlDMCAFOYDI0I/syFLK
LLHAPMLBPtmOIENNOCmLEvNSMPEHc+d2mbPOFMEHEJLIFHALElvPNBCMPAJDHihOzOS7kBGOGIIL
JHOOOJOMAJDJDO3MGFMIBFHDLFfe5nt53LKqBLBNDAJJHBKDHNLIJCN+bPLPMAHFKii8CFsfzcK+
KCLHGMPJCKDKIENOFNPEw27AAIEmIcwB0LA6p0X3POPKFNFHIHLEFPJHACMP0laaHFpn5AwBCMLK
NyNGTeFA/cPKGNCGEENMNNNOHCyf0A6wYpDECBIDI/op1nHC16OPFOEGPMKJNOCOMCDXoPMSJOOE
LLOCAYArrPnKZPNIDIHGNFLCBKLFLCfOENLIu9HOCFEAMbaRofsaeUPPJJDKPMFPJHOJHIFbPA9U
iaCHKLHBPWHi70GKboOLKCMOIODIONPJKrGLOPBKhpFGGNDL0fPnfNJDEfJCPPLPPPNKOPICUFNC
BHLNmNd1cIwptRxD1LLPAFHCCAPENMDKNPHSFGMBPBKb02LmcJju/DxhwPOFLHLEPPGALEEAHZ+B
BFCKCPFBKubDt104r3EndKAFGFNPDANLDEBH8RLOIHFMJOE8NvpLwD0EMliaMDHLHFHKPPNKBOOG
fNNPMKPLO+mcrD0MOOLKGH9DjGVPJBPOAFNIBENMiqOPA+8+GQqv84HMHMPIOEcV8jq5ulPNIBPE
ALLKo3V+6XKg9PJFTKJNCPFCDNOgoN/8t+PKFIGGFPKHDP57yPIHAJPVqhPHONNPPnDEFGMEHPPP
OLPHPLHKLHLCAHMGHOGC5nOFDKEHPF+98KHFPHHPECHPJGNPFMBMBLDMKOLGJNKHLIKPOBCOOKLJ
KFPGLGKBEPLIGHPKNNHPHJHCLFCHOFOHKBMDDDLFNNPOCFAHJBKHDJOOPNPNFNKHNOMPGFLMJGPK
NPHGBFMOGKPILNPPNHOOLPNPKLLNNKILGDHLJPHGPFGPPHLLIIPINGBDAAOOMGIOLFMLFKLOOGIJ
ILFMAJHONNNPJNJCLOMNHHCNLOPDHHPLDLBKLHIGEPHLAELGPHPKLFMNPCOOBPJPOLGHNNPNHDHH
PPBLHPLHIPGIPFPNFLLLPPOHLKKLLNMLPOGPMHOPLIPHJPLPEOBHMNLLLALBFKMFIKPHNLGGOLHO
ONJJPOKNANLJGNKOOHGPLJLJCNDPHPOHPPEDJNDDLCCNLPGPDNJIDCCLOPPOCGCOLPPLPDIOBPKA
EKGOHMPPPPHNCIPIJLHPPFPOPPPPDPNKHCLHANNFCNDPJBLLNNBBHDNNBHPIMFPHDAEEOOIBBCGI
KOAJHMNGHEAEIOHMFNICELOJFFLPMHBLCPDGKGCBHDOLAOOHKFAJV407DOFHPGKBKFNNCMLOBECI
EFHHOLBAJLCJDHBeXV18bLODKKPHCHPPPFPPKPPMAGPKPIMAOCPMEOErENKtDBLFMGCIMP/EACER
AQACAQUBAQEBAQAAAAAAAAEAERAgITAxQEFRUHGQ/9oACAECEQE/EPQFE6aTcj1/ADePAOz7xqWx
09sDf3gSt46TvzAXCsKZTzvWuuQJ1FlyybSomFsBbAqOsPsTNLhUCNcnRqtgoCDeNh2lx61nWKtg
GLI/iKvLe1cNwUu4R/JWmobFYWowq+AiXxBtKJ04oY/iBKDNeQROEJUe4LDNxXLp5BqUPADFWwKw
pBhEuBTjp5SXHvVcuXtLi3kaly4NxNtVc41FJskSs1AlYXfWdwwlxKyFw28I1CkiQJU2lYdZ3kbl
RgP2MW/ECu2VZ24jvP2CuW78QQaj+IMW4bOL4DuXFlfZcYG4xK8AS6i3kYU4eA7lSooRcjUvnCLr
OHUBYAZe9IpzBUXgOBGUMTAXAwpl78RtvFvgGpcXbBFxqXFi4Jce/CRb4Rh6gLCKIpCogxy2nbwB
c/zi6YrChFXA1DCokfCOuGpUDC7RV1mH2VeCJzfNNSmVNoOAwYu3DcuXBGXEuUcgZREgE2m0siny
XkNoRquGiUZW5LOW2Wy3WO2HriJ29YlSyopXDZLIt/8ACgLgEQiV/EC47bxbg1CqiV/DOtJ04v/E
ACIRAQADAAEFAQEBAQEAAAAAAAEAESExECAwQEFRYVBxkP/aAAgBAREBPxD11ouJg2+2gxpf/Aog
F3Bq9oOYbzBs/wACUEoHd0DmXD77bUtVQUHaRQxCrI2/USSkL/J/xK1cG7VouVd1C7rvVqiPe64B
48iNgK5B/ZiWjZE/IV5jXmDNS/yFZKDIiw72KjANYaX0EbEfJdblDXyBPJV0gAZ2oPyIeIg5LlSw
5KGxOYl0d+ioKf0IpLYL5l3EP35k5ENPAg8kU4gwqLahYXA/YN8diCO2YlQvBKIA9BLIJU+JjSJJ
AuxG0gGEmwDCchg3scLYKPq/TS58vCw5iwUQOWI3ZTmPJNusEQ2TjkbfqWaRIHdVBEs7gXY61CCg
QPCVNmW4IkjJBr7MvquruBRc49q0MPqBWzghq4Ab1QYs4m3YPiVod1noYYVFWAOqhEcjfyf1BjvG
XFp2WlCAOokotvooJTFWfJaWx/EVC2salfYC8w476WgKuB8YvKWwPEIkM+QT0kBsyotGQwhGkLGo
WeDniUmsNC4Q5L1sDNYAZ6SCJc/WAkZMdCVt3OXg0M0TS5vCbZjUUEX5CHofhC0A6pZAgXLblFPB
zT9GXRcdbIU6i2kpz524jfe51UsQo2QVpg3x2ifZmRJwbPy7Q5HmbcSjnvFuyvyAuouoKLgOdEH3
oKSPyxoLgFgqnpZUMFFPgJdlChk9LyH0hfNxtv2DYAR4jFqUs4+jrIKPDVK24XSALYnyCRhBGyJP
s+CSxMhdf2JTYnl6Cog/fF9IW7NMTUEII6IZZxEa2FYVNib/AJFd+gu14VCO8it6EkB87ueYDpCu
JZ8QqZA/YN5jmCPW5ZE1LPE1IlZLMSRrDVvC3bJVzhkS5JVzEueQX5FBGeYquQX7N+SyCu1lB1Tj
oa98Nq5CzGXrpSN+JYlzyVcpKfkA7xA07Hb4HiL+TRKVnto2m11AjvgZlL3Klf8AhQghOIx2Ac/x
KWRLkAiGUQ6b/h8qavqMuPfF/8QAKBABAQACAgIBBAIDAQEBAAAAAREAITFBUWFxEIGRobHB0eHw
8SAw/9oACAEAAAE/EPkf8Dg3L4xk+v6fQXzi3vLu7lcYNcg6cNW4PhdYW0x3AuOluL94WiZVmKC/
TInf9Ygaed4p5cNKr+NYqijx6wRt1POPWN7XIqy/SVzp9uDsWYxuJ68YMCaeH3iNg128fSWJH/H0
8Jg3tneM6785a+M3A9+8ihfGJTW4ZcDbde/GNA7sftd/rG3wXQ+LDf2xEo0F9k6xqXXBnw04k4V3
lVVwzQM+khLvkwSzdzThFKa6TKdoUFOB4Pvr7XOkCZTf/uEmCDfTTISS75cCaVZ4xzQt7yqqyGr5
zg1s7ypd7xeAHa9TGyC64ucqYS4PTr+fp4Z4MLZcUw1Hw/hwXK4q9v4zvFfpVy785VeDOGzCPxlc
msr5M4dx7MYfLlbdYr6cW64xWdOCncyh3txTK3Ky+sETmPeVDfV2ZXyYPB184qGiaxEim+fWVVMp
vATNzB5UdeMo7X5wRRo3mjpEwojb/OWbSnrnARQULNHeRlWWHO8k5Wda5zYb17xTqZQFbPEmCgNd
XxlBNf4yAE2hQ4M1aNgAHWVFBpAe16xQxST1GJRpNBOHFrAbPxjAEH88YOgyum9YkObqkyBvn55z
Q0YGpzgTdQoQ5cEuqMN3Yf3jeSg6CrnJgCkPT2+8AdGFg1cuUERKc3xiAJF3q8bxKnAyt/nIrYJy
XvOT/wB98TlDfGKoRpPHGbdz/eCRk+JhRZtODv5xKK0feXJWf849HyAnP3ye156mNFNa8ZXzh+p/
f0uXz9R+2X19ZrnH5uHjzkRwqt6z7cuPOLcUeCYOWzbrFbmsqTrLrjNJNj86wd63fOQ4ddmVWKPs
xL11+cKAPDsy6yPjCBHSbxXY/wAYfr94h8C9Bo+nsDxl2iw5MqrzSbwJenifS6kPnLSbPS6yQGjc
Ds3PthIgDUXCcoeNaxYAJyPnU4xpYLyrtb/5iq65Vwza78YWTvEyKaaR3c2dmvBoxR4A++AEtPDl
tTA684+zNvfWQaYbDGGp2hwHj3hzwnymQgIK5nXT59YNanZvZicQNjjCr9lynOp4xbNTDEeD94gK
DwceMWPDJocTNpXy4tlkuvbjp8/HH0ENrgnLYb++XLh+h/D9JZ7x+df/ACm/ofGPWAu2ZNcffDjO
dmJt8H0Nb+nD5x51x9IdOBb6PoXrIF4wMdc9+MNFnXI94qHkxis0Yno+rrNx17950/PGccdb+oMv
WH6wYqTm427R1ej6bRfH0FT3OMQoULz6wQdlu7A1q4uwpBaHfZ9vOIshqeqaf5wSrEQLtb19s0Ng
6rMcICfbnGXJQuWqvP8Af02B8n0VLpOz1ng07vrNJfUJcEJbwKeNf1ieVaFIW5QmkN08PThAigQA
WKb/AGYiKLw6Q5HLIIPv3iG0+Gsui7PeSVeHg84qq6AHLKZDiUDzvJNzfaG8WW8hDX7+gwTzgYM+
Mn0R+RH+cT6TE/GLppcVUj4DfeXdpRxxoacp3ixBEAiBEyM5PjF7MhawJdgDkvGBhAotAcrOD3i1
izcHMEovq5zmo3SKARRIB0Lt3JtPLkOkAC3aoXcq7mWbSDNLFUqXQxE4QTYsD0jEx6TkciVg6RVR
hQhXXGpHPY4FKEqDw70uLhVU5CMXXR54xKNwsp4KUH0twvTnAVkJ3coJgFJG2SlDb4Oclj7XAcxN
M7LdmLLzeo6bV0FTa4faxeJSirAoa3vrH5CC0p4h3epzio6lidfu/CZfiEdw3t8cP4wzGTXCOU5C
NqTJ/wCFaK4q6Pu48ezzamqCbIzdwIHK0gCqPibrrBaCvfym3EurZc1SOEKeR4T2LswceumPIO0+
BwhkroAMddR1lFX0cpahy8OwwBA1gDA2NiBqYUj9HQlFcFHVd40QbN0eAaX1cqTC6kUJB5qX7XAW
QUkYBklLc2Hn8kyVl4VA4ZhuWwVIk2I85ChCqgOCqr93D2oopQ5YcB5dY/lwAKZopS9xwshlwCuq
sDjt3vKNO6EBK+zZ3TBMVGXYWKll4OHIdcGQeal+1xXtoRQdI7H1kkB3VwSzRgKw5wLCH10Y3Bos
5vzioAs9Y8GqrJ6M0DQl4wgZQfPjHDEooWCnr+82KDz8vGEHKofW7+3JYaGmWjejc8467+2aeDn9
YKqcnDm15XzgNDTxhS6oOt5JBxgKzGE4Z2Y73k+ttvP8HLjvLnJn2z4+H/0vOGeeBS4jggTXPeTn
NKUgeASnFfGcdBioUMMKDt4XrJ31jBUhDeLXBc9wFD8j9scX35NCH3br0+MSQVY4pJ+nFtDkVrKG
9O30rg4ZrqlwJ3K89e8lZpdgEHg2Hx3MFOeimVit1Bl0gkuGPqakEY9MUpxgfslXmntYS8zvOc/j
Uh1XawBe8JxKipiRTkK6db3cDzkFiSEchvTTbh5ce0C0dwqe5m3w1VpRKkA68F3cI8JzNLW35b+c
KheyaUQHgR4NesY9mqJQ02MG+H3jVyLAK2u2KK+J1jkWQdjgmzYWPUxVlb/NNGyu2czE8GAHFofS
8+LgnbKa0Yhqmjy9HGKTnQEAWAxDabbivvEocRwQJrnu5KqUHfpcCw4DH01SOkHIE4bekiY0aAKk
BEFCCIadayD+5eLI/pcRJeJe6o1sJESEnOO2Y50oIdjsjp+GI9HKWcFQdu5iVfD++WBFgi/NwjC7
HToJ4lfk9YOsASMjEXoZdJSXBqBtXZFE2MDejxzhcOK1Mwq7dwPgPGIqFxJsB+NLjTM3EK8jVJpx
qa3mtKAwJQXZqc8BryKMs85qUsfecqqdPGbdUfDngom97bgunTsmBVgwdfOBwaDgmRHDpnjKzCQ3
Emz7Oczm2627+OM5RBonEw2x3qtmUGFaMctUYAZYavZgOmjR98RHHPk3rGDBvne8aigXdwIGkSX3
l8hTr3knPefBijxcnf4yuUYBpx8P0v0jBzdsQbqNHTk8Y6Y7QhRdCN0d4qRAwNrAD3rf5ygwrqUv
FpFSN6VxuFSMo3yXVBhOrcR56xfuSALsBtHfnISOBqtpG0RSPTlT7AwyJVSmrL4TAuJAauTQoCIw
NiWFsMGl6rzTZVYPovvJoShCWUEdViI7fLiB0qG+UVXTNyXhUw5mIW7HLSU8cYudcbVrlpKvWGXo
ETXYdJVwGphxJoyjLsq6cTvHY6hBFHdVddTGqy3wrQJaKOzTh5XVKUkSpxwjo3MY8MEMBNAJau1w
+VIoA3UI/Nxpb190ikRFAE2a4wcSglSaSApdi1dyAOhSaQRsodLwHWGgnR6hSh14DeFxGYYAKUWB
0GGieIreaIX2Be7i0NXVCmgRAAAsAxUDoQWrAD8b/OOxPJUq0BEis383Od3HqQUJooF3HsywbiwD
S7e9wm5bikQk94Yd9v4TRKzsBe1zXuAY2MCSjgR53W4/06MQENKt++GKgKgI0Ef3gNE9Rw3+jbYA
FTSByN27jMe5W+9wlYKcALwqYlmWaKgFW1KM3ouo4OkKOGoNACcdVTvbhCUCyQTZQ6XgOsB7UQfv
CXxQL2uJjVwQA0AdB0Zfs9fGaAlXfwYAYHXBJjTGocb4wKaDzm20heDmYgIF9+cKgqmfbKpKokGF
+cq7RWCprWr3ftjgDQeGI+EO8lSCR2l3zvCoIChrnDaSMHA2cj+sDS9GLgm1/vBtTA1reOjSj2GJ
CLegZRI7735wbVd65tx9J988Q115++RVUw8ZWSBzs/hwmPP0Y8Yhhi34xcvrP5xWYJHr/wCFx39N
XVcq81+gF2wxDWtXkyGzjJJe85k3rBeC/nBDDTxpxqAky9+OMi4EvWVpBN3WIjxz5yvZ3rFU/nGm
ta3gW+s2UPvmiJvWbHdswb03rDaDxgTZOxd4OBeSwN4prju+DEgshRvnrYfGMECACtxsPPvEkVNF
2En45yQ6WOjhwmLyrm2bVV9c4p1Vwd5Td++DB2WgowMbV3yn+cfbq42RvBF0GBBvkg5xBtWJ3jAs
Cb3JlENGKd3ATZ1IxnjGWKmgEXyv+M47aB2O/A94niAl2rvzhSAw1zrBnYISJCeM8Ip7uCOKTWu8
TVFbXj94uLs753rNm6O43v3loQW4zj7YTTwavNwxSHR5yCdKbcQXPbnic4/OvnJ5TT30/Q/+ANfQ
+33xE1nHw4tM4N95d8ZHjHx4wFyYF+hefGLQ9ZLXIhb1m56wJzc5OQGxcScQxPHWS4KInOV/jNtZ
dZO/dw9Y700+3OBWfxlSzWRlmjBD2kxrt+Mni5wZwm/nDLFoZYzZ97cAFBdKnfEyBKAFIjWvGKko
HZG83+MBeyAsdw4/UPzmhJ85sawC4s+uldY0Xv3j9LqZKcmtzd+cpHwHuXDYUAU7cII4NcYC3w9c
4iBOllwIORrS4JcAg7R7L3k34WkJrx6cCIjawlm+98cfGVIRDVdtwo0gOLrHvRGuMoHLUvb/ANxi
QMkbPeAEH4HjOShpt8fGMZETThFpOLePtkpkZvvIQ7Q0ecdmzHUzf9Z14n7+ij0Ah/P0n0MRXsUR
4A24ajaHYbBOnWzrL2UvEi7hepoecI4ImJFEKN0TaY0iqqpPCgz7YPTmhJ3nLiWBuwFQsFld84oY
oSOqMyXgzZtq7eAGvBTjneQdYocgKmBe3Rh4gIjYFH9mdZO4wwCKC+NrJOWfvETYOq7cQBLXSggg
Alqc5AaCxxT1+cfxrYIErBbGAnj5wgUnkJ+MgkodByHzgEFZVFDxjvEhujknX+MgB0Ma7w6AQNkQ
cdA32Op/3rJ/sbtm9AtsGRA1QYfswY3rLED75zmUaEVcD0p7nGBWdu/vgLrIn2xd4x6ko6V0YagB
I0AolOSnOaipEY/Qc/jGFqMRyJfWIhNY2BWnkXV1gbUG2uL1rvKVlGhABDvaZUc0qECr+B1iSMaa
hGOvKSLqYwND+RwO+Dzm05C7xKCKOdz8ZSip0nWBbVvjvFx2N/fEdYBgDFE2HDjkYI05+fnNfQWi
iIBE1wmIXGMg14rPz1jmylWLYAMqqga3c64I7OsgxAFaQKySaFvLxkO1ktAWxO1SXjAdAic3dcZA
Le/nDEkYg4QxCtkFNJpZQF14wMBUbzzmhJx2GK0Kjes5ClV0FZ7Cv2cQqhWRxIsE8jcUd1rUxSXw
/v6X1kXOMNiDpGJ98MT2aqX7lcUuKFETkR7xTzYMGQVbMDXYt53i83p0Yum0W3qdTNz2KXRyvwj8
OFARIuBK7a3xhud3O0BUdGkIgwyAqoASeAIIx88uWL9RCgpVPMYUrvFxNGGaKBhomPZyezJJPs1A
8pF0POjNSw3HEFmwAZ198A042QMHxllN0Y5KVTzGFK7xnBfU2TeuYH4xTFYFQJQApCKq6TCttAQh
I1qgKefeAa49GhhYIArNRTyCAsIQPglsIlVUfWNrMoILL9gH1k2SWAKi0SJDOAwnQPCCQjQSkDwP
VytB6CjQijHYXoV1zhj0OFBCkEIC7hdpjEgzcMqKsaVFJFmMLhFcBJGCIGkWnnBwixsArqpVO5Gz
GKmhi5lIl5nFZMrYIgikHSWgXzja5qkQohUCFNLK8ZOkHi1IBpRKeOesH1oNNxrsGgoUUrNTzBjC
FcjsGHVmRPTAWpQFQkoya1cnhwAWgYla8rAXiEqYXQTgUdhBWgc3AWEIcFTTxY51phSzEQF+maBQ
KBDeDtxIYBJ56MhRUeUqR26kggEcxgMXc/WAiIci6JKNN2cNeZo5QA3h2ROAgHqY1TlZpDOPFHA2
OMVUK+RbnhC42xSjZzrir6xXLt3gvRQVAo7vGPQBWoxsJApZdWamWB1SAkpVPMYUrvHP56YO3RXY
AWU4q0uVBxAWphQvHBUzj/DwQ18zKoaWaQkTgq1tXetYKZYUGqCKCHgXaA5OZBto2DQNcQ2aoYGm
noBhAA1pnvS7x6EZCijoNFVXFUOMciqnuB98RkPIpi8JC0jteMlulYTwQjGAvpDnEgENREAgDtbu
84AtHmhQEllUCwdm245QoFUhRNgAnBtebl2JZlQGpoVhNwnC0Vi6I0jhtLTnU41grUGNDdUdMUid
buFHgJSRBUKAFCHjBU0EigJUUIPENhiFA4WECM0yC7VbbHK33MYuG5y2jtMOBWo3R/vrATsr8jkJ
prxMkD0/vDw/RyYYuykIdJsBugeJxjqOUwdqvKr24vjyBCqoHRVYd3FOAVJF0i8t7uUDXEO86M33
5x3KVQPlBmUjQrZVW83u4LSSqS4Suk8mFEM5HJaR3ve/nBQCxKiIhvhNOIteC22JFvhDXGjxgpfG
QLDGclDT68YAc2RuJjfB0bPGaNQJX4VZmnghXA4KtmTYUIgERDfCacRo2DsCiwfZk1Q3Triu9sJu
61jMBRIPAq2QNWa4xIDUeo1pWjRpvB4xFVFsVeYOi9znNTkyokYGiijORfOejhBUggzixS+82ZzP
fgLDE0U0XKk3v2OO7hGraORkEq6PePVYaiERLbIpOxcBAS0AA5Yl5h3lBJeeTaNfvjiiSqjLEWKV
212+XAgcCBDZheDaw1v3hFhiOh9bSepilcriXkTjFyBRhiIgmyKSyKd44BaBQhSAyh3yXIIqcIht
V3ssygyJq3Nqt9uchHZikorpYb5wtMxKj1Vn2w5tBj9W1nqzEcjVJaCiWigxuwy80rpjFZYCAQDZ
5XAcoEEG2AJCq67XzgTQOOvcSyu3INLoQBFGpAI6kzlaaYXWk3ldqK1bVU3Squu28uL5zmQaqGu1
5vONpzzFe1ryuHpA6EQiG+E0mCBMCRBADYJOiGk1ibgWmAhMAAk3VyKPCCoIhF2UH5Dxly7FJolq
1KC3wZMTtQPa1Rdb3qb3jj/EIiIitN7p2YwSqzZqiUu973fOKwMOdwmkb0uzh8YXitIpoCJ4Q/ne
OhO0xUtVXlXe7ixVwUPVDXrnEYDIlQIbfB1lLLFCCRF5R7vOU2VSrc0Mb+8hDtlnPbw23XbctdAJ
xmzlt2teLcDFArdosadoLFsr5wRSAyAsFaBXRJXziRDVIwiCtBFJxFOFxIAayAwKFgpBZ0dGI6A3
JOQvANXbWeDD208AyPW85IaAAvC8/MzRoONjut/hvOHzlFxzU5zrATFwKclzY+PoDy48469Ge+cc
3r/GAr4uKcXIb1g3ch7yBUZlJJnC72fvGgZIqqc7waATbaZRcHAGXWn5MVzkY+Jq9OJpyPhzk273
/wBco1xPWB3y+MJLejfjEBzFOnByUZ0lw0wEi8/rOQNXYkUOnDI129uVsQjdd4xiiO5tdTR6wdgJ
Yav94AEqu67e/wDzIn5NFcc5Qlgn7yGlCrXrOXtGOu+ZjQKldAgDQ5djZKVU8R7x0sIWDzfLznAo
N8kwh2K6OMCIg15dL4xEp5Nnm8YNKhFB/wBZSmgbvhwEQFOR95sI2CdYXU2c/DgikbqrefjFkoB5
i3EBWsi+cKLwI5KrpYp25YaED1d6H75KNVhNge/nO9tGvLy4Uvvlrb1j9gTQQ5jvzg6ER2wwe+cK
vk3CBeHfMwWW46cuKtRXRirh2CInASdhjsGgO7piKqLTTX/GSZola3XxhiCgtQ6wqL4d+XDU2j3v
Ot5/tj4fpL9d88mf98ZfnLgjpK40gEMHWKMhMvnjKez53ghwb9d4F27XrKPNDs8YXwz1j8TW5Mu8
uUTVpLxjgOAW8+g5xIV/TDT5Mj4fLvBO64KY8jz0TFxyYJ5c0Ic+cq7r98E8o4KVP1hqP/GRVJXC
OANRXB8tTw6ffzhjWiwsW5sCgozff95oBEN+3+8RaAxLVx5UBo2V8OBUQaHc7rDCh3HGh/Bxl1Uq
iDswWpTKGqevWcwaA+PWEovL8TCCA+feUvJPFwJyD4djg60NNQeL3hFDgRU4MQdiIbt/nEjyNonO
sKIivTi2N0mMAi73uBjXZHW00ZWm6Ka2/bBYKcOlrVygKQFMH0Hx54yvRml2cZad04Tg/nJ5FBZL
98HUARUjetZAbrdNfbBdcaq8/H+c81gcEfl5x2kPClH4esgmtBbRecg7CbLoMUAoJ+82Gm3bigwb
7t1g/vJA4xL2bP7zpn3zU95evoTiqVAAKqvABV8GEFBEwlUIIxpqJwuUtpW0i7hepod4B4VMSKMo
LRNpvGmNdqk8UH9ZN9Y3lydYoh24aylpgqFgsr0OPJKlOKM+jtNi7fAOPBrjneGzwcax6QrhnqQd
VWGBRFY0Aol72ZCHnOBQbAILKDtgHlTL2lpGff7YnMrg64JjgXOXj8ZxsXxiR7OTIzhXfOBQAJI1
KXXG1h4xIo8mET4cAhtvrEVq1HrGjhXpMQI1TIUHZ4wyFjYtj7w2BedhzcgRF7Wc9YJYO7Yk0muc
aL4IIUfLgWUgqx6H/eQgiAPD7wA0TZZv1vGefYBET1ihyJzesuKIwrHKSQq85bZ6mU1V6O8cMtLS
KMWKU8GElJ0Q7wDUVlXejKUTkAQ6cgRsQvGQLVWL6cUhaJo7yKIYoBw/HzjEMJC9/nAWTlDYqAjw
c4OhNBoKiXvY4Bn0otOxQp9sAjQpE69o9ZJqTxSr4/1kMjddiPOKdHVwAag1o56xg0Dl8Ypi1XAj
CpdrF11wzcFB8E++LkrUGdHxhlqgWYhViLwhjsX3vAElTu4Go495W/bH95zDOG5cMRcD1FFo62vk
1lSEMiSE6AUDa1XwKGGCijpHh+kGSII9EDXYq87xeaU6MXTaLa8TqZu8BS6OV8xH4coBmJQJXbW+
MIxuJWgKjo0hIMMgIyEEnqJRj57yvt6EcFKp5jCld/SqoSAwhDElFp7MKldQqA+RF0POjNQz1lwF
mwAZ198bpjaQIA9TJGT2aRgTgq15XeSN1LTsHudYcAgxSAgQPZ3AHWEXPCUopbKvCW7sIMUHhhQj
QSkD0zVwxi1CCjvNI72t1eshJoBNtGUQiQU9rhxhEAFqJdkUhZ3MgS5FRQIUVImpBhhVIeGlCNBK
QdD1c1t+pIYNdi3nfjABYlILNb5gGIFHgXAdTQEDqN7uA3jgJ6JGF1TcIJWqV2VoLQUgoCGmjvOS
meZ+sSKCHSgZvY7BrCQBpUrVgLUhl1p6A8CjuQVoG250GP8AhaYWk+K4kINQoi6SEHRrRmpYiCh2
OWNChdKzEjavSArDaCQsoM21jMXS0AFtLKu7xhhB35uEUgoQ00d4jBN8FjRCktiu5vEOpJpKwpKK
KhLoTjHbKaKLUPpes4BPGopIEVKcEHWGUe8cwjQSkDwPS42jgo1BNlV07oaIExSNNJIE5ROh2IDu
XAD2ldUR8AkF8p1mil6gpEJIUIddYKAQMmUaiDkK2tPOIoK76G9IN+Fs1ziJcpKVCFUJKM61cPIM
00MNVCVbOoBLlCAoUidbboXaBjqJCQoDTf4xe8Q0VPByANfPO8a9MafQBIOxtIV5M2y2UYQoljSs
prccdC0AoIQ4ZxwbmWmNYkCA+AwHlk1MqKMU1fxvGNiUgSCsm0CuFaWgEIum0W3qdTIzWACgaLYa
3Et3YY2oKpCT1BBB0aYesYDNoUHY5asoXSswJAFEOqVlUIBZqyq4XgigQCPRtPhcIWzgAgjCCIhy
b6xFJw2+cBWUkNcZalfzgfADfxgA8V8+P8434GHA+H8OJO8/eTHWsFjVBEnko2ZNADrg4Sun3jgO
VyO1XlfeXUuAhqoDxtXFHIKlF0i8t7uXTlEO82pvEknUA9gxxoUGqSaq827uAzgrJcNOn2byRB4I
5LSO9733vBgrEREROeE04JeC82xIt8IQ416wWDGQ2DGclBnFDxgMqiNxsr4NDZ49Y2kEavwqzDbS
FWR1VWGKZEtIMUVqKCj4wXUgoJ4DerWzmuKLnqVeaCG+/OWPGjNCqsF0KrDVV7wHjy5+ArMtSZ3a
b40O/WG7lFqQAHkAAPE1kXxD78FdcGE8R0J8CszhHBz8BdYpZJJRdItqPdyqNqqXeYLC9wzgzlT8
gS61g1MpWhAKHFQBe4Z1+YyXexGY5XQJTqictxBLnH8GoVqEdC7Q5xrhIGrSA04I+QtNZUQOAwlQ
IDg2qtIYojA1SQihBaKrAPeR2cKhOILD8YPGhICEAbQDQHWsBRgaAILXadZNQMYGOtrPVyM41BTx
VVXjvBFZQGHYWDOJj75nDCqUseLfcwUHkYbhSrPt4wFdsCdEIKh41iByqkN7UNV7ftiGSwk8NJpO
NOKqYUg1RKbEUlkU7ykrSthCDOKDzzLgnU4S/MSvtzTEAFdDbebd3CQA60GxrspZjiVu6Drvp7El
+TVUKqMqARAAOA5cBDawQLKXSDpNlZltgxFAzhd7dsXz7x1i4iMEAbQLAP7xizCWqERKtiKfCneD
6pUXGuVRYoPMX3hv3ApIOhVvxjTCgIjLELtBZbK+XLJO6oc0C8G1hrfvLVKgHeaGb71hEoKkhWwH
gVX5VycUivwKRdlDXGjxh2W4kPiJh+MJFQBRQEAXoNB0GSaSFU6illPOb8AdABBZxiip6R3lZzse
ViY1N05Q63gCdmCusnxxQFLTj4c2lyau8GXI5GzJxig6MNWPU7CCEHdHMOfpHocQgT6RCGyoUdY4
4qUdKM1l1OMfBfvipPW3xgLRamzzgnb5+cRNXDQrJSMoaBruzwOUDJr850TDxI03YhTXMg5pzD1i
b2xKnT7wNyPYI+G4hoAMu6FCfA7yACtP1nXOPegAVQRXWtjOdYxClPGNBJv2WQfcFboBV4tirvyE
EIAFKi/jJhQEI1KCzix14mHKesNgCGneCUJziN7TJPk3MbTwtPJlAYWTjKphUQLyr0AKvgwEGofj
ED62H43g+JRUdaWHCK/rDRSJlGXjims1FdCq8uCRvKb1Ie+bjSgEkmxRTjyDPhwSgAFDTAy6JPLv
CDwxIheNYEAAh+xhLiDPiqdejGRiC0LZDZcNBoSNKC4IlQNDwvzlgRdg6Pn1m91DE68/bKuCedXj
rIyAa1dIbcLynA8n8/xi0KE6TpN8PGMUMpQZz7wo8AXQC+vziIpe9uPXgDem3w/znE7Ib2R8zHU5
ilmEip9Tj3hQ4JZyGVBBnE3fWA6ofLm01Xm3hxZ2SMJZ98YsdnXnGq137cRI8nGCBh6dYKWPiHGV
07wSzXYfpwdvzjjJXvFugckhrjVGidmsQchMyElmqbD441iFKVSggUAo1U4Ay0FGBK0pwKR6F7mB
wHY04KQIGi0RejJfCCcJwRUYqXRuYyQTJqQlnVZhSD8JZWhopJ385T8YgIdjljZQulZguAQFhh0q
0J4nzgSUCAqGNGrsOsSnaaAiIQaoUW3jANgPFhChUVrrQbpm/wAklgW2qSMRK7MuuvZoFo6IlHYG
8U4tYSF2WipQUTgzj5FcEktQEWEt3YYM5SQIjHHClyTYGQsUTSouyvvCmErjIGhyZVgL6wh42hik
C8km1k3iCEigJSOtCxytn6EcFKp5jCld4RmwSQL9WKlSQNTKGApEFu+5StDFrMAgqRAMezyi7/eF
CxDVlIANQA7BxJ5tSEjWx7gpBphGDwWpYkbRHTxxrEu1JbwoggSBAAG94AWNcaY5OxD0nlkDyNG+
D8TrpR1j1IhSplTFkFOG74JNUSdQ9QpABeW7riIBMK4EKoB2x3u3CBApQCoytIit1ONY21K+w5vC
X7YQBPBup2HSCDg3vCKBAcJ1/jIas2E7epwEBDg3vEQgZiiEomwAlA2vnBFPWpW5GCw27GQfGk0G
IPAFPCZIbBNXYXR+8heesQBDfTgELYAjQd6wlHyJ2f8AeM5CAwsEdzfdw2WDaug3yveOWyA06eH+
5i0aaB0KfaV7xQMXlGeuMoeEAm3595GBGG3rBENgrBo6g42lQ2EDFENgNDGQKAslXezrFohLgVKd
x84ZKU2rtDifoMLkgRJt1/2sTY82nj1lzSIU1bkErvidYivagPMPeBsV6nWLYS3TvrGF1Adt/GUa
UXkytppxfkmCGnnkyJONRN7xfWIjuqj/AD9eOvzm0pmiVtJREdm4ij5KY9d50iIs8wC+sHwgBBOK
jX75rR6Iqtry4Xc4uENo0Snlh0vc5xqtaX/FVdZErguDJFlIR51kRhCTktI73vfe8nnUUGeKh+ME
IdltCQ8hNTiawTx7pwSzizV5xkcMbI8MS5yfxJ+aO/vgZtgAFag2gq6ygF91A0rsoMdaMvBalK88
p+saXxAhWoDwVWHdcJuIqCdAS/fATUCIeNWfrNZ6S2TyUbMU0BWKShXSw3zrBwSACFnz0+cGSyHR
EiFeEo+tZR5gJK82pv43lweBHtb8N713vAg0AAbFt0rte+8voU0aRibEdl7PGGEB0kLyVwB6cJgr
au5WXivlxLdUGp4BhznNNaMaUFgsNm9GLm4uUeVXauIoQ1oBIbQmoamuMMplFARIDQwN85pgoKqw
ROXpBPe+cGIoIFJaU73vfeGioAQE2UNMd7xvXQtfIDDvj3iaQnRaJFvYhDjR4xi1UcM8Fhz+8NaE
VDtQg3433kGJoyAZACCqNVdujHJIW1pqmFV36AOjHTF6Z4O3ARaHhkboib04iooOgwSCjpxPd9dm
D5EgnjRHpG4IAYWsCfe9ZNcAreV/7ePEQFKAW/1hposHmF5ccYEBodXyfF3+ce8NCfr7f84lHIe3
v48YkUS8FrMgaNtmt/8AXIIdgNc11+cLohDYF1z98XRwKpUHb+kxhjoE4fXnzrJBvb1m5v3PDlF5
0b8YAbGv3g7U6Scf6wBKA52YzXZuT3hFWgmy5BgVusTVmrPoZfjGMLKc/fArl8cZDm5d60Y1DPLr
HjfGKr25R00m8ab/AOM2rj/OOlzuX7Zug+bjn31ga27e7iz38YLsWdXlxp5Xz1gC6fzlmyuucAvK
O9Yq4VdYu3jz3myNvXSeM6IpCrmr/GSjoDs/hiujRnG8Zhgt1oxUCJmzRmNIK63munS++DLVH4Mk
d0njCKb6JcYp5H1M93Ga5PLgCVz6wKUzwd4myEDX3xVXQDzz50fv3gD2EIbXACoWgGt87f8AucpV
ViQU9ZTFV54TLqb07wQB4aO80VutB0nPHOISTRg0Hi+cIJAs44hxDLVFCBw71eNf6ywhFIKb9+/D
iFArAVDy/wDTHcyO72Pg6fjBRBCSRo5cROuAXl9s694piI3HQ73kRuHUWvrxl1NyHl9jEEUIahXX
6xCBILvQn+M7YEAeU9vfeEIKvI3Y/wBODKAtW35wUbjo9HnII8qV7fGJZyLzoMQgaHb5zZoRWcPH
vEaBkl/xlqqhxQ5yQPz1lOrT39BmT3+so7qq/Tg6TOr9supnLeCBsfn6W5gMvK+MEK2v6wH7NYuC
SfvGMfPGHI4hkn+feQqb8mJft3k0qjMRNV95ABNnLl4Q55xHsv6y6D6DIzRzMEdpB/eDBrbQOXAN
K8jxPGEki7NSc3zm0OS6XhMTQvD0vnCBLeHlP8Zw4a0LuZzSp8YwR1N8bcLad+85IxfJgyQa6HAE
Es046DWnCVycY0TxessGnkfeBEb7TvJg4AKafjHiEK2w8/8Abx4ESKNz5/GIlFLDNePDgXJBqqAu
MaElHb5wIECdPDjeMAAHFbzgoYA7Q0nd8Jn3Ktce4hdUifBiRquVXUPOdJRBbtMJZEwSLjpRTbw+
i84EhQ0+P/P6y7UAqTncv6xIaEQytt/wTKqVgcCX12YZNoCAz7/qZqlWnaqTxcuKp3Pt+sZtClDV
PE7y1gRQXgySajSc5qhwus0C2c+sJVhDrVyYo2nHrGAKQejEDXjYa4xUAoPU1jLrjFoa/wB4iAm+
MesELsS/hw4fpNXDFWLygABVV0ACr4MACECBBVQRiOzY6yl1qwkLuF3JodpgtEiYgUQoLRNpvERR
Vqk8UGfbKusTrqcZtqC9Yna7bCAXS8u9Y6kqLeqMZjwnJ4xqEqxb0Djwa453lbV25w5d5t3ID2sM
BUGNpSP8P0op86Poic9dYN1y61lBQTffjNklXnxlnMikUIag1qfbISx23RS6IxL/AC4AlS0m9PXv
WFj3IMKBzvpfOWCABwn3v6wI1HEVeQGCS0Nx317ciAta66uUldqZU1ds4/DhXFRWIAId7TAWzcK4
F0Fcqnm4DYc5UyqhOLvESbVN67zYxakA/wC+2AUUPPF++JhWhPJOeM3gm36AVd9w4MnOERQo+brA
sBCOkCrqSDu64yjoBR0+/bigEXS998fjLIV5B/X2wy4U01CAg1o0zveGSRU3NzAkFdNiBZdC704g
goSOqMcCSYm6cuCOYOrEVQ4Aq8/nA0Kih1RKIRTc3pN4LAdGqChobiCcVzWVAKcJ9uNZfVQiABXf
d1rtyVqCI02ZAOt2KjrmmLEKoeg7jhBGh2zQvhwIGA6XyPGFCoXVDr1iLGw4uCHZ0OWF1rmmArug
5jghVI6HmHnBKJN4Tv5+myvHrzgVh3nhrWCAzSBD5wp43gd/8YleD84a2bmOyQANEkJyoJO+MAQv
LxtTdogSoUgdpANARRpEdieMuuTICEOiBrsVeWuMMCmQy6bRaep1MiRIpdFK/IfhwoVSaQJTy1vj
esPh+h+gKjo01IMMYQQgIngNEY+eXK4fsJkpVPMUKV39GuCgQGiY6pyezBYDUKiaDcXQ86M1nnWc
QXsAGderizxLRAgD1M2m8dQ7vvSZABKSmKLVAhR2xesQ4t4aF2WiqoKJwZt98NAPU0eAR2YyBHI6
M2oVIjqpgAgmMjJZqmw+ONZBMKvSQIAo1U4AwuW1mw0g0JKh3g30vZ2RzkagwHS1028TeoTuvKgV
OSOj7iPxhCHJDADgowaUOYe8fICIHUADVK329ZQEFGoAUNhrboLrnB0NyJCIldBJAR5cIiEoTebU
LQUetMWyHcIgAiIbQiFF55w0oOGxVPHjWITQiQi6bRbep1MRK2DYCV+Q/eMXygbHFEFgEd3jEXCw
jJEFFV0Oh6TUA4aKAAkXbFNgtMJRICKQqi6A0gInOhYBhYEATU0gKNdPOEtTBeQWgUsG7EeMNaRl
rKwFEt0NBmk0NeJwACIm0hvzjyAFaUrUfln4wVRLggRONDSzmeMsH03GAFAMCjSh3lGzrlMuQXsl
izebFPwGhm8iF/tkyDkJY9YiKQb4Rjs04gUx9AsLboxTgyIlU2CgCnAnvEUbCQRdCDVha28YU5ai
oWiQKYXVnUxKIHexXCbBfnmArPJggNA68Z0sRPWCQBHurIaGocCQwRJc12iLCXZlTOQ0bUG4q29r
RcUiED4D8pD8piCAF4Zb/rJAF+ZJP7yHjZfxkmaD4whksFJ3rWMGwV5pigVVkAzdU60HM+MFhrzz
wZpqn+MdUQAjZpyz47XhfWVDY1ggQBe01+esYdeBmuHvKUd7P4c96mKvOQTcxTo++K+GqijsTjNw
Ue2HSut71i+RK1TtV5Ve3HkuBEC1AeCqw7XFK4Kki6RWomkecsG+Id5pZ86xpI1APKDPH4xeaDex
NVebd3BSSVwuE3p9mIiOG5JaXzve+94ITXsIiJzwmnNwrFNbEi+w1xr1gLvHhuFGclBj4PGavUDc
TFfBobPBi2oxK/Cus1dPbKHBVWGKAexgiIFkmp41hTFHbTxLJ6mVABSFeeU3j6XqyPInGMBsmIEQ
bQRiHNcBFujaEAs4sAvOsMAIB0nFRrPfGcuM3bZvbi7nFwKGyBRQCAXoIBwYPwg3ACANoBoBIcYv
IlOcW0EF/wBZyNBJRgKq7HLyw3inAKoolrajDT4wC5WCQIEsk1OJrNz8vm0B3jhvliQgFDpQC+jx
kDMRBONLNdeMUqJU05GJT1gDCaADzQxvet5WTjWGIjs3sUTsUxFYqiMe4l5w2W1atuzava+ebhfl
DaoMS1KDHWjxhM5NyHFQgkJZZnOEjMOhiVPOEmmNtV2iX73nEIBE2gWI7dsW7XzmpQgEW9IaG3Rr
b5yeiQaQnY827uNCiqAWAqrVALzA8YQVCjGAANVAAl4DGM/VVJ2tX75pwYJiIULBQNm9YjndZKVF
Etag7vB4zYgFT3UV8FQacw8Y1pheAjRVRobO8DA8afkjXEALkVNqIu973d4whHRgwk9LxuPWcTaQ
w1bG7e7bnGoAB+UHeHOIFkBAW1ho8YKKcArF6Gm72jLjjANBiqqwFVVQOQNBg3YvRNez/tZDo41r
xnr+8VwQdk03iZtKvd4PWKA+DEVqhfMD/OM0NHqtcHsSCqcidYvoahKpjdN84kkTtmUYb751iLYv
B0PjELQE57+M2L0/vNj8YlfnFYHXf/wV3cPJIeHGUfHHvKHGvOs2gBWwDvJqkCqm3Y2E3ZPeLo6M
gYAeFXQfnI0cba1HTSE205OcHFuOOGXsKifIiPxgX3gvM05K5uA4O+MTl39CmzkweevOI8OpPtjj
ZXgMGAo+v7xobON6MLVKPM1T7Yij15OYYz6DROT+tNw0V03fh9f7xYh0lu/H0kL54wFZkUeMFQlz
mkDguaCQGnp87zUBTi7q3s/xhUKiNPTgBQqAvA8gd7M0dC8U794YWHknCzZgtFGEZEJxMILYnWVs
mcPj3lZFYbvWRxWG2b484RSpWiTeKC0AbS0ZoxVKtXlySLd4jBxy+Mp7V6psLiAtAarhaiXqsLjq
M9I6yKKcDlEFEgffn1iQkAaLyEoBw95swQUoVYjhx4G0BVm6YAughUl71jsUEIX1pybKI3j7/jCt
ogXSoPD7zgC+T1f6wCIK8CbfeKqvTdNK8Yqtarmi3bNb4xVnQxXgzfACwyqWzdV4mNPkE2YCdVT+
HHThBO+vp+mAQP6jCE7judyYuoqCVi6KgQ4qhMtPDPDaLQaEE0XIkAkiCoytIit1ONYpANa2yJVV
URRgcGc7cxcs5tE6EWheIg6L2BAKkQdhrjTgayK0JACXQCteCOC4SARzgaCYUO3xmxjZBMwC7MNv
OucDUMKBoN1VOA2RWSSAhJtDo3kXBQQCoytIit1ONYP5FcDz9h+HDwNTnETDQtd6wKhiJi8JkwUa
YRFauDCju5/eS8AFor3na6DbH9YqHXjrEMrhevZib3SROEnGK6bRnzr/ALeO6fDm2Hi46OAeXNJw
OW6ySMVlefaHxlgCqwHyYFAQijXt31koSCtvHHxgUo5Xr/WFBEGgpXdc1dNbOvGO+gEijudH7zjt
WK711vEiJztf1khKDajK+MXqg70Q1iyKQ7fJgK2ReFmdH2443nc5wDaI4t1hCLm1/wA42q/HGKkt
rOOMKpvJN0LHsxUE2PPOOIbs8YyKkhJzz/kxtEULz+816TZ3y/yXF9IcTaL7/jK8xd0GudeDGDug
Ro3TT1mmTposA/nAEUK7O/C+cJ6joaPr1gEh3vAUBtXRhoJ2HAz84NHAFvAfY85EWHCO9n/ayAts
OxvnWvHeO2p98GepP7z4YnHvLr3lpzvNYVFrQkCUiREi/OVydZVSylYBAgGJisUC5EV00GmAgGEj
ktPbe994TRAA4A45T9YM6gCiEAbQDg6xhNuqndeXhT4UxAVLIM1COhdocuKBBRHBlBWgws5hi7Pa
lwRtF7TnGElLVUqpvVVX2rj07FgtNS6aGzFCjC7AaC336fzgLFagQEgB0AAHQGMEe+fnErvTNLNA
p9s1mhjzilNtxBHPG0ykoMxA4b5wvWCnxjqRON4KT3T3lLHPOIKO54yh3HXWX5X2azStGo9jnXI8
9k+cZFIK3WsOnYbg9X95wQaTSz5/9wAYpA64m9+NYQnqCa15Nf8AGQAijZKh49YqqjdRSnTloIbb
0P3+3WBFga3Kf4xlcPAozGSJtgovrEXWS71y4c9kdf3iUlDnjn3gaWpwDu4cBZ4x1svgTjBSUvN6
MCCk8n9YiYkkqYIW0ddOJdI+ZfziDxVfU1iBKWvGDDicnvELFQG5a94/wHdeDea1RTgdK/5yLsG2
KQ/7nF0gWgLD15+M0GBXaV8ffD9VTEBZ3z18ZZsIBVht5s7yQoJoB5vvCAJTTNHxkCgIG6hleynC
mn75Y84RUsvZ1m8JoBaN7+2EKbEHlfjIAlEnP58YiVpUuzHwn4wnpR/Dg3h4xJzjMq4ANpgJC5Jh
VwGzFbvnrKrxmk0XInnIpcmEAI1MPYcGqwvRiVgb7x0zWvpLd13nJdcQwQEgyfJjvi1cUudzz1kX
EKQPfGDYQa8HebEJYe8lg+W4ijk1cOpN8X+sK1ihJpfPvNLCuxnK9mADowqcVnMd85AjEZUse3wY
S7Akv2nFcjQl6JfxjDaCu0P4yvp3oT1y4ijYl8j7wnyOg7Ts77mbYTZVsPj5xeomI1X/AL+sChNK
z79YjyCtwsFLu5ZCqfrNiPGWjeOfeCgF2uh8Y+/ILfPx6w1FqeO/iYsECGpx/wAY1egWOuPzjSBF
G6O/AZUAqyyYsDbz15mCalTvgwK4bR7Ll8liELH4zwZAFUnejy/5y2xvtef9ZVvIzbNPVyqoRQLx
vjF6kK06mMV8Aui/04ghi7t1PO8EqW7u1ftgQATS76Mg4ANtkPnKqCJqtYesS0HeU0fbzlowD4uA
aIJwTA3Z+skd7R/nDXziO3AXExJg4vUMuDG+OMFR53nI+uPWNjPPjOSvPzl1PPrL4+1x23Eee/XW
bW4Bds8YGSbcnOfZs76+jg9dZAsaH2cVeVbkK9/GLY2t++GhAgjTA552o+XBEq7OPecp2/Gs4Qf1
hISRZIvznCAiIyA0b84kdW1vFdZqgoGLz1r/AKmWLYAV3w4VJRWvf3xRL2d8HvEiXa+PxiHsFSlJ
85Ma5LtIJqB9rggbLPsXnNgFgUTkOjffeC1RAEgPdmDAjXIAQgO15wkJL36cJanbuc4uoXzs1hpK
Va6msonGub/eagqA7P4+MFgtLRk/vEAaGV3q4IKxXWHY35Xnf94yBR20/GRGiPCZRGq1V/RmpbVr
OjivrWOuhAbwL0l8YuiqgjwJvjIIGkRN86+P9YLMQvOo5GwPVwCbi1UunCIlCHYT3y8P9Y6WhV0i
nQe8h804eR8fOBKbC2iV1EcqgwNK84YFJAHZN5YSJLqd4PaqoY3wPUzkdiAydOXDf95fp7XKcjto
E2nVETyI5S11bSF3C9TQ7cAsKmJFGUFom03iWOu1SeFBn2ykCXFpKu7goUZvGTZtQpCwWV3pyDdZ
TYprWC7kyqpK7fADXg1xzvIdk+m/wgONujBMhiNAKPzscAnz1e8U+jOp5zrIu6HrBIKkQ0VfwYrJ
VJUFd1ra7dYxQDc2+8VFG97xaB/7hodc8ZLgL+8RMFasKDQ0NIXfFy2G2qrCkE0spLpwCNAtKbT5
6DrA2ATZZB4+cfBFG8CEhvl2YJkG9A3N4nOqO6Pq4IsYnJp8a84thDDbQzz+c5FGcUsvvNGBDU82
8YhURKWi7ScZzDqMNRDxey4VAsKoktUIjp994AFgVdixtfvlC0V6R4cie92d+MGdQtXvNED2+8de
hEj24BpBvBm62YtUUAHcXMPeVd9iF7wkQm7OTIKGJGADZyxHCto23hfvgCbTh9/fGUDQGLocWvIK
TwYpKFsHlDEAQIQCCxQdshramEKU0ij+c3FXajTbOK9mmZNAIKas8ZNDAKIUyvgKvF1hFKtBuZ2X
kffOCQJR0KyfFxVRAByKJeHY7zgh6N7E807xrYACtpd37bxA0Dye/OGYNagbvle3AJAQ52TYeOMc
MgBYXt0GKvjjYzST7ZTddCXz84qcQFI0+2AfDiFuC/2w5w/8zrAeMgX65hFSFBYKFlm84i9TSDgn
QwmuQKcKOFAijpvf0QwQ1XsgNdi3neLTWnRi6bRbep1MjaNUaOV80Pw4hcUDkldtb43r5wzPwnaA
qOjSEQYZExQgJPEEEY+eXK6XowwUqnmMKV3lm5jkkuQaJjqnJ8YLHuhUD0hdDzozSKVRcBZsAGdf
fOkMTwMHwZbbYxOSlU8xQpXeKyTUY3sKxADinFWrkZKQN0woLo6qY1CkRSaF7g4qWPQEOxy1ZQul
ZiweGBqH8Fwa64ipRaGznXG3AxEQhLBE6SfdkJR5JEEjwEPtjdjVAROEi2a5F5yQG2AsUTSotqr7
zlmoIhRaoEKO2L1k+BgbWqk5GuRtraFAUedDXaBiPhWx1b4UgM4GYJJEoBTEGiKTvve8ZPTTAoRT
TuXoV1zm9psAqVA2qN9j3kSEBPex+RcChAhgEhTVUVCXQnGB2gCUIUCBu3MAdZEJAhqZSIPJRgDr
BiscKI1Cep9snR/AABwUYb35gcYjZLYEUADm1tu04mW8i0sokJyLSnOToAkVBNbi1edGA4QjCLVB
QUh0rlgiQ0hbxg1e07mRt+SWrEid2cVwkDq1GIkEHm628mGI5Q4SMRUYrya3HAUcOCoHW0AAOo3u
5JOrpQga4B+sVGKUqFUfkMkbZYoEGDVRiILZg9LpRSFo2iUYgc84RhCIpIOLetN4C65yBoEimDLZ
puJbuwgmARrShGglIOh6ub6kskTInBVrauBEEhpBT3DjEA3BQwECB7WwB1gZ0RJEKAugAiRE24cI
MsBNZqCSKNaecFiS0S4oDwet+MbTZLuQoRQ0gLa0842ZxYqIZeCKA7DWGWrOoA0JNAgo83mOJrPh
EAi/kb7w1IKgMQoC6A0gIm3KkKLTyiCigdLZcM4C2L4xFSRvCSlHA0PW8BBBqm099GcWoui5G7+T
O0E3W3f+MUgDGl+DD9b+H6a0TDnWcawnrABDFGiqK+DodYyjlMo7VeVfOVkuAhWoDxtX74o5BUou
kXlvdywY4h3nlN43gaoHygxxwmpAqqq8rd3nBbaVyHCV0+zAgoOLktI73vfe8mwVImIiAvCaneNG
rFbbEi8iGuNGsDC46BQYzkoMdUPGTISBuNio6VDZ4PGMqxGqPVWZpABXkcFWzDSaxLiInPCc4ScC
oAIAbGp0Q0msAlBpXBAYAKTdW4+NiCJRBF2UGeQcnbuglwCYT4zmqYYdaSJjSZpSltVN6q1navOc
xRJhBGlUjVeF1d4DEN/mgy9WYrbHZhYAs1fGTMkCBmw2kPjKVxqdDxtJ6kwJ4kOEQBGgCgHBrjGL
caK1VRXTVdTbeccTwvwRFLRoNN6wU64TCWngx3u7ypcIrtSgsTiofL5yAmjs2GiKjwI+zGXrney1
furjOsEwhwhYTqY5gFVh5UGb7844b6NJdNBm+5ziK5yjfKCC/PjImyrCKCqrthXlhXWOZuRkS8it
TWx5xETAEZRE5cIQdaNaMDFJY2ptRy0IhyC2TAO6qZCAwAcG6uajNJ0eGJcIgopoViLtK7by+cEt
NYI3BDo26PLjhJDbl4rWbc4XpQr2CX74kwEqWhQU4oKX25MRKSELFBilZeK4D7YY3xK6PRrH43S5
A4KtmDeIjbYoQ3OPtvFJtCFCqoDwKrDtXNjqCmPArMD1CtKFFFaihz4MIlwIRHAR0ItnN3iAuqoi
b0Ib785+1f3YCDliO8Wg5RFnvjEAgdhAm4TY1tusMLa/fNiV9u94warUrVXu/OMIJIJVbVbKy8Vn
OBwZDW5oDpHes2iHHfkCXxvNGoLDGCWcUFLLHLA03WecFnwOTziTqhoMP2h53iJ2aQGnBS8Td7vW
GUc6rh+p/eU7y9XOM5wkSpAAtepm0DtpEbDWo9Xi4N27xSlFB5ERBExPeP0JAtlZ2LVCJ2Yclx5Z
jEBkG7WLA54P2YwTrpkcgod+siq+9Yb3E1EwKgbfH0DW+zJwHO7jqJ34QpZUWoStPObX24oDb7Gj
FrkAOxUrxEPwcBy3XjrCweMROcQQKrxmyg0TxgkDVV18Y7lEUB4nxlMOOZ8uHsU7mrhQAD3d5sQa
c+8pDpdHAYippymaHNemYtHTzXxrE9bcPWRAabeUMS7e0dFpePxhRoLLoP8ALg4J904xBAEVDeDk
QVQLLIh+nAp1e55wL7PD6xfSc4kX0zHewXRla872zVwjd0nveWL0Nw7xmNqtDxOsY1tdTziqJOUv
WPXgheOcFsPP6wR0pd4IAWXrGJAZWvWsAhDrVwyKRpnczmoAKocHhPz/ADhJHelbyuNU0TVu09fb
FNAAiXt9fQ+W5CczCAbIvId4imonb24AAGjcTvBsOn842zkeTEBERplA0ha4V/rBRgH5jr5x9/RM
44xiSCpR/ACD9sWwxMBcciqF3/eX39wjVBJWna0ldzKYyEkFtCBFuKAbMkAieaQsNgDoVmPogEkB
aBAoQ8FyIVZhkSBJZF6t5jl+RlSoFZNoyppi8YCyL2FE0F5lepgYsMESQddCffG+HUIiTXOw8trX
NTVyogRtozYVKplnMlCgqEah0uhR6yIVCEqrSu0L0Dxlyx3eagHhIHeA+Pdk8oaDRAhqznCmJ/HY
gEE2EQZyPOQ1ABoVZrlFv4wiBUhQVZujCutBEwEzw5UOCUWAScN3YQjEYGgCZ6AvuZHJHkTCAjte
MG6bv/OPGC5Hx6T+8XWg2i865hy4K1jse/Z5xIfa7cEAD2FxKe1184jYXi+MMIjTduFwFlnkx0qp
SM3LmhQ5485ov/tl1WAsDdw45K2Dj1lDUXKxQcIQBFHEE0XYvDluw63W3I9sCBsDx7uOaOSnj2cm
BOkD3dYKItOt6w3VS7wDTDXFUJ4yga7eMXBSmzFsRFvBmo8moeMrugGqzjKbq99TFXfeCkykQAt8
A5FGXKun7GDwFO1y/bBXVyRKbTT+8SUgtrVQkIfzlUQCqbJ/Jjdy9ytZ7DFAAssRoZpvS8Hd/rBk
djZ0Ock08oaDLWIHW8GCBNzCBJfNwRYHvFors51zgL23fgwqAjhXFVHyf3ny539BfUxC3tPKSL8L
98nckuHQAwPWLWta5bzsa3vOKLh5iI27JIjp605vKOqIAuDSRqEEd14cBoBJARTA7VvE3yDVpQDH
FQK8sM5tSbMSCERIRNQj1gvSPgCqpFKqsKv2zQH0KJGF1RR81wTmRdKiDPMUvvOu7lJogsMEFIgs
h5KTXrNn3WKEGjVXnWLKciEtUXhXdPGILxur8KswhRqQfYqzCSaGmK2ruVl4rOcUojywd9pzgkMQ
VEQBtANAcGduoitdo6qu+NAHWLGsaPGqZY7BdGrjVsMk0/8AmMCAI2PM99d5FyC2efjKCa3e93F0
m8p1oPrLG0cXaKW3m5ugV79Yh5KATxkKI/vvDfUj0P8AeDye+c4Snpq5MGBYvjDpFFidYtMQ7C/j
N4KjQwDpb3lC0GoKnDWukeqes3HLVmnXAmE5h+Pn1hIeeGa/9wQPamA1pqWXWDG3YPMfxiKLR1U3
gFRBFMQ15FxVVU29mKoV0GpjBjY8zNAQsroPnJ2k5Ipz4/zgIhjLW/vNSIUCbd46kRNk2ab5xNkX
bET/AJxLBDtTT/vNMtQdeeK+8Q3GrPT/ALxCUII985bAF73zg16DLOJtaacgOEe+7iI3L4cTgpR5
7x5CrDaGSQ75+co3xir/ACZJ0afw/U94PxjP9/8A5iz2fxhq3SveUnvHWlEDWGzQIXnNA63l0IhN
7cUlYt4yIl3kgOU5Rzbo5efeSTYu19b+2APEmx5vrxmq4PGSgnHjxn5F49ZUs1nXv6MMGXTh2rQD
Z24FPfN6xopofrOWNhFvnGKBvWLqij+cBgzSXEGoFF6neVAg1ojOn7zNyxjV+S4BUQQ58H941EHR
uL+sSAuhm6eHNDRRu9J5/wC6wgCsoJUHuecFQXkn/GKQjm8bKKLpn6wDsESt5yrYjCD4yQA63cZQ
UQZg6UTtDNKCEapp6x06coB2p5wUppeFD9YoBRSCtLYD53jNpLqnL2/zhAd9A7ec5Aouju4bIhdl
HXvx85XZBpN/bFEbXeVKjLL9DWKVUts5pvKAN9twCtQE5lxUcH8rgDTavN5yNL25sdZ9rZ/D9J31
nH9Zt3Mcd8fQLnv6GPP1ecHeAI8OCBycb+cqHBHrL1/HeMOuOTFA8vnxlSzWVK8ZTDZeA3hW6Vu+
HK+lRJYq5aJfVxX3jrGffjEVft9sBp7zmy6xIx1g7x9ZsXWNaN+rkCa3vEjVRannBbRJhVV2vblG
rswJ8V3vKqIeVPZ34yhTtFd97/7eKRoiKeblJFSV1cAEhNb2ZZ0bt1xOdfjG3ypPM4P11gDMitde
cobAbRCBlRtHidecBStOtOKhOBKcYIkq9wLkw8hSFP13g1A4RIr2uWqGM5Hbz9sJI0hU2z1lKYLt
I0ZZIAO3+jBVF0acBcvTavnvAYKOlu9P+clwoGUs+3nGorrw3n1MYPfQ61v485294BNiKlySF9XE
mKalqYIQQQgPOJIRU5MUQZrZgAVZYh1iDwr0+DzjKwvvDfxP4cjhL6yLvOCb3mo92UC9r0GUEBIi
9mhrLS2raQu4XqaHbgHBVYRRCgtE2m8WdV0qTxQcJnswhzziyhupUBUFlfGPBKlOGMy6x3m9du9A
NeDXHO8Gf1lJMD6kBYK6P3g4gI2wKJfkcqk6N4xi7xkRLQ3Of5wVSIrgQWLHbIa5TKkOfGJ9oFeb
evjHsMC7ADXe0PjAOxbeELQ3HfvtyAU29q5cgQKi0KE54HeH8FatOqakKtfHOEBptNZ6eOMQ4aYb
84uvLeck5yo84FQm/WSpdmzAC2DnDRQEK7OMI8QftjNwvi7xPBRNSG+eMuQsKVhFnAQd3nWJq4wr
qV2EdE3XsxCeEDWq3a+sbAXYNGdgY/jznjek/WDCK2jlevjNgKE5dzCQBpWUN8zCARsqHI8HvLRJ
A0LtwiQQGwQ++VmuQqoCqSBBN3nWRK0a0CV1poyLlAhtNIj5/wC7xC0iYFACCqqED9ZJRMtV0Xzj
F2flyxE6848KPJY5GEVaJAaBdocYdU2ElYG7/wB/eIoW3x5xVWkWjp/sxTaJGcWf9rEDlysgA13t
OMdQ13tgEIc0c653jd+G+cVm69uLlWDS0KE54HeI4u7VJ4oM+2Nb48nTiIhHjnWBHeh05U+UnDxg
OfxP7y6wdOW9fSb70RFOEVCoDaawJBOvMlJ0qAp6NcUOKBijpHvLOLBlwuPZAa7FXnePhUmRi6bR
bbqdTI3mKXRyp6R+HEKCRUCU8tb43h4dnO0AUdGkIgwx9JWoJPUQRR88uV1vQjgpVPMYUrvJz1EQ
JDRsdU5PeCtYWCgPmRdDzozSsNxxBZsAGdffLDgZERYT0GAg6vIVmtiI1Ve7la+MjomgbsFYFdZO
rGiUoApxJtZN4hSiAagqJUi642+sfNTAVQANEhPRd7w04FAsVTx2a+MVxKpQhXTaEniEyBGo1qGo
EgkBgFB3ggIQCIicaFBzg9OgFCKMer0Lxzh0XEFljQQgLuF2mMLWKaTQVASvMDccCI7CyxVRF0qB
rgSzNC8SWqUBUJKMmtYgcp8Adx1ukwkKWkMUWqBCjti9YslbQwXZ2KlAonBhJlyEB6mjwDezGWJQ
CVLUIoiLtT1lTBbRKb5sAGda84+XPYEheHIA/fO8k4RkBICQRTbrbyZRyOqRBBLGlZYG45ejswkK
Fmh0ocw9mNWYABTEDiquJVHiQiBrVFtrXrhhethUFa2K30gesnR6orRR07DXaBjPgL3YKFgU69XE
SwgUmOiU0gOizVySGlxws1sAjVV4coCQw2Ai3hiI+8DndQVBJKUBFhLd2GOpdbZXAsCgaXje3F+6
G3CJQDV80Wd5UUdB0lWbbSu9B1gYgChPUmNI0OGtuKT8Dg9KNiAoxHjB9StpJwoWuroZpMHI6mQi
6bRaV1OpklCsCmKLYeZLd8ECMiNaUI0EpB0PVw0FxVCCU0+kcPUEh4UFCdmnJbCyKKF2Si0uTEFc
CEwkqBSe99YCsQoKwTEPMYesYiIFQdkm26ibBvjNMc8QIpVRbPK4qbUuQex0pyezJHy4QICMJSCx
WXeXQqylNg0DRqGzVDBC2QCCdOOFBxSiUeiBrsVed4/0bokLstFVQKJwYcvJdKc4kImnLGpfGApx
lh52P5yeM9ZuTFxTwVUROxOMjnXkRpFdb3rGwUTKO1XlfeXEcAhVUDoquLOQVKLpF5b3cpfUEMea
Gb71vFpBVA+UGY9fE1STavK93CRaVSXCV0nkwMmggclvy3vfeDIrkmIic8Jzl7VittiRfYa41hw6
MgUGM5KGnwYAcUCcTG+Do2eMRQCJX4VZmo8leRwVrPWQ5tGDOIma6wifyYJAI2Q441kUyUpQRc8p
p3sW5yO1AnevLVW6m984IdQTcY0fJqu8cVA6pXIo7HxxkSCYBRCANoBozZTLEu2wZzvGiv8A8Vf2
uPllRL0ljp6rPnKXQ6cmp7Gtc4ZhJHCmza0nWblbqst0rrp1gICI7Qsa7KWYyqbmCIgWRGTxrjJd
OjxPjaT1i55tNl55T9YxL64l5EiObBTTUbpXWzrELRVAERFaIg0mzNNhmmMqIsUVi8V84KcgAQWC
NgXg1kgnEYA2RKiPEdYqoFWGKwXaioAvMDwYRpnalTSS7hxbDiZLqWlBI1tbw133hIc12TYgWjFB
BTo1higLpNI8iJw+8XobaK9VZnECL32BUNaw0Sy4560sJ8axAQQRLaAw3umKAdQrUqFDdldTavLk
ytQXueFGx7wzQ0pEAhyq+xznBUXggu1OALLAODDWDICwqwBO1ZOV84tG4ZR4Yl75x0dlZpyHLewd
3ZcVGCgQHnQxvet4fb0QQqqB0KrDtXOGmFvwFZlwULKugAqq6Da3KOpiA80NTRRXLJWRQCiiDsUF
OKHjJFlrra27bXepvBmiB/JmNdrzvbkUFUZQIC2p4HiHgwshISF5FGozdcaRYUrSjNPFB+QyU3rO
xSK03vWAECJGHpVmGoaNAOkGJzziGQkRRdIvKJzecvX6gO82pv4zkETx4zQDghoyEQ1N5ZP3iFBN
n94Mb9LnwcZzj9O95fObHBsMvLvpY2BLV2vgF8DOWDbAsQGA8K6wyc4eUUqitAs5Cv8APjBgycEt
CiakBLvlNYLVXjSRWSTQ5tusUmjBB4p3nINMAAJgwb3vh8Y0EiO7M1E1y1OMlcMnRQCwsLc5RFyB
jKYYqCfrDly14HX4wZcuqMDnWOgN/PGMhSKdgo+4r4TNkpDiGcpYPvFspD55yVmcPHGcyQTfkxdw
WHF5PWNAr3vOw8dBg1opLLhENLRzss9zAVXF2XVPjw40saQVK+VeucS9CnAFGv8A28SSiLUss4rn
EVfBgCiNIT5wVgAdnnX7++AIJjzKQ69YDsVpnT4bjoqNlhId+T4wSTbTGa+cldjwczwYpegEQjXl
+2DShCQj/wC4gGRFDYj0e/nAC1kqqt14xYQi8DR8+XzkTsNWhqZQCCgDnEgmomDSiG0eMZcmgVh+
euMqgDS649/GMN1AUcHr1gGNaEtoYvQBNOucLICHFxU1aRk4HxgelDneVBXngucu64wbOHRj0SJz
MJQfbAHdibzWI1EKa+zkfqOWQnMI4KPOwZ2mCFLCSraoi6VJrgSzJntgLUoCoSUZNauIs+Mgdw8b
pMJClpDFFqgQo7YvWOMW+NC7LRVUFE4MVzBFQjmPDKXAcGOsgyvsBPGXTxc9dgAYu2zJULzAAIxn
Ow2qrxgzDTipER01NuVYprGPJaAJIeOgPtiJFhsiORaHnACSroIRpdKDyE41itOiIBAQN2IaF1iw
mMdpQyTQiA652jlrW1QhqRBKm4mIlphiIEkUQmwu3RMUmLjgoALFuVfUHLWDDPCVmx4C00FHEZPL
ZKgNAKEhF5VwSK1dBbVJSpDT3zj+oUDWkIhBEB1zuOCAQUmIQpoCrGO+coCUEAQMvYl9TBqAnFkR
HTU22qxTWCSnyUyJVVURRgcGA+6Lifwq/wAOdZyHd1OzK2KSTB39EYM+2afGSKLewzvbiKslWuph
ohuB4W+cspEarxzxrtxYoURrk8ucUYcyEPR6MHaSRNU6ubni5DhE/mY5YCuku/NwQ2CiVPzr8YEM
IWry/wDmARFXIQDGJXBAnB/7gUd8TKBJ42zBpWUWPnKEkdD2f5x2YdJZm9QL5GX11kBIDfm/GMKU
63s/POIFCBJ38Tx+MCvDLd39mcUoygccc5pAjre9ZRobIAKnesYwhog032ZfITjrluNC9rvWIBQC
6HvIgUXmYr8G8RBtD9Zy4H5ykDXi52FvzzvB8sk85sOw7Dzl+vzk/Mf39OvoFxmLhRETiJ3nmdOw
3StNx1h5YBiA2NdlLiiwsZBECyJqeNZ6nTqfG0nrFtJUhXnlMTGKo1WVDgsL5mP9VGVLB1VenXjO
eDJR21BcQWGRofSGcQWa68ZUDZI8AXRxo8ZxdO1BwF4DoNZ0NAuiEI2kACOjJACpBOIuzH4SLFmx
FWbDFkJkkKKlOFFpeMJeKFyedjd4KXQHCIUa7qL5hgKIojxPjaTKjCgHedDN94yIoaIxE8YkEq0/
BVnGFqiCoDQ29O8bvoISg05enI3/AKwTjSzXXjIVpLxJ4Fh+MERBO0DQe+1e1Xv6CNVDNIFw4l53
gi3d49YAkt7zr/eIGrjIS3vKGKBQ85JHdjXXf5xJDfian2zaoE7bT1zhr0qoO+TLVAilNJ38ZFGl
AgprWD2Od3lfjGYd9+u5nPXivGMt2pjed5b6jLg0E5dPOOTp6r1jojvowggN1znX3ykF4Yd043gq
4mtO+MLMliicnJj0zl7HhM2hDqyzjOETStdmRSNNuCGcE7bh5vWAF5NiuphQqkbeV9+8ig0PnvEu
I9854NJnO7judry/OAAE1BuURf8AGRYJH9YAdN1joAh37wEIInGWROXnP4n9519OvpL/AH/8OsNp
nsNnMxN+jF8d85yywHtxUn/XFU4jiglzvBwOVxyCheM6+kuHeTes4x+nH1C3cyTrnjJhTkcaG76+
k38j9ByiCyvGI2FEJ1c4AIQN15++TyZzJrAGw3te8F01UTyd/wDecJhUGFrzyeMBBScI7MC0lUW2
5V3JZ8zFqNGvvki1Ia94aRwH5cGiU236+MOTb4Zgtnc/rrHnHgxVDejjEAveIbRdfnEtKghyf8+c
VRSq8zR8YdiQKAauEek6HrBF6IJxfGHwDQC8kwsGBCgr/neMn4V4ho3jKig7TdzYPRrJnPPJgZJi
LtF2ZRzNfQQOVZt9YEz+Y/v631gZx8ZtcnvAfGMvzhrcuGx1OsFOsQPGBrITdxYh4z3/AHnJ4x5h
cQqFAmi84LIqLFr/AK+Pr33esC97xI6b8fUDvWO+MnnJkOPDMAmneb8z+8FCkbpveVw/bEYFZc3K
roC44Ag4O55/1iMgWuqrxgEb6sdrz7xcbIWiawjbRsI6M2qwU45xFdLqCzvRjjA64gSvGAcBvu5F
xTkFuEAR1abwyumzjDVSxhcFVEmhOPjDg2nWG6utzAw68J1lFQnq1MCFw9c4CqXVhuY74gZVpyZa
F5OJlM0s794wNvlqfOGCCBpUUcRRHgnBr1k0xF32nXvAKBSNWBON5eADQJYM4++UxOpN6PfnDwHj
WomThQU6u83Tc75H2xA7q2bx0jr3kzoRcIVi+PWI9ces2DrYfpyZI58Z/Wc02lP3wHt8YCkFyiWt
CM2dO4uUlpW0Bdwu5NDtwjiqYkUQoLRNpvF0VZKk8KDPtmzrF07zhLN6xA27uCoWCyu9OIgKiThR
msszZN4xfADXg1xzvPRv4yp4xC1Jsm1mGCiOiiOzwji0dee+3Au8HZC206pqdrU65xrUDDm2b5zn
rX+MChEVCvy8YjyAw7AZxIP3rHSyE4G4SU54xdr6x2ozKu7b3hTAq+C42BC8CxnmZwiY7mvy84Cn
BNFOQjwxQuvF85sYCArkm5xsdYRAO0J5+cM2o7IvaKD+QxqBdRjpPaYliEiVP/MQmwJAip1fLiqk
5BAVfwcZJKE4pp+cc4KFXywv3yDAUjQRRj8mDqd2OQhZfHbhCam+eDCHD5cEOE/zkIAK6ZyYOpM4
DXlg6OXnWErcFlQFTUiCNvrGE0FEvdibCbqcmXVslKm7CFCbslOcA3ROGiCBqgZrvxhTSsmveWfO
VlpXne83JbCxsGDV2vgF8UulQs0l0KBaaVD3jRsD4LfjENGI1J0U64ddZ2CQAOdecFAR205+BxtA
o3uMvOBNfxm/n+8GJ1utPeaRK7VKHtO8YULQFYJPHz3jTQ9FOAnl2T/rhaQt3P1lreGahlf85/E/
hwcc2a+jk6M2LEB8uw9uM1HTBQ0WqDfO4458YBFGoj36waLgyQVHsANXYq87xeB06MXTaLbdTqYt
0gpdGLPSP3wgqjjgSnlrfG8FBs5+gCjo0hEGGPozIET0aEUfPeW8/SjkpVPMYUrv6fQBZMNEx1S0
94DP+hUATwXQ86M1qDecQGbABnX3zdqIEgQB6mXQSJIySaFauhU4DAHApleSgqKK86NzBpwQahYZ
sNa6r5zk4UgJoXuXNEYHkKzWxEaqvDZhyHvG07LRUoKJwYMEag2m4/cM0QqZrvLNXV+DCrfcFJCg
GBRpQ7xXPbeljQFJbFdzeUniOIWF0iioS6HrHXnwbpEuwvMlu+CD89BhLyCEODWj7oSFrUBKHjep
kZpjhQVabaE3qfNMQETBEjQESccG5DBfWHUcoNBKQdD1cUJEEgGg12LedvUyooASijXjmB+MUoXi
BgOpoAAem93E2DdJi3jBq9p3MShkwIghxsR1HxgKsKghQdaC+vnDSRAABgQ1Qt538Yq9QBKhqs5G
4rIEQqI6GgHgjZu5rE4soGEPRU+MZiWgCiQ+B34xE9UALhJ0g/j5yKQlAtUdKi7KzvG3VEZR6CNT
k1yY3I6iqgWiAxbtT1ks60EtGpsgadDNbmRYlCU2BVKIkIhrpBWKY+AFRI0hIaMZcALQZBrVm08B
3ghOfY3FDhSk1txSIpG0WJ9wxWYcjVGprtVwbJbRgsy0VVAonBiRPhUCGED25gDrDYalNijHhnrB
FH1osr8A+t5bMJiQQp2IOjakpbjJAQtFAFkQlDXGnGDHU1rEOYR4ptU4c2OgW0QAoQKoFol4MLCY
QAAUJDloUzVEajvFSFeeTDgq+nEJJpWU7e8HpVthFmgfvftiqlVnKwPR4MOSQSlLcG7Dd6MUwUiD
ZfnJlF204nObzgaoO8P1P7+h/GXNvvFLIFERON9Yxl6gfFXXBx4xOFKZR2q8r7ywnwEKqgPBVYe8
RMFUkUiK1E5vOWImAHeaGb784osaoHlBly9OFbKq3m93BASUkuErpPJhMGEjktPbe997w4CuSsRE
54TTiwrrXtsSPfCEONHjDg6OgUGM5KGvR4wApoEUbFfBobPBiRAxqj1VmOkYClw427xTG1gF5bWt
5tw2Gx3CNNqunZ4xByItmVBF5Kp4r5cNQMhEEYitKDPJeTJe3jBnETAOvGAdnUB13anb1vG8mIIH
kRNiTNwlGOaAVXlALzA8YU2yiQABbUANeA1iTFzVfJVXR3jbBJ8TwGD48dZdgoYwKVQWgq2I7Xlu
GfkDNCkSEFKV4AmAYIqQJECwIyTjXGaPXuaAQbQ4Q0GuMnYhgLglnFmrzM4LRUdCCw14ybkKkikR
eUTm84zdlIu8oWHzlP2mqGbBjr9ZxC2J8oa/fAMha0oI153W73jUIK6oyoLBYV7mKciRlFIi2onI
84Zk4P5BpETS/nBDSUBN5WJX24tYWMDHYCEhhJVsikvDisCHKF0ocCznBRUJIBwCZr4wdKa1QgD6
8JkPMEINkVp51nI2KHhwqzjrJytu0vJXT7w0cliXCV0+87symgsqx2sK9w8YXppVaLHbaVi+XOSF
KjRY07SsvFwGAkkFijfYGcaPGLKCpCvNqbxyNWgbzo1vHJCVFV5hwWFnMyWZWdWwdVeevGBZIRrA
QiIjjRu61rRDvwp8KcZcJ9i6BoIK8YFFoIEa2CXWrjOpFsII8fONO9c56b+e8tRo51a3IUggOIMi
AL3D3grUT94TmgE07ywZQV8jNDZR0wI/91nAQCvGu8D4A8CZ+m/hzT3jrX06Zx9GkbZoSIIO1AYA
JXKH4lCn2xdB0aUgBB2oA1ng7MM2IflWB+XJNUzaUUZOeMe/eBs6xp8YgEaTsFH3FfCY70b9/Qfp
8Yd6KjesqNi9jdf1iiDip7xgIFrzp9YW6xn571kiG7+A6xBoR23TziXAY62mu/OWWEFY6PtnLSoS
qEwNAi7RtD+MNG0A6JTHoX7K5z7nxr+Mqyq3vOHf3xii6l8zJRVZdYS+TOePOCLjGq+9bmcSKla6
Z0ZCSougMtcnKuzEiQOHOnNycBpm/viefPrNreUc+HOm7dy2YAK0BJiro175y6oHrGCjZ5duHO/3
jIqQKt6xQL1LMJd8XLQXArigij+ssAFXbvxjUIBK3vApKd6wngRWdL/0xeA3OKPxkHQisR2/OWja
bQs9ess3htVTT67cawV7e8quAYFq6xbbfR4z1dXIGvWHnL58YEqh884Bzut35zeJDmM1eMOzb04f
sP7xyY4GCzRKiyE7B2nYTKyhoU0SBpx8DZilA4AxEGMtKHNPGM+P7RFQqWpThaTUUmj4qRWTaArw
xeMcSK0AkGlRRF3OMB4lMEgUOQ2G3XjGYYGgqhIIQ0aVTccO+hmdLldoXh3yuASu0aIr87p9LEJu
XeVCP3/Acq5zjOsTNXtwXPfW877MIkZON8ZrCB5MBQS8obTIAATswGtfCYKik+MoFIcZuLb77xA6
vwdZpAu9zxnHWRa4nLbYe8jd9OeMRIR53zlGF4yAyL+skS6+/WPMCfe5LkJrBpSDR3vx8uIYDZRJ
gGhda78c5KUNLRf44xBUCE1i6VPHrEcF3z7wQ0DtruZujXuYPYH5x5ujfHjOYlNYzdB5l5wAyH+c
YkKwLO81gkulffWAw0fHvCCzzvGlsgayEiciBrEEVsrJt8fGFWioocz+cewc3pr8Yqh36G3AQEao
9+MVWHPOPA9de8HJBPjN2mu9dZaD45cSDj5wByi9+MpIT1ecAYK5yTdN5rKAkafw4ee82/b6qcOq
I8ibMEkCokilTeqafWs4kMW/IEuKlsstbAFnFgb5yYOJCkIF5kA54Jmlrt+sna8a5x1Wq7heVjt9
4otFmjQBZxYBedYlSy0gyi5TRpx6Qw0QKQAYAa0HdcERBO0DQXvtXtV7ya51jPoHXGrgauvPOV8u
IQ11cpL5eMuQp1iA72fGccecHgmvnEnHFmIu0PkwHPLd48q61j2HxieJbkzgPeAAIX+fpW3wXIih
vmvWRnhc0R653jKypSBdefH5wI7SkZ3/ABiOsgAFUOOXneaOEvZRcR8hEWSeveJCTjcbu4a53mrx
304i6Gu64czquEhovm7z5J89Y8YHiOUj0n8YC6MKKVPOQWh94QkMuBShW3nGoPTYeMaazccoibsM
UJAWAN3/ADgawpuwnr75MABAYeTb9nBRETZ8j/hwg9KJ41N4EElTEEt2t+DHrd++Jduz11ggg338
YwIPBvebXa4CadI8Oa4BZgtrd8+8dsW05EP5+jOvr1hi9GT636vxk1ctz2XFLinjZ7wQTHbrvHxx
4rzjx84dfSCuE7riT5ypzguPOBe87Tk895zCzGU1esDo32E84ce1zq7twWh4uKXTTGn44XNSKxAZ
ziGgQERuvT/WFsHCtNLvvyYgJoXRN68dOUoXahctDdFhiRi48E/WcPm6cHIqnWVoAJ+800WfxiQg
7nn+Mauj7GIOFV4xbob/AIzeD98WatNTXWWUNYwbseA198d08mWjSgmpkkqqGVo/vFFmGjgfnDU2
oqadca+c4AZdKu3XrEjYRU7HiYQUdyfbAHgWc4p1HkxGEecHf3g7DEuABrfPOL0/fWbO9ecdALo4
1mnjA/Mfw/8AwcYmCHWO+MmJq/8A0qkmBgPn740bxldYTv8AORT0Z185tJHEeJvA33xm0s4zrDSw
uReKveKOdYmGt5rlG42Xzg3WawG64dYO33gRsr4uEiPPI4U3KPrOuNuXkUjVj85SAOUVZllBFYLp
9YjVjii6uIUGcbmsJdHWy6zbg7wB3Y5QIub3Qr14wNVTziBTXNxoNn+Mg3tdifu5G13xgHImHD5z
hxL+MZCW8rk1p13zmyBWG/WHmciOnGQgPv3kPYardmE4H3yuRHaLd4jaPCP/AHWUCFM9yr7yWwp1
caykwOh1eLgiTWnVcEKcjxi6nBfoyOFecs6MP1P7xcDO85xmxHYGF2g/xmtOu6YrpDQS/J5y1NK2
kLuF6mh24CwqYkUQoLRNpvG/Fdqk8UGfb6GHO8eYN1KoWCyvRjqhUpwprPkuO03Lt3oBrwa453l5
8Z1zzm2Y2zldGHMDG2Bjv5MiGuPOcPnLvWrgo6W+cu2zeBKV6hAq75YY8iFJoKrSDVwupjz8G984
UBcbIANd7TD+THRRAQa0ePnLX55+iAvfjIm8YOAvnH+TENJfD3i7zWt3GXQHQgCgKiMFneCDxTKs
F35zvPlXvLOSAwrdiRCb2cmLY1qc+sElDXnClugNvvBju5sXV1igzgf1nL6uGKPMo3rJUPu4Sofj
BNxbkUIMg7o5hzvAS3UPiYGkBLOlSCaWU26mBXRreaibGjcGKyzvCMAB8rhBo4894QgiAvbo31h6
gQjQREvZRxlh7pU+lBn2wLegLhsICoC/LhAmV49ZWunjDbgWlj3cpVZMhtee8idU78ZAterTGuSv
nOVmjJdqHx9D9T+/pXzhw/Ql1cB5VhkkEIRUXi7V/ZDrHGCgoo5G7E8ZsZgwQTXsgNdi3neLTWnR
i6bRbep1MjeYUujlnpH4cQFGFwJXbW+MNzu52gKjo0hEGGTgBsCTEGhFHzy7y/N6MclKp5ihSu8H
6GTYViDRMaUWnvAIW4VEfULoedGaVhuOILNgAzr74BpcEgYPiZcW9GOClU8xhSu8Ugqg3uwrEAOK
cVa3BhTAW1CgujgqY3CkciaF7lxcsYgIdjlqyhdKzHY8MDUK+RbhUKpypRaGznXG3LQawL4WoAUh
tVdJgPFRAgoA7FPGGPbI7jUGinJp2GO/B4iQkYSEFisu8LNSSlm1GpfCFSlMeyKnbBwS8IDosJct
G+jHJSqeYwpXeITRyUIEV+ER94wWAJAhhA3a2AOsfBEIZDCsACICPLmgC1DTkSKcaUXCFhXQRDR1
RSHIXrE5iOzVd/KrmgC5kYum0W1dTqZv8wpdHK/CP3wlQrF2UKMtNm9QStEHJGNhamWcTUmIETlE
2Na84ZwBwySulXiPUPeQUTh0h0NAAHpvdyPeRCpdPBWU2BKVy116McFKp5jCld5EExtkFdKvEeoT
CXISAQF5sAEWA3u5J99PIbETaAUjdmQDXTULRIFMLqzkmaEGAFY0eKAp/eVMzJAGJjpBvRQGbrbv
sZsYSlSioS6E4y143UCBAnZrNClEmhLNU2HxxrB2IYAVCwOKq4SLWzQECcFWvK78ZtqoA0AHylh9
sFQwFAiwXW2G9XzxhPkBPIgUUDSCQYYgwC0QIA9BhmQRgKO80jva3V6xxj3hoXZaKqgonBggD7hN
x+4ZTGHe2uFNXVQuudtRR8ZA7rxu6xRjXxoXZaKqgonBgqChCKCjzsNdustmdSJSDCgCnBrzmvHA
QawIb+WryrjQRvjkly6Hh3gwnNxPEoby6Ca5yJwYfqf39OPpPGJwYURE4R84o2jvTku3Nu7ziLGJ
qjtV5V8uI5YgQrUB4qrrF3ItBFIi5R7vOUTFAO80s3iWxqgeUGZavC0qqt5vdw0WlUlwldPswQgj
I5LdO9733k4KhIiInPCc4ratC22JF9hrjR4w4GR0NgxnJQZxo8YEM0QuNipvSobPWKkTuqPVWZoT
JXkcFawwQCvYRETnhNOQwU0gEAbgk6IamsogHVUEJhANG6uIVoIMQRDbxQfneQGPQCcRMJ8Ze7tM
KRiRNYoK2pVtVS8VV12rirEAYTyw7XtecgAgQAgCRqQNcYiRilpKMYmqD9jPkcVIEVpvesGMESse
lWZwa6l6UFQ1rJBqEkERCvCacdgUSTmgMN7y9uKgvOhnzn7GJcgIOc9fm4xxvVIQVDFUNCpIABX0
AZZf8ArzQZvvW8XoFUDygxxyIUx0XBQvKBXlhcn2YTQIsU4UrLxvFjSNBQUoooVZXnEEJgKIQBtA
NAcGs4/Sar2CXxm+wILQgEHFQC/HjAwNCSCIm3RNPrCGoq8QgDaAaAdGX4E9cmwQcUl2NEeGJcTS
ACWsDbcWg1F58uGwsljj1RGYFQ1TBSiWpo0+DxigjE2pwgMJ1MBJJSMRUG9DWhzW84hZp2hEY4sA
vgxo2baqeV26xbIq0oUUVqKDu8GNBFrKKWrDpXepvKieVsCx28lY9V84LulIq8ldPvNAZC6RwVVh
itLqYW1FR3vGtLUgrzym/jFbCKoo4ROMshy1QKAVXlAL4Dxljb4wRECyTU8axbSVKV55TfxjREFE
Txs7xx8iwAiKWjQad4ypVWqtVxVhwY/e4Tvn3i8H5xb3HIeGH7j+H685HAQEVEBe16O3NH6T8agf
yGH9hKtNyEjyu/HOVy5PxjZu1IBUeilfKBdxGZRUYChmlEl4eshZuPRUBfVcNGwFwoXmXchramPs
TJ98P3gzoc3xgOUUoFUqhZOeDn2ecAxuC4G8Jhh8rA9uDO/s5ResbzGYMzXA/wCss714x3WbLUn8
5Q6uVbbfjjFTw3xijxzkPeEkrfWQIDy7+MWr7yoBh3Mn4OMbBOTHwTyb4xcjrU44cVIpz5crTQLg
E06fxgiu/BiIHj+MjWpxfnK+f1it6T7XD4VOcjS1fDl6A95DNaOrzjbFEGuNVPO3BZvNtiAS+chz
X5coUuh0dZvnzm+ct7wfKzvNApW95p4Icf7xJ2JgrqX75V1dYq6SHoxOeI4tHzda6xEa4JPL8Y9u
w8azsrhtnycfDifSa+lWJZ9rafow2fQC8EqBsQ2qukzSIBAG1zUAVzWx/UImiEsBCi884nGNREOx
y1ZQulZhqMpoU7PJ7MfdrEWUY1Vd8g71nAEuoQU6KfiYWRqCIUQzmFbWrxgAFhiRD7GkqQ8m1Vjd
IBMhqCHY7KXQKcN3YQs8IykLowRsNuujJxAow4hJQhxpbzMLnbNURVSgNhXZAybqYmBBSVKoFg7N
txjCMiGPB5Sd3G4pZFTP4gfmYFEjWzCcTaAtbxONZEI4AISChwI+hwQUEQ8V/wDgY3IZOJgws35x
39brCc4FMnTi7Dv+skj5xhoMhZMb6Dtxnmx77MVb2/r6JHp+MsLs8Zsj0msDZuujFVr9BThcuuo9
eHDccO5iRpDFwSJgSLw4zgbjlI8JrWdHPtx3rnHWrvvAvGPL3kMq7wWGc8bxbk71go6xfXPHrBQH
CL6xOys85sWTDk+cjn8x/Dg5Mv0X29UR5E2OePOthNgx8YaQQCyASq7lZ4yKcoQTjSzXXjJQnFBn
Eqa+MMIJg0VgvBt0awYsvCYM8WAvPO94ybRFCllOGVnzhcWk9waiyaNejCUSGiFlOGVniuQusLEJ
SEUUFVBeXeBAJBUQgDaAaJnBfaH5AlxctFlJoAs4sAXnEBZCRREl4TUxY1JWoukW1Hu85HDTkeQX
Tzsw4S0JHgK6TpNmHAmUYyxTt2y+cvoYFsOSeLot0UDbiM+hu9YC3uZXe8G6l8b4xd8fB1lSanxg
L9W3feE0PnKeHP4eXxkeFCZfL9sNtE3gpDf3xr/P0BbDOHeCNQROzFfS09YwmfGbPBPxm0VJceX5
z/DDgE4xG50bcnset3bnPaj2+esF6Gn3yGqVmh4zkIJ+8EHPzgKJ/OXJH7YGylBn3xa7ieMBQ3XH
oxpX8es2gwY7n0N4FgvHGIFbr1kDY/nDbt/OTv7ffPvy35j+H696zjLl8fUNY6+v7mWFcW/OGPG+
cNPZ5zn4esu/GPu67y+sXL7y0lv044D7zi4BIsc0hG4HvEpRszf0CuNu84e/oO8XW+sPEq5YTu5E
803vOUD1iK3hBDd5wq3nzkQCzxjU7EcBBWXFoh/vAhV+2MQe+8Zb4wgjudZE0fbFBIz1vH8B/WDy
t0b2N+cGvAq8uO24zxrFHU166ym6zi+MSOCE8dx7wAtQ8YBsRwZZ4z5ySr3jJpfGdNT1hLXjKHPJ
1cUe19YhySeM5cc8esWdfv6H6n9/TrBy/WZLxg5MDEnnA7uUk85MCY1c198qNNY9cTNS6zX2y5R6
wZjLXI5P5zgbk1zvJTufSPWBDZnfnKf+YuU+/wBFJPP6x30w7b7y7sy3EWsXykym9fGadTzj584F
IVOc5b5w5Jzj7RfJg3e/GLrsnjFVcgaF95IdDznAXfxxihKAO/nEWT4md8ZbqbXEmnh6yJEvgDJW
69jhAA/9yU3bglhiR3T5MJ6b5xjRNecAdtfnNN+DGu8U6Pzi3OLiHXCYwlPeacYwIU1+cm89Z1nz
gNWwKAaqq8AFfjBcklwJVUEY3iJw5YTl4kXcL1NDyYB4VMSKMoLRNpvEGVdrR4oP6znn6bT4xRg3
UFAWCyvRjohUpxRn02TYu3wA14Ncc7zjjlzmZFZEB1t0Yc4ETgRE97HK7viVPpQe/GJNZxm9FdqW
XgUdQeZi694CV4wtxpLTqmuCrU5Oc3gjLwYuDrEmWweELTmO/wCc2fj60IuE1RQAdxcw9/Q54sxa
TW8pJMAxYswUBoqqgAYePcxgYY1NTtWGBwACNAMT8jiJ6xEhVXQgNDcd9XzhDvC2WKkE1ZTnSYB8
mNGH6xKcsNVayCLs37yQpeOc3HAAuldGRjDMbAognOzDMO5RfYKFPtmlndpziFp8hm9pkCZ1kFB6
OsWYAEKlEKE5kHeaViSi+4UKfbNDRV89ZsFRVQQWUHbIe0xZuAdXvFOKtfjEJzU1XqEtej5xtm6c
zFRda9Z0EJ47wlEBVpuTU7XeL8vb/GA9jhSiS1QicJ57wlEpzjHS/wCMZ1xjQa2/rJUOdZBNYhq4
p/DnHf1nlxwgDHapomhNnC4jSEZRV5KAlkSB2o4YUUciPfr6IYIhj2QGuxbzvFovTIxdNott1Opm
9yFLo5Z6R++FGiRaBK7a3xvDcbOdoAo6NIRBhk/HYAk9BBFHzy4OvejHBSqeYwpXebc8qgJEhomO
qWnswCbtCoHpC6HnRmtQbjiAzYAM6++MkplsCA/GM8VIZamkBm1TgDCKIabgCGhAM8sQCgCO+Y9i
/gxHgQAwrdboAnjI9GbgiFsCJDXBgVARrahGglIOh6uWLxUIUIEYgy9C5L+fclyQNsDZUreQlglA
FL3GP9Y54B+gIBBCoAM7mBtVluGhAQCjrR3hAEV3DIqClb5SzeU1dcKhT3Kzc94DQHTsAAOo3u5I
lsVQQ9A/WG+VwEKhFGMZehfnHCPIKQQIvO02C0y6xAVTE5sABwjZu4DZMcgCJjEuncnWTAngBmk0
o7Oq4BYMKKTAeUSPHPWP0o/qCcNBIL5TrHrTmCOEONGuDrJOoLu2aaqG9DzvLMs1EQnDtBvuDjuG
3iEK6VQgeITKXC4SIOR2awBkBmQks1TYfHGsULEgAgUHHLcZ1KAiaUEjtu7vFXe7UQiiKCoeZdYo
/hhVABezKu7xjRMRSBAHoMFIYWlFEkexibBvjGlUSQA09obTzch2oAxh4SnK1rzjGA9KQEV60iPv
HjhVuQXFYAaQEeXJGIlAIBmoJAUa6ecIlOcQADsTNOyTBWQ4WleCoFOL7yBqBKoCRKA1NwcOgH4q
EL3Kjg0AairDRNkuuNvrEgErqB0MQqdp3MlEjgBvANEcs2yCiooJFrd3eOWoZkoBGCFYLtg85bij
KU2DQIjUNmqGKYjkpC1ig1TtO5mhhdhg+lBbUulTXGX5vQjgpVPMYUrvEtIQAVEJKLT2Y7ZOxhIJ
KgUnvfWAVhwoayuLDjwZoLZ97g060OC7+M35x/cfw/SfT1jx2FER6j5xQD1IfOldN3rH0cTVHaq7
X3ljPAIVqA8bVxZyCpRdIvKJzcun6Id5oZvvzjeRqgeUGOPXg1sq283u4aLSqS4Suk8mAqYbMlpT
uO997w4CuSkRE54TTlx7wttiRfYa416w4HT0CwxnJQY+DxhCmgBbs2eHRs8GcgiCvwqzNAJK8jgr
WGagTFPlRr982wpWgAFUXaqEXzirGncqtX85ppGQiRhYUUfNcL98HSgQZ5ilzjDxT8BWYwqKFa0s
dJZWfL5x+zz4DteNc5PJ6MJEhW7NPk1j+YxKx7iXCJJBAHFWz1lu8AloMVqUNPg8Y2qldKMsOCws
51nC/an5A7xJ6RdKAgzixS87x4DLupE3v2OMqRL02GKuygx8HjOL7lPyBLh6ZiVj3EuKlr5H2vy2
Du7LiGBqCPImzN6JBygiVbIpONuDIJFjYCDOLF37wRIGP2VtZ6xfz1FHtduAmEQVEIA2gGoYRfwC
JqDehrQ5recsVGjSIizzAL6zn94yPtdujBwJJAKHS9gZxoyuVSjFPLDqws5mD5YAAGha8g6zQ2Qu
cOCqsPGH17WPlbX74go6sjyrtwPn9VgobCbcddXFUJGk5oDBu/nP2/C9AY4VxCBflEr7zm8sAfEc
8vONebSnebVb7codcxRRiWpQ0+DxkeHUQ1SI6ppnOWswIamy/DauptuVaUtyPNRAu7zVt6ByQE0E
Cu2AV7d4bAJIBQ6XsDONHjCjqojiRUdKhs9YDQIkYeqsxdeY1adWJco7EFoi78kV2+XAAVwViIhX
hNJ4xZTxW2xIt7EIcaPGAkDnD2t+G9673jYs3bslFixd87cRw1N77w1TNRbci9OfzH8P06+pAFGA
G3N0WBEI2HdR6vFwTKHSlKKDyIiCJ9OMaQKlgKkkKjJeMMSYIZP7asKgECqroDpzv1ieMnnH5+cC
JMuBVWC+tC1MQ6gLQDyUGPsy+s9//J95eGmFE0xD0OD56xbg1bgm/wCMZnT+ssL3jzgce8SdzEmD
k18d5foGSHOG/jAEr3lTVp1l1gQvnE784+GPZftnLzo3rJ4x1vZ8Y67D6eXAoV27ygbt/WOk4eb5
xWkXBh6ecY7OzBDU31iXEpHEdluUDyYTyX33kH1ibZxwYVbpuplV1ML1cOzr4xgWvreIjvKh851S
j/OLJv8AeH6n951l1nX0YgRRKP4AQfti2GJAXHIqhd/3hEFNa3F6tDk70u84iUOKog9l+1cvEsAV
ZKEGzArToy6Q05IQoS1N7By5oyWvYBVKuo8o05ysaAIlI+QUPnFOIAKmKI0AE4NrzkmSBK0hrh/A
Gad1lRACjGyPSjzM1tlJYTMigWJUluM0GNVEkkgDgAK83OKwTgAZGCKw5E6Jk4gLCIpCUmztcB9B
CkEU4YVHTN4J1PkVRGFAESAe7i1RI0Biu9qBt3gwmohYgKiA3Fol0GDXf73IC1BAUKPISDTAC6gi
4SNuVYprCcyFtcFEohsKlIGBX7XlWJ94/LjjOMkacY1YujnGcBMO/jLrjjPvlHGT636g9ZL8YE5M
gqI4Y4iROP3jtrh6yV3wZHBnLfDhTSo9OFtec3NczWRNo6fziqq85NHy4pA8ZHBl+Mmzs8414ieE
4yumesKEd4r9mKkh/nDTtTJS9GgyBh/5ilYuK9ms0bHWKI73hqPY8ZbiQPeKoHjE4xJ8L+/rt1nx
iFdaaUkX4XJbJLh0AMD1gKqQkHmo1x9ltK7bXq7nFwEV6c67B3rWcLRifKjX74LKA1sLHbaVi+Xz
hwcN5hWF4KujzlDIyluaDN4vGldKMsOrC+ZiYP8AqUtyQAnLhIBK6wsa5SsXy+crZOUtzQY395xp
2h+US4I3TXmRLOLFL7xkNCaELFOGVl4rlUIwDvNDN9+cfCIJiHFOGVlzhMpL8gS5UtFmjQBZxUAv
PGSUbCM4gs114w4RYTAiJLwmp4xFAiQZ2O4NXbWeDOtP6yr26yk42cmcScZxmwbyHRjtxib05F55
xBu3Xc/WCHrmbwTr7zNucj18c49DxlHjDgxeP17zX0QFbM4Ees9d/SNz4MRxcTWzXvB5t8znOQXJ
329piWWfbNjePD3iiTjvEfP3w2rgV07yxiOUaF3iuyY5HBkTl5zVd+MdFPOfzhOmO29e/ObIKa++
IGz95t4w/U/vNOX6X/5l4w1i4OVfoXrHYfzl+2a6v0H75d4cXWXxhO7g9SmWPnvCrcFOM42eMWpN
u75xpoL3i0gbefWaKXWKBzlvc7vjLOCfzl8L+cGc7MvhA/eUu3XGL31lBL9B+86cfXXnF2TH1gzL
a++K68ZN739UmuA2vn1i9cHjvHwfucOoH3gAp+TO53rOPBjTTT5wSbt+cndvnzgchv35w+8it9Y4
M5xVa5LpMfH8YKNHeV0SZFad5/jNJF/OD73lAXU51g3wuN8HD9T+/wD8Ej3hJft9HO/pb7zzhzvH
f/yVxJnJrr6lPoupvjxiuaLi4T7Zuf4wjbjLZruZznt3gVyT2dzFXXHnFvx9OftgzHTSbLmwpLxv
HXy5Q5E1d4RI6HNGOMjoXV0Ybvc1k1DLz4N/4+nBxaaxOwfObCOx8Yang3lbdZJj5CYMb4xb0d5o
7PnGOExXlrHnDNTVXyGafObo7x5v8fUL3m56cNO+sVVx/Z/Bx+oY7wK0AAqq6ABV8GA5AKQMVUEY
js31lZaVtAXcL1NDzgFhUxIoygtE2m8RTVUtHigz7Zs7zT9840/fHXDdSqFgsr0YiIVknkceLmyb
l28ANeDXHO/rtvAB8rDD1ARGwKP7M6znJGcmQmoX6GAT1kgYiN0EOheUPBaoC43Q9hNgOQXaGvkp
vHiVA1ghaG4lw0QF2oqQTSynOkxahIoDFKgu5DXKZVCqmQNKoQJE6e8EySFUUlagKgLfWPsAqhQF
m5Xxj5YKBbAV4k2TeHR6zgnF2GbXvF09axeHVF4ApUkI3d2lBcUfapWkahEF1viXOk1XWFGgKgL8
uV2cFAqVAdNB2up3gYU38YVgMvOLohAqgjtNNXF1M5JIOz5zQejw7uVJZ6sxyvVdIUGhpsQ784vC
nWhERQdxTXMzTzvOXWTHJDEFA0YkUzgPOsU8JBVBFbrkeLnIc73juDtp7wAVcofcKFPtgEVeMA0S
WyItgvAzXOVdDAwU+MQTX2xk/jCurnHLc2nJg0FhoQQNd7TC5CSyUWtaThPOSnvJeLP4+jQPok+Q
/hz7fUcE+jJYKPYVDtJ3g3dYocAApCHKqvwKPGFFHIj39EMEA0aIGuxV5cfm9MjF02i23U6mRtIK
XRyz0j8OBBRFHAldtb4w3O7naAqOjSEQYZMBmgJPRoRR895fW9GOClU8xhSu8OOgKBIaJ3SnJ7wC
ZlAoHlIuh50ZqUG44gM2ADOvvhgFOyBg+MqL+zuSlU6YoUrvDcqCQxsaoEKO2L1hLGpIYotUCFHb
F6xyVbikBFetIj7xLmjDWJSVJde3IEACgjABo4Tub3ibhqMh2OWrKF0rM56ZZKyryMNessbOWiqV
auk+Mc/TZIQrpVkniEy5oEkQ1TpDYN4xgafgsFUUAQI9p6w89AKsBAL0BAwhgABByk3XR3AyAIMR
KpsKAKdM85DqQLSOl9PD85HTEAGGqQRSHIXrHGUpBsTI8VfmTC8Ma3QRFFElEqHPGOBgHgAirk5T
yuNsVC7UCV74XxkrACEAGxphB5i4xTd/g5yCwCqAVZhFRUGKQL0E2sm8P03QXQDtNPrWK2BpeAG/
so/bA+GAmwRXuQ/KGGwhSFS1obNuuNvrAVRBGhZCIVAo7vGCScqnRgKJboaDNJqAiIQHYE7QVylR
IJtquORVwhAZxotETwvJk0jQbhVI7DR1ZjWEgSFDsISCMhNDkN/GAICIhFCIUXnnHyIJGm6U0wl9
4qtlYXRBIgrZ1es3qFsCKK9xIL5TrDADXEUFOHYa7QMvCOmAtiFgScHq4nk1Q0VkEIcGtGHMgRpE
6NUBT+8btPkEACgKhWAbQtynJ6xgRApw62sm8vBecDgo87BnaYwNoYFeQ0vG6gzZZhiSNAkGmQRE
OTfWagrEkIGuxbzt6wxEjQyCulXiPUJjCEq3ILisANICPLkkbeAdhKAjoKKdzBZIHImgFijsulSH
BeH5GEERNhI1rnrHaUV1BOGgkF8p1jMI4YQRDihDrrHOCgIo1G7p4wS74MUvGLfcnXz9d5Zi42qI
j6es66GSOyK0jvWPIInUdqvb7ygnwEK1A62rizEFSi6ReW93KBjiHedGbxLA1QPKDHFjQaVVVXm3
dw0klUlwldJ5Mmgwi5LdO9733vBkFyTEROeE05YpKFtsSL7DXGjxhY6OgUGM5KGnweMB38CKJio6
aGzwYKgN1fhVmaEyV5HBWsMEBWsARE54TTnrdOp8bSesB6pOo8bSesb4USS2gMG7wHUOcPve2t11
NtzuWU1GNI7RV3kea0BnETCYJF6xnIkSTkYlHxgYxIBRCANoBoxfTqkNmvLVW67cIIUEMPG1mcYp
RxDUpFQ20CrDtcapVcAjUtHQ08ZvclNIrTHFQK86xpBfigFQxAK84h3vbtXU3nOzM18kd4+Ra4l5
V2uF9mITQ8qG1WysvFZzkmHnmiwjou5xj6cXBWUK6WGzesVsdQR5V24VCkT7YtVOILuO3Zd78Y1U
xrabr8Nt123KGKuC1qm3ld4pVksoVil2lYvl85IngdNiwvBVYecMYwqEQBGgGodYqW7JFCOxuxb5
FwSfkJAHADsunkuBkgRGBsa7LuecmF4CicQWa68YSkwkhCxThSsXivnLKOMHZBWht0eXNIXAbLxV
desS4PiuW3tre9d7wkmhAaUpVoMjEcdDka0wihBaKrAPecSERF7bXjzlhKzKnNqvHnrERcAoREQ3
lNPkxiDCiI+RMPnMSseCrM/UfKgFQxVgCpIpEXlE5uEwAAUQgDaAaA4M/dLLkBji4Uy1HuJcHi6K
geajUe7zg2YAUQgDaAaA4yKZRcoIg2yKTiL5wGHgpAOj5F084iiidR2q9vv6pBzs/hyfnHvOrfoK
BRAA5ccr0RWFOI0DHS9m8ODoJtArJJoW319Ln+cZ46y3DTne8M57xugNgXfrpyWuAwM+VDD5XR7c
l+nfvOd5vO8SfRUJgjvjKpN+8Eo++MvfH9YPcvOUWu74wZdO8/HeW8u/4xXyTlwFxJTnX4waOJia
vdzZxCfn6iv394j8rlid/wB4Lws5yAnMRMEEEkd4Qsyk21W6xoDgS8v37zR7+PGPxIXnePXR5zRc
nrIIiSdDgU93jEBnMxKlI7uQ3yXnOWF94ad5XnB/bvWUWr13gxzQvNNZQJBcVIjgvnO7PtkNzXje
Fd5Nwqjidh+cnHvCzjLeV0/h+n25xX6MQEcSj+AEH7YqDdrz+dAD2Yl8gSqXTsizsMsAJJIgIGga
8DkJZLIuNDmgvLa1xkpozYlrcQLEdEuzJHVARKUAt7U3RIVypw9nUKKBHy4WpcWIIRFV6Viheg6x
o3JxGovw/quO6CQILTZoUfjLgjBgQCXsS+pj4tQAsDrmDdWEXlwxcQh6XCtmFw1z3ir9N/DDrj6c
HBTXHn6NS4MJecG6DZsxrU1NfODQyJzijcUt/UwWffGu3Nm8Q9b5K8ubfRmw+eMfOQcuaa3MGtBe
7jbxoMCxOO+8QHrvPGIacQ5xLp8ayHeGux16zV1Wnty+GptTnN1V88ZUjs6yoWb84r3lEC/6yAvD
xrDXzxxxibygGm8ANGj1nAh85c4M79OKrE4dYJs1uTDXeed4OianLMaldf3m9fjLOsr5w/efw5sd
/UN7yHdaOUmX4WbWB3IOAvAdGB8Ms2RCVSfrI5NFwIRBtkUntya2wdOBBnFil95qqcP3VEzmwF73
2jvzvFSFasd5qNbmjaqShBo1V25BgwYESFbs0+cKppiPSKWXRv4xu2ggCDSi9O/nA8BSguBd3QW8
U7c2YcS5x98Da/Q0tz8zAcacmHDzjJzv4znn7ZDRrfGbL1MoGufOA1f0xaG185YWbesDJN8lmH/j
l/DhKEbyYCwLvESCuBXXGEbXJduHEHdue5vxmgVjihgjqs6wCbYju4wIlvOAkFWTWIwivkmHsLnI
jTy+MjZNPM6y7pI5UEc5723NwDHDXjvHlOLy4yN2efGO3vBalU9aM0Q/TnGgbHvAaBzgAo8dOLOH
WF7GIsBvrxhpzvC0ePGG3ge8C6GzG8eMRj19BvRp/ec5Ozj6rkwG539R3cXetfT/AJw7lxVw5x4r
hbrJvespJIYCujK7Os3xgo4Cc/bBDSVxa1wY4O335y7fQC7qPExESQsx2a/PjIXezlwY6a6wFr0b
zvFKLuYU2DFbF4cCHOHNcVUCuE0ir0ZSsaNBhKXjFFJz+s1XZvBifNwa1sd5VKaLMvRN8Zxq66xI
V48OC3Wj9YF9nHjGghzzMmro9YLQ7PGKIjW2HWAGlH5wQSG+66cUI6ZwZeVLdGGIN95o04cGPF+c
gEBlp6w8HWLSjd528Y6N8eMpZne+cVDZDI4fqf3lusup9Q1msvrHnE+pibyZxfpz1g8j39E1/WHW
aO1+eMC4AMwhoMu+bjvdxwKhiLeBRfH0L1kGq+/GSmnWOxgr6zaR3nGc89ZP95oIxwFclzu4Cnh1
z3gxHLziFOE8YU+74wVxEU8YGribw4W9TB8iYk7QMNh294NAb5w595yROPHWWxNHOs1O7d1wUeMW
LYa5MrSaHKTbZrWsBdcSa/r6jG/QNPswQNl75zS0IZLepjx885Vh3jE1174xRT0ce8rXFuibD+ce
fr1i43iiPAG3HCh+4KgjpvWTRXQ0UAQ1RKUurgMcFfYysFhy6fjCadBRAKduE/OLTVTUiFobifTj
6sAKiVJ4UFPt9NIuwHR4DTvJerMrY6xN+phzL1hclAESANnpM0l7xuYBFUEV15GRcQcgklHlYoHL
zrH1BUEozsezDbtnePwNIhoVd86OMa0GEqCq601cLqYDadYTJYKUAEO9phzwtTsBCDujmHO/pE4K
8ZdlJLi6UmDqgeMUAbNaMSt5uEcT1l5zYAFO+8odhXKeDxm2V1kJ3iELJUoktaInCdPeDkkO+8k4
bhloZVMVIJpZTnSYrxJMlLr4xIup6c6a4x0EMCNjWhEWwXgZrnLovGMHjUPeDucb25HBpar1kNv9
mBXx2fOCDpzDzlHaXz6zeUrUeKYLAOhcgGEgDBeSgx9g5JON7fWJveu5vLxsoQWIaBu1ngd4QoFF
tSlfG1hXgzTnnxh0VxPf5wpAHB5Sg+mrWIUhqaCK6hseF1gTfG+8E5E++MX6594A8PecplLu2n35
z19JfobUHCMcqroT2ravvvFfVGpU4b5Yn4LjM6BUIEpp9b+izjG2iEK6VZA8QmbXPBaA6WgAB6b3
lQR8KVATqiB6xHAbPRd5+cZ6kRAA2IRZEKLzzkEVR7MDXYq87y0BQzYwlVSioTgJxnTiaBiDVGid
msuSWmIhbJEhrgysItxCGqQRSHIXrHBs2Gouz5W4Iuy8gV6sWykhsmbrIlgKWORKHmXWBtOxwOAL
asq7vGGAi0wGgpodU7mMkIjB1QBpqt9vWLpYY5Qr7K4Yiq1qUWhs51xtywOsCuFqANIbVXSYjBTA
EFQOxTxgt2iO41jakprkMUYlYiQkYSEFisu8ATMPl8iNS+EKlKGPA7Ttg4JeELos1ct16lDJSqeY
oUrvKoy5QgRXrSI+8M/QSgBhA9rYA6xAOAQyGFYABICPLhOesaDjU0mmLThxY4slKlAVklGTWrl6
6oCFSijGMvQvzgG9yCkAJF52mwWmIp2QwoVRYAaQETnDUTdIKFFJxYozlMbwSGDqAB2VvO3rIQhl
Fc1HXOmRBdmKFYWuFoBJS3gpUybygPacEVGK50bmapqlALE6eQEeM1SFREpQUBSI6qesDoEBQSbG
kdHDXmYIgEysULucB3J1MZXhgVAg7V3OK8S5tiWpLkgbYCypW8ckYlIukfjTgsWQhdCxEASAwCx3
mjv2XYgoy62b1B21vRhEE0jH7JjjpQ0VVBI7V3d4ahQhgwBGDFYLtAcHYk+FGwaBriGzVmMAkVyt
ApBQGl4vLjsFZabogpHqtZvEJGTnRHU0AjhGzdym9cCSgRhWU3CUrdJREBDscsdKF0rMQUd+zY4K
JCUIs1s5gGAU0QqxKJsi69uU9xwg6wDRIfbe8fYieAO4eN0mEhSkhii1QIUdsXrN/IoEWa8cwDCx
KQq0TUabs4a6ZiSzkRLdHAQoxHgzl9UtUDsIVVg6s6xQXt0esSOu8vXWOoeTu9P14Prxnm4w4C8H
rODo3PTQrMXIICxAANvoDFAdViEAocDo3gZiICiEAbQDQHGcTUIfkDvCAJgNHuO+ceJwC5IENvoD
Jp4hBONLNdYo5BUoukXlvdxQNiaQ4hdfbBgCkMVFab0NbOa3nDUiSpAiOzexR8imbW2rTQQZ5il9
5+gcHILrJj4SDxFdHowGGI2N5tTfxlV8UBtV04qqzzi98arfYPJ09dZvwmilBY4qBXl1i1CLSDKL
lNGnLFNpBdMTZiLLalW1UvFVddq4AhQBU8sO17XnJSEoCIAm1IBONY8J1LSUZR4oP2yazuRC6XZ5
wK4RFh6qzNzUjn4Csw0FQiAREN8JpxyhxJOaAwbvKUZqC80Gb7yaEn54AQcdkQoRE4ROEw0nCMYb
GuynGMGdP0Mm9+xx3csTFs0GKuygx1o8ZzkGxPYMcGuoNIQChxUAvOjxjXRlpBlFyjDTh9KiwCAb
Qmpxg3hk5Pir+8WtPL2PFV1iLOqQba8tVbqbcAIiCjHgqzFyF4e0QkmmaFXpvyRLgxJd42zZtXve
u7g9AEL5Gjds65xLb0JkRIV7AHyacZATyJtsGc7+cu1ysBIsLygb7h4xOCFVXQCqrwG13g4nJIKH
RfAZxo8YIrgDLRULpUNngxBlCwREUtNg0zmSYqQeajcS4ucopEW1E0j1nFGOX5Aly4aQaQgFnFgb
9HjJwXqDOJU/WSY0dCiMZyUGPjGBuqCryg6F9YPUcoe9vw2rrveSbUpqMaR21XePOGxgiIFkmp41
nqdOp8bSesRDKsLPKDoX0YfE0AAKqAPlX5VwZ0RNHuJee8dEEqmqvKry5wT3kBJu46c/if3lz3j9
ApQFQF+XE19O8mCLa0sbA5ryvgF8CYO6MaIBGBdPB/8ADcpwawgPhifn6heM3PTnOJiEByqw/eWe
gE0BRpCpOSnhcF5YCuxgedK4oEqpaOZS6+Muk+ijwJc8gehQ+5nDTU+nf0DyeZiDgfzjpzlPOT/w
yxqF6ypm/jPze8AKynRecduq5ZJ1+s9B+cZrft9CrpJq5AMRZq4knvGDvesWq8XA0XY85A3A7V/j
KkluzzMcQao/SP8AnKEomgYfrKDBp03Lm9EdBD16xFRAgklXlcOHyEaJ6xb+t95qb4u/WXzCecXq
TXfn6bC9ObODHD6UBeH9ZN3z1ibzwOXDJ8YUGHOsF2xjwT1dGB8+svjD9T+//k3g0OzafkMtSQ6p
Vwpq62F1p21FnxkDuHjdJiiGvjQuy0VVBRODF8wRQI5jwylnGBBdp0s3ykTCotnY1B2oIUpH7XCc
yFtcFEohsKlIGG+JAMCApUqgWDs23FMhEVAojoATg2vNxTGKCCC+EdeL4yJEjegKG0Q0Ip5M0gWB
hBRUS8gb4pkZpQEHSkDcei40I9MhAjGbdhtVXjJfpgYEBSpVAsHZtuLMdQavQ+mT75INLjCBQArQ
OtvRggGgQoFnVqxOraodoIARYDyr0YnMBRAQWtWqDmnjCZs8m+1FICUZpnjKUT/o13yoz3X6qePp
DeocHLjKyTHfdwR0TjNOuTLH9zAEa7wq1L5xEHbDFGEk5duPxa7MS7D7ecVuDMg8W+MhCT5xFks7
wXQAfGce8DmA2+/RlaT7Yz1k2ILubb1iKBoIvMv94otGvbvAS0I8mbChMel94jARZ2pxvEJlTWg7
6nqY7GR3vFFpJHH4mA0pBYPWJFMWyLD9YnvefbNATscmAKMQKm8SfQN6dfOLwDK9J7nOSLdnWAqp
TH5ciYN+J/D9Osv0V4IkijhE4cowlqlMBVeYAvMDLKn5giIFkmp41lMbUhXnlMW2aoqssOCwvmYF
hmpZZNR0rvx4weUtAI/dcYFUJgRE54TUxZyCpRdIvLe7musgAPNgzneKuUN3kRSxed+3FVaHZ1EJ
VIEwIiQXYQDuC6YzwmsRVEKXggsAAwByqvEhEbxIEFhijlClFIi8o93L6s2hTSPkezjGfewDzYMv
GGxURsNtG6tb5rnkRxBbYMuIAkhqeWHb7cgXkROSACVKVbJoXKcpNatqtaA0HW/LhnXv62Ome8dA
JzgjqY1Hiui4G4sxU1xMjLNHeIE5vnHRu3kw2tcd4CjhfbAhOY/bKFYe8QK0F1roxHAw98ucAN5G
7hgwIb7/AM4Dk8jyr5++DrhSrLVyqCuvYf5x+5TBU71t85ddh8d47D/OKABml8mHeNlFfWQGT7LW
A4Dp1esFzsOUzYTnuZpbH4y31jrUwlWVp8ZfRk74wfeXnCA+ZrOcUk6wEFOcQNNecsJnxGH6n95M
m8f/AKmsP/qZxrn6PnIjfth+vGO/Rq4kcsr24Do4/wAZNPk+rs+mGBcmXWKC3FH9YpVe8vIg+XNe
d/GbQZFinjEjDgpiEIY9e8nqFd66xeR++VK2PVxVcFF4XATTc/WUoPV3iaFT56x0nSCTgHv5yyUn
GsS14VyAbvvE9jI50M8Yo/HjLTpdnrIYYCCvvxiKF2Uu+DEUQ9oP95yNH2xXLmVzp9jNqZRHeCh1
jt+MrJi5NXDOPjrK5T/jFvvBF3ZlaP2Modd5/9k=

--Apple-Mail=_28390993-0824-4076-9BB4-A393B4240961--

--Apple-Mail=_80F7AF02-A57D-492A-BB1A-EADACB4A44D8--

--Apple-Mail=_63A6ECF9-E510-4CCA-9FFF-1FDAC57A3B98
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-----

iQCVAwUBUwxQBdZcnpRveo1xAQKlSAP/fDZsKqrjHPSqmZNeEJ6tSrPIRMFAzo0f
cPOrxwSH/HaFbg7gjsSvnt8Gt1NpKOMWyEoXrv+sV8Pb6rDdNui9l3+O0DZoU6eo
csoIzn6VrgoRaQiLs+YW/PxbsbAR8GHQYx62EKOQz3/9624KIB5fXljVwk9nYsO/
qxMkzoAgHC4=
=C/Cg
-----END PGP SIGNATURE-----

--Apple-Mail=_63A6ECF9-E510-4CCA-9FFF-1FDAC57A3B98--


From nobody Tue Feb 25 00:14:31 2014
Return-Path: <ggm@algebras.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 DC5ED1A036C for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 00:14:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.719
X-Spam-Level: **
X-Spam-Status: No, score=2.719 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, FM_FORGED_GMAIL=0.622, HTML_IMAGE_ONLY_08=1.651, HTML_IMAGE_RATIO_02=0.437, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_REMOTE_IMAGE=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 7Ube5v-3zmNn for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 00:14:28 -0800 (PST)
Received: from mail-pd0-f173.google.com (mail-pd0-f173.google.com [209.85.192.173]) by ietfa.amsl.com (Postfix) with ESMTP id A2E761A0363 for <ietf@ietf.org>; Tue, 25 Feb 2014 00:14:28 -0800 (PST)
Received: by mail-pd0-f173.google.com with SMTP id z10so2274259pdj.4 for <ietf@ietf.org>; Tue, 25 Feb 2014 00:14:28 -0800 (PST)
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=UInjMQ51j6gf+rhO6D1HgkA96LL3P004skpXF/hyY2Y=; b=YWTsf9Mw+DMricWaS2JtFBsv8EId0Ny2rJ/jE0qbF7GEMUYy93dF6cLDMDpaKF86Dx ejExoypHAWV/rCFh2r1mPIfFwYA1WpGY0TqvdeOoEFcEl3J2rwcTo2NvfN3yXgUOVGQ8 wqdzcoO3ezX9N0Nje8D2GSDmmd9BNZIIKfJJbSwEiMorLrZvpL60ewTtSgm9VFQClAvE A5DgfHwUSBDwyUi5ogejKuvgwUEhtA73W75CC+tAmUSfNHfZf7u+VYU7VwCUdMCk6Ln7 F/12uX+5XGjbabh7gXpZG6klUtacngLe/NP48xsI0S1ROfBEiR0RV3QAKMKAhwHuAjnw U71A==
X-Gm-Message-State: ALoCoQlqIPQY/u+jQahvom1U/Mvxy3dIDt1kPzFLlFKLDqYAUpNMdqQjYvOhd3fht4JcdKsYcVl2
MIME-Version: 1.0
X-Received: by 10.68.29.72 with SMTP id i8mr5179687pbh.116.1393316067817; Tue, 25 Feb 2014 00:14:27 -0800 (PST)
Received: by 10.70.88.203 with HTTP; Tue, 25 Feb 2014 00:14:27 -0800 (PST)
X-Originating-IP: [220.247.147.138]
In-Reply-To: <A69B9723-DA0C-462D-92A6-001B7EFE3DE4@netapp.com>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info> <00D21295-2E84-4CF1-9ABA-E2024D245580@cisco.com> <290E20B455C66743BE178C5C84F1240847E633472B@EXMB01CMS.surrey.ac.uk> <530C2C78.3050602@bbiw.net> <290E20B455C66743BE178C5C84F1240847E633472D@EXMB01CMS.surrey.ac.uk> <A69B9723-DA0C-462D-92A6-001B7EFE3DE4@netapp.com>
Date: Tue, 25 Feb 2014 16:14:27 +0800
Message-ID: <CAKr6gn0JRcknnzBq=s-Sbt6yDECqwj=H+HLMzVVcXO2=KCLZyg@mail.gmail.com>
Subject: Re: Ad hominems
From: George Michaelson <ggm@algebras.org>
To: "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/related; boundary=bcaec52160c948fee904f336ad6e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/J3A4uGAMiSjhUsDJfpX2zB9LPIs
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, 25 Feb 2014 08:14:30 -0000

--bcaec52160c948fee904f336ad6e
Content-Type: multipart/alternative; boundary=bcaec52160c948fee704f336ad6d

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

thou shalt not ruin a perfectly good bar fight by introducing logic,
clarity of argument, or fact.


On Tue, Feb 25, 2014 at 4:10 PM, Eggert, Lars <lars@netapp.com> wrote:

> I suggest we use this as the new Note Well.
>
> Lars
>
>

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

<div dir=3D"ltr">thou shalt not ruin a perfectly good bar fight by introduc=
ing logic, clarity of argument, or fact.</div><div class=3D"gmail_extra"><b=
r><br><div class=3D"gmail_quote">On Tue, Feb 25, 2014 at 4:10 PM, Eggert, L=
ars <span dir=3D"ltr">&lt;<a href=3D"mailto:lars@netapp.com" target=3D"_bla=
nk">lars@netapp.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 style=3D"word-wrap:break-word">I sugges=
t we use this as the new Note Well.<div><br></div><div>Lars</div><div><br><=
/div>
<div><img height=3D"679" width=3D"637" src=3D"cid:61260F18-5AA2-412B-B26E-2=
6960AC835C0@hq.netapp.com"></div></div></blockquote></div><br></div>

--bcaec52160c948fee704f336ad6d--
--bcaec52160c948fee904f336ad6e
Content-Type: image/jpg; x-unix-mode=0644; name="1483220_718769974810683_97803309_n.jpg"
Content-Disposition: inline; 
	filename="1483220_718769974810683_97803309_n.jpg"
Content-Transfer-Encoding: base64
Content-ID: <61260F18-5AA2-412B-B26E-26960AC835C0@hq.netapp.com>
X-Attachment-Id: 4532702a47a56403_0.0.1.1

/9j/4AAQSkZJRgABAgAAAQABAAD//gAEKgD/4gIcSUNDX1BST0ZJTEUAAQEAAAIMbGNtcwIQAABt
bnRyUkdCIFhZWiAH3AABABkAAwApADlhY3NwQVBQTAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
9tYAAQAAAADTLWxjbXMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAApkZXNjAAAA/AAAAF5jcHJ0AAABXAAAAAt3dHB0AAABaAAAABRia3B0AAABfAAAABRyWFla
AAABkAAAABRnWFlaAAABpAAAABRiWFlaAAABuAAAABRyVFJDAAABzAAAAEBnVFJDAAABzAAAAEBi
VFJDAAABzAAAAEBkZXNjAAAAAAAAAANjMgAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAB0ZXh0AAAA
AEZCAABYWVogAAAAAAAA9tYAAQAAAADTLVhZWiAAAAAAAAADFgAAAzMAAAKkWFlaIAAAAAAAAG+i
AAA49QAAA5BYWVogAAAAAAAAYpkAALeFAAAY2lhZWiAAAAAAAAAkoAAAD4QAALbPY3VydgAAAAAA
AAAaAAAAywHJA2MFkghrC/YQPxVRGzQh8SmQMhg7kkYFUXdd7WtwegWJsZp8rGm/fdPD6TD////b
AEMACQYHCAcGCQgICAoKCQsOFw8ODQ0OHBQVERciHiMjIR4gICUqNS0lJzIoICAuPy8yNzk8PDwk
LUJGQTpGNTs8Of/bAEMBCgoKDgwOGw8PGzkmICY5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5OTk5
OTk5OTk5OTk5OTk5OTk5OTk5OTk5Of/CABEIAqcCfQMAIgABEQECEQH/xAAbAAACAwEBAQAAAAAA
AAAAAAAAAQIDBQQGB//EABcBAQEBAQAAAAAAAAAAAAAAAAABAgP/xAAXAQEBAQEAAAAAAAAAAAAA
AAAAAQID/9oADAMAAAERAhEAAAHxLiibrCZAJusJkAmQCbrCbrCwrZNQCxQCxQC0rCbqZYoskoBJ
1smQkOVLJOKJCiTcUTcAtUXF90Thp0Wc+oTpfaTK2OIiaiy6zn6eVsqsrzalWd8ycEWRgxuDJqAT
K2ScUSdYNOIMQAAADQNMEwAAAQADTBAAxDlFg0yKkhTTIgAgHKAOSCLTAUh2VdeUq5189Om7n3Gw
3IxENpE0Mldz34oyEtblHeYxkqUoyHGSHGURIBuIABOE4AAGhnh9Az7eA4M/2fQeJ4/ceHPaYuj0
EvG+o86ej6LPPnBb6aR5W301p4+70V55fj9tM8py+6DxtHr6jkw/VB5ej2UjyfP72B4zV1Ljx0PR
2HjdCj1B57b08g4ebR5jO0dq7LzMvS2y+e4/U06nka9XIoU4khMi2g6+XqwlTYsajDo4tyUG9yJJ
CnEJwJFckhpghonCSEANNGrVns0bcgNvFTNCjmR6PzgGr2+dDR7MJmmswNMzQ0ujFD0fPiBp2ZDN
3kzGaRmo9JxZAaVmSjfpx2L0XnWd8eFndueWZs34k+d9N2ePcdHd5+PSXUxdMaFKLAnWStiovlB8
tPm6ubUg0dI4yQ4yQOMhRkBFsg0yUJwAAByIrprKzR5CgYCdpSTgB28YhyIOcBPp5yMpdeXC7+pc
06qyk6Q5i12VRuRBdHPQO0ri4hJImp2RaRXLTj0UVyu1dc1ropE4zENkJwmVyJl81bw1zw6bNTOR
b1lKvpAjITsgRJwCPRSJWKFGSoTQNM0c+cTv0/PM3ubMDs0/OXGp1+b6DT4+Os9BViyOrX87ab3N
lyjcjk1Yvdo+aem7HBsTU7sKs3oYli7FuRHDr7Mawn15XTXTPNeprPAemh3+fvjbxZR53RM+rTaz
uKvc3LsCwu1/OdBtRxOgu0sKo3DDkbcc23jb+vOqjsp4qu836Mew15YV0a9mUYutXnUmzh3RHTIj
njOHWCGCGAAJoYMSYMiyUWyJJkVKB1SUOVqQukAVMTGgCUQm4KLbeYjvOSfO2y5+hUpOOa6D1LoV
1xZV0c+kFJdJN0yJImIcScIBZOMi+VNnGyUYywqtu3OeciIXVC2SoJLVTDS6kjqJwlo4ygDQF1PU
Onr4Tv5erVPNHouYxre3UPNR3OsxOXd5DOlvVmNV3bBhGxZi+aPR1amCvUwrzL9Baeae9aYFOvaY
b9DymUvQh549LE85btXxh26Zm5NPocs4J+j4YzIb6PNnqa9zzMvSZ1cBrUmcblp5yPpuUyDa6Ywr
NyjlcePRraefno9MYstWOmLT6fP1MuO7CshNCgMJKI4ziCYE6w6aYhKUqC8o6ii+iJZbzMsjFFkq
bAdaLba6o6YK3NnyWU7lr57wjX1FUunkIyrZOVAdXTmM0+Km8hKNo5c/Vzsr+W3FpdEdzpsoct/J
ZOSHP28uzsovs6oVR52TVa3RqnUnZXkc9vJ0k7uaW5dBIdtIREgAGNDi4jEw0M+Zr9Hn7jeWAjQ6
8ORq9fnJm/n58TZtxA368ZHoc3PrNbs8/M6trzE42L8iMulZiV6j1cqw7+7AD0VWJA7e7Bma/V52
01+HPD0vNk1HpKce/F7oc0Yp5LqtQtplXQKfOyjZXmklIjKFVk6UukXbyXS9FNtXOvm6+TcjOJ0k
osFODIpggRJIJxlEAQMAYCYgaYmIaJBGcQBA0xAhtSJWUyyv5ukzeePWq5HKG5IQKUWJSQMABl1k
pcdVWwcUVXXbnJ0xlDnCeaq4w3OiFIWzqthU2xK+gkSrsWKuXop3KlNdY1GQSTKyURIYKSHGcRDB
X09BOnRzDu5evTPNP0XMYtvdpnm1t9Zi8W9xma/Q1mJX36Z5+PpLDzD7tY829noMh7fDzvDH0PFG
RR6Q3MKr0VmnmHt3GDVrdp5uen2Hnp+hsjIhu18tYcfQ16mPZtceXDRp9W3nYaGlqYlW+VhVehiY
F984gtKzNyLtmjDINTNiuroZyRku8rlNBBsSsRTMQiYRTiNoBxC+FbLHWFxSidsuYnbVIiqwsmqS
+XOjpjUiV3Myy3nC6/heXbHmUvXCu+K0UbkrOd1ZbyssnROOpVPN6XzywvjBynLKrrm2VL0c4Isj
CB0Khl8qIl6ridNnDblo86ny1Misqar5dZTCyncGlTigky/KFsTF5ozj1ggH38HSbtGbUbPR5mZs
9XmrTR6MOw9DxZNZsWYyOrgtqIthEkgUkJiGiQ0IdtLjur5+rneNdFW5E6GsScsK5TpIOdlJCzaF
KPbLTBqLCNkRtBCYELYWkHGzLokU8dTijSbpsQGpaqeuHScvUrIVd9eS5yPSNNaIGIAkhADAGIYR
GCkmBFgSgEiJIiwaBSTAYJNkbK74mC56nEtiFCfSF3NcnRXJ8tVxnHShRs65UbKxMY5VyJFUhSlW
OTiPp5OjKaur5aUkHHIj2zfOm3FdkLedUVCjlur65UZPRQsrGmgZ1Ea9XHO/l6tU80ei5jGt7dQ8
3Hc6jF5N3jMye/AxY9uweYPSI829fQPOT7eow1vcJnHoLDznRtWxgPZnm4s+6szZ7OZS5/S0Zed6
N3mrNNuWLiQ2p2eXexX1mU/RM89HVsM2O3wnHV6TNMyXoGeclt9J5x7k4xp7dfO5MO/pPPz0u7TE
lsSyw4T566Clk421xTDr59yEZLQQA1Iku/mKZVovKLBXczJ31SIxQSdcSy7nRf1c/KdUabSDrZ10
0h1OiebZLngdMaJ2OdSrq5q7S98so7LM/s5WTgYqdUOkv5qH1lhWi6fOycqw6KVWd/LBF0a0X30S
jtio8NRdT0mU12Xw5Z9JdWFJtEruOzLsqLOWuKMo98pph38F5qduBWb0sW87o8XCb3NyRNWOPA9F
mckT0XNnc5trHDceGGvz50ygQO1W4rhGuItHSOVcwlCQpwAIMn18fdzqHTzs4wNKV2U7lMZw3LVC
QyMhIY62gsc8i4lzs411y2xJFVN9PXMG4aWEWSYAiIXc84hGUaGIYmIAAAAAAABuMgUojQxpBIix
WSeaq0rGBSTBMRZKMiLgA0iXdw9XOyqsqzWrCgovRVTkcseyjchOEtIyU4RbLNlOtc7fSqdSajZS
lZXLCqyneRWR0jODLCINRYpCCMojTQ7ae0rr0M07+Tr1DzJ6PmMazu1DzUdzrMTk3uMzZb9Ziw7+
8x47lp5rq1683Nr0O6zzk97mrMo1+881L0HMYq9EHnn6Kw8yduuecXoazD7Na3LIp078XFe8Hljv
0esw+jp6cXNr3ZZYC31WLZ12GVftcxgQ9EtzzstzErqW7x8rx073FLlnoaemcbm1u7TzVupA4KfS
TPMJgCkEJwBoG0F1cAnKoOhUMlc7zhv5QtjORXKVBZOjsKrCEOqMC5VlXqqJdKkLXGs6DmkWqhll
lKOmull13L1Ytqoni1aGabkZ09GorITzbIkMWwros7ZctsWc7jRVfHSEq69TvqRjVlnM4tonzbzY
6zSwpZa6GDQAglCUQGg0M+Rr9GLI2J4iPQeasgbvJx8p6JYrO+eWj0EMMO/rxyNLv86zZtwVXVfk
2noOXLRs9PnQ6M++gmkCJoQIlFhb083VytcpVSwtlAjONhXZRXqX1wnqRhM0JVKOi3iuzbCDlnV0
RyhV0KiuyFip6ubQA1ENkCUQaBpocZRAAGmIABgmMQ0DQMQCkgk3FQFAwQ0AMQwTUiJJANCZOK5W
uUnGWQMzZ1uFQjI6ZgN1CYCECjbAi2CYi+zmeb1oXK1uZoV3Ecke01ONWm5XGSqLTE2iUXEAAtq0
znp0M07+Tr1DzR6PlMa3t1Dza2usxePe4zNlv1mTX37Gb5W/eLPNGvfWDZ6PKOOrZ7TzJpa0eWPR
uPN2eimebe01xrdnkjMv7OswTciY9mvyRxQ2eaM6r0NfWYJ6HjMt+hqMI32YleyzLjryPPL1FJ53
qo3Tn5e7S5XBhthiFnEdhVZi1zrNCqRqQVk65S8qmMo6gAEki+uyASdJcVsV3OE7ua0UYosnQF13
Hdm2zqnlZRKqrUKJutFl3MFndlqu2nlCyzllqTUI10rnZfOqzFUqbDo51WWQrluWz5gvdCLyhHRX
GQToC6fPMLedHbfRHjq6MAjzdXNuRkjcmoqLLeZx0wqJemEJRTGS6RABoZ8z0nFnRNTowJm/yZUj
bn5yRr8lVRQNA0waQ5JFircTSRJIJIdRUkKcZCTiTi5EAZZZW8WyE1m1wuq1IiNxqQRGEkIHEFMi
E0huucdNd9XPRbGUR5Ovm3IprcGmDIkotiiwcZRAAAABiAAAAABiaYAAJgJgmACGNAAAmDTHFoG4
gAXW0TxZkFBBx0iD1EwGmhxbEDEJgJiamXqBzthUFnPOGohvSLTAENCJIRKLQ0AW1SOvn7OE7+Tq
1TzJ6PmMW3t1Dza2+sxePe4zNfoajFj3a55k9Ijzhsd55593SYNm7MwqNXvPNP0XGZS9NSefPRSP
OHf2mXzaegeclr3mLVpap5d+k5DEl6Gw80vScxjG9wHDb23mJZ6PmMCWzyGe/TUmDLW6DCl07B5a
30WUZy2Og88/T5Bnv0GUcbEAAJg4yiAA3G4gOZB1MuKLyu6dArq6iyMAtlSiy7mtJdOeHRFVFhWF
5zyJzpRbKlHVHnC9Ug76GO3nZfGAS0soLJUInfQix0hc6AtKmdNUAaSLVFFxSi2zlRfUmWToC2uI
dNEQAYgAkgIyiAAaWbM2p4yN6eAivdw7jVv85aX7HnNE7K8eRuX+ZuNuGEzS7cKs3cHo5RAxAwAE
NAAMGAgU4hN1yCIgGhtMIyCJKJKUJjREEwkhDUoiRIiwBiEME0EgAQBKIOMogMEANDE0xAAwGhAx
DEAwENDEAxggAENDEME0A1IQAOINMAAZGQmgaYDcCREGwItwHKIKTQ4yiCGEkyJIEkwBiUgcJRBo
C6nQKqdTJO7l6tU8yej5jFu7dQ81Hc6zF497jM2W/WY0r9Y84eiyyHJ6bnMG7YoMd+iR567V0Dyi
9HwGX06Vx541+880blpjc/pMwzz0fOY0PQ8Bxw9FQYJtcxTy+loMGe9mHNX6LLOB+lpMA9DExFtT
PPWb8Dz63WYXV06R5k9HymPboWGNb6GkwI+hxjnYCaBxlEBoJRZdX38xTKtF4UE7uZk7lzFsYhOV
V5XZVA7eWAX1wC9U9hUUoulQFkYMurUTsqpC5UhbGKL64B0VwCx1ok65FqqC+NUi6pI7qKEXSoCx
0hdGAT6+IL4UhY60XRgHTVUE5VgJMcWDjKIABoZ/Qal+NWbdWSz0vLiwO7px5mvRl9RsVYkzXtwo
Hdr+ZtNW7AmbE8Gw9BzZaOVgA2RJBFTCKbIkkIlECQIbEpMiSQlJkHIItoipxAGRYwGgcQGmAgGm
A4jSmQbCIwcZRAAAAAGJgCBoAaGgAAaAYgGgYmDQDixgiSaEIG4sAAQwlBkmmEWgakAAkRG0DQEo
iGCG0EhITQSTAQAIJOANoHGcAAC6nuK6tTINDk6tU8y/RcxjWd2mecjt9Zice/xmZL0EDEr0Nc8w
/Rh52PoUefltdZ5+dOqZsfQ8xkvQyi+rfiY3PvIw4+nrPO9c0Q5fRIwujc88VHVsmDTvWnnD0GeU
LazjOjvWGAvQ8Rky9DxHBVvSMB7kzz12t0nmTv6zFNzoPNnpInnbNiRiQ9BYebWtmEUwlCURoYpR
ZbDt5iuVQXlDJXc6LLuXpK4xtFKgLLuUOg5w6K6wsnSBZWFhALKWFllAWSpiXOkJwAvOcOmqAF1L
JzqRNQZYoItt5gvqgFpCJO7nDT4qAudAO2pFyqZY6QuVMiyVATUQQSCMogAHfwdBq3efmbnNm1mn
3YLNu3z3QdzyYmxdiSOeIxNMQMBMTAEwBoGmCGIAEwaAEwBgCYJhGSBqURsZFSQgBMkIUiDGIaEx
iaABiABSiNNEoyiAAAxAAAAAADEAANNBJAJoYMBAIBgCaCYmIYREwACUJgmCHEGkMQScWNoCM6yQ
IBoknEbSBNDEDcWSSAaABhGSJQnAABygzqn30GZoZ/cctHpuQxVu8hm37dh5ns3OYwX39xhWbHKZ
l+xAx4+i5jEt3uA4ad6Zhve4DJfpEeeNXQPNPeZ59ejyjPfoOYyH6QPNm30GBXv2nmrNK8wjXtMR
ejmea6NpGAvRc5idVPoTzT9Czzl23M87HbuPPT9HkHJVq9RgPatPP3bnGcFG72HmF28I0BKEog0A
FpGylFigFsp3nJCAdEKryVdQWKAXwrmWJhKqVRYq7hWc6OiusL1UF0+VnQ6AtqiHRZyIudExkIlz
qZIrC7o4WWX87i22m7nSm6ogivpJz53VpXEurgy6uKLVWFllAXwqZ0wpCcABoHGUQGg0s2RsX4dh
v+asgbsMys9DXiVmx1+frPQ2ecvNUzeY3c3iRvTw4m2sYNSvigUIAAJOMiLbIiABgmAIGnIhIBJo
LI9eVatrxY1OHSStpR0ShbzvKujm6RSTqLlEEwbUSSAUoyEIJIYgkKLQAAAAAAAAAAAAwEAMAaaB
xmRUohKMiI0DUhNTIpxJCkIATiDamQBkoyZeSjx0ufs4txxtp3JODLLqL8V09HLEZVz6RwnAGMim
gBgJgIG0ADP/xAAyEAACAgECBQMEAQQDAQADAAABAgADEQQSEBMgIUEFFDEiIzBAMjM0NVAVJEIG
NkNg/9oACAEAAAEFAh8dOZmZmeGfxZ6MzP4szPRnrTMMEsMEzM9SntBH+c8RCeOeGZnq8f6Lx1Dp
HzD8Zjnv+BfmZjnt+h4/0ufwZifO4RzEhg6cwTznEyTO0zB0j8fj9scD+igwsP8AKHrExwEPBvmH
iPx+OjRtp0uWr0xtHpE0Os19mhvLVVPa9+mu0/D070ffNDo/da1NN6frCRg6TR6evSJX6dr0Sqx7
L9JfQF01zo+i1KNfprtPBodSWXRalnsret/+O1m2um22HR6kVU6e2816JR6Wuk1DD2Wp5t1NlDV6
LU2JXTZa40OqKemenDVVro9Q1t+mu0/CvRam1NNpbLtR6xpqNMnpNNd+t11a1ayut7Xu011S0023
M2lvC6pUXQ16HU2oVKk9HmeAJX8HHDx1Dgevx00//jn/AM//AH/p+qus9W0orq05vof06f8Azv8A
e+hEe/8AQa2HqGoIbUatTqPRNBoH1renfZ9N9Kss1Glpser/AOfOpu/4HVu13oPrOoupr9c1N1T+
p1u/q2nZf+T0H0+o+iai3UOrtT6BTbbb6FqrrKfRfUdTcvpmuAuXW311a2hq39b9P1V1nq3pjML/
AE7V7dNra2b03TKraj1nU6irXeofR6p687+99C/yPqYPv/S81+mel2Pfpqtyehq1reiahVb0/wBW
1Ooq1/qTXtqenPDMrjfOMxv48cfpLrrF0Wj1T6S2jV2Uaqj1C+i/U+pW31TRat9HbXe9V93rGptr
mj19+jmp9X1F9ek1dukfUep3XVe8s9mdZZ7JtZY2j1ess1Y1mts1Zt9Svt1H/L3cyv1K6u7RayzR
to9fbpFt9Uvspt1llumv1ll+n1GssvpX1jUBatfdXqqNXZRqaPULqNQvqlws1PqFl9UT1fUKrau1
9Tq9S+qt0mobS2/87qonqOoXU3a+6+n0sstWrvNeh1GsstoT1fUKL7nvtx0Z4ZginB3TxgmMMHEE
78PmYmJ46vH+oPEcF+BmeT9M8/h8L8sMQTOI3z36AekDp8f6wxR9IyYfk/HTmDqPaARo3wMwniJ3
4CHq8dCgsbqXpZF3M+l2JbWarONacxyMGe3biBkupR4KXLQLmJTuGIunYkzM7TsY22YE2TaYlZc8
KkNj9CdyyEORDCuEY9lQsqIXjVlUxwHRjsO/Ad4w5ZCmwppja5nL+01ZVeHzCnafPBENkwZsPDx0
6rJJBB1H9C61n1ClxeyZh/yAJtc2PdU5JUzRnbKzzZXbY1WsLPq3JKJdb7ilrFrt+2yZLavO9bWN
tTc5bmDVaUsunTBVWVra72NdnMprsPLTVEmd3TSLiUtab0L6iq5uZpbHb3ZG+wW6gjd9zeAx3GGy
2vTaxQKrHeuaB2VhfYlf01LqQDqXJK7s20PY9YQiuy1ufX91gy2MLGavVl3uo7KDVTGU0TWu+FsZ
dQDbXLG5QstJcnllPuTAtjXtyD/XxgnsMTx07jCSSSTN7ZFtgQW2KuSWa61puM59xm9oCRNzR7bL
I7M559xiu+0W3QWvlrjk2Njm2Y3NhrbHld7V18195tctVa6RGZJkxmzOY5QblJZiRmWPa0Flqu1t
hj2vZK7LC7ExmJVLbFPMsrIssBVmQ7mMFjrPJutiMRZdqN6PZY43sSS2OZY7ITt3tEfZPk821H3F
iWbcllgQFooMJMywZrGJ7leY2095mEzx+qv8YTn8e4zdMjpHwQDNkXsIZiN+QRIOLibZjiMzz3nz
MiGyZP7Kfxb4/MGM3xD3MHDOIDCwgMzmWHvM9eYIJ4WZ2zMMyRARGM+RnhuAm+ZMPT46K0ax7KSi
ou5n0uxLazVZxrQ2WEYM9u3Edy6lGlXct8fgesp0jo3ETfB9UtUqZ8n5O2MpMwZjgBkuux+J6EhG
S42u64bGTjEPeKpcEz5hQhOHn8NCu9lrDYQQdR/b3Ws+pUuL2TMP+QBNrmx7qnyUM0Z2ys82V2WN
VrWZtU9ze4rY2NpydgwsvYNTY1h16tm4sHHa83uGptsZtRrLHdA1lVWpYU1aPatOQdScrcRvspLX
VBrXquKZ3ObXduXv+vWEF6Awmi/uac2rY4auy0jVbTmnLR7Gs0mmsK08tve3NzNJa7e4r3uulXFY
us5QALowawWOatW5OqsYodV3m5lvDiJZc63FAdY5iMXq32WJ1eOhHZC11rwksSSRvbItsCLbYq7i
Sb7Wm4w33Gb2mSJuaPa9kdmc72yHeJbYobcVeyx5fqbLW3Nl7Hc2XWWR7bHG9s72KrbYgydqMyEu
8W2xYtzbrdRuWzUhqzZYU3vua6xoltnMbLMLLcVvse212jWO6Cxw3MZi7vMEhGtpm45a+1pVZ9y2
wvGssyMze2S9mdxw25juYwkmC6xVLFo19hHNdkYkzc21rLGB6vHWlZccEpZoRg9SrnjsPLgMWo2O
UOzgyFUldLWw6f6XUp+CpGsdlwyUM42/Uvxmf/rfOVaeMnGRBPHLgXvjbGJjd4c7Z2gXDTOJnPE8
M8cdB4eOjQ/3PubfaPmu1gvPAHN1bBkqscobDdXeUylh51tjW6OgrXpT9DudmobMBrU2uV0iO3sS
XOp0eQVdufvtfRvkqWtV6QpoZWgVwv02022MLaGfmUbQNV9oUsyMGa+k/XS9xazRO1c025XQ7TpA
UO6xBWBbSzZob+ME3TaIJnsTBMwDt2jPMk8AY0+TjEI4eDCIOB6vHQpKnJwt1qnmWGCxxHdnK2Oo
3GG2wpvfOThLHriW2IebYCbLGPNsCZJAdgDbZsR3rPNsM3swa60zmWhdzQuzRrTh7rbIbbGgvtA3
Ngks29s7iB7i4zcYGIAvuA3tFutADvs5g2M5aNBwUGKvZY0Aye8PaAzGZ8T4nhcw/A7TvG/lO8E8
CGDq8fsg4PzMbgQYAYeodaiZneDvLBiDMxF7Q9yBDmYxF+M95mYEIneKvAifMbKkcT3/AA+P2l7T
IncgR8GMMdR6sT4gMaFS0XGGhyAsLAQvD3mZunyM8PBPEdge0cHAhh4Dhno8dVaNY9lJrRBuZ9Ns
S6s1Wca0L2YwZyG4gZLqUbrrrLqyGsz5L8LKyh4hCy8D8QDgeDd5UrMVQu4Q7HgbHBKy/BE3uw2t
KgbGuQpLKzW2O6gk54OJ4PAwdXjh46KVd2s+rRkYOo/oXWs+pUuL2TMP9+DzXNjXVPkoZoztlf3Z
XZY1etLNqnQ+8yXQGtTpDi9Dus9xb7R8122fz1Pyrnnhd1d1jVV2uTaXuFn0VBn5envY2pprHXTK
XW/R7Rq0t/6+dsRjyw+FRwgxyUZuWFdt+kYjUnUWLpGKq2s2l6tsUmmV/dlLNYFK11apfv0j/q3P
W2sL/XY2ywvbXHxWs7xvg/HA8Bxxx2meOgEgtbY5JJJJI3tkW2BBbYq7jlrrWm4w33Gb2gJE3NHt
eyMxcm60jnWbObYEBKk3Ws247Rbap5rzdmM7ZrscKxJjb8860BbXQZOGutZUdkgtsCKxUrY9crvZ
E3sStjqEd0m51JJhsZW3HJdnnMdWLFiC2OY03NhrrGKWuh3HCW7UyQwtsUC+0Guwx33T442CDqzM
8EmZ4/G9RraAbiybeLoU/JngG75hXr7mfHH4heZjn6oOHjoAgnn54oYPmZmRMZcQifJ6FUmAYijv
gtPHRo1BtoLW1WNzaXtLWZSt03AL91PrdOa1jKx3V/eitbdU9pazUdq/yDghgjiEY4gZmBtm2eDF
yZtneH56BDwPxjh4gEPwkXgYIZ2E7zZmEYJ4CuFeBPYmeOil1Rr7zZGusY7jObZs3tuN9xi22JPc
XbudbkuxjXWMUbBsc2P+dWxPkHtNvcJ2yJjvmFhw+YOw7zJEIzx+OGYfj4IGZ8TM857wxO5+Bk57
gssVp/KfE7zOYyQDbAYewLLx8fr56R1A4hbt8DME7Qnv8Ssz5jT4ncwcMw/PD/zMz54+cwRPlpjE
xmCeQe+7ce4mIvwZ2jMOjx/ogvADMIxBCp4fMAwBGm6Hh48dB6yMSr5mZng38hBwzwMAzNv4rKWr
RF3M+l2JbWarONal7GGDPbtDwAyXBRulELxqyqQ9AqLEptUfB7xQeVvgaD4YTuIP4KIZt28TwHBo
tW6vb9Lo1Z8Z4/AUbjX8mY+lO5bGTlmKbWWZ7sJuAh7zx8ww9pmHp04Q26pc0EEHU/0LrWfUqXW9
kzD/AJAE2ubGurfJQzRnbK/uyuyxqtYWfVuSUDZtoax61T7d5TOgdkYXWJXsFprfm67L2MSx1OS6
VsVer6ppy9ga1rKdKXXTf1E1B2GnM07HZTu2lGItdq0tYmzO2KeZHayzQoz1aSw8tFwW1TK6b7Kq
r22U1dtM9rjU6zJhe5bMqDewemy1ufWxsbTMdi/QivsGCuuR9i96tVbYyxATq0YJXf8AzHBWhzwY
fSRPHTuaEkkkkb2yLbAi22KuSWa61puM59xm9oCRNxj22WR3Zzz7jEf7l2o3o1tjg2WFFYod7GJd
tSp+Xa91lk32FedZs5hVjYTDdYx3GLY6Sq77xJZ+daAltgC2WCBmVSSZkxnaK+DdqN6V2Oh3mB3B
Ls7JZYsycAnHNsEZ2cvqbGhJw1llk3tkM4lVtggZlAsauZ7pY6FTDYxPOdQttiTcds+YYrmDuTMZ
njp9qQLqjUeLLt47G2WVmqzq5bA8Nh5fETbiCHtw88PHD5h7RTD8QzEeDgOrx0Dgv8pjvFEPaZzw
HQfifEDbierRf1iQmnbaHO17Ki91SPdZTbZy42Zqmc6aoty1tOoS11xpfpRGc06aocuxubTfYbKd
Q7b1LpqUdkNhHI4gYnzCQs+Zjr88RCcTMaYx+YAmKuOBhnxLO/DE89Qm+eOip+W41FyhbHVkt+4+
pDtbqSy7iRVcFN9vNbm2AZOGtscI7I1modi1jsXtssj3WWRrHac2zZvbNlm4cB2nyS/HPDxBG6B8
9uDZJHaZmAY6iEHhn8AXM244Z4Z77p2lvb8Jg4eP2hDCeHjrPFfkmMYePcRofgp1+NvQYeAncSz8
J4+P2MT4g/Ov8vmYhijMZcDcREMLd+82wr0bTBMYmYpm+eTAJjEOY3xB+Lx0VobHsr2BF3M+l2Jb
WarONa8ywjBnt24gZLqUeWVmuKNxiCbDi1DXw2HlhCa+rPT5QM7BftFe2ZZ/GeQRFOY3wTAsIE2k
Ush2d8pXumZniajM942I/wAKmURS44bDy7UNVmenx0aXcLrBzNKQQdR/QutZ9QC4vZMw/wCQB5rm
xrqnyUM0Z2ys82V2WNVqyW1l7XczuH/lbS7ItljNTprHGmWxvcaQskd3XR6RnXSphkGyyxTffLm5
mldD7zJdAUU6Q4vA5jadntHPfkrg2V2ffFtqaa4DFlhOoRnGq0i51NGb1se+xbXuFqDdq6mxFfK/
+tQ1jaIvdXprSlIe0qFLi8FZe4ekqVZmZW0x2wXPL1+xY3KdmsrXQZBo+8uoZX062P8A8fdYz6gF
FPR46ASC1tjsSSSSRvbItsCLbYq5JLX2tNxhvuM3tASJuaPbZZGdnJtsKC2xWFrw2GbmiuyTe2Rd
Yq82yJY6TmOWax2Z7bWLX2tOdaV51uwW2BAxUtbY7NbY5ycB23b2Z97NGZpvbcupFSjObLHsLW2W
AtYaw9qqGYQM6ne25rGeLa4iuyDvOZYqlsx7bHjubHLuCGM7iJY4htsVha+Q7LHssdmsewhmA3tn
muE6PH46qWth0p4lCE5Z5JrIq4VadrI1KqqLvYjB6yhCZ/AYvyADwJ7D5fgqZnxBMxY7QNMiHGIP
ntCBNvBu4HabswEiN3X8I69EAb1N+olzczSuh95kugNakg4o+lkuqDbn5rFuRrLH2M6VaY7S9Ob0
ey+2ushLKtrWbu1DMK6sVikJZrN194P11EHnMW5OUrd+2jg/BX/KCGYhAM+CvBe0ZhiGDhvJg+e0
2xe87zE29u4gGZ8HH0wfi8dAOI1tjlrrWhutK863YLbAm4lTadka2x1NtjKzswLEze257HdjdYxQ
kKLHVjbYRzrNgtsVMx7bHLX2tGuseG6xl5tmy1+Y34UGZ2jHEEExid4CAGaEkwcD057ZBg+O0OYc
zbP4w5J/8mZ/F4/U8fp4ijHA/PxBHm6d+Bg4nqEBnzw+Y0Q9/OzMIP4vH6ax/wBHEAgAhMA6FzHm
BD+M8Qe+OBxFh+JjMwJtm3r8dCIbHspKKi7mfS7EtrNVvGtDZYRgz27cVGSVKM3BUJr41obH5Z5X
ViFZidoyFJ5srNT5g78EUuQYRlmUozQdKjJKEVgZWyo1saircaqWshqCzGZZWa3zGg+OkiYmOPjo
0GPcOBZpiCDqf6F1rPqQXF7JmH/IAm1zY11TklTNG22VnmyuyxqtUzHVs2dV9L2aZ7bERPt3tdzA
UU+nsV1nPtTSHara3BspBBTG3NrVMp92thF6Nz0vYNTbYzajVWsV32V1ax3rhTmvqGBrssZtTomZ
W3WLXb9vWnN995VlJf3WizmnNqVM9lZJtmead9lel1A+xecNczNcCinTt9DKyyj6WTbbYp5i0uxg
+ivVn/sK2IHEyOoGAdzieOgdo1tjkkkliRvbItsCLbYq5JLXWtNxnPuM3tASJuaPa9kLs5DNlndi
bLHDPYwNthUWWbB2LMzBbGDMSxFtuN/dr9ycyzDO2d3ZrXsG9872Kra6qLrVZGbdn6AzZVmUrZYs
ec1yxZsG2zZTbyo1juXssePbY8a61ottiwu0LsYbHwLbAi22qpLbTadiHE5lhnMsQJayQjtxzibp
unzPiEw/GZ46UrLh12siFxACxZSrcShCdIMOIIYYBibpuneD4zgboXm4/gSNPPjdGPfgeGeGPxfE
J7hocz/zMTPVmbpuWeOjRqDZp2stq3utXMaut8ylnLGy0U3NyhzW9wmPb2n/AKn4N03TcZmbjM/h
8cVE+Z8RuDHPWOnHS2Z8TuYvwT2z1Y6fHQpKk3WsUtsQbjgWOH5r71utWZON7ZssBW1+Y36w6Fnw
eLcR+btwyJ5Yfk8f6bPFI3wIfkCHoHA8R1iGAdu07COe34/H+iHWDiFpuhaBv0i839t8LQnt+Px0
Iu5rKClaLuZ9LsS2s1Wca05lhGDPbtxHcupR+lELxqyqRULKiF/wZ4WVGroC5U9A6q6y/AjA6QMl
l2NbWarJWhsf8njoAydX/WIIOp/oXWs+pUut7JmH/IAm1zY11T5KmaM7ZWedK7LGq1hZ9W+SgbNt
L2PWifbvKZ0Durc+xE70yxmrbQbgdP8AeX7d0d9RajklEQnW6djsrxVXWtZ13MtdfUHZr1LreyZl
zmuqnHts2e4V29xvsqqvPKrckqlje4DW11oRXTql+/pyU0/3Cas508Oot9prf7p7m9xWTa1CkUNY
zDWMzaqxrG1wNan09iusNzjRuh94DWp0QB1GnZrZqLC9nV46AcTcdxJJLEze2RbYEW2xVySWutab
jOfcZvaAkTc2Hsssjuzk33GJZh7tRvRrrXhtsKKxQlmMF1onNs3K7LGtdi9j2FrbHBvuMF1oC3WI
qW2II1tjhiSRbYEWyxVLMZk49yAm9sra6DJwb7TN7ZS2xBW71wWMFR3Ql3JF1oG9pk4JLHcxgdhH
tsePbZZGdnLXWlebYEBILO7TnWkC2wJ8FrbGPX46K0NljDDBCa+Ow8u2h6krQ2OFy/Vsbl8K0Nj/
ALefxY/S8dHpzFdZS9gq1AwbjzVvKZIImxec4S6hLLV1Gn7V1b11IscMzFK7m5QyViuV1FLPsrVj
S153qWe5u56D+mZ46/H4T+Tx0KSpW2xFNjtGutZTbYULM0ttNk3HButYZODqgE3tlLbK5k4N9xG9
s8x8G6xjuOBaQn+mP6Pj/ajhn9jx/wDx/jorRrHspKKihmfS7EtrNVnGtDZYRgz27cQMl1KNbWar
OC0OW4CsmvjZWazxWotX0VVGziBkupRpZWayVwOHIfMAJLKUdhtbp2HluNrRBubjyHzxFZNcZcdf
jo0IzqbsWaQgg6n+hdaz6lS63smYf8gCbXNjXVPkoZoztlZ50rssarWszapyUut76jVfSVtc3VN7
hL3DU6VnXTd3p042rzrfbWfTNwD6ljZp99lVWpbZRpS66ZWPKa25Uv8AsK7tWmjlBLxLXemx3B1f
dVtb3Gnnubfaaz6dY9r89C9sdyatYzNqnfl3apcakNZ7xEJ1lRWulLBWLjYmmuyjAkLWxsi2tXXZ
upTXZXVPa/Pq+9NS4fT1s9WkcPy3yVB2kX2S1MP0eOgHBe2xySSSxM3tkW2BFtsVcklrrWm4zn3G
b2gJE3NHtssjuzkXWq1V2LGJZuY4GTh7bHCWPXObZvNthKWPXBbYG3tnJwltiDJxVcaqzY7FLbEC
WPWdxisVJtsLZOOdbvZix3tnewmTgksTY5CuwjW2NGdnItsVixZqdS6EXWhUssQJbZXA7wWuHNjk
h2E3GU3BJdZzLOY5m44ex7JXY9c3NOfcZvabmm5iOjx0fM9qQLqjUeDVlU41VczpqrNrHserkNt/
2njo0X9YkJp7+0qXlQ22ii0hY7BX1TF6VNtYvs2UafdXpCxWs2X5tPKFljUjSHYqvEVLKkf7Vjio
WO7VL9sfx1H+mPSPw+Oip+W41FwC22K29zEtsQLbarbmhJMFtirk4GoZa97GC2xVS2yubjjJwLbA
m47Utsrm44N1jLz7SDaeX+Yfpj9Px/sDB+94/eH5x0D97x0Vo1j2UlFQbmfS7EtrNVnGtDZYRgz2
7cQMl1KP1qheNS6yxDWSMLUnNssQpHrKIi73aoqnQ9DpDSwErQ2PVQbRwZCqcRWTKkNjnp8NWVTg
67WEqrNr9aoWVl29Xjo0ZIus2DREEHU/0LrWfUguL2TMP+QBNrmx7qnyUM0Z2ys86V22NVrCz6t8
lMl0yXRFJ1tVjIGc2VXlMqzLKLrTQtje4q+kalmNZJM3tZZQz2hFVoHtdSoI5mxtYCL677ebZc6z
uXVj7g2WZ0ZAvVABz7FT6KUduWNYdxR2SzQsfdIX1FVrczTahjamnc16XOZeS+mpAIoPPXdc9N2a
2Xm8z5t0QzfWbLzussS2xm1C2N7iorXSzGqoPcq/BoJeO73aQ5B4eOgHBax3JJYliRvbItsCLbYq
kks11rTcYb7jN7QEibjHsssjuzk33Gc6zZzrNgutC7mm5sGywpEdkm9twdpZY9hm5obbHJLYa2xx
zHiWWISSxjWO0FtinmWGOSxm9zNzRbbFO5oSTN7hgWBDMA11rRrrGXccb3y7tYdzQ2uzWakGsW2B
xbYHNtsGRHseyNbY43tne25bbEFdj1xXdTvbLW2FgzCEknh46W0ti1csirrNR4VobH/33jo0X9ZX
Fa8rlvSXvRrmt0+kblp/Tj4DIzmnT14rWyw6Y55wcjVnufzn9EcDB+146Kn5bkkzmPuNtjNk7Uts
riW2IVsdXs1DsTbYTvYK11jwWkD9rH+k8f7Afv8Aj/bnpH6fjoUFjZRZW9mnZFAyfafRbWaz0W1m
qyLp2bosQ1tGQqijcx7GIheNWVSBGZUrLj8eeLLjiR26aqzY/HkNnjVWbWPY8FXMZCg6GQoHrKr+
MH/torJUylS39gtre43WVVatAK9aMavUMbUutZ9TTnNE0P8Ac1N7isWWuvqDM2oLWrZUCRnmA2NV
p7XJu0DsrC+xK+9MsZqzoN2dP95c13R31FqOSVRSdbp2OyvbVWFDay5uZpdKWXTKx5SPhGsNVFrk
2htjgfXqyrpUdo1f11Gy2vS6nNCtuRO700AhdLuSM/K0v1Vs9r8+r70DK7JZlRZi3fbXXewpruKA
6b+Otsd0qsZBZYXpZT7zJdNZY7JzLa9LZspGrx7jj46SSY9tjhmLHcdu9spbYgS2yuEli11rLvbI
vuA3vASp3Ha9tjhnZoLbAgdxDdaZuJG9sqzIS7GC61ZzbMqzJGssdnseyPbY459xgutCrdYirZYg
+I11rSu41Vmx2K2WINxxvbIscMbbC7uzne0sseye4da0tsQ13siB7d+bDA1gVy5lrmxjY+NxjW2M
y2Mjb2yttlYydptsKAkQuxXc03NOdaV51uwuxVbrECWOhJz0eOitDY/RVS1sOlPRZWaz0gZNtfKd
aya7UNVnBULJ+kJ26VXM+IJ8cDmfyhGP1fHR6exXV85xo3Q+8BrUkHFH0tWwNS/bC2FdSvNrlpV5
an3xi5K3ssp3PzVsK6nQHbqaTYQwVraS0vYpEVr5vDr0D9NRmHhnEMzA26LnLDtg/lEPV46ASCzu
051pUW2BCxI57gPbZZOfcRvbK3WIu5scx963sWv1HMRrbHXe2QSIt1irzLCVutVRdaItgSprPt/l
8dR4YgwB2jHHSrQmN3Xjj9Dx/ovP5cSv+MIM+ZiZmeC9p8zEf54ePz//xAAdEQACAgMBAQEAAAAA
AAAAAAABEUBQABAgMGCQ/9oACAECEQE/AZJqDyKgaNQYq0qxYoCjPHCch+roV0aYaMZQj92pIpXC
fwI2qUVjpBwuVwZY8HyaV8KS4aozt46Q/lAdjD5f/8QAIxEAAgIBBQEAAwEBAAAAAAAAAAECERAS
IDAxQCFBUFFxkP/aAAgBAREBPwH0P6yK+7ZEe/0En8ER2y/QtXhbZ9CIv3tmoW19Yj5LNRZqLLXO
t98l4oorFlmo1LDdIuxb2J5bo1ljYuT879JoY1RY7Yoke98l9KNTSLGaWaBJLla+8WhFDxe2z847
FErw3XFJjs/GLaFMci286rIeRPheIjQxYoSRIRHyNCdGre3jVSG7H/BRZpGIcsR8rwt2nD7NO2ih
/BPytWUfUJ3sbx9I9b5YoUqE7y2PxVpYmaiz6Xwy6O8NUf4KX9JS/gmxLxPKRLril0LLQ8RrxXhR
HESof3FcDKEiyhR/o4iFK/A2UJbJWsLgfQnhIrLidc7Yo7piVlClubG2xRxHra1fNYlvmIsao6FL
FjkUKOLI9eJ/RcDR0V9w4lViissSF4WLhk8fkboci/6JPCFLP0j14GLin3ixmmxKsUOOLLER9Vjw
uyt7jj8FmsteSy8NGkooXfDWNJTwizVxssT2UzTsfYxLjjiijSVy0VwPvC4UMh62vpTFw0yhKv8A
hRY5MUmX+kk6EJFDuxff0f5IZkR4v//EAEYQAAEDAwEFBAcFBAgGAwEAAAEAAhEDEiExBBMiQVEQ
MmFxICMwQEKBsTNSkaHBUHKS8BRDU2BidKLRBXBzguHxJDRj0v/aAAgBAAAGPwL9pT7KP7hx/d/T
+4WnYf2HO0sL6caBHa/6M6wcpz9UG0qDhTsMhx5/iqjqdB+7DjCspsLndAvW03N8+wVNpiwjDQUa
Uwxsk+SqUdna5lVow6dVBX9L2yS091oT20m7iqNJW7Ywud0CmrSc0IPbScWkxICax1F9ztMaob2m
WzpKDdy+SJTqYouuGuFY9ha7oVd/R3wnWMLrdfBbw0XhnWFFJhfHRbQ+rSisx3P5JhbRcb9Mardb
l9/RW1WFp8Ve2i8t8lZTYXO6K8UH2+SqPqB4EcBHNGkKLrxqOi9bTc3svZQeW9VurTM8Xgmtp0HD
P2hOqbTqtubBwqrGCGtdhW02lzugQ3tNzQiKLC+Oic51JwDdcaKkRszmO/tDo5XsouLVDsHofaT7
tU8/1X/YVVY6oSzi4ei259xZ61wLmjICr0t7Xr8w5zTg+fY//pn6hVxzIP1TpHcaZVRzdC4wtndT
zZFwH4J1pta3mVtlSkZqAxPgtrZXc59O3V2UXMNrrtR5oVN47eTF3PVUXvNzrtT81sopVCyRJhUN
28txJhbNuoFS3Uq1+11KtbILQIbov+IQq7K1QvEc019Ew5zuIjzVc1SXQYBPTC2XduLSYEhbK5tR
wc+JI10X/DDVzeRd+SF21VmFsRTaMIvY1zZp5ubGVVY6oSzi4eQX/EGAm1pNo6ZKrDaG1ix5zWby
+avo7VvtnadHDI+apNd3S8Aprab3MaALQFsjmm174ujzRbcbYGJTfIqvj4ltVWn9rotqZWeX07dX
ZV1AkOJ4iNVVNUk5wT0wv+Htd3TUaCmMpOc0AC1o0Ku2im2nULdB7PPu52UNZYefNbymGkxHEjtD
Q28zroqlVlvrDLmnRbq1lOnzDBr2GpTDSSI4lvmGHzKLIpsu1LRnsO7ItPwnRGnDWA62oupEZ1B0
KNINp02HUMGq/okNsmZ5obJDbAZnmm7LDd20zPNU94GiwQITDUDRaIEKnX4WvZpAW8bRoNdzNuqr
VQ2nNXvYTnUw03COJFjbXMPwuT6JbTsd0Gip7OQ2ynpGqpUHBttPSFSpODQKWBCFzKT3DRzhlO2n
DqjvvI7Q0NuM66KpWZbNTJB0VR1lO2pqyOFbmxlOl91gjsaHMpVC3RzhlDaHm54IK3jw0HwQqsAL
h1Xco/gf90+u22X95sYK3Yaykw6hg1TxS2oMqf2b9Cn0q1ZtSvUPw8kzZyG2Uzg80Lm06hbo5wyj
UqGXH+5mfajs19PT9s+HuQ90gCT4INeIJEqC4N8Sg416WRI1z+SdTdq3HoNYNXGER07DkYZf8u2E
WnUGOxjYy8SO10fCJ7A37wuCjswtOzn2kSBAJz22t6H0Y6qw6gx2scfi0RATncm6o28hKY46P09j
qpVrtUA3JRYwj97l2CpyJhMM97PoAyM/l6BjkJ9lR5ndhQcFbN+4fqtqpHuBrsKhRYPUuDcRg9Vs
tgkSR/qRhl3re71yqbw8uDaze+3LVtDXZtItHTK2im4k2N7obDW+Sd/lh+iru5in+oVB7+J8PieZ
Gi3lQ8TagDXfVVJ+9AW0U3EmxvdDYa3yWycRgtV5eQXv+BsuK2h1MQ+8acgnmuI9VmNShH2ccEdF
s8mfVk5+aZvs+tAyqgO8cWnEsAtW0OZrw56aoVXzvbDkDOuqouhzja/LhF2EC4vYXO77W6+BTrID
94Q4tVVwhr+CfAwmO5uZk9VussO77hHCcaqq5uagbwqk+q0d18HrjmmXQ54qgC5VSXOfa4QS2I8l
XghrKU/DMKg8gudY4i8d48lTe/k+A7mtqe5zg8PiWjIGVUcGm7czxDx1W8fPFzWz7uczoNcohjf6
3l5BbW1piGt/RVLT/Vn6LZbTrM+PEnlrnt9a4cDZTg1tvgVtFNxLrG6BsNb5KnTgfZBwEautTHVf
7duStqJHT6ram4taCQI0K2d9XLrXcteioEl7zvhxOaB8lWk93LfDK5nhH0VZ3RuPmmMdULXghzoa
q7mDjFS2egVBtTv2y75plH4GM4vHElUG0B3xJMalRQgbyqbT4LaxjdgaRzlVDA9XSDfmf5KpOq8T
gxztJ8lRu3juObntAwqj8ZeLcd1FztW0eL+H/wArPZrHpg3HGikmSUATpoibjJ1MqwVHBvSVa17g
08gVM56oXVXmNJKOTnVZqv8AxXeOka8kYOuqGTjTwXG9zo6lS9xcfFZqv/iQ4nQ3TOiPrH51zqrr
3T1lEyTOudVE4HJRe6BplRJjohc9zo6lPa2QXEGQdFeXOu6zlXF7rusrhqObPQwpa9zZ6FEScqJl
W7x9vSVwyHeCuL3F3WUBJxn5o+te7rJV4e4O6ysvceeq43ud5lX7x93WUTJzrnVBvIKG1HgeDkbH
ubPQ6ouD3A6TKlriD1CEuOES17gTqQdez7V/TvJrny+PFWC/WSXukqHVHHzKJuMnXOqGTjTwQc57
iRoSUcld92nVOj4hCl2UXCo8E6mVLiT5om4ydTOqtD3Bp5ApvEeHTwRknOqOTxa+KGTjTOiuL3T1
lRJ8kWmZPecefZKwf2LlYPafYa+469mFn2Gn7K17J9DT3OF+vsMFY9oGN1KDrmuacS0qLg3xKDjX
pZEjXP5JzHRLfQawauMIjsORhl/y7YTmnUY7IkDzR9i2fiEj2WUI5otOo9DVT6ACcwxLTHp5UqEW
nlhRIMcx2a9jgIFguKx2Nfydp7W1hgnn4IUaQJbMyfiKgiCtm/cP1W1Uj3A12FQosHqXBuIweq2W
wSJI/wBSPBd6zu9cqm8PLg2s3D2wWraGu0aRaOmVtFNxJsb3Q2Gt8k7/ACw/RV3cxT/UKg9/E+Hx
PMjRbyoeJtQBrvqqt33itqbi1oJAjQ9Vs73ZcWvk/iqNOSwu8Ja/zWy0jFrsO8eJVQ7eOLTiWAWp
9Fw9TzEYiNVSpnu7oOiNTaqRh9VwqYvaBPgmFzy5gqgEPbBCqg7xxacSwC1bVSPctdhULjIslUNz
8WuO8ZTxSgTVcJ+QVV8ua4EZaJICbg2uZ6y4RjqnOaQ2kynwmJx181QcZc6xxF4y48k3+kab5okr
ad6MCOXdyq1P1ha1phtggdCqTG2gCmHGR/hVGpc8u3kXOELaXuc8Oa+JAkgJtodJbmREoUnExu+6
1vDom4BOcfJf/IyA9oE/RVA7eGOrQLVWwbGz3NW+KNYEPfu5Ybc6qlUqiX8evMWq9xlzamD8kJL2
XP74Ez5rdwy6/wCSqkuc+HDJbAHktptAmmDYI/ErZzUHEd588KkSNdoaq5wLXC3Hd8lvDN+6BkDn
1VM8RMOy8a4TXl3E2oIKqXThxW1FuDe39Ux3xOZkqjSYJpOAxGD1Wy0/geTceouW0ir3Q3p3cqtT
4ywAw2wQOhVOmIDbGk/gtkZUPAXkH8ltArDDRjHdM+0lji09QULqr3R1ciSZJQBJxoibjJ1MqwPc
G9JVrXuA6AqZz1QuqPMaZRyc6rNV/wDEu8dI15IwYnVDJxouN7nR1Kl7i4+KJuMnXOqEOONMqxtR
wHQFCZgKHvc6OpT+JwYT3ZwgZMjRS57nR1K46jnR1Khz3OA6lE3GTqZQaXG0aCUQx7mg9CrZMdFL
HFp8CncR4tc6oWvcI0gobwueAZguQbD3CZN7plOa2/i+++YHgrDUdb0nCDg4yNDK4qjjPUq7evu6
3KZJ80Gh7xGnForolcTi6OpQl7nR1KuuN3WVcXOu6zlXF7i7rKtExrC4XubPQqeaN1R5nqVc65x6
h0FMi4W5kukypNRxPi5RJg6oQTjQgq4udPWVClxLj4rJdnWStVYHut6ShnRQajyPNWl7rekrUlWS
63ogH1HOA5E+3dEcIu7af/6G0KPTOQIHPt3nwzHaGt1KL+QMdrHYh+nZw+XzTi2ox9uoCbPxCR7A
NGpUBwd4hMIjjfYER07b/GOzKwtPTwh70McnfQoPu474u5wtoqA2CQJa2T8lUL7gDQBOM8k93wCn
NK0Tj/dU3cZdnicIlbEJNu8/ULaBUPC0iPDKrU/WFrWmG2CB0KpU8WGkJbGvCg55lwqRPyQeHPaS
+CWtlV6jZpNkDu8Uovtf9kJcBxN8U95cHB1HBiDrzVOn6wsLBwhgg4VBjYFzTPjkotu4d4B8lVou
HqADiMARgp7wQLW6xMeS2V0u4hkuGTlOBccvC2im4k2N7obDW+SZSotBplgwRh2FRj7a11k6aqSD
nmVs7aR4mtNXzP8AIVSqKe7e2O7oVXc7i3TbWg9cKmH1HSRe4NbqPErZ65GnCB4z/shR5zc7zWyU
m4nid+P+ye3EOqNawdFVbc5ww0C2GgzyW1NxumtIj8gqrwYtYVTa57s8bg1mo1yVRP3Kbqv8/kqT
LjpcQ1vLxVIUG94T5olwAax8ujp/IVR5+OoP19HGe3K0UHtHvMgkK2cdEXNqPBOplZe7SNUIe4W6
Z0UucXHxUB7gJnVHJzqrC91vSVNxkY1UTjouB7m+RRLXuaTrBQIqOkaGUS57iTrlWB7rek4QE6aI
gOIB1EqzeOt+7OFLHFp8Fmo4wZ1R43S7XOq+0fp95bu91vScIcR4dPBcTifMqnGCzEhcdRzvMrie
4+ZQAqvAGglDiOMhSTJKm4yMarXxWar/AOJHJzqiJ11QAqvgaZXedpGvJAb14A0yoD3AdJW7YCJy
SeaDYhrRHoYUn25/ZEhePZp7tHblc1qpC8FntH7N8eyF4+5RC8Vr6OOzHoaehhA+5BrdUHXNc04l
qguDfEoONelkSNc/knUzq3HoNYNXGER07DkYZf8ALtjqi06gx7BxHwiUAYyJ9ETzaHeg5w0br7Ix
yEpobqt71MLPa8iOESewMGpMIjp2WhMEjIlWk8pUowNBKx2T7nazvQU21lkPiPvKCIWzfun6raqR
7ga7Co0mD1Lg3EYd1WyhgkSR/qRht3rO71yqTw8uDazcPbkLaGuzaRaOmVtFNxJsb3Q2Gt8k7/LD
9FXdzFP9QqD3w58PiecaLeVDxNqANd9VVu+8VtRjFjlugSw7vuOHCcaqnT9YWFg4QwQcIG26J81S
q37wcY4m50TX3cd8Xc4W0VAbBIEtbJ+SqayaIOfkmf8ATb9FSp/CWNkdcLZbRP8A7TzTMHfOytqp
Y3YaSGwtmY0cDmNxHeVMU3PhxPdZN2Ud2Ims4Z6YVYSRbk03t7vkVtAaeQ+qoUWD1Lg3EYd1XUQ7
54K3pe4PLoJYwFbU6k0tIt5aLeOA3hpHUf4hBVI3VJfra0G4yiG3023mHAT8incTmu3hBNNq2hzB
blvLRSDl1GT4lMzklBwcQ41DnnoFXfJa7hy1sxITTDu7mREptY/1rRTPn/IT2DWnR/OQqD38T4fE
840TXVckVW2kovDntcahBLWynljCANcaKoR3nuDFutwHZDJuPkqtUOLQ59gtbJT++2YbvAMzC2kz
BkN4Uyv1YGt89J91kGCgXPc4jSSpJk9UAScaIm4ydTKsFR1vSVa17g3oCpnKF1V5jTKOTnVfav8A
4l3jpGvJYJEocRxp4Lje53mVLnFx8Srd4+OkqzePs6SrA91nScKQSCrnVHE+aicIubUeCdTKy92k
arWUOIyOcotD3gdAVBJ1lE3OzrnVW7x8dJUNqOaD0KieHorXVHFvQlcLi3yKsFRwb0nCwYXA5zZ6
FPa2bnEG6VLnvLjqiGvcB4GFwvc3yMLhe5vkVqcoQ5wIGDOimTPVcTnHnkq8PcHdZUuMnxUXGNYR
Nxk651Q4jjRAmo8kaSdES17hPQo8R4tc6os6kEHorpz1RDHuaDrBU72oCfFHLoPeg6oACGtEALw9
rlcvavaXNlhjz7IGpT5IlpiO1v8AiE+2z2ePsZ93z2ZRWPTjsn0iYutaSB1KZvxN9SBjUIiajpcA
2WABpW1NxumtIj8gt0N4WNbloYIONVs9FsAlpc6RyTLnOeDVEXNiBzhMs+0qVS9W3SykLi5zZlbO
657jxOlwgwqIq5NWoSfGFVFQcOA0Ro6eS2puN01pEfkFs7eYZ+vt8+yxr7vhZX07c+hleHsZcCfI
wQmxdDepkoF1RxI0JOiOTnVWbx1nScIOuMjQys1X/wASFr3CNIKBNapI0NyB3j5GmVlxMIF1RxI0
k6LMlp1E6oudqfctFhSfRlT6Me4YUqR2YUnsg5WOzw7NP2XHusdo7Y7Mfs7Po3e94PsceyY53x6K
Lg3xKDjXpZEjXP5J1N2rfQawauMIjsORhl/y7YCLTqDHpG3kJTHff09KGkO4bsIGQZ/LslPeI4Tn
0MejMg+XsHVJAAx5omRhWnX0okDxPb4qNB1K/wBlHVFrtQYKwFHbPsxvCA3xVI7xr3EnScqCIK2b
9w/VbVSPcDXYVCiwepcG4jB6rZQwSJI/1Iwy71vd65VN4eXBtZuHty1bQ12bSLR0ytopuJNje6Gw
1vknf5Yfoq7ulP8AUKg9/G+HxPMjRbyoeJtQBrvqqk/eIW0U3EmxvdDYa3yVKnA+yDojvOtwmOq/
27MkLarhAkD81Wp+sLQDDbBA6FVbT/Vn6LZYMTM+PEn0tN1VJ/7eaY/rUH1W0U6w9W0Hl3eiq0XD
1ABxGAIwVugSw7vuFvCcaqGGPUfotnnLrXkA8zlNdWyRVbaStoDtGxb4ZW0OZqLflqmNf36zCP8A
+U2l9xufNCkSfs+61vDoqNPLC7TEtf5qlSywnGktetlAz/7TrDB3zsraGfAG92E4iJFAfoqTncT4
fE8yNE51TXeAA/ig6l3i8hxVZzYbU9XPgYW9d39zdIEnXVU3cRdnicIlbPufi1x3jKrMYeAVYj8V
WI1Bb+qe515ApjLdW6ZTHXXXNwYg/NbNTa3gcxuI7y2ekI3bnEHxFxVUHeOLTiWAWram4taCQI5r
Znvy4tfJ/FUafEwnThlr/NUoL86hrQbjKIbfTaXmHAT8imtxipmPNfFTl54miZ8CoxcHfCtpd8Qe
ACeWqoY1Y0n8FRgv4tbWg3GU4tBsujt8+yPYjJxp4KSZJQBJxoibjJ1MqwVHBvSVa2o4N6AqZz1Q
uqvMaZ0Ryc6rNV/8S7x0jXkjB1QycaLje50dSpe4uPivtX/imudL48VYL9ZJe6SuKo93mVYXuLek
qWuIPUIS440yqmpqPwXTyTHxNplQXut5CVYXus+7KsvfZ0nCm53gZWpMaIFz3EjTOiOTnVS1zm+R
W8qXVCMjKl2pQAqvgacWitbUeAfFWh7gOgKtDnBvQFZJPzXeOfFd4/jyUnia3QSrBecyS90lcD3N
noUcnOqBuMjTOil7i49SjY9zQehVsmNVE4QO8fw6ZVznFx8SgGuc0WhpE6oCcDRQ57nAdSibjLtc
6oQ440zorRUcG9AVDXOE9CuF7m+RV055Lhe4TrB7Dc9x8yg0VHQOVyIa9wB6FW3G3p7Yl1Wm2DGZ
1QkgyJBHP0BkHHLtv5TCcw6t6em0OIbcJz238pj9uXfcaXfgFRa6jvCZfqU55ltlNtrQJslUyQ57
wxzuNve6Jgr5vqADxCrXjBhrcaEnktpqNjLwxvyRqRdVZRb+J5qjvO+6TPOOS2SlPA43Hyn/AMKr
vDwue0Dwkqu31ljRFtgAb0VWoBL2DHh4pjqmXw9/jphUm1B9pUnzACI9Y+XANlgABTi3uggWOHcP
gtouMimyweeEyi0RRAF2MEcytlpU8XZPzKrOGj6vD+foStFHtMej190HuM64IUCtUA6XK5rnB3WU
X1LnHrdkJktc5jersn5oNaX4My50lRJjVEvvLvvNdBCnkBAzKAvdA0Eq2cdFDnuIHIlSxxaeoTCC
4Oa2JnKlz3H5rje50dShfUc6OpXE9xnqVZe63pOEHXGRplNAw1ug9HHt4Wvbj3DXtH7dn2Q9GO3R
D9rD0Cp9nop7MrCntx7mGDUr7Rjv3SouDfEoONelkSNc/knMOrenoNYNXGER2HIwy/5dsdUWnUGO
wTzAcokDz7XOGjdUJ5gHs3nwzCc8RDY9qGMHEVvOUwibgsduFlYWnbhbzGsJjvvdjjhoaJk+i8gh
zWcwsdspzo7uqcR8Intv5TCdTOo9mCxtxAOPkhU3bWvvtFoiVBwVs37h+q2qke5a7CoUWD1Lg3EY
PVbLYJEkf6kYZd63u9cqk8PLg2s3vty1bQ12bSLR0ytopuJNje6Gw1vknf5Yfoq7uYp/qFQe/iqQ
+J5kaLeVDxNqANd9VUvPxQq9ING6aDjkB1QeCBbQbmJjyWzuNxJY7Lhk6rY2t0d3vHiW0A6MItHR
bRaToPqqFL4HU2yOuFs7biL82tb3s81VYDwirEeGVtDmai35aptWp9tuyZAzrqqToc59roL297oq
d4a71kAu+nkqpLnPtcMlsAeS2oxixy3QJYd33HN4TjVU6frCwsHAGCDhA2F0TpqqdS7ed625uZjR
MdWyRVaGkqufuuFuO75LeOm/ch0gSZ6rZy28k4LnCJCBu4zUOfkFXxqWFbQw9yDhUKbB6swYjHms
iTBIHih/Sc+saAT9FUFUcDSJn4fJVqbWjdNGnIDqqED4Gn8lsjRGTnx4lVfc4FpAFre6E57Qd4KU
5H5x5KmXzN5z1Wz2SJnIHinFpczjg2Nn5LarJaIGPHCoUmD1Lg3EYd1Wy0sbtx4j1Fyqg7xxacSw
C1Q4ELaw0kf+1WOJs/ULZzdl3ePXK4W/1pVXvM7ovZqMLaeIZa13CI6KsWiTuymPrZfJtMZOEDNR
zru85oHyTgDi+FtVM9wNdhU6frCwsHCGCDj2UgwUC57iRoSUSTJKAJ00RNxk6mVYHus6SrW1HBp5
AqZz1QuqvMaSUcnOqzVf/Eu8dI15IwYnVDJxp4Lje50dSpc4uPirC91vSVcHuB0mVmo78UM6aeCP
Ec6rhcW+SDrjI0MqwVHBvSU7jdxd7Oq4Hub5FX3uv6zlXOc4u6ygXPcSNJKN1R5nGSrd4+OkqzeO
s6SrL3W9JwpBg+Cl73EjqUC6o4kaSdFEnOqBuMjQzori8l3UlcTifnKOXH5om4ydc6psNfI5X8M9
YUrje50dSgHPc6OpVjqjrfuyg3ePDRyuQycaeCuDnA9Qrrjd1nK4nk+ZlQ2o4eTlLXOB8CjxHi18
VYHuDOk4QzpogHPc4DqVc7VXXuBPOVg6ocRxpnREh7hPQ6oua9wPWUXXuk6mVwuI8lc97iRzJXG9
zvMogOIB1E6ouuMnUyrL3W9J9xx1A+acG1Kb3N1APa1x0dot5iLrU2oYgmB2sggXzE+CnfU3eAlN
YNXGAiPYNfyd7jnsz2x26duVp6Xip9x0kwSB4wqd7Wu9ZAc76eSqkuc+1wglsR5LazGLHLdAlh3f
cc3hONVTp+sLCwcIYIOFMGDotm+61pqn+fkvV0y1z8XOdMKvTc22gwEWxgdE5g4TTZxU3DHmFRpk
4DAVQY+kHky/WFSApjgpF4ZrlM/pGZqC39f0Tg5gtLoGND4KodW0adnz/mVc2m2mKYuOrlSqEucQ
Hvlwg+CbSHA+0ugjheFQY01JcLiGsBuQbHAXaKwtFrnBokd0+CqtuJbhgFsNBnktrrWw1oLR9E9g
4TTZxU3DHmFuvWFjW8TQwQcaqkOrnH6ezx2z6UD0YPZhZ9Lkso+4yEC6o4kaSVxVHmepVu8fHSVZ
vHWdJVge63pOEGyYGgTQJEC3zHYGue4gciVY6o4t6SgHOJjSeSySVdcbhzlXPe5x6koOdUcSNJKO
cFS1xaeoWajj81ZvHWdJVgqODek9gL3udHUriqvPmVxVHO8yrTUcW9JVhe+zpKnQDAHQe3/RadmP
cMftnw9HHunn+2x7lPuga3Uq65rm6S0qLg3xKDjXpZEjXP5J1N2renoNYNXGER07DkYZf8u2Oqc0
6gx2ufybHoBjdShUxBNvseXYCeYkKEWHksLl2GOQnsEc0WnUY9MCQPEq+RF1qJkY5J7S5stP4pzX
EAgT6GMZA+aPr6ZI5Cf9uwsmSNfc8iZa4fkr90GOD7RaNVBwVs37h+q2qke4GuwqFFg9S4NxGD1W
yhgkSR/qRht3rO71yqTw8uDaze+3IW0Ndo0i3wytopuJNjdA2Gt8k7/LD9FXd0p/qFQe/ifD4nmR
ot5UPE2oA131CqXfeIW0A43cltrZ+apOhzn2ugvA4uimrn1zMlbVcIEgfmq9ING6aDjkB1VOn6ws
LBwhgg4VODqYVwdDzVOfkFXflruHLGzGE0gGS3MiJQouJjd9xreHRbLTMWu73jxLaN4NB00ytpxi
1yp08WboSI14VR3xn10fJVZ3joOJYBatppnuBrsKheSRZKoCiMO1x3jKe6lgmqQ4p1GIcQx5HQ8/
qn7QB9oLf5+QW00jG7DXcKqWn4CqO6+LXxMr1eIcq9F2t8j8U7aNBUFn5/7BVaLh6gA4jAHIqtaJ
duzCY+qLqkmyeeFdVbvC2oLZ5+Ca8E1Q2oOB7YPkqbry4Nqtw9uQnOp49cc9FUJEPIYXeeVtZGoe
1V7sxRx+Sp0/WFhYOAMEHCo0hLC7Thlr/NZGOq2bo1hqn+fkg1tFjTrOSmXF7gag7wiBzhfEx1R0
h0TPgUCC9r3uM7ts/JPtEdmfTj2ILnuJGklEkySgCdNETcZOplWB7g3pKta9wb0BV056oXVXmNJK
OTnVZqv/AIl3jpGvJGDEoZONFxvc7zKl7i4+K3lxu6zlXOcSesrjqOPmVx1Hu8yrC91vSVYHut6S
pGPJcTnHPMq65wd1nKkmT1QG9fjxQniA6lOaA/P3nzHkoNR8DlKm4z5qJx0QDnuMdTKJuMnUyg0u
No0Eohr3AHkCi4VHgnUyi64h3VW3GOiJuMnnKkEg+CNr3CdYcgri913WVbJgclZvHW9Jwnxq5seS
ue9xI5koXPc6OpQvqOdGklC6o8xpJXDUc3yKMuPFr4oy4mdc6rvu0jVWB7rek4Ra2o5o6AoNJMDQ
JgyIFvmFIMEdFmo/+JWsc4DoCuFzmz90x7DVY7PP2DiPhElESD4hOIjhEnsAHNFp1HoNfyd6Ueyj
9oc/SJi61pcB1Q32Q6oACRy1KFSkOOq8yQPyVeoWta9zg3CdUi6qyk38+a2d9T7TiPjam1GTvKjj
c7n5Ks8ReS1vzjKtOjaU1Md7hVGu7SnI8zy+qpzq57nfT3zPvJ9xlpIPgpNR5PmiGPc0HoVE4V4e
67rKvvdf1nKNtRwnWCokx0RNxk651TabQRTGddSp0AwB0H9657B2T7nPZj9sRC0Wnuei0Wi09yi4
N8Sr72OExgoC4N8Sg416WRI1z+ScwxLfQawauMIjsORhl/y7YCLTqDHpGOQlMcdH6djnDRuqfHwt
n2QBIkiY6egTIxy9m4j4RPY0yDPpQEWnUGEWGJHTsDG6n3KFuW6U+EKCIK2b9w/VbVSPctdhUKLB
6lwbiMHqtlsEiSP9SMMu9b3euVTeHlwbWb325atoa7IaRb4ZW0U3EmxvdDYa3yTv8sP0Vd3Sn+oV
B7+KpD4nnGi3lQ8TagDXfVVJ1uIC2im4k2N7obDW+SpUwB9kHARq63CY6r/bsyVtVwgSB+arU/WF
rWmG2CB0KqWn+rP0WyhpiZnx4k+1xYDVIFjZJW2tZgax81WtEu3Z/RMfWy+TaY1wqV5e/wBaBc9o
HyVRr2i0Hn8PktopuJNje6Gw1vktmxixp/JUaWaZdpwy1/mqIBfxa2sBuMoN0p7zQqvvcbvIx3TK
yZgD6KhRYPUuDcRg9VstgkSR/qVS2ATWeJVafvN/VV6ceqax0CMARhUKWN26m24dcKhuB3tcamdE
9tKBNZzfLRbRTcSbG90NhrfJUKXwOptkdcLZxQHf1x3jKLpcx28IO7bPyVQtYQOeNFVqU++CBPQK
qagAcaP45QouJ+z7jW8OnNbLj4H/AKoPu474ujMJ8dVtTcWtBIEaHqtmc7Ly14nrqmnd3euGOqFR
tRxtqDvtyFUu+8U+k8epzIjERqqdP1hYWDhDBBwqdp1MK743VCCfkFtZjFjlTp+sLCwcIYIOFpJg
loPMwmOrZIrNDSfzCM6DAHtJCukz1UkySgCTjRE3GTqZVgqODekq1r3BvQFTOULqrzGklHJzqs1X
/wAS7x0jXkjBIlDJxouN7neZUucXHxWar/4k1z5dHirBfrJL3SVDqjz5lWF7rek4UtJB6hCXHGiM
VHi7XOqu3jpiJlS1xB8Fc97nEcyVxvc7zKh73OA6lfav/iQaKjwBylWtqODegKIa9zQeh7IfUc4D
kSpJlWB7rek4VrXuDTyBWXE5lRJgohrXjEQXy1vkgbjI0MqGVHNB6FRJjWF9q/8AiQNxkIhlRzQe
hXA9zfIp4+/qpY4tPgUSXGTqZ1QG9fA0yu87HionCkmT4om4y7XOqHEcaZ0XE9x8yuOo53mVLnFx
8Si01XkdJVge63pOFIMFcTieeSrd4+OkqwPdb0nCwgXVHEjQk6e1axupMKLg7xCc/k2PQvOkwPFM
c6OP8k1g1cYVtzR48vTv+GY7Qwan9u04OpW8LyC9+rGy4rawB8bcKq2S23Wm5vd8iq1L1ha0GG2C
B0KEgiU3efY0GNlYql/rZJLYiVWFsUaQPDGnRV39GR+KZSaPUBoLsYONVs1NmHP4nHzKvoCDUqOy
PoqzwG3ktb84yqrXvJsYbgG8MplHFjGcfjiVslIk2uJcR8//AAqryM1XBoW1RG7YIAjnK2O8y7vE
+E/+Ef25IJB8EQ17gDyBWXuM+KtdUeW9CVYajrekoSSYwENYgSJ6IicHVQajyNNVE4KIph4kRBfI
b5IOuMjTK4HubPQqJMdFG9fGmqJuMnXKAvdDdM6KTUeTrqiJOdURmSLZ6D/m6GN1KD7muacS0qC4
N8Sg416WRI1z+Scx2rfQawauMIjsORhl/wAu2Ai06gwiw6jp2tbgXNuHa5+IbHoCebQ70HVJAAxn
n6LjIAaJJPbARadQY7BMZAKBkZ7XgxLG3H+fn2R1RadQYREg+I9K/wCGYREh0cx2RIHifQeDEsbc
f5+foOfybHYMg4nHtG+EnzQtp7uKkWjmoIgrZv3D9VtVI9y12FQosHqXBuIweq2WwSJI/wBSMMu9
b3euVTeHlwbWb325atoa74SLR0ytopuJNje6Gw1vknf5Yfoq7uYp/qFQe/iqQ+J5kaLeVDxNqANd
9Qqt33iFtNS6wXAXAS5bsj7akNfvJlL+zbnz5rZrjI3ROfIqnvjPrgPkqodvHFpxLALVtDmai35a
q5w9Y6kfnkLZrm8qhzzwhVYeNz4cQPwCdUdcyoGs7rdMKo9oN24nibqZ1VF7su4hKobj4tcd4zoq
9Nh4BViPxW0OYOIW56arfPA3m6Oo/wAQgqiaX9Zl2O8ZTzs+PWkEjl4LaLeE2NLgORxKquaJe1kt
VGpVEv49fiFqY8u4m1QAfBbVUH2jXxPRuVRe77RzeJUKXwOptkdcLZcDuP8A1Qfdx3xdzhPLcZlV
zOlERP8A2rZ6hgv4pLhOio1Lnk7yLnCFVu+8QtoPE0XDjZyXERxQZAhVKUeqaHQIwBGFs8DFjfoq
EF/FqGsm4yiG30mmoYcBM+BVanOlWOHTmtqfT+0DgJ6Bb0gb00CTj/FgrZ3vy6HifktkDDE6+PEn
GgIO9cDH5BT3XAN08lXM6URE/wDatnfU4ncfLWNEDNRzru85oHyTX0cOLyHEfktpD2hrrmYC2im4
k2N7obDW+Sc4RI2YfotlM5f3j1ynwOEOj2UhAuqOJGklSTJKAJ00RNxk6mVYHut6SrWvcG9AVM56
oXVXmNJKOTnVZqv/AIl3jpGvJGDEoZONFxvc6OpUvcXHxRcKjwTqZTX1Ln293KJOpQF7oGmVE46I
Bz3OA6lcD3N8ir73X/enKk1HT5rge5vkVcKjrtJlE3GXa51UTgKGPc0HoVbJjontbILiDIOiJL3E
nXKhj3NB6FcD3N8ijxHi18VLSQeoVxe4u6yrZMdFfvH3dZUuJJ6lB1xkaZQ4jjTKtnHRSTJUF7oi
NeSEOcLdM6LiqOM9Spc4uPiUXNqODjzlSSSUJc5zRPDPgrRUeAOUqGvc0HoVwVHNnoUQHO4tc6q8
Pdd1lElzpOudUIccaZQycaeCddvLjq5r4JRfEeCgvdERryQycaeC43ud5lcD3N8ijk518Vmq/p3l
3jpGvJDiONPBRcYmfZkuq02wbczqgCQQRII59rHGOPT0HG4Na3Un0YBAxJJ5LWfTBkZaXAeX7au+
40u/AKi11HeEy/Uqq6Iik0Bv3ZVG4d1jqpH0VN7O+8kSBp4JznEteLWSxsxiVVq28TaYBuHMqgXm
XkEz4KgygO+JJjUqqKZhj6pA8v5Kq1WjNwbPRb2oAaopZkdTj8lQ3WtQSTHeKu2Yd+o7I+i2hzTa
7haY+9zVapANrYE9SqPFUueJNrAbkTHqqdQuPkm1LntqVXHLGT8ltFRjYJeGiRp1VRujmN42OGPP
zVSmXEinTNzQ3hUcqVGD+H+5/bU64IUCtUA6XK5r3AnmCsudpGqIa9zQdYKLm1HgnUyjxHOvihJm
FYHuDekoCcBMZTJZE5B1Rlxzr4qwPcG9JRse5s9CokwiJwVYHuDekotkweShj3NB6FRJjorHVHFv
SVG9f01RbmXGXEnX/m1a3VB1zXNPNqi4N8Sg416WRI1z+SdTdq3GPQawauMIjsORhl/y7Y6otOoM
ewdHwiSqk/1feQnm0OTTIM8kGAgT1Tcg3CcJriRxZA5wmsGrjCvxF1vo5+9b81UJj1Zg9gY3UoEP
YOK3J7WOOj8j0IBB4bsK0emx2OPTtIkHxHZYI9g5w0bqhkHHL2eG3SCCPCFbTD81MXc8KDgrZv3D
9VtVI9y12FQosHqXBuIweq2UMEiSP9SMMu9b3euVTeHlwbWb325atoa7RpFo6ZW0U3EmxvdDYa3y
Tv8ALD9FXdzFP9QqD38VSHxPMjRbyoeJtQBrvqFUnW6AtopuJNjdA2Gt8lugSw7vuObwnGq3QJYd
33HN4TjVbNAxY0/ktja3R2vjxKu1/dY4W/4VWp+sLWgw2wQOhRtMSIK2k3kmAfzVCl8DqbQR1wtm
Nl0Ndp81TqioXDIkiHLK2cO4vVFwB5uymuq5LazbSUwP7p2gyq++0YJGO6ZT4H/2ct/Cfqqo4mtb
DN4zlCMwZAOBCbNR3elbY6eIVAAemqFaQDuZc6JK2RwLpcIJcMnKkuMpoOjuE/NMa4f/AF+J34St
ltMXTPjxJ5a57PWuEsbPyW0upi0yzUaaqk8951ME+K4TH/x5/JAno76FMuhzt6ALlUJc58PES2AP
JVhJFutN7e75FV3N70tz01W9iau4u05zqqdSp37iJ6hbNiTY8gdTlA7Rn1jQCfzC2rejujpplbU+
n3w8CegRqvtYRTkutk+fmtnfxEljsuGTqtJMEgeMKlvxLN5Fx18ltArDDRjHdMraqR+ztdhUKXwO
ptuHXCoWl/FqGsm4yi7Z5E1SD1HQLaxAY6AYai5o420Glqo1Kol/Hr8QtUu4nCpA/BQRB9hIQc57
iRzJUkySgCdNEXXGTqZVgqODekq1tRwb0BUznqhdVeY0ko5OdVmq/wDiXeOka8kYMShk408Fxvc6
OpUucXHxWar/AOJWbx1nSVZvH2dJwrRUeAOUocR4dPBHJzqrC91vSezhcW+RQNxkaGUIceHTOi43
ud5nsGTjRAuqOJGknRRJjVQ+o5wHIlN4zw6Z0Use5p8CpcST49nE9xnqUC17gQI1Ql7jGdVJJJ6n
scbzxa51QyeHREtqOBOsFESc6rJ0QcHukaGVcCZ6rU9VxVXmcZKtdUcW9CVE4PJAhxlumdFL3Fx8
UMnGiBqOL45OKc1t/F958wPBXh7g7rKvD3X9ZyvtHfipC43ud5lQ57nAciUTcZOplB1xkaGVDXua
D0K4Hub5FEtc4E6wUHXGRoZVxe4u6yoBOsqSZJ9i+piGGChU5Ex7B8EEM1I7Awan+4l33Gl34BbO
x/deCX/P/wBKnScLnUqbnx1Kp7/PrRbPTmq7nd24WjonHibcYFRomFWe821L7bqbZVSo1p3jGDvD
n1THVBL4e/TOmFRDh9pVn5BGDG+qx/P4ra61sNaC0fRUaAw1lt3yyj/cOdcELJJV17rusq41HF3W
VbOOi4HubPQolj3NJ6FXte4O6ymEFwc1sTOVJqOnzVocbei46jneZT9S9+C49P8AnJABJ8E1jhxO
5IuuY63DrTogJhB/9Io2kxz/ANkAYyAfRdTdEtxjsp5HGCR8vQtdr2MdiHoCQJ5ntNvISmOxD8js
c7k3VOiOEXe3GQccu0GQZ5elaNfQeDHA24/z8/QtEDnJWs9pyBAnKbPxCR6LZ+ISExx0f7TZCfut
W1XCMR85UEEHxVP/AKh+gVCl8DqbQR1wqG4+LXHeM6JwpjArHTyCIjp9FWAJFuTTe3u+RW1Uj3A1
2E2i4n7PuNbw6c1sv7j/ANUOeHfQqnvjPrgPkq+9xu8jHdMriPIR+CZSpNBplgxydjK2WIw1xyJ6
rZnkuf66LnCESwwd87P4LaqWN2GkhsKpaf6s/RbKGmJmfHiT7XFgNUgWNklba1mB0Hmq1ol26P6J
j6+X3G0xrhUry9/rQLnNj5Ko17RAPP4fJbRTcSbG6BsNb5LZ8Ysb9FRp5pl2nDLX+aogF/FrawG4
yrKY+PAcqpLnPtcMlsAeS2hzBxC3PRb1wG83R1H+IQVRNz5qZdawG4yiaPD653nGFtNLG7DCQ2EH
Wu+xbxN1b4o1XPu9VLXBmdeipu4y7PE4RK2Y2XcLtNeaZUvvGRLhDls26xM5A1ynGhwk1IdHLGn1
VdzGxUhhdA7p5q9w9Y6kZ8chbNI13n0WztuIDzNrG655o24mq4T4YWhBCrmdKIj8ls76vE7j5axo
qBJqOO+HE5oHyVZ5JaWkAWN7oTiy4E0STIiSqG5+PXHeMpwpwAazhPQQFWp+sLWtMNsEDoVX/wCn
+oVC4kiyVsbW6O18eJbQDoxwtHRbWYxY5boEsO77jm8JxqqFxJFkrZt3iZ0GuU4sLmG+DY2eWida
0jwPssmYQD6jnAdSpcST4q2cdEHXGRoZRDHuaD0KNj3NnWCpJkq11Rxb0JRNxk6mUAKr4GmdEOM4
8VIJBVs46KHVHOA6lC5xMaSVYKjrOkoQ4i3TOizUeeeqgkxqibjJ1zqpa4g9QhLjjRGKjxdrnVXb
x0xEyuFxHkrnPcSOZK43ud5lAPe5wHUrNV/8SDRUeB0lWtqODegKIa9zQehUhcVR5nGSntbIJIMg
6IkvcSdc6ohr3AHoVE46Im4ydc6oOD3AjEyr73XdZype4uPihDjw6Z0XG9zj4lMYxzmWiDB1ypY9
zfIp4BNziDdK3m8df1nKk1HT5q0VXBvSVxOJz1VztVF7tI15IZONEHOe4kaEnRXNc5p6gouuMnnK
IZUc0eBUSY6Kwvdb0lYMSg242jQShxHh08EcnOqt3j46SrN46zpKDS42jlKhtR48nLhe5s6wfZBj
dT6OMZA+adbVpvLckCfQAPMA+kAOatua4jWE5/JpATmGJbjHa533f21Tg6mFd8bqhk/ILazGLHKn
T9YWFg4QwQcKYMHRbN0a01T/AD8lXLaO6Nvfk/gqlMuJFOmbmhvCmUcWMZx+OJKoMoDviSY1T6pH
DRqH6CEWCLqrrzP3QmXuc8OqgC5sfgqu9w3DW47sqvTc2KDGkWxp0TKOLGM4/HElNd92SUwmo4Pr
H4G5PJMaBwvrl3yH8lB17muruJFjZP4ou2cQalR2QPyW0McGtdIJjl1W0vGGBgY38fecejn3yQYK
4nE88lW7x8dJVl7rek4QbJgaBMtJa5oiQVx1Hu8yo3r+mqJuMnUyrW1HgdAVFxg8lfe67rKmqXVG
8wXKwXxMy90lBrqjiByJRNxk6mVgwrRUcG9AVN7p81a2o4N6Ap0VHi7XOqcGg3uw4zyQpjA1Pife
o9Of7jn0592//8QAKhABAAICAQMEAQUBAQEBAAAAAQARITFBEFFxIGGBoZEwscHR8PFA4VD/2gAI
AQAAAT8hdLyS5cuXL6LdS+i4suXLly5cvHRcuXHoX0zFgy5cuL06S5cvouXLgwWMIp1O7tF+WZm8
xV6BZcuyXPhIP/2A3zL5HMcJfEevuXAcy76iy4suLOXn9K5cvrfW+ty+r6Ll1L6a6mXK9ZblyzA3
HUVoqv6n4UHpcuDEnzLnftgU9u0BW4GDLNw6XF616CV6OXn/AM9+jjq9TPV6CJslx1n0kZJbx2ho
zMtT39IjGX0sTugwXXzHYlQ7DNcLB3nMb7dcupHPW579efn9Q/Xp6tuhj9AMxbfQSpwG5XP0la3q
aHxxFfEKjrrrphMH2m9tTS+GZCx9uID556vic9HxNsrH6HL05wc7t/kg207ZyqBmNlC7bhpgxBwP
3LMNwXKatdIw9FyS+1bfeBerBN0Y2/SySvzHcKRpn53ko+ctpUP3ONB0XAzFymJXGwsWwOLTyhAd
rGGFjEGOIxHrcIvJeDMP2JZ/G5SN9qRjeF+xHq7amo29wGwmP7QUFtINNWC8OO85XOUlp6yJtFpb
smYzYHMG3vAjzcTVpaPtKbO6Uw/MuduAU34hImRSsm6Vit+mYmDiXIFG1cS4egO0ON3BcVNKt1Fh
21IstKWF/wDJEERz2DjMKKxY1vxExJbwJOyPSveVCU9FjDn5h8IFbPMS/axGJb11NwMzNvXy+PV9
l+yb/wDGo9aIE4o4qCZ5dQTivyysBpRu10N3SBL4KA9Ch7W6m8SvC4RNfaFCoUiTJYvtDkJgTNDf
7sNGrW4NMdfgGwuCZY39PdELe7HYm9BJq6qC9+rtW+85JwDYUuYA6MD6/wA+YrA03+8aRr07qJi4
jpkfwRHMilr/AIYkX6LTVMJq1tS8pzNCebLTks4LP5mdEZR5dn4j1ogTocVNgGzjsJyIQToFP4fm
IUm3y75cz6mULi95l0PxzFYCSXVlN/7iMSpQ1DW6h/3cTZO/E1ELlWQo/thataxo08sd8t47P/Ij
P91bf/U+lsDMu4mGvh57SrMF8p329KNyu01xL5l/PS2o7GBzqzzOaKDDF6mVjY7lDLETM1Ae8Go1
K6nVbHz6HpZMdtHlfeZPSoGo4uqQO3zEAygLd/8AZVqjdJ8ulkIuilWPHiBKcgkI1RTlvvowHZEb
tBhh1GWV4Ao9w4Sj3Fby+g8r7xXYcHlfeLfGFHkvf3hhpov3n2idbEX+4pQurVV72xK6OvPzbnAD
ZVHjMYTWKL+zBmz6NkF7x05XsZhd6ZBtjnMKHrEG3FZzDnUKW9VnPtCPtLqNisppiviOb3EDt8wt
riN3XLctV/arUHgZvDM5xOcEViAQHbMY0eIrcQMcQK0JRszGmcqGVfwKLOJI/KWQ/oPLLCz6Vhx+
NfcHFsAP5Zhl2b9OTbWaQMS+8udgVOcykDvjpgLt5ijaUBwy2IYZxOU23LzK2jSfaVUPeYg9utTl
/wChIR6Zj0Fm+l+qupOToZjgXzKHBjzGq0rzEcMRbtFxCX0dwLlVNytQxAsuIPPEz+F4nBf/ACeZ
8w5EzcUmBuYMQ32gz8xZZlmmpx15ef8A1MIR6cS+jr0V0463DooMuZKJXmY0MHaWylwzKYlQajad
kpTMzuJj3mdynjzDSqW5gxZOz5nGNyjxMlcRzmOqjZlHREnEVsJ536OXpGuTQLWUIlr2gESe7R+J
YJGpZGYFLJr0IrAAv3jc4q6I9i78q+89KjkNrU2D5eeg/HKdn+OjeyW1cu5WtczFYVRcUX/Uw0fa
A05hRofmcDSDgVBf3MtrmJcX4hKVwq6Lx03LdAqZ9i/4nHoFI2qIj25eZhqm33i4eNR89qtNgNSr
8hBMYR+TUTA3vwRAChfZTX8Rw09AVklVniUJHGJwwYEwQN1mMRKKhX9wxlcEswTkw7xmWuVZPfH/
AGL0UUHzX8ROhFBmeA58o4wTEVWZXEWlO9TJVdFPeXa8+kUbFGc1T59xkCGEZ/ud8akWCuBDfmCx
bLQpk/cxaUBOcpwzN/AhiaEoudD2joARV7WJ3HKlCeXTzgAUpZdMEJDWGpYZZheozm6Qqat7O14n
cGqUJ5RwtTv3yy1fBdpAxvUDVwFjLXf3UeZi1OCzL7w2+E8X/wBd4lMcbRam/vG7wE14xH1IYS71
v6gYYui/cmDq9RWUMO9XGrlw9Fuz9zUFAEwMHt/MsDoba1QdjcUqgdTYrrtM5Ner3O44LsDdyiae
YmDs7Gslv4jTDkTJtFnnJGKTXjEbWMj7Yh+WxZZZCz3gNHYEQvInfQSfI8Q0pKFs91e2Y8miEW0q
h8RsglVY3GujBexbE5xmwadH5uNIWdHfBlvwq47mEBaM2Pc3LbjZQoGjeCNSCmAM1nWszueRqE8o
VJKoLtLmR7CFlM48RvYCLTmT8QzUCZ8znDy5KL+UEBRMY52zxNeCAD2sSgONNaKWzHDNfyB/LKHo
qzPBd8fzC9cdL3P3KkUNam1z70EvYA61wzIRXNctm0+xN4DwNDBX3DJRxUU0F+dsDOhdnY/uMVzR
JOaw5qllkuyrAOzDLNyAaZZVIlY5Xuv/AMCCtyvmM1eCZ5YcvPqtchir1GbkWq2sMRQUF1FW6/YY
+Rdl1+I23cSEWGlt5ZuPtF3ZwwpGLvb8xoW6KLeo+V/pPEpyFKo7JiGLPL6RgV9Lmp7skVsaguis
rUohcWbUvaCcc7+B48mruu0yFtz9neJFvFbBAATsoKi573byxBgNoI1FACFTC/7l9i919pao0s7l
p3kPaLKjZUWO4jJL35iZUqoF4mB+T1+IyqBpVVMNUqzv8xUpLaPwZnlgqy47Rii7Kt+ZQ45pbw94
wLJq5qMElKz3XmJUvwXB794/3OpnvCFZOEI0Q97CGAgsHaQyZ6SmZhXC3XMf2/gPlG1Wucr3jwtc
UtYIIAYVcxxTxKm/hZKtHjLKYtxSstStpbeUwnzX0jnTlBSaAXvO5x6ab4O3iIB3DNVm/wCIlyW3
a7nA2Q7fMbYtbVy2XHuIRc2pT8S3ge75YiAU8xe/McZdtn7QYVpytfhLOdas1qNmsXZbE5ototpo
lB3ncYH7k/p+nvqS+tSmX1VotKjrow6a6X0qXKIZWJogVxzHOJZcOCgn/wBpvD8Ryw/mG+8TxMMV
n25mGcH34nA2hG9XA+Z5ZfE2bld25xC3eyczvUpdYgqLDAcRoOJS/LiVuO35gl/CGuxFTAn4gfLK
Mc95nBS+I4d2Z/4gfknYhbpcdPx+m/ovUtfGLle/S+t3GXLl+kmvymOye4MWIQK6X7kt+OWA7vli
nMB3eIDjB/MeyX3l9npg6HuYljmKmBBXozuNAC2U4fbuYjG3yx5lyl2l3KG4VYTLWp5X8zkHhluF
Vx2im2+iovHV29Jo3C/rtgD2hExPdo/EuEjUsjNJKa103KiAlAX7y7NjXSnsX5q+89QkMriYi1V5
6Eu821iZYvVXvNz2gSP7N/j0V0YlrODvDG37SqYJ4isKukFzIj5JgxyQ+IgGkuNXAuYkeSUWdWZA
tq3RHcJCTUHU1PhlEWVqopXeX8oEcGMQq3BFJUt/CI1J4LL+5LaBZnEPJ2ighlOc/wD2KGkth+GZ
Ph/2H/yGY90enOIJqOnz6TNGN2qqZv4hTsuLOjUZIDCPE/1O+JCLBXAhd+YLFutCmT9zApUE5ynH
FX/AhqaHIToe0ZEUKvaxH3GqUJ5dHVwCyll0wSoNYamDLcLlGc3SWAVAL7XC8ezUCflFnpSbaKRZ
BjXPPy9ogrHVrS2L7R/CGEu9b+pQjQ/5B5gHgFIV1vPiUp9FQudvE5wkKfF9omoDCXet/UqIqhXA
hd+Zdah+VsGzgrW2Vh+KgKBhF0ZAmLZNXIf65RjdZW8GuPmC4UDuG6f5zAHPYEBeRGoWqBSmceIa
VGM104Ia/ghO2N/9nI+ubTb3ijlIHSUfUVhYA7F/ozHcAFEl3oiLDZ7wtbywFBUV7spinYAVSufC
ogjoqtV639QZ4kg2H+eY3rNxTgtO9XFUGEI1cu+YfpgcwWx9S8HRx+uOX/ZzBgqu/wDaLgm3KmIU
dwB0bPkq476byZ44uEaNkRYQjp3X7I942JdLp3qU31+lbdmIyQOUEyTJogL7XEiKAa1FrlUHuNsM
ri9SmT9wjaVHuSi4SaUuGjB/uJwFmTtjfjzKQ8DDbSMFSl1Q0Jyza1MKg+5xEfMcTcwTc5efT4PK
mbZSyxpjFkWq5YsACgupe3X7DFybsuvxFbftIMUWlt5ZuNtV2l4faYTi72/MEBNFZWp3c/8ASeIV
TAVR2TEcWeWvESL/AEuanBJLdsVWo0tvKAweeGl7l9H5ISgLgF6lcW0FalQW1xoshqBXqtQcu0Ua
lEBaDsBacCtRtufNhlwn2ATehgUuLZAN5Yucetupisn/AMjNWe5JUU+RAb733gGUF79NHjLCK4u5
Lr8CCFTpqAgPGGRC0LVtrcTeFOa68wMaXasymmeFqjmpSb7lREpsC9qdkKCtRGT7bv8AML0jnP8A
aI7AWd15mld8ji5aHNLyOIUtd83AxSqbWyVI18gXvfeZIJuQVzfwRLwIim+82r3RuWsd9oR3ze3L
q3bdXjzU1xm3bLS5U7zzCqugVu6jEJ7Lr8QgqdAvUwaqqXVRtIHfr8TJuBWXia4r3nhZpaQtCLg1
MzcIjzK95VL9BtQzr7f564fRlV5x/cZ+Q10xDpWelF7h7vYjdS8Qt0w/LK95cV9TME2LmHd35idH
TgL8GoYh99wPdaJShzd2w75My2Gvw046VPbovaLKF7qLhtVO5T+Y0GgPfH1mCLA2qyLT2lBZXNjJ
B4JRtG3JZMHA97g28sWWNRdHhmmtwemeZ4CJNBzBtc+0rjUtY3E5PMqyIWoj2sbua5gd7mAGPb0p
CFuuYlmpeXpdKhrE6lRyyaFKDXiUJ65FS/CUd0Mn/aCuJwtWMg+VwtWsjo8afOYlWwvxRBqKBr2s
fEFwyE7Y3/2BrtpsN2ZYuoU0cI4Fgt6KMvmK82ElwjIF0S2szkWNad4VcJcsx07wmKQ94Td+c8Sk
AsayNUvxFhXCG4ZU7eDA+syn9uc7IMO8qJ1ikHuje2E37jH3PqUJ5RviXMMl+bhSs8Ftb77TR6zg
33hQj5oP5xD3w8m9dVHxoJOLUv6ZiMIDVF/ixqIJ/aH+yfqEB1XlaPg/eOib2so6fhMOdZ6G3FVA
Onw7rmhjgMLhPMQeH5Tg/eKzo6wnKe3tMCUNHZbqGSdjH1ZzXOJgMzaN7cPsROQe0Ro+nzEzNqBx
Rp+SEMjiVEmmN7H6nIsI0br23MtElT/CZfsiEpSLTmDbxM0dpjsS4GBbnZjOIZJRG25U+8C9wLE7
ZRz069oul3uXUv1rQjVjU5pneWLmgiY7Y7g7i12ifMFfonufVWzRcAEF95hGLVe/MAJnTdfiFHHK
Owdpz7O8sXFnI7uLm0HBS5jUtWbIYQKSrTtBAt8V9IsCQ0F1MeywoPmKKU6Sj3TK6YuFKhbw958z
y/y7xKl9C1BsG93fSUV+U+kPoMVyOXcQVjoTi7/llTi9WtS5ztXY3Wpq6COiNVhVF6e8QKRarllY
NJR2rtA0HQ4Xz3im1vlAaYu9uBBBovcAoygdEc95re7s8Q56GHiBbLlvp+JyCRS7f1uKAqQe/eY2
EFnjohwiZD7w6tHlmnaBkijIWoVEjRMna+ItY2R9kcsT3RYcTC/JmbuGClC6eWCghL/CXykzs4nv
i6Ez6Xb1V146G+gRxDpU1L6+eoZi3T5Haf5NQDFN2qBGmGNyu0Oq3HfWjmDnM3mYCVCuYcgbirep
h5gWpcadw1zLVHHMp4nBhls1jvEFrRxNg2IVdjj6hbKUpXtfxMljntEtmz4jbSj7lRZmYEFlbuUr
MtqoFFXFaulYqVU4l+hK/D0HQ11ZuGIzMGV0ZcZxLx6kuyLAkHKjrSmDBULswlMpjOJTiXicS8QS
kg/cBQM01NlnNxhkw95yH5nYCcSr37agsMPXDOUJZg+5bZuPvFx1E1yS6DQjghpi2B2l2itZllZV
At3qUU7+Ycm5VX8mIQxX7Q5o3AkHEHePQ9VOh0+k0i3eXzchrL7QyJPdo/ExiGpZEpFrVqEeiKAA
Xq2Ns5VLlZbC78q+89MRjG1UwnqXk6Vjr56fMXUM2+0TxV49mK1beJ7jHxxxCFqMRXZOlcwIcmEf
k11FDpYnRxU9pbL9oKcxfEzxNqUiCnPfH/Y+FRxEF/ELW2AI5d5D+YGKjr8ILq4qO1UNXMNO6ug7
syoOv2ZluUquLLh7xmnxU9iNoocPxM34Rt9k2GHe9x5h5Ys+ZV8RO19Ew6MdvSrWrW6srJMuml5s
m/OIjKRhHif7XfEhFgrgQu/MH63WgTJ+5mxUE5y/iYVuf+BFAYGle6HtGxAijGrEfcapQnl085AF
KWXTBtfphuLDLOLlGc3SWkVAL7XOApbrGsTz8e7FE08wkKQ94Td/fEql1KiqY2e5uJqmDVvae5Eu
ScRSg14lAeuBUvliLjCSlK93vO7g4LOrxblHuFrNe+cRDRniVsAwwHGfM3vVyArNwdRtEchTntUr
J0nCymEImHwTPiiSykx4EGi3WgTJ+4MEDpvhBkK3hgBRxRLFsG2b3triZjGF2VYf7iVuljVOA5+p
YJqqv7HtHgBUPajLg3LDXzgVTfiV1V6GwvMzdwn3lyYKsFG0cUhY+MxhwUqNLvR7VEqJVm4WF/A/
MrkbOOSfz9RajWGwwe8uxDmzvJ+0Iyi9exll1IpDS1e2sygX6Fl/gmWEFqXXYRL4Fbuu2ccR7nAk
gZWfMBojYFF9/wAH3Gl394PgH2R72Tyhtym0XUCUI5glSo/lPaGJbxLy6X1JIDScTf3oqkdORtXM
XABVnUbbp9h8xMC9l1HbdtIMsbS27vNx9ou7NpmEYtV7lJa0UWtS33/6TxBWgFNOyYhgd5fSJDW6
uanDtLsgFMSi2qnw4z1BAtcX9IZMNI0kJA5QrsJyLO6vFzWRYeYK5R3Gu0tW3TGWAQPRZiInG00z
LHeBeXnzEg2Y2yEHwTKy1Uab0CAx3ajZbFwUTaSkSVpKWiyMFXi7fEsLrVjPbtOK4khqCiVf9y1K
NK7s94gA7G+kvgp3cGDSw7ULgBMKznb7zmiAL8I197eWYNytsme8ONJor/MToTasspcG0tgYq4Ez
/clAUGQvXibm6lWHg+ypcpEq/wCpGCvADSi/7mMsLeeb8zWhkpcdDEFHmULe1L5SyhfJuezlnqXG
GGsJ0Zjc1eZ5aj7mWdwO0AOEwyQbeer6a67mc3Av6TbHMrSiLQe0tl8dQE0lOumum4ldeYsJaNy8
tvExIpisvSVn0ZISuHEOBtmI1qCL22QPeIvfSVaTFaijMQF+JzN9EdTDDqBDeuoldGLQntfcrEPm
mZtqeyQiW1Ke4j8EqskvroZmo3i5+DFuFHE5dL6VGQUi8BiBmIWUQLTxdQb453I0Z7cQUUOUxeE8
xtC61i2Tf3HccnZeTX4IjNZAkBfBM+dq7Vz+8RTes8dWHziX9Y0+ia8YZgZmVwAB+8pVWwywY+Fw
QUOVwuE8w2nJflJ9McekL9XHRllLyCK+cQ3MTbpWImkCtKNEuDZfaOaClKm1udzqY5W4YeI295mj
9oNHtMsH5m036DC9xVY1NYizuKlMIUJzgvPaO8S21VxJ3V3gxR8l3MHsfcLuMR8qPkPDMZvpE0Yj
IVdTnMVZyl+hGGrDeO4x00WI3z3X4Jk+6ixjOLvb8xe3yv6QEB49gljYvuu1Ri3irJRMpHMLJzWF
V7FiY8Ut1zMmzUr8Iu+GKnzi1fwdL9uly7mo59FYlSuIkt+Ij9u0Ul3rQTyQoM+CvEqVvG5W7oZs
8zLyPEpb3SlQXX3LT29ovumveWLHc4tKXBK2ZbCkGEOYncS0pxKOyVpxAGmJsxNh4hUo6d2T4myH
5iDbhiBTxOHCV3jBzaYaDKW4jnGZUOYRY5grvKKr4lzl5j6SL6n02HpK6LrpVdFmpeYvBPaJXRsy
WY7g6JliDNBFLZLjORMQFfMShA47RGK5IkWDmklroJbbpVl9C37StT8pzqY1K0SNCmIo/pMtMS+e
IPImrLxYpA9hUtaiqtndhOdSxNIzNsM8x/TX0I+t6V6h6XWIs1FuXLtGolI57+Iz/wBiWKXPHRUt
GbTOMXeLE8j4ImufxOegY89LgRYJVwxjme0rTDEq2uYkK/hFBnvfwQ79eJZYw3ZqLOZVg1jOPaF6
yMvFzE5xE/tHJtm5V3KqmfMWx9QTABRzCJie7R+JcJGpZGYFKa16K1AAXuxFOGoynsX5q+89TFsW
pt/S8wl9SNkXe/BGnSBaezX8QlI66D7TBBWW0Vf5g+xwfui/hMmFcS1FAO7P/JZM/mUc4gu/zUsz
h7TBLbc6hXdGJvEAtkv2e0FWu37zEdhLxUzYuaqAjKPzLl2PxANGwKXL4iEwAL8ly1/lLE9/mWzN
kpnfzbiBnaGw2mHcT4IrQ45gDG1UfEnARGqJ2GRxCMkEZZgpWT5g+PdmQOv5ggtLTRr29NeIztS8
GI3zfOPGIyQGEeJ/md8aEWCuBDfmCRbrQpk/czIqCG8v4h0lV/AhiYGhc6HtG5Aij2sR9xqlCeXR
ykAVUsumDaw0hqWHvL8LlGc3SBbVqX2vE7glShPKKLWE+YILt4DMTOI4qghrUg4Zydsb8eYFMWuO
5hDXese5hmvh4Bv7KPzLWA1OxwmJJQMBXpCyHZ4YH1mFOFz25RNPMBJSXHtjBolQGlp9xRKCDO8k
ZTMhXtYgsZsqt7ktCmYO1HL+JjPFXly/18RFb7OobWveKAmPdz8vaIXLId+559oLdCxrveIthgGe
Jj3YQYDjMHuBgnPKOGGsLqYfmHStgmXGEwPiMyYKP3jGkCqb1ddor43NHZg071AMsMOj8PmUrUrW
3ZP1Gp+iGgqx+YnAkx7QSmCIymD/AHMKOTZlhfDvNhJdWGbi/g4+CL7R4yGEu9b+oPjWagJnzEQq
SbaKSmUVyFx+XtEF3dG8BthKqyq/se38ywcwOGLwvFiD2H+3Kbg3xgzAjRKTvmk7WCtxmr6DOA2/
Uui5Qxr2uay001M6OCCzAHsy+XHEsN/MqcanLz6qvK5fSO3ZCrlioAKC6l7dfsMXIuy6/EVM20hG
4ptanNx9oO7PKaVR3t+Y0LdFZWp8/wD0niGWSlNOyYTid5a8RgeEXNTg8lq2NS1oot6igIY0sxxT
xN7cbJVo8ZYsCKqlYIAdN0fEOmekpjkD+BzAxCFGFt47ziUad6ZcO3tWhAh8cnX4joD3f0lYSaoF
YSsbmVlxN3Xy18IUi7ivfme8M0RDuiOZq/aMEyW+8S8aVqh5sMDBgtn7SEectJCLVlLp5d451t2b
Z8wGNpSW+HiCV/IR+O0PGCLJVo8ZYuWdri5lKw7F7feCc8KPonvyQtho2wOXPfBY4uBYQtl4ZYGw
Ur4PaN+6FjCKXxdUKloNDB4hxogK1F1PgX7kxA5+RuWLptIMeBdhQZirbYxf4hnsyyHPmLPdxLll
3tzMvDu1utTOBrAqIJt8ELh3AXli5qbe0oEDjZGZ34jog+E5efSCtG5Us2b8Fpg4gIHcNg9HeMHL
Xt1Gx/z4xIpT7uhH0VIVNWK/x0r3mTjS/wDGP5hHoLZZZ3M0rjcybZdwNLlUYI5xxHKzBqJZmcLm
LEe6ck5CXbgZbiOYr8k0WbRxDb0CVUvM9okCkq45miZPTITiNrXUZklN58XTKHab1qBM4IrmQA/a
NKouOn0gLy6PyiSu/cgba48QafEL8Xt/MoFu0D4hzzCNy0lIZTxdTA2g2uIr4SgGyqtFs/RHaso1
eT9gyuuRUUtLfce12x9n/wBJRQENUOz9hm7aA0XuuaHDmXk1+ECXZEyClvlZoJxK/wCgsq6zKZWj
PaNOiz80/EXdBW91H9mE6Udh2n3EjvkVnsfiokwCU8f/AESq8xKlYmLtNc0mIGY2rZ3Q3FxXMMQM
E9qJuYtf4nGUg1r8TWmZaqx0vAqE9gdxeRhFuXXE5zDUwuI4jL7zmcdRnspB/t0VQm+IXnsnIKl1
xPdPwm9T260HT2QRvM5enWaWDuJUCmJQFRPYdCjK7HGtG7jMhYYvZ592vxDVQc/prPFRtTWwvnvL
ypVfmqOaEpDZXu8wBQuoVFznud5YuGdfkoT3NKUzCfUZm1W/mAkA2KmowPDLmpRCtL2oO6Ndjdam
z7e/6QHEalsEolXr9x6GWW1RhWQlVm/eBZcxPw6H4RZ3HRkNzmfUWEyzcsC1i1HiW0J8XCrq7h76
WMKYAtmoLvPwwSUQu5szz0IoxC7l94PeVC2K85eTgj/8ZDuLlLPFygBNxQ6fcGpnpcVRVM9ycvP/
AIk6ViVjriNdA8E74jGaiuowlV4Zi+00lYGeYMfM0XAoR/EVY/Puw3MXi4GWpR9koGzLGqwr2iJh
6EzU1LOJ2m5h3Sqq6xBvPxMTA8dpg5anvF2tl5LTO3eZCpXU1LuX3xMcM16UTl/5a6VKnshQjC7j
voReldTZOZbBlfXWFt7RFa1O6bDUJxuc5WC4jacwK5zfErhuMXU1iZrUp+ZVslKKT7Q3DxUaY28s
Q4V+0SaTZTz0XFXMa7SjmK6fMuB06iU9CZfacTMC4EucvPpr9touCSW/cqAbE92j8S4SNSyM2KU8
PQ6IAC/eXZsa6U9i/NX3npcYhtVNg+XnokWYyuzK3n8rEzADVsXNER9ltRYsXG9kvplUwz+8dayH
vm/66XLo9FoFzI5OlMFBW4TjSXyxKKstb5o/udnNUcsNbfE/cimmXVopUM94EACYCt2yzZL1WiUK
D+c/7LNTFQH3qUBZhwzeLsFrdS3EV3lwS5boItsOaxNH06LT8QgBzKYsEfk1K1d++1//AGO4wvVx
Pzj8itNa6HMOlM5efSyi4G7yhMdqA129v5jIENjxP9zviEiUK4EN+YbFutCmT9zEpQE5yh1mb+BH
AaEoudD2lWIRR7WI+41ShPLo5yAKUsumDVxqDUwZfheozm6S/DDt2Ll66kZhaHvCqixzsAw7x5cv
WwUuUwGDDS2GICaKwbTEDBZPoTLZUV8ucAUC2dO6xCR4FSARzK6t7kzCMAVFAp3q5sokAuHC85nA
wD8w14S5QxGQtEusaxPPx5sUTTzC6pDkHJu/OeIxtEq0Y2e5uauaOMzYXeYEzhnLkhnZepbL8Jbt
pj0Bp3qOrNoVfmlhxbcoGcBYV3pYyRR8cCZvzLoBcwKt8rgUCCvSBqJPAElLd34agkc0Fb6hphVM
wdD3jWSn2kLgRxe5iWpRAlya17ZljTsFYrfBcZcyhGRRFPQGxeWI0WWpUaO7BdwpV7uBSbYlrWy0
CZP3DAZIo5NFxpSGEu9b+pZIdkh3zDR4SsOBo1qHcUrBZwplNdB48FSyJdcArwrt/UKRKByLcq4a
mEJYKvknFsbWpv8ANMdIVTGKztniBe0NPamP2XBXAhd+YXFIe+Ju/viaZb1W/wAPSSQGkm4PwKR2
yLVcsXChoLqWt1+wx0Gtl1+Ii3MSEbmm95ZuJtB3ZwzCcXe35ghZootany/9J4goSiqOyYhidi/p
GB49c1OLKWrYKbPN1+ISGSgVh2icvcpbwu4fB3vt/CXAwd7fmXS0lN6xPbnbBPaqt1LPtT8u8R9w
0RvfmX2lCo5WZsb4RqYMota2RBTEotqp+5rr8SgD999IRcGlVUBauKKTZc+qw3MJYXvzBnMasfhN
xpsWfM1eSyoVTIq8viK3PEtoYeAjJ3IeDdwp2Rc1Ar+gjUtgjSdQGZABUS8+OfLHae+UimHkxmo+
Z5C82UwS9ZSWRoysXKeAGi+7mZczZdogCk0LqA6OBGptxgfjEXHAkO3zMkY0aauWxQ/wHadxH2kY
MeKKBIeOxbLlb1lUEaDWEhxZNZppbyUIX+QoYKAnxdficbm4kxHK/U4AFFeVohEGFWvG9nUOt34T
neE5urj4Wwc4/wC9cmJCzgWviMjX90/kjZ2DyMzINNWdK9BLqYjNh4T/AB0Hoax0NxX0hGuNM1if
yMTB1Fe6mVqbKqY0MSznIg3jED71fDBqmYi5jwccSm7BThzMbRV3e3Sl01k7w3F7kQNe0zOBeIB/
KOzSXWJ7s3uHePXEvEXR0+kXgTrkKpRcAF5g2sZH2xHAEt1jWJ5+PNiiaeYTFIe8Ju/viCFTcTcq
VPl9z/SOTKnFHdYI/wCgDA3dRVtUeJ2d+ZdO1T3c/swKAZHS2uPEPbcUKt53wym6dcpSmniHACBh
7UU2K4XQpp/KwbnguzjS+80XpNQFfC5YSGRdrPxGUwQBfur8Tt+f2cEeMXkLNQr6+RvQ7vM5kFDl
w+oq6qLnss78xUDZaRbJv7mfbN8Yfx0GPQsqY6ftRUdKqBWJX27S1kEX8wx4JZU4l77zmcExnuWu
48TBnmUIIRkqZbECbfcQ3QS7NJqc1lWMorKF/slOFudxqXBHsSpmoS5zmVKlTl6UQlJpJvjYVSWp
SqbWyAExKLaCfua6/EoFvi/pFQbmMEasjpHY3X300geShD4JpuoGjNBXT2lTiCi26JjdmbCBAHVh
max6VqAFuUvDDRriymPgpu7fP/J+7rr8R4q7LqCMmIqG0VagaWJTawqitUrCpppOpcGvf1HwqXRF
9KI1H0Zncgrt4lDES6mkfyQKvhubDDcxlGfbrTEuPTDvI0u8pkbGZaS+0HdKD2gKLJ9nEWhrMavU
7pbtDXvOOlEYy8RYs5ef1jrmV0Mx4f8Ai46W7TZvMRxSU+4lwmNmZm8XHSPDLuMIm17gR8Tul8wz
nmKVj0JUSamrgJ2DuNFXL0mD3JlXFNLrBxOQYTEDDLlx1K6OujOX6h+hi5griv1TqwTqBzcA3uW4
BmT3/aPYmbnmAafiHIvoDG5m6jTAIjxBohmVEg4qoYYrhLYhhAc7iY9kq2YmGQomSzArUpkkW2Rz
wxZx+JUroPRZdr0lFbUEP3Z2APaEbE92j8SwQNSyMAKU8OpKBAAv3l28q6I9i/NX3nrRjaogJt5U
8k7O3QXpeHvm/wCpfRh6W9E2W1BzYD/MqMKlxhfEH2lGLv8AaYOvylJrJNNea4nsYjT2ummVIVuE
Tvj34hwC0ZfB0MMZwJuPVRYrperlm7A1Zgmf27B5P+wavsZbfErBEVf0htN5O9a/MeuZoKK8rRKu
+6RGHmOYJpcQyzHiorJz1xZL4M/xHJ3/AGnLR+Y9sXWnpc5efTq4AHdtiYxUsDMcV7RECGx4n+Z3
xIRYK4EN+YbFstCmT9ziRBOcpYrc/wDAhgaEovdD2jYigaxqxO4dWoTy6OYgCrVl0wasNYalh7y3
C9RnNwvWtEvtcO9ABBDZdOWc85BWD3ZzMpQCF7tkUVQQpqb19YzC0PeF1SFjlN35zxLgjI9yALLJ
XMAPbjoINmu2YBVBYku9DEssj7ktbyytcYXWtsQyeCC6Xpgl5MTa7mJk8XAtmZdKu19hjxBhsWEq
9GfqUHXBXFnPmWcg/K2a2lwtlYfqI3xBMmCj94NOOArQfW0AYVkrTbf+OZmEAUxZm/MOlM+OcYgs
titS87D9YjM6lJXGYHVaLeAo/T9SkQGPbK/8cxQUp9AMH1mVoQMKvklSAHTmt6981B1RJxdrjPEF
SfY6qXNPTSvdDyTI1VpM4EKqBwKy/wCI2LIj23D1IDKbupCgOzd/fEe4vAOXXy9plEyQ4NSpK+d3
P9I78OybQL1NCVkQFvglEWjPR/EjLcQD+5BVU3kQM8694t57JLNMq8kW/E5uVzcrOCWXylnCBOCc
vPpShGk0k3x8K1HTZCrliYEFBdS9r49h8xc27Lr8RO3bSDFlJbeWbj7RdpcMpDi72/MalmijLU+V
/pPEFsUU07JiOJ3lrxKpfNXNT36A7i9T72Xme6TSWV7R7WPTCVSsEpnm6/ExhPi6/EKCKMjtNmG2
zPeU/WVVwgXttm/mAMBkF6PE+jra7Tthbqt19JYWMQnRAYIFDsH/ACXzrnli4VH0FpGyvj2GLgci
YE3cUSDNYIx2+ZUHbDli72Bq2CW7y+xhM65VJPKmguPNP+RvZpWe6iCrqy2I0te+/pHwHAo05Df1
BmgyFIqntF2p58QtRdqu7LTM/wA1lInM2uz9p3f232RZFzSrXbxKBb4v6TmaVIS0FuHBFhUdI7G6
+4quchUkvN6+6gimbSEtgXa20zHklVLnEGMLLc5lJQDAxKcMnvF1EFjcW714ht59TKAZ7zX8zRv5
cMcQGe81/MuZClUTYq09blzjIHsn+PVhtKNMohUuOJRcTcYdhKX7ROHM4HiO4hSWOCp7kcnQfRqc
phVRzhAqzPpLIYa8dBe+m72zLoPE46e0KIsuc4gGzqW+ycDBltIv4Yj2mly0uUwlwU0y8LUJ0XP0
o4px5BicNigafRgl7Rmcfb7TCoVGBMv7EVqSrJeV+wYtjkrWRLz+GLcjBLwqvZK9l2gYzV+YneOA
Mss/RDUBGr3bH+cRM+/jGH7j6q6WnMumaYI0ExVL3FJbVy8xj1HEv2l+3pbo6YTAYkoIWOviWIS5
+8bmuisnEvEdV1BmATEqqlDubeZad/iL8Ib4Ohbl9d9FE5lPSqXpHlWlUk94ML8TYhAQubNZXV4u
U4O2rn7uL7TyN5Ljn8i8sXF1ONLbyi+9sNlOY+FS/QQ9D1VPeXcIR6qnvKi+biPYg485jXMvhxKX
6HLFjllckvqmJnc5j0H2l8vuLez7gFGD5hjzIFLA6s46b6a6YnL/AMR0vpfoX0XL6YiVBj6Vypa4
it4mu0ue7U2KVs8dbxKMagqGemk95fS55IzaXvGL94BdMkK8y0yr9pZF9PianEbgz3l9LnL/AMNd
K/R10r1F6Vj0VKrcwg0gzW0vikqovIR7ziJ2mp71FagR9odomMdL6eZUMS6BgIKZDLG40qidpqe9
Rh6eOnLz6TLNctEF33kswGRPdo/EJEjUsjFpKa16EQgAX7y7NjXSnsX5q+89SnsWiYB1Lz6nwbsf
gjJFC09mv46DdhH5NQ1IM2+1h/Por0EbZcHIhd2Lz0uEsEsMnL46KldMpz0JU1A2G/fb/MxOZNwb
PM3Ax03AiluWo+3peSMLZp4dCst6Ju5rHQgROlS/Ry8+lAG3ExGXFHLy/m4iUGEeJ/md8aEShXAh
vzBIt1oUyfuYnABOcodZVfwIYmhKLnQ9o2ogFe1iLudUoTy6eWgCqll0wamNQbjB7y/C9RnN0hQ1
yjteIu41ShPKLSsqLFshP3gCymcRRVBDWpBwyE7Y348wFYtcdzCHscr3MMM/Q7643qLKkgBqxcSd
QwVfMYNqNrNb/NMtD2oB528RgQZhV71HcEqUJ5RkL8JFaJTRy6+XtEXzapNgpt+ojiynsXqFBUHC
xqCVt8H+EGi2WhTJ+5gcAE5ylZcDGQoxAuJtj7TSBYlY4BTy5wF4CtbZ2XxUIjRDWlWCdwypQnlN
D1FfPnMbALsysP1LuGmFe22t+YCC9IaWr21mcNFhnJn81BtOnG8GX3lb0ZOiytXuULUctJuRD2zR
Sg14hAQA2o8QvDM1An5TOXdywpGvkrftcQpYRKL7wPaXCVAL7XM1QJP8DvCYpD3hN398S6AyPcmh
rkmahwJLdY1iExTHvCbv74gqwXGAqh+AUs5f6JgwKiMB049PLz6UQiJpJ7pbyzfeO1ItXbAkAaC6
lrdfsPmPkXZdRU3bSDFlpbd3m4u0HdnDCkYu9vzGpZootan+9ezxNKBTTsmAxZ5alYumrmpwfS1b
KSzRRa1KFDhSxriniV9vCyVaPthNJqsrCSZ039IdO9JTHrHuOoSTFdX+UrVF2W2naM8JWqhfRJCk
LKJrNUNasDNSkFaKLWpkbkB0RIzbSE2B4FBlQnqQlCWtLutxQG9lw72cSDDa7kPPeVI8gXuLACzk
AppKQ11bBG2xAxcxXk7MX3lML0UWtSvF6hvJNkSBQZbNju4uEFfLvNz3HJVFE8Ni/KDcdIdEpRNw
Oy9xc3Z3V4vvGqk5WYqfWL9yYCP+gimXu8rKYCNXNT3rpYxUR2mjCgt9/wCkJIDScTur8jPeJKYl
FtVKBb4r6QUFImkm3p4r4RVzH0E+Jy9PHllw2ADuU/mGtLw98/8APRVjCoO+6axjAOdN/kmgkD5l
riLyeHr4n+X1YHhL79L9DDpfor0GfRfS76OJvquZldK6HSrlI+ipg9QeglXOXpwTYHxLUdGSQMeI
JeH86PVarqtmqC4RSdsb8eZpwLLNkeMJe9S6+VjFYrpl8vaGi0TRT911M/7Hyg/a4vZugclR6BtA
y8Xipx7AbQvAmTRpoozP8y1pOaqct5bYPKY6uN1xnvBQDA+0peJdcrb+0wBrOrADFegz/cf2hWjl
/WcdCX0Y9RrpGvWzHoe0O0yR9A9Gv0Hry9Ikw0qkm4PyAZdahd7VqAyLkpASJ03X4moYyN0doMFF
DQUVf4gJWal4ZjPOC6qBsqwUvDLxubBbpMMMqWxCEG2HLm7yLyxcEJAYL1LeLq2YGcEsWy9oUOGi
vD3nGJ2L3M6mcvwnpvrfp49Ny/TcO0vMu9wOh0uX0rvxF7y5vqC5qXDMublem+tzl/4rnH6HHXXr
v1XNzUvpiVUqcx6CL0OSG+t9KOtXE6jGMPQdeXn/ANdfq8egal30vq9PiB03LO0HMU6KV1Iyjokr
odKI9SXHpy9Jq3ql/HbAHtAZJ7tH4lwkalkboUprXoYEAC/eXZsa6I9i/NX3nqx7FqAfnLyRhxWn
h1yOGseAf6ehCe2QnOb/AK6sIWNRXZL9DGfnuOx+PSD2PhOOOqHsWibT8vPQpara7JcyNdps8yum
gAM3GP6dAQ2qm4dLzNY3wsx02TZ01vD859M4sINzb7HS4XNQAZOMf06bl4hfS8PfP/ITBZg9j2mp
z0rozl6UprYoN0HHzEhX2BGnvmyoyQGEeJ/md8aEShXAhvzBItloUyfuYtKAnOUwpM38CGJoSi50
PaNiIir2sR9xqlCeXTzkAUpZdMGpTUGpYe8twvUZzcLCKgL7XCpU/BYZxKOwdBThYvvZ9zAOA8mf
6fEbOC7CxueLbe414jaEMJd639Qncyur9yZe9eMgqf3/ABLzYNLglDIAEsAPg3EYQNSUuVHGY73Q
QMDT8RR7bOSCV+8BYwVrbKy+otR0Y0FJPzM5I0W9yAuTd5KsD/amQ5shbKw/WI3cQ5nSvDcKFedV
awuVmkLrJb+Lggl4EaeXfMtjVRyIyRq1KaZu0+pcCFvCry0/iZLKivlzlBVmWk3KHPZoUoNeJpJA
FcO4dNl1WoBQQ4o9nNQZlsHVUfUuIqEvtcwc4qhfbXZ/iNkoNqCbrhmOfvSCx9fmM6trWIMT50B4
Db9TFNFp9h7RcELAMBF+IhuqIM5sn1FI1wexg71GXXqW0MP3g4M+ulsMVuhsZA+jceGEVDTSDXa9
Vq4QtFF5KF+UaIVTGKztniYACFkwU/eIQ+zSOYu51ShPKUwsJZeecr1bKqLONMZ63LVjxK9HL0oS
Imkm3thWozci1dsDQQ0F1LW6/YYuDey6/EVN20gxZaW3lm4u0HdnDKQlWq9xqWaKMtT/ACr2eJlR
RTTsmI4neWowLulzU4PJatmpWY7Z3AsOrd/iKHaWsDc7KXouc2zvLFzQjAVqdyC9E/e8/aWGcsr5
3Hlud4rg4kGB3XaLqcKfB7xYtugvBG2zApc78W8sXFpCFRpf9wpw0lZIq2YFLjxZd4rn88ftC5Xp
KSYn5VndSvmN5YuHYLWe68xu1bS1nHOpbEMIdU7F7nNM7yxccKTatsthaK/h4nd+K/RDXJrbW2e9
NLJviQHbGjltW1lEFATrKP5hDPIDoijfgQGXIVtcXBBI0n2RMGtlX+YgkNJ+yVQeWGl7mE/NfSCb
Dfgg94zGSg7AKIms9Ffw8QrMWeW3tHhZNZostzvFGoNTvL7RIWaKZajl5f6TxD96/wBJctVYXhe8
cwldOXpBVGWVKNq/BaYOJZg0dg6slQKOauvQgoRduvr0uaitACEQAB2c+sTzySln9nqR/wDJcPRx
HEvE1L6cejUWaIkvo9KnHp5efSAvLo/KJK79Sw21x4gaHyIxj9/zKJztX4/YTwTl40e24faeEtyV
2tX8QHLBGK208TLYCbyo/ZlCqsls2n2ItTnTVTP7I7psVL5K/tEFUnIdqCBZKXkVT7FajtWqV20O
BAFocRYv9jLh0EYsD+4gi4pgebeuJgy7mXCj6r5g5KNF4bY8QAFEDILVa3FwvO+9r7sywNJS3rlv
Lc5W30IdX0X+mwmujCePTxL9NdNoT2m4/pOXn06zSwdxKg8xKAqIy2WQLG4quy9jtNBcCFzSBMds
WCpe8tveC2KKLdEeruy6YslOgvBG4zTSyr+o5U3uzt7xiubLpgAG2HLnu8urxcDKjYXhj5d2XX4g
ICzNsMKdmBi5s8i8sXCoLptIiJSsL6i7SzmPYeg6HSvRUegjv1cQ9L0YdGCMvrUr076mpXXM5ef/
AHMOh6bm5fS+p6F6T0vzL7xg5jL9B0eh6HpcvpzPicvP/wCAeleqv0TucpfqC5qEc+gly5v9Tc5/
HpNGW7tBL8uq6y+0M2J7tH4lwkalkagUtw9CAAAX7y7OGuiPYu/KvvPViG1U2D5efRXoOX8GigBp
4ZqGLMRXZLg+wacnmOk+q6JldZNte3mW35/cn1HcgAXrMspyfmSok1OJhK3/AJfcp4Un75/roPlv
RLyRgyXV/wAS4x8ih+Br+OuWL4XbbRV/mCnBpc+xf8dVYz1uGi0C/BqBKxKNr8uHoAKFFz7F/oBd
hH8qlgZ4cte3ovHTl6QopMWlWVQaJdhnJePkjIEMI8T/ADO+NCJQrgQu/MNi2WhTJ+5xIgnOU45m
/gQxNCUXOh7RlRQo9rEXcapQnl0c5AFKWXTBqU1BqWGWYXqM5uAW1ts7XiPutWoTymOj5zYomnme
ehzYomnmZ0eExDmAlY6Wwx1DFg0tMfEFfwUnbG/HmZU6RydpbBUO3Q/aZbMQ+XOKnV2lL3ke5Lkq
H4899xG0tFZ7QTN6mxo/sS98SbO8n7QjWK3ggiKymmFQQtP+Fg/KpUjE4C0fstxeeaciztwxToxy
edX+JkzYgyL1l4mTEjdWHeDeXUQe6OdmVc1lKZyk/iwgHbr79p/YExZyMe5hmRBdCqNZOoazxQKq
3iNtAPdaX9SqNY4dzGbFNjcrPHbGKTXjETPHXPMZQCYd7o4pgABlMws0CkO7A+VTZzAjNZ/MsUki
4GkTHQTZbv4NTiSAXS9cEQXVQGc2T5qOmhQYF1hC32R6mDaAeAOs2FUpOp/4mI79tamFQfcqYohX
Ahd+ZqOop584YDzoDwG36gdWkqwx/JFZYLUKlwKWSirzi3zVwYS8CNPLvmCXoHrNKxApQYR468vS
gIiaSaabIUjFyLV2xMCCgupazX7DHyLsuvxFTNtIMUNLbyzcXaLuzhlIcXe35ghbootam3/aY8QQ
JRTTsmMYneX0jgv6XNTg+lq2Ugmii1qfu66/E/dx/SCssgOifzV+kwGLvb8wwmdN1+JUSVpKWiya
T4tggWr7P0QcsnN3Sy+Y8teJvnaVfCKsa2F894b1IShALH+UrtFbBtouOUnaruaZb6VdjdalZUBF
g7RullRXh7xa9bS1mtS0lu1+yYB8xrxN/TSizFgnYvbKexpRbogcAqBWEUhZ4OcypBF4Dz3l5gVr
WyByTkpAGVyWwwIrCkaPae7bHbNH5vXid9VywUuLvS6/AiZd2VbF5a3db5isq0rl87iQRE0kWFk1
mqHteEoS9uv2GYRX1sEZ78Cgy2XXdxc2hQULAyGdbBMD8qzuoJTGgee8duRau3rpekFaMstAwGOR
/wDlkUdL5Ocf9/QDajrWM9ujCmkvv+lfrvp89eeieq5dvS+l45ly+gXKzXo9onW5fWul9DpXp5ef
SAvzR+USO5+FHV/RjQXsFta/YiAsrAzQX46lLtgowlXHwS3aSuBnFfMxdKbDTHu4uNe9WjZ454qb
JRHIFLfKzGZyeT/+sBFK/CswcowU0uP1KtSOpvZcdo0vq46nqvoPSegjCEWLfUvHUSGpv0XiN11q
Wxb6nR/Q5enWaWDuJX8yvxhRbdEULQa3HzMR0qzupzDO8sXL3v64ubGsKFz2IDyndPqZtVv5gBkX
ld53B0tNpcXCqC1SsclyQW9359HHSvXqV0v36V6ePSTos3KlTxL6GDppj04m8QubZx0qL7zHRz03
0qG5qPTjpy8/+p9PPU68dbhfHo3NT36uempvq9Ocy06XOJV9HqS89Ll9Oehfo5ef/Nx08+pK9B1r
HovHQIzGpVxh6TB1yOvaM26cxJv9DfTiHo5ekS4aBazG9hOeeJT4Kiy/vCUFmrdEQIsAb3hFFW12
S/S3CS3Dpi22nld/j0LSoA/kvo62gp8NQMgFcBBYWPudEyDO/BGS0Gj2a/joZzCPyajKttfaz++p
H0J0v2ly03KqWdmH2e0b6V42aOTz1pJcMwE4IXPsX010RriGbjH9J+0x36WUoFaADMzAFOTnokoe
/Bv2PePBr8N/jpUrosH9i/xEeKFK9muvPRjr0ijY0wR/GVfMvGoHfs/1PYiArpkTbMQ+XOBsYK1t
lZfUx3TrhwR9mA18JQQ53J4o0IsFcCG/MpajN0WVrv8Az0XUdADU6liMS2nI14lA6DhY1BM+EPrI
25IZsyPzcVs+vhTw5jdmoBpMfUv7YYZqox4DDAcZgexa47mE9hSvcwwz9Dvrjeo9qVIGrFxhahAq
+Y4OBazW/wA0wQdUFjzt4jChzCr3qO4ZWoTyjiNTahQUhA5d+XtEPzapNgptgoNNdTempqzlypiM
vI0W7Zmd5u8lWH+4g7VgB4jn6nExBopTCY3ABgOM+ZrwzU8GEJQJ8ESq5hisZFR40+cyh1V0pyyP
cib+6HamHvE4OC2LWxEJiCnsfhbFV3c4B+ELNrVsgqf3/EwoUXxDsdgDXurGCRYFkphEBdGcmSBb
Zdc1cq2g5ZKF+UqYNMI52zxDrXbFy6/uI/ckUA00RqTkstlYfrExTIRewCXnwwnbG/vmEU98ApAf
lbHMBEx0thlHeosZpicYa3WNYnn482KJp5gKoPytiquKbstbELtzU6tO7BazWjjAFNZwQh05eqns
oot0TWggVqe96lbLRZVsti5hldWwTbhgcuADuwFy8LuLcBk3JSXt1+wwDjSHUVW5Vdl7nvhAanIM
7yxcH61CoQMBmsiiLCVxdfiOtbafRHbUsyezTG1K2C894qpxpbeUMmekplkT3HXMIN4ur/KZ4F2W
3XaOWy4tVDGmyFI8KJpumnDArUSFmisrUBGcgdESO20hN5eBQYKhETSS3wq1rZHgDFRpf9w7g0lY
TfnwcGKZ1W8sXF7GNLbyh4yoFYdpYLnvfae55FbA1j7P0RcfMqpnahK8k/zGSR2oXMGrhkVf9xH5
FxdG8s253OT61QTSjk3bLzFiXgfgqLCc0q+HiJgxOxembcPivhPFCQxtldTsY4CbGLm5ot5YuAkz
puvxLeyimnZE6uxwIavlfpMBxd7fmICYlFtVP3NdfiJU6HgSuNqqQj5c2IXLFqq8+jl59J6W9Hp3
AFFeVogMW1O1G9noQUvC8CX6nNWqglx74ND2gZTyBX/kctJbh1IVVVT2WvSSuhMe01M9K6FzJE6U
56joSx7QJzfMwOIvbMpJR7GI89My5frqHQj016OXn03VGR7kexNUzUOAJbrGsQmqY94Td/fEEKm4
m4aoX7vOf6SrOPY+3eWBpKW9ct5bgYpjq45kY1yZLXXT7EUAuw70B/JKC7uhYZKr3z+CV+rxDgbP
ZoiyR21WypD4uPtIiP7LqBimOrjmRBGgeEFy+KUbSOTeDEAgKqmxbIKTNZTgmHFTlYcfynsCNlGl
93AgUg+FfsvqK9AdxlvoqXjEthK6VLj36Xs6mtCpigMsbPeKW4lCtiAWfmWU/GIk0x7HQ9LGjzLv
0NpxNzXXl59JJQZE4ndf5Ge8SExKLaqICb4v6RKNuHBMj9Y5S7/mHUT2diQkAwvqWt1+wzJI7shM
3MrbYWYGB1uPmZaZaG+/mKPMli7fG5rBchCXtr62GWt1imnZMlUuyEbiwvNrzuZDJdkI+rxdX+UG
IGz3NH1LDaX+Q9JLJz6Vl46tw30YSnHSzKt1iabi4mXKuZ1KScKSqmoW5jt79NyszTcSuuj13MkX
iJUNTl5/8h+jx6KhK063xPbqNS+ldDcPaZMNW5jnw1BEYcYU6LEigNsGpknfcww5g5l8dG4lSr/U
Z//aAAwDAAABEQIRAAAQ4s0g088s488ccA0YkQs080g62v8AAPJL4DEIMDPPOBNPNLGNPAPMPJAK
MINPPAKPKWrnHDMIgG/CEOFHPFPLPLPHAFHAECICOOALIEMCHXKcPIIN9rrOBILENHPNKHLPPHGD
NPKOFEDHEOANOhwoKFEHXLDCHLOOLFPMGANENNMOMK6MHPdYDLJNhtJHFFFMDk4GNNNEG8NOFFHE
CJHHBbTK3/BRwsbPXdqEHIJKCd8LGfhSWQGOONGMHOOHD1rPPGJw75IeQxlDMCAFOYDI0I/syFLK
LLHAPMLBPtmOIENNOCmLEvNSMPEHc+d2mbPOFMEHEJLIFHALElvPNBCMPAJDHihOzOS7kBGOGIIL
JHOOOJOMAJDJDO3MGFMIBFHDLFfe5nt53LKqBLBNDAJJHBKDHNLIJCN+bPLPMAHFKii8CFsfzcK+
KCLHGMPJCKDKIENOFNPEw27AAIEmIcwB0LA6p0X3POPKFNFHIHLEFPJHACMP0laaHFpn5AwBCMLK
NyNGTeFA/cPKGNCGEENMNNNOHCyf0A6wYpDECBIDI/op1nHC16OPFOEGPMKJNOCOMCDXoPMSJOOE
LLOCAYArrPnKZPNIDIHGNFLCBKLFLCfOENLIu9HOCFEAMbaRofsaeUPPJJDKPMFPJHOJHIFbPA9U
iaCHKLHBPWHi70GKboOLKCMOIODIONPJKrGLOPBKhpFGGNDL0fPnfNJDEfJCPPLPPPNKOPICUFNC
BHLNmNd1cIwptRxD1LLPAFHCCAPENMDKNPHSFGMBPBKb02LmcJju/DxhwPOFLHLEPPGALEEAHZ+B
BFCKCPFBKubDt104r3EndKAFGFNPDANLDEBH8RLOIHFMJOE8NvpLwD0EMliaMDHLHFHKPPNKBOOG
fNNPMKPLO+mcrD0MOOLKGH9DjGVPJBPOAFNIBENMiqOPA+8+GQqv84HMHMPIOEcV8jq5ulPNIBPE
ALLKo3V+6XKg9PJFTKJNCPFCDNOgoN/8t+PKFIGGFPKHDP57yPIHAJPVqhPHONNPPnDEFGMEHPPP
OLPHPLHKLHLCAHMGHOGC5nOFDKEHPF+98KHFPHHPECHPJGNPFMBMBLDMKOLGJNKHLIKPOBCOOKLJ
KFPGLGKBEPLIGHPKNNHPHJHCLFCHOFOHKBMDDDLFNNPOCFAHJBKHDJOOPNPNFNKHNOMPGFLMJGPK
NPHGBFMOGKPILNPPNHOOLPNPKLLNNKILGDHLJPHGPFGPPHLLIIPINGBDAAOOMGIOLFMLFKLOOGIJ
ILFMAJHONNNPJNJCLOMNHHCNLOPDHHPLDLBKLHIGEPHLAELGPHPKLFMNPCOOBPJPOLGHNNPNHDHH
PPBLHPLHIPGIPFPNFLLLPPOHLKKLLNMLPOGPMHOPLIPHJPLPEOBHMNLLLALBFKMFIKPHNLGGOLHO
ONJJPOKNANLJGNKOOHGPLJLJCNDPHPOHPPEDJNDDLCCNLPGPDNJIDCCLOPPOCGCOLPPLPDIOBPKA
EKGOHMPPPPHNCIPIJLHPPFPOPPPPDPNKHCLHANNFCNDPJBLLNNBBHDNNBHPIMFPHDAEEOOIBBCGI
KOAJHMNGHEAEIOHMFNICELOJFFLPMHBLCPDGKGCBHDOLAOOHKFAJV407DOFHPGKBKFNNCMLOBECI
EFHHOLBAJLCJDHBeXV18bLODKKPHCHPPPFPPKPPMAGPKPIMAOCPMEOErENKtDBLFMGCIMP/EACER
AQACAQUBAQEBAQAAAAAAAAEAERAgITAxQEFRUHGQ/9oACAECEQE/EPQFE6aTcj1/ADePAOz7xqWx
09sDf3gSt46TvzAXCsKZTzvWuuQJ1FlyybSomFsBbAqOsPsTNLhUCNcnRqtgoCDeNh2lx61nWKtg
GLI/iKvLe1cNwUu4R/JWmobFYWowq+AiXxBtKJ04oY/iBKDNeQROEJUe4LDNxXLp5BqUPADFWwKw
pBhEuBTjp5SXHvVcuXtLi3kaly4NxNtVc41FJskSs1AlYXfWdwwlxKyFw28I1CkiQJU2lYdZ3kbl
RgP2MW/ECu2VZ24jvP2CuW78QQaj+IMW4bOL4DuXFlfZcYG4xK8AS6i3kYU4eA7lSooRcjUvnCLr
OHUBYAZe9IpzBUXgOBGUMTAXAwpl78RtvFvgGpcXbBFxqXFi4Jce/CRb4Rh6gLCKIpCogxy2nbwB
c/zi6YrChFXA1DCokfCOuGpUDC7RV1mH2VeCJzfNNSmVNoOAwYu3DcuXBGXEuUcgZREgE2m0siny
XkNoRquGiUZW5LOW2Wy3WO2HriJ29YlSyopXDZLIt/8ACgLgEQiV/EC47bxbg1CqiV/DOtJ04v/E
ACIRAQADAAEFAQEBAQEAAAAAAAEAESExECAwQEFRYVBxkP/aAAgBAREBPxD11ouJg2+2gxpf/Aog
F3Bq9oOYbzBs/wACUEoHd0DmXD77bUtVQUHaRQxCrI2/USSkL/J/xK1cG7VouVd1C7rvVqiPe64B
48iNgK5B/ZiWjZE/IV5jXmDNS/yFZKDIiw72KjANYaX0EbEfJdblDXyBPJV0gAZ2oPyIeIg5LlSw
5KGxOYl0d+ioKf0IpLYL5l3EP35k5ENPAg8kU4gwqLahYXA/YN8diCO2YlQvBKIA9BLIJU+JjSJJ
AuxG0gGEmwDCchg3scLYKPq/TS58vCw5iwUQOWI3ZTmPJNusEQ2TjkbfqWaRIHdVBEs7gXY61CCg
QPCVNmW4IkjJBr7MvquruBRc49q0MPqBWzghq4Ab1QYs4m3YPiVod1noYYVFWAOqhEcjfyf1BjvG
XFp2WlCAOokotvooJTFWfJaWx/EVC2salfYC8w476WgKuB8YvKWwPEIkM+QT0kBsyotGQwhGkLGo
WeDniUmsNC4Q5L1sDNYAZ6SCJc/WAkZMdCVt3OXg0M0TS5vCbZjUUEX5CHofhC0A6pZAgXLblFPB
zT9GXRcdbIU6i2kpz524jfe51UsQo2QVpg3x2ifZmRJwbPy7Q5HmbcSjnvFuyvyAuouoKLgOdEH3
oKSPyxoLgFgqnpZUMFFPgJdlChk9LyH0hfNxtv2DYAR4jFqUs4+jrIKPDVK24XSALYnyCRhBGyJP
s+CSxMhdf2JTYnl6Cog/fF9IW7NMTUEII6IZZxEa2FYVNib/AJFd+gu14VCO8it6EkB87ueYDpCu
JZ8QqZA/YN5jmCPW5ZE1LPE1IlZLMSRrDVvC3bJVzhkS5JVzEueQX5FBGeYquQX7N+SyCu1lB1Tj
oa98Nq5CzGXrpSN+JYlzyVcpKfkA7xA07Hb4HiL+TRKVnto2m11AjvgZlL3Klf8AhQghOIx2Ac/x
KWRLkAiGUQ6b/h8qavqMuPfF/8QAKBABAQACAgIBBAIDAQEBAAAAAREAITFBUWFxEIGRobHB0eHw
8SAw/9oACAEAAAE/EPkf8Dg3L4xk+v6fQXzi3vLu7lcYNcg6cNW4PhdYW0x3AuOluL94WiZVmKC/
TInf9Ygaed4p5cNKr+NYqijx6wRt1POPWN7XIqy/SVzp9uDsWYxuJ68YMCaeH3iNg128fSWJH/H0
8Jg3tneM6785a+M3A9+8ihfGJTW4ZcDbde/GNA7sftd/rG3wXQ+LDf2xEo0F9k6xqXXBnw04k4V3
lVVwzQM+khLvkwSzdzThFKa6TKdoUFOB4Pvr7XOkCZTf/uEmCDfTTISS75cCaVZ4xzQt7yqqyGr5
zg1s7ypd7xeAHa9TGyC64ucqYS4PTr+fp4Z4MLZcUw1Hw/hwXK4q9v4zvFfpVy785VeDOGzCPxlc
msr5M4dx7MYfLlbdYr6cW64xWdOCncyh3txTK3Ky+sETmPeVDfV2ZXyYPB184qGiaxEim+fWVVMp
vATNzB5UdeMo7X5wRRo3mjpEwojb/OWbSnrnARQULNHeRlWWHO8k5Wda5zYb17xTqZQFbPEmCgNd
XxlBNf4yAE2hQ4M1aNgAHWVFBpAe16xQxST1GJRpNBOHFrAbPxjAEH88YOgyum9YkObqkyBvn55z
Q0YGpzgTdQoQ5cEuqMN3Yf3jeSg6CrnJgCkPT2+8AdGFg1cuUERKc3xiAJF3q8bxKnAyt/nIrYJy
XvOT/wB98TlDfGKoRpPHGbdz/eCRk+JhRZtODv5xKK0feXJWf849HyAnP3ye156mNFNa8ZXzh+p/
f0uXz9R+2X19ZrnH5uHjzkRwqt6z7cuPOLcUeCYOWzbrFbmsqTrLrjNJNj86wd63fOQ4ddmVWKPs
xL11+cKAPDsy6yPjCBHSbxXY/wAYfr94h8C9Bo+nsDxl2iw5MqrzSbwJenifS6kPnLSbPS6yQGjc
Ds3PthIgDUXCcoeNaxYAJyPnU4xpYLyrtb/5iq65Vwza78YWTvEyKaaR3c2dmvBoxR4A++AEtPDl
tTA684+zNvfWQaYbDGGp2hwHj3hzwnymQgIK5nXT59YNanZvZicQNjjCr9lynOp4xbNTDEeD94gK
DwceMWPDJocTNpXy4tlkuvbjp8/HH0ENrgnLYb++XLh+h/D9JZ7x+df/ACm/ofGPWAu2ZNcffDjO
dmJt8H0Nb+nD5x51x9IdOBb6PoXrIF4wMdc9+MNFnXI94qHkxis0Yno+rrNx17950/PGccdb+oMv
WH6wYqTm427R1ej6bRfH0FT3OMQoULz6wQdlu7A1q4uwpBaHfZ9vOIshqeqaf5wSrEQLtb19s0Ng
6rMcICfbnGXJQuWqvP8Af02B8n0VLpOz1ng07vrNJfUJcEJbwKeNf1ieVaFIW5QmkN08PThAigQA
WKb/AGYiKLw6Q5HLIIPv3iG0+Gsui7PeSVeHg84qq6AHLKZDiUDzvJNzfaG8WW8hDX7+gwTzgYM+
Mn0R+RH+cT6TE/GLppcVUj4DfeXdpRxxoacp3ixBEAiBEyM5PjF7MhawJdgDkvGBhAotAcrOD3i1
izcHMEovq5zmo3SKARRIB0Lt3JtPLkOkAC3aoXcq7mWbSDNLFUqXQxE4QTYsD0jEx6TkciVg6RVR
hQhXXGpHPY4FKEqDw70uLhVU5CMXXR54xKNwsp4KUH0twvTnAVkJ3coJgFJG2SlDb4Oclj7XAcxN
M7LdmLLzeo6bV0FTa4faxeJSirAoa3vrH5CC0p4h3epzio6lidfu/CZfiEdw3t8cP4wzGTXCOU5C
NqTJ/wCFaK4q6Pu48ezzamqCbIzdwIHK0gCqPibrrBaCvfym3EurZc1SOEKeR4T2LswceumPIO0+
BwhkroAMddR1lFX0cpahy8OwwBA1gDA2NiBqYUj9HQlFcFHVd40QbN0eAaX1cqTC6kUJB5qX7XAW
QUkYBklLc2Hn8kyVl4VA4ZhuWwVIk2I85ChCqgOCqr93D2oopQ5YcB5dY/lwAKZopS9xwshlwCuq
sDjt3vKNO6EBK+zZ3TBMVGXYWKll4OHIdcGQeal+1xXtoRQdI7H1kkB3VwSzRgKw5wLCH10Y3Bos
5vzioAs9Y8GqrJ6M0DQl4wgZQfPjHDEooWCnr+82KDz8vGEHKofW7+3JYaGmWjejc8467+2aeDn9
YKqcnDm15XzgNDTxhS6oOt5JBxgKzGE4Z2Y73k+ttvP8HLjvLnJn2z4+H/0vOGeeBS4jggTXPeTn
NKUgeASnFfGcdBioUMMKDt4XrJ31jBUhDeLXBc9wFD8j9scX35NCH3br0+MSQVY4pJ+nFtDkVrKG
9O30rg4ZrqlwJ3K89e8lZpdgEHg2Hx3MFOeimVit1Bl0gkuGPqakEY9MUpxgfslXmntYS8zvOc/j
Uh1XawBe8JxKipiRTkK6db3cDzkFiSEchvTTbh5ce0C0dwqe5m3w1VpRKkA68F3cI8JzNLW35b+c
KheyaUQHgR4NesY9mqJQ02MG+H3jVyLAK2u2KK+J1jkWQdjgmzYWPUxVlb/NNGyu2czE8GAHFofS
8+LgnbKa0Yhqmjy9HGKTnQEAWAxDabbivvEocRwQJrnu5KqUHfpcCw4DH01SOkHIE4bekiY0aAKk
BEFCCIadayD+5eLI/pcRJeJe6o1sJESEnOO2Y50oIdjsjp+GI9HKWcFQdu5iVfD++WBFgi/NwjC7
HToJ4lfk9YOsASMjEXoZdJSXBqBtXZFE2MDejxzhcOK1Mwq7dwPgPGIqFxJsB+NLjTM3EK8jVJpx
qa3mtKAwJQXZqc8BryKMs85qUsfecqqdPGbdUfDngom97bgunTsmBVgwdfOBwaDgmRHDpnjKzCQ3
Emz7Oczm2627+OM5RBonEw2x3qtmUGFaMctUYAZYavZgOmjR98RHHPk3rGDBvne8aigXdwIGkSX3
l8hTr3knPefBijxcnf4yuUYBpx8P0v0jBzdsQbqNHTk8Y6Y7QhRdCN0d4qRAwNrAD3rf5ygwrqUv
FpFSN6VxuFSMo3yXVBhOrcR56xfuSALsBtHfnISOBqtpG0RSPTlT7AwyJVSmrL4TAuJAauTQoCIw
NiWFsMGl6rzTZVYPovvJoShCWUEdViI7fLiB0qG+UVXTNyXhUw5mIW7HLSU8cYudcbVrlpKvWGXo
ETXYdJVwGphxJoyjLsq6cTvHY6hBFHdVddTGqy3wrQJaKOzTh5XVKUkSpxwjo3MY8MEMBNAJau1w
+VIoA3UI/Nxpb190ikRFAE2a4wcSglSaSApdi1dyAOhSaQRsodLwHWGgnR6hSh14DeFxGYYAKUWB
0GGieIreaIX2Be7i0NXVCmgRAAAsAxUDoQWrAD8b/OOxPJUq0BEis383Od3HqQUJooF3HsywbiwD
S7e9wm5bikQk94Yd9v4TRKzsBe1zXuAY2MCSjgR53W4/06MQENKt++GKgKgI0Ef3gNE9Rw3+jbYA
FTSByN27jMe5W+9wlYKcALwqYlmWaKgFW1KM3ouo4OkKOGoNACcdVTvbhCUCyQTZQ6XgOsB7UQfv
CXxQL2uJjVwQA0AdB0Zfs9fGaAlXfwYAYHXBJjTGocb4wKaDzm20heDmYgIF9+cKgqmfbKpKokGF
+cq7RWCprWr3ftjgDQeGI+EO8lSCR2l3zvCoIChrnDaSMHA2cj+sDS9GLgm1/vBtTA1reOjSj2GJ
CLegZRI7735wbVd65tx9J988Q115++RVUw8ZWSBzs/hwmPP0Y8Yhhi34xcvrP5xWYJHr/wCFx39N
XVcq81+gF2wxDWtXkyGzjJJe85k3rBeC/nBDDTxpxqAky9+OMi4EvWVpBN3WIjxz5yvZ3rFU/nGm
ta3gW+s2UPvmiJvWbHdswb03rDaDxgTZOxd4OBeSwN4prju+DEgshRvnrYfGMECACtxsPPvEkVNF
2En45yQ6WOjhwmLyrm2bVV9c4p1Vwd5Td++DB2WgowMbV3yn+cfbq42RvBF0GBBvkg5xBtWJ3jAs
Cb3JlENGKd3ATZ1IxnjGWKmgEXyv+M47aB2O/A94niAl2rvzhSAw1zrBnYISJCeM8Ip7uCOKTWu8
TVFbXj94uLs753rNm6O43v3loQW4zj7YTTwavNwxSHR5yCdKbcQXPbnic4/OvnJ5TT30/Q/+ANfQ
+33xE1nHw4tM4N95d8ZHjHx4wFyYF+hefGLQ9ZLXIhb1m56wJzc5OQGxcScQxPHWS4KInOV/jNtZ
dZO/dw9Y700+3OBWfxlSzWRlmjBD2kxrt+Mni5wZwm/nDLFoZYzZ97cAFBdKnfEyBKAFIjWvGKko
HZG83+MBeyAsdw4/UPzmhJ85sawC4s+uldY0Xv3j9LqZKcmtzd+cpHwHuXDYUAU7cII4NcYC3w9c
4iBOllwIORrS4JcAg7R7L3k34WkJrx6cCIjawlm+98cfGVIRDVdtwo0gOLrHvRGuMoHLUvb/ANxi
QMkbPeAEH4HjOShpt8fGMZETThFpOLePtkpkZvvIQ7Q0ecdmzHUzf9Z14n7+ij0Ah/P0n0MRXsUR
4A24ajaHYbBOnWzrL2UvEi7hepoecI4ImJFEKN0TaY0iqqpPCgz7YPTmhJ3nLiWBuwFQsFld84oY
oSOqMyXgzZtq7eAGvBTjneQdYocgKmBe3Rh4gIjYFH9mdZO4wwCKC+NrJOWfvETYOq7cQBLXSggg
Alqc5AaCxxT1+cfxrYIErBbGAnj5wgUnkJ+MgkodByHzgEFZVFDxjvEhujknX+MgB0Ma7w6AQNkQ
cdA32Op/3rJ/sbtm9AtsGRA1QYfswY3rLED75zmUaEVcD0p7nGBWdu/vgLrIn2xd4x6ko6V0YagB
I0AolOSnOaipEY/Qc/jGFqMRyJfWIhNY2BWnkXV1gbUG2uL1rvKVlGhABDvaZUc0qECr+B1iSMaa
hGOvKSLqYwND+RwO+Dzm05C7xKCKOdz8ZSip0nWBbVvjvFx2N/fEdYBgDFE2HDjkYI05+fnNfQWi
iIBE1wmIXGMg14rPz1jmylWLYAMqqga3c64I7OsgxAFaQKySaFvLxkO1ktAWxO1SXjAdAic3dcZA
Le/nDEkYg4QxCtkFNJpZQF14wMBUbzzmhJx2GK0Kjes5ClV0FZ7Cv2cQqhWRxIsE8jcUd1rUxSXw
/v6X1kXOMNiDpGJ98MT2aqX7lcUuKFETkR7xTzYMGQVbMDXYt53i83p0Yum0W3qdTNz2KXRyvwj8
OFARIuBK7a3xhud3O0BUdGkIgwyAqoASeAIIx88uWL9RCgpVPMYUrvFxNGGaKBhomPZyezJJPs1A
8pF0POjNSw3HEFmwAZ198A042QMHxllN0Y5KVTzGFK7xnBfU2TeuYH4xTFYFQJQApCKq6TCttAQh
I1qgKefeAa49GhhYIArNRTyCAsIQPglsIlVUfWNrMoILL9gH1k2SWAKi0SJDOAwnQPCCQjQSkDwP
VytB6CjQijHYXoV1zhj0OFBCkEIC7hdpjEgzcMqKsaVFJFmMLhFcBJGCIGkWnnBwixsArqpVO5Gz
GKmhi5lIl5nFZMrYIgikHSWgXzja5qkQohUCFNLK8ZOkHi1IBpRKeOesH1oNNxrsGgoUUrNTzBjC
FcjsGHVmRPTAWpQFQkoya1cnhwAWgYla8rAXiEqYXQTgUdhBWgc3AWEIcFTTxY51phSzEQF+maBQ
KBDeDtxIYBJ56MhRUeUqR26kggEcxgMXc/WAiIci6JKNN2cNeZo5QA3h2ROAgHqY1TlZpDOPFHA2
OMVUK+RbnhC42xSjZzrir6xXLt3gvRQVAo7vGPQBWoxsJApZdWamWB1SAkpVPMYUrvHP56YO3RXY
AWU4q0uVBxAWphQvHBUzj/DwQ18zKoaWaQkTgq1tXetYKZYUGqCKCHgXaA5OZBto2DQNcQ2aoYGm
noBhAA1pnvS7x6EZCijoNFVXFUOMciqnuB98RkPIpi8JC0jteMlulYTwQjGAvpDnEgENREAgDtbu
84AtHmhQEllUCwdm245QoFUhRNgAnBtebl2JZlQGpoVhNwnC0Vi6I0jhtLTnU41grUGNDdUdMUid
buFHgJSRBUKAFCHjBU0EigJUUIPENhiFA4WECM0yC7VbbHK33MYuG5y2jtMOBWo3R/vrATsr8jkJ
prxMkD0/vDw/RyYYuykIdJsBugeJxjqOUwdqvKr24vjyBCqoHRVYd3FOAVJF0i8t7uUDXEO86M33
5x3KVQPlBmUjQrZVW83u4LSSqS4Suk8mFEM5HJaR3ve/nBQCxKiIhvhNOIteC22JFvhDXGjxgpfG
QLDGclDT68YAc2RuJjfB0bPGaNQJX4VZmnghXA4KtmTYUIgERDfCacRo2DsCiwfZk1Q3Triu9sJu
61jMBRIPAq2QNWa4xIDUeo1pWjRpvB4xFVFsVeYOi9znNTkyokYGiijORfOejhBUggzixS+82ZzP
fgLDE0U0XKk3v2OO7hGraORkEq6PePVYaiERLbIpOxcBAS0AA5Yl5h3lBJeeTaNfvjiiSqjLEWKV
212+XAgcCBDZheDaw1v3hFhiOh9bSepilcriXkTjFyBRhiIgmyKSyKd44BaBQhSAyh3yXIIqcIht
V3ssygyJq3Nqt9uchHZikorpYb5wtMxKj1Vn2w5tBj9W1nqzEcjVJaCiWigxuwy80rpjFZYCAQDZ
5XAcoEEG2AJCq67XzgTQOOvcSyu3INLoQBFGpAI6kzlaaYXWk3ldqK1bVU3Squu28uL5zmQaqGu1
5vONpzzFe1ryuHpA6EQiG+E0mCBMCRBADYJOiGk1ibgWmAhMAAk3VyKPCCoIhF2UH5Dxly7FJolq
1KC3wZMTtQPa1Rdb3qb3jj/EIiIitN7p2YwSqzZqiUu973fOKwMOdwmkb0uzh8YXitIpoCJ4Q/ne
OhO0xUtVXlXe7ixVwUPVDXrnEYDIlQIbfB1lLLFCCRF5R7vOU2VSrc0Mb+8hDtlnPbw23XbctdAJ
xmzlt2teLcDFArdosadoLFsr5wRSAyAsFaBXRJXziRDVIwiCtBFJxFOFxIAayAwKFgpBZ0dGI6A3
JOQvANXbWeDD208AyPW85IaAAvC8/MzRoONjut/hvOHzlFxzU5zrATFwKclzY+PoDy48469Ge+cc
3r/GAr4uKcXIb1g3ch7yBUZlJJnC72fvGgZIqqc7waATbaZRcHAGXWn5MVzkY+Jq9OJpyPhzk273
/wBco1xPWB3y+MJLejfjEBzFOnByUZ0lw0wEi8/rOQNXYkUOnDI129uVsQjdd4xiiO5tdTR6wdgJ
Yav94AEqu67e/wDzIn5NFcc5Qlgn7yGlCrXrOXtGOu+ZjQKldAgDQ5djZKVU8R7x0sIWDzfLznAo
N8kwh2K6OMCIg15dL4xEp5Nnm8YNKhFB/wBZSmgbvhwEQFOR95sI2CdYXU2c/DgikbqrefjFkoB5
i3EBWsi+cKLwI5KrpYp25YaED1d6H75KNVhNge/nO9tGvLy4Uvvlrb1j9gTQQ5jvzg6ER2wwe+cK
vk3CBeHfMwWW46cuKtRXRirh2CInASdhjsGgO7piKqLTTX/GSZola3XxhiCgtQ6wqL4d+XDU2j3v
Ot5/tj4fpL9d88mf98ZfnLgjpK40gEMHWKMhMvnjKez53ghwb9d4F27XrKPNDs8YXwz1j8TW5Mu8
uUTVpLxjgOAW8+g5xIV/TDT5Mj4fLvBO64KY8jz0TFxyYJ5c0Ic+cq7r98E8o4KVP1hqP/GRVJXC
OANRXB8tTw6ffzhjWiwsW5sCgozff95oBEN+3+8RaAxLVx5UBo2V8OBUQaHc7rDCh3HGh/Bxl1Uq
iDswWpTKGqevWcwaA+PWEovL8TCCA+feUvJPFwJyD4djg60NNQeL3hFDgRU4MQdiIbt/nEjyNonO
sKIivTi2N0mMAi73uBjXZHW00ZWm6Ka2/bBYKcOlrVygKQFMH0Hx54yvRml2cZad04Tg/nJ5FBZL
98HUARUjetZAbrdNfbBdcaq8/H+c81gcEfl5x2kPClH4esgmtBbRecg7CbLoMUAoJ+82Gm3bigwb
7t1g/vJA4xL2bP7zpn3zU95evoTiqVAAKqvABV8GEFBEwlUIIxpqJwuUtpW0i7hepod4B4VMSKMo
LRNpvGmNdqk8UH9ZN9Y3lydYoh24aylpgqFgsr0OPJKlOKM+jtNi7fAOPBrjneGzwcax6QrhnqQd
VWGBRFY0Aol72ZCHnOBQbAILKDtgHlTL2lpGff7YnMrg64JjgXOXj8ZxsXxiR7OTIzhXfOBQAJI1
KXXG1h4xIo8mET4cAhtvrEVq1HrGjhXpMQI1TIUHZ4wyFjYtj7w2BedhzcgRF7Wc9YJYO7Yk0muc
aL4IIUfLgWUgqx6H/eQgiAPD7wA0TZZv1vGefYBET1ihyJzesuKIwrHKSQq85bZ6mU1V6O8cMtLS
KMWKU8GElJ0Q7wDUVlXejKUTkAQ6cgRsQvGQLVWL6cUhaJo7yKIYoBw/HzjEMJC9/nAWTlDYqAjw
c4OhNBoKiXvY4Bn0otOxQp9sAjQpE69o9ZJqTxSr4/1kMjddiPOKdHVwAag1o56xg0Dl8Ypi1XAj
CpdrF11wzcFB8E++LkrUGdHxhlqgWYhViLwhjsX3vAElTu4Go495W/bH95zDOG5cMRcD1FFo62vk
1lSEMiSE6AUDa1XwKGGCijpHh+kGSII9EDXYq87xeaU6MXTaLa8TqZu8BS6OV8xH4coBmJQJXbW+
MIxuJWgKjo0hIMMgIyEEnqJRj57yvt6EcFKp5jCld/SqoSAwhDElFp7MKldQqA+RF0POjNQz1lwF
mwAZ198bpjaQIA9TJGT2aRgTgq15XeSN1LTsHudYcAgxSAgQPZ3AHWEXPCUopbKvCW7sIMUHhhQj
QSkD0zVwxi1CCjvNI72t1eshJoBNtGUQiQU9rhxhEAFqJdkUhZ3MgS5FRQIUVImpBhhVIeGlCNBK
QdD1c1t+pIYNdi3nfjABYlILNb5gGIFHgXAdTQEDqN7uA3jgJ6JGF1TcIJWqV2VoLQUgoCGmjvOS
meZ+sSKCHSgZvY7BrCQBpUrVgLUhl1p6A8CjuQVoG250GP8AhaYWk+K4kINQoi6SEHRrRmpYiCh2
OWNChdKzEjavSArDaCQsoM21jMXS0AFtLKu7xhhB35uEUgoQ00d4jBN8FjRCktiu5vEOpJpKwpKK
KhLoTjHbKaKLUPpes4BPGopIEVKcEHWGUe8cwjQSkDwPS42jgo1BNlV07oaIExSNNJIE5ROh2IDu
XAD2ldUR8AkF8p1mil6gpEJIUIddYKAQMmUaiDkK2tPOIoK76G9IN+Fs1ziJcpKVCFUJKM61cPIM
00MNVCVbOoBLlCAoUidbboXaBjqJCQoDTf4xe8Q0VPByANfPO8a9MafQBIOxtIV5M2y2UYQoljSs
prccdC0AoIQ4ZxwbmWmNYkCA+AwHlk1MqKMU1fxvGNiUgSCsm0CuFaWgEIum0W3qdTIzWACgaLYa
3Et3YY2oKpCT1BBB0aYesYDNoUHY5asoXSswJAFEOqVlUIBZqyq4XgigQCPRtPhcIWzgAgjCCIhy
b6xFJw2+cBWUkNcZalfzgfADfxgA8V8+P8434GHA+H8OJO8/eTHWsFjVBEnko2ZNADrg4Sun3jgO
VyO1XlfeXUuAhqoDxtXFHIKlF0i8t7uXTlEO82pvEknUA9gxxoUGqSaq827uAzgrJcNOn2byRB4I
5LSO9733vBgrEREROeE04JeC82xIt8IQ416wWDGQ2DGclBnFDxgMqiNxsr4NDZ49Y2kEavwqzDbS
FWR1VWGKZEtIMUVqKCj4wXUgoJ4DerWzmuKLnqVeaCG+/OWPGjNCqsF0KrDVV7wHjy5+ArMtSZ3a
b40O/WG7lFqQAHkAAPE1kXxD78FdcGE8R0J8CszhHBz8BdYpZJJRdItqPdyqNqqXeYLC9wzgzlT8
gS61g1MpWhAKHFQBe4Z1+YyXexGY5XQJTqictxBLnH8GoVqEdC7Q5xrhIGrSA04I+QtNZUQOAwlQ
IDg2qtIYojA1SQihBaKrAPeR2cKhOILD8YPGhICEAbQDQHWsBRgaAILXadZNQMYGOtrPVyM41BTx
VVXjvBFZQGHYWDOJj75nDCqUseLfcwUHkYbhSrPt4wFdsCdEIKh41iByqkN7UNV7ftiGSwk8NJpO
NOKqYUg1RKbEUlkU7ykrSthCDOKDzzLgnU4S/MSvtzTEAFdDbebd3CQA60GxrspZjiVu6Drvp7El
+TVUKqMqARAAOA5cBDawQLKXSDpNlZltgxFAzhd7dsXz7x1i4iMEAbQLAP7xizCWqERKtiKfCneD
6pUXGuVRYoPMX3hv3ApIOhVvxjTCgIjLELtBZbK+XLJO6oc0C8G1hrfvLVKgHeaGb71hEoKkhWwH
gVX5VycUivwKRdlDXGjxh2W4kPiJh+MJFQBRQEAXoNB0GSaSFU6illPOb8AdABBZxiip6R3lZzse
ViY1N05Q63gCdmCusnxxQFLTj4c2lyau8GXI5GzJxig6MNWPU7CCEHdHMOfpHocQgT6RCGyoUdY4
4qUdKM1l1OMfBfvipPW3xgLRamzzgnb5+cRNXDQrJSMoaBruzwOUDJr850TDxI03YhTXMg5pzD1i
b2xKnT7wNyPYI+G4hoAMu6FCfA7yACtP1nXOPegAVQRXWtjOdYxClPGNBJv2WQfcFboBV4tirvyE
EIAFKi/jJhQEI1KCzix14mHKesNgCGneCUJziN7TJPk3MbTwtPJlAYWTjKphUQLyr0AKvgwEGofj
ED62H43g+JRUdaWHCK/rDRSJlGXjims1FdCq8uCRvKb1Ie+bjSgEkmxRTjyDPhwSgAFDTAy6JPLv
CDwxIheNYEAAh+xhLiDPiqdejGRiC0LZDZcNBoSNKC4IlQNDwvzlgRdg6Pn1m91DE68/bKuCedXj
rIyAa1dIbcLynA8n8/xi0KE6TpN8PGMUMpQZz7wo8AXQC+vziIpe9uPXgDem3w/znE7Ib2R8zHU5
ilmEip9Tj3hQ4JZyGVBBnE3fWA6ofLm01Xm3hxZ2SMJZ98YsdnXnGq137cRI8nGCBh6dYKWPiHGV
07wSzXYfpwdvzjjJXvFugckhrjVGidmsQchMyElmqbD441iFKVSggUAo1U4Ay0FGBK0pwKR6F7mB
wHY04KQIGi0RejJfCCcJwRUYqXRuYyQTJqQlnVZhSD8JZWhopJ385T8YgIdjljZQulZguAQFhh0q
0J4nzgSUCAqGNGrsOsSnaaAiIQaoUW3jANgPFhChUVrrQbpm/wAklgW2qSMRK7MuuvZoFo6IlHYG
8U4tYSF2WipQUTgzj5FcEktQEWEt3YYM5SQIjHHClyTYGQsUTSouyvvCmErjIGhyZVgL6wh42hik
C8km1k3iCEigJSOtCxytn6EcFKp5jCld4RmwSQL9WKlSQNTKGApEFu+5StDFrMAgqRAMezyi7/eF
CxDVlIANQA7BxJ5tSEjWx7gpBphGDwWpYkbRHTxxrEu1JbwoggSBAAG94AWNcaY5OxD0nlkDyNG+
D8TrpR1j1IhSplTFkFOG74JNUSdQ9QpABeW7riIBMK4EKoB2x3u3CBApQCoytIit1ONY21K+w5vC
X7YQBPBup2HSCDg3vCKBAcJ1/jIas2E7epwEBDg3vEQgZiiEomwAlA2vnBFPWpW5GCw27GQfGk0G
IPAFPCZIbBNXYXR+8heesQBDfTgELYAjQd6wlHyJ2f8AeM5CAwsEdzfdw2WDaug3yveOWyA06eH+
5i0aaB0KfaV7xQMXlGeuMoeEAm3595GBGG3rBENgrBo6g42lQ2EDFENgNDGQKAslXezrFohLgVKd
x84ZKU2rtDifoMLkgRJt1/2sTY82nj1lzSIU1bkErvidYivagPMPeBsV6nWLYS3TvrGF1Adt/GUa
UXkytppxfkmCGnnkyJONRN7xfWIjuqj/AD9eOvzm0pmiVtJREdm4ij5KY9d50iIs8wC+sHwgBBOK
jX75rR6Iqtry4Xc4uENo0Snlh0vc5xqtaX/FVdZErguDJFlIR51kRhCTktI73vfe8nnUUGeKh+ME
IdltCQ8hNTiawTx7pwSzizV5xkcMbI8MS5yfxJ+aO/vgZtgAFag2gq6ygF91A0rsoMdaMvBalK88
p+saXxAhWoDwVWHdcJuIqCdAS/fATUCIeNWfrNZ6S2TyUbMU0BWKShXSw3zrBwSACFnz0+cGSyHR
EiFeEo+tZR5gJK82pv43lweBHtb8N713vAg0AAbFt0rte+8voU0aRibEdl7PGGEB0kLyVwB6cJgr
au5WXivlxLdUGp4BhznNNaMaUFgsNm9GLm4uUeVXauIoQ1oBIbQmoamuMMplFARIDQwN85pgoKqw
ROXpBPe+cGIoIFJaU73vfeGioAQE2UNMd7xvXQtfIDDvj3iaQnRaJFvYhDjR4xi1UcM8Fhz+8NaE
VDtQg3433kGJoyAZACCqNVdujHJIW1pqmFV36AOjHTF6Z4O3ARaHhkboib04iooOgwSCjpxPd9dm
D5EgnjRHpG4IAYWsCfe9ZNcAreV/7ePEQFKAW/1hposHmF5ccYEBodXyfF3+ce8NCfr7f84lHIe3
v48YkUS8FrMgaNtmt/8AXIIdgNc11+cLohDYF1z98XRwKpUHb+kxhjoE4fXnzrJBvb1m5v3PDlF5
0b8YAbGv3g7U6Scf6wBKA52YzXZuT3hFWgmy5BgVusTVmrPoZfjGMLKc/fArl8cZDm5d60Y1DPLr
HjfGKr25R00m8ab/AOM2rj/OOlzuX7Zug+bjn31ga27e7iz38YLsWdXlxp5Xz1gC6fzlmyuucAvK
O9Yq4VdYu3jz3myNvXSeM6IpCrmr/GSjoDs/hiujRnG8Zhgt1oxUCJmzRmNIK63munS++DLVH4Mk
d0njCKb6JcYp5H1M93Ga5PLgCVz6wKUzwd4myEDX3xVXQDzz50fv3gD2EIbXACoWgGt87f8AucpV
ViQU9ZTFV54TLqb07wQB4aO80VutB0nPHOISTRg0Hi+cIJAs44hxDLVFCBw71eNf6ywhFIKb9+/D
iFArAVDy/wDTHcyO72Pg6fjBRBCSRo5cROuAXl9s694piI3HQ73kRuHUWvrxl1NyHl9jEEUIahXX
6xCBILvQn+M7YEAeU9vfeEIKvI3Y/wBODKAtW35wUbjo9HnII8qV7fGJZyLzoMQgaHb5zZoRWcPH
vEaBkl/xlqqhxQ5yQPz1lOrT39BmT3+so7qq/Tg6TOr9supnLeCBsfn6W5gMvK+MEK2v6wH7NYuC
SfvGMfPGHI4hkn+feQqb8mJft3k0qjMRNV95ABNnLl4Q55xHsv6y6D6DIzRzMEdpB/eDBrbQOXAN
K8jxPGEki7NSc3zm0OS6XhMTQvD0vnCBLeHlP8Zw4a0LuZzSp8YwR1N8bcLad+85IxfJgyQa6HAE
Es046DWnCVycY0TxessGnkfeBEb7TvJg4AKafjHiEK2w8/8Abx4ESKNz5/GIlFLDNePDgXJBqqAu
MaElHb5wIECdPDjeMAAHFbzgoYA7Q0nd8Jn3Ktce4hdUifBiRquVXUPOdJRBbtMJZEwSLjpRTbw+
i84EhQ0+P/P6y7UAqTncv6xIaEQytt/wTKqVgcCX12YZNoCAz7/qZqlWnaqTxcuKp3Pt+sZtClDV
PE7y1gRQXgySajSc5qhwus0C2c+sJVhDrVyYo2nHrGAKQejEDXjYa4xUAoPU1jLrjFoa/wB4iAm+
MesELsS/hw4fpNXDFWLygABVV0ACr4MACECBBVQRiOzY6yl1qwkLuF3JodpgtEiYgUQoLRNpvERR
Vqk8UGfbKusTrqcZtqC9Yna7bCAXS8u9Y6kqLeqMZjwnJ4xqEqxb0Djwa453lbV25w5d5t3ID2sM
BUGNpSP8P0op86Poic9dYN1y61lBQTffjNklXnxlnMikUIag1qfbISx23RS6IxL/AC4AlS0m9PXv
WFj3IMKBzvpfOWCABwn3v6wI1HEVeQGCS0Nx317ciAta66uUldqZU1ds4/DhXFRWIAId7TAWzcK4
F0Fcqnm4DYc5UyqhOLvESbVN67zYxakA/wC+2AUUPPF++JhWhPJOeM3gm36AVd9w4MnOERQo+brA
sBCOkCrqSDu64yjoBR0+/bigEXS998fjLIV5B/X2wy4U01CAg1o0zveGSRU3NzAkFdNiBZdC704g
goSOqMcCSYm6cuCOYOrEVQ4Aq8/nA0Kih1RKIRTc3pN4LAdGqChobiCcVzWVAKcJ9uNZfVQiABXf
d1rtyVqCI02ZAOt2KjrmmLEKoeg7jhBGh2zQvhwIGA6XyPGFCoXVDr1iLGw4uCHZ0OWF1rmmArug
5jghVI6HmHnBKJN4Tv5+myvHrzgVh3nhrWCAzSBD5wp43gd/8YleD84a2bmOyQANEkJyoJO+MAQv
LxtTdogSoUgdpANARRpEdieMuuTICEOiBrsVeWuMMCmQy6bRaep1MiRIpdFK/IfhwoVSaQJTy1vj
esPh+h+gKjo01IMMYQQgIngNEY+eXK4fsJkpVPMUKV39GuCgQGiY6pyezBYDUKiaDcXQ86M1nnWc
QXsAGderizxLRAgD1M2m8dQ7vvSZABKSmKLVAhR2xesQ4t4aF2WiqoKJwZt98NAPU0eAR2YyBHI6
M2oVIjqpgAgmMjJZqmw+ONZBMKvSQIAo1U4AwuW1mw0g0JKh3g30vZ2RzkagwHS1028TeoTuvKgV
OSOj7iPxhCHJDADgowaUOYe8fICIHUADVK329ZQEFGoAUNhrboLrnB0NyJCIldBJAR5cIiEoTebU
LQUetMWyHcIgAiIbQiFF55w0oOGxVPHjWITQiQi6bRbep1MRK2DYCV+Q/eMXygbHFEFgEd3jEXCw
jJEFFV0Oh6TUA4aKAAkXbFNgtMJRICKQqi6A0gInOhYBhYEATU0gKNdPOEtTBeQWgUsG7EeMNaRl
rKwFEt0NBmk0NeJwACIm0hvzjyAFaUrUfln4wVRLggRONDSzmeMsH03GAFAMCjSh3lGzrlMuQXsl
izebFPwGhm8iF/tkyDkJY9YiKQb4Rjs04gUx9AsLboxTgyIlU2CgCnAnvEUbCQRdCDVha28YU5ai
oWiQKYXVnUxKIHexXCbBfnmArPJggNA68Z0sRPWCQBHurIaGocCQwRJc12iLCXZlTOQ0bUG4q29r
RcUiED4D8pD8piCAF4Zb/rJAF+ZJP7yHjZfxkmaD4whksFJ3rWMGwV5pigVVkAzdU60HM+MFhrzz
wZpqn+MdUQAjZpyz47XhfWVDY1ggQBe01+esYdeBmuHvKUd7P4c96mKvOQTcxTo++K+GqijsTjNw
Ue2HSut71i+RK1TtV5Ve3HkuBEC1AeCqw7XFK4Kki6RWomkecsG+Id5pZ86xpI1APKDPH4xeaDex
NVebd3BSSVwuE3p9mIiOG5JaXzve+94ITXsIiJzwmnNwrFNbEi+w1xr1gLvHhuFGclBj4PGavUDc
TFfBobPBi2oxK/Cus1dPbKHBVWGKAexgiIFkmp41hTFHbTxLJ6mVABSFeeU3j6XqyPInGMBsmIEQ
bQRiHNcBFujaEAs4sAvOsMAIB0nFRrPfGcuM3bZvbi7nFwKGyBRQCAXoIBwYPwg3ACANoBoBIcYv
IlOcW0EF/wBZyNBJRgKq7HLyw3inAKoolrajDT4wC5WCQIEsk1OJrNz8vm0B3jhvliQgFDpQC+jx
kDMRBONLNdeMUqJU05GJT1gDCaADzQxvet5WTjWGIjs3sUTsUxFYqiMe4l5w2W1atuzava+ebhfl
DaoMS1KDHWjxhM5NyHFQgkJZZnOEjMOhiVPOEmmNtV2iX73nEIBE2gWI7dsW7XzmpQgEW9IaG3Rr
b5yeiQaQnY827uNCiqAWAqrVALzA8YQVCjGAANVAAl4DGM/VVJ2tX75pwYJiIULBQNm9YjndZKVF
Etag7vB4zYgFT3UV8FQacw8Y1pheAjRVRobO8DA8afkjXEALkVNqIu973d4whHRgwk9LxuPWcTaQ
w1bG7e7bnGoAB+UHeHOIFkBAW1ho8YKKcArF6Gm72jLjjANBiqqwFVVQOQNBg3YvRNez/tZDo41r
xnr+8VwQdk03iZtKvd4PWKA+DEVqhfMD/OM0NHqtcHsSCqcidYvoahKpjdN84kkTtmUYb751iLYv
B0PjELQE57+M2L0/vNj8YlfnFYHXf/wV3cPJIeHGUfHHvKHGvOs2gBWwDvJqkCqm3Y2E3ZPeLo6M
gYAeFXQfnI0cba1HTSE205OcHFuOOGXsKifIiPxgX3gvM05K5uA4O+MTl39CmzkweevOI8OpPtjj
ZXgMGAo+v7xobON6MLVKPM1T7Yij15OYYz6DROT+tNw0V03fh9f7xYh0lu/H0kL54wFZkUeMFQlz
mkDguaCQGnp87zUBTi7q3s/xhUKiNPTgBQqAvA8gd7M0dC8U794YWHknCzZgtFGEZEJxMILYnWVs
mcPj3lZFYbvWRxWG2b484RSpWiTeKC0AbS0ZoxVKtXlySLd4jBxy+Mp7V6psLiAtAarhaiXqsLjq
M9I6yKKcDlEFEgffn1iQkAaLyEoBw95swQUoVYjhx4G0BVm6YAughUl71jsUEIX1pybKI3j7/jCt
ogXSoPD7zgC+T1f6wCIK8CbfeKqvTdNK8Yqtarmi3bNb4xVnQxXgzfACwyqWzdV4mNPkE2YCdVT+
HHThBO+vp+mAQP6jCE7judyYuoqCVi6KgQ4qhMtPDPDaLQaEE0XIkAkiCoytIit1ONYpANa2yJVV
URRgcGc7cxcs5tE6EWheIg6L2BAKkQdhrjTgayK0JACXQCteCOC4SARzgaCYUO3xmxjZBMwC7MNv
OucDUMKBoN1VOA2RWSSAhJtDo3kXBQQCoytIit1ONYP5FcDz9h+HDwNTnETDQtd6wKhiJi8JkwUa
YRFauDCju5/eS8AFor3na6DbH9YqHXjrEMrhevZib3SROEnGK6bRnzr/ALeO6fDm2Hi46OAeXNJw
OW6ySMVlefaHxlgCqwHyYFAQijXt31koSCtvHHxgUo5Xr/WFBEGgpXdc1dNbOvGO+gEijudH7zjt
WK711vEiJztf1khKDajK+MXqg70Q1iyKQ7fJgK2ReFmdH2443nc5wDaI4t1hCLm1/wA42q/HGKkt
rOOMKpvJN0LHsxUE2PPOOIbs8YyKkhJzz/kxtEULz+816TZ3y/yXF9IcTaL7/jK8xd0GudeDGDug
Ro3TT1mmTposA/nAEUK7O/C+cJ6joaPr1gEh3vAUBtXRhoJ2HAz84NHAFvAfY85EWHCO9n/ayAts
OxvnWvHeO2p98GepP7z4YnHvLr3lpzvNYVFrQkCUiREi/OVydZVSylYBAgGJisUC5EV00GmAgGEj
ktPbe994TRAA4A45T9YM6gCiEAbQDg6xhNuqndeXhT4UxAVLIM1COhdocuKBBRHBlBWgws5hi7Pa
lwRtF7TnGElLVUqpvVVX2rj07FgtNS6aGzFCjC7AaC336fzgLFagQEgB0AAHQGMEe+fnErvTNLNA
p9s1mhjzilNtxBHPG0ykoMxA4b5wvWCnxjqRON4KT3T3lLHPOIKO54yh3HXWX5X2azStGo9jnXI8
9k+cZFIK3WsOnYbg9X95wQaTSz5/9wAYpA64m9+NYQnqCa15Nf8AGQAijZKh49YqqjdRSnTloIbb
0P3+3WBFga3Kf4xlcPAozGSJtgovrEXWS71y4c9kdf3iUlDnjn3gaWpwDu4cBZ4x1svgTjBSUvN6
MCCk8n9YiYkkqYIW0ddOJdI+ZfziDxVfU1iBKWvGDDicnvELFQG5a94/wHdeDea1RTgdK/5yLsG2
KQ/7nF0gWgLD15+M0GBXaV8ffD9VTEBZ3z18ZZsIBVht5s7yQoJoB5vvCAJTTNHxkCgIG6hleynC
mn75Y84RUsvZ1m8JoBaN7+2EKbEHlfjIAlEnP58YiVpUuzHwn4wnpR/Dg3h4xJzjMq4ANpgJC5Jh
VwGzFbvnrKrxmk0XInnIpcmEAI1MPYcGqwvRiVgb7x0zWvpLd13nJdcQwQEgyfJjvi1cUudzz1kX
EKQPfGDYQa8HebEJYe8lg+W4ijk1cOpN8X+sK1ihJpfPvNLCuxnK9mADowqcVnMd85AjEZUse3wY
S7Akv2nFcjQl6JfxjDaCu0P4yvp3oT1y4ijYl8j7wnyOg7Ts77mbYTZVsPj5xeomI1X/AL+sChNK
z79YjyCtwsFLu5ZCqfrNiPGWjeOfeCgF2uh8Y+/ILfPx6w1FqeO/iYsECGpx/wAY1egWOuPzjSBF
G6O/AZUAqyyYsDbz15mCalTvgwK4bR7Ll8liELH4zwZAFUnejy/5y2xvtef9ZVvIzbNPVyqoRQLx
vjF6kK06mMV8Aui/04ghi7t1PO8EqW7u1ftgQATS76Mg4ANtkPnKqCJqtYesS0HeU0fbzlowD4uA
aIJwTA3Z+skd7R/nDXziO3AXExJg4vUMuDG+OMFR53nI+uPWNjPPjOSvPzl1PPrL4+1x23Eee/XW
bW4Bds8YGSbcnOfZs76+jg9dZAsaH2cVeVbkK9/GLY2t++GhAgjTA552o+XBEq7OPecp2/Gs4Qf1
hISRZIvznCAiIyA0b84kdW1vFdZqgoGLz1r/AKmWLYAV3w4VJRWvf3xRL2d8HvEiXa+PxiHsFSlJ
85Ma5LtIJqB9rggbLPsXnNgFgUTkOjffeC1RAEgPdmDAjXIAQgO15wkJL36cJanbuc4uoXzs1hpK
Va6msonGub/eagqA7P4+MFgtLRk/vEAaGV3q4IKxXWHY35Xnf94yBR20/GRGiPCZRGq1V/RmpbVr
OjivrWOuhAbwL0l8YuiqgjwJvjIIGkRN86+P9YLMQvOo5GwPVwCbi1UunCIlCHYT3y8P9Y6WhV0i
nQe8h804eR8fOBKbC2iV1EcqgwNK84YFJAHZN5YSJLqd4PaqoY3wPUzkdiAydOXDf95fp7XKcjto
E2nVETyI5S11bSF3C9TQ7cAsKmJFGUFom03iWOu1SeFBn2ykCXFpKu7goUZvGTZtQpCwWV3pyDdZ
TYprWC7kyqpK7fADXg1xzvIdk+m/wgONujBMhiNAKPzscAnz1e8U+jOp5zrIu6HrBIKkQ0VfwYrJ
VJUFd1ra7dYxQDc2+8VFG97xaB/7hodc8ZLgL+8RMFasKDQ0NIXfFy2G2qrCkE0spLpwCNAtKbT5
6DrA2ATZZB4+cfBFG8CEhvl2YJkG9A3N4nOqO6Pq4IsYnJp8a84thDDbQzz+c5FGcUsvvNGBDU82
8YhURKWi7ScZzDqMNRDxey4VAsKoktUIjp994AFgVdixtfvlC0V6R4cie92d+MGdQtXvNED2+8de
hEj24BpBvBm62YtUUAHcXMPeVd9iF7wkQm7OTIKGJGADZyxHCto23hfvgCbTh9/fGUDQGLocWvIK
TwYpKFsHlDEAQIQCCxQdshramEKU0ij+c3FXajTbOK9mmZNAIKas8ZNDAKIUyvgKvF1hFKtBuZ2X
kffOCQJR0KyfFxVRAByKJeHY7zgh6N7E807xrYACtpd37bxA0Dye/OGYNagbvle3AJAQ52TYeOMc
MgBYXt0GKvjjYzST7ZTddCXz84qcQFI0+2AfDiFuC/2w5w/8zrAeMgX65hFSFBYKFlm84i9TSDgn
QwmuQKcKOFAijpvf0QwQ1XsgNdi3neLTWnRi6bRbep1MjaNUaOV80Pw4hcUDkldtb43r5wzPwnaA
qOjSEQYZExQgJPEEEY+eXK6XowwUqnmMKV3lm5jkkuQaJjqnJ8YLHuhUD0hdDzozSKVRcBZsAGdf
fOkMTwMHwZbbYxOSlU8xQpXeKyTUY3sKxADinFWrkZKQN0woLo6qY1CkRSaF7g4qWPQEOxy1ZQul
ZiweGBqH8Fwa64ipRaGznXG3AxEQhLBE6SfdkJR5JEEjwEPtjdjVAROEi2a5F5yQG2AsUTSotqr7
zlmoIhRaoEKO2L1k+BgbWqk5GuRtraFAUedDXaBiPhWx1b4UgM4GYJJEoBTEGiKTvve8ZPTTAoRT
TuXoV1zm9psAqVA2qN9j3kSEBPex+RcChAhgEhTVUVCXQnGB2gCUIUCBu3MAdZEJAhqZSIPJRgDr
BiscKI1Cep9snR/AABwUYb35gcYjZLYEUADm1tu04mW8i0sokJyLSnOToAkVBNbi1edGA4QjCLVB
QUh0rlgiQ0hbxg1e07mRt+SWrEid2cVwkDq1GIkEHm628mGI5Q4SMRUYrya3HAUcOCoHW0AAOo3u
5JOrpQga4B+sVGKUqFUfkMkbZYoEGDVRiILZg9LpRSFo2iUYgc84RhCIpIOLetN4C65yBoEimDLZ
puJbuwgmARrShGglIOh6ub6kskTInBVrauBEEhpBT3DjEA3BQwECB7WwB1gZ0RJEKAugAiRE24cI
MsBNZqCSKNaecFiS0S4oDwet+MbTZLuQoRQ0gLa0842ZxYqIZeCKA7DWGWrOoA0JNAgo83mOJrPh
EAi/kb7w1IKgMQoC6A0gIm3KkKLTyiCigdLZcM4C2L4xFSRvCSlHA0PW8BBBqm099GcWoui5G7+T
O0E3W3f+MUgDGl+DD9b+H6a0TDnWcawnrABDFGiqK+DodYyjlMo7VeVfOVkuAhWoDxtX74o5BUou
kXlvdywY4h3nlN43gaoHygxxwmpAqqq8rd3nBbaVyHCV0+zAgoOLktI73vfe8mwVImIiAvCaneNG
rFbbEi8iGuNGsDC46BQYzkoMdUPGTISBuNio6VDZ4PGMqxGqPVWZpABXkcFWzDSaxLiInPCc4ScC
oAIAbGp0Q0msAlBpXBAYAKTdW4+NiCJRBF2UGeQcnbuglwCYT4zmqYYdaSJjSZpSltVN6q1navOc
xRJhBGlUjVeF1d4DEN/mgy9WYrbHZhYAs1fGTMkCBmw2kPjKVxqdDxtJ6kwJ4kOEQBGgCgHBrjGL
caK1VRXTVdTbeccTwvwRFLRoNN6wU64TCWngx3u7ypcIrtSgsTiofL5yAmjs2GiKjwI+zGXrney1
furjOsEwhwhYTqY5gFVh5UGb7844b6NJdNBm+5ziK5yjfKCC/PjImyrCKCqrthXlhXWOZuRkS8it
TWx5xETAEZRE5cIQdaNaMDFJY2ptRy0IhyC2TAO6qZCAwAcG6uajNJ0eGJcIgopoViLtK7by+cEt
NYI3BDo26PLjhJDbl4rWbc4XpQr2CX74kwEqWhQU4oKX25MRKSELFBilZeK4D7YY3xK6PRrH43S5
A4KtmDeIjbYoQ3OPtvFJtCFCqoDwKrDtXNjqCmPArMD1CtKFFFaihz4MIlwIRHAR0ItnN3iAuqoi
b0Ib785+1f3YCDliO8Wg5RFnvjEAgdhAm4TY1tusMLa/fNiV9u94warUrVXu/OMIJIJVbVbKy8Vn
OBwZDW5oDpHes2iHHfkCXxvNGoLDGCWcUFLLHLA03WecFnwOTziTqhoMP2h53iJ2aQGnBS8Td7vW
GUc6rh+p/eU7y9XOM5wkSpAAtepm0DtpEbDWo9Xi4N27xSlFB5ERBExPeP0JAtlZ2LVCJ2Yclx5Z
jEBkG7WLA54P2YwTrpkcgod+siq+9Yb3E1EwKgbfH0DW+zJwHO7jqJ34QpZUWoStPObX24oDb7Gj
FrkAOxUrxEPwcBy3XjrCweMROcQQKrxmyg0TxgkDVV18Y7lEUB4nxlMOOZ8uHsU7mrhQAD3d5sQa
c+8pDpdHAYippymaHNemYtHTzXxrE9bcPWRAabeUMS7e0dFpePxhRoLLoP8ALg4J904xBAEVDeDk
QVQLLIh+nAp1e55wL7PD6xfSc4kX0zHewXRla872zVwjd0nveWL0Nw7xmNqtDxOsY1tdTziqJOUv
WPXgheOcFsPP6wR0pd4IAWXrGJAZWvWsAhDrVwyKRpnczmoAKocHhPz/ADhJHelbyuNU0TVu09fb
FNAAiXt9fQ+W5CczCAbIvId4imonb24AAGjcTvBsOn842zkeTEBERplA0ha4V/rBRgH5jr5x9/RM
44xiSCpR/ACD9sWwxMBcciqF3/eX39wjVBJWna0ldzKYyEkFtCBFuKAbMkAieaQsNgDoVmPogEkB
aBAoQ8FyIVZhkSBJZF6t5jl+RlSoFZNoyppi8YCyL2FE0F5lepgYsMESQddCffG+HUIiTXOw8trX
NTVyogRtozYVKplnMlCgqEah0uhR6yIVCEqrSu0L0Dxlyx3eagHhIHeA+Pdk8oaDRAhqznCmJ/HY
gEE2EQZyPOQ1ABoVZrlFv4wiBUhQVZujCutBEwEzw5UOCUWAScN3YQjEYGgCZ6AvuZHJHkTCAjte
MG6bv/OPGC5Hx6T+8XWg2i865hy4K1jse/Z5xIfa7cEAD2FxKe1184jYXi+MMIjTduFwFlnkx0qp
SM3LmhQ5485ov/tl1WAsDdw45K2Dj1lDUXKxQcIQBFHEE0XYvDluw63W3I9sCBsDx7uOaOSnj2cm
BOkD3dYKItOt6w3VS7wDTDXFUJ4yga7eMXBSmzFsRFvBmo8moeMrugGqzjKbq99TFXfeCkykQAt8
A5FGXKun7GDwFO1y/bBXVyRKbTT+8SUgtrVQkIfzlUQCqbJ/Jjdy9ytZ7DFAAssRoZpvS8Hd/rBk
djZ0Ock08oaDLWIHW8GCBNzCBJfNwRYHvFors51zgL23fgwqAjhXFVHyf3ny539BfUxC3tPKSL8L
98nckuHQAwPWLWta5bzsa3vOKLh5iI27JIjp605vKOqIAuDSRqEEd14cBoBJARTA7VvE3yDVpQDH
FQK8sM5tSbMSCERIRNQj1gvSPgCqpFKqsKv2zQH0KJGF1RR81wTmRdKiDPMUvvOu7lJogsMEFIgs
h5KTXrNn3WKEGjVXnWLKciEtUXhXdPGILxur8KswhRqQfYqzCSaGmK2ruVl4rOcUojywd9pzgkMQ
VEQBtANAcGduoitdo6qu+NAHWLGsaPGqZY7BdGrjVsMk0/8AmMCAI2PM99d5FyC2efjKCa3e93F0
m8p1oPrLG0cXaKW3m5ugV79Yh5KATxkKI/vvDfUj0P8AeDye+c4Snpq5MGBYvjDpFFidYtMQ7C/j
N4KjQwDpb3lC0GoKnDWukeqes3HLVmnXAmE5h+Pn1hIeeGa/9wQPamA1pqWXWDG3YPMfxiKLR1U3
gFRBFMQ15FxVVU29mKoV0GpjBjY8zNAQsroPnJ2k5Ipz4/zgIhjLW/vNSIUCbd46kRNk2ab5xNkX
bET/AJxLBDtTT/vNMtQdeeK+8Q3GrPT/ALxCUII985bAF73zg16DLOJtaacgOEe+7iI3L4cTgpR5
7x5CrDaGSQ75+co3xir/ACZJ0afw/U94PxjP9/8A5iz2fxhq3SveUnvHWlEDWGzQIXnNA63l0IhN
7cUlYt4yIl3kgOU5Rzbo5efeSTYu19b+2APEmx5vrxmq4PGSgnHjxn5F49ZUs1nXv6MMGXTh2rQD
Z24FPfN6xopofrOWNhFvnGKBvWLqij+cBgzSXEGoFF6neVAg1ojOn7zNyxjV+S4BUQQ58H941EHR
uL+sSAuhm6eHNDRRu9J5/wC6wgCsoJUHuecFQXkn/GKQjm8bKKLpn6wDsESt5yrYjCD4yQA63cZQ
UQZg6UTtDNKCEapp6x06coB2p5wUppeFD9YoBRSCtLYD53jNpLqnL2/zhAd9A7ec5Aouju4bIhdl
HXvx85XZBpN/bFEbXeVKjLL9DWKVUts5pvKAN9twCtQE5lxUcH8rgDTavN5yNL25sdZ9rZ/D9J31
nH9Zt3Mcd8fQLnv6GPP1ecHeAI8OCBycb+cqHBHrL1/HeMOuOTFA8vnxlSzWVK8ZTDZeA3hW6Vu+
HK+lRJYq5aJfVxX3jrGffjEVft9sBp7zmy6xIx1g7x9ZsXWNaN+rkCa3vEjVRannBbRJhVV2vblG
rswJ8V3vKqIeVPZ34yhTtFd97/7eKRoiKeblJFSV1cAEhNb2ZZ0bt1xOdfjG3ypPM4P11gDMitde
cobAbRCBlRtHidecBStOtOKhOBKcYIkq9wLkw8hSFP13g1A4RIr2uWqGM5Hbz9sJI0hU2z1lKYLt
I0ZZIAO3+jBVF0acBcvTavnvAYKOlu9P+clwoGUs+3nGorrw3n1MYPfQ61v485294BNiKlySF9XE
mKalqYIQQQgPOJIRU5MUQZrZgAVZYh1iDwr0+DzjKwvvDfxP4cjhL6yLvOCb3mo92UC9r0GUEBIi
9mhrLS2raQu4XqaHbgHBVYRRCgtE2m8WdV0qTxQcJnswhzziyhupUBUFlfGPBKlOGMy6x3m9du9A
NeDXHO8Gf1lJMD6kBYK6P3g4gI2wKJfkcqk6N4xi7xkRLQ3Of5wVSIrgQWLHbIa5TKkOfGJ9oFeb
evjHsMC7ADXe0PjAOxbeELQ3HfvtyAU29q5cgQKi0KE54HeH8FatOqakKtfHOEBptNZ6eOMQ4aYb
84uvLeck5yo84FQm/WSpdmzAC2DnDRQEK7OMI8QftjNwvi7xPBRNSG+eMuQsKVhFnAQd3nWJq4wr
qV2EdE3XsxCeEDWq3a+sbAXYNGdgY/jznjek/WDCK2jlevjNgKE5dzCQBpWUN8zCARsqHI8HvLRJ
A0LtwiQQGwQ++VmuQqoCqSBBN3nWRK0a0CV1poyLlAhtNIj5/wC7xC0iYFACCqqED9ZJRMtV0Xzj
F2flyxE6848KPJY5GEVaJAaBdocYdU2ElYG7/wB/eIoW3x5xVWkWjp/sxTaJGcWf9rEDlysgA13t
OMdQ13tgEIc0c653jd+G+cVm69uLlWDS0KE54HeI4u7VJ4oM+2Nb48nTiIhHjnWBHeh05U+UnDxg
OfxP7y6wdOW9fSb70RFOEVCoDaawJBOvMlJ0qAp6NcUOKBijpHvLOLBlwuPZAa7FXnePhUmRi6bR
bbqdTI3mKXRyp6R+HEKCRUCU8tb43h4dnO0AUdGkIgwx9JWoJPUQRR88uV1vQjgpVPMYUrvJz1EQ
JDRsdU5PeCtYWCgPmRdDzozSsNxxBZsAGdffLDgZERYT0GAg6vIVmtiI1Ve7la+MjomgbsFYFdZO
rGiUoApxJtZN4hSiAagqJUi642+sfNTAVQANEhPRd7w04FAsVTx2a+MVxKpQhXTaEniEyBGo1qGo
EgkBgFB3ggIQCIicaFBzg9OgFCKMer0Lxzh0XEFljQQgLuF2mMLWKaTQVASvMDccCI7CyxVRF0qB
rgSzNC8SWqUBUJKMmtYgcp8Adx1ukwkKWkMUWqBCjti9YslbQwXZ2KlAonBhJlyEB6mjwDezGWJQ
CVLUIoiLtT1lTBbRKb5sAGda84+XPYEheHIA/fO8k4RkBICQRTbrbyZRyOqRBBLGlZYG45ejswkK
Fmh0ocw9mNWYABTEDiquJVHiQiBrVFtrXrhhethUFa2K30gesnR6orRR07DXaBjPgL3YKFgU69XE
SwgUmOiU0gOizVySGlxws1sAjVV4coCQw2Ai3hiI+8DndQVBJKUBFhLd2GOpdbZXAsCgaXje3F+6
G3CJQDV80Wd5UUdB0lWbbSu9B1gYgChPUmNI0OGtuKT8Dg9KNiAoxHjB9StpJwoWuroZpMHI6mQi
6bRaV1OpklCsCmKLYeZLd8ECMiNaUI0EpB0PVw0FxVCCU0+kcPUEh4UFCdmnJbCyKKF2Si0uTEFc
CEwkqBSe99YCsQoKwTEPMYesYiIFQdkm26ibBvjNMc8QIpVRbPK4qbUuQex0pyezJHy4QICMJSCx
WXeXQqylNg0DRqGzVDBC2QCCdOOFBxSiUeiBrsVed4/0bokLstFVQKJwYcvJdKc4kImnLGpfGApx
lh52P5yeM9ZuTFxTwVUROxOMjnXkRpFdb3rGwUTKO1XlfeXEcAhVUDoquLOQVKLpF5b3cpfUEMea
Gb71vFpBVA+UGY9fE1STavK93CRaVSXCV0nkwMmggclvy3vfeDIrkmIic8Jzl7VittiRfYa41hw6
MgUGM5KGnwYAcUCcTG+Do2eMRQCJX4VZmo8leRwVrPWQ5tGDOIma6wifyYJAI2Q441kUyUpQRc8p
p3sW5yO1AnevLVW6m984IdQTcY0fJqu8cVA6pXIo7HxxkSCYBRCANoBozZTLEu2wZzvGiv8A8Vf2
uPllRL0ljp6rPnKXQ6cmp7Gtc4ZhJHCmza0nWblbqst0rrp1gICI7Qsa7KWYyqbmCIgWRGTxrjJd
OjxPjaT1i55tNl55T9YxL64l5EiObBTTUbpXWzrELRVAERFaIg0mzNNhmmMqIsUVi8V84KcgAQWC
NgXg1kgnEYA2RKiPEdYqoFWGKwXaioAvMDwYRpnalTSS7hxbDiZLqWlBI1tbw133hIc12TYgWjFB
BTo1higLpNI8iJw+8XobaK9VZnECL32BUNaw0Sy4560sJ8axAQQRLaAw3umKAdQrUqFDdldTavLk
ytQXueFGx7wzQ0pEAhyq+xznBUXggu1OALLAODDWDICwqwBO1ZOV84tG4ZR4Yl75x0dlZpyHLewd
3ZcVGCgQHnQxvet4fb0QQqqB0KrDtXOGmFvwFZlwULKugAqq6Da3KOpiA80NTRRXLJWRQCiiDsUF
OKHjJFlrra27bXepvBmiB/JmNdrzvbkUFUZQIC2p4HiHgwshISF5FGozdcaRYUrSjNPFB+QyU3rO
xSK03vWAECJGHpVmGoaNAOkGJzziGQkRRdIvKJzecvX6gO82pv4zkETx4zQDghoyEQ1N5ZP3iFBN
n94Mb9LnwcZzj9O95fObHBsMvLvpY2BLV2vgF8DOWDbAsQGA8K6wyc4eUUqitAs5Cv8APjBgycEt
CiakBLvlNYLVXjSRWSTQ5tusUmjBB4p3nINMAAJgwb3vh8Y0EiO7M1E1y1OMlcMnRQCwsLc5RFyB
jKYYqCfrDly14HX4wZcuqMDnWOgN/PGMhSKdgo+4r4TNkpDiGcpYPvFspD55yVmcPHGcyQTfkxdw
WHF5PWNAr3vOw8dBg1opLLhENLRzss9zAVXF2XVPjw40saQVK+VeucS9CnAFGv8A28SSiLUss4rn
EVfBgCiNIT5wVgAdnnX7++AIJjzKQ69YDsVpnT4bjoqNlhId+T4wSTbTGa+cldjwczwYpegEQjXl
+2DShCQj/wC4gGRFDYj0e/nAC1kqqt14xYQi8DR8+XzkTsNWhqZQCCgDnEgmomDSiG0eMZcmgVh+
euMqgDS649/GMN1AUcHr1gGNaEtoYvQBNOucLICHFxU1aRk4HxgelDneVBXngucu64wbOHRj0SJz
MJQfbAHdibzWI1EKa+zkfqOWQnMI4KPOwZ2mCFLCSraoi6VJrgSzJntgLUoCoSUZNauIs+Mgdw8b
pMJClpDFFqgQo7YvWOMW+NC7LRVUFE4MVzBFQjmPDKXAcGOsgyvsBPGXTxc9dgAYu2zJULzAAIxn
Ow2qrxgzDTipER01NuVYprGPJaAJIeOgPtiJFhsiORaHnACSroIRpdKDyE41itOiIBAQN2IaF1iw
mMdpQyTQiA652jlrW1QhqRBKm4mIlphiIEkUQmwu3RMUmLjgoALFuVfUHLWDDPCVmx4C00FHEZPL
ZKgNAKEhF5VwSK1dBbVJSpDT3zj+oUDWkIhBEB1zuOCAQUmIQpoCrGO+coCUEAQMvYl9TBqAnFkR
HTU22qxTWCSnyUyJVVURRgcGA+6Lifwq/wAOdZyHd1OzK2KSTB39EYM+2afGSKLewzvbiKslWuph
ohuB4W+cspEarxzxrtxYoURrk8ucUYcyEPR6MHaSRNU6ubni5DhE/mY5YCuku/NwQ2CiVPzr8YEM
IWry/wDmARFXIQDGJXBAnB/7gUd8TKBJ42zBpWUWPnKEkdD2f5x2YdJZm9QL5GX11kBIDfm/GMKU
63s/POIFCBJ38Tx+MCvDLd39mcUoygccc5pAjre9ZRobIAKnesYwhog032ZfITjrluNC9rvWIBQC
6HvIgUXmYr8G8RBtD9Zy4H5ykDXi52FvzzvB8sk85sOw7Dzl+vzk/Mf39OvoFxmLhRETiJ3nmdOw
3StNx1h5YBiA2NdlLiiwsZBECyJqeNZ6nTqfG0nrFtJUhXnlMTGKo1WVDgsL5mP9VGVLB1VenXjO
eDJR21BcQWGRofSGcQWa68ZUDZI8AXRxo8ZxdO1BwF4DoNZ0NAuiEI2kACOjJACpBOIuzH4SLFmx
FWbDFkJkkKKlOFFpeMJeKFyedjd4KXQHCIUa7qL5hgKIojxPjaTKjCgHedDN94yIoaIxE8YkEq0/
BVnGFqiCoDQ29O8bvoISg05enI3/AKwTjSzXXjIVpLxJ4Fh+MERBO0DQe+1e1Xv6CNVDNIFw4l53
gi3d49YAkt7zr/eIGrjIS3vKGKBQ85JHdjXXf5xJDfian2zaoE7bT1zhr0qoO+TLVAilNJ38ZFGl
AgprWD2Od3lfjGYd9+u5nPXivGMt2pjed5b6jLg0E5dPOOTp6r1jojvowggN1znX3ykF4Yd043gq
4mtO+MLMliicnJj0zl7HhM2hDqyzjOETStdmRSNNuCGcE7bh5vWAF5NiuphQqkbeV9+8ig0PnvEu
I9854NJnO7judry/OAAE1BuURf8AGRYJH9YAdN1joAh37wEIInGWROXnP4n9519OvpL/AH/8OsNp
nsNnMxN+jF8d85yywHtxUn/XFU4jiglzvBwOVxyCheM6+kuHeTes4x+nH1C3cyTrnjJhTkcaG76+
k38j9ByiCyvGI2FEJ1c4AIQN15++TyZzJrAGw3te8F01UTyd/wDecJhUGFrzyeMBBScI7MC0lUW2
5V3JZ8zFqNGvvki1Ia94aRwH5cGiU236+MOTb4Zgtnc/rrHnHgxVDejjEAveIbRdfnEtKghyf8+c
VRSq8zR8YdiQKAauEek6HrBF6IJxfGHwDQC8kwsGBCgr/neMn4V4ho3jKig7TdzYPRrJnPPJgZJi
LtF2ZRzNfQQOVZt9YEz+Y/v631gZx8ZtcnvAfGMvzhrcuGx1OsFOsQPGBrITdxYh4z3/AHnJ4x5h
cQqFAmi84LIqLFr/AK+Pr33esC97xI6b8fUDvWO+MnnJkOPDMAmneb8z+8FCkbpveVw/bEYFZc3K
roC44Ag4O55/1iMgWuqrxgEb6sdrz7xcbIWiawjbRsI6M2qwU45xFdLqCzvRjjA64gSvGAcBvu5F
xTkFuEAR1abwyumzjDVSxhcFVEmhOPjDg2nWG6utzAw68J1lFQnq1MCFw9c4CqXVhuY74gZVpyZa
F5OJlM0s794wNvlqfOGCCBpUUcRRHgnBr1k0xF32nXvAKBSNWBON5eADQJYM4++UxOpN6PfnDwHj
WomThQU6u83Tc75H2xA7q2bx0jr3kzoRcIVi+PWI9ces2DrYfpyZI58Z/Wc02lP3wHt8YCkFyiWt
CM2dO4uUlpW0Bdwu5NDtwjiqYkUQoLRNpvF0VZKk8KDPtmzrF07zhLN6xA27uCoWCyu9OIgKiThR
msszZN4xfADXg1xzvPRv4yp4xC1Jsm1mGCiOiiOzwji0dee+3Au8HZC206pqdrU65xrUDDm2b5zn
rX+MChEVCvy8YjyAw7AZxIP3rHSyE4G4SU54xdr6x2ozKu7b3hTAq+C42BC8CxnmZwiY7mvy84Cn
BNFOQjwxQuvF85sYCArkm5xsdYRAO0J5+cM2o7IvaKD+QxqBdRjpPaYliEiVP/MQmwJAip1fLiqk
5BAVfwcZJKE4pp+cc4KFXywv3yDAUjQRRj8mDqd2OQhZfHbhCam+eDCHD5cEOE/zkIAK6ZyYOpM4
DXlg6OXnWErcFlQFTUiCNvrGE0FEvdibCbqcmXVslKm7CFCbslOcA3ROGiCBqgZrvxhTSsmveWfO
VlpXne83JbCxsGDV2vgF8UulQs0l0KBaaVD3jRsD4LfjENGI1J0U64ddZ2CQAOdecFAR205+BxtA
o3uMvOBNfxm/n+8GJ1utPeaRK7VKHtO8YULQFYJPHz3jTQ9FOAnl2T/rhaQt3P1lreGahlf85/E/
hwcc2a+jk6M2LEB8uw9uM1HTBQ0WqDfO4458YBFGoj36waLgyQVHsANXYq87xeB06MXTaLbdTqYt
0gpdGLPSP3wgqjjgSnlrfG8FBs5+gCjo0hEGGPozIET0aEUfPeW8/SjkpVPMYUrv6fQBZMNEx1S0
94DP+hUATwXQ86M1qDecQGbABnX3zdqIEgQB6mXQSJIySaFauhU4DAHApleSgqKK86NzBpwQahYZ
sNa6r5zk4UgJoXuXNEYHkKzWxEaqvDZhyHvG07LRUoKJwYMEag2m4/cM0QqZrvLNXV+DCrfcFJCg
GBRpQ7xXPbeljQFJbFdzeUniOIWF0iioS6HrHXnwbpEuwvMlu+CD89BhLyCEODWj7oSFrUBKHjep
kZpjhQVabaE3qfNMQETBEjQESccG5DBfWHUcoNBKQdD1cUJEEgGg12LedvUyooASijXjmB+MUoXi
BgOpoAAem93E2DdJi3jBq9p3MShkwIghxsR1HxgKsKghQdaC+vnDSRAABgQ1Qt538Yq9QBKhqs5G
4rIEQqI6GgHgjZu5rE4soGEPRU+MZiWgCiQ+B34xE9UALhJ0g/j5yKQlAtUdKi7KzvG3VEZR6CNT
k1yY3I6iqgWiAxbtT1ks60EtGpsgadDNbmRYlCU2BVKIkIhrpBWKY+AFRI0hIaMZcALQZBrVm08B
3ghOfY3FDhSk1txSIpG0WJ9wxWYcjVGprtVwbJbRgsy0VVAonBiRPhUCGED25gDrDYalNijHhnrB
FH1osr8A+t5bMJiQQp2IOjakpbjJAQtFAFkQlDXGnGDHU1rEOYR4ptU4c2OgW0QAoQKoFol4MLCY
QAAUJDloUzVEajvFSFeeTDgq+nEJJpWU7e8HpVthFmgfvftiqlVnKwPR4MOSQSlLcG7Dd6MUwUiD
ZfnJlF204nObzgaoO8P1P7+h/GXNvvFLIFERON9Yxl6gfFXXBx4xOFKZR2q8r7ywnwEKqgPBVYe8
RMFUkUiK1E5vOWImAHeaGb784osaoHlBly9OFbKq3m93BASUkuErpPJhMGEjktPbe997w4CuSsRE
54TTiwrrXtsSPfCEONHjDg6OgUGM5KGvR4wApoEUbFfBobPBiRAxqj1VmOkYClw427xTG1gF5bWt
5tw2Gx3CNNqunZ4xByItmVBF5Kp4r5cNQMhEEYitKDPJeTJe3jBnETAOvGAdnUB13anb1vG8mIIH
kRNiTNwlGOaAVXlALzA8YU2yiQABbUANeA1iTFzVfJVXR3jbBJ8TwGD48dZdgoYwKVQWgq2I7Xlu
GfkDNCkSEFKV4AmAYIqQJECwIyTjXGaPXuaAQbQ4Q0GuMnYhgLglnFmrzM4LRUdCCw14ybkKkikR
eUTm84zdlIu8oWHzlP2mqGbBjr9ZxC2J8oa/fAMha0oI153W73jUIK6oyoLBYV7mKciRlFIi2onI
84Zk4P5BpETS/nBDSUBN5WJX24tYWMDHYCEhhJVsikvDisCHKF0ocCznBRUJIBwCZr4wdKa1QgD6
8JkPMEINkVp51nI2KHhwqzjrJytu0vJXT7w0cliXCV0+87symgsqx2sK9w8YXppVaLHbaVi+XOSF
KjRY07SsvFwGAkkFijfYGcaPGLKCpCvNqbxyNWgbzo1vHJCVFV5hwWFnMyWZWdWwdVeevGBZIRrA
QiIjjRu61rRDvwp8KcZcJ9i6BoIK8YFFoIEa2CXWrjOpFsII8fONO9c56b+e8tRo51a3IUggOIMi
AL3D3grUT94TmgE07ywZQV8jNDZR0wI/91nAQCvGu8D4A8CZ+m/hzT3jrX06Zx9GkbZoSIIO1AYA
JXKH4lCn2xdB0aUgBB2oA1ng7MM2IflWB+XJNUzaUUZOeMe/eBs6xp8YgEaTsFH3FfCY70b9/Qfp
8Yd6KjesqNi9jdf1iiDip7xgIFrzp9YW6xn571kiG7+A6xBoR23TziXAY62mu/OWWEFY6PtnLSoS
qEwNAi7RtD+MNG0A6JTHoX7K5z7nxr+Mqyq3vOHf3xii6l8zJRVZdYS+TOePOCLjGq+9bmcSKla6
Z0ZCSougMtcnKuzEiQOHOnNycBpm/viefPrNreUc+HOm7dy2YAK0BJiro175y6oHrGCjZ5duHO/3
jIqQKt6xQL1LMJd8XLQXArigij+ssAFXbvxjUIBK3vApKd6wngRWdL/0xeA3OKPxkHQisR2/OWja
bQs9ess3htVTT67cawV7e8quAYFq6xbbfR4z1dXIGvWHnL58YEqh884Bzut35zeJDmM1eMOzb04f
sP7xyY4GCzRKiyE7B2nYTKyhoU0SBpx8DZilA4AxEGMtKHNPGM+P7RFQqWpThaTUUmj4qRWTaArw
xeMcSK0AkGlRRF3OMB4lMEgUOQ2G3XjGYYGgqhIIQ0aVTccO+hmdLldoXh3yuASu0aIr87p9LEJu
XeVCP3/Acq5zjOsTNXtwXPfW877MIkZON8ZrCB5MBQS8obTIAATswGtfCYKik+MoFIcZuLb77xA6
vwdZpAu9zxnHWRa4nLbYe8jd9OeMRIR53zlGF4yAyL+skS6+/WPMCfe5LkJrBpSDR3vx8uIYDZRJ
gGhda78c5KUNLRf44xBUCE1i6VPHrEcF3z7wQ0DtruZujXuYPYH5x5ujfHjOYlNYzdB5l5wAyH+c
YkKwLO81gkulffWAw0fHvCCzzvGlsgayEiciBrEEVsrJt8fGFWioocz+cewc3pr8Yqh36G3AQEao
9+MVWHPOPA9de8HJBPjN2mu9dZaD45cSDj5wByi9+MpIT1ecAYK5yTdN5rKAkafw4ee82/b6qcOq
I8ibMEkCokilTeqafWs4kMW/IEuKlsstbAFnFgb5yYOJCkIF5kA54Jmlrt+sna8a5x1Wq7heVjt9
4otFmjQBZxYBedYlSy0gyi5TRpx6Qw0QKQAYAa0HdcERBO0DQXvtXtV7ya51jPoHXGrgauvPOV8u
IQ11cpL5eMuQp1iA72fGccecHgmvnEnHFmIu0PkwHPLd48q61j2HxieJbkzgPeAAIX+fpW3wXIih
vmvWRnhc0R653jKypSBdefH5wI7SkZ3/ABiOsgAFUOOXneaOEvZRcR8hEWSeveJCTjcbu4a53mrx
304i6Gu64czquEhovm7z5J89Y8YHiOUj0n8YC6MKKVPOQWh94QkMuBShW3nGoPTYeMaazccoibsM
UJAWAN3/ADgawpuwnr75MABAYeTb9nBRETZ8j/hwg9KJ41N4EElTEEt2t+DHrd++Jduz11ggg338
YwIPBvebXa4CadI8Oa4BZgtrd8+8dsW05EP5+jOvr1hi9GT636vxk1ctz2XFLinjZ7wQTHbrvHxx
4rzjx84dfSCuE7riT5ypzguPOBe87Tk895zCzGU1esDo32E84ce1zq7twWh4uKXTTGn44XNSKxAZ
ziGgQERuvT/WFsHCtNLvvyYgJoXRN68dOUoXahctDdFhiRi48E/WcPm6cHIqnWVoAJ+800WfxiQg
7nn+Mauj7GIOFV4xbob/AIzeD98WatNTXWWUNYwbseA198d08mWjSgmpkkqqGVo/vFFmGjgfnDU2
oqadca+c4AZdKu3XrEjYRU7HiYQUdyfbAHgWc4p1HkxGEecHf3g7DEuABrfPOL0/fWbO9ecdALo4
1mnjA/Mfw/8AwcYmCHWO+MmJq/8A0qkmBgPn740bxldYTv8AORT0Z185tJHEeJvA33xm0s4zrDSw
uReKveKOdYmGt5rlG42Xzg3WawG64dYO33gRsr4uEiPPI4U3KPrOuNuXkUjVj85SAOUVZllBFYLp
9YjVjii6uIUGcbmsJdHWy6zbg7wB3Y5QIub3Qr14wNVTziBTXNxoNn+Mg3tdifu5G13xgHImHD5z
hxL+MZCW8rk1p13zmyBWG/WHmciOnGQgPv3kPYardmE4H3yuRHaLd4jaPCP/AHWUCFM9yr7yWwp1
caykwOh1eLgiTWnVcEKcjxi6nBfoyOFecs6MP1P7xcDO85xmxHYGF2g/xmtOu6YrpDQS/J5y1NK2
kLuF6mh24CwqYkUQoLRNpvG/Fdqk8UGfb6GHO8eYN1KoWCyvRjqhUpwprPkuO03Lt3oBrwa453l5
8Z1zzm2Y2zldGHMDG2Bjv5MiGuPOcPnLvWrgo6W+cu2zeBKV6hAq75YY8iFJoKrSDVwupjz8G984
UBcbIANd7TD+THRRAQa0ePnLX55+iAvfjIm8YOAvnH+TENJfD3i7zWt3GXQHQgCgKiMFneCDxTKs
F35zvPlXvLOSAwrdiRCb2cmLY1qc+sElDXnClugNvvBju5sXV1igzgf1nL6uGKPMo3rJUPu4Sofj
BNxbkUIMg7o5hzvAS3UPiYGkBLOlSCaWU26mBXRreaibGjcGKyzvCMAB8rhBo4894QgiAvbo31h6
gQjQREvZRxlh7pU+lBn2wLegLhsICoC/LhAmV49ZWunjDbgWlj3cpVZMhtee8idU78ZAterTGuSv
nOVmjJdqHx9D9T+/pXzhw/Ql1cB5VhkkEIRUXi7V/ZDrHGCgoo5G7E8ZsZgwQTXsgNdi3neLTWnR
i6bRbep1MjeYUujlnpH4cQFGFwJXbW+MNzu52gKjo0hEGGTgBsCTEGhFHzy7y/N6MclKp5ihSu8H
6GTYViDRMaUWnvAIW4VEfULoedGaVhuOILNgAzr74BpcEgYPiZcW9GOClU8xhSu8Ugqg3uwrEAOK
cVa3BhTAW1CgujgqY3CkciaF7lxcsYgIdjlqyhdKzHY8MDUK+RbhUKpypRaGznXG3LQawL4WoAUh
tVdJgPFRAgoA7FPGGPbI7jUGinJp2GO/B4iQkYSEFisu8LNSSlm1GpfCFSlMeyKnbBwS8IDosJct
G+jHJSqeYwpXeITRyUIEV+ER94wWAJAhhA3a2AOsfBEIZDCsACICPLmgC1DTkSKcaUXCFhXQRDR1
RSHIXrE5iOzVd/KrmgC5kYum0W1dTqZv8wpdHK/CP3wlQrF2UKMtNm9QStEHJGNhamWcTUmIETlE
2Na84ZwBwySulXiPUPeQUTh0h0NAAHpvdyPeRCpdPBWU2BKVy116McFKp5jCld5EExtkFdKvEeoT
CXISAQF5sAEWA3u5J99PIbETaAUjdmQDXTULRIFMLqzkmaEGAFY0eKAp/eVMzJAGJjpBvRQGbrbv
sZsYSlSioS6E4y143UCBAnZrNClEmhLNU2HxxrB2IYAVCwOKq4SLWzQECcFWvK78ZtqoA0AHylh9
sFQwFAiwXW2G9XzxhPkBPIgUUDSCQYYgwC0QIA9BhmQRgKO80jva3V6xxj3hoXZaKqgonBggD7hN
x+4ZTGHe2uFNXVQuudtRR8ZA7rxu6xRjXxoXZaKqgonBgqChCKCjzsNdustmdSJSDCgCnBrzmvHA
QawIb+WryrjQRvjkly6Hh3gwnNxPEoby6Ca5yJwYfqf39OPpPGJwYURE4R84o2jvTku3Nu7ziLGJ
qjtV5V8uI5YgQrUB4qrrF3ItBFIi5R7vOUTFAO80s3iWxqgeUGZavC0qqt5vdw0WlUlwldPswQgj
I5LdO9733k4KhIiInPCc4ratC22JF9hrjR4w4GR0NgxnJQZxo8YEM0QuNipvSobPWKkTuqPVWZoT
JXkcFawwQCvYRETnhNOQwU0gEAbgk6IamsogHVUEJhANG6uIVoIMQRDbxQfneQGPQCcRMJ8Ze7tM
KRiRNYoK2pVtVS8VV12rirEAYTyw7XtecgAgQAgCRqQNcYiRilpKMYmqD9jPkcVIEVpvesGMESse
lWZwa6l6UFQ1rJBqEkERCvCacdgUSTmgMN7y9uKgvOhnzn7GJcgIOc9fm4xxvVIQVDFUNCpIABX0
AZZf8ArzQZvvW8XoFUDygxxyIUx0XBQvKBXlhcn2YTQIsU4UrLxvFjSNBQUoooVZXnEEJgKIQBtA
NAcGs4/Sar2CXxm+wILQgEHFQC/HjAwNCSCIm3RNPrCGoq8QgDaAaAdGX4E9cmwQcUl2NEeGJcTS
ACWsDbcWg1F58uGwsljj1RGYFQ1TBSiWpo0+DxigjE2pwgMJ1MBJJSMRUG9DWhzW84hZp2hEY4sA
vgxo2baqeV26xbIq0oUUVqKDu8GNBFrKKWrDpXepvKieVsCx28lY9V84LulIq8ldPvNAZC6RwVVh
itLqYW1FR3vGtLUgrzym/jFbCKoo4ROMshy1QKAVXlAL4Dxljb4wRECyTU8axbSVKV55TfxjREFE
Txs7xx8iwAiKWjQad4ypVWqtVxVhwY/e4Tvn3i8H5xb3HIeGH7j+H685HAQEVEBe16O3NH6T8agf
yGH9hKtNyEjyu/HOVy5PxjZu1IBUeilfKBdxGZRUYChmlEl4eshZuPRUBfVcNGwFwoXmXchramPs
TJ98P3gzoc3xgOUUoFUqhZOeDn2ecAxuC4G8Jhh8rA9uDO/s5ResbzGYMzXA/wCss714x3WbLUn8
5Q6uVbbfjjFTw3xijxzkPeEkrfWQIDy7+MWr7yoBh3Mn4OMbBOTHwTyb4xcjrU44cVIpz5crTQLg
E06fxgiu/BiIHj+MjWpxfnK+f1it6T7XD4VOcjS1fDl6A95DNaOrzjbFEGuNVPO3BZvNtiAS+chz
X5coUuh0dZvnzm+ct7wfKzvNApW95p4Icf7xJ2JgrqX75V1dYq6SHoxOeI4tHzda6xEa4JPL8Y9u
w8azsrhtnycfDifSa+lWJZ9rafow2fQC8EqBsQ2qukzSIBAG1zUAVzWx/UImiEsBCi884nGNREOx
y1ZQulZhqMpoU7PJ7MfdrEWUY1Vd8g71nAEuoQU6KfiYWRqCIUQzmFbWrxgAFhiRD7GkqQ8m1Vjd
IBMhqCHY7KXQKcN3YQs8IykLowRsNuujJxAow4hJQhxpbzMLnbNURVSgNhXZAybqYmBBSVKoFg7N
txjCMiGPB5Sd3G4pZFTP4gfmYFEjWzCcTaAtbxONZEI4AISChwI+hwQUEQ8V/wDgY3IZOJgws35x
39brCc4FMnTi7Dv+skj5xhoMhZMb6Dtxnmx77MVb2/r6JHp+MsLs8Zsj0msDZuujFVr9BThcuuo9
eHDccO5iRpDFwSJgSLw4zgbjlI8JrWdHPtx3rnHWrvvAvGPL3kMq7wWGc8bxbk71go6xfXPHrBQH
CL6xOys85sWTDk+cjn8x/Dg5Mv0X29UR5E2OePOthNgx8YaQQCyASq7lZ4yKcoQTjSzXXjJQnFBn
Eqa+MMIJg0VgvBt0awYsvCYM8WAvPO94ybRFCllOGVnzhcWk9waiyaNejCUSGiFlOGVniuQusLEJ
SEUUFVBeXeBAJBUQgDaAaJnBfaH5AlxctFlJoAs4sAXnEBZCRREl4TUxY1JWoukW1Hu85HDTkeQX
Tzsw4S0JHgK6TpNmHAmUYyxTt2y+cvoYFsOSeLot0UDbiM+hu9YC3uZXe8G6l8b4xd8fB1lSanxg
L9W3feE0PnKeHP4eXxkeFCZfL9sNtE3gpDf3xr/P0BbDOHeCNQROzFfS09YwmfGbPBPxm0VJceX5
z/DDgE4xG50bcnset3bnPaj2+esF6Gn3yGqVmh4zkIJ+8EHPzgKJ/OXJH7YGylBn3xa7ieMBQ3XH
oxpX8es2gwY7n0N4FgvHGIFbr1kDY/nDbt/OTv7ffPvy35j+H696zjLl8fUNY6+v7mWFcW/OGPG+
cNPZ5zn4esu/GPu67y+sXL7y0lv044D7zi4BIsc0hG4HvEpRszf0CuNu84e/oO8XW+sPEq5YTu5E
803vOUD1iK3hBDd5wq3nzkQCzxjU7EcBBWXFoh/vAhV+2MQe+8Zb4wgjudZE0fbFBIz1vH8B/WDy
t0b2N+cGvAq8uO24zxrFHU166ym6zi+MSOCE8dx7wAtQ8YBsRwZZ4z5ySr3jJpfGdNT1hLXjKHPJ
1cUe19YhySeM5cc8esWdfv6H6n9/TrBy/WZLxg5MDEnnA7uUk85MCY1c198qNNY9cTNS6zX2y5R6
wZjLXI5P5zgbk1zvJTufSPWBDZnfnKf+YuU+/wBFJPP6x30w7b7y7sy3EWsXykym9fGadTzj584F
IVOc5b5w5Jzj7RfJg3e/GLrsnjFVcgaF95IdDznAXfxxihKAO/nEWT4md8ZbqbXEmnh6yJEvgDJW
69jhAA/9yU3bglhiR3T5MJ6b5xjRNecAdtfnNN+DGu8U6Pzi3OLiHXCYwlPeacYwIU1+cm89Z1nz
gNWwKAaqq8AFfjBcklwJVUEY3iJw5YTl4kXcL1NDyYB4VMSKMoLRNpvEGVdrR4oP6znn6bT4xRg3
UFAWCyvRjohUpxRn02TYu3wA14Ncc7zjjlzmZFZEB1t0Yc4ETgRE97HK7viVPpQe/GJNZxm9FdqW
XgUdQeZi694CV4wtxpLTqmuCrU5Oc3gjLwYuDrEmWweELTmO/wCc2fj60IuE1RQAdxcw9/Q54sxa
TW8pJMAxYswUBoqqgAYePcxgYY1NTtWGBwACNAMT8jiJ6xEhVXQgNDcd9XzhDvC2WKkE1ZTnSYB8
mNGH6xKcsNVayCLs37yQpeOc3HAAuldGRjDMbAognOzDMO5RfYKFPtmlndpziFp8hm9pkCZ1kFB6
OsWYAEKlEKE5kHeaViSi+4UKfbNDRV89ZsFRVQQWUHbIe0xZuAdXvFOKtfjEJzU1XqEtej5xtm6c
zFRda9Z0EJ47wlEBVpuTU7XeL8vb/GA9jhSiS1QicJ57wlEpzjHS/wCMZ1xjQa2/rJUOdZBNYhq4
p/DnHf1nlxwgDHapomhNnC4jSEZRV5KAlkSB2o4YUUciPfr6IYIhj2QGuxbzvFovTIxdNott1Opm
9yFLo5Z6R++FGiRaBK7a3xvDcbOdoAo6NIRBhk/HYAk9BBFHzy4OvejHBSqeYwpXebc8qgJEhomO
qWnswCbtCoHpC6HnRmtQbjiAzYAM6++MkplsCA/GM8VIZamkBm1TgDCKIabgCGhAM8sQCgCO+Y9i
/gxHgQAwrdboAnjI9GbgiFsCJDXBgVARrahGglIOh6uWLxUIUIEYgy9C5L+fclyQNsDZUreQlglA
FL3GP9Y54B+gIBBCoAM7mBtVluGhAQCjrR3hAEV3DIqClb5SzeU1dcKhT3Kzc94DQHTsAAOo3u5I
lsVQQ9A/WG+VwEKhFGMZehfnHCPIKQQIvO02C0y6xAVTE5sABwjZu4DZMcgCJjEuncnWTAngBmk0
o7Oq4BYMKKTAeUSPHPWP0o/qCcNBIL5TrHrTmCOEONGuDrJOoLu2aaqG9DzvLMs1EQnDtBvuDjuG
3iEK6VQgeITKXC4SIOR2awBkBmQks1TYfHGsULEgAgUHHLcZ1KAiaUEjtu7vFXe7UQiiKCoeZdYo
/hhVABezKu7xjRMRSBAHoMFIYWlFEkexibBvjGlUSQA09obTzch2oAxh4SnK1rzjGA9KQEV60iPv
HjhVuQXFYAaQEeXJGIlAIBmoJAUa6ecIlOcQADsTNOyTBWQ4WleCoFOL7yBqBKoCRKA1NwcOgH4q
EL3Kjg0AairDRNkuuNvrEgErqB0MQqdp3MlEjgBvANEcs2yCiooJFrd3eOWoZkoBGCFYLtg85bij
KU2DQIjUNmqGKYjkpC1ig1TtO5mhhdhg+lBbUulTXGX5vQjgpVPMYUrvEtIQAVEJKLT2Y7ZOxhIJ
KgUnvfWAVhwoayuLDjwZoLZ97g060OC7+M35x/cfw/SfT1jx2FER6j5xQD1IfOldN3rH0cTVHaq7
X3ljPAIVqA8bVxZyCpRdIvKJzcun6Id5oZvvzjeRqgeUGOPXg1sq283u4aLSqS4Suk8mAqYbMlpT
uO997w4CuSkRE54TTlx7wttiRfYa416w4HT0CwxnJQY+DxhCmgBbs2eHRs8GcgiCvwqzNAJK8jgr
WGagTFPlRr982wpWgAFUXaqEXzirGncqtX85ppGQiRhYUUfNcL98HSgQZ5ilzjDxT8BWYwqKFa0s
dJZWfL5x+zz4DteNc5PJ6MJEhW7NPk1j+YxKx7iXCJJBAHFWz1lu8AloMVqUNPg8Y2qldKMsOCws
51nC/an5A7xJ6RdKAgzixS87x4DLupE3v2OMqRL02GKuygx8HjOL7lPyBLh6ZiVj3EuKlr5H2vy2
Du7LiGBqCPImzN6JBygiVbIpONuDIJFjYCDOLF37wRIGP2VtZ6xfz1FHtduAmEQVEIA2gGoYRfwC
JqDehrQ5recsVGjSIizzAL6zn94yPtdujBwJJAKHS9gZxoyuVSjFPLDqws5mD5YAAGha8g6zQ2Qu
cOCqsPGH17WPlbX74go6sjyrtwPn9VgobCbcddXFUJGk5oDBu/nP2/C9AY4VxCBflEr7zm8sAfEc
8vONebSnebVb7codcxRRiWpQ0+DxkeHUQ1SI6ppnOWswIamy/DauptuVaUtyPNRAu7zVt6ByQE0E
Cu2AV7d4bAJIBQ6XsDONHjCjqojiRUdKhs9YDQIkYeqsxdeY1adWJco7EFoi78kV2+XAAVwViIhX
hNJ4xZTxW2xIt7EIcaPGAkDnD2t+G9673jYs3bslFixd87cRw1N77w1TNRbci9OfzH8P06+pAFGA
G3N0WBEI2HdR6vFwTKHSlKKDyIiCJ9OMaQKlgKkkKjJeMMSYIZP7asKgECqroDpzv1ieMnnH5+cC
JMuBVWC+tC1MQ6gLQDyUGPsy+s9//J95eGmFE0xD0OD56xbg1bgm/wCMZnT+ssL3jzgce8SdzEmD
k18d5foGSHOG/jAEr3lTVp1l1gQvnE784+GPZftnLzo3rJ4x1vZ8Y67D6eXAoV27ygbt/WOk4eb5
xWkXBh6ecY7OzBDU31iXEpHEdluUDyYTyX33kH1ibZxwYVbpuplV1ML1cOzr4xgWvreIjvKh851S
j/OLJv8AeH6n951l1nX0YgRRKP4AQfti2GJAXHIqhd/3hEFNa3F6tDk70u84iUOKog9l+1cvEsAV
ZKEGzArToy6Q05IQoS1N7By5oyWvYBVKuo8o05ysaAIlI+QUPnFOIAKmKI0AE4NrzkmSBK0hrh/A
Gad1lRACjGyPSjzM1tlJYTMigWJUluM0GNVEkkgDgAK83OKwTgAZGCKw5E6Jk4gLCIpCUmztcB9B
CkEU4YVHTN4J1PkVRGFAESAe7i1RI0Biu9qBt3gwmohYgKiA3Fol0GDXf73IC1BAUKPISDTAC6gi
4SNuVYprCcyFtcFEohsKlIGBX7XlWJ94/LjjOMkacY1YujnGcBMO/jLrjjPvlHGT636g9ZL8YE5M
gqI4Y4iROP3jtrh6yV3wZHBnLfDhTSo9OFtec3NczWRNo6fziqq85NHy4pA8ZHBl+Mmzs8414ieE
4yumesKEd4r9mKkh/nDTtTJS9GgyBh/5ilYuK9ms0bHWKI73hqPY8ZbiQPeKoHjE4xJ8L+/rt1nx
iFdaaUkX4XJbJLh0AMD1gKqQkHmo1x9ltK7bXq7nFwEV6c67B3rWcLRifKjX74LKA1sLHbaVi+Xz
hwcN5hWF4KujzlDIyluaDN4vGldKMsOrC+ZiYP8AqUtyQAnLhIBK6wsa5SsXy+crZOUtzQY395xp
2h+US4I3TXmRLOLFL7xkNCaELFOGVl4rlUIwDvNDN9+cfCIJiHFOGVlzhMpL8gS5UtFmjQBZxUAv
PGSUbCM4gs114w4RYTAiJLwmp4xFAiQZ2O4NXbWeDOtP6yr26yk42cmcScZxmwbyHRjtxib05F55
xBu3Xc/WCHrmbwTr7zNucj18c49DxlHjDgxeP17zX0QFbM4Ees9d/SNz4MRxcTWzXvB5t8znOQXJ
329piWWfbNjePD3iiTjvEfP3w2rgV07yxiOUaF3iuyY5HBkTl5zVd+MdFPOfzhOmO29e/ObIKa++
IGz95t4w/U/vNOX6X/5l4w1i4OVfoXrHYfzl+2a6v0H75d4cXWXxhO7g9SmWPnvCrcFOM42eMWpN
u75xpoL3i0gbefWaKXWKBzlvc7vjLOCfzl8L+cGc7MvhA/eUu3XGL31lBL9B+86cfXXnF2TH1gzL
a++K68ZN739UmuA2vn1i9cHjvHwfucOoH3gAp+TO53rOPBjTTT5wSbt+cndvnzgchv35w+8it9Y4
M5xVa5LpMfH8YKNHeV0SZFad5/jNJF/OD73lAXU51g3wuN8HD9T+/wD8Ej3hJft9HO/pb7zzhzvH
f/yVxJnJrr6lPoupvjxiuaLi4T7Zuf4wjbjLZruZznt3gVyT2dzFXXHnFvx9OftgzHTSbLmwpLxv
HXy5Q5E1d4RI6HNGOMjoXV0Ybvc1k1DLz4N/4+nBxaaxOwfObCOx8Yang3lbdZJj5CYMb4xb0d5o
7PnGOExXlrHnDNTVXyGafObo7x5v8fUL3m56cNO+sVVx/Z/Bx+oY7wK0AAqq6ABV8GA5AKQMVUEY
js31lZaVtAXcL1NDzgFhUxIoygtE2m8RTVUtHigz7Zs7zT9840/fHXDdSqFgsr0YiIVknkceLmyb
l28ANeDXHO/rtvAB8rDD1ARGwKP7M6znJGcmQmoX6GAT1kgYiN0EOheUPBaoC43Q9hNgOQXaGvkp
vHiVA1ghaG4lw0QF2oqQTSynOkxahIoDFKgu5DXKZVCqmQNKoQJE6e8EySFUUlagKgLfWPsAqhQF
m5Xxj5YKBbAV4k2TeHR6zgnF2GbXvF09axeHVF4ApUkI3d2lBcUfapWkahEF1viXOk1XWFGgKgL8
uV2cFAqVAdNB2up3gYU38YVgMvOLohAqgjtNNXF1M5JIOz5zQejw7uVJZ6sxyvVdIUGhpsQ784vC
nWhERQdxTXMzTzvOXWTHJDEFA0YkUzgPOsU8JBVBFbrkeLnIc73juDtp7wAVcofcKFPtgEVeMA0S
WyItgvAzXOVdDAwU+MQTX2xk/jCurnHLc2nJg0FhoQQNd7TC5CSyUWtaThPOSnvJeLP4+jQPok+Q
/hz7fUcE+jJYKPYVDtJ3g3dYocAApCHKqvwKPGFFHIj39EMEA0aIGuxV5cfm9MjF02i23U6mRtIK
XRyz0j8OBBRFHAldtb4w3O7naAqOjSEQYZMBmgJPRoRR895fW9GOClU8xhSu8OOgKBIaJ3SnJ7wC
ZlAoHlIuh50ZqUG44gM2ADOvvhgFOyBg+MqL+zuSlU6YoUrvDcqCQxsaoEKO2L1hLGpIYotUCFHb
F6xyVbikBFetIj7xLmjDWJSVJde3IEACgjABo4Tub3ibhqMh2OWrKF0rM56ZZKyryMNessbOWiqV
auk+Mc/TZIQrpVkniEy5oEkQ1TpDYN4xgafgsFUUAQI9p6w89AKsBAL0BAwhgABByk3XR3AyAIMR
KpsKAKdM85DqQLSOl9PD85HTEAGGqQRSHIXrHGUpBsTI8VfmTC8Ma3QRFFElEqHPGOBgHgAirk5T
yuNsVC7UCV74XxkrACEAGxphB5i4xTd/g5yCwCqAVZhFRUGKQL0E2sm8P03QXQDtNPrWK2BpeAG/
so/bA+GAmwRXuQ/KGGwhSFS1obNuuNvrAVRBGhZCIVAo7vGCScqnRgKJboaDNJqAiIQHYE7QVylR
IJtquORVwhAZxotETwvJk0jQbhVI7DR1ZjWEgSFDsISCMhNDkN/GAICIhFCIUXnnHyIJGm6U0wl9
4qtlYXRBIgrZ1es3qFsCKK9xIL5TrDADXEUFOHYa7QMvCOmAtiFgScHq4nk1Q0VkEIcGtGHMgRpE
6NUBT+8btPkEACgKhWAbQtynJ6xgRApw62sm8vBecDgo87BnaYwNoYFeQ0vG6gzZZhiSNAkGmQRE
OTfWagrEkIGuxbzt6wxEjQyCulXiPUJjCEq3ILisANICPLkkbeAdhKAjoKKdzBZIHImgFijsulSH
BeH5GEERNhI1rnrHaUV1BOGgkF8p1jMI4YQRDihDrrHOCgIo1G7p4wS74MUvGLfcnXz9d5Zi42qI
j6es66GSOyK0jvWPIInUdqvb7ygnwEK1A62rizEFSi6ReW93KBjiHedGbxLA1QPKDHFjQaVVVXm3
dw0klUlwldJ5Mmgwi5LdO9733vBkFyTEROeE05YpKFtsSL7DXGjxhY6OgUGM5KGnweMB38CKJio6
aGzwYKgN1fhVmaEyV5HBWsMEBWsARE54TTnrdOp8bSesB6pOo8bSesb4USS2gMG7wHUOcPve2t11
NtzuWU1GNI7RV3kea0BnETCYJF6xnIkSTkYlHxgYxIBRCANoBoxfTqkNmvLVW67cIIUEMPG1mcYp
RxDUpFQ20CrDtcapVcAjUtHQ08ZvclNIrTHFQK86xpBfigFQxAK84h3vbtXU3nOzM18kd4+Ra4l5
V2uF9mITQ8qG1WysvFZzkmHnmiwjou5xj6cXBWUK6WGzesVsdQR5V24VCkT7YtVOILuO3Zd78Y1U
xrabr8Nt123KGKuC1qm3ld4pVksoVil2lYvl85IngdNiwvBVYecMYwqEQBGgGodYqW7JFCOxuxb5
FwSfkJAHADsunkuBkgRGBsa7LuecmF4CicQWa68YSkwkhCxThSsXivnLKOMHZBWht0eXNIXAbLxV
desS4PiuW3tre9d7wkmhAaUpVoMjEcdDka0wihBaKrAPecSERF7bXjzlhKzKnNqvHnrERcAoREQ3
lNPkxiDCiI+RMPnMSseCrM/UfKgFQxVgCpIpEXlE5uEwAAUQgDaAaA4M/dLLkBji4Uy1HuJcHi6K
geajUe7zg2YAUQgDaAaA4yKZRcoIg2yKTiL5wGHgpAOj5F084iiidR2q9vv6pBzs/hyfnHvOrfoK
BRAA5ccr0RWFOI0DHS9m8ODoJtArJJoW319Ln+cZ46y3DTne8M57xugNgXfrpyWuAwM+VDD5XR7c
l+nfvOd5vO8SfRUJgjvjKpN+8Eo++MvfH9YPcvOUWu74wZdO8/HeW8u/4xXyTlwFxJTnX4waOJia
vdzZxCfn6iv394j8rlid/wB4Lws5yAnMRMEEEkd4Qsyk21W6xoDgS8v37zR7+PGPxIXnePXR5zRc
nrIIiSdDgU93jEBnMxKlI7uQ3yXnOWF94ad5XnB/bvWUWr13gxzQvNNZQJBcVIjgvnO7PtkNzXje
Fd5Nwqjidh+cnHvCzjLeV0/h+n25xX6MQEcSj+AEH7YqDdrz+dAD2Yl8gSqXTsizsMsAJJIgIGga
8DkJZLIuNDmgvLa1xkpozYlrcQLEdEuzJHVARKUAt7U3RIVypw9nUKKBHy4WpcWIIRFV6Viheg6x
o3JxGovw/quO6CQILTZoUfjLgjBgQCXsS+pj4tQAsDrmDdWEXlwxcQh6XCtmFw1z3ir9N/DDrj6c
HBTXHn6NS4MJecG6DZsxrU1NfODQyJzijcUt/UwWffGu3Nm8Q9b5K8ubfRmw+eMfOQcuaa3MGtBe
7jbxoMCxOO+8QHrvPGIacQ5xLp8ayHeGux16zV1Wnty+GptTnN1V88ZUjs6yoWb84r3lEC/6yAvD
xrDXzxxxibygGm8ANGj1nAh85c4M79OKrE4dYJs1uTDXeed4OianLMaldf3m9fjLOsr5w/efw5sd
/UN7yHdaOUmX4WbWB3IOAvAdGB8Ms2RCVSfrI5NFwIRBtkUntya2wdOBBnFil95qqcP3VEzmwF73
2jvzvFSFasd5qNbmjaqShBo1V25BgwYESFbs0+cKppiPSKWXRv4xu2ggCDSi9O/nA8BSguBd3QW8
U7c2YcS5x98Da/Q0tz8zAcacmHDzjJzv4znn7ZDRrfGbL1MoGufOA1f0xaG185YWbesDJN8lmH/j
l/DhKEbyYCwLvESCuBXXGEbXJduHEHdue5vxmgVjihgjqs6wCbYju4wIlvOAkFWTWIwivkmHsLnI
jTy+MjZNPM6y7pI5UEc5723NwDHDXjvHlOLy4yN2efGO3vBalU9aM0Q/TnGgbHvAaBzgAo8dOLOH
WF7GIsBvrxhpzvC0ePGG3ge8C6GzG8eMRj19BvRp/ec5Ozj6rkwG539R3cXetfT/AJw7lxVw5x4r
hbrJvespJIYCujK7Os3xgo4Cc/bBDSVxa1wY4O335y7fQC7qPExESQsx2a/PjIXezlwY6a6wFr0b
zvFKLuYU2DFbF4cCHOHNcVUCuE0ir0ZSsaNBhKXjFFJz+s1XZvBifNwa1sd5VKaLMvRN8Zxq66xI
V48OC3Wj9YF9nHjGghzzMmro9YLQ7PGKIjW2HWAGlH5wQSG+66cUI6ZwZeVLdGGIN95o04cGPF+c
gEBlp6w8HWLSjd528Y6N8eMpZne+cVDZDI4fqf3lusup9Q1msvrHnE+pibyZxfpz1g8j39E1/WHW
aO1+eMC4AMwhoMu+bjvdxwKhiLeBRfH0L1kGq+/GSmnWOxgr6zaR3nGc89ZP95oIxwFclzu4Cnh1
z3gxHLziFOE8YU+74wVxEU8YGribw4W9TB8iYk7QMNh294NAb5w595yROPHWWxNHOs1O7d1wUeMW
LYa5MrSaHKTbZrWsBdcSa/r6jG/QNPswQNl75zS0IZLepjx885Vh3jE1174xRT0ce8rXFuibD+ce
fr1i43iiPAG3HCh+4KgjpvWTRXQ0UAQ1RKUurgMcFfYysFhy6fjCadBRAKduE/OLTVTUiFobifTj
6sAKiVJ4UFPt9NIuwHR4DTvJerMrY6xN+phzL1hclAESANnpM0l7xuYBFUEV15GRcQcgklHlYoHL
zrH1BUEozsezDbtnePwNIhoVd86OMa0GEqCq601cLqYDadYTJYKUAEO9phzwtTsBCDujmHO/pE4K
8ZdlJLi6UmDqgeMUAbNaMSt5uEcT1l5zYAFO+8odhXKeDxm2V1kJ3iELJUoktaInCdPeDkkO+8k4
bhloZVMVIJpZTnSYrxJMlLr4xIup6c6a4x0EMCNjWhEWwXgZrnLovGMHjUPeDucb25HBpar1kNv9
mBXx2fOCDpzDzlHaXz6zeUrUeKYLAOhcgGEgDBeSgx9g5JON7fWJveu5vLxsoQWIaBu1ngd4QoFF
tSlfG1hXgzTnnxh0VxPf5wpAHB5Sg+mrWIUhqaCK6hseF1gTfG+8E5E++MX6594A8PecplLu2n35
z19JfobUHCMcqroT2ravvvFfVGpU4b5Yn4LjM6BUIEpp9b+izjG2iEK6VZA8QmbXPBaA6WgAB6b3
lQR8KVATqiB6xHAbPRd5+cZ6kRAA2IRZEKLzzkEVR7MDXYq87y0BQzYwlVSioTgJxnTiaBiDVGid
msuSWmIhbJEhrgysItxCGqQRSHIXrHBs2Gouz5W4Iuy8gV6sWykhsmbrIlgKWORKHmXWBtOxwOAL
asq7vGGAi0wGgpodU7mMkIjB1QBpqt9vWLpYY5Qr7K4Yiq1qUWhs51xtywOsCuFqANIbVXSYjBTA
EFQOxTxgt2iO41jakprkMUYlYiQkYSEFisu8ATMPl8iNS+EKlKGPA7Ttg4JeELos1ct16lDJSqeY
oUrvKoy5QgRXrSI+8M/QSgBhA9rYA6xAOAQyGFYABICPLhOesaDjU0mmLThxY4slKlAVklGTWrl6
6oCFSijGMvQvzgG9yCkAJF52mwWmIp2QwoVRYAaQETnDUTdIKFFJxYozlMbwSGDqAB2VvO3rIQhl
Fc1HXOmRBdmKFYWuFoBJS3gpUybygPacEVGK50bmapqlALE6eQEeM1SFREpQUBSI6qesDoEBQSbG
kdHDXmYIgEysULucB3J1MZXhgVAg7V3OK8S5tiWpLkgbYCypW8ckYlIukfjTgsWQhdCxEASAwCx3
mjv2XYgoy62b1B21vRhEE0jH7JjjpQ0VVBI7V3d4ahQhgwBGDFYLtAcHYk+FGwaBriGzVmMAkVyt
ApBQGl4vLjsFZabogpHqtZvEJGTnRHU0AjhGzdym9cCSgRhWU3CUrdJREBDscsdKF0rMQUd+zY4K
JCUIs1s5gGAU0QqxKJsi69uU9xwg6wDRIfbe8fYieAO4eN0mEhSkhii1QIUdsXrN/IoEWa8cwDCx
KQq0TUabs4a6ZiSzkRLdHAQoxHgzl9UtUDsIVVg6s6xQXt0esSOu8vXWOoeTu9P14Prxnm4w4C8H
rODo3PTQrMXIICxAANvoDFAdViEAocDo3gZiICiEAbQDQHGcTUIfkDvCAJgNHuO+ceJwC5IENvoD
Jp4hBONLNdYo5BUoukXlvdxQNiaQ4hdfbBgCkMVFab0NbOa3nDUiSpAiOzexR8imbW2rTQQZ5il9
5+gcHILrJj4SDxFdHowGGI2N5tTfxlV8UBtV04qqzzi98arfYPJ09dZvwmilBY4qBXl1i1CLSDKL
lNGnLFNpBdMTZiLLalW1UvFVddq4AhQBU8sO17XnJSEoCIAm1IBONY8J1LSUZR4oP2yazuRC6XZ5
wK4RFh6qzNzUjn4Csw0FQiAREN8JpxyhxJOaAwbvKUZqC80Gb7yaEn54AQcdkQoRE4ROEw0nCMYb
GuynGMGdP0Mm9+xx3csTFs0GKuygx1o8ZzkGxPYMcGuoNIQChxUAvOjxjXRlpBlFyjDTh9KiwCAb
Qmpxg3hk5Pir+8WtPL2PFV1iLOqQba8tVbqbcAIiCjHgqzFyF4e0QkmmaFXpvyRLgxJd42zZtXve
u7g9AEL5Gjds65xLb0JkRIV7AHyacZATyJtsGc7+cu1ysBIsLygb7h4xOCFVXQCqrwG13g4nJIKH
RfAZxo8YIrgDLRULpUNngxBlCwREUtNg0zmSYqQeajcS4ucopEW1E0j1nFGOX5Aly4aQaQgFnFgb
9HjJwXqDOJU/WSY0dCiMZyUGPjGBuqCryg6F9YPUcoe9vw2rrveSbUpqMaR21XePOGxgiIFkmp41
nqdOp8bSesRDKsLPKDoX0YfE0AAKqAPlX5VwZ0RNHuJee8dEEqmqvKry5wT3kBJu46c/if3lz3j9
ApQFQF+XE19O8mCLa0sbA5ryvgF8CYO6MaIBGBdPB/8ADcpwawgPhifn6heM3PTnOJiEByqw/eWe
gE0BRpCpOSnhcF5YCuxgedK4oEqpaOZS6+Muk+ijwJc8gehQ+5nDTU+nf0DyeZiDgfzjpzlPOT/w
yxqF6ypm/jPze8AKynRecduq5ZJ1+s9B+cZrft9CrpJq5AMRZq4knvGDvesWq8XA0XY85A3A7V/j
KkluzzMcQao/SP8AnKEomgYfrKDBp03Lm9EdBD16xFRAgklXlcOHyEaJ6xb+t95qb4u/WXzCecXq
TXfn6bC9ObODHD6UBeH9ZN3z1ibzwOXDJ8YUGHOsF2xjwT1dGB8+svjD9T+//k3g0OzafkMtSQ6p
Vwpq62F1p21FnxkDuHjdJiiGvjQuy0VVBRODF8wRQI5jwylnGBBdp0s3ykTCotnY1B2oIUpH7XCc
yFtcFEohsKlIGG+JAMCApUqgWDs23FMhEVAojoATg2vNxTGKCCC+EdeL4yJEjegKG0Q0Ip5M0gWB
hBRUS8gb4pkZpQEHSkDcei40I9MhAjGbdhtVXjJfpgYEBSpVAsHZtuLMdQavQ+mT75INLjCBQArQ
OtvRggGgQoFnVqxOraodoIARYDyr0YnMBRAQWtWqDmnjCZs8m+1FICUZpnjKUT/o13yoz3X6qePp
DeocHLjKyTHfdwR0TjNOuTLH9zAEa7wq1L5xEHbDFGEk5duPxa7MS7D7ecVuDMg8W+MhCT5xFks7
wXQAfGce8DmA2+/RlaT7Yz1k2ILubb1iKBoIvMv94otGvbvAS0I8mbChMel94jARZ2pxvEJlTWg7
6nqY7GR3vFFpJHH4mA0pBYPWJFMWyLD9YnvefbNATscmAKMQKm8SfQN6dfOLwDK9J7nOSLdnWAqp
TH5ciYN+J/D9Osv0V4IkijhE4cowlqlMBVeYAvMDLKn5giIFkmp41lMbUhXnlMW2aoqssOCwvmYF
hmpZZNR0rvx4weUtAI/dcYFUJgRE54TUxZyCpRdIvLe7musgAPNgzneKuUN3kRSxed+3FVaHZ1EJ
VIEwIiQXYQDuC6YzwmsRVEKXggsAAwByqvEhEbxIEFhijlClFIi8o93L6s2hTSPkezjGfewDzYMv
GGxURsNtG6tb5rnkRxBbYMuIAkhqeWHb7cgXkROSACVKVbJoXKcpNatqtaA0HW/LhnXv62Ome8dA
JzgjqY1Hiui4G4sxU1xMjLNHeIE5vnHRu3kw2tcd4CjhfbAhOY/bKFYe8QK0F1roxHAw98ucAN5G
7hgwIb7/AM4Dk8jyr5++DrhSrLVyqCuvYf5x+5TBU71t85ddh8d47D/OKABml8mHeNlFfWQGT7LW
A4Dp1esFzsOUzYTnuZpbH4y31jrUwlWVp8ZfRk74wfeXnCA+ZrOcUk6wEFOcQNNecsJnxGH6n95M
m8f/AKmsP/qZxrn6PnIjfth+vGO/Rq4kcsr24Do4/wAZNPk+rs+mGBcmXWKC3FH9YpVe8vIg+XNe
d/GbQZFinjEjDgpiEIY9e8nqFd66xeR++VK2PVxVcFF4XATTc/WUoPV3iaFT56x0nSCTgHv5yyUn
GsS14VyAbvvE9jI50M8Yo/HjLTpdnrIYYCCvvxiKF2Uu+DEUQ9oP95yNH2xXLmVzp9jNqZRHeCh1
jt+MrJi5NXDOPjrK5T/jFvvBF3ZlaP2Modd5/9k=
--bcaec52160c948fee904f336ad6e--


From nobody Tue Feb 25 00:30:06 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 9D7001A035C for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 00:30:04 -0800 (PST)
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 I3ulgulqF5ly for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 00:30:00 -0800 (PST)
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 8A2531A016B for <ietf@ietf.org>; Tue, 25 Feb 2014 00:30:00 -0800 (PST)
Received: by mail-yh0-f46.google.com with SMTP id v1so6498169yhn.33 for <ietf@ietf.org>; Tue, 25 Feb 2014 00:29:59 -0800 (PST)
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=SAtaU8+vwTz48PqMSlFZEs7nL+uYBuWDzk+9js6PG5c=; b=jUfVcH3HsQF6v3Hl6U4mCcDmbuEdWPtpyMKGbVn7fYVm2IWamrcTZDsJm+4YSmdOQH y1JpkCLIwoicv6l1HzgbIdY5B/Soy7zZ7nz/bI/A86Y7c4SgHcdC4TDuiDCD3y1VBz8f q5S94IitossYowsXQekeaTaXyycCn6mPl/TXrGpOvJhIPUhZRnEFWog23x/yx4K7vOUE 5/4xBLrCIShdO9jU9AXoVg8CUH1k4v4Ijj3tywbG0uVfhs584fXi77vA3TF2Tpt/e2Qa yqbjKUjaA4QCX3vA9FgSv+JT2aHGmy1ldRDyXyh6A7FKKLpbx3j8OIakr/ewlu73n/iz hbUw==
MIME-Version: 1.0
X-Received: by 10.236.62.232 with SMTP id y68mr4691123yhc.12.1393316999616; Tue, 25 Feb 2014 00:29:59 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Tue, 25 Feb 2014 00:29:59 -0800 (PST)
In-Reply-To: <CAC4RtVBfMFijaZt8_AhBuic8yFqc+OJAJCWrmpfBqRgJgJ-L4Q@mail.gmail.com>
References: <m2eh38sucu.wl%randy@psg.com> <52FB1948.2000101@gmail.com> <m28utgsrxf.wl%randy@psg.com> <CADnDZ89uEo1Tny_ySvMCi-NP31dxt6AnLF6k6b4nZqRA7eQCHA@mail.gmail.com> <290E20B455C66743BE178C5C84F1240847E6334711@EXMB01CMS.surrey.ac.uk> <8967C58F-678F-4ECD-A9E0-EA3718F33A70@gmail.com> <CAC4RtVBfMFijaZt8_AhBuic8yFqc+OJAJCWrmpfBqRgJgJ-L4Q@mail.gmail.com>
Date: Tue, 25 Feb 2014 09:29:59 +0100
Message-ID: <CADnDZ8_PobCzkP0FJEV5duwjpXabm_s96wPrOLJBUXrjmkbhJA@mail.gmail.com>
Subject: Re: calls for discussion
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: multipart/alternative; boundary=089e01228f9ed260a604f336e401
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cBAKDUQ4R7MtxgEsnqGmCHYtyNI
Cc: Margaret Wasserman <margaretw42@gmail.com>, "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: Tue, 25 Feb 2014 08:30:05 -0000

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

Hi Barry,

I agree with you and Margaret. My comments below,

On Tuesday, February 25, 2014, Barry Leiba wrote:

> Sorry for being late with this: I'm behind, and catching up.
>
> Margaret says...
> > and in many WGs, _all_ of the most important decisions have been made
> > in a meeting room at an IETF plenary meeting (and merely "confirmed"
> > on the list) for many years.  In other words, most of our work is
> > _not_ done on the mailing lists, or even by people who are reading
> > most of the messages that are sent to those lists.
>
> Indeed.  When I do my document reviews for IESG telechats, I read the
> shepherd writeups (and really appreciate the good ones!), have a look
> at the document history in the datatracker and any last-call
> discussions, and, depending upon what I find, sometimes go look at the
> working group discussions.


I agree totally, and believe still IETF meetings and lists discussions need
improvements, and ADs guidance.


>
> There have been times when a search for the document name in the
> working group list archive looked something like this:
>
> [lmnop] New Version Notification - draft-ietf-lmnop-banana-07.txt,
> internet-drafts
> [lmnop] New Version Notification - draft-ietf-lmnop-banana-06.txt,
> internet-drafts
> [lmnop] New Version Notification - draft-ietf-lmnop-banana-05.txt,
> internet-drafts
> [lmnop] New Version Notification - draft-ietf-lmnop-banana-04.txt,
> internet-drafts
> [lmnop] New Version Notification - draft-ietf-lmnop-banana-03.txt,
> internet-drafts
>
> In other words, no discussion whatsoever... just document revisions.


I experience WG chair calling a participant discussion/input as disturbing
mail boxes.


> I would ask the responsible AD where the discussion was that produced
> each of these revs, and the AD would say, well, this is one of those
> working groups that does all of its work in the meetings, and they got
> a lot done on this document at IETF this, and IETF that.  So I'd go
> look at the minutes from those IETF meetings.
>
> Guess what I didn't find.
>
> I'm sure there was discussion in the meetings, but there was little or
> nothing documenting it, and no explicit calls for discussion on the
> mailing list, at least not with the document name associated with it.


I commented before about documentation in this organisation, and IMHO  it
needs improvement as well.


> (It's possible that issues were discussed, and the document name
> wasn't mentioned, but the chairs and AD didn't help point me at them.)


I find it difficult to review and discuss with authors sometimes as well, I
like to do it on the list. However, some groups discuss and comment review
through private channel so that it always is not easy for IESG or any
reviewer to know the dangerous bits.


>
> This hasn't happened in a while.  It gave me a very uneasy feeling,
> and I intent to push back harder should it happen again.  I believe
> that we need to be having these discussions on the mailing list.


I agree, thanks


>   I
> believe that discussions that are relied on from the meetings need to
> be minuted in a way that those not present can find and review them.


A policy should guide these activities because it is important to the IETF
organisation future and experience. If an organisation has no
effective documentations then it will not have experience and will fall in
future.


> And I believe that we need to have a record of reaching consensus on a
> document.  A series of document revs followed by a last call, with
> little or no record of discussion, just doesn't make it.
>
>
I agree, but just to point out that I experienced one WG document in one
WG, while editors are editing issues by DT discussions not the WG
discussions, so the editors may not know the rules or there is no much
policy for editors, they can edit any thing even without discussion (they
just use the WG to adopt and then they do what they like and they may even
not acknowledge inputs to discourage participation).

Thanks to you and Margaret for these important comments.

AB

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

Hi Barry,<div><br></div><div>I agree with you and Margaret. My comments bel=
ow,<br><br>On Tuesday, February 25, 2014, Barry Leiba  wrote:<br><blockquot=
e class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc sol=
id;padding-left:1ex">
Sorry for being late with this: I&#39;m behind, and catching up.<br>
<br>
Margaret says...<br>
&gt; and in many WGs, _all_ of the most important decisions have been made<=
br>
&gt; in a meeting room at an IETF plenary meeting (and merely &quot;confirm=
ed&quot;<br>
&gt; on the list) for many years. =A0In other words, most of our work is<br=
>
&gt; _not_ done on the mailing lists, or even by people who are reading<br>
&gt; most of the messages that are sent to those lists.<br>
<br>
Indeed. =A0When I do my document reviews for IESG telechats, I read the<br>
shepherd writeups (and really appreciate the good ones!), have a look<br>
at the document history in the datatracker and any last-call<br>
discussions, and, depending upon what I find, sometimes go look at the<br>
working group discussions.</blockquote><div><br></div><div>I agree totally,=
 and believe still IETF meetings and lists discussions need improvements, a=
nd ADs guidance.=A0</div><div>=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<br>
There have been times when a search for the document name in the<br>
working group list archive looked something like this:<br>
<br>
[lmnop] New Version Notification - draft-ietf-lmnop-banana-07.txt,<br>
internet-drafts<br>
[lmnop] New Version Notification - draft-ietf-lmnop-banana-06.txt,<br>
internet-drafts<br>
[lmnop] New Version Notification - draft-ietf-lmnop-banana-05.txt,<br>
internet-drafts<br>
[lmnop] New Version Notification - draft-ietf-lmnop-banana-04.txt,<br>
internet-drafts<br>
[lmnop] New Version Notification - draft-ietf-lmnop-banana-03.txt,<br>
internet-drafts<br>
<br>
In other words, no discussion whatsoever... just document revisions.</block=
quote><div><br></div><div>I experience WG chair calling a participant discu=
ssion/input=A0as disturbing mail boxes.=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">

<br>
I would ask the responsible AD where the discussion was that produced<br>
each of these revs, and the AD would say, well, this is one of those<br>
working groups that does all of its work in the meetings, and they got<br>
a lot done on this document at IETF this, and IETF that. =A0So I&#39;d go<b=
r>
look at the minutes from those IETF meetings.<br>
<br>
Guess what I didn&#39;t find.<br>
<br>
I&#39;m sure there was discussion in the meetings, but there was little or<=
br>
nothing documenting it, and no explicit calls for discussion on the<br>
mailing list, at least not with the document name associated with it.</bloc=
kquote><div><br></div><div>I commented before about documentation in this o=
rganisation, and IMHO=A0=A0it needs improvement as well.=A0</div><div>=A0</=
div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
(It&#39;s possible that issues were discussed, and the document name<br>
wasn&#39;t mentioned, but the chairs and AD didn&#39;t help point me at the=
m.)</blockquote><div><br></div><div>I find it difficult to review and discu=
ss with authors sometimes as well, I like to do it on the list. However, so=
me groups discuss and comment review through private channel so that it alw=
ays is not easy for IESG or any reviewer to know the dangerous bits.</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
<br>
This hasn&#39;t happened in a while. =A0It gave me a very uneasy feeling,<b=
r>
and I intent to push back harder should it happen again. =A0I believe<br>
that we need to be having these discussions on the mailing list.</blockquot=
e><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"></blockquote><div><br></div><div>I agree, =
thanks</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">=A0=A0I<br>
believe that discussions that are relied on from the meetings need to<br>
be minuted in a way that those not present can find and review them.</block=
quote><div><br></div><div>A policy should guide these activities because it=
 is important to the IETF organisation future and experience. If an organis=
ation has no effective=A0documentations=A0then it will not have experience =
and will fall in future.=A0</div>
<div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">
And I believe that we need to have a record of reaching consensus on a<br>
document. =A0A series of document revs followed by a last call, with<br>
little or no record of discussion, just doesn&#39;t make it.<br>
<br></blockquote><div><br></div><div>I agree, but just to point out that=A0=
I experienced one WG=A0document in one WG, while editors are=A0editing=A0is=
sues=A0by DT discussions not the=A0WG discussions, so the editors may not k=
now the rules or there is no much policy for editors, they can edit any thi=
ng even without discussion (they just use the WG to adopt and then they do =
what they like and they may even not acknowledge inputs to discourage parti=
cipation).=A0</div>
<div><br></div><div>Thanks to you and Margaret for these important comments=
.=A0</div><div><br></div><div>AB</div><div>=A0</div></div>

--089e01228f9ed260a604f336e401--


From nobody Tue Feb 25 00:57:09 2014
Return-Path: <sama.digitalpolicy@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 292691A03A5 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 00:57:08 -0800 (PST)
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 IyeXnyT1DDrG for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 00:57:06 -0800 (PST)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id D6E131A0388 for <ietf@ietf.org>; Tue, 25 Feb 2014 00:57:05 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id rp18so61498iec.22 for <ietf@ietf.org>; Tue, 25 Feb 2014 00:57:05 -0800 (PST)
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=39wGZofapyXoXbBH50Jv9o2B8/swzOjgAvZSrboF3Pw=; b=BmV3KMtjRxcw9kXecnxdlqUbY1xsZFOBV/U7jAs3cVA677uK+anyNMo9ycIFsv6+EW /6+MGYQYSn5walaylTR4LcRVISs+IqJawS2Kvw3CtVbStfZ+Z2ISv+3OFI00HrVz1oOw azRK2NDQSGLcof1gj6pichmDUbtMGr7YUmiu4RXkKdZgDncHfalygylfVSSrilYl+Ave x3/hKBJQ8L8xRZqSoCzOgxNLnoMLj7xtjLq/18t6HgcCat5AWOdVK+7+/u85WIRFuyE7 vGgBoEjU4Wdp7J+xdPocvXJgi3gwHuumKvMJWkhKeWfQ8trsW0ZYpk2dMPWyz6PUp8MK AYwQ==
MIME-Version: 1.0
X-Received: by 10.43.143.211 with SMTP id jn19mr19023601icc.0.1393318624993; Tue, 25 Feb 2014 00:57:04 -0800 (PST)
Sender: sama.digitalpolicy@gmail.com
Received: by 10.50.178.235 with HTTP; Tue, 25 Feb 2014 00:57:04 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140222080001.0d7a85e0@elandnews.com>
References: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com> <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@mail.gmail.com> <6.2.5.6.2.20140222080001.0d7a85e0@elandnews.com>
Date: Tue, 25 Feb 2014 09:57:04 +0100
X-Google-Sender-Auth: JkhzML5O_EHeyz04r2bjLCJXvZ4
Message-ID: <CAOLD2+anwyXiRrS-LVnvKXmSjVjOo1moxG8S8zeETT7Mqfpg4w@mail.gmail.com>
Subject: Re: IETF Anti-Harassment Procedures
From: Andrea Glorioso <andrea@digitalpolicy.it>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=001a11c2f1acb3bf4b04f33745c8
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1NeL82EpgP6ZzDOUZDuNIRhuC5M
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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: Tue, 25 Feb 2014 08:57:08 -0000

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

Hi SM,

On Sat, Feb 22, 2014 at 6:39 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Andrea,
>
> At 06:50 22-02-2014, Andrea Glorioso wrote:
>
>> Could you please clarify / expand on what you mean exactly?
>>
>
> The end of the sentence is about using the procedures in
> draft-farrresnickel-harassment-00 when other procedures have been
> ineffective.  As such it allows the procedures to be invoked when the other
> procedures did not produce the desired results.
>
> My preference is to use this intended BCP when a case of harassment is
> reported.  If it a case of, for example, me being rude to you, that can be
> addressed through existing BCPs (unless it is reported as harassment).  I
> prefer not to see this intended BCP used as a threat.  That avoids having
> to get into a lengthy security consideration discussion about the misuse of
> the intended BCP.
>

What you say makes sense to me, but I do not well enough the general "norms
of behaviour" within the IETF to go much beyond in my comments. However, I
do not see the logical link between your original statement regarding the
nature of law and the way it is used (or not) and your consideration above.
This does not invalidate the value of this latest comment of yours, of
course.


>  The passage seems quite clear to me. An IETF document (whatever its
>> nature) cannot trump applicable laws. In some countries / jurisdictions,
>> especially when certain forms of harassment are a criminal offense, not
>> informing authorities might be itself a violation of the law. The trick is
>> of course knowing which particular law / legal system would apply. That's
>> not something that can be solved in this document, though.
>>
>
> The question was about whether an Area Director would inform the
> authorities.  There was a question from Fred Baker during a previous
> discussion about the same topic ( http://www.ietf.org/mail-
> archive/web/ietf/current/msg83398.html ).  There wasn't any response to
> that question.
>

Not being a lawyer but having studied law and working in an environment
where legal procedures are rather important, I honestly do not think it is
possible to give a universally valid answer to such a question. It depends
on many factors, including (but not limited to) what the applicable law(s)
of the applicable jurisdiction(s) say. I understand it is not the purpose
of this proposed BCP to become a general compendium of anti-harassment
laws. ;)

Best,

Andrea

--
I speak only for myself. Sometimes I do not even agree with myself. Keep it
in mind.
Twitter: @andreaglorioso
Facebook: https://www.facebook.com/andrea.glorioso
LinkedIn: http://www.linkedin.com/profile/view?id=1749288&trk=tab_pro

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

<div dir=3D"ltr">Hi SM,<br><div class=3D"gmail_extra"><br><div class=3D"gma=
il_quote">On Sat, Feb 22, 2014 at 6:39 PM, S Moonesamy <span dir=3D"ltr">&l=
t;<a href=3D"mailto:sm+ietf@elandsys.com" target=3D"_blank">sm+ietf@elandsy=
s.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 Andrea,<div class=3D""><br>
At 06:<a href=3D"tel:50%2022-02-2014" value=3D"+15022022014" target=3D"_bla=
nk">50 22-02-2014</a>, Andrea Glorioso wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Could you please clarify / expand on what you mean exactly?<br>
</blockquote>
<br></div>
The end of the sentence is about using the procedures in draft-farrresnicke=
l-<u></u>harassment-00 when other procedures have been ineffective. =A0As s=
uch it allows the procedures to be invoked when the other procedures did no=
t produce the desired results.<br>

<br>
My preference is to use this intended BCP when a case of harassment is repo=
rted. =A0If it a case of, for example, me being rude to you, that can be ad=
dressed through existing BCPs (unless it is reported as harassment). =A0I p=
refer not to see this intended BCP used as a threat. =A0That avoids having =
to get into a lengthy security consideration discussion about the misuse of=
 the intended BCP.<br>
</blockquote><div><br></div><div>What you say makes sense to me, but I do n=
ot well enough the general &quot;norms of behaviour&quot; within the IETF t=
o go much beyond in my comments. However, I do not see the logical link bet=
ween your original statement regarding the nature of law and the way it is =
used (or not) and your consideration above. This does not invalidate the va=
lue of this latest comment of yours, of course.<br>
</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 class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">
The passage seems quite clear to me. An IETF document (whatever its nature)=
 cannot trump applicable laws. In some countries / jurisdictions, especiall=
y when certain forms of harassment are a criminal offense, not informing au=
thorities might be itself a violation of the law. The trick is of course kn=
owing which particular law / legal system would apply. That&#39;s not somet=
hing that can be solved in this document, though.<br>

</blockquote>
<br></div>
The question was about whether an Area Director would inform the authoritie=
s. =A0There was a question from Fred Baker during a previous discussion abo=
ut the same topic ( <a href=3D"http://www.ietf.org/mail-archive/web/ietf/cu=
rrent/msg83398.html" target=3D"_blank">http://www.ietf.org/mail-<u></u>arch=
ive/web/ietf/current/<u></u>msg83398.html</a> ). =A0There wasn&#39;t any re=
sponse to that question.<br>
</blockquote><div><br></div><div>Not being a lawyer but having studied law =
and working in an environment where legal procedures are rather important, =
I honestly do not think it is possible to give a universally valid answer t=
o such a question. It depends on many factors, including (but not limited t=
o) what the applicable law(s) of the applicable jurisdiction(s) say. I unde=
rstand it is not the purpose of this proposed BCP to become a general compe=
ndium of anti-harassment laws. ;)<br>
<br></div><div>Best,<br><br>Andrea<br></div></div><br>--<br>I speak only fo=
r myself. Sometimes I do not even agree with myself. Keep it in mind.<br>Tw=
itter: @andreaglorioso<br>Facebook: <a href=3D"https://www.facebook.com/and=
rea.glorioso" target=3D"_blank">https://www.facebook.com/andrea.glorioso</a=
><br>
LinkedIn: <a href=3D"http://www.linkedin.com/profile/view?id=3D1749288&amp;=
trk=3Dtab_pro" target=3D"_blank">http://www.linkedin.com/profile/view?id=3D=
1749288&amp;trk=3Dtab_pro</a>
</div></div>

--001a11c2f1acb3bf4b04f33745c8--


From nobody Tue Feb 25 02:04:47 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 90B3C1A0665 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 02:04:44 -0800 (PST)
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 x8zrMJABGC8R for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 02:04:42 -0800 (PST)
Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0011.outbound.protection.outlook.com [213.199.154.11]) by ietfa.amsl.com (Postfix) with ESMTP id 405381A0031 for <ietf@ietf.org>; Tue, 25 Feb 2014 02:04:40 -0800 (PST)
Received: from AMXPRD0310HT002.eurprd03.prod.outlook.com (157.56.248.133) by AM3PR07MB241.eurprd07.prod.outlook.com (10.242.18.139) with Microsoft SMTP Server (TLS) id 15.0.888.9; Tue, 25 Feb 2014 10:04:38 +0000
Message-ID: <00ec01cf3210$4a1e50c0$4001a8c0@gateway.2wire.net>
From: t.p. <daedulus@btconnect.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, <ietf@ietf.org>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Date: Tue, 25 Feb 2014 09:59:28 +0000
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: DBXPR07CA018.eurprd07.prod.outlook.com (10.141.8.176) To AM3PR07MB241.eurprd07.prod.outlook.com (10.242.18.139)
X-Forefront-PRVS: 01334458E5
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009001)(6009001)(51704005)(199002)(189002)(13464003)(377454003)(24454002)(74706001)(95416001)(74876001)(94946001)(92566001)(95666003)(50466002)(74366001)(87266001)(74662001)(31966008)(47446002)(74502001)(56816005)(90146001)(89996001)(87976001)(83072002)(85306002)(87286001)(85852003)(84392001)(65816001)(88136002)(14496001)(66066001)(77982001)(80022001)(92726001)(33646001)(61296002)(83322001)(80976001)(59766001)(47776003)(63696002)(79102001)(44716002)(62236002)(93136001)(81342001)(81542001)(93916002)(62966002)(86362001)(93516002)(51856001)(46102001)(53806001)(42186004)(19580395003)(76482001)(69226001)(54316002)(19580405001)(56776001)(76796001)(76786001)(47736001)(49866001)(44736004)(23756003)(47976001)(50986001)(94316002)(4396001)(77156001)(50226001)(77096001)(74416001)(7726001); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB241; H:AMXPRD0310HT002.eurprd03.prod.outlook.com; CLIP:157.56.248.133; FPR:1CF6F5E5.BC3750C6.B3D39DF7.8AD9D971.20360; PTR:InfoNoRecords; A:0; MX:1; LANG:en; 
X-OriginatorOrg: btconnect.com
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/s5DirZ58f8I73dsVUl-M2at_RmM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Feb 2014 10:04:44 -0000

----- Original Message -----
From: "Andrew Sullivan" <ajs@anvilwalrusden.com>
To: <ietf@ietf.org>
Sent: Monday, February 24, 2014 8:14 PM
> On Mon, Feb 24, 2014 at 02:37:13PM -0500, Phillip Hallam-Baker wrote:
> > Could we have an RFC to explain what is and what is not a valid
ad-hominem
> > argument?
>
> There are no valid _ad hominem_ arguments.  _Ad hominem_ is a short
> name of a fallacious form or reasoning where one attacks the person
> making the argument _instead of_ attacking the argument as such.
> (More fully, of course, it's known as _argumentum ad hominem_.)

Yes, clearly, but what then is the plural, when you have more than one
ad hominem, against the same or different people? argumenta ad hominem,
which is then abbreviated to ad hominem?

Tom Petch



>
> > Ad Hominem is a perfectly valid argument against claims of fact when
made
> > against the authority making the claim. "PT Barnum is a notorious
liar' is
> > a perfectly valid argument against a claim PT Barnum is making about
having
> > found a mermaid.
>
> I think this is only sort of true.  When Barnum is making his
> argument, he's offering testimony ("I found a mermaid").  In this
> case, pointing out that Barnum is a notorious liar is an attack on the
> testimony.  It's therefore not an _ad hominem_ because you're not
> attacking the person speaking, but arguing about the premises of
> Barnum's original argument from testimony.  Even there, it'd be a
> pretty weak argument, until you added, "Also, there are no previous
> known cases of mermaids, and PT Barnum has refused to allow anyone
> else to examine the alleged mermaid."  Otherwise, you could as easily
> use the premise "Barnum is a notorious liar" when Barnum says, "A
> contradiction cannot be true."
>
> The primary consideration is always relevance to the argument at hand.
> That's why _ad hominem_ is usually classified as a fallacy of
> relevance.  It's also why I prefer to avoid the term _ad hominem_ in
> favour of pointing out why something is irrelevant to the argument at
> hand.
>
> > The question at issue here is not merely the conclusion but the
implied
> > statement of the facts.
>
> I disagree.  The question is whether the argument against a given
> position is relevant to the truth or falisty of that position (or its
> supporting premises).  In the case of an _ad hominem_, the irrelevance
> lies with attending to the speaker instead of that which is spoken.
>
> Best regards,
>
> Andrew
>
> --
> Andrew Sullivan
> ajs@anvilwalrusden.com
>
>


From nobody Tue Feb 25 02:35: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 74EFE1A036B for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 02:35:04 -0800 (PST)
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 H_QvTtgNdJA5 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 02:35:03 -0800 (PST)
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 0A0501A0685 for <ietf@ietf.org>; Tue, 25 Feb 2014 02:35:01 -0800 (PST)
Received: by mail-yk0-f175.google.com with SMTP id 131so18124193ykp.6 for <ietf@ietf.org>; Tue, 25 Feb 2014 02:35:01 -0800 (PST)
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=1x3WkworOsD5YASqy0viSP1EpOOgJwrsr1rGuJ2LkQM=; b=cBz1PjgxypOlSaIPWOleafFdrWw0WBZDv/oRVUEaNtkOxAvSwJclyqG8NvzbQnguBe NqZe+kJlKSI0Xev0Hf5acoIKAejWpsPGdOYChR+/tiC9PFHwLISpbS9Dp/hyLBqAEALz 82EylXz9A6VG55axuKETvgTq/OMm/zOt0tiqfMkZt1d0WrQIX/22A+HGQWu/zgHfML8Q bRspMmdb9UIXwH/CmYyaKPXZEkz2kUkwNBkfjGcfKGgHcNNU224hkm6ioZ4xbpJ7jZ8i igewnMOCJP4M2Brkq0zXQuY+sMErqt+BCxpG9oLkUpi+8DQXS3moBz5YjtHjT5l89lRd ExWw==
MIME-Version: 1.0
X-Received: by 10.236.8.68 with SMTP id 44mr5027432yhq.39.1393324501045; Tue, 25 Feb 2014 02:35:01 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Tue, 25 Feb 2014 02:35:00 -0800 (PST)
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E633472B@EXMB01CMS.surrey.ac.uk>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com> <530B5398.7070705@dcrocker.net> <AF345D44D8B66B87E09D9256@JcK-HP8200.jck.com> <530B75B3.7000300@dcrocker.net> <CAMm+Lwh9acLPiW_PJkAZO+7zS6jH+W5suWDZMdys_UOypT7MFA@mail.gmail.com> <20140224201457.GO35396@mx1.yitter.info> <00D21295-2E84-4CF1-9ABA-E2024D245580@cisco.com> <290E20B455C66743BE178C5C84F1240847E633472B@EXMB01CMS.surrey.ac.uk>
Date: Tue, 25 Feb 2014 11:35:00 +0100
Message-ID: <CADnDZ8948ZaFHeyqtdqWkLtrpnwmOvjtzTOpLhBHr7K4TgK89Q@mail.gmail.com>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Content-Type: multipart/alternative; boundary=089e01634e40f1166c04f338a324
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Jhi0ayfKTBpVoWD94KliYEKQIW8
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, 25 Feb 2014 10:35:04 -0000

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

On Tuesday, February 25, 2014, wrote:

> This ongoing discussion of what constitutes an ad hominem argument is all
> very well,
> but I'd like to point out that I didn't make an ad hominem argument or
> assertion.
>
> I simply asked a question.
>
>
IMHO, you did do an ad hominem argument many times on IETF lists and I
reported to IETF Chair and to another AD, before months about that, but
still you continue and I cannot fix that situation if majority like that or
if ADs cannot fix it.

AB

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

<br><br>On Tuesday, February 25, 2014,   wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex">This ongoing discussion of what constitutes an ad hominem argument i=
s all very well,<br>

but I&#39;d like to point out that I didn&#39;t make an ad hominem argument=
 or assertion.<br>
<br>
I simply asked a question.<br>
<br></blockquote><div><br></div><div>IMHO,=A0you did do an ad=A0hominem arg=
ument many times on IETF lists=A0and I reported to IETF Chair and to=A0anot=
her AD,=A0before months about that, but still you continue and I cannot fix=
 that situation if majority like that or if ADs cannot fix it.=A0</div>
<div><br></div><div>AB</div><div>=A0</div>

--089e01634e40f1166c04f338a324--


From nobody Tue Feb 25 03:32:35 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 411281A0060; Tue, 25 Feb 2014 03:32:29 -0800 (PST)
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 AhAyi7u5h5Xr; Tue, 25 Feb 2014 03:32:27 -0800 (PST)
Received: from mail.amsl.com (mail.amsl.com [IPv6:2001:1890:126c::1:15]) by ietfa.amsl.com (Postfix) with ESMTP id E93A61A0693; Tue, 25 Feb 2014 03:32:27 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c9a.amsl.com (Postfix) with ESMTP id 358EB9FB50; Tue, 25 Feb 2014 03:31:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c9a.amsl.com ([127.0.0.1]) by localhost (c9a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZcXwBi9d3Edu; Tue, 25 Feb 2014 03:31:17 -0800 (PST)
Received: from [IPv6:2a00:1d50:2:101:a53e:be49:3265:5df6] (unknown [IPv6:2a00:1d50:2:101:a53e:be49:3265:5df6]) by c9a.amsl.com (Postfix) with ESMTPSA id 413049FB4A; Tue, 25 Feb 2014 03:31:16 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Subject: Welcome to IETF-89
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Tue, 25 Feb 2014 13:32:24 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <8D875E83-F8EC-4D92-B6BB-C013128E6213@ietf.org>
To: "ietf-announce@ietf.org" <ietf-announce@ietf.org>, "89all@ietf.org" <89all@ietf.org>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_IuPEQTyDXiPfTU5eCVVtWi-7Pk
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: 89attendees@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, 25 Feb 2014 11:32:29 -0000

I would like to welcome you all to our meeting in London next week. Here =
are some thoughts for the week from my perspective:

http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/

Jari Arkko, IETF Chair


From nobody Tue Feb 25 04:30:07 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 21A9F1A06BB for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 04:30:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 XbGqkJG1RyvL for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 04:30:05 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id E27BD1A036B for <ietf@ietf.org>; Tue, 25 Feb 2014 04:30:04 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.156.84]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1PCTfqX009283 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Feb 2014 04:29:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393331397; bh=cBX5AdZK7lhdaHLReUtK9tGJZsqztYj12GzntS/HQoc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=5DeD3lYs4snaJEbqOoS+yuordf8hU3uEHAnhGK60bkabcac4UfagZti24VgtzrrH8 fGGSZaeHnOp9vPtmX8UvPZBjjtLv0JD0l/vBhWmh3OxlHcYHv8zo4qQ8Gk2T4jat6j QFff68bykJ8DiM6dBUi4LqL859+WEeQO6m4gGitI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393331397; i=@elandsys.com; bh=cBX5AdZK7lhdaHLReUtK9tGJZsqztYj12GzntS/HQoc=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=lp+eODQonSNGl/QPcQ4t1E4IIxeXcf2lJygx3hyFnjl9OP4kogvxHEJAvyOz/NUdQ fNwP3sllSfC2yL6gnmXvZ4kp5DZU7iGKJOue2T9dSfkKHhHJWWdBWgfE/rH8qJlXmE ntUgBlsekCD02Udx9MstNMC5Tm/9t6xL1LuTrkEM=
Message-Id: <6.2.5.6.2.20140225040919.0cd6d138@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 25 Feb 2014 04:20:10 -0800
To: Andrea Glorioso <andrea@digitalpolicy.it>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: IETF Anti-Harassment Procedures
In-Reply-To: <CAOLD2+anwyXiRrS-LVnvKXmSjVjOo1moxG8S8zeETT7Mqfpg4w@mail.g mail.com>
References: <6.2.5.6.2.20140221125316.0b8f6098@elandnews.com> <CAOLD2+aL58jG8NrzDp4yUWDZJmMP=VahwrLkrim_afS84ncEfg@mail.gmail.com> <6.2.5.6.2.20140222080001.0d7a85e0@elandnews.com> <CAOLD2+anwyXiRrS-LVnvKXmSjVjOo1moxG8S8zeETT7Mqfpg4w@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/H7aTeTmjj9onB_LEi_oeoWNIhyY
Cc: Adrian Farrel <adrian@olddog.co.uk>, 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: Tue, 25 Feb 2014 12:30:06 -0000

Hi Andrea,
At 00:57 25-02-2014, Andrea Glorioso wrote:
>What you say makes sense to me, but I do not well enough the general 
>"norms of behaviour" within the IETF to go much beyond in my 
>comments. However, I do not see the logical link between your 
>original statement regarding the nature of law and the way it is 
>used (or not) and your consideration above. This does not invalidate 
>the value of this latest comment of yours, of course.

Ok.

>Not being a lawyer but having studied law and working in an 
>environment where legal procedures are rather important, I honestly 
>do not think it is possible to give a universally valid answer to 
>such a question. It depends on many factors, including (but not 
>limited to) what the applicable law(s) of the applicable 
>jurisdiction(s) say. I understand it is not the purpose of this 
>proposed BCP to become a general compendium of anti-harassment laws. ;)

I smiled as I read the above. :-)

Regards,
S. Moonesamy 


From nobody Tue Feb 25 08:07:24 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 A73131A07AA for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 08:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.348
X-Spam-Level: 
X-Spam-Status: No, score=-3.348 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z2N118W-Pt8Y for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 08:07:21 -0800 (PST)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.0.80]) by ietfa.amsl.com (Postfix) with ESMTP id 2E5F81A011E for <ietf@ietf.org>; Tue, 25 Feb 2014 08:07:21 -0800 (PST)
Received: from dhcp89-089-218.bbn.com ([128.89.89.218]:51216) by smtp.bbn.com with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kent@bbn.com>) id 1WIKXP-000Mnp-Kf; Tue, 25 Feb 2014 11:07:19 -0500
Message-ID: <530CBFB7.90802@bbn.com>
Date: Tue, 25 Feb 2014 11:07:19 -0500
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.3.0
MIME-Version: 1.0
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>,  "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu>
In-Reply-To: <20140224213030.C5E6718C126@mercury.lcs.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lVxrMTlXF9Bq_iI4v0EqyLYxD_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: Tue, 25 Feb 2014 16:07:22 -0000

+1


>      ...
>
> You mean, it's rude to ask what someone's experience is?
>
> If so, that's odd: I myself found it 'bloody rude' (well, actually, I'd use a
> slightly different term, but hey...) for someone to make suggestions on how
> to improve our meeting process when they have really no experience of it.
>
> 	Noel
>
>


From nobody Tue Feb 25 08:30:04 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 E71A61A0110 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 08:30:02 -0800 (PST)
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 D_H2vi5h63Fo for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 08:30:01 -0800 (PST)
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 45ACF1A0077 for <ietf@ietf.org>; Tue, 25 Feb 2014 08:30:01 -0800 (PST)
Received: by mail-la0-f47.google.com with SMTP id y1so2945139lam.20 for <ietf@ietf.org>; Tue, 25 Feb 2014 08:29:59 -0800 (PST)
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=yM6XMysxc19CKAOdM5XM1yFVpMgJUL5Fz4PO48g8xk0=; b=uX71pqJdQUVo0fF2L26IbeAm0V4f910nh44TOsoj3AwOt/Cs5KUjEVXvRLWMtmRxOc lu4CKTFhKxuTXedb6mdPmp5v671n2e2POPkPp03s90LZmsBqr6Ae+chNRdKfqgkbPzfE HP6CQY4tDeJqb9mUNd1+xyXZ+TQuN9yO92A/NyxKbWIxwOsCv+Md4ODC4zc5oEWzjtnw g/m68UFviwFkrqp1XDr3GCSXs06QVwSvGqVWgZ+SVRoE2oHUNSdbMlVFlGVQVPqLerpR O4VaB6g8oSkXLOkqQ9Iwd6QTu0Foeytn37/iv1CBRdbIYj/2QBwIMbqb0yHuXeKZcLhL eYOw==
MIME-Version: 1.0
X-Received: by 10.112.72.40 with SMTP id a8mr357835lbv.68.1393345799621; Tue, 25 Feb 2014 08:29:59 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Tue, 25 Feb 2014 08:29:59 -0800 (PST)
In-Reply-To: <20140224213030.C5E6718C126@mercury.lcs.mit.edu>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu>
Date: Tue, 25 Feb 2014 11:29:59 -0500
Message-ID: <CAMm+Lwg1xZjr7GPbf=WJZz1HMsLpYpZnqNKpwrVsQ1QBJo1VFQ@mail.gmail.com>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Content-Type: multipart/alternative; boundary=001a11c23e2e6f92ed04f33d9948
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/5vtkT_KKCzpp6ADdFiZpSSZiVZI
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: Tue, 25 Feb 2014 16:30:03 -0000

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

On Mon, Feb 24, 2014 at 4:30 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu>wrote:

>
> If so, that's odd: I myself found it 'bloody rude' (well, actually, I'd
> use a
> slightly different term, but hey...) for someone to make suggestions on how
> to improve our meeting process when they have really no experience of it.
>

You are of course free to propose any change you like. But the standard has
always been an opinion and a keyboard.

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

--001a11c23e2e6f92ed04f33d9948
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, Feb 24, 2014 at 4:30 PM, Noel Chiappa <span dir=3D"ltr">&lt;<a href=3D"=
mailto:jnc@mercury.lcs.mit.edu" target=3D"_blank">jnc@mercury.lcs.mit.edu</=
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"><br>
If so, that&#39;s odd: I myself found it &#39;bloody rude&#39; (well, actua=
lly, I&#39;d use a<br>
slightly different term, but hey...) for someone to make suggestions on how=
<br>
to improve our meeting process when they have really no experience of it.<b=
r></blockquote><div><br></div><div>You are of course free to propose any ch=
ange you like. But the standard has always been an opinion and a keyboard.=
=A0</div>
</div><div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">ht=
tp://hallambaker.com/</a><br>
</div></div>

--001a11c23e2e6f92ed04f33d9948--


From nobody Tue Feb 25 08:59:44 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 7CE6A1A00D9 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 08:59:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.251
X-Spam-Level: 
X-Spam-Status: No, score=0.251 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RP_MATCHES_RCVD=-0.547, 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 mqkHUfGMCbHl for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 08:59:41 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 1B76A1A00A3 for <ietf@ietf.org>; Tue, 25 Feb 2014 08:59:41 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P4RNW5PG0G000MXS@mauve.mrochek.com> for ietf@ietf.org; Tue, 25 Feb 2014 08:54:39 -0800 (PST)
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 <01P4RKDV6Y8W00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 25 Feb 2014 08:54:36 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P4RNW46DFQ00004W@mauve.mrochek.com>
Date: Tue, 25 Feb 2014 08:35:57 -0800 (PST)
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
In-reply-to: "Your message dated Tue, 25 Feb 2014 11:07:19 -0500" <530CBFB7.90802@bbn.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com>
To: Stephen Kent <kent@bbn.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0zZ6xMpXlJOH9PzDgUPyrWyF40o
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "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, 25 Feb 2014 16:59:42 -0000

I find myself compelled to agree with both Noel and Kent here. The question may
have been posed offensively - I take no position on that - but in matters
like this past experience is hugely relevant.

Like it or not, not every issue that comes up can be decided on the basis of
crisp technical arguments. (In fact it really seems to me that are less
able to decide things purely on technical merit as time goes on.)

And it's not just internal IETF matters at issue here: If, say, someone makes a
statement about the probable impact of some technical choice on the future
deployment of a protocol, people have every right to know if that statement is
based on past deployment experience or is nothing but guesswork.

And yes, this puts newcomers at something of a disadvantage because of their
lack of experience. And also note that when such questions are asked, the
answers can be disconcerting. You don't know what experience someone has until
you ask, and sometimes you find they have substantive experience that makes
them the expert, not you.

				Ned

> +1


> >      ...
> >
> > You mean, it's rude to ask what someone's experience is?
> >
> > If so, that's odd: I myself found it 'bloody rude' (well, actually, I'd use a
> > slightly different term, but hey...) for someone to make suggestions on how
> > to improve our meeting process when they have really no experience of it.
> >
> > 	Noel
> >
> >


From nobody Tue Feb 25 09:58:06 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 9CCED1A01B3 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 09:57:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.047
X-Spam-Level: 
X-Spam-Status: No, score=-2.047 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id e_C7bcOT6Wv8 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 09:57:53 -0800 (PST)
Received: from mercury.lcs.mit.edu (mercury.lcs.mit.edu [18.26.0.122]) by ietfa.amsl.com (Postfix) with ESMTP id A33D91A0199 for <ietf@ietf.org>; Tue, 25 Feb 2014 09:57:50 -0800 (PST)
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 5521718C139; Tue, 25 Feb 2014 12:57:49 -0500 (EST)
To: ietf@ietf.org
Subject: Re: Ad hominems
Message-Id: <20140225175749.5521718C139@mercury.lcs.mit.edu>
Date: Tue, 25 Feb 2014 12:57:49 -0500 (EST)
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/PVrAQ2s5leSCrGFtA93daT8tFXE
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: Tue, 25 Feb 2014 17:57:59 -0000

    > From: <l.wood@surrey.ac.uk>

    > I'd like to point out that I didn't make an ad hominem argument or
    > assertion.

    > From: Dave Crocker <dcrocker@bbiw.net>

    > The form of your note was not the issue. It was the substance. The
    > substance was directed at a person and was /about/ that person. It's
    > the 'about' that made it ad hominem.

I think there are different thresholds for 'ad hominem' - loosely interpreted
as '_inappropriately_ about the speaker rather than about what they say' -
depending on the area.

For instance, in a purely technical issue (e.g. 'that algorithm scales as
O(<foo>), not O(<bar>), as has been contended'), I think it's pretty clear
that pretty much anything about the questioner is relatively immaterial.
There's an objective 'right' or 'wrong', etc. So the 'ad hominem' threshold
there is pretty low.

On the other hand, for discussions of group governance, I think the person's
experience/knowledge/etc _are_ relevant, because when it comes to managing
human groups, there are no 'right' answers. (Which is why the Law of
Unintended Consequences often comes into play in human governance decisions.)
That kind of information about someone has some real utility in evaluating
their thoughts about such topics, so _some_ questioning is legitimate.

And in these latter case, I suspect there's also a grey area - 'you're an
idiot' is pretty clearly over the line, 'how much experience have you had
running large groups' is probably relevant, and 'how old are you' (as a quick
example off the top of my head, not necessarily the greyest I could come up
with if I spent more time thinking about it) is somewhere in the middle..

	Noel


From nobody Tue Feb 25 10:16:17 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 6E9071A011E for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 10:16:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GsKQfti39qw2 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 10:16:10 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 5E0EF1A013E for <ietf@ietf.org>; Tue, 25 Feb 2014 10:16:10 -0800 (PST)
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 C26C61B80D3 for <ietf@ietf.org>; Tue, 25 Feb 2014 10:16:09 -0800 (PST)
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 BB78F190052; Tue, 25 Feb 2014 10:16:09 -0800 (PST)
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, 25 Feb 2014 10:16:09 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Ad hominems
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140225175749.5521718C139@mercury.lcs.mit.edu>
Date: Tue, 25 Feb 2014 13:16:07 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <39F64491-8D52-4676-9EFE-ACD2F71B42ED@nominum.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
X-Mailer: Apple Mail (2.1827)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/0ku4BXqaFS_zeisrt0kwi9c_KLA
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: Tue, 25 Feb 2014 18:16:14 -0000

On Feb 25, 2014, at 12:57 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu> =
wrote:
> and 'how old are you' (as a quick
> example off the top of my head, not necessarily the greyest I could =
come up
> with if I spent more time thinking about it) is somewhere in the =
middle..

Actually, if you think a bit more about this you might conclude that =
it's not in the middle at all.   It's almost always pejorative, whether =
the implied age is young or old.


From nobody Tue Feb 25 10:48:33 2014
Return-Path: <barryleiba.mailing.lists@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 156D51A0289 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 10:48:28 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, 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 34hQnWIdSe3Q for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 10:48:26 -0800 (PST)
Received: from mail-ve0-x232.google.com (mail-ve0-x232.google.com [IPv6:2607:f8b0:400c:c01::232]) by ietfa.amsl.com (Postfix) with ESMTP id 352A31A0127 for <ietf@ietf.org>; Tue, 25 Feb 2014 10:48:26 -0800 (PST)
Received: by mail-ve0-f178.google.com with SMTP id jy13so928190veb.37 for <ietf@ietf.org>; Tue, 25 Feb 2014 10:48:25 -0800 (PST)
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=Xj4PfWRV/vupTXKvkqBMHGt5v+Hpt1LbWFvOQ2EbHEo=; b=oGSLmM9nalDm09Y6hTrWtU77D48VzSFx25R42lCWsFpjjwr/lt44t9SbhdxdCc8AzM rIR8Ofpm49OiKJOHNCDVjDy1vuK80IdUSmrdDGdtKOUHcgRm1jaav5FJ8ZWykPuRHspa 8I05+59FK3L35muAhIxJxMPFc9gG/SshG1CkppjcgYflSzsWGCp+Lf3vTqE6piPj+rRL x8hsqPpkHfpeuIXFQ5w0H2FN9VxOJyE6iR9G42jXnnlPjDZbdO/IQu/xnYX2LNOe4KxD TAKzua3co9IuxdEOIMyKY6TLPTHLjCvXLwHp4wEDwRCLbGgjBh0ziTpu6K5E1PUJXNLG ZsTA==
MIME-Version: 1.0
X-Received: by 10.221.34.211 with SMTP id st19mr2211561vcb.5.1393354104954; Tue, 25 Feb 2014 10:48:24 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.19.104 with HTTP; Tue, 25 Feb 2014 10:48:24 -0800 (PST)
In-Reply-To: <20140225175749.5521718C139@mercury.lcs.mit.edu>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu>
Date: Tue, 25 Feb 2014 10:48:24 -0800
X-Google-Sender-Auth: zpZRNrAuI5E0cRPDbacjHVOEsWU
Message-ID: <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com>
Subject: Re: Ad hominems
From: Barry Leiba <barryleiba@computer.org>
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/Z3miiAYifWWjAKIB6tOtGEbN9X4
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, 25 Feb 2014 18:48:28 -0000

> On the other hand, for discussions of group governance, I think the person's
> experience/knowledge/etc _are_ relevant, because when it comes to managing
> human groups, there are no 'right' answers. (Which is why the Law of
> Unintended Consequences often comes into play in human governance decisions.)
> That kind of information about someone has some real utility in evaluating
> their thoughts about such topics, so _some_ questioning is legitimate.

I don't dispute that, and there may, indeed, be cases where it's more
relevant.  In this case, it's not.  Leaving names off:

- A suggestion was made that we consider giving each presenter 5
minutes of agenda time.

- One response was given asking what experience with our meetings
gives that person standing to make such a suggestion.

- More than one response was given saying that that, or something very
much like it, had been tried before, and didn't work.

Now, which of those responses was the more useful one?  Which is more
in line with how we prefer to conduct our business?

I personally think that when questioning someone's background or
credentials is, in our environment, useful and appropriate at all,
it's only so as a back-stop, not as a first-order consideration.

Barry


From nobody Tue Feb 25 11:04:54 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 C0A511A01A9 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:04:45 -0800 (PST)
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 80eMqiBX62Dq for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:04:40 -0800 (PST)
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 EDB8D1A01D3 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:04:39 -0800 (PST)
Received: by mail-ob0-f176.google.com with SMTP id wo20so3264971obc.7 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:04:39 -0800 (PST)
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=fy+OM2Qpu7EhDFqYXqZDw6LxjLds/i6RcDTJOh/aGvM=; b=gMsK9kD2QUEtqzWoulHd4IK7tZ/bVKE+ZKOVDotFg/EA2m2X2dKVrd6Q3f2p3UZ9oy ss0Z2DME6iljgNa2nMdwaMh8RTokfYOPYgPAjLc3C7RWxOZBmWgmSfji+bVHJWzVsDIA U19VmSm1lgd08Uz3ivWnTpmGb2Ny1aW56q/b523VztfPsuYpbHJULdlzUbiu7FMYJxnj c719sZIv+WdhjrXJMXDCOJv/vGCVoTvoNJS5Pc0QC55bRlL76BENqnGiwhYXvDkwLBYy sT6pIy9ddLGjUCMB7YzY5FCVTguZXZtLZH1RpoHELQ75ZeLF353WG9D1YdzE4mCsNAT3 Tv3Q==
MIME-Version: 1.0
X-Received: by 10.60.174.77 with SMTP id bq13mr2886021oec.0.1393355078968; Tue, 25 Feb 2014 11:04:38 -0800 (PST)
Received: by 10.182.48.9 with HTTP; Tue, 25 Feb 2014 11:04:38 -0800 (PST)
In-Reply-To: <01P4RNW46DFQ00004W@mauve.mrochek.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com>
Date: Tue, 25 Feb 2014 14:04:38 -0500
Message-ID: <CAPv4CP8c90LRtbS4n6SkfObhVa3W5Ld9nWWjUwVxAhesTNGjcQ@mail.gmail.com>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
From: Scott Brim <scott.brim@gmail.com>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Content-Type: multipart/alternative; boundary=089e011825f8872bff04f33fc202
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/wBSTeNKoMLtjlXjy5VNqA82bwss
Cc: "ietf@ietf.org" <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: Tue, 25 Feb 2014 19:04:46 -0000

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

Yes, there are often cases where experience and proven judgment matter
tremendously, but in this case the question was resolved _more_ simply by a
factual response, even without taking into account the original proposer's
experience level.

Scott

On Tuesday, February 25, 2014, <ned+ietf@mauve.mrochek.com> wrote:

> I find myself compelled to agree with both Noel and Kent here. The
> question may
> have been posed offensively - I take no position on that - but in matters
> like this past experience is hugely relevant.
>
> Like it or not, not every issue that comes up can be decided on the basis
> of
> crisp technical arguments. (In fact it really seems to me that are less
> able to decide things purely on technical merit as time goes on.)
>
> And it's not just internal IETF matters at issue here: If, say, someone
> makes a
> statement about the probable impact of some technical choice on the future
> deployment of a protocol, people have every right to know if that
> statement is
> based on past deployment experience or is nothing but guesswork.
>
> And yes, this puts newcomers at something of a disadvantage because of
> their
> lack of experience. And also note that when such questions are asked, the
> answers can be disconcerting. You don't know what experience someone has
> until
> you ask, and sometimes you find they have substantive experience that makes
> them the expert, not you.
>
>                                 Ned
>
>  +1
>>
>
>
>  >      ...
>> >
>> > You mean, it's rude to ask what someone's experience is?
>> >
>> > If so, that's odd: I myself found it 'bloody rude' (well, actually, I'd
>> use a
>> > slightly different term, but hey...) for someone to make suggestions on
>> how
>> > to improve our meeting process when they have really no experience of
>> it.
>> >
>> >       Noel
>> >
>> >
>>
>
>

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

Yes, there are often cases where experience and proven judgment matter trem=
endously, but in this case the question was resolved _more_ simply by a fac=
tual response, even without taking into account the original proposer&#39;s=
 experience level. =A0<div>
<br></div><div>Scott<br><br>On Tuesday, February 25, 2014,  &lt;<a href=3D"=
mailto:ned%2Bietf@mauve.mrochek.com">ned+ietf@mauve.mrochek.com</a>&gt; wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">
I find myself compelled to agree with both Noel and Kent here. The question=
 may<br>
have been posed offensively - I take no position on that - but in matters<b=
r>
like this past experience is hugely relevant.<br>
<br>
Like it or not, not every issue that comes up can be decided on the basis o=
f<br>
crisp technical arguments. (In fact it really seems to me that are less<br>
able to decide things purely on technical merit as time goes on.)<br>
<br>
And it&#39;s not just internal IETF matters at issue here: If, say, someone=
 makes a<br>
statement about the probable impact of some technical choice on the future<=
br>
deployment of a protocol, people have every right to know if that statement=
 is<br>
based on past deployment experience or is nothing but guesswork.<br>
<br>
And yes, this puts newcomers at something of a disadvantage because of thei=
r<br>
lack of experience. And also note that when such questions are asked, the<b=
r>
answers can be disconcerting. You don&#39;t know what experience someone ha=
s until<br>
you ask, and sometimes you find they have substantive experience that makes=
<br>
them the expert, not you.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Ned<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
+1<br>
</blockquote>
<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
&gt; =A0 =A0 =A0...<br>
&gt;<br>
&gt; You mean, it&#39;s rude to ask what someone&#39;s experience is?<br>
&gt;<br>
&gt; If so, that&#39;s odd: I myself found it &#39;bloody rude&#39; (well, =
actually, I&#39;d use a<br>
&gt; slightly different term, but hey...) for someone to make suggestions o=
n how<br>
&gt; to improve our meeting process when they have really no experience of =
it.<br>
&gt;<br>
&gt; =A0 =A0 =A0 Noel<br>
&gt;<br>
&gt;<br>
</blockquote>
<br>
</blockquote></div>

--089e011825f8872bff04f33fc202--


From nobody Tue Feb 25 11:22:39 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 8EFF11A019C for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:22:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.702
X-Spam-Level: 
X-Spam-Status: No, score=0.702 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, LOTS_OF_MONEY=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 DimzzohdMN4C for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:22:30 -0800 (PST)
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 78B911A0199 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:22:30 -0800 (PST)
Received: by mail-lb0-f172.google.com with SMTP id c11so971758lbj.17 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:22:28 -0800 (PST)
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=C6kA3K4WWZCH6axCoQW+oBs2EqeBW6LOlOJmiSJKeR4=; b=mBjGEvfRgwPMzUDuDcfLhK8M40SagpggzIUiRuuNebD8UzFSy6L6mtuauTlgK8KXOM k51qWOvN9jNGj8yHTAU0qgo2jRjxxsPuy/XSSjYw6rpe02TY+SLeS4AGIZ9mvpzrAAHw w9kJmYBuGwtE/IsnpyH5kONxJk/5+I+1/Bfx2eb/Z34/5MqMyE5Sa6VuA6VaF3AyGHhx 94Qb2+9rxsff0tS1P7xnNXge5nJu+VAFNgJ8toIP0xsqNrRae1zMQsf1+3cg6SHNU6Wk XHQezw3XPdi/pMO0eT/9Kzg2aCcdL9xkpeSGneXW0Cq7H4PGSjFQ2mSotE30n9QE3F83 YnUQ==
MIME-Version: 1.0
X-Received: by 10.112.138.233 with SMTP id qt9mr814890lbb.34.1393356148775; Tue, 25 Feb 2014 11:22:28 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Tue, 25 Feb 2014 11:22:28 -0800 (PST)
In-Reply-To: <39F64491-8D52-4676-9EFE-ACD2F71B42ED@nominum.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <39F64491-8D52-4676-9EFE-ACD2F71B42ED@nominum.com>
Date: Tue, 25 Feb 2014 14:22:28 -0500
Message-ID: <CAMm+LwitXTjjggPs6RHhgCuZU4ogiGUeW2HPp=Y5a_R4bdbamw@mail.gmail.com>
Subject: Re: Ad hominems
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=089e012297104b277c04f34002d0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7O71Wg2VRoxfgRMWN2lBK3NVk_g
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "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: Tue, 25 Feb 2014 19:22:33 -0000

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

On Tue, Feb 25, 2014 at 1:16 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Feb 25, 2014, at 12:57 PM, Noel Chiappa <jnc@mercury.lcs.mit.edu>
> wrote:
> > and 'how old are you' (as a quick
> > example off the top of my head, not necessarily the greyest I could come
> up
> > with if I spent more time thinking about it) is somewhere in the middle..
>
> Actually, if you think a bit more about this you might conclude that it's
> not in the middle at all.   It's almost always pejorative, whether the
> implied age is young or old.
>

Well one of the points I am about to make in my next podcast on BitCoin is
that the reason BitCoiners with technical chops tend to have a median age
of about 27 is that the older generation of crypto types have seen it all
before in Gold Age, eGold, Liberty Reserve etc.

But in that case it is making a point to a group that is running round
making the claim that their scheme is the future of finance because it is
new. So pointing out that it is e-Gold with 'blockchain' for 'bearer' is
rather relevant.


As Barry points out in his post, it all depends on context. The problem
here was that the poster raised a reasonable point and the first response
was rude and exclusionary and not backed up by any substance. In the right
circumstances 'well we tried that and it failed in Kobe' might be a
relevant argument. But 'who the hell are you to ask' is not a reasonable
response to an initial suggestion made in a reasonable manner.

There are cases where rudeness is justified and necessary. When a group is
running round burning $20 million worth of electricity a month and mouthing
off about how everyone who doesn't believe in their scheme is an idiot,
then its time to take the gloves off. Rude or not, when $350 million of a
total float of $7 billion is alleged to be missing due to one bank that
might have failed, anyone who does not understand the jig is up is going to
be calling themselves things far worse than stupid in a short time.

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

--089e012297104b277c04f34002d0
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 T=
ue, Feb 25, 2014 at 1:16 PM, Ted Lemon <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:ted.lemon@nominum.com" target=3D"_blank">ted.lemon@nominum.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"">On Feb 25, 2014, at 12:57 PM=
, Noel Chiappa &lt;<a href=3D"mailto:jnc@mercury.lcs.mit.edu">jnc@mercury.l=
cs.mit.edu</a>&gt; wrote:<br>

&gt; and &#39;how old are you&#39; (as a quick<br>
&gt; example off the top of my head, not necessarily the greyest I could co=
me up<br>
&gt; with if I spent more time thinking about it) is somewhere in the middl=
e..<br>
<br>
</div>Actually, if you think a bit more about this you might conclude that =
it&#39;s not in the middle at all. =A0 It&#39;s almost always pejorative, w=
hether the implied age is young or old.<br></blockquote><div><br></div><div=
>
Well one of the points I am about to make in my next podcast on BitCoin is =
that the reason BitCoiners with technical chops tend to have a median age o=
f about 27 is that the older generation of crypto types have seen it all be=
fore in Gold Age, eGold, Liberty Reserve etc.</div>
<div><br></div><div>But in that case it is making a point to a group that i=
s running round making the claim that their scheme is the future of finance=
 because it is new. So pointing out that it is e-Gold with &#39;blockchain&=
#39; for &#39;bearer&#39; is rather relevant.</div>
<div><br></div><div><br></div><div>As Barry points out in his post, it all =
depends on context. The problem here was that the poster raised a reasonabl=
e point and the first response was rude and exclusionary and not backed up =
by any substance. In the right circumstances &#39;well we tried that and it=
 failed in Kobe&#39; might be a relevant argument. But &#39;who the hell ar=
e you to ask&#39; is not a reasonable response to an initial suggestion mad=
e in a reasonable manner.</div>
</div><div class=3D"gmail_extra"><br></div>There are cases where rudeness i=
s justified and necessary. When a group is running round burning $20 millio=
n worth of electricity a month and mouthing off about how everyone who does=
n&#39;t believe in their scheme is an idiot, then its time to take the glov=
es off. Rude or not, when $350 million of a total float of $7 billion is al=
leged to be missing due to one bank that might have failed, anyone who does=
 not understand the jig is up is going to be calling themselves things far =
worse than stupid in a short time.<br clear=3D"all">
<div><br></div>-- <br>Website: <a href=3D"http://hallambaker.com/">http://h=
allambaker.com/</a><br>
</div></div>

--089e012297104b277c04f34002d0--


From nobody Tue Feb 25 11:24:00 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 9FE121A00B1 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:23:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.148
X-Spam-Level: 
X-Spam-Status: No, score=-8.148 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.547, 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 MxULEn3q94ch for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:23:56 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) by ietfa.amsl.com (Postfix) with ESMTP id E5B961A01D3 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:23:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3875; q=dns/txt; s=iport; t=1393356228; x=1394565828; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to; bh=dxa/KJk+Q+dDzDvLzogzftCZ2PPSyUE38rblFqqHPGE=; b=MatqLwrGqIrM1rg01dyKsPuimMIvRtYXSh2+05FOBFP4Z2Ghv7uCTdl/ ehT9P+Q2BYBzqoPtWLWE83wM2mseyE86zySNmdM4ENSncG3nfbR1w2BTq Tr4ild1hIWNtvXIvy+fUMY12yMO+rLqSPx9wqsztAzAFHYOKx0tMd7hC/ U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhgFAKDsDFOQ/khM/2dsb2JhbABZDoJ4iXK1Z4MJgRkWdIIlAQEBBHgBEAsEFAkWDwkDAgECAUUGAQwBBwEBiAHIIheNbgsDAwFQB4Q4BJg2kiiCbj+BaQgX
X-IronPort-AV: E=Sophos;i="4.97,541,1389744000"; d="scan'208,217";a="6112320"
Received: from ams-core-3.cisco.com ([144.254.72.76]) by aer-iport-1.cisco.com with ESMTP; 25 Feb 2014 19:23:47 +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 s1PJNjx0031739 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Feb 2014 19:23:46 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s1PJNgZ6004207; Tue, 25 Feb 2014 19:23:44 GMT
Message-ID: <530CEDBE.7080609@cisco.com>
Date: Tue, 25 Feb 2014 19:23:42 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Barry Leiba <barryleiba@computer.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Ad hominems
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com>
In-Reply-To: <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------060305020208060306090707"
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WbpzjNOREAR4PFYiNkG7p2R6XpY
Cc: IETF discussion list <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: Tue, 25 Feb 2014 19:23:58 -0000

This is a multi-part message in MIME format.
--------------060305020208060306090707
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 25/02/2014 18:48, Barry Leiba wrote:
>> On the other hand, for discussions of group governance, I think the person's
>> experience/knowledge/etc _are_ relevant, because when it comes to managing
>> human groups, there are no 'right' answers. (Which is why the Law of
>> Unintended Consequences often comes into play in human governance decisions.)
>> That kind of information about someone has some real utility in evaluating
>> their thoughts about such topics, so _some_ questioning is legitimate.
> I don't dispute that, and there may, indeed, be cases where it's more
> relevant.  In this case, it's not.  Leaving names off:
>
> - A suggestion was made that we consider giving each presenter 5
> minutes of agenda time.
Let's look at the text that started this discussion:

"Dear IETF WGs' Chairs,

"I suggest in London that you assign only maximum 10 minutes
present per WG draft and maximum 5 minute for individual draft
(as limit policy). We need to use more input and have more face2face
(F2F) discussion in our meeting. I remember we discussed this before
...."

Although that text started with the word "suggestion", the
text construction is that of an instruction.

When I saw Lloyd's email my first thought  was Francis Urquhart's
catchphrase, and I suspect that I might not have been alone.

Stewart






--------------060305020208060306090707
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 25/02/2014 18:48, Barry Leiba wrote:<br>
    </div>
    <blockquote
cite="mid:CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com"
      type="cite">
      <blockquote type="cite">
        <pre wrap="">On the other hand, for discussions of group governance, I think the person's
experience/knowledge/etc _are_ relevant, because when it comes to managing
human groups, there are no 'right' answers. (Which is why the Law of
Unintended Consequences often comes into play in human governance decisions.)
That kind of information about someone has some real utility in evaluating
their thoughts about such topics, so _some_ questioning is legitimate.
</pre>
      </blockquote>
      <pre wrap="">
I don't dispute that, and there may, indeed, be cases where it's more
relevant.  In this case, it's not.  Leaving names off:

- A suggestion was made that we consider giving each presenter 5
minutes of agenda time.
</pre>
    </blockquote>
    Let's look at the text that started this discussion:<br>
    <br>
    "Dear IETF WGs' Chairs,
    <div><br>
    </div>
    <div>"I suggest in London&nbsp;that you assign only maximum 10 minutes <br>
      present per WG draft and maximum 5 minute for individual draft <br>
      (as limit policy).&nbsp;We need to use more input and have more
      face2face <br>
      (F2F)&nbsp;discussion in our meeting. I remember we discussed this
      before<br>
      ...."<br>
      <br>
      Although that text started with the word "suggestion", the<br>
      text construction is that of an instruction.<br>
      <br>
      When I saw Lloyd's email my first thought&nbsp; was
      <meta http-equiv="content-type" content="text/html;
        charset=ISO-8859-1">
      Francis Urquhart's <br>
      catchphrase, and I suspect that I might not have been alone.<br>
      <br>
      Stewart<br>
      <br>
      <br>
      <br>
      <br>
    </div>
    <br>
  </body>
</html>

--------------060305020208060306090707--


From nobody Tue Feb 25 11:31:56 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 D6C4B1A01F4 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:31:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.851
X-Spam-Level: 
X-Spam-Status: No, score=0.851 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_42=0.6, RP_MATCHES_RCVD=-0.547, 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 VdJczS7IJWV5 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:31:48 -0800 (PST)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.59.230.40]) by ietfa.amsl.com (Postfix) with ESMTP id 045551A0186 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:31:48 -0800 (PST)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P4RT7QYXTC000OJR@mauve.mrochek.com> for ietf@ietf.org; Tue, 25 Feb 2014 11:26:46 -0800 (PST)
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 <01P4RO1R2MDS00004W@mauve.mrochek.com> (original mail from NED@mauve.mrochek.com) for ietf@ietf.org; Tue, 25 Feb 2014 11:26:43 -0800 (PST)
From: ned+ietf@mauve.mrochek.com
Message-id: <01P4RT7PU2OC00004W@mauve.mrochek.com>
Date: Tue, 25 Feb 2014 11:09:14 -0800 (PST)
Subject: Re: Ad hominems
In-reply-to: "Your message dated Tue, 25 Feb 2014 10:48:24 -0800" <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_WU5UGUjDDdB0ZJ0T_TlEjviWKs
Cc: Noel Chiappa <jnc@mercury.lcs.mit.edu>, 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, 25 Feb 2014 19:31:50 -0000

> > On the other hand, for discussions of group governance, I think the person's
> > experience/knowledge/etc _are_ relevant, because when it comes to managing
> > human groups, there are no 'right' answers. (Which is why the Law of
> > Unintended Consequences often comes into play in human governance decisions.)
> > That kind of information about someone has some real utility in evaluating
> > their thoughts about such topics, so _some_ questioning is legitimate.

> I don't dispute that, and there may, indeed, be cases where it's more
> relevant.  In this case, it's not.  Leaving names off:

> - A suggestion was made that we consider giving each presenter 5
> minutes of agenda time.

> - One response was given asking what experience with our meetings
> gives that person standing to make such a suggestion.

> - More than one response was given saying that that, or something very
> much like it, had been tried before, and didn't work.

> Now, which of those responses was the more useful one?

The answer is we really can't tell, because the discussion was meta'ed before
the question could be answered.

Speaking for myself, I have no idea what that answer would have been. My
impression is that the original suggestion came from someone  who doesn't have
substantive IETF experience, but for all I know they may have substantive and
directly relevant experience in some other venue. And if that were indeed the
case, isn't it possible that "running code" from somewhere else would be
helpful in addressing this perennial and vexing issue?

> Which is more
> in line with how we prefer to conduct our business?

Again, I take no position on whether or not the question was asked in an 
offensive fashion or not. But the way I would prefer to conduct our business is
that substance trumps form. And to my mind the underlying question *was*
relevant.

> I personally think that when questioning someone's background or
> credentials is, in our environment, useful and appropriate at all,
> it's only so as a back-stop, not as a first-order consideration.

And as I stated previously, I strongly disagree. I think background and
experience are often highly relevant to a wide variety of discussions, both
technical and procedural, we seem to be having these days.

It's also the case that people with relevant knowledge and experience often
neglect to point that out. And not everyone knows everyone's antecedants. (This
is the other side of the Dunning-Kruger effect coming into play.) For example,
I have on several occasions been accused of engaging in mindreading when I
averred as to what the intentions behind various parts of MIME were at the time
it was written.

				Ned


From nobody Tue Feb 25 11:40:42 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 A88A61A01FC for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:40:34 -0800 (PST)
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 5TIy17eKKOf3 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:40:31 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0FB6A1A01F3 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:40:31 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1PJeKB5020755 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Feb 2014 11:40:23 -0800
Message-ID: <530CF16B.8070703@dcrocker.net>
Date: Tue, 25 Feb 2014 11:39:23 -0800
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.3.0
MIME-Version: 1.0
To: stbryant@cisco.com, Barry Leiba <barryleiba@computer.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Ad hominems
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com>
In-Reply-To: <530CEDBE.7080609@cisco.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, 25 Feb 2014 11:40:24 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/67445sERcBTNFoTLnkTNpfOzWtU
Cc: IETF discussion list <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, 25 Feb 2014 19:40:34 -0000

On 2/25/2014 11:23 AM, Stewart Bryant wrote:
> "I suggest in London that you assign only maximum 10 minutes
> present per WG draft and maximum 5 minute for individual draft
> (as limit policy). We need to use more input and have more face2face
> (F2F) discussion in our meeting. I remember we discussed this before
> ...."
>
> Although that text started with the word "suggestion", the
> text construction is that of an instruction.


Instruction?  Huh?  That characterization warrants careful explanation. 
  Please provide it.

The note 1) made a suggestion, and 2) Stated a need.  It implied that 
implementing the change would remedy the need.

What part of that qualifies as "instruction" rather than, for example, 
explanation?

There was nothing tutorial, parental or authoritative in the note making 
the suggestion.  Everything focusing on background and presence or lack 
of expertise was introduced by others, in response.  Hence, ad hominem.

d/


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Feb 25 11:41:20 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 D98DF1A022D for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:41:18 -0800 (PST)
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 6K5mnbzdMhIg for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:41:15 -0800 (PST)
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 C651F1A0228 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:41:15 -0800 (PST)
Received: by mail-pd0-f174.google.com with SMTP id y13so3374298pdi.5 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:41:14 -0800 (PST)
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=JpG2P8GL5IxaYDaJBUmPBSlGZx3J74aFhW2a6PzGSaM=; b=0421r5Tnb+lYfgA7pT0dRzFp1EYyvJSAxxJjNpqScfVXjoK1O+vW3cWXPgeRr73rce D5NH8H7G7Xh3om5RIKkD63rx2Syx+85YJkvkRpx1gxR6w7irg+hf/0MGJQ59NJWM5s2I nHXOh5SDBSK7rb+q9b9d9lx6xapzN8lljl+FWAp1DU0kfDBKZMNtFZe3t/Ngz8CA9NSi rRENBweUQzwLjCxouGuCVLqBu9BuDZvOleHUavDCcGFI2SLzkDW4NVZxrjdDLa2gvM3o 2a+Ye/77YMp5rrGvExVgk9SkQtcqvXWSXyNlCU6Lw8sGguLPk7WVTlGWFP5DTTzv8oSq PMxw==
X-Received: by 10.66.141.197 with SMTP id rq5mr3664958pab.64.1393357274906; Tue, 25 Feb 2014 11:41:14 -0800 (PST)
Received: from spandex.local (63-140-68-38-rb2.sol.dsl.dynamic.acsalaska.net. [63.140.68.38]) by mx.google.com with ESMTPSA id pe3sm13350411pbc.23.2014.02.25.11.41.13 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Feb 2014 11:41:14 -0800 (PST)
Message-ID: <530CF1D6.7040000@gmail.com>
Date: Tue, 25 Feb 2014 10:41:10 -0900
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: Ad hominems
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <01P4RT7PU2OC00004W@mauve.mrochek.com>
In-Reply-To: <01P4RT7PU2OC00004W@mauve.mrochek.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/n9rv4r-tz8n9ndZzi1MRUPVeSog
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Feb 2014 19:41:19 -0000

On 2/25/14 10:09 AM, ned+ietf@mauve.mrochek.com wrote:
> Again, I take no position on whether or not the question was asked in an 
> offensive fashion or not. But the way I would prefer to conduct our business is
> that substance trumps form. And to my mind the underlying question *was*
> relevant.

I thought that there was a non-negligible possibility that the
intent was to be disruptive (mission accomplished).  Given the
size of the mailing list and the number of IETF participants it's
not very likely that every single person will just let it go.

To be honest I have no idea how to deal with intent here and
tend to think the fairest thing is to not deal with it to the
extent possible (can't always ignore it [for example, the descent
of EFF members on the IETF during the TLS authz discussions],
but I think you usually can).  I thought Lloyd should have
ignored it but he didn't, and it seems pretty clear to me
that if someone does care about intent, context and history
matter a very great deal.

Melinda


From nobody Tue Feb 25 11:52: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 DF3A21A0741 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:52:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.447
X-Spam-Level: 
X-Spam-Status: No, score=-0.447 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jh2xlWKQmkGP for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 11:52:32 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id B9FED1A06E8 for <ietf@ietf.org>; Tue, 25 Feb 2014 11:52:32 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WIO3L-000I7R-LB; Tue, 25 Feb 2014 14:52:31 -0500
Date: Tue, 25 Feb 2014 14:52:11 -0500
From: John C Klensin <john-ietf@jck.com>
To: ned+ietf@mauve.mrochek.com
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Message-ID: <3FF3186251572A0DB04C2762@JcK-HP8200.jck.com>
In-Reply-To: <01P4RNW46DFQ00004W@mauve.mrochek.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Y0sZWt6pl8dlBzNTHAkzJ8g7NmI
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, 25 Feb 2014 19:52:35 -0000

--On Tuesday, February 25, 2014 08:35 -0800
ned+ietf@mauve.mrochek.com wrote:

> I find myself compelled to agree with both Noel and Kent here.
> The question may
> have been posed offensively - I take no position on that - but
> in matters
> like this past experience is hugely relevant.
>...

Borrowing a note from Ned's comments, I am honesty confused by
those who think Lloyd's question was inappropriate.  I hope we
can, at least temporarily, ignore both the tone some of us have
read into that question and whether it meets the criteria for ad
hominem argumentation or not.  

So, for those who think the question was inappropriate, a
comparative question about the following two entirely
hypothetical cases:

 Case 1: You have proposed a change to the way IETF
	operates its meetings and have asserted that your change
	would help things work much better.  Can you explain the
	experience you have had with those meetings on which you
	base your suggestion so it can help us evaluate whether
	to take it seriously?
	
 Case 2: You have asserted that a protocol feature being
	reviewed in a WG does not work.  Have you implemented
	and tested it and, if not, on what basis do you make
	that assertion?

I suggest that, if the second question is considered
inappropriate and prohibited, we are in big trouble.  I hope
there is general agreement on that subject.  But I'm having
trouble understanding why the two questions are different:  both
ask about experience and the basis for the suggestion or
comment.  If there is a difference, would someone please explain
it?

    john






From nobody Tue Feb 25 12:06:25 2014
Return-Path: <barryleiba.mailing.lists@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 5E1C41A037A for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 12:06:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.621
X-Spam-Level: 
X-Spam-Status: No, score=0.621 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, 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 ztAaZxVAkTJu for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 12:06:19 -0800 (PST)
Received: from mail-ve0-x233.google.com (mail-ve0-x233.google.com [IPv6:2607:f8b0:400c:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 3ACB81A01E1 for <ietf@ietf.org>; Tue, 25 Feb 2014 12:06:19 -0800 (PST)
Received: by mail-ve0-f179.google.com with SMTP id oz11so1045364veb.24 for <ietf@ietf.org>; Tue, 25 Feb 2014 12:06:18 -0800 (PST)
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=NhLos1EtPjT6JSx+x1f1ifMnCqgK3LMc1D0XAR13sG0=; b=Jj9K07cHCfFyIjiHqSEf5pOXtbBZ19t9sPNcSGVruuJao4uNdgcy9DI3O8WDoaw8JB Ka5KYMHGopkM451xDkTdbryl8AEQ3b4F8Cnyy0rIHrY+CvI17GqzmatKB8au8jln4ZSA KzVWmMrSlnhwAArHP+q6E637q/5m1nmWvh6YevF0E7DGpZo4ArIqZG6KXJGtJh2GQTbh J8w0ErdBw7fMjoBPw+buskyI1Gtg56BKVtWKwVnxUW2rW/PTg4ZbQ4sbHsAkoKcEOPyf dBMkyI7MPGtZL+6YJnuX2o1X5UutjJ5s2yK/xtz3KsZPGRd0yCwqYpRahA1UFd3iEJ/+ yKXw==
MIME-Version: 1.0
X-Received: by 10.220.133.80 with SMTP id e16mr2480608vct.13.1393358778032; Tue, 25 Feb 2014 12:06:18 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.19.104 with HTTP; Tue, 25 Feb 2014 12:06:17 -0800 (PST)
In-Reply-To: <3FF3186251572A0DB04C2762@JcK-HP8200.jck.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com> <3FF3186251572A0DB04C2762@JcK-HP8200.jck.com>
Date: Tue, 25 Feb 2014 12:06:17 -0800
X-Google-Sender-Auth: ChEqEUalXWzm6kuBRSkfRSHlvNo
Message-ID: <CAC4RtVBcx6K4=O3nUCRqz=r_5nAsYzsuQoMJiYLmKyX6DPWiZw@mail.gmail.com>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
From: Barry Leiba <barryleiba@computer.org>
To: John C Klensin <john-ietf@jck.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aQ8oAfmI9Y5BQX_4bOeVXxr01Ow
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, 25 Feb 2014 20:06:20 -0000

>  Case 2: You have asserted that a protocol feature being
>         reviewed in a WG does not work.  Have you implemented
>         and tested it and, if not, on what basis do you make
>         that assertion?
>
> I suggest that, if the second question is considered
> inappropriate and prohibited, we are in big trouble.  I hope
> there is general agreement on that subject.  But I'm having
> trouble understanding why the two questions are different

The second question is not appropriate *as the first response*.

If someone should asset that a protocol feature won't work, they
should say why -- they should give a technical assessment that backs
their assertion.  If they don't, requesting *that* should be our first
response.

There's a point in the conversation when, yes, it is absolutely
appropriate to ask what background they have and what testing they've
actually done that supports their argument.  But someone who has never
written a line of code can still find a technical flaw, and it's the
technical argument that we should consider first.

Barry


From nobody Tue Feb 25 12:12: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 E9CB91A01EA for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 12:12:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.149
X-Spam-Level: 
X-Spam-Status: No, score=-8.149 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.547, 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 Lldd_dMLHss2 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 12:12:28 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) by ietfa.amsl.com (Postfix) with ESMTP id 3C84A1A0157 for <ietf@ietf.org>; Tue, 25 Feb 2014 12:12:28 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2030; q=dns/txt; s=iport; t=1393359147; x=1394568747; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=n0GrtADLIWVk/aVUQ53blcIzQPDsXQoTP12711K78Ek=; b=fYQrPO/IvjOn3BGoIb+GtCj0YfUk+zkYCaFYirW6FxTISTnGCgwF4b93 YwoHj4WvNMiD3zGGvZOvWDCBiTR0aGiGdAhGk37ByQKSH31ZDZJl0keqo 8/Nkom6/Nki8dD6uYL6G5bEPaCO1yOgSwPIbGQKn8Hfl5mKVk1jXbgkvQ A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhQFAC34DFOQ/khR/2dsb2JhbABZDoJ4v1mDCYEZFnSCJQEBAQQ4Mw0BEAsYCRYPCQMCAQIBRQYBDAEHAQGIAcgwF415A1QHhDgBA5g2kiiCbj+BaQ
X-IronPort-AV: E=Sophos;i="4.97,541,1389744000";  d="scan'208";a="1361286"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by aer-iport-3.cisco.com with ESMTP; 25 Feb 2014 20:12:26 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s1PKCQAE025965 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Feb 2014 20:12:26 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id s1PKCNK5005949; Tue, 25 Feb 2014 20:12:24 GMT
Message-ID: <530CF927.4080203@cisco.com>
Date: Tue, 25 Feb 2014 20:12:23 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: dcrocker@bbiw.net, Barry Leiba <barryleiba@computer.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: Re: Ad hominems
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net>
In-Reply-To: <530CF16B.8070703@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/lRAj5S64v6-0W7MOUKYCeDb--t0
Cc: IETF discussion list <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: Tue, 25 Feb 2014 20:12:33 -0000

On 25/02/2014 19:39, Dave Crocker wrote:
> On 2/25/2014 11:23 AM, Stewart Bryant wrote:
>> "I suggest in London that you assign only maximum 10 minutes
>> present per WG draft and maximum 5 minute for individual draft
>> (as limit policy). We need to use more input and have more face2face
>> (F2F) discussion in our meeting. I remember we discussed this before
>> ...."
>>
>> Although that text started with the word "suggestion", the
>> text construction is that of an instruction.
>
>
> Instruction?  Huh?  That characterization warrants careful 
> explanation.  Please provide it.
>
> The note 1) made a suggestion, and 2) Stated a need.  It implied that 
> implementing the change would remedy the need.
>
> What part of that qualifies as "instruction" rather than, for example, 
> explanation?
>
> There was nothing tutorial, parental or authoritative in the note 
> making the suggestion.  Everything focusing on background and presence 
> or lack of expertise was introduced by others, in response.  Hence, ad 
> hominem.
>
> d/

Dave

First, please can I request that you take a less harassing approach to
this discussion.

I explained how I interpreted that that text when I first read it.
That was a personal interpretation of the text on first reading,
and as such requires no further explanation.

As to the later context concerning the original posters remarks:
I was already fully aware that London would be their first F2F
meeting when I read the OP, and I am fairly confident that
Lloyd also had that context before he posted.

So, please consider that

1) There was widely shared prior context in the early
discussion.

2) That everyone sees text though their personal lenses
coloured by both experience and context and will interpret
it accordingly.

In the case of this text construct itself, I read it as an instruction
because that is the style of text I might have written if I were
issuing an instruction to the RTG WG Chairs as their AD.

- Stewart








From nobody Tue Feb 25 12:23:05 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 649FA1A076C for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 12:22:59 -0800 (PST)
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 gGU37_XBZzyQ for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 12:22:55 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.161]) by ietfa.amsl.com (Postfix) with ESMTP id E34271A072E for <ietf@ietf.org>; Tue, 25 Feb 2014 12:22:54 -0800 (PST)
Received: from [195.245.230.131:13175] by server-1.bemta-3.messagelabs.com id A2/37-17293-D9BFC035; Tue, 25 Feb 2014 20:22:53 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-5.tower-78.messagelabs.com!1393359772!31656375!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 31309 invoked from network); 25 Feb 2014 20:22:52 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-5.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 25 Feb 2014 20:22:52 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT012P.surrey.ac.uk ([131.227.200.39]) with mapi; Tue, 25 Feb 2014 20:22:52 +0000
From: <l.wood@surrey.ac.uk>
To: <dcrocker@bbiw.net>, <stbryant@cisco.com>, <barryleiba@computer.org>, <jnc@mercury.lcs.mit.edu>
Date: Tue, 25 Feb 2014 20:22:14 +0000
Subject: RE: Ad hominems
Thread-Topic: Ad hominems
Thread-Index: Ac8yYpX/UnTimQbGSUiFtWIuTBAmeQABK+xI
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334735@EXMB01CMS.surrey.ac.uk>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com>,<530CF16B.8070703@dcrocker.net>
In-Reply-To: <530CF16B.8070703@dcrocker.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/kcLaUJ_FftJQzBfm5NCGjgpK058
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, 25 Feb 2014 20:22:59 -0000

> There was nothing tutorial, parental or authoritative in the note
> making the suggestion.=20

because there wasn't a MUST or a SHOULD in it?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Dave Crocker [dhc@dcrocker.=
net]
Sent: 25 February 2014 19:39
To: stbryant@cisco.com; Barry Leiba; Noel Chiappa
Cc: IETF discussion list
Subject: Re: Ad hominems

On 2/25/2014 11:23 AM, Stewart Bryant wrote:
> "I suggest in London that you assign only maximum 10 minutes
> present per WG draft and maximum 5 minute for individual draft
> (as limit policy). We need to use more input and have more face2face
> (F2F) discussion in our meeting. I remember we discussed this before
> ...."
>
> Although that text started with the word "suggestion", the
> text construction is that of an instruction.


Instruction?  Huh?  That characterization warrants careful explanation.
  Please provide it.

The note 1) made a suggestion, and 2) Stated a need.  It implied that
implementing the change would remedy the need.

What part of that qualifies as "instruction" rather than, for example,
explanation?

There was nothing tutorial, parental or authoritative in the note making
the suggestion.  Everything focusing on background and presence or lack
of expertise was introduced by others, in response.  Hence, ad hominem.

d/


--
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Feb 25 12:34:54 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 5C5741A0198 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 12:34:47 -0800 (PST)
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 YP-PkbeWpNpB for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 12:34:43 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.147]) by ietfa.amsl.com (Postfix) with ESMTP id E033E1A0131 for <ietf@ietf.org>; Tue, 25 Feb 2014 12:34:42 -0800 (PST)
Received: from [195.245.231.67:63147] by server-11.bemta-5.messagelabs.com id 29/61-23886-16EFC035; Tue, 25 Feb 2014 20:34:41 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-3.tower-82.messagelabs.com!1393360478!32020362!2
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 28043 invoked from network); 25 Feb 2014 20:34:40 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-3.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 25 Feb 2014 20:34:40 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Tue, 25 Feb 2014 20:34:37 +0000
From: <l.wood@surrey.ac.uk>
To: <stbryant@cisco.com>, <dcrocker@bbiw.net>, <barryleiba@computer.org>, <jnc@mercury.lcs.mit.edu>
Date: Tue, 25 Feb 2014 20:32:16 +0000
Subject: RE: Ad hominems
Thread-Topic: Ad hominems
Thread-Index: Ac8yZva07pCdpGd0RKa4aQB68gJP/wAAbWA4
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334736@EXMB01CMS.surrey.ac.uk>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net>,<530CF927.4080203@cisco.com>
In-Reply-To: <530CF927.4080203@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/477BRKGdfCcl4oMQLVLm2BLlUkM
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, 25 Feb 2014 20:34:48 -0000

> As to the later context concerning the original posters remarks:
> I was already fully aware that London would be their first F2F
> meeting when I read the OP

and the IETF mentoring program is very helpful to new attendees,
I'm told.

http://www.ietf.org/resources/mentoring-program.html

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Stewart Bryant [stbryant@ci=
sco.com]
Sent: 25 February 2014 20:12
To: dcrocker@bbiw.net; Barry Leiba; Noel Chiappa
Cc: IETF discussion list
Subject: Re: Ad hominems

On 25/02/2014 19:39, Dave Crocker wrote:
> On 2/25/2014 11:23 AM, Stewart Bryant wrote:
>> "I suggest in London that you assign only maximum 10 minutes
>> present per WG draft and maximum 5 minute for individual draft
>> (as limit policy). We need to use more input and have more face2face
>> (F2F) discussion in our meeting. I remember we discussed this before
>> ...."
>>
>> Although that text started with the word "suggestion", the
>> text construction is that of an instruction.
>
>
> Instruction?  Huh?  That characterization warrants careful
> explanation.  Please provide it.
>
> The note 1) made a suggestion, and 2) Stated a need.  It implied that
> implementing the change would remedy the need.
>
> What part of that qualifies as "instruction" rather than, for example,
> explanation?
>
> There was nothing tutorial, parental or authoritative in the note
> making the suggestion.  Everything focusing on background and presence
> or lack of expertise was introduced by others, in response.  Hence, ad
> hominem.
>
> d/

Dave

First, please can I request that you take a less harassing approach to
this discussion.

I explained how I interpreted that that text when I first read it.
That was a personal interpretation of the text on first reading,
and as such requires no further explanation.

As to the later context concerning the original posters remarks:
I was already fully aware that London would be their first F2F
meeting when I read the OP, and I am fairly confident that
Lloyd also had that context before he posted.

So, please consider that

1) There was widely shared prior context in the early
discussion.

2) That everyone sees text though their personal lenses
coloured by both experience and context and will interpret
it accordingly.

In the case of this text construct itself, I read it as an instruction
because that is the style of text I might have written if I were
issuing an instruction to the RTG WG Chairs as their AD.

- Stewart







From nobody Tue Feb 25 13:22:34 2014
Return-Path: <mstjohns@comcast.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 310A81A024A for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 13:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.65
X-Spam-Level: 
X-Spam-Status: No, score=0.65 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, MISSING_MID=0.497, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W9MOfDw0Xmvt for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 13:22:18 -0800 (PST)
Received: from qmta03.westchester.pa.mail.comcast.net (qmta03.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:32]) by ietfa.amsl.com (Postfix) with ESMTP id 6A9481A0786 for <ietf@ietf.org>; Tue, 25 Feb 2014 13:21:50 -0800 (PST)
Received: from omta02.westchester.pa.mail.comcast.net ([76.96.62.19]) by qmta03.westchester.pa.mail.comcast.net with comcast id WjNP1n0020QuhwU53lMpi6; Tue, 25 Feb 2014 21:21:49 +0000
Received: from Mike-T530ssd.comcast.net ([68.34.113.195]) by omta02.westchester.pa.mail.comcast.net with comcast id WlMo1n00w4D0RQL3NlMpAF; Tue, 25 Feb 2014 21:21:49 +0000
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 25 Feb 2014 16:21:38 -0500
To: stbryant@cisco.com,dcrocker@bbiw.net, Barry Leiba <barryleiba@computer.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
From: Michael StJohns <mstjohns@comcast.net>
Subject: Re: Ad hominems
In-Reply-To: <530CF927.4080203@cisco.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393363309; bh=CusvNYyOJ+z/IuQBfSIZVlfBG+O7s0WBNkQhDXrSZaM=; h=Received:Received:Date:To:From:Subject:Mime-Version:Content-Type; b=ClWV8uxnkvniYL3poYsJUdVxVxLV5hIZ7s0bZNFhy49G9WU/XHCAQsO4+AmrzkE3M jhGp+O35VfDuy2Dhh8JGs5/V28MAcekzgU1oe3L+3Gsf9NJvaaOboiLHL/5kMDQ4Pe LXxIa6rEcN5AI+t/wwOUcmTnih5uh6g4rHgjuZtd7M/E4cmx3P2vmDnu+gWxUUATyC 6h9EuzMU4sshRy1k8edtBPaTuvdH/r6QGeyujHMgV/ST183DgKafI1DcJJwjyUappS 1fvgyT+zlXuhKw6RdImCkZlCcLxx3VSH2d33VB0AW+DaVKNUFQ7mR0ZNKkwSOqcqud CQvND3UJLGfdg==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-sCthyrrZIRFtjNh8kNg-PWrZ4E
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, 25 Feb 2014 21:22:23 -0000

At 03:12 PM 2/25/2014, Stewart Bryant wrote:
>On 25/02/2014 19:39, Dave Crocker wrote:
>>On 2/25/2014 11:23 AM, Stewart Bryant wrote:
>>>"I suggest in London that you assign only maximum 10 minutes
>>>present per WG draft and maximum 5 minute for individual draft
>>>(as limit policy). We need to use more input and have more face2face
>>>(F2F) discussion in our meeting. I remember we discussed this before
>>>...."
>>>
>>>Although that text started with the word "suggestion", the
>>>text construction is that of an instruction.
>>
>>
>>Instruction?  Huh?  That characterization warrants careful explanation.  Please provide it.
>>
>>The note 1) made a suggestion, and 2) Stated a need.  It implied that implementing the change would remedy the need.
>>
>>What part of that qualifies as "instruction" rather than, for example, explanation?
>>
>>There was nothing tutorial, parental or authoritative in the note making the suggestion.  Everything focusing on background and presence or lack of expertise was introduced by others, in response.  Hence, ad hominem.
>>
>>d/
>
>Dave
>
>First, please can I request that you take a less harassing approach to
>this discussion.
>
>I explained how I interpreted that that text when I first read it.
>That was a personal interpretation of the text on first reading,
>and as such requires no further explanation.
>
>As to the later context concerning the original posters remarks:
>I was already fully aware that London would be their first F2F
>meeting when I read the OP, and I am fairly confident that
>Lloyd also had that context before he posted.
>
>So, please consider that
>
>1) There was widely shared prior context in the early
>discussion.
>
>2) That everyone sees text though their personal lenses
>coloured by both experience and context and will interpret
>it accordingly.
>
>In the case of this text construct itself, I read it as an instruction
>because that is the style of text I might have written if I were
>issuing an instruction to the RTG WG Chairs as their AD.
>
>- Stewart
>
>

I read the original email much like Stewart did.  Unlike a number of the posters on this chain, I did not review the email "de novo" - or in isolation from the original poster's other emails and considered it in the context of other postings from the originator. I briefly considered whether or not it would be profitable for either the IETF or for the poster to note my dissatisfaction with his post publicly or privately.   I decided against, but the discussion has progressed. 

This chain has been about "ad hominem" attacks, but I considered the original post to be somewhat of an  "ad ordinationem" - or an attack on the organization.  It's possible that I'm overreacting to the style of posting or "lost in translation" language nuances in this interpretation, but that interpretation  is colored by a pretty long record of [personal interpretation] "you must do it my way"  or "your way is wrong" posts by the original poster over the last 6 or so months. <opinion>    As it is, I read the original post as a negative comment by an outsider on established processes and cultures internal to the IETF and the comment should get appropriate weighting based on the posters lack of experience within the organization. </opinion>

The IETF is and has been for quite a while a technological meritocracy of some flavor [personal observation based on 28 years of experience with the IETF].  We *always* consider the relevant experience, expertise, past commentary and general sanity of a speaker when considering what to do about their speech.  So the inquiry into the poster's experience was neither irrelevant or unusual.    

Mike






From nobody Tue Feb 25 13:39:44 2014
Return-Path: <jdrake@juniper.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 6C5111A024A for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 13:39:35 -0800 (PST)
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 I0Icppcw8K5O for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 13:39:32 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe005.messaging.microsoft.com [207.46.163.28]) by ietfa.amsl.com (Postfix) with ESMTP id 9E2891A0151 for <ietf@ietf.org>; Tue, 25 Feb 2014 13:39:32 -0800 (PST)
Received: from mail181-co9-R.bigfish.com (10.236.132.229) by CO9EHSOBE031.bigfish.com (10.236.130.94) with Microsoft SMTP Server id 14.1.225.22; Tue, 25 Feb 2014 21:39:31 +0000
Received: from mail181-co9 (localhost [127.0.0.1])	by mail181-co9-R.bigfish.com (Postfix) with ESMTP id 7EEB5700067;	Tue, 25 Feb 2014 21:39:31 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(z569dhzbb2dI98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzd9hdchz1de098h1033IL1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh25cch9a9j1155h)
Received-SPF: pass (mail181-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT004.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(51704005)(479174003)(199002)(189002)(24454002)(13464003)(377454003)(66066001)(76482001)(94946001)(19580395003)(54356001)(53806001)(80976001)(93136001)(81542001)(93516002)(46102001)(19580405001)(83322001)(54316002)(65816001)(86362001)(56776001)(51856001)(95666003)(63696002)(76786001)(47736001)(76796001)(83072002)(85852003)(87936001)(92566001)(94316002)(2201001)(76576001)(81342001)(74366001)(33646001)(90146001)(56816005)(87266001)(85306002)(74876001)(2656002)(74706001)(74316001)(49866001)(69226001)(4396001)(47976001)(2171001)(80022001)(50986001)(59766001)(77982001)(95416001)(81816001)(79102001)(81686001)(221733001)(74502001)(74662001)(47446002)(31966008)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR05MB772; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.11; FPR:9E28FCBD.97FAE3C2.71F3397B.8AF6DA41.20523; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail181-co9 (localhost.localdomain [127.0.0.1]) by mail181-co9 (MessageSwitch) id 139336437081072_15814; Tue, 25 Feb 2014 21:39:30 +0000 (UTC)
Received: from CO9EHSMHS020.bigfish.com (unknown [10.236.132.234])	by mail181-co9.bigfish.com (Postfix) with ESMTP id 04DE4A00079; Tue, 25 Feb 2014 21:39:30 +0000 (UTC)
Received: from BL2PRD0510HT004.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS020.bigfish.com (10.236.130.30) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 25 Feb 2014 21:39:29 +0000
Received: from BLUPR05MB772.namprd05.prod.outlook.com (10.141.209.27) by BL2PRD0510HT004.namprd05.prod.outlook.com (10.255.100.39) with Microsoft SMTP Server (TLS) id 14.16.411.0; Tue, 25 Feb 2014 21:39:29 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB772.namprd05.prod.outlook.com (10.141.209.27) with Microsoft SMTP Server (TLS) id 15.0.883.10; Tue, 25 Feb 2014 21:39:28 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0883.010; Tue, 25 Feb 2014 21:39:28 +0000
From: John E Drake <jdrake@juniper.net>
To: Michael StJohns <mstjohns@comcast.net>, "stbryant@cisco.com" <stbryant@cisco.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Barry Leiba <barryleiba@computer.org>, Noel Chiappa <jnc@mercury.lcs.mit.edu>
Subject: RE: Ad hominems
Thread-Topic: Ad hominems
Thread-Index: AQHPMlMY1+1fMY6PIUGbeZ4hVqDQFZrGT6wAgAAJ3QCAAARigIAACTiAgAATWQCAAAJ0YA==
Date: Tue, 25 Feb 2014 21:39:27 +0000
Message-ID: <500805f1dfb947128cef921b2085a165@BLUPR05MB562.namprd05.prod.outlook.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <20140225212232.F00711A036D@ietfa.amsl.com>
In-Reply-To: <20140225212232.F00711A036D@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.11]
x-forefront-prvs: 01334458E5
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/lTQmSo2SbENTXcKOhtslQStDr7M
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, 25 Feb 2014 21:39:35 -0000

Mike,

Finally a voice of sanity.  As an aside, I thought Lloyd's original email w=
as remarkably restrained given the context of the last year or so. =20

Yours Irrespectively,

John

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Michael StJohns
> Sent: Tuesday, February 25, 2014 1:22 PM
> To: stbryant@cisco.com; dcrocker@bbiw.net; Barry Leiba; Noel Chiappa
> Cc: IETF discussion list
> Subject: Re: Ad hominems
>=20
> At 03:12 PM 2/25/2014, Stewart Bryant wrote:
> >On 25/02/2014 19:39, Dave Crocker wrote:
> >>On 2/25/2014 11:23 AM, Stewart Bryant wrote:
> >>>"I suggest in London that you assign only maximum 10 minutes present
> >>>per WG draft and maximum 5 minute for individual draft (as limit
> >>>policy). We need to use more input and have more face2face
> >>>(F2F) discussion in our meeting. I remember we discussed this before
> >>>...."
> >>>
> >>>Although that text started with the word "suggestion", the text
> >>>construction is that of an instruction.
> >>
> >>
> >>Instruction?  Huh?  That characterization warrants careful explanation.
> Please provide it.
> >>
> >>The note 1) made a suggestion, and 2) Stated a need.  It implied that
> implementing the change would remedy the need.
> >>
> >>What part of that qualifies as "instruction" rather than, for example,
> explanation?
> >>
> >>There was nothing tutorial, parental or authoritative in the note makin=
g the
> suggestion.  Everything focusing on background and presence or lack of
> expertise was introduced by others, in response.  Hence, ad hominem.
> >>
> >>d/
> >
> >Dave
> >
> >First, please can I request that you take a less harassing approach to
> >this discussion.
> >
> >I explained how I interpreted that that text when I first read it.
> >That was a personal interpretation of the text on first reading, and as
> >such requires no further explanation.
> >
> >As to the later context concerning the original posters remarks:
> >I was already fully aware that London would be their first F2F meeting
> >when I read the OP, and I am fairly confident that Lloyd also had that
> >context before he posted.
> >
> >So, please consider that
> >
> >1) There was widely shared prior context in the early discussion.
> >
> >2) That everyone sees text though their personal lenses coloured by
> >both experience and context and will interpret it accordingly.
> >
> >In the case of this text construct itself, I read it as an instruction
> >because that is the style of text I might have written if I were
> >issuing an instruction to the RTG WG Chairs as their AD.
> >
> >- Stewart
> >
> >
>=20
> I read the original email much like Stewart did.  Unlike a number of the =
posters
> on this chain, I did not review the email "de novo" - or in isolation fro=
m the
> original poster's other emails and considered it in the context of other =
postings
> from the originator. I briefly considered whether or not it would be prof=
itable
> for either the IETF or for the poster to note my dissatisfaction with his=
 post
> publicly or privately.   I decided against, but the discussion has progre=
ssed.
>=20
> This chain has been about "ad hominem" attacks, but I considered the orig=
inal
> post to be somewhat of an  "ad ordinationem" - or an attack on the
> organization.  It's possible that I'm overreacting to the style of postin=
g or "lost
> in translation" language nuances in this interpretation, but that interpr=
etation
> is colored by a pretty long record of [personal interpretation] "you must=
 do it
> my way"  or "your way is wrong" posts by the original poster over the las=
t 6 or
> so months. <opinion>    As it is, I read the original post as a negative =
comment
> by an outsider on established processes and cultures internal to the IETF=
 and
> the comment should get appropriate weighting based on the posters lack of
> experience within the organization. </opinion>
>=20
> The IETF is and has been for quite a while a technological meritocracy of=
 some
> flavor [personal observation based on 28 years of experience with the IET=
F].
> We *always* consider the relevant experience, expertise, past commentary
> and general sanity of a speaker when considering what to do about their
> speech.  So the inquiry into the poster's experience was neither irreleva=
nt or
> unusual.
>=20
> Mike
>=20
>=20
>=20
>=20
>=20
>=20



From nobody Tue Feb 25 13: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 EC9441A02A0 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 13:48:24 -0800 (PST)
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 EmWBphzfmpVu for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 13:48:17 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1E81B1A02C4 for <ietf@ietf.org>; Tue, 25 Feb 2014 13:48:17 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1PLmBeC024020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Feb 2014 13:48:15 -0800
Message-ID: <530D0F63.5020605@dcrocker.net>
Date: Tue, 25 Feb 2014 13:47:15 -0800
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.3.0
MIME-Version: 1.0
To: stbryant@cisco.com
Subject: Re: Ad hominems
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com>
In-Reply-To: <530CF927.4080203@cisco.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, 25 Feb 2014 13:48:15 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/99whpaZEDNRJ1A1XZK-NPGwFdkA
Cc: IETF discussion list <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, 25 Feb 2014 21:48:25 -0000

On 2/25/2014 12:12 PM, Stewart Bryant wrote:
> On 25/02/2014 19:39, Dave Crocker wrote:
>> On 2/25/2014 11:23 AM, Stewart Bryant wrote:
>>> Although that text started with the word "suggestion", the
>>> text construction is that of an instruction.
>>
>>
>> Instruction?  Huh?  That characterization warrants careful
>> explanation.  Please provide it.
>>
>> The note 1) made a suggestion, and 2) Stated a need.  It implied that
>> implementing the change would remedy the need.
>>
>> What part of that qualifies as "instruction" rather than, for example,
>> explanation?
>>
>> There was nothing tutorial, parental or authoritative in the note
>> making the suggestion.  Everything focusing on background and presence
>> or lack of expertise was introduced by others, in response.  Hence, ad
>> hominem.
>>
>> d/
>
> Dave
>
> First, please can I request that you take a less harassing approach to
> this discussion.

If I knew what you considered harassing and how it constitutes 
harassing, I'd be able to consider the request.  Given the import of a 
word like harassing, it's surprising it would be used without any 
explanation.  So, sitting as a standalone assertion, without 
explanation, it's difficult to see how your 'request' is constructive.


> I explained how I interpreted that that text when I first read it.
> That was a personal interpretation of the text on first reading,
> and as such requires no further explanation.

As nearly as I can tell, you are referring to the note posted with

      Date: Tue, 25 Feb 2014 19:23:42 +0000

and I don't see an 'explanation' in it.  I see the assertion that labels 
the text and that's what I was asking to have explained.  (It's the 
first quoted text at the start of the current message.)


> As to the later context concerning the original posters remarks:
> I was already fully aware that London would be their first F2F
> meeting when I read the OP, and I am fairly confident that
> Lloyd also had that context before he posted.

So?


> So, please consider that
>
> 1) There was widely shared prior context in the early
> discussion.

a) This nicely points to a likely source of misbehaviors in the IETF: 
confusing close, familiar groups that have plenty of context, with 
public, diverse environments which do not. This is not a private club, 
where behaviors can comfortably be whatever the members want.  This is 
an open, international forum in which there should be some expectation 
of professional demeanor.  In such an environment, challenging someone's 
expertise is warranted only in the face of their claiming expertise, 
which he didn't.

b) The prior context you are claiming is irrelevant to the exchange in 
question.  He didn't call on it, and as nearly as I can tell from my own 
reading of the IETF list, whatever context you are referring to -- and I 
don't know what or where it was -- it had nothing to do with the 
specific suggestion being made.


> 2) That everyone sees text though their personal lenses
> coloured by both experience and context and will interpret
> it accordingly.

What a delightfully "Through the Looking Glass" approach to demurring 
from responsibility for personal behavior.  It's especially amusing in a 
community that writes international specifications that rely on getting 
common interpretations, in the service of interoperability.

It nicely points to individual difference as if there were no shared 
conventions and meaning.  Since the essence of 'communication' is shared 
meaning, that's quite a trick.


> In the case of this text construct itself, I read it as an instruction
> because that is the style of text I might have written if I were
> issuing an instruction to the RTG WG Chairs as their AD.

OK.  So "do x; we need y" is an instruction.  Well, yeah, that works 
well when everyone has a thoroughly shared context, where no real 
explanations are needed.  Such as works in a tightly-knit team.

But that's a bit unusual -- and highly risky -- to assume in an open, 
diverse forum like the IETF..

d/

ps.  By way of noting a pattern of comments made on this thread:  There 
seems to be some view that disliking a speaker is a sufficient reason 
for attacking them (publicly.)  Of course, it isn't.  It's an excellent 
reason for ignoring them.  But not for attacking them.


-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Feb 25 13:59: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 C45821A079D for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 13:59:05 -0800 (PST)
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 DuA93-vzDLMt for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 13:59:02 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id DA02A1A01E5 for <ietf@ietf.org>; Tue, 25 Feb 2014 13:59:02 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1PLwwf6024635 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Feb 2014 13:59:01 -0800
Message-ID: <530D11EA.2060404@dcrocker.net>
Date: Tue, 25 Feb 2014 13:58:02 -0800
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.3.0
MIME-Version: 1.0
To: John C Klensin <john-ietf@jck.com>, ned+ietf@mauve.mrochek.com
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com> <3FF3186251572A0DB04C2762@JcK-HP8200.jck.com>
In-Reply-To: <3FF3186251572A0DB04C2762@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]); Tue, 25 Feb 2014 13:59:02 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/57Pms6XaMQ2uh7Q_31BBnchf_BA
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, 25 Feb 2014 21:59:06 -0000

On 2/25/2014 11:52 AM, John C Klensin wrote:
> for those who think the question was inappropriate, a
> comparative question about the following two entirely
> hypothetical cases:
...
>   Case 2: You have asserted that a protocol feature being
> 	reviewed in a WG does not work.  Have you implemented
> 	and tested it and, if not, on what basis do you make
> 	that assertion?


For this thread, it's been interesting to watch the way people have been 
skipping logic steps, conflating issues, inventing issues, wandering off 
into hypotheticals, or entirely missing basic issues.

When a suggestion is made and there has been no offer of expertise to 
justify it, the reasonable challenge is "What is the basis for believing 
that the suggestion is appropriate?" or an equivalent that targets the 
pragmatics of the suggestion.  It's entirely impersonal and entirely 
relevant.

What's happened here, instead, including your above examples (until the 
second part of the question in Case 2, is to challenge the person making 
the suggestion.

Absent an assertion of authority by the person making the suggestion -- 
and it was absent in this case -- questioning the background of that 
person is an ad hominem.

If the speaker is not arguing from authority, questioning their 
authority is somewhere between suspect and harassment.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Feb 25 14:38:04 2014
Return-Path: <jdrake@juniper.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 A787D1A07A3 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 14:37:57 -0800 (PST)
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 uTlOllPu1-1i for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 14:37:55 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe004.messaging.microsoft.com [207.46.163.27]) by ietfa.amsl.com (Postfix) with ESMTP id BEE9E1A079D for <ietf@ietf.org>; Tue, 25 Feb 2014 14:37:54 -0800 (PST)
Received: from mail191-co9-R.bigfish.com (10.236.132.246) by CO9EHSOBE021.bigfish.com (10.236.130.84) with Microsoft SMTP Server id 14.1.225.22; Tue, 25 Feb 2014 22:37:53 +0000
Received: from mail191-co9 (localhost [127.0.0.1])	by mail191-co9-R.bigfish.com (Postfix) with ESMTP id B593E300139;	Tue, 25 Feb 2014 22:37:53 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(z579ehzbb2dI98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1de098h1033IL8275bh8275dh1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh25cch9a9j1155h)
Received-SPF: pass (mail191-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(13464003)(24454002)(199002)(189002)(479174003)(51704005)(87266001)(69226001)(56776001)(54316002)(83322001)(19580395003)(76482001)(19580405001)(85306002)(94946001)(95416001)(94316002)(86362001)(87936001)(2656002)(81342001)(50986001)(47736001)(47976001)(4396001)(49866001)(81542001)(47446002)(74502001)(31966008)(59766001)(93136001)(51856001)(46102001)(93516002)(53806001)(80976001)(33646001)(54356001)(92566001)(81816001)(79102001)(77982001)(74366001)(63696002)(74316001)(81686001)(76576001)(76796001)(76786001)(65816001)(74662001)(66066001)(90146001)(80022001)(56816005)(74876001)(74706001)(83072002)(85852003)(95666003)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR05MB770; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.11; FPR:BFF8CAA5.1C2897DA.B1EF3447.88EA604D.20232; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail191-co9 (localhost.localdomain [127.0.0.1]) by mail191-co9 (MessageSwitch) id 1393367870858372_4736; Tue, 25 Feb 2014 22:37:50 +0000 (UTC)
Received: from CO9EHSMHS016.bigfish.com (unknown [10.236.132.251])	by mail191-co9.bigfish.com (Postfix) with ESMTP id C325484004C; Tue, 25 Feb 2014 22:37:50 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS016.bigfish.com (10.236.130.26) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 25 Feb 2014 22:37:50 +0000
Received: from BLUPR05MB770.namprd05.prod.outlook.com (10.141.209.25) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.411.0; Tue, 25 Feb 2014 22:37:41 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB770.namprd05.prod.outlook.com (10.141.209.25) with Microsoft SMTP Server (TLS) id 15.0.883.10; Tue, 25 Feb 2014 22:37:39 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0883.010; Tue, 25 Feb 2014 22:37:39 +0000
From: John E Drake <jdrake@juniper.net>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, John C Klensin <john-ietf@jck.com>, "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Subject: RE: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Topic: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Index: AQHPMaekO1W0xKmIKkirN3CZG6qAVprGJAGAgAAOxlKAADAOgIAAIyoAgAAJTSA=
Date: Tue, 25 Feb 2014 22:37:38 +0000
Message-ID: <4dfe7ef03cbb4e08b9028a1b2e8dea3f@BLUPR05MB562.namprd05.prod.outlook.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com> <3FF3186251572A0DB04C2762@JcK-HP8200.jck.com> <530D11EA.2060404@dcrocker.net>
In-Reply-To: <530D11EA.2060404@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.11]
x-forefront-prvs: 01334458E5
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/SPH4bEtU4Fa5aUFho7apLW14WoI
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, 25 Feb 2014 22:37:57 -0000

Dave,

Snipped, question inline.=20

Yours Irrespectively,

John

> -----Original Message-----
> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Dave Crocker
> Sent: Tuesday, February 25, 2014 1:58 PM
> To: John C Klensin; ned+ietf@mauve.mrochek.com
> Cc: ietf@ietf.org
> Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for
> presentations and face2face discussions)
>=20
> On 2/25/2014 11:52 AM, John C Klensin wrote:
> > for those who think the question was inappropriate, a comparative
> > question about the following two entirely hypothetical cases:
> ...
> >   Case 2: You have asserted that a protocol feature being
> > 	reviewed in a WG does not work.  Have you implemented
> > 	and tested it and, if not, on what basis do you make
> > 	that assertion?
>=20
>=20
> For this thread, it's been interesting to watch the way people have been
> skipping logic steps, conflating issues, inventing issues, wandering off =
into
> hypotheticals, or entirely missing basic issues.

[JD]  For my personal understanding, why isn't the above an ad hominem atta=
ck
of those that disagree with you?




From nobody Tue Feb 25 15:22: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 4F10F1A07AB for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:21:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 QmOP-y0ibG_2 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:21:51 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id F01801A0324 for <ietf@ietf.org>; Tue, 25 Feb 2014 15:21:49 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.156.84]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1PNLKLA007983 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 25 Feb 2014 15:21:31 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393370493; bh=lDiHxvFnSkyyawDN/X/V69PEBUZTL00m6MENDV3BSd4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=jIl2G1I++ghISQ65pV2GOCDfixzrtTMBIEvoo7FEGtZlEFT3H+Di9lQGvz+PKUzz5 f9xCtPLhIztsu4ThoGsaCNnFmrMyLTwbrKsrM55K6oJjW4/8gAV3JazLRMMxdUMY27 FjeUroS2XhWNDre9Xpjbcxn+YEig3PnUPX91m6h4=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393370493; i=@elandsys.com; bh=lDiHxvFnSkyyawDN/X/V69PEBUZTL00m6MENDV3BSd4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=0NdbD56SCeuaf6pTwAhMpzj4bavwUmfOR1H6W/VQVyrl4e5URBs8SvEfL4y+m122P vAyGPHK7Pf3RNyPLDEsNuA+8+iwDvHg1pLsjOAXjezCJJPw1h5H5Ith4qIu2IkbKva cSix5ZqxpDkbRrQe51GpmcSUoOqxkB7wJPAuK/oo=
Message-Id: <6.2.5.6.2.20140225145100.0ca68e10@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 25 Feb 2014 15:20:39 -0800
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: A private club (was: Ad hominems)
In-Reply-To: <530D0F63.5020605@dcrocker.net>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/WsdXJ07OrriSYpEsa-nEAxC0WYI
Cc: dcrocker@bbiw.net, 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: Tue, 25 Feb 2014 23:21:53 -0000

At 13:47 25-02-2014, Dave Crocker wrote:
>a) This nicely points to a likely source of misbehaviors in the 
>IETF: confusing close, familiar groups that have plenty of context, 
>with public, diverse environments which do not. This is not a 
>private club, where behaviors can comfortably be whatever the 
>members want.  This is an open, international forum in which there 
>should be some expectation of professional demeanor.  In such an 
>environment, challenging someone's expertise is warranted only in 
>the face of their claiming expertise, which he didn't.

If the IETF is a private club members can do whatever they want.  If 
the IETF is an international organization there is an expectation 
that the members will act in a professional manner when the situation 
warrants it.  Please note that I did not go for an extreme as it 
might quash individualism [1].

Regards,
S. Moonesamy

1. a theory maintaining the political and economic independence of 
the individual and stressing individual initiative, action, and interests. 


From nobody Tue Feb 25 15:32:46 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 001BE1A07E2 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:32:41 -0800 (PST)
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 Gl1AmKUOSwO7 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:32:39 -0800 (PST)
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 182C71A07DF for <ietf@ietf.org>; Tue, 25 Feb 2014 15:32:39 -0800 (PST)
Received: by mail-pd0-f182.google.com with SMTP id v10so119873pde.27 for <ietf@ietf.org>; Tue, 25 Feb 2014 15:32:38 -0800 (PST)
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=6++yjs/qG7sw3XWqQO+RGotTEqJmND0oKwjdUFLdSq4=; b=f66LxpENoe1iTg1pjOKSjLOhewSn/M4+nI4TvHOZWFVtadfcgQCOXSBfSLr9Jurp+D Prlx9KiwWKCGm4au7tFq+hNchSRQqpNX4ut51KBD3IdRM8RxSSeV89tuzsQt1WhbyYNN fyyb/+2EjqP4b0bYJgi+tgN60/NtdigVr2G9y3kBjR1M1vXlDapnvNa7qTcmpdzCveDx xyDoBzeMDtD7p8+qPyc8GXn+2s6G88Eh3LdKaAH1S+69sClQE4F7iHbANiMdQKQYKGu+ jihJiXvEZ6eIiyEfJomaJoI9xozFuxye6aIm+BOXzA9O4NxZpOw49r5WBpKhAZ2KocQ3 j/vw==
X-Received: by 10.66.65.134 with SMTP id x6mr4630235pas.12.1393371158240; Tue, 25 Feb 2014 15:32:38 -0800 (PST)
Received: from spandex.local (63-140-68-38-rb2.sol.dsl.dynamic.acsalaska.net. [63.140.68.38]) by mx.google.com with ESMTPSA id n6sm14461584pbj.22.2014.02.25.15.32.36 for <ietf@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Feb 2014 15:32:37 -0800 (PST)
Message-ID: <530D2813.1080304@gmail.com>
Date: Tue, 25 Feb 2014 14:32:35 -0900
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: A private club
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net>
In-Reply-To: <6.2.5.6.2.20140225145100.0ca68e10@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CW6pe_qJ6jbMqNj_hUssOy139QE
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Feb 2014 23:32:42 -0000

On 2/25/14 2:20 PM, S Moonesamy wrote:
> If the IETF is a private club members can do whatever they want.  If the
> IETF is an international organization there is an expectation that the
> members will act in a professional manner when the situation warrants
> it. 

The IETF does not have members.  This is not a minor point.

Melinda



From nobody Tue Feb 25 15:36:34 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 2A68F1A01B2 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:36:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.447
X-Spam-Level: 
X-Spam-Status: No, score=-0.447 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id egHbAk6dhiHy for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:36:23 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id BFB541A00C2 for <ietf@ietf.org>; Tue, 25 Feb 2014 15:36:22 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WIRXx-000Iw4-CL; Tue, 25 Feb 2014 18:36:21 -0500
Date: Tue, 25 Feb 2014 18:36:00 -0500
From: John C Klensin <john-ietf@jck.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, ietf@ietf.org
Subject: Re: Ad hominems
Message-ID: <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com>
In-Reply-To: <20140225175749.5521718C139@mercury.lcs.mit.edu>
References: <20140225175749.5521718C139@mercury.lcs.mit.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-ZxM5XdNMhQGGFwQ-uXjlcC6mzM
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Feb 2014 23:36:25 -0000

--On Tuesday, February 25, 2014 12:57 -0500 Noel Chiappa
<jnc@mercury.lcs.mit.edu> wrote:

>...
> I think there are different thresholds for 'ad hominem' -
> loosely interpreted as '_inappropriately_ about the speaker
> rather than about what they say' - depending on the area.

Noel,

See Andrew's careful explanation for a better definition, but an
ad hominem argument is not about the speaker or necessarily
addressed to the speaker.  "Joe is a meat eater, and therefore
his position on BGP is obviously incorrect" is an example,
albeit an extreme one: some property is attributed to Joe that
some members of the community might find unattractive and Joe's
association with that property is then used as a argument
against accepting Joe's view on something completely irrelevant
to that property.  Whether that is also a personal attack on Joe
is irrelevant to the ad hominem argument.

The only thing I can think of that would affect the "threshold"
is the degree of relevancy between the property being asserted
and the proposed conclusion.

>...
> On the other hand, for discussions of group governance, I
> think the person's experience/knowledge/etc _are_ relevant,
> because when it comes to managing human groups, there are no
> 'right' answers. (Which is why the Law of Unintended
> Consequences often comes into play in human governance
> decisions.) That kind of information about someone has some
> real utility in evaluating their thoughts about such topics,
> so _some_ questioning is legitimate.

It seems to me that we keep getting distracted by two things:

(1) The difference between a personal attack on someone (direct
or indirect) and an ad hominem argument.  They actually have
very little to do with each other.  Certainly there are
instances of the former that are not instances of the latter and
vice versa.

(2) The relationship between whether a question or other form of
challenge to an idea is appropriate and/or politically correct
in form and personal attacks.  I can ask a question that is
perfectly in order and phrase it with the intent that the person
being asked feels personally attacked, I can ask inappropriate
questions so that they are not... and the other cases exist too.

> And in these latter case, I suspect there's also a grey area -
> 'you're an idiot' is pretty clearly over the line, 'how much
> experience have you had running large groups' is probably
> relevant, and 'how old are you' (as a quick example off the
> top of my head, not necessarily the greyest I could come up
> with if I spent more time thinking about it) is somewhere in
> the middle..

Whatever those are, they are not ad hominem arguments because
there is, in non-philosopher language, no "and therefore"
construction.  Those are all assertions that, again, may be true
or false and may or may not be appropriate in polite company
whether or not they are personal attacks and regardless of their
truth status.     You are talking about more or less appropriate
questions and statements above, not ad hominem anything.

Under normal circumstances, I'd mutter something about
terminology errors about a logic fallacy into my beard and move
on rather than commenting on this at all.  But we seem to be
stepping into policy arguments about what constitutes
harassment.  There I think these distinctions become important
because ad hominem arguments, while they reflect badly on the
person who tries to make them and may reflect badly on anyone
who doesn't see the logic fallacy, are rarely considered
harassing even if repeated to the point of silliness.  Personal
attacks, whether separate or the first, "Melvin is an idiot",
part of  an ad hominem or other argument, are another matter
entirely.  And I think it is important to be clear about what we
are talking about.

   john






From nobody Tue Feb 25 15:38: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 E0F4A1A01BC for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:38:02 -0800 (PST)
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 M9O59e7mFeJ2 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:37:58 -0800 (PST)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id B9BA31A00C2 for <ietf@ietf.org>; Tue, 25 Feb 2014 15:37:58 -0800 (PST)
Received: from [192.168.156.199] (rrcs-67-52-140-5.west.biz.rr.com [67.52.140.5]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id s1PNbsFj026872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Feb 2014 15:37:57 -0800
Message-ID: <530D291A.3040907@dcrocker.net>
Date: Tue, 25 Feb 2014 15:36:58 -0800
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.3.0
MIME-Version: 1.0
To: John E Drake <jdrake@juniper.net>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com> <3FF3186251572A0DB04C2762@JcK-HP8200.jck.com> <530D11EA.2060404@dcrocker.net> <4dfe7ef03cbb4e08b9028a1b2e8dea3f@BLUPR05MB562.namprd05.prod.outlook.com>
In-Reply-To: <4dfe7ef03cbb4e08b9028a1b2e8dea3f@BLUPR05MB562.namprd05.prod.outlook.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, 25 Feb 2014 15:37:58 -0800 (PST)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HD0zc8N9nPM7PWivyl877nyjt10
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: Tue, 25 Feb 2014 23:38:03 -0000

On 2/25/2014 2:37 PM, John E Drake wrote:
>> For this thread, it's been interesting to watch the way people have been
>> >skipping logic steps, conflating issues, inventing issues, wandering off into
>> >hypotheticals, or entirely missing basic issues.
> [JD]  For my personal understanding, why isn't the above an ad hominem attack
> of those that disagree with you?



For the same reason your question to me is not an ad hominem:

      The focus is on what was said, not who said it.

So while my previous note might be criticized for being overly broad or 
or overly vague, or inadequately substantiated, or just plain wrong, it 
was not "about" the people but rather "about" the things being said.


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net


From nobody Tue Feb 25 15:51:54 2014
Return-Path: <jdrake@juniper.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 36A0A1A0326 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:51:50 -0800 (PST)
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 JKfrfF5OcBvX for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 15:51:48 -0800 (PST)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id 49D1A1A07A0 for <ietf@ietf.org>; Tue, 25 Feb 2014 15:51:48 -0800 (PST)
Received: from mail81-va3-R.bigfish.com (10.7.14.225) by VA3EHSOBE009.bigfish.com (10.7.40.29) with Microsoft SMTP Server id 14.1.225.22; Tue, 25 Feb 2014 23:51:46 +0000
Received: from mail81-va3 (localhost [127.0.0.1])	by mail81-va3-R.bigfish.com (Postfix) with ESMTP id DAB54200189; Tue, 25 Feb 2014 23:51:46 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT005.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -23
X-BigFish: VPS-23(z579ehzbb2dI98dI9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz8275ch1de098h1033IL8275dh1de097hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh25cch9a9j1155h)
Received-SPF: pass (mail81-va3: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT005.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(13464003)(24454002)(51704005)(479174003)(189002)(199002)(85306002)(74876001)(74706001)(74316001)(2656002)(33646001)(90146001)(87266001)(74366001)(56816005)(81686001)(79102001)(31966008)(74662001)(47446002)(74502001)(81816001)(77982001)(59766001)(50986001)(69226001)(4396001)(49866001)(47976001)(80022001)(95416001)(53806001)(80976001)(93136001)(81542001)(76482001)(66066001)(19580395003)(54356001)(94946001)(76786001)(47736001)(76796001)(63696002)(94316002)(92566001)(76576001)(81342001)(87936001)(83072002)(85852003)(56776001)(51856001)(86362001)(83322001)(19580405001)(65816001)(46102001)(54316002)(93516002)(95666003)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR05MB772; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.11; FPR:AF8AF485.1F3B57CA.71E22477.86EBA27C.20253; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail81-va3 (localhost.localdomain [127.0.0.1]) by mail81-va3 (MessageSwitch) id 1393372305394322_18044; Tue, 25 Feb 2014 23:51:45 +0000 (UTC)
Received: from VA3EHSMHS043.bigfish.com (unknown [10.7.14.228])	by mail81-va3.bigfish.com (Postfix) with ESMTP id 4907CE0092;	Tue, 25 Feb 2014 23:51:45 +0000 (UTC)
Received: from BL2PRD0510HT005.namprd05.prod.outlook.com (157.56.240.101) by VA3EHSMHS043.bigfish.com (10.7.99.53) with Microsoft SMTP Server (TLS) id 14.16.227.3; Tue, 25 Feb 2014 23:51:44 +0000
Received: from BLUPR05MB772.namprd05.prod.outlook.com (10.141.209.27) by BL2PRD0510HT005.namprd05.prod.outlook.com (10.255.100.40) with Microsoft SMTP Server (TLS) id 14.16.411.0; Tue, 25 Feb 2014 23:51:44 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB772.namprd05.prod.outlook.com (10.141.209.27) with Microsoft SMTP Server (TLS) id 15.0.883.10; Tue, 25 Feb 2014 23:51:43 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0883.010; Tue, 25 Feb 2014 23:51:43 +0000
From: John E Drake <jdrake@juniper.net>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: RE: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Topic: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Index: AQHPMaekO1W0xKmIKkirN3CZG6qAVprGJAGAgAAOxlKAADAOgIAAIyoAgAAJTSCAABJXAIAAA3VQ
Date: Tue, 25 Feb 2014 23:51:42 +0000
Message-ID: <b1d30944a246454b8cdddd2663e4346d@BLUPR05MB562.namprd05.prod.outlook.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com> <3FF3186251572A0DB04C2762@JcK-HP8200.jck.com> <530D11EA.2060404@dcrocker.net> <4dfe7ef03cbb4e08b9028a1b2e8dea3f@BLUPR05MB562.namprd05.prod.outlook.com> <530D291A.3040907@dcrocker.net>
In-Reply-To: <530D291A.3040907@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.11]
x-forefront-prvs: 01334458E5
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ch3Zkhl7XWJCKcRHVENyjBLjO5s
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, 25 Feb 2014 23:51:50 -0000

Dave,

But you use the phrase "the way people have been" and then you list all of =
the terrible things of which these people have been guilty. =20

Yours Irrespectively,

John

> -----Original Message-----
> From: Dave Crocker [mailto:dhc@dcrocker.net]
> Sent: Tuesday, February 25, 2014 3:37 PM
> To: John E Drake
> Cc: ietf@ietf.org
> Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for
> presentations and face2face discussions)
>=20
> On 2/25/2014 2:37 PM, John E Drake wrote:
> >> For this thread, it's been interesting to watch the way people have
> >> been
> >> >skipping logic steps, conflating issues, inventing issues, wandering
> >> >off into hypotheticals, or entirely missing basic issues.
> > [JD]  For my personal understanding, why isn't the above an ad hominem
> > attack of those that disagree with you?
>=20
>=20
>=20
> For the same reason your question to me is not an ad hominem:
>=20
>       The focus is on what was said, not who said it.
>=20
> So while my previous note might be criticized for being overly broad or o=
r overly
> vague, or inadequately substantiated, or just plain wrong, it was not "ab=
out"
> the people but rather "about" the things being said.
>=20
>=20
> d/
> --
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
>=20



From nobody Tue Feb 25 16:32:22 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 15D2F1A07E7 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 16:32:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.559
X-Spam-Level: 
X-Spam-Status: No, score=0.559 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_LETTER=-2, HELO_MISMATCH_INFO=1.448, HOST_MISMATCH_NET=0.311] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fXBZM2aSldA3 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 16:32:13 -0800 (PST)
Received: from mx1.yitter.info (ow5p.x.rootbsd.net [208.79.81.114]) by ietfa.amsl.com (Postfix) with ESMTP id 1F0831A07A3 for <ietf@ietf.org>; Tue, 25 Feb 2014 16:32:12 -0800 (PST)
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 4A42C8A031 for <ietf@ietf.org>; Wed, 26 Feb 2014 00:32:11 +0000 (UTC)
Date: Tue, 25 Feb 2014 19:32:09 -0500
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Message-ID: <20140226003151.GB38432@mx1.yitter.info>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com> <3FF3186251572A0DB04C2762@JcK-HP8200.jck.com> <530D11EA.2060404@dcrocker.net> <4dfe7ef03cbb4e08b9028a1b2e8dea3f@BLUPR05MB562.namprd05.prod.outlook.com> <530D291A.3040907@dcrocker.net> <b1d30944a246454b8cdddd2663e4346d@BLUPR05MB562.namprd05.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <b1d30944a246454b8cdddd2663e4346d@BLUPR05MB562.namprd05.prod.outlook.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/LqNaGCLChxQiJTBlG6-1uk5uLfA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 00:32:19 -0000

Hi,

On Tue, Feb 25, 2014 at 11:51:42PM +0000, John E Drake wrote:

> But you use the phrase "the way people have been" and then you list all of the terrible things of which these people have been guilty.  

As I tried to show in my previous note, the key point about _ad
hominem_ is that it's about relevance, not just about the person.

Suppose Andrew offers testimony that he saw Green Humpty Dumpty on the
wall this morning, and says it explains the green stain on the wall.
John says, "Andrew is a liar, because I have this secret letter from
him that I intercepted and that says he used green paint in his
graffiti on that wall; and also, I have this video capture from the
period in question that shows the wall with no Humpty Dumpty on it,
but shows Andrew painting the wall," that is not an _ad hominem_ no
matter how it impugns Andrew's integrity.  The counter-argument is
directly relevant to testing the truth of the testimony, and therefore
to undermining Andrew's conclusion.

The term "_ad hominem_" is not a four-dollar way to say "makes me feel
bad".  It is a particular kind of fallacy in which the fallacious
argument attacks the person speaking instead of the propositions in
question.  Saying, "John Sullivan is bald; you shouldn't believe his
hair tips," is a fallacy, because my father's manifest baldness is
just not related to whether his hair tips would be good for you.  (As
it happens, they wouldn't be.  But his baldness is not the reason you
should think that.  There are successful bald hairdressers.)

Whether a given bad argument is an _ad hominem_ or an appeal to
popularity or a (phony) appeal to authority -- or even a circular
argument ("begging the question") -- is just about the least
interesting question I can think to answer.  The issue when we are
having these kinds of discussion is whether a given argument is a good
one, and part of that evaluation has to be relevance, but getting the
classification just so is only fun for students of rhetoric.

All of that is, as John says elsewhere, also unrelated to whether we are
creating a chilly environment, harassing people, or welcoming people
into our standards-making activities.  I can -- and I bet you can too
-- construct a perfectly valid, relevant, and devastating argument
that is delivered in such a way as to wound the person whose argument
I am attacking.  And I can produce -- I bet you can too -- an argument
that is lousy, but that makes everyone in the room feel warm and
fuzzy.  These issues are very loosely coupled to whether something is
an _ad hominem_.  I think we ought to focus less on the classification
of boorish or ill-reasoned utterances and much more on the quality of
the reasoning and the openness of the presentation.

Best regards,

A


-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Tue Feb 25 16:42:06 2014
Return-Path: <pthaler@broadcom.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F326D1A02AA for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 16:42:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.547
X-Spam-Level: 
X-Spam-Status: No, score=-0.547 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ii25NhOKdeda for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 16:41:58 -0800 (PST)
Received: from mail-gw2-out.broadcom.com (mail-gw2-out.broadcom.com [216.31.210.63]) by ietfa.amsl.com (Postfix) with ESMTP id 192A31A0822 for <ietf@ietf.org>; Tue, 25 Feb 2014 16:41:58 -0800 (PST)
X-IronPort-AV: E=Sophos; i="4.97,543,1389772800"; d="scan'208,217"; a="16583514"
Received: from irvexchcas06.broadcom.com (HELO IRVEXCHCAS06.corp.ad.broadcom.com) ([10.9.208.53]) by mail-gw2-out.broadcom.com with ESMTP; 25 Feb 2014 16:57:42 -0800
Received: from SJEXCHCAS06.corp.ad.broadcom.com (10.16.203.14) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.3.174.1; Tue, 25 Feb 2014 16:41:34 -0800
Received: from SJEXCHMB09.corp.ad.broadcom.com ([fe80::3da7:665e:cc78:181f]) by SJEXCHCAS06.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0174.001; Tue, 25 Feb 2014 16:41:35 -0800
From: Pat Thaler <pthaler@broadcom.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, ietf <ietf@ietf.org>
Subject: RE: Policy of WG chairs in organising time for presentations and face2face discussions
Thread-Topic: Policy of WG chairs in organising time for presentations and face2face discussions
Thread-Index: AQHPMRKWgdgRJUuSBkWf6oWpXGOUVZrGsZtg
Date: Wed, 26 Feb 2014 00:41:34 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672B01A59D@SJEXCHMB09.corp.ad.broadcom.com>
References: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com>
In-Reply-To: <CADnDZ8_87HBzNXOWbG+3nsmDv0vLajf2m_ddhvgnwj03_wsH4A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
Content-Type: multipart/alternative; boundary="_000_EB9B93801780FD4CA165E0FBCB3C3E672B01A59DSJEXCHMB09corpa_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/iT6FdsgNlGZy3P70omqc-d6PZUY
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 00:42:04 -0000

--_000_EB9B93801780FD4CA165E0FBCB3C3E672B01A59DSJEXCHMB09corpa_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I'm not an IETF WG Chair, but I have attended IETF meetings for some time a=
nd have many years of experience chairing in other organizations.

A significant part of the job of a chair is facilitating sound progress of =
chartered work. Issues that haven't been resolved on the list may be comple=
x ones that take more than 10 minutes to understand and get to the heart of=
 differing viewpoints.  It is often more efficient to devote more meeting t=
ime to getting such issues sorted rather than to distribute meeting time ev=
enly across drafts.

Also, when a group has multiple drafts/projects to progress, it is often mo=
re efficient for the group to concentrate on drafts that are foundational (=
i.e. that need to be settled so that other work items can progress) or that=
 are close to done in order to finish those and be able to concentrate futu=
re efforts on the remaining items.

An even arbitrary distribution of time doesn't serve those purposes.

Pat

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun
Sent: Sunday, February 23, 2014 7:43 PM
To: ietf
Subject: Policy of WG chairs in organising time for presentations and face2=
face discussions

Dear IETF WGs' Chairs,

I suggest in London that you assign only maximum 10 minutes present per WG =
draft and maximum 5 minute for individual draft (as limit policy). We need =
to use more input and have more face2face (F2F) discussion in our meeting. =
I remember we discussed this before but it will be nice if we know what cha=
irs are thinking before few days of the meeting.

Meeting time is money and that we need to improve the use of IETF times wit=
hin F2F WG discussions and decisions.  If an author cannot describe issues =
of draft in 10 minutes then it will be difficult for the WG listeners to di=
scuss and make decisions within another 10 minutes per item. Please comment=
.

Best wishes,

Abdussalam

WG Meetings are needed for group interactions and group decisions not indiv=
idual presentations or individual decisions.

--_000_EB9B93801780FD4CA165E0FBCB3C3E672B01A59DSJEXCHMB09corpa_
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;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","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-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">I&#8217;m not an IETF WG Chair, but I h=
ave attended IETF meetings for some time and have many years of experience =
chairing in other organizations.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">A significant part of the job of a chai=
r is facilitating sound progress of chartered work. Issues that haven&#8217=
;t been resolved on the list may be complex ones that take more
 than 10 minutes to understand and get to the heart of differing viewpoints=
. &nbsp;It is often more efficient to devote more meeting time to getting s=
uch issues sorted rather than to distribute meeting time evenly across draf=
ts.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Also, when a group has multiple drafts/=
projects to progress, it is often more efficient for the group to concentra=
te on drafts that are foundational (i.e. that need to be
 settled so that other work items can progress) or that are close to done i=
n order to finish those and be able to concentrate future efforts on the re=
maining items.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">An even arbitrary distribution of time =
doesn&#8217;t serve those purposes.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;">Pat<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> ietf [ma=
ilto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Abdussalam Baryun<br>
<b>Sent:</b> Sunday, February 23, 2014 7:43 PM<br>
<b>To:</b> ietf<br>
<b>Subject:</b> Policy of WG chairs in organising time for presentations an=
d face2face discussions<o:p></o:p></span></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Dear IETF WGs' Chairs,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">I suggest in London&nbsp;that you assign only maximu=
m 10 minutes present per WG draft and maximum 5 minute for individual draft=
 (as limit policy).&nbsp;We need to use more input and have more face2face =
(F2F)&nbsp;discussion in our meeting. I remember
 we discussed this before but it will be nice if we know what chairs are th=
inking before few days of the meeting.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Meeting&nbsp;time&nbsp;is money and that we need to =
improve the&nbsp;use of&nbsp;IETF times&nbsp;within F2F&nbsp;WG&nbsp;discus=
sions and decisions.&nbsp;&nbsp;If an author cannot describe issues of&nbsp=
;draft in 10 minutes then it will be difficult for the WG&nbsp;listeners to=
 discuss and make
 decisions within another 10 minutes per item. Please comment.&nbsp;<o:p></=
o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Best wishes,<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Abdussalam<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">WG&nbsp;Meetings are =
needed for group&nbsp;interactions and group decisions&nbsp;not individual&=
nbsp;presentations or individual decisions.&nbsp;<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_EB9B93801780FD4CA165E0FBCB3C3E672B01A59DSJEXCHMB09corpa_--


From nobody Tue Feb 25 16:49:45 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 193681A033B for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 16:49:41 -0800 (PST)
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 9p_piwXWmB2j for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 16:49:37 -0800 (PST)
Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1AA4C1A01D5 for <ietf@ietf.org>; Tue, 25 Feb 2014 16:49:36 -0800 (PST)
Received: by mail-lb0-f175.google.com with SMTP id w7so124461lbi.20 for <ietf@ietf.org>; Tue, 25 Feb 2014 16:49:35 -0800 (PST)
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=nhKtrOQBJAVZASwHnIwP7BdhTPlQK3jF678hFpdk0iE=; b=HeRZ5LVNUwmb90v5g8skpID4BmVl0OeVYrWQAGW/PjjCLvhqpWE5zB3gVA47rkWcQ8 8o51K+bazZq7CnIfvam5vbW2nXUgaAbkr7gSDur6g7ffgjX29syiPNg3wf0c/m9xnGGA abpL3DyQv93XvQlnJGJNx4ayOJ3e8sTVyWJyrb1KfWoun40LeRI3+5Zm1HdE7NWElyBJ tDRoF40OA0DOnuvIyBJWsnlbxcws8DA4xQiAa1sYy50Sm7nAsysNDWr5dEHQHKL5bgZF zSrmQZwjzJjbSYmm+3DADPiMWVVgfzbZ8om6gjcaG00iAbQsL0V5yaMl5un0jSPWJ5Kd tbag==
MIME-Version: 1.0
X-Received: by 10.152.23.169 with SMTP id n9mr54224laf.45.1393375775228; Tue, 25 Feb 2014 16:49:35 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Tue, 25 Feb 2014 16:49:35 -0800 (PST)
In-Reply-To: <530D2813.1080304@gmail.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com>
Date: Tue, 25 Feb 2014 19:49:35 -0500
Message-ID: <CAMm+LwjWt-8KpA85bP5aF9Vryq8a=7Ou=QR6iZxr4rZPvJn19A@mail.gmail.com>
Subject: Re: A private club
From: Phillip Hallam-Baker <hallam@gmail.com>
To: Melinda Shore <melinda.shore@gmail.com>
Content-Type: multipart/alternative; boundary=089e0160b99a1f086104f344943e
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_VXtsZ5utK1UySJb_3113D6llUU
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, 26 Feb 2014 00:49:41 -0000

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

That is a polite fiction.

I have no doubt that the lawyers would find that we were members if it
suited them.

We don't have any rights, that is true enough.



On Tue, Feb 25, 2014 at 6:32 PM, Melinda Shore <melinda.shore@gmail.com>wrote:

> On 2/25/14 2:20 PM, S Moonesamy wrote:
> > If the IETF is a private club members can do whatever they want.  If the
> > IETF is an international organization there is an expectation that the
> > members will act in a professional manner when the situation warrants
> > it.
>
> The IETF does not have members.  This is not a minor point.
>
> Melinda
>
>
>


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

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

<div dir=3D"ltr">That is a polite fiction.<div><br></div><div>I have no dou=
bt that the lawyers would find that we were members if it suited them.</div=
><div><br></div><div>We don&#39;t have any rights, that is true enough.=A0<=
/div>
<div><br></div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail=
_quote">On Tue, Feb 25, 2014 at 6:32 PM, Melinda Shore <span dir=3D"ltr">&l=
t;<a href=3D"mailto:melinda.shore@gmail.com" target=3D"_blank">melinda.shor=
e@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 2/25/14 2:20 PM, S Moonesamy wrote:<br>
&gt; If the IETF is a private club members can do whatever they want. =A0If=
 the<br>
&gt; IETF is an international organization there is an expectation that the=
<br>
&gt; members will act in a professional manner when the situation warrants<=
br>
&gt; it.<br>
<br>
The IETF does not have members. =A0This is not a minor point.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Melinda<br>
<br>
<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r>Website: <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><=
br>
</div>

--089e0160b99a1f086104f344943e--


From nobody Tue Feb 25 17:28: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 808371A0831 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 17:28:27 -0800 (PST)
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 8HViK2LHvlbC for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 17:28:23 -0800 (PST)
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 ABB171A0830 for <ietf@ietf.org>; Tue, 25 Feb 2014 17:28:23 -0800 (PST)
Received: by mail-pb0-f47.google.com with SMTP id up15so234526pbc.34 for <ietf@ietf.org>; Tue, 25 Feb 2014 17:28:22 -0800 (PST)
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=B1XyejZBpX36mr3XB5XY3G1//K5xxRJruxgmdeNooaI=; b=QgC9uW/y3hl9jRxcPLqZgs3VDg5m90ez1p0lb3zw2DE3hDiWPFhnLCqdXfvxtS2SPo Wj+p6ndJ+5qZuqOVjX1hEO8b99LcyJU3b9LU98xz62Nr9DbjX2RUuGrASjAvC/tce7hK SX2MeJFIfZ28/omqs3+XWCqi2lE/HP10uenR5nwR9MRLU2AG8PJxrsKpanuYcpCxfjZn XysPCvuFwgs8Qys9zAQAmISfzzsfYeQTkTgbtELXbrZwWPez5a/1HHsAhLPAyMRHJzOi TEzFB2tXJszbbCdtvddzzumMQCnAvRwi5oekGLwD334kb00TBodBjB3TGBAApzttJhfR pDgg==
X-Received: by 10.68.0.35 with SMTP id 3mr3290786pbb.52.1393378102744; Tue, 25 Feb 2014 17:28:22 -0800 (PST)
Received: from [172.24.31.170] (wireless-nat-1.auckland.ac.nz. [130.216.30.112]) by mx.google.com with ESMTPSA id z3sm41768093pas.15.2014.02.25.17.28.20 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 25 Feb 2014 17:28:21 -0800 (PST)
Message-ID: <530D4337.9020505@gmail.com>
Date: Wed, 26 Feb 2014 14:28:23 +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: IAB <iab@iab.org>
Subject: Re: Call for Review of draft-iab-filtering-considerations-06.txt, "Technical Considerations for Internet Service Blocking and Filtering"
References: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org>
In-Reply-To: <C4DCDDAC-C2C9-4F10-BF19-BDFEBC28CB46@iab.org>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Uq6fPPWEKCX3wEH6QiaNQc8JSY4
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, 26 Feb 2014 01:28:28 -0000

Hi,

I'm assuming this document falls in the category of technical
advice under clause 2(e) of the IAB charter. Otherwise I'm
not quite sure what it's for. It would be good if the
Introduction said why the document is being published.
(It says who it is aimed at, but not why.)

> Restricting objectionable content or services.  Certain
>       communications may be viewed as undesirable, harmful, or illegal
>       by particular governments, enterprises, or users (e.g., parents).
>       Governments may seek to block communications that are deemed to be
>       defamation, hate speech, obscenity, intellectual property
>       infringement, or otherwise objectionable.  Enterprises may seek to
>       restrict employees from accessing content that is not deemed to be
>       work appropriate.  Parents may restrict their children from
>       accessing content or services targeted for adults.

I have a feeling that you should avoid all judgmental language
here. I suggest something *much* simpler, that doesn't speculate
about motivation:

Restricting unwanted content or services. Certain
 communications may be unwanted by particular governments,
 enterprises, or individual users (e.g., parents).

The technical content of the draft seems good to me, but
I'm a bit worried that in a year or two, we'll hear some
governments saying "Oh sure, we're blocking Facebook and
YouTube; we're fully conformant to RFC7xxx from the Internet
Architecture Board."

  Brian


From nobody Tue Feb 25 17:44:08 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 EE0051A0833 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 17:44:06 -0800 (PST)
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 6afCLxFWqgKL for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 17:44:04 -0800 (PST)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id C60F81A02B7 for <ietf@ietf.org>; Tue, 25 Feb 2014 17:44:04 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id i11so156877oag.37 for <ietf@ietf.org>; Tue, 25 Feb 2014 17:44:03 -0800 (PST)
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=C5KbSwsztCa+BYLomrfsuXdJw8NvqcX5/jsd95tVD9w=; b=HON3A+qRUdBlGVUWvE+mXFUeesL3Mrskpm+uoTanLZMH+ih6p8hCdBa/zBG92U+FyC 2WGxhxDi7DVCyq1mwkmTCapxW4P+clbZBGXeGhA5jTtWBoNhDMGdX/GTxJ6MeGDG+iI6 ZYMEd2trwV4TUnWCRZrY544CTUm/6sNsDIsV6mUx3Ky54+813Z7bP8zJPVC1lk/cpPwU 50S6LXA1nlWWVf7VF/S3+jk/KvliigSaSzhh06E6/zUGzCONWHBa649jGOp8aCR3RsUm mawGFZWUDrgyfBLIq6Ijc6V2V900x3RsbnrwdhQ651+u5EHkcoS/o4OQomojm2gjWCVW RPJA==
MIME-Version: 1.0
X-Received: by 10.60.98.240 with SMTP id el16mr4219694oeb.50.1393379043584; Tue, 25 Feb 2014 17:44:03 -0800 (PST)
Received: by 10.76.112.8 with HTTP; Tue, 25 Feb 2014 17:44:03 -0800 (PST)
In-Reply-To: <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com>
Date: Wed, 26 Feb 2014 02:44:03 +0100
Message-ID: <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com>
Subject: Re: Ad hominems
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Content-Type: multipart/alternative; boundary=089e011832a6ee44c704f345566b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mi7vg2nHhYjG8dvSZvfTCI8Zqjg
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, 26 Feb 2014 01:44:07 -0000

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

John,

The person have been in the IETF meeting remotely participating, and the
current WGs agenda is not known how it was organised so the suggestion was
based on past and current facts.

Readers may assume the person is not experience but why do they assume that
meeting don't need improvement or why they assume that current meeting
agenda cannot be commented on or why they assume that IETF meeting are
perfectly organised.

IMHO If the comment was from some one else, many will change their mind
just because he/she is popular experience not because of any other type
of experience.

AB

AB

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

John,<div><br></div>The person have been in the IETF meeting remotely parti=
cipating,=A0and the current WGs=A0agenda is not known how it was organised =
so the suggestion was based on past and current facts.=A0<div><br></div><di=
v>Readers may assume the person is not experience but why do they assume th=
at meeting don&#39;t need improvement or why they=A0assume that current=A0m=
eeting agenda cannot be commented on or why they assume that IETF meeting a=
re perfectly organised.=A0</div>
<div><br></div><div>IMHO=A0If the comment was from some one else, many will=
 change their=A0mind just because he/she is popular experience=A0not becaus=
e of any other=A0type of=A0experience.=A0</div><div><br></div><div>AB</div>=
<div><br>
</div><div>AB<br><div><br></div></div>

--089e011832a6ee44c704f345566b--


From nobody Tue Feb 25 17:47:15 2014
Return-Path: <jdrake@juniper.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 9D92F1A0836 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 17:47:14 -0800 (PST)
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, 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 3FJO4yNJHUxQ for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 17:47:12 -0800 (PST)
Received: from ch1outboundpool.messaging.microsoft.com (ch1ehsobe006.messaging.microsoft.com [216.32.181.186]) by ietfa.amsl.com (Postfix) with ESMTP id 4373A1A02B7 for <ietf@ietf.org>; Tue, 25 Feb 2014 17:47:12 -0800 (PST)
Received: from mail27-ch1-R.bigfish.com (10.43.68.236) by CH1EHSOBE012.bigfish.com (10.43.70.62) with Microsoft SMTP Server id 14.1.225.22; Wed, 26 Feb 2014 01:47:10 +0000
Received: from mail27-ch1 (localhost [127.0.0.1])	by mail27-ch1-R.bigfish.com (Postfix) with ESMTP id CF62918060B; Wed, 26 Feb 2014 01:47:10 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -26
X-BigFish: VPS-26(z569dhz8e8O9371Ic85fhzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1d7338h1de098h1033IL17326ah8275bh8275dh18c673h1de097h186068hz2fh109h2a8h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h20f0h2216h22d0h2336h2461h2487h24d7h2516h2545h255eh25cch9a9j1155h)
Received-SPF: pass (mail27-ch1: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(22804002)(189002)(199002)(19300405004)(76576001)(16236675002)(63696002)(74316001)(81686001)(31966008)(76786001)(15202345003)(76796001)(59766001)(51856001)(81816001)(79102001)(74366001)(65816001)(15975445006)(77982001)(74876001)(74706001)(83072002)(85852003)(66066001)(80022001)(90146001)(54356001)(94316002)(86362001)(95416001)(92566001)(85306002)(94946001)(69226001)(87266001)(19580405001)(19580395003)(76482001)(83322001)(54316002)(56776001)(56816005)(80976001)(53806001)(93516002)(93136001)(46102001)(47446002)(74662001)(33646001)(221733001)(2656002)(47736001)(47976001)(50986001)(81342001)(87936001)(74502001)(49866001)(95666003)(4396001)(81542001)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR05MB705; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.11; FPR:BC9E6AC5.8F3657C9.7C3F78B.DAE6E34D.201DA; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Received: from mail27-ch1 (localhost.localdomain [127.0.0.1]) by mail27-ch1 (MessageSwitch) id 1393379228152386_10943; Wed, 26 Feb 2014 01:47:08 +0000 (UTC)
Received: from CH1EHSMHS042.bigfish.com (snatpool1.int.messaging.microsoft.com [10.43.68.254])	by mail27-ch1.bigfish.com (Postfix) with ESMTP id 20B1D160238;	Wed, 26 Feb 2014 01:47:08 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by CH1EHSMHS042.bigfish.com (10.43.69.251) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 26 Feb 2014 01:47:02 +0000
Received: from BLUPR05MB705.namprd05.prod.outlook.com (10.141.207.11) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.423.0; Wed, 26 Feb 2014 01:47:02 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB705.namprd05.prod.outlook.com (10.141.207.11) with Microsoft SMTP Server (TLS) id 15.0.883.10; Wed, 26 Feb 2014 01:46:55 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0883.010; Wed, 26 Feb 2014 01:46:54 +0000
From: John E Drake <jdrake@juniper.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>, John C Klensin <john-ietf@jck.com>
Subject: RE: Ad hominems
Thread-Topic: Ad hominems
Thread-Index: AQHPMlMY1+1fMY6PIUGbeZ4hVqDQFZrGoAcAgAAjx4CAAABZIA==
Date: Wed, 26 Feb 2014 01:46:54 +0000
Message-ID: <0861b3e963fc43a5901de8ccba2d9e61@BLUPR05MB562.namprd05.prod.outlook.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com>
In-Reply-To: <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.11]
x-forefront-prvs: 0134AD334F
Content-Type: multipart/alternative; boundary="_000_0861b3e963fc43a5901de8ccba2d9e61BLUPR05MB562namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Net4Nl5VXOMziI8d_pm5CDpaqEs
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, 26 Feb 2014 01:47:14 -0000

--_000_0861b3e963fc43a5901de8ccba2d9e61BLUPR05MB562namprd05pro_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

AB,

As Dave Crocker wisely advised, there are situations in which it is best to=
 ignore the correspondent.

Yours Irrespectively,

John

From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun
Sent: Tuesday, February 25, 2014 5:44 PM
To: John C Klensin
Cc: ietf@ietf.org
Subject: Re: Ad hominems

John,

The person have been in the IETF meeting remotely participating, and the cu=
rrent WGs agenda is not known how it was organised so the suggestion was ba=
sed on past and current facts.

Readers may assume the person is not experience but why do they assume that=
 meeting don't need improvement or why they assume that current meeting age=
nda cannot be commented on or why they assume that IETF meeting are perfect=
ly organised.

IMHO If the comment was from some one else, many will change their mind jus=
t because he/she is popular experience not because of any other type of exp=
erience.

AB

AB


--_000_0861b3e963fc43a5901de8ccba2d9e61BLUPR05MB562namprd05pro_
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 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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
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;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.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"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">AB,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">As Dave Crocker wisely ad=
vised, there are situations in which it is best to ignore the correspondent=
.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">Yours Irrespectively,<o:p=
></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D">John<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1F497D"><o:p>&nbsp;</o:p></span><=
/p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.0pt;font-family:&quot=
;Calibri&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-=
size:11.0pt;font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;"> ietf [=
mailto:ietf-bounces@ietf.org]
<b>On Behalf Of </b>Abdussalam Baryun<br>
<b>Sent:</b> Tuesday, February 25, 2014 5:44 PM<br>
<b>To:</b> John C Klensin<br>
<b>Cc:</b> ietf@ietf.org<br>
<b>Subject:</b> Re: Ad hominems<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">John,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<p class=3D"MsoNormal">The person have been in the IETF meeting remotely pa=
rticipating,&nbsp;and the current WGs&nbsp;agenda is not known how it was o=
rganised so the suggestion was based on past and current facts.&nbsp;<o:p><=
/o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Readers may assume the person is not experience but =
why do they assume that meeting don't need improvement or why they&nbsp;ass=
ume that current&nbsp;meeting agenda cannot be commented on or why they ass=
ume that IETF meeting are perfectly organised.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">IMHO&nbsp;If the comment was from some one else, man=
y will change their&nbsp;mind just because he/she is popular experience&nbs=
p;not because of any other&nbsp;type of&nbsp;experience.&nbsp;<o:p></o:p></=
p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">AB<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">AB<o:p></o:p></p>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_0861b3e963fc43a5901de8ccba2d9e61BLUPR05MB562namprd05pro_--


From nobody Tue Feb 25 18:23:25 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 735AF1A0224 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 18:23:23 -0800 (PST)
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 xK04Jo4OmUAD for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 18:23:21 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.165]) by ietfa.amsl.com (Postfix) with ESMTP id 51DD31A02D7 for <ietf@ietf.org>; Tue, 25 Feb 2014 18:23:21 -0800 (PST)
Received: from [85.158.137.99:16414] by server-5.bemta-3.messagelabs.com id DC/F7-04712-7105D035; Wed, 26 Feb 2014 02:23:19 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-7.tower-217.messagelabs.com!1393381399!14861943!1
X-Originating-IP: [131.227.200.31]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23801 invoked from network); 26 Feb 2014 02:23:19 -0000
Received: from exht011p.surrey.ac.uk (HELO EXHT011P.surrey.ac.uk) (131.227.200.31) by server-7.tower-217.messagelabs.com with AES128-SHA encrypted SMTP; 26 Feb 2014 02:23:19 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT011P.surrey.ac.uk ([131.227.200.31]) with mapi; Wed, 26 Feb 2014 02:23:18 +0000
From: <l.wood@surrey.ac.uk>
To: <jdrake@juniper.net>, <john-ietf@jck.com>
Date: Wed, 26 Feb 2014 02:22:01 +0000
Subject: RE: Ad hominems
Thread-Topic: Ad hominems
Thread-Index: AQHPMlMY1+1fMY6PIUGbeZ4hVqDQFZrGoAcAgAAjx4CAAABZIIAACkM9
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334737@EXMB01CMS.surrey.ac.uk>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com>, <0861b3e963fc43a5901de8ccba2d9e61@BLUPR05MB562.namprd05.prod.outlook.com>
In-Reply-To: <0861b3e963fc43a5901de8ccba2d9e61@BLUPR05MB562.namprd05.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/STsDFPPNg_kHJk2OQYdLPRecBwk
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, 26 Feb 2014 02:23:23 -0000

> As Dave Crocker wisely advised, there are situations in which it is best =
to ignore the correspondent.

Of course, ignoring the correspondent, rather than the correspondence, woul=
d be an
ad-hominem response. Which would be unacceptable. No?

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of John E Drake [jdrake@junipe=
r.net]
Sent: 26 February 2014 01:46
To: Abdussalam Baryun; John C Klensin
Cc: ietf@ietf.org
Subject: RE: Ad hominems

AB,

As Dave Crocker wisely advised, there are situations in which it is best to=
 ignore the correspondent.

Yours Irrespectively,

John


From nobody Tue Feb 25 18:33:00 2014
Return-Path: <jdrake@juniper.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 DE9AD1A0396 for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 18:32:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.949
X-Spam-Level: 
X-Spam-Status: No, score=-2.949 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, UNRESOLVED_TEMPLATE=1.252] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iCbMGiddkRch for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 18:32:55 -0800 (PST)
Received: from co9outboundpool.messaging.microsoft.com (co9ehsobe003.messaging.microsoft.com [207.46.163.26]) by ietfa.amsl.com (Postfix) with ESMTP id AC2431A0224 for <ietf@ietf.org>; Tue, 25 Feb 2014 18:32:55 -0800 (PST)
Received: from mail1-co9-R.bigfish.com (10.236.132.236) by CO9EHSOBE004.bigfish.com (10.236.130.67) with Microsoft SMTP Server id 14.1.225.22; Wed, 26 Feb 2014 02:32:54 +0000
Received: from mail1-co9 (localhost [127.0.0.1])	by mail1-co9-R.bigfish.com (Postfix) with ESMTP id 70C444002AE;	Wed, 26 Feb 2014 02:32:54 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT001.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -21
X-BigFish: VPS-21(z569dhz9371I542I1432Izz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h2189h1d1ah1d2ah21bch1fc6hzz1730fah1de098h1033IL177df4h17326ah8275bh8275dh1de097h186068hz2fh109h2a8h839h944hd24hf0ah1220h1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1fe8h1ff5h2216h22d0h2336h2461h2487h24ach24d7h2516h2545h255eh25cch9a9j1155h)
Received-SPF: pass (mail1-co9: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=jdrake@juniper.net; helo=BL2PRD0510HT001.namprd05.prod.outlook.com ; .outlook.com ; 
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(10009001)(6009001)(377454003)(13464003)(199002)(189002)(51704005)(87266001)(19580405001)(76482001)(19580395003)(54316002)(56776001)(83322001)(69226001)(94946001)(86362001)(85306002)(95416001)(94316002)(87936001)(2656002)(81342001)(221733001)(50986001)(47736001)(47976001)(49866001)(4396001)(81542001)(47446002)(74502001)(31966008)(93136001)(59766001)(51856001)(46102001)(53806001)(93516002)(80976001)(33646001)(54356001)(92566001)(81816001)(79102001)(15198665003)(77982001)(15975445006)(74366001)(63696002)(74316001)(81686001)(76576001)(15202345003)(15395725003)(76796001)(76786001)(74662001)(80022001)(66066001)(65816001)(56816005)(85852003)(74706001)(74876001)(83072002)(90146001)(95666003)(24736002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR05MB770; H:BLUPR05MB562.namprd05.prod.outlook.com; CLIP:66.129.241.11; FPR:301AC37D.3E2757CA.13E3339B.D8A2200F.20161; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Received: from mail1-co9 (localhost.localdomain [127.0.0.1]) by mail1-co9 (MessageSwitch) id 1393381972681663_22316; Wed, 26 Feb 2014 02:32:52 +0000 (UTC)
Received: from CO9EHSMHS031.bigfish.com (unknown [10.236.132.235])	by mail1-co9.bigfish.com (Postfix) with ESMTP id 980A134008B;	Wed, 26 Feb 2014 02:32:52 +0000 (UTC)
Received: from BL2PRD0510HT001.namprd05.prod.outlook.com (157.56.240.101) by CO9EHSMHS031.bigfish.com (10.236.130.41) with Microsoft SMTP Server (TLS) id 14.16.227.3; Wed, 26 Feb 2014 02:32:52 +0000
Received: from BLUPR05MB770.namprd05.prod.outlook.com (10.141.209.25) by BL2PRD0510HT001.namprd05.prod.outlook.com (10.255.100.36) with Microsoft SMTP Server (TLS) id 14.16.423.0; Wed, 26 Feb 2014 02:32:49 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com (10.141.202.141) by BLUPR05MB770.namprd05.prod.outlook.com (10.141.209.25) with Microsoft SMTP Server (TLS) id 15.0.883.10; Wed, 26 Feb 2014 02:32:48 +0000
Received: from BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) by BLUPR05MB562.namprd05.prod.outlook.com ([10.141.202.141]) with mapi id 15.00.0883.010; Wed, 26 Feb 2014 02:32:49 +0000
From: John E Drake <jdrake@juniper.net>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "john-ietf@jck.com" <john-ietf@jck.com>
Subject: RE: Ad hominems
Thread-Topic: Ad hominems
Thread-Index: AQHPMlMY1+1fMY6PIUGbeZ4hVqDQFZrGoAcAgAAjx4CAAABZIIAACkM9gAAC8wA=
Date: Wed, 26 Feb 2014 02:32:48 +0000
Message-ID: <59391171f1bf443395b3c6c20fc7f747@BLUPR05MB562.namprd05.prod.outlook.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com>, <0861b3e963fc43a5901de8ccba2d9e61@BLUPR05MB562.namprd05.prod.outlook.com> <290E20B455C66743BE178C5C84F1240847E6334737@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334737@EXMB01CMS.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [66.129.241.11]
x-forefront-prvs: 0134AD334F
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-FOPE-CRA-Verdict: 157.56.240.101$surrey.ac.uk%13189%4%DuplicateDomain-c684c95e-93ad-459f-9d80-96fa46cd75af.juniper.net%False%False%0$
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
X-FOPE-CONNECTOR: Id%0$Dn%SURREY.AC.UK$RO%1$TLS%0$FQDN%$TlsDn%
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/cJ4ibOz-dNRABLRGHnmX22hW62E
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, 26 Feb 2014 02:32:58 -0000

Speak to Dave.

Yours Irrespectively,

John

> -----Original Message-----
> From: l.wood@surrey.ac.uk [mailto:l.wood@surrey.ac.uk]
> Sent: Tuesday, February 25, 2014 6:22 PM
> To: John E Drake; john-ietf@jck.com
> Cc: ietf@ietf.org
> Subject: RE: Ad hominems
>=20
> > As Dave Crocker wisely advised, there are situations in which it is bes=
t to
> ignore the correspondent.
>=20
> Of course, ignoring the correspondent, rather than the correspondence, wo=
uld
> be an ad-hominem response. Which would be unacceptable. No?
>=20
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: ietf [ietf-bounces@ietf.org] On Behalf Of John E Drake
> [jdrake@juniper.net]
> Sent: 26 February 2014 01:46
> To: Abdussalam Baryun; John C Klensin
> Cc: ietf@ietf.org
> Subject: RE: Ad hominems
>=20
> AB,
>=20
> As Dave Crocker wisely advised, there are situations in which it is best =
to
> ignore the correspondent.
>=20
> Yours Irrespectively,
>=20
> John
>=20



From nobody Tue Feb 25 18:35:28 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 99AE21A038D for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 18:35:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O0altxN_-DYR for <ietf@ietfa.amsl.com>; Tue, 25 Feb 2014 18:35:25 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id BD2D61A0383 for <ietf@ietf.org>; Tue, 25 Feb 2014 18:35:25 -0800 (PST)
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 1WIUL8-0005CA-Df; Wed, 26 Feb 2014 02:35:19 +0000
Date: Wed, 26 Feb 2014 10:35:16 +0800
Message-ID: <m27g8imwij.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John E Drake <jdrake@juniper.net>
Subject: Re: Ad hominems
In-Reply-To: <59391171f1bf443395b3c6c20fc7f747@BLUPR05MB562.namprd05.prod.outlook.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.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/5CH2rJ1LbL6fYagAPoojXsQpxCc
Cc: John C Klensin <john-ietf@jck.com>, 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, 26 Feb 2014 02:35:26 -0000

> Speak to Dave.

who's dave?


From nobody Wed Feb 26 02:07:32 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 F0F141A01E9 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 02:07:23 -0800 (PST)
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 mZPDAZrOy1Eo for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 02:07:23 -0800 (PST)
Received: from mail-oa0-x230.google.com (mail-oa0-x230.google.com [IPv6:2607:f8b0:4003:c02::230]) by ietfa.amsl.com (Postfix) with ESMTP id 3FD381A01E6 for <ietf@ietf.org>; Wed, 26 Feb 2014 02:07:23 -0800 (PST)
Received: by mail-oa0-f48.google.com with SMTP id m1so583385oag.7 for <ietf@ietf.org>; Wed, 26 Feb 2014 02:07:22 -0800 (PST)
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=OVYzkNmBbDk48DYYYYtw7waZ7smXfvIb9+XwzIIxuM8=; b=ge15jRjMmQTDcUwnDC3OhRFPp9lCdlgoBFCl+R0WM1lS5mq7AdMAR6YLgrA7iKTL9h 4PYuJMHUyFHcAH53ArDffjA6y2g9bAW1q6SGWd6wLV/S9J13G764NTS5EMYwtiu1odNh uZW0RSZmf0MZTLeK4KUDDOH+1H389TeI8kBRE=
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=OVYzkNmBbDk48DYYYYtw7waZ7smXfvIb9+XwzIIxuM8=; b=eYOwMBrBNv2aoRPA+5J3V0uPxDnPjklKhIGa9TYfH4i2QnzVE3rD4iz2gnHrgNTmlu 0J/21DLwYve3/pG+vUwDKUpGacNv4KHISxT8BGz2QZWJoHiIbuzLx9DmowKNF67RMGX/ A3m90KwU5sN8WwPckb08eKj41zjeslRWq7nDG9+JUluxvhOS3f0+gBVUea2pqZn6gTwy YoAbYNA+EW5G4FCi+TEQ2OnLPL6LjVv6a0aEi9UP8+Eg/lu3qyyvHvEsjFyzRYSmO/fQ xUWvRh1/6wyDJjiDb/Q5ZJoGHQiiALIuXVWqz2fuKbjIj23yDcoLwZq6gFwSwObPFHj2 dXQQ==
X-Gm-Message-State: ALoCoQknn42Nf7ztqflZWDxmvqbcWWm+W3z+LBC4BmL/sxJTUlVf6t+0+TwqhGc3xJEVwZVGRotK
MIME-Version: 1.0
X-Received: by 10.182.196.3 with SMTP id ii3mr2040518obc.11.1393409242055; Wed, 26 Feb 2014 02:07:22 -0800 (PST)
Received: by 10.60.55.197 with HTTP; Wed, 26 Feb 2014 02:07:21 -0800 (PST)
In-Reply-To: <m27g8imwij.wl%randy@psg.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com> <59391171f1bf443395b3c6c20fc7f747@BLUPR05MB562.namprd05.prod.outlook.com> <m27g8imwij.wl%randy@psg.com>
Date: Wed, 26 Feb 2014 10:07:21 +0000
Message-ID: <CAKHUCzwyWqa5ovwbOAj27rcP_QbVLDWUdaRWTAMBLV48V4o7JA@mail.gmail.com>
Subject: Re: Ad hominems
From: Dave Cridland <dave@cridland.net>
To: Randy Bush <randy@psg.com>
Content-Type: multipart/alternative; boundary=089e015383e4e6576104f34c5e46
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/r-iber0xAk9QbYOw__CtJkHMWgw
Cc: John C Klensin <john-ietf@jck.com>, 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, 26 Feb 2014 10:07:24 -0000

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

Pretty much everyone.


On Wed, Feb 26, 2014 at 2:35 AM, Randy Bush <randy@psg.com> wrote:

> > Speak to Dave.
>
> who's dave?
>
>

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

<div dir=3D"ltr"><div>Pretty much everyone.</div></div><div class=3D"gmail_=
extra"><br><br><div class=3D"gmail_quote">On Wed, Feb 26, 2014 at 2:35 AM, =
Randy Bush <span dir=3D"ltr">&lt;<a href=3D"mailto: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:1p=
x #ccc solid;padding-left:1ex">&gt; Speak to Dave.<br>
<br>
who&#39;s dave?<br>
<br>
</blockquote></div><br></div>

--089e015383e4e6576104f34c5e46--


From nobody Wed Feb 26 02:10:57 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 652061A01DA for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 02:10:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 vfbllqgdbN1c for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 02:10:48 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 68CB21A019D for <ietf@ietf.org>; Wed, 26 Feb 2014 02:10:48 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1QAASZh013398 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Feb 2014 02:10:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393409440; bh=S9sl/oQ1pkYlvx5gfaNBJkmGzaWtqksCOlXE353mJwE=; h=Date:To:From:Subject:In-Reply-To:References; b=EKKtdEe4STZriys5PFFQfEfVdY2RS0ZagpaiqGetNdUCYyV1X5p8o9kgbMrcbxzpz qE0GVPGLBrDjV5HjN28B0lIOBMweXSRXwXBjbiJ4QXlK6DjllsDpNoBIdg70D02lYE gzAUiYOPNQZr1D5yQmFq5bIrq197hxZGDVTzgSZE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393409440; i=@elandsys.com; bh=S9sl/oQ1pkYlvx5gfaNBJkmGzaWtqksCOlXE353mJwE=; h=Date:To:From:Subject:In-Reply-To:References; b=Jt648ksnf45N5wzr4xRELEwx66Lze1uT7LpZHylpe2Np06AO+g2btXOelq8oK0MqG pyc3ia5Y9Z7o6sIFgt00+/sXdeYzFTmy+Lwmpag3E/VKC0ZD3y69cAwXkI84CxDwrD 9e5ue/Dg/o0xjEWKwy+8N6xSQgAgDjtI2G5EATMk=
Message-Id: <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 26 Feb 2014 00:34:15 -0800
To: Melinda Shore <melinda.shore@gmail.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
In-Reply-To: <530D2813.1080304@gmail.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/_cnen9Gll3nkWBBmfcKPt0fDfMI
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 10:10:52 -0000

Hi Melinda,
At 15:32 25-02-2014, Melinda Shore wrote:
>The IETF does not have members.  This is not a minor point.

I should have written:

   the individuals will act in a professional manner when the situation
   warrants it.

I am not comfortable stating that there is consensus on an 
Internet-Draft when participation is from a small number of 
individuals having some affiliation in common.  That creates an 
appearance of a private club.

It is difficult to convince someone who is, for example, from a 
developing country that the IETF is a large open international 
community when a quick look at 
http://www.ietf.org/mail-archive/web/ietf/current/maillist.html shows 
that there has only been participation from individuals from one or 
two countries.

It might be that the meaning of "situation" in my previous message 
was unclear.  I'll use 
http://www.ietf.org/mail-archive/web/hybi/current/msg03047.html as an 
example to illustrate what I was thinking about.  One of the 
difficulties in resolving a situation is figuring out how to avoid 
the perception of a private club.

Regards,
S. Moonesamy 


From nobody Wed Feb 26 03:13:23 2014
Return-Path: <drc@virtualized.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 D0FE71A025A for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 03:13:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.448
X-Spam-Level: 
X-Spam-Status: No, score=-2.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.547, 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 OPxwqpzrR55Q for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 03:13:15 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id ED69A1A0255 for <ietf@ietf.org>; Wed, 26 Feb 2014 03:13:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 5A89C86719; Wed, 26 Feb 2014 06:13:12 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 30227-05; Wed, 26 Feb 2014 06:13:10 -0500 (EST)
Received: from [10.111.40.148] (unknown [60.52.197.44]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 8ACD5866C8; Wed, 26 Feb 2014 06:12:58 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_3038147E-E92B-4707-8047-23B511A0C9B2"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Ad hominems
From: David Conrad <drc@virtualized.org>
In-Reply-To: <CAKHUCzwyWqa5ovwbOAj27rcP_QbVLDWUdaRWTAMBLV48V4o7JA@mail.gmail.com>
Date: Wed, 26 Feb 2014 19:12:34 +0800
Message-Id: <4A10919E-BE9F-42C5-9032-9DBFA6A8EC15@virtualized.org>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com> <59391171f1bf443395b3c6c20fc7f747@BLUPR05MB562.namprd05.prod.outlook.com> <m27g8imwij.wl%randy@psg.com> <CAKHUCzwyWqa5ovwbOAj27rcP_QbVLDWUdaRWTAMBLV48V4o7JA@mail.gmail.com>
To: Dave Cridland <dave@cridland.net>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/135vqNPrA7QsgAbPSoTZ6jRgZjE
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, 26 Feb 2014 11:13:18 -0000

--Apple-Mail=_3038147E-E92B-4707-8047-23B511A0C9B2
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_723D8D5D-107A-494F-9B9A-2FD2DE7EF8AE"


--Apple-Mail=_723D8D5D-107A-494F-9B9A-2FD2DE7EF8AE
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=iso-8859-1

On Feb 26, 2014, at 6:07 PM, Dave Cridland <dave@cridland.net> wrote:
> Pretty much everyone.
> 
> On Wed, Feb 26, 2014 at 2:35 AM, Randy Bush <randy@psg.com> wrote:
> > Speak to Dave.
> 
> who's dave?
> 
> 

+1

Regards,
-drc


--Apple-Mail=_723D8D5D-107A-494F-9B9A-2FD2DE7EF8AE
Content-Transfer-Encoding: 7bit
Content-Type: text/html;
	charset=iso-8859-1

<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">On Feb 26, 2014, at 6:07 PM, Dave Cridland &lt;<a href="mailto:dave@cridland.net">dave@cridland.net</a>&gt; wrote:<div><blockquote type="cite"><div dir="ltr">Pretty much everyone.</div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 26, 2014 at 2:35 AM, Randy Bush <span dir="ltr">&lt;<a href="mailto:randy@psg.com" target="_blank">randy@psg.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; position: static; z-index: auto;">&gt; Speak to Dave.<br>
<br>
who's dave?<br>
<br>
</blockquote></div><br></div>
</blockquote></div><br><div>+1</div><div><br></div><div>Regards,</div><div>-drc</div><div><br></div></body></html>
--Apple-Mail=_723D8D5D-107A-494F-9B9A-2FD2DE7EF8AE--

--Apple-Mail=_3038147E-E92B-4707-8047-23B511A0C9B2
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

iQEcBAEBAgAGBQJTDcwmAAoJENV6ebf0/4rXXfAH/0SU49F/BAyxEmMgMQMtQYRt
vHSsNKywR6mqhNH4MIwfqPkfRBOqp/yyU5vWTSo6S0FPyl+wChrK2wm+rb1ykPp7
dg1j/8oqy/TJv/BNJmJhXexrd7E6pkJuWiGCUoROgTN2k0a64cX955P0MHougSsG
QvYcyZ5FiQf8fgBRXgDsGPv/3/5rfNfylK8HLjaZKVeqkYtPkeNf9L+CVOuL/G+d
Jm4uAmhCN4ZCJeXDmxGYi6xRRCJ29pls+v2u+bRoZYY5s6niVOt19RVBIydfrL4H
h/DG3J2bTvtHs6HnsuDZRC+X7SNKUqjmGZnUaCuQXXNVuATC0SBbKplaHWlDTiM=
=Vch/
-----END PGP SIGNATURE-----

--Apple-Mail=_3038147E-E92B-4707-8047-23B511A0C9B2--


From nobody Wed Feb 26 03:51:12 2014
Return-Path: <izaac@setec.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 EFCE11A028E for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 03:51:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.549
X-Spam-Level: 
X-Spam-Status: No, score=-0.549 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Kv0NA-LRkhJF for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 03:51:07 -0800 (PST)
Received: from abbott.setec.org (abbott.setec.org [64.90.166.179]) by ietfa.amsl.com (Postfix) with ESMTP id 1893A1A0068 for <ietf@ietf.org>; Wed, 26 Feb 2014 03:51:07 -0800 (PST)
Received: from 154-62-165-21.pools.spcsdns.net (66-87-128-154.pools.spcsdns.net [66.87.128.154]) by abbott.setec.org (Postfix) with ESMTPSA id 45E1FC698 for <ietf@ietf.org>; Wed, 26 Feb 2014 06:51:05 -0500 (EST)
User-Agent: Kaiten Mail
In-Reply-To: <m27g8imwij.wl%randy@psg.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com> <m27g8imwij.wl%randy@psg.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Subject: Re: Ad hominems
From: Izaac <izaac@setec.org>
Date: Wed, 26 Feb 2014 06:51:02 -0500
To: IETF <ietf@ietf.org>
Message-ID: <eafd3372-12d7-4e6c-a9c3-cd4e97aeb440@email.android.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VS0rLFf8NrX_0BVVU55q2nE-nyo
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 11:51:10 -0000

Randy Bush <randy@psg.com> wrote:
>> Speak to Dave.
>
>who's dave?

Dave's not here, man.

-- 
Izaac


From nobody Wed Feb 26 05:16:37 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 4DD741A030B for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 05:16:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.447
X-Spam-Level: 
X-Spam-Status: No, score=-0.447 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qci64Ly5qyvM for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 05:16:29 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 54DC41A02F5 for <ietf@ietf.org>; Wed, 26 Feb 2014 05:16:29 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WIeLa-000Jxj-Gx; Wed, 26 Feb 2014 08:16:26 -0500
Date: Wed, 26 Feb 2014 08:16:04 -0500
From: John C Klensin <john-ietf@jck.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Subject: Knowledge and suggestions (was: Re: Ad hominems)
Message-ID: <F07E5EA375E40279ACE7646E@JcK-HP8200.jck.com>
In-Reply-To: <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/635TWSIkkYgLMdjz17VCsHKgX5w
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, 26 Feb 2014 13:16:33 -0000

Changing the subject line and moving away from debates about
logic fallacies and attacks...

--On Wednesday, February 26, 2014 02:44 +0100 Abdussalam Baryun
<abdussalambaryun@gmail.com> wrote:

> John,
> 
> The person have been in the IETF meeting remotely
> participating, and the current WGs agenda is not known how it
> was organised so the suggestion was based on past and current
> facts.

Actually, in many WGs, those who have been actively
participating in the WG are fairly aware of how the agenda was
constructed and organized.  Many WG chairs ask for agenda
suggestions before the agenda is posted, others conclude (as I
often have) that the work of the WG makes the agenda obvious and
not worth wasting list time on [1].  Once the preliminary agenda
for a WG meeting is posted, WG participants are free to ask
questions about it or even to challenge it [2].   It the agenda
is not posted, even after complaints within the WG or
suggestions for changes are ignored, it is entirely reasonable
and appropriate to immediately involve the AD, questioning
whether the WG Chair(s) need additional supervision and/or their
appropriateness for the role.

In all of the above, WGs differ.  Some have many agenda items,
some only a few.  Some are at stages in their work where they
consider tutorial-style presentations appropriate, others have
specific issues that they need to be discuss and need to assume
that anyone with an interest in participating (rather than
merely observing) will have read (and made a serious effort to
understand) the relevant drafts.  In some, there is a lot of
room for improvement in how those norms and expectations are
communicated within the WG; others do well about that.   The
existence of those differences has been discussed often enough
on this list that I believe it is reasonable to expect those who
have participated in more than two or three meetings, even
remotely, and who take their participation seriously and expect
other to do so, to understand it.

Those differences, and that presumption of understanding, means
that any "all WGs should do X" suggestion is immediately
suspect, independent of who makes it or the value of "X".
"Suspect" doesn't mean it is necessarily wrong or a bad idea,
just that it will get a lot more scrutiny and that someone
making the proposal would be well-advised to provide more
extensive explanation and rationale when the suggestion is made.
If that isn't present, the person making the suggestion is
likely to discover that some of us respond with too-long notes
(like this one) that explore the details and that others respond
with short comments or questions that can easily be mistaken for
attacks on the proposer whether that is intended or not.  I'm
sure there is a happy middle ground but many of us, in part due
to lack of time, aren't good at consistently finding it.

> Readers may assume the person is not experience but why do
> they assume that meeting don't need improvement or why they
> assume that current meeting agenda cannot be commented on or
> why they assume that IETF meeting are perfectly organised.

I think you are making assumptions in the paragraph above that
are symptomatic of why you then perceive yourself as being
mistreated.  I've been around the community for some years, have
participated in multiple WGs, authored or edited multiple
documents, and held a few WG Chair and other "leadership"
positions.   I don't think I've run into anyone with significant
IETF experience who believes the system (or meetings in
particular) would not benefit from improvements.  There is less
agreement about what those improvements should be, as some
spectacular failures in process change efforts demonstrate.
Similarly, no one I know of assumes that focused comments on the
meeting agenda are out of order.  There are typically many
comments on the IETF list about ordering of meetings and
conflicts among WG slots; if you had visibility into the WG
Chairs list (see note [2] below), you would have seen far more.
And comments on particular WG agendas are very much in order
within those WGs, as discussed above.

The key problem with your comment/suggestion, stripped of all of
the (IMO) emotional and peripheral comments that followed
(relevant or not), was that it made (or appeared to make) a
blanket suggestion of a change for all WGs without nearly enough
argument or explanation _within the proposal note_ to overcome
the strong presumption that WGs differ sufficiently that no
suggestion about agenda constraints is applicable to all of
them.  I note that, while much of the community agrees in
principle that extensive "presentations" in WG sessions are bad
news, ideas to ban them have gotten no traction for much the
same reason.

> IMHO If the comment was from some one else, many will change
> their mind just because he/she is popular experience not
> because of any other type of experience.

For the reasons given above, I just do not believe that.  If
that exact same comment had come, e.g., from Dave Crocker or
myself, the substantive response that it was not a useful idea
would almost certainly have been identical.  There would be a
difference: many members of the community feel far more freedom
to heap abuse on Dave and myself (and sometimes we on each
other) when we suggest something about which the community
thinks we should have known better than they would do with
someone whose experience in the community is less deep and
tested.

I look forward to meeting you in person next week.
best,
   john





[1] Perhaps, in the quest for transparency, that is bad judgment
although, as usual, I remain instinctively opposed to more rigid
rules.  For the same reason and because most WG chairs don't
need extra work, I'm instinctively opposed to rules that would
require the WG chair(s) to explain the agenda choices when the
preliminary agenda is posted.  Both of those topics might well
benefit from additional discussion among those who are
interested (I hope not on the IETF list).

[2]  These kinds of topics in WG leadership and management are
among those that are periodically discussed on the WG Chairs
list and training sessions.  For reasons of efficiency and to
avoid various sorts of disruption and attacks (neither of which
is an entirely theoretical problem) that list and those sessions
are limited to WG Chairs (and the IAB and IESG).   From time to
time, I've advocated making the mailing list or its archives
available on a read-only basis to the broader community and/or
broadcasting the training sessions on an informational,
listen-only, basis.  I think that either or both might improve
transparency and understanding of what WG Chairs do and why, but
have never pressed the idea when it hasn't gotten traction.
IESG and EDU team, perhaps it is time to consider it.


From nobody Wed Feb 26 05:32:32 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 49EE61A031F for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 05:32:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 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.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xmmFbBAs3N_O for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 05:32:23 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC56D1A0325 for <ietf@ietf.org>; Wed, 26 Feb 2014 05:32:23 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1QDWAmr003863 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf@ietf.org>; Wed, 26 Feb 2014 05:32:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393421542; bh=pYOkpDQAxB8EIOy9YCB5dRFYeWK5NpPW6AkzxhOQzOQ=; h=Date:To:From:Subject:In-Reply-To:References; b=hap4uZPtvO48Rgh/iv2owx8YLxXwMcgKhNTKWsNW+fxQ4e/LBU/d7ykCKODdzLtps bgA1dnUzk+XjwnFuK8q2hckFgDCQ8pWa+R2xjqvihCwS+WGqXveFrFLdhwO+pczwPD bk9r1h4LmvNh2fiTfVpLohnnquifDWLw2vrWq5Ns=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393421542; i=@elandsys.com; bh=pYOkpDQAxB8EIOy9YCB5dRFYeWK5NpPW6AkzxhOQzOQ=; h=Date:To:From:Subject:In-Reply-To:References; b=MDs7gXp6udwgcqOulVbTwM80QznJSPX4zf+kMgMPF5OuXOw1evlfyEFGRuIRIjurO 7TSKSG4q2m6/c/JgRdOK8Psi1yXYofln8c/d7rue2Dyb94ut3JhWC0avSU5pvHnKnQ baD4tDCaoF4kzYQl/YBm8RwhwLFLU4/MTdWZ/6kw=
Message-Id: <6.2.5.6.2.20140226043234.0d0a0f60@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 26 Feb 2014 05:29:48 -0800
To: ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
In-Reply-To: <m2zjleji25.wl%randy@psg.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <m2zjleji25.wl%randy@psg.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/pntnIFMB8fg8z7_Q6TUYWkEL0ic
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 13:32:28 -0000

Hello,

I received a private comment which contained some some advice about 
IETF process in response to the message at 
http://www.ietf.org/mail-archive/web/ietf/current/msg86321.html  That 
advice contradicts the advice provided by participants who are also 
Area Directors.

In my opinion such occurrences can cause confusion for the average 
participant as it is difficult to know whom to believe.  It can be 
even more difficult for people who reside in some parts of the world 
due to cultural differences.

Regards,
S. Moonesamy


From nobody Wed Feb 26 05:57:30 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 494C81A0363 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 05:57:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.917
X-Spam-Level: **
X-Spam-Status: No, score=2.917 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hdiOGLfn30dI for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 05:57:24 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 72CB61A00B9 for <ietf@ietf.org>; Wed, 26 Feb 2014 05:57:24 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1QDv5FF009337; Wed, 26 Feb 2014 13:57:05 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1QDuxxD009323 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Feb 2014 13:57:04 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'S Moonesamy'" <sm+ietf@elandsys.com>, <ietf@ietf.org>
Subject: Clarifying IETF process [Was: A private club]
Date: Wed, 26 Feb 2014 13:57:00 -0000
Message-ID: <0e3601cf32fa$a1de7fc0$e59b7f40$@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: Ac8y+k5f6R9rRS4nTrCwv68mb3KO+A==
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7jpJKqXDrhy-IykCD7CQZUZ71rs
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: Wed, 26 Feb 2014 13:57:26 -0000

Hello SM,

The point you make in your second paragraph is very valid, but it is hard to
comment on your first paragraph without details.

Would you care to phrase the issue succinctly so that a (moderately) definitive
statement can be made?

Thanks,
Adrian

> Hello,
> 
> I received a private comment which contained some some advice about
> IETF process in response to the message at
> http://www.ietf.org/mail-archive/web/ietf/current/msg86321.html  That
> advice contradicts the advice provided by participants who are also
> Area Directors.
> 
> In my opinion such occurrences can cause confusion for the average
> participant as it is difficult to know whom to believe.  It can be
> even more difficult for people who reside in some parts of the world
> due to cultural differences.
> 
> Regards,
> S. Moonesamy


From nobody Wed Feb 26 05:59:42 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 24C171A0363 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 05:59:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.447
X-Spam-Level: 
X-Spam-Status: No, score=-0.447 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JPScOWKNNrD1 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 05:59:34 -0800 (PST)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0F4F01A035C for <ietf@ietf.org>; Wed, 26 Feb 2014 05:59:34 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WIf1H-000K0r-Vz; Wed, 26 Feb 2014 08:59:31 -0500
Date: Wed, 26 Feb 2014 08:59:10 -0500
From: John C Klensin <john-ietf@jck.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
Message-ID: <884F51283FE98A20FB8E7EC2@JcK-HP8200.jck.com>
In-Reply-To: <6.2.5.6.2.20140226043234.0d0a0f60@elandnews.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <m2zjleji25.wl%randy@psg.com> <6.2.5.6.2.20140226043234.0d0a0f60@elandnews.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/JgJDdJIDzRWXygpy7jkNDXFJ1dg
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, 26 Feb 2014 13:59:38 -0000

--On Wednesday, February 26, 2014 05:29 -0800 S Moonesamy
<sm+ietf@elandsys.com> wrote:

> Hello,
> 
> I received a private comment which contained some some advice
> about IETF process in response to the message at
> http://www.ietf.org/mail-archive/web/ietf/current/msg86321.htm
> l  That advice contradicts the advice provided by participants
> who are also Area Directors.

Subramanian,

Without details, the above is indistinguishable from innuendo.
That is not helpful in informing the rest of us about anything
other than that there are differences in opinion and perspective
in the community (I trust that doesn't surprise anyone).  I
recommend (in public because this context seems to require it)
that you go back to the person who made that comment, note the
contradiction, and ask for permission to bring the IESG (or
relevant ADs) into the conversation.  I hope we can look forward
to a report on your conclusions after the discussions that
should result.

> In my opinion such occurrences can cause confusion for the
> average participant as it is difficult to know whom to
> believe.  

But I think that leaves only two choices:

(1) Someone who receives apparently-contradictory advice draws
all parties involved into a conversation and tries to get the
issues straightened out and the confusion eliminated.  That is
particularly important because I've often found that some
apparent contradictions are merely people saying what is
ultimately the same thing from widely different perspectives and
in different terms.

(2) We establish a complete canon of procedural rules and
definitions, insist that anyone participating in the IETF
formally subscribe to it, and kick anyone who deviates off all
the mailing lists.

I can't begin to list the reasons why the second would be a bad
idea but, as long as we come from different backgrounds,
cultures, and perspectives on the IETF, differences such as the
one you describe are inevitable and the only important questions
are whether we can put the effort and good faith into sorting
them out (even if the result is in agreeing to disagree) or
whether we just complain.

> It can be even more difficult for people who reside
> in some parts of the world due to cultural differences.

Sure.  There is no question that we've got a lot of cultural
differences and resulting potential disconnects here, even among
"native" speakers of English and/or North American and Western
European residents.    We should be working on them and it is
good that attempts in that direction are moving forward.  But
there are some of those cultural issues here that are probably
not going to change and probably shouldn't, even if changes
would widen nominal participation.  As two examples among many,
those who are unwilling to speak up about their views are going
to be at a disadvantage, at least until we replace rough
consensus with secret ballots at every decision point.  Second,
if we could devise a vocabulary and interaction style that would
be politically correct in every culture of the world, it would
be a foreign language and culture to all, or almost all, of us
and, if only for that reason, might not contribute to
efficiency.  The same comment would apply to our adopting the
formalized language of international diplomacy as often used in
some other SDOs.

I do worry that industry consolidation and related factors are
resulting in an increasing number of WGs with active
participation only from people associated with a small number of
companies.  That not only looks bad but is a threat to making of
industry standards even when everyone involved is acting in good
faith.   But I don't know any fixes other that reversing those
industry trends or giving up.  The first doesn't seem to be
within our power and I assume there is consensus that the second
isn't desirable.

best,
   john



From nobody Wed Feb 26 06:24:15 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 4892E1A03AB for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 06:24:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.448
X-Spam-Level: 
X-Spam-Status: No, score=-7.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOHr2p36vCVa for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 06:24:06 -0800 (PST)
Received: from e34.co.us.ibm.com (e34.co.us.ibm.com [32.97.110.152]) by ietfa.amsl.com (Postfix) with ESMTP id 80D821A03BA for <ietf@ietf.org>; Wed, 26 Feb 2014 06:23:52 -0800 (PST)
Received: from /spool/local by e34.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>; Wed, 26 Feb 2014 07:13:45 -0700
Received: from d03dlp03.boulder.ibm.com (9.17.202.179) by e34.co.us.ibm.com (192.168.1.134) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Wed, 26 Feb 2014 07:13:42 -0700
Received: from b03cxnp08026.gho.boulder.ibm.com (b03cxnp08026.gho.boulder.ibm.com [9.17.130.18]) by d03dlp03.boulder.ibm.com (Postfix) with ESMTP id 8015719D8041 for <ietf@ietf.org>; Wed, 26 Feb 2014 07:13:37 -0700 (MST)
Received: from d03av06.boulder.ibm.com (d03av06.boulder.ibm.com [9.17.195.245]) by b03cxnp08026.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1QEDDCA5505290 for <ietf@ietf.org>; Wed, 26 Feb 2014 15:13:13 +0100
Received: from d03av06.boulder.ibm.com (loopback [127.0.0.1]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id s1QEH68c017993 for <ietf@ietf.org>; Wed, 26 Feb 2014 07:17:06 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-65-220-130.mts.ibm.com [9.65.220.130]) by d03av06.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id s1QEH4GC017893 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Feb 2014 07:17:05 -0700
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s1QEDaB1028746; Wed, 26 Feb 2014 09:13:36 -0500
Date: Wed, 26 Feb 2014 09:13:36 -0500
Message-ID: <m34n3m0xnz.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: Knowledge and suggestions (was: Re: Ad hominems)
In-Reply-To: <F07E5EA375E40279ACE7646E@JcK-HP8200.jck.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com> <F07E5EA375E40279ACE7646E@JcK-HP8200.jck.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14022614-1542-0000-0000-000006A1F0CC
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VZf9EkNdB9WUfKoD9fBcWYzAiRY
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, 26 Feb 2014 14:24:10 -0000

> I think you are making assumptions in the paragraph above that
> are symptomatic of why you then perceive yourself as being
> mistreated.

Strong agreement.

> The key problem with your comment/suggestion, stripped of all of
> the (IMO) emotional and peripheral comments that followed
> (relevant or not), was that it made (or appeared to make) a
> blanket suggestion of a change for all WGs without nearly enough
> argument or explanation _within the proposal note_ to overcome
> the strong presumption that WGs differ sufficiently that no
> suggestion about agenda constraints is applicable to all of
> them.  I note that, while much of the community agrees in
> principle that extensive "presentations" in WG sessions are bad
> news, ideas to ban them have gotten no traction for much the
> same reason.

+1

And more to the point (and this is very important context), this same
suggestion has been made many times before, with exactly the same long
discussion and the same conclusion (i.e,. no consensus to do this,
with good arguments for why it's not a good policy). It's a simplistic
proposal that just doesn't make sense as a blanket policy.

> [2]  These kinds of topics in WG leadership and management are
> among those that are periodically discussed on the WG Chairs
> list and training sessions.  For reasons of efficiency and to
> avoid various sorts of disruption and attacks (neither of which
> is an entirely theoretical problem) that list and those sessions
> are limited to WG Chairs (and the IAB and IESG).
> time, I've advocated making the mailing list or its archives
> available on a read-only basis to the broader community and/or
> broadcasting the training sessions on an informational,
> listen-only, basis. 

wgchairs list archive is publically available.

http://www.ietf.org/mail-archive/web/wgchairs/current/maillist.html

Thomas


From nobody Wed Feb 26 06:39:46 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 3631E1A03AA for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 06:39:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aMBjJgcI36wP for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 06:39:37 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 4A40E1A0393 for <ietf@ietf.org>; Wed, 26 Feb 2014 06:39:36 -0800 (PST)
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 1WIfe1-0007FX-4T; Wed, 26 Feb 2014 14:39:34 +0000
Date: Wed, 26 Feb 2014 22:39:30 +0800
Message-ID: <m2ha7mj5ul.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Knowledge and suggestions (was: Re: Ad hominems)
In-Reply-To: <m34n3m0xnz.wl%narten@us.ibm.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com> <F07E5EA375E40279ACE7646E@JcK-HP8200.jck.com> <m34n3m0xnz.wl%narten@us.ibm.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/V-2gOZQO9QG_2HwNOgpsp52yYqY
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, 26 Feb 2014 14:39:40 -0000

> And more to the point (and this is very important context), this same
> suggestion has been made many times before, with exactly the same long
> discussion and the same conclusion (i.e,. no consensus to do this,
> with good arguments for why it's not a good policy). It's a simplistic

the reason the suggestion is repeated is that it tends to actually have
some effect for a while.  nothing is absolute, nothing is a cure, the
disease is in our minds.

randy


From nobody Wed Feb 26 06:53: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 2D6141A0410 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 06:53:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.147
X-Spam-Level: 
X-Spam-Status: No, score=-3.147 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Aez8cJ8zV5w5 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 06:53:02 -0800 (PST)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 3A2C71A0574 for <ietf@ietf.org>; Wed, 26 Feb 2014 06:52:51 -0800 (PST)
Received: from [198.252.137.115] (helo=JcK-HP8200.jck.com) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1WIfqr-000K5T-Ee; Wed, 26 Feb 2014 09:52:49 -0500
Date: Wed, 26 Feb 2014 09:52:27 -0500
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>
Subject: Re: Knowledge and suggestions (was: Re: Ad hominems)
Message-ID: <CEE09580DE0EC99E3FD45661@JcK-HP8200.jck.com>
In-Reply-To: <m34n3m0xnz.wl%narten@us.ibm.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com> <F07E5EA375E40279ACE7646E@JcK-HP8200.jck.com> <m34n3m0xnz.wl%narten@us.ibm.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
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QRa45LOKJ9JEfyZY-UgkKyQbHz4
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, 26 Feb 2014 14:53:05 -0000

--On Wednesday, February 26, 2014 09:13 -0500 Thomas Narten
<narten@us.ibm.com> wrote:

> I've advocated making the mailing list or its archives
>> available on a read-only basis to the broader community and/or
>> broadcasting the training sessions on an informational,
>> listen-only, basis. 
> 
> wgchairs list archive is publically available.
> 
> http://www.ietf.org/mail-archive/web/wgchairs/current/maillist
> .html

Sorry.  Hadn't noticed that change.  Should have checked before
assuming it had not been made.

best,
   john





From nobody Wed Feb 26 06:55:25 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 EFE1C1A0353 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 06:55:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ybpIskUa-JIk for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 06:55:21 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id F13851A041B for <ietf@ietf.org>; Wed, 26 Feb 2014 06:55:20 -0800 (PST)
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 1WIftD-0007HN-Ha; Wed, 26 Feb 2014 14:55:16 +0000
Date: Wed, 26 Feb 2014 22:55:14 +0800
Message-ID: <m2fvn5kjot.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John C Klensin <john-ietf@jck.com>
Subject: Re: A private club
In-Reply-To: <884F51283FE98A20FB8E7EC2@JcK-HP8200.jck.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <m2zjleji25.wl%randy@psg.com> <6.2.5.6.2.20140226043234.0d0a0f60@elandnews.com> <884F51283FE98A20FB8E7EC2@JcK-HP8200.jck.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/HIP7gvuvUYKT9J-dt9-5ETja23o
Cc: S Moonesamy <sm+ietf@elandsys.com>, 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, 26 Feb 2014 14:55:24 -0000

it was probably i being stupid and trying to tell SM that the wg chairs
determine consensus.  and when he is a wg chair, he can do so.

if it could be automated, we would not need humans.  but i am sure the
second guessing would not abate.

randy, who has way too much technical work and too many plane flights to
       be stupid and engage here


From nobody Wed Feb 26 07:18:08 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 8F3A01A0687 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 07:18:03 -0800 (PST)
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 4KvJLbgzaHGy for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 07:17:59 -0800 (PST)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com [IPv6:2a00:1450:4010:c04::233]) by ietfa.amsl.com (Postfix) with ESMTP id 5E09D1A066F for <ietf@ietf.org>; Wed, 26 Feb 2014 07:17:51 -0800 (PST)
Received: by mail-lb0-f179.google.com with SMTP id p9so466907lbv.24 for <ietf@ietf.org>; Wed, 26 Feb 2014 07:17:49 -0800 (PST)
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=GAKaUdzvXMYVdu6nFVE39NbmB6xawxp6QmacHd/uYsI=; b=ECIwKWLQBmuNYd48TaJe2VtiQMuW/sLYtKqgTcffWCFnkVivDEnz378RMKwZ+SMCOU /qUie6rfucxbipz1EyLbDWC8Y3HHSRk+G3c074bl4QPdu38HsAj4n5ukzpU21Ye2KduW BpYn+IOI0Q2VyhA+HogoWKZAJSe+Iptlli+KqG7QLmoStXrjULXyIUlTjHcR7ndgAxHe yB834N2FgU2uQGWQjZKcy3bEIQHRDAhzx4LSKR3BN3hLDXvC6LO/WgS2R+tgUB/PIrH4 GKA4CdqlVYMwrNb2JVHJQ21NUssqJhMVWXV/qoMe5DSdCHUxmftuUCByU0GpkkT4S+vk 922g==
MIME-Version: 1.0
X-Received: by 10.152.23.169 with SMTP id n9mr2087881laf.45.1393427869440; Wed, 26 Feb 2014 07:17:49 -0800 (PST)
Received: by 10.112.37.168 with HTTP; Wed, 26 Feb 2014 07:17:49 -0800 (PST)
Date: Wed, 26 Feb 2014 10:17:49 -0500
Message-ID: <CAMm+Lwg12DZfWNdmqaRo=ha3g+5bPaMRaXd1BwUXbdSmwf3-uw@mail.gmail.com>
Subject: Consequences of Snowdonia
From: Phillip Hallam-Baker <hallam@gmail.com>
To: IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=089e0160b99a2d9f6904f350b5e5
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/RPxKSEynyGbLMPGLaEiXMBiA8Rw
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 15:18:03 -0000

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

This is off topic but I know from sources that my posts here reach certain
targets.


Fact: The Russian Army is mobilizing on the borders of Ukraine

Fact: Cyber attack activities by Russian government sponsored and
unaffiliated supporters are going to ramp up as part of that effort.

Fact: The Internet security community can't trust the NSA to coordinate the
response because you betrayed us.

Fact: There is an acknowledged risk that cyber-attacks whether from
government sponsored organizations or independent groups could be the spark
that turns an international crisis into a war.


I don't think we need to debate the facts further. We are now in a very
bad, very dangerous situation and the fault for the loss of trust lies with
the US military.

This is not a problem caused by one incident or disclosure. The
cyber-attack doctrine itself is at fault. The industrialized world is the
worlds biggest glass house and we spend $55 billion a year inventing new
ways to throw stones.


If there is an invasion it is very likely that the Russians will attempt a
repeat of their tactic from the South Ossetia campaign and using BGP
rerouting and Web site hijacking to issue bogus instructions purporting to
be from the Ukraine government telling citizens, police etc. to make no
resistance.




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

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

<div dir=3D"ltr"><div>This is off topic but I know from sources that my pos=
ts here reach certain targets.</div><div><br></div><div><br></div><div>Fact=
: The Russian Army is mobilizing on the borders of Ukraine</div><div><br></=
div>
<div>Fact: Cyber attack activities by Russian government sponsored and unaf=
filiated supporters are going to ramp up as part of that effort.</div><div>=
<br></div><div>Fact: The Internet security community can&#39;t trust the NS=
A to coordinate the response because you betrayed us.</div>
<div><br></div><div>Fact: There is an acknowledged risk that cyber-attacks =
whether from government sponsored organizations or independent groups could=
 be the spark that turns an international crisis into a war.</div><div>
<br></div><div><br></div><div>I don&#39;t think we need to debate the facts=
 further. We are now in a very bad, very dangerous situation and the fault =
for the loss of trust lies with the US military.</div><div><br></div>This i=
s not a problem caused by one incident or disclosure. The cyber-attack doct=
rine itself is at fault. The industrialized world is the worlds biggest gla=
ss house and we spend $55 billion a year inventing new ways to throw stones=
.<div>
<br clear=3D"all"><div><br></div><div>If there is an invasion it is very li=
kely that the Russians will attempt a repeat of their tactic from the South=
 Ossetia campaign and using BGP rerouting and Web site hijacking to issue b=
ogus instructions purporting to be from the Ukraine government telling citi=
zens, police etc. to make no resistance.</div>
<div><br></div><div><br></div><div><br></div><div><br></div>-- <br>Website:=
 <a href=3D"http://hallambaker.com/">http://hallambaker.com/</a><br>
</div></div>

--089e0160b99a2d9f6904f350b5e5--


From nobody Wed Feb 26 08:10:23 2014
Return-Path: <benamar73@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 DE0791A0488; Tue, 25 Feb 2014 22:34:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level: 
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_20=-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, GB_I_INVITATION=-2, 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 Yz8pleyOv55M; Tue, 25 Feb 2014 22:34:30 -0800 (PST)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id E0C7A1A045A; Tue, 25 Feb 2014 22:34:29 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id i11so392155oag.37 for <multiple recipients>; Tue, 25 Feb 2014 22:34:28 -0800 (PST)
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=2ZTrxMEWip/aMGvVxIy7PLgriWUvK6N/hy7GrmRwl5s=; b=QxFYoSTulsC3zRSs3hq/5V8D5DOL4dTyAI2lhW8vxMUyJDmFUFVD7kdI8ykTnYbaBh t0hodqgzzT/hl1r9cdxrTOXhpYhGFpxcD2EKUjIgpJPbm7FSTwYER54G4XcRNNB5uEaN q2Zpwkp2m62CvYF1W3Ru8egq86UHYLiSIrqNYnGuPArtrpkWluTvKrdxJqlm9iOstijS CmZWI2oqWFW6TbmBBcWqqajkqnnnrIn/mVR8/BAsjnZAyXG0iE/ITkmc2iCTKOQg0abL 9pNVZeJaiF0Ikrz4TK0YbscA6atCx/V7cpKDOva0Ome5X2Eq3vFJFZBq+JTbWqTCL54c H6Xw==
MIME-Version: 1.0
X-Received: by 10.60.150.134 with SMTP id ui6mr85555oeb.62.1393396468691; Tue, 25 Feb 2014 22:34:28 -0800 (PST)
Received: by 10.76.153.68 with HTTP; Tue, 25 Feb 2014 22:34:28 -0800 (PST)
In-Reply-To: <8D875E83-F8EC-4D92-B6BB-C013128E6213@ietf.org>
References: <8D875E83-F8EC-4D92-B6BB-C013128E6213@ietf.org>
Date: Wed, 26 Feb 2014 06:34:28 +0000
Message-ID: <CAMugd_Vzf+W7b_OC1i0xEhxsoox57qvju_ReyMTv4vv=Hsm=Yg@mail.gmail.com>
Subject: Re: [89all] Welcome to IETF-89
From: Nabil Benamar <benamar73@gmail.com>
To: 89attendees@ietf.org
Content-Type: multipart/alternative; boundary=047d7b5d36028c373204f3496528
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/14O7H5qPQuAIeXf91mEy4hzWS7A
X-Mailman-Approved-At: Wed, 26 Feb 2014 08:10:13 -0800
Cc: "89all@ietf.org" <89all@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>, "ietf-announce@ietf.org" <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: Wed, 26 Feb 2014 06:34:32 -0000

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

Dear Jari,

Thank you for the nice words and invitation...I have particularly
appreciated this comment in your message:" ICANN is a consumer of the
technology that we produce at the IETF..." .Well said :)


*Best wishes*
*=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9=88*
*Nabil Benamar*
*Moulay Ismail University.*
*Meknes. Morocco*
*nabilbenamar.com <http://nabilbenamar.com>*


On Tue, Feb 25, 2014 at 11:32 AM, IETF Chair <chair@ietf.org> wrote:

> I would like to welcome you all to our meeting in London next week. Here
> are some thoughts for the week from my perspective:
>
> http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/
>
> Jari Arkko, IETF Chair
>
> _______________________________________________
> 89all mailing list
> 89all@ietf.org
> https://www.ietf.org/mailman/listinfo/89all
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif"><font size=3D"4" color=3D"#3d85c6">Dear Jari,</font></div><div =
class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"><font size=
=3D"4" color=3D"#3d85c6"><br>
</font></div><div class=3D"gmail_default" style=3D"font-family:verdana,sans=
-serif"><font size=3D"4" color=3D"#3d85c6">Thank you for the nice words and=
 invitation...I have particularly appreciated this comment in your message:=
&quot;=C2=A0<span style=3D"font-family:Verdana,Helvetica,Arial,sans-serif;l=
ine-height:24.126985549926758px">ICANN is a consumer of the technology that=
 we produce at the IETF...&quot;</span>=C2=A0.Well said :)</font></div>
<div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"><font=
 size=3D"4" color=3D"#3d85c6"><br></font></div><div class=3D"gmail_extra"><=
font size=3D"4" color=3D"#3d85c6"><br clear=3D"all"></font><div><div dir=3D=
"ltr"><div style=3D"text-align:left">
<font face=3D"sans-serif" size=3D"4" color=3D"#3d85c6"><b>Best wishes</b></=
font></div><div dir=3D"rtl" style=3D"text-align:left"><font face=3D"sans-se=
rif" size=3D"4" color=3D"#3d85c6"><b>=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=
=D8=B9=D9=85=D8=B1=D9=88</b></font></div><div style=3D"text-align:left">
<font face=3D"sans-serif" size=3D"4" color=3D"#3d85c6"><b>Nabil Benamar</b>=
</font></div><div style=3D"text-align:left"><font face=3D"sans-serif" size=
=3D"4" color=3D"#3d85c6"><b>Moulay Ismail University.</b></font></div><div =
style=3D"text-align:left">
<font face=3D"sans-serif" size=3D"4" color=3D"#3d85c6"><b>Meknes. Morocco</=
b></font></div><div style=3D"text-align:left"><font face=3D"sans-serif" siz=
e=3D"4" color=3D"#3d85c6"><b><a href=3D"http://nabilbenamar.com" target=3D"=
_blank">nabilbenamar.com</a></b></font></div>
</div></div>
<font size=3D"4" color=3D"#3d85c6"><br><br></font><div class=3D"gmail_quote=
"><font size=3D"4" color=3D"#3d85c6">On Tue, Feb 25, 2014 at 11:32 AM, IETF=
 Chair <span dir=3D"ltr">&lt;<a href=3D"mailto:chair@ietf.org" target=3D"_b=
lank">chair@ietf.org</a>&gt;</span> wrote:<br>
</font><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><font size=3D"4" color=3D"#3d85c6">I =
would like to welcome you all to our meeting in London next week. Here are =
some thoughts for the week from my perspective:<br>

<br>
<a href=3D"http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/" target=3D"=
_blank">http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/</a><br>
<br>
Jari Arkko, IETF Chair<br>
<br>
_______________________________________________<br>
89all mailing list<br>
<a href=3D"mailto:89all@ietf.org">89all@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/89all" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/89all</a><br>
</font></blockquote></div><br></div></div>

--047d7b5d36028c373204f3496528--


From nobody Wed Feb 26 08:10:27 2014
Return-Path: <benamar73@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 995641A0481; Tue, 25 Feb 2014 22:42:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.749
X-Spam-Level: 
X-Spam-Status: No, score=-3.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, GB_I_INVITATION=-2, 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 iopxX6zK35Er; Tue, 25 Feb 2014 22:42:05 -0800 (PST)
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 5B62C1A02D2; Tue, 25 Feb 2014 22:42:05 -0800 (PST)
Received: by mail-ob0-f172.google.com with SMTP id wm4so351597obc.3 for <multiple recipients>; Tue, 25 Feb 2014 22:42:04 -0800 (PST)
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=LQeEokqSAb4ppeH5GYaFtmp9faVm2+KL9pqUq3Wy150=; b=ywgWMQPSbfbZHHoFQcR2q3Pgl+FV6irJHNRUwEEYaY7lTFuncOs2W2l06sw5cGdsIm 6wokIiC8mxAXJK6yzYARirGzwdb08CYSbcZa5w2hRSX0m2VayWIEDsXvWJ82yovRhsfF 8OH+Tjz21U2sqt9BnCdJqE9iQXHo/Kw+376wY7uHbirsphXCEAhBYJU5B7LKG0pvaRMx CM0E9dVtssmRx4apVuPVKxzXrfoV+9juluiiGeB3pGIuzbXzHTSoqOLrK32hDCKsThxf RRUgg0YrtjB7LvfoGm5F+k5uTuBeR2sDNFMaoRPekXHaWFG8BsisfMVpnDJ9NnJqDnR+ Gh1Q==
MIME-Version: 1.0
X-Received: by 10.60.115.68 with SMTP id jm4mr5148327oeb.45.1393396923979; Tue, 25 Feb 2014 22:42:03 -0800 (PST)
Received: by 10.76.153.68 with HTTP; Tue, 25 Feb 2014 22:42:03 -0800 (PST)
In-Reply-To: <CAMugd_Vzf+W7b_OC1i0xEhxsoox57qvju_ReyMTv4vv=Hsm=Yg@mail.gmail.com>
References: <8D875E83-F8EC-4D92-B6BB-C013128E6213@ietf.org> <CAMugd_Vzf+W7b_OC1i0xEhxsoox57qvju_ReyMTv4vv=Hsm=Yg@mail.gmail.com>
Date: Wed, 26 Feb 2014 06:42:03 +0000
Message-ID: <CAMugd_UoVHOM5o-ht6ynOCOHrfHm3DtUk6fd-1DyYitRHYCRHw@mail.gmail.com>
Subject: Re: [89all] Welcome to IETF-89
From: Nabil Benamar <benamar73@gmail.com>
To: 89attendees@ietf.org
Content-Type: multipart/alternative; boundary=089e0115f368af5c7104f3498018
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/q6mc5S2npv-VKpwtiOe8VMdgl14
X-Mailman-Approved-At: Wed, 26 Feb 2014 08:10:13 -0800
Cc: "89all@ietf.org" <89all@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>, "ietf-announce@ietf.org" <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: Wed, 26 Feb 2014 06:42:08 -0000

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

So, lot of thanks to ICANN for hosting this meeting !

*Best wishes*
*=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9=88*
*Nabil Benamar*
*Moulay Ismail University.*
*Meknes. Morocco*
*nabilbenamar.com <http://nabilbenamar.com>*


On Wed, Feb 26, 2014 at 6:34 AM, Nabil Benamar <benamar73@gmail.com> wrote:

> Dear Jari,
>
> Thank you for the nice words and invitation...I have particularly
> appreciated this comment in your message:" ICANN is a consumer of the
> technology that we produce at the IETF..." .Well said :)
>
>
> *Best wishes*
> *=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9=88*
> *Nabil Benamar*
> *Moulay Ismail University.*
> *Meknes. Morocco*
> *nabilbenamar.com <http://nabilbenamar.com>*
>
>
> On Tue, Feb 25, 2014 at 11:32 AM, IETF Chair <chair@ietf.org> wrote:
>
>> I would like to welcome you all to our meeting in London next week. Here
>> are some thoughts for the week from my perspective:
>>
>> http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/
>>
>> Jari Arkko, IETF Chair
>>
>> _______________________________________________
>> 89all mailing list
>> 89all@ietf.org
>> https://www.ietf.org/mailman/listinfo/89all
>>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif;font-size:large;color:#3d85c6">So, lot of thanks to ICANN for ho=
sting this meeting !=C2=A0</div></div><div class=3D"gmail_extra"><br clear=
=3D"all"><div>
<div dir=3D"ltr"><div style=3D"text-align:left"><font color=3D"#1f497d" fac=
e=3D"sans-serif"><span style=3D"font-size:15px"><b>Best wishes</b></span></=
font></div><div dir=3D"rtl" style=3D"text-align:left"><font color=3D"#1f497=
d" face=3D"sans-serif"><span style=3D"font-size:15px"><b>=D9=86=D8=A8=D9=8A=
=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9=88</b></span></font></div>
<div style=3D"text-align:left"><font color=3D"#1f497d" face=3D"sans-serif">=
<span style=3D"font-size:15px"><b>Nabil Benamar</b></span></font></div><div=
 style=3D"text-align:left"><font color=3D"#1f497d" face=3D"sans-serif"><b>M=
oulay Ismail University.</b></font></div>
<div style=3D"text-align:left"><font color=3D"#1f497d" face=3D"sans-serif">=
<b>Meknes. Morocco</b></font></div><div style=3D"text-align:left"><font col=
or=3D"#1f497d" face=3D"sans-serif"><b><a href=3D"http://nabilbenamar.com" t=
arget=3D"_blank">nabilbenamar.com</a></b></font></div>
</div></div>
<br><br><div class=3D"gmail_quote">On Wed, Feb 26, 2014 at 6:34 AM, Nabil B=
enamar <span dir=3D"ltr">&lt;<a href=3D"mailto:benamar73@gmail.com" target=
=3D"_blank">benamar73@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 .8ex;border-left:1px #ccc solid;border-r=
ight:1px #ccc solid;padding-left:1ex;padding-right:1ex">
<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif"><font size=3D"4" color=3D"#3d85c6">Dear Jari,</font></div><div =
class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"><font size=
=3D"4" color=3D"#3d85c6"><br>

</font></div><div class=3D"gmail_default" style=3D"font-family:verdana,sans=
-serif"><font size=3D"4" color=3D"#3d85c6">Thank you for the nice words and=
 invitation...I have particularly appreciated this comment in your message:=
&quot;=C2=A0<span style=3D"font-family:Verdana,Helvetica,Arial,sans-serif;l=
ine-height:24.126985549926758px">ICANN is a consumer of the technology that=
 we produce at the IETF...&quot;</span>=C2=A0.Well said :)</font></div>

<div class=3D"gmail_default" style=3D"font-family:verdana,sans-serif"><font=
 size=3D"4" color=3D"#3d85c6"><br></font></div><div class=3D"gmail_extra"><=
font size=3D"4" color=3D"#3d85c6"><br clear=3D"all"></font><div><div dir=3D=
"ltr"><div style=3D"text-align:left">

<font face=3D"sans-serif" size=3D"4" color=3D"#3d85c6"><b>Best wishes</b></=
font></div><div dir=3D"rtl" style=3D"text-align:left"><font face=3D"sans-se=
rif" size=3D"4" color=3D"#3d85c6"><b>=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=
=D8=B9=D9=85=D8=B1=D9=88</b></font></div><span class=3D"HOEnZb"><font color=
=3D"#888888"><div style=3D"text-align:left">

<font face=3D"sans-serif" size=3D"4" color=3D"#3d85c6"><b>Nabil Benamar</b>=
</font></div><div style=3D"text-align:left"><font face=3D"sans-serif" size=
=3D"4" color=3D"#3d85c6"><b>Moulay Ismail University.</b></font></div><div =
style=3D"text-align:left">

<font face=3D"sans-serif" size=3D"4" color=3D"#3d85c6"><b>Meknes. Morocco</=
b></font></div><div style=3D"text-align:left"><font face=3D"sans-serif" siz=
e=3D"4" color=3D"#3d85c6"><b><a href=3D"http://nabilbenamar.com" target=3D"=
_blank">nabilbenamar.com</a></b></font></div>

</font></span></div></div><div><div class=3D"h5">
<font size=3D"4" color=3D"#3d85c6"><br><br></font><div class=3D"gmail_quote=
"><font size=3D"4" color=3D"#3d85c6">On Tue, Feb 25, 2014 at 11:32 AM, IETF=
 Chair <span dir=3D"ltr">&lt;<a href=3D"mailto:chair@ietf.org" target=3D"_b=
lank">chair@ietf.org</a>&gt;</span> wrote:<br>

</font><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><font size=3D"4" color=3D"#3d85c6">I =
would like to welcome you all to our meeting in London next week. Here are =
some thoughts for the week from my perspective:<br>


<br>
<a href=3D"http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/" target=3D"=
_blank">http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/</a><br>
<br>
Jari Arkko, IETF Chair<br>
<br>
_______________________________________________<br>
89all mailing list<br>
<a href=3D"mailto:89all@ietf.org" target=3D"_blank">89all@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/89all" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/89all</a><br>
</font></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>

--089e0115f368af5c7104f3498018--


From nobody Wed Feb 26 08:10:31 2014
Return-Path: <abdelmoniem.rezk@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 443461A0190; Wed, 26 Feb 2014 01:28:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.898
X-Spam-Level: 
X-Spam-Status: No, score=-3.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, 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 vM-5N_tBwbWb; Wed, 26 Feb 2014 01:28:10 -0800 (PST)
Received: from relais-inet.francetelecom.com (relais-ias91.francetelecom.com [193.251.215.91]) by ietfa.amsl.com (Postfix) with ESMTP id F205F1A018D; Wed, 26 Feb 2014 01:28:09 -0800 (PST)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm13.si.francetelecom.fr (ESMTP service) with ESMTP id 4A03A32444E; Wed, 26 Feb 2014 10:28:08 +0100 (CET)
Received: from Exchangemail-eme1.itn.ftgroup (unknown [10.114.31.55]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 2467327C0B7; Wed, 26 Feb 2014 10:28:08 +0100 (CET)
Received: from OPEXCLILM23.corporate.adroot.infra.ftgroup ([169.254.2.154]) by OPEXCLILH03.corporate.adroot.infra.ftgroup ([10.114.31.55]) with mapi id 14.03.0174.001; Wed, 26 Feb 2014 10:28:07 +0100
From: <abdelmoniem.rezk@orange.com>
To: "89attendees@ietf.org" <89attendees@ietf.org>
Subject: RE: [89attendees] [89all] Welcome to IETF-89
Thread-Topic: [89attendees] [89all] Welcome to IETF-89
Thread-Index: AQHPMh1K0xp3nLY8s0uFLxXZIi9CyZrHBJoAgAACHoCAAD6xQA==
Date: Wed, 26 Feb 2014 09:28:07 +0000
Message-ID: <23035_1393406888_530DB3A8_23035_4284_1_E7E18C472D67E84580701DBFDED9240F4F74B287@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <8D875E83-F8EC-4D92-B6BB-C013128E6213@ietf.org> <CAMugd_Vzf+W7b_OC1i0xEhxsoox57qvju_ReyMTv4vv=Hsm=Yg@mail.gmail.com> <CAMugd_UoVHOM5o-ht6ynOCOHrfHm3DtUk6fd-1DyYitRHYCRHw@mail.gmail.com>
In-Reply-To: <CAMugd_UoVHOM5o-ht6ynOCOHrfHm3DtUk6fd-1DyYitRHYCRHw@mail.gmail.com>
Accept-Language: en-US, fr-FR
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.3]
Content-Type: multipart/related; boundary="_004_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_"; type="multipart/alternative"
MIME-Version: 1.0
X-PMX-Version: 6.0.3.2322014, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.2.25.93015
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/sfS2Wy__g6AqdyYlQC3ZUelrdvo
X-Mailman-Approved-At: Wed, 26 Feb 2014 08:10:12 -0800
Cc: "89all@ietf.org" <89all@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>, "ietf-announce@ietf.org" <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: Wed, 26 Feb 2014 09:28:15 -0000

--_004_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_
Content-Type: multipart/alternative;
	boundary="_000_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_"


--_000_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgR3V5cw0KSSBhbSByZWdpc3RlcmVkIHRvIGF0dGVuZCB0aGUgZXZlbnQgcmVtb3RlbHkgLCBJ
IHdvbmRlciBob3cgdGhpcyBpcyBjb29yZGluYXRlZCBhbmQgaXMgdGhlcmUgYW55IGxpdmUgc2Vz
c2lvbnMgdGhyb3VnaCB3ZWIgY29sbGFib3JhdGlvbnMgb3IgY29uZmVyZW5jaW5nID8NCg0KVGhh
bmtzIGFuZCBCZXN0IFJlZ2FyZHMNCg0KW2h0dHA6Ly93d3cub3JhbmdlLmNvbS9zaXJpdXMvbG9n
b3NfbWFpbC9vcmFuZ2VfbG9nby5naWZdDQpBYmRlbG1vbmllbSBSZXprICxNLlNjLixNSUVULE1J
RUVFDQoNCkZyb206IDg5YXR0ZW5kZWVzIFttYWlsdG86ODlhdHRlbmRlZXMtYm91bmNlc0BpZXRm
Lm9yZ10gT24gQmVoYWxmIE9mIE5hYmlsIEJlbmFtYXINClNlbnQ6IDI2IEZlYnJ1YXJ5IDIwMTQg
MDY6NDINClRvOiA4OWF0dGVuZGVlc0BpZXRmLm9yZw0KQ2M6IDg5YWxsQGlldGYub3JnOyBpZXRm
QGlldGYub3JnIERpc2N1c3Npb247IGlldGYtYW5ub3VuY2VAaWV0Zi5vcmcNClN1YmplY3Q6IFJl
OiBbODlhdHRlbmRlZXNdIFs4OWFsbF0gV2VsY29tZSB0byBJRVRGLTg5DQoNClNvLCBsb3Qgb2Yg
dGhhbmtzIHRvIElDQU5OIGZvciBob3N0aW5nIHRoaXMgbWVldGluZyAhDQoNCkJlc3Qgd2lzaGVz
DQrZhtio2YrZhCDYqNmG2LnZhdix2YgNCk5hYmlsIEJlbmFtYXINCk1vdWxheSBJc21haWwgVW5p
dmVyc2l0eS4NCk1la25lcy4gTW9yb2Njbw0KbmFiaWxiZW5hbWFyLmNvbTxodHRwOi8vbmFiaWxi
ZW5hbWFyLmNvbT4NCg0KT24gV2VkLCBGZWIgMjYsIDIwMTQgYXQgNjozNCBBTSwgTmFiaWwgQmVu
YW1hciA8YmVuYW1hcjczQGdtYWlsLmNvbTxtYWlsdG86YmVuYW1hcjczQGdtYWlsLmNvbT4+IHdy
b3RlOg0KRGVhciBKYXJpLA0KDQpUaGFuayB5b3UgZm9yIHRoZSBuaWNlIHdvcmRzIGFuZCBpbnZp
dGF0aW9uLi4uSSBoYXZlIHBhcnRpY3VsYXJseSBhcHByZWNpYXRlZCB0aGlzIGNvbW1lbnQgaW4g
eW91ciBtZXNzYWdlOiIgSUNBTk4gaXMgYSBjb25zdW1lciBvZiB0aGUgdGVjaG5vbG9neSB0aGF0
IHdlIHByb2R1Y2UgYXQgdGhlIElFVEYuLi4iIC5XZWxsIHNhaWQgOikNCg0KDQpCZXN0IHdpc2hl
cw0K2YbYqNmK2YQg2KjZhti52YXYsdmIDQpOYWJpbCBCZW5hbWFyDQpNb3VsYXkgSXNtYWlsIFVu
aXZlcnNpdHkuDQpNZWtuZXMuIE1vcm9jY28NCm5hYmlsYmVuYW1hci5jb208aHR0cDovL25hYmls
YmVuYW1hci5jb20+DQoNCk9uIFR1ZSwgRmViIDI1LCAyMDE0IGF0IDExOjMyIEFNLCBJRVRGIENo
YWlyIDxjaGFpckBpZXRmLm9yZzxtYWlsdG86Y2hhaXJAaWV0Zi5vcmc+PiB3cm90ZToNCkkgd291
bGQgbGlrZSB0byB3ZWxjb21lIHlvdSBhbGwgdG8gb3VyIG1lZXRpbmcgaW4gTG9uZG9uIG5leHQg
d2Vlay4gSGVyZSBhcmUgc29tZSB0aG91Z2h0cyBmb3IgdGhlIHdlZWsgZnJvbSBteSBwZXJzcGVj
dGl2ZToNCg0KaHR0cDovL3d3dy5pZXRmLm9yZy9ibG9nLzIwMTQvMDIvd2VsY29tZS10by1pZXRm
LTg5Lw0KDQpKYXJpIEFya2tvLCBJRVRGIENoYWlyDQoNCl9fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fDQo4OWFsbCBtYWlsaW5nIGxpc3QNCjg5YWxsQGlldGYu
b3JnPG1haWx0bzo4OWFsbEBpZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vODlhbGwNCg0KDQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpv
aW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBv
dSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRpZmZ1c2VzLCBleHBs
b2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBt
ZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVyIGV0
IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBl
bGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBkZWNs
aW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZv
cm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRz
IG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQg
bWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwg
dXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNlaXZl
ZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0
ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxzIG1heSBiZSBhbHRl
cmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9k
aWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=

--_000_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7
fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpUYWhvbWE7DQoJcGFub3NlLTE6MiAxMSA2IDQg
MyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpWZXJkYW5hOw0KCXBhbm9z
ZS0xOjIgMTEgNiA0IDMgNSA0IDQgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1z
b05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowY207DQoJbWFy
Z2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRp
bWVzIE5ldyBSb21hbiIsInNlcmlmIjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRl
cmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQpwLk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29BY2V0YXRlDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IENoYXIiOw0K
CW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZTo4LjBwdDsN
Cglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5ob2VuemINCgl7bXNv
LXN0eWxlLW5hbWU6aG9lbnpiO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBl
OnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJWZXJkYW5hIiwic2Fucy1zZXJpZiI7DQoJ
Y29sb3I6IzFGNDk3RDt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0KCXttc28tc3R5bGUtbmFtZToi
QmFsbG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUt
bGluazoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7
DQoJbXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tR0I7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlm
IjsNCgltc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUzt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7
c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBw
dDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBz
cGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4
bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIg
ZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4N
Cjxib2R5IGxhbmc9IkVOLUdCIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xh
c3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+SGkgR3V5czxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjoj
MUY0OTdEIj5JIGFtIHJlZ2lzdGVyZWQgdG8gYXR0ZW5kIHRoZSBldmVudCByZW1vdGVseSAsIEkg
d29uZGVyIGhvdyB0aGlzIGlzIGNvb3JkaW5hdGVkIGFuZCBpcyB0aGVyZSBhbnkgbGl2ZSBzZXNz
aW9ucyB0aHJvdWdoIHdlYiBjb2xsYWJvcmF0aW9ucyBvciBjb25mZXJlbmNpbmcgPzxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3
RCI+VGhhbmtzIGFuZCBCZXN0IFJlZ2FyZHM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZxdW90Oywm
cXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOmJsYWNrIj48aW1nIHdpZHRoPSI0MCIgaGVpZ2h0
PSI0MCIgaWQ9IlBpY3R1cmVfeDAwMjBfMSIgc3JjPSJjaWQ6aW1hZ2UwMDEuZ2lmQDAxQ0YzMkQ1
LjBENjk5NUMwIiBhbHQ9Imh0dHA6Ly93d3cub3JhbmdlLmNvbS9zaXJpdXMvbG9nb3NfbWFpbC9v
cmFuZ2VfbG9nby5naWYiPjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250
LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6
IzFGNDk3RCI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VmVyZGFuYSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkFiZGVsbW9uaWVtIFJl
emsgLE0uU2MuLE1JRVQsTUlFRUU8bzpwPjwvbzpwPjwvc3Bhbj48L2I+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7VmVyZGFuYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+RnJvbTo8L3NwYW4+PC9iPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtU
YWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+IDg5YXR0ZW5kZWVzIFttYWlsdG86
ODlhdHRlbmRlZXMtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+TmFiaWwg
QmVuYW1hcjxicj4NCjxiPlNlbnQ6PC9iPiAyNiBGZWJydWFyeSAyMDE0IDA2OjQyPGJyPg0KPGI+
VG86PC9iPiA4OWF0dGVuZGVlc0BpZXRmLm9yZzxicj4NCjxiPkNjOjwvYj4gODlhbGxAaWV0Zi5v
cmc7IGlldGZAaWV0Zi5vcmcgRGlzY3Vzc2lvbjsgaWV0Zi1hbm5vdW5jZUBpZXRmLm9yZzxicj4N
CjxiPlN1YmplY3Q6PC9iPiBSZTogWzg5YXR0ZW5kZWVzXSBbODlhbGxdIFdlbGNvbWUgdG8gSUVU
Ri04OTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjE4LjBwdDtmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZx
dW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzNEODVDNiI+U28sIGxvdCBvZiB0aGFua3MgdG8g
SUNBTk4gZm9yIGhvc3RpbmcgdGhpcyBtZWV0aW5nICEmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiciBjbGVh
cj0iYWxsIj4NCjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjVwdDtmb250LWZhbWlseTomcXVvdDtB
cmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkJlc3Qgd2lz
aGVzPC9zcGFuPjwvYj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIGFsaWdu
PSJyaWdodCIgZGlyPSJSVEwiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQ7ZGlyZWN0aW9uOnJ0bDt1
bmljb2RlLWJpZGk6ZW1iZWQiPg0KPGI+PHNwYW4gbGFuZz0iQVItU0EiIHN0eWxlPSJmb250LXNp
emU6MTEuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYm
cXVvdDs7Y29sb3I6IzFGNDk3RCI+2YbYqNmK2YQg2KjZhti52YXYsdmIPC9zcGFuPjwvYj48c3Bh
biBkaXI9IkxUUiI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj5OYWJpbCBCZW5hbWFy
PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJBUi1TQSIgZGlyPSJSVEwiPjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPk1v
dWxheSBJc21haWwgVW5pdmVyc2l0eS48L3NwYW4+PC9iPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+TWVrbmVzLiBNb3JvY2Nv
PC9zcGFuPjwvYj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFu
IHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPjxhIGhyZWY9Imh0dHA6Ly9uYWJpbGJlbmFtYXIuY29tIiB0YXJn
ZXQ9Il9ibGFuayI+bmFiaWxiZW5hbWFyLmNvbTwvYT48L3NwYW4+PC9iPjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90
dG9tOjEyLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+T24gV2VkLCBGZWIgMjYsIDIwMTQgYXQgNjozNCBBTSwgTmFiaWwgQmVuYW1hciAmbHQ7
PGEgaHJlZj0ibWFpbHRvOmJlbmFtYXI3M0BnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5iZW5h
bWFyNzNAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2Zv
bnQtZmFtaWx5OiZxdW90O1ZlcmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xv
cjojM0Q4NUM2Ij5EZWFyIEphcmksPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O1Zl
cmRhbmEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojM0Q4NUM2Ij5UaGFuayB5
b3UgZm9yIHRoZSBuaWNlIHdvcmRzIGFuZCBpbnZpdGF0aW9uLi4uSSBoYXZlIHBhcnRpY3VsYXJs
eSBhcHByZWNpYXRlZCB0aGlzIGNvbW1lbnQgaW4geW91ciBtZXNzYWdlOiZxdW90OyZuYnNwO0lD
QU5OIGlzIGEgY29uc3VtZXIgb2YgdGhlIHRlY2hub2xvZ3kgdGhhdCB3ZSBwcm9kdWNlDQogYXQg
dGhlIElFVEYuLi4mcXVvdDsmbmJzcDsuV2VsbCBzYWlkIDopPC9zcGFuPjxzcGFuIHN0eWxlPSJm
b250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtWZXJkYW5hJnF1b3Q7LCZxdW90O3NhbnMt
c2VyaWYmcXVvdDsiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2NvbG9y
OiMzRDg1QzYiPjxiciBjbGVhcj0iYWxsIj4NCjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
My41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90
Oztjb2xvcjojM0Q4NUM2Ij5CZXN0IHdpc2hlczwvc3Bhbj48L2I+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0icmlnaHQiIGRpcj0iUlRMIiBzdHlsZT0idGV4dC1h
bGlnbjpsZWZ0O2RpcmVjdGlvbjpydGw7dW5pY29kZS1iaWRpOmVtYmVkIj4NCjxiPjxzcGFuIGxh
bmc9IkFSLVNBIiBzdHlsZT0iZm9udC1zaXplOjEzLjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlh
bCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMzRDg1QzYiPtmG2KjZitmEINio
2YbYudmF2LHZiDwvc3Bhbj48L2I+PHNwYW4gZGlyPSJMVFIiPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTMuNXB0
O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzNEODVDNiI+TmFiaWwgQmVuYW1hcjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iQVItU0EiIGRp
cj0iUlRMIiBzdHlsZT0iY29sb3I6Izg4ODg4OCI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1m
YW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojM0Q4
NUM2Ij5Nb3VsYXkgSXNtYWlsIFVuaXZlcnNpdHkuPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iY29s
b3I6Izg4ODg4OCI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMy41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojM0Q4NUM2Ij5NZWtuZXMuIE1vcm9j
Y288L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJjb2xvcjojODg4ODg4Ij48bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEz
LjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMzRDg1QzYiPjxhIGhyZWY9Imh0dHA6Ly9uYWJpbGJlbmFtYXIuY29tIiB0YXJnZXQ9
Il9ibGFuayI+bmFiaWxiZW5hbWFyLmNvbTwvYT48L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJjb2xv
cjojODg4ODg4Ij48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTMuNXB0O2NvbG9yOiMzRDg1QzYiPk9uIFR1ZSwgRmViIDI1LCAy
MDE0IGF0IDExOjMyIEFNLCBJRVRGIENoYWlyICZsdDs8YSBocmVmPSJtYWlsdG86Y2hhaXJAaWV0
Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5jaGFpckBpZXRmLm9yZzwvYT4mZ3Q7IHdyb3RlOjwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTMuNXB0O2NvbG9yOiMzRDg1QzYiPkkgd291bGQgbGlrZSB0byB3ZWxjb21lIHlvdSBh
bGwgdG8gb3VyIG1lZXRpbmcgaW4gTG9uZG9uIG5leHQgd2Vlay4gSGVyZSBhcmUgc29tZSB0aG91
Z2h0cyBmb3IgdGhlIHdlZWsgZnJvbSBteSBwZXJzcGVjdGl2ZTo8YnI+DQo8YnI+DQo8YSBocmVm
PSJodHRwOi8vd3d3LmlldGYub3JnL2Jsb2cvMjAxNC8wMi93ZWxjb21lLXRvLWlldGYtODkvIiB0
YXJnZXQ9Il9ibGFuayI+aHR0cDovL3d3dy5pZXRmLm9yZy9ibG9nLzIwMTQvMDIvd2VsY29tZS10
by1pZXRmLTg5LzwvYT48YnI+DQo8YnI+DQpKYXJpIEFya2tvLCBJRVRGIENoYWlyPGJyPg0KPGJy
Pg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQo4
OWFsbCBtYWlsaW5nIGxpc3Q8YnI+DQo8YSBocmVmPSJtYWlsdG86ODlhbGxAaWV0Zi5vcmciIHRh
cmdldD0iX2JsYW5rIj44OWFsbEBpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvLzg5YWxsIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby84OWFsbDwvYT48L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxQUkU+X19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
XwoKQ2UgbWVzc2FnZSBldCBzZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMg
aW5mb3JtYXRpb25zIGNvbmZpZGVudGllbGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVu
dCBkb25jCnBhcyBldHJlIGRpZmZ1c2VzLCBleHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jp
c2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVjdSBjZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6
IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0ZXVyIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMg
cGllY2VzIGpvaW50ZXMuIExlcyBtZXNzYWdlcyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRp
YmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5nZSBkZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNp
IGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJlLCBkZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRo
aXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBv
ciBwcml2aWxlZ2VkIGluZm9ybWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRo
ZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRo
b3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVh
c2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRh
Y2htZW50cy4KQXMgZW1haWxzIG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBm
b3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVk
LgpUaGFuayB5b3UuCjwvUFJFPjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_--

--_004_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_
Content-Type: image/gif; name="image001.gif"
Content-Description: image001.gif
Content-Disposition: inline; filename="image001.gif"; size=1264;
	creation-date="Wed, 26 Feb 2014 09:28:06 GMT";
	modification-date="Wed, 26 Feb 2014 09:28:06 GMT"
Content-ID: <image001.gif@01CF32D5.0D6995C0>
Content-Transfer-Encoding: base64

R0lGODlhKAAoAPcAAP9mAP9lAP////9jAP9kAP9gAP9eAP9dAP9iAP9fAP/x5/9cAP9YAP9ZAP/6
9v+3i/9yGf9lBP+ygv/n1/+IQf/Xvf/fyf+kbP+3if/LrP9jAv9oBv+7kP9oCP91Hf/UuP9xF/+/
lv/awP9mB/+JPf+XV/+EPP+KPf/y6f+HQf+HQv9pC/+PRf/s4f/59f9/Mv9kAv9lAv+cXf/IpP/8
+v/8+P+4jf/Stf9VAP/Ttv/Bmf/Lq/9sDv9vEP9sC/+JPv+2hv9xFv+VUP+ALf9zGv+1h//w5v/u
4v9kBf/JqP/Vuv+3h/+KQv+IQv+2h/9kC/+9k//t4v92G//dyf9bAP9vEv+zhf9aAP91JP/07P/D
nf/awf+UT/9pCP/dxv/Nrv+pc//p2v9hAP+GPf9pBv+GP/9iA/9iCv+ocv+QSv/Zwv/AmP+8j/+d
Xv/Mqv+lbf/Psf+IOv/7+P/Orv9nCP+SU/96Lv96J//j0f9nA/9eBP/bw//aw//k1P+STf/r3f/n
1v/Ipf+6jf+gZ/+eYv/Lqv/Mrf/gzP9zG/+xgP+ygf/XvP/gzf+JQf/Cm/+VVf+FOP/fzP+QTP/h
zv/Xvv+LRv/Gn//s3/+4iv9kAf9rFP+tdv9rCP9lAf9yFv+pcf94KP+xe//Yv/94If9pCv+COf+Z
Vf+ue/+7kf9XAP9nCv/q3f9iAf+9lP9uEf9oA//l1P+FN////f+ncv+OR//v5f/y5/+aX/+hY/9+
K/9hAf/59P+hZ/+IPv+fYv90Gv/Qs/+XVf9wE/+VVP9+Lf+YWP/eyf+mbv9+Mf96Jv91HP/HpP+8
kQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAAAAAALAAAAAAoACgA
AAj/AAEIHEiwoMGDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuQ
AQYQCEBAZABOUnqM8FEQwQCBNGkKHPATQICjMoEimBlgaIFfYNAk2lTAKREIBQa86sKqigZdiEAU
INBpABIPqmSaUbYiAhkCCUBAeNKIVihTPwnwWFZDjpYBvQBROvSigi0FIRBgEKXExR5XGgI5sIBn
yQIMClA4ikAgUwyBB04JuDBLwJsxAiK1IWbFjgQBpZLIenRLQJphAiT5EsDGj4A6JhzIOECwwBY+
DK5MmtNEgAkcHS4AYyQgRYYJDbAIEBKiz4IztaA4zRFwA44DZsQHJqgwpQEVWG4oCIjDYE0WUCUE
lMkQpkAyAVxwEIUemuzCARA0QDJKLp40NdABxwjwACoCECLfCal80UIlHwiggiF/FHCHAMEwIcAO
OQggCAkSlmABCVUNFAAdRaCggAQFxCLCEAv8YIwXrSyCjCIzIOCBCCw0gIsaNhhhCQO8THCJDsIU
NRABBmywgQFINSWGTAYMQNNPMSVwwgfFDCLAJwcYAEMeBtR00EwyytjUnQ7GFEQhR6yCSQc1HeUR
XKSMEKdCAQEAOw==

--_004_E7E18C472D67E84580701DBFDED9240F4F74B287OPEXCLILM23corp_--


From nobody Wed Feb 26 08:10:34 2014
Return-Path: <benamar73@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 A18F21A012B; Wed, 26 Feb 2014 01:35:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.749
X-Spam-Level: 
X-Spam-Status: No, score=-3.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, GB_I_INVITATION=-2, 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 o3QYPMcKjYvz; Wed, 26 Feb 2014 01:35:16 -0800 (PST)
Received: from mail-ob0-x234.google.com (mail-ob0-x234.google.com [IPv6:2607:f8b0:4003:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id 78B6F1A0152; Wed, 26 Feb 2014 01:35:16 -0800 (PST)
Received: by mail-ob0-f180.google.com with SMTP id vb8so512376obc.11 for <multiple recipients>; Wed, 26 Feb 2014 01:35:15 -0800 (PST)
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=GH9fKsC51+aDdYZ78sL+TyuYoJO6lf9OxwkrUuxvwdY=; b=ej1tFLzQasYuA92nFwKT5vXHCa7UtLlSu/ni1y8LUKxUqgHe+bG0itF4ihGQykEMeD 3PbwlmzQ8Lvsq1E05jOptmBrNG+EY4atxPnh4aRVSdjA7avfy+IJsYXRJdZF7M+bOebt RI9HjXJg7+psPtZE/9pmOOuPwhmfwZsBncNKc/2VNjb/MQPhT1muHFVRF6X9jwupZBkr Rni0f+m90Gzn6GyKDxBBnLCCpbrdeMxnusauVf/dPkJQ/SJ+4PW8zNUeK3fEFDHKYN0D Y1Qih5dzHdqA/0jxGsAIApWuKm/gf02usLgmJgaOBryKh59Hd11dC0bC/FaHDBPbVER2 ymbg==
MIME-Version: 1.0
X-Received: by 10.182.19.164 with SMTP id g4mr745637obe.58.1393407315086; Wed, 26 Feb 2014 01:35:15 -0800 (PST)
Received: by 10.76.153.68 with HTTP; Wed, 26 Feb 2014 01:35:14 -0800 (PST)
In-Reply-To: <23035_1393406888_530DB3A8_23035_4284_1_E7E18C472D67E84580701DBFDED9240F4F74B287@OPEXCLILM23.corporate.adroot.infra.ftgroup>
References: <8D875E83-F8EC-4D92-B6BB-C013128E6213@ietf.org> <CAMugd_Vzf+W7b_OC1i0xEhxsoox57qvju_ReyMTv4vv=Hsm=Yg@mail.gmail.com> <CAMugd_UoVHOM5o-ht6ynOCOHrfHm3DtUk6fd-1DyYitRHYCRHw@mail.gmail.com> <23035_1393406888_530DB3A8_23035_4284_1_E7E18C472D67E84580701DBFDED9240F4F74B287@OPEXCLILM23.corporate.adroot.infra.ftgroup>
Date: Wed, 26 Feb 2014 09:35:14 +0000
Message-ID: <CAMugd_Ut2+ZYBcgP0X=nDaoUTBtmW31AZikKYP4oUR8BUS-wXQ@mail.gmail.com>
Subject: Re: [89attendees] [89all] Welcome to IETF-89
From: Nabil Benamar <benamar73@gmail.com>
To: abdelmoniem.rezk@orange.com
Content-Type: multipart/related; boundary=001a11c2a5f60b42c904f34bec39
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/uCmZDNnW0ybiHhLAIyu5-4OPLXU
X-Mailman-Approved-At: Wed, 26 Feb 2014 08:10:13 -0800
Cc: "89all@ietf.org" <89all@ietf.org>, "ietf-announce@ietf.org" <ietf-announce@ietf.org>, "ietf@ietf.org Discussion" <ietf@ietf.org>, "89attendees@ietf.org" <89attendees@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 09:35:21 -0000

--001a11c2a5f60b42c904f34bec39
Content-Type: multipart/alternative; boundary=001a11c2a5f60b42c704f34bec38

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

Hi Abdelmoniem,

here is the link for the remote participation:
http://www.ietf.org/meeting/89/remote-participation.html

All the best

*Best wishes*
*=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9=88*
*Nabil Benamar*
*Moulay Ismail University.*
*Meknes. Morocco*
*nabilbenamar.com <http://nabilbenamar.com>*


On Wed, Feb 26, 2014 at 9:28 AM, <abdelmoniem.rezk@orange.com> wrote:

>  Hi Guys
>
> I am registered to attend the event remotely , I wonder how this is
> coordinated and is there any live sessions through web collaborations or
> conferencing ?
>
>
>
> Thanks and Best Regards
>
>
>
> [image: http://www.orange.com/sirius/logos_mail/orange_logo.gif]
>
> *Abdelmoniem Rezk ,M.Sc.,MIET,MIEEE*
>
>
>
> *From:* 89attendees [mailto:89attendees-bounces@ietf.org] *On Behalf Of *=
Nabil
> Benamar
> *Sent:* 26 February 2014 06:42
> *To:* 89attendees@ietf.org
> *Cc:* 89all@ietf.org; ietf@ietf.org Discussion; ietf-announce@ietf.org
> *Subject:* Re: [89attendees] [89all] Welcome to IETF-89
>
>
>
> So, lot of thanks to ICANN for hosting this meeting !
>
>
>   *Best wishes*
>
> *=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9=88*
>
> *Nabil Benamar*
>
> *Moulay Ismail University.*
>
> *Meknes. Morocco*
>
> *nabilbenamar.com <http://nabilbenamar.com>*
>
>
>
> On Wed, Feb 26, 2014 at 6:34 AM, Nabil Benamar <benamar73@gmail.com>
> wrote:
>
> Dear Jari,
>
>
>
> Thank you for the nice words and invitation...I have particularly
> appreciated this comment in your message:" ICANN is a consumer of the
> technology that we produce at the IETF..." .Well said :)
>
>
>
>
>   *Best wishes*
>
> *=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9=88*
>
> *Nabil Benamar*
>
> *Moulay Ismail University.*
>
> *Meknes. Morocco*
>
> *nabilbenamar.com <http://nabilbenamar.com>*
>
>
>
> On Tue, Feb 25, 2014 at 11:32 AM, IETF Chair <chair@ietf.org> wrote:
>
> I would like to welcome you all to our meeting in London next week. Here
> are some thoughts for the week from my perspective:
>
> http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/
>
> Jari Arkko, IETF Chair
>
> _______________________________________________
> 89all mailing list
> 89all@ietf.org
> https://www.ietf.org/mailman/listinfo/89all
>
>
>
>
>
> _________________________________________________________________________=
________________________________________________
>
> Ce message et ses pieces jointes peuvent contenir des informations confid=
entielles ou privilegiees et ne doivent donc
> pas etre diffuses, exploites ou copies sans autorisation. Si vous avez re=
cu ce message par erreur, veuillez le signaler
> a l'expediteur et le detruire ainsi que les pieces jointes. Les messages =
electroniques etant susceptibles d'alteration,
> Orange decline toute responsabilite si ce message a ete altere, deforme o=
u falsifie. Merci.
>
> This message and its attachments may contain confidential or privileged i=
nformation that may be protected by law;
> they should not be distributed, used or copied without authorisation.
> If you have received this email in error, please notify the sender and de=
lete this message and its attachments.
> As emails may be altered, Orange is not liable for messages that have bee=
n modified, changed or falsified.
> Thank you.
>
>
> _______________________________________________
> 89attendees mailing list
> 89attendees@ietf.org
> https://www.ietf.org/mailman/listinfo/89attendees
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:verdana,=
sans-serif;font-size:large;color:rgb(61,133,198)">Hi Abdelmoniem,</div><div=
 class=3D"gmail_default" style=3D"font-family:verdana,sans-serif;font-size:=
large;color:rgb(61,133,198)">
<br></div><div class=3D"gmail_default" style=3D"font-family:verdana,sans-se=
rif;font-size:large;color:rgb(61,133,198)">here is the link for the remote =
participation:</div><div class=3D"gmail_default"><font color=3D"#3d85c6" fa=
ce=3D"verdana, sans-serif" size=3D"4"><a href=3D"http://www.ietf.org/meetin=
g/89/remote-participation.html">http://www.ietf.org/meeting/89/remote-parti=
cipation.html</a></font><br>
</div><div class=3D"gmail_default"><font color=3D"#3d85c6" face=3D"verdana,=
 sans-serif" size=3D"4"><br></font></div><div class=3D"gmail_default"><font=
 color=3D"#3d85c6" face=3D"verdana, sans-serif" size=3D"4">All the best</fo=
nt></div></div>
<div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr"><div sty=
le=3D"text-align:left"><font color=3D"#1f497d" face=3D"sans-serif"><span st=
yle=3D"font-size:15px"><b>Best wishes</b></span></font></div><div dir=3D"rt=
l" style=3D"text-align:left">
<font color=3D"#1f497d" face=3D"sans-serif"><span style=3D"font-size:15px">=
<b>=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=D9=86=D8=B9=D9=85=D8=B1=D9=88</b></span>=
</font></div><div style=3D"text-align:left"><font color=3D"#1f497d" face=3D=
"sans-serif"><span style=3D"font-size:15px"><b>Nabil Benamar</b></span></fo=
nt></div>
<div style=3D"text-align:left"><font color=3D"#1f497d" face=3D"sans-serif">=
<b>Moulay Ismail University.</b></font></div><div style=3D"text-align:left"=
><font color=3D"#1f497d" face=3D"sans-serif"><b>Meknes. Morocco</b></font><=
/div><div style=3D"text-align:left">
<font color=3D"#1f497d" face=3D"sans-serif"><b><a href=3D"http://nabilbenam=
ar.com" target=3D"_blank">nabilbenamar.com</a></b></font></div></div></div>
<br><br><div class=3D"gmail_quote">On Wed, Feb 26, 2014 at 9:28 AM,  <span =
dir=3D"ltr">&lt;<a href=3D"mailto:abdelmoniem.rezk@orange.com" target=3D"_b=
lank">abdelmoniem.rezk@orange.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 .8ex;border-left:1px #ccc solid;border-=
right:1px #ccc solid;padding-left:1ex;padding-right:1ex">






<div lang=3D"EN-GB" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Guys<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#1f497d">I am registered to attend=
 the event remotely , I wonder how this is coordinated and is there any liv=
e sessions through web collaborations or conferencing ?<u></u><u></u></span=
></p>

<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#1f497d">Thanks and Best Regards<u=
></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;"><img width=3D"40" height=3D"40" src=3D"=
cid:image001.gif@01CF32D5.0D6995C0" alt=3D"http://www.orange.com/sirius/log=
os_mail/orange_logo.gif"></span><span style=3D"font-size:10.0pt;font-family=
:&quot;Verdana&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u><u></u></=
span></p>

<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Verdana&quot;,&quot;sans-serif&quot;;color:#1f497d">Abdelmoniem Rezk ,M.Sc=
.,MIET,MIEEE<u></u><u></u></span></b></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US" style=3D"font-size:10.0pt;fo=
nt-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span =
lang=3D"EN-US" style=3D"font-size:10.0pt;font-family:&quot;Tahoma&quot;,&qu=
ot;sans-serif&quot;"> 89attendees [mailto:<a href=3D"mailto:89attendees-bou=
nces@ietf.org" target=3D"_blank">89attendees-bounces@ietf.org</a>]
<b>On Behalf Of </b>Nabil Benamar<br>
<b>Sent:</b> 26 February 2014 06:42<br>
<b>To:</b> <a href=3D"mailto:89attendees@ietf.org" target=3D"_blank">89atte=
ndees@ietf.org</a><br>
<b>Cc:</b> <a href=3D"mailto:89all@ietf.org" target=3D"_blank">89all@ietf.o=
rg</a>; <a href=3D"mailto:ietf@ietf.org" target=3D"_blank">ietf@ietf.org</a=
> Discussion; <a href=3D"mailto:ietf-announce@ietf.org" target=3D"_blank">i=
etf-announce@ietf.org</a><br>

<b>Subject:</b> Re: [89attendees] [89all] Welcome to IETF-89<u></u><u></u><=
/span></p><div><div class=3D"h5">
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:18.0pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#3d85c6">So, lot of thanks to ICAN=
N for hosting this meeting !=C2=A0<u></u><u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><br clear=3D"all">
<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.5pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#1f497d">Best wishes</span></b><u=
></u><u></u></p>
<p class=3D"MsoNormal" align=3D"right" dir=3D"RTL" style=3D"text-align:left=
;direction:rtl">
<b><span lang=3D"AR-SA" style=3D"font-size:11.5pt;font-family:&quot;Arial&q=
uot;,&quot;sans-serif&quot;;color:#1f497d">=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=
=D9=86=D8=B9=D9=85=D8=B1=D9=88</span></b><span dir=3D"LTR"><u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:11.5pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#1f497d">Nabil Benamar</span></b>=
<span lang=3D"AR-SA" dir=3D"RTL"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;;color:#1f497d">Moulay Ismail University.</span></b><u></=
u><u></u></p>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;;color:#1f497d">Meknes. Morocco</span></b><u></u><u></u><=
/p>
<p class=3D"MsoNormal"><b><span style=3D"font-family:&quot;Arial&quot;,&quo=
t;sans-serif&quot;;color:#1f497d"><a href=3D"http://nabilbenamar.com" targe=
t=3D"_blank">nabilbenamar.com</a></span></b><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=C2=A0<u></u><=
/p>
<div>
<p class=3D"MsoNormal">On Wed, Feb 26, 2014 at 6:34 AM, Nabil Benamar &lt;<=
a href=3D"mailto:benamar73@gmail.com" target=3D"_blank">benamar73@gmail.com=
</a>&gt; wrote:<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#3d85c6">Dear Jari,</span><span st=
yle=3D"font-family:&quot;Verdana&quot;,&quot;sans-serif&quot;"><u></u><u></=
u></span></p>

</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Verdana&quot;,&quot=
;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;font-family:&quot;Ve=
rdana&quot;,&quot;sans-serif&quot;;color:#3d85c6">Thank you for the nice wo=
rds and invitation...I have particularly appreciated this comment in your m=
essage:&quot;=C2=A0ICANN is a consumer of the technology that we produce
 at the IETF...&quot;=C2=A0.Well said :)</span><span style=3D"font-family:&=
quot;Verdana&quot;,&quot;sans-serif&quot;"><u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Verdana&quot;,&quot=
;sans-serif&quot;"><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;color:#3d85c6"><br c=
lear=3D"all">
</span><u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#3d85c6">Best wishes</span></b><u=
></u><u></u></p>
<p class=3D"MsoNormal" align=3D"right" dir=3D"RTL" style=3D"text-align:left=
;direction:rtl">
<b><span lang=3D"AR-SA" style=3D"font-size:13.5pt;font-family:&quot;Arial&q=
uot;,&quot;sans-serif&quot;;color:#3d85c6">=D9=86=D8=A8=D9=8A=D9=84 =D8=A8=
=D9=86=D8=B9=D9=85=D8=B1=D9=88</span></b><span dir=3D"LTR"><u></u><u></u></=
span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#3d85c6">Nabil Benamar</span></b>=
<span lang=3D"AR-SA" dir=3D"RTL" style=3D"color:#888888"><u></u><u></u></sp=
an></p>

<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#3d85c6">Moulay Ismail University=
.</span></b><span style=3D"color:#888888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#3d85c6">Meknes. Morocco</span></=
b><span style=3D"color:#888888"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:13.5pt;font-family:&quot=
;Arial&quot;,&quot;sans-serif&quot;;color:#3d85c6"><a href=3D"http://nabilb=
enamar.com" target=3D"_blank">nabilbenamar.com</a></span></b><span style=3D=
"color:#888888"><u></u><u></u></span></p>

</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><u></u>=C2=A0<u></u><=
/p>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;color:#3d85c6">On Tu=
e, Feb 25, 2014 at 11:32 AM, IETF Chair &lt;<a href=3D"mailto:chair@ietf.or=
g" target=3D"_blank">chair@ietf.org</a>&gt; wrote:</span><u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:13.5pt;color:#3d85c6">I wou=
ld like to welcome you all to our meeting in London next week. Here are som=
e thoughts for the week from my perspective:<br>
<br>
<a href=3D"http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/" target=3D"=
_blank">http://www.ietf.org/blog/2014/02/welcome-to-ietf-89/</a><br>
<br>
Jari Arkko, IETF Chair<br>
<br>
_______________________________________________<br>
89all mailing list<br>
<a href=3D"mailto:89all@ietf.org" target=3D"_blank">89all@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/89all" target=3D"_blank">h=
ttps://www.ietf.org/mailman/listinfo/89all</a></span><u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div></div></div>
<pre>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu=
 ce message par erreur, veuillez le signaler
a l&#39;expediteur et le detruire ainsi que les pieces jointes. Les message=
s electroniques etant susceptibles d&#39;alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou =
falsifie. Merci.

This message and its attachments may contain confidential or privileged inf=
ormation that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and dele=
te this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been =
modified, changed or falsified.
Thank you.
</pre></div>

<br>_______________________________________________<br>
89attendees mailing list<br>
<a href=3D"mailto:89attendees@ietf.org">89attendees@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/89attendees" target=3D"_bl=
ank">https://www.ietf.org/mailman/listinfo/89attendees</a><br>
<br></blockquote></div><br></div>

--001a11c2a5f60b42c704f34bec38--
--001a11c2a5f60b42c904f34bec39
Content-Type: image/gif; name="image001.gif"
Content-Disposition: inline; filename="image001.gif"
Content-Transfer-Encoding: base64
Content-ID: <image001.gif@01CF32D5.0D6995C0>
X-Attachment-Id: 60a60e035a267871_0.0.1

R0lGODlhKAAoAPcAAP9mAP9lAP////9jAP9kAP9gAP9eAP9dAP9iAP9fAP/x5/9cAP9YAP9ZAP/6
9v+3i/9yGf9lBP+ygv/n1/+IQf/Xvf/fyf+kbP+3if/LrP9jAv9oBv+7kP9oCP91Hf/UuP9xF/+/
lv/awP9mB/+JPf+XV/+EPP+KPf/y6f+HQf+HQv9pC/+PRf/s4f/59f9/Mv9kAv9lAv+cXf/IpP/8
+v/8+P+4jf/Stf9VAP/Ttv/Bmf/Lq/9sDv9vEP9sC/+JPv+2hv9xFv+VUP+ALf9zGv+1h//w5v/u
4v9kBf/JqP/Vuv+3h/+KQv+IQv+2h/9kC/+9k//t4v92G//dyf9bAP9vEv+zhf9aAP91JP/07P/D
nf/awf+UT/9pCP/dxv/Nrv+pc//p2v9hAP+GPf9pBv+GP/9iA/9iCv+ocv+QSv/Zwv/AmP+8j/+d
Xv/Mqv+lbf/Psf+IOv/7+P/Orv9nCP+SU/96Lv96J//j0f9nA/9eBP/bw//aw//k1P+STf/r3f/n
1v/Ipf+6jf+gZ/+eYv/Lqv/Mrf/gzP9zG/+xgP+ygf/XvP/gzf+JQf/Cm/+VVf+FOP/fzP+QTP/h
zv/Xvv+LRv/Gn//s3/+4iv9kAf9rFP+tdv9rCP9lAf9yFv+pcf94KP+xe//Yv/94If9pCv+COf+Z
Vf+ue/+7kf9XAP9nCv/q3f9iAf+9lP9uEf9oA//l1P+FN////f+ncv+OR//v5f/y5/+aX/+hY/9+
K/9hAf/59P+hZ/+IPv+fYv90Gv/Qs/+XVf9wE/+VVP9+Lf+YWP/eyf+mbv9+Mf96Jv91HP/HpP+8
kQAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACH5BAAAAAAALAAAAAAoACgA
AAj/AAEIHEiwoMGDCBMqXMiwocOHECNKnEixosWLGDNq3Mixo8ePIEOKHEmypMmTKFOqXMmypcuQ
AQYQCEBAZABOUnqM8FEQwQCBNGkKHPATQICjMoEimBlgaIFfYNAk2lTAKREIBQa86sKqigZdiEAU
INBpABIPqmSaUbYiAhkCCUBAeNKIVihTPwnwWFZDjpYBvQBROvSigi0FIRBgEKXExR5XGgI5sIBn
yQIMClA4ikAgUwyBB04JuDBLwJsxAiK1IWbFjgQBpZLIenRLQJphAiT5EsDGj4A6JhzIOECwwBY+
DK5MmtNEgAkcHS4AYyQgRYYJDbAIEBKiz4IztaA4zRFwA44DZsQHJqgwpQEVWG4oCIjDYE0WUCUE
lMkQpkAyAVxwEIUemuzCARA0QDJKLp40NdABxwjwACoCECLfCal80UIlHwiggiF/FHCHAMEwIcAO
OQggCAkSlmABCVUNFAAdRaCggAQFxCLCEAv8YIwXrSyCjCIzIOCBCCw0gIsaNhhhCQO8THCJDsIU
NRABBmywgQFINSWGTAYMQNNPMSVwwgfFDCLAJwcYAEMeBtR00EwyytjUnQ7GFEQhR6yCSQc1HeUR
XKSMEKdCAQEAOw==
--001a11c2a5f60b42c904f34bec39--


From nobody Wed Feb 26 09:14:02 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 E77E01A06E4 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 09:13:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 WmlrIQQUNTR6 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 09:13:53 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 395821A06EC for <ietf@ietf.org>; Wed, 26 Feb 2014 09:13:52 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1QHDaah001945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Feb 2014 09:13:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393434830; bh=jWAts5N6WC1Q2BnWXv8ZSkofNd4KX/I1YuiBtvyu7Zs=; h=Date:To:From:Subject:In-Reply-To:References; b=JYXS0UA52CMft13hQxfXyW3wRBrWMxbNsR4Wszg1NhqPxgCwVFSwJ4XqjVjkfTzCJ h6XEVPc4TanTt0HIVA1nT071V4tXxGY+jbLz+H4zLeKP/2Uz5CxfS+PNYKpV4D7QW2 4WqELeCwa4myni5UYBRVqO8LuPsM8LGItOgZw0S8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393434830; i=@elandsys.com; bh=jWAts5N6WC1Q2BnWXv8ZSkofNd4KX/I1YuiBtvyu7Zs=; h=Date:To:From:Subject:In-Reply-To:References; b=yEqTaSwmFh9js5EGhL0eGrOJP+n2PaNuMVoMh/CYmR/gGK28/Zj9h7s6I8uDHJ3TN RxDZ6vjq+wQsQYG8HcyMwaMWJ0Hvshv1HobXySg4Hqm8Au19ZXvjyXLSkQj6cKT8nx UdBChFGFWB7MUYvYLLWFhIQq13/TMRlXD9rubbus=
Message-Id: <6.2.5.6.2.20140226074723.0e37af20@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 26 Feb 2014 08:55:32 -0800
To: adrian@olddog.co.uk, John C Klensin <john-ietf@jck.com>, ietf@ietf.org
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/J3QzLkbOuolXTg1QAlPCB-rJNps
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 17:13:55 -0000

Hi Adrian, John,
At 05:57 26-02-2014, Adrian Farrel wrote:
>The point you make in your second paragraph is very valid, but it is hard to
>comment on your first paragraph without details.
>
>Would you care to phrase the issue succinctly so that a (moderately) 
>definitive
>statement can be made?

I consider the matter as closed.

At 05:59 26-02-2014, John C Klensin wrote:

Please note that I did not ignore your message.  In my opinion the 
discussion would get out of hand.

Regards,
S. Moonesamy 


From nobody Wed Feb 26 09:14:11 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 A0B151A06F2 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 09:14:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 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.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PqSH_JCGXtNj for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 09:14:01 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D8501A06EF for <ietf@ietf.org>; Wed, 26 Feb 2014 09:13:56 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1QHDaaj001945 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Feb 2014 09:13:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393434834; bh=yDpYJIl3ghPJlmdfe3v3Qx4QT3+OnIavkQ8/Oh5ndp0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JsSuMGCJqapxNZVqAIGBTqpNC7qBk9L/LaoqM13PsDZa0206mwpat/73qI25I1EhG Nsv+AEWSk7xsOydo1gv7v3S6pBh/FgcRWuULUOObG3p5SOlIuly3/Of8r5J2nA9rYA E8kQfgh/4VapzvSYlJXR1BB2e/SrHBzWkQo7yWZg=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393434834; i=@elandsys.com; bh=yDpYJIl3ghPJlmdfe3v3Qx4QT3+OnIavkQ8/Oh5ndp0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=qs5qyE+SaIN4IN6opRCVtEQKFeJLlbNoWAaj0iYJFZTS9SH7fNHHeD9KMubYfUhrx HO3WnuEB74s9DKDK9Wo4MKIk2Ck6aogrk848sHgzed6xgP77iURO1e27087ZcCR0om INBxIHlPCUOsGGQPKWW0pDFxTJ3oYs5JoqfDkK3A=
Message-Id: <6.2.5.6.2.20140226085842.0d42b268@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 26 Feb 2014 09:12:56 -0800
To: John C Klensin <john-ietf@jck.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
In-Reply-To: <884F51283FE98A20FB8E7EC2@JcK-HP8200.jck.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <m2zjleji25.wl%randy@psg.com> <6.2.5.6.2.20140226043234.0d0a0f60@elandnews.com> <884F51283FE98A20FB8E7EC2@JcK-HP8200.jck.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eDXXSpG-bOyJy8g1-9_mLFG6mHc
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, 26 Feb 2014 17:14:02 -0000

Hi John,
At 05:59 26-02-2014, John C Klensin wrote:
>Without details, the above is indistinguishable from innuendo.
>That is not helpful in informing the rest of us about anything
>other than that there are differences in opinion and perspective
>in the community (I trust that doesn't surprise anyone).  I
>recommend (in public because this context seems to require it)
>that you go back to the person who made that comment, note the
>contradiction, and ask for permission to bring the IESG (or
>relevant ADs) into the conversation.  I hope we can look forward
>to a report on your conclusions after the discussions that
>should result.

I suggested posting the comment to the ietf@ietf.org mailing list 
before I posted my message.

I'll comment from a general perspective.  People do not mention 
advice publicly as the difference of opinions might be 
highlighted.  My guess is that there are differences of opinions even 
between Area Directors. :-)  I think that some people would be 
surprised to hear what is said in private and what is said in public.

Take care,
-sm 


From nobody Wed Feb 26 09:30:31 2014
Return-Path: <joelja@bogus.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73AC91A06FD for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 09:30:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UIx-fnB5hkky for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 09:30:21 -0800 (PST)
Received: from nagasaki.bogus.com (nagasaki.bogus.com [IPv6:2001:418:1::81]) by ietfa.amsl.com (Postfix) with ESMTP id 3E44F1A0163 for <ietf@ietf.org>; Wed, 26 Feb 2014 09:30:20 -0800 (PST)
Received: from [192.168.43.134] ([172.56.38.90]) (authenticated bits=0) by nagasaki.bogus.com (8.14.7/8.14.7) with ESMTP id s1QHT6xP075337 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 26 Feb 2014 17:29:10 GMT (envelope-from joelja@bogus.com)
Message-ID: <530E245C.4070904@bogus.com>
Date: Wed, 26 Feb 2014 09:29:00 -0800
From: joel jaeggli <joelja@bogus.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:27.0) Gecko/20100101 Thunderbird/27.0
MIME-Version: 1.0
To: S Moonesamy <sm+ietf@elandsys.com>, John C Klensin <john-ietf@jck.com>
Subject: Re: A private club
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <m2zjleji25.wl%randy@psg.com> <6.2.5.6.2.20140226043234.0d0a0f60@elandnews.com> <884F51283FE98A20FB8E7EC2@JcK-HP8200.jck.com> <6.2.5.6.2.20140226085842.0d42b268@elandnews.com>
In-Reply-To: <6.2.5.6.2.20140226085842.0d42b268@elandnews.com>
X-Enigmail-Version: 1.6
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xS8HSwsDkSwbtAb4XIL6TmD90rvDWQfBD"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (nagasaki.bogus.com [147.28.0.81]); Wed, 26 Feb 2014 17:29:11 +0000 (UTC)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/yO81pcAzxpKwc8ltlImY6JMl0rE
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, 26 Feb 2014 17:30:23 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--xS8HSwsDkSwbtAb4XIL6TmD90rvDWQfBD
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 2/26/14, 9:12 AM, S Moonesamy wrote:

>  My guess
> is that there are differences of opinions even between Area Directors.

Anyone whose ever read the minutes if an IESG meeting, knows that there
are differences of opinion especially among area directors.

http://www.ietf.org/iesg/minutes.html



--xS8HSwsDkSwbtAb4XIL6TmD90rvDWQfBD
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 Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlMOJFwACgkQ8AA1q7Z/VrKpSQCfZc6hFAelHgGIR7gOoei7TTO1
oiUAn2Zl1IqNZBLc+yb7IKfzeCsOk2dk
=5zDp
-----END PGP SIGNATURE-----

--xS8HSwsDkSwbtAb4XIL6TmD90rvDWQfBD--


From nobody Wed Feb 26 11:06:27 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 1F2EA1A0205 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 11:06:23 -0800 (PST)
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 3IYYQOLsXfBA for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 11:06:20 -0800 (PST)
Received: from mail-pb0-x233.google.com (mail-pb0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id 7940B1A010F for <ietf@ietf.org>; Wed, 26 Feb 2014 11:06:20 -0800 (PST)
Received: by mail-pb0-f51.google.com with SMTP id un15so1387833pbc.24 for <ietf@ietf.org>; Wed, 26 Feb 2014 11:06:19 -0800 (PST)
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=6z8qIJHLJ1auVp1ZKyDkCzIgBspon3ZQ0ZKdJG/40B8=; b=kYOoT+7tnrXvnABo3wanwGvPuZVfcYOMq0NUih7EAdczyICVNRQ2DaNMKHl6lWf2bJ e5RUCTK9sBKZDDveqotb88VWfwUZmBM1d3BItQZZrTfR+KtvmKBv0AfsdCM3OrfQUCcn QpFXfEnOAYMfb4we5Q0ZacKngxltkyX6EfjODbr1IS04cezSdCbqKT8zc6z1WE/uskca GN762FyYmyZDtN4d2bL75zTaPVd5W/kbBA0fFVS9uJo70Zce91W7sSMcRMzYf/akziNg 082v/a3sO4afEUedWGJ9vjzUc5LtImdwdKaXz196t9jArpl5tVPbRJvd2eLTjoWK9Wj3 7waw==
X-Received: by 10.68.223.193 with SMTP id qw1mr8826138pbc.16.1393441579166; Wed, 26 Feb 2014 11:06:19 -0800 (PST)
Received: from [192.168.178.23] (39.194.69.111.dynamic.snap.net.nz. [111.69.194.39]) by mx.google.com with ESMTPSA id fk4sm12804729pab.23.2014.02.26.11.06.16 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Feb 2014 11:06:18 -0800 (PST)
Message-ID: <530E3B27.5030508@gmail.com>
Date: Thu, 27 Feb 2014 08:06:15 +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: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net>
In-Reply-To: <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/CmakYm5Oig-9ibNP1Q66ELTEmw0
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, 26 Feb 2014 19:06:23 -0000

On 26/02/2014 21:34, S Moonesamy wrote:
...
> I am not comfortable stating that there is consensus on an
> Internet-Draft when participation is from a small number of individuals
> having some affiliation in common.  That creates an appearance of a
> private club.

But participation is open to everybody; if I don't choose to comment
on a draft, that is my problem, not the problem of those who do
comment. Nobody has ever told me that I am not allowed to comment.

> It is difficult to convince someone who is, for example, from a
> developing country that the IETF is a large open international community
> when a quick look at
> http://www.ietf.org/mail-archive/web/ietf/current/maillist.html shows
> that there has only been participation from individuals from one or two
> countries.

I'm sorry... which particular mail threads do you mean? Anyway, a
lot of comments come from a country called gmail, which you won't
find in the UN list.

I understand that it's hard for people to understand that there
is no barrier to speech in the IETF and that there is no secret
handshake.

On 27/02/2014 06:12, S Moonesamy wrote:

...
> I think that some people would be surprised to hear what is said in private and what is said in public. 

Really? It seems to me to be a universal aspect of human behaviour
that people are more disciplined and careful when speaking in
public than when speaking in private. If my private opinion is that
some IETF work is "Yuck", "Pointless", or "Relatively harmless"
(examples from my private notes) I am unlikely to say so in public.
I would use more analytic language.

    Brian


From nobody Wed Feb 26 11:18:59 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 A77D41A016E for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 11:18:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.768
X-Spam-Level: 
X-Spam-Status: No, score=-1.768 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.547, SPF_NEUTRAL=0.779] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60nB8fuB-8L0 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 11:18:50 -0800 (PST)
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 889A61A0860 for <ietf@ietf.org>; Wed, 26 Feb 2014 11:18:50 -0800 (PST)
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 s1QJISTE006369; Wed, 26 Feb 2014 19:18:28 GMT
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s1QJISTE006369
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1393442308; bh=H4hYTqpEYMyHuuY6D/6Qrb87tQ4=; h=References:Mime-Version:In-Reply-To:Cc:From:Subject:Date:To; b=J7d4Q751DME4Y8FEFEOlTNAvBdseP6v4k6q1wwDyQx3rt1IBMqF88xOcr9S8T/fOZ fJq6Go+3mLmC7bPslrGLfzI038YWedZ6JXsN86CX79X7Ne+MFR0ev6GruZBDock5nN Ds03vxntLPe+iokvLFjLgUFkhkuhkOQ6mfy4IwJ0=
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 q1PJIS0959629576ZF ret-id none; Wed, 26 Feb 2014 19:18:28 +0000
Received: from [10.5.112.112] (dab-ntm1-h-60-9.dab.02.net [82.132.231.136]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s1QJIMIH022513 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 26 Feb 2014 19:18:25 GMT
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com> <F20E0403-2380-4186-9177-216BD001C66B@ecs.soton.ac.uk>
Mime-Version: 1.0 (1.0)
In-Reply-To: <530E3B27.5030508@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|7438390d6ed69415c616d67f90b01a78q1PJIS03tjc|ecs.soton.ac.uk|F20E0403-2380-4186-9177-216BD001C66B@ecs.soton.ac.uk>
X-Mailer: iPhone Mail (11B554a)
From: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: A private club
Date: Wed, 26 Feb 2014 19:18:18 +0000
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q1PJIS095962957600; tid=q1PJIS0959629576ZF; 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: s1QJISTE006369
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/bluRvgXSx_abzV6eNq2tgTpqPgc
Cc: S Moonesamy <sm+ietf@elandsys.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, 26 Feb 2014 19:18:56 -0000

> On 26 Feb 2014, at 19:06, Brian E Carpenter <brian.e.carpenter@gmail.com> w=
rote:.
>=20
> I'm sorry... which particular mail threads do you mean? Anyway, a
> lot of comments come from a country called gmail, which you won't
> find in the UN list.

Yet!

tim


From nobody Wed Feb 26 11:36:09 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 5B9211A0141 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 11:36:04 -0800 (PST)
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_50=0.8, HELO_EQ_SE=0.35, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6bGteb0z5AOt for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 11:35:59 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id B9D4C1A01A7 for <ietf@ietf.org>; Wed, 26 Feb 2014 11:35:59 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 9CB28A3; Wed, 26 Feb 2014 20:35:57 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 953549A for <ietf@ietf.org>; Wed, 26 Feb 2014 20:35:57 +0100 (CET)
Date: Wed, 26 Feb 2014 20:35:57 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf@ietf.org
Subject: Re: A private club
In-Reply-To: <530E3B27.5030508@gmail.com>
Message-ID: <alpine.DEB.2.02.1402262021170.747@uplift.swm.pp.se>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.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/uWsX7XnxQXBgqhPisUfVNjn_gw0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Feb 2014 19:36:04 -0000

On Thu, 27 Feb 2014, Brian E Carpenter wrote:

> I understand that it's hard for people to understand that there is no 
> barrier to speech in the IETF and that there is no secret handshake.

There are no *formal* barriers. I like that about the IETF, but I don't 
agree that there are no barriers. I'd imagine a lot of people will be shy 
to join a discussion and voice their opinion, especially if they're not 
used to the discussion climate. In some cultures I imagine it's not common 
that one voices a dissenting opinion against the sitting chairman of that 
organisation.

I have no idea how to improve this, I personally find the IETF to be 
extremely open, but I also know a lot of people who are intimidated by the 
thought of going up against the world "elite" and voicing their opinion. 
Few people feel comfortable doing that.

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


From nobody Wed Feb 26 11:42:30 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 77F791A06E2 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 11:42:23 -0800 (PST)
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 i_cG5PERZT_8 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 11:42:21 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 4D73D1A0117 for <ietf@ietf.org>; Wed, 26 Feb 2014 11:42:17 -0800 (PST)
Received: by mail-pa0-f42.google.com with SMTP id kl14so1415267pab.29 for <ietf@ietf.org>; Wed, 26 Feb 2014 11:42:16 -0800 (PST)
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=qDuOhvsJF+PuP1IpR+txnPV9i9ujw2q1EVQy8SLsFhs=; b=UqiysgUbOgDCvKvGgfcQ4k10L9CrZyKwN7MC+QocxWPkr6EUe9z9W2mkfAYhpUtDmO DiCo5UUJDznmxewD6JeWpjh3HPdGqF9+OXNjiuzLt/XOYAoXuH5FTRiRArdVQjvRCMe3 a5PHQNtBPwLjW8HWWhNFkKneFU0KOBowYHlltjF7F4Tvkx482ReuxrAuArx3YFG9CqNP 1Fxrf+i/91nWY4LyUgv6B9l9tx2j9Bb1a/YlfpmzsuSa3atx16m1wZZZYHqYlzPOIlkH 5h2mdfWKLZDvQg0aY2YC7cqv/h+evQiddXSPO4YbLz06VZZ4SlyzM6EgRA3R8HbHgZ0h hZvA==
X-Received: by 10.69.1.2 with SMTP id bc2mr8881172pbd.102.1393443736020; Wed, 26 Feb 2014 11:42:16 -0800 (PST)
Received: from [192.168.178.23] (39.194.69.111.dynamic.snap.net.nz. [111.69.194.39]) by mx.google.com with ESMTPSA id vf7sm6072675pbc.5.2014.02.26.11.42.13 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Feb 2014 11:42:15 -0800 (PST)
Message-ID: <530E439B.1050509@gmail.com>
Date: Thu, 27 Feb 2014 08:42:19 +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: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: A private club
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com> <alpine.DEB.2.02.1402262021170.747@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1402262021170.747@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/MjGjxIFXFvWFClRCbDxKKJbhEGI
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, 26 Feb 2014 19:42:23 -0000

On 27/02/2014 08:35, Mikael Abrahamsson wrote:
> On Thu, 27 Feb 2014, Brian E Carpenter wrote:
> 
>> I understand that it's hard for people to understand that there is no
>> barrier to speech in the IETF and that there is no secret handshake.
> 
> There are no *formal* barriers. I like that about the IETF, but I don't
> agree that there are no barriers. I'd imagine a lot of people will be
> shy to join a discussion and voice their opinion, especially if they're
> not used to the discussion climate. In some cultures I imagine it's not
> common that one voices a dissenting opinion against the sitting chairman
> of that organisation.
> 
> I have no idea how to improve this, I personally find the IETF to be
> extremely open, but I also know a lot of people who are intimidated by
> the thought of going up against the world "elite" and voicing their
> opinion. Few people feel comfortable doing that.

Correct, but I suspect that this depends on the individual at least
as much as on the individual's culture.

As I've said before: suggestions for improving http://www.ietf.org/newcomers.html
are always welcome.

    Brian


From nobody Wed Feb 26 12:46:43 2014
Return-Path: <llynch@civil-tongue.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 8F0711A016E for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 12:46:40 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7_aopOyWAXR8 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 12:46:35 -0800 (PST)
Received: from hans.rg.net (hans.rg.net [IPv6:2001:418:1::42]) by ietfa.amsl.com (Postfix) with ESMTP id D87191A014B for <ietf@ietf.org>; Wed, 26 Feb 2014 12:46:35 -0800 (PST)
Received: from hiroshima.bogus.com (hiroshima.bogus.com [IPv6:2001:418:1::80]) (authenticated bits=0) by hans.rg.net (8.14.7/8.14.7) with ESMTP id s1QKkXu8095914 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 26 Feb 2014 20:46:34 GMT (envelope-from llynch@civil-tongue.net)
Date: Wed, 26 Feb 2014 12:46:33 -0800 (PST)
From: Lucy Lynch <llynch@civil-tongue.net>
X-X-Sender: llynch@hiroshima.bogus.com
To: Izaac <izaac@setec.org>
Subject: squeaky dolphin (was Re: Ad hominems)
In-Reply-To: <eafd3372-12d7-4e6c-a9c3-cd4e97aeb440@email.android.com>
Message-ID: <alpine.BSF.2.00.1402261245490.17543@hiroshima.bogus.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com> <m27g8imwij.wl%randy@psg.com> <eafd3372-12d7-4e6c-a9c3-cd4e97aeb440@email.android.com>
User-Agent: Alpine 2.00 (BSF 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2zViv99NxysmwUz6l3kh-9N89W0
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, 26 Feb 2014 20:46:40 -0000

Ok -

You guys are trying to make me laugh - cyber magicians!

cryptome.org/2014/02/gchq-online-deception.pdf
cryptome.org/2014/01/gchq-squeaky-dolphin.pdf

- Lucy

On Wed, 26 Feb 2014, Izaac wrote:

> Randy Bush <randy@psg.com> wrote:
>>> Speak to Dave.
>>
>> who's dave?
>
> Dave's not here, man.
>
>


From nobody Wed Feb 26 14:34:57 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 2C1491A0257 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 14:34:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.937
X-Spam-Level: 
X-Spam-Status: No, score=-0.937 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 dDY2QsZspL3J for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 14:34:47 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CD891A00BA for <ietf@ietf.org>; Wed, 26 Feb 2014 14:34:47 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1QMYRb3004129 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Feb 2014 14:34:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393454080; bh=ABUxRXCwzMO4v22LCBa7BMMt1G6gbdvXAvVGfdQGe2U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=YkONZkb7vPyJnAz4Br7AflaNlY22I7QQ9NcU6L2+Nn7UCNvRNO3W1q0xdEX4djATQ timn3mBFGkL723DVRCF1H0/ozlQvQ6DZHeetSkrqx56dsk4cOyCniifhE+sE3Wvz1G Hx8wEc9StTYv+SrgJ3XBTZo+aQLVDO+eVHW5bdI0=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393454080; i=@elandsys.com; bh=ABUxRXCwzMO4v22LCBa7BMMt1G6gbdvXAvVGfdQGe2U=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=4umYRLc571Jr6EQ9zt+YFHAVtdHQKAaG3/rhhG166YVUjChektlr1piV6NU/yutGl 0M3gavZ/yx8H6lRg2d8nTEU6/S5R9/D7nRc+QL9dFj+WKmcFLLMkfxxzZKaWr8GZUW U2P1dCW3IFxVzVhHF5JzkdECgv3bWvc7vgb/CUIQ=
Message-Id: <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 26 Feb 2014 14:21:07 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
In-Reply-To: <530E3B27.5030508@gmail.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/ivjELuuNyGXIVsiNIkOMdi_la3o
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, 26 Feb 2014 22:34:52 -0000

Hi Brian,
At 11:06 26-02-2014, Brian E Carpenter wrote:
>But participation is open to everybody; if I don't choose to comment
>on a draft, that is my problem, not the problem of those who do
>comment. Nobody has ever told me that I am not allowed to comment.

I am using "you" for clarity.  It is not intended as antagonism.  You 
have been participating in the IETF since a long time.  I don't think 
that someone would tell you that you are not allowed to comment.

If a person posts a comment and receives a sarcastic reply he or she 
will be uncomfortable to post more comments.  If a person sees 
"someone like him/her" receiving sarcastic replies the person will be 
uncomfortable to post a comment.

If the only comments posted are from participants affiliated with 
Vendor X I would not write that there is consensus for the draft to 
move forward.

>I'm sorry... which particular mail threads do you mean? Anyway, a
>lot of comments come from a country called gmail, which you won't
>find in the UN list.

There isn't a country called "gmail" in the UN list. :-)  I was not 
pointing to a particular mail thread.  If an Area Director asks for 
the list of countries I'll post it.

>I understand that it's hard for people to understand that there
>is no barrier to speech in the IETF and that there is no secret
>handshake.

I beg to differ on the "barrier to speech".  There is a message from 
a French reader at 
http://www.ietf.org/mail-archive/web/ietf/current/msg85043.html  The 
IAOC and Juliao Braga
had some difficulty understanding each other (if I recall correctly 
he asked me why I did not try to help).

There has been discussions about newcomers.  I do not derive any 
benefit by arguing in favor of newcomers except, maybe, getting some 
reviews for IETF work.  My conclusion from the discussions was that 
there are difficulties.

>Really? It seems to me to be a universal aspect of human behaviour
>that people are more disciplined and careful when speaking in
>public than when speaking in private. If my private opinion is that
>some IETF work is "Yuck", "Pointless", or "Relatively harmless"
>(examples from my private notes) I am unlikely to say so in public.
>I would use more analytic language.

I posted that message to ietf@ietf.org by mistake.

If I was having a discussion with someone I am familiar with about 
another person's draft I might write "relatively harmless".  I have 
never sent a private message to an author saying "Yuck".  Please note 
that I am not saying that the word is inappropriate.

If there is a pattern of insulting (private) comments from a 
person(s) who speaks nicely in public, would the regular IETF 
participant be aware of that?  That is what I thought about when I 
responded to the "I trust that doesn't surprise anyone." written by 
John Klensin.

Regards,
S. Moonesamy 


From nobody Wed Feb 26 14:51:17 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 6AE591A0726 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 14:51:10 -0800 (PST)
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 Hzc9w1kZOY5w for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 14:51:07 -0800 (PST)
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 1467B1A0723 for <ietf@ietf.org>; Wed, 26 Feb 2014 14:51:06 -0800 (PST)
Received: by mail-yk0-f174.google.com with SMTP id 20so4427087yks.5 for <ietf@ietf.org>; Wed, 26 Feb 2014 14:51:05 -0800 (PST)
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=oEsdCUbkEb021H5KwZrHAkQSlhE5qlkkaPHy8qUG00M=; b=l1Kv4xNUX9/8OI83mAOC2Fj4n6vjq5My422scQDqRYVmwWsoCAfxiOsPJI+iKY/MbP 63yImN5G8TsldvAP7DT1JyUpRBaxd/TeXvMvIfIWKoSjwaMtoVMX+BD7mv6nTGZYgVQU YYRkPoN69ozh45aHnt5DFuUSf1o2UV22nzgWNpTGaQjcDfyr8Uv+2UeJBkOhGjhSyGwe gZHtRsb0IiczJ/PVMzml5d/VacJO4uiA8Wlp3JRa/KNd8EBxFaEls/jj5iqS25XWPHAE 8Zxln9EScDdCiFLvLWaASvohz3XtiSmHDLlXhTqoDiohhgMXEB+rhXvVDcvMmuGEleE1 kZTA==
MIME-Version: 1.0
X-Received: by 10.236.124.193 with SMTP id x41mr11206378yhh.54.1393455065583;  Wed, 26 Feb 2014 14:51:05 -0800 (PST)
Received: by 10.170.186.70 with HTTP; Wed, 26 Feb 2014 14:51:05 -0800 (PST)
Received: by 10.170.186.70 with HTTP; Wed, 26 Feb 2014 14:51:05 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com> <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com>
Date: Wed, 26 Feb 2014 13:51:05 -0900
Message-ID: <CAKRbAfA3Jc3=Z3=Xpo4nCK371i+EodrBchwsB8BOz4JUP7RWVA@mail.gmail.com>
Subject: Re: A private club
From: Melinda Shore <melinda.shore@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=20cf303a364531d70904f3570ac0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9KOJ-IBp0UMdn1MDIMhf34T4jjs
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, 26 Feb 2014 22:51:10 -0000

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

I was apparently involved in this offline whatever and have absolutely no
idea what you're bothered by, or why.  More clarity and less innuendo would
be helpful.

Melinda

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

<p dir=3D"ltr">I was apparently involved in this offline whatever and have =
absolutely no idea what you&#39;re bothered by, or why.=A0 More clarity and=
 less innuendo would be helpful.=A0 </p>
<p dir=3D"ltr">Melinda</p>

--20cf303a364531d70904f3570ac0--


From nobody Wed Feb 26 14:58:37 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 C56F61A0790 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 14:58:31 -0800 (PST)
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 i9jjCVhKPIKW for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 14:58:27 -0800 (PST)
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 CA3641A078E for <ietf@ietf.org>; Wed, 26 Feb 2014 14:58:27 -0800 (PST)
Received: by mail-pd0-f170.google.com with SMTP id y10so1588773pdj.1 for <ietf@ietf.org>; Wed, 26 Feb 2014 14:58:26 -0800 (PST)
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=uDlEv0ltH4bveKe5E/s04GCG4mnjcv5WbMCFa8CDt8o=; b=SRZWja9oUhqbo8ECFVuSTmvdR/DfDfXM8Mj7tJr6hp691sIh9ccJoMREOq79CVNve4 VwfvOItemVsenTrYKuUWy2Vb9I8cZUNvYawpiSSD7GHwDBuwbXbi7d4NxpQO3lOyP3qE pDPXSISA/Gm7mfUz6mI/5neKbUaaYB3H87JosBtXRbU9FJRkUgOm9NFSPUe0hS9rlpcQ UlYyBxyXQZPouX+ydCXdbiiprmQikJyIE7W9h3z/oNhmi1rWZyD7pPVpSqnmuKZmvlZp WEy+1P+GY8abPtt/v77TR/kbp4bsdEKiCO/Jt7MxhEaLHF0+cLpWvwsmLDXt97I7b65/ MfKg==
X-Received: by 10.66.144.227 with SMTP id sp3mr11775053pab.100.1393455506602;  Wed, 26 Feb 2014 14:58:26 -0800 (PST)
Received: from [192.168.178.23] (39.194.69.111.dynamic.snap.net.nz. [111.69.194.39]) by mx.google.com with ESMTPSA id qf7sm16231998pac.14.2014.02.26.14.58.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 26 Feb 2014 14:58:26 -0800 (PST)
Message-ID: <530E7196.60103@gmail.com>
Date: Thu, 27 Feb 2014 11:58:30 +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: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com> <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3AvROXcYpkTLVG6qRRVmq6F_sBo
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, 26 Feb 2014 22:58:32 -0000

On 27/02/2014 11:21, S Moonesamy wrote:
> Hi Brian,
> At 11:06 26-02-2014, Brian E Carpenter wrote:
>> But participation is open to everybody; if I don't choose to comment
>> on a draft, that is my problem, not the problem of those who do
>> comment. Nobody has ever told me that I am not allowed to comment.
> 
> I am using "you" for clarity.  It is not intended as antagonism.  You
> have been participating in the IETF since a long time.  I don't think
> that someone would tell you that you are not allowed to comment.

Sorry, I should have used the impersonal "one" instead of "you".
I wasn't think about myself.

> If a person posts a comment and receives a sarcastic reply he or she
> will be uncomfortable to post more comments.  If a person sees "someone
> like him/her" receiving sarcastic replies the person will be
> uncomfortable to post a comment.

Indeed. Sarcasm is not a good tool for professional communication.
Unfortunately, sometimes a perfectly serious remark is (mis)understood
as sarcasm.

> If the only comments posted are from participants affiliated with Vendor
> X I would not write that there is consensus for the draft to move forward.

That's a real problem, but sometimes there is consensus in such a case,
and sometimes there is resignation. It's a matter of judgment, and one tha
a WG Chair has to make sometimes.

>> I'm sorry... which particular mail threads do you mean? Anyway, a
>> lot of comments come from a country called gmail, which you won't
>> find in the UN list.
> 
> There isn't a country called "gmail" in the UN list. :-)  I was not
> pointing to a particular mail thread.  If an Area Director asks for the
> list of countries I'll post it.
> 
>> I understand that it's hard for people to understand that there
>> is no barrier to speech in the IETF and that there is no secret
>> handshake.
> 
> I beg to differ on the "barrier to speech".  There is a message from a
> French reader at
> http://www.ietf.org/mail-archive/web/ietf/current/msg85043.html  The
> IAOC and Juliao Braga
> had some difficulty understanding each other (if I recall correctly he
> asked me why I did not try to help).

You're talking about a barrier to understanding. That's not what
I meant.

> There has been discussions about newcomers.  I do not derive any benefit
> by arguing in favor of newcomers except, maybe, getting some reviews for
> IETF work.  My conclusion from the discussions was that there are
> difficulties.

Of course there are. That's true in any large organisation.

>> Really? It seems to me to be a universal aspect of human behaviour
>> that people are more disciplined and careful when speaking in
>> public than when speaking in private. If my private opinion is that
>> some IETF work is "Yuck", "Pointless", or "Relatively harmless"
>> (examples from my private notes) I am unlikely to say so in public.
>> I would use more analytic language.
> 
> I posted that message to ietf@ietf.org by mistake.
> 
> If I was having a discussion with someone I am familiar with about
> another person's draft I might write "relatively harmless".  I have
> never sent a private message to an author saying "Yuck".  Please note
> that I am not saying that the word is inappropriate.
> 
> If there is a pattern of insulting (private) comments from a person(s)
> who speaks nicely in public, would the regular IETF participant be aware
> of that?  That is what I thought about when I responded to the "I trust
> that doesn't surprise anyone." written by John Klensin.

I really think most humans would be aware of that. I don't see
anything specific to the IETF in such inconsistency.

Regards
    Brian


From nobody Wed Feb 26 16:46: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 983911A07D5 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 16:46:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 PgYpMCQ69Gnb for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 16:46:02 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id C99731A0772 for <ietf@ietf.org>; Wed, 26 Feb 2014 16:46:02 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1R0jfdC026111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Feb 2014 16:45:52 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393461954; bh=uurcnJrxGw44PdVlah+PQ2wD9VViu1T3+Opa4G4UUPA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=KEaMGzm968UOsUx+LwM6RK5/mMb3NcHrQnZcTuc8TdDz+PjwXkYFFM3rK2AkwEkJL SfHct7hVjgYYVr9LK8eSXlvPX2mr0g3kJgXFzqNlOgDQ+w0oukiQxjg3cfWrYXChhr PKt7hNp0KqVa5CyS4InDXpl25kYy4ZjzIueQlvDM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393461954; i=@elandsys.com; bh=uurcnJrxGw44PdVlah+PQ2wD9VViu1T3+Opa4G4UUPA=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=oK7afxRulj5ElSgc6au126zuelNpdLDulYR5p7T4ZwwW8vPq0MqXkfpTo1LnnHvqZ hRYajnko7aIuaRG+gpnuNr5rta59LwTmW9eNt+n8wXOv3z/iBHXYAEmwOjgtTWUI07 SKWvEroAdFcdWxh2yqwuWbIMaQNvynA/xixKhzZU=
Message-Id: <6.2.5.6.2.20140226150129.0ccbe308@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 26 Feb 2014 15:07:40 -0800
To: Melinda Shore <melinda.shore@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
In-Reply-To: <CAKRbAfA3Jc3=Z3=Xpo4nCK371i+EodrBchwsB8BOz4JUP7RWVA@mail.g mail.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com> <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com> <CAKRbAfA3Jc3=Z3=Xpo4nCK371i+EodrBchwsB8BOz4JUP7RWVA@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/VHNKyIytmYOoac87gNb5dowS-K8
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, 27 Feb 2014 00:46:05 -0000

Hi Melinda,
At 14:51 26-02-2014, Melinda Shore wrote:
>I was apparently involved in this offline whatever and have 
>absolutely no idea what you're bothered by, or why.  More clarity 
>and less innuendo would be helpful.

In a message to Adrian Farrel and John Klensin I commented as follows:

   "I consider the matter as closed."

I am not bothered by that matter.  I am okay with you sharing the 
private message I wrote (Cc to melinda.shore@gmail.com) with 
ietf@ietf.org if that is helpful.

Regards,
S. Moonesamy  


From nobody Wed Feb 26 16:46:20 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 5C13B1A0772 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 16:46:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 BQjmadHtat14 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 16:46:04 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id CC37C1A074A for <ietf@ietf.org>; Wed, 26 Feb 2014 16:46:04 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.232.154]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1R0jfdE026111 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 26 Feb 2014 16:45:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393461959; bh=5pBgpNN7UaEQj9OsVvtpCPjWKbVZwjlht4oNNAop4M0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=QhRHCJZ90p4R1GX7MtESESmVmEHT/Svk8at4GCc97ckln93t1c1oiGY0Y1/PD5iBK 2egZBRGzxQV+YjepVyoFBZh7WJDphphvWJdNNKrwV+KX42Ssas+0KQPLaPsmwzlnfI w3eToPOt7GAyYpu6IKCZbAFqm8sTeoNS/PSoxZ8c=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393461959; i=@elandsys.com; bh=5pBgpNN7UaEQj9OsVvtpCPjWKbVZwjlht4oNNAop4M0=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=Yu8diJ54kagX7ggqXwzROqyl+/7Ztt3XBckeH5BVTapsYmdnqTjQPMGnPkXUt6XFi nStnqVNGA4kYoNk/XcEhwA06iST3NYomCq1D0AWeS5hHt4HtU+1+OLoQL0Eux6FOPe gFlTZEkz8aSovYowWiwB7IFCQaiNLP3CZpmtZKOg=
Message-Id: <6.2.5.6.2.20140226150759.0d030938@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 26 Feb 2014 16:37:04 -0800
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: A private club
In-Reply-To: <530E7196.60103@gmail.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com> <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com> <530E7196.60103@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/9EtD2VuQKf5PaQYZ65JeZa0KdqM
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, 27 Feb 2014 00:46:06 -0000

Hi Brian,
At 14:58 26-02-2014, Brian E Carpenter wrote:
>Sorry, I should have used the impersonal "one" instead of "you".
>I wasn't think about myself.

I did not find anything wrong or offensive, etc. in your previous 
message.  I explained why I used "you" as I could not find a way to 
express the idea in an the impersonal manner while trying to explain things.

>Indeed. Sarcasm is not a good tool for professional communication.
>Unfortunately, sometimes a perfectly serious remark is (mis)understood
>as sarcasm.

Ok.

>That's a real problem, but sometimes there is consensus in such a case,
>and sometimes there is resignation. It's a matter of judgment, and one tha
>a WG Chair has to make sometimes.

There can be resignation if there is a perception that the WG Chair 
has already made up his mind, e.g. the perception that the WG Chair 
is part of a private club.  It can affect future work and make it 
difficult for the group to reach agreement in future.

>You're talking about a barrier to understanding. That's not what
>I meant.

Ok.

Mikael Abrahamsson understood what I was trying to explain.  He said 
it better than I could.

Regards,
S. Moonesamy 


From nobody Wed Feb 26 18:03:26 2014
Return-Path: <barryleiba.mailing.lists@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 D35631A0683 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 18:03:13 -0800 (PST)
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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, 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 u7A0k6VvpfHG for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 18:03:12 -0800 (PST)
Received: from mail-vc0-x236.google.com (mail-vc0-x236.google.com [IPv6:2607:f8b0:400c:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id 8BC8D1A027B for <ietf@ietf.org>; Wed, 26 Feb 2014 18:03:12 -0800 (PST)
Received: by mail-vc0-f182.google.com with SMTP id id10so1878688vcb.27 for <ietf@ietf.org>; Wed, 26 Feb 2014 18:03:11 -0800 (PST)
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=vg7JPaP/yghBzV2ERCjQpCQZMGXsM9lU5M6UmqXvo7I=; b=LxivETk35NQ4lpEuq4c7NYit8T8abGaVFgPQx5FcagB70j8wQKqlKpLrIC5yzxSGeS Hg2V99ItS4hvYAoeiFFtC64/uLraFEAQzVCu8QimUw8e4veKeH1pm12o0TUZ3oIak8Ak ZFPwmhB+vXmkJGnhPF/r1pOKLIV0E3XiQuSJ5LtAff/fEUUlsPQADloGa+TCFP+GJxMr uDByzl+/IufOPS9fAYvmsOAqExsAb4dKZ8XmbH0/e6xtTJQJBWZGCHFhx3j3z2h8VpT7 uFTnwfX2291B5vNFsyHSSfSoYLkyDPmMz31mK7OqwJIsoPJ2WNc+QHbpunvNdcb/l5ih 4DXg==
MIME-Version: 1.0
X-Received: by 10.52.30.230 with SMTP id v6mr7103869vdh.6.1393466590944; Wed, 26 Feb 2014 18:03:10 -0800 (PST)
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.58.19.104 with HTTP; Wed, 26 Feb 2014 18:03:10 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com> <6.2.5.6.2.20140226111228.0e88f6c8@elandnews.com>
Date: Wed, 26 Feb 2014 18:03:10 -0800
X-Google-Sender-Auth: jouYoKFlglOhXqU3bJkaChWAHIw
Message-ID: <CAC4RtVDrqyASLaGqHCMHa_E1tczjypPa3DTkoj-Zenz9dE4Znw@mail.gmail.com>
Subject: Re: A private club
From: Barry Leiba <barryleiba@computer.org>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/TuKmgD7Udi8wwVNBBxzFFhFdE58
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: Thu, 27 Feb 2014 02:03:14 -0000

> If a person posts a comment and receives a sarcastic reply he or she will be
> uncomfortable to post more comments.  If a person sees "someone like
> him/her" receiving sarcastic replies the person will be uncomfortable to
> post a comment.

This is a really important point that merits highlighting, because we
(collectively, not present company in particular) *very* often don't
understand and take to heart.

If Joe Slobotnik gets nasty to Gar Farkle, because that's just what
those two do, and they're both experienced IETFers and "they can take
it", that might be fine for Joe and Gar.  But Abraham Wallflower, the
newbie who's trying to get up the courage to start speaking, might
well look at this and say, "Oh, MAN, I don't want to be treated like
THAT," and go away without every having contributed.

Even worse if Gar Farkle is a relative newbie who's gotten off on the
wrong foot with folks, and those folks feel free to treat him badly
because they think he's a pillock.  If, as SM says, Abe W sees Gar as
"someone like me", it makes it much worse, and then we find ourselves
driving people away... new, young people, many of whom may have good
ideas and be the future of our organization.

Really: let's be careful with that stuff.  I'd love to see us all
learn to treat each other with professional respect, regardless of
what we think of each other.

Barry


From nobody Wed Feb 26 18:16:16 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 E50851A0759 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 18:16:12 -0800 (PST)
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 usEvbU5Xom5v for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 18:16:09 -0800 (PST)
Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) by ietfa.amsl.com (Postfix) with ESMTP id 75BE51A0686 for <ietf@ietf.org>; Wed, 26 Feb 2014 18:16:09 -0800 (PST)
Received: by mail-la0-f41.google.com with SMTP id gl10so1262270lab.28 for <ietf@ietf.org>; Wed, 26 Feb 2014 18:16:07 -0800 (PST)
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=Z7qH6hvQQZ1XimrML3xWpfpamaeYsWUuQUqG3gGqqvE=; b=y46KekI6dinqQUTn1mNmOEA5aCBbkvV4QG4YlEM7zW+PiwcbcWw2Gg6jnW1pYIdAfA G0MgedXOafHF3SKP/0SbTVNGdKEaOusTMMpjtIDwPj7wk/lJIJn1hbxqsWyvCAFLwGSM 0keuj4CBx+LhMkJxKnyH+xfDoa4nfZ0/0+5uUcNpOoE8y+eHmp3ynf/4PQbHKt67cer3 53QEoHfiL/7r0nrRCHw1yKjK5AKRRl/VnBt5qMRlT8GTdL5OTEnQrP02S/UMuJSxY/o3 Q9u59NFpkCB5cSWQHFnGboYHs0sf2vZq6VWl0NPt5A1m7tnhKHZ9uJhMOSnOG++ShOHL 2w/g==
MIME-Version: 1.0
X-Received: by 10.112.170.199 with SMTP id ao7mr8975lbc.56.1393467367343; Wed, 26 Feb 2014 18:16:07 -0800 (PST)
Sender: christopher.morrow@gmail.com
Received: by 10.152.45.196 with HTTP; Wed, 26 Feb 2014 18:16:07 -0800 (PST)
In-Reply-To: <CAMm+Lwg12DZfWNdmqaRo=ha3g+5bPaMRaXd1BwUXbdSmwf3-uw@mail.gmail.com>
References: <CAMm+Lwg12DZfWNdmqaRo=ha3g+5bPaMRaXd1BwUXbdSmwf3-uw@mail.gmail.com>
Date: Wed, 26 Feb 2014 21:16:07 -0500
X-Google-Sender-Auth: CpuGtD6tPR3h4MHLeZernVOVhEo
Message-ID: <CAL9jLaa+NNy5ci+-QFPo-w6ODhBaPQj=11B2qRMyanxZ_TV75w@mail.gmail.com>
Subject: Re: Consequences of Snowdonia
From: Christopher Morrow <morrowc.lists@gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/VGD7nHCqqNx4hlf90Ft6_OnJ16E
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: Thu, 27 Feb 2014 02:16:13 -0000

On Wed, Feb 26, 2014 at 10:17 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> This is off topic but I know from sources that my posts here reach certain
> targets.

you're probably just trolling but...

> Fact: The Russian Army is mobilizing on the borders of Ukraine

this is akin to what happened in ~04 with Estonia/Talinin, almost?

> Fact: The Internet security community can't trust the NSA to coordinate the
> response because you betrayed us.

In which prior incident has anyone of consequence cared a whit about
what 'nsa' had to say or coordinate? (none, really, none)

> If there is an invasion it is very likely that the Russians will attempt a
> repeat of their tactic from the South Ossetia campaign and using BGP
> rerouting and Web site hijacking to issue bogus instructions purporting to

welp, I'm super glad we fixed bgp security and hijacking and
'mis-origination' ... wait. :(


From nobody Wed Feb 26 19:02:49 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 783791A0730 for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 19:02:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2OGUzAPACgQK for <ietf@ietfa.amsl.com>; Wed, 26 Feb 2014 19:02:45 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id DF7C11A071F for <ietf@ietf.org>; Wed, 26 Feb 2014 19:02:42 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E65C52CC5D; Thu, 27 Feb 2014 05:02:39 +0200 (EET)
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 vOW8a8u59p8d; Thu, 27 Feb 2014 05:02:39 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 370022CC48; Thu, 27 Feb 2014 05:02:39 +0200 (EET)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Consequences of Snowdonia
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <CAMm+Lwg12DZfWNdmqaRo=ha3g+5bPaMRaXd1BwUXbdSmwf3-uw@mail.gmail.com>
Date: Thu, 27 Feb 2014 03:02:38 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <4550452E-CEE2-4A9F-8DFE-75FDF2020B6C@piuha.net>
References: <CAMm+Lwg12DZfWNdmqaRo=ha3g+5bPaMRaXd1BwUXbdSmwf3-uw@mail.gmail.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jGiKVz9iVXc3zlYElkv5cP1IZj8
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: Thu, 27 Feb 2014 03:02:47 -0000

Phillip,

I'm not quite sure how this relates to what we as engineers need to do =
for networking. Can we avoid discussing specific conflicts?

(What tools we might develop to prevent routing hijacks etc. might be a =
more interesting and in-scope topic.)

Jari


From nobody Thu Feb 27 00:24:09 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 B255C1A002A for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 00:24:07 -0800 (PST)
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 RktWCcornwMY for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 00:24:05 -0800 (PST)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) by ietfa.amsl.com (Postfix) with ESMTP id B19E61A0045 for <ietf@ietf.org>; Thu, 27 Feb 2014 00:24:05 -0800 (PST)
Received: by mail-yh0-f53.google.com with SMTP id v1so2258253yhn.26 for <ietf@ietf.org>; Thu, 27 Feb 2014 00:24:04 -0800 (PST)
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=UJqBvTno/iDaHlGyohVYxMrNKzPBTLkUV4bQkMkzxo8=; b=KbyeAEvgBW2KE5UXb6xtc3dXLOv76sWZmh+gAU/lK+YYycCdm2r6Nz/UXXjx1RfEHR 3wCnJ/9KTnxWzdX0oEn1Q6DyDlRiim1p8y5TatqZEdDnEVgj0nRVYL6m8yFvheIWaJWu amCUmmva3eA4Ts9ULEtufXlzBA+XXYXbBWkBTRnTwOxkb+PdhtZtDWfG0FIqlmKvjY/B 7xWWGfaAgVqto6Zo8c2lKjUDJhZqgn/D7/M1o2SpypX0lsEtTdtDCEXN0Qe97EgTUBvi BwaeRUw6vtSaM30i+87g7cYxxx2KOS7bq2PUlQuilQT/xrlOzndvNzn3jR08cuxCe6YR 2hEQ==
MIME-Version: 1.0
X-Received: by 10.236.108.202 with SMTP id q50mr57279yhg.146.1393489444127; Thu, 27 Feb 2014 00:24:04 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Thu, 27 Feb 2014 00:24:04 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140226074723.0e37af20@elandnews.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com>
Date: Thu, 27 Feb 2014 09:24:04 +0100
Message-ID: <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com>
Subject: Re: Clarifying IETF process [Was: A private club]
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=20cf303b433d50c9b104f35f0b7c
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tt0f5hesGMM9hkPP0R7xemoBBa0
Cc: John C Klensin <john-ietf@jck.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "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, 27 Feb 2014 08:24:07 -0000

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

Hi Moonesamy,

You may close at you end but your input became an IETF input so I will not
close it because it is valid at my experience knowing about other
organisations. So I will answer my view to Adrian's question.

Clubing in private (i. e. closed from access) or hiding its powers should
be not allowed in any IETF processes. If you have a club just announce it.
I remember Adrian send a message saying that two ADs had same organisation
affiliation and that one should leave the IETF position which was excellent
process and proves high performance of IESG but what about WGs.

On the other hand, IMHO, Being social in IETF and creating social clubs is
not bad, but it should not influence IETF participants decisions, because
it is better that participants follow engineering logic/practice reasons
not following private/public clubs. Increasing Diversity into IETF is the
solution to avoid wrong clubings in IESG and IETF WGs (i. e. IETF's
main decision makings).

Please comment,

AB

Please note that my experience in IETF is two years remote participation,
two years monitoring without participation, and coming to the new meeting
to break the ice. The IETF has few private clubs very easily discovered
just by watching the lists, however, some participants still follow
engineering reasoning. I have experience with another volunteering
organisation (other than this IETF) for 2 years f2f participation and was a
council member to make decisions that guide that organisation output.



On Wednesday, February 26, 2014, S Moonesamy wrote:

> Hi Adrian, John,
> At 05:57 26-02-2014, Adrian Farrel wrote:
>
>> The point you make in your second paragraph is very valid, but it is hard
>> to
>> comment on your first paragraph without details.
>>
>> Would you care to phrase the issue succinctly so that a (moderately)
>> definitive
>> statement can be made?
>>
>
> I consider the matter as closed.
>
> At 05:59 26-02-2014, John C Klensin wrote:
>
> Please note that I did not ignore your message.  In my opinion the
> discussion would get out of hand.
>
> Regards,
> S. Moonesamy
>

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

Hi Moonesamy,<div><br></div><div>You may close at you end but your input be=
came an IETF input so I will not close it because it is valid at my experie=
nce knowing about=A0other organisations. So I will answer my view to Adrian=
&#39;s question.=A0</div>
<div><br></div><div>Clubing in private (i. e.=A0closed from=A0access)=A0or =
hiding its powers should be not allowed in any IETF processes. If you have =
a club just announce it. I remember Adrian send a message saying that two A=
Ds had same organisation affiliation and that one should leave the IETF pos=
ition which was excellent process and proves high performance of IESG but w=
hat about WGs.=A0</div>
<div><br></div><div>On the other hand, IMHO,=A0Being social in IETF and cre=
ating social clubs is not bad, but it should not influence IETF participant=
s=A0decisions, because it is better that participants follow engineering lo=
gic/practice reasons not following=A0private/public clubs. Increasing=A0Div=
ersity into IETF=A0is the solution to avoid wrong clubings in IESG and IETF=
 WGs (i. e. IETF&#39;s main=A0decision makings).=A0</div>
<div><br></div><div>Please comment,</div><div><br></div><div>AB</div><div><=
br></div><div>Please note that my experience in IETF is two years remote pa=
rticipation, two years monitoring without participation, and coming to the =
new meeting to break the ice. The IETF has few private clubs very easily di=
scovered just by watching the lists, however, some participants still follo=
w engineering reasoning. I have experience with another volunteering organi=
sation (other than this IETF)=A0for 2 years f2f participation and was=A0a c=
ouncil member to make decisions that guide that organisation output.=A0</di=
v>
<div><br></div><div>=A0<br><br>On Wednesday, February 26, 2014, S Moonesamy=
  wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">Hi Adrian, John,<br>
At 05:57 26-02-2014, Adrian Farrel wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
The point you make in your second paragraph is very valid, but it is hard t=
o<br>
comment on your first paragraph without details.<br>
<br>
Would you care to phrase the issue succinctly so that a (moderately) defini=
tive<br>
statement can be made?<br>
</blockquote>
<br>
I consider the matter as closed.<br>
<br>
At 05:59 26-02-2014, John C Klensin wrote:<br>
<br>
Please note that I did not ignore your message. =A0In my opinion the discus=
sion would get out of hand.<br>
<br>
Regards,<br>
S. Moonesamy <br>
</blockquote></div>

--20cf303b433d50c9b104f35f0b7c--


From nobody Thu Feb 27 00:45:40 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 3D79D1A00CF for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 00:45:39 -0800 (PST)
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 JOsX4pvHooll for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 00:45:36 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.162]) by ietfa.amsl.com (Postfix) with ESMTP id 2135C1A0075 for <ietf@ietf.org>; Thu, 27 Feb 2014 00:45:35 -0800 (PST)
Received: from [195.245.230.131:36667] by server-2.bemta-3.messagelabs.com id 73/34-06531-E2BFE035; Thu, 27 Feb 2014 08:45:34 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-15.tower-78.messagelabs.com!1393490733!28736308!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17440 invoked from network); 27 Feb 2014 08:45:33 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-15.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 27 Feb 2014 08:45:33 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Thu, 27 Feb 2014 08:45:32 +0000
From: <l.wood@surrey.ac.uk>
To: <ietf@ietf.org>
Date: Thu, 27 Feb 2014 08:43:05 +0000
Subject: RE: Clarifying IETF process [Was: A private club]
Thread-Topic: Clarifying IETF process [Was: A private club]
Thread-Index: Ac8zlWM7NG10aWebRIKEDq1wcyxG9QAAouQ6
Message-ID: <290E20B455C66743BE178C5C84F1240847E633473C@EXMB01CMS.surrey.ac.uk>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com>, <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com>
In-Reply-To: <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@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/obBb635LJOSVqWS1dubAuJjXG5A
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Feb 2014 08:45:39 -0000

> however, some participants still follow engineering reasoning

In the Internet ENGINEERING Task Force?

Imagine that.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Abdussalam Baryun [abdussal=
ambaryun@gmail.com]
Sent: 27 February 2014 08:24
To: S Moonesamy
Cc: John C Klensin; adrian@olddog.co.uk; ietf@ietf.org
Subject: Re: Clarifying IETF process [Was: A private club]

Hi Moonesamy,

You may close at you end but your input became an IETF input so I will not =
close it because it is valid at my experience knowing about other organisat=
ions. So I will answer my view to Adrian's question.

Clubing in private (i. e. closed from access) or hiding its powers should b=
e not allowed in any IETF processes. If you have a club just announce it. I=
 remember Adrian send a message saying that two ADs had same organisation a=
ffiliation and that one should leave the IETF position which was excellent =
process and proves high performance of IESG but what about WGs.

On the other hand, IMHO, Being social in IETF and creating social clubs is =
not bad, but it should not influence IETF participants decisions, because i=
t is better that participants follow engineering logic/practice reasons not=
 following private/public clubs. Increasing Diversity into IETF is the solu=
tion to avoid wrong clubings in IESG and IETF WGs (i. e. IETF's main decisi=
on makings).

Please comment,

AB

Please note that my experience in IETF is two years remote participation, t=
wo years monitoring without participation, and coming to the new meeting to=
 break the ice. The IETF has few private clubs very easily discovered just =
by watching the lists, however, some participants still follow engineering =
reasoning. I have experience with another volunteering organisation (other =
than this IETF) for 2 years f2f participation and was a council member to m=
ake decisions that guide that organisation output.



On Wednesday, February 26, 2014, S Moonesamy wrote:
Hi Adrian, John,
At 05:57 26-02-2014, Adrian Farrel wrote:
The point you make in your second paragraph is very valid, but it is hard t=
o
comment on your first paragraph without details.

Would you care to phrase the issue succinctly so that a (moderately) defini=
tive
statement can be made?

I consider the matter as closed.

At 05:59 26-02-2014, John C Klensin wrote:

Please note that I did not ignore your message.  In my opinion the discussi=
on would get out of hand.

Regards,
S. Moonesamy


From nobody Thu Feb 27 00:46:30 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 0F9D61A0773 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 00:46:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.322
X-Spam-Level: *
X-Spam-Status: No, score=1.322 tagged_above=-999 required=5 tests=[BAYES_50=0.8, 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 C6CMLAy8bKYX for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 00:46:28 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) by ietfa.amsl.com (Postfix) with ESMTP id 58EFA1A0075 for <ietf@ietf.org>; Thu, 27 Feb 2014 00:46:28 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id wn1so2079323obc.0 for <ietf@ietf.org>; Thu, 27 Feb 2014 00:46:26 -0800 (PST)
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=KAsvcL2LczJq8r2MeqVYH543KLtNgCRUqhZVOVoL020=; b=Qf2X7nj2BxH6IR1z5gb1O+516b8+lwG4GQH/vmzjOluxf2L8HQ9KAg0TecDomFsYwP O3HtzvLw0BoxRrNPCfYzi0lsbIDiyBf2THVB/0Kwb19RnJbFZegTpugNE5E/UP9xGvQT BfJsqcDlVoYJ4jlGbX9khDhvBN4DvyLftPV9Q=
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=KAsvcL2LczJq8r2MeqVYH543KLtNgCRUqhZVOVoL020=; b=bQWyG4MVoegMypnaFdSSnWwJ6hP+Rz2OHKc5BCHer94p2+JWpWqnJmWEQYy/moZLf9 5A2fCKNvVUjhT8uW5Euv6Di3rD08BkN3LK4nHfcPZCOSIFmTEuaZvtHUReKJNMoSje6H 9/a9I59ira0IomwiJUyVswLC2bOhYKU0OIWxO1PXja35mavtPDn638BbqRCDt69Reven 0QZ4/N73Q/+MAJ6GedHkcLVDQtIewNxXI+zyOOZ10tpPoPFwiLFOXRyMUiadtzUZG+Oo mX6ntnWhh5XH420/QlIYfWG4AYxIAKRtoAp1MIYsAOl4egguNsK7jssSewaKfRHGhfAe oEAQ==
X-Gm-Message-State: ALoCoQmL8ZGkECqLH46gjI4yNKeCtYRyRn/4ja17FJOWAkbRaEO/jR3NVHz4l8XTNQHmeNqioT5b
MIME-Version: 1.0
X-Received: by 10.60.63.11 with SMTP id c11mr116162oes.82.1393490786913; Thu, 27 Feb 2014 00:46:26 -0800 (PST)
Received: by 10.60.55.197 with HTTP; Thu, 27 Feb 2014 00:46:26 -0800 (PST)
In-Reply-To: <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com>
Date: Thu, 27 Feb 2014 08:46:26 +0000
Message-ID: <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com>
Subject: Re: Clarifying IETF process [Was: A private club]
From: Dave Cridland <dave@cridland.net>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c20c545a1fe504f35f5b3f
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/hMnFHbV3UQkTsfC3pqTP1X90dRQ
Cc: John C Klensin <john-ietf@jck.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, S Moonesamy <sm+ietf@elandsys.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, 27 Feb 2014 08:46:30 -0000

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

On 27 February 2014 08:24, Abdussalam Baryun <abdussalambaryun@gmail.com>wrote:

> On the other hand, IMHO, Being social in IETF and creating social clubs is
> not bad, but it should not influence IETF participants decisions, because
> it is better that participants follow engineering logic/practice reasons
> not following private/public clubs. Increasing Diversity into IETF is the
> solution to avoid wrong clubings in IESG and IETF WGs (i. e. IETF's
> main decision makings).
>
>
I think it's important to note that the IETF participants are human.

Humans work best together when there's a social, as well as professional,
element to their relationship. In fact, I'd argue that in terms of general
progress toward a sensible goal, the social element is more important - I'm
far more inclined to listen to a new idea with an open mind from someone I
like.

Forming social relationships between participants therefore does influence
participants decisions, and usually in a positive manner.

This idea that we should become emotionless robots making perfect logical
decisions seems sensible at first glance, but it's just not how groups of
people work.

As each person joins the group, the nature of the group changes in subtle
ways. The trick is to ensure those changes are both positive, and as small
as possible - then they'll be welcomed by the group as a whole.

I would, therefore, argue that the best way a new participant can gain
traction within a group is to be personable, and make a good first
impression. The best way we can be open to new participants is to welcome
them and give them the benefit of the doubt as they find their feet
socially.

The worst way a new participant can gain traction is to repeatedly appear
to claim they know what's wrong with the group, and cause friction. The
worst way to treat a newcomer is, of course, pretty obvious, but boils down
to the group avoiding even the slightest change.

As to diversity, let me really make myself unpopular.

I think that if we suddenly introduced large numbers of people from
different cultural backgrounds, the balance of the group as a whole would
shift so violently that all social cohesion would be lost, and the net
result would be a massive decrease in work output.

Instead we should tread carefully. I agree that ensuring maximal inclusion
is a good thing; lots of different cultural backgrounds will introduce new
ideas and concepts for the group to draw upon. But working slowly is going
to lead to a better result, not only for the "old guard", but for the
newcomers too.

Dave.

--001a11c20c545a1fe504f35f5b3f
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 2=
7 February 2014 08:24, Abdussalam Baryun <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:abdussalambaryun@gmail.com" target=3D"_blank">abdussalambaryun@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>On the other hand, IMHO,=A0Being social=
 in IETF and creating social clubs is not bad, but it should not influence =
IETF participants=A0decisions, because it is better that participants follo=
w engineering logic/practice reasons not following=A0private/public clubs. =
Increasing=A0Diversity into IETF=A0is the solution to avoid wrong clubings =
in IESG and IETF WGs (i. e. IETF&#39;s main=A0decision makings).=A0</div>

<div><br></div></blockquote><div><br></div><div>I think it&#39;s important =
to note that the IETF participants are human.</div><div><br></div><div>Huma=
ns work best together when there&#39;s a social, as well as professional, e=
lement to their relationship. In fact, I&#39;d argue that in terms of gener=
al progress toward a sensible goal, the social element is more important - =
I&#39;m far more inclined to listen to a new idea with an open mind from so=
meone I like.</div>
<div><br></div><div>Forming social relationships between participants there=
fore does influence participants decisions, and usually in a positive manne=
r.<br></div><div><br></div><div>This idea that we should become emotionless=
 robots making perfect logical decisions seems sensible at first glance, bu=
t it&#39;s just not how groups of people work.</div>
<div><br></div><div>As each person joins the group, the nature of the group=
 changes in subtle ways. The trick is to ensure those changes are both posi=
tive, and as small as possible - then they&#39;ll be welcomed by the group =
as a whole.</div>
<div><br></div><div>I would, therefore, argue that the best way a new parti=
cipant can gain traction within a group is to be personable, and make a goo=
d first impression. The best way we can be open to new participants is to w=
elcome them and give them the benefit of the doubt as they find their feet =
socially.</div>
<div><br></div><div>The worst way a new participant can gain traction is to=
 repeatedly appear to claim they know what&#39;s wrong with the group, and =
cause friction. The worst way to treat a newcomer is, of course, pretty obv=
ious, but boils down to the group avoiding even the slightest change.</div>
<div><br></div><div>As to diversity, let me really make myself unpopular.</=
div><div><br></div><div>I think that if we suddenly introduced large number=
s of people from different cultural backgrounds, the balance of the group a=
s a whole would shift so violently that all social cohesion would be lost, =
and the net result would be a massive decrease in work output.</div>
<div><br></div><div>Instead we should tread carefully. I agree that ensurin=
g maximal inclusion is a good thing; lots of different cultural backgrounds=
 will introduce new ideas and concepts for the group to draw upon. But work=
ing slowly is going to lead to a better result, not only for the &quot;old =
guard&quot;, but for the newcomers too.</div>
<div><br></div><div>Dave.</div></div></div></div>

--001a11c20c545a1fe504f35f5b3f--


From nobody Thu Feb 27 01:09:10 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 7C9451A003B for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 01:09:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.651
X-Spam-Level: 
X-Spam-Status: No, score=0.651 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, 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 6QpI1WjNhZ4Z for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 01:08:59 -0800 (PST)
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 638571A079C for <ietf@ietf.org>; Thu, 27 Feb 2014 01:08:57 -0800 (PST)
Received: by mail-oa0-f41.google.com with SMTP id o6so2175108oag.14 for <ietf@ietf.org>; Thu, 27 Feb 2014 01:08:55 -0800 (PST)
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=JRGZp/bJ1K1YCu7Ghug0QSgjwfuRQWLcR55VDqqrSJ0=; b=yg0G4JSTNOVfgLmXCxjCNpNdKWiiV7wtedML+DBDCBr67rSwOT3NmKnyABzy73AZNW 6QqWh0R9hhw/WDKzNOfwo87xysi3T8t/ZXpm1FASlsOBDd49uP8RmQKqMaBubiWrYSSR +tM26/tnB8DVrl8a9xwXADfNKgWnt725YaeY+J6VKtfs7mOqMPwtgrInJ9NJw5C3bmVF XkOOPRu4LyngjXG1VgBmAC45m3tb7ZoShlUa9IP2qAzSNdFBV9UXKYe7HTRBieZ+HlFm dTX7qcQC/UBNCqPnDLJJhsUJEjEEeW84ZfqJOtxdkzeXY2O+A18torZHgWPIMIa0a8ge V2vg==
MIME-Version: 1.0
X-Received: by 10.60.123.74 with SMTP id ly10mr10651109oeb.14.1393492135897; Thu, 27 Feb 2014 01:08:55 -0800 (PST)
Received: by 10.76.23.138 with HTTP; Thu, 27 Feb 2014 01:08:55 -0800 (PST)
In-Reply-To: <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com>
Date: Thu, 27 Feb 2014 04:08:55 -0500
Message-ID: <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com>
Subject: Re: Clarifying IETF process [Was: A private club]
From: Donald Eastlake <d3e3e3@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=047d7b5d42fcc1efe304f35fabac
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1SaLcAGlTvG2idkvEiJOS19iW2I
Cc: John C Klensin <john-ietf@jck.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>, S Moonesamy <sm+ietf@elandsys.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, 27 Feb 2014 09:09:01 -0000

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

See RFC 4144.

Donsld

On Thursday, February 27, 2014, Dave Cridland <dave@cridland.net> wrote:

> On 27 February 2014 08:24, Abdussalam Baryun <abdussalambaryun@gmail.com<javascript:_e(%7B%7D,'cvml','abdussalambaryun@gmail.com');>
> > wrote:
>
>> On the other hand, IMHO, Being social in IETF and creating social clubs
>> is not bad, but it should not influence IETF participants decisions,
>> because it is better that participants follow engineering logic/practice
>> reasons not following private/public clubs. Increasing Diversity into
>> IETF is the solution to avoid wrong clubings in IESG and IETF WGs (i. e.
>> IETF's main decision makings).
>>
>>
> I think it's important to note that the IETF participants are human.
>
> Humans work best together when there's a social, as well as professional,
> element to their relationship. In fact, I'd argue that in terms of general
> progress toward a sensible goal, the social element is more important - I'm
> far more inclined to listen to a new idea with an open mind from someone I
> like.
>
> Forming social relationships between participants therefore does influence
> participants decisions, and usually in a positive manner.
>
> This idea that we should become emotionless robots making perfect logical
> decisions seems sensible at first glance, but it's just not how groups of
> people work.
>
> As each person joins the group, the nature of the group changes in subtle
> ways. The trick is to ensure those changes are both positive, and as small
> as possible - then they'll be welcomed by the group as a whole.
>
> I would, therefore, argue that the best way a new participant can gain
> traction within a group is to be personable, and make a good first
> impression. The best way we can be open to new participants is to welcome
> them and give them the benefit of the doubt as they find their feet
> socially.
>
> The worst way a new participant can gain traction is to repeatedly appear
> to claim they know what's wrong with the group, and cause friction. The
> worst way to treat a newcomer is, of course, pretty obvious, but boils down
> to the group avoiding even the slightest change.
>
> As to diversity, let me really make myself unpopular.
>
> I think that if we suddenly introduced large numbers of people from
> different cultural backgrounds, the balance of the group as a whole would
> shift so violently that all social cohesion would be lost, and the net
> result would be a massive decrease in work output.
>
> Instead we should tread carefully. I agree that ensuring maximal inclusion
> is a good thing; lots of different cultural backgrounds will introduce new
> ideas and concepts for the group to draw upon. But working slowly is going
> to lead to a better result, not only for the "old guard", but for the
> newcomers too.
>
> Dave.
>


-- 
Sent from Gmail Mobile

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

See RFC 4144.<div><br></div><div>Donsld<span></span><br><br>On Thursday, Fe=
bruary 27, 2014, Dave Cridland &lt;<a href=3D"mailto:dave@cridland.net">dav=
e@cridland.net</a>&gt; wrote:<br><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">On 2=
7 February 2014 08:24, Abdussalam Baryun <span dir=3D"ltr">&lt;<a href=3D"j=
avascript:_e(%7B%7D,&#39;cvml&#39;,&#39;abdussalambaryun@gmail.com&#39;);" =
target=3D"_blank">abdussalambaryun@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>On the other hand, IMHO,=A0Being social=
 in IETF and creating social clubs is not bad, but it should not influence =
IETF participants=A0decisions, because it is better that participants follo=
w engineering logic/practice reasons not following=A0private/public clubs. =
Increasing=A0Diversity into IETF=A0is the solution to avoid wrong clubings =
in IESG and IETF WGs (i. e. IETF&#39;s main=A0decision makings).=A0</div>


<div><br></div></blockquote><div><br></div><div>I think it&#39;s important =
to note that the IETF participants are human.</div><div><br></div><div>Huma=
ns work best together when there&#39;s a social, as well as professional, e=
lement to their relationship. In fact, I&#39;d argue that in terms of gener=
al progress toward a sensible goal, the social element is more important - =
I&#39;m far more inclined to listen to a new idea with an open mind from so=
meone I like.</div>

<div><br></div><div>Forming social relationships between participants there=
fore does influence participants decisions, and usually in a positive manne=
r.<br></div><div><br></div><div>This idea that we should become emotionless=
 robots making perfect logical decisions seems sensible at first glance, bu=
t it&#39;s just not how groups of people work.</div>

<div><br></div><div>As each person joins the group, the nature of the group=
 changes in subtle ways. The trick is to ensure those changes are both posi=
tive, and as small as possible - then they&#39;ll be welcomed by the group =
as a whole.</div>

<div><br></div><div>I would, therefore, argue that the best way a new parti=
cipant can gain traction within a group is to be personable, and make a goo=
d first impression. The best way we can be open to new participants is to w=
elcome them and give them the benefit of the doubt as they find their feet =
socially.</div>

<div><br></div><div>The worst way a new participant can gain traction is to=
 repeatedly appear to claim they know what&#39;s wrong with the group, and =
cause friction. The worst way to treat a newcomer is, of course, pretty obv=
ious, but boils down to the group avoiding even the slightest change.</div>

<div><br></div><div>As to diversity, let me really make myself unpopular.</=
div><div><br></div><div>I think that if we suddenly introduced large number=
s of people from different cultural backgrounds, the balance of the group a=
s a whole would shift so violently that all social cohesion would be lost, =
and the net result would be a massive decrease in work output.</div>

<div><br></div><div>Instead we should tread carefully. I agree that ensurin=
g maximal inclusion is a good thing; lots of different cultural backgrounds=
 will introduce new ideas and concepts for the group to draw upon. But work=
ing slowly is going to lead to a better result, not only for the &quot;old =
guard&quot;, but for the newcomers too.</div>

<div><br></div><div>Dave.</div></div></div></div>
</blockquote></div><br><br>-- <br>Sent from Gmail Mobile<br>

--047d7b5d42fcc1efe304f35fabac--


From nobody Thu Feb 27 01:13:41 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 7EE0A1A0165 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 01:13:39 -0800 (PST)
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 LDJgyPEG7Zrm for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 01:13:37 -0800 (PST)
Received: from mail-yk0-x229.google.com (mail-yk0-x229.google.com [IPv6:2607:f8b0:4002:c07::229]) by ietfa.amsl.com (Postfix) with ESMTP id 518441A0103 for <ietf@ietf.org>; Thu, 27 Feb 2014 01:13:37 -0800 (PST)
Received: by mail-yk0-f169.google.com with SMTP id 142so5910856ykq.0 for <ietf@ietf.org>; Thu, 27 Feb 2014 01:13:35 -0800 (PST)
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; bh=hw7OEqxBIJYSbPJ0X8uKWEptTd/Mu6tvgb0pRnKVk2Q=; b=eM5Kzdpksomk1lcuTELmi6LZCHJk/r+oolHTKrdhmFtXWUoJYhkqrcUj3//zaQPfzL a4Tq/N5yvO2Ucp7khJPqPljMw/frnNbMPNMy/RIFJC83ZMGOiFPFt18dgE82DrVUeimr orVtrL+NLAX+H1gCvziKk29UkiXZRhUbh/iAQVs00UR7juoJU16e5cy9pgouFo2z075j YI6KXgk/03KydnadHslmz/8p2lFFj9jNnKh7vMdqE9+GDSBL/58jnRDGQ3iE/I52j3bw 5IJoEJ5bnBkCJSQerGdrgzDWlnciVCQCxlAUfypLCvJVFt8mK1eT0rbSlrrw2cyYLOev CWxg==
MIME-Version: 1.0
X-Received: by 10.236.129.198 with SMTP id h46mr13795019yhi.17.1393492415679;  Thu, 27 Feb 2014 01:13:35 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Thu, 27 Feb 2014 01:13:35 -0800 (PST)
In-Reply-To: <CADnDZ8_DBSAq4bwZnEPWOHcqrhFrCjburoBrotztoZxtcDegJg@mail.gmail.com>
References: <CADnDZ8_DBSAq4bwZnEPWOHcqrhFrCjburoBrotztoZxtcDegJg@mail.gmail.com>
Date: Thu, 27 Feb 2014 10:13:35 +0100
Message-ID: <CADnDZ8_zPsROqTdhr7UR63FcZZb67W2SeOrh72no5TPdBfOrpA@mail.gmail.com>
Subject: Re: Social activities under societies (was Re: anti-harassment procedures
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf300e4eed6f110904f35fbc31
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/3InOb8GkgzLvtAPgh37sqvW48G0
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Feb 2014 09:13:39 -0000

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

Social clubs solve many problem in IETF but it should not be private or
hidden if established or organised. Comments below,

On Saturday, February 22, 2014, Abdussalam Baryun wrote:

> Hi Keith
>
> My comments below,
>
> On Saturday, February 22, 2014, Keith Moore wrote:
>
>> On 02/21/2014 08:19 PM, Timothy B. Terriberry wrote:
>>
>>> In my view, a successful harassment policy needs to do two things:
>>> 1) Clearly establish what is unacceptable behavior.
>>> 2) Clearly indicate whom to go to for help.
>>>
>>> Section 4 satisfies (2) adequately. This statement, however, indicates
>>> that you are punting on (1).
>>>
>>
> IMHO the Requirement 1 is a must, to give good reasons for some penalties.
>
>
>> While I understand the desire to do (1), in my experience with discussing
>> harassment policies in other organizations it has been a rathole, or at
>> least a slippery slope.
>
>
> Yes, but only because societies still don't solve it when interacting with
> other cultures or minorities. Usually organisations should build a strong
> culture related to its vision and policies. In countries,
> organisations, universities, etc. they encourage establishing
> of clubs/societies to make people interact under social goals or
> activities (do we have social societies in IETF?) I think that is missing
> or I am not aware because was remotely working.
>

IETF has engineering reasoning goal in its decisions and it should not
allow any type of clubs that may try to influence decisions against IETF
visions.


>
> I know that there is a social event in meetings and hopefully will try to
> join if I get availability time in this meeting.
>
>
>> While it's not too hard to identify a few obviously harassing or abusive
>> behaviors, it can be very hard to draw a bright line between acceptable and
>> unacceptable behaviors in general.
>
>
> Yes it is very hard for engineers, so we need external advise which is
> very good for this best practice work.
>
>>
>

The IETF already is organised to guide its processes to the best of
its visions and goals, so if small clubs interfere that vision signal and
goal channel, then the IETF should guide those clubs socially.

AB

Please note that I have good experience in IETF for 2 years and am
reviewing many drafts of IETF. This note is important because there may
be few clubs in IETF that try to make my participation not valid as
influencing quality of interaction between remote and f2f participants.

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

Social clubs solve many problem in IETF but it should not be private or hid=
den if established or organised.=A0Comments below,<br><br>On Saturday, Febr=
uary 22, 2014, Abdussalam Baryun  wrote:<br><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Hi Keith</div><div><br></div><div>My comments below,</div><div><br></d=
iv>On Saturday, February 22, 2014, Keith Moore  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">

On 02/21/2014 08:19 PM, Timothy B. Terriberry wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
In my view, a successful harassment policy needs to do two things:<br>
1) Clearly establish what is unacceptable behavior.<br>
2) Clearly indicate whom to go to for help.<br>
<br>
Section 4 satisfies (2) adequately. This statement, however, indicates that=
 you are punting on (1).=A0<br>
</blockquote></blockquote><div><br></div><div>IMHO the=A0Requirement 1 is a=
 must, to give good reasons for some=A0penalties.=A0</div><div>=A0</div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex">


While I understand the desire to do (1), in my experience with discussing h=
arassment policies in other organizations it has been a rathole, or at leas=
t a slippery slope. =A0=A0</blockquote><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

</blockquote><div><br></div><div>Yes, but only because societies still don&=
#39;t solve it when interacting with other cultures=A0or minorities.=A0Usua=
lly organisations should build a strong culture related to its vision and=
=A0policies. In countries, organisations,=A0universities, etc. they encoura=
ge establishing of=A0clubs/societies to make people interact under social g=
oals or activities=A0(do we have social=A0societies in IETF?) I think that =
is missing or I am not aware because was remotely working.=A0</div>
</blockquote><div><br></div><div>IETF has engineering reasoning goal=A0in i=
ts decisions and it should not allow any type of=A0clubs that may try=A0to =
influence decisions against IETF visions.=A0</div><div>=A0=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">

<div><br></div><div>I know that there is a social event in meetings and hop=
efully will try to join if I get availability time in this meeting.=A0</div=
><div>=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">

While it&#39;s not too hard to identify a few obviously harassing or abusiv=
e behaviors, it can be very hard to draw a bright line between acceptable a=
nd unacceptable behaviors in general. =A0=A0</blockquote><div><br></div><di=
v>

Yes it is very hard for engineers, so we need external advise which is very=
 good for this best practice work.=A0=A0</div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"></blockquote>

<div>=A0</div></blockquote><div><br></div><div>The IETF already is organise=
d to guide its processes to the best of its=A0visions and goals, so if smal=
l clubs interfere that vision signal and goal channel, then the IETF should=
 guide those clubs socially.=A0</div>
<div><br></div><div>AB</div><div><br></div>Please note that I have good=A0e=
xperience in IETF for 2 years and am reviewing many drafts of IETF. This no=
te is important because there may be=A0few clubs=A0in IETF that try to make=
 my participation not valid as influencing quality of=A0interaction between=
 remote and f2f participants.=A0

--20cf300e4eed6f110904f35fbc31--


From nobody Thu Feb 27 02:17:09 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 701B51A0810 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 02:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.452
X-Spam-Level: 
X-Spam-Status: No, score=0.452 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, GB_FINANCIALPROBLEM=1, RP_MATCHES_RCVD=-0.547] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8eihO2sjVKI3 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 02:17:05 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id A5C5E1A07DE for <ietf@ietf.org>; Thu, 27 Feb 2014 02:17:04 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id C3A662CC61; Thu, 27 Feb 2014 12:17:01 +0200 (EET)
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 J5JJ7sY1MdER; Thu, 27 Feb 2014 12:17:01 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 17BBF2CC48; Thu, 27 Feb 2014 12:17:01 +0200 (EET)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: A private club
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <alpine.DEB.2.02.1402262021170.747@uplift.swm.pp.se>
Date: Thu, 27 Feb 2014 10:17:00 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D3E9285-3617-4B22-AE18-2A0790AB51C3@piuha.net>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net> <530E3B27.5030508@gmail.com> <alpine.DEB.2.02.1402262021170.747@uplift.swm.pp.se>
To: Mikael Abrahamsson <swmike@swm.pp.se>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/2kC7Tcih9JFVoTSeTaSCJENf0vw
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, 27 Feb 2014 10:17:07 -0000

>> I understand that it's hard for people to understand that there is no =
barrier to speech in the IETF and that there is no secret handshake.
>=20
> There are no *formal* barriers. I like that about the IETF, but I =
don't agree that there are no barriers.

Right. We are an open organisation, but it doesn't mean that =
participation is always easy and effortless, or even possible for =
everyone. That is of course a known problem, and we are doing several =
things to make it easier.

For instance, it is difficult to enter any new culture, but we try to =
educate & mentor newcomers.=20

Cost of attending is clearly a burden for many. ISOC has programs to =
financially help people who can not come to the meetings, and to =
actively pull people from, for instance, some regions of the world. =
Remote attendance has become easier as time goes by, which also helps =
with the financial problems and far-away participants.

The engineers are sometimes seen as working in their corner, not =
connecting to the rest of the world. But I think today many of us do try =
to reach the rest of the world.

I think our discussion culture is pretty hard [as these threads =
demonstrate I guess], although my observation is that we're improving =
and at least realising some of these issues. The culture does matter, =
and I think an environment with soft discussion culture tends to be not =
just more inviting but also produces better results. But we do have more =
work to do in this area. I think Lars' post on the types of arguments to =
avoid, perhaps made tongue-in-cheek, was actually spot on. It is up to =
all of us to improve the discussion culture. What can *I* or *you* do =
today to make an IETF discussion go smoother? (And of course, we can =
still disagree without being disagreeable=85)

And of course, everything is relative. I think IETF is relatively easy =
to access among different technical standards bodies, and definitely =
easier to access than, say, various processes involving per-country =
representation. But of course, I may just mix well with the engineers. =
And my definition of easy to access relates more to making an impact in =
whatever standard we are working on rather than just getting a seat at a =
table.

Jari


From nobody Thu Feb 27 02:56: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 A378B1A01F8 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 02:56:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 qDCKX1BkCFaZ for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 02:56:15 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7069B1A01CF for <ietf@ietf.org>; Thu, 27 Feb 2014 02:56:15 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.234.32]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1RAtqD7004871 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Feb 2014 02:56:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393498566; bh=OhbfeY/ArNYng0irbIfw/NOylndHus45vMXEU5J5HXk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VHNDXjF5/qD66hy2oc8Sn56EnPXnn35idpHWClrD1Qk24aS+49L8vQqufs9E6CaWK X4iGkIX1nf+PcyPQy8l+090jFx2hHXmUV20nBeVIwI0K1uiF0S8iiqUFU5K6zLsnMe mCfMXTeufREBFaYbCYelvvRsr9IFHRCwxrxjeyyI=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393498566; i=@elandsys.com; bh=OhbfeY/ArNYng0irbIfw/NOylndHus45vMXEU5J5HXk=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ht6tIcnluifT9fBg+F82M0IrRM+uST9m5cPXFafXmjVg+sc9HIFw6c7BX3WpQo49F JBhkCF8HSPXWnaMgSuU6EWG3RRThRa1jGyt4+jQzg1xEEiLSx6OguimWaba7MHbSdH 2u0CEndc/DwD6Pj8KZjgPnvwGQDNnaJLly9m2pe4=
Message-Id: <6.2.5.6.2.20140227021439.0bb5c600@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Feb 2014 02:53:55 -0800
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.g mail.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@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/6-aJlZoJlR9WKD3jdSVWPe3e7Fg
Cc: John C Klensin <john-ietf@jck.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Feb 2014 10:56:16 -0000

Hi Abdussalam,
At 00:24 27-02-2014, Abdussalam Baryun wrote:
>Clubing in private (i. e. closed from access) or hiding its powers 
>should be not allowed in any IETF processes. If you have a club just 
>announce it. I remember Adrian send a message saying that two ADs 
>had same organisation affiliation and that one should leave the IETF 
>position which was excellent process and proves high performance of 
>IESG but what about WGs.

I am one of the SPFBIS WG Chairs.  I don't work for the same company 
as the other WG co-Chair.  We don't have any clubs or organizations 
in common except the IETF.  I could not find anything else which 
might be a concern.

Regards,
S. Moonesamy 


From nobody Thu Feb 27 03:46:09 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 D61BA1A0264 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 03:46:07 -0800 (PST)
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, 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 1yXGidDnLfBY for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 03:46:05 -0800 (PST)
Received: from asmtp3.iomartmail.com (asmtp3.iomartmail.com [62.128.201.159]) by ietfa.amsl.com (Postfix) with ESMTP id 651EC1A0238 for <ietf@ietf.org>; Thu, 27 Feb 2014 03:46:05 -0800 (PST)
Received: from asmtp3.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1RBk1NT012758 for <ietf@ietf.org>; Thu, 27 Feb 2014 11:46:01 GMT
Received: from 950129200 (15.21.90.92.rev.sfr.net [92.90.21.15]) (authenticated bits=0) by asmtp3.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1RBjxR0012713 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <ietf@ietf.org>; Thu, 27 Feb 2014 11:46:00 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: <ietf@ietf.org>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <6.2.5.6.2.20140227021439.0bb5c600@elandnews.com>
In-Reply-To: <6.2.5.6.2.20140227021439.0bb5c600@elandnews.com>
Subject: RE: Clarifying IETF process [Was: A private club]
Date: Thu, 27 Feb 2014 11:45:58 -0000
Message-ID: <110a01cf33b1$7c769d50$7563d7f0$@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: AQKhPBDpdM0RT6g54LGywL/yr5b9WAG9w+32AYMO2SEB9CLOtZj7Qcgg
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/vZEzsefda0Yq1EbjXFytVsscsfI
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, 27 Feb 2014 11:46:08 -0000

At 00:24 27-02-2014, Abdussalam Baryun wrote:
>Clubing in private (i. e. closed from access) or hiding its powers
>should be not allowed in any IETF processes. If you have a club just
>announce it. I remember Adrian send a message saying that two ADs
>had same organisation affiliation and that one should leave the IETF
>position which was excellent process and proves high performance of
>IESG but what about WGs.

Hi,

For the avoidance of doubt, I did not say "one [of the Routing ADs] should leave
the IETF position"
I explained how the two Routing ADs would try to operate to avoid any issues of
bias (or seeming bias) caused by our shared affiliation.

Abdussalam might like to look through the WG chairs page at
http://datatracker.ietf.org/wg/ to see how many WGs are chaired by people with
the same affiliation. I think he will find it an exceptionally low number. The
situation arises from time to time when people change jobs, but ADs usually
attempt to avoid appointing into that position. If it was ever a problem, you
can be sure the community would be shouting about it.

Adrian


From nobody Thu Feb 27 03:47:03 2014
Return-Path: <mary.h.barnes@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 B520B1A066A for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 03:47:01 -0800 (PST)
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 HsL9BvGAf_nx for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 03:46:59 -0800 (PST)
Received: from mail-vc0-x233.google.com (mail-vc0-x233.google.com [IPv6:2607:f8b0:400c:c03::233]) by ietfa.amsl.com (Postfix) with ESMTP id 410F31A0239 for <ietf@ietf.org>; Thu, 27 Feb 2014 03:46:59 -0800 (PST)
Received: by mail-vc0-f179.google.com with SMTP id lh14so2357719vcb.38 for <ietf@ietf.org>; Thu, 27 Feb 2014 03:46:57 -0800 (PST)
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=aYnxCMoVGi4dWNwMZoA543Mku/T+6ShAnCN0VfQJ0wU=; b=KvGYlS9oo/u22NGwIL76hKibIYeh+h74Gx8tkQA3v4lDlxlroJnPobteXKKBOh3Py3 /KM8/TOlyFnA/6NxJgqfCxmBOhs87YLoN0ZoxWiSvkdb/Ep43ejhwopkMD9CF9JXDUQ/ jS63zGJahkGXn9PnFiO8AfxxEXwJq56ifAUgFXdfvKW8m2+5jjHyk+13LIaiBJ2WaJZQ YVacXq2FCljRrh90ylucxoTcOopyu+JO64ZAEtDGqfovbJzYcRb6U78H/WZKMGWdpOKX mXjsCOKyt4b29oZHEwPO40XtTiPiONrW7z3mwyZuTMYg73zdNw1ZXYVz9CABoJcszhjr 2SlA==
MIME-Version: 1.0
X-Received: by 10.220.95.139 with SMTP id d11mr10279972vcn.21.1393501617438; Thu, 27 Feb 2014 03:46:57 -0800 (PST)
Received: by 10.58.222.10 with HTTP; Thu, 27 Feb 2014 03:46:57 -0800 (PST)
In-Reply-To: <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com>
Date: Thu, 27 Feb 2014 05:46:57 -0600
Message-ID: <CABmDk8m1Qk=-63LZnUZEW5vwXOucj+5tTJJH=PfcFEqPttoB-g@mail.gmail.com>
Subject: Re: Clarifying IETF process [Was: A private club]
From: Mary Barnes <mary.h.barnes@gmail.com>
To: Dave Cridland <dave@cridland.net>
Content-Type: multipart/alternative; boundary=001a11c2ae76e6c34304f361e05d
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/QfaXfsAGg8C1OUFizFTU2CsHu6o
Cc: John C Klensin <john-ietf@jck.com>, "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "ietf@ietf.org" <ietf@ietf.org>, S Moonesamy <sm+ietf@elandsys.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, 27 Feb 2014 11:47:01 -0000

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

Dave,

Just one comment below [MB].

Mary.


On Thu, Feb 27, 2014 at 2:46 AM, Dave Cridland <dave@cridland.net> wrote:

> On 27 February 2014 08:24, Abdussalam Baryun <abdussalambaryun@gmail.com>wrote:
>
>> On the other hand, IMHO, Being social in IETF and creating social clubs
>> is not bad, but it should not influence IETF participants decisions,
>> because it is better that participants follow engineering logic/practice
>> reasons not following private/public clubs. Increasing Diversity into
>> IETF is the solution to avoid wrong clubings in IESG and IETF WGs (i. e.
>> IETF's main decision makings).
>>
>>
> I think it's important to note that the IETF participants are human.
>
> Humans work best together when there's a social, as well as professional,
> element to their relationship. In fact, I'd argue that in terms of general
> progress toward a sensible goal, the social element is more important - I'm
> far more inclined to listen to a new idea with an open mind from someone I
> like.
>
> Forming social relationships between participants therefore does influence
> participants decisions, and usually in a positive manner.
>
> This idea that we should become emotionless robots making perfect logical
> decisions seems sensible at first glance, but it's just not how groups of
> people work.
>
> As each person joins the group, the nature of the group changes in subtle
> ways. The trick is to ensure those changes are both positive, and as small
> as possible - then they'll be welcomed by the group as a whole.
>
> I would, therefore, argue that the best way a new participant can gain
> traction within a group is to be personable, and make a good first
> impression. The best way we can be open to new participants is to welcome
> them and give them the benefit of the doubt as they find their feet
> socially.
>
> The worst way a new participant can gain traction is to repeatedly appear
> to claim they know what's wrong with the group, and cause friction. The
> worst way to treat a newcomer is, of course, pretty obvious, but boils down
> to the group avoiding even the slightest change.
>
> As to diversity, let me really make myself unpopular.
>

> I think that if we suddenly introduced large numbers of people from
> different cultural backgrounds, the balance of the group as a whole would
> shift so violently that all social cohesion would be lost, and the net
> result would be a massive decrease in work output.
>
[MB] That's a very easy statement for someone who is in the majority
culturally and gender wise to make.   I certainly hope you are in the
majority.  My perspective would be that we might actually make better
progress with this "violent shift" that disrupts the current "social
cohesion" by bringing in new ideas and different, more effective ways of
working.  [/MB]

>
> Instead we should tread carefully. I agree that ensuring maximal inclusion
> is a good thing; lots of different cultural backgrounds will introduce new
> ideas and concepts for the group to draw upon. But working slowly is going
> to lead to a better result, not only for the "old guard", but for the
> newcomers too.
>
> Dave.
>

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

<div dir=3D"ltr">Dave,<div><br></div><div>Just one comment below [MB].=A0</=
div><div><br></div><div>Mary.=A0<br><div class=3D"gmail_extra"><br><br><div=
 class=3D"gmail_quote">On Thu, Feb 27, 2014 at 2:46 AM, Dave Cridland <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:dave@cridland.net" target=3D"_blank">dav=
e@cridland.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 dir=3D"ltr"><div class=3D"gmail_extra">=
<div class=3D"gmail_quote"><div class=3D"">On 27 February 2014 08:24, Abdus=
salam Baryun <span dir=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail=
.com" target=3D"_blank">abdussalambaryun@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>On the other hand, IMHO,=A0Being social=
 in IETF and creating social clubs is not bad, but it should not influence =
IETF participants=A0decisions, because it is better that participants follo=
w engineering logic/practice reasons not following=A0private/public clubs. =
Increasing=A0Diversity into IETF=A0is the solution to avoid wrong clubings =
in IESG and IETF WGs (i. e. IETF&#39;s main=A0decision makings).=A0</div>


<div><br></div></blockquote><div><br></div></div><div>I think it&#39;s impo=
rtant to note that the IETF participants are human.</div><div><br></div><di=
v>Humans work best together when there&#39;s a social, as well as professio=
nal, element to their relationship. In fact, I&#39;d argue that in terms of=
 general progress toward a sensible goal, the social element is more import=
ant - I&#39;m far more inclined to listen to a new idea with an open mind f=
rom someone I like.</div>

<div><br></div><div>Forming social relationships between participants there=
fore does influence participants decisions, and usually in a positive manne=
r.<br></div><div><br></div><div>This idea that we should become emotionless=
 robots making perfect logical decisions seems sensible at first glance, bu=
t it&#39;s just not how groups of people work.</div>

<div><br></div><div>As each person joins the group, the nature of the group=
 changes in subtle ways. The trick is to ensure those changes are both posi=
tive, and as small as possible - then they&#39;ll be welcomed by the group =
as a whole.</div>

<div><br></div><div>I would, therefore, argue that the best way a new parti=
cipant can gain traction within a group is to be personable, and make a goo=
d first impression. The best way we can be open to new participants is to w=
elcome them and give them the benefit of the doubt as they find their feet =
socially.</div>

<div><br></div><div>The worst way a new participant can gain traction is to=
 repeatedly appear to claim they know what&#39;s wrong with the group, and =
cause friction. The worst way to treat a newcomer is, of course, pretty obv=
ious, but boils down to the group avoiding even the slightest change.</div>

<div><br></div><div>As to diversity, let me really make myself unpopular.=
=A0</div></div></div></div></blockquote><blockquote class=3D"gmail_quote" s=
tyle=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>I=
 think that if we suddenly introduced large numbers of people from differen=
t cultural backgrounds, the balance of the group as a whole would shift so =
violently that all social cohesion would be lost, and the net result would =
be a massive decrease in work output.</div>
</div></div></div></blockquote><div>[MB] That&#39;s a very easy statement f=
or someone who is in the majority culturally and gender wise to make. =A0 I=
 certainly hope you are in the majority. =A0My perspective would be that we=
 might actually make better progress with this &quot;violent shift&quot; th=
at disrupts the current &quot;social cohesion&quot; by bringing in new idea=
s and different, more effective ways of working. =A0[/MB]</div>
<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><br></div><div>Instead we should tread carefully. I agree that ensurin=
g maximal inclusion is a good thing; lots of different cultural backgrounds=
 will introduce new ideas and concepts for the group to draw upon. But work=
ing slowly is going to lead to a better result, not only for the &quot;old =
guard&quot;, but for the newcomers too.</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></div>

--001a11c2ae76e6c34304f361e05d--


From nobody Thu Feb 27 03:52:01 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 22C5A1A025E; Thu, 27 Feb 2014 03:51:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.957
X-Spam-Level: 
X-Spam-Status: No, score=0.957 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.793, SPF_FAIL=0.001, TO_EQ_FM_DOM_SPF_FAIL=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 mVSw5h8RLuL4; Thu, 27 Feb 2014 03:51:55 -0800 (PST)
Received: from p130.piuha.net (unknown [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 578C81A018D; Thu, 27 Feb 2014 03:51:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E04052CC61; Thu, 27 Feb 2014 13:51:22 +0200 (EET)
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 PbTfE0Len3Nw; Thu, 27 Feb 2014 13:51:21 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 899AD2CC48; Thu, 27 Feb 2014 13:51:21 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Subject: conclusion on draft-farrell-perpass
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: IETF Chair <chair@ietf.org>
Date: Thu, 27 Feb 2014 11:51:21 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <9CC97547-2F05-44A0-A89C-E837BAA804B2@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/FVIqzg5li2V86KMOaEwp7rx0XAI
Cc: "ietf@ietf.org Mailing List" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: "ietf@ietf.org Mailing List" <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, 27 Feb 2014 11:51:58 -0000

The IESG has made a conclusion on draft-farrell-perpass [1]. This draft =
was extensively discussed during the last call and within the IESG. As =
you have seen, there has also been a number of document revisions and =
changes based on the discussion. The last version reflected changes that =
the IESG felt were necessary to move forward.=20

It has not been an easy to task to determine what the final outcome =
should be. The IESG took the approach that the document should reflect =
community opinion, not just our opinions, even if many of us had strong =
opinions on the topic. But even reflecting community opinion was not =
easy. I have over 700 e-mails on this topic, some of those e-mails focus =
on specific aspects, and the opinions and the draft changed as the =
discussion progressed [2]. Nevertheless, I want to thank everyone who =
has contributed on this topic. You really care about this topic, and =
making the right recommendations at the IETF. Thank you.

The IESG believed there eventually was consensus to publish the document =
and our main question was whether the document should proceed as =
initially planned (BCP) or whether it should be downgraded to =
Informational. After a discussion we have concluded that there is (very) =
rough consensus to publish the document as BCP. While there was clearly =
no full consensus, we believe that issues were discussed sufficiently to =
allow them to be addressed - even if no full agreement with the entire =
group could be reached.

There were three high-level concerns that I wanted to discuss in this =
e-mail:

1) Some forms of network management, traffic measurements, and similar =
important tasks might be affected by a broad definition of pervasive =
surveillance. We should obviously not make legitimate networking tasks =
harder, and that was not the intent of the document. In the last =
version, we believe that the the third last paragraph of Section 2 =
clarifies this sufficiently.

2) The document has too little specific guidance, making it difficult to =
follow it as a rule (if the document is a BCP) and is easily subject to =
mis- or over-application. The document is indeed thin on the specific =
guidance. Its primary message is to say that pervasive monitoring is yet =
another threat that we need to consider when working on Internet =
technology. This seems inline with RFC 2026 notion that BCPs can be =
"community's best current thinking on a statement of principle". Also, =
we see positive signs about many of those more specific details emerging =
in various documents.

3) The document, particularly as a BCP, could be used to block documents =
by ADs in an unreasonable fashion. There was considerable concern about =
this. However, the IESG process for document approval is most commonly =
not based on specific rules in existing RFCs, but rather specific =
technical concerns of the individual AD reviewers. ADs occasionally =
raise invalid issues on documents, and we expect (and get) pushback when =
that happens. I have certainly made mistakes when filing a Discuss. =
These are resolved through discussion. In more severe cases, we have =
override procedures, appeals, discussions with the Nomcom, and recall =
procedures to deal with these issues. In other words, if we start from =
the assumption of a misbehaving AD, no new documents are needed to file =
an inappropriate Discuss. Any AD can raise concerns about pervasive =
monitoring under the current Discuss criteria, and this document doesn't =
change that. We don't think this document will significantly change =
things for the worse. However, the IESG felt that there is an =
opportunity to clarify our procedures with regards to this specific =
case:

The IESG intends to make a change to its Discuss criteria statement [3]. =
While the general thrust of the statement already indicates that AD =
disagreement with informed WG consensus is a NOT an acceptable basis for =
a discuss, we wanted to say that more explicitly in the specific context =
of adequate consideration for pervasive monitoring issues. Section 3.2 =
of the Discuss criteria statement is about criteria that are not =
appropriate basis for a Discuss. We plan to say that while it is =
generally necessary that IETF work considers the impact of specific =
threats such as pervasive surveillance, informed and rational community =
decisions about the particular protocols and the possible need for =
mitigating mechanisms will be respected.

In addition, there were a number of other issues that were discussed. =
These included, for instance:

- Request to not support more encryption, and a point that surveillance =
can have good or useful motives. (Although there is little by way of =
solutions in the current draft, and previous RFCs have already talked at =
length about IETF position towards encryption.)

- Argument that the document will lead to one concern dominating others. =
(The draft says "... mitigate the technical aspects of PM, just as we do =
for protocol vulnerabilities in general")

- Architectural issues and separate legal/political remedies should be =
brought up. (They are now.)

- Whether to describe the issue as an attack or as indistinguishable =
from an attack. (Current text is the result of the discussion started by =
Stephen Kent.)

- The textual style of the document is that it reads as "too offended". =
(Some changes were done regarding this, but otherwise this comment was =
considered to be in the rough.)

- The document should include a checklist and more detailed actions. =
(See 2 above. Also, various documents under development are more likely =
to produce a more fine-grained guidance on specific issues.)

This e-mail is a report of the IESG's conclusion on the matter. I will =
proceed with the approval of the document in the next couple of days.

References:

[1] http://tools.ietf.org/html/draft-farrell-perpass-attack-06
[2] =
http://tools.ietf.org/rfcdiff?url1=3Ddraft-farrell-perpass-attack-02.txt&u=
rl2=3Ddraft-farrell-perpass-attack-06.txt
[3] https://www.ietf.org/iesg/statement/discuss-criteria.html

Jari Arkko for the IESG


From nobody Thu Feb 27 04:25:27 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 53D9D1A0068 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 04:25:25 -0800 (PST)
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_05=-0.5, 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 8cv7JyMmCAd6 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 04:25:23 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.145]) by ietfa.amsl.com (Postfix) with ESMTP id E4E2E1A0062 for <ietf@ietf.org>; Thu, 27 Feb 2014 04:25:22 -0800 (PST)
Received: from [85.158.136.51:57018] by server-9.bemta-5.messagelabs.com id 5A/65-11237-0BE2F035; Thu, 27 Feb 2014 12:25:20 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-9.tower-49.messagelabs.com!1393503920!20291641!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 19804 invoked from network); 27 Feb 2014 12:25:20 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-9.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 27 Feb 2014 12:25:20 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Thu, 27 Feb 2014 12:25:19 +0000
From: <l.wood@surrey.ac.uk>
To: <ietf@ietf.org>
Date: Thu, 27 Feb 2014 12:25:19 +0000
Subject: RE: Clarifying IETF process [Was: A private club]
Thread-Topic: Clarifying IETF process [Was: A private club]
Thread-Index: Ac8zlWM7NG10aWebRIKEDq1wcyxG9QAAouQ6AAeNKNc=
Message-ID: <290E20B455C66743BE178C5C84F1240847E633473D@EXMB01CMS.surrey.ac.uk>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com>, <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com>, <290E20B455C66743BE178C5C84F1240847E633473C@EXMB01CMS.surrey.ac.uk>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E633473C@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/6NVtq-SwHoPPnfwsEjAW6JA8vYA
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Feb 2014 12:25:25 -0000

> I have experience with another volunteering organisation (other than this=
 IETF) for 2 years f2f
> participation and was a council member to make decisions that guide that =
organisation output.

What output did the University of Glamorgan Union Cultural Societies Commit=
tee produce?

And what is its relevance to the technical decisions made in the IETF?

Lloyd Wood
http://about.me/lloydwood


From nobody Thu Feb 27 04:49:50 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 ACBEF1A000A for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 04:49:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b1hvWKnzweSS for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 04:49:47 -0800 (PST)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) by ietfa.amsl.com (Postfix) with ESMTP id A39CB1A0210 for <ietf@ietf.org>; Thu, 27 Feb 2014 04:49:46 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 3E93DBE74 for <ietf@ietf.org>; Thu, 27 Feb 2014 12:49:44 +0000 (GMT)
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 NpEqm8oyook7 for <ietf@ietf.org>; Thu, 27 Feb 2014 12:49:42 +0000 (GMT)
Received: from [10.2.3.4] (unknown [109.144.217.159]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 5EBE1BE70 for <ietf@ietf.org>; Thu, 27 Feb 2014 12:49:41 +0000 (GMT)
User-Agent: K-9 Mail for Android
In-Reply-To: <9CC97547-2F05-44A0-A89C-E837BAA804B2@ietf.org>
References: <9CC97547-2F05-44A0-A89C-E837BAA804B2@ietf.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8
Subject: Re: conclusion on draft-farrell-perpass
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Thu, 27 Feb 2014 12:49:37 +0000
To: ietf@ietf.org
Message-ID: <51a30d71-a9aa-4a46-b7fd-96f4715a7626@email.android.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zJ2QaKtRDxCLVuIwvnezm0oWHZU
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Feb 2014 12:49:49 -0000

Thank you!

Apologies for the hassle, I owe you beers:-)

But seriously, thanks for sponsoring this and doing such a thorough job.

S


On 27 February 2014 11:51:21 GMT+00:00, IETF Chair <chair@ietf.org> wrote:
>The IESG has made a conclusion on draft-farrell-perpass [1]. This draft
>was extensively discussed during the last call and within the IESG. As
>you have seen, there has also been a number of document revisions and
>changes based on the discussion. The last version reflected changes
>that the IESG felt were necessary to move forward. 
>
>It has not been an easy to task to determine what the final outcome
>should be. The IESG took the approach that the document should reflect
>community opinion, not just our opinions, even if many of us had strong
>opinions on the topic. But even reflecting community opinion was not
>easy. I have over 700 e-mails on this topic, some of those e-mails
>focus on specific aspects, and the opinions and the draft changed as
>the discussion progressed [2]. Nevertheless, I want to thank everyone
>who has contributed on this topic. You really care about this topic,
>and making the right recommendations at the IETF. Thank you.
>
>The IESG believed there eventually was consensus to publish the
>document and our main question was whether the document should proceed
>as initially planned (BCP) or whether it should be downgraded to
>Informational. After a discussion we have concluded that there is
>(very) rough consensus to publish the document as BCP. While there was
>clearly no full consensus, we believe that issues were discussed
>sufficiently to allow them to be addressed - even if no full agreement
>with the entire group could be reached.
>
>There were three high-level concerns that I wanted to discuss in this
>e-mail:
>
>1) Some forms of network management, traffic measurements, and similar
>important tasks might be affected by a broad definition of pervasive
>surveillance. We should obviously not make legitimate networking tasks
>harder, and that was not the intent of the document. In the last
>version, we believe that the the third last paragraph of Section 2
>clarifies this sufficiently.
>
>2) The document has too little specific guidance, making it difficult
>to follow it as a rule (if the document is a BCP) and is easily subject
>to mis- or over-application. The document is indeed thin on the
>specific guidance. Its primary message is to say that pervasive
>monitoring is yet another threat that we need to consider when working
>on Internet technology. This seems inline with RFC 2026 notion that
>BCPs can be "community's best current thinking on a statement of
>principle". Also, we see positive signs about many of those more
>specific details emerging in various documents.
>
>3) The document, particularly as a BCP, could be used to block
>documents by ADs in an unreasonable fashion. There was considerable
>concern about this. However, the IESG process for document approval is
>most commonly not based on specific rules in existing RFCs, but rather
>specific technical concerns of the individual AD reviewers. ADs
>occasionally raise invalid issues on documents, and we expect (and get)
>pushback when that happens. I have certainly made mistakes when filing
>a Discuss. These are resolved through discussion. In more severe cases,
>we have override procedures, appeals, discussions with the Nomcom, and
>recall procedures to deal with these issues. In other words, if we
>start from the assumption of a misbehaving AD, no new documents are
>needed to file an inappropriate Discuss. Any AD can raise concerns
>about pervasive monitoring under the current Discuss criteria, and this
>document doesn't change that. We don't think this document will
>significantly change things for the worse. However, the IESG felt that
>there is an opportunity to clarify our procedures with regards to this
>specific case:
>
>The IESG intends to make a change to its Discuss criteria statement
>[3]. While the general thrust of the statement already indicates that
>AD disagreement with informed WG consensus is a NOT an acceptable basis
>for a discuss, we wanted to say that more explicitly in the specific
>context of adequate consideration for pervasive monitoring issues.
>Section 3.2 of the Discuss criteria statement is about criteria that
>are not appropriate basis for a Discuss. We plan to say that while it
>is generally necessary that IETF work considers the impact of specific
>threats such as pervasive surveillance, informed and rational community
>decisions about the particular protocols and the possible need for
>mitigating mechanisms will be respected.
>
>In addition, there were a number of other issues that were discussed.
>These included, for instance:
>
>- Request to not support more encryption, and a point that surveillance
>can have good or useful motives. (Although there is little by way of
>solutions in the current draft, and previous RFCs have already talked
>at length about IETF position towards encryption.)
>
>- Argument that the document will lead to one concern dominating
>others. (The draft says "... mitigate the technical aspects of PM, just
>as we do for protocol vulnerabilities in general")
>
>- Architectural issues and separate legal/political remedies should be
>brought up. (They are now.)
>
>- Whether to describe the issue as an attack or as indistinguishable
>from an attack. (Current text is the result of the discussion started
>by Stephen Kent.)
>
>- The textual style of the document is that it reads as "too offended".
>(Some changes were done regarding this, but otherwise this comment was
>considered to be in the rough.)
>
>- The document should include a checklist and more detailed actions.
>(See 2 above. Also, various documents under development are more likely
>to produce a more fine-grained guidance on specific issues.)
>
>This e-mail is a report of the IESG's conclusion on the matter. I will
>proceed with the approval of the document in the next couple of days.
>
>References:
>
>[1] http://tools.ietf.org/html/draft-farrell-perpass-attack-06
>[2]
>http://tools.ietf.org/rfcdiff?url1=draft-farrell-perpass-attack-02.txt&url2=draft-farrell-perpass-attack-06.txt
>[3] https://www.ietf.org/iesg/statement/discuss-criteria.html
>
>Jari Arkko for the IESG



From nobody Thu Feb 27 05:22:02 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 3C7C61A02A2; Thu, 27 Feb 2014 05:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29d59xJFgY4i; Thu, 27 Feb 2014 05:22:00 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 73AFB1A021A; Thu, 27 Feb 2014 05:22:00 -0800 (PST)
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 1WJ0uT-0001ur-Eg; Thu, 27 Feb 2014 13:21:57 +0000
Date: Thu, 27 Feb 2014 13:21:56 +0000
Message-ID: <m2d2i8itcb.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Chair <chair@ietf.org>
Subject: Re: conclusion on draft-farrell-perpass
In-Reply-To: <9CC97547-2F05-44A0-A89C-E837BAA804B2@ietf.org>
References: <9CC97547-2F05-44A0-A89C-E837BAA804B2@ietf.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/xaNlguHjc-yVAjHRCETsxyBQFfc
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: Thu, 27 Feb 2014 13:22:01 -0000

thank you.  this is important.

randy


From nobody Thu Feb 27 05:50:33 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 CCD501A028D for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 05:50:30 -0800 (PST)
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=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 Jhb3SiwI6LAK for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 05:50:27 -0800 (PST)
Received: from mail-vc0-f178.google.com (mail-vc0-f178.google.com [209.85.220.178]) by ietfa.amsl.com (Postfix) with ESMTP id 5E5CF1A021F for <ietf@ietf.org>; Thu, 27 Feb 2014 05:50:27 -0800 (PST)
Received: by mail-vc0-f178.google.com with SMTP id ik5so2543030vcb.9 for <ietf@ietf.org>; Thu, 27 Feb 2014 05:50:25 -0800 (PST)
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=LIsJVPTQO95eGfmYNAaitJ/SYvZHb72zlqL8QGqNpuk=; b=d4mQjrYwo65NBJMR4ljPMWmtQ061FW6We0Cc9noo1F4RfNx56wv0sF52Z1dmpj3OgI r9dWnEVplgyLSMpSFFnhhNxPMbP/ARmKhJs9Xz7r974JJzTP3opjPUBK6WplDT7c8KVQ FaIaM0I1b3PzMsbASkCWmiXpTmBN8GQRsUgBL39t59W8dI0gJVLa/aIpSySkwbHR7NN3 lbmlIqE4GXIlDdaEKPNOMXzuSTjJBz2jD2HXmtqkjrm6ofH/j9P1uu+oBMFV3T1kAUuk Qyf2WJlVN52AZ/fFr/uKbJop7zCrv0RUyKgaqg06cKaYEctWRWsnEWT651VZ71KOUyCn GV1g==
X-Gm-Message-State: ALoCoQlJv41KN/E8hhWO5mOAo2EM6PVcur7VvnrrqtSl4E9p8s4mc77Q4uWbrMi6pN2emde8nreC
MIME-Version: 1.0
X-Received: by 10.52.89.230 with SMTP id br6mr9325269vdb.20.1393509025589; Thu, 27 Feb 2014 05:50:25 -0800 (PST)
Received: by 10.220.98.73 with HTTP; Thu, 27 Feb 2014 05:50:25 -0800 (PST)
X-Originating-IP: [149.7.216.40]
Received: by 10.220.98.73 with HTTP; Thu, 27 Feb 2014 05:50:25 -0800 (PST)
In-Reply-To: <9CC97547-2F05-44A0-A89C-E837BAA804B2@ietf.org>
References: <9CC97547-2F05-44A0-A89C-E837BAA804B2@ietf.org>
Date: Thu, 27 Feb 2014 05:50:25 -0800
Message-ID: <CAHBU6ivumEy4YQus-4eJxHn1WqLQEZ7uec8TZ4Yy4q-t36jC9A@mail.gmail.com>
Subject: Re: conclusion on draft-farrell-perpass
From: Tim Bray <tbray@textuality.com>
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary=20cf307f376676491404f3639acb
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/tuWw20t9zfUPOx5ja3KrAPZhTAw
Cc: 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: Thu, 27 Feb 2014 13:50:31 -0000

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

Well done.
On Feb 27, 2014 12:52 PM, "IETF Chair" <chair@ietf.org> wrote:

> The IESG has made a conclusion on draft-farrell-perpass [1]. This draft
> was extensively discussed during the last call and within the IESG. As you
> have seen, there has also been a number of document revisions and changes
> based on the discussion. The last version reflected changes that the IESG
> felt were necessary to move forward.
>
> It has not been an easy to task to determine what the final outcome should
> be. The IESG took the approach that the document should reflect community
> opinion, not just our opinions, even if many of us had strong opinions on
> the topic. But even reflecting community opinion was not easy. I have over
> 700 e-mails on this topic, some of those e-mails focus on specific aspects,
> and the opinions and the draft changed as the discussion progressed [2].
> Nevertheless, I want to thank everyone who has contributed on this topic.
> You really care about this topic, and making the right recommendations at
> the IETF. Thank you.
>
> The IESG believed there eventually was consensus to publish the document
> and our main question was whether the document should proceed as initially
> planned (BCP) or whether it should be downgraded to Informational. After a
> discussion we have concluded that there is (very) rough consensus to
> publish the document as BCP. While there was clearly no full consensus, we
> believe that issues were discussed sufficiently to allow them to be
> addressed - even if no full agreement with the entire group could be
> reached.
>
> There were three high-level concerns that I wanted to discuss in this
> e-mail:
>
> 1) Some forms of network management, traffic measurements, and similar
> important tasks might be affected by a broad definition of pervasive
> surveillance. We should obviously not make legitimate networking tasks
> harder, and that was not the intent of the document. In the last version,
> we believe that the the third last paragraph of Section 2 clarifies this
> sufficiently.
>
> 2) The document has too little specific guidance, making it difficult to
> follow it as a rule (if the document is a BCP) and is easily subject to
> mis- or over-application. The document is indeed thin on the specific
> guidance. Its primary message is to say that pervasive monitoring is yet
> another threat that we need to consider when working on Internet
> technology. This seems inline with RFC 2026 notion that BCPs can be
> "community's best current thinking on a statement of principle". Also, we
> see positive signs about many of those more specific details emerging in
> various documents.
>
> 3) The document, particularly as a BCP, could be used to block documents
> by ADs in an unreasonable fashion. There was considerable concern about
> this. However, the IESG process for document approval is most commonly not
> based on specific rules in existing RFCs, but rather specific technical
> concerns of the individual AD reviewers. ADs occasionally raise invalid
> issues on documents, and we expect (and get) pushback when that happens. I
> have certainly made mistakes when filing a Discuss. These are resolved
> through discussion. In more severe cases, we have override procedures,
> appeals, discussions with the Nomcom, and recall procedures to deal with
> these issues. In other words, if we start from the assumption of a
> misbehaving AD, no new documents are needed to file an inappropriate
> Discuss. Any AD can raise concerns about pervasive monitoring under the
> current Discuss criteria, and this document doesn't change that. We don't
> think this document will significantly change things for the worse.
> However, the IESG felt that there is an opportunity to clarify our
> procedures with regards to this specific case:
>
> The IESG intends to make a change to its Discuss criteria statement [3].
> While the general thrust of the statement already indicates that AD
> disagreement with informed WG consensus is a NOT an acceptable basis for a
> discuss, we wanted to say that more explicitly in the specific context of
> adequate consideration for pervasive monitoring issues. Section 3.2 of the
> Discuss criteria statement is about criteria that are not appropriate basis
> for a Discuss. We plan to say that while it is generally necessary that
> IETF work considers the impact of specific threats such as pervasive
> surveillance, informed and rational community decisions about the
> particular protocols and the possible need for mitigating mechanisms will
> be respected.
>
> In addition, there were a number of other issues that were discussed.
> These included, for instance:
>
> - Request to not support more encryption, and a point that surveillance
> can have good or useful motives. (Although there is little by way of
> solutions in the current draft, and previous RFCs have already talked at
> length about IETF position towards encryption.)
>
> - Argument that the document will lead to one concern dominating others.
> (The draft says "... mitigate the technical aspects of PM, just as we do
> for protocol vulnerabilities in general")
>
> - Architectural issues and separate legal/political remedies should be
> brought up. (They are now.)
>
> - Whether to describe the issue as an attack or as indistinguishable from
> an attack. (Current text is the result of the discussion started by Stephen
> Kent.)
>
> - The textual style of the document is that it reads as "too offended".
> (Some changes were done regarding this, but otherwise this comment was
> considered to be in the rough.)
>
> - The document should include a checklist and more detailed actions. (See
> 2 above. Also, various documents under development are more likely to
> produce a more fine-grained guidance on specific issues.)
>
> This e-mail is a report of the IESG's conclusion on the matter. I will
> proceed with the approval of the document in the next couple of days.
>
> References:
>
> [1] http://tools.ietf.org/html/draft-farrell-perpass-attack-06
> [2]
> http://tools.ietf.org/rfcdiff?url1=draft-farrell-perpass-attack-02.txt&url2=draft-farrell-perpass-attack-06.txt
> [3] https://www.ietf.org/iesg/statement/discuss-criteria.html
>
> Jari Arkko for the IESG
>
>

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

<p dir=3D"ltr">Well done.</p>
<div class=3D"gmail_quote">On Feb 27, 2014 12:52 PM, &quot;IETF Chair&quot;=
 &lt;<a href=3D"mailto:chair@ietf.org">chair@ietf.org</a>&gt; wrote:<br typ=
e=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
The IESG has made a conclusion on draft-farrell-perpass [1]. This draft was=
 extensively discussed during the last call and within the IESG. As you hav=
e seen, there has also been a number of document revisions and changes base=
d on the discussion. The last version reflected changes that the IESG felt =
were necessary to move forward.<br>

<br>
It has not been an easy to task to determine what the final outcome should =
be. The IESG took the approach that the document should reflect community o=
pinion, not just our opinions, even if many of us had strong opinions on th=
e topic. But even reflecting community opinion was not easy. I have over 70=
0 e-mails on this topic, some of those e-mails focus on specific aspects, a=
nd the opinions and the draft changed as the discussion progressed [2]. Nev=
ertheless, I want to thank everyone who has contributed on this topic. You =
really care about this topic, and making the right recommendations at the I=
ETF. Thank you.<br>

<br>
The IESG believed there eventually was consensus to publish the document an=
d our main question was whether the document should proceed as initially pl=
anned (BCP) or whether it should be downgraded to Informational. After a di=
scussion we have concluded that there is (very) rough consensus to publish =
the document as BCP. While there was clearly no full consensus, we believe =
that issues were discussed sufficiently to allow them to be addressed - eve=
n if no full agreement with the entire group could be reached.<br>

<br>
There were three high-level concerns that I wanted to discuss in this e-mai=
l:<br>
<br>
1) Some forms of network management, traffic measurements, and similar impo=
rtant tasks might be affected by a broad definition of pervasive surveillan=
ce. We should obviously not make legitimate networking tasks harder, and th=
at was not the intent of the document. In the last version, we believe that=
 the the third last paragraph of Section 2 clarifies this sufficiently.<br>

<br>
2) The document has too little specific guidance, making it difficult to fo=
llow it as a rule (if the document is a BCP) and is easily subject to mis- =
or over-application. The document is indeed thin on the specific guidance. =
Its primary message is to say that pervasive monitoring is yet another thre=
at that we need to consider when working on Internet technology. This seems=
 inline with RFC 2026 notion that BCPs can be &quot;community&#39;s best cu=
rrent thinking on a statement of principle&quot;. Also, we see positive sig=
ns about many of those more specific details emerging in various documents.=
<br>

<br>
3) The document, particularly as a BCP, could be used to block documents by=
 ADs in an unreasonable fashion. There was considerable concern about this.=
 However, the IESG process for document approval is most commonly not based=
 on specific rules in existing RFCs, but rather specific technical concerns=
 of the individual AD reviewers. ADs occasionally raise invalid issues on d=
ocuments, and we expect (and get) pushback when that happens. I have certai=
nly made mistakes when filing a Discuss. These are resolved through discuss=
ion. In more severe cases, we have override procedures, appeals, discussion=
s with the Nomcom, and recall procedures to deal with these issues. In othe=
r words, if we start from the assumption of a misbehaving AD, no new docume=
nts are needed to file an inappropriate Discuss. Any AD can raise concerns =
about pervasive monitoring under the current Discuss criteria, and this doc=
ument doesn&#39;t change that. We don&#39;t think this document will signif=
icantly change things for the worse. However, the IESG felt that there is a=
n opportunity to clarify our procedures with regards to this specific case:=
<br>

<br>
The IESG intends to make a change to its Discuss criteria statement [3]. Wh=
ile the general thrust of the statement already indicates that AD disagreem=
ent with informed WG consensus is a NOT an acceptable basis for a discuss, =
we wanted to say that more explicitly in the specific context of adequate c=
onsideration for pervasive monitoring issues. Section 3.2 of the Discuss cr=
iteria statement is about criteria that are not appropriate basis for a Dis=
cuss. We plan to say that while it is generally necessary that IETF work co=
nsiders the impact of specific threats such as pervasive surveillance, info=
rmed and rational community decisions about the particular protocols and th=
e possible need for mitigating mechanisms will be respected.<br>

<br>
In addition, there were a number of other issues that were discussed. These=
 included, for instance:<br>
<br>
- Request to not support more encryption, and a point that surveillance can=
 have good or useful motives. (Although there is little by way of solutions=
 in the current draft, and previous RFCs have already talked at length abou=
t IETF position towards encryption.)<br>

<br>
- Argument that the document will lead to one concern dominating others. (T=
he draft says &quot;... mitigate the technical aspects of PM, just as we do=
 for protocol vulnerabilities in general&quot;)<br>
<br>
- Architectural issues and separate legal/political remedies should be brou=
ght up. (They are now.)<br>
<br>
- Whether to describe the issue as an attack or as indistinguishable from a=
n attack. (Current text is the result of the discussion started by Stephen =
Kent.)<br>
<br>
- The textual style of the document is that it reads as &quot;too offended&=
quot;. (Some changes were done regarding this, but otherwise this comment w=
as considered to be in the rough.)<br>
<br>
- The document should include a checklist and more detailed actions. (See 2=
 above. Also, various documents under development are more likely to produc=
e a more fine-grained guidance on specific issues.)<br>
<br>
This e-mail is a report of the IESG&#39;s conclusion on the matter. I will =
proceed with the approval of the document in the next couple of days.<br>
<br>
References:<br>
<br>
[1] <a href=3D"http://tools.ietf.org/html/draft-farrell-perpass-attack-06" =
target=3D"_blank">http://tools.ietf.org/html/draft-farrell-perpass-attack-0=
6</a><br>
[2] <a href=3D"http://tools.ietf.org/rfcdiff?url1=3Ddraft-farrell-perpass-a=
ttack-02.txt&amp;url2=3Ddraft-farrell-perpass-attack-06.txt" target=3D"_bla=
nk">http://tools.ietf.org/rfcdiff?url1=3Ddraft-farrell-perpass-attack-02.tx=
t&amp;url2=3Ddraft-farrell-perpass-attack-06.txt</a><br>

[3] <a href=3D"https://www.ietf.org/iesg/statement/discuss-criteria.html" t=
arget=3D"_blank">https://www.ietf.org/iesg/statement/discuss-criteria.html<=
/a><br>
<br>
Jari Arkko for the IESG<br>
<br>
</blockquote></div>

--20cf307f376676491404f3639acb--


From nobody Thu Feb 27 06:58:03 2014
Return-Path: <john@jlc.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 190CF1A02DD for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 06:58:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.848
X-Spam-Level: 
X-Spam-Status: No, score=-2.848 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2V5lpkC2gIT7 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 06:57:59 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 090F81A020D for <ietf@ietf.org>; Thu, 27 Feb 2014 06:57:59 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id F0856C94E6; Thu, 27 Feb 2014 09:57:55 -0500 (EST)
Date: Thu, 27 Feb 2014 09:57:55 -0500
From: John Leslie <john@jlc.net>
To: Donald Eastlake <d3e3e3@gmail.com>
Subject: Re: Clarifying IETF process [Was: A private club]
Message-ID: <20140227145755.GY54716@verdi>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com>
User-Agent: Mutt/1.4.1i
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Svsm3jh7C6yCN8kOpo8w22qw4Rg
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, 27 Feb 2014 14:58:01 -0000

Donald Eastlake <d3e3e3@gmail.com> wrote:
> 
> See RFC 4144.
] 
]...
] 3.  Eighty Percent of Success is Showing Up
] 
]  It is the simplest thing! If you are absent, how can you have much
]  prominence or influence?
] 
]  This applies to all venues, email/messaging, telephone/video
]  conference, and especially in-person or face-to-face meetings.  You
]  do not need 100% attendance, but your absences should be rare.  If
]  possible, only miss less important events.

   Generally good advice...

   But many of us cannot afford the cost of three IETF weeks before we
see some return. (Especially those who need their employer to subsidize
three weeks of their time as well as the travel costs...)

   We cannot reasonably hope to change human nature -- least of all by
writing one RFC -- but surely we can do something to ameliorate this
economic disincentive?

--
John Leslie <john@jlc.net>


From nobody Thu Feb 27 07:42:49 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 89AB41A0300 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 07:42:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.962
X-Spam-Level: 
X-Spam-Status: No, score=0.962 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, J_CHICKENPOX_35=0.6, RP_MATCHES_RCVD=-0.547, 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 zaWJNhRbgM1X for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 07:42:46 -0800 (PST)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 179221A010C for <ietf@ietf.org>; Thu, 27 Feb 2014 07:42:45 -0800 (PST)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WJ36h-0008Lq-2h; Thu, 27 Feb 2014 15:42:43 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 876E5580249; Thu, 27 Feb 2014 10:42:41 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1393515761; bh=jz4EqG7zPreZq/vvlKemHKlwZsLWuVC9lOLkSt0nWcA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=SieQdGpEFyQd/NHRZqW7HXMVk0llxGY7wM/TiwNMGI1TVWVJ8VA/Ug8mKQQmYYULY WBwoykyNwal1vbiXj9o2Bz3opcaMutPiZz1c2nGd4fPweMSU1oEMxXtZYx9+MxGSQ8 QrAJYI1aMhraQqcCTrliY/Uga2u9gcJb+tgn1E5Q=
Date: Thu, 27 Feb 2014 10:42:41 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: John Leslie <john@jlc.net>
Subject: Re: Clarifying IETF process [Was: A private club]
Message-ID: <20140227154241.GB7982@thunk.org>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140227145755.GY54716@verdi>
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/7Ah9ESI_lBI6LUjQN7ELwC9O9gU
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, 27 Feb 2014 15:42:47 -0000

On Thu, Feb 27, 2014 at 09:57:55AM -0500, John Leslie wrote:
> Donald Eastlake <d3e3e3@gmail.com> wrote:
> > 
> ] 3.  Eighty Percent of Success is Showing Up
> ] 
> ]  It is the simplest thing! If you are absent, how can you have much
> ]  prominence or influence?
> ] 
> ]  This applies to all venues, email/messaging, telephone/video
> ]  conference, and especially in-person or face-to-face meetings.  You
> ]  do not need 100% attendance, but your absences should be rare.  If
> ]  possible, only miss less important events.
> 
>    Generally good advice...
> 
>    But many of us cannot afford the cost of three IETF weeks before we
> see some return. (Especially those who need their employer to subsidize
> three weeks of their time as well as the travel costs...)
> 
>    We cannot reasonably hope to change human nature -- least of all by
> writing one RFC -- but surely we can do something to ameliorate this
> economic disincentive?

I've always thought this is a feature, but a bug.  The reality is that
there are a huge numbers of net.kooks out there.  It may be
politically incorrect to say that, but it's true.  So if you are
trying to pariticpate remotely, it's possible, but you have to be
really, really good with your technical presentations, your evidence,
with sample implementations, perhaps a huge installed base, etc.

(And funny that, if you have all of this, it's likely that some
company will be quite willing to fund you to show up to an IETF
meeting.)

Other standards committees have other ways of filtering out kooks.  In
the ISO world, your company needs to pay $$$ to become a member of
some organization like ANSI or INCITES, or you have to get the US
State Department, or the equivalent in your company, to give you
accreditation.  The fact that the IETF allows participation by
technically minded people trying to participate remotely, and
hopefully pursuade some number of people who *do* have funding to
attend in person to help champion your cause, makes it actually far
more open than many other standards organizations that I've had the
opportunity to work in.

For example, I was once involved in a ISO-related standards activity
where there was active plotting[1] to hold a series in-person meetings
in far-off countries in Asia specifically because there was a known
kook/troublemaker who was based out of Europe, and it was hoped that
by holding the meetings in various companies in Asia, it would put the
travel costs of this known trouble maker out of reach --- and it
worked; the person, who had gotten ISO accrediation for some small
country that had the same standing as all of the USA, never did end up
attending any of the in-person meetings.

[1] Not by me; I and the others who had originally done the technical
work wasn't up on the policies and procedures of ISO, so the companies
that were interested in pushing this standard forward paid $$$ to
consultants whose primary careers was to work the ISO process; I just
got to see that particular sausage making factory and was quite
astonished by how it worked in comparison to the IETF.

Is any of this perfect?  No; but it's important to keep in mind that
standards organizations are composed of humans; both those who are
highly incentivized to make progress, and those who seem to have goals
to try to stop progress.  Quite frankly, I find the IETF setup of
requiring the investment of in-person face time to be a far better way
of solving the "how do you filter out the koooks and make progress
while still being open" than what I've seen in other standards
settings processes.

       	       				- Ted


From nobody Thu Feb 27 10:17: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 604AB1A0404 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 10:17:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.737
X-Spam-Level: 
X-Spam-Status: No, score=-1.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, J_CHICKENPOX_21=0.6, RP_MATCHES_RCVD=-0.547, 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 v2-iqwIwWpSb for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 10:17:04 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 674581A03E3 for <ietf@ietf.org>; Thu, 27 Feb 2014 10:17:03 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.234.32]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1RIGTtD029463 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Feb 2014 10:16:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393525006; bh=g66vkYwHB5DaapDTQZ9UHuq3Th/YUXlgnVJh7qobQD4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=1fow99p4U68TXDsQ7zztri19bqdDVLsFrrhNvFtnqy2SBrw6y1cXLiGycUqyruPMG yVQ/eGiHIYmp+xsX/KWhoShDJ1h5Gk2x0xcyJZAZiJVwrH200rDbpIp6/uUf/1hfO1 FsiHZgLt4kU+vc4lRJApdMBF+1StnmyHr+4WMO20=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393525006; i=@elandsys.com; bh=g66vkYwHB5DaapDTQZ9UHuq3Th/YUXlgnVJh7qobQD4=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=NUo48HYt4OJfCno52RgcvGvrpWNa9F9b5uQEvS2BGPY2SZiaPLlBlLExY9qhCnLV1 ox2DW7ZBzRu4qiRDupj/CHEQH79LIuxBsvj8h5gdicmM1RSdgLfmKyKwwkjq5oz5+h 9oqNc3ypSZqO0sG3M0uBtqriTfY1zUFBWA2BRMQo=
Message-Id: <6.2.5.6.2.20140227075435.0d761828@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Feb 2014 09:44:03 -0800
To: Mary Barnes <mary.h.barnes@gmail.com>, John Leslie <john@jlc.net>, "Theodore Ts'o" <tytso@mit.edu>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <CABmDk8m1Qk=-63LZnUZEW5vwXOucj+5tTJJH=PfcFEqPttoB-g@mail.g mail.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CABmDk8m1Qk=-63LZnUZEW5vwXOucj+5tTJJH=PfcFEqPttoB-g@mail.gmail.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/UbpttLTow1KZWkbnLbwk_tJ91Hk
Cc: John C Klensin <john-ietf@jck.com>, adrian@olddog.co.uk, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Feb 2014 18:17:05 -0000

Hi Mary, John, Ted,
At 03:46 27-02-2014, Mary Barnes wrote:
>[MB] That's a very easy statement for someone=20
>who is in the majority culturally and gender=20
>wise to make.   I certainly hope you are in the=20
>majority.  My perspective would be that we might=20
>actually make better progress with this "violent=20
>shift" that disrupts the current "social=20
>cohesion" by bringing in new ideas and=20
>different, more effective ways of working.  [/MB]

As background information, I was the first WG=20
Chair from the African and Latin American=20
regions.  There is now a WG Chair from the Latin=20
American region.  Adrian Farrel deserves credit=20
for that.  There was the following comment in the=20
Latin American region [1] about that:

   "Es la =FAnica Working Group Chair que vive en Latam, no?"

I agree with the "bringing in new ideas and=20
different, more effective ways of working".  I am=20
not inclined to follow the "IETF way"; I like to=20
see results while keeping the people I work with happy.

At 06:57 27-02-2014, John Leslie wrote:
>But many of us cannot afford the cost of three IETF weeks before we
>see some return. (Especially those who need their employer to subsidize
>three weeks of their time as well as the travel costs...)
>
>    We cannot reasonably hope to change human nature -- least of all by
>writing one RFC -- but surely we can do something to ameliorate this
>economic disincentive?

The issue is not about changing human=20
nature.  There was a perfectly valid reason (in=20
my opinion) for why there were three meetings (I=20
did not preface the last word with "IETF" as I=20
would then have to explain the history).  I would=20
be curious to read what others people think about the economic disincentive.

At 07:42 27-02-2014, Theodore Ts'o wrote:
>trying to pariticpate remotely, it's possible, but you have to be
>really, really good with your technical presentations, your evidence,
>with sample implementations, perhaps a huge installed base, etc.
>
>(And funny that, if you have all of this, it's likely that some
>company will be quite willing to fund you to show up to an IETF
>meeting.)

That's why there are a lot of Powerpoint=20
presentations.  Making fancy speeches at the=20
microphone may capture the attention of some company. :-)

Regards,
S. Moonesamy

1. https://mail.lacnic.net/pipermail/ietf-lac/2013-November/000418.html =20


From nobody Thu Feb 27 10:30:48 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 E07F61A042E for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 10:30:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.116
X-Spam-Level: **
X-Spam-Status: No, score=2.116 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=0.77] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X1FNK1I84M1d for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 10:30:46 -0800 (PST)
Received: from asmtp1.iomartmail.com (asmtp1.iomartmail.com [62.128.201.248]) by ietfa.amsl.com (Postfix) with ESMTP id 5978E1A03F2 for <ietf@ietf.org>; Thu, 27 Feb 2014 10:30:46 -0800 (PST)
Received: from asmtp1.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1RIURQD024648; Thu, 27 Feb 2014 18:30:28 GMT
Received: from 950129200 (108.26.90.92.rev.sfr.net [92.90.26.108]) (authenticated bits=0) by asmtp1.iomartmail.com (8.13.8/8.13.8) with ESMTP id s1RIUPw7024638 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 27 Feb 2014 18:30:26 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'S Moonesamy'" <sm+ietf@elandsys.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CABmDk8m1Qk=-63LZnUZEW5vwXOucj+5tTJJH=PfcFEqPttoB-g@mail.gmail.com> <6.2.5.6.2.20140227075435.0d761828@elandnews.com>
In-Reply-To: <6.2.5.6.2.20140227075435.0d761828@elandnews.com>
Subject: RE: Clarifying IETF process [Was: A private club]
Date: Thu, 27 Feb 2014 18:30:23 -0000
Message-ID: <126201cf33e9$fc404260$f4c0c720$@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: AQKhPBDpdM0RT6g54LGywL/yr5b9WAG9w+32AYMO2SEBUoJymwH0OxKlAlDIYIaY3pcsQA==
Content-Language: en-gb
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/fzpCs1xBGs0YhN82HFhtslyb56A
Cc: 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, 27 Feb 2014 18:30:48 -0000

Hi SM,

> There is now a WG Chair from the Latin
> American region.  Adrian Farrel deserves credit
> for that. 

Thanks, but no I don't.
I always appoint the best person for the job.
Ines owes her position as WG co-chair in the ROLL WG to her capabilities not to
her town of residence.

Adrian


From nobody Thu Feb 27 16:54:07 2014
Return-Path: <john@jlc.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 A081A1A0186 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 16:54:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level: 
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, J_CHICKENPOX_21=0.6, J_CHICKENPOX_35=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: 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_WOReFMSgnE for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 16:54:04 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id EC6C71A02C6 for <ietf@ietf.org>; Thu, 27 Feb 2014 16:54:03 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id 57EF9C94FA; Thu, 27 Feb 2014 19:53:59 -0500 (EST)
Date: Thu, 27 Feb 2014 19:53:59 -0500
From: John Leslie <john@jlc.net>
To: Theodore Ts'o <tytso@mit.edu>
Subject: Re: Clarifying IETF process [Was: A private club]
Message-ID: <20140228005359.GZ54716@verdi>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140227154241.GB7982@thunk.org>
User-Agent: Mutt/1.4.1i
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/HNiUJE6ryQy1vRKD7zikziR3m4c
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, 28 Feb 2014 00:54:05 -0000

Theodore Ts'o <tytso@mit.edu> wrote:
> 
> On Thu, Feb 27, 2014 at 09:57:55AM -0500, John Leslie wrote:
>> Donald Eastlake <d3e3e3@gmail.com> wrote:
>>> 
>>] 3. Eighty Percent of Success is Showing Up
>>]... 
>> 
>> We cannot reasonably hope to change human nature -- least of all by
>> writing one RFC -- but surely we can do something to ameliorate this
>> economic disincentive?
> 
> I've always thought this is a feature, but a bug.

   (Quoted without comment...)

> The reality is that there are a huge numbers of net.kooks out there.

   Oh my! :^( :^(

> It may be politically incorrect to say that, but it's true.

   Absolutely! Just count those Linux kooks!

   ;^)

> So if you are trying to pariticpate remotely, it's possible, but you
> have to be really, really good with your technical presentations,
> your evidence, with sample implementations, perhaps a huge installed
> base, etc.

   Umm...

   You're welcome to think that, if it makes you feel better...

> (And funny that, if you have all of this, it's likely that some
> company will be quite willing to fund you to show up to an IETF
> meeting.)

   You're welcome to think that, too...

> Other standards committees have other ways of filtering out kooks.

   "Born: 1968"... You must have been around in the 1990's...
Anyone who lived through Usenet should have learned _many_ ways to
filter out "kooks"...

> ...  Quite frankly, I find the IETF setup of requiring the investment
> of in-person face time to be a far better way of solving the "how do
> you filter out the koooks and make progress while still being open"
> than what I've seen in other standards settings processes.

   But _my_ question is, why does the "IETF" need to filter out the
"kooks?"

--
John Leslie <john@jlc.net>


From nobody Thu Feb 27 17:07: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 E38551A0654 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 17:07:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zPUh-FgIAa7g for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 17:07:09 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id A2DDC1A0307 for <ietf@ietf.org>; Thu, 27 Feb 2014 17:07:09 -0800 (PST)
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 22E551B817E for <ietf@ietf.org>; Thu, 27 Feb 2014 17:07:08 -0800 (PST)
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 F3A66190052; Thu, 27 Feb 2014 17:07:07 -0800 (PST)
Received: from [192.168.43.232] (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, 27 Feb 2014 17:07:07 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Clarifying IETF process [Was: A private club]
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140228005359.GZ54716@verdi>
Date: Thu, 27 Feb 2014 20:07:03 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6OQtMXA6g8aF79yCFE4_8d2QjkY
Cc: 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: Fri, 28 Feb 2014 01:07:11 -0000

On Feb 27, 2014, at 7:53 PM, John Leslie <john@jlc.net> wrote:
>   But _my_ question is, why does the "IETF" need to filter out the
> "kooks?"

Because they burn our most precious resource: the time of active =
contributors.

Of course, there is no way to filter out kooks, so the point is moot, =
but you asked, and that's why.


From nobody Thu Feb 27 17:36:55 2014
Return-Path: <john@jlc.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 813C01A01EB for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 17:36:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.747
X-Spam-Level: 
X-Spam-Status: No, score=-4.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5CRIlW7Wq7HW for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 17:36:53 -0800 (PST)
Received: from mailhost.jlc.net (mailhost.jlc.net [199.201.159.4]) by ietfa.amsl.com (Postfix) with ESMTP id 6115F1A01E0 for <ietf@ietf.org>; Thu, 27 Feb 2014 17:36:53 -0800 (PST)
Received: by mailhost.jlc.net (Postfix, from userid 104) id B458CC94BF; Thu, 27 Feb 2014 20:36:46 -0500 (EST)
Date: Thu, 27 Feb 2014 20:36:46 -0500
From: John Leslie <john@jlc.net>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Clarifying IETF process [Was: A private club]
Message-ID: <20140228013646.GA54716@verdi>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com>
User-Agent: Mutt/1.4.1i
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1sCU6L-6kJe5qRDFXEU689yNxDM
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, 28 Feb 2014 01:36:54 -0000

Ted Lemon <ted.lemon@nominum.com> wrote:
> On Feb 27, 2014, at 7:53 PM, John Leslie <john@jlc.net> wrote:
> 
>> But _my_ question is, why does the "IETF" need to filter out the
>> "kooks?"
> 
> Because they burn our most precious resource: the time of active
> contributors.

   Hi, Ted!

> Of course, there is no way to filter out kooks, so the point is moot,

   I couldn't have said it better!

> but you asked, and that's why.

   Apparently, there's a logical step in there which I missed... :^(

   Somebody help me, please: If the time of active contributors is a
precious resource, isn't the obvious solution to encourage more folks
to _become_ active contributors?

--
John Leslie <john@jlc.net>


From nobody Thu Feb 27 17:43:17 2014
Return-Path: <derhoermi@gmx.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 6A71D1A02CD for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 17:43:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SUFRH7kODdd4 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 17:43:13 -0800 (PST)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.20]) by ietfa.amsl.com (Postfix) with ESMTP id 568581A02CC for <ietf@ietf.org>; Thu, 27 Feb 2014 17:43:13 -0800 (PST)
Received: from netb ([89.204.154.58]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M6B6s-1XBS1n1vfG-00yAVg for <ietf@ietf.org>; Fri, 28 Feb 2014 02:43:11 +0100
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: John Leslie <john@jlc.net>
Subject: Re: Clarifying IETF process [Was: A private club]
Date: Fri, 28 Feb 2014 02:43:10 +0100
Message-ID: <8aqvg99fnfo5q76tbilnvjuh808rgtlop1@hive.bjoern.hoehrmann.de>
References: <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <20140228013646.GA54716@verdi>
In-Reply-To: <20140228013646.GA54716@verdi>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K0:iQi3yy0IyaWP8gIvgZUACyev89uqfEBkDkc5w0nuqc0+2vUB3u0 t+6Kc7uiK4A5mOXnGYGledsmrbisFJ+Be1AElf9ufTLkZEYuJ4DVOpzn1+QmkGJtu8loENt XQtEWX4B2je87LlK33IKlWutOaxI+6Qvb5o1Cy7OB5TA100uYTBIe7mvcq4i8iMskXGLDgb Ht1NZ/7iZDWU8hTMkMXBg==
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/zmAxEYXtK0OTOBbRvq_f_5KVtuY
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, 28 Feb 2014 01:43:15 -0000

* John Leslie wrote:
>   Somebody help me, please: If the time of active contributors is a
>precious resource, isn't the obvious solution to encourage more folks
>to _become_ active contributors?

http://en.wikipedia.org/wiki/The_Mythical_Man-Month is probably related.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 


From nobody Thu Feb 27 17:51:57 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 666101A064A for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 17:51:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 2eI-jt0Hp3gk for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 17:51:54 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 376931A04BA for <ietf@ietf.org>; Thu, 27 Feb 2014 17:51:54 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.226.234.32]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1S1pcok027573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Feb 2014 17:51:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393552312; bh=k8dSZinqviojjRPM5UJujGCKF1AOUF1SMSDeDd03iMU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=TTzaK8RmrZfsW+vbyWHl/ZCWtYoNVrr4G8eU6UdxqE/CDG/VsZONE4KwpyAWNPkMv VCgqxClyVV+FMSPDY2G/dpxFAF8CZ56Di8m/x0NqaG6QNdyb24A4jjA59C7c+UR2Bh eSzlGWE4ZZY4ZCovctI32CenHVD8p8+RVuT/KCT8=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393552312; i=@elandsys.com; bh=k8dSZinqviojjRPM5UJujGCKF1AOUF1SMSDeDd03iMU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=JT0o+cEeesBWu233UeHAcGw7H4F+/OYUsBN7/Re5ee7KwW8HXtahTTfGNgSXjN6cV CDwM9tjuZ0SB7O5XR0s0D0NxZFIItO/X66wo6mtf0RHK8gDc7+5r7gKD1qY5y3M+pC QYBz6hISz3jwR+7X8VsoMSMDbYzovOdIsPkSDLhQ=
Message-Id: <6.2.5.6.2.20140227171611.0dfd3460@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Feb 2014 17:51:15 -0800
To: Ted Lemon <ted.lemon@nominum.com>, John Leslie <john@jlc.net>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/gUBSrlUMln9Yl4Myvzj7lzCprKQ
Cc: 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: Fri, 28 Feb 2014 01:51:55 -0000

Hi Ted,
At 17:07 27-02-2014, Ted Lemon wrote:
>Because they burn our most precious resource: the time of active contributors.

I do not filter out anyone.

John Leslie is an IESG scribe.  Is he considered as an active contributor?

Quoting some text from the Tao:

   "The IETF is really about its participants.  Because the IETF welcomes all
    interested individuals, IETF participants come from all over the world
    and from many different parts of the Internet industry."

If where a person resides is not important then the "come from all 
over the world" is incorrect.

The recent discussions have clarified that regular IETF participants 
are aware that some IETF participants do not adhere to BCP 
54.  Quoting the IETF Chair out of context:

   'This seems inline with RFC 2026 notion that BCPs can be "community's best
    current thinking on a statement of principle".'

It is difficult to believe that the IESG is unaware of that.  It 
seems that people are turning a blind eye [1].

Regards,
S. Moonesamy

1. To knowingly refuse to acknowledge something which you know to be real. 


From nobody Thu Feb 27 20:07:05 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 1DE1C1A06D0 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 20:07:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.439
X-Spam-Level: 
X-Spam-Status: No, score=-0.439 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 BQEfqRb_vV8r for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 20:07:01 -0800 (PST)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id 5F4291A06CE for <ietf@ietf.org>; Thu, 27 Feb 2014 20:07:01 -0800 (PST)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WJEiw-0003iJ-8n; Fri, 28 Feb 2014 04:06:58 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 3D7D0580249; Thu, 27 Feb 2014 23:06:57 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1393560417; bh=YqEtxvcMSwlUeytzjiYEZ5J6bXoi3DWlTAeMX8Sq4bk=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=fZpyqffwAHGRTRoSo/jQ7ci90t9murvlMS0T3fQqbm596qshNVnj9iTbgy7qqkMK/ 5oH78E5yNwrzRPMaIj+t3UJF/EdT3S6sktfp0a0NJCeidKHhAYODrSVH+vH7SSt5y4 5xpvBOkJYQNGPDCpp0e8rGdRBoNu7ydHPJRuQX9Y=
Date: Thu, 27 Feb 2014 23:06:57 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: John Leslie <john@jlc.net>
Subject: Re: Clarifying IETF process [Was: A private club]
Message-ID: <20140228040657.GA3348@thunk.org>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <20140228013646.GA54716@verdi>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140228013646.GA54716@verdi>
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/FcvA9J85fVzQQtgzUP21dcFxSGY
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, 28 Feb 2014 04:07:03 -0000

On Thu, Feb 27, 2014 at 08:36:46PM -0500, John Leslie wrote:
>    Somebody help me, please: If the time of active contributors is a
> precious resource, isn't the obvious solution to encourage more folks
> to _become_ active contributors?

Only the competent ones.  There's a reason why all of the successful
companies in Silicon Valley spend a huge amount of effort making sure
that you don't hire people who will drag down the rest of the team.

So if there is a way of encouraging the compentent to be active
contributors, and discourage the incompetent, the open source project
and standards body is more likely to thrive.  The fact that someone
has the funding to attend a face to face meeting, whether it be to an
open source conference, or a standards meeting, certainly does not
correlate perfectly with competence, granted.

But my personal experience is that it works surprisingly well, so the
fact that face to face meetings might make it harder for those who
can't find someone who thinks it worthwhile to fund their work and/or
travel, is not something that I personally have a problem with.  Of
course, I'm not on the IETF leadership, so fortunately, it's not up to
me.  :-)

Cheers,

						- Ted





From nobody Thu Feb 27 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 BA6CC1A0295 for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 21:53:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.748
X-Spam-Level: 
X-Spam-Status: No, score=-4.748 tagged_above=-999 required=5 tests=[BAYES_50=0.8, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cqu9TyrIzXUI for <ietf@ietfa.amsl.com>; Thu, 27 Feb 2014 21:53:10 -0800 (PST)
Received: from e7.ny.us.ibm.com (e7.ny.us.ibm.com [32.97.182.137]) by ietfa.amsl.com (Postfix) with ESMTP id 886CD1A01CD for <ietf@ietf.org>; Thu, 27 Feb 2014 21:53:09 -0800 (PST)
Received: from /spool/local by e7.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, 28 Feb 2014 00:53:07 -0500
Received: from d01dlp03.pok.ibm.com (9.56.250.168) by e7.ny.us.ibm.com (192.168.1.107) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 28 Feb 2014 00:53:04 -0500
Received: from b01cxnp23032.gho.pok.ibm.com (b01cxnp23032.gho.pok.ibm.com [9.57.198.27]) by d01dlp03.pok.ibm.com (Postfix) with ESMTP id B2A4CC9003E for <ietf@ietf.org>; Fri, 28 Feb 2014 00:53:00 -0500 (EST)
Received: from d01av02.pok.ibm.com (d01av02.pok.ibm.com [9.56.224.216]) by b01cxnp23032.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1S5r3VO10027368 for <ietf@ietf.org>; Fri, 28 Feb 2014 05:53:03 GMT
Received: from d01av02.pok.ibm.com (localhost [127.0.0.1]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s1S5r3cr005735 for <ietf@ietf.org>; Fri, 28 Feb 2014 00:53:03 -0500
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.44.115.148]) by d01av02.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s1S5r3C8005730 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <ietf@ietf.org>; Fri, 28 Feb 2014 00:53:03 -0500
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 s1S5r3X1016386 for <ietf@ietf.org>; Fri, 28 Feb 2014 00:53:03 -0500
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.14.7/8.14.7/Submit) id s1S5r2xK016347 for ietf@ietf.org; Fri, 28 Feb 2014 00:53:02 -0500
From: Thomas Narten <narten@us.ibm.com>
Message-Id: <201402280553.s1S5r2xK016347@rotala.raleigh.ibm.com>
Date: Fri, 28 Feb 2014 00:53:02 -0500
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: No
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14022805-5806-0000-0000-0000243D5554
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/jij0J4Ok2_ZI9e8K-t-0pVlEjZg
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2014 05:53:14 -0000

Total of 175 messages in the last 7 days.
 
script run at: Fri Feb 28 00:53:02 EST 2014
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
 10.86% |   19 |  8.11% |   137255 | sm+ietf@elandsys.com
  6.29% |   11 |  7.17% |   121385 | abdussalambaryun@gmail.com
  5.71% |   10 |  4.18% |    70800 | dhc@dcrocker.net
  5.14% |    9 |  3.92% |    66360 | l.wood@surrey.ac.uk
  4.57% |    8 |  4.44% |    75139 | hallam@gmail.com
  0.57% |    1 |  7.23% |   122381 | ggm@algebras.org
  0.57% |    1 |  7.22% |   122252 | lars@netapp.com
  4.00% |    7 |  3.29% |    55728 | brian.e.carpenter@gmail.com
  4.00% |    7 |  3.26% |    55258 | john-ietf@jck.com
  2.86% |    5 |  3.35% |    56777 | jdrake@juniper.net
  2.86% |    5 |  1.88% |    31890 | adrian@olddog.co.uk
  1.71% |    3 |  2.67% |    45138 | benamar73@gmail.com
  2.29% |    4 |  1.70% |    28813 | barryleiba@computer.org
  2.29% |    4 |  1.66% |    28096 | john@jlc.net
  2.29% |    4 |  1.54% |    26027 | melinda.shore@gmail.com
  2.29% |    4 |  1.45% |    24490 | ted.lemon@nominum.com
  2.29% |    4 |  1.18% |    20054 | randy@psg.com
  1.71% |    3 |  1.62% |    27418 | dave@cridland.net
  1.71% |    3 |  1.32% |    22264 | moore@network-heretics.com
  1.71% |    3 |  1.11% |    18821 | loa@pi.nu
  1.14% |    2 |  1.37% |    23168 | mary.h.barnes@gmail.com
  1.14% |    2 |  1.37% |    23134 | andrea@digitalpolicy.it
  1.14% |    2 |  1.36% |    22956 | ron.even.tlv@gmail.com
  1.14% |    2 |  1.06% |    17890 | stbryant@cisco.com
  1.14% |    2 |  1.02% |    17191 | narten@us.ibm.com
  0.57% |    1 |  1.59% |    26856 | abdelmoniem.rezk@orange.com
  1.14% |    2 |  0.99% |    16839 | stephen.farrell@cs.tcd.ie
  1.14% |    2 |  0.99% |    16711 | scott.brim@gmail.com
  1.14% |    2 |  0.95% |    16155 | chair@ietf.org
  1.14% |    2 |  0.94% |    15965 | tytso@mit.edu
  1.14% |    2 |  0.89% |    15147 | lear@cisco.com
  1.14% |    2 |  0.88% |    14862 | ajs@anvilwalrusden.com
  1.14% |    2 |  0.84% |    14156 | ned+ietf@mauve.mrochek.com
  1.14% |    2 |  0.77% |    12971 | jari.arkko@piuha.net
  1.14% |    2 |  0.74% |    12494 | paf@frobbit.se
  1.14% |    2 |  0.70% |    11879 | derhoermi@gmx.net
  1.14% |    2 |  0.69% |    11684 | tterriberry@mozilla.com
  1.14% |    2 |  0.66% |    11099 | jnc@mercury.lcs.mit.edu
  0.57% |    1 |  1.14% |    19248 | tbray@textuality.com
  0.57% |    1 |  1.13% |    19084 | dafalla@yahoo.com
  0.57% |    1 |  1.01% |    17167 | geoff.ietf@mulligan.com
  0.57% |    1 |  0.84% |    14210 | apvelan.ietf@gmail.com
  0.57% |    1 |  0.82% |    13945 | pthaler@broadcom.com
  0.57% |    1 |  0.74% |    12578 | d3e3e3@gmail.com
  0.57% |    1 |  0.58% |     9824 | ietf@thomasclausen.org
  0.57% |    1 |  0.57% |     9615 | mstjohns@comcast.net
  0.57% |    1 |  0.55% |     9277 | vesely@tana.it
  0.57% |    1 |  0.54% |     9098 | fred@cisco.com
  0.57% |    1 |  0.52% |     8829 | daedulus@btconnect.com
  0.57% |    1 |  0.48% |     8114 | jmpolk@cisco.com
  0.57% |    1 |  0.47% |     8024 | ietf@trammell.ch
  0.57% |    1 |  0.47% |     7960 | drc@virtualized.org
  0.57% |    1 |  0.43% |     7217 | ynir@checkpoint.com
  0.57% |    1 |  0.42% |     7071 | tjc@ecs.soton.ac.uk
  0.57% |    1 |  0.39% |     6673 | becha@ripe.net
  0.57% |    1 |  0.39% |     6597 | johnl@taugh.com
  0.57% |    1 |  0.39% |     6587 | morrowc.lists@gmail.com
  0.57% |    1 |  0.38% |     6493 | joelja@bogus.com
  0.57% |    1 |  0.38% |     6481 | dcrocker@bbiw.net
  0.57% |    1 |  0.35% |     5852 | swmike@swm.pp.se
  0.57% |    1 |  0.31% |     5164 | llynch@civil-tongue.net
  0.57% |    1 |  0.30% |     5062 | kent@bbn.com
  0.57% |    1 |  0.30% |     5023 | izaac@setec.org
--------+------+--------+----------+------------------------
100.00% |  175 |100.00% |  1692696 | Total


From nobody Fri Feb 28 00:08:38 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 1AA051A0021 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 00:08:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z7l3YzplGZO8 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 00:08:33 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id C2EA21A0017 for <ietf@ietf.org>; Fri, 28 Feb 2014 00:08:33 -0800 (PST)
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 1WJIUd-0004Gh-VN; Fri, 28 Feb 2014 08:08:28 +0000
Date: Fri, 28 Feb 2014 08:08:27 +0000
Message-ID: <m2vbvzvev8.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.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/doy5xKWQBqbQC0fTigCK4oae4s8
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, 28 Feb 2014 08:08:35 -0000

> Of course, there is no way to filter out kooks

man procmail


From nobody Fri Feb 28 00:09: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 E4CAF1A076A for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 00:09:19 -0800 (PST)
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 r_9GfngZOAGl for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 00:09:18 -0800 (PST)
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 6324B1A0021 for <ietf@ietf.org>; Fri, 28 Feb 2014 00:09:05 -0800 (PST)
Received: by mail-yh0-f49.google.com with SMTP id z6so311103yhz.36 for <ietf@ietf.org>; Fri, 28 Feb 2014 00:09:03 -0800 (PST)
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=Dy+7pNNFyTiOxsliwxBOh6LWbQO3+TF0QnbBhNjjE/s=; b=Wab9U6rUN2lS54AbLTJE5rYqzycPedEMep1boz3gSbim97SVso6XSK+cAZ2GmXkbWy 0s4UBWVk+mQBdEG0uOa5tiuX/pDSa5UNoJ+hHfZK6h436Mpnq/TdivHWK+9KS1uW/MiP 6Io5z8kNdhd0juNusesvQv4618ukdd+3CPz8av4+cbn5JrOKnY9LWe+DbYVY/+2I9ERF 4IL2V6UmgCi8yP38aUUb2m9ho+DjgV44SjmBzx9w5xtiN0ZiHsutU5gbQb620G2GiA/b E8iw2QG2R4aUXkQc6DOhmQ4jKEyhpimGdklcyqp/vEdZn6/9VGbSpz7yyoYjRirlphzm Giww==
MIME-Version: 1.0
X-Received: by 10.236.124.104 with SMTP id w68mr1757099yhh.2.1393574943401; Fri, 28 Feb 2014 00:09:03 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Fri, 28 Feb 2014 00:09:03 -0800 (PST)
In-Reply-To: <m34n3m0xnz.wl%narten@us.ibm.com>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <B8A7FCE9A03D55CEAEB34881@JcK-HP8200.jck.com> <CADnDZ8_nb7ByhjqgtW_4EAqApYNaJEK_Q8ns08VoOgww4iD9Dg@mail.gmail.com> <F07E5EA375E40279ACE7646E@JcK-HP8200.jck.com> <m34n3m0xnz.wl%narten@us.ibm.com>
Date: Fri, 28 Feb 2014 09:09:03 +0100
Message-ID: <CADnDZ89EB_ZJtBTbPq9Xi3sx9CN7=+RLx9kd=gWMtKfAR9q75w@mail.gmail.com>
Subject: Knowledge and suggestions (was: Re: Ad hominems)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Thomas Narten <narten@us.ibm.com>
Content-Type: multipart/alternative; boundary=20cf300fac3378291204f372f3b7
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/l0IvIRCsvW9rxf8_fkegr5EuGNI
Cc: John C Klensin <john-ietf@jck.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, 28 Feb 2014 08:09:20 -0000

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

On Wednesday, February 26, 2014, Thomas Narten wrote:

> > I think you are making assumptions in the paragraph above that
> > are symptomatic of why you then perceive yourself as being
> > mistreated.
>
> Strong agreement.


The mistreated is not an assumption it is a feeling position felt through
experience within an organisation.  The assumption mislead starts/comes
from the responder-to-suggestions when he/she reads any first
message suggestion (usually then tries to see from whom and think
personal).  Respect is very important in Human to Human (H2H)
communication that
can be sensed easily, but often many start expecting to get respect when
they assume they have a right to suggest. Many H also will expect that they
get not respected when they argue others personal issues in public.

I will add to the subject: right to suggest.

AB

>
>

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

On Wednesday, February 26, 2014, Thomas Narten  wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">&gt; I think you are making assumptions in the paragraph abov=
e that<br>


&gt; are symptomatic of why you then perceive yourself as being<br>
&gt; mistreated.<br>
<br>
Strong agreement.</blockquote><div><br></div><div>The mistreated is not an =
assumption it is a feeling position felt through experience within an organ=
isation.=A0=A0The assumption mislead=A0starts/comes from the responder-to-s=
uggestions=A0when he/she=A0reads any first message=A0suggestion (usually th=
en tries to see from whom=A0and think personal).=A0=A0Respect is very impor=
tant in Human to Human (H2H)=A0<span></span>communication=A0that can be sen=
sed easily, but often=A0many start expecting to get respect when they assum=
e they have a right to suggest. Many H=A0also will=A0expect that they get n=
ot respected when they argue others=A0personal issues in public.=A0</div>

<div><br></div><div>I will add to the subject: right to suggest.=A0</div><d=
iv><br></div><div>AB</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
</blockquote>

--20cf300fac3378291204f372f3b7--


From nobody Fri Feb 28 01:29:47 2014
Return-Path: <rw@firstpr.com.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2AF51A00FF for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:29:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.657
X-Spam-Level: ***
X-Spam-Status: No, score=3.657 tagged_above=-999 required=5 tests=[BAYES_99=3.5, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RP_MATCHES_RCVD=-0.547] autolearn=no
Received: 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-gBBKHxttFk for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:29:42 -0800 (PST)
Received: from gair.firstpr.com.au (gair.firstpr.com.au [150.101.162.123]) by ietfa.amsl.com (Postfix) with ESMTP id 4946E1A0075 for <ietf@ietf.org>; Fri, 28 Feb 2014 01:29:42 -0800 (PST)
Received: from [10.0.0.6] (unknown [10.0.0.6]) by gair.firstpr.com.au (Postfix) with ESMTP id 2A8181759C1; Fri, 28 Feb 2014 20:29:38 +1100 (EST)
Message-ID: <531056FE.6010905@firstpr.com.au>
Date: Fri, 28 Feb 2014 20:29:34 +1100
From: Robin Whittle <rw@firstpr.com.au>
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 Discussion Mailing List <ietf@ietf.org>
Subject: US users give the Net a good rap
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/-tFgsM6vzqYKqUnK9qNM_pRnfN8
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2014 09:29:43 -0000

http://www.pewinternet.org/2014/02/27/the-web-at-25-in-the-u-s/
http://www.pewinternet.org/files/2014/02/PIP_25th-anniversary-of-the-Web_022714_pdf.pdf

In a phone survey of 1006 adults in the continental USA, 87% used the
Internet, with 58% of those questioned owning a smartphone.  Of these
users, when questioned about whether the Internet was good, bad or both
for society and for themselves:

Q:      "For society"  "For me"
Good    76%            90%
Both    15%             6%
Bad      8&             3%

 - Robin



From nobody Fri Feb 28 01:44: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 87EF41A0059 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:44:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H8ujqetcm9ma for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:44:27 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 4572C1A003B for <ietf@ietf.org>; Fri, 28 Feb 2014 01:44:27 -0800 (PST)
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 874891B80EA for <ietf@ietf.org>; Fri, 28 Feb 2014 01:44:25 -0800 (PST)
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 63D05190043; Fri, 28 Feb 2014 01:44:25 -0800 (PST)
Received: from [192.168.101.54] (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, 28 Feb 2014 01:44:25 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Clarifying IETF process [Was: A private club]
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20140228013646.GA54716@verdi>
Date: Fri, 28 Feb 2014 09:36:44 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <9B0B3C9D-E05D-434C-BB68-648657E7A1E5@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <20140228013646.GA54716@verdi>
To: John Leslie <john@jlc.net>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/mwqc1neIj--8x3gUJh8Sqfklk3M
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, 28 Feb 2014 09:44:28 -0000

On Feb 28, 2014, at 1:36 AM, John Leslie <john@jlc.net> wrote:
>   Somebody help me, please: If the time of active contributors is a
> precious resource, isn't the obvious solution to encourage more folks
> to _become_ active contributors?

In principle yes, and in practice probably, but I think being an =
effective contributor is the only thing that's valuable.   Being active =
isn't if you aren't effective.   And being an effective contributor is =
non-trivial.


From nobody Fri Feb 28 01:45:35 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 DD44E1A012E for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:45:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o_Tv3egcJHP7 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:45:32 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id E58D11A003B for <ietf@ietf.org>; Fri, 28 Feb 2014 01:45:32 -0800 (PST)
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 6926C1B80E5 for <ietf@ietf.org>; Fri, 28 Feb 2014 01:45:31 -0800 (PST)
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 62A58190043; Fri, 28 Feb 2014 01:45:31 -0800 (PST)
Received: from [192.168.101.54] (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, 28 Feb 2014 01:45:31 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Clarifying IETF process [Was: A private club]
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <6.2.5.6.2.20140227171611.0dfd3460@resistor.net>
Date: Fri, 28 Feb 2014 09:45:26 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <2ED519E2-F5B0-4AA0-9F5C-1A0BF19B0929@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <6.2.5.6.2.20140227171611.0dfd3460@resistor.net>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/D_lo7mMVcZ8C6szT_ksRuG28fD4
Cc: Theodore Ts'o <tytso@mit.edu>, John Leslie <john@jlc.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: Fri, 28 Feb 2014 09:45:34 -0000

On Feb 28, 2014, at 1:51 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:
> I do not filter out anyone.

If you mean an email filter robot, I don't either.   And I'm generally =
really happy to see new names go by, and see what the new people with =
whom they are associated have to say.   I think that that's the =
obligation we have.

But I've learned the hard way since joining the IESG that I absolutely =
do not have enough time to do the things I'm supposed to be doing _and_ =
read and respond to every email message everyone sends.   And indeed, as =
in this case, by responding I wind up increasing my workload, because =
interesting people reply.   :)


From nobody Fri Feb 28 01:49:40 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 BB2B51A079A for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:49:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rjchpRkMUfpy for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:49:38 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 38F8D1A0184 for <ietf@ietf.org>; Fri, 28 Feb 2014 01:49:38 -0800 (PST)
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 BBE211B80E5 for <ietf@ietf.org>; Fri, 28 Feb 2014 01:49:36 -0800 (PST)
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 B13DC190043; Fri, 28 Feb 2014 01:49:36 -0800 (PST)
Received: from [192.168.101.54] (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, 28 Feb 2014 01:49:36 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Clarifying IETF process [Was: A private club]
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <m2vbvzvev8.wl%randy@psg.com>
Date: Fri, 28 Feb 2014 09:49:27 +0000
Content-Transfer-Encoding: 7bit
Message-ID: <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Tw0eb51efsZV1YnZlTSbzgfPoAo
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, 28 Feb 2014 09:49:40 -0000

On Feb 28, 2014, at 8:08 AM, Randy Bush <randy@psg.com> wrote:
> man procmail

Can't.   :(


From nobody Fri Feb 28 01:53:49 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 69E651A079E for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:53:48 -0800 (PST)
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 UASCsagG09U8 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 01:53:46 -0800 (PST)
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 084381A0184 for <ietf@ietf.org>; Fri, 28 Feb 2014 01:53:45 -0800 (PST)
Received: by mail-yh0-f49.google.com with SMTP id z6so391139yhz.8 for <ietf@ietf.org>; Fri, 28 Feb 2014 01:53:44 -0800 (PST)
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=ZCJBvc1/Y9SF8XVLKvGjKQmtBVzv1ejjTGj0j/9MC4Q=; b=r65QK14wsPWotOXJ+eDXfBAR9+PeRH8YpmKhXXx04ltne9z9AW/XJ/oYiiUcp4Mr0f +JG7JcNZcx5JB2LFgmVz7g68U6W2QIJA+DWV435axgWrIN3cueH8Oz3A3NULkwRjDGw0 Fs25TICAqIyEmlV046pC/H+zS1eLPyDRxRoulMOLbeJzvBPt4uP8JAFcZdUpG72ppqvz El5RLNyRT46hE8bLsCwuTso9pDAEWaWvImaIOaeq1AQsDm1+LcfOmY7PWMKsRwYodrSf 6/5Ei0e4Q/dIspb4XGLAB4c/lvPcOtS/TvYQvCcD7mP4VucJSHgQwvGbdN+4KBGym25Q 82kQ==
MIME-Version: 1.0
X-Received: by 10.236.15.102 with SMTP id e66mr835729yhe.69.1393581224098; Fri, 28 Feb 2014 01:53:44 -0800 (PST)
Received: by 10.170.202.7 with HTTP; Fri, 28 Feb 2014 01:53:44 -0800 (PST)
In-Reply-To: <01P4RNW46DFQ00004W@mauve.mrochek.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com>
Date: Fri, 28 Feb 2014 10:53:44 +0100
Message-ID: <CADnDZ8_ZgDp-rWETgdMp7o+XXVXcHv2B58h-Pon=5xmgi0e8uQ@mail.gmail.com>
Subject: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>
Content-Type: multipart/alternative; boundary=089e0122a3d4d4043e04f37469cd
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/F4SZLcuhFX1baLqWmDh9b4PXr1g
Cc: "ietf@ietf.org" <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: Fri, 28 Feb 2014 09:53:48 -0000

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

I agree to write a draft to help the suggestion of having future draft of
defining an Ad hominems and preventing it.  Comments below,

On Tuesday, February 25, 2014, wrote:

> I find myself compelled to agree with both Noel and Kent here. The
> question may
> have been posed offensively - I take no position on that - but in matters
> like this past experience is hugely relevant.
>
>
Remote participants do experience meetings as f2f participants do. The
question was not relevant, because it assumes that there is no problem in
IETF meetings and assumes that the improvement is needed in the poster
participant side (that may make it personal when one is disturbing another
many times).

Like it or not, not every issue that comes up can be decided on the basis of
> crisp technical arguments. (In fact it really seems to me that are less
> able to decide things purely on technical merit as time goes on.)
>
> And it's not just internal IETF matters at issue here: If, say, someone
> makes a
> statement about the probable impact of some technical choice on the future
> deployment of a protocol, people have every right to know if that
> statement is
> based on past deployment experience or is nothing but guesswork.


All People have rights and right to speak, but no need for making it look
funny when the poster is new comer or still had no RFC. If you say what is
your experience to some one new of 2 years and had no RFC, that
question will be like new comer have not same right as old comer to Speak.
Melinda once mention as to get technical work done to get recognise, but my
opinion is that this way of thinking to exclude new people until they do
RFC or do f2f attendance, is bad for IETF.

>
> And yes, this puts newcomers at something of a disadvantage because of
> their
> lack of experience.


All have lack of types of experience in any organisation and specially
IETF. Not being able to welcome new participants is bad behavior if IETF is
not able to solve AD hominems.

And also note that when such questions are asked, the
> answers can be disconcerting. You don't know what experience someone has
> until
> you ask, and sometimes you find they have substantive experience that makes
> them the expert, not you.


If the question was the first conversation between two participants in IETF
then you are right. That was not the case, the case was one person doing Ad
homenimes to a new comer for many time, then that new comer reported cases
to IETF chair and to ADs. After that when the new comer will show up after
large patients, and made a suggestion, that Ad homenime person continues to
discourage the new comer. I hope you understand the specific case, and then
I agree we can look into general case of we need to know what is experience
of input makers.

IETF is responsible to solve this personal experience answering, not any
participant. Just because one person is known or welcomed that should not
mean experience. Just because one person has an RFC or many RFCs, that does
not mean they can do Ad hominemes.

I am very sorry but it looks now better for me to leave the IETF list
discussion (excluding LC comments and Review) for some time because this
list seems with no experience how to deal with new comers, and I will work
hard on Sunday to distribute the message to all new comers that this list
is dangerous list for new comers. I may also just make a question and
comment in the tutorial for new comers. I did enjoy posting on this list
because there are some great people I noticed, but I will stop for some
time for the list to think about its behavior/progress and new comers think
about their progress.

I think I will report/post the IETF list behavior with its
welcoming experiences with analysis and recommendation in one
historical draft when I return.

See you in meetings, thanks,

Salam

AB

>
>
>

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

I agree to write a draft to help the suggestion of having future=A0draft of=
 defining=A0an Ad hominems and preventing it.=A0=A0Comments below,<br><br>O=
n Tuesday, February 25, 2014,   wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I find myself compelled to agree with both Noel and Kent here. The question=
 may<br>


have been posed offensively - I take no position on that - but in matters<b=
r>
like this past experience is hugely relevant.<br>
<br></blockquote><div><br></div><div>Remote participants do experience meet=
ings as f2f participants do.=A0The question was not relevant,=A0because it =
assumes that there is no problem in IETF=A0<span></span>meetings and assume=
s that the improvement is needed in the poster participant=A0side (that may=
 make it personal when one is disturbing another many times).=A0<span></spa=
n></div>

<div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">

Like it or not, not every issue that comes up can be decided on the basis o=
f<br>
crisp technical arguments. (In fact it really seems to me that are less<br>
able to decide things purely on technical merit as time goes on.)<br>
<br>
And it&#39;s not just internal IETF matters at issue here: If, say, someone=
 makes a<br>
statement about the probable impact of some technical choice on the future<=
br>
deployment of a protocol, people have every right to know if that statement=
 is<br>
based on past deployment experience or is nothing but guesswork.</blockquot=
e><div><br></div><div>All=A0People have rights and right to speak,=A0but no=
 need for making it look funny when the poster is new comer or still had no=
 RFC. If you say what is your experience to some one new of 2 years and had=
 no RFC, that question=A0will be like new comer have not same right as old =
comer to Speak. Melinda once mention as to get technical work done to get r=
ecognise, but my opinion is that this way of thinking to exclude new people=
 until they do RFC or do f2f attendance,=A0is bad for IETF.=A0</div>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
And yes, this puts newcomers at something of a disadvantage because of thei=
r<br>
lack of experience.=A0</blockquote><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"></blockq=
uote><div><br></div><div>All have lack of types of=A0experience in any orga=
nisation and=A0specially IETF. Not being able to welcome new participants i=
s bad behavior if IETF is not able to solve AD hominems.=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">And also note that when such =
questions are asked, the<br>
answers can be disconcerting. You don&#39;t know what experience someone ha=
s until<br>
you ask, and sometimes you find they have substantive experience that makes=
<br>
them the expert, not you.</blockquote><div><br></div><div>If the question w=
as the first conversation between two participants in IETF then you are rig=
ht. That was not the case, the case was one person doing Ad homenimes to a =
new comer for many time, then that new comer reported cases to IETF chair a=
nd to ADs. After that when the new comer will show up after large patients,=
 and made a suggestion, that Ad homenime person continues to discourage the=
 new comer. I hope you understand the specific case, and then I agree we ca=
n look into=A0general case of we need to know what is experience of input m=
akers.=A0</div>
<div><br></div><div>IETF is responsible to solve this personal experience a=
nswering, not any participant. Just because one person is known or welcomed=
 that should not mean experience. Just because one person has an RFC or man=
y RFCs, that does not mean they can do Ad hominemes.=A0</div>
<div><br></div><div>I am very sorry but it looks now better for me to leave=
 the IETF list discussion=A0(excluding LC comments and Review)=A0for some t=
ime=A0because this list seems with no experience how to deal with new comer=
s, and I will work hard on Sunday to distribute the message to all new come=
rs that this list is dangerous list for new comers. I may also=A0just make =
a question and comment in the tutorial for new comers. I did enjoy posting =
on this list because there are some great people I noticed,=A0but I will st=
op for some time for the list to think about its behavior/progress=A0and ne=
w comers think about their progress.=A0</div>
<div><br></div><div>I think I=A0will report/post=A0the IETF list behavior w=
ith its welcoming=A0experiences with analysis and recommendation=A0in one h=
istorical=A0draft when I return.=A0</div><div><br></div><div>See you in mee=
tings, thanks,</div>
<div><br></div><div>Salam</div><div><br></div><div>AB</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><br>
<br>
</blockquote>

--089e0122a3d4d4043e04f37469cd--


From nobody Fri Feb 28 03:02:35 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 446D91A00EF for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 03:02:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nk4fI9oevTW9 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 03:02:33 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id 4E4DF1A00CB for <ietf@ietf.org>; Fri, 28 Feb 2014 03:02:33 -0800 (PST)
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 1WJLD3-0004pO-PY; Fri, 28 Feb 2014 11:02:30 +0000
Date: Fri, 28 Feb 2014 11:02:29 +0000
Message-ID: <m2lhwvbiuy.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.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/cSWJzz7PFrIle68ss3oyzNHE3dE
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, 28 Feb 2014 11:02:34 -0000

>> man procmail
> Can't.   :(

my deep sympathies


From nobody Fri Feb 28 04:22:45 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 EFFEA1A07C7 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 04:22:31 -0800 (PST)
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 M0fTXSmvOkOG for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 04:22:26 -0800 (PST)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 176811A07E8 for <ietf@ietf.org>; Fri, 28 Feb 2014 04:21:06 -0800 (PST)
Received: by mail-qa0-f45.google.com with SMTP id hw13so554850qab.32 for <ietf@ietf.org>; Fri, 28 Feb 2014 04:21:05 -0800 (PST)
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=sRgObcsw8uDsb/Tm6F+zhIQcS4R6/LO6//e9jEQosLQ=; b=va1UWHUe2NefDunRLi+7zEcN8rYIEjTimLe475Jrf2GFGz932fnJohy7+9hbAUBTKW pIIaNG9ZJ9NJEQI3dEK2/c172z872wNWrXldbYflnasaKKy39iG2rmNub2cAvDpPnOHx IDu2KA4sU/eSNQVqhlv+XxdL8yybpEQJxOJELSDbQSGwC8xgSKLFlvYE+srrP5x9c1p8 YxZxGjxn3qUK8B7XhVP5vB5YNXS1WlfGidtjGhQ0sB3ROU91Bw2Rq6kQeico9p/cQxpa UZ7c6FQ5Fu/yZaYVFMhfAx+ecIsXBNbZT3o1UHdSZ/x2Uin8yEQlUi4d6y7n5EKG/m2F 1COw==
MIME-Version: 1.0
X-Received: by 10.140.95.179 with SMTP id i48mr2916461qge.1.1393590065102; Fri, 28 Feb 2014 04:21:05 -0800 (PST)
Received: by 10.224.186.142 with HTTP; Fri, 28 Feb 2014 04:21:05 -0800 (PST)
In-Reply-To: <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com>
Date: Fri, 28 Feb 2014 17:51:05 +0530
Message-ID: <CAEP5zKRhpzhFT293cngvzf65AsdgS6A6f=K-HneDJbJHSbN1DA@mail.gmail.com>
Subject: Re: Clarifying IETF process [Was: A private club]
From: Chaitanya Dhareshwar <chaitanyabd@gmail.com>
To: Ted Lemon <ted.lemon@nominum.com>
Content-Type: multipart/alternative; boundary=001a11c16dfccb02a004f37678b6
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/erR0NaWPwUXhamM8hjk0wYu4YBo
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, 28 Feb 2014 12:22:32 -0000

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

Try http://www.gsp.com/cgi-bin/man.cgi?topic=procmailrc or
http://unixhelp.ed.ac.uk/CGI/man-cgi?procmail

*Chaitanya Dhareshwar*

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


On Fri, Feb 28, 2014 at 3:19 PM, Ted Lemon <ted.lemon@nominum.com> wrote:

> On Feb 28, 2014, at 8:08 AM, Randy Bush <randy@psg.com> wrote:
> > man procmail
>
> Can't.   :(
>
>

--001a11c16dfccb02a004f37678b6
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">Try=A0<a href=3D"http://www.gsp.com/cgi-bin/man.cgi?topic=3Dproc=
mailrc" style=3D"font-family:arial">http://www.gsp.com/cgi-bin/man.cgi?topi=
c=3Dprocmailrc</a>=A0or=A0<a href=3D"http://unixhelp.ed.ac.uk/CGI/man-cgi?p=
rocmail" style=3D"font-family:arial">http://unixhelp.ed.ac.uk/CGI/man-cgi?p=
rocmail</a></div>
</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=3D"ltr"><d=
iv><font face=3D"tahoma,sans-serif"><strong><font color=3D"#3d85c6">Chaitan=
ya Dhareshwar</font></strong></font></div><div><strong><font color=3D"#3d85=
c6" face=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 Fri, Feb 28, 2014 at 3:19 PM, Ted Lem=
on <span dir=3D"ltr">&lt;<a href=3D"mailto:ted.lemon@nominum.com" target=3D=
"_blank">ted.lemon@nominum.com</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">
On Feb 28, 2014, at 8:08 AM, Randy Bush &lt;<a href=3D"mailto:randy@psg.com=
">randy@psg.com</a>&gt; wrote:<br>
&gt; man procmail<br>
<br>
Can&#39;t. =A0 :(<br>
<br>
</blockquote></div><br></div>

--001a11c16dfccb02a004f37678b6--


From nobody Fri Feb 28 04:31:42 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 86F7A1A0285 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 04:31:39 -0800 (PST)
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 5xaSZqXSNPOx for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 04:31:35 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.145]) by ietfa.amsl.com (Postfix) with ESMTP id DC9781A025E for <ietf@ietf.org>; Fri, 28 Feb 2014 04:31:34 -0800 (PST)
Received: from [195.245.231.67:45716] by server-9.bemta-5.messagelabs.com id 76/5A-11237-4A180135; Fri, 28 Feb 2014 12:31:32 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-11.tower-82.messagelabs.com!1393590691!26170022!1
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 5861 invoked from network); 28 Feb 2014 12:31:32 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-11.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 28 Feb 2014 12:31:32 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT021P.surrey.ac.uk ([131.227.200.35]) with mapi; Fri, 28 Feb 2014 12:31:31 +0000
From: <l.wood@surrey.ac.uk>
To: <chaitanyabd@gmail.com>, <ted.lemon@nominum.com>
Date: Fri, 28 Feb 2014 12:28:38 +0000
Subject: RE: Clarifying IETF process [Was: A private club]
Thread-Topic: Clarifying IETF process [Was: A private club]
Thread-Index: Ac80f9/Ub0S4BvzcR62zF4kso9DdzgAALu14
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334740@EXMB01CMS.surrey.ac.uk>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com>, <CAEP5zKRhpzhFT293cngvzf65AsdgS6A6f=K-HneDJbJHSbN1DA@mail.gmail.com>
In-Reply-To: <CAEP5zKRhpzhFT293cngvzf65AsdgS6A6f=K-HneDJbJHSbN1DA@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/YkNq-77_4xkroX5XvrU5atskYmg
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, 28 Feb 2014 12:31:39 -0000

For an Area Director and IESG member, reading IETF mail, not discarding it =
unread, is one of the responsibilities of the role.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: ietf [ietf-bounces@ietf.org] On Behalf Of Chaitanya Dhareshwar [chait=
anyabd@gmail.com]
Sent: 28 February 2014 12:21
To: Ted Lemon
Cc: IETF Disgust
Subject: Re: Clarifying IETF process [Was: A private club]

Try http://www.gsp.com/cgi-bin/man.cgi?topic=3Dprocmailrc or http://unixhel=
p.ed.ac.uk/CGI/man-cgi?procmail

Chaitanya Dhareshwar

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


On Fri, Feb 28, 2014 at 3:19 PM, Ted Lemon <ted.lemon@nominum.com<mailto:te=
d.lemon@nominum.com>> wrote:
On Feb 28, 2014, at 8:08 AM, Randy Bush <randy@psg.com<mailto:randy@psg.com=
>> wrote:
> man procmail

Can't.   :(



From nobody Fri Feb 28 04:54:49 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 466DB1A023D for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 04:54:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.448
X-Spam-Level: 
X-Spam-Status: No, score=-7.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6QPjozB6IRie for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 04:54:47 -0800 (PST)
Received: from e8.ny.us.ibm.com (e8.ny.us.ibm.com [32.97.182.138]) by ietfa.amsl.com (Postfix) with ESMTP id 0E64C1A0241 for <ietf@ietf.org>; Fri, 28 Feb 2014 04:54:46 -0800 (PST)
Received: from /spool/local by e8.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, 28 Feb 2014 07:54:45 -0500
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e8.ny.us.ibm.com (192.168.1.108) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 28 Feb 2014 07:54:43 -0500
Received: from b01cxnp22035.gho.pok.ibm.com (b01cxnp22035.gho.pok.ibm.com [9.57.198.25]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id B0B4F38C803D for <ietf@ietf.org>; Fri, 28 Feb 2014 07:54:42 -0500 (EST)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by b01cxnp22035.gho.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1SCsg4E3932628 for <ietf@ietf.org>; Fri, 28 Feb 2014 12:54:42 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 s1SCsg9A019062 for <ietf@ietf.org>; Fri, 28 Feb 2014 07:54:42 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-49-141-170.mts.ibm.com [9.49.141.170]) by d01av01.pok.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s1SCseex018996 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 28 Feb 2014 07:54:41 -0500
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s1SCsdaO006218; Fri, 28 Feb 2014 07:54:39 -0500
Date: Fri, 28 Feb 2014 07:54:39 -0500
Message-ID: <m3ha7jmm7k.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: <l.wood@surrey.ac.uk>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334740@EXMB01CMS.surrey.ac.uk>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14022812-0320-0000-0000-000002921EE4
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/7y2rml_Ljd5cy6z_QNw_c3ZRF9s
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, 28 Feb 2014 12:54:48 -0000

> For an Area Director and IESG member, reading IETF mail, not
> discarding it unread, is one of the responsibilities of the role.

This is a blanket statement that I cannot support.

IESG members (as well as IETFers in general) need to be smart about
using their limited cycles. They do not have cycles to read every
piece of email and read every document that they are "responsible"
for. 

Reading every piece of IETF email definitely is not prioritizing
resources properly. Indeed, it is not uncommon to see threads that
exhibit properties often associated with DOS attacks.

Thomas


From nobody Fri Feb 28 05:21:20 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 91C181A0252 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 05:21:17 -0800 (PST)
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 tIkVzgMNL2Jq for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 05:21:15 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.139]) by ietfa.amsl.com (Postfix) with ESMTP id 0AFF51A0154 for <ietf@ietf.org>; Fri, 28 Feb 2014 05:21:14 -0800 (PST)
Received: from [85.158.136.51:19385] by server-3.bemta-5.messagelabs.com id 72/51-13671-84D80135; Fri, 28 Feb 2014 13:21:12 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-2.tower-49.messagelabs.com!1393593672!21259618!1
X-Originating-IP: [131.227.200.43]
X-StarScan-Received: 
X-StarScan-Version: 6.9.16; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 25518 invoked from network); 28 Feb 2014 13:21:12 -0000
Received: from exht022p.surrey.ac.uk (HELO EXHT022P.surrey.ac.uk) (131.227.200.43) by server-2.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 28 Feb 2014 13:21:12 -0000
Received: from EXMB01CMS.surrey.ac.uk ([169.254.1.204]) by EXHT022P.surrey.ac.uk ([131.227.200.43]) with mapi; Fri, 28 Feb 2014 13:21:11 +0000
From: <l.wood@surrey.ac.uk>
To: <narten@us.ibm.com>
Date: Fri, 28 Feb 2014 13:19:43 +0000
Subject: RE: Clarifying IETF process [Was: A private club]
Thread-Topic: Clarifying IETF process [Was: A private club]
Thread-Index: Ac80hEOiTGC4ZEhDRU2G8+htYFcVXgAA3q8I
Message-ID: <290E20B455C66743BE178C5C84F1240847E6334741@EXMB01CMS.surrey.ac.uk>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi>	<20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com>, <m3ha7jmm7k.wl%narten@us.ibm.com>
In-Reply-To: <m3ha7jmm7k.wl%narten@us.ibm.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/LDQ5R9U8Rkzp58U5Mo-I2ygnob4
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, 28 Feb 2014 13:21:17 -0000

I didn't say reading _all_ IETF mail.

But 'don't miss stuff' is a maxim. And filters can be blinders.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: Thomas Narten [narten@us.ibm.com]
Sent: 28 February 2014 12:54
To: Wood L  Dr (Electronic Eng)
Cc: chaitanyabd@gmail.com; ted.lemon@nominum.com; ietf@ietf.org
Subject: Re: Clarifying IETF process [Was: A private club]

> For an Area Director and IESG member, reading IETF mail, not
> discarding it unread, is one of the responsibilities of the role.

This is a blanket statement that I cannot support.

IESG members (as well as IETFers in general) need to be smart about
using their limited cycles. They do not have cycles to read every
piece of email and read every document that they are "responsible"
for.

Reading every piece of IETF email definitely is not prioritizing
resources properly. Indeed, it is not uncommon to see threads that
exhibit properties often associated with DOS attacks.

Thomas


From nobody Fri Feb 28 07:17:15 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 834C91A0824 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:17:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yGuC3Ao6FNBJ for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:17:10 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id 842C31A02AE for <ietf@ietf.org>; Fri, 28 Feb 2014 07:17:10 -0800 (PST)
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 2A8571B80EA for <ietf@ietf.org>; Fri, 28 Feb 2014 07:17:08 -0800 (PST)
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 0EBA4190043; Fri, 28 Feb 2014 07:17:08 -0800 (PST)
Received: from [130.129.154.206] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 28 Feb 2014 07:17:07 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Clarifying IETF process [Was: A private club]
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <m3ha7jmm7k.wl%narten@us.ibm.com>
Date: Fri, 28 Feb 2014 15:17:03 +0000
Content-Transfer-Encoding: 7bit
Message-ID: <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <m3ha7jmm7k.wl%narten@us.ibm.com>
To: Thomas Narten <narten@us.ibm.com>
X-Mailer: Apple Mail (2.1874)
X-Originating-IP: [192.168.1.10]
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/1zwmETRG9wygP3AeAathiCuIDds
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, 28 Feb 2014 15:17:12 -0000

On Feb 28, 2014, at 12:54 PM, Thomas Narten <narten@us.ibm.com> wrote:
> Reading every piece of IETF email definitely is not prioritizing
> resources properly. Indeed, it is not uncommon to see threads that
> exhibit properties often associated with DOS attacks.

+1

Nevertheless, procmail doesn't seem like the right answer.


From nobody Fri Feb 28 07:18:06 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 0AC981A083C for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:18:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DgU38-q_cnwu for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:18:01 -0800 (PST)
Received: from shell-too.nominum.com (shell-too.nominum.com [64.89.228.229]) by ietfa.amsl.com (Postfix) with ESMTP id BFF241A02BD for <ietf@ietf.org>; Fri, 28 Feb 2014 07:18:01 -0800 (PST)
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 2380F1B80CC for <ietf@ietf.org>; Fri, 28 Feb 2014 07:18:00 -0800 (PST)
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 1B565190043; Fri, 28 Feb 2014 07:18:00 -0800 (PST)
Received: from [130.129.154.206] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 28 Feb 2014 07:17:59 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
Subject: Re: Clarifying IETF process [Was: A private club]
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <290E20B455C66743BE178C5C84F1240847E6334741@EXMB01CMS.surrey.ac.uk>
Date: Fri, 28 Feb 2014 15:17:57 +0000
Content-Transfer-Encoding: quoted-printable
Message-ID: <E37FFD4A-7CE3-4725-94B5-C8033B53ADF1@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi>	<20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com>, <m3ha7jmm7k.wl%narten@us.ibm.com> <290E20B455C66743BE178C5C84F1240847E6334741@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/3VI56RvbHEV5TXWcqJfkuHf2V1c
Cc: narten@us.ibm.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, 28 Feb 2014 15:18:04 -0000

On Feb 28, 2014, at 1:19 PM, l.wood@surrey.ac.uk wrote:
> But 'don't miss stuff' is a maxim.

I've never heard it before.   It's unattainable.   We all miss stuff.   =
If you think we've missed something important, please say so.


From nobody Fri Feb 28 07:22:41 2014
Return-Path: <juliao@braga.eti.br>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65BDA1A0832 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:22:39 -0800 (PST)
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] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EeH5hsovzXqq for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:22:37 -0800 (PST)
Received: from mail-yh0-f44.google.com (mail-yh0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id 2880A1A02FD for <ietf@ietf.org>; Fri, 28 Feb 2014 07:22:37 -0800 (PST)
Received: by mail-yh0-f44.google.com with SMTP id f73so823160yha.31 for <ietf@ietf.org>; Fri, 28 Feb 2014 07:22:35 -0800 (PST)
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:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=qVoJk+Ddw8x4xZBfK/6RKczZcVmprYTGtA2DoyHJ+CE=; b=H8fGh3VDPc2s+dNuNz/dY5DtOm/626ofFjKwpCMt+wnaksyXASuiMThsUjESfUgY6a lsjDSByArT6i1rLFbA6Ia6IgrJPI5YAJv3vPdUmsI4M7Z1/LHNuVlnkJXDWsyv3qsSZE DANVaZ/n+KnI0Zi05J8/A1M5mGU4uwygJ7eAni4oEAWV18mPdWsDS2nKVKc96VZbwa97 4QplnwEbpaBIYbPe+G6X0U+7ERcKtQWsq1SQMNnY5Yu1DcHzzVR388qoKqyZ4S6H/FX4 PECED9jtsYRSiu4zeCO0BDfBT6nP9SBANaFZWpCMgWvXZCKN7aWP0MHHh3X02MKgGytO /hsw==
X-Gm-Message-State: ALoCoQkhrw2OEiNKwO2nxtkV/JyhmubaLhvVmPbumQ54dcIzqUECJ3P35sXzH0eptTUFFp4iexNM
X-Received: by 10.236.93.208 with SMTP id l56mr2402588yhf.112.1393600955079; Fri, 28 Feb 2014 07:22:35 -0800 (PST)
Received: from ?IPv6:2001:1294:1295:1295::167? ([2001:1294:1295:1295::167]) by mx.google.com with ESMTPSA id 23sm6637049yhj.5.2014.02.28.07.22.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 28 Feb 2014 07:22:34 -0800 (PST)
Message-ID: <5310A9B6.10301@braga.eti.br>
Date: Fri, 28 Feb 2014 12:22:30 -0300
From: Juliao Braga <juliao@braga.eti.br>
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: Clarifying IETF process [Was: A private club]
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <m3ha7jmm7k.wl%narten@us.ibm.com>
In-Reply-To: <m3ha7jmm7k.wl%narten@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/w0G_TgoInVqBOi2ZfqjbaFhGKj4
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2014 15:22:39 -0000

I think one of the fundamental ability to an Area Director and IESG
member is read diagonally. Exactly how we do as responsible members of
the IETF.

So is possible to capture the relevant information.

[]s, Julião

Em 28/02/2014 09:54, Thomas Narten escreveu:
>> For an Area Director and IESG member, reading IETF mail, not
>> discarding it unread, is one of the responsibilities of the role.
> 
> This is a blanket statement that I cannot support.
> 
> IESG members (as well as IETFers in general) need to be smart about
> using their limited cycles. They do not have cycles to read every
> piece of email and read every document that they are "responsible"
> for. 
> 
> Reading every piece of IETF email definitely is not prioritizing
> resources properly. Indeed, it is not uncommon to see threads that
> exhibit properties often associated with DOS attacks.
> 
> Thomas
> 
> 


From nobody Fri Feb 28 07:28:49 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 DA6BE1A083B for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:28:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.689
X-Spam-Level: *
X-Spam-Status: No, score=1.689 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.547, 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 mxaUSbqlzrc4 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:28:44 -0800 (PST)
Received: from cdpipgw01.twcable.com (cdpipgw01.twcable.com [165.237.59.22]) by ietfa.amsl.com (Postfix) with ESMTP id EFC281A02DD for <ietf@ietf.org>; Fri, 28 Feb 2014 07:28:43 -0800 (PST)
X-SENDER-IP: 10.136.163.15
X-SENDER-REPUTATION: None
X-IronPort-AV: E=Sophos;i="4.97,562,1389762000";  d="scan'208,217";a="206579113"
Received: from unknown (HELO PRVPEXHUB06.corp.twcable.com) ([10.136.163.15]) by cdpipgw01.twcable.com with ESMTP/TLS/RC4-MD5; 28 Feb 2014 10:27:03 -0500
Received: from PRVPEXVS15.corp.twcable.com ([10.136.163.78]) by PRVPEXHUB06.corp.twcable.com ([10.136.163.15]) with mapi; Fri, 28 Feb 2014 10:27:04 -0500
From: "George, Wes" <wesley.george@twcable.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Date: Fri, 28 Feb 2014 10:27:03 -0500
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Topic: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
Thread-Index: Ac80mYhJaJ8e00KnQP+3EJinl6aQUQ==
Message-ID: <CF35F90C.120C7%wesley.george@twcable.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com> <CADnDZ8_ZgDp-rWETgdMp7o+XXVXcHv2B58h-Pon=5xmgi0e8uQ@mail.gmail.com>
In-Reply-To: <CADnDZ8_ZgDp-rWETgdMp7o+XXVXcHv2B58h-Pon=5xmgi0e8uQ@mail.gmail.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_CF35F90C120C7wesleygeorgetwcablecom_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/6vJ3e3DR0ARDyom52EiPRHakd1c
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, 28 Feb 2014 15:28:47 -0000

--_000_CF35F90C120C7wesleygeorgetwcablecom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RnJvbTogQWJkdXNzYWxhbSBCYXJ5dW4gPGFiZHVzc2FsYW1iYXJ5dW5AZ21haWwuY29tPG1haWx0
bzphYmR1c3NhbGFtYmFyeXVuQGdtYWlsLmNvbT4+DQoNClJlbW90ZSBwYXJ0aWNpcGFudHMgZG8g
ZXhwZXJpZW5jZSBtZWV0aW5ncyBhcyBmMmYgcGFydGljaXBhbnRzIGRvLg0KDQpXR10gSWYgb25l
IHN0cmljdGx5IGNvbnNpZGVycyBhZ2VuZGEgYW5kIHByZXNlbnRhdGlvbiBkaXNjdXNzaW9uIHdp
dGhpbiBhIFdHIG1lZXRpbmcsIHRoYXQgc3RhdGVtZW50IGlzIGJhc2ljYWxseSB0cnVlLiBIb3dl
dmVyLCBhcyBzb21lb25lIHdobyB1c3VhbGx5IGF0dGVuZHMgaW4gcGVyc29uIGJ1dCBoYXMgaGFk
IHRvIHBhcnRpY2lwYXRlIHJlbW90ZWx5IGluIHRoZSBwYXN0IGFuZCB0aGVyZWZvcmUgY2FuIGRp
cmVjdGx5IGNvbXBhcmUgdGhlIHR3bywgSSBub3RlIHRoYXQgd2hlbiB0YWtlbiBvbiB0aGUgd2hv
bGUsIG15IGV4cGVyaWVuY2UgZm9yIG1lZXRpbmcgYXR0ZW5kYW5jZSByZW1vdGVseSB2cyBpbiBw
ZXJzb24gd2FzIHZhc3RseSBkaWZmZXJlbnQuDQoNCg0KIFRoZSBxdWVzdGlvbiB3YXMgbm90IHJl
bGV2YW50LCBiZWNhdXNlIGl0IGFzc3VtZXMgdGhhdCB0aGVyZSBpcyBubyBwcm9ibGVtIGluIElF
VEYgbWVldGluZ3MgYW5kIGFzc3VtZXMgdGhhdCB0aGUgaW1wcm92ZW1lbnQgaXMgbmVlZGVkIGlu
IHRoZSBwb3N0ZXIgcGFydGljaXBhbnQgc2lkZSAodGhhdCBtYXkgbWFrZSBpdCBwZXJzb25hbCB3
aGVuIG9uZSBpcyBkaXN0dXJiaW5nIGFub3RoZXIgbWFueSB0aW1lcykuDQoNCldHXSBJIGRpc2Fn
cmVlLiBUaGVyZSBoYXMgYmVlbiBzaWduaWZpY2FudCB2aXJ0dWFsIGluayB3YXN0ZWQgb24gZGlz
Y3Vzc2luZyBJRVRG4oCZcyBwcm9ibGVtcyBpbiBtZWV0aW5ncyBvZiDigJxwcmVzZW50aW5n4oCd
IGEgZHJhZnQgZm9yIGZvbGtzIHdobyBoYXZlbuKAmXQgcmVhZCBpdCBpbnN0ZWFkIG9mIGRpc2N1
c3NpbmcgYW5kIHJlc29sdmluZyBpc3N1ZXMgdGhhdCBtdXN0IGJlIGFkZHJlc3NlZCBmb3IgdGhl
IGRyYWZ0IHRvIG1ha2UgZm9yd2FyZCBwcm9ncmVzcy4gSSBhZG1pdCB0aGF0IHRoZSBxdWVzdGlv
biBtYXkgaGF2ZSBiZWVuIGN1cnRseSBwaHJhc2VkLCBidXQgaXTigJlzIHBlcmZlY3RseSBsZWdp
dGltYXRlIHRvIGFzayDigJx3aHkgZG8geW91IHRoaW5rIHRoYXQgdGhpcyBpcyBhIGdvb2QgaWRl
YT/igJ0gd2hlbiBldmFsdWF0aW5nIGEgc2VlbWluZ2x5IGFyYml0cmFyeSBzdWdnZXN0aW9uIHN1
Y2ggYXMgdGhpcywgZXNwZWNpYWxseSB3aGVuIHRoZSBzdWdnZXN0aW9uIGlzIGFic2VudCBtdWNo
IGluIHRoZSB3YXkgb2YganVzdGlmaWNhdGlvbi4gU2luY2UgdGhpcyB3YXMgZGlyZWN0bHkgcmVs
YXRlZCB0byBtZWV0aW5nIGZsb3csIG9uZeKAmXMgZXhwZXJpZW5jZSB3aXRoaW4gV0cgbWVldGlu
Z3MgaXMgcmVsZXZhbnQsIGFzIHN1cmVseSBhcyBvbmXigJlzIGV4cGVyaWVuY2UgYW5kIGtub3ds
ZWRnZSBvZiBCR1AgY29tZXMgaW50byBwbGF5IHdoZW4gZXZhbHVhdGluZyBhIHN1Z2dlc3Rpb24g
dG8gYSBCR1AgZHJhZnQsIG9yIG9uZeKAmXMgZXhwZXJpZW5jZSB3aXRoIElFVEYgcHJvY2VzcyB3
aGVuIHN1Z2dlc3RpbmcgcHJvY2VzcyBjaGFuZ2VzLg0KDQoNCkFsbCBQZW9wbGUgaGF2ZSByaWdo
dHMgYW5kIHJpZ2h0IHRvIHNwZWFrLCBidXQgbm8gbmVlZCBmb3IgbWFraW5nIGl0IGxvb2sgZnVu
bnkgd2hlbiB0aGUgcG9zdGVyIGlzIG5ldyBjb21lciBvciBzdGlsbCBoYWQgbm8gUkZDLiBJZiB5
b3Ugc2F5IHdoYXQgaXMgeW91ciBleHBlcmllbmNlIHRvIHNvbWUgb25lIG5ldyBvZiAyIHllYXJz
IGFuZCBoYWQgbm8gUkZDLCB0aGF0IHF1ZXN0aW9uIHdpbGwgYmUgbGlrZSBuZXcgY29tZXIgaGF2
ZSBub3Qgc2FtZSByaWdodCBhcyBvbGQgY29tZXIgdG8gU3BlYWsuIE1lbGluZGEgb25jZSBtZW50
aW9uIGFzIHRvIGdldCB0ZWNobmljYWwgd29yayBkb25lIHRvIGdldCByZWNvZ25pc2UsIGJ1dCBt
eSBvcGluaW9uIGlzIHRoYXQgdGhpcyB3YXkgb2YgdGhpbmtpbmcgdG8gZXhjbHVkZSBuZXcgcGVv
cGxlIHVudGlsIHRoZXkgZG8gUkZDIG9yIGRvIGYyZiBhdHRlbmRhbmNlLCBpcyBiYWQgZm9yIElF
VEYuDQoNCldHXSBZZXMsIGFsbCBoYXZlIGEgcmlnaHQgdG8gc3BlYWsuIEJ1dCBJRVRGLCBsaWtl
IG1hbnkgZ3JvdXBzIG9mIGVuZ2luZWVycywgaXMgcHJpbWFyaWx5IG1lcml0LWJhc2VkLiBBbGwg
c3RhcnQgd2l0aCBlZmZlY3RpdmVseSB6ZXJvIGNyZWRpYmlsaXR5LCBhbmQgYnVpbGQgdGhhdCB1
cCBvdmVyIHRpbWUgYnkgcHJvdmlkaW5nIHVzZWZ1bCAocXVhbGl0eSwgcmF0aGVyIHRoYW4gcXVh
bnRpdHkpIGZlZWRiYWNrIGluIGFyZWFzIHdoZXJlIHRoZXkgaGF2ZSBleHBlcnRpc2UuIEFsbCBz
aG91bGQgYWxzbyBxdWlja2x5IGxlYXJuIG5vdCB0byBiZSBvZmZlbmRlZCB3aGVuIHNvbWVvbmUg
c2F5cyB0aGF0IHRoZSBzdWdnZXN0aW9uIGlzIGEgYmFkIG9uZSwgb3IgZG9lcyBub3QgaW1tZWRp
YXRlbHkgaW1wbGVtZW50IGl0LiBUaGUgbWlzdGFrZSB5b3UgbWFrZSwgQUIsIGlzIHRvIGFzc3Vt
ZSB0aGF0IHNpbXBseSBiZWNhdXNlIHNvbWVvbmUgcXVlc3Rpb25lZCB3aHkgeW91IHRob3VnaHQg
eW91ciBzdWdnZXN0aW9uIHdhcyBhIGdvb2Qgb25lIGJ5IGFza2luZyBhYm91dCB5b3VyIGV4cGVy
aWVuY2UsIHRoYXQgdGhlIHF1ZXN0aW9uIHdhcyBhYm91dCBzaHV0dGluZyBvdXQgYSBuZXdjb21l
ciwgb3IgaW50ZW5kZWQgdG8gaW1wbHkgdGhhdCB5b3XigJlyZSBzb21laG93IGEgYmFkIHBlcnNv
biBiZWNhdXNlIHlvdSBtYWRlIGEgcG9vcmx5IHRob3VnaHQtb3V0IGFuZCBwb29ybHkganVzdGlm
aWVkIHN1Z2dlc3Rpb24gb2YgYSBibGFua2V0IGNoYW5nZSB0byBtZWV0aW5nIGZsb3cuDQoNCg0K
SWYgdGhlIHF1ZXN0aW9uIHdhcyB0aGUgZmlyc3QgY29udmVyc2F0aW9uIGJldHdlZW4gdHdvIHBh
cnRpY2lwYW50cyBpbiBJRVRGIHRoZW4geW91IGFyZSByaWdodC4gVGhhdCB3YXMgbm90IHRoZSBj
YXNlLCB0aGUgY2FzZSB3YXMgb25lIHBlcnNvbiBkb2luZyBBZCBob21lbmltZXMgdG8gYSBuZXcg
Y29tZXIgZm9yIG1hbnkgdGltZSwgdGhlbiB0aGF0IG5ldyBjb21lciByZXBvcnRlZCBjYXNlcyB0
byBJRVRGIGNoYWlyIGFuZCB0byBBRHMuIEFmdGVyIHRoYXQgd2hlbiB0aGUgbmV3IGNvbWVyIHdp
bGwgc2hvdyB1cCBhZnRlciBsYXJnZSBwYXRpZW50cywgYW5kIG1hZGUgYSBzdWdnZXN0aW9uLCB0
aGF0IEFkIGhvbWVuaW1lIHBlcnNvbiBjb250aW51ZXMgdG8gZGlzY291cmFnZSB0aGUgbmV3IGNv
bWVyLg0KDQpXR10gVGhlcmXigJlzIGEgY2hhcmFjdGVyLCBJbmlnbyBNb250b3lhLCBpbiBhIFVT
IG1vdmllIGNhbGxlZCDigJxUaGUgUHJpbmNlc3MgQnJpZGXigJ0gd2hvIG1ha2VzIGEgc3RhdGVt
ZW50IGluIHRoZSBtb3ZpZSB0aGF0IHNvbWUgcGFydHMgb2YgdGhlIGludGVybmV0IGFyZSBmb25k
IG9mIHF1b3RpbmcgZHVyaW5nIGFyZ3VtZW50cywg4oCceW91IGtlZXAgdXNpbmcgdGhhdCB3b3Jk
4oCmIEkgZG8gbm90IHRoaW5rIGl0IG1lYW5zIHdoYXQgeW91IHRoaW5rIGl0IGRvZXMu4oCdIEFz
IHlvdSBjYW4gc2VlIGZyb20gdGhlIGRpc2N1c3Npb24gb24gdGhpcyB0aHJlYWQsIGV2ZW4gd2l0
aCBnb29kIGRlZmluaXRpb25zIG9mIGFkIGhvbWluZW0sIHdlIGRvbuKAmXQgaGF2ZSBhbnkgc29y
dCBvZiBhZ3JlZW1lbnQgdGhhdCB0aGUgcmVzcG9uc2UgaW4gcXVlc3Rpb24gd2FzIGluZGVlZCBh
biBhZCBob21pbmVtIGF0dGFjayBvbiB5b3UsIGFuZCBJIGNhbuKAmXQgcmVhbGx5IHNwZWFrIHRv
IGFueSBvZiB0aGUgcHJldmlvdXMgaW5jaWRlbnRzIEkgdGhpbmsgeW914oCZcmUgdmFndWVseSBy
ZWZlcmVuY2luZyBoZXJlIGJlY2F1c2UgSSBkb27igJl0IGhhdmUgYW55IHBlcnNvbmFsIGtub3ds
ZWRnZSBvZiB0aGUgY2lyY3Vtc3RhbmNlcy4NCg0KDQpJRVRGIGlzIHJlc3BvbnNpYmxlIHRvIHNv
bHZlIHRoaXMgcGVyc29uYWwgZXhwZXJpZW5jZSBhbnN3ZXJpbmcsIG5vdCBhbnkgcGFydGljaXBh
bnQuIEp1c3QgYmVjYXVzZSBvbmUgcGVyc29uIGlzIGtub3duIG9yIHdlbGNvbWVkIHRoYXQgc2hv
dWxkIG5vdCBtZWFuIGV4cGVyaWVuY2UuIEp1c3QgYmVjYXVzZSBvbmUgcGVyc29uIGhhcyBhbiBS
RkMgb3IgbWFueSBSRkNzLCB0aGF0IGRvZXMgbm90IG1lYW4gdGhleSBjYW4gZG8gQWQgaG9taW5l
bXMuDQoNCldHXSB0aGlzIGlzbuKAmXQgYWJvdXQgZXhwZXJpZW5jZS4gVGhpcyBpcyBhYm91dCBj
cmVkaWJpbGl0eSwgYXMgd2VsbCBhcyBnb29kIGlkZWFzIHZzIGJhZCBvbmVzLCBhbmQgaG93IHRo
ZXkgYXJlIHByZXNlbnRlZC4gV2hlbiBwZW9wbGUgcXVlc3Rpb24gYW4gdW5rbm93biAodG8gdGhl
bSkgcGVyc29uJ3MgZXhwZXJpZW5jZSB3aXRoaW4gSUVURiwgdGhleeKAmXJlIG9mdGVuIGRvaW5n
IGl0IGluIG9yZGVyIHRvIHRyeSB0byBnaXZlIHlvdSB0aGUgYmVuZWZpdCBvZiB0aGUgZG91YnQg
KEkuZS4gQmUgcGF0aWVudCBhbmQgZ2l2ZSBndWlkYW5jZSB3aGlsZSBhIG5ldyBwZXJzb24gbGVh
cm5zKS4gSSBwZXJzb25hbGx5IGhhdmUgYmVlbiB0aGUgYmVuZWZpY2lhcnkgb2YgdGhhdCBtYW55
IHRpbWVzLCBmcm9tIG1hbnkgZXhwZXJpZW5jZWQgcGFydGljaXBhbnRzLCBib3RoIG9uLWxpc3Qg
YW5kIG9mZiwgYW5kIGJvdGggaW4gbWF0dGVycyBvZiB0ZWNobm9sb2d5IGFuZCBpbiBJRVRGIHBy
b2Nlc3MgYW5kIGN1bHR1cmUuIEhvd2V2ZXIsIGJhc2VkIG9uIHlvdXIgcHJldmlvdXMgcG9zdHMg
dG8gdGhpcyBsaXN0LCBhbmQgbWFueSBkaWZmZXJlbnQgcGFydGljaXBhbnRz4oCZIHJlcGxpZXMg
dG8geW91LCB5b3Ugc2VlbSB0byBiZSB2ZXJ5IHF1aWNrIHRvIGJlIG9mZmVuZGVkIGJ5IHRoaXMg
YXMgYSBwZXJjZWl2ZWQgc2xpZ2h0LCByYXRoZXIgdGhhbiB3aWxsaW5nIHRvIGF2YWlsIHlvdXJz
ZWxmIG9mIHRoZSBwYXRpZW5jZSBhbmQgZ3VpZGFuY2Ugb2ZmZXJlZCBhbmQgbW9yZSBpbXBvcnRh
bnRseSwgY2hhbmdlIHlvdXIgbWV0aG9kcyBpbiByZXNwb25zZSB0byB0aGF0IGd1aWRhbmNlLg0K
DQoNCkkgYW0gdmVyeSBzb3JyeSBidXQgaXQgbG9va3Mgbm93IGJldHRlciBmb3IgbWUgdG8gbGVh
dmUgdGhlIElFVEYgbGlzdCBkaXNjdXNzaW9uIChleGNsdWRpbmcgTEMgY29tbWVudHMgYW5kIFJl
dmlldykgZm9yIHNvbWUgdGltZSBiZWNhdXNlIHRoaXMgbGlzdCBzZWVtcyB3aXRoIG5vIGV4cGVy
aWVuY2UgaG93IHRvIGRlYWwgd2l0aCBuZXcgY29tZXJzLA0KIFdHXSBJIGFncmVlIHdpdGggdGhl
IGZpcnN0IHN0YXRlbWVudCwgYnV0IG5vdCB0aGUgc2Vjb25kLiBBZnRlciAyIHllYXJzLCB5b3Xi
gJlyZSBub3QgcmVhbGx5IGEgbmV3Y29tZXIgYW55bW9yZSwgYXJlIHlvdT8NCg0KDQphbmQgSSB3
aWxsIHdvcmsgaGFyZCBvbiBTdW5kYXkgdG8gZGlzdHJpYnV0ZSB0aGUgbWVzc2FnZSB0byBhbGwg
bmV3IGNvbWVycyB0aGF0IHRoaXMgbGlzdCBpcyBkYW5nZXJvdXMgbGlzdCBmb3IgbmV3IGNvbWVy
cy4gSSBtYXkgYWxzbyBqdXN0IG1ha2UgYSBxdWVzdGlvbiBhbmQgY29tbWVudCBpbiB0aGUgdHV0
b3JpYWwgZm9yIG5ldyBjb21lcnMuIEkgZGlkIGVuam95IHBvc3Rpbmcgb24gdGhpcyBsaXN0IGJl
Y2F1c2UgdGhlcmUgYXJlIHNvbWUgZ3JlYXQgcGVvcGxlIEkgbm90aWNlZCwgYnV0IEkgd2lsbCBz
dG9wIGZvciBzb21lIHRpbWUgZm9yIHRoZSBsaXN0IHRvIHRoaW5rIGFib3V0IGl0cyBiZWhhdmlv
ci9wcm9ncmVzcyBhbmQgbmV3IGNvbWVycyB0aGluayBhYm91dCB0aGVpciBwcm9ncmVzcy4NCg0K
V0ddIEFuZCBhcyBub3RlZCBhYm92ZSwgdGhhdCBpcyBjZXJ0YWlubHkgeW91ciByaWdodCBhcyBh
IHBhcnRpY2lwYW50LiBIb3dldmVyLCBJIHNpbmNlcmVseSBob3BlIHRoYXQgbmV3Y29tZXJzIHdp
bGwgbm90IGhlZWQgdGhpcyAoYmFkKSBhZHZpY2UsIGFzIHlvdXIgZXhwZXJpZW5jZSBpcyBub3Qg
dHlwaWNhbCwgYW5kIEkgZmxhdGx5IHJlamVjdCB5b3VyIGFzc2VydGlvbiB0aGF0IHRoZSBJRVRG
IGFuZCB0aGUgd2F5IHRoYXQgaXRzIHBhcnRpY2lwYW50cyBoYXZlIHRyZWF0ZWQgeW91IGlzIHBy
aW1hcmlseSB0byBibGFtZSBmb3IgeW91ciBkaWZmaWN1bHRpZXMgaW4gcGFydGljaXBhdGluZyBp
biB0aGUgSUVURi4gTmV3Y29tZXJzIG9mdGVuIGhhdmUgZ3JlYXQgZmVlZGJhY2ssIGVzcGVjaWFs
bHkgcmVnYXJkaW5nIHRlY2huaWNhbCBpc3N1ZXMgYWJvdXQgd2hpY2ggdGhleSBoYXZlIGV4cGVy
dGlzZSwgYnV0IHRoZXkgc2hvdWxkIG5vdCBmZWVsIGRpc2NvdXJhZ2VkIGlmIHRoZWlyIGZlZWRi
YWNrIGlzIG5vdCBhbHdheXMgaW1wbGVtZW50ZWQgbm9yIGFzc3VtZSB0aGF0IHRoZSByZWFzb24g
dGhlaXIgZmVlZGJhY2sgaXMgbm90IGltcGxlbWVudGVkIGlzIGJlY2F1c2UgdGhleSBhcmUgYSBu
ZXdjb21lci4gIEZ1cnRoZXIsIHdoZW4gaXQgY29tZXMgdG8gSUVURiBwcm9jZXNzIGFuZCBjdWx0
dXJlLCBpdOKAmXMgaGFyZCBmb3IgZXZlbiBleHBlcmllbmNlZCBJRVRGZXJzIHRvIGVmZmVjdCBj
aGFuZ2UsIGV2ZW4gd2l0aCBnb29kLCB3ZWxsLWp1c3RpaWZpZWQgaWRlYXMgYmFzZWQgb24geWVh
cnMgb2YgZXhwZXJpZW5jZSB3aXRoaW4gdGhlIGV4aXN0aW5nIHByb2Nlc3MgYW5kIGN1bHR1cmUs
IHNvIGluIHRoYXQgY2FzZSwgSXTigJlzIG5vdCBqdXN0IHlvdS4NCg0KSSB3aXNoIHlvdSBsdWNr
IGluIExvbmRvbiwgbWF5IGl0IGJlIGEgdmFsdWFibGUgbGVhcm5pbmcgZXhwZXJpZW5jZSBmb3Ig
eW91LCBhcyB3ZWxsIGFzIGFuIG9wcG9ydHVuaXR5IHRvIGZvcmdlIHNvbWUgZ29vZCB3b3JraW5n
IHJlbGF0aW9uc2hpcHMgd2l0aCBvdGhlciBwYXJ0aWNpcGFudHMuDQoNCldlcyBHZW9yZ2UNCg0K
QW55dGhpbmcgYmVsb3cgdGhpcyBsaW5lIGhhcyBiZWVuIGFkZGVkIGJ5IG15IGNvbXBhbnnigJlz
IG1haWwgc2VydmVyLCBJIGhhdmUgbm8gY29udHJvbCBvdmVyIGl0Lg0KLS0tLS0tLS0tLS0NCg0K
DQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KVGhpcyBFLW1haWwgYW5kIGFueSBv
ZiBpdHMgYXR0YWNobWVudHMgbWF5IGNvbnRhaW4gVGltZSBXYXJuZXIgQ2FibGUgcHJvcHJpZXRh
cnkgaW5mb3JtYXRpb24sIHdoaWNoIGlzIHByaXZpbGVnZWQsIGNvbmZpZGVudGlhbCwgb3Igc3Vi
amVjdCB0byBjb3B5cmlnaHQgYmVsb25naW5nIHRvIFRpbWUgV2FybmVyIENhYmxlLiBUaGlzIEUt
bWFpbCBpcyBpbnRlbmRlZCBzb2xlbHkgZm9yIHRoZSB1c2Ugb2YgdGhlIGluZGl2aWR1YWwgb3Ig
ZW50aXR5IHRvIHdoaWNoIGl0IGlzIGFkZHJlc3NlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVu
ZGVkIHJlY2lwaWVudCBvZiB0aGlzIEUtbWFpbCwgeW91IGFyZSBoZXJlYnkgbm90aWZpZWQgdGhh
dCBhbnkgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBjb3B5aW5nLCBvciBhY3Rpb24gdGFr
ZW4gaW4gcmVsYXRpb24gdG8gdGhlIGNvbnRlbnRzIG9mIGFuZCBhdHRhY2htZW50cyB0byB0aGlz
IEUtbWFpbCBpcyBzdHJpY3RseSBwcm9oaWJpdGVkIGFuZCBtYXkgYmUgdW5sYXdmdWwuIElmIHlv
dSBoYXZlIHJlY2VpdmVkIHRoaXMgRS1tYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBz
ZW5kZXIgaW1tZWRpYXRlbHkgYW5kIHBlcm1hbmVudGx5IGRlbGV0ZSB0aGUgb3JpZ2luYWwgYW5k
IGFueSBjb3B5IG9mIHRoaXMgRS1tYWlsIGFuZCBhbnkgcHJpbnRvdXQuDQo=

--_000_CF35F90C120C7wesleygeorgetwcablecom_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgLXdlYmtpdC1saW5lLWJy
ZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsgY29sb3I6IHJnYigwLCAwLCAwKTsgZm9udC1zaXplOiAx
NHB4OyBmb250LWZhbWlseTogQ2FsaWJyaSwgc2Fucy1zZXJpZjsiPg0KPGRpdj4NCjxkaXY+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZTogMTFwdDsgZm9udC1mYW1pbHk6IENhbGlicmk7IGZvbnQtd2Vp
Z2h0OiBib2xkOyI+RnJvbToNCjwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxMXB0OyBm
b250LWZhbWlseTogQ2FsaWJyaTsiPkFiZHVzc2FsYW0gQmFyeXVuICZsdDs8L3NwYW4+PGEgaHJl
Zj0ibWFpbHRvOmFiZHVzc2FsYW1iYXJ5dW5AZ21haWwuY29tIiBzdHlsZT0iZm9udC1zaXplOiAx
MXB0OyBmb250LWZhbWlseTogQ2FsaWJyaTsiPmFiZHVzc2FsYW1iYXJ5dW5AZ21haWwuY29tPC9h
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDExcHQ7IGZvbnQtZmFtaWx5OiBDYWxpYnJpOyI+Jmd0
Ozwvc3Bhbj48L2Rpdj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+UmVtb3RlIHBhcnRpY2lwYW50
cyBkbyBleHBlcmllbmNlIG1lZXRpbmdzIGFzIGYyZiBwYXJ0aWNpcGFudHMgZG8uPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9zcGFuPg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+V0ddIElmIG9u
ZSBzdHJpY3RseSBjb25zaWRlcnMgYWdlbmRhIGFuZCBwcmVzZW50YXRpb24gZGlzY3Vzc2lvbiB3
aXRoaW4gYSBXRyBtZWV0aW5nLCB0aGF0IHN0YXRlbWVudCBpcyBiYXNpY2FsbHkgdHJ1ZS4gSG93
ZXZlciwgYXMgc29tZW9uZSB3aG8gdXN1YWxseSBhdHRlbmRzIGluIHBlcnNvbiBidXQgaGFzIGhh
ZCB0byBwYXJ0aWNpcGF0ZSByZW1vdGVseSBpbiB0aGUgcGFzdCBhbmQgdGhlcmVmb3JlIGNhbiBk
aXJlY3RseSBjb21wYXJlDQogdGhlIHR3bywgSSBub3RlIHRoYXQgd2hlbiB0YWtlbiBvbiB0aGUg
d2hvbGUsIG15IGV4cGVyaWVuY2UgZm9yIG1lZXRpbmcgYXR0ZW5kYW5jZSByZW1vdGVseSB2cyBp
biBwZXJzb24gd2FzIHZhc3RseSBkaWZmZXJlbnQuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0K
PGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+Jm5ic3A7VGhlIHF1ZXN0aW9uIHdhcyBub3QgcmVsZXZh
bnQsJm5ic3A7YmVjYXVzZSBpdCBhc3N1bWVzIHRoYXQgdGhlcmUgaXMgbm8gcHJvYmxlbSBpbiBJ
RVRGJm5ic3A7bWVldGluZ3MgYW5kIGFzc3VtZXMgdGhhdCB0aGUgaW1wcm92ZW1lbnQgaXMgbmVl
ZGVkIGluIHRoZSBwb3N0ZXIgcGFydGljaXBhbnQmbmJzcDtzaWRlICh0aGF0IG1heSBtYWtlIGl0
IHBlcnNvbmFsIHdoZW4gb25lIGlzIGRpc3R1cmJpbmcgYW5vdGhlciBtYW55IHRpbWVzKS4mbmJz
cDs8L2Rpdj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PldHXSBJIGRpc2FncmVlLiBUaGVyZSBo
YXMgYmVlbiBzaWduaWZpY2FudCB2aXJ0dWFsIGluayB3YXN0ZWQgb24gZGlzY3Vzc2luZyBJRVRG
4oCZcyBwcm9ibGVtcyBpbiBtZWV0aW5ncyBvZiDigJxwcmVzZW50aW5n4oCdIGEgZHJhZnQgZm9y
IGZvbGtzIHdobyBoYXZlbuKAmXQgcmVhZCBpdCBpbnN0ZWFkIG9mIGRpc2N1c3NpbmcgYW5kIHJl
c29sdmluZyBpc3N1ZXMgdGhhdCBtdXN0IGJlIGFkZHJlc3NlZCBmb3IgdGhlIGRyYWZ0IHRvIG1h
a2UgZm9yd2FyZA0KIHByb2dyZXNzLiBJIGFkbWl0IHRoYXQgdGhlIHF1ZXN0aW9uIG1heSBoYXZl
IGJlZW4gY3VydGx5IHBocmFzZWQsIGJ1dCBpdOKAmXMgcGVyZmVjdGx5IGxlZ2l0aW1hdGUgdG8g
YXNrIOKAnHdoeSBkbyB5b3UgdGhpbmsgdGhhdCB0aGlzIGlzIGEgZ29vZCBpZGVhP+KAnSB3aGVu
IGV2YWx1YXRpbmcgYSBzZWVtaW5nbHkgYXJiaXRyYXJ5IHN1Z2dlc3Rpb24gc3VjaCBhcyB0aGlz
LCBlc3BlY2lhbGx5IHdoZW4gdGhlIHN1Z2dlc3Rpb24gaXMgYWJzZW50IG11Y2gNCiBpbiB0aGUg
d2F5IG9mIGp1c3RpZmljYXRpb24uIFNpbmNlIHRoaXMgd2FzIGRpcmVjdGx5IHJlbGF0ZWQgdG8g
bWVldGluZyBmbG93LCBvbmXigJlzIGV4cGVyaWVuY2Ugd2l0aGluIFdHIG1lZXRpbmdzIGlzIHJl
bGV2YW50LCBhcyBzdXJlbHkgYXMgb25l4oCZcyBleHBlcmllbmNlIGFuZCBrbm93bGVkZ2Ugb2Yg
QkdQIGNvbWVzIGludG8gcGxheSB3aGVuIGV2YWx1YXRpbmcgYSBzdWdnZXN0aW9uIHRvIGEgQkdQ
IGRyYWZ0LCBvciBvbmXigJlzIGV4cGVyaWVuY2UNCiB3aXRoIElFVEYgcHJvY2VzcyB3aGVuIHN1
Z2dlc3RpbmcgcHJvY2VzcyBjaGFuZ2VzLiAmbmJzcDs8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JD
X0JPRFlfU0VDVElPTiI+DQo8ZGl2PjxzcGFuPjwvc3Bhbj48L2Rpdj4NCjxkaXY+PGJyPg0KPC9k
aXY+DQo8YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAg
LjhleDtib3JkZXItbGVmdDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxicj4N
CjwvYmxvY2txdW90ZT4NCjxkaXY+QWxsJm5ic3A7UGVvcGxlIGhhdmUgcmlnaHRzIGFuZCByaWdo
dCB0byBzcGVhaywmbmJzcDtidXQgbm8gbmVlZCBmb3IgbWFraW5nIGl0IGxvb2sgZnVubnkgd2hl
biB0aGUgcG9zdGVyIGlzIG5ldyBjb21lciBvciBzdGlsbCBoYWQgbm8gUkZDLiBJZiB5b3Ugc2F5
IHdoYXQgaXMgeW91ciBleHBlcmllbmNlIHRvIHNvbWUgb25lIG5ldyBvZiAyIHllYXJzIGFuZCBo
YWQgbm8gUkZDLCB0aGF0IHF1ZXN0aW9uJm5ic3A7d2lsbCBiZSBsaWtlIG5ldyBjb21lciBoYXZl
IG5vdA0KIHNhbWUgcmlnaHQgYXMgb2xkIGNvbWVyIHRvIFNwZWFrLiBNZWxpbmRhIG9uY2UgbWVu
dGlvbiBhcyB0byBnZXQgdGVjaG5pY2FsIHdvcmsgZG9uZSB0byBnZXQgcmVjb2duaXNlLCBidXQg
bXkgb3BpbmlvbiBpcyB0aGF0IHRoaXMgd2F5IG9mIHRoaW5raW5nIHRvIGV4Y2x1ZGUgbmV3IHBl
b3BsZSB1bnRpbCB0aGV5IGRvIFJGQyBvciBkbyBmMmYgYXR0ZW5kYW5jZSwmbmJzcDtpcyBiYWQg
Zm9yIElFVEYuPC9kaXY+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5XR10gWWVz
LCBhbGwgaGF2ZSBhIHJpZ2h0IHRvIHNwZWFrLiBCdXQgSUVURiwgbGlrZSBtYW55IGdyb3VwcyBv
ZiBlbmdpbmVlcnMsIGlzIHByaW1hcmlseSBtZXJpdC1iYXNlZC4gQWxsIHN0YXJ0IHdpdGggZWZm
ZWN0aXZlbHkgemVybyBjcmVkaWJpbGl0eSwgYW5kIGJ1aWxkIHRoYXQgdXAgb3ZlciB0aW1lIGJ5
IHByb3ZpZGluZyB1c2VmdWwgKHF1YWxpdHksIHJhdGhlciB0aGFuIHF1YW50aXR5KSBmZWVkYmFj
ayBpbiBhcmVhcyB3aGVyZQ0KIHRoZXkgaGF2ZSBleHBlcnRpc2UuIEFsbCBzaG91bGQgYWxzbyBx
dWlja2x5IGxlYXJuIG5vdCB0byBiZSBvZmZlbmRlZCB3aGVuIHNvbWVvbmUgc2F5cyB0aGF0IHRo
ZSBzdWdnZXN0aW9uIGlzIGEgYmFkIG9uZSwgb3IgZG9lcyBub3QgaW1tZWRpYXRlbHkgaW1wbGVt
ZW50IGl0LiBUaGUgbWlzdGFrZSB5b3UgbWFrZSwgQUIsIGlzIHRvIGFzc3VtZSB0aGF0IHNpbXBs
eSBiZWNhdXNlIHNvbWVvbmUgcXVlc3Rpb25lZCB3aHkgeW91IHRob3VnaHQgeW91cg0KIHN1Z2dl
c3Rpb24gd2FzIGEgZ29vZCBvbmUgYnkgYXNraW5nIGFib3V0IHlvdXIgZXhwZXJpZW5jZSwgdGhh
dCB0aGUgcXVlc3Rpb24gd2FzIGFib3V0IHNodXR0aW5nIG91dCBhIG5ld2NvbWVyLCBvciBpbnRl
bmRlZCB0byBpbXBseSB0aGF0IHlvdeKAmXJlIHNvbWVob3cgYSBiYWQgcGVyc29uIGJlY2F1c2Ug
eW91IG1hZGUgYSBwb29ybHkgdGhvdWdodC1vdXQgYW5kIHBvb3JseSBqdXN0aWZpZWQgc3VnZ2Vz
dGlvbiBvZiBhIGJsYW5rZXQgY2hhbmdlDQogdG8gbWVldGluZyBmbG93LjwvZGl2Pg0KPHNwYW4g
aWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXY+Jm5ic3A7PC9kaXY+DQo8YmxvY2txdW90
ZSBjbGFzcz0iZ21haWxfcXVvdGUiIHN0eWxlPSJtYXJnaW46MCAwIDAgLjhleDtib3JkZXItbGVm
dDoxcHggI2NjYyBzb2xpZDtwYWRkaW5nLWxlZnQ6MWV4Ij4NCjxicj4NCjwvYmxvY2txdW90ZT4N
CjxkaXY+SWYgdGhlIHF1ZXN0aW9uIHdhcyB0aGUgZmlyc3QgY29udmVyc2F0aW9uIGJldHdlZW4g
dHdvIHBhcnRpY2lwYW50cyBpbiBJRVRGIHRoZW4geW91IGFyZSByaWdodC4gVGhhdCB3YXMgbm90
IHRoZSBjYXNlLCB0aGUgY2FzZSB3YXMgb25lIHBlcnNvbiBkb2luZyBBZCBob21lbmltZXMgdG8g
YSBuZXcgY29tZXIgZm9yIG1hbnkgdGltZSwgdGhlbiB0aGF0IG5ldyBjb21lciByZXBvcnRlZCBj
YXNlcyB0byBJRVRGIGNoYWlyIGFuZCB0byBBRHMuDQogQWZ0ZXIgdGhhdCB3aGVuIHRoZSBuZXcg
Y29tZXIgd2lsbCBzaG93IHVwIGFmdGVyIGxhcmdlIHBhdGllbnRzLCBhbmQgbWFkZSBhIHN1Z2dl
c3Rpb24sIHRoYXQgQWQgaG9tZW5pbWUgcGVyc29uIGNvbnRpbnVlcyB0byBkaXNjb3VyYWdlIHRo
ZSBuZXcgY29tZXIuPC9kaXY+DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5XR10g
VGhlcmXigJlzIGEgY2hhcmFjdGVyLCBJbmlnbyBNb250b3lhLCBpbiBhIFVTIG1vdmllIGNhbGxl
ZCDigJxUaGUgUHJpbmNlc3MgQnJpZGXigJ0gd2hvIG1ha2VzIGEgc3RhdGVtZW50IGluIHRoZSBt
b3ZpZSB0aGF0IHNvbWUgcGFydHMgb2YgdGhlIGludGVybmV0IGFyZSBmb25kIG9mIHF1b3Rpbmcg
ZHVyaW5nIGFyZ3VtZW50cywg4oCceW91IGtlZXAgdXNpbmcgdGhhdCB3b3Jk4oCmIEkgZG8gbm90
IHRoaW5rIGl0IG1lYW5zIHdoYXQgeW91IHRoaW5rDQogaXQgZG9lcy7igJ0gQXMgeW91IGNhbiBz
ZWUgZnJvbSB0aGUgZGlzY3Vzc2lvbiBvbiB0aGlzIHRocmVhZCwgZXZlbiB3aXRoIGdvb2QgZGVm
aW5pdGlvbnMgb2YgYWQgaG9taW5lbSwgd2UgZG9u4oCZdCBoYXZlIGFueSBzb3J0IG9mIGFncmVl
bWVudCB0aGF0IHRoZSByZXNwb25zZSBpbiBxdWVzdGlvbiB3YXMgaW5kZWVkIGFuIGFkIGhvbWlu
ZW0gYXR0YWNrIG9uIHlvdSwgYW5kIEkgY2Fu4oCZdCByZWFsbHkgc3BlYWsgdG8gYW55IG9mIHRo
ZSBwcmV2aW91cw0KIGluY2lkZW50cyBJIHRoaW5rIHlvdeKAmXJlIHZhZ3VlbHkgcmVmZXJlbmNp
bmcgaGVyZSBiZWNhdXNlIEkgZG9u4oCZdCBoYXZlIGFueSBwZXJzb25hbCBrbm93bGVkZ2Ugb2Yg
dGhlIGNpcmN1bXN0YW5jZXMuPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPHNwYW4gaWQ9Ik9M
S19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXY+PGJyPg0KPC9kaXY+DQo8ZGl2PklFVEYgaXMgcmVz
cG9uc2libGUgdG8gc29sdmUgdGhpcyBwZXJzb25hbCBleHBlcmllbmNlIGFuc3dlcmluZywgbm90
IGFueSBwYXJ0aWNpcGFudC4gSnVzdCBiZWNhdXNlIG9uZSBwZXJzb24gaXMga25vd24gb3Igd2Vs
Y29tZWQgdGhhdCBzaG91bGQgbm90IG1lYW4gZXhwZXJpZW5jZS4gSnVzdCBiZWNhdXNlIG9uZSBw
ZXJzb24gaGFzIGFuIFJGQyBvciBtYW55IFJGQ3MsIHRoYXQgZG9lcyBub3QgbWVhbiB0aGV5IGNh
biBkbyBBZCBob21pbmVtcy4mbmJzcDs8L2Rpdj4NCjwvc3Bhbj4NCjxkaXY+PGJyPg0KPC9kaXY+
DQo8ZGl2PldHXSB0aGlzIGlzbuKAmXQgYWJvdXQgZXhwZXJpZW5jZS4gVGhpcyBpcyBhYm91dCBj
cmVkaWJpbGl0eSwgYXMgd2VsbCBhcyBnb29kIGlkZWFzIHZzIGJhZCBvbmVzLCBhbmQgaG93IHRo
ZXkgYXJlIHByZXNlbnRlZC4gV2hlbiBwZW9wbGUgcXVlc3Rpb24gYW4gdW5rbm93biAodG8gdGhl
bSkgcGVyc29uJ3MgZXhwZXJpZW5jZSB3aXRoaW4gSUVURiwgdGhleeKAmXJlIG9mdGVuIGRvaW5n
IGl0IGluIG9yZGVyIHRvIHRyeSB0byBnaXZlIHlvdSB0aGUNCiBiZW5lZml0IG9mIHRoZSBkb3Vi
dCAoSS5lLiBCZSBwYXRpZW50IGFuZCBnaXZlIGd1aWRhbmNlIHdoaWxlIGEgbmV3IHBlcnNvbiBs
ZWFybnMpLiBJIHBlcnNvbmFsbHkgaGF2ZSBiZWVuIHRoZSBiZW5lZmljaWFyeSBvZiB0aGF0IG1h
bnkgdGltZXMsIGZyb20gbWFueSBleHBlcmllbmNlZCBwYXJ0aWNpcGFudHMsIGJvdGggb24tbGlz
dCBhbmQgb2ZmLCBhbmQgYm90aCBpbiBtYXR0ZXJzIG9mIHRlY2hub2xvZ3kgYW5kIGluIElFVEYg
cHJvY2VzcyBhbmQNCiBjdWx0dXJlLiBIb3dldmVyLCBiYXNlZCBvbiB5b3VyIHByZXZpb3VzIHBv
c3RzIHRvIHRoaXMgbGlzdCwgYW5kIG1hbnkgZGlmZmVyZW50IHBhcnRpY2lwYW50c+KAmSByZXBs
aWVzIHRvIHlvdSwgeW91IHNlZW0gdG8gYmUgdmVyeSBxdWljayB0byBiZSBvZmZlbmRlZCBieSB0
aGlzIGFzIGEgcGVyY2VpdmVkIHNsaWdodCwgcmF0aGVyIHRoYW4gd2lsbGluZyB0byBhdmFpbCB5
b3Vyc2VsZiBvZiB0aGUgcGF0aWVuY2UgYW5kIGd1aWRhbmNlIG9mZmVyZWQNCiBhbmQgbW9yZSBp
bXBvcnRhbnRseSwgY2hhbmdlIHlvdXIgbWV0aG9kcyBpbiByZXNwb25zZSB0byB0aGF0IGd1aWRh
bmNlLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtfU1JDX0JPRFlfU0VD
VElPTiI+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5JIGFtIHZlcnkgc29ycnkgYnV0IGl0IGxv
b2tzIG5vdyBiZXR0ZXIgZm9yIG1lIHRvIGxlYXZlIHRoZSBJRVRGIGxpc3QgZGlzY3Vzc2lvbiZu
YnNwOyhleGNsdWRpbmcgTEMgY29tbWVudHMgYW5kIFJldmlldykmbmJzcDtmb3Igc29tZSB0aW1l
Jm5ic3A7YmVjYXVzZSB0aGlzIGxpc3Qgc2VlbXMgd2l0aCBubyBleHBlcmllbmNlIGhvdyB0byBk
ZWFsIHdpdGggbmV3IGNvbWVycyw8L2Rpdj4NCjwvc3Bhbj4NCjxkaXY+Jm5ic3A7V0ddIEkgYWdy
ZWUgd2l0aCB0aGUgZmlyc3Qgc3RhdGVtZW50LCBidXQgbm90IHRoZSBzZWNvbmQuIEFmdGVyIDIg
eWVhcnMsIHlvdeKAmXJlIG5vdCByZWFsbHkgYSBuZXdjb21lciBhbnltb3JlLCBhcmUgeW91Pzwv
ZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXY+PC9kaXY+DQo8L3Nw
YW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxzcGFuIGlkPSJPTEtf
U1JDX0JPRFlfU0VDVElPTiI+DQo8ZGl2PmFuZCBJIHdpbGwgd29yayBoYXJkIG9uIFN1bmRheSB0
byBkaXN0cmlidXRlIHRoZSBtZXNzYWdlIHRvIGFsbCBuZXcgY29tZXJzIHRoYXQgdGhpcyBsaXN0
IGlzIGRhbmdlcm91cyBsaXN0IGZvciBuZXcgY29tZXJzLiBJIG1heSBhbHNvJm5ic3A7anVzdCBt
YWtlIGEgcXVlc3Rpb24gYW5kIGNvbW1lbnQgaW4gdGhlIHR1dG9yaWFsIGZvciBuZXcgY29tZXJz
LiBJIGRpZCBlbmpveSBwb3N0aW5nIG9uIHRoaXMgbGlzdCBiZWNhdXNlIHRoZXJlIGFyZSBzb21l
DQogZ3JlYXQgcGVvcGxlIEkgbm90aWNlZCwmbmJzcDtidXQgSSB3aWxsIHN0b3AgZm9yIHNvbWUg
dGltZSBmb3IgdGhlIGxpc3QgdG8gdGhpbmsgYWJvdXQgaXRzIGJlaGF2aW9yL3Byb2dyZXNzJm5i
c3A7YW5kIG5ldyBjb21lcnMgdGhpbmsgYWJvdXQgdGhlaXIgcHJvZ3Jlc3MuJm5ic3A7PC9kaXY+
DQo8L3NwYW4+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5XR10gQW5kIGFzIG5vdGVkIGFib3Zl
LCB0aGF0IGlzIGNlcnRhaW5seSB5b3VyIHJpZ2h0IGFzIGEgcGFydGljaXBhbnQuIEhvd2V2ZXIs
IEkgc2luY2VyZWx5IGhvcGUgdGhhdCBuZXdjb21lcnMgd2lsbCBub3QgaGVlZCB0aGlzIChiYWQp
IGFkdmljZSwgYXMgeW91ciBleHBlcmllbmNlIGlzIG5vdCB0eXBpY2FsLCBhbmQgSSBmbGF0bHkg
cmVqZWN0IHlvdXIgYXNzZXJ0aW9uIHRoYXQgdGhlIElFVEYgYW5kIHRoZSB3YXkgdGhhdCBpdHMg
cGFydGljaXBhbnRzDQogaGF2ZSB0cmVhdGVkIHlvdSBpcyBwcmltYXJpbHkgdG8gYmxhbWUgZm9y
IHlvdXIgZGlmZmljdWx0aWVzIGluIHBhcnRpY2lwYXRpbmcgaW4gdGhlIElFVEYuIE5ld2NvbWVy
cyBvZnRlbiBoYXZlIGdyZWF0IGZlZWRiYWNrLCBlc3BlY2lhbGx5IHJlZ2FyZGluZyB0ZWNobmlj
YWwgaXNzdWVzIGFib3V0IHdoaWNoIHRoZXkgaGF2ZSBleHBlcnRpc2UsIGJ1dCB0aGV5IHNob3Vs
ZCBub3QgZmVlbCBkaXNjb3VyYWdlZCBpZiB0aGVpciBmZWVkYmFjayBpcw0KIG5vdCBhbHdheXMg
aW1wbGVtZW50ZWQgbm9yIGFzc3VtZSB0aGF0IHRoZSByZWFzb24gdGhlaXIgZmVlZGJhY2sgaXMg
bm90IGltcGxlbWVudGVkIGlzDQo8c3BhbiBzdHlsZT0iZm9udC13ZWlnaHQ6IGJvbGQ7Ij5iZWNh
dXNlPC9zcGFuPiZuYnNwO3RoZXkgYXJlIGEgbmV3Y29tZXIuICZuYnNwO0Z1cnRoZXIsIHdoZW4g
aXQgY29tZXMgdG8gSUVURiBwcm9jZXNzIGFuZCBjdWx0dXJlLCBpdOKAmXMgaGFyZCBmb3IgZXZl
biBleHBlcmllbmNlZCBJRVRGZXJzIHRvIGVmZmVjdCBjaGFuZ2UsIGV2ZW4gd2l0aCBnb29kLCB3
ZWxsLWp1c3RpaWZpZWQgaWRlYXMgYmFzZWQgb24geWVhcnMgb2YgZXhwZXJpZW5jZSB3aXRoaW4g
dGhlDQogZXhpc3RpbmcgcHJvY2VzcyBhbmQgY3VsdHVyZSwgc28gaW4gdGhhdCBjYXNlLCBJdOKA
mXMgbm90IGp1c3QgeW91LiZuYnNwOzwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXY+SSB3
aXNoIHlvdSBsdWNrIGluIExvbmRvbiwgbWF5IGl0IGJlIGEgdmFsdWFibGUgbGVhcm5pbmcgZXhw
ZXJpZW5jZSBmb3IgeW91LCBhcyB3ZWxsIGFzIGFuIG9wcG9ydHVuaXR5IHRvIGZvcmdlIHNvbWUg
Z29vZCB3b3JraW5nIHJlbGF0aW9uc2hpcHMgd2l0aCBvdGhlciBwYXJ0aWNpcGFudHMuPC9kaXY+
DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdj5XZXMgR2VvcmdlPC9kaXY+DQo8ZGl2Pjxicj4NCjwv
ZGl2Pg0KPHNwYW4gaWQ9Ik9MS19TUkNfQk9EWV9TRUNUSU9OIj4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMGluIDBpbiAwLjAwMDFwdDsgZm9udC1z
aXplOiAxMXB0OyI+PHNwYW4gc3R5bGU9ImNvbG9yOiByZ2IoMTI3LCAxMjcsIDEyNyk7Ij5Bbnl0
aGluZyBiZWxvdyB0aGlzIGxpbmUgaGFzIGJlZW4gYWRkZWQgYnkgbXkgY29tcGFueeKAmXMgbWFp
bCBzZXJ2ZXIsIEkgaGF2ZSBubyBjb250cm9sIG92ZXIgaXQuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMGluIDBpbiAwLjAwMDFwdDsg
Zm9udC1zaXplOiAxMXB0OyI+PHNwYW4gc3R5bGU9ImNvbG9yOiByZ2IoMTI3LCAxMjcsIDEyNyk7
Ij4tLS0tLS0tLS0tLTwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj48c3BhbiBzdHls
ZT0iY29sb3I6IHJnYigxMjcsIDEyNywgMTI3KTsiPjxicj4NCjwvc3Bhbj48L2Rpdj4NCjwvc3Bh
bj48YnI+DQo8aHI+DQo8Zm9udCBmYWNlPSJBcmlhbCIgY29sb3I9IkdyYXkiIHNpemU9IjEiPlRo
aXMgRS1tYWlsIGFuZCBhbnkgb2YgaXRzIGF0dGFjaG1lbnRzIG1heSBjb250YWluIFRpbWUgV2Fy
bmVyIENhYmxlIHByb3ByaWV0YXJ5IGluZm9ybWF0aW9uLCB3aGljaCBpcyBwcml2aWxlZ2VkLCBj
b25maWRlbnRpYWwsIG9yIHN1YmplY3QgdG8gY29weXJpZ2h0IGJlbG9uZ2luZyB0byBUaW1lIFdh
cm5lciBDYWJsZS4gVGhpcyBFLW1haWwgaXMgaW50ZW5kZWQgc29sZWx5DQogZm9yIHRoZSB1c2Ug
b2YgdGhlIGluZGl2aWR1YWwgb3IgZW50aXR5IHRvIHdoaWNoIGl0IGlzIGFkZHJlc3NlZC4gSWYg
eW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCBvZiB0aGlzIEUtbWFpbCwgeW91IGFy
ZSBoZXJlYnkgbm90aWZpZWQgdGhhdCBhbnkgZGlzc2VtaW5hdGlvbiwgZGlzdHJpYnV0aW9uLCBj
b3B5aW5nLCBvciBhY3Rpb24gdGFrZW4gaW4gcmVsYXRpb24gdG8gdGhlIGNvbnRlbnRzIG9mIGFu
ZCBhdHRhY2htZW50cyB0bw0KIHRoaXMgRS1tYWlsIGlzIHN0cmljdGx5IHByb2hpYml0ZWQgYW5k
IG1heSBiZSB1bmxhd2Z1bC4gSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBFLW1haWwgaW4gZXJy
b3IsIHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgcGVybWFuZW50bHkg
ZGVsZXRlIHRoZSBvcmlnaW5hbCBhbmQgYW55IGNvcHkgb2YgdGhpcyBFLW1haWwgYW5kIGFueSBw
cmludG91dC48YnI+DQo8L2ZvbnQ+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CF35F90C120C7wesleygeorgetwcablecom_--


From nobody Fri Feb 28 07:30:05 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 1CE8D1A083B for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:30:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level: 
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GkuELyZufSbn for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:29:59 -0800 (PST)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) by ietfa.amsl.com (Postfix) with ESMTP id BAD8C1A02DD for <ietf@ietf.org>; Fri, 28 Feb 2014 07:29:59 -0800 (PST)
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 1WJPNp-00064B-LK; Fri, 28 Feb 2014 15:29:53 +0000
Date: Fri, 28 Feb 2014 15:29:52 +0000
Message-ID: <m261nzb6hb.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <m3ha7jmm7k.wl%narten@us.ibm.com> <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.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/bBYdnGup7fk1gUjsjnet1ABbnoM
Cc: Thomas Narten <narten@us.ibm.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, 28 Feb 2014 15:30:01 -0000

> Nevertheless, procmail doesn't seem like the right answer.

for some of us it is the best answer we have.  there is way too much
real work to do, and the denial of clue attacks are sufficiently
depressing to impinge on one's ability work.

jck once suggested a 2x2 matrix, with clue on one axis and energy on the
other.  the real threat is the clueless and energetic.  thomas seems to
have a primitive and very rough cut at a metric.

randy


From nobody Fri Feb 28 07:57:04 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 4FE611A00DE for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:57:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.448
X-Spam-Level: 
X-Spam-Status: No, score=-7.448 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.547, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2ibyyBN60XKA for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 07:57:02 -0800 (PST)
Received: from e32.co.us.ibm.com (e32.co.us.ibm.com [32.97.110.150]) by ietfa.amsl.com (Postfix) with ESMTP id 023D41A0835 for <ietf@ietf.org>; Fri, 28 Feb 2014 07:57:01 -0800 (PST)
Received: from /spool/local by e32.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>; Fri, 28 Feb 2014 08:57:00 -0700
Received: from d03dlp01.boulder.ibm.com (9.17.202.177) by e32.co.us.ibm.com (192.168.1.132) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 28 Feb 2014 08:56:58 -0700
Received: from b03cxnp08025.gho.boulder.ibm.com (b03cxnp08025.gho.boulder.ibm.com [9.17.130.17]) by d03dlp01.boulder.ibm.com (Postfix) with ESMTP id 8CA191FF0045 for <ietf@ietf.org>; Fri, 28 Feb 2014 08:56:57 -0700 (MST)
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by b03cxnp08025.gho.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id s1SFuvEx11010360 for <ietf@ietf.org>; Fri, 28 Feb 2014 16:56:57 +0100
Received: from d03av03.boulder.ibm.com (localhost [127.0.0.1]) by d03av03.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVout) with ESMTP id s1SFuvac016416 for <ietf@ietf.org>; Fri, 28 Feb 2014 08:56:57 -0700
Received: from cichlid.raleigh.ibm.com (sig-9-49-141-170.mts.ibm.com [9.49.141.170]) by d03av03.boulder.ibm.com (8.14.4/8.14.4/NCO v10.0 AVin) with ESMTP id s1SFutqT016286 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 28 Feb 2014 08:56:56 -0700
Received: from cichlid.raleigh.ibm.com.us.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.4/8.12.5) with ESMTP id s1SFusXw008126; Fri, 28 Feb 2014 10:56:54 -0500
Date: Fri, 28 Feb 2014 10:56:54 -0500
Message-ID: <m3fvn3mdrt.wl%narten@us.ibm.com>
From: Thomas Narten <narten@us.ibm.com>
To: Ted Lemon <ted.lemon@nominum.com>
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <m3ha7jmm7k.wl%narten@us.ibm.com> <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/23.1 (x86_64-redhat-linux-gnu) MULE/6.0 (HANACHIRUSATO)
MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
X-TM-AS-MML: disable
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 14022815-0928-0000-0000-0000000F4B86
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/S4VCjvRIeeU7Gn4OZ0kyovgGcy0
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, 28 Feb 2014 15:57:03 -0000

> Nevertheless, procmail doesn't seem like the right answer.

Perhaps not for all.

But the other extreme (which some here regularly advocate) is complete
openness to all - just in case they might potentially have something
useful to contribute - even if the overwhelming past history strongly
suggests that will never happen.

We have people that post that are effectively DOS generators.  Their
postings are largely not taken seriously (or even read most likely) by
anyone who has been an IETF contributer for any length of time. Yet
they do get responded to (even the strong sometimes have moments of
weakness and take the bait) and it sucks away cycles from the
community that should really be directed towards more important
things.

Yet, by not kicking them off of lists and otherwise making it clear
that they have worn out their welcome, the community sends an implicit
signal to the lurkers/newcomers that even such voices are welcome and
that their disruptive tactics are perfectly acceptable behavior. Even
worse, it probably encourages some do to do the same.

Of course, everyone should get a grace period when they start, but it
should not be open ended. IMO, we are sometimes too tolerant of what
should be unnacceptable behavior -- behavior that is a drain on IETF
resources and produces little of use in return.  IMO, it does not help
the organization and it even drives away participation from those we
really want to keep. 

Case in point: there are many long-time IETFers who do not subscribe
to this list. Signal-to-noise is just too low. That should tell us
something.

Thomas


From nobody Fri Feb 28 08:03:21 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 1B1D91A085C for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 08:03:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.547
X-Spam-Level: 
X-Spam-Status: No, score=-2.547 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.547] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id r4M6bc1mFRSW for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 08:03:13 -0800 (PST)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id 821341A00DE for <ietf@ietf.org>; Fri, 28 Feb 2014 08:03:13 -0800 (PST)
Received: from SUBMAN.elandsys.com ([197.224.129.233]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id s1SG2o0L025254 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 28 Feb 2014 08:03:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1393603383; bh=uyJa7df0uoyNfLKbXJVlzCfhOrQ/7ef/pbI/02Hr9Z8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=iu/jTdFdeslvHEcX5ZTczvjyRaGmg0uToLHYd77ijCp/DwWCJelIW45LoiHgIMYZP OD341nWXyR+tBHHhFyFvBr6AKSD70oMDFlvXFlwz0A/00bwP6SnD/Aol9x9SbfUGHn xHzKXqITUt2qWAyEK04SlXt9YEftoa4t4rE2IAXM=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1393603383; i=@elandsys.com; bh=uyJa7df0uoyNfLKbXJVlzCfhOrQ/7ef/pbI/02Hr9Z8=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=VOOqd6rWGFu0muI6FXnblOSvzTUeB0faSLx90PWfqKNxlPyXRGDaM8Uqrp0IcC65w fFBlaGxjq/V5r5F8C1q4GPW8t9dh/Y/rYDZOs7/q+wvO2lsjK4XcsmGeQ63UFp/SDA YaQ6OCK7bzmx7bGSbs31a5Xnu8a4eJfYdO2AuaGc=
Message-Id: <6.2.5.6.2.20140228061633.0d6acfb8@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Fri, 28 Feb 2014 07:35:54 -0800
To: Chaitanya Dhareshwar <chaitanyabd@gmail.com>
From: S Moonesamy <sm+ietf@elandsys.com>
Subject: Filtering email (was: Clarifying IETF process)
In-Reply-To: <CAEP5zKRhpzhFT293cngvzf65AsdgS6A6f=K-HneDJbJHSbN1DA@mail.g mail.com>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <CAEP5zKRhpzhFT293cngvzf65AsdgS6A6f=K-HneDJbJHSbN1DA@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/hxTbEUCKsJ7av9Shse-eCDGSz3M
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, 28 Feb 2014 16:03:18 -0000

Hi Chaitanya,
At 04:21 28-02-2014, Chaitanya Dhareshwar wrote:
>Try http://www.gsp.com/cgi-

There was a problem with the afnog server around Christmas in 
2011.  This is one of the situations where it would be a problem if I 
was not reachable by email.  Using the phone was not an 
option.  There is the timezone difference and trying to find a person 
who can actually help.

In the email world there is something called the "first contact" 
problem.  Filtering email is not about judgement.  It is about being 
able to draw up a list of considerations and evaluating the 
consequences of what has not happened yet.

If I suggest to a person to try procmail I would discuss about the 
considerations with him/her.

Regards,
S. Moonesamy  


From nobody Fri Feb 28 08:07:53 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 026801A0308 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 08:07:51 -0800 (PST)
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 S7jKoQOwPI8I for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 08:07:49 -0800 (PST)
Received: from mail-qa0-x233.google.com (mail-qa0-x233.google.com [IPv6:2607:f8b0:400d:c00::233]) by ietfa.amsl.com (Postfix) with ESMTP id D43E81A02E0 for <ietf@ietf.org>; Fri, 28 Feb 2014 08:07:48 -0800 (PST)
Received: by mail-qa0-f51.google.com with SMTP id j7so851340qaq.10 for <ietf@ietf.org>; Fri, 28 Feb 2014 08:07:46 -0800 (PST)
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=7qZFCs8QZLdba4q2vsa5B+tfBeeEwumSseUZbFnOXjg=; b=uOrFJn0gJ9ac74nYqq9R6nWv6UCog9RLVkR9ynRiUdSA1pZBxZbXJsq3YoVth+2PM/ WzC7vuXgZIa2mnDabAro1Zyxmtg7WhW0+1wKYiR3dIoKGHJAjtGkg4CKVGnkix/D/JbW nclFMe2J72bXz7eWUQwr8ubwzFytfUPNjOOBABpwyS2SLP1kG5rQnuHeyy6IxMUZCs7O Ta5rlE990havk5oCZ08slwavk366kmG1Iq1Ep3eAwXNWPnWXvPWvFMXABvzmk/3+8BpE o8p+3UaGntTC+SCHJnthxakrItnztiE1NcMYfYnVEgXH8v8bLYGZd/jX2y9mys5kF0nf jUjQ==
MIME-Version: 1.0
X-Received: by 10.224.114.141 with SMTP id e13mr4673105qaq.65.1393603666758; Fri, 28 Feb 2014 08:07:46 -0800 (PST)
Received: by 10.224.186.142 with HTTP; Fri, 28 Feb 2014 08:07:46 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140228061633.0d6acfb8@resistor.net>
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <CAEP5zKRhpzhFT293cngvzf65AsdgS6A6f=K-HneDJbJHSbN1DA@mail.gmail.com> <6.2.5.6.2.20140228061633.0d6acfb8@resistor.net>
Date: Fri, 28 Feb 2014 21:37:46 +0530
Message-ID: <CAEP5zKRyQQRypbAG81HXPTpSC5DZCvYU2X1Wd6+sQRUvutvtAQ@mail.gmail.com>
Subject: Re: Filtering email (was: Clarifying IETF process)
From: Chaitanya Dhareshwar <chaitanyabd@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=047d7bea44d483e9e404f379a377
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/70LrnUJacmnNgM0RrM5TDxaMYIM
Cc: IETF Discuss <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2014 16:07:51 -0000

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

I'm not taking sides there. The links were to help Ted get an equivalent of
"man procmail".

Personally I find both sides of the argument interesting, so I'll continue
to sit on the fence until I have a compelling reason to jump in...

Thanks,

*Chaitanya Dhareshwar*

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


On Fri, Feb 28, 2014 at 9:05 PM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> Hi Chaitanya,
> At 04:21 28-02-2014, Chaitanya Dhareshwar wrote:
>
>> Try http://www.gsp.com/cgi-
>>
>
> There was a problem with the afnog server around Christmas in 2011.  This
> is one of the situations where it would be a problem if I was not reachable
> by email.  Using the phone was not an option.  There is the timezone
> difference and trying to find a person who can actually help.
>
> In the email world there is something called the "first contact" problem.
>  Filtering email is not about judgement.  It is about being able to draw up
> a list of considerations and evaluating the consequences of what has not
> happened yet.
>
> If I suggest to a person to try procmail I would discuss about the
> considerations with him/her.
>
> Regards,
> S. Moonesamy
>

--047d7bea44d483e9e404f379a377
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&#39;m not taking sides there. The links were to help Ted get a=
n equivalent of &quot;man procmail&quot;.=A0</div><div class=3D"gmail_defau=
lt" style=3D"font-family:tahoma,sans-serif">
<br></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-ser=
if">Personally I find both sides of the argument interesting, so I&#39;ll c=
ontinue to sit on the fence until I have a compelling reason to jump in...=
=A0</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">Th=
anks,</div></div><div class=3D"gmail_extra"><br clear=3D"all"><div><div dir=
=3D"ltr"><div>
<font face=3D"tahoma,sans-serif"><strong><font color=3D"#3d85c6">Chaitanya =
Dhareshwar</font></strong></font></div><div><strong><font color=3D"#3d85c6"=
 face=3D"Tahoma"></font></strong><font face=3D"tahoma,sans-serif"><br><a hr=
ef=3D"http://in.linkedin.com/in/chaitanyabd" target=3D"_blank"><font color=
=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"#3d8=
5c6">Blog</font></a><font> <font face=3D"tahoma,sans-serif">| </font><font =
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 Fri, Feb 28, 2014 at 9:05 PM, S Moone=
samy <span dir=3D"ltr">&lt;<a href=3D"mailto:sm+ietf@elandsys.com" target=
=3D"_blank">sm+ietf@elandsys.com</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">
Hi Chaitanya,<br>
At 04:21 28-02-2014, Chaitanya Dhareshwar wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Try <a href=3D"http://www.gsp.com/cgi-" target=3D"_blank">http://www.gsp.co=
m/cgi-</a><br>
</blockquote>
<br>
There was a problem with the afnog server around Christmas in 2011. =A0This=
 is one of the situations where it would be a problem if I was not reachabl=
e by email. =A0Using the phone was not an option. =A0There is the timezone =
difference and trying to find a person who can actually help.<br>

<br>
In the email world there is something called the &quot;first contact&quot; =
problem. =A0Filtering email is not about judgement. =A0It is about being ab=
le to draw up a list of considerations and evaluating the consequences of w=
hat has not happened yet.<br>

<br>
If I suggest to a person to try procmail I would discuss about the consider=
ations with him/her.<br>
<br>
Regards,<br>
S. Moonesamy =A0<br>
</blockquote></div><br></div>

--047d7bea44d483e9e404f379a377--


From nobody Fri Feb 28 10:44:33 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 CDF1B1A0252 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 10:44:32 -0800 (PST)
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 2AeucbbCx6Ae for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 10:44:30 -0800 (PST)
Received: from news.winserver.com (pop3.winserver.com [208.247.131.9]) by ietfa.amsl.com (Postfix) with ESMTP id E7BFB1A0238 for <ietf@ietf.org>; Fri, 28 Feb 2014 10:44:29 -0800 (PST)
DKIM-Signature: v=1; d=isdg.net; s=tms1; a=rsa-sha1; c=simple/relaxed; l=947; t=1393613062; h=Received:Received: Received:Received:Message-ID:Date:From:Organization:To:Subject: List-ID; bh=v5ygLrXeXawmbTrWRyuJAKBpXl8=; b=S4CVmRIXsEaa9z083uTS eRB8LkeMARPhfx4Rl48LY2FrHM/BMyLMLV9j6p8XeYsxPBJriIpU21WPvZke3uH9 tDLJHCf6HBWfunziH2f7ERvVAYxMoIlp5UBuLwDHGON6TGqPIGtYiNAFzFH1bNSk V7ULUOJhYZBOLXAxaoZuQPA=
Received: by winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 28 Feb 2014 13:44:22 -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 2895519636.23237.3068; Fri, 28 Feb 2014 13:44:21 -0500
DKIM-Signature: v=1; d=beta.winserver.com; s=tms1; a=rsa-sha256; c=simple/relaxed; l=947; t=1393612418; h=Received:Received: Message-ID:Date:From:Organization:To:Subject:List-ID; bh=pqjR2Sz 8r8nOtGiJKXDMaOU1KfmSSt0pInqNgoGzWCY=; b=ygHoClUmlyBzlBQgE4KSdRh 5FlKmjXG/xz4YiDdURSTODl2SdD+v5lQQkTGiwJZ1Qvmobhyimg/eddDHheYEe+2 ub/udmf4+kPRdC9WhPMAHMTN9NAVWnwNqb6tYw7lv94kiqXv001nyAYgJFP31xrI qh4/q2Z5NbVbJnNPvJa8=
Received: by beta.winserver.com (Wildcat! SMTP Router v7.0.454.4) for ietf@ietf.org; Fri, 28 Feb 2014 13:33:38 -0500
Received: from [192.168.1.2] ([99.121.4.27]) by beta.winserver.com (Wildcat! SMTP v7.0.454.4) with ESMTP id 2341797506.9.6004; Fri, 28 Feb 2014 13:33:37 -0500
Message-ID: <5310D908.2070602@isdg.net>
Date: Fri, 28 Feb 2014 13:44:24 -0500
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: Ted Lemon <ted.lemon@nominum.com>, Thomas Narten <narten@us.ibm.com>
Subject: Re: Clarifying IETF process [Was: A private club]
References: <0e3601cf32fa$a1de7fc0$e59b7f40$@olddog.co.uk> <6.2.5.6.2.20140226074723.0e37af20@elandnews.com> <CADnDZ882kx9utfQt=HVC7LdZGjKrr1WQHfqwUSCyi6RHCJGQjw@mail.gmail.com> <CAKHUCzyb79unSZOmsOJPezhW+eyGBGpiSdqrupYux7-1BO0d=A@mail.gmail.com> <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <m3ha7jmm7k.wl%narten@us.ibm.com> <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.com>
In-Reply-To: <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/L7T2ZIWhNTo74R4cSeKU_0hsTIQ
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, 28 Feb 2014 18:44:33 -0000

Personal filtering is one thing, advocating it to others as a general 
practice is another.  That is where the IETF or the WG process tends 
to go sour -- when it does appear to be a "private club," and 
"ignorance" and "Follow the Chieftain" syndrome is high. While it is 
obviously used to move an agenda forward, its not always pretty, nor 
fair when it happens and it hasn't been convincing of late the end 
results are often better.  You may get your  "RFC" but at what cost?

Thanks

Hector Santos, CTO
Santronics Software, Inc.

On 2/28/2014 10:17 AM, Ted Lemon wrote:
> On Feb 28, 2014, at 12:54 PM, Thomas Narten <narten@us.ibm.com> wrote:
>> Reading every piece of IETF email definitely is not prioritizing
>> resources properly. Indeed, it is not uncommon to see threads that
>> exhibit properties often associated with DOS attacks.
>
> +1
>
> Nevertheless, procmail doesn't seem like the right answer.
>
>
>

-- 
HLS



From nobody Fri Feb 28 13:45:06 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 CFC941A022D for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 13:45:04 -0800 (PST)
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_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, 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 ZLyQpLV-cx6M for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 13:45:04 -0800 (PST)
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 940271A01F6 for <ietf@ietf.org>; Fri, 28 Feb 2014 13:45:03 -0800 (PST)
Received: (qmail 4172 invoked from network); 28 Feb 2014 21:45:01 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 28 Feb 2014 21:45: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:mime-version:content-type:content-transfer-encoding; s=5311035e.xn--hew.k1402; i=johnl@user.iecc.com; bh=ncCZe0oZqpPOyBa689lkAMMAQb3SXTVKW2JDm0oWG/k=; b=NFkv5QXmfX02o4wO6X2f8gAt97v7jhC1yAeTZrEYT6S8kITrIdp2zmovrDUHQ8mzrmH18lX45mSUeudVymTRBTU9Q9pjtY0HC0umgbUOkOF69+9pGuhkKm17ghyBl5Pl3WTsti6/m+yd3MQw3SKcDTRRBFZdkGJQK8CN9zAyeKniOzToqlw7WfZZCm/lkZr+XMNj/JGyklJcBF/TCYB65PMX5K54NzNxDVKy9KyZWvoSj3Is4V4hkPHaDx5bxayQ
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=5311035e.xn--hew.k1402; bh=ncCZe0oZqpPOyBa689lkAMMAQb3SXTVKW2JDm0oWG/k=; b=mNS/e2Zw2UcZD4VGPFffWKtO0roTpmsZ85EHQ1itf0jXFHJkC4cyb8pd2Zj7OdmRF54U7epWXiUg5BgMB5VotPvTN7ZSxWvzgXG98ksPKlKQeUpkoDkDb8iLwwbGny8FUbLJM6+yvMIPTqInpzBtJq6SMinoeXEdwfz/WDWmyQohqsFvQXxQ8rlEDDe8BIK1HDz3TsFYeDDF9opSQMBnbQZrHJ6lE9AKT3zKKD6v0cfcxiN0UZJh1jMsyz8zTKdv
Date: 28 Feb 2014 21:44:40 -0000
Message-ID: <20140228214440.33574.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Clarifying IETF process [Was: A private club]
In-Reply-To: <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.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/SdOhCuHHFNK41AZFXvAopqx89dc
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2014 21:45:05 -0000

>Nevertheless, procmail doesn't seem like the right answer.

Generally I agree, although I've found a very small number of people
whose content/traffic ratio is so poor that procmail just does what
I'd do anyway, only faster.

R's,
John




From nobody Fri Feb 28 14:10:56 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 B5B351A0269 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 14:10:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.547, 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 3qLJ0jN2TU90 for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 14:10:51 -0800 (PST)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) by ietfa.amsl.com (Postfix) with ESMTP id F17FF1A0156 for <ietf@ietf.org>; Fri, 28 Feb 2014 14:10:50 -0800 (PST)
Received: from root (helo=closure.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.80) (envelope-from <tytso@thunk.org>) id 1WJVdl-0000rl-4i; Fri, 28 Feb 2014 22:10:45 +0000
Received: by closure.thunk.org (Postfix, from userid 15806) id 84CC0580249; Fri, 28 Feb 2014 17:10:44 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=thunk.org; s=mail; t=1393625444; bh=2TZnyxU0GseL0WjiWmPPOwhzmnZdgh8k90gFrwFeWEw=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=LZVkMtqMSrk859p1PbN3bXMrBedZkYqnJds9NjZOQ6QVSSHlTGkfCJ/MJYewfGO9l GeoacBltWaEo6Z5o8wHVEtHErmzZ6mcXfYwdBjdILWoYFeP9v1sBcNunb74eQIXKy4 tQQlgtNVByRrzPQoR4Kzscil9THeE6LP3nJSiyzY=
Date: Fri, 28 Feb 2014 17:10:44 -0500
From: Theodore Ts'o <tytso@mit.edu>
To: Hector Santos <hsantos@isdg.net>
Subject: Re: Clarifying IETF process [Was: A private club]
Message-ID: <20140228221044.GA11245@thunk.org>
References: <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <m3ha7jmm7k.wl%narten@us.ibm.com> <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.com> <5310D908.2070602@isdg.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5310D908.2070602@isdg.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 imap.thunk.org); SAEximRunCond expanded to false
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/eD4BA_xKCud6eoRTqsyWfGyclTM
Cc: Thomas Narten <narten@us.ibm.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, 28 Feb 2014 22:10:54 -0000

On Fri, Feb 28, 2014 at 01:44:24PM -0500, Hector Santos wrote:
> Personal filtering is one thing, advocating it to others as a
> general practice is another.  That is where the IETF or the WG
> process tends to go sour -- when it does appear to be a "private
> club," and "ignorance" and "Follow the Chieftain" syndrome is high.
> While it is obviously used to move an agenda forward, its not always
> pretty, nor fair when it happens and it hasn't been convincing of
> late the end results are often better.  You may get your  "RFC" but
> at what cost?

If someone is carrying out a denial of service attack against an
someone on the IESG, recommending that they filter someone who has
proven that they are lacking in clue doesn't seem to me to be the same
thing as a "private club".

					- Ted


From nobody Fri Feb 28 15:30:34 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 5FD261A028E for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 15:30:32 -0800 (PST)
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 LlTGcSu_Biaa for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 15:30:30 -0800 (PST)
Received: from mail-pb0-x22c.google.com (mail-pb0-x22c.google.com [IPv6:2607:f8b0:400e:c01::22c]) by ietfa.amsl.com (Postfix) with ESMTP id DD74F1A0234 for <ietf@ietf.org>; Fri, 28 Feb 2014 15:30:30 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id rp16so1385280pbb.31 for <ietf@ietf.org>; Fri, 28 Feb 2014 15:30:28 -0800 (PST)
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=sAXeuecVLy1jyCk2Z53ufG8WvgdQlcNV2sNzyNkLnlo=; b=ZN1EEsW6DJNsTlIrd5Dvp6x/MzTdlFW/fMT7wT2hgpJvqv9Lv/oBZpMfiAddGjBWLc XO/WshU+qUD6/VKvaiey0UIjCJTqDxBQ2KRBYtuYe8TgYEoOIy4i3Liz5i1st5jNGWRq 7zMLrr+oJ3WW3OiSj45zQQ/KY3tF2YndYwNo7FlNgQFjOd+0RhNwgfjhbX0RWgBHtkN+ l2lbPyEx9kxXf6YcGoZ3hCH33kFGBUY6vVTVxeBGdmEGChlBEwxPJJmJxxUFl8WNekqU plPNChErtXFe9aAixoH2Xxisf4WOAKo8Zq49mtTr81HuKxi3V0i+jchcuakTvrJr9dgT Dd9g==
MIME-Version: 1.0
X-Received: by 10.66.163.138 with SMTP id yi10mr6393295pab.95.1393630228897; Fri, 28 Feb 2014 15:30:28 -0800 (PST)
Received: by 10.66.220.102 with HTTP; Fri, 28 Feb 2014 15:30:28 -0800 (PST)
In-Reply-To: <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net>
References: <20140225175749.5521718C139@mercury.lcs.mit.edu> <CAC4RtVDOM3OVVstYFR_dpN=+eB=W-_rNdV8Ur_B-YFxTk3vsAQ@mail.gmail.com> <530CEDBE.7080609@cisco.com> <530CF16B.8070703@dcrocker.net> <530CF927.4080203@cisco.com> <530D0F63.5020605@dcrocker.net> <6.2.5.6.2.20140225145100.0ca68e10@resistor.net> <530D2813.1080304@gmail.com> <6.2.5.6.2.20140225222950.0bbcd1a0@resistor.net>
Date: Fri, 28 Feb 2014 15:30:28 -0800
Message-ID: <CAL0qLwZ2whe2zVsHk6JjdTO8VD2kCjOkq-HR7TO59sZ1JfGCUg@mail.gmail.com>
Subject: Re: A private club
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: multipart/alternative; boundary=047d7b86f262bde56a04f37fd2c9
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/aUy3KTWcWrmSIaxLHY2JF4WnGAM
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, 28 Feb 2014 23:30:32 -0000

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

On Wed, Feb 26, 2014 at 12:34 AM, S Moonesamy <sm+ietf@elandsys.com> wrote:

> I am not comfortable stating that there is consensus on an Internet-Draft
> when participation is from a small number of individuals having some
> affiliation in common.  That creates an appearance of a private club.
>

I understand what you're saying here, but I think if we were to establish
rules that demand a non-small number of diverse individuals for anything to
get published, we would be a lot less able to make progress on much of
anything than is the case now.  I'm sure we would all prefer more obvious
consensus and diversity, but sometimes we have to go with what we can
muster.  It's definitely a worthwhile compromise, in my opinion.

-MSK

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

<div dir=3D"ltr">On Wed, Feb 26, 2014 at 12:34 AM, 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> 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">I am not comfortable stating that there is c=
onsensus on an Internet-Draft when participation is from a small number of =
individuals having some affiliation in common. =A0That creates an appearanc=
e of a private club.<br>
</blockquote><div><br></div><div>I understand what you&#39;re saying here, =
but I think if we were to establish rules that demand a non-small number of=
 diverse individuals for anything to get published, we would be a lot less =
able to make progress on much of anything than is the case now.=A0 I&#39;m =
sure we would all prefer more obvious consensus and diversity, but sometime=
s we have to go with what we can muster.=A0 It&#39;s definitely a worthwhil=
e compromise, in my opinion.<br>
<br></div><div>-MSK<br></div></div></div></div>

--047d7b86f262bde56a04f37fd2c9--


From nobody Fri Feb 28 15:43:50 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 824491A015E for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 15:43:49 -0800 (PST)
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 JZso70MPc3Kv for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 15:43:48 -0800 (PST)
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 61F271A02F8 for <ietf@ietf.org>; Fri, 28 Feb 2014 15:43:48 -0800 (PST)
Received: by mail-pd0-f181.google.com with SMTP id p10so1358213pdj.40 for <ietf@ietf.org>; Fri, 28 Feb 2014 15:43:46 -0800 (PST)
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=VXneRrbZOsDDt6nDR8CWcfGnKaScTa9k2apyEqb5WIg=; b=lWxcoDvU7glXbp2qgtLT2Fb8stZJojOHjQrN3Hso+W4P4boYYu6jt4HWH/7wCB78RS j/vju2vWqOAO+re5QJ5C2FWtz70MVvMwRY2AiOVPo0OYZQFc5Bk2xJI/+hcX6dRh7pgN pgPyMYKAMM6U5njv6WdHJbs7lD398jGzF1HGdLFnoB9o/VVnE0ZOfH2mc4WKHrrXhD46 0ZMslmNmaivYn6lKgJAEFY0/fStXYGPI+IeVowvGxbmgZ245tjDuJDijzpOsvueakYua qGgjLd42ofbVVAgqHEwE1Ri6nn4BxP0sGDrCuXvWe+AKFlylmYSTitkwQLee3jCKlfgx NX3Q==
MIME-Version: 1.0
X-Received: by 10.66.136.131 with SMTP id qa3mr6343116pab.77.1393631026549; Fri, 28 Feb 2014 15:43:46 -0800 (PST)
Received: by 10.66.220.102 with HTTP; Fri, 28 Feb 2014 15:43:46 -0800 (PST)
In-Reply-To: <20140228221044.GA11245@thunk.org>
References: <CAF4+nEHF-OyDHYq0daQ+6qSf+RiLBuBYVU-OZA56n69TuE5wRQ@mail.gmail.com> <20140227145755.GY54716@verdi> <20140227154241.GB7982@thunk.org> <20140228005359.GZ54716@verdi> <4437AB18-7120-48F2-B0F7-C5104912FA6A@nominum.com> <m2vbvzvev8.wl%randy@psg.com> <7CE5C434-AC6B-47E7-B709-66A6ED70F684@nominum.com> <m3ha7jmm7k.wl%narten@us.ibm.com> <0356EA8E-A1F3-4E93-B9BD-ACB16740BF9C@nominum.com> <5310D908.2070602@isdg.net> <20140228221044.GA11245@thunk.org>
Date: Fri, 28 Feb 2014 15:43:46 -0800
Message-ID: <CAL0qLwai05=prN+W0bkwHPRGpuYxKaqXvBqyZRWfwJNUZ3+A4g@mail.gmail.com>
Subject: Re: Clarifying IETF process [Was: A private club]
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
Content-Type: multipart/alternative; boundary=001a113376904919f404f380028b
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Ds-A38M8T5xnBZYm4fEKl7CRXTQ
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, 28 Feb 2014 23:43:49 -0000

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

+1, especially if you insert "or a working group" after "IESG".

I feel it's unfair to claim there's a private club if your only evidence is
that an idea of yours didn't get support when you shared it.  It's also not
correct that this is something to take personally.  A better use of one's
energy would be to get a deeper understanding of the "why", which only
enables a more productive outcome the next time.

-MSK


On Fri, Feb 28, 2014 at 2:10 PM, Theodore Ts'o <tytso@mit.edu> wrote:

> On Fri, Feb 28, 2014 at 01:44:24PM -0500, Hector Santos wrote:
> > Personal filtering is one thing, advocating it to others as a
> > general practice is another.  That is where the IETF or the WG
> > process tends to go sour -- when it does appear to be a "private
> > club," and "ignorance" and "Follow the Chieftain" syndrome is high.
> > While it is obviously used to move an agenda forward, its not always
> > pretty, nor fair when it happens and it hasn't been convincing of
> > late the end results are often better.  You may get your  "RFC" but
> > at what cost?
>
> If someone is carrying out a denial of service attack against an
> someone on the IESG, recommending that they filter someone who has
> proven that they are lacking in clue doesn't seem to me to be the same
> thing as a "private club".
>
>                                         - Ted
>
>

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

<div dir=3D"ltr"><div>+1, especially if you insert &quot;or a working group=
&quot; after &quot;IESG&quot;.<br><br></div>I feel it&#39;s unfair to claim=
 there&#39;s a private club if your only evidence is that an idea of yours =
didn&#39;t get support when you shared it.=A0 It&#39;s also not correct tha=
t this is something to take personally.=A0 A better use of one&#39;s energy=
 would be to get a deeper understanding of the &quot;why&quot;, which only =
enables a more productive outcome the next time.<br>
<br>-MSK<br></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_qu=
ote">On Fri, Feb 28, 2014 at 2:10 PM, Theodore Ts&#39;o <span dir=3D"ltr">&=
lt;<a href=3D"mailto:tytso@mit.edu" target=3D"_blank">tytso@mit.edu</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"">On Fri, Feb 28, 2014 at 01:4=
4:24PM -0500, Hector Santos wrote:<br>
&gt; Personal filtering is one thing, advocating it to others as a<br>
&gt; general practice is another. =A0That is where the IETF or the WG<br>
&gt; process tends to go sour -- when it does appear to be a &quot;private<=
br>
&gt; club,&quot; and &quot;ignorance&quot; and &quot;Follow the Chieftain&q=
uot; syndrome is high.<br>
&gt; While it is obviously used to move an agenda forward, its not always<b=
r>
&gt; pretty, nor fair when it happens and it hasn&#39;t been convincing of<=
br>
&gt; late the end results are often better. =A0You may get your =A0&quot;RF=
C&quot; but<br>
&gt; at what cost?<br>
<br>
</div>If someone is carrying out a denial of service attack against an<br>
someone on the IESG, recommending that they filter someone who has<br>
proven that they are lacking in clue doesn&#39;t seem to me to be the same<=
br>
thing as a &quot;private club&quot;.<br>
<br>
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0=
 =A0 - Ted<br>
<br>
</blockquote></div><br></div>

--001a113376904919f404f380028b--


From nobody Fri Feb 28 15:52:19 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 B19C61A032A for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 15:52:17 -0800 (PST)
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 FHjejMnWSW1i for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 15:52:16 -0800 (PST)
Received: from mail-pa0-x231.google.com (mail-pa0-x231.google.com [IPv6:2607:f8b0:400e:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 644A11A024A for <ietf@ietf.org>; Fri, 28 Feb 2014 15:52:16 -0800 (PST)
Received: by mail-pa0-f49.google.com with SMTP id hz1so1408918pad.36 for <ietf@ietf.org>; Fri, 28 Feb 2014 15:52:14 -0800 (PST)
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=hLOXGBeM7+cBZrrRe7+A0LK+kQOijJTfLi9uxvlnaoU=; b=GxvoJfIgNueYPK4Hazv3WG4jtOa/JbGH0kaDKp8su8t1wruJrwrgyHcNV6YrIovkJ8 Ol5nKwfGRWJgOrn1ldMF2jLPvSNn5HRhyk6sAZnTV3EKMzVAEcbpYWmPFEYawZcWczoS q/QwTjfXrIHv6Ev9qC/VTx5sDClpefscewdIXcRaoq+t3vzHdmvYIEMTlUr7KF0B794y kySSipslanK7w1GmsKXFrpldrcjtBIl1+IC9bBUWrUzMYzCFwCnwXcciKhYxibjOCSE3 mSPjn5pkgyb4kGRPe8yJp5QJj3Mzx2X3qsSYNXQKviWVY3ZL7CtE6GGUb7yhwqSkJJuq EBDA==
MIME-Version: 1.0
X-Received: by 10.68.170.36 with SMTP id aj4mr6656996pbc.54.1393631534517; Fri, 28 Feb 2014 15:52:14 -0800 (PST)
Received: by 10.66.220.102 with HTTP; Fri, 28 Feb 2014 15:52:14 -0800 (PST)
In-Reply-To: <CADnDZ8_ZgDp-rWETgdMp7o+XXVXcHv2B58h-Pon=5xmgi0e8uQ@mail.gmail.com>
References: <20140224213030.C5E6718C126@mercury.lcs.mit.edu> <530CBFB7.90802@bbn.com> <01P4RNW46DFQ00004W@mauve.mrochek.com> <CADnDZ8_ZgDp-rWETgdMp7o+XXVXcHv2B58h-Pon=5xmgi0e8uQ@mail.gmail.com>
Date: Fri, 28 Feb 2014 15:52:14 -0800
Message-ID: <CAL0qLwYvuSEJTdybbVAECdqwAOQrvfcCZoSoAfb+rDFpCG_YNg@mail.gmail.com>
Subject: Re: Ad hominems (was: Policy of WG chairs in organising time for presentations and face2face discussions)
From: "Murray S. Kucherawy" <superuser@gmail.com>
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bacb21c90143104f3802043
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/Sc6IeEzfuyh62WQE2HyE62x8elo
Cc: "ned+ietf@mauve.mrochek.com" <ned+ietf@mauve.mrochek.com>, "ietf@ietf.org" <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: Fri, 28 Feb 2014 23:52:17 -0000

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

On Fri, Feb 28, 2014 at 1:53 AM, Abdussalam Baryun <
abdussalambaryun@gmail.com> wrote:

> I agree to write a draft to help the suggestion of having future draft of
> defining an Ad hominems and preventing it.  Comments below,


I am fully on board with efforts to make participation by relative
newcomers more smooth and comfortable.  However, I feel the idea of
creating an RFC merely to define "ad hominem" and suggest ways to prevent
it is just a bit silly.  For example, I can imagine a citation like "Your
comment is an ad hominem, as defined in RFCxxxx.  Please don't do that, or
rephrase your question."  And I can imagine both veterans and newcomers
alike thinking that's just a bizarre thing to do, or to have to do.

Perhaps I'm just amazed that we've reached a point where we feel we
actually have to write down what things constitute professional conduct (or
the opposite).

-MSK

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

<div dir=3D"ltr">On Fri, Feb 28, 2014 at 1:53 AM, Abdussalam Baryun <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:abdussalambaryun@gmail.com" target=3D"_bla=
nk">abdussalambaryun@gmail.com</a>&gt;</span> wrote:<br><div class=3D"gmail=
_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">I agree to write =
a draft to help the suggestion of having future=A0draft of defining=A0an Ad=
 hominems and preventing it.=A0=A0Comments below,</blockquote>
<div><br></div><div>I am fully on board with efforts to make participation =
by relative newcomers more smooth and comfortable.=A0 However, I feel the i=
dea of creating an RFC merely to define &quot;ad hominem&quot; and suggest =
ways to prevent it is just a bit silly.=A0 For example, I can imagine a cit=
ation like &quot;Your comment is an ad hominem, as defined in RFCxxxx.=A0 P=
lease don&#39;t do that, or rephrase your question.&quot;=A0 And I can imag=
ine both veterans and newcomers alike thinking that&#39;s just a bizarre th=
ing to do, or to have to do.<br>
<br></div><div>Perhaps I&#39;m just amazed that we&#39;ve reached a point w=
here we feel we actually have to write down what things constitute professi=
onal conduct (or the opposite).<br><br></div><div>-MSK<br></div></div></div=
>
</div>

--047d7bacb21c90143104f3802043--


From nobody Fri Feb 28 15:57:56 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 E79021A02CA for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 15:57:54 -0800 (PST)
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 KEL4YbFQtAGt for <ietf@ietfa.amsl.com>; Fri, 28 Feb 2014 15:57:53 -0800 (PST)
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 4CE581A02A7 for <ietf@ietf.org>; Fri, 28 Feb 2014 15:57:53 -0800 (PST)
Received: (qmail 27893 invoked from network); 28 Feb 2014 23:57:50 -0000
Received: from miucha.iecc.com (64.57.183.18) by mail1.iecc.com with QMQP; 28 Feb 2014 23:57:50 -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=53112280.xn--hew.k1402; i=johnl@user.iecc.com; bh=tUntLcKQ72wA3FnTsTunNbz/1x1kcL2B5lPrg08gnhY=; b=EU/hqunqqW7TCAy0+FIaDO9/HmsymuboDzRSP8oeEGmpyr6JukCqwYM3+WaCek7XzGXSfyOvST4/i0Fjd/NVbeOX1Fb8dN/QnZayTK+9gzZ2Xi6JI0ZEALEC4IBB0c8LUIhm99xSFBRv/12/nE/UcBQJZthYNZdpYEavT4kXI9iAGm5uFyI58NiVRWpKUU+hmggaXNp3NUEFXFhvQ5xm2sLNVCc2pPg/QjSTEApysXGUGzxQKX9E2ydyw9NsaJeV
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=53112280.xn--hew.k1402; bh=tUntLcKQ72wA3FnTsTunNbz/1x1kcL2B5lPrg08gnhY=; b=RpR+5rvqmE7jslnfaujuPqy0a43QmhkyvXi+EBml0AKpLREqK5mnY45PyUb5I6WXZAtoNKgH9QLALDnANhzSCEWUmJkmP105cjF2a7WGEzuEiOgl6/g+Up/CTOL7i9RU/36cNX8HnYugIHzpYfqHIJN9ykky+1ffyfq/jtqyHVsUg0pdkvrl66x90GYgPyLFT5WL3VJcs7jxTmof/VSMI9dkJqbMO2BurvdV0PU5NK6+gr4hs28H+rdHXq2PJrQw
Date: 28 Feb 2014 23:57:30 -0000
Message-ID: <20140228235730.34274.qmail@joyce.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: We're officially a cabal
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/xHlKNDCeTdHN8ZATVuZwrL3JMKs
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Feb 2014 23:57:55 -0000

See "These six organizations secretly run the Internet":

http://bgr.com/2014/02/19/who-runs-the-internet-6-secret-companies/

The IETF is #3, while the IAB is only #5.

R's,
John

PS: The ITU is #6.

PPS: Please feel free to send corrections to the author of the
article, not to this list.


From nobody Fri Feb 28 23:38:15 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 D972C1A064A; Fri, 28 Feb 2014 23:38:07 -0800 (PST)
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, MANGLED_LIST=2.3, 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 ZGaLgYuI1Ao8; Fri, 28 Feb 2014 23:38:06 -0800 (PST)
Received: from p3plsmtpa08-09.prod.phx3.secureserver.net (p3plsmtpa08-09.prod.phx3.secureserver.net [173.201.193.110]) by ietfa.amsl.com (Postfix) with ESMTP id 7A1361A0642; Fri, 28 Feb 2014 23:38:06 -0800 (PST)
Received: from spectre ([173.8.184.78]) by p3plsmtpa08-09.prod.phx3.secureserver.net with  id Y7e21n00C1huGat017e2iJ; Sat, 01 Mar 2014 00:38:04 -0700
From: "Peter Yee" <peter@akayla.com>
To: <draft-fairhurst-ipdvb-ule-iana.all@tools.ietf.org>
Subject: Gen-ART LC review of draft-fairhurst-ipdvb-ule-iana-05
Date: Fri, 28 Feb 2014 23:38:09 -0800
Message-ID: <094c01cf3521$3246d710$96d48530$@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: Ac81HgXbbOG0QnGwTUW8b/mclBzGGg==
Content-Language: en-us
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf/oOwkYhPUK8Jf-yLub_carBzZkWQ
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: Sat, 01 Mar 2014 07:38:08 -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-fairhurst-ipdvb-ule-iana-05
Reviewer: Peter Yee
Review Date: February-27-2014
IETF LC End Date: February-28-2014
IESG Telechat date: TBD

Summary: This draft is basically ready for publication as a Standards Track
RFC, but has nits that should be fixed before publication. [Ready with
nits.]

This document updates the IANA rules for maintenance of the ULE Next-Header
registry, as originally specified in RFC 4326.


Nits:

General nits:

Throughout the document, make all references to the registry in question
read "Next-Header registry" for consistency with RFC 4326, except in titles
or section headers where each word would be capitalized.


Specific nits:

Page 1, Title: consider inserting "Next-Header" between "ULE" and "Registry"
since that's the registry in question.

Page 1, Abstract, 2nd sentence: change "codepoints" to "code points" to
align with RFC 4259 and ATSC usage.

Page 3, Section 2.1, 1st sentence of the 1st and second paragraphs: you
refer to Mandatory Extension Headers and Optional Extension Headers
registries.  From RFC 4326, these are really subdivisions of the single
Next-Header registry.  You might want to rephrase those sentences to reflect
that you are not defining two registries.

Page 3, Section 2.1, 1st paragraph, 3rd sentence: Should that be "or the
specified protocol" or "of the specified protocol"?  I wasn't certain from
the context in RFC 4326 how the type values are used.

Page 3, Section 3, 1st paragraph, 2nd sentence: replace "these" with "them".

Page 5, 1st partial paragraph, last sentence: change "can not" to "cannot";
change "guarenteed" to "guaranteed".

Page 5, 1st full paragraph, last sentence: insert "is" between "that" and
"to".  

Page 5, Section 4, 1st paragraph: insert "an" between "record" and
"additional"

Section 8: as this section will be removed, no corrections are noted.

		-Peter Yee



